Bug 179843
Summary: | 2.6.15-1.1830_FC4 and later crash on Acer Aspire 1700 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | J.Jansen <joukj> | ||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | CC: | pfrields, wtogami | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | FC5 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-10-21 02:05:15 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
J.Jansen
2006-02-03 11:36:15 UTC
can you capture that dump somehow ? Even a digital camera picture would be great. (If you can, add 'vga=791' to your boot command line, and you'll also get a smaller font, so I'll be able to read more of the backtrace). Thanks. Created attachment 124317 [details]
machine hangs with tis message when sutting down
see other comment
The problem becomes rather weird: I can boot now, but it crashes in the same (or simmilar?) way when shutting down/rebooting (I attached an image of the screen when it hangs) What changed bewteen friday and now: -I performed a selinux relabeling -I installed newly released updates I just upgraded to kernel2.6.15-1.1831_FC4, but the system still hangs when shutting down/rebooting. looks like the notifier list contained garbage somehow. What modules do you usually have loaded? Nothing of my own. Only the machine "standards" [root@tarantella tmp]# zcat /boot/initrd*1831*img | cpio -idmv . bin bin/hotplug bin/insmod bin/nash bin/udev bin/udevstart bin/modprobe init dev dev/systty dev/null dev/tty4 dev/tty2 dev/ram dev/tty1 dev/tty3 dev/console sys loopfs sbin sysroot lib lib/jbd.ko lib/ext3.ko proc etc etc/udev etc/udev/udev.conf 4449 blocks [root@tarantella etc]# cat modprobe.conf alias eth0 sis900 alias snd-card-0 snd-intel8x0 install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0 alias usb-controller ehci-hcd alias usb-controller1 ohci-hcd I installed 2.6.15-1.1833_FC4 today. The first time boot it hanged just before starting X11. Only after rebooting in an older kernel I could boot into the 1833 kernel, but when shutting down it hangs just when performing the "halt system". Now I Half solve the problem when booting into another kernel, but what will happen when I upgrade in the next weeks to FC5? Do I run into the same problems without the possibility to boot into another kernel? I just got a brainwave and installed the smp kernel (1833) although it is a single P4 laptop. The smp kernel does not show the problem at all. So I have a "work-around" for the moment. [This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you. FC5 gives no problem at all A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. As mentioned in comment #10 I only saw this problem in FC4. all kernels for FC5 I tested, including 2.6.18-1.2200.fc5 give no problem on my system. Jouk |