Re: Strange networking problems after update 5.2.1-5.3
In message: [EMAIL PROTECTED] Gerrit Kühn [EMAIL PROTECTED] writes: : I will do so if it's the support for the cards that is broken. However, I : have tried 4 different cards now, and only one of them worked. So I'm : tending to put the blame on the pcmcia bridge and it's driver. Blame doesn't belong there, but elsewhere in the system. The second ed card is broken in the ed driver (people with other bridges have reported problems), while the cardbus activation issue almost certainly is a resource issue (because other people with TI-1225 bridge work). I'll be happy to help you track down that issue, however. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange networking problems after update 5.2.1-5.3
In message: [EMAIL PROTECTED] Gerrit Kühn [EMAIL PROTECTED] writes: : On Tue, 04 Jan 2005 03:36:53 -0700 (MST) M. Warner Losh [EMAIL PROTECTED] : wrote about Re: Strange networking problems after update 5.2.1-5.3: : : : MWL : I will do so if it's the support for the cards that is broken. : MWL However, I : have tried 4 different cards now, and only one of them : MWL worked. So I'm : tending to put the blame on the pcmcia bridge and : MWL it's driver. : : MWL Blame doesn't belong there, but elsewhere in the system. The second : MWL ed card is broken in the ed driver (people with other bridges have : MWL reported problems), while the cardbus activation issue almost : MWL certainly is a resource issue (because other people with TI-1225 : MWL bridge work). I'll be happy to help you track down that issue, : MWL however. : : Thank you very much in advance. : Please tell me which information you need. You've likely already sent this before... But can you send a full dmesg with hw.cbb.debug=1 and hw.cardbus.debug=1 (these are set in /boot/loader.conf) and a devinfo -r. I have a handle on the ed card showing up as NE-1000. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom and sio
In message: [EMAIL PROTECTED] Brandon Fosdick [EMAIL PROTECTED] writes: : Judging from the man page, ucom is limited to acting like a tty with no : support for sio. Is this true? Is there some magic config bit somewhere : that will enable hidden sio support? Ummm, I don't know what you are asking here. ucom supports all the rs232 stuff w/o problem. I use it all the time with my phone to dial into the network. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devfs rules
In message: [EMAIL PROTECTED] Ivan Voras [EMAIL PROTECTED] writes: : It seems devd.conf works only for static devices, not hotplugged, : while devfs rules works for those, but they vanish on reboot. That's not true. devd devinitely deals with hotplugged devices. I use it all the time. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: latest -stable ucom0 not created
In message: [EMAIL PROTECTED] Kim Culhan [EMAIL PROTECTED] writes: : : Just upgraded to the latest -stable. : : When I try to use tip with /dev/com0 it returns: : : /dev/ucom0: No such file or directory : link down : : I added device ucom and device ubsa to the kernel config : but this did not help. : : Any help here is greatly appreciated. ls /dev/ttyU* Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2 - 5.3 without single mode?
In message: [EMAIL PROTECTED] dima [EMAIL PROTECTED] writes: : Is it possible to cvsup from 5.2 to 5.3 without booting in single mode? : I have a remote machine and want update it, but it is no console access, : only SSH. : You don't actually need to reboot in single-user mode. Just make sure your users wouldn't use the server hard during the : # mergemaster -p : # make installworld : # mergemaster : cycle. You can basically disable all the services but sshd for that task enable them again after the second reboot. While you don't NEED to go into single user (I do the above all the time), you are setting yourself up to get screwed the first time that a new, common system call is introudced... Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2 - 5.3 without single mode?
In message: [EMAIL PROTECTED] Stephen Montgomery-Smith [EMAIL PROTECTED] writes: : M. Warner Losh wrote: : In message: [EMAIL PROTECTED] : dima [EMAIL PROTECTED] writes: : : Is it possible to cvsup from 5.2 to 5.3 without booting in single mode? : : I have a remote machine and want update it, but it is no console access, : : only SSH. : : You don't actually need to reboot in single-user mode. Just make sure your users wouldn't use the server hard during the : : # mergemaster -p : : # make installworld : : # mergemaster : : cycle. You can basically disable all the services but sshd for that task enable them again after the second reboot. : : While you don't NEED to go into single user (I do the above all the : time), you are setting yourself up to get screwed the first time that : a new, common system call is introudced... : : : So if there is a new common system call introduced, will it arrive with : a nice entry in UPDATING plus a HEADS UP? Maybe, maybe not. All I'm saying is that often you can get away with short cuts, but unless you really know what's going on there are a number of different things that can mess you up trying to do the shortcut. Some of which can be a 'restore from backup' mistake. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What OS are you? fun
In message: [EMAIL PROTECTED] Gregory Bond [EMAIL PROTECTED] writes: : Rob wrote: : : You'd better cite your source and / or reasoning, as ~3*10^8m/s =is= : the : accepted constant speed of light in vacuum. : : It's deeper than that. The second and the meter are both defined in : terms of wavelengths of light, which (as a consequence) fixes the speed : of light _by definition_, at _exactly_ *299 792 458 m s^-1. The second is not defined in terms of the speed of light. It is defined in terms of the number of hyperfine transitions of cesium: http://www.bipm.fr/en/si/si_brochure/chapter2/2-1/second.html The second is the duration of 9 192 631 770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the caesium 133 atom. This definition refers to a caesium atom at rest at a temperature of 0 K. The meter used to be defined in terms the wavelength of Krypton-86 radiation, but that was changed in 1983. It is nowdefined in terms of how far light travels in a given time interval. See http://physics.nist.gov/cuu/Units/meter.html for a good historical perspective. So the definition of the meter is dependent on the second, but the second is independent. However, the definition implicitly assumes that today's fundamental constants of the universe are indeed constant. There's been some evidence that suggests, but is so far inconclusive, that some or all of the fundamental constants of the universe may vary on the order of a few parts in 10^15 over the last few billion years or so. The definition of the meter was changed before this evidence was known. And this is indeed, very off topic. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SIIG cards and puc
In message: [EMAIL PROTECTED] John-Mark Gurney [EMAIL PROTECTED] writes: : Paul Sandys wrote this message on Mon, Nov 22, 2004 at 11:46 -0500: : The SIIG card I have does use shared interrupt for both ports, so I don't see : any other way around it. : : The 0x4001 is a regular flag that's used by sio.c . I found an undocumented : feature in there, that allows you to set a FIFO size, so I used it in : combination with the shared irq flag. : : Ahh, yes... Then we now have the interesting problem that it appears : that PUC and sio share flags... :( : : from puc.c: : type = (sc-sc_desc.ports[i].flags PUC_FLAGS_MEMORY) : ? SYS_RES_MEMORY : SYS_RES_IOPORT; : : and: : device_set_flags(sc-sc_ports[i].dev, : sc-sc_desc.ports[i].flags); : : which means you are also turning on memory mapping for the card... : : I'm not comfortable including a flag for an undocumented feature as a : standard part of the system.. Care to document it? :) : : Also, are you sure it's the ISMULTIPORT that needs to be set? (and not : the MEMORY flag you are acidentally also setting?) From what I've read : of the PUC driver, it handles the multiport case for you since it hands : out the interrupts to the sio driver... see this comment above puc_intr: : * This is an interrupt handler. For boards that can't tell us which : * device generated the interrupt it just calls all the registered : * handlers sequencially, but for boards that can tell us which : : hmmm.. that's probably how it gets around the fact that it doesn't need : to pass in the multiport flag, so we should probably be clearing that : flag before passing it down to the lower layers... You don't need the MULTIPORT to use PUC. If you do, then something in the tables is setup right. MULTIPORT is only for ISA cards. So that's clearly wrong. Can someone send me the patch for review. I've added devices to puc in the past. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serious networking (em) performance (ggate and NFS) problem
In message: !~!UENERkVCMDkAAQACABgA0VcX9IoJqUaXPS8MjT1PdsKQ/[EMAIL PROTECTED] Daniel Eriksson [EMAIL PROTECTED] writes: : Finally, my question. What would you recommend: : 1) Run with ACPI disabled and debug.mpsafenet=1 and hope that the mix of : giant-safe and giant-locked (em and ahc) doesn't trigger any bugs. This is : what I currently do. : 2) Run with ACPI disabled and debug.mpsafenet=0 and accept lower network : performance (it is a high-traffic server, so I'm not sure this is a valid : option). : 3) Run with ACPI enabled and debug.mpsafenet=1 and accept that em0 : interrupts leak to the atapci1+ ithread. This I have done in the past. I don't know if I'm to a 'recommendation' so much as a 'I'd try your normal configuration with mpsetfet=0' to see if that makes a difference in the performance that you see. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serious networking (em) performance (ggate and NFS) problem
In message: [EMAIL PROTECTED] Robert Watson [EMAIL PROTECTED] writes: : (1) I'd first off check that there wasn't a serious interrupt problem on : the box, which is often triggered by ACPI problems. Get the box to be : as idle as possible, and then use vmstat -i or stat -vmstat to see if : anything is spewing interrupts. Also, make sure that you aren't sharing interrupts between GIANT-LOCKED and non-giant-locked cards. This might be exposing bugs in the network layer that debug.mpsafenet=0 might correct. Just noticed that our setup here has that setup, so I'll be looking into that area of things. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pccard modem and ethernet don't work together
In message: [EMAIL PROTECTED] Ronald Klop [EMAIL PROTECTED] writes: : On Wed, 10 Nov 2004 01:56:09 -0700 (MST), M. Warner Losh [EMAIL PROTECTED] : wrote: : : In message: [EMAIL PROTECTED] : Ronald Klop [EMAIL PROTECTED] writes: : : I posted the same text as below to current@ on 20 Oct, but got no : answer. : : Is there somebody here who knows more about this or can tell me where : to : : look further? : : I got a 'me too' message from somebody who googled my previous : question, : : so there are more people with this problem. : : I ment to reply, but got busy with the release. I'll see if I can : recreate the problem. : : Warner : : Thanks in advance. : I am still looking around myself and am wondering if I need to run pccardd? : I thought it was replaced by devd, but it is still in the system. : Does pccardd have more functionality than devd and is it possible that it : can solve my problem? : Or am I looking in the wrong direction? pccardd won't help. The problem is almost certainly some kind of resource allocation issue that's casuing the cards to fail. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCMCIA modem heating
In message: [EMAIL PROTECTED] Zoran Kolic [EMAIL PROTECTED] writes: : Hi all! : Don't wonna make stupid : quiestions, but this is : something I have to know : to make reclamation if neces- : sary. : After 5-10 minutes of inter- : net connection, when detached, : my pccard modem is hot as fur- : nace. I can barely take it in : my hand. Is it normal beha- : veour? : Model is Zoltrix, has cirrus : on the sticker. Try setting debug.mpsafenet=0 in your /boot/loader.conf. I have similar sounding issues with -current and my USB modem + ppp. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Termcap Makefile Doesn't Honor DESTDIR
In message: [EMAIL PROTECTED] Jason C. Wells [EMAIL PROTECTED] writes: : The makefile in /usr/src/share/termcap doesn't honor DESTDIR. Should it? Likely. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pccard modem and ethernet don't work together
In message: [EMAIL PROTECTED] Ronald Klop [EMAIL PROTECTED] writes: : I posted the same text as below to current@ on 20 Oct, but got no answer. : Is there somebody here who knows more about this or can tell me where to : look further? : I got a 'me too' message from somebody who googled my previous question, : so there are more people with this problem. I ment to reply, but got busy with the release. I'll see if I can recreate the problem. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld needs root privileges?
In message: [EMAIL PROTECTED] Joan Picanyol [EMAIL PROTECTED] writes: : Hi, : : I've recvsuped and removed /usr/src and /usr/obj, same symtoms in : RELENG_5 and RELENG_5_3. Is this expected/known? No. I've built many many many times w/o root, both current and RELENG_5 over the past few weeks... Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade questions 4.10 - 5-stable
In message: [EMAIL PROTECTED] Brooks Davis [EMAIL PROTECTED] writes: : I'm interested about directories that are changed by system/system : programs - I belive most confusing is /var in theory there shouldn't : be anything important there (well except logs), but I already noticed : there is mail, crontab jobs, informations what ports were installed : even mysql port install database there. : : By design /var contains things that change frequently during system : operation, not things that are unimportant. Thing in /var/run and : /var/tmp are required to be things you can lose, but many of the rest of : the directories are of crucial importance. It used to be the case, long time ago (like 10-15 years), that /var was irrelevant accross reboots, so many people got the idea that it never would be unimportant. In that ensuing years, /var has become something that can contain more interesting files that should be preserved. That's the history that people have with /var. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTPD and SecureLevel
In message: [EMAIL PROTECTED] David Magda [EMAIL PROTECTED] writes: : : On Jun 16, 2004, at 03:47, Pavel M. Rebrov wrote: : : I've installed and configured ntpd daemon and was wondering if it : going to work with SecureLevel higher than 1. SecureLevel 2 forbids : changing the system date and, therefore, ntpdate and rdate won't work. : : Have ntpdate run before hand to get the time with in a close amount of : the 'real' time. There should be an rc.conf item for ntpdate. : : ntpd(8) doesn't actually change the time by making it 'jump' to the : correct time; it slows down or speeds up the rate at which the timer : runs at. only if you run it with -x, otherwise it will set the time if it is off by more than 128ms. -x Normally, the time is slewed if the offset is less than the step threshold, which is 128 ms by default, and stepped if above the threshold. This option forces the time to be slewed in all cases. If the step threshold is set to zero, all offsets are stepped, regardless of value and regardless of the -x option. In general, this is not a good idea, as it bypasses the clock state machine which is designed to cope with large time and frequency errors Note: Since the slew rate is limited to 0.5 ms/s, each second of adjustment requires an amortization interval of 2000 s. Thus, an adjustment of many seconds can take hours or days to amortize. This option can be used with the -q option. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is 4.10-BETA stable?
In message: [EMAIL PROTECTED] Dave Horsfall [EMAIL PROTECTED] writes: : Well, imagine my dismay when I was greeted with 4.10-BETA instead... It appears that re changed the way they are tagging releases again. The last time we had 4.x-BETA was 4.2. A review of the cvs log for the newvers.sh file shows that 5.1 and 5.2 had a BETA release, but all other 4.x releases since 4.3 went through the sequence 4.x-STABLE - 4.x+1-PRERELEASE - 4.x+1-RC - 4.x+1-STABLE You'll have to ask re@ why this wasn't done this time. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is 4.10-BETA stable?
In message: [EMAIL PROTECTED] Michael Nottebrock [EMAIL PROTECTED] writes: : On Thursday 22 April 2004 16:16, Dave Horsfall wrote: : On Thu, 22 Apr 2004, Ceri Davies wrote: :Are there any, umm, release notes for 4.10-BETA, so I can see what I'm :in for? : : They're in src/release, but you do have STABLE. The BETA in 4.10-BETA : means that we're considering this code for release as 4.10-RELEASE, and : that's all. : : Many thanks. : : Btw, this is a FAQ - and it's in the FAQ, too. : : http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RELEASE-CANDIDATE Notice that the FAQ doesn't talk about -BETA at all. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Stallion EC8/32-AT
Anybody successfully using the Stallion EC8/32-AT on -stable? I just tried using the one I got on ebay and found that it hands on port close and passes no characters at all. Do any of the stallion cards work? Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
sshd 'zombie' processes
each scp or ssh I do to a 4.8-stable machine I have gives me two 'zombie' processes: root 282 0.0 0.4 5236 2184 ?? I 7:41AM 0:00.05 sshd: imp [priv] (sshd) imp 284 0.0 0.4 5252 2260 ?? I 7:41AM 0:00.01 sshd: [EMAIL PROTECTED] (sshd) I had been running 4.8-RC when I first noticed it and reported it. People here said this had been fixed shortly after 4.8, but it is still broken. :-( Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel core dump in recent 4.8-STABLE
In message: [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : : The only interesting commit I see in that range is Tor's process : leader sharing work. Cc'ing him. : : That commit broke kernel modules depending on the layout of struct : proc. Since recompiling the kernel module isn't an option for third : party binary modules, the new p_fdtol variable should be moved to the : end of struct proc. this patch looks good to me. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: changes in FreeBSD-STABLE src/sys/i386/i386/nexus.c 1.26.2.9
cTimeTag Unit 3 Channel 3:Got Tag 472221 84751:086171223:20002 Correlated Timescale
In message: [EMAIL PROTECTED]
Oliver Eikemeier [EMAIL PROTECTED] writes:
: After rebuilding my kernel with FreeBSD-STABLE booting fails with:
:
: panic: still using grody create_intr interface
:
: when loading the ata0 driver (FreeBSD 4.8-PRERELEASE, 440 LX based
: motherboard)
:
: After I changed line 495 of src/sys/i386/i386/nexus.c rev 1.26.2.9 to
:
: switch (flags ~INTR_TYPE_FAST) {
:
: everything works as expected. Could this be a typo in the recent
: changes? Otherwise I'm happy to post my dmesg.
Nope, I botched the merge :-( 1.26.9.10 fixes this problem. Sorry
for the bother.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: wi0 and mtu setting
In message: [EMAIL PROTECTED] Evren Yurtesen [EMAIL PROTECTED] writes: : I definetely agree and obviously since mikrotikos supports this then linux : should do since mikrotikos is built on linux. Why shouldnt FreeBSD support : setting mtu of wireless interfaces higher than 1500 Patches? Complaining in -stable might not attract my attention to the problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: wi0 and mtu setting [bad idea]
In message: [EMAIL PROTECTED] Evren Yurtesen [EMAIL PROTECTED] writes: : Yes, actually this is why I asked first about MTU settings in wi. I use : PPPoE and it has 8bytes overhead. It could be nice to set MTU to 1508 so : 1500 byte ethernet frames can be encapsualted in PPPoE without : fragmentation. : : I just dont understand why FreeBSD people have to make this wi driver so : tight in standarts even though there are wireless cards which support : non-standard(and sometimes nice) things which can be useful. I definetely : disagree that something should be in standard so you will allow setting of : it! Dude, you are being way too confrontational here. Since I am the wi driver maintainer, and I haven't said I wouldn't support this, you are just being an ass rather than doing things in a way that would motivate people to allow you the flexibility to do. I'm not conversant on all the technical issues, but so far I've missed patches that I could test to see if they cause problems or not. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: wi0 and mtu setting [bad idea]
In message: [EMAIL PROTECTED] Evren Yurtesen [EMAIL PROTECTED] writes: : I think something is called broken when it doesnt work as you expect it to : work or it doesnt comply with standards. : Also I think something is called an 'extra feature' if it is not in the : standard which defines it but you have access to it. : : Can you please show me the 802.11b document where it says the MTU shouldnt : be more than 1500bytes? Maybe it doesnt say that the MTU can be more than : 1500 bytes but I think the standards also doesnt say if it must be smaller : than 1500 bytes. : : Also by lettin user to be able to set MTU higher than 1500 you do not : break the wi driver. You give an extra feature to it. It is the user who : breaks the standards(if it says in 802.11b standards that the MTU cant be : bigger than 1500) if he/she sets MTU higher than 1500 Actually, if you want to play the standards card, you need to show where in the doc it is allowed. The burdon of proof is on you, not the me, for this. I've seen some compelling arguments to do this, but also a lot of stupid grousing and complaining that make me ill inclined to help. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: wi0 and mtu setting [bad idea]
In message: [EMAIL PROTECTED] Evren Yurtesen [EMAIL PROTECTED] writes: : Sorry about that but everybody seemed to disagree to having this option of : 1500+ MTU settings in wi driver. : : If you will support this, then its just fine for me. I dont complain! =) : Sorry! Well, this converstation needs to take place on the net@ list. In -current, at least, if_ethersubr.c prevents 'ethernet' drivers from setting the mtu higher. There's some experimental patches that make 802.11 its own network thing which were ported over from NetBSD, but even those don't allow one to set it higher since it just uses the if_ethersubr code path for mtu setting. So while I'll make it possible for the wi driver, it won't help at all until this higher level stuff is resolved. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Netgear MA301 Wireless PCI woes
In message: [EMAIL PROTECTED] rik [EMAIL PROTECTED] writes: : Well, I found out what the problem is. The face plate is far enough away : from where it should be that the card wasn't physically plugged in. : Seems my kernel and the generic kernels both work... That would also cause it not to show up :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ipl problem in wi_hostapp.c ?
In message: [EMAIL PROTECTED] Paul Herman [EMAIL PROTECTED] writes: : On Mon, 20 May 2002, M. Warner Losh wrote: : : In message: [EMAIL PROTECTED] : Paul Herman [EMAIL PROTECTED] writes: : : Just curious, what is then the reason that splsoftclock() has the : : magical property of clearing all other SWI_* bits? I ask because : : the folowing change to ipl_funcs.c also stopped the panic I was : : experiencing. Machine is still running for now :-) : : splsoftclock() isn't supposed to be used in driver code. : : I see. : : Well, if it makes it less broken before any fixes get MFCed, it : might be nice to simply bump the two splsoftclock()s in : wi_hostapp.c to splnet() before 4.6-RELEASE. : : Thanks Warner for the info, and thanks Drew for noticing the : problem in the first place. You've got a good eye. Actually, I'll be MFCing a mostly proper fix today. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: dump over SSH: please MFC
In message: [EMAIL PROTECTED] Johann Frisch [EMAIL PROTECTED] writes: : 5 months ago, a change was made to Allow users to specify a : command to use as remote command instead of using rcmd directly, : see http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/net/rcmd.c : : The comment says this should have been MFC'd after 2 months but it : wasn't. Both NetBSD and OpenBSD have similar features and I'd like : FreeBSD to catch up so I can use dump over SSH the right way. I made that change. Alas, I've been somewhat swamped for a while now, so it looks like others will have to make the MFC (if it hasn't already happened while I wasn't looking). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pccard working on smp in -stable?
In message: [EMAIL PROTECTED] Nate Lawson [EMAIL PROTECTED] writes: : The desktop machine is SMP with an ISA pccard controller added. I've : looked into the archives and found a suggestion that pccard has not been : tested with SMP. Is this correct? What would be involved with getting it : working? While I'm told that SMP works with pccard, I've never gotten it to work on my SMP box that has (had) a pccard ISA bridge in it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 3Com AirConnect Driver Merge
In message: 3CC2573A@caliber Alex McHale [EMAIL PROTECTED] writes: : 5.0-CURRENT recently had a merge from NetBSD in the wi driver, for support for : Symbol based cards (such as the 3Com AirConnect). I am curious if this merge : will ever happen in 4.5. If anyone can tell me YAY or NAY for certain, I : would veyr much appreciate that. A merge will never happen for 4.5-RELEASE. However, one is planned before 4.6-RELEASE. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NFS timing out over wi0 interface using UDP?
In message: [EMAIL PROTECTED] Mike Gratton [EMAIL PROTECTED] writes: : If anyone knows of any reason why it may be failing, or wants any : debugging data, please let me know, otherwise I'll just file a PR. I've done some pretty heavy stuff over NFS over wi0 (including a buildworld/install world to a /usr/src and /usr/obj NFS mounted). It was slow, but it worked w/o time outs. Maybe you are too far away from the wireless base station? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Unknown user: smmsp
In message: Pine.WNT.4.43.0204141515370.3044-10@den2 Juha Saarinen [EMAIL PROTECTED] writes: : On Sat, 13 Apr 2002, David W. Chapman Jr. wrote: : : I don't know if its fixed, but another problem is when you try to use : mergemaster it used to fail because that user couldn't be found, most : likely due to mtree, IIRC. : : Would it be hard to fix? Seems wrong to have to manually add the Sendmail : users just to build world. Yes, as it is in the mtree files now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: dell inspiron 8000 freebsd -stable
In message: 004901c1d53f$552ca650$1fa531d8@saturated paul [EMAIL PROTECTED] writes: :DVD-ROM drive on inspiron 8000 doesn't work in freebsd -stable. I : searched the mailing lists and found a work around to do an : autoboot_delay=60 which after doing my dvdrom drive worked fine in FreeBSD : 4.5 -release, however does not work in -stable. : I get a..acd0c:Device not configured. Any help would be greatly : appreciated My DVD-ROM worked great up through FreeBSD-stable 4.5 as of when I upgraded to -current (so say sometime in late Janurary). I'm not sure what has changed since then. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: make: 1: Syntax error: ( unexpected
In message: [EMAIL PROTECTED] Jonathan Chen [EMAIL PROTECTED] writes: : On Sun, Mar 24, 2002 at 08:28:08PM -0800, Peter Hessler wrote: : I am trying to update my 4.5-stable system, and I keep getting the : error make: 1: Syntax error: ( unexpected : : The error text you're getting shows that you aren't using the standard : make in /usr/bin. Looks like you're invoking GNU make instead - not a : good idea; it should have been installed as gmake and not make. It might also be due to a corrupt make binary. The kernel thinks it is a shell script... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: make: 1: Syntax error: ( unexpected
In message: a05101001b8c474c19623@[208.201.244.160] Peter Hessler [EMAIL PROTECTED] writes: : It looks like the make executable is bunk. I am using bsd make, not : gmake. Now I need to generate make w/o make. (yay!) Been there, done that, hated it. Your best bet is to grab one off a cdrom or some other machine... And check other binaries to see if there were other oopses. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pcmcia insert/remove/insert on boot?
In message: [EMAIL PROTECTED] Tim Kellers [EMAIL PROTECTED] writes: : I see that same message on the Dell latitude I'm using --with both the Dell : TrueMobile and the Orinoco Wavelan cards (both gold and silver). Apparently : is cause no trouble (that I've seen). If it didn't show up in red on my : console, I'd probably not have noticed it until I read a dmesg As far as I can tell, it is a benign bug for most people. I think that it comes from not masking a certain type of interrupt while the card is becoming ready, as the standard/mindshare books recommend. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: bizarre hanging at root mount
In message: 200203141601.LAA69821 [EMAIL PROTECTED] writes: : Hi Warner, I have an even stranger problem now. Lpd and syslogd : refuse to start from rc. I can start Lpd manually, but syslogd : won't. I wonder if this has anything to do with those kernel tuning : params. I went and CVSup'd and made world again, but to no avail. That's odd. I don't know what would cause this... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: PC-Card
In message: [EMAIL PROTECTED] Pete French [EMAIL PROTECTED] writes: : I just upgraded it to -STABLE and both problems have gone away. Cards work : fine both with ISA routing and PCI routing. Excellent, good work Warner! You are welcome. Hope that I don't break you again with 5.0. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: speeding up usb
In message: [EMAIL PROTECTED] Randy Bush [EMAIL PROTECTED] writes: : that usb umass hard drive is sloow. anything i can do? 200kB/s is the normal speed that you should expect on writes. There are faster CF cards available (usually listed as 4x or 8x on the box), but CF is slow to write. Also, the USB stack seems to be limited to about 400-500kB/s right now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: RELENG_4_? Branch Terminology
In message: [EMAIL PROTECTED] Christopher Schulte [EMAIL PROTECTED] writes: : 4.4-RELEASEp1 would be the 1st commit to RELENG_4_4 (aka the security : branch) after RELENG_4_4_0_RELEASE (4.4-RELEASE). commit here is subjective. Sometimes it can be multiple events that comprise a logical commit. But that is an excellent first order approximation. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Another Linksys WDT11 problem
In message: [EMAIL PROTECTED]
Brooks Davis [EMAIL PROTECTED] writes:
: On Mon, Jan 28, 2002 at 08:52:06PM -0600, Eric Liedtke wrote:
: Ok, from my last mail I got the card working fine. So it was time to
: tranfer it to a 3rd machine, my home router, as it's final resting place
: and I have run into a new problemI am getting a error message of
:
: wi0: mac read failed 5
:
: I poked around in the code a little bit, but couldn't come up with
: anything of use. I am not sure how to go about troubleshooting this from
: here, so any advice would be great. Thanks
:
: Ok, this is a bit of a shot in the dark, but what the heck. If you look
: for that error message in the driver, you'll find this comment:
:
: /*
: * Read the station address.
: * And do it twice. I've seen PRISM-based cards that return
: * an error when trying to read it the first time, which causes
: * the probe to fail.
: */
:
: My guess is that in some circumstances this hack isn't enough. The
: first thing to try would be stuffing a delay in between the two reads
: like so:
:
: wi_read_record(sc, (struct wi_ltv_gen *)mac);
: ---DELAY(50);
: if ((error = wi_read_record(sc, (struct wi_ltv_gen *)mac)) != 0) {
: device_printf(dev, mac read failed %d\n, error);
: wi_free(dev);
: return (error);
: }
:
: Try playing with the delay value a bit if that doesn't work.
Actaully, it should loop a few times reading it with a small delay
between each time. But this code seems very fragile. somethine else
in the system changes and it goes from working to non working.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: Firewall config non-intuitiveness
In message: [EMAIL PROTECTED] Nate Williams [EMAIL PROTECTED] writes: : If I enable the clutch in my car, my car moves (assuming it's in gear). : If I disable it, the power is no longer going to the drive wheels. That's not quite right, but it is a good analogy. If you disable your clutch, then you are going to have to shift without it and deal with putting it into gear at stops. If you enable your clutch, then you can use it to help in shifting. This isn't quite the same as what you said, and an analogous condition exists with the firewall rules. If you engage your clutch, then you can shift. If you disengage your clutch then your car will go if it is gear (and won't if it isn't). Also, when you enable apm, you aren't enabling power management. That's done in the BIOS. You are enabling the OS using the power management. If you set apm_enable to NO, then the OS doesn't enable power management, but at the same time it doesn't go down to the BIOS to turn off the power management settings in the BIOS. The effects in this case are almost identical, but some BIOSes will still spin down the hard disk, etc even when APM isn't engaged. When you say sendmail_enable=no, it doesn't prevent another mailer from binding to port 25. It just fails to start sendmail, which is the default behavior for the system. If you have sendmail_enable=NO, it doesn't go through and delete the mail queue, or make it impossible to run sendmail from a cron job. I'd argue that the firewall_enable is poorly named, but does the same thing. At most we should rename it to ipfw_maybe_load_ipfw_and_then_load_rules to be 100% correct. firewall_enable=YES means, right now: 1) If ipfw isn't in the kernel, load it. 2) load the rules firewall_enable=NO means do nothing. Same as when sendmail_enable=NO. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Firewall config non-intuitiveness
In message: [EMAIL PROTECTED] Crist J. Clark [EMAIL PROTECTED] writes: : Warner, if the proposed change were to be made, you could get the same : effect by doing, : : firewall_enable=YES : firewall_script=/dev/null : : Which I think more accurately describes the behavior you want (if : someone were to browse the rc.conf and try to understand your : configuration, they'd be more likely to understand what you are trying : to do if they saw the above). You want to enable firewalling, but : don't want to load any rules. But I don't want it to fail unsafely. That's the part that I still do not like about the change and why I'm making a big deal out of it. This is a security feature that you are proposing that we depart from our long standing tradition and make fail unsafely. rc scipts shouldn't take things out of the kernel that people have specifically compiled into the kernel. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Firewall config non-intuitiveness
In message: [EMAIL PROTECTED] Nate Williams [EMAIL PROTECTED] writes: : You still haven't responded to my comment that I have it setup like : this on some of my boxes so that I can do things that don't fit in : well with the current firewall paradigm. Nor to my comment that we : shouldn't be changing a security feature in a fail*UN*safe way. : : Explain to me how disabling the firewall with 'FIREWALL_ENABLE=NO' can : be unsafe? Because I have the firewall compiled into my kernel with the setting to not pass any packets. Due to some strange network stuff on my end, I don't load the actual rules until way late in the boot process, later than the normal firewall rules. I go from having the system not passing any packets, to the system passing only those that the firewall rules allow. Most of the reason I do this is because I have to get data on usage patterns from another system, and can't do that early enough in the boot process. The rules I have are dynamic based on how much bandwidth the coop has used so far this month and other conditions that change from time to time. Right now we do default route AFTER we load the firewall rules. However, the usage data is on another machine, not on my local segment. We've also found that the wireless link we have does better when bandwidth limited during bad weather (again, the data isn't on the router, but on another machine not on its local segment). Another reason would be because we would be communicating with a host that accepts only ipsec connections. This too happens after the firewall rules are added. While we don't do this today, it won't be too long into the future before we do do this. : Can you show me *ANY* system that uses a closed down firewall that also : has FIREWALL_ENABLE=NO? That would be the only 'safe-unsafe' : transition, since otherwise the default firewall setup is wide-open. rover.village.org has such a setup today. : I'll grant that I might be in the minority here, but I sure don't want : my the ability to use my firewall going away after my next : mergemaster change because you were helpful and unloaded/disabled : stuff for me. : : Fixing something that's broken is still fixing something. If you don't : want a firewall, then why have it activated and enabled? (This is a : rhetorical question.) Because I don't want the automatic firewall rules to happen at the place in the boot sequence where they happen now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
