Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Apr 2008 07:55:12 -0700
From:      "Ryan Lackey" <ryan.lackey@gmail.com>
To:        "John Baldwin" <jhb@freebsd.org>, freebsd-stable@freebsd.org
Subject:   Re: HP DL145G2 boot problems with 7.0
Message-ID:  <5bfab4bc0804250755s10006a5eu8d58153ce1dc3a78@mail.gmail.com>
In-Reply-To: <200804250856.51805.jhb@freebsd.org>
References:  <5bfab4bc0804211223w34d41326g7350c51da35a1721@mail.gmail.com> <200804250856.51805.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
I actually figured out the problem.  I had gmirror on the machine, and was
booting to do maintenance using
non-gmirror kernel sometimes.  One kernel was using ad4, the other using
ad6, and one using gm0(ad4/ad6).

Kernel modules and kernel were consequently getting out of sync.

Problems are fixed now -- I'm currently being amazed by the SMP performance,
kqueue, and some
threaded python...doing as much on 2 old machines from 2005 and freebsd with
optimized python as we were
doing with 55 linux machines running badly tuned php5 in apache.

On Fri, Apr 25, 2008 at 5:56 AM, John Baldwin <jhb@freebsd.org> wrote:

> On Monday 21 April 2008 03:23:04 pm Ryan Lackey wrote:
> > I have 4 HP DL145G2 boxes (dual opteron).  I recently upgrded them from
> > 6.2-STABLE to 7.0-RELEASE using cvsup on each, compiling world + kernel.
> >
> > The upgrade was (fairly painless on two machines, and has broken the
> other
> > two machines.
> >
> > On boot, the broken machines hang somewhere after kbdc and psm, and
> before
> > serial driver initialization.
> >
> > Specifically, I see:
> > psm0:  unable to allocate IRQ
> > psmcpnp0: PS/2 mouse port irq 12 on acpi0
> > pm0: ps2 mouse irq 12 on atkbdc0
> > ioapic0: routing intpin 12 (ISA IRQ 12) to vector 57
> > psm0: giant-locked
> > psm0: thread
> > psm0: model intellimouse explorer....
> > psm0: config; 0000000000 flags: 000000008, packet size:4
> > psm0: syncmask:08, syncbits:00
> >
> > After that, it hangs.
>
> I would add more printfs to figure out exactly where it dies.  I would
> start
> by seeing if it makes it out of the psm driver.  If so, then I would start
> adding printfs to the new-bus code in sys/kern/subr_bus.c to see if
> drivers
> are probing when it hangs.
>
> --
> John Baldwin
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5bfab4bc0804250755s10006a5eu8d58153ce1dc3a78>