5.1-RELEASE TODO

2003-06-01 Thread Robert Watson
This is an automated bi-daily mailing of the FreeBSD 5.1 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.1R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.1. FreeBSD 5.1

Re: Native JDK with libthr/libkse

2003-06-01 Thread Daniel Eischen
On Sat, 31 May 2003, Dag-Erling Smorgrav wrote: Daniel Eischen [EMAIL PROTECTED] writes: What are the above error messages? Sorry, I've never been able to build native java for FreeBSD. # cd /usr/ports/java/jdk13 # make install clean That's what I meant; it didn't work for me. It got

mailing list

2003-06-01 Thread Klaus Mahsarski
___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD 5.1-BETA2 boot up messages

2003-06-01 Thread Valentin Nechayev
Fri, May 30, 2003 at 18:53:16, segr (Stephane Raimbault) wrote about FreeBSD 5.1-BETA2 boot up messages: SR I just noticed that when I boot up in FreeBSD 5.1-BETA2 I get a whole bunch of SR messages fly by the screen (see below for errors from /var/log/messages). SR Does anyone know what is

Re: Libthr stable enough for testing

2003-06-01 Thread Valentin Nechayev
Fri, May 30, 2003 at 17:38:04, larse (Lars Eggert) wrote about Re: Libthr stable enough for testing: LE I tried, but the following is a surefire way to freeze my SMP box solid LE at the moment (with today's libthr): SCHED_ULE or SCHED_4BSD? -netch-

Re: Libthr stable enough for testing

2003-06-01 Thread Lars Eggert
Valentin Nechayev wrote: Fri, May 30, 2003 at 17:38:04, larse (Lars Eggert) wrote about Re: Libthr stable enough for testing: LE I tried, but the following is a surefire way to freeze my SMP box solid LE at the moment (with today's libthr): SCHED_ULE or SCHED_4BSD? SCHED_4BSD -- Lars Eggert

[-CURRENT tinderbox] failure on i386/pc98

2003-06-01 Thread Tinderbox
TB --- 2003-05-31 18:52:11 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-05-31 18:52:11 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-05-31 18:54:44 - building world TB --- cd

[-CURRENT tinderbox] failure on ia64/ia64

2003-06-01 Thread Tinderbox
TB --- 2003-05-31 19:06:48 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-05-31 19:06:48 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-05-31 19:08:27 - building world TB --- cd

[-CURRENT tinderbox] failure on sparc64/sparc64

2003-06-01 Thread Tinderbox
TB --- 2003-05-31 19:21:20 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-05-31 19:21:20 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-05-31 19:23:04 - building world TB

HEADSDOWN: You can take me out of your .procmailrc now.

2003-06-01 Thread Poul-Henning Kamp
I have flushed my integration tree now for all but three patches which are subject to various special handlings. Sorry about the commit-storm, but I didn't feel like dumping it all into one commit (What I did during code freeze). And now, back to the real substantial stuff in the other trees

viapropm doesnt like sys/dev/pci.c rev 1.214

2003-06-01 Thread David P. Reese Jr.
In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG and comparing the results. For some odd reason, this doesnt work when my viapropm tries to attach. Allocating its port resources fails in

Re: 5.1-RELEASE TODO

2003-06-01 Thread Luigi Rizzo
On Sat, May 31, 2003 at 09:00:16AM -0400, Robert Watson wrote: This is an automated bi-daily mailing of the FreeBSD 5.1 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.1R/todo.html Automated mailing of this list will continue through

USB Quirk Patch: SanDisk ImageMate CF SDDR31 (V:0x0781, P:0x0002)

2003-06-01 Thread Sean Kelly
Whenever I plug my SanDisk SDDR31 CF reader into my 5.1-BETA system, I am told that the device doesn't support Get Max Lun. I have added a USB quirk to my kernel to fix this, and it seems to work perfectly. I would appreciate if somebody would consider adding this before 5.2-RELEASE. umass0:

Re: Native JDK with libthr/libkse

2003-06-01 Thread Eivind Olsen
--On 31. mai 2003 11:22 -0400 Daniel Eischen [EMAIL PROTECTED] wrote: That's what I meant; it didn't work for me. It got pretty far through the build but seemed to run out of some sort of resource. I couldn't tell by the error message what it was, and I don't have the log anymore. The last time I

make errors in 5.1 beta 2 due to faulty mobo or pwr supply

2003-06-01 Thread FreeBSD_Guy
in a prior post, I reported after a fresh kernel developer install from the x86 5.1 beta 2 ISO, i successfully configured the network and ping a domain name. Then I attempted to install /usr/ports/net/cvsup-without-gui. This fails and repeated attempts provide differing failures. output

Re: Native JDK with libthr/libkse

2003-06-01 Thread Christopher Johnson
On Sat, 31 May 2003, Dag-Erling Smorgrav wrote: Daniel Eischen [EMAIL PROTECTED] writes: What are the above error messages? Sorry, I've never been able to build native java for FreeBSD. # cd /usr/ports/java/jdk13 # make install clean DES I disagree. I recently built jdk13 on

Re: Native JDK with libthr/libkse

2003-06-01 Thread Dag-Erling Smorgrav
Christopher Johnson [EMAIL PROTECTED] writes: On Sat, 31 May 2003, Dag-Erling Smorgrav wrote: Daniel Eischen [EMAIL PROTECTED] writes: What are the above error messages? Sorry, I've never been able to build native java for FreeBSD. # cd /usr/ports/java/jdk13 # make install clean I

FreeBSD 5.1 Release: Enlightenment BUS ERROR

2003-06-01 Thread FreeBSD_Guy
FreeBSD 5.1 Release Enlightenment BUS ERROR all actions performed as root installed 5.1 beta 2 installed bash from ports then cvsuped to 5.1 release then from ports installed xfree86, enlightenment, eterm, all with out problems. While compiling mozilla from one login, i logged in again on

Re: viapropm doesnt like sys/dev/pci.c rev 1.214

2003-06-01 Thread M. Warner Losh
In message: [EMAIL PROTECTED] David P. Reese Jr. [EMAIL PROTECTED] writes: : Is it my chipset's fault for not reading back the correct register value? : The board is a SOYO K7VTAPRO-2AA6. What other info would be helpful in : this situation? It appears that there's some non-zero

Re: viapropm doesnt like sys/dev/pci.c rev 1.214

2003-06-01 Thread Dag-Erling Smorgrav
David P. Reese Jr. [EMAIL PROTECTED] writes: In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG and comparing the results. For some odd reason, this doesnt work when my viapropm tries to attach. viapropm is

Re: 5.1-RELEASE TODO

2003-06-01 Thread Scott Long
Luigi Rizzo wrote: On Sat, May 31, 2003 at 09:00:16AM -0400, Robert Watson wrote: This is an automated bi-daily mailing of the FreeBSD 5.1 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.1R/todo.html Automated mailing of this list will

Re: 5.1-RELEASE TODO

2003-06-01 Thread Robert Watson
On Sat, 31 May 2003, Scott Long wrote: It's been a matter of not having enough time, nothing more. I *will* address this one way or another before the release. I apologize for taking so long. Ditto, here, unfortunately. I managed to hose my sparc64 box a couple of weeks ago trying to

Re: 5.1-RELEASE TODO

2003-06-01 Thread Bruce A. Mah
If memory serves me right, Scott Long wrote: It's been a matter of not having enough time, nothing more. I *will* address this one way or another before the release. I apologize for taking so long. Scott, you're hardly the only person with the ability to test this problem. In fact, you're

Re: 5.1-RELEASE TODO

2003-06-01 Thread Bernd Walter
On Sat, May 31, 2003 at 02:24:59PM -0700, Luigi Rizzo wrote: On Sat, May 31, 2003 at 09:00:16AM -0400, Robert Watson wrote: ++ | Issue | Status| Responsible | Description |

viapm attach failure (was Re: loader vs PCI)

2003-06-01 Thread Conrad Sabatier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20-May-2003 Julian Elischer wrote: Is there any capability in the loader to do such things as get/set a PCI config space register? Looking at the man page I'd say not, but there is mention of some PNP capacity (though not currently

Re: 5.1-RELEASE TODO

2003-06-01 Thread Luigi Rizzo
On Sat, May 31, 2003 at 08:18:10PM -0400, Robert Watson wrote: On Sat, 31 May 2003, Scott Long wrote: It's been a matter of not having enough time, nothing more. I *will* address this one way or another before the release. I apologize for taking so long. Ditto, here, unfortunately.

Re: 5.1-RELEASE TODO

2003-06-01 Thread Bernd Walter
On Sat, May 31, 2003 at 05:39:58PM -0700, Luigi Rizzo wrote: On Sat, May 31, 2003 at 08:18:10PM -0400, Robert Watson wrote: On Sat, 31 May 2003, Scott Long wrote: It's been a matter of not having enough time, nothing more. I *will* address this one way or another before the release.

Re: viapropm doesnt like sys/dev/pci.c rev 1.214

2003-06-01 Thread David P. Reese Jr.
On Sun, Jun 01, 2003 at 01:52:57AM +0200, Dag-Erling Smorgrav wrote: David P. Reese Jr. [EMAIL PROTECTED] writes: In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG and comparing the results. For some odd

Re: Native JDK with libthr/libkse

2003-06-01 Thread Daniel Eischen
On Sun, 1 Jun 2003, Dag-Erling Smorgrav wrote: Christopher Johnson [EMAIL PROTECTED] writes: On Sat, 31 May 2003, Dag-Erling Smorgrav wrote: Daniel Eischen [EMAIL PROTECTED] writes: What are the above error messages? Sorry, I've never been able to build native java for FreeBSD.

BOOTP_NFSV3

2003-06-01 Thread David Yeske
I have a suggestion to deprecate the BOOTP_NFSV3 option, and I wanted to get some feedback. If NFS_ROOT and BOOTP_NFSV3 are defined, then it is a noop in sys/i386/i386/locore.s? If NFS_ROOT is defined and BOOTP_NFSV3 is undefined then it copies in a nfs_diskless structure in

Fatal trap on RELENG_5_1 SMP

2003-06-01 Thread Magnus J
Hello everyone I'm getting a fatal trap when I do 'shutdown' on an SMP-box that I did cvsup on RELENG_5_1 yesterday. 'reboot' works without any problems. This is the message: Fatal trap 12: page fault while in kernel mode cpuid=1; lapic.id = 0100 fault virtual address = 0x0 fault code

vm-related panic with 5.1RC1

2003-06-01 Thread Martin Blapp
Hi all, I just got this panic during compile of openoffice Fatal trap 12 while in kernel mode fault virtual address = 0x68 fault code= supervisor read, page not present instruction pointer = 0x8:0xc0271f4d stack pointer = 0x10:0xe6e51ab0 frame pointer =

Re: Native JDK with libthr/libkse

2003-06-01 Thread Sheldon Hearn
On (2003/06/01 00:50), Daniel Eischen wrote: I just built jdk13 a couple of days ago. No problem whatsoever. You guys must have rotten karma or something. Did you already have a native JDK installed? I built the native 1.4.1 JDK two weeks ago, first without the native JDK for

vm-related panic with 5.1RC1

2003-06-01 Thread Martin Blapp
Hi all, I just got this panic during compile of openoffice Fatal trap 12 while in kernel mode fault virtual address = 0x68 fault code= supervisor read, page not present instruction pointer = 0x8:0xc0271f4d stack pointer = 0x10:0xe6e51ab0 frame pointer =

Re: 5.1-RELEASE TODO

2003-06-01 Thread Luigi Rizzo
On Sun, Jun 01, 2003 at 03:32:56AM +0200, Bernd Walter wrote: ... :) And I hoped a programmer who knows the source could find out and fix very quickly. sorry, i missed the offending line number in your previous email. I think i missed a in all the first arguments to bcopy in the

Re: 5.1-RELEASE TODO

2003-06-01 Thread Richard Arends
On Sat, 31 May 2003, Robert Watson wrote: |---++---+---| | || | The recently upgraded | | || | if_wi driver is more | |

vnode locking problem in pseudofs/procfs

2003-06-01 Thread Don Lewis
I just stumbled across this vnode locking problem in procfs() db tr Debugger(c05215d4,c0520b94,c669b000,c0521615,e6d77764) at Debugger+0x54 vfs_badlock(c0521615,c0520b94,c669b000,c05b4340,c669b000) at vfs_badlock+0x45 assert_vop_locked(c669b000,c0520b94,c0520adf,358,c6a35400) at

Re: Native JDK with libthr/libkse

2003-06-01 Thread Dag-Erling Smorgrav
Daniel Eischen [EMAIL PROTECTED] writes: On Sun, 1 Jun 2003, Dag-Erling Smorgrav wrote: I just built jdk13 a couple of days ago. No problem whatsoever. You guys must have rotten karma or something. Did you already have a native JDK installed? No. I used linux-sun-jdk13 to bootstrap. DES

halt thread / mmap chatter

2003-06-01 Thread Petri Helenius
Got the chatter below on a box which had some libkse and some mmap activity when it got shutdown. Built from morning of 30th May sources. Pete May 30 08:56:08 kompak halt: hallted by root ock order reversal 1st 0xc3335aa8 sigacts (sigacts) @ kern/subr_trap.c:248 2nd 0xc3347d88 process lock

raidframe

2003-06-01 Thread Petri Helenius
Is there anyone actually successfully using raidframe and if yes, what kind of hardware? Same question goes for any recent SCSI RAID controllers supported by FreeBSD. I admit not having tried all combinations but it seems that using anything else than simple ahc scsi stuff results in kernel panic

Re: raidframe

2003-06-01 Thread matt
I'm using a Ami MegaRaid 1500 in 5.x without any issues. -m On Sun, 1 Jun 2003, Petri Helenius wrote: Is there anyone actually successfully using raidframe and if yes, what kind of hardware? Same question goes for any recent SCSI RAID controllers supported by FreeBSD. I admit not

fdisk/disklabel - Error: unable to write data to disk ad0

2003-06-01 Thread Herbert
Hei! On Thursday May 29th I installed FreeBSD 5.1 Beta2. The next day I've update to CURRENT from May 30th. I have a 60 GB ATA harddisk and during installation I created only 1 20 GB slice for FreeBSD. Today I wanted to use the other 40 GB of my hard disk and create two more slices each 20 GB.