lkml.org 
[lkml]   [2005]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: sata_promise KERNEL_BUG on 2.6.12
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



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-06-20 04:28    [from the cache]
©2003-2011 Jasper Spaans