Bug 1691
Summary: | Unplugging AC Adapter causes "Synaptics driver lost sync" | ||
---|---|---|---|
Product: | ACPI | Reporter: | S Clark (epicanis+bugreport) |
Component: | Power-Battery | Assignee: | Luming Yu (luming.yu) |
Status: | REJECTED UNREPRODUCIBLE | ||
Severity: | normal | CC: | acpi-bugzilla, hanno |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.0-test11 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | acpidmp output |
Description
S Clark
2003-12-17 10:19:41 UTC
Created attachment 1691 [details]
acpidmp output
> spurious 8259A interrupt: IRQ7. > ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd > 9: 105954 XT-PIC acpi This isn't a reasonable number of ACPI interrupts -- likely that there is a problem even before the actual event (which added at most 3 interrupts). Please try booting with "acpi_pic_sci=edge" Another thing to always try when running with XP-PIC "nolapic", since it seems that on most machines in this config it does more harm than good... thanks, -Len No luck there, I'm afraid. Though I notice that even with the acpi_pic_sci=edge I STILL get the "was edge triggered, setting to level triggered" kernel message during bootup. And at the risk of adding a complication, I get almost the same behavior when I try to adjust the screen brightness (is that an acpi key event?) The odd thing is that although hitting fn-F6 to reduce the screen brightness instantly kills the touchpad, in this case I DON'T get the 'synaptics driver lost sync' messages. I have no idea if this means it's unrelated, or if it's just a new complication, but there it is... I'm on the 'official' 2.6.0 kernel now, though it didn't look like any of the patches between the two touched much of anything that's relevant. I also see that the -mm patch for -test11 has a whole mess of ps2mouse and synaptics updates, but I unfortunately couldn't get the kernel to compile after I'd applied it to -test11, so I have no idea if those patches resolve anything I'm experiencing. would you please try the latest ACPI patch w/o acpi_pic_sci=edge? *** Bug 843 has been marked as a duplicate of this bug. *** problem still exist in linux-2.6.9? please re-open if this issue can be reproduced with 2.6.10 or later. |