Fedora Users — Re: Boot hangs on modprobe errors

Re: Boot hangs on modprobe errors

Date Prev

Date Next

Thread Prev

Thread Next

Date Index

Thread Index

To: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>

Subject: Re: Boot hangs on modprobe errors

From: Laura Speck <girlstar@xxxxxxxxx>

Date: Thu, 02 Oct 2008 22:57:18 +0100

Cc: "Community assistance, encouragement, and advice for using Fedora." <fedora-list@xxxxxxxxxx>

In-reply-to: <20081002213956.666b2546@xxxxxxxxxxxxxxxxxxx>

References: <3421f5f0810021134t547fbdew9314336a18c67df5@xxxxxxxxxxxxxx> <20081002213956.666b2546@xxxxxxxxxxxxxxxxxxx>

Reply-to: "Community assistance, encouragement, and advice for using Fedora." <fedora-list@xxxxxxxxxx>

User-agent: Thunderbird 2.0.0.17 (Windows/20080914)

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.

--
Laura

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines