Re: Kernel built with new GCC panics immediately

2003-07-11 Thread Shizuka Kudo
--- Lukas Ertl [EMAIL PROTECTED] wrote: Hi there, just wanted to report that a kernel built with the new gcc panics immediately when booting. I've seen this on two machines. Panic and reboot happens fast that I couldn't get the panic message. Same here for an AMD Athlon a Pentium III. The

gcc 3.3.1

2003-07-11 Thread Sergey Matveychuk
Don't forget bump __FreeBSD_version. :) Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

setting CPUTYPE=p4 with gcc-3.3

2003-07-11 Thread Glenn Johnson
Is it safe to set CPUTYPE to p4 for those with p4 processors now that gcc has been upgraded to 3.3 in -CURRENT? If so, should this be set up accordingly in bsd.cpu.mk? -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list

Re: [acpi-jp 2393] Re: Updated ec-burst.diff patch

2003-07-11 Thread Anish Mistry
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Attached is some hokey magic, which will cause your system to panic if you have a device plugged in a being access when you go into suspend. The panic will be on resume. I think it is because the usb interrupts change at least that is what i

Re: nvidia-driver database?

2003-07-11 Thread Munish Chopra
On 2003-07-11 20:48 +, Evan Dower wrote: We've been posting our success stories and problems for a few days now. Has anybody tried to compile these sorts of things into some sort of database? Maybe something keeping track of hardware, configuration details, and performance (success or

Regarding VMWare 3.0 Port and an odd bug that i've been gettingover and over again...

2003-07-11 Thread Scott M. Likens
I've been using VMWare in 5.1-RELEASE for quite some time and such, and have ALWAYS gotten this bug and haven't been able to figure out exactly why it does this, but it requires me to reboot. Anyhow here's the layout of the system. P3 800Mhz with 512meg of SDRAM AHA 2940U2W, Dual 17Gig Ultra

[-CURRENT tinderbox] failure on alpha/alpha

2003-07-11 Thread Tinderbox
TB --- 2003-07-12 04:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-12 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-12 04:04:21 - building world TB --- cd

Re: setting CPUTYPE=p4 with gcc-3.3

2003-07-11 Thread Kris Kennaway
On Fri, Jul 11, 2003 at 09:10:14PM -0500, Glenn Johnson wrote: Is it safe to set CPUTYPE to p4 for those with p4 processors now that gcc has been upgraded to 3.3 in -CURRENT? Compile some of the code that was known to be bad (see the archives for extensive discussion) and tell us :) Kris

[-CURRENT tinderbox] failure on amd64/amd64

2003-07-11 Thread Tinderbox
TB --- 2003-07-12 04:49:24 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-07-12 04:49:24 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-12 04:51:54 - building world TB --- cd