From owner-freebsd-current Sun Feb 4 0:35:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 9BCFC37B4EC; Sun, 4 Feb 2001 00:35:40 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f148ZTt19389; Sun, 4 Feb 2001 00:35:34 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102040835.f148ZTt19389@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Greg Lehey Cc: Robert Watson , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Watch your devfs permissions in driver make_dev calls In-Reply-To: <20010204115741.G27504@sydney.worldwide.lemis.com> Date: Sun, 04 Feb 2001 00:35:29 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Friday, 2 February 2001 at 20:10:10 -0800, Peter Wemm wrote: > > Robert Watson wrote: > > > >> crw-r--r-- 1 root wheel 78, 0 Dec 31 1969 pci > > > > This one may appear harmless, but it is not. It is trivially easy to creat e > > an alignment fault (fatal on an alpha) with the userland pciconf tool. > > We must not allow this to be used by users until the kernel part is fixed. > > > > Eg: try this on an alpha: pciconf -r -l pci0:x:x 0x3 - ie: read a longword > > at byte offset 3 in configuration space.. kaboom! > > This looks like a separate issue. Presumably you can do this as root > as well. pciconf should check the parameters. The kernel should check the parameters passed in from the userland, at least, it should not die like this. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 0:45:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 84BED37B401 for ; Sun, 4 Feb 2001 00:45:07 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f148j4B17571; Sun, 4 Feb 2001 09:45:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Makoto MATSUSHITA Cc: current@freebsd.org Subject: Re: doFS.sh should obey MDDEVICE if available In-Reply-To: Your message of "Sun, 04 Feb 2001 08:24:09 +0900." <20010204082409C.matusita@jp.FreeBSD.org> Date: Sun, 04 Feb 2001 09:45:04 +0100 Message-ID: <17569.981276304@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since mdconfig can autoallocate the device, why is this needed ? In message <20010204082409C.matusita@jp.FreeBSD.org>, Makoto MATSUSHITA writes: > >src/release/scripts/doFS.sh rev. 1.6 doesn't consider MDDEVICE variable >(formaly, VNDEVICE). Here is a sample fix to use MDDEVICE variable to >configure md -- trivial, add '-u' option if MDDEVICE is already defined. > >-- - >Makoto `MAR' MATSUSHITA > >Index: doFS.sh >=================================================================== >RCS file: /pub/cvsup/FreeBSD.cvs/src/release/scripts/doFS.sh,v >retrieving revision 1.29 >diff -c -r1.29 doFS.sh >*** doFS.sh 2001/01/31 22:58:39 1.29 >--- doFS.sh 2001/02/03 23:16:51 >*************** >*** 37,43 **** > awk 'BEGIN {printf "%c%c", 85, 170}' |\ > dd of=${FSIMG} obs=1 seek=510 conv=notrunc 2>/dev/null > >! MDDEVICE=`mdconfig -a -t vnode -f ${FSIMG}` > if [ ! -c /dev/${MDDEVICE} ] ; then > if [ -f /dev/MAKEDEV ] ; then > ( cd /dev && sh MAKEDEV ${MDDEVICE} ) >--- 37,47 ---- > awk 'BEGIN {printf "%c%c", 85, 170}' |\ > dd of=${FSIMG} obs=1 seek=510 conv=notrunc 2>/dev/null > >! if [ "x${MDDEVICE}" != "x" ] ; then >! mdconfig -a -t vnode -f ${FSIMG} -u ${MDDEVICE} >! else >! MDDEVICE=`mdconfig -a -t vnode -f ${FSIMG}` >! fi > if [ ! -c /dev/${MDDEVICE} ] ; then > if [ -f /dev/MAKEDEV ] ; then > ( cd /dev && sh MAKEDEV ${MDDEVICE} ) > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 2: 3:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id BE40D37B401 for ; Sun, 4 Feb 2001 02:03:23 -0800 (PST) Received: from gorean.org (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id CAA75569 for ; Sun, 4 Feb 2001 02:03:22 -0800 (PST) (envelope-from DougB@gorean.org) Message-ID: <3A7D28EA.9EF46BAE@gorean.org> Date: Sun, 04 Feb 2001 02:03:22 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Dangling symlink in /usr/compat/linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, /usr/compat/linux/usr/lib/X11 points to ../X11R6/lib/X11, but there is no X11 in /usr/compat/linux/usr/X11R6/lib. There are linux X libraries in the directory, although I'm not sure what the right change would be. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 2:24: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 90EEE37B401 for ; Sun, 4 Feb 2001 02:23:47 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id LAA29898; Sun, 4 Feb 2001 11:23:43 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14PMKc-000456-00 for ; Sun, 04 Feb 2001 11:23:42 +0100 Date: Sun, 4 Feb 2001 11:23:42 +0100 From: Szilveszter Adam To: freebsd-current@freebsd.org Subject: Re: Dangling symlink in /usr/compat/linux Message-ID: <20010204112342.A15191@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , freebsd-current@freebsd.org References: <3A7D28EA.9EF46BAE@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A7D28EA.9EF46BAE@gorean.org>; from DougB@gorean.org on Sun, Feb 04, 2001 at 02:03:22AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 04, 2001 at 02:03:22AM -0800, Doug Barton wrote: > FYI, /usr/compat/linux/usr/lib/X11 points to ../X11R6/lib/X11, but > there is no X11 in /usr/compat/linux/usr/X11R6/lib. There are linux X > libraries in the directory, although I'm not sure what the right change > would be. Are you sure? This what I get: [11:19, Feb 04., Sun] cc@fonix:/home/cc ttyv4 % ls -l /usr/compat/linux/usr/lib/X11/ total 2 drwxr-xr-x 2 root wheel 2048 Nov 17 14:03 config [11:19, Feb 04., Sun] cc@fonix:/home/cc ttyv4 % ls -l /usr/compat/linux/usr/X11R6/lib/X11/ total 2 drwxr-xr-x 2 root wheel 2048 Nov 17 14:03 config Seems to be in order to me... at least, the symlink definitely points to somewhere that exists. (I installed linux-base quite some time ago but I know it works because I use RealPlayer every day:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 6:33:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from caligula.anu.edu.au (caligula.anu.edu.au [150.203.224.42]) by hub.freebsd.org (Postfix) with ESMTP id 1134037B491 for ; Sun, 4 Feb 2001 06:33:15 -0800 (PST) Received: (from avalon@localhost) by caligula.anu.edu.au (8.9.3/8.9.3) id BAA05436 for current@freebsd.org; Mon, 5 Feb 2001 01:33:13 +1100 (EST) From: Darren Reed Message-Id: <200102041433.BAA05436@caligula.anu.edu.au> Subject: update of ipfilter To: current@freebsd.org Date: Mon, 5 Feb 2001 01:33:13 +1100 (Australia/ACT) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well, I got as far as importing ipfilter 3.4.16 into -current before I realised that ref5 is not working properly (again) or for some reason it just doesn't know about the ssh files that freefall does so if I just broke -current, I'm sorry but if I could have done a test compile on a 5.x box I would have... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 6:46:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id 09CFF37B491 for ; Sun, 4 Feb 2001 06:45:55 -0800 (PST) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id 50F1714C5D; Sun, 4 Feb 2001 08:45:54 -0600 (CST) To: FreeBSD Current Subject: Re: kernel trap 26 panic References: From: Michael Harnois Date: 04 Feb 2001 08:45:53 -0600 In-Reply-To: (John Baldwin's message of "Sat, 03 Feb 2001 22:54:33 -0800 (PST)") Message-ID: <867l36ld5q.fsf@mharnois.workgroup.net> Lines: 13 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.2 (Terspichore) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 03 Feb 2001 22:54:33 -0800 (PST), John Baldwin said: > The ppbus does painful things with its interrupt handlers. This > is a known problem and on the todo list, just not fixed yet. This problem (with lpr) is new in the past couple of days, at least here ... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org There are things that are so serious that you can only joke about them. -- Werner Heisenberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 6:46:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 61BB037B4EC for ; Sun, 4 Feb 2001 06:45:55 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id BAA12281; Mon, 5 Feb 2001 01:45:27 +1100 Date: Mon, 5 Feb 2001 01:45:08 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Cejka Rudolf Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG Subject: Re: Does task scheduler work correctly? (... nice bug fix) In-Reply-To: <20010201201413.A55503@dcse.fee.vutbr.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Feb 2001, Cejka Rudolf wrote: > Sheldon Hearn wrote (2001/02/01): > > What I remember of the discussions that surrounded this one, your > > summary is correct. The only thing is that nice isn't so much _broken_ > > as it just isn't doing what you'd expect it to. :-) > > Ok, scheduler in -current is not broken. But I'm afraid that in -stable Nah, it is broken. > it is - can (niced) process cause a lock of machine?. Currently, we > have dual processor box with 4.2-STABLE and it silently locks too often. > With current scheduler in mind, it is hard to say if I should search in > HW or SW for a potential fix... I think only processes with niceness less than -5 can cause lockups. This is because they get assigned priorities below some kernel priorities, so priority inversion is possible. I think priority inversions between processes running in user mode are impossible (because low-priority (higher priority numbered) processes can't block in user mode). > > I don't think any of the FreeBSD manual pages suggest that nice 20 > > processes aren't supposed to get _any_ CPU time. > > Maybe. But there are some conventions and two-process sensitivity > 2.5:1 is not very big (is low). Solaris and Linux have much bigger > ratio (sufficient). So why FreeBSD has to be so much different? Just a bug. The relative weights of the priorities are mostly determined accidentally by the following formula in resetpriority(): newpriority = PUSER + p->p_estcpu / INVERSE_ESTCPU_WEIGHT + NICE_WEIGHT * (p->p_nice - PRIO_MIN); For process mixes consisting of only long-running cpu hog processes, the priorities tend to a common limit (this is fairly obvious -- lower priority processes get run more; this increases their priority until it is not lower, so the priority of all the processes is similar; also, correct design of the algorithm that decays p_estcpu should ensure that the common priority doesn't hunt). For the simple case of 2 long-running cpu hog processes with nicenesses n1 and n2, the priority for both tends towards a limit of approximately 104 (see ps output). This corresponds to the (p_estcpu / weight) term for the process with the lowest nice value tending towards its maximum value of (PRIO_MAX - PRIO_MIN - PPQ == 36); the maximum is nearly reached because of correct design of of the decay algorithm, and actually reached because of bugs). The p_estcpu's for the two processes can be calculated from this: 104 = 48 + p->p_estcpu / 8 + 1 * (p->p_nice + 20) p->p_estcpu = (36 - p->p_nice) * 8 In the limit, the runtimes are to a first approximation proportional to p_estcpu (higher terms depend on the decay algorithm), so for processes with niceness n0 and n1, the relative runtimes are approximately: (36 - n0) : (36 - n1) This formula is neither simple nor good. For n0 = 0 and n1 = 20, it gives the ratio of 36:16, which is close to the 2.5:1 ratio observed by Cejka. I observe a ratio closer to 3:1 for the runtimes, and the formula gives almost the exact ratio for the p_estcpu's. The formula breaks down near (n0 = -16, n1 = 20), since the p_estcpu term can never raise the priority by more than 36, so the ratio is 1:0 for n0 < - 16 and n1 = 20. This is a bug. > Insensitivity of nice were problem in the past and it is going back. For RELENG_4 before I imported the fixes from NetBSD, the corresponding calculations are: 127 = 50 + p->p_estcpu / 4 + 2 * p->p_nice p->p_estcpu = (38.5 - p->p_nice) * 8 ratio = (38.5 - n0) : (38.5 - n1) ratio for nicenesses (0, 20) = 38.5:18.5 so -current is almost perfectly bug for bug compatible in this area with RELENG_4! :-( In RELENG_4, the corresponding calculations are: 86 = 50 + p->p_estcpu / 8 + 2 * p->p_nice p->p_estcpu = (18 - p->p_nice) * 16 ratio = (18 - n0) : (18 - n1) ratio for nicenesses (0, 20) = 18:-2 (formula invalid, actually 1:0) ratio for nicenesses (0, 17) = 18:1 Quick fix: --- Index: kern/kern_synch.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v retrieving revision 1.124 diff -c -2 -r1.124 kern_synch.c *** kern/kern_synch.c 2001/01/31 04:29:51 1.124 --- kern/kern_synch.c 2001/02/03 15:16:44 *************** *** 1039,1044 **** mtx_enter(&sched_lock, MTX_SPIN); if (p->p_rtprio.type == RTP_PRIO_NORMAL) { ! newpriority = PUSER + p->p_estcpu / INVERSE_ESTCPU_WEIGHT + ! NICE_WEIGHT * (p->p_nice - PRIO_MIN); newpriority = min(newpriority, MAXPRI); p->p_usrpri = newpriority; --- 1039,1046 ---- mtx_enter(&sched_lock, MTX_SPIN); if (p->p_rtprio.type == RTP_PRIO_NORMAL) { ! newpriority = PUSER + ! (PRIO_MAX - PRIO_MIN + 1) * ! (p->p_estcpu / INVERSE_ESTCPU_WEIGHT) / ! (PRIO_MAX - p->p_nice + 1); newpriority = min(newpriority, MAXPRI); p->p_usrpri = newpriority; Index: sys/proc.h =================================================================== RCS file: /home/ncvs/src/sys/sys/proc.h,v retrieving revision 1.145 diff -c -2 -r1.145 proc.h *** sys/proc.h 2001/01/31 04:29:52 1.145 --- sys/proc.h 2001/02/03 15:56:49 *************** *** 493,505 **** * XXX macros for scheduler. Shouldn't be here, but currently needed for * bounding the dubious p_estcpu inheritance in wait1(). * INVERSE_ESTCPU_WEIGHT is only suitable for statclock() frequencies in * the range 100-256 Hz (approximately). */ #define ESTCPULIM(e) \ ! min((e), INVERSE_ESTCPU_WEIGHT * (NICE_WEIGHT * (PRIO_MAX - PRIO_MIN) - \ ! PPQ) + INVERSE_ESTCPU_WEIGHT - 1) ! #define INVERSE_ESTCPU_WEIGHT 8 /* 1 / (priorities per estcpu level). */ ! #define NICE_WEIGHT 1 /* Priorities per nice level. */ ! #define PPQ (128 / NQS) /* Priorities per queue. */ struct mtx; --- 493,505 ---- * XXX macros for scheduler. Shouldn't be here, but currently needed for * bounding the dubious p_estcpu inheritance in wait1(). + * XXX PPQ no longer needed for that. * INVERSE_ESTCPU_WEIGHT is only suitable for statclock() frequencies in * the range 100-256 Hz (approximately). */ #define ESTCPULIM(e) \ ! min((e), (INVERSE_ESTCPU_WEIGHT * (MAXPRI + 1 - PUSER) - 1) * \ ! (PRIO_MAX + 1) / (PRIO_MAX - PRIO_MIN + 1)) ! #define INVERSE_ESTCPU_WEIGHT 16 /* Resol. of estcpu for priorities. */ ! #define PPQ ((MAXPRI + 1) / NQS) /* Priorities per queue. */ struct mtx; --- This works by making the steady-state value of p_estcpu proportional to (PRIO_MAX - p->p_nice + 1) = (21 - p->p_nice). This gives interestingly different ramping up of the priorities: the initial priority is now independent of p_nice, so niced processes aren't completely locked out by short-lived unniced processes. I have a better fix that uses a table of multipliers instead of the divisor (PRIO_MAX - p->p_nice + 1) in the above. It is unfinished in different ways. Correctly limiting p_estcpu and/or scaling is a problem in all versions. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 8: 6:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 7E9B737B491 for ; Sun, 4 Feb 2001 08:06:27 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f14G6Qh70979 for ; Sun, 4 Feb 2001 11:06:27 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 4 Feb 2001 11:06:26 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-current@FreeBSD.org Subject: Reclaim 8 0 Killed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Updated to a recent -CURRENT yesterday on one of my boxes, and noticed a slightly unusual shutdown message: syncing disks... 8 8 5 5 1 1 done Reclaim 8 0 Killed Uptime: 10h23m28s Rebooting... Don't know what it means, or if it's harmful, but it's certainly different :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 8:10:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 35BFB37B491; Sun, 4 Feb 2001 08:10:30 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f14GAdB19407; Sun, 4 Feb 2001 17:10:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: freebsd-current@FreeBSD.ORG Subject: Re: Reclaim 8 0 Killed In-Reply-To: Your message of "Sun, 04 Feb 2001 11:06:26 EST." Date: Sun, 04 Feb 2001 17:10:38 +0100 Message-ID: <19405.981303038@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's normal. bpf implements what I currently have for my preferred way of preventing a DoS with cloning devices. The message indicates that the bpf0 device node were reclaimed. Poul-Henning In message , Robert Watson writes: > >Updated to a recent -CURRENT yesterday on one of my boxes, and noticed a >slightly unusual shutdown message: > > syncing disks... 8 8 5 5 1 1 > done > Reclaim 8 0 Killed > Uptime: 10h23m28s > Rebooting... > >Don't know what it means, or if it's harmful, but it's certainly different >:-). > >Robert N M Watson FreeBSD Core Team, TrustedBSD Project >robert@fledge.watson.org NAI Labs, Safeport Network Services > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 8:33: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 40D4237B491 for ; Sun, 4 Feb 2001 08:32:38 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f14GWbh71183 for ; Sun, 4 Feb 2001 11:32:37 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 4 Feb 2001 11:32:36 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-current@FreeBSD.org Subject: Advansys driver problems: adv1 probe now fails (Invalid baseport ... Failing probe) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-878574975-981304356=:65610" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-878574975-981304356=:65610 Content-Type: TEXT/PLAIN; charset=US-ASCII Recently, I updated a box with an ISA Advansys controller card + HP CD Burner to -CURRENT. On doing so, I discovered that my machine crashed at boot due to a NULL pointer passed to free(). John Baldwin provided me with a set of patches that appears to correct bugs in the Advansys (adv) driver that resolve this problem, allowing the probe to continue through (and then fail gracefully, as opposed to panicking). I've attached the references to the patches he provided to this e-mail. It should be pointed out, just for reference, that I've used this card successfully under FreeBSD for a number of years, and the hardware is believed to be in reasonable shape. It's sort of an interesting story, however. I updated in October, and discovered the box crashed--I didn't have time to deal with it then, so added a "disable adv0" to my /boot/kernel.conf. Putting that in there caused the device to probe as adv1, and work fine. Taking out the "disable adv0" causes the October kernel to panic in free() also. I've included three dmesg snippets from boot -v. after.txt Feb 3, 2001 + jhb patches with "di adv0" in kernel.conf after-2.txt Feb 3, 2001 + jhb patches without "di adv0" in kernel.conf before.txt Sep 29, 2000 with "di adv0" in kernel.conf before-2.txt Sep 29, 2000 without "di adv0" in kernel.conf before-2 includes a panic, needless to say, due to breakage in the driver resulting in free() dying. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Sat, 3 Feb 2001 12:42:12 -0800 (PST) From: John Baldwin To: rwatson@FreeBSD.org Subject: adv patch Robert, A patch can be found at http://www.FreeBSD.org/~jhb/patches/adv.patch It compiles at least. John --0-878574975-981304356=:65610 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="after.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: after.txt Li4uDQphZHYwOiBBZHZhblN5cyBTQ1NJIEhvc3QgQWRhcHRlciwgU0NTSSBJ RCA3LCBxdWV1ZSBkZXB0aCAxNg0KYWR2MCBmYWlsZWQgdG8gcHJvYmUgYXQg cG9ydCAweDExMCBpcnEgMTUgZHJxIDcgb24gaXNhMA0KLi4uDQppc2FfcHJv YmVfY2hpbGRyZW46IHByb2JpbmcgUG5QIGRldmljZXMNCmFkdjE6IEFkdmFu U3lzIFNDU0kgSG9zdCBBZGFwdGVyLCBTQ1NJIElEIDcsIHF1ZXVlIGRlcHRo IDE2DQphZHYxOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4MjAgc3BlY2lmaWVk LiBOZWFyZXN0IHZhbGlkIGJhc2Vwb3J0IGlzIDB4MTAwLiAgRmFpbA0KaW5n IHByb2JlLg0KYWR2MTogSW52YWxpZCBiYXNlcG9ydCBvZiAweDAgc3BlY2lm aWVkLiBOZWFyZXN0IHZhbGlkIGJhc2Vwb3J0IGlzIDB4MTAwLiAgRmFpbGkN Cm5nIHByb2JlLg0KYWR2MTogSW52YWxpZCBiYXNlcG9ydCBvZiAweDQwIHNw ZWNpZmllZC4gTmVhcmVzdCB2YWxpZCBiYXNlcG9ydCBpcyAweDEwMC4gIEZh aWwNCmluZyBwcm9iZS4NCmFkdjE6IEludmFsaWQgYmFzZXBvcnQgb2YgMHg3 MCBzcGVjaWZpZWQuIE5lYXJlc3QgdmFsaWQgYmFzZXBvcnQgaXMgMHgxMDAu ICBGYWlsDQppbmcgcHJvYmUuDQp1bmtub3duOiA8UE5QMDMwMz4gY2FuJ3Qg YXNzaWduIHJlc291cmNlcw0KdW5rbm93bjogPFBOUDAzMDM+IGF0IHBvcnQg MHg2MCBvbiBpc2EwDQphZHYxOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4NjEg c3BlY2lmaWVkLiBOZWFyZXN0IHZhbGlkIGJhc2Vwb3J0IGlzIDB4MTAwLiAg RmFpbA0KaW5nIHByb2JlLg0KdW5rbm93bjogPFBOUDA4MDA+IGZhaWxlZCB0 byBwcm9iZSBhdCBwb3J0IDB4NjEgb24gaXNhMA0KYWR2MTogSW52YWxpZCBi YXNlcG9ydCBvZiAweGYwIHNwZWNpZmllZC4gTmVhcmVzdCB2YWxpZCBiYXNl cG9ydCBpcyAweDEwMC4gIEZhaWwNCmluZyBwcm9iZS4NCmFkdjE6IEludmFs aWQgYmFzZXBvcnQgb2YgMHg0MDAgc3BlY2lmaWVkLiBOZWFyZXN0IHZhbGlk IGJhc2Vwb3J0IGlzIDB4MzMwLiAgRmFpDQpsaW5nIHByb2JlLg0KdW5rbm93 bjogPFBOUDBjMDI+IGNhbid0IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246 IDxQTlAwYzAyPiBhdCBwb3J0IDB4MTAtMHgxZiwweDIyLTB4M2Ygb24gaXNh MA0KdW5rbm93bjogPFBOUDA1MDE+IGNhbid0IGFzc2lnbiByZXNvdXJjZXMN CnVua25vd246IDxQTlAwNTAxPiBhdCBwb3J0IDB4M2Y4LTB4M2ZmIG9uIGlz YTANCnVua25vd246IDxQTlAwNDAwPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2Vz DQp1bmtub3duOiA8UE5QMDQwMD4gYXQgcG9ydCAweDM3OC0weDM3YiBvbiBp c2EwDQp1bmtub3duOiA8UE5QMDcwMD4gY2FuJ3QgYXNzaWduIHJlc291cmNl cw0KdW5rbm93bjogPFBOUDA3MDA+IGF0IHBvcnQgMHgzZjAtMHgzZjUgb24g aXNhMA0KYWR2MTogSW52YWxpZCBiYXNlcG9ydCBvZiAweDExMSBzcGVjaWZp ZWQuIE5lYXJlc3QgdmFsaWQgYmFzZXBvcnQgaXMgMHgxMjAuICBGYWkNCmxp bmcgcHJvYmUuDQp1bmtub3duOiA8QUJQNTE0MD4gZmFpbGVkIHRvIHByb2Jl IGF0IHBvcnQgMHgxMTEtMHgxMjAgaW9tZW0gMHhjODAwMC0weGNmZmZmIGly cQ0KIDExIGRycSA1IG9uIGlzYTANCi4uLg0K --0-878574975-981304356=:65610 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="after-2.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: after-2.txt YWR2MDogQWR2YW5TeXMgU0NTSSBIb3N0IEFkYXB0ZXIsIFNDU0kgSUQgNywg cXVldWUgZGVwdGggMTYNCmFkdjAgZmFpbGVkIHRvIHByb2JlIGF0IHBvcnQg MHgxMTAgaXJxIDE1IGRycSA3IG9uIGlzYTANCi4uLg0KYWR2MTogQWR2YW5T eXMgU0NTSSBIb3N0IEFkYXB0ZXIsIFNDU0kgSUQgNywgcXVldWUgZGVwdGgg MTYNCmFkdjE6IEludmFsaWQgYmFzZXBvcnQgb2YgMHgyMCBzcGVjaWZpZWQu IE5lYXJlc3QgdmFsaWQgYmFzZXBvcnQgaXMgMHgxMDAuICBGYWlsDQppbmcg cHJvYmUuDQphZHYxOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4MCBzcGVjaWZp ZWQuIE5lYXJlc3QgdmFsaWQgYmFzZXBvcnQgaXMgMHgxMDAuICBGYWlsaQ0K bmcgcHJvYmUuDQphZHYxOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4NDAgc3Bl Y2lmaWVkLiBOZWFyZXN0IHZhbGlkIGJhc2Vwb3J0IGlzIDB4MTAwLiAgRmFp bA0KaW5nIHByb2JlLg0KYWR2MTogSW52YWxpZCBiYXNlcG9ydCBvZiAweDcw IHNwZWNpZmllZC4gTmVhcmVzdCB2YWxpZCBiYXNlcG9ydCBpcyAweDEwMC4g IEZhaWwNCmluZyBwcm9iZS4NCnVua25vd246IDxQTlAwMzAzPiBjYW4ndCBh c3NpZ24gcmVzb3VyY2VzDQp1bmtub3duOiA8UE5QMDMwMz4gYXQgcG9ydCAw eDYwIG9uIGlzYTANCmFkdjE6IEludmFsaWQgYmFzZXBvcnQgb2YgMHg2MSBz cGVjaWZpZWQuIE5lYXJlc3QgdmFsaWQgYmFzZXBvcnQgaXMgMHgxMDAuICBG YWlsDQppbmcgcHJvYmUuDQp1bmtub3duOiA8UE5QMDgwMD4gZmFpbGVkIHRv IHByb2JlIGF0IHBvcnQgMHg2MSBvbiBpc2EwDQphZHYxOiBJbnZhbGlkIGJh c2Vwb3J0IG9mIDB4ZjAgc3BlY2lmaWVkLiBOZWFyZXN0IHZhbGlkIGJhc2Vw b3J0IGlzIDB4MTAwLiAgRmFpbA0KaW5nIHByb2JlLg0KYWR2MTogSW52YWxp ZCBiYXNlcG9ydCBvZiAweDQwMCBzcGVjaWZpZWQuIE5lYXJlc3QgdmFsaWQg YmFzZXBvcnQgaXMgMHgzMzAuICBGYWkNCmxpbmcgcHJvYmUuDQp1bmtub3du OiA8UE5QMGMwMj4gY2FuJ3QgYXNzaWduIHJlc291cmNlcw0KdW5rbm93bjog PFBOUDBjMDI+IGF0IHBvcnQgMHgxMC0weDFmLDB4MjItMHgzZiBvbiBpc2Ew DQp1bmtub3duOiA8UE5QMDUwMT4gY2FuJ3QgYXNzaWduIHJlc291cmNlcw0K dW5rbm93bjogPFBOUDA1MDE+IGF0IHBvcnQgMHgzZjgtMHgzZmYgb24gaXNh MA0KdW5rbm93bjogPFBOUDA0MDA+IGNhbid0IGFzc2lnbiByZXNvdXJjZXMN CnVua25vd246IDxQTlAwNDAwPiBhdCBwb3J0IDB4Mzc4LTB4MzdiIG9uIGlz YTANCnVua25vd246IDxQTlAwNzAwPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2Vz DQp1bmtub3duOiA8UE5QMDcwMD4gYXQgcG9ydCAweDNmMC0weDNmNSBvbiBp c2EwDQphZHYxOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4MTExIHNwZWNpZmll ZC4gTmVhcmVzdCB2YWxpZCBiYXNlcG9ydCBpcyAweDEyMC4gIEZhaQ0KbGlu ZyBwcm9iZS4NCnVua25vd246IDxBQlA1MTQwPiBmYWlsZWQgdG8gcHJvYmUg YXQgcG9ydCAweDExMS0weDEyMCBpb21lbSAweGM4MDAwLTB4Y2ZmZmYgaXJx DQogMTEgZHJxIDUgb24gaXNhMA0KLi4uDQoNCg== --0-878574975-981304356=:65610 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="before.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: before.txt YWR2MTogQWR2YW5TeXMgU0NTSSBIb3N0IEFkYXB0ZXIsIFNDU0kgSUQgNywg cXVldWUgZGVwdGggMTYNCmFkdjE6IDxBQlA1MTQwPiBhdCBwb3J0IDB4MTEw IGlvbWVtIDB4YzgwMDAtMHhjZmZmZiBpcnEgMTEgZHJxIDUgb24gaXNhMA0K YWR2MjogSW52YWxpZCBiYXNlcG9ydCBvZiAweDIwIHNwZWNpZmllZC4gTmVh cmVzdCB2YWxpZCBiYXNlcG9ydCBpcyAweDEwMC4gIEZhaWxpbmcgcHJvYmUu DQphZHYyOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4MCBzcGVjaWZpZWQuIE5l YXJlc3QgdmFsaWQgYmFzZXBvcnQgaXMgMHgxMDAuICBGYWlsaW5nIHByb2Jl Lg0KYWR2MjogSW52YWxpZCBiYXNlcG9ydCBvZiAweDQwIHNwZWNpZmllZC4g TmVhcmVzdCB2YWxpZCBiYXNlcG9ydCBpcyAweDEwMC4gIEZhaWxpbmcgcHJv YmUuDQphZHYyOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4NzAgc3BlY2lmaWVk LiBOZWFyZXN0IHZhbGlkIGJhc2Vwb3J0IGlzIDB4MTAwLiAgRmFpbGluZyBw cm9iZS4NCnVua25vd246IDxQTlAwMzAzPiBjYW4ndCBhc3NpZ24gcmVzb3Vy Y2VzDQp1bmtub3duOiA8UE5QMDMwMz4gYXQgcG9ydCAweDYwIG9uIGlzYTAN CmFkdjI6IEludmFsaWQgYmFzZXBvcnQgb2YgMHg2MSBzcGVjaWZpZWQuIE5l YXJlc3QgdmFsaWQgYmFzZXBvcnQgaXMgMHgxMDAuICBGYWlsaW5nIHByb2Jl Lg0KdW5rbm93bjogPFBOUDA4MDA+IGZhaWxlZCB0byBwcm9iZSBhdCBwb3J0 IDB4NjEgb24gaXNhMA0KYWR2MjogSW52YWxpZCBiYXNlcG9ydCBvZiAweGYw IHNwZWNpZmllZC4gTmVhcmVzdCB2YWxpZCBiYXNlcG9ydCBpcyAweDEwMC4g IEZhaWxpbmcgcHJvYmUuDQphZHYyOiBJbnZhbGlkIGJhc2Vwb3J0IG9mIDB4 NDAwIHNwZWNpZmllZC4gTmVhcmVzdCB2YWxpZCBiYXNlcG9ydCBpcyAweDMz MC4gIEZhaWxpbmcgcHJvYmUuDQphZHYyOiBJbnZhbGlkIGJhc2Vwb3J0IG9m IDB4MTAgc3BlY2lmaWVkLiBOZWFyZXN0IHZhbGlkIGJhc2Vwb3J0IGlzIDB4 MTAwLiAgRmFpbGluZyBwcm9iZS4NCnVua25vd246IDxQTlAwNTAxPiBjYW4n dCBhc3NpZ24gcmVzb3VyY2VzDQp1bmtub3duOiA8UE5QMDUwMT4gYXQgcG9y dCAweDNmOC0weDNmZiBvbiBpc2EwDQp1bmtub3duOiA8UE5QMDQwMD4gY2Fu J3QgYXNzaWduIHJlc291cmNlcw0KdW5rbm93bjogPFBOUDA0MDA+IGF0IHBv cnQgMHgzNzgtMHgzN2Igb24gaXNhMA0KdW5rbm93bjogPFBOUDA3MDA+IGNh bid0IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246IDxQTlAwNzAwPiBhdCBw b3J0IDB4M2YwLTB4M2Y1IG9uIGlzYTANCkJJT1MgR2VvbWV0cmllczoNCiAw OjAyMGNmZTNmIDAuLjUyND01MjUgY3lsaW5kZXJzLCAwLi4yNTQ9MjU1IGhl YWRzLCAxLi42Mz02MyBzZWN0b3JzDQogMCBhY2NvdW50ZWQgZm9yDQpEZXZp Y2UgY29uZmlndXJhdGlvbiBmaW5pc2hlZC4NCg0KLi4uDQoNCldhaXRpbmcg MTUgc2Vjb25kcyBmb3IgU0NTSSBkZXZpY2VzIHRvIHNldHRsZQ0KKHByb2Jl MjphZHYxOjA6MjowKTogSU5RVUlSWS4gQ0RCOiAxMiAxIDgwIDAgZmYgMCAN Cihwcm9iZTI6YWR2MTowOjI6MCk6IElMTEVHQUwgUkVRVUVTVCBhc2M6MjQs MA0KKHByb2JlMjphZHYxOjA6MjowKTogSW52YWxpZCBmaWVsZCBpbiBDREIg c2tzOmMwLDINCkNyZWF0aW5nIERJU0sgY2QwDQpwYXNzMCBhdCBhZHYxIGJ1 cyAwIHRhcmdldCAyIGx1biAwDQpwYXNzMDogPEhQIEM0MzI0L0M0MzI1IDEu Mjc+IFJlbW92YWJsZSBDRC1ST00gU0NTSS0yIGRldmljZSANCnBhc3MwOiAz LjMwME1CL3MgdHJhbnNmZXJzDQoNCi4uLg0KDQooY2QwOmFkdjE6MDoyOjAp OiBSRUFEIENEIFJFQ09SREVEIENBUEFDSVRZLiBDREI6IDI1IDAgMCAwIDAg MCAwIDAgMCAwIA0KKGNkMDphZHYxOjA6MjowKTogTk9UIFJFQURZIGFzYzo0 LDANCihjZDA6YWR2MTowOjI6MCk6IExvZ2ljYWwgdW5pdCBub3QgcmVhZHks IGNhdXNlIG5vdCByZXBvcnRhYmxlDQpjZDAgYXQgYWR2MSBidXMgMCB0YXJn ZXQgMiBsdW4gMA0KY2QwOiA8SFAgQzQzMjQvQzQzMjUgMS4yNz4gUmVtb3Zh YmxlIENELVJPTSBTQ1NJLTIgZGV2aWNlIA0KY2QwOiAzLjMwME1CL3MgdHJh bnNmZXJzDQpjZDA6IEF0dGVtcHQgdG8gcXVlcnkgZGV2aWNlIHNpemUgZmFp bGVkOiBOT1QgUkVBRFksIExvZ2ljYWwgdW5pdCBub3QgcmVhZHksIGNhdXNl IG5vdCByZXBvcnRhYmxlDQoNCg== --0-878574975-981304356=:65610 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="before-2.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: before-2.txt YWR2MDogQWR2YW5TeXMgU0NTSSBIb3N0IEFkYXB0ZXIsIFNDU0kgSUQgNywg cXVldWUgZGVwdGggMTYNCg0KDQpGYXRhbCB0cmFwIDEyOiBwYWdlIGZhdWx0 IHdoaWxlIGluIGtlcm5lbCBtb2RlDQpmYXVsdCB2aXJ0dWFsIGFkZHJlc3Mg ICA9IDB4YzBhODk5YjgNCmZhdWx0IGNvZGUgICAgICAgICAgICAgID0gc3Vw ZXJ2aXNvciByZWFkLCBwYWdlIG5vdCBwcmVzZW50DQppbnN0cnVjdGlvbiBw b2ludGVyICAgICA9IDB4ODoweGMwMWNmZDU4DQpzdGFjayBwb2ludGVyICAg ICAgICAgICA9IDB4MTA6MHhjMDQ3OWI0OA0KZnJhbWUgcG9pbnRlciAgICAg ICAgICAgPSAweDEwOjB4YzA0NzliNjANCmNvZGUgc2VnbWVudCAgICAgICAg ICAgID0gYmFzZSAweDAsIGxpbWl0IDB4ZmZmZmYsIHR5cGUgMHgxYg0KICAg ICAgICAgICAgICAgICAgICAgICAgPSBEUEwgMCwgcHJlcyAxLCBkZWYzMiAx LCBncmFuIDENCnByb2Nlc3NvciBlZmxhZ3MgICAgICAgID0gaW50ZXJydXB0 IGVuYWJsZWQsIHJlc3VtZSwgSU9QTCA9IDANCmN1cnJlbnQgcHJvY2VzcyAg ICAgICAgID0gMCAoc3dhcHBlcikNCmtlcm5lbDogdHlwZSAxMiB0cmFwLCBj b2RlPTANClN0b3BwZWQgYXQgICAgICBmcmVlKzB4MjQ6ICAgICAgbW92c3ds ICAwKCVlYXgpLCVlY3gNCmRiPiB0cmFjZQ0KZnJlZSgwLGMwM2E4YjgwLGMw ZDQ4YjAwLGMwNDc5YmE4LGMwMmViMzhlKSBhdCBmcmVlKzB4MjQNCmFkdl9m cmVlKGMwZDQ4YjAwLGMwZDA1MDc4LGMwY2ZkZjgwLGMwZDRkYzAwLGZmZmZm ZikgYXQgYWR2X2ZyZWUrMHg4ZQ0KYWR2X2lzYV9wcm9iZShjMGQ0ZGMwMCxj MGQ0ZGMwMCxjMGQ0NDU4MCxjMGQ0ZGMwMCwxKSBhdCBhZHZfaXNhX3Byb2Jl KzB4MTEyDQpkZXZpY2VfcHJvYmVfY2hpbGQoYzBkNDQ1ODAsYzBkNGRjMDAs YzBkNGRjMDAsYzA0NzljMTgsMCkgYXQgZGV2aWNlX3Byb2JlX2NoaWxkKzB4 Y2ENCmRldmljZV9wcm9iZV9hbmRfYXR0YWNoKGMwZDRkYzAwKSBhdCBkZXZp Y2VfcHJvYmVfYW5kX2F0dGFjaCsweDM1DQppc2FfcHJvYmVfY2hpbGRyZW4o YzBkNDQ1ODApIGF0IGlzYV9wcm9iZV9jaGlsZHJlbisweGRlDQpjb25maWd1 cmUoMCw0NzdjMDAsNDc3MDAwLDAsYzAxMjcxNDIpIGF0IGNvbmZpZ3VyZSsw eDRhDQptaV9zdGFydHVwKCkgYXQgbWlfc3RhcnR1cCsweDY4DQpiZWdpbigp IGF0IGJlZ2luKzB4MjkNCmRiPiANCg0K --0-878574975-981304356=:65610-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 13:10:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (unknown [213.162.128.50]) by hub.freebsd.org (Postfix) with ESMTP id 2C7D637B491 for ; Sun, 4 Feb 2001 13:10:29 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id 6728B2DC0B; Sun, 4 Feb 2001 22:16:52 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id C50147817; Sun, 4 Feb 2001 22:11:33 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id C0C6210E1C for ; Sun, 4 Feb 2001 22:11:33 +0100 (CET) Date: Sun, 4 Feb 2001 22:11:33 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: Broken procfs/status, related to kthreads Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Whoever made procfs aware of kernel threads broke also the /proc/%pid/status line. Or, maybe it's a by-product of showing kthreads in the proc table... According to procfs(5), the status line contains several well-defined fields separated by spaces. However, the kernel thread names look like 'swi5: task queue' and 'swi1: net', which results in variable number of space-separated fields. As a consequence, some software that parses this line gives incorrect results. I noticed this while trying to fix mysterious coredumps in src/release/picobsd/tinyware/aps (which is obsolete anyway, but it should work). Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 14:37: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7246537B491 for ; Sun, 4 Feb 2001 14:36:44 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id JAA00147; Mon, 5 Feb 2001 09:36:28 +1100 Date: Mon, 5 Feb 2001 09:36:09 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG Subject: Re: Broken procfs/status, related to kthreads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Feb 2001, Andrzej Bialecki wrote: > According to procfs(5), the status line contains several well-defined > fields separated by spaces. However, the kernel thread names look like > 'swi5: task queue' and 'swi1: net', which results in variable number of > space-separated fields. As a consequence, some software that parses this > line gives incorrect results. I think procfs never actually implemented this. Program names may have spaces in them too. Of course, the line is too hard to parse if the first "field" has spaces in it. Only MAXCOMLEN and NAME_MAX prevent the command name being the contents of another process's status line :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 15: 1:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id 6659837B401; Sun, 4 Feb 2001 15:01:00 -0800 (PST) Received: (from gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) id XAA18659; Sun, 4 Feb 2001 23:00:58 GMT (envelope-from gabriel) Date: Sun, 4 Feb 2001 23:00:58 +0000 From: Jose Gabriel J Marcelino To: freebsd-mobile@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Aironet under NEWCARD Message-ID: <20010204230058.A18603@devils.maquina.com> References: <20010204025751.A16147@devils.maquina.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010204025751.A16147@devils.maquina.com>; from gabriel@maquina.com on Sun, Feb 04, 2001 at 02:57:51AM +0000 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Replying to myself. Seeing no answers I decided to work a little on adding the NEWCARD support to an(4) and I'm now sending this using it :-) It works ok, but card reinsertions cause at least this notebook to panic. I've submitted a PR with the appropriate patches. It's online at: http://www.freebsd.org/cgi/query-pr.cgi?pr=24854 Now I'm on to that ich (i810 and 440MX) AC97 audio driver :-) Regards Gabriel On Sun, Feb 04, 2001 at 02:57:51AM +0000, Jose Gabriel J Marcelino wrote: > Hi, > - The main problem however is that now the OLDCARD kernel crashes after > I remove my Cisco 340 (Aironet) PC Card from the only PC card slot present. > > I can give more detailed information on that if someone wants it, but I guess > the later has to do with the NEWCARD changes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 15:19:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from postfix2-2.free.fr (postfix2-2.free.fr [213.228.0.140]) by hub.freebsd.org (Postfix) with ESMTP id E889237B401 for ; Sun, 4 Feb 2001 15:19:36 -0800 (PST) Received: from localhost (rouen-41-202.dial.proxad.net [213.228.41.202]) by postfix2-2.free.fr (Postfix) with ESMTP id 4C8396B65A for ; Mon, 5 Feb 2001 00:19:34 +0100 (CET) X-Sender: medical.acps@free.fr From: jcb To: current@freebsd.org Date: Mon, 05 Feb 2001 22:05:00 +0100 Subject: 25.000 EMAILS MEDECINS Organization: acps MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20010204231934.4C8396B65A@postfix2-2.free.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cher Mr ou Mme. Nous vous prions de bien vouloir trouver ci-dessous une information concernant les adresses électroniques concernant les disciplines suivantes. Médecins généralistes et spécialistes-kinésithérapeutes-homéopathes-gynécologues-rhumatologues-pneumo logues-gastro-entérologues-psychiatres-infirmières-cliniques- hopitaux Quantité 25.000 ADRESSES @MAILS PAYS : FRANCE BELGIQUE SUISSE Livraison par @mail ou sur disquette Pc - Mac Espérant répondre à votre attente, Vous souhaitant bonne réception de la présente. Dans l'attente de vous lire recevez mes cordiales salutations. Jc Boulan ACPS jcb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 17: 5:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id BD29B37B684 for ; Sun, 4 Feb 2001 17:05:22 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA81389; Sun, 4 Feb 2001 17:05:12 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A7DFC47.C76A9872@FreeBSD.org> Date: Sun, 04 Feb 2001 17:05:11 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Szilveszter Adam Cc: freebsd-current@FreeBSD.org Subject: Re: Dangling symlink in /usr/compat/linux References: <3A7D28EA.9EF46BAE@gorean.org> <20010204112342.A15191@petra.hos.u-szeged.hu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Szilveszter Adam wrote: > > On Sun, Feb 04, 2001 at 02:03:22AM -0800, Doug Barton wrote: > > FYI, /usr/compat/linux/usr/lib/X11 points to ../X11R6/lib/X11, but > > there is no X11 in /usr/compat/linux/usr/X11R6/lib. There are linux X > > libraries in the directory, although I'm not sure what the right change > > would be. > > Are you sure? Ummm... duh. :) I confirmed this on two machines. > This what I get: > > [11:19, Feb 04., Sun] cc@fonix:/home/cc ttyv4 % ls -l > /usr/compat/linux/usr/lib/X11/ > total 2 > drwxr-xr-x 2 root wheel 2048 Nov 17 14:03 config > [11:19, Feb 04., Sun] cc@fonix:/home/cc ttyv4 % ls -l > /usr/compat/linux/usr/X11R6/lib/X11/ > total 2 > drwxr-xr-x 2 root wheel 2048 Nov 17 14:03 config > > Seems to be in order to me... at least, the symlink definitely points to > somewhere that exists. Have you installed any linux X apps other than real player? That and netscape are all I have installed. > (I installed linux-base quite some time ago but I know it works because I > use RealPlayer every day:-) Me too. Doug -- "Pain heals. Chicks dig scars. Glory . . . lasts forever." -- Keanu Reeves as Shane Falco in "The Replacements" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 17:31: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id 1845437B491; Sun, 4 Feb 2001 17:30:41 -0800 (PST) Received: (from gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) id BAA19123; Mon, 5 Feb 2001 01:30:38 GMT (envelope-from gabriel) Date: Mon, 5 Feb 2001 01:30:38 +0000 From: Jose Gabriel J Marcelino To: freebsd-mobile@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Aironet/NEWCARD reinsertion panic Message-ID: <20010205013038.B19069@devils.maquina.com> References: <20010204025751.A16147@devils.maquina.com> <20010204230058.A18603@devils.maquina.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010204230058.A18603@devils.maquina.com>; from gabriel@maquina.com on Sun, Feb 04, 2001 at 11:00:58PM +0000 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, Ok, some people tried to help me find out why does the Aironet driver panic on reinsertion, under NEWCARD with my recent patch (see previous message and PR) however I need additional help to find the problem. I'm including the complete details on the events leading to the panic. My kernel conf is at: http://devils.maquina.com/~gabriel/MINIME Verbose kernel boot dmesgs are at: http://devils.maquina.com/~gabriel/boot.newcard Card attach messages are at: http://devils.maquina.com/~gabriel/boot.an The debug dmesg I get on NEWCARD after removing the card: pccard1: 00 CD 3b cardbus0: Detaching card: no cards to detach! pccbb_pcic_socket_disable pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb0: WARNING: Resource left allocated! This is a bug... (rid=0, type=3, addr=44001000) pccbb0: WARNING: Resource left allocated! This is a bug... (rid=0, type=1, addr=b) pccbb0: WARNING: Resource left allocated! This is a bug... (rid=0, type=4, addr=100) This is suspicious, however I'm not sure where's the problem. After that, after I reinsert the card I get lots of scrolling lines like this: CISTPL_NONE 00 And after that DDB takes over: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xcaed8000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01672c0 stack pointer = 0x10:0xc9f43c8c frame pointer = 0x10:0xc9f43e74 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 7 (pccbb0) kernel: type 12 trap, code=0 Stopped at pccard_scan_cis+0x120: movb 0(%eax,%edx,1),%al db> trace pccard_scan_cis(c1082680,c0167e0c,c9f43e88,0,0) at pccard_scan_cis+0x120 pccard_read_cis(c1091a00) at pccard_read_cis+0xa9 pccard_attach_card(c1082680) at pccard_attach_card+0xc5 pccbb_insert(c1091c00,c9f43fa8,c1091c00,c9f43f94,c01b659d) at pccbb_insert+0x9e pccbb_event_thread(c1091c00,c9f43fa8) at pcbb_event_thread+0x37 fork_exit(c0287278,c1091c00,c9f43fa8) at fork_exit+0x2d fork_trampoline() at fork_trampoline+0x8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 17:55:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6721837B401; Sun, 4 Feb 2001 17:54:57 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f151sbV07104; Mon, 5 Feb 2001 02:54:38 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 5 Feb 2001 03:01:46 +0100 (CET) From: Martin Blapp To: Jun Kuriyama Cc: freebsd-current@FreeBSD.ORG, snap-users@kame.net, alfred@FreeBSD.ORG Subject: Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, So, I have merged in the newest libc changes and fixed some buildworld issues. It still needs some _THREAD_SAFE fixes I guess, cause we build now thread-safe libc per default. But we can do this later ... Go into your CURRENT source tree and execute the shell archive, it will create the necessary directories and remove some files to prevent appling files two times. You find the TI-RPC patch on: http:/www.attic.ch/patches/rpc.diff_04022001.sh.tgz Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 17:56:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 9865A37B4EC; Sun, 4 Feb 2001 17:56:18 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f151uEV07166; Mon, 5 Feb 2001 02:56:14 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 5 Feb 2001 03:03:22 +0100 (CET) From: Martin Blapp To: Jun Kuriyama Cc: freebsd-current@FreeBSD.ORG, snap-users@kame.net, alfred@FreeBSD.ORG Subject: Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Argl, the correct URL is of course: http://www.attic.ch:80/patches/rpc.diff_04022001.sh.tgz Cheers: Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ On Mon, 5 Feb 2001, Martin Blapp wrote: > > Hi, > > So, I have merged in the newest libc changes and fixed some > buildworld issues. It still needs some _THREAD_SAFE fixes I > guess, cause we build now thread-safe libc per default. But > we can do this later ... > > Go into your CURRENT source tree and execute the shell archive, > it will create the necessary directories and remove some files > to prevent appling files two times. > > You find the TI-RPC patch on: > > http:/www.attic.ch/patches/rpc.diff_04022001.sh.tgz > > Martin > > Martin Blapp, mb@imp.ch > ------------------------------------------------ > Improware AG, UNIX solution and service provider > Zurlindenstrasse 29, 4133 Pratteln, Switzerland > Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 > ------------------------------------------------ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 20:30:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.83]) by hub.freebsd.org (Postfix) with ESMTP id A2A7437B491 for ; Sun, 4 Feb 2001 20:29:52 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id 8218A5350E; Mon, 5 Feb 2001 11:29:44 +0700 (JAVT) Date: Mon, 5 Feb 2001 11:29:44 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: buildkernel target died... Message-ID: <20010205112944.A615@office.naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Latest -CURRENT buidkernel died with this error messages: ===> sound/driver ===> sound/driver/ad1816 rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o snd_ad1816.ko snd_ad1816.kld ad1816.o @ machine symb.tmp tmp.o bus_if.h device_if.h isa_if.h pci_if.h ac97_if.h channel_if.h feeder_if.h mixer_if.h ===> sound/driver/cmi cd: can't cd to /usr/src/sys/modules/sound/driver/cmi *** Error code 2 Stop in /usr/src/sys/modules/sound/driver. *** Error code 1 Stop in /usr/src/sys/modules/sound. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/DANTE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 22: 8:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 33D0F37B491 for ; Sun, 4 Feb 2001 22:08:10 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sun, 4 Feb 2001 22:06:15 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.1) id f15675D61624 for current@freebsd.org; Sun, 4 Feb 2001 22:07:05 -0800 (PST) (envelope-from cjc) Date: Sun, 4 Feb 2001 22:07:04 -0800 From: "Crist J. Clark" To: current@freebsd.org Subject: Kernel Panic from Yesterday's CVSup Message-ID: <20010204220704.C91447@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="PNTmBPCT7hxwcZjr" X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii I don't recall reports of trouble with recent CURRENT, but my CVSup from yesterday afternoon is panicing. Before I try too debug this, has anyone been getting these or knows what I might be missing? Boot messages and the panic info are attached. -- Crist J. Clark cjclark@alum.mit.edu --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="boot.msg" 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 #1: Sun Feb 4 20:09:00 PST 2001 cjc@bubbles.cjclark.org:/usr/obj/usr/src/sys/BUBBLES Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping = 11 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30130176 (29424K bytes) Preloaded elf kernel "kernel" at 0xc02a9000. Intel Pentium detected, installing workaround for F00F bug apm0: on motherboard apm0: found APM BIOS v1.1, connected at v1.1 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 8.0 (no driver attached) ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc1: cannot reserve I/O port range sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A ep0: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:20:af:17:a3:e9 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 1000 packets/entry by default ad0: 1222MB [2484/16/63] at ata0-master BIOSPIO acd0: CDROM at ata0-slave using BIOSPIO Mounting root from ufs:/dev/ad0s1a kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xe fault code = supervisor read, page not present instruction pointer = 0x8:0xc01f2553 stack pointer = 0x10:0xc3a2bf50 frame pointer = 0x10:0xc3a2bf64 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 16 (irq14: ata0) trap number = 12 panic: page fault syncing disks... done Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot <-- --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=BUBBLES # $Id: BUBBLES,v 1.4 2001/02/04 06:49:24 cjc Exp cjc $ # # BUBBLES - 2000/11/11, cjc # # Kernel configuration for IBM Pentium 133 # # 2000/12/09, cjc - DEVEL became BUBBLES # machine i386 cpu I586_CPU ident BUBBLES maxusers 32 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options DEVFS #Device Filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING #options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci #options COMPAT_OLDISA # compatability shims for lnc, le #options COMPAT_OLDPCI # compatability shims for lnc # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # atkbdc0 controls both the keyboard and the PS/2 mouse #device atkbdc 1 # At keyboard controller #device atkbd # at keyboard #device psm # psm mouse #device vga # VGA screen # splash screen/screen saver #device splash # syscons is the default console driver, resembling an SCO console #device sc 1 # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) device apm # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # ISA Ethernet NICs. pccard nics included. device ep # Etherlink III based cards # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device #options NOBLOCKRANDOM # avoid any blocking on device random device loop # Network loopback device ether # Ethernet support #device sl # Kernel SLIP #device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) #device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # Needed for ipfwlogd development options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_EXTRA_VERBOSE #print TCP flag information options IPFIREWALL_VERBOSE_LIMIT=1000 #limit verbosity options IPDIVERT #divert sockets #End --PNTmBPCT7hxwcZjr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 22:44:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 22B0337B401; Sun, 4 Feb 2001 22:43:59 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f156ht971685; Sun, 4 Feb 2001 23:43:55 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102050643.f156ht971685@harmony.village.org> To: Jose Gabriel J Marcelino Subject: Re: Aironet/NEWCARD reinsertion panic Cc: freebsd-mobile@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Mon, 05 Feb 2001 01:30:38 GMT." <20010205013038.B19069@devils.maquina.com> References: <20010205013038.B19069@devils.maquina.com> <20010204025751.A16147@devils.maquina.com> <20010204230058.A18603@devils.maquina.com> Date: Sun, 04 Feb 2001 23:43:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010205013038.B19069@devils.maquina.com> Jose Gabriel J Marcelino writes: : Ok, some people tried to help me find out why does the Aironet driver : panic on reinsertion, under NEWCARD with my recent patch (see previous : message and PR) however I need additional help to find the problem. *ALL* cards panic on reinsertion. At least all of them that I've tried. This has been broken in the past 2 or 3 weeks. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Feb 4 23:15:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B7AAA37B401; Sun, 4 Feb 2001 23:15:03 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f157Ex971949; Mon, 5 Feb 2001 00:14:59 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102050714.f157Ex971949@harmony.village.org> To: Jose Gabriel J Marcelino Subject: Re: Aironet/NEWCARD reinsertion panic Cc: freebsd-mobile@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Mon, 05 Feb 2001 01:30:38 GMT." <20010205013038.B19069@devils.maquina.com> References: <20010205013038.B19069@devils.maquina.com> <20010204025751.A16147@devils.maquina.com> <20010204230058.A18603@devils.maquina.com> Date: Mon, 05 Feb 2001 00:14:59 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010205013038.B19069@devils.maquina.com> Jose Gabriel J Marcelino writes: : db> trace : pccard_scan_cis(c1082680,c0167e0c,c9f43e88,0,0) at pccard_scan_cis+0x120 : pccard_read_cis(c1091a00) at pccard_read_cis+0xa9 : pccard_attach_card(c1082680) at pccard_attach_card+0xc5 : pccbb_insert(c1091c00,c9f43fa8,c1091c00,c9f43f94,c01b659d) at pccbb_insert+0x9e : pccbb_event_thread(c1091c00,c9f43fa8) at pcbb_event_thread+0x37 : fork_exit(c0287278,c1091c00,c9f43fa8) at fork_exit+0x2d : fork_trampoline() at fork_trampoline+0x8 Ah, this is a different panic than I've seeing on are removal. Looks like a resource conflict (likely unrelated to the resources not released, but there is a chance). The 16-bit support is still somewhat fragile in -current... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 0:16:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 1D92237B4EC for ; Mon, 5 Feb 2001 00:16:08 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id JAA10753; Mon, 5 Feb 2001 09:16:00 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14PgoZ-0001pO-00 for ; Mon, 05 Feb 2001 09:15:59 +0100 Date: Mon, 5 Feb 2001 09:15:59 +0100 From: Szilveszter Adam To: freebsd-current@FreeBSD.org Subject: Re: Dangling symlink in /usr/compat/linux Message-ID: <20010205091559.A5563@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.org References: <3A7D28EA.9EF46BAE@gorean.org> <20010204112342.A15191@petra.hos.u-szeged.hu> <3A7DFC47.C76A9872@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A7DFC47.C76A9872@FreeBSD.org>; from DougB@FreeBSD.org on Sun, Feb 04, 2001 at 05:05:11PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Doug, Sorry for the belated answer, I hit the hay in the meantime... but now, good morning to everybody outta there:-) On Sun, Feb 04, 2001 at 05:05:11PM -0800, Doug Barton wrote: > Ummm... duh. :) I confirmed this on two machines. OK I think I nailed it:-) I took a trip to the /var/db/pkg directory, it was very educational:-) /var/db/pkg/linux_base-6.1/+CONTENTS, the offending line in my installled copy: @exec ln -sf ../X11R6/lib/X11 %D/usr/lib/X11 @unexec rm %D/usr/lib/X11 But the port that actually did something to that directory was linux_devtools. It puts the config directory for X11 there. So you may very much be correct... unless you install linux_devtools, there may be no /usr/X11R6/lib/X11 directory at all. So short workaround: install linux_devtools:-) Long workaround: Take a long hard look at what's going on before posting to say that *it works for me* /*note to myself */ Solution: ? ( Maybe create the directory once we symlink to it? Seems like a good idea... ) (Most probably this problem never surfaced before because the maintainers had both ports installed on their systems.) Luckily, the date on the directories tipped me off, since I installed the devtools port only two days later... > Have you installed any linux X apps other than real player? That and > netscape are all I have installed. No, only Netscape, RP, Flash plugin and linux-jdk are linux apps on my system (oh yes and that unwieldy beast, Star Office) all from ports, except for RP which I downloaded quite some time ago and installed by hand and had no reason to upgrade ever since... but most of these do not put anything under the /usr/compat/linux/ hierarchy at all, but rather prefer /usr/local. > > (I installed linux-base quite some time ago but I know it works because I > > use RealPlayer every day:-) > > Me too. Using it right now:-) Good line quality from Charleston, SC. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 0:50:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (unknown [213.162.128.50]) by hub.freebsd.org (Postfix) with ESMTP id 8246D37B6A7 for ; Mon, 5 Feb 2001 00:50:29 -0800 (PST) Received: by mimer.webgiro.com (Postfix, from userid 66) id EC7622DC0F; Mon, 5 Feb 2001 09:56:51 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 37AF57817; Mon, 5 Feb 2001 09:52:10 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 2C9FA10E1C; Mon, 5 Feb 2001 09:52:10 +0100 (CET) Date: Mon, 5 Feb 2001 09:52:06 +0100 (CET) From: Andrzej Bialecki To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: Broken procfs/status, related to kthreads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Feb 2001, Bruce Evans wrote: > On Sun, 4 Feb 2001, Andrzej Bialecki wrote: > > > According to procfs(5), the status line contains several well-defined > > fields separated by spaces. However, the kernel thread names look like > > 'swi5: task queue' and 'swi1: net', which results in variable number of > > space-separated fields. As a consequence, some software that parses this > > line gives incorrect results. > > I think procfs never actually implemented this. Program names may > have spaces in them too. Of course, the line is too hard to parse if > the first "field" has spaces in it. Only MAXCOMLEN and NAME_MAX > prevent the command name being the contents of another process's > status line :-). Ok, then how should this be fixed? We could escape the space characters with something: swi5:$task$queue 14 0 0 0 -1,-1 noflags 981365276,40 0,0 0,0 nochan 0 0 0,0 - and for command name 'my$prog': my$$prog 334 1 332 0 -1,-1 noflags 981361691,37404 0,0 0,5748 select 0 0 0,0 - or similar... The commands with $ in them are much less likely than the names with spaces, which on -current are guaranteed to occur. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 1:31:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 606F237B6A1 for ; Mon, 5 Feb 2001 01:30:56 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA85664; Mon, 5 Feb 2001 01:30:26 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A7E72B2.F7855952@FreeBSD.org> Date: Mon, 05 Feb 2001 01:30:26 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Indra Cc: freebsd-current@FreeBSD.org Subject: Re: buildkernel target died... References: <20010205112944.A615@office.naver.co.id> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Indra wrote: > > Latest -CURRENT buidkernel died with this error messages: > > ===> sound/driver > ===> sound/driver/ad1816 > rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o snd_ad1816.ko snd_ad1816.kld ad1816.o @ machine symb.tmp tmp.o bus_if.h device_if.h isa_if.h pci_if.h ac97_if.h channel_if.h feeder_if.h mixer_if.h > ===> sound/driver/cmi > cd: can't cd to /usr/src/sys/modules/sound/driver/cmi > *** Error code 2 In order to follow -current you have to follow freebsd-current mailing list and the commit logs. Cameron recently committed some new stuff, then committed the makefile for it a little while after. This was all described on the lists. If you're using cvsup, try it again. If you're using cvs, make sure you include the -d flag to update. -- "Pain heals. Chicks dig scars. Glory . . . lasts forever." -- Keanu Reeves as Shane Falco in "The Replacements" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 1:46:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.83]) by hub.freebsd.org (Postfix) with ESMTP id AEF3337B401; Mon, 5 Feb 2001 01:46:42 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id BE59E5350E; Mon, 5 Feb 2001 16:46:39 +0700 (JAVT) Date: Mon, 5 Feb 2001 16:46:39 +0700 From: John Indra To: Doug Barton Cc: freebsd-current@FreeBSD.org Subject: Re: buildkernel target died... Message-ID: <20010205164639.A1717@office.naver.co.id> Mail-Followup-To: Doug Barton , freebsd-current@FreeBSD.org References: <20010205112944.A615@office.naver.co.id> <3A7E72B2.F7855952@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3A7E72B2.F7855952@FreeBSD.org>; from DougB@FreeBSD.org on Mon, Feb 05, 2001 at 01:30:26AM -0800 X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 05, 2001 at 01:30:26AM -0800, Doug Barton wrote: >In order to follow -current you have to follow freebsd-current mailing >list and the commit logs. Cameron recently committed some new stuff, then >committed the makefile for it a little while after. This was all described >on the lists. If you're using cvsup, try it again. If you're using cvs, >make sure you include the -d flag to update. Sorry... I am subscribed to freebsd-current and commit logs mailing list. But sometimes I just skip reading those commit logs :) Will try tommorrow... /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 3:53:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 807F037B401 for ; Mon, 5 Feb 2001 03:53:35 -0800 (PST) Received: (qmail 4423 invoked by uid 1000); 5 Feb 2001 11:47:17 -0000 Date: Mon, 5 Feb 2001 12:47:17 +0100 From: Andrea Campi To: freebsd-current@freebsd.org Subject: [a.campi@inet.it: Page fault] Message-ID: <20010205124716.A1955@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On -CURRENT I get this under different conditions, i.e. sometimes at boot as mentioned a couple of days ago, and today again at pccard extraction. I can provide other info if instructed as to what info you need. ;-) Bye, Andrea Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de fault code = supervisor read, page not present instruction pointer = 0x8:0xdeadc0de stack pointer = 0x10:0xc65def68 frame pointer = 0x10:0xc65def78 code segment = base 0x0, limit 0xffffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 257 (irq3: ep0) kernel: type 12 trap, code=0 Stopped at 0xdeadc0de: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de fault code = supervisor read, page not present instruction pointer = 0x8:0xc01eb46c stack pointer = 0x10:0xc65dedcc frame pointer = 0x10:0xc65dedd0 code segment = base 0x0, limit 0xffffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 257 (irq3: ep0) kernel: type 12 trap, code=0 db> -- There's no place like ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 5:38:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id CC21337B401 for ; Mon, 5 Feb 2001 05:38:13 -0800 (PST) Received: (qmail 36372 invoked by uid 1000); 4 Feb 2001 23:13:07 -0000 Date: Mon, 5 Feb 2001 00:13:07 +0100 From: Andrea Campi To: Jose Gabriel J Marcelino Cc: freebsd-mobile@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Aironet under NEWCARD Message-ID: <20010205001305.A34346@webcom.it> References: <20010204025751.A16147@devils.maquina.com> <20010204230058.A18603@devils.maquina.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010204230058.A18603@devils.maquina.com>; from gabriel@maquina.com on Sun, Feb 04, 2001 at 11:00:58PM +0000 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Now I'm on to that ich (i810 and 440MX) AC97 audio driver :-) Great news! And please MFC it asap ;-) Seriously, I've been using it on -STABLE for months, if you need volunteers for testing, I can help. Bye, Andrea > > Regards > > Gabriel > > On Sun, Feb 04, 2001 at 02:57:51AM +0000, Jose Gabriel J Marcelino wrote: > > Hi, > > - The main problem however is that now the OLDCARD kernel crashes after > > I remove my Cisco 340 (Aironet) PC Card from the only PC card slot present. > > > > I can give more detailed information on that if someone wants it, but I guess > > the later has to do with the NEWCARD changes. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Press every key to continue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 6:35:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 63B9937B401; Mon, 5 Feb 2001 06:34:46 -0800 (PST) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.1/8.11.1) with ESMTP id f15EYjU12641; Mon, 5 Feb 2001 09:34:45 -0500 (EST) Date: Mon, 5 Feb 2001 09:34:44 -0500 (EST) From: Trevor Johnson To: Shunsuke Akiyama , Subject: od driver for -CURRENT Message-ID: <200102040157370.13362-100000@blues.jpj.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od driver for magneto-optical disks, which I got from his archives at ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/OD/ . I have only tested it a little, but I'm able to do "tar cf /dev/od0 ..." under 4-STABLE and untar under Linux 2.2.16 or FreeBSD 5-CURRENT. If under -CURRENT I boot up while the MO disk (a 640 MB one) is in the drive (Olympus MOS364), the data read from it gets corrupted. That happens with the da driver as well. I merged the changes from the da driver into the od driver, so I probably brought the bug in too. Anyway, it's at http://people.freebsd.org/~trevor/src/od-20010203-current.diff.gz . -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 7: 5:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from horus.imag.fr (horus.imag.fr [129.88.38.2]) by hub.freebsd.org (Postfix) with ESMTP id 3364C37B491 for ; Mon, 5 Feb 2001 07:05:26 -0800 (PST) Received: (from richier@localhost) by horus.imag.fr (8.9.3/8.8.6) id QAA00704; Mon, 5 Feb 2001 16:05:36 +0100 (MET) Date: Mon, 5 Feb 2001 16:05:36 +0100 (MET) From: Jean-Luc Richier Message-Id: <200102051505.QAA00704@horus.imag.fr> In-Reply-To: Francis Dupont's message as of Jan 25, 16:49. Organization: IMAG, Grenoble, France X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Francis Dupont , souissi@nic.fr, snap-users@kame.net, Francois.Tigeot@nic.fr Subject: Re: (KAME-snap 3974) Re: TI-RPC, IPv6 and NFS (was: Re: strong recommendation re: NFS) Cc: Feico Dillema , Matt Dillon , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dans votre courrier du 25 Jan 16:49 vous ecrivez : > In your previous mail you wrote: > > It is not impossible to support IPv6 NFS without switching to TI-RPC, > INRIA IPv6 has the code (IIRC). > >=> this code was ported to FreeBSD 4.2. I'll give more details as soon as >I am back to my office (ie. next week). The code is available on ftp.imag.fr, directory /archive/networking/ipv6/INRIA/FreeBSD4 files FILES-NFS-FreeBSD42.tgz (files) or PATCH-NFS-FreeBSD42 (patch) It as been tested against Solaris8. > > However, if you try this, there will > be a lot of of non-intuitive typecast against library arguments. > >=> this is a matter of taste. TI-RPC is not perfect tooo (:-). and also the old RPC interface is too weak to manage correctly different types of transport at the same time. It agree that a long term solution is to change to the TI-RPC interface, but the real TI-RPC libraries are complicated. -- Jean-Luc RICHIER (Jean-Luc.Richier@Imag.Fr richier@imag.fr) Laboratoire Logiciels, Systemes et Reseaux (LSR-IMAG) IMAG-CAMPUS, BP 72, F-38402 St Martin d'Heres Cedex Tel : +33 4 76 82 72 32 Fax : +33 4 76 82 72 87 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 7:54:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 6D30A37B401; Mon, 5 Feb 2001 07:53:53 -0800 (PST) Received: from localhost (trevor@localhost) by blues.jpj.net (8.11.1/8.11.1) with ESMTP id f15Frq014998; Mon, 5 Feb 2001 10:53:52 -0500 (EST) Date: Mon, 5 Feb 2001 10:53:52 -0500 (EST) From: Trevor Johnson To: Shunsuke Akiyama , Subject: Re: od driver for -CURRENT In-Reply-To: <200102040157370.13362-100000@blues.jpj.net> Message-ID: <200102051005190.13533-100000@blues.jpj.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was able to do: # mount_msdos /dev/od0 /mnt # newfs_msdos /dev/od0 # cp mozilla-win32-0.7.zip /mnt/ under FreeBSD -CURRENT, then unzip the file under Windows 95 OSR2 with no problems. However, the patched sysinstall still crashes, and neither disklabel nor newfs are working: # disklabel -r -w /dev/od0 mo640 disklabel: ioctl DIOCWLABEL: Operation not supported by device # newfs -T mo640 /dev/od0c Warning: Block size restricts cylinders per group to 10. Warning: 3776 sector(s) in last cylinder unallocated /dev/od0c: 1241408 sectors in 76 cylinders of 1 tracks, 16384 sectors 606.2MB in 8 cyl groups (10 c/g, 80.00MB/g, 9600 i/g) super-block backups (for fsck -b #) at: write error: 1241404 newfs: wtfs - writecombine: Invalid argument -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 9:48:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from karon.dynas.se (karon.dynas.se [192.71.43.4]) by hub.freebsd.org (Postfix) with SMTP id 62F7337B491 for ; Mon, 5 Feb 2001 09:48:12 -0800 (PST) Received: (qmail 60170 invoked from network); 5 Feb 2001 17:48:10 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by 172.16.1.1 with SMTP; 5 Feb 2001 17:48:10 -0000 Received: (qmail 29658 invoked from network); 5 Feb 2001 17:48:09 -0000 Received: from explorer.rsa.com (10.81.217.59) by spirit.dynas.se with SMTP; 5 Feb 2001 17:48:09 -0000 Received: (from mikko@localhost) by explorer.rsa.com (8.11.1/8.11.1) id f15Hm1976448; Mon, 5 Feb 2001 09:48:01 -0800 (PST) (envelope-from mikko) Date: Mon, 5 Feb 2001 09:48:01 -0800 (PST) From: Mikko Tyolajarvi Message-Id: <200102051748.f15Hm1976448@explorer.rsa.com> To: abial@webgiro.com Cc: freebsd-current@freebsd.org Subject: Re: Broken procfs/status, related to kthreads Newsgroups: local.freebsd.current References: X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd.current you write: >On Mon, 5 Feb 2001, Bruce Evans wrote: [...] >> I think procfs never actually implemented this. Program names may >> have spaces in them too. Of course, the line is too hard to parse if >> the first "field" has spaces in it. Only MAXCOMLEN and NAME_MAX >> prevent the command name being the contents of another process's >> status line :-). >Ok, then how should this be fixed? >We could escape the space characters with something: >swi5:$task$queue 14 0 0 0 -1,-1 noflags 981365276,40 0,0 0,0 nochan 0 0 0,0 - >and for command name 'my$prog': >my$$prog 334 1 332 0 -1,-1 noflags 981361691,37404 0,0 0,5748 select 0 0 0,0 - >or similar... IMHO a correct solution would be to use a separator that cannot occur in any of the fields. All fields but the command name can be considered "well behaved" (= under control by procfs), and the command name is subject to file name limitations: that leaves NUL, "\n" and maybe "/" (of only the basename is shown) as safe separators. The "cmdline" file seems to solve the problem by using NULs. Come to think of it: another solution, in this case, would be to put the command name last on the line: anything beyond field N is the command name, including any spaces. But, please, no quoting. $.02, /Mikko -- Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 10: 8:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (node16292.a2000.nl [24.132.98.146]) by hub.freebsd.org (Postfix) with ESMTP id 9101D37B401 for ; Mon, 5 Feb 2001 10:07:49 -0800 (PST) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.1/8.11.1) id f15I8AU03130 for freebsd-current@freebsd.org; Mon, 5 Feb 2001 19:08:10 +0100 (CET) (envelope-from adrian) Date: Mon, 5 Feb 2001 19:08:09 +0100 From: Adrian Chadd To: freebsd-current@freebsd.org Subject: Re: Broken procfs/status, related to kthreads Message-ID: <20010205190809.A3033@roaming.cacheboy.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from abial@webgiro.com on Mon, Feb 05, 2001 at 09:52:06AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 05, 2001, Andrzej Bialecki wrote: > Ok, then how should this be fixed? > > We could escape the space characters with something: > > swi5:$task$queue 14 0 0 0 -1,-1 noflags 981365276,40 0,0 0,0 nochan 0 0 0,0 - > > and for command name 'my$prog': > > my$$prog 334 1 332 0 -1,-1 noflags 981361691,37404 0,0 0,5748 select 0 0 0,0 - > > or similar... > > The commands with $ in them are much less likely than the names with > spaces, which on -current are guaranteed to occur. .. or we output information in a new file (say, /proc/$pid/stat?) which looks like the rlimit output? I like that idea better. adrian -- Adrian Chadd "Programming is like sex: One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 14:52:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BBA0237B698 for ; Mon, 5 Feb 2001 14:52:13 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f15Mp9394918; Mon, 5 Feb 2001 14:51:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010204220704.C91447@rfx-216-196-73-168.users.reflex> Date: Mon, 05 Feb 2001 14:51:59 -0800 (PST) From: John Baldwin To: "Crist J. Clark" Subject: RE: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Feb-01 Crist J. Clark wrote: > I don't recall reports of trouble with recent CURRENT, but my CVSup > from yesterday afternoon is panicing. Before I try too debug this, has > anyone been getting these or knows what I might be missing? > > Boot messages and the panic info are attached. Could you please turn on DDB, WITNESS, and INVARIANTS in your kernel and see if you can reproduce this? Also, compile the kernel with debug symbols. Then type 'trace' at the db> prompt when it does to get a backtrace of where it blew up. Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 15:15:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 570B037B491; Mon, 5 Feb 2001 15:15:14 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f15NF8i28372 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 6 Feb 2001 00:15:11 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f15NFVr68271 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Tue, 6 Feb 2001 00:15:33 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f15NFRN00974; Tue, 6 Feb 2001 00:15:27 +0100 (CET) (envelope-from ticso) Date: Tue, 6 Feb 2001 00:15:27 +0100 From: Bernd Walter To: Trevor Johnson Cc: Shunsuke Akiyama , current@FreeBSD.ORG Subject: Re: od driver for -CURRENT Message-ID: <20010206001527.B548@cicely5.cicely.de> References: <200102040157370.13362-100000@blues.jpj.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200102040157370.13362-100000@blues.jpj.net>; from trevor@jpj.net on Mon, Feb 05, 2001 at 09:34:44AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 05, 2001 at 09:34:44AM -0500, Trevor Johnson wrote: > I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od > driver for magneto-optical disks, which I got from his archives at > ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/OD/ . I have only tested it a > little, but I'm able to do "tar cf /dev/od0 ..." under 4-STABLE and untar > under Linux 2.2.16 or FreeBSD 5-CURRENT. If under -CURRENT I boot up > while the MO disk (a 640 MB one) is in the drive (Olympus MOS364), the > data read from it gets corrupted. That happens with the da driver as > well. I merged the changes from the da driver into the od driver, so I > probably brought the bug in too. > > Anyway, > it's at http://people.freebsd.org/~trevor/src/od-20010203-current.diff.gz What is the od driver able to do that the da driver can't? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 16: 1: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 93AC237B503; Mon, 5 Feb 2001 16:00:49 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA86897; Mon, 5 Feb 2001 17:00:41 -0700 (MST) (envelope-from ken) Date: Mon, 5 Feb 2001 17:00:41 -0700 From: "Kenneth D. Merry" To: Bernd Walter Cc: Trevor Johnson , Shunsuke Akiyama , current@FreeBSD.ORG Subject: Re: od driver for -CURRENT Message-ID: <20010205170041.A86739@panzer.kdm.org> References: <200102040157370.13362-100000@blues.jpj.net> <20010206001527.B548@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010206001527.B548@cicely5.cicely.de>; from ticso@cicely5.cicely.de on Tue, Feb 06, 2001 at 12:15:27AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 06, 2001 at 00:15:27 +0100, Bernd Walter wrote: > On Mon, Feb 05, 2001 at 09:34:44AM -0500, Trevor Johnson wrote: > > I've made an attempt at an update for -CURRENT of Shunsuke Akiyama's od > > driver for magneto-optical disks, which I got from his archives at > > ftp://daemon.jp.freebsd.org/pub/FreeBSD-jp/OD/ . I have only tested it a > > little, but I'm able to do "tar cf /dev/od0 ..." under 4-STABLE and untar > > under Linux 2.2.16 or FreeBSD 5-CURRENT. If under -CURRENT I boot up > > while the MO disk (a 640 MB one) is in the drive (Olympus MOS364), the > > data read from it gets corrupted. That happens with the da driver as > > well. I merged the changes from the da driver into the od driver, so I > > probably brought the bug in too. > > > > Anyway, > > it's at http://people.freebsd.org/~trevor/src/od-20010203-current.diff.gz > > What is the od driver able to do that the da driver can't? I exchanged some mail with Akiyama-san around the end of October about the od(4) driver. In short, we'd like to make sure that the cd(4) driver and da(4) driver have the od driver's functionality, so there isn't a need for another driver. I think we already have the most important functionality from the od(4) driver in the da and cd drivers. If there are any features that are in the od(4) driver that should be in the da(4) or cd(4) drivers, but aren't, please speak up. Note that his patches also include some other filesystem-type patches, which would have to be looked at by someone who actually knows something about filesystems. :) (i.e. not me) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 17:27:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.147.1.144]) by hub.freebsd.org (Postfix) with ESMTP id B55E237B67D; Mon, 5 Feb 2001 17:27:28 -0800 (PST) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls06.mediaone.net (8.11.1/8.11.1) with ESMTP id f161RRK26658; Mon, 5 Feb 2001 20:27:27 -0500 (EST) Message-ID: <3A7F52F7.4D214AD9@acm.org> Date: Mon, 05 Feb 2001 20:27:19 -0500 From: Jim Bloom X-Mailer: Mozilla 4.76 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: "Crist J. Clark" , current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is occuring on my laptop (AST Ascentia 810N) which I can't seem to get to create a core dump. Here is a hand transcription of what I see. Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 pccard: card inserted, slot 1 kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc0270ad8 stack pointer = 0x10:0xc2fb4f50 frame pointer = 0x10:0xc2fb4f64 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 16 (irq14:ata0) kernel: type 9 trap, code=0 Stopped at sw1b+0x77: ltr %si backtrace sw1b(4000) at sw1b+0x77 (note this is actually swtch()) ithd_loop(0,c2fb4fa8) at ithd_loop+0xf7 fork_exit(c0275bd0,0,c2fb4fa8_ at fork_exit+0x2d fork_trampoline() at fork_trampoline+0x8 I don't have WITNESS or INVARIANTS at this time and don;t have a serial console so I can't capture the output. I can try adding these to my kernel and transcribe a little bit by hand. I can also send my kernel config and dmesg from a Nov kernel which boots. Jim Bloom bloom@acm.org John Baldwin wrote: > > On 05-Feb-01 Crist J. Clark wrote: > > I don't recall reports of trouble with recent CURRENT, but my CVSup > > from yesterday afternoon is panicing. Before I try too debug this, has > > anyone been getting these or knows what I might be missing? > > > > Boot messages and the panic info are attached. > > Could you please turn on DDB, WITNESS, and INVARIANTS in your kernel and see if > you can reproduce this? Also, compile the kernel with debug symbols. Then > type 'trace' at the db> prompt when it does to get a backtrace of where it blew > up. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 17:30:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id EF85F37B491 for ; Mon, 5 Feb 2001 17:30:13 -0800 (PST) Received: (qmail 8410 invoked by uid 1000); 6 Feb 2001 01:23:56 -0000 Date: Tue, 6 Feb 2001 02:23:56 +0100 From: Andrea Campi To: Jim Bloom Cc: John Baldwin , "Crist J. Clark" , current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010206022354.B613@webcom.it> References: <3A7F52F7.4D214AD9@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A7F52F7.4D214AD9@acm.org>; from bloom@acm.org on Mon, Feb 05, 2001 at 08:27:19PM -0500 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to bother everybody, but did anybody note from my panic trace, that instruction pointer is 0xdeadc0de? Isn't that bad? :-p On Mon, Feb 05, 2001 at 08:27:19PM -0500, Jim Bloom wrote: > I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is > occuring on my laptop (AST Ascentia 810N) which I can't seem to get to create a > core dump. Here is a hand transcription of what I see. > > Mounting root from ufs:/dev/ad0s1a > pccard: card inserted, slot 0 > pccard: card inserted, slot 1 > kernel trap 9 with interrupts disabled > > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x8:0xc0270ad8 > stack pointer = 0x10:0xc2fb4f50 > frame pointer = 0x10:0xc2fb4f64 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 16 (irq14:ata0) > kernel: type 9 trap, code=0 > Stopped at sw1b+0x77: ltr %si > > backtrace > sw1b(4000) at sw1b+0x77 (note this is actually swtch()) > ithd_loop(0,c2fb4fa8) at ithd_loop+0xf7 > fork_exit(c0275bd0,0,c2fb4fa8_ at fork_exit+0x2d > fork_trampoline() at fork_trampoline+0x8 > > I don't have WITNESS or INVARIANTS at this time and don;t have a serial console > so I can't capture the output. > > I can try adding these to my kernel and transcribe a little bit by hand. I can > also send my kernel config and dmesg from a Nov kernel which boots. > > Jim Bloom > bloom@acm.org > > John Baldwin wrote: > > > > On 05-Feb-01 Crist J. Clark wrote: > > > I don't recall reports of trouble with recent CURRENT, but my CVSup > > > from yesterday afternoon is panicing. Before I try too debug this, has > > > anyone been getting these or knows what I might be missing? > > > > > > Boot messages and the panic info are attached. > > > > Could you please turn on DDB, WITNESS, and INVARIANTS in your kernel and see if > > you can reproduce this? Also, compile the kernel with debug symbols. Then > > type 'trace' at the db> prompt when it does to get a backtrace of where it blew > > up. Thanks. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Speak softly and carry a cellular phone. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 19:17:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id AD42A37B401 for ; Mon, 5 Feb 2001 19:17:08 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f163HP215400; Tue, 6 Feb 2001 03:17:25 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f163J2610146; Tue, 6 Feb 2001 03:19:02 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102060319.f163J2610146@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: domi@saargate.de Cc: freebsd-current@freebsd.org, Brian Somers Subject: Strange fopen() behaviour (was: xsane patch to maintainer) In-Reply-To: Message from Brian Somers of "Tue, 06 Feb 2001 02:35:12 GMT." <200102060235.f162ZC609373@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_8122223300" Date: Tue, 06 Feb 2001 03:19:01 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_8122223300 Content-Type: text/plain; charset=us-ascii > Hi, > > Would you mind if I commit the attached patch for the xsane port ? > It makes sense - rather than dropping a core when fopen() fails (and > fclose() is called with a NULL arg). It happens when your home > directory isn't writable :-/ I've cc'd -current as I think something more sinister is going on. To recap, I'm having trouble running xsane on -current from about two days ago. fopen() is failing... The attached patch exposes more about what's wrong. Interestingly enough, the file it's trying to create is in /tmp (mode 1777, separate filesystem), and according to truss: lstat("/tmp//preview-level-0-15-b924dc",0xbfbfe894) ERR#2 'No such file or directory' umask(0x7f) = 7 (0x7) /tmp//preview-level-0-15-b924dc17767-microtek:_dev_scanner.ppm: could not create for preview-level 0: No such file or directory write(2,0xbfbfe48c,128) = 128 (0x80) getuid() = 15 (0xf) lstat("/tmp//preview-level-1-15-jNO6zx",0xbfbfe894) ERR#2 'No such file or directory' umask(0x7f) = 127 (0x7f) /tmp//preview-level-1-15-jNO6zx09158-microtek:_dev_scanner.ppm: could not create for preview-level 1: No such file or directory write(2,0xbfbfe48c,128) = 128 (0x80) getuid() = 15 (0xf) lstat("/tmp//preview-level-2-15-CO6k7w",0xbfbfe894) ERR#2 'No such file or directory' umask(0x7f) = 127 (0x7f) break(0x8134000) = 0 (0x0) /tmp//preview-level-2-15-CO6k7w39017-microtek:_dev_scanner.ppm: could not create for preview-level 2: No such file or directory write(2,0xbfbfe48c,128) = 128 (0x80) fopen() is failing after calling lstat() (I assume via _open()) !!! As if the "wb" didn't mean O_CREAT ??!? Very strange. Anyway, here's the patch if you're interested. I'll look into things further on Wednesday. Cheers. -- Brian Don't _EVER_ lose your sense of humour ! --==_Exmh_8122223300 Content-Type: text/plain ; name="patch-ae"; charset=us-ascii Content-Description: patch-ae Content-Disposition: attachment; filename="patch-ae" --- src/xsane-preview.c.orig Sun Jan 14 15:35:06 2001 +++ src/xsane-preview.c Tue Feb 6 03:03:18 2001 @@ -2802,6 +2802,7 @@ int i; char buf[256]; char filename[PATH_MAX]; + FILE *fp; DBG(DBG_proc, "preview_new\n"); @@ -2830,9 +2831,17 @@ if (preview_make_image_path(p, sizeof(filename), filename, i)>=0) { umask(0177); /* create temporary file with "-rw-------" permissions */ - fclose(fopen(filename, "wb")); /* make sure file exists, b = binary mode for win32 */ - umask(XSANE_DEFAULT_UMASK); /* define new file permissions */ - p->filename[i] = strdup(filename);/* store filename */ + fp = fopen(filename, "wb"); /* make sure file exists, b = binary mode for win32 */ + if (fp == NULL) { + fprintf(stderr, "%s: could not create for preview-level %d: %s\n", filename, i, strerror(errno)); + p->filename[i] = NULL; + } + else + { + fclose(fp); + umask(XSANE_DEFAULT_UMASK); /* define new file permissions */ + p->filename[i] = strdup(filename);/* store filename */ + } } else { --==_Exmh_8122223300-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 19:22:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 969BA37B491 for ; Mon, 5 Feb 2001 19:22:05 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f163MM215427; Tue, 6 Feb 2001 03:22:22 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f163O0610286; Tue, 6 Feb 2001 03:24:00 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102060324.f163O0610286@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brian Somers Cc: domi@saargate.de, freebsd-current@freebsd.org Subject: Re: Strange fopen() behaviour In-Reply-To: Message from Brian Somers of "Tue, 06 Feb 2001 03:19:01 GMT." <200102060319.f163J2610146@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Feb 2001 03:23:59 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've cc'd -current as I think something more sinister is going on. > To recap, I'm having trouble running xsane on -current from about two > days ago. fopen() is failing... > > The attached patch exposes more about what's wrong. Interestingly > enough, the file it's trying to create is in /tmp (mode 1777, > separate filesystem), and according to truss: > > lstat("/tmp//preview-level-0-15-b924dc",0xbfbfe894) ERR#2 'No such file or directory' > umask(0x7f) = 7 (0x7) > /tmp//preview-level-0-15-b924dc17767-microtek:_dev_scanner.ppm: could not create for preview-level 0: No such file or directory > write(2,0xbfbfe48c,128) = 128 (0x80) > getuid() = 15 (0xf) > lstat("/tmp//preview-level-1-15-jNO6zx",0xbfbfe894) ERR#2 'No such file or directory' > umask(0x7f) = 127 (0x7f) > /tmp//preview-level-1-15-jNO6zx09158-microtek:_dev_scanner.ppm: could not create for preview-level 1: No such file or directory > write(2,0xbfbfe48c,128) = 128 (0x80) > getuid() = 15 (0xf) > lstat("/tmp//preview-level-2-15-CO6k7w",0xbfbfe894) ERR#2 'No such file or directory' > umask(0x7f) = 127 (0x7f) > break(0x8134000) = 0 (0x0) > /tmp//preview-level-2-15-CO6k7w39017-microtek:_dev_scanner.ppm: could not create for preview-level 2: No such file or directory > write(2,0xbfbfe48c,128) = 128 (0x80) > > fopen() is failing after calling lstat() (I assume via _open()) !!! > As if the "wb" didn't mean O_CREAT ??!? Very strange. [.....] And just to top it all, I see this in my daily report (first time I've ever seen it on this machine...): dev.lan.Awfulhak.org kernel log messages: > microuptime() went backwards (18415.166882 -> 18415.158249) > microuptime() went backwards (18490.192910 -> 18490.187579) > microuptime() went backwards (19572.644000 -> 19572.638237) > microuptime() went backwards (19878.637972 -> 19878.637330) > microuptime() went backwards (20043.869158 -> 20043.868971) > microuptime() went backwards (20074.159108 -> 20074.152253) > microuptime() went backwards (20210.078270 -> 20210.072448) -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 19:30:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 6368337B401 for ; Mon, 5 Feb 2001 19:30:08 -0800 (PST) Received: (qmail 9931 invoked by uid 1000); 6 Feb 2001 03:23:50 -0000 Date: Tue, 6 Feb 2001 04:23:49 +0100 From: Andrea Campi To: Brian Somers Cc: domi@saargate.de, freebsd-current@freebsd.org Subject: Re: Strange fopen() behaviour (was: xsane patch to maintainer) Message-ID: <20010206042348.A9639@webcom.it> References: <200102060319.f163J2610146@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102060319.f163J2610146@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Tue, Feb 06, 2001 at 03:19:01AM +0000 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > lstat("/tmp//preview-level-0-15-b924dc",0xbfbfe894) ERR#2 'No such file or directory' ^^ surely this is not nice!! My guess is that the double slash is confusing everything... Anyway, I'm more interested in below: > @@ -2830,9 +2831,17 @@ > if (preview_make_image_path(p, sizeof(filename), filename, i)>=0) > { > umask(0177); /* create temporary file with "-rw-------" permissions */ > - fclose(fopen(filename, "wb")); /* make sure file exists, b = binary mode for win32 */ > - umask(XSANE_DEFAULT_UMASK); /* define new file permissions */ > - p->filename[i] = strdup(filename);/* store filename */ > + fp = fopen(filename, "wb"); /* make sure file exists, b = binary mode for win32 */ > + if (fp == NULL) { > + fprintf(stderr, "%s: could not create for preview-level %d: %s\n", filename, i, strerror(errno)); > + p->filename[i] = NULL; > + } > + else > + { > + fclose(fp); > + umask(XSANE_DEFAULT_UMASK); /* define new file permissions */ > + p->filename[i] = strdup(filename);/* store filename */ > + } I REALLY hope above code is NEVER EVER run as root, as this is a great recipe for interesting failures... /me hands Brian a few symlinks to /etc/master.passwd from /tmp If you are patching it, make sure you get it right, you'd do everybody a big favor. Bye, Andrea -- It is easier to fix Unix than to live with NT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 20:47:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 8DAEA37B401 for ; Mon, 5 Feb 2001 20:47:29 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp151.geekhouse.net [192.168.1.151]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f164lpc26042; Mon, 5 Feb 2001 20:47:52 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A7F52F7.4D214AD9@acm.org> Date: Mon, 05 Feb 2001 20:46:41 -0800 (PST) From: John Baldwin To: Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org, "Crist J. Clark" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Jim Bloom wrote: > I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is > occuring on my laptop (AST Ascentia 810N) which I can't seem to get to create > a > core dump. Here is a hand transcription of what I see. > > Mounting root from ufs:/dev/ad0s1a > pccard: card inserted, slot 0 > pccard: card inserted, slot 1 > kernel trap 9 with interrupts disabled > > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x8:0xc0270ad8 > stack pointer = 0x10:0xc2fb4f50 > frame pointer = 0x10:0xc2fb4f64 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 16 (irq14:ata0) > kernel: type 9 trap, code=0 > Stopped at sw1b+0x77: ltr %si > > backtrace > sw1b(4000) at sw1b+0x77 (note this is actually swtch()) Actually, this is beyond the end of cpu_switch I think. You are effectively off in lala land. > ithd_loop(0,c2fb4fa8) at ithd_loop+0xf7 This is either in the mtx_enter of Giant or in the interrupt handler itself. I'm betting an interrupt handler isn't being setup properly one way or another, and that the code is jumping through a bogus pointer and ending up in lala land executing random code. > fork_exit(c0275bd0,0,c2fb4fa8_ at fork_exit+0x2d > fork_trampoline() at fork_trampoline+0x8 > > I don't have WITNESS or INVARIANTS at this time and don;t have a serial > console > so I can't capture the output. These help to capture bugs by doing extra checks though, and especially with current they are highly, highly, highly recommended right now. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 20:49:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id 66CD537B401 for ; Mon, 5 Feb 2001 20:49:31 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp151.geekhouse.net [192.168.1.151]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f164lrc26046; Mon, 5 Feb 2001 20:47:54 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010206022354.B613@webcom.it> Date: Mon, 05 Feb 2001 20:46:42 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Andrea Campi wrote: > Sorry to bother everybody, but did anybody note from my panic trace, > that instruction pointer is 0xdeadc0de? Isn't that bad? :-p That means it is free'd memory. One cause might be something that is free'ing its interrupt handler w/o releasing it properly. Alternatively, it might be a race in the interrupt list code that was been brought about by preemption. Since locks are rather expensive, we have avoided locking the list of interrupt handlers in the past, but we may have to break down and do that now. :( This will hurt interrupt latency unless I can figure out a slick way of fixing it. Can anyone confirm that a pre-preemption kernel works fine for them? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 21:36: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id DFD0A37B491 for ; Mon, 5 Feb 2001 21:35:38 -0800 (PST) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id QAA67983 for ; Tue, 6 Feb 2001 16:35:32 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.1.R) for ; Tue, 06 Feb 2001 16:34:41 +1100 Reply-To: From: "Chris Knight" To: Cc: Subject: md, current and stable Date: Tue, 6 Feb 2001 16:34:39 +1100 Message-ID: <004301c08ffe$807f85c0$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, Since the new md was introduced, it is not possible to build a -current snapshot on a -stable box. Are there any plans to MFC this soon? Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 22:36:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id EF88137B491; Mon, 5 Feb 2001 22:36:26 -0800 (PST) Received: from grondar.za (root@gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id f166aJC38816; Tue, 6 Feb 2001 08:36:23 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200102060636.f166aJC38816@gratis.grondar.za> To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup References: In-Reply-To: ; from John Baldwin "Mon, 05 Feb 2001 20:46:42 PST." Date: Tue, 06 Feb 2001 08:36:43 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin said: > On 06-Feb-01 Andrea Campi wrote: > > > Sorry to bother everybody, but did anybody note from my panic trace, > > that instruction pointer is 0xdeadc0de? Isn't that bad? :-p > > That means it is free'd memory. One cause might be something > that is free'ing its interrupt handler w/o releasing it properly. > Alternatively, it might be a race in the interrupt list code that was > been brought about by preemption. Since locks are rather expensive, > we have avoided locking the list of interrupt handlers in the past, > but we may have to break down and do that now. :( This will hurt > interrupt latency unless I can figure out a slick way of fixing it. > Can anyone confirm that a pre-preemption kernel works fine for them? I have 2 SMP boxes (one with pentium 200MMX's, the other with PPro 233's. There are other differences in peripherals). Both boxes run an identical build of a kernel dating to sun 4th feb. The PPro is rock-stable. The PentiumMMX is very fragile, and will panic easily (often in vm_fault) with a sig9 (IIRC). M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Feb 5 22:43:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id 73AFF37B491; Mon, 5 Feb 2001 22:43:41 -0800 (PST) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id PAA29810; Tue, 6 Feb 2001 15:43:38 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id PAA29551; Tue, 6 Feb 2001 15:43:33 +0900 (JST) To: current@FreeBSD.ORG Cc: ticso@cicely5.cicely.de, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: <20010205170041.A86739@panzer.kdm.org> References: <200102040157370.13362-100000@blues.jpj.net> <20010206001527.B548@cicely5.cicely.de> <20010205170041.A86739@panzer.kdm.org> X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010206154333F.non@ever.sanda.gr.jp> Date: Tue, 06 Feb 2001 15:43:33 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Kenneth D. Merry" Date: Mon, 5 Feb 2001 17:00:41 -0700 > I think we already have the most important functionality from the od(4) > driver in the da and cd drivers. If there are any features that are > in the od(4) driver that should be in the da(4) or cd(4) drivers, but > aren't, please speak up. Though I have not tried `da' lately, if you don't insert a medium in the drive at the time of CAM rescan bus, `da' tries to get the geometry by XPT_CALC_GEOMETRY then panics with divided by zero in most SCSI drivers. With `od' it says just the medium is 0MB and does not cause panic. Probably `od' knows the medium is not in the drive (watching UNIT READY or something?). Is it safe to change the size (geometry) of media with `da', eg. at first no medium (0MB), then 128MB, 230MB, 640MB (sector size is 2048bytes) and so on ? // Noriaki Mitsunaga // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 0:22:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 3EC5437B401; Tue, 6 Feb 2001 00:22:20 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 6 Feb 2001 00:17:16 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.1) id f168HvL78251; Tue, 6 Feb 2001 00:17:57 -0800 (PST) (envelope-from cjc) Date: Tue, 6 Feb 2001 00:17:51 -0800 From: "Crist J. Clark" To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010206001751.F91447@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <20010204220704.C91447@rfx-216-196-73-168.users.reflex> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="kORqDWCi7qDJ0mEj" X-Mailer: Mutt 1.0i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Feb 05, 2001 at 02:51:59PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii On Mon, Feb 05, 2001 at 02:51:59PM -0800, John Baldwin wrote: > > On 05-Feb-01 Crist J. Clark wrote: > > I don't recall reports of trouble with recent CURRENT, but my CVSup > > from yesterday afternoon is panicing. Before I try too debug this, has > > anyone been getting these or knows what I might be missing? > > > > Boot messages and the panic info are attached. > > Could you please turn on DDB, WITNESS, and INVARIANTS in your kernel and see if > you can reproduce this? Also, compile the kernel with debug symbols. Then > type 'trace' at the db> prompt when it does to get a backtrace of where it blew > up. Thanks. OK. The boot messages and debug output is attachment one, the kernel config is second. For the record, I have not made any changes to the kernel; fresh CVSup. -- Crist J. Clark cjclark@alum.mit.edu --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="boot.msg" 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 #2: Mon Feb 5 23:59:09 PST 2001 cjc@rfx-216-196-73-168.users.reflexcom.com:/usr/obj/export/current/src/sys/BUBBLES Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping = 11 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30015488 (29312K bytes) Preloaded elf kernel "kernel.BUBBLES" at 0xc02c5000. Intel Pentium detected, installing workaround for F00F bug apm0: on motherboard apm0: found APM BIOS v1.1, connected at v1.1 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 8.0 (no driver attached) ep0: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:20:af:17:a3:e9 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc1: cannot reserve I/O port range sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 1000 packets/entry by default ad0: 1222MB [2484/16/63] at ata0-master BIOSPIO acd0: CDROM at ata0-slave using BIOSPIO Mounting root from ufs:/dev/ad0s1a kernel trap 9 with interrupts disabled panic: mutex sched lock recursed at /export/current/src/sys/kern/kern_synch.c:918 Debugger("panic") Stopped at Debugger+0x44: pushl %ebx db> trace Debugger(c0215a83) at Debugger+0x44 panic(c02148a2,c022fc69,c02160a0,396,c0823f00) at panic+0x70 _mtx_assert(c0278140,9,c02160a0,396,c0823f00) at _mtx_assert+0x63 mi_switch(c3611b80,20,9,c3a29f08,c01f2a6d) at mi_switch+0x25 sched_ithd(e) at sched_ithd+0xd9 Xresume14() at Xresume14+0x8 --- interrupt, eip = 0x8, esp = 0xc3a29ee4, ebp = 0xc3a29ed4 --- (null)(c01fcd58,8,80286,c02781a0,20) at 0x8 db> --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=BUBBLES # $Id: BUBBLES,v 1.4 2001/02/04 06:49:24 cjc Exp cjc $ # # BUBBLES - 2000/11/11, cjc # # Kernel configuration for IBM Pentium 133 # # 2000/12/09, cjc - DEVEL became BUBBLES # machine i386 cpu I586_CPU ident BUBBLES maxusers 32 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options WITNESS options INVARIANTS options DDB options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem #options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options DEVFS #Device Filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING #options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci #options COMPAT_OLDISA # compatability shims for lnc, le #options COMPAT_OLDPCI # compatability shims for lnc # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # atkbdc0 controls both the keyboard and the PS/2 mouse #device atkbdc 1 # At keyboard controller #device atkbd # at keyboard #device psm # psm mouse #device vga # VGA screen # splash screen/screen saver #device splash # syscons is the default console driver, resembling an SCO console #device sc 1 # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) device apm # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # ISA Ethernet NICs. pccard nics included. device ep # Etherlink III based cards # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device #options NOBLOCKRANDOM # avoid any blocking on device random device loop # Network loopback device ether # Ethernet support #device sl # Kernel SLIP #device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) #device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # Needed for ipfwlogd development options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about #options IPFIREWALL_EXTRA_VERBOSE #print TCP flag information options IPFIREWALL_VERBOSE_LIMIT=1000 #limit verbosity options IPDIVERT #divert sockets #End --kORqDWCi7qDJ0mEj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 1:39:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id AD4DB37B503; Tue, 6 Feb 2001 01:39:10 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14Q4aX-0004Pn-00; Tue, 06 Feb 2001 11:39:05 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id LAA19714; Tue, 6 Feb 2001 11:39:03 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 19548; Tue Feb 6 11:38:24 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 14Q4Zr-000K2A-00; Tue, 06 Feb 2001 11:38:23 +0200 To: chris@aims.com.au Cc: phk@freebsd.org, current@freebsd.org Subject: Re: md, current and stable In-reply-to: Your message of "Tue, 06 Feb 2001 16:34:39 +1100." <004301c08ffe$807f85c0$020aa8c0@aims.private> Date: Tue, 06 Feb 2001 11:38:23 +0200 Message-ID: <77013.981452303@axl.fw.uunet.co.za> From: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 06 Feb 2001 16:34:39 +1100, "Chris Knight" wrote: > Since the new md was introduced, it is not possible to build a -current > snapshot on a -stable box. Are there any plans to MFC this soon? Woah, what's the problem? This sounds like something that should be fixed, not covered up with an MFC. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 1:47: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 1A27337B401 for ; Tue, 6 Feb 2001 01:46:42 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f169jSu33275; Tue, 6 Feb 2001 10:45:28 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Tue, 6 Feb 2001 10:52:36 +0100 (CET) From: Martin Blapp To: Francis.Dupont@enst-bretagne.fr, souissi@nic.fr, snap-users@kame.net, Francois.Tigeot@nic.fr Cc: feico@pasta.cs.uit.no, dillon@earth.backplane.com, freebsd-current@FreeBSD.ORG Subject: Re: (KAME-snap 3974) Re: TI-RPC, IPv6 and NFS (was: Re: strongrecommendation re: NFS) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I already wrote in a prior statement, Alfred Perlstein and I ported TI_RPC to FreeBSD. It compiles with recent CURRENT. http://www.attic.ch/patches/rpc.diff_01152001-2.sh.tgz All you have to do is to start rpc.diff_01152001-2.sh in the source tree and make a buildworld and then run mergemaster (installing etc/defaults/rc.conf and etc/netconfig) Then the system is ready. Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 2:24:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id 4AF0337B4EC for ; Tue, 6 Feb 2001 02:24:30 -0800 (PST) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id VAA68383 for ; Tue, 6 Feb 2001 21:24:27 +1100 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.1.R) for ; Tue, 06 Feb 2001 21:24:01 +1100 Reply-To: From: "Chris Knight" To: Cc: , Subject: RE: md, current and stable Date: Tue, 6 Feb 2001 21:23:59 +1100 Message-ID: <004a01c09026$ec0261f0$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <77013.981452303@axl.fw.uunet.co.za> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, > -----Original Message----- > From: Sheldon Hearn [mailto:sheldonh@uunet.co.za] > Sent: Tuesday, 6 February 2001 20:38 > To: chris@aims.com.au > Cc: phk@freebsd.org; current@freebsd.org > Subject: Re: md, current and stable > > > On Tue, 06 Feb 2001 16:34:39 +1100, "Chris Knight" wrote: > > > Since the new md was introduced, it is not possible to > build a -current > > snapshot on a -stable box. Are there any plans to MFC this soon? > > Woah, what's the problem? This sounds like something that should be > fixed, not covered up with an MFC. > When -current's release scripts were cut over to use mdconfig due to PHK's death warrant notice of vn, vnconfig and MFS, release builds stopped working on -stable due to -stable's md driver not having a handler for /dev/mdctl. As vn + friends are disappearing, it makes sense for md to be MFCed, thus fixing the problem. > Ciao, > Sheldon. > > Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 2:26:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4BC4537B491 for ; Tue, 6 Feb 2001 02:26:06 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f16APwB33054; Tue, 6 Feb 2001 11:25:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: chris@aims.com.au Cc: sheldonh@uunet.co.za, current@freebsd.org Subject: Re: md, current and stable In-Reply-To: Your message of "Tue, 06 Feb 2001 21:23:59 +1100." <004a01c09026$ec0261f0$020aa8c0@aims.private> Date: Tue, 06 Feb 2001 11:25:58 +0100 Message-ID: <33052.981455158@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <004a01c09026$ec0261f0$020aa8c0@aims.private>, "Chris Knight" writes: >Howdy, > >> -----Original Message----- >> From: Sheldon Hearn [mailto:sheldonh@uunet.co.za] >> Sent: Tuesday, 6 February 2001 20:38 >> To: chris@aims.com.au >> Cc: phk@freebsd.org; current@freebsd.org >> Subject: Re: md, current and stable >> >> >> On Tue, 06 Feb 2001 16:34:39 +1100, "Chris Knight" wrote: >> >> > Since the new md was introduced, it is not possible to >> build a -current >> > snapshot on a -stable box. Are there any plans to MFC this soon? >> >> Woah, what's the problem? This sounds like something that should be >> fixed, not covered up with an MFC. >> >When -current's release scripts were cut over to use mdconfig due to PHK's >death warrant notice of vn, vnconfig and MFS, release builds stopped working >on -stable due to -stable's md driver not having a handler for /dev/mdctl. >As vn + friends are disappearing, it makes sense for md to be MFCed, thus >fixing the problem. Somebody with a stable machine: try it and send patches. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 3:56:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id E0FB037B401 for ; Tue, 6 Feb 2001 03:56:34 -0800 (PST) Received: (qmail 2198 invoked by uid 1000); 6 Feb 2001 11:50:17 -0000 Date: Tue, 6 Feb 2001 12:50:17 +0100 From: Andrea Campi To: John Baldwin Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010206125016.A1752@webcom.it> References: <20010206022354.B613@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Feb 05, 2001 at 08:46:42PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 05, 2001 at 08:46:42PM -0800, John Baldwin wrote: > > On 06-Feb-01 Andrea Campi wrote: > > Sorry to bother everybody, but did anybody note from my panic trace, > > that instruction pointer is 0xdeadc0de? Isn't that bad? :-p > > That means it is free'd memory. One cause might be something that is free'ing > its interrupt handler w/o releasing it properly. Alternatively, it might be a Ok, can't help with the rest of your answer, but I'd like to help debug if the issue is here. Problem: I can't do anything at db> prompt? Backtrace is doing nothing except triggering a new register dump (another fault I assume). Anyway, I'm using: device card device pcic device ep I started looking around in src/sys/dev/{ep,pccard,pcic}/* for recent changes that could have caused it, but I soon got lost... :( What should I try? I can go back to an earlier kernel (via cvs & compile, sadly I don't have any old working kernel anymore), but I'd have to first understand how far back I can go without getting out of sync between kernel & world... Meanwhile, I'll try the latest kernel, and also cardbus to see if the results are different in any way... Bye, Andrea -- Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 4:30:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 802A037B503; Tue, 6 Feb 2001 04:30:24 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f16CUDS14805 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 6 Feb 2001 13:30:15 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f16CUZr70078 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Tue, 6 Feb 2001 13:30:38 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f16CUVT23161; Tue, 6 Feb 2001 13:30:31 +0100 (CET) (envelope-from ticso) Date: Tue, 6 Feb 2001 13:30:30 +0100 From: Bernd Walter To: non@ever.sanda.gr.jp Cc: current@FreeBSD.ORG, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT Message-ID: <20010206133030.A2232@cicely5.cicely.de> References: <200102040157370.13362-100000@blues.jpj.net> <20010206001527.B548@cicely5.cicely.de> <20010205170041.A86739@panzer.kdm.org> <20010206154333F.non@ever.sanda.gr.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010206154333F.non@ever.sanda.gr.jp>; from non@ever.sanda.gr.jp on Tue, Feb 06, 2001 at 03:43:33PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 06, 2001 at 03:43:33PM +0900, non@ever.sanda.gr.jp wrote: > From: "Kenneth D. Merry" > Date: Mon, 5 Feb 2001 17:00:41 -0700 > > I think we already have the most important functionality from the od(4) > > driver in the da and cd drivers. If there are any features that are > > in the od(4) driver that should be in the da(4) or cd(4) drivers, but > > aren't, please speak up. > > Though I have not tried `da' lately, if you don't insert a medium in > the drive at the time of CAM rescan bus, `da' tries to get the > geometry by XPT_CALC_GEOMETRY then panics with divided by zero in most > SCSI drivers. With `od' it says just the medium is 0MB and does not > cause panic. Probably `od' knows the medium is not in the drive > (watching UNIT READY or something?). Sounds very much like a bug which should be fixed than worked around. Especialy when even the workaround doesn't run! I was running a HP mo which claimed to be an optical drive. It did run very fine under every condition. Now the drive is configured to inquiry as direct access because I used it on a solaris box for some days. Now all my removeable drives claim all to be direct access. I asume your drive firmware doesn't send a propper 'NOT READY'. But that shouldn't panic the system. > Is it safe to change the size (geometry) of media with `da', eg. at > first no medium (0MB), then 128MB, 230MB, 640MB (sector size is > 2048bytes) and so on ? Can you provide us with the exact message and a stack trace from the system? And don't forget the exact drive inquiry string and version. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 5:41:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 11A2337B491; Tue, 6 Feb 2001 05:41:09 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 883A831FB; Tue, 6 Feb 2001 13:41:07 +0000 (GMT) Date: Tue, 6 Feb 2001 13:41:07 +0000 From: Josef Karthauser To: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010206134107.E820@tao.org.uk> Mail-Followup-To: Josef Karthauser , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cYtjc4pxslFTELvY" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --cYtjc4pxslFTELvY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I'm wondering what's changed recently to cause vmware2 running on the linuxemu to lose a lot of performance with disk I/O. A couple of weeks ago I could boot win2000 under vmware2 in a matter of minutes; on today's kernel it takes 5 or 10 minutes to boot, and disk I/O is through the roof. Could someone please hit me with a clue-bat :) Joe --cYtjc4pxslFTELvY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjp//vMACgkQXVIcjOaxUBZa1QCg4Mk6A34Rh5Lv9RnBL9bVePye JCUAoJPwdOpMeW5XKZt+SNdbKXQG9BZc =10sY -----END PGP SIGNATURE----- --cYtjc4pxslFTELvY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 6:13:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 1CAD037B69F for ; Tue, 6 Feb 2001 06:13:04 -0800 (PST) Received: (qmail 5394 invoked by uid 1000); 6 Feb 2001 14:06:46 -0000 Date: Tue, 6 Feb 2001 15:06:45 +0100 From: Andrea Campi To: John Baldwin Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010206150643.A462@webcom.it> References: <20010206022354.B613@webcom.it> <20010206125016.A1752@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010206125016.A1752@webcom.it>; from andrea@webcom.it on Tue, Feb 06, 2001 at 12:50:17PM +0100 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Problem: I can't do anything at db> prompt? Backtrace is doing nothing except > triggering a new register dump (another fault I assume). New kernel, new panic, new info: db> witness_list "Giant" (0xc0279be0) locked at ../../i386/isa/ithread.c:191 db> show registers cs 0x8 ds 0x10 es 0x10 fs 0x18 ss 0x10 eax 0xdeadc0de ecx 0xc59eb4b4 edx 0xc0279be0 Giant ebx 0xc0a7a480 _end+0x36f8 esp 0xc65faf68 ebp 0xc65faf78 esi 0xc0a7a4e0 _end+0x3758 edi 0xc01fc998 ithd_loop eax 0xdeadc0de efl 0x10282 Besides the obvious need to fix this one problem, shouldn't we ASSERT ih->ih_handler != NULL before calling it? Bye, Andrea -- Reboot America. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 6:21:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id 0419A37B491; Tue, 6 Feb 2001 06:21:15 -0800 (PST) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id XAA43300; Tue, 6 Feb 2001 23:21:13 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id XAA14472; Tue, 6 Feb 2001 23:21:12 +0900 (JST) To: current@FreeBSD.ORG Cc: trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: <20010206133030.A2232@cicely5.cicely.de> References: <20010205170041.A86739@panzer.kdm.org> <20010206154333F.non@ever.sanda.gr.jp> <20010206133030.A2232@cicely5.cicely.de> X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010206232112W.non@ever.sanda.gr.jp> Date: Tue, 06 Feb 2001 23:21:12 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 50 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bernd Walter Date: Tue, 6 Feb 2001 13:30:30 +0100 > > Though I have not tried `da' lately, if you don't insert a medium in > > the drive at the time of CAM rescan bus, `da' tries to get the > > geometry by XPT_CALC_GEOMETRY then panics with divided by zero in most > > SCSI drivers. With `od' it says just the medium is 0MB and does not > > cause panic. Probably `od' knows the medium is not in the drive > > (watching UNIT READY or something?). > > Sounds very much like a bug which should be fixed than worked around. > Especialy when even the workaround doesn't run! I should have written that I didn't dare to do above in 4-stable and 5-current with `da' driver. I tried with 3.x without `od'. Today I tried with 4.2-RELEASE (sorry not -current) and, 1. Boot up the 4.2-RELEASE with GENERIC kernel. 2. Connect MO drive with PC Card SCSI(ncv). 3. Insert PC Card without medium in the MO drive. 4. The pccardd automatically run camcontrol rescan. 5. Message says that da0 is 0MB capacity. 6. Run fdisk da0 7. got panic with divided by zero. Probably divided by zero is caused at line 737 or 748 in the scsi_low_action() in cam/scsi/scsi_low.c because of ccg->block_size or secs_per_cylinder is zero. If I insert a 128MB medium in the drive at 3, no panic occurs. > I asume your drive firmware doesn't send a propper 'NOT READY'. I don't think so. I tried two drives and many people claimed that `da' caused the same problem with MOs and Zips in Japanese mailing lists at the era of 3.x . That's the one reason many people in Japan eager to `od'. > > Is it safe to change the size (geometry) of media with `da', eg. at > > first no medium (0MB), then 128MB, 230MB, 640MB (sector size is > > 2048bytes) and so on ? I didn't dare to do this medium change with `da'. Because I thought `da' did not read the geometry when I changed media. > Can you provide us with the exact message and a stack trace from the > system? > And don't forget the exact drive inquiry string and version. I will try with -current later (may be in one week). // Noriaki Mitsuanga // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 7:41:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E6C2137B401; Tue, 6 Feb 2001 07:41:06 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id CAA26756; Wed, 7 Feb 2001 02:40:47 +1100 Date: Wed, 7 Feb 2001 02:40:27 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Josef Karthauser Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: <20010206134107.E820@tao.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Feb 2001, Josef Karthauser wrote: > I'm wondering what's changed recently to cause vmware2 running on > the linuxemu to lose a lot of performance with disk I/O. Use of cmpxchg and possibly other SMP pessimizations. > A couple of weeks ago I could boot win2000 under vmware2 in a matter > of minutes; on today's kernel it takes 5 or 10 minutes to boot, > and disk I/O is through the roof. > > Could someone please hit me with a clue-bat :) Read your freebsd-emulation mail :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 7:46:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id D996937B401; Tue, 6 Feb 2001 07:46:20 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 956C2311E; Tue, 6 Feb 2001 15:46:19 +0000 (GMT) Date: Tue, 6 Feb 2001 15:46:19 +0000 From: Josef Karthauser To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010206154619.G820@tao.org.uk> Mail-Followup-To: Josef Karthauser , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <20010206134107.E820@tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="f5QefDQHtn8hx44O" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Wed, Feb 07, 2001 at 02:40:27AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --f5QefDQHtn8hx44O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 07, 2001 at 02:40:27AM +1100, Bruce Evans wrote: > > Could someone please hit me with a clue-bat :) >=20 > Read your freebsd-emulation mail :-). /me wanders off to subscribe to freebsd-emulation. Thanks Bruce. Joe --f5QefDQHtn8hx44O Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqAHEsACgkQXVIcjOaxUBYqIwCgmL2d2E8Qp41zsQb22WnuJvdy PVYAn2mLiu4ZlxbSi+vAuvXnig+iTlzQ =QLFF -----END PGP SIGNATURE----- --f5QefDQHtn8hx44O-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 8: 3:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.jbloom.org (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id A1E6F37B401; Tue, 6 Feb 2001 08:02:58 -0800 (PST) Received: from acm.org (localhost [127.0.0.1]) by jbloom.jbloom.org (8.11.2/8.11.2) with ESMTP id f16G2u025104; Tue, 6 Feb 2001 11:02:57 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <3A80202F.6DAA1328@acm.org> Date: Tue, 06 Feb 2001 11:02:55 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The line where I was having the trap is still within cpu_switch (line 236 of swtch.s). I added WITNESS and INVARIANTS to my kernel and I get a new panic. This time I see: kernel trap 12 with interrupts disabled panic: mutex sched lock recursed at ../../kern/kern_synch.c:918 panic() _mtx_assert(c031b6c0,9,c0290990,396,c043b100) at _mtx_assert+0x63 mi_switch(c031b6c0,0,c,c24bef08,c02681cd) at mi_switch+0x25 sched_ithd(e) at sched_ithd+0xd9 Xresume14() at Xresume14+0x8 --- interrupt, eip = 0xc02b0008, esp - 0xc2fbeee4, epb = 0xc2feed4 --- __set_sysinit_set_sym_sc_mem_sys_init(c0275020,c02b0008,286,c031b7230,0) at __set_sysinit_set_sym_sc_mem_sys_init+0x644 Jim Bloom bloom@acm.org PS: Here is the original message. It was cut and pasted from the logs since your message is sitting in another OS on a dual boot machine. On 06-Feb-01 Jim Bloom wrote: > I have seen both a trap 12 and a trap 9 from a Friday Feb. 2 kernel. This is > occuring on my laptop (AST Ascentia 810N) which I can't seem to get to create > a > core dump. Here is a hand transcription of what I see. > > Mounting root from ufs:/dev/ad0s1a > pccard: card inserted, slot 0 > pccard: card inserted, slot 1 > kernel trap 9 with interrupts disabled > > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x8:0xc0270ad8 > stack pointer = 0x10:0xc2fb4f50 > frame pointer = 0x10:0xc2fb4f64 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 16 (irq14:ata0) > kernel: type 9 trap, code=0 > Stopped at sw1b+0x77: ltr %si > > backtrace > sw1b(4000) at sw1b+0x77 (note this is actually swtch()) Actually, this is beyond the end of cpu_switch I think. You are effectively off in lala land. > ithd_loop(0,c2fb4fa8) at ithd_loop+0xf7 This is either in the mtx_enter of Giant or in the interrupt handler itself. I'm betting an interrupt handler isn't being setup properly one way or another, and that the code is jumping through a bogus pointer and ending up in lala land executing random code. > fork_exit(c0275bd0,0,c2fb4fa8_ at fork_exit+0x2d > fork_trampoline() at fork_trampoline+0x8 > > I don't have WITNESS or INVARIANTS at this time and don;t have a serial > console > so I can't capture the output. These help to capture bugs by doing extra checks though, and especially with current they are highly, highly, highly recommended right now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 8:27:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id F0E0C37B491 for ; Tue, 6 Feb 2001 08:27:26 -0800 (PST) Received: (qmail 27752 invoked by uid 666); 6 Feb 2001 16:35:03 -0000 Received: from reggae-14-23.nv.iinet.net.au (HELO elischer.org) (203.59.77.23) by mail.m.iinet.net.au with SMTP; 6 Feb 2001 16:35:03 -0000 Message-ID: <3A8017B6.B278F3CE@elischer.org> Date: Tue, 06 Feb 2001 07:26:46 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Josef Karthauser Cc: freebsd-current@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: <20010206134107.E820@tao.org.uk> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > > Hi, > > I'm wondering what's changed recently to cause vmware2 running on > the linuxemu to lose a lot of performance with disk I/O. > > A couple of weeks ago I could boot win2000 under vmware2 in a matter > of minutes; on today's kernel it takes 5 or 10 minutes to boot, > and disk I/O is through the roof. > > Could someone please hit me with a clue-bat :) > > Joe > > -------------------------------------------------------------------------------- > Part 1.2Type: application/pgp-signature I noticed this too. It's about 3 x slower for me. Even the startup sequence when we haven't even loaded the bootblocks is MUCH slower.. I'm using vmware 1.0.x and running FreeBSD on it for kernel debugging. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 8:50: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 77D8C37B401 for ; Tue, 6 Feb 2001 08:49:47 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.2/8.11.2) id f16GqFC07634 for freebsd-current@freebsd.org; Tue, 6 Feb 2001 08:52:15 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200102061652.f16GqFC07634@troutmask.apl.washington.edu> Subject: Close PR misc/24122 and misc/15471 To: FreeBSD Current Date: Tue, 6 Feb 2001 08:52:15 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone close PR misc/{24122,15471}? PR misc/24122 is no longer relevent. I doubt anyone will every apply the patches in PR misc/15471 to older versions of FreeBSD. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 8:56:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 4712737B401 for ; Tue, 6 Feb 2001 08:55:54 -0800 (PST) Received: (qmail 29523 invoked by uid 666); 6 Feb 2001 17:03:31 -0000 Received: from reggae-14-23.nv.iinet.net.au (HELO elischer.org) (203.59.77.23) by mail.m.iinet.net.au with SMTP; 6 Feb 2001 17:03:31 -0000 Message-ID: <3A801E63.52D2B524@elischer.org> Date: Tue, 06 Feb 2001 07:55:15 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Bruce Evans Cc: Josef Karthauser , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > On Tue, 6 Feb 2001, Josef Karthauser wrote: > > > I'm wondering what's changed recently to cause vmware2 running on > > the linuxemu to lose a lot of performance with disk I/O. > > Use of cmpxchg and possibly other SMP pessimizations. > > > A couple of weeks ago I could boot win2000 under vmware2 in a matter > > of minutes; on today's kernel it takes 5 or 10 minutes to boot, > > and disk I/O is through the roof. > > > > Could someone please hit me with a clue-bat :) > > Read your freebsd-emulation mail :-). You are wrong Bruce, the cmpxchg discussion was regarding why running FreeBSD as a GUEST OS was slow, because the virtual machine was very slow at emulating them. That does not explain why Windows2000 and the Boot loader both slowed down by a factor or 3->6 over teh last 2 weeks. It's even slower to start up, before it has even started any emulation.. This feels like the system is massively slowing down page activations or some other sort of exceptions that are standard for vmware. The same vmware with the same guest OS (not been updated) is now much slower. > > Bruce > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 9:21:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 23B0037B503 for ; Tue, 6 Feb 2001 09:20:59 -0800 (PST) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 1LYSFYM6; Tue, 6 Feb 2001 12:21:00 -0500 Reply-To: Randell Jesup To: current@FreeBSD.ORG Subject: Re: Please review sh SIGSTOP fix From: Randell Jesup Date: 06 Feb 2001 12:25:28 -0500 In-Reply-To: Martin Cracauer's message of "Fri, 2 Feb 2001 11:50:41 +0100" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer writes: >would you please have a look at the following sh fix? My brain is a >bit rusty and maybe I overlook a drawback. > >When a child is receiving SIGSTOP, eval continues with the next >command. While that is correct for the interactive case (Control-Z >and you get the prompt back), it is wrong for a shellscript, which >just continues with the next command, never again waiting for the >stopped child. Noted when childs from cronjobs were stopped, just to >make more processes (by wosch). Careful - is this behavior used as a feature during boot when starting services? I.e. you can ^Z and it will continue with the next service; effectively backgrounding the service that's waiting. I.e. is this a feature (perhaps accidental) that people assume and rely on? And if so, is there another way to get the functionality, and is it important to people? Perhaps I'm totally wrong here and misunderstood the issue. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 11: 3: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id B2CD137B401 for ; Tue, 6 Feb 2001 11:02:48 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f16J1V325315; Tue, 6 Feb 2001 11:01:31 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010206001751.F91447@rfx-216-196-73-168.users.reflex> Date: Tue, 06 Feb 2001 11:02:32 -0800 (PST) From: John Baldwin To: "Crist J. Clark" Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Crist J. Clark wrote: > On Mon, Feb 05, 2001 at 02:51:59PM -0800, John Baldwin wrote: >> >> On 05-Feb-01 Crist J. Clark wrote: >> > I don't recall reports of trouble with recent CURRENT, but my CVSup >> > from yesterday afternoon is panicing. Before I try too debug this, has >> > anyone been getting these or knows what I might be missing? >> > >> > Boot messages and the panic info are attached. >> >> Could you please turn on DDB, WITNESS, and INVARIANTS in your kernel and see >> if >> you can reproduce this? Also, compile the kernel with debug symbols. Then >> type 'trace' at the db> prompt when it does to get a backtrace of where it >> blew >> up. Thanks. > > OK. The boot messages and debug output is attachment one, the kernel > config is second. For the record, I have not made any changes to the > kernel; fresh CVSup. ARGH. The trap code is breaking this. We are getting a trap with interrupts disabled because we have hit a bug while holding a spin mutex. The handy-dandy trap code then enables interrupts for us which allows an interrupt to come in and blow up recursing on sched_lock and obscuring the previous trap. That, and it looks like ddb can't follow back through an interrupt trace properly. Can you edit src/sys/i386/i386/trap.c and comment out the 'enable_intr()' with the nasty comment above it about spin mutexes in trap(): /* * We should walk p_heldmtx here and see if any are * spin mutexes, and not do this if so. */ enable_intr(); } Just comment out that enable_intr() and please try again. This should give you a stack trace where the actual bug is. Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 11: 4:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7752A37B65D for ; Tue, 6 Feb 2001 11:04:04 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f16J1W325323; Tue, 6 Feb 2001 11:01:32 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A80202F.6DAA1328@acm.org> Date: Tue, 06 Feb 2001 11:02:34 -0800 (PST) From: John Baldwin To: Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Jim Bloom wrote: > The line where I was having the trap is still within cpu_switch (line > 236 of swtch.s). > > I added WITNESS and INVARIANTS to my kernel and I get a new panic. > This time I see: > > kernel trap 12 with interrupts disabled > panic: mutex sched lock recursed at ../../kern/kern_synch.c:918 > > panic() > _mtx_assert(c031b6c0,9,c0290990,396,c043b100) at _mtx_assert+0x63 > mi_switch(c031b6c0,0,c,c24bef08,c02681cd) at mi_switch+0x25 > sched_ithd(e) at sched_ithd+0xd9 > Xresume14() at Xresume14+0x8 > --- interrupt, eip = 0xc02b0008, esp - 0xc2fbeee4, epb = 0xc2feed4 --- > __set_sysinit_set_sym_sc_mem_sys_init(c0275020,c02b0008,286,c031b7230,0) > at __set_sysinit_set_sym_sc_mem_sys_init+0x644 > > Jim Bloom > bloom@acm.org Hmmmmm, can you show the registers? I wonder if we are somehow running a process that isn't fully created yet. Hmm, that shouldn't be a problem looking at fork1().. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 11: 6:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 8A3C637B401 for ; Tue, 6 Feb 2001 11:06:22 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f16J1W325319; Tue, 6 Feb 2001 11:01:32 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010206150643.A462@webcom.it> Date: Tue, 06 Feb 2001 11:02:33 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Andrea Campi wrote: >> Problem: I can't do anything at db> prompt? Backtrace is doing nothing >> except >> triggering a new register dump (another fault I assume). > > New kernel, new panic, new info: > > db> witness_list > "Giant" (0xc0279be0) locked at ../../i386/isa/ithread.c:191 > db> show registers > cs 0x8 > ds 0x10 > es 0x10 > fs 0x18 > ss 0x10 > eax 0xdeadc0de > ecx 0xc59eb4b4 > edx 0xc0279be0 Giant > ebx 0xc0a7a480 _end+0x36f8 > esp 0xc65faf68 > ebp 0xc65faf78 > esi 0xc0a7a4e0 _end+0x3758 > edi 0xc01fc998 ithd_loop > eax 0xdeadc0de > efl 0x10282 > > Besides the obvious need to fix this one problem, shouldn't we > ASSERT ih->ih_handler != NULL before calling it? It isn't null in this case, it is 0xdeadc0de. Can you try a pre-preemption kernel and see if that fixes it? > Bye, > Andrea -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 11:31:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D188737B401; Tue, 6 Feb 2001 11:31:04 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f16JSl344507; Tue, 6 Feb 2001 11:28:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <77013.981452303@axl.fw.uunet.co.za> Date: Tue, 06 Feb 2001 11:29:48 -0800 (PST) From: John Baldwin To: Sheldon Hearn Subject: Re: md, current and stable Cc: current@FreeBSD.org, phk@FreeBSD.org, chris@aims.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Sheldon Hearn wrote: > > > On Tue, 06 Feb 2001 16:34:39 +1100, "Chris Knight" wrote: > >> Since the new md was introduced, it is not possible to build a -current >> snapshot on a -stable box. Are there any plans to MFC this soon? > > Woah, what's the problem? This sounds like something that should be > fixed, not covered up with an MFC. Erm, building releases of different branches than the build box isn't really supported. If you want a -current release, build it on a -current box. If you want a -stable release, build it on a -stable box. It may work at times that you can build -stable on -current and vice versa, but that is not supported and one does so at their own risk. Releases are bad enough as is w/o having to add in a multitude of hacks so that one can roll a 5.0 release on a 2.2.x box, etc. > Ciao, > Sheldon. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 11:38:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 7665137B401 for ; Tue, 6 Feb 2001 11:38:02 -0800 (PST) Received: (from cracauer@localhost) by knight.cons.org (8.11.1/8.11.1) id f16Jbrb09265; Tue, 6 Feb 2001 20:37:53 +0100 (CET) Date: Tue, 6 Feb 2001 20:37:52 +0100 From: Martin Cracauer To: Randell Jesup Cc: current@FreeBSD.ORG Subject: Re: Please review sh SIGSTOP fix Message-ID: <20010206203752.A9211@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rjesup@wgate.com on Tue, Feb 06, 2001 at 12:25:28PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Randell Jesup wrote: > Martin Cracauer writes: > >would you please have a look at the following sh fix? My brain is a > >bit rusty and maybe I overlook a drawback. > > > >When a child is receiving SIGSTOP, eval continues with the next > >command. While that is correct for the interactive case (Control-Z > >and you get the prompt back), it is wrong for a shellscript, which > >just continues with the next command, never again waiting for the > >stopped child. Noted when childs from cronjobs were stopped, just to > >make more processes (by wosch). > > Careful - is this behavior used as a feature during boot when > starting services? I.e. you can ^Z and it will continue with the next > service; effectively backgrounding the service that's waiting. I.e. is > this a feature (perhaps accidental) that people assume and rely on? I hope not, thats definitivly a bug. Do you intent to continue the stopped proccess anytime? I don't think that are many cases where they were hung so that backgrounding them is needed but where they are not completely hung. > And > if so, is there another way to get the functionality, and is it important > to people? Control-C kills the currently starting process and Control-\ makes the whole /etc/rc return to singleuser-mode. That are the only documented ways to interact with /etc/rc. If you really want to background one process from /etc/rc, you would still do that by writing a wrapped that catches SIGINT and send SIGSTOP to its child (which is the original thing to start). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ As far as I'm concerned, if something is so complicated that you can't ex- plain it in 10 seconds, then it's probably not worth knowing anyway -Calvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 11:40:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 3874237B491 for ; Tue, 6 Feb 2001 11:40:34 -0800 (PST) Received: (from cracauer@localhost) by knight.cons.org (8.11.1/8.11.1) id f16JeVB09306; Tue, 6 Feb 2001 20:40:31 +0100 (CET) Date: Tue, 6 Feb 2001 20:40:31 +0100 From: Martin Cracauer To: Randell Jesup Cc: current@FreeBSD.ORG Subject: Re: Please review sh SIGSTOP fix Message-ID: <20010206204031.C9211@cons.org> References: <20010206203752.A9211@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010206203752.A9211@cons.org>; from cracauer@cons.org on Tue, Feb 06, 2001 at 08:37:52PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20010206203752.A9211@cons.org>, Martin Cracauer wrote: > If you really want to background one process from /etc/rc, you would > still do that by writing a wrapped that catches SIGINT and send ^^^^^^^ ^ wrapper shellscript s > SIGSTOP to its child (which is the original thing to start). Sorry Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ As far as I'm concerned, if something is so complicated that you can't ex- plain it in 10 seconds, then it's probably not worth knowing anyway -Calvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 12:32:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C85EF37B491; Tue, 6 Feb 2001 12:31:52 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f16KTH986019; Tue, 6 Feb 2001 13:29:17 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102062029.f16KTH986019@harmony.village.org> To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: John Baldwin , current@FreeBSD.ORG, "Crist J. Clark" , Jim Bloom In-reply-to: Your message of "Tue, 06 Feb 2001 12:50:17 +0100." <20010206125016.A1752@webcom.it> References: <20010206125016.A1752@webcom.it> <20010206022354.B613@webcom.it> Date: Tue, 06 Feb 2001 13:29:17 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010206125016.A1752@webcom.it> Andrea Campi writes: : Problem: I can't do anything at db> prompt? Backtrace is doing nothing except : triggering a new register dump (another fault I assume). I'm having all kinds of issues with -current and pccards. OLDCARD hangs solid when I remove a card. Newcard randomly does weird things. If you want stability, I'd strongly advise running -stable for the next few months on your laptop. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 12:36:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.jbloom.org (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id A85C337B4EC; Tue, 6 Feb 2001 12:36:11 -0800 (PST) Received: from acm.org (localhost [127.0.0.1]) by jbloom.jbloom.org (8.11.2/8.11.2) with ESMTP id f16Ka6030030; Tue, 6 Feb 2001 15:36:07 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <3A806036.5694FD66@acm.org> Date: Tue, 06 Feb 2001 15:36:06 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here are the registers (subject to typing errors): cs 0xc2fb0008 ds 0xa000010 es 0x10 fs 0x18 ss 0x10 eax 0x12 ecx 0x20 edx 0xc00b8f00 ebx 0x2 esp 0xc2fbee1c ebp 0xc2fbee28 esi 0x100 edi 0xc0290990 __set_sysctl_set_sym_sysctl__kern_fscale+0x4 eip 0xc0266fcc Debugger+44 efl 0x56 Jim Bloom bloom@acm.org John Baldwin wrote: > > On 06-Feb-01 Jim Bloom wrote: > > The line where I was having the trap is still within cpu_switch (line > > 236 of swtch.s). > > > > I added WITNESS and INVARIANTS to my kernel and I get a new panic. > > This time I see: > > > > kernel trap 12 with interrupts disabled > > panic: mutex sched lock recursed at ../../kern/kern_synch.c:918 > > > > panic() > > _mtx_assert(c031b6c0,9,c0290990,396,c043b100) at _mtx_assert+0x63 > > mi_switch(c031b6c0,0,c,c24bef08,c02681cd) at mi_switch+0x25 > > sched_ithd(e) at sched_ithd+0xd9 > > Xresume14() at Xresume14+0x8 > > --- interrupt, eip = 0xc02b0008, esp - 0xc2fbeee4, epb = 0xc2feed4 --- > > __set_sysinit_set_sym_sc_mem_sys_init(c0275020,c02b0008,286,c031b7230,0) > > at __set_sysinit_set_sym_sc_mem_sys_init+0x644 > > > > Jim Bloom > > bloom@acm.org > > Hmmmmm, can you show the registers? I wonder if we are somehow running a > process that isn't fully created yet. Hmm, that shouldn't be a problem > looking at fork1().. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 12:38:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with ESMTP id 3FE1B37B4EC; Tue, 6 Feb 2001 12:38:05 -0800 (PST) Received: (from magus@localhost) by hurlame.pdl.cs.cmu.edu (8.11.1/8.11.1) id f16Kbx544151; Tue, 6 Feb 2001 15:37:59 -0500 (EST) (envelope-from magus) To: John Baldwin Cc: current@FreeBSD.org Subject: Re: md, current and stable References: From: Nat Lanza Date: 06 Feb 2001 15:37:57 -0500 In-Reply-To: John Baldwin's message of "Tue, 06 Feb 2001 11:29:48 -0800 (PST)" Message-ID: Lines: 17 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin writes: > Releases are bad enough as is w/o having to add in a multitude of > hacks so that one can roll a 5.0 release on a 2.2.x box, etc. Sure, but allowing 4.x users to do a source upgrade to 5.0 makes the upgrade path much more flexible. There's a big difference between "support source upgrades from version N-1" and "support source upgrades from all versions". --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 12:39:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 1A5C437B4EC; Tue, 6 Feb 2001 12:39:20 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f16KdQB37896; Tue, 6 Feb 2001 21:39:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Nat Lanza Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: md, current and stable In-Reply-To: Your message of "06 Feb 2001 15:37:57 EST." Date: Tue, 06 Feb 2001 21:39:26 +0100 Message-ID: <37894.981491966@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nat Lanza writes: >John Baldwin writes: > >> Releases are bad enough as is w/o having to add in a multitude of >> hacks so that one can roll a 5.0 release on a 2.2.x box, etc. > >Sure, but allowing 4.x users to do a source upgrade to 5.0 makes the >upgrade path much more flexible. There's a big difference between >"support source upgrades from version N-1" and "support source >upgrades from all versions". You don't need "make release" to do a source upgrade from 4.x to 5.x... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 12:46:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with ESMTP id EAFB637B65D; Tue, 6 Feb 2001 12:46:09 -0800 (PST) Received: (from magus@localhost) by hurlame.pdl.cs.cmu.edu (8.11.1/8.11.1) id f16KfTZ44161; Tue, 6 Feb 2001 15:41:29 -0500 (EST) (envelope-from magus) To: Poul-Henning Kamp Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: md, current and stable References: <37894.981491966@critter> From: Nat Lanza Date: 06 Feb 2001 15:41:29 -0500 In-Reply-To: Poul-Henning Kamp's message of "Tue, 06 Feb 2001 21:39:26 +0100" Message-ID: Lines: 17 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > You don't need "make release" to do a source upgrade from 4.x to 5.x... You're right. Whoops. I can still see it being useful in some cases, though, and as long as the changes necessary to support it aren't too ugly it might be worthwhile. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 12:48:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id A060537B67D; Tue, 6 Feb 2001 12:48:15 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f16KmNB38052; Tue, 6 Feb 2001 21:48:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Nat Lanza Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: md, current and stable In-Reply-To: Your message of "06 Feb 2001 15:41:29 EST." Date: Tue, 06 Feb 2001 21:48:23 +0100 Message-ID: <38050.981492503@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nat Lanza writes: >Poul-Henning Kamp writes: > >> You don't need "make release" to do a source upgrade from 4.x to 5.x... > >You're right. Whoops. > >I can still see it being useful in some cases, though, and as long as >the changes necessary to support it aren't too ugly it might be >worthwhile. I think it is possible without too much trouble, but it would take somebody to do it, it will not make my TODO list in finite time unless somebody sends me patches. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 13:12:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.ruhr.de (in-ruhr3.ruhr.de [212.23.134.2]) by hub.freebsd.org (Postfix) with SMTP id 2098D37B4EC for ; Tue, 6 Feb 2001 13:12:30 -0800 (PST) Received: (qmail 17184 invoked by alias); 6 Feb 2001 21:12:22 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.11.0/8.11.0) id f16LCJR06752 for freebsd-current@freebsd.org; Tue, 6 Feb 2001 22:12:19 +0100 (CET) (envelope-from ue) Date: Tue, 6 Feb 2001 22:12:19 +0100 From: Udo Erdelhoff To: freebsd-current@freebsd.org Subject: Looking for old snapshots Message-ID: <20010206221219.F382@nathan.ruhr.de> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I tried to install a snapshot of -current on my "new" test box. The hardware used for the box should be OK, I've managed to boot it with a recent snapshot of RELENG_4. -current is another matter. I've tried to install 20010131 and 20001204 and both die with a "Fatal Trap 18: integer divide fault while in kernel mode". The last words are: sio4: probe failed test(s): 0 2 4 6 9 unknown: failed to probe at port 0x10-0x1f on isa0 adv1: Invalid baseport of 0x20 specified. Nearest valid baseport is 0x100. Failing probe. Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc01e1c64 stack pointer = 0x10:0xc07d5704 frame pointer = 0x10:0xc07d570c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 0 (swapper) trap number = 18 panic: integer divide fault Uptime: 0s Any further analysis seems impossible: The kernel on the install floppy doesn't contain any symbols :-( The box is a P-60 (complete with the floating point bug) on a really old Intel mainboard (82433LX chipset?). The box has 32 MByte RAM, an Adaptec 2940 AU and an Oak Technologies ISA VGA Card. Right now, I'm looking for old (Sep/Oct/Nov 2000) snapshots of -current to find a version that works on this box. Thanks in advance /s/Udo -- Murphy was an optimist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 13:39:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3251737B401 for ; Tue, 6 Feb 2001 13:38:54 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f16Lb0348231; Tue, 6 Feb 2001 13:37:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A806036.5694FD66@acm.org> Date: Tue, 06 Feb 2001 13:38:03 -0800 (PST) From: John Baldwin To: Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Jim Bloom wrote: > Here are the registers (subject to typing errors): > > cs 0xc2fb0008 > ds 0xa000010 > es 0x10 > fs 0x18 > ss 0x10 > eax 0x12 > ecx 0x20 > edx 0xc00b8f00 > ebx 0x2 > esp 0xc2fbee1c > ebp 0xc2fbee28 > esi 0x100 > edi 0xc0290990 __set_sysctl_set_sym_sysctl__kern_fscale+0x4 > eip 0xc0266fcc Debugger+44 > efl 0x56 > > Jim Bloom > bloom@acm.org Erm, this doesn't look good: movl $GPROC0_SEL*8, %esi /* GSEL(entry, SEL_KPL) */ ltr %si #define GPROC0_SEL 4 /* Task state process slot zero and up */ Thus, %esi should be 32 == 0x20, not 0x100. :( I have no clue why that is screwed up, unless something is overwriting your code segment. Can you panic it and do an x/i of sw1b+0x72? It should look something like this: 121: be 20 00 00 00 mov $0x20,%esi 126: 0f 00 de ltr %si -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 14:37:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.jbloom.org (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 9B30B37B491; Tue, 6 Feb 2001 14:37:00 -0800 (PST) Received: from acm.org (localhost [127.0.0.1]) by jbloom.jbloom.org (8.11.2/8.11.2) with ESMTP id f16Mat036706; Tue, 6 Feb 2001 17:36:59 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <3A807C86.DFD3F274@acm.org> Date: Tue, 06 Feb 2001 17:36:54 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which kernel do you want me to try this with? I have tried two different kernels with two different errors. (Both have been sent at different times in the past couple days.) The registers listed here from the second kernel (with WITNESS, INVARIANTS, INVARIANT_SUPPORT, MUTEX_DEBUG). As such the addresses disagree (sw1b has 8 more bytes for invariants), but the text segment was correct. Without debug, I get the trap 9. With debug, I get a trap 12 immediately followed by a panic with mutex shced lock recursion. I rebuilt the kernel with out the debugging and check the state of things. The code is correct and the esi register had the expected value. Jim Bloom bloom@acm.org P.S. I am hitting the same problem Robert Watson mentioned. I don't have room for three kernels on the machine. John Baldwin wrote: > > On 06-Feb-01 Jim Bloom wrote: > > Here are the registers (subject to typing errors): > > > > cs 0xc2fb0008 > > ds 0xa000010 > > es 0x10 > > fs 0x18 > > ss 0x10 > > eax 0x12 > > ecx 0x20 > > edx 0xc00b8f00 > > ebx 0x2 > > esp 0xc2fbee1c > > ebp 0xc2fbee28 > > esi 0x100 > > edi 0xc0290990 __set_sysctl_set_sym_sysctl__kern_fscale+0x4 > > eip 0xc0266fcc Debugger+44 > > efl 0x56 > > > > Jim Bloom > > bloom@acm.org > > Erm, this doesn't look good: > > movl $GPROC0_SEL*8, %esi /* GSEL(entry, SEL_KPL) */ > ltr %si > > #define GPROC0_SEL 4 /* Task state process slot zero and up */ > > Thus, %esi should be 32 == 0x20, not 0x100. :( I have no clue why that is > screwed up, unless something is overwriting your code segment. Can you panic > it and do an x/i of sw1b+0x72? It should look something like this: > > 121: be 20 00 00 00 mov $0x20,%esi > 126: 0f 00 de ltr %si To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 14:58:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.34.222.47]) by hub.freebsd.org (Postfix) with SMTP id 56E7037B401 for ; Tue, 6 Feb 2001 14:57:53 -0800 (PST) Received: (qmail 1174 invoked by uid 1000); 6 Feb 2001 22:24:50 -0000 Date: Tue, 6 Feb 2001 23:24:50 +0100 From: Andrea Campi To: John Baldwin Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010206232450.B588@webcom.it> References: <20010206150643.A462@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Tue, Feb 06, 2001 at 11:02:33AM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Besides the obvious need to fix this one problem, shouldn't we > > ASSERT ih->ih_handler != NULL before calling it? > > It isn't null in this case, it is 0xdeadc0de. Can you try a pre-preemption > kernel and see if that fixes it? *BLUSH* Of course ehehe ;-) Ok, I will. Can you give me a date I should try going back to, without kernel getting out of sync with my world? Bye, Andrea -- Yes, I've heard of "decaf." What's your point? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 15:15:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 84BD637B491 for ; Tue, 6 Feb 2001 15:15:31 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f16NDY350636; Tue, 6 Feb 2001 15:13:34 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A807C86.DFD3F274@acm.org> Date: Tue, 06 Feb 2001 15:14:37 -0800 (PST) From: John Baldwin To: Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Jim Bloom wrote: > Which kernel do you want me to try this with? I have tried two > different kernels with two different errors. (Both have been sent at > different times in the past couple days.) The registers listed here > from the second kernel (with WITNESS, INVARIANTS, INVARIANT_SUPPORT, > MUTEX_DEBUG). As such the addresses disagree (sw1b has 8 more bytes for > invariants), but the text segment was correct. You'll have to turn off WITNESS to get it to die in cpu_switch(), but you'll want to leave the others on for now. > Without debug, I get the trap 9. With debug, I get a trap 12 > immediately followed by a panic with mutex shced lock recursion. > > I rebuilt the kernel with out the debugging and check the state of > things. The code is correct and the esi register had the expected > value. Hmmmmmmmm. Ok, try with debugging minus WITNESS (and you don't want MUTEX_DEBUG, that slows things down a _lot_). Then see if %esi is still 0x100 instead of 0x20. If so, then check the instructions to make sure they aren't hosed. > P.S. I am hitting the same problem Robert Watson mentioned. I don't > have room for three kernels on the machine. Yes. :( The default / size for -current is not very good, as development boxes need more room on / than production boxes. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 15:17:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 9239D37B503 for ; Tue, 6 Feb 2001 15:17:26 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f16NDY350640; Tue, 6 Feb 2001 15:13:34 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010206232450.B588@webcom.it> Date: Tue, 06 Feb 2001 15:14:38 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Feb-01 Andrea Campi wrote: >> > Besides the obvious need to fix this one problem, shouldn't we >> > ASSERT ih->ih_handler != NULL before calling it? >> >> It isn't null in this case, it is 0xdeadc0de. Can you try a pre-preemption >> kernel and see if that fixes it? > > *BLUSH* Of course ehehe ;-) > > Ok, I will. Can you give me a date I should try going back to, without kernel > getting out of sync with my world? Umm, this is the commit you want to be before: jake 2001/01/31 19:34:21 PST Modified files: sys/alpha/alpha interrupt.c machdep.c sys/i386/isa ithread.c npx.c Log: Implement preemptive scheduling of hardware interrupt threads. ... A kernel on the 30th or so should work fine with an up to date world. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 15:34:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail-ob.kamp.net (mail-ob.kamp.net [195.62.97.26]) by hub.freebsd.org (Postfix) with ESMTP id DF56B37B401 for ; Tue, 6 Feb 2001 15:34:25 -0800 (PST) Received: from bsdevil.meta.net.ob.kamp.net (port-24.d.kamp.de [195.62.120.216]) by mail-ob.kamp.net (8.10.1/8.10.1) with ESMTP id f16NYI229243; Wed, 7 Feb 2001 00:34:20 +0100 Date: Wed, 7 Feb 2001 00:34:18 +0100 Message-Id: <200102062334.f16NYI229243@mail-ob.kamp.net> From: Farid Hajji To: brian@Awfulhak.org Cc: brian@Awfulhak.org, domi@saargate.de, freebsd-current@FreeBSD.ORG In-reply-to: <200102060324.f163O0610286@hak.lan.Awfulhak.org> (message from Brian Somers on Tue, 06 Feb 2001 03:23:59 +0000) Subject: Re: Strange fopen() behaviour X-Mailer: Emacs-20.7.1/FreeBSD-5.0-CURRENT Reply-To: farid.hajji@ob.kamp.net References: <200102060324.f163O0610286@hak.lan.Awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > dev.lan.Awfulhak.org kernel log messages: > > microuptime() went backwards (18415.166882 -> 18415.158249) > > microuptime() went backwards (18490.192910 -> 18490.187579) > > microuptime() went backwards (19572.644000 -> 19572.638237) > > microuptime() went backwards (19878.637972 -> 19878.637330) > > microuptime() went backwards (20043.869158 -> 20043.868971) > > microuptime() went backwards (20074.159108 -> 20074.152253) > > microuptime() went backwards (20210.078270 -> 20210.072448) I'm also seing this as of CURRENT-2001-01-27 and later: pcm1: hwptr went backwards 36 -> 0 pcm1: hwptr went backwards 40 -> 16 pcm1: hwptr went backwards 2084 -> 2048 pcm1: hwptr went backwards 2092 -> 2064 Strange... -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | farid.hajji@ob.kamp.net - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 17:52:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 2C15637B491; Tue, 6 Feb 2001 17:52:08 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f171o6221006; Wed, 7 Feb 2001 01:50:06 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f16NUDN00646; Tue, 6 Feb 2001 23:30:13 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102062330.f16NUDN00646@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Julian Elischer Cc: Bruce Evans , Josef Karthauser , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: Message from Julian Elischer of "Tue, 06 Feb 2001 07:55:15 PST." <3A801E63.52D2B524@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Feb 2001 23:30:13 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bruce Evans wrote: > > > > On Tue, 6 Feb 2001, Josef Karthauser wrote: > > > > > I'm wondering what's changed recently to cause vmware2 running on > > > the linuxemu to lose a lot of performance with disk I/O. > > > > Use of cmpxchg and possibly other SMP pessimizations. > > > > > A couple of weeks ago I could boot win2000 under vmware2 in a matter > > > of minutes; on today's kernel it takes 5 or 10 minutes to boot, > > > and disk I/O is through the roof. > > > > > > Could someone please hit me with a clue-bat :) > > > > Read your freebsd-emulation mail :-). > > You are wrong Bruce, the cmpxchg discussion was regarding why > running FreeBSD as a GUEST OS was slow, because the virtual machine was > very slow at emulating them. That does not explain why Windows2000 and the Boot > loader > both slowed down by a factor or 3->6 over teh last 2 weeks. > > It's even slower to start up, before it has even started any emulation.. > > This feels like the system is massively slowing down page activations or > some other sort of exceptions that are standard for vmware. > > The same vmware with the same guest OS (not been updated) is now much slower. Indeed. I've been doing a ``make build'' on an OpenBSD-current vm for three days (probably about 36 hours excluding suspends) on a 366MHz laptop with a ATA33 disk. This is on a Feb 4 kernel. NetBSD next.... > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000-2001 > ---> X_.---._/ > v -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 18: 7:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 12ACF37B401; Tue, 6 Feb 2001 18:07:07 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 6 Feb 2001 18:05:08 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.1) id f1725eJ99431; Tue, 6 Feb 2001 18:05:40 -0800 (PST) (envelope-from cjc) Date: Tue, 6 Feb 2001 18:05:39 -0800 From: "Crist J. Clark" To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010206180539.I91447@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <20010206001751.F91447@rfx-216-196-73-168.users.reflex> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ctP54qlpMx3WjD+/" X-Mailer: Mutt 1.0i In-Reply-To: ; from jhb@FreeBSD.org on Tue, Feb 06, 2001 at 11:02:32AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ctP54qlpMx3WjD+/ Content-Type: text/plain; charset=us-ascii On Tue, Feb 06, 2001 at 11:02:32AM -0800, John Baldwin wrote: [snip] > ARGH. The trap code is breaking this. [snip] > Just comment out that enable_intr() and please try again. This should give you > a stack trace where the actual bug is. Thanks. Done. And the winner is... (see attachment, did not repeat the kernel config since it has not changed) -- Crist J. Clark cjclark@alum.mit.edu --ctP54qlpMx3WjD+/ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="boot.msg" 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 #3: Tue Feb 6 13:59:53 PST 2001 cjc@rfx-216-196-73-168.users.reflexcom.com:/usr/obj/export/current/src/sys/BUBBLES Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping = 11 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30015488 (29312K bytes) Preloaded elf kernel "kernel.BUBBLES" at 0xc02c5000. Intel Pentium detected, installing workaround for F00F bug apm0: on motherboard apm0: found APM BIOS v1.1, connected at v1.1 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 8.0 (no driver attached) ep0: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:20:af:17:a3:e9 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc1: cannot reserve I/O port range sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 1000 packets/entry by default ad0: 1222MB [2484/16/63] at ata0-master BIOSPIO acd0: CDROM at ata0-slave using BIOSPIO Mounting root from ufs:/dev/ad0s1a kernel trap 9 with interrupts disabled panic: blockable mtx_enter() of Giant when not legal @ /export/current/src/sys/i386/i386/trap.c:653 Debugger("panic") Stopped at Debugger+0x44: pushl %ebx db> trace Debugger(c0215a83) at Debugger+0x44 panic(c0214bc0,c022fc74,c0230820,28d,c02782e0) at panic+0x70 witness_enter(c02782e0,0,c0230820,28d,0) at witness_enter+0x1d9 _mtx_enter(c02782e0,0,c0230820,28d,c02781a0) at _mtx_enter+0x106 trap(18,10,10,c3612a60,20) at trap+0x583 calltrap() at calltrap+0x5 --- trap 0x9, eip = 0xc01fc642, esp = 0xc3a29f50, ebp = 0xc3a29f64 --- sw1b(4000) at sw1b+0x81 ithd_loop(0,c3a29fa8) at ithd_loop+0x10d fork_exit(c0200d94,0,c3a29fa8) at fork_exit+0x2d fork_trampoline() at fork_trampoline+0x8 db> --ctP54qlpMx3WjD+/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 18:35: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from jbloom.jbloom.org (reyim.ne.mediaone.net [24.218.251.241]) by hub.freebsd.org (Postfix) with ESMTP id 8313137B401; Tue, 6 Feb 2001 18:34:43 -0800 (PST) Received: from acm.org (localhost [127.0.0.1]) by jbloom.jbloom.org (8.11.2/8.11.2) with ESMTP id f172Yf071651; Tue, 6 Feb 2001 21:34:42 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <3A80B43B.659DCED5@acm.org> Date: Tue, 06 Feb 2001 21:34:35 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 06-Feb-01 Jim Bloom wrote: > > Which kernel do you want me to try this with? I have tried two > > different kernels with two different errors. (Both have been sent at > > different times in the past couple days.) The registers listed here > > from the second kernel (with WITNESS, INVARIANTS, INVARIANT_SUPPORT, > > MUTEX_DEBUG). As such the addresses disagree (sw1b has 8 more bytes for > > invariants), but the text segment was correct. > > You'll have to turn off WITNESS to get it to die in cpu_switch(), but you'll > want to leave the others on for now. I turned off WITNESS and still received the mutex error. A little reading of the code showed that mutex assertions are inclued with ifdef INVARIANTS. > > > Without debug, I get the trap 9. With debug, I get a trap 12 > > immediately followed by a panic with mutex shced lock recursion. > > > > I rebuilt the kernel with out the debugging and check the state of > > things. The code is correct and the esi register had the expected > > value. > > Hmmmmmmmm. Ok, try with debugging minus WITNESS (and you don't want > MUTEX_DEBUG, that slows things down a _lot_). Then see if %esi is > still 0x100 instead of 0x20. If so, then check the instructions to make sure > they aren't hosed. With INVARIANTS turned off and WITNESS on, I received a trap 27 (stack fault) at sw1b+0x77. The instructions are fine and %esi was 0x20 as it should be. I won't worry about MUTEX_DEBUG being slow just yet. I am only around the start of /etc/rc when the machine dies. Do you have any other ideas on things that I can try to diagnose this problem? Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 21: 0:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 0E46537B401 for ; Tue, 6 Feb 2001 21:00:09 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f174wj358348; Tue, 6 Feb 2001 20:58:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010206180539.I91447@rfx-216-196-73-168.users.reflex> Date: Tue, 06 Feb 2001 20:59:52 -0800 (PST) From: John Baldwin To: "Crist J. Clark" Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Feb-01 Crist J. Clark wrote: > On Tue, Feb 06, 2001 at 11:02:32AM -0800, John Baldwin wrote: > > [snip] > >> ARGH. The trap code is breaking this. > > [snip] > >> Just comment out that enable_intr() and please try again. This should give >> you >> a stack trace where the actual bug is. Thanks. > > Done. And the winner is... (see attachment, did not repeat the kernel > config since it has not changed) Well, can't win with WITNESS here. :) It is still panic'ing on the 'ltr' though. Hmm, oh. ARgh. It's showing the regs from teh most recent panic probably. *sigh* Just turn off WITNESS altogether. It is getting in our way in this particular instance. Sorry for the numerous bounces back and forth. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 21: 1:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5578F37B401 for ; Tue, 6 Feb 2001 21:01:31 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f174wk358352; Tue, 6 Feb 2001 20:58:46 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A80B43B.659DCED5@acm.org> Date: Tue, 06 Feb 2001 20:59:54 -0800 (PST) From: John Baldwin To: Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Feb-01 Jim Bloom wrote: > John Baldwin wrote: >> >> On 06-Feb-01 Jim Bloom wrote: >> > Which kernel do you want me to try this with? I have tried two >> > different kernels with two different errors. (Both have been sent at >> > different times in the past couple days.) The registers listed here >> > from the second kernel (with WITNESS, INVARIANTS, INVARIANT_SUPPORT, >> > MUTEX_DEBUG). As such the addresses disagree (sw1b has 8 more bytes for >> > invariants), but the text segment was correct. >> >> You'll have to turn off WITNESS to get it to die in cpu_switch(), but you'll >> want to leave the others on for now. > > I turned off WITNESS and still received the mutex error. A little > reading of the code showed that mutex assertions are inclued with ifdef > INVARIANTS. > >> >> > Without debug, I get the trap 9. With debug, I get a trap 12 >> > immediately followed by a panic with mutex shced lock recursion. >> > >> > I rebuilt the kernel with out the debugging and check the state of >> > things. The code is correct and the esi register had the expected >> > value. >> >> Hmmmmmmmm. Ok, try with debugging minus WITNESS (and you don't want >> MUTEX_DEBUG, that slows things down a _lot_). Then see if %esi is >> still 0x100 instead of 0x20. If so, then check the instructions to make >> sure >> they aren't hosed. > > With INVARIANTS turned off and WITNESS on, I received a trap 27 (stack > fault) at sw1b+0x77. The instructions are fine and %esi was 0x20 as it > should be. I won't worry about MUTEX_DEBUG being slow just yet. I am > only around the start of /etc/rc when the machine dies. A stack fault on 'ltr'? Hmm... leeching from teh 386 manual on ltr: Protected Mode Exceptions #GP(0) for an illegal memory operand effective address in the CS, DS, ES, FS, or GS segments; #SS(0) for an illegal address in the SS segment; #GP(0) if the current privilege level is not 0; #GP(selector) if the object named by the source selector is not a TSS or is already busy; #NP(selector) if the TSS is marked "not present"; #PF(fault-code) for a page fault Hmm, so our %ss selector must be invalid in the new TSS. h0h0. Ok, umm. I have no idea how that happened. AFAIK, that shouldn't be touched once the system is up and running. :( So, probably something is trashing it by walking off a dead pointer or some such. :( > Do you have any other ideas on things that I can try to diagnose this > problem? Right now, no. I know of one potential problem child with preemption: the interrupt thread list handling, and I'm overhauling the ithread code right now so I can try and fix that. > Jim Bloom > bloom@acm.org -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 21:41:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 3E8FF37B699 for ; Tue, 6 Feb 2001 21:41:11 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.2/8.11.2) id f175hYZ14318 for freebsd-current@freebsd.org; Tue, 6 Feb 2001 21:43:34 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200102070543.f175hYZ14318@troutmask.apl.washington.edu> Subject: DEVFS and ms-dos partitions To: FreeBSD Current Date: Tue, 6 Feb 2001 21:43:33 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a world and kernel from 4 Feb 01. I tried listing the contents in my mounted MS-DOS slice via "ls /msdos" as a normal users, but got a permission denied message (which I've never received before). So, a quick check on the directory permissions shows: d-------w- 1 root 493 arch 4096 Jan 1 1980 msdos/ which appears to be somewhat strange. So, I unmounted the slice and manually mounted the slice with various incantations of mount_msdos. All yield the above listing. The source in src/sbin/mount_msdos has changed in a long time, so is this a side effect of using DEVFS? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 22: 8:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id A7E6F37B503 for ; Tue, 6 Feb 2001 22:08:36 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA08281; Wed, 7 Feb 2001 17:08:27 +1100 Date: Wed, 7 Feb 2001 17:08:05 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Steve Kargl Cc: FreeBSD Current Subject: Re: DEVFS and ms-dos partitions In-Reply-To: <200102070543.f175hYZ14318@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Feb 2001, Steve Kargl wrote: > I have a world and kernel from 4 Feb 01. I tried listing the > contents in my mounted MS-DOS slice via "ls /msdos" as a normal > users, but got a permission denied message (which I've never > received before). So, a quick check on the directory permissions > shows: > > d-------w- 1 root 493 arch 4096 Jan 1 1980 msdos/ > > which appears to be somewhat strange. So, I unmounted the > slice and manually mounted the slice with various incantations > of mount_msdos. All yield the above listing. > > The source in src/sbin/mount_msdos has changed in a long time, > so is this a side effect of using DEVFS? This is caused by the same bug that cause panics for exporting filesystems (things in mount structs moving around whenever the size of struct mtx changes). struct msdosfs_args is particularly well designed to be affected by this bug even when nothing is exported: struct msdosfs_args { char *fspec; /* blocks special holding the fs to mount */ struct export_args export; /* network export information */ uid_t uid; /* uid that owns msdosfs files */ gid_t gid; /* gid that owns msdosfs files */ mode_t mask; /* mask to be applied for msdosfs perms */ int flags; /* see below */ int magic; /* version number */ u_int16_t u2w[128]; /* Local->Unicode table */ u_int8_t ul[128]; /* Local upper->lower table */ u_int8_t lu[128]; /* Local lower->upper table */ u_int8_t d2u[128]; /* DOS->local table */ u_int8_t u2d[128]; /* Local->DOS table */ }; The fields after the export field become garbage when the size of the export field changes. The garbage is easy to see using `ls -ld /msdos'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 22:34: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 7380437B491 for ; Tue, 6 Feb 2001 22:33:42 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.2/8.11.2) id f176a2f14720; Tue, 6 Feb 2001 22:36:02 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200102070636.f176a2f14720@troutmask.apl.washington.edu> Subject: Re: DEVFS and ms-dos partitions In-Reply-To: from Bruce Evans at "Feb 7, 2001 05:08:05 pm" To: Bruce Evans Date: Tue, 6 Feb 2001 22:36:02 -0800 (PST) Cc: FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Tue, 6 Feb 2001, Steve Kargl wrote: > > > > > d-------w- 1 root 493 arch 4096 Jan 1 1980 msdos/ > > > > The source in src/sbin/mount_msdos has changed in a long time, not > > so is this a side effect of using DEVFS? > > This is caused by the same bug that cause panics for exporting > filesystems (things in mount structs moving around whenever the size > of struct mtx changes). struct msdosfs_args is particularly well > designed to be affected by this bug even when nothing is exported: > [snip of struct] > The fields after the export field become garbage when the size of the > export field changes. The garbage is easy to see using `ls -ld /msdos'. Hmmm, thanks for the explanation. That o+w permission is a little worrisome. I take it there's no way to force a a different mode on the directory (short of never getting world and kernel out-of-sync, which makes chasing the last mutex bugs much more fun). Mea culpa: I know better. It is a slice not a partition. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 22:42:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interocity.com (www.interocity.com [209.208.240.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C52837B401; Tue, 6 Feb 2001 22:41:35 -0800 (PST) Received: from dampyr (unverified [209.208.240.108]) by mail.interocity.com (Rockliffe SMTPRA 2.1.6) with SMTP id for ; Tue, 06 Feb 2001 14:23:31 -0500 Message-ID: <000a01c09072$4a2a46d0$6cf0d0d1@interocity.com> Reply-To: "press" From: "press" To: Subject: WELCOME TO THE SOJOURN PROJECT! Date: Tue, 6 Feb 2001 14:23:30 -0500 Organization: sojourn project MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C09048.612AE4E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C09048.612AE4E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The Sojourn Project is a civil rights education project that takes high = school students from around the nation to historical civil rights = landmarks throughout the South. From time to time, we use this = newsletter to publicize our program and encourage involvement from the = African-American community. For more information about the program, = please visit http://www.sojournproject.org. =20 INDEPENDENCE COMMUNITY FOUNDATION GRANT SUPPORTS CIVIL RIGHTS EDUCATION = PROJECT IN BROOKLYN =20 For Immediate Release - January 30, 2001 =20 BROOKLYN, N.Y. -- On the eve of Black History Month, the New York = chapter of the Sojourn civil rights project today proudly announced the = receipt of a grant from the Independence Community Foundation (ICF) that = will underwrite a Brooklyn public high school student for a 10-day = travel-study program to civil rights landmarks in the South. The = student will join a group of New York City and California students who = qualify for expeditions scheduled for spring 2001. In addition to this = student scholarship, the ICF grant will provide organizational support = for Sojourn to present a course on civil rights history to students from = Brooklyn high schools and non-profit programs. =20 Marilyn G. Gelber, Executive Director of ICF, said: "Independence = Foundation is pleased to support such a worthy project. We are = particularly delighted that this $5,000 grant will allow a Brooklyn = student to explore firsthand the roots of our nation's civil rights = movement and personally observe the extraordinary change that leaders = like the Rev. Dr. Martin Luther King Jr. helped to bring about. By = understanding history, young people will be better prepared to combat = bigotry today." =20 ICF's advocacy on behalf of Sojourn has been a vital factor in = successfully introducing the project to Brooklyn and its broad network = of philanthropic support. According to Sojourn board member NY State = Assemblyman Roger Green (57th AD), "The staff at ICF vetted the program = as it rolled out in Brooklyn last summer. Then they pledged their = support. And then they went the extra mile, providing introductions to = other supporters. Without the foresight and generosity of ICF, = Sojourn's presence in New York would still be a dream. ICF made it = real." Mr. Green chairs the Assembly Committee on Children & Families = in Albany. =20 Sojourn provides an opportunity for high school students from New York = City, San Francisco, Oakland and Los Angeles to travel to the South and = study the civil rights era in intimate settings. The program's = itinerary includes Washington DC, Atlanta, Tuskegee, Montgomery, Selma, = Birmingham, Jackson, Little Rock and Memphis. By way of a "living = history" syllabus - books, documentaries, recordings and on-site visits = with civil rights veterans - lessons of tolerance, nonviolence, personal = courage, compassion, forgiveness, faith, hope, justice and civic = responsibility are imparted during expeditions. =20 John Lewis (U.S. Congressman), Myrlie Evers-Williams (Medgar Evers' = widow), members of the Little Rock Nine, voting rights pioneer Robert = Moses, Rev. Fred Shuttlesworth (leader of the 1963 Birmingham movement), = Chris McNair (father of one of four little girls killed in a Birmingham = church bombing) and Martin Luther King III, among others, meet with = students and teachers during their many stops through the South.=20 =20 Since February 1999, Sojourn has conducted eight civil rights = expeditions. More than 665 participants have met with civil rights = veterans who have shared the program's ethical lesson plans. By the end = of this school year, Sojourn will have served more than 1000 students. = To visit Sojourn's Web site, click: www.sojournproject.org. To visit = the Web site of the Independence Community Foundation, click: = www.icfny.org. =20 "Until justice rolls down like waters and righteousness like a mighty stream." =20 ------=_NextPart_000_0007_01C09048.612AE4E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 The Sojourn Project is a civil rights education project = that takes=20 high school students from around the nation to historical civil rights = landmarks=20 throughout the South. From time to time, we use this newsletter to = publicize our=20 program and encourage involvement from the African-American community. = For more=20 information about the program, please visit http://www.sojournproject.org.=
 

 

INDEPENDENCE = COMMUNITY=20 FOUNDATION GRANT SUPPORTS CIVIL RIGHTS = EDUCATION=20 PROJECT IN BROOKLYN

 

For Immediate=20 Release –=20 January 30, 2001

 

BROOKLYN,=20 N.Y. -- On=20 the eve of Black History Month, the New York chapter of the Sojourn = civil rights=20 project today proudly announced the receipt of a grant from the = Independence=20 Community Foundation (ICF) that will underwrite a Brooklyn public high = school=20 student for a 10-day travel-study program to civil rights landmarks in = the=20 South.  The student will = join a=20 group of New York City and California students who qualify for = expeditions=20 scheduled for spring 2001.  = In=20 addition to this student scholarship, the ICF grant will provide = organizational=20 support for Sojourn to present a course on civil rights history to = students from=20 Brooklyn high schools and non-profit programs.

 

Marilyn G. Gelber, = Executive=20 Director of ICF, said: “Independence Foundation is pleased to = support such a=20 worthy project.  We are = particularly=20 delighted that this $5,000 grant will allow a Brooklyn student to = explore=20 firsthand the roots of our nation’s civil rights movement and = personally observe=20 the extraordinary change that leaders like the Rev. Dr. Martin Luther = King Jr.=20 helped to bring about. By understanding history, young people will be = better=20 prepared to combat bigotry today.”

 

ICF’s = advocacy on behalf of=20 Sojourn has been a vital factor in successfully introducing the project = to=20 Brooklyn and its broad network of philanthropic support.  According to Sojourn board = member NY=20 State Assemblyman Roger Green (57th AD), “The staff at = ICF vetted the=20 program as it rolled out in Brooklyn last summer.  Then they pledged their = support.  And then they went the extra = mile,=20 providing introductions to other supporters.  Without the foresight and = generosity of=20 ICF, Sojourn’s presence in New York would still be a dream.  ICF made it real.”  Mr. Green chairs the Assembly = Committee=20 on Children & Families in Albany.

 

Sojourn=20 provides an opportunity for high school students from New York City, San = Francisco, Oakland and Los Angeles to travel to the South and study the = civil=20 rights era in intimate settings.  = The=20 program’s itinerary includes Washington DC, Atlanta, Tuskegee, = Montgomery,=20 Selma, Birmingham, Jackson, Little Rock and Memphis.  By way of a “living = history” syllabus —=20 books, documentaries, recordings and on-site visits with civil rights = veterans —=20 lessons of tolerance, nonviolence, personal courage, compassion, = forgiveness,=20 faith, hope, justice and civic responsibility are imparted during=20 expeditions.  =

John Lewis (U.S.=20 Congressman), Myrlie Evers-Williams (Medgar Evers’ widow), members = of the Little=20 Rock Nine, voting rights pioneer Robert Moses, Rev. Fred Shuttlesworth = (leader=20 of the 1963 Birmingham movement), Chris McNair (father of one of four = little=20 girls killed in a Birmingham church bombing) and Martin Luther King III, = among=20 others, meet with students and teachers during their many stops through = the=20 South.

 

Since February = 1999, Sojourn=20 has conducted eight civil rights expeditions.  More than 665 participants = have met with=20 civil rights veterans who have shared the program’s ethical lesson = plans.  By the end of this school = year, Sojourn=20 will have served more than 1000 students. =20 To visit Sojourn’s Web site, click: www.sojournproject.org.  To visit the Web site of the=20 Independence Community Foundation, click: www.icfny.org.   

“Until justice=20 rolls down like waters

and = righteousness=20 like a mighty stream.”

 

------=_NextPart_000_0007_01C09048.612AE4E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 23: 4:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 440D337B4EC for ; Tue, 6 Feb 2001 23:04:27 -0800 (PST) Received: from xor.obsecurity.org ([64.165.226.103]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G8D002W4H80P1@mta5.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Tue, 6 Feb 2001 21:43:13 -0800 (PST) Received: by xor.obsecurity.org (Postfix, from userid 1000) id BCB4866B62; Tue, 06 Feb 2001 21:45:51 -0800 (PST) Date: Tue, 06 Feb 2001 21:45:51 -0800 From: Kris Kennaway Subject: Re: Strange fopen() behaviour In-reply-to: <200102062334.f16NYI229243@mail-ob.kamp.net>; from farid.hajji@ob.kamp.net on Wed, Feb 07, 2001 at 12:34:18AM +0100 To: Farid Hajji Cc: freebsd-current@FreeBSD.ORG Message-id: <20010206214551.A19370@mollari.cthul.hu> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200102060324.f163O0610286@hak.lan.Awfulhak.org> <200102062334.f16NYI229243@mail-ob.kamp.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Feb 07, 2001 at 12:34:18AM +0100, Farid Hajji wrote: > I'm also seing this as of CURRENT-2001-01-27 and later: > pcm1: hwptr went backwards 36 -> 0 > pcm1: hwptr went backwards 40 -> 16 > pcm1: hwptr went backwards 2084 -> 2048 > pcm1: hwptr went backwards 2092 -> 2064 These have existed "forever"..different problem. Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6gOEPWry0BWjoQKURAgrsAJ9Nd36e6tMdCEKfQt/GHvnOfL0BkQCfWA+6 jvsGjyGXHFNMJZdREt3nGr0= =PLEp -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Feb 6 23:13:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from octopus.phy.bg.ac.yu (octopus.phy.bg.ac.yu [147.91.80.4]) by hub.freebsd.org (Postfix) with ESMTP id E2F5B37B401 for ; Tue, 6 Feb 2001 23:13:37 -0800 (PST) Received: from octopus.phy.bg.ac.yu (octopus.phy.bg.ac.yu [147.91.80.4]) by octopus.phy.bg.ac.yu (Postfix) with ESMTP id C3CAF19F37 for ; Wed, 7 Feb 2001 08:13:31 +0100 (CET) Date: Wed, 7 Feb 2001 08:13:31 +0100 (CET) From: Rasa Karapandza To: current@freebsd.org Subject: ctm via mail NEWBIE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I receive ctm-src current by e-mail, which I retrive using netscape. I save message as plain text then I try uudecode and I alvays get no begin line I tryed to edit file but I'm not able to get it work. Regards, Rasa P.S. I know that this question doesn,t belong here but I did not get answer for a long time from questions@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 1:30:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 9B95537B491 for ; Wed, 7 Feb 2001 01:30:17 -0800 (PST) Received: (qmail 627 invoked by uid 1000); 7 Feb 2001 09:23:59 -0000 Date: Wed, 7 Feb 2001 10:23:58 +0100 From: Andrea Campi To: John Baldwin Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010207102357.A502@webcom.it> References: <20010206232450.B588@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Tue, Feb 06, 2001 at 03:14:38PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ok, I will. Can you give me a date I should try going back to, without kernel > > getting out of sync with my world? > > A kernel on the 30th or so should work fine with an up to date world. Thought I had tried this... FreeBSD 5.0-CURRENT #0: Wed Jan 10 11:00:55 CET 2001 root@brian:/usr/obj/usr/src/sys/THINKPAD is fine. I am currently doing a cvs co -D"2001-01-30" src/sys I will report on this later. Bye, Andrea -- Tagline generated by 'gensig' mail-client-independent .signature generator. Get your copy at http://www.geeks.com/~robf/gensig/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 1:37:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.port.ru (mx6.port.ru [194.67.23.42]) by hub.freebsd.org (Postfix) with ESMTP id 0348C37B699; Wed, 7 Feb 2001 01:36:55 -0800 (PST) Received: from adsl-141-154-118-213.bostma.adsl.bellatlantic.net ([141.154.118.213] helo=kan.dnsalias.net) by smtp6.port.ru with esmtp (Exim 3.14 #87) id 14QR1w-000Lyk-00; Wed, 07 Feb 2001 12:36:53 +0300 Received: (from kan@localhost) by kan.dnsalias.net (8.11.2/8.11.2) id f175woN00732; Wed, 7 Feb 2001 00:58:50 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.6 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Feb 2001 00:58:49 -0500 (EST) From: "Alexander N. Kabaev" To: freebsd-current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Cc: John Baldwin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can easily reproduce the panic on my -CURRENT Athlon box by just starting any print job. Other that that, the system seems to be running OK, i.e. no panics occur unless some lpr activity is involved. Here is the stack dump: #9 0xc02a9fbc in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -857849588, tf_esi = 32, tf_ebp = -696148124, tf_isp = -696148164, tf_ebx = -1069967232, tf_edx = -857849856, tf_ecx = -868400672, tf_eax = -1070952435, tf_trapno = 9, tf_err = 32, tf_eip = -1070952316, tf_cs = 8, tf_eflags = 65670, tf_esp = -1071733991, tf_ss = 0}) at ../../i386/i386/trap.c:656 #10 0xc02a9084 in sw1b () #11 0xc02b075b in ithd_loop (dummy=0x0) at ../../i386/isa/ithread.c:216 #12 0xc01dc48d in fork_exit (callout=0xc02b0664 , arg=0x0, frame=0xd6819fa8) at ../../kern/kern_fork.c:669 and disassembled code at the point of the trap looks like 0xc02a9076 : mov %eax,0x0(%ebx) 0xc02a9079 : mov 0x4(%edi),%eax 0xc02a907c : mov %eax,0x4(%ebx) 0xc02a907f : mov $0x20,%esi 0xc02a9084 : ltr %si ...... ^^^^^^^^^^^^^^ Also, a pretty unpleasant crash occurs on the latest current boxes everytime vidcontrol is used to change console resolution to the VESA_800x600 mode. I was able to get the crash dump, but unfortunately it seems like the stack is becoming corrupt and so there is no useful information to report. ---------------------------------- E-Mail: Alexander N. Kabaev Date: 07-Feb-2001 Time: 00:35:38 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 1:57:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 4422037B69D for ; Wed, 7 Feb 2001 01:57:16 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id KAA01479 for ; Wed, 7 Feb 2001 10:48:12 +0100 (MET) Date: Wed, 7 Feb 2001 10:48:12 +0100 (CET) From: Harti Brandt To: Subject: Current buildworld broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With a freshly CVSuped current I get: ===> usr.bin/ncal cc -O -pipe -Wall -Wmissing-prototypes -fstrict-prototypes -ansi -pedantic -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/ncal/ncal.c /usr/src/usr.bin/ncal/ncal.c: In function `printeaster': /usr/src/usr.bin/ncal/ncal.c:390: warning: unknown conversion type character `F' in format /usr/src/usr.bin/ncal/ncal.c: In function `mkmonth': /usr/src/usr.bin/ncal/ncal.c:581: warning: flag `O' used with type `B' /usr/src/usr.bin/ncal/ncal.c: In function `mkmonthb': /usr/src/usr.bin/ncal/ncal.c:672: warning: flag `O' used with type `B' cc -O -pipe -Wall -Wmissing-prototypes -fstrict-prototypes -ansi -pedantic -I/usr/obj/usr/src/i386/usr/include -o ncal ncal.o -lcalendar gzip -cn /usr/src/usr.bin/ncal/ncal.1 > ncal.1.gz ===> usr.bin/netstat cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/if.c /usr/src/usr.bin/netstat/if.c: In function `intpr': /usr/src/usr.bin/netstat/if.c:401: structure has no member named `lh_first' /usr/src/usr.bin/netstat/if.c:401: structure has no member named `le_next' /usr/src/usr.bin/netstat/if.c:389: warning: `multiaddr' might be used uninitialized in this function *** Error code 1 Stop in /usr/src/usr.bin/netstat. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. This is probably related to the change of the type of the multiaddr list. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 3:52:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 847B137B65D for ; Wed, 7 Feb 2001 03:52:30 -0800 (PST) Received: (qmail 1270 invoked by uid 1000); 7 Feb 2001 11:46:11 -0000 Date: Wed, 7 Feb 2001 12:46:11 +0100 From: Andrea Campi To: John Baldwin Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010207124609.A594@webcom.it> References: <20010206232450.B588@webcom.it> <20010207102357.A502@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010207102357.A502@webcom.it>; from andrea@webcom.it on Wed, Feb 07, 2001 at 10:23:58AM +0100 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running a kernel I got with this: > > cvs co -D"2001-01-30" src/sys > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00 I get: panic: malloc(M_WAITOK) in interrupt context Debugger("panic") Stopped at Debugger+0x45: pushl %ebx db> trace Debugger(c02119a3) at Debugger+0x45 panic(....) malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend ithd_loop(0,c6623fa8) at ithd_loop+0x56 fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 fork_trampoline() at fork_trampoline+0x8 db> witness_list "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 -- Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 5:34: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 2AD9E37B401 for ; Wed, 7 Feb 2001 05:33:45 -0800 (PST) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id 51CDE5C4C for ; Wed, 7 Feb 2001 14:33:44 +0100 (CET) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id 86D904E77; Wed, 7 Feb 2001 14:33:43 +0100 (CET) Date: Wed, 7 Feb 2001 14:33:43 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Sound driver broken Message-ID: <20010207143343.A48233@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sources as of a few minutes ago. cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/sound/pcm/channel.c ../../dev/sound/pcm/channel.c: In function `chn_lockinit': ../../dev/sound/pcm/channel.c:50: structure has no member named `mutex' ../../dev/sound/pcm/channel.c:50: structure has no member named `name' ../../dev/sound/pcm/channel.c:51: structure has no member named `mutex' The pcm_channel struct has no « mutex » field... -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 5:51:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0B9FC37B491 for ; Wed, 7 Feb 2001 05:50:59 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f17DouT64429 for freebsd-current@FreeBSD.ORG; Wed, 7 Feb 2001 14:50:56 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.1/8.11.0) with SMTP id f17Dogx56216 for ; Wed, 7 Feb 2001 14:50:43 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <033801c0910d$093451c0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: Subject: *_ROOT removed Date: Wed, 7 Feb 2001 14:51:12 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While the error-messages are clear, I don't remember seeing any = heads-up, or mentioning of this in UPDATING Or is it just me...? -------------------------------------------------------------- >>> Kernel build for GINA started on Mon Feb 5 07:13:06 CET 2001 -------------------------------------------------------------- =3D=3D=3D> GINA mkdir -p /usr/obj/usr/src/sys cd /usr/src/sys/i386/conf; = PATH=3D/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/= obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d = /usr/obj/usr/src/sys/GINA GINA WARNING: option `FFS' moved from opt_ffs.h to opt_dontuse.h WARNING: unknown option `FFS_ROOT' removed from = /usr/obj/usr/src/sys/GINA/opt_ffs.h GINA:31: unknown option "CD9660_ROOT" *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 6:29:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id BACEC37B491 for ; Wed, 7 Feb 2001 06:28:55 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f17ESgt64468; Wed, 7 Feb 2001 06:28:43 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102071428.f17ESgt64468@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Leif Neland" Cc: freebsd-current@FreeBSD.ORG Subject: Re: *_ROOT removed In-Reply-To: <033801c0910d$093451c0$0e00a8c0@neland.dk> Date: Wed, 07 Feb 2001 06:28:42 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Leif Neland" wrote: > While the error-messages are clear, I don't remember seeing any heads-up, or mentioning of this in UPDATING > > Or is it just me...? No, there wasn't one.. The commit message was pretty clear - You are reading them, right? We usually do HEAD UP's for stuff that will break people pretty badly or get them in trouble (eg: an unviable kernel if the instructions are not followed). At least you got the message. buildkernel would have silently ignored this up until recently. > -------------------------------------------------------------- > >>> Kernel build for GINA started on Mon Feb 5 07:13:06 CET 2001 > -------------------------------------------------------------- > ===> GINA > mkdir -p /usr/obj/usr/src/sys > cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/ src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/ bin config -d /usr/obj/usr/src/sys/GINA GINA > WARNING: option `FFS' moved from opt_ffs.h to opt_dontuse.h > WARNING: unknown option `FFS_ROOT' removed from /usr/obj/usr/src/sys/GINA/opt _ffs.h > GINA:31: unknown option "CD9660_ROOT" > *** Error code 1 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 8:12: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 28EF237B401; Wed, 7 Feb 2001 08:11:51 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f17GBgd22842 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Wed, 7 Feb 2001 17:11:44 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f17GC6r75090 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO); Wed, 7 Feb 2001 17:12:08 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f17GBvS72778; Wed, 7 Feb 2001 17:11:57 +0100 (CET) (envelope-from ticso) Date: Wed, 7 Feb 2001 17:11:57 +0100 From: Bernd Walter To: non@ever.sanda.gr.jp Cc: current@FreeBSD.ORG, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT Message-ID: <20010207171156.A72756@cicely5.cicely.de> References: <20010205170041.A86739@panzer.kdm.org> <20010206154333F.non@ever.sanda.gr.jp> <20010206133030.A2232@cicely5.cicely.de> <20010206232112W.non@ever.sanda.gr.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010206232112W.non@ever.sanda.gr.jp>; from non@ever.sanda.gr.jp on Tue, Feb 06, 2001 at 11:21:12PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 06, 2001 at 11:21:12PM +0900, non@ever.sanda.gr.jp wrote: > Today I tried with 4.2-RELEASE (sorry not -current) and, > 1. Boot up the 4.2-RELEASE with GENERIC kernel. > 2. Connect MO drive with PC Card SCSI(ncv). > 3. Insert PC Card without medium in the MO drive. > 4. The pccardd automatically run camcontrol rescan. > 5. Message says that da0 is 0MB capacity. > 6. Run fdisk da0 > 7. got panic with divided by zero. > > Probably divided by zero is caused at line 737 or 748 in the > scsi_low_action() in cam/scsi/scsi_low.c because of ccg->block_size or > secs_per_cylinder is zero. I never used fdisk on a removeable disk as I only needed them for FreeBSD. The follwoing always worked for me: dd if=/dev/zero bs=10240 count=1 of=/dev/dax disklabel -rw dax auto disklabel -e dax It looks like fdisk triggers the bug. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 8:43:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id 2462A37B491; Wed, 7 Feb 2001 08:43:14 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id 93440BAAF; Wed, 7 Feb 2001 11:43:12 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: Andrea Campi Cc: John Baldwin , current@FreeBSD.ORG, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup In-Reply-To: Message from Andrea Campi of "Wed, 07 Feb 2001 12:46:11 +0100." <20010207124609.A594@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Feb 2001 11:43:12 -0500 From: Jake Burkholder Message-Id: <20010207164312.93440BAAF@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Running a kernel I got with this: > > > > > cvs co -D"2001-01-30" src/sys > > > > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00 > > I get: > > panic: malloc(M_WAITOK) in interrupt context > Debugger("panic") > Stopped at Debugger+0x45: pushl %ebx > db> trace > Debugger(c02119a3) at Debugger+0x45 > panic(....) > malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a > exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 > kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend > ithd_loop(0,c6623fa8) at ithd_loop+0x56 > fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 > fork_trampoline() at fork_trampoline+0x8 > db> witness_list > "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 > Make sure you have intr_machdep.c version 1.47. revision 1.47 date: 2001/01/28 17:20:11 > -- > Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 10:59:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from unix.za.net (unix.os.org.za [196.7.89.10]) by hub.freebsd.org (Postfix) with ESMTP id 9873137B684 for ; Wed, 7 Feb 2001 10:59:25 -0800 (PST) Received: from bradley by unix.za.net with local (Exim 3.16 #1) id 14QZoD-0009og-00 for current@FreeBSD.org; Wed, 07 Feb 2001 20:59:17 +0200 To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: http://www.FreeBSD.org/handbook/makeworld.html X-Mailer: Lynx, Version 2.8.2rel.1 Subject: http://www.FreeBSD.org/handbook/makeworld.html Message-Id: From: Bradley Clayton Date: Wed, 07 Feb 2001 20:59:17 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want mailling list :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 11:26:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A56D837B67D; Wed, 7 Feb 2001 11:26:20 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id UAA63833; Wed, 7 Feb 2001 20:26:15 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Brian Somers Cc: Julian Elischer , Bruce Evans , Josef Karthauser , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: <200102062330.f16NUDN00646@hak.lan.Awfulhak.org> From: Dag-Erling Smorgrav Date: 07 Feb 2001 20:26:15 +0100 In-Reply-To: Brian Somers's message of "Tue, 06 Feb 2001 23:30:13 +0000" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm > for three days (probably about 36 hours excluding suspends) on a > 366MHz laptop with a ATA33 disk. Would it be possible for someone experiencing this slowdown to try to narrow down the day (or even the week) on which it occurred? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 11:29:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from rapidsite.vwh.net (rapidsite.vwh.net [161.58.231.114]) by hub.freebsd.org (Postfix) with ESMTP id 151E437B67D for ; Wed, 7 Feb 2001 11:29:38 -0800 (PST) Received: from nohdr.ids.rapidsite.net (ids02.team-center.net [209.238.9.28]) by rapidsite.vwh.net (8.8.8) id MAA85736; Wed, 7 Feb 2001 12:30:28 -0700 (MST) Date: Wed, 7 Feb 2001 12:30:28 -0700 (MST) Message-Id: <200102071930.MAA85736@rapidsite.vwh.net> From: Sarah Pollister Subject: Re: [IDS-1980911] VERIO AUP VIOLATION e550915 To: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for informing us about this. Sending unsolicited e-mail or making inappropriate commercial newsgroup posts from our web servers is strictly forbidden. It is also forbidden to promote web sites hosted on our servers in such mailings or postings. You may see our acceptable use policy here: http://www.iserver.com/aboutus/policies/server.html This user was warned and if this happens again, their account (frat-movie.com) will be disabled. Please let us know should you have any comments or questions. Sarah Hostmaster SECURE.NET/VerioWH ==== Excerpt from your message received 2/6/2001 10:00:18 MST ==== > > >Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) > by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id FAA07576 > for ; Sun, 28 Jan 2001 05:59:59 -0800 >(PST) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com >[207.113.159.21]) > by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id FAA12761 > for ; Sun, 28 Jan 2001 05:59:58 -0800 (PST) > (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from >mx1.FreeBSD.org ([216.136.204.125]) > by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id FAA03869 > for ; Sun, 28 Jan 2001 05:59:58 -0800 (PST) > (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from >hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) > by mx1.FreeBSD.org (Postfix) with ESMTP > id 6DECE6E2571; Sun, 28 Jan 2001 05:59:40 -0800 (PST) Received: by >hub.freebsd.org (Postfix, from userid 538) > id 1675037B402; Sun, 28 Jan 2001 05:59:39 -0800 (PST) Received: >from localhost (localhost [127.0.0.1]) > by hub.freebsd.org (Postfix) with SMTP > id E5D862E8191; Sun, 28 Jan 2001 05:59:38 -0800 (PST) Received: by >hub.freebsd.org (bulk_mailer v1.12); Sun, 28 Jan 2001 05:59:38 -0800 >Delivered-To: freebsd-current@freebsd.org Received: ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 12:42:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 07A6637B491 for ; Wed, 7 Feb 2001 12:42:24 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA23424; Thu, 8 Feb 2001 07:42:11 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01JZUYRL0CYO90ITCX@cim.alcatel.com.au>; Thu, 8 Feb 2001 07:42:10 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f17Kg8310048; Thu, 08 Feb 2001 07:42:08 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Thu, 08 Feb 2001 07:42:08 +1100 From: Peter Jeremy Subject: Re: ctm via mail NEWBIE In-reply-to: ; from rasa@phy.bg.ac.yu on Wed, Feb 07, 2001 at 08:13:31AM +0100 To: Rasa Karapandza Cc: current@FreeBSD.ORG Mail-followup-to: Rasa Karapandza , current@FreeBSD.ORG Message-id: <20010208074208.E90937@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Feb-07 08:13:31 +0100, Rasa Karapandza wrote: >I receive ctm-src current by e-mail, which I retrive using netscape. >I save message as plain text then I try uudecode and I alvays get no begin >line I tryed to edit file but I'm not able to get it work. CTM mail isn't uuencoded, which is probably your major problem. The e-mail body should begin as follows: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 CTM_MAIL BEGIN cvs-cur.6780.gz 1 1 H4sIAINA7jkCA+xba3Mbt5L9LP4K3NxUKQ+TxHMwQ2+2rMhyooolqyQld2u3tlx4DTkWyWFmhpa0 ... The e-mail messages should be fed into ctm_rmail to decode. I feed them into the following (directly from sendmail, but you could do it manually): /usr/local/bin/pgpv -f | \ /usr/sbin/ctm_rmail -f -v -p $CTM/pieces -d $CTM/deltas -l $CTM/log (Where $CTM is my ctm "home", with pieces and deltas as sub-directories). You can skip the pgpv if you don't want to check the signatures. I apply the decoded CTM's as a separate step with: # ctm_rmail -uv -b $CVSROOT -d $CTM/deltas Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 12:54:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id EF06737B491; Wed, 7 Feb 2001 12:54:20 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 07B4A31FE; Wed, 7 Feb 2001 20:54:20 +0000 (GMT) Date: Wed, 7 Feb 2001 20:54:20 +0000 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010207205420.C1656@tao.org.uk> Mail-Followup-To: Josef Karthauser , Dag-Erling Smorgrav , Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <200102062330.f16NUDN00646@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="NklN7DEeGtkPCoo3" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Wed, Feb 07, 2001 at 08:26:15PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NklN7DEeGtkPCoo3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote: > Brian Somers writes: > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm=20 > > for three days (probably about 36 hours excluding suspends) on a=20 > > 366MHz laptop with a ATA33 disk. >=20 > Would it be possible for someone experiencing this slowdown to try to > narrow down the day (or even the week) on which it occurred? I'll compile up a couple of kernels and see if I can hone it down. Joe --NklN7DEeGtkPCoo3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqBtfwACgkQXVIcjOaxUBb8MACdFdr0tweLa8LLOEGgT0DAB2gf fQUAni2uorGEGJNM34Y38zbYuFzsm+Ky =wz/e -----END PGP SIGNATURE----- --NklN7DEeGtkPCoo3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 12:56:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id E7F1A37B491; Wed, 7 Feb 2001 12:56:13 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 6F8FE326F; Wed, 7 Feb 2001 20:56:14 +0000 (GMT) Date: Wed, 7 Feb 2001 20:56:14 +0000 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010207205614.D1656@tao.org.uk> Mail-Followup-To: Josef Karthauser , Dag-Erling Smorgrav , Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <200102062330.f16NUDN00646@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cPi+lWm09sJ+d57q" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Wed, Feb 07, 2001 at 08:26:15PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --cPi+lWm09sJ+d57q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote: > Brian Somers writes: > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm=20 > > for three days (probably about 36 hours excluding suspends) on a=20 > > 366MHz laptop with a ATA33 disk. >=20 > Would it be possible for someone experiencing this slowdown to try to > narrow down the day (or even the week) on which it occurred? As I think about it it was definitity working before the symbol changes in libc/libc_r changed. Was that last week? No probably the week before. It was working fine last week, but I'm not sure which day's I updated the kernel. I'll try some builds. Joe --cPi+lWm09sJ+d57q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqBtm0ACgkQXVIcjOaxUBb4WgCeLZkI/Hmxn4Vs6KDJKX7KaCRj cP4An0wTO38MpezN7Gmwul+YMflBYytI =E5Lz -----END PGP SIGNATURE----- --cPi+lWm09sJ+d57q-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 13:28:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id B46B337B65D for ; Wed, 7 Feb 2001 13:28:21 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.2/8.11.1) id f17LQJC64785; Wed, 7 Feb 2001 13:26:19 -0800 (PST) (envelope-from obrien) Date: Wed, 7 Feb 2001 13:26:19 -0800 From: "David O'Brien" To: Peter Wemm Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: *_ROOT removed Message-ID: <20010207132618.A64612@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <033801c0910d$093451c0$0e00a8c0@neland.dk> <200102071428.f17ESgt64468@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102071428.f17ESgt64468@mobile.wemm.org>; from peter@netplex.com.au on Wed, Feb 07, 2001 at 06:28:42AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 07, 2001 at 06:28:42AM -0800, Peter Wemm wrote: > No, there wasn't one.. The commit message was pretty clear - You are > reading them, right? We usually do HEAD UP's for stuff that will break > people pretty badly or get them in trouble (eg: an unviable kernel if the > instructions are not followed). I thought we did them for any issue that can confuse or cause a lot of questions on this list... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 14:13:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 9DB9237B491 for ; Wed, 7 Feb 2001 14:13:37 -0800 (PST) Received: (qmail 2396 invoked by uid 1000); 7 Feb 2001 22:07:21 -0000 Date: Wed, 7 Feb 2001 23:07:20 +0100 From: Andrea Campi To: Jake Burkholder Cc: John Baldwin , current@FreeBSD.ORG, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010207230719.A534@webcom.it> References: <20010207164312.93440BAAF@cr66388-a.rchrd1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010207164312.93440BAAF@cr66388-a.rchrd1.on.wave.home.com>; from jburkholder0829@home.com on Wed, Feb 07, 2001 at 11:43:12AM -0500 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > panic: malloc(M_WAITOK) in interrupt context > > Debugger("panic") > > Stopped at Debugger+0x45: pushl %ebx > > db> trace > > Debugger(c02119a3) at Debugger+0x45 > > panic(....) > > malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a > > exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 > > kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend > > ithd_loop(0,c6623fa8) at ithd_loop+0x56 > > fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 > > fork_trampoline() at fork_trampoline+0x8 > > db> witness_list > > "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 > > > > Make sure you have intr_machdep.c version 1.47. > > revision 1.47 > date: 2001/01/28 17:20:11 Actually I have /intr_machdep.c/1.49/Mon Jan 29 11:57:26 2001/ But the differences shouldn't matter... Bye, Andrea -- Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 14:21:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2E5D537B67D for ; Wed, 7 Feb 2001 14:21:15 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f17ML6x17768; Wed, 7 Feb 2001 14:21:06 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f17MKhM13832; Wed, 7 Feb 2001 14:20:43 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010207124609.A594@webcom.it> Date: Wed, 07 Feb 2001 14:20:43 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Feb-01 Andrea Campi wrote: > Running a kernel I got with this: > >> >> cvs co -D"2001-01-30" src/sys >> > > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00 > > I get: > > panic: malloc(M_WAITOK) in interrupt context > Debugger("panic") > Stopped at Debugger+0x45: pushl %ebx > db> trace > Debugger(c02119a3) at Debugger+0x45 > panic(....) > malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a > exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 > kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend > ithd_loop(0,c6623fa8) at ithd_loop+0x56 > fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 > fork_trampoline() at fork_trampoline+0x8 > db> witness_list > "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 Erm, ithd_loop() doesn't call kthread_suspend(). *sigh*. Something else is rather messed up here I'm afraid. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 15: 1:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 4AD9B37B6C3 for ; Wed, 7 Feb 2001 15:01:19 -0800 (PST) Received: (qmail 3018 invoked by uid 1000); 7 Feb 2001 22:55:02 -0000 Date: Wed, 7 Feb 2001 23:55:01 +0100 From: Andrea Campi To: John Baldwin Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010207235459.B534@webcom.it> References: <20010207124609.A594@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Wed, Feb 07, 2001 at 02:20:43PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 07, 2001 at 02:20:43PM -0800, John Baldwin wrote: > > On 07-Feb-01 Andrea Campi wrote: > > Running a kernel I got with this: > > > >> > >> cvs co -D"2001-01-30" src/sys > >> > > > > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00 > > > > I get: > > > > panic: malloc(M_WAITOK) in interrupt context > > Debugger("panic") > > Stopped at Debugger+0x45: pushl %ebx > > db> trace > > Debugger(c02119a3) at Debugger+0x45 > > panic(....) > > malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a > > exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 > > kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend > > ithd_loop(0,c6623fa8) at ithd_loop+0x56 > > fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 > > fork_trampoline() at fork_trampoline+0x8 > > db> witness_list > > "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 > > Erm, ithd_loop() doesn't call kthread_suspend(). *sigh*. Something > else is rather messed up here I'm afraid. So I thought... also, kthread_suspend() doesn't call exit1(), does it? No matter what, ithd_loop() calls kthread_exit() which calls exit1() which happily MALLOC's with M_WAITOK... Something is messed up, indeed, but it seems to be a case of WISIWYG instead of what I mean... ;-) Also, I think this issue has been there longer but it might have been masked by me not having INVARIANTS defined at times (am I correct to read the code as not panicing #ifndef INVARIANTS?). So I am going back before this revision: revision 1.78 date: 2001/01/21 19:25:07; author: jake; state: Exp; lines: +3 -2 Make intr_nesting_level per-process, rather than per-cpu. Setup interrupt threads to run with it always >= 1, so that malloc can detect M_WAITOK from "interrupt" context. This is also necessary in order to context switch from sched_ithd() directly. Re: the strace db trace above, is it possible that it might be because I have: CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 in make.conf? I put these after somebody mentioned using it here... Bye, Andrea -- Weird enough for government work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 15:13:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B84C637B6C8 for ; Wed, 7 Feb 2001 15:13:12 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f17ND0002020; Wed, 7 Feb 2001 15:13:00 -0800 (PST) Date: Wed, 7 Feb 2001 15:13:00 -0800 From: Alfred Perlstein To: Peter Wemm Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: *_ROOT removed Message-ID: <20010207151300.S26076@fw.wintelcom.net> References: <033801c0910d$093451c0$0e00a8c0@neland.dk> <200102071428.f17ESgt64468@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102071428.f17ESgt64468@mobile.wemm.org>; from peter@netplex.com.au on Wed, Feb 07, 2001 at 06:28:42AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Peter Wemm [010207 06:29] wrote: > "Leif Neland" wrote: > > While the error-messages are clear, I don't remember seeing any heads-up, or > mentioning of this in UPDATING > > > > Or is it just me...? > > No, there wasn't one.. The commit message was pretty clear - You are > reading them, right? We usually do HEAD UP's for stuff that will break > people pretty badly or get them in trouble (eg: an unviable kernel if the > instructions are not followed). > > At least you got the message. buildkernel would have silently ignored this > up until recently. Does this mean that 'FFS' isn't optional anymore? I mean it probably hasn't been (or never was) but the intention was that to build 4.4BSD you needed _either_ UFS or INET, but you could ditch either one and still build a kernel. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 15:13:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 0885137B6C6; Wed, 7 Feb 2001 15:13:07 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id D53AF311F; Wed, 7 Feb 2001 23:13:06 +0000 (GMT) Date: Wed, 7 Feb 2001 23:13:06 +0000 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010207231306.B972@tao.org.uk> Mail-Followup-To: Josef Karthauser , Dag-Erling Smorgrav , Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org References: <200102062330.f16NUDN00646@hak.lan.Awfulhak.org> <20010207205614.D1656@tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="rJwd6BRFiFCcLxzm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010207205614.D1656@tao.org.uk>; from joe@tao.org.uk on Wed, Feb 07, 2001 at 08:56:14PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --rJwd6BRFiFCcLxzm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 07, 2001 at 08:56:14PM +0000, Josef Karthauser wrote: > On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote: > > Brian Somers writes: > > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm=20 > > > for three days (probably about 36 hours excluding suspends) on a=20 > > > 366MHz laptop with a ATA33 disk. > >=20 > > Would it be possible for someone experiencing this slowdown to try to > > narrow down the day (or even the week) on which it occurred? >=20 > As I think about it it was definitity working before the symbol changes > in libc/libc_r changed. Was that last week? No probably the week > before. It was working fine last week, but I'm not sure which day's I > updated the kernel. >=20 > I'll try some builds. Ok. The problem definitely began between -D2001-01-29 and -D2001-01-30. I'll try and binary chop to workout what caused it. Joe --rJwd6BRFiFCcLxzm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqB1oEACgkQXVIcjOaxUBZmLACdFs5Z49cd+aK5jsWqtNO+hj/8 U+UAoKFW6ho76jA2Q5GiNKJHY0s5eCZf =a5nW -----END PGP SIGNATURE----- --rJwd6BRFiFCcLxzm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 15:15:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 5FB2137B6C3 for ; Wed, 7 Feb 2001 15:14:53 -0800 (PST) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.2/8.11.2) id f17NEkY12617; Wed, 7 Feb 2001 18:14:46 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.6-3 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010207235459.B534@webcom.it> Date: Wed, 07 Feb 2001 18:14:46 -0500 (EST) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Re: the strace db trace above, is it possible that it might be because I > have: > > CFLAGS ?= -O -pipe -mcpu=i686 -march=i686 > COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686 No, I was getting the same panic with the kernel, compiled with stock flags. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 15:54: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id CE40A37B69D; Wed, 7 Feb 2001 15:53:42 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id C22E2BAB0; Wed, 7 Feb 2001 18:53:41 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: Andrea Campi Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup In-Reply-To: Message from Andrea Campi of "Wed, 07 Feb 2001 23:55:01 +0100." <20010207235459.B534@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Feb 2001 18:53:41 -0500 From: Jake Burkholder Message-Id: <20010207235341.C22E2BAB0@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Feb 07, 2001 at 02:20:43PM -0800, John Baldwin wrote: > > > > On 07-Feb-01 Andrea Campi wrote: > > > Running a kernel I got with this: > > > > > >> > > >> cvs co -D"2001-01-30" src/sys > > >> > > > > > > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00 > > > > > > I get: > > > > > > panic: malloc(M_WAITOK) in interrupt context > > > Debugger("panic") > > > Stopped at Debugger+0x45: pushl %ebx > > > db> trace > > > Debugger(c02119a3) at Debugger+0x45 > > > panic(....) > > > malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a > > > exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 > > > kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend > > > ithd_loop(0,c6623fa8) at ithd_loop+0x56 > > > fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 > > > fork_trampoline() at fork_trampoline+0x8 > > > db> witness_list > > > "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 > > > > Erm, ithd_loop() doesn't call kthread_suspend(). *sigh*. Something > > else is rather messed up here I'm afraid. > > So I thought... also, kthread_suspend() doesn't call exit1(), does it? > > > No matter what, ithd_loop() calls kthread_exit() which calls exit1() > which happily MALLOC's with M_WAITOK... > Something is messed up, indeed, but it seems to be a case of WISIWYG instead > of what I mean... ;-) > > > Also, I think this issue has been there longer but it might have been masked > by me not having INVARIANTS defined at times (am I correct to read the code as > not panicing #ifndef INVARIANTS?). So I am going back before this revision: > > revision 1.78 > date: 2001/01/21 19:25:07; author: jake; state: Exp; lines: +3 -2 > Make intr_nesting_level per-process, rather than per-cpu. Setup > interrupt threads to run with it always >= 1, so that malloc can > detect M_WAITOK from "interrupt" context. This is also necessary > in order to context switch from sched_ithd() directly. > This is why you're getting the panic in exit1(), but I thought I fixed this in intr_machdep.c version 1.47. revision 1.47 date: 2001/01/28 17:20:11; author: jake; state: Exp; lines: +2 -1 Clear intr_nesting_level when an interrupt thread has no more handlers and wants to exit, so it doesn't panic in exit1() which malloc()s with M_WAITOK. Reported by: Bob Bishop To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16: 3:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 190C237B6A4 for ; Wed, 7 Feb 2001 16:03:33 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1802p996815; Wed, 7 Feb 2001 17:03:00 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102080003.f1802p996815@harmony.village.org> To: farid.hajji@ob.kamp.net Subject: Re: Strange fopen() behaviour Cc: brian@Awfulhak.org, domi@saargate.de, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 07 Feb 2001 00:34:18 +0100." <200102062334.f16NYI229243@mail-ob.kamp.net> References: <200102062334.f16NYI229243@mail-ob.kamp.net> <200102060324.f163O0610286@hak.lan.Awfulhak.org> Date: Wed, 07 Feb 2001 17:02:51 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102062334.f16NYI229243@mail-ob.kamp.net> Farid Hajji writes: : > dev.lan.Awfulhak.org kernel log messages: : > > microuptime() went backwards (18415.166882 -> 18415.158249) : > > microuptime() went backwards (18490.192910 -> 18490.187579) : > > microuptime() went backwards (19572.644000 -> 19572.638237) : > > microuptime() went backwards (19878.637972 -> 19878.637330) : > > microuptime() went backwards (20043.869158 -> 20043.868971) : > > microuptime() went backwards (20074.159108 -> 20074.152253) : > > microuptime() went backwards (20210.078270 -> 20210.072448) : I'm also seing this as of CURRENT-2001-01-27 and later: : pcm1: hwptr went backwards 36 -> 0 : pcm1: hwptr went backwards 40 -> 16 : pcm1: hwptr went backwards 2084 -> 2048 : pcm1: hwptr went backwards 2092 -> 2064 That's different. It is a sound thing that's related to the really crappy interrupt performance that we have in current. You'll likely see it as far back as october or so (I was seeing them at BSDCON). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16: 7:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from sonyplaystations2.com (fll-VoDSL54-cust107.mpowercom.net [208.57.54.107]) by hub.freebsd.org (Postfix) with SMTP id 599C237B65D for ; Wed, 7 Feb 2001 16:07:19 -0800 (PST) From: To: current@freebsd.org Subject: How's it going? Date: Wed, 7 Feb 2001 18:54:41 Message-Id: <30.900104.8524@sonyplaystations2.com> Reply-To: info@chocolatejungle.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looking for the finest handmade gourmet chocolate for that special someone? http://chocolatejungle.com Never stored, made fresh everyday, shipped anywhere on the same day you order it! "Chocolate... 'cause its a jungle out there!" [You are receiving this email because you opted for specials on this specific subject. If you wish to be removed from future mailings, reply to "chocolatejungle@yahoo.com".] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16:34: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id F252A37B401; Wed, 7 Feb 2001 16:33:40 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Feb 2001 00:33:39 +0000 (GMT) To: John Baldwin Cc: Andrea Campi , Jim Bloom , "Crist J. Clark" , current@FreeBSD.org, iedowse@maths.tcd.ie Subject: Re: Kernel Panic from Yesterday's CVSup In-Reply-To: Your message of "Wed, 07 Feb 2001 14:20:43 PST." Date: Thu, 08 Feb 2001 00:33:38 +0000 From: Ian Dowse Message-ID: <200102080033.aa50630@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: >> malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a >> exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 >> kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend >> ithd_loop(0,c6623fa8) at ithd_loop+0x56 >> fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 >> fork_trampoline() at fork_trampoline+0x8 >> db> witness_list >> "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 > >Erm, ithd_loop() doesn't call kthread_suspend(). *sigh*. Something >else is rather messed up here I'm afraid. Note that the return address into kthread_suspend is kthread_suspend+0x0. Since the call to exit1() in kthread_exit is the very last operation in kthread_exit, you'd expect the return address on the stack to be at the start of the next function... Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16:34:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 4338D37B65D for ; Wed, 7 Feb 2001 16:34:09 -0800 (PST) Received: (qmail 12302 invoked by uid 1000); 8 Feb 2001 00:27:49 -0000 Date: Thu, 8 Feb 2001 01:27:45 +0100 From: Andrea Campi To: Jake Burkholder Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010208012740.A3525@webcom.it> References: <20010207235341.C22E2BAB0@cr66388-a.rchrd1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010207235341.C22E2BAB0@cr66388-a.rchrd1.on.wave.home.com>; from jburkholder0829@home.com on Wed, Feb 07, 2001 at 06:53:41PM -0500 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is why you're getting the panic in exit1(), but I thought I fixed > this in intr_machdep.c version 1.47. > > revision 1.47 > date: 2001/01/28 17:20:11; author: jake; state: Exp; lines: +2 -1 > Clear intr_nesting_level when an interrupt thread has no more > handlers and wants to exit, so it doesn't panic in exit1() > which malloc()s with M_WAITOK. Well, either it fails to deliver, but then somebody else would have seen it, or it's in some way tied to my hw setup. Could there be a race, an interrupt firing at a very bad time? Shouldn't be a problem if locking is correct... Bah... any idea? Andrea -- The dark ages were caused by the Y1K problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16:41:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D0EE337B4EC for ; Wed, 7 Feb 2001 16:41:20 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f180eax21380; Wed, 7 Feb 2001 16:40:36 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f180eDD15628; Wed, 7 Feb 2001 16:40:13 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010207235459.B534@webcom.it> Date: Wed, 07 Feb 2001 16:40:13 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Feb-01 Andrea Campi wrote: > On Wed, Feb 07, 2001 at 02:20:43PM -0800, John Baldwin wrote: >> >> On 07-Feb-01 Andrea Campi wrote: >> > Running a kernel I got with this: >> > >> >> >> >> cvs co -D"2001-01-30" src/sys >> >> >> > >> > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00 >> > >> > I get: >> > >> > panic: malloc(M_WAITOK) in interrupt context >> > Debugger("panic") >> > Stopped at Debugger+0x45: pushl %ebx >> > db> trace >> > Debugger(c02119a3) at Debugger+0x45 >> > panic(....) >> > malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a >> > exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1 >> > kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend >> > ithd_loop(0,c6623fa8) at ithd_loop+0x56 >> > fork_exit(c01fc7fc,0,c6623fa8) at fork_exit+0x8 >> > fork_trampoline() at fork_trampoline+0x8 >> > db> witness_list >> > "Giant" (0xc0279a40) locked at ../../i386/isa/ithread.c:162 >> >> Erm, ithd_loop() doesn't call kthread_suspend(). *sigh*. Something >> else is rather messed up here I'm afraid. > > So I thought... also, kthread_suspend() doesn't call exit1(), does it? > > > No matter what, ithd_loop() calls kthread_exit() which calls exit1() > which happily MALLOC's with M_WAITOK... > Something is messed up, indeed, but it seems to be a case of WISIWYG instead > of what I mean... ;-) > > > Also, I think this issue has been there longer but it might have been masked > by me not having INVARIANTS defined at times (am I correct to read the code > as > not panicing #ifndef INVARIANTS?). So I am going back before this revision: > > revision 1.78 > date: 2001/01/21 19:25:07; author: jake; state: Exp; lines: +3 -2 > Make intr_nesting_level per-process, rather than per-cpu. Setup > interrupt threads to run with it always >= 1, so that malloc can > detect M_WAITOK from "interrupt" context. This is also necessary > in order to context switch from sched_ithd() directly. Yes, the intr_nesting_level needs to be dropped before calling kthread_exit(). I have this fixed in a different manner locally. You can try that to see if it gets farther. However, your problems with lpr are a known problem and one that is in the process of being fixed. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16:47:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id D7C7637B401 for ; Wed, 7 Feb 2001 16:47:33 -0800 (PST) Received: (qmail 14490 invoked by uid 1000); 8 Feb 2001 00:41:15 -0000 Date: Thu, 8 Feb 2001 01:41:12 +0100 From: Andrea Campi To: John Baldwin Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010208014108.A13541@webcom.it> References: <20010207235459.B534@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Wed, Feb 07, 2001 at 04:40:13PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes, the intr_nesting_level needs to be dropped before calling kthread_exit(). > I have this fixed in a different manner locally. You can try that to see if it > gets farther. However, your problems with lpr are a known problem and one that > is in the process of being fixed. No that was the other guy. My problem is when ejecting a pccard ethernet card, which of course is the only device on that irq, triggering this bug which is probably much less exercised on desktops (another good argument for keeping current on my laptop). This said, I'd love to try your patch to decrement intr_nesting_level and see what happens. Bye, andrea -- To boldly go where I surely don't belong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16:57:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E79437B65D for ; Wed, 7 Feb 2001 16:56:52 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f180upX99660 for freebsd-current@freebsd.org; Thu, 8 Feb 2001 01:56:51 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.1/8.11.0) with ESMTP id f180uBx58662 for ; Thu, 8 Feb 2001 01:56:12 +0100 (CET) (envelope-from leifn@neland.dk) Date: Thu, 8 Feb 2001 01:56:11 +0100 (CET) From: Leif Neland To: freebsd-current@freebsd.org Subject: pkg_update Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems pkg_update is only usable when installing from packages, not from ports. Even when I first do a make package, and then try a pkg_update it appears it does not work correctly, as it wants to uninstall the latest version before it reinstalls it. Could pkg_update be a target in bsd.port.mk? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 16:59:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E849637B4EC for ; Wed, 7 Feb 2001 16:59:31 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f180xNx21942; Wed, 7 Feb 2001 16:59:23 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f180x0a15852; Wed, 7 Feb 2001 16:59:00 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010208014108.A13541@webcom.it> Date: Wed, 07 Feb 2001 16:59:00 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Feb-01 Andrea Campi wrote: >> >> Yes, the intr_nesting_level needs to be dropped before calling >> kthread_exit(). >> I have this fixed in a different manner locally. You can try that to see if >> it >> gets farther. However, your problems with lpr are a known problem and one >> that >> is in the process of being fixed. > > No that was the other guy. My problem is when ejecting a pccard ethernet > card, > which of course is the only device on that irq, triggering this bug which is > probably much less exercised on desktops (another good argument for keeping > current on my laptop). > > This said, I'd love to try your patch to decrement intr_nesting_level and see > what happens. My patches may help with this, but they are a lot more than just a single change, they are an overhaul of the interrupt threads code. :) If you are really curious, you can find them at http://www.FreeBSD.org/~jhb/patches/sys.patch. Currently, however, they reduce the system to a crawl. Well, at least console I/O feels like a 2400 baud modem. I'm even losing characters on the keyboard. :( -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17: 7:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.port.ru (mx2.port.ru [194.67.23.33]) by hub.freebsd.org (Postfix) with ESMTP id 1099937B491; Wed, 7 Feb 2001 17:07:20 -0800 (PST) Received: from adsl-141-154-118-11.bostma.adsl.bellatlantic.net ([141.154.118.11] helo=kan.dnsalias.net) by smtp2.port.ru with esmtp (Exim 3.14 #87) id 14QfYL-0008qk-00; Thu, 08 Feb 2001 04:07:18 +0300 Received: (from kan@localhost) by kan.dnsalias.net (8.11.2/8.11.2) id f1817Cm01329; Wed, 7 Feb 2001 20:07:12 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.6 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Feb 2001 20:07:12 -0500 (EST) From: "Alexander N. Kabaev" To: John Baldwin Subject: Re: Kernel Panic from Yesterday's CVSup Cc: freebsd-current@FreeBSD.ORG, Andrea Campi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, your problems with lpr are a known problem and one > that is in the process of being fixed. That was me who reported lpr problems in this thread. I just found it curious that Andrea's panics look absolutely identical to ones I am getting here when attempting to use lpr. Do you really think that is a pure coincidence? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17:13:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4439737B4EC for ; Wed, 7 Feb 2001 17:13:10 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f181D1x22579; Wed, 7 Feb 2001 17:13:01 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f181Ccs16046; Wed, 7 Feb 2001 17:12:38 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Feb 2001 17:12:38 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: "Alexander N. Kabaev" Subject: Re: Kernel Panic from Yesterday's CVSup Cc: Andrea Campi , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Feb-01 Alexander N. Kabaev wrote: >> However, your problems with lpr are a known problem and one >> that is in the process of being fixed. > That was me who reported lpr problems in this thread. I just found it curious > that Andrea's panics look absolutely identical to ones I am getting here when > attempting to use lpr. Do you really think that is a pure coincidence? No, I'm hoping they are both related to a race between removing an ithread and adding a new one, in which case my patches will serve to fix this. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17:25:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 3B0F637B491 for ; Wed, 7 Feb 2001 17:25:33 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f181PRt70396; Wed, 7 Feb 2001 17:25:27 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102080125.f181PRt70396@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alfred Perlstein Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: *_ROOT removed In-Reply-To: <20010207151300.S26076@fw.wintelcom.net> Date: Wed, 07 Feb 2001 17:25:27 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Peter Wemm [010207 06:29] wrote: > > "Leif Neland" wrote: > > > While the error-messages are clear, I don't remember seeing any heads-up, or > > mentioning of this in UPDATING > > > > > > Or is it just me...? > > > > No, there wasn't one.. The commit message was pretty clear - You are > > reading them, right? We usually do HEAD UP's for stuff that will break > > people pretty badly or get them in trouble (eg: an unviable kernel if the > > instructions are not followed). > > > > At least you got the message. buildkernel would have silently ignored this > > up until recently. > > Does this mean that 'FFS' isn't optional anymore? I mean it probably > hasn't been (or never was) but the intention was that to build 4.4BSD > you needed _either_ UFS or INET, but you could ditch either one and > still build a kernel. No, FFS_ROOT was unused. We have a generic mountroot mechanism, so we no longer needed to compile the "special" FFS-specific version of the code into autoconf.c. FFS is still optional. For i386 FFS_ROOT and CD9660_ROOT did nothing, and on alpha/ia64 it did something that was more likely to cause problems than help. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17:26: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 6067237B4EC; Wed, 7 Feb 2001 17:25:42 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id MAA06100; Thu, 8 Feb 2001 12:25:17 +1100 Date: Thu, 8 Feb 2001 12:24:55 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Josef Karthauser Cc: Dag-Erling Smorgrav , Brian Somers , Julian Elischer , freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: <20010207231306.B972@tao.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Feb 2001, Josef Karthauser wrote: > On Wed, Feb 07, 2001 at 08:56:14PM +0000, Josef Karthauser wrote: > > On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote: > > > Brian Somers writes: > > > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm > > > > for three days (probably about 36 hours excluding suspends) on a > > > > 366MHz laptop with a ATA33 disk. > > > > > > Would it be possible for someone experiencing this slowdown to try to > > > narrow down the day (or even the week) on which it occurred? > > > > As I think about it it was definitity working before the symbol changes > > in libc/libc_r changed. Was that last week? No probably the week > > before. It was working fine last week, but I'm not sure which day's I > > updated the kernel. > > > > I'll try some builds. > > Ok. The problem definitely began between -D2001-01-29 and -D2001-01-30. > I'll try and binary chop to workout what caused it. If you have ata disks, try "options ATA_ENABLE_WC". Nothing else has changed significantly in this period. I don't know how this would effect vmware boot speeds. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17:26:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 9D09C37B6B1 for ; Wed, 7 Feb 2001 17:25:52 -0800 (PST) Received: (qmail 19183 invoked by uid 1000); 8 Feb 2001 01:19:34 -0000 Date: Thu, 8 Feb 2001 02:19:33 +0100 From: Andrea Campi To: John Baldwin Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010208021930.C13541@webcom.it> References: <20010208014108.A13541@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Wed, Feb 07, 2001 at 04:59:00PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My patches may help with this, but they are a lot more than just a single > change, they are an overhaul of the interrupt threads code. :) If you are > really curious, you can find them at > http://www.FreeBSD.org/~jhb/patches/sys.patch. Currently, however, they reduce > the system to a crawl. Well, at least console I/O feels like a 2400 baud > modem. I'm even losing characters on the keyboard. :( Sort of killing a mosquito with a missile ;-) Seriously, I will try your patch to confirm it works, then I'll go back to a regular -current kernel and live without ejecting the card... While I was reading your patch I was wondering: what's the situation with IRQ sharing between PCCard and other devices? Since you're doing such a massive rework, wouldn't this be a good time to also deal with this if possible (well not now of course, after your patch is confirmed ok and committed)? In case I was not clear: at the moment pccard and cardbus devices can't share IRQ line with any kind of other devices. The best explanation of this mentioned only pccard and said it was handled as ISA so you coulnd't share, but in theory it was possible to handle pccard in a different way. And cardbus shouldn't be a problem at all I think. Bye, Andrea -- Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17:34:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B5D5537B69C for ; Wed, 7 Feb 2001 17:34:27 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f181YKG10917; Wed, 7 Feb 2001 17:34:20 -0800 (PST) Date: Wed, 7 Feb 2001 17:34:20 -0800 From: Alfred Perlstein To: Peter Wemm Cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: *_ROOT removed Message-ID: <20010207173420.C26076@fw.wintelcom.net> References: <20010207151300.S26076@fw.wintelcom.net> <200102080125.f181PRt70396@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102080125.f181PRt70396@mobile.wemm.org>; from peter@netplex.com.au on Wed, Feb 07, 2001 at 05:25:27PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Peter Wemm [010207 17:25] wrote: > Alfred Perlstein wrote: > > * Peter Wemm [010207 06:29] wrote: > > > "Leif Neland" wrote: > > > > While the error-messages are clear, I don't remember seeing any heads-up, > or > > > mentioning of this in UPDATING > > > > > > > > Or is it just me...? > > > > > > No, there wasn't one.. The commit message was pretty clear - You are > > > reading them, right? We usually do HEAD UP's for stuff that will break > > > people pretty badly or get them in trouble (eg: an unviable kernel if the > > > instructions are not followed). > > > > > > At least you got the message. buildkernel would have silently ignored this > > > up until recently. > > > > Does this mean that 'FFS' isn't optional anymore? I mean it probably > > hasn't been (or never was) but the intention was that to build 4.4BSD > > you needed _either_ UFS or INET, but you could ditch either one and > > still build a kernel. > > No, FFS_ROOT was unused. We have a generic mountroot mechanism, so we no > longer needed to compile the "special" FFS-specific version of the code > into autoconf.c. FFS is still optional. For i386 FFS_ROOT and CD9660_ROOT > did nothing, and on alpha/ia64 it did something that was more likely to > cause problems than help. Sorry, I should have looked at the delta but the cvs message wasn't included in the gripe. thanks for clearing it up. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17:47: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E8A1037B401 for ; Wed, 7 Feb 2001 17:46:41 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f181k1x23530; Wed, 7 Feb 2001 17:46:01 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f181jci16457; Wed, 7 Feb 2001 17:45:38 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010208021930.C13541@webcom.it> Date: Wed, 07 Feb 2001 17:45:38 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Feb-01 Andrea Campi wrote: >> >> My patches may help with this, but they are a lot more than just a single >> change, they are an overhaul of the interrupt threads code. :) If you are >> really curious, you can find them at >> http://www.FreeBSD.org/~jhb/patches/sys.patch. Currently, however, they >> reduce >> the system to a crawl. Well, at least console I/O feels like a 2400 baud >> modem. I'm even losing characters on the keyboard. :( > > Sort of killing a mosquito with a missile ;-) > > Seriously, I will try your patch to confirm it works, then I'll go back > to a regular -current kernel and live without ejecting the card... Keep your kernel.old around. Trust me, the new kernel won't be very usable. :) > In case I was not clear: at the moment pccard and cardbus devices can't > share IRQ line with any kind of other devices. The best explanation of > this mentioned only pccard and said it was handled as ISA so you coulnd't > share, but in theory it was possible to handle pccard in a different way. > And cardbus shouldn't be a problem at all I think. cardbus already shares. pccard under NEWCARD shares as well. My work is at a lower-level than that though, that is in the pccard/cardbus specific code. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 17:57: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.239.10.243]) by hub.freebsd.org (Postfix) with SMTP id 4A88137B401 for ; Wed, 7 Feb 2001 17:56:43 -0800 (PST) Received: (qmail 20505 invoked by uid 1000); 8 Feb 2001 01:50:25 -0000 Date: Thu, 8 Feb 2001 02:50:24 +0100 From: Andrea Campi To: John Baldwin Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010208025022.F13541@webcom.it> References: <20010208021930.C13541@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Wed, Feb 07, 2001 at 05:45:38PM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Sort of killing a mosquito with a missile ;-) > > > > Seriously, I will try your patch to confirm it works, then I'll go back > > to a regular -current kernel and live without ejecting the card... > > Keep your kernel.old around. Trust me, the new kernel won't be very usable. > :) Better yet, I always keep a /boot/kernel.safe/ for those times when I compile a lot of different kernels so that I don't have to remember to save a working one ;-) Seriously, that's ok, I only want to check if I get the same panic. And give feedback of course. > > In case I was not clear: at the moment pccard and cardbus devices can't > > share IRQ line with any kind of other devices. The best explanation of > > this mentioned only pccard and said it was handled as ISA so you coulnd't > > share, but in theory it was possible to handle pccard in a different way. > > And cardbus shouldn't be a problem at all I think. > > cardbus already shares. pccard under NEWCARD shares as well. My work is at a > lower-level than that though, that is in the pccard/cardbus specific code. cardbus gives me some problem I didn't investigate yes in details, but pccard - I tried but got nowhere. Both drivers probe and attach (ep0 on pccard, csa on motherboard), so I have pcic-pci0 and sound card sharing IRQ 11, ep0 on IRQ 3. But if I try playing anything I get no IRQ from the sound card... Ok I will leave this for the future... ;-) Bye, Andrea -- The computer revolution is over. The computers won. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 18:13:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns1.pywell.com (ns1.pywell.com [142.59.207.115]) by hub.freebsd.org (Postfix) with SMTP id C561E37B4EC for ; Wed, 7 Feb 2001 18:13:40 -0800 (PST) Received: (qmail 61549 invoked from network); 7 Feb 2001 19:13:13 -0000 Received: from 24.68.91.180.on.wave.home.com (HELO zoltan) (24.68.91.180) by ns1.pywell.com with SMTP; 7 Feb 2001 19:13:13 -0000 Message-ID: <000c01c09174$d4d0c720$4500a8c0@zoltan> From: "Zoltan Kraus" To: Subject: Date: Wed, 7 Feb 2001 21:14:12 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01C0914A.EB681C10" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0009_01C0914A.EB681C10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe ------=_NextPart_000_0009_01C0914A.EB681C10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe
------=_NextPart_000_0009_01C0914A.EB681C10-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 18:23:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 762B937B401 for ; Wed, 7 Feb 2001 18:22:59 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id C50E05762A; Wed, 7 Feb 2001 20:23:35 -0600 (CST) Date: Wed, 7 Feb 2001 20:23:35 -0600 From: "Michael C . Wu" To: Leif Neland Cc: freebsd-current@freebsd.org Subject: Re: pkg_update Message-ID: <20010207202335.C20454@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , Leif Neland , freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from leifn@neland.dk on Thu, Feb 08, 2001 at 01:56:11AM +0100 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 08, 2001 at 01:56:11AM +0100, Leif Neland scribbled: | It seems pkg_update is only usable when installing from packages, not from | ports. Because it is a package update system. If you want to update from the ports, use 'pkg_version -c |sh' | Even when I first do a make package, and then try a pkg_update it appears | it does not work correctly, as it wants to uninstall the latest version | before it reinstalls it. | | Could pkg_update be a target in bsd.port.mk? No, use the above. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 19: 7:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 74E8637B699; Wed, 7 Feb 2001 19:07:33 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f18376h23008; Wed, 7 Feb 2001 22:07:07 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 7 Feb 2001 22:07:06 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dag-Erling Smorgrav Cc: Brian Somers , Julian Elischer , Bruce Evans , Josef Karthauser , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Feb 2001, Dag-Erling Smorgrav wrote: > Brian Somers writes: > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm > > for three days (probably about 36 hours excluding suspends) on a > > 366MHz laptop with a ATA33 disk. > > Would it be possible for someone experiencing this slowdown to try to > narrow down the day (or even the week) on which it occurred? I've experienced a substantial slowdown in VMware since bumping forwards from -STABLE on my workstation. As I recently commented on -emulation, I've also been experiencing 30-40 second hangs of the system during VMware startup and occasional serious slowdown while running, which may be related to the fairly intensive VM activity for page wiring and the like, or possible poor interaction with the ATA driver. I also get messages on the order of the following: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 2696, size: 4096 And have heard that others have started getting them also, although don't have confirmation of that. It may be that things need retuning a bit in -CURRENT, or that we need to wait for SMPng to do some pushdown of locks. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 19:55: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C43F137B491 for ; Wed, 7 Feb 2001 19:54:42 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA23654; Thu, 8 Feb 2001 14:54:20 +1100 Date: Thu, 8 Feb 2001 14:53:59 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Peter Wemm Cc: Alfred Perlstein , Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: *_ROOT removed In-Reply-To: <200102080125.f181PRt70396@mobile.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Feb 2001, Peter Wemm wrote: > Alfred Perlstein wrote: > > Does this mean that 'FFS' isn't optional anymore? I mean it probably > > hasn't been (or never was) but the intention was that to build 4.4BSD > > you needed _either_ UFS or INET, but you could ditch either one and > > still build a kernel. > > No, FFS_ROOT was unused. We have a generic mountroot mechanism, so we no > longer needed to compile the "special" FFS-specific version of the code > into autoconf.c. FFS is still optional. For i386 FFS_ROOT and CD9660_ROOT > did nothing, and on alpha/ia64 it did something that was more likely to > cause problems than help. Except the optionality of FFS is broken. Leaving it out gives: ufs_lookup.o: In function `ufs_dirremove': ufs_lookup.o(.text+0x125e): undefined reference to `ffs_snapgone' ufs_lookup.o: In function `ufs_dirrewrite': ufs_lookup.o(.text+0x1349): undefined reference to `ffs_snapgone' ffs_snapgone is in an optional file but is referenced in a standard file. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 21: 3:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C44F837B401 for ; Wed, 7 Feb 2001 21:03:35 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1853J998701; Wed, 7 Feb 2001 22:03:19 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102080503.f1853J998701@harmony.village.org> To: Peter Wemm Subject: Re: *_ROOT removed Cc: Alfred Perlstein , Leif Neland , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 07 Feb 2001 17:25:27 PST." <200102080125.f181PRt70396@mobile.wemm.org> References: <200102080125.f181PRt70396@mobile.wemm.org> Date: Wed, 07 Feb 2001 22:03:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102080125.f181PRt70396@mobile.wemm.org> Peter Wemm writes: : No, FFS_ROOT was unused. We have a generic mountroot mechanism, so we no : longer needed to compile the "special" FFS-specific version of the code : into autoconf.c. FFS is still optional. For i386 FFS_ROOT and CD9660_ROOT : did nothing, and on alpha/ia64 it did something that was more likely to : cause problems than help. Then why was FFS moved to opt_dontuse.h? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 21: 7:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 88B4E37B503; Wed, 7 Feb 2001 21:07:20 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1857C998723; Wed, 7 Feb 2001 22:07:12 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102080507.f1857C998723@harmony.village.org> To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Feb 2001 02:19:33 +0100." <20010208021930.C13541@webcom.it> References: <20010208021930.C13541@webcom.it> <20010208014108.A13541@webcom.it> Date: Wed, 07 Feb 2001 22:07:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010208021930.C13541@webcom.it> Andrea Campi writes: : While I was reading your patch I was wondering: what's the situation with : IRQ sharing between PCCard and other devices? Since you're doing such a : massive rework, wouldn't this be a good time to also deal with this if : possible (well not now of course, after your patch is confirmed ok and : committed)? Sharing of IRQ between PCCARDs is not possible at the hardware level, unless your bridge supports it. OLDCARD only supports the legacy mode, so it isn't possible to share interrupts. NEWCARD supports cardbus bridges, which support sharing of interrupts in a very limited sense, but good enough for our purposes. : In case I was not clear: at the moment pccard and cardbus devices can't : share IRQ line with any kind of other devices. The best explanation of : this mentioned only pccard and said it was handled as ISA so you coulnd't : share, but in theory it was possible to handle pccard in a different way. : And cardbus shouldn't be a problem at all I think. ISA bus cannot share interrupts at all. Full stop[*]. Most pccard/cardbus bridges operate in a mode where they use ISA interrupts, so cannot share interrupts at all. The hardware just won't work if you try. NEWCARD tries to kick the cardbus bridge into full PCI mode, where you can share interrupts, since all the interrupts are going through the PCI hardware chain which does support interrupt sharing. Warner [*] Special, oddball cards can be made to support sharing. Those aren't relevant here because pcic bridges and the like aren't oddball. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 21:31: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id BAED937B401 for ; Wed, 7 Feb 2001 21:30:49 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA02343; Thu, 8 Feb 2001 16:30:29 +1100 Date: Thu, 8 Feb 2001 16:30:05 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: Peter Wemm , Alfred Perlstein , Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: *_ROOT removed In-Reply-To: <200102080503.f1853J998701@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Feb 2001, Warner Losh wrote: > In message <200102080125.f181PRt70396@mobile.wemm.org> Peter Wemm writes: > : No, FFS_ROOT was unused. We have a generic mountroot mechanism, so we no > : longer needed to compile the "special" FFS-specific version of the code > : into autoconf.c. FFS is still optional. For i386 FFS_ROOT and CD9660_ROOT > : did nothing, and on alpha/ia64 it did something that was more likely to > : cause problems than help. > > Then why was FFS moved to opt_dontuse.h? Becuase that's the right place for it. It is kernel sources that don't (shouldn't) use it, not kernel configuration files. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 21:34:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1A1DB37B491 for ; Wed, 7 Feb 2001 21:34:05 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f185Xl998985; Wed, 7 Feb 2001 22:33:48 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102080533.f185Xl998985@harmony.village.org> To: Bruce Evans Subject: Re: *_ROOT removed Cc: Peter Wemm , Alfred Perlstein , Leif Neland , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Feb 2001 16:30:05 +1100." References: Date: Wed, 07 Feb 2001 22:33:47 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : Becuase that's the right place for it. It is kernel sources that don't : (shouldn't) use it, not kernel configuration files. Ah. OK. I'll update the UPDATING entry I'm writing then. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 21:59: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D92A237B401 for ; Wed, 7 Feb 2001 21:58:46 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f185wg345158; Thu, 8 Feb 2001 06:58:42 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.1/8.11.0) with ESMTP id f185vLx59871; Thu, 8 Feb 2001 06:57:26 +0100 (CET) (envelope-from leifn@neland.dk) Date: Thu, 8 Feb 2001 06:57:21 +0100 (CET) From: Leif Neland To: "Michael C . Wu" Cc: freebsd-current@FreeBSD.ORG Subject: Re: pkg_update In-Reply-To: <20010207202335.C20454@peorth.iteration.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Feb 2001, Michael C . Wu wrote: > On Thu, Feb 08, 2001 at 01:56:11AM +0100, Leif Neland scribbled: > | It seems pkg_update is only usable when installing from packages, not from > | ports. > > Because it is a package update system. If you want to update > from the ports, use 'pkg_version -c |sh' > But that does not update the dependencies in the other ports to this version. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 7 23:18:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from www.evil.2y.net (ip-216-23-55-121.adsl.one.net [216.23.55.121]) by hub.freebsd.org (Postfix) with ESMTP id 4284B37B401; Wed, 7 Feb 2001 23:18:22 -0800 (PST) Received: (from cokane@localhost) by www.evil.2y.net (8.11.2/8.11.1) id f187VXK01108; Thu, 8 Feb 2001 02:31:33 -0500 (EST) (envelope-from cokane) Date: Thu, 8 Feb 2001 02:31:33 -0500 From: Coleman Kane To: multimedia@FreeBSD.org Cc: current@FreeBSD.org Subject: Voodoo Graphics owners: Message-ID: <20010208023133.A1090@cokane.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I would like to know if any owners of Voodoo Graphics boards have tried using their card with the kernel driver I wrote. I would like to know how stable the code is for both the Voodoo Graphics and Voodoo II boards before I make any rash decisions (like tagging it for RELENG_4). So far I have gotten success stories from Voodoo II owners, but I haven't heard from and Voodoo Graphics owners (and I don't own one of these cards). Anyway, I'll write up a quick man page tomorrow and hopefully I'll get some feedback. Thanks in advance, Coleman Kane To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 0:31:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 9F1FA37B401; Thu, 8 Feb 2001 00:30:53 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f188VS229933; Thu, 8 Feb 2001 08:31:28 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f188X0Q53810; Thu, 8 Feb 2001 08:33:00 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102080833.f188X0Q53810@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Maxim Sobolev Cc: brian@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [Fwd: cvs commit: src/lib/libc/stdio findfp.c] In-Reply-To: Message from Maxim Sobolev of "Wed, 07 Feb 2001 22:16:21 +0200." <3A81AD15.127A18C2@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Feb 2001 08:33:00 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, at least half way through an installworld, xsane works again :-) Thanks. > Hi, > > Please check to see if it would solve your problems with fopen(). > > -Maxim > -------- Original Message -------- > Subject: cvs commit: src/lib/libc/stdio findfp.c > Date: Wed, 7 Feb 2001 09:34:50 -0800 (PST) > From: Maxim Sobolev > To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org > > sobomax 2001/02/07 09:34:49 PST > > Modified files: > lib/libc/stdio findfp.c > Log: > Fix a f^Hdamn typo, which prevented to fopen() more that 17 files at once. > > Tested by: knu, sobomax and other #bsdcode'rs > > Revision Changes Path > 1.9 +2 -2 src/lib/libc/stdio/findfp.c -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 1:38:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id AD2E337B503 for ; Thu, 8 Feb 2001 01:38:40 -0800 (PST) Received: (qmail 1126 invoked by uid 1000); 8 Feb 2001 09:32:21 -0000 Date: Thu, 8 Feb 2001 10:32:21 +0100 From: Andrea Campi To: John Baldwin Cc: current@FreeBSD.org, "Crist J. Clark" , Jim Bloom Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010208103221.A1088@webcom.it> References: <20010208021930.C13541@webcom.it> <20010208025022.F13541@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010208025022.F13541@webcom.it>; from andrea@webcom.it on Thu, Feb 08, 2001 at 02:50:24AM +0100 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Seriously, that's ok, I only want to check if I get the same panic. And give > feedback of course. Here I am again. Didn't get as far as a login prompt, I have a panic when qmail starts up: lock order reversal 1st lockmgr last acquired @ ../../kern/kern_lock.c:239 2nd 0xc02630c0 uidinfo hash @ ../../kern/kern_resource.c:727 3rd 0xc0261080 lockmgr @ ../../kern/kern_lock.c:239 panic: mutex_enter: recursion on non-recursive mutex process lock @ +../../kern/kern_lock.c:260 Debugger("panic") Stopped at Debugger+0x46: pushl %ebx db> trace Debugger(c0213d83) at Debugger+0x46 panic(c0212cc0,c0211119,c021195a,104,c65d6964) at panic+0x70 witness_enter(c65d6964,0,c021195a,104,c65d6964) at witness_enter+0x1b2 _mtx_enter(c65d6964,0,c021195a,104) at _mtx_enter+0x154 lockmgr(c026849c,1,0,c65d6840,c0a6691c) at lockmgr+0xad kernacc(c027bd40,4,1,c023c500,0c0212497,34d) at kernacc+0x54 mtx_validate(c0a6691c,1) at mtx_validate+0x59 mtx_init(c0a6691c,c02138cc,0,0,57) at mtx_init+0x13 uicreate(57,c65d6964,c0a6d0c0,c65e0f30,c014f13a) at uicreate+0x8a uifind(57,c65d6964,0,c02135b0,586) at uifind+0x33 change_ruid(c65d6840,57,c65d6840,0,1) at change_ruid+0x46 setuid(c65d6840,c65e0f80,bfbffd80,bfbffd7c,bfbffd90) at setuid+0x3a syscall2(2f,2f,2f,bfbffd90,bfbffd7c) at syscall2+0x29c Xint0x80_syscall() at Xint0x80_syscall+0x23 --- syscall 0x17, eip = 0x280a039c, esp 0xbfbffcdc, ebp = 0xbfbffcf8 At least I think it's qmail, looking at the `ps' output... -- The best things in life are free, but the expensive ones are still worth a look. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 1:40:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from multiopen.com (multiopen.com [216.122.202.217]) by hub.freebsd.org (Postfix) with ESMTP id 6E86D37B65D; Thu, 8 Feb 2001 01:40:18 -0800 (PST) Received: from multiopen.com ([211.36.232.217]) by multiopen.com (8.9.3/8.9.3) with SMTP id SAA15380; Thu, 8 Feb 2001 18:34:43 +0900 (KST) Message-Id: <200102080934.SAA15380@multiopen.com> From: "Michael Sussman" To: "julia15@hp.com"@FreeBSD.ORG, julia15@hp.com Subject: Regarding your suggestion to "multiopen.com" Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 8 Feb 2001 18:39:54 +0900 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, ma'am. We really appreciate your funding proposal. Our management department will go over the deal for a couple of days. Thanks. Best Regards http://www.multiopen.com csc@multiopen.com Michael Sussman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 1:41: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id D947F37B698 for ; Thu, 8 Feb 2001 01:40:49 -0800 (PST) Received: (qmail 1210 invoked by uid 1000); 8 Feb 2001 09:34:33 -0000 Date: Thu, 8 Feb 2001 10:34:33 +0100 From: Andrea Campi To: Warner Losh Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010208103433.B1088@webcom.it> References: <20010208021930.C13541@webcom.it> <20010208014108.A13541@webcom.it> <20010208021930.C13541@webcom.it> <200102080507.f1857C998723@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102080507.f1857C998723@harmony.village.org>; from imp@harmony.village.org on Wed, Feb 07, 2001 at 10:07:12PM -0700 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ISA bus cannot share interrupts at all. Full stop[*]. Most > pccard/cardbus bridges operate in a mode where they use ISA > interrupts, so cannot share interrupts at all. The hardware just > won't work if you try. NEWCARD tries to kick the cardbus bridge into > full PCI mode, where you can share interrupts, since all the > interrupts are going through the PCI hardware chain which does support > interrupt sharing. Thanks for expressing in a proper way what I was trying to say ;-) Will try again with cardbus and report. So are you saying it SHOULD work (as far as my chipset is behaving, I suppose)? Bye, Andrea -- "One world, one web, one program" -- Microsoft promotional ad "Ein Volk, ein Reich, ein Fuehrer" -- Adolf Hitler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 3:35:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 77A2B37B401; Thu, 8 Feb 2001 03:35:20 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 7984C311E; Thu, 8 Feb 2001 11:35:19 +0000 (GMT) Date: Thu, 8 Feb 2001 11:35:19 +0000 From: Josef Karthauser To: Robert Watson Cc: Dag-Erling Smorgrav , Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010208113519.A789@tao.org.uk> Mail-Followup-To: Josef Karthauser , Robert Watson , Dag-Erling Smorgrav , Brian Somers , Julian Elischer , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Wed, Feb 07, 2001 at 10:07:06PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 07, 2001 at 10:07:06PM -0500, Robert Watson wrote: >=20 > On 7 Feb 2001, Dag-Erling Smorgrav wrote: >=20 > > Brian Somers writes: > > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm=20 > > > for three days (probably about 36 hours excluding suspends) on a=20 > > > 366MHz laptop with a ATA33 disk. > >=20 > > Would it be possible for someone experiencing this slowdown to try to > > narrow down the day (or even the week) on which it occurred? >=20 > I've experienced a substantial slowdown in VMware since bumping forwards > from -STABLE on my workstation. As I recently commented on -emulation, > I've also been experiencing 30-40 second hangs of the system during VMware > startup and occasional serious slowdown while running, which may be > related to the fairly intensive VM activity for page wiring and the like, > or possible poor interaction with the ATA driver. I also get messages on > the order of the following:=20 The slowdown during start up appears to be in biowr; this is probably because of IDE write caching being switched off. More seriously the vmware hangs during various phases of it's boot process. i.e: 714 root -14 0 123M 79192K inode 0:45 25.29% 25.29% vmware When this happens the whole machine freezes also. Processes run, but new processes don't get forked. The whole machine appears to be I/O bound. (What's the 'inode' state?) The problem is definitely solved by enabling ATA_ENABLE_WC in the kernel config. What's unclear to me is why the hang in 'inode' with it switched off. I understand that biowr's would take longer, which is vmware does as it brings up the virtual machine, but why the hanging and freezing in 'inode'? Joe RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.91 retrieving revision 1.92 diff -u -r1.91 -r1.92 --- ata-disk.c 2001/01/19 13:53:54 1.91 +++ ata-disk.c 2001/01/29 18:00:35 1.92 @@ -25,7 +25,7 @@ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * - * $FreeBSD: src/sys/dev/ata/ata-disk.c,v 1.91 2001/01/19 13:53:54 peter E= xp $ + * $FreeBSD: src/sys/dev/ata/ata-disk.c,v 1.92 2001/01/29 18:00:35 sos Exp= $ */ =20 #include "opt_global.h" @@ -133,10 +133,15 @@ 0, 0, 0, 0, ATA_C_F_ENAB_RCACHE, ATA_WAIT_INTR)) printf("ad%d: enabling readahead cache failed\n", adp->lun); =20 +#if defined(ATA_ENABLE_WC) || defined(ATA_ENABLE_TAGS) if (ata_command(adp->controller, adp->unit, ATA_C_SETFEATURES, 0, 0, 0, 0, ATA_C_F_ENAB_WCACHE, ATA_WAIT_INTR)) printf("ad%d: enabling write cache failed\n", adp->lun); - +#else + if (ata_command(adp->controller, adp->unit, ATA_C_SETFEATURES, + 0, 0, 0, 0, ATA_C_F_DIS_WCACHE, ATA_WAIT_INTR)) + printf("ad%d: disabling write cache failed\n", adp->lun); +#endif /* use DMA if drive & controller supports it */ ata_dmainit(adp->controller, adp->unit, ata_pmode(AD_PARAM), ata_wmode(AD_PARAM), ata_umode(AD_PARA= M)); --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqChHYACgkQXVIcjOaxUBat+ACeMJNFQX4zP+xZSRxN1fDqcYeJ qTMAoOiVt/Rhx4louR4jTipN1ZavkRmz =ezi+ -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 4: 8:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 6BA4E37B491 for ; Thu, 8 Feb 2001 04:08:25 -0800 (PST) Received: (qmail 13646 invoked by uid 666); 8 Feb 2001 12:15:51 -0000 Received: from reggae-02-154.nv.iinet.net.au (HELO elischer.org) (203.59.91.154) by mail.m.iinet.net.au with SMTP; 8 Feb 2001 12:15:51 -0000 Message-ID: <3A828C2C.F7CDA809@elischer.org> Date: Thu, 08 Feb 2001 04:08:12 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Josef Karthauser Cc: Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: <20010208113519.A789@tao.org.uk> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > > The slowdown during start up appears to be in biowr; this is probably > because of IDE write caching being switched off. More seriously > the vmware hangs during various phases of it's boot process. Write caching is incompaible with soft updates. The drive must NEVER report that something is on disk when it really is not! > > i.e: > > 714 root -14 0 123M 79192K inode 0:45 25.29% 25.29% vmware > > When this happens the whole machine freezes also. Processes run, but > new processes don't get forked. The whole machine appears to be I/O > bound. (What's the 'inode' state?) this sounds like a differnt starvation problem. when it's happenning, what does 'iostat 1' show? (how many transactions per second?) I believe that vmware mmaps a region of memory and then somehow syncs it to disk. (It is certainly doing something like it here). > > The problem is definitely solved by enabling ATA_ENABLE_WC in the kernel > config. What's unclear to me is why the hang in 'inode' with it > switched off. I understand that biowr's would take longer, which is > vmware does as it brings up the virtual machine, but why the hanging > and freezing in 'inode'? maybe syncing mmapped regions locks out other types of activity? Matt? > > +#else > + if (ata_command(adp->controller, adp->unit, ATA_C_SETFEATURES, > + 0, 0, 0, 0, ATA_C_F_DIS_WCACHE, ATA_WAIT_INTR)) > + printf("ad%d: disabling write cache failed\n", adp->lun); > +#endif > we used to do this on the interjet because we ran soft updates. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 4:27:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 684B837B401; Thu, 8 Feb 2001 04:27:29 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id AC9C5324B; Thu, 8 Feb 2001 12:27:24 +0000 (GMT) Date: Thu, 8 Feb 2001 12:27:24 +0000 From: Josef Karthauser To: Julian Elischer Cc: Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010208122724.A701@tao.org.uk> Mail-Followup-To: Josef Karthauser , Julian Elischer , Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A828C2C.F7CDA809@elischer.org>; from julian@elischer.org on Thu, Feb 08, 2001 at 04:08:12AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 08, 2001 at 04:08:12AM -0800, Julian Elischer wrote: > Josef Karthauser wrote: > >=20 > > 714 root -14 0 123M 79192K inode 0:45 25.29% 25.29% vmware > >=20 > > When this happens the whole machine freezes also. Processes run, but > > new processes don't get forked. The whole machine appears to be I/O > > bound. (What's the 'inode' state?) > this sounds like a differnt starvation problem. > when it's happenning, what does 'iostat 1' show? > (how many transactions per second?) It looks like below. Joe tty ad0 fd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 179 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 2 0 0 2 97 0 59 8.00 66 0.52 0.00 0 0.00 1 0 2 2 95 0 60 8.00 68 0.53 0.00 0 0.00 1 0 1 2 97 0 60 8.00 68 0.53 0.00 0 0.00 0 0 1 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 1 1 98 0 59 8.00 66 0.52 0.00 0 0.00 0 0 0 2 98 79 60 8.00 67 0.53 0.00 0 0.00 0 0 1 2 98 183 60 8.00 68 0.53 0.00 0 0.00 0 0 3 2 95 143 60 8.00 67 0.53 0.00 0 0.00 0 0 3 3 94 197 59 8.00 67 0.53 0.00 0 0.00 1 0 1 2 97 48 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 8 60 8.00 67 0.53 0.00 0 0.00 0 0 2 2 96 228 59 8.00 66 0.52 0.00 0 0.00 1 0 2 2 96 40 60 8.00 67 0.53 0.00 0 0.00 0 0 2 2 96 0 60 8.00 68 0.53 0.00 0 0.00 1 0 1 2 97 0 60 8.00 67 0.53 0.00 0 0.00 1 0 1 3 95 0 59 8.00 67 0.53 0.00 0 0.00 1 0 1 2 97 tty ad0 fd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 179 8.00 68 0.53 0.00 0 0.00 0 0 2 2 97 0 60 8.00 67 0.53 0.00 0 0.00 1 0 1 2 96 0 59 8.00 67 0.53 0.00 0 0.00 0 0 0 3 97 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 1 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 68 0.53 0.00 0 0.00 1 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 1 2 98 0 59 8.00 67 0.53 0.00 0 0.00 0 0 2 2 95 0 60 8.00 68 0.53 0.00 0 0.00 0 0 1 3 96 0 60 8.00 68 0.53 0.00 0 0.00 2 0 1 2 95 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 0 59 8.00 66 0.52 0.00 0 0.00 0 0 0 2 98 0 60 8.00 66 0.52 0.00 0 0.00 0 0 0 2 98 0 60 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqCkKwACgkQXVIcjOaxUBZXKACeIHaYQRyE7ReyHeoY9J4rFxJm MBAAoMP7fiFRqjV00Q7Rcc5mXHGPRsGM =SBRa -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 4:43:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id 9823A37B503; Thu, 8 Feb 2001 04:43:03 -0800 (PST) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id VAA26958; Thu, 8 Feb 2001 21:43:00 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id VAA15397; Thu, 8 Feb 2001 21:43:00 +0900 (JST) To: current@FreeBSD.ORG Cc: trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: <20010207171156.A72756@cicely5.cicely.de> References: <20010206133030.A2232@cicely5.cicely.de> <20010206232112W.non@ever.sanda.gr.jp> <20010207171156.A72756@cicely5.cicely.de> X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010208214259C.non@ever.sanda.gr.jp> Date: Thu, 08 Feb 2001 21:42:59 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 35 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bernd Walter Date: Wed, 7 Feb 2001 17:11:57 +0100 > On Tue, Feb 06, 2001 at 11:21:12PM +0900, non@ever.sanda.gr.jp wrote: > > Today I tried with 4.2-RELEASE (sorry not -current) and, > > 1. Boot up the 4.2-RELEASE with GENERIC kernel. > > 2. Connect MO drive with PC Card SCSI(ncv). > > 3. Insert PC Card without medium in the MO drive. > > 4. The pccardd automatically run camcontrol rescan. > > 5. Message says that da0 is 0MB capacity. > > 6. Run fdisk da0 > > 7. got panic with divided by zero. > > > > Probably divided by zero is caused at line 737 or 748 in the > > scsi_low_action() in cam/scsi/scsi_low.c because of ccg->block_size or > > secs_per_cylinder is zero. I tried with same drive and another SCSI card (ahc0) in 4.2-RELEASE. No problem were found. I watched the diffs between da.c and od.c. It seems like some fault in scsi_low.c. Hmm, my fault.... Sorry for claiming `da'. By the way, in Japanese users mailing list, some said that `da' does not check whether a medium is writerable or not (write protected). If you mount a write protected medium with -rw, it will lead bad condition when you do umount. > I never used fdisk on a removeable disk as I only needed them for FreeBSD. : > It looks like fdisk triggers the bug. I used fdisk just to check if there is a slice or not. Fdisk did not make problem. // Noriaki Mitsunaga // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 4:58:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-01.iinet.net.au (syncopation-01.iinet.net.au [203.59.24.37]) by hub.freebsd.org (Postfix) with SMTP id 7560037B4EC for ; Thu, 8 Feb 2001 04:58:30 -0800 (PST) Received: (qmail 9349 invoked by uid 666); 8 Feb 2001 13:05:15 -0000 Received: from reggae-13-123.nv.iinet.net.au (HELO elischer.org) (203.59.79.123) by mail.m.iinet.net.au with SMTP; 8 Feb 2001 13:05:15 -0000 Message-ID: <3A8297E9.78B93F25@elischer.org> Date: Thu, 08 Feb 2001 04:58:17 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Josef Karthauser Cc: Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> <20010208122724.A701@tao.org.uk> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > > On Thu, Feb 08, 2001 at 04:08:12AM -0800, Julian Elischer wrote: > > Josef Karthauser wrote: > > > > > > 714 root -14 0 123M 79192K inode 0:45 25.29% 25.29% vmware > > > > > > When this happens the whole machine freezes also. Processes run, but > > > new processes don't get forked. The whole machine appears to be I/O > > > bound. (What's the 'inode' state?) > > this sounds like a differnt starvation problem. > > when it's happenning, what does 'iostat 1' show? > > (how many transactions per second?) > > It looks like below. Looks like some way of clustering this might achieve a lot. what does systat -vmstat or vmstat 1 show? Better still, I guess we could do a linux-truss and see what it's doing... > Joe > > tty ad0 fd0 cpu > tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id > 0 179 8.00 67 0.53 0.00 0 0.00 0 0 0 2 98 > 0 59 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 > 0 60 8.00 68 0.53 0.00 0 0.00 0 0 0 2 98 > 0 60 8.00 67 0.53 0.00 0 0.00 2 0 0 2 97 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 5:25:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A7E4737B65D; Thu, 8 Feb 2001 05:25:10 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA67849; Thu, 8 Feb 2001 14:24:39 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Julian Elischer Cc: Josef Karthauser , Robert Watson , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> From: Dag-Erling Smorgrav Date: 08 Feb 2001 14:24:39 +0100 In-Reply-To: Julian Elischer's message of "Thu, 08 Feb 2001 04:08:12 -0800" Message-ID: Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > I believe that vmware mmaps a region of memory and then somehow syncs > it to disk. (It is certainly doing something like it here). Theory: VMWare mmaps a region of memory corresponding to the virtual machine's "physical" RAM, then touches every page during startup. Unless some form of clustering is done, this causes 16384 write operations for a 64 MB virtual machine... DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 6:48:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 11F8B37B503; Thu, 8 Feb 2001 06:48:09 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id B2031311F; Thu, 8 Feb 2001 14:47:59 +0000 (GMT) Date: Thu, 8 Feb 2001 14:47:59 +0000 From: Josef Karthauser To: Julian Elischer Cc: Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010208144759.A7913@tao.org.uk> Mail-Followup-To: Josef Karthauser , Julian Elischer , Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> <20010208122724.A701@tao.org.uk> <3A8297E9.78B93F25@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A8297E9.78B93F25@elischer.org>; from julian@elischer.org on Thu, Feb 08, 2001 at 04:58:17AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 08, 2001 at 04:58:17AM -0800, Julian Elischer wrote: >=20 > Looks like some way of clustering this might achieve a lot. >=20 > what does systat -vmstat or vmstat 1 > show? > Better still, I guess we could do a linux-truss > and see what it's doing... I believe that it's strace under linux. If someone can provide me with a binary of this tool I'll happily run it here and see what vmware's doing. Joe --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqCsZ8ACgkQXVIcjOaxUBbC/wCgjgfWeOZiQcMI+m5341WegDkP APUAn2Ka3u9dI24ONeLMtlwjeE7sxk3h =759q -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 6:51: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 30DEE37B4EC; Thu, 8 Feb 2001 06:50:49 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Feb 2001 14:50:48 +0000 (GMT) Date: Thu, 8 Feb 2001 14:50:48 +0000 From: David Malone To: Josef Karthauser Cc: Julian Elischer , Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: What's changed recently with vmware/linuxemu/file I/O Message-ID: <20010208145048.A10252@walton.maths.tcd.ie> References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> <20010208122724.A701@tao.org.uk> <3A8297E9.78B93F25@elischer.org> <20010208144759.A7913@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010208144759.A7913@tao.org.uk>; from joe@tao.org.uk on Thu, Feb 08, 2001 at 02:47:59PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 08, 2001 at 02:47:59PM +0000, Josef Karthauser wrote: > > what does systat -vmstat or vmstat 1 > > show? > > Better still, I guess we could do a linux-truss > > and see what it's doing... > > I believe that it's strace under linux. If someone can provide me > with a binary of this tool I'll happily run it here and see what > vmware's doing. You could use FreeBSD ktrace and then the linux_kdump port. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 8:13:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 1112F37B65D for ; Thu, 8 Feb 2001 08:13:29 -0800 (PST) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by avias.com (8.11.2/8.11.2) with ESMTP id f18GDPG81892 for ; Thu, 8 Feb 2001 19:13:26 +0300 (MSK) (envelope-from camel@avias.com) Date: Thu, 8 Feb 2001 19:13:24 +0300 (MSK) From: Ilya Naumov To: Subject: problems with playback via pcm device Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have Ensoniq ES1371-based soundcard supported by pcm driver and experience some problems. the sound played is interruped by clicks and distorsions, and they appear more often when the disk activity is high. during playback the kernel generates messages like 'pcm0: hwptr went backwards 64 -> 32'. any ideas? here is my dmesg: 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 #2: Thu Feb 8 18:19:26 MSK 2001 root@camel.avias.com:/garbage/src/sys/compile/CAMEL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 550023689 Hz CPU: AMD Athlon(tm) Processor (550.02-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ff AMD Features=0xc0400000 real memory = 134135808 (130992K bytes) avail memory = 125829120 (122880K bytes) Preloaded elf kernel "kernel" at 0xc03de000. Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00f15e0 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 (no driver attached) pci0: at 4.3 (no driver attached) pcm0: port 0xa400-0xa43f irq 9 at device 9.0 on pci0 ahc0: port 0xa000-0xa0ff mem 0xe1800000-0xe1800fff irq 5 at device 10.0 on pci0 aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x9800-0x987f mem 0xe1000000-0xe100007f irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:10:5a:74:c4:6c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 psm0: flags 0x8000 irq 12 on atkbdc0 psm0: model NetMouse/NetScroll Optical, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources atspeaker0: at port 0x61 on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 200 packets/entry by default ncp_load: [210-213] ad0: 8223MB [16708/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master using WDMA2 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a xl0: promiscuous mode enabled /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 8:59:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9242437B491; Thu, 8 Feb 2001 08:59:27 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f18Guh941601; Thu, 8 Feb 2001 09:56:43 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102081656.f18Guh941601@harmony.village.org> To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Feb 2001 10:34:33 +0100." <20010208103433.B1088@webcom.it> References: <20010208103433.B1088@webcom.it> <20010208021930.C13541@webcom.it> <20010208014108.A13541@webcom.it> <20010208021930.C13541@webcom.it> <200102080507.f1857C998723@harmony.village.org> Date: Thu, 08 Feb 2001 09:56:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010208103433.B1088@webcom.it> Andrea Campi writes: : Will try again with cardbus and report. So are you saying it SHOULD work : (as far as my chipset is behaving, I suppose)? Cardbus works, more or less, on -current right now. Some cards just work, other cards need help. I keep meaning to do a survey, but haven't found the time to do it yet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 9:20:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id D7ED837B491; Thu, 8 Feb 2001 09:20:34 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA12326; Thu, 8 Feb 2001 10:20:10 -0700 (MST) (envelope-from ken) Date: Thu, 8 Feb 2001 10:20:10 -0700 From: "Kenneth D. Merry" To: non@ever.sanda.gr.jp Cc: current@FreeBSD.ORG, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT Message-ID: <20010208102010.A12099@panzer.kdm.org> References: <20010206133030.A2232@cicely5.cicely.de> <20010206232112W.non@ever.sanda.gr.jp> <20010207171156.A72756@cicely5.cicely.de> <20010208214259C.non@ever.sanda.gr.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010208214259C.non@ever.sanda.gr.jp>; from non@ever.sanda.gr.jp on Thu, Feb 08, 2001 at 09:42:59PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 08, 2001 at 21:42:59 +0900, non@ever.sanda.gr.jp wrote: > From: Bernd Walter > Date: Wed, 7 Feb 2001 17:11:57 +0100 > > On Tue, Feb 06, 2001 at 11:21:12PM +0900, non@ever.sanda.gr.jp wrote: > > > Today I tried with 4.2-RELEASE (sorry not -current) and, > > > 1. Boot up the 4.2-RELEASE with GENERIC kernel. > > > 2. Connect MO drive with PC Card SCSI(ncv). > > > 3. Insert PC Card without medium in the MO drive. > > > 4. The pccardd automatically run camcontrol rescan. > > > 5. Message says that da0 is 0MB capacity. > > > 6. Run fdisk da0 > > > 7. got panic with divided by zero. > > > > > > Probably divided by zero is caused at line 737 or 748 in the > > > scsi_low_action() in cam/scsi/scsi_low.c because of ccg->block_size or > > > secs_per_cylinder is zero. > > I tried with same drive and another SCSI card (ahc0) in > 4.2-RELEASE. No problem were found. I watched the diffs between da.c > and od.c. It seems like some fault in scsi_low.c. Hmm, my fault.... > > Sorry for claiming `da'. No problem. :) > By the way, in Japanese users mailing list, some said that `da' does > not check whether a medium is writerable or not (write > protected). If you mount a write protected medium with -rw, it will > lead bad condition when you do umount. Hmm, can you demonstrate the problem? The write-protect check in the od driver is one of the things that the da driver doesn't have. I figured it wouldn't really be necessary, since any attempted writes would be returned with errors. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 9:21:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 23F4337B4EC for ; Thu, 8 Feb 2001 09:20:50 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f18HKkl24631 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 8 Feb 2001 18:20:48 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f18HL7P79452 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Thu, 8 Feb 2001 18:21:13 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f18HL7B80771 for freebsd-current@freebsd.org; Thu, 8 Feb 2001 18:21:07 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Feb 2001 18:21:07 +0100 From: Bernd Walter To: freebsd-current@freebsd.org Subject: atomic_ question Message-ID: <20010208182106.B80741@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are atomic_* implementations allowed to spin/sleep? The question is because some platforms don't have atomic operations for adding and so on (e.g. sparcv8). The only way to implement them on these platforms is to use a lock. Now I'm wonder if the use of a sleep mutex is allowed or is a simple spinning lock the sensefull choice. One of the results is that there is no mutex/lock allocated specially for this purpose and there is a need to allocate one globaly for all. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 9:27:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 34D2637B491 for ; Thu, 8 Feb 2001 09:27:18 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f18HRFl25468 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 8 Feb 2001 18:27:17 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f18HReP79459 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Thu, 8 Feb 2001 18:27:42 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f18HReN80794 for freebsd-current@freebsd.org; Thu, 8 Feb 2001 18:27:40 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Feb 2001 18:27:40 +0100 From: Bernd Walter To: freebsd-current@freebsd.org Subject: Overview of machine dependend routines Message-ID: <20010208182740.A80779@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there an overview available which defines all machine dependend routines that are needed. By looking into the code it's not always obvious if a given function is one called by the MI code or if it's only a helper function inside. I asume the definitions from "Inside 4.4BSD" are outdated in some cases. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 10:22:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 3799737B401 for ; Thu, 8 Feb 2001 10:22:33 -0800 (PST) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout0.freenet.de with esmtp (Exim 3.22 #1) id 14QviC-0001sq-00 for current@freebsd.org; Thu, 08 Feb 2001 19:22:32 +0100 Received: from a2efb.pppool.de ([213.6.46.251] helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.22 #1) id 14QviA-0001kW-00 for current@freebsd.org; Thu, 08 Feb 2001 19:22:31 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.2/8.11.2) with ESMTP id f18IJSC10666 for ; Thu, 8 Feb 2001 19:19:29 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200102081819.f18IJSC10666@Magelan.Leidinger.net> Date: Thu, 8 Feb 2001 19:19:27 +0100 (CET) From: Alexander Leidinger Subject: kernel trap 12 with interrupts disabled To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, if I run a program compiled with gcc's function profiling option I get "kernel trap 12 with interrupts disabled". If I run it withhin X11, the machine deadlocks hard (no response from the numlock led on the keyboard), withhin a virtual console I get a lot of "kernel trap ..." and the program runs fine. -current as of Feb. 6, ~2pm UTC. Bye, Alexander. -- I believe the technical term is "Oops!" http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 10:29:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 86F9A37B6A7 for ; Thu, 8 Feb 2001 10:28:52 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f18ISN603401; Thu, 8 Feb 2001 20:28:26 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.2/8.11.2) with ESMTP id f18ISSm11870; Thu, 8 Feb 2001 20:28:28 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A82E545.2AB2BDBD@FreeBSD.org> Date: Thu, 08 Feb 2001 20:28:21 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Alexander Leidinger Cc: current@FreeBSD.org Subject: Re: kernel trap 12 with interrupts disabled References: <200102081819.f18IJSC10666@Magelan.Leidinger.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger wrote: > Hi, > > if I run a program compiled with gcc's function profiling option I get > "kernel trap 12 with interrupts disabled". The same is here. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 10:42:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B98B537B6AA for ; Thu, 8 Feb 2001 10:42:38 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f18IgQ951815; Thu, 8 Feb 2001 11:42:26 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102081842.f18IgQ951815@harmony.village.org> To: Ilya Naumov Subject: Re: problems with playback via pcm device Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Feb 2001 19:13:24 +0300." References: Date: Thu, 08 Feb 2001 11:42:26 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Ilya Naumov writes: : during playback the kernel generates messages like 'pcm0: hwptr went : backwards 64 -> 32'. any ideas? : FreeBSD 5.0-CURRENT #2: Thu Feb 8 18:19:26 MSK 2001 Interrupt latency in current really sucks right now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 11:16:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5D65D37B65D for ; Thu, 8 Feb 2001 11:16:21 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f18JBP318534; Thu, 8 Feb 2001 11:11:25 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010208103221.A1088@webcom.it> Date: Thu, 08 Feb 2001 11:12:59 -0800 (PST) From: John Baldwin To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Feb-01 Andrea Campi wrote: >> Seriously, that's ok, I only want to check if I get the same panic. And give >> feedback of course. > > Here I am again. Didn't get as far as a login prompt, I have a panic when > qmail > starts up: Turn MUTEX_DEBUG off. It appears to be broken atm. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 11:17:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9809637B503 for ; Thu, 8 Feb 2001 11:16:52 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA18737 for ; Thu, 8 Feb 2001 11:16:54 -0800 Date: Thu, 8 Feb 2001 11:16:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: Fibre Channel "Hardware" List... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just put up a simple Fibre Channel "Suggest Hardware Matrix" as the beginnings of what one might expect for Fibre Channel in FreeBSD- see http://people.freebsd.org/~mjacob/Fibre_Channel_Hardware.txt Suggestions welcome! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 11:44:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from utep.el.utwente.nl (utep.el.utwente.nl [130.89.30.10]) by hub.freebsd.org (Postfix) with ESMTP id 5EBBF37B6A0 for ; Thu, 8 Feb 2001 11:44:27 -0800 (PST) Received: from tn.utwente.nl (uttnb55.tn.utwente.nl [130.89.74.55]) by utep.el.utwente.nl (8.9.3/8.9.3) with ESMTP id UAA25759 for ; Thu, 8 Feb 2001 20:45:17 +0100 Message-ID: <3A82F721.8EA2B0E1@tn.utwente.nl> Date: Thu, 08 Feb 2001 20:44:33 +0100 From: "Andrei A. Dergatchev" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,ru MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just put up a simple Fibre Channel "Suggest Hardware Matrix" as the > beginnings of what one might expect for Fibre Channel in FreeBSD- see > > http://people.freebsd.org/~mjacob/Fibre_Channel_Hardware.txt > > Suggestions welcome! As you asked, just suggestions here from someone who is putting FC stuff together for my own :-) - "Very expensive (in my opinion)" - if you mention "expensive"-"not expensive", I would propose to add rough price estimations too - this might be of interest for beginners imho. "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 ? Regards, Andrei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 11:49:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 2308C37B6BE for ; Thu, 8 Feb 2001 11:49:09 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14Qx3z-00037q-00; Thu, 08 Feb 2001 19:49:07 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f18JpdQ01993; Thu, 8 Feb 2001 20:51:39 +0100 (CET) (envelope-from wkb) Date: Thu, 8 Feb 2001 20:51:39 +0100 From: Wilko Bulte To: "Andrei A. Dergatchev" Cc: current@freebsd.org Subject: Re: Fibre Channel "Hardware" List... Message-ID: <20010208205139.B1823@freebie.demon.nl> References: <3A82F721.8EA2B0E1@tn.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A82F721.8EA2B0E1@tn.utwente.nl>; from A.Dergatchev@tn.utwente.nl on Thu, Feb 08, 2001 at 08:44:33PM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 11:58:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A516A37B6C0 for ; Thu, 8 Feb 2001 11:58:19 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA18872; Thu, 8 Feb 2001 11:58:18 -0800 Date: Thu, 8 Feb 2001 11:58:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Andrei A. Dergatchev" Cc: current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... In-Reply-To: <3A82F721.8EA2B0E1@tn.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cool! I'll update page momentarily with corrections! > > > > > I've just put up a simple Fibre Channel "Suggest Hardware Matrix" as the > > beginnings of what one might expect for Fibre Channel in FreeBSD- see > > > > http://people.freebsd.org/~mjacob/Fibre_Channel_Hardware.txt > > > > Suggestions welcome! > > As you asked, just suggestions here from someone who is putting > FC stuff together for my own :-) - > > "Very expensive (in my opinion)" - if you mention "expensive"-"not > expensive", > I would propose to add rough price estimations too - this might be of > interest > for beginners imho. > > "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 ? > > Regards, > > Andrei > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 12:13:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C3E9937B4EC for ; Thu, 8 Feb 2001 12:13:33 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA18958; Thu, 8 Feb 2001 12:13:30 -0800 Date: Thu, 8 Feb 2001 12:13:27 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: "Andrei A. Dergatchev" , current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... In-Reply-To: <20010208205139.B1823@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. > 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 :-( > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 12:20:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from utep.el.utwente.nl (utep.el.utwente.nl [130.89.30.10]) by hub.freebsd.org (Postfix) with ESMTP id 0A9E937B6C3 for ; Thu, 8 Feb 2001 12:19:55 -0800 (PST) Received: from tn.utwente.nl (uttnb55.tn.utwente.nl [130.89.74.55]) by utep.el.utwente.nl (8.9.3/8.9.3) with ESMTP id VAA26525 for ; Thu, 8 Feb 2001 21:21:07 +0100 Message-ID: <3A82FF86.3D79F717@tn.utwente.nl> Date: Thu, 08 Feb 2001 21:20:22 +0100 From: "Andrei A. Dergatchev" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,ru MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. Thanks ! And for the page too - very good and useful !! For poor owners of 2GB-ready Seagates, I wonder can you advise on any affordable 2GB enclosure ? Everything affordable I saw is a bit old and 1GB-only. Of course, I don't now if it will make any real difference - will burst speed twice as fast or what ? Would be really nice to hear from someone knowledgeable :-) Thanks again ! Regards, Andrei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 12:24:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0079E37B4EC for ; Thu, 8 Feb 2001 12:23:54 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA19013; Thu, 8 Feb 2001 12:23:53 -0800 Date: Thu, 8 Feb 2001 12:23:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Andrei A. Dergatchev" Cc: current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... In-Reply-To: <3A82FF86.3D79F717@tn.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. > > Thanks ! And for the page too - very good and useful !! > > For poor owners of 2GB-ready Seagates, I wonder can you advise > on any affordable 2GB enclosure ? Everything affordable I saw is > a bit old and 1GB-only. Of course, I don't now if it will make any > real difference - will burst speed twice as fast or what ? Would be > really nice to hear from someone knowledgeable :-) About the 2Gb drives, sorry! I have no clue as yet about this! > > Thanks again ! You're welcome! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 12:27:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id F1A9B37B6AC; Thu, 8 Feb 2001 12:26:56 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f18KRW232717; Thu, 8 Feb 2001 20:27:32 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f18KT7A03220; Thu, 8 Feb 2001 20:29:07 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102082029.f18KT7A03220@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Josef Karthauser , Julian Elischer , Robert Watson , Dag-Erling Smorgrav , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: Message from Josef Karthauser of "Thu, 08 Feb 2001 14:47:59 GMT." <20010208144759.A7913@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Feb 2001 20:29:07 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Feb 08, 2001 at 04:58:17AM -0800, Julian Elischer wrote: > >=20 > > Looks like some way of clustering this might achieve a lot. > >=20 > > what does systat -vmstat or vmstat 1 > > show? > > Better still, I guess we could do a linux-truss > > and see what it's doing... > > I believe that it's strace under linux. If someone can provide me > with a binary of this tool I'll happily run it here and see what > vmware's doing. > > Joe The problem seems to have gone away after this (kindly pointed out to me by Maxim after my other post about xsane dropping cores): : Subject: cvs commit: src/lib/libc/stdio findfp.c : Date: Wed, 7 Feb 2001 09:34:50 -0800 (PST) : From: Maxim Sobolev : To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org : : sobomax 2001/02/07 09:34:49 PST : : Modified files: : lib/libc/stdio findfp.c : Log: : Fix a f^Hdamn typo, which prevented to fopen() more that 17 files at once. : : Tested by: knu, sobomax and other #bsdcode'rs : : Revision Changes Path : 1.9 +2 -2 src/lib/libc/stdio/findfp.c -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 12:44: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from utep.el.utwente.nl (utep.el.utwente.nl [130.89.30.10]) by hub.freebsd.org (Postfix) with ESMTP id AA1F237B6C5 for ; Thu, 8 Feb 2001 12:43:47 -0800 (PST) Received: from tn.utwente.nl (uttnb55.tn.utwente.nl [130.89.74.55]) by utep.el.utwente.nl (8.9.3/8.9.3) with ESMTP id VAA27108 for ; Thu, 8 Feb 2001 21:45:00 +0100 Message-ID: <3A83051F.C40CDA96@tn.utwente.nl> Date: Thu, 08 Feb 2001 21:44:15 +0100 From: "Andrei A. Dergatchev" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,ru MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > > > > > > > > > > Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. [my perhaps poorly worded question] > > About the 2Gb drives, sorry! I have no clue as yet about this! Sorry for the confusion, I meant drives capable of 2 Gbit/s, which the 2300 will supposingly support. My question was that many enclosure support 1 Gbit/s, right ? So, I was wondering have you heard about those which support 2 [Gbit/s] ? Because one do need to have something in between the 2300 card and Cheetah-4 FC drive, right :-) ? Adapter in a case of 1 drive only, I presume, and enclosure in the case of multiple drives. > > > > > Thanks again ! > > You're welcome! Regards, Andrei To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 12:58:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A1ED37B6D4 for ; Thu, 8 Feb 2001 12:57:55 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA19550; Thu, 8 Feb 2001 12:57:55 -0800 Date: Thu, 8 Feb 2001 12:57:52 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Andrei A. Dergatchev" Cc: current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... In-Reply-To: <3A83051F.C40CDA96@tn.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Feb 2001, Andrei A. Dergatchev wrote: > > > Matthew Jacob wrote: > > > > > > > > > > > > > > > > > Oh, yeah, about this, 2300 support is comint "real soon" -this will be 2GBit. > > [my perhaps poorly worded question] > > > > > About the 2Gb drives, sorry! I have no clue as yet about this! > > Sorry for the confusion, I meant drives capable of 2 Gbit/s, > which the 2300 will supposingly support. My question was > that many enclosure support 1 Gbit/s, right ? So, I was > wondering have you heard about those which support 2 [Gbit/s] ? I've heard that Ancor has one. I think that Brocade has one too. I have had access as yet to neither. > Because one do need to have something in between the 2300 card > and Cheetah-4 FC drive, right :-) ? Adapter in a case of 1 drive > only, I presume, and enclosure in the case of multiple drives. Yes. I have no idea who is, as yet, building enclosures with 2Gb interfaces either. This is much like Ultra3- it took at least a year after Ultra3 came out (with disks ready to go) to find a JBOD that would be Ultra3 to the JBOD itself. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 12:58:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 3F0F837B6D7 for ; Thu, 8 Feb 2001 12:58:10 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA29029; Fri, 9 Feb 2001 07:57:55 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01JZWDLDW1IOO2IZIS@cim.alcatel.com.au>; Fri, 9 Feb 2001 07:57:52 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f18Kvo801356; Fri, 09 Feb 2001 07:57:50 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Fri, 09 Feb 2001 07:57:50 +1100 From: Peter Jeremy Subject: Re: atomic_ question In-reply-to: <20010208182106.B80741@cicely5.cicely.de>; from ticso@cicely5.cicely.de on Thu, Feb 08, 2001 at 06:21:07PM +0100 To: Bernd Walter Cc: freebsd-current@FreeBSD.ORG Mail-followup-to: Bernd Walter , freebsd-current@FreeBSD.ORG Message-id: <20010209075749.Z90937@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010208182106.B80741@cicely5.cicely.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Feb-08 18:21:07 +0100, Bernd Walter wrote: >Are atomic_* implementations allowed to spin/sleep? The atomic_* operations are the primitives used to build all the higher level locking functions. Therefore you are not allowed to sleep. As for spinning: You can't implement them using a `normal' spinlock. Some architectures, eg the Alpha, don't have RMW primitives. The Alpha has load-locked and store-conditional instructions which let you build atomic operations - you need to spin between the load and store if the store fails. The store will only fail if you took an interrupt between the load and store or if another master updated the location between your load and store. Look into /sys/alpha/alpha/atomic.s for code. >The only way to implement them on these platforms is to use a lock. Except that locks are built using the atomic_* functions. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 13: 4: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from conn.mc.mpls.visi.com (conn.mc.mpls.visi.com [208.42.156.2]) by hub.freebsd.org (Postfix) with ESMTP id 7EF2A37B6D7 for ; Thu, 8 Feb 2001 13:03:45 -0800 (PST) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by conn.mc.mpls.visi.com (Postfix) with ESMTP id 53A378185; Thu, 8 Feb 2001 15:01:20 -0600 (CST) Received: from localhost (mestery@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id PAA23668; Thu, 8 Feb 2001 15:03:44 -0600 (CST) X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs Date: Thu, 8 Feb 2001 15:03:44 -0600 (CST) From: "Kyle A.D. Mestery" To: Matthew Jacob Cc: "Andrei A. Dergatchev" , current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Thu, 8 Feb 2001, Matthew Jacob wrote: > On Thu, 8 Feb 2001, Andrei A. Dergatchev wrote: > > > > > Sorry for the confusion, I meant drives capable of 2 Gbit/s, > > which the 2300 will supposingly support. My question was > > that many enclosure support 1 Gbit/s, right ? So, I was > > wondering have you heard about those which support 2 [Gbit/s] ? > > I've heard that Ancor has one. I think that Brocade has one too. I have had > access as yet to neither. > It's true, we at Qlogic (formerly Ancor) do have a 2Gb switch in the works. We demoed said switch at Comdex. It's pretty impressive watching your data stream by at 198MB/second! Interestingly enough, said switch runs Linux as the underlying OS (if I had been at Ancor 1 month before I got here, we'd be running FreeBSD instead!) -- Kyle Mestery / Qlogic Corporation \ mestery@visi.com / kyle.mestery@qlogic.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 13:21:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 60E4D37B401 for ; Thu, 8 Feb 2001 13:21:31 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f18LL8V19716 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 8 Feb 2001 22:21:25 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f18LLWP80518 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Thu, 8 Feb 2001 22:21:35 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f18LLW681415 for freebsd-current@FreeBSD.ORG; Thu, 8 Feb 2001 22:21:32 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Feb 2001 22:21:32 +0100 From: Bernd Walter To: freebsd-current@FreeBSD.ORG Subject: Re: atomic_ question Message-ID: <20010208222131.D81067@cicely5.cicely.de> References: <20010208182106.B80741@cicely5.cicely.de> <20010209075749.Z90937@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010209075749.Z90937@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Fri, Feb 09, 2001 at 07:57:50AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 09, 2001 at 07:57:50AM +1100, Peter Jeremy wrote: > On 2001-Feb-08 18:21:07 +0100, Bernd Walter wrote: > >Are atomic_* implementations allowed to spin/sleep? > > The atomic_* operations are the primitives used to build all the > higher level locking functions. Therefore you are not allowed to > sleep. > > As for spinning: You can't implement them using a `normal' spinlock. > Some architectures, eg the Alpha, don't have RMW primitives. The > Alpha has load-locked and store-conditional instructions which let you > build atomic operations - you need to spin between the load and store > if the store fails. The store will only fail if you took an interrupt > between the load and store or if another master updated the location > between your load and store. Look into /sys/alpha/alpha/atomic.s for > code. The alpha way of doing it is very similar to sparcv9. But the alpha code and the code neccesary for sparcv9 has a difference compared to normal spinning. If you get interrupted the interupt code can modify the same value without getting blocked while the interrupted code simply needs another cycle. On sparcv8 you don't have an operation doing conditionaly stores and you don't have RMW operations. The only way to do is to have a global lock variable on which you spin until the current client finishes. That means you can't use them in interrupt code! I saw that some implementations for atomic code for sparcv8 disables interrupts before fetching the lock to suround this problem. Do we grant usuage of the atomic functions in interrupt code? If yes there is a need to disable interrupts! I'm not talking about interrupt threads. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 13:35:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 9ACB337B6B7 for ; Thu, 8 Feb 2001 13:34:57 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f18LWw322589; Thu, 8 Feb 2001 13:32:58 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010208222131.D81067@cicely5.cicely.de> Date: Thu, 08 Feb 2001 13:34:34 -0800 (PST) From: John Baldwin To: Bernd Walter Subject: Re: atomic_ question Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Feb-01 Bernd Walter wrote: > Do we grant usuage of the atomic functions in interrupt code? > If yes there is a need to disable interrupts! > I'm not talking about interrupt threads. Yes, we use spin mutexes to schedule ithreads, and we use other atomic operations in IPI handlers. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 14:45:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 557E737BAAF; Thu, 8 Feb 2001 14:45:34 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f18MjPc48604; Thu, 8 Feb 2001 23:45:25 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Thu, 8 Feb 2001 23:52:32 +0100 (CET) From: Martin Blapp To: alfred@freebsd.org, kuriyama@imgsrc.co.jp, snap-users@kame.net, Francois.Tigeot@nic.fr, ru@freebsd.org, eischen@vigrid.com, Francis.Dupont@enst-bretagne.fr, feico@pasta.cs.uit.no, dillon@earth.backplane.com Cc: asmodai@freebsd.org, freebsd-current@freebsd.org Subject: TI-RPC status (99% done) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have reworked my patches and I run now successfully CURRENT with them, make buildworld has been sucessfull and everything seems to work so far. http://www.attic.ch/patches/rpc.diff_02082001-2.sh.tgz Can't we commit this to CURRENT now ? I'd like to see a history of my changes, I don't have the patch in cvs here, and I'd like that others see the changes too and can tell me if they are correct. These are the changes I have done on this release. # rpc.diff_02082001-2: # Added IPPROT_ST to rpcinfo and rpcbind to correct # output of 'rpcinfo -p'. All Unix socket connections # are correctly displayed as 'local' instead of garbage. # # Corrected rpcinfo.8 to be correctly displayed. I had # to convert all .Nm "" to .Nm # # Fixed some .rej, some man-pages have been updated. # # Removed again some _THREAD_SAFE definitions to make # it fit to the new CURRENT libc-format. More on this # will follow this week. Just go into you CURRENT Source tree and run the patch.sh, then make world and run mergemaster after (to copy all needed files like netconfig and the patches defaults/rc.conf Thank you for your time you spend on the patch. Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 16: 5:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 41F5037B698 for ; Thu, 8 Feb 2001 16:05:05 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id LAA19033; Fri, 9 Feb 2001 11:00:21 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01JZWJYE5H5C8ZKKKC@cim.alcatel.com.au>; Fri, 9 Feb 2001 11:00:10 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f19004V02770; Fri, 09 Feb 2001 11:00:04 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Fri, 09 Feb 2001 11:00:04 +1100 From: Peter Jeremy Subject: Re: atomic_ question In-reply-to: <20010208222131.D81067@cicely5.cicely.de>; from ticso@cicely5.cicely.de on Thu, Feb 08, 2001 at 10:21:32PM +0100 To: Bernd Walter Cc: freebsd-current@FreeBSD.ORG Mail-followup-to: Bernd Walter , freebsd-current@FreeBSD.ORG Message-id: <20010209110004.D90937@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010208182106.B80741@cicely5.cicely.de> <20010209075749.Z90937@gsmx07.alcatel.com.au> <20010208222131.D81067@cicely5.cicely.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Feb-08 22:21:32 +0100, Bernd Walter wrote: >On sparcv8 you don't have an operation doing conditionaly stores and >you don't have RMW operations. >The only way to do is to have a global lock variable on which you spin >until the current client finishes. The SPARC architecture supports SMP so there must be some synchronisation primitive that works between processors (disabling interrupts only works on the current processor). Normally the same primitive can be used to synchronise accesses within the same processor. I know the older SPARC's had a test-and-set instruction which was locked RMW - there must be something similar in v8 and v9. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 16:11: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0E53E37B503 for ; Thu, 8 Feb 2001 16:10:50 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id f190Ahc51672; Fri, 9 Feb 2001 01:10:43 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Fri, 9 Feb 2001 01:17:49 +0100 (CET) From: Martin Blapp To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: /usr/src/UPDATING Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Warner, Can you add a remark about the devfs and vinum conflict to UPDATING ? I had serious problems today, because I have been bitten by this conflict. Devfs is now in GENERIC-KERNEL in CURRENT, and if you upgrade and have vinum set up on on /usr, you cannot mount it - no way. mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported mkdir: /dev/vinum: Operation not supported Can't create /dev/vinum/Control: No such file or directory Can't create /dev/vinum/control: No such file or directory Can't create /dev/vinum/controld: No such file or directory Can't get vinum config: Bad file descriptor Can't open /dev/vinum/Control: Bad file descriptor It is not possible to unmount devfs, so only way is to boot an old kernel (if it works) or boot a cd-rom. This should be definitly in UPDATING. You have to compile a Kernel without devfs. Possible Text: Remove "option devfs" from your KERNEL-CONFIG if you are using vinum and you upgrade from STABLE. Else you cannot mount your vinum-volumes. Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 18: 8:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 1B3DF37B69C for ; Thu, 8 Feb 2001 18:08:02 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id f1927xS09810 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Fri, 9 Feb 2001 03:08:00 +0100 (MET) Received: from cicely5.cicely.de (cicely5.cicely.de [fec0:0:0:104::5]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id f1928JP81298 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Fri, 9 Feb 2001 03:08:27 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.11.1/8.11.1) id f1928Jl82131 for freebsd-current@FreeBSD.ORG; Fri, 9 Feb 2001 03:08:19 +0100 (CET) (envelope-from ticso) Date: Fri, 9 Feb 2001 03:08:19 +0100 From: Bernd Walter To: freebsd-current@FreeBSD.ORG Subject: Re: atomic_ question Message-ID: <20010209030819.C81461@cicely5.cicely.de> References: <20010208182106.B80741@cicely5.cicely.de> <20010209075749.Z90937@gsmx07.alcatel.com.au> <20010208222131.D81067@cicely5.cicely.de> <20010209110004.D90937@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010209110004.D90937@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Fri, Feb 09, 2001 at 11:00:04AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 09, 2001 at 11:00:04AM +1100, Peter Jeremy wrote: > On 2001-Feb-08 22:21:32 +0100, Bernd Walter wrote: > >On sparcv8 you don't have an operation doing conditionaly stores and > >you don't have RMW operations. > >The only way to do is to have a global lock variable on which you spin > >until the current client finishes. > > The SPARC architecture supports SMP so there must be some > synchronisation primitive that works between processors (disabling > interrupts only works on the current processor). Normally the same > primitive can be used to synchronise accesses within the same > processor. I know the older SPARC's had a test-and-set instruction > which was locked RMW - there must be something similar in v8 and v9. sparcv8 has: LDSTUB - which is a atomic load into register and store 0xff SWAP - which exchanges a register with memory atomicly sparcv9 has additionaly the Comapare And Set (CAS) operation which makes it similar in use as alpha. I can't speak for sparcv7 and older but maybe you are refering to sparcv9 with it's CAS operation as an "older" SPARC or have a vendor specific extension in mind. Disabling interrupts will work fine because the reason is to avoid deadlocks. The only thing needed is that the processor holding the lock can't be interrupted until it's finished. If another CPU want's the same lock it can spinwait because the other CPU still gets the chance to release the lock. No doubt the available primitives are enough - but I wanted to know if its neccessary to go the complete ugly way. The sparv8 way for FreeBSDs atomic_ is now clear to me: disable ints for the CPU in question fetch the lock do the real work wmb unlock restore ints Thank you all for making this clear. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 18:38:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 68F0437B401 for ; Thu, 8 Feb 2001 18:37:55 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f192bqf20394; Thu, 8 Feb 2001 18:37:52 -0800 (PST) Date: Thu, 8 Feb 2001 18:37:52 -0800 From: Alfred Perlstein To: Bernd Walter Cc: freebsd-current@FreeBSD.ORG Subject: Re: atomic_ question Message-ID: <20010208183752.F26076@fw.wintelcom.net> References: <20010208182106.B80741@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010208182106.B80741@cicely5.cicely.de>; from ticso@cicely5.cicely.de on Thu, Feb 08, 2001 at 06:21:07PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Bernd Walter [010208 09:21] wrote: > Are atomic_* implementations allowed to spin/sleep? > The question is because some platforms don't have atomic operations > for adding and so on (e.g. sparcv8). Actually, you can use atomic_* on sparc, but you're limited to 24 bits. > The only way to implement them on these platforms is to use a lock. > Now I'm wonder if the use of a sleep mutex is allowed or is a simple > spinning lock the sensefull choice. Either one would work. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 20:33:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.83]) by hub.freebsd.org (Postfix) with ESMTP id 6621E37B4EC for ; Thu, 8 Feb 2001 20:33:39 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id 57D671CB4C0; Fri, 9 Feb 2001 11:33:35 +0700 (JAVT) Date: Fri, 9 Feb 2001 11:33:35 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: buildworld failed Message-ID: <20010209113335.A58091@office.naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dunno whether this happens only to me, but in my machine, latest -CURRENT buildworld target failed with this message: ===> share/monetdef grep -v '^#' < /usr/src/share/monetdef/en_US.ISO_8859-1.src > en_US.ISO_8859-1.out grep -v '^#' < /usr/src/share/monetdef/nl_NL.ISO_8859-1.src > nl_NL.ISO_8859-1.out grep -v '^#' < /usr/src/share/monetdef/ru_RU.KOI8-R.src > ru_RU.KOI8-R.out ===> share/msgdef grep -v '^#' < /usr/src/share/msgdef/en_US.ISO_8859-1.src > en_US.ISO_8859-1.out grep -v '^#' < /usr/src/share/msgdef/nl_NL.ISO_8859-1.src > nl_NL.ISO_8859-1.out grep -v '^#' < /usr/src/share/msgdef/ru_RU.KOI8-R.src > ru_RU.KOI8-R.out ===> share/numericdef make: don't know how to make nl_NL.ISO_8859-1.out. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 20:34:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A80937B65D; Thu, 8 Feb 2001 20:34:05 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA18587; Thu, 8 Feb 2001 23:33:32 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f194X1u42681; Thu, 8 Feb 2001 23:33:01 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14979.29437.518299.842853@grasshopper.cs.duke.edu> Date: Thu, 8 Feb 2001 23:33:01 -0500 (EST) To: Dag-Erling Smorgrav Cc: Julian Elischer , Josef Karthauser , Robert Watson , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Julian Elischer writes: > > I believe that vmware mmaps a region of memory and then somehow syncs > > it to disk. (It is certainly doing something like it here). > > Theory: VMWare mmaps a region of memory corresponding to the virtual > machine's "physical" RAM, then touches every page during startup. > Unless some form of clustering is done, this causes 16384 write > operations for a 64 MB virtual machine... > Pretty much. But the issue is that this should never hit the disk unless we're under memory pressure because it is mapped MAP_NOSYNC (actually the file is unlinked prior to the mmap() and a heuristic in vm_mmap() detects this and sets MAP_NOSYNC). The real problem is that our MAP_NOSYNC doesn't fully work in at least one major case. As I understand it, the technique we use is to set the MAP_ENTRY_NOSYNC in the map entry at mmap time. On a write fault, PG_NOSYNC is set in the page's flags. A lazy msync will skip PG_NOSYNC pages. The problem comes when a page is read from prior to being written to. The page gets mapped in read/write and we don't take a write fault, so the PG_NOSYNC flag never gets set. (This accounts for the flurry of disk i/o shortly after vmware starts). When the pages get sunk to disk, the vnode is locked and the application will freeze in a "vmpfw" The following patch sets PG_NOSYNC on faults other than write faults. This seems to work for my test program, and for vmware (I've only very briefly tested it). Assuming that it is correct, the code around it should be reorganized somewhat. This is against -stable, as I don't have any -current i386s.. Index: vm_fault.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_fault.c,v retrieving revision 1.108.2.2 diff -u -r1.108.2.2 vm_fault.c --- vm_fault.c 2000/08/04 22:31:11 1.108.2.2 +++ vm_fault.c 2001/02/08 23:04:02 @@ -804,6 +804,10 @@ } vm_page_dirty(fs.m); vm_pager_page_unswapped(fs.m); + } else { + if ((fs.entry->eflags & MAP_ENTRY_NOSYNC) && + (fs.m->dirty == 0)) + vm_page_flag_set(fs.m, PG_NOSYNC); } } Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 21:12:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E23FA37B401 for ; Thu, 8 Feb 2001 21:12:16 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f195C4x65541; Thu, 8 Feb 2001 21:12:04 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f195BZw37668; Thu, 8 Feb 2001 21:11:35 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010209113335.A58091@office.naver.co.id> Date: Thu, 08 Feb 2001 21:11:34 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: John Indra Subject: RE: buildworld failed Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Feb-01 John Indra wrote: > Dunno whether this happens only to me, but in my machine, latest -CURRENT > buildworld target failed with this message: That has been fixed, you want to cvsup and try again. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 21:44:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 49A3B37B401 for ; Thu, 8 Feb 2001 21:44:28 -0800 (PST) Received: from elischer.org (reggae-14-106.nv.iinet.net.au [203.59.77.106]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id NAA20961 for ; Fri, 9 Feb 2001 13:44:20 +0800 Message-ID: <3A8383AB.69E0E297@elischer.org> Date: Thu, 08 Feb 2001 21:44:11 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> <20010208122724.A701@tao.org.uk> <3A8297E9.78B93F25@elischer.org> <20010208144759.A7913@tao.org.uk> <20010208145048.A10252@walton.maths.tcd.ie> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > > On Thu, Feb 08, 2001 at 02:47:59PM +0000, Josef Karthauser wrote: > > > what does systat -vmstat or vmstat 1 > > > show? > > > Better still, I guess we could do a linux-truss > > > and see what it's doing... > > > > I believe that it's strace under linux. If someone can provide me > > with a binary of this tool I'll happily run it here and see what > > vmware's doing. > > You could use FreeBSD ktrace and then the linux_kdump port. > > David. I believe truss can do linux binaries which is why I mantionned it. (but I have never done it) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 22:11: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 649A337B491 for ; Thu, 8 Feb 2001 22:10:41 -0800 (PST) Received: (qmail 31377 invoked by uid 666); 9 Feb 2001 06:18:03 -0000 Received: from reggae-14-106.nv.iinet.net.au (HELO elischer.org) (203.59.77.106) by mail.m.iinet.net.au with SMTP; 9 Feb 2001 06:18:03 -0000 Message-ID: <3A8389D5.627F2B69@elischer.org> Date: Thu, 08 Feb 2001 22:10:29 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: "Kyle A.D. Mestery" Cc: Matthew Jacob , "Andrei A. Dergatchev" , current@FreeBSD.ORG Subject: Re: Fibre Channel "Hardware" List... References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Kyle A.D. Mestery" wrote: > > It's true, we at Qlogic (formerly Ancor) do have a 2Gb switch in the > works. We demoed said switch at Comdex. It's pretty impressive watching > your data stream by at 198MB/second! Interestingly enough, said switch > runs Linux as the underlying OS (if I had been at Ancor 1 month before I > got here, we'd be running FreeBSD instead!) that's easy to fix: Can you please send me all your changes and drivers for linux in your product? You may email them to "julian@elischer.org" or put them up at a generally accessible web server for our perusal.. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 8 22:12: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B2DAA37B491 for ; Thu, 8 Feb 2001 22:11:44 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA24970; Fri, 9 Feb 2001 17:11:33 +1100 Date: Fri, 9 Feb 2001 17:10:05 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: kernel trap 12 with interrupts disabled In-Reply-To: <200102081819.f18IJSC10666@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 8 Feb 2001, Alexander Leidinger wrote: > if I run a program compiled with gcc's function profiling option I get > "kernel trap 12 with interrupts disabled". This happens with the standard profiling option -pg. Pagefaults occur in copyin() (called from addupc_task() which is called from ast()) while sched_lock is held. This is not good. Incrementing the profiling counters is supposed to be pushed to ordinary process context so that things like copyin() can work (they have to be able to fault in pages, so they have to be able to sleep...), so using sched_lock to lock things here is wrong. > If I run it withhin X11, the machine deadlocks hard (no response from > the numlock led on the keyboard), withhin a virtual console I get a lot > of "kernel trap ..." and the program runs fine. It's surprising that it doesn't always deadlock. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 0:18:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.83]) by hub.freebsd.org (Postfix) with ESMTP id 3CA6D37B503 for ; Fri, 9 Feb 2001 00:17:53 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id 248791CB513; Fri, 9 Feb 2001 15:17:49 +0700 (JAVT) Date: Fri, 9 Feb 2001 15:17:49 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: buildworld failed. again... Message-ID: <20010209151749.A58102@office.naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Latest -CURRENT buildworld target failed again with this message: ===> share/monetdef grep -v '^#' < /usr/src/share/monetdef/en_US.ISO_8859-1.src > en_US.ISO_8859-1.out grep -v '^#' < /usr/src/share/monetdef/nl_NL.ISO_8859-1.src > nl_NL.ISO_8859-1.out grep -v '^#' < /usr/src/share/monetdef/ru_RU.KOI8-R.src > ru_RU.KOI8-R.out ===> share/msgdef grep -v '^#' < /usr/src/share/msgdef/en_US.ISO_8859-1.src > en_US.ISO_8859-1.out grep -v '^#' < /usr/src/share/msgdef/nl_NL.ISO_8859-1.src > nl_NL.ISO_8859-1.out grep -v '^#' < /usr/src/share/msgdef/ru_RU.KOI8-R.src > ru_RU.KOI8-R.out ===> share/numericdef make: don't know how to make nl_NL.ISO_8859-1.out. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error I thought that this problem has been fixed. Am I the only one experiencing this? /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 1:12: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 17F8537B684 for ; Fri, 9 Feb 2001 01:11:49 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f199BG930571; Fri, 9 Feb 2001 10:11:16 +0100 (CET) (envelope-from asmodai) Date: Fri, 9 Feb 2001 10:11:16 +0100 From: Jeroen Ruigrok van der Werven To: John Indra Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld failed Message-ID: <20010209101116.A30191@lucifer.bart.nl> References: <20010209113335.A58091@office.naver.co.id> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010209113335.A58091@office.naver.co.id>; from john@office.naver.co.id on Fri, Feb 09, 2001 at 11:33:35AM +0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010209 05:35], John Indra (john@office.naver.co.id) wrote: >Dunno whether this happens only to me, but in my machine, latest -CURRENT >buildworld target failed with this message: >===> share/numericdef >make: don't know how to make nl_NL.ISO_8859-1.out. Stop Should be fixed. Apologies. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Fallen into ever-mourn, with these wings so torn, after your day my dawn... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 1:42:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 9661A37B503 for ; Fri, 9 Feb 2001 01:42:23 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f199gLT30727; Fri, 9 Feb 2001 10:42:21 +0100 (CET) (envelope-from asmodai) Date: Fri, 9 Feb 2001 10:42:21 +0100 From: Jeroen Ruigrok van der Werven To: Harti Brandt Cc: freebsd-current@FreeBSD.ORG Subject: Re: Current buildworld broken Message-ID: <20010209104221.B30191@lucifer.bart.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from brandt@fokus.gmd.de on Wed, Feb 07, 2001 at 10:48:12AM +0100 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010207 11:00], Harti Brandt (brandt@fokus.gmd.de) wrote: > >With a freshly CVSuped current I get: > > >===> usr.bin/ncal >cc -O -pipe -Wall -Wmissing-prototypes -fstrict-prototypes -ansi -pedantic -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/ncal/ncal.c >/usr/src/usr.bin/ncal/ncal.c: In function `printeaster': >/usr/src/usr.bin/ncal/ncal.c:390: warning: unknown conversion type character `F' in format You are probably caught in between commits. Always cvsup after such problems, after you waited an hour or so for your favourite cvsup mirror up pick up any further commits, and then try again, and THEN report things like this. Saves traffic. :) -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Fallen into ever-mourn, with these wings so torn, after your day my dawn... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 2:13:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 6678F37B503 for ; Fri, 9 Feb 2001 02:13:29 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA21270; Fri, 9 Feb 2001 11:13:26 +0100 (MET) Date: Fri, 9 Feb 2001 11:13:26 +0100 (CET) From: Harti Brandt To: Jeroen Ruigrok van der Werven Cc: Harti Brandt , Subject: Re: Current buildworld broken In-Reply-To: <20010209104221.B30191@lucifer.bart.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Feb 2001, Jeroen Ruigrok van der Werven wrote: JRvdW>-On [20010207 11:00], Harti Brandt (brandt@fokus.gmd.de) wrote: JRvdW>> JRvdW>>With a freshly CVSuped current I get: JRvdW>> ... JRvdW> JRvdW>You are probably caught in between commits. JRvdW> JRvdW>Always cvsup after such problems, after you waited an hour or so for JRvdW>your favourite cvsup mirror up pick up any further commits, and then try JRvdW>again, and THEN report things like this. Saves traffic. :) I did report after cvsupping twice, but I had a cvs that dumped core in deep subdirectories and did not tell me about that. In my feeling cvs has become quit unstable for a couple of months now... harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 2:57:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from hammerhead.fks.lan (tc6-3-16.cyberport.net [216.166.155.95]) by hub.freebsd.org (Postfix) with ESMTP id D622037B401 for ; Fri, 9 Feb 2001 02:57:34 -0800 (PST) Received: from localhost (myke@localhost) by hammerhead.fks.lan (8.9.3/8.9.3) with ESMTP id DAA97692; Fri, 9 Feb 2001 03:56:10 -0700 (MST) (envelope-from myke@fks.bt) X-Authentication-Warning: hammerhead.fks.lan: myke owned process doing -bs Date: Fri, 9 Feb 2001 03:56:10 -0700 (MST) From: Mike Holling X-Sender: To: Ilya Naumov Cc: Subject: Re: problems with playback via pcm device In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i have Ensoniq ES1371-based soundcard supported by pcm driver and > experience some problems. the sound played is interruped by clicks and > distorsions, and they appear more often when the disk activity is high. > during playback the kernel generates messages like 'pcm0: hwptr went > backwards 64 -> 32'. any ideas? I have similar problems, except the disruptions only seem to occur during keyboard activity. I ran a cvsup while using mpg123 and had no problems, which is pretty impressive since the machine is a P133. However, even a small amount of typing causes noticeable audio glitches. This happens both with a ES1371 and an old SB16 ISA card. It seems I may also be losing keystrokes from the keyboard, though I haven't confirmed it's not a problem with the keyboard itself. - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 3: 5: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9F8D137B401 for ; Fri, 9 Feb 2001 03:04:45 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f19B4Px72952; Fri, 9 Feb 2001 03:04:25 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f19B3xj42543; Fri, 9 Feb 2001 03:03:59 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 09 Feb 2001 03:03:59 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Mike Holling Subject: Re: problems with playback via pcm device Cc: current@FreeBSD.ORG, Ilya Naumov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Feb-01 Mike Holling wrote: >> i have Ensoniq ES1371-based soundcard supported by pcm driver and >> experience some problems. the sound played is interruped by clicks and >> distorsions, and they appear more often when the disk activity is high. >> during playback the kernel generates messages like 'pcm0: hwptr went >> backwards 64 -> 32'. any ideas? > > I have similar problems, except the disruptions only seem to occur during > keyboard activity. I ran a cvsup while using mpg123 and had no problems, > which is pretty impressive since the machine is a P133. However, even a > small amount of typing causes noticeable audio glitches. This happens > both with a ES1371 and an old SB16 ISA card. It seems I may also be > losing keystrokes from the keyboard, though I haven't confirmed it's not a > problem with the keyboard itself. This could be related to the entropy gathering by the random kthread. Have you tried removing the random device from your kernel? > - Mike -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 3:33: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id D363937B65D; Fri, 9 Feb 2001 03:32:47 -0800 (PST) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by avias.com (8.11.2/8.11.2) with ESMTP id f19BWhG18973; Fri, 9 Feb 2001 14:32:44 +0300 (MSK) (envelope-from camel@avias.com) Date: Fri, 9 Feb 2001 14:32:43 +0300 (MSK) From: Ilya Naumov To: John Baldwin Cc: Mike Holling , Subject: Re: problems with playback via pcm device In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Feb 2001, John Baldwin wrote: > >> i have Ensoniq ES1371-based soundcard supported by pcm driver and > >> experience some problems. the sound played is interruped by clicks and > >> distorsions, and they appear more often when the disk activity is high. > >> during playback the kernel generates messages like 'pcm0: hwptr went > >> backwards 64 -> 32'. any ideas? > This could be related to the entropy gathering by the random kthread. Have you > tried removing the random device from your kernel? yes, i've tried. no effect. sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 3:37: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from hammerhead.fks.lan (tc6-3-16.cyberport.net [216.166.155.95]) by hub.freebsd.org (Postfix) with ESMTP id D700237B69C; Fri, 9 Feb 2001 03:36:50 -0800 (PST) Received: from localhost (myke@localhost) by hammerhead.fks.lan (8.9.3/8.9.3) with ESMTP id EAA97757; Fri, 9 Feb 2001 04:35:49 -0700 (MST) (envelope-from myke@fks.bt) X-Authentication-Warning: hammerhead.fks.lan: myke owned process doing -bs Date: Fri, 9 Feb 2001 04:35:48 -0700 (MST) From: Mike Holling X-Sender: To: Ilya Naumov Cc: John Baldwin , Subject: Re: problems with playback via pcm device In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This could be related to the entropy gathering by the random kthread. Have you > > tried removing the random device from your kernel? > > yes, i've tried. no effect. This seems to have fixed the problem for me, thanks! I'm using the machine now and am getting no keyboard-related glitches in audio, just when the machine gets busy (which is fine since I don't expect a P133 to be able to do too much else when playing MP3's). - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 4:16:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id 43AE237B6E7; Fri, 9 Feb 2001 04:16:19 -0800 (PST) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id VAA76642; Fri, 9 Feb 2001 21:16:17 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id VAA01834; Fri, 9 Feb 2001 21:16:17 +0900 (JST) To: current@FreeBSD.ORG Cc: trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: <20010208102010.A12099@panzer.kdm.org> References: <20010207171156.A72756@cicely5.cicely.de> <20010208214259C.non@ever.sanda.gr.jp> <20010208102010.A12099@panzer.kdm.org> X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010209211616W.non@ever.sanda.gr.jp> Date: Fri, 09 Feb 2001 21:16:16 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 51 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Kenneth D. Merry" Subject: Re: od driver for -CURRENT > > By the way, in Japanese users mailing list, some said that `da' does > > not check whether a medium is writerable or not (write > > protected). If you mount a write protected medium with -rw, it will > > lead bad condition when you do umount. > > Hmm, can you demonstrate the problem? The write-protect check in the od > driver is one of the things that the da driver doesn't have. I figured it > wouldn't really be necessary, since any attempted writes would be returned > with errors. The problem is you cannot unmount after -rw mount with a write-protected medium. Below has been done also in 4.2-RELEASE with GENERIC kernel, 1. Insert a write protected medium, 2. mount /dev/da0s1c /mnt, cel# mount /dev/da0s1c /mnt 3. umount /mnt cel# umount /mnt umount: unmount of /mnt failed: Input/output error cel# umount /mnt umount: unmount of /mnt failed: Input/output error Umount does not success and `Write protected' messages continue to appear 4. reboot (umount fails) In /var/log/mesages, Feb 9 21:10:28 cel /kernel: (da0:ahc0:0:3:0): WRITE(06). CDB: a 0 7 c9 2 0 Feb 9 21:10:28 cel /kernel: (da0:ahc0:0:3:0): DATA PROTECT asc:27,0 Feb 9 21:10:28 cel /kernel: (da0:ahc0:0:3:0): Write protected Feb 9 21:10:35 cel /kernel: (da0:ahc0:0:3:0): WRITE(06). CDB: a 0 7 c9 2 0 Feb 9 21:10:35 cel /kernel: (da0:ahc0:0:3:0): DATA PROTECT asc:27,0 Feb 9 21:10:35 cel /kernel: (da0:ahc0:0:3:0): Write protected Feb 9 21:10:35 cel /kernel: (da0:ahc0:0:3:0): WRITE(06). CDB: a 0 7 c9 2 0 Feb 9 21:10:35 cel /kernel: (da0:ahc0:0:3:0): DATA PROTECT asc:27,0 Feb 9 21:10:35 cel /kernel: (da0:ahc0:0:3:0): Write protected Feb 9 21:10:40 cel /kernel: (da0:ahc0:0:3:0): WRITE(06). CDB: a 0 0 49 4 0 Feb 9 21:10:40 cel /kernel: (da0:ahc0:0:3:0): DATA PROTECT asc:27,0 Feb 9 21:10:40 cel /kernel: (da0:ahc0:0:3:0): Write protected Feb 9 21:11:09 cel /kernel: (da0:ahc0:0:3:0): WRITE(06). CDB: a 0 0 49 4 0 Feb 9 21:11:09 cel /kernel: (da0:ahc0:0:3:0): DATA PROTECT asc:27,0 Feb 9 21:11:09 cel /kernel: (da0:ahc0:0:3:0): Write protected Feb 9 21:11:38 cel /kernel: (da0:ahc0:0:3:0): WRITE(06). CDB: a 0 0 49 4 0 Feb 9 21:11:38 cel /kernel: (da0:ahc0:0:3:0): DATA PROTECT asc:27,0 Feb 9 21:11:38 cel /kernel: (da0:ahc0:0:3:0): Write protected Hope this helps. // Noriaki Mitsunaga // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 6:14:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 808DD37B87A for ; Fri, 9 Feb 2001 06:14:17 -0800 (PST) Received: (qmail 3748 invoked by uid 1000); 9 Feb 2001 14:07:58 -0000 Date: Fri, 9 Feb 2001 15:07:57 +0100 From: Andrea Campi To: Warner Losh Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010209150757.A470@webcom.it> References: <20010208103433.B1088@webcom.it> <20010208021930.C13541@webcom.it> <20010208014108.A13541@webcom.it> <20010208021930.C13541@webcom.it> <200102080507.f1857C998723@harmony.village.org> <20010208103433.B1088@webcom.it> <200102081656.f18Guh941601@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102081656.f18Guh941601@harmony.village.org>; from imp@harmony.village.org on Thu, Feb 08, 2001 at 09:56:43AM -0700 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 08, 2001 at 09:56:43AM -0700, Warner Losh wrote: > In message <20010208103433.B1088@webcom.it> Andrea Campi writes: > : Will try again with cardbus and report. So are you saying it SHOULD work > : (as far as my chipset is behaving, I suppose)? > > Cardbus works, more or less, on -current right now. Some cards just > work, other cards need help. I keep meaning to do a survey, but > haven't found the time to do it yet. Of course cardbus per se is working, I meant irq sharing when using cardbus... And, it's not working for me, i.e. my pccard using cardbus is working on irq 11, my csa audio card is probed and configured on irq 11, but audio playback is not. If you or anybody else has time and is willing to debug this I am available, but I understand there are a lot of things which are more urgent so I will just wait. On a separate note, I am thinking about adapting rc.pccard to carbus, or writing a new rc.cardbus; is anybody working on this? Going back to the original thread, removing my card under cardbus simply hangs my laptop. I have no idea how to debug this. Bye, Andrea -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 7:28:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6DE7C37B823; Fri, 9 Feb 2001 07:15:07 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA26411; Fri, 9 Feb 2001 10:14:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f19FELc01925; Fri, 9 Feb 2001 10:14:21 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14980.2381.849005.313177@grasshopper.cs.duke.edu> Date: Fri, 9 Feb 2001 10:14:21 -0500 (EST) To: freebsd-current@FreeBSD.ORG Cc: Dag-Erling Smorgrav , Julian Elischer , Josef Karthauser , Robert Watson , Brian Somers , Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O In-Reply-To: <14979.29437.518299.842853@grasshopper.cs.duke.edu> References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> <14979.29437.518299.842853@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin writes: > > Dag-Erling Smorgrav writes: > > Julian Elischer writes: > > > I believe that vmware mmaps a region of memory and then somehow syncs > > > it to disk. (It is certainly doing something like it here). > > > > Theory: VMWare mmaps a region of memory corresponding to the virtual > > machine's "physical" RAM, then touches every page during startup. > > Unless some form of clustering is done, this causes 16384 write > > operations for a 64 MB virtual machine... > > > > Pretty much. But the issue is that this should never hit the disk > unless we're under memory pressure because it is mapped MAP_NOSYNC > (actually the file is unlinked prior to the mmap() and a heuristic in > vm_mmap() detects this and sets MAP_NOSYNC). I take it back. At least with the latest version of vmware, it is apparently not mapped MAP_NOSYNC. I think they've moved from mmap'ing a file in $TMPDIR to just using the CONFIG.std save/resume file. Perhaps this is only if you have resumed from a suspended state... I haven't checked that out yet. At any rate, hacking linux_mmap to ad MAP_NOSYNC to mmaped files, in combination with yesterdays patch, appears to improve perf. considerably. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 8:23:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id B8A4C37B6B3 for ; Fri, 9 Feb 2001 07:24:20 -0800 (PST) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 14RFPH-0006AF-00; Fri, 09 Feb 2001 16:24:19 +0100 Received: from b8422.pppool.de ([213.7.132.34] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.22 #1) id 14RFPG-0000Jp-00; Fri, 09 Feb 2001 16:24:18 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.2/8.11.2) with ESMTP id f19D52T02449; Fri, 9 Feb 2001 14:05:03 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200102091305.f19D52T02449@Magelan.Leidinger.net> Date: Fri, 9 Feb 2001 14:05:01 +0100 (CET) From: Alexander Leidinger Subject: Re: kernel trap 12 with interrupts disabled To: bde@zeta.org.au Cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Feb, Bruce Evans wrote: > Pagefaults occur in copyin() (called from addupc_task() which is called > from ast()) while sched_lock is held. This is not good. Incrementing > the profiling counters is supposed to be pushed to ordinary process > context so that things like copyin() can work (they have to be able > to fault in pages, so they have to be able to sleep...), so using > sched_lock to lock things here is wrong. Are we talking about /sys/kern/kern_clock.c: statclock()? I'm not familiar with the kernel and that's the only place I find something related to profiling if I grep for "profil" and look at the results. If yes, what is to to? >> If I run it withhin X11, the machine deadlocks hard (no response from >> the numlock led on the keyboard), withhin a virtual console I get a lot >> of "kernel trap ..." and the program runs fine. > > It's surprising that it doesn't always deadlock. First I thought I have a hardware problem, I was able to profile the program 4-5 times withhin X11 at a day before. Without changing anything except the options to the program I wasn't able to profile it later. Bye, Alexander. -- Loose bits sink chips. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 8:32: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from syncopation-03.iinet.net.au (syncopation-03.iinet.net.au [203.59.24.49]) by hub.freebsd.org (Postfix) with SMTP id 2489537BBFF for ; Fri, 9 Feb 2001 08:15:52 -0800 (PST) Received: (qmail 10745 invoked by uid 666); 9 Feb 2001 16:23:12 -0000 Received: from reggae-03-225.nv.iinet.net.au (HELO elischer.org) (203.59.78.225) by mail.m.iinet.net.au with SMTP; 9 Feb 2001 16:23:12 -0000 Message-ID: <3A8417B3.126F47AB@elischer.org> Date: Fri, 09 Feb 2001 08:15:47 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG, Dag-Erling Smorgrav , Josef Karthauser , Robert Watson , Brian Somers , Bruce Evans , freebsd-hackers@FreeBSD.ORG Subject: Re: What's changed recently with vmware/linuxemu/file I/O References: <20010208113519.A789@tao.org.uk> <3A828C2C.F7CDA809@elischer.org> <14979.29437.518299.842853@grasshopper.cs.duke.edu> <14980.2381.849005.313177@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > > Andrew Gallatin writes: > > > > Dag-Erling Smorgrav writes: > > > Julian Elischer writes: > > > > I believe that vmware mmaps a region of memory and then somehow syncs > > > > it to disk. (It is certainly doing something like it here). > > > > > > Theory: VMWare mmaps a region of memory corresponding to the virtual > > > machine's "physical" RAM, then touches every page during startup. > > > Unless some form of clustering is done, this causes 16384 write > > > operations for a 64 MB virtual machine... > > > > > > > Pretty much. But the issue is that this should never hit the disk > > unless we're under memory pressure because it is mapped MAP_NOSYNC > > (actually the file is unlinked prior to the mmap() and a heuristic in > > vm_mmap() detects this and sets MAP_NOSYNC). > > I take it back. At least with the latest version of vmware, it is > apparently not mapped MAP_NOSYNC. I think they've moved from > mmap'ing a file in $TMPDIR to just using the CONFIG.std save/resume > file. Perhaps this is only if you have resumed from a suspended > state... I haven't checked that out yet. > > At any rate, hacking linux_mmap to ad MAP_NOSYNC to mmaped files, in > combination with yesterdays patch, appears to improve > perf. considerably. I don't like the sound of that hack.. are they doing something in Linux to tell Linux to not sync it? I nkow it's gross but could we only do that hack if it'a vmware? (probably should be on -emulation) > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 9:21:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (brian.inet.it [213.92.4.195]) by hub.freebsd.org (Postfix) with SMTP id 1A50337D563 for ; Fri, 9 Feb 2001 09:21:10 -0800 (PST) Received: (qmail 2346 invoked by uid 1000); 9 Feb 2001 17:14:53 -0000 Date: Fri, 9 Feb 2001 18:14:52 +0100 From: Andrea Campi To: John Baldwin Cc: Jim Bloom , "Crist J. Clark" , current@FreeBSD.org Subject: Re: Kernel Panic from Yesterday's CVSup Message-ID: <20010209181451.B500@webcom.it> References: <20010208103221.A1088@webcom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Feb 08, 2001 at 11:12:59AM -0800 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here I am again. Didn't get as far as a login prompt, I have a panic when > > qmail > > starts up: > > Turn MUTEX_DEBUG off. It appears to be broken atm. Done, no panic, and performance is bad but not so bad. -- Reboot America. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 10:23:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 4AADF37B401 for ; Fri, 9 Feb 2001 10:23:19 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id 348CDD34; Fri, 9 Feb 2001 10:23:17 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id KAA11837; Fri, 9 Feb 2001 10:23:16 -0800 (PST) Message-ID: <3A843594.B28776D8@cup.hp.com> Date: Fri, 09 Feb 2001 10:23:16 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Szilveszter Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: Dangling symlink in /usr/compat/linux References: <3A7D28EA.9EF46BAE@gorean.org> <20010204112342.A15191@petra.hos.u-szeged.hu> <3A7DFC47.C76A9872@FreeBSD.org> <20010205091559.A5563@petra.hos.u-szeged.hu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [taken to -ports] Szilveszter Adam wrote: > > @exec ln -sf ../X11R6/lib/X11 %D/usr/lib/X11 > @unexec rm %D/usr/lib/X11 The link is correct. On a Redhat 6.2 system: dhcp00% cd /mnt/usr/lib dhcp00% ls -al X11 lrwxrwxrwx 1 root wheel 16 Jul 18 2000 X11 -> ../X11R6/lib/X11 dhcp00% more /mnt/etc/redhat-release Red Hat Linux release 6.2 (Zoot) > Solution: ? ( Maybe create the directory once we symlink to it? Seems like > a good idea... ) Can you tell me what the problem was. I missed that. > (Most probably this problem never surfaced before because the maintainers > had both ports installed on their systems.) I do have both ports in fact :-) -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 10:26:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 665C137B4EC for ; Fri, 9 Feb 2001 10:26:10 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id FAA31083; Sat, 10 Feb 2001 05:26:02 +1100 Date: Sat, 10 Feb 2001 05:25:40 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: kernel trap 12 with interrupts disabled In-Reply-To: <200102091305.f19D52T02449@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Feb 2001, Alexander Leidinger wrote: > On 9 Feb, Bruce Evans wrote: > > > Pagefaults occur in copyin() (called from addupc_task() which is called > > from ast()) while sched_lock is held. This is not good. Incrementing > > the profiling counters is supposed to be pushed to ordinary process > > context so that things like copyin() can work (they have to be able > > to fault in pages, so they have to be able to sleep...), so using > > sched_lock to lock things here is wrong. > > Are we talking about /sys/kern/kern_clock.c: statclock()? I'm not No :-). ast() is in /sys/${MACHINE}/${MACHINE}/trap.c. Incrementing the profiling counters is much too hard to do in statclock(), since statclock() is a fast interrupt handler, so statclock() only schedules an AST to do the increment. The scheduling of the AST is rather tangled and pessimized to support optimizations that aren't possible while statclock() is a fast interrupt handler. See addupc_intr(), fuswintr(), suswintr() and need_proftick(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 11: 4: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id EB8DD37B69C for ; Fri, 9 Feb 2001 11:03:38 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.1/8.11.1) id f18NQko86416; Thu, 8 Feb 2001 23:26:46 GMT (envelope-from nik) Date: Thu, 8 Feb 2001 23:26:46 +0000 From: Nik Clayton To: "Michael C . Wu" Cc: Leif Neland , freebsd-current@freebsd.org Subject: Re: pkg_update Message-ID: <20010208232645.A86390@canyon.nothing-going-on.org> References: <20010207202335.C20454@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010207202335.C20454@peorth.iteration.net>; from keichii@iteration.net on Wed, Feb 07, 2001 at 08:23:35PM -0600 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 07, 2001 at 08:23:35PM -0600, Michael C . Wu wrote: > On Thu, Feb 08, 2001 at 01:56:11AM +0100, Leif Neland scribbled: > | It seems pkg_update is only usable when installing from packages, not from > | ports. > > Because it is a package update system. If you want to update > from the ports, use 'pkg_version -c |sh' Never, ever, *ever* do this. "pkg_version -c" is a hack to make cut-n-paste easier. The output is sorted alphabetically and no notice is taken of dependencies between different ports. *If* you know what you're doing then -c is useful to help save you some typing. But you should never run the commands automatically. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 11: 4:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 6BCC037B69B; Fri, 9 Feb 2001 11:04:14 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id TAA26172; Fri, 9 Feb 2001 19:45:21 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14RIXp-0007qw-00; Fri, 09 Feb 2001 19:45:21 +0100 Date: Fri, 9 Feb 2001 19:45:21 +0100 From: Szilveszter Adam To: Marcel Moolenaar Cc: freebsd-current@FreeBSD.ORG, ports@freebsd.org Subject: Re: Dangling symlink in /usr/compat/linux Message-ID: <20010209194521.D27987@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , Marcel Moolenaar , freebsd-current@FreeBSD.ORG, ports@freebsd.org References: <3A7D28EA.9EF46BAE@gorean.org> <20010204112342.A15191@petra.hos.u-szeged.hu> <3A7DFC47.C76A9872@FreeBSD.org> <20010205091559.A5563@petra.hos.u-szeged.hu> <3A843594.B28776D8@cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A843594.B28776D8@cup.hp.com>; from marcel@cup.hp.com on Fri, Feb 09, 2001 at 10:23:16AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Marcel, On Fri, Feb 09, 2001 at 10:23:16AM -0800, Marcel Moolenaar wrote: > [taken to -ports] I see it nowhere in the headers, so I am going to add a Cc: for it... > The link is correct. On a Redhat 6.2 system: > > dhcp00% cd /mnt/usr/lib > dhcp00% ls -al X11 > lrwxrwxrwx 1 root wheel 16 Jul 18 2000 X11 -> ../X11R6/lib/X11 > dhcp00% more /mnt/etc/redhat-release > Red Hat Linux release 6.2 (Zoot) Which is not the point:-) > > Solution: ? ( Maybe create the directory once we symlink to it? Seems like > > a good idea... ) > > Can you tell me what the problem was. I missed that. The problem if you want it that way, is that although the symlink is created upon installing linux_base, the directory it points to is not. Hence the ${SUBJECT} about a "Dangling symlink". (If you install linux_devtools, the directory is created, since there is a subdir in it. That's why the problem may be harder to detect:-) Maybe it would be a good idea to create a (empty if need be) /usr/compat/linux/usr/X11R6/lib/X11 directory upon installing linux_base? I have no idea how this came up btw, maybe some installation of some third-party sw tried to follow the symlink and got confused? I just tried to react to the problem at hand... > > (Most probably this problem never surfaced before because the maintainers > > had both ports installed on their systems.) > > I do have both ports in fact :-) Me too, that's why I at first very self-confidently posted something along the lines of "It works for me!" which earned blank stares from just about anybody else:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 11:25:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 02FB337B698; Fri, 9 Feb 2001 11:24:55 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA01229; Sat, 10 Feb 2001 06:24:43 +1100 Date: Sat, 10 Feb 2001 06:24:20 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: non@ever.sanda.gr.jp Cc: current@FreeBSD.ORG, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: <20010209211616W.non@ever.sanda.gr.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Feb 2001 non@ever.sanda.gr.jp wrote: > From: "Kenneth D. Merry" > Subject: Re: od driver for -CURRENT > > > By the way, in Japanese users mailing list, some said that `da' does > > > not check whether a medium is writerable or not (write > > > protected). If you mount a write protected medium with -rw, it will > > > lead bad condition when you do umount. > > > > Hmm, can you demonstrate the problem? The write-protect check in the od > > driver is one of the things that the da driver doesn't have. I figured it > > wouldn't really be necessary, since any attempted writes would be returned > > with errors. > > The problem is you cannot unmount after -rw mount with a write-protected > medium. This is essentially the same bug that causes problems for writing to write protected media or unwriteable blocks using the block device. There are many open PRs about this bug. It used to cause panics, but now it just causes endless retries (except under RELENG_3 where it still causes panics). The fix is to not retry endlessly. The correct number of retries is not clear. RELENG_2 has the slightly wrong fix of not retrying at all (in the vfs layer). Not retrying is probably right for most errors on physical blocks, but for write protect errors you might want to physically change the write protection so retrying (not too often) for a minute or two might be best. Anyway, there needs to be a way to stop the retries. I first saw this problem for a floppy driver that I wrote in 1984. It retried endlessly. Users did not like this :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 14:32:40 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by hub.freebsd.org (Postfix) with ESMTP id C714937B503; Fri, 9 Feb 2001 14:32:21 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA05150; Fri, 9 Feb 2001 14:32:17 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f19MW0X23361; Fri, 9 Feb 2001 14:32:00 -0800 (PST) (envelope-from bmah) Message-Id: <200102092232.f19MW0X23361@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: Nik Clayton Cc: "Michael C . Wu" , Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: pkg_update In-Reply-To: <20010208232645.A86390@canyon.nothing-going-on.org> References: <20010207202335.C20454@peorth.iteration.net> <20010208232645.A86390@canyon.nothing-going-on.org> Comments: In-reply-to Nik Clayton message dated "Thu, 08 Feb 2001 23:26:46 +0000." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-327729888P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 09 Feb 2001 14:32:00 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-327729888P Content-Type: text/plain; charset=us-ascii If memory serves me right, Nik Clayton wrote: > On Wed, Feb 07, 2001 at 08:23:35PM -0600, Michael C . Wu wrote: > > On Thu, Feb 08, 2001 at 01:56:11AM +0100, Leif Neland scribbled: > > | It seems pkg_update is only usable when installing from packages, not fro > m > > | ports. > > > > Because it is a package update system. If you want to update > > from the ports, use 'pkg_version -c |sh' > > Never, ever, *ever* do this. > > "pkg_version -c" is a hack to make cut-n-paste easier. The output is > sorted alphabetically and no notice is taken of dependencies between > different ports. Plus it's been known to wipe out Ports Upgrade kits. This was particularly bad when some upgrade kits replaced little non-essentials like ld*.so, things like that. I just put a big fat warning to this effect followed by "exit 1" at the start of the commands output, and committed to -CURRENT. I'll MFC early next week. Bruce. --==_Exmh_-327729888P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6hG/g2MoxcVugUsMRAkr2AJ0Q5985cUY0yrTLZLNBfLKOuwJBrwCgy+rp P+92RBVLmyChIQK1T2CSHTs= =AZ8F -----END PGP SIGNATURE----- --==_Exmh_-327729888P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 15: 2:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 112A437B401 for ; Fri, 9 Feb 2001 15:02:24 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) id f19N2MI77324 for freebsd-current@FreeBSD.ORG.AVP; Sat, 10 Feb 2001 00:02:22 +0100 (CET) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.11.2/8.11.2) with UUCP id f19N2Lw77302; Sat, 10 Feb 2001 00:02:21 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.1/8.11.0) with SMTP id f19N2Ax69220; Sat, 10 Feb 2001 00:02:11 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <00c501c092ec$678e73a0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Nik Clayton" , "Michael C . Wu" Cc: References: <20010207202335.C20454@peorth.iteration.net> <20010208232645.A86390@canyon.nothing-going-on.org> Subject: Re: pkg_update Date: Sat, 10 Feb 2001 00:02:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by ns.internet.dk id f19N2Lw77302 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Feb 07, 2001 at 08:23:35PM -0600, Michael C . Wu wrote: > > On Thu, Feb 08, 2001 at 01:56:11AM +0100, Leif Neland scribbled: > > | It seems pkg_update is only usable when installing from packages, not from > > | ports. > > > > Because it is a package update system. If you want to update > > from the ports, use 'pkg_version -c |sh' > > Never, ever, *ever* do this. > Just installing a new version of a port seems to work. Couldn't it be made possible to use just the update-of-dependencies part of pkg_update without doing the pkg_delete/pkg_install bit? Perhaps I'll try... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 16:21:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id 81A9D37B6D2; Fri, 9 Feb 2001 16:21:31 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id QAA29719; Fri, 9 Feb 2001 16:21:33 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f1A0LVS25017; Fri, 9 Feb 2001 16:21:31 -0800 (PST) (envelope-from bmah) Message-Id: <200102100021.f1A0LVS25017@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: "Leif Neland" Cc: "Nik Clayton" , "Michael C . Wu" , freebsd-ports@FreeBSD.ORG Subject: Re: pkg_update In-Reply-To: <00c501c092ec$678e73a0$0e00a8c0@neland.dk> References: <20010207202335.C20454@peorth.iteration.net> <20010208232645.A86390@canyon.nothing-going-on.org> <00c501c092ec$678e73a0$0e00a8c0@neland.dk> Comments: In-reply-to "Leif Neland" message dated "Sat, 10 Feb 2001 00:02:39 +0100." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-79411961P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 09 Feb 2001 16:21:31 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_-79411961P Content-Type: text/plain; charset=us-ascii [moved to -ports] If memory serves me right, "Leif Neland" wrote: > Couldn't it be made possible to use just the update-of-dependencies part of p > kg_update without doing the pkg_delete/pkg_install bit? > > Perhaps I'll try... Manipulating the bits is relatively straightforward. Doing so in a meaningful way, and being able to cover all the edge cases, that's quite hard (as I've just re-learned). If you browse through the archives of -ports for the last few days, you'll get an idea of some of the problems. Every few months, the topic comes up, and discussion is just tapering off from the last round. Not to say you shouldn't work on this problem...just saying that it's not quite as straightforward as most people (myself included) think when they first tackle it. Cheers, Bruce. --==_Exmh_-79411961P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6hImK2MoxcVugUsMRAvR/AKDqAOfVNhWx0jVbTN6TnPDV+9ArXgCdG9cv RlvxBKFAHu+6wDRizamoiDo= =qSgS -----END PGP SIGNATURE----- --==_Exmh_-79411961P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 17:37:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id B96BA37B6A1 for ; Fri, 9 Feb 2001 17:37:30 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f1A1bTR08154; Sat, 10 Feb 2001 01:37:29 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.2/8.11.1) with ESMTP id f19HgfN01528; Fri, 9 Feb 2001 17:42:41 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200102091742.f19HgfN01528@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brian Somers Cc: domi@saargate.de, freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: Strange fopen() behaviour In-Reply-To: Message from Brian Somers of "Tue, 06 Feb 2001 03:23:59 GMT." <200102060324.f163O0610286@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Feb 2001 17:42:41 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to follow up, this was fixed with v1.9 of src/lib/libc/stdio/findfp.c Thanks Maxim ! > > I've cc'd -current as I think something more sinister is going on. > > To recap, I'm having trouble running xsane on -current from about two > > days ago. fopen() is failing... > > > > The attached patch exposes more about what's wrong. Interestingly > > enough, the file it's trying to create is in /tmp (mode 1777, > > separate filesystem), and according to truss: > > > > lstat("/tmp//preview-level-0-15-b924dc",0xbfbfe894) ERR#2 'No such file or directory' > > umask(0x7f) = 7 (0x7) > > /tmp//preview-level-0-15-b924dc17767-microtek:_dev_scanner.ppm: could not create for preview-level 0: No such file or directory > > write(2,0xbfbfe48c,128) = 128 (0x80) > > getuid() = 15 (0xf) > > lstat("/tmp//preview-level-1-15-jNO6zx",0xbfbfe894) ERR#2 'No such file or directory' > > umask(0x7f) = 127 (0x7f) > > /tmp//preview-level-1-15-jNO6zx09158-microtek:_dev_scanner.ppm: could not create for preview-level 1: No such file or directory > > write(2,0xbfbfe48c,128) = 128 (0x80) > > getuid() = 15 (0xf) > > lstat("/tmp//preview-level-2-15-CO6k7w",0xbfbfe894) ERR#2 'No such file or directory' > > umask(0x7f) = 127 (0x7f) > > break(0x8134000) = 0 (0x0) > > /tmp//preview-level-2-15-CO6k7w39017-microtek:_dev_scanner.ppm: could not create for preview-level 2: No such file or directory > > write(2,0xbfbfe48c,128) = 128 (0x80) > > > > fopen() is failing after calling lstat() (I assume via _open()) !!! > > As if the "wb" didn't mean O_CREAT ??!? Very strange. > [.....] > > And just to top it all, I see this in my daily report (first time > I've ever seen it on this machine...): > > dev.lan.Awfulhak.org kernel log messages: > > microuptime() went backwards (18415.166882 -> 18415.158249) > > microuptime() went backwards (18490.192910 -> 18490.187579) > > microuptime() went backwards (19572.644000 -> 19572.638237) > > microuptime() went backwards (19878.637972 -> 19878.637330) > > microuptime() went backwards (20043.869158 -> 20043.868971) > > microuptime() went backwards (20074.159108 -> 20074.152253) > > microuptime() went backwards (20210.078270 -> 20210.072448) > -- > Brian > > Don't _EVER_ lose your sense of humour ! -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 20:28:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 01F1837B401; Fri, 9 Feb 2001 20:28:21 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1A4PlW10042; Fri, 9 Feb 2001 21:25:47 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102100425.f1A4PlW10042@harmony.village.org> To: Andrea Campi Subject: Re: Kernel Panic from Yesterday's CVSup Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 09 Feb 2001 15:07:57 +0100." <20010209150757.A470@webcom.it> References: <20010209150757.A470@webcom.it> <20010208103433.B1088@webcom.it> <20010208021930.C13541@webcom.it> <20010208014108.A13541@webcom.it> <20010208021930.C13541@webcom.it> <200102080507.f1857C998723@harmony.village.org> <20010208103433.B1088@webcom.it> <200102081656.f18Guh941601@harmony.village.org> Date: Fri, 09 Feb 2001 21:25:47 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010209150757.A470@webcom.it> Andrea Campi writes: : Of course cardbus per se is working, I meant irq sharing when using cardbus... Works great for me. : And, it's not working for me, i.e. my pccard using cardbus is working on irq : 11, my csa audio card is probed and configured on irq 11, but audio playback : is not. Audio and current is also dicy. : just wait. On a separate note, I am thinking about adapting rc.pccard to : carbus, or writing a new rc.cardbus; is anybody working on this? /sbin/devd :-) : Going back to the original thread, removing my card under cardbus simply : hangs my laptop. I have no idea how to debug this. Neither do I. I make guesses until it is working. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 20:44:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 0C1DD37B401; Fri, 9 Feb 2001 20:43:59 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.2/8.11.2) with ESMTP id f1A4hqj00429; Fri, 9 Feb 2001 20:43:57 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Fri, 09 Feb 2001 20:43:51 -0800 To: current@FreeBSD.ORG From: Manfred Antar Subject: Current SMP Kernel panics Cc: smp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A current kernel built 10 mins ago form fresh cvsup panics: APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 IPsec: Initialized Security Association Processing. panic: mutex sched lock not owned at ../../kern/kern_synch.c:175 cpuid = 0; lapic.id = 00000000 syncing disks... done Uptime: 0s dpt0: Shutting down (mode 100) HBA. Please wait... dpt0: Controller was warned of shutdown and is now disabled Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 9 22:58:35 2001 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 1B17637B491; Fri, 9 Feb 2001 22:58:18 -0800 (PST) Date: Fri, 9 Feb 2001 22:58:18 -0800 From: "John W. De Boskey" To: current@FreeBSD.org Subject: disklabel.c & disklabel.8 patch Message-ID: <20010209225817.A24289@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been using the disklabel.c patch which allows easier configuration by being able to specify a new disklabel of the form: # size offset fstype [fsize bsize bps/cpg] a: 400M 0 4.2BSD 4096 16384 75 # (Cyl. 0 - 812*) b: 1G * swap c: * * unused e: 204800 * 4.2BSD f: 5g * 4.2BSD g: * * 4.2BSD An up-to-date copy of disklabel.c can be found at: http://people.freebsd.org/~jwd/disklabel.c The man page can be found at: http://people.freebsd.org/~jwd/disklabel/disklabel.8 or in html format: http://people.freebsd.org/~jwd/disklabel/disklabel.8.html Patch files: http://people.freebsd.org/~jwd/disklabel/disklabel.c.patch http://people.freebsd.org/~jwd/disklabel/disklabel.8.patch I'd like to commit these if no one sees any major problems with them. These patches are the original work of Randell Jesup, and I believe Matt Dillon, with additional work by Warner Losh. Please let me know if I've left someone out. Incorporated into this is the fix for PR bin/22727. A simple one character fix. Comments Welcome! -John ps: The .html file was generated via groff. It seems to have some interesting side effects with the '[' and ']' characters. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 5:50:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id E8F3837B491; Sat, 10 Feb 2001 05:50:12 -0800 (PST) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id WAA24055; Sat, 10 Feb 2001 22:50:10 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id WAA21251; Sat, 10 Feb 2001 22:50:10 +0900 (JST) To: current@FreeBSD.ORG Cc: trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: References: <20010209211616W.non@ever.sanda.gr.jp> X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010210225009W.non@ever.sanda.gr.jp> Date: Sat, 10 Feb 2001 22:50:09 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 25 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Bruce Evans Date: Sat, 10 Feb 2001 06:24:20 +1100 (EST) > On Fri, 9 Feb 2001 non@ever.sanda.gr.jp wrote: > > From: "Kenneth D. Merry" > > > Hmm, can you demonstrate the problem? The write-protect check in the od > > > driver is one of the things that the da driver doesn't have. I figured it > > > wouldn't really be necessary, since any attempted writes would be returned > > > with errors. > > > > The problem is you cannot unmount after -rw mount with a write-protected > > medium. > > This is essentially the same bug that causes problems for writing to > write protected media or unwriteable blocks using the block device. Are there any reason device drivers do not check if thier devices are writable or not when they are opened ? I think returning an error value, like `od', is the easiest way to avoid this problem. > I first saw this problem for a floppy driver that I wrote in 1984. It > retried endlessly. Users did not like this :-). I was told not to write-protect floppies when using UNIX :-( // Noriaki Mitsunaga // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 6: 5:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from out-mx1.crosswinds.net (out-mx1.crosswinds.net [209.208.163.38]) by hub.freebsd.org (Postfix) with ESMTP id 3D67B37B65D for ; Sat, 10 Feb 2001 06:05:35 -0800 (PST) Received: from member-mx1.crosswinds.net (member-mx1.crosswinds.net [209.208.163.43]) by out-mx1.crosswinds.net (Postfix) with ESMTP id 375B24974E for ; Sat, 10 Feb 2001 09:05:34 -0500 (EST) Received: from lexx.my.domain (unknown [195.110.170.54]) by member-mx1.crosswinds.net (Postfix) with SMTP id D2D8036438 for ; Sat, 10 Feb 2001 09:05:20 -0500 (EST) From: John Murphy To: current@FreeBSD.ORG Subject: Compaq WL200 Date: Sat, 10 Feb 2001 14:06:52 +0000 Organization: not a lot.org Reply-To: john@T-F-I.freeserve.co.uk Message-ID: <3jia8tk63svu9ijshdhf1b3ull3imrlij9@4ax.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to use a Compaq WL200 PCI wireless LAN Card with FreeBSD soon. I've seen mention of the pcic driver in -current, but I'm runing -stable at present. Is the Compaq WL200 already supported by current? If not, is there work in progress? Thanks, John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 7:21: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 5C57C37B4EC; Sat, 10 Feb 2001 07:20:46 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f1AFKeF23286; Sat, 10 Feb 2001 16:20:40 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1AFKYK00603; Sat, 10 Feb 2001 16:20:34 +0100 (CET) (envelope-from asmodai) Date: Sat, 10 Feb 2001 16:20:34 +0100 From: Jeroen Ruigrok/Asmodai To: Manfred Antar Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Current SMP Kernel panics Message-ID: <20010210162033.C406@daemon.ninth-circle.org> References: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com>; from null@pozo.com on Fri, Feb 09, 2001 at 08:43:51PM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010210 06:26], Manfred Antar (null@pozo.com) wrote: >APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 >IPsec: Initialized Security Association Processing. >panic: mutex sched lock not owned at ../../kern/kern_synch.c:175 Me too. 166 static void 167 roundrobin(arg) 168 void *arg; 169 { 170 #ifndef SMP 171 struct proc *p = curproc; /* XXX */ 172 #endif 173 174 #ifdef SMP 175 need_resched(); 176 forward_roundrobin(); 177 #else 178 if (p == PCPU_GET(idleproc) || RTP_PRIO_NEED_RR(p->p_rtprio.type) ) 179 need_resched(); 180 #endif 181 182 callout_reset(&roundrobin_callout, sched_quantum, roundrobin, NUL L); 183 } Should it become: #ifdef SMP mtx_lock_spin(&sched_lock); need_resched(); forward_roundrobin(); mtx_unlock_spin(&sched_lock); #else ? I cannot test it yet, need to reanimate my testbox first. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 7:51:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 3DB3837B503; Sat, 10 Feb 2001 07:50:57 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f1AFoqO04003; Sat, 10 Feb 2001 08:50:52 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200102101550.f1AFoqO04003@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: non@ever.sanda.gr.jp Cc: current@FreeBSD.ORG, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: Your message of "Sat, 10 Feb 2001 22:50:09 +0900." <20010210225009W.non@ever.sanda.gr.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Feb 2001 08:50:52 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Are there any reason device drivers do not check if thier devices are >writable or not when they are opened ? I think returning an error >value, like `od', is the easiest way to avoid this problem. It is not necessarily sufficient since the media may be changed after open on certain types of devices that don't have a media lock. Some devices will only tell you that they are write protected on the first write, etc. For the devices where we can tell, we should make the check in open, but not rely on that catching all cases where a driver will return EACCESS. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 7:51:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.34.222.47]) by hub.freebsd.org (Postfix) with SMTP id D8D6337B491 for ; Sat, 10 Feb 2001 07:51:22 -0800 (PST) Received: (qmail 3818 invoked by uid 1000); 10 Feb 2001 11:49:04 -0000 Date: Sat, 10 Feb 2001 12:49:03 +0100 From: Andrea Campi To: Warner Losh Cc: John Baldwin , Jim Bloom , "Crist J. Clark" , current@FreeBSD.ORG Subject: Cardbus, audio & irq sharing [Was: Kernel Panic from Yesterday's CVSup] Message-ID: <20010210124903.A785@webcom.it> References: <20010208103433.B1088@webcom.it> <20010208021930.C13541@webcom.it> <20010208014108.A13541@webcom.it> <20010208021930.C13541@webcom.it> <200102080507.f1857C998723@harmony.village.org> <20010208103433.B1088@webcom.it> <200102081656.f18Guh941601@harmony.village.org> <20010209150757.A470@webcom.it> <200102100425.f1A4PlW10042@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200102100425.f1A4PlW10042@harmony.village.org>; from imp@harmony.village.org on Fri, Feb 09, 2001 at 09:25:47PM -0700 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : And, it's not working for me, i.e. my pccard using cardbus is working on irq > : 11, my csa audio card is probed and configured on irq 11, but audio playback > : is not. > > Audio and current is also dicy. Well, the same happened under -stable. I think this will be my last IBM laptop, I don't like the way IRQs are wired, and it also looks like ACPI is tricky. > : just wait. On a separate note, I am thinking about adapting rc.pccard to > : carbus, or writing a new rc.cardbus; is anybody working on this? > > /sbin/devd :-) Pointers to this? Does it run dhclient like rc.pccard does? Although one of the nicest things about cardbus is that, having the card in at boot, it probed and configured much earlier during the boot process, making it possible to ifconfig it normally. > : Going back to the original thread, removing my card under cardbus simply > : hangs my laptop. I have no idea how to debug this. > > Neither do I. I make guesses until it is working. Ok ;-) Sounds fun :-P -- Press every key to continue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 8:24:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id CB79337B401; Sat, 10 Feb 2001 08:24:21 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f1AGOHK25539; Sat, 10 Feb 2001 17:24:17 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1AGOIl00820; Sat, 10 Feb 2001 17:24:18 +0100 (CET) (envelope-from asmodai) Date: Sat, 10 Feb 2001 17:24:17 +0100 From: Jeroen Ruigrok/Asmodai To: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Current SMP Kernel panics Message-ID: <20010210172417.F406@daemon.ninth-circle.org> References: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> <20010210162033.C406@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010210162033.C406@daemon.ninth-circle.org>; from asmodai@wxs.nl on Sat, Feb 10, 2001 at 04:20:34PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010210 16:27], Jeroen Ruigrok/Asmodai (asmodai@wxs.nl) wrote: >#ifdef SMP > mtx_lock_spin(&sched_lock); > need_resched(); > forward_roundrobin(); > mtx_unlock_spin(&sched_lock); >#else This does not quite work. I don't get the panic() anymore, but now I have solve the hanging. :) Perhaps only need_resched() needs to be spinlocked. I am not sure, I am not a SMP guru. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 8:54:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EFFAD37B4EC; Sat, 10 Feb 2001 08:54:17 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f1AGsGi26440; Sat, 10 Feb 2001 08:54:16 -0800 (PST) Date: Sat, 10 Feb 2001 08:54:16 -0800 From: Alfred Perlstein To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Current SMP Kernel panics Message-ID: <20010210085416.H3274@fw.wintelcom.net> References: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> <20010210162033.C406@daemon.ninth-circle.org> <20010210172417.F406@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010210172417.F406@daemon.ninth-circle.org>; from asmodai@wxs.nl on Sat, Feb 10, 2001 at 05:24:17PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jeroen Ruigrok/Asmodai [010210 08:24] wrote: > -On [20010210 16:27], Jeroen Ruigrok/Asmodai (asmodai@wxs.nl) wrote: > >#ifdef SMP > > mtx_lock_spin(&sched_lock); > > need_resched(); > > forward_roundrobin(); > > mtx_unlock_spin(&sched_lock); > >#else > > This does not quite work. > > I don't get the panic() anymore, but now I have solve the hanging. :) > > Perhaps only need_resched() needs to be spinlocked. I am not sure, I am > not a SMP guru. That looks correct, need_resched() needs sched_lock. I'm currently looking to see if forward_roundrobin() does as well. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 9: 6:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id F00B537B4EC; Sat, 10 Feb 2001 09:06:32 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.2/8.11.2) with ESMTP id f1AH6O600441; Sat, 10 Feb 2001 09:06:26 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010210090400.00a6d0b8@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sat, 10 Feb 2001 09:06:23 -0800 To: Jeroen Ruigrok/Asmodai From: Manfred Antar Subject: Re: Current SMP Kernel panics Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: <20010210162033.C406@daemon.ninth-circle.org> References: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:20 PM 2/10/2001 +0100, Jeroen Ruigrok/Asmodai wrote: >-On [20010210 06:26], Manfred Antar (null@pozo.com) wrote: >>APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 >>IPsec: Initialized Security Association Processing. >>panic: mutex sched lock not owned at ../../kern/kern_synch.c:175 > >Me too. > >166 static void >167 roundrobin(arg) >168 void *arg; >169 { >170 #ifndef SMP >171 struct proc *p = curproc; /* XXX */ >172 #endif >173 >174 #ifdef SMP >175 need_resched(); >176 forward_roundrobin(); >177 #else >178 if (p == PCPU_GET(idleproc) || RTP_PRIO_NEED_RR(p->p_rtprio.type) > ) >179 need_resched(); >180 #endif >181 >182 callout_reset(&roundrobin_callout, sched_quantum, roundrobin, NUL > L); >183 } > >Should it become: > >#ifdef SMP > mtx_lock_spin(&sched_lock); > need_resched(); > forward_roundrobin(); > mtx_unlock_spin(&sched_lock); >#else > >? > >I cannot test it yet, need to reanimate my testbox first. > I tried the above and the machine just hangs when it comes to: SMP: AP CPU # 1 Launched! :( Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 9:10:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id EA17837B401; Sat, 10 Feb 2001 09:10:05 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id BECB0BAB0; Sat, 10 Feb 2001 12:10:05 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: Jeroen Ruigrok/Asmodai Cc: Manfred Antar , current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Current SMP Kernel panics In-Reply-To: Message from Jeroen Ruigrok/Asmodai of "Sat, 10 Feb 2001 16:20:34 +0100." <20010210162033.C406@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Feb 2001 12:10:05 -0500 From: Jake Burkholder Message-Id: <20010210171005.BECB0BAB0@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Should it become: > > #ifdef SMP > mtx_lock_spin(&sched_lock); > need_resched(); > forward_roundrobin(); > mtx_unlock_spin(&sched_lock); > #else > > ? > > I cannot test it yet, need to reanimate my testbox first. You need to handle the UP case as well :) Also, I don't think that sched_lock should be held across forward_roundrobin(). But, my box still hangs with the assertion satisifed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 9:11:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 5ABC737B4EC; Sat, 10 Feb 2001 09:11:17 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f1AHBCn27833; Sat, 10 Feb 2001 18:11:13 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1AHBD001018; Sat, 10 Feb 2001 18:11:13 +0100 (CET) (envelope-from asmodai) Date: Sat, 10 Feb 2001 18:11:13 +0100 From: Jeroen Ruigrok/Asmodai To: Alfred Perlstein Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Current SMP Kernel panics Message-ID: <20010210181112.G406@daemon.ninth-circle.org> References: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> <20010210162033.C406@daemon.ninth-circle.org> <20010210172417.F406@daemon.ninth-circle.org> <20010210085416.H3274@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010210085416.H3274@fw.wintelcom.net>; from bright@wintelcom.net on Sat, Feb 10, 2001 at 08:54:16AM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010210 18:08], Alfred Perlstein (bright@wintelcom.net) wrote: >* Jeroen Ruigrok/Asmodai [010210 08:24] wrote: >> >> Perhaps only need_resched() needs to be spinlocked. I am not sure, I am >> not a SMP guru. > >That looks correct, need_resched() needs sched_lock. Problem is that when I sched_lock need_resched() it just hangs and doesn't boot further. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 11:10:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id 15C4137B491; Sat, 10 Feb 2001 11:10:25 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id 0BD73BAB0; Sat, 10 Feb 2001 14:10:25 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: freebsd-current@freebsd.org Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_synch.c In-Reply-To: Message from Jake Burkholder of "Sat, 10 Feb 2001 11:07:32 PST." <200102101907.f1AJ7XY67400@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Feb 2001 14:10:24 -0500 From: Jake Burkholder Message-Id: <20010210191025.0BD73BAB0@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > jake 2001/02/10 11:07:32 PST > > Modified files: > sys/kern kern_synch.c > Log: > Acquire sched_lock around need_resched() in roundrobin() to satisfy > assertions that it is held. Since roundrobin() is a timeout there's > no possible way that it could be called with sched_lock held. > > Revision Changes Path > 1.126 +5 -9 src/sys/kern/kern_synch.c > > This fixes the tripped assertion in need_resched(), but -current still hangs on boot. We're working on it :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 11:46:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 5A3A937B65D; Sat, 10 Feb 2001 11:46:04 -0800 (PST) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f1AJjxZ32773; Sat, 10 Feb 2001 20:45:59 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.1/8.11.0) id f1AJjtW01593; Sat, 10 Feb 2001 20:45:55 +0100 (CET) (envelope-from asmodai) Date: Sat, 10 Feb 2001 20:45:55 +0100 From: Jeroen Ruigrok/Asmodai To: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Current SMP Kernel panics Message-ID: <20010210204555.J406@daemon.ninth-circle.org> References: <5.0.2.1.2.20010209204045.00ac42a8@pozo.com> <20010210162033.C406@daemon.ninth-circle.org> <20010210172417.F406@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010210172417.F406@daemon.ninth-circle.org>; from asmodai@wxs.nl on Sat, Feb 10, 2001 at 05:24:17PM +0100 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010210 17:30], Jeroen Ruigrok/Asmodai (asmodai@wxs.nl) wrote: >Perhaps only need_resched() needs to be spinlocked. I am not sure, I am >not a SMP guru. To add: It needed to be spinlocked as you saw jake's commit affirmed and fixed. However I am currently hanging just after lauching the second CPU: art_init: trying /sched!st in/init SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff After that the only things I get are: Generator gate Generator gate finish after each couple of seconds. Going in ddb yields [abbreviated, no serial console]: ddb> show mutex Giant @ ../../kern_intr:427 ddb> show witness spinlocks: sio @ isa/sio.c:2549 sched_lock @ kern/kern_sync.c:809 clk @ i386/isa/clock.c:406 callout @ kern/kern_timeout.c:283 ithread table @ i386/isa/intr_machdep.c:587 ithread list @ kern/kern_intr.237 ap boot @ i386/i386/mp_machdep.c:2270 imen @ i386/i386/mpapic.c:261 Going out of ddb by panicing resulted in either a direct kernel trap 12 with interrupts disabled or a kernel trap 0 with interrupts disabled after which another panic led to a kernel trap 12 with interrupts disabled. The kernel trap 12 was an infinite loop. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 I'm a child of the air, I'm a witch of the wind... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 12:36:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 32D7837B401; Sat, 10 Feb 2001 12:36:38 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id HAA30154; Sun, 11 Feb 2001 07:36:15 +1100 Date: Sun, 11 Feb 2001 07:35:51 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Justin T. Gibbs" Cc: non@ever.sanda.gr.jp, current@FreeBSD.ORG, trevor@jpj.net, akiyama@FreeBSD.ORG Subject: Re: od driver for -CURRENT In-Reply-To: <200102101550.f1AFoqO04003@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 10 Feb 2001, Justin T. Gibbs wrote: > >Are there any reason device drivers do not check if thier devices are > >writable or not when they are opened ? I think returning an error > >value, like `od', is the easiest way to avoid this problem. > > It is not necessarily sufficient since the media may be changed after > open on certain types of devices that don't have a media lock. Some > devices will only tell you that they are write protected on the first > write, etc. For the devices where we can tell, we should make the check > in open, but not rely on that catching all cases where a driver will > return EACCESS. Also, writing to a write protected sector is a special case of an i/o error, so it will be handled by non-broken general i/o error handling. Also^2, write protection might be for individual sectors and might change while the device is open, just like most i/o errors. We actually have this for most disks -- FreeBSD has write protection of label sectors in software, and it can be turned on and off while the device is open. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 12:38:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24]) by hub.freebsd.org (Postfix) with ESMTP id 31C9B37B401; Sat, 10 Feb 2001 12:37:58 -0800 (PST) Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id E1C1BBAB0; Sat, 10 Feb 2001 15:37:57 -0500 (EST) X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.3 To: freebsd-current@freebsd.org Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/i386/i386 trap.c In-Reply-To: Message from Jake Burkholder of "Sat, 10 Feb 2001 12:33:35 PST." <200102102033.f1AKXZl75971@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 10 Feb 2001 15:37:52 -0500 From: Jake Burkholder Message-Id: <20010210203757.E1C1BBAB0@cr66388-a.rchrd1.on.wave.home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > jake 2001/02/10 12:33:35 PST > > Modified files: > sys/alpha/alpha trap.c > sys/i386/i386 trap.c > Log: > Clear the reschedule flag after finding it set in userret(). This > used to be in cpu_switch(), but I don't see any difference between > doing it here. > > Revision Changes Path > 1.45 +2 -1 src/sys/alpha/alpha/trap.c > 1.174 +2 -1 src/sys/i386/i386/trap.c > > This fixes -current on my machines (i386 UP and SMP). Should be in the clear now. asmodia has seen a lock reversal between the process lock and uidinfo lock, but I can't reproduce it. You probably want to remove the kernel option WITNESS_DDB if you have it it enabled. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 13:33:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.34.222.47]) by hub.freebsd.org (Postfix) with SMTP id B24C137B65D for ; Sat, 10 Feb 2001 13:33:19 -0800 (PST) Received: (qmail 498 invoked by uid 1000); 10 Feb 2001 21:26:14 -0000 Date: Sat, 10 Feb 2001 22:26:12 +0100 From: Andrea Campi To: Jake Burkholder Cc: freebsd-current@freebsd.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/i386/i386 trap.c Message-ID: <20010210222610.A449@webcom.it> References: <20010210203757.E1C1BBAB0@cr66388-a.rchrd1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010210203757.E1C1BBAB0@cr66388-a.rchrd1.on.wave.home.com>; from jburkholder0829@home.com on Sat, Feb 10, 2001 at 03:37:52PM -0500 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This fixes -current on my machines (i386 UP and SMP). Confirmed for UP i686. > Should be in the clear now. asmodia has seen a lock reversal between > the process lock and uidinfo lock, but I can't reproduce it. You > probably want to remove the kernel option WITNESS_DDB if you have it > it enabled. Same here. I get the (now usual): lock order reversal 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644 2nd 0xc0299bc0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 3rd 0xc6595dac vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 then later: lock order reversal 1st lockmgr last acquired @ ../../kern/kern_lock.c:505 2nd 0xc02824a0 uidinfo hash @ ../../kern/kern_resource.c:727 3rd 0xc0280460 lockmgr @ ../../kern/kern_lock.c:239 and a few seconds later: lock order reversal 1st lockmgr last acquired @ ../../kern/kern_lock.c:505 2nd 0xc0ac9e1c uidinfo struct @ ../../kern/kern_resource.c:781 3rd 0xc0280460 lockmgr @ ../../kern/kern_lock.c:239 Bye, Andrea -- The best things in life are free, but the expensive ones are still worth a look. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 13:51: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [212.34.222.47]) by hub.freebsd.org (Postfix) with SMTP id 1064637B503 for ; Sat, 10 Feb 2001 13:50:48 -0800 (PST) Received: (qmail 449 invoked by uid 1000); 10 Feb 2001 21:37:47 -0000 Date: Sat, 10 Feb 2001 22:37:46 +0100 From: Andrea Campi To: Jake Burkholder Cc: freebsd-current@freebsd.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/i386/i386 trap.c Message-ID: <20010210223745.A406@webcom.it> References: <20010210203757.E1C1BBAB0@cr66388-a.rchrd1.on.wave.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010210203757.E1C1BBAB0@cr66388-a.rchrd1.on.wave.home.com>; from jburkholder0829@home.com on Sat, Feb 10, 2001 at 03:37:52PM -0500 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Clear the reschedule flag after finding it set in userret(). This > > used to be in cpu_switch(), but I don't see any difference between > > doing it here. > > Should be in the clear now. asmodia has seen a lock reversal between > the process lock and uidinfo lock, but I can't reproduce it. You > probably want to remove the kernel option WITNESS_DDB if you have it > it enabled. Another one, during fsck (I can still panic the system by ejecting pccard): lock order reversal 1st vnode interlock last acquired @ ../../ufs/ffs/ffs_vfsops.c:396 2nd 0xc0299bc0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:457 3rd 0xc60bafec vnode interlock @ ../../kern/vfs_subr.c:1871 -- Yes, I've heard of "decaf." What's your point? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 15:49:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C5A1137B491; Sat, 10 Feb 2001 15:48:53 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id KAA04863; Sun, 11 Feb 2001 10:48:51 +1100 Date: Sun, 11 Feb 2001 10:48:27 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "John W. De Boskey" Cc: current@FreeBSD.ORG Subject: Re: disklabel.c & disklabel.8 patch In-Reply-To: <20010209225817.A24289@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Feb 2001, John W. De Boskey wrote: > I've been using the disklabel.c patch which allows easier > configuration by being able to specify a new disklabel of > the form: > > # size offset fstype [fsize bsize bps/cpg] > a: 400M 0 4.2BSD 4096 16384 75 # (Cyl. 0 - 812*) > b: 1G * swap > c: * * unused > e: 204800 * 4.2BSD > f: 5g * 4.2BSD > g: * * 4.2BSD > > > An up-to-date copy of disklabel.c can be found at: > > http://people.freebsd.org/~jwd/disklabel.c > > The man page can be found at: > > http://people.freebsd.org/~jwd/disklabel/disklabel.8 > > or in html format: > > http://people.freebsd.org/~jwd/disklabel/disklabel.8.html > > > Patch files: > > http://people.freebsd.org/~jwd/disklabel/disklabel.c.patch > http://people.freebsd.org/~jwd/disklabel/disklabel.8.patch > > > I'd like to commit these if no one sees any major problems > with them. These are not suitable for commit in their current form. The disklabel.c patch has more than the usual density of style bugs. It doesn't even use the normal brace style. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 16:38:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id BC0E837B401; Sat, 10 Feb 2001 16:37:58 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1B0bsW17861; Sat, 10 Feb 2001 17:37:54 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102110037.f1B0bsW17861@harmony.village.org> To: Bruce Evans Subject: Re: disklabel.c & disklabel.8 patch Cc: "John W. De Boskey" , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Feb 2001 10:48:27 +1100." References: Date: Sat, 10 Feb 2001 17:37:54 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : These are not suitable for commit in their current form. The : disklabel.c patch has more than the usual density of style bugs. : It doesn't even use the normal brace style. You can find a mostly cleaned up version at http://people.freebsd.org/~imp/disklabel.c.patch but there's still some problems.... Warner P.S. There's also some problems getting to freefall, so the patch really isn't there yet... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 20:45:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 83CC337B491 for ; Sat, 10 Feb 2001 20:45:16 -0800 (PST) Received: from xor.obsecurity.org ([63.207.60.67]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G8K00FT7T1ZE5@mta6.snfc21.pbi.net> for current@FreeBSD.org; Sat, 10 Feb 2001 20:42:05 -0800 (PST) Received: by xor.obsecurity.org (Postfix, from userid 1000) id 1CE8766B26; Sat, 10 Feb 2001 20:44:39 -0800 (PST) Date: Sat, 10 Feb 2001 20:44:38 -0800 From: Kris Kennaway Subject: New OpenSSL snapshot for testing To: current@FreeBSD.org Message-id: <20010210204438.A52632@mollari.cthul.hu> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Well, I lost the previous OpenSSL snapshot with a hard disk crash (and it's no longer on the FTP site) so I had to redo it - please test this one instead: http://www.freebsd.org/~kris/openssl-0.9.6-stable-20010210.tbz Same deal as before - unpack it in /usr/src and rebuild. I'll commit this in a week. Kris --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6hhi2Wry0BWjoQKURAj7cAKD7dXBNRlCQ92bTsApTpdn+vBwnsACdEsYG A+0hFGlQY36XddN7A0tOBrU= =vbZ5 -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 10 21:50:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailer.tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130]) by hub.freebsd.org (Postfix) with ESMTP id 9674237B503 for ; Sat, 10 Feb 2001 21:50:20 -0800 (PST) Received: from localhost (natto.tydfam.machida.tokyo.jp [210.161.209.131]) by mailer.tydfam.machida.tokyo.jp (8.11.1/3.7W10/03/98) with ESMTP id f1B5oGP59819 for ; Sun, 11 Feb 2001 14:50:16 +0900 (JST) To: current@FreeBSD.org Subject: Is Sawfish running on -current? X-Mailer: Mew version 1.94.1 on XEmacs 21.1 (Channel Islands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010211145016O.ken@tydfam.machida.tokyo.jp> Date: Sun, 11 Feb 2001 14:50:16 +0900 From: Takeshi Ken Yamada X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the following error while compiling Sawfish on recent -current. Is it my half updated fault or the -current issue? gmake[1]: Entering directory `/home/SRC/FreeBSD/FreeBSD-current/ports/x11-wm/sawfish/work/sawfish-0.36/lisp' SAWFISHLISPDIR=. SAWFISHEXECDIR=../src/.libexec SAWFISHDOCFILE=../DOC /usr/local/libexec/rep/i386--freebsd5.0/libtool --mode=execute -dlopen ../src/gradient.la ../src/sawfish --batch --no-rc compiler -f compile-batch sawfish/wm.jl Segmentation fault - core dumped gmake[1]: *** [sawfish/wm.jlc] Error 139 gmake[1]: Leaving directory `/home/SRC/FreeBSD/FreeBSD-current/ports/x11-wm/sawfish/work/sawfish-0.36/lisp' gmake: *** [all] Error 2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message