Oops in 2.5.38-mm2

Oops in 2.5.38-mm2

[Grega Fajdiga]

Good day,

I get this oops at startup in 2.5.38-mm2. The oops
might be in vanilla too, but didn't check.

ksymoops 2.4.4 on i686 2.5.38.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.5.38/ (default)
     -m /boot/System.map-2.5.38 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

c0117826 c02433c0 c02452c2 00000562 c0362c70 c0134386 c02452c2
       00000562 c150b080 ffffffff 00000000 00000fff c0362e94 dfdf9c80 c01d2e60
       04000000 c0362c70 c0109562 00000018 000001d0 dfdf9c80 c0362c60 0000000e
Call Trace: [<c0117826>] [<c0134386>] [<c01d2e60>] [<c0109562>] [<c01cc496>]
   [<c01d2e60>] [<c01cc8fc>] [<c01cc16d>] [<c01dcf6b>] [<c01050b1>] [<c0105060>]
   [<c0105539>]
Warning (Oops_read): Code line not seen, dumping what data is available

Trace; c0117826 <__might_sleep+56/5d>
Trace; c0134386 <kmalloc+66/1f0>
Trace; c01d2e60 <ide_intr+0/1d0>
Trace; c0109562 <request_irq+52/a0>
Trace; c01cc496 <init_irq+206/350>
Trace; c01d2e60 <ide_intr+0/1d0>
Trace; c01cc8fc <hwif_init+10c/250>
Trace; c01cc16d <probe_hwif_init+1d/70>
Trace; c01dcf6b <ide_setup_pci_device+3b/60>
Trace; c01050b1 <init+51/1d0>
Trace; c0105060 <init+0/1d0>
Trace; c0105539 <kernel_thread_helper+5/c>


2 warnings issued.  Results may not be reliable.

If you need anymore info, please ask.

Also, please CC me, since I'm not on the list.

Best Regards,
Grega Fajdiga

Re: Oops in 2.5.38-mm2

[Andrew Morton]

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.

Re: Oops in 2.5.38-mm2

[Jens Axboe]

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.

-- 
Jens Axboe

Re: Oops in 2.5.38-mm2

[Andrew Morton]

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.