From owner-freebsd-current Sun Oct 31 1: 6:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (Postfix) with ESMTP id 89F4C14C20; Sun, 31 Oct 1999 01:06:31 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (silvia [209.109.233.59]) by vader.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id BAA16487; Sun, 31 Oct 1999 01:05:19 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id BAA23878; Sun, 31 Oct 1999 01:05:15 -0800 (PST) To: Brian Fundakowski Feldman Cc: Nik Clayton , current@FreeBSD.org Subject: Re: /usr/share/calendar/calendar.freebsd ? References: From: asami@FreeBSD.org (fifi -- hamster of Satoshi) Date: 31 Oct 1999 02:05:14 -0700 In-Reply-To: Brian Fundakowski Feldman's message of "Sun, 31 Oct 1999 00:13:14 -0400 (EDT)" Message-ID: Lines: 8 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Brian Fundakowski Feldman * Cool idea! Let's just limit it to the committer birthdays and not * pets' birthdays too (sorry Asami's hamster and Jordan's cats, but it Why not? Discrimination! I've committed things too! -fifi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 2:42:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id CB01714C20 for ; Sun, 31 Oct 1999 02:42:49 -0800 (PST) (envelope-from iceman@nrg4u.com) Received: (qmail 11734 invoked from network); 31 Oct 1999 10:42:11 -0000 Received: from unknown (HELO nrg4u.com) ([195.134.128.182]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 31 Oct 1999 10:42:11 -0000 Message-ID: <381C1D84.C0125AD7@nrg4u.com> Date: Sun, 31 Oct 1999 11:44:20 +0100 From: Iceman X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Leif Neland Cc: Alan Cox , current@FreeBSD.ORG Subject: Re: Sv: copy-on-write optimized faults References: <19991029144743.Z16685@cs.rice.edu> <01d501bf22f7$75a55820$0e00a8c0@neland.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > > I would appreciate it if people running -current would run a "vmstat -s" > > and tell me if they see a NON-ZERO value for copy-on-write optimized > > faults. About six months ago, I implemented a simpler and more general > > optimization at an earlier "fork in the road". (In effect, I avoid > > the creation of the redundant vm object that "copy-on-write > > optimized faults" applies to.) > > > FreeBSD ns.internet.dk 3.3-STABLE FreeBSD 3.3-STABLE #6: Fri Oct 1 16:06:46 CEST 1999 root@neland.dk:/usr/src/sys/compile/DK i386 > > 9272885 copy-on-write faults > 2062637 copy-on-write optimized faults < > I must have something configured wrong, or??? I get high numbers too: FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun Jun 13 20:31:43 CEST 1999 opi@mailtoaster1.pipeline.ch:/usr/src/sys /compile/mailtoaster1 i386 11:40AM up 137 days, 23:26, 1 user, load averages: 0.00, 0.00, 0.00 64598649 cpu context switches 2745071057 device interrupts 32328669 software interrupts 43110463 traps 296791454 system calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 22418 vnode pager pageins 46048 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 122 page daemon wakeups 188111 pages examined by the page daemon 2100 pages reactivated 10358286 copy-on-write faults 693663 copy-on-write optimized faults 20699423 zero fill pages zeroed 15663587 zero fill pages prezeroed 252 intransit blocking page faults 41725673 total VM faults taken 43325585 pages freed 112 pages freed by daemon 25621561 pages freed by exiting processes 17199 pages active 35325 pages inactive 1922 pages in VM cache 8481 pages wired down 1067 pages free 4096 bytes per page 85804588 total name lookups cache hits (67% pos + 5% neg) system 7% per-directory deletions 1%, falsehits 0%, toolong 0% FreeBSD proxy.pipeline.ch 3.3-STABLE FreeBSD 3.3-STABLE #3: Fri Oct 8 11:08:16 CEST 1999 opi@proxy.pipeline.ch:/usr/src/sys/compile/ proxy i386 11:38AM up 22 days, 14:59, 2 users, load averages: 0.00, 0.00, 0.00 16661677 cpu context switches 467666693 device interrupts 12164983 software interrupts 11257840 traps 120776685 system calls 6941 swap pager pageins 7483 swap pager pages paged in 725 swap pager pageouts 2821 swap pager pages paged out 4196 vnode pager pageins 12204 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 1885 page daemon wakeups 4572222 pages examined by the page daemon 4850 pages reactivated 449499 copy-on-write faults 30784 copy-on-write optimized faults 555925 zero fill pages zeroed 312825 zero fill pages prezeroed 576 intransit blocking page faults 1619807 total VM faults taken 1826533 pages freed 1817 pages freed by daemon 703761 pages freed by exiting processes 22101 pages active 2977 pages inactive 1520 pages in VM cache 4868 pages wired down 224 pages free 4096 bytes per page 18695799 total name lookups cache hits (51% pos + 4% neg) system 31% per-directory deletions 0%, falsehits 0%, toolong 0% -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 2:46:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 0D48014E06 for ; Sun, 31 Oct 1999 02:46:48 -0800 (PST) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id LAA17048 for ; Sun, 31 Oct 1999 11:46:46 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.9.3) with ESMTP id LAA00673 for ; Sun, 31 Oct 1999 11:46:45 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <199910311046.LAA00673@trantor.xs4all.nl> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@FreeBSD.ORG Subject: ATAPI CD errors Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Oct 1999 11:46:44 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I switched to the 'new' atapi driver and I am having trouble with my cdrom which worked fine using the old wd driver. I have the following in my config file : controller ata0 device atadisk0 device atapicd0 The device exists: $ ls -l /dev/acd0* brw-r----- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a brw-r----- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c Booting gives the following : ad0: ATA-3 disk at ata0 as master ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as slave acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33 acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked But when I try to mount the CD I get the following error : atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 Anybody any idea or hint ?? TIA Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 2:58:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2776E14C38 for ; Sun, 31 Oct 1999 02:58:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA05902; Sun, 31 Oct 1999 10:58:15 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 31 Oct 1999 10:58:14 +0000 (GMT) From: Doug Rabson To: Paul van der Zwan Cc: freebsd-current@freebsd.org Subject: Re: ATAPI CD errors In-Reply-To: <199910311046.LAA00673@trantor.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Paul van der Zwan wrote: > > I switched to the 'new' atapi driver and I am having trouble with my cdrom > which worked fine using the old wd driver. > > I have the following in my config file : > > controller ata0 > device atadisk0 > device atapicd0 > > The device exists: > $ ls -l /dev/acd0* > brw-r----- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a > brw-r----- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c > > Booting gives the following : > ad0: ATA-3 disk at ata0 as master > ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue, UDMA33 > Creating DISK ad0 > Creating DISK wd0 > atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 > acd0: CDROM drive at ata0 as slave > acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33 > acd0: supported read types: CD-DA > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > > But when I try to mount the CD I get the following error : > atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 > atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 > > Anybody any idea or hint ?? I get this on a machine at work which I recently put FreeBSD on. I moved it back to the wdc driver for now. If any extra information would help to debug this, I'm happy to test things. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 3: 6:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 667B014C38 for ; Sun, 31 Oct 1999 03:06:45 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 16912 invoked by uid 1001); 31 Oct 1999 11:06:41 +0000 (GMT) To: iceman@nrg4u.com Cc: leif@neland.dk, alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: Sv: copy-on-write optimized faults From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 31 Oct 1999 11:44:20 +0100" References: <381C1D84.C0125AD7@nrg4u.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 31 Oct 1999 12:06:41 +0100 Message-ID: <16910.941368001@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I get high numbers too: > > FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun > Jun 13 20:31:43 CEST 1999 opi@mailtoaster1.pipeline.ch:/usr/src/sys > /compile/mailtoaster1 i386 Read the original message. It says: > > I would appreciate it if people running -current would run a "vmstat -s" Notice "people running -current". The numbers for people running -stable are not interesting. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 3:16: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id A10BF14E34 for ; Sun, 31 Oct 1999 03:15:54 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id MAA14225 for ; Sun, 31 Oct 1999 12:15:45 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 31 Oct 1999 12:15:45 +0100 (CET) From: Leif Neland To: freebsd-current@freebsd.org Subject: new kernel, old userland -> signal 12? 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 run pre-signal-change-current on my gateway-apache-squid-imap-sendmail-mysql-roxen server and post-signal-change-current on my other box. I have compiled a new kernel on the post-signal-change machine, and installed it (as kernel.new) on the old machine. But I get a panic, trap 12 while in kernel mode after a few minutes. Is this to be expected, and am I just supposed to upgrade userland too, or is it a serious problem which should be solved before I upgrade? I don't want to break this box, as this is my connection to the world... 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 31 3:33:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 1B6A514E34 for ; Sun, 31 Oct 1999 03:33:20 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id MAA18230 for ; Sun, 31 Oct 1999 12:33:11 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 31 Oct 1999 12:33:11 +0100 (CET) From: Leif Neland To: freebsd-current@freebsd.org Subject: ed0 hangs at boot. 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 current, cvsupped around 3:00 GMT 31 oct. When trying to boot a new kernel, the machine simply hangs. I have narrowed it down to ed0, by removing other devices with visual config at boot. However, nothing is shown regarding ed0, so the hang probably occurs early in the probing. Therefore I see no reason to type a dmesg from the hang; but I enclose a normal dmesg.boot with the old kernel. I have my ed0 at a non-standard 0x340. The hang happens both with my custom kernel with this adress, and with a generic kernel, with this adress changed at visual config. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Sun Jul 18 12:00:53 CEST 1999 root@gina.neland.dk:/usr/src/sys/compile/ARNOLD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P5 (59.97-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x515 Stepping = 5 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62222336 (60764K bytes) Preloaded elf kernel "kernel" at 0xc02c2000. Intel Pentium detected, installing workaround for F00F bug Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 ncr0: irq 11 at device 1.0 on pci0 isab0: at device 2.0 on pci0 vga-pci0: at device 6.0 on pci0 isa0: on motherboard ed0 at port 0x340-0x35f irq 10 on isa0 ed0: address 00:80:c8:18:9c:c2, type NE2000 (16 bit) atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA (mono) <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 16450 sio2: configured irq 5 not in bitmap of probed irqs 0 sio3: configured irq 9 not in bitmap of probed irqs 0 ppc0 at port 0x378-0x37f on isa0 ppc0: PC87332 chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 ppi0: on ppbus 0 ppc1 at port 0x278-0x27f irq 5 on isa0 ppc1: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt1: on ppbus 1 lpt1: Interrupt-driven port ppi1: on ppbus 1 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver Waiting 5 seconds for SCSI devices to settle da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) changing root device to da0s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [88765 x 2048 byte records] machine i386 cpu I586_CPU ident ARNOLD maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 controller ncr0 controller scbus0 device da0 #Only need one of these, the code dynamically grows device pass0 device cd0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x31 # Advanced Power Management device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? port IO_COM3 irq 5 device sio3 at isa? port IO_COM4 irq 9 device ed0 at isa? port 0x340 irq 10 iomem 0xd8000 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 2 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's options KTRACE #kernel tracing options SYSVSHM options SYSVMSG options SYSVSEM pseudo-device bpf 4 #Berkeley packet filter device pca0 at isa? port IO_TIMER1 options SOFTUPDATES To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 3:38:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id B1C9F14E34 for ; Sun, 31 Oct 1999 03:38:28 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 11834 invoked from network); 31 Oct 1999 11:37:50 -0000 Received: from unknown (HELO pipeline.ch) ([195.134.128.182]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 31 Oct 1999 11:37:50 -0000 Message-ID: <381C2A8F.FB7E52D3@pipeline.ch> Date: Sun, 31 Oct 1999 12:39:59 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: leif@neland.dk, alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: Sv: copy-on-write optimized faults References: <381C1D84.C0125AD7@nrg4u.com> <16910.941368001@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > > I get high numbers too: > > > > FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun > > Jun 13 20:31:43 CEST 1999 opi@mailtoaster1.pipeline.ch:/usr/src/sys > > /compile/mailtoaster1 i386 > > Read the original message. It says: > > > > I would appreciate it if people running -current would run a "vmstat -s" > > Notice "people running -current". The numbers for people running -stable > are not interesting. Sorry, I got it too late... Here comes my -current vmstat -s: FreeBSD opi.flirtbox.ch 4.0-CURRENT FreeBSD 4.0-CURRENT #25: Fri Oct 15 18:51:55 CEST 1999 opi@opi.flirtbox.ch:/usr/src/sys/compile/opi i386 2276542 cpu context switches 190670731 device interrupts 842992 software interrupts 2635334 traps 17743991 system calls 16 swap pager pageins 20 swap pager pages paged in 10 swap pager pageouts 14 swap pager pages paged out 3900 vnode pager pageins 14335 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 345 page daemon wakeups 137481 pages examined by the page daemon 7730 pages reactivated 867915 copy-on-write faults 0 copy-on-write optimized faults 1295449 zero fill pages zeroed 1106142 zero fill pages prezeroed 56 intransit blocking page faults 2560858 total VM faults taken 2706144 pages freed 2 pages freed by daemon 1819076 pages freed by exiting processes 1773 pages active 3016 pages inactive 501 pages in VM cache 1903 pages wired down 268 pages free 4096 bytes per page 5426026 total name lookups cache hits (54% pos + 4% neg) system 18% per-directory deletions 0%, falsehits 0%, toolong 0% -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 3:40:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (Postfix) with ESMTP id 0D75714E99 for ; Sun, 31 Oct 1999 03:40:31 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (silvia [209.109.233.59]) by vader.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id DAA16827 for ; Sun, 31 Oct 1999 03:39:20 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA27331; Sun, 31 Oct 1999 03:39:17 -0800 (PST) To: current@FreeBSD.org Subject: Re: /usr/share/calendar/calendar.freebsd ? References: From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 31 Oct 1999 04:39:16 -0700 In-Reply-To: asami@FreeBSD.org's message of "31 Oct 1999 02:05:14 -0700" Message-ID: Lines: 12 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: asami@FreeBSD.org (fifi -- hamster of Satoshi) * Why not? Discrimination! I've committed things too! * * -fifi Oops, I left the cage door open! Sorry folks! No, I honestly have no idea what fifi was talking about. I've never let her commit things. Ok, not without me watching over her shoulder.... Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 4: 6:14 1999 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 DBB1914C0B for ; Sun, 31 Oct 1999 04:05:53 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id MAA66790; Sun, 31 Oct 1999 12:05:51 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 31 Oct 1999 12:01:00 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 31 Oct 1999 12:00:57 +0000 To: Leif Neland From: Bob Bishop Subject: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 12:33 pm +0100 31/10/99, Leif Neland wrote: >current, cvsupped around 3:00 GMT 31 oct. > >When trying to boot a new kernel, the machine simply hangs. >I have narrowed it down to ed0[etc] The LinkSys probe code (in particular the checksum at the start of ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine up. I guess you have the same problem. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 4:58: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 15F6D14CDF for ; Sun, 31 Oct 1999 04:57:46 -0800 (PST) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id NAA05374 for ; Sun, 31 Oct 1999 13:57:44 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.9.3) with ESMTP id NAA02349; Sun, 31 Oct 1999 13:57:31 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <199910311257.NAA02349@trantor.xs4all.nl> X-Mailer: exmh version 2.1.0 09/18/1999 To: Paul van der Zwan Cc: freebsd-current@FreeBSD.ORG, paulz@trantor.xs4all.nl Subject: Re: ATAPI CD errors In-Reply-To: Message from Paul van der Zwan of "Sun, 31 Oct 1999 11:46:44 +0100." <199910311046.LAA00673@trantor.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Oct 1999 13:57:30 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199910311046.LAA00673@trantor.xs4all.nl>, Paul van der Zwan wrote: > >I switched to the 'new' atapi driver and I am having trouble with my cdrom >which worked fine using the old wd driver. > >I have the following in my config file : > >controller ata0 >device atadisk0 >device atapicd0 > >The device exists: >$ ls -l /dev/acd0* >brw-r----- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a >brw-r----- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c > >Booting gives the following : >ad0: ATA-3 disk at ata0 as master >ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S >ad0: 16 secs/int, 0 depth queue, UDMA33 >Creating DISK ad0 >Creating DISK wd0 >atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 >acd0: CDROM drive at ata0 as slave >acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33 >acd0: supported read types: CD-DA >acd0: Audio: play, 255 volume levels >acd0: Mechanism: ejectable tray >acd0: Medium: no/blank disc inside, unlocked > >But when I try to mount the CD I get the following error : >atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 >atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 > >Anybody any idea or hint ?? I hate to followup on my own messages , but I made a 'small' error. The message above was cause by an empty drive ( wrong PC ;-() The real message I get is : $ sudo mount /cdrom cd9660: Operation not permitted And dmesg gives the following: atapi: PREVENT_ALLOW - UNIT ATTENTION skey=6 asc=28 ascq=00 error=08 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 BTW this is on a -current cvsupped and built last night. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 5:24:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id E45A014C3A for ; Sun, 31 Oct 1999 05:24:52 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id OAA78721 for current@FreeBSD.org; Sun, 31 Oct 1999 14:13:13 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Sun, 31 Oct 1999 14:13:05 +0100 From: Marcel Moolenaar Message-ID: <381C4061.8396772C@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <79049.941312718@localhost>, Subject: Re: -current build fails Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vincent Poy wrote: > I have always read the -current mailing list but you have to > remember that by the time I do the update, the known problem should > already have been gone. I assume you have a lousy way of expressing yourself (in this case) and that you don't actually mean what you wrote... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 31 5:27:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 58BA314C3A; Sun, 31 Oct 1999 05:26:10 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id KAA52424; Sun, 31 Oct 1999 10:18:53 GMT (envelope-from nik) Date: Sun, 31 Oct 1999 10:18:52 +0000 From: Nik Clayton To: fifi -- hamster of Satoshi Cc: Brian Fundakowski Feldman , Nik Clayton , current@FreeBSD.org, chat@freebsd.org Subject: Re: /usr/share/calendar/calendar.freebsd ? Message-ID: <19991031101852.A52200@catkin.nothing-going-on.org> Reply-To: chat@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from fifi -- hamster of Satoshi on Sun, Oct 31, 1999 at 02:05:14AM -0700 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Redirecting to -chat] On Sun, Oct 31, 1999 at 02:05:14AM -0700, fifi -- hamster of Satoshi wrote: > * From: Brian Fundakowski Feldman > > * Cool idea! Let's just limit it to the committer birthdays and not > * pets' birthdays too (sorry Asami's hamster and Jordan's cats, but it > > Why not? Discrimination! I've committed things too! Isn't this a breach of some "You shall not share your account and password with anyone else rule?" If it isn't, it should be :-) N -- A different "distribution" of Linux is really a different operating system. They just refuse to call it that because it's bad press. But that's what the shoe fits. -- Tom Christiansen, <199910211639.KAA18701@jhereg.perl.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 31 5:56:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id AD18B14E1E for ; Sun, 31 Oct 1999 05:56:54 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id OAA02071; Sun, 31 Oct 1999 14:56:37 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 31 Oct 1999 14:56:37 +0100 (CET) From: Leif Neland To: Bob Bishop Cc: freebsd-current@FreeBSD.ORG Subject: Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Bob Bishop wrote: > Hi, > > At 12:33 pm +0100 31/10/99, Leif Neland wrote: > >current, cvsupped around 3:00 GMT 31 oct. > > > >When trying to boot a new kernel, the machine simply hangs. > >I have narrowed it down to ed0[etc] > > The LinkSys probe code (in particular the checksum at the start of > ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > up. I guess you have the same problem. > Yes, I added a return(0) at the beginning of ed_get_linksys(); and now I'm up. But now is the question how to fix if_ed permanently... Perhaps a reordering could help. If ed_get_linksys was called later than my card was detected... My card is a dlink 250. 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 31 6:20:32 1999 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 0DE4814CAF for ; Sun, 31 Oct 1999 06:20:28 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id OAA67646; Sun, 31 Oct 1999 14:20:27 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 31 Oct 1999 14:12:17 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 31 Oct 1999 14:12:14 +0000 To: Leif Neland From: Bob Bishop Subject: Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 2:56 pm +0100 31/10/99, Leif Neland wrote: >[...]If ed_get_linksys was called later than my card was >detected... I guess it's an ordering thing, but I don't have a LinkSys card here for testing. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 7: 3:51 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 55C2D14DF9; Sun, 31 Oct 1999 07:03:50 -0800 (PST) From: "Jonathan M. Bresler" To: rb@gid.co.uk Cc: leifn@neland.dk, freebsd-current@FreeBSD.ORG In-reply-to: (message from Bob Bishop on Sun, 31 Oct 1999 12:00:57 +0000) Subject: Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot) Message-Id: <19991031150350.55C2D14DF9@hub.freebsd.org> Date: Sun, 31 Oct 1999 07:03:50 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The LinkSys probe code (in particular the checksum at the start of > ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > up. I guess you have the same problem. > ouch! not good....what is the ethernet address of your ne2000 clone? jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 7: 7:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 6CE5614DF9 for ; Sun, 31 Oct 1999 07:07:34 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id KAA25646; Sun, 31 Oct 1999 10:07:21 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199910311507.KAA25646@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andre Oppermann Cc: sthaug@nethelp.no, leif@neland.dk, alc@cs.rice.edu, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Sv: copy-on-write optimized faults References: <381C1D84.C0125AD7@nrg4u.com> <16910.941368001@verdi.nethelp.no> <381C2A8F.FB7E52D3@pipeline.ch> In-reply-to: Your message of "Sun, 31 Oct 1999 12:39:59 +0100." <381C2A8F.FB7E52D3@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Oct 1999 10:07:20 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And my mine... I get zero COW optimized faults. louie@whizzo[20] $ vmstat -s 47312081 cpu context switches 89421468 device interrupts 30438305 software interrupts 16214761 traps 244593116 system calls 1546 swap pager pageins 5124 swap pager pages paged in 4185 swap pager pageouts 22164 swap pager pages paged out 13486 vnode pager pageins 86761 vnode pager pages paged in 217 vnode pager pageouts 217 vnode pager pages paged out 1151 page daemon wakeups 7505975 pages examined by the page daemon 23256 pages reactivated 663440 copy-on-write faults 0 copy-on-write optimized faults 7306697 zero fill pages zeroed 4185272 zero fill pages prezeroed 1801 intransit blocking page faults 8604076 total VM faults taken 8804200 pages freed 20 pages freed by daemon 2300440 pages freed by exiting processes 16937 pages active 6580 pages inactive 1268 pages in VM cache 6594 pages wired down 245 pages free 4096 bytes per page 20885389 total name lookups cache hits (84% pos + 0% neg) system 4% per-directory deletions 0%, falsehits 0%, toolong 0% louie@whizzo[21] $ uname -a FreeBSD whizzo.transsys.com 4.0-CURRENT FreeBSD 4.0-CURRENT #8: Tue Oct 26 22:55:45 EDT 1999 louie@whizzo.transsys.com:/usr/src/sys/compile/WHIZZO i386 louie@whizzo[22] $ uptime 10:06AM up 4 days, 10:17, 0 users, load averages: 0.04, 0.03, 0.00 louie@whizzo[23] $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 7:21: 6 1999 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 6E29814A0B; Sun, 31 Oct 1999 07:20:56 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id PAA68050; Sun, 31 Oct 1999 15:20:55 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 31 Oct 1999 15:16:59 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19991031150350.55C2D14DF9@hub.freebsd.org> References: (message from Bob Bishop on Sun, 31 Oct 1999 12:00:57 +0000) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 31 Oct 1999 15:16:56 +0000 To: "Jonathan M. Bresler" From: Bob Bishop Subject: Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot) Cc: leifn@neland.dk, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 7:03 am -0800 31/10/99, Jonathan M. Bresler wrote: >> >> The LinkSys probe code (in particular the checksum at the start of >> ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine >> up. I guess you have the same problem. >> > > ouch! not good....what is the ethernet address of your ne2000 >clone? ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 7:52:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0EF9B14BE0 for ; Sun, 31 Oct 1999 07:52:19 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11hxGw-000EJi-00; Sun, 31 Oct 1999 10:51:58 -0500 Date: Sun, 31 Oct 1999 10:51:57 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Doug Rabson Cc: Paul van der Zwan , freebsd-current@freebsd.org Subject: Re: ATAPI CD errors 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 Have you either tried disabling DMA on the drive? This is easily achieved by the following (whitespace mangled): --- atapi-all.c 1999/10/10 18:08:38 1.19 +++ atapi-all.c 1999/10/23 16:51:12 @@ -135,7 +135,8 @@ udmamode(atp->atapi_parm), atp->atapi_parm->dmaflag); - if (!(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && + if (atp->atapi_parm->device_type != ATAPI_TYPE_CDROM && + !(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && !ata_dmainit(atp->controller, atp->unit, (apiomode(atp->atapi_parm) < 0) ? (atp->atapi_parm->dmaflag ? 4 : 0) : -- 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 31 7:54:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id A3F4014BEF for ; Sun, 31 Oct 1999 07:54:14 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-11.blackbox-2.netaxs.com (dyn-11.blackbox-2.netaxs.com [207.106.60.11]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id KAA22328 for ; Sun, 31 Oct 1999 10:54:12 -0500 (EST) Date: Sun, 31 Oct 1999 10:54:11 -0500 (EST) From: Bryan Liesner To: freebsd-current@freebsd.org Subject: ATAPI tape drive not probed 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 had an ATAPI CDROM as master and an HP Colorado tape as slave set up on my system for quite some time now. I recently migrated to 4.0 and I'm using the new ATA drivers. Below is a snip from my kernel config: controller ata0 device atadisk0 device atapicd0 device atapist0 At boot time, the messages show that there are two devices on the channel, but only the CDROM is configured. Any ideas? ata0: Aladdin: two atapi devices on this channel, DMA disabled atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@netaxs.com Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 8:13:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4768614C24; Sun, 31 Oct 1999 08:13:05 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id QAA00498; Sun, 31 Oct 1999 16:13:25 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 31 Oct 1999 16:13:25 +0000 (GMT) From: Doug Rabson To: Brian Fundakowski Feldman Cc: Paul van der Zwan , freebsd-current@freebsd.org Subject: Re: ATAPI CD errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote: > Have you either tried disabling DMA on the drive? This is easily achieved > by the following (whitespace mangled): I'll try it on Monday. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 8:34:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D8FE014C24; Sun, 31 Oct 1999 08:34:06 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA92381; Sun, 31 Oct 1999 17:34:04 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199910311634.RAA92381@freebsd.dk> Subject: Re: ATAPI CD errors In-Reply-To: from Doug Rabson at "Oct 31, 1999 04:13:25 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 31 Oct 1999 17:34:04 +0100 (CET) Cc: green@FreeBSD.ORG (Brian Fundakowski Feldman), paulz@trantor.xs4all.nl (Paul van der Zwan), 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 Doug Rabson wrote: > On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote: > > > Have you either tried disabling DMA on the drive? This is easily achieved > > by the following (whitespace mangled): > > I'll try it on Monday. Hmm, as well as DMA might be the reason, it only applies to reads/writes all other communication with the drive is non-DMA. So if the drive doesn't even probe right, there are other reasons.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 8:56:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.powertech.no (intentia.powertech.no [195.159.0.220]) by hub.freebsd.org (Postfix) with ESMTP id 6098814C3A for ; Sun, 31 Oct 1999 08:56:04 -0800 (PST) (envelope-from kjetil@poltergeist.net) Received: from poltergeist.net (caught.in.the.poltergeist.net [195.159.99.57]) by mail.powertech.no (8.9.3/8.8.5) with ESMTP id RAA28332 for ; Sun, 31 Oct 1999 17:56:02 +0100 Message-ID: <381C749C.AB2AD6C3@poltergeist.net> Date: Sun, 31 Oct 1999 17:55:56 +0100 From: Kjetil Svenheim X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the same problem with my NE2000 clone, so for now I have to use an old kernel that I made 2 weeks ago. My NE2000-clone uses port 300, irq 11 > Yes, I added a return(0) at the beginning of ed_get_linksys(); and now I'm > up. But now is the question how to fix if_ed permanently... Perhaps a > reordering could help. If ed_get_linksys was called later than my card was > detected... Ehm, if I was to do this to fix the problem, what file would I edit? And yeah, I am interested in a permanent solution as well. :) - Kjetil Svenheim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 9:11:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id C0C8114CAC for ; Sun, 31 Oct 1999 09:11:45 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1002) id 80DE7C3; Sun, 31 Oct 1999 09:11:45 -0800 (PST) Date: Sun, 31 Oct 1999 09:11:45 -0800 From: Chris Piazza To: Kjetil Svenheim Cc: freebsd-current@FreeBSD.ORG Subject: Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot) Message-ID: <19991031091145.B430@norn.ca.eu.org> References: <381C749C.AB2AD6C3@poltergeist.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <381C749C.AB2AD6C3@poltergeist.net> X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 31, 1999 at 05:55:56PM +0100, Kjetil Svenheim wrote: > I have the same problem with my NE2000 clone, so for now I have to use > an old kernel that I made 2 weeks ago. > > My NE2000-clone uses port 300, irq 11 > > > Yes, I added a return(0) at the beginning of ed_get_linksys(); and now I'm > > up. But now is the question how to fix if_ed permanently... Perhaps a > > reordering could help. If ed_get_linksys was called later than my card was > > detected... > > Ehm, if I was to do this to fix the problem, what file would I edit? > > And yeah, I am interested in a permanent solution as well. :) /sys/dev/ed/if_ed.c:902. -Chris -- cpiazza@home.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 9:18:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from megadodo.segNET.COM (megadodo.segNET.COM [206.34.181.3]) by hub.freebsd.org (Postfix) with ESMTP id 3937214C58; Sun, 31 Oct 1999 09:18:19 -0800 (PST) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a126.bf.sover.net [209.198.85.126]) by megadodo.segNET.COM (8.9.1a/8.8.5) with ESMTP id MAA22693; Sun, 31 Oct 1999 12:17:29 -0500 (EST) Date: Sun, 31 Oct 1999 12:16:21 +0000 (GMT) From: Adam Strohl To: Bob Bishop Cc: "Jonathan M. Bresler" , leifn@neland.dk, freebsd-current@FreeBSD.ORG Subject: Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot) 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 also get this lock up on a machine with a ISA NE2000 clone: ed0 at 0x300-0x31f irq 9 on isa ed0: address 00:40:33:23:6b:c1, type NE2000 (16 bit) I have every other NIC driver removed, but a -CURRENT kernel with ed0 enabled on it will cause it to lock hard. Disabling the device in the kernel config will let me boot. On Sun, 31 Oct 1999, Bob Bishop wrote: > >> The LinkSys probe code (in particular the checksum at the start of > >> ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > >> up. I guess you have the same problem. > >> > > > > ouch! not good....what is the ethernet address of your ne2000 > >clone? > > ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 > ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 10: 5:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 595FD14BDE for ; Sun, 31 Oct 1999 10:05:22 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA17082 for current@FreeBSD.org; Sun, 31 Oct 1999 19:05:00 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3048E878D; Sun, 31 Oct 1999 16:24:19 +0100 (CET) Date: Sun, 31 Oct 1999 16:24:19 +0100 From: Ollivier Robert To: current@FreeBSD.org Subject: Re: /usr/share/calendar/calendar.freebsd ? Message-ID: <19991031162419.A8415@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Satoshi - Ports Wraith - Asami: > let her commit things. Ok, not without me watching over her shoulder.... Experience shows that even this is not enough to prevent accidents (Hi Greg!). :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 10:52:47 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 8FBDB14CAC; Sun, 31 Oct 1999 10:52:41 -0800 (PST) From: "Jonathan M. Bresler" To: freebsd-current@FreeBSD.ORG Cc: kjetil@poltergeist.net, rb@gid.co.uk, leifn@neland.dk, adams@digitalspark.net Subject: Linksys conflicts with NE2000 Message-Id: <19991031185241.8FBDB14CAC@hub.freebsd.org> Date: Sun, 31 Oct 1999 10:52:41 -0800 (PST) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG okay i have changed the order in which we test for NE1000, NE2000, and the Linksys (dl10016c ? ethernet controller). pleazse test and let me know how this patch does. hopefully the problem will be solved. does *ANYONE* have an NE1000, the can test? before adding in teh Linksys we tested: NE1000 then NE2000. NE1000 worked NE2000 worked Linksys we mistaken for an NE1000 after adding the Linksys we tested: Linksys, NE1000, NE2000. NE1000 worked (?? no reports for failure ??) NE2000 failed Linksys worked try the patch in http://www.freebsd.org/~jmb/if_ed.c.patch the order there is: if (NE1000-like) test Linksys, test NE1000 else test for NE2000 else unknown return ENXIO jmb ps. not crazy about the form of the code if () { } else { if () { } else { } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 11:31:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 42B1814A1B; Sun, 31 Oct 1999 11:31:42 -0800 (PST) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA07164; Sun, 31 Oct 1999 20:31:40 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA00450; Sun, 31 Oct 1999 20:25:32 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <199910311925.UAA00450@trantor.xs4all.nl> X-Mailer: exmh version 2.1.0 09/18/1999 To: Brian Fundakowski Feldman Cc: Doug Rabson , Paul van der Zwan , freebsd-current@freebsd.org, paulz@trantor.xs4all.nl Subject: Re: ATAPI CD errors In-Reply-To: Message from Brian Fundakowski Feldman of "Sun, 31 Oct 1999 10:51:57 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Oct 1999 20:25:32 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brian Fun dakowski Feldman wrote: >Have you either tried disabling DMA on the drive? This is easily achieved >by the following (whitespace mangled): > >--- atapi-all.c 1999/10/10 18:08:38 1.19 >+++ atapi-all.c 1999/10/23 16:51:12 >@@ -135,7 +135,8 @@ > udmamode(atp->atapi_parm), > atp->atapi_parm->dmaflag); >- if (!(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && >+ if (atp->atapi_parm->device_type != ATAPI_TYPE_CDROM && >+ !(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && > !ata_dmainit(atp->controller, atp->unit, > (apiomode(atp->atapi_parm) < 0) ? > (atp->atapi_parm->dmaflag ? 4 : 0) : > This patch allows me to mount the cdrom... The probes show PIO mode i.s.o. DMA. So it looks like DMA is broken for this drive.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 11:31:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.50]) by hub.freebsd.org (Postfix) with ESMTP id 369BC14C0E; Sun, 31 Oct 1999 11:31:42 -0800 (PST) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA13001; Sun, 31 Oct 1999 20:31:41 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA00450; Sun, 31 Oct 1999 20:25:32 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <199910311925.UAA00450@trantor.xs4all.nl> X-Mailer: exmh version 2.1.0 09/18/1999 To: Brian Fundakowski Feldman Cc: Doug Rabson , Paul van der Zwan , freebsd-current@freebsd.org, paulz@trantor.xs4all.nl Subject: Re: ATAPI CD errors In-Reply-To: Message from Brian Fundakowski Feldman of "Sun, 31 Oct 1999 10:51:57 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Oct 1999 20:25:32 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brian Fun dakowski Feldman wrote: >Have you either tried disabling DMA on the drive? This is easily achieved >by the following (whitespace mangled): > >--- atapi-all.c 1999/10/10 18:08:38 1.19 >+++ atapi-all.c 1999/10/23 16:51:12 >@@ -135,7 +135,8 @@ > udmamode(atp->atapi_parm), > atp->atapi_parm->dmaflag); >- if (!(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && >+ if (atp->atapi_parm->device_type != ATAPI_TYPE_CDROM && >+ !(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && > !ata_dmainit(atp->controller, atp->unit, > (apiomode(atp->atapi_parm) < 0) ? > (atp->atapi_parm->dmaflag ? 4 : 0) : > This patch allows me to mount the cdrom... The probes show PIO mode i.s.o. DMA. So it looks like DMA is broken for this drive.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 11:56:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A4DA814E5E for ; Sun, 31 Oct 1999 11:56:19 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA23302 for ; Sun, 31 Oct 1999 11:56:17 -0800 (PST) Date: Sun, 31 Oct 1999 11:56:15 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: current@freebsd.org Subject: Discussions starting on -arch. 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 am going to try host the following discussions on -arch over the next week. 1/ which direction (maybe multiple) are we going with threads. 2/ SMP. how to go about it from here.. 3/ In what ways should the VFS and the filesystems be changed/cleaned-up 4/ what about posix extensions such as scheduler classes... I will be doing them SERIALLY, by which I mean that While talking about #1 we don't wander off into #2 unless it directly affects #1. I will try add 'reminders of upcoming topics' regularly so people can hold off, knowing that their topic is on the way.. The first discussion will be on THREADS. A hot topic these days. and I will be posting a stating note on the topic in a short while.. If you are not on Arch, or think you are but don't get a small note from me om it (similar to this one) in a short time, then subscribe by: echo "subscribe FreeBSD-arch" |mail majordomo@freebsd.org should do it. This note will not be reposted on -current. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 12:12:10 1999 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 92A0914C01 for ; Sun, 31 Oct 1999 12:12:06 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 5CF1E1C41; Sun, 31 Oct 1999 14:14:22 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 5987A3837; Sun, 31 Oct 1999 14:14:22 -0500 (EST) Date: Sun, 31 Oct 1999 14:14:22 -0500 (EST) From: Bill Fumerola To: "Louis A. Mamakos" Cc: current@FreeBSD.ORG Subject: Re: Sv: copy-on-write optimized faults In-Reply-To: <199910311507.KAA25646@whizzo.transsys.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 Sun, 31 Oct 1999, Louis A. Mamakos wrote: > And my mine... I get zero COW optimized faults. THE E-MAIL EXPLICITLY SAID ONLY TO POST IF YOU HAVE MORE THEN 0 FAULTS I hope one day the people who don't read this list carefully miss something really important and it eats your system as a result. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Sun Oct 31 12:22:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 20CAC14CAC for ; Sun, 31 Oct 1999 12:22:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id MAA07438; Sun, 31 Oct 1999 12:22:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199910312022.MAA07438@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Discussions starting on -arch. In-reply-to: Your message of "Sun, 31 Oct 1999 11:56:15 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Oct 1999 12:22:33 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am not that really interested on threads.. Is there a possibility of having an async call gate for which the kernel can do the scheduling whether be for a uni processor or a multi processor enviroment. -- Amancio Hasty hasty@rah.star-gate.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 31 12:25:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 49B0D14CAC; Sun, 31 Oct 1999 12:25:46 -0800 (PST) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id VAA09025; Sun, 31 Oct 1999 21:25:35 +0100 (CET) (envelope-from leif@neland.dk) Message-ID: <006001bf23de$1ba6eea0$0e00a8c0@neland.dk> From: "Leif Neland" To: "Jonathan M. Bresler" , Cc: , References: <19991031150350.55C2D14DF9@hub.freebsd.org> Subject: Sv: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot) Date: Sun, 31 Oct 1999 21:11:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >=20 > >=20 > > The LinkSys probe code (in particular the checksum at the start of > > ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the = machine > > up. I guess you have the same problem. > >=20 >=20 > ouch! not good....what is the ethernet address of your ne2000 > clone? =20 ed0 at port 0x340-0x35f iomem 0xd8000 irq 10 on isa0 ed0: address 00:80:c8:18:9c:c2, type NE2000 (16 bit) 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 31 12:27:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 09C6514CAC for ; Sun, 31 Oct 1999 12:27:49 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA23807; Sun, 31 Oct 1999 12:27:46 -0800 (PST) Date: Sun, 31 Oct 1999 12:27:44 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: Discussions starting on -arch. In-Reply-To: <199910312022.MAA07438@rah.star-gate.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 yes it is a possibility.. see terry's thread model (coming up soon). (at least lurk) On Sun, 31 Oct 1999, Amancio Hasty wrote: > > I am not that really interested on threads.. > > > Is there a possibility of having an async call gate for which the kernel > can do the scheduling whether be for a uni processor or a multi processor > enviroment. > > > -- > > Amancio Hasty > hasty@rah.star-gate.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 31 12:32:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A982D14CAC for ; Sun, 31 Oct 1999 12:32:55 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA23879; Sun, 31 Oct 1999 12:32:53 -0800 (PST) Date: Sun, 31 Oct 1999 12:32:51 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: Discussions starting on -arch. 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 p.s. this should not be in -current but in -arch On Sun, 31 Oct 1999, Julian Elischer wrote: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 13:12:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 736A214E76; Sun, 31 Oct 1999 13:12:24 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id WAA08619; Sun, 31 Oct 1999 22:12:06 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 31 Oct 1999 22:12:06 +0100 (CET) From: Leif Neland To: "Jonathan M. Bresler" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Linksys conflicts with NE2000 In-Reply-To: <19991031185241.8FBDB14CAC@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 Sun, 31 Oct 1999, Jonathan M. Bresler wrote: > > okay i have changed the order in which we test for NE1000, NE2000, and > the Linksys (dl10016c ? ethernet controller). > > pleazse test and let me know how this patch does. > hopefully the problem will be solved. > I tried it, I could boot, and I'm doing a installworld over nfs as I write this. Thanks, now I can continue my plans for letting the isdncard reject calls from callers hiding their CLID... 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 31 13:20:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 4099A14E76 for ; Sun, 31 Oct 1999 13:20:08 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm202.cvzoom.net (lcm202.cvzoom.net [208.230.69.202]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id QAA02520 for ; Sun, 31 Oct 1999 16:01:31 -0500 (EST) Date: Sun, 31 Oct 1999 16:19:04 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: ESS sound drivers and 4.0-current 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 believe the ESS drivers weren't committed to 4.0-current yet. When I grep ' ESS ' in /sys/i386/isa/sound, the only thing I can come up with is the ESS support that was in the old voxware sound code. Sanpei, who is developing the ESS sound drivers, says they were committed to the newpcm drivers. I believe they were not added yet. From http://home.jp.freebsd.org/~sanpei/: tarball for 4-current --> our ESS(ISA) code was commited to newpcm driver in 4.0-current(1999/09/04) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 16: 7:36 1999 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 43C9314F6C for ; Sun, 31 Oct 1999 16:07:17 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id AAA71656; Mon, 1 Nov 1999 00:05:52 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 31 Oct 1999 23:56:28 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19991031185241.8FBDB14CAC@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 31 Oct 1999 23:56:25 +0000 To: "Jonathan M. Bresler" From: Bob Bishop Subject: Re: Linksys conflicts with NE2000 Cc: freebsd-current@FreeBSD.ORG, kjetil@poltergeist.net, leifn@neland.dk, adams@digitalspark.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 10:52 am -0800 31/10/99, Jonathan M. Bresler wrote: >okay i have changed the order in which we test for NE1000, NE2000, and >the Linksys (dl10016c ? ethernet controller). > >pleazse test and let me know how this patch does.[etc] OK the patch fixes the problem here. [Thanks for the context diff] -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 16:47:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 8B94914C24; Sun, 31 Oct 1999 16:47:43 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.3/8.9.3) with ESMTP id TAA29088; Sun, 31 Oct 1999 19:47:40 -0500 (EST) Date: Sun, 31 Oct 1999 19:47:40 -0500 (EST) From: jack To: "Jonathan M. Bresler" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Linksys conflicts with NE2000 In-Reply-To: <19991031185241.8FBDB14CAC@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 Today Jonathan M. Bresler wrote: > okay i have changed the order in which we test for NE1000, NE2000, and > the Linksys (dl10016c ? ethernet controller). > > pleazse test and let me know how this patch does. > hopefully the problem will be solved. Works with my NE2000 clone. Thanks Jonathan. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 18:30:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id B4509150C4 for ; Sun, 31 Oct 1999 18:30:14 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id LAA39297; Mon, 1 Nov 1999 11:30:12 +0900 (JST) Message-Id: <199911010230.LAA39297@rina.r.dl.itc.u-tokyo.ac.jp> To: current@freebsd.org Cc: Seigo Tanimura Subject: Strange atapi active state, ending in ATA_IGNORE_INTR? From: Seigo Tanimura 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: Mon, 01 Nov 1999 11:30:12 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My box has got three ata disks and one atapi cdrom drive(on secondary slave). Since a few weeks ago the cdrom drive does not get probed. Oct 30 19:31:46 silver /kernel: ata-pci0: at device 4.1 on pci0 Oct 30 19:31:46 silver /kernel: ata-pci0: Busmastering DMA supported Oct 30 19:31:46 silver /kernel: ata0: iobase=0x01f0 altiobase=0x03f6 Oct 30 19:31:46 silver /kernel: ata0: mask=03 status0=50 status1=50 Oct 30 19:31:46 silver /kernel: ata0: mask=03 status0=50 status1=50 Oct 30 19:31:46 silver /kernel: ata0: devices = 0x3 Oct 30 19:31:46 silver /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Oct 30 19:31:46 silver /kernel: ata1: iobase=0x0170 altiobase=0x0376 Oct 30 19:31:46 silver /kernel: ata1: mask=03 status0=50 status1=50 Oct 30 19:31:47 silver /kernel: ata1: mask=03 status0=50 status1=00 Oct 30 19:31:47 silver /kernel: ata1: devices = 0x9 Oct 30 19:31:47 silver /kernel: ata1 at 0x0170 irq 15 on ata-pci0 (snip) Oct 30 19:31:49 silver /kernel: ata0: master: success setting up UDMA2 mode on PIIX4 chip Oct 30 19:31:49 silver /kernel: ad0: piomode=4 dmamode=2 udmamode=2 Oct 30 19:31:49 silver /kernel: ad0: ATA-3 disk at ata0 as master Oct 30 19:31:49 silver /kernel: ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Oct 30 19:31:49 silver /kernel: ad0: 16 secs/int, 0 depth queue, UDMA33 Oct 30 19:31:49 silver /kernel: Creating DISK ad0 Oct 30 19:31:49 silver /kernel: Creating DISK wd0 Oct 30 19:31:49 silver /kernel: ata0: slave: success setting up UDMA2 mode on PIIX4 chip Oct 30 19:31:49 silver /kernel: ad1: piomode=4 dmamode=2 udmamode=2 Oct 30 19:31:49 silver /kernel: ad1: ATA-4 disk at ata0 as slave Oct 30 19:31:49 silver /kernel: ad1: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S Oct 30 19:31:49 silver /kernel: ad1: 16 secs/int, 0 depth queue, UDMA33 Oct 30 19:31:49 silver /kernel: Creating DISK ad1 Oct 30 19:31:49 silver /kernel: Creating DISK wd1 Oct 30 19:31:49 silver /kernel: ata1: master: success setting up UDMA2 mode on PIIX4 chip Oct 30 19:31:49 silver /kernel: ad2: piomode=4 dmamode=2 udmamode=2 Oct 30 19:31:49 silver /kernel: ad2: ATA-4 disk at ata1 as master Oct 30 19:31:49 silver /kernel: ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Oct 30 19:31:49 silver /kernel: ad2: 16 secs/int, 0 depth queue, UDMA33 Oct 30 19:31:49 silver /kernel: Creating DISK ad2 Oct 30 19:31:49 silver /kernel: Creating DISK wd2 Oct 30 19:31:49 silver /kernel: DANGER wait_intr active=ATA_IGNORE_INTR The active state after disk probe does not get back to ATA_IDLE, resulting atapi_getparam() to fail on atapi_wait(). Calling atapi_getparam() twice continuously in atapi_attach() helped me, although it is not a proper fix at all. Below is the dmesg. Oct 30 19:36:39 silver /kernel: ata1-slave: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 Oct 30 19:36:39 silver /kernel: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=04 Oct 30 19:36:39 silver /kernel: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=28 ascq=00 error=04 Oct 30 19:36:39 silver /kernel: acd0: CDROM drive at ata1 as slave Oct 30 19:36:39 silver /kernel: acd0: read 2755KB/s (2755KB/s), 128KB buffer, PIO Oct 30 19:36:39 silver /kernel: acd0: supported read types: CD-DA Oct 30 19:36:39 silver /kernel: acd0: Audio: play, 16 volume levels Oct 30 19:36:39 silver /kernel: acd0: Mechanism: ejectable tray Oct 30 19:36:39 silver /kernel: acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 20:31:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 93DA1151C9 for ; Sun, 31 Oct 1999 20:31:40 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.30]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FKI00AEW4J0AO@mta1.snfc21.pbi.net> for current@FreeBSD.ORG; Sun, 31 Oct 1999 20:30:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id B3F5F91567; Sun, 31 Oct 1999 20:30:35 -0800 (PST) Date: Sun, 31 Oct 1999 20:30:35 -0800 (PST) From: Alex Zepeda Subject: Re: Linksys LNE100TX In-reply-to: <37F39267.EC5FE001@MexComUSA.net> To: Edwin Culp Cc: Bill Paul , 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 On Thu, 30 Sep 1999, Edwin Culp wrote: > Did it and got these messages: > > mx0: at device 16.0 on pci0 > mx0: couldn't map ports/memory > device_probe_and_attach: mx0 attach returned 6 > > I must be missing something else. Tell your computer you're not using a PnP OS (it's a BIOS thing). Otherwise it won't assign stuff and FreeBSD can't really do much then. - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 21:40: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from bamboo.verinet.com (bamboo.verinet.com [204.144.246.5]) by hub.freebsd.org (Postfix) with ESMTP id EDE0514BC4 for ; Sun, 31 Oct 1999 21:40:00 -0800 (PST) (envelope-from hibma@skylink.it) Received: from henny (cherry41.verinet.com [207.174.160.230]) by bamboo.verinet.com (8.9.3/8.9.3) with SMTP id WAA29023; Sun, 31 Oct 1999 22:39:47 -0700 Date: Sun, 31 Oct 1999 21:39:33 -0700 (MST) From: Nick Hibma X-Sender: n_hibma@henny Reply-To: Nick Hibma To: Garrett Wollman Cc: Christopher Masto , usb-bsd@egroups.com, current@freebsd.org Subject: Re: VESA module breaks USB? In-Reply-To: <199910291505.LAA95902@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ohci0: irq 9 at device 11.0 on pci0 > > +ohci_waitintr: timeout > > IRQ 9 is shared with the VGA controller. Perhaps calling the VESA > BIOS caused it to do something strange that interfered with the > delivery of this interrupt on your motherboard. No, this has something to do with soft resetting vs. hard resetting. It might be that this is related to soft rebooting out of Windows. Try switching off and on your machine. I've seen this before but not yet spent the time to fix it. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 31 21:52: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 3CE6314E6F for ; Sun, 31 Oct 1999 21:52:04 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id AAA27583; Mon, 1 Nov 1999 00:51:55 -0500 (EST) Message-ID: <19991101005154.A27488@netmonger.net> Date: Mon, 1 Nov 1999 00:51:55 -0500 From: Christopher Masto To: Nick Hibma , Garrett Wollman Cc: usb-bsd@egroups.com, current@freebsd.org Subject: Re: VESA module breaks USB? References: <199910291505.LAA95902@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Sun, Oct 31, 1999 at 09:39:33PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 31, 1999 at 09:39:33PM -0700, Nick Hibma wrote: > > > ohci0: irq 9 at device 11.0 on pci0 > > > +ohci_waitintr: timeout > > > > IRQ 9 is shared with the VGA controller. Perhaps calling the VESA > > BIOS caused it to do something strange that interfered with the > > delivery of this interrupt on your motherboard. > > No, this has something to do with soft resetting vs. hard > resetting. It might be that this is related to soft rebooting out of > Windows. Try switching off and on your machine. I don't have Windows, but I can try a hard boot at some point and see if it helps. I can also try to fiddle with the IRQs just in case, but they are after all being assigned by FreeBSD. For now I've just turned off VESA, but I think it is going to become non-optional at some point and I'd hate to see my USB go away. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Sun Oct 31 23:14:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 922F014F9A for ; Sun, 31 Oct 1999 23:14:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA34280; Sun, 31 Oct 1999 23:14:37 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA43949; Sun, 31 Oct 1999 23:14:36 -0800 (PST) (envelope-from obrien) Date: Sun, 31 Oct 1999 23:14:35 -0800 From: "David O'Brien" To: Vincent Poy Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails Message-ID: <19991031231435.C10904@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <79049.941312718@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from vince@venus.GAIANET.NET on Sat, Oct 30, 1999 at 02:43:47PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 30, 1999 at 02:43:47PM -0700, Vincent Poy wrote: > > Yes, I am still running -current. I read the -current mailing > list on a more regular basis than most of the people out there. By what measure? I think you've shown the opposite. > I have always read the -current mailing list but you have to > remember that by the time I do the update, the known problem should > already have been gone. Hum... From E-day and C-day you didn't learn that not all things are "problems"? > I did read the UPDATING file and search the list as soon as I posted > and fixed the problem on my own. I was just worried that rebooting > with a new kernel before a world build might actually render the system > bootless. Aren't you enough of a FreeBSD sysadmin to know your previous kernel is available as /kernel.old and that you can specify the kernel used at the boot prompt? -- -- David (obrien@NUXI.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 31 23:19:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 51D9714F9A; Sun, 31 Oct 1999 23:19:10 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id XAA10534; Sun, 31 Oct 1999 23:18:52 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Sun, 31 Oct 1999 23:18:52 -0800 (PST) From: Vincent Poy To: "David O'Brien" Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: <19991031231435.C10904@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 Sun, 31 Oct 1999, David O'Brien wrote: > On Sat, Oct 30, 1999 at 02:43:47PM -0700, Vincent Poy wrote: > > > > Yes, I am still running -current. I read the -current mailing > > list on a more regular basis than most of the people out there. > > By what measure? I think you've shown the opposite. I guess I better say that I'll read the lists more slowly next time. > > I have always read the -current mailing list but you have to > > remember that by the time I do the update, the known problem should > > already have been gone. > > Hum... From E-day and C-day you didn't learn that not all things are > "problems"? I never said they were. > > I did read the UPDATING file and search the list as soon as I posted > > and fixed the problem on my own. I was just worried that rebooting > > with a new kernel before a world build might actually render the system > > bootless. > > Aren't you enough of a FreeBSD sysadmin to know your previous kernel is > available as /kernel.old and that you can specify the kernel used at the > boot prompt? That would work if you were sitting in front of the machines. All my machines are over 500 miles away. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 1:58:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 06DCC14D06 for ; Mon, 1 Nov 1999 01:58:33 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA68294; Mon, 1 Nov 1999 09:58:42 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 1 Nov 1999 09:58:42 +0000 (GMT) From: Doug Rabson To: Donn Miller Cc: current@freebsd.org Subject: Re: ESS sound drivers and 4.0-current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Donn Miller wrote: > I believe the ESS drivers weren't committed to 4.0-current yet. When I > grep ' ESS ' in /sys/i386/isa/sound, the only thing I can come up with is > the ESS support that was in the old voxware sound code. Sanpei, who is > developing the ESS sound drivers, says they were committed to the newpcm > drivers. I believe they were not added yet. > > >From http://home.jp.freebsd.org/~sanpei/: > > tarball for 4-current --> our ESS(ISA) code was commited to newpcm driver > in 4.0-current(1999/09/04) The sound drivers for -current are in sys/dev/pcm. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 2: 9: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id ED6E514D06 for ; Mon, 1 Nov 1999 02:08:38 -0800 (PST) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id MAA03588; Mon, 1 Nov 1999 12:07:43 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199911011007.MAA03588@oskar.dev.nanoteq.co.za> Subject: Re: ESS sound drivers and 4.0-current In-Reply-To: from Doug Rabson at "Nov 1, 99 09:58:42 am" To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 1 Nov 1999 12:07:43 +0200 (SAT) Cc: dmmiller@cvzoom.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 > On Sun, 31 Oct 1999, Donn Miller wrote: > > > I believe the ESS drivers weren't committed to 4.0-current yet. When I > > grep ' ESS ' in /sys/i386/isa/sound, the only thing I can come up with is > > the ESS support that was in the old voxware sound code. Sanpei, who is > > developing the ESS sound drivers, says they were committed to the newpcm > > drivers. I believe they were not added yet. > > > > >From http://home.jp.freebsd.org/~sanpei/: > > > > tarball for 4-current --> our ESS(ISA) code was commited to newpcm driver > > in 4.0-current(1999/09/04) > > The sound drivers for -current are in sys/dev/pcm. I have made a change to the ESS code in the pcm/isa/sb.c to allow my ESS1869 card to change the volume in both channels ... I'm running current of a few days ago. Previously the right hand channel stayed at one volume no matter what the mixer tells it. I have previously sent and email with the changes, but I'm happy to do it again :) ... It works for my card, but I don't know if it breaks anything else. Reinier -------- snip ------ snip ------- snip ------ jarrow# cvs diff -c sb.c Index: sb.c =================================================================== RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v retrieving revision 1.29 diff -c -r1.29 sb.c *** sb.c 1999/10/16 15:57:33 1.29 --- sb.c 1999/11/01 10:05:41 *************** *** 1191,1197 **** val = sb_getmixer(sb, regoffs); change_bits(iomap, &val, dev, LEFT_CHN, left); sb_setmixer(sb, regoffs, val); ! if ((*iomap)[dev][RIGHT_CHN].regno != regoffs) { /* Change register */ regoffs = (*iomap)[dev][RIGHT_CHN].regno; if (regoffs != 0) { val = sb_getmixer(sb, regoffs); /* Read the new one */ --- 1191,1197 ---- val = sb_getmixer(sb, regoffs); change_bits(iomap, &val, dev, LEFT_CHN, left); sb_setmixer(sb, regoffs, val); ! if (((*iomap)[dev][RIGHT_CHN].regno != regoffs) || (sb->bd_flags & BD_F_ESS)) { /* Change register */ regoffs = (*iomap)[dev][RIGHT_CHN].regno; if (regoffs != 0) { val = sb_getmixer(sb, regoffs); /* Read the new one */ > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > 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 Nov 1 2:10:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 9400914C1C for ; Mon, 1 Nov 1999 02:10:51 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11iEPt-000NbF-00; Mon, 01 Nov 1999 12:10:21 +0200 From: Sheldon Hearn To: "Chris D. Faulhaber" Cc: Marcel Moolenaar , current@FreeBSD.ORG Subject: Re: make buildworld problem... In-reply-to: Your message of "Fri, 29 Oct 1999 08:46:29 -0400." Date: Mon, 01 Nov 1999 12:10:21 +0200 Message-ID: <90720.941451021@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999 08:46:29 -0400, "Chris D. Faulhaber" wrote: > As an interim hack, would the following patch, which verifies > kern.osreldate >= 400011, suffice? I'd be in favour of this if all the changes were associated with comments containing ``XXX required for sigset_t migration''. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 2:21:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id D42A514E04 for ; Mon, 1 Nov 1999 02:21:33 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm202.cvzoom.net (lcm202.cvzoom.net [208.230.69.202]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id FAA16466; Mon, 1 Nov 1999 05:02:10 -0500 (EST) Date: Mon, 1 Nov 1999 05:19:53 -0500 (EST) From: Donn Miller To: Reinier Bezuidenhout Cc: Doug Rabson , current@FreeBSD.ORG Subject: Re: ESS sound drivers and 4.0-current In-Reply-To: <199911011007.MAA03588@oskar.dev.nanoteq.co.za> 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 Thanks for the patch; I'll try it. I have the ESS 1868 isa card. The problem I'm having isn't really volume problems. When I use RealPlayer 5.0, certain realaudio clips play through extremely fast, and I can hear the sound in bursts along the way. The speed/sample rate itself doesn't increase, but the entire clip whizzes by extremely fast, and I hear short bursts of the clip. Maybe the clip isn't being memory mapped properly? I also get messages like this via syslogd: Oct 31 08:49:06 /kernel: WARNING: driver snd should register devices with make_ dev() (dev_t = "#snd/6") Oct 31 10:21:40 /kernel: WARNING: driver snd should register devices with make_ dev() (dev_t = "#snd/6") Nov 1 03:00:22 /kernel: WARNING: driver snd should register devices with make_ dev() (dev_t = "#snd/19") Maybe this has something to do with it? - Donn On Mon, 1 Nov 1999, Reinier Bezuidenhout wrote: > I have made a change to the ESS code in the pcm/isa/sb.c to allow > my ESS1869 card to change the volume in both channels ... I'm running > current of a few days ago. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 2:27:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id A500F14E04 for ; Mon, 1 Nov 1999 02:27:16 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (u1033.seaple.icc.ne.jp [210.170.9.33]) by titanium.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id TAA21382; Mon, 1 Nov 1999 19:27:10 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id TAA28696; Mon, 1 Nov 1999 19:27:05 +0900 (JST) Date: Mon, 1 Nov 1999 19:27:05 +0900 (JST) Message-Id: <199911011027.TAA28696@lavender.yy.cs.keio.ac.jp> To: dmmiller@cvzoom.net Cc: current@FreeBSD.ORG, sanpei@sanpei.org, fwkg7679@mb.infoweb.ne.jp Subject: Re: ESS sound drivers and 4.0-current In-Reply-To: Your message of "Mon, 1 Nov 1999 06:19:04 JST". From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dmmiller@cvzoom.net wrote: >> I believe the ESS drivers weren't committed to 4.0-current yet. When I >> grep ' ESS ' in /sys/i386/isa/sound, the only thing I can come up with is >> the ESS support that was in the old voxware sound code. Sanpei, who is >> developing the ESS sound drivers, says they were committed to the newpcm >> drivers. I believe they were not added yet. >> >> From http://home.jp.freebsd.org/~sanpei/: >> >> tarball for 4-current --> our ESS(ISA) code was commited to newpcm driver >> in 4.0-current(1999/09/04) ESS(ISA) code was imported to newpcm sound driver(sys/dev/pcm) by Cameron Grant(thank for your committing). Please check these directories and below cvs change log http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/dev/pcm/isa/sb.c ------------------------------------------------- Message-Id: <199909041823.LAA76446@freefall.freebsd.org> From: Cameron Grant Date: Sat, 4 Sep 1999 11:23:24 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/dev/pcm/isa sb.c Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk cg 1999/09/04 11:23:23 PDT Modified files: sys/dev/pcm/isa sb.c Log: incorporate better ess support Obtained From: KUROSAWA Takahiro Tested By: peter Revision Changes Path 1.21 +276 -69 src/sys/dev/pcm/isa/sb.c ------------------------------------------------- But -current code has some probem. Kurosawa-san reported problem and send patch to Grant. But Grant is too busy to commit about it, I think. MIHIRA Sanpei Yoshiro Yokohama, Japan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 2:30:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.5]) by hub.freebsd.org (Postfix) with ESMTP id 8741114F91 for ; Mon, 1 Nov 1999 02:30:27 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: by server.amis.net (Postfix, from userid 66) id D8548D5C29; Mon, 1 Nov 1999 11:30:26 +0100 (CET) Received: by gold.amis.net (Postfix, from userid 1000) id B76F41D5F; Mon, 1 Nov 1999 11:29:51 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id AFD1A57ED; Mon, 1 Nov 1999 11:29:51 +0100 (CET) Date: Mon, 1 Nov 1999 11:29:51 +0100 (CET) From: Blaz Zupan To: Donn Miller Cc: Reinier Bezuidenhout , Doug Rabson , current@FreeBSD.ORG Subject: Re: ESS sound drivers and 4.0-current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Nov 1999, Donn Miller wrote: > Thanks for the patch; I'll try it. I have the ESS 1868 isa card. The > problem I'm having isn't really volume problems. When I use RealPlayer > 5.0, certain realaudio clips play through extremely fast, and I can hear > the sound in bursts along the way. The speed/sample rate itself doesn't > increase, but the entire clip whizzes by extremely fast, and I hear > short bursts of the clip. Maybe the clip isn't being memory mapped > properly? I believe this to be a problem in newpcm, as it appears with my onboard soundcard too. Also, when playing MP3's, sometimes the machine decides to play static (white noise) instead of the sample. Here is what I have: pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 unknown0: at port 0x211 on isa0 This problem is present since the switch to newpcm. Before newpcm, I did not experience problems with RealPlayer or my MP3 player (no matter which one). I'm running -current as of yesterday and the sound chip is on board on a Intel AN430TX motherboard. Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 2:42:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 77BE614A08 for ; Mon, 1 Nov 1999 02:42:16 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (u1033.seaple.icc.ne.jp [210.170.9.33]) by titanium.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id TAA21744; Mon, 1 Nov 1999 19:41:48 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id TAA28726; Mon, 1 Nov 1999 19:41:45 +0900 (JST) Date: Mon, 1 Nov 1999 19:41:45 +0900 (JST) Message-Id: <199911011041.TAA28726@lavender.yy.cs.keio.ac.jp> To: dmmiller@cvzoom.net Cc: rbezuide@oskar.dev.nanoteq.co.za, dfr@nlsystems.com, current@FreeBSD.ORG, sanpei@sanpei.org, fwkg7679@mb.infoweb.ne.jp Subject: Re: ESS sound drivers and 4.0-current In-Reply-To: Your message of "Mon, 1 Nov 1999 19:19:53 JST". From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Thanks for the patch; I'll try it. I have the ESS 1868 isa card. The >> problem I'm having isn't really volume problems. When I use RealPlayer >> 5.0, certain realaudio clips play through extremely fast, and I can hear >> the sound in bursts along the way. The speed/sample rate itself doesn't >> increase, but the entire clip whizzes by extremely fast, and I hear >> short bursts of the clip. Maybe the clip isn't being memory mapped >> properly? try below patch for -current which was written by Kurosawa-san . --- sys/dev/pcm/isa/sb.c.org Tue Sep 7 17:42:44 1999 +++ sys/dev/pcm/isa/sb.c Mon Sep 13 23:38:45 1999 @@ -880,9 +880,9 @@ ess_format(struct sb_chinfo *ch, u_int32_t format) { struct sb_info *sb = ch->parent; - int play = (ch->dir == PCMDIR_PLAY)? 1 : 0; - int b16 = (ch->fmt & AFMT_S16_LE)? 1 : 0; - int stereo = (ch->fmt & AFMT_STEREO)? 1 : 0; + int play = (format == PCMDIR_PLAY)? 1 : 0; + int b16 = (format & AFMT_S16_LE)? 1 : 0; + int stereo = (format & AFMT_STEREO)? 1 : 0; u_char c; ch->fmt = format; sb_reset_dsp(sb); --- sys/dev/pcm/dsp.c.orig Sun Sep 5 02:03:59 1999 +++ sys/dev/pcm/dsp.c Mon Sep 13 23:40:10 1999 @@ -54,8 +54,18 @@ if ((d->flags & SD_F_PRIO_SET) == SD_F_PRIO_SET) panic("read and write both prioritised"); if (d->flags & SD_F_SIMPLEX) { +#if 0 *rdch = (d->flags & SD_F_PRIO_RD)? d->arec[chan] : &d->fakechan; *wrch = (d->flags & SD_F_PRIO_WR)? d->aplay[chan] : &d->fakechan; +#else + if (!(d->flags & SD_F_PRIO_SET)) { + *rdch = d->arec[chan]? d->arec[chan] : &d->fakechan; + *wrch = d->aplay[chan]? d->aplay[chan] : &d->fakechan; + } else { + *rdch = (d->flags & SD_F_PRIO_RD)? d->arec[chan] : &d->fakechan; + *wrch = (d->flags & SD_F_PRIO_WR)? d->aplay[chan] : &d->fakechan; + } +#endif } else { *rdch = d->arec[chan]; *wrch = d->aplay[chan]; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 6: 5: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26]) by hub.freebsd.org (Postfix) with ESMTP id 57F0514FF9; Mon, 1 Nov 1999 06:04:59 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta2.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FKI002PFV1JI6@mta2.rcsntx.swbell.net>; Mon, 1 Nov 1999 08:03:20 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id IAA02129; Mon, 01 Nov 1999 08:04:18 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 01 Nov 1999 08:04:18 -0600 From: Chris Costello Subject: Re: -current build fails In-reply-to: To: Vincent Poy Cc: David O'Brien , FreeBSD-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991101080418.B602@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <19991031231435.C10904@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 31, 1999, Vincent Poy wrote: > > Aren't you enough of a FreeBSD sysadmin to know your previous kernel is > > available as /kernel.old and that you can specify the kernel used at the > > boot prompt? > > That would work if you were sitting in front of the machines. All > my machines are over 500 miles away. That's the perfect example of how and where not to use -CURRENT. -- |Chris Costello |You had mail, but the super-user read it, and deleted it! `--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 6:22: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 06E6414C90 for ; Mon, 1 Nov 1999 06:21:55 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id XAA05337; Mon, 1 Nov 1999 23:20:50 +0900 (JST) Message-Id: <199911011420.XAA05337@rina.r.dl.itc.u-tokyo.ac.jp> To: dmmiller@cvzoom.net Cc: rbezuide@oskar.dev.nanoteq.co.za, dfr@nlsystems.com, current@FreeBSD.ORG Cc: Seigo Tanimura Subject: Re: ESS sound drivers and 4.0-current From: Seigo Tanimura In-Reply-To: Your message of "Mon, 1 Nov 1999 05:19:53 -0500 (EST)" References: 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: Mon, 01 Nov 1999 23:20:50 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Nov 1999 05:19:53 -0500 (EST), Donn Miller said: dmmiller> I also get messages like this via syslogd: dmmiller> Oct 31 08:49:06 /kernel: WARNING: driver snd should register devices with dmmiller> make_ dmmiller> dev() (dev_t = "#snd/6") (snip) newpcm is still using cdevsw_add() to register the driver handlers. I will fix that, thanks. Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 7: 1:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 533A714BC2 for ; Mon, 1 Nov 1999 07:01:39 -0800 (PST) (envelope-from gadde@cs.duke.edu) Received: from cod.cs.duke.edu (cod.cs.duke.edu [152.3.140.124]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id KAA28601 for ; Mon, 1 Nov 1999 10:01:38 -0500 (EST) Received: (gadde@localhost) by cod.cs.duke.edu (8.8.5/8.6.9) id KAA03207 for current@FreeBSD.ORG; Mon, 1 Nov 1999 10:01:37 -0500 (EST) Date: Mon, 1 Nov 1999 10:01:37 -0500 From: Syam Gadde To: current@FreeBSD.ORG Subject: Re: ESS sound drivers and 4.0-current Message-ID: <19991101100136.A3202@cod.cs.duke.edu> References: <199911011007.MAA03588@oskar.dev.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199911011007.MAA03588@oskar.dev.nanoteq.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Reinier Bezuidenhout (rbezuide@oskar.dev.nanoteq.co.za): > I have made a change to the ESS code in the pcm/isa/sb.c to allow > my ESS1869 card to change the volume in both channels ... I'm running > current of a few days ago. I experienced this problem too... same chip. I tried a similar patch to yours weeks ago, but now I'm more convinced that the right way to do it is this (included below). Even if "val" doesn't change, don't you still need to change the bits for the right channel? (as the old pcm code does) -syam Index: sb.c =================================================================== RCS file: /scratch/ncvs/src/sys/dev/pcm/isa/sb.c,v retrieving revision 1.29 diff -u -r1.29 sb.c --- sb.c 1999/10/16 15:57:33 1.29 +++ sb.c 1999/10/26 13:29:09 @@ -1195,10 +1195,10 @@ regoffs = (*iomap)[dev][RIGHT_CHN].regno; if (regoffs != 0) { val = sb_getmixer(sb, regoffs); /* Read the new one */ - change_bits(iomap, &val, dev, RIGHT_CHN, right); - sb_setmixer(sb, regoffs, val); } else right = left; } else right = left; + change_bits(iomap, &val, dev, RIGHT_CHN, right); + sb_setmixer(sb, regoffs, val); return left | (right << 8); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 12: 4:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id B5FE514A2F for ; Mon, 1 Nov 1999 12:04:42 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 8FACA3E2E; Mon, 1 Nov 1999 21:04:40 +0100 (CET) Date: Mon, 1 Nov 1999 21:04:40 +0100 From: Jesper Skriver To: current@FreeBSD.org Subject: ep problem with 4.0-19991101-CURRENT snapshot Message-ID: <19991101210440.A12410@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to get a real operating system on my Compaq presario 1260. I boot from the pccard floppies, and have a 3com 3c589c in pcmcia slot0, sysinstall finds this with default setting for IRQ and memory address, and does not find it with any other combination. sysinstall can assign a ip address via. DHCP, but the machine cannot be ping'ed from other hosts on the lan, same if I manually configure ep0 via ifconfig. This machine has a 'TI PCI 1131 PCI-CardBus Bridge' Any ideas ? Or ideas on how to get debug output that can help in debugging this problem ? A couple of notes: My IBM ThinkPad 560 works fine with the same 3c589c card both in 3.3-STABLE and 4.0-CURRENT, and the same card also works in Win98 on the Compaq. 3.3-STABLE doesn't find the card when it's in the Compaq, neither does NetBSD 1.4.1 or Redhat linux (yes, I'm getting desperate to get rid of windows on this machine ...) /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 12:32:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.sitaranetworks.com (apollo.sitaranetworks.com [199.103.141.105]) by hub.freebsd.org (Postfix) with ESMTP id 051BE154C5 for ; Mon, 1 Nov 1999 12:30:57 -0800 (PST) (envelope-from grog@lemis.com) Message-ID: <19991028110624.33678@mojave.worldwide.lemis.com> Date: Thu, 28 Oct 1999 11:06:24 -0400 From: Greg Lehey To: Garrett Wollman , Poul-Henning Kamp Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: lsof + namecache References: <312.941094594@critter.freebsd.dk> <199910281452.KAA91520@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199910281452.KAA91520@khavrinen.lcs.mit.edu>; from Garrett Wollman on Thu, Oct 28, 1999 at 10:52:30AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 28 October 1999 at 10:52:30 -0400, Garrett Wollman wrote: > < said: > > > The lsof functionality should in my opinion be added to the system, > > and the necessary hooks should be added to the kernel using sysctl. > > fstat(1). It doesn't quite have the functionality. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 12:49:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 30295152AD for ; Mon, 1 Nov 1999 12:48:45 -0800 (PST) (envelope-from grog@lemis.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id HAA29981; Tue, 2 Nov 1999 07:17:57 +1030 (CST) (envelope-from grog@lemis.com) Message-ID: <19991101141751.16107@mojave.sitaranetworks.com> Date: Mon, 1 Nov 1999 14:17:51 -0500 From: Greg Lehey To: Ollivier Robert , current@FreeBSD.ORG Subject: Re: /usr/share/calendar/calendar.freebsd ? Reply-To: Greg Lehey References: <19991031162419.A8415@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19991031162419.A8415@keltia.freenix.fr>; from Ollivier Robert on Sun, Oct 31, 1999 at 04:24:19PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 31 October 1999 at 16:24:19 +0100, Ollivier Robert wrote: > According to Satoshi - Ports Wraith - Asami: >> let her commit things. Ok, not without me watching over her shoulder.... > > Experience shows that even this is not enough to prevent accidents (Hi Greg!). > :-) I've never let my horses commit anything. Well, I won't admit it, anyway. But I still think their birthdays belong in the list :-) Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 12:50: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 6F3C115362; Mon, 1 Nov 1999 12:49:54 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id MAA14882; Mon, 1 Nov 1999 12:49:05 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Mon, 1 Nov 1999 12:49:05 -0800 (PST) From: Vincent Poy To: Chris Costello Cc: "David O'Brien" , FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: <19991101080418.B602@holly.calldei.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, 1 Nov 1999, Chris Costello wrote: > On Sun, Oct 31, 1999, Vincent Poy wrote: > > > Aren't you enough of a FreeBSD sysadmin to know your previous kernel is > > > available as /kernel.old and that you can specify the kernel used at the > > > boot prompt? > > > > That would work if you were sitting in front of the machines. All > > my machines are over 500 miles away. > > That's the perfect example of how and where not to use > -CURRENT. And your argument could be not to use -STABLE or -RELEASE since both would have the same problems. Like I said before, it's not which version that is run since one can just make a mistake in /etc/rc.conf and the machine would boot in a continous loop and panic. I was just saying running a kernel with new sys tree on a older binary tree might not always work even though we hope to have it that way. There is a difference between make world then new kernel and then reboot then make new kernel and then reboot and then build world and then make another kernel. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 13:48:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id E5B3F14E2A for ; Mon, 1 Nov 1999 13:48:00 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id PAA01667; Mon, 1 Nov 1999 15:47:41 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Mon, 1 Nov 1999 15:47:41 -0600 (CST) From: David Scheidt To: Greg Lehey Cc: Ollivier Robert , current@FreeBSD.ORG Subject: Re: /usr/share/calendar/calendar.freebsd ? In-Reply-To: <19991101141751.16107@mojave.sitaranetworks.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, 1 Nov 1999, Greg Lehey wrote: > I've never let my horses commit anything. Well, I won't admit it, > anyway. > > But I still think their birthdays belong in the list :-) > Can't remember 1 January? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 15:10:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id 2374A14FFB; Mon, 1 Nov 1999 15:10:17 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FKJ00AI1KAZGX@mta3.rcsntx.swbell.net>; Mon, 1 Nov 1999 17:09:00 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id RAA03501; Mon, 01 Nov 1999 17:09:57 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 01 Nov 1999 17:09:57 -0600 From: Chris Costello Subject: Re: -current build fails In-reply-to: To: Vincent Poy Cc: David O'Brien , FreeBSD-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991101170957.I602@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <19991101080418.B602@holly.calldei.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 01, 1999, Vincent Poy wrote: > > That's the perfect example of how and where not to use > > -CURRENT. > > And your argument could be not to use -STABLE or -RELEASE since > both would have the same problems. Like I said before, it's not which Quite the reverse. You _should_ anticipate an unbootable system at each upgrade of -CURRENT. We're not trying to make another -STABLE here. -- |Chris Costello |May the force be... your umbrella! - Plucky Duck `------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 15:16:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 231FC153AB; Mon, 1 Nov 1999 15:15:57 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id PAA15877; Mon, 1 Nov 1999 15:15:29 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Mon, 1 Nov 1999 15:15:29 -0800 (PST) From: Vincent Poy To: Chris Costello Cc: "David O'Brien" , FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: <19991101170957.I602@holly.calldei.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, 1 Nov 1999, Chris Costello wrote: > On Mon, Nov 01, 1999, Vincent Poy wrote: > > > That's the perfect example of how and where not to use > > > -CURRENT. > > > > And your argument could be not to use -STABLE or -RELEASE since > > both would have the same problems. Like I said before, it's not which > > Quite the reverse. You _should_ anticipate an unbootable > system at each upgrade of -CURRENT. We're not trying to make > another -STABLE here. That is a known factor but I'm just saying booting with a newer kernel than the bins adds up another issue altogether. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 16:10:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from sinai.dhs.org (adsl-216-103-54-61.dsl.lsan03.pacbell.net [216.103.54.61]) by hub.freebsd.org (Postfix) with ESMTP id CDE4A14A03; Mon, 1 Nov 1999 16:10:23 -0800 (PST) (envelope-from sab@sinai.dhs.org) Received: from localhost (sab@localhost) by sinai.dhs.org (8.9.3/8.9.2) with ESMTP id QAA39781; Mon, 1 Nov 1999 16:02:39 -0800 (PST) (envelope-from sab@sinai.dhs.org) Date: Mon, 1 Nov 1999 16:02:39 -0800 (PST) From: Scott Benjamin To: current@freebsd.org, hardware@freebsd.org Subject: IDA driver issues upon installation. Probing devices hangs (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 am trying to install the stable snapshot from 10301999 on a compaq proliant 4500 with a smart array controller. I recompile the installation kernel and dropped it on the disk. The newly compile kernel has the ida driver included (as the drives are on that controller). It finds the controller and the logical drives, but when the installation program starts, it hangs at Probing for devices. The ida driver also reports "irq with no handler" when the kernel finds the device (prior to the probing screen). I've tried moving irq's around and removing some other cards but nothing. If I boot without the ida driver, it works ifne except that I don't have any drives to install on. If you need any more information please let me know. Thanks! Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 16:37:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com. (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with SMTP id CD6E215329 for ; Mon, 1 Nov 1999 16:37:44 -0800 (PST) (envelope-from bugs@freebsd.netcom.com) Received: by freebsd.netcom.com. (SMI-8.6/SMI-SVR4) id SAA13823; Mon, 1 Nov 1999 18:37:43 -0600 From: bugs@freebsd.netcom.com (Mark Hittinger) Message-Id: <199911020037.SAA13823@freebsd.netcom.com.> Subject: ep0 3com etherlink III still unhappy To: freebsd-current@freebsd.org Date: Mon, 1 Nov 1999 18:37:42 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: Ethernet address ff:ff:ff:ff:ff:ff ep1: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 ep1: Ethernet address 00:a0:24:a1:9a:1e The card is actually 0x300, not 0x210. Disabling pnp isn't a work around any longer. This is just an FYI Later Mark Hittinger Mindspring/Netcom/Dallas bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 17:27:11 1999 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 5CCF214C4A for ; Mon, 1 Nov 1999 17:27:08 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id UAA00960; Mon, 1 Nov 1999 20:27:04 -0500 (EST) Date: Mon, 1 Nov 1999 20:27:04 -0500 (EST) From: "Matthew N. Dodd" To: Mark Hittinger Cc: freebsd-current@FreeBSD.ORG Subject: Re: ep0 3com etherlink III still unhappy In-Reply-To: <199911020037.SAA13823@freebsd.netcom.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 There appear to be some settings in the 3c509 config program that prevent the ISA enumerator from recognizing cards in PnP mode. I'm unsure what they are at this point. On Mon, 1 Nov 1999, Mark Hittinger wrote: > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: Ethernet address ff:ff:ff:ff:ff:ff > ep1: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > ep1: Ethernet address 00:a0:24:a1:9a:1e > > The card is actually 0x300, not 0x210. Disabling pnp isn't a work around > any longer. The card is actually at whatever the PnP system sets it up to be at. FreeBSD can and does reassign PnP resources. If you are going to use PnP mode, use ep1 for now. If you turn off PnP mode, you'll be able to use ep0. I hope to solve this when I get the 3c509/3c59x doc books. -- | 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 Nov 1 23:28:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id DA34014EC1 for ; Mon, 1 Nov 1999 23:28:20 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.1) id KAA10045 for current@freebsd.org; Tue, 2 Nov 1999 10:28:17 +0300 (MSK) (envelope-from ache) Date: Tue, 2 Nov 1999 10:28:16 +0300 From: "Andrey A. Chernov" To: current@freebsd.org Subject: netstat can't be compiled due to netgraph Message-ID: <19991102102816.A10035@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /usr/src/usr.bin/netstat/netgraph.c:51: netgraph.h: No such file or directory Please fix this thing. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 23:36:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (hermes.dialup.ru [194.87.16.230]) by hub.freebsd.org (Postfix) with ESMTP id C974714EC1 for ; Mon, 1 Nov 1999 23:35:37 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.1) id KAA12525 for current@freebsd.org; Tue, 2 Nov 1999 10:35:32 +0300 (MSK) (envelope-from ache) Date: Tue, 2 Nov 1999 10:34:52 +0300 From: "Andrey A. Chernov" To: corrent@freebsd.org Subject: mount_nwfs can't be compiled due to netncp Message-ID: <19991102103452.A12496@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /usr/src/sbin/mount_nwfs/mount_nwfs.c:50: netncp/ncp_lib.h: No such file or directory /usr/src/sbin/mount_nwfs/mount_nwfs.c:51: netncp/ncp_rcfile.h: No such file or directory Please fix. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 23:51: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 1104414F1D; Mon, 1 Nov 1999 23:50:53 -0800 (PST) Date: Mon, 1 Nov 1999 23:50:53 -0800 From: "Andrey A. Chernov" To: current@freebsd.org Subject: Re: netstat can't be compiled due to netgraph Message-ID: <19991101235053.A2141@freebsd.org> References: <19991102102816.A10035@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991102102816.A10035@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Nov 02, 1999 at 10:28:16AM +0300 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 02, 1999 at 10:28:16AM +0300, Andrey A. Chernov wrote: > /usr/src/usr.bin/netstat/netgraph.c:51: netgraph.h: No such file or > directory > Please fix this thing. Sorry false alarm, libnetgraph must be installed first -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 1 23:52:19 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 3A10F14A21; Mon, 1 Nov 1999 23:52:18 -0800 (PST) Date: Mon, 1 Nov 1999 23:52:18 -0800 From: "Andrey A. Chernov" To: current@freebsd.org Subject: Re: mount_nwfs can't be compiled due to netncp Message-ID: <19991101235218.B2141@freebsd.org> References: <19991102103452.A12496@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991102103452.A12496@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Nov 02, 1999 at 10:34:52AM +0300 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 02, 1999 at 10:34:52AM +0300, Andrey A. Chernov wrote: > /usr/src/sbin/mount_nwfs/mount_nwfs.c:50: netncp/ncp_lib.h: No such file > or directory > /usr/src/sbin/mount_nwfs/mount_nwfs.c:51: netncp/ncp_rcfile.h: No such > file or directory > > Please fix. Sorry false alarm, libncp must be installed first -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 0:18:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 74E0014F51 for ; Tue, 2 Nov 1999 00:18:05 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id AAA78751; Tue, 2 Nov 1999 00:17:54 -0800 (PST) Date: Tue, 2 Nov 1999 00:17:53 -0800 (PST) From: Julian Elischer To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: netstat can't be compiled due to netgraph In-Reply-To: <19991102102816.A10035@nagual.pp.ru> 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 have you done a make libs? netgraph.h is installed in 'make world' as part of lib/libnetgraph cd /usr/src/lib/libnetgraph make depend make make install (make clean) On Tue, 2 Nov 1999, Andrey A. Chernov wrote: > /usr/src/usr.bin/netstat/netgraph.c:51: netgraph.h: No such file or > directory > Please fix this thing. > > > -- > Andrey A. Chernov > http://www.nagual.pp.ru/~ache/ > MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y > > > 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 Tue Nov 2 1:58:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8522F14F21 for ; Tue, 2 Nov 1999 01:58:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA29930; Tue, 2 Nov 1999 09:58:46 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 2 Nov 1999 09:58:46 +0000 (GMT) From: Doug Rabson To: Mark Hittinger Cc: freebsd-current@freebsd.org Subject: Re: ep0 3com etherlink III still unhappy In-Reply-To: <199911020037.SAA13823@freebsd.netcom.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, 1 Nov 1999, Mark Hittinger wrote: > > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: Ethernet address ff:ff:ff:ff:ff:ff > ep1: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > ep1: Ethernet address 00:a0:24:a1:9a:1e > > The card is actually 0x300, not 0x210. Disabling pnp isn't a work around > any longer. Does ep1 work (i.e. can you send and receive packets on ep1)? If so, you can probably change your kernel config to have just 'device ep0' which would allow the card to appear as ep0 again. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 1:59:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 073BF1533C for ; Tue, 2 Nov 1999 01:58:59 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id LAA51209 for current@freebsd.org; Tue, 2 Nov 1999 11:58:55 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911020958.LAA51209@zibbi.mikom.csir.co.za> Subject: GENERIC build broken To: current@freebsd.org Date: Tue, 2 Nov 1999 11:58:55 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (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 A GENERIC kernel build breaks here with: --------- sh ../../conf/newvers.sh GENERIC cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf vers.c linking kernel mfs_vfsops.o: In function `mfs_init': mfs_vfsops.o(.text+0x63d): undefined reference to `mountrootfsname' *** Error code 1 1 error --------- Is it just some unfinished commits? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 4: 6:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (hda.bicnet.net [208.220.68.243]) by hub.freebsd.org (Postfix) with ESMTP id E583A14F99 for ; Tue, 2 Nov 1999 04:06:01 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA20898; Tue, 2 Nov 1999 06:49:10 -0500 (EST) From: Peter Dufault Message-Id: <199911021149.GAA20898@hda.hda.com> Subject: Re: ep0 3com etherlink III still unhappy In-Reply-To: from Doug Rabson at "Nov 2, 99 09:58:46 am" To: dfr@nlsystems.com (Doug Rabson) Date: Tue, 2 Nov 1999 06:49:10 -0500 (EST) Cc: bugs@freebsd.netcom.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (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 > > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. ... > > ep0: Ethernet address ff:ff:ff:ff:ff:ff > > ep1: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > > ep1: Ethernet address 00:a0:24:a1:9a:1e I still have problems with probing ep's on one Cyrix system. One thing that has made it better is passing a bit delay down to elink_idseq, that is: > void > elink_idseq(u_char p, void (*bit_delay)(void)) > { > register int i; > register u_char c; > > c = 0xff; > for (i = 255; i; i--) { > (*bit_delay)(); > outb(ELINK_ID_PORT, c); > if (c & 0x80) { > c <<= 1; I haven't bothered committing this since it still fails 1 out of 6 times. Without this it fails 1 out of 3 times. If it logically makes sense that a delay is needed here (I don't have any docs) someone might add it. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 7: 2:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (hda.bicnet.net [208.220.68.243]) by hub.freebsd.org (Postfix) with ESMTP id 1970114A25 for ; Tue, 2 Nov 1999 07:02:02 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id JAA21488 for current@freebsd.org; Tue, 2 Nov 1999 09:56:39 -0500 (EST) From: Peter Dufault Message-Id: <199911021456.JAA21488@hda.hda.com> Subject: Ross Harvey's nice fixes and associated clean up To: current@freebsd.org Date: Tue, 2 Nov 1999 09:56:38 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've merged Ross Harvey's "nice" fixes and associated clean up from NetBSD in with my own scheduler hacks. They're at http://www.freebsd.org/~dufault via the "system" link. I won't promise much other than that the resulting kernel boots and runs with no obvious problems to my canned regression tests. There could yet be glaring problems. For the alpha people - I didn't add a separate scheduler clock, you'll have to do that on your own and modify kern_clock.c to not call "update_estcpu", instead call that from your scheduler clock. See Ross's work, my "update_estcpu" is the equivalent of his "sched_clock". If we keep this work I'll match his nomenclature. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 8:45:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 057A51565A; Tue, 2 Nov 1999 08:42:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA51592; Tue, 2 Nov 1999 08:42:30 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 08:42:30 -0800 (PST) From: Matthew Dillon Message-Id: <199911021642.IAA51592@apollo.backplane.com> To: John Hay Cc: msmith@freebsd.org, current@freebsd.org Subject: Re: GENERIC build broken References: <199911020958.LAA51209@zibbi.mikom.csir.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :A GENERIC kernel build breaks here with: : :--------- :sh ../../conf/newvers.sh GENERIC :cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf vers.c :linking kernel :mfs_vfsops.o: In function `mfs_init': :mfs_vfsops.o(.text+0x63d): undefined reference to `mountrootfsname' :*** Error code 1 :1 error :--------- : :Is it just some unfinished commits? : :John :-- :John Hay -- John.Hay@mikom.csir.co.za It looks like a dead global in mfs due to Mike's reorganization of the rootfs stuff. I'll let Mike do the trivial fix, though, since he broke it :-). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 8:55:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt050n71.san.rr.com (dt054n7c.san.rr.com [24.30.152.124]) by hub.freebsd.org (Postfix) with ESMTP id 5CDD914BD2 for ; Tue, 2 Nov 1999 08:54:36 -0800 (PST) (envelope-from DougB@simplenet.com) Received: from simplenet.com (master [10.0.0.2]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id IAA00749; Tue, 2 Nov 1999 08:53:54 -0800 (PST) (envelope-from DougB@simplenet.com) Message-ID: <381F1722.3F85DA1@simplenet.com> Date: Tue, 02 Nov 1999 08:53:54 -0800 From: Doug Barton X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved References: <199910271928.MAA35915@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > (Approved by jkh) > > /etc/make.conf.local will become /etc/make.conf and /etc/make.conf will > become /etc/defaults/make.conf. This change is long overdue. > > The sys.mk adjustment has already been committed. An email has been > sent to the CVS meisters to get /usr/src/etc/make.conf moved. > > make will dump out with an appropriate error and instructions if you > update your source tree and still have an /etc/make.conf.local. I like this change (kind of) but is it really necessary to cause make to exit if there is a make.conf.local? Why not have it read all 3? One of the things we talked about at the 'Con was that a three tiered system works well for rc.conf when you have a lot of machines sharing similar configuration details, but with some unique elements present on each machine. Perhaps I'm missing something, but how can make.conf.local be a bad thing? Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 9: 3:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 93AF314DC3 for ; Tue, 2 Nov 1999 09:03:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA51793; Tue, 2 Nov 1999 09:03:11 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 09:03:11 -0800 (PST) From: Matthew Dillon Message-Id: <199911021703.JAA51793@apollo.backplane.com> To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved References: <199910271928.MAA35915@apollo.backplane.com> <381F1722.3F85DA1@simplenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> sent to the CVS meisters to get /usr/src/etc/make.conf moved. :> :> make will dump out with an appropriate error and instructions if you :> update your source tree and still have an /etc/make.conf.local. : : I like this change (kind of) but is it really necessary to cause make :to exit if there is a make.conf.local? Why not have it read all 3? One :of the things we talked about at the 'Con was that a three tiered system :works well for rc.conf when you have a lot of machines sharing similar :configuration details, but with some unique elements present on each :machine. Perhaps I'm missing something, but how can make.conf.local be a :bad thing? : :Doug I think it is necessary to make it exit for now, because what we are really doing is a net-0 gain in files... turning what used to be functionality in /etc/make.conf.local into /etc/make.conf. The intent is not to add a third file. If the intent were to add a third configuration file then, sure, we could allow all three. But that isn't my intent. I am somewhat worried that people upgrading from 3.x to 4.x will get confused if that error message is not in there. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 9:10:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt050n71.san.rr.com (dt054n7c.san.rr.com [24.30.152.124]) by hub.freebsd.org (Postfix) with ESMTP id 2B83414BC9 for ; Tue, 2 Nov 1999 09:10:36 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id JAA00858; Tue, 2 Nov 1999 09:10:32 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <381F1B08.AF4E0585@gorean.org> Date: Tue, 02 Nov 1999 09:10:32 -0800 From: Doug Barton X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved References: <199910271928.MAA35915@apollo.backplane.com> <381F1722.3F85DA1@simplenet.com> <199911021703.JAA51793@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :> sent to the CVS meisters to get /usr/src/etc/make.conf moved. > :> > :> make will dump out with an appropriate error and instructions if you > :> update your source tree and still have an /etc/make.conf.local. > : > : I like this change (kind of) but is it really necessary to cause make > :to exit if there is a make.conf.local? Why not have it read all 3? One > :of the things we talked about at the 'Con was that a three tiered system > :works well for rc.conf when you have a lot of machines sharing similar > :configuration details, but with some unique elements present on each > :machine. Perhaps I'm missing something, but how can make.conf.local be a > :bad thing? > : > :Doug > > I think it is necessary to make it exit for now, because what we are > really doing is a net-0 gain in files... turning what used to be > functionality in /etc/make.conf.local into /etc/make.conf. The intent is > not to add a third file. If the intent were to add a third configuration > file then, sure, we could allow all three. But that isn't my intent. Ok, well put me on record as wanting three files. While I still have some reservations about the whole /etc/defaults thing, I believe that if we are going to use it we should use it to full advantage, offering people more functionality, not less. Unless I am missing something, the worst thing that could happen if someone had all three files is that the settings they want will get read from /etc/make.conf.local. The only time this causes a problem is if you change a default setting for something that was in the "old" make.conf file (evil), or change the name of a define in /etc/defaults/make.conf (_really_ evil). I'm a little behind in my freebsd mail, so forgive me if this has been covered. If not, I hope this will spark some conversation. Thanks, Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 9:46:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from s8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by hub.freebsd.org (Postfix) with ESMTP id 2D0FB14C4A for ; Tue, 2 Nov 1999 09:46:08 -0800 (PST) (envelope-from jcwells@u.washington.edu) Received: from localhost (jcw@localhost) by s8-37-26.student.washington.edu (8.9.3/8.9.3) with ESMTP id WAA03811; Tue, 2 Nov 1999 22:41:19 GMT (envelope-from jcwells@u.washington.edu) X-Authentication-Warning: s8-37-26.student.washington.edu: jcw owned process doing -bs Date: Tue, 2 Nov 1999 22:41:19 +0000 (GMT) From: "Jason C. Wells" X-Sender: jcw@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: Doug Barton Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved In-Reply-To: <381F1B08.AF4E0585@gorean.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, 2 Nov 1999, Doug Barton wrote: >> I think it is necessary to make it exit for now, because what we are >> really doing is a net-0 gain in files... turning what used to be >> functionality in /etc/make.conf.local into /etc/make.conf. The intent is >> not to add a third file. If the intent were to add a third configuration >> file then, sure, we could allow all three. But that isn't my intent. > > Ok, well put me on record as wanting three files. While I still have I am not for proliferation of config files. rc.conf and rc.conf.local should have been handled the same way AFAIC. Put me down as wanting two files. An extra file is just more shtuff to keep track of. I too am iffy on /etc/defaults. If the purpose of defaults is to keep "standard" things in isolation then lets do that. Begrudgingly, defaults do clean up /etc a bit. It makes mergemastering easier too. The defaults will be better when they become more complete. >some reservations about the whole /etc/defaults thing, I believe that if >we are going to use it we should use it to full advantage, offering >people more functionality, not less. Unless I am missing something, the The number of files relating to make would still be two. The purpose of each of those files is the same. The new functionality is precisely equal to the previous functionality. Thank You, | http://students.washington.edu/jcwells/ Jason Wells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 9:49: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from supra.rotterdam.luna.net (supra.rotterdam.luna.net [194.151.24.24]) by hub.freebsd.org (Postfix) with ESMTP id 61CC814BD2 for ; Tue, 2 Nov 1999 09:48:51 -0800 (PST) (envelope-from stephanb@luna.nl) Received: (from stephanb@localhost) by supra.rotterdam.luna.net (•8.8.8/tcpwrp+ismx/8.8.8/chk+tcpwrpr) id SAA28025 for current@freebsd.org; Tue, 2 Nov 1999 18:48:49 +0100 (CET) Date: Tue, 2 Nov 1999 18:48:49 +0100 From: Stephan van Beerschoten To: current@freebsd.org Subject: compile error (graphics) Message-ID: <19991102184849.A27936@supra.rotterdam.luna.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Organization: Luna Internet Services http://www.luna.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get this constantly when compiling graphical programs (it seems like constantly though). I got it while copiling xscreensaver from ports: ... cc -Wall -Wstrict-prototypes -Wnested-externs -Wno-format \ -L/usr/X11R6/lib -o xscreensaver xscreensaver.o windows.o \ timers.o subprocs.o xset.o splash.o setuid.o stderr.o prefs.o \ lock.o passwd.o passwd-kerberos.o passwd-pwent.o ../utils/fade.o \ ../utils/overlay.o ../utils/xroger.o ../utils/spline.o \ ../utils/yarandom.o ../utils/resources.o ../utils/usleep.o \ ../utils/visual.o -L/usr/X11R6/lib -lXmu -lXss -lXdpms -lXxf86vm \ -lSM -lICE -lXmu -lXt -lXt -lX11 -lXext -lkrb -ldes -lcrypt /usr/lib/libkrb.so: undefined reference to `init_error_table' /usr/lib/libkrb.so: undefined reference to `initialize_error_table_r' *** Error code 1 I got the same error while trying to compile xlockmore from ports, and I know I've seen this before that one as well, I just can't remember. anyone ? I'm running CVS-updated 4.0-CURRENT as of a few hours ago. -Steve -- Stephan van Beerschoten Email: stephanb@luna.nl Network Engineer Luna Internet Services www.luna.nl PO Box 28013 3003 KA Rotterdam NL PGPKey fingerprint = 45 57 97 61 B2 12 FB 4C 77 8D 35 29 C4 2A 2D 27 "Geekpocalypse '2000 -- The Enemy Is Going To Kick Your Ass" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 9:58: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 1EA9914D46 for ; Tue, 2 Nov 1999 09:57:52 -0800 (PST) (envelope-from patrick@137.org) Received: from friley-162-229.res.iastate.edu (friley-162-229.res.iastate.edu [129.186.162.229]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 6A43C175; Tue, 2 Nov 1999 11:57:47 -0600 (CST) Received: from friley-162-229.res.iastate.edu (friley-162-229.res.iastate.edu [127.0.0.1]) by friley-162-229.res.iastate.edu (Postfix) with ESMTP id A10F75D12; Tue, 2 Nov 1999 11:57:46 -0600 (CST) To: Stephan van Beerschoten Cc: current@freebsd.org Subject: Re: compile error (graphics) In-reply-to: Message from Stephan van Beerschoten of "Tue, 02 Nov 1999 18:48:49 +0100." <19991102184849.A27936@supra.rotterdam.luna.net> Date: Tue, 02 Nov 1999 11:57:46 -0600 From: Patrick Hartling Message-Id: <19991102175746.A10F75D12@friley-162-229.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephan van Beerschoten wrote: } ... } cc -Wall -Wstrict-prototypes -Wnested-externs -Wno-format \ } -L/usr/X11R6/lib -o xscreensaver xscreensaver.o windows.o \ } timers.o subprocs.o xset.o splash.o setuid.o stderr.o prefs.o \ } lock.o passwd.o passwd-kerberos.o passwd-pwent.o ../utils/fade.o \ } ../utils/overlay.o ../utils/xroger.o ../utils/spline.o \ } ../utils/yarandom.o ../utils/resources.o ../utils/usleep.o \ } ../utils/visual.o -L/usr/X11R6/lib -lXmu -lXss -lXdpms -lXxf86vm \ } -lSM -lICE -lXmu -lXt -lXt -lX11 -lXext -lkrb -ldes -lcrypt } /usr/lib/libkrb.so: undefined reference to `init_error_table' } /usr/lib/libkrb.so: undefined reference to `initialize_error_table_r' } *** Error code 1 } } I got the same error while trying to compile xlockmore from ports, } and I know I've seen this before that one as well, I just can't } remember. anyone ? You need to add -lcom_err to your link line. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | Carver Lab - 0095E Black Engineering http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 9:59:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 900A814C4A for ; Tue, 2 Nov 1999 09:59:53 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA00779; Tue, 2 Nov 1999 12:59:25 -0500 (EST) Message-ID: <19991102125925.A28816@netmonger.net> Date: Tue, 2 Nov 1999 12:59:25 -0500 From: Christopher Masto To: "Jason C. Wells" , Doug Barton Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved Mail-Followup-To: "Jason C. Wells" , Doug Barton , Matthew Dillon , freebsd-current@FreeBSD.ORG References: <381F1B08.AF4E0585@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Jason C. Wells on Tue, Nov 02, 1999 at 10:41:19PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 02, 1999 at 10:41:19PM +0000, Jason C. Wells wrote: > Put me down as wanting two files. An extra file is just more shtuff to > keep track of. I too am iffy on /etc/defaults. If the purpose of defaults > is to keep "standard" things in isolation then lets do that. Begrudgingly, > defaults do clean up /etc a bit. It makes mergemastering easier too. The > defaults will be better when they become more complete. The thing about the defaults/foo.conf, foo.conf, foo.conf.local scheme is that you don't _have_ to use foo.conf.local if you don't want to. Some of us have a use for it, such as putting site configuration in foo.conf, and machine configuration in foo.conf.local. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- 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 Nov 2 10: 3:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id E5BF514DB2 for ; Tue, 2 Nov 1999 10:03:23 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA75282; Tue, 2 Nov 1999 13:03:03 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <381F1B08.AF4E0585@gorean.org> References: <199910271928.MAA35915@apollo.backplane.com> <381F1722.3F85DA1@simplenet.com> <199911021703.JAA51793@apollo.backplane.com> <381F1B08.AF4E0585@gorean.org> Date: Tue, 2 Nov 1999 13:04:25 -0500 To: Doug Barton , Matthew Dillon From: Garance A Drosihn Subject: Re: minor heads up - /etc/make.conf{,.local} being moved Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:10 AM -0800 11/2/99, Doug Barton wrote: >Matthew Dillon wrote: > > I think it is necessary to make it exit for now, because what we are > > really doing is a net-0 gain in files... turning what used to be > > functionality in /etc/make.conf.local into /etc/make.conf. The > > intent is not to add a third file. > > Ok, well put me on record as wanting three files. Sounds like it would be fine to have three files, you just shouldn't use /etc/make.conf.local as the name of that third file. Your site's own /etc/make.conf (with "local to your site" changes) could include logic to pick up "machine-specific" settings via some other filename. Maybe /etc/make.conf.hostname, or /etc/hostdefs/make.conf I'm not quite sure what filename is best, I'm just saying that you should be able to get the flexibility you want even though we "choke" on /etc/make.conf.local (just to catch those people who don't realize these first two files have been moved around) --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 10:29: 6 1999 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 9F03914CE8 for ; Tue, 2 Nov 1999 10:28:52 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id NAA21027; Tue, 2 Nov 1999 13:28:40 -0500 (EST) Date: Tue, 2 Nov 1999 13:28:40 -0500 (EST) From: "Matthew N. Dodd" To: Doug Rabson Cc: Mark Hittinger , freebsd-current@FreeBSD.ORG Subject: Re: ep0 3com etherlink III still unhappy 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, 2 Nov 1999, Doug Rabson wrote: > On Mon, 1 Nov 1999, Mark Hittinger wrote: > > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: eeprom failed to come ready. > > ep0: Ethernet address ff:ff:ff:ff:ff:ff > > ep1: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > > ep1: Ethernet address 00:a0:24:a1:9a:1e > > > > The card is actually 0x300, not 0x210. Disabling pnp isn't a work around > > any longer. > > Does ep1 work (i.e. can you send and receive packets on ep1)? If so, > you can probably change your kernel config to have just 'device ep0' > which would allow the card to appear as ep0 again. As per my commit 'heads up' nobody should have anything more or less than 'device ep0' in their config file. I'm assuming he is booting a GENERIC kernel, which I changed to reflect my modifications to if_ep. -- | 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 Tue Nov 2 11:24:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id CF9E715067; Tue, 2 Nov 1999 11:24:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA00870; Tue, 2 Nov 1999 11:15:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911021915.LAA00870@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: John Hay , msmith@freebsd.org, current@freebsd.org Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 08:42:30 PST." <199911021642.IAA51592@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 11:15:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got dragged away yesterday before I could fix this properly; it actually requires a bit more finessing due to the way MFS creates a root-private instance of itself when it nominates itself as root. I don't want to commit a half-baked fix, so I'm going to ask for a little forbearance and fix it properly this evening. > :A GENERIC kernel build breaks here with: > : > :--------- > :sh ../../conf/newvers.sh GENERIC > :cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf vers.c > :linking kernel > :mfs_vfsops.o: In function `mfs_init': > :mfs_vfsops.o(.text+0x63d): undefined reference to `mountrootfsname' > :*** Error code 1 > :1 error > :--------- > : > :Is it just some unfinished commits? > : > :John > :-- > :John Hay -- John.Hay@mikom.csir.co.za > > It looks like a dead global in mfs due to Mike's reorganization of > the rootfs stuff. I'll let Mike do the trivial fix, though, since he > broke it :-). > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 11:33: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles556.castles.com [208.214.165.120]) by hub.freebsd.org (Postfix) with ESMTP id 3E3291523B for ; Tue, 2 Nov 1999 11:32:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA00931 for ; Tue, 2 Nov 1999 11:24:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911021924.LAA00931@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Heads up: GENERIC broken (mfs) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 11:24:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Those of you that have been reading this list will have noticed that I broke MFS_ROOT and thus GENERIC last night. This message is just to let you all know that I know it's broke (now), and that I'll be working on it this evening (PST). Apologies for the breakage in the interim. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 12:32:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt050n71.san.rr.com (dt054n7c.san.rr.com [24.30.152.124]) by hub.freebsd.org (Postfix) with ESMTP id 2D61B15328 for ; Tue, 2 Nov 1999 12:32:41 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gateway.gorean.org (gateway.gorean.org [10.0.0.1]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id MAA02193; Tue, 2 Nov 1999 12:30:44 -0800 (PST) (envelope-from Doug@gorean.org) Date: Tue, 2 Nov 1999 12:30:14 -0800 (PST) From: Doug Barton X-Sender: doug@dt050n71.san.rr.com To: "Jason C. Wells" Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved 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, 2 Nov 1999, Jason C. Wells wrote: > On Tue, 2 Nov 1999, Doug Barton wrote: > > >> I think it is necessary to make it exit for now, because what we are > >> really doing is a net-0 gain in files... turning what used to be > >> functionality in /etc/make.conf.local into /etc/make.conf. The intent is > >> not to add a third file. If the intent were to add a third configuration > >> file then, sure, we could allow all three. But that isn't my intent. > > > > Ok, well put me on record as wanting three files. While I still have > Put me down as wanting two files. An extra file is just more shtuff to > keep track of. I too am iffy on /etc/defaults. If the purpose of defaults > is to keep "standard" things in isolation then lets do that. Begrudgingly, > defaults do clean up /etc a bit. It makes mergemastering easier too. The > defaults will be better when they become more complete. Actually system updates are exactly why I treat the /etc/defaults business with a great deal of mistrust. It hides (or more precisely, it _can_ hide) details of changes and new options from the user. Using mergemaster at least allows you to see more clearly what has been changed, however It still makes me nervous. I'm contemplating some changes that will help correlate differences between /etc/defaults/*.conf and /etc/*.conf[.local], but right now I have no time to hack them out. > >some reservations about the whole /etc/defaults thing, I believe that if > >we are going to use it we should use it to full advantage, offering > >people more functionality, not less. Unless I am missing something, the > > The number of files relating to make would still be two. The purpose of > each of those files is the same. The new functionality is precisely equal > to the previous functionality. Well I don't think that you've made a case yet that the number of files should be zero sum, and as someone pointed out you don't have to use make.conf.local if you don't want or need it. My points are simply that we already have a precedent, the three-tier system for rc.conf has proven to be useful, and if we are going to make a change anyway let's give the user more options, not less. Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 13:38:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BBE7314C35; Tue, 2 Nov 1999 13:38:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA52917; Tue, 2 Nov 1999 13:38:28 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 13:38:28 -0800 (PST) From: Matthew Dillon Message-Id: <199911022138.NAA52917@apollo.backplane.com> To: Mike Smith Cc: John Hay , msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911021915.LAA00870@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : .. Mike Smith writes .. :I got dragged away yesterday before I could fix this properly; it :actually requires a bit more finessing due to the way MFS creates a :root-private instance of itself when it nominates itself as root. I :don't want to commit a half-baked fix, so I'm going to ask for a little :forbearance and fix it properly this evening. If you can actually fix the MFS hacks that have been put in over the years to deal with root fs mounts a lot of people are going to be *very* happy with you! It is certainly worth some temporary breakage. I am not happy at all with the rootfsid hacks I made a few months ago but I didn't have time to do anything about it at the time and I had to get BOOTP working again after someone left it broken for a couple of weeks. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 13:42:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C5208154B1 for ; Tue, 2 Nov 1999 13:42:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA52978; Tue, 2 Nov 1999 13:42:33 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 13:42:33 -0800 (PST) From: Matthew Dillon Message-Id: <199911022142.NAA52978@apollo.backplane.com> To: Garance A Drosihn Cc: Doug Barton , freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved References: <199910271928.MAA35915@apollo.backplane.com> <381F1722.3F85DA1@simplenet.com> <199911021703.JAA51793@apollo.backplane.com> <381F1B08.AF4E0585@gorean.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :At 9:10 AM -0800 11/2/99, Doug Barton wrote: :>Matthew Dillon wrote: :> > I think it is necessary to make it exit for now, because what we are :> > really doing is a net-0 gain in files... turning what used to be :> > functionality in /etc/make.conf.local into /etc/make.conf. The :> > intent is not to add a third file. :> :> Ok, well put me on record as wanting three files. : :Sounds like it would be fine to have three files, you just shouldn't :use /etc/make.conf.local as the name of that third file. Your site's :own /etc/make.conf (with "local to your site" changes) could include :logic to pick up "machine-specific" settings via some other filename. :Maybe /etc/make.conf.hostname, or /etc/hostdefs/make.conf : :I'm not quite sure what filename is best, I'm just saying that you :should be able to get the flexibility you want even though we "choke" :on /etc/make.conf.local (just to catch those people who don't realize :these first two files have been moved around) : :--- :Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Yes, precisely. What I do for site distribution is have a /conf directory hierarchy. The machine autoconfigures itself by any number of means to determine which subdirectory to use and creates a softlink /conf/ME which points to the subdirectory, /conf/. All the major files in /etc then become softlinks to /conf/ME/. For make.conf, a three-file version would have /etc/defaults/make.conf, /etc/make.conf which contains the installation-wide parameters, and it would include /conf/ME/make.conf for the platform-specific parameters. And there you have it... -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 15:15: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 4E7FC15537 for ; Tue, 2 Nov 1999 15:14:58 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.19]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAAB5F for ; Wed, 3 Nov 1999 00:14:40 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA00496 for current@freebsd.org; Wed, 3 Nov 1999 00:13:55 +0100 (CET) (envelope-from asmodai) Date: Wed, 3 Nov 1999 00:13:55 +0100 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: named.conf oddity Message-ID: <19991103001355.A281@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I finally decided to make world this box to a new CURRENT. The old one was a few weeks old. Now the weird thing that struc me was: Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:4: syntax error near '195.121.1.34' Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:7: syntax error near '}' I start named with -b /etc/dns/named.conf And this is my, working for the last half year named.conf: options { directory "/etc/dns"; forwarders { 195.121.1.34; 195.121.1.66; }; }; [ snip of zone files ] And I have no clue where this originates from. Since named after complaining proceeds to start up and work. My configuration worked months before this. The named.conf file at /usr/src/etc/namedb/named.conf looks the same. Anyone with any ideas about this? Thanks, kind regards, -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best There are 3 kinds of lies: lies, damned lies, and statistics. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 17:51:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-15.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.15]) by hub.freebsd.org (Postfix) with ESMTP id 876C2154CB for ; Tue, 2 Nov 1999 17:51:39 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA03527; Wed, 3 Nov 1999 01:51:34 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id RAA00508; Tue, 2 Nov 1999 17:41:24 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911021741.RAA00508@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Mike Bush Cc: freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: SYN Flood/DoS/PPP/ipfw In-Reply-To: Message from Mike Bush of "Fri, 29 Oct 1999 14:16:50 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 17:41:24 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The other day my machine was attacked with, what i believe is, a SYN > flood. tcpdump gave me this output (1.1.1.1 is me and 2.2.2.2 is him) > > 20:57:05.828276 2.2.2.2.4064 > 1.1.1.1.33948: S > 1409055765:14090557 > 65(0) win 32120 (DF) > 20:57:05.836343 2.2.2.2.4065 > 1.1.1.1.14060: S > 1409337177:14093371 > 77(0) win 32120 (DF) > 20:57:05.877668 2.2.2.2.4066 > 1.1.1.1.24418: S > 1402287967:14022879 > 67(0) win 32120 (DF) > 20:57:05.878095 2.2.2.2.4067 > 1.1.1.1.63768: S > 1395991751:13959917 > 51(0) win 32120 (DF) > ... > > Anyways, this attack lasted for about 40 minutes and I had a firewall > ('ipfw show' said the packets were being denied). After about 30 minutes > my system began swapping. I looked around and found ppp (what i used to > connect with via tun0) was now taking up 47MB of RAM and was still > growing. The attack didnt really effect the system load until it started > swapping.. and then it was minimal. > > So my question is.. Is this a problem with my firewall rules or a problem > in ppp? (I run ppp with -alias) I was always under the impression that if > you deny the SYN's where you can (or where they shouldnt be) then they > cant cause a problem. I guess this is wrong. I don't know of any memory leaks in ppp, but that doesn't mean much :-] You could try staging the event again and doing a ppp ``show mem'' to see how much memory ppp things it has..... > My system: > CPU: pII 266 > RAM: 64MB > SWAP: 115MB > OS: FreeBSD-current 4.0 (Oct 20, 1999) > > FreeBSD fan > Mike -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 18: 6:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1]) by hub.freebsd.org (Postfix) with ESMTP id E36BF14D50 for ; Tue, 2 Nov 1999 18:06:52 -0800 (PST) (envelope-from mks@us.networkcs.com) Received: from us.networkcs.com (us.networkcs.com [137.66.11.15]) by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id UAA94300; Tue, 2 Nov 1999 20:06:51 -0600 (CST) (envelope-from mks@us.networkcs.com) Received: (from mks@localhost) by us.networkcs.com (8.9.2/8.8.7) id UAA39981; Tue, 2 Nov 1999 20:06:51 -0600 (CST) From: Mike Spengler Message-Id: <199911030206.UAA39981@us.networkcs.com> Subject: Re: named.conf oddity In-Reply-To: <19991103001355.A281@daemon.ninth-circle.org> from Jeroen Ruigrok/Asmodai at "Nov 3, 99 00:13:55 am" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Tue, 2 Nov 1999 20:06:51 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 Jeroen Ruigrok/Asmodai said: > > Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:4: syntax error > near '195.121.1.34' > Nov 3 00:07:44 daemon named[481]: /etc/dns/named.conf:7: syntax error > near '}' > > I start named with -b /etc/dns/named.conf > > And this is my, working for the last half year named.conf: > > options { > directory "/etc/dns"; > forwarders { > 195.121.1.34; > 195.121.1.66; > }; > }; It seems a recent update to lib/libc/net/inet_addr.c is the culprit here. Any IP address with a component of 34 will fail in inet_aton(). Here's a patch that should fix it up: Index: inet_addr.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet_addr.c,v retrieving revision 1.9 diff -u -r1.9 inet_addr.c --- inet_addr.c 1999/10/31 04:43:55 1.9 +++ inet_addr.c 1999/11/03 02:01:52 @@ -65,6 +65,8 @@ #include #include +#include +#include #include /* @@ -98,7 +100,7 @@ u_long val; char *c; char *endptr; - int base, gotend, n; + int gotend, n; c = (char *)cp; n = 0; @@ -111,8 +113,10 @@ errno = 0; val = strtoul(c, &endptr, 0); - if (val == ERANGE) /* Fail completely if it overflowed. */ + if ((val == ULONG_MAX) && (errno == ERANGE)) { + /* Fail completely if it overflowed. */ return (0); + } /* * If the whole string is invalid, endptr will equal -- Mike Spengler Network Computing Services, Inc. Email: mks@networkcs.com 1200 Washington Ave. So. Phone: +1 612 337 3557 Minneapolis MN 55415 FAX: +1 612 337 3400 (aka Minnesota Supercomputer Center) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 19:46:47 1999 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 C0F2814DA5 for ; Tue, 2 Nov 1999 19:46:41 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p83-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id OAA27023; Wed, 3 Nov 1999 14:51:33 +1100 Date: Wed, 3 Nov 1999 14:46:25 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mike Spengler Cc: Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: named.conf oddity In-Reply-To: <199911030206.UAA39981@us.networkcs.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 > It seems a recent update to lib/libc/net/inet_addr.c is the culprit here. > Any IP address with a component of 34 will fail in inet_aton(). Here's a > patch that should fix it up: > > > Index: inet_addr.c > =================================================================== > RCS file: /home/ncvs/src/lib/libc/net/inet_addr.c,v > retrieving revision 1.9 > diff -u -r1.9 inet_addr.c > --- inet_addr.c 1999/10/31 04:43:55 1.9 > +++ inet_addr.c 1999/11/03 02:01:52 > @@ -65,6 +65,8 @@ > > #include > #include > +#include > +#include > #include > > /* > @@ -98,7 +100,7 @@ > u_long val; > char *c; > char *endptr; > - int base, gotend, n; > + int gotend, n; > > c = (char *)cp; > n = 0; > @@ -111,8 +113,10 @@ > errno = 0; > val = strtoul(c, &endptr, 0); > > - if (val == ERANGE) /* Fail completely if it overflowed. */ > + if ((val == ULONG_MAX) && (errno == ERANGE)) { > + /* Fail completely if it overflowed. */ > return (0); > + } > > /* > * If the whole string is invalid, endptr will equal > The check should be simply `if (errno == ERANGE)'. The (val == ULONG_MAX) check is a harmless bug (harmless because non-overflowing values > 0xffffff, including ULONG_MAX, cause a failure later). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 20:20:31 1999 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 BB35914C39 for ; Tue, 2 Nov 1999 20:20:25 -0800 (PST) (envelope-from imp@harmony.village.org) 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 VAA67989; Tue, 2 Nov 1999 21:20:24 -0700 (MST) (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 VAA17265; Tue, 2 Nov 1999 21:22:50 -0700 (MST) Message-Id: <199911030422.VAA17265@harmony.village.org> To: Jesper Skriver Subject: Re: ep problem with 4.0-19991101-CURRENT snapshot Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 01 Nov 1999 21:04:40 +0100." <19991101210440.A12410@skriver.dk> References: <19991101210440.A12410@skriver.dk> Date: Tue, 02 Nov 1999 21:22:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991101210440.A12410@skriver.dk> Jesper Skriver writes: : sysinstall can assign a ip address via. DHCP, but the machine cannot be : ping'ed from other hosts on the lan, same if I manually configure ep0 : via ifconfig. This sounds like the classic "The right interrupt isn't assigned problem" that I see from time to time. What IRQ did ep0 say it was using? Ditto for pcic0? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 20:51:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 9E2CE154BE; Tue, 2 Nov 1999 20:51:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA02095; Tue, 2 Nov 1999 20:42:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030442.UAA02095@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Mike Smith , John Hay , msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 13:38:28 PST." <199911022138.NAA52917@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 20:42:22 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : .. Mike Smith writes .. > :I got dragged away yesterday before I could fix this properly; it > :actually requires a bit more finessing due to the way MFS creates a > :root-private instance of itself when it nominates itself as root. I > :don't want to commit a half-baked fix, so I'm going to ask for a little > :forbearance and fix it properly this evening. > > If you can actually fix the MFS hacks that have been put in over the > years to deal with root fs mounts a lot of people are going to be > *very* happy with you! It is certainly worth some temporary breakage. The current plan is to have a separate MFS_ROOT conditional sysinit that runs just before the root-mount sysinit. If this one finds an MFS, it'll take over the first spot in the "compatibility" roots list. This isn't quite as nice as I'd have liked, but I can't (yet) write to the kernel environment, so that's about the best I can do. > I am not happy at all with the rootfsid hacks I made a few months ago > but I didn't have time to do anything about it at the time and I had > to get BOOTP working again after someone left it broken for a couple > of weeks. Well, bootp in the kernel has to die too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21: 0:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 98E4A156D2; Tue, 2 Nov 1999 20:59:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA54728; Tue, 2 Nov 1999 20:59:38 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 20:59:38 -0800 (PST) From: Matthew Dillon Message-Id: <199911030459.UAA54728@apollo.backplane.com> To: Mike Smith Cc: John Hay , msmith@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911030442.UAA02095@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I am not happy at all with the rootfsid hacks I made a few months ago :> but I didn't have time to do anything about it at the time and I had :> to get BOOTP working again after someone left it broken for a couple :> of weeks. : :Well, bootp in the kernel has to die too. Huh? And replace it with what? BOOTP is the only way to get an NFS root and swap. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21: 9:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B885A155CD for ; Tue, 2 Nov 1999 21:09:37 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40416>; Wed, 3 Nov 1999 16:04:03 +1100 Content-return: prohibited Date: Wed, 3 Nov 1999 16:09:25 +1100 From: Peter Jeremy Subject: Re: GENERIC build broken In-reply-to: <199911030459.UAA54728@apollo.backplane.com> To: Matthew Dillon Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov3.160403est.40416@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199911030442.UAA02095@dingo.cdrom.com> <199911030459.UAA54728@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-03 15:59:38 +1100, Matthew Dillon wrote: >:Well, bootp in the kernel has to die too. > > Huh? And replace it with what? BOOTP is the only way to get an NFS > root and swap. Sun uses reverse ARP to do this. Reverse ARP _is_ a hack, but it _is_ an alternative to BOOTP. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:16: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 7AFDD14E96 for ; Tue, 2 Nov 1999 21:15:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA02257; Tue, 2 Nov 1999 21:06:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030506.VAA02257@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 20:59:38 PST." <199911030459.UAA54728@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 21:06:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> I am not happy at all with the rootfsid hacks I made a few months ago > :> but I didn't have time to do anything about it at the time and I had > :> to get BOOTP working again after someone left it broken for a couple > :> of weeks. > : > :Well, bootp in the kernel has to die too. > > Huh? And replace it with what? BOOTP is the only way to get an NFS > root and swap. No; that's what the loader is for. The kernel shouldn't be doing any application-level snot like BOOTP at all. The same work was previously done by netboot; putting bootp into the kernel was _always_ the wrong idea. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:23:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id E5FEC1500D for ; Tue, 2 Nov 1999 21:23:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA02306; Tue, 2 Nov 1999 21:15:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030515.VAA02306@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: peter.jeremy@alcatel.com.au Cc: current@FreeBSD.ORG Subject: diskless boot roadmap (was:L Re: GENERIC build broken ) In-reply-to: Your message of "Wed, 03 Nov 1999 16:09:25 +1100." <99Nov3.160403est.40416@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 21:15:03 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 1999-Nov-03 15:59:38 +1100, Matthew Dillon wrote: > >:Well, bootp in the kernel has to die too. > > > > Huh? And replace it with what? BOOTP is the only way to get an NFS > > root and swap. > > Sun uses reverse ARP to do this. Reverse ARP _is_ a hack, but it _is_ > an alternative to BOOTP. RARP would be a really bad move at the moment, since everyone else is using DHCP. For those that are still following, the roadmap looks like this at the moment: - On the PC, we will be following the PXE lead, since that's where the market is going. This basically involves using the PXE firmware which will talk to a PXE server to get the loader. It can also be conned into using normal DHCP. File transfer is either by MTFTP (multicast TFTP) or normal TFTP. The loader will do plain DHCP and use NFS to get the kernel straight out of the prospective root filesystem. Please don't complain about how ugly PXE is. It's the closest thing the PC world has ever seen to a sane network boot architecture. You're welcome to go work on RPL if you want some perspective. 8) - On the Alpha, diskless booting involves BOOTP/TFTP to fetch the loader. The loader will then happily use BOOTP or DHCP again (since SRM is too stupid to tell _us_ what it discovered) and NFS to read the kernel from the root filesystem. As you can see from the above, there's no call for RARP, bootparam, RPL or any other form of mumbo-jumbo. There's also no call for the kernel to do any of this work; the loader will do it all and pass it in to the kernel in a format it can use directly. What is currently missing, you ask? - The loader DHCP code needs to be written. - The kernel needs to improve the way it handles interface configuration information passed to it by the loader. - We need more PXE work done for the i386 loader. Intel are helping here a little, but I could use a couple of extra hands to get this done sooner rather than later. That's about it; we're almost there. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:34:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 52B461504B for ; Tue, 2 Nov 1999 21:34:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA54968; Tue, 2 Nov 1999 21:34:51 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 21:34:51 -0800 (PST) From: Matthew Dillon Message-Id: <199911030534.VAA54968@apollo.backplane.com> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911030442.UAA02095@dingo.cdrom.com> <199911030459.UAA54728@apollo.backplane.com> <99Nov3.160403est.40416@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> Huh? And replace it with what? BOOTP is the only way to get an NFS :> root and swap. : :Sun uses reverse ARP to do this. Reverse ARP _is_ a hack, but it _is_ :an alternative to BOOTP. : :Peter Mmm. Well, I suppose, but it isn't going to be any less complex because rarp does not support all the require features natively. BOOTP is a very simple protocol. You can't get much simpler and the kernel root fs portion of the implementation is going to wind up being the same anyway. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:37:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8ABAC1504B for ; Tue, 2 Nov 1999 21:37:21 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40376>; Wed, 3 Nov 1999 16:31:19 +1100 Content-return: prohibited Date: Wed, 3 Nov 1999 16:36:39 +1100 From: Peter Jeremy Subject: Re: diskless boot roadmap (was:L Re: GENERIC build broken ) In-reply-to: <199911030515.VAA02306@dingo.cdrom.com> To: Mike Smith Cc: current@FreeBSD.ORG Reply-To: peter.jeremy@Alcatel.com.au Message-Id: <99Nov3.163119est.40376@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Nov3.160403est.40416@border.alcanet.com.au> <199911030515.VAA02306@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-03 16:15:03 +1100, Mike Smith wrote: >> On 1999-Nov-03 15:59:38 +1100, Matthew Dillon wrote: >> >:Well, bootp in the kernel has to die too. >> > >> > Huh? And replace it with what? BOOTP is the only way to get an NFS >> > root and swap. >> >> Sun uses reverse ARP to do this. Reverse ARP _is_ a hack, but it _is_ >> an alternative to BOOTP. > >RARP would be a really bad move at the moment, since everyone else is >using DHCP. I'm not suggesting we move to RARP. Matt was stating that BOOTP is the only way. > There's also no call for the kernel >to do any of this work; the loader will do it all and pass it in to the >kernel in a format it can use directly. Sounds excellent. (Not that I'm offering at this point in time). Initialisation code in the permanently resident kernel is basically just wasting physical RAM. The less of it there is, the better. How much of the probe code can we move into userland? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:39:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A5E4F1504B for ; Tue, 2 Nov 1999 21:39:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA55014; Tue, 2 Nov 1999 21:39:47 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 21:39:47 -0800 (PST) From: Matthew Dillon Message-Id: <199911030539.VAA55014@apollo.backplane.com> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911030506.VAA02257@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Huh? And replace it with what? BOOTP is the only way to get an NFS :> root and swap. : :No; that's what the loader is for. The kernel shouldn't be doing any :application-level snot like BOOTP at all. : :The same work was previously done by netboot; putting bootp into the :kernel was _always_ the wrong idea. : :-- :\\ Give a man a fish, and you feed him for a day. \\ Mike Smith Great in theory, but unless someone is actually willing to do the great deal of work required to support this we're stuck with BOOTP in the kernel. Even if you were to do this most of the junk in the kernel to actually do the mounts would have to stick around. Frankly, I don't think it's such a big deal to leave it in the kernel, you wouldn't actually be cleaning much up by moving it out. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:45:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 3DEB81504B for ; Tue, 2 Nov 1999 21:45:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA02461; Tue, 2 Nov 1999 21:35:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030535.VAA02461@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: peter.jeremy@Alcatel.com.au Cc: current@FreeBSD.ORG Subject: probe code (was Re: diskless boot roadmap) In-reply-to: Your message of "Wed, 03 Nov 1999 16:36:39 +1100." <99Nov3.163119est.40376@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 21:35:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Initialisation code in the permanently resident kernel is basically > just wasting physical RAM. The less of it there is, the better. > How much of the probe code can we move into userland? Actually, with PnP architectures becoming the norm, probe code basically goes away, so the whole point is pretty moot. Attach code is somewhat bulkier, but you need to bear in mind that it's needed for devices that arrive after boot time. Attach code is typically far too closely tied to the operational code to separate it at all. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:47:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 9605814E96 for ; Tue, 2 Nov 1999 21:47:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA02485 for ; Tue, 2 Nov 1999 21:38:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030538.VAA02485@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 21:39:47 PST." <199911030539.VAA55014@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 21:38:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> Huh? And replace it with what? BOOTP is the only way to get an NFS > :> root and swap. > : > :No; that's what the loader is for. The kernel shouldn't be doing any > :application-level snot like BOOTP at all. > : > :The same work was previously done by netboot; putting bootp into the > :kernel was _always_ the wrong idea. > > Great in theory, but unless someone is actually willing to do the > great deal of work required to support this we're stuck with BOOTP > in the kernel. Er, hello? It's _already_been_done_, even. See above inre: netboot. > Even if you were to do this most of the junk in the > kernel to actually do the mounts would have to stick around. Frankly, > I don't think it's such a big deal to leave it in the kernel, you > wouldn't actually be cleaning much up by moving it out. It's pointless duplicating it in the kernel when the code that's loaded the kernel has already done it. Nuking it from the kernel has several benefits: - the bootp code in the kernel has rotted, and is quite ugly. - it removes one more confusing option. - it's redundant. The code for performing the actual NFS root mount is tiny compared to the bootp and ifconfig code. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 21:51:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 6F38414C39; Tue, 2 Nov 1999 21:51:08 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (william@pm3b-38.cybcon.com [205.147.75.103]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id VAA03541; Tue, 2 Nov 1999 21:51:05 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 02 Oct 1999 21:49:35 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Subject: Make world error on todays cvsup...... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doing a make world on a DEC Alpha 200 4/233 I get this: The command that produced this was make -DNOGAMES -j 4 world ---------------------------------------------------- cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h /usr/obj/usr/src/tmp/usr/include/cam cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 msdosfs/*.h /usr/obj/usr/src/tmp/usr/include/msdosfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 net/*.h /usr/obj/usr/src/tmp/usr/include/net cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netatalk/*.h /usr/obj/usr/src/tmp/usr/include/netatalk cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netatm/*.h /usr/obj/usr/src/tmp/usr/include/netatm cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netgraph/*.h /usr/obj/usr/src/tmp/usr/include/netgraph cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netinet/*.h /usr/obj/usr/src/tmp/usr/include/netinet cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netipx/*.h /usr/obj/usr/src/tmp/usr/include/netipx cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netkey/*.h /usr/obj/usr/src/tmp/usr/include/netkey cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netncp/*.h /usr/obj/usr/src/tmp/usr/include/netncp cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netns/*.h /usr/obj/usr/src/tmp/usr/include/netns cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 nfs/*.h /usr/obj/usr/src/tmp/usr/include/nfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 nwfs/*.h /usr/obj/usr/src/tmp/usr/include/nwfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 pccard/*.h /usr/obj/usr/src/tmp/usr/include/pccard cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 posix4/*.h /usr/obj/usr/src/tmp/usr/include/posix4 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 sys/*.h /usr/obj/usr/src/tmp/usr/include/sys cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 vm/*.h /usr/obj/usr/src/tmp/usr/include/vm cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 isofs/cd9660/*.h /usr/obj/usr/src/tmp/usr/include/isofs/cd9660 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h /usr/obj/usr/src/tmp/usr/include/ufs/ffs install: ufs/ffs/softdep.h: No such file or directory *** Error code 71 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ----------------------- any ideas.... ---------------------------------- E-Mail: William Woods Date: 02-Oct-99 Time: 21:45:37 FreeBSD 3.3 -Stable ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 22:24:50 1999 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 77E4115088 for ; Tue, 2 Nov 1999 22:24:44 -0800 (PST) (envelope-from jdp@polstra.com) 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 WAA00106; Tue, 2 Nov 1999 22:24:43 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA47615; Tue, 2 Nov 1999 22:24:42 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 2 Nov 1999 22:24:42 -0800 (PST) Message-Id: <199911030624.WAA47615@vashon.polstra.com> To: wwoods@cybcon.com Subject: Re: Make world error on todays cvsup...... In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , William Woods wrote: > Doing a make world on a DEC Alpha 200 4/233 I get this: ... > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h > /usr/obj/usr/src/tmp/usr/include/ufs/ffs > install: ufs/ffs/softdep.h: No such file or directory > *** Error code 71 ... > any ideas.... Yep. Read /usr/src/sys/ufs/ffs/README.softupdates, and do what it says. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 22:34:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 84D2914FCD for ; Tue, 2 Nov 1999 22:34:21 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (william@pm3b-38.cybcon.com [205.147.75.103]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id WAA06843; Tue, 2 Nov 1999 22:34:17 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911030624.WAA47615@vashon.polstra.com> Date: Sat, 02 Oct 1999 22:32:48 -0700 (PDT) Reply-To: wwoods@cybcon.com From: William Woods To: John Polstra Subject: Re: Make world error on todays cvsup...... Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you... On 03-Nov-99 John Polstra wrote: > In article , > William Woods wrote: >> Doing a make world on a DEC Alpha 200 4/233 I get this: > ... >> cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h >> /usr/obj/usr/src/tmp/usr/include/ufs/ffs >> install: ufs/ffs/softdep.h: No such file or directory >> *** Error code 71 > ... >> any ideas.... > > Yep. Read /usr/src/sys/ufs/ffs/README.softupdates, and do what it > says. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron ---------------------------------- E-Mail: William Woods Date: 02-Oct-99 Time: 22:28:41 FreeBSD 3.3 -Stable ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 23: 3:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2A01614DA5 for ; Tue, 2 Nov 1999 23:03:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA55313; Tue, 2 Nov 1999 23:03:07 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 23:03:07 -0800 (PST) From: Matthew Dillon Message-Id: <199911030703.XAA55313@apollo.backplane.com> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911030538.VAA02485@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> great deal of work required to support this we're stuck with BOOTP :> in the kernel. : :Er, hello? It's _already_been_done_, even. See above inre: netboot. Good god, you are talking about netboot? Hello? Mike, I get the feeling that you've never actually tried to use netboot. You seem to believe that it is direct replacement for BOOTP. It isn't even close. netboot only works with a very small number of ethernet cards while the BOOTP code in the kernel works with *all* ethernet cards that the kernel supports. netboot doesn't work with a single one of my machines. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 23:23:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 7590114FCD for ; Tue, 2 Nov 1999 23:23:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA03030; Tue, 2 Nov 1999 23:14:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030714.XAA03030@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 23:03:07 PST." <199911030703.XAA55313@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 23:14:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> great deal of work required to support this we're stuck with BOOTP > :> in the kernel. > : > :Er, hello? It's _already_been_done_, even. See above inre: netboot. > > Good god, you are talking about netboot? Hello? Mike, I get the feeling > that you've never actually tried to use netboot. You "get" wrong. You could probably actually search the archives for much of what I've said about diskless booting over the last four or so years and get a reasonable picture of what I know, or just accept that fact that I'm acutely aware of the possibilities and limitations that currently exist. I'd like to suggest you use etherboot in the interim, but it doesn't fill in the nfs_diskless structure, which is somewhat of a pity since that's all that's needed. You could probably fix this in about ten minutes if you want a functional solution, and it probably supports most if not all of the cards you currently have. > You seem to believe > that it is direct replacement for BOOTP. It isn't even close. That's neither what I said, nor what I believe. I merely pointed out that netboot has already done the "great deal of work" that you're agonising about. You'll note that the loader also already contains this "great deal of work", since it seems to netboot Alphas just fine. If you care to read what I've actually written, you'll note that I am advocating the death of BOOTP once it's replaced by something that works better. You might want to consider turning down the gain on your Panic-o-tronic implant on this one. > netboot > only works with a very small number of ethernet cards while the BOOTP > code in the kernel works with *all* ethernet cards that the kernel > supports. The BOOTP code in the kernel is singularly useless if you can't get the kernel onto the machine in the first place. Until I see clear air under your feet via judicious use of your own bootstraps, I'll persist in making diskless booting work properly. Should you care to be part of the solution rather than part of the problem, I'd appreciate it if you could pick up a couple of network cards that boast PXE 2.0 compliant boot ROMs. I still hold out hope of having something minimally functional before Comdex, although the first step will probably still require BOOTP in the kernel. It was quite unnecessary and inappropriate to get so frazzled about this in public Matt. I'm not a moron, and labelling me such isn't really terribly productive. You could have made the points you tried to above without anywhere near as much angst, and I could have addressed them far more palatably as well. As a general rule, it's useful to assume that the person you're talking to is not a complete idiot. If it looks like they're behaving that way, you might want to double-check your assumptions before going off. It's a little more overhead, but it can save on the repercussions later. Regards, -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 23:24:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id DF738154F7 for ; Tue, 2 Nov 1999 23:24:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA03050; Tue, 2 Nov 1999 23:16:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030716.XAA03050@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 23:03:07 PST." <199911030703.XAA55313@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 23:16:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've settled Matt's qualms in private, since this was getting a little off track. Needless to say I'm quite on top of the current set of issues, and Matt's just a bit confused about what I'm trying to say. > :> great deal of work required to support this we're stuck with BOOTP > :> in the kernel. > : > :Er, hello? It's _already_been_done_, even. See above inre: netboot. > > Good god, you are talking about netboot? Hello? Mike, I get the feeling > that you've never actually tried to use netboot. You seem to believe > that it is direct replacement for BOOTP. It isn't even close. netboot > only works with a very small number of ethernet cards while the BOOTP > code in the kernel works with *all* ethernet cards that the kernel > supports. > > netboot doesn't work with a single one of my machines. > > -Matt > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 2 23:53:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6BF9F14D15 for ; Tue, 2 Nov 1999 23:53:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA55780; Tue, 2 Nov 1999 23:53:38 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 23:53:38 -0800 (PST) From: Matthew Dillon Message-Id: <199911030753.XAA55780@apollo.backplane.com> To: Mike Smith Cc: current@freebsd.org Subject: Re: GENERIC build broken References: <199911030721.XAA03097@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think there is only one thing that will ever allow us to remove the BOOTP code from the kernel, and that is if a time comes when the BIOSes for all standard off-the-shelf motherboards all have the ability to set a boot-from-network option. When/if that ever occurs, then we will be able to remove the code. I can tell you from experience that relying on standards without direct bios support across the board, or relying and ad-hoc programs like netboot, simply will not stand the test of time. What may appear to work fine now for X number of PC motherboards/ethercard brands will only work for X/2 number of PC motherboards/ethercards two years from now. Only something integrated into the kernel or something that uses the kernel's driver source directly can stand the test of time prior to ubiquitous BIOS integration. It is a sad but true fact. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 0: 6:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 19BA615086 for ; Wed, 3 Nov 1999 00:06:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA03299; Tue, 2 Nov 1999 23:58:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030758.XAA03299@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@freebsd.org Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 23:53:38 PST." <199911030753.XAA55780@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 23:58:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think there is only one thing that will ever allow us to remove > the BOOTP code from the kernel, and that is if a time comes when > the BIOSes for all standard off-the-shelf motherboards all have > the ability to set a boot-from-network option. When/if that ever > occurs, then we will be able to remove the code. Please take a few minutes to go to developer.intel.com and read about PXE. Note that it's card-centric, not board-centric, so it doesn't require any buy-in from motherboard vendors. Also, because it's software only, there are already third-party vendors with software for most cards on the market. The last time I looked, InCom had support for well over 100 different network cards. With the general adoption of PXE in the WfM context for diskless WinTel installs, you can be certain that any network adapter with a bootrom socket is going to have PXE-compliant support available. If you want to participate in this dicussion much futher without dragging us off on these irrelevant tangents, it's quite important that you catch up on your reading. If you've been and looked at PXE more than a few months ago, go back again as they've massively updated the spec for PXE 2.0. Note that PXE 2.0, and UNDI in particular, go so far as to make it quite feasible to write a generic kernel driver that will talk to any PCI or PnP network adapter with a PXE-compliant bootrom. Not that I'm advocating this, you should understand. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 0:11:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id A2C5615003 for ; Wed, 3 Nov 1999 00:11:14 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.2/8.9.2) id JAA33688; Wed, 3 Nov 1999 09:09:21 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911030809.JAA33688@info.iet.unipi.it> Subject: Re: GENERIC build broken In-Reply-To: <199911030538.VAA02485@dingo.cdrom.com> from Mike Smith at "Nov 2, 1999 9:38:54 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 3 Nov 1999 09:09:21 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Sorry for jumping into the thread but note that netboot is not functional with ELF kernels, and in any case it basically only supports one card type. Now you tell me that etherboot is so much better than netboot, but it still only supports a few cards and some of them do not even work for all models (e.g. "de" is notoriously broken). Here we have a few labs running FreeBSD diskless, and kernel bootp support is the only thing that lets us do the job without messing up too much with configurations. We boot kernels from a small fbsd partition (which isn't that bad after all, because in the end you need some place to stick netboot/etherboot onto, and this reduces a lot of traffic/server load when in the morning or at the beginning of a class everybody reboots at the same time), and then do the bootp config, nfs-mount root etc. The alternative would be, i believe, to have a small fs image that the boot loader brings up, containing whatever (DHCP client etc.) is needed to do an ifconfig, set an address and a route, and then proceed. Of course it can be done but this requires a bit of annoying tricks to replace /etc/rc at some point (which is the same trick picobsd does, and is a big source of confusion). cheers luigi > > :application-level snot like BOOTP at all. > > : > > :The same work was previously done by netboot; putting bootp into the > > :kernel was _always_ the wrong idea. ... > Er, hello? It's _already_been_done_, even. See above inre: netboot. ... > It's pointless duplicating it in the kernel when the code that's loaded > the kernel has already done it. Nuking it from the kernel has several > benefits: > > - the bootp code in the kernel has rotted, and is quite ugly. > - it removes one more confusing option. > - it's redundant. > The code for performing the actual NFS root mount is tiny compared to > the bootp and ifconfig code. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 2:16:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 0D18514F51; Wed, 3 Nov 1999 02:16:23 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA41423; Wed, 3 Nov 1999 10:14:54 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 3 Nov 1999 10:14:54 +0000 (GMT) From: Doug Rabson To: William Woods Cc: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: Make world error on todays cvsup...... 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, 2 Oct 1999, William Woods wrote: > Doing a make world on a DEC Alpha 200 4/233 I get this: > > The command that produced this was make -DNOGAMES -j 4 world > > /usr/obj/usr/src/tmp/usr/include/ufs/ffs > install: ufs/ffs/softdep.h: No such file or directory It looks like you have a broken symlink. The source for softupdates moved from src/contrib/sys/softupdates to src/sys/contrib/softupdates. You need to re-make the symlinks from src/sys/ufs/ffs. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 3:10:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 0B1C014CAB; Wed, 3 Nov 1999 03:10:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id DAA04459; Wed, 3 Nov 1999 03:00:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911031100.DAA04459@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: current@FreeBSD.org Subject: Re: cvs commit: src/sys/kern vfs_conf.c src/sys/ufs/mfs mfs_vfsops.c In-reply-to: Your message of "Wed, 03 Nov 1999 03:02:49 PST." <199911031102.DAA75099@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Nov 1999 03:00:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This should fix GENERIC and thus also the release builds. Sorry about the delay in getting this part committed. > msmith 1999/11/03 03:02:49 PST > > Modified files: > sys/kern vfs_conf.c > sys/ufs/mfs mfs_vfsops.c > Log: > Make MFS work with the new root filesystem search process. > > In order to achieve this, root filesystem mount is moved from > SI_ORDER_FIRST to SI_ORDER_SECOND in the SI_SUB_MOUNT_ROOT sysinit > group. Now, modules which wish to usurp the default root mount > can use SI_ORDER_FIRST. > > A compiled-in or preloaded MFS filesystem will become the root > filesystem unless the vfs.root.mountfrom environment variable refers > to a valid bootable device. This will normally only be the case when > the kernel and MFS image have been loaded from a disk which has a > valid /etc/fstab file. In this case, the variable should be manually > overridden in the loader, or the kernel booted with -a. In either > case "mfs:" should be supplied as the new value. > > Also fix a typo in one DFLTROOT case that would not have compiled. > > Revision Changes Path > 1.35 +11 -9 src/sys/kern/vfs_conf.c > 1.78 +31 -15 src/sys/ufs/mfs/mfs_vfsops.c > > > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 4:28:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.mtci.ne.jp (smtp.mtci.ne.jp [210.231.230.8]) by hub.freebsd.org (Postfix) with ESMTP id 2802414E96 for ; Wed, 3 Nov 1999 04:28:06 -0800 (PST) (envelope-from ks_org@aax.mtci.ne.jp) Received: from smtp.mtci.ne.jp (ppp83-Kisaradu1.mtci.ne.jp [210.172.11.93]) by smtp.mtci.ne.jp (8.8.8/3.6W) with SMTP id VAA08251 for ; Wed, 3 Nov 1999 21:26:18 +0900 Date: Wed, 3 Nov 1999 21:26:18 +0900 Message-Id: <199911031226.VAA08251@smtp.mtci.ne.jp> From: =?iso-2022-jp?B?S2F6dW1pIFNhc2FraQ==?= To: =?iso-2022-jp?B?ZnJlZWJzZC1jdXJyZW50QGZyZWVic2Qub3Jn?= Subject: =?iso-2022-jp?B?GyRCJTslaSU3ITwlcz5lTiYlLSVjJXMlWiE8JXMbKEI=?= Mime-Version: 1.0 Content-Type: text/plain; charset= "ISO-2022-JP" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B!y!y!y(B $B%;%i%7!<%s>eN&%-%c%s%Z!<%s(B $B!y!y!y(B '99$BG/EYA4JF(BNo.1$B%;!<%k%9$r>e$2$F$$$k9q:]FC5v%5%W%j%a%s%H!"(B $B%;%i%7!<%s(B[CELLASENE]$B$,$$$h$$$h:#7nF|K\$K>eN&$7$^$9!#(B $B%;%i%7!<%s$Oc32$r5/$3$7$F$$$k$?$a!"(B $B0lEYH/@8$9$k$HHnBg2=$9$k$3$H$O$"$C$F$b!"(B $B%@%$%(%C%H$d1?F0$r9T$C$F$b!"$J$+$J$+Mn$H$;$J$$$N$,8=o$KMn$H$7$K$/$$;iKC$N$?$a!"BN=E$dBN7A$K4X$o$i$:!"(B $BLs(B90$B!s$N=w@-$,%;%k%i%$%H$K$D$$$FG:$s$G$$$k$HJs9p$5$l$F$$$^$9!#(B $B%@%$%(%C%H$NI,MW$J$5$=$&$J!"$d$;$F$$$k=w@-$,%@%$%(%C%H$r9T$&$N$O!"(B $B$3$N%;%k%i%$%H$rMn$H$7$?$$$H$$$&5$;}$A$KB>$J$j$^$;$s!#(B $B%;%i%7!<%s$O!"$3$N%;%k%i%$%H$r=|5n$9$k$?$a$K%$%?%j%"$G3+H/$5$l!"(B $BNW>28&5f$N7k2L!"%;%k%i%$%H=|5n8z2L$,3N$+$a$i$l$?@$3&M#0l$N@=IJ$G$9!#(B $B@$3&Cf$N=w@-$K@d;?$5$l$F$*$j!"A4@$3&$G:#G/(B650$BK|%;%C%H$,HNGd$5$l!"(B $B%*!<%9%H%i%j%"$G$O(B60$BK|%;%C%H$N8BDjHNGd$@$C$?$3$H$b$"$j!"(B $BGc@j$a$K$h$kK=F0$,KVH/$7$?$&$($K!"(B $B:G8e$N(B1$B%;%C%H$K$O(B12,000US$B%I%k(B($BLs(B130$BK|1_(B)$B$N%W%l%_%"$,$D$$$?(B $B%(%T%=!<%I$bJs9p$5$l$F$$$^$9!#(B $B$*6b$N$+$+$kH~MF@07A$d%(%9%F$K$+$h$&$3$H$J$/!"(B $B$o$:$+(B8$B=54V$G%R%C%W%i%$%s!$%l%C%0%i%$%s$r$-$l$$$K@0$($k(B $B:#@$3&Cf$G:G$bCmL\$5$l$F$$$k%5%W%j%a%s%H!H%;%i%7!<%s!I$K$D$$$F(B $B!&99$K>\$7$$@bL@$r$44uK>$NJ}(B $B!&@=IJ9XF~4uK>$NJ}(B $B$O2<5-(BURL$B$K@=IJ35MW!$NW>28&5f7k2L!$%*!<%@!<%U%)!<%`(B $BEy$,7G:\$5$l$F$$$^$9$N$G@'Hs$4Mw2<$5$$!#(B $B%;%i%7!<%s>\:Y>pJs(BURL http://www.dab.hi-ho.ne.jp/bios_life/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 4:59:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 4CF4B14F62 for ; Wed, 3 Nov 1999 04:59:18 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id SAA02128; Wed, 3 Nov 1999 18:58:00 +0600 (NOVT) (envelope-from nnd) Date: Wed, 3 Nov 1999 18:58:00 +0600 (NOVT) Message-Id: <199911031258.SAA02128@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: freebsd-current@freebsd.org Subject: CTM-deltas generation sptopped ? User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are no new CTM-deltas on 'ctm.freebsd.org' at least 22 hours. Is this known problem ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 9:50: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F1C43157E2 for ; Wed, 3 Nov 1999 09:49:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA59950; Wed, 3 Nov 1999 09:49:32 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Nov 1999 09:49:32 -0800 (PST) From: Matthew Dillon Message-Id: <199911031749.JAA59950@apollo.backplane.com> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911030758.XAA03299@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> I think there is only one thing that will ever allow us to remove :> the BOOTP code from the kernel, and that is if a time comes when :> the BIOSes for all standard off-the-shelf motherboards all have :> the ability to set a boot-from-network option. When/if that ever :> occurs, then we will be able to remove the code. : :Please take a few minutes to go to developer.intel.com and read about :PXE. Note that it's card-centric, not board-centric, so it doesn't :require any buy-in from motherboard vendors. Also, because it's :software only, there are already third-party vendors with software for :most cards on the market. Mike, you aren't listening to what I am saying. Go back to my last email and read it again carefully. All the standards in the world for network card operation won't help you until the BIOS actually tries to use them directly. PXE sounds cool, but coolness doesn't count unless all the motherboard manufacturers start using it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10: 9:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 6D01514C84 for ; Wed, 3 Nov 1999 10:09:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA06333; Wed, 3 Nov 1999 10:00:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911031800.KAA06333@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Wed, 03 Nov 1999 09:49:32 PST." <199911031749.JAA59950@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Nov 1999 10:00:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> I think there is only one thing that will ever allow us to remove > :> the BOOTP code from the kernel, and that is if a time comes when > :> the BIOSes for all standard off-the-shelf motherboards all have > :> the ability to set a boot-from-network option. When/if that ever > :> occurs, then we will be able to remove the code. > : > :Please take a few minutes to go to developer.intel.com and read about > :PXE. Note that it's card-centric, not board-centric, so it doesn't > :require any buy-in from motherboard vendors. Also, because it's > :software only, there are already third-party vendors with software for > :most cards on the market. > > Mike, you aren't listening to what I am saying. Go back to my last > email and read it again carefully. All the standards in the world > for network card operation won't help you until the BIOS actually > tries to use them directly. PXE sounds cool, but coolness doesn't > count unless all the motherboard manufacturers start using it. I'm offended, and a little amused. You say "you aren't listening to what I'm saying", yet you have quoted a paragraph in which I say "... it doesn't require any buy-in from motherboard vendors." Are you calling me a liar, or stupid, or are you not reading what I'm saying? Clarification here would help me to decide how to treat your further responses on this topic. Note that in either case, you're wrong. PXE doesn't require any action on the part of motherboard manufacturers at all. You're welcome, should you care to take my earlier device, to add some brief study of the int 19 boot vector chain and the PnP device option ROM interface to your reading list. I note that you haven't even looked at PXE yet. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:21:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id BFE5B14DD0 for ; Wed, 3 Nov 1999 10:21:16 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA32067; Wed, 3 Nov 1999 19:17:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Wed, 03 Nov 1999 09:49:32 PST." <199911031749.JAA59950@apollo.backplane.com> Date: Wed, 03 Nov 1999 19:17:39 +0100 Message-ID: <32065.941653059@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911031749.JAA59950@apollo.backplane.com>, Matthew Dillon writes: > >: >:> I think there is only one thing that will ever allow us to remove >:> the BOOTP code from the kernel, and that is if a time comes when >:> the BIOSes for all standard off-the-shelf motherboards all have >:> the ability to set a boot-from-network option. When/if that ever >:> occurs, then we will be able to remove the code. >: >:Please take a few minutes to go to developer.intel.com and read about >:PXE. Note that it's card-centric, not board-centric, so it doesn't >:require any buy-in from motherboard vendors. Also, because it's >:software only, there are already third-party vendors with software for >:most cards on the market. > > Mike, you aren't listening to what I am saying. Go back to my last > email and read it again carefully. All the standards in the world > for network card operation won't help you until the BIOS actually > tries to use them directly. PXE sounds cool, but coolness doesn't > count unless all the motherboard manufacturers start using it. Matt, Please try to do as Mike says, it would save a lot of time and windmills if you would check the facts rather than keep arguing your unfounded dogma. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:24:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8066C150F0 for ; Wed, 3 Nov 1999 10:24:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA60287; Wed, 3 Nov 1999 10:24:43 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Nov 1999 10:24:43 -0800 (PST) From: Matthew Dillon Message-Id: <199911031824.KAA60287@apollo.backplane.com> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911031800.KAA06333@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm offended, and a little amused. You say "you aren't listening to :what I'm saying", yet you have quoted a paragraph in which I say :"... it doesn't require any buy-in from motherboard vendors." : :Are you calling me a liar, or stupid, or are you not reading what I'm No, I'm just giving you the reality. Until I can buy *generic* motherboards and/or ethernet cards that actually netboot, what standards a few of them might use is moot. It would be phenominally stupid for me to restrict my purchases to just those cards and/or motherboards (since I tend to get MB's with built-in ethernets these days) which are capable of netbooting, because I would wind up paying a significant premium for the privilage. The issue of the BIOS support is the same issue that you have with floppy / HD / CDRom boot ordering. The BIOS needs to be aware of the bootability of the network device in order for one to be able to control the boot ordering. Just having a network adapter capable of netbooting, or even a network adapter flash configuration that allows you to turn it on and off, is not quite sufficient. Think of CDRom booting. When just a few bios's were able to boot from CDRom, nobody could depend on it and very few people were shipping bootable cdroms. But once pretty much all the motherboards started to be able to boot from an IDE CDRom, the issue went away and now everyone I know boots their Linux, FreeBSD, etc... OS distributions from CDRom and don't even bother with boot floppies any more. CDRom booting also didn't eally come into its own until the boot ordering could be controlled by the BIOSes. Early BIOSes had only limited options for CDRom boot ordering vs floppy, SCSI, and IDE drives, and that created problems. We have exactly the same issues with netbooting that we had with CDRom booting. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:26:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 71C6114E7E for ; Wed, 3 Nov 1999 10:26:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA60300; Wed, 3 Nov 1999 10:25:38 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Nov 1999 10:25:38 -0800 (PST) From: Matthew Dillon Message-Id: <199911031825.KAA60300@apollo.backplane.com> To: Poul-Henning Kamp Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <32065.941653059@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> tries to use them directly. PXE sounds cool, but coolness doesn't :> count unless all the motherboard manufacturers start using it. : :Matt, : :Please try to do as Mike says, it would save a lot of time and windmills :if you would check the facts rather than keep arguing your unfounded :dogma. : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." Go fly a kite, Poul. I'm not interesting in listening to your spouting off any more. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:35:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 0B61114D15 for ; Wed, 3 Nov 1999 10:35:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA06471; Wed, 3 Nov 1999 10:26:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911031826.KAA06471@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Wed, 03 Nov 1999 10:24:43 PST." <199911031824.KAA60287@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Nov 1999 10:26:38 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :I'm offended, and a little amused. You say "you aren't listening to > :what I'm saying", yet you have quoted a paragraph in which I say > :"... it doesn't require any buy-in from motherboard vendors." > : > :Are you calling me a liar, or stupid, or are you not reading what I'm > > No, I'm just giving you the reality. Until I can buy *generic* > motherboards and/or ethernet cards that actually netboot, what > standards a few of them might use is moot. You can. Go do it. Guess what I'm working on PXE with? Yes, if you make a bad buying choice on the network card, you're going to spend a few dollars on a bootprom. *shrug* Welcome to "bootable" vs. "non-bootable" network cards. > We have exactly the same issues with netbooting that we had with CDRom > booting. Actually, what we have is the same set of issues that we've had with booting from cards with their own firmware since about 1986. (Possibly earlier; that's just when I first got involved with it.) By your logic, until motherboards have options for controlling the boot order of eg. plug-in SCSI adapters there is no point in you buying plug-in SCSI adapters. So what have you been using for the last thirteen years? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:41: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 259AD14A2D for ; Wed, 3 Nov 1999 10:40:56 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA32209; Wed, 3 Nov 1999 19:38:20 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Wed, 03 Nov 1999 10:24:43 PST." <199911031824.KAA60287@apollo.backplane.com> Date: Wed, 03 Nov 1999 19:38:19 +0100 Message-ID: <32207.941654299@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911031824.KAA60287@apollo.backplane.com>, Matthew Dillon writes: >:I'm offended, and a little amused. You say "you aren't listening to >:what I'm saying", yet you have quoted a paragraph in which I say >:"... it doesn't require any buy-in from motherboard vendors." >: >:Are you calling me a liar, or stupid, or are you not reading what I'm > > No, I'm just giving you the reality. Until I can buy *generic* > motherboards and/or ethernet cards that actually netboot, what > standards a few of them might use is moot. I think most if not all the ethernet cards I or my customers have bought over the last year have sported mighty fine netboot capabilities. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:44:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 487A514A2D for ; Wed, 3 Nov 1999 10:44:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA60534; Wed, 3 Nov 1999 10:43:43 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Nov 1999 10:43:43 -0800 (PST) From: Matthew Dillon Message-Id: <199911031843.KAA60534@apollo.backplane.com> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911031826.KAA06471@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> No, I'm just giving you the reality. Until I can buy *generic* :> motherboards and/or ethernet cards that actually netboot, what :> standards a few of them might use is moot. : :You can. Go do it. Guess what I'm working on PXE with? Yes, if you :make a bad buying choice on the network card, you're going to spend a :few dollars on a bootprom. *shrug* Welcome to "bootable" vs. :"non-bootable" network cards. You've just made my point. PXE sounds wonderful, but it isn't going to be generic until you don't have to think about it. Networking technology changes fairly quickly. Requiring specialized hardware may accomplish your short-term goals, but it also locks you into a technology which may or may not be able to keep up with the times. Many seemingly great technologies have gone by the wayside precisely because of this problem. Some are on the brink -- LS120 floppies, for example, almost went extinct because of a lack of generic compatibility. They still might. I think network booting in a generic environment will happen, but it isn't here yet. :> We have exactly the same issues with netbooting that we had with CDRom :> booting. : :Actually, what we have is the same set of issues that we've had with :booting from cards with their own firmware since about 1986. (Possibly :earlier; that's just when I first got involved with it.) : :By your logic, until motherboards have options for controlling the boot :order of eg. plug-in SCSI adapters there is no point in you buying :plug-in SCSI adapters. So what have you been using for the last :thirteen years? Complete nonsense. Even with SCSI drives you could still control the boot ordering between the floppy, CDRom, and generic 'hard drive' (being whatever was installed as C:). People who run SCSI drives tend not to run IDE drives so the IDE<->SCSI ordering isn't an issue. Network booting is much closer to the CDRom-booting problem then it is to SCSI booting, which is why I used CDRom-booting as an example. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:45:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 1894014F04 for ; Wed, 3 Nov 1999 10:45:41 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id LAA14183; Wed, 3 Nov 1999 11:44:55 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA09963; Wed, 3 Nov 1999 11:44:54 -0700 Date: Wed, 3 Nov 1999 11:44:54 -0700 Message-Id: <199911031844.LAA09963@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Matthew Dillon , Mike Smith , current@FreeBSD.ORG Subject: Re: GENERIC build broken In-Reply-To: <32207.941654299@critter.freebsd.dk> References: <199911031824.KAA60287@apollo.backplane.com> <32207.941654299@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think most if not all the ethernet cards I or my customers > have bought over the last year have sported mighty fine netboot > capabilities. FWIW, few of the cards I've bought over the years sport netboot. And, netboot is an impossibility in 'embedded' systems that use things like PCMCIA/CARDBUS, which are becoming common-place for embedded routers and such. Netboot (IMO) is an unacceptable solution to many folks. It seems that 'progress' in this case means removing alot of existing functionality that is used by a number of folks. (CDROM root, BOOTP, etc...) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:56:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5785414CE0 for ; Wed, 3 Nov 1999 10:56:35 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA60751; Wed, 3 Nov 1999 10:56:29 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Nov 1999 10:56:29 -0800 (PST) From: Matthew Dillon Message-Id: <199911031856.KAA60751@apollo.backplane.com> To: Nate Williams Cc: Poul-Henning Kamp , Mike Smith , current@FreeBSD.ORG Subject: Re: GENERIC build broken References: <199911031824.KAA60287@apollo.backplane.com> <32207.941654299@critter.freebsd.dk> <199911031844.LAA09963@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I think most if not all the ethernet cards I or my customers :> have bought over the last year have sported mighty fine netboot :> capabilities. : :FWIW, few of the cards I've bought over the years sport netboot. And, :netboot is an impossibility in 'embedded' systems that use things like :PCMCIA/CARDBUS, which are becoming common-place for embedded routers and :such. : :Netboot (IMO) is an unacceptable solution to many folks. It seems that :'progress' in this case means removing alot of existing functionality :that is used by a number of folks. : :(CDROM root, BOOTP, etc...) : :Nate The day that any of us can walk into a well-stocked CompUSA store and see more then 70% of the network card brands sport a netboot capability out of the box is the day that we can start to think about doing without the kernel BOOTP code. That day may not come for a few years. It certainly isn't here now. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 10:57:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 70598154AE for ; Wed, 3 Nov 1999 10:57:19 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA32338 for ; Wed, 3 Nov 1999 19:57:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: YAJKHT (Yet a Junior kernel hacker task) In-reply-to: Your message of "Wed, 03 Nov 1999 09:54:27 PST." <199911031754.JAA67357@freefall.freebsd.org> Date: Wed, 03 Nov 1999 19:57:03 +0100 Message-ID: <32336.941655423@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that we have grudingly accepted the existence of the ctype macros (isdigit(3) and friends) along with strto{u}[ql](3) into the kernel, there are a considerable number of places where they could be used to make code more readable. Needless to say you need to *test* your patches before you send them to us with send-pr. About the only place which is sacred is the gdb-stubs, please be aware that particular isolation requirements apply to that code which make it un-smart to rely on library functions. (that is why the gdb-stubs even come with their own strlen(3) & strcat(3) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 11: 7: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 62C5B14CE0 for ; Wed, 3 Nov 1999 11:06:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA06668; Wed, 3 Nov 1999 10:57:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911031857.KAA06668@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: current@FreeBSD.ORG Subject: Re: GENERIC build broken In-reply-to: Your message of "Wed, 03 Nov 1999 11:44:54 MST." <199911031844.LAA09963@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Nov 1999 10:57:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think most if not all the ethernet cards I or my customers > > have bought over the last year have sported mighty fine netboot > > capabilities. > > FWIW, few of the cards I've bought over the years sport netboot. And, > netboot is an impossibility in 'embedded' systems that use things like > PCMCIA/CARDBUS, which are becoming common-place for embedded routers and > such. Argh! More FUD! Network booting is not an impossibility in an embedded product using PCCARD or CARDBUS. > Netboot (IMO) is an unacceptable solution to many folks. It seems that > 'progress' in this case means removing alot of existing functionality > that is used by a number of folks. > > (CDROM root, BOOTP, etc...) More FUD! CDROM root devices still work fine. The automated search stuff was broken, and it's gone because it was in the way. There will be a new automated search process that will work properly. BOOTP in the kernel will go _when_there_is_an_acceptable_alternative_. Yes, progress means losing the crap. How much more like a shark would you look like if you didn't lose your baby teeth? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 11:18: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 7281A14CE0 for ; Wed, 3 Nov 1999 11:17:46 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id MAA14558; Wed, 3 Nov 1999 12:17:44 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA10150; Wed, 3 Nov 1999 12:17:43 -0700 Date: Wed, 3 Nov 1999 12:17:43 -0700 Message-Id: <199911031917.MAA10150@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Subject: Re: GENERIC build broken In-Reply-To: <199911031857.KAA06668@dingo.cdrom.com> References: <199911031844.LAA09963@mt.sri.com> <199911031857.KAA06668@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think most if not all the ethernet cards I or my customers > > > have bought over the last year have sported mighty fine netboot > > > capabilities. > > > > FWIW, few of the cards I've bought over the years sport netboot. And, > > netboot is an impossibility in 'embedded' systems that use things like > > PCMCIA/CARDBUS, which are becoming common-place for embedded routers and > > such. > > Argh! More FUD! Network booting is not an impossibility in an > embedded product using PCCARD or CARDBUS. Ok, please explain how I add a netboot prom to my 3C589 card? > > Netboot (IMO) is an unacceptable solution to many folks. It seems that > > 'progress' in this case means removing alot of existing functionality > > that is used by a number of folks. > > > > (CDROM root, BOOTP, etc...) > > More FUD! CDROM root devices still work fine. Then you do a very poor job of writing commit logs. +++++++++++++++++++++++++++++++++++++++++++++++ msmith 1999/11/01 15:51:01 PST Modified files: sys/kern vfs_conf.c ... Log: This is a complete rewrite of vfs_conf.c, which changes the way the root filesystem is discovered. .... In addition, support for CDROM root devices has been removed; it was a nasty hack and didn't work. +++++++++++++++++++++++++++++++++++++++++++++++ Note the last sentence. Does that say that support for CDROM root devices has been removed? I thought it did. > The automated search > stuff was broken, and it's gone because it was in the way. There will > be a new automated search process that will work properly. I thought the general idea was that *until* something better came along, you left things the way they were (ie; not removing them). That's certainly the message that's been communicated in the past. > BOOTP in > the kernel will go _when_there_is_an_acceptable_alternative_. You've already stated *THERE IS AN ACCEPTABLE ALTERNATIVE*, and it's PXE. (I can use all caps instead of underscores to make a point too :) > Yes, progress means losing the crap. One man's crap is another man's diamond... > How much more like a shark would you look like if you didn't lose your > baby teeth? There ya go, Mike. Let's degenerate this dicussion into name calling and putdowns, cause that'll make you feel better, won't it? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 11:18:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 4130014CE0 for ; Wed, 3 Nov 1999 11:18:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA06730; Wed, 3 Nov 1999 11:09:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911031909.LAA06730@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Network booting, I'm off to work (was Re: GENERIC build broken) In-reply-to: Your message of "Wed, 03 Nov 1999 10:43:43 PST." <199911031843.KAA60534@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Nov 1999 11:09:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok folks. It's pretty clear that Matt and I have a difference of opinion here. I can either spend more time trying to deal with what I see as FUD, or actually do the work, and I'm picking the latter. Yes, I'm aware of what people are currently doing inre: diskless booting. No, I don't plan to arbitrarily sabotage these already-working configurations just for the fun of it. Yes, there are continuation plans that should allow almost all of these configurations to continue to work, either in their current or a slightly modified form. No, I don't mean to force anyone to go buy new bootroms, or to upgrade their hardware. But yes, this is the best way to get diskless booting to work right. Understand that development work that's worthwhile is focussed on the future. FreeBSD is not an operating system for retired hardware; that's across the hall with the NetBSD folks. We need to keep ourselves focussed on where we're going, and right now, in this context, it means that we need to look at doing PXE on i386 properly. I'm more than happy to talk to people about the technical issues involved (and have been behind all the smoke), and I've had an open call for participants and contributors for months (almost no respondents) to both do the grunt work and help drive the bus. Thanks for following this, and I hope to have something to show for it fairly soon. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 12:27: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 30E1615531 for ; Wed, 3 Nov 1999 12:27:02 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA147102; Wed, 3 Nov 1999 15:25:21 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <199911031917.MAA10150@mt.sri.com> References: <199911031844.LAA09963@mt.sri.com> <199911031857.KAA06668@dingo.cdrom.com> <199911031917.MAA10150@mt.sri.com> Date: Wed, 3 Nov 1999 15:26:43 -0500 To: nate@mt.sri.com (Nate Williams), Mike Smith From: Garance A Drosihn Subject: Re: GENERIC build broken Cc: nate@mt.sri.com (Nate Williams), current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:17 PM -0700 11/3/99, Nate Williams wrote: > > BOOTP in > > the kernel will go _when_there_is_an_acceptable_alternative_. > >You've already stated *THERE IS AN ACCEPTABLE ALTERNATIVE*, and it's >PXE. (I can use all caps instead of underscores to make a point too :) I thought he was saying that "bootp in the kernel" should be removed at some point in the future. Not "all bootp" support, but just "inside-the-kernel hacks for bootp". I say let's cross the "remove bootp in the kernel" bridge when we actually come to it. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 12:28:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id ABEF4150F0 for ; Wed, 3 Nov 1999 12:28:22 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA41826; Wed, 3 Nov 1999 15:27:32 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <199911031909.LAA06730@dingo.cdrom.com> References: <199911031909.LAA06730@dingo.cdrom.com> Date: Wed, 3 Nov 1999 15:28:53 -0500 To: Mike Smith , Matthew Dillon From: Garance A Drosihn Subject: Re: Network booting, I'm off to work (was Re: GENERIC build broken) Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:09 AM -0800 11/3/99, Mike Smith wrote: >I can either spend more time trying to deal with what I see >as FUD, or actually do the work, and I'm picking the latter. > >[...snip...]. We need to keep ourselves focussed on where we're >going, and right now, in this context, it means that we need >to look at doing PXE on i386 properly. I believe this work will be valuable, and look forward to it. Some of this discussion will be easier once we have an actual implementation in front of us. I do appreciate the advance notice though, as we (some of us here at RPI) will be buying some new intel-ish machines soon, and networking booting is a going to be a topic of keen interest on those machines. If proper support for PXE will be coming to FreeBSD, then we'll be sure to keep that in mind with this new hardware that we are going to be buying anyway. FreeBSD can worry about ripping out other older options (such as bootp in the kernel) after we have the new options in place. Once everyone can actually test the new options, then we can have a productive discussion as to whether the old options should go. I personally have no idea whether they should or should not go, I'm just hoping we can defer that debate until after we have alternatives (including PXE support) ready. Note that I am assuming that the new PXE support will not *REQUIRE* that any old support be ripped out, and thus we do not need to debate the second question at this time. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 13:10:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 8BB8314C83; Wed, 3 Nov 1999 13:10:50 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Thu, 4 Nov 1999 08:05:18 +1100 Content-return: prohibited Date: Thu, 4 Nov 1999 08:10:43 +1100 From: Peter Jeremy Subject: Pageable kernels (was Re: diskless boot roadmap) In-reply-to: <99110304555400.19188@nomad.dataplex.net> To: Richard Wackerbarth Cc: freebsd-current@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov4.080518est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <99Nov3.160403est.40416@border.alcanet.com.au> <199911030515.VAA02306@dingo.cdrom.com> <99Nov3.163119est.40376@border.alcanet.com.au> <99110304555400.19188@nomad.dataplex.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This is heading more towards -arch than -current] On 1999-Nov-03 21:53:07 +1100, Richard Wackerbarth wrote: >> How much of the probe code can we move into userland? >Or alternately, transient kernel memory. Use it, then lose it. IMHO, there are some items (like the PNP ID tables) that really belong in a user-editable file, rather than the kernel source. This file could then be read by /boot/loader (and maybe a runtime daemon similar to pccardd). And taking the idea of transient kernel memory a bit further: How about supporting paging within the kernel? At least for text space, this would seem to be a fairly simple matter of tagging functions as pageable (eg add '__attribute__((section("text_pageable")))' to the function declaration), and treating that section of KVM the same way as user text space (though probably with a higher preference for being resident and a higher priority for paging in). Paging data may be a bit trickier, but would seem to be amenable to a mixture of variable attributes and a new `pageable' flag for kernel malloc. Initialisation code is an obvious candidate for paging, but I suspect that everything except interrupt handlers, the paging code and device drivers associated with the paging devices could be made pageable. In fact, the above all sounds so obvious and simple that I wonder if I'm missing something... Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 13:12:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id A2C3215394 for ; Wed, 3 Nov 1999 13:12:02 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id F0BAE3E30; Wed, 3 Nov 1999 22:11:54 +0100 (CET) Date: Wed, 3 Nov 1999 22:11:54 +0100 From: Jesper Skriver To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: ep problem with 4.0-19991101-CURRENT snapshot Message-ID: <19991103221154.A26018@skriver.dk> References: <19991101210440.A12410@skriver.dk> <199911030422.VAA17265@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911030422.VAA17265@harmony.village.org>; from imp@village.org on Tue, Nov 02, 1999 at 09:22:50PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 02, 1999 at 09:22:50PM -0700, Warner Losh wrote: > In message <19991101210440.A12410@skriver.dk> Jesper Skriver writes: > : sysinstall can assign a ip address via. DHCP, but the machine cannot be > : ping'ed from other hosts on the lan, same if I manually configure ep0 > : via ifconfig. > > This sounds like the classic "The right interrupt isn't assigned > problem" that I see from time to time. What IRQ did ep0 say it was > using? Ditto for pcic0? You're right, disabled the sound card, so ep0 got it's own, and now it's working, thanks. /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 13:46:33 1999 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 3ECFF150CA for ; Wed, 3 Nov 1999 13:46:27 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11j8E1-0006ZE-00 for current@freebsd.org; Wed, 3 Nov 1999 21:45:49 +0000 Date: Wed, 3 Nov 1999 22:45:48 +0100 (CET) From: Marc Schneiders To: current@freebsd.org Subject: make release won't work for me 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 To save on bandwidth and the ridiculous phone charges I pay, I would like to make release to install on another machine, as I am afraid installing 3.1 (of which I have the CD) and updating from the /usr/obj on my main machine (which I did before) might not work with recent changes in current. Cvsupped an hour ago and cvs-ed my /usr/src against my /home/ncvs. Did set CVSROOT and in the Makefile BUILDNAME and CHROOTDIR. # cd /usr/src/release and # make release Starts and runs ok for a while... This is where it stops: ===> gnu/usr.bin/grep install -c -s -o root -g wheel -m 555 grep /reserve/usr/bin /reserve/usr/bin/egrep -> /reserve/usr/bin/grep /reserve/usr/bin/fgrep -> /reserve/usr/bin/grep /reserve/usr/bin/zgrep -> /reserve/usr/bin/grep /reserve/usr/bin/zegrep -> /reserve/usr/bin/grep /reserve/usr/bin/zfgrep -> /reserve/usr/bin/grep ===> gnu/usr.bin/grep/doc sflag=`grep -q ^INFO-DIR-SECTION grep.info || echo 1`; eflag=`grep -q ^START-INFO-DIR-ENTRY grep.info || echo 1`; install-info ${sflag:+--section="System Utilities"} ${eflag:+--entry=} grep.info /reserve/usr/share/info/dir grep: grep.info: No such file or directory grep: grep.info: No such file or directory install-info: No such file or directory for grep.info *** Error code 1 I had the same a couple of days back. Both trying make release 3.3 and 4.0. Posted it to questions@ but no reply. Is it too stupid to answer maybe? Please ridicule me! Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 10:24pm up 7 days, 16:05, load average: 0.07 0.04 0.27 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 13:57:41 1999 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 918EB14EA1 for ; Wed, 3 Nov 1999 13:57:31 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11j8Pw-000DGq-00 for current@freebsd.org; Wed, 3 Nov 1999 21:58:08 +0000 Date: Wed, 3 Nov 1999 22:57:29 +0100 (CET) From: Marc Schneiders To: current@freebsd.org Subject: make release stupidity ..? 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 Forget for now, pls, about my earlier message. Found some discussion about this (I hope) in cvs-all. Thx. Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 10:55pm up 7 days, 16:36, load average: 0.70 0.27 0.18 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 14:24: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id C94ED150E6 for ; Wed, 3 Nov 1999 14:23:53 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id OAA39942 for ; Wed, 3 Nov 1999 14:23:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911032223.OAA39942@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: vga driver and signal Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Nov 1999 14:23:15 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Say is there anyone that can add signal delivery to the /sys/dev/fb/vga.c? (For now any quick hack to the driver for delivering the signal will do ) The context is from a posting to the xfree86 mailing list: keithp@suse.com said: > You need to fit one event in per retrace. If you knew > the phase of the sampling clock with respect to the retrace > you could do that by skipping one sample then two then one, etc... > But we don't know the phase and if you do that with > arbitrary phase you end up sending two events in one retrace > and then skipping the next and it looks worse. > If we had a signal delivered at vertical retrace time, we could easily > sync the mouse rate with the video rate -- run the mouse events > through a simple filter and estimate mouse position at the vertical > retrace interval using some forward estimation. > Additionally, the vertical retrace signal could be used for the double > buffering extension to avoid tearing, and for the sync extension which > kinda wants this. And for many video cards which can't update > colormaps or cursor positions at other times without visible artifacts > on the screen. > It would take some kernel work though; the results might well be worth > the effort. > -keith I am too busy nowdays working :( Have Fun Guys! -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 15:41:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id D7A1A1510E for ; Wed, 3 Nov 1999 15:41:03 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Thu, 4 Nov 1999 10:34:16 +1100 Content-return: prohibited Date: Thu, 4 Nov 1999 10:39:40 +1100 From: Peter Jeremy Subject: Re: CTM-deltas generation sptopped ? In-reply-to: <199911031258.SAA02128@wint.itfs.nsk.su> To: nnd@mail.nsk.ru Cc: freebsd-current@freebsd.org, chuckr@picnic.mat.net Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov4.103416est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <199911031258.SAA02128@wint.itfs.nsk.su> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-03 23:58:00 +1100, nnd@mail.nsk.ru wrote: > There are no new CTM-deltas on 'ctm.freebsd.org' >at least 22 hours. The last e-mail delta I have is cvs-cur.5804, which arrived here at 0808UTC (about 5 hours before your message). I would have expected to receive 5805 (or at least an initial part) about 5 hours ago now, so I suspect something is wrong. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 16:22:36 1999 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 B1B5A15664 for ; Wed, 3 Nov 1999 16:22:21 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p27-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id LAA25923; Thu, 4 Nov 1999 11:27:20 +1100 Date: Thu, 4 Nov 1999 11:22:06 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: nnd@mail.nsk.ru Cc: freebsd-current@FreeBSD.ORG Subject: Re: CTM-deltas generation sptopped ? In-Reply-To: <199911031258.SAA02128@wint.itfs.nsk.su> 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, 3 Nov 1999 nnd@mail.nsk.ru wrote: > There are no new CTM-deltas on 'ctm.freebsd.org' > at least 22 hours. > > Is this known problem ? I've been waiting 41 hours now for cvs-cur.5804.gz. Also, ftp.freebsd.org has been hard to reach since freebsdcon (it usually refuses to connect since it has 5000 users). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 17:27:52 1999 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 C90B014E96 for ; Wed, 3 Nov 1999 17:27:46 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p27-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA31402; Thu, 4 Nov 1999 12:32:48 +1100 Date: Thu, 4 Nov 1999 12:27:34 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: YAJKHT (Yet a Junior kernel hacker task) In-Reply-To: <32336.941655423@critter.freebsd.dk> 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 > About the only place which is sacred is the gdb-stubs, please be > aware that particular isolation requirements apply to that code > which make it un-smart to rely on library functions. (that is why > the gdb-stubs even come with their own strlen(3) & strcat(3) The same applies to ddb and everything else that is called before vm is initialised. gdb is just less chummy with the "library" than ddb. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 18: 4: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id D850D14E27 for ; Wed, 3 Nov 1999 18:03:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA01738 for ; Wed, 3 Nov 1999 17:53:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911040153.RAA01738@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Re: cvs commit: src/sys/kern vfs_conf.c In-reply-to: Your message of "Wed, 03 Nov 1999 17:40:18 PST." <199911040140.RAA14380@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Nov 1999 17:53:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This should bring CDROM-as-root operation almost back to the state it was at prior to my gutting the i386 autoconf.c. I've left the really old-and-nasty cdrom drives out of the list of devices that are searched for automatically; you can either specify the device manually with eg. set vfs.root.mountfrom=cd9660:/dev/matcd0a in the loader or, if you really need them working like this let me know and I'll add them to the list. For IDE and SCSI cdroms, you can just boot -C in the loader and all should work like it used to. Note that there's now no dependancy between root on a cdrom and the CD9660_ROOT option; you should be able to boot eg. a UFS filesystem off a cdrom with an appropriate vfs.root.mountfromn setting. The -C auto-search won't find this combination unless you update the list of defaults it tries however. Please note that I say "should"; this code looks right and builds OK, but I don't have a CD to try it with. Feedback would be appreciated. Thanks to Guy Helmer for pointing out that the cdrom-as-root stuff did actually work for him. Note that this commit was delayed about 8 hours by painful and pointless bike-shed discussions. 8( > msmith 1999/11/03 17:40:18 PST > > Modified files: > sys/kern vfs_conf.c > Log: > Re-implement the handing of RB_CDROM in a machine-independant fashion. > We currently only search SCSI and IDE CDROMs; if there's felt to be a > need for supporting the very old and rare soundcard etc. drives for this > application they can be trivially added. > > Revision Changes Path > 1.36 +25 -1 src/sys/kern/vfs_conf.c > > > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 18:51:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id B39CC14CFB for ; Wed, 3 Nov 1999 18:51:22 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id IAA03088; Thu, 4 Nov 1999 08:47:27 +0600 (NOVT) (envelope-from nnd) Date: Thu, 4 Nov 1999 08:47:27 +0600 (NOVT) Message-Id: <199911040247.IAA03088@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: freebsd-current@freebsd.org Subject: Re: CTM-deltas generation sptopped ? In-Reply-To: <99Nov4.103416est.40323@border.alcanet.com.au> User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <99Nov4.103416est.40323@border.alcanet.com.au> Peter Jeremy wrote: > On 1999-Nov-03 23:58:00 +1100, nnd@mail.nsk.ru wrote: >> There are no new CTM-deltas on 'ctm.freebsd.org' >>at least 22 hours. > > The last e-mail delta I have is cvs-cur.5804, which arrived here at > 0808UTC (about 5 hours before your message). I would have expected to > receive 5805 (or at least an initial part) about 5 hours ago now, so I > suspect something is wrong. So, "generation" process is not totally stopped, but there is no cvs-cur.5804 in the FTP repositores at least on 'ctm.freebsd.org' and 'ftp.freebsd.org'. Other CTM "collections" also have no new deltas in FTP archives on the abovementioned sites. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 3 20:14:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 37BE515635; Wed, 3 Nov 1999 20:14:07 -0800 (PST) (envelope-from andrews@technologist.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=argon) by neptune.psn.net with smtp (PSN Internet Service 2.12 #3) id 11jEGU-0005dT-00; Wed, 3 Nov 1999 21:12:47 -0700 Message-Id: <3.0.6.32.19991103231237.008b0d40@mail.psn.net> X-Sender: andrews@mail.psn.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 03 Nov 1999 23:12:37 -0500 To: Warner Losh From: Will Andrews Subject: Re: laptop problems Cc: mobile@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199911012325.QAA09846@harmony.village.org> References: <3.0.6.32.19991101181513.0081bb40@mail.psn.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:25 PM 11/1/99 -0700, you wrote: >What's your eeporm problem? I have fixed and committed patches to the >ep driver where the card wasn't being identified. I thought I sent you something about this before.. My card IS getting recognized, and seems to be on the appropriate port, BUT, I think memory pointers are getting mixed up, because it's returning the _WRONG_ MAC address. Plus, 'pccard0' is being used even though it's not in the kernel currently loaded. Here's the kernel output (that I found erroneous): pcic: polling, can't alloc 0 pcic: polling, can't alloc 0 Here's the pccardd output: ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at port 0x240-0x25f irq 10 slot 0 on pccard0 ep0: Ethernet address 4b:57:4b:57:4b:57 ep0: strange connector type in EEPROM, assuming AUI Yes, I have a 3Com 3CCFE574BT that has worked with -CURRENT before. And yes, the kernel sources (at least relevant to pccard) is up to date, including your EEPROM an pcic_p.c (or whatever) fixes. The devclass_alloc_unit() problem was fixed by the pcic_p.c fix, but EEPROM problems lurk. :\ >Me too. I'll know when I get home tonight. Well? *cross fingers* :) --- It's been a few days since I wrote this reply. I've been hacking /sys/dev/ep/if_ep.c, trying to figure out what's wrong. I originally thought the ep_get_macaddr() function's for() loop was erroneous in that it uses an integer `i' in the for loop instead of a u_int_16. That theory didn't go (still got the wrong MAC addresses.. something's not right.), however, I did find out that the polling thing was caused by pcic's IRQ not being assigned properly. I hardwared the pcic_irq = 11; in my /sys/pccard/pcic.c, and that removed the error. So, somebody borked pcic.c in this respect somewhere (haven't looked further yet), although this hardwire didn't fix the MAC address problem. Then I had a look at the odd EEPROM problem, which seems to have been caused by erroneous values in IFM_ETHER_10T, etc. I put in a debugging device_printf(), and found my ifm.ifmedia (whatever's in the switch() with a default: that outputs the error message above (it's in /sys/dev/ep/if_ep.c)) to equal 0. What the hell's wrong with this thing? IFM_ETHER_10T should be 0, judging by the array definition given. Perhaps you meant to use an enum? Anyway, I plugged in a case 0: to see if that fixed the problem, and it did. So, something's borked with that too. /me will check CVS logs tomorrow to see if in one place or another ep_get_macaddr(), etc. got borked somehow. Thoughts / Comments? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 0: 4:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (deep-thought.demos.su [195.133.1.74]) by hub.freebsd.org (Postfix) with ESMTP id 69F9A14C94; Thu, 4 Nov 1999 00:04:46 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id LAA02956; Thu, 4 Nov 1999 11:04:00 +0300 (MSK) (envelope-from ache) Date: Thu, 4 Nov 1999 11:03:59 +0300 From: "Andrey A. Chernov" To: scsi@freebsd.org, current@freebsd.org Subject: -current panic on AHA Message-ID: <19991104110359.A2933@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Very fresh -current always paniced after detecting SCSI devices on aha0: AHA-1542CF FW Rev. B.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs page fault: supervisor, read page not present Old kernel from Oct 8 works nicely Sorry can't provide more info about panic, it is remote computer. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 0:12:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D69B14CE0 for ; Thu, 4 Nov 1999 00:12:22 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm202.cvzoom.net (lcm202.cvzoom.net [208.230.69.202]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id CAA09215 for ; Thu, 4 Nov 1999 02:53:41 -0500 (EST) Date: Thu, 4 Nov 1999 03:11:21 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: ESS 1868 driver (again) 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 got the one email that said that there was some trouble with the ESS 1868 sound driver under FreeBSD-current. Is there an issue with -current and newpcm that is causing the 1868 sound driver to not work? Also, I'd like to know how to compile the newpcm sound driver as a loadable kernel module, so that I can just load and unload it with kld{load,unload}. I tried the patch Sanpei gave me, but no dice (ESS 1868). When I try playing certain RealPlayer clips, for example, a 2 minute clip will finish in about 10 seconds with short bursts of sound along the way. Actually, it does play the entire clip through, but the entire clip goes wizzing by at an extremely high rate of speed with only short bursts of sound along the way. Video+audio clips will show a "fast-forwarding" effect with no or short bursts of sound. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 0:19:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id D68E814CE0 for ; Thu, 4 Nov 1999 00:19:43 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.2/8.9.2) id JAA37674; Thu, 4 Nov 1999 09:18:53 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911040818.JAA37674@info.iet.unipi.it> Subject: Re: ESS 1868 driver (again) In-Reply-To: from Donn Miller at "Nov 4, 1999 3:11:21 am" To: dmmiller@cvzoom.net (Donn Miller) Date: Thu, 4 Nov 1999 09:18:53 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I got the one email that said that there was some trouble with the ESS > 1868 sound driver under FreeBSD-current. Is there an issue with -current > and newpcm that is causing the 1868 sound driver to not work? Also, I'd guys, you should realize that the ESS1868 codecs (and friends) are extremely unfriendly to the programmer, and possibly (according to Sanpei comments) broken in their handling of auto-dma. As a consequence i cannot believe anyone wants to write a driver for this chip fighting against all idiosincracies of the hardware and its ugly design. If you have a machine with that card, just replace it with a better supported one. If you have a laptop with that card, well, you have bad luck, but chances are that your laptop is already obsolete and in 1yrs you will have to replace it because the battery has died, the keyboard has broken keys, and the hard disk starts failing on some sectors. Just be patient... cheers luigi > module, so that I can just load and unload it with kld{load,unload}. > > I tried the patch Sanpei gave me, but no dice (ESS 1868). When I try > playing certain RealPlayer clips, for example, a 2 minute clip will finish > in about 10 seconds with short bursts of sound along the way. Actually, > it does play the entire clip through, but the entire clip goes wizzing by > at an extremely high rate of speed with only short bursts of sound along > the way. Video+audio clips will show a "fast-forwarding" effect with no > or short bursts of sound. > > - Donn > > > > 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 Nov 4 1:35:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id F3CC014CF8 for ; Thu, 4 Nov 1999 01:35:37 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcm202.cvzoom.net (lcm202.cvzoom.net [208.230.69.202]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id EAA12017; Thu, 4 Nov 1999 04:15:59 -0500 (EST) Date: Thu, 4 Nov 1999 04:33:38 -0500 (EST) From: Donn Miller To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: ESS 1868 driver (again) In-Reply-To: <199911040818.JAA37674@info.iet.unipi.it> 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, 4 Nov 1999, Luigi Rizzo wrote: > guys, you should realize that the ESS1868 codecs (and friends) > are extremely unfriendly to the programmer, and possibly > (according to Sanpei comments) broken in their handling of > auto-dma. As a consequence i cannot believe anyone wants to > write a driver for this chip fighting against all idiosincracies > of the hardware and its ugly design. > > If you have a machine with that card, just replace it with a better > supported one. If you have a laptop with that card, well, you have Which members of the SoundBlaster family are supported? Is the SoundBlaster 16 WavEffects supported? I'd like to get one of the wavetable synth models. Thanks. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 5: 5:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 8A220156FC for ; Thu, 4 Nov 1999 05:05:55 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:A1Yb3W2MhArt90/l8sW++PCe561mA91+@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id WAA29919; Thu, 4 Nov 1999 22:04:23 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA16201; Thu, 4 Nov 1999 22:08:57 +0900 (JST) Message-Id: <199911041308.WAA16201@zodiac.mech.utsunomiya-u.ac.jp> To: Amancio Hasty Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: vga driver and signal In-reply-to: Your message of "Wed, 03 Nov 1999 14:23:15 PST." <199911032223.OAA39942@rah.star-gate.com> References: <199911032223.OAA39942@rah.star-gate.com> Date: Thu, 04 Nov 1999 22:08:56 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AFAIK, not all video cards generate the vertical retrace interrupt. Even worse, some BIOSes have a configuration option which instract the BIOS NOT to assign an IRQ to the PCI video card. I fully agree that the vertical retrace interrupt will be of great value, but I wonder if it is really worth the trouble, because it might be available in only few cards and systems at the end of the day... Well, I may be wrong :-) Kazu >Say is there anyone that can add signal delivery to the /sys/dev/fb/vga.c? >(For now any quick hack to the driver for delivering the signal will do ) > >The context is from a posting to the xfree86 mailing list: > > >keithp@suse.com said: >> You need to fit one event in per retrace. If you knew >> the phase of the sampling clock with respect to the retrace >> you could do that by skipping one sample then two then one, etc... >> But we don't know the phase and if you do that with >> arbitrary phase you end up sending two events in one retrace >> and then skipping the next and it looks worse. >> If we had a signal delivered at vertical retrace time, we could easily >> sync the mouse rate with the video rate -- run the mouse events >> through a simple filter and estimate mouse position at the vertical >> retrace interval using some forward estimation. > >> Additionally, the vertical retrace signal could be used for the double >> buffering extension to avoid tearing, and for the sync extension which >> kinda wants this. And for many video cards which can't update >> colormaps or cursor positions at other times without visible artifacts >> on the screen. > >> It would take some kernel work though; the results might well be worth >> the effort. > >> -keith > >I am too busy nowdays working :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 5:14:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CD23215749 for ; Thu, 4 Nov 1999 05:14:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA93012; Thu, 4 Nov 1999 14:13:23 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911041313.OAA93012@freebsd.dk> Subject: Re: vga driver and signal In-Reply-To: <199911041308.WAA16201@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Nov 4, 1999 10:08:56 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 4 Nov 1999 14:13:23 +0100 (CET) Cc: hasty@rah.star-gate.com (Amancio Hasty), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 It seems Kazutaka YOKOTA wrote: > > AFAIK, not all video cards generate the vertical retrace interrupt. > Even worse, some BIOSes have a configuration option which instract the > BIOS NOT to assign an IRQ to the PCI video card. > > I fully agree that the vertical retrace interrupt will be of great > value, but I wonder if it is really worth the trouble, because it might > be available in only few cards and systems at the end of the day... > > Well, I may be wrong :-) Well, sortof :) The delay caused by the system to process the interrupt and deliver the signal etc is unpredictable (well sortof) and is almost certainly too long so the window of opportunity will be missed ... This has been discussed to death many times in the past for the mouse pointer updates etc etc... -Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 5:29:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 4A78E14DEB for ; Thu, 4 Nov 1999 05:29:10 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:lvOtpj+ThhEP7C+JQO4vFhN4HrWs6Cvn@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id WAA31511; Thu, 4 Nov 1999 22:26:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA16908; Thu, 4 Nov 1999 22:30:56 +0900 (JST) Message-Id: <199911041330.WAA16908@zodiac.mech.utsunomiya-u.ac.jp> To: Soren Schmidt Cc: hasty@rah.star-gate.com (Amancio Hasty), current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 14:13:23 +0100." <199911041313.OAA93012@freebsd.dk> References: <199911041313.OAA93012@freebsd.dk> Date: Thu, 04 Nov 1999 22:30:55 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Well, I may be wrong :-) > >Well, sortof :) > >The delay caused by the system to process the interrupt and deliver >the signal etc is unpredictable (well sortof) and is almost certainly >too long so the window of opportunity will be missed ... > >This has been discussed to death many times in the past for the >mouse pointer updates etc etc... > >-Soren You are absolutely right. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 6: 9:41 1999 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 1A22E1504C for ; Thu, 4 Nov 1999 06:09:37 -0800 (PST) (envelope-from dennis.glatting@software-munitions.com) Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157]) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id GAA28427; Thu, 4 Nov 1999 06:08:14 -0800 (PST) X-Authentication-Warning: btw.plaintalk.bellevue.wa.us: Host fwiw.plaintalk.bellevue.wa.us [206.129.5.157] claimed to be software-munitions.com Message-ID: <3821934D.E01B1045@software-munitions.com> Date: Thu, 04 Nov 1999 06:08:13 -0800 From: Dennis Glatting X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: vga driver and signal References: <199911032223.OAA39942@rah.star-gate.com> <199911041308.WAA16201@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms6EE05AD488DDFC4BA6D7C8DB" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms6EE05AD488DDFC4BA6D7C8DB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kazutaka YOKOTA wrote: > > I fully agree that the vertical retrace interrupt will be of great > value, but I wonder if it is really worth the trouble, because it might > be available in only few cards and systems at the end of the day... > I may have value synchronizing animation, such as games. --------------ms6EE05AD488DDFC4BA6D7C8DB Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIKLgYJKoZIhvcNAQcCoIIKHzCCChsCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B7owggSEMIID7aADAgECAhAV4oOYVg1pE0gVFzzXJ4WbMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDMyMTAwMDAw MFoXDTAwMDMyMDIzNTk1OVowggEoMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxGDAWBgNVBAMUD0Rlbm5pcyBHbGF0dGluZzE1MDMGCSqG SIb3DQEJARYmZGVubmlzLmdsYXR0aW5nQHNvZnR3YXJlLW11bml0aW9ucy5jb20wgZ8wDQYJ KoZIhvcNAQEBBQADgY0AMIGJAoGBAKSBSrAz19P5zPsu3odv359aq1FIuU7RXSXlVga0DqpE ST8T6/e3wtn1f8NnfnytpCWP4r2FgO51Z2Q8o5fy99Gajtlm5tYDBEm09HGWoxAYfEJE8oVI lMCDRQazW5WFiY8WkoNl36eoVl0Oa5rsaSMnk5u45R7Mu3wyLRBooXfnAgMBAAGjggEGMIIB AjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUF BwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVy aVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2Ug bGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYDVR0fBCww KjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0B AQQFAAOBgQAlb2LpvHzHBF/o/uILYbM2MGnIkf4y7PN+XQnMAXpk1mIFeVtIH+kquwCo93ra 9h1wdohBxmPt4Sw/EHG4WNr8PnYXuo7kFOBokqSTOYQTr/6zbSKnjXhO3N4qWKoS0dK0G8GO QTKulULvZBkmbnHJ1YIvES2KH7hC2Uzs1K7SDDCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKo JV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2ln biwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9u IEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5NTlaMIHMMRcwFQYDVQQK Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4s TElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFs IFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEBAQUAA4GN ADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZMUFweoFLuUgT Vi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5UiE+HSr8Z2vkV6A+Hthzj zMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMC AQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNp Z24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQDAgEGMA0G CSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bxndPKZDjcG5gMB4ZbhRVq D7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9d WBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYICPDCCAjgCAQEwgeEwgcwx FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3 b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEBXig5hWDWkTSBUX PNcnhZswCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3 DQEJBTEPFw05OTExMDQxNDA4MTNaMCMGCSqGSIb3DQEJBDEWBBQcUjVL1txnuNPhWyXhShlp 1SlzzjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAHBgUr DgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgC3d iS9O4vCTvUdsYUSE7uGsSURFSyVIQPnRbwTRvMtcBMUYe4GdLgBsvHl6ZWEBAJw1nRhqZtBa QW10ncj9h9Z73QVYqIPgz4rMO/ekokv1TxwkrQd9fBNj2M2JMNATEC+AHnNZnB5SRJ7lkZ50 mbrckYVViNZEc0Kf0OvK2EAP --------------ms6EE05AD488DDFC4BA6D7C8DB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 6:13:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id F17021504C for ; Thu, 4 Nov 1999 06:13:23 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA01341; Thu, 4 Nov 1999 09:13:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA07769; Thu, 4 Nov 1999 09:12:46 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 4 Nov 1999 09:12:46 -0500 (EST) To: Mike Smith Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Network booting, I'm off to work (was Re: GENERIC build broken) In-Reply-To: <199911031909.LAA06730@dingo.cdrom.com> References: <199911031843.KAA60534@apollo.backplane.com> <199911031909.LAA06730@dingo.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14369.35974.496839.872957@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, I'm not trying to contribute to the FUD, rather I'm just trying to understand what you're proposing and what effect it will have on my current environment. Right now we have an OS research cluster of 30+ Pentium II machines. These machines are used for both real research & for class projects by students who have root access to them & who can install their own hacked kernels. These machines are essentially crashboxes. These machines boot off of local IDE & SCSI disks. They are all rackmounted, so they run headless & have their console via a serial port. Most do not even have graphics cards installed. Interacting with the BIOS is a painful process involving walking over to the lab, pulling a box off the rack, moving it to the workbench, inserting a video card & attaching a monitor/kbd. My install process is to boot the machines diskless via a BOOTP kernel stashed away on the root filesystem of the machine (or on a floppy if it is a first time install, or if things get really out of hand). When a machine boots diskless, it mounts a shared volume on the installation server. A script is run (I call it mirror) which disklabels the disk & restores a dump(8)ed backup of a good 'prototype' machine. The script continues on to massage a few configuration files (eg, setting the hostname & ipaddr) and builds an fstab based on what the root disks name is. All of this takes about 10 minutes max. Maybe 15 if I have to walk over to the lab & plunk a floppy in the box. Because these machines get trashed fairly frequently (students with root access who are hacking device drivers can trash all sorts of things in many fun & exciting ways! You should try it if you're in need of laughs sometime!) the ability to restore a box to sanity quickly is very important to me. My question boils down to: Will I be able to re-install a machine using your new i386 netboot just as easily as I can now? Or will I have to be physically present at each machine & diddle with the bios to toggle between disk & netboots? And what if the NIC doesn't support PXE? Am I just SOL? Again, I'm not trying to contribute to the FUD. I'm just not sure I understand how what you are proposing will affect me. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 7:23:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by hub.freebsd.org (Postfix) with ESMTP id B2E2014C32 for ; Thu, 4 Nov 1999 07:23:43 -0800 (PST) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtprch1.nortel.com; Thu, 4 Nov 1999 09:18:52 -0600 Received: from hcarp00g.ca.nortel.com by zcars01t; Thu, 4 Nov 1999 10:18:42 -0500 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id KAA08827 for ; Thu, 4 Nov 1999 10:21:55 -0500 (EST) Date: Thu, 4 Nov 1999 10:21:55 -0500 (EST) From: "Andrew Atrens" X-Sender: atrens@hcarp00g.ca.nortel.com Reply-To: "Andrew Atrens" To: current@freebsd.org Subject: Re: ESS 1868 driver (again) 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 All, I'm having trouble with my old Yamaha OPL based ISA soundcard. It used to work flawlessly, but now as Don, I get `bursty' sound. Most pronounced effect is when using `rvplayer'. If I open rvplayer and click to play a sound clip everything is just peachy until I move the mouse, causing a window to autoraise or some such (basically generating X activity) at which point the clip starts `bursting'. For fun I tried running rvplayer with `rtprio'. Folks don't try this at home :) . The clip plays flawlessly _but_ my machine is completely locked up for the duration. Further, when playing short clips through `nas', I typically only get to hear one burst of the clip. The effect is kind of like what one hears when cruising for tunes using an old AM `dial' radio. Interestingly enough, mpg123 and xanim seem unaffected. Here's how my card is currently detected - pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 Yamaha: ver 0x21 DMA config 0x84 pcm: setmap 30000, ff00; 0xc77e9000 -> 30000 pcm: setmap 40000, ff00; 0xc77f9000 -> 40000 unknown0: at port 0x201 on isa0 If I'm not mistaken the old pcm preferred MSS emulation for this card. Is it possible that the new pcm tries to use SB emulation ? I ask because I know my SB emulation settings for this card are _wrong_. With old pcm, this didn't appear to matter, but with new pcm, hmmmm. Something to try out I guess when I get home tonight :) .. Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 10: 3:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 6ABFD151C2 for ; Thu, 4 Nov 1999 10:02:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id KAA46924; Thu, 4 Nov 1999 10:01:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911041801.KAA46924@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), current@FreeBSD.ORG Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 14:13:23 +0100." <199911041313.OAA93012@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 10:01:37 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Kazutaka YOKOTA wrote: > > > > AFAIK, not all video cards generate the vertical retrace interrupt. > > Even worse, some BIOSes have a configuration option which instract the > > BIOS NOT to assign an IRQ to the PCI video card. > > > > I fully agree that the vertical retrace interrupt will be of great > > value, but I wonder if it is really worth the trouble, because it might > > be available in only few cards and systems at the end of the day... > > > > Well, I may be wrong :-) > > Well, sortof :) > > The delay caused by the system to process the interrupt and deliver > the signal etc is unpredictable (well sortof) and is almost certainly > too long so the window of opportunity will be missed ... > > This has been discussed to death many times in the past for the > mouse pointer updates etc etc... > Let me ask a different question: How does Microsoft's DirectX handle delivery of vertical retrace interrupt? -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 10: 8: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 2250F14DF6 for ; Thu, 4 Nov 1999 10:07:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id KAA46989; Thu, 4 Nov 1999 10:07:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911041807.KAA46989@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA Cc: current@freebsd.org Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 22:08:56 +0900." <199911041308.WAA16201@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 10:07:14 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > AFAIK, not all video cards generate the vertical retrace interrupt. > Even worse, some BIOSes have a configuration option which instract the > BIOS NOT to assign an IRQ to the PCI video card. > > I fully agree that the vertical retrace interrupt will be of great > value, but I wonder if it is really worth the trouble, because it might > be available in only few cards and systems at the end of the day... > > Well, I may be wrong :-) It is okay if the card does not have a vertical retrace option and if it is disabled by the BIOS I hope that the PCI header info for the vga card states that the interrupt is disabled. Just generate a patch and pass it on to the Xfree86 group . They are trying all sort of things to sync up the mouse with the vga vertical retrace interrupt. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 11: 0:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 821EA15794 for ; Thu, 4 Nov 1999 11:00:45 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA77394; Thu, 4 Nov 1999 20:00:06 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911041900.UAA77394@freebsd.dk> Subject: Re: vga driver and signal In-Reply-To: <199911041801.KAA46924@rah.star-gate.com> from Amancio Hasty at "Nov 4, 1999 10:01:37 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 4 Nov 1999 20:00:06 +0100 (CET) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), 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 Amancio Hasty wrote: > > It seems Kazutaka YOKOTA wrote: > > > > > > AFAIK, not all video cards generate the vertical retrace interrupt. > > > Even worse, some BIOSes have a configuration option which instract the > > > BIOS NOT to assign an IRQ to the PCI video card. > > > > > > I fully agree that the vertical retrace interrupt will be of great > > > value, but I wonder if it is really worth the trouble, because it might > > > be available in only few cards and systems at the end of the day... > > > > > > Well, I may be wrong :-) > > > > Well, sortof :) > > > > The delay caused by the system to process the interrupt and deliver > > the signal etc is unpredictable (well sortof) and is almost certainly > > too long so the window of opportunity will be missed ... > > > > This has been discussed to death many times in the past for the > > mouse pointer updates etc etc... > > > > Let me ask a different question: How does Microsoft's DirectX handle delivery > of vertical retrace interrupt? I dont know (and dont care) if/how they do, but they would have to do some pretty nasty hacks to get that to work, maybe thats why directx is lacking behind on NT their top notch OS?? We care about multitasking, wintendo dont. The problem is that in say 1024*768@75Hz you have about 800us in the vertical blank period, then try messure our interrupt latency (or better ask PHK he's done lots in that direction), then take a look at the signal code. What else did I forget, oh well you probably wont have 800us, the videochip's requirements will probably cut that down significantly, you will probably need to do a couble of inb/outb's that has to finish within the window to make this usefull as well.. Oh and yes, you have to make damn sure no other interrupts occur when you have gotten control, or your timing will get skewed too.. Now take some serious resolutions like 1280*1024@80Hz and this rapidly becomes a nightmare. Belive me, I did spend alot of time with this for the mousepointer stuff, and the best way I could come up with was busypolling for the event to happen, and that is a nono ... -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 Nov 4 11: 8:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id ECA9714DA1 for ; Thu, 4 Nov 1999 11:08:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id LAA47415; Thu, 4 Nov 1999 11:07:53 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911041907.LAA47415@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), current@FreeBSD.ORG Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 20:00:06 +0100." <199911041900.UAA77394@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 11:07:53 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What will happen if the X server was running with real time priorities which syncing up with a vertical retrace seems to imply? -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 11:54:26 1999 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 0ACE115127; Thu, 4 Nov 1999 11:53:55 -0800 (PST) (envelope-from imp@harmony.village.org) 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 MAA74475; Thu, 4 Nov 1999 12:53:27 -0700 (MST) (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 MAA09155; Thu, 4 Nov 1999 12:52:47 -0700 (MST) Message-Id: <199911041952.MAA09155@harmony.village.org> To: Will Andrews Subject: Re: laptop problems Cc: mobile@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 03 Nov 1999 23:12:37 EST." <3.0.6.32.19991103231237.008b0d40@mail.psn.net> References: <3.0.6.32.19991103231237.008b0d40@mail.psn.net> <3.0.6.32.19991101181513.0081bb40@mail.psn.net> Date: Thu, 04 Nov 1999 12:52:47 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3.0.6.32.19991103231237.008b0d40@mail.psn.net> Will Andrews writes: : My card IS getting recognized, and seems to be on the appropriate port, : BUT, I think memory pointers are getting mixed up, because it's : returning the _WRONG_ MAC address. That's usually an indication that something is wrong. : Plus, 'pccard0' is being used even : though it's not in the kernel currently loaded. It must be, or it won't work at all. : Here's the kernel output (that I found erroneous): : pcic: polling, can't alloc 0 : pcic: polling, can't alloc 0 Hardwire your pcic's irq to one that works. : Here's the pccardd output: : : ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at : port 0x240-0x25f irq 10 slot 0 on pccard0 : ep0: Ethernet address 4b:57:4b:57:4b:57 : ep0: strange connector type in EEPROM, assuming AUI : : Yes, I have a 3Com 3CCFE574BT that has worked with -CURRENT before. : And yes, the kernel sources (at least relevant to pccard) is up to : date, including your EEPROM an pcic_p.c (or whatever) fixes. The : devclass_alloc_unit() problem was fixed by the pcic_p.c fix, but : EEPROM problems lurk. :\ Hmmm. Looks like I'll need access to the hardware to fix it then. Or Matt Dodd will. : It's been a few days since I wrote this reply. I've been hacking : /sys/dev/ep/if_ep.c, trying to figure out what's wrong. I : originally thought the ep_get_macaddr() function's for() loop : was erroneous in that it uses an integer `i' in the for loop : instead of a u_int_16. That theory didn't go (still got the : wrong MAC addresses.. something's not right.), however, I did : find out that the polling thing was caused by pcic's IRQ not : being assigned properly. I hardwared the pcic_irq = 11; in my : /sys/pccard/pcic.c, and that removed the error. So, somebody : borked pcic.c in this respect somewhere (haven't looked : further yet), although this hardwire didn't fix the MAC : address problem. I woundn't expect it to. : Then I had a look at the odd EEPROM problem, which seems to have : been caused by erroneous values in IFM_ETHER_10T, etc. I put in : a debugging device_printf(), and found my ifm.ifmedia (whatever's : in the switch() with a default: that outputs the error message : above (it's in /sys/dev/ep/if_ep.c)) to equal 0. What the hell's : wrong with this thing? IFM_ETHER_10T should be 0, judging by : the array definition given. Perhaps you meant to use an enum? : Anyway, I plugged in a case 0: to see if that fixed the problem, : and it did. So, something's borked with that too. : : /me will check CVS logs tomorrow to see if in one place or : another ep_get_macaddr(), etc. got borked somehow. Patches? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 12: 0:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 180B415127 for ; Thu, 4 Nov 1999 12:00:44 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA91632 for current@FreeBSD.ORG; Thu, 4 Nov 1999 13:00:44 -0700 (MST) (envelope-from ken) Message-Id: <199911042000.NAA91632@panzer.kdm.org> Subject: TCP sockets stuck in the CLOSING state To: current@FreeBSD.ORG Date: Thu, 4 Nov 1999 13:00:44 -0700 (MST) From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (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 Before I spend a lot of time hunting this down, I figured it might be worth asking -- is there any particular reason why TCP sockets may be getting stuck in the CLOSING state more often now? I upgraded a machine from -current as of about June 26th to -current as of last Friday (October 29th), and I've got an ever increasing number of sockets stuck in the CLOSING state: Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 myhost.1929 othermailserver1.auth CLOSING tcp 0 0 myhost.1904 othermailserver1.auth CLOSING tcp 0 0 myhost.1899 othermailserver1.auth CLOSING tcp 0 0 myhost.4570 othermailserver1.auth CLOSING tcp 0 0 myhost.3659 othermailserver1.auth CLOSING tcp 0 0 myhost.3524 somewebserver.http CLOSING tcp 0 0 myhost.3171 othermailserver1.auth CLOSING tcp 0 0 myhost.3080 othermailserver1.auth CLOSING tcp 0 0 myhost.2957 othermailserver1.auth CLOSING tcp 0 0 myhost.2006 othermailserver2.smtp CLOSING tcp 0 0 myhost.1808 othermailserver1.auth CLOSING tcp 0 0 myhost.1632 othermailserver1.auth CLOSING tcp 0 0 myhost.1603 othermailserver1.auth CLOSING tcp 0 0 myhost.1558 hub.FreeBSD.ORG.smtp CLOSING tcp 0 0 myhost.1320 othermailserver1.auth CLOSING tcp 0 0 myhost.4374 othermailserver1.auth CLOSING tcp 0 0 myhost.4102 othermailserver1.auth CLOSING tcp 0 0 myhost.4067 othermailserver1.auth CLOSING tcp 0 0 myhost.3101 othermailserver2.smtp CLOSING tcp 0 0 myhost.3030 othermailserver1.auth CLOSING tcp 0 0 myhost.1609 othermailserver1.auth CLOSING This didn't seem to happen with the previous version of -current. I looked through the commitlogs for the TCP code, and I saw some timer changes, but nothing that looked like it would obviously have this effect. Anyone have any ideas? Thanks, Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 13:22:12 1999 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 68C8815210 for ; Thu, 4 Nov 1999 13:22:09 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id NAA21840; Thu, 4 Nov 1999 13:46:01 -0800 (PST) Date: Thu, 4 Nov 1999 13:46:01 -0800 (PST) From: Alfred Perlstein To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG Subject: Re: TCP sockets stuck in the CLOSING state In-Reply-To: <199911042000.NAA91632@panzer.kdm.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 Thu, 4 Nov 1999, Kenneth D. Merry wrote: > > Before I spend a lot of time hunting this down, I figured it might be worth > asking -- is there any particular reason why TCP sockets may be getting > stuck in the CLOSING state more often now? > > I upgraded a machine from -current as of about June 26th to -current as of > last Friday (October 29th), and I've got an ever increasing number of > sockets stuck in the CLOSING state: > > Active Internet connections > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp 0 0 myhost.1929 othermailserver1.auth CLOSING > tcp 0 0 myhost.1904 othermailserver1.auth CLOSING .... > tcp 0 0 myhost.1609 othermailserver1.auth CLOSING > > This didn't seem to happen with the previous version of -current. I looked > through the commitlogs for the TCP code, and I saw some timer changes, but > nothing that looked like it would obviously have this effect. > > Anyone have any ideas? me too! Needed to reboot to allow something to bind to the socket. Ie. happening to server side sockets. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 16:42:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from roadwarrior.stanford.edu (Ricochet-9.Stanford.EDU [171.66.252.9]) by hub.freebsd.org (Postfix) with ESMTP id A29D214D2B for ; Thu, 4 Nov 1999 16:42:28 -0800 (PST) (envelope-from techie@roadwarrior.stanford.edu) Received: (from techie@localhost) by roadwarrior.stanford.edu (8.9.3/8.9.2) id QAA00326 for current@freebsd.org; Thu, 4 Nov 1999 16:42:15 -0800 (PST) (envelope-from techie) Date: Thu, 4 Nov 1999 16:42:15 -0800 (PST) From: Bob Vaughan Message-Id: <199911050042.QAA00326@roadwarrior.stanford.edu> To: current@freebsd.org Subject: boot problems with todays kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG kernel source cvsup'd within the last hour.. world from 991101 Preloaded elf module "linux.ko" at 0xc03bf2cc. Preloaded elf module "atapi.ko" at 0xc03bf36c. link_elf: symbol atapi_drvtab undefined Intel Pentium detected, installing workaround for F00F bug VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c7a88 (c0007a88) VESA: Copyright 1994 TRIDENT MICROSYSTEMS INC. apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 devclass_alloc_unit: npx0 already exists, using next available unit number isa0: on isab0 ide_pci0: at device 1.1 on pci0 uhci0: irq 0 at device 1.2 on pci0 uhci0: could not map ports device_probe_and_attach: uhci0 attach returned 6 chip1: at device 1.3 on pci0 vga-pci0: at device 2.0 on pci0 pcic-pci0: irq 10 at device 3.0 on pci0 pcic-pci1: irq 10 at device 3.1 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 3909MB (8007552 sectors), 7944 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, accel, dma, iordy wcd0: drive speed 2416KB/sec, 128KB cache wcd0: supported read types: CD-DA wcd0: Audio: play, 16 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at irq 10 on isa0 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 sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 unknown0: at port 0x800-0x807 on isa0 pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 unknown1: at port 0x201 on isa0 Mounting root from ufs:/dev/wd0s1a pccard: card inserted, slot 0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0680c04 stack pointer = 0x10:0xc03d3f08 frame pointer = 0x10:0x2a94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = none # # ROADWARRIOR -- Laptop machine with ide/usb/pcmcia/tools # # $Id: ROADWARRIOR,v 1.143.3.0.1 1999/11/03 21:15:00 techie Exp $ machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident ROADWARRIOR maxusers 30 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores ## options from LINT options MD5 options PERFMON options NETATALK options ICMP_BANDLIM options PCIC_RESUME_RESET options MROUTING # Multicast routing options COMPAT_LINUX options POWERFAIL_NMI options INCLUDE_CONFIG_FILE options DDB options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) controller isa0 controller pnp0 controller eisa0 controller pci0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 device wcd0 #IDE CD-ROM # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor device npx0 at isa? port IO_NPX irq 13 device apm0 at nexus? flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support device pcic0 at isa? device pcic1 at isa? controller card0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 controller miibus0 device ep0 device ed0 at isa? port 0x320 irq 11 conflicts iomem 0xd8000 # audio device pcm0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 4 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf 4 # Berkeley packet filter pseudo-device snp # USB support controller uhci0 # UHCI PCI->USB interface controller usb0 # USB Bus (required) device ugen0 # Generic device uhid0 # "Human Interface Devices" device ukbd0 # Keyboard device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 device ums0 # Mouse -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@w6yx.stanford.edu | kc6sxc@w6yx.ampr.org | techie@t.stanford.edu | KC6SXC@W6YX.#NCA.CA.USA.NOAM | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 16:43: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 0B1FB14D2B for ; Thu, 4 Nov 1999 16:42:53 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id QAA49569 for ; Thu, 4 Nov 1999 16:41:28 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050041.QAA49569@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: reply to field Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 16:41:28 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Curious, why is the reply field in the email header not set to the originating mailing list? Just thought that it will make it easier to reply to postings to the mailing lists so people don't get multiple copies of the same message. I don't have such problem because I have a mail filter which delete duplicate messages. Cheers -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 16:55:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id B17171511A for ; Thu, 4 Nov 1999 16:55:22 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FKP003MF95RCZ@mta3.rcsntx.swbell.net> for current@FreeBSD.ORG; Thu, 4 Nov 1999 18:53:51 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id SAA19750; Thu, 04 Nov 1999 18:54:33 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Thu, 04 Nov 1999 18:54:32 -0600 From: Chris Costello Subject: Re: reply to field In-reply-to: <199911050041.QAA49569@rah.star-gate.com> To: Amancio Hasty Cc: current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991104185432.T602@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199911050041.QAA49569@rah.star-gate.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 04, 1999, Amancio Hasty wrote: > Curious, why is the reply field in the email header not set > to the originating mailing list? Just thought that it will make > it easier to reply to postings to the mailing lists so people don't > get multiple copies of the same message. I don't have such > problem because I have a mail filter which delete duplicate > messages. a.) Your message is off-topic. Please don't post this sort of thing to -current anymore. b.) I think it's useful. When someone responds to me on the list, I get a copy in my main mailbox and in the mailbox where I keep messages for that list. -- |Chris Costello |Last one out, turn off the computer! `------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 16:58: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rp-plus.de (clubserv.rp-online.de [149.221.232.11]) by hub.freebsd.org (Postfix) with ESMTP id 73373151AF for ; Thu, 4 Nov 1999 16:57:45 -0800 (PST) (envelope-from alex@cichlids.com) Received: from neutron.cichlids.com (as8-pri51.rp-plus.de [149.221.239.179]) by mail.rp-plus.de (8.9.1a/8.9.1) with ESMTP id BAA09494; Fri, 5 Nov 1999 01:57:32 +0100 (MET) Received: from cichlids.cichlids.com (root@cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (8.9.3/8.9.1) with ESMTP id BAA30476; Fri, 5 Nov 1999 01:57:49 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id BAA21322; Fri, 5 Nov 1999 01:57:36 +0100 (CET) (envelope-from alex) From: Alexander Langer Date: Fri, 5 Nov 1999 01:57:36 +0100 To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: reply to field Message-ID: <19991105015736.A21301@cichlids.cichlids.com> Mail-Followup-To: Amancio Hasty , current@FreeBSD.ORG References: <199911050041.QAA49569@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911050041.QAA49569@rah.star-gate.com>; from hasty@rah.star-gate.com on Thu, Nov 04, 1999 at 04:41:28PM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Amancio Hasty (hasty@rah.star-gate.com): > it easier to reply to postings to the mailing lists so people don't > get multiple copies of the same message. I don't have such > problem because I have a mail filter which delete duplicate > messages. Reply-To: also destroys private Reply-To:'s. You can use a MUA, that supports "group reply", as Mutt does. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 17: 7:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id A4AD91511A for ; Thu, 4 Nov 1999 17:07:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id RAA49835; Thu, 4 Nov 1999 17:05:53 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050105.RAA49835@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alexander Langer Cc: current@FreeBSD.ORG Subject: Re: reply to field In-reply-to: Your message of "Fri, 05 Nov 1999 01:57:36 +0100." <19991105015736.A21301@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 17:05:53 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thus spake Amancio Hasty (hasty@rah.star-gate.com): > > > it easier to reply to postings to the mailing lists so people don't > > get multiple copies of the same message. I don't have such > > problem because I have a mail filter which delete duplicate > > messages. > > Reply-To: also destroys private Reply-To:'s. > > You can use a MUA, that supports "group reply", as Mutt does. > I just thought it was a good idea . Recently I subscribed to another group mailing lists and the folks over there don't seem to mind if the reply field is set . The net effect is less traffic on the net and those who hate the extra traffic over their links love it. Cheers -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 17:13: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B7476156AC for ; Thu, 4 Nov 1999 17:12:50 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id BAA73384; Fri, 5 Nov 1999 01:13:07 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 5 Nov 1999 01:13:07 +0000 (GMT) From: Doug Rabson To: Amancio Hasty Cc: Soren Schmidt , Kazutaka YOKOTA , current@freebsd.org Subject: Re: vga driver and signal In-Reply-To: <199911041801.KAA46924@rah.star-gate.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 Thu, 4 Nov 1999, Amancio Hasty wrote: > > It seems Kazutaka YOKOTA wrote: > > > > > > AFAIK, not all video cards generate the vertical retrace interrupt. > > > Even worse, some BIOSes have a configuration option which instract the > > > BIOS NOT to assign an IRQ to the PCI video card. > > > > > > I fully agree that the vertical retrace interrupt will be of great > > > value, but I wonder if it is really worth the trouble, because it might > > > be available in only few cards and systems at the end of the day... > > > > > > Well, I may be wrong :-) > > > > Well, sortof :) > > > > The delay caused by the system to process the interrupt and deliver > > the signal etc is unpredictable (well sortof) and is almost certainly > > too long so the window of opportunity will be missed ... > > > > This has been discussed to death many times in the past for the > > mouse pointer updates etc etc... > > > > Let me ask a different question: How does Microsoft's DirectX handle delivery > of vertical retrace interrupt? It doesn't. DX8 might deal with this, I'm not sure. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 17:15:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id 2637B151DC for ; Thu, 4 Nov 1999 17:10:24 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id TAA38738; Thu, 4 Nov 1999 19:01:48 -0600 (CST) (envelope-from obonilla) Date: Thu, 4 Nov 1999 19:01:48 -0600 From: Oscar Bonilla To: Chris Costello Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: reply to field Message-ID: <19991104190148.A38726@fisicc-ufm.edu> References: <199911050041.QAA49569@rah.star-gate.com> <19991104185432.T602@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <19991104185432.T602@holly.calldei.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 04, 1999 at 06:54:32PM -0600, Chris Costello wrote: > On Thu, Nov 04, 1999, Amancio Hasty wrote: > > Curious, why is the reply field in the email header not set > > to the originating mailing list? Just thought that it will make > > it easier to reply to postings to the mailing lists so people don't > > get multiple copies of the same message. I don't have such > > problem because I have a mail filter which delete duplicate > > messages. > > a.) Your message is off-topic. Please don't post this sort of > thing to -current anymore. agreed. > b.) I think it's useful. When someone responds to me on the > list, I get a copy in my main mailbox and in the mailbox > where I keep messages for that list. > this has been discussed in depth on the mailing lists. search for it and you'll find pleny of reasons why to set/not set the reply to field. regards, -oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 17:18:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-198-202.guate.net [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id 7AAEC1561B for ; Thu, 4 Nov 1999 17:16:04 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id TAA38738; Thu, 4 Nov 1999 19:01:48 -0600 (CST) (envelope-from obonilla) Date: Thu, 4 Nov 1999 19:01:48 -0600 From: Oscar Bonilla To: Chris Costello Cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: reply to field Message-ID: <19991104190148.A38726@fisicc-ufm.edu> References: <199911050041.QAA49569@rah.star-gate.com> <19991104185432.T602@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <19991104185432.T602@holly.calldei.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 04, 1999 at 06:54:32PM -0600, Chris Costello wrote: > On Thu, Nov 04, 1999, Amancio Hasty wrote: > > Curious, why is the reply field in the email header not set > > to the originating mailing list? Just thought that it will make > > it easier to reply to postings to the mailing lists so people don't > > get multiple copies of the same message. I don't have such > > problem because I have a mail filter which delete duplicate > > messages. > > a.) Your message is off-topic. Please don't post this sort of > thing to -current anymore. agreed. > b.) I think it's useful. When someone responds to me on the > list, I get a copy in my main mailbox and in the mailbox > where I keep messages for that list. > this has been discussed in depth on the mailing lists. search for it and you'll find pleny of reasons why to set/not set the reply to field. regards, -oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 17:30:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 00D2E14F59 for ; Thu, 4 Nov 1999 17:30:37 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id TAA04858; Thu, 4 Nov 1999 19:28:49 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id TAA27568; Thu, 4 Nov 1999 19:28:49 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id PAA20756; Thu, 4 Nov 1999 15:44:45 -0600 (CST) Date: Thu, 4 Nov 1999 15:44:45 -0600 (CST) From: Jonathan Lemon Message-Id: <199911042144.PAA20756@free.pcs> To: ken@kdm.org, current@freebsd.org Subject: Re: TCP sockets stuck in the CLOSING state X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > >Before I spend a lot of time hunting this down, I figured it might be worth >asking -- is there any particular reason why TCP sockets may be getting >stuck in the CLOSING state more often now? Not sure. But here's a tcpdump trace of a socket that ends up in the CLOSING state. (on the host ``cache''). 14:55:49.142607 folly.56982 > cache.9000: S 1691420120:1691420120(0) win 16384 (DF) 14:55:49.142663 cache.9000 > folly.56982: S 1946461253:1946461253(0) ack 1691420121 win 17520 (DF) 14:55:49.142991 folly.56982 > cache.9000: . ack 1 win 17520 (DF) 14:55:49.143384 folly.56982 > cache.9000: P 1:188(187) ack 1 win 17520 (DF) 14:55:49.340283 cache.9000 > folly.56982: . ack 188 win 17520 (DF) 14:55:50.287660 cache.9000 > folly.56982: P 1:1442(1441) ack 188 win 17520 (DF) 14:55:50.484537 cache.9000 > folly.56982: . 1442:2902(1460) ack 188 win 17520 (DF) 14:55:50.484552 cache.9000 > folly.56982: P 2902:4362(1460) ack 188 win 17520 (DF) 14:55:50.490171 cache.9000 > folly.56982: P 4362:4781(419) ack 188 win 17520 (DF) 14:55:50.490369 cache.9000 > folly.56982: F 4781:4781(0) ack 188 win 17520 (DF) 14:55:50.492154 folly.56982 > cache.9000: . ack 4781 win 17520 (DF) 14:55:50.492160 folly.56982 > cache.9000: F 188:188(0) ack 4781 win 17520 (DF) 14:55:50.492229 cache.9000 > folly.56982: . ack 189 win 17520 (DF) 14:55:51.490279 cache.9000 > folly.56982: . ack 189 win 17520 (DF) Note that I think there are at least two oddities here: 1. the other end (folly) never acks the FIN. The packets at timestamp .492154 and .492160 do not cover the FIN in the sequence space. Yet the host `folly' closes the socket. 2. the end that is stuck in CLOSING (cache) never retransmits the FIN. (The tcpdump extends for about 5 minutes after the last packet, with 0 packets lost). Both machines are running -current from early this week. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 18:36:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 16FE415753 for ; Thu, 4 Nov 1999 18:36:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA00620; Thu, 4 Nov 1999 18:23:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911050223.SAA00620@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: Soren Schmidt , yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), current@FreeBSD.ORG Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 11:07:53 PST." <199911041907.LAA47415@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 18:23:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What will happen if the X server was running with real time priorities which > syncing up with a vertical retrace seems to imply? The only real way to do this "right" is going to be to have the X server load a KLD, which will then be able to hook the relevant interrupt(s). Any other alternative involves interrupt delivery to user-space, which is just not practical. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 18:43:45 1999 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 B6879157AD for ; Thu, 4 Nov 1999 18:43:39 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA58383; Thu, 4 Nov 1999 21:42:42 -0500 (EST) (envelope-from wollman) Date: Thu, 4 Nov 1999 21:42:42 -0500 (EST) From: Garrett Wollman Message-Id: <199911050242.VAA58383@khavrinen.lcs.mit.edu> To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: reply to field In-Reply-To: <199911050041.QAA49569@rah.star-gate.com> References: <199911050041.QAA49569@rah.star-gate.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Curious, why is the reply field in the email header not set > to the originating mailing list? Because that would be an incredibly obnoxious (I would even say asinine) thing to do. If I want to make a reply to the list, I'll make a reply to the list. If I don't, I won't. Readers of the FreeBSD mailing-lists are expected to be smart enough to know the difference between ``reply'' and ``followup'' (or whatever the relevant commands in their MUA are). In short, we have had this discussion (at regular intervals) and the answer is still ``no''. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 18:43:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 540B715826 for ; Thu, 4 Nov 1999 18:43:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id SAA50513; Thu, 4 Nov 1999 18:41:55 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050241.SAA50513@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), current@FreeBSD.ORG Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 18:23:52 PST." <199911050223.SAA00620@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 18:41:55 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What will happen if the X server was running with real time priorities which > > syncing up with a vertical retrace seems to imply? > > The only real way to do this "right" is going to be to have the X > server load a KLD, which will then be able to hook the relevant > interrupt(s). Any other alternative involves interrupt delivery to > user-space, which is just not practical. > Hi Mike, Your idea sounds intriguing . How should we wired the KLD to the X server? or how will the KLD inform the X server that it has received a vertical retrace interrupt . -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 18:49:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 51BB5157A9 for ; Thu, 4 Nov 1999 18:49:46 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA24160; Fri, 5 Nov 1999 13:18:21 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911050241.SAA50513@rah.star-gate.com> Date: Fri, 05 Nov 1999 13:18:20 +1030 (CST) From: "Daniel O'Connor" To: Amancio Hasty Subject: Re: vga driver and signal Cc: current@FreeBSD.ORG, (Kazutaka YOKOTA) , Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Nov-99 Amancio Hasty wrote: > Your idea sounds intriguing . How should we wired the KLD to > the X server? or how will the KLD inform the X server that it > has received a vertical retrace interrupt . It depends what you wanted to do, but you could have the X server feed the KLD commands to do on a vert refresh, and when it happens the commands are executed in kernel mode, which would save you a lot of time. Kind of complex though. Also the interrupt latency problem is still there. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 18:56:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 2916315801 for ; Thu, 4 Nov 1999 18:56:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id SAA50665; Thu, 4 Nov 1999 18:54:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050254.SAA50665@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), Mike Smith Subject: Re: vga driver and signal In-reply-to: Your message of "Fri, 05 Nov 1999 13:18:20 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 18:54:11 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 05-Nov-99 Amancio Hasty wrote: > > Your idea sounds intriguing . How should we wired the KLD to > > the X server? or how will the KLD inform the X server that it > > has received a vertical retrace interrupt . > > It depends what you wanted to do, but you could have the X server feed the KLD > commands to do on a vert refresh, and when it happens the commands are executed > in kernel mode, which would save you a lot of time. > > Kind of complex though. Also the interrupt latency problem is still there. Not sure that this is as elegant as what you are suggesting , can the kernel schedule a user level routine to be executed when an interrupt occurs? I guess on Windoze land this is called a driver call-back. Just trying to prevent dragging the whole X server to the kernel -- Actually dragging the whole X server to the kernel is not a bad idea --- however it is something that I can not afford to do right now :( -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 18:57:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4FAD5157A9 for ; Thu, 4 Nov 1999 18:57:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA00787; Thu, 4 Nov 1999 18:47:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911050247.SAA00787@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: Mike Smith , yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), current@FreeBSD.ORG Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 18:41:55 PST." <199911050241.SAA50513@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 18:47:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The only real way to do this "right" is going to be to have the X > > server load a KLD, which will then be able to hook the relevant > > interrupt(s). Any other alternative involves interrupt delivery to > > user-space, which is just not practical. > > Hi Mike, > Your idea sounds intriguing . How should we wired the KLD to > the X server? or how will the KLD inform the X server that it > has received a vertical retrace interrupt . The X server would have to load the KLD when it starts. The KLD would have to contain _all_ of the code that would run when the interrupt triggered. You would still have absolutely no latency guarantee on delivery of the interrupt to the KLD; you'd have to check on entry to the handler to see whether you weren't already too late. Basically, the whole idea is just totally screwed. You shouldn't be trying to do this because it just can't be done right. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 19: 2:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id B3B4F157A9 for ; Thu, 4 Nov 1999 19:02:14 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id WAA07712; Thu, 4 Nov 1999 22:00:27 -0500 (EST) (envelope-from luoqi) Date: Thu, 4 Nov 1999 22:00:27 -0500 (EST) From: Luoqi Chen Message-Id: <199911050300.WAA07712@lor.watermarkgroup.com> To: current@FreeBSD.ORG, techie@roadwarrior.stanford.edu Subject: Re: boot problems with todays kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc0680c04 > stack pointer = 0x10:0xc03d3f08 > frame pointer = 0x10:0x2a94 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > interrupt mask = none > CVSup again. Mike Smith has just committed a fix. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 19: 2:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 147F615838 for ; Thu, 4 Nov 1999 19:02:36 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA24331; Fri, 5 Nov 1999 13:31:15 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911050254.SAA50665@rah.star-gate.com> Date: Fri, 05 Nov 1999 13:31:15 +1030 (CST) From: "Daniel O'Connor" To: Amancio Hasty Subject: Re: vga driver and signal Cc: Mike Smith Cc: Mike Smith , (Kazutaka YOKOTA) , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Nov-99 Amancio Hasty wrote: > Not sure that this is as elegant as what you are suggesting , can > the kernel schedule a user level routine to be executed when an interrupt > occurs? I guess on Windoze land this is called a driver call-back. Well.. KLD? :) Thats about as close as it gets. You would have to reload the KLD each time you wanted to change it.. Yech. IMHO Mike is right, its not something FreeBSD is geared towards because of interrupt latency. The KLD idea *could* work depending on what you wanted to do. > Just trying to prevent dragging the whole X server to the kernel -- > Actually dragging the whole X server to the kernel is not a bad > idea --- however it is something that I can not afford to do right now :( Well depends on your definition of 'bad'. No paging in the kernel, which would be kind of wasteful :) Go look at GGI for stuff about kernel gaphics drivers. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 19: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id E28BC15858 for ; Thu, 4 Nov 1999 19:02:43 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id JAA04430; Fri, 5 Nov 1999 09:01:06 +0600 (NOVT) (envelope-from nnd) Date: Fri, 5 Nov 1999 09:01:06 +0600 (NOVT) Message-Id: <199911050301.JAA04430@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: freebsd-current@freebsd.org Subject: Is CTM dead forever ? User-Agent: tin/pre-1.4-19990927 ("Nine While Nine") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can somebody check and say why there are no new cvs-cur CTM deltas after cvs-cur.5803.gz ? (at least on 'ctm.freebsd.org' and 'ftp.freebsd.org') Are there any other sites with FTP fetchable CTM deltas ? (and with more current ones ?) Yes, I can switch to 'cvs-up'ing FreeBSD sources, but this is less convinient here in Siberia :-) N. Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 19: 8: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 8BABE155D5 for ; Thu, 4 Nov 1999 19:08:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id TAA50795; Thu, 4 Nov 1999 19:05:41 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050305.TAA50795@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), current@FreeBSD.ORG Subject: Re: vga driver and signal In-reply-to: Your message of "Thu, 04 Nov 1999 18:47:35 PST." <199911050247.SAA00787@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 19:05:41 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The only real way to do this "right" is going to be to have the X > > > server load a KLD, which will then be able to hook the relevant > > > interrupt(s). Any other alternative involves interrupt delivery to > > > user-space, which is just not practical. > > > > Hi Mike, > > Your idea sounds intriguing . How should we wired the KLD to > > the X server? or how will the KLD inform the X server that it > > has received a vertical retrace interrupt . > > The X server would have to load the KLD when it starts. The KLD would > have to contain _all_ of the code that would run when the interrupt > triggered. You would still have absolutely no latency guarantee on > delivery of the interrupt to the KLD; you'd have to check on entry to > the handler to see whether you weren't already too late. > > Basically, the whole idea is just totally screwed. You shouldn't be > trying to do this because it just can't be done right. Hi Mike I should be trying to do this for it can have interesting applications such as a Tivo player. Not sure what the problem with interrupt latency is ... Can you elaborate a little bit more ? Tnks! -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 19:18:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from rmx06.iname.net (rmx06.iname.net [206.253.130.53]) by hub.freebsd.org (Postfix) with ESMTP id F2F4714DE6 for ; Thu, 4 Nov 1999 19:18:38 -0800 (PST) (envelope-from davec@unforgettable.com) Received: from weba7.iname.net by rmx06.iname.net (8.9.1/8.8.0) with ESMTP id WAA01673 ; Thu, 4 Nov 1999 22:14:53 -0500 (EST) From: davec@unforgettable.com Received: (from root@localhost) by weba7.iname.net (8.9.1a/8.9.2.Alpha2) id WAA19710; Thu, 4 Nov 1999 22:14:53 -0500 (EST) MIME-Version: 1.0 Message-Id: <991104221452CC.26561@weba7.iname.net> Date: Thu, 4 Nov 1999 22:14:52 -0500 (EST) Content-Type: Text/Plain Content-Transfer-Encoding: 7bit To: current@FreeBSD.ORG Subject: IPFilter in -current? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm curious as to the current status of IP Filter in the -current branch of FreeBSD. Since its removal from the kernel in October, there have been a few emails about getting/wanting it back. May I ask who is currently working on that and what sort of progress they are making? Thank you. Dave Davec@unforgettable.com ---------------------------------------------------------------- Get your free email from AltaVista at http://altavista.iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 19:39:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id D389C1567E for ; Thu, 4 Nov 1999 19:39:08 -0800 (PST) (envelope-from andrews@technologist.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=argon) by neptune.psn.net with smtp (PSN Internet Service 2.12 #3) id 11ja8v-00048X-00; Thu, 4 Nov 1999 20:34:26 -0700 Message-Id: <3.0.6.32.19991104222248.008b3e10@mail.psn.net> X-Sender: andrews@mail.psn.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 04 Nov 1999 22:22:48 -0500 To: Bob Vaughan From: Will Andrews Subject: Re: boot problems with todays kernel Cc: current@FreeBSD.ORG In-Reply-To: <199911050042.QAA00326@roadwarrior.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:42 PM 11/4/99 -0800, you wrote: Seems to me like a simple problem: >devclass_alloc_unit: npx0 already exists, using next available unit number >device npx0 at isa? port IO_NPX irq 13 Shouldn't this be "at nexus?" ? Like apm0 is. I'm not quite sure it was the problem that Mike Smith just fixed (vfs_conf.c, that is). Or was npx0's assignment changed in a recent commit? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 19:54:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 682F71567E for ; Thu, 4 Nov 1999 19:54:41 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id OAA62225; Fri, 5 Nov 1999 14:23:33 +1030 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199911050353.OAA62225@gizmo.internode.com.au> Subject: Re: vga driver and signal To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Nov 1999 14:23:33 +1030 (CST) Cc: doconnor@gsoft.com.au, current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp, mike@smith.net.au In-Reply-To: <199911050254.SAA50665@rah.star-gate.com> from "Amancio Hasty" at Nov 4, 99 06:54:11 pm X-Mailer: ELM [version 2.4 PL25] 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 Amancio Hasty wrote: > Not sure that this is as elegant as what you are suggesting , can > the kernel schedule a user level routine to be executed when an interrupt > occurs? I guess on Windoze land this is called a driver call-back. Under UNIX it's called a signal handler :-) - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 20:53:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 9D1A9150B7 for ; Thu, 4 Nov 1999 20:53:27 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.2/8.9.2) id FAA40729; Fri, 5 Nov 1999 05:52:02 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911050452.FAA40729@info.iet.unipi.it> Subject: Re: ESS 1868 driver (again) In-Reply-To: from "Charles M. Hannum" at "Nov 4, 1999 1:50:11 pm" To: root@ihack.net (Charles M. Hannum) Date: Fri, 5 Nov 1999 05:52:02 +0100 (CET) Cc: dmmiller@cvzoom.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 > Luigi Rizzo writes: > > > guys, you should realize that the ESS1868 codecs (and friends) > > are extremely unfriendly to the programmer, and possibly > > (according to Sanpei comments) broken in their handling of > > auto-dma. > > ?? > > I wouldn't say the interface is *pretty*, but the only problem we had > with these chips under NetBSD was figuring out how to differentiate > the various models. They work reasonably well, and we do use > auto-initialize DMA. (Several people are even using them in stereo > systems, as the ES1887 is what's in the Shark.) ok, the comment about auto-dma was just related to what i heard from other people who tried to add ESS support to the pcm driver. I should also mention that one of the goals of "pcm" was support of full duplex audio. I just gave up on the ESS after seeing how complex it would have been (in terms of changes to the pcm driver) to make it work in full duplex as well as in other modes. cheers luigi > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 21:18: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id BA36915206 for ; Thu, 4 Nov 1999 21:18:05 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by exit.com (8.9.3/8.9.3) with ESMTP id VAA56858 for ; Thu, 4 Nov 1999 21:18:00 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.1) id VAA29749 for current@freebsd.org; Thu, 4 Nov 1999 21:18:00 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199911050518.VAA29749@realtime.exit.com> Subject: Wondering about cardbus support. To: current@freebsd.org Date: Thu, 4 Nov 1999 21:18:00 -0800 (PST) Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the misfortune to have a cardbus Ethernet card that came with my Dell laptop. I was wondering how cardbus support was going, and if I could help in any way. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 21:20:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id A94AA1505E for ; Thu, 4 Nov 1999 21:20:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA01533; Thu, 4 Nov 1999 21:10:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911050510.VAA01533@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: current@FreeBSD.ORG Subject: Re: Network booting, I'm off to work (was Re: GENERIC build broken) In-reply-to: Your message of "Thu, 04 Nov 1999 09:12:46 EST." <14369.35974.496839.872957@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Nov 1999 21:10:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My question boils down to: Will I be able to re-install a machine > using your new i386 netboot just as easily as I can now? Or will I > have to be physically present at each machine & diddle with the bios > to toggle between disk & netboots? And what if the NIC doesn't > support PXE? Am I just SOL? The possible options in this scenario are massively varied, and which one you go with is going to depend on a variety of factors. If we assume that you can use PXE with your boxes, you could configure each machine to try booting from the net first, and then fall back to local disk. When you wanted to recover a machine, you'd enable the DHCP server config for it, and punt the machine. If the DHCP server was answering for it, it'd come up off the network regardless of the state of the disk. In conjunction with some networked power switches this'd let you reinstall without ever leaving your office. This is what PXE was originally all about; unattended diskless (re)installs. If you can't, or don't want to use PXE network bootstraps for your machines, your 'rescue' kernel would just contain an MFS with a DHCP client and a tiny script to find your installation server's shared volume. You could use the PicoBSD tools to build this very easily. Those are what I'd consider to be the two cleanest and easiest approaches in your particular situation. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 21:41:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B5BC614DE6 for ; Thu, 4 Nov 1999 21:41:54 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA05591; Fri, 5 Nov 1999 00:39:21 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 5 Nov 1999 00:39:21 -0500 (EST) From: Chuck Robey To: peter.jeremy@alcatel.com.au Cc: nnd@mail.nsk.ru, freebsd-current@freebsd.org Subject: Re: CTM-deltas generation sptopped ? In-Reply-To: <99Nov4.103416est.40323@border.alcanet.com.au> 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, 4 Nov 1999, Peter Jeremy wrote: > On 1999-Nov-03 23:58:00 +1100, nnd@mail.nsk.ru wrote: > > There are no new CTM-deltas on 'ctm.freebsd.org' > >at least 22 hours. > > The last e-mail delta I have is cvs-cur.5804, which arrived here at > 0808UTC (about 5 hours before your message). I would have expected to > receive 5805 (or at least an initial part) about 5 hours ago now, so I > suspect something is wrong. I stopped reading the list for a few days (letting my mail pile up) while I handled a panic situation at the University, sorry. I can't traceroute or ping the source of ctm's, and I have mail out to the owner of the system. Now that I'm aware, I will follow this as fast as I can. > > Peter > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 22: 4:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9]) by hub.freebsd.org (Postfix) with SMTP id F1E02152A2 for ; Thu, 4 Nov 1999 22:04:30 -0800 (PST) (envelope-from spock@techfour.net) Received: (qmail 26840 invoked from network); 5 Nov 1999 06:02:17 -0000 Received: from cm-208-138-197-238.fredericksburg.mg.ispchannel.com (HELO enterprise.muriel.penguinpowered.com) (208.138.197.238) by mail001.mediacity.com with SMTP; 5 Nov 1999 06:02:17 -0000 Content-Length: 1088 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.6.32.19991104222248.008b3e10@mail.psn.net> X-SENDERNAME: `Mike Heffner` Date: Fri, 05 Nov 1999 01:03:50 -0500 (EST) From: Mike Heffner To: Will Andrews Subject: Re: boot problems with todays kernel Cc: current@FreeBSD.ORG, Bob Vaughan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Nov-99 Will Andrews chanted: | At 04:42 PM 11/4/99 -0800, you wrote: | | Seems to me like a simple problem: | |>devclass_alloc_unit: npx0 already exists, using next available unit number | |>device npx0 at isa? port IO_NPX irq 13 | | Shouldn't this be "at nexus?" ? Like apm0 is. I'm not quite sure it was | the problem that Mike Smith just fixed (vfs_conf.c, that is). | | Or was npx0's assignment changed in a recent commit? i've noticed the same message (devclass_alloc_unit...) with a recent kernel, but it hasn't effected anything. i haven't had the time to track it down, so i just ignored the message | | -- | Will Andrews | GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- | ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ | G++>+++ e->++++ h! r-->+++ y? | --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 05-Nov-99 Time: 01:01:11 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 22:46:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id A0E6F14DA4; Thu, 4 Nov 1999 22:46:06 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA46540; Fri, 5 Nov 1999 08:43:35 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911050643.IAA46540@gratis.grondar.za> To: "Andrey A. Chernov" Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: -current panic on AHA Date: Fri, 05 Nov 1999 08:43:35 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Very fresh -current always paniced after detecting SCSI devices on > aha0: AHA-1542CF FW Rev. B.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs > page fault: supervisor, read page not present > Old kernel from Oct 8 works nicely > Sorry can't provide more info about panic, it is remote computer. This is not SCSI specific. It is happening on my Libretto laptop and a dual-cpu PPRO box with SCSI (AHC). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 22:47:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70]) by hub.freebsd.org (Postfix) with ESMTP id 6CE2614DA4 for ; Thu, 4 Nov 1999 22:47:38 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id WAA40360; Thu, 4 Nov 1999 22:44:54 -0800 (PST) Date: Thu, 4 Nov 1999 22:44:54 -0800 (PST) From: Bob Vaughan Message-Id: <199911050644.WAA40360@tantivy.stanford.edu> To: andrews@technologist.com, techie@roadwarrior.stanford.edu Subject: Re: boot problems with todays kernel Cc: current@FreeBSD.ORG In-Reply-To: <3.0.6.32.19991104222248.008b3e10@mail.psn.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok.. I tweaked the conf, and re-cvsup'd.. and i now have a bootable kernel.. but there is now another problem.. (see below) > From andrews@technologist.com Thu Nov 4 19:36:38 1999 > Date: Thu, 04 Nov 1999 22:22:48 -0500 > To: Bob Vaughan > From: Will Andrews > Subject: Re: boot problems with todays kernel > Cc: current@FreeBSD.ORG > > At 04:42 PM 11/4/99 -0800, you wrote: > > Seems to me like a simple problem: > > >devclass_alloc_unit: npx0 already exists, using next available unit number > > >device npx0 at isa? port IO_NPX irq 13 > > Shouldn't this be "at nexus?" ? Like apm0 is. I'm not quite sure it was > the problem that Mike Smith just fixed (vfs_conf.c, that is). > > Or was npx0's assignment changed in a recent commit? > I'm now running into issues with pccard and the ep driver, where ep0 (3c574B) is seen at boot time, at a familiar port/irq, but with a bogus mac address.. (4b:57:4b:57:4b:57). ifconfig -a will immediately lock up the system, with a reboot following a minute or two later.. this only happens when there is a card inserted.. roadwarrior shutdown: reboot by techie: roadwarrior syslogd: exiting on signal 15 roadwarrior /kernel: roadwarrior /kernel: syncing disks... done roadwarrior /kernel: Rebooting... roadwarrior /kernel: Copyright (c) 1992-1999 The FreeBSD Project. roadwarrior /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 roadwarrior /kernel: The Regents of the University of California. All rights reserved. roadwarrior /kernel: FreeBSD 4.0-CURRENT #3: Thu Nov 4 21:16:03 PST 1999 roadwarrior /kernel: techie@roadwarrior.stanford.edu:/c1/current/src/sys/compile/ROADWARRIOR roadwarrior /kernel: Timecounter "i8254" frequency 1193182 Hz roadwarrior /kernel: CPU: Pentium/P55C (233.87-MHz 586-class CPU) roadwarrior /kernel: Origin = "GenuineIntel" Id = 0x543 Stepping = 3 roadwarrior /kernel: Features=0x8001bf roadwarrior /kernel: real memory = 100663296 (98304K bytes) roadwarrior /kernel: avail memory = 93634560 (91440K bytes) roadwarrior /kernel: Preloaded elf kernel "kernel" at 0xc03bf000. roadwarrior /kernel: Preloaded elf module "splash_bmp.ko" at 0xc03bf09c. roadwarrior /kernel: Preloaded elf module "vesa.ko" at 0xc03bf140. roadwarrior /kernel: Preloaded splash_image_data "/boot/splash.bmp" at 0xc03bf1dc. roadwarrior /kernel: Preloaded elf module "cd9660.ko" at 0xc03bf22c. roadwarrior /kernel: Preloaded elf module "linux.ko" at 0xc03bf2cc. roadwarrior /kernel: Preloaded elf module "atapi.ko" at 0xc03bf36c. roadwarrior /kernel: link_elf: symbol atapi_drvtab undefined roadwarrior /kernel: Intel Pentium detected, installing workaround for F00F bug roadwarrior /kernel: VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c7a88 (c0007a88) roadwarrior /kernel: VESA: Copyright 1994 TRIDENT MICROSYSTEMS INC. roadwarrior /kernel: roadwarrior /kernel: apm0: on motherboard roadwarrior /kernel: apm: found APM BIOS v1.2, connected at v1.2 roadwarrior /kernel: npx0: on motherboard roadwarrior /kernel: npx0: INT 16 interface roadwarrior /kernel: pcib0: on motherboard roadwarrior /kernel: pci0: on pcib0 roadwarrior /kernel: isab0: at device 1.0 on pci0 roadwarrior /kernel: isa0: on isab0 roadwarrior /kernel: ide_pci0: at device 1.1 on pci0 roadwarrior /kernel: uhci0: irq 0 at device 1.2 on pci0 roadwarrior /kernel: uhci0: could not map ports roadwarrior /kernel: device_probe_and_attach: uhci0 attach returned 6 roadwarrior /kernel: chip1: at device 1.3 on pci0 roadwarrior /kernel: vga-pci0: at device 2.0 on pci0 roadwarrior /kernel: pcic-pci0: irq 10 at device 3.0 on pci0 roadwarrior /kernel: pcic-pci1: irq 10 at device 3.1 on pci0 roadwarrior /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 roadwarrior /kernel: fdc0: FIFO enabled, 8 bytes threshold roadwarrior /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 roadwarrior /kernel: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 roadwarrior /kernel: wdc0: unit 0 (wd0): roadwarrior /kernel: wd0: 3909MB (8007552 sectors), 7944 cyls, 16 heads, 63 S/T, 512 B/S roadwarrior /kernel: wdc1 at port 0x170-0x177 irq 15 on isa0 roadwarrior /kernel: wdc1: unit 0 (atapi): , removable, accel, dma, iordy roadwarrior /kernel: wcd0: drive speed 2416KB/sec, 128KB cache roadwarrior /kernel: wcd0: supported read types: CD-DA roadwarrior /kernel: wcd0: Audio: play, 16 volume levels roadwarrior /kernel: wcd0: Mechanism: ejectable tray roadwarrior /kernel: wcd0: Medium: no/blank disc inside, unlocked roadwarrior /kernel: atkbdc0: at port 0x60-0x6f on isa0 roadwarrior /kernel: atkbd0: irq 1 on atkbdc0 roadwarrior /kernel: psm0: irq 12 on atkbdc0 roadwarrior /kernel: psm0: model Generic PS/2 mouse, device ID 0 roadwarrior /kernel: vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 roadwarrior /kernel: sc0: on isa0 roadwarrior /kernel: sc0: VGA <16 virtual consoles, flags=0x200> roadwarrior /kernel: pcic0: at irq 10 on isa0 roadwarrior /kernel: pccard0: on pcic0 roadwarrior /kernel: pccard1: on pcic0 roadwarrior /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 roadwarrior /kernel: sio0: type 16550A roadwarrior /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 roadwarrior /kernel: sio2: not probed (disabled) roadwarrior /kernel: sio3: not probed (disabled) roadwarrior /kernel: ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 roadwarrior /kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode roadwarrior /kernel: plip0: on ppbus 0 roadwarrior /kernel: lpt0: on ppbus 0 roadwarrior /kernel: lpt0: Interrupt-driven port roadwarrior /kernel: ppi0: on ppbus 0 roadwarrior /kernel: unknown0: at port 0x800-0x807 on isa0 roadwarrior /kernel: pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 roadwarrior /kernel: unknown1: at port 0x201 on isa0 roadwarrior /kernel: Mounting root from ufs:/dev/wd0s1a roadwarrior /kernel: pccard: card inserted, slot 0 roadwarrior pccardd[62]: Using I/O addr 0x240, size 32 roadwarrior pccardd[62]: Setting config reg at offs 0x10000 to 0x41, Reset time = 50 ms roadwarrior lpd[144]: restarted roadwarrior pccardd[62]: Assigning I/O window 0, start 0x240, size 0x20 flags 0x7 roadwarrior pccardd[62]: Assign ep0, io 0x240-0x25f, mem 0x0, 0 bytes, irq 3, flags 0 roadwarrior /kernel: ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at port 0x240-0x25f irq 3 slot 0 on pccard0 roadwarrior /kernel: ep0: Ethernet address 4b:57:4b:57:4b:57 roadwarrior pccardd[62]: pccardd started roadwarrior /kernel: roadwarrior /kernel: roadwarrior /kernel: Fatal trap 12: page fault while in kernel mode roadwarrior /kernel: fault virtual address = 0x0 roadwarrior /kernel: fault code = supervisor read, page not present roadwarrior /kernel: instruction pointer = 0x8:0x0 roadwarrior /kernel: stack pointer = 0x10:0xc7523de4 roadwarrior /kernel: frame pointer = 0x10:0xc7523e08 roadwarrior /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b roadwarrior /kernel: = DPL 0, pres 1, def32 1, gran 1 roadwarrior /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 roadwarrior /kernel: current process = 310 (ifconfig) roadwarrior /kernel: interrupt mask = net tty roadwarrior /kernel: trap number = 12 roadwarrior /kernel: panic: page fault roadwarrior /kernel: roadwarrior /kernel: syncing disks... 24 24 20 12 done roadwarrior /kernel: Automatic reboot in 15 seconds - press a key on the console to abort and again at a different location.. (same kernel.) roadwarrior /kernel: Mounting root from ufs:/dev/wd0s1a roadwarrior /kernel: pccard: card inserted, slot 0 roadwarrior pccardd[60]: Using I/O addr 0x240, size 32 roadwarrior pccardd[60]: Setting config reg at offs 0x10000 to 0x41, Reset time = 50 ms roadwarrior lpd[144]: restarted roadwarrior pccardd[60]: Assigning I/O window 0, start 0x240, size 0x20 flags 0x7 roadwarrior pccardd[60]: Assign ep0, io 0x240-0x25f, mem 0x0, 0 bytes, irq 3, flags 0 roadwarrior /kernel: ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at port 0x240-0x25f irq 3 slot 0 on pccard0 roadwarrior /kernel: ep0: Ethernet address 4b:57:4b:57:4b:57 roadwarrior pccardd[60]: pccardd started roadwarrior /kernel: roadwarrior /kernel: roadwarrior /kernel: Fatal trap 12: page fault while in kernel mode roadwarrior /kernel: fault virtual address = 0x0 roadwarrior /kernel: fault code = supervisor read, page not present roadwarrior /kernel: instruction pointer = 0x8:0x0 roadwarrior /kernel: stack pointer = 0x10:0xc74edde4 roadwarrior /kernel: frame pointer = 0x10:0xc74ede08 roadwarrior /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b roadwarrior /kernel: = DPL 0, pres 1, def32 1, gran 1 roadwarrior /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 roadwarrior /kernel: current process = 312 (ifconfig) roadwarrior /kernel: interrupt mask = net tty roadwarrior /kernel: trap number = 12 roadwarrior /kernel: panic: page fault roadwarrior /kernel: roadwarrior /kernel: syncing disks... 7 7 3 done roadwarrior /kernel: Automatic reboot in 15 seconds - press a key on the console to abort I'm rebuilding modules again as i type this, and we'll see what develops.. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 23:20:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CB63F15894 for ; Thu, 4 Nov 1999 23:20:24 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA54980; Fri, 5 Nov 1999 08:19:07 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911050719.IAA54980@freebsd.dk> Subject: Re: vga driver and signal In-Reply-To: <199911050254.SAA50665@rah.star-gate.com> from Amancio Hasty at "Nov 4, 1999 06:54:11 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Nov 1999 08:19:07 +0100 (CET) Cc: doconnor@gsoft.com.au (Daniel O'Connor), current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), mike@smith.net.au (Mike Smith) 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 Amancio Hasty wrote: > > Just trying to prevent dragging the whole X server to the kernel -- > Actually dragging the whole X server to the kernel is not a bad > idea --- however it is something that I can not afford to do right now :( Ahh, horror, Terry's old idea is coming back again :) Seriously, you need (at least) all the code that deals with the videoHW on the interrupt in the kernel, there is no way to get this to userland reliably and without significant delay. This will drag in most off the ddx layer I'm afraid, so its really not practical. Lets step back for a moment, this is clearly the wrong solution to everything, what exactly is it you want to do or want to accomplish?? Lets see if we can come up with another way of doing that... -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 Nov 4 23:20:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from neptune.psn.net (neptune.psn.net [207.211.58.16]) by hub.freebsd.org (Postfix) with ESMTP id 9BF46158A2; Thu, 4 Nov 1999 23:20:22 -0800 (PST) (envelope-from andrews@technologist.com) Received: from 5042-243.008.popsite.net ([209.224.140.243] helo=argon) by neptune.psn.net with smtp (PSN Internet Service 2.12 #3) id 11jdef-0003JL-00; Fri, 5 Nov 1999 00:19:26 -0700 Message-Id: <3.0.6.32.19991105021908.008c1de0@mail.psn.net> X-Sender: andrews@mail.psn.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 05 Nov 1999 02:19:08 -0500 To: Bob Vaughan From: Will Andrews Subject: Re: boot problems with todays kernel Cc: current@FreeBSD.ORG, mdodd@FreeBSD.ORG, imp@FreeBSD.ORG In-Reply-To: <199911050644.WAA40360@tantivy.stanford.edu> References: <3.0.6.32.19991104222248.008b3e10@mail.psn.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ CC:'d to mdodd, imp as it relates to their current work ] At 10:44 PM 11/4/99 -0800, you wrote: >I'm now running into issues with pccard and the ep driver, where ep0 (3c574B) >is seen at boot time, at a familiar port/irq, but with a bogus mac address.. >(4b:57:4b:57:4b:57). ifconfig -a will immediately lock up the system, with a >reboot following a minute or two later.. >this only happens when there is a card inserted.. I have EXACTLY the same problems! Exactly the same PC-Card, exactly the same MAC address problem.. I even get that exact same MAC address - 4b:57:4b:57:4b:57! I've been looking over Matt Dodd's commit (-r1.91) to if_ep.c, and I think I may have figured out this problem. I'll need to do some testing first to see. I'll send a patch on Saturday if/when my fixes get the MAC address right. I suspect that if the fix gets the MAC address right, connectivity / kernel stability with if_ep will return. > roadwarrior /kernel: pcic0: at irq 10 on isa0 > roadwarrior /kernel: pccard0: on pcic0 > roadwarrior /kernel: pccard1: on pcic0 I believe I have the same PCIC controller. > roadwarrior /kernel: pccard: card inserted, slot 0 > roadwarrior pccardd[62]: Using I/O addr 0x240, size 32 > roadwarrior pccardd[62]: Setting config reg at offs 0x10000 to 0x41, Reset time = 50 ms > roadwarrior lpd[144]: restarted > roadwarrior pccardd[62]: Assigning I/O window 0, start 0x240, size 0x20 flags 0x7 > roadwarrior pccardd[62]: Assign ep0, io 0x240-0x25f, mem 0x0, 0 bytes, irq 3, flags 0 > roadwarrior /kernel: ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at port 0x240-0x25f irq 3 slot 0 on pccard0 > roadwarrior /kernel: ep0: Ethernet address 4b:57:4b:57:4b:57 Hmm.. ep0 on IRQ 3? It should be on IRQ 10. At least, that's what has always worked for me on previous -CURRENT code. Otherwise I get the same last 2 messages. I note though that your PCIC is using IRQ 10. Normally, mine would use IRQ 11, and ep0 would use IRQ 10. > roadwarrior /kernel: Fatal trap 12: page fault while in kernel mode > roadwarrior /kernel: fault virtual address = 0x0 > roadwarrior /kernel: fault code = supervisor read, page not present > roadwarrior /kernel: instruction pointer = 0x8:0x0 > roadwarrior /kernel: stack pointer = 0x10:0xc7523de4 > roadwarrior /kernel: frame pointer = 0x10:0xc7523e08 > roadwarrior /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b > roadwarrior /kernel: = DPL 0, pres 1, def32 1, gran 1 > roadwarrior /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 > roadwarrior /kernel: current process = 310 (ifconfig) > roadwarrior /kernel: interrupt mask = net tty > roadwarrior /kernel: trap number = 12 > roadwarrior /kernel: panic: page fault > roadwarrior /kernel: > roadwarrior /kernel: syncing disks... 24 24 20 12 done > roadwarrior /kernel: Automatic reboot in 15 seconds - press a key on the console to abort Yep - this happens to me when i do a `ifconfig ep0`. Ka-boom. >roadwarrior /kernel: Mounting root from ufs:/dev/wd0s1a >roadwarrior /kernel: pccard: card inserted, slot 0 >roadwarrior pccardd[60]: Using I/O addr 0x240, size 32 >roadwarrior pccardd[60]: Setting config reg at offs 0x10000 to 0x41, Reset time = 50 ms >roadwarrior lpd[144]: restarted >roadwarrior pccardd[60]: Assigning I/O window 0, start 0x240, size 0x20 flags 0x7 >roadwarrior pccardd[60]: Assign ep0, io 0x240-0x25f, mem 0x0, 0 bytes, irq 3, flags 0 Again, I don't like that IRQ. I'll get back to y'all on the MAC address issue. Good night. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 23:35:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 3B64E14D23 for ; Thu, 4 Nov 1999 23:35:22 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id BAA95943; Fri, 5 Nov 1999 01:34:15 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199911050734.BAA95943@celery.dragondata.com> Subject: Re: vga driver and signal To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Nov 1999 01:34:15 -0600 (CST) Cc: doconnor@gsoft.com.au (Daniel O'Connor), current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), mike@smith.net.au (Mike Smith) In-Reply-To: <199911050254.SAA50665@rah.star-gate.com> from "Amancio Hasty" at Nov 04, 1999 06:54:11 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Kind of complex though. Also the interrupt latency problem is still there. > > Not sure that this is as elegant as what you are suggesting , can > the kernel schedule a user level routine to be executed when an interrupt > occurs? I guess on Windoze land this is called a driver call-back. > > In a project I'm working on now (that some of you saw at FreeBSDCon) I had a need to sync a lot of things to a vsync interrupt. I ended up writing a small driver to attach to the video card. My program would do a blocking read on the device, which would put that process to sleep. The interrupt handler would shove one byte of data back to the process through the read (indicating interrupt status) and wake up the process. This works, but still has a problem if latency and missed interrupts if you aren't reading when the interrupt happens. (I've worked around those too, but that's quite a bit more involved to fix it). You'll probably need to end up changing the scheduler slightly, or playing with rtprio. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 23:42:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id AB9D514D23 for ; Thu, 4 Nov 1999 23:42:39 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id SAA02118; Fri, 5 Nov 1999 18:10:10 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199911050734.BAA95943@celery.dragondata.com> Date: Fri, 05 Nov 1999 18:10:09 +1030 (CST) From: "Daniel O'Connor" To: Kevin Day Subject: Re: vga driver and signal Cc: (Mike Smith) Cc: (Mike Smith) , (Kazutaka YOKOTA) , current@FreeBSD.ORG, (Amancio Hasty) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Nov-99 Kevin Day wrote: > This works, but still has a problem if latency and missed interrupts if you > aren't reading when the interrupt happens. (I've worked around those too, > but that's quite a bit more involved to fix it). You'll probably need to end > up changing the scheduler slightly, or playing with rtprio. So what sort of latency do you achieve? What do you mean by 'more involved'? :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 4 23:46: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 5540E15868 for ; Thu, 4 Nov 1999 23:46:01 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id XAA52807; Thu, 4 Nov 1999 23:44:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050744.XAA52807@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: doconnor@gsoft.com.au (Daniel O'Connor), current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), mike@smith.net.au (Mike Smith) Subject: Re: vga driver and signal In-reply-to: Your message of "Fri, 05 Nov 1999 08:19:07 +0100." <199911050719.IAA54980@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 04 Nov 1999 23:44:51 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Amancio Hasty wrote: > > = > > Just trying to prevent dragging the whole X server to the kernel -- > > Actually dragging the whole X server to the kernel is not a bad > > idea --- however it is something that I can not afford to do right no= w :( > = > Ahh, horror, Terry's old idea is coming back again :) Actually is my old idea not Terry's. > Seriously, you need (at least) all the code that deals with the videoHW= > on the interrupt in the kernel, there is no way to get this to userland= > reliably and without significant delay. This will drag in most off the > ddx layer I'm afraid, so its really not practical. > = > Lets step back for a moment, this is clearly the wrong solution to > everything, what exactly is it you want to do or want to accomplish?? > Lets see if we can come up with another way of doing that... Okay, The problem that the XFree86 group is trying to solve is that when a user moves an opaque window it gets little tearings = along the edges because the repaint of the window came in in the middle of a vertical retrace also moving the window is not that smooth. Apparently, the Accel-x folks have solved this problem because according to some their X server does not have any problems in moving opaque windows. As Kevin Day, just posted this problem has other applications for instance dedicated video players . One solution that the XFree86 folks are trying is to sync up = the mouse interrupts to the refresh rate. = Mark Vojkovich has reported good success with this approach however the problem is that we can not arbritraly set the mouse interrupt rate like we can = with a vga card. Actually, what we need is a dialogue between the XFree86 group and this group . For now , I can serve as the bridge and it gets too involved then we will have to cross-post between the = two groups. -- = Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 0: 9:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 88A5E15875 for ; Fri, 5 Nov 1999 00:09:15 -0800 (PST) (envelope-from devet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id JAA12462; Fri, 5 Nov 1999 09:06:50 +0100 (MET) Received: (from devet@localhost) by adv.iae.nl (8.9.3/8.8.6) id JAA74999; Fri, 5 Nov 1999 09:00:00 +0100 (CET) Date: Fri, 5 Nov 1999 09:00:00 +0100 (CET) From: Arjan de Vet Message-Id: <199911050800.JAA74999@adv.iae.nl> To: davec@unforgettable.com Subject: Re: IPFilter in -current? X-Newsgroups: list.freebsd.current In-Reply-To: <991104221452CC.26561@weba7.iname.net> Organization: Internet Access Eindhoven, the Netherlands Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <991104221452CC.26561@weba7.iname.net> you write: >Hello, I'm curious as to the current status of IP Filter in the -current >branch of FreeBSD. Since its removal from the kernel in October, there >have been a few emails about getting/wanting it back. May I ask who is >currently working on that and what sort of progress they are making? >Thank you. Guido van Rooij (guido@freebsd.org) is working on it and he recently showed me ipfilter 3.2.2 (I think) working as a loadable module for FreeBSD-current. As soon as it's fully tested he'll commit it. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 0:19:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 82341156D7 for ; Fri, 5 Nov 1999 00:19:40 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA70396; Fri, 5 Nov 1999 09:19:29 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911050819.JAA70396@freebsd.dk> Subject: Re: vga driver and signal In-Reply-To: <199911050744.XAA52807@rah.star-gate.com> from Amancio Hasty at "Nov 4, 1999 11:44:51 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Nov 1999 09:19:29 +0100 (CET) Cc: doconnor@gsoft.com.au (Daniel O'Connor), current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), mike@smith.net.au (Mike Smith) 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 Amancio Hasty wrote: > > Lets step back for a moment, this is clearly the wrong solution to > > everything, what exactly is it you want to do or want to accomplish?? > > Lets see if we can come up with another way of doing that... > > Okay, > > The problem that the XFree86 group is trying to solve is that > when a user moves an opaque window it gets little tearings > along the edges because the repaint of the window came in > in the middle of a vertical retrace also moving the window > is not that smooth. Apparently, the Accel-x folks have solved > this problem because according to some their X server > does not have any problems in moving opaque windows. > As Kevin Day, just posted this problem has other applications > for instance dedicated video players . Hmm, there will always be problems here I'd say, there is no way you can copy an entire window in just one blank period. BTW I dont see any problems here with my ATI cards, movement is nice an smooth, no visible artifacts, but it might just be because my HW is sufficiently fast for the task. I'm not sure I've seen this problem since the old 486/ET4000 days where updates where painfully slow given todays standards. Is this problem seen on lots of HW, or is it just to cope with some specific boards ?? One possible solution could be to copy the changes to some off screen location in the video memory, then have the card do the copy when the blank period starts, that way we only need a little KLD that can do the copy on a given card. For other cards it might be from memory to the card, but crossing the usr/kernel barrier will be a problem to solve (latency & | speed wise). You will need a different KLD for every card you support (or one huge one). The problem is that it is probably not possible to copy the entire window in one blank period, so it will have to be able to break up those requests, and shedule them over a number of blank periods, that again will make it painfully slow, and probably look much worse than the current approach. > One solution that the XFree86 folks are trying is to sync up > the mouse interrupts to the refresh rate. > Mark Vojkovich has reported > good success with this approach however the problem is that > we can not arbritraly set the mouse interrupt rate like we can > with a vga card. Hmm I dont think this will fly, there are too many unknown latensies and delays in this senario for it to be functional on any resonable set of hardware options. Is all this just because some of the new video HW are crappy, ie that they produce snow/flicker/whatever (like in the old CGA days) or is this a genuine problem, as I said above I've never seen any problems on my ATI cards, and my laptop doesn't have this either (neomagic).. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 1:24:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6447515280 for ; Fri, 5 Nov 1999 01:24:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA19465 for ; Fri, 5 Nov 1999 01:24:50 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA74280 for current@freebsd.org; Fri, 5 Nov 1999 01:24:50 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Nov 1999 01:24:50 -0800 From: "David O'Brien" To: current@freebsd.org Subject: GCC 2.95.2 testing Message-ID: <19991105012449.A74246@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've got GCC 2.95.2 working as the base compiler. It is still a little rough, but I wanted to put it in more hands for testing. My Alpha is booting from a GENERIC kernel and world built from gcc 2.95.2. This is one compiler bug in building libreadline, but I have a hack around it. The i386 doesn't fair as well. GENERIC can only be compiled if `ahc0' is removed. This is a call to IA-32 ASM experts to find a fix. I have made two sets of files available: ftp://relay.nuxi.com/pub/FreeBSD/gcc2952-991004.tar.gz ftp://relay.nuxi.com/pub/FreeBSD/gcc2952-991004-sidelines.tar.gz To use ether fetch them and then cd into your version of `/usr/src' and then untar them. `gcc2952-991004' will overwrite your current src/gnu/usr.bin/cc/ and src/gnu/lib/ contents. Using this dist, you can do a full `make world' and wind up with gcc 2.95.2 as your base compiler and the world built with it. `gcc2952-991004-sidelines' will not overwrite any of your existing files. To build it simply: cd /usr/src/gnu/usr.bin/cc.gcc2952 make obj make depend all install cd /usr/src/gnu/lib make -f Makefile.gcc2952 obj make -f Makefile.gcc2952 depend all install Note that this will replace your existing compiler with gcc 2.95.2. So YOU MIGHT WANT TO BACKUP YOUR EXISTING EGCS 1.1.2 COMPILER. The files you'll want to back up are /usr/bin/{cc,c++} /usr/libexec/{cpp,cc1*,f771} /usr/lib/libg2c* /usr/lib/libgcc* /usr/lib/libstdc++.* /usr/lib/libobjc.* /usr/include/g++ There is one casualty of the gcc 2.95.2 compiler -- Objective-C support is currently broken. Enjoy! -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 1:38:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1C1A714EA4 for ; Fri, 5 Nov 1999 01:38:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id BAA53523; Fri, 5 Nov 1999 01:37:27 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911050937.BAA53523@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: doconnor@gsoft.com.au (Daniel O'Connor), current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), mike@smith.net.au (Mike Smith) Subject: Re: vga driver and signal In-reply-to: Your message of "Fri, 05 Nov 1999 09:19:29 +0100." <199911050819.JAA70396@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 05 Nov 1999 01:37:27 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is all this just because some of the new video HW are crappy, ie that > they produce snow/flicker/whatever (like in the old CGA days) or is > this a genuine problem, as I said above I've never seen any problems > on my ATI cards, and my laptop doesn't have this either (neomagic).. > = Yes, this is a problem if you try to do a blit in the middle of a vertica= l retrace you will get a small artifact for instance as you move your windo= w you will see have a line or more half drawn and when you stop moving the window the blit completes. What determines the lacking retrace is the delta time of the mouse movement. = -- = Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 2: 0:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id B0F0D1588F for ; Fri, 5 Nov 1999 02:00:22 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1475 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Fri, 5 Nov 1999 10:58:06 +0100 (CET) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id D429C38D6; Fri, 5 Nov 1999 10:58:04 +0100 (MET) Subject: Re: IPFilter in -current? In-Reply-To: <199911050800.JAA74999@adv.iae.nl> from Arjan de Vet at "Nov 5, 99 09:00:00 am" To: Arjan.deVet@adv.iae.nl (Arjan de Vet) Date: Fri, 5 Nov 1999 10:58:04 +0100 (MET) Cc: davec@unforgettable.com, current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 588 Message-Id: <19991105095804.D429C38D6@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Arjan de Vet: > Guido van Rooij (guido@freebsd.org) is working on it and he recently > showed me ipfilter 3.2.2 (I think) working as a loadable module for > FreeBSD-current. As soon as it's fully tested he'll commit it. This is very good news! hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 2:26: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 2424014C1F for ; Fri, 5 Nov 1999 02:25:58 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA39579 for current@FreeBSD.org; Fri, 5 Nov 1999 11:00:06 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Fri, 05 Nov 1999 11:00:04 +0100 From: Marcel Moolenaar Message-ID: <3822AAA4.F65E094B@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <19991105012449.A74246@dragon.nuxi.com> Subject: Re: GCC 2.95.2 testing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > I've got GCC 2.95.2 working as the base compiler. It is still a little > rough, but I wanted to put it in more hands for testing. If it doesn't interfere with my current work, then I'll get to it ASAP. I already have some fixes for the current binutils and egcs WRT to cross-compilation that I like to test on GCC 2.95.2, because building an Alpha world on i386 triggers a bug in egcs. If gcc 2.95.2 doesn't have that bug, then I for one don't have to chase it :-) > The i386 doesn't fair as well. GENERIC can only be compiled if `ahc0' is > removed. This is a call to IA-32 ASM experts to find a fix. Ok, thanks. It should trigger on my system then... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Nov 5 8:59:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B90411522B for ; Fri, 5 Nov 1999 08:59:16 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id LAA07200; Fri, 5 Nov 1999 11:54:25 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 5 Nov 1999 11:54:24 -0500 (EST) From: Chuck Robey To: peter.jeremy@alcatel.com.au Cc: nnd@mail.nsk.ru, freebsd-current@FreeBSD.ORG Subject: Re: CTM-deltas generation sptopped ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Nov 1999, Chuck Robey wrote: > On Thu, 4 Nov 1999, Peter Jeremy wrote: > > > On 1999-Nov-03 23:58:00 +1100, nnd@mail.nsk.ru wrote: > > > There are no new CTM-deltas on 'ctm.freebsd.org' > > >at least 22 hours. > > > > The last e-mail delta I have is cvs-cur.5804, which arrived here at > > 0808UTC (about 5 hours before your message). I would have expected to > > receive 5805 (or at least an initial part) about 5 hours ago now, so I > > suspect something is wrong. > > I stopped reading the list for a few days (letting my mail pile up) while > I handled a panic situation at the University, sorry. I can't traceroute > or ping the source of ctm's, and I have mail out to the owner of the > system. > > Now that I'm aware, I will follow this as fast as I can. Replying to my own mail, I want to give an update: the machine that generates ctm has crashed, and the vinum volume doesn't fsck cleanly on startup. It's not a disaster, this can all be fixed, nothing critical *could* have been lost, because I've copies of everything critical right here. The likelihood, tho, is that it'll be a couple days at least until ctm comes back up, because I think I'm going to have to recreate it. Be patient, I'll announce when it gets back up. Oh, yeah, anoncvs is down too, same reasons, same response. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 11:47:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 33CF714C91 for ; Fri, 5 Nov 1999 11:47:52 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA16813 for ; Fri, 5 Nov 1999 11:47:23 -0800 (PST) Date: Fri, 5 Nov 1999 11:47:22 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: OOps broke make world.. 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 broken 'make world' because I forgot theat netstat has promiscuous fingers in places it shouldn't 'QUICK FIX:' copy old /usr/src/sys/netgraph/ng_socketvar.h from before I deleted it. then netstat should recompile.. I will fix it as soon as I get to my source tree. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 13:16:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from spiral.inspiral.net (spiral.inspiral.net [194.204.49.249]) by hub.freebsd.org (Postfix) with ESMTP id 228F614D64 for ; Fri, 5 Nov 1999 13:16:00 -0800 (PST) (envelope-from mauri@spiral.inspiral.net) Received: from localhost (mauri@localhost) by spiral.inspiral.net (8.9.3/8.9.3) with ESMTP id XAA86526 for ; Fri, 5 Nov 1999 23:13:46 +0200 (EET) (envelope-from mauri@spiral.inspiral.net) Date: Fri, 5 Nov 1999 23:13:46 +0200 (EET) From: Lauri Laupmaa To: current@freebsd.org Subject: stuck with ~year old current 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 I have -CURRENT from 16 nov 1998 and stuck badly... If I make new kernel, loader says its format's unknown, if I try to make new loader, it says some gcc flag is unknown, if I try to make new gcc it barfs also... From where should I start ? TIA _____ Lauri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 13:48:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 3589214C8F for ; Fri, 5 Nov 1999 13:48:16 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id NAA58130 for ; Fri, 5 Nov 1999 13:46:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911052146.NAA58130@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: more on vga vsync Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Nov 1999 13:46:44 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 04 Nov 1999 14:35:58 -0800, Amancio Hasty wrote: > >This show > up on the FreeBSD mailing list when I ask about modifying vga.c >to > deliver a signal. > >> Let me ask a different question: How does > Microsoft's DirectX handle >> delivery of vertical retrace interrupt? > The vertical retrace interrupt is not exposed to applications in the > DirectX model -- it's all internal to the DirectX provider. The > DirectX blit and flip- surface (for double buffering) calls both have > an option to request that the operation be delayed until the end of > this frame. This is implemented in one three ways: > - if the chip has a hardware blit option to delay until VSYNC, this > is pretty easy, and you don't need the interrupt; > - if the chip has a VSYNC interrupt, the driver has to hook the > interrupt > and process the operation at interrupt time; > - otherwise, the chip is permitted to do a delayed callback; the > operation > does not have to OCCUR within VBLANK, it just has to delay until > after > the current frame ends. > However, all of this is strictly for DirectX. GDI and the GDI driver > interface know nothing about vertical retrace, since the interface > has to work for printers and plotters as well as displays. Move > window operations use GDI, and thus are not synchronized with > vertical retrace in any way. In our case the X server is somewhat the DirectX provider. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 13:54: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id A212814EB2 for ; Fri, 5 Nov 1999 13:54:05 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FKQ00IE0VGKYR@mta4.rcsntx.swbell.net> for current@FreeBSD.ORG; Fri, 5 Nov 1999 15:53:09 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id PAA23113; Fri, 05 Nov 1999 15:53:45 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Fri, 05 Nov 1999 15:53:44 -0600 From: Chris Costello Subject: Re: stuck with ~year old current In-reply-to: To: Lauri Laupmaa Cc: current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991105155344.Z602@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 05, 1999, Lauri Laupmaa wrote: > Hi > > I have -CURRENT from 16 nov 1998 and stuck badly... > If I make new kernel, loader says its format's unknown, if I try to make > new loader, it says some gcc flag is unknown, if I try to make new gcc it > barfs also... > > >From where should I start ? Read all of the -current mailing list starting in 17 November 1998 all the way up to today, and then read /usr/src/UPDATING. -- |Chris Costello |MOP AND GLOW - Floor wax used by Three Mile Island cleanup team. `---------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 14: 1:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1D1B314EB2 for ; Fri, 5 Nov 1999 14:01:25 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id XAA12055 for freebsd-current@FreeBSD.ORG; Fri, 5 Nov 1999 23:01:08 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 65E198711; Fri, 5 Nov 1999 22:59:16 +0100 (CET) Date: Fri, 5 Nov 1999 22:59:16 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Serious locking problem in CURRENT Message-ID: <19991105225916.A14961@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While changing my Postfix configuration, I stumbled on something weird. One of Postfix's processes (master) runs all the time and keep a exclusive write lock on $spool/pid/master.pid. When one does a reload, postfix-script runs master with the ``-t'' argument which makes master try to get a lock on the pid file. Under 3.3-RELEASE, everything is fine, the lock can't be obtained and Postfix knows it is already running. Under -CURRENT (two days old), the lock IS OBTAINED, meaning Postfix thinks it is not running. 3.3-RELEASE: OK -=-=-=- 402 [22:56] root@sidhe:/etc/postfix# make postfix reload postfix-script: refreshing the Postfix mail system 404 [22:56] root@sidhe:spool/postfix# kdump|tail -20 8359 master RET getrlimit 0 8359 master CALL chdir(0x8057b28) 8359 master NAMI "/var/spool/postfix" 8359 master RET chdir 0 8359 master CALL access(0x805c3e8,0) 8359 master NAMI "pid/master.pid" 8359 master RET access 0 8359 master CALL open(0x805c3e8,0x2,0) 8359 master NAMI "pid/master.pid" 8359 master RET open 7 8359 master CALL fstat(0x7,0xbfbfd300) 8359 master RET fstat 0 8359 master CALL lstat(0x805c3e8,0xbfbfd2a0) 8359 master NAMI "pid/master.pid" 8359 master RET lstat 0 8359 master CALL flock(0x7,0x6) 8359 master RET flock -1 errno 35 Resource temporarily unavailable 8359 master CALL close(0x7) 8359 master RET close 0 8359 master CALL exit(0x1) -=-=-=- 4.0-CURRENT: NOT OK -=-=-=- 331 [22:55] root@keltia:spool/postfix# postfix reload postfix-script: fatal: the Postfix mail system is not running 332 [22:56] root@keltia:spool/postfix# kdump|tail -20 14942 master RET gettimeofday 0 14942 master CALL getrlimit(0x1,0xbfbfd3d0) 14942 master RET getrlimit 0 14942 master CALL chdir(0x80589e8) 14942 master NAMI "/var/spool/postfix" 14942 master RET chdir 0 14942 master CALL access(0x805e248,0) 14942 master NAMI "pid/master.pid" 14942 master RET access 0 14942 master CALL open(0x805e248,0x2,0) 14942 master NAMI "pid/master.pid" 14942 master RET open 7 14942 master CALL fstat(0x7,0xbfbfd324) 14942 master RET fstat 0 14942 master CALL lstat(0x805e248,0xbfbfd2c4) 14942 master NAMI "pid/master.pid" 14942 master RET lstat 0 14942 master CALL flock(0x7,0x6) <<<<<<<< ????? 14942 master RET flock 0 <<<<<<<< ????? 14942 master CALL exit(0) -=-=-=- I've verified that it has a lock on 3.3-RELEASE but can't on CURRENT since lsof is broken (sigh). 3.3-RELEASE: 405 [22:56] root@sidhe:spool/postfix# lsof pid/master.pid COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 7155 root 7uW VREG 0,131079 17 18615 pid/master.pid ^^^ Same Postfix versions on both. I even recompiled it on CURRENT. 406 [22:58] root@sidhe:spool/postfix# postconf mail_version mail_version = Snapshot-19990912 333 [22:56] root@keltia:spool/postfix# postconf mail_version mail_version = Snapshot-19990912 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 14: 5:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BAF2914E23 for ; Fri, 5 Nov 1999 14:05:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA24763 for ; Fri, 5 Nov 1999 14:04:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA25543 for current@freebsd.org; Fri, 5 Nov 1999 14:04:15 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Nov 1999 14:04:15 -0800 From: "David O'Brien" To: current@freebsd.org Subject: show stopper for Gcc 2.95.2 conversion Message-ID: <19991105140415.A25486@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19991105012449.A74246@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991105012449.A74246@dragon.nuxi.com>; from obrien@NUXI.com on Fri, Nov 05, 1999 at 01:24:50AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The current show stopper for switching over to GCC 2.95.2 is a problem compiling the `ahc' driver: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../dev/aic7xxx/aic7xxx.c ../../dev/aic7xxx/aic7xxx.c: In function `ahc_download_instr': machine/bus.h:584: Invalid `asm' statement: machine/bus.h:584: fixed or forbidden register 2 (cx) was spilled for class CREG. *** Error code 1 The message is misleading, as the problematic header is /sys/i386/include/bus.h not, /usr/include/machine/bus.h. -- -- 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 Nov 5 14:17: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 18C4B15352 for ; Fri, 5 Nov 1999 14:16:49 -0800 (PST) (envelope-from taavi@uninet.ee) Received: by ns.uninet.ee (Postfix, from userid 1001) id 8A50C25AA9; Sat, 6 Nov 1999 00:16:43 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by ns.uninet.ee (Postfix) with SMTP id 842FA14A1A; Sat, 6 Nov 1999 00:16:43 +0200 (EET) Date: Sat, 6 Nov 1999 00:16:43 +0200 (EET) From: Taavi Talvik To: Chris Costello Cc: Lauri Laupmaa , current@FreeBSD.ORG Subject: Re: stuck with ~year old current In-Reply-To: <19991105155344.Z602@holly.calldei.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, 5 Nov 1999, Chris Costello wrote: > > I have -CURRENT from 16 nov 1998 and stuck badly... ... > Read all of the -current mailing list starting in 17 November > 1998 all the way up to today, and then read /usr/src/UPDATING. No, it does not work. Currently it is impossible to upgrade from 3.1 to todays current without having bootblocks and loader compiled/taken from some other todays current system. Issues from top of head gcc!=egcc - bootblocks and loader cannot be compilied. Loader v0.6 cannot load current kernel. Only alternative to get these from outside is to upgrade graduall.. but who knows which intermediate source repository dates are good for it? best regard, taavi ----------------------------------------------------------- Taavi Talvik | Internet: taavi@uninet.ee Unineti Andmeside AS | phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 14:19:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 037AA14F54 for ; Fri, 5 Nov 1999 14:19:37 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id XAA89907 for ; Fri, 5 Nov 1999 23:18:29 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9C36C4.dip.t-dialin.net [62.156.54.196]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id XAA89893 for ; Fri, 5 Nov 1999 23:18:26 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id WAA51715 for ; Fri, 5 Nov 1999 22:53:21 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <382351D1.F79539A1@dead-end.net> Date: Fri, 05 Nov 1999 22:53:21 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: ESS 1868 driver, again Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I read the last mails regarding problems with their ESS 1868 boards. Well, at least it is partially working for them. I didn't have any luck with the driver for some time now. I couldn't get a single tone. With the old voxware driver, sound worked at least partially (44.1 kHz, 8 Bit, mono), but with the new driver I didn't have any luck at all. Here my configuration: device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 and during boot: pcm0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 If I try to play something, I only get the following error from the driver: sb_dspwr(0xc0) timed out. The old voxware driver: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? port 0x220 irq 5 drq 5 conflicts device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 device mpu0 at isa? port 0x330 sb0 at port 0x220 irq 5 drq 1 on isa0 Hmm... Could this be an ESS688 based card (rev 11) snd0: isa_compat: didn't get ports for sbxvi sbxvi0 at port 0x220 irq 5 drq 5 on isa0 isa_compat: didn't get ports for sbxvi snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] opl0 at port 0x388 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] Any hints are welcome. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 14:20:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id A442D14BDE; Fri, 5 Nov 1999 14:20:10 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id XAA89890; Fri, 5 Nov 1999 23:18:25 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9C36C4.dip.t-dialin.net [62.156.54.196]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id XAA89874; Fri, 5 Nov 1999 23:18:15 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id XAA51772; Fri, 5 Nov 1999 23:02:53 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3823540C.AE8ADA4F@dead-end.net> Date: Fri, 05 Nov 1999 23:02:52 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: sio working References: <199910230241.UAA26689@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > OK. I managed to get sio and ep working on the plane back from > FreeBSDCon'99. There are some problems with card eject at the moment, > but will be committing things to the tree shortly. > > Basically, I completely gutted the compatibilty layer and it became > much easier. More later after I've had a chance to spend time with my > wife and unwind from the drive back. I didn't have any luck using the sio driver with my card. Card info from "pccardc dumpcis": Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 2 000: 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = reserved, 32 units Tuple #2, code = 0x15 (Version 1 info), length = 32 000: 04 01 49 6e 74 65 6c 6c 69 67 65 6e 74 00 50 43 010: 4d 43 49 41 20 46 41 58 2b 4d 4f 44 45 4d 00 ff Version = 4.1, Manuf = [Intelligent],card vers = [PCMCIA FAX+MODEM] Tuple #3, code = 0x20 (Manufacturer ID), length = 4 000: 00 02 01 00 PCMCIA ID = 0x200, OEM ID = 0x1 Tuple #4, code = 0x21 (Functional ID), length = 2 000: 02 00 Serial port/modem Tuple #5, code = 0x22 (Functional EXT), length = 4 000: 00 02 0f 5c Serial interface extension: 16550 UART, Parity - Space,Mark,Odd,Even, Tuple #6, code = 0x22 (Functional EXT), length = 9 000: 05 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #7, code = 0x22 (Functional EXT), length = 9 000: 06 1f 1f 00 04 00 00 04 00 Modem interface capabilities: Tuple #8, code = 0x22 (Functional EXT), length = 12 000: 02 06 00 3f 1c 03 03 0f 07 00 01 b5 Data modem services available: Tuple #9, code = 0x22 (Functional EXT), length = 8 000: 13 06 00 1f 00 02 00 b5 Tuple #10, code = 0x22 (Functional EXT), length = 8 000: 23 06 00 1f 00 02 00 b5 Tuple #11, code = 0x1a (Configuration map), length = 5 000: 01 27 80 ff 67 Reg len = 2, config register addr = 0xff80, last config = 0x27 Registers: XXX--XX- Tuple #12, code = 0x1b (Configuration entry), length = 19 000: cf 41 99 79 55 3d 86 46 26 4c aa 60 f8 03 07 f0 010: bc 86 28 Config index = 0xf(default) Interface byte = 0x41 (I/O) +RDY/-BSY active Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 3.5 x 10mA Max current average over 1 second: 1 x 100mA, ext = 0x46 Max current average over 10 ms: 2 x 100mA Power down supply current: 4.5 x 1mA Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3f8 block length = 0x8 IRQ modes: Level, Pulse, Shared IRQs: 4 5 6 7 10 11 12 13 15 Max twin cards = 0 Misc attr: (Audio-BVD2) (Power down supported) Tuple #13, code = 0x1b (Configuration entry), length = 7 000: 17 08 aa 60 f8 02 07 Config index = 0x17 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2f8 block length = 0x8 Tuple #14, code = 0x1b (Configuration entry), length = 7 000: 1f 08 aa 60 e8 03 07 Config index = 0x1f Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x3e8 block length = 0x8 Tuple #15, code = 0x1b (Configuration entry), length = 7 000: 27 08 aa 60 e8 02 07 Config index = 0x27 Card decodes 10 address lines, 8 Bit I/O only I/O address # 1: block start = 0x2e8 block length = 0x8 Tuple #16, code = 0xff (Terminator), length = 0 My entry in /etc/pccard.conf: io 0x240-0x400 irq 11 15 card "Intelligent" "PCMCIA FAX+MODEM" # config 0x0f "sio2" ? # config 0x17 "sio2" ? config 0x1f "sio2" ? # config 0x27 "sio2" ? I tried many different combinations. I disabled the onboard serial devices in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with irq 4 but the only thing I get is sio2: configured irq -1071415680 not in bitmap of probed irqs 0 The irq number isn't always the same. It seems to be a pointer. Here the remaining relevant lines from my configuration: controller card0 controller pcic0 at isa? irq 10 controller pcic1 at isa? irq 10 Boot output: pcic-pci0: at device 10.0 on pci0 pcic-pci1: at device 10.1 on pci0 [...] pcic0: at irq 10 on isa0 pccard0: on pcic0 pccard1: on pcic0 Any hints? Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 14:20:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id 2605C15352 for ; Fri, 5 Nov 1999 14:20:46 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.9.3/8.9.3) with ESMTP id XAA21575; Fri, 5 Nov 1999 23:20:34 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.9.3/8.9.3) with UUCP id XAA27720; Fri, 5 Nov 1999 23:20:34 +0100 (MET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.3/8.8.8) with ESMTP id XAA22010; Fri, 5 Nov 1999 23:20:09 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Fri, 5 Nov 1999 23:20:09 +0100 (CET) From: Michael Reifenberger To: Lauri Laupmaa Cc: current@FreeBSD.ORG Subject: Re: stuck with ~year old current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 5 Nov 1999, Lauri Laupmaa wrote: ... > I have -CURRENT from 16 nov 1998 and stuck badly... > If I make new kernel, loader says its format's unknown, if I try to make > new loader, it says some gcc flag is unknown, if I try to make new gcc it The flag is probably -fformat-extensions so eliminate it from /usr/share/mk/bsd.kern.mk. Then build linker/kernel/world. The other fortcoming issues should be in /usr/src/UPDATING. If not please tell the solutions to imp@village.org :-) Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 14:32:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 31EF0153EA; Fri, 5 Nov 1999 14:32:37 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id JAA07091; Sat, 6 Nov 1999 09:02:06 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991105171215.45417@mojave.sitaranetworks.com> Date: Fri, 5 Nov 1999 17:12:15 -0500 From: Greg Lehey To: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: show stopper for Gcc 2.95.2 conversion Reply-To: Greg Lehey References: <19991105012449.A74246@dragon.nuxi.com> <19991105140415.A25486@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19991105140415.A25486@dragon.nuxi.com>; from David O'Brien on Fri, Nov 05, 1999 at 02:04:15PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 November 1999 at 14:04:15 -0800, David O'Brien wrote: > The current show stopper for switching over to GCC 2.95.2 is a problem > compiling the `ahc' driver: > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. > -I../../../include -DKERNEL -include opt_global.h -elf > ../../dev/aic7xxx/aic7xxx.c > ../../dev/aic7xxx/aic7xxx.c: In function `ahc_download_instr': > machine/bus.h:584: Invalid `asm' statement: > machine/bus.h:584: fixed or forbidden register 2 (cx) was spilled for class CREG. > *** Error code 1 > > The message is misleading, as the problematic header is > /sys/i386/include/bus.h not, /usr/include/machine/bus.h. In the kernel build environment, machine/ points to ../../i386/include. From the point of view of the compiler, the name is correct. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 14:39:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 21ABB14D3D; Fri, 5 Nov 1999 14:39:45 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id JAA07098; Sat, 6 Nov 1999 09:09:13 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991105173835.10766@mojave.sitaranetworks.com> Date: Fri, 5 Nov 1999 17:38:35 -0500 From: Greg Lehey To: "D. Rock" , Warner Losh Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: sio working Reply-To: Greg Lehey References: <199910230241.UAA26689@harmony.village.org> <3823540C.AE8ADA4F@dead-end.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <3823540C.AE8ADA4F@dead-end.net>; from D. Rock on Fri, Nov 05, 1999 at 11:02:52PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 5 November 1999 at 23:02:52 +0100, D. Rock wrote: > Warner Losh wrote: >> >> OK. I managed to get sio and ep working on the plane back from >> FreeBSDCon'99. There are some problems with card eject at the moment, >> but will be committing things to the tree shortly. >> >> Basically, I completely gutted the compatibilty layer and it became >> much easier. More later after I've had a chance to spend time with my >> wife and unwind from the drive back. > > I didn't have any luck using the sio driver with my card. > > Card info from "pccardc dumpcis": > > > card "Intelligent" "PCMCIA FAX+MODEM" > # config 0x0f "sio2" ? > # config 0x17 "sio2" ? > config 0x1f "sio2" ? > # config 0x27 "sio2" ? On my Dell Latitude CPi I have: device sio0 at isa? port IO_COM1 flags 0x90 irq 4 device sio1 at isa? port IO_COM2 irq 3 sio0 really exists; it seems that sio1 shouldn't be there, since I get the message Nov 5 17:15:39 mojave /kernel: devclass_alloc_unit: sio1 already exists, using next available unit number Nov 5 17:15:39 mojave /kernel: sio2 at port 0x2e8-0x2ef irq 5 slot 1 on pccard0 Nov 5 17:15:39 mojave /kernel: sio2: type 16550A Anyway, this configuration works: at least I can use it to dial in to a remote system. > I tried many different combinations. I disabled the onboard serial devices > in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with > irq 4 but the only thing I get is > sio2: configured irq -1071415680 not in bitmap of probed irqs 0 > > The irq number isn't always the same. It seems to be a pointer. Or junk. > Here the remaining relevant lines from my configuration: > controller card0 > controller pcic0 at isa? irq 10 > controller pcic1 at isa? irq 10 ISTR you should put card0 after pcic0 and pcic1. Also, I have no interrupts: device pcic0 at isa? device pcic1 at isa? controller card0 > Boot output: > pcic-pci0: at device 10.0 on pci0 > pcic-pci1: at device 10.1 on pci0 > [...] > pcic0: at irq 10 on isa0 > pccard0: on pcic0 > pccard1: on pcic0 I have: Nov 5 17:15:19 mojave /kernel: pcic-pci0: irq 11 at device 3.0 on pci0 Nov 5 17:15:19 mojave /kernel: pcic-pci1: irq 11 at device 3.1 on pci0 ... Nov 5 17:15:19 mojave /kernel: pcic0: on isa0 Nov 5 17:15:19 mojave /kernel: pccard0: on pcic0 Nov 5 17:15:19 mojave /kernel: pccard1: on pcic0 Nov 5 17:15:19 mojave /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 Nov 5 17:15:19 mojave /kernel: sio0: type 16550A Nov 5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 15:56:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id F28D814E9B for ; Fri, 5 Nov 1999 15:56:38 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA16290 for freebsd-current@FreeBSD.ORG; Sat, 6 Nov 1999 00:56:35 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3858E878D; Sat, 6 Nov 1999 00:50:16 +0100 (CET) Date: Sat, 6 Nov 1999 00:50:16 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Re: Serious locking problem in CURRENT Message-ID: <19991106005016.A865@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list References: <19991105225916.A14961@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991105225916.A14961@keltia.freenix.fr> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Ollivier Robert: > 3.3-RELEASE: > > 405 [22:56] root@sidhe:spool/postfix# lsof pid/master.pid > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > master 7155 root 7uW VREG 0,131079 17 18615 pid/master.pid > ^^^ Apparently the lock is NOT done on FreeBSD 4.0: 202 [0:47] root@keltia:sysutils/lsof# lsof /var/spool/postfix/pid/master.pid COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 242 root 7u VREG 13,131080 17 29093 pid/master.pid ^^^ (thanks to David O'Brien for having updated the lsof port). > Same Postfix versions on both. I even recompiled it on CURRENT. We have a problem here... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 17:41: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 48A6714D22; Fri, 5 Nov 1999 17:40:52 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 6DF041927; Sat, 6 Nov 1999 02:41:06 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 68B5D49D8; Sat, 6 Nov 1999 02:41:06 +0100 (CET) Date: Sat, 6 Nov 1999 02:41:06 +0100 (CET) From: Andrzej Bialecki To: sos@freebsd.org Cc: freebsd-current@freebsd.org Subject: libvgl - status and perspectives 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, Today I noticed accidentally that either libvgl is broken, or the demo program does something wrong - the mouse cursor doesn't move. But this brings more general question regarding console graphics library. As it is today, libvgl is almost useless due to very limited set of functions. There were discussions whether to port SVGAlib or GGI. Do you know if someone is working/planning to work on it? Thanks for any info. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 18:43:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D8D0214D85 for ; Fri, 5 Nov 1999 18:43:45 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id VAA26890; Fri, 5 Nov 1999 21:43:07 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA03974; Fri, 5 Nov 1999 21:42:36 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 5 Nov 1999 21:42:36 -0500 (EST) To: "Andrew Atrens" Cc: current@freebsd.org Subject: Re: ESS 1868 driver (again) In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14371.38041.94642.336584@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Atrens writes: > > Here's how my card is currently detected - > > pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 > Yamaha: ver 0x21 DMA config 0x84 > pcm: setmap 30000, ff00; 0xc77e9000 -> 30000 > pcm: setmap 40000, ff00; 0xc77f9000 -> 40000 > unknown0: at port 0x201 on isa0 > > If I'm not mistaken the old pcm preferred MSS emulation for this card. Is > it possible that the new pcm tries to use SB emulation ? I ask because I > know my SB emulation settings for this card are _wrong_. With old pcm, > this didn't appear to matter, but with new pcm, hmmmm. Something to try > out I guess when I get home tonight :) .. I have a very similar sound card as the on-board audio device on my Dell Dimension XPS D300: pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 Yamaha: ver 0x21 DMA config 0x82 pcm: setmap 30000, ff00; 0xcafae000 -> 30000 pcm: setmap 40000, ff00; 0xcafbe000 -> 40000 unknown0: at port 0x201 on isa0 I experience nearly the exact same symptoms as you (real player speeds through clips, amp works. I haven't tried the rtprio hack ;-). As with you, old pcm worked flawlessly. Have you made any progress? Is pcm using mss or sb mode on your card? Does forcing it one way or the other help? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 19:28:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A9EE614C37 for ; Fri, 5 Nov 1999 19:28:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA25886 for ; Fri, 5 Nov 1999 19:27:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA27684 for freebsd-current@FreeBSD.ORG; Fri, 5 Nov 1999 19:27:24 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Nov 1999 19:27:24 -0800 From: "David O'Brien" To: "FreeBSD Current Users' list" Subject: Re: Serious locking problem in CURRENT Message-ID: <19991105192724.A27651@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991105225916.A14961@keltia.freenix.fr> <19991106005016.A865@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991106005016.A865@keltia.freenix.fr>; from roberto@keltia.freenix.fr on Sat, Nov 06, 1999 at 12:50:16AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (thanks to David O'Brien for having updated the lsof port). More so to Vic Abell for bending over backwards to deal our changes. I forgot to mention that I've now given him access to my Alpha. So 4.46.1 mostly works on the Alpha now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 21: 7:23 1999 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 DAAD214BF8; Fri, 5 Nov 1999 21:07:19 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p89-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA17470; Sat, 6 Nov 1999 16:12:36 +1100 Date: Sat, 6 Nov 1999 16:07:06 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: show stopper for Gcc 2.95.2 conversion In-Reply-To: <19991105140415.A25486@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, 5 Nov 1999, David O'Brien wrote: > The current show stopper for switching over to GCC 2.95.2 is a problem > compiling the `ahc' driver: > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. > -I../../../include -DKERNEL -include opt_global.h -elf > ../../dev/aic7xxx/aic7xxx.c > ../../dev/aic7xxx/aic7xxx.c: In function `ahc_download_instr': > machine/bus.h:584: Invalid `asm' statement: > machine/bus.h:584: fixed or forbidden register 2 (cx) was spilled for class CREG. > *** Error code 1 The asm statement is broken. The clobber list shouldn't include any registers that are explicitly allocated as operands. See rev.1.85 of where this bug was fixed for several functions that used to have it there. Many functions in have the same bug. > The message is misleading, as the problematic header is > /sys/i386/include/bus.h not, /usr/include/machine/bus.h. It's actually machine/bus.h, where "machine" is the symlink to ../../i386/include in the compile directory. This is correct. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 5 21:29:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0E69114CB7 for ; Fri, 5 Nov 1999 21:29:28 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA26274 for ; Fri, 5 Nov 1999 21:27:55 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA74886 for current@FreeBSD.ORG; Fri, 5 Nov 1999 21:27:55 -0800 (PST) (envelope-from obrien) Date: Fri, 5 Nov 1999 21:27:55 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: show stopper for Gcc 2.95.2 conversion Message-ID: <19991105212755.T29186@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991105140415.A25486@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bde@zeta.org.au on Sat, Nov 06, 1999 at 04:07:06PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 06, 1999 at 04:07:06PM +1100, Bruce Evans wrote: > > The message is misleading, as the problematic header is > > /sys/i386/include/bus.h not, /usr/include/machine/bus.h. > > It's actually machine/bus.h, where "machine" is the symlink to > ../../i386/include in the compile directory. This is correct. Technically correct, but I wanted to make sure that anybody that wanted to help fix this was working the right file. Thus I wanted to mention that /usr/include/machine/bus.h was *not* the file to be working on. :) -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 1: 4:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 2D71314CAA for ; Sat, 6 Nov 1999 01:04:30 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id LAA32822 for freebsd-current@freebsd.org; Sat, 6 Nov 1999 11:04:28 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911060904.LAA32822@zibbi.mikom.csir.co.za> Subject: doscmd broken on current? To: freebsd-current@freebsd.org Date: Sat, 6 Nov 1999 11:04:28 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (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 Is doscmd working for anyone on current? Here I just get: --------- angel:~ > doscmd -bx Illegal instruction (core dumped) angel:~ > gdb /usr/obj/usr/src/usr.bin/doscmd/doscmd doscmd.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... Core was generated by `doscmd'. Program terminated with signal 4, Illegal instruction. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x3e in ?? () (gdb) bt #0 0x3e in ?? () #1 0x2600260 in ?? () Cannot access memory at address 0x2600000. (gdb) --------- I have tried it on a single processor and SMP -current and both do the same thing. I had it working a while back, so I think my configuration is ok. Ideas on how to look into this? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 1:35:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 3529114CAE for ; Sat, 6 Nov 1999 01:35:42 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id KAA00510 for ; Sat, 6 Nov 1999 10:34:18 +0100 (CET) Message-Id: <199911060934.KAA00510@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@freebsd.org Subject: Re: show stopper for Gcc 2.95.2 conversion Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 06 Nov 1999 16:07:06 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Nov 1999 10:34:18 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: >On Fri, 5 Nov 1999, David O'Brien wrote: > >> The current show stopper for switching over to GCC 2.95.2 is a problem >> compiling the `ahc' driver: >> >> cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >> -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. >> -I../../../include -DKERNEL -include opt_global.h -elf >> ../../dev/aic7xxx/aic7xxx.c >> ../../dev/aic7xxx/aic7xxx.c: In function `ahc_download_instr': >> machine/bus.h:584: Invalid `asm' statement: >> machine/bus.h:584: fixed or forbidden register 2 (cx) was spilled for class >CREG. >> *** Error code 1 > >The asm statement is broken. The clobber list shouldn't include any >registers that are explicitly allocated as operands. > As usual, Bruce is right. Here's a patch to bus.h which works for both EGCS and GCC 2.95.2. I have ahc0 and ahc1 and I generated and successfully booted kernels using both compilers with this patch. ===================== Patch ============================= --- /sys/i386/include/bus.h Sat Aug 28 02:44:07 1999 +++ /sys/i386/include/bus.h_mod Sat Nov 6 09:45:47 1999 @@ -260,7 +260,7 @@ loop 1b" : "=&a" (__x) : "r" (bsh + offset), "D" (addr), "c" (count) : - "%edi", "%ecx", "memory"); + "memory"); } #endif } @@ -288,7 +288,7 @@ loop 1b" : "=&a" (__x) : "r" (bsh + offset), "D" (addr), "c" (count) : - "%edi", "%ecx", "memory"); + "memory"); } #endif } @@ -316,7 +316,7 @@ loop 1b" : "=&a" (__x) : "r" (bsh + offset), "D" (addr), "c" (count) : - "%edi", "%ecx", "memory"); + "memory"); } #endif } @@ -364,7 +364,7 @@ loop 1b" : "=&a" (__x) : "d" (bsh + offset), "D" (addr), "c" (count) : - "%edx", "%edi", "%ecx", "memory"); + "memory"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -378,7 +378,7 @@ movsb" : : "S" (bsh + offset), "D" (addr), "c" (count) : - "%esi", "%edi", "%ecx", "memory"); + "memory"); } #endif } @@ -401,7 +401,7 @@ loop 1b" : "=&a" (__x) : "d" (bsh + offset), "D" (addr), "c" (count) : - "%edx", "%edi", "%ecx", "memory"); + "memory"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -415,7 +415,7 @@ movsw" : : "S" (bsh + offset), "D" (addr), "c" (count) : - "%esi", "%edi", "%ecx", "memory"); + "memory"); } #endif } @@ -438,7 +438,7 @@ loop 1b" : "=&a" (__x) : "d" (bsh + offset), "D" (addr), "c" (count) : - "%edx", "%edi", "%ecx", "memory"); + "memory"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -452,7 +452,7 @@ movsl" : : "S" (bsh + offset), "D" (addr), "c" (count) : - "%esi", "%edi", "%ecx", "memory"); + "memory"); } #endif } @@ -580,8 +580,7 @@ movb %%al,(%1) \n\ loop 1b" : "=&a" (__x) : - "r" (bsh + offset), "S" (addr), "c" (count) : - "%esi", "%ecx"); + "r" (bsh + offset), "S" (addr), "c" (count)); } #endif } @@ -608,8 +607,7 @@ movw %%ax,(%1) \n\ loop 1b" : "=&a" (__x) : - "r" (bsh + offset), "S" (addr), "c" (count) : - "%esi", "%ecx"); + "r" (bsh + offset), "S" (addr), "c" (count)); } #endif } @@ -636,8 +634,7 @@ movl %%eax,(%1) \n\ loop 1b" : "=&a" (__x) : - "r" (bsh + offset), "S" (addr), "c" (count) : - "%esi", "%ecx"); + "r" (bsh + offset), "S" (addr), "c" (count)); } #endif } @@ -686,7 +683,7 @@ loop 1b" : "=&a" (__x) : "d" (bsh + offset), "S" (addr), "c" (count) : - "%edx", "%esi", "%ecx", "memory"); + "memory"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -700,7 +697,7 @@ movsb" : : "D" (bsh + offset), "S" (addr), "c" (count) : - "%edi", "%esi", "%ecx", "memory"); + "memory"); } #endif } @@ -723,7 +720,7 @@ loop 1b" : "=&a" (__x) : "d" (bsh + offset), "S" (addr), "c" (count) : - "%edx", "%esi", "%ecx", "memory"); + "memory"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -737,7 +734,7 @@ movsw" : : "D" (bsh + offset), "S" (addr), "c" (count) : - "%edi", "%esi", "%ecx", "memory"); + "memory"); } #endif } @@ -760,7 +757,7 @@ loop 1b" : "=&a" (__x) : "d" (bsh + offset), "S" (addr), "c" (count) : - "%edx", "%esi", "%ecx", "memory"); + "memory"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -774,7 +771,7 @@ movsl" : : "D" (bsh + offset), "S" (addr), "c" (count) : - "%edi", "%esi", "%ecx", "memory"); + "memory"); } #endif } --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.cpqcorp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 2:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id ECCB514C40 for ; Sat, 6 Nov 1999 02:54:21 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 17D231CC6; Sat, 6 Nov 1999 18:54:20 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "D. Rock" Cc: current@FreeBSD.ORG Subject: Re: ESS 1868 driver, again In-reply-to: Your message of "Fri, 05 Nov 1999 22:53:21 +0100." <382351D1.F79539A1@dead-end.net> Date: Sat, 06 Nov 1999 18:54:20 +0800 From: Peter Wemm Message-Id: <19991106105420.17D231CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "D. Rock" wrote: > I read the last mails regarding problems with their ESS 1868 boards. > Well, at least it is partially working for them. I didn't have any > luck with the driver for some time now. I couldn't get a single tone. > > With the old voxware driver, sound worked at least partially > (44.1 kHz, 8 Bit, mono), but with the new driver I didn't have any > luck at all. > > Here my configuration: > device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 Err, the ESS1868 is a PNP device. You should only have "device pcm0" and nothing more. You might also try "options PNPBIOS". You are running -current, right? > and during boot: > pcm0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 4:54: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from krabi.mbp.ee (krabi.mbp.ee [194.204.12.83]) by hub.freebsd.org (Postfix) with ESMTP id DE3A514CA5 for ; Sat, 6 Nov 1999 04:54:02 -0800 (PST) (envelope-from mauri@krabi.mbp.ee) Received: from localhost (mauri@localhost) by krabi.mbp.ee (8.9.3/8.9.3) with ESMTP id OAA05909; Sat, 6 Nov 1999 14:53:58 +0200 (EET) (envelope-from mauri@krabi.mbp.ee) Date: Sat, 6 Nov 1999 14:53:58 +0200 (EET) From: Lauri Laupmaa To: Michael Reifenberger Cc: current@FreeBSD.ORG Subject: Re: stuck with ~year old current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Nov 1999, Michael Reifenberger wrote: > The flag is probably -fformat-extensions so eliminate it from > /usr/share/mk/bsd.kern.mk. > Then build linker/kernel/world. Thank you all who replied! The trick was to take new loader from running system, because it was impossible to build one with old gcc... _____________ Lauri Laupmaa ...speaking for myself only... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 5:45:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4644B14DFE for ; Sat, 6 Nov 1999 05:45:49 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 6 Nov 1999 13:45:48 +0000 (GMT) Date: Sat, 6 Nov 1999 13:45:48 +0000 From: David Malone To: Ollivier Robert Cc: FreeBSD Current Users' list Subject: Re: Serious locking problem in CURRENT Message-ID: <19991106134548.A2921@walton.maths.tcd.ie> References: <19991105225916.A14961@keltia.freenix.fr> <19991106005016.A865@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991106005016.A865@keltia.freenix.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 06, 1999 at 12:50:16AM +0100, Ollivier Robert wrote: A child process seems to be able to let go of a parent's lock on 4.0 by closing a file discriptor, the same doesn't seem to be true on 3.3. For example, if you try to run two copies of the included program as on 3.3, you get a resource unavailable message. 12:57:walton 6% ./lockf_test /tmp/blah 5 & [1] 2453 13:01:walton 7% ./lockf_test /tmp/blah 5 Unable to open file: Resource temporarily unavailable 13:01:walton 8% [1] Done ./lockf_test /tmp/blah 5 On 4.0 two run concurrently quite happily: 12:54:gonzo 65% ./lockf_test /tmp/blah 5 & [1] 943 13:02:gonzo 66% ./lockf_test /tmp/blah 5 [1] Done ./lockf_test /tmp/blah 5 13:02:gonzo 67% If you remove the "if(fork==0){close(fd);}" it two copies will not run concurrently on 4.0. I'm not sure which behavior is correct, but I suspect the 3.0 behavior is, 'cos /usr/bin/lockf is broken by this on 4.0. David. #include #include #include #include int main(int argc,char **argv) { int fd; if( argc != 3 ) { fprintf(stderr, "Usage: %s filename seconds\n", argv[0]); exit(1); } if( (fd = open(argv[1], O_RDONLY|O_CREAT|O_NONBLOCK|O_EXLOCK,0666)) == -1 ) { perror("Unable to open file"); exit(2); } if( fork() == 0 ) { close(fd); } sleep(atoi(argv[2])); exit(0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 8:12:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id DBD4314CD5 for ; Sat, 6 Nov 1999 08:12:52 -0800 (PST) (envelope-from patrick@137.org) Received: from friley-162-229.res.iastate.edu (friley-162-229.res.iastate.edu [129.186.162.229]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id B2BC464 for ; Sat, 6 Nov 1999 10:12:51 -0600 (CST) Received: from friley-162-229.res.iastate.edu (friley-162-229.res.iastate.edu [127.0.0.1]) by friley-162-229.res.iastate.edu (Postfix) with ESMTP id A17A05D12 for ; Sat, 6 Nov 1999 10:12:50 -0600 (CST) To: freebsd-current@freebsd.org Subject: Java segfaulting Date: Sat, 06 Nov 1999 10:12:50 -0600 From: Patrick Hartling Message-Id: <19991106161250.A17A05D12@friley-162-229.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -current as of 9:00 CDT October 30, and ever since I rebuilt, I have not been able to run any Java applications. All of them exit with the following error output: SIGSEGV 11* segmentation violation Full thread dump: Monitor Cache Dump: Registered Monitor Dump: Monitor IO lock: Child death monitor: Event monitor: I/O monitor: Alarm monitor: Memory allocation lock: Monitor registry: Thread Alarm Q: I also get this on the console: pid 649 (java_X), uid 13773: exited on signal 6 Is anyone else seeing this? If not, is there anything I might have missed when updating last weekend? My previous build was from October 12 (cvsup'd around 4:00 CDT I believe). I do know for sure that Java worked during the time between rebuilds. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:25:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id A9DCD14BCD for ; Sat, 6 Nov 1999 09:25:22 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id KAA21835; Sat, 6 Nov 1999 10:25:21 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA24454; Sat, 6 Nov 1999 10:25:21 -0700 Date: Sat, 6 Nov 1999 10:25:21 -0700 Message-Id: <199911061725.KAA24454@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Patrick Hartling Cc: freebsd-current@FreeBSD.ORG Subject: Re: Java segfaulting In-Reply-To: <19991106161250.A17A05D12@friley-162-229.res.iastate.edu> References: <19991106161250.A17A05D12@friley-162-229.res.iastate.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm running -current as of 9:00 CDT October 30, and ever since I rebuilt, I > have not been able to run any Java applications. All of them exit with > the following error output: Running Java on -current is at best a hit-miss operation, simply because we were forced to hard-code in some linker information into the JVM to support FreeBSD 3.0-3.2. This can cause problems in FreeBSD 4.*, since often the linker changes. This is not to say that it is due to those kinds of changes, but given the number of *large* scale changes to the entire 4.0 system, I'm suprised it works at all. At this point, the only platforms that I expect the JDK to work are 2.2.*/3.*. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:31:44 1999 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 1A0BE14E97; Sat, 6 Nov 1999 09:31:40 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA82505; Sat, 6 Nov 1999 10:31:38 -0700 (MST) (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 KAA22229; Sat, 6 Nov 1999 10:31:12 -0700 (MST) Message-Id: <199911061731.KAA22229@harmony.village.org> To: "Andrey A. Chernov" Subject: Re: -current panic on AHA Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Nov 1999 11:03:59 +0300." <19991104110359.A2933@nagual.pp.ru> References: <19991104110359.A2933@nagual.pp.ru> Date: Sat, 06 Nov 1999 10:31:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991104110359.A2933@nagual.pp.ru> "Andrey A. Chernov" writes: : Very fresh -current always paniced after detecting SCSI devices on : aha0: AHA-1542CF FW Rev. B.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs : page fault: supervisor, read page not present : Old kernel from Oct 8 works nicely : Sorry can't provide more info about panic, it is remote computer. That's very odd. Any chance that you can provide more info on the panic? I'd like to look into this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:31:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id E914C14F30 for ; Sat, 6 Nov 1999 09:31:52 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id LAA23242 for ; Sat, 6 Nov 1999 11:31:51 -0600 (CST) Date: Sat, 6 Nov 1999 11:31:50 -0600 (CST) From: Steve Price To: freebsd-current@FreeBSD.org Subject: gzip(1) hanging Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've got a -current box freshly CVSup'd and built from last night that is exhibiting some rather bizarre behavior. I actually noticed the problem on my Alpha package building machine, but the same behavior exists on my i386 box. To see what I'm seeing (or maybe not :) all you have to do is this: cd /usr/ports/graphics/jpeg make extract The gzip(1) process is hanging in pipdwt. I run the equivalent commands from the commandline and it works fine. I 'kill -6'd the offending process and this is what the stack trace looks like. (gdb) bt #0 0x80502b4 in write () #1 0x804e319 in write_buf (fd=1, buf=0x80a6300, cnt=32768) at /usr/src/gnu/usr.bin/gzip/util.c:162 #2 0x804e2d6 in flush_window () at /usr/src/gnu/usr.bin/gzip/util.c:139 #3 0x804d47c in inflate_codes (tl=0x80b8008, td=0x80bd008, bl=9, bd=6) at /usr/src/gnu/usr.bin/gzip/inflate.c:580 #4 0x804df09 in inflate_dynamic () at /usr/src/gnu/usr.bin/gzip/inflate.c:857 #5 0x804e00a in inflate_block (e=0xbfbfd8c8) at /usr/src/gnu/usr.bin/gzip/inflate.c:902 #6 0x804e06c in inflate () at /usr/src/gnu/usr.bin/gzip/inflate.c:933 #7 0x804c7d0 in unzip (in=4, out=1) at /usr/src/gnu/usr.bin/gzip/unzip.c:120 #8 0x8048db3 in treat_file ( iname=0xbfbfdaed "/usr/ports/distfiles//jpegsrc.v6b.tar.gz") at /usr/src/gnu/usr.bin/gzip/gzip.c:820 #9 0x804873d in main (argc=5, argv=0xbfbfd9b8) at /usr/src/gnu/usr.bin/gzip/gzip.c:599 #10 0x80480e9 in _start () Can anyone confirm this happens on their box? Anyone have any ideas on how to go about fixing this? Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:44:41 1999 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 5213314C20 for ; Sat, 6 Nov 1999 09:44:38 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA82557; Sat, 6 Nov 1999 10:44:37 -0700 (MST) (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 KAA22325; Sat, 6 Nov 1999 10:44:19 -0700 (MST) Message-Id: <199911061744.KAA22325@harmony.village.org> To: frank@exit.com Subject: Re: Wondering about cardbus support. Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Nov 1999 21:18:00 PST." <199911050518.VAA29749@realtime.exit.com> References: <199911050518.VAA29749@realtime.exit.com> Date: Sat, 06 Nov 1999 10:44:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911050518.VAA29749@realtime.exit.com> Frank Mayhar writes: : I have the misfortune to have a cardbus Ethernet card that came with my : Dell laptop. I was wondering how cardbus support was going, and if I could : help in any way. Here's the status of what's going on... I have started to port the newconfig cardbus and pccard system to newbus. I've managed to make pccard and pcic compile for that. I'm working on getting cardbus and the pccbb driver compiling as well. I've committed the pccard parts of this, but not the cardbus side. I had heard of an effort in Japan to also do cardbus support, but my attempts to contact them have been unsuccessful so far. However, in the middle of this work my Sony VAIO laptop up and died. It has been sent back to Sony for repairs, but I don't know when I'll get it back from them, or if the data on my hard drive will be intact. My current plan is while I'm waiting for the VAIO to come back is to try to get the pcic device attaching, as well as trying to wire up the pccard bus to it. I'm a little short on time, but am making what progress I can... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:47: 6 1999 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 2687414C20; Sat, 6 Nov 1999 09:47:03 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA82577; Sat, 6 Nov 1999 10:47:02 -0700 (MST) (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 KAA22355; Sat, 6 Nov 1999 10:46:44 -0700 (MST) Message-Id: <199911061746.KAA22355@harmony.village.org> To: Will Andrews Subject: Re: boot problems with todays kernel Cc: Bob Vaughan , current@FreeBSD.ORG, mdodd@FreeBSD.ORG In-reply-to: Your message of "Fri, 05 Nov 1999 02:19:08 EST." <3.0.6.32.19991105021908.008c1de0@mail.psn.net> References: <3.0.6.32.19991105021908.008c1de0@mail.psn.net> <3.0.6.32.19991104222248.008b3e10@mail.psn.net> Date: Sat, 06 Nov 1999 10:46:43 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3.0.6.32.19991105021908.008c1de0@mail.psn.net> Will Andrews writes: : Hmm.. ep0 on IRQ 3? It should be on IRQ 10. At least, that's what has : always worked : for me on previous -CURRENT code. Otherwise I get the same last 2 messages. I've always used 11. : Yep - this happens to me when i do a `ifconfig ep0`. Ka-boom. I'm not seeing this here. What cards are involved to make this happen? It is possible something got screwed up when I converted to newbus the if_ep_pccard attachment... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:49:50 1999 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 B53BD14C20; Sat, 6 Nov 1999 09:49:46 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA82586; Sat, 6 Nov 1999 10:49:44 -0700 (MST) (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 KAA22375; Sat, 6 Nov 1999 10:49:26 -0700 (MST) Message-Id: <199911061749.KAA22375@harmony.village.org> To: Greg Lehey Subject: Re: sio working Cc: "D. Rock" , current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 05 Nov 1999 17:38:35 EST." <19991105173835.10766@mojave.sitaranetworks.com> References: <19991105173835.10766@mojave.sitaranetworks.com> <199910230241.UAA26689@harmony.village.org> <3823540C.AE8ADA4F@dead-end.net> Date: Sat, 06 Nov 1999 10:49:26 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991105173835.10766@mojave.sitaranetworks.com> Greg Lehey writes: : Nov 5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Unless you are running pccardd, you won't see the pccard devices show up. The probe messages that I'm interested in would be the ones that say something about it being on pccard0. Maybe I'm just confused. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:53:50 1999 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 1E7AA14EDE; Sat, 6 Nov 1999 09:53:46 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA82610; Sat, 6 Nov 1999 10:53:45 -0700 (MST) (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 KAA22419; Sat, 6 Nov 1999 10:53:28 -0700 (MST) Message-Id: <199911061753.KAA22419@harmony.village.org> To: "D. Rock" Subject: Re: sio working Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 05 Nov 1999 23:02:52 +0100." <3823540C.AE8ADA4F@dead-end.net> References: <3823540C.AE8ADA4F@dead-end.net> <199910230241.UAA26689@harmony.village.org> Date: Sat, 06 Nov 1999 10:53:28 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3823540C.AE8ADA4F@dead-end.net> "D. Rock" writes: : I tried many different combinations. I disabled the onboard serial devices : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with : irq 4 but the only thing I get is : sio2: configured irq -1071415680 not in bitmap of probed irqs 0 That is very odd... Do you have sio2 in your config file? If so just take it out and see if that helps or hurts (or replace what is there with "device sio2" As always when you see odd problems like this, try a make clean && make depend && make in the compile directory (after reconfiguring). I don't think it will help the current situation, but it won't hurt. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 9:56:25 1999 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 781C414E97 for ; Sat, 6 Nov 1999 09:56:23 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA82630; Sat, 6 Nov 1999 10:56:22 -0700 (MST) (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 KAA22478; Sat, 6 Nov 1999 10:56:03 -0700 (MST) Message-Id: <199911061756.KAA22478@harmony.village.org> To: John Hay Subject: Re: doscmd broken on current? Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 06 Nov 1999 11:04:28 +0200." <199911060904.LAA32822@zibbi.mikom.csir.co.za> References: <199911060904.LAA32822@zibbi.mikom.csir.co.za> Date: Sat, 06 Nov 1999 10:56:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911060904.LAA32822@zibbi.mikom.csir.co.za> John Hay writes: : angel:~ > doscmd -bx I've never been able to boot dos with doscmd. I've only ever run programs like sourcer with 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 Nov 6 10: 0:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 97F5B14F0C for ; Sat, 6 Nov 1999 10:00:20 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id LAA22149; Sat, 6 Nov 1999 11:00:19 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA24683; Sat, 6 Nov 1999 11:00:18 -0700 Date: Sat, 6 Nov 1999 11:00:18 -0700 Message-Id: <199911061800.LAA24683@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Steve Price Cc: freebsd-current@FreeBSD.ORG Subject: Re: gzip(1) hanging In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a -current box freshly CVSup'd and built from last > night that is exhibiting some rather bizarre behavior. I > actually noticed the problem on my Alpha package building > machine, but the same behavior exists on my i386 box. > > To see what I'm seeing (or maybe not :) all you have to do > is this: > > cd /usr/ports/graphics/jpeg > make extract Martin C. made a change to 'sh' yesterday with regards to file-descriptors that might have something to do with this... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 10:26:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 0630414E46 for ; Sat, 6 Nov 1999 10:26:35 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id MAA24279; Sat, 6 Nov 1999 12:26:33 -0600 (CST) Date: Sat, 6 Nov 1999 12:26:33 -0600 (CST) From: Steve Price To: Nate Williams Cc: freebsd-current@FreeBSD.ORG Subject: Re: gzip(1) hanging In-Reply-To: <199911061800.LAA24683@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Nov 1999, Nate Williams wrote: # > I've got a -current box freshly CVSup'd and built from last # > night that is exhibiting some rather bizarre behavior. I # > actually noticed the problem on my Alpha package building # > machine, but the same behavior exists on my i386 box. # > # > To see what I'm seeing (or maybe not :) all you have to do # > is this: # > # > cd /usr/ports/graphics/jpeg # > make extract # # Martin C. made a change to 'sh' yesterday with regards to # file-descriptors that might have something to do with this... Great catch Nate! The following patch fixes the problem that I'm seeing and still addresses the problem Martin was trying to fix as part of bin/14527. Index: eval.c =================================================================== RCS file: /home/ncvs/src/bin/sh/eval.c,v retrieving revision 1.23 diff -u -r1.23 eval.c --- eval.c 1999/11/05 12:06:30 1.23 +++ eval.c 1999/11/06 18:18:23 @@ -499,7 +499,7 @@ close(prevfd); } if (pip[1] >= 0) { - if (!prevfd > 0) + if (prevfd < 0) close(pip[0]); if (pip[1] != 1) { close(1); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 10:42: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 00B0714E82 for ; Sat, 6 Nov 1999 10:41:59 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA11324; Sat, 6 Nov 1999 12:41:58 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id MAA29996; Sat, 6 Nov 1999 12:41:58 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id MAA26019; Sat, 6 Nov 1999 12:41:57 -0600 (CST) Date: Sat, 6 Nov 1999 12:41:57 -0600 (CST) From: Jonathan Lemon Message-Id: <199911061841.MAA26019@free.pcs> To: jhay@mikom.csir.co.za, current@freebsd.org Subject: Re: doscmd broken on current? X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Is doscmd working for anyone on current? Here I just get: > >--------- > >I have tried it on a single processor and SMP -current and both do the same >thing. I had it working a while back, so I think my configuration is ok. > >Ideas on how to look into this? Start by invoking it with the various debug/trace options. I'd guess that it may be broken by the signal-related changes that were made recently. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 11:14:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id DAF1414BDC; Sat, 6 Nov 1999 11:14:18 -0800 (PST) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id WAA24069; Sat, 6 Nov 1999 22:13:44 +0300 (MSK) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id WAA02732; Sat, 6 Nov 1999 22:21:03 +0300 (MSK) (envelope-from dima@tejblum.pp.ru) Message-Id: <199911061921.WAA02732@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: David Malone Cc: Ollivier Robert , "FreeBSD Current Users' list" , green@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: Serious locking problem in CURRENT In-reply-to: Your message of "Sat, 06 Nov 1999 13:45:48 GMT." <19991106134548.A2921@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Nov 1999 22:21:03 +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > A child process seems to be able to let go of a parent's lock on > 4.0 by closing a file discriptor, the same doesn't seem to be true > on 3.3. So, apparently, it was broken in rev. 1.68 of kern_descript.c. (Another example that comments (in closef() in this case) serve no purpose :-/). BTW, I have another little concern with that commit: It make possible for last close() of a file descriptor to return 0 instead of the error from VOP_CLOSE(), and the error from VOP_CLOSE() to be ignored. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 11:29:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id EA1EC14BE0 for ; Sat, 6 Nov 1999 11:29:21 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA11411; Sat, 6 Nov 1999 13:29:17 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id NAA24877; Sat, 6 Nov 1999 13:29:16 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id NAA26145; Sat, 6 Nov 1999 13:29:16 -0600 (CST) Date: Sat, 6 Nov 1999 13:29:16 -0600 (CST) From: Jonathan Lemon Message-Id: <199911061929.NAA26145@free.pcs> To: dwmalone@maths.tcd.ie, current@freebsd.org, Ollivier Robert Subject: Re: Serious locking problem in CURRENT X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > >On Sat, Nov 06, 1999 at 12:50:16AM +0100, Ollivier Robert wrote: > >A child process seems to be able to let go of a parent's lock on >4.0 by closing a file discriptor, the same doesn't seem to be true >on 3.3. From the manual page for flock: NOTES Locks are on files, not file descriptors. That is, file descriptors du- plicated through dup(2) or fork(2) do not result in multiple instances of a lock, but rather multiple references to a single lock. If a process holding a lock on a file forks and the child explicitly unlocks the file, the parent will lose its lock. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 12: 2: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 3626714C27 for ; Sat, 6 Nov 1999 12:01:57 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA00624; Sat, 6 Nov 1999 22:01:48 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911062001.WAA00624@gratis.grondar.za> To: Steve Price Cc: freebsd-current@FreeBSD.ORG Subject: Re: gzip(1) hanging Date: Sat, 06 Nov 1999 22:01:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can anyone confirm this happens on their box? Anyone have any > ideas on how to go about fixing this? I get exactly the same thing. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 12:24:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 5B3B814E8F for ; Sat, 6 Nov 1999 12:24:50 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id WAA41602; Sat, 6 Nov 1999 22:24:35 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911062024.WAA41602@zibbi.mikom.csir.co.za> Subject: Re: doscmd broken on current? In-Reply-To: <199911061841.MAA26019@free.pcs> from Jonathan Lemon at "Nov 6, 1999 12:41:57 pm" To: jlemon@americantv.com (Jonathan Lemon) Date: Sat, 6 Nov 1999 22:24:35 +0200 (SAT) Cc: jhay@mikom.csir.co.za, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > >Is doscmd working for anyone on current? Here I just get: > > > >--------- > > > >I have tried it on a single processor and SMP -current and both do the same > >thing. I had it working a while back, so I think my configuration is ok. > > > >Ideas on how to look into this? > > Start by invoking it with the various debug/trace options. I'd guess > that it may be broken by the signal-related changes that were made > recently. hehehe It dies at the very first vm86 instruction, so I guess something isn't setup correctly to enter vm86 mode via the sigreturn(): ------------ angel:/usr/src/usr.bin/doscmd > doscmd -bx23At init_path(3, /, (null)) init_path(4, /home/jhay/dos, (null)) CS: IP instruction AX BX CX DX DI SI SP BP SS DS ES 0000:7c00 jmp 0000:7c3e 0000 0000 0000 0000 0000 0000 7ffe 0000 9800 0000 0000 I v Illegal instruction angel:/usr/src/usr.bin/doscmd > ------------ Hmmm I see the sigreturn man page hasn't been updated, it still says that sigreturn takes a struct sigcontext * argument, while the signal.h file says it takes ucontext_t *. Now to try and figure out how this stuff is supposed to work. :-) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 12:50:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 9612114C9E; Sat, 6 Nov 1999 12:50:29 -0800 (PST) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id XAA24667; Sat, 6 Nov 1999 23:50:28 +0300 (MSK) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id XAA03228; Sat, 6 Nov 1999 23:57:41 +0300 (MSK) (envelope-from dima@tejblum.pp.ru) Message-Id: <199911062057.XAA03228@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Brian Fundakowski Feldman Cc: Dmitrij Tejblum , "FreeBSD Current Users' list" From: Dmitrij Tejblum Subject: Re: Serious locking problem in CURRENT In-reply-to: Your message of "Sat, 06 Nov 1999 14:25:50 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Nov 1999 23:57:40 +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > There were zero comments about what order things happen in; in fact, > the ordering in this case is Just Plain Lame (TM). It's much more > correct to explicitly check for fp->f_count == 1. Not sure what you mean. The commit clearly states that POSIX and BSD locking intentionally handled in different ways here. Frankly, I see nothing lame in the ordering. The second VOP_ADVLOCK just should be moved to fdrop(). > > BTW, I have another little concern with that commit: It make possible for > > last close() of a file descriptor to return 0 instead of the error from > > VOP_CLOSE(), and the error from VOP_CLOSE() to be ignored. When a process do closef() on a descriptor "held" by another process (by fhold(), e.g. the process do read() on the descriptor), it will just return 0 without the call to fo_close(). Then, when the other process drop the descriptor, fdrop() call fo_close() but the error is thrown away. No? Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 15:12: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 42FAE14F97 for ; Sat, 6 Nov 1999 15:11:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id PAA33630; Sat, 6 Nov 1999 15:11:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA05885; Sat, 6 Nov 1999 15:11:48 -0800 (PST) (envelope-from obrien) Date: Sat, 6 Nov 1999 15:11:48 -0800 From: "David O'Brien" To: Gary Jennejohn Cc: freebsd-current@freebsd.org Subject: Re: show stopper for Gcc 2.95.2 conversion Message-ID: <19991106151148.B5642@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199911060934.KAA00510@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911060934.KAA00510@peedub.muc.de>; from garyj@peedub.muc.de on Sat, Nov 06, 1999 at 10:34:18AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 06, 1999 at 10:34:18AM +0100, Gary Jennejohn wrote: > Here's a patch to bus.h which works for both EGCS and GCC 2.95.2. I have Here is the patch I've been working on (before I 1st got BDE's reply). The changes are mostly from OpenBSD + style changes for the way we do things. Can you also test this one? Index: bus.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/bus.h,v retrieving revision 1.6 diff -u -r1.6 bus.h --- bus.h 1999/08/28 00:44:07 1.6 +++ bus.h 1999/11/06 21:42:15 @@ -252,15 +252,14 @@ else #endif { - int __x __asm__("%eax"); __asm __volatile(" \n\ cld \n\ - 1: movb (%1),%%al \n\ + 1: movb (%2),%%al \n\ stosb \n\ loop 1b" : - "=&a" (__x) : - "r" (bsh + offset), "D" (addr), "c" (count) : - "%edi", "%ecx", "memory"); + "=D" (addr), "=c" (count) : + "r" (bsh + offset), "0" (addr), "1" (count) : + "%eax", "memory"); } #endif } @@ -280,15 +279,14 @@ else #endif { - int __x __asm__("%eax"); __asm __volatile(" \n\ cld \n\ - 1: movw (%1),%%ax \n\ + 1: movw (%2),%%ax \n\ stosw \n\ loop 1b" : - "=&a" (__x) : - "r" (bsh + offset), "D" (addr), "c" (count) : - "%edi", "%ecx", "memory"); + "=D" (addr), "=c" (count) : + "r" (bsh + offset), "0" (addr), "1" (count) : + "%eax", "memory"); } #endif } @@ -308,15 +306,14 @@ else #endif { - int __x __asm__("%eax"); __asm __volatile(" \n\ cld \n\ - 1: movl (%1),%%eax \n\ + 1: movl (%2),%%eax \n\ stosl \n\ loop 1b" : - "=&a" (__x) : - "r" (bsh + offset), "D" (addr), "c" (count) : - "%edi", "%ecx", "memory"); + "=D" (addr), "=c" (count) : + "r" (bsh + offset), "0" (addr), "1" (count) : + "%eax", "memory"); } #endif } @@ -355,16 +352,16 @@ if (tag == I386_BUS_SPACE_IO) #endif { - int __x __asm__("%eax"); + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ - 1: inb %w1,%%al \n\ + 1: inb %w2,%%al \n\ stosb \n\ - incl %1 \n\ + incl %2 \n\ loop 1b" : - "=&a" (__x) : - "d" (bsh + offset), "D" (addr), "c" (count) : - "%edx", "%edi", "%ecx", "memory"); + "=D" (addr), "=c" (count), "=d" (_port_) : + "0" (addr), "1" (count), "2" (bsh + offset) : + "%eax", "memory", "cc"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -372,13 +369,14 @@ else #endif { + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ repne \n\ movsb" : - : - "S" (bsh + offset), "D" (addr), "c" (count) : - "%esi", "%edi", "%ecx", "memory"); + "=S" (_port_), "=D" (addr), "=c" (count) : + "0" (addr), "1" (count), "2" (bsh + offset) : + "memory", "cc"); } #endif } @@ -392,16 +390,16 @@ if (tag == I386_BUS_SPACE_IO) #endif { - int __x __asm__("%eax"); + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ - 1: inw %w1,%%ax \n\ + 1: inw %w2,%%ax \n\ stosw \n\ - addl $2,%1 \n\ + addl $2,%2 \n\ loop 1b" : - "=&a" (__x) : - "d" (bsh + offset), "D" (addr), "c" (count) : - "%edx", "%edi", "%ecx", "memory"); + "=D" (addr), "=c" (count), "=d" (_port_) : + "0" (addr), "1" (count), "2" (bsh + offset) : + "%eax", "memory", "cc"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -409,13 +407,14 @@ else #endif { + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ repne \n\ movsw" : - : - "S" (bsh + offset), "D" (addr), "c" (count) : - "%esi", "%edi", "%ecx", "memory"); + "=S" (_port_), "=D" (addr), "=c" (count) : + "0" (addr), "1" (count), "2" (bsh + offset) : + "memory", "cc"); } #endif } @@ -429,16 +428,16 @@ if (tag == I386_BUS_SPACE_IO) #endif { - int __x __asm__("%eax"); + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ - 1: inl %w1,%%eax \n\ + 1: inl %w2,%%eax \n\ stosl \n\ - addl $4,%1 \n\ + addl $4,%2 \n\ loop 1b" : - "=&a" (__x) : - "d" (bsh + offset), "D" (addr), "c" (count) : - "%edx", "%edi", "%ecx", "memory"); + "=D" (addr), "=c" (count), "=d" (_port_) : + "0" (addr), "1" (count), "2" (bsh + offset) : + "%eax", "memory", "cc"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -446,13 +445,14 @@ else #endif { + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ repne \n\ movsl" : - : - "S" (bsh + offset), "D" (addr), "c" (count) : - "%esi", "%edi", "%ecx", "memory"); + "=S" (_port_), "=D" (addr), "=c" (count) : + "0" (addr), "1" (count), "2" (bsh + offset) : + "memory", "cc"); } #endif } @@ -573,15 +573,14 @@ else #endif { - int __x __asm__("%eax"); __asm __volatile(" \n\ cld \n\ 1: lodsb \n\ - movb %%al,(%1) \n\ + movb %%al,(%2) \n\ loop 1b" : - "=&a" (__x) : - "r" (bsh + offset), "S" (addr), "c" (count) : - "%esi", "%ecx"); + "=S" (addr), "=c" (count) : + "r" (bsh + offset), "0" (addr), "1" (count) : + "%eax", "memory", "cc"); } #endif } @@ -601,15 +600,15 @@ else #endif { - int __x __asm__("%eax"); __asm __volatile(" \n\ cld \n\ 1: lodsw \n\ movw %%ax,(%1) \n\ + movw %%ax,(%2) \n\ loop 1b" : - "=&a" (__x) : - "r" (bsh + offset), "S" (addr), "c" (count) : - "%esi", "%ecx"); + "=S" (addr), "=c" (count) : + "r" (bsh + offset), "0" (addr), "1" (count) : + "%eax", "memory", "cc"); } #endif } @@ -629,15 +628,14 @@ else #endif { - int __x __asm__("%eax"); __asm __volatile(" \n\ cld \n\ 1: lodsl \n\ - movl %%eax,(%1) \n\ + movl %%eax,(%2) \n\ loop 1b" : - "=&a" (__x) : - "r" (bsh + offset), "S" (addr), "c" (count) : - "%esi", "%ecx"); + "=S" (addr), "=c" (count) : + "r" (bsh + offset), "0" (addr), "1" (count) : + "%eax", "memory", "cc"); } #endif } @@ -677,16 +675,16 @@ if (tag == I386_BUS_SPACE_IO) #endif { - int __x __asm__("%eax"); + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ 1: lodsb \n\ outb %%al,%w1 \n\ incl %1 \n\ loop 1b" : - "=&a" (__x) : - "d" (bsh + offset), "S" (addr), "c" (count) : - "%edx", "%esi", "%ecx", "memory"); + "=S" (addr), "=c" (count), "=d" (_port_) : + "0" (bsh + offset), "1" (addr), "2" (count) : + "%eax", "memory", "cc"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -694,13 +692,14 @@ else #endif { + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ repne \n\ movsb" : - : - "D" (bsh + offset), "S" (addr), "c" (count) : - "%edi", "%esi", "%ecx", "memory"); + "=S" (addr), "=D" (_port_), "=c" (count) : + "0" (bsh + offset), "1" (addr), "2" (count) : + "memory", "cc"); } #endif } @@ -714,16 +713,16 @@ if (tag == I386_BUS_SPACE_IO) #endif { - int __x __asm__("%eax"); + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ 1: lodsw \n\ outw %%ax,%w1 \n\ addl $2,%1 \n\ loop 1b" : - "=&a" (__x) : - "d" (bsh + offset), "S" (addr), "c" (count) : - "%edx", "%esi", "%ecx", "memory"); + "=S" (addr), "=c" (count), "=d" (_port_) : + "0" (bsh + offset), "1" (addr), "2" (count) : + "%eax", "memory", "cc"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -731,13 +730,14 @@ else #endif { + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ repne \n\ movsw" : - : - "D" (bsh + offset), "S" (addr), "c" (count) : - "%edi", "%esi", "%ecx", "memory"); + "=S" (addr), "=D" (_port_), "=c" (count) : + "0" (bsh + offset), "1" (addr), "2" (count) : + "memory", "cc"); } #endif } @@ -751,16 +751,16 @@ if (tag == I386_BUS_SPACE_IO) #endif { - int __x __asm__("%eax"); + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ 1: lodsl \n\ outl %%eax,%w1 \n\ addl $4,%1 \n\ loop 1b" : - "=&a" (__x) : - "d" (bsh + offset), "S" (addr), "c" (count) : - "%edx", "%esi", "%ecx", "memory"); + "=S" (addr), "=c" (count), "=d" (_port_) : + "0" (bsh + offset), "1" (addr), "2" (count) : + "%eax", "memory", "cc"); } #endif #if defined(_I386_BUS_MEMIO_H_) @@ -768,13 +768,14 @@ else #endif { + int _port_ = bsh + offset; \ __asm __volatile(" \n\ cld \n\ repne \n\ movsl" : - : - "D" (bsh + offset), "S" (addr), "c" (count) : - "%edi", "%esi", "%ecx", "memory"); + "=S" (addr), "=D" (_port_), "=c" (count) : + "0" (bsh + offset), "1" (addr), "2" (count) : + "memory", "cc"); } #endif } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 16:38:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 07C2614F93 for ; Sat, 6 Nov 1999 16:38:39 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA50519 for ; Sat, 6 Nov 1999 16:38:39 -0800 (PST) Date: Sat, 6 Nov 1999 16:38:38 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: Old KLD bug.. 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 If I have a KLD module that has a registered dependency on some other module, then when I load the forst module it will load the second. this is all well and good but it ALWYA loads it, even when it's already in the kernel.. if kldstat can see it, then surely the loading modules should be able to work it out. This has been partly fixed in -current (it loads but doesn't link) but in 3.x it actually links the new one over the existing one, which is kinda wrong.. Is there anyone that understands this stuff that has an idea of ho to fix this? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 16:43:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id AF28614DBF for ; Sat, 6 Nov 1999 16:43:02 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id BAA69907; Sun, 7 Nov 1999 01:42:41 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (pC19F74D2.dip.t-dialin.net [193.159.116.210]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id BAA69883; Sun, 7 Nov 1999 01:42:34 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id BAA61531; Sun, 7 Nov 1999 01:42:41 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3824CAF3.A31B97D5@dead-end.net> Date: Sun, 07 Nov 1999 01:42:27 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: ESS 1868 driver, again References: <19991106105420.17D231CC6@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > "D. Rock" wrote: > > I read the last mails regarding problems with their ESS 1868 boards. > > Well, at least it is partially working for them. I didn't have any > > luck with the driver for some time now. I couldn't get a single tone. > > > > With the old voxware driver, sound worked at least partially > > (44.1 kHz, 8 Bit, mono), but with the new driver I didn't have any > > luck at all. > > > > Here my configuration: > > device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 > > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and > nothing more. You might also try "options PNPBIOS". You are running > -current, right? What does "options PNPBIOS" do. I didn't find it in LINT? This one doesn't seem to be a PNP device. I set all the resources manually via BIOS. If it was a PNP device, it shouldn't be detected any longer by the old voxware driver. # pnpinfo Checking for Plug-n-Play devices... No Plug-n-Play devices were found Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 16:50:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id D272314DBF; Sat, 6 Nov 1999 16:50:43 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id BAA70619; Sun, 7 Nov 1999 01:50:28 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (pC19F74D2.dip.t-dialin.net [193.159.116.210]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id BAA70611; Sun, 7 Nov 1999 01:50:25 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id BAA61586; Sun, 7 Nov 1999 01:50:39 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3824CCD1.C07B6A8@dead-end.net> Date: Sun, 07 Nov 1999 01:50:25 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: sio working References: <3823540C.AE8ADA4F@dead-end.net> <199910230241.UAA26689@harmony.village.org> <199911061753.KAA22419@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <3823540C.AE8ADA4F@dead-end.net> "D. Rock" writes: > : I tried many different combinations. I disabled the onboard serial devices > : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with > : irq 4 but the only thing I get is > : sio2: configured irq -1071415680 not in bitmap of probed irqs 0 > > That is very odd... Do you have sio2 in your config file? If so just > take it out and see if that helps or hurts (or replace what is there > with "device sio2" As always when you see odd problems like this, > try a make clean && make depend && make in the compile directory > (after reconfiguring). I don't think it will help the current > situation, but it won't hurt. Had tried it all before. No sio2 in kernel. Below is the complete config file Daniel --- machine i386 ident LAPTOP maxusers 6 options PQ_LARGECACHE cpu I686_CPU options COMPAT_43 #options USER_LDT options SYSVSHM options SYSVSEM options SYSVMSG options MD5 #options DDB #options DDB_UNATTENDED options KTRACE options PERFMON options UCONSOLE #options USERCONFIG #options VISUAL_USERCONFIG options INET pseudo-device ether #pseudo-device sppp pseudo-device loop pseudo-device bpf pseudo-device tun #options MROUTING #options IPFIREWALL #options IPFIREWALL_VERBOSE #options IPFIREWALL_FORWARD #options IPFIREWALL_DEFAULT_TO_ACCEPT #options IPDIVERT #options IPSTEALTH options ICMP_BANDLIM #options DUMMYNET options FFS options NFS options NFS_NOSERVER options CD9660 options MSDOSFS options PROCFS options FFS_ROOT options SOFTUPDATES options QUOTA options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L #controller scbus0 #device ch0 #device da0 #device sa0 #device cd0 #device pass0 #options SCSI_REPORT_GEOMETRY pseudo-device pty #pseudo-device speaker #pseudo-device gzip #pseudo-device vn #pseudo-device snp 3 options MSGBUF_SIZE=20480 controller isa0 #options AUTO_EOI_1 #controller pnp0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP="german.iso" device psm0 at atkbdc? irq 12 #options PSM_HOOKAPM #options PSM_RESETAFTERSUSPEND device vga0 at isa? port ? conflicts options VGA_WIDTH90 options VESA pseudo-device splash device sc0 at isa? options MAXCONS=6 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options SC_PIXEL_MODE device npx0 at nexus? port IO_NPX flags 0x0 irq 13 #controller ata0 #device atadisk0 #device atapicd0 controller wdc0 at isa? port IO_WD1 flags 0xe0ffc0ff irq 14 device wd0 at wdc0 drive 0 options IDE_DELAY=2000 device wcd0 controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #options EXTRA_SIO=1 device ed0 #device xe0 #controller snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? port 0x220 irq 5 drq 5 conflicts #device sbmidi0 at isa? port 0x330 #device opl0 at isa? port 0x388 #device mpu0 at isa? port 0x330 device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 #device pca0 at isa? port IO_TIMER1 device apm0 at nexus? device joy0 at isa? port IO_GAME #controller miibus0 controller pci0 controller card0 controller pcic0 at isa? irq 10 controller pcic1 at isa? irq 10 #options PCIC_RESUME_RESET #controller smbus0 #controller intpm0 #device smb0 at smbus? #controller iicbus0 #controller iicbb0 #device ic0 at iicbus? #device iic0 at iicbus? #device iicsmb0 at iicbus? #options AVM_A1_PCMCIA #device isic0 #pseudo-device "i4bq921" #pseudo-device "i4bq931" #pseudo-device "i4b" #pseudo-device "i4btrc" 4 #pseudo-device "i4bctl" #pseudo-device "i4brbch" 4 #pseudo-device "i4btel" 2 #pseudo-device "i4bipr" 4 #options IPR_VJ #pseudo-device "i4bisppp" 4 controller ppbus0 #controller vpo0 at ppbus? device lpt0 at ppbus? device ppi0 at ppbus? device ppc0 at isa? port? irq 7 drq 3 controller uhci0 controller usb0 device ugen0 #device uhid0 #device ukbd0 #device ulpt0 #controller umass0 #device ums0 options HZ=500 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 16:55:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles549.castles.com [208.214.165.113]) by hub.freebsd.org (Postfix) with ESMTP id 7B1A814DBF for ; Sat, 6 Nov 1999 16:55:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA08334; Sat, 6 Nov 1999 16:46:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911070046.QAA08334@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: current@freebsd.org Subject: Re: Old KLD bug.. In-reply-to: Your message of "Sat, 06 Nov 1999 16:38:38 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Nov 1999 16:46:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If I have a KLD module that has a registered dependency on some other > module, > then when I load the forst module it will load the second. > this is all well and good but it ALWYA loads it, > even when it's already in the kernel.. > > if kldstat can see it, then surely the loading modules should be able to > work it out. > > This has been partly fixed in -current (it loads but doesn't link) > but in 3.x it actually links the new one over the existing one, > which is kinda wrong.. > > Is there anyone that understands this stuff that has an idea of ho to fix > this? Yes. See my posts previously on making the distinction between 'file' and 'module'. You've just acquired some new programming talent there; I'm sure I could dope out enough of what was worked out last time we talked about this to give her something to work on. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 17:16:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 86D2F14EF9 for ; Sat, 6 Nov 1999 17:16:44 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA51119; Sat, 6 Nov 1999 17:16:37 -0800 (PST) Date: Sat, 6 Nov 1999 17:16:37 -0800 (PST) From: Julian Elischer To: Mike Smith Cc: current@freebsd.org Subject: Re: Old KLD bug.. In-Reply-To: <199911070046.QAA08334@dingo.cdrom.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 > > Yes. See my posts previously on making the distinction between 'file' > and 'module'. You've just acquired some new programming talent there; > I'm sure I could dope out enough of what was worked out last time we > talked about this to give her something to work on. 8) > As if she doesn't have anything better to do.. :-) Various peopl said they were going to fix it but never did. It's the learning curve that gets me.. I don't grok any of this module/file stuff. I just know it's incredibly broken and stops netgraph from being truely useful. J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 17:19:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id A868514DBF for ; Sat, 6 Nov 1999 17:19:54 -0800 (PST) (envelope-from camel@avias.com) Received: from CAMEL (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.3) with ESMTP id EAA61930 for ; Sun, 7 Nov 1999 04:19:52 +0300 (MSK) (envelope-from camel@avias.com) Date: Sun, 7 Nov 1999 04:15:33 +0300 From: Ilya Naumov X-Mailer: The Bat! (v1.36) S/N F29DEE5D / Educational Reply-To: Ilya Naumov X-Priority: 3 (Normal) Message-ID: <17177.991107@avias.com> To: current@FreeBSD.ORG Subject: SB Live! driver 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 Hello, good news. Creative Labs has decided to make the drivers for their Soundblaster Live open source (see http://opensource.creative.com/). so, are there any plans to port it for FreeBSD? Best regards, Ilya mailto:camel@avias.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 17:29: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 0E98F14CD2 for ; Sat, 6 Nov 1999 17:29:01 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id RAA73684; Sat, 6 Nov 1999 17:27:40 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911070127.RAA73684@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ilya Naumov Cc: current@FreeBSD.ORG Subject: Re: SB Live! driver In-reply-to: Your message of "Sun, 07 Nov 1999 04:15:33 +0300." <17177.991107@avias.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Nov 1999 17:27:40 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Take it up with -multimedia . The gus tarted to talk about it over there. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 17:45:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id C8DA114DD2 for ; Sat, 6 Nov 1999 17:45:51 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id CAA75582; Sun, 7 Nov 1999 02:45:42 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9D1A87.dip.t-dialin.net [62.157.26.135]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id CAA75574; Sun, 7 Nov 1999 02:45:40 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id CAA62358; Sun, 7 Nov 1999 02:45:48 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3824D9BD.1EB36C17@dead-end.net> Date: Sun, 07 Nov 1999 02:45:33 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Peter Wemm , current@FreeBSD.ORG Subject: Re: ESS 1868 driver, again References: <19991106105420.17D231CC6@overcee.netplex.com.au> <3824CAF3.A31B97D5@dead-end.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "D. Rock" wrote: > > > Here my configuration: > > > device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 > > > > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and > > nothing more. You might also try "options PNPBIOS". You are running > > -current, right? > What does "options PNPBIOS" do. I didn't find it in LINT? > > This one doesn't seem to be a PNP device. I set all the resources manually via BIOS. > If it was a PNP device, it shouldn't be detected any longer by the old voxware > driver. > > # pnpinfo > Checking for Plug-n-Play devices... > No Plug-n-Play devices were found Uups, forget my previous post. I added "options PNPBIOS" to my configuration and also only a line "device pcm0", but the problem remains: Probe message: Nov 7 03:34:45 /kernel.new: pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,5 on isa0 And then later, if I try to play something: Nov 7 03:34:45 /kernel.new: sb_dspwr(0xd0) timed out. Nov 7 03:34:45 /kernel.new: sb_dspwr(0xc0) timed out. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 17:53: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 5D38514EB9; Sat, 6 Nov 1999 17:53:04 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id CAA76113; Sun, 7 Nov 1999 02:53:01 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9D1A87.dip.t-dialin.net [62.157.26.135]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id CAA76105; Sun, 7 Nov 1999 02:52:59 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id CAA62386; Sun, 7 Nov 1999 02:53:10 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <3824DB77.9BD2CF0A@dead-end.net> Date: Sun, 07 Nov 1999 02:52:55 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Warner Losh Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: sio working References: <3823540C.AE8ADA4F@dead-end.net> <199910230241.UAA26689@harmony.village.org> <199911061753.KAA22419@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <3823540C.AE8ADA4F@dead-end.net> "D. Rock" writes: > : I tried many different combinations. I disabled the onboard serial devices > : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with > : irq 4 but the only thing I get is > : sio2: configured irq -1071415680 not in bitmap of probed irqs 0 > > That is very odd... Do you have sio2 in your config file? If so just > take it out and see if that helps or hurts (or replace what is there > with "device sio2" As always when you see odd problems like this, > try a make clean && make depend && make in the compile directory > (after reconfiguring). I don't think it will help the current > situation, but it won't hurt. With the latest -current I get a slightly different output: Nov 7 03:34:47 /kernel.new: pccard: card inserted, slot 0 Nov 7 03:34:57 /kernel.new: sio2: irq maps: 0x105 0x105 0x105 0x105 Nov 7 03:34:57 /kernel.new: sio2: probe failed test(s): 0 1 4 6 7 9 Nov 7 03:34:57 pccardd[15]: driver allocation failed for Intelligent(PCMCIA FAX+MODEM): Device not configured How intelligent is pccardd? This card has several config entries, but only the first one contains also possible IRQs, the additional entries only contain I/O ports. So I also tried to use the first one (and disabling the conflicting sio0 in BIOS + kernel config) Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 19:49:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.wa.home.com (ha1.rdc1.wa.home.com [24.0.2.66]) by hub.freebsd.org (Postfix) with ESMTP id 4B33D14BD6 for ; Sat, 6 Nov 1999 19:49:54 -0800 (PST) (envelope-from francis.j.bruening@bigfoot.com) Received: from c583119a ([24.0.55.28]) by mail.rdc1.wa.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19991107034954.GNFT6286.mail.rdc1.wa.home.com@c583119a> for ; Sat, 6 Nov 1999 19:49:54 -0800 From: "Francis J. Bruening" Cc: Subject: RE: SB Live! driver Date: Sat, 6 Nov 1999 19:53:12 -0800 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.2910.0) In-Reply-To: <199911070127.RAA73684@rah.star-gate.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just checked the web-site for a mailing list called freebsd-multimedia. I didn't find it?!? Is the web-site out of date, or did you mean some other mailing list? I too, am very anxious to get the SBLive stuff... thanks in advance. Regards, Francis -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org]On Behalf Of Amancio Hasty Sent: Saturday, November 06, 1999 5:28 PM To: Ilya Naumov Cc: current@freebsd.org Subject: Re: SB Live! driver Hi, Take it up with -multimedia . The gus tarted to talk about it over there. -- Amancio Hasty hasty@rah.star-gate.com 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 Nov 6 19:57:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id C624E14BD6 for ; Sat, 6 Nov 1999 19:57:53 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id TAA74526; Sat, 6 Nov 1999 19:56:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199911070356.TAA74526@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Francis J. Bruening" Cc: current@FreeBSD.ORG Subject: Re: SB Live! driver In-reply-to: Your message of "Sat, 06 Nov 1999 19:53:12 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Nov 1999 19:56:48 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subscribe to : freebsd-multimedia@freebsd.org Have Fun Amancio -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 20: 8:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 0B9DB14DBF for ; Sat, 6 Nov 1999 20:08:51 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA26460 for current@freebsd.org; Sun, 7 Nov 1999 05:08:47 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id EFE5F8711; Sun, 7 Nov 1999 02:01:02 +0100 (CET) Date: Sun, 7 Nov 1999 02:01:02 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: Serious locking problem in CURRENT Message-ID: <19991107020102.A9992@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <199911061929.NAA26145@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199911061929.NAA26145@free.pcs> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jonathan Lemon: > NOTES > Locks are on files, not file descriptors. That is, file descriptors > du- plicated through dup(2) or fork(2) do not result in multiple > instances of a lock, but rather multiple references to a single lock. > If a process holding a lock on a file forks and the child explicitly > unlocks the file, the parent will lose its lock. Right but in Postfix case this is not the case. The "master" process run to check whether Postfix is running or not is definitely NOT a child of the real "master" process. We just have a case where a lock on a given file is not seen at all by another process, thus defeating the whole idea. Locking is broken. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 21:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 45AA214FF9 for ; Sat, 6 Nov 1999 21:38:37 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 783251C03; Sun, 7 Nov 1999 13:38:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "D. Rock" Cc: current@FreeBSD.ORG Subject: Re: ESS 1868 driver, again In-reply-to: Your message of "Sun, 07 Nov 1999 02:45:33 +0100." <3824D9BD.1EB36C17@dead-end.net> Date: Sun, 07 Nov 1999 13:38:36 +0800 From: Peter Wemm Message-Id: <19991107053836.783251C03@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "D. Rock" wrote: > "D. Rock" wrote: > > > > Here my configuration: > > > > device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 > > > > > > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and > > > nothing more. You might also try "options PNPBIOS". You are running > > > -current, right? > > What does "options PNPBIOS" do. I didn't find it in LINT? > > > > This one doesn't seem to be a PNP device. I set all the resources manually via BIOS. > > If it was a PNP device, it shouldn't be detected any longer by the old voxw are > > driver. > > > > # pnpinfo > > Checking for Plug-n-Play devices... > > No Plug-n-Play devices were found > Uups, forget my previous post. > > I added "options PNPBIOS" to my configuration and also only a line "device pc m0", > but the problem remains: > > Probe message: > Nov 7 03:34:45 /kernel.new: pcm0: at port 0x220-0x22f,0x388-0x38b ,0x330-0x331 irq 5 drq 1,5 on isa0 > > And then later, if I try to play something: > Nov 7 03:34:45 /kernel.new: sb_dspwr(0xd0) timed out. > Nov 7 03:34:45 /kernel.new: sb_dspwr(0xc0) timed out. > > Daniel PNPBIOS turns on the interface between the computer and the motherboard bios so that it can obtain all the PNP information for all the motherboard devices. This means we can do PNP-style configuration for motherboard resources (eg: serial, parallel, floppy drive, keyboard, etc etc) As to why the 1869 isn't working for you, that's anybody's guess. You might try posting the 'dmesg' output (not from syslog) and your complete config file, as well as any other pertinant information you can think of. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 22:40:59 1999 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 0096714C11; Sat, 6 Nov 1999 22:40:55 -0800 (PST) (envelope-from imp@harmony.village.org) 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 XAA84253; Sat, 6 Nov 1999 23:40:53 -0700 (MST) (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 XAA03003; Sat, 6 Nov 1999 23:39:55 -0700 (MST) Message-Id: <199911070639.XAA03003@harmony.village.org> To: "D. Rock" Subject: Re: sio working Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 07 Nov 1999 02:52:55 +0100." <3824DB77.9BD2CF0A@dead-end.net> References: <3824DB77.9BD2CF0A@dead-end.net> <3823540C.AE8ADA4F@dead-end.net> <199910230241.UAA26689@harmony.village.org> <199911061753.KAA22419@harmony.village.org> Date: Sat, 06 Nov 1999 23:39:54 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3824DB77.9BD2CF0A@dead-end.net> "D. Rock" writes: : With the latest -current I get a slightly different output: : : Nov 7 03:34:47 /kernel.new: pccard: card inserted, slot 0 : Nov 7 03:34:57 /kernel.new: sio2: irq maps: 0x105 0x105 0x105 0x105 : Nov 7 03:34:57 /kernel.new: sio2: probe failed test(s): 0 1 4 6 7 9 : Nov 7 03:34:57 pccardd[15]: driver allocation failed for Intelligent(PCMCIA FAX+MODEM): Device not configured OK, looks like it failed to probe. At a guess is appears that this card is conflicting with something else, otherwise it wouldn't be failing these probes. : How intelligent is pccardd? This card has several config entries, : but only the first one contains also possible IRQs, the additional : entries only contain I/O ports. So I also tried to use the first one : (and disabling the conflicting sio0 in BIOS + kernel config) pccardd does what you tell it to do. The IRQs in the CIS entries are just hints anyway, pccardd is free to ignore them if it sees fit. They are there to tell the BIOS that "cards of this type are generally mapped to these IRQs, be nice to stupid drivers and map them there please." FreeBSD doesn't have any stupid drivers. :-) However, I don't think the irq issue is your problem. I think that it may be that you are trying to map a serial port to where one might already exist. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 6 22:45:24 1999 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 7038B14C33; Sat, 6 Nov 1999 22:45:18 -0800 (PST) (envelope-from imp@harmony.village.org) 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 XAA84273; Sat, 6 Nov 1999 23:45:17 -0700 (MST) (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 XAA03042; Sat, 6 Nov 1999 23:44:19 -0700 (MST) Message-Id: <199911070644.XAA03042@harmony.village.org> To: "D. Rock" Subject: Re: sio working Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Sun, 07 Nov 1999 01:50:25 +0100." <3824CCD1.C07B6A8@dead-end.net> References: <3824CCD1.C07B6A8@dead-end.net> <3823540C.AE8ADA4F@dead-end.net> <199910230241.UAA26689@harmony.village.org> <199911061753.KAA22419@harmony.village.org> Date: Sat, 06 Nov 1999 23:44:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3824CCD1.C07B6A8@dead-end.net> "D. Rock" writes: : device sio0 at isa? port IO_COM1 flags 0x10 irq 4 : device sio1 at isa? port IO_COM2 irq 3 These look good. IIRC, the kernel I tested with also had: device sio2 at isa? port IO_COM3 irq 5 disabled or device sio2 in it, but I may be misremembering. Just make sure that you use the config entry that gives you a port at 0x3e8, since most laptops have COM1 and COM2 which really cannot be disabled (well, the BIOS says you can disable them, but I've seen a few where the BIOS disabling is broken). : #options EXTRA_SIO=1 This is totally bogus and should never ever be used. Better to remove it completely from your config file, lest the temptation is there to use it. : options HZ=500 I don't think this option will work, but I don't think that's what is breaking things. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message