Announcing snapshots.se.freebsd.org - now with AMD64 snapshots

[John Baldwin]

On Monday 26 July 2004 04:10 am, Poul-Henning Kamp wrote:
> In message <20040725214004.GA63752 at freebie.xs4all.nl>, Wilko Bulte writes:
> >On Sun, Jul 25, 2004 at 11:33:37PM +0200, Poul-Henning Kamp wrote:
> >> In message <20040725053409.GY2959 at sirius.firepipe.net>, Will Andrews 
writes:
> >> >The site also builds i386 and alpha snapshots every day.
> >> >Although I admit I haven't been able to figure out what's wrong
> >> >with the alpha snaps (they haven't worked since March)...
> >>
> >> I tried to get my alpha live so I could test tty patches on it
> >> but gave up.  5.2.1-R gave the same error as a snapshot from
> >> .jp and it looks to me like the machine doesn't even want to
> >> recognize the CD as bootable.
> >
> >There is some outstanding issue with the loader on alpha (toolchain
> >related as I understand it) but that should not keep it from getting
> >to the 1st stage boot.
>
> Actually I remembered wrong.
>
> The jp snapshot gave this:
> 	block 0 of dka100.1.0.2000.0 is not a valid boot block

There was an issue where cross-built bsdlabel's wouldn't write out the SRM 
checksum and boot info that I fixed a while ago.  It maybe that the jp 
machines need to update to a newer world.

> Whereas 5.2.1 gave this:
>
> 	cia0: extended capabilities: 21<DWEN,BWEN>
> 	pcib0: <2117x PCI host bus adapter> on cia0
> 	pci0: <PCI bus> on pcib0
> 	eisab0: <PCI-EISA bridge> at device 7.0 on pci0
>
> 	halted CPU 0
>
> 	halt code = 7
> 	machine check while in PAL mode
> 	PC = 18100

This may mean that the eisa probe needs to be less destructive.  Perhaps using 
a kernel w/o the eisa device would work better.

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org