From: Jens Axboe <axboe@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, viro@ftp.linux.org.uk
Subject: Re: 2.6.16-git4: kernel BUG at block/ll_rw_blk.c:3497
Date: Wed, 29 Mar 2006 10:16:43 +0200 [thread overview]
Message-ID: <20060329081642.GU8186@suse.de> (raw)
In-Reply-To: <44288882.4020809@rtr.ca>
On Mon, Mar 27 2006, Mark Lord wrote:
> This popped up during heavy RAID5 testing today (2.6.16-git4).
> The SATA drives are being run by a modified sata_mv that I'm testing,
> and it seems to be behaving now, except for the BUG below:
>
> Cheers
>
> ------------[ cut here ]------------
> kernel BUG at block/ll_rw_blk.c:3497!
> invalid opcode: 0000 [#1]
> PREEMPT SMP
> Modules linked in: sata_mv libata raid5 xor snd_pcm_oss snd_pcm snd_timer
> snd_page_alloc snd_mixer_oss snd soundcore edd pl2303 usbserial usblp
> usbhid evdev joydev sg sr_mod ide_cd cdrom af_packet ohci_hcd sworks_agp
> agpgart e100 mii i2c_piix4 i2c_core usbcore sd_mod dm_mod scsi_mod
> CPU: 1
> EIP: 0060:[<b0209e76>] Not tainted VLI
> EFLAGS: 00010246 (2.6.16-git4 #1)
> EIP is at put_io_context+0x66/0x80
> eax: 00000000 ebx: b1ac096c ecx: e3ced12c edx: ef25b798
> esi: ed72a570 edi: ed72aa20 ebp: 00000000 esp: d2619f78
> ds: 007b es: 007b ss: 0068
> Process cat (pid: 16399, threadinfo=d2618000 task=ed72a570)
> Stack: <0>b19acba0 b0124ea5 00000004 d2619fbc d2619fbc b035c26b 00000001
> 00000000
> e043b660 d2618000 00000000 b0125097 00000000 3abf1f04 3abf1f04
> d2618000
> b0102e1b 00000000 00000000 00000000 3abf1f04 3abf1f04 aff1e8d8
> 000000fc
> Call Trace:
> [<b0124ea5>] do_exit+0x295/0x410
> [<b0125097>] do_group_exit+0x37/0xa0
> [<b0102e1b>] sysenter_past_esp+0x54/0x75
> Code: 75 22 b8 00 e0 ff ff 21 e0 ff 48 14 8b 40 08 a8 08 75 24 89 da 5b a1
> 44 b8 46 b0 e9 65 6a f5 ff ff d2 eb d0 90 ff d2 eb d9 5b c3 <0f> 0b a9 0d
> 2c ac 36 b0 89 f6 eb 9b e8 79 f2 12 00 eb d5 8d b4
> <1>Fixing recursive fault but reboot is needed!
Auch, so that's
BUG_ON(atomic_read(&ioc->refcount) == 0);
triggering. What sort of testing were you running, exactly?
Al, any ideas?
--
Jens Axboe
next prev parent reply other threads:[~2006-03-29 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:51 2.6.16-git4: kernel BUG at block/ll_rw_blk.c:3497 Mark Lord
2006-03-29 8:16 ` Jens Axboe [this message]
2006-03-29 8:27 ` Al Viro
2006-03-29 9:08 ` Jens Axboe
2006-03-29 13:52 ` Mark Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060329081642.GU8186@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox