On Thu, 2008-10-02 at 22:57 +0100, Laura Speck wrote: > Alan Cox wrote: > > > INFO: task scsi_scan_0:449 blocked for more than 120 seconds > > > > > > > It got stuck trying to scan a scsi device - perhaps the RAID array. If > > you hit a key during the boot prompt from grub and edit the boot line to > > remove the "quiet" it will spew rather more info which should help see > > what broke and where > > > You are right :) Tons and tons of this: > > aac_srb: aac_fib_send failed with status: 8195 > > I found this https://bugzilla.redhat.com/show_bug.cgi?id=450444 > > Adding aacraid.dacmode=0 did not help, same errors. But mem=4G did. I > went into the GRUB menu and edited the boot line ('e') and it booted > fine. > > Can anyone point me in the direction of how I would permanently fix > this? I noticed on > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=94cf6ba11b that it says "limiting the discovered kernel memory (mem=4G) with an associated loss in runtime performance" - is there a better way to fix this issue, now that I can actually access the box? > > Thanks in advance!!! :) Much appreciated. ---- You probably realize this but you could add the mem=4G line to /boot/grub/grub.conf to permanently use that option. You could also try using the PAE kernel as that is capable of addressing > 3 GB of RAM You probably want to make sure the firmware on the PERC 3/Di is the latest version as suggested by Jeff Lawson since he reported that the problem went away after updating (and using the PAE kernel but he was using CentOS 5, not Fedora) Craig -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
