RE: lockmgr panic on shutdown

2003-11-01 Thread Bruce Evans
On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote: > The obvious solution might be to change line 1161 of ffs_vfsops to > pass vget() "curthread" rather than td. I assume there's a good > reason why "thread0" is passed from boot(), but I can't see why > that's of any use to the vnode locking. Passing &t

Re: Dualbooting STABLE & CURRENT

2003-11-01 Thread Steve Wingate
> > I don't like the sound of that. I'll just stick with STABLE until 5.x is > > really ready. > > -STABLE will have the same problem since its in boot0 and the BIOS, not > the OS on the partition its trying to boot. Actually STABLE will have no problems as it's been running on this box for over a

Re: Dualbooting STABLE & CURRENT

2003-11-01 Thread Doug White
On Sat, 1 Nov 2003, Steve Wingate wrote: > > "Nothing happens" probably means "its beeping but I can't hear it" :) > > > > If that happens, its because boot0 and the BIOS can't figure out how to > > reach the partition, generally because the geometry is wrong. Try zeroing > > off the front end of

RE: lockmgr panic on shutdown

2003-11-01 Thread Doug White
On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote: > >> For giggles I'm rolling back vfs_default.c back to 1.87 since its along > >> the backtrace path. > > > >This didn't work so -CURRENT is fully broke. > > > >I'd suggest staying on 10/30 not before 4PM PST if you want to not crash > >on shutdown. > >

Re: Dualbooting STABLE & CURRENT

2003-11-01 Thread Steve Wingate
> "Nothing happens" probably means "its beeping but I can't hear it" :) > > If that happens, its because boot0 and the BIOS can't figure out how to > reach the partition, generally because the geometry is wrong. Try zeroing > off the front end of the disk, partitioning it with DOS FDISK, then put

Re: Forward: HEADS UP! Default value of ip6_v6only changed

2003-11-01 Thread Eugene M. Kim
Michael Nottebrock wrote: Christian Weisgerber wrote: If we ship with a default of v6only off, then people will not fix software to open two sockets. This in turn means that turning v6only on will break this software. I find the notion of making people "fix" their software to not rely on RFC

RE: lockmgr panic on shutdown

2003-11-01 Thread peter . edwards
>> For giggles I'm rolling back vfs_default.c back to 1.87 since its along >> the backtrace path. > >This didn't work so -CURRENT is fully broke. > >I'd suggest staying on 10/30 not before 4PM PST if you want to not crash >on shutdown. > The patch worked for me. (Well, a slightly modified one: I

RE: lockmgr panic on shutdown

2003-11-01 Thread Doug White
On Sat, 1 Nov 2003, Doug White wrote: > For giggles I'm rolling back vfs_default.c back to 1.87 since its along > the backtrace path. This didn't work so -CURRENT is fully broke. I'd suggest staying on 10/30 not before 4PM PST if you want to not crash on shutdown. > > I suspect I'll need to bac

RE: lockmgr panic on shutdown

2003-11-01 Thread Doug White
For giggles I'm rolling back vfs_default.c back to 1.87 since its along the backtrace path. I suspect I'll need to back up the whole thing to before the commit for the struct mount locking until jeff & kan can straighten things out. On Sun, 2 Nov 2003 [EMAIL PROTECTED] wrote: > > > >I can confir

RE: lockmgr panic on shutdown

2003-11-01 Thread peter . edwards
>I can confirm the lockmgr panic on shutdown reported by someone else >earlier (whose message I mistakenly deleted). > >It looks like swapper is trying to undo a lock from pagedaemon and runs >into trouble. This is probably related to the Giant pushdown of >vm_pageout() that alc did last week. >

Re: lockmgr panic on shutdown

2003-11-01 Thread Doug White
More info. I think this is actually related to kan's reversion of src/sys/kern/vfs_default.c. I'm trying rev 1.88 of that file. In the meantime, here is the panic message and backtrace. I have a crashdump if desired. panic: lockmgr: thread 0xc493be40, not exclusive lock holder 0xc071f320 unlock

pthread_mutex_lock crashed

2003-11-01 Thread Sergey Matveychuk
Hello! I've tested MICO port (CORBA implementation) both on -stable and -current. I use lang/gcc33 port for -stable. On -stable all goes right, but on -current one example crashed in pthread_mutex_lock(). Here is gdb back tracing: #0 0x280830c9 in _atomic_lock () from /usr/lib/libc_r.so.5 #1

lockmgr panic on shutdown

2003-11-01 Thread Doug White
I can confirm the lockmgr panic on shutdown reported by someone else earlier (whose message I mistakenly deleted). It looks like swapper is trying to undo a lock from pagedaemon and runs into trouble. This is probably related to the Giant pushdown of vm_pageout() that alc did last week. I'm build

Re: Dualbooting STABLE & CURRENT

2003-11-01 Thread Doug White
On Sat, 1 Nov 2003, Steve Wingate wrote: > I need some help dual booting STABLE & CURRENT. I have two SCSI disks > with: > STABLE taking the entire first disk (works fine) > CURRENT taking the first 1/3 of the second disk and > backup data taking the remaining 2/3 of the second disk. > > I have in

Re: Dualbooting STABLE & CURRENT

2003-11-01 Thread Steve Wingate
> > Try to install booteasy from STABLE, only from STABLE, to both > harddisk. don't install booteasy when install CURRENT > or try to recover boot easy from STABLE on the second hardisk as > described in the handbook > it works for me > > sham khalil I have tried this and it still doesn't boot t

Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes: : Mensaje citado por "M. Warner Losh" <[EMAIL PROTECTED]>: : : | cvs update -PAd : | : | Pruning is very important. : : Warner, : : It hadn't even dawned on me but, after several days of suffering with this : problem, I couldn

Re: Dualbooting STABLE & CURRENT

2003-11-01 Thread Sham Khalil
On Sat, 1 Nov 2003, Steve Wingate wrote: > I need some help dual booting STABLE & CURRENT. I have two SCSI disks > with: > STABLE taking the entire first disk (works fine) > CURRENT taking the first 1/3 of the second disk and > backup data taking the remaining 2/3 of the second disk. > > I have

panic during shutdown in lockmgr()

2003-11-01 Thread Thorsten Greiner
Hi, with a -CURRENT kernel built today I am consistently getting a panic during shutdown. Unfortunately a debug kernel refuses to do a core dump, so I only have a naked stack trace: panic: lockmgr: thread 0xc1918720, not exclusive lock holder 0xc06b5660 unlocking #0 0xc04fc40a in doadump () #1

Re: jumbograms (& em) & nfs a no go

2003-11-01 Thread Barney Wolff
On Sat, Nov 01, 2003 at 01:09:07PM -0800, Terry Lambert wrote: > Barney Wolff wrote: > > > Implies the sending host is not honoring the MTU restriction when > > > deciding whether or not to frag packets. > > > > 67582 looks awfully bogus even as a pre-frag length. How could that come > > over the

Re: FreeBSD-CURRENT kernel hangs on starting KDE

2003-11-01 Thread Michael L. Squires
> System: FreeBSD 5.1-CURRENT i386 > > Relevant hardware config: > Mainboard : ASUS P4S533-E (SIS645DX north, SIS962/L south bridges) > Memory : PC2700 512MB DDR RAM (memtest86 tested) > VGA card : ATI RADEON 9000 PRO I had similar lockups with a SuperMicro P6DGH (dual PIII/850)/ATI All-in

[current tinderbox] failure on i386/pc98

2003-11-01 Thread Tinderbox
TB --- 2003-11-01 21:03:26 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-11-01 21:03:26 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-11-01 21:03:26 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs

FreeBSD-CURRENT kernel hangs on starting KDE

2003-11-01 Thread Tamás R.
I'm sorry for my previous e-mail, I hope it will look better :) Some months ago I installed a FreeBSD-current system on my desktop computer. I use the KDE desktop environment and I compiled really everything from ports. I periodically maintain it so my system is up-to-date. I have been experiencin

FreeBSD-CURRENT kernel hangs on starting KDE

2003-11-01 Thread Tamás R.
Hi, Some months ago I installed a FreeBSD-current system on my desktop computer. I use the KDE desktop environment and I compiled really everything from ports. I periodically maintain it so my system is up-to-date. I have been experiencing a problem with FreeBSD-current kernel all the time. Som

Dualbooting STABLE & CURRENT

2003-11-01 Thread Steve Wingate
I need some help dual booting STABLE & CURRENT. I have two SCSI disks with: STABLE taking the entire first disk (works fine) CURRENT taking the first 1/3 of the second disk and backup data taking the remaining 2/3 of the second disk. I have installed CURRENT (at least 8 times) but I cannot get it

Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
Mensaje citado por "M. Warner Losh" <[EMAIL PROTECTED]>: | cvs update -PAd | | Pruning is very important. Warner, It hadn't even dawned on me but, after several days of suffering with this problem, I couldn't agree more. I am converted, believe me. I will be doing that more often. I've become

Re: jumbograms (& em) & nfs a no go

2003-11-01 Thread Terry Lambert
Barney Wolff wrote: > > Implies the sending host is not honoring the MTU restriction when > > deciding whether or not to frag packets. > > 67582 looks awfully bogus even as a pre-frag length. How could that come > over the wire? The sending host is not honoring the MTU restriction? 8-) 8-). Mo

Re: ata and mfs problems

2003-11-01 Thread Soren Schmidt
It seems Sven Esbjerg wrote: > On my Fujitsu-Siemens S-4572 I get random hangs when doing recursive copying > to af mfs device. I suspect it has something to do with the fact the I still > get a lot of spurious interrupst on the ata controller. Those spurious interrupts are because ata1 share irq1

Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
Mensaje citado por Jean-Marc Zucconi <[EMAIL PROTECTED]>: | > eculp writes: | | > Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>: | > | On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote: | > | > I'm having problems with current buildworld in gnu now on two | differen

ata and mfs problems

2003-11-01 Thread Sven Esbjerg
On my Fujitsu-Siemens S-4572 I get random hangs when doing recursive copying to af mfs device. I suspect it has something to do with the fact the I still get a lot of spurious interrupst on the ata controller. I'm doing the following: dd if=/dev/zero of=mfsroot bs=1k count=25000 mdconfig -a -t vno

Re: jumbograms (& em) & nfs a no go

2003-11-01 Thread Tom
On Fri, 31 Oct 2003, Michal Mertl wrote: ... > > As I recall, when I used a crossover cable, I could not get the > > adapters to go to 1000, only 100. That might have been the cable, > > or not. > > I can confirm it works equally well with crossover as with straight cable. Depends usually. S

Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread M. Warner Losh
cvs update -PAd Pruning is very important. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread Jean-Marc Zucconi
> eculp writes: > Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>: > | On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote: > | > I'm having problems with current buildworld in gnu now on two different > | > machines in current(today). The latest is the following: >

Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>: | On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote: | > I'm having problems with current buildworld in gnu now on two different | > machines in current(today). The latest is the following: | > | > rm: tar: is a directory | >

Re: ACPI S1/S3 power states not working

2003-11-01 Thread YaShiTe
I'm using Motherboard based on VIA chipset and the S3 doesnt work correctly. On resume if there are X the system doesn't restart and without X the system resmumes but hangs few later. I'm using FreeBSD 5.1-CURRENT: Wed Oct 29 15:35:15 CET 2003 i386 On Sat, 1 Nov 2003 22:02:56 +0200 Aragon Gouve

ACPI S1/S3 power states not working

2003-11-01 Thread Aragon Gouveia
Hi, I'm using a Dell Inspiron 8000 running BIOS A22 (latest AFAIK) and FreeBSD 5.1-RELEASE. I've compiled a fixed DSDT following Stijn's instructions which did fix a bunch of errors during/after bootup. I'm trying to get some of the power saving states working but am having no luck and can't see

Re: buildworld error: rm: tar: is a directory

2003-11-01 Thread Ruslan Ermilov
On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote: > I'm having problems with current buildworld in gnu now on two different > machines in current(today). The latest is the following: > > rm: tar: is a directory > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/tar. > *** Error

[current tinderbox] failure on alpha/alpha

2003-11-01 Thread Tinderbox
TB --- 2003-11-01 17:00:01 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-11-01 17:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-11-01 17:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/

Re: Sysinstall's fdisk/disklabel should be improved

2003-11-01 Thread Valentin Nechayev
Wed, Oct 29, 2003 at 16:43:12, q (Ulrich Spoerlein) wrote about "Re: Sysinstall's fdisk/disklabel should be improved": >> It is NOT useless. Why do you think it is? Perhaps you don't relize >> that some BIOS's wont boot from a hard disk that isn't partitioned to >> agree with the specificatio

Re: Sysinstall's fdisk/disklabel should be improved

2003-11-01 Thread Valentin Nechayev
Sun, Oct 26, 2003 at 18:58:52, q (Ulrich Spoerlein) wrote about "Sysinstall's fdisk/disklabel should be improved": US> First of all, the Partition Editor has the 'A' option to use all of the US> available HDD space. It creates a DOS-compatible slice (starting at US> sector 63 and ending on cyli

if_xname, byte order and OpenBSD 3.4 + CARP

2003-11-01 Thread Max Laier
Hello, this just a short "yes, we are aware of things" message. As OpenBSD 3.4 was released three days ago, we will release pf 2.0 soon. However, before that can take place there are some issues that have to be resolved beforehand: 1) As you may know, Brooks Davis has finally brought if_xname t

Jail Hosting required

2003-11-01 Thread Dave Johnson
Hi Please can someone recommend a hosting service in the UK that can provide a Jail service for us. Please reply off list. Regards ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any ma

Re: CDDA with common programs (ATAng)

2003-11-01 Thread Arjan van Leeuwen
On Saturday 01 November 2003 16:54, Arjan van Leeuwen wrote: > On Saturday 01 November 2003 09:08, Harald Schmalzbauer wrote: > > Hi all, > > > > in the archive I found a discussion about some implementation changes > > with ATAng which breakes CDDA support for (all?) common programs. > > Will it e

Re: CDDA with common programs (ATAng)

2003-11-01 Thread Arjan van Leeuwen
On Saturday 01 November 2003 09:08, Harald Schmalzbauer wrote: > Hi all, > > in the archive I found a discussion about some implementation changes with > ATAng which breakes CDDA support for (all?) common programs. > Will it ever be possible to use FreeBSD with e.g. kaudiocreator (needs > cdparanoi

Re: problems with sysinstall

2003-11-01 Thread Valentin Nechayev
Wed, Oct 29, 2003 at 05:44:44, sem (Sergey Matveychuk) wrote about "problems with sysinstall": SM> The first one: when I install -current on disk where WinXP on first SM> slice, sysinstall brakes WinXP boot complete. I got 'Missing operation SM> system' everytime. Even I've tried 'fixboot' an

Re: problems with sysinstall

2003-11-01 Thread Valentin Nechayev
Wed, Oct 29, 2003 at 17:32:29, dwhite (Doug White) wrote about "Re: problems with sysinstall": >> Well, I understand it for slices. But why I can't create new partition >> in exist slice and newfs it? It was OK in -stable. DW> yes, this is a change to -current. It is for your own safety. Don't

5.2-RELEASE TODO

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

Re: problems with sysinstall

2003-11-01 Thread Janet Sullivan
Well, I understand it for slices. But why I can't create new partition in exist slice and newfs it? It was OK in -stable. yes, this is a change to -current. It is for your own safety. My own safety? I can down the system in a million ways, yet can't do what I actually want? A major reason I got f

Re: problems with sysinstall

2003-11-01 Thread David Taylor
On Wed, 29 Oct 2003, Doug White wrote: > On Wed, 29 Oct 2003, Sergey Matveychuk wrote: >> Doug White wrote: >>> This is normal and for your protection. you can't edit the disk you're >>> running off of. If you are running off of ad1, make sure 1) you're root >>> when you run sysinstall and b) you

Sticky mouse with SCHED_ULE 10-30-03

2003-11-01 Thread Schnoopay
> Are you using moused? Is this SMP or UP? What CPUs are you using? > > Thanks, > Jeff I am having similar problems after my last cvsup (10-31-03) also using a USB MS Intellimouse. Mouse is slow to respond under ULE but fine under 4BSD. The mouse feels like it's being sampled at a slow rate. I

[current tinderbox] failure on sparc64/sparc64

2003-11-01 Thread Tinderbox
TB --- 2003-11-01 11:51:26 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-11-01 11:51:26 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-11-01 11:51:26 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q

buildworld error: rm: tar: is a directory

2003-11-01 Thread eculp
I'm having problems with current buildworld in gnu now on two different machines in current(today). The latest is the following: rm: tar: is a directory *** Error code 1 Stop in /usr/src/gnu/usr.bin/tar. *** Error code 1 Stop in /usr/src/gnu/usr.bin/tar. *** Error code 1 Stop in /usr/src/gnu/u

[current tinderbox] failure on ia64/ia64

2003-11-01 Thread Tinderbox
TB --- 2003-11-01 10:17:16 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-11-01 10:17:16 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-11-01 10:17:16 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs

Re: NULL td passed to propagate_priority() when using xmms...

2003-11-01 Thread Soren Schmidt
It seems Sean Chittenden wrote: > Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but, > for those interested (this is using ule 1.67, rebuilding world now), > here's my stack. I couldn't figure out where td was being set to > NULL. :( Oh! Where is TD_SET_LOCK defined? egrep -r

[current tinderbox] failure on i386/pc98

2003-11-01 Thread Tinderbox
TB --- 2003-11-01 09:07:51 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-11-01 09:07:51 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-11-01 09:07:51 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs

[current tinderbox] failure on i386/i386

2003-11-01 Thread Tinderbox
TB --- 2003-11-01 07:42:04 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-11-01 07:42:04 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-11-01 07:42:04 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs

CDDA with common programs (ATAng)

2003-11-01 Thread Harald Schmalzbauer
Hi all, in the archive I found a discussion about some implementation changes with ATAng which breakes CDDA support for (all?) common programs. Will it ever be possible to use FreeBSD with e.g. kaudiocreator (needs cdparanoia)? I'm no friend of copying audiotracks by hand, give them a more or le