Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Jeff Garzik <jgarzik@xxxxxxxxx>
- Date: Thu, 12 Jan 2006 15:59:29 -0500
Alan Cox wrote:
On Iau, 2006-01-12 at 16:55 +1300, Reuben Farrelly wrote:
ata1: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x0 irq 0 ata2: SATA max UDMA/133 cmd 0x0 ctl 0x2 bmdma 0x8 irq 0 Unable to handle kernel NULL pointer dereference at virtual address 00000000
That is the critical bit. The SATA ports have no PCI resources assigned for bus mastering (BAR 4). libata should have driven the device PIO in this case but the resource should have been assigned.
Agreed. This appears to be BIOS assigning bad values to SATA hardware.
However, libata should recognize this and not attempt to iomap or drive the hardware, in that case, rather than oops.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Reuben Farrelly
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- References:
- [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Greg KH
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Linus Torvalds
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Andrew Morton
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Alan Cox
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Andrew Morton
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Reuben Farrelly
- Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- From: Alan Cox
- [GIT PATCH] PCI patches for 2.6.15 - retry
- Prev by Date: Re: pcnet32 devices with incorrect trident vendor ID
- Next by Date: Re: pcnet32 devices with incorrect trident vendor ID
- Previous by thread: Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- Next by thread: Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- Index(es):
Relevant Pages
|
|
