From: Andrew Morton <akpm@osdl.org>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: 2.6.10-rc2 pbook oops on resume
Date: Tue, 16 Nov 2004 21:49:38 -0800 [thread overview]
Message-ID: <20041116214938.65601546.akpm@osdl.org> (raw)
In-Reply-To: <1100605854.6333.7.camel@localhost>
Soeren Sonnenburg <kernel@nn7.de> wrote:
>
> machine comes up ok, but I see this oops in dmesg... Any ideas ?
That would be due to this code in ohci_pci_resume():
#ifdef CONFIG_PMAC_PBOOK
if (_machine == _MACH_Pmac)
enable_irq (to_pci_dev(hcd->self.controller)->irq);
#endif
enabling an already-enabled IRQ.
I think Ben plays in this area?
> Soeren
>
> hda: Set PIO timing for mode 0, reg: 0x0c50032b
> eth0: suspending, WakeOnLan disabled
> radeonfb: suspending to state: 3...
> agpgart: Putting AGP V2 device at 0000:00:0b.0 into 0x mode
> agpgart: Putting AGP V2 device at 0000:00:10.0 into 0x mode
> radeonfb: switching to D2 state...
> cpufreq: resume failed to assert current frequency is what timing core
> thinks it is.
> radeonfb: switching to D0 state...
> radeonfb: resumed !
> Badness in enable_irq at kernel/irq/manage.c:106
> Call trace:
> [c0007570] dump_stack+0x18/0x28
> [c000536c] check_bug_trap+0xb4/0xf0
> [c0005538] ProgramCheckException+0x190/0x1c0
> [c0004954] ret_from_except_full+0x0/0x4c
> [c003cd70] enable_irq+0xa0/0xa8
> [c02813e8] ohci_pci_resume+0xbc/0xd4
> [c0277ee0] usb_hcd_pci_resume+0xb0/0x114
> [c01c9fbc] pci_device_resume+0x4c/0x50
> [c0224d2c] resume_device+0x44/0x4c
> [c0224e64] dpm_resume+0x130/0x148
> [c0224eb4] device_resume+0x38/0x78
> [c04b1be4] 0xc04b1be4
> [c04b20cc] 0xc04b20cc
> [c04b2930] 0xc04b2930
> [c0078e34] sys_ioctl+0x100/0x318
> Badness in enable_irq at kernel/irq/manage.c:106
> Call trace:
> [c0007570] dump_stack+0x18/0x28
> [c000536c] check_bug_trap+0xb4/0xf0
> [c0005538] ProgramCheckException+0x190/0x1c0
> [c0004954] ret_from_except_full+0x0/0x4c
> [c003cd70] enable_irq+0xa0/0xa8
> [c02813e8] ohci_pci_resume+0xbc/0xd4
> [c0277ee0] usb_hcd_pci_resume+0xb0/0x114
> [c01c9fbc] pci_device_resume+0x4c/0x50
> [c0224d2c] resume_device+0x44/0x4c
> [c0224e64] dpm_resume+0x130/0x148
> [c0224eb4] device_resume+0x38/0x78
> [c04b1be4] 0xc04b1be4
> [c04b20cc] 0xc04b20cc
> [c04b2930] 0xc04b2930
> [c0078e34] sys_ioctl+0x100/0x318
>
> --
> Sometimes, there's a moment as you're waking, when you become aware of
> the real world around you, but you're still dreaming.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-11-17 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 11:50 2.6.10-rc2 pbook oops on resume Soeren Sonnenburg
2004-11-17 5:49 ` Andrew Morton [this message]
2004-11-17 6:09 ` Benjamin Herrenschmidt
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=20041116214938.65601546.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=kernel@nn7.de \
--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