From: Andrew Morton <akpm@digeo.com>
To: Jens Axboe <axboe@suse.de>
Cc: Grega Fajdiga <Gregor.Fajdiga@telemach.net>,
linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.5.38-mm2
Date: Mon, 23 Sep 2002 11:13:46 -0700 [thread overview]
Message-ID: <3D8F59DA.5ACD0044@digeo.com> (raw)
In-Reply-To: 20020923180435.GF15479@suse.de
Jens Axboe wrote:
>
> On Mon, Sep 23 2002, Andrew Morton wrote:
> > Grega Fajdiga wrote:
> > >
> > > Good day,
> > >
> > > I get this oops at startup in 2.5.38-mm2. The oops
> >
> > It's not an oops - it's just a warning.
> >
> > > ..
> > > Trace; c0117826 <__might_sleep+56/5d>
> > > Trace; c0134386 <kmalloc+66/1f0>
> > > Trace; c01d2e60 <ide_intr+0/1d0>
> >
> > ide_intr() is calling sleeping functions inside ide_lock.
>
> this is ludicris, why on earth would ide_intr() call kmalloc() from its
> isr?! the trace is obviously bogus.
>
Argh, sorry - brain is mush. It's init_irq() which is calling
sleeping functions inside ide_lock. The ide_intr is just stack gunk.
prev parent reply other threads:[~2002-09-23 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 13:33 Oops in 2.5.38-mm2 Grega Fajdiga
2002-09-23 17:01 ` Andrew Morton
2002-09-23 18:04 ` Jens Axboe
2002-09-23 18:13 ` Andrew Morton [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=3D8F59DA.5ACD0044@digeo.com \
--to=akpm@digeo.com \
--cc=Gregor.Fajdiga@telemach.net \
--cc=axboe@suse.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