From: Russell King <rmk@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Michael Frank <mflt1@micrologica.com.hk>,
daniel.ritz@gmx.ch, linux-kernel@vger.kernel.org,
linux-pcmcia@lists.infradead.org
Subject: Re: 2.5.74-mm3 yenta-socket oops back
Date: Thu, 10 Jul 2003 11:08:56 +0100 [thread overview]
Message-ID: <20030710110856.A1074@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030709213010.1882a898.akpm@osdl.org>; from akpm@osdl.org on Wed, Jul 09, 2003 at 09:30:10PM -0700
On Wed, Jul 09, 2003 at 09:30:10PM -0700, Andrew Morton wrote:
> This one may not be. How did we get here with no thread to handle the
> event? Do you have an oops trace on this one?
It's correct. Had the fan in my server not died last night, I'd have
gotten some of these fixes to Linus. God how I hate anything with fans
in. They're the number one cause of failure.
The problem is that the interrupts are claimed before pcmcia has been
properly initialised, so the cs.c-private bits of pcmcia_socket aren't
setup.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2003-07-10 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 22:39 yenta-socket oops with 2.5.73-mm3, 2.5.74, 2.5.74-mm1 Daniel Ritz
2003-07-06 3:26 ` Michael Frank
2003-07-06 7:45 ` Russell King
2003-07-06 13:14 ` Michael Frank
2003-07-06 22:15 ` Russell King
2003-07-07 2:02 ` Michael Frank
2003-07-10 3:27 ` 2.5.74-mm3 yenta-socket oops back Michael Frank
2003-07-10 4:30 ` Andrew Morton
2003-07-10 7:09 ` Michael Frank
2003-07-10 7:56 ` Andrew Morton
2003-07-10 10:08 ` Russell King [this message]
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=20030710110856.A1074@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=mflt1@micrologica.com.hk \
/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