From: Jiri Slaby <jirislaby@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: pnp changes -> suspend oops [Was: 2.6.26-rc5-mm2]
Date: Wed, 11 Jun 2008 20:08:53 +0200 [thread overview]
Message-ID: <485014B5.7080305@gmail.com> (raw)
In-Reply-To: <20080609223145.5c9a2878.akpm@linux-foundation.org>
On 06/10/2008 07:31 AM, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc5/2.6.26-rc5-mm2/
Hi,
I face problems after some of the pnp changes. If this is not known, I may
bisect it, it's 100% reproducible. I have no real logs, It panics prior to
network is woken up to see something on netconsole, I just captured a function
name and an offset of place where it oopses.
pnpacpi_encode_resources, ACPI_RESOURCE_TYPE_DMA case, pnp_get_resource(dev,
IORESOURCE_DMA, dma) returns NULL, which is dereferenced at pnpacpi_encode_dma
at p->flags.
It happens on resume after mem > /sys/power/state.
next prev parent reply other threads:[~2008-06-11 18:10 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 5:31 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 6:12 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10 7:28 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10 8:34 ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 8:48 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10 9:15 ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 12:34 ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-11 18:09 ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-11 23:58 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-12 19:29 ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-12 21:15 ` 2.6.26-rc5-mm2 (swap_state.c:77) Hugh Dickins
2008-06-13 17:45 ` Rik van Riel
2008-06-13 21:15 ` Hugh Dickins
2008-06-13 22:03 ` Rik van Riel
2008-06-10 15:34 ` 2.6.26-rc5-mm2 Lee Schermerhorn
2008-06-10 16:50 ` 2.6.26-rc5-mm2 Hugh Dickins
2008-06-10 10:20 ` 2.6.26-rc5-mm2 lockup up on Intel G33+ICH9R+Core2Duo, -mm1 okay Grant Coady
2008-06-10 18:18 ` Andrew Morton
2008-06-10 21:48 ` Grant Coady
2008-06-10 11:50 ` 2.6.26-rc5-mm2 compile error in vmscan.c Helge Hafting
2008-06-10 12:23 ` Johannes Weiner
2008-06-10 18:37 ` Andrew Morton
2008-06-12 8:13 ` Helge Hafting
2008-06-11 2:26 ` 2.6.26-rc5-mm2 (compile error in mm/memory_hotplug.c) Yasunori Goto
2008-06-11 6:00 ` 2.6.26-rc5-mm2: OOM with 1G free swap Alexey Dobriyan
2008-06-11 6:11 ` Nick Piggin
2008-06-11 6:15 ` Nick Piggin
2008-06-11 6:27 ` Andrew Morton
2008-06-11 6:31 ` Nick Piggin
2008-06-11 6:36 ` KOSAKI Motohiro
2008-06-11 7:31 ` Frederik Deweerdt
2008-06-11 12:57 ` Rik van Riel
2008-06-11 13:44 ` Nick Piggin
2008-06-11 17:56 ` [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388! Kamalesh Babulal
2008-06-11 18:28 ` Dave Hansen
2008-06-11 18:37 ` Vegard Nossum
2008-06-12 6:55 ` Kamalesh Babulal
2008-06-11 18:08 ` Jiri Slaby [this message]
2008-06-11 19:03 ` pnp changes -> suspend oops [Was: 2.6.26-rc5-mm2] Bjorn Helgaas
2008-06-12 21:10 ` Jiri Slaby
2008-06-12 21:22 ` Bjorn Helgaas
2008-06-12 21:39 ` Jiri Slaby
2008-06-12 21:57 ` Bjorn Helgaas
2008-06-12 21:57 ` Jiri Slaby
2008-06-13 16:05 ` Jiri Slaby
2008-06-13 17:23 ` Bjorn Helgaas
2008-06-16 10:43 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=485014B5.7080305@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox