Having successfully upgraded one system in-place from 5.4 to 6.0 I had a go at the second system today. This is an old Compaq proliant 1600R with two 500mhz pentium3's in it. Currently running 5.4 quite happily. so I buildworld, buildkernel, insall kernel and rebooot to check that the kernel works... ...and the new kernel will not boot past the point where it says atkdb0: [GIANT LOCKED] (under 5.4 the next thing I get is psm0 for the mouse.) My kernel is (almost) a generic SMP one - the only changes are that I have removed INET6 and all CPU's apart from I686_CPU. I have tried booting this in 'safe' mode, and sevarl other options from the beatsie menu, but no dice. I havent yet tried a straight 'GENERIC' kernel, and given the time of night wont be able to until tomorrow, but am very puzzled as I havent seen anything like this before. Does anyone have any hints or suggestions as to what I might try ? -pcf.
Hi I have the same behavior on Compaq AP400 (2xPIII 700MHz). The problem disappeared when I disconnect the mouse. May be this can help your :) On 23 Nov 2005, at 21:37, Pete French wrote:> Having successfully upgraded one system in-place from 5.4 to 6.0 I > had a go > at the second system today. This is an old Compaq proliant 1600R with > two 500mhz pentium3's in it. Currently running 5.4 quite happily. > > so I buildworld, buildkernel, insall kernel and rebooot to check that > the kernel works... > > ...and the new kernel will not boot past the point where it says > atkdb0: [GIANT LOCKED] > > (under 5.4 the next thing I get is psm0 for the mouse.) > > My kernel is (almost) a generic SMP one - the only changes are that I > have removed INET6 and all CPU's apart from I686_CPU. > > I have tried booting this in 'safe' mode, and sevarl other options > from > the beatsie menu, but no dice. I havent yet tried a straight 'GENERIC' > kernel, and given the time of night wont be able to until tomorrow, > but > am very puzzled as I havent seen anything like this before. > > Does anyone have any hints or suggestions as to what I might try ? > > -pcf. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org"
> I have the same behavior on Compaq AP400 (2xPIII 700MHz). > The problem disappeared when I disconnect the mouse.Ah! Now that is worth knowing - I didnt even think of trying that. So does anyone know why the mouse being connected causes it to not boot ? I can rebuild the kernel without the mouse driver, that might help... thanks, -pcf.
On Fri, 25 Nov 2005 01:18 am, Pete French wrote:> > I have the same behavior on Compaq AP400 (2xPIII 700MHz). > > The problem disappeared when I disconnect the mouse. > > Ah! Now that is worth knowing - I didnt even think of trying that. > So does anyone know why the mouse being connected causes it to not > boot ? > > I can rebuild the kernel without the mouse driver, that might help...We have an array of new ASUS machine connected through a KVM. These machines panic when the kernel is probing for the mouse if ACPI is not loaded. If a mouse is not plugged in, no panic. If ACPI is loaded and the mouse is plugged in, it boots fine. Paul.
> We have an array of new ASUS machine connected through a KVM. These > machines panic when the kernel is probing for the mouse if ACPI is not > loaded. If a mouse is not plugged in, no panic. If ACPI is loaded and > the mouse is plugged in, it boots fine.I didnt try ACPI. I merely took the ouse driiver out of the kernel. Interestingly this then let me boot single user, but would not boot multi user! I had to physically unplug the mouse in the end. Shall file a PR (unless someone else already did?) -pcf.
On Fri, 25 Nov 2005 09:01 pm, Pete French wrote:> > We have an array of new ASUS machine connected through a KVM. > > These machines panic when the kernel is probing for the mouse if > > ACPI is not loaded. If a mouse is not plugged in, no panic. If > > ACPI is loaded and the mouse is plugged in, it boots fine. > > I didnt try ACPI. I merely took the ouse driiver out of the kernel. > Interestingly this then let me boot single user, but would not boot > multi user! I had to physically unplug the mouse in the end. > > Shall file a PR (unless someone else already did?)For the ASUS machines, we think it is already covered in PR i386/69750. Paul.
Hi Pete!> > We have an array of new ASUS machine connected through a KVM. These > > machines panic when the kernel is probing for the mouse if ACPI is not > > loaded. If a mouse is not plugged in, no panic. If ACPI is loaded and > > the mouse is plugged in, it boots fine. > > I didnt try ACPI. I merely took the ouse driiver out of the kernel. > Interestingly this then let me boot single user, but would not boot multi > user! I had to physically unplug the mouse in the end.Is there any chance that the very mouse is not working correctly? What if you change the device and try again? Best regards Zoran
> Is there any chance that the very mouse > is not working correctly? What if you change > the device and try again?very unlikely I would think - the mouse works correclt if thr machine run FreeBSD 5 or FreeBSD 5, and also under Windows2000 (it is connected via a KVM). Also someone else reported the same problem, also on Compaq hardware. If I get a moment to rebooot the system I will try with a different mouse, however. -pete.