public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.16-rc3 kernel BUG at drivers/scsi/sata_mv.c:1018
Date: Wed, 15 Feb 2006 14:16:53 +0100	[thread overview]
Message-ID: <20060215131653.GA26178@favonius> (raw)

Hi Jeff and others,

I get a kernel BUG message when I try to create a raid1 or raid5 over
nine 64MB partitions located on nine sata disks (Maxtor Pro 500) on a
fresh setup. The system locks hard: no sysrq.

The onboard controller is an nVidia nForce with three disks.
The six other disks are connected to a Marvell 88SX6081 controller.

Last night and the first half of today all disks were tested with
badblocks in write mode, which the system survived just fine (one disk
out of ten detected as broken, so nine disks left).

A google search leads me to

http://www.uwsg.iu.edu/hypermail/linux/kernel/0601.2/0479.html

and

http://www.uwsg.iu.edu/hypermail/linux/kernel/0601.2/0626.html

I had MSI disabled in the .config already, and will try again with debug
options set.

In the mean time, is this of any help?

I can try any patch you throw at me, or any config option, as this
system is not in production yet.

	Sander

Linux version 2.6.16-rc3 (root@elisha) (gcc version 4.0.3 20060104 (prerelease) (Debian 4.0.2-6))

mdadm -C -l1 -n9 /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 \
/dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1

[19697.866199] md: bind<sda1>
[19697.866251] md: bind<sdc1>
[19697.866294] md: bind<sdd1>
[19697.866332] md: bind<sde1>
[19697.866374] md: bind<sdf1>
[19697.866414] md: bind<sdg1>
[19697.866454] md: bind<sdh1>
[19697.866492] md: bind<sdi1>
[19697.866531] md: bind<sdj1>
[19697.866734] raid1: raid set md0 active with 9 out of 9 mirrors
[19697.866888] ----------- [cut here ] --------- [please bite here ] ---------
[19697.866921] Kernel BUG at drivers/scsi/sata_mv.c:1018
[19697.866950] invalid opcode: 0000 [1] SMP 
[19697.866984] CPU 1 
[19697.867010] Modules linked in:
[19697.867040] Pid: 2491, comm: mdadm Not tainted 2.6.16-rc3 #1
[19697.867075] RIP: 0010:[<ffffffff8029975a>] <ffffffff8029975a>{mv_qc_prep+307}
[19697.867103] RSP: 0000:ffff81013fc9bd28  EFLAGS: 00010002
[19697.867152] RAX: ffff81000c63f03d RBX: ffff81013a691500 RCX: ffff81000c63f02a
[19697.867186] RDX: ffff81013a5639d8 RSI: 0000000000000046 RDI: ffff81013a5639b8
[19697.867220] RBP: ffff81013a5639b8 R08: 0000000000000004 R09: ffff81013fc9bc4c
[19697.867267] R10: 00000000000000c3 R11: ffffffff802e188d R12: 0000000000000000
[19697.867302] R13: ffff81013a563480 R14: ffffffff8027d502 R15: ffff81013a563480
[19697.867335] FS:  00002b35e01f7ae0(0000) GS:ffff81013fc759c0(0000) knlGS:0000000000000000
[19697.867384] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[19697.867415] CR2: 0000000000511768 CR3: 00000001333fc000 CR4: 00000000000006e0
[19697.867450] Process mdadm (pid: 2491, threadinfo ffff81013a040000, task ffff81013a591020)
[19697.867497] Stack: ffff81013a5639b8 ffff81013a5639b8 ffff81013a603280 ffffffff802932bd 
[19697.867546]        ffff81013a603280 ffff81013a5639b8 ffff81013a562280 ffff81013a563558 
[19697.867624]        ffff81013a563480 ffffffff8027d502 
[19697.867662] Call Trace: <IRQ> <ffffffff802932bd>{ata_qc_issue+794}
[19697.867710]        <ffffffff8027d502>{scsi_done+0} <ffffffff8029765d>{ata_scsi_translate+172}
[19697.867778]        <ffffffff802972ae>{ata_scsi_rw_xlat+0} <ffffffff8027d502>{scsi_done+0}


-- 
Humilis IT Services and Solutions
http://www.humilis.net

             reply	other threads:[~2006-02-15 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 13:16 Sander [this message]
2006-02-15 14:33 ` 2.6.16-rc3 kernel BUG at drivers/scsi/sata_mv.c:1018 Sander
2006-02-15 14:59 ` Jens Axboe
2006-02-15 16:31   ` Sander

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=20060215131653.GA26178@favonius \
    --to=sander@humilis.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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