Configuration:
JumpStart! 1.1 and DS10.
>>> show version
V5.8-10 Aug 21 2000 16:20:43
Background:
I've got two DS10 from Compaq connected
to
a 8 port Compaq console switch. When
I reboot the system I lose the ability
to use the PrintScrn key to switch
between the two. I have to press the
reset
button on the console switch to regain
the console switch menu.
Problem:
But if I do this while booting the
JumpStart! 1.1
CD I get the following error immediately
following
the console switch reset:
pc_keyb.c:811 spinlock stuck in swapper
at fffffc000043e76c(0)
owner swapper at fffffc000043e244(0)
pc_keyb.c:479
Workaround:
Don't press the reset button on the
console switch
while using the JumpStart! 1.1 CD.
Christian Rosnes
christian@cellus.no
Logged In: YES
user_id=294675
I think what's happening here is that the system is sensing
the "disappearance" of the keyboard when you hit the reset
switch
(the switch box sends the system the appropriate signals
that indicate it has a keyboard attached, and when you hit
the reset, the
signals stop), and it gets confused. I've seen this in our
lab, myself; we have several machines tied together with a
switch box,
and if I reset it during the boot, I get a message like
this. I'll take a look, but I think pc_keyb.c is part of the
standard C library, and
not part of JumpStart itself.
Logged In: YES
user_id=294675
I wanted to follow up again, as something caught my
attention; when you say that you lose the ability to use the
PrintScrn switch, is that permanent, or just during the
reboot process? I know we've seen something similar before,
and I just wanted to clarify that; I think the system that's
rebooting gets control of the box and doesn't let go until
it's finished rebooting, but I thought it released it
afterward, and I wanted to see if that was your experience
with this.
Regards,
Mike Lease,
Alpha Technology Solutions Group
mike.lease@compaq.com
Logged In: YES
user_id=294675
Hello again,
I'd just like to check in and see if my comments helped. If
I don't hear back from you within a couple of weeks, I'll
assume we can close this bug.
Regards,
Mike Lease,
ATSG