[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46129968.9000304@gmail.com>
Date: Tue, 03 Apr 2007 20:14:00 +0200
From: Rene Herman <rene.herman@...il.com>
To: Pekka J Enberg <penberg@...helsinki.fi>
CC: linux-kernel@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>
Subject: Re: mcdx -- do_request(): non-read command to cd!!
On 04/03/2007 07:31 PM, Pekka J Enberg wrote:
> Oh, well, here goes. Rene, would you be so kind and spin the wheel once
> more? =)
Absolutely!
root@...2:~# dd if=/dev/mcdx0 of=/dev/null
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[<c1047787>] Not tainted VLI
EFLAGS: 00010082 (2.6.20.4 #11)
EIP is at free_block+0x58/0xcf
eax: 07ff46c6 ebx: c1d5f100 ecx: c1d5f12c edx: 160010b9
esi: c16414e0 edi: c160c960 ebp: 00000001 esp: c1575ef0
ds: 007b es: 007b ss: 0068
Process events/0 (pid: 4, ti=c1575000 task=c1577510 task.ti=c1575000)
Stack: 00000000 00000002 c165fa38 c165fa38 00000002 c165fa00 00000000
c1047eb6
00000000 00000000 c16414e0 c160c960 c16414e0 c160c960 c14ab540
00000292
c1047f3a 00000000 00000000 00000292 c14ab544 c154ebc0 c101ec7a
c154ec14
Call Trace:
[<c1047eb6>] drain_array+0x94/0xc3
[<c1047f3a>] cache_reap+0x55/0xe9
[<c101ec7a>] run_workqueue+0x8f/0x14d
[<c1047ee5>] cache_reap+0x0/0xe9
[<c101ee5a>] worker_thread+0x122/0x14b
[<c100e2d8>] default_wake_function+0x0/0xc
[<c100e2d8>] default_wake_function+0x0/0xc
[<c101ed38>] worker_thread+0x0/0x14b
[<c1021800>] kthread+0x72/0x97
[<c102178e>] kthread+0x0/0x97
[<c1002b47>] kernel_thread_helper+0x7/0x10
=======================
Code: 05 03 15 4c ab 4a c1 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 a8 80 75
04 0f 0b eb fe 8b 5a 1c 8b 44 24 20 8b 53 04 8b 74 87 18 8b 03 <89> 02
c7 03 00 01 10 00 89 50 04 c7 43 04 00 02 20 00 8b 44 24
EIP: [<c1047787>] free_block+0x58/0xcf SS:ESP 0068:c1575ef0
That is, the exact same oops the tar test showed which I expect is
progress -- the dd is now in fact doing something :-)
When I now switched the monitor to 5va2 itself it was happily generating
more oopses and supposedly "fixing up recursive faults", while advicing
me to reboot. 2 seconds later it didn't leave me a choice as it dropped
dead :-)
Just to keep track, I'm now using the patches (minus 03) at:
http://members.home.nl/rene.herman/mcdx/
(for lkml: with 03, the machine locks itself hard each and every time
without information).
Thanks again :)
Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists