From owner-freebsd-current Sun Oct 1 0:24:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 165E837B503 for ; Sun, 1 Oct 2000 00:24:07 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e917NPG01069; Sun, 1 Oct 2000 00:23:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010010723.e917NPG01069@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Motomichi Matsuzaki Cc: Alexander@Leidinger.net, current@FreeBSD.ORG Subject: Re: config(8) weirdness In-Reply-To: <86lmwafl04.wl@tkc.att.ne.jp> Date: Sun, 01 Oct 2000 00:23:25 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG EEK! I will take a look at this right now... Motomichi Matsuzaki wrote: > > Hi. > > At Sun, 27 Aug 2000 15:16:01 +0200 (CEST), > Alexander Leidinger wrote: > > > Can anyone success compiling kernel with the following config? > > > > > > # 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 > > > > > I've the same problem. > > > This is obvous BUG of config(8), newly introduced 'count' feature. > > In /sys/conf/files.i386 : > > dev/ata/atapi-all.c count atapicd > dev/ata/atapi-all.c count atapifd > dev/ata/atapi-all.c count atapist > > On the current implementation, > the first line is only effective, > > i.e. same as: > > dev/ata/atapi-all.c count atapicd > #dev/ata/atapi-all.c count atapifd > #dev/ata/atapi-all.c count atapist > > Then, atapi-all.c will be copiled only when atapicd is enabled. > > > To exchange the lines of files.i386 takes effect as a symptomatic therapy. > But..., fix for config(8) is needed. > > -- > Motomichi Matsuzaki > Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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 Oct 1 1:19:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8C08C37B502; Sun, 1 Oct 2000 01:19:50 -0700 (PDT) Received: (from kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA80075; Sun, 1 Oct 2000 01:19:50 -0700 (PDT) (envelope-from kris@FreeBSD.org) Date: Sun, 1 Oct 2000 01:19:50 -0700 From: Kris Kennaway To: Tony Johnson Cc: CHOI Junho , current@freebsd.org Subject: Re: Today -current broken on build Message-ID: <20001001011950.A9499@freefall.freebsd.org> References: <86u2axjimp.fsf@gnomaniac.myhome> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gjohnson@gs.verio.net on Sun, Oct 01, 2000 at 12:20:04AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 01, 2000 at 12:20:04AM -0500, Tony Johnson wrote: > Run 4.0 or piss off... Tony, I suggest you apologise to Mr Choi for this extremely insulting message. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 1:55:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id B49F137B66C for ; Sun, 1 Oct 2000 01:55:09 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e918siU07464; Sun, 1 Oct 2000 01:54:44 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: "Tony Johnson" Cc: "CHOI Junho" , current@FreeBSD.ORG Subject: Re: Today -current broken on build In-Reply-To: Message from "Tony Johnson" of "Sun, 01 Oct 2000 00:20:04 CDT." Date: Sun, 01 Oct 2000 01:54:44 -0700 Message-ID: <7460.970390484@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Run 4.0 or piss off... That's totally inappropriate. He's reporting a BUILD ERROR which is an occasional fact of life in -current and should be reported so that whomever broke AMD can go fix the build. He's also a developer of FreeBSD and simply reporting this to the other developers. I'm getting very tired of you, Tony. I think it's time for you to go off the air for awhile before all of us feel the same way. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 3:35: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id C743A37B66C; Sun, 1 Oct 2000 03:34:57 -0700 (PDT) Received: from fmrl02.sul.t-online.de by mailout00.sul.t-online.com with smtp id 13fgQM-0003zP-00; Sun, 01 Oct 2000 12:32:50 +0200 Received: from neutron.cichlids.com (520050424122-0001@[62.225.195.108]) by fmrl02.sul.t-online.com with esmtp id 13fgQE-069wvoC; Sun, 1 Oct 2000 12:32:42 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id BF786AB91; Sun, 1 Oct 2000 12:33:20 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 20FD414B09; Sun, 1 Oct 2000 12:32:17 +0200 (CEST) Date: Sun, 1 Oct 2000 12:32:17 +0200 From: Alexander Langer To: Poul-Henning Kamp Cc: Jeremy Lea , Mike Meyer , current@FreeBSD.ORG Subject: Re: setting device permissions for DEVFS Message-ID: <20001001123217.A2644@cichlids.cichlids.com> Mail-Followup-To: Alexander Langer , Poul-Henning Kamp , Jeremy Lea , Mike Meyer , current@FreeBSD.ORG References: <20000930120607.C349@shale.csir.co.za> <11056.970344237@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <11056.970344237@critter>; from phk@critter.freebsd.dk on Sat, Sep 30, 2000 at 10:03:57PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > You guys are overlooking something about DEVFS: devices may appear > post-boot. Ah, yes. BTW: Devices don't disappear if you unload devices. This happens for example with bktr.ko. When I then reload bktr.ko, I get the following: WARNING: Driver mistake: repeat make_dev("bktr0") WARNING: Driver mistake: repeat make_dev("tuner0") WARNING: Driver mistake: repeat make_dev("vbi0") > We need a generic "devd" which finds out that devices have appeared, > set their perms (if needed/wanted) and executes any commands needed > (getty, mount, etc etc) by the device. Hmm. A technical question: How would the devd be notifed about an event in the devfs? Does it open a (new) device as for example the usbd does, or how would you solve that? Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 3:39:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (beachchick.freebsd.dk [212.242.34.253]) by hub.freebsd.org (Postfix) with ESMTP id BB3B237B502; Sun, 1 Oct 2000 03:39:34 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e91AdON13128; Sun, 1 Oct 2000 12:39:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alexander Langer Cc: Jeremy Lea , Mike Meyer , current@FreeBSD.ORG Subject: Re: setting device permissions for DEVFS In-Reply-To: Your message of "Sun, 01 Oct 2000 12:32:17 +0200." <20001001123217.A2644@cichlids.cichlids.com> Date: Sun, 01 Oct 2000 12:39:23 +0200 Message-ID: <13126.970396763@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001001123217.A2644@cichlids.cichlids.com>, Alexander Langer write s: >Thus spake Poul-Henning Kamp (phk@critter.freebsd.dk): > >> You guys are overlooking something about DEVFS: devices may appear >> post-boot. > >Ah, yes. > >BTW: Devices don't disappear if you unload devices. >This happens for example with bktr.ko. That is because the bktr driver fails to call destroy_dev() when it unloads. >Hmm. A technical question: How would the devd be notifed about an >event in the devfs? There are many ways to do this, a kqueue() or poll() based solution is probably the correct way, monitoring the sysctl vfs.devfs.generation is the Q&D way. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Oct 1 6: 5:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 31F9D37B502; Sun, 1 Oct 2000 06:05:15 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e91D5Cr23487; Sun, 1 Oct 2000 22:05:12 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: msmith@freebsd.org Cc: iwasaki@jp.FreeBSD.org, haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-Reply-To: <200009302245.e8UMjmh01156@mass.osd.bsdi.com> References: <20001001065134S.iwasaki@jp.FreeBSD.org> <200009302245.e8UMjmh01156@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Message-Id: <20001001220452O.iwasaki@jp.FreeBSD.org> Date: Sun, 01 Oct 2000 22:04:52 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 76 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>> Cool. On some machine, thermal management requires Embedded Controller I/O. > >>> Anybody working on this? > >> > >> Yeah. I just discovered that I need this. > >> > >> I haven't look at how operation regions are handled, so I'm not sure how > >> hard it's going to be to implement the hooks necessary for this. > > > > Some VAIOs, ThinkPads require this too, luckily my PORTEGE doesn't. > > I can test the thermal management code earlier :-) > > Swine. 8) Yes :-) > > PowerResource code keeps pointers to the PowerResource objects, then > > finds a pointer to methods of the object dynamically. Can we do it in > > similar way for thermal management? > > Well, yes, but you have to go back and re-parse the actual AML. I'm not > even sure if it's safe to assume that the thermal zone is in the same > place in the bytecode (it should be, I guess). I also think it shoud be... > I went reading through the ACPICA documentation to work this out. They > acually have a very nice technique where they attach the I/O handlers to > a point in the namespace, and then when something attempts I/O, they > travel back up the namespace to the root, looking for the first matching > I/O handler. > > This means that when your EC driver finds an embedded controller, you > just attach your I/O handler to the EC object. Then anytime someone > tries to do I/O to the EC, your handler gets called. Yes, we can have large benefit by migrating to ACPICA. I suggest that we make ACPICA version of AML interpreter run in userland as a debugger for the first evaluation. By doing this work we can make sure it works actually on FreeBSD and estimate the work volume of kernel porting. Also we know the amldb is very useful from our development experience. Another suggestion is that this migration should be done prudently. During ACPICA porting, we add ACPICA compatible wrappers to current aml code (e.g. AcpiWalkNamespace() -> aml_apply_foreach_found_objects()) and modify acpi driver code so that we migrate to ACPICA smoothly. BTW, last time Watanabe-san tried to write EC stuff, but unfortunately his laptop was broken *twice* by testing. Be careful, otherwise your Dell will go to the hospital 8) > I can write the driver easily enough, but I don't know how I/O is > currently handled in the AML interpreter. The more I look at ACPICA, the > more I like the idea of using it, presuming that it actually works... > > > Last time I compared only few files and found many differences between > > them not only for naming. I think these two used the same code > > originally, but enhanced separately. Now that it's difficult to > > compare them... > > Hmm. I guess I should spend some more time looking at this. I don't > mean to devalue all the work that's been put into the current AML code, > but ACPICA has already solved a lot of the problems that we haven't even > touched yet (Notify, locking, etc...) OK, before making our decision, I want to make sure something. - Licence Linux folks apply GPL for it. Is it possible to apply BSD style licence for FreeBSD version of ACPICA? or should we put it sys/contrib? - Support from Intel My major concern is this one. I wonder whether our local changes for ACPICA can feed back to original code. If not, maintenance will become hard... Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 6: 7: 2 2000 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 B46BB37B502 for ; Sun, 1 Oct 2000 06:06:55 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13fipJ-0001d6-00 for current@freebsd.org; Sun, 01 Oct 2000 15:06:45 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id PAA25895 for ; Sun, 1 Oct 2000 15:06:48 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 25774; Sun Oct 1 15:05:30 2000 Received: from bofh.fw.uunet.co.za (bofh.fw.uunet.co.za [172.16.3.35]) by kg.ops.uunet.co.za (Postfix) with ESMTP id 091FC16FDD for ; Sun, 1 Oct 2000 15:05:28 +0200 (SAST) Received: by bofh.fw.uunet.co.za (Postfix, from userid 1000) id 193F45C05; Sun, 1 Oct 2000 15:05:28 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by bofh.fw.uunet.co.za (Postfix) with ESMTP id 0E3401EB2 for ; Sun, 1 Oct 2000 15:05:28 +0200 (SAST) Date: Sun, 1 Oct 2000 15:05:27 +0200 (SAST) From: Khetan Gajjar X-Sender: khetan@bofh.fw.uunet.co.za To: current@freebsd.org Subject: Oddity after SMPNG kernel Message-ID: X-Cell: +27 82 416 0160 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I've upgraded my -current box from a pre-SMPNG kernel (an August vintage) to a post-SMPNG kernel (built today), and have noticed behaviour I haven't seen discussed in -current. I followed the instructions in UPDATING as well as discussed on the -current list, and the system boots with nothing out of the ordinary. There is no /modules, and the host is a UP machine. However, after approximately 20-30 minutes, it appears to slow down immensely, until it basically halts. Keyboard input at the console appears not to have any effect (although Caps, Scroll and Num lock work). The machine is pingable, and I can change VT's, but no input is accepted. All services on the box get as far as the Connected stage, but no banner appears. I left it for several minutes, and saw microuptime() went backwards (2757.4076411 -> 2757.992648), with the right hand side number increasing periodically. After I hard-boot the machine it carries on as normal again for 20-30 minutes before reverting to it's zombie state. Booting a kernel prior to the SMPNG changes does not have the same problems. Should I revert to PRE_SMPNG days, with a cvsup tag of *default release=cvs tag=PRE_SMPNG ? Here is the output of dmesg : Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sun Oct 1 13:41:45 SAST 2000 khetan@chain.freebsd.os.org.za:/usr/src/sys/compile/CHAIN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200456354 Hz CPU: Pentium/P54C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 117440512 (114688K bytes) config> port sbc 0x220 config> q avail memory = 110428160 (107840K bytes) Preloaded elf kernel "kernel" at 0xc039d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc039d09c. Intel Pentium detected, installing workaround for F00F bug ccd0-1: Concatenated disk drivers VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c1bfc (c0001bfc) VESA: S3 Incorporated. Trio64V+ npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 atapci0: port 0x4000-0x400f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 irq 14 at devic e 0.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: (vendor=0x1039, dev=0x0009) at 1.1 pcib1: at device 2.0 on pci0 pci1: on pcib1 pci0: at 9.0 irq 5 de0: port 0xe000-0xe07f mem 0xea000000-0xea00007f irq 9 at device 11.0 on pci0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:f9:2f:c8 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 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 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 plip0: on ppbus0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> 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 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 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 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. de0: enabling 10baseT port ad0: 8693MB [17662/16/63] at ata0-master UDMA33 ad1: 1033MB [2100/16/63] at ata1-master WDMA2 Mounting root from ufs:/dev/ad0s1a Khetan Gajjar. --- khetan@uunet.co.za * khetan@os.org.za * PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * kg+details@uunet.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 8:25:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id A538237B502 for ; Sun, 1 Oct 2000 08:25:29 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e91FR7G63783 for ; Mon, 2 Oct 2000 00:27:09 +0900 (JST) Date: Mon, 02 Oct 2000 00:27:07 +0900 Message-ID: <7mr96037lg.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: current@FreeBSD.ORG Subject: Re: Today -current broken on build In-Reply-To: In your message of "1 Oct 2000 04:24:14 GMT" <86u2axjimp.fsf@gnomaniac.myhome> References: <86u2axjimp.fsf@gnomaniac.myhome> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1 Oct 2000 04:24:14 GMT, CHOI Junho wrote: > I have cvsup'ed today, build stopped with the following error: I got same one, reported by my nightly buildworld failure. I think this happened between 9/30 00:00 JST and 10/1 00:00 JST... -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:35:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5F3E837B502 for ; Sun, 1 Oct 2000 10:35:43 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA00547; Sun, 1 Oct 2000 11:35:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA00782; Sun, 1 Oct 2000 11:35:32 -0600 (MDT) Message-Id: <200010011735.LAA00782@harmony.village.org> To: "Tony Johnson" Subject: Re: Today -current broken on build Cc: "CHOI Junho" , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 01 Oct 2000 00:20:04 CDT." References: Date: Sun, 01 Oct 2000 11:35:32 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Tony Johnson" writes: : Run 4.0 or piss off... Tony, this is an *UN*acceptible attitude. CHOI-san is reporting a problem. He didn't rail against anything, nor did he demand a fix. This is 100% acceptible. Your message, however, was rude and inappropriate. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:41:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A583037B66E; Sun, 1 Oct 2000 10:41:51 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA00564; Sun, 1 Oct 2000 11:41:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA00818; Sun, 1 Oct 2000 11:41:46 -0600 (MDT) Message-Id: <200010011741.LAA00818@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: ACPI megapatch Cc: tshiozak@astec.co.jp, acpi-jp@jp.freebsd.org, msmith@FreeBSD.ORG, haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@FreeBSD.ORG In-reply-to: Your message of "Fri, 29 Sep 2000 23:47:22 +0900." <20000929234722R.iwasaki@jp.FreeBSD.org> References: <20000929234722R.iwasaki@jp.FreeBSD.org> <200009290916.e8T9GmA04415@mass.osd.bsdi.com> <20000929220517P.iwasaki@jp.FreeBSD.org> <20000929.224139.70178011.tshiozak@astec.co.jp> Date: Sun, 01 Oct 2000 11:41:46 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000929234722R.iwasaki@jp.FreeBSD.org> Mitsuru IWASAKI writes: : Thanks Shiozaki-san, I think `reg' is short for registers of the : target chip, correct? Yes. Traditionally fooreg.h has "hardware" definitions on it. Device registers, flag masks and other such things. Both OLDCARD and NEWCARD do this. : How about kernel/userland shareable stuff like ioctl? Traditionally, these have been placed in fooio.h. The reason that foo.h hasn't been used more is, as pointed out earlier, foo.h is generated by config. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:45:48 2000 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 7B25137B502 for ; Sun, 1 Oct 2000 10:45:46 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e91Hjj963009; Sun, 1 Oct 2000 12:45:45 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: current@FreeBSD.ORG Subject: Re: Today -current broken on build References: <200010011735.LAA00782@harmony.village.org> From: Michael Harnois Date: 01 Oct 2000 12:45:45 -0500 In-Reply-To: <200010011735.LAA00782@harmony.village.org> Message-ID: <86zokoh2uu.fsf@mharnois.workgroup.net> Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) 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, 01 Oct 2000 11:35:32 -0600, Warner Losh said: > Tony, this is an *UN*acceptible attitude. CHOI-san is reporting > a problem. He didn't rail against anything, nor did he demand a > fix. This is 100% acceptible. Your message, however, was rude > and inappropriate. I hate to spoil the moment ... but does anyone have an idea what the fix is? Nothing in the amd directory seems to have changed in the past couple of weeks, so it must be somewhere else, and I'm not bright enough to figure out where. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org "It is dangerous to be right in matters on which the established authorities are wrong." -- Voltaire To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:49: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9F43437B502 for ; Sun, 1 Oct 2000 10:48:56 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA00590; Sun, 1 Oct 2000 11:48:55 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA00868; Sun, 1 Oct 2000 11:48:52 -0600 (MDT) Message-Id: <200010011748.LAA00868@harmony.village.org> To: Alexander Langer Subject: Re: setting device permissions for DEVFS Cc: Mike Meyer , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 30 Sep 2000 20:17:38 +0200." <20000930201738.A17165@cichlids.cichlids.com> References: <20000930201738.A17165@cichlids.cichlids.com> <20000929180208.A821@cichlids.cichlids.com> <20000930120037.A4899@cichlids.cichlids.com> <14806.11402.323948.403889@guru.mired.org> Date: Sun, 01 Oct 2000 11:48:52 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000930201738.A17165@cichlids.cichlids.com> Alexander Langer writes: : No - instead we should add something like devfs_permission{0,1,2,etc} : (and maybe ownership) to rc.conf, which can be modified there and : then rc.devfs sets them - similar to the ifconfig stuff. : : Opinions? devd? We need it for other reasons (think removable devices). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:49:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D1D9037B502; Sun, 1 Oct 2000 10:49:34 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA00599; Sun, 1 Oct 2000 11:49:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA00888; Sun, 1 Oct 2000 11:49:33 -0600 (MDT) Message-Id: <200010011749.LAA00888@harmony.village.org> To: Jeremy Lea Subject: Re: setting device permissions for DEVFS Cc: Mike Meyer , Alexander Langer , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 30 Sep 2000 12:06:07 PDT." <20000930120607.C349@shale.csir.co.za> References: <20000930120607.C349@shale.csir.co.za> <20000929180208.A821@cichlids.cichlids.com> <20000930120037.A4899@cichlids.cichlids.com> <14806.11402.323948.403889@guru.mired.org> <20000930201738.A17165@cichlids.cichlids.com> <14806.13976.356085.876527@guru.mired.org> Date: Sun, 01 Oct 2000 11:49:33 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000930120607.C349@shale.csir.co.za> Jeremy Lea writes: : Can mtree not be used for this? Seems like the quickest and cleanest : solution to me... No. Think removable devices. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:51:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 108B737B502; Sun, 1 Oct 2000 10:51:15 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA00612; Sun, 1 Oct 2000 11:51:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA00911; Sun, 1 Oct 2000 11:51:13 -0600 (MDT) Message-Id: <200010011751.LAA00911@harmony.village.org> To: Poul-Henning Kamp Subject: Re: setting device permissions for DEVFS Cc: Jeremy Lea , Mike Meyer , Alexander Langer , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 30 Sep 2000 22:03:57 +0200." <11056.970344237@critter> References: <11056.970344237@critter> Date: Sun, 01 Oct 2000 11:51:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <11056.970344237@critter> Poul-Henning Kamp writes: : We need a generic "devd" which finds out that devices have appeared, : set their perms (if needed/wanted) and executes any commands needed : (getty, mount, etc etc) by the device. ifconfig and dhclient are likely the most often executed ones now. I agree we need a generic devd. Does devfs use the kqueue interface? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:53:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 79E9B37B502 for ; Sun, 1 Oct 2000 10:53:23 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA00621; Sun, 1 Oct 2000 11:53:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA00931; Sun, 1 Oct 2000 11:53:21 -0600 (MDT) Message-Id: <200010011753.LAA00931@harmony.village.org> To: Alan Cox Subject: Re: kthread_create() Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 30 Sep 2000 18:35:51 CDT." <20000930183551.A2132@cs.rice.edu> References: <20000930183551.A2132@cs.rice.edu> Date: Sun, 01 Oct 2000 11:53:21 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000930183551.A2132@cs.rice.edu> Alan Cox writes: : Does anyone know if it's by design or by accident that kthread_create : specifies RFFDG to fork1? It seems odd to ask for the file descriptor : table to be copied and not shared. I think that I did that, or Peter didn't change it. I copied it from NetBSD of the time. I think it made sense to me since I wanted stdout to be the console. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 10:55:47 2000 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 B5A5437B502; Sun, 1 Oct 2000 10:55:43 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e91HtXN14854; Sun, 1 Oct 2000 19:55:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Jeremy Lea , Mike Meyer , Alexander Langer , current@FreeBSD.ORG Subject: Re: setting device permissions for DEVFS In-Reply-To: Your message of "Sun, 01 Oct 2000 11:51:13 MDT." <200010011751.LAA00911@harmony.village.org> Date: Sun, 01 Oct 2000 19:55:33 +0200 Message-ID: <14852.970422933@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010011751.LAA00911@harmony.village.org>, Warner Losh writes: >In message <11056.970344237@critter> Poul-Henning Kamp writes: >: We need a generic "devd" which finds out that devices have appeared, >: set their perms (if needed/wanted) and executes any commands needed >: (getty, mount, etc etc) by the device. > >ifconfig and dhclient are likely the most often executed ones now. > >I agree we need a generic devd. Does devfs use the kqueue interface? Not right now, but it could. Right now you can tell something happened by examining the sysctl vfs.devfs.generation -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Oct 1 10:57:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 166E837B502; Sun, 1 Oct 2000 10:57:42 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA00644; Sun, 1 Oct 2000 11:57:37 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA00993; Sun, 1 Oct 2000 11:57:37 -0600 (MDT) Message-Id: <200010011757.LAA00993@harmony.village.org> To: Poul-Henning Kamp Subject: Re: setting device permissions for DEVFS Cc: Jeremy Lea , Mike Meyer , Alexander Langer , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 01 Oct 2000 19:55:33 +0200." <14852.970422933@critter> References: <14852.970422933@critter> Date: Sun, 01 Oct 2000 11:57:37 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14852.970422933@critter> Poul-Henning Kamp writes: : Not right now, but it could. Right now you can tell something happened : by examining the sysctl vfs.devfs.generation OK. As soon as I get NEWCARD attaching devices, I'll revisit this as it is needed for pccard stuff. If things go well, this will be before BSDcon, but I keep hitting new problems with newer -current that weren't there in earlier versions :-(. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 11:24:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id 3587C37B502; Sun, 1 Oct 2000 11:24:06 -0700 (PDT) Received: from fmrl00.sul.t-online.de by mailout06.sul.t-online.com with smtp id 13fnkF-0004UA-00; Sun, 01 Oct 2000 20:21:51 +0200 Received: from neutron.cichlids.com (520050424122-0001@[62.225.195.108]) by fmrl00.sul.t-online.com with esmtp id 13fnk2-0k38nwC; Sun, 1 Oct 2000 20:21:38 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id B1EADAB91; Sun, 1 Oct 2000 20:22:15 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id AD9D914B09; Sun, 1 Oct 2000 20:21:03 +0200 (CEST) Date: Sun, 1 Oct 2000 20:21:03 +0200 From: Alexander Langer To: Warner Losh Cc: Poul-Henning Kamp , Jeremy Lea , Mike Meyer , current@FreeBSD.ORG Subject: Re: setting device permissions for DEVFS Message-ID: <20001001202103.C1374@cichlids.cichlids.com> Mail-Followup-To: Alexander Langer , Warner Losh , Poul-Henning Kamp , Jeremy Lea , Mike Meyer , current@FreeBSD.ORG References: <11056.970344237@critter> <200010011751.LAA00911@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: <200010011751.LAA00911@harmony.village.org>; from imp@village.org on Sun, Oct 01, 2000 at 11:51:13AM -0600 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Warner Losh (imp@village.org): > ifconfig and dhclient are likely the most often executed ones now. > I agree we need a generic devd. Does devfs use the kqueue interface? What I also LOVED to use is mounting nfs dirs when a pccard ethernet device is plugged in. Currently, I modified rc.pccard for that :) Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 11:29:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2400837B503; Sun, 1 Oct 2000 11:29:41 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA00788; Sun, 1 Oct 2000 12:29:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA01277; Sun, 1 Oct 2000 12:29:39 -0600 (MDT) Message-Id: <200010011829.MAA01277@harmony.village.org> To: Alexander Langer Subject: Re: setting device permissions for DEVFS Cc: Poul-Henning Kamp , Jeremy Lea , Mike Meyer , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 01 Oct 2000 20:21:03 +0200." <20001001202103.C1374@cichlids.cichlids.com> References: <20001001202103.C1374@cichlids.cichlids.com> <11056.970344237@critter> <200010011751.LAA00911@harmony.village.org> Date: Sun, 01 Oct 2000 12:29:39 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001001202103.C1374@cichlids.cichlids.com> Alexander Langer writes: : Currently, I modified rc.pccard for that :) Don't you mean pccard.conf? You can do the mounting now. I think that umount -f would work for dismounting on eject, but haven't tested it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 11:45:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id DC44237B503 for ; Sun, 1 Oct 2000 11:45:45 -0700 (PDT) Received: from fmrl00.sul.t-online.de by mailout00.sul.t-online.com with smtp id 13fo7H-00053b-00; Sun, 01 Oct 2000 20:45:39 +0200 Received: from neutron.cichlids.com (520050424122-0001@[62.225.195.108]) by fmrl00.sul.t-online.com with esmtp id 13fo76-0mHSPAC; Sun, 1 Oct 2000 20:45:28 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 8A949AB91; Sun, 1 Oct 2000 20:46:12 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 374E214B09; Sun, 1 Oct 2000 20:45:10 +0200 (CEST) Date: Sun, 1 Oct 2000 20:45:10 +0200 From: Alexander Langer To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: setting device permissions for DEVFS Message-ID: <20001001204510.A1952@cichlids.cichlids.com> Mail-Followup-To: Alexander Langer , Warner Losh , current@FreeBSD.ORG References: <20001001202103.C1374@cichlids.cichlids.com> <11056.970344237@critter> <200010011751.LAA00911@harmony.village.org> <20001001202103.C1374@cichlids.cichlids.com> <200010011829.MAA01277@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: <200010011829.MAA01277@harmony.village.org>; from imp@village.org on Sun, Oct 01, 2000 at 12:29:39PM -0600 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. X-Sender: 520050424122-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Warner Losh (imp@village.org): > Don't you mean pccard.conf? You can do the mounting now. I think > that umount -f would work for dismounting on eject, but haven't tested > it. No, I meant /etc/pccard_ether :) It works just fine. I don't unmount, though. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 11:54:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A46D137B66C for ; Sun, 1 Oct 2000 11:54:22 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e91Is5U09421; Sun, 1 Oct 2000 11:54:05 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Michael Harnois Cc: current@FreeBSD.ORG Subject: Re: Today -current broken on build In-Reply-To: Message from Michael Harnois of "01 Oct 2000 12:45:45 CDT." <86zokoh2uu.fsf@mharnois.workgroup.net> Date: Sun, 01 Oct 2000 11:54:05 -0700 Message-ID: <9417.970426445@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I hate to spoil the moment ... but does anyone have an idea what the > fix is? Nothing in the amd directory seems to have changed in the > past couple of weeks, so it must be somewhere else, and I'm not bright > enough to figure out where. Yeah, somebody forgot that typedefs and structure names can't conflict. :) I've just committed the fix. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 12:12:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 68FD037B503 for ; Sun, 1 Oct 2000 12:12:52 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e91JEPh03548; Sun, 1 Oct 2000 12:14:26 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010011914.e91JEPh03548@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jordan Hubbard Cc: Michael Harnois , current@FreeBSD.ORG Subject: Re: Today -current broken on build In-reply-to: Your message of "Sun, 01 Oct 2000 11:54:05 PDT." <9417.970426445@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Oct 2000 12:14:25 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I hate to spoil the moment ... but does anyone have an idea what the > > fix is? Nothing in the amd directory seems to have changed in the > > past couple of weeks, so it must be somewhere else, and I'm not bright > > enough to figure out where. > > Yeah, somebody forgot that typedefs and structure names can't > conflict. :) I've just committed the fix. Er, this is probably the wrong fix. It sounds like the kernel 'callout' structure is ending up visible in userland, which it shouldn't. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 12:21: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 881C537B503; Sun, 1 Oct 2000 12:20:55 -0700 (PDT) Received: from localhost (rjgdzw@localhost [127.0.0.1] (may be forged)) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id e91JKk549150; Sun, 1 Oct 2000 15:20:49 -0400 (EDT) (envelope-from green@FreeBSD.org) Message-Id: <200010011920.e91JKk549150@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Mike Smith Cc: Jordan Hubbard , Michael Harnois , current@FreeBSD.org Subject: Re: Today -current broken on build In-Reply-To: Message from Mike Smith of "Sun, 01 Oct 2000 12:14:25 PDT." <200010011914.e91JEPh03548@mass.osd.bsdi.com> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Oct 2000 15:20:45 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > I hate to spoil the moment ... but does anyone have an idea what the > > > fix is? Nothing in the amd directory seems to have changed in the > > > past couple of weeks, so it must be somewhere else, and I'm not bright > > > enough to figure out where. > > > > Yeah, somebody forgot that typedefs and structure names can't > > conflict. :) I've just committed the fix. > > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. Thing is, I for one can't figure out what just changed. I've been manually following all the ways sys/callout.h would be included, and none seem to apply here. For example, sys/systm.h isn't included in any way I can tell by this amd file, and sys/callout.h isn't explicitly either. This is really annoying. So, sys/callout.h should be in #ifdef _KERNEL #endif /* _KERNEL */, but I just can't find out what broke it in the first place so I didn't want to fix anything. It would be nice to have the system Mozilla uses for this where we can pinpoint automatically what commit broke things. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 12:22:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id DA96C37B503; Sun, 1 Oct 2000 12:22:39 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e91JMNU53246; Sun, 1 Oct 2000 12:22:24 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Mike Smith Cc: Michael Harnois , current@FreeBSD.ORG Subject: Re: Today -current broken on build In-Reply-To: Message from Mike Smith of "Sun, 01 Oct 2000 12:14:25 PDT." <200010011914.e91JEPh03548@mass.osd.bsdi.com> Date: Sun, 01 Oct 2000 12:22:23 -0700 Message-ID: <53242.970428143@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. It wasn't clear to me if it was clashing with the internal typedef or something else - the namespace issues with gcc are a little unclear to me here (at least it's not VMS C, with a global member name space :). In any case, we can certainly revert the change if it transpires that the pollution came from elsewhere and for now, at least, -current is working again. clock.c includes a butt-load of system headers through am_defs.h and I can't immediately tell if the callout stuff is being exposed inappropriately or not. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 12:45:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.atsoft.pl (ns.atsoft.pl [212.160.91.102]) by hub.freebsd.org (Postfix) with ESMTP id 3F68F37B502 for ; Sun, 1 Oct 2000 12:45:07 -0700 (PDT) Received: from kawka ([212.160.91.98]) by ns.atsoft.pl (8.10.1/8.10.1) with SMTP id e91Ligb19946 for ; Sun, 1 Oct 2000 21:44:53 GMT Message-ID: <02de01c02be0$11513fe0$0201a8c0@kawka> From: =?iso-8859-2?Q?Janusz_Or=B3owski?= To: Subject: Date: Sun, 1 Oct 2000 21:44:40 +0200 Organization: janusz@atsoft.pl MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 12:47:25 2000 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 9E4A437B503 for ; Sun, 1 Oct 2000 12:47:21 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA96796; Sun, 1 Oct 2000 12:47:16 -0700 (PDT) (envelope-from obrien) Date: Sun, 1 Oct 2000 12:47:16 -0700 From: "David O'Brien" To: Michael Harnois , current@FreeBSD.ORG Subject: Re: Today -current broken on build Message-ID: <20001001124716.A96755@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <9417.970426445@winston.osd.bsdi.com> <200010011914.e91JEPh03548@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010011914.e91JEPh03548@mass.osd.bsdi.com>; from msmith@freebsd.org on Sun, Oct 01, 2000 at 12:14:25PM -0700 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 Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote: > > > I hate to spoil the moment ... but does anyone have an idea what the > > > fix is? Nothing in the amd directory seems to have changed in the > > > past couple of weeks, so it must be somewhere else, and I'm not bright > > > enough to figure out where. > > > > Yeah, somebody forgot that typedefs and structure names can't > > conflict. :) I've just committed the fix. > > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. This commit also took a file off the vendor branch and the maintainer of src/contrib was not consulted. The committer that committed something w/o testing `make world' should have backed out their commit and then discussed that they wanted a change made in Amd or taken a different approach in their commit. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 13: 6:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id DA31437B503 for ; Sun, 1 Oct 2000 13:06:12 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e91K7Sh03718; Sun, 1 Oct 2000 13:07:29 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010012007.e91K7Sh03718@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-reply-to: Your message of "Sun, 01 Oct 2000 22:04:52 +0900." <20001001220452O.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Oct 2000 13:07:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > PowerResource code keeps pointers to the PowerResource objects, then > > > finds a pointer to methods of the object dynamically. Can we do it in > > > similar way for thermal management? > > > > Well, yes, but you have to go back and re-parse the actual AML. I'm not > > even sure if it's safe to assume that the thermal zone is in the same > > place in the bytecode (it should be, I guess). > > I also think it shoud be... /me crosses his fingers > > I went reading through the ACPICA documentation to work this out. They > > acually have a very nice technique where they attach the I/O handlers to > > a point in the namespace, and then when something attempts I/O, they > > travel back up the namespace to the root, looking for the first matching > > I/O handler. > > > > This means that when your EC driver finds an embedded controller, you > > just attach your I/O handler to the EC object. Then anytime someone > > tries to do I/O to the EC, your handler gets called. > > Yes, we can have large benefit by migrating to ACPICA. I suggest that > we make ACPICA version of AML interpreter run in userland as a > debugger for the first evaluation. By doing this work we can make > sure it works actually on FreeBSD and estimate the work volume of > kernel porting. Also we know the amldb is very useful from our > development experience. Indeed. I've just taken the hard path to start with, and got the kernel integration (mostly) resolved. Fortunately, the ACPICA code includes a complete user-space ACPI interpreter for just this purpose. I think some of their test code has rotted a bit (eg. their AcpiDump tool), but it shouldn't be too hard to get this going. > Another suggestion is that this migration should be done prudently. > During ACPICA porting, we add ACPICA compatible wrappers to current > aml code (e.g. AcpiWalkNamespace() -> aml_apply_foreach_found_objects()) > and modify acpi driver code so that we migrate to ACPICA smoothly. This would be very difficult. > BTW, last time Watanabe-san tried to write EC stuff, but unfortunately > his laptop was broken *twice* by testing. > Be careful, otherwise your Dell will go to the hospital 8) Ack. I'll bear that in mind. > > Hmm. I guess I should spend some more time looking at this. I don't > > mean to devalue all the work that's been put into the current AML code, > > but ACPICA has already solved a lot of the problems that we haven't even > > touched yet (Notify, locking, etc...) > > OK, before making our decision, I want to make sure something. > - Licence > Linux folks apply GPL for it. Is it possible to apply BSD style > licence for FreeBSD version of ACPICA? or should we put it sys/contrib? The Intel licence on the "generic Unix" version of ACPICA is suitable for direct inclusion in FreeBSD. I'm not sure that the Intel code shouldn't be in sys/contrib *anyway*. > - Support from Intel > My major concern is this one. I wonder whether our local changes > for ACPICA can feed back to original code. If not, maintenance will > become hard... If we do things right, we should have little trouble with this. We have some pretty good relations with the right parts of Intel, and as long as we keep the code changes clean, they should be happy to accept them. Given how much work the Intel people went through just to get their code into the Linux kernel, I think they will find us *much* more friendly. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 15: 3:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id BC70937B66C for ; Sun, 1 Oct 2000 15:03:26 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e91M4wJ00361; Sun, 1 Oct 2000 15:04:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010012204.e91M4wJ00361@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: takawata@shidahara1.planet.sci.kobe-u.ac.jp, haro@tk.kubota.co.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Interesting AML bug... recommended workaround? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Oct 2000 15:04:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's what seems to be an interesting AML or AML parser bug. OperationRegion(PSRG, SystemMemory, 0x0410, 0x1) Field(PSRG, DWordAcc, NoLock, Preserve) { , 2, PS2E, 1 } The field is marked for 32-bit access, but the region is only 1 byte wide. What's the correct thing to do here? Expand the region to accomodate the field's access requirements? Constrain the access size of the field to that of the region? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 15:16:27 2000 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 5E43C37B66C for ; Sun, 1 Oct 2000 15:16:25 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e91MGPP66217; Sun, 1 Oct 2000 17:16:25 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: current@FreeBSD.ORG Subject: Re: Today -current broken on build Keywords: fix,commit References: <9417.970426445@winston.osd.bsdi.com> <200010011914.e91JEPh03548@mass.osd.bsdi.com> <20001001124716.A96755@dragon.nuxi.com> From: Michael Harnois Date: 01 Oct 2000 17:16:25 -0500 In-Reply-To: <20001001124716.A96755@dragon.nuxi.com> Message-ID: <86itrcgqbq.fsf@mharnois.workgroup.net> Lines: 32 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is better than watching the soaps. I'll be waiting anxiously for the next installment. ;<) On Sun, 1 Oct 2000 12:47:16 -0700, "David O'Brien" said: > On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote: >> > > I hate to spoil the moment ... but does anyone have an idea >> what the > > fix is? Nothing in the amd directory seems to >> have changed in the > > past couple of weeks, so it must be >> somewhere else, and I'm not bright > > enough to figure out >> where. > > Yeah, somebody forgot that typedefs and structure >> names can't > conflict. :) I've just committed the fix. >> >> Er, this is probably the wrong fix. It sounds like the kernel >> 'callout' structure is ending up visible in userland, which it >> shouldn't. > This commit also took a file off the vendor branch and the > maintainer of src/contrib was not consulted. > The committer that committed something w/o testing `make world' > should have backed out their commit and then discussed that they > wanted a change made in Amd or taken a different approach in > their commit. > -- -- David (obrien@FreeBSD.org) -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org "Doing bad things is not evangelism." -- Ann Hafften To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 15:38:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from web2001.mail.yahoo.com (web2001.mail.yahoo.com [128.11.68.201]) by hub.freebsd.org (Postfix) with SMTP id 32C9837B66D for ; Sun, 1 Oct 2000 15:38:26 -0700 (PDT) Received: (qmail 6179 invoked by uid 60001); 1 Oct 2000 22:38:25 -0000 Message-ID: <20001001223825.6178.qmail@web2001.mail.yahoo.com> Received: from [212.151.148.176] by web2001.mail.yahoo.com; Sun, 01 Oct 2000 15:38:25 PDT Date: Sun, 1 Oct 2000 15:38:25 -0700 (PDT) From: krister johansson To: FreeBSD-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 subscribe krister.lars.johansson@ssab.com __________________________________________________ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 17: 7: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailout1.hananet.net (mailout1.hananet.net [210.220.163.34]) by hub.freebsd.org (Postfix) with ESMTP id 6E62837B677 for ; Sun, 1 Oct 2000 17:05:37 -0700 (PDT) Received: from gnomaniac.myhome ([211.58.2.102]) by mailout1.hananet.net (Netscape Messaging Server 4.15) with ESMTP id G1S08P00.H44; Mon, 2 Oct 2000 09:05:13 +0900 Received: (from cjh@localhost) by gnomaniac.myhome (8.11.0/8.11.0) id e9204P601247; Mon, 2 Oct 2000 09:04:25 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) X-Authentication-Warning: gnomaniac.myhome: cjh set sender to cjh@kr.FreeBSD.org using -f To: Warner Losh Cc: current@freebsd.org Subject: Re: Today -current broken on build References: <200010011735.LAA00782@harmony.village.org> From: CHOI Junho Date: 02 Oct 2000 09:03:53 +0900 In-Reply-To: Warner Losh's message of "Sun, 01 Oct 2000 11:35:32 -0600" Message-ID: <86vgvcjehi.fsf@gnomaniac.myhome> Lines: 17 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 >>>>> "WL" == Warner Losh writes: WL> this is an *UN*acceptible attitude. CHOI-san is reporting a -san is Japanese word, and I am Korean. Due to historical reason, most Korean do not want to be treated as Japanese and most of them will be angry. Please don't call me 'CHOI-san'. Equivalent word is '-nim' in Korean online community. But it should be after his given name, not surname. 'Junho-nim' is good, but you don't have to always. -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho KFUG Web Data Bank FreeBSD, GNU/Linux Developer http://people.FreeBSD.org/~cjh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 17:14:43 2000 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 01BA637B503; Sun, 1 Oct 2000 17:14:36 -0700 (PDT) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id JAA62399; Mon, 2 Oct 2000 09:14:35 +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 JAA01654; Mon, 2 Oct 2000 09:14:34 +0900 (JST) To: freebsd-current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: [CFR] ncv, nsp, stg SCSI drivers In-Reply-To: Your message of "Sat, 30 Sep 2000 15:20:07 +0900" <20000930152007K.non@ever.sanda.gr.jp> References: <20000930152007K.non@ever.sanda.gr.jp> X-Mailer: Mew version 1.93 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: <20001002091434A.non@ever.sanda.gr.jp> Date: Mon, 02 Oct 2000 09:14:34 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, the files colud not fetch. I think you can now fetch them. // Noriaki Mitsunaga From: non@ever.sanda.gr.jp Date: Sat, 30 Sep 2000 15:20:07 +0900 > From: Poul-Henning Kamp > Date: Wed, 27 Sep 2000 15:25:42 +0200 > > Use a normal timeout ? > > I changed to use timeout() and now they do not change clock.c. > > Updated files can be obtained from, > http://home.jp.freebsd.org/~non/scsi_low-20000930.tar.gz (added files) > http://home.jp.freebsd.org/~non/scsi_low-20000930.diff.gz (diff to current) > http://home.jp.freebsd.org/~non/scsi_low4-20000930.diff.gz (diff to stable) > > You will need the tar.gz file and one of diff.gz file. Or you can > obtain the diff from, > http://home.jp.freebsd.org/~non/scsi_low-20000926-20000930.diff.gz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 18:14: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 7A2EB37B502; Sun, 1 Oct 2000 18:13:57 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e921DuL02614; Sun, 1 Oct 2000 18:13:56 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma002609; Sun, 1 Oct 2000 18:13:36 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id SAA71517; Sun, 1 Oct 2000 18:13:36 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200010020113.SAA71517@bubba.whistle.com> Subject: Re: sendmail related changes In-Reply-To: <14806.44340.887777.120946@horsey.gshapiro.net> "from Gregory Neil Shapiro at Sep 30, 2000 08:19:16 pm" To: Gregory Neil Shapiro Date: Sun, 1 Oct 2000 18:13:36 -0700 (PDT) Cc: freebsd-current@FreeBSD.org, cvs-committers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Neil Shapiro writes: > sendmail's version of vacation is completely backwards compatible with the > existing version. It also contains new features and bug fixes that are not > in the current FreeBSD version. This will take care of PR bin/15227. > > 2. Copy cf config building tree into /usr/share/sendmail/cf Yes to all three! For #2, we can maybe go a step further.. the README in that directory is somewhat daunting. For example, we could also copy the /usr/src/etc/sendmail directory into /usr/share/sendmail/cf/freebsd or something like that (maybe with a simpler Makefile) and include a few more example config files besides "freefall.mc" that demonstrate how to configure in various scenarios. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 21:11:39 2000 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 22E6937B66C for ; Sun, 1 Oct 2000 21:11:37 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id GAA91351 for freebsd-current@freebsd.org; Mon, 2 Oct 2000 06:11:35 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id e921GfN66232 for ; Mon, 2 Oct 2000 03:16:42 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Mon, 2 Oct 2000 03:16:41 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: adv0 -> panic 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 get a "Panic: Page fault while in supervisor mode" just after adv0 is displayed during boot. If I just remove the card, I can boot. Current current. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 21:12: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 2148B37B502 for ; Sun, 1 Oct 2000 21:11:55 -0700 (PDT) Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id VAA06013; Sun, 1 Oct 2000 21:03:27 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id AAA01643; Mon, 2 Oct 2000 00:11:48 -0400 (EDT) Received: from 110.net (corp-no-243 [132.245.139.243]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id AAA10577; Mon, 2 Oct 2000 00:11:41 -0400 for Message-ID: <39D80B01.90BFADFF@110.net> Date: Mon, 02 Oct 2000 00:11:45 -0400 From: Chain Lee X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Cc: chain@110.net Subject: ATA disk support broken for PC-CARD in 5.0-CURRENT?? Content-Type: multipart/mixed; boundary="------------5973DFB385669862D1224E5A" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------5973DFB385669862D1224E5A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, PC-CARD IDE hard disk and compact flash card support is broken in recent 5.0-CURRENT. Does anyone have an idea what the problem is? Please copy reply to me. I don't subscribe to the 'current' mailing list. Thanks, -chain --------------5973DFB385669862D1224E5A Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: Received: from lavender.sanpei.org (ppp128.dialup.st.keio.ac.jp [131.113.27.128]) by ms01.conversent.com (8.10.2/8.10.2) with ESMTP id e91E0Zw29906 for ; Sun, 1 Oct 2000 10:00:37 -0400 (EDT) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id e91Dtld01154; Sun, 1 Oct 2000 22:55:47 +0900 (JST) Message-Id: <200010011355.e91Dtld01154@lavender.sanpei.org> To: chain@110.net Cc: non@FreeBSD.org From: sanpei@FreeBSD.org Subject: Re: PCCARD support in FreeBSD 5.0-CURRENT In-Reply-To: Your message of "Sun, 01 Oct 2000 00:09:15 -0400" References: <39D6B8EB.44CAEFC2@110.net> X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 01 Oct 2000 22:55:47 +0900 Sender: sanpei@sanpei.org X-Mozilla-Status2: 00000000 >I have been using compact flash card and ATA disks on my >Toshiba 3440CT running FreeBSD 4.0 release without problem. >Recently I updated my system to 5.0-CURRENT (I use cvsup >every now and then and rebuild and install). Now whenever I >plug in a compact flash card or a 2.5 inch ide disk I get the following: > >--------- >pccard: card inserted, slot 0 >Sep 30 23:49:37 alice pccardd[33545]: Card "Microtech International >Inc."("IDE PCCARD") [(C) ARCHOS S.A. 1995-98 Fax +33 1 60 >13 99 18] [(null)] matched "Microtech International Inc." ("IDE PCCARD") >[(null)] [(null)] >ata4 at port 0x250-0x25f irq 5 slot 0 on pccard0 >ata4-master: ata_command: timeout waiting for intr >ata4-master: identify failed >Sep 30 23:49:52 alice pccardd[33545]: ata4: Microtech International Inc. >(IDE PCCARD) inserted. >--------- > >I cannot use any of the PCCARD device using the ATA driver any more. >Do you have any idea what is going on? I would appreciate your help in >getting >this working again. I also have same problem. I could use compact flash under 5-current last month...... I think this problem is related to sys/dev/ata changes. Would you ask this problem in current@FreeBSD.org mailing list? --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. --------------5973DFB385669862D1224E5A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 22:59:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 8F94637B502; Sun, 1 Oct 2000 22:59:27 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e925xOr75697; Mon, 2 Oct 2000 14:59:24 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: msmith@freebsd.org Cc: iwasaki@jp.FreeBSD.org, haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-Reply-To: <200010012007.e91K7Sh03718@mass.osd.bsdi.com> References: <20001001220452O.iwasaki@jp.FreeBSD.org> <200010012007.e91K7Sh03718@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001002145821S.iwasaki@jp.FreeBSD.org> Date: Mon, 02 Oct 2000 14:58:21 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 59 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes, we can have large benefit by migrating to ACPICA. I suggest that > > we make ACPICA version of AML interpreter run in userland as a > > debugger for the first evaluation. By doing this work we can make > > sure it works actually on FreeBSD and estimate the work volume of > > kernel porting. Also we know the amldb is very useful from our > > development experience. > > Indeed. I've just taken the hard path to start with, and got the kernel > integration (mostly) resolved. Fortunately, the ACPICA code includes a > complete user-space ACPI interpreter for just this purpose. I think some > of their test code has rotted a bit (eg. their AcpiDump tool), but it > shouldn't be too hard to get this going. I and acpi-jp folks discussed ACPICA migration last night, there is no objections so far. Most of them agreed that evaluation must be done at least. Some people already started lerning ACPICA with documents and source code. Mike, I'm feeling we need to have a migration plan. Do you have any plan on this? # I have to learn first before my participation to the discussion :-) > > Another suggestion is that this migration should be done prudently. > > During ACPICA porting, we add ACPICA compatible wrappers to current > > aml code (e.g. AcpiWalkNamespace() -> aml_apply_foreach_found_objects()) > > and modify acpi driver code so that we migrate to ACPICA smoothly. > > This would be very difficult. OK, but I'll try, this will be my private project. I won't complain anything if most of the code is deleted after migration. I hope I'll get some understanding on ACPICA programming. > > OK, before making our decision, I want to make sure something. > > - Licence > > Linux folks apply GPL for it. Is it possible to apply BSD style > > licence for FreeBSD version of ACPICA? or should we put it sys/contrib? > > The Intel licence on the "generic Unix" version of ACPICA is suitable for > direct inclusion in FreeBSD. I'm not sure that the Intel code shouldn't > be in sys/contrib *anyway*. I see. I found that we may have additional license terms, but I leave it to your discretion. > > - Support from Intel > > My major concern is this one. I wonder whether our local changes > > for ACPICA can feed back to original code. If not, maintenance will > > become hard... > > If we do things right, we should have little trouble with this. We have > some pretty good relations with the right parts of Intel, and as long as > we keep the code changes clean, they should be happy to accept them. OK. > Given how much work the Intel people went through just to get their code > into the Linux kernel, I think they will find us *much* more friendly. 8) # Welcome new committers from Intel :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 22:59:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id CDF4A37B502; Sun, 1 Oct 2000 22:59:44 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e925xgr75782; Mon, 2 Oct 2000 14:59:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: msmith@freebsd.org Cc: iwasaki@jp.FreeBSD.org, takawata@shidahara1.planet.sci.kobe-u.ac.jp, haro@tk.kubota.co.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: Interesting AML bug... recommended workaround? In-Reply-To: <200010012204.e91M4wJ00361@mass.osd.bsdi.com> References: <200010012204.e91M4wJ00361@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001002145839G.iwasaki@jp.FreeBSD.org> Date: Mon, 02 Oct 2000 14:58:39 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's what seems to be an interesting AML or AML parser bug. > > OperationRegion(PSRG, SystemMemory, 0x0410, 0x1) > Field(PSRG, DWordAcc, NoLock, Preserve) { > , 2, > PS2E, 1 > } > > The field is marked for 32-bit access, but the region is only 1 byte > wide. What's the correct thing to do here? Expand the region to > accomodate the field's access requirements? Constrain the access size of > the field to that of the region? I thought read 32-bit, update target bits, write back whole 32-bit for updating. For reading value, read 32-bit and shift & mask bits as well. I hope I could understand description in Spec 15.2.3.3.1.9; "If desired, AccessType can be used to force minimum access width." Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 23:40:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 7BE6B37B66E for ; Sun, 1 Oct 2000 23:40:43 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e926g4h00359; Sun, 1 Oct 2000 23:42:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010020642.e926g4h00359@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-reply-to: Your message of "Mon, 02 Oct 2000 14:58:21 +0900." <20001002145821S.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Oct 2000 23:42:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Yes, we can have large benefit by migrating to ACPICA. I suggest that > > > we make ACPICA version of AML interpreter run in userland as a > > > debugger for the first evaluation. By doing this work we can make > > > sure it works actually on FreeBSD and estimate the work volume of > > > kernel porting. Also we know the amldb is very useful from our > > > development experience. > > > > Indeed. I've just taken the hard path to start with, and got the kernel > > integration (mostly) resolved. Fortunately, the ACPICA code includes a > > complete user-space ACPI interpreter for just this purpose. I think some > > of their test code has rotted a bit (eg. their AcpiDump tool), but it > > shouldn't be too hard to get this going. > > I and acpi-jp folks discussed ACPICA migration last night, there is no > objections so far. Most of them agreed that evaluation must be done > at least. Some people already started lerning ACPICA with documents and > source code. > Mike, I'm feeling we need to have a migration plan. Do you have any > plan on this? I have an enormous patch that I can put up later tonight on Freefall. I have the ACPICA 20000915 release fully integrated, and I've ported their sample OSPM components just for fun (there are problems with these, and I think we will only want them as examples). I also ported their ACPI dump utility, but it's output is much uglier than ours. The Intel code is clean, and the operating system interfaces are well documented. I've mailed a promising contact at Intel to see how they feel about accepting our changes. There is still a lot of work to be done. I want to at least have one sample acpi child device ready - I'll try converting their thermal management OSPM component so that you can play with it. 8) (There is a chicken-and-egg problem with their bus manager component and the embedded controller support which means that I still have a hot laptop. Grrr. 8) > # I have to learn first before my participation to the discussion :-) I hope that you will find ACPICA well documented. You should read the developer's guide first, as it contains lots of very useful information. > > > Another suggestion is that this migration should be done prudently. > > > During ACPICA porting, we add ACPICA compatible wrappers to current > > > aml code (e.g. AcpiWalkNamespace() -> aml_apply_foreach_found_objects()) > > > and modify acpi driver code so that we migrate to ACPICA smoothly. > > > > This would be very difficult. > > OK, but I'll try, this will be my private project. I won't complain > anything if most of the code is deleted after migration. I hope I'll > get some understanding on ACPICA programming. I think that it will be easier just to adapt existing code to the new interfaces than to write a compatibility layer. > > The Intel licence on the "generic Unix" version of ACPICA is suitable for > > direct inclusion in FreeBSD. I'm not sure that the Intel code shouldn't > > be in sys/contrib *anyway*. > > I see. I found that we may have additional license terms, but I leave > it to your discretion. The additional terms are just Intel's legal department trying to make the BSD license look big and scary. 8) We've talked to Intel about this same license text in other contexts before; it is the same as the 4-clause BSD license. > > Given how much work the Intel people went through just to get their code > > into the Linux kernel, I think they will find us *much* more friendly. 8) > > # Welcome new committers from Intel :-) Now *that* would be *nice*. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 1 23:47:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 5231C37B502 for ; Sun, 1 Oct 2000 23:47:27 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e926mxh00396; Sun, 1 Oct 2000 23:48:59 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010020648.e926mxh00396@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: takawata@shidahara1.planet.sci.kobe-u.ac.jp, haro@tk.kubota.co.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: Interesting AML bug... recommended workaround? In-reply-to: Your message of "Mon, 02 Oct 2000 14:58:39 +0900." <20001002145839G.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Oct 2000 23:48:59 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Here's what seems to be an interesting AML or AML parser bug. > > > > OperationRegion(PSRG, SystemMemory, 0x0410, 0x1) > > Field(PSRG, DWordAcc, NoLock, Preserve) { > > , 2, > > PS2E, 1 > > } > > > > The field is marked for 32-bit access, but the region is only 1 byte > > wide. What's the correct thing to do here? Expand the region to > > accomodate the field's access requirements? Constrain the access size of > > the field to that of the region? > > I thought read 32-bit, update target bits, write back whole 32-bit for > updating. For reading value, read 32-bit and shift & mask bits as well. > I hope I could understand description in Spec 15.2.3.3.1.9; "If desired, > AccessType can be used to force minimum access width." This is clarified in the 2.0 spec 16.2.3.3.1.11; the short answer is that it's illegal. There is already a workaround in the ACPICA code that truncates over-sized operation requests, but it didn't fix up the granularity to match. I've added that support and will send it back to Intel. I'll also bug Intel about the BIOS in this machine (ISP1100), since this is a real error. I doubt they'll do much about it though. Regards, -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 0: 5:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 4220E37B503 for ; Mon, 2 Oct 2000 00:05:30 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e9275TG05860 for ; Mon, 2 Oct 2000 00:05:29 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010020705.e9275TG05860@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: HEADS UP - cvs-1.11 imported Date: Mon, 02 Oct 2000 00:05:29 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've updated the cvs base code. I'm pretty confident that it has come through ok, but please keep an eye out for weird stuff due to repairs of merge conflicts. 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 Mon Oct 2 0:27:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from squishycow.goldenterrace.com.au (squishycow.goldenterrace.com.au [203.41.110.130]) by hub.freebsd.org (Postfix) with ESMTP id 4ADE537B502; Mon, 2 Oct 2000 00:27:09 -0700 (PDT) Received: from roaming.cacheboy.net (unknown [203.41.110.145]) by squishycow.goldenterrace.com.au (Postfix) with ESMTP id A5AA419D17; Mon, 2 Oct 2000 18:27:05 +1100 (EST) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e927R1801409; Mon, 2 Oct 2000 09:27:01 +0200 (CEST) (envelope-from adrian) Date: Mon, 2 Oct 2000 09:26:59 +0200 From: Adrian Chadd To: freebsd-fs@freebsd.org Cc: freebsd-current@freebsd.org Subject: fsck wrappers, commit candidate Message-ID: <20001002092659.A1395@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 24, 2000, Adrian Chadd wrote: > On Sun, Sep 24, 2000, Kris Kennaway wrote: > > > > The trouble is that some of the FS strings have spaces in their filenames. > > > This might confuse a few people. > > > > How about mapping spaces to '_' characters - I doubt it would cause any > > namespace collisions. > > Yes, as bp mentioned to me before, so I'm thinking about passing the fsname > through a tolower() and a s/ /_/g before using it as a filename. > > Any problems with this? Ok, I've since done this and I've updated the tarball again at http://people.freebsd.org/~adrian/fsck/ . This is the version which I would like to commit, so I'd like some feedback beforehand. Thanks! Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 1:15:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 71D4237B503 for ; Mon, 2 Oct 2000 01:15:24 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9288Gh00664; Mon, 2 Oct 2000 01:08:16 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010020808.e9288Gh00664@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Mitsuru IWASAKI , haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-reply-to: Your message of "Sun, 01 Oct 2000 23:42:04 PDT." <200010020642.e926g4h00359@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Oct 2000 01:08:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have an enormous patch that I can put up later tonight on Freefall. Actually, I couldn't make CVS do what I wanted, so it's a big tarball with an itty-bitty little patch instead. This requires an up-to-date -current kernel (for the pci_cfgreg changes, etc.) I haven't done anything special with newbus attachments yet, and the embedded controller stuff is still broken, but this should compile and run. It needs resource management work (only interrupts are handled correctly) and lots of event handlers and so on, but it should be a good foundation to start with. Comments and suggestions would definitely be appreciated. http://people.freebsd.org/~msmith/acpica-bsd-20001002.tar.gz -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 2:52:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 49ED737B503; Mon, 2 Oct 2000 02:52:31 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e929qSr38391; Mon, 2 Oct 2000 18:52:28 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: msmith@freebsd.org Cc: iwasaki@jp.FreeBSD.org, haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-Reply-To: <200010020808.e9288Gh00664@mass.osd.bsdi.com> References: <200010020642.e926g4h00359@mass.osd.bsdi.com> <200010020808.e9288Gh00664@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001002185030U.iwasaki@jp.FreeBSD.org> Date: Mon, 02 Oct 2000 18:50:30 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 57 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, I couldn't make CVS do what I wanted, so it's a big tarball > with an itty-bitty little patch instead. > > This requires an up-to-date -current kernel (for the pci_cfgreg changes, > etc.) > > I haven't done anything special with newbus attachments yet, and the > embedded controller stuff is still broken, but this should compile and > run. It needs resource management work (only interrupts are handled > correctly) and lots of event handlers and so on, but it should be a good > foundation to start with. Great! This is really great!! I didn't think we can have ACPICA kernel so earlier. > Comments and suggestions would definitely be appreciated. > > http://people.freebsd.org/~msmith/acpica-bsd-20001002.tar.gz OK, I have a patch for AcpiOsSleep and AcpiOsSleepUsec which I was involed in recently. For Semaphore, mtx_* (ported from BSD/OS?) is used in your implementation. I just wonder if NetBSD people will use traditional lock... --- OsdSchedule.c- Mon Oct 2 18:20:32 2000 +++ OsdSchedule.c Mon Oct 2 18:34:24 2000 @@ -36,6 +36,7 @@ #include #include #include +#include /* * This is a little complicated due to the fact that we need to build and then @@ -112,11 +113,20 @@ void AcpiOsSleep (UINT32 Seconds, UINT32 Milliseconds) { - tsleep(NULL, 0, "acpislp", (Seconds * hz) + Milliseconds / (1000 * hz)); + int timo; + + timo = (Seconds * hz) + Milliseconds / (1000 * hz); + if (timo == 0) /* 0 means no timeout... */ + timo = 1; + tsleep(NULL, 0, "acpislp", timo); } void AcpiOsSleepUsec (UINT32 Microseconds) { - tsleep(NULL, 0, "acpislp", Microseconds / (1000000 * hz)); + if (Microseconds > 1000) { /* the interpreter will be released */ + AcpiOsSleep(0, Microseconds / 1000); + } else { + DELAY(Microseconds); + } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 3: 6:22 2000 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 5E68B37B502 for ; Mon, 2 Oct 2000 03:06:19 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e92A6IN18800 for ; Mon, 2 Oct 2000 12:06:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: #include in From: Poul-Henning Kamp Date: Mon, 02 Oct 2000 12:06:18 +0200 Message-ID: <18798.970481178@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trying to compile the ircII port, it crashes with: ===> Building for ircii-4.4X cc -I. -I/usr/ports/irc/ircII/work/ircii-4.4X/include -O -pipe -DHAVE_CONFIG_H -c /usr/ports/irc/ircII/work/ircii-4.4X/source/alias.c In file included from /usr/include/sys/queue.h:40, from /usr/include/netinet6/in6.h:76, from /usr/include/netinet/in.h:475, from /usr/ports/irc/ircII/work/ircii-4.4X/include/irc.h:79, from /usr/ports/irc/ircII/work/ircii-4.4X/source/alias.c:35: /usr/ports/irc/ircII/work/ircii-4.4X/include/struct.h:51: syntax error before `_' This is because there is a file called "struct.h" in the ircII distribution. The addition of #include to looks a bit unsettling to me: A sys/* file shouldn't reference a /usr/include file I think ? Is the correct thing not to mv to , create a which just pulls in and have #include ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Oct 2 3:18:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 3B19437B670; Mon, 2 Oct 2000 03:15:31 -0700 (PDT) Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id MAA81219; Mon, 2 Oct 2000 12:15:01 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by C992631-A.pinol1.sfba.home.com (8.11.0/8.11.0) id e92AEWb73388; Mon, 2 Oct 2000 03:14:32 -0700 (PDT) (envelope-from reg) Date: Mon, 2 Oct 2000 03:14:32 -0700 From: Jeremy Lea To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: #include in Message-ID: <20001002031432.I30468@shale.csir.co.za> References: <18798.970481178@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <18798.970481178@critter>; from phk@FreeBSD.ORG on Mon, Oct 02, 2000 at 12:06:18PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, Oct 02, 2000 at 12:06:18PM +0200, Poul-Henning Kamp wrote: > This is because there is a file called "struct.h" in the ircII distribution. > > The addition of #include to looks a bit unsettling > to me: A sys/* file shouldn't reference a /usr/include file I think ? > > Is the correct thing not to mv to , create > a which just pulls in and have > #include ? This breaks several other ports (like BitchX). -Jeremy -- FreeBSD - Because the best things in life are free... 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 Oct 2 3:20:43 2000 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 534AF37B502; Mon, 2 Oct 2000 03:20:40 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e92AKdN18869; Mon, 2 Oct 2000 12:20:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Jeremy Lea Cc: current@FreeBSD.ORG Subject: Re: #include in In-Reply-To: Your message of "Mon, 02 Oct 2000 03:14:32 PDT." <20001002031432.I30468@shale.csir.co.za> Date: Mon, 02 Oct 2000 12:20:39 +0200 Message-ID: <18867.970482039@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001002031432.I30468@shale.csir.co.za>, Jeremy Lea writes: >> Is the correct thing not to mv to , create >> a which just pulls in and have >> #include ? > >This breaks several other ports (like BitchX). I think this breaks all IRC's which are cloned from the same origin :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Oct 2 8:51:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 6885037B502 for ; Mon, 2 Oct 2000 08:51:20 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id LAA56697; Mon, 2 Oct 2000 11:51:14 -0400 (EDT) Date: Mon, 2 Oct 2000 11:51:14 -0400 (EDT) From: "Matthew N. Dodd" To: Motomichi Matsuzaki Cc: current@FreeBSD.org Subject: Re: NS DP83932 SONIC driver for pc98 In-Reply-To: <8666nml37d.wl@tkc.att.ne.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 Sun, 24 Sep 2000, Motomichi Matsuzaki wrote: > This is very stable for usual operation. > I hope this will be merged into the tree. I'll take a look at it. I think I've got the beginnings of an EISA attachment. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 10:16: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 1387E37B503; Mon, 2 Oct 2000 10:16:04 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e92HAdU58460; Mon, 2 Oct 2000 10:10:39 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Poul-Henning Kamp Cc: Jeremy Lea , current@FreeBSD.ORG Subject: Re: #include in In-Reply-To: Message from Poul-Henning Kamp of "Mon, 02 Oct 2000 12:20:39 +0200." <18867.970482039@critter> Date: Mon, 02 Oct 2000 10:10:39 -0700 Message-ID: <58456.970506639@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >This breaks several other ports (like BitchX). > > I think this breaks all IRC's which are cloned from the same origin :-) I'm still looking for the downside to this. ;-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 10:51:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (massive.dataloss.net [212.189.232.193]) by hub.freebsd.org (Postfix) with SMTP id 5DC8737B502 for ; Mon, 2 Oct 2000 10:51:04 -0700 (PDT) Received: (qmail 98262 invoked by uid 1000); 2 Oct 2000 17:53:07 -0000 Date: Mon, 2 Oct 2000 19:53:07 +0200 From: Peter van Dijk To: current@FreeBSD.ORG Subject: Re: #include in Message-ID: <20001002195307.A97178@dataloss.net> Mail-Followup-To: current@FreeBSD.ORG References: <58456.970506639@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <58456.970506639@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Mon, Oct 02, 2000 at 10:10:39AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 02, 2000 at 10:10:39AM -0700, Jordan Hubbard wrote: > > >This breaks several other ports (like BitchX). > > > > I think this breaks all IRC's which are cloned from the same origin :-) > > I'm still looking for the downside to this. ;-) 'HEY!' ;P Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 10:59:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from sv02.kmjeuro.com (fireblade.austria.kmjeuro.com [212.236.19.28]) by hub.freebsd.org (Postfix) with ESMTP id A654737B503 for ; Mon, 2 Oct 2000 10:59:03 -0700 (PDT) Received: (from root@localhost) by sv02.kmjeuro.com (8.9.3/8.9.3) id TAA36952 for freebsd-current@freebsd.org; Mon, 2 Oct 2000 19:58:55 +0200 (CEST) (envelope-from k.joch@kmjeuro.com) Received: from wsjk02 (151ppp.infohighway.proline.at [212.236.19.5]) by sv02.kmjeuro.com (8.9.3/8.9.3) with SMTP id TAA36900 for ; Mon, 2 Oct 2000 19:58:48 +0200 (CEST) (envelope-from k.joch@kmjeuro.com) Message-ID: <01f601c02c9a$6ce72fd0$4800a8c0@wsjk02.kmjeuro.com> From: "Karl M. Joch" To: Subject: What happens when pressing "a key to reboot" Date: Mon, 2 Oct 2000 19:58:08 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG after cvsup and make world today i want to investigate why my notebook cant reboot. but i am really new to the source of freebsd. can one tell me where to look? i can shutdown fine with shutdown -h now till the system writes "press any key to reboot". when pressing the key the screen gets immediatly black and the system hangs forever. i would like to compare the cvsupdates since mid of august, but i have no real idea where to start. is there any docu to read about the source, giving a newbee a start? or any hint what happens when pressing the key? would really like to find it out, because not beeing able to reboot and not beeing able to use apm is not really fun sometimes. especially where current works really fine on my notebook and a older siemens P75 dual CPU box. thanks, regards, Karl M. Joch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 12:36:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F3C7237B66D for ; Mon, 2 Oct 2000 12:36:50 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e92JanI03890; Mon, 2 Oct 2000 13:36:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA13954; Mon, 2 Oct 2000 13:36:49 -0600 (MDT) Message-Id: <200010021936.NAA13954@harmony.village.org> To: Chain Lee Subject: Re: ATA disk support broken for PC-CARD in 5.0-CURRENT?? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Oct 2000 00:11:45 EDT." <39D80B01.90BFADFF@110.net> References: <39D80B01.90BFADFF@110.net> Date: Mon, 02 Oct 2000 13:36:49 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39D80B01.90BFADFF@110.net> Chain Lee writes: : PC-CARD IDE hard disk and compact flash card support is broken : in recent 5.0-CURRENT. Does anyone have an idea what the problem is? : : Please copy reply to me. I don't subscribe to the 'current' mailing list. They are? Hmmm, I'll have to look at this... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 14:12:40 2000 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 4002437B502; Mon, 2 Oct 2000 14:12:37 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA41291; Mon, 2 Oct 2000 14:12:36 -0700 (PDT) (envelope-from obrien) Date: Mon, 2 Oct 2000 14:12:36 -0700 From: "David O'Brien" To: Mike Smith Cc: current@freebsd.org Subject: Re: Today -current broken on build Message-ID: <20001002141236.A41202@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <9417.970426445@winston.osd.bsdi.com> <200010011914.e91JEPh03548@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010011914.e91JEPh03548@mass.osd.bsdi.com>; from msmith@freebsd.org on Sun, Oct 01, 2000 at 12:14:25PM -0700 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 Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote: > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > structure is ending up visible in userland, which it shouldn't. The build was broken by the inclusion of in sys/sys/mbuf.h rev 1.56. includes sys/sys/proc.h as of rev 1.7. sys/sys/proc.h includes sys/sys/callout.h and that's were it comes from. -- -- David (obrien@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 Oct 2 14:22:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 3FFD037B66C; Mon, 2 Oct 2000 14:22:31 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e92LOCh03251; Mon, 2 Oct 2000 14:24:12 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010022124.e92LOCh03251@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: Today -current broken on build In-reply-to: Your message of "Mon, 02 Oct 2000 14:12:36 PDT." <.A41202@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Oct 2000 14:24:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The build was silently broken by AMD including previously. It wasn't exposed until recently. The correct fix was still to not include anywhere in AMD (or anywhere else in userland for that matter). > On Sun, Oct 01, 2000 at 12:14:25PM -0700, Mike Smith wrote: > > Er, this is probably the wrong fix. It sounds like the kernel 'callout' > > structure is ending up visible in userland, which it shouldn't. > > The build was broken by the inclusion of in > sys/sys/mbuf.h rev 1.56. includes sys/sys/proc.h as of > rev 1.7. sys/sys/proc.h includes sys/sys/callout.h and that's were it > comes from. > > -- > -- David (obrien@FreeBSD.org) > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 14:25: 5 2000 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 C822337B502; Mon, 2 Oct 2000 14:25:01 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA41459; Mon, 2 Oct 2000 14:25:01 -0700 (PDT) (envelope-from obrien) Date: Mon, 2 Oct 2000 14:25:00 -0700 From: "David O'Brien" To: Mike Smith Cc: current@freebsd.org Subject: Re: Today -current broken on build Message-ID: <20001002142500.B41202@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <.A41202@dragon.nuxi.com> <200010022124.e92LOCh03251@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010022124.e92LOCh03251@mass.osd.bsdi.com>; from msmith@freebsd.org on Mon, Oct 02, 2000 at 02:24:12PM -0700 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 Mon, Oct 02, 2000 at 02:24:12PM -0700, Mike Smith wrote: > > The build was silently broken by AMD including previously. > It wasn't exposed until recently. The correct fix was still to not > include anywhere in AMD (or anywhere else in userland for > that matter). Yes I know. I was trying to figure out and explain why it was just now exposed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 14:53:39 2000 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 C30DF37B502; Mon, 2 Oct 2000 14:53:32 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e92LrSN43780; Mon, 2 Oct 2000 23:53:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org, hackers@freebsd.org Subject: mtree verification output format From: Poul-Henning Kamp Date: Mon, 02 Oct 2000 23:53:28 +0200 Message-ID: <43778.970523608@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to change the outputformat of mtree(8) to be more systematic and machine-readable. The changes amount to: make "extra" and "missing" attributes in the output rather than prefixes which can be confused with filenames. Don't do the "run-in" of the first attribute with a short filename I attach below a before/after example which show the effect. Any objections ? Poul-Henning Before: ------------ rc: size (13134, 13135) cksum (2005920215, 873112433) ttys: cksum (2486739860, 2798556681) extra: bla malloc.conf: permissions (0755, 0777) missing: ./objformat ------------ After: ------------ rc: size (13134, 13135) cksum (2005920215, 873112433) ttys: cksum (2486739860, 2798556681) bla: extra malloc.conf: permissions (0755, 0777) ./objformat: missing ------------ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Oct 2 14:57:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 63C9F37B502; Mon, 2 Oct 2000 14:57:30 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA30548; Mon, 2 Oct 2000 17:57:29 -0400 (EDT) (envelope-from wollman) Date: Mon, 2 Oct 2000 17:57:29 -0400 (EDT) From: Garrett Wollman Message-Id: <200010022157.RAA30548@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: mtree verification output format In-Reply-To: <43778.970523608@critter> References: <43778.970523608@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > make "extra" and "missing" attributes in the output > rather than prefixes which can be confused with filenames. > Don't do the "run-in" of the first attribute with a short > filename This looks like a good change, but while you're there: > size (13134, 13135) > cksum (2005920215, 873112433) This is still very obscure; I'd like to see: size (was 1234, should be 5678) cksum (was 42424242, should be 69696969) ...so that it's clear what the meaning of the numbers is. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 14:59:31 2000 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 F3ABC37B502; Mon, 2 Oct 2000 14:59:24 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e92LxJN43885; Mon, 2 Oct 2000 23:59:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format In-Reply-To: Your message of "Mon, 02 Oct 2000 17:57:29 EDT." <200010022157.RAA30548@khavrinen.lcs.mit.edu> Date: Mon, 02 Oct 2000 23:59:19 +0200 Message-ID: <43883.970523959@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010022157.RAA30548@khavrinen.lcs.mit.edu>, Garrett Wollman write s: >< said: > >> make "extra" and "missing" attributes in the output >> rather than prefixes which can be confused with filenames. > >> Don't do the "run-in" of the first attribute with a short >> filename > >This looks like a good change, but while you're there: > >> size (13134, 13135) >> cksum (2005920215, 873112433) > >This is still very obscure; I'd like to see: > > size (was 1234, should be 5678) > cksum (was 42424242, should be 69696969) > >...so that it's clear what the meaning of the numbers is. In that case I think I would like to loose the ',' also. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Oct 2 15:54:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 28B9037B503 for ; Mon, 2 Oct 2000 15:54:13 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e92Mtgh03620; Mon, 2 Oct 2000 15:55:43 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010022255.e92Mtgh03620@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-reply-to: Your message of "Mon, 02 Oct 2000 18:50:30 +0900." <20001002185030U.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Oct 2000 15:55:42 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Great! This is really great!! I didn't think we can have ACPICA > kernel so earlier. Well, let's see if it works right first. 8) I hear from Intel that they plan to release a new code revision today, so I will be updating when they do. I also hear that Andrew Grover (the chap at Intel that's been answering my mails) has just joined acpi-jp (G'day!). > > Comments and suggestions would definitely be appreciated. > > > > http://people.freebsd.org/~msmith/acpica-bsd-20001002.tar.gz > > OK, I have a patch for AcpiOsSleep and AcpiOsSleepUsec which I was > involed in recently. Thanks, I've incorporated it. > For Semaphore, mtx_* (ported from BSD/OS?) is used in your implementation. > I just wonder if NetBSD people will use traditional lock... I guess that depends on how they decide to thread their kernel. Right now, the code can be built entirely unthreaded and that might be their best option. At some point, they'll have to bite the bullet and implement some synchronisation primitives of their own. If they have any common sense, they'll use the BSD/OS model as we have (or some variant on it). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 17:47:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from maxim.gba.oz.au (gba.gw.bit.net.au [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 51F7A37B66C for ; Mon, 2 Oct 2000 17:47:05 -0700 (PDT) Received: (qmail 90162 invoked by uid 1001); 3 Oct 2000 10:46:56 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Tue, 03 Oct 2000 10:46:56 +1000 From: Greg Black To: Poul-Henning Kamp Cc: Garrett Wollman , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format References: <43883.970523959@critter> In-reply-to: <43883.970523959@critter> of Mon, 02 Oct 2000 23:59:19 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >This is still very obscure; I'd like to see: > > > > size (was 1234, should be 5678) > > cksum (was 42424242, should be 69696969) > > > >...so that it's clear what the meaning of the numbers is. > > In that case I think I would like to loose the ',' also. While you're at it, why not use single word verbs: size (got 1234 wanted 5678) cksum (got 42424242 wanted 69696969) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 17:55: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id 8AA7437B503; Mon, 2 Oct 2000 17:54:57 -0700 (PDT) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id A61D1382; Mon, 2 Oct 2000 20:54:56 -0400 (EDT) Received: (from jon@localhost) by fury.csh.rit.edu (8.9.3+Sun/8.9.1) id UAA23283; Mon, 2 Oct 2000 20:54:28 -0400 (EDT) Date: Mon, 2 Oct 2000 20:54:28 -0400 From: Jon Parise To: Greg Black Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format Message-ID: <20001002205427.A23243@csh.rit.edu> References: <43883.970523959@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gjb-freebsd@gba.oz.au on Tue, Oct 03, 2000 at 10:46:56AM +1000 X-Operating-System: SunOS 5.7 (sun4u) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 03, 2000 at 10:46:56AM +1000, Greg Black wrote: > > > size (was 1234, should be 5678) > > > cksum (was 42424242, should be 69696969) > > > > > >...so that it's clear what the meaning of the numbers is. > > > > In that case I think I would like to loose the ',' also. > > While you're at it, why not use single word verbs: > > size (got 1234 wanted 5678) > cksum (got 42424242 wanted 69696969) Or perhaps: size (got 1234 expected 5678) cksum (got 42424242 expected 69696969) -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 17:57:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 2170737B502; Mon, 2 Oct 2000 17:57:12 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e930wfh04015; Mon, 2 Oct 2000 17:58:42 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010030058.e930wfh04015@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Black Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format In-reply-to: Your message of "Tue, 03 Oct 2000 10:46:56 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Oct 2000 17:58:41 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >This is still very obscure; I'd like to see: > > > > > > size (was 1234, should be 5678) > > > cksum (was 42424242, should be 69696969) > > > > > >...so that it's clear what the meaning of the numbers is. > > > > In that case I think I would like to loose the ',' also. > > While you're at it, why not use single word verbs: > > size (got 1234 wanted 5678) > cksum (got 42424242 wanted 69696969) Try "expected", but yes, this is a better idea. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 17:59:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from maxim.gba.oz.au (gba.gw.bit.net.au [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id E247C37B66C for ; Mon, 2 Oct 2000 17:59:48 -0700 (PDT) Received: (qmail 90542 invoked by uid 1001); 3 Oct 2000 10:59:45 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Tue, 03 Oct 2000 10:59:45 +1000 From: Greg Black To: Mike Smith Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format References: <200010030058.e930wfh04015@mass.osd.bsdi.com> In-reply-to: <200010030058.e930wfh04015@mass.osd.bsdi.com> of Mon, 02 Oct 2000 17:58:41 MST Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >This is still very obscure; I'd like to see: > > > > > > > > size (was 1234, should be 5678) > > > > cksum (was 42424242, should be 69696969) > > > > > > > >...so that it's clear what the meaning of the numbers is. > > > > > > In that case I think I would like to loose the ',' also. > > > > While you're at it, why not use single word verbs: > > > > size (got 1234 wanted 5678) > > cksum (got 42424242 wanted 69696969) > > Try "expected", but yes, this is a better idea. You're right, "expected" is better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 18:35: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id EB4D537B66C for ; Mon, 2 Oct 2000 18:34:54 -0700 (PDT) Received: from localhost (trish@localhost) by superconductor.rush.net (8.9.3/8.9.3) with ESMTP id VAA28697; Mon, 2 Oct 2000 21:34:41 -0400 (EDT) Date: Mon, 2 Oct 2000 21:34:41 -0400 (EDT) From: Siobhan Patricia Lynch X-Sender: trish@superconductor.rush.net To: Tony Johnson Cc: Gerhard Sittig , freebsd-current@FreeBSD.ORG Subject: RE: interesting problem 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 Sat, 30 Sep 2000, Tony Johnson wrote: > I must admit that I have been less then tactful about this thread. I > apologize for this. This is my last response to this because once again > this has gone on far too long. > > As far as this response goes. I sense "selective reading." I never said > anything abut leaving FreeBSD, even though some developers like Alfred want > this, with his "piss off" comments. > If you knew alfred, you might understand :p (and I say this with the greatest of love for this friend of mine) > > > > It appears that I am not the only one who has seen this. Don't call this an > unsubstantiated comment... It's not just me. > Noone said you didn't have a problem, the attitude about something broken in -current and "fix it now" was the problem, -current is unstable, I personally have issues with running it on my development box right now, so I went back to PRE_SMPNG and will worry about it after everything is supposedly "fixed" , I suggest a similar solution for you. If you must have a working machine, 4-STABLE may be for you. I personally, do try and find out why I have issues like this, and try to provide debugging onfo if possible. Right now, I don;t have time due to my new position at VA, so have stopped tracking -CURRENT as closely. I did exactly what the handbook suggests. I don;t whine when my -CURRENT build is broken. > Guys/gals, stop telling me to just use 4.0 and fix the problem. How do I > "help myself" fix a problem with boot floppies?? Noone seems to have an > answer to this question, except for "piss off" by Alfred, use 4.0 by pretty > much everyone, and "forget your damn irq's" by Alfred. Maybe you are coming > in at the tail end and you did not re-read all the info that was said here. > Please go back and reread in an "unselective" manner. I know "I" didn't > break anything , as I do not alter /usr/src in any way. > > and thats the point, unless you are going to help debug this, and help code, you should not be running -CURRENT. You have missed the point, it has flown over your head, its now landing on the ground, you might want to go pick it up. Thanks for telling us about the problem, when one has time, after other issues are resolved, I'm sure it will be. Demanding that one if us fix it right now is not going to help your case. > This is definitly an election year... > > that obvious huh? -Trish __ Trish Lynch FreeBSD - The Power to Serve trish@bsdunix.net Rush Networking trish@rush.net VA Linux Systems trish@valinux.com O|S|D|N trish@osdn.com --- "So much style without substance. So much stuff without style. It's hard to recognize the real thing. It comes along once in a while. Like a rare and precious metal beneath a ton of rock It takes some time and trouble to separate from the stock You sometimes have to listen to a lot of useless talk." -Rush, Grand Designs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 18:44:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id ABEFF37B502; Mon, 2 Oct 2000 18:44:16 -0700 (PDT) Received: from localhost (trish@localhost) by superconductor.rush.net (8.9.3/8.9.3) with ESMTP id VAA31807; Mon, 2 Oct 2000 21:41:27 -0400 (EDT) Date: Mon, 2 Oct 2000 21:41:26 -0400 (EDT) From: Siobhan Patricia Lynch X-Sender: trish@superconductor.rush.net To: Jordan Hubbard Cc: Poul-Henning Kamp , Jeremy Lea , current@FreeBSD.ORG Subject: Re: #include in In-Reply-To: <58456.970506639@winston.osd.bsdi.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 Mon, 2 Oct 2000, Jordan Hubbard wrote: > > >This breaks several other ports (like BitchX). > > > > I think this breaks all IRC's which are cloned from the same origin :-) > > I'm still looking for the downside to this. ;-) > Well *some* of us still use ircII, however I've successfully compiled such under -current, but yes, I needed to do a little work :p -trish __ Trish Lynch FreeBSD - The Power to Serve trish@bsdunix.net Rush Networking trish@rush.net VA Linux Systems trish@valinux.com O|S|D|N trish@osdn.com --- "how long till my soul gets it right can any human being ever reach that kind of light i call on the resting soul of galileo king of night vision, king of insight" -Indigo Girls, Galileo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 19:46:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id AF80937B503 for ; Mon, 2 Oct 2000 19:46:08 -0700 (PDT) Received: (qmail 7282 invoked from network); 3 Oct 2000 02:46:04 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 3 Oct 2000 02:46:04 -0000 Date: Tue, 3 Oct 2000 13:45:59 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: #include in In-Reply-To: <18798.970481178@critter> 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, 2 Oct 2000, Poul-Henning Kamp wrote: > Trying to compile the ircII port, it crashes with: > > ===> Building for ircii-4.4X > cc -I. -I/usr/ports/irc/ircII/work/ircii-4.4X/include -O -pipe -DHAVE_CONFIG_H -c /usr/ports/irc/ircII/work/ircii-4.4X/source/alias.c > In file included from /usr/include/sys/queue.h:40, > from /usr/include/netinet6/in6.h:76, > from /usr/include/netinet/in.h:475, > from /usr/ports/irc/ircII/work/ircii-4.4X/include/irc.h:79, > from /usr/ports/irc/ircII/work/ircii-4.4X/source/alias.c:35: > /usr/ports/irc/ircII/work/ircii-4.4X/include/struct.h:51: syntax error before `_' > > This is because there is a file called "struct.h" in the ircII distribution. > > The addition of #include to looks a bit unsettling > to me: A sys/* file shouldn't reference a /usr/include file I think ? I corresponded with the author of this bug soon after it was committed, but didn't follow up. > Is the correct thing not to mv to , create > a which just pulls in and have > #include ? Of course not. Just expand the one macro that is used (strbase()) in the one place that it is used in . I think should have been removed when offsetof() became standard. It was only used in one place in /usr/src (lastcomm). Only the fldsiz() macro is used there. defines 2 other macros: fldoff() and strbase(). fldoff() is a bad version of offsetof() (one that takes a struct tag instead of a type, so it can't be used with typedefed structs). strbase() is now used in . It is easy to implement directly using offsetof(). Unfortunately, if it is implemented using offsetof(), then will depend on . Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 20:34:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id EC4C537B66C for ; Mon, 2 Oct 2000 20:34:54 -0700 (PDT) Received: (qmail 37957 invoked by uid 100); 3 Oct 2000 03:34:54 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14809.21470.203540.847030@guru.mired.org> Date: Mon, 2 Oct 2000 22:34:54 -0500 (CDT) To: current@freebsd.org Subject: Problem with buildkernel & modules... X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had a persistent (but minor) problem building -current kernels for a while. I was hoping someone had a fix before taking time to figure out exactly what was broken myself. Basically, the build goes: linking kernel text data bss dec hex filename 1869802 297944 2299408 4467154 4429d2 kernel cd /sharetmp/src/sys/modules && env MAKEOBJDIRPREFIX=/usr/obj/sharetmp/src/sys/GURU/modules KMODDIR=/usr/obj/sharetmp/src/i386/boot/kernel make obj all ===> 3dfx ===> accf_data ===> accf_http [long list of things deleted - but no other 3dfx mention] ===> splash/bmp ===> splash/pcx ===> streams ===> svr4 ===> vesa ===> wi ===> 3dfx make: don't know how to make @/i386/linux/linux_ioctl.h. Stop *** Error code 2 Stop in /sharetmp/src/sys/modules. *** Error code 1 Stop in /usr/obj/sharetmp/src/sys/GURU. *** Error code 1 Stop in /sharetmp/src. *** Error code 1 Stop in /sharetmp/src. su-2.04# Since I don't need 3dfx, I just remove it from src/sys/modules/Makefile, and things build fine. If someone has as to why 3dfx is trying to create this file, and how to fix it, I'd appreciate seeing a copy. Thanx, ; Mon, 2 Oct 2000 21:19:23 -0700 Content-Length: 1307 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 Date: Mon, 02 Oct 2000 21:19:27 -0700 (PDT) From: John Baldwin To: phk@FreeBSD.org Subject: bpf "fix" Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I stared at the bpf code some last week, and determined that the extra make_dev() was in bpf's open() method in the non-devfs case. As such, I have a rather simple patch. However, I don't like a driver having to be aware of devfs. Does anyone have any other (preferably cleaner) ways to fix this? http://www.FreeBSD.org/~jhb/patches/bpf.patch Index: net/bpf.c =================================================================== RCS file: /usr/cvs/src/sys/net/bpf.c,v retrieving revision 1.67 diff -u -r1.67 bpf.c --- net/bpf.c 2000/09/19 10:28:41 1.67 +++ net/bpf.c 2000/09/27 00:51:30 @@ -363,8 +363,10 @@ */ if (d) return (EBUSY); - make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, - "bpf%d", dev2unit(dev)); + /* XXX - ugly, we shouldn't have to know about devfs here */ + if (!devfs_present) + make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, + "bpf%d", dev2unit(dev)); MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); bzero(d, sizeof(*d)); dev->si_drv1 = d; -- 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 Oct 2 21:38:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from ego.mind.net (ego.mind.net [206.99.66.9]) by hub.freebsd.org (Postfix) with ESMTP id 7E41537B502; Mon, 2 Oct 2000 21:38:52 -0700 (PDT) Received: from takhus-home.ashlandfn.org (AFN-Dyn-6315110844.pc.ashlandfiber.net [63.151.108.44]) by ego.mind.net (8.9.3/8.9.3) with ESMTP id VAA08234; Mon, 2 Oct 2000 21:38:51 -0700 Received: from localhost (fleisher@localhost) by takhus-home.ashlandfn.org (8.11.0/8.11.0) with ESMTP id e934ceG34345; Mon, 2 Oct 2000 21:38:45 -0700 (PDT) (envelope-from takhus@takhus.mind.net) X-Authentication-Warning: takhus-home.ashlandfn.org: fleisher owned process doing -bs Date: Mon, 2 Oct 2000 21:38:40 -0700 (PDT) From: Tony Fleisher X-Sender: fleisher@takhus-home.ashlandfn.org To: John Baldwin Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bpf "fix" 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 submitted a PR on this a few weeks ago. See: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21391 for comments from phk. On Mon, 2 Oct 2000, John Baldwin wrote: > I stared at the bpf code some last week, and determined that the > extra make_dev() was in bpf's open() method in the non-devfs > case. As such, I have a rather simple patch. However, I don't > like a driver having to be aware of devfs. Does anyone have any > other (preferably cleaner) ways to fix this? > > http://www.FreeBSD.org/~jhb/patches/bpf.patch > > Index: net/bpf.c > =================================================================== > RCS file: /usr/cvs/src/sys/net/bpf.c,v > retrieving revision 1.67 > diff -u -r1.67 bpf.c > --- net/bpf.c 2000/09/19 10:28:41 1.67 > +++ net/bpf.c 2000/09/27 00:51:30 > @@ -363,8 +363,10 @@ > */ > if (d) > return (EBUSY); > - make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, > - "bpf%d", dev2unit(dev)); > + /* XXX - ugly, we shouldn't have to know about devfs here */ > + if (!devfs_present) > + make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, > + "bpf%d", dev2unit(dev)); > MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); > bzero(d, sizeof(*d)); > dev->si_drv1 = d; > > -- > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 2 21:54:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 1A4BA37B502; Mon, 2 Oct 2000 21:54:28 -0700 (PDT) Received: from laptop.baldwin.cx ([24.6.244.187]) by mail.rdc1.va.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001003045427.MAPV26082.mail.rdc1.va.home.com@laptop.baldwin.cx>; Mon, 2 Oct 2000 21:54:27 -0700 Content-Length: 2111 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: Mon, 02 Oct 2000 21:54:31 -0700 (PDT) From: John Baldwin To: Tony Fleisher Subject: Re: bpf "fix" Cc: current@FreeBSD.ORG, phk@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Oct-00 Tony Fleisher wrote: > I submitted a PR on this a few weeks ago. > > See: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21391 for comments > from phk. Hmm, well your patch would break in the non-DEVFS case. In the non-DEVFS case, open() still needs to call make_dev(), but I'm eager to see what phk's better solution is. :-P > On Mon, 2 Oct 2000, John Baldwin wrote: > >> I stared at the bpf code some last week, and determined that the >> extra make_dev() was in bpf's open() method in the non-devfs >> case. As such, I have a rather simple patch. However, I don't >> like a driver having to be aware of devfs. Does anyone have any >> other (preferably cleaner) ways to fix this? >> >> http://www.FreeBSD.org/~jhb/patches/bpf.patch >> >> Index: net/bpf.c >> =================================================================== >> RCS file: /usr/cvs/src/sys/net/bpf.c,v >> retrieving revision 1.67 >> diff -u -r1.67 bpf.c >> --- net/bpf.c 2000/09/19 10:28:41 1.67 >> +++ net/bpf.c 2000/09/27 00:51:30 >> @@ -363,8 +363,10 @@ >> */ >> if (d) >> return (EBUSY); >> - make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, >> - "bpf%d", dev2unit(dev)); >> + /* XXX - ugly, we shouldn't have to know about devfs here */ >> + if (!devfs_present) >> + make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, >> + "bpf%d", dev2unit(dev)); >> MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); >> bzero(d, sizeof(*d)); >> dev->si_drv1 = d; >> >> -- >> >> 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 >> > -- 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 Oct 2 22: 7:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from ego.mind.net (ego.mind.net [206.99.66.9]) by hub.freebsd.org (Postfix) with ESMTP id A3E7337B503; Mon, 2 Oct 2000 22:07:50 -0700 (PDT) Received: from takhus-home.ashlandfn.org (AFN-Dyn-6315110844.pc.ashlandfiber.net [63.151.108.44]) by ego.mind.net (8.9.3/8.9.3) with ESMTP id WAA15481; Mon, 2 Oct 2000 22:07:49 -0700 Received: from localhost (fleisher@localhost) by takhus-home.ashlandfn.org (8.11.0/8.11.0) with ESMTP id e9357g834466; Mon, 2 Oct 2000 22:07:42 -0700 (PDT) (envelope-from takhus@takhus.mind.net) X-Authentication-Warning: takhus-home.ashlandfn.org: fleisher owned process doing -bs Date: Mon, 2 Oct 2000 22:07:42 -0700 (PDT) From: Tony Fleisher X-Sender: fleisher@takhus-home.ashlandfn.org To: John Baldwin Cc: phk@FreeBSD.org, current@FreeBSD.org Subject: Re: bpf "fix" 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 Yeah, I didn't figure that my patch was correct. I too am waiting to see what phk comes up with. :) He did commit a new flag to sys/sys/conf.h on Sep. 19 "Introduce experimental SI_CHEAPCLONE flag set it on cloned bpfs." but I have not seen anything in the source come up that uses it... yet.: conf.h:59: #define SI_CHEAPCLONE 0x0008 /* can be removed_dev'ed when vnode reclaims */ Regards, TOny. On Mon, 2 Oct 2000, John Baldwin wrote: > > On 03-Oct-00 Tony Fleisher wrote: > > I submitted a PR on this a few weeks ago. > > > > See: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21391 for comments > > from phk. > > Hmm, well your patch would break in the non-DEVFS case. In the non-DEVFS > case, open() still needs to call make_dev(), but I'm eager to see what phk's > better solution is. :-P > > > On Mon, 2 Oct 2000, John Baldwin wrote: > > > >> I stared at the bpf code some last week, and determined that the > >> extra make_dev() was in bpf's open() method in the non-devfs > >> case. As such, I have a rather simple patch. However, I don't > >> like a driver having to be aware of devfs. Does anyone have any > >> other (preferably cleaner) ways to fix this? > >> > >> http://www.FreeBSD.org/~jhb/patches/bpf.patch > >> > >> Index: net/bpf.c > >> =================================================================== > >> RCS file: /usr/cvs/src/sys/net/bpf.c,v > >> retrieving revision 1.67 > >> diff -u -r1.67 bpf.c > >> --- net/bpf.c 2000/09/19 10:28:41 1.67 > >> +++ net/bpf.c 2000/09/27 00:51:30 > >> @@ -363,8 +363,10 @@ > >> */ > >> if (d) > >> return (EBUSY); > >> - make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, > >> - "bpf%d", dev2unit(dev)); > >> + /* XXX - ugly, we shouldn't have to know about devfs here */ > >> + if (!devfs_present) > >> + make_dev(&bpf_cdevsw, minor(dev), UID_ROOT, GID_WHEEL, 0600, > >> + "bpf%d", dev2unit(dev)); > >> MALLOC(d, struct bpf_d *, sizeof(*d), M_BPF, M_WAITOK); > >> bzero(d, sizeof(*d)); > >> dev->si_drv1 = d; > >> > >> -- > >> > >> 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 > >> > > > > -- > > 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 Oct 2 23: 6:17 2000 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 66DBB37B502; Mon, 2 Oct 2000 23:06:14 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e9366CN45964; Tue, 3 Oct 2000 08:06:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: current@FreeBSD.org Subject: Re: bpf "fix" In-Reply-To: Your message of "Mon, 02 Oct 2000 21:19:27 PDT." Date: Tue, 03 Oct 2000 08:06:12 +0200 Message-ID: <45962.970553172@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: >I stared at the bpf code some last week, and determined that the >extra make_dev() was in bpf's open() method in the non-devfs >case. As such, I have a rather simple patch. However, I don't >like a driver having to be aware of devfs. Does anyone have any >other (preferably cleaner) ways to fix this? Yes, I'm working on a patch for all pseudo devices so that they go away (entirely) when no longer used. That's the problem with cloning devices: you need a way to get rid of them again or you have a DoS on your hands. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Oct 3 1: 8:17 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 558) id 9D03137B502; Tue, 3 Oct 2000 01:08:16 -0700 (PDT) To: current@FreeBSD.ORG Subject: Re: #include in Message-Id: <20001003080816.9D03137B502@hub.freebsd.org> Date: Tue, 3 Oct 2000 01:08:16 -0700 (PDT) From: hsu@FreeBSD.ORG (Jeffrey Hsu) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think should have been removed when offsetof() became > standard. At last count, offsetof() is defined in 11 different places in the kernel: alpha/alpha/machdep.c, line 234 dev/sym/sym_hipd.c, line 347 i386/i386/machdep.c, line 246 kern/sysv_sem.c, line 110 kern/uipc_usrreq.c, line 548 netinet/ip_compat.h, line 56 netinet/ip_fil.h, line 254 netinet6/icmp6.c, line 761 netinet6/in6_proto.c, line 126 netinet6/raw_ip6.c, line 348 pc98/i386/machdep.c, line 254 If we unify it in one header file, I'd be happy to use that for STAILQ_LAST(). > strbase() is now used in . It is > easy to implement directly using offsetof(). Unfortunately, if it is > implemented using offsetof(), then will depend on > . So, what's the correct solution? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 1:36:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id BF6E037B66D; Tue, 3 Oct 2000 01:36:15 -0700 (PDT) Received: from stinky.palnet.com (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id KAA09439; Tue, 3 Oct 2000 10:41:03 +0200 (IST) Message-Id: <5.0.0.23.0.20001003100820.00ad9470@192.116.19.220> X-Sender: mustafa@192.116.19.220 X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.23 (Beta) Date: Tue, 03 Oct 2000 10:17:51 +0200 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org From: Mustafa Deeb Subject: Internet Prepaid Card Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I'm working on building a system that will handle Internet Prepaid Cards where the user would connect for a certain amount of time and then disconnect ofcourse this is not implemented in Radius. after some digging, I was able to control it through Session-Timeout Attribute in Radius and some scripts that will decrement the value until it reaches 1, but still this means I'll have to put an entry for each card in the users file along with another entry in master.passwd file, I don't if radiusd can handle that amount of entries, and anyways, if my password file is more than 10k lines, that's not good. the other approach that I'm looking into is through database, radiusd is patched to do auth and acct from database, but not read configuration I wonder if someone did this before, make radiusd read its configuration from a database my aim here is to make radius read the Session-Timeout from a database or use Oracle Radius Adapter, on and oracle database, but I couldn't find Session-Timeout in it too. did somebody did this before? Best Regards Mustafa N. Deeb Palnet Communications Ltd. Technical Director To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 6:16:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 5FD5437B502 for ; Tue, 3 Oct 2000 06:16:25 -0700 (PDT) Received: (qmail 18081 invoked by uid 0); 3 Oct 2000 13:16:23 -0000 Received: from p3ee20a9a.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.154) by mail.gmx.net with SMTP; 3 Oct 2000 13:16:23 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id KAA02693 for current@freebsd.org; Tue, 3 Oct 2000 10:13:54 +0200 Date: Tue, 3 Oct 2000 10:13:54 +0200 From: Gerhard Sittig To: current@freebsd.org Subject: Re: mtree verification output format Message-ID: <20001003101354.B31338@speedy.gsinet> Mail-Followup-To: current@freebsd.org References: <43778.970523608@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <43778.970523608@critter>; from phk@freebsd.org on Mon, Oct 02, 2000 at 11:53:28PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 02, 2000 at 23:53 +0200, Poul-Henning Kamp wrote: > > I would like to change the outputformat of mtree(8) to be more > systematic and machine-readable. > > [ ... ] > > Before: > ------------ > rc: size (13134, 13135) > cksum (2005920215, 873112433) > ttys: cksum (2486739860, 2798556681) > extra: bla > malloc.conf: > permissions (0755, 0777) > missing: ./objformat > ------------ > > After: > ------------ > rc: > size (13134, 13135) > cksum (2005920215, 873112433) > ttys: > cksum (2486739860, 2798556681) > bla: > extra > malloc.conf: > permissions (0755, 0777) > ./objformat: > missing > ------------ I miss the continuation mark (backslashes at line ends). In case someone wrote parsers / formatters they should still be there. This way you don't change grammar but merely layout for better readability by humans. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 6:21:39 2000 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 6448937B503 for ; Tue, 3 Oct 2000 06:21:35 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e93DLWN47935; Tue, 3 Oct 2000 15:21:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Gerhard Sittig Cc: current@FreeBSD.ORG Subject: Re: mtree verification output format In-Reply-To: Your message of "Tue, 03 Oct 2000 10:13:54 +0200." <20001003101354.B31338@speedy.gsinet> Date: Tue, 03 Oct 2000 15:21:32 +0200 Message-ID: <47933.970579292@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001003101354.B31338@speedy.gsinet>, Gerhard Sittig writes: >I miss the continuation mark (backslashes at line ends). In case >someone wrote parsers / formatters they should still be there. >This way you don't change grammar but merely layout for better >readability by humans. I don't change the md5-grammar, only the output when it verifies a filesystem against a file (containing a spec in the usual grammar). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Oct 3 7:49: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B59B837B502 for ; Tue, 3 Oct 2000 07:49:02 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA79984; Tue, 3 Oct 2000 16:55:12 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010031455.QAA79984@freebsd.dk> Subject: Re: ATA disk support broken for PC-CARD in 5.0-CURRENT?? In-Reply-To: <200010021936.NAA13954@harmony.village.org> from Warner Losh at "Oct 2, 2000 01:36:49 pm" To: imp@village.org (Warner Losh) Date: Tue, 3 Oct 2000 16:55:12 +0200 (CEST) Cc: chain@110.net (Chain Lee), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Warner Losh wrote: > In message <39D80B01.90BFADFF@110.net> Chain Lee writes: > : PC-CARD IDE hard disk and compact flash card support is broken > : in recent 5.0-CURRENT. Does anyone have an idea what the problem is? > : > : Please copy reply to me. I don't subscribe to the 'current' mailing list. > > They are? Hmmm, I'll have to look at this... This should have been fixed... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 10:37:34 2000 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 3CC9737B503 for ; Tue, 3 Oct 2000 10:37:29 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id TAA64571; Tue, 3 Oct 2000 19:32:05 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id e93GpPN47297; Tue, 3 Oct 2000 18:51:27 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Tue, 3 Oct 2000 18:51:24 +0200 (CEST) From: Leif Neland To: Seigo Tanimura Cc: n@nectar.com, current@FreeBSD.ORG Subject: Updating ports In-Reply-To: <14805.63360.137164.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.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 Sat, 30 Sep 2000, Seigo Tanimura wrote: > On Thu, 28 Sep 2000 11:55:55 -0500, > "Jacques A. Vidrine" said: > > >> It would also be helpful for us to (semi-)automatically update old > >> binaries installed by ports. (I have been trying this for a couple of > >> days) > > Jacques> Personally I don't want sysinstall or make world to touch my ports. > Jacques> But a tool to do this would be great. > > Completely automatic update of installed ports is acutally difficult > because we cannot get to know the language or required toolkit from > the name of a binary. (eg emulator/wine and japanese/wine, timidity++-xaw > and timidity++-tcltk) We can still detect and enumerate the ports that > possibly installed old binaries, and decide which of the ports listed > up to update. > Isn't enough information in /var/db/pkg? Perhaps a level of redirection is needed in the dependencies? (sp?) Something like the Debian way? Instead of foo-1.23 being required by bar-3.34, bar should just require a foo >1.20. Or even bar requires an xyzzy. xyzzy is supplied by fee xyzzy is supplied by fie Then the user has the option of installing fee or fie. Leif. (Who descrambled the message-file for Collossal adventure on his zx81 converted to cp/m many years ago...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 11:57:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [64.20.73.233]) by hub.freebsd.org (Postfix) with ESMTP id 5009937B66C for ; Tue, 3 Oct 2000 11:57:07 -0700 (PDT) Received: from boomer.forrie.com (dhcp-north-71-168.navipath.net [64.20.71.168]) by forrie.net with id e93Iv6v24220 for ; Tue, 3 Oct 2000 14:57:06 -0400 (EDT) Message-Id: <5.0.0.25.2.20001003144925.02136170@64.20.73.233> X-Sender: forrie@64.20.73.233 X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Tue, 03 Oct 2000 14:50:35 -0400 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Options for IPFilter Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since IPFilter is integrated as an option into the OS, can we get a better config in the rc.* scripts so that we can define which filter to use (ipfw or ipfilter) and appropriate options. Thx/_F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 12: 0:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 91CA237B66C for ; Tue, 3 Oct 2000 12:00:10 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 906069B05; Tue, 3 Oct 2000 15:00:09 -0400 (EDT) Date: Tue, 3 Oct 2000 15:00:09 -0400 From: Chris Faulhaber To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Options for IPFilter Message-ID: <20001003150009.A51698@pawn.primelocation.net> Mail-Followup-To: Chris Faulhaber , Forrest Aldrich , freebsd-current@freebsd.org References: <5.0.0.25.2.20001003144925.02136170@64.20.73.233> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.2.20001003144925.02136170@64.20.73.233>; from forrie@forrie.com on Tue, Oct 03, 2000 at 02:50:35PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 03, 2000 at 02:50:35PM -0400, Forrest Aldrich wrote: > Since IPFilter is integrated as an option into the OS, can we get a better > config in the rc.* scripts so that we can define which filter to use (ipfw > or ipfilter) and appropriate options. > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20202 -- ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Oct 3 12: 5: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from valcho.net (valcho.net [208.10.211.61]) by hub.freebsd.org (Postfix) with SMTP id 8951237B503 for ; Tue, 3 Oct 2000 12:05:00 -0700 (PDT) Received: (qmail 588 invoked by uid 1000); 3 Oct 2000 19:04:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Oct 2000 19:04:53 -0000 Date: Tue, 3 Oct 2000 15:04:53 -0400 (EDT) From: Valentin Chopov To: freebsd-current@freebsd.org Subject: ATA DMA support is 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 After last changes ata DMA support is not workind and atapicd is not recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) Val ------------ Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #5: Tue Oct 3 14:33:01 EDT 2000 root@valsei.valcho.net:/usr/src/sys/compile/VALCHO Timecounter "i8254" frequency 1193176 Hz CPU: Pentium III/Pentium III Xeon/Celeron (647.60-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 134086656 (130944K bytes) avail memory = 123797504 (120896K bytes) Preloaded elf kernel "kernel" at 0xc065d000. Pentium Pro MTRR support enabled VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc05d2182 (1000022) VESA: S3 Incorporated. M7 BIOS md0: Malloc disk apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 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 irq 11 isab0: at device 5.0 on pci0 isa0: on isab0 atapci0: port 0xfff0-0xffff at device 5.1 on pci0 atapci0: Busmastering DMA enabled uhci0: port 0xff80-0xff9f irq 11 at device 5.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 5.3 pci0: (vendor=0x11c1, dev=0x0441) at 7.0 irq 3 pci0: (vendor=0x1179, dev=0x0d01) at 9.0 irq 11 pci0: at 11.0 pci0: at 11.1 pcm0: port 0xfefc-0xfeff,0xff00-0xff3f mem 0xefff8000-0xefffffff irq 11 at device 12.0 on pci0 acpi0: on motherboard fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pmtimer0 on isa0 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 IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to accept, logging disabled IPv6 packet filtering initialized, default to accept, logging disabled IPsec: Initialized Security Association Processing. IP Filter: v3.4.9 initialized. Default = pass all, Logging = disabled ata1-master: identify retries exceeded ad0: 11513MB [23392/16/63] at ata0-master BIOSPIO Mounting root from ufs:/dev/ad0s3a pccard: card inserted, slot 1 ep0: <3Com 3C556> at port 0x240-0x25f irq 5 slot 1 on pccard1 ep0: Ethernet address 00:00:86:52:40:af To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 12:38:32 2000 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 C1FE437B677 for ; Tue, 3 Oct 2000 12:38:24 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.1/8.11.0) id e93JcOJ03739; Tue, 3 Oct 2000 14:38:24 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: freebsd-current@freebsd.org Subject: page fault while in kernel mode Keywords: fault,pointer,page From: Michael Harnois Date: 03 Oct 2000 14:38:24 -0500 Message-ID: <86d7hhlnpr.fsf@mharnois.workgroup.net> Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The past three days or so with -current my system has been locking up solid under load. Today I was fortunate enough to have in happen when in console mode so that I could see the problem: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc029e6cb stack pointer = 0x10:0xcefdfe18 frame pointer = 0x10:0xccfdfe20 code segment = base 0x0, limit 0xffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2355 (procmail) trap number = 12 panic: page fault acpi0: acpi_io_pml_enable(1) = (0) acpi0: acpi_io_gpe0_enable(1) = (0) syncing disks... -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 13:19:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4396B37B66D for ; Tue, 3 Oct 2000 13:19:22 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA62550; Tue, 3 Oct 2000 22:25:34 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010032025.WAA62550@freebsd.dk> Subject: Re: ATA DMA support is broken In-Reply-To: from Valentin Chopov at "Oct 3, 2000 03:04:53 pm" To: valentin@valcho.net (Valentin Chopov) Date: Tue, 3 Oct 2000 22:25:34 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Valentin Chopov wrote: > After last changes ata DMA support is not workind and atapicd is not > recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) Are you sure this is with the latest changes ? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 13:23:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id 3CB2C37B66C for ; Tue, 3 Oct 2000 13:23:12 -0700 (PDT) Received: (qmail 30888 invoked by uid 666); 3 Oct 2000 20:23:04 -0000 Received: from reggae-34-48.nv.iinet.net.au (HELO elischer.org) (203.59.167.48) by mail.m.iinet.net.au with SMTP; 3 Oct 2000 20:23:04 -0000 Message-ID: <39DA400C.F3251EB8@elischer.org> Date: Tue, 03 Oct 2000 13:22:36 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Options for IPFilter References: <5.0.0.25.2.20001003144925.02136170@64.20.73.233> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forrest Aldrich wrote: > > Since IPFilter is integrated as an option into the OS, can we get a better > config in the rc.* scripts so that we can define which filter to use (ipfw > or ipfilter) and appropriate options. > > Thx/_F > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Well, since you know how to use ipfiler, I guess that makes you the ideal pereson to submit the patches,, right? :-) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 13:34:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from valcho.net (valcho.net [208.10.211.61]) by hub.freebsd.org (Postfix) with SMTP id 88E2637B66D for ; Tue, 3 Oct 2000 13:34:44 -0700 (PDT) Received: (qmail 1011 invoked by uid 1000); 3 Oct 2000 20:34:37 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Oct 2000 20:34:37 -0000 Date: Tue, 3 Oct 2000 16:34:37 -0400 (EDT) From: Valentin Chopov To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA DMA support is broken In-Reply-To: <200010032025.WAA62550@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren, yes, I didn't make world today, but cvsup is after your last commit. Before that in my dmesg it was : ad0: 11513MB [23392/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using UDMA33 Thanks, Val =20 On Tue, 3 Oct 2000, Soren Schmidt wrote: > It seems Valentin Chopov wrote: > > After last changes ata DMA support is not workind and atapicd is not > > recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) >=20 > Are you sure this is with the latest changes ? >=20 > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 13:38:42 2000 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 8497A37B502 for ; Tue, 3 Oct 2000 13:38:40 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.1/8.11.0) id e93Kcc219604; Tue, 3 Oct 2000 15:38:38 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: Valentin Chopov Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA DMA support is broken References: From: Michael Harnois Date: 03 Oct 2000 15:38:37 -0500 In-Reply-To: Message-ID: <86pulhoe2a.fsf@mharnois.workgroup.net> Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) 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, 3 Oct 2000 15:04:53 -0400 (EDT), Valentin Chopov said: > After last changes ata DMA support is not workind and atapicd is > not recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) Same problem here on an Intel 815 chipset. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org No man knows how bad he is till he has tried very hard to be good. -- C.S. Lewis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 14:34:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from caffeine.gerp.org (caffeine.gerp.org [216.80.26.45]) by hub.freebsd.org (Postfix) with SMTP id 0FC2037B66D for ; Tue, 3 Oct 2000 14:34:48 -0700 (PDT) Received: (qmail 22058 invoked by uid 100); 3 Oct 2000 21:19:56 -0000 Date: Tue, 3 Oct 2000 16:19:55 -0500 From: "Kevin M. Dulzo" To: Soren Schmidt Cc: freebsd-current@freebsd.org Subject: Re: ATA DMA support is broken Message-ID: <20001003161955.A2852@caffeine.gerp.org> Reply-To: kdulzo@gerp.org References: <200010032025.WAA62550@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <200010032025.WAA62550@freebsd.dk>; from sos@freebsd.dk on Tue, Oct 03, 2000 at 10:25:34PM +0200 X-Operating-System: OpenBSD caffeine 2.7 CAFFEINE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 03, 2000 at 10:25:34PM +0200, Soren Schmidt wrote: > Are you sure this is with the latest changes ? > > -Søren > > I have a similar issue since approximately 4 hours ago. I also do not use the GENERIC.hints and made some attempts to tune them... although NOTES would lead me to believe I do not, I now need the hints for both ata.0 and ata.1. This is a Dell Inspiron (7500) laptop. Relevant dmesg: atapci0: port 0x1050-0x105f at device 7.1 on pci0 atapci0: Busmastering DMA enabled ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1-master: identify retries exceeded ad0: 11513MB [23392/16/63] at ata0-master BIOSPIO N.B. My normally recognized DVD drive is not recognized. It is the master on the secondary controller. -- :Kevin M. Dulzo: eyes betray a soul and bear its thinking beyond words they say so many things to me --vnvnation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 14:45:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from caffeine.gerp.org (caffeine.gerp.org [216.80.26.45]) by hub.freebsd.org (Postfix) with SMTP id CE58037B502 for ; Tue, 3 Oct 2000 14:45:23 -0700 (PDT) Received: (qmail 27330 invoked by uid 100); 3 Oct 2000 21:30:32 -0000 Date: Tue, 3 Oct 2000 16:30:31 -0500 From: "Kevin M. Dulzo" To: freebsd-current@freebsd.org Subject: Apparant lockups/process wedging. Message-ID: <20001003163031.B2852@caffeine.gerp.org> Reply-To: kdulzo@gerp.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: OpenBSD caffeine 2.7 CAFFEINE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had several lockups since I gave -current a whirl. I finally have a crash dump so hopefully can help isolate the issue. These seems to be repeatable easily by rebooting without powering off (on my one machine). sh (pid 6) has locked, other startup proceeses spawned from /etc/rc (named for example) have locked. By locking, they just spin off into lala land and chew on CPU time, as well they become uninterruptable and prevent the machine from entering multi-user mode. I can provide dmesg/kernel config/hints/dump to anyone but I felt too much to dump down the list. The 'where' output of gdb -k only seems to show my manual break and 'panic' calls. -- :Kevin M. Dulzo: eyes betray a soul and bear its thinking beyond words they say so many things to me --vnvnation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 18: 1:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemicals.tacorp.com (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id 88FBF37B502 for ; Tue, 3 Oct 2000 18:01:28 -0700 (PDT) Received: (from morganw@localhost) by volatile.chemicals.tacorp.com (8.11.1/8.11.1) id e9411Qc55079; Tue, 3 Oct 2000 21:01:26 -0400 (EDT) (envelope-from morganw) Date: Tue, 3 Oct 2000 21:01:26 -0400 (EDT) From: Wesley Morgan To: current@freebsd.org Cc: Soren Schmidt , "Kevin M. Dulzo" Subject: Re: ATA DMA support is 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 I'm seeing the same problem on my Tecra 8000: atapci0: port 0xfe60-0xfe6f at device 5.1 on pci0 atapci0: Busmastering DMA enabled ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ata1-master: identify retries exceeded ad0: 6194MB [13424/15/63] at ata0-master BIOSPIO Before adding the hints to /boot/device.hints, only the atapci0 was detected. Works fine with the hints though. -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ wesleymorgan@home.com _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 18:32: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 190A037B66C; Tue, 3 Oct 2000 18:32:00 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13gdKG-000JXE-00; Wed, 04 Oct 2000 03:26:28 +0200 Date: Wed, 4 Oct 2000 03:26:28 +0200 From: Neil Blakey-Milner To: Leif Neland Cc: Seigo Tanimura , n@nectar.com, ports@FreeBSD.org Subject: Re: Updating ports Message-ID: <20001004032628.A74975@mithrandr.moria.org> References: <14805.63360.137164.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> 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 Tue, Oct 03, 2000 at 06:51:24PM +0200 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -> -ports ] On Tue 2000-10-03 (18:51), Leif Neland wrote: > > Jacques> Personally I don't want sysinstall or make world to touch my ports. > > Jacques> But a tool to do this would be great. > > > > Completely automatic update of installed ports is acutally difficult > > because we cannot get to know the language or required toolkit from > > the name of a binary. (eg emulator/wine and japanese/wine, timidity++-xaw > > and timidity++-tcltk) We can still detect and enumerate the ports that > > possibly installed old binaries, and decide which of the ports listed > > up to update. > > > Isn't enough information in /var/db/pkg? > > Perhaps a level of redirection is needed in the dependencies? (sp?) > > Something like the Debian way? > Instead of foo-1.23 being required by bar-3.34, bar should just require a > foo >1.20. > > Or even bar requires an xyzzy. > xyzzy is supplied by fee > xyzzy is supplied by fie > Then the user has the option of installing fee or fie. This really is an issue for ports@, not current@. We've had a long discussion on this, and not much has come out of it yet, but I imagine that it just needs some time to simmer at a low heat before some deep-frying. (: So far, we've identified (or, rather, some people have suggested) that we need relative versioning and virtual packages, so we've covered your suggestions. My "accurate" versioning stuff has come in (epoch, revision, just like Debian), and it'll take some time more for someone to supply and review the code for the others. I believe Satoshi is reviewing a port of the NetBSD relative versioning stuff at the moment. Virtual packages are an interesting thing, I don't believe there's code available for it, but it should be easy enough. Luckily, it seems things are progressing, and that the creative juices are flowing again. Will has a talk which includes stuff based loosely on some suggestions of mine from way-back, which he'll give at BSDcon (hopefully I can make it), and that will probably be a good brain-storming starter. So, things are looking up. I can't actually remember why I replied to this, other than to move it over to ports. My mind is a'wandering. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 19:16: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id CFE4D37B502 for ; Tue, 3 Oct 2000 19:15:58 -0700 (PDT) Received: (qmail 26955 invoked by uid 0); 4 Oct 2000 02:15:57 -0000 Received: from p3ee2160b.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.11) by mail.gmx.net with SMTP; 4 Oct 2000 02:15:57 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id WAA04423 for current@FreeBSD.ORG; Tue, 3 Oct 2000 22:09:02 +0200 Date: Tue, 3 Oct 2000 22:09:02 +0200 From: Gerhard Sittig To: current@FreeBSD.ORG Subject: Re: mtree verification output format Message-ID: <20001003220902.E31338@speedy.gsinet> Mail-Followup-To: current@FreeBSD.ORG References: <20001003101354.B31338@speedy.gsinet> <47933.970579292@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <47933.970579292@critter>; from phk@critter.freebsd.dk on Tue, Oct 03, 2000 at 03:21:32PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 03, 2000 at 15:21 +0200, Poul-Henning Kamp wrote: > In message <20001003101354.B31338@speedy.gsinet>, Gerhard Sittig writes: > > >I miss the continuation mark (backslashes at line ends). [...] > > I don't change the md5-grammar, only the output when it verifies > a filesystem against a file (containing a spec in the usual grammar). Oops! I must have dreamed of something else when I replied. I guess I should have had a closer look at a FreeBSD machine and not just read the mail on another one ... Feel free to direct my previous concerns to /dev/null (not that they had much of weight before, anyway). :> virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 19:33:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id E005137B502; Tue, 3 Oct 2000 19:33:26 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e942XNr71742; Wed, 4 Oct 2000 11:33:24 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: msmith@freebsd.org Cc: iwasaki@jp.FreeBSD.org, haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI megapatch In-Reply-To: <200010022255.e92Mtgh03620@mass.osd.bsdi.com> References: <20001002185030U.iwasaki@jp.FreeBSD.org> <200010022255.e92Mtgh03620@mass.osd.bsdi.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001004113250E.iwasaki@jp.FreeBSD.org> Date: Wed, 04 Oct 2000 11:32:50 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 24 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Great! This is really great!! I didn't think we can have ACPICA > > kernel so earlier. > > Well, let's see if it works right first. 8) I hear from Intel that they > plan to release a new code revision today, so I will be updating when > they do. I also hear that Andrew Grover (the chap at Intel that's been > answering my mails) has just joined acpi-jp (G'day!). Welcome to acpi-jp ML, Andrew and Mike! I've just tried acpica-bsd-20001003, this is greater than before :-) It seems GPE events are handled correctly on my PORTEGE. BTW, System sleep transition and PowerResource manipulation are not implemented yet where we have done already. # I'm not sure we did in right way though :-) How is the status on them? May I try to implement them porting our old code? > > OK, I have a patch for AcpiOsSleep and AcpiOsSleepUsec which I was > > involed in recently. > > Thanks, I've incorporated it. Ack, thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 20:49:10 2000 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 EFC2D37B503 for ; Tue, 3 Oct 2000 20:49:08 -0700 (PDT) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.11.0/8.11.0) id e943n8J00811; Tue, 3 Oct 2000 22:49:08 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: freebsd-current@FreeBSD.ORG Subject: Re: page fault while in kernel mode References: From: Michael Harnois Date: 03 Oct 2000 22:49:08 -0500 In-Reply-To: Message-ID: <86r95xmfkb.fsf@mharnois.workgroup.net> Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Nike) 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, 03 Oct 2000 19:33:01 -0400 (EDT), Bosko Milekic said: > Also, is there anything particular that you > notice that is happening in parallel to this? Anything special > you're doing? I can tell you now that rolling back to PRE_SMPNG makes the problem go away. So it's something that's happened to -current since then. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org Everything I did in my life that was worthwhile, I caught hell for. -- Earl Warren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Oct 3 23:12:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from master.telia.net (master.telia.net [194.237.170.70]) by hub.freebsd.org (Postfix) with ESMTP id 61BBE37B66E for ; Tue, 3 Oct 2000 23:12:27 -0700 (PDT) Received: from localhost (elite@localhost) by master.telia.net (8.9.3/8.9.1) with ESMTP id IAA47139; Wed, 4 Oct 2000 08:11:39 +0200 (CEST) (envelope-from khaled@w-arts.com) X-Authentication-Warning: master.telia.net: elite owned process doing -bs Date: Wed, 4 Oct 2000 08:11:39 +0200 (CEST) From: Khaled Daham X-Sender: elite@master.telia.net To: Valentin Chopov Cc: freebsd-current@freebsd.org Subject: Re: ATA DMA support is broken 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 Tue, 3 Oct 2000, Valentin Chopov wrote: > FreeBSD 5.0-CURRENT #5: Tue Oct 3 14:33:01 EDT 2000 > root@valsei.valcho.net:/usr/src/sys/compile/VALCHO > Timecounter "i8254" frequency 1193176 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (647.60-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x681 Stepping = 1 > Features=0x383f9ff > real memory = 134086656 (130944K bytes) > avail memory = 123797504 (120896K bytes) Atleast you get the right CPU speed :) on 4.1.1 I get ( on a Tecra 8000 ) Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (193.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 268369920 (262080K bytes) avail memory = 258650112 (252588K bytes) But this is not related to current. /Khaled Daham, w.arts Mail: khaled@w-arts.com Cell: +46-70-6785492, +966-54491462 FreeBSD: 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 Oct 4 1:30:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B974937B502 for ; Wed, 4 Oct 2000 01:30:49 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA33310; Wed, 4 Oct 2000 10:37:04 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010040837.KAA33310@freebsd.dk> Subject: Re: ATA DMA support is broken In-Reply-To: from Wesley Morgan at "Oct 3, 2000 09:01:26 pm" To: morganw@chemicals.tacorp.com (Wesley Morgan) Date: Wed, 4 Oct 2000 10:37:04 +0200 (CEST) Cc: current@freebsd.org, kdulzo@caffeine.gerp.org (Kevin M. Dulzo) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Wesley Morgan wrote: > I'm seeing the same problem on my Tecra 8000: > atapci0: port 0xfe60-0xfe6f at device 5.1 on pci0 > atapci0: Busmastering DMA enabled > ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 > ata1 at port 0x170-0x177,0x376 irq 15 on isa0 > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed > ata1-master: identify retries exceeded > ad0: 6194MB [13424/15/63] at ata0-master BIOSPIO > > Before adding the hints to /boot/device.hints, only the atapci0 was > detected. Works fine with the hints though. This should be fixed now... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 4 5: 2:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id E678337B503 for ; Wed, 4 Oct 2000 05:02:54 -0700 (PDT) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id E1B1A10E04 for ; Wed, 4 Oct 2000 14:02:53 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id 4022A9B387; Wed, 4 Oct 2000 14:02:50 +0200 (CEST) Date: Wed, 4 Oct 2000 14:02:50 +0200 From: Alain Thivillon To: current@freebsd.org Subject: -CURRENT clock deviation Message-ID: <20001004140250.H5060@yoko.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed that -CURRENT (build last week) is subject to a very high clock deviation: Oct 4 12:14:08 yoko ntpd[674]: time reset 1.367273 s Oct 4 12:14:08 yoko ntpd[674]: synchronisation lost Oct 4 12:32:26 yoko ntpd[674]: synchronisation lost Oct 4 12:41:06 yoko ntpd[674]: time reset 4.372092 s Oct 4 12:41:06 yoko ntpd[674]: synchronisation lost Oct 4 13:01:31 yoko ntpd[674]: time reset 1.410883 s Oct 4 13:01:31 yoko ntpd[674]: synchronisation lost Oct 4 13:23:06 yoko ntpd[674]: time reset 3.039882 s Oct 4 13:23:06 yoko ntpd[674]: synchronisation lost My ntp server is not the cause, other clients have no problems. Deviation seems to be around 5 seconds / 30 min. I run -CURRENT on a laptop, it seems that last commit in idle loop (the one replacing loop by HLT and lowering temperature) broke the clock. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 4 9:19:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from comand.net (comand.net [209.95.105.58]) by hub.freebsd.org (Postfix) with ESMTP id A316A37B66D for ; Wed, 4 Oct 2000 09:19:56 -0700 (PDT) Received: from dell (adsl-151-203-25-129.bostma.adsl.bellatlantic.net [151.203.25.129]) by comand.net (8.9.3/8.9.3) with SMTP id JAA05252 for ; Wed, 4 Oct 2000 09:19:50 -0700 (PDT) From: "Marios Andreou" To: Subject: subscribe Date: Wed, 4 Oct 2000 12:19:48 -0400 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: 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 Oct 4 10:42:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7226237B503; Wed, 4 Oct 2000 10:42:14 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e94HgBX91791; Wed, 4 Oct 2000 10:42:11 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Cc: bde@freebsd.org Subject: ext2fs support for writing - what's the verdict? Date: Wed, 04 Oct 2000 10:42:11 -0700 Message-ID: <91787.970681331@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As most people probably know, you can't write on ext2fs filesystems with any of the "newer" Linux distributions, like Red Hat 6.2 on up. The filesystem mount refuses r/w permission with the message "WARNING: R/W mount of #
denied due to unsupported optional features" Do we plan to do anything about that? Heck, I'm not even sure who maintains ext2fs these days - bde maybe? [hopeful facial expression] :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 4 10:51:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from krycek.zoominternet.net (krycek.zoominternet.net [63.67.120.9]) by hub.freebsd.org (Postfix) with SMTP id B471737B502 for ; Wed, 4 Oct 2000 10:51:47 -0700 (PDT) Received: (qmail 8408 invoked from network); 4 Oct 2000 18:52:31 -0000 Received: from lcm243.cvzoom.net (208.230.69.243) by krycek.zoominternet.net with SMTP; 4 Oct 2000 18:52:31 -0000 Date: Wed, 4 Oct 2000 13:51:45 -0400 (EDT) From: Donn Miller To: Jordan Hubbard Cc: current@freebsd.org, bde@freebsd.org Subject: Re: ext2fs support for writing - what's the verdict? In-Reply-To: <91787.970681331@winston.osd.bsdi.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 Wed, 4 Oct 2000, Jordan Hubbard wrote: > As most people probably know, you can't write on ext2fs filesystems > with any of the "newer" Linux distributions, like Red Hat 6.2 on > up. The filesystem mount refuses r/w permission with the message > "WARNING: R/W mount of #
denied due to unsupported optional features" > > Do we plan to do anything about that? Heck, I'm not even sure who > maintains ext2fs these days - bde maybe? [hopeful facial expression] :-) I think you can manipulate those features somewhat from FreeBSD with tunefs, but I don't know how. Alexander Viro said something about this on comp.unix.bsd.freebsd.misc. In Deja, I would do a search in CUBFM for Alexander Viro and ext2fs. I kinda wish Viro would read this list, as he seems to be an expert on areas common to both FreeBSD and Linux. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 4 14:22:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 9B09A37B502; Wed, 4 Oct 2000 14:22:48 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id XAA33893; Wed, 4 Oct 2000 23:22:46 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e94LMSG00391; Wed, 4 Oct 2000 23:22:28 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Wed, 4 Oct 2000 23:22:28 +0200 (CEST) From: Michael Reifenberger To: FreeBSD-Current Cc: sos@freebsd.org Subject: Still no go with Sandisk SM and -current Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2146186496-970694548=:324" 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-2146186496-970694548=:324 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, As the subject says, I get the following message from my Tecra8000 and -current: ata4 at port 0x250-0x25f irq 10 slot 1 on pccard1 ata4-master: ata_command: timeout waiting for intr ata4-master: identify failed pccard: card inserted, slot 1 Attached is the pccardc dumpcis output. I tried with a appropriate hint but got no success too. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS --0-2146186496-970694548=:324 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dumpcis.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dumpcis.out" Q29uZmlndXJhdGlvbiBkYXRhIGZvciBjYXJkIGluIHNsb3QgMA0KVHVwbGUg IzEsIGNvZGUgPSAweDEgKENvbW1vbiBtZW1vcnkgZGVzY3JpcHRvciksIGxl bmd0aCA9IDINCiAgICAwMDA6ICAwMCBmZg0KCUNvbW1vbiBtZW1vcnkgZGV2 aWNlIGluZm9ybWF0aW9uOg0KCQlEZXZpY2UgbnVtYmVyIDEsIHR5cGUgTm8g ZGV2aWNlLCBXUFMgPSBPRkYNCgkJU3BlZWQgPSBObyBzcGVlZCwgTWVtb3J5 IGJsb2NrIHNpemUgPSByZXNlcnZlZCwgMzIgdW5pdHMNClR1cGxlICMyLCBj b2RlID0gMHgxNyAoQXR0cmlidXRlIG1lbW9yeSBkZXNjcmlwdG9yKSwgbGVu Z3RoID0gMw0KICAgIDAwMDogIDQzIDAyIGZmDQoJQXR0cmlidXRlIG1lbW9y eSBkZXZpY2UgaW5mb3JtYXRpb246DQoJCURldmljZSBudW1iZXIgMSwgdHlw ZSBFRVBST00sIFdQUyA9IE9GRg0KCQlTcGVlZCA9IDE1MG5TLCBNZW1vcnkg YmxvY2sgc2l6ZSA9IDhLYiwgMSB1bml0cw0KVHVwbGUgIzMsIGNvZGUgPSAw eDIwIChNYW51ZmFjdHVyZXIgSUQpLCBsZW5ndGggPSA0DQogICAgMDAwOiAg MDEgMDEgODkgMDUNCglQQ01DSUEgSUQgPSAweDEwMSwgT0VNIElEID0gMHg1 ODkNClR1cGxlICM0LCBjb2RlID0gMHgyMSAoRnVuY3Rpb25hbCBJRCksIGxl bmd0aCA9IDINCiAgICAwMDA6ICAwNiAwMA0KCU5ldHdvcmsvTEFOIGFkYXB0 ZXINClR1cGxlICM1LCBjb2RlID0gMHgxNSAoVmVyc2lvbiAxIGluZm8pLCBs ZW5ndGggPSA1Nw0KICAgIDAwMDogIDA0IDAxIDMzIDQzIDZmIDZkIDIwIDQz IDZmIDcyIDcwIDZmIDcyIDYxIDc0IDY5DQogICAgMDEwOiAgNmYgNmUgMDAg MzMgNDMgMzUgMzggMzkgMDAgNTQgNTAgMmYgNDIgNGUgNDMgMjANCiAgICAw MjA6ICA0YyA0MSA0ZSAyMCA0MyA2MSA3MiA2NCAyMCA1NiA2NSA3MiAyZSAy MCAzMiA2MQ0KICAgIDAzMDogIDAwIDMwIDMwIDMwIDMwIDMwIDMyIDAwIGZm DQoJVmVyc2lvbiA9IDQuMSwgTWFudWYgPSBbM0NvbSBDb3Jwb3JhdGlvbl0s IGNhcmQgdmVycyA9IFszQzU4OV0NCglBZGRpdC4gaW5mbyA9IFtUUC9CTkMg TEFOIENhcmQgVmVyLiAyYV0sWzAwMDAwMl0NClR1cGxlICM2LCBjb2RlID0g MHgxYSAoQ29uZmlndXJhdGlvbiBtYXApLCBsZW5ndGggPSA2DQogICAgMDAw OiAgMDIgMDMgMDAgMDAgMDEgMDMNCglSZWcgbGVuID0gMywgY29uZmlnIHJl Z2lzdGVyIGFkZHIgPSAweDEwMDAwLCBsYXN0IGNvbmZpZyA9IDB4Mw0KCVJl Z2lzdGVyczogWFgtLS0tLS0gDQpUdXBsZSAjNywgY29kZSA9IDB4MWIgKENv bmZpZ3VyYXRpb24gZW50cnkpLCBsZW5ndGggPSAxNQ0KICAgIDAwMDogIGMx IDAxIDFkIDcxIDU1IDM1IDU1IDU0IGUwIDcyIDVkIDY0IDMwIGZmIGZmDQoJ Q29uZmlnIGluZGV4ID0gMHgxKGRlZmF1bHQpDQoJSW50ZXJmYWNlIGJ5dGUg PSAweDEgKEkvTykNCglWY2MgcHdyOg0KCQlOb21pbmFsIG9wZXJhdGluZyBz dXBwbHkgdm9sdGFnZTogNSB4IDFWDQoJCU1heCBjdXJyZW50IGF2ZXJhZ2Ug b3ZlciAxIHNlY29uZDogMyB4IDEwbUENCgkJTWF4IGN1cnJlbnQgYXZlcmFn ZSBvdmVyIDEwIG1zOiA1IHggMTBtQQ0KCQlQb3dlciBkb3duIHN1cHBseSBj dXJyZW50OiA1IHggMW1BDQoJV2FpdCBzY2FsZSBTcGVlZCA9IDcuMCB4IDEw MCBucw0KCVJEWS9CU1kgc2NhbGUgU3BlZWQgPSA1LjAgeCAxMDAgdXMNCglD YXJkIGRlY29kZXMgNCBhZGRyZXNzIGxpbmVzLCBmdWxsIDgvMTYgQml0IEkv Tw0KCQlJUlEgbW9kZXM6IExldmVsDQoJCUlSUXM6ICAwIDEgMiAzIDQgNSA2 IDcgOCA5IDEwIDExIDEyIDEzIDE0IDE1DQpUdXBsZSAjOCwgY29kZSA9IDB4 MWIgKENvbmZpZ3VyYXRpb24gZW50cnkpLCBsZW5ndGggPSA3DQogICAgMDAw OiAgMDMgMDEgNzEgNTUgMjYgMjYgNTQNCglDb25maWcgaW5kZXggPSAweDMN CglWY2MgcHdyOg0KCQlOb21pbmFsIG9wZXJhdGluZyBzdXBwbHkgdm9sdGFn ZTogNSB4IDFWDQoJCU1heCBjdXJyZW50IGF2ZXJhZ2Ugb3ZlciAxIHNlY29u ZDogMiB4IDEwMG1BDQoJCU1heCBjdXJyZW50IGF2ZXJhZ2Ugb3ZlciAxMCBt czogMiB4IDEwMG1BDQoJCVBvd2VyIGRvd24gc3VwcGx5IGN1cnJlbnQ6IDUg eCAxbUENClR1cGxlICM5LCBjb2RlID0gMHgxOSAoSkVERUMgZGVzY3IgZm9y IGF0dHJpYnV0ZSBtZW1vcnkpLCBsZW5ndGggPSAzDQogICAgMDAwOiAgMDAg MDAgZmYNClR1cGxlICMxMCwgY29kZSA9IDB4MTQgKE5vIGxpbmspLCBsZW5n dGggPSAwDQpUdXBsZSAjMTEsIGNvZGUgPSAweDEwIChDaGVja3N1bSksIGxl bmd0aCA9IDUNCiAgICAwMDA6ICA4OSBmZiA4MCAwMCAwMA0KCUNoZWNrc3Vt IGZyb20gb2Zmc2V0IDY1NDE3LCBsZW5ndGggMTI4LCB2YWx1ZSBpcyAweDAN ClR1cGxlICMxMiwgY29kZSA9IDB4ZmYgKFRlcm1pbmF0b3IpLCBsZW5ndGgg PSAwDQoyIHNsb3RzIGZvdW5kDQo= --0-2146186496-970694548=:324-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 4 15:29:11 2000 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 D88DD37B503; Wed, 4 Oct 2000 15:29:05 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id JAA20603; Thu, 5 Oct 2000 09:28:41 +1100 Date: Thu, 5 Oct 2000 09:28:36 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jordan Hubbard Cc: current@freebsd.org, bde@freebsd.org Subject: Re: ext2fs support for writing - what's the verdict? In-Reply-To: <91787.970681331@winston.osd.bsdi.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 Wed, 4 Oct 2000, Jordan Hubbard wrote: > As most people probably know, you can't write on ext2fs filesystems > with any of the "newer" Linux distributions, like Red Hat 6.2 on > up. The filesystem mount refuses r/w permission with the message > "WARNING: R/W mount of #
denied due to unsupported optional features" > > Do we plan to do anything about that? Heck, I'm not even sure who > maintains ext2fs these days - bde maybe? [hopeful facial expression] :-) I have 64K off uncommitted diffs (-c2) for ext2fs, but none for sparse superblocks. This problem is easy to work around by not using unsupported optional features. Run tune2fs and e2fsck under Linux to turn off the features (see tune2fs(8)). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Oct 4 23:52:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 93D4137B66C; Wed, 4 Oct 2000 23:52:24 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e956pgX96517; Wed, 4 Oct 2000 23:51:50 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Bruce Evans Cc: current@freebsd.org, bde@freebsd.org Subject: Re: ext2fs support for writing - what's the verdict? In-Reply-To: Message from Bruce Evans of "Thu, 05 Oct 2000 09:28:36 +1100." Date: Wed, 04 Oct 2000 23:51:41 -0700 Message-ID: <96512.970728701@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have 64K off uncommitted diffs (-c2) for ext2fs, but none for sparse > superblocks. This problem is easy to work around by not using > unsupported optional features. Run tune2fs and e2fsck under Linux to > turn off the features (see tune2fs(8)). That's a nice idea and may work in my particular case, but this is also the out-of-box configuration for Red Hat and most Linux-to-FreeBSD users wouldn't know a tune2fs if it snuck up and bit them on the ass in broad daylight. How hard would it be to support sparse superblocks? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 0: 0:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 462FB37B503 for ; Thu, 5 Oct 2000 00:00:25 -0700 (PDT) Received: (qmail 87560 invoked by uid 100); 5 Oct 2000 07:00:24 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14812.9992.117646.55129@guru.mired.org> Date: Thu, 5 Oct 2000 02:00:24 -0500 (CDT) To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: ext2fs support for writing - what's the verdict? In-Reply-To: <96512.970728701@winston.osd.bsdi.com> References: <96512.970728701@winston.osd.bsdi.com> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard writes: > That's a nice idea and may work in my particular case, but this is > also the out-of-box configuration for Red Hat and most > Linux-to-FreeBSD users wouldn't know a tune2fs if it snuck up and bit > them on the ass in broad daylight. How hard would it be to support > sparse superblocks? Just FYI, Mandrake 7.1 does the same thing out of the box. ; Thu, 5 Oct 2000 02:37:08 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 9818A5D08 for ; Thu, 5 Oct 2000 11:37:02 +0200 (CEST) Date: Thu, 5 Oct 2000 11:37:02 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: freebsd-current@freebsd.org Subject: TI1225 CardBus controller 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 We have a lot of Lucent WaveLan (Orinoco) installations, primarily using the ISA-to-PCMCIA adapters. We would urgently need a PCI-to-PCMCIA solution and Lucent provides the adapters which use a TI1225 chip. Unfortunatelly the legacy FreeBSD pccard driver has problems with this chip. I'm willing to put some work into making it work. I know about Warner's CardBus effort, but it's going too slow for my taste because I need a solution now (meaning this month). From reading the mailing list archives, I figured that the TI1225 driver does actually work in some laptops, because the BIOS does some magic initialization which the driver misses when running on a non-laptop box. Could somebody who has a laptop with a TI1225 PC card controller chip please contact me? My idea currently is to print out the values of important chip registers on a laptop and on a desktop and check what the differences are. This way I may be able to find out what the driver is missing out in the initialization. Anyone with knowledge of the issues involved is welcomed to contact me as well with as much information as possible - because my idea could be totally wrong for example. I have the datasheet for the TI1225 and am looking at it, but it's just too much for a newbie like me. I think comparing the setup of registers on a working and a non-working configuration could be a possible way to solve the problem, even for a newbie :) Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 3:41: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 9830937B502; Thu, 5 Oct 2000 03:40:47 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 8C61728A0F; Thu, 5 Oct 2000 17:40:41 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 7A962287DF; Thu, 5 Oct 2000 17:40:41 +0700 (ALMST) Date: Thu, 5 Oct 2000 17:40:41 +0700 (ALMST) From: Boris Popov To: freebsd-current@freebsd.org Cc: freebsd-smp@freebsd.org Subject: Problems with kthread_exit() and SMPng Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1753296439-970742441=:43806" 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-1753296439-970742441=:43806 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, Currently I'm trying to make KLD which uses kernel threads unloadable under recent -current. The prototype of functions looks like this: void my_thread(void*arg) { while(wearewanted) { do_something(); tsleep(); } exited = 1; kthread_exit(0); } void my_unload() { wearewanted = 0; while (!exited) tsleep(1sec); } my_unload() function called from the module unload event which issued from the kldunload() syscall. Unfortunately, kernel panics in the mtx_exit_hard() function. After some examination I've found that two fields in the Giant mutex structure set to unexpected values: ---- empty mtx_blocked for mutex Giant mtx_contested not in any list for mutex Giant ---- These messages printed by added diagnostics code. With this patch (see attachment) it is possible to load and unload KLD without any problems on UP machine except that the above messages printed. However, I'm don't know if they are correct. (btw, 4.1 doesn't have this problem). Any ideas why this happened and how to fix it ? -- Boris Popov http://www.butya.kz/~bp/ --0-1753296439-970742441=:43806 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="synch_machdep.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="synch_machdep.diff" SW5kZXg6IHN5bmNoX21hY2hkZXAuYw0KPT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PQ0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3N5cy9pMzg2L2kzODYvc3lu Y2hfbWFjaGRlcC5jLHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS41DQpkaWZm IC11IC1yMS41IHN5bmNoX21hY2hkZXAuYw0KLS0tIHN5bmNoX21hY2hkZXAu YwkyMDAwLzEwLzA0IDAxOjIwOjQ5CTEuNQ0KKysrIHN5bmNoX21hY2hkZXAu YwkyMDAwLzEwLzA1IDEwOjIzOjMzDQpAQCAtMzU1LDEwICszNTUsMTYgQEAN CiAJCXAgPSBDVVJQUk9DOw0KIAkJcDEgPSBUQUlMUV9GSVJTVCgmbS0+bXR4 X2Jsb2NrZWQpOw0KIAkJTVBBU1MocC0+cF9tYWdpYyA9PSBQX01BR0lDKTsN Ci0JCU1QQVNTKHAxLT5wX21hZ2ljID09IFBfTUFHSUMpOw0KLQkJVEFJTFFf UkVNT1ZFKCZtLT5tdHhfYmxvY2tlZCwgcDEsIHBfcHJvY3EpOw0KKwkJaWYg KHAxKSB7DQorCQkJTVBBU1MocDEtPnBfbWFnaWMgPT0gUF9NQUdJQyk7DQor CQkJVEFJTFFfUkVNT1ZFKCZtLT5tdHhfYmxvY2tlZCwgcDEsIHBfcHJvY3Ep Ow0KKwkJfSBlbHNlDQorCQkJcHJpbnRmKCJlbXB0eSBtdHhfYmxvY2tlZCBm b3IgbXV0ZXggJXNcbiIsIG0tPm10eF9kZXNjcmlwdGlvbik7DQogCQlpZiAo VEFJTFFfRU1QVFkoJm0tPm10eF9ibG9ja2VkKSkgew0KLQkJCUxJU1RfUkVN T1ZFKG0sIG10eF9jb250ZXN0ZWQpOw0KKwkJCWlmIChtLT5tdHhfY29udGVz dGVkLmxlX3ByZXYgIT0gTlVMTCkNCisJCQkJTElTVF9SRU1PVkUobSwgbXR4 X2NvbnRlc3RlZCk7DQorCQkJZWxzZQ0KKwkJCQlwcmludGYoIm10eF9jb250 ZXN0ZWQgbm90IGluIGFueSBsaXN0IGZvciBtdXRleCAlc1xuIiwgbS0+bXR4 X2Rlc2NyaXB0aW9uKTsNCiAJCQlhdG9taWNfY21wc2V0X2ludCgmbS0+bXR4 X2xvY2ssIG0tPm10eF9sb2NrLA0KIAkJCQkJICBNVFhfVU5PV05FRCk7DQog CQkJQ1RSMShLVFJfTE9DSywgIm10eF9leGl0OiAweCVwIG5vdCBoZWxkIiwg bSk7DQpAQCAtMzczLDEyICszNzksMTUgQEANCiAJCWlmIChwcmkgPiBwLT5w X25hdGl2ZXByaSkNCiAJCQlwcmkgPSBwLT5wX25hdGl2ZXByaTsNCiAJCVNF VF9QUklPKHAsIHByaSk7DQotCQlDVFIyKEtUUl9MT0NLLCAibXR4X2V4aXQ6 IDB4JXAgY29udGVzdGVkIHNldHJ1bnF1ZXVlIDB4JXAiLA0KLQkJICAgIG0s IHAxKTsNCi0JCXAxLT5wX2Jsb2NrZWQgPSBOVUxMOw0KLQkJcDEtPnBfc3Rh dCA9IFNSVU47DQotCQlzZXRydW5xdWV1ZShwMSk7DQotCQlpZiAoKHR5cGUg JiBNVFhfTk9TV0lUQ0gpID09IDAgJiYgcDEtPnBfcHJpb3JpdHkgPCBwcmkp IHsNCisJCWlmIChwMSkgew0KKwkJCUNUUjIoS1RSX0xPQ0ssICJtdHhfZXhp dDogMHglcCBjb250ZXN0ZWQgc2V0cnVucXVldWUgMHglcCIsDQorCQkJICAg IG0sIHAxKTsNCisJCQlwMS0+cF9ibG9ja2VkID0gTlVMTDsNCisJCQlwMS0+ cF9zdGF0ID0gU1JVTjsNCisJCQlzZXRydW5xdWV1ZShwMSk7DQorCQl9DQor CQlpZiAoKHR5cGUgJiBNVFhfTk9TV0lUQ0gpID09IDAgJiYNCisJCSAgICAo cDEgPT0gTlVMTCB8fCBwMS0+cF9wcmlvcml0eSA8IHByaSkpIHsNCiAjaWZk ZWYgbm90eWV0DQogCQkJaWYgKHAtPnBfZmxhZyAmIChQX0lUSEQgfCBQX1NJ VEhEKSkgew0KIAkJCQlpdGhkX3QgKml0ID0gKGl0aGRfdCAqKXA7DQo= --0-1753296439-970742441=:43806-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 4: 4: 1 2000 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 9647F37B502; Thu, 5 Oct 2000 04:03:56 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA20933; Thu, 5 Oct 2000 22:03:52 +1100 Date: Thu, 5 Oct 2000 22:03:47 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jeffrey Hsu Cc: current@FreeBSD.ORG Subject: Re: #include in In-Reply-To: <20001003080816.9D03137B502@hub.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 Tue, 3 Oct 2000, Jeffrey Hsu wrote: > > I think should have been removed when offsetof() became > > standard. > > At last count, offsetof() is defined in 11 different places in the kernel: > alpha/alpha/machdep.c, line 234 >... Some other places include . > If we unify it in one header file, I'd be happy to use that for STAILQ_LAST(). is a good place for it now. > > strbase() is now used in . It is > > easy to implement directly using offsetof(). Unfortunately, if it is > > implemented using offsetof(), then will depend on > > . > > So, what's the correct solution? I'm currently using the following. This avoids a bug in fldoff(): casting to int is wrong and causes warnings on alphas. I use a cast to __uintptr_t since casting to size_t is normally right (offsetof() depends on it), and __uintptr_t is normally equivalent to size_t and is easier to get at. --- diff -c2 queue.h~ queue.h *** queue.h~ Fri Aug 4 21:38:55 2000 --- queue.h Thu Oct 5 21:22:51 2000 *************** *** 38,43 **** #define _SYS_QUEUE_H_ - #include - /* * This file defines five types of data structures: singly-linked lists, --- 38,41 ---- *************** *** 224,231 **** } while (0) #define STAILQ_LAST(head, type, field) \ ! (STAILQ_EMPTY(head) ? \ ! NULL : \ ! strbase(type, (head)->stqh_last, field)) #define STAILQ_NEXT(elm, field) ((elm)->field.stqe_next) --- 222,239 ---- } while (0) + /* + * XXX auxiliary macros for STAILQ_LAST() adapted from offsetof() in + * and strbase() in . + */ + #include + + #define __offsetof(type, member) \ + ((__uintptr_t)(&((type *)0)->member)) + #define __strbase(name, addr, field) \ + ((struct name *)((char *)(addr) - __offsetof(struct name, field))) + #define STAILQ_LAST(head, type, field) \ ! (STAILQ_EMPTY(head) ? NULL : \ ! __strbase(type, (head)->stqh_last, field)) #define STAILQ_NEXT(elm, field) ((elm)->field.stqe_next) --- Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 6:36:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by hub.freebsd.org (Postfix) with ESMTP id D7AE737B66D for ; Thu, 5 Oct 2000 06:36:19 -0700 (PDT) Received: from cronyx.ru by hanoi.cronyx.ru with ESMTP id RAA02641; (8.9.3/vak/2.1) Thu, 5 Oct 2000 17:43:21 +0400 (MSD) Message-ID: <39DC84E3.9DEF3F87@cronyx.ru> Date: Thu, 05 Oct 2000 17:40:51 +0400 From: Kurakin Roman Organization: Cronyx X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Submiting new code Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, How can I send a quite big submission of source code. Handbook says that I should put big part of report in to ftp.freebsd.org/pub/FreeBSD/incoming but I can't found it. Kurakin Roman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 6:45:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 464BE37B502 for ; Thu, 5 Oct 2000 06:45:39 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.ca ([24.201.203.136]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G1O0075SSZAXN@field.videotron.net> for freebsd-current@freebsd.org; Sat, 30 Sep 2000 02:35:34 -0400 (EDT) Date: Sat, 30 Sep 2000 02:39:27 -0400 (EDT) From: Bosko Milekic Subject: [HEADS-UP] mbuf mutex code going in... To: freebsd-current@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 Hello, I've just committed the mbuf-related SMPng code.... please see commit logs for details, and: http://people.freebsd.org/~bmilekic/mtx_journal I sincerely hope that there were little or no errors, as I've tried hard to avoid them. But this is a big diff, it's been sitting around for a while, and it covers a lot of things. So, despite 6 versions of a diff, and numerous reviews, certain things may have slipped through the cracks. Please, don't panic: just report problems and provide all necessary details. I'll do my best to take care of all issues as soon as possible, if necessary. :-) If all goes well, more commits, some adding important functionality, to follow... Regards, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 7:16:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 8860037B66C for ; Thu, 5 Oct 2000 07:16:24 -0700 (PDT) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G1V00HM0NWJO9@falla.videotron.net> for freebsd-current@FreeBSD.ORG; Tue, 3 Oct 2000 19:29:07 -0400 (EDT) Date: Tue, 03 Oct 2000 19:33:01 -0400 (EDT) From: Bosko Milekic Subject: Re: page fault while in kernel mode In-reply-to: <86d7hhlnpr.fsf@mharnois.workgroup.net> To: Michael Harnois Cc: freebsd-current@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 Hi Michael, Do you think you can provide us with a stack trace, at the least? This would deffinately give us something more to work with. Unfortunately, with this information, it's very difficult to pin-point the problem, as we're not certain as to what is at 0xc029e6cb, exactly. Also, is there anything particular that you notice that is happening in parallel to this? Anything special you're doing? On 3 Oct 2000, Michael Harnois wrote: > The past three days or so with -current my system has been locking up > solid under load. Today I was fortunate enough to have in happen when > in console mode so that I could see the problem: > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x10000 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc029e6cb > stack pointer = 0x10:0xcefdfe18 > frame pointer = 0x10:0xccfdfe20 > code segment = base 0x0, limit 0xffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 2355 (procmail) > trap number = 12 > panic: page fault > acpi0: acpi_io_pml_enable(1) = (0) > acpi0: acpi_io_gpe0_enable(1) = (0) > syncing disks... > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > No man knows how bad he is > till he has tried very hard to be good. -- C.S. Lewis Regards, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 7:29:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 46A4737B502; Thu, 5 Oct 2000 07:29:48 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id KAA77924; Thu, 5 Oct 2000 10:29:40 -0400 (EDT) (envelope-from mwlucas) Date: Thu, 5 Oct 2000 10:29:40 -0400 From: Michael Lucas To: Kurakin Roman Cc: freebsd-current@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: Submiting new code Message-ID: <20001005102940.A77870@blackhelicopters.org> References: <39DC84E3.9DEF3F87@cronyx.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39DC84E3.9DEF3F87@cronyx.ru>; from rik@cronyx.ru on Thu, Oct 05, 2000 at 05:40:51PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (copied to -doc for reasons which will become clear below) The FTP server no longer accepts uploads. Use uuencode and send-pr. Many people put code submissions up on a local web site and request comments on -current or -hackers before doing this. It makes the eventual code submission much more likely to be accepted. Docs folks, would one of you like to whack the offending statement from the Handbook? It looks like section 19.2.4 is the problem. (Of course, if we have a new FTP site, that would be good too. :) On Thu, Oct 05, 2000 at 05:40:51PM +0400, Kurakin Roman wrote: > Hi, > > How can I send a quite big submission of source code. Handbook > says that I should put big part of report in to > ftp.freebsd.org/pub/FreeBSD/incoming but I can't found it. > > Kurakin Roman > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 8: 7:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id CD7F837B502 for ; Thu, 5 Oct 2000 08:07:44 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA64837; Thu, 5 Oct 2000 11:07:29 -0400 (EDT) (envelope-from wollman) Date: Thu, 5 Oct 2000 11:07:29 -0400 (EDT) From: Garrett Wollman Message-Id: <200010051507.LAA64837@khavrinen.lcs.mit.edu> To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Subject: TI1225 CardBus controller In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > From reading the mailing list archives, I figured that the TI1225 > driver does actually work in some laptops, because the BIOS does > some magic initialization which the driver misses when running on a > non-laptop box. It's not necessarily just because of what the BIOS does. I am of the belief that the PCI card only works under the CardBus programming model. The reason should be obvious: the IRQ lines that the PC-Card interface needs aren't available on the PCI connector. When that chip is used in a laptop, it's connected directly to the PIIX so that it can get the full ISA functionality it needs in order to implement the Intel PCIC programming model. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 8:46:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by hub.freebsd.org (Postfix) with ESMTP id 7621537B502; Thu, 5 Oct 2000 08:46:38 -0700 (PDT) Received: from cronyx.ru by hanoi.cronyx.ru with ESMTP id TAA03188; (8.9.3/vak/2.1) Thu, 5 Oct 2000 19:54:52 +0400 (MSD) Message-ID: <39DCA3B7.E089F90D@cronyx.ru> Date: Thu, 05 Oct 2000 19:52:23 +0400 From: Kurakin Roman Organization: Cronyx X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Michael Lucas Cc: freebsd-current@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: Submiting new code References: <39DC84E3.9DEF3F87@cronyx.ru> <20001005102940.A77870@blackhelicopters.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you. Michael Lucas wrote: > > (copied to -doc for reasons which will become clear below) > > The FTP server no longer accepts uploads. Use uuencode and send-pr. > > Many people put code submissions up on a local web site and request > comments on -current or -hackers before doing this. It makes the > eventual code submission much more likely to be accepted. > > Docs folks, would one of you like to whack the offending statement > from the Handbook? It looks like section 19.2.4 is the problem. (Of > course, if we have a new FTP site, that would be good too. :) > > On Thu, Oct 05, 2000 at 05:40:51PM +0400, Kurakin Roman wrote: > > Hi, > > > > How can I send a quite big submission of source code. Handbook > > says that I should put big part of report in to > > ftp.freebsd.org/pub/FreeBSD/incoming but I can't found it. > > > > Kurakin Roman > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Michael Lucas > mwlucas@blackhelicopters.org > http://www.blackhelicopters.org/~mwlucas/ > Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 8:57:57 2000 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 CD53237B66C for ; Thu, 5 Oct 2000 08:57:49 -0700 (PDT) Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id XAA06124; Thu, 5 Oct 2000 23:57:43 +0800 Received: from elischer.org (reggae-39-94.nv.iinet.net.au [203.59.173.94]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with ESMTP id XAA14222; Thu, 5 Oct 2000 23:57:32 +0800 Message-ID: <39DCA4CF.A5B5F2F8@elischer.org> Date: Thu, 05 Oct 2000 08:57:03 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Blaz Zupan Cc: freebsd-current@freebsd.org Subject: Re: TI1225 CardBus controller 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 Blaz Zupan wrote: > > Could somebody who has a laptop with a TI1225 PC card controller chip please > contact me? My idea currently is to print out the values of important chip > registers on a laptop and on a desktop and check what the differences > are. This way I may be able to find out what the driver is missing out in the > initialization. > The Dell Inspiron 7500 has one...... works just fine.. pcic-pci0: at device 4.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC p ci int + CSC serial isa irq] pcic-pci1: at device 4.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC p ci int + CSC serial isa irq] ... pccard: card inserted, slot 0 sio4 at port 0x2e8-0x2ef irq 9 slot 0 on pccard0 sio4: type 16550A -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 11: 4:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id 45F6F37B503; Thu, 5 Oct 2000 11:04:09 -0700 (PDT) Received: from stinky.palnet.com (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id UAA36175; Thu, 5 Oct 2000 20:09:10 +0200 (IST) Message-Id: <5.0.0.23.0.20001005194437.00abf8a8@192.116.19.220> X-Sender: mustafa@192.116.19.220 X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.23 (Beta) Date: Thu, 05 Oct 2000 19:45:40 +0200 To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org From: Mustafa Deeb Subject: Looking for Patches Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, anyone knows where to find a MYSQL patch for cistron? cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 13: 7:53 2000 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 2AD4237B502; Thu, 5 Oct 2000 13:07:50 -0700 (PDT) Received: from laptop.baldwin.cx (john@dhcp248.osd.bsdi.com [204.216.28.248]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95K79i12478; Thu, 5 Oct 2000 13:07:10 -0700 (PDT) (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: Date: Thu, 05 Oct 2000 13:07:23 -0700 (PDT) From: John Baldwin To: Valentin Chopov , sos@FreeBSD.org Subject: RE: ATA DMA support is broken Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Oct-00 Valentin Chopov wrote: > After last changes ata DMA support is not workind and atapicd is not > recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) Yes, I've currently got the last round of ATA commits backed out in sys/dev/ata on my machine as well. The problem seems to be that the atapci driver is not attaching the ata child devices. Normal dmesg output: atapci0: port 0x1050-0x105f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 17301MB [35152/16/63] at ata0-master UDMA33 Bad dmesg output: atapci0: port 0x1050-0x105f at device 7.1 on pci0 -- 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 Oct 5 13:17:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 3292F37B503 for ; Thu, 5 Oct 2000 13:17:27 -0700 (PDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA10665; Thu, 5 Oct 2000 16:17:10 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id QAA05445; Thu, 5 Oct 2000 16:17:09 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA05434; Thu, 5 Oct 2000 16:17:09 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 5 Oct 2000 16:17:09 -0400 (EDT) From: Kenneth Wayne Culver To: Julian Elischer Cc: Blaz Zupan , freebsd-current@FreeBSD.ORG Subject: Re: TI1225 CardBus controller In-Reply-To: <39DCA4CF.A5B5F2F8@elischer.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 It doesn't work for cardbus. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 5 Oct 2000, Julian Elischer wrote: > Blaz Zupan wrote: > > > > > Could somebody who has a laptop with a TI1225 PC card controller chip please > > contact me? My idea currently is to print out the values of important chip > > registers on a laptop and on a desktop and check what the differences > > are. This way I may be able to find out what the driver is missing out in the > > initialization. > > > > The Dell Inspiron 7500 has one...... > works just fine.. > > pcic-pci0: at device 4.0 on pci0 > pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr > save][FUNC p > ci int + CSC serial isa irq] > pcic-pci1: at device 4.1 on pci0 > pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr > save][FUNC p > ci int + CSC serial isa irq] > ... > pccard: card inserted, slot 0 > sio4 at port 0x2e8-0x2ef irq 9 slot 0 on pccard0 > sio4: type 16550A > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Perth > v > > > 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 Oct 5 13:25:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7601537B502 for ; Thu, 5 Oct 2000 13:25:15 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e95KPDK00943; Thu, 5 Oct 2000 14:25:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA01734; Thu, 5 Oct 2000 14:25:13 -0600 (MDT) Message-Id: <200010052025.OAA01734@harmony.village.org> To: Blaz Zupan Subject: Re: TI1225 CardBus controller Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 05 Oct 2000 11:37:02 +0200." References: Date: Thu, 05 Oct 2000 14:25:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Blaz Zupan writes: : We have a lot of Lucent WaveLan (Orinoco) installations, primarily using the : ISA-to-PCMCIA adapters. We would urgently need a PCI-to-PCMCIA solution and : Lucent provides the adapters which use a TI1225 chip. Unfortunatelly the : legacy FreeBSD pccard driver has problems with this chip. I'm willing to put : some work into making it work. I know about Warner's CardBus effort, but it's : going too slow for my taste because I need a solution now (meaning this : month). : : From reading the mailing list archives, I figured that the TI1225 driver does : actually work in some laptops, because the BIOS does some magic initialization : which the driver misses when running on a non-laptop box. The TI-1225 works in a lot of laptops. The problem is that the pci cards don't have the "normal" cheater connection to the south bridge to do PCI based interrupts. : Anyone with knowledge of the issues involved is welcomed to contact me as well : with as much information as possible - because my idea could be totally wrong : for example. The problem is that FreeBSD needs to be able to route the interrupts to the pci bus using PCIBIOS (on i386, maybe others) but doesn't have a good interface for that. You would have to implement that infrastructure, or flesh out one of the partially implemented versions floating around and then fix the pcic driver to somehow know that it has to route the interrupts as well as just establishing them. If you'd like a less vague description, and are willing to work on it please let me know. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 13:26:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 38B9037B503; Thu, 5 Oct 2000 13:26:22 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA47742; Thu, 5 Oct 2000 22:32:57 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010052032.WAA47742@freebsd.dk> Subject: Re: ATA DMA support is broken In-Reply-To: from John Baldwin at "Oct 5, 2000 01:07:23 pm" To: jhb@FreeBSD.ORG (John Baldwin) Date: Thu, 5 Oct 2000 22:32:57 +0200 (CEST) Cc: valentin@valcho.net (Valentin Chopov), sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems John Baldwin wrote: > > On 03-Oct-00 Valentin Chopov wrote: > > After last changes ata DMA support is not workind and atapicd is not > > recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) > > Yes, I've currently got the last round of ATA commits backed out in > sys/dev/ata on my machine as well. The problem seems to be that the > atapci driver is not attaching the ata child devices. Normal dmesg > output: > > atapci0: port 0x1050-0x105f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 17301MB [35152/16/63] at ata0-master UDMA33 > > Bad dmesg output: > > atapci0: port 0x1050-0x105f at device 7.1 on pci0 I fixed this ~20 hours after that commit, blunder on my part, sorry... Use ata-all.c rev 1.73 or later... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 13:29: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5866E37B502 for ; Thu, 5 Oct 2000 13:28:57 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e95KStK00967; Thu, 5 Oct 2000 14:28:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA01780; Thu, 5 Oct 2000 14:28:54 -0600 (MDT) Message-Id: <200010052028.OAA01780@harmony.village.org> To: Garrett Wollman Subject: Re: TI1225 CardBus controller Cc: Blaz Zupan , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 05 Oct 2000 11:07:29 EDT." <200010051507.LAA64837@khavrinen.lcs.mit.edu> References: <200010051507.LAA64837@khavrinen.lcs.mit.edu> Date: Thu, 05 Oct 2000 14:28:54 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010051507.LAA64837@khavrinen.lcs.mit.edu> Garrett Wollman writes: : < said: : : > From reading the mailing list archives, I figured that the TI1225 : > driver does actually work in some laptops, because the BIOS does : > some magic initialization which the driver misses when running on a : > non-laptop box. : : It's not necessarily just because of what the BIOS does. I am of the : belief that the PCI card only works under the CardBus programming : model. I don't think that's the case. This card would work fine under the legacy model if you can have the interupts routed correctly as well as all the other stuff it does. The interrupt routing really is the only issue here, at least from my reading of the data sheets and such. there's also a side issue of level vs pulse interrupts that you might run into. You can still use the legacy interface to talk to card, modulo one or two pci config space register settings (iirc). Maybe this is what you mean. : The reason should be obvious: the IRQ lines that the PC-Card : interface needs aren't available on the PCI connector. When that chip : is used in a laptop, it's connected directly to the PIIX so that it : can get the full ISA functionality it needs in order to implement the : Intel PCIC programming model. This part is correct. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 14:31:16 2000 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 2A72537B66E; Thu, 5 Oct 2000 14:31:10 -0700 (PDT) Received: from laptop.baldwin.cx (john@dhcp248.osd.bsdi.com [204.216.28.248]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95LUsi15499; Thu, 5 Oct 2000 14:30:54 -0700 (PDT) (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: Date: Thu, 05 Oct 2000 14:31:07 -0700 (PDT) From: John Baldwin To: Boris Popov Subject: RE: Problems with kthread_exit() and SMPng Cc: freebsd-smp@FreeBSD.org, freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Oct-00 Boris Popov wrote: > Hello, > > Currently I'm trying to make KLD which uses kernel threads > unloadable under recent -current. The prototype of functions looks like > this: > > void > my_thread(void*arg) > { > while(wearewanted) { > do_something(); > tsleep(); > } > exited = 1; > kthread_exit(0); > } > > void > my_unload() > { > wearewanted = 0; > while (!exited) > tsleep(1sec); > } > > my_unload() function called from the module unload event which > issued from the kldunload() syscall. > > Unfortunately, kernel panics in the mtx_exit_hard() function. > After some examination I've found that two fields in the Giant mutex > structure set to unexpected values: > ---- > empty mtx_blocked for mutex Giant > mtx_contested not in any list for mutex Giant > ---- > > These messages printed by added diagnostics code. With this patch > (see attachment) it is possible to load and unload KLD without any > problems on UP machine except that the above messages printed. However, > I'm don't know if they are correct. (btw, 4.1 doesn't have this problem). > > Any ideas why this happened and how to fix it ? > -- > Boris Popov > http://www.butya.kz/~bp/ -- 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 Oct 5 14:31:24 2000 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 E2E0737B671; Thu, 5 Oct 2000 14:31:10 -0700 (PDT) Received: from laptop.baldwin.cx (john@dhcp248.osd.bsdi.com [204.216.28.248]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95LUti15503; Thu, 5 Oct 2000 14:30:55 -0700 (PDT) (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: Date: Thu, 05 Oct 2000 14:31:07 -0700 (PDT) From: John Baldwin To: Boris Popov Subject: RE: Problems with kthread_exit() and SMPng Cc: freebsd-smp@FreeBSD.org, freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Oct-00 Boris Popov wrote: > Hello, > > Currently I'm trying to make KLD which uses kernel threads > unloadable under recent -current. The prototype of functions looks like > this: > > void > my_thread(void*arg) > { > while(wearewanted) { > do_something(); > tsleep(); > } > exited = 1; > kthread_exit(0); > } You need to have Giant before you call kthread_exit(). > my_unload() function called from the module unload event which > issued from the kldunload() syscall. > > Unfortunately, kernel panics in the mtx_exit_hard() function. > After some examination I've found that two fields in the Giant mutex > structure set to unexpected values: Ah, I need to add a KASSERT() to the start of mtx_exit_hard() to verify that we own the mutex we are releasing. > ---- > empty mtx_blocked for mutex Giant > mtx_contested not in any list for mutex Giant > ---- > > These messages printed by added diagnostics code. With this patch > (see attachment) it is possible to load and unload KLD without any > problems on UP machine except that the above messages printed. However, > I'm don't know if they are correct. (btw, 4.1 doesn't have this problem). It is a bogus patch though. If you release a contested mutex, it should always have someone who is waiting to grab it. > Any ideas why this happened and how to fix it ? > -- > Boris Popov > http://www.butya.kz/~bp/ -- 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 Oct 5 14:32: 2 2000 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 186FE37B503; Thu, 5 Oct 2000 14:31:59 -0700 (PDT) Received: from laptop.baldwin.cx (john@dhcp248.osd.bsdi.com [204.216.28.248]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95LUMi15459; Thu, 5 Oct 2000 14:30:26 -0700 (PDT) (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: <200010052032.WAA47742@freebsd.dk> Date: Thu, 05 Oct 2000 14:30:34 -0700 (PDT) From: John Baldwin To: Soren Schmidt Subject: Re: ATA DMA support is broken Cc: freebsd-current@FreeBSD.org, sos@FreeBSD.org, (Valentin Chopov) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Oct-00 Soren Schmidt wrote: > It seems John Baldwin wrote: >> >> On 03-Oct-00 Valentin Chopov wrote: >> > After last changes ata DMA support is not workind and atapicd is not >> > recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) >> >> Yes, I've currently got the last round of ATA commits backed out in >> sys/dev/ata on my machine as well. The problem seems to be that the >> atapci driver is not attaching the ata child devices. Normal dmesg >> output: >> >> atapci0: port 0x1050-0x105f at device 7.1 on >> pci0 >> ata0: at 0x1f0 irq 14 on atapci0 >> ata1: at 0x170 irq 15 on atapci0 >> ad0: 17301MB [35152/16/63] at ata0-master UDMA33 >> >> Bad dmesg output: >> >> atapci0: port 0x1050-0x105f at device 7.1 on >> pci0 > > I fixed this ~20 hours after that commit, blunder on my part, sorry... > Use ata-all.c rev 1.73 or later... Woot! Thanks. > -Søren -- 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 Oct 5 14:46:56 2000 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 5BFD737B503; Thu, 5 Oct 2000 14:46:47 -0700 (PDT) Received: from laptop.baldwin.cx (john@dhcp248.osd.bsdi.com [204.216.28.248]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95Lkai16181; Thu, 5 Oct 2000 14:46:36 -0700 (PDT) (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: Date: Thu, 05 Oct 2000 14:46:49 -0700 (PDT) From: John Baldwin To: John Baldwin Subject: RE: Problems with kthread_exit() and SMPng Cc: freebsd-current@FreeBSD.org, freebsd-smp@FreeBSD.org, Boris Popov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ugh, my mail client ate my reply, lemme try again. > On 05-Oct-00 Boris Popov wrote: >> Hello, >> >> Currently I'm trying to make KLD which uses kernel threads >> unloadable under recent -current. The prototype of functions looks like >> this: >> >> void >> my_thread(void*arg) >> { >> while(wearewanted) { >> do_something(); >> tsleep(); >> } >> exited = 1; >> kthread_exit(0); >> } You need Giant before calling kthread_exit(). >> void >> my_unload() >> { >> wearewanted = 0; >> while (!exited) >> tsleep(1sec); >> } >> >> my_unload() function called from the module unload event which >> issued from the kldunload() syscall. >> >> Unfortunately, kernel panics in the mtx_exit_hard() function. >> After some examination I've found that two fields in the Giant mutex >> structure set to unexpected values: It should have died much earlier if you had INVARIANTS turned on. :( It looks like you are releasing a mutex you probably do not own because cpu_exit() (called by exit1() -> exit() -> kthread_exit()) releases Giant as one of its final tasks. >> ---- >> empty mtx_blocked for mutex Giant >> mtx_contested not in any list for mutex Giant >> ---- >> >> These messages printed by added diagnostics code. With this patch >> (see attachment) it is possible to load and unload KLD without any >> problems on UP machine except that the above messages printed. However, >> I'm don't know if they are correct. (btw, 4.1 doesn't have this problem). This patch is bogus I'm afraid. A contested mutex should always have a process waiting to grab it when it is released. -- 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 Oct 5 15:56:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id CE78037B502; Thu, 5 Oct 2000 15:56:37 -0700 (PDT) Received: from silvia.hip.berkeley.edu (sji-ca42-27.ix.netcom.com [209.111.212.27]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA10757; Thu, 5 Oct 2000 18:56:19 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.11.0/8.11.0) id e95MtOa52663; Thu, 5 Oct 2000 15:55:24 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Date: Thu, 5 Oct 2000 15:55:24 -0700 (PDT) Message-Id: <200010052255.e95MtOa52663@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: stable@freebsd.org, current@freebsd.org Reply-To: ports@freebsd.org Subject: HEADS UP: ports layout restructuring happening this weekend From: asami@freebsd.org (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello world, As those of you who have been following the ports list may know, we are changing the ports skeletons' layout in an effort to reduce the number of small directories and significantly speed up operation on the ports tree. This should especially help operations such as "CVS update", and will also reduce the number of i-nodes required to keep the whole tree around. The conversion will be done this weekend. It will only take a day or two. There should be no functional changes that you can see after the conversion (minus the bugs I may introduce, of course). However, during the conversion, the tree will be in an inconsistent state and attempts to use the tree will fail in most weird ways, so it is recommended that you cvsup the tree on or before Friday and do not cvsup again until I post an "all clear" message. Thanks, -PW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 18:30:30 2000 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 DF73737B503 for ; Thu, 5 Oct 2000 18:30:26 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e961UCi23836; Thu, 5 Oct 2000 18:30:12 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e961RlU43037; Thu, 5 Oct 2000 18:27:47 -0700 (PDT) (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: <20001004140250.H5060@yoko.hsc.fr> Date: Thu, 05 Oct 2000 18:27:47 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Alain Thivillon Subject: RE: -CURRENT clock deviation Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Oct-00 Alain Thivillon wrote: > > I have noticed that -CURRENT (build last week) is subject to a very high > clock deviation: I'm about to commit some changes to the clock interrupt code on the x86, try again once those are in place. > I run -CURRENT on a laptop, it seems that last commit in idle loop (the > one replacing loop by HLT and lowering temperature) broke the clock. Hmm, this shouldn't really break it. -- 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 Oct 5 18:39:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id B111B37B502; Thu, 5 Oct 2000 18:39:43 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e961fTh03854; Thu, 5 Oct 2000 18:41:34 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010060141.e961fTh03854@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: Alain Thivillon , current@FreeBSD.ORG Subject: Re: -CURRENT clock deviation In-reply-to: Your message of "Thu, 05 Oct 2000 18:27:47 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Oct 2000 18:41:29 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 04-Oct-00 Alain Thivillon wrote: > > > > I have noticed that -CURRENT (build last week) is subject to a very high > > clock deviation: > > I run -CURRENT on a laptop, it seems that last commit in idle loop (the > > one replacing loop by HLT and lowering temperature) broke the clock. > > Hmm, this shouldn't really break it. I'm also a little surprised about that, but the whole "idle thread" concept is up for some major revision soon anyway, with APCI promising to substantially change the way we view "idleness" in a lot of cases. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 18:55:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id D8E4D37B503; Thu, 5 Oct 2000 18:55:35 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id B93CB28AB3; Fri, 6 Oct 2000 08:55:14 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id A6B8828AAF; Fri, 6 Oct 2000 08:55:14 +0700 (ALMST) Date: Fri, 6 Oct 2000 08:55:14 +0700 (ALMST) From: Boris Popov To: John Baldwin Cc: freebsd-current@FreeBSD.org, freebsd-smp@FreeBSD.org Subject: RE: Problems with kthread_exit() and SMPng 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 Thu, 5 Oct 2000, John Baldwin wrote: > You need Giant before calling kthread_exit(). Ok. > >> After some examination I've found that two fields in the Giant mutex > >> structure set to unexpected values: > > It should have died much earlier if you had INVARIANTS turned on. :( It > looks like you are releasing a mutex you probably do not own because > cpu_exit() (called by exit1() -> exit() -> kthread_exit()) releases Giant > as one of its final tasks. This is probably the bug somewhere in the diagnostic code. I have INVARIANTS/INVARIANT_SUPPORT/DIAGNOSTIC turned on and UP machine just panics in the mtx_exit_hard() while SMP machine silently reboots :( > This patch is bogus I'm afraid. A contested mutex should always have a > process waiting to grab it when it is released. Yes, it should be bogus. But diagnostic is rather useful :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 19:50: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemicals.tacorp.com (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id CF7C737B502 for ; Thu, 5 Oct 2000 19:50:04 -0700 (PDT) Received: (from morganw@localhost) by volatile.chemicals.tacorp.com (8.11.1/8.11.1) id e962o3A71561; Thu, 5 Oct 2000 22:50:03 -0400 (EDT) (envelope-from morganw) Date: Thu, 5 Oct 2000 22:50:03 -0400 (EDT) From: Wesley Morgan To: current@freebsd.org Subject: panic in ufs_extattr_uepm_destroy() 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'm getting a panic in ufs_extattr_uepm_destroy() because in ffs_vfsops.c it is being called (line 788) with ump NULL: ufs_extattr_uepm_destroy(&ump->um_extattr); Of course disabling FFS_EXTATTR gets rid of this:) -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ wesleymorgan@home.com _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 19:53:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from irv1-mail2.intelenet.net (irv1-mail2.intelenet.net [204.182.160.3]) by hub.freebsd.org (Postfix) with ESMTP id 0F4E037B502; Thu, 5 Oct 2000 19:53:39 -0700 (PDT) Received: from nimba.intelenet.net (nimba.intelenet.net [207.38.65.93]) by irv1-mail2.intelenet.net (8.9.3/8.9.3) with ESMTP id TAA14133; Thu, 5 Oct 2000 19:53:38 -0700 (PDT) Received: by nimba.intelenet.net (Postfix, from userid 1294) id 4908183C72; Thu, 5 Oct 2000 19:53:38 -0700 (PDT) Date: Thu, 5 Oct 2000 19:53:38 -0700 From: matthew zeier To: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: boot problem with Mylex DAC960 - help ? Message-ID: <20001005195337.B8952@intelenet.net> 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 I installed 4.1.1 on an Intel ISP 2150 with a Mylex AcceleRAID 250. The fireware on the controller is 4.06 . After install and while it starts to boot I get: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 636kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (jkh@narf.osd.bsdi.com, Mon Sep 25 23:47:21 GMT 2000) Loading /boot/defaults/loader.conf | It hangs right there. Anyone run into this and resolve it? According to the mailing list archives, I should be able to boot off the Mylex. Thanks. - mz -- matthew zeier - "There ain't no rules around here. We're trying to accomplish something." - Thomas Edison To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 20:45:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id A199637B502; Thu, 5 Oct 2000 20:45:29 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e963lJh04201; Thu, 5 Oct 2000 20:47:19 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010060347.e963lJh04201@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: matthew zeier Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: boot problem with Mylex DAC960 - help ? In-reply-to: Your message of "Thu, 05 Oct 2000 19:53:38 PDT." <20001005195337.B8952@intelenet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Oct 2000 20:47:19 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know of any problems related to this at this time. Make sure you have the latest BIOS from Intel for the ISP2150. > I installed 4.1.1 on an Intel ISP 2150 with a Mylex AcceleRAID 250. The > fireware on the controller is 4.06 . > > After install and while it starts to boot I get: > > BTX loader 1.00 BTX version is 1.01 > Console: internal video/keyboard > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS 636kB/523200kB available memory > > FreeBSD/i386 bootstrap loader, Revision 0.8 > (jkh@narf.osd.bsdi.com, Mon Sep 25 23:47:21 GMT 2000) > Loading /boot/defaults/loader.conf > | > > > It hangs right there. Anyone run into this and resolve it? > > According to the mailing list archives, I should be able to boot off the > Mylex. > > Thanks. > > - mz > > -- > matthew zeier - "There ain't no rules around here. We're trying to > accomplish something." - Thomas Edison > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Oct 5 21:14:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from irv1-mail2.intelenet.net (irv1-mail2.intelenet.net [204.182.160.3]) by hub.freebsd.org (Postfix) with ESMTP id D9A8437B503; Thu, 5 Oct 2000 21:14:09 -0700 (PDT) Received: from nimba.intelenet.net (nimba.intelenet.net [207.38.65.93]) by irv1-mail2.intelenet.net (8.9.3/8.9.3) with ESMTP id VAA24118; Thu, 5 Oct 2000 21:14:09 -0700 (PDT) Received: by nimba.intelenet.net (Postfix, from userid 1294) id 2751583C72; Thu, 5 Oct 2000 21:14:09 -0700 (PDT) Date: Thu, 5 Oct 2000 21:14:08 -0700 From: matthew zeier To: Mike Smith Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: boot problem with Mylex DAC960 - help ? Message-ID: <20001005211408.C8952@intelenet.net> References: <20001005195337.B8952@intelenet.net> <200010060347.e963lJh04201@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010060347.e963lJh04201@mass.osd.bsdi.com>; from msmith@freebsd.org on Thu, Oct 05, 2000 at 08:47:19PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 05, 2000 at 08:47:19PM -0700, Mike Smith wrote: > > I don't know of any problems related to this at this time. Make sure you > have the latest BIOS from Intel for the ISP2150. I do. I noticed an updated BIOS for the Mylex... that's for tomorrow. > > > I installed 4.1.1 on an Intel ISP 2150 with a Mylex AcceleRAID 250. The > > fireware on the controller is 4.06 . > > > > After install and while it starts to boot I get: > > > > BTX loader 1.00 BTX version is 1.01 > > Console: internal video/keyboard > > BIOS drive A: is disk0 > > BIOS drive C: is disk1 > > BIOS 636kB/523200kB available memory > > > > FreeBSD/i386 bootstrap loader, Revision 0.8 > > (jkh@narf.osd.bsdi.com, Mon Sep 25 23:47:21 GMT 2000) > > Loading /boot/defaults/loader.conf > > | > > > > > > It hangs right there. Anyone run into this and resolve it? > > > > According to the mailing list archives, I should be able to boot off the > > Mylex. > > > > Thanks. > > > > - mz > > > > -- > > matthew zeier - "There ain't no rules around here. We're trying to > > accomplish something." - Thomas Edison > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > -- matthew zeier - "There ain't no rules around here. We're trying to accomplish something." - Thomas Edison To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 6:37: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id B7E7737B503; Fri, 6 Oct 2000 06:36:59 -0700 (PDT) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id AA10710E05; Fri, 6 Oct 2000 15:36:58 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id C8D849B281; Fri, 6 Oct 2000 15:36:54 +0200 (CEST) Date: Fri, 6 Oct 2000 15:36:54 +0200 From: Alain Thivillon To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: -CURRENT clock deviation Message-ID: <20001006153654.F427@yoko.hsc.fr> References: <20001004140250.H5060@yoko.hsc.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.2i In-Reply-To: ; from jhb@FreeBSD.ORG on Thu, Oct 05, 2000 at 06:27:47PM -0700 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin écrivait (wrote) : > I'm about to commit some changes to the clock interrupt code on the x86, > try again once those are in place. Yes, fixed: no more clock skew now. FreeBSD yoko.hsc.fr 5.0-CURRENT FreeBSD 5.0-CURRENT #70: Fri Oct 6 13:32:01 CEST 2000 titi@yoko.hsc.fr:/usr/src/sys/compile/YOKO50 i386 27 [15:35] titi@yoko:~# ntpdc ntpdc> peers remote local st poll reach delay offset disp ======================================================================= *itesec.hsc.fr 192.70.106.76 2 256 377 0.00230 0.019965 0.00351 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 6:41:41 2000 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 8B6D437B66D for ; Fri, 6 Oct 2000 06:41:37 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id JAA64892; Fri, 6 Oct 2000 09:41:29 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 6 Oct 2000 09:41:29 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Wesley Morgan Cc: current@freebsd.org Subject: Re: panic in ufs_extattr_uepm_destroy() 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 Thu, 5 Oct 2000, Wesley Morgan wrote: > I'm getting a panic in ufs_extattr_uepm_destroy() because in ffs_vfsops.c > it is being called (line 788) with ump NULL: > > ufs_extattr_uepm_destroy(&ump->um_extattr); > > Of course disabling FFS_EXTATTR gets rid of this:) Hmm. I added these changes without adequate testing so as to fix a problem with Jason's addition of a lockdestroy, which also rapidly resulted in a mess :-). I'm away from my dev box right now, as I'm on travel, so haven't tested the following, but it should work. Let me know, and I'll commit it ASAP. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services Index: ffs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v retrieving revision 1.129 diff -u -r1.129 ffs_vfsops.c --- ffs_vfsops.c 2000/10/04 04:44:51 1.129 +++ ffs_vfsops.c 2000/10/06 13:40:57 @@ -772,7 +772,7 @@ int mntflags; struct proc *p; { - register struct ufsmount *ump; + register struct ufsmount *ump = VFSTOUFS(mp); register struct fs *fs; int error, flags; @@ -794,7 +794,6 @@ if ((error = ffs_flushfiles(mp, flags, p)) != 0) return (error); } - ump = VFSTOUFS(mp); fs = ump->um_fs; if (fs->fs_ronly == 0) { fs->fs_clean = fs->fs_flags & FS_UNCLEAN ? 0 : 1; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 10:43:46 2000 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 6681237B66C; Fri, 6 Oct 2000 10:43:44 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA49483; Fri, 6 Oct 2000 10:43:43 -0700 (PDT) (envelope-from obrien) Date: Fri, 6 Oct 2000 10:43:43 -0700 From: "David O'Brien" To: Robert Watson Cc: current@freebsd.org Subject: Re: panic in ufs_extattr_uepm_destroy() Message-ID: <20001006104343.A49423@dragon.nuxi.com> Reply-To: obrien@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 rwatson@freebsd.org on Fri, Oct 06, 2000 at 09:41:29AM -0400 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 Fri, Oct 06, 2000 at 09:41:29AM -0400, Robert Watson wrote: > Index: ffs_vfsops.c > =================================================================== > RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v > retrieving revision 1.129 > diff -u -r1.129 ffs_vfsops.c > --- ffs_vfsops.c 2000/10/04 04:44:51 1.129 > +++ ffs_vfsops.c 2000/10/06 13:40:57 > @@ -772,7 +772,7 @@ > int mntflags; > struct proc *p; > { > - register struct ufsmount *ump; > + register struct ufsmount *ump = VFSTOUFS(mp); > register struct fs *fs; > int error, flags; This has a KNF style problem. The line you remove should stay and "ump = VFSTOUFS(mp);" added. -- -- David (obrien@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 Oct 6 11:11:29 2000 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 9D58C37B502; Fri, 6 Oct 2000 11:11:27 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id OAA68193; Fri, 6 Oct 2000 14:11:26 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 6 Oct 2000 14:11:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "David O'Brien" Cc: current@freebsd.org Subject: Re: panic in ufs_extattr_uepm_destroy() In-Reply-To: <20001006104343.A49423@dragon.nuxi.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 Fri, 6 Oct 2000, David O'Brien wrote: > This has a KNF style problem. The line you remove should stay and > "ump = VFSTOUFS(mp);" added. Well, either way, it has to be moved further up in the function or you dereference the NULL pointer. Bruce also pointed out the style problem, and I'll commit a fix to that this evening when I'm backin in Massachusetts. I should point out that the reason I modified it the way I did was to make it consistent witth use of VFSTOUFS in many other locations in the UFS/FFS code. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, 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 Fri Oct 6 11:44:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id DD2CC37B503 for ; Fri, 6 Oct 2000 11:44:42 -0700 (PDT) Received: from bloop.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Fri, 6 Oct 2000 13:46:37 -0500 Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e96IiAG06031 for ; Fri, 6 Oct 2000 13:44:10 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200010061844.e96IiAG06031@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: AMD X86-64 simulator available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Oct 2000 13:44:10 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Those of you who peruse slashdot will've already seen this - it's a Linux binary, and requires humungous amounts of memory & disk, 384MB & 4GB respectively. http://www.x86-64.org/downloads/ Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 13:24:24 2000 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 88E7937B503 for ; Fri, 6 Oct 2000 13:24:21 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id e96KR8J96088 for freebsd-current@freebsd.org; Fri, 6 Oct 2000 13:27:08 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200010062027.e96KR8J96088@troutmask.apl.washington.edu> Subject: make installkernel broken by recent manpage changes To: FreeBSD Current Date: Fri, 6 Oct 2000 13:27:08 -0700 (PDT) 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 ===> joy install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 install: joy.8.gz: No such file or directory *** Error code 71 -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 14:17:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 02AF837B502; Fri, 6 Oct 2000 14:17:10 -0700 (PDT) Received: (from netch@localhost) by segfault.kiev.ua (8) id AGO13145; Sat, 7 Oct 2000 00:17:05 +0300 (EEST) (envelope-from netch) Date: Sat, 7 Oct 2000 00:13:36 +0300 From: Valentin Nechayev To: freebsd-current@freebsd.org, phk@freebsd.org Subject: microuptime() went backwards: possible diagnosis Message-ID: <20001007001336.A346@nn.kiev.ua> Reply-To: netch@netch.kiev.ua Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Organization: Lucky Netch Incorporated X-42: On Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following is partial dmesg output from 5.0(13)-CURRENT-20001002 kernel with advanced debugging prints: ==={{{ mi_startup(): call subsystem 0x8800000(142606336), microuptime is 1.4027506 mi_startup(): call subsystem 0x8800000(142606336), microuptime is 1.4027897 mi_startup(): call subsystem 0xa000000(167772160), microuptime is 1.4028290 mi_startup(): call subsystem 0xa800000(176160768), microuptime is 1.4028701 mi_switch(): microuptime() went backwards (1.4029032 -> 0.734106) mi_switch(): microuptime() went backwards (1.4029032 -> 0.734590) mi_switch(): microuptime() went backwards (1.4029032 -> 0.735077) mi_switch(): microuptime() went backwards (1.4029032 -> 0.735555) [...] mi_switch(): microuptime() went backwards (1.4029032 -> 1.053263) mi_switch(): microuptime() went backwards (1.4029032 -> 1.053756) mi_startup(): call subsystem 0xd000000(218103808), microuptime is 1.054550 proc0_post(): switchtime initialized to 1.54864 mi_startup(): call subsystem 0xe000000(234881024), microuptime is 1.055501 mi_startup(): call subsystem 0xe400000(239075328), microuptime is 1.056012 ===}}} mi_switch() uses static variable 'switchtime' which keeps microuptime data when previous switching occured. For non-MP systems, proc0_post() sets it up. But first mi_switch() call occures when SI_SUB_INT_CONFIG_HOOKS (or SI_SUB_KICK_SCHEDULER?) subsystem called - why? IMHO it is too early for mi_switch(), it should be enabled on SI_SUB_RUN_SCHEDULER. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This was first question. Another one is strange value returned by microuptime() (3-5 millions of microseconds). This value becomes strange on my system during third SI_SUB_CONFIGURE instance, which is configure() in i386/i386/autoconf.c: [...] isa_probe_children: before probing non-PNP device: microuptime=0.349777, x=0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd.c: fd_probe(): before set_motor(): microuptime=0.291463, x=0 fdc0: FIFO enabled, 8 bytes threshold fd.c: fd_probe(): before NE7CMD_SENSED(): microuptime=1.292409, x=0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 isa_probe_children: after probing non-PNP device: microuptime=1.1653283, x=0 isa_probe_children: before probing non-PNP device: microuptime=1.1604514, x=7 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 isa_probe_children: after probing non-PNP device: microuptime=1.3138749, x=7 [...] it isn't possible to normalize value during this subsystem startup, is it? /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 14:55: 4 2000 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 AC0ED37B503; Fri, 6 Oct 2000 14:55:00 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e96Ls5i54065; Fri, 6 Oct 2000 14:54:05 -0700 (PDT) (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: <20001007001336.A346@nn.kiev.ua> Date: Fri, 06 Oct 2000 14:54:22 -0700 (PDT) From: John Baldwin To: Valentin Nechayev Subject: RE: microuptime() went backwards: possible diagnosis Cc: phk@FreeBSD.org, freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Oct-00 Valentin Nechayev wrote: > Following is partial dmesg output from 5.0(13)-CURRENT-20001002 kernel > with advanced debugging prints: The problem was that the interrupt threads for the clk interrupt introduced enough latency that occasionally (mostly during a heavy load of interrupts) tc_windup() wasn't called soon enough to update the timecounter. Making clock interrupts not be threaded fixes this problem. -- 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 Oct 6 15:17:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 6A6F837B503; Fri, 6 Oct 2000 15:17:06 -0700 (PDT) Received: from netch@localhost by burka.carrier.kiev.ua id BGO31522; Sat, 7 Oct 2000 01:17:03 +0300 (EEST) (envelope-from netch) Date: Sat, 7 Oct 2000 01:17:03 +0300 (EEST) Message-Id: <200010062217.BGO31522@burka.carrier.kiev.ua> From: netch@carrier.kiev.ua (Valentin Nechayev) To: John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.5-STABLE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Fri, 6 Oct 2000 22:00:23 +0000 (UTC), jhb wrote: JB> The problem was that the interrupt threads for the clk interrupt introduced JB> enough latency that occasionally (mostly during a heavy load of interrupts) JB> tc_windup() wasn't called soon enough to update the timecounter. Making On my system _each_ boot causes hundreds of these messages. And as described, long offsets without updating are caused by some code in drivers, i.e. DELAY(1000000) in isa/fd.c. Is it nesessary to call tc_windup() between iterations in isa_configure? ;| JB> clock interrupts not be threaded fixes this problem. Oh, well, I understand now that scheduling is nesessary to be run early because interrupts are implemented as kernel threads even when kernel is in phase of hardware detection.;( /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 15:32:55 2000 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 01E7237B503 for ; Fri, 6 Oct 2000 15:32:53 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e96MVwi55328; Fri, 6 Oct 2000 15:31:58 -0700 (PDT) (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: <200010062217.BGO31522@burka.carrier.kiev.ua> Date: Fri, 06 Oct 2000 15:32:15 -0700 (PDT) From: John Baldwin To: (Valentin Nechayev) Subject: Re: microuptime() went backwards Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Oct-00 Valentin Nechayev wrote: > At Fri, 6 Oct 2000 22:00:23 +0000 (UTC), jhb wrote: > > JB> The problem was that the interrupt threads for the clk interrupt > introduced > JB> enough latency that occasionally (mostly during a heavy load of > interrupts) > JB> tc_windup() wasn't called soon enough to update the timecounter. Making > > On my system _each_ boot causes hundreds of these messages. > And as described, long offsets without updating are caused by some > code in drivers, i.e. DELAY(1000000) in isa/fd.c. Is it nesessary to call > tc_windup() between iterations in isa_configure? ;| Yes, I know. The problem didn't occur as badly on SMP systems as the clk ithread didn't suffer from as much latency in that case, but on UP systems it could be quite bad. I used to get it both during boot and when doing things like starting up X. > JB> clock interrupts not be threaded fixes this problem. > > Oh, well, I understand now that scheduling is nesessary to be run early > because interrupts are implemented as kernel threads even when kernel > is in phase of hardware detection.;( This is not done yet. It is something that is on the todo list though (to move SI_SUB_INIT_CLOCKS earlier, basically). > /netch -- 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 Oct 6 20: 9: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR8-44.accesscable.net [24.138.8.44]) by hub.freebsd.org (Postfix) with ESMTP id 1A1C937B502 for ; Fri, 6 Oct 2000 20:09:02 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e9737jm00582 for ; Sat, 7 Oct 2000 00:07:46 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 7 Oct 2000 00:07:45 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: make -j16 world causes ffs_valloc() failure ... 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 newest source code, cvsup an hour ago or so ... if I do a build of the kernel (to enable DDB), it compiles fine. If I do a 'make -j16 world', it panic's with the following: mode = 0100600, inum = 729, fs = /tmp panic: ffs_valloc: dup alloc cpuid = 0; lapic.id = 00000000 and a DDB trace that look slike: panic() ffs_valloc() ufs_makeinode() ufs_create() ufs_vnoperate() vn_open() open() syscall() Xint0x80_syscall() Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 21:15:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43]) by hub.freebsd.org (Postfix) with ESMTP id 9F3E637B66C for ; Fri, 6 Oct 2000 21:15:27 -0700 (PDT) Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net) by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7) id 13hlOQ-00031I-00 for current@freebsd.org; Sat, 07 Oct 2000 04:15:26 +0000 Received: from [204.1.90.43] (helo=power) by dfw-mmp1.email.verio.net with smtp (Exim 3.15 #4) id 13hlOQ-00056V-00 for current@freebsd.org; Sat, 07 Oct 2000 04:15:26 +0000 From: "Tony Johnson" To: "Current@Freebsd.Org" Subject: thanks Date: Fri, 6 Oct 2000 23:15:26 -0500 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, sorry fr the mini uprising, but I guess you fixed the boot disk issue that I was having because I can now boot 1004 from boot floppies. For some reason my backup kernels couldn't boot the system fully after a cvsup, but I won't get int all that. System's up and running. Gotta make changes to my kernel file so it does SMP right but as someple have said, I will help myself. Thank you. Tony Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Oct 6 23:22:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id D70C537B502 for ; Fri, 6 Oct 2000 23:22:42 -0700 (PDT) Received: (qmail 24657 invoked from network); 7 Oct 2000 06:22:38 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 7 Oct 2000 06:22:38 -0000 Date: Sat, 7 Oct 2000 17:22:33 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Valentin Nechayev Cc: John Baldwin , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: <200010062217.BGO31522@burka.carrier.kiev.ua> 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, 7 Oct 2000, Valentin Nechayev wrote: > At Fri, 6 Oct 2000 22:00:23 +0000 (UTC), jhb wrote: > JB> tc_windup() wasn't called soon enough to update the timecounter. Making > > On my system _each_ boot causes hundreds of these messages. > And as described, long offsets without updating are caused by some > code in drivers, i.e. DELAY(1000000) in isa/fd.c. Is it nesessary to call > tc_windup() between iterations in isa_configure? ;| Not really. The timecounters overflow to bizarre values if the boot takes a long time (more than about 4 seconds), but there is no problem unless something looks at the time before tc_windup() is working and expects the time to be monotonic. Previously mi_switch() looked at the time before tc_windup() was called, and this was impossible to avoid because getting to tc_windup() involved a context switch. Now the misbehaviour should only be visible using a debugger or debugging code that prints the time. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 1:38: 1 2000 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 0AFCD37B503 for ; Sat, 7 Oct 2000 01:37:58 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13hpUS-0005Md-00; Sat, 07 Oct 2000 08:37:56 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e978N7J91531; Sat, 7 Oct 2000 10:23:07 +0200 (CEST) (envelope-from wkb) Date: Sat, 7 Oct 2000 10:23:07 +0200 From: Wilko Bulte To: Steve Kargl Cc: FreeBSD Current Subject: Re: make installkernel broken by recent manpage changes Message-ID: <20001007102307.B91198@freebie.demon.nl> References: <200010062027.e96KR8J96088@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200010062027.e96KR8J96088@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Fri, Oct 06, 2000 at 01:27:08PM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 06, 2000 at 01:27:08PM -0700, Steve Kargl wrote: > ===> joy > install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel > install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 > install: joy.8.gz: No such file or directory > *** Error code 71 Saw this 2 minutes ago too on alpha -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 4: 8:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94C2537B66D for ; Sat, 7 Oct 2000 04:08:29 -0700 (PDT) Received: from tori.COM (L0009P19.dipool.highway.telekom.at [62.46.65.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 525896E25F1 for ; Sat, 7 Oct 2000 04:08:27 -0700 (PDT) Received: (from philipp@localhost) by tori.COM (8.11.0/8.9.3) id e97B4cn06807 for freebsd-current@freebsd.org; Sat, 7 Oct 2000 13:04:38 +0200 (CEST) (envelope-from philipp) Date: Sat, 7 Oct 2000 13:04:38 +0200 From: Philipp Huber To: freebsd-current@freebsd.org Subject: downgrade? Message-ID: <20001007130438.D244@tori.mini.net> 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! is it possible to downgrade a freebsd-current installation to -stable? or is it better to reinstall the whole system? thx Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 4:13:34 2000 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 1931D37B502 for ; Sat, 7 Oct 2000 04:13:32 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e97BDTU20716; Sat, 7 Oct 2000 04:13:29 -0700 (PDT) Date: Sat, 7 Oct 2000 04:13:28 -0700 From: Alfred Perlstein To: Philipp Huber Cc: freebsd-current@FreeBSD.ORG Subject: Re: downgrade? Message-ID: <20001007041328.S272@fw.wintelcom.net> References: <20001007130438.D244@tori.mini.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001007130438.D244@tori.mini.net>; from uebs@gmx.at on Sat, Oct 07, 2000 at 01:04:38PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Philipp Huber [001007 04:08] wrote: > hi! > > is it possible to downgrade a freebsd-current installation to -stable? > or is it better to reinstall the whole system? It's possible by building a 4.x-stable system and tar'ing the /usr/src and /usr/obj over to your -current then doing several 'make -k installworld' followed by a 'make installworld' to make sure it's all been installed then by building a kernel using the "make buildkernel" method described in src/UPDATING. -- -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 Oct 7 4:22:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id B891D37B502 for ; Sat, 7 Oct 2000 04:22:12 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e97BO4h02959; Sat, 7 Oct 2000 04:24:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010071124.e97BO4h02959@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: acpi-jp@jp.freebsd.org Cc: current@freebsd.org Subject: Latest ACPICA megapatch now up Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Oct 2000 04:24:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://people.freebsd.org/~msmith/acpica-bsd-20001007.tar.gz This includes: - ACPI as PnP enumerator for ISA (there are issues here, and this doesn't disable the "real" PnPBIOS code yet, so you will get duplicates on some machines). - Power/Sleep button code (Iwasaki-san) - Improved Embedded Controller support (Watanabe-san, changed somewhat by me, not tested in changed form) - ioctl interface for compatibility with the previous codebase And probably a whole lot more that I've forgotten. Comments, suggestions, etc. welcome as usual. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 5:16:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97E0D37B66C for ; Sat, 7 Oct 2000 05:16:56 -0700 (PDT) Received: from tori.COM (L0009P19.dipool.highway.telekom.at [62.46.65.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A1E56E253C for ; Sat, 7 Oct 2000 05:16:54 -0700 (PDT) Received: (from philipp@localhost) by tori.COM (8.11.0/8.9.3) id e97Ao7F06677 for freebsd-current@freebsd.org; Sat, 7 Oct 2000 12:50:07 +0200 (CEST) (envelope-from philipp) Date: Sat, 7 Oct 2000 12:50:07 +0200 From: Philipp Huber To: freebsd-current@freebsd.org Subject: downgrade to stable? Message-ID: <20001007125007.B244@tori.mini.net> 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! is it possible to downgrade a freebsd-current installation to -stable? or is it better to reinstall the whole system? thx Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 7:35:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id CB06937B66C for ; Sat, 7 Oct 2000 07:35:37 -0700 (PDT) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id PAA37180 for current@freebsd.org; Sat, 7 Oct 2000 15:35:36 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id PAA81651 for ; Sat, 7 Oct 2000 15:30:24 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 7 Oct 2000 15:30:25 +0100 To: current@freebsd.org From: Bob Bishop Subject: Recent kernels won't boot Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Kernels built from recent cvsup (<24 hrs) quit immediately on boot, back to the BIOS, no messages no nothin'. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 7:49:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemicals.tacorp.com (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id E148637B503 for ; Sat, 7 Oct 2000 07:49:13 -0700 (PDT) Received: (from morganw@localhost) by volatile.chemicals.tacorp.com (8.11.1/8.11.1) id e97EnC935380; Sat, 7 Oct 2000 10:49:12 -0400 (EDT) (envelope-from morganw) Date: Sat, 7 Oct 2000 10:49:12 -0400 (EDT) From: Wesley Morgan To: current@freebsd.org Subject: pcmcia and ed 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 Some recent change to either the ed device or pccard support is making the kernel hiccup on my ethernet card: ed0 at port 0x300-0x31f irq 10 slot 1 on pccard1 ed0: address 00:e0:98:88:db:09, type Linksys (16 bit) module_register: module isa/ed already exists! Module isa/ed failed to register: 17 module_register: module isa/ed already exists! Module isa/ed failed to register: 17 module_register: module pccard/ed already exists! Module pccard/ed failed to register: 17 module_register: module pci/ed already exists! Module pci/ed failed to register: 17 the driver is compiled in the kernel, but it is loading the KLD anyway. Everything still functions, however. -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ wesleymorgan@home.com _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 7:59:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 8991737B503 for ; Sat, 7 Oct 2000 07:59:14 -0700 (PDT) Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157]) by btw.plaintalk.bellevue.wa.us (8.11.1/8.11.1) with ESMTP id e97Ex8P08350 for ; Sat, 7 Oct 2000 07:59:08 -0700 (PDT) Message-ID: <39DF3A3C.B46A3A32@software-munitions.com> Date: Sat, 07 Oct 2000 07:59:08 -0700 From: Dennis Glatting X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: cvs servers load Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any running load information on the CVS servers available? I'd like to adjust my pointers to help spread the load. My current pointers, for myself and two clients, is cvsup3. My location: Redmond, Washington (across lake Sammamish from the Evil Empire) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 9:25:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR8-44.accesscable.net [24.138.8.44]) by hub.freebsd.org (Postfix) with ESMTP id 9392437B503; Sat, 7 Oct 2000 09:25:34 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e97GONR03210; Sat, 7 Oct 2000 13:24:23 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 7 Oct 2000 13:24:23 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: ahc panic on <24hr kernel ... 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 source code CVSup as of early this morning, system is a dual celeron, with the following scsi controller: ahc0: port 0xc800-0xc8ff mem 0xef000000-0xef000fff irq 17 at device 13.0 on pci0 after little time after rebooting, and sped up by doing a make world, I get: --------- Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 01000000 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0131464 stack pointer = 0x10:0xcb7a3e90 frame pointer = 0x10:0xcb7a3ea0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 6 current process = 16 ( irq 17: ahc0 ) kernel: type 12 trap, code = 0 CPU1 stopping CPUs: 0x00000001... stopped Stopped at ahc_match_scb+0x18: movl 0(%esi),%eax and a trace from DDB shows: ahc_match_scb() @ +0x18 ahc_search_qinfifo @ +0xf7 ahc_freeze_devq @ +0x5d ahc_handle_seqint @ +0x135 ahc_freebsd_intr @ +0x97 ithd_loop @ +0x6f fork_trampoline @ +0x44 ------------ Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 10:19:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 51A0B37B66C for ; Sat, 7 Oct 2000 10:19:48 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA24134; Sat, 7 Oct 2000 10:19:33 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e97HJWO29176; Sat, 7 Oct 2000 10:19:32 -0700 (PDT) (envelope-from jdp) Date: Sat, 7 Oct 2000 10:19:32 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010071719.e97HJWO29176@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Cc: dennis.glatting@software-munitions.com Subject: Re: cvs servers load In-Reply-To: <39DF3A3C.B46A3A32@software-munitions.com> References: <39DF3A3C.B46A3A32@software-munitions.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <39DF3A3C.B46A3A32@software-munitions.com>, Dennis Glatting wrote: > Any running load information on the CVS servers available? Nope, sorry. > I'd like to adjust my pointers to help spread the load. My current > pointers, for myself and two clients, is cvsup3. > > My location: Redmond, Washington > (across lake Sammamish from the Evil Empire) Often the newer (higher numbered) servers are less loaded than the older ones. CVSup9.FreeBSD.org is brand new and could handle a lot more clients. It's a fast machine and it's still sitting idle most of the time. Given where you live, you might want to try cvsup7, since it is located just across Lake Washington from you in the Westin building. If you're lucky, you might be able to get to it without having your packets travel halfway across the US and back. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 10:36:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 0C38F37B66C; Sat, 7 Oct 2000 10:36:48 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA97128; Sat, 7 Oct 2000 13:36:43 -0400 (EDT) (envelope-from wollman) Date: Sat, 7 Oct 2000 13:36:43 -0400 (EDT) From: Garrett Wollman Message-Id: <200010071736.NAA97128@khavrinen.lcs.mit.edu> To: Dennis Glatting Cc: current@FreeBSD.ORG, hubs@FreeBSD.ORG Subject: cvs servers load In-Reply-To: <39DF3A3C.B46A3A32@software-munitions.com> References: <39DF3A3C.B46A3A32@software-munitions.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Any running load information on the CVS servers available? I keep stats for cvsup3 (thanks to cricket and ucd-snmp). cvsup3 peaks out in the early morning with a five-minute load between 12 and 17. Rarely does the load average get below 2. Cvsup3's swap utilization hovers around 200 MB most of the day, and exceeds 300 MB during that peak. For all that, it's still only pushing about 4 Mbit/s peak -- or about an eighth what rpmfind.net does six floor-tiles away. I was hoping to replace it this year, but the money got pushed out of the budget. (Run machines into the ground, we do! I still maintain some services running on a seven-year-old Sparc IPX.) If anyone has half a gig of memory (4 x 128M or 8 x 64M) for an Intel BB440FX and would like a tax deduction.... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 10:39:24 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 7A5A037B66D; Sat, 7 Oct 2000 10:39:19 -0700 (PDT) Date: Sat, 7 Oct 2000 10:39:19 -0700 From: John DeBoskey To: Current List Subject: ccd causing page fault in kernel Message-ID: <20001007103919.A60611@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I don't have alot of information to provide yet on this yet. The fault information scrolls off the top of the console... I have /usr/obj mounted on a ccd. Less then 2 minutes into a make world, the console shows a ccd problem, error 5. Page fault in the kernel. The above problem is repeatable (but the machine is not infront of me right now). I unmounted the /usr/obj ccd filesystem, and am running a make world onto the /usr system which is not a ccd and things seem to work fine (so far). It may be monday before I can get a kernel rebuilt with the debugger enabled. This is a single processor machine, UP kernel, sources current as of 11:30am EST. No error information is written to syslog. -John -- dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Oct 7 11:39:55 EDT 2000 toor@FreeBSD.xxx.xxx.com:/usr/src/sys/compile/FreeBSD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 548627644 Hz CPU: Pentium III/Pentium III Xeon/Celeron (548.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 402653184 (393216K bytes) avail memory = 387346432 (378268K bytes) Preloaded elf kernel "kernel" at 0xc03f6000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled md0: Malloc disk 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 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 atapci0: Busmastering DMA enabled ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xdce0-0xdcff irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 ahc0: port 0xd800-0xd8ff mem 0xff002000-0xff002fff irq 10 at device 13.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xd400-0xd4ff mem 0xff001000-0xff001fff irq 9 at device 14.0 on pci0 aic7895: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc2: port 0xd000-0xd0ff mem 0xff000000-0xff000fff irq 11 at device 14.1 on pci0 aic7895: Single Channel B, SCSI Id=7, 32/255 SCBs pcib2: at device 15.0 on pci0 pci2: on pcib2 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xdc00-0xdc7f mem 0xff003000-0xff00307f irq 11 at device 17.0 on pci0 xl0: Ethernet address: 00:b0:d0:25:67:2a 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 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, 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 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 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 ad0: 19473MB [39566/16/63] at ata0-master UDMA33 ad1: 12416MB [25228/16/63] at ata0-slave UDMA33 acd0: CDROM at ata1-master using UDMA33 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da2 at ahc0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) cd0 at ahc2 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 11: 3:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3158937B502 for ; Sat, 7 Oct 2000 11:03:19 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e97I3Gd00944; Sat, 7 Oct 2000 12:03:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA01359; Sat, 7 Oct 2000 12:03:15 -0600 (MDT) Message-Id: <200010071803.MAA01359@harmony.village.org> To: Wesley Morgan Subject: Re: pcmcia and ed Cc: current@FreeBSD.org In-reply-to: Your message of "Sat, 07 Oct 2000 10:49:12 EDT." References: Date: Sat, 07 Oct 2000 12:03:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Wesley Morgan writes: : Some recent change to either the ed device or pccard support is making the : kernel hiccup on my ethernet card: : : ed0 at port 0x300-0x31f irq 10 slot 1 on pccard1 : ed0: address 00:e0:98:88:db:09, type Linksys (16 bit) : module_register: module isa/ed already exists! : Module isa/ed failed to register: 17 : module_register: module isa/ed already exists! : Module isa/ed failed to register: 17 : module_register: module pccard/ed already exists! : Module pccard/ed failed to register: 17 : module_register: module pci/ed already exists! : Module pci/ed failed to register: 17 : : the driver is compiled in the kernel, but it is loading the KLD : anyway. Everything still functions, however. The module name should be if_ed. I'll go fix it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 11: 4:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 63EA037B66C for ; Sat, 7 Oct 2000 11:04:17 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e97I4Fd00953; Sat, 7 Oct 2000 12:04:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA01379; Sat, 7 Oct 2000 12:04:15 -0600 (MDT) Message-Id: <200010071804.MAA01379@harmony.village.org> To: Philipp Huber Subject: Re: downgrade to stable? Cc: freebsd-current@FreeBSD.org In-reply-to: Your message of "Sat, 07 Oct 2000 12:50:07 +0200." <20001007125007.B244@tori.mini.net> References: <20001007125007.B244@tori.mini.net> Date: Sat, 07 Oct 2000 12:04:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001007125007.B244@tori.mini.net> Philipp Huber writes: : is it possible to downgrade a freebsd-current installation to -stable? : or is it better to reinstall the whole system? Yes. However, it is tricky and not for the feign of heart. It involves doing an install world onto the system, rebooting the stable kernel and then looking for libraries that are too new. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 11:17:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 615CA37B503 for ; Sat, 7 Oct 2000 11:17:56 -0700 (PDT) Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157]) by btw.plaintalk.bellevue.wa.us (8.11.1/8.11.1) with ESMTP id e97IHtP10111 for ; Sat, 7 Oct 2000 11:17:55 -0700 (PDT) Message-ID: <39DF68D3.E3D6379C@software-munitions.com> Date: Sat, 07 Oct 2000 11:17:55 -0700 From: Dennis Glatting X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: cvs servers load References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup7 is indeed closer. Thanks. jdp@polstra.com wrote: > = > In article <39DF3A3C.B46A3A32@software-munitions.com>, Dennis Glatting > wrote: > = > > Any running load information on the CVS servers available? > = > Nope, sorry. > = > > I'd like to adjust my pointers to help spread the load. My current > > pointers, for myself and two clients, is cvsup3. > > > > My location: Redmond, Washington > > (across lake Sammamish from the Evil Empire) > = > Often the newer (higher numbered) servers are less loaded than the > older ones. CVSup9.FreeBSD.org is brand new and could handle a lot > more clients. It's a fast machine and it's still sitting idle most > of the time. Given where you live, you might want to try cvsup7, > since it is located just across Lake Washington from you in the Westin > building. If you're lucky, you might be able to get to it without > having your packets travel halfway across the US and back. > = > John > -- > John Polstra jdp@polstr= a.com > John D. Polstra & Co., Inc. Seattle, Washingto= n USA > "Disappointment is a good sign of basic intelligence." -- Ch=F6gyam = Trungpa -- = Dennis Glatting Copyright (c) 2000 Software Munitions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 11:38:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id B26CE37B678 for ; Sat, 7 Oct 2000 11:38:36 -0700 (PDT) Received: (qmail 66412 invoked by uid 1000); 7 Oct 2000 18:38:35 -0000 Date: Sat, 7 Oct 2000 20:38:35 +0200 From: "Karsten W. Rohrbach" To: Garrett Wollman Cc: Dennis Glatting , current@FreeBSD.ORG, hubs@FreeBSD.ORG Subject: Re: cvs servers load Message-ID: <20001007203835.D66128@rohrbach.de> Reply-To: karsten@rohrbach.de References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071736.NAA97128@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200010071736.NAA97128@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Sat, Oct 07, 2000 at 01:36:43PM -0400 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if somebody knows the doodads and pitfalls in linux cvs in conjuction with cvsupd and is able to tell me what goes wrong, i could get the cvsupd on filepile running. at the moment i got a somewhat borken repository which might come from the linux ccvs. i do not know very much about cvsup's interoperation with cvs but apparently something goes really wrong on that box :-/ if we could get that box running we would have a high volume euro cvsup repo in place. (at the moment the box runs at about 30 to 50mbit/s 24x7 with peaks at 17:00 local time with less that 10% cpu consumption and a load far below 1, normally around 0.30) no flames please, this box is running on linux due to driver support for the hardware no more no less. /k Garrett Wollman(wollman@khavrinen.lcs.mit.edu)@Sat, Oct 07, 2000 at 01:36:43PM -0400: > < said: > > > Any running load information on the CVS servers available? > > I keep stats for cvsup3 (thanks to cricket and ucd-snmp). cvsup3 > peaks out in the early morning with a five-minute load between 12 and > 17. Rarely does the load average get below 2. Cvsup3's swap > utilization hovers around 200 MB most of the day, and exceeds 300 MB > during that peak. For all that, it's still only pushing about 4 > Mbit/s peak -- or about an eighth what rpmfind.net does six > floor-tiles away. > > I was hoping to replace it this year, but the money got pushed out of > the budget. (Run machines into the ground, we do! I still maintain > some services running on a seven-year-old Sparc IPX.) > > If anyone has half a gig of memory (4 x 128M or 8 x 64M) for an Intel > BB440FX and would like a tax deduction.... > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- > cd /pub; more beer KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 11:42:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id F27AC37B503; Sat, 7 Oct 2000 11:42:40 -0700 (PDT) Received: from silvia.hip.berkeley.edu (sji-ca7-112.ix.netcom.com [209.109.235.112]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id OAA10604; Sat, 7 Oct 2000 14:42:36 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.11.0/8.11.0) id e97IgYi77657; Sat, 7 Oct 2000 11:42:34 -0700 (PDT) (envelope-from asami) To: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: cvs commit: CVSROOT avail References: <200010071839.LAA35413@freefall.freebsd.org> From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 07 Oct 2000 11:42:30 -0700 In-Reply-To: Satoshi Asami's message of "Sat, 7 Oct 2000 11:39:58 -0700 (PDT)" Message-ID: Lines: 18 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll post another message when I'm done. -PW --- From: Satoshi Asami Date: Sat, 7 Oct 2000 11:39:58 -0700 (PDT) X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-committers@FreeBSD.org asami 2000/10/07 11:39:58 PDT Modified files: . avail Log: The ports tree is now locked for the layout change. Revision Changes Path 1.127 +2 -2 CVSROOT/avail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 11:56:11 2000 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 F274F37B66D for ; Sat, 7 Oct 2000 11:56:07 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA73922 for current@freebsd.org; Sat, 7 Oct 2000 11:56:07 -0700 (PDT) (envelope-from obrien) Date: Sat, 7 Oct 2000 11:56:07 -0700 From: "David O'Brien" To: current@freebsd.org Subject: Re: cvs servers load Message-ID: <20001007115607.A73312@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010071719.e97HJWO29176@vashon.polstra.com>; from jdp@polstra.com on Sat, Oct 07, 2000 at 10:19:32AM -0700 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 Sat, Oct 07, 2000 at 10:19:32AM -0700, jdp@polstra.com wrote: > of the time. Given where you live, you might want to try cvsup7, Hey! That's the one I use -- don't tell anyone about it. :-))) Where is cvsup8? I get the fastest ping times to it. A traceroute implies it is also in Seatle, WA. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 12: 0:31 2000 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 1D46A37B502 for ; Sat, 7 Oct 2000 12:00:28 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA84911; Sat, 7 Oct 2000 12:00:14 -0700 (PDT) (envelope-from obrien) Date: Sat, 7 Oct 2000 12:00:13 -0700 From: "David O'Brien" To: Warner Losh Cc: freebsd-current@FreeBSD.org Subject: Re: downgrade to stable? Message-ID: <20001007120013.C73312@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20001007125007.B244@tori.mini.net> <200010071804.MAA01379@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: <200010071804.MAA01379@harmony.village.org>; from imp@village.org on Sat, Oct 07, 2000 at 12:04:15PM -0600 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 Sat, Oct 07, 2000 at 12:04:15PM -0600, Warner Losh wrote: > and then looking for libraries that are too new. Would one not want to keep the libraries that are too new for things in /usr/local that would need them. Since the shlib symlink will be for the "older" lib, there really isn't any problem having too new ones present. -- -- David (obrien@FreeBSD.org) Gnu is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 12: 5:25 2000 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 11EFB37B502 for ; Sat, 7 Oct 2000 12:05:22 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA94592; Sat, 7 Oct 2000 12:05:11 -0700 (PDT) (envelope-from obrien) Date: Sat, 7 Oct 2000 12:05:10 -0700 From: "David O'Brien" To: Steve Kargl Cc: FreeBSD Current Subject: Re: make installkernel broken by recent manpage changes Message-ID: <20001007120510.E73312@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200010062027.e96KR8J96088@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010062027.e96KR8J96088@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Fri, Oct 06, 2000 at 01:27:08PM -0700 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 Fri, Oct 06, 2000 at 01:27:08PM -0700, Steve Kargl wrote: > ===> joy > install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel > install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 > install: joy.8.gz: No such file or directory > *** Error code 71 I'll check it out. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 12:10:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id A797C37B502 for ; Sat, 7 Oct 2000 12:10:53 -0700 (PDT) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id XAA62236; Sat, 7 Oct 2000 23:10:50 +0400 (MSD) From: Igor Timkin Message-Id: <200010071910.XAA62236@logger.gamma.ru> Subject: Re: Recent kernels won't boot In-Reply-To: "from Bob Bishop at Oct 7, 2000 03:30:25 pm" To: Bob Bishop Date: Sat, 7 Oct 2000 23:10:50 +0400 (MSD) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't any problem: ivt@ivthome:/home/ivt:3:306>uname -a FreeBSD ivthome.gamma.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Oct 7 13:09:54 MSD 2000 ivt@ivthome.gamma.ru:/usr/src/sys/compile/IVTHOME i386 > Hi, > > Kernels built from recent cvsup (<24 hrs) quit immediately on boot, back to > the BIOS, no messages no nothin'. > > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 > > > > > 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 Sat Oct 7 12:14:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay1.inwind.it (relay1.inwind.it [212.141.53.67]) by hub.freebsd.org (Postfix) with ESMTP id 649B337B66C for ; Sat, 7 Oct 2000 12:14:41 -0700 (PDT) Received: from bartequi.ottodomain.org (62.98.162.211) by relay1.inwind.it (5.1.046) id 39DD783D0002E29C; Sat, 7 Oct 2000 21:14:30 +0200 From: Salvo Bartolotta Date: Sat, 07 Oct 2000 20:15:28 GMT Message-ID: <20001007.20152800@bartequi.ottodomain.org> Subject: Re: downgrade? To: Alfred Perlstein Cc: Philipp Huber , freebsd-current@FreeBSD.ORG In-Reply-To: <20001007041328.S272@fw.wintelcom.net> References: <20001007130438.D244@tori.mini.net> <20001007041328.S272@fw.wintelcom.net> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 10/7/00, 12:13:28 PM, Alfred Perlstein wrote=20 regarding Re: downgrade?: > * Philipp Huber [001007 04:08] wrote: > > hi! > > > > is it possible to downgrade a freebsd-current installation to -stabl= e? > > or is it better to reinstall the whole system? > It's possible by building a 4.x-stable system and tar'ing the > /usr/src and /usr/obj over to your -current then doing several > 'make -k installworld' followed by a 'make installworld' to make > sure it's all been installed then by building a kernel using the > "make buildkernel" method described in src/UPDATING. > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." Dear Alfred Perlstein, =20 From the posts I have been reading, I seem to understand that the=20 following may apply (depending on the divergence/relationship between=20 -CURRENT and -STABLE): -- It may be necessary to downgrade the toolchain (e.g. binutils;=20 gcc); -- It may be necessary to downgrade "script"utils (ie perl). Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 12:42:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 4EE7537B503; Sat, 7 Oct 2000 12:42:38 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13hzrg-0002XQ-00; Sat, 07 Oct 2000 19:42:36 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e97JidG93307; Sat, 7 Oct 2000 21:44:39 +0200 (CEST) (envelope-from wkb) Date: Sat, 7 Oct 2000 21:44:39 +0200 From: Wilko Bulte To: "David O'Brien" Cc: current@freebsd.org Subject: Re: cvs servers load Message-ID: <20001007214439.D93146@freebie.demon.nl> References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001007115607.A73312@dragon.nuxi.com>; from obrien@freebsd.org on Sat, Oct 07, 2000 at 11:56:07AM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 07, 2000 at 11:56:07AM -0700, David O'Brien wrote: > On Sat, Oct 07, 2000 at 10:19:32AM -0700, jdp@polstra.com wrote: > > of the time. Given where you live, you might want to try cvsup7, > > Hey! That's the one I use -- don't tell anyone about it. :-))) > > Where is cvsup8? I get the fastest ping times to it. A traceroute > implies it is also in Seatle, WA. Time to put the cvsup servers on the map with ICBM coordinates maybe? -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 13:18:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id E42F137B66C; Sat, 7 Oct 2000 13:18:24 -0700 (PDT) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id 0383A287; Sat, 7 Oct 2000 16:18:19 -0400 (EDT) Received: (from jon@localhost) by fury.csh.rit.edu (8.9.3+Sun/8.9.1) id QAA16581; Sat, 7 Oct 2000 16:17:45 -0400 (EDT) Date: Sat, 7 Oct 2000 16:17:45 -0400 From: Jon Parise To: Wilko Bulte Cc: "David O'Brien" , current@freebsd.org Subject: Re: cvs servers load Message-ID: <20001007161744.A16521@csh.rit.edu> Mail-Followup-To: Wilko Bulte , David O'Brien , current@freebsd.org References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> <20001007214439.D93146@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001007214439.D93146@freebie.demon.nl>; from wkb@freebie.demon.nl on Sat, Oct 07, 2000 at 09:44:39PM +0200 X-Operating-System: SunOS 5.7 (sun4u) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 07, 2000 at 09:44:39PM +0200, Wilko Bulte wrote: > Time to put the cvsup servers on the map with ICBM coordinates maybe? I think that would actually be quite useful (or, at the very least, purely informative). -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 13:23:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 5422637B503; Sat, 7 Oct 2000 13:23:15 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 875271C6A; Sat, 7 Oct 2000 16:22:59 -0400 (EDT) Date: Sat, 7 Oct 2000 16:22:59 -0400 From: Bill Fumerola To: Jon Parise Cc: Wilko Bulte , David O'Brien , current@freebsd.org Subject: Re: cvs servers load Message-ID: <20001007162259.P38472@jade.chc-chimes.com> References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> <20001007214439.D93146@freebie.demon.nl> <20001007161744.A16521@csh.rit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20001007161744.A16521@csh.rit.edu>; from jon@csh.rit.edu on Sat, Oct 07, 2000 at 04:17:45PM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 07, 2000 at 04:17:45PM -0400, Jon Parise wrote: > > Time to put the cvsup servers on the map with ICBM coordinates maybe? > > I think that would actually be quite useful (or, at the very least, > purely informative). I've often thought it would be neat if in sysinstall the ftpX.freebsd.org mentioned next to it which provider the mirror site [primarily] used or at least the name of the entity that was hosting it. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 15:27:55 2000 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 AE0DC37B502 for ; Sat, 7 Oct 2000 15:27:53 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e97MRoV05952; Sat, 7 Oct 2000 15:27:50 -0700 (PDT) Date: Sat, 7 Oct 2000 15:27:50 -0700 From: Alfred Perlstein To: Salvo Bartolotta Cc: Philipp Huber , freebsd-current@FreeBSD.ORG Subject: Re: downgrade? Message-ID: <20001007152749.Z272@fw.wintelcom.net> References: <20001007130438.D244@tori.mini.net> <20001007041328.S272@fw.wintelcom.net> <20001007.20152800@bartequi.ottodomain.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001007.20152800@bartequi.ottodomain.org>; from bartequi@inwind.it on Sat, Oct 07, 2000 at 08:15:28PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Salvo Bartolotta [001007 12:14] wrote: > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > > On 10/7/00, 12:13:28 PM, Alfred Perlstein wrote > regarding Re: downgrade?: > > > > * Philipp Huber [001007 04:08] wrote: > > > hi! > > > > > > is it possible to downgrade a freebsd-current installation to -stable? > > > or is it better to reinstall the whole system? > > > It's possible by building a 4.x-stable system and tar'ing the > > /usr/src and /usr/obj over to your -current then doing several > > 'make -k installworld' followed by a 'make installworld' to make > > sure it's all been installed then by building a kernel using the > > "make buildkernel" method described in src/UPDATING. > > > -- > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > "I have the heart of a child; I keep it in a jar on my desk." > > > > Dear Alfred Perlstein, > > > > >From the posts I have been reading, I seem to understand that the > following may apply (depending on the divergence/relationship between > -CURRENT and -STABLE): > > -- It may be necessary to downgrade the toolchain (e.g. binutils; > gcc); > -- It may be necessary to downgrade "script"utils (ie perl). > > Yes you're correct there will be problems with perl, that's why you need a 4.x machine to do the building on and that's also why you may need several 'make -k installworld' runs to finally get a 'make installworld' to 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 Sat Oct 7 15:34:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from krycek.zoominternet.net (krycek.zoominternet.net [63.67.120.9]) by hub.freebsd.org (Postfix) with SMTP id 8122737B66C for ; Sat, 7 Oct 2000 15:34:18 -0700 (PDT) Received: (qmail 30489 invoked from network); 7 Oct 2000 22:34:15 -0000 Received: from lcm243.cvzoom.net (208.230.69.243) by krycek.zoominternet.net with SMTP; 7 Oct 2000 22:34:15 -0000 Date: Sat, 7 Oct 2000 18:34:16 -0400 (EDT) From: Donn Miller To: Alfred Perlstein Cc: Salvo Bartolotta , Philipp Huber , freebsd-current@FreeBSD.ORG Subject: Re: downgrade? In-Reply-To: <20001007152749.Z272@fw.wintelcom.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 Sat, 7 Oct 2000, Alfred Perlstein wrote: > Yes you're correct there will be problems with perl, that's > why you need a 4.x machine to do the building on and that's also > why you may need several 'make -k installworld' runs to finally > get a 'make installworld' to work. How about: sh -c "while true ; do make -k installworld && break ; done" Would this work? This is assuming that make -k returns a success (0) error code when there are no errors. Does make -k return an error code when the last command in the Makefile is successful, even if there are errors? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 17:39:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay1.inwind.it (relay1.inwind.it [212.141.53.67]) by hub.freebsd.org (Postfix) with ESMTP id 909FB37B502 for ; Sat, 7 Oct 2000 17:39:42 -0700 (PDT) Received: from bartequi.ottodomain.org (62.98.162.217) by relay1.inwind.it (5.1.046) id 39DD783D0003343A; Sun, 8 Oct 2000 02:39:33 +0200 From: Salvo Bartolotta Date: Sun, 08 Oct 2000 01:40:29 GMT Message-ID: <20001008.1402900@bartequi.ottodomain.org> Subject: Re: downgrade? To: Alfred Perlstein Cc: Philipp Huber , freebsd-current@FreeBSD.ORG References: X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Dear Alfred Perlstein, > > > > > > > > >From the posts I have been reading, I seem to understand that the > > following may apply (depending on the divergence/relationship betwee= n > > -CURRENT and -STABLE): > > > > -- It may be necessary to downgrade the toolchain (e.g. binutils; > > gcc); > > -- It may be necessary to downgrade "script"utils (ie perl). > > > > > Yes you're correct there will be problems with perl, that's > why you need a 4.x machine to do the building on and that's also > why you may need several 'make -k installworld' runs to finally > get a 'make installworld' to work. Oooops, I had another problem in mind. I thought of the theoretical general problem of downgrading a -CURRENT machine in a "self-consistent" fashion (ie on the same machine). I haven't done that (so far), so I am not aware of any [other] unwanted side-effects. AFAIR, a few weeks ago, someone performed such an operation (in the first week of August or so); I read several posts about the matter. If somebody has successfully tried such an operation recently (on a PRE_SMPNG machine), s/he will be able to help Phillip. Anyway, your suggestion sounds safer. Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 17:52:27 2000 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 7263937B503 for ; Sat, 7 Oct 2000 17:52:24 -0700 (PDT) Received: by peorth.iteration.net (Postfix, from userid 1001) id 0D49E5730B; Sat, 7 Oct 2000 19:52:43 -0500 (CDT) Date: Sat, 7 Oct 2000 19:52:43 -0500 From: "Michael C . Wu" To: Bob Bishop Cc: current@freebsd.org Subject: Re: Recent kernels won't boot Message-ID: <20001007195242.C45189@peorth.iteration.net> Reply-To: "Michael C . Wu" 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 rb@gid.co.uk on Sat, Oct 07, 2000 at 03:30:25PM +0100 X-FreeBSD-Header: This is a subliminal message from the vast FreeBSD conspiracy project. X-Operating-System: FreeBSD peorth.iteration.net 4.1.1-RELEASE FreeBSD 4.1.1-RELEASE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 07, 2000 at 03:30:25PM +0100, Bob Bishop scribbled: | Kernels built from recent cvsup (<24 hrs) quit immediately on boot, back to | the BIOS, no messages no nothin'. Try removing the ACPI options in kernel and apply Mike Smith's latest ACPI megapatches. Please also include info on your hardware/BIOS when your system cannot boot like your situation. -- +------------------------------------------------------------------+ | 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 Sat Oct 7 18: 3:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 9660637B502 for ; Sat, 7 Oct 2000 18:03:13 -0700 (PDT) Received: (qmail 71076 invoked by uid 100); 8 Oct 2000 01:03:12 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14815.51152.842361.329859@guru.mired.org> Date: Sat, 7 Oct 2000 20:03:12 -0500 (CDT) To: current@freebsd.org Subject: sio problems? X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently got my digital camera back out, and started pulling the old pictures from it. I noticed something I hadn't ever seen before - silo overflows from the sio port. At the moment, I'm wondering if this is a known problem that is being investigated (SMPNG comes to mind), or something new. Thanx, ; Sat, 7 Oct 2000 19:10:40 -0700 (PDT) Received: from localhost (scrappy@localhost) by hub.org (8.10.1/8.10.1) with ESMTP id e982Adn10205 for ; Sat, 7 Oct 2000 22:10:39 -0400 (EDT) Date: Sat, 7 Oct 2000 22:10:39 -0400 (EDT) From: "Marc G. Fournier" To: freebsd-current@freebsd.org Subject: latest ahc panic, more data ... 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 okay, have been watching the conversation going on in the committers list, and am watching for any new commits that seem appropriate, but figure adding a little bit of extra info as I come up with it might help? latest reboot had a bit more info then the last, and started with: ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x73 scb(147) ach0: WARNING no command for scb 147 (cmdcmplt) QOUTPOS=132 Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 19:54:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 9A63E37B502; Sat, 7 Oct 2000 19:54:23 -0700 (PDT) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G2300L0EC2M4O@field.videotron.net>; Sat, 7 Oct 2000 22:54:22 -0400 (EDT) Date: Sat, 07 Oct 2000 22:58:20 -0400 (EDT) From: Bosko Milekic Subject: Re: latest ahc panic, more data ... In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: gibbs@freebsd.org Cc: freebsd-current@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 I've just been hit by one such problem on bootup. This is -current as of today, so I suspect it's the commits that went in the past two days. Basically, I tracked it down just enough to know that the problem is happening during a call to ahc_print_path() in aic7xxx.c, specifically for me, this happens during bootup in ahc_handle_scsiint() right after the second call to ahc_abort_scbs(). ahc_print_path() is called like this: ahc_print_path(ahc, scb); (why both ahc and scb are being passed, I have no idea, since ahc_print_path only actually makes use of scb). For the unaware, ahc_print_path() seems to only wrap a call to xpt_print_path() to which it passes scb->io_ctx->ccb_h.path as an argument, and in this case, scb->io_ctx happens to be NULL, so during its pass, a NULL pointer gets dereferenced and the page fault happens. The NULLing out of this is coming somewhere in ahc_handle_scsiint(), because some prior ahc_print_path()s (with the same arguments) are succeeding. I have not tried backing out the changes from the past two days and trying again, but this was not happening a week ago. So what's going on here? On Sat, 7 Oct 2000, Marc G. Fournier wrote: > > okay, have been watching the conversation going on in the committers list, > and am watching for any new commits that seem appropriate, but figure > adding a little bit of extra info as I come up with it might help? > > latest reboot had a bit more info then the last, and started with: > > ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x73 scb(147) > ach0: WARNING no command for scb 147 (cmdcmplt) > QOUTPOS=132 > > Marc G. Fournier scrappy@hub.org > Systems Administrator @ hub.org > scrappy@{postgresql|isc}.org ICQ#7615664 Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 20: 7:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from hub.org (hub.org [216.126.84.1]) by hub.freebsd.org (Postfix) with ESMTP id D4B0837B503; Sat, 7 Oct 2000 20:07:06 -0700 (PDT) Received: from localhost (scrappy@localhost) by hub.org (8.10.1/8.10.1) with ESMTP id e9836tw20183; Sat, 7 Oct 2000 23:07:05 -0400 (EDT) Date: Sat, 7 Oct 2000 23:06:55 -0400 (EDT) From: "Marc G. Fournier" To: Bosko Milekic Cc: gibbs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: latest ahc panic, more data ... 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 there is a thread going on in committers that appears to revolve aroudn this issue, and Justin has been throwing out patches, so it is being worked on "fast and furious" ... I'm currently up in Windows (Dual-Boot machine fo rmy little girl) watching for a physical commit to the repository that at least suggestions its a fix before rebooting and upgrading :) On Sat, 7 Oct 2000, Bosko Milekic wrote: > > I've just been hit by one such problem on bootup. This is -current as of > today, so I suspect it's the commits that went in the past two days. > > Basically, I tracked it down just enough to know that the problem is > happening during a call to ahc_print_path() in aic7xxx.c, specifically > for me, this happens during bootup in ahc_handle_scsiint() right after > the second call to ahc_abort_scbs(). > > ahc_print_path() is called like this: > > ahc_print_path(ahc, scb); > > (why both ahc and scb are being passed, I have no idea, since > ahc_print_path only actually makes use of scb). > > For the unaware, ahc_print_path() seems to only wrap a call to > xpt_print_path() to which it passes scb->io_ctx->ccb_h.path as an > argument, and in this case, scb->io_ctx happens to be NULL, so during its > pass, a NULL pointer gets dereferenced and the page fault happens. > > The NULLing out of this is coming somewhere in ahc_handle_scsiint(), > because some prior ahc_print_path()s (with the same arguments) are > succeeding. > > I have not tried backing out the changes from the past two days and > trying again, but this was not happening a week ago. > > So what's going on here? > > On Sat, 7 Oct 2000, Marc G. Fournier wrote: > > > > > okay, have been watching the conversation going on in the committers list, > > and am watching for any new commits that seem appropriate, but figure > > adding a little bit of extra info as I come up with it might help? > > > > latest reboot had a bit more info then the last, and started with: > > > > ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x73 scb(147) > > ach0: WARNING no command for scb 147 (cmdcmplt) > > QOUTPOS=132 > > > > Marc G. Fournier scrappy@hub.org > > Systems Administrator @ hub.org > > scrappy@{postgresql|isc}.org ICQ#7615664 > > > > Bosko Milekic > bmilekic@technokratis.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 21:15: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from ego.mind.net (ego.mind.net [206.99.66.9]) by hub.freebsd.org (Postfix) with ESMTP id D6BC437B502; Sat, 7 Oct 2000 21:14:58 -0700 (PDT) Received: from takhus-home.ashlandfn.org (AFN-Dyn-6315110844.pc.ashlandfiber.net [63.151.108.44]) by ego.mind.net (8.9.3/8.9.3) with ESMTP id VAA24398; Sat, 7 Oct 2000 21:14:58 -0700 Received: from localhost (fleisher@localhost) by takhus-home.ashlandfn.org (8.11.1/8.11.1) with ESMTP id e97NeZu00340; Sat, 7 Oct 2000 16:40:35 -0700 (PDT) (envelope-from takhus@takhus.mind.net) X-Authentication-Warning: takhus-home.ashlandfn.org: fleisher owned process doing -bs Date: Sat, 7 Oct 2000 16:40:35 -0700 (PDT) From: Tony Fleisher X-Sender: fleisher@takhus-home.ashlandfn.org To: "David O'Brien" Cc: Steve Kargl , FreeBSD Current Subject: Re: make installkernel broken by recent manpage changes In-Reply-To: <20001007120510.E73312@dragon.nuxi.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 I just ran through this myself trying to update to newest -current. I am not exactly sure what caused the breakage (perhaps some changes inthe share/mk/* files?), nor what the "proper" fix is, however I was able to get the kernel to install properly by adding NOMANCOMPRESS=true in the following Makefiles: sys/modules/{ibcs2,joy,linux,osf1,svr4}/Makefile I suspect that more people haven't noticed this because they have NOMANCOMPRESS defined in /etc/make.conf or their environment. Regards, TOny. On Sat, 7 Oct 2000, David O'Brien wrote: > On Fri, Oct 06, 2000 at 01:27:08PM -0700, Steve Kargl wrote: > > ===> joy > > install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel > > install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 > > install: joy.8.gz: No such file or directory > > *** Error code 71 > > I'll check it out. > > -- > -- David (obrien@FreeBSD.org) > > > 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 Sat Oct 7 21:16:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from ego.mind.net (ego.mind.net [206.99.66.9]) by hub.freebsd.org (Postfix) with ESMTP id DF69D37B503; Sat, 7 Oct 2000 21:16:29 -0700 (PDT) Received: from takhus-home.ashlandfn.org (AFN-Dyn-6315110844.pc.ashlandfiber.net [63.151.108.44]) by ego.mind.net (8.9.3/8.9.3) with ESMTP id VAA24624; Sat, 7 Oct 2000 21:16:29 -0700 Received: from localhost (fleisher@localhost) by takhus-home.ashlandfn.org (8.11.1/8.11.1) with ESMTP id e984GSk45119; Sat, 7 Oct 2000 21:16:28 -0700 (PDT) (envelope-from takhus@takhus.mind.net) X-Authentication-Warning: takhus-home.ashlandfn.org: fleisher owned process doing -bs Date: Sat, 7 Oct 2000 21:16:28 -0700 (PDT) From: Tony Fleisher X-Sender: fleisher@takhus-home.ashlandfn.org To: "David O'Brien" Cc: Steve Kargl , FreeBSD Current Subject: Re: make installkernel broken by recent manpage changes (fwd) 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 just ran through this myself trying to update to newest -current. I am not exactly sure what caused the breakage (perhaps some changes inthe share/mk/* files?), nor what the "proper" fix is, however I was able to get the kernel to install properly by adding NOMANCOMPRESS=true in the following Makefiles: sys/modules/{ibcs2,joy,linux,osf1,svr4}/Makefile I suspect that more people haven't noticed this because they have NOMANCOMPRESS defined in /etc/make.conf or their environment. Regards, TOny. On Sat, 7 Oct 2000, David O'Brien wrote: > On Fri, Oct 06, 2000 at 01:27:08PM -0700, Steve Kargl wrote: > > ===> joy > > install -C -c -o root -g wheel -m 555 joy.ko /boot/kernel > > install -C -c -o root -g wheel -m 444 joy.8.gz /usr/share/man/man8 > > install: joy.8.gz: No such file or directory > > *** Error code 71 > > I'll check it out. > > -- > -- David (obrien@FreeBSD.org) > > > 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 Sat Oct 7 22:49: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 2114E37B66C; Sat, 7 Oct 2000 22:49:03 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13i9Ur-0000NM-00; Sat, 07 Oct 2000 23:59:41 -0600 Message-ID: <39E00D4D.A9EE1D8@softweyr.com> Date: Sat, 07 Oct 2000 23:59:41 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: David O'Brien , current@freebsd.org Subject: Re: cvs servers load References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> <20001007214439.D93146@freebie.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > On Sat, Oct 07, 2000 at 11:56:07AM -0700, David O'Brien wrote: > > On Sat, Oct 07, 2000 at 10:19:32AM -0700, jdp@polstra.com wrote: > > > of the time. Given where you live, you might want to try cvsup7, > > > > Hey! That's the one I use -- don't tell anyone about it. :-))) > > > > Where is cvsup8? I get the fastest ping times to it. A traceroute > > implies it is also in Seatle, WA. > > Time to put the cvsup servers on the map with ICBM coordinates maybe? . o O I feel another Xearth markers file coming. ftp servers, cvsup servers, www servers, etc? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Oct 7 22:53:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 51E4337B502; Sat, 7 Oct 2000 22:53:49 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 79CFB1C69; Sun, 8 Oct 2000 01:53:36 -0400 (EDT) Date: Sun, 8 Oct 2000 01:53:36 -0400 From: Bill Fumerola To: Wes Peters Cc: Wilko Bulte , David O'Brien , current@freebsd.org Subject: Re: cvs servers load Message-ID: <20001008015336.W38472@jade.chc-chimes.com> References: <39DF3A3C.B46A3A32@software-munitions.com> <200010071719.e97HJWO29176@vashon.polstra.com> <20001007115607.A73312@dragon.nuxi.com> <20001007214439.D93146@freebie.demon.nl> <39E00D4D.A9EE1D8@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39E00D4D.A9EE1D8@softweyr.com>; from wes@softweyr.com on Sat, Oct 07, 2000 at 11:59:41PM -0600 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 07, 2000 at 11:59:41PM -0600, Wes Peters wrote: > . o O I feel another Xearth markers file coming. ftp servers, cvsup > servers, www servers, etc? -rw-r--r-- 1 billf ncvs 2398 May 7 15:23 /usr/ports/astro/xearth/files/freebsd.ftp.markers -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message