Hi Andrew: This Chip is JMB363 not JMB361. ;-) This is a known issue. Because jmicron module will probe both fn0 and fn1 device under Debian 4.0r0. Please add " jmicron.jmicron=no_probe" to skip jmicron module probing in OS installation. Best Regards, Ethan Hsiao -----Original Message----- From: linux-ide-owner@xxxxxxxxxxxxxxx [mailto:linux-ide-owner@xxxxxxxxxxxxxxx] On Behalf Of Andrew Paprocki Sent: Tuesday, May 22, 2007 8:48 AM To: linux-ide@xxxxxxxxxxxxxxx Subject: JMicron JMB361 sporadically failing to initialize from at least 2.6.18.4 to 2.6.22-rc2 I have a Gigabyte GA-965P-DQ6 motherboard which has onboard Intel ICH8 raid as well as a "Gigabyte" (rebranded JMicron) chipset for 2 separate SATA ports. When I boot the machine, it completely sporadically fails to initialize the JMB361 chipset which it detects, claiming "dma_base is invalid". When it works (~20% of the time), it will correctly detect the chip and all drives connected to it. It feels like a race condition.. I have a DVD-RW & my boot SATAII drive connected to the controller, so this bug has the nasty side effect of hanging my machine for eternity waiting for the root drive to appear. The dma_base trace is listed below: JMB361: IDE controller at PCI slot 0000:03:00.0 ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 177 JMB361: chipset revision 3 JMB361: 100% native mode on irq 177 JMB361: dma_base is invalid ide0: JMB361 Bus-Master DMA disabled (BIOS) JMB361: dma_base is invalid ide1: JMB361 Bus-Master DMA disabled (BIOS) This seems to be the same problem as reported here: http://www.mail-archive.com/debian-bugs-dist@xxxxxxxxxxxxxxxx/msg339806.ht ml And numerous other people seem to be hitting this in newer kernels. A Google search for 'jmb361 dma_base' turns up a lot of hits. Does anyone know what is causing this and if it is fixed in any dev branch? I've tried the stock Debian etch netinst 2.6.18.4 kernel, as well as my own build of 2.6.21.1 and 2.6.22-rc2 and they all exhibit the same problem. Let me know what I can do to help debug this on my end. Thanks -Andrew - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
