Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Jun 2013 14:23:56 +0930
From:      Shane Ambler <FreeBSD@ShaneWare.Biz>
To:        Ewald Jenisch <a@jenisch.at>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Panic/reboot while trying to install 9.1 on a HP Proliant DL580G5
Message-ID:  <51BBF364.3010003@ShaneWare.Biz>
In-Reply-To: <20130614140325.GA2551@aurora.oekb.co.at>
References:  <20130606141104.GA1261@aurora.oekb.co.at> <51B13325.6060404@ShaneWare.Biz> <20130614140325.GA2551@aurora.oekb.co.at>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 14/06/2013 23:33, Ewald Jenisch wrote:
> On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote:
>> Just guessing from what I see -
>>
>> The panic is "No usable event timer found!"

I did say just guessing and thought someone more knowledgeable may have
spoken by now. One thing I did find - there is a freebsd-proliant
mailing list that may be more helpful than here.

> Thanks much for the hints you sent me. Since I'm pretty swamped with
> work it took me a couple of days before I could go on with my tests.
>
>> Can you boot into single user mode?
>
> Nope - freezes at the exact same point during boot.
>
>> what does sysctl kern.eventtimer.choice show?
>
> Well - nothing to be honest:
> "variable 'kern.eventtimer.choice' not found"

Wondering if the system needs to be running to see that.

>> Have you tried kern.eventtimer.periodic=0 or other values for
>> kern.eventtimer.timer?
>
> With "kern.eventtimer.periodic=0" - same result.
>
> What other values would be valid for "kern.eventtimer.timer"?

That's where the eventtimer.choice comes in.
As an example on my asus mb I get
kern.eventtimer.choice: LAPIC(600) HPET(550) HPET1(440) HPET2(440)
HPET3(440) HPET4(440) i8254(100) RTC(0)
I thought in single user mode you could see your list of available options.

>> Is the panic the same without the loader adjustments?
>
> Yes, absolutely the same.
>
>> Does it boot 8.3 ?
>
> Haven't tried this, since I need to go to 9.1 on this system
> anyway. Besides that the server is in a remote DC so changing disks is
> not an easy thing to do.

If 8.3 boots it then you can patch and compile your own kernel that
supports your hardware. Being remote it may not be helpful unless you
can have some indication that it will boot 8.3





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?51BBF364.3010003>