Re: ffs_valloc: dup alloc panics with stable/current
On Fri, Dec 08, 2000 at 02:45:00AM -0800, Mike Smith wrote: > > We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it > > with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with > > three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). > > All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System > > is working quite well but under heavier load we start to get scsi > > errors from luns. > > sense = 4 asc = 3 asq = 0 > > sense = 1 asc = 3 asq = 0 > > sense = 3 asc = 12 asq = 0 > > sense = 3 asc = 11 asq = 0 > > Your disks just aren't up to this sort of workload. > > > This is not so bad but 5-30 minutes after this command system will > > always panic. > > cd /uu ; dump 0buf 126 - /w | restore xbf 126 - > > > > mode = 0100644, inum = 720391, fs = /uu > > panic: ffs_valloc: dup alloc > > This looks like memory or PCI data corruption. You don't say how you're > generating this load, or what the motherboard is, but I suspect that you > may have hardware issues here. PCI bus clock is at the nominal speed? Can be a source of interesting effects. -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** world build known broken
On Wed, Jan 03, 2001 at 10:35:48AM -0800, Matt Dillon wrote: > > :The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I > :suspected. I've got to head to an appointment, so the world will be broken > :for a little while. > : > > ( sky starts to fall as David O takes a coffee break at the local > starbucks, remarking merrily to other patrons who are staring out > the window in horror: "I did that!" ). Yikes.. if that is the case my vote is to hook David up to an IV caffeine drip.. ;-) -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fibre Channel "Hardware" List...
On Thu, Feb 08, 2001 at 08:44:33PM +0100, Andrei A. Dergatchev wrote: > "I have used lots of different Seagate and a few IBM drives and typically > have had few problems with them." - and absolutely nothing about single > channel vs dual channel, issues with putting them together etc ? > > What's up with "1026Gbit" - is it really true ? No, it should be 1.062 Gbit (the current fullspeed FC). Dual speed is coming soon. Don't ask for prices :-( -- | / o / / _ Arnhem, The Netherlandsemail: [EMAIL PROTECTED] |/|/ / / /( (_) Bultehttp://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Directory structure on current.freebsd.org
As p...@originative.co.uk wrote... > > -Original Message- > > From: Peter Jeremy [mailto:peter.jer...@auss2.alcatel.com.au] > > Sent: Wednesday, January 20, 1999 6:21 AM > > To: freebsd-current@FreeBSD.ORG > > Subject: Re: Directory structure on current.freebsd.org > > > > > > Oliver Fromme wrote: > > >In releases/snapshots they're called "axp" and "x86", while in > > >ports they're called "alpha" and "i386". > > > > I agree that having two different names is confusing. > > > > DEC (or Compaq) literature seems to use both Alpha and AXP - I'm not > > sure that either is an especially better choice. Officially it is Alpha AXP. Alpha was too generic to be trademarked. > > I personally find "i386" a pain because it is used to specify both an > > architecture (IA-32) and a particular implementation (80386) of that > > architecture. In some cases it may not be clear which is meant. > > I think the architecture names are more appropriate than any cpu related > name. For the alpha, while we might all use alpha in everyday speech axp > is more specific when it comes to releases since the alpha release of Hear hear ;-) > the alpha code can get a tad confusing, I think that's why it was > changed in the first place. It'd be nice if i386 could become IA32 but > it probably won't happen. Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: boot.flp versions
As Joao Carlos Mendes Luis wrote... > #define quoting(Jordan K. Hubbard) > // All: Sorry the boot.flp has been broken for this long, but I've had > // other distractions lately. I will make it work once more, somehow > // or other, and just keep your eyes on current.freebsd.org over > // the next few days. When it returns to 1.44MB in size again, give > // it a try. :) > > Another problem I had with that snap here is that it does not install > on a machine with 8M RAM. It started installing, but stopped in > random places during file copy. It did work after I remade the > kern.flp with only the devices I had (thus, using less memory). > > I noticed that swapping was disabled in the BOOTMFS kernel. Is this > really necessary ? How hard is to add an option "use this swap > partition during install", or even a "create and use a vn swap file in > /usr/tmp during install" ? > > Or should I just assume 8M RAM machines are not any more supported ? What grew so drastically that the memory requirements grew from 5 Mbytes minimum memory to > 8Mb? (remember all those discussions when 4Mb became too small to run the install floppy?) Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: panic: found dirty cache page 0xf046f1c0
As Matthew Dillon wrote... > I've committed one bug fix to the 'found dirty cache page' bug -- > turns out vm_map_split() was the culprit, renaming pages > without removing them from PQ_CACHE. The bug was introduced > in -3.0, and hit the KASSERT() I put in -4.x. > > I've committed a general inlining of 'changing the page dirty > status to VM_PAGE_BITS_ALL' and put a sanity check in the inline. > If this problem occurs again, you will get a different panic. > One of: > > vm_page_dirty: page in cache! > vm_page_busy: page already busy!!! > vm_page_wakeup: page not busy!!! > > If your box drops into DDB, please get a backtrace and report > it to the list or to me and we should be able to track down > any remaining dirty-pages-in-PQ_CACHE bugs. FYI: a buildworld of -current including the above on FreeBSD/axp completed without any incidents. Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: 2Re: panic: found dirty cache page 0xf046f1c0
As Alfred Perlstein wrote... > On Sat, 23 Jan 1999, Matthew Dillon wrote: > > i have 'ed' driver and mine blows up as well. > > > :Here too... pretty quickly after boot on a SMP machine (current as of Jan > > :12) that pushes quite a bit of traffic, the following messages appear: > > : > > :de0: abnormal interrupt: transmit underflow (raising TX threshold to > > 96|256) > > :de0: abnormal interrupt: transmit underflow (raising TX threshold to > > 128|512) > > :de0: abnormal interrupt: transmit underflow (raising TX threshold to > > 160|1024) I have seen these messages on both Freebsd/x86 and /axp with single CPU machines. Almost all of them disappeared when I started using decent UTP cabling. Believe it or not. So, I'd say the messages are not linked to SMP at all. > > : > > :de0: rev 0x22 int a irq 16 on pci0.12.0 > > :de0: 21140A [10-100Mb/s] pass 2.2 > > :de0: address 00:c0:f0:1f:5d:0d > > :de0: enabling Full Duplex 100baseTX port> > > Three people getting these panics, three people with DEC ethernet > > cards. Random complaints about card during ifconfig: speaker goes > > click, > > console gets junked, etc etc etc. > > > > > s there anyone having this panic who does NOT have a DEC ethernet > > card ? Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DEVFS, the time has come...
As Archie Cobbs wrote... > Doug Rabson writes: > > And another thing. Why can't we use a non-driver-specific name for the > > disk? Most users simply don't care whether the driver was fd, wfd, wd or > > anything. They just want to get to their files without any fuss. > > I agree.. and same thing goes for Ethernet drivers. I actually > like the way Linux always has "eth0", "eth1", ... (which we could Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this just a matter of taste or is there more to it? I for one don't see any advantage in eth[0-9] style device naming. Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DEVFS, the time has come...
As sth...@nethelp.no wrote... > > > I agree.. and same thing goes for Ethernet drivers. I actually > > > like the way Linux always has "eth0", "eth1", ... (which we could > > > > Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this > > just a matter of taste or is there more to it? I for one don't see any > > advantage in eth[0-9] style device naming. > > I can give you one example. We run a FreeBSD box here which receives > all of the traffic (port mirroring) from some Ethernet switches. On > the FreeBSD box, we run nnstat, tcpdump etc. for monitoring purposes. > > Recently I changed some of the DEC 21x4x based cards on this box to > Intel cards. Thus the interface names changed from deN to fxpN. This > meant we had to update a bunch of Perl and shell scripts. It would > have been much nicer (no need to update) if the interfaces were simply > named ethN. Hmmm. Well I happen to like the concept of being able to tell straight away what device I'm talking to. eth# style naming does not allow that. But I can understand that other people might feel otherwise. Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DEVFS, the time has come...
As Daniel O'Connor wrote... > On 27-Jan-99 Wilko Bulte wrote: > > > I agree.. and same thing goes for Ethernet drivers. I actually > > > like the way Linux always has "eth0", "eth1", ... (which we could > > Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this > > just a matter of taste or is there more to it? I for one don't see any > > advantage in eth[0-9] style device naming. > Well, for one its sucks trying to get newbies to work out what their network > card is > called.. Not true IMO. You still need to know what hardware you have before you can build your own kernels etc etc. > Also the eth[0..x] thing means you can replace your ethernet card with a new > one of a > different type without having to look through your config code for references > to ed0 or > whatever. True. > Another thing.. we get to be more Linux like, which is a good thing, right? > *duck* Ducking does not help with todays laser-guided precision ammo ;-) ;-) And to answer your question: the day FreeBSD aims to become like Linux I'm likely to install NT. Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/i386/eisa ahb.c
As Jordan K. Hubbard wrote... > > How Mr. ignoromous Nate could construe this to mean that I was trying > > to brush something under the rug is beyond me. As I said to Julian, > > I probably shouldn't have made the committ, but the fact is that I > > not only left the module on my hotlist, I also immediately brought > > the potential problem to the attention of the entire list and thence, > > I think this whole tangled thread can probably be summed up thusly: > > There will always be those remarking from the sidelines about any > change which goes into the FreeBSD source tree, and I do mean ANY > change, the amount of commentary usually in inverse proportion to the > importance of the change. This is just a given. It's also a given > that some of these people will have far less clue than others and even > those who have a clue will often express their comments in such a way > as to come across as criticising or carping, even though they may not > have meant to. There are a lot of engineers here and human > interaction is rarely their strong suit. > > In any case, rather than getting into a protracted furball with each > and every commentator and perhaps using inappropriate language in a > public mailing list in the process, you've gotta do what pro golfers > and ballplayers do - learn to ignore the crowd when it hasn't got Ah, you mean like John McEnroe ? ;-) Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DEVFS, the time has come...
As David Wolfskill wrote... > >From: Wilko Bulte > >Date: Wed, 27 Jan 1999 23:12:18 +0100 (CET) > > >Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this > >just a matter of taste or is there more to it? I for one don't see any > >advantage in eth[0-9] style device naming. > > It's a matter of whether you want the name to reflect the implementation > vs. the function. > > For someone involved in the details of the implementation, being > (acutely!) aware of those details can be very important. Guilty your honor ;-) My daily work is in supporting customers, so I can really do without mapping 'convenient names' to physical stuff. For an example: look at the Solaris symlink jungle for device naming. > For someone who merely wants to have a certain physical port on the > machine connected to a particular network, that level of detail is not > always appropriate. > > It depends on your focus. Agreed. Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: make release - Party Time! (but not for the AXP)
As Jordan K. Hubbard wrote... > > Unfortunately the AXP is still hosed :( > > Hmmm. Let me look at this - I may have failed to adjust one of the > constants for the AXP case. Sidestepping a bit: will there be AXP specific CDROMs in the WC CDROM distribution? Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: ifq_maxlen problem...
As Open Systems Inc. wrote... > On Thu, 4 Feb 1999, Jaroslaw Bazydlo wrote: > > > After yesterdays 'make world' I am having such warnings: > > > ep0 XXX: driver didn't set ifq_maxlen > > lo0 XXX: driver didn't set ifq_maxlen > > ^ > > The system itself seems to work fine (for last 24 hrs). What do those > > messages mean??? Does anyone of you noticed similar messages??? > > I get the same thing for my kingston DEC based 10/100 card and lo0. > The card still works though so the chance of this being life threatening > are low :-) Interesting. I have the same Kingston 10/100 and I've never seen it. YMMV obviously. Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: 5.0 Freezes under high load with SMP.
On Tue, Jan 14, 2003 at 11:12:30AM -0800, Nate Lawson wrote: > On Tue, 14 Jan 2003, wade wrote: > > Although GENERIC functions perfectly, when I enable SMP in GENERIC, the box > > freezes during big build jobs ( i.e. buildworld. ). This box functioned > > well in SMP mode und 4.7-STABLE. The big problem is that freezing does not > > leave core files or any other debugging information. > > > > Hardware: > > ASUS CUV4X-D > > 2 X PIII 600 MHz Coppermine. > > 512 MB 133MHz RAM. > > Hit ctl-alt-esc on console to enter DDB (enable this kernel option if you > haven't already). Type "trace" to find out what is hung. If this doesn't > work, attach a serial console and do a break there and "trace". Interesting, as I have been trying the last 3 days to reproduce freezes that people reported on 5.0 on (specifically) the ASUS BP6 mainboard. I ran continuous make -j16 buildworlds to see if I could break it, but no luck (or very good luck, depends on your perspective ;-) -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0 Freezes under high load with SMP.
On Tue, Jan 14, 2003 at 11:51:36AM -0800, Nate Lawson wrote: > On Tue, 14 Jan 2003, Wilko Bulte wrote: > > On Tue, Jan 14, 2003 at 11:12:30AM -0800, Nate Lawson wrote: > > > On Tue, 14 Jan 2003, wade wrote: > > > > Although GENERIC functions perfectly, when I enable SMP in GENERIC, the box > > > > freezes during big build jobs ( i.e. buildworld. ). This box functioned > > > > well in SMP mode und 4.7-STABLE. The big problem is that freezing does not > > > > leave core files or any other debugging information. > > > > > > > > Hardware: > > > > ASUS CUV4X-D > > > > 2 X PIII 600 MHz Coppermine. > > > > 512 MB 133MHz RAM. > > > > > > Hit ctl-alt-esc on console to enter DDB (enable this kernel option if you > > > haven't already). Type "trace" to find out what is hung. If this doesn't > > > work, attach a serial console and do a break there and "trace". > > > > Interesting, as I have been trying the last 3 days to reproduce freezes > > that people reported on 5.0 on (specifically) the ASUS BP6 mainboard. > > > > I ran continuous make -j16 buildworlds to see if I could break it, but > > no luck (or very good luck, depends on your perspective ;-) > > That's an Abit BP6, different from this Asus mobo. :) Yes, I know ;) -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unexpected machine check on 5.0 alpha
On Wed, Jan 15, 2003 at 02:19:19PM -0800, Kris Kennaway wrote: > On Wed, Jan 15, 2003 at 05:15:56PM -0500, Andrew Gallatin wrote: > > > > Kris Kennaway writes: > > > I just got this on one of the axp machines [*]: > > > > > > unexpected machine check: > > > > > > mces= 0x1 > > > vector = 0x670 > > > > 670 is a "cpu machine check" -- thats most likely an uncorretable > > memory parity error or some other (intermittent) hardware failure > > caused by overheating, etc. > > > > This is what? A miata? > > Yes. Time to check the fan for the CPU, and the air'tunnel' feeding the air to the heatsink. I had one come loose after servicing the machine. Impractical.. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: disklabel(8): men at work.
On Sun, Jan 26, 2003 at 03:47:11PM +0100, Poul-Henning Kamp wrote: > > I'm still not done with disklabel(8), and I have not run it through > all the tests I want (I'm waiting for my glacial 233MHz EV45 alpha > to compile a world) so be careful what you do with disklabel and in > particular the -B option. Time to put a DS10 on wantlist.sgml I suppose? ;) -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: where is MAKEDEV
On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote: > Hi, > > I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now > everything seems OK, but my sound card. In the handbook they say I must > use the MAKEDEV script (as in Linux) but I can't find it on my disk. > I tried to download it with the sysinstall tool but again there seems to > be no package available. > > What can I do? Read the docs/mailing list archives? ;-) Kidding aside: -current uses devfs, which makes MAKEDEV obsolete. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Force 1 CPU on SMP kernel?
On Tue, Jan 28, 2003 at 12:33:32PM -0500, Andre Guibert de Bruet wrote: > > > On Tue, 28 Jan 2003, Adam Migus wrote: > > > Yes, just to be more explicit. What I want to do is get the > > 'real' difference a second processor makes. ie. If I run > > GENERIC I'm not incurring the overhead associated with SMP/APIC. > > I want to use the same kernel making as small a change as > > nessessary to have the machine start/use just one CPU. > > I'm not aware of any hacks to disable APs through loader.conf. If you're > trying to benchmark the system's performance with 1 vs N CPUs, you're best > off pulling all but the BSP CPU out of the machine. For such a benchmark > to be accurate, you shouldn't make any software changes (kernel, daemons > or startup configs). VOlunteers to implement psradm maybe? W/ -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem
On Sat, Feb 15, 2003 at 10:37:26PM +0100, [EMAIL PROTECTED] wrote: > In message <[EMAIL PROTECTED]>, Makoto Matsushita writes: > > > >I've tried to do "make release" of FreeBSD/alpha on FreeBSD/i386 box > >last night, and found that follow error while generating drivers.flp: > > > >If my understandings are correct, this is because disklabel(8) kicked > >is FreeBSD/i386 native binary which doesn't know about FreeBSD/alpha > >disklabel structure or whatever. > > > >Are there any workaround/fix? > > Not yet. I think adding a "-m architecture" flag to disklabel is the > way around this problem, but have not had time to do so. But now that you have an alpha machine... ;-) -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wi0 - need help
On Sat, Mar 01, 2003 at 08:08:36PM +0100, Christoph P. Kukulies wrote: > On Sat, Mar 01, 2003 at 11:35:37AM -0700, M. Warner Losh wrote: > > > It works! > Packets started flowing right after I typed in the above line. > > > > > and > > > > ifconfig wi0 192.168.254.2 netmask 255.255.255.0 ssid kuku stationname \ > > kukulap media DS/11Mbps mediaopt adhoc[*] > > > > [*] adhoc is spelled ibss-create on 4.x > > > > Warner > > How can I find out whether I can run the interface in hostap mode? > At the moment it runs in adhoc mode. If you try ifconfig hostap and the card is not capable of doing that (wrong chipset e.g) it will give you an error. Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IP over IEEE1394?
On Wed, Mar 05, 2003 at 07:25:20AM -0600, David Leimbach wrote: > Interesting... I didn't even know we had Ethernet over firewire :). > > Mac OS X and Windows XP both have IP over firewire either working or > in the works and somewhat usable. The only one I can claim any > experience > with is Mac OS X. It's somewhat flaky though and you get unreliable > spikes > in some basic performance tests I have done with it. > > It would be a really interesting value added feature for FreeBSD 5.x > and could potentially open FBSD up even more to the "cluster" market > which is somewhere its not as proliferated as linux. > > With the advent of firewire2 on the horizon it may be even more > impressive. The interconnect is just 10% of the whole cluster story. Firewire is one possibility, but Fibrechannel you could do today if you wanted to. We have Fibrechannel support in the Qlogic isp(4) driver (thanks Matt!) today. W/ -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Removal of netns
On Tue, Mar 04, 2003 at 07:56:27AM -0800, Terry Lambert wrote: > Tim Robbins wrote: > > Is there a compelling reason why I shouldn't remove netns? That is, does > > it serve a purpose now that it could not serve if it was moved to the > > Attic? > > Might as well move /sys/i386/conf/GENERIC to the attic while > you are at it. It can serve it's purpose from there, too. > > Is there a compelling reason for doing this, other than "I > want to make some API/locking change, but I don't want to > have to keep this code working at the same time"? Maximizing Is there a compelling reason for you to moan about the removal of things constantly? -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Official request: Please make GNU grep the default
Op 18 aug. 2010 om 18:48 heeft Gabor Kovesdan het volgende geschreven: > Em 2010.08.13. 10:43, Doug Barton escreveu: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> Gabor, >> >> I hope at this point it goes without saying that I have a lot of respect >> for the work you've done on BSD grep, and I've already told you that I >> think you're very courageous for taking the project on. I've been >> testing and evaluating it for some time now, and I think I've given it a >> fair trial. You've done a fairly good job of responding to bug reports, >> and I understand that the exposure BSD grep has received as the default >> in HEAD has been very valuable in exposing additional areas that need >> work. However, with all that in mind I am officially asking you to >> please change the default in HEAD to GNU grep. (Note, I am _not_ asking >> you to remove BSD grep from the tree, just to change the default.) >> >> My reason is simple, performance. [...] > > I've just committed a patch with the kind help of Dimitry Andric, which gives > BSD grep a huge performance boost. The performance is now almost comparable > to GNU grep. I think with this, BSD grep may remain default if no other > serious issues come up. Please report if you notice something weird. > > I know about some minor issues, which aren't fixed yet. I'll be out for 4 > days as of tomorrow but when I come back I'll take care of these: > - Infinite loop when reading directory on ZFS/NFS filesystem > - Problems with context grepping > > When reply, please remove core@ from CC, let's not bother them with this, I > just wanted to let them know that I'm not neglecting this issue but if still > demanded for a good reason, No worries there Gabor! Wilko > I'll switch back to default GNU grep. > > Gabor > > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: We have ath, now what about Broadcom?
On Wed, Jul 23, 2003 at 06:21:23PM -0400, Matthew Emmerton wrote: > > > Folks, ... > > > Can anyone provide some pointers or links that would bring me > > > up-to-date on the current state of affairs on this subject, > > > especially as it related to FreeBSD or *BSD in general? > > > > The folks at Broadcom have not been willing to release any information > > on their 800.11g chips for fear of violating FCC regs. The required > > NDA would prohibit the release of the source. You can program > > both the transmit power and frequency if you have this. (I make no > > claim as to whether their concerns have any validity.) > > > > For that reason there has been no open-source support for these chips. > > Why would Broadcom be scared? Obviously it's the _driver_ that controls the > power/freq output of the chip, so the responsibility of staying within FCC > regs is that of the driver authors. Of course, the "no warranty" aspects of > open source drivers turns a blind eye to liability, but would things really > come back to Broadcom? Simple: ETOOMANYCORPORATELAWYERS is most likely the culprit.. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 01:07:46PM +0100, Mark Murray wrote: > Hi > > Latest boot on my Alpha breaks thus: > > real memory = 266371072 (254 MB) > avail memory = 250863616 (239 MB) > cia0: <2117x Core Logic chipset> > cia0: ALCOR/ALCOR2, pass 3 > cia0: extended capabilities: 21 > pcib0: <2117x PCI host bus adapter> on cia0 > pci0: on pcib0 > eisab0: at device 7.0 on pci0 > > halted CPU 0 > > halt code = 7 > machine check while in PAL mode > PC = 18100 > >>> > > Any idea what gives? Not really, but as a datapoint today's -current does work OK on a EISA-less machine. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 05:31:27PM +0100, Mark Murray wrote: > Wilko Bulte writes: > > > halt code = 7 > > > machine check while in PAL mode > > > PC = 18100 > > > >>> > > > > > > Any idea what gives? > > > > Not really, but as a datapoint today's -current > > does work OK on a EISA-less machine. > > GENERIC kernel also has above error. > > Remove eisa, and the boot goes straight to panic (no clock). That is because your clock sits behind eisa I think. ticso recently posted some days ago that eisa is now mandatory on alpha. I did not follow in detail to be honest. Check the archives. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Alpha/EISA broken?
On Fri, Jul 25, 2003 at 07:02:09PM +0200, Bernd Walter wrote: > > eisab0: at device 7.0 on pci0 > > > > halted CPU 0 > > > > halt code = 7 > > machine check while in PAL mode > > PC = 18100 > > >>> > > > > Any idea what gives? > > Sounds like an SRM problem or EISA configuration problem. > Normaly the bus and then system board should be probed at this point. > We never used EISA on alpha before - EISA bridge support was only > conditionalisized on pci. Which triggers me: did you run the ECU? A copy is at: ftp://ftp.tcja.nl/pub/wilko/alpha > In case something is wrong with your eisa setup. > Eisa configuration has to be done via alphabios. Do 'runecu' from the SRM console and it should work. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3Com 3C9340 (3C200) support
On Thu, Jul 24, 2003 at 02:23:01AM -0400, Nathan Binkert wrote: > > I own an Abit IS7-G which includes an intergrated 3Com 3C940 card > > currently not supported in any FreeBSD branch to my knowledge. Some > > people said that the nic could world with the Tigon III driver but I > > haven't been able to get it to work with it during install. Are there > > any plans or projects to get this card supported in the near future? A > > Linux driver is provided by 3Com. Thanks in advance for your time. > > In the next few days, I will be committing support for this chip to the > OpenBSD sk driver. Our sk driver was based on the freebsd, so it will be > simple to backport. Can you please be so kind to send a short headsup when you are done? I'm planning on getting your work integrated once you have the OpenBSD driver updated. (I'm lazy, I admit ;) -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Alpha/EISA broken?
On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote: > Wilko Bulte writes: > > > Sounds like an SRM problem or EISA configuration problem. > > > Normaly the bus and then system board should be probed at this point. > > > We never used EISA on alpha before - EISA bridge support was only > > > conditionalisized on pci. > > > > Which triggers me: did you run the ECU? > > > > A copy is at: > > > > ftp://ftp.tcja.nl/pub/wilko/alpha > > I have this now. It looks like something I dd(1) onto a floppy? yessir -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Alpha/EISA broken?
On Thu, Jul 31, 2003 at 02:03:12PM +0100, Mark Murray wrote: > Wilko Bulte writes: > > On Thu, Jul 31, 2003 at 01:40:28PM +0100, Mark Murray wrote: > > > Wilko Bulte writes: > > > > > Sounds like an SRM problem or EISA configuration problem. > > > > > Normaly the bus and then system board should be probed at this point. > > > > > We never used EISA on alpha before - EISA bridge support was only > > > > > conditionalisized on pci. > > > > > > > > Which triggers me: did you run the ECU? > > > > > > > > A copy is at: > > > > > > > > ftp://ftp.tcja.nl/pub/wilko/alpha > > > > > > I have this now. It looks like something I dd(1) onto a floppy? > > > > yessir > > :-) > > And then do what with? Boot off it? run it from the bios? >>> runecu from SRM. Better have a VGA card installed. Serial console is possible to but is a bit (hum..) of a challenge. -- | / o / /_ _ FreeBSD core team secretary |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
crash when bringing up fddi interface
I added a DEC DEFPA PCI FDDI card to my Alpha.
When ifconfig fpa0 I am greeted by the following
panic:
fatal kernel trap:
trap entry = 0x2 (memory management fault)
cpuid = 2
faulting va= 0x53c443f891b8
type = access violation
cause = load instructon
pc = 0xfc4addc8
ra = 0xfc4ad3ac
sp = 0xfe0039dfd970
usp= 0x11fffa70
curthread = 0xfc0006acba20
pid = 571, comm = ifconfig
Stopped at rt_maskedcopy+0x18: ldq_u t0,0(a2)
<0x53c443f891b8>
db> tb
No such command
db> bt
No such command
db> tsa^H ^H^H ^Hrace
rt_maskedcopy() at rt_maskedcopy+0x18
rtrequest1() at rtrequest1+0x39c
rtinit() at rtinit+0x250
in_ifinit() at in_ifinit+0x6d4
in_control() at in_control+0x918
ifioctl() at ifioctl+0x2b4
soo_ioctl() at soo_ioctl+0x290
ioctl() at ioctl+0x750
syscall() at syscall+0x3b8
XentSys() at XentSys+0x64
--- syscall (54, FreeBSD ELF64, ioctl) ---
--- user mode ---
db>
So, something appears to go wrong in:
static void
rt_maskedcopy(src, dst, netmask)
struct sockaddr *src, *dst, *netmask;
{
register u_char *cp1 = (u_char *)src;
register u_char *cp2 = (u_char *)dst;
register u_char *cp3 = (u_char *)netmask;
u_char *cplim = cp2 + *cp3;
u_char *cplim2 = cp2 + *cp1;
*cp2++ = *cp1++; *cp2++ = *cp1++; /* copies sa_len & sa_family */
cp3 += 2;
if (cplim > cplim2)
cplim = cplim2;
while (cp2 < cplim)
*cp2++ = *cp1++ & *cp3++;
if (cp2 < cplim2)
bzero((caddr_t)cp2, (unsigned)(cplim2 - cp2));
}
My other DEFPA lives in a BP6 x86 box and is not panicing.
Suggestions?
W/
--
| / o / /_ _ [EMAIL PROTECTED]
|/|/ / / /( (_) Bulte
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SAN disk with freebsd?
On Sun, Aug 10, 2003 at 06:53:09AM +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes: > >Anyone using a storage area network with freebsd (or linux)? Anything to > >recommend as working well or to stay way from? > > I have a customer doing that. Is this your customer running the DEC^WCompaq^WHP HSG80 raid array? > Works ok. > > You need qlogic 2300 cards and the isp driver which Matt Jacob maintains. Qlogic 2200 should also work (but is 1Gbit only) Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM/vinum compatibility (was: vinum lock panic at startup-current)
On Sat, Aug 09, 2003 at 06:38:51AM +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey" > writes: > > >> and it seems that vinum does not respect the D_NOGIANT flag which > >> GEOM recently started setting. > > > >Probably because it didn't know about it. As I've said before, it > >would be nice to be informed about the changes you're making, > >particularly given your stated intention of doing no work on Vinum. > > I had the choice between supporting sos@ effort to de-Giantize ATA > or wait for the non-maintainer of vinum to possibly react to his email Come on.. a bit of politeness goes a long way.. > so I chose the former as being more beneficial to the project. W/ -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: driver maintainers, please help
On Thu, Aug 14, 2003 at 09:45:27AM -0700, David O'Brien wrote: > On Wed, Aug 13, 2003 at 03:11:35PM +0200, Lukas Ertl wrote: > > this is a call for help from the various driver maintainers. In a recent > > discussion on -doc it has come out that several manpages are not in sync > > with what's listed in the 5.1 Hardware Notes, > > We also have several drivers in 5.1 that don't even have man pages. :-( "Reference to documentation is the hallmark of the coward" ;) But you are right of course... -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best Known Methods for dual booting WinXP + -current
On Thu, Aug 07, 2003 at 06:49:55PM -0700, David O'Brien wrote: > On Thu, Aug 07, 2003 at 03:40:27PM -0500, Cagle, John (ISS-Houston) wrote: > > Had to use FFS filesystem since Grub doesn't support UFS. > ^^^ > UFS1 ^^^ UFS2 -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mergemaster b0rked?
for i in answer isdntel.sh record tell tell-record unknown_incoming ; do install -o -g -m 700 $i /var/tmp/temproot/etc/isdn ; done ; for i in holidays.Disdnd.rates.Aisdnd.rates.D isdnd.rates.F isdnd.rates.L isdnd.rates.UK.BT isdnd.rc.sample isdntel.alias.sample ; do install -o -g -m 600 $i /var/tmp/temproot/etc/isdn ; done install: -g: Invalid argument *** Error code 67 Stop in /usr/src/etc/isdn. *** Error code 1 Stop in /usr/src/etc. *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the temproot environment # ?? This is on Alpha btw. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mergemaster b0rked?
On Mon, Aug 18, 2003 at 04:19:22PM -0400, Craig Rodrigues wrote: > On Mon, Aug 18, 2003 at 07:05:54PM +0200, Wilko Bulte wrote: > > for i in answer isdntel.sh record > > tell tell-record unknown_incoming ; do > > install -o -g -m 700 $i /var/tmp/temproot/etc/isdn ; done ; for i in > ^^ > > Why doesn't the -g flag have a GID as an argument? Because it seems that BINGRP and BINOWNER are undefined. > > install: -g: Invalid argument > > *** Error code 67 > > -- > Craig Rodrigues > http://crodrigues.org > [EMAIL PROTECTED] > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ---end of quoted text--- -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [current tinderbox] failure on alpha/alpha
On Wed, Aug 20, 2003 at 01:59:42PM -0400, Andrew Gallatin wrote: > > Tinderbox writes: > > > cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DIN_GCC -DHAVE_CONFIG_H > -DPREFIX=\"/usr\" > -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../cc_tools > > -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../cc_tools > > -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc > > -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/config > > -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f > -I. -c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/contrib/gcc/f/stc.c > > cc1: error: invalid option `tune=ev5' > > cc1: error: invalid option `ieee' > > cc1: error: bad value (ev4) for -mcpu= switch > > I assume that this is a crossbuild problem? FWIW on a true alpha buildworld ran fine last night. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: > Hi, > > I ported the openbsd additions to the sk driver to support the 3c940 > gigabit network card which is commonly found in the above asus > motherboard. Testers/comments/commits welcome, but please don't blame > me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: > On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: > > On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: > > > Hi, > > > > > > I ported the openbsd additions to the sk driver to support the 3c940 > > > gigabit network card which is commonly found in the above asus > > > motherboard. Testers/comments/commits welcome, but please don't blame > > > me if it burns your house down or something :) > > > > Hi Stuart, > > > > I tried this patch instead of the earlier ones you pointed me to on IRC. > > > > Unfortunately my Asus P4P800 still locks up solid (reset button required) > > after printing the 3c940's ethernet address. > > > > I'm interested to know if other P4P800 owners have the same issue. > > > > Wilko > > > Hi Wilko, > > Sorry to hear you are still having trouble. Thus far I have only been > able to find one other person to test the driver and for him it works > perfectly(also a P4P800). Right, that is a valuable datapoint. > Are you running up do date -current, or is there anything strange about > your setup at all? Not that I know, but given that it works for another P4P800 I can find out what is special locally. W/ -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: > On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: > > On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: ... > > Unfortunately my Asus P4P800 still locks up solid (reset button required) > > after printing the 3c940's ethernet address. > > > > I'm interested to know if other P4P800 owners have the same issue. > > > > Wilko > > > Hi Wilko, > > Sorry to hear you are still having trouble. Thus far I have only been > able to find one other person to test the driver and for him it works > perfectly(also a P4P800). > > Are you running up do date -current, or is there anything strange about > your setup at all? I just did a buildworld on a freshly checked out tree, applied the patches and tried again. Unfortunately that did not help. I continue my investigation. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 12:17:52PM +, Jens Rehsack wrote: > Stuart Walsh wrote: > >On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: > > > >>On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: > >> > >>>Hi, > >>> > >>>I ported the openbsd additions to the sk driver to support the 3c940 > >>>gigabit network card which is commonly found in the above asus > >>>motherboard. Testers/comments/commits welcome, but please don't blame > >>>me if it burns your house down or something :) > >> > >>Hi Stuart, > >> > >>I tried this patch instead of the earlier ones you pointed me to on IRC. > >> > >>Unfortunately my Asus P4P800 still locks up solid (reset button required) > >>after printing the 3c940's ethernet address. > >> > >>I'm interested to know if other P4P800 owners have the same issue. > >> > >>Wilko > >> > > > >Hi Wilko, > > > >Sorry to hear you are still having trouble. Thus far I have only been > >able to find one other person to test the driver and for him it works > >perfectly(also a P4P800). > > Hi Guys, > > I have 2 machines with P4P800-Deluxe with the 3C940. If phk@ could fix > the swap-issue, so that I can reboot easily, I would test your patches, > too. Que? What swap issue? I can dual boot stable and current just fine on the P4P800. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun, Aug 24, 2003 at 03:13:18PM +0200, Wilko Bulte wrote: > On Sun, Aug 24, 2003 at 12:35:01PM +0100, Stuart Walsh wrote: > > On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: > > > On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: > > ... > > > > Unfortunately my Asus P4P800 still locks up solid (reset button required) > > > after printing the 3c940's ethernet address. > > > > > > I'm interested to know if other P4P800 owners have the same issue. > > > > > > Wilko > > > > > Hi Wilko, > > > > Sorry to hear you are still having trouble. Thus far I have only been > > able to find one other person to test the driver and for him it works > > perfectly(also a P4P800). > > > > Are you running up do date -current, or is there anything strange about > > your setup at all? > > I just did a buildworld on a freshly checked out tree, applied the patches > and tried again. > > Unfortunately that did not help. I continue my investigation. Going to the latest BIOS also did not make any difference (long shot, I know). Can someone with a P4P800 who has gotten it to work please post their dmesg? Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: src/gnu/usr.bin Makefile src/lib Makefile src/sbinMakefile src/usr.bin Makefile src/usr.sbin Makefile
On Sat, Aug 30, 2003 at 02:55:32PM +0200, Andreas Klemm wrote: > On Sat, Aug 30, 2003 at 03:46:53AM -0700, Doug Barton wrote: > > On Sat, 30 Aug 2003, Poul-Henning Kamp wrote: > > > > > In message <[EMAIL PROTECTED]>, Doug Barton writes: > > > >Poul-Henning, > > > > > > > >Please don't forget to update src/share/examples/etc/make.conf > > > >accordingly. > > > > > > Hmm, so this stuff is documented both in make.conf(5) and an examples > > > file ? Sounds like one place too many to me. > > > > Well, there's "always" been an example make.conf file. In previous > > incarnations it's lived in /etc, then /etc/defaults. I also agree with > > the previous poster that it's useful to have such an example, and > > mergemaster uses it for the -p option. > > In former times the make.conf file has been installed in /etc > when doing a fresh FreeBSD installation. It contained useful > commented out options. > > If memory serves me right, the file isn't installed anymore > by default. Is there a reason ? I regarded this as useful > tro have it around under /etc, so to say "ready for use". See /etc/defaults/make.conf -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Fri, Sep 05, 2003 at 07:50:24PM +0100, Stuart Walsh wrote: > On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: > > Hi again chaps, > > I've been working on other things lately, including getting ready to > move house and looking after my 3 month old daughter :) but recently I've Changing nappies? ;) > took up trying to get this driver working again. If anyone is interested in > helping out, could they give http://stu.bash.sh/if_sk.c and > http://stu.bash.sh/if_skreg.h a try and let me know what output you get. > I'm only really interested in what happens after the MAC gets printed so > don't go to too much trouble to get the exact info. > > Just plonk the files in /usr/src/sys/pci over the top of the old ones. > Thanks to anyone who helps out. OK.. what it does is as follows: - print ethernet address - then it prints: Yukon chip detected Phy type 4 adr 0 initialising yukon device phy reset set mac reset set mac reset clear mac reset set This all on an Asus P4P800. Obviously a copper based NIC, without cable connected in this case. hth Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat, Sep 13, 2003 at 03:37:51PM +0100, Stuart Walsh wrote: > On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote: > > I have my own *working* driver, which is for 4-STABLE. It works with > > SK-9521 V2.0 (for me, at least) and it should work with 3C940. > > > > Note: This driver is ported from Nathan L. Binkert's OpenBSD driver. > > Note: This is completely independent from Stuart Walsh's work. ;-) > > Note: You must recompile MII driver and dependent network drivers. > > > > It's worth noting my patch was a port of Natan's patch also(which is actually > Bill's driver technically speaking ;), so I'd be interested to see where i > went wrong. But if it works then great, I'll get on with something else :) > It's somewhat difficult to fine tune a driver when you dont actually own > the hardware in question. I just tried Jung-uk Kim's driver on -stable and sofar it works OK: pcib2: at device 30.0 on pci0 pci2: on pcib2 skc0: <3Com 3C940 Gigabit Ethernet> port 0xd400-0xd4ff mem 0xfeaf8000-0xfeafbfff irq 11 at device 5.0 on pci2 skc0: 3Com Gigabit LOM (3C940) sk0: on skc0 sk0: Ethernet address: 00:0c:6e:4f:77:0c miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 1000baseTX-FDX, 100baseTX-FDX, 100baseTX, 10baseTX-FDX, 10baseTX, auto isp0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 10 at device 9.0 on pci2 This is with the LOM found on Asus P4P800 btw. Curious minds obviously wonder about the difference with Stuart's driver ;) ENOTIME to check right now. Sleep first. Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Gcc 3.2.2 vs gcc 3.2.3
On Mon, Sep 22, 2003 at 02:25:27PM +, Holger Kipp wrote: > > > Justin Smith ([EMAIL PROTECTED]) wrote: > >I'm running a P4 2.4 Ghz processor with 512meg of ram. > > > >I've had the problem of getting signal 11 and signal 4 when I make > >buildworld and buildkernel. > > > >I tested my system with memtest86 (for several hours) and it says > >everything is OK. > > We had similar problems once. It turned out to be a 'lucky' combination of good > mainboard and good memory that were slightly incompatible. > > memtest86 might not detect this, but make buildworld will. If you don't get the > errors at the same location every time, it might be the same issue. We found > out after contacting both the mainboard and the memory chip vendors. Same experience here, also on P4, with DDR400 memory. Asus mainboard, with memory from the Asus qualified memory list. Did not work worth sh*, at least not with memory at DDR400 speeds. Other memory fixed is perfectly. Go figure.. -- Wilko [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-RELEASE TODO
On Mon, Sep 29, 2003 at 02:05:16PM -0400, Daniel Eischen wrote: > On Mon, 29 Sep 2003, Robert Watson wrote: > > > |-+---+-+| > > | | | | Userland bits | > > | | | | implemented, | > > | KSE support for | In| Marcel | kernel bits not| > > | alpha | progress. | Moolenaar | implemented. | > > | | | | Required for | > > | | | | 5.2-RELEASE. | > > You should probably remove Marcel from this item. This task needs > another volunteer. Recently Marcel noted to me he was planning to engage on this one. I have offered him help for testing. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-RELEASE TODO
On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote: > On Mon, Sep 29, 2003 at 08:07:32PM +0200, Wilko Bulte wrote: > > > > > > You should probably remove Marcel from this item. This task needs > > > another volunteer. > > > > Recently Marcel noted to me he was planning to engage on this one. I have > > offered him help for testing. > > The deal is this (if you find your way between the parenthesis): > ... > At the DevSummit we failed to reach agreement that alpha should be > dropped to a tier 2 platform, but we did acknowledge that alpha needs > developers pronto. There it was also agreed that I would enter a > holding pattern (which roughly boils down to me circling between home, > work and Starbucks) until either someone fixes KSE or my weakness > shows and I do it anyway (the fact that I looked at it this weekend > means that I was pretty close to folding -- I made it to Starbucks > just in time). You get red hair from too much coffee anyway :-) :-) > I also mentioned recently (in the last couple of days) that we should > worry more about sparc64 than alpha. Simply because I think alpha is > on it's way down and should already be a tier 2 platform and sparc64 > is still on its way up ... sort of. In my book sparc64 is also with one foot in the grave. As is Sun itself. If we want to be future proof ia64 and amd64 are the only viable architectures. The rest are just interesting passtimes.. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM Gate.
On Tue, Oct 14, 2003 at 10:44:14PM +0200, Oldach, Helge wrote: > From: Richard Tobin [mailto:[EMAIL PROTECTED] > > > Ok, GEOM Gate is ready for testing. > > > For those who don't know what it is, they can read README: > > > > Aaargh! It's the return of nd(4) from SunOS. > > Excuse me? > > # uname -a > SunOS galaxy 4.1.4 18 sun4m Too new.. > # man nd > No manual entry for nd. > # -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM Gate.
On Wed, Oct 15, 2003 at 12:28:12AM -0700, Terry Lambert wrote: > Wilko Bulte wrote: > > On Tue, Oct 14, 2003 at 10:44:14PM +0200, Oldach, Helge wrote: > > > From: Richard Tobin [mailto:[EMAIL PROTECTED] > > > > > Ok, GEOM Gate is ready for testing. > > > > > For those who don't know what it is, they can read README: > > > > > > > > Aaargh! It's the return of nd(4) from SunOS. > > > > > > Excuse me? > > > > > > # uname -a > > > SunOS galaxy 4.1.4 18 sun4m > > > > Too new.. > > Yeah... Think Sun2 systems > > http://www.netbsd.org/Documentation/network/netboot/nd.html /me fondly remembers the hacked-up backplane in the Sun2/170 to allow it to use 7 1MB RAM cards.. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: hiding e-mail adresses needed badly
On Wed, Oct 15, 2003 at 03:29:21PM +0400, Andrey Chernov wrote: I fail to see why this is relevant to -current but OK.. I think that the opportunity to do this has long since passed. Just type your name in Google and see what happens.. Wilko > Due to increased activity of SPAM harvesters what are our plans to hide > our addresses from public WWW? I mean all browseable mailing lists, > FreeBSD site, CVS via WWW, PRs, ports and docs. > > As I think, simple form will be enough to stop > them. > > -- > Andrey Chernov | http://ache.pp.ru/ > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ---end of quoted text--- -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld fails on Alpha?
ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/fetch.c cc -O -pipe -mcpu=ev6 -mieee -I. -DINET6 -DWITH_SSL -Wsystem-headers -Werror -Wa ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/common.c /usr/src/lib/libfetch/common.c:58: error: `EAINONAME' undeclared here (not in a function) /usr/src/lib/libfetch/common.c:58: error: initializer element is not constant /usr/src/lib/libfetch/common.c:58: error: (near initialization for `_netdb_errli st[0].num') /usr/src/lib/libfetch/common.c:58: error: initializer element is not constant /usr/src/lib/libfetch/common.c:58: error: (near initialization for `_netdb_errli st[0]') /usr/src/lib/libfetch/common.c:60: error: initializer element is not constant /usr/src/lib/libfetch/common.c:60: error: (near initialization for `_netdb_errli st[1]') /usr/src/lib/libfetch/common.c:61: error: initializer element is not constant /usr/src/lib/libfetch/common.c:61: error: (near initialization for `_netdb_errli st[2]') /usr/src/lib/libfetch/common.c:62: error: initializer element is not constant /usr/src/lib/libfetch/common.c:62: error: (near initialization for `_netdb_errli st[3]') /usr/src/lib/libfetch/common.c:63: error: initializer element is not constant /usr/src/lib/libfetch/common.c:63: error: (near initialization for `_netdb_errli st[4]') *** Error code 1 Stop in /usr/src/lib/libfetch. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Seen before? Or just me? -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld fails on Alpha?
On Sat, Oct 25, 2003 at 06:06:24AM +0900, Hajimu UMEMOTO wrote: > Hi, > > >>>>> On Fri, 24 Oct 2003 23:03:31 +0200 > >>>>> Wilko Bulte <[EMAIL PROTECTED]> said: > > wkb> ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/common.c > wkb> /usr/src/lib/libfetch/common.c:58: error: `EAINONAME' undeclared here (not > > It was fixed already. Please re-cvsup. > Sorry for the mess. No problem, I'll re-cvsup -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Thu, Nov 06, 2003 at 09:52:27PM -0800, Matthew Dillon wrote: > :I just tried Jung-uk Kim's driver on -stable and sofar it works OK: > : > > ... and I just ported it to DragonFly and it works fine there too > with an ASUS K8V Motherboard. Kudos! Good to hear that ;) Jung-uk has provided me with some more patches to fix some issues with promiscuous mode. I have not had time to look at those yet. [EMAIL PROTECTED] committed some extra PCI-IDs to sk(4) yesterday, you might want to fold those into DragonFly as well. cheers, Wilko -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld failure on sparc64?
===> lib/libpam/modules/pam_radius cc -O -pipe -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_radius/pam_radius.c /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function `build_access_request': /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast increases required alignment of target type *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_radius. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 ? -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Alpha too.. (was: Re: buildworld failure on sparc64?
On Wed, Nov 12, 2003 at 11:37:18PM +0100, Wilko Bulte wrote: And on Alpha as well: ===> lib/libpam/modules/pam_radius^M cc -O -pipe -mcpu=ev6 -mieee -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/inc lude -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers -Werror -Wall -Wno-format -y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-st rings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_radius/pa m_radius.c^M /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function `build_access_request':^M /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast increases required alignment o f target type^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam/modules/pam_radius.^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam/modules.^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam.^M *** Error code 1^M > ===> lib/libpam/modules/pam_radius > cc -O -pipe > -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/include > -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers > -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow > -Wcast-align -Wno-uninitialized -c > /usr/src/lib/libpam/modules/pam_radius/pam_radius.c > /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function > `build_access_request': > /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast > increases required alignment of target type > *** Error code 1 > > Stop in /usr/src/lib/libpam/modules/pam_radius. > *** Error code 1 > > Stop in /usr/src/lib/libpam/modules. > *** Error code 1 > > > ? > > -- > | / o / /_ _ > |/|/ / / /( (_) Bulte [EMAIL PROTECTED] > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ---end of quoted text--- -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to disable devices in -current / 5.2-BETA?
On Tue, Dec 02, 2003 at 11:11:48AM -0700, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Scott Long <[EMAIL PROTECTED]> writes: > : However, having a general mechanism for disabling newbus devices would be > : really nice. > > Agreed. But today and 5.2 you lose. However, it isn't easy. What > does disabled mean? Don't attach? Don't even probe? If you don't You could disable the driver altogether. Assuming that is what is desired. -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: WORM & CAM CD
As Andreas Dobloug wrote ... > * Kenneth D. Merry > | > Has the worm driver been taken out of current? > | Yes. You have to use cdrecord now for SCSI CD burners. > > cdrecord lacks support for a whole lot of CD-burners... ? Having just a while ago downloaded the latest cdrecord source I'd say the list of supported hardware for cdrecord is a helluvalot longer than the worm stuff ever had. Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: show stopper for EGCS import
As David O'Brien wrote ... > > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from > > the EGCS source rather than our home-grown ones. > ..snip.. > > I've made the same fix to lib/csu as I did libgcc, but now am getting > > the same weird "install" problem Poul-Henning was getting. > > Well FMH! I found a typo I made in Makefile.inc1. However, there is > still a bootstrapping problem related to using the EGCS > crtbegin.o/crtend.o. So boys and girls, are are going to use the > "sjlj-exceptions" type exception machanism for a while. > > THE SWITCH HAS BEEN PULLED! FWIW, my Aspen Alpine AXP doing a buildworld on freshly (this afternoon) supped -current: . ===> etc/sendmail rm -f freebsd.cf (cd /usr/src/etc/sendmail && m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/ sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc ) > freebsd.cf chmod 444 freebsd.cf 16293.67 real 12302.28 user 3910.24 sys Buildworld seems to work fine on the alpha port. Congrats I'd say. Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Panic from today's current
As Luoqi Chen wrote ... > > The kernel-configfile and dmesg-output is available from: > > http://www.attic.ch/fuchur_kernel.html > > > > panic at: generic_bcopy+0x1arepe movsl (%esi), %es:(%edi) > > > > db> trace > > generic_bcopy(c02cc380,c7bb9b1f,0,a,0) at generic_bcopy+0x1a > > sccnputc(cff,1,c7bb9b80,c016c066) at sccnputc+0x180 > > cnputc(a,0,0,a,c7bb9bcc) at cnputc+0x3d > > putchar(a,c7bb9bf0) at putchar+0xa6 > > kvprintf(c028da63,c016bfc0,c7bb9bf0,a,c7bb9c04) at kvprintf+0x64 > > printf(c028da49,8000,c1159b00,a8,c7bc3e60) at printf+0x3d > > trap(10,10,a8,c1159b00,c7bb9ce8) at trap+0x462 > > calltrap() at calltrap+0x3c > > --- trap 0x13, eip = 0xc7bb9c68, ebp = 0xc7bb9ce8 --- > > Trap 19 (0x13) is NMI, this problem doesn't seem to be software related. NMI.. could be a RAM parity error or somebody/something fooling around with the IOCHKN line on the ISA bus. Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: NFS, blocks of NULLs in files
As Bob Bishop wrote ... > I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably > with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999) > running both on server and client (except that the client's kernel is 24hrs > older than that). > > It happens during a kernel build on the client, so both the sources and > objects are being accessed via NFS. During the 'generating linker set > emulation glue for ELF' phase, a lot of the .o's turn up with blocks of > NULLs. The rest of the world builds fine, but /usr/obj is local so there is > little or no NFS writing going on in that case. I have the impression I'm seeing similar things here. I have a 3.1 NFS server holding the -current sources. I build kernels over NFS using a -current testbox. Sometimes it builds kernels alright, sometimes you get kernels that panic with 100% repeatability. Just doing a config -r and a rebuild normally fixes this. The same thing happened when the NFS server was still at 2.2.8-stable Buildworlds with a local /usr/obj seem to work just fine. Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! )
As Warner Losh wrote ... > In message <199904181923.naa25...@mt.sri.com> Nate Williams writes: > : This is wonderful, but has this ever happened in our mailing lists? I > : guess I don't remember anyone *ever* ridiculing or harassing someone for > : not being fluent in the language. > > I have seen people ask others to explain again since they didn't > understand, but I cannot recall ever seeing anybody holding someone up > to ridicule publically. I have deep respect for several people that > have pushed through the language barrier. Maybe we should decide that this is a thing to keep in mind and let it rest for now? Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: newbus and modem(s)
As Rick Whitesel wrote ... > Hi: > Just wanted to say that I think the lack of a free-for-all CVS is > exactly what is required to consistently move FreeBSD forward. If someone Free-for-all as in 'everybody can do commits' ? This is a joke I hope. There already exists such a thing. It is called Linux (and even there the kernel is controlled). > feels they would like to take a different approach, then I say by all means > do so. If you can convince people to join your development effort then > great!, if not, then great!. > > Rick Whitesel > Scientist > NBase-Xyplex > rwhite...@nbase-xyplex.com Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
As Christopher T. Johnson wrote ... > Some extra information on tape problems: > > FreeBSD neunacht.netgsi.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Apr 22 > 16:50:33 EDT 1999 root@:/m/src/sys/compile/NEUNACHT i386 > > This is SMP machine with scsi only. > > The tape drive is an EXABYTE-8200. > > When doing tape IO that lasts for an extend period of time the tape drive > will show an amber light. This normally means SCSI activity. At that > point any reads or writes to the device happen at 1.4Mbytes/second when > the max I know that this drive will do is 0.24 Mbytes/second. The drive is speced for 270 kb/sec max IRRC. > We've replaced the tape drive. We've tested with different tapes. > > It LOOKS like the drive is detecting some sort of error and then going > into "toss data mode". This has cost me lots and lots of backups and > is very distressing. Exabyte is not particularly famous for stable firmware. I have a 8200 here and a 4.0-current testbox. No SMP though, a lowly P100 machine. I'll give it a try and report later today. > One interesting data point. When I issue an mt erase command it runs for > a fairly long time. It should runn for just over 2 hours. It gets about > 3/4s of the way and stops. Again with the orange light. The interesting > data point is that four tapes have all stopped at almost the same point. > (Visual inspection of amount of media left on the reels.) I can also try that, but it'll probably take until tomorrow. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
As Christopher T. Johnson wrote ... > REGARDLESS! > The drive is reporting an error condition and that error is NOT > getting back to user land. I've verified the problem with amdump Oh? Where/what is the error, does the console tell you? > amflush and dd. In ALL cases once the amber light goes on solid > systat -vmstat shows a solid 1.4MB/second data transfer into > never never land. That sounds like a bug. But it could be CAM not understanding that the 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte lockup.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
As Matthew Dillon wrote ... > The amber LED on exabytes typically means 'drive needs cleaning'. Exabyte > drives should be cleaned once or twice a week depending on how heavily > you use them. If an exabyte drive is not cleaned on a regular basis, the > transfer rate will drop steadily as the drive is forced to rewrite sectors > on the tape. Additionally, the larger gaps produced by the rewrites will > result in much less storage per tape. Very true. But a 8200 only has a green and an amber LED. Amber is SCSI activity on this model. > I dunno about the 8200. The mamoth exabytes can do 3 MBytes/sec. Any > exabyte drive should transfer up to its rating. If it transfers more > slowly, it is either damaged or in need of cleaning. The 8200 is Mark I and is dog slow compared to the later models. > When purchasing cleaning tapes, be sure to purchase the correct cleaning > tapes for the type of drive you have. Exabytes tend to be fairly > sensitive > and putting in the wrong sort of cleaning tape can damage the head. Yep, stay away from the Video8 cleaning cartridges. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
As Christopher T. Johnson wrote ... > > As Christopher T. Johnson wrote ... > > > > > REGARDLESS! > > > The drive is reporting an error condition and that error is NOT > > > getting back to user land. I've verified the problem with amdump > > > > Oh? Where/what is the error, does the console tell you? > > Sorry, no error reported, just the lights. Amber light, no green solid. > Either the kernel has the device "active" OR it is an error indicator. > Exabyte is known for doing that. In my experience it was always the drive, but YMMV. > > > amflush and dd. In ALL cases once the amber light goes on solid > > > systat -vmstat shows a solid 1.4MB/second data transfer into > > > never never land. > > > > That sounds like a bug. But it could be CAM not understanding that the > > 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte > > lockup.. > > Yep, been there done that. But these drives have been rock solid. It is > not the case of putting in a new, unknown drive and finding out that > it is a little strange. It is the case where I have a hardware configuration > that has been stable that suddenly isn't. CAM might trigger different code paths in the firmware. Or different timing. Or.. > The original change is the upgrade to 4.0-CURRENT. After that drive > "failed" I took our back up drive and put it into production and got exactly > the same failure mode. > > Here is the sequence that I just did: > Old working tape. > mt erase & > 1hr 30minutes or so later > Drive makes sounds of tape stopping. I also tried that in the meantime (it said *click* just a minute ago ;-) and I did not experience any problem with the erase operation. > Amber light comes on Nope, after the tape motion stops I have the green one on again. > mt erase reports done (no errors) > mt rewind > mt: /dev/nrsa0: Device busy p100#mt -f /dev/rst0 rewind p100# My P100 testbox uses a NCR810 to drive the 8200. Any chance you can try an 8200 with different f/w ? I'll also try a 'dump' again with more data, my previous test was 300Mb. Maybe that is not enough (I doubt it, but still..) Will post results when it's finished writing. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
As Bob Willcox wrote ... > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > Exabyte is not particularly famous for stable firmware. > > I have quite a number of 8200's here (though I don't really use them > much anymore since I now have a Mammoth) that I have installed new > firmware in. From an email discussion with an Exabyte tech support > person back in '93 (I believe it was), the latest level of firmware in Well, you sent it to me in March 1995 (just found the original email ;-) > shipping 8200's (this was right at their end-of-life) was: > > MX: 2680 > SV: C034 > > This is for generic models. OEM models may have different versions > due to customizations. And these are not recommended for general use. I have a second Exaybyte drive here, I could try to see what firmware that one has and if I can get it to fail. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
As Christopher T. Johnson wrote ... > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > > > Exabyte is not particularly famous for stable firmware. > > > > I have quite a number of 8200's here (though I don't really use them > > much anymore since I now have a Mammoth) that I have installed new > > firmware in. From an email discussion with an Exabyte tech support > > person back in '93 (I believe it was), the latest level of firmware in > > shipping 8200's (this was right at their end-of-life) was: > > > > MX: 2680 > > SV: C034 > > > Unfortunately I don't have a eprom burner :-( > ... > cam_debug: queuing for immediate ccb > > cam_debug: queuing for immediate ccb > > After which I have the same error again. > > After this world is installed, I'll test again, then build and test with > a UP kernel. > > Chris > > PS Thanks for all the help I've been getting from people willing to try > and replicate the problem. To get another datapoint I ran the 1.3Gb dump on another Exabyte drive. This one is a: sa0: Removable Sequential Access SCSI-CCS device No problems found. I'll do a resup and bring the testbox to the latest -current to see if that makes any difference. Will take time.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
As Bob Willcox wrote ... > On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: > > As Bob Willcox wrote ... > > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > > > shipping 8200's (this was right at their end-of-life) was: > > > > > > MX: 2680 > > > SV: C034 > > > > > > This is for generic models. OEM models may have different versions > > > due to customizations. > > > > And these are not recommended for general use. > > Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I That is what I've been told by an Exabyte engineer years back. I can only guess that some OEMs need adaptations to the firmware behaviour that are incompatible with what the rest of the world needs (or has standardised on, e.g. in the ANSI SCSI standard). Again, guessing. > have have precisely these firmware levels in them (2680 & C034). Also, Mine works OK with that f/w. Not that I use the 8200 often anymore, I like my DLT4000 much better than the 8200. ;-) Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Further on tape & CAM problems
[ should we keep this on -current ?? ] As Bob Willcox wrote ... > On Fri, Apr 30, 1999 at 12:36:25AM +0200, Wilko Bulte wrote: > > As Bob Willcox wrote ... > > > On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: > > > > As Bob Willcox wrote ... > > > > > On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: > > > Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I > > > > That is what I've been told by an Exabyte engineer years back. I can only > > guess that some OEMs need adaptations to the firmware behaviour that are > > incompatible with what the rest of the world needs (or has standardised > > on, e.g. in the ANSI SCSI standard). Again, guessing. > > Well, I can only speak for the IBM OEM'd drives that I have (as a > retired IBMer, I've been picking them up at their employee surplus > store here in Austin, TX). For these drives the generic firmware works > just fine. I can see why Exabyte wouldn't openly recommend the change > though. The hardware is probably the same, so an EPROM swap brings them to the generic model. > recall that we did have some customizations in the firmware for the > RS/6K AIX systems. In addition to changing the Inquiry command Vendor > ID data, I believe there were some functional changes (I don't recall > the details). I have always suspected that the functional changes are > likely what made the IBM OEM'd drives fail on FreeBSD! The upgraded > firmware IBM drives work on both (as "Other SCSI Tape Drive"). That is quite possible. And it matches the recommendation of the Exabyte engineer. > > Mine works OK with that f/w. Not that I use the 8200 often anymore, > > I like my DLT4000 much better than the 8200. ;-) > > I much prefer my Exabyte Mammouth drives as well :-) > > (But I do seem to get some fun out of playing with the 8200's I get for > $10 apiece from the surplus store :-) Absolutely right. And I got my DLT4000 for US$ 25 so you can guess where I got it from 8-) Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: kernel.old
As Chuck Robey wrote ... > I was thinking about Peter Wemm's recent change to the kernel Makefile, > making a way to install multiple kernels without fragging your last > known good kernel, and it got me to thinking, scragging kernel.old, now > that we have good kld's, isn't the only way to find yourself well and > truly screwed if your new kernel decides it's shy. Shy enough to hide on the swap device after a panic ;-) ? Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Doug Rabson wrote ... > On Sun, 9 May 1999, Khaled Daham wrote: > > > Hello folks > > > > I cvsupped,made world, built a kernel today and from now on the de > > interfaces only comes up in 100BaseTX, what causes it not to negotiate ? > > My Apr_29 kernel doesnt behave like this. > > > > The link lamp flickered like hell so it was quite a nice atmosphere for > > awhile , but i got tired of it :) > > > > /Khaled, Telia Network Services > > > > Mail: kha...@telia.net > > Cell: 070-6785492 > > Work: 08-4567281 > > > > :hacker: /n./ [originally, someone who makes furniture with an axe] > > Some tulip boards in alpha systems don't autonegociate properly so the SRM > has a way of forcing them to a particular mode. A change was made recently Recently... I think it's been there for a couple of years. > to respect the SRM setting instead of using autoneg. The variable is > typically called ewa0_mode. To find the right setting, type > > >>>set ewa0_mode > > from the SRM prompt and it will give you a list of settings. Choose one, > then type e.g.: > > >>>set ewa0_mode Twisted-Pair Keep in mind that older SRMs that understand the older Tulip 10/100Mbit chips (21140 IRRC) might not recognise the new ones (is that the 21143?) Bit me once.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: tosha after CAM changes
As Kenneth D. Merry wrote ... > Eric Hodel wrote... > > "Kenneth D. Merry" wrote: > > > So I'm a little confused here. Does camcontrol work? Try this: > > > > > > camcontrol devlist > > > > camcontrol: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for > > device > > > > > camcontrol tur -n da -u 0 -v > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > cam_lookup_pass: Inappropriate ioctl for device > > > > perhaps deleting and resupping is in order? > > It looks like you may not have the kernel side of the changes. When was > your kernel compiled? > > You may indeed want to cvsup again. I had the same phenomenon here. cvsup && buildworld && installworld && make clean tosha ; make tosha fixed it. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Doug Rabson wrote ... > On Sun, 9 May 1999, Wilko Bulte wrote: > > > As Doug Rabson wrote ... > > > On Sun, 9 May 1999, Khaled Daham wrote: > > > > > > > Hello folks > > > > > > > > I cvsupped,made world, built a kernel today and from now on the de > > > > > > Some tulip boards in alpha systems don't autonegociate properly so the SRM > > > has a way of forcing them to a particular mode. A change was made recently > > > > Recently... I think it's been there for a couple of years. > > Maybe you are remembering a NetBSD change? We just started doing the same > thing in FreeBSD recently. Oops I was confusing things with another email about the messages the driver spits out on dma not keeping up. > > > to respect the SRM setting instead of using autoneg. The variable is > > > typically called ewa0_mode. To find the right setting, type > > > > > > >>>set ewa0_mode > > > > > > from the SRM prompt and it will give you a list of settings. Choose one, > > > then type e.g.: > > > > > > >>>set ewa0_mode Twisted-Pair > > > > Keep in mind that older SRMs that understand the older Tulip 10/100Mbit > > chips (21140 IRRC) might not recognise the new ones (is that the 21143?) > > > > Bit me once.. > > Yeah. That must be why my 164lx won't netboot. Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit only) worked just dandy. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Doug Rabson wrote ... > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > only) worked just dandy. > > That reminds me. Does your Alpine still work after the new-bus stuff? I > wasn't sure I hadn't broken it when I changed the apecs driver. My Alpine is on a not so current -current, but it is rebuilding world now. Stay tuned, I can probably tell you more tomorrow. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Wilko Bulte wrote ... > As Doug Rabson wrote ... > > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > > only) worked just dandy. > > > > That reminds me. Does your Alpine still work after the new-bus stuff? I > > wasn't sure I hadn't broken it when I changed the apecs driver. > > My Alpine is on a not so current -current, but it is rebuilding world now. > Stay tuned, I can probably tell you more tomorrow. Bah.. Extracting pod2man (with variable substitutions) cd ext/B; miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B INST_ARCHLIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B ; make -B config PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl Writing Makefile for DynaLoader ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false false: not found *** Error code 1 This is -current as of last Sunday. I'll resup tonight to see if it got fixed in the meantime Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Sometimes again SCSI don't finish to boot
As Gianmarco Giovannelli wrote ... > > In 4.0-current sometimes the box will froze again after the : > "Waiting 3 seconds for SCSI devices to settle" > then nothing happens. > It was a thing happened also in early 1999, before the branch in > 4.0-current and 3.1 stable, if I remember well. > > Any others experience such behaviour ? > Here is again (part of) my infos: > > FreeBSD 4.0-CURRENT #0: Wed May 12 13:03:16 CEST 1999 > r...@gmarco.eclipse.org:/usr/src/sys/compile/GMARCO > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 400911064 Hz > CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x651 Stepping=1 > Features=0x183f9ff PAT,PSE36,MMX,FXSR> > real memory = 134217728 (131072K bytes) > avail memory = 127868928 (124872K bytes) > Preloaded elf kernel "kernel" at 0xc02ae000. > Pentium Pro MTRR support enabled, default memory type is uncacheable > Probing for PnP devices: > pcib0: on motherboard > pci0: on pcib0 > chip0: at device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vga-pci0: irq 11 at device 0.0 on pci1 > isab0: at device 4.0 on pci0 > chip1: at device 4.1 on pci0 > chip2: at device 4.3 on pci0 > ahc0: irq 14 at device 6.0 on pci0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > [...] > Waiting 3 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 3.300MB/s transfers > changing root device to da0s1a > da2 at ahc0 bus 0 target 2 lun 0 > da2: Removable Direct Access SCSI-2 device Have you tried this without the ZIP drive? I've heared from people they sometimes cause grief. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Nt source licenses...
As e...@habatech.no wrote ... > > On 12-May-99 Ustimenko Semen wrote: > > > > Are we going to get this license? I am interested in NTFS > > source code a lot... > > > > P.S. What's happening with MS? > > > They have got a virus. I think they're calling it Open Source... Na... it's called US Dept of Justice I guess ;-) > They're fighting really hard to get rid of it, but these things can happen > from time to time :) Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Mark Murray wrote ... > Wilko Bulte wrote: > > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl > > Writing Makefile for DynaLoader > > ==> Your Makefile has been rebuilt. <== > > ==> Please rerun the make command. <== > > false > > false: not found > > *** Error code 1 > > I periodically see this one reported, and It is always repaired > by the reporter making sure their tree is _really_ clean before > doing a make world. "Really clean" means "make cleandir" _twice_, > and complete removal of the contents of /usr/obj. _Then_ cvsup. > I prefer to usr CVS checkout, as it shows all the differences and > other turds in my source tree. Unfortunately: Extracting pod2man (with variable substitutions) cd ext/B; miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib Makefile.PL LINKTYPE=dynamic INSTALLDIRS=perl PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl LIBS="-lperl" INSTALLMAN3DIR=/usr/obj/usr/src/tmp/usr/share/perl/man3 INST_LIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B INST_ARCHLIB=/usr/obj/usr/src/gnu/usr.bin/perl/perl/build/B ; make -B config PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl Writing Makefile for DynaLoader ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false false: not found *** Error code 1 even after rm -rf /usr/obj | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Rodney W. Grimes wrote ...
> > Wilko Bulte wrote:
> > > PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
> > > Writing Makefile for DynaLoader
> > > ==> Your Makefile has been rebuilt. <==
> > > ==> Please rerun the make command. <==
> > > false
> > > false: not found
> > > *** Error code 1
> >
> > I periodically see this one reported, and It is always repaired
> > by the reporter making sure their tree is _really_ clean before
> > doing a make world. "Really clean" means "make cleandir" _twice_,
>
> This indicates to me, the original author of ``cleandir'', that
> something has broken the functionality that it had. This something
> is more than likely the removal of code similiar to:
>
> cd /usr/obj/{.CURDIR}; chflags -R noschg tmp; rm -rf *;
>
> before the equiv of:
> cd {.CURDIR}; ${make} clean
>
> > and complete removal of the contents of /usr/obj. _Then_ cvsup.
> > I prefer to usr CVS checkout, as it shows all the differences and
> > other turds in my source tree.
>
> If ``make cleandir'' is leaving some cruft in any form behind anyplace
> in the build tree things are broken.
Sounds very reasonable to me. Running the same command twice to get
things really clean sounds suspicious ;-)
In any case: I'm rebuilding now after a cvsup && chflags -R noschg
/usr/obj/* && rm -rf /usr/obj/*
We'll see what happens next.
| / o / / _ Arnhem, The Netherlands- Powered by FreeBSD -
|/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Doug Rabson wrote ... > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > only) worked just dandy. > > That reminds me. Does your Alpine still work after the new-bus stuff? I > wasn't sure I hadn't broken it when I changed the apecs driver. After a buildworld of yesterday's -current and a new kernel things work just fine. As an added bonus the serial console seems to work better. It used to be very slow, looks like that is gone. If you want more info you'll have to wait a bit, I'll be offline for a week. Wilko | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Doug Rabson wrote ... > On Sat, 15 May 1999, Wilko Bulte wrote: > > > As Doug Rabson wrote ... > > > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > > > only) worked just dandy. > > > > > > That reminds me. Does your Alpine still work after the new-bus stuff? I > > > wasn't sure I hadn't broken it when I changed the apecs driver. > > > > After a buildworld of yesterday's -current and a new kernel things > > work just fine. As an added bonus the serial console seems to work better. > > It used to be very slow, looks like that is gone. > > > > If you want more info you'll have to wait a bit, I'll be offline for > > a week. > > Thats good. The slow serial sounds like it used to be polling (i.e. sio > interrupts weren't getting through). I've been away to Oslo this week, but I plan to bang a bit more on the console to see if it keeps working ok. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Wilko Bulte wrote ... > As Doug Rabson wrote ... > > On Sat, 15 May 1999, Wilko Bulte wrote: > > > > > As Doug Rabson wrote ... > > > > On Mon, 10 May 1999, Wilko Bulte wrote: > > > After a buildworld of yesterday's -current and a new kernel things > > > work just fine. As an added bonus the serial console seems to work better. > > > It used to be very slow, looks like that is gone. > > > > > > If you want more info you'll have to wait a bit, I'll be offline for > > > a week. > > > > Thats good. The slow serial sounds like it used to be polling (i.e. sio > > interrupts weren't getting through). > > I've been away to Oslo this week, but I plan to bang a bit more on the > console to see if it keeps working ok. Banged on it and it works great now on the Alpine. Wilko | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
error message, what does this mean?
Hi My P100 testbox running a fairly recent current just said: May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, flags 0 May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, flags 0 May 27 23:39:23 p100 /kernel: vnode_pager_getpages: I/O read error May 27 23:39:23 p100 /kernel: vm_fault: pager read error, pid 252 (cp) May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 May 27 23:39:23 p100 /kernel: : 0xc36002c0: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) etc This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. Both disks are on seperate SCSI buses. Is this because the cp -R tries to copy /proc ?? | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: error message, what does this mean?
As Bruce Evans wrote ... > >May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages > >May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 > >May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, > >writecount 0, > > refcount 0, flags (VOBJBUF) > >May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180, > >flags 0 > >May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4, > >... > > >This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. > >Both disks are on seperate SCSI buses. Is this because the cp -R > >tries to copy /proc ?? > > Probably. Procfs has bugs that cause bad things to happen when some > files in it are copied. Hmm. Never seen it before. But doing a "cd / ; find . -fstype ufs -print | cpio -pudm /mnt" works like a charm without the vnode_pager messages. So looks like procfs alright. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: error message, what does this mean?
As Matthew Dillon wrote ... > :etc > : > :This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing. > :Both disks are on seperate SCSI buses. Is this because the cp -R > :tries to copy /proc ?? > : > :| / o / / _Arnhem, The Netherlands- Powered by FreeBSD - > :|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl > http://www.freebsd.org > > It seems to me that a cp command like is probably trying to > cp -R /mnt to /mnt ... /* will include /mnt, right? I'm not > sure what would be causing the errors, though, unless the cp > is recursing endlessly due to the cp of /mnt on top of /mnt > and running the filesystem out of space... In the end that happens, but not after a couple of seconds already. I'm quite sure it is the copying of /proc that triggers the messages. The VT_PROCFS like in May 28 10:04:15 p100 /kernel: tag VT_PROCFS, type 6, pid 193, mode 180, flags 0 also seems to indicate this. If I do: cd / ; find . -fstype ufs -print | cpio -pdum /mnt it works just fine without messages (of course until /mnt becomes full like you mention above). I've never seen this procfs behaviour before BTW. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: IRQ sharing with newbus
As Doug Rabson wrote ... > On Tue, 1 Jun 1999, Matthew N. Dodd wrote: > > > On Tue, 1 Jun 1999, Mark Newton wrote: > > > So, guys -- What is the officially blessed way of sharing IRQs under > > > newbus? > > > > If you find out, let me know since the EISA code suffers the same problem > > (though the drivers do a bit better job detecting the condition, and just > > fail to attach instead of panicing.) > > For EISA, it should be possible to add RF_SHAREABLE to the > bus_alloc_resource call (assuming that EISA interrupts are shareable like > pci interrupts). IRRC (it's been years) EISA cards can, but don't have to, support shared interrupts. I think the SCU/ECU can set this based on what the .CFG file of the card tells it the hardware can do. I once designed a EISA 2 channel SCSI adapter but that was > 9 years ago. Bitrot.. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Time drift.
On Wed, Mar 12, 2003 at 07:14:38AM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Andrew > P. Lentvorski, Jr." writes: > > >An $8.00 wristwatch has much better time accuracy that your multi-$100 PC. > > That's because the crystal in your wristwatch is cut specially so that it > has a flat temp-co at about 23-16 C, whereas the xtal in your computer > is has a gradient all the way from 0 to 70 C. And this is easily verifiable too: just leave your wristwatch in an unheated (cold) bedroom and watch the drift. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Don't upgrade your Alphas!
On Mon, Mar 17, 2003 at 02:12:31PM -0800, David Schultz wrote: > Thus spake Ruslan Ermilov <[EMAIL PROTECTED]>: > > Hold off upgrading your Alphas for a moment. > > Something broke libc recently that results in > > (at least) floating point exceptions from > > awk(1) (this is not related to today's awk > > upgrade). > > > > I've been able to reproduce this on beast.freebsd.org > > by building the fresh libc.a and linking awk with > > it, and running a test case. > > > > I haven't been able to reproduce this with 8th > > March libc, so the time window for the breakage > > is low. > > > > I suspect the recent gtdoa commit to libc; we > > will know that is less than an hour. > > Whups. You're probably using a locale in which the decimal point > is not a period. In that case, please use the patches I just > posted to the following thread, which I just CC'd you. Ruslan has been using my Alphas to test this and there is no locale set on those. > If it really is an Alpha issue and not a locale issue, awk is > probably dying on one of the scripts used by the kernel build. > If you could send me the command line that causes awk to die, > that would be helpful. I'm running a kernel build on beast > right now to see if I can reproduce a problem. I have a meeting > in a few minutes, but I'll be back in five hours or so to follow > up on this. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Clock running double time
On Tue, Mar 18, 2003 at 07:23:48PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Kevin Oberman" writes: > > >> kern.timecounter.hardware=TSC > > > >Can someone explain why TSC is preferred to i8254 (or why not)? > > Cheaper access & better resolution. Which brings me to the question if there is a comprehensive story on timekeeping in FreeBSD in the docs? Like the EuroBSDcon2002 one, but with answers to questions like the one above added. [I did not hunt in the doc tree for it btw] -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Removing Sendmail
On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: ... > [stepping back a bit ] > > I find an odd situation here whenever this topic comes up. One the > one hand, people are always wanting to split the entire base system > up into small packages for each little piece of the base. On the > other hand, one of FreeBSD's selling points in real-world environments > is that it doesn't have a bunch of little packages for the base system > like Linux distros. Do people really prefer something like having > rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, > etc.? One of the worst mis-features of Linux in my book. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing Sendmail
On Wed, Apr 02, 2003 at 11:28:53PM +0300, Dan Naumov wrote: > On Wed, 2 Apr 2003 21:56:40 +0200 > Wilko Bulte <[EMAIL PROTECTED]> wrote: > > > On Wed, Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: > > > > > > I find an odd situation here whenever this topic comes up. One the > > > one hand, people are always wanting to split the entire base system > > > up into small packages for each little piece of the base. On the > > > other hand, one of FreeBSD's selling points in real-world > > > environments is that it doesn't have a bunch of little packages for > > > the base system like Linux distros. Do people really prefer > > > something like having rpm's for /bin/ps to having one lump base dist > > > for all of /bin, /sbin, etc.? > > > > One of the worst mis-features of Linux in my book. > > I think being able to update just about ANYTHING, except the kernel > without the need for a reboot is one of the best features of Linux and > actual advantages it has over FreeBSD. Then go and run Linux. I like my FreeBSD bikeshed better ;) -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: policy on GPL'd drivers?
On Tue, May 27, 2003 at 10:23:04AM -0400, Alexander Kabaev wrote: > On Tue, 27 May 2003 07:20:17 -0700 > Steve Kargl <[EMAIL PROTECTED]> wrote: > > > On Tue, May 27, 2003 at 08:45:29AM -0400, Alexander Kabaev wrote: > > > On Tue, 27 May 2003 14:36:26 +0200 > > > > > > I and no doubt many others will insist on keeping GPLed drivers out > > > of the tree. I have no objections for this drivers to be confined in > > > ports though. > > > > kargl[205] ls /sys/gnu/dev/sound/pci > > csaimg.h* emu10k1-ac97.h emu10k1.h maestro3_dsp.h maestro3_reg.h > > > > The maestro3 driver is in the tree and is covered by the GPL > > for the same reasons that David will need to GPL the FreeBSD > > version of the nForce driver. > > > > -- > > Steve > This doesn't mean it is an open season for contaminating the tree with > GPL. Nobody said so. But this is a policy set by core.. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: src/share/man/man4 axe.4 mac_portacl.4 my.4rndtest.4 rue.4 sbsh.4 src/share/man/man4/man4.i386 pae.4 sbni.4vpd.4
On Fri, May 30, 2003 at 12:31:05AM +0300, Ruslan Ermilov wrote: > On Thu, May 29, 2003 at 02:28:36PM -0700, Ruslan Ermilov wrote: > > ru 2003/05/29 14:28:36 PDT > > > > FreeBSD src repository > > > > Modified files: > > share/man/man4 axe.4 mac_portacl.4 my.4 rndtest.4 rue.4 > > sbsh.4 > > share/man/man4/man4.i386 pae.4 sbni.4 vpd.4 > > Log: > > Assorted mdoc(7) fixes. > > > > Approved by:re (blanket) > > > Now this is real funny: the sbsh(4) manpage says the driver > first appeared in FreeBSD 4.9, but 5.1 will be released > before 4.9. Something wrong with our release model? ;) Virtualised time? -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Proof of concept patch for device rearrangement
On Thu, Jun 19, 2003 at 01:16:56AM +0200, Maxime Henrion wrote: > walt wrote: > > Poul-Henning Kamp wrote: > > > > >I have uploaded a proof of concept patch: > > > > > > http://phk.freebsd.dk/patch/fd_dev.patch > > > > > > >...And with this code enabled, it is possible to go from userland to > > >device driver without touching Giant underway. > > > > I'm sorry, I can't parse that last sentence. Could you explain in > > 25 words or less (or 3 lines of code) what it means? > > > > 'Giant' is the lock that Alan is trying to get rid of? > > Giant is the big lock that protects the whole kernel that everyone is > trying to get rid of :-). Get rid of the lock that is ;-) -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ReiserFS
On Sun, Jun 22, 2003 at 07:00:26PM +0200, Brad Knowles wrote: > At 9:50 AM -0700 2003/06/22, Lars Eggert wrote: > > > Make the ReiserFS box an NFS server and mount it on FreeBSD to copy the > > data over. > > What if it's the same machine? What if they have only the one > machine, so they can't even copy it over to another one, just to copy > it back? Borrow a tape unit, or a second disk, or a CDRW / DVDRW. Something along those lines, lacking Reiserfs in FreeBSD that leaves you little other option. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
