#5550: Boot Panic with ipwifi3945(abg) : out of MTRRs! [r35779] -----------------------------------------+---------------------------------- Reporter: composr | Owner: axeld Type: bug | Status: new Priority: blocker | Milestone: Unscheduled Component: Network & Internet/Wireless | Version: R1/alpha1 Keywords: | Blockedby: Platform: All | Blocking: -----------------------------------------+---------------------------------- Hello all, this is finally my first submission, which I will be happy to work out with the developers as much as possible. I have been following Haiku for a long time, and have been wanting to be more involved, so here we go. '''Setup''' I am running this particular build of Haiku on a Dell Latitude D830, which contains an Intel PROSet Wireless 3495ABG adapter. I have the machine set up with 4 partitions: * sda1: Linux / (root) * sda2: [swap] * sda3: Linux /liferay (for work projects) * sda4: Haiku All seems well, and I have the development environment set up in my Linux system, following the configuration for a GCC4-cross-compile and all. '''Procedure''' I updated my SVN to r35779 and built out a raw image, which was then written to a USB stick. I rebooted from the USB stick to find it would not boot. The splash screen shows up, and each icon lights up predictably during the boot process. Once the boot script is launched, I get a black screen indefinitely. Upon reboot, and configuring the screen dump instead of the splash screen, I end up with the following panic message: "(PANIC: add_used_mtrr(0xe00000000, 0x20000000, 1): out of MTRRs!)" I cannot retrieve the end of what the screen dump says, because it dumps to the screen, which immediately clears and drops to the kernel debugger. There are two ways I have confirmed this is a result of the wireless chipset: 1) Upon reboot, I drop into the BIOS setup, and disable the wireless adapter completely. Upon save and continue booting, Haiku boots as normal. 2) I have rebuilt Haiku, commenting out the inclusion of the wifi drivers in the HaikuImage ruleset in jam. Upon boot, proceeds as expected with no errors. Unfortunately, since the only way to get system information is through turning off the wireless adapter, it does not show up in the dumps I am attaching. I will plan on rebuilding Haiku, commenting out the wifi drivers install script, and hope that I can get it booted so I can provide dumps that contain the wireless adapter's information. I apologise for any confusion, and look forward to helping out as much as possible. -- Ticket URL: <http://dev.haiku-os.org/ticket/5550> Haiku <http://dev.haiku-os.org> Haiku - the operating system.