Re: Linuv 2.6.15-rc1

Zilvinas Valinskas
2005-11-16T09:48:21Z

Hello,

Please see : http://www.gemtek.lt/~zilvinas/dumps/trace

This time I didn't see oops printed again :( Don't understand why,
although I have managed to capture SysRQ-T output - see URL above.
Kernel has been updated this morning to revision:

f6ff56cd56b83d8edf4b3cffc5c53c56b37a5081

plus additionally applied patch from URL. Interesting this time I
haven't seen any signs of slab corruptions or any such things :(

I hope this helps. Any other ideas and things to try out ? :)

btw, what are these messages about:
Unknown notification: subtype=40,flags=0xa0,size=40

I've read a ipw2200.c code and didn't see what is subtype=40 ...
Because once those messages are starting showing up - immediately (most
of the time) follows by kernel freeze (sysrq is working though ...).

Zilvinas

On Wed, Nov 16, 2005 at 01:49:04PM +0800, Zhu Yi wrote:
> On Tue, 2005-11-15 at 16:00 +0200, Zilvinas Valinskas wrote:
> > Hello again,
> >
> > screenshots of ooops (not of the best quality though :( ) -
> > http://www.gemtek.lt/~zilvinas/dumps/ - as it can be seen from
> > screenshots crashing in _ipw_read_indirect_0xa9/0x179 ... This time it
> > took a while to reproduce a problem. Somehow I get impression it is
> > either f/w loading related (see attached oops.1 file) and/or initiating
> > scan and reading back wireless scan results ??? ...
>
> Please try the patch below and see if it makes any difference.
> http://bughost.org/bugzilla/show_bug.cgi?id=821
>
> Thanks,
> -yi
>
> -
> 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/