dumpdev default

2012-01-16 Thread Aristedes Maniatis
The manual states that dumpdev "AUTO is the default as of FreeBSD 6.0" [1] However: # uname -a FreeBSD xx 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # grep dumpdev /etc/defaults/rc.conf dumpdev="NO"

Re: Certain Registers in amd64 Unavailable to Developers

2012-01-16 Thread Shawn Webb
Nevermind. It's rdi and rsi that I should use. Sorry for the wasted bandwidth. ;) Thanks, Shawn On Mon, Jan 16, 2012 at 7:41 PM, Shawn Webb wrote: > Hey stable@, > > First off, I'm not too sure if this is the right mailing list (maybe > freebsd-hackers@?). Sorry if it is. This is just the maili

Certain Registers in amd64 Unavailable to Developers

2012-01-16 Thread Shawn Webb
Hey stable@, First off, I'm not too sure if this is the right mailing list (maybe freebsd-hackers@?). Sorry if it is. This is just the mailing list I subscribe to, so I thought I'd start here. Anyways, I'm looking at the regs struct (machine/reg.h) on FreeBSD 9-stable amd64. It appears that struc

Re: Reading from CDROM broken on 9.0-RELEASE/sparc64

2012-01-16 Thread C. P. Ghost
On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote: > Hello, > > I think that reading from CDROM is actually broken > in 9.0-RELEASE/sparc64. > > On FreeBSD 8.2-RELEASE/sparc64, mounting a physical > CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso > and running sha256 on usr/freebsd-dist/*

"xpt_config still waiting" solved: bad disk

2012-01-16 Thread freebsd-stable
Hi.. I just wanted to report a bug with FreeBSD 8.2-RELEASE-p5, as packaged with FreeNAS 8.0.3. A hard drive failed in a strange way, in that it was detected by the computer's BIOS and firmware, but did not reply to information requests from the kernel. The boot process stopped with a series of

Re: Can't boot 9.0-RELEASE on sparc64

2012-01-16 Thread C. P. Ghost
On Mon, Jan 16, 2012 at 11:07 PM, Kurt Lidl wrote: > I noted that booting off a cdrom image was broken for the 9.0-RC3 images > as well: > > http://lists.freebsd.org/pipermail/freebsd-current/2011-December/030747.html > > There was no followup. > > I've since managed to netboot that machine from t

Can't boot 9.0-RELEASE on sparc64

2012-01-16 Thread Kurt Lidl
I noted that booting off a cdrom image was broken for the 9.0-RC3 images as well: http://lists.freebsd.org/pipermail/freebsd-current/2011-December/030747.html There was no followup. I've since managed to netboot that machine from the 9.0 release, and get a 9.0-STABLE world built and installed o

Re: Reading from CDROM broken on 9.0-RELEASE/sparc64

2012-01-16 Thread C. P. Ghost
On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote: > Hello, > > I think that reading from CDROM is actually broken > in 9.0-RELEASE/sparc64. > > On FreeBSD 8.2-RELEASE/sparc64, mounting a physical > CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso > and running sha256 on usr/freebsd-dist/*

Reading from CDROM broken on 9.0-RELEASE/sparc64

2012-01-16 Thread C. P. Ghost
Hello, I think that reading from CDROM is actually broken in 9.0-RELEASE/sparc64. On FreeBSD 8.2-RELEASE/sparc64, mounting a physical CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso and running sha256 on usr/freebsd-dist/*.txz yields the same results as listed in usr/freebsd-dist/MANIFEST