Re: strange umass/scsi behaviour

2003-07-30 Thread Nate Lawson
On Wed, 30 Jul 2003, John Hay wrote: Does anyone have an idea why the umass/scsi code behave differently between if you boot with a device already plugged in as opposed to plugging it in later? In my case it is a Sandisk Cruiser. If I plug it in before booting, it works just great, but if I

Re: strange umass/scsi behaviour

2003-07-30 Thread John Hay
On Tue, Jul 29, 2003 at 11:28:18PM -0700, Nate Lawson wrote: On Wed, 30 Jul 2003, John Hay wrote: Does anyone have an idea why the umass/scsi code behave differently between if you boot with a device already plugged in as opposed to plugging it in later? In my case it is a Sandisk Cruiser.

Re: STEP 2, fixing dhclient behaviour with multiple interfaces

2003-07-30 Thread Martin Blapp
Hi, Odd: %%% # cat /etc/sleep_dhclient #!/bin/sh omshell /dev/null EOF connect new control open set state = 3 update close EOF # cat /etc/wakeup_dhclient #!/bin/sh omshell /dev/null EOF connect new control open set state = 4 update close EOF %%% This was working

4.8-Current Depreciated files

2003-07-30 Thread Benjamin Close
Hi All, I'm about to upgrade from FreeBSD 4.8 to Current (following the instructions in UPDATING) and was just wondering if mergemaster removes depreciated files between the two versions. Ie: /etc/rc.sendmail I believe is now depreciated to one of the rcNG scripts. Does merge master handle

show locks w/o ddb?

2003-07-30 Thread Mike Silbersack
This may be a dumb question, but is there a way to call whatever show locks calls from within the kernel, similar to how we can call backtrace()? Thanks, Mike Silby Silbersack ___ [EMAIL PROTECTED] mailing list

Re: STEP 2, fixing dhclient behaviour with multiple interfaces

2003-07-30 Thread Dominic Mitchell
On Wed, Jul 30, 2003 at 08:52:19AM +0200, Martin Blapp wrote: But the interface adding does still not work. Maybe a different syntax than this ? connect new interface open set rl0 = up; update close I think you want this syntax (although I still couldn't get it to work): connect new

Re: STEP 2, fixing dhclient behaviour with multiple interfaces

2003-07-30 Thread Dominic Mitchell
On Tue, Jul 29, 2003 at 10:18:05PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Martin Blapp [EMAIL PROTECTED] writes: : Hi Folks, : : I had a closer loom at the OMAPI stuff in dhclient. : : Just to say, I'm very disappointed. The only objects that exist are: :

Re: 4.8-Current Depreciated files

2003-07-30 Thread John Birrell
On Wed, Jul 30, 2003 at 04:44:54PM +0930, Benjamin Close wrote: I'm about to upgrade from FreeBSD 4.8 to Current (following the instructions in UPDATING) and was just wondering if mergemaster removes depreciated files between the two versions. Ie: /etc/rc.sendmail I believe is now

Re: Who is responsible for the install check goo in Makefile.inc1

2003-07-30 Thread Ruslan Ermilov
[ Moved to -current ] On Tue, Jul 29, 2003 at 07:12:09PM -0700, Peter Wemm wrote: John Birrell wrote: [...] The installworld check for a kernel with the new sigaction promptly core-dumped sh with the unsupported syscall. I think this check should be based on sysctl kern.osreldate, not

Re: Who is responsible for the install check goo in Makefile.inc1

2003-07-30 Thread John Birrell
On Wed, Jul 30, 2003 at 10:24:42AM +0300, Ruslan Ermilov wrote: I'm regularly upgrading 4.0-RELEASE to 5.x-CURRENT to check that the upgrade path wasn't broken, and this check comes very handy. I wouldn't object though if it was done using kern.osreldate. I'd happily test any patches in this

Re: Who is responsible for the install check goo in Makefile.inc1

2003-07-30 Thread Ruslan Ermilov
On Wed, Jul 30, 2003 at 05:34:01PM +1000, John Birrell wrote: On Wed, Jul 30, 2003 at 10:24:42AM +0300, Ruslan Ermilov wrote: I'm regularly upgrading 4.0-RELEASE to 5.x-CURRENT to check that the upgrade path wasn't broken, and this check comes very handy. I wouldn't object though if it was

Re: Who is responsible for the install check goo in Makefile.inc1

2003-07-30 Thread John Birrell
On Wed, Jul 30, 2003 at 10:37:29AM +0300, Ruslan Ermilov wrote: Sure, that would be a much better (and safer) approach. Could you please send me your code as well, I'm interested in revieweing it. I'd just like to add something like this before Peter's check that runs sh:

Re: [current tinderbox] failure on i386/i386

2003-07-30 Thread Harti Brandt
That was just bad luck between two related commits. Sorry. harti On Tue, 29 Jul 2003, Tinderbox wrote: TTB --- 2003-07-29 18:31:41 - starting CURRENT tinderbox run for i386/i386 TTB --- 2003-07-29 18:31:41 - checking out the source tree TTB --- cd /home/des/tinderbox/CURRENT/i386/i386 TTB ---

Re: HEADSUP: UMA not reentrant / possible memory leak

2003-07-30 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Poul-Henning Kamp writes: [I'm CC'ing current because this seems to have a significant negative impact on -current kernel stability, and we can use some more data, in particular on non-i386 SMP machines] OK, thanks to a very quick response from JeffR this seems to

Failed to make buildkernel with device ath

2003-07-30 Thread David Lodeiro
I've tried to rebuild the kernel a couple of times now with device ath to add support for my 54g card. The system was cvsup to current yesterday ( 29/07/03) and make buildworld completed succesfully. However rebuilding the kernel fails on this : if_ath.o: In function `ath_attach':

Re: Failed to make buildkernel with device ath

2003-07-30 Thread Lukas Ertl
On Wed, 30 Jul 2003, David Lodeiro wrote: I've tried to rebuild the kernel a couple of times now with device ath to add support for my 54g card. The system was cvsup to current yesterday ( 29/07/03) and make buildworld completed succesfully. However rebuilding the kernel fails on this :

bsdlabel warnings

2003-07-30 Thread Petri Helenius
Is this normal that multiple installations of 5.1-RELEASE complain when running bsdlabel: # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 524288 634.2BSD 2048 16384 32776 b: 4194304 524351 swap c: 39102273

Re: bsdlabel warnings

2003-07-30 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Petri Helenius writes: Is this normal that multiple installations of 5.1-RELEASE complain when running bsdlabel: # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 524288 634.2BSD 2048 16384 32776 b: 4194304

Re: bsdlabel warnings

2003-07-30 Thread Petri Helenius
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Petri Helenius writes: Is this normal that multiple installations of 5.1-RELEASE complain when running bsdlabel: # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 524288 634.2BSD 2048

Re: Compaq Evo N610c

2003-07-30 Thread Tony Maher
Update on Compaq Evo N610c Thanks to an email from Simon in the UK I now have battery support in my N610c. /boot/loader.conf is now hw.pci.allow_unsupported_io_range=1 acpi_dsdt_load=YES acpi_dsdt_name=/boot/acpi_dsdt.aml A patch for acpi_dsdt is attached. Now xbatt (and apm) works

USB HP cd-writer plus 8200 problem

2003-07-30 Thread Zherdev Anatoly
Hello. I have a problem with USB HP cd writer 8200 series under -CURRENT (under -stable it does not detect as umass at all). System detect it as umass0 but after camcontrol rescan (or in boot time) kernel print out this kernel: umass0: CBI reset failed, TIMEOUT and camcontrol devlist does not

Re: Compaq Evo N610c

2003-07-30 Thread Robert =?unknown-8bit?q?Blacqui=E8re?=
Great this works ;-) even with the drive bay battery removed and inserted ;-) Only thing stil acts weird is the pcmcia (wireless) stuff... It seems the first memory ports can't be used zo 0x100-0x13f but the second card gets a other pool 0x180 i think and works ... maybe i can overrule or

Re: STEP 2, fixing dhclient behaviour with multiple interfaces

2003-07-30 Thread Tony Finch
Terry Lambert [EMAIL PROTECTED] wrote: I can't wait for IPv6 stateless autoconfiguration plus SLPv2 so we can get rid of all this DHCP crap once and for all. 8-(. SLPv2 is used to find the gateway and DNS server, and after that, everything magically works. I thought that the gateway address is

Re: HEADSUP: UMA not reentrant / possible memory leak

2003-07-30 Thread Bosko Milekic
On Tue, Jul 29, 2003 at 11:42:51PM -0400, Jeff Roberson wrote: On Wed, 30 Jul 2003 [EMAIL PROTECTED] wrote: The indication of this is that the g_bio zone does not return to zero USED as it should. It looks like z-uz_cachefree is slightly out of date (updated in zone_timout() every

Re: STEP 2, fixing dhclient behaviour with multiple interfaces

2003-07-30 Thread Robert Watson
On Tue, 29 Jul 2003, Terry Lambert wrote: This is part of the problem. The other parts are that this is really networking code, and should be a separate thing, if possible, and, as Martin just pointed out, the OMAPI stuff is not really cooked yet. Hence the notion of a neteventd -- I don't

sh coredump through rc.subr

2003-07-30 Thread Tobias Roth
i just managed to get an sh coredump with an rc.d/ script of mine. here is part of the output of /etc/rc.d/test stop : /etc/rc.d/test: DEBUG: run_rc_command: evaluating :(). Loading configuration files. Node type = 15 pid 5183 (sh), uid 0: exited on signal 11 (core dumped) zsh: segmentation fault

Re: strange umass/scsi behaviour

2003-07-30 Thread Yar Tikhiy
On Wed, Jul 30, 2003 at 08:44:34AM +0200, John Hay wrote: The last message is Opened disk da0 - 6. That is a little strange because I thought we only do 10 byte commands to usb devices. The problem is that only da0 pitch up in the /dev directory. There should be a da0s1 too. Using fdisk on

RE: Compaq Evo N610c

2003-07-30 Thread Cagle, John (ISS-Houston)
Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com website.) I know that the _OSI(Windows 2001) bug will be fixed in the F.15 release, but I don't think the _GL_ portion of your patch will be included. Did you have to remove the Acquire Release of _GL_ in order

Re: FreeBSD 5.1-R kernel panic

2003-07-30 Thread Stephane Raimbault
Hi Bosko, My kernel panic'd again this morning. I had removed all the USB devices from my kernel and had set my /etc/rc.conf to usbd_enable=NO and the kernel panic'd again. I have attached both my kernel config file and the trace of the panic. Let me know if I can provide any further

Re: FreeBSD 5.1-R kernel panic

2003-07-30 Thread Bosko Milekic
On Wed, Jul 30, 2003 at 09:25:34AM -0600, Stephane Raimbault wrote: Hi Bosko, My kernel panic'd again this morning. I had removed all the USB devices from my kernel and had set my /etc/rc.conf to usbd_enable=NO and the kernel panic'd again. I have attached both my kernel config file and

Does bimap (ipnat) work to anyone ?

2003-07-30 Thread Piotr Koper
Hi, Does ``bimap'' work to anyone ? I'm using IP Filter: v3.4.31 (336) and I can't make it work for me: ipnat.conf: bimap fxp0 212.182.x.x/32 - 192.168.10.5/32 I have aditional ethernet alias (212.182.x.x) and when I ping this address from the Internet it replys from 192.168.10.5, traceroute

Re: FreeBSD 5.1-R kernel panic

2003-07-30 Thread Stephane Raimbault
Hi Bosko, Thank you for your suggestion. I am a little un-easy about upgrading my system from -RELEASE to -CURRENT. Did you mean, simply upgrading the kernel to -CURRENT, or the entire system? I'll think of a way I can continue this testing with you so that we can make sure this problem is

[current tinderbox] failure on alpha/alpha

2003-07-30 Thread Tinderbox
TB --- 2003-07-30 16:00:05 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-30 16:00:05 - 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-30 16:02:04 - building world TB --- cd

gcc segfault on -CURRENT (cvs yesterday)

2003-07-30 Thread Kai Mosebach
Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Cheers Kai c++ -D_THREAD_SAFE -DFREEBSD_DEBUG -DPTHREADS -DFREEBSD_THREADS -DREL30 \ -DFREEBSD -DI386 -DSAG -I/usr/local/sapdb/depend/incl -I/projects/sapdb/\

(no subject)

2003-07-30 Thread jojolaterreur
_ Envie de discuter en live avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France ___ [EMAIL PROTECTED] mailing list

RE: PATCH: Disable 6 byte commands for USB, firewire, ATAPICAM

2003-07-30 Thread John Baldwin
On 25-Jul-2003 Nate Lawson wrote: Attached is a patch that disables ever sending 6 byte commands to buses that do not support them. Numerous USB devices hang when receiving a 6 byte command. For testing, this patch comments out the scsi_da quirks for devices that I believe are addressed by

RE: show locks w/o ddb?

2003-07-30 Thread John Baldwin
On 30-Jul-2003 Mike Silbersack wrote: This may be a dumb question, but is there a way to call whatever show locks calls from within the kernel, similar to how we can call backtrace()? If you have DDB compiled in you could call the appropriate witness function, though I think it is a static

Re: gconftool-2 failing

2003-07-30 Thread Joe Marcus Clarke
On Sun, 2003-07-20 at 18:59, Rik wrote: I have recently run into a problem with the gconftool-2 service that comes with gnome2. When I go into X I get a gcond process that runs out of control. If I try to install ports that require the gconftool-2 to run the port will fail to install.

RE: Compaq Evo N610c

2003-07-30 Thread Tony Maher
On Thu Jul 31 01:04:15 2003 John Cagle wrote: Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com website.) Laptop is currently in use so I cannot get to bios however: from acpi_dsdt file RSDT: Length=44, Revision=1, Checksum=199, OEMID=COMPAQ, OEM Table

Re: FreeBSD 5.1-R kernel panic

2003-07-30 Thread Bosko Milekic
On Wed, Jul 30, 2003 at 11:02:05AM -0600, Stephane Raimbault wrote: Hi Bosko, Thank you for your suggestion. I am a little un-easy about upgrading my system from -RELEASE to -CURRENT. Did you mean, simply upgrading the kernel to -CURRENT, or the entire system? Due to potential sync

RE: panic: sleeping thread owns a mutex

2003-07-30 Thread John Baldwin
On 28-Jul-2003 Kris Kennaway wrote: One of the alpha package machines just died with the following: panic: sleeping thread owns a mutex panic() at panic+0x160 propagate_priority() at propagate_priority+0x148 _mtx_lock_sleep() at _mtx_lock_sleep+0x264 _mtx_lock_flags() at

Error with Atheros chipset.

2003-07-30 Thread Marcin Jessa
Hi Guys. I've recompiled -CURRENT with support for atheros cards. I have two cards, one PCI(desktop) and one PCMCIA(laptop). Both are Proxim 11a/b/g combo cards with AR5212 chips. The cards are recognized fine. pciconf -l -vv shows: [EMAIL PROTECTED]:4:0: class=0x02 card=0x0a6014b7

make -U

2003-07-30 Thread Ruslan Ermilov
Sorry, I've accidentally dropped an email about `make -U'. I think that it's not needed, since the functionality can easily be achieved by running make FOO=, i.e., assigning an empty value. Remember that command line variables take precedence over globals, so the following makefile, FOO+= bar

Re: make -U

2003-07-30 Thread Juli Mallett
* Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ] [ w.r.t. make -U ] Sorry, I've accidentally dropped an email about `make -U'. I think that it's not needed, since the functionality can easily be achieved by running make FOO=, i.e., assigning an empty value. Remember that

Re: make -U

2003-07-30 Thread Ruslan Ermilov
On Wed, Jul 30, 2003 at 04:23:20PM -0500, Juli Mallett wrote: * Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ] [ w.r.t. make -U ] Sorry, I've accidentally dropped an email about `make -U'. I think that it's not needed, since the functionality can easily be achieved by

Re: strange umass/scsi behaviour

2003-07-30 Thread Nate Lawson
On Wed, 30 Jul 2003, John Hay wrote: On Tue, Jul 29, 2003 at 11:28:18PM -0700, Nate Lawson wrote: On Wed, 30 Jul 2003, John Hay wrote: Does anyone have an idea why the umass/scsi code behave differently between if you boot with a device already plugged in as opposed to plugging it in

bug in big pipe code causing performance problems

2003-07-30 Thread Pierre Beyssac
Hello, If no one objects to it, I'd like to commit the following ASAP. It fixes an obvious bug in the big pipe code, a discrepancy between how free space is calculated in write vs poll. The bug affects stable as well. The bug's implications are less obvious: it make write(2) on a non-blocking

Re: make -U

2003-07-30 Thread Juli Mallett
* Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ] [ w.r.t. Re: make -U ] On Wed, Jul 30, 2003 at 04:23:20PM -0500, Juli Mallett wrote: * Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ] [ w.r.t. make -U ] Sorry, I've accidentally dropped an email about `make -U'.

Re: 4.8-Current Depreciated files

2003-07-30 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Benjamin Close [EMAIL PROTECTED] writes: : Hi All, : I'm about to upgrade from FreeBSD 4.8 to Current (following the : instructions in UPDATING) and was just wondering if mergemaster removes : depreciated files between the two versions. Ie:

Re: bug in big pipe code causing performance problems

2003-07-30 Thread Pierre Beyssac
On Wed, Jul 30, 2003 at 11:32:49PM +0200, Pierre Beyssac wrote: - if (space 0 (wpipe-pipe_buffer.cnt PIPE_SIZE)) { + if (space 0 + wpipe-pipe_buffer.cnt wpipe-pipe_buffer.size) { PS : not-so-obvious after all since the above is equivalent to (space

Re: bug in big pipe code causing performance problems

2003-07-30 Thread Mike Silbersack
On Wed, 30 Jul 2003, Pierre Beyssac wrote: On Wed, Jul 30, 2003 at 11:32:49PM +0200, Pierre Beyssac wrote: - if (space 0 (wpipe-pipe_buffer.cnt PIPE_SIZE)) { + if (space 0 +wpipe-pipe_buffer.cnt wpipe-pipe_buffer.size) { PS : not-so-obvious

Re: Error with Atheros chipset.

2003-07-30 Thread Sam Leffler
[Not sure about cross-posting but I'll leave it for now.] I've recompiled -CURRENT with support for atheros cards. I have two cards, one PCI(desktop) and one PCMCIA(laptop). Both are Proxim 11a/b/g combo cards with AR5212 chips. The cards are recognized fine. pciconf -l -vv shows: [EMAIL

Upgrade to 5.1 fixes wi0 accesspoint mode fubar.

2003-07-30 Thread David Gilbert
For various reasons, I upgraded my firewall from 4.8-STABLE to 5.1-CURRENT. Recently, I complained that the wireless clients of the wi0 PCI card running in hostap mode would loose sync. It was repeatable that they clients would loose sync when the server was serving more interrupts. One of the

Re: gcc segfault on -CURRENT (cvs yesterday)

2003-07-30 Thread Kris Kennaway
On Wed, Jul 30, 2003 at 06:40:58PM +0200, Kai Mosebach wrote: Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Do you have stale C++ headers in /usr/include? Kris pgp0.pgp Description: PGP signature

AW: gcc segfault on -CURRENT (cvs yesterday)

2003-07-30 Thread Kai Mosebach
On Wed, Jul 30, 2003 at 06:40:58PM +0200, Kai Mosebach wrote: Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Do you have stale C++ headers in /usr/include? I did a rm -rf /usr/include before make

Re: gcc segfault on -CURRENT (cvs yesterday)

2003-07-30 Thread Kris Kennaway
On Wed, Jul 30, 2003 at 10:29:58PM +0200, Kai Mosebach wrote: On Wed, Jul 30, 2003 at 06:40:58PM +0200, Kai Mosebach wrote: Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Do you have stale

-current panic: ffs_valloc: dup alloc

2003-07-30 Thread John
Hi, On a newly installed 20030729-CURRENT system, the system panic'd during a pkg_add. Note the mode/inum/fs at the end of the Fetch line. # pkg_add -r zsh Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-current/Latest/zsh.tbz...mode = 0177560, inum = 48, fs = /var panic:

[Fwd: cvs commit: src/sys/kern sys_pipe.c]

2003-07-30 Thread Alan L. Cox
I believe that the attached commit addresses the panic: sleeping thread owns a mutex problem reported by Kris and another related problem reported a few days earlier. The earlier problem report included the following stack trace: Sleeping on objtrm with the following non-sleepablelocks held:

Re: [Fwd: cvs commit: src/sys/kern sys_pipe.c]

2003-07-30 Thread Kris Kennaway
On Wed, Jul 30, 2003 at 11:15:09PM -0500, Alan L. Cox wrote: I believe that the attached commit addresses the panic: sleeping thread owns a mutex problem reported by Kris and another related problem reported a few days earlier. The earlier problem report included the following stack trace:

Lucent IBSS mode doesn't work in -CURRENT?

2003-07-30 Thread Greg 'groggy' Lehey
Earlier this month I sent a message saying that my wireless card (Orinoco) doesn't work at all any more. In the meantime, I've narrowed the problem down to IBSS (ad-hoc) mode: it works fine in BSS (base station) mode. I'd like to know if *anybody* is using IBSS (maybe with Orinoco cards) on a

[current tinderbox] failure on alpha/alpha

2003-07-30 Thread Tinderbox
TB --- 2003-07-31 04:00:06 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-31 04:00:06 - 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-31 04:02:17 - building world TB --- cd

Re: strange umass/scsi behaviour

2003-07-30 Thread John Hay
Does anyone have an idea why the umass/scsi code behave differently between if you boot with a device already plugged in as opposed to plugging it in later? In my case it is a Sandisk Cruiser. If I plug it in before booting, it works just great, but if I plug it in later, it