http://bugzilla.kernel.org/show_bug.cgi?id=10552
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |REJECTED
Resolution| |INVALID
------- Comment #7 from [EMAIL PROTECTED] 2008-05-05 19:16 -------
As Yakui said in comment #5, the device \_SB_.PCI0.LPC0.SIO_.COMA
really doesn't exist in the Vendor's ACPI BIOS -- so it is correct
that Linux complains when trying to Notify it.
Secondly...
Method (_L08, 0, NotSerialized)
{
Notify (\_SB.PCI0.LPC0.SIO.COMA, 0x02)
}
all the AML does on this GPE is to do that notify -- there is no
code to go and turn off any hardware interrupt source.
So it makes sense that if you get this, you'll get it again
as soon as we return from the interrupt handler.
Finally, the fact that some serial cables work and some do not
suggest that the cable is mis-wired to trigger a one-time
event that this serial port does not expect -- perhaps
flow control?
I suggest that you use the cable that works, and also
explore the BIOS for SETUP options related to the serial port.
I don't see a Linux bug here.
--
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 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
