Bug 177585
|
Description
Jeff Kuehn
2006-01-11 22:10:47 UTC
Created attachment 123082 [details]
example of successful single processor boot
Created attachment 123083 [details]
example of successful SMP boot
Created attachment 123084 [details]
2.6.14-1.1637_FC4 panic example
Created attachment 123085 [details]
2.6.14-1.1644_FC4 panic example
Created attachment 123086 [details]
2.6.14-1.1653_FC4 panic example
Created attachment 123087 [details]
2.6.14-1.1656_FC4 panic example
Created attachment 123088 [details]
2.6.14-1.1637_FC4smp panic example 1
Created attachment 123089 [details]
2.6.14-1.1637_FC4smp panic example 2
Created attachment 123090 [details]
2.6.14-1.1644_FC4smp panic example 1
Created attachment 123091 [details]
2.6.14-1.1644_FC4smp panic example 2
Created attachment 123092 [details]
2.6.14-1.1653_FC4smp panic example 1
Created attachment 123093 [details]
2.6.14-1.1653_FC4smp panic example 2
Created attachment 123094 [details]
2.6.14-1.1656_FC4smp panic example 1
Created attachment 123095 [details]
2.6.14-1.1656_FC4smp panic example 2
does the 2.6.15 based test kernel in updates-testing work ? Several attempts to boot the 2.6.15 kernel from updates-testing resulted in the
following scoreboard:
2.6.15 single processor kernel:
2 panics before reaching login prompt
2.6.15 SMP kernel:
8 panics before reaching login prompt
3 boot attempts made it all the way to a login prompt
(one of these was left standing to check stability overnight)
Serial console captured all 13 boot attempts. Console logs will be added to the
attachment list as a tarball of 2.6.15 logs.
Created attachment 123140 [details]
2.6.15 boot logs for 13 attempts (10 panics, 3 survive to login prompt) (UP and SMP)
Created attachment 123141 [details]
2.6.15 boot logs for 13 attempts (10 panics, 3 survive to login prompt) (UP and SMP)
This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) 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_REPORTER 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. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. Installed and tested 2.6.15-1.1830_FC4 on SMP Opteron box. This kernel still crashes as demonstrated in the previous traces. Of the kernels installed on this system: vmlinuz-2.6.11-1.1369_FC4 vmlinuz-2.6.11-1.1369_FC4smp vmlinuz-2.6.13-1.1526_FC4 vmlinuz-2.6.13-1.1526_FC4smp vmlinuz-2.6.13-1.1532_FC4 vmlinuz-2.6.13-1.1532_FC4smp vmlinuz-2.6.14-1.1637_FC4 vmlinuz-2.6.14-1.1637_FC4smp vmlinuz-2.6.14-1.1644_FC4 vmlinuz-2.6.14-1.1644_FC4smp vmlinuz-2.6.14-1.1653_FC4 vmlinuz-2.6.14-1.1653_FC4smp vmlinuz-2.6.14-1.1656_FC4 vmlinuz-2.6.14-1.1656_FC4smp vmlinuz-2.6.15-1.1823_FC4 vmlinuz-2.6.15-1.1823_FC4smp vmlinuz-2.6.15-1.1824_FC4 vmlinuz-2.6.15-1.1824_FC4smp vmlinuz-2.6.15-1.1830_FC4 vmlinuz-2.6.15-1.1830_FC4smp the most recent working kernel still appears to be 2.6.13-1.1532_FC4smp. [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. 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. This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you. |