Re: ACPI??? was - Re: -current TCP performance hosed?
On Sun, Sep 16, 2001 at 12:37:53PM +0200, Oliver Fromme wrote: Have you verified that the duplex setting of your network interface is correct? It should be set to half-duplex if the machine is connected to a hub. Don't trust autoselect. Check the collision LEDs at the card (if present) and at the hub during data transfer. If everything looks OK, try putting a different card into that machine. My ethernet card is definitely running half duplex. Also, as I mentioned, as a client, the box behaves fine, but not as a server. Geoff. -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI??? was - Re: -current TCP performance hosed?
On Mon, Sep 17, 2001 at 11:55:48AM +0200, Oliver Fromme wrote: Well, duplex mismatch can result in asymmetric behaviour. It could be a problem with the transmit part of the driver. You didn't mention what kind of NIC and driver you use, IIRC. Maybe trying a different NIC could indicate whether this is a driver problem or something else. I intend to change my NIC. That will just take a little more time to arrange. Geoff. -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI??? was - Re: -current TCP performance hosed?
On Mon, Sep 17, 2001 at 02:55:16PM +0200, Geoff Rehmet wrote: On Mon, Sep 17, 2001 at 11:55:48AM +0200, Oliver Fromme wrote: Well, duplex mismatch can result in asymmetric behaviour. It could be a problem with the transmit part of the driver. You didn't mention what kind of NIC and driver you use, IIRC. Maybe trying a different NIC could indicate whether this is a driver problem or something else. I intend to change my NIC. That will just take a little more time to arrange. I've found the culprit - after moving my main network interface from ep0 to xl0, things suddenly work a lot better. Thus, it is probably either the card or the driver. (Admittedly, the card is quite ancient.) Geoff. -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI??? was - Re: -current TCP performance hosed?
On Sat, Sep 15, 2001 at 09:43:57AM -0400, Bosko Milekic wrote: On Sat, Sep 15, 2001 at 01:08:28AM +0200, Geoff Rehmet wrote: You said this happens with a few-day-old kernel. Is this an implication that it didn't happen before? Can you say, with a certain level of certainty exactly when this started happening, especially if it's something that only started to occur very recently, this may be a worthy piece of information. Thanks. No, I can't say for certain when this started. In fact, reverting to a kernel from June 27 still shows the same problem. However, I have done the following exercise, with three machines, two of which sit on our internal LAN together, on the same hub, with the third sitting on our public network (in our hosting room). Configs being: hangdog:- 5.0-CURRENT, 128M RAM, PII-266 (internal LAN) deadpoint: - 4.3-STABLE, 128M RAM, PI-166 (internal LAN) illuminati: - 4.2-RELEASE, 128M RAM, PII-333 (public network) hangdog and deadpoint sit on the same hub at my desk. There are 3 router hops from my hub to the hosting network - one of those hops being a firewall. All three machines are running IPFW. I did a test of downloading a 240M odd file from one machine to the other as a test. Everything looked fine, until I used hangdog (my -CURRENT box) as the server. I aborted that download, as it was too painfully slow. The transfer rates were as follows: ServerClient ---- illuminati - deadpoint (4.2 - 4.3)852kBps illuminati - hangdog (4.2 - 5.0)788kBps hangdog- deadpoint (5.0 - 4.3) 83kBps Thus, it appears that -CURRENT is still doing OK as a client, but is struggling badly as a server. At this point, this seems, from the empirical evidence, to have nothing to do with ACPI. Geoff. == deadpoint:/usr/tmp# fetch http://illuminati/~geoff/V379243.GHO Receiving V379243.GHO (255742011 bytes): 100% 255742011 bytes transferred in 292.8 seconds (852.90 kBps) deadpoint:/usr/tmp# rm V379243.GHO deadpoint:/usr/tmp# uname -a FreeBSD deadpoint.is.co.za 4.3-STABLE FreeBSD 4.3-STABLE #2: Thu Jul 19 14:15:37 SAST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/DEADPOINT i386 deadpoint:/usr/tmp# deadpoint:/usr/tmp# dmesg | more Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-STABLE #2: Thu Jul 19 14:15:37 SAST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/DEADPOINT Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 165790172 Hz CPU: Pentium/P55C (165.79-MHz 586-class CPU) === hangdog:~% fetch http://illuminati/~geoff/V379243.GHO Receiving V379243.GHO (255742011 bytes): 100% 255742011 bytes transferred in 316.8 seconds (788.40 kBps) hangdog:~% hangdog:~% dmesg | more Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Sep 11 14:15:17 SAST 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/HANGDOG Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 267274474 Hz CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) Origin = GenuineIntel Id = 0x634 Stepping = 4 === deadpoint:/usr/tmp# fetch http://hangdog/V379243.GHO Receiving V379243.GHO (255742011 bytes): 4%^C 10948608 bytes transferred in 128.6 seconds (83.11 kBps) fetch: transfer interrupted deadpoint:/usr/tmp# = illuminati:~% dmesg | more Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #2: Mon Feb 26 14:24:51 SAST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 332388500 Hz CPU: Pentium II/Pentium II Xeon/Celeron (332.39-MHz 686-class CPU) Origin = GenuineIntel Id = 0x650 Stepping = 0 -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-current TCP performance hosed?
I was just wondering if anyone has been experiencing problems with TCP performance on -current -- my box built on 11 Sept is dog slow - max 60kbps over 10baseT. I'm going to try and revert to an older kernel and see if there is a difference. Geoff. -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current TCP performance hosed?
On Fri, Sep 14, 2001 at 04:13:37PM -0400, Bosko Milekic wrote: On Fri, Sep 14, 2001 at 09:57:24PM +0200, Geoff Rehmet wrote: I was just wondering if anyone has been experiencing problems with TCP performance on -current -- my box built on 11 Sept is dog slow - max 60kbps over 10baseT. I'm going to try and revert to an older kernel and see if there is a difference. No. Not here. Make sure that all the debugging options are OFF in your kernel configuration file? Nope, no debug options, but I am getting loads of microuptime() went backwards (29804.3839847 - 29804.925730) microuptime() went backwards (29804.3839847 - 29804.926005) microuptime() went backwards (29804.3839847 - 29804.926316) microuptime() went backwards (29804.3839847 - 29804.926741) microuptime() went backwards (29804.3839847 - 29804.927119) microuptime() went backwards (29804.3839847 - 29804.928361) microuptime() went backwards (29804.3839847 - 29804.928867) microuptime() went backwards (29804.3839847 - 29804.932863) microuptime() went backwards (29804.3839847 - 29804.945770) microuptime() went backwards (29804.3839847 - 29804.946271) microuptime() went backwards (29804.3839847 - 29804.948524) microuptime() went backwards (29804.3839847 - 29804.949926) microuptime() went backwards (29804.3839847 - 29804.950331) microuptime() went backwards (29804.3839847 - 29804.952237) microuptime() went backwards (29804.3839847 - 29804.953419) microuptime() went backwards (29804.3839847 - 29804.955314) microuptime() went backwards (29804.3839847 - 29804.955781) -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI??? was - Re: -current TCP performance hosed?
It seems that, on Fri, Sep 14, 2001 at 03:18:47PM -0700, in message [EMAIL PROTECTED], Mike Smith wrote: Nope, no debug options, but I am getting loads of microuptime() went backwards (29804.3839847 - 29804.925730) ALi chipset? Try turning off the ACPI timer if you haven't already; set debug.acpi.disable=timer at the loader prompt. If this works, please let me know (with ACPI in the subject line so I don't miss it). Tried that, also tried set hint.acpi.0.disable=1 - neither had any effect. The kernel is not compiled with apm... Geoff. -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED], [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: src/sys/i386/isa/ipl.s rev 1.35 should fix boot lockups
Seems to be 100% now - I'm busy throwing a make -j 8 buildworld and a make -j 4 on the kernel, plus taring my source tree and browsing the web a little to see tha my console response is OK. ALL LOOKS COOL Thanks Matt! -Original Message- From: Matthew Dillon [mailto:[EMAIL PROTECTED]] Sent: 29 March 2000 11:15 To: [EMAIL PROTECTED] Cc: Geoff Rehmet; Bob Bishop; Alain Thivillon; Kenneth Wayne Culver Subject: src/sys/i386/isa/ipl.s rev 1.35 should fix boot lockups Rev 1.35 of src/sys/i386/isa/ipl.s, which I just committed, should fix the boot lockups. Many thanks for Alain Thivillon who was able to catch it in the act with DDB and narrow the problem down to doreti looping on astpending. To anyone I asked to try backing out the recent patch with an explicit revision checkout, please remember to blow away your src/sys/i386 subtree and check it out again so those files are not locked to a fixed revision. I am hoping that this will also fix Bob Bishop's reported boot lockup. The slow-response and jerky mouse problem should also be fixed. -Matt Matthew Dillon [EMAIL PROTECTED] Index: isa/ipl.s === RCS file: /home/ncvs/src/sys/i386/isa/ipl.s,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- isa/ipl.s 2000/03/29 06:15:43 1.34 +++ isa/ipl.s 2000/03/29 09:07:47 1.35 @@ -36,7 +36,7 @@ * * @(#)ipl.s * - * $FreeBSD: src/sys/i386/isa/ipl.s,v 1.34 2000/03/29 06:15:43 dillon Exp $ + * $FreeBSD: src/sys/i386/isa/ipl.s,v 1.35 2000/03/29 09:07:47 dillon Exp $ */ @@ -126,7 +126,7 @@ decb_intr_nesting_level /* Check for ASTs that can be handled now. */ - cmpl$0,_astpending + testl $AST_PENDING,_astpending je doreti_exit testb $SEL_RPL_MASK,TF_CS(%esp) jne doreti_ast To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UP kernel performance and Matt Dillon's patches
Matthew Dillon writes : :I'm running a UP machine with Matt's latest changes. I was just :compiling a new kernel and noticed the my PS/2 mouse under X was very :sluggish. I never noticed this sort of behavior before the changes, :even while doing ``make -j8 buildworld''. : :The compile was running on a UW SCSI disk on an Adaptec aic7880 Ultra :SCSI adapter on my motherboard, in case it matters. : :Looks like something has been verschlimmbessert (a wonderful German :word which means "made worse through improvement" :) : : :Gary Jennejohn / [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Ok, I'll take a look at it... the most likely cause is that I somehow broke need_resched. Not impossible, I'll check it out. I'm seeing the same symptoms while doing a make - my console performance is very jumpy and sluggish. Geoff. -- Geoff Rehmet, The Internet Solution [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] tel: +27-83-292-5800 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
Patrick Bihan-Faou writes : [Charset iso-8859-1 unsupported, filtering to ASCII...] Hi, If we are changing the meaning of "USA_RESIDENT", could we replace it by something else completely. I know that the USA are the center of the universe ;-), but... It seems to me that a things progress, the crypto regulation gets more complicated everyday. Why not have a "CRYPTO_COUNTRY" variable that could be set to "USA" "FRANCE" "CANADA" or "other" based where you live and weither special consideration must be taken relative to the crypto code ? Hmm, i would also look at something similar - rather generalise towards countries that are crypto-unfriendly (like the USA, France, etc.) g. -- Geoff Rehmet, The Internet Solution [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] tel: +27-83-292-5800 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Dropping connections without RST
Geoff Rehmet writes: : Not that easily.. how are you going to make ipfw dynamically know : which ports have listeners and which don't? By filtering all RST packets? My view was that this is much simpler than filtering packets - never generate the packet. My guess is that it creates lower overheads. In some instances, I don't want to look at every packet (which in effect happens with a packet filter). Plus, packets with RST in them are used for other purposes besides rejecting new incoming connections.. True, my implementation is specific that I only omit generating a RST when the icoming segment is a SYN. All other instances where you would generate a RST are left alone, and carry on behaving as before - otherwise you might break TCP behaviour. Geoff. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATA - Trouble mounting secondary master
Hmm, My root device still lands up on "wd0" - even though my fstab has the root filesystem on ad0s1a. I haven't looked at getting it to use the ad dev entries for the root file system. (I'm assuming that is still WIP.) Geoff. -Original Message- From: Soren Schmidt [mailto:[EMAIL PROTECTED]] Sent: 11 August 1999 08:53 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: ATA - Trouble mounting secondary master It seems Geoff Rehmet wrote: Brian McGroarty writes : In using the ATA driver, I'm unable to automatically mount a partition on a master drive on the secondary controller. fsck complains that device rwd2s1e isn't configured and exists. Immediately mounting by hand works perfectly. Compiling the kernel with wd instead of ata eliminates the problem. Hmm, I had exactly the same problem, although it manifested itself with a secondary master or slave. It went away a few weeks ago, and I was never able to make any sensible progress in tracking the problem down. Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATA - Trouble mounting secondary master
I just rebooted on an August 11 kernel. My system still is happy with the disks. Hmm. I can't remember exactly where my tracing went, before I left off before, but the message you are seeing comes from /sys/i386/isa/diskslice_machdep.c, line 200 (version 1.35). What you will probably find, is that if you put a line that goes: goto reread_mbr instead of "goto done", you will find that, on the second attempt, it reads the mbr successfully. The above is a severe kludge, and that is why I never committed any code to do anything of the sort. I think the error is actually somewhere in the ATA code (sorry Soren). I don't want to patch around a bug. Now somebody remarked that after the probe, a drive status light stayed on - maybe, the probe is not doing something properly for some drives, or there is somethign timing out. -Original Message- From: Kevin Street [mailto:[EMAIL PROTECTED]] Sent: 12 August 1999 03:10 To: Soren Schmidt Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: ATA - Trouble mounting secondary master Kevin Street [EMAIL PROTECTED] writes: Soren Schmidt [EMAIL PROTECTED] writes: Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... I tried with the ad dev entries for my problem as well with no improvement. I've also tried using: dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 as the first access to one of the failing drives (ad0). The first dd fails with device not configured, but any subsequent access works fine. It seems it's left in an odd state by the driver start up, but all it takes is a read to get it sorted out again. More on this. I just booted with -v and now when I do the first dd I see: ad0: invalid primary partition table: no magic and the same on ad2 when the swapon fails. So how do I get the magic back into my relationship with my drives? -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: best time for cvsup?
Dag-Erling Smorgrav writes : Nick Hibma [EMAIL PROTECTED] writes: Most active committers are in the States if you look at the frequency of commit messages. The European morning is the safest I guess. Not if I'm within reach of an Internet connection ;) Back in the days of version 1.1, the tree was often broken in the European / South African morning, which meant that a I was sometimes doing patches before a make world would work again. I think the maturity of the FreeBSD development process has changed somewhat since then. :-) Geoff. -- Geoff Rehmet, The Internet Solution [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] tel: +27-83-292-5800 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TCP SACK
I was wondering if anyone was busy looking at implementing TCP SACk (selective ack) on FreeBSD. Thanks, Geoff. -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: [EMAIL PROTECTED] URL: http://www.is.co.za To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X crashing under current
Kenneth Wayne Culver writes : I also am experiencing a kernel panic whenever I start X using today's kernel. Thanks After powering off and on again, I am now able to get a new kernel up, but now it boots happily, so I have no crash dumps, no traces, nothing to show for my story. I re-CVSuped this morning, and am now working again. (Trust me not to enable crash dumps when I installed my system - back in the old days, it was default) Anyhow, I'm now waiting to catch the bastard when it falls! Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Today's kernel crashes on starting X
I'm currently running into a problem, that when I start my system, it spontaneously reboots when starting X. Has anyone else run into this? -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geo...@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic ! panic ! panic !
Luoqi Chen writes : I'm trying to get a crash dump myself, but the kernel I have right now, is screwing up my keyboard, and I cannot even log in! I will try again. Geoff. After make world this morning I received this panic : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0155ca4 stack pointer = 0x10:0xc6864d64 frame pointer = 0x10:0xc6864d78 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty trap number = 12 panic: page fault I receive this panic with screen, but before I kept this box resetting itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the panic probably due to X loading. Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: panic ! panic ! panic !
Only one problem with that - screen and keyboard are not responding when it panics. I'm hoping that I will be able to get a dump which I can look at post mortem. I'm going to try again though. The kernel I have at the moment is totally messing up my keyboard, and I cannot even get a single user login! Geoff. -Original Message- From: Poul-Henning Kamp [mailto:p...@critter.freebsd.dk] Sent: 12 May 1999 05:56 To: Geoff Rehmet Cc: lu...@watermarkgroup.com; curr...@freebsd.org Subject: Re: panic ! panic ! panic ! At least put DDB in your kernel, type trace when it panics and tell us what it says. In message 19990512154854.78032.qm...@rucus.ru.ac.za, Geoff Rehmet writes: Luoqi Chen writes : I'm trying to get a crash dump myself, but the kernel I have right now, is screwing up my keyboard, and I cannot even log in! I will try again. Geoff. After make world this morning I received this panic : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0155ca4 stack pointer = 0x10:0xc6864d64 frame pointer = 0x10:0xc6864d78 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume , IOPL=0 current process = 374 (screen-3.7.6) interrupt mask = tty trap number = 12 panic: page fault I receive this panic with screen, but before I kept this box resetting itself trying to enter in X... and I was trying Xfree 3.3.3.1 (recompiled and reinstalled) SVGA, Metrolink and Xaccel 5.0 . But I could not seen the panic probably due to X loading. Could you show us the symbols around the faulting instruction at 0xc0155ca4? It would be even better if you have a crash dump and the gdb backtrace. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
newbus - kernel compile failure (old + new PCI drivers)
Since the newbus changes, I have had kernel compile failures, due to
the fact that I don't have any old style PCI drivers configured
on my system. By #ifdef'ing out the code that wraperises the
old driver code.
Diffs are as follows (this requires defining NOOLDPCIDRIVERS).
Obviously, this code should eventually all disappear, but is there
a more elegant way of doing things at the moment? Are these
changes worth committing?
*** pci.c.orig Mon Apr 19 08:21:08 1999
--- pci.c Wed Apr 21 23:41:33 1999
***
*** 846,851
--- 846,852
#include pci_if.h
+ #if !defined(NOOLDPCIDRIVERS)
/*
* A simple driver to wrap the old pci driver mechanism for back-compat.
*/
***
*** 921,928
--- 922,932
{ 0, 0 }
};
+ #endif
+
static devclass_t pci_devclass;
+ #if !defined(NOOLDPCIDRIVERS)
/*
* Create a new style driver around each old pci driver.
*/
***
*** 946,951
--- 950,956
devclass_add_driver(pci_devclass, driver);
}
}
+ #endif
/*
* New style pci driver. Parent device is either a pci-host-bridge or a
***
*** 1330,1336
--- 1335,1343
{
switch (what) {
case MOD_LOAD:
+ #if !defined(NOOLDPCIDRIVERS)
pci_wrap_old_drivers();
+ #endif
break;
case MOD_UNLOAD:
*** userconfig.c.orig Wed Apr 21 23:45:28 1999
--- userconfig.cWed Apr 21 23:41:22 1999
***
*** 570,575
--- 570,576
insdev(scratch,ap[i].id_enabled?active:inactive);
}
#if NPCI 0
+ #if !defined(NOOLDPCIDRIVERS)
for (i = 0; i pcidevice_set.ls_length; i++)
{
if (pcidevice_set.ls_items[i])
***
*** 595,600
--- 596,602
}
}
}
+ #endif
#endif/* NPCI 0 */
}
--
Geoff Rehmet, The Internet Solution - Infrastructure
tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800
email: geo...@is.co.za
URL: http://www.is.co.za
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Having trouble with the new ATAPI driver
William Liao writes : Hi, I did a CVSUP and make world at 4/15, then I decided to try the new ATAPI driver on my box. So I made some necessary changes to my kernel config and made a new kernel. But after boot, it always hangs on mounting disks. The message is: swapon: /dev/wd0s1b: Device not configured Then I tried to boot into single user mode and mount the slices manually. Unfortunately, same thing happened again when I tried to mount my /home, /var, etc. Mount replied: /dev/wd2s1e: Device not configured. Did I miss anything?... Thanks for your help. I've actually seen the same symptoms, with one of my swap partitions, but it is now also giving me this with one of my file systems, on fsck, at bootup. It drops me to single user (since fsck -p fails), I run fsck -p manually, it is happy, and I go multiuser. The same happened with the swap partition in question - a second swapon -a, and everything worked - that slice has however since become my /tmp, as I already had enough swap. I have only been getting device not configured errors on ad2 though. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
ATA driver
Hi There, I've just decided to keep my list of bonnie tests running. I haven't pulled the latest changes yet, as CVSUP is basically a day behind from cvsup.za.freebsd.org. Here is what I have so far: First committed version of ATA ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 ATA-noX64 3340 69.7 2984 11.9 1400 8.6 3135 62.4 3182 9.4 135.3 4.4 ATA-noX1 128 3221 68.5 2860 13.4 1169 7.6 2961 58.4 3038 12.2 54.2 2.3 ATA-noX1 128 3169 68.2 2933 12.8 1222 7.8 2944 58.1 3081 12.1 57.8 2.4 ATA-noX1 128 3175 66.9 3017 14.3 1166 7.6 3105 61.2 3142 12.4 56.3 2.4 After CVSUPing changes from 4/3/99 (before UPDATE-2 heads up message) All tests : freshly booted, no X ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA2 128 3140 67.6 3023 12.0 1175 7.5 3057 58.8 3068 8.6 56.3 2.0 ATA2 128 3122 67.4 3008 11.9 1161 7.2 3121 62.6 3189 9.1 57.5 2.1 ATA2 128 3125 65.9 2981 11.8 1177 7.1 3064 60.2 3189 9.6 56.5 2.1 The only significant diference is on Sequential block inputs and random seeks where, notably the CU times have gone down. (I have taken no account of other changes in the kernel.) Geoff. -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geo...@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Printing is vvveeerrryyy slow
Alfred Perlstein writes : Printing is very slow. I have a HP LaserJet III attached to lpt0. Printing in the pcl, text, mode is slower than I expect. Printing in the postscipt mode is extremely slow. A 30K postscript file has been OVER 5 minutes and is not finished! have you tried: lptcontrol -p I remeber the friendlies on #freebsd suggesting this to me when i had similar symptoms last year. It's a long long time since I was working on the lpt driver. This kind of symptom was a common problem during its development. I haveen't been able to really appreciate the code for the nltp driver, so I also can't really see if there is a problem. Biggest problem when I was hacking on the lpt driver was that interrupts tended to get lost sometimes. I seem to recall, that there were some problems with slow printing that just could not be fixed. Going into polled mode (lptcotnrol -p) is probably your best bet at the moment. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Printing is vvveeerrryyy slow
Re: CALL FOR TESTERS of new ATA/ATAPI driver..
Søren Schmidt writes : Good work, no more stinky delay :-) Thanks!, and I hate delays too :) It works beautifully for me. I can imagine that the people with UDMA drives can't wait for DMA support in it. :-) I've run some tests with Bonnie. Need to still reboot with my old kernel, and run the same test to see what it did. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
ATA driver
Just some results of testing the comparison of wd and ata: Both bonnie tests were run on a freshly booted machine, P133, 64M RAM, running X and netscape, but only Bonnie active: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 It may be worth testing with a larger file, freshly booted, with no X running. For reference, here is output of dmesg from my system: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Mar 2 08:26:46 SAST 1999 ge...@hangdog.is.co.za:/usr/src/sys/compile/HANGDOG.ata Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 133269971 Hz CPU: Pentium/P54C (133.27-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping=12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 67108864 (65536K bytes) avail memory = 63021056 (61544K bytes) Preloaded elf kernel kernel at 0xf023d000. Probing for devices on PCI bus 0: chip0: Intel 82437VX PCI cache memory controller rev 0x02 on pci0.0.0 chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 ata-pci0: Intel PIIX3 IDE controller rev 0x00 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 vga0: S3 Trio graphics accelerator rev 0x00 int a irq 11 on pci0.11.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ata-isa1: already registered as ata0 ata1 not found at 0x1f0 ata-isa2: already registered as ata1 ata2 not found at 0x170 ppc0 at 0x378 irq 7 on isa ppc0: W83877F chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*UTP*] address 00:60:97:3d:ff:fc vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ata1: unwanted interrupt ata1: unwanted interrupt Intel Pentium detected, installing workaround for F00F bug ep0 XXX: driver didn't set ifq_maxlen ad0: Maxtor 71084 A/QA3S1D20 ATA-? disk at ata0 as master ad0: 1036MB (2122780 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad1: Conner Peripherals 850MB - CFS850A/8.32 ATA-? disk at ata0 as slave ad1: 812MB (1664583 sectors), 1651 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue acd0: ATAPI CDROM/V1.50 CDROM drive at ata1 as master acd0: drive speed 687 - 5500KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to ad0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Geoff. -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geo...@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: CALL FOR TESTERS of new ATA/ATAPI driver..
On 02-Mar-99 SXren Schmidt wrote: Its in the works, together with the tagged queuing some of the newer drives supports. Wow! :) Is there any chance od adding the ability to 'wire' devices a la SCSI? :) I'll think about it, but lots of things has higher priority... -Søren I just repeated the Bonnie tests without X running, on a freshly booted machine. (WD is still with X and netscape.) As I said, I am not running any flags on WD, but asl Luigi pointed out, I could probably do with some newer hard drives! Geoff. ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA+X+Nets 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD+X+Netsc 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 ATA-noX64 3340 69.7 2984 11.9 1400 8.6 3135 62.4 3182 9.4 135.3 4.4 ATA-noX1 128 3221 68.5 2860 13.4 1169 7.6 2961 58.4 3038 12.2 54.2 2.3 Geoff. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: adding DHCP client to src/contrib/
-Original Message- From: David O'Brien [mailto:obr...@nuxi.com] Sent: 09 February 1999 10:54 To: Geoff Rehmet Cc: curr...@freebsd.org Subject: Re: adding DHCP client to src/contrib/ It may even be necessary to use bpf initially, but there must be a more elegant way - having a quick look around - it would be a good idea to look at the code which already exists in libstand (/usr/src/lib/libstand/bootp.c). There is. Date: Wed, 16 Sep 1998 15:20:45 -0400 (EDT) From: Garrett Wollman woll...@khavrinen.lcs.mit.edu Message-Id: 199809161920.paa07...@khavrinen.lcs.mit.edu ..snip.. The problem is that the network code assumes, at a very deep level, that you can't have any IP traffic until you have an address configured (and this is wrong, but requires work to fix). -GAWollman Unfortunately, I don't have the knowledge of the part of the kernel that needs changing. Hopefully, it will be possible to find the person who will be able to do that work - I also do not have the knowledge to do this. It is probably worth fixing, to get a more elegant way for DHCP to work, and I believe that DHCP should be committed with a view to changing the use of bpf. I realise this is not an easy proposition. Geoff. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: adding DHCP client to src/contrib/
Steve Kargl writes : Content-Type: text/BLOAT These should be left has ports. I can understand the people who need DHCP to get their systems up. OTOH, where does one draw the line. Is DHCP core functionality? Another issue to be taken into account: there is already a bootp daemon in the tree. Anyone putting any DHCP functionality in should look very seriously at any possibilities of combining the functionality, rather than creating what amounts to a degree of redundancy. (I haven't looked at DHCP-WIDE, and consequently, I don't know if it also supports bootp functionality.) I personally would prefer to see DHCP left a port. But, OTOH, more and more people are using dynamic IP address assignment on their networks. (Not an easy one.) Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: adding DHCP client to src/contrib/
Sean Eric Fagan writes : In article 19990209074440.15845.qmail.kithrup.freebsd.curr...@rucus.ru.ac.za you write: Is DHCP core functionality? As much as an editor and PPP are, yes -- without it, some people simply *cannot* get on the net. Your point is valid. Before it goes in, there are some points to look at though: - Integration with bootp functionality (if possible) - DHCP-WIDE requires you to have bpf configured into your kernel for a GENERIC kernel, this is VERY BAD - is there a more elegant way to handle this? I certainly would not like to see the generic kernel in the distribution going out into the world with bpf enabled. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: adding DHCP client to src/contrib/
Sean Eric Fagan writes : There's really no other way to do it: you need the ability to grab packets that come from an unidentified machine, which doesn't have an IP address. You could write some other method of doing this -- and then put it into every single ethernet (et al) device driver -- or you could just use BPF, which really isn't all that large. Bootpd doesn't require bpf in order to work. Incoming requests all have the IP number 0.0.0.0. The issue, as I understand it, is to get a reply from an unknown server (who has an IP address), while you have no IP address. I would still be very reticent to see BPF in a generic kernel because of the security implications. Remember that the DHCP client is listening for a datagram which has its own layer 2 address as the destination address. - No need for promiscuous mode. The only problem is that the client doesn't know its own IP number. I would really not like DHCP to require FreeBSD being shipped with bpf enabled. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: adding DHCP client to src/contrib/
Sean Eric Fagan writes : 1. /dev/bpf0 is mode 400, root.wheel -- to read it, you need to break root. 2. If you can break root, you can rebuild a kernel with BPF *anyway*. Not quite - bpf is potentially dangerous where a sysadmin is inexperienced. On a system with a generic kernel and no source on it, it may be fairly difficult to get a kernel with bpf onto the system. Where there is an experienced admin, this becomes less of an issue. I am not trying to stop DHCP being added to the tree. It may even be necessary to use bpf initially, but there must be a more elegant way - having a quick look around - it would be a good idea to look at the code which already exists in libstand (/usr/src/lib/libstand/bootp.c). I haven't had an exhaustive look through the code, but this should give the necessary material to work out another way of doing things. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Building a new system to current
Hi, I'm in the process of setting up a new FreeBSD-current box, starting with 3.0 Release, and moving to current. One question I have, is whether to go to the ELF kernel before I recompile the world with current source. My plan is as follows: - Load 3.0-RELEASE (done) - archive and delete all a.out tools (done) - update to the new bootblocks (done) - move to ELF kernel - CVSup to current - rebuild the world - come up on current I have tarred up all the a.out libraries and tools, to try and make sure that I don't install anything that depends on a.out. Hopefully, I will not have to go back on that! Apart from the comments in src/UPDATING, Peter Wemm's ELF day web page, and Robert Nordiers page on the new bootblocks, can anyone think of anything I should take into account? regards, Geoff (hoping to be hacking again soon!) -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geo...@is.co.za URL: http://www.is.co.za http://www.is.co.za/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
