We need to see the entire error message. Can he boot with kernel option "vga=791" and take a picture of the output?

That - and several other vga options - just gave a black screen. I also tried some combinations of nomodeset.

I will go visit him tomorrow and see what is going on.

Is serial console the only option? I doubt his machine has serial port at all.

I will try the latest koji kernel - is there something else that could be relevant to test?

vga=1 should give you a 50-line display.

The other option is to use boot_delay to slow down the message scroll rate.

Created attachment 443095 [details]
boot oops with kernel-PAE-2.6.34.6-52.fc13.i686

With a combination of vga=1 and boot_delay=10 I got it all - even though the quality isn't good.

(It isn't easy to find any documentation about how to use boot_delay.)

*** Bug 630473 has been marked as a duplicate of this bug. ***

*** Bug 632593 has been marked as a duplicate of this bug. ***

It's oopsing here, in acpi_ns_lookup() line 339:

        if (!(flags & ACPI_NS_PREFIX_IS_SCOPE)) {
                /*
                 * This node might not be a actual "scope" node (such as a
                 * Device/Method, etc.)  It could be a Package or other object
                 * node. Backup up the tree to find the containing scope node.
                 */
===>            while (!acpi_ns_opens_scope(prefix_node->type) &&
                       prefix_node->type != ACPI_TYPE_ANY) {
                        prefix_node =
                            acpi_ns_get_parent_node(prefix_node);
                }
        }

prefix_node is NULL

Backtrace:
acpi_ns_get_node
acpi_get_handle
acpi_gts_bfs_check
acpi_sleep_init
acpi_init

This bug also hit me with a Lenove 3000 G530. I could workaround by using the kernel parameter "noacpi".

Same problem is seen with kernel-PAE-2.6.35.6-44.fc14.i686

Could you attach the acpidump output?

Created attachment 454450 [details]
acpidump generated from lenovo u350

please note this problem is reproducible with the latest 2.6.35.7 stable kernel

Created attachment 454526 [details]
acpidump of a Lenovo 3000 also known as G530

This is an acpidump of a Lenovo 3000 also known as G530.
It hits the same problem. The following workarounds could be found:

acpi=off
-or-
acpi_no_auto_ssdt

The problem did not occur with kernel-2.6.34.7-56.fc13.i686.rpm which is the standard kernel on FC13 installations disks. The problem occurren only after "yum update" to the mentioned kernel.

(My above statement, that "noacpi" works is wrong. Only the above worked. Sorry.)

A summary,

Below kernels oops
kernel-PAE-2.6.34.6-47.fc13.i686
kernel-PAE-2.6.34.6-52.fc13.i686
kernel-PAE-2.6.35.6-44.fc14.i686
2.6.35.7 stable

Below kernel works
kernel-2.6.34.7-56.fc13.i686

Would you guys help to test if the latest upstream kernel 2.6.36 works or not?

Thanks.

The rawhide kernel should work on F13 and it's been updated to 2.6.36 now.

I can confirm the issue is solved building a 2.6.36 kernel.

Created attachment 455282 [details]
acpidump from FUJITSU SIEMENS AMILO Li3710

I can confirm that kernel-PAE-2.6.36-1.fc15.i686 works.

I hope we can get a fix in a f13 kernel too.

I can also confirm that kernel-PAE-2.6.36-1.fc15.i686 works for Lenovo 3000 also known as G530.

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.