Bug 172376

I'm seeing the same behavior with FC4, kernel 2.6.13-1.1532_FC4smp. I also see
it with kernel 2.6.14-1.1633_FC4smp.

My machines are also from HP, though they're xw8200 workstations with dual Xeon
EM64T chips.

Also, I just determined that booting with 'acpi=off' makes it work. I also tried
'acpi=noirq', 'pci=noacpi', and 'pnpacpi=off' and none of them helped.

does the 2.6.14 update from updates-testing fix this ?

2.6.14-1633 doesn't fix it for me. I'll try to get any relevant output from the
serial console.

Created attachment 120785 [details]
dmesg boot output from 2.6.14-1633 with APIC enabled

The machine freezes immediately after printing this dmesg output.

Created attachment 120786 [details]
dmesg boot output from 2.6.14-1633 with APIC disabled

The system boots normally after printing this dmesg output (which I truncated).
I did notice that it complains about a weird NMI, but the system seems fine.

That's "ACPI" disabled :-)  (Which confused me at first).

Oops--right you are. Sorry about that! :)

Just a quick update--the released 2.6.14-1.1637_FC4.src.rpm still exhibits the
same problem.

thanks,
lars

2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.

Looks like I beat you to it! ;)

2.6.14-1.1644_FC4 fixed this problem for me. Thanks!
-lars

Hmm. I was a bit premature posting that things are fixed; I'd left the acpi=off
option in the boot arguments while testing. Sadly two out of my three testing
HPs are still freezing in the same way as before. I'm inspecting the kernel's
boot output to see if I can find why one of them works and the others don't.

sorry,
lars

Hi folks,

I'm sad to report that this issue still happens on some of our HP workstations
with Fedora Core 5 test 2. I haven't been able to find any obvious differences
between workstations that freeze and ones that don't.

Can anybody give me a hint as to what the kernel is doing immediately after
printing the output at the end of the dmesg log I attached earlier
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=172376)?

We haven't been able to update the kernels on our FC4 machines since October
because of this problem.

Thanks,
lars

Does "acpi=off" always make this hang go away?
If yes, please try just "pnpacpi=off"

Hi,

acpi=off does seem to make the hang disappear, but pnpacpi=off doesn't help; the
machine still freezes.

Thanks,
lars

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.

The freeze still occurs with kernel 2.6.15-1.1830_FC4.

thanks,
lars

[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 is a mass-close to kernel bugs in NEEDINFO state)

As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.

If you believe that this bug was closed in error, please feel free to reopen
this bug.