Hi Peter,

Peter Neal wrote:

> That'll be because I forgot to attach it :-) Third time lucky..?

Sorry for the slow response.

It should be possible to make sense of this trace using
scripts/decodecode from the kernel source tree, but first some basic
questions:

- was this reproducible?
- if so, was the stack trace in the oops always the same?
- is it still reproducible?
- if so, does it happen with the latest lenny kernel? Results from
a lenny-backports kernel would be helpful as well.

Thanks,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111001020345.GA4845@elie.sbx02827.chicail.waypor t.net">http://lists.debian.org/20111001020345.GA4845@elie.sbx02827.chicail.waypor t.net

It seems to have gone away, I haven't had the issue for ages now.
Thanks for the response.

On 1 October 2011 03:03, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi Peter,
>
> Peter Neal wrote:
>
>> That'll be because I forgot to attach it :-) Third time lucky..?
>
> Sorry for the slow response.
>
> It should be possible to make sense of this trace using
> scripts/decodecode from the kernel source tree, but first some basic
> questions:
>
> *- was this reproducible?
> *- if so, was the stack trace in the oops always the same?
> *- is it still reproducible?
> *- if so, does it happen with the latest lenny kernel? *Results from
> * a lenny-backports kernel would be helpful as well.
>
> Thanks,
> Jonathan
>



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CALJvf+rwGPBEzC_0WrNDjF2y6t4p14uHQO8CDu3aBbZtp4Daa A@mail.gmail.com">http://lists.debian.org/CALJvf+rwGPBEzC_0WrNDjF2y6t4p14uHQO8CDu3aBbZtp4Daa A@mail.gmail.com