kernel BUG at /build/buildd/linux-2.6.35/net/sunrpc/rpc_pipe.c:474!; EIP is at __rpc_create_common+0x79/0xb0 [sunrpc]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
I found my machine "hung" (not really, just unable to do much of anything with it since nfs4 was wedged) and discovered the following in the syslog (in the WifiSyslog attachment):
Jan 17 07:23:02 pc kernel: [150100.860016] kernel BUG at /build/
Jan 17 07:23:02 pc kernel: [150100.865098] invalid opcode: 0000 [#1] SMP
Jan 17 07:23:02 pc kernel: [150100.865098] last sysfs file: /sys/devices/
Jan 17 07:23:02 pc kernel: [150100.879734] Modules linked in: des_generic binfmt_misc vboxnetadp vboxnetflt vboxdrv ipt_MASQUERADE iptable_nat bridge stp kvm_amd kvm autofs4 xt_hl nf_conntrack_ipv6 xt_limit ipt_REJECT xt_tcpudp ipt_addrtype snd_hda_
Jan 17 07:23:02 pc kernel: q raid6_pq async_xor async_memcpy async_tx raid1 raid0 multipath linear dm_raid45 floppy firewire_ohci firewire_core xor sata_nv pata_amd forcedeth crc_itu_t
Jan 17 07:23:02 pc kernel: [150100.879734]
Jan 17 07:23:02 pc kernel: [150100.879734] Pid: 16730, comm: mount.nfs4 Tainted: P 2.6.35-24-generic #42-Ubuntu M2NPV-VM/System Product Name
Jan 17 07:23:02 pc kernel: [150100.879734] EIP: 0060:[<f8289f39>] EFLAGS: 00010246 CPU: 0
Jan 17 07:23:02 pc kernel: [150100.879734] EIP is at __rpc_create_
Jan 17 07:23:02 pc kernel: [150100.879734] EAX: ec9a1e00 EBX: ec9a1e00 ECX: 00001180 EDX: f6739770
Jan 17 07:23:02 pc kernel: [150100.879734] ESI: ec9a1e78 EDI: f6739770 EBP: efddbbb4 ESP: efddbb98
Jan 17 07:23:02 pc kernel: [150100.879734] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 17 07:23:02 pc kernel: [150100.879734] Process mount.nfs4 (pid: 16730, ti=efdda000 task=f6ae0cb0 task.ti=efdda000)
Jan 17 07:23:02 pc kernel: [150100.879734] Stack:
Jan 17 07:23:02 pc kernel: [150100.879734] f6f12000 efddbbf4 f835a2b0 efddbbb4 f6739770 ec9a1e78 f835a2b0 efddbc0c
Jan 17 07:23:02 pc kernel: [150100.879734] <0> f828a101 f828e5a0 f1d86700 c08c4700 c08c4700 f6ae0cb0 ffffffff f1d86700
Jan 17 07:23:02 pc kernel: [150100.879734] <0> ec9a1e00 f835a2b0 f6f12000 c07c1180 efddbc0c efddbbf4 c05c978d 019ab38c
Jan 17 07:23:02 pc kernel: [150100.879734] Call Trace:
Jan 17 07:23:02 pc kernel: [150100.879734] [<f828a101>] ? rpc_mkpipe+
Jan 17 07:23:02 pc kernel: [150100.879734] [<c05c978d>] ? _raw_spin_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8355a0d>] ? gss_create+
Jan 17 07:23:02 pc kernel: [150100.879734] [<f827bfd8>] ? xs_setup_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f827e629>] ? rpcauth_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8280030>] ? svc_process_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8277345>] ? rpc_new_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f827da57>] ? __rpc_init_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8277545>] ? rpc_create+
Jan 17 07:23:02 pc kernel: [150100.879734] [<f84c6ea8>] ? __fscache_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f84c6ea8>] ? __fscache_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8379ae4>] ? nfs_create_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8379bb7>] ? nfs4_init_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f837ada0>] ? nfs4_set_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f837aeb4>] ? nfs4_init_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f837b053>] ? nfs4_create_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f83854eb>] ? nfs4_remote_
Jan 17 07:23:02 pc kernel: [150100.879734] [<c020fadf>] ? __alloc_
Jan 17 07:23:02 pc kernel: [150100.879734] [<c0231629>] ? alloc_vfsmnt+
Jan 17 07:23:02 pc kernel: [150100.879734] [<c021b354>] ? vfs_kern_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f83868b9>] ? nfs_do_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f83869bf>] ? nfs4_try_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8386ca1>] ? nfs_alloc_
Jan 17 07:23:02 pc kernel: [150100.879734] [<f8386d50>] ? nfs4_get_
Jan 17 07:23:02 pc kernel: [150100.879734] [<c0231629>] ? alloc_vfsmnt+
Jan 17 07:23:02 pc kernel: [150100.879734] [<c021b354>] ? vfs_kern_
Jan 17 07:23:02 pc kernel: [150100.879734] [<c022f9b3>] ? get_fs_
Jan 17 07:23:02 pc kernel: [150100.879734] [<c021b4fe>] ? do_kern_
Jan 17 07:23:02 pc kernel: [150100.879734] [<c0232b2c>] ? do_mount+
Jan 17 07:23:02 pc kernel: [150100.879734] [<c0232bdb>] ? sys_mount+0x6b/0xa0
Jan 17 07:23:02 pc kernel: [150100.879734] [<c05c9cc4>] ? syscall_
Jan 17 07:23:02 pc kernel: [150100.879734] Code: 00 8b 5d 0c 85 db 74 09 8b 45 0c 89 86 60 01 00 00 89 f2 89 f8 e8 78 0a fa c7 89 f8 e8 61 00 fa c7 31 c0 83 c4 10 5b 5e 5f 5d c3 <0f> 0b eb fe 8b 47 28 c7 44 24 08 40 e5 28 f8 c7 44 24 04 24 1d
Jan 17 07:23:02 pc kernel: [150100.879734] EIP: [<f8289f39>] __rpc_create_
Jan 17 07:23:02 pc kernel: [150101.268626] ---[ end trace 00cfd37e849c2caa ]---
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
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,
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.
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: Mon Jan 17 08:33:13 2011
Frequency: Once every few weeks.
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=
ProcEnviron:
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageV
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.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Brian J. Murrell, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
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/KernelMainl ineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel- unable- to-test- upstream' , and comment as to why specifically you were unable to test it.
Please let us know your results. Thanks in advance.
Helpful Bug Reporting Links: /help.ubuntu. com/community/ ReportingBugs# Bug_Reporting_ Etiquette /help.ubuntu. com/community/ ReportingBugs# A3._Make_ sure_the_ bug_hasn. 27t_already_ been_reported /help.ubuntu. com/community/ ReportingBugs# Adding_ Apport_ Debug_Informati on_to_an_ Existing_ Launchpad_ Bug /help.ubuntu. com/community/ ReportingBugs# Adding_ Additional_ Attachments_ to_an_Existing_ Launchpad_ Bug
https:/
https:/
https:/
https:/