http://bugzilla.kernel.org/show_bug.cgi?id=11348





------- Comment #6 from [EMAIL PROTECTED]  2008-08-22 13:48 -------
It's rather impossible (because of the "throttling" of io, as I wrote already).
I tried to, anyway - but pay attention, that in fact it has been done really
AFTER the problem has been observed, not during - and below is the result of
cat /proc/interrupts :

           CPU0       
  0:      27516    XT-PIC-XT        timer
  1:        287    XT-PIC-XT        i8042
  2:          0    XT-PIC-XT        cascade
  3:          3    XT-PIC-XT        ohci1394
  4:          1    XT-PIC-XT      
  6:          5    XT-PIC-XT        floppy
  9:          0    XT-PIC-XT        acpi
 10:      17598    XT-PIC-XT        sata_sil
 11:        728    XT-PIC-XT        uhci_hcd:usb1, eth0
 12:       8723    XT-PIC-XT        i8042
 14:       1204    XT-PIC-XT        ata_piix
 15:       7358    XT-PIC-XT        ata_piix, bttv0, EMU10K1,
[EMAIL PROTECTED]:0000:01:00.0
NMI:          0   Non-maskable interrupts
LOC:          0   Local timer interrupts
TRM:          0   Thermal event interrupts
SPU:          0   Spurious interrupts
ERR:          0
MIS:          0

...and here's output of grep . /sys/firmware/acpi/interrupts/* :

/sys/firmware/acpi/interrupts/error:0
/sys/firmware/acpi/interrupts/ff_gbl_lock:0
/sys/firmware/acpi/interrupts/ff_pmtimer:0
/sys/firmware/acpi/interrupts/ff_pwr_btn:0
/sys/firmware/acpi/interrupts/ff_rt_clk:0
/sys/firmware/acpi/interrupts/ff_slp_btn:0
/sys/firmware/acpi/interrupts/gpe00:0
/sys/firmware/acpi/interrupts/gpe01:0
/sys/firmware/acpi/interrupts/gpe02:0
/sys/firmware/acpi/interrupts/gpe03:0
/sys/firmware/acpi/interrupts/gpe04:0
/sys/firmware/acpi/interrupts/gpe05:0
/sys/firmware/acpi/interrupts/gpe06:0
/sys/firmware/acpi/interrupts/gpe07:0
/sys/firmware/acpi/interrupts/gpe08:0
/sys/firmware/acpi/interrupts/gpe09:0
/sys/firmware/acpi/interrupts/gpe0A:0
/sys/firmware/acpi/interrupts/gpe0B:0
/sys/firmware/acpi/interrupts/gpe0C:0
/sys/firmware/acpi/interrupts/gpe0D:0
/sys/firmware/acpi/interrupts/gpe0E:0
/sys/firmware/acpi/interrupts/gpe0F:0
/sys/firmware/acpi/interrupts/gpe_all:0
/sys/firmware/acpi/interrupts/sci:0

...but, alas, it's not possible to trace anything using "top" ("frozen" output
for duration of the "throttling").

BTW: Did you mention the comments from the mail at the list, sent at Tue, 19
Aug 2008 13:48:07 +0200 by Dan Vratil <[EMAIL PROTECTED]>, with the
subject "ACPI failure"? He wrote: "Then in one version (i think it was
2.6.25.6, but not sure) ACPI tables were updated to be compatible with Windows
Vista, but it has broken down my ACPI".

I think, he just described the same problem.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to