Re: Oops removing files on a full f/s

[Steve Lord <lord@xxxxxxx>]

Yes, a backtrace from this would be really useful, also, in the backtrace
you will see the arguments of the functions, if you could take the third
argument of __make_request and pass it to the md command in kdb:

kdb> md <address>

and send the output of that too - it will dump the buffer contents
which may help.

Thanks

  Steve

> fsstress filled up /usr 100% so I was going remove the p* directories
> and files. This provoked an oops:
> 
> Kernel BUG at ll_rw_blk.c:700!
> 
> Entering kdb (current=0xcbc1a000, pid 944) on processor 0 Oops: invalid
> operand due to oops @ 0xc020fca4
> 
> eax=0x0000001f ebx=0x00000000 ecx=0x00000002 
> edx=0x20000000 esi=0xca02da80 esp=0xcbc1bd3c
> eip=0xc020fca4 ebp=0xc040a240 xss=0x00000018
> xcs=0x00000010 eflags=0x00010286
> xds=0x00000018 xes=0x00000018
> origeax=0xffffffff &regs=0xcbc1bd00
> 
> [0]kdb>
> 
> Anything useful likely to come out of this, or should I just reboot?
> 
> -- Juha