From: Jeff Garzik <jgarzik@pobox.com>
To: Marcel Naziri <silent@zwobbl.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_promise KERNEL_BUG on 2.6.12
Date: Sun, 19 Jun 2005 22:25:05 -0400 [thread overview]
Message-ID: <42B62901.3000500@pobox.com> (raw)
In-Reply-To: <200506200402.55229.silent@zwobbl.de>
Marcel Naziri wrote:
> Now, when I connect the drives to port 1 & 2 of the controller, booting up
> stops with this:
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 17
> ata1: SATA max UDMA/133 cmd 0xF8802200 ctl 0xF8802238 bdma 0x0 irq 17
> ata2: SATA max UDMA/133 cmd 0xF8802280 ctl 0xF88022B8 bdma 0x0 irq 17
> ata3: SATA max UDMA/133 cmd 0xF8802300 ctl 0xF8802338 bdma 0x0 irq 17
> ata4: SATA max UDMA/133 cmd 0xF8802380 ctl 0xF88023B8 bdma 0x0 irq 17
> ata1: no device found (phy stat 00000000)
> scsi0 : sata_promise
> ata2: dev 0 ATA, max UDMA/100, 312581808 sectors: lba48
> ------------[ cut here ]------------
> kernel BUG at drivers/scsi/libata-core.c:2077!
> invalid operand: 0000 [#1]
> PREEMPT
> Modules linked in:
> CPU: 0
> EIP: 0060:[<c025f60f>] Not tainted VLI
> EFLAGS: 00010246 (2.6.12)
> EIP is at ata_dev_set_xfermode+0xcf/0xf0
This is highly strange. Do you have any patches applied, or is this
vanilla 2.6.12 kernel?
Can you turn off preempt and try to reproduce ?
Can you provide your full .config ?
> Can it deal with the fact, that the drives are not scanned in port order of
> the controller? They seem to be mapped like
> port 1 > ata4
> port 2 > ata2
> port 3 > ata1
> port 4 > ata3
The driver scans the ports in the order presented internally in the
hardware.
Jeff
next prev parent reply other threads:[~2005-06-20 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 2:02 sata_promise KERNEL_BUG on 2.6.12 Marcel Naziri
2005-06-20 2:25 ` Jeff Garzik [this message]
2005-06-20 2:38 ` Marcel Naziri
2005-06-20 2:41 ` Jeff Garzik
2005-06-20 12:32 ` Marcel Naziri
2005-06-20 13:25 ` Simon Sudler
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=42B62901.3000500@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=silent@zwobbl.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.