Description of problem: After upgrading to kernel 2.6.19-1.2895 (and everything else up to date as of 01/18/07) I get the following message just after grub boots the kernel: JMB361: dma_base is invalid JMB361: dma_base is invalid Then it hard locks, the HD light stays on full (see referenced ticket, this happened to others before) and it stays there forever. Does it every time, going back to the old kernel 2.6.18-1.2869 works. Version-Release number of selected component (if applicable): 2.6.19-1.2895 Additional info: HD: Western Digital Caviar WD2500KS Motherboard: GIGABYTE GA-965P-S3, info here: http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=2321&ProductName=GA-965P-S3
Without 'quiet' on, JMB361: chipset revision 2 JMB361: 100% native mode on irq 17 JMB361: dma_base is invalid ide0: JMB361 Bus-Master DMA disabled (BIOS) --- It booted properly when I set an option in BIOS (although it worked fine the other way in 2.6.18 if you recall), SATA Port0-3 Native Mode: Native IDE (it was previously set to Legacy IDE)
I had the same problem and bypassed it by changing the BIOS option as described by Brett Hoerner. I get the same error messages on JMB361 as Brett Hoerner.
I have the same problem (kernel-2.6.19-1.2911.fc6, GIGABYTE GA-965P-S3 motherboard). Brett's method allowed me to boot, but error message still appears twice: JMB363: dma_base is invalid Also, older kernel worked fine.
(This is a mass-update to all current FC6 kernel bugs in NEW state) Hello, I'm reviewing this bug list as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug, however this version of Fedora is no longer maintained. Please attempt to reproduce this bug with a current version of Fedora (presently Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a few days if there is no further information lodged. Thanks for using Fedora!
Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA, since no information has been lodged for over 30 days. Please re-open this bug or file a new one if you can provide the requested data, and thanks for filing the original report!