[Bug 790220] Re: Kernel panic from nfsd on lightly loaded system
** Tags removed: hibernate resume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790220 Title: Kernel panic from nfsd on lightly loaded system -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790220] [NEW] Kernel panic from nfsd on lightly loaded system
Public bug reported: Binary package hint: nfs-kernel-server Twice in the past six months this box has experienced a kernel panic. There are two active client machines. The nfs exports are of a drbd (protocol C) mounted device formatted ext4 on an underlying 3ware 9650SE-16ML with 10 2TB WD RE4 SATA drives for a total of ~9TB. The networking includes an 4x LACP bonded network device. (Overkill, in hindsight.) CPU was fairly low at ~10%. There are no logs of the event, but we did snap a picture with a phone: http://geekomatic.ch/images /nfsd-goes-boom.jpg As I expect this to occur again at some point, I'm going to tweak the console settings in hopes of catching more information. Even peak loads are not that high...so adding some debug logging is an option. Let me know. Dropping the LACP is an option. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-server 2.6.32-24.43 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-24.43-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory Date: Mon May 30 14:52:34 2011 Frequency: Once every few months. InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release amd64 (20100427) Lsusb: Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 002: ID 8087:0020 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-24-server root=/dev/mapper/hostname-root ro ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux dmi.bios.date: 10/28/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3878.2009.1028.1049 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55KG dmi.board.vendor: Intel Corporation dmi.board.version: AAE47218-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3878.2009.1028.1049:bd10/28/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55KG:rvrAAE47218-404:cvn:ct2:cvr: ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hibernate lucid needs-upstream-testing resume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790220 Title: Kernel panic from nfsd on lightly loaded system -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790220] Re: Kernel panic from nfsd on lightly loaded system
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790220 Title: Kernel panic from nfsd on lightly loaded system -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652388] [NEW] package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
Public bug reported: 1) Version: ubuntu 10.04.1 LTS 2) mst...@desktop:~$ apt-cache policy fglrx fglrx: Installed: 2:8.723.1-0ubuntu5 Candidate: 2:8.723.1-0ubuntu5 Version table: *** 2:8.723.1-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/restricted Packages 100 /var/lib/dpkg/status 2:8.723.1-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/restricted Packages 3) it to install 4) it broke while building, it was being upgraded by the update manager. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: fglrx 2:8.723.1-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic-pae 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic-pae i686 Architecture: i386 Date: Thu Sep 30 09:39:40 2010 DkmsStatus: fglrx, 8.723.1: added ErrorMessage: fglrx kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: Dell Inc. OptiPlex 760 PackageVersion: 2:8.723.1-0ubuntu5 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic-pae root=UUID=399582a3-61d6-4827-8895-e8f7ff6da436 ro quiet splash SourcePackage: fglrx-installer Title: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build dmi.bios.date: 08/03/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0M863N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/03/2010:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M863N:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-25-generic-pae ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/652388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652388] Re: package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build
** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659293/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659294/+files/CurrentDmesg.txt ** Attachment added: DKMSBuildLog.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659295/+files/DKMSBuildLog.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659296/+files/Dependencies.txt ** Attachment added: GdmLog.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659297/+files/GdmLog.txt ** Attachment added: GdmLog1.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659298/+files/GdmLog1.txt ** Attachment added: GdmLog2.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659299/+files/GdmLog2.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659300/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659301/+files/Lsusb.txt ** Attachment added: PciDisplay.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659302/+files/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659303/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659304/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659305/+files/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659306/+files/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659307/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659308/+files/UdevLog.txt ** Attachment added: XorgConf.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659309/+files/XorgConf.txt ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659310/+files/XorgLog.txt ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659311/+files/XorgLogOld.txt ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659312/+files/Xrandr.txt ** Attachment added: make.log.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659313/+files/make.log.txt ** Attachment added: setxkbmap.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659314/+files/setxkbmap.txt ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659315/+files/xdpyinfo.txt ** Attachment added: xkbcomp.txt https://bugs.launchpad.net/bugs/652388/+attachment/1659316/+files/xkbcomp.txt -- package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel module failed to build https://bugs.launchpad.net/bugs/652388 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569900] Re: mount: mounting /dev/md0 on /root/ failed: Invalid argument
I've also had the same issue, but with smaller disks: WD RE3 250GB (WD2502ABYS) Using the suggested sizes when creating the md* devices (a single ext3 / partition + one swap partition) resulted with the Invalid argument error message and the initramfs prompt. Manually defining the size to be slightly less than the suggested size worked like a charm. Stu -- mount: mounting /dev/md0 on /root/ failed: Invalid argument https://bugs.launchpad.net/bugs/569900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
