Bug 9358

Created attachment 13515 [details]
dmesg

Created attachment 13516 [details]
dmidecode

Created attachment 13517 [details]
lspci

I currently have some problems getting the pictures from my camera to my pc (not caused by Linux ;)). Will post them soon.

Will you please try it with boot option of pci=nommconf ?
If the system can be booted successfully, please upload the info of acpidump.
Thanks.

It would be great that the acpidump info is attached.
Thanks.

I am trying to fix the laptop with Jonathan, which means that I sometimes visit him and we do debug procedures ;) Sadly, we had not have time yesterday but we hope that we can try today. Thanks for your help!

Sorry for the delay.

Booting using pci=nommconf does not work. I will attach the regarding photos.

Created attachment 13568 [details]
pci=nommconf (sorry for bad quality)

Created attachment 13569 [details]
pci=nommconf + acpi_osi=Linux

Created attachment 13570 [details]
pci=nommconf  + pci=nodma

Created attachment 13571 [details]
without any boot options

AFAIK, acpidump would only have worked with acpi=on, wouldn't it?

Thanks.
Anyway, Please boot the system with acpi=off noapic and then attach the info of acpidump.

Created attachment 13601 [details]
acpidump

Acpidump attached.

Hi, Jonatha && Martin
the boot option should be "pci=nommconf" (not "pci=mmconf"). Will you please try it again?
Thanks.

It will be greate if you can attach the dmesg using serial-port and pci info (lspci -vvxxx).

How can one create a dmesg using a serial port? ( I even do not know if the laptop has one )

We did use pci=nommconf, but we have described the attachments wrongly. Though, we retried using pci=nommconf and it still did not work.

Created attachment 13626 [details]
lspci -vvxxx output

Thanks for the info.
From the comment #1 there is no MPS table and it means that APIC table doesn't exist in acpi=off . So /proc/cpuinfo only shows one cpu.

Will you please enable the debug of PCI and ACPI in kernel configuration and boot the system with the option of acpi=noirq ?
If the system can be booted, please attach the dmesg.
Thanks.

Lets go fishing:-)

Please report if any of the following cmdline params make it boot:

nohz=off
nolapic
maxcpus=1
hpet=disable
acpi=ht
pci=noacpi

if any boot, please attach the resulting dmesg -s64000 output.

> acpi=off ide=nodma noapic
Also, are all three of these necessary, or does the system boot
when using just acpi=off?

> Also, are all three of these necessary, or does the system boot when using
> just acpi=off?

All three are necessary.

>> are all three of these necessary?
> All three are necessary.

that is odd, on laptops, "noapic" is usually redundant with "acpi=off"
because the IOAPIC support is generally in ACPI and not available in MPS.

ie. I would expect the following to give the same results:
acpi=off ide=nodma noapic
acpi=off ide_nodma

Let's see, maybe we have mixed up something. We will meet this evening and try the boot options that you and Yakui have written down.

Created attachment 13677 [details]
dmesg of acpi=ht irqpoll ide=nodma

We had some success using acpi=ht irqpoll ide=nodma. The system booted fine after some delays.

When using the "acpi=ht irqpoll ide=nodma", then the system freezes when using the touchpad. USB devices (e.g. mouse) do not work.

When you need pictures of the other boot options, then please pleave a note.

> Intel MultiProcessor Specification v1.4
>    Virtual Wire compatibility mode.

okay, that explains why "noapic" makes a difference even when "acpi=off".

however, if 
acpi=ht irqpoll ide=nodma

booted, then so should acpi=off irqpoll ide=nodma
except you'll have just 1 processor instead of two.

if you boot with the additional parameter "debug" on the cmdline,
do you see anything more on the screen upon the boot hang?

please attach the failing .config

Created attachment 13680 [details]
kernel .config

it's just the plain fedora 8 debug kernel, but i have attached the .config, though.

the "hangs" happened after the kernel was booted, so we already saw "welcome to fedora". Then we had some delay and pressed ENTER multiple times. Something failed, then the system went ahead. 

We'll try with debug one of the next days and we will also take some nice photos :) Well numbered, like the first three pictures before (but I doubt that we have some paper from the M-company left) ;)

> we already saw "welcome to fedora"

okay, so we got to init -- but the modules load after that point.

does it get that far even w/o any kernel boot parameters?

If you boot the fedora CDROM into "Memory test", does it survive overnight?

> does it get that far even w/o any kernel boot parameters?
No, it does not. See attachment 13571 [details] for a screenshot w/o any bootoptions.

We will try "Memory test" and "debug" as soon as we can, but the laptop also goes to RMA soon, which is a little problematic so it can take some time.

Another finding is the following: 

We tried out Backtrack (http://www.remote-exploit.org/backtrack.html) and it worked w/o any boot parameters. It also did not freeze or have a delay at the startup and it showed how long the battery would last. BUT: It also only showed up one CPU.

The normal "main stream" distributions all fail to boot, which is weird. And afaik, the Fedora kernel does not contain any third party patches.

we retried acpi=ht irqpoll ide=nodma with kernel 2.6.23.8 and it did not result in anything. it says something like:

I/O error dev sda
READ capacy failed
hostbyte=DID_BAD_TARGET
select() to /dev/rtc to wait for clock tick timed out

if it helps you to have SSH access, please tell us

re: backtrack works
i don't know what kernel they use, but it might have "acpi=off"
built in, say via CONFIG_ACPI=n.  Can you get the dmesg
off that configuration?

Have you tried anyting older than FC8, say FC7 or earlier?
It is possible that some of the recent timer changes are involved.

re: comment #32
so this worked before (comment #25) but now it doesn't work?
What changed?  Where were the delays reported in comment #25?
(you can enable printk timestamps if you build a kernel
 with CONFIG_PRINTK_TIME=y)

hi again, sorry for the delays, you should expect some more in answering. also note that we do not have the time to rebuild kernels often, but leave a note when you think that it is important in order to fix the bug.

we'd like to wait for 2.6.24 to hit us via updates first, as there seem to be lots of acpi fixed. we just installed 2.6.24-rc8 to just quick and dirty try if there are any improvements, but booting without anything or noapic irqpoll did not work, but it works using acpi=off ide=nodma noapic irqpoll as always. We'll attach dmesg output, but currently can not test anything with that new kernel. We'd like to wait for the official 2.6.24 release. Maybe you can get anything out of this dmesg?

Created attachment 14499 [details]
dmesg with 2.6.24 rcx

Created attachment 15158 [details]
try the custom DSDT

Will you please try the custom DSDT and see whether the system still fails in acpi mode?
How to use custom DSDT can be found in the following website:
http://www.lesswatts.org/projects/acpi/faq.php.
Thanks.

Created attachment 15159 [details]
use the attached tool to dump BIOS PRT/MPS table

Will you please use the attached tool to dump BIOS PRT/MPS table?

Created attachment 15173 [details]
result of pirq

So, I tried it with 2.6.25-0.90.rc3.git5. So far, I noticed that the kernel detects 2 CPUs, which is good:

Brought up 2 CPUs
PCI: Usinconfiguration type 1
Setting up standrd PCI ressources

Then it hangs

When I boot with acpi=off it hangs with the following / or it boots very slow ( I stopped after two minutes ):

Unlink after NO-Irq

Will you please add the boot option of "pci=nommconf" and see whether it still hangs?

It will be great if you can boot the system with the option of "pci=nommconf pci=noacpi" and attach the output of dmesg.

Thanks.

It says the following:

Simple boot flag value 05 read from cmos ram was invalid
Simple boot flag at 0x44 set to 0x1

Correction:

It says the following :

ACPI: DSDT override uses original SSDTs unless .... xxxxx Namespace lookup failure, AE_NOT_FOUND
lockdep fixing up alternatives
CPU 1 irqstacks hard xxxxxxxxxxxx

Second startup

Trying to set up timer as Virtual Wire IRQ APIC error on CPU0: 80 works

Hi, Jonathan
    Will you please try the latest kernel and see whether it still hangs?
    Will you please try the boot option of "pci=noacpi"?
    If the system still hangs, please capture the screen and attach it.
    
    In the comment #43 there exists the following message:
    >xxxxx Namespace lookup failure, AE_NOT_FOUND
    Will you please give the real name of "xxxxx"?
    Thanks.

>     Will you please try the latest kernel and see whether it still hangs?

yum, which means the kernel that ships with the fedora 9 installer.

>     Will you please try the boot option of "pci=noacpi"?

attached, as the one without any options

>    Will you please give the real name of "xxxxx"?

sorry, i do not have that kernel anymore :(

camera not working, i ll provide it later.. sorry

As there is no response from bug reportor for more than one month, the bug will be rejected. If the problem still exists, please reopen it.
Thanks.