Bug 10552
Summary: | ACPI Error (psargs-0355): [\_SB_.PCI0.LPC0.SIO_.COMA] Namespace | ||
---|---|---|---|
Product: | ACPI | Reporter: | lofagove (wuzhao.chen) |
Component: | Other | Assignee: | Zhang Rui (rui.zhang) |
Status: | REJECTED INVALID | ||
Severity: | normal | CC: | acpi-bugzilla |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.21 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
lspci -vxxx output
acpidump output file |
Description
lofagove
2008-04-25 02:08:01 UTC
Please attach the output of acpidump, lspci -vxxx. Thanks. Created attachment 15906 [details]
lspci -vxxx output
Created attachment 15907 [details]
acpidump output file
Hi, lofagove, The dmesg output of a more recent kernel would bring more valuable infor for us to debug. As you've already tried 2.6.25, would you please attach the dmesg please? Hi, Iofagove Thanks for the info. It seems that the error message is related with the following error in BIOS. > External (\_SB_.PCI0.LPC0.SIO_.COMA) (COMA can't be found in other SSDT tables). So OS reports the error message But it is very strange that OS raises the following message, and do not stop untill disconnected. It seems that the GPE 0x08 method can't be disabled. We will try to investigate the reason. Will you please confirm whether the windows can work well on this laptop? Thanks. Hi,all Sorry for replying you so late. Thank you for your help. Some other problems had occured when tring 2.6.25, so I can not get the messages about dmesg output. for this error message,I had tried some other serial lines,some can work well, some can't. It sounds too strange,so I do not sure if it is linux ACPI's bug. For some reasons I haven't try windows OS ,do not confirm if it can work well.I'm communicating with the hardware supporter, hoping than he can give some detail informations. now i have no idea about this,any other methods to try? Thanks. 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. |