[Fwd: Re: Kernel panicking in 6.2 and 7-CURRENT -- interrupt issues]

[Ed Dotorg]

youshi10 at u.washington.edu wrote:
> On Tue, 29 May 2007 youshi10 at u.washington.edu wrote:
> 
>> Hello,
>>     I'm trying to install 7-CURRENT on my desktop, locally instead of 
>> on a virtual machine, and I'm running into an issue where the kernel 
>> almost always panics on boot with my motherboard (ASUS P5N-SLI E), due 
>> to some sort of interrupt assignment / probing issues.
>>
>> Observations:
>>     1. 7-CURRENT (built) never properly detects the interrupts on the 
>> system.
>>     2. 7-CURRENT (May ISO snapshot) doesn't properly detect my USB 
>> keyboard, but boots and runs sysinstall.
>>     3. 6.2 RELEASE panics if I don't boot FreeBSD up into "safe mode", 
>> due to an issue with the ohci driver (I think the error message had 
>> something to deal with device adding / enumeration and not being able 
>> to find a memory / interrupt address).
>>
>>     First off, if I could get some of the command line arguments to 
>> pass to the kernel to emulate safe-mode, that would be much 
>> appreciated. Second off, if anybody has any ideas on how to debug this 
>> issue, I'll go off and try to determine what the cause is. If it's 
>> anything like it was before (clean out /usr/obj, rebuild), I'll be ok. 
>> Otherwise, I'll have to purchase more parts and build another 
>> dedicated FreeBSD system :(..
>>
>> Thanks,
>> -Garrett
> 
> Sorry for cross-posting so much, but this information is relevant to all 
> of the mailing lists included.
> 
> Ok I "solved" my problem, to a certain extent.
> 
> Basically the ASUS P5N-E SLI motherboard (nVidia chipset) isn't bootable 
> with FreeBSD 6.2 RELEASE without going into SAFE MODE (panics after 
> ohci_add_done looking for a non-existent memory address, if the USB 
> controller is enabled in the BIOS with "Legacy Mode", i.e. USB Keyboard 
> compatible), and isn't compatible with FreeBSD 7 at all (kernel can't 
> map IRQs properly on up-to-date CURRENT and panics in kernel mode during 
> boot).
> 
> Strangely enough the 7-CURRENT snapshot ISOs work, but then again it 
> doesn't setup the OHCI and USB keyboard stuff properly, and I can't get 
> any sort of input from my keyboard, obviously.
> 
> The ASUS P5B-DLX motherboard (Intel chipset) is compatible with FreeBSD 
> 6.2 and 7 though, without any hacks.
> 
> Maybe someone should update some documentation on the release notes page 
> for supported hardware?
> 
> Thanks,
> -Garrett
> 
> PS Please CC me in any communication as I'm not subscribed to doc@, 
> stable@, or usb at .
> 
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> 
> 


-- 

Greetings,

I've been experiencing a similar problem.  I'm installing from a 6.2 Release CD to an Abit fp-in9 sli board (nvidia nforce mcp51 disk controller and nvidia nforce mcp13 network adapter), 2 gig ddr2 ram, sata 300 disk.  The install goes without problems but after rebooting, the onboard nic is not active.  "nve0: failed to start NVIDIA Hardware interface".  I add an fxp card, at this point 6.2 release is installed and functional and the system boots up normally.  I can cvsup ports, install ports and even upgrade xorg with no problems.  Although the xorg meta port (x11-drivers) caused me a little grief.  I can also compile a generic or custom kernel and all is ok.

My problem begins when I cvsup to releng_6 and compile a new kernel.  My most recent cvsup is from yesterday 6-4-2007 although I've been fussing with this board since the middle of May.   After make buildworld and make kernel (GENERIC or custom kernel) I reboot and end up at the "mountroot>" prompt where GEOM tells me that the only device available to boot from is fd0.  But, if I reboot and select Safe Mode the machine comes up without problems and I can finish the steps to building the new kernel.  From then on with each reboot I must select Safe Mode for the machine to come up.  I get the same results whether my disk drive is a single IDE or a single SATA-300.

It would be nice to get things working with this board.  This is my first nvidia chipset board but it looks as though I'll be looking for one with the trusty Intel chipset.


Ed