linux-kernel - Re: pnp changes -> suspend oops [Was: 2.6.26-rc5-mm2]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Jun 2008 23:57:58 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org
Subject: Re: pnp changes -> suspend oops [Was: 2.6.26-rc5-mm2]

On 06/12/2008 11:57 PM, Bjorn Helgaas wrote:
> On Thursday 12 June 2008 03:39:14 pm Jiri Slaby wrote:
>> On 06/12/2008 11:22 PM, Bjorn Helgaas wrote:
>>> On Thursday 12 June 2008 03:10:04 pm Jiri Slaby wrote:
>>>> On 06/11/2008 09:03 PM, Bjorn Helgaas wrote:
>>>>> Before you go to all the trouble of bisecting it, can you turn on
>>>>> CONFIG_PNP_DEBUG and try the following debug patch?  I think this
>>>>> will prevent the oops, but it's just papering over the real problem,
>>>>> so please capture the complete dmesg log.
>>>> ACPI: PCI interrupt for device 0000:00:02.0 disabled
>>>> serial 00:07: disabled
>>>> serial 00:06: disabled
>>>> ACPI handle has no context!
>>>> ACPI: PCI interrupt for device 0000:00:1d.7 disabled
>>>> ...
>>>> serial 00:06:   no dma resource to encode!
>>>> serial 00:06: activated
>>>> serial 00:07:   no dma resource to encode!
>>>> serial 00:07: activated
>>>> ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
>>> Interesting.  I wonder why a serial device would have a DMA resource.
>>> We encode resources by following a template from _CRS, so evidently
>>> that template had a DMA resource.  Or something deeper is wrong.
>>>
>>> Can you send me the rest of that dmesg log?
>> Below.
> 
> Thanks, but it looks like CONFIG_PNP_DEBUG is not turned on.  Can
> you turn that on and capture the log again, please?

Sorry, too tired, so I overlooked it. Tomorrow. Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/