Ubuntu
linux package

WARNING: at /build/buildd/linux-2.6.35/mm/slub.c:2794 ksize+0x88/ 0x90()

Bug #695703 reported by Brian J. Murrell on 2010-12-30

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

While trying to mount an NFS filesystem the mount command hung and errors were reported in dmesg, which can been seen in the dmesg attachment to this bug. The command I was using to mount:

$ sudo mount linux:/usr/local /mnt/test/

Which was denied by the server:

mount.nfs: access denied by server while mounting linux:/usr/local

This denial was expected as the export requires a GSS credential. Above, I was just testing that an NFS3 mount would fail.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: brian 4005 F.... pulseaudio
/dev/snd/controlC2: brian 4005 F.... pulseaudio
/dev/snd/controlC1: brian 4005 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 22'
   Mixer name : 'Analog Devices AD1986A'
   Components : 'HDA:11d41986,104381b3,00100500'
   Controls : 37
   Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'U0x46d0x8c5'/'USB Device 0x46d:0x8c5 at usb-0000:00:0b.1-4, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08c5'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 3072
   Mono: Capture 0 [0%] [18.00dB] [on]
Card2.Amixer.info:
Card hw:2 'Live'/'SB Live! Value [CT4832] (rev.7, serial:0x80271102) at 0xbc00, irq 17'
   Mixer name : 'TriTech TR28602'
   Components : 'AC97a:54524123'
   Controls : 216
   Simple ctrls : 38
Date: Thu Dec 30 09:28:55 2010
Lsusb:
Bus 002 Device 002: ID 04f9:01e9 Brother Industries, Ltd
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 046d:08c5 Logitech, Inc. QuickCam Pro 5000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-24-generic root=/dev/mapper/rootvol-ubuntu_root ro console=ttyS0,115200 console=tty0 crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 08/07/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401
dmi.board.name: M2NPV-VM
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NPV-VMACPIBIOSRevision1401:bd08/07/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnM2NPV-VM:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Tags:

Revision history for this message

Brian J. Murrell (brian-interlinx) wrote on 2010-12-30:

AcpiTables.txt Edit (128.7 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (1.3 KiB, text/plain; charset="utf-8")
AplayDevices.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ArecordDevices.txt Edit (691 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (54.6 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (4.7 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (11.6 KiB, text/plain; charset="utf-8")
Card2.Amixer.values.txt Edit (9.7 KiB, text/plain; charset="utf-8")
Card2.Codecs.codec97.0.ac97.0.0.txt Edit (411 bytes, text/plain; charset="utf-8")
Card2.Codecs.codec97.0.ac97.0.0.regs.txt Edit (767 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (66.8 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (138 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (13.8 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.2 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (131.6 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (270.5 KiB, text/plain; charset="utf-8")
UserAsoundrc.txt Edit (1.1 KiB, text/plain; charset="utf-8")
UserAsoundrcAsoundconf.txt Edit (2.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (179.8 KiB, text/plain; charset="utf-8")

Brad Figg (brad-figg) on 2011-04-07

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2012-04-08:

Brian J. Murrell, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Brian J. Murrell (brian-interlinx) wrote on 2012-04-08: Re: [Bug 695703] Re: WARNING: at /build/buildd/linux-2.6.35/mm/slub.c:2794 ksize+0x88/ 0x90()

On 12-04-08 03:45 PM, Christopher M. Penalver wrote:
> Brian J. Murrell, thank you for reporting this and helping make Ubuntu better.

You are welcome. I just wish my reports actually led to bug fixing
activity.

> Maverick reached EOL on April 2012.

Uhm. It's still April 2012 so it's not EOL yet.

Besides, you are reporting Maverick is EOL as if I only just reported
this bug yesterday. Not at all. I reported this bug 16 months ago,
while Maverick was still a very supported release and yet there hasn't
been a single thing done with this bug report the entire time except
changing it from New -> Confirmed, 4 months after it was reported.

> Please see this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases

Again, I say, this was a completely supported release when I reported
this bug so please don't lecture me on how to determine supported
releases. I know fine well what releases are supported and which ones
are not. Apparently, given that this report was completely ignored, you
folks do not understand what's a supported release and what is not.

> We were wondering if this is still an issue in a supported release?

Oh, unlike the supported release it was in 16 months ago when I first
reported it?

> If
> so, can you try with the latest development release of Ubuntu?

Why would I bother? So that this bug report can sit around for more
years to come until you can tell me it's on an unsupported release again?

> Also, if you could test the latest upstream kernel available that would
> be great.

Again, a whole lot of work on my part only to have this bug sit moribund
for years to come again. No thanks. I've already done my part and you
failed to do you part so why would I enter into that agreement again?

> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete

LOL. And now from Confirmed to Incomplete? You folks kill me.

I am sorry for my attitude here but the lack of activity on this bug is
all-too-common for the bugs I report about Ubuntu and I'm just so tired
of it.

On 12-04-08 03:45 PM, Christopher M. Penalver wrote:
> Brian J. Murrell, thank you for reporting this and helping make Ubuntu better.

You are welcome.  I just wish my reports actually led to bug fixing
activity.

> Maverick reached EOL on April 2012.

Uhm.  It's still April 2012 so it's not EOL yet.

Besides, you are reporting Maverick is EOL as if I only just reported
this bug yesterday.  Not at all.  I reported this bug 16 months ago,
while Maverick was still a very supported release and yet there hasn't
been a single thing done with this bug report the entire time except
changing it from New -> Confirmed, 4 months after it was reported.

> Please see this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases

Again, I say, this was a completely supported release when I reported
this bug so please don't lecture me on how to determine supported
releases.  I know fine well what releases are supported and which ones
are not.  Apparently, given that this report was completely ignored, you
folks do not understand what's a supported release and what is not.

> We were wondering if this is still an issue in a supported release?

Oh, unlike the supported release it was in 16 months ago when I first
reported it?

> If
> so, can you try with the latest development release of Ubuntu?

Why would I bother?  So that this bug report can sit around for more
years to come until you can tell me it's on an unsupported release again?

> Also, if you could test the latest upstream kernel available that would
> be great.

Again, a whole lot of work on my part only to have this bug sit moribund
for years to come again.  No thanks.  I've already done my part and you
failed to do you part so why would I enter into that agreement again?

> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete

LOL.  And now from Confirmed to Incomplete?  You folks kill me.

I am sorry for my attitude here but the lack of activity on this bug is
all-too-common for the bugs I report about Ubuntu and I'm just so tired
of it.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-06-09:

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

WARNING: at /build/buildd/linux-2.6.35/mm/slub.c:2794 ksize+0x88/ 0x90()

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package