From: Brown, Len <len.brown@in...> - 2003-11-30 06:26:35
Hmmm, my copy of iasl couldn't parse this DSDT;-(
Can you attach the /proc/interrupts with these dmesg logs and acpidmp to
a bug report?
acpi=3Dforce cases generally aren't the highest priority, but the fact
that it used to work and then broke makes it interesting.
Also, if you get a chance, it would be good to know if 2.6.0 works
differently, and if in 2.4.23 the cmdline "acpi_irq_nobalance" makes any
How to file a bug against ACPI:
Category: Power Management
Please attach the output from dmidecode, available in /usr/sbin/, or
Please attach the output from acpidmp, available in /usr/sbin/, or in
Please attach /proc/interrupts and the dmesg output showing the failure,
> -----Original Message-----
> From: acpi-devel-admin@...=20
> [mailto:acpi-devel-admin@...] On Behalf Of=20
> Chris Rankin
> Sent: Friday, November 28, 2003 10:06 PM
> To: acpi-devel@...
> Subject: [ACPI] [EXTRA] Regression in 2.4.23 w.r.t. 2.4.22 on i840
> Ref: 2.4.23 PCI devices go nuts unless "pci=3Dnoacpi".
> Here's the output from acpidmp for my machine. Come to
> think of it, you'd probably want this.
> Download Yahoo! Messenger now for a chance to win Live At=20
> Knebworth DVDs
Get latest updates about Open Source Projects, Conferences and News.