5.4-RCx "jumping to kernel entry" hang on Ultra1/2/30
royce at alaska.net
Fri Apr 29 10:13:11 PDT 2005
On 4/29/2005 8:39 AM, Marcel Moolenaar wrote:
> On Apr 29, 2005, at 8:25 AM, Royce Williams wrote:
>> On Thu, 28 Apr 2005 15:19:14 -0400, Ken Smith wrote:
>>> On Thu, 2005-04-28 at 11:02 -0800, Royce Williams wrote:
>>>> Would it be too much trouble to ask for a boot-only as well? Some
>>>> us have limited bandwidth.
>>> MD5 (5.4-RC3-p1-sparc64-bootonly.iso) = e68f59a41eaa458c365cbe6edd4f7d86
>> This ISO consistently gets me past the hang on my Ultra30 when on
>> serial A. Full boot output attached so that other testers may
>> reference it.
>> Ken, Marcel -- thanks very much! I hope that Gavin's issue can also
>> be resolved.
> Ok, now I'm officially in a state of severe confusion. The patch I had
> an issue with the Zilog Z8530 SCC. The dmesg(8) you attached shows that you
> don't have one. You have a Siemens SAB82532 SCC and 2 16550's. It
> doesn't add
> up. Did you attach the right dmesg(8)? Did the RC3-p1 ISO contain other
> changes that happened to fix your problem? Is your problem really fixed or
> were you just lucky?
I just double-checked by booting again. That's definitely my Ultra 30,
and I'm definitely using Ken's -p1 ISO, downloaded from ftp4 this morning
Here's a fresh paste from a fresh boot (note that this is straight from
the console at boot):
FreeBSD 5.4-RC3 #1: Thu Apr 28 13:53:28 UTC 2005
root at binkley.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
uart0: <SAB 82532 v3.2, channel A> on puc0
uart0: CTS oflow
uart0: console (9600,n,8,1)
uart1: <SAB 82532 v3.2, channel B> on puc0
uart1: CTS oflow
uart2: <16550 or compatible> addr 0x14003083f8-0x14003083ff irq 41 on ebus0
uart3: <16550 or compatible> addr 0x14003062f8-0x14003062ff irq 42 on ebus0
Marcel, I don't know if anything else besides your changes went into
the ISO, but I doubt it -- Ken, can you confirm?
I booted three times from the -p1 ISO and didn't get the lockup. I was
in a hurry this morning and did not have time to follow this up with
separate testing of the old ISO. I suppose it's possible that something
else made my problem go away. I can test the vanilla 5.4-RC3 ISO again
when I get home.
Dieter and Gheorghe both reported the same problem on different
hardware; I'd be curious to see their test results and dmesg.
Incidentally, that "stray vector" error I mentioned at the outset is
showing up right after the "jumping to kernel entry 0xc0040000." :
stray vector interrupt 2029
I have no idea if this is related in any way.
Royce D. Williams - IP Engineering, ACS
personal: [first]@alaska.net - PGP: 3FC087DB/1776A531
work: [first.last]@acsalaska.net - http://www.tycho.org/royce/
More information about the freebsd-sparc64