[Bug 973270] Re: Printer does not provide REQUIRED job history.
This bug needs to be reopened. Closing it because of some hardware issue when affected hardware clearly could be driven properly in earlier versions is a cop out. The reality is, users are affected by the software upgrade adversely. Blaming it on the hardware is silly. Even if that hardware contains a flaw, it clearly can be worked around - in this case, by choosing a different protocol. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973270 Title: Printer does not provide REQUIRED job history. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/973270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613995] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/53124235/Dependencies.txt -- Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed. https://bugs.launchpad.net/bugs/613995 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 613995] Re: Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed.
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: criticalmass criticalmass tries to start (fullscreen), gets my screens (dual-screen setup) into 640x480 video mode, and then crashes and burns with the following error: criticalmass: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion `mt->mesaFormat == image->base.TexFormat' failed. Leaving my desktop behind in 640x480 isn't funny, I tell you. Why doesn't X recover from something like that gracefully? But I digress .. I also found this bug in the RedHat bugzilla, so I'm not the only one. Here is the bug ID: https://bugzilla.redhat.com/show_bug.cgi?id=575432 - I will come back later and fill in any other details such as the - backtrace you folks undoubtedbly need ;-) + I will come back later and fill in any other details such as the backtrace you folks undoubtedbly need ;-) + --- + Architecture: i386 + DistroRelease: Ubuntu 10.04 + Package: criticalmass 1:1.0.0-1.2ubuntu1 + PackageArchitecture: i386 + ProcEnviron: + LANGUAGE=en_US:en + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 + Tags: lucid + Uname: Linux 2.6.32-24-generic i686 + UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev users video ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/53124184/Dependencies.txt ** Description changed: Binary package hint: criticalmass criticalmass tries to start (fullscreen), gets my screens (dual-screen setup) into 640x480 video mode, and then crashes and burns with the following error: criticalmass: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion `mt->mesaFormat == image->base.TexFormat' failed. Leaving my desktop behind in 640x480 isn't funny, I tell you. Why doesn't X recover from something like that gracefully? But I digress .. I also found this bug in the RedHat bugzilla, so I'm not the only one. Here is the bug ID: https://bugzilla.redhat.com/show_bug.cgi?id=575432 I will come back later and fill in any other details such as the backtrace you folks undoubtedbly need ;-) --- Architecture: i386 DistroRelease: Ubuntu 10.04 Package: criticalmass 1:1.0.0-1.2ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Tags: lucid Uname: Linux 2.6.32-24-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev users video + + --- + Architecture: i386 + DistroRelease: Ubuntu 10.04 + Package: criticalmass 1:1.0.0-1.2ubuntu1 + PackageArchitecture: i386 + ProcEnviron: + LANGUAGE=en_US:en + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 + Tags: lucid + Uname: Linux 2.6.32-24-generic i686 + UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev users video -- Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed. https://bugs.launchpad.net/bugs/613995 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 613995] Re: Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed.
I've added the line: "set resolutions = 1280x960,1152x864,1024x768" to the configuration file in ~/.critter/critter_config.txt before generating that startup log. That didn't actually fix the crash, but it did prevent criticalmass from putting my screen in 640x480 first. -- Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed. https://bugs.launchpad.net/bugs/613995 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 613995] Re: Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed.
Startup log. ** Attachment added: "critter_output.txt" http://launchpadlibrarian.net/53123421/critter_output.txt -- Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed. https://bugs.launchpad.net/bugs/613995 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 613995] [NEW] Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed.
Public bug reported: Binary package hint: criticalmass criticalmass tries to start (fullscreen), gets my screens (dual-screen setup) into 640x480 video mode, and then crashes and burns with the following error: criticalmass: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion `mt->mesaFormat == image->base.TexFormat' failed. Leaving my desktop behind in 640x480 isn't funny, I tell you. Why doesn't X recover from something like that gracefully? But I digress .. I also found this bug in the RedHat bugzilla, so I'm not the only one. Here is the bug ID: https://bugzilla.redhat.com/show_bug.cgi?id=575432 I will come back later and fill in any other details such as the backtrace you folks undoubtedbly need ;-) ** Affects: criticalmass (Ubuntu) Importance: Undecided Status: New ** Affects: criticalmass (Fedora) Importance: Unknown Status: Unknown ** Visibility changed to: Public ** This bug is no longer flagged as a security vulnerability ** Bug watch added: Red Hat Bugzilla #575432 https://bugzilla.redhat.com/show_bug.cgi?id=575432 ** Also affects: criticalmass (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=575432 Importance: Unknown Status: Unknown -- Criticalmass crashes at start with the error: radeon_mipmap_tree.c:420: migrate_image_to_miptree: Assertion mt->mesaFormat == image->base.TexFormat' failed. https://bugs.launchpad.net/bugs/613995 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 325973] Re: gnome-session keeps respawning nautilus when no desktop is drawed
karmic. Me too ;-) -- gnome-session keeps respawning nautilus when no desktop is drawed https://bugs.launchpad.net/bugs/325973 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
Re: [Bug 367828] Re: Add a symbolic link to the latest generated chart
On Mon, Apr 27, 2009 at 4:41 PM, Scott James Remnant wrote: > On Mon, 2009-04-27 at 14:25 +0000, Randakar wrote: > >> Oh, it's fairly simple: I'm tweaking a server a bit and want to have >> the latest boot posted on a static webpage somewhere. >> > Bootcharts don't mean anything on their own. > > It's a useful tool to assess the impact of a change; but for that you > need to know what change was made, and have the before and after > bootcharts for comparison. > > Thus the "latest" bootchart doesn't really mean much. > It does tell me whether the system has rebooted yet ;-) This is not really something I use for comparing boot times per se, it's part of a "here's the current server status" page. This system is for educational use and I use this mostly to show what kind of toys are on there for people to play with ;-) Regards, Floris --- 'Or lawyers may say, “But if I decline, someone else will do it. So what is gained?” My reply: “Let someone else do it. But not you. Honor is personal. Worry about yourself. You don’t get a pass from moral responsibility because you acted for a client.” That’s the first lesson I would offer, aimed at lawyers. A second lesson, aimed at all, is this: Keep ready your capacity for outrage. This is very important. Next to the vote, outrage is the one response each of us can contribute. Outrage is how honor must confront dishonor. If we lose the capacity for outrage, we are in serious trouble. ' --- Stephen Gillers -- Add a symbolic link to the latest generated chart https://bugs.launchpad.net/bugs/367828 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
Re: [Bug 367828] Re: Add a symbolic link to the latest generated chart
On Mon, Apr 27, 2009 at 3:02 PM, Scott James Remnant wrote: > I'm not sure that I see the point of this. > Oh, it's fairly simple: I'm tweaking a server a bit and want to have the latest boot posted on a static webpage somewhere. Since the 'latest boot' is not statically known I just added this symlink to provide a static name thus avoiding complicated code to find the latest boot chart and link that in dynamically. Like I said, it's a nice to have, nothing more. Symlinks are fairly lightweight so it doesn't hurt does it? Regards, Floris -- 'Or lawyers may say, “But if I decline, someone else will do it. So what is gained?” My reply: “Let someone else do it. But not you. Honor is personal. Worry about yourself. You don’t get a pass from moral responsibility because you acted for a client.” That’s the first lesson I would offer, aimed at lawyers. A second lesson, aimed at all, is this: Keep ready your capacity for outrage. This is very important. Next to the vote, outrage is the one response each of us can contribute. Outrage is how honor must confront dishonor. If we lose the capacity for outrage, we are in serious trouble. ' --- Stephen Gillers -- Add a symbolic link to the latest generated chart https://bugs.launchpad.net/bugs/367828 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 367828] Re: Add a symbolic link to the latest generated chart
** Description changed: Binary package hint: bootchart When the bootchart is generated a symbolic link to the latest generated bootchart in the target directory would be rather nice to have. This can be accomplished by changing the relevant bits in /etc/init.d /stop-bootchart into: --- # Generate SVG and optionally PNG if pybootchartgui is installed if [ -x /usr/bin/bootchart ]; then if grep -q "bootchart=svg" /proc/cmdline; then format=svg else format=png fi - bootchart -f $format -o "$CHARTS" "$TARBALL" && \ - ln -f -s "$BASE.$format" "$CHARTS/latest.$format" + bootchart -f $format -o "$CHARTS" "$TARBALL" && ln -f -s "$BASE.$format" "$CHARTS/latest.$format" fi --- (Adding the ln -s if bootchart is run without an error exit status) This is on Ubuntu 9.04, bootchart version 0.90.1-3 -- Add a symbolic link to the latest generated chart https://bugs.launchpad.net/bugs/367828 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 367828] [NEW] Add a symbolic link to the latest generated chart
Public bug reported: Binary package hint: bootchart When the bootchart is generated a symbolic link to the latest generated bootchart in the target directory would be rather nice to have. This can be accomplished by changing the relevant bits in /etc/init.d /stop-bootchart into: --- # Generate SVG and optionally PNG if pybootchartgui is installed if [ -x /usr/bin/bootchart ]; then if grep -q "bootchart=svg" /proc/cmdline; then format=svg else format=png fi bootchart -f $format -o "$CHARTS" "$TARBALL" && \ ln -f -s "$BASE.$format" "$CHARTS/latest.$format" fi --- (Adding the ln -s if bootchart is run without an error exit status) This is on Ubuntu 9.04, bootchart version 0.90.1-3 ** Affects: bootchart (Ubuntu) Importance: Undecided Status: New -- Add a symbolic link to the latest generated chart https://bugs.launchpad.net/bugs/367828 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 300089] Re: Warnings when compiling kernel
This affects Ubuntu 9.04 as well. The comment OP is referring to can be found in a LKML thread here: http://kerneltrap.org/mailarchive/linux-kernel/2008/11/20/4215134 Clearly this is a relatively harmless message - especially given the fact that mainline doesn't even see it. However, it pollutes my kernel builds for no good reason and gets in the way of doing 'real' work on it. Going forward I see several methods of resolving this: 1) Disable the "-Wformat-security" compiler option in gcc (but - presumably there was a reason for enabling it) 2) Disable said option inside kernel builds. - doing this makes it an upstream change. 3) Go through the kernel and fix all these warnings with a single mega-patch that is liable to never get accepted. Upstream change again. Given that I don't consider myself quite enough of an expert on the kernel sources and the security trade-offs inherent in the various choices here and given that any upstream kernel patch probably should make it's way through Ubuntu anyway some guidance from an ubuntu dev on this is appreciated ;-) -- Warnings when compiling kernel https://bugs.launchpad.net/bugs/300089 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 248738] Re: Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver)
Reply by email and reply in forum ftw .. ah well that's what you get for being impatient. -- Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver) https://bugs.launchpad.net/bugs/248738 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 248738] Re: Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver)
On Wed, Jul 16, 2008 at 1:44 AM, Chris Coulson <[EMAIL PROTECTED]> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately we can't fix it, because your description > does not yet have enough information. Very well. > > Please include the following additional information, if you have not already > done so (pay attention to lspci's additional options): > 1. Please include the output of the command "uname -a" in your next response. > It should be one, long line of text which includes the exact kernel version > you're running, as well as the CPU architecture. That's in there .. Linux vuurmuur 2.6.24-19-server #2 SMP Tue Feb 12 05:48:21 UTC 2008 i686 GNU/Linux > 2. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report. Done. > 3. Please attach your /etc/fstab to this bug report. Done. > 4. Please run "sudo fdisk -l > fdisk.log" and attach the resulting file "fdisk.log" to this bug report. Done. Note - this is 2.6.20 output. > 5. Please post the output of "ls -l /dev/disk/by-uuid". lrwxrwxrwx 1 root root 10 2008-07-15 08:19 0e6a0dc2-b469-4941-a58c-75ac821188f1 -> ../../hda5 lrwxrwxrwx 1 root root 10 2008-07-15 08:19 62805293-968a-4e16-a35d-e026974ed3f8 -> ../../hdc5 lrwxrwxrwx 1 root root 32 2008-07-15 08:19 a552512b-ae49-4c32-bb4b-eb4f28c62a58 -> ../../mapper/lvm2|Ubuntu|newroot lrwxrwxrwx 1 root root 29 2008-07-15 08:19 d33e8a5f-edd7-401d-bd2d-0356a36af37c -> ../../mapper/lvm2|Ubuntu|root If you're wondering what hdc is doing in there and not getting mounted; It's the old harddrive that started failing a while back, I haven't bothered to remove it from the system yet. Hence the root vs newroot mappings. -- Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver) https://bugs.launchpad.net/bugs/248738 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 248738] Re: Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver)
** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/16054220/lspci-vvnn.log -- Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver) https://bugs.launchpad.net/bugs/248738 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
Re: [Bug 248738] Re: Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver)
On Wed, Jul 16, 2008 at 1:44 AM, Chris Coulson <[EMAIL PROTECTED]> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately we can't fix it, because your description > does not yet have enough information. Very well. > > Please include the following additional information, if you have not already > done so (pay attention to lspci's additional options): > 1. Please include the output of the command "uname -a" in your next response. > It should be one, long line of text which includes the exact kernel version > you're running, as well as the CPU architecture. That's in there .. Linux vuurmuur 2.6.24-19-server #2 SMP Tue Feb 12 05:48:21 UTC 2008 i686 GNU/Linux > 2. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report. Will do shortly. > 3. Please attach your /etc/fstab to this bug report. Will do shortly. > 4. Please run "sudo fdisk -l > fdisk.log" and attach the resulting file "fdisk.log" to this bug report. Will do shortly. Note - this is 2.6.20 output. > 5. Please post the output of "ls -l /dev/disk/by-uuid". lrwxrwxrwx 1 root root 10 2008-07-15 08:19 0e6a0dc2-b469-4941-a58c-75ac821188f1 -> ../../hda5 lrwxrwxrwx 1 root root 10 2008-07-15 08:19 62805293-968a-4e16-a35d-e026974ed3f8 -> ../../hdc5 lrwxrwxrwx 1 root root 32 2008-07-15 08:19 a552512b-ae49-4c32-bb4b-eb4f28c62a58 -> ../../mapper/lvm2|Ubuntu|newroot lrwxrwxrwx 1 root root 29 2008-07-15 08:19 d33e8a5f-edd7-401d-bd2d-0356a36af37c -> ../../mapper/lvm2|Ubuntu|root If you're wondering what hdc is doing in there and not getting mounted; It's the old harddrive that started failing a while back, I haven't bothered to remove it from the system yet. Hence the root vs newroot mappings. Regards, Floris -- Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver) https://bugs.launchpad.net/bugs/248738 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 248738] Re: Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver)
** Attachment added: "fstab" http://launchpadlibrarian.net/16054214/fstab -- Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver) https://bugs.launchpad.net/bugs/248738 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 248738] Re: Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver)
** Attachment added: "fdisk.log" http://launchpadlibrarian.net/16054211/fdisk.log -- Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver) https://bugs.launchpad.net/bugs/248738 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 248738] [NEW] Unable to mount IDE partition after Kernel upgrade 2.6.20 -> 2.6.24 (PATA driver)
Public bug reported: After upgrading my dinky old firewall to Ubuntu 8.04 the kernel refuses to mount the /boot partition. Instead I get an error message saying (quoting from memory) "Unable to mount: Already mounted or /dev/sda5 is in use"). Affected package: linux-image-2.6.24-19-server Unaffected package: linux-image-2.6.20-16-server I've tried finding what process had opened the partition with lsof, even dropping down to runlevel 1 in an attempt to shut down all processes that might cause the device to be opened, but no such luck. Even after running 'telinit 1' the system refuses to mount /dev/sda5 anywhere. Not on /boot, not on a new mountpoint in /mnt, not anywhere else. Booting the 2.6.20 kernel resolves the issue. Therefore the kernel upgrade to 2.6.24 is likely to be the cause. The most telling symptom is that 2.6.24 apparently attempts to inflict a new PATA driver on the drives. 2.6.20 doesn't. All disk devices for the partitions get renamed from /dev/hd* to /dev/sd*. The partition in question is a small partition on /dev/hda5 or /dev/sda5 depending on the kernel used. The root partition lives on the same drive on LVM (hda6 / sda6) and is not affected. It mounts just fine. Here's dmesg output from the two kernels. 2.6.20 [0.00] Linux version 2.6.20-16-server ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Tue Feb 12 05:48:21 UTC 2008 (Ubuntu 2.6.20-16.35-server) [0.00] BIOS-provided physical RAM map: [0.00] sanitize start [0.00] sanitize end [0.00] copy_e820_map() start: size: 0009f800 end: 0009f800 type: 1 [0.00] copy_e820_map() type is E820_RAM [0.00] copy_e820_map() start: 0009f800 size: 0800 end: 000a type: 2 [0.00] copy_e820_map() start: 000e size: 0002 end: 0010 type: 2 [0.00] copy_e820_map() start: 0010 size: 13f0 end: 1400 type: 1 [0.00] copy_e820_map() type is E820_RAM [0.00] copy_e820_map() start: fff8 size: 0008 end: 0001 type: 2 [0.00] BIOS-e820: - 0009f800 (usable) [0.00] BIOS-e820: 0009f800 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 1400 (usable) [0.00] BIOS-e820: fff8 - 0001 (reserved) [0.00] 0MB HIGHMEM available. [0.00] 320MB LOWMEM available. [0.00] Entering add_active_range(0, 0, 81920) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] Normal 4096 ->81920 [0.00] HighMem 81920 ->81920 [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 ->81920 [0.00] On node 0 totalpages: 81920 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 608 pages used for memmap [0.00] Normal zone: 77216 pages, LIFO batch:15 [0.00] HighMem zone: 0 pages used for memmap [0.00] DMI 2.0 present. [0.00] ACPI: Unable to locate RSDP [0.00] Allocating PCI resources starting at 2000 (gap: 1400:ebf8) [0.00] Detected 266.702 MHz processor. [ 36.465775] Built 1 zonelists. Total pages: 81280 [ 36.465800] Kernel command line: root=/dev/mapper/Ubuntu-newroot ro quiet splash [ 36.467247] Local APIC disabled by BIOS -- you can enable it with "lapic" [ 36.467306] mapped APIC to d000 (0128b000) [ 36.467370] Initializing CPU#0 [ 36.467581] PID hash table entries: 2048 (order: 11, 8192 bytes) [ 36.469320] Console: colour VGA+ 80x25 [ 36.471193] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 36.473062] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 36.539364] Memory: 312464k/327680k available (2020k kernel code, 14608k reserved, 901k data, 332k init, 0k highmem) [ 36.539450] virtual kernel memory layout: [ 36.539460] fixmap : 0xfff4f000 - 0xf000 ( 704 kB) [ 36.539472] pkmap : 0xffc0 - 0xffe0 (2048 kB) [ 36.539484] vmalloc : 0xd480 - 0xffbfe000 ( 691 MB) [ 36.539495] lowmem : 0xc000 - 0xd400 ( 320 MB) [ 36.539506] .init : 0xc03e1000 - 0xc0434000 ( 332 kB) [ 36.539517] .data : 0xc02f9319 - 0xc03da754 ( 901 kB) [ 36.539528] .text : 0xc010 - 0xc02f9319 (2020 kB) [ 36.539554] Checking if this processor honours the WP bit even in supervisor mode... Ok. [ 36.687545] Calibrating delay using timer specific routine.. 534.10 BogoMIPS (lpj=2670512) [ 36.687871] Security Framework v1.0.0 initialized [ 36.687936] SELinux:
[Bug 76530] Re: update-manager falls back to disttribution upgrade after python crashes in apt-check, due to a segfault in pkgcache::VerIterator::Downloadable
** Attachment added: "another crash dump" http://librarian.launchpad.net/5482239/_usr_bin_python.1000.crash -- update-manager falls back to disttribution upgrade after python crashes in apt-check, due to a segfault in pkgcache::VerIterator::Downloadable https://launchpad.net/bugs/76530 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76525] python crashes while running update notifier
Public bug reported: Logging in seems to be enough. The update-notifier crashes, in the crash report it looks like python is running /usr/lib/update-notifier/apt-check ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: Unconfirmed -- python crashes while running update notifier https://launchpad.net/bugs/76525 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73966] Re: [patch] update-grub is broken
That workaround probably should read 'remove linux-image-kdump OR set #alternatives=false in /boot/grub/menu.list' ;-) Nonetheless, good work. Thanks. -- [patch] update-grub is broken https://launchpad.net/bugs/73966 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76341] Re: [Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages
** Attachment added: "/var/log/messages (scroll to the end)" http://librarian.launchpad.net/5445612/messages.log.tar.bz2 -- [Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages https://launchpad.net/bugs/76341 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76341] Re: [Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages
** Attachment added: "lspci" http://librarian.launchpad.net/5445615/lspci -- [Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages https://launchpad.net/bugs/76341 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76341] [Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages
Public bug reported: Binary package hint: linux-source-2.6.20 When booting in 2.6.20, suddenly /var/log/messages is spammed with: Dec 18 21:52:45 localhost kernel: [ 163.416320] Intel ISA PCIC probe: not found. Dec 18 21:52:45 localhost kernel: [ 163.435252] Intel ISA PCIC probe: not found. Dec 18 21:52:45 localhost kernel: [ 163.482263] Intel ISA PCIC probe: not found. Dec 18 21:52:45 localhost kernel: [ 163.531793] Intel ISA PCIC probe: not found. Dec 18 21:52:45 localhost kernel: [ 163.579588] Intel ISA PCIC probe: not found. Dec 18 21:52:45 localhost kernel: [ 163.627409] Intel ISA PCIC probe: not found. Dec 18 21:52:46 localhost kernel: [ 163.671705] Intel ISA PCIC probe: not found. Dec 18 21:52:46 localhost kernel: [ 163.719473] Intel ISA PCIC probe: not found. Dec 18 21:52:46 localhost kernel: [ 163.769181] Intel ISA PCIC probe: not found. I'll attach lspci + boot log shortly. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- [Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages https://launchpad.net/bugs/76341 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards
That teaches me to speak too soon ;-) 2.6.20 landed. Trying to reproduce there, yields: --- [EMAIL PROTECTED]:~# modprobe i82365 FATAL: Error inserting i82365 (/lib/modules/2.6.20-2-generic/kernel/drivers/pcmcia/i82365.ko): No such device --- As it should. Consider this bug swatted. -- [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards
Ben, The new kernel did NOT fix this bug. Running package version 2.6.19-7.11, tested it as follows: modprobe i82365 BUG: soft lockup detected on CPU#0! *hang* -- [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74146] Re: nvidia 1.0.9629 crashes X
Note that I am using a DFP device, as describe in that nv forum comment. -- nvidia 1.0.9629 crashes X https://launchpad.net/bugs/74146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74146] Re: nvidia 1.0.9629 crashes X
I appear to be having similar problems. I turned on the 'desktop-effects' stuff yesterday and it turns my machine into a brick after I login. I get some interesting 'Xid' messages in syslog (attached). I already had problems with the screensaver kicking in and hanging the machine, and of late it appears usplash and these drivers have begun a catfight about resolutions, as usplash suddenly turns to blueish (kubuntu) snow halfway during boot. More worrying is that these crashes appear to be causing filesystem corruption. At first it was not clear to me what was happening but after such a crash I had some really odd behaviour that cleared up after running an fsck. (which found errors, I might add). ** Attachment added: "xid messages from syslog" http://librarian.launchpad.net/5388256/nvidia_syslog_xid_messages.log -- nvidia 1.0.9629 crashes X https://launchpad.net/bugs/74146 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73966] Re: [Feisty] update-grub fails mysteriously on feisty
Bug disappears if I remove linux-image-kdump. (!) -- [Feisty] update-grub fails mysteriously on feisty https://launchpad.net/bugs/73966 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73966] Re: Postinst script fails running update-grub
After some research I managed to get some output which should clarify matters: [EMAIL PROTECTED]:~# sh -x `which update-grub` 2> update-grub.txt ** Attachment added: "update-grub.txt" http://librarian.launchpad.net/5248147/update-grub.txt ** Summary changed: - Postinst script fails running update-grub + [Feisty] update-grub fails mysteriously on feisty -- [Feisty] update-grub fails mysteriously on feisty https://launchpad.net/bugs/73966 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards
Allcolor_g, can you try running a vanilla 2.6.19 kernel and then issuing the modprobe by hand? I wonder if this affects upstream. On paper all that is needed to trigger the bug would be: modprobe pcmcia_core modprobe i82365 -- [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards
** Summary changed: - [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! + [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards -- [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft lockup detected on CPU#0!" on Asus motherboards https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73177] Re: linux-image-2.6.19-6 fails to find disks
Ok, 2.6.19-7 boots for me* so I consider this one resolved. Please close this bug :-) *) (with a workaround for https://bugs.launchpad.net/distros/ubuntu/+source/linux- source-2.6.19/+bug/72895) -- linux-image-2.6.19-6 fails to find disks https://launchpad.net/bugs/73177 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
I can now confirm that running '/etc/init.d/pcmciautils start' as root after bootup hangs the kernel. That script sources /etc/default/pcmciautils which lists what hardware it thinks I have: -- [EMAIL PROTECTED]:~# cat /etc/default/pcmciautils # Defaults for PCMCIA (sourced by /etc/init.d/pcmcia) PCMCIA=yes PCIC=i82365 PCIC_OPTS= CORE_OPTS= CARDMGR_OPTS= # If REFRAIN_FROM_IFUP is set to yes, cardmgr will not bring up # network interfaces. They should be brought up by hotplug instead. REFRAIN_FROM_IFUP=yes - Presumably removing the S13pcmciautils link is overkill, just setting PCMCIA to 'no' would be enough to stop that module from loading. I wonder why it is set to this in the first place, I surely don't have any PCMCIA hardware .. All that having been said though, I think it has been shown abundantly now that loading the i82365 module causes the lockup. -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
Removed S13pcmciautils, and now it boots! You were dead right on that one. It also seems to me that the bug here is definitely in either that i82365 PCMCIA bridge driver module, or in the code that attempts to find PCMCIA devices. My guess is the latter. One of the things I noticed was that this system doesn't even *have* an i82365 pci device when I look at the lspci output. No surprise there when I apply hindsight.. Here's what the S13pcmciautils script does (and note the kernel never reaches the end of this script): --- log_daemon_msg "Loading PCMCIA bridge driver module" "$PCIC" if [ "$CORE_OPTS" ]; then modprobe -Qb pcmcia_core $CORE_OPTS fi modprobe -Qb $PCIC $PCIC_OPTS log_end_msg $? -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
S13 is pcmciautils alright, but S40 is S40networking. It doesn't sound like a good idea to remove that to me. But I'll try this. -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
No such luck for me. Still getting the lockup on 2.6.19-7. -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73966] Re: Postinst script fails running update-grub
** Attachment added: "menu.lst" http://librarian.launchpad.net/5218052/menu.lst -- Postinst script fails running update-grub https://launchpad.net/bugs/73966 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73966] Re: Postinst script fails running update-grub
menu.lst after running update-grub Definitely no update of any kind .. -- Postinst script fails running update-grub https://launchpad.net/bugs/73966 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73966] Postinst script fails running update-grub
Public bug reported: Binary package hint: grub The 2.6.19-7 kernel package fails to run update-grub properly. Or perhaps update-grub fails because somebody broke it ;-). Both were updated to new versions today (grub version: 0.97-19ubuntu1) The error message is this: --- [EMAIL PROTECTED]:/boot# aptitude install linux-image-generic Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Building tag database... Done The following NEW packages will be automatically installed: linux-image-2.6.19-7-generic The following NEW packages will be installed: linux-image-2.6.19-7-generic linux-image-generic 0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/23.0MB of archives. After unpacking 68.2MB will be used. Do you want to continue? [Y/n/?] Y Writing extended state information... Done Preconfiguring packages ... Selecting previously deselected package linux-image-2.6.19-7-generic. (Reading database ... 167548 files and directories currently installed.) Unpacking linux-image-2.6.19-7-generic (from .../linux-image-2.6.19-7-generic_2.6.19-7.10_i386.deb) ... Done. Selecting previously deselected package linux-image-generic. Unpacking linux-image-generic (from .../linux-image-generic_2.6.19.2_i386.deb) ... Setting up linux-image-2.6.19-7-generic (2.6.19-7.10) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.19-7-generic Running postinst hook /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.19-7-generic User hook script /usr/sbin/update-grub failed at /var/lib/dpkg/info/linux-image-2.6.19-7-generic.postinst line 1201. Running the /usr/sbin/update-grub script by hand gives me as output: --- [EMAIL PROTECTED]:/boot# /usr/sbin/update-grub Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.19-7-generic [EMAIL PROTECTED]:/boot# --- The disturbing thing is that I have a number of kernels but only the new one is listed. If I reboot the new kernel does NOT show up in the grub menu; Instead it shows all the old boot options, suggesting update-grub did not actually update grub. ** Affects: grub (Ubuntu) Importance: Undecided Status: Unconfirmed -- Postinst script fails running update-grub https://launchpad.net/bugs/73966 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
** Attachment added: "lspci output" http://librarian.launchpad.net/5198097/lspci -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73177] Re: linux-image-2.6.19-6 fails to find disks
Added a stack trace for the soft lockup problem to https://bugs.launchpad.net/distros/ubuntu/+source/linux-source-2.6.19/+bug/72895 As for this bug, from looking at the kernel output it appears this bug is fixed (looks like we manage to get through USB initialisation now), though the suspicious ATA message remains in the kernel output. (for reference: "ATA: abnormal status 0x8 on port 0x177") -- linux-image-2.6.19-6 fails to find disks https://launchpad.net/bugs/73177 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
Correction, I spotted a typo in there ;-) === BUG: soft lockup detected on CPU#0! [] dump_trace+0x192/0x1c0 [] show_trace_log_lvl+0x18/0x30 [] show_trace+0xf/0x20 [] dump_stack+0x15/0x20 [] softlockup_tick+0x9b/0xe0 [] update_process_times+0x31/0x80 [] smp_apic_timer_interrupt+0x8e/0xb0 [] apic_timer_interrupt+0x1f/0x30 [] _spin_lock_irqsave+0x11/0x30 [] __down+0x46/0xf3 [] __down_failed+0x7/0x10 [] device_attach+0x2c/0x80 [] bus_attach_device+0x26/0x60 [] device_add+0x37d/0x4d0 [] platform_device_add+0xf7/0x150 [] init_i82365+0x2f/0x47c [i82365] [] sys_init_module+0x15b/0x1c70 [] sysenter_past_esp+0x56/0x79 [] 0xb7f2c410 === -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
Alright, here comes a stack trace: This trace appears right after it attempts to load the i82365 module. (some kind of pcmcia bridge device, I gather.) Be aware this was typed in by hand from a blurry photo, zeroes might be 8's and vice-versa especially near the bottom. === BUG: soft lockup detected on CPU#0! [] dump_trace+0x192/0x1c0 [] show_trace_log_lvl+0x18/0x30 [] show_trace+0xf/0x20 [] dump_stack+0x15/0x20 [] softlockup_tick+0x9b/0xe0 [] update_process_times+0x31/0x80 [] smp_apic_timer_interrupt+0x8e/0xb0 [] apic_timer_interrupt+0x1f/0x30 [] _spin_lock_irqsave+0x11/0x30 [] __down+0x46/0xf3 [] __down_failed+0x7/0x10 [] device_attach+0x2c/0x80 [] bus_attach_device+0x26/0x60 [] device_add+0x37d/0x4d0 [] platform_device_add+0xf7/0x150 [] init_i82365+0x2f/0x47c [i82365] [] sys_init_module+0x15b/0x1c70 [] sysenter_past_esp+0x56/0x79 [] 0xb7f2c410 === -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
To continue this barrage of comments, I removed the nvidia binary driver package before I made that trace as well - to no effect, obviously. -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
Ok, pci=noacpi and acpi=off don't fix the issue. Instead, 'acpi=off' turns the soft lockup into a full-blown kernel panic. Removing the nvidia stuff now. Not expecting much of it since the 'tainted' flag wasn't set during that kernel panic, suggesting that it hadn't loaded yet. Nonetheless .. -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72895] Re: [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
I can confirm this one. Same thing happening on my box. Hardware: AMD Sempron Processor 3400+ Asus mobo K8VXSE NVidia GeForce FX 5200 1Gb ram No LVM No TV card. In all, pretty similar to the original reporter's hardware. More importantly the lockup appears to occur directly after the kernel loads the (binary) NVidia driver. (ugh ..) Tried booting with noapic and pci=routeirq, neither helps. I still have to try pci=noacpi and acpi=off, if those don't help I'll remove the restricted-modules package to see if it makes a difference. Unfortunately I can't seem to get to the stage where disks are mounted, otherwise I'd be able to post a stacktrace. -- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0! https://launchpad.net/bugs/72895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 73177] Re: linux-image-2.6.19-6 fails to find disks
On 11/27/06, Ben Collins <[EMAIL PROTECTED]> wrote: > This has been fixed with an initramfs-tools update. > > ** Changed in: linux-source-2.6.19 (Ubuntu) >Status: Unconfirmed => Fix Released > Ok, the update landed this morning. The good news is, I no longer see the problem occurring where the kernel fails to find it's filesystems on the SATA drive. The bad news; Now I get: BUG: soft lockup detected on CPU#0! However, still no access to the log files due to filesystems not actually being mounted before this issue occurs. I'll follow the instructions on https://help.ubuntu.com/community/DebuggingIRQProblems to see if they make that problem go away. Regards, Floris Kraak -- "Rarely do we find men who willingly engage in hard, solid thinking. There is an almost universal quest for easy answers and half-baked solutions. Nothing pains some people more than having to think." - Martin Luther King -- linux-image-2.6.19-6 fails to find disks https://launchpad.net/bugs/73177 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 73177] Re: linux-image-2.6.19-6 fails to find disks
On 11/27/06, Ben Collins <[EMAIL PROTECTED]> wrote: > This has been fixed with an initramfs-tools update. > > ** Changed in: linux-source-2.6.19 (Ubuntu) >Status: Unconfirmed => Fix Released > When does this update land? As an aside, there is a usability issue here also - the splash screen gets in the way of useful error reporting once the system hits this bug. In a regular boot it appears as if the system just hung itself, while that is far from the truth .. At any rate, thanks for looking into this issue! Regards, Floris -- "Rarely do we find men who willingly engage in hard, solid thinking. There is an almost universal quest for easy answers and half-baked solutions. Nothing pains some people more than having to think." - Martin Luther King -- linux-image-2.6.19-6 fails to find disks https://launchpad.net/bugs/73177 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73177] linux-image-2.6.19-6 fails to find disks
Public bug reported: Binary package hint: linux-source-2.6.19 Upgraded to Feisty today. Upgraded my kernel to 2.6.19-6 in the process. Unfortunately that kernel version appears to not find any disks. While booting in recovery mode everything goes fine up until where it detects my USB hardware (logitech keyboard and mouse). There the log halts and I get disk activity for a long time, until it gives up with a scary error message: (apologies beforehand for any inaccuracies, I'm doing this from heart as the logging never hits the disk) "Alert! Cannot find disk /dev/disk/by-uuid/! Dropping back into a shell!" Poking around in /dev at that stage, it seems /dev/disk is missing entirely. This bug does not affect 2.6.17-10, the kernel version in Edgy. That one boots fine (running it right now in fact). Looking further, I see one message in the 2.6.19 log that does not appear in 2.6.17, which looks decidedly odd (and related) to me: "ATA: abnormal status 0x8 on port 0x177" I'm appending the boot log for 2.6.17-10 as it appears none of the 2.6.19 boot logs have actually landed on disk. I will put a marker in the log pointing at where 2.6.19 stops booting for me. Nov 24 20:54:37 localhost syslogd 1.4.1#18ubuntu6: restart. Nov 24 20:54:37 localhost kernel: Inspecting /boot/System.map-2.6.17-10-generic Nov 24 20:54:37 localhost kernel: Loaded 22825 symbols from /boot/System.map-2.6.17-10-generic. Nov 24 20:54:37 localhost kernel: Symbols match kernel version 2.6.17. Nov 24 20:54:37 localhost kernel: No module symbols loaded - kernel modules not enabled. Nov 24 20:54:37 localhost kernel: [17179569.184000] Linux version 2.6.17-10-generic ([EMAIL PROTECTED]) (gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Fri Oct 13 18:45:35 UTC 2006 (Ubuntu 2.6.17-10.33-generic) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-provided physical RAM map: Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: - 0009fc00 (usable) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: 0009fc00 - 000a (reserved) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: 000e4000 - 0010 (reserved) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: 0010 - 3ffb (usable) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: 3ffb - 3ffc (ACPI data) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: 3ffc - 3fff (ACPI NVS) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: 3fff - 4000 (reserved) Nov 24 20:54:37 localhost kernel: [17179569.184000] BIOS-e820: ff78 - 0001 (reserved) Nov 24 20:54:37 localhost kernel: [17179569.184000] 127MB HIGHMEM available. Nov 24 20:54:37 localhost kernel: [17179569.184000] 896MB LOWMEM available. Nov 24 20:54:37 localhost kernel: [17179569.184000] found SMP MP-table at 000ff780 Nov 24 20:54:37 localhost kernel: [17179569.184000] DMI 2.3 present. Nov 24 20:54:37 localhost kernel: [17179569.184000] ACPI: PM-Timer IO Port: 0x808 Nov 24 20:54:37 localhost kernel: [17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Nov 24 20:54:37 localhost kernel: [17179569.184000] Processor #0 15:12 APIC version 16 Nov 24 20:54:37 localhost kernel: [17179569.184000] ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) Nov 24 20:54:37 localhost kernel: [17179569.184000] IOAPIC[0]: apic_id 1, version 3, address 0xfec0, GSI 0-23 Nov 24 20:54:37 localhost kernel: [17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Nov 24 20:54:37 localhost kernel: [17179569.184000] Enabling APIC mode: Flat. Using 1 I/O APICs Nov 24 20:54:37 localhost kernel: [17179569.184000] Using ACPI (MADT) for SMP configuration information Nov 24 20:54:37 localhost kernel: [17179569.184000] Allocating PCI resources starting at 5000 (gap: 4000:bf78) Nov 24 20:54:37 localhost kernel: [17179569.184000] Built 1 zonelists Nov 24 20:54:37 localhost kernel: [17179569.184000] Kernel command line: root=UUID=c7d17e34-b19e-4c01-bfb5-a56a4a0ba4de ro single Nov 24 20:54:37 localhost kernel: [17179569.184000] Enabling fast FPU save and restore... done. Nov 24 20:54:37 localhost kernel: [17179569.184000] Enabling unmasked SIMD FPU exception support... done. Nov 24 20:54:37 localhost kernel: [17179569.184000] Initializing CPU#0 Nov 24 20:54:37 localhost kernel: [17179569.184000] PID hash table entries: 4096 (order: 12, 16384 bytes) Nov 24 20:54:37 localhost kernel: [17179569.184000] Detected 2002.804 MHz processor. Nov 24 20:54:37 localhost kernel: [17179569.184000] Using pmtmr for high-res timesource Nov 24 20:54:37 localhost kernel: [17179569.184000] Console: colour VGA+ 80x25 Nov 24 20:54:37 localhost kernel: [17179570.936000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[Bug 59810] Re: crash on exit
Same problem here. Using binary nvidia drivers. -- crash on exit https://launchpad.net/bugs/59810 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57951] Re: xchat crashes frequently on quit
Another crash output report.. -- xchat crashes frequently on quit https://launchpad.net/bugs/57951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57875] Re: Azureus does not start
+1 All the same symptoms. -- Azureus does not start https://launchpad.net/bugs/57875 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
