Re: Interrupt storm
From: Andre Guibert de Bruet (andy_at_siliconlandmark.com)
Date: 03/30/05
- Previous message: Randy Bush: "Re: HEADSUP: ATA mkIII has been committed"
- In reply to: Dan Cojocar: "Re: Interrupt storm"
- Next in thread: Dan Cojocar: "Re: Interrupt storm"
- Reply: Dan Cojocar: "Re: Interrupt storm"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 30 Mar 2005 10:53:48 -0500 (EST) To: Dan Cojocar <dan.cojocar@gmail.com>
On Wed, 30 Mar 2005, Dan Cojocar wrote:
> On Tue, 29 Mar 2005 15:46:52 -0500 (EST), Andre Guibert de Bruet wrote:
>>
>> Have you tried booting this machine using GENERIC with ACPI turned off?
>
> I tried running GENERIC and i get the following lor and watchdog
> timeout, no interrupt storms:
--- 8< --- <snip> --- 8< ---
> Here is the full dmesg: http://cs.ubbcluj.ro/~dan/dmesg.txt.generic
> I tried also my kernel with apic, i don't get interrupt storms but
> i get watchdog timeout message just like with GENERIC.
> Here is the full dmesg: http://cs.ubbcluj.ro/~dan/dmesg.txt.apic
> And finally i tried my kernel without apic and without acpi, it's
> running just fine, no interrupt storms, no watchdog timeout, but i
> don't have acpi :(, here is the final
> dmesg: http://cs.ubbcluj.ro/~dan/dmesg.txt.noacpi.
It looks like your motherboard's DSDT is doing something hokey. I would
complain to the board manufacturer about this. For the timebeing, you can
dump the DSDT into ASL format, modify it, compile it back to DSDT and load
a proper version on system startup. If this is your first time, you
probably want to run "acpidump -d > my.asl" and make the resulting file
available somewhere.
Would you also mind sharing the kernel config file that was used to build
the kernel that gaves you the mother of all interrupt parties?
Cheers,
Andy
| Andre Guibert de Bruet | Enterprise Software Consultant >
| Silicon Landmark, LLC. | http://siliconlandmark.com/ >
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Randy Bush: "Re: HEADSUP: ATA mkIII has been committed"
- In reply to: Dan Cojocar: "Re: Interrupt storm"
- Next in thread: Dan Cojocar: "Re: Interrupt storm"
- Reply: Dan Cojocar: "Re: Interrupt storm"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: [>=2.6.23][BUG] Oops on power disconnection
... I thought it was a acpi (dsdt) problem. ... If you get different backtraces
on reboots even you only modified things ... You might want to try the latest kernel
or the patch posted there. ... Looks like a cpuidle problem (or at least acpi).
... (Linux-Kernel) - Documentation - How to debug ACPI Problems
... I made up a little How-To for what I find out is nice to debug ACPI ... There
are ACPI tables (DSDT and SSDTs), ... The kernel makes use of provided BIOS functions
... (Linux-Kernel) - Re: [>=2.6.23][BUG] Oops on power disconnection
... I thought it was a acpi (dsdt) problem. ... > (switching to battery).
... > in particular is of kernel 2.6.24.3. ... Looks like a cpuidle problem (or
at least acpi). ... (Linux-Kernel) - ACPI -- Workaround for broken DSDT
... Please note that a recompiled and fixed DSDT table exists for the Compaq Presario ...
compile time from a configuration menu, and compile it in to the kernel. ... This
may be useful in the future for broken ACPI. ... (Linux-Kernel) - Re: Interrupt storm
... >> i get watchdog timeout message just like with GENERIC. ... >>
And finally i tried my kernel without apic and without acpi, ... >> running just
fine, no interrupt storms, no watchdog timeout, but i ... > It looks like your motherboard's
DSDT is doing something hokey. ... (freebsd-current)