Bug 11350 (p2540) - Freezes on fujitsu amilo p2540
Summary: Freezes on fujitsu amilo p2540
Status: REJECTED INSUFFICIENT_DATA
Alias: p2540
Product: ACPI
Classification: Unclassified
Component: Config-Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-16 01:27 UTC by Rondeau Matthieu
Modified: 2008-11-25 06:47 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.25.14-108.fc9.x86_64
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Rondeau Matthieu 2008-08-16 01:27:35 UTC
Latest working kernel version:2.6.25.14-108.fc9.x86_64

Earliest failing kernel version:2.6.25.14-108.fc9.x86_64

Distribution: Fedora 9 (Tried Debian 4.0 etch, same problem)

Hardware Environment: 
-Processor : Intel Pentium Dual core T2370
             Chipset Intel965PM+ICH8-M
-Memory : 2Go DDR2 667

Software Environment: Fedora 9, repo softwares

Problem Description:
The computer keeps on freezing.
I had a message which said :
Kernel message : You have a hardware problem, most likely on PCI bus
Kernel message : Dazed and Confused, but trying to continue

I put the options : apic=off noapic apm=power-off at the kernel boot, and it worked just fine.

Steps to reproduce: Just install any distro on the computer, then don't put the option on the boot.
Comment 1 Andrew Morton 2008-08-16 01:42:38 UTC
> Latest working kernel version:2.6.25.14-108.fc9.x86_64
> Earliest failing kernel version:2.6.25.14-108.fc9.x86_64

This doesn't make sense.  Which kernel version was OK?  WHich kernel version was not?

Also, I assume that "apic=off" was supposed to be "acpi=off"

Are all three of those options required to make it boot?  Or just acpi=off?
Comment 2 Rondeau Matthieu 2008-08-16 01:57:51 UTC
I putted this because I only tried on this one for Fedora, for I upgraded my system right after the installation wad over.
Anyway, sorry I made a mistake, of course the option is acpi.
The options are : acpi=off noapic apm=off. Sorry 
Still it is working with acpi=off only.
Comment 3 ykzhao 2008-08-17 07:17:08 UTC
Hi, Rondeau
   Will you please try to boot the system with acpi disabled and attach the output of acpidump, lspci -vxxx?
   Will you please add the boot option of "initcall_debug" and attach the screenshot when the system freezes?
   Thanks.
   
   
Comment 4 Rondeau Matthieu 2008-08-17 07:23:33 UTC
Sure.*
Right now I am not able to do so for I am on holidays, but as soon as I get to the computer, I will post what you asked.
Comment 5 Zhang Rui 2008-08-17 18:39:07 UTC
(In reply to comment #0)
> Problem Description:
> The computer keeps on freezing.
Does this happen on or after booting time?
Do you mean it freezes for a few seconds and then work again?

> I had a message which said :
> Kernel message : You have a hardware problem, most likely on PCI bus
> Kernel message : Dazed and Confused, but trying to continue
when did you get this message? during boot time?
Please attach the full dmesg output with this message in. :)
Comment 6 Zhang Rui 2008-09-09 19:13:24 UTC
Rondeau, any updates?
Comment 7 ykzhao 2008-09-17 20:03:06 UTC
Hi, Rondeau
    Will you please add the following boot option on the latest kernel(2.6.27-rc6) and see whether the system still hangs?
    a. idle=poll
    b. nolapic_timer
    c. processor.max_cstate=1( Had better compile it as built-in kernel module)
   thanks.
Comment 8 Zhang Rui 2008-09-22 01:00:51 UTC
Rondeau, how was you holiday? :)
any update?
Comment 9 Rondeau Matthieu 2008-09-23 15:13:46 UTC
I have tried another kernel in the mean time, and it worked (I recompiled it)
I shall give you the exact description of the kernel the moment I find time to sit down in front of my laptop
Comment 10 Zhang Rui 2008-10-30 02:00:23 UTC
any update, Rondeau?
seems that it's already fixed in the latest kernel release, right?
Comment 11 Zhang Rui 2008-11-24 22:43:28 UTC
fixed in the latest kernel release?
no response from the bug reporter.

Rondeau,
please re-open it if the problem still exists.
Comment 12 Rondeau Matthieu 2008-11-25 06:47:48 UTC
Sorry for not responding.
Yes it was fixed with the lastest release, now it works fine

Note You need to log in before you can comment on or make changes to this bug.