Ben writes:
> It looks like we have enough information from you in this case,
> but in future please use reportbug. We install extensive 'bug'
> scripts to gather system information that may be relevant.

OK, willdo.

I had another occurrence of this last night, with a
not-very-plausible-looking stack trace. I captured it with my digital
camera and here it is retyped (timestamps omitted, and wrap damage fixed):

Process cat (pid: 2464, ti=f46f4000 task=f6104000 task.ti=f46f6000)
Stack:
ffffe000 4f3b1ffc 4f3b0000 00000000 4f3b0000 4f3b0575 00000000 f46f5f28
<0> c100510e c12737fc c12de85f 00000000 f46f5f28 205b0020 00000000 c12de85f
<0> f46f60bc f46f6080 00000000 c10059e4 00000000 c12737fc c12de85f c12df00c
Call trace:
[<c100510e>] ? dump_trace+0x60/0x8e
[<c10059e4>] ? show_trace_log_lvl+0x2e/0x36
[<c1004f53>] ? show_trace_log_lvl+0x8b/0x93
[<c1004fe6>] ? show_registers+0x8b/0x153
[<c126e6bd>] ? __die+0x70/0xbb
[<c101b74b>] ? no_context+0xe5/0x10e
[<c101b889>] ? __bad_area_nosemaphore+0x115/0x11d
Code: 24 28 31 c9 89 f2 ff d7 83 c3 04 83 7c 24 2c 00 74 0d 3b 5c 24 2c 73 22 3b 1c 24 72 1d eb 0c 3b 5c 24 08 76 15 3b 5c 24 04 73 0f <8b> 33 89 f0 e8 6b c8 03 00 85 c0 75 9d eb ce 83 c4 10 89 e8 5b
EPI: [<c1005ab6>] print_context_stack+0x80/0x9a SS:ESP 0068:f46f5ef0
CR2: 00000000f43b0575
---[ end trace 6f407ad9f5c9fda3 ]---

In case it's at all relevant, a copy of cat running on this machine is
quite likely to have been reading or writing a pty with a SLIP line
discipline.

Here's the image:
http://www.chiark.greenend.org.uk/~ijackson/2011/617708-crash.png

Ian.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 19834.26131.768642.89677@chiark.greenend.org.uk">h ttp://lists.debian.org/19834.26131.768642.89677@chiark.greenend.org.uk