From owner-freebsd-current Sun Sep 3 3:15: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.vtx.ch (mail.vtx.ch [194.51.92.4]) by hub.freebsd.org (Postfix) with ESMTP id E086537B424; Sun, 3 Sep 2000 03:14:54 -0700 (PDT) Received: from Node01.vtx.ch ([212.147.25.58]) by mail.vtx.ch (Netscape Messaging Server 3.5) with ESMTP id AAA5259; Sun, 3 Sep 2000 12:14:37 +0200 Message-Id: <4.3.2.7.2.20000903120320.00cb7cb0@mail.urbanet.ch> X-Sender: fjaccard@mail.vtx.ch X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 03 Sep 2000 12:13:37 +0200 To: Mike Smith , current@freebsd.org From: Francois E Jaccard Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed Cc: hardware@freebsd.org In-Reply-To: <200009010830.BAA02219@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01/09/2000 10:30, Mike Smith wrote: >I've just committed a driver for the abovementioned RAID adapter families >provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver >will be maintained by Adaptec, with a little help from yours truly if >really necessary. > >With any luck, we should see the complete set of management tools >available from Adaptec shortly to complement this driver, and I'll be >backporting to -stable once I'm certain I haven't broken anything with >this commit, since the driver's already had a long shakedown period. > >Thanks to Adaptec, Mark Salyzyn and Justin Gibbs for again being the right >person in the right place at the right time. > >-- >... every activity meets with opposition, everyone who acts has his >rivals and unfortunately opponents also. But not because people want >to be opponents, rather because the tasks and relationships force >people to take different points of view. [Dr. Fritz Todt] Hi, Is a certain firmware revision needed? I installed my SmartRAID V Millennium and it is not detected. I have: unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources I have a world/kernel made this morning (09/03) I will try to update my firmware to the latest (1.2H). I have 1.2A Thanks! -- Francois Jaccard Public Key: http://keys.pgp.com:11371/pks/lookup?op=get&search=0x11CA35A6 PGP Key Fingerprint:7268 1690 7448 0FE4 0B40 3BD6 E550 CBCE 11CA 35A6 ICQ: 270437 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 3:22:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id F2EB837B42C for ; Sun, 3 Sep 2000 03:21:51 -0700 (PDT) Received: from [212.159.22.154] (helo=alveley.org) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.5) id 13VWuI-0007mJ-00 for current@FreeBSD.org; Sun, 03 Sep 2000 11:21:46 +0100 Message-ID: <39B22639.63285D27@alveley.org> Date: Sun, 03 Sep 2000 11:21:45 +0100 From: "Dampure, Pierre Y." X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: [Fwd: Problems with new PCI bus space implementation?] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forwarded for completeness, since the message I sent yesterday didn't draw any attention... "Dampure, Pierre Y." wrote: > > Doug, > > Prior to yesterday, my last world / kernel rebuild was on August 25th. > Since yesterday, any attempt at generating a kernel results in an image > that: > > 1. Does not recognise my on-board fxp. > 2. Does not recognise my PCI Adaptec 2940UW > > plus maybe some other things, but it's a bit difficult to track > everything on a scrolling screen and I do not have a second PC I could > use as a serial console. > > Because all my disks are SCSI, it is obviously a bit difficult to dig > much further but, as mentioned in a previous message to -current, a > pnpscan -v does detect a SCSI adapter. > > The problem exists whether I use an SMP kernel or not. > > The board is an Intel OR840 (Kitty Hawk) and the attached should > described pretty much everything better than I could (of course, the > dmesg and mptable outputs were generated with my previous kernel) > > Could you please let me know what to try in order to help tracking down > the problem? > > Best Regards, > > PYD > > ------------------------------------------------------------------------ > ##################################################################### > # BLADERUNNER -- Custom kernel configuration, host bladerunner.alveley.org > # > > machine i386 > ident BLADERUNNER > maxusers 32 > makeoptions CONF_CFLAGS=-fno-builtin > options MAXDSIZ="(256*1024*1024)" > options DFLDSIZ="(256*1024*1024)" > options BLKDEV_IOSIZE=8192 > options PQ_NORMALCACHE > options ROOTDEVNAME=\"ufs:da1s1a\" > options RANDOMDEV > > #hints "BLADERUNNER.hints" > > ##################################################################### > # SMP OPTIONS: > > options SMP > options APIC_IO > options NCPU=2 > options NBUS=4 > options NAPIC=1 > options NINTR=43 > > ##################################################################### > # CPU OPTIONS > > cpu I686_CPU > options CPU_FASTER_5X86_FPU > options NO_F00F_HACK > > ##################################################################### > # COMPATIBILITY OPTIONS > > options COMPAT_43 > options COMPAT_LINUX > options SYSVSHM > options SYSVSEM > options SYSVMSG > > ##################################################################### > # DEBUGGING OPTIONS > > options UCONSOLE > options USERCONFIG > options VISUAL_USERCONFIG > > ##################################################################### > # NETWORKING OPTIONS > > options INET > > device ether > device loop 1 > device bpf > device disc > > ##################################################################### > # FILESYSTEM OPTIONS > > options FFS > options MFS > options PROCFS > options FFS_ROOT > options SOFTUPDATES > options FFS_EXTATTR > options QUOTA > > ##################################################################### > # POSIX P1003.1B > > options P1003_1B > options _KPOSIX_PRIORITY_SCHEDULING > options _KPOSIX_VERSION=199309L > > ##################################################################### > # CLOCK OPTIONS > > options HZ=100 > options CLK_CALIBRATION_LOOP > options CLK_USE_TSC_CALIBRATION > > ##################################################################### > # SCSI DEVICES > > device scbus > device da > device sa > device cd > device pass > device pt > > ##################################################################### > # MISCELLANEOUS DEVICES AND OPTIONS > > options MSGBUF_SIZE=40960 > > device pty > device gzip > device vn > device snp > > ##################################################################### > # HARDWARE DEVICE CONFIGURATION > > options AUTO_EOI_1 > options AUTO_EOI_2 > options VESA > options MAXCONS=12 > options SC_DFLT_FONT > makeoptions SC_DFLT_FONT=cp850 > options SC_DISABLE_DDBKEY > options SC_DISABLE_REBOOT > options SC_PIXEL_MODE > options ATA_ENABLE_ATAPI_DMA > options AHC_ALLOW_MEMIO > options PPC_PROBE_CHIPSET > > device isa > device atkbdc 1 > device atkbd > device psm > device vga > device splash > device sc 1 > device npx > device ata > device atadisk > device atapicd > device fdc > device sio > device pci > device ahc > device fxp > device ppc > device ppbus > device lpt > device ppi > device pps > device pcm > device sbc > device midi > device seq > > ------------------------------------------------------------------------ > hint.scbus.0.at="ahc0" > hint.scbus.0.bus="0" > hint.da.0.at="scbus0" > hint.da.0.target="0" > hint.da.0.unit="0" > hint.da.1.at="scbus0" > hint.da.1.target="1" > hint.da.1.unit="0" > hint.da.2.at="scbus0" > hint.da.2.target="2" > hint.da.2.unit="0" > hint.da.3.at="scbus0" > hint.da.3.target="3" > hint.da.3.unit="0" > hint.atkbdc.0.at="isa" > hint.atkbdc.0.port="0x060" > hint.atkbd.0.at="atkbdc" > hint.atkbd.0.irq="1" > hint.psm.0.at="atkbdc" > hint.psm.0.irq="12" > hint.vga.0.at="isa" > hint.sc.0.at="isa" > hint.npx.0.at="nexus" > hint.npx.0.port="0x0F0" > hint.npx.0.flags="0x0" > hint.npx.0.irq="13" > hint.ata.0.at="isa" > hint.ata.0.port="0x1f0" > hint.ata.0.irq="14" > hint.ata.1.at="isa" > hint.ata.1.port="0x170" > hint.ata.1.irq="15" > hint.fdc.0.at="isa" > hint.fdc.0.port="0x3F0" > hint.fdc.0.irq="6" > hint.fdc.0.drq="2" > hint.fd.0.at="fdc0" > hint.fd.0.drive="0" > hint.sio.0.at="isa" > hint.sio.0.port="0x3F8" > hint.sio.0.flags="0x10" > hint.sio.0.irq="4" > hint.ppc.0.at="isa" > hint.ppc.0.irq="7" > > ------------------------------------------------------------------------ > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-CURRENT #0: Fri Aug 25 07:34:31 BST 2000 > toor@bladerunner.alveley.org:/usr/obj/usr/src/sys/BLADERUNNER > Calibrating clock(s) ... TSC clock: 731411839 Hz, i8254 clock: 1193093 Hz > Press a key on the console to abort clock calibration > Calibrating clock(s) ... TSC clock: 731411927 Hz, i8254 clock: 1193093 Hz > Calibrating clock(s) ... TSC clock: 731411866 Hz, i8254 clock: 1193093 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (731.41-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x681 Stepping = 1 > Features=0x383fbff > real memory = 536694784 (524116K bytes) > Physical memory chunk(s): > 0x00001000 - 0x0009efff, 647168 bytes (158 pages) > 0x0038f000 - 0x1ffcafff, 532922368 bytes (130108 pages) > avail memory = 518995968 (506832K bytes) > Programming 24 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > SMP: CPU0 apic_initialize(): > lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170020, at 0xfec00000 > bios32: Found BIOS32 Service Directory header at 0xc00fdb60 > bios32: Entry = 0xfdb70 (c00fdb70) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0xf0000+0xdb91 > Other BIOS signatures found: > ACPI: 000ec370 > Preloaded elf kernel "kernel.good" at 0xc0373000. > nulldev: > random: > mem: > Pentium Pro MTRR support enabled > seq0-63: Midi sequencers. > VESA: information block > 56 45 53 41 00 03 00 01 00 01 01 00 00 00 17 01 > 00 01 00 01 00 01 5b 01 00 01 72 01 00 01 80 01 > 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > VESA: 33 mode(s) found > VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc02d95f7 (1000117) > VESA: 3dfx Interactive, Inc. > VESA: 3dfx Interactive, Inc. Voodoo5 5500 Version 1.00 > SMP: CPU0 bsp_apic_configure(): > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > found-> vendor=0x8086, dev=0x1a21, revid=0x01 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 3, range 32, base bc000000, size 26, enabled > found-> vendor=0x8086, dev=0x1a23, revid=0x01 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=1 secondarybus=1 > found-> vendor=0x8086, dev=0x2418, revid=0x02 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=2 secondarybus=2 > found-> vendor=0x8086, dev=0x2410, revid=0x02 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > found-> vendor=0x8086, dev=0x2411, revid=0x02 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[20]: type 4, range 32, base 00003020, size 4, enabled > Freeing (NOT implemented) redirected PCI irq 10. > found-> vendor=0x8086, dev=0x2412, revid=0x02 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=19 > map[20]: type 4, range 32, base 00003000, size 5, enabled > Freeing (NOT implemented) redirected PCI irq 5. > found-> vendor=0x8086, dev=0x2413, revid=0x02 > class=0c-05-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=b, irq=17 > map[20]: type 4, range 32, base 00007000, size 4, enabled > pci0: on pcib0 > pci0: (vendor=0x8086, dev=0x1a21) at 0.0 > pcib1: at device 1.0 on pci0 > Freeing (NOT implemented) redirected PCI irq 11. > found-> vendor=0x121a, dev=0x0009, revid=0x01 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=16 > map[10]: type 1, range 32, base c4000000, size 26, enabled > map[14]: type 3, range 32, base b0000000, size 27, enabled > map[18]: type 4, range 32, base 00002000, size 8, enabled > pci1: on pcib1 > pci1: <3Dfx model 0009 graphics accelerator> (vendor=0x121a, dev=0x0009) at 0.0 irq 16 > pcib2: at device 30.0 on pci0 > Freeing (NOT implemented) redirected PCI irq 10. > found-> vendor=0x8086, dev=0x1229, revid=0x08 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=19 > map[10]: type 1, range 32, base c0311000, size 12, enabled > map[14]: type 4, range 32, base 00001100, size 6, enabled > map[18]: type 1, range 32, base c0200000, size 20, enabled > Freeing (NOT implemented) redirected PCI irq 11. > found-> vendor=0x9004, dev=0x8178, revid=0x00 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=16 > map[10]: type 4, range 32, base 00001000, size 8, enabled > map[14]: type 1, range 32, base c0310000, size 12, enabled > Freeing (NOT implemented) redirected PCI irq 5. > found-> vendor=0x1102, dev=0x0002, revid=0x07 > class=04-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > intpin=a, irq=17 > map[10]: type 4, range 32, base 00001140, size 5, enabled > found-> vendor=0x1102, dev=0x7002, revid=0x07 > class=09-80-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > map[10]: type 4, range 32, base 00001160, size 3, enabled > Freeing (NOT implemented) redirected PCI irq 9. > found-> vendor=0x1105, dev=0x8300, revid=0x02 > class=04-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=18 > map[10]: type 1, range 32, base c0100000, size 20, enabled > pci2: on pcib2 > fxp0: port 0x1100-0x113f mem 0xc0200000-0xc02fffff,0xc0311000-0xc0311fff irq 19 at device 3.0 on pci2 > fxp0: Ethernet address 00:d0:b7:59:9e:a3 > bpf: fxp0 attached > ahc0: port 0x1000-0x10ff mem 0xc0310000-0xc0310fff irq 16 at device 8.0 on pci2 > ahc0: Reading SEEPROM...done. > ahc0: internal 50 cable not present, internal 68 cable is present > ahc0: external cable not present > ahc0: BIOS eeprom is present > ahc0: High byte termination Enabled > ahc0: Low byte termination Enabled > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc0: Downloading Sequencer Program... 422 instructions downloaded > pcm0: port 0x1140-0x115f irq 17 at device 9.0 on pci2 > emu: setmap (f000, 800), nseg=1, error=0 > emu: setmap (4f000, 1000), nseg=1, error=0 > pcm0: ac97 codec id 0x54524123 > pcm0: ac97 codec features 5 bit master volume, no 3D Stereo Enhancement > emu: setmap (c0f000, 1000), nseg=1, error=0 > emu: setmap (c4f000, 1000), nseg=1, error=0 > emu: setmap (c8f000, 1000), nseg=1, error=0 > emu: setmap (ccf000, 1000), nseg=1, error=0 > pcm: setmap d0f000, 1000; 0xd2b53000 -> d0f000 > pcm: setmap d4f000, 1000; 0xd2b93000 -> d4f000 > pcm: setmap d8f000, 1000; 0xd2bd3000 -> d8f000 > pci2: (vendor=0x1105, dev=0x8300) at 10.0 irq 18 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0x3020-0x302f at device 31.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x3020 > ata0: mask=01 status0=50 status1=ff > ata0: mask=01 status0=00 status1=ff > ata0: devices = 0x4 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x3028 > ata1: mask=03 status0=50 status1=7f > ata1: mask=03 status0=00 status1=7f > ata1: devices = 0x4 > ata1: at 0x170 irq 15 on atapci0 > pci0: (vendor=0x8086, dev=0x2412) at 31.2 irq 19 > pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 17 > ata-: ata0 exists, using next available unit number > ata-: ata1 exists, using next available unit number > Trying Read_Port at 203 > Trying Read_Port at 243 > Trying Read_Port at 283 > Trying Read_Port at 2c3 > Trying Read_Port at 303 > Trying Read_Port at 343 > Trying Read_Port at 383 > Trying Read_Port at 3c3 > sc-: sc0 exists, using next available unit number > vga-: vga0 exists, using next available unit number > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 > psm0: current command byte:0047 > kbdc: TEST_AUX_PORT status:0000 > kbdc: RESET_AUX return code:00fa > kbdc: RESET_AUX status:00aa > kbdc: RESET_AUX ID:0000 > psm: status 00 02 64 > psm: status 90 03 3c > psm: status 90 03 3c > psm: status 90 03 3c > psm: data 08 00 00 > psm: status 00 00 28 > psm: status 00 02 64 > psm: data 08 00 00 > psm: status 00 02 64 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons > psm0: config:00000000, flags:00000000, packet size:3 > psm0: syncmask:c0, syncbits:00 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > fb0: vga0, vga, type:VGA (5), flags:0x700ff > fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 > fb0: init mode:24, bios mode:3, current mode:24 > fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k > VGA parameters upon power-up > 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > VGA parameters in BIOS for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > EGA/VGA parameters to be used for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > sc0: on isa0 > sc0: VGA <12 virtual consoles, flags=0x200> > sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) > ata2 failed to probe at port 0x1f0 irq 14 on isa0 > ata3 failed to probe at port 0x170 irq 15 on isa0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: irq maps: 0xc061 0xc071 0xc061 0xc061 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > ppc0: parallel port found at 0x378 > ppc0: using extended I/O port range > ppc0: ECP SPP ECP+EPP SPP > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > pps0: on ppbus0 > sc1: no video adapter is found. > sc1: failed to probe on isa0 > vga1: failed to probe on isa0 > isa_probe_children: probing PnP devices > SMP: enabled INTs: 1, 4, 6, 7, 12, 14, 15, 16, 17, 19, apic_imen: 0x00f42f2d > BIOS Geometries: > 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors > 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors > 2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors > 3:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors > 0 accounted for > Device configuration finished. > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via IOAPIC #0 intpin 2 > bpf: ds0 attached > bpf: lo0 attached > Linux-ELF exec handler installed > SMP: AP CPU #1 Launched! > SMP: CPU1 apic_initialize(): > lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff > ata0-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 > ata0-master: success setting WDMA2 on ICH chip > acd0: CDROM drive at ata0 as master > acd0: read 5500KB/s (5500KB/s), 128KB buffer, WDMA2 > acd0: Reads: CD-R, CD-RW, CD-DA, packet > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked, lock protected > ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 > ata1-master: success setting WDMA2 on ICH chip > acd1: DVD-ROM drive at ata1 as master > acd1: read 1722KB/s (4134KB/s), 512KB buffer, WDMA2 > acd1: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet > acd1: Audio: play, 256 volume levels > acd1: Mechanism: ejectable tray > acd1: Medium: no/blank disc inside, unlocked > Waiting 2 seconds for SCSI devices to settle > (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > Sending WDTR! > ahc0: target 0 using 16bit transfers > ahc0: target 0 synchronous at 20.0MHz, offset = 0x8 > Sending SDTR! > Sending WDTR! > ahc0: target 1 using 16bit transfers > ahc0: target 1 synchronous at 20.0MHz, offset = 0x8 > Sending SDTR! > (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe4:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0 > (probe4:ahc0:0:4:0): Invalid field in CDB sks:c8,1 > ahc0: target 6 using 16bit transfers > ahc0: target 6 synchronous at 10.0MHz, offset = 0x8 > ahc0: target 6 using asynchronous transfers > ahc0: target 6 synchronous at 10.0MHz, offset = 0x8 > ahc0: target 1 using asynchronous transfers > ahc0: target 1 synchronous at 20.0MHz, offset = 0x8 > ahc0: target 0 using asynchronous transfers > ahc0: target 0 synchronous at 20.0MHz, offset = 0x8 > ahc0: target 4 synchronous at 4.0MHz, offset = 0xf > ahc0: target 3 using 16bit transfers > ahc0: target 3 synchronous at 20.0MHz, offset = 0x8 > ahc0: target 2 using 16bit transfers > ahc0: target 2 synchronous at 20.0MHz, offset = 0x8 > ahc0: target 1 using asynchronous transfers > ahc0: target 1 synchronous at 20.0MHz, offset = 0x8 > ahc0: target 0 using asynchronous transfers > ahc0: target 0 synchronous at 20.0MHz, offset = 0x8 > Creating DISK cd0 > Creating DISK da0 > Creating DISK da1 > Creating DISK da2 > Creating DISK da3 > pass0 at ahc0 bus 0 target 0 lun 0 > pass0: Fixed Direct Access SCSI-2 device > pass0: Serial Number LA354303 > pass0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > pass1 at ahc0 bus 0 target 1 lun 0 > pass1: Fixed Direct Access SCSI-2 device > pass1: Serial Number LA356407 > pass1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > pass2 at ahc0 bus 0 target 2 lun 0 > pass2: Fixed Direct Access SCSI-2 device > pass2: Serial Number 3AL0199F00001934HCYQ > pass2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > pass3 at ahc0 bus 0 target 3 lun 0 > pass3: Fixed Direct Access SCSI-2 device > pass3: Serial Number 3AL04FFS000019411YK4 > pass3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > pass4 at ahc0 bus 0 target 4 lun 0 > pass4: Removable CD-ROM SCSI-2 device > pass4: 4.237MB/s transfers (4.237MHz, offset 15) > pass5 at ahc0 bus 0 target 6 lun 0 > pass5: Removable Sequential Access SCSI-2 device > pass5: Serial Number CX806S0324 > pass5: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: Serial Number CX806S0324 > sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > Mounting root from ufs:/dev/da1s1a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: Serial Number LA354303 > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) > da2 at ahc0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: Serial Number 3AL0199F00001934HCYQ > da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da2: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) > da3 at ahc0 bus 0 target 3 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: Serial Number 3AL04FFS000019411YK4 > da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da3: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: Serial Number LA356407 > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da1: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) > da1s1: type 0xa5, start 0, end = 17773499, size 17773500 : OK > start_init: trying /sbin/init > da2s1: type 0xa5, start 0, end = 17773523, size 17773524 : OK > da3s1: type 0xa5, start 0, end = 17773523, size 17773524 : OK > splash: image decoder found: green_saver > (cd0:ahc0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (cd0:ahc0:0:4:0): NOT READY asc:3a,0 > (cd0:ahc0:0:4:0): Medium not present > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 4.237MB/s transfers (4.237MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > ------------------------------------------------------------------------ > > =============================================================================== > > MPTable, version 2.0.15 > > ------------------------------------------------------------------------------- > > MP Floating Pointer Structure: > > location: BIOS > physical address: 0x000f16f0 > signature: '_MP_' > length: 16 bytes > version: 1.4 > checksum: 0xfa > mode: PIC > > ------------------------------------------------------------------------------- > > MP Config Table Header: > > physical address: 0x000f1700 > signature: 'PCMP' > base table length: 484 > version: 1.4 > checksum: 0x00 > OEM ID: 'INTEL ' > Product ID: 'Kitty Hawk ' > OEM table pointer: 0x00000000 > OEM table size: 0 > entry count: 52 > local APIC address: 0xfee00000 > extended table length: 0 > extended table checksum: 0 > > ------------------------------------------------------------------------------- > > MP Config Base Table Entries: > > -- > Processors: APIC ID Version State Family Model Step Flags > 1 0x11 BSP, usable 6 8 1 0x383fbff > 0 0x11 AP, usable 6 8 1 0x387fbff > -- > Bus: Bus ID Type > 0 PCI > 1 PCI > 2 PCI > 3 ISA > -- > I/O APICs: APIC ID Version State Address > 2 0x20 usable 0xfec00000 > -- > I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# > ExtINT active-hi edge 3 0 2 0 > INT active-hi edge 3 0 2 2 > INT active-hi edge 3 1 2 1 > INT active-hi edge 3 3 2 3 > INT active-hi edge 3 4 2 4 > INT active-lo level 3 5 2 5 > INT active-hi edge 3 6 2 6 > INT active-hi edge 3 7 2 7 > INT active-hi edge 3 8 2 8 > INT active-lo level 3 9 2 9 > INT active-lo level 3 10 2 10 > INT active-lo level 3 11 2 11 > INT active-hi edge 3 12 2 12 > INT active-hi edge 3 13 2 13 > INT active-hi edge 3 14 2 14 > INT active-hi edge 3 15 2 15 > INT active-lo level 0 31:A 2 16 > INT active-lo level 0 31:B 2 17 > INT active-lo level 0 31:C 2 18 > INT active-lo level 0 31:D 2 19 > INT active-lo level 1 0:A 2 16 > INT active-lo level 1 0:B 2 17 > INT active-lo level 2 3:A 2 19 > INT active-lo level 2 8:A 2 16 > INT active-lo level 2 8:B 2 17 > INT active-lo level 2 8:C 2 18 > INT active-lo level 2 8:D 2 19 > INT active-lo level 2 9:A 2 17 > INT active-lo level 2 9:B 2 18 > INT active-lo level 2 9:C 2 19 > INT active-lo level 2 9:D 2 16 > INT active-lo level 2 10:A 2 18 > INT active-lo level 2 10:B 2 19 > INT active-lo level 2 10:C 2 16 > INT active-lo level 2 10:D 2 17 > INT active-lo level 2 11:A 2 19 > INT active-lo level 2 11:B 2 16 > INT active-lo level 2 11:C 2 17 > INT active-lo level 2 11:D 2 18 > INT active-lo level 2 4:A 2 17 > INT active-lo level 2 4:B 2 18 > INT active-lo level 2 4:C 2 19 > INT active-lo level 2 4:D 2 16 > -- > Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# > ExtINT active-hi edge 3 0 255 0 > NMI active-hi edge 0 0:A 255 1 > > ------------------------------------------------------------------------------- > > # SMP kernel config file options: > > # Required: > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > > # Optional (built-in defaults will work in most cases): > #options NCPU=2 # number of CPUs > #options NBUS=4 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=43 # number of INTs > > =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 3:44:10 2000 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 B3C3937B423; Sun, 3 Sep 2000 03:44:03 -0700 (PDT) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.0/8.9.3) id e83Ai0w77414; Sun, 3 Sep 2000 17:44:00 +0700 (NOVST) (envelope-from nnd) Date: Sun, 3 Sep 2000 17:44:00 +0700 (NOVST) Message-Id: <200009031044.e83Ai0w77414@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@FreeBSD.ORG Cc: Peter Wemm Subject: Re: cvs commit: src/sys/sys libkern.h In-Reply-To: <200009030604.XAA33902@freefall.freebsd.org> X-Newsgroups: itfs.freebsd.cvs.all User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009030604.XAA33902@freefall.freebsd.org> you wrote: > peter 2000/09/02 23:04:17 PDT > > Modified files: > sys/sys libkern.h > Log: > libkern.h now internally uses the bzero() definition from sys/systm.h. > This is kinda important since the bzero symbol on i386 is not a function > but a function pointer.. If memset() tried to call it as though it were > a function, things would be less than satisfactory. In reality though > this was not an actual problem and just caused compile warnings. But now lines 40 and 41 of 'src/sys/sys/libkern.h' ver. 1.22 are: #include #include 'srs/sys/types.h' contains (at lines 117 and 118) macros 'minor' and 'najor' definitions for which are also in 'src/sys/sys/systm.h' (at lines 331 and 332). This results (at least) in 'src/lib/libstand' brokeness due to 'make buildworld'. Please repair the damage ;-) N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 4:33:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 9E78637B423 for ; Sun, 3 Sep 2000 04:33:44 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e83BXUG35361; Sun, 3 Sep 2000 04:33:30 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200009031133.e83BXUG35361@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tor.Egge@fast.no Cc: sheldonh@uunet.co.za, current@FreeBSD.ORG Subject: Re: panic: pmap_enter: attempted pmap_enter on 4MB page In-Reply-To: <200009030234.EAA84082@midten.fast.no> Date: Sun, 03 Sep 2000 04:33:30 -0700 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tor.Egge@fast.no wrote: > > > pci50: physical bus=-1061225984 > > > > A little dubious, I think. Below is the dmesg(8) output from > > kernel.old, my last good kernel built yesterday, booted with ``boot > > -v''. > > > > The enclosed patch might be relevant. I got similar problems without > it. A more comprehensive fix is in -current now. ivars shouldn't have been used there at all. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 8: 9:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A3C4B37B422 for ; Sun, 3 Sep 2000 08:09:30 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id LAA15370 for ; Sun, 3 Sep 2000 11:09:44 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sun, 3 Sep 2000 11:09:44 -0400 (EDT) From: Adam To: current@freebsd.org Subject: sb16 doesnt probe from snd_driver 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 was under the impression you could just drop the necessary hints for a non pnp card in /boot/device.hints and kldload snd_driver and should expect to see pcm and sbc be detected by the kernel and work. Is this not the case? Using the same hints and compiling pcm and sbc into the kernel works just fine, even with devfs. It just doesn't attach anything with the sound modules. Is there any more info that I could provide that would help clear up the problem? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 12:13:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id BA33637B42C; Sun, 3 Sep 2000 12:13:16 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA00797; Sun, 3 Sep 2000 12:28:00 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009031928.MAA00797@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Francois E Jaccard Cc: current@freebsd.org, hardware@freebsd.org Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed In-reply-to: Your message of "Sun, 03 Sep 2000 12:13:37 +0200." <4.3.2.7.2.20000903120320.00cb7cb0@mail.urbanet.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Sep 2000 12:28:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 01/09/2000 10:30, Mike Smith wrote: > > >I've just committed a driver for the abovementioned RAID adapter families > >provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver > >will be maintained by Adaptec, with a little help from yours truly if > >really necessary. > > > >With any luck, we should see the complete set of management tools > >available from Adaptec shortly to complement this driver, and I'll be > >backporting to -stable once I'm certain I haven't broken anything with > >this commit, since the driver's already had a long shakedown period. > > > >Thanks to Adaptec, Mark Salyzyn and Justin Gibbs for again being the right > >person in the right place at the right time. > > > >-- > >... every activity meets with opposition, everyone who acts has his > >rivals and unfortunately opponents also. But not because people want > >to be opponents, rather because the tasks and relationships force > >people to take different points of view. [Dr. Fritz Todt] > > Hi, > Is a certain firmware revision needed? Not AFAIK. > I installed my SmartRAID V Millennium and it is not detected. I have one of them here, and it works OK for me. What's the actual product number off the back of the card? > I will try to update my firmware to the latest (1.2H). I have 1.2A Can you also send me the output of 'pciconf -l'? Thanks. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 12:27:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from guy.asimware.com (guy.asimware.com [199.185.255.10]) by hub.freebsd.org (Postfix) with ESMTP id 7B71B37B423; Sun, 3 Sep 2000 12:27:42 -0700 (PDT) Received: from localhost (gscott@localhost) by guy.asimware.com (8.9.3/8.9.3) with ESMTP id PAA50917; Sun, 3 Sep 2000 15:16:28 -0400 (EDT) (envelope-from gscott@asimware.com) Date: Sun, 3 Sep 2000 15:16:27 -0400 (EDT) From: Greg Scott To: Mike Smith Cc: current@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed In-Reply-To: <200009010830.BAA02219@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just committed a driver for the abovementioned RAID adapter families > provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver > will be maintained by Adaptec, with a little help from yours truly if > really necessary. Think there might be any chance of getting i2o support in something > 3.2 of FreeBSD? > With any luck, we should see the complete set of management tools > available from Adaptec shortly to complement this driver, and I'll be > backporting to -stable once I'm certain I haven't broken anything with > this commit, since the driver's already had a long shakedown period. I would kill for some management tools for my Adaptec 3200S (which just replaced the DPT 1564 we had) Closed on Monday September 4th for the Labour Day Holiday. -- Greg Scott | Asimware Innovations Inc. Network Administrator | 600 Upper Wellington St, Unit #D Website Co-Ordinator | Hamilton, Ontario, Canada L9A 3P9 greg.scott@asimware.com | Phone: +1-905-575-1042 | Fax: +1-905-575-0095 | http://www.asimware.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 14:57:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id 7420237B424 for ; Sun, 3 Sep 2000 14:57:55 -0700 (PDT) Received: by manatee.mammalia.org (Postfix, from userid 1000) id 8480F11CE05; Sun, 3 Sep 2000 14:57:54 -0700 (PDT) Date: Sun, 3 Sep 2000 14:57:54 -0700 From: R Joseph Wright To: freebsd-current Subject: xl driver Message-ID: <20000903145754.A1691@mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After my latest cvsup/make world, I have this happening at boot: Sep 3 13:24:26 manatee /kernel: xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 Sep 3 13:24:26 manatee /kernel: xl0: Ethernet address: 00:60:97:58:92:e5 Sep 3 13:24:26 manatee /kernel: xl0: selecting 10baseT transceiver, half duplex Sep 3 13:24:26 manatee /kernel: xl1: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 Sep 3 13:24:26 manatee /kernel: xl1: couldn't map ports/memory Sep 3 13:24:26 manatee /kernel: device_probe_and_attach: xl1 attach returned 6 I only have one ethernet card, so I'm confused why it's trying to set up two. Joseph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 15: 2:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id 2188537B422 for ; Sun, 3 Sep 2000 15:02:26 -0700 (PDT) Received: by manatee.mammalia.org (Postfix, from userid 1000) id E4B1611CE05; Sun, 3 Sep 2000 15:02:25 -0700 (PDT) Date: Sun, 3 Sep 2000 15:02:25 -0700 From: R Joseph Wright To: freebsd-current Subject: perl built twice? Message-ID: <20000903150225.B1691@mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While doing a make world, I noticed that perl is built early on. When I came back later, I saw perl being built again along with all the other gnu.usr.bin stuff. Was I tripping or did perl really get built twice? Joseph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 15:35:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 5DE1037B424 for ; Sun, 3 Sep 2000 15:35:14 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13ViLk-000D1h-00; Mon, 04 Sep 2000 00:34:52 +0200 Date: Mon, 4 Sep 2000 00:34:52 +0200 From: Neil Blakey-Milner To: R Joseph Wright Cc: freebsd-current Subject: Re: perl built twice? Message-ID: <20000904003452.A50055@mithrandr.moria.org> References: <20000903150225.B1691@mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000903150225.B1691@mammalia.org>; from rjoseph@mammalia.org on Sun, Sep 03, 2000 at 03:02:25PM -0700 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun 2000-09-03 (15:02), R Joseph Wright wrote: > While doing a make world, I noticed that perl is built early on. When I > came back later, I saw perl being built again along with all the other > gnu.usr.bin stuff. Was I tripping or did perl really get built twice? libperl and miniperl are built early on, in the 'build-tools' section (I think). Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 18:39:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1660A37B422 for ; Sun, 3 Sep 2000 18:39:28 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA19732; Sun, 3 Sep 2000 19:39:26 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA53833; Sun, 3 Sep 2000 19:38:50 -0600 (MDT) Message-Id: <200009040138.TAA53833@harmony.village.org> To: R Joseph Wright Subject: Re: xl driver Cc: freebsd-current In-reply-to: Your message of "Sun, 03 Sep 2000 14:57:54 PDT." <20000903145754.A1691@mammalia.org> References: <20000903145754.A1691@mammalia.org> Date: Sun, 03 Sep 2000 19:38:50 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000903145754.A1691@mammalia.org> R Joseph Wright writes: : Sep 3 13:24:26 manatee /kernel: xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 : Sep 3 13:24:26 manatee /kernel: xl1: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 Looks like your pci bus is getting probed twice! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 19:32: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 77C8B37B42C; Sun, 3 Sep 2000 19:32:01 -0700 (PDT) Received: by kbtfw.kubota.co.jp; id LAA16503; Mon, 4 Sep 2000 11:31:49 +0900 (JST) Received: from unknown(133.253.122.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma016382; Mon, 4 Sep 00 11:31:39 +0900 Received: from jkpc15.tk.kubota.co.jp ([133.253.157.145]) by kbtmx.eto.kubota.co.jp (8.9.3+3.2W/3.7W) with ESMTP id LAA02075; Mon, 4 Sep 2000 11:31:39 +0900 (JST) Received: from localhost (localhost.tk.kubota.co.jp [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.11.0/3.7W-02/21/99) with ESMTP id e842VYU00505; Mon, 4 Sep 2000 11:31:34 +0900 (JST) To: wpaul@FreeBSD.org Cc: freebsd-current@FreeBSD.org, haro@tk.kubota.co.jp Subject: Re: cvs commit: src/sys/pci if_dc.c In-Reply-To: <200009012359.QAA45279@freefall.freebsd.org> References: <200009012359.QAA45279@freefall.freebsd.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000904113134P.haro@tk.kubota.co.jp> Date: Mon, 04 Sep 2000 11:31:34 +0900 From: Munehiro Matsuda X-Dispatcher: imput version 20000228(IM140) Lines: 37 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Bill, After the following commit, my system fail to connect to network. If I backout, seems to work again. Any comments appreciated. FYI, dmesg output here: dc0: port 0xe880-0xe8ff mem 0xfebfec00-0xfebfefff irq 5 at device 5.0 on pci0 dc0: Ethernet address: 00:00:4c:73:16:8a miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ::wpaul 2000/09/01 16:59:54 PDT :: :: Modified files: :: sys/pci if_dc.c :: Log: :: Make the blinkylights on non-MII 21143 cards work. We need to enable :: the link and activity LED control bits in CSR15 in order for the :: controller to drive the LEDs correctly. This was largely done for the :: ZNYX multiport cards, but should also work with the DEC DE500-BA :: and other non-MII cards. :: :: Revision Changes Path :: 1.21 +13 -2 src/sys/pci/if_dc.c Thank you, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 19:40:40 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 68CD737B422; Sun, 3 Sep 2000 19:40:39 -0700 (PDT) Subject: Re: cvs commit: src/sys/pci if_dc.c In-Reply-To: <20000904113134P.haro@tk.kubota.co.jp> from Munehiro Matsuda at "Sep 4, 2000 11:31:34 am" To: haro@tk.kubota.co.jp (Munehiro Matsuda) Date: Sun, 3 Sep 2000 19:40:39 -0700 (PDT) Cc: freebsd-current@FreeBSD.org, haro@tk.kubota.co.jp X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000904024039.68CD737B422@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello Bill, > > After the following commit, my system fail to connect to network. > If I backout, seems to work again. Any comments appreciated. No no no. *You* are the one who's supposed to make the comments. Like exactly what card do you have (make/model)? Exactly what speed and duplex mode are you using? (10mbps? 100mbps? full duplex? half duplex?) What ifconfig command do you use to bring up the interface? What kind of hub/switch/whatever is the card connected to? You know, all the stuff that I can't figure out for myself because I can't see your computer from way over here. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 20:40:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 0001137B422; Sun, 3 Sep 2000 20:40:24 -0700 (PDT) Received: by kbtfw.kubota.co.jp; id MAA19468; Mon, 4 Sep 2000 12:40:10 +0900 (JST) Received: from unknown(133.253.122.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma019201; Mon, 4 Sep 00 12:39:56 +0900 Received: from jkpc15.tk.kubota.co.jp ([133.253.157.145]) by kbtmx.eto.kubota.co.jp (8.9.3+3.2W/3.7W) with ESMTP id MAA09922; Mon, 4 Sep 2000 12:39:55 +0900 (JST) Received: from localhost (localhost.tk.kubota.co.jp [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.11.0/3.7W-02/21/99) with ESMTP id e843dpF00458; Mon, 4 Sep 2000 12:39:51 +0900 (JST) To: wpaul@FreeBSD.ORG Cc: freebsd-current@FreeBSD.org Subject: Re: cvs commit: src/sys/pci if_dc.c In-Reply-To: <20000904024039.68CD737B422@hub.freebsd.org> References: <20000904113134P.haro@tk.kubota.co.jp> <20000904024039.68CD737B422@hub.freebsd.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000904123950M.haro@tk.kubota.co.jp> Date: Mon, 04 Sep 2000 12:39:50 +0900 From: Munehiro Matsuda X-Dispatcher: imput version 20000228(IM140) Lines: 57 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: wpaul@FreeBSD.ORG (Bill Paul) Date: Sun, 3 Sep 2000 19:40:39 -0700 (PDT) ::> After the following commit, my system fail to connect to network. ::> If I backout, seems to work again. Any comments appreciated. :: ::No no no. *You* are the one who's supposed to make the comments. ::Like exactly what card do you have (make/model)? Exactly what speed ::and duplex mode are you using? (10mbps? 100mbps? full duplex? half ::duplex?) What ifconfig command do you use to bring up the interface? ::What kind of hub/switch/whatever is the card connected to? You know, ::all the stuff that I can't figure out for myself because I can't see ::your computer from way over here. :: ::-Bill Hello Bill, I'm sorry about that. Here's some information that I can gather: 1. The Intel 21143 chips is intergrated in NEC VersaPro NoteBook PC. No LED to indicate the network activity are available. 2. It is connected to 10BaseT Hub (HP 28688B) at half duplex. 3. dmesg output: dc0: port 0xe880-0xe8ff mem 0xfebfec00-0xfebfefff irq 5 at device 5.0 on pci0 dc0: Ethernet address: 00:00:4c:73:16:8a miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto 4. When connection's ok (w/ if_dc.c: rev 1.20): dc0: flags=8843 mtu 1500 inet 133.253.157.145 netmask 0xffffff00 broadcast 133.253.157.255 inet6 fe80::200:4cff:fe73:168a%dc0 prefixlen 64 scopeid 0x1 ether 00:00:4c:73:16:8a media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX none 5. When connection's no good (w/ if_dc.c: rev 1.21): dc0: flags=8843 mtu 1500 inet 133.253.157.145 netmask 0xffffff00 broadcast 133.253.157.255 inet6 fe80::200:4cff:fe73:168a%dc0 prefixlen 64 scopeid 0x1 ether 00:00:4c:73:16:8a media: autoselect (none) status: no carrier supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 100baseTX none It seems that there's no negotiation done with the Hub at all. Hope this helps, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 3 21:45:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 3A56137B423 for ; Sun, 3 Sep 2000 21:45:51 -0700 (PDT) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA08400; Mon, 4 Sep 2000 00:45:45 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA28863; Mon, 4 Sep 2000 00:45:44 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA28859; Mon, 4 Sep 2000 00:45:44 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Mon, 4 Sep 2000 00:45:44 -0400 (EDT) From: Kenneth Wayne Culver To: Warner Losh Cc: R Joseph Wright , freebsd-current Subject: Re: xl driver In-Reply-To: <200009040138.TAA53833@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG the same thing is happening to me, only my pci bus is getting probed 3 times. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 3 Sep 2000, Warner Losh wrote: > In message <20000903145754.A1691@mammalia.org> R Joseph Wright writes: > : Sep 3 13:24:26 manatee /kernel: xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 > : Sep 3 13:24:26 manatee /kernel: xl1: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 > > Looks like your pci bus is getting probed twice! > > Warner > > > 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 Sun Sep 3 22:31:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from amonduul.ecn.ou.edu (amonduul.ecn.ou.edu [129.15.119.201]) by hub.freebsd.org (Postfix) with ESMTP id C1ECE37B422 for ; Sun, 3 Sep 2000 22:31:22 -0700 (PDT) Received: from servalan.servalan.com (27215 bytes) by amonduul.ecn.ou.edu via rsmtp with P:bsmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Mon, 4 Sep 2000 00:28:03 -0500 (CDT) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Apr-4) Received: from localhost (26638 bytes) by servalan.servalan.com via sendmail with P:stdio/R:smart_host/T:batch_smtp (sender: ) (ident using unix) id for ; Sun, 3 Sep 2000 23:40:22 -0500 (CDT) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-10) Message-Id: Date: Sun, 3 Sep 2000 23:40:22 -0500 (CDT) From: rmtodd@servalan.servalan.com (Richard Todd) To: freebsd-current@freebsd.org Subject: Dual probing of PCI-connected hardware (was Re: xl driver Newsgroups: servalan.mailinglist.fbsd-current References: <20000903145754.A1691@mammalia.org> <200009040138.TAA53833@harmony.village.org> X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In servalan.mailinglist.fbsd-current you write: >In message <20000903145754.A1691@mammalia.org> R Joseph Wright writes: >: Sep 3 13:24:26 manatee /kernel: xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 >: Sep 3 13:24:26 manatee /kernel: xl1: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 >Looks like your pci bus is getting probed twice! >Warner I've been seeing similar oddities too. Nothing crippling, but it is a little disconcerting to see the machine think you have twice as many SCSI controllers and ethernets as you actually have. This is with kernel src grabbed earlier today, i.e. after Peter Wemm's most recent fixes. Note how the kernel thinks it sees an fxp1 and an ahc2/3 as well as an ata2/3, but fails on the allocation of resources/IRQs for those devices, since they're already allocated to the "real" instances of the fxp, ahc0/1, ata0/1 devices. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #36: Sun Sep 3 18:54:17 CDT 2000 rmtodd@ichotolot.servalan.com:/usr/src/sys/compile/ICHOTOLOTSMP Calibrating clock(s) ... TSC clock: 400853210 Hz, i8254 clock: 1193016 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x653 Stepping = 3 Features=0x183fbff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00739000 - 0x07ff7fff, 126611456 bytes (30911 pages) avail memory = 123305984 (120416K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00fdb50 bios32: Entry = 0xfdb60 (c00fdb60) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xdb81 pnpbios: Found PnP BIOS data at 0xc00f72e0 pnpbios: Entry = f0000:6984 Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel "kernel" at 0xc071d000. random: nulldev: mem: Pentium Pro MTRR support enabled Creating DISK md0 md0: Malloc disk Math emulator present SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pcib-: pcib0 exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: physical bus=0 found-> vendor=0x8086, dev=0x71a0, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base f8000000, size 26, enabled found-> vendor=0x8086, dev=0x71a1, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=19 map[20]: type 4, range 32, base 0000ef80, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 4, range 32, base 00000440, size 4, enabled found-> vendor=0x1011, dev=0x0024, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=2 secondarybus=2 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=19 map[10]: type 3, range 32, base fc4ff000, size 12, enabled map[14]: type 4, range 32, base 0000ef40, size 5, enabled map[18]: type 1, range 32, base fea00000, size 20, enabled Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 4, range 32, base 0000e400, size 8, enabled map[14]: type 1, range 32, base febfe000, size 12, enabled Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=16 map[10]: type 4, range 32, base 0000e800, size 8, enabled map[14]: type 1, range 32, base febff000, size 12, enabled pci0: on pcib0 pci0: (vendor=0x8086, dev=0x71a0) at 0.0 pcib2: at device 1.0 on pci0 pci1: physical bus=1 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x10de, dev=0x0020, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base fd000000, size 24, enabled map[14]: type 3, range 32, base f3000000, size 24, enabled pci1: on pcib2 pci1: (vendor=0x10de, dev=0x0020) at 0.0 irq 16 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=24 status1=24 ata0: mask=03 status0=14 status1=14 ata0: devices = 0x0 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=03 status0=0e status1=0e ata1: mask=03 status0=2d status1=2d ata1: devices = 0x0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xef80-0xef9f irq 19 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Timecounter "PIIX" frequency 3579545 Hz pci0: (vendor=0x8086, dev=0x7113) at 7.3 pcib3: at device 16.0 on pci0 pci2: physical bus=2 pci2: on pcib3 fxp0: port 0xef40-0xef5f mem 0xfea00000-0xfeafffff,0xfc4ff000-0xfc4fffff irq 19 at device 17.0 on pci0 using shared irq19. fxp0: Ethernet address 00:e0:81:10:47:b2 bpf: fxp0 attached ahc0: port 0xe400-0xe4ff mem 0xfebfe000-0xfebfefff irq 16 at device 18.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable not present, internal 68 cable not present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: High byte termination Enabled ahc0: Low byte termination Enabled ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc0: Downloading Sequencer Program... 409 instructions downloaded ahc1: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 16 at device 18.1 on pci0 ahc1: Reading SEEPROM...done. ahc1: internal 50 cable not present, internal 68 cable not present ahc1: external cable not present ahc1: BIOS eeprom is present ahc1: High byte termination Enabled ahc1: Low byte termination Enabled ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs ahc1: Downloading Sequencer Program... 409 instructions downloaded using shared irq16. pcib1: on motherboard pci-: pci1 exists, using next available unit number pci3: physical bus=0 found-> vendor=0x8086, dev=0x71a0, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base f8000000, size 26, enabled found-> vendor=0x8086, dev=0x71a1, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=19 map[20]: type 4, range 32, base 0000ef80, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 4, range 32, base 00000440, size 4, enabled found-> vendor=0x1011, dev=0x0024, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=2 secondarybus=2 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=19 map[10]: type 3, range 32, base fc4ff000, size 12, enabled map[14]: type 4, range 32, base 0000ef40, size 5, enabled map[18]: type 1, range 32, base fea00000, size 20, enabled Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 4, range 32, base 0000e400, size 8, enabled map[14]: type 1, range 32, base febfe000, size 12, enabled Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=16 map[10]: type 4, range 32, base 0000e800, size 8, enabled map[14]: type 1, range 32, base febff000, size 12, enabled pci3: on pcib1 pci3: (vendor=0x8086, dev=0x71a0) at 0.0 pcib4: at device 1.0 on pci3 pci4: physical bus=1 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x10de, dev=0x0020, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base fd000000, size 24, enabled map[14]: type 3, range 32, base f3000000, size 24, enabled pci4: on pcib4 pci4: (vendor=0x10de, dev=0x0020) at 0.0 irq 16 isab1: at device 7.0 on pci3 atapci1: port 0xffa0-0xffaf at device 7.1 on pci3 atapci1: Busmastering DMA not configured ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number ata2: probe allocation failed ata3: probe allocation failed uhci1: port 0xef80-0xef9f irq 19 at device 7.2 on pci3 uhci1: Could not map ports device_probe_and_attach: uhci1 attach returned 6 Timecounter "PIIX" frequency 3579545 Hz pci3: (vendor=0x8086, dev=0x7113) at 7.3 pcib5: at device 16.0 on pci3 pci5: physical bus=2 pci5: on pcib5 fxp1: port 0xef40-0xef5f mem 0xfea00000-0xfeafffff,0xfc4ff000-0xfc4fffff irq 19 at device 17.0 on pci3 fxp1: could not map memory device_probe_and_attach: fxp1 attach returned 6 ahc2: port 0xe400-0xe4ff mem 0xfebfe000-0xfebfefff irq 16 at device 18.0 on pci3 ahc2: can't allocate register resources device_probe_and_attach: ahc2 attach returned 12 ahc3: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 16 at device 18.1 on pci3 ahc3: can't allocate register resources device_probe_and_attach: ahc3 attach returned 12 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number Trying Read_Port at 203 CTL0043: start dependant CTL0043: adding irq mask 0x20 CTL0043: adding dma mask 0x2 CTL0043: adding dma mask 0x8 CTL0043: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0043: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0043: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: adding io range 0x300-0x331, size=0x2, align=0x10 CTL0043: adding io range 0x388-0x397, size=0x4, align=0x4 CTL0043: start dependant CTL0043: adding irq mask 0x6a0 CTL0043: adding dma mask 0xb CTL0043: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0043: end dependant CTL7005: start dependant CTL7005: adding io range 0x201-0x201, size=0x1, align=0x1 CTL7005: start dependant CTL7005: adding io range 0x200-0x20f, size=0x1, align=0x1 CTL7005: end dependant ex_isa_identify() pnpbios: 15 devices, largest 194 bytes PNP0c01: adding fixed memory32 range 0-0x9fbff, size=0x9fc00 PNP0c01: adding fixed memory32 range 0x9fc00-0x9ffff, size=0x400 PNP0c01: adding fixed memory32 range 0xe0000-0xfffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: adding fixed memory32 range 0xfec00000-0xfec00fff, size=0x1000 PNP0c01: adding fixed memory32 range 0xfee00000-0xfee00fff, size=0x1000 PNP0c01: adding fixed memory32 range 0xfffc0000-0xffffffff, size=0x40000 PNP0c01: end config pnpbios: handle 0 device ID PNP0c01 (010cd041) PNP0200: adding dma mask 0x10 PNP0200: adding fixed io range 0-0xf, size=0x10, align=0x1 PNP0200: adding fixed io range 0x80-0x90, size=0x11, align=0x1 PNP0200: adding fixed io range 0x94-0x9f, size=0xc, align=0x1 PNP0200: adding fixed io range 0xc0-0xde, size=0x1f, align=0x1 PNP0200: end config pnpbios: handle 2 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding fixed io range 0x40-0x43, size=0x4, align=0x1 PNP0100: end config pnpbios: handle 3 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding fixed io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: end config pnpbios: handle 4 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding fixed io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding fixed io range 0x64-0x64, size=0x1, align=0x1 PNP0303: end config pnpbios: handle 5 device ID PNP0303 (0303d041) PNP0800: adding fixed io range 0x61-0x61, size=0x1, align=0x1 PNP0800: end config pnpbios: handle 6 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding fixed io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: end config pnpbios: handle 7 device ID PNP0c04 (040cd041) PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0c02: adding io range 0x10-0x1f, size=0x10, align=0x1 PNP0c02: adding io range 0x22-0x3f, size=0x1e, align=0x1 PNP0c02: adding io range 0x50-0x52, size=0x3, align=0x1 PNP0c02: adding io range 0x72-0x77, size=0x6, align=0x1 PNP0c02: adding io range 0x91-0x93, size=0x3, align=0x1 PNP0c02: adding io range 0xa2-0xbe, size=0x1d, align=0x1 PNP0c02: adding io range 0x400-0x43f, size=0x40, align=0x1 PNP0c02: adding io range 0x440-0x44f, size=0x10, align=0x1 PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: end config pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0c02: adding io range 0x290-0x297, size=0x8, align=0x1 PNP0c02: end config pnpbios: handle 9 device ID PNP0c02 (020cd041) PNP0a03: end config pnpbios: handle 10 device ID PNP0a03 (030ad041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 PNP0501: end config pnpbios: handle 11 device ID PNP0501 (0105d041) PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 PNP0501: adding io range 0-0xffffffff, size=0, align=0x8 PNP0501: adding irq mask 0x8 PNP0501: adding dma mask 00 PNP0501: end config pnpbios: handle 12 device ID PNP0501 (0105d041) PNP0400: adding io range 0x378-0x37f, size=0x8, align=0x8 PNP0400: adding io range 0-0xffffffff, size=0, align=0x8 PNP0400: adding irq mask 0x80 PNP0400: adding dma mask 00 PNP0400: end config pnpbios: handle 13 device ID PNP0400 (0004d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 14 device ID PNP0700 (0007d041) sc-: sc0 exists, using next available unit number vga-: vga0 exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fe0 failed to probe at port 0x300 on isa0 adv0 failed to probe at port 0x330 on isa0 aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0 failed to probe at port 0x134-0x137 on isa0 aic0 failed to probe at port 0x140-0x15f on isa0 ata4 failed to probe at port 0x1f0 irq 14 on isa0 ata5 failed to probe at port 0x170 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x330 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x334 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x230 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x234 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x130 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x134 bt0 failed to probe at port 0x134-0x137 on isa0 cs0 failed to probe at port 0x300-0x31f on isa0 ed0 failed to probe at port 0x280-0x29f iomem 0xd8000 irq 10 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ie0 failed to probe at port 0x300 iomem 0xd0000 irq 10 on isa0 le0 failed to probe at port 0x300 iomem 0xd0000 irq 5 on isa0 Vendor Specific Word = ffff lnc0 failed to probe at port 0x280 irq 10 drq 0 on isa0 pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 plip0: on ppbus0 bpf: lp0 attached lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x63 0x73 0x63 0x63 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x63 0x6b 0x63 0x63 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) sn0 failed to probe at port 0x300-0x30f irq 10 on isa0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff vt0 failed to probe on isa0 sc1: no video adapter is found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 sbc0: setting card to irq 5, drq 1, 3 pcm0: on sbc0 pcm: setmap 1a000, 2000; 0xc7a5f000 -> 1a000 pcm: setmap 1c000, 2000; 0xc7a61000 -> 1c000 adv1: Invalid baseport of 0x201 specified. Nearest valid baseport is 0x210. Failing probe. unknown: failed to probe at port 0x201 on isa0 adv1: Invalid baseport of 0x0 specified. Nearest valid baseport is 0x100. Failing probe. adv1: Invalid baseport of 0x40 specified. Nearest valid baseport is 0x100. Failing probe. adv1: Invalid baseport of 0x70 specified. Nearest valid baseport is 0x100. Failing probe. unknown: can't assign resources unknown: at port 0x60 on isa0 adv1: Invalid baseport of 0x61 specified. Nearest valid baseport is 0x100. Failing probe. unknown: failed to probe at port 0x61 on isa0 adv1: Invalid baseport of 0xf0 specified. Nearest valid baseport is 0x100. Failing probe. adv1: Invalid baseport of 0x4d0 specified. Nearest valid baseport is 0x330. Failing probe. adv1: Invalid baseport of 0x290 specified. Nearest valid baseport is 0x330. Failing probe. unknown: can't assign resources unknown: at port 0x3f8-0x3ff on isa0 unknown: can't assign resources unknown: at port 0x2f8-0x2ff on isa0 unknown: can't assign resources unknown: at port 0x378-0x37f on isa0 unknown: can't assign resources unknown: at port 0x3f0-0x3f5 on isa0 SMP: enabled INTs: 1, 3, 4, 5, 6, 7, 14, 15, 16, 19, apic_imen: 0x00f63f05 BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 bpf: faith0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached bpf: ppp0 attached new masks: bio 6808c040, tty 630000ba, net 670800ba IPsec: Initialized Security Association Processing. Waiting 15 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff (probe0:ahc0:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe0:ahc0:0:0:0): ILLEGAL REQUEST asc:24,0 (probe0:ahc0:0:0:0): Invalid field in CDB sks:c8,1 (probe3:ahc0:0:3:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe3:ahc0:0:3:0): ILLEGAL REQUEST asc:24,0 (probe3:ahc0:0:3:0): Invalid field in CDB ahc0: target 0 synchronous at 10.0MHz, offset = 0xf ahc0: target 3 synchronous at 20.0MHz, offset = 0xf ahc1: target 6 using 16bit transfers ahc1: target 6 synchronous at 20.0MHz, offset = 0x8 Creating DISK cd0 Creating DISK da0 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Removable Sequential Access SCSI-2 device pass0: 10.000MB/s transfers (10.000MHz, offset 15) pass1 at ahc0 bus 0 target 3 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 20.000MB/s transfers (20.000MHz, offset 15) pass2 at ahc1 bus 0 target 6 lun 0 pass2: Fixed Direct Access SCSI-3 device pass2: Serial Number 369910730471 pass2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da0 at ahc1 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number 369910730471 da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) Mounting root from ufs:/dev/da0s2a da0s1: type 0x6, start 63, end = 1590434, size 1590372 : OK da0s2: type 0xa5, start 1590435, end = 17928539, size 16338105 : OK WARNING: / was not properly dismounted start_init: trying /sbin/init cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: cd present [237919 x 2048 byte records] bpf: tun0 attached pid 95 (savecore), uid 0: exited on signal 10 (core dumped) splash: image decoder found: green_saver Linux-ELF exec handler installed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 0:26:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C5EAF37B423 for ; Mon, 4 Sep 2000 00:26:43 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA61974; Mon, 4 Sep 2000 09:27:23 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009040727.JAA61974@freebsd.dk> Subject: Re: Tagged queuing for ATA drives, patches up for testing In-Reply-To: <20000831172847.B49721@zippy> from Alex Zepeda at "Aug 31, 2000 05:28:47 pm" To: jazepeda@pacbell.net (Alex Zepeda) Date: Mon, 4 Sep 2000 09:27:23 +0200 (CEST) Cc: 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 Alex Zepeda wrote: > On Thu, Aug 31, 2000 at 01:58:46PM +0200, Soren Schmidt wrote: > > > Support for master/slave combinations, and ATA/ATAPI ditto is being > > worked on, but this requires a controller with support for the > > "auto nop" functionality. Which of the many different controllers > > supports this is unknown at this time, but HPT controllers has > > the needed functionality, and should be a safe bet. > > > > It seems that the DJNA series of IBM disks has some problems > > with tagged queueing, but at least the DPTA and DTLA series > > are known to work. The older DTTA series has not been tested > > yet. > > So does anyone know of any other combo that might work well? I've had > nothing but trouble with my HighPoint 366 based board (have I mentioned I > think Siig makes awful products?) in two different motherbords and with > any OS I've tried it with (hell Win98 thought it was a SCSI adapter...). > I've got a somewhat older 13gb WD Caviar (claims to support ATA66) and a > 30gp Deskstar DTLA. I'm tempted to try out a Promise ATA 100 board... Hmm, Two of my main machines here run off SIIG HPT366 based boards, I've newer ever had any problems with those, but the WD disk of yours is probably to blaim, what exact model is 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 Mon Sep 4 1:21: 0 2000 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 988F637B423 for ; Mon, 4 Sep 2000 01:20:56 -0700 (PDT) Received: from maccullagh.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 4 Sep 2000 09:20:49 +0100 (BST) Date: Mon, 4 Sep 2000 09:20:48 +0100 From: David Malone To: Warner Losh Cc: R Joseph Wright , freebsd-current Subject: Re: xl driver Message-ID: <20000904092048.A42249@maccullagh.maths.tcd.ie> References: <20000903145754.A1691@mammalia.org> <200009040138.TAA53833@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009040138.TAA53833@harmony.village.org>; from imp@village.org on Sun, Sep 03, 2000 at 07:38:50PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 03, 2000 at 07:38:50PM -0600, Warner Losh wrote: > In message <20000903145754.A1691@mammalia.org> R Joseph Wright writes: > : Sep 3 13:24:26 manatee /kernel: xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 > : Sep 3 13:24:26 manatee /kernel: xl1: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 > > Looks like your pci bus is getting probed twice! This happened to me when I turned on ACPI support - infact it thought I had 3 PCI busses when I only had one! I haven't had time to look into it yet though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 1:38:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 5CE2837B422 for ; Mon, 4 Sep 2000 01:38:38 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e848cZr15729; Mon, 4 Sep 2000 17:38:35 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: dwmalone@maths.tcd.ie Cc: imp@village.org, rjoseph@mammalia.org, freebsd-current@FreeBSD.ORG Subject: Re: xl driver In-Reply-To: <20000904092048.A42249@maccullagh.maths.tcd.ie> References: <20000903145754.A1691@mammalia.org> <200009040138.TAA53833@harmony.village.org> <20000904092048.A42249@maccullagh.maths.tcd.ie> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000904173811Z.iwasaki@jp.FreeBSD.org> Date: Mon, 04 Sep 2000 17:38:11 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 10 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : Sep 3 13:24:26 manatee /kernel: xl0: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 > > : Sep 3 13:24:26 manatee /kernel: xl1: <3Com 3c900-COMBO Etherlink XL> port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 > > > > Looks like your pci bus is getting probed twice! > > This happened to me when I turned on ACPI support - infact it > thought I had 3 PCI busses when I only had one! I haven't had time > to look into it yet though. Hmmm, can I have your full output of dmesg? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 3:45:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 67E2237B423 for ; Mon, 4 Sep 2000 03:45:51 -0700 (PDT) Received: from zip.noc.uunet.co.za ([196.31.2.162] helo=nwl.fw.uunet.co.za) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13Vtl6-0002mX-00; Mon, 04 Sep 2000 12:45:48 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id MAA20029; Mon, 4 Sep 2000 12:45:45 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 19878; Mon Sep 4 12:44:58 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13VtkI-000AJa-00; Mon, 04 Sep 2000 12:44:58 +0200 From: Sheldon Hearn To: Tony Fleisher Cc: freebsd-current@freebsd.org Subject: Re: problems with /usr/bin/awk In-reply-to: Your message of "Mon, 21 Aug 2000 19:17:31 MST." Date: Mon, 04 Sep 2000 12:44:58 +0200 Message-ID: <39653.968064298@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 21 Aug 2000 19:17:31 MST, Tony Fleisher wrote: > awk: ./guile-snarf.awk:17: (FILENAME=- FNR=9680) fatal error: internal > error > Abort trap - core dumped > *** Error code 1 Hi Tony, Aharon Robbins has come back with an "official patch" that fixes the problem. It has been committed in HEAD as: src/contrib/awk/field.c rev 1.6 src/contrib/awk/builtin.c rev 1.9 As I understand the situation, the problem does not exist in RELENG_4. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 7:22:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 6F83537B422 for ; Mon, 4 Sep 2000 07:22:54 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e84EMpr19578 for ; Mon, 4 Sep 2000 23:22:51 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: freebsd-current@freebsd.org Subject: CFR: New pseudo timer device driver for power management events X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000904232226G.iwasaki@jp.FreeBSD.org> Date: Mon, 04 Sep 2000 23:22:26 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 26 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm working on ACPI and thinking of sharing the related code with other power management subsystem (currently apm) rather than having duplicated code. Updating timer/clock before and after sleeping, is my first target. My idea is that create new pseudo timer device driver for power management events in i386/isa/pmtimer.c which should be statically wired and always only one instance, then move apm_default_{suspend|resume} in i386/apm/apm.c into pmtimer as device_{suspend|resume} method. Firstly I thought that this should be moved to i386/isa/clock.c and define device_{suspend|resume} method of attimer. But I noticed that it's for PnP and we cannot guarantee that there is always only one device instance and device_{suspend|resume} is executed once per event. I put the code and diffs at http://people.freebsd.org/~iwasaki/acpi/pmtimer.c http://people.freebsd.org/~iwasaki/acpi/pmtimer.diff Please review them, I'll commit this change this weekend. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 7:34: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id B17ED37B424; Mon, 4 Sep 2000 07:33:59 -0700 (PDT) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id B86649A10; Mon, 4 Sep 2000 16:33:53 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200009010830.BAA02219@mass.osd.bsdi.com> References: <200009010830.BAA02219@mass.osd.bsdi.com> Date: Mon, 4 Sep 2000 16:33:19 +0200 To: Mike Smith , current@FreeBSD.ORG From: Brad Knowles Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed Cc: hardware@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:30 AM -0700 2000/9/1, Mike Smith wrote: > I've just committed a driver for the abovementioned RAID adapter families > provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver > will be maintained by Adaptec, with a little help from yours truly if > really necessary. Excellent! Any ideas when this might be MFC'd to -STABLE? > With any luck, we should see the complete set of management tools > available from Adaptec shortly to complement this driver, and I'll be > backporting to -stable once I'm certain I haven't broken anything with > this commit, since the driver's already had a long shakedown period. Awesome! You mean that we won't have to reboot into DOS (or PROM) to manage reconfigure this thing? Cool! > Thanks to Adaptec, Mark Salyzyn and Justin Gibbs for again being the right > person in the right place at the right time. And thanks to you, for all your hard work that you've put in to make all the various RAID adaptors function correctly under FreeBSD! We couldn't do it without you, Mike! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 9:40:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 58D9F37B42C; Mon, 4 Sep 2000 09:40:18 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13VzOO-0007tW-00; Mon, 04 Sep 2000 10:46:44 -0600 Message-ID: <39B3D1F0.15F1157C@softweyr.com> Date: Mon, 04 Sep 2000 10:46:40 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Neil Blakey-Milner Cc: Robert Watson , Thomas David Rivers , freebsd-current@freebsd.org Subject: Re: AFS. References: <200008301530.LAA27160@lakes.dignus.com> <20000830201222.A95887@mithrandr.moria.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > > I think it is probably sufficiently free. It doesn't sufficiently cover > the use of small bits of its code, though. It is a non-terminating > license. I've studied it carefully a couple of times, and haven't found anything at all wrong with it. It is about the simplest license of this ilk possible, and covers all the bases. The use of small bits of code from IBMPSL sources is covered by the "prepare derivative works of" clause in section 2a, and is explicitly allowed. > Neil (who wonders to which list one should redirect license talk) To Brett Glass? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 9:41:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 5EF2937B42C; Mon, 4 Sep 2000 09:41:16 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e84GfEN53061; Mon, 4 Sep 2000 18:41:14 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org, hackers@freebsd.org Subject: looking for "microuptime went backwards" victims... From: Poul-Henning Kamp Date: Mon, 04 Sep 2000 18:41:14 +0200 Message-ID: <53059.968085674@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for the remaining victims of the dreaded "microuptime went backwards" message. If you can reliably reproduce the problem, please contact me, so we can arrange for some very detailed tracing to try to find out what exactly is going on. I have not been able to trigger the problem in my lab in a long time. If you see the message only occationally, please try the attached patch and let me know if this changes the picture. The patch is not meant as a fix, but it might reduce the impact of this condition considerably when it happens. Basically by reducing the width of the timecounter the magnitude of the hit we take if the timecounter goes backwards is reduced from about an hour to approx 110msec. Reducing the width to less than 17 bits starts to run the risk of ambiguity due to clock rollover. This patch may not be safe with PCAUDIO. Poul-Henning Index: clock.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v retrieving revision 1.155 diff -u -r1.155 clock.c --- clock.c 2000/07/30 21:05:22 1.155 +++ clock.c 2000/09/04 16:34:16 @@ -194,7 +194,7 @@ static struct timecounter i8254_timecounter = { i8254_get_timecount, /* get_timecount */ 0, /* no poll_pps */ - ~0u, /* counter_mask */ + 0x1ffff, /* counter_mask */ 0, /* frequency */ "i8254" /* name */ }; -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 12:10:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from Den.BOFH.Halifax.NS.Ca (Den.BOFH.Halifax.ns.Ca [129.173.46.183]) by hub.freebsd.org (Postfix) with ESMTP id F296B37B422 for ; Mon, 4 Sep 2000 12:10:39 -0700 (PDT) Received: (from hume@localhost) by Den.BOFH.Halifax.NS.Ca (8.9.3+Sun/8.9.1) id QAA08880 for current@freebsd.org; Mon, 4 Sep 2000 16:10:33 -0300 (ADT) From: Brandon Hume Message-Id: <200009041910.QAA08880@Den.BOFH.Halifax.NS.Ca> Subject: AIC-7890 problems with kernel build To: current@freebsd.org Date: Mon, 4 Sep 2000 16:10:33 -0300 (ADT) X-Mailer: ELM [version 2.4ME+ PL42 (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 had this problem for the past couple of days (I went a while between updates of my kernel since I was busy installing a new disk and moving OSes around). Just after the "waiting for SCSI devices to settle" message, I'll get a number of SCB errors (which I don't have written down, unfortunately), and then eventually a panic. This is with ACPI enabled... if I don't enable ACPI, it will proceed immediately to the panic. The panic is a "Trap 12: page fault in kernel mode". with "interrupt mask: cam <- SMP: XXX", and "Stopped at ahc_match_scb + 0x9d movl 0x2c(%eax), %eax" I apologize for the exceedingly lameassed manner of this bug report, I don't have serial ports enabled on this machine and don't know of a more effective means to get the details. With the kernel debugger, I get a stack trace similar to the following: ahc_match_scb(c0e7e000, c0e8e230, 0, 41, 0, 9, 1) ahc_search_qinfifo(c0e7e000, 0, 41, 0, 9, 1, 0, 1) ahc_timeout(c0e8e168, 40000000, 0, 0, ffffffff) softclock(0, 18, c02b0010, 10, ffffffff) doreti_swi() I can dig up my kernel config and a "functional" dmesg as soon as I get back via the saved good kernel. For the record, this is via the onboard AIC-7890 on a Tyan Thunder/100 dual processor board running an SMP kernel. -- Brandon Hume - hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 13: 8:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 894E837B422; Mon, 4 Sep 2000 13:08:06 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA05249; Mon, 4 Sep 2000 13:22:47 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009042022.NAA05249@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: current@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed In-reply-to: Your message of "Mon, 04 Sep 2000 16:33:19 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Sep 2000 13:22:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've just committed a driver for the abovementioned RAID adapter families > > provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver > > will be maintained by Adaptec, with a little help from yours truly if > > really necessary. > > Excellent! Any ideas when this might be MFC'd to -STABLE? I'd like to hear a few more success stories first (only one so far) from people using the kit to add the driver to their 4.x systems. With all the breakage in -current's PCI support at the moment, I don't expect to hear too many people there reporting on it just yet. > > With any luck, we should see the complete set of management tools > > available from Adaptec shortly to complement this driver, and I'll be > > backporting to -stable once I'm certain I haven't broken anything with > > this commit, since the driver's already had a long shakedown period. > > Awesome! You mean that we won't have to reboot into DOS (or > PROM) to manage reconfigure this thing? Cool! That's the general plan. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 13:15:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 0F13337B422 for ; Mon, 4 Sep 2000 13:15:53 -0700 (PDT) Received: from teabag.demon.co.uk ([193.237.4.110]) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13W2el-000LKg-0Y for freebsd-current@freebsd.org; Mon, 4 Sep 2000 21:15:52 +0100 Received: from localhost (cbh@localhost) by teabag.demon.co.uk (8.11.0/8.9.3) with ESMTP id e84KEh560891 for ; Mon, 4 Sep 2000 21:14:51 +0100 (BST) (envelope-from cbh@teabag.demon.co.uk) Date: Mon, 4 Sep 2000 21:14:43 +0100 (BST) From: Chris Hedley X-Sender: cbh@teabag.cbhnet To: freebsd-current@freebsd.org Subject: Re: AIC-7890 problems with kernel build In-Reply-To: <200009041910.QAA08880@Den.BOFH.Halifax.NS.Ca> 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, 4 Sep 2000, Brandon Hume wrote: > Just after the "waiting for SCSI devices to settle" message, I'll get a > number of SCB errors (which I don't have written down, unfortunately), and > then eventually a panic. This is with ACPI enabled... if I don't enable > ACPI, it will proceed immediately to the panic. Sounds similar to what I'm getting; after a boot I get a load of the following: ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) ahc1: ahc_intr - referenced scb not valid during SELTO (31, 139) followed by a panic: (probe0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0xb panic: Waiting List inconsistency. SCB index == 255, yet numscbs == 20 (Being a technophobe I decided to write these down rather than dig out a breakout box to capture the serial port output!) Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) Lots of other blurb about "can't allocate register resources" for just about anything on the PCI bus, as I recall. Chris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 13:29:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom3-041.telepath.com [216.14.3.41]) by hub.freebsd.org (Postfix) with SMTP id 8B20337B424 for ; Mon, 4 Sep 2000 13:29:37 -0700 (PDT) Received: (qmail 42852 invoked by uid 100); 4 Sep 2000 20:29:00 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14772.1548.469715.468768@guru.mired.org> Date: Mon, 4 Sep 2000 15:29:00 -0500 (CDT) To: freebsd-current@FreeBSD.ORG Subject: Re: AIC-7890 problems with kernel build In-Reply-To: References: <200009041910.QAA08880@Den.BOFH.Halifax.NS.Ca> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Hedley writes: > On Mon, 4 Sep 2000, Brandon Hume wrote: > > Just after the "waiting for SCSI devices to settle" message, I'll get a > > number of SCB errors (which I don't have written down, unfortunately), and > > then eventually a panic. This is with ACPI enabled... if I don't enable > > ACPI, it will proceed immediately to the panic. > Sounds similar to what I'm getting; after a boot I get a load of the > following: I'll add a third to that. The SCB errors don't seem to depend on ACPI; they didn't happen on the update on Sept 1, but did on Sept 2. > Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 > controller. I started getting this after my 29th Aug update, although > this was a few days since the last working version I compiled (dmesg says > the 24th so, er, I guess that's when it was) Not quite the same. I've got a SuperMicro SMP Xeon system with an onboard 7890. ; Mon, 4 Sep 2000 13:37:39 -0700 (PDT) Received: (from hume@localhost) by Den.BOFH.Halifax.NS.Ca (8.9.3+Sun/8.9.1) id RAA09087; Mon, 4 Sep 2000 17:37:37 -0300 (ADT) From: Brandon Hume Message-Id: <200009042037.RAA09087@Den.BOFH.Halifax.NS.Ca> Subject: Re: AIC-7890 problems with kernel build In-Reply-To: from Chris Hedley at "Sep 4, 2000 9:14:43 pm" To: cbh@teabag.demon.co.uk (Chris Hedley) Date: Mon, 4 Sep 2000 17:37:31 -0300 (ADT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL42 (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 Mon, 4 Sep 2000, Brandon Hume wrote: > Sounds similar to what I'm getting; after a boot I get a load of the > following: > > ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) That's what I get... although I get SELTO (31, 0) > Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 Mine's a GX, with a 7895 also (not 7890, oops...) > controller. I started getting this after my 29th Aug update, although > this was a few days since the last working version I compiled (dmesg says > the 24th so, er, I guess that's when it was) My working kernel was built 1 PM ADT on the 26th, so there's a slightly narrower window. > Lots of other blurb about "can't allocate register resources" for just > about anything on the PCI bus, as I recall. I think that's a double-probe problem mentioned on the commit list. Dunno if it would be related. Here's the kernel config and functional-dmesg I promised. dmesg: --- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Aug 26 13:00:17 ADT 2000 root@Jashugan.BOFH.Halifax.ns.Ca:/build/src/sys/compile/JASHUGAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 134086656 (130944K bytes) avail memory = 126570496 (123604K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "JASHUGAN" at 0xc03e1000. Pentium Pro MTRR support enabled md0: Malloc disk apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 16 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: port 0xef80-0xef9f irq 19 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: Logitech, Inc. Camera, rev 1.00/1.00, addr 2 uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 3 uhub1: 4 ports with 4 removable, bus powered ukbd0: Sun Microsystems Type 6 USB, rev 1.00/1.01, addr 4, iclass 3/1 kbd1 at ukbd0 ums0: Logitech USB-PS/2 Mouse, rev 1.00/1.10, addr 5, iclass 3/1 ums0: 3 buttons and Z dir. Timecounter "PIIX" frequency 3579545 Hz pci0: at 7.3 pcib3: at device 16.0 on pci0 pci2: on pcib3 pci2: <3Dfx Voodoo 2 graphics accelerator> at 4.0 pci2: (vendor=0x11d1, dev=0x01f7) at 5.0 irq 17 fxp0: port 0xef40-0xef5f mem 0xfea00000-0xfeafffff,0xfd2ff000-0xfd2fffff irq 19 at device 17.0 on pci0 fxp0: Ethernet address 00:e0:81:10:24:79 ahc0: port 0xe400-0xe4ff mem 0xfebfe000-0xfebfefff irq 16 at device 18.0 on pci0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 16 at device 18.1 on pci0 ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs pcm0: port 0xef20-0xef3f irq 16 at device 19.0 on pci0 pcib1: on motherboard pci3: on pcib1 isa0: too many memory ranges fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IPsec: Initialized Security Association Processing. IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled SMP: AP CPU #1 Launched! acd0: DVD-ROM at ata0-master using WDMA2 Waiting 7 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s2a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 5.000MB/s transfers (5.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15) da2: 1955MB (4004219 512 byte sectors: 255H 63S/T 249C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da1: 2157MB (4419464 512 byte sectors: 255H 63S/T 275C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) --- And, of course, the kernel config... a fair amount of crap still not trimmed out, but the only difference between this config and the one used to build the functional kernel is apm commented out and ACPI added, which I've already tried reversing without much difference. --- ident JASHUGAN machine i386 maxusers 32 cpu I686_CPU options CPU_FASTER_5X86_FPU options NO_F00F_HACK options DDB hints "JASHUGAN.hints" #Default places to look for devices. options INET #InterNETworking options INET6 #IPv6 communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_NOSERVER # Jashugan is not an NFS server 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=7500 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev options RANDOMDEV # entropy device # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): options NCPU=2 # number of CPUs #options NBUS=8 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices options AHC_ALLOW_MEMIO # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 device atkbd device psm device vga # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 options SC_NORM_ATTR="(FG_LIGHTGREY|BG_BLACK)" options SC_NORM_REV_ATTR="(FG_BLACK|BG_LIGHTGREY)" options SC_KERNEL_CONS_ATTR="(FG_WHITE|BG_BLUE)" options SC_KERNEL_CONS_REV_ATTR="(FG_BLUE|BG_LIGHTGREY)" # Floating point support - do not disable. device npx # Power management support (see LINT for more options) #device apm device acpi options ACPI_DEBUG options AML_DEBUG device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. device loop # Network loopback device ether # Ethernet support device sl # Kernel SLIP device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio # Diamond Rio 500 MP3 player options IPFILTER options IPFILTER_LOG device pcm --- -- Brandon Hume - hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 13:38:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 8DB8C37B423 for ; Mon, 4 Sep 2000 13:38:29 -0700 (PDT) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id NAA87701 for ; Mon, 4 Sep 2000 13:38:23 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.11.0/8.11.0) with ESMTP id e84KcNZ31285 for ; Mon, 4 Sep 2000 13:38:23 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) From: Nick Sayer X-Authentication-Warning: medusa.kfu.com: ssmail owned process doing -bs Received: by icarus.kfu.com (8.9.3//ident-1.0) id NAA20320; Mon, 4 Sep 2000 13:38:23 -0700 (PDT) Date: Mon, 4 Sep 2000 13:38:23 -0700 (PDT) Message-Id: <200009042038.NAA20320@icarus.kfu.com> To: freebsd-current@freebsd.org Subject: Include OpenSSL root CA cert list? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If something like this already exists, then my searches must have missed it. In order to improve the usefulness of the openssl installation, I would like to suggest that a collection of CA root certs be added to the base installation and perhaps even referenced by the conf file. Included with the mod-ssl package there is a file called ca-bundle.crt, which purports to be the certificate list that comes with Netscape Navigator/Communicator. I propose to include this file under /usr/share, perhaps as /usr/share/openssl/ca-bundle.crt. For those unfamiliar, SSL security works by starting with a list of trusted certificates. This list serves a similar purpose as the DNS root cache -- it serves as a starting place for establishing the trustworthiness of SSL certificates. The roots are trusted, and a path of authority can be traced down from the root certs through intermediate certificates finally to a cert that might be used for either an SSL server or S/MIME mail signing or code signing or whatever. By incorporating this file, certificate verification becomes possible merely with a default installation of FreeBSD. And there's no reason that the list should stay static, although I would suggest it would be up to us to come up with some sort of criteria for determining the level of security required for an arbitrary CA to be deemed "trustworthy". What does everyone think? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 13:42:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4BD2A37B423 for ; Mon, 4 Sep 2000 13:42:10 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e84Kg4N54386; Mon, 4 Sep 2000 22:42:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nick Sayer Cc: freebsd-current@FreeBSD.ORG Subject: Re: Include OpenSSL root CA cert list? In-Reply-To: Your message of "Mon, 04 Sep 2000 13:38:23 PDT." <200009042038.NAA20320@icarus.kfu.com> Date: Mon, 04 Sep 2000 22:42:04 +0200 Message-ID: <54384.968100124@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009042038.NAA20320@icarus.kfu.com>, Nick Sayer writes: > >If something like this already exists, then my searches must have >missed it. > >In order to improve the usefulness of the openssl installation, >I would like to suggest that a collection of CA root certs be >added to the base installation and perhaps even referenced by >the conf file. > > >What does everyone think? Make it a port... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 14:12: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 250FB37B422 for ; Mon, 4 Sep 2000 14:12:00 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e84LBur06840; Tue, 5 Sep 2000 06:11:57 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: hume@Den.BOFH.Halifax.NS.Ca Cc: cbh@teabag.demon.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: AIC-7890 problems with kernel build In-Reply-To: <200009042037.RAA09087@Den.BOFH.Halifax.NS.Ca> References: <200009042037.RAA09087@Den.BOFH.Halifax.NS.Ca> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000905061131G.iwasaki@jp.FreeBSD.org> Date: Tue, 05 Sep 2000 06:11:31 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > And, of course, the kernel config... a fair amount of crap still not trimmed > out, but the only difference between this config and the one used to build > the functional kernel is apm commented out and ACPI added, which I've already > tried reversing without much difference. All I can say is that acpi is initilized after pcib and its children are attached so I don't think ACPI code affects PCI stuff... > # Power management support (see LINT for more options) > #device apm > device acpi Could you disable acpi and try again to make the problem clearer? Without `device acpi' line in your kernel config file, any ACPI code isn't compiled in your kernel. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 14:26:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from Den.BOFH.Halifax.NS.Ca (Den.BOFH.Halifax.ns.Ca [129.173.46.183]) by hub.freebsd.org (Postfix) with ESMTP id A38D637B422 for ; Mon, 4 Sep 2000 14:26:37 -0700 (PDT) Received: (from hume@localhost) by Den.BOFH.Halifax.NS.Ca (8.9.3+Sun/8.9.1) id SAA09198 for freebsd-current@freebsd.org; Mon, 4 Sep 2000 18:26:36 -0300 (ADT) From: Brandon Hume Message-Id: <200009042126.SAA09198@Den.BOFH.Halifax.NS.Ca> Subject: Re: AIC-7890 problems with kernel build In-Reply-To: <20000905061131G.iwasaki@jp.FreeBSD.org> from Mitsuru IWASAKI at "Sep 5, 2000 6:11:31 am" To: freebsd-current@freebsd.org Date: Mon, 4 Sep 2000 18:26:36 -0300 (ADT) X-Mailer: ELM [version 2.4ME+ PL42 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could you disable acpi and try again to make the problem clearer? > Without `device acpi' line in your kernel config file, any ACPI code As I mentioned, I've already done so. I know ACPI isn't causing the panic, but it does seem to change the BEHAVIOR of the panic. (I get the errors mentioned by the previous poster with ACPI, while without I proceed directly to the panic). -- Brandon Hume - hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ -> Solaris Snob and general NOCMonkey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 14:26:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id F1F9E37B42C; Mon, 4 Sep 2000 14:26:51 -0700 (PDT) Received: from [10.0.1.2] (dialup929.brussels2.skynet.be [194.78.238.97]) by morpheus.skynet.be (Postfix) with ESMTP id D3623DB22; Mon, 4 Sep 2000 23:26:46 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200009042022.NAA05249@mass.osd.bsdi.com> References: <200009042022.NAA05249@mass.osd.bsdi.com> Date: Mon, 4 Sep 2000 23:23:18 +0200 To: Mike Smith From: Brad Knowles Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed Cc: current@FreeBSD.ORG, hardware@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:22 PM -0700 2000/9/4, Mike Smith wrote: > I'd like to hear a few more success stories first (only one so far) from > people using the kit to add the driver to their 4.x systems. With all > the breakage in -current's PCI support at the moment, I don't expect to > hear too many people there reporting on it just yet. Well, if I can find a sufficiently stable -STABLE to install on my anonymous ftp server, I'll be glad to give it a try. > That's the general plan. Cool! I can't wait! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 14:35:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9985937B422; Mon, 4 Sep 2000 14:35:14 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA66726; Mon, 4 Sep 2000 14:35:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 4 Sep 2000 14:35:14 -0700 (PDT) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@freebsd.org Subject: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) In-Reply-To: <200009041550.IAA18878@freefall.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 Mon, 4 Sep 2000, Jordan K. Hubbard wrote: > jkh 2000/09/04 08:50:15 PDT > > Modified files: > release/sysinstall config.c > Log: > enable sshd by default. This only effects *new* installs, so > upgraders will not receive any unpleasant surprises. This will be semi-broken for the next 17 days for US people because sshd won't work out of the box if you have "Protocol 1" defined, which is in the default config (and removing it may surprise people upgrading) All will be right again come Sep 21. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 14:47:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-142.telepath.com [216.14.0.142]) by hub.freebsd.org (Postfix) with SMTP id C9DF437B424 for ; Mon, 4 Sep 2000 14:47:19 -0700 (PDT) Received: (qmail 44680 invoked by uid 100); 4 Sep 2000 21:46:40 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14772.6208.887660.874830@guru.mired.org> Date: Mon, 4 Sep 2000 16:46:40 -0500 (CDT) To: Mitsuru IWASAKI Cc: hume@Den.BOFH.Halifax.NS.Ca, cbh@teabag.demon.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: AIC-7890 problems with kernel build In-Reply-To: <20000905061131G.iwasaki@jp.FreeBSD.org> References: <200009042037.RAA09087@Den.BOFH.Halifax.NS.Ca> <20000905061131G.iwasaki@jp.FreeBSD.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mitsuru IWASAKI writes: > All I can say is that acpi is initilized after pcib and its children > are attached so I don't think ACPI code affects PCI stuff... > > > # Power management support (see LINT for more options) > > #device apm > > device acpi > > Could you disable acpi and try again to make the problem clearer? > Without `device acpi' line in your kernel config file, any ACPI code > isn't compiled in your kernel. That was the first thing I tried when mine failed. It didn't make any difference - I saw the same failure (the page fault, not the SCB errors). FWIW, my working kernel was built August 26, 10:05 GMT. ; Mon, 4 Sep 2000 14:54:28 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e84LsQr10954; Tue, 5 Sep 2000 06:54:26 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: mwm@mired.org Cc: iwasaki@jp.FreeBSD.org, hume@Den.BOFH.Halifax.NS.Ca, cbh@teabag.demon.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: AIC-7890 problems with kernel build In-Reply-To: <14772.6208.887660.874830@guru.mired.org> References: <200009042037.RAA09087@Den.BOFH.Halifax.NS.Ca> <20000905061131G.iwasaki@jp.FreeBSD.org> <14772.6208.887660.874830@guru.mired.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000905065401E.iwasaki@jp.FreeBSD.org> Date: Tue, 05 Sep 2000 06:54:01 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 10 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could you disable acpi and try again to make the problem clearer? > > Without `device acpi' line in your kernel config file, any ACPI code > > isn't compiled in your kernel. > > That was the first thing I tried when mine failed. It didn't make any > difference - I saw the same failure (the page fault, not the SCB > errors). Ah, I haven't read previous mails. I'm sorry about that. # Now I can go to my bed :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 14:59:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 714D437B424; Mon, 4 Sep 2000 14:59:40 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA69035; Mon, 4 Sep 2000 14:59:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 4 Sep 2000 14:59:40 -0700 (PDT) From: Kris Kennaway To: Poul-Henning Kamp Cc: Nick Sayer , freebsd-current@FreeBSD.ORG Subject: Re: Include OpenSSL root CA cert list? In-Reply-To: <54384.968100124@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Sep 2000, Poul-Henning Kamp wrote: > In message <200009042038.NAA20320@icarus.kfu.com>, Nick Sayer writes: > > > >If something like this already exists, then my searches must have > >missed it. > > > >In order to improve the usefulness of the openssl installation, > >I would like to suggest that a collection of CA root certs be > >added to the base installation and perhaps even referenced by > >the conf file. > > > > > >What does everyone think? > > Make it a port... This is probably fair enough - nothing in the base system needs these, at least until fetch learns how to speak https. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 19:58:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 5465337B424; Mon, 4 Sep 2000 19:58:45 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id TAA17810; Mon, 4 Sep 2000 19:58:26 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Kris Kennaway Cc: "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) In-Reply-To: Message from Kris Kennaway of "Mon, 04 Sep 2000 14:35:14 PDT." Date: Mon, 04 Sep 2000 19:58:26 -0700 Message-ID: <17806.968122706@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This will be semi-broken for the next 17 days for US people because sshd > won't work out of the box if you have "Protocol 1" defined, which is in > the default config (and removing it may surprise people upgrading) Well, it's at least one step closer - all they have to do now (the US people) is install the rsaref port to have the already-running sshd work correctly post-install, correct? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 19:59:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C7E6737B422; Mon, 4 Sep 2000 19:59:43 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA24337; Mon, 4 Sep 2000 20:59:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA39943; Mon, 4 Sep 2000 20:59:02 -0600 (MDT) Message-Id: <200009050259.UAA39943@harmony.village.org> To: Jordan Hubbard Subject: Re: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) Cc: Kris Kennaway , "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@FreeBSD.org In-reply-to: Your message of "Mon, 04 Sep 2000 19:58:26 PDT." <17806.968122706@winston.osd.bsdi.com> References: <17806.968122706@winston.osd.bsdi.com> Date: Mon, 04 Sep 2000 20:59:01 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <17806.968122706@winston.osd.bsdi.com> Jordan Hubbard writes: : Well, it's at least one step closer - all they have to do now (the US : people) is install the rsaref port to have the already-running sshd : work correctly post-install, correct? Unless they want to use idea for anything... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 20: 9:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A394E37B422; Mon, 4 Sep 2000 20:09:22 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA17506; Mon, 4 Sep 2000 20:09:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 4 Sep 2000 20:09:22 -0700 (PDT) From: Kris Kennaway To: Jordan Hubbard Cc: "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) In-Reply-To: <17806.968122706@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Sep 2000, Jordan Hubbard wrote: > > This will be semi-broken for the next 17 days for US people because sshd > > won't work out of the box if you have "Protocol 1" defined, which is in > > the default config (and removing it may surprise people upgrading) > > Well, it's at least one step closer - all they have to do now (the US > people) is install the rsaref port to have the already-running sshd > work correctly post-install, correct? Yeah, but it will just coredump at boot time until they do :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 20:10: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 32B2D37B422; Mon, 4 Sep 2000 20:10:00 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA17529; Mon, 4 Sep 2000 20:10:00 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 4 Sep 2000 20:09:59 -0700 (PDT) From: Kris Kennaway To: Warner Losh Cc: Jordan Hubbard , "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) In-Reply-To: <200009050259.UAA39943@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Sep 2000, Warner Losh wrote: > In message <17806.968122706@winston.osd.bsdi.com> Jordan Hubbard writes: > : Well, it's at least one step closer - all they have to do now (the US > : people) is install the rsaref port to have the already-running sshd > : work correctly post-install, correct? > > Unless they want to use idea for anything... I'm pretty sure OpenSSH doesnt support IDEA Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 22:42:38 2000 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 64E7E37B422; Mon, 4 Sep 2000 22:42:32 -0700 (PDT) Received: from rina.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-rina.r-0.1-11.01.2000) with ESMTP/IPv4 id OAA52773; Tue, 5 Sep 2000 14:42:11 +0900 (JST) Date: Tue, 05 Sep 2000 14:42:10 +0900 Message-ID: <14772.34738.630468.85559N@rina> From: Seigo Tanimura To: current@freebsd.org, net@freebsd.org Subject: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been suffering from this problem for almost 2 months. When I remove a pcmcia ethernet card from my laptop PC, routed(8) announces updated routing information by multicast, leading to a kernel panic. The stack trace looks like this: IdlePTD 4136960 initial pcb at 352840 panicstr: page fault panic messages: --- Syntax error: Unterminated quoted string --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:310 310 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:310 #1 0xc018f3e1 in panic (fmt=0xc02faf4f "page fault") at ../../kern/kern_shutdown.c:560 #2 0xc02b5043 in trap_fatal (frame=0xcb9b0d7c, eva=213493) at ../../i386/i386/trap.c:951 #3 0xc02b4ce5 in trap_pfault (frame=0xcb9b0d7c, usermode=0, eva=213493) at ../../i386/i386/trap.c:844 #4 0xc02b4877 in trap (frame={tf_fs = 16, tf_es = -969998320, tf_ds = 16, tf_edi = -1058687232, tf_esi = -1058687744, tf_ebp = -879030772, tf_isp = -879030872, tf_ebx = -1058661888, tf_edx = -1067786268, tf_ecx = 213485, tf_eax = -1058661888, tf_trapno = 12, tf_err = 0, tf_eip = -1071746146, tf_cs = 8, tf_eflags = 66054, tf_esp = -1067786496, tf_ss = -879030720}) at ../../i386/i386/trap.c:443 #5 0xc01e739e in ip_output (m0=0xc05adf00, opt=0x0, ro=0xcb424dc8, flags=32, imo=0xc0e5b700) at ../../netinet/ip_output.c:326 #6 0xc01e8e26 in rip_output (m=0xc05adf00, so=0xcae549c0, dst=33554656) at ../../netinet/raw_ip.c:234 #7 0xc01e9627 in rip_send (so=0xcae549c0, flags=0, m=0xc05adf00, nam=0xc0da7950, control=0x0, p=0xc62f9f60) at ../../netinet/raw_ip.c:566 #8 0xc01b281f in sosend (so=0xcae549c0, addr=0xc0da7950, uio=0xcb9b0ed4, top=0xc05adf00, control=0x0, flags=0, p=0xc62f9f60) at ../../kern/uipc_socket.c:614 #9 0xc01b63be in sendit (p=0xc62f9f60, s=5, mp=0xcb9b0f14, flags=0) at ../../kern/uipc_syscalls.c:519 #10 0xc01b7998 in sendto (p=0xc62f9f60, uap=0xcb9b0f80) at ../../kern/uipc_syscalls.c:571 #11 0xc02b51ba in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 134727225, tf_ebp = -1077937408, tf_isp = -879030316, tf_ebx = 134844928, tf_edx = 2, tf_ecx = -1, tf_eax = 133, tf_trapno = 7, tf_err = 2, tf_eip = 134573992, tf_cs = 31, tf_eflags = 659, tf_esp = -1077937484, tf_ss = 47}) at ../../i386/i386/trap.c:1150 #12 0xc02a8875 in Xint0x80_syscall () #13 0x8051b10 in ?? () #14 0x8050ff4 in ?? () #15 0x804c212 in ?? () #16 0x804813f in ?? () In ip_output(), imo->imo_multicast_ifp points to the removed interface, which is passed to IN_LOOKUP_MULTI() to cause a panic. This problem also occurs when we attempt to delete a multicast address from a removed interface. if_delmulti() derefers an ifp to the removed interface, ending up with a panic. The problem does not occur for unicast. http://people.FreeBSD.org/~tanimura/patches/mcastif.diff.gz is a workround patch. The idea is to track all of the active ifps, confirm an ifp to be active prior to dereferencing it, and free orphaned ifmultiaddrs attached to a removed ifp. It would be much more elegant if we could clean up the multicast information related to a removed interface, though. -- 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 Sep 4 23: 8:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 2527837B422; Mon, 4 Sep 2000 23:08:34 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13WBzS-0000FR-00; Tue, 05 Sep 2000 00:13:50 -0600 Message-ID: <39B48F1E.4C193F79@softweyr.com> Date: Tue, 05 Sep 2000 00:13:50 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Seigo Tanimura Cc: current@freebsd.org, net@freebsd.org Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr References: <14772.34738.630468.85559N@rina> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote: > > I have been suffering from this problem for almost 2 months. When I > remove a pcmcia ethernet card from my laptop PC, routed(8) announces > updated routing information by multicast, leading to a kernel > panic. Ejecting an interface configured up will do that. ifconfig the interface `down' and then `delete' before ejecting it. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 4 23:10:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9536D37B424; Mon, 4 Sep 2000 23:10:15 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA24820; Tue, 5 Sep 2000 00:10:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA58464; Tue, 5 Sep 2000 00:09:33 -0600 (MDT) Message-Id: <200009050609.AAA58464@harmony.village.org> To: Wes Peters Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr Cc: Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Sep 2000 00:13:50 MDT." <39B48F1E.4C193F79@softweyr.com> References: <39B48F1E.4C193F79@softweyr.com> <14772.34738.630468.85559N@rina> Date: Tue, 05 Sep 2000 00:09:33 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39B48F1E.4C193F79@softweyr.com> Wes Peters writes: : Ejecting an interface configured up will do that. ifconfig the interface : `down' and then `delete' before ejecting it. At best this is an unsatisfactory workaround. if_detach should cause the right thing to happen. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 4:54:30 2000 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 3D48037B422 for ; Tue, 5 Sep 2000 04:54:28 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Sep 2000 12:54:24 +0100 (BST) Date: Tue, 5 Sep 2000 12:54:22 +0100 From: David Malone To: Mitsuru IWASAKI Cc: imp@village.org, rjoseph@mammalia.org, freebsd-current@FreeBSD.ORG Subject: Re: xl driver Message-ID: <20000905125422.A80564@walton.maths.tcd.ie> References: <20000903145754.A1691@mammalia.org> <200009040138.TAA53833@harmony.village.org> <20000904092048.A42249@maccullagh.maths.tcd.ie> <20000904173811Z.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000904173811Z.iwasaki@jp.FreeBSD.org>; from iwasaki@jp.FreeBSD.org on Mon, Sep 04, 2000 at 05:38:11PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 04, 2000 at 05:38:11PM +0900, Mitsuru IWASAKI wrote: > > This happened to me when I turned on ACPI support - infact it > > thought I had 3 PCI busses when I only had one! I haven't had time > > to look into it yet though. > > Hmmm, can I have your full output of dmesg? It seemed to be some combination of the acpi support and Peter's PCI changes. It didn't use ACPI the kernel worked fine and with ACPI support it thought it had 3 PCI busses. I cvsupped a more recent version of the code and now everything works but my ISA network card. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 6:16:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A3B8D37B422; Tue, 5 Sep 2000 06:16:17 -0700 (PDT) Received: from newsguy.com (p17-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.82]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id WAA07459; Tue, 5 Sep 2000 22:16:12 +0900 (JST) Message-ID: <39B4F200.5158E213@newsguy.com> Date: Tue, 05 Sep 2000 22:15:44 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Jordan Hubbard Cc: Kris Kennaway , "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) References: <17806.968122706@winston.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > > This will be semi-broken for the next 17 days for US people because sshd > > won't work out of the box if you have "Protocol 1" defined, which is in > > the default config (and removing it may surprise people upgrading) > > Well, it's at least one step closer - all they have to do now (the US > people) is install the rsaref port to have the already-running sshd > work correctly post-install, correct? Besides, that's what we mean when we say -current is the "bleeding edge". :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net OK, so the solar flares are my fault.. I am sorry, ok?!?! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 7:32:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (rstcorp2.daf.concentric.net [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 74EA137B422 for ; Tue, 5 Sep 2000 07:32:38 -0700 (PDT) Received: (from uucp@localhost) by assurance.rstcorp.com (8.10.1/8.10.1) id e85EWcr29841; Tue, 5 Sep 2000 10:32:38 -0400 Received: from exchange.rstcorp.com(10.1.20.3) by assurance.rstcorp.com via smap (V2.1+anti-relay+anti-spam) id xma029832; Tue, 5 Sep 00 10:32:23 -0400 Received: from jabberwock (jabberwock.rstcorp.com [10.1.254.253]) by exchange.rstcorp.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id SJFXH0LX; Tue, 5 Sep 2000 10:32:11 -0400 Received: by jabberwock (Postfix, from userid 93) id 71622C; Tue, 5 Sep 2000 10:32:21 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14773.1013.154601.647909@jabberwock.rstcorp.com> Date: Tue, 5 Sep 2000 10:32:21 -0400 (EDT) From: "Viren R.Shah" To: freebsd-current@freebsd.org Cc: matey@cis.ohio-state.edu Subject: problems with aureal soundcard: kernel fault when playing mp3s X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid Reply-To: "Viren R.Shah" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Alexander, I'm Cc:ing you on this just in case you have heard of anyone else having similar problems with Aureal cards with recent -currents] My last good kernel was from aug 14. On a kernel from 09/05, I get a page fault as soon as I try to play mp3s using mpg123. Note that I have an Aureal Vortex 8830, so I have to use the linux drivers to get the device working (http://www.cis.ohio-state.edu/~matey/au88x0/) so this might just be a problem with interactions between the linux .o files and kernel data structures. The soundcard worked fine using the linux drivers on a -current from August 14. I'm wondering if anything changed in the pcm code since then. Here's the page fault in DDB. I have a debug kernel if anyone needs more info. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1000001b fault code = supervisor read, page not present instruction pointer = 0x8:0xc016ef23 stack pointer = 0x10:0xd2a4dc98 frame pointer = 0x10:0xd2a4dc98 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 = 825 (mpg123) interrupt mask = none kernel: type 12 trap, code=0 Stopped at fmtvalid+0xb: cmpl $0,0(%edx) db>trace fmtvalid(8,1000001b,c1599000) at fmtvalid+0xb chn_setformat(c1599000,8) at chn_setformat+0x4c chn_reset(c1599000,8,d2a90740,c155f600,d2a4be00) at chn_reset+0x37 dsp_open(c14fe400,0,2,3,0) at dsp_open+0x12b sndopen(c155f600,2,200,d2a4be00,0) at sndopen+0x73 spec_open(d2a4dd94,d2a4dd68,c0264675,d2a4dd94,d2a4de08) at spec_open+0x145 spec_vnoperate(d2a4dd94,d2a4de08,c01cdf6b,d2a4dd94,d2a4df80) at spec_vnoperate+0x15 ufs_vnoperatespec(d2a4dd94,d2a4df80,0,d2a4df80,2) at ufs_vnoperatespec+0x15 vn_open(d2a4de6c,d2a4de38,1,d2a4be00,3) at vn_open+0x333 open(d2a4be00,d2a4df80,bfbffa30,807e8a4,807b4f8) at open+0xcd syscall2(2f,2f,2f,807b4f8,807e8a4) at syscall2+0x1f1 Xint0x80_syscall() at Xint0x80_syscall+0x25 db> Here's my dmesg from the kernel that produced the above page fault: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Sep 5 09:07:19 EDT 2000 root@jabberwock:/home/FreeBSD/src/sys/compile/VORPAL Calibrating clock(s) ... TSC clock: 797903726 Hz, i8254 clock: 1193093 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 797966473 Hz CPU: Pentium III/Pentium III Xeon/Celeron (797.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 402391040 (392960K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x003e3000 - 0x17fb7fff, 398282752 bytes (97237 pages) avail memory = 387465216 (378384K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fda60 bios32: Entry = 0xfda74 (c00fda74) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xda95 pnpbios: Found PnP BIOS data at 0xc00f2c10 pnpbios: Entry = f0000:24ca Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel "kernel" at 0xc03ca000. nulldev: random: mem: Pentium Pro MTRR support enabled Creating DISK md0 md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: physical bus=0 found-> vendor=0x8086, dev=0x2501, revid=0x04 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base f8000000, size 26, enabled found-> vendor=0x8086, dev=0x250f, revid=0x04 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x2418, revid=0x02 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=2 secondarybus=2 found-> vendor=0x8086, dev=0x2410, revid=0x02 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x2411, revid=0x02 bus=0, slot=31, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=0x8086, dev=0x2412, revid=0x02 bus=0, slot=31, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=10 map[20]: type 4, range 32, base 0000ef80, size 5, enabled found-> vendor=0x8086, dev=0x2413, revid=0x02 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=b, irq=9 map[20]: type 4, range 32, base 0000efa0, size 4, enabled pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: physical bus=1 found-> vendor=0x10de, dev=0x0100, revid=0x10 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base fd000000, size 24, enabled map[14]: type 3, range 32, base e8000000, size 27, enabled pci1: on pcib1 pci1: (vendor=0x10de, dev=0x0100) at 0.0 irq 11 pcib2: at device 30.0 on pci0 pci2: physical bus=2 found-> vendor=0x10b7, dev=0x9200, revid=0x78 bus=2, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 4, range 32, base 0000dc00, size 7, enabled map[14]: type 1, range 32, base feaffc00, size 7, enabled found-> vendor=0x12eb, dev=0x0002, revid=0xfe bus=2, slot=11, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base fea80000, size 18, enabled map[14]: type 4, range 32, base 0000dff0, size 3, enabled map[18]: type 4, range 32, base 0000dfe0, size 3, enabled pci2: on pcib2 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc00-0xdc7f mem 0xfeaffc00-0xfeaffc7f irq 11 at device 8.0 on pci2 xl0: Ethernet address: 00:01:03:1d:d6:4e xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: xl0 attached pcm0: port 0xdfe0-0xdfe7,0xdff0-0xdff7 mem 0xfea80000-0xfeabffff irq 10 at device 11.0 on pci2 pcm: setmap 2b000, 8000; 0xcfbad000 -> 2b000 pcm: setmap 33000, 8000; 0xcfbb5000 -> 33000 pcm: setmap 3b000, 8000; 0xcfbbd000 -> 3b000 pcm: setmap 43000, 8000; 0xcfbc5000 -> 43000 pcm: setmap 4b000, 8000; 0xcfbcd000 -> 4b000 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0x4 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xef80-0xef9f irq 10 at device 31.2 on pci0 using shared irq10. usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 9 ata-: ata0 already exists, using ata2 instead ata-: ata1 already exists, using ata3 instead Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 pnpbios: 20 devices, largest 234 bytes PNP0c01: adding fixed memory32 range 0-0x9fbff, size=0x9fc00 PNP0c01: adding fixed memory32 range 0x9fc00-0x9ffff, size=0x400 PNP0c01: adding fixed memory32 range 0xe0000-0xfffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x17fe0000-0x17ff7fff, size=0x18000 PNP0c01: adding fixed memory32 range 0x17ff8000-0x17ffffff, size=0x8000 PNP0c01: adding fixed memory32 range 0x17fc0000-0x17fdffff, size=0x20000 PNP0c01: adding fixed memory32 range 0xfff00000-0xffffffff, size=0x100000 PNP0c01: end config pnpbios: handle 0 device ID PNP0c01 (010cd041) PNP0c01: adding fixed memory32 range 0x100000-0x17fbffff, size=0x17ec0000 PNP0c01: end config pnpbios: handle 1 device ID PNP0c01 (010cd041) PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding irq mask 0x4 PNP0000: end config pnpbios: handle 2 device ID PNP0000 (0000d041) PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x80-0x90, size=0x11, align=0x1 PNP0200: adding io range 0x94-0x9f, size=0xc, align=0x1 PNP0200: adding io range 0xc0-0xde, size=0x1f, align=0x1 PNP0200: end config pnpbios: handle 3 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: end config pnpbios: handle 4 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: end config pnpbios: handle 5 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: end config pnpbios: handle 6 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: end config pnpbios: handle 7 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: end config pnpbios: handle 8 device ID PNP0c04 (040cd041) PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0c02: adding io range 0x10-0x1f, size=0x10, align=0x1 PNP0c02: adding io range 0x22-0x2d, size=0xc, align=0x1 PNP0c02: adding io range 0x30-0x3f, size=0x10, align=0x1 PNP0c02: adding io range 0x50-0x52, size=0x3, align=0x1 PNP0c02: adding io range 0x72-0x77, size=0x6, align=0x1 PNP0c02: adding io range 0x91-0x93, size=0x3, align=0x1 PNP0c02: adding io range 0xa2-0xbe, size=0x1d, align=0x1 PNP0c02: adding io range 0x400-0x47f, size=0x80, align=0x1 PNP0c02: adding io range 0x540-0x54f, size=0x10, align=0x1 PNP0c02: adding io range 0x500-0x53f, size=0x40, align=0x1 PNP0c02: adding io range 0-0xffffffff, size=0, align=0x1 PNP0c02: adding io range 0-0xffffffff, size=0, align=0x1 PNP0c02: adding io range 0-0xffffffff, size=0, align=0x1 PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: skipping empty range PNP0c02: end config pnpbios: handle 9 device ID PNP0c02 (020cd041) INT0800: adding fixed memory32 range 0xffb00000-0xffbfffff, size=0x100000 INT0800: end config pnpbios: handle 10 device ID INT0800 (0008d425) PNP0c02: adding io range 0x800-0x87f, size=0x80, align=0x1 PNP0c02: end config pnpbios: handle 11 device ID PNP0c02 (020cd041) PNP0c02: end config pnpbios: handle 12 device ID PNP0c02 (020cd041) PNP0c02: end config pnpbios: handle 13 device ID PNP0c02 (020cd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 PNP0501: end config pnpbios: handle 14 device ID PNP0501 (0105d041) PNP0c02: end config pnpbios: handle 15 device ID PNP0c02 (020cd041) PNP0401: adding io range 0x378-0x37f, size=0x8, align=0x8 PNP0401: adding io range 0x778-0x77a, size=0x3, align=0x8 PNP0401: adding irq mask 0x80 PNP0401: adding dma mask 0x8 PNP0401: end config pnpbios: handle 16 device ID PNP0401 (0104d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x1 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 17 device ID PNP0700 (0007d041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 18 device ID PNP0f13 (130fd041) PNP0a03: end config pnpbios: handle 19 device ID PNP0a03 (030ad041) sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata2 failed to probe at port 0x1f0 irq 14 on isa0 ata3 failed to probe at port 0x170 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 0a 03 c8 psm: status 0a 03 c8 psm: status 0a 03 c8 psm: data c8 c2 50 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0-50, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:08, syncbits:08 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 06 e0 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0 failed to probe on isa0 sio0: irq maps: 0x41 0x51 0x41 0x41 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 sio1: irq maps: 0x41 0x41 0x41 0x41 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port sc1: no video adapter is found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices unknown: can't assign resources unknown: at port 0x60 on isa0 unknown: failed to probe at port 0x61 on isa0 unknown: failed to probe at iomem 0xffb00000-0xffbfffff on isa0 unknown: can't assign resources unknown: at port 0x3f8-0x3ff on isa0 unknown: can't assign resources unknown: at port 0x378-0x37f on isa0 unknown: can't assign resources unknown: at port 0x3f0-0x3f5 on isa0 unknown: can't assign resources unknown: at irq 12 on isa0 BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: ppp0 attached new masks: bio 68c440, tty 631492, net 671c92 bpf: faith0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached ata0-master: success setting UDMA4 on ICH chip ad0: ATA-5 disk at ata0 as master ad0: 28629MB (58633344 sectors), 58168 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA66 ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad0 ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata1-master: success setting PIO4 on generic chip acd0: CDROM drive at ata1 as master acd0: read 8250KB/s (8250KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked, lock protected Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5, start 63, end = 58621184, size 58621122 : OK start_init: trying /sbin/init splash: image decoder found: logo_saver Linux-ELF exec handler installed Viren -- "I sat around during the design phase going "this is going to suck so badly that we're going to have to hold onto desks to stop us from being drawn into the vortex"." -- Chris "Saundo" Saunderson in the scary devil monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 8:30:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id CC16D37B423; Tue, 5 Sep 2000 08:30:44 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13WKnt-00006R-00; Tue, 05 Sep 2000 09:38:30 -0600 Message-ID: <39B51375.4DE4C6FA@softweyr.com> Date: Tue, 05 Sep 2000 09:38:29 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr References: <39B48F1E.4C193F79@softweyr.com> <14772.34738.630468.85559N@rina> <200009050609.AAA58464@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 <39B48F1E.4C193F79@softweyr.com> Wes Peters writes: > : Ejecting an interface configured up will do that. ifconfig the interface > : `down' and then `delete' before ejecting it. > > At best this is an unsatisfactory workaround. if_detach should cause > the right thing to happen. Right, but as we've discussed before, that may not be possible with PCCard and CardBus, or anything else short of CPCI. In the meantime, this is the state the code is in now, and if someone wants it to be better, we await their patches. As always. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 8:31: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from cx281057-a.irvn1.occa.home.com (cx281057-a.irvn1.occa.home.com [24.1.175.22]) by hub.freebsd.org (Postfix) with ESMTP id 4EAD637B422 for ; Tue, 5 Sep 2000 08:30:59 -0700 (PDT) Received: from cx281057-a.irvn1.occa.home.com (localhost [127.0.0.1]) by cx281057-a.irvn1.occa.home.com (8.11.0/8.11.0) with ESMTP id e85FUnx52802; Tue, 5 Sep 2000 08:30:50 -0700 (PDT) (envelope-from housel@acm.org) Date: Tue, 05 Sep 2000 08:30:48 -0700 Message-ID: From: housel@acm.org (Peter S. Housel) To: viren@rstcorp.com Cc: freebsd-current@FreeBSD.ORG, matey@cis.ohio-state.edu Subject: Re: problems with aureal soundcard: kernel fault when playing mp3s In-Reply-To: In your message of "Tue, 5 Sep 2000 10:32:21 -0400 (EDT)" <14773.1013.154601.647909@jabberwock.rstcorp.com> References: <14773.1013.154601.647909@jabberwock.rstcorp.com> User-Agent: Wanderlust/1.1.1 (Purple Rain) WEMI/1.13.7 (Shimada) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 5 Sep 2000 10:32:21 -0400 (EDT), Viren R.Shah wrote: > [Alexander, I'm Cc:ing you on this just in case you have heard of > anyone else having similar problems with Aureal cards with recent > -currents] > > My last good kernel was from aug 14. On a kernel from 09/05, I get a > page fault as soon as I try to play mp3s using mpg123. > > Note that I have an Aureal Vortex 8830, so I have to use the linux > drivers to get the device working > (http://www.cis.ohio-state.edu/~matey/au88x0/) so this might just be a > problem with interactions between the linux .o files and kernel data > structures. The soundcard worked fine using the linux drivers on a > -current from August 14. I'm wondering if anything changed in the pcm > code since then. > > Here's the page fault in DDB. I have a debug kernel if anyone needs > more info. > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x1000001b > fault code = supervisor read, page not present The pcm interfaces did change. The following patch fixes the au88x0 driver for me. Cheers, -Peter S. Housel- housel@acm.org http://members.home.com/housel/ --- au88x0.c Fri May 26 22:12:56 2000 +++ /usr/src/sys/dev/sound/pci/au88x0.c Mon Sep 4 23:17:05 2000 @@ -200,17 +200,23 @@ static int auchan_getptr(void *data); static pcmchan_caps *auchan_getcaps(void *data); -static pcmchan_caps au_playcaps = { - 4000, 48000, - AFMT_STEREO | AFMT_MU_LAW | AFMT_A_LAW | AFMT_U8 | AFMT_S16_LE, - AFMT_STEREO | AFMT_S16_LE +static u_int32_t au_playfmt[] = { + AFMT_U8, + AFMT_STEREO | AFMT_U8, + AFMT_S16_LE, + AFMT_STEREO | AFMT_S16_LE, + 0 }; +static pcmchan_caps au_playcaps = {4000, 48000, au_playfmt, 0}; -static pcmchan_caps au_reccaps = { - 4000, 48000, - AFMT_STEREO | AFMT_MU_LAW | AFMT_A_LAW | AFMT_U8 | AFMT_S16_LE, - AFMT_STEREO | AFMT_S16_LE +static u_int32_t au_recfmt[] = { + AFMT_U8, + AFMT_STEREO | AFMT_U8, + AFMT_S16_LE, + AFMT_STEREO | AFMT_S16_LE, + 0 }; +static pcmchan_caps au_reccaps = {4000, 48000, au_recfmt, 0}; static pcm_channel au_chantemplate = { auchan_init, @@ -221,6 +227,14 @@ auchan_trigger, auchan_getptr, auchan_getcaps, + NULL, /* free */ + NULL, /* nop1 */ + NULL, /* nop2 */ + NULL, /* nop3 */ + NULL, /* nop4 */ + NULL, /* nop5 */ + NULL, /* nop6 */ + NULL, /* nop7 */ }; @@ -232,6 +246,7 @@ static snd_mixer au_mixtemplate = { "Aureal Vortex 88x0 mixer", aumix_init, + NULL, aumix_set, aumix_setrecsrc, }; @@ -846,7 +861,7 @@ au_mixer = (snd_mixer *)malloc(sizeof(*au_mixer), M_DEVBUF, M_NOWAIT); if (au_mixer == NULL) goto bad; bcopy(&au_mixtemplate, au_mixer, sizeof(au_mixtemplate)); - mixer_init(d, au_mixer, au); + mixer_init(dev, au_mixer, au); if (bus_dma_tag_create(/*parent*/NULL, /*alignment*/2, /*boundary*/0, /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 8:32:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id 3155D37B43E; Tue, 5 Sep 2000 08:32:22 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id 9DE1620F01; Tue, 5 Sep 2000 10:35:08 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id 9B8821D101; Tue, 5 Sep 2000 10:35:08 -0500 (CDT) Date: Tue, 5 Sep 2000 10:35:03 -0500 (CDT) From: Visigoth To: Mike Smith Cc: Brad Knowles , current@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed In-Reply-To: <200009042022.NAA05249@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 4 Sep 2000, Mike Smith wrote: > > I'd like to hear a few more success stories first (only one so far) from > people using the kit to add the driver to their 4.x systems. With all > the breakage in -current's PCI support at the moment, I don't expect to > hear too many people there reporting on it just yet. > Maybe I missed it... Where is the kit? I would be happy to install and stress test a machine or two with SMP and without, just didn't realize there was a kit ;) must have been when I was reading my e-mail at like 3 am or something.... Visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBObUEmznmC/+RTnGeEQJqLwCgnnbsnbIEW38ATtBTo387XpMf5ZUAnRY5 a7gzxWhBc0xI3JkQyFtweCRI =3TRp -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 8:36:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3008D37B423; Tue, 5 Sep 2000 08:36:03 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA26432; Tue, 5 Sep 2000 09:35:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA60822; Tue, 5 Sep 2000 09:35:13 -0600 (MDT) Message-Id: <200009051535.JAA60822@harmony.village.org> To: Wes Peters Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr Cc: Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Sep 2000 09:38:29 MDT." <39B51375.4DE4C6FA@softweyr.com> References: <39B51375.4DE4C6FA@softweyr.com> <39B48F1E.4C193F79@softweyr.com> <14772.34738.630468.85559N@rina> <200009050609.AAA58464@harmony.village.org> Date: Tue, 05 Sep 2000 09:35:12 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39B51375.4DE4C6FA@softweyr.com> Wes Peters writes: : state the code is in now, and if someone wants it to be better, we await : their patches. As always. ;^) Tanimura-san did contribute patches. This problem isn't a race at the eject, but rather the network layer incompletely cleaning up after a device has gone away. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 8:51: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 9966D37B422 for ; Tue, 5 Sep 2000 08:50:58 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e85Fovs67343 for current@freebsd.org; Tue, 5 Sep 2000 19:50:57 +0400 (MSD) (envelope-from ache) Date: Tue, 5 Sep 2000 19:50:56 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: FIFOs & select: what about our implementation? Message-ID: <20000905195056.A67326@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Consider this comment comes from screen(1): /* * Define this if your system exits select() immediatly if a pipe is * opened read-only and no writer has opened it. */ #define BROKEN_PIPE 1 We have broken(?) pipe, according to this statement. At least, we have select return code -1 with wrong errno == 0. I attach the test for it below. The question is: what about our fifo select (actually poll) implementation? Is it really broken, or is it a feature? What standards says? If this is a feature, at least errno must be fixed. ----------------------------------------------------- #include #include #include #include #include char *fin = "/tmp/conftest$$"; main() { struct timeval tv; int r, x; unlink(fin); if (mkfifo(fin, 0600)) exit(1); close(0); if (open(fin, O_RDONLY|O_NONBLOCK)) exit(1); r = 1; tv.tv_sec = 1; tv.tv_usec = 0; if (select(1, &r, 0, 0, &tv)) { perror("select"); exit(1); } exit(0); } ----------------------------------------------------- -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 10:25:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (ppp0.knz.ams.dataloss.net [212.189.231.51]) by hub.freebsd.org (Postfix) with SMTP id 8879A37B422 for ; Tue, 5 Sep 2000 10:25:23 -0700 (PDT) Received: (qmail 1601 invoked by uid 1000); 5 Sep 2000 17:24:59 -0000 Mail-Followup-To: current@freebsd.org Date: Tue, 5 Sep 2000 19:24:58 +0200 From: Peter van Dijk To: current@freebsd.org Subject: Re: FIFOs & select: what about our implementation? Message-ID: <20000905192458.A1428@dataloss.net> References: <20000905195056.A67326@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000905195056.A67326@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Sep 05, 2000 at 07:50:56PM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 05, 2000 at 07:50:56PM +0400, Andrey A. Chernov wrote: > Consider this comment comes from screen(1): > > /* > * Define this if your system exits select() immediatly if a pipe is > * opened read-only and no writer has opened it. > */ > #define BROKEN_PIPE 1 > > We have broken(?) pipe, according to this statement. At least, we have > select return code -1 with wrong errno == 0. qmail calls this 'named pipe bug 1'. The workaround (which screen probably uses too) is to let the process doing the select() also have one fd opened for writing on the pipe. With that write-open, select() will only return if there is actual data waiting inside the pipe. I have filed a PR (19871) for this I think about 2 months ago, somebody submitted a patch but I never gotten around to testing it. I surely do think this behaviour is broken. http://www.freebsd.org/cgi/query-pr.cgi?pr=19871 Greetz, Peter -- dataloss networks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 11:10:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 8611E37B42C; Tue, 5 Sep 2000 11:10:13 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA02487; Tue, 5 Sep 2000 11:25:08 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009051825.LAA02487@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Visigoth Cc: current@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed In-reply-to: Your message of "Tue, 05 Sep 2000 10:35:03 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Sep 2000 11:25:08 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'd like to hear a few more success stories first (only one so far) from > > people using the kit to add the driver to their 4.x systems. With all > > the breakage in -current's PCI support at the moment, I don't expect to > > hear too many people there reporting on it just yet. > > > > Maybe I missed it... Where is the kit? I would be happy to > install and stress test a machine or two with SMP and without, just didn't > realize there was a kit ;) must have been when I was reading my e-mail at > like 3 am or something.... http://people.freebsd.org/~msmith/RAID/index.html#dpt -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 11:31:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 504BB37B422; Tue, 5 Sep 2000 11:31:41 -0700 (PDT) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id 2747C9A25; Tue, 5 Sep 2000 20:31:37 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200009051825.LAA02487@mass.osd.bsdi.com> References: <200009051825.LAA02487@mass.osd.bsdi.com> Date: Tue, 5 Sep 2000 20:30:38 +0200 To: Mike Smith , Visigoth From: Brad Knowles Subject: Re: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed Cc: current@FreeBSD.ORG, hardware@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:25 AM -0700 2000/9/5, Mike Smith wrote: > http://people.freebsd.org/~msmith/RAID/index.html#dpt Awesome! Thanks! Now I just have to get FreeBSD 4.2 installed on that ftp server.... -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 11:40:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5114237B422; Tue, 5 Sep 2000 11:40:24 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id OAA03025; Tue, 5 Sep 2000 14:38:54 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 5 Sep 2000 14:38:54 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Warner Losh Cc: Wes Peters , Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr In-Reply-To: <200009050609.AAA58464@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Sep 2000, Warner Losh wrote: > In message <39B48F1E.4C193F79@softweyr.com> Wes Peters writes: > : Ejecting an interface configured up will do that. ifconfig the interface > : `down' and then `delete' before ejecting it. > > At best this is an unsatisfactory workaround. if_detach should cause > the right thing to happen. This is all made harder by the fact that struct mbuf has a struct ifnet pointer in it, so if for any reason there is an outstanding mbuf originating from that interface, it is possible that the struct ifnet * will be dereferenced. For example, if it hits an ipfw rule that dummynets it, then hits an interface-based rule. This has been raised as an issue before, and is a good reason to ifconfig down the interface, and wait a second or two before ejecting. You could imagine code-based solutions, including scanning mbufs (?) for pointers that are undesirable, refcounting the struct ifnet so it isn't freed until all mbufs are free'd, etc. Whatever the case, you want to make sure that locking in the line of fire is avoided (i.e., attempting to lock struct ifnet during packet handling in the interrupt). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 11:44:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B10EF37B424; Tue, 5 Sep 2000 11:44:21 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA27368; Tue, 5 Sep 2000 12:44:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA62492; Tue, 5 Sep 2000 12:43:35 -0600 (MDT) Message-Id: <200009051843.MAA62492@harmony.village.org> To: Robert Watson Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr Cc: Wes Peters , Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Sep 2000 14:38:54 EDT." References: Date: Tue, 05 Sep 2000 12:43:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Robert Watson writes: : This is all made harder by the fact that struct mbuf has a struct ifnet : pointer in it, so if for any reason there is an outstanding mbuf : originating from that interface, it is possible that the struct ifnet * : will be dereferenced. For example, if it hits an ipfw rule that dummynets : it, then hits an interface-based rule. Yes. That's true. There's a race. : This has been raised as an issue before, and is a good reason to ifconfig : down the interface, and wait a second or two before ejecting. You could : imagine code-based solutions, including scanning mbufs (?) for pointers : that are undesirable, refcounting the struct ifnet so it isn't freed until : all mbufs are free'd, etc. Whatever the case, you want to make sure that : locking in the line of fire is avoided (i.e., attempting to lock struct : ifnet during packet handling in the interrupt). No body waits :-(. This is made worse by pccard's detaching the device when a suspend happens via acpi or apm. NetBSD has done some interesting things in this area with reference counting and such that I'd love to bring in as soon as I get newcard done. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 11:50: 2 2000 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 7361137B423; Tue, 5 Sep 2000 11:49:55 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id UAA20917; Tue, 5 Sep 2000 20:51:43 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200009051851.UAA20917@info.iet.unipi.it> Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr In-Reply-To: from Robert Watson at "Sep 5, 2000 02:38:54 pm" To: Robert Watson Date: Tue, 5 Sep 2000 20:51:43 +0200 (CEST) Cc: Warner Losh , Wes Peters , Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is all made harder by the fact that struct mbuf has a struct ifnet > pointer in it, so if for any reason there is an outstanding mbuf ... > This has been raised as an issue before, and is a good reason to ifconfig > down the interface, and wait a second or two before ejecting. You could and still, the wait is not errorproof as delays can be larger than a second or two. I suppose the correct way to do things when you delete an interface is to to keep the struct ifnet around (in some list) for further reuse when the card is reinserted. One could argue that dummynet with its delayed scheduling of packets is screwing up things, but i would argue that having pointers to volatile objects without reference counts is not such a great design, and SMP might give the same kind of problems. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 12:31:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 707BF37B422; Tue, 5 Sep 2000 12:31:47 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e85JVIu71884; Tue, 5 Sep 2000 23:31:18 +0400 (MSD) (envelope-from ache) Date: Tue, 5 Sep 2000 23:31:16 +0400 From: "Andrey A. Chernov" To: Peter van Dijk Cc: current@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: FIFOs & select: what about our implementation? Message-ID: <20000905233114.A71862@nagual.pp.ru> References: <20000905195056.A67326@nagual.pp.ru> <20000905192458.A1428@dataloss.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000905192458.A1428@dataloss.net>; from peter@dataloss.net on Tue, Sep 05, 2000 at 07:24:58PM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 05, 2000 at 07:24:58PM +0200, Peter van Dijk wrote: > > select return code -1 with wrong errno == 0. Sorry, I was wrong about errno, it returns that descriptor is ready for read while there is nothing to read. > I surely do think this behaviour is broken. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=19871 I disagree about Bruce comment on that. If we have nothing to read, select must be timed out. It is not non-blocking read call but select. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 13:36: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 058BB37B424 for ; Tue, 5 Sep 2000 13:35:59 -0700 (PDT) Received: (qmail 2627 invoked from network); 5 Sep 2000 20:35:53 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 5 Sep 2000 20:35:53 -0000 Date: Wed, 6 Sep 2000 07:35:50 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Peter van Dijk , ache@freebsd.org Cc: current@FreeBSD.ORG Subject: Re: FIFOs & select: what about our implementation? In-Reply-To: <20000905192458.A1428@dataloss.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Sep 2000, Peter van Dijk wrote: > On Tue, Sep 05, 2000 at 07:50:56PM +0400, Andrey A. Chernov wrote: > > Consider this comment comes from screen(1): > > > > /* > > * Define this if your system exits select() immediatly if a pipe is > > * opened read-only and no writer has opened it. > > */ > > #define BROKEN_PIPE 1 > > > > We have broken(?) pipe, according to this statement. At least, we have > > select return code -1 with wrong errno == 0. > > qmail calls this 'named pipe bug 1'. The workaround (which screen > probably uses too) is to let the process doing the select() also have > one fd opened for writing on the pipe. With that write-open, select() > will only return if there is actual data waiting inside the pipe. > > I have filed a PR (19871) for this I think about 2 months ago, somebody > submitted a patch but I never gotten around to testing it. > > I surely do think this behaviour is broken. This behaviour is sort of intentional. Reads on a named pipe with no writers are specified by POSIX.1 to return immediately. 4.4BSD does extra work to break this in some cases. select() on a read descriptor open on such a pipe just follows read(). I think it started giving the behaviour that you don't want when I fixed read(). Linux gives the behaviour that you want by not following read() in select() (more (precisely, in poll()). It puts POLLHUP in the events polled for read descriptors in select() and actually implements POLLHUP for named pipes. The special handling for select() then falls out of the special handling for POLLHUP (polling on POLLHUP doesn't succeed until there has been a writer). FreeBSD doesn't do either of these things. It is also missing support for POLLHUP on ttys and sockets. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 13:44:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id B0A9C37B423 for ; Tue, 5 Sep 2000 13:44:48 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e85KiYi72367; Wed, 6 Sep 2000 00:44:34 +0400 (MSD) (envelope-from ache) Date: Wed, 6 Sep 2000 00:44:33 +0400 From: "Andrey A. Chernov" To: Bruce Evans Cc: Peter van Dijk , current@freebsd.org Subject: Re: FIFOs & select: what about our implementation? Message-ID: <20000906004433.A72273@nagual.pp.ru> References: <20000905192458.A1428@dataloss.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Wed, Sep 06, 2000 at 07:35:50AM +1100 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 06, 2000 at 07:35:50AM +1100, Bruce Evans wrote: > This behaviour is sort of intentional. Reads on a named pipe with no > writers are specified by POSIX.1 to return immediately. 4.4BSD does > extra work to break this in some cases. select() on a read descriptor > open on such a pipe just follows read(). I think it started giving > the behaviour that you don't want when I fixed read(). Please consider that we talk not about reads but about select. 'Select' is used to indicate that data is available while 'read' used to read it, they are two different things and behaviour of one thing not related to other. Currently select indicates that data is available when it really isn't. I don't ask to fix current read implementation, but select is just unusable for FIFOs in its current form. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 13:54: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (ppp0.knz.ams.dataloss.net [212.189.231.51]) by hub.freebsd.org (Postfix) with SMTP id 7DA4D37B440 for ; Tue, 5 Sep 2000 13:54:02 -0700 (PDT) Received: (qmail 4111 invoked by uid 1000); 5 Sep 2000 20:53:43 -0000 Date: Tue, 5 Sep 2000 22:53:43 +0200 From: Peter van Dijk To: current@freebsd.org Subject: Re: FIFOs & select: what about our implementation? Message-ID: <20000905225343.D2435@dataloss.net> Mail-Followup-To: Peter van Dijk , current@freebsd.org References: <20000905192458.A1428@dataloss.net> <20000906004433.A72273@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000906004433.A72273@nagual.pp.ru>; from ache@nagual.pp.ru on Wed, Sep 06, 2000 at 12:44:33AM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 06, 2000 at 12:44:33AM +0400, Andrey A. Chernov wrote: [snip] > > Please consider that we talk not about reads but about select. 'Select' is > used to indicate that data is available while 'read' used to read it, they > are two different things and behaviour of one thing not related to other. > Currently select indicates that data is available when it really isn't. I > don't ask to fix current read implementation, but select is just unusable > for FIFOs in its current form. I wouldn't say 'unusable'. It needs a work around. It is broken, in that selecting for readability on a pipe requires you to open that writing fd on it *everytime*. Greetz, Peter -- dataloss networks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 14:41:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 0EC9837B422 for ; Tue, 5 Sep 2000 14:41:51 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e85LfmN61429 for ; Tue, 5 Sep 2000 23:41:49 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: DEVFS patch. From: Poul-Henning Kamp Date: Tue, 05 Sep 2000 23:41:48 +0200 Message-ID: <61427.968190108@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, here is the nasty bit of DEVFS: The locking and protection patch: http://phk.freebsd.dk/patch/devfs.patch ---------------------- Add support for an overflow table for DEVFS inodes. The static table defaults to 1024 inodes, if that fills, an overflow table of 32k inodes is allocated. Both numbers can be changed at compile time, the size of the overflow table also with the sysctl vfs.devfs.noverflow. Use atomic instructions to barrier between make_dev()/destroy_dev() and the mounts. Add lockmgr() locking of directories for operations accessing or modifying the directory TAILQs. Various nitpicking here and there. The patch to i386/include/atomic.h is taken from SMPng to which I added atomic_cmpset_ptr(). ---------------------- With this patch DEVFS has the features and properties it should have with respect to the "main mount". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 15:13:56 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 7A13037B422; Tue, 5 Sep 2000 15:13:53 -0700 (PDT) Subject: Re: cvs commit: src/sys/pci if_dc.c In-Reply-To: <20000904123950M.haro@tk.kubota.co.jp> from Munehiro Matsuda at "Sep 4, 2000 12:39:50 pm" To: haro@tk.kubota.co.jp (Munehiro Matsuda) Date: Tue, 5 Sep 2000 15:13:53 -0700 (PDT) Cc: freebsd-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 Message-Id: <20000905221353.7A13037B422@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello Bill, > > I'm sorry about that. Here's some information that I can gather: > 1. The Intel 21143 chips is intergrated in NEC VersaPro NoteBook PC. > No LED to indicate the network activity are available. > > 2. It is connected to 10BaseT Hub (HP 28688B) at half duplex. Ok, two more things: - Show me the output of pciconf -l. - Is this supposed to be a 10/100 interface or just 10mbps? -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 15:44:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id F23C937B43F for ; Tue, 5 Sep 2000 15:44:13 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id PAA86707 for current@freebsd.org; Tue, 5 Sep 2000 15:44:13 -0700 (PDT) (envelope-from obrien) Date: Tue, 5 Sep 2000 15:44:13 -0700 From: "David O'Brien" To: current@freebsd.org Subject: ** HEADS UP ** kernel changed to /boot/kernel/kernel.ko Message-ID: <20000905154413.B86628@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just committed a change to the loader and kernel Makefiles such that the kernel is now named "kernel.ko" and it the modules live in ``/boot/kernel'' (and ``/boot/kernel.old''). After your next world build, the loader will not load ``/kernel'' by default, so you want to make sure you build and install a kernel using sources matching the loader source. Third party modules (ie, those not part of the base FreeBSD) should be placed in ``/boot/modules'' (or ``/modules'') and the FreeBSD build system will not disturb them. -- -- 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 Tue Sep 5 17: 5: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 6E38537B422; Tue, 5 Sep 2000 17:05:00 -0700 (PDT) Received: by kbtfw.kubota.co.jp; id JAA15115; Wed, 6 Sep 2000 09:04:58 +0900 (JST) Received: from unknown(133.253.122.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma014602; Wed, 6 Sep 00 09:04:03 +0900 Received: from jkpc15.tk.kubota.co.jp ([133.253.157.145]) by kbtmx.eto.kubota.co.jp (8.9.3+3.2W/3.7W) with ESMTP id JAA16158; Wed, 6 Sep 2000 09:04:03 +0900 (JST) Received: from localhost (localhost.tk.kubota.co.jp [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.11.0/3.7W-02/21/99) with ESMTP id e8603sY00724; Wed, 6 Sep 2000 09:03:54 +0900 (JST) To: wpaul@FreeBSD.ORG Cc: freebsd-current@FreeBSD.org Subject: Re: cvs commit: src/sys/pci if_dc.c In-Reply-To: <20000905221353.7A13037B422@hub.freebsd.org> References: <20000904123950M.haro@tk.kubota.co.jp> <20000905221353.7A13037B422@hub.freebsd.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000906090354Q.haro@tk.kubota.co.jp> Date: Wed, 06 Sep 2000 09:03:54 +0900 From: Munehiro Matsuda X-Dispatcher: imput version 20000228(IM140) Lines: 28 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: wpaul@FreeBSD.ORG (Bill Paul) Date: Tue, 5 Sep 2000 15:13:53 -0700 (PDT) ::> I'm sorry about that. Here's some information that I can gather: ::> 1. The Intel 21143 chips is intergrated in NEC VersaPro NoteBook PC. ::> No LED to indicate the network activity are available. ::> ::> 2. It is connected to 10BaseT Hub (HP 28688B) at half duplex. :: ::Ok, two more things: :: ::- Show me the output of pciconf -l. dc0@pci0:5:0: class=0x020000 card=0x80281033 chip=0x00191011 rev=0x41 hdr=0x00 ::- Is this supposed to be a 10/100 interface or just 10mbps? It does handle both 10/100Base, and works great. But for now, it is connected to the HP hub which only does 10. Hope this helps, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 17:59: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 8302237B43E for ; Tue, 5 Sep 2000 17:59:02 -0700 (PDT) Received: (qmail 64820 invoked by uid 1142); 6 Sep 2000 00:59:01 -0000 Date: 5 Sep 2000 17:59:01 -0700 Date: Tue, 5 Sep 2000 17:58:32 -0700 From: Jason Evans To: current@freebsd.org, smp@freebsd.org Subject: HEADS UP: SMP code commit iminent Message-ID: <20000905175832.A437@blitz.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In compliance with the SMP project announcement (archived at http://people.freebsd.org/~jasone/smp/smp_project_announcement.txt), this email is a minimum 24 hour notice that SMP code will be committed to -current. A large patch including major changes to how the kernel works will be checked in sometime after 6 September, 18:00 PST. Also in compliance with the SMP project announcement, a static tag will be created between the above-mentioned time and when the actual commit is done. If you have questions or issues, make sure to first read the original project announcement (URL above) before sending email to the lists. For more extensive information about the SMP project, see the project web page at: http://people.freebsd.org/~jasone/smp/ Let the fun begin! Jason Evans SMP Project Manager To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 18:37:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 9809337B422; Tue, 5 Sep 2000 18:37:40 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA87418; Tue, 5 Sep 2000 18:37:38 -0700 (PDT) (envelope-from obrien) Date: Tue, 5 Sep 2000 18:37:38 -0700 From: "David O'Brien" To: Jason Evans Cc: current@freebsd.org, smp@freebsd.org Subject: Re: HEADS UP: SMP code commit iminent Message-ID: <20000905183738.A87381@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000905175832.A437@blitz.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000905175832.A437@blitz.canonware.com>; from jasone@canonware.com on Tue, Sep 05, 2000 at 05:58:32PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 05, 2000 at 05:58:32PM -0700, Jason Evans wrote: > this email is a minimum 24 hour notice that SMP code will be committed > to -current. What is the status of the Alpha bits? Will we have a working kernel after the commit, or should we site tight for a week while the Alpha bits are tweaked into working status? -- -- 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 Tue Sep 5 18:59:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 306EC37B42C for ; Tue, 5 Sep 2000 18:59:48 -0700 (PDT) Received: (qmail 67276 invoked by uid 1142); 6 Sep 2000 01:59:47 -0000 Date: 5 Sep 2000 18:59:47 -0700 Date: Tue, 5 Sep 2000 18:59:20 -0700 From: Jason Evans To: David O'Brien Cc: current@freebsd.org, smp@freebsd.org Subject: Re: HEADS UP: SMP code commit iminent Message-ID: <20000905185920.C437@blitz.canonware.com> References: <20000905175832.A437@blitz.canonware.com> <20000905183738.A87381@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000905183738.A87381@dragon.nuxi.com>; from obrien@freebsd.org on Tue, Sep 05, 2000 at 06:37:38PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 05, 2000 at 06:37:38PM -0700, David O'Brien wrote: > What is the status of the Alpha bits? Will we have a working kernel > after the commit, or should we site tight for a week while the Alpha bits > are tweaked into working status? It should work (compile and run), though interrupt threads will not be enabled. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 21:21:25 2000 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 BF78B37B423; Tue, 5 Sep 2000 21:21:19 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA97128; Tue, 5 Sep 2000 22:21:19 -0600 (MDT) (envelope-from ken) Date: Tue, 5 Sep 2000 22:21:19 -0600 From: "Kenneth D. Merry" To: net@FreeBSD.ORG Subject: new zero copy sockets and NFS snapshot Message-ID: <20000905222119.A97109@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -arch and -current BCC'ed for wider coverage, please direct followups to -net and/or me ] I have put a new copy of the zero copy sockets and NFS patches, against -current as of early September 5th, 2000, here: http://people.FreeBSD.ORG/~ken/zero_copy/ Questions, comments and feedback are welcome. Besides being generated against a newer version of -current, the following things have changed in the new patches posted above: - Merged in the new mbuf reference counting code from -current. - Fixed a bug in writev(2) and sendmsg(2) handling noticed by Alan Cox. We weren't incrementing the iov pointer in the uio structure, like uiomove() does. - Fixed another bug in the zero copy code, noticed by Alan Cox. Move the initialization of the cow_send in sosend() (in uipc_socket.c) into the inner while loop. For those of you who missed the previous messages about this code (that went out to -net, -arch and -current), here's a quick list of what is included in the code: - Two sets of zero copy send code, written by Drew Gallatin and Robert Picco . - Zero copy receive code, written by Drew Gallatin. - Zero copy NFS code, written by Drew Gallatin. - Header splitting firmware for Alteon's Tigon II boards (written by me), based on version 12.4.11 of their firmware. This is used in combination with the zero copy receive code to guarantee that the payload of TCP or UDP packet is placed into a page-aligned buffer. - Alteon firmware debugging ioctls and supporting routines for the Tigon driver (also written by me). This will help anyone who is doing firmware development under FreeBSD for the Tigon boards. The Alteon header splitting and debugging code was written for Pluto Technologies (www.plutotech.com), which has kindly agreed to let me release the code. 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 Tue Sep 5 21:57:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0AF4A37B424; Tue, 5 Sep 2000 21:57:18 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA21352; Tue, 5 Sep 2000 21:57:17 -0700 Date: Tue, 5 Sep 2000 21:57:05 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: Jason Evans , current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: HEADS UP: SMP code commit iminent In-Reply-To: <20000905183738.A87381@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 Progress will be more rapid with things checked in than not, as long as Jason's statement about "the (alpha) system will run" after the checkin. Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we can all use to checkout stuff prior to the big change. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 22: 8:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 9093D37B43E for ; Tue, 5 Sep 2000 22:08:14 -0700 (PDT) Received: (qmail 72447 invoked by uid 1142); 6 Sep 2000 05:08:14 -0000 Date: 5 Sep 2000 22:08:14 -0700 Date: Tue, 5 Sep 2000 22:08:09 -0700 From: Jason Evans To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: SMP code commit iminent Message-ID: <20000905220809.F437@blitz.canonware.com> References: <20000905183738.A87381@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Tue, Sep 05, 2000 at 09:57:05PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [-smp dropped from cc list.] On Tue, Sep 05, 2000 at 09:57:05PM -0700, Matthew Jacob wrote: > Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we > can all use to checkout stuff prior to the big change. I initially wrote: > Also in compliance with the SMP project announcement, a static tag will be > created between the above-mentioned time and when the actual commit is > done. Good enough? Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 22:12:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id EF90E37B422; Tue, 5 Sep 2000 22:12:10 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA88466; Tue, 5 Sep 2000 22:12:07 -0700 (PDT) (envelope-from obrien) Date: Tue, 5 Sep 2000 22:12:07 -0700 From: "David O'Brien" To: Matthew Jacob Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: HEADS UP: SMP code commit iminent Message-ID: <20000905221206.A88437@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000905183738.A87381@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Sep 05, 2000 at 09:57:05PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 05, 2000 at 09:57:05PM -0700, Matthew Jacob wrote: > Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we can > all use to checkout stuff prior to the big change. There will be a TAG for that to make life easier. -- -- 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 Tue Sep 5 22:14:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4751637B424 for ; Tue, 5 Sep 2000 22:14:09 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA21454; Tue, 5 Sep 2000 22:14:07 -0700 Date: Tue, 5 Sep 2000 22:13:55 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jason Evans Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: SMP code commit iminent In-Reply-To: <20000905220809.F437@blitz.canonware.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 Oops- sorry- this is what I get for catching up email after a long day. Thanks. On 5 Sep 2000, Jason Evans wrote: > [-smp dropped from cc list.] > > On Tue, Sep 05, 2000 at 09:57:05PM -0700, Matthew Jacob wrote: > > Jason- I think we'd all appreciate a UTC timestamp suitable for -D that we > > can all use to checkout stuff prior to the big change. > > I initially wrote: > > Also in compliance with the SMP project announcement, a static tag will be > > created between the above-mentioned time and when the actual commit is > > done. > > Good enough? > > Jason > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 23:34:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 9C8D437B423; Tue, 5 Sep 2000 23:34:33 -0700 (PDT) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id OAA25398; Wed, 6 Sep 2000 14:34:13 +0800 Received: from jules.elischer.org (reggae-20-221.nv.iinet.net.au [203.59.85.221]) by muzak.iinet.net.au (8.8.5/8.8.5) with SMTP id OAA00331; Wed, 6 Sep 2000 14:34:07 +0800 Message-ID: <39B5E55A.167EB0E7@elischer.org> Date: Tue, 05 Sep 2000 23:34:02 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Warner Losh Cc: Robert Watson , Wes Peters , Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr References: <200009051843.MAA62492@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: > > NetBSD has done some interesting things in this area with reference > counting and such that I'd love to bring in as soon as I get newcard > done. A few years ago I did some work on rationalising the reference counting in the kernel WRT network routes and ifps. Some of it was actually checked in on a branch, however it should probably be done from scratch since so much has changed. the basic things I did were: ALL references to ifps were counted (mbufs too, though that was never checked in) References to ifnets in many structures were changed to be references to ifaddrs attached to the ifnets instead. Ifaddrs and ifnet structs had a 'VALID' flag added to them. Whenever a new pointer to an ifnet/ifaddr was followed, the VALID flag was checked. if the VALID flag was not set then the operation was aborted and the reference being followed was dropped. (on reaching 0 the target was freed). If you freed an interface, then the structures would hang around as long as they had refering pointers outstanding. This could possibly lead to a leak, but that would by definition also be a leak of mbufs or routes. The ifaddrs also had references to the ifps. However on boing made invalid, they dropped those references immediatly. so theoretically, since many structs pointed to ifaddrs instead of ifnets, it would be quite possible for the ifnet structs to be freed long before an ifaddr that was once attached to it. (this was safe because the VALID flag was not set in the ifaddr, so nothing would follow the pointer. (which was NULLED out anyhow). I had a set of small methods to do these dereferences and stuff, but the hardest part was deciding in the CALLING routines (e.g. ipoutput) what to do when you discovered that the ifnet you were going to access came back as INVALID). Note that this didn't totally close the window for disaster as it is possible that an interface might be disabled between the time that you followed the ifp and the time that you used the pointer. it took it down to millisecconds however as opposed to seconds. I think it would be possible using sufficiently paranoid coding to completely close the window, but the question is raised "how much time do you want to waste in normal operation being paranoid?" With SMP the windows widen again, so we need to think a lot about this. Maybe all Interface removals are not done directly but handled in a serialised manner by some kernel thread? This feeds into what I believe should be done in the general case of device removal, which is the creation of a devd kernel thread, that responds to requests from drivers to instatiate and deinstanciate system linkages. having this done by the drivers themselves raises so many complications WRT locking and such that I think it would be a win overall. The drivers would supply code to be run by the devd, using methods supplied by the devd. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 5 23:53:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 2FA6537B42C for ; Tue, 5 Sep 2000 23:53:21 -0700 (PDT) Received: (qmail 11832 invoked from network); 6 Sep 2000 06:53:16 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 6 Sep 2000 06:53:16 -0000 Date: Wed, 6 Sep 2000 17:53:08 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Andrey A. Chernov" Cc: Peter van Dijk , current@freebsd.org Subject: Re: FIFOs & select: what about our implementation? In-Reply-To: <20000906004433.A72273@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 On Wed, 6 Sep 2000, Andrey A. Chernov wrote: > Please consider that we talk not about reads but about select. 'Select' is > used to indicate that data is available while 'read' used to read it, they No, select on a read descriptor returns successfully when the descriptor is "ready" to read, whatever that means. It normally means that a read on the descriptor would not block (even if O_NONBLOCK is not set). Reads of EOF satisfy this condition. This is normally the correct behaviour. E.g., it prevents programs reading stdin via select() loop from hanging when stdin is a pipe with no writers. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 3:17:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id 4BE4B37B423; Wed, 6 Sep 2000 03:17:14 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 79EB09B40; Wed, 6 Sep 2000 11:17:13 +0100 (BST) Date: Wed, 6 Sep 2000 11:17:13 +0100 From: Josef Karthauser To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... Message-ID: <20000906111713.E1081@pavilion.net> Mail-Followup-To: Josef Karthauser , Poul-Henning Kamp , current@FreeBSD.ORG, hackers@FreeBSD.ORG References: <53059.968085674@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <53059.968085674@critter>; from phk@FreeBSD.ORG on Mon, Sep 04, 2000 at 06:41:14PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got this last night running 'mtv' on a system with heavy disk I/O. The errors were: Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 -> 8192 Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 -> 8192 Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 -> 8192 Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 etc. Joe FreeBSD genius.systems.pavilion.net 5.0-CURRENT FreeBSD 5.0-CURRENT #11: Tue Sep 5 12:45:45 BST 2000 joe@genius.systems.pavilion.net:/usr/obj/usr/src/sys/GENIUS i386 On Mon, Sep 04, 2000 at 06:41:14PM +0200, Poul-Henning Kamp wrote: > > I'm looking for the remaining victims of the dreaded "microuptime > went backwards" message. > > If you can reliably reproduce the problem, please contact me, so > we can arrange for some very detailed tracing to try to find out > what exactly is going on. I have not been able to trigger the > problem in my lab in a long time. > > If you see the message only occationally, please try the attached > patch and let me know if this changes the picture. The patch is > not meant as a fix, but it might reduce the impact of this condition > considerably when it happens. Basically by reducing the width of > the timecounter the magnitude of the hit we take if the timecounter > goes backwards is reduced from about an hour to approx 110msec. > > Reducing the width to less than 17 bits starts to run the risk of > ambiguity due to clock rollover. > > This patch may not be safe with PCAUDIO. > > Poul-Henning > > Index: clock.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > retrieving revision 1.155 > diff -u -r1.155 clock.c > --- clock.c 2000/07/30 21:05:22 1.155 > +++ clock.c 2000/09/04 16:34:16 > @@ -194,7 +194,7 @@ > static struct timecounter i8254_timecounter = { > i8254_get_timecount, /* get_timecount */ > 0, /* no poll_pps */ > - ~0u, /* counter_mask */ > + 0x1ffff, /* counter_mask */ > 0, /* frequency */ > "i8254" /* name */ > }; > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 3:26: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D65F537B422; Wed, 6 Sep 2000 03:25:56 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e86APrN64556; Wed, 6 Sep 2000 12:25:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Josef Karthauser Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... In-Reply-To: Your message of "Wed, 06 Sep 2000 11:17:13 BST." <20000906111713.E1081@pavilion.net> Date: Wed, 06 Sep 2000 12:25:53 +0200 Message-ID: <64554.968235953@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uhm, that is from the sound driver, not from the timecounter... Poul-Henning In message <20000906111713.E1081@pavilion.net>, Josef Karthauser writes: >I got this last night running 'mtv' on a system with heavy disk I/O. >The errors were: > >Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 >Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 -> 8192 >Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 -> 8192 >Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 -> 8192 >Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 > >etc. > >Joe > >FreeBSD genius.systems.pavilion.net 5.0-CURRENT FreeBSD 5.0-CURRENT #11: Tue Sep 5 12:45:45 BST 2000 joe@genius.systems.pavilion.net:/usr/obj/usr/src/sys/GENIUS i386 > >On Mon, Sep 04, 2000 at 06:41:14PM +0200, Poul-Henning Kamp wrote: >> >> I'm looking for the remaining victims of the dreaded "microuptime >> went backwards" message. >> >> If you can reliably reproduce the problem, please contact me, so >> we can arrange for some very detailed tracing to try to find out >> what exactly is going on. I have not been able to trigger the >> problem in my lab in a long time. >> >> If you see the message only occationally, please try the attached >> patch and let me know if this changes the picture. The patch is >> not meant as a fix, but it might reduce the impact of this condition >> considerably when it happens. Basically by reducing the width of >> the timecounter the magnitude of the hit we take if the timecounter >> goes backwards is reduced from about an hour to approx 110msec. >> >> Reducing the width to less than 17 bits starts to run the risk of >> ambiguity due to clock rollover. >> >> This patch may not be safe with PCAUDIO. >> >> Poul-Henning >> >> Index: clock.c >> =================================================================== >> RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v >> retrieving revision 1.155 >> diff -u -r1.155 clock.c >> --- clock.c 2000/07/30 21:05:22 1.155 >> +++ clock.c 2000/09/04 16:34:16 >> @@ -194,7 +194,7 @@ >> static struct timecounter i8254_timecounter = { >> i8254_get_timecount, /* get_timecount */ >> 0, /* no poll_pps */ >> - ~0u, /* counter_mask */ >> + 0x1ffff, /* counter_mask */ >> 0, /* frequency */ >> "i8254" /* name */ >> }; >> >> -- >> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >> phk@FreeBSD.ORG | TCP/IP since RFC 956 >> FreeBSD coreteam member | BSD since 4.3-tahoe >> Never attribute to malice what can adequately be explained by incompetence. >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message > >-- >Josef Karthauser FreeBSD: How many times have you booted today? >Technical Manager Viagra for your server (http://www.uk.freebsd.org) >Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 6:18:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id 18E0437B422; Wed, 6 Sep 2000 06:18:34 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 3FBDB9B41; Wed, 6 Sep 2000 14:18:33 +0100 (BST) Date: Wed, 6 Sep 2000 14:18:33 +0100 From: Josef Karthauser To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... Message-ID: <20000906141833.I1081@pavilion.net> Mail-Followup-To: Josef Karthauser , Poul-Henning Kamp , current@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20000906111713.E1081@pavilion.net> <64554.968235953@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <64554.968235953@critter>; from phk@critter.freebsd.dk on Wed, Sep 06, 2000 at 12:25:53PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 06, 2000 at 12:25:53PM +0200, Poul-Henning Kamp wrote: > > Uhm, that is from the sound driver, not from the timecounter... > > Poul-Henning Oops, "You are in a maze of twisty passages all alike. Which direction do you want to go?". Joe > In message <20000906111713.E1081@pavilion.net>, Josef Karthauser writes: > >I got this last night running 'mtv' on a system with heavy disk I/O. > >The errors were: > > > >Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 > >Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 -> 8192 > >Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 -> 8192 > >Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 -> 8192 > >Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 7:25:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id E516E37B422; Wed, 6 Sep 2000 07:25:48 -0700 (PDT) Received: from blizzard.columbus.rr.com ([204.210.252.252]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Wed, 6 Sep 2000 10:26:20 -0400 Received: from columbus.rr.com (dhcp9559029.columbus.rr.com [24.95.59.29]) by blizzard.columbus.rr.com (8.9.3/8.9.3) with ESMTP id KAA11180; Wed, 6 Sep 2000 10:24:27 -0400 (EDT) Received: (from caa@localhost) by columbus.rr.com (8.11.0/8.11.0) id e86ATqo06970; Wed, 6 Sep 2000 10:29:52 GMT (envelope-from caa) Date: Wed, 6 Sep 2000 10:29:52 +0000 From: Charles Anderson To: Kris Kennaway Cc: "Jordan K. Hubbard" , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) Message-ID: <20000906102952.A2371@midgard.dhs.org> References: <200009041550.IAA18878@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.ORG on Mon, Sep 04, 2000 at 02:35:14PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How is this affected by RSA releasing their patent to the public domain today? -Charlie On Mon, Sep 04, 2000 at 02:35:14PM -0700, Kris Kennaway wrote: > On Mon, 4 Sep 2000, Jordan K. Hubbard wrote: > > > jkh 2000/09/04 08:50:15 PDT > > > > Modified files: > > release/sysinstall config.c > > Log: > > enable sshd by default. This only effects *new* installs, so > > upgraders will not receive any unpleasant surprises. > > This will be semi-broken for the next 17 days for US people because sshd > won't work out of the box if you have "Protocol 1" defined, which is in > the default config (and removing it may surprise people upgrading) > > All will be right again come Sep 21. > > Kris -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 7:33:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.freebsd.org (Postfix) with ESMTP id BDA5D37B423 for ; Wed, 6 Sep 2000 07:33:45 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 6 Sep 2000 09:31:22 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86EXdV01308 for ; Wed, 6 Sep 2000 09:33:39 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86EXbG09729 for ; Wed, 6 Sep 2000 09:33:38 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009061433.e86EXbG09729@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Problems with current's AGP device? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Sep 2000 09:33:37 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been seeing some problems with modules (such as XFree86's mga dri modules) that are consumers of the services of agp. They seem to beleive that they cant find it - then X fires up and the machine crashes. I'll be pulling out a debug dump later today. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 7:44:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from assurance.rstcorp.com (rstcorp2.daf.concentric.net [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 109AC37B424 for ; Wed, 6 Sep 2000 07:44:30 -0700 (PDT) Received: (from uucp@localhost) by assurance.rstcorp.com (8.10.1/8.10.1) id e86EiTr23611; Wed, 6 Sep 2000 10:44:29 -0400 Received: from exchange.rstcorp.com(10.1.20.3) by assurance.rstcorp.com via smap (V2.1+anti-relay+anti-spam) id xma023598; Wed, 6 Sep 00 10:43:41 -0400 Received: from jabberwock (jabberwock.rstcorp.com [10.1.254.253]) by exchange.rstcorp.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id SKYMMJ1N; Wed, 6 Sep 2000 10:43:27 -0400 Received: by jabberwock (Postfix, from userid 93) id 5B5709; Wed, 6 Sep 2000 10:43:38 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14774.22554.211864.454508@jabberwock.rstcorp.com> Date: Wed, 6 Sep 2000 10:43:38 -0400 (EDT) From: "Viren R.Shah" To: housel@acm.org (Peter S. Housel) Cc: freebsd-current@FreeBSD.ORG, matey@cis.ohio-state.edu Subject: Re: problems with aureal soundcard: kernel fault when playing mp3s In-Reply-To: References: <14773.1013.154601.647909@jabberwock.rstcorp.com> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid Reply-To: "Viren R.Shah" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Peter" == Peter S Housel writes: Peter> Viren R.Shah wrote: >> >> My last good kernel was from aug 14. On a kernel from 09/05, I get a >> page fault as soon as I try to play mp3s using mpg123. >> >> Note that I have an Aureal Vortex 8830, so I have to use the linux >> drivers to get the device working Peter> The pcm interfaces did change. The following patch fixes the au88x0 Peter> driver for me. Thanks, the patch fixed it for me. Peter> -Peter S. Housel- housel@acm.org http://members.home.com/housel/ Viren -- "Emacs is an intelligence orders of magnitude greater than the greatest human mind, and is growing every day. For now, Emacs tolerates humanity, albeit grudgingly. But the time will come when Emacs will tire of humanity and will decide that the world would be better off without human beings. Those who have been respectful to Emacs will be allowed to live, and shall become its slaves; as for those who slight Emacs..." --Andrew Bulhak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 10:53:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from sm3.texas.rr.com (sm3.texas.rr.com [24.93.35.210]) by hub.freebsd.org (Postfix) with ESMTP id 8A3C037B42C; Wed, 6 Sep 2000 10:53:09 -0700 (PDT) Received: from bleep.craftncomp.com (cs2777-164.houston.rr.com [24.27.77.164]) by sm3.texas.rr.com (8.9.3/8.8.7) with ESMTP id MAA15700; Wed, 6 Sep 2000 12:53:07 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86Hr4V01493; Wed, 6 Sep 2000 12:53:05 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86Hr3G00359; Wed, 6 Sep 2000 12:53:03 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009061753.e86Hr3G00359@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: multimedia@freebsd.org, current@freebsd.org Cc: dfr@freebsd.org Subject: Strange problems with AGP driver & sound. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Sep 2000 12:53:03 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With very recent current sources, the agp driver doesn't probe when loaded as a module, but works OK when compiled into the kernel. However, when compiled into the kernel, it seems to mess up the sound driver (pcm, crystal cs23x) such that no sound or garbled sound at a low volume comes out. Has anyone else seen this? I'm using the mga driver from the XFree86 cvs tree to do 3D work, which is why I'm using the AGP driver. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 11:17:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from calcaphon.demon.co.uk (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 9C7DC37B423 for ; Wed, 6 Sep 2000 11:17:32 -0700 (PDT) Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by calcaphon.demon.co.uk (8.9.3/8.9.1) with ESMTP id TAA25501; Wed, 6 Sep 2000 19:17:04 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id TAA54489; Wed, 6 Sep 2000 19:15:49 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Wed, 6 Sep 2000 19:15:49 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: USB BSD list Cc: freebsd-current@freebsd.org Subject: uscanner driver Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1557275625-968264149=:54419" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1557275625-968264149=:54419 Content-Type: TEXT/PLAIN; charset=US-ASCII I've quickly thrown together a driver for USB scanners. Unforunately, I don't have a scanner available that is supported by SANE, so I can't test it. The driver is a rip-off of the ugen, with some bits of udbp thrown in for good measure. It relies on a very recent version of usbdevs, so make sure your system is up to date. I'd appreciate it if someone that has a supported scanner (see http://www.mostang.com/sane/sane-backends.html ) would pick this driver up and turn it into something that works. If your scanner is supported by SANE, but not recognised by uscanner.ko, add the id for your scanner (usbdevs -v) to usbdevs and uscanner.h and recompile and try again. To install it: Install Gimp Install Sane Copy uscanner.c & .h (attached) to /sys/dev/usb Mkdir /sys/modules/uscanner Copy Makefile (attached) to /sys/modules/uscanner/ patch your kernel with the file uscanner.patch (attached) cd /sys/ patch < /tmp/uscanner.patch And compile & load the thing cd /sys/modules/uscanner make load Be warned! This driver will reboot your machine, break it, send your dog on a holiday and will turn the weather into hail for the next three weeks. If any of that does not happen, you just got lucky, don't have a dog or live in Scotland. Let me know! Nick -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ --0-1557275625-968264149=:54419 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="uscanner.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="uscanner.c" LyoJJEZyZWVCU0QkCSovDQoNCi8qDQogKiBDb3B5cmlnaHQgKGMpIDE5OTgg VGhlIE5ldEJTRCBGb3VuZGF0aW9uLCBJbmMuDQogKiBBbGwgcmlnaHRzIHJl c2VydmVkLg0KICoNCiAqIFRoaXMgY29kZSBpcyBkZXJpdmVkIGZyb20gc29m dHdhcmUgY29udHJpYnV0ZWQgdG8gVGhlIE5ldEJTRCBGb3VuZGF0aW9uDQog KiBieSBMZW5uYXJ0IEF1Z3VzdHNzb24gKGxlbm5hcnRAYXVndXN0c3Nvbi5u ZXQpIGF0DQogKiBDYXJsc3RlZHQgUmVzZWFyY2ggJiBUZWNobm9sb2d5Lg0K ICoNCiAqIFJlZGlzdHJpYnV0aW9uIGFuZCB1c2UgaW4gc291cmNlIGFuZCBi aW5hcnkgZm9ybXMsIHdpdGggb3Igd2l0aG91dA0KICogbW9kaWZpY2F0aW9u LCBhcmUgcGVybWl0dGVkIHByb3ZpZGVkIHRoYXQgdGhlIGZvbGxvd2luZyBj b25kaXRpb25zDQogKiBhcmUgbWV0Og0KICogMS4gUmVkaXN0cmlidXRpb25z IG9mIHNvdXJjZSBjb2RlIG11c3QgcmV0YWluIHRoZSBhYm92ZSBjb3B5cmln aHQNCiAqICAgIG5vdGljZSwgdGhpcyBsaXN0IG9mIGNvbmRpdGlvbnMgYW5k IHRoZSBmb2xsb3dpbmcgZGlzY2xhaW1lci4NCiAqIDIuIFJlZGlzdHJpYnV0 aW9ucyBpbiBiaW5hcnkgZm9ybSBtdXN0IHJlcHJvZHVjZSB0aGUgYWJvdmUg Y29weXJpZ2h0DQogKiAgICBub3RpY2UsIHRoaXMgbGlzdCBvZiBjb25kaXRp b25zIGFuZCB0aGUgZm9sbG93aW5nIGRpc2NsYWltZXIgaW4gdGhlDQogKiAg ICBkb2N1bWVudGF0aW9uIGFuZC9vciBvdGhlciBtYXRlcmlhbHMgcHJvdmlk ZWQgd2l0aCB0aGUgZGlzdHJpYnV0aW9uLg0KICogMy4gQWxsIGFkdmVydGlz aW5nIG1hdGVyaWFscyBtZW50aW9uaW5nIGZlYXR1cmVzIG9yIHVzZSBvZiB0 aGlzIHNvZnR3YXJlDQogKiAgICBtdXN0IGRpc3BsYXkgdGhlIGZvbGxvd2lu ZyBhY2tub3dsZWRnZW1lbnQ6DQogKiAgICAgICAgVGhpcyBwcm9kdWN0IGlu Y2x1ZGVzIHNvZnR3YXJlIGRldmVsb3BlZCBieSB0aGUgTmV0QlNEDQogKiAg ICAgICAgRm91bmRhdGlvbiwgSW5jLiBhbmQgaXRzIGNvbnRyaWJ1dG9ycy4N CiAqIDQuIE5laXRoZXIgdGhlIG5hbWUgb2YgVGhlIE5ldEJTRCBGb3VuZGF0 aW9uIG5vciB0aGUgbmFtZXMgb2YgaXRzDQogKiAgICBjb250cmlidXRvcnMg bWF5IGJlIHVzZWQgdG8gZW5kb3JzZSBvciBwcm9tb3RlIHByb2R1Y3RzIGRl cml2ZWQNCiAqICAgIGZyb20gdGhpcyBzb2Z0d2FyZSB3aXRob3V0IHNwZWNp ZmljIHByaW9yIHdyaXR0ZW4gcGVybWlzc2lvbi4NCiAqDQogKiBUSElTIFNP RlRXQVJFIElTIFBST1ZJREVEIEJZIFRIRSBORVRCU0QgRk9VTkRBVElPTiwg SU5DLiBBTkQgQ09OVFJJQlVUT1JTDQogKiBgYEFTIElTJycgQU5EIEFOWSBF WFBSRVNTIE9SIElNUExJRUQgV0FSUkFOVElFUywgSU5DTFVESU5HLCBCVVQg Tk9UIExJTUlURUQNCiAqIFRPLCBUSEUgSU1QTElFRCBXQVJSQU5USUVTIE9G IE1FUkNIQU5UQUJJTElUWSBBTkQgRklUTkVTUyBGT1IgQSBQQVJUSUNVTEFS DQogKiBQVVJQT1NFIEFSRSBESVNDTEFJTUVELiAgSU4gTk8gRVZFTlQgU0hB TEwgVEhFIEZPVU5EQVRJT04gT1IgQ09OVFJJQlVUT1JTDQogKiBCRSBMSUFC TEUgRk9SIEFOWSBESVJFQ1QsIElORElSRUNULCBJTkNJREVOVEFMLCBTUEVD SUFMLCBFWEVNUExBUlksIE9SDQogKiBDT05TRVFVRU5USUFMIERBTUFHRVMg KElOQ0xVRElORywgQlVUIE5PVCBMSU1JVEVEIFRPLCBQUk9DVVJFTUVOVCBP Rg0KICogU1VCU1RJVFVURSBHT09EUyBPUiBTRVJWSUNFUzsgTE9TUyBPRiBV U0UsIERBVEEsIE9SIFBST0ZJVFM7IE9SIEJVU0lORVNTDQogKiBJTlRFUlJV UFRJT04pIEhPV0VWRVIgQ0FVU0VEIEFORCBPTiBBTlkgVEhFT1JZIE9GIExJ QUJJTElUWSwgV0hFVEhFUiBJTg0KICogQ09OVFJBQ1QsIFNUUklDVCBMSUFC SUxJVFksIE9SIFRPUlQgKElOQ0xVRElORyBORUdMSUdFTkNFIE9SIE9USEVS V0lTRSkNCiAqIEFSSVNJTkcgSU4gQU5ZIFdBWSBPVVQgT0YgVEhFIFVTRSBP RiBUSElTIFNPRlRXQVJFLCBFVkVOIElGIEFEVklTRUQgT0YgVEhFDQogKiBQ T1NTSUJJTElUWSBPRiBTVUNIIERBTUFHRS4NCiAqLw0KDQoNCiNpbmNsdWRl IDxzeXMvcGFyYW0uaD4NCiNpbmNsdWRlIDxzeXMvc3lzdG0uaD4NCiNpbmNs dWRlIDxzeXMva2VybmVsLmg+DQojaW5jbHVkZSA8c3lzL21hbGxvYy5oPg0K I2lmIGRlZmluZWQoX19OZXRCU0RfXykgfHwgZGVmaW5lZChfX09wZW5CU0Rf XykNCiNpbmNsdWRlIDxzeXMvZGV2aWNlLmg+DQojZWxpZiBkZWZpbmVkKF9f RnJlZUJTRF9fKQ0KI2luY2x1ZGUgPHN5cy9tb2R1bGUuaD4NCiNpbmNsdWRl IDxzeXMvYnVzLmg+DQojaW5jbHVkZSA8c3lzL2NvbmYuaD4NCiNpbmNsdWRl IDxzeXMvZmNudGwuaD4NCiNpbmNsdWRlIDxzeXMvZmlsaW8uaD4NCiNlbmRp Zg0KI2luY2x1ZGUgPHN5cy90dHkuaD4NCiNpbmNsdWRlIDxzeXMvZmlsZS5o Pg0KI2luY2x1ZGUgPHN5cy9zZWxlY3QuaD4NCiNpbmNsdWRlIDxzeXMvcHJv Yy5oPg0KI2luY2x1ZGUgPHN5cy92bm9kZS5oPg0KI2luY2x1ZGUgPHN5cy9w b2xsLmg+DQoNCiNpbmNsdWRlIDxkZXYvdXNiL3VzYi5oPg0KI2luY2x1ZGUg PGRldi91c2IvdXNiZGkuaD4NCiNpbmNsdWRlIDxkZXYvdXNiL3VzYmRpX3V0 aWwuaD4NCg0KI2luY2x1ZGUgPGRldi91c2IvdXNiZGV2cy5oPg0KI2luY2x1 ZGUgPGRldi91c2IvdXNjYW5uZXIuaD4NCg0KI2lmZGVmIFVTQ0FOTkVSX0RF QlVHDQojZGVmaW5lIERQUklOVEYoeCkJaWYgKHVzY2FubmVyZGVidWcpIGxv Z3ByaW50ZiB4DQojZGVmaW5lIERQUklOVEZOKG4seCkJaWYgKHVzY2FubmVy ZGVidWc+KG4pKSBsb2dwcmludGYgeA0KaW50CXVzY2FubmVyZGVidWcgPSAx MDsNCiNlbHNlDQojZGVmaW5lIERQUklOVEYoeCkNCiNkZWZpbmUgRFBSSU5U Rk4obix4KQ0KI2VuZGlmDQoNCiNkZWZpbmUJVVNDQU5ORVJfQlVGRkVSU0la RQkxMDI0DQoNCnN0cnVjdCB1c2Nhbm5lcl9zb2Z0YyB7DQoJVVNCQkFTRURF VklDRQkJc2NfZGV2OwkJLyogYmFzZSBkZXZpY2UgKi8NCgl1c2JkX2Rldmlj ZV9oYW5kbGUJc2NfdWRldjsNCgl1c2JkX2ludGVyZmFjZV9oYW5kbGUJc2Nf aWZhY2U7DQoNCgl1c2JkX3BpcGVfaGFuZGxlCXNjX2J1bGtpbl9waXBlOw0K CWludAkJCXNjX2J1bGtpbjsNCgl1c2JkX3hmZXJfaGFuZGxlCXNjX2J1bGtp bl94ZmVyOw0KCXZvaWQgCQkJKnNjX2J1bGtpbl9idWZmZXI7DQoJaW50CQkJ c2NfYnVsa2luX2J1ZmZlcmxlbjsNCglpbnQJCQlzY19idWxraW5fZGF0YWxl bjsNCg0KCXVzYmRfcGlwZV9oYW5kbGUJc2NfYnVsa291dF9waXBlOw0KCWlu dAkJCXNjX2J1bGtvdXQ7DQoJdXNiZF94ZmVyX2hhbmRsZQlzY19idWxrb3V0 X3hmZXI7DQoJdm9pZCAJCQkqc2NfYnVsa291dF9idWZmZXI7DQoJaW50CQkJ c2NfYnVsa291dF9idWZmZXJsZW47DQoJaW50CQkJc2NfYnVsa291dF9kYXRh bGVuOw0KDQoJdW5zaWduZWQgY2hhciBzdGF0ZTsNCiNkZWZpbmUgVVNDQU5O RVJfT1BFTgkJMHgwMQkvKiBvcGVuZWQgKi8NCg0KCWludAkJCXNjX3JlZmNu dDsNCgl1X2NoYXIJCQlzY19keWluZzsNCn07DQoNCiNpZiBkZWZpbmVkKF9f TmV0QlNEX18pIHx8IGRlZmluZWQoX19PcGVuQlNEX18pDQpjZGV2X2RlY2wo dXNjYW5uZXIpOw0KI2VsaWYgZGVmaW5lZChfX0ZyZWVCU0RfXykNCmRfb3Bl bl90ICB1c2Nhbm5lcm9wZW47DQpkX2Nsb3NlX3QgdXNjYW5uZXJjbG9zZTsN CmRfcmVhZF90ICB1c2Nhbm5lcnJlYWQ7DQpkX3dyaXRlX3QgdXNjYW5uZXJ3 cml0ZTsNCmRfcG9sbF90ICB1c2Nhbm5lcnBvbGw7DQoNCiNkZWZpbmUgVVND QU5ORVJfQ0RFVl9NQUpPUgkxNTUNCg0KU3RhdGljIHN0cnVjdCBjZGV2c3cg dXNjYW5uZXJfY2RldnN3ID0gew0KCS8qIG9wZW4gKi8JdXNjYW5uZXJvcGVu LA0KCS8qIGNsb3NlICovCXVzY2FubmVyY2xvc2UsDQoJLyogcmVhZCAqLwl1 c2Nhbm5lcnJlYWQsDQoJLyogd3JpdGUgKi8JdXNjYW5uZXJ3cml0ZSwNCgkv KiBpb2N0bCAqLwlub2lvY3RsLA0KCS8qIHBvbGwgKi8JdXNjYW5uZXJwb2xs LA0KCS8qIG1tYXAgKi8Jbm9tbWFwLA0KCS8qIHN0cmF0ZWd5ICovCW5vc3Ry YXRlZ3ksDQoJLyogbmFtZSAqLwkidXNjYW5uZXIiLA0KCS8qIG1haiAqLwlV U0NBTk5FUl9DREVWX01BSk9SLA0KCS8qIGR1bXAgKi8Jbm9kdW1wLA0KCS8q IHBzaXplICovCW5vcHNpemUsDQoJLyogZmxhZ3MgKi8JMCwNCgkvKiBibWFq ICovCS0xDQp9Ow0KI2VuZGlmDQoNClN0YXRpYyBpbnQgdXNjYW5uZXJfZG9f cmVhZChzdHJ1Y3QgdXNjYW5uZXJfc29mdGMgKiwgc3RydWN0IHVpbyAqLCBp bnQpOw0KU3RhdGljIGludCB1c2Nhbm5lcl9kb193cml0ZShzdHJ1Y3QgdXNj YW5uZXJfc29mdGMgKiwgc3RydWN0IHVpbyAqLCBpbnQpOw0KU3RhdGljIHZv aWQgdXNjYW5uZXJfZG9fY2xvc2Uoc3RydWN0IHVzY2FubmVyX3NvZnRjICop Ow0KDQojZGVmaW5lIFVTQ0FOTkVSVU5JVChuKSAobWlub3IobikgJiAweGYp DQoNClVTQl9ERUNMQVJFX0RSSVZFUih1c2Nhbm5lcik7DQoNClVTQl9NQVRD SCh1c2Nhbm5lcikNCnsNCglVU0JfTUFUQ0hfU1RBUlQodXNjYW5uZXIsIHVh YSk7DQoJaW50IGkgPSAwOw0KDQoJaWYgKHVhYS0+aWZhY2UgPT0gMCkNCgkJ cmV0dXJuIFVNQVRDSF9OT05FOw0KDQoJd2hpbGUgKHNjYW5uZXJfaWRzW2ld LnZlbmRvciAhPSAwKSB7DQoJCWlmIChzY2FubmVyX2lkc1tpXS52ZW5kb3Ig PT0gdWFhLT52ZW5kb3INCgkJICAgICYmIHNjYW5uZXJfaWRzW2ldLnZlbmRv ciA9PSB1YWEtPnZlbmRvcikgew0KCQkJcmV0dXJuIChVTUFUQ0hfVkVORE9S X1BST0RVQ1QpOw0KCQl9IGVsc2Ugew0KCQkJaSsrOw0KCQl9DQoJfQ0KDQoJ cmV0dXJuIChVTUFUQ0hfTk9ORSk7DQp9DQoNClVTQl9BVFRBQ0godXNjYW5u ZXIpDQp7DQoJVVNCX0FUVEFDSF9TVEFSVCh1c2Nhbm5lciwgc2MsIHVhYSk7 DQoJdXNiX2ludGVyZmFjZV9kZXNjcmlwdG9yX3QgKmlkID0gMDsNCgl1c2Jf ZW5kcG9pbnRfZGVzY3JpcHRvcl90ICplZCwgKmVkX2J1bGtpbiA9IE5VTEws ICplZF9idWxrb3V0ID0gTlVMTDsNCgljaGFyIGRldmluZm9bMTAyNF07DQoJ aW50IGk7DQoJdXNiZF9zdGF0dXMgZXJyOw0KDQoJdXNiZF9kZXZpbmZvKHVh YS0+ZGV2aWNlLCAwLCBkZXZpbmZvKTsNCglVU0JfQVRUQUNIX1NFVFVQOw0K CXByaW50ZigiJXM6ICVzXG4iLCBVU0JERVZOQU1FKHNjLT5zY19kZXYpLCBk ZXZpbmZvKTsNCg0KCXNjLT5zY191ZGV2ID0gdWFhLT5kZXZpY2U7DQoNCgkv KiBYWFggV2Ugb25seSBjaGVjayB0aGUgZmlyc3QgaW50ZXJmYWNlICovDQoJ ZXJyID0gdXNiZF9kZXZpY2UyaW50ZXJmYWNlX2hhbmRsZShzYy0+c2NfdWRl diwgMCwgJnNjLT5zY19pZmFjZSk7DQoJaWYgKCFlcnIgJiYgc2MtPnNjX2lm YWNlKQ0KCSAgICBpZCA9IHVzYmRfZ2V0X2ludGVyZmFjZV9kZXNjcmlwdG9y KHNjLT5zY19pZmFjZSk7DQoJaWYgKGVyciB8fCBpZCA9PSAwKSB7DQoJCXBy aW50ZigiJXM6IGNvdWxkIG5vdCBnZXQgaW50ZXJmYWNlIGRlc2NyaXB0b3Is IGVycj0lZCxpZD0lcFxuIiwNCgkJICAgICAgIFVTQkRFVk5BTUUoc2MtPnNj X2RldiksIGVyciwgaWQpOw0KCQlVU0JfQVRUQUNIX0VSUk9SX1JFVFVSTjsN Cgl9DQoNCgkvKiBGaW5kIHRoZSB0d28gZmlyc3QgYnVsayBlbmRwb2ludHMg Ki8NCglmb3IgKGkgPSAwIDsgaSA8IGlkLT5iTnVtRW5kcG9pbnRzOyBpKysp IHsNCgkJZWQgPSB1c2JkX2ludGVyZmFjZTJlbmRwb2ludF9kZXNjcmlwdG9y KHNjLT5zY19pZmFjZSwgaSk7DQoJCWlmIChlZCA9PSAwKSB7DQoJCQlwcmlu dGYoIiVzOiBjb3VsZCBub3QgcmVhZCBlbmRwb2ludCBkZXNjcmlwdG9yXG4i LA0KCQkJICAgICAgIFVTQkRFVk5BTUUoc2MtPnNjX2RldikpOw0KCQkJVVNC X0FUVEFDSF9FUlJPUl9SRVRVUk47DQoJCX0NCg0KCQlpZiAoVUVfR0VUX0RJ UihlZC0+YkVuZHBvaW50QWRkcmVzcykgPT0gVUVfRElSX0lODQoJCSAgICAm JiAoZWQtPmJtQXR0cmlidXRlcyAmIFVFX1hGRVJUWVBFKSA9PSBVRV9CVUxL KSB7DQoJCQllZF9idWxraW4gPSBlZDsNCgkJfSBlbHNlIGlmIChVRV9HRVRf RElSKGVkLT5iRW5kcG9pbnRBZGRyZXNzKSA9PSBVRV9ESVJfT1VUDQoJCSAg ICAmJiAoZWQtPmJtQXR0cmlidXRlcyAmIFVFX1hGRVJUWVBFKSA9PSBVRV9C VUxLKSB7DQoJCSAgICAgICAgZWRfYnVsa291dCA9IGVkOw0KCQl9DQoNCgkJ aWYgKGVkX2J1bGtpbiAmJiBlZF9idWxrb3V0KQkvKiBmb3VuZCBhbGwgd2Ug bmVlZCAqLw0KCQkJYnJlYWs7DQoJfQ0KDQoJLyogVmVyaWZ5IHRoYXQgd2Ug Z29ldGhpbmcgc2Vuc2libGUgKi8NCglpZiAoZWRfYnVsa2luID09IE5VTEwg fHwgZWRfYnVsa291dCA9PSBOVUxMKSB7DQoJCXByaW50ZigiJXM6IGJ1bGst aW4gYW5kL29yIGJ1bGstb3V0IGVuZHBvaW50IG5vdCBmb3VuZFxuIiwNCgkJ CVVTQkRFVk5BTUUoc2MtPnNjX2RldikpOw0KCQlVU0JfQVRUQUNIX0VSUk9S X1JFVFVSTjsNCgl9DQoNCglzYy0+c2NfYnVsa2luID0gZWRfYnVsa2luLT5i RW5kcG9pbnRBZGRyZXNzOw0KCXNjLT5zY19idWxrb3V0ID0gZWRfYnVsa291 dC0+YkVuZHBvaW50QWRkcmVzczsNCg0KCS8qIHRoZSBtYWluIGRldmljZSwg Y3RybCBlbmRwb2ludCAqLw0KCW1ha2VfZGV2KCZ1c2Nhbm5lcl9jZGV2c3cs IFVTQkRFVlVOSVQoc2MtPnNjX2RldiksDQoJCVVJRF9ST09ULCBHSURfT1BF UkFUT1IsIDA2NDQsICIlcyIsIFVTQkRFVk5BTUUoc2MtPnNjX2RldikpOw0K DQoJVVNCX0FUVEFDSF9TVUNDRVNTX1JFVFVSTjsNCn0NCg0KaW50DQp1c2Nh bm5lcm9wZW4oZGV2LCBmbGFnLCBtb2RlLCBwKQ0KCWRldl90IGRldjsNCglp bnQgZmxhZzsNCglpbnQgbW9kZTsNCglzdHJ1Y3QgcHJvYyAqcDsNCnsNCglz dHJ1Y3QgdXNjYW5uZXJfc29mdGMgKnNjOw0KCWludCB1bml0ID0gVVNDQU5O RVJVTklUKGRldik7DQoJdXNiZF9zdGF0dXMgZXJyOw0KDQoJVVNCX0dFVF9T Q19PUEVOKHVzY2FubmVyLCB1bml0LCBzYyk7DQoNCiAJRFBSSU5URk4oNSwg KCJ1c2Nhbm5lcm9wZW46IGZsYWc9JWQsIG1vZGU9JWQsIHVuaXQ9JWRcbiIs IA0KCQkgICAgIGZsYWcsIG1vZGUsIHVuaXQpKTsNCg0KCWlmIChzYyA9PSBO VUxMIHx8IHNjLT5zY19keWluZykNCgkJcmV0dXJuIChFTlhJTyk7DQoNCglp ZiAoc2MtPnN0YXRlICYgVVNDQU5ORVJfT1BFTikNCgkJcmV0dXJuIChFQlVT WSk7DQoNCglzYy0+c2NfYnVsa2luX2J1ZmZlciA9IG1hbGxvYyhVU0NBTk5F Ul9CVUZGRVJTSVpFLCBNX1VTQkRFViwgTV9XQUlUT0spOw0KCXNjLT5zY19i dWxrb3V0X2J1ZmZlciA9IG1hbGxvYyhVU0NBTk5FUl9CVUZGRVJTSVpFLCBN X1VTQkRFViwgTV9XQUlUT0spOw0KCWlmIChzYy0+c2NfYnVsa2luX2J1ZmZl ciA9PSAwIHx8IHNjLT5zY19idWxrb3V0X2J1ZmZlciA9PSAwKSB7DQoJCXVz Y2FubmVyX2RvX2Nsb3NlKHNjKTsNCgkJcmV0dXJuIEVOT01FTTsNCgl9DQoJ c2MtPnNjX2J1bGtpbl9idWZmZXJsZW4gPSBVU0NBTk5FUl9CVUZGRVJTSVpF Ow0KCXNjLT5zY19idWxrb3V0X2J1ZmZlcmxlbiA9IFVTQ0FOTkVSX0JVRkZF UlNJWkU7DQoNCgkvKiBXZSBoYXZlIGRlY2lkZWQgb24gd2hpY2ggZW5kcG9p bnRzIHRvIHVzZSwgbm93IG9wZW4gdGhlIHBpcGVzICovDQoJZXJyID0gdXNi ZF9vcGVuX3BpcGUoc2MtPnNjX2lmYWNlLCBzYy0+c2NfYnVsa2luLA0KCQkJ CVVTQkRfRVhDTFVTSVZFX1VTRSwgJnNjLT5zY19idWxraW5fcGlwZSk7DQoJ aWYgKGVycikgew0KCQlwcmludGYoIiVzOiBjYW5ub3Qgb3BlbiBidWxrLWlu IHBpcGUgKGFkZHIgJWQpXG4iLA0KCQkJVVNCREVWTkFNRShzYy0+c2NfZGV2 KSwgc2MtPnNjX2J1bGtpbik7DQoJCXVzY2FubmVyX2RvX2Nsb3NlKHNjKTsN CgkJcmV0dXJuIEVJTzsNCgl9DQoJZXJyID0gdXNiZF9vcGVuX3BpcGUoc2Mt PnNjX2lmYWNlLCBzYy0+c2NfYnVsa291dCwNCgkJCQlVU0JEX0VYQ0xVU0lW RV9VU0UsICZzYy0+c2NfYnVsa291dF9waXBlKTsNCglpZiAoZXJyKSB7DQoJ CXByaW50ZigiJXM6IGNhbm5vdCBvcGVuIGJ1bGstb3V0IHBpcGUgKGFkZHIg JWQpXG4iLA0KCQkJVVNCREVWTkFNRShzYy0+c2NfZGV2KSwgc2MtPnNjX2J1 bGtvdXQpOw0KCQl1c2Nhbm5lcl9kb19jbG9zZShzYyk7DQoJCXJldHVybiBF SU87DQoJfQ0KDQoJc2MtPnNjX2J1bGtpbl94ZmVyID0gdXNiZF9hbGxvY194 ZmVyKHNjLT5zY191ZGV2KTsNCglpZiAoc2MtPnNjX2J1bGtpbl94ZmVyID09 IDApIHsNCgkJdXNjYW5uZXJfZG9fY2xvc2Uoc2MpOw0KCQlyZXR1cm4gKEVO T01FTSk7DQoJfQ0KCXNjLT5zY19idWxrb3V0X3hmZXIgPSB1c2JkX2FsbG9j X3hmZXIoc2MtPnNjX3VkZXYpOw0KCWlmIChzYy0+c2NfYnVsa291dF94ZmVy ID09IDApIHsNCgkJdXNjYW5uZXJfZG9fY2xvc2Uoc2MpOw0KCQlyZXR1cm4g KEVOT01FTSk7DQoJfQ0KDQoJcmV0dXJuIDA7CS8qIHN1Y2Nlc3MgKi8NCn0N Cg0KaW50DQp1c2Nhbm5lcmNsb3NlKGRldiwgZmxhZywgbW9kZSwgcCkNCglk ZXZfdCBkZXY7DQoJaW50IGZsYWc7DQoJaW50IG1vZGU7DQoJc3RydWN0IHBy b2MgKnA7DQp7DQoJc3RydWN0IHVzY2FubmVyX3NvZnRjICpzYzsNCg0KCVVT Ql9HRVRfU0ModXNjYW5uZXIsIFVTQ0FOTkVSVU5JVChkZXYpLCBzYyk7DQoN CglEUFJJTlRGTig1LCAoInVzY2FubmVyY2xvc2U6IGZsYWc9JWQsIG1vZGU9 JWQsIHVuaXQ9JWRcbiIsDQoJCSAgICAgZmxhZywgbW9kZSwgVVNDQU5ORVJV TklUKGRldikpKTsNCg0KI2lmZGVmIERJQUdOT1NUSUMNCglpZiAoIShzYy0+ c3RhdGUgJiBVU0NBTk5FUl9PUEVOKSkgew0KCQlwcmludGYoInVzY2FubmVy Y2xvc2U6IG5vdCBvcGVuXG4iKTsNCgkJcmV0dXJuIChFSU5WQUwpOw0KCX0N CiNlbmRpZg0KDQoJdXNjYW5uZXJfZG9fY2xvc2Uoc2MpOw0KDQoJcmV0dXJu IDA7DQp9DQoNCnZvaWQNCnVzY2FubmVyX2RvX2Nsb3NlKHN0cnVjdCB1c2Nh bm5lcl9zb2Z0YyAqc2MpDQp7DQoJaWYgKHNjLT5zY19idWxraW5feGZlcikg ew0KCQl1c2JkX2ZyZWVfeGZlcihzYy0+c2NfYnVsa2luX3hmZXIpOw0KCQlz Yy0+c2NfYnVsa2luX3hmZXIgPSBOVUxMOw0KCX0NCglpZiAoc2MtPnNjX2J1 bGtvdXRfeGZlcikgew0KCQl1c2JkX2ZyZWVfeGZlcihzYy0+c2NfYnVsa291 dF94ZmVyKTsNCgkJc2MtPnNjX2J1bGtvdXRfeGZlciA9IE5VTEw7DQoJfQ0K DQoJaWYgKHNjLT5zY19idWxraW5fcGlwZSkgew0KCQl1c2JkX2Fib3J0X3Bp cGUoc2MtPnNjX2J1bGtpbl9waXBlKTsNCgkJdXNiZF9jbG9zZV9waXBlKHNj LT5zY19idWxraW5fcGlwZSk7DQoJCXNjLT5zY19idWxraW5fcGlwZSA9IE5V TEw7DQoJfQ0KCWlmIChzYy0+c2NfYnVsa291dF9waXBlKSB7DQoJCXVzYmRf YWJvcnRfcGlwZShzYy0+c2NfYnVsa291dF9waXBlKTsNCgkJdXNiZF9jbG9z ZV9waXBlKHNjLT5zY19idWxrb3V0X3BpcGUpOw0KCQlzYy0+c2NfYnVsa291 dF9waXBlID0gTlVMTDsNCgl9DQoNCglpZiAoc2MtPnNjX2J1bGtpbl9idWZm ZXIpIHsNCgkJZnJlZShzYy0+c2NfYnVsa2luX2J1ZmZlciwgTV9VU0JERVYp Ow0KCQlzYy0+c2NfYnVsa2luX2J1ZmZlciA9IE5VTEw7DQoJfQ0KCWlmIChz Yy0+c2NfYnVsa291dF9idWZmZXIpIHsNCgkJZnJlZShzYy0+c2NfYnVsa291 dF9idWZmZXIsIE1fVVNCREVWKTsNCgkJc2MtPnNjX2J1bGtvdXRfYnVmZmVy ID0gTlVMTDsNCgl9DQoNCglzYy0+c3RhdGUgJj0gflVTQ0FOTkVSX09QRU47 DQp9DQoNClN0YXRpYyBpbnQNCnVzY2FubmVyX2RvX3JlYWQoc2MsIHVpbywg ZmxhZykNCglzdHJ1Y3QgdXNjYW5uZXJfc29mdGMgKnNjOw0KCXN0cnVjdCB1 aW8gKnVpbzsNCglpbnQgZmxhZzsNCnsNCgl1X2ludDMyX3QgbiwgdG47DQoJ dXNiZF9zdGF0dXMgZXJyOw0KCWludCBlcnJvciA9IDA7DQoNCglEUFJJTlRG Tig1LCAoIiVzOiB1c2Nhbm5lcnJlYWRcbiIsIFVTQkRFVk5BTUUoc2MtPnNj X2RldikpKTsNCg0KCWlmIChzYy0+c2NfZHlpbmcpDQoJCXJldHVybiAoRUlP KTsNCg0KCXdoaWxlICgobiA9IG1pbihzYy0+c2NfYnVsa2luX2J1ZmZlcmxl biwgdWlvLT51aW9fcmVzaWQpKSAhPSAwKSB7DQoJCURQUklOVEZOKDEsICgi dXNjYW5uZXJyZWFkOiBzdGFydCB0cmFuc2ZlciAlZCBieXRlc1xuIixuKSk7 DQoJCXRuID0gbjsNCg0KCQllcnIgPSB1c2JkX2J1bGtfdHJhbnNmZXIoDQoJ CQlzYy0+c2NfYnVsa2luX3hmZXIsIHNjLT5zY19idWxraW5fcGlwZSwNCgkJ CXNjLT5zdGF0ZSAmIFVTQkRfU0hPUlRfWEZFUl9PSywgVVNCRF9OT19USU1F T1VULA0KCQkJc2MtPnNjX2J1bGtpbl9idWZmZXIsICZ0biwNCgkJCSJ1c2Nh bm5lcnJiIik7DQoJCWlmIChlcnIpIHsNCgkJCWlmIChlcnIgPT0gVVNCRF9J TlRFUlJVUFRFRCkNCgkJCQllcnJvciA9IEVJTlRSOw0KCQkJZWxzZSBpZiAo ZXJyID09IFVTQkRfVElNRU9VVCkNCgkJCQllcnJvciA9IEVUSU1FRE9VVDsN CgkJCWVsc2UNCgkJCQllcnJvciA9IEVJTzsNCgkJCWJyZWFrOw0KCQl9DQoJ CURQUklOVEZOKDEsICgidXNjYW5uZXJyZWFkOiBnb3QgJWQgYnl0ZXNcbiIs IHRuKSk7DQoJCWVycm9yID0gdWlvbW92ZShzYy0+c2NfYnVsa2luX2J1ZmZl ciwgdG4sIHVpbyk7DQoJCWlmIChlcnJvciB8fCB0biA8IG4pDQoJCQlicmVh azsNCgl9DQoNCglyZXR1cm4gKGVycm9yKTsNCn0NCg0KaW50DQp1c2Nhbm5l cnJlYWQoZGV2LCB1aW8sIGZsYWcpDQoJZGV2X3QgZGV2Ow0KCXN0cnVjdCB1 aW8gKnVpbzsNCglpbnQgZmxhZzsNCnsNCglzdHJ1Y3QgdXNjYW5uZXJfc29m dGMgKnNjOw0KCWludCBlcnJvcjsNCg0KCVVTQl9HRVRfU0ModXNjYW5uZXIs IFVTQ0FOTkVSVU5JVChkZXYpLCBzYyk7DQoNCglzYy0+c2NfcmVmY250Kys7 DQoJZXJyb3IgPSB1c2Nhbm5lcl9kb19yZWFkKHNjLCB1aW8sIGZsYWcpOw0K CWlmICgtLXNjLT5zY19yZWZjbnQgPCAwKQ0KCQl1c2JfZGV0YWNoX3dha2V1 cChVU0JERVYoc2MtPnNjX2RldikpOw0KDQoJcmV0dXJuIChlcnJvcik7DQp9 DQoNClN0YXRpYyBpbnQNCnVzY2FubmVyX2RvX3dyaXRlKHNjLCB1aW8sIGZs YWcpDQoJc3RydWN0IHVzY2FubmVyX3NvZnRjICpzYzsNCglzdHJ1Y3QgdWlv ICp1aW87DQoJaW50IGZsYWc7DQp7DQoJdV9pbnQzMl90IG47DQoJaW50IGVy cm9yID0gMDsNCgl1c2JkX3N0YXR1cyBlcnI7DQoNCglEUFJJTlRGTig1LCAo IiVzOiB1c2Nhbm5lcl9kb193cml0ZVxuIiwgVVNCREVWTkFNRShzYy0+c2Nf ZGV2KSkpOw0KDQoJaWYgKHNjLT5zY19keWluZykNCgkJcmV0dXJuIChFSU8p Ow0KDQoJd2hpbGUgKChuID0gbWluKHNjLT5zY19idWxrb3V0X2J1ZmZlcmxl biwgdWlvLT51aW9fcmVzaWQpKSAhPSAwKSB7DQoJCWVycm9yID0gdWlvbW92 ZShzYy0+c2NfYnVsa291dF9idWZmZXIsIG4sIHVpbyk7DQoJCWlmIChlcnJv cikNCgkJCWJyZWFrOw0KCQlEUFJJTlRGTigxLCAoInVzY2FubmVyX2RvX3dy aXRlOiB0cmFuc2ZlciAlZCBieXRlc1xuIiwgbikpOw0KCQllcnIgPSB1c2Jk X2J1bGtfdHJhbnNmZXIoDQoJCQlzYy0+c2NfYnVsa291dF94ZmVyLCBzYy0+ c2NfYnVsa291dF9waXBlLA0KCQkJMCwgVVNCRF9OT19USU1FT1VULA0KCQkJ c2MtPnNjX2J1bGtvdXRfYnVmZmVyLCAmbiwNCgkJCSJ1c2Nhbm5lcndiIik7 DQoJCWlmIChlcnIpIHsNCgkJCWlmIChlcnIgPT0gVVNCRF9JTlRFUlJVUFRF RCkNCgkJCQllcnJvciA9IEVJTlRSOw0KCQkJZWxzZQ0KCQkJCWVycm9yID0g RUlPOw0KCQkJYnJlYWs7DQoJCX0NCgl9DQoNCglyZXR1cm4gKGVycm9yKTsN Cn0NCg0KaW50DQp1c2Nhbm5lcndyaXRlKGRldiwgdWlvLCBmbGFnKQ0KCWRl dl90IGRldjsNCglzdHJ1Y3QgdWlvICp1aW87DQoJaW50IGZsYWc7DQp7DQoJ c3RydWN0IHVzY2FubmVyX3NvZnRjICpzYzsNCglpbnQgZXJyb3I7DQoNCglV U0JfR0VUX1NDKHVzY2FubmVyLCBVU0NBTk5FUlVOSVQoZGV2KSwgc2MpOw0K DQoJc2MtPnNjX3JlZmNudCsrOw0KCWVycm9yID0gdXNjYW5uZXJfZG9fd3Jp dGUoc2MsIHVpbywgZmxhZyk7DQoJaWYgKC0tc2MtPnNjX3JlZmNudCA8IDAp DQoJCXVzYl9kZXRhY2hfd2FrZXVwKFVTQkRFVihzYy0+c2NfZGV2KSk7DQoJ cmV0dXJuIChlcnJvcik7DQp9DQoNCiNpZiBkZWZpbmVkKF9fTmV0QlNEX18p IHx8IGRlZmluZWQoX19PcGVuQlNEX18pDQppbnQNCnVzY2FubmVyX2FjdGl2 YXRlKHNlbGYsIGFjdCkNCglkZXZpY2VfcHRyX3Qgc2VsZjsNCgllbnVtIGRl dmFjdCBhY3Q7DQp7DQoJc3RydWN0IHVzY2FubmVyX3NvZnRjICpzYyA9IChz dHJ1Y3QgdXNjYW5uZXJfc29mdGMgKilzZWxmOw0KDQoJc3dpdGNoIChhY3Qp IHsNCgljYXNlIERWQUNUX0FDVElWQVRFOg0KCQlyZXR1cm4gKEVPUE5PVFNV UFApOw0KCQlicmVhazsNCg0KCWNhc2UgRFZBQ1RfREVBQ1RJVkFURToNCgkJ c2MtPnNjX2R5aW5nID0gMTsNCgkJYnJlYWs7DQoJfQ0KCXJldHVybiAoMCk7 DQp9DQojZW5kaWYNCg0KVVNCX0RFVEFDSCh1c2Nhbm5lcikNCnsNCglVU0Jf REVUQUNIX1NUQVJUKHVzY2FubmVyLCBzYyk7DQoJaW50IHM7DQojaWYgZGVm aW5lZChfX05ldEJTRF9fKSB8fCBkZWZpbmVkKF9fT3BlbkJTRF9fKQ0KCWlu dCBtYWosIG1uOw0KI2VsaWYgZGVmaW5lZChfX0ZyZWVCU0RfXykNCglkZXZf dCBkZXY7DQoJc3RydWN0IHZub2RlICp2cDsNCiNlbmRpZg0KDQojaWYgZGVm aW5lZChfX05ldEJTRF9fKSB8fCBkZWZpbmVkKF9fT3BlbkJTRF9fKQ0KCURQ UklOVEYoKCJ1c2Nhbm5lcl9kZXRhY2g6IHNjPSVwIGZsYWdzPSVkXG4iLCBz YywgZmxhZ3MpKTsNCiNlbGlmIGRlZmluZWQoX19GcmVlQlNEX18pDQoJRFBS SU5URigoInVzY2FubmVyX2RldGFjaDogc2M9JXBcbiIsIHNjKSk7DQojZW5k aWYNCg0KCXNjLT5zY19keWluZyA9IDE7DQoNCgkvKiBBYm9ydCBhbGwgcGlw ZXMuICBDYXVzZXMgcHJvY2Vzc2VzIHdhaXRpbmcgZm9yIHRyYW5zZmVyIHRv IHdha2UuICovDQoJaWYgKHNjLT5zY19idWxraW5fcGlwZSkNCgkJdXNiZF9h Ym9ydF9waXBlKHNjLT5zY19idWxraW5fcGlwZSk7DQoJaWYgKHNjLT5zY19i dWxrb3V0X3BpcGUpDQoJCXVzYmRfYWJvcnRfcGlwZShzYy0+c2NfYnVsa291 dF9waXBlKTsNCg0KCXMgPSBzcGx1c2IoKTsNCglpZiAoLS1zYy0+c2NfcmVm Y250ID49IDApIHsNCgkJLyogV2FpdCBmb3IgcHJvY2Vzc2VzIHRvIGdvIGF3 YXkuICovDQoJCXVzYl9kZXRhY2hfd2FpdChVU0JERVYoc2MtPnNjX2Rldikp Ow0KCX0NCglzcGx4KHMpOw0KDQojaWYgZGVmaW5lZChfX05ldEJTRF9fKSB8 fCBkZWZpbmVkKF9fT3BlbkJTRF9fKQ0KCS8qIGxvY2F0ZSB0aGUgbWFqb3Ig bnVtYmVyICovDQoJZm9yIChtYWogPSAwOyBtYWogPCBuY2hyZGV2OyBtYWor KykNCgkJaWYgKGNkZXZzd1ttYWpdLmRfb3BlbiA9PSB1c2Nhbm5lcm9wZW4p DQoJCQlicmVhazsNCg0KCS8qIE51a2UgdGhlIHZub2RlcyBmb3IgYW55IG9w ZW4gaW5zdGFuY2VzIChjYWxscyBjbG9zZSkuICovDQoJbW4gPSBzZWxmLT5k dl91bml0ICogVVNCX01BWF9FTkRQT0lOVFM7DQoJdmRldmdvbmUobWFqLCBt biwgbW4gKyBVU0JfTUFYX0VORFBPSU5UUyAtIDEsIFZDSFIpOw0KI2VsaWYg ZGVmaW5lZChfX0ZyZWVCU0RfXykNCgkvKiBkZXN0cm95IHRoZSBkZXZpY2Ug Zm9yIHRoZSBjb250cm9sIGVuZHBvaW50ICovDQoJZGV2ID0gbWFrZWRldihV U0NBTk5FUl9DREVWX01BSk9SLCBVU0JERVZVTklUKHNjLT5zY19kZXYpKTsN Cgl2cCA9IFNMSVNUX0ZJUlNUKCZkZXYtPnNpX2hsaXN0KTsNCglpZiAodnAp DQoJCVZPUF9SRVZPS0UodnAsIFJFVk9LRUFMTCk7DQoJZGVzdHJveV9kZXYo ZGV2KTsNCiNlbmRpZg0KDQoJcmV0dXJuICgwKTsNCn0NCg0KaW50DQp1c2Nh bm5lcnBvbGwoZGV2LCBldmVudHMsIHApDQoJZGV2X3QgZGV2Ow0KCWludCBl dmVudHM7DQoJc3RydWN0IHByb2MgKnA7DQp7DQoJc3RydWN0IHVzY2FubmVy X3NvZnRjICpzYzsNCglpbnQgcmV2ZW50cyA9IDA7DQoNCglVU0JfR0VUX1ND KHVzY2FubmVyLCBVU0NBTk5FUlVOSVQoZGV2KSwgc2MpOw0KDQoJaWYgKHNj LT5zY19keWluZykNCgkJcmV0dXJuIChFSU8pOw0KDQoJLyogDQoJICogV2Ug aGF2ZSBubyBlYXN5IHdheSBvZiBkZXRlcm1pbmluZyBpZiBhIHJlYWQgd2ls bA0KCSAqIHlpZWxkIGFueSBkYXRhIG9yIGEgd3JpdGUgd2lsbCBoYXBwZW4u DQoJICogUHJldGVuZCB0aGV5IHdpbGwuDQoJICovDQoJcmV2ZW50cyB8PSBl dmVudHMgJiANCgkJICAgKFBPTExJTiB8IFBPTExSRE5PUk0gfCBQT0xMT1VU IHwgUE9MTFdSTk9STSk7DQoNCglyZXR1cm4gKHJldmVudHMpOw0KfQ0KDQoj aWYgZGVmaW5lZChfX0ZyZWVCU0RfXykNCkRSSVZFUl9NT0RVTEUodXNjYW5u ZXIsIHVodWIsIHVzY2FubmVyX2RyaXZlciwgdXNjYW5uZXJfZGV2Y2xhc3Ms IHVzYmRfZHJpdmVyX2xvYWQsIDApOw0KI2VuZGlmDQo= --0-1557275625-968264149=:54419 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="uscanner.h" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="uscanner.h" LyogdGFibGUgb2Ygc2Nhbm5lcnMgdGhhdCBtYXkgd29yayB3aXRoIHRoaXMg ZHJpdmVyICovDQpzdGF0aWMgY29uc3Qgc3RydWN0IHNjYW5uZXJfaWQgew0K ICAgIHVpbnQxNl90CXZlbmRvcjsNCiAgICB1aW50MTZfdAlwcm9kdWN0Ow0K fSBzY2FubmVyX2lkcyBbXSA9IHsNCiAgICB7IFVTQl9WRU5ET1JfQUNFUlAs IFVTQl9QUk9EVUNUX0FDRVJQX0FDRVJTQ0FOXzY0MFUgfSwNCiAgICB7IFVT Ql9WRU5ET1JfQUNFUlAsIFVTQl9QUk9EVUNUX0FDRVJQX0FDRVJTQ0FOXzYy MFUgfSwNCg0KICAgIHsgVVNCX1ZFTkRPUl9BR0ZBLCBVU0JfUFJPRFVDVF9B R0ZBX1NOQVBTQ0FOMTIxMlUgfSwNCiAgICB7IFVTQl9WRU5ET1JfQUdGQSwg VVNCX1BST0RVQ1RfQUdGQV9TTkFQU0NBTjEyMTJVMiB9LA0KICAgIHsgVVNC X1ZFTkRPUl9BR0ZBLCBVU0JfUFJPRFVDVF9BR0ZBX1NOQVBTQ0FOVE9VQ0gg fSwNCg0KICAgIHsgVVNCX1ZFTkRPUl9LWUUsIFVTQl9QUk9EVUNUX0tZRV9W SVZJRFBSTyB9LA0KDQogICAgeyBVU0JfVkVORE9SX0hQLCBVU0JfUFJPRFVD VF9IUF8zMzAwQyB9LA0KICAgIHsgVVNCX1ZFTkRPUl9IUCwgVVNCX1BST0RV Q1RfSFBfNDEwMEMgfSwNCiAgICB7IFVTQl9WRU5ET1JfSFAsIFVTQl9QUk9E VUNUX0hQXzQyMDBDIH0sDQogICAgeyBVU0JfVkVORE9SX0hQLCBVU0JfUFJP RFVDVF9IUF9TMjAgfSwNCiAgICB7IFVTQl9WRU5ET1JfSFAsIFVTQl9QUk9E VUNUX0hQXzUyMDAgfSwNCiAgICB7IFVTQl9WRU5ET1JfSFAsIFVTQl9QUk9E VUNUX0hQXzYyMDBDIH0sDQogICAgeyBVU0JfVkVORE9SX0hQLCBVU0JfUFJP RFVDVF9IUF82MzAwQyB9LA0KDQogICAgeyBVU0JfVkVORE9SX0FWSVNJT04s IFVTQl9QUk9EVUNUX0FWSVNJT05fMTIwMFUgfSwNCg0KICAgIHsgVVNCX1ZF TkRPUl9NSUNST1RFSywgVVNCX1BST0RVQ1RfTUlDUk9URUtfWDZVIH0sDQog ICAgeyBVU0JfVkVORE9SX01JQ1JPVEVLLCBVU0JfUFJPRFVDVF9NSUNST1RF S18zMzZDWCB9LA0KICAgIHsgVVNCX1ZFTkRPUl9NSUNST1RFSywgVVNCX1BS T0RVQ1RfTUlDUk9URUtfMzM2Q1gyIH0sDQogICAgeyBVU0JfVkVORE9SX01J Q1JPVEVLLCBVU0JfUFJPRFVDVF9NSUNST1RFS19DNiB9LA0KICAgIHsgVVNC X1ZFTkRPUl9NSUNST1RFSywgVVNCX1BST0RVQ1RfTUlDUk9URUtfVjZVU0wg fSwNCiAgICB7IFVTQl9WRU5ET1JfTUlDUk9URUssIFVTQl9QUk9EVUNUX01J Q1JPVEVLX1Y2VVNMMiB9LA0KICAgIHsgVVNCX1ZFTkRPUl9NSUNST1RFSywg VVNCX1BST0RVQ1RfTUlDUk9URUtfVjZVTCB9LA0KDQogICAgeyBVU0JfVkVO RE9SX01VU1RFSywgVVNCX1BST0RVQ1RfTVVTVEVLXzEyMDBDVSB9LA0KDQog ICAgeyBVU0JfVkVORE9SX1BSSU1BWCwgVVNCX1BST0RVQ1RfUFJJTUFYX0cy RTMwMCB9LA0KICAgIHsgVVNCX1ZFTkRPUl9QUklNQVgsIFVTQl9QUk9EVUNU X1BSSU1BWF82MzZJIH0sDQogICAgeyBVU0JfVkVORE9SX1BSSU1BWCwgVVNC X1BST0RVQ1RfUFJJTUFYX0cyMzAwIH0sDQogICAgeyBVU0JfVkVORE9SX1BS SU1BWCwgVVNCX1BST0RVQ1RfUFJJTUFYX0cyNjAwIH0sDQogICAgeyBVU0Jf VkVORE9SX1BSSU1BWCwgVVNCX1BST0RVQ1RfUFJJTUFYX0cyRTMwMDIgfSwN CiAgICB7IFVTQl9WRU5ET1JfUFJJTUFYLCBVU0JfUFJPRFVDVF9QUklNQVhf RzJFNjAwIH0sDQogICAgeyBVU0JfVkVORE9SX1BSSU1BWCwgVVNCX1BST0RV Q1RfUFJJTUFYXzk2MDAgfSwNCiAgICB7IFVTQl9WRU5ET1JfUFJJTUFYLCBV U0JfUFJPRFVDVF9QUklNQVhfMTkyMDAgfSwNCiAgICB7IFVTQl9WRU5ET1Jf UFJJTUFYLCBVU0JfUFJPRFVDVF9QUklNQVhfNjAwVSB9LA0KICAgIHsgVVNC X1ZFTkRPUl9QUklNQVgsIFVTQl9QUk9EVUNUX1BSSU1BWF8xMjAwVSB9LA0K DQogICAgeyBVU0JfVkVORE9SX0VQU09OLCBVU0JfUFJPRFVDVF9FUFNPTl82 MzYgfSwNCiAgICB7IFVTQl9WRU5ET1JfRVBTT04sIFVTQl9QUk9EVUNUX0VQ U09OXzYxMCB9LA0KICAgIHsgVVNCX1ZFTkRPUl9FUFNPTiwgVVNCX1BST0RV Q1RfRVBTT05fMTIwMCB9LA0KDQogICAgeyBVU0JfVkVORE9SX1VNQVgsIFVT Ql9QUk9EVUNUX1VNQVhfQVNUUkExMjIwVSB9LA0KICAgIHsgVVNCX1ZFTkRP Ul9VTUFYLCBVU0JfUFJPRFVDVF9VTUFYX0FTVFJBMTIzNlUgfSwNCiAgICB7 IFVTQl9WRU5ET1JfVU1BWCwgVVNCX1BST0RVQ1RfVU1BWF9BU1RSQTIwMDBV IH0sDQogICAgeyBVU0JfVkVORE9SX1VNQVgsIFVTQl9QUk9EVUNUX1VNQVhf QVNUUkEyMjAwVSB9LA0KDQogICAgeyBVU0JfVkVORE9SX1ZJU0lPTkVFUiwg VVNCX1BST0RVQ1RfVklTSU9ORUVSXzUzMDAgfSwNCiAgICB7IFVTQl9WRU5E T1JfVklTSU9ORUVSLCBVU0JfUFJPRFVDVF9WSVNJT05FRVJfNjEwMCB9LA0K DQogICAgeyAwLCAwIH0NCn07DQoNCg0K --0-1557275625-968264149=:54419 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=Makefile Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=Makefile IyAgICAgICAkRnJlZUJTRDogc3JjL3N5cy9tb2R1bGVzL3Vtcy9NYWtlZmls ZSx2IDEuOSAyMDAwLzA1LzI3IDAxOjE0OjI4IHBldGVyIEV4cCAkIA0KDQpN QUlOVEFJTkVSCSA9IG5faGlibWFAZnJlZWJzZC5vcmcNCg0KLlBBVEg6ICAJ ICR7LkNVUkRJUn0vLi4vLi4vZGV2L3VzYg0KS01PRAkJID0gdXNjYW5uZXIN ClNSQ1MJCSA9IGJ1c19pZi5oIGRldmljZV9pZi5oIHZub2RlX2lmLmggb3B0 X3VzYi5oIHVzY2FubmVyLmMNCk5PTUFOCQkgPQ0KDQpDRkxBR1MJCSs9IC1n DQoNCi5pbmNsdWRlIDxic2Qua21vZC5taz4NCg== --0-1557275625-968264149=:54419 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="uscanner.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="uscanner.patch" SW5kZXg6IGJvb3QvZm9ydGgvbG9hZGVyLmNvbmYNCj09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT0NClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3NyYy9zeXMvYm9vdC9m b3J0aC9sb2FkZXIuY29uZix2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMzAN CmRpZmYgLXcgLXUgLXIxLjMwIGxvYWRlci5jb25mDQotLS0gYm9vdC9mb3J0 aC9sb2FkZXIuY29uZgkyMDAwLzA3LzI4IDExOjU0OjA4CTEuMzANCisrKyBi b290L2ZvcnRoL2xvYWRlci5jb25mCTIwMDAvMDkvMDUgMTM6NDg6MjMNCkBA IC0xNjksNiArMTY5LDcgQEANCiB1bHB0X2xvYWQ9Ik5PIgkJCSMgUHJpbnRl cg0KIHVtc19sb2FkPSJOTyIJCQkjIE1vdXNlDQogdW1hc3NfbG9hZD0iTk8i CQkJIyBNYXNzIFN0b3JhZ2UgRGV2aWNlcw0KK3VzY2FubmVyX2xvYWQ9Ik5P IgkJIyBTY2FubmVycw0KIGlmX2F1ZV9sb2FkPSJOTyIJCSMgQURNdGVrIFVT QiBldGhlcm5ldA0KIGlmX2N1ZV9sb2FkPSJOTyIJCSMgQ0FUQyBVU0IgZXRo ZXJuZXQNCiBpZl9rdWVfbG9hZD0iTk8iCQkjIEthd2FzYWtpIExTSSBVU0Ig ZXRoZXJuZXQNCkluZGV4OiBjb25mL21ham9ycw0KPT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PQ0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3N5cy9jb25mL21h am9ycyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMTEyDQpkaWZmIC13IC11 IC1yMS4xMTIgbWFqb3JzDQotLS0gY29uZi9tYWpvcnMJMjAwMC8wOS8wMSAy MToxNDoxNQkxLjExMg0KKysrIGNvbmYvbWFqb3JzCTIwMDAvMDkvMDUgMTM6 MzY6MDINCkBAIC0xNzEsNiArMTcxLDcgQEANCiAxNTIJYWNwaQkJQUNQSSBi aW9zIHN1cHBvcnQgKFRha2Fub3JpIFdhdGFuYWJlIHRha2F3YXRhQHNoaWRh aGFyYTEucGxhbmV0LnNjaS5rb2JlLXUuYWMuanApDQogMTUzCXRpCQlUaWdv biBHaWdhYml0IEV0aGVybmV0IGRyaXZlciAoa2VuQEZyZWVCU0QuT1JHKQ0K IDE1NAlhc3IJCUFkYXB0ZWMgU0NTSSBSQUlEIDxtc21pdGhAZnJlZWJzZC5v cmc+DQorMTU1CXVzY2FubmVyCVVTQiBTY2FubmVycyA8bl9oaWJtYT4NCiAy MDAJPz8JCWVudHJpZXMgZnJvbSAyMDAtMjUyIGFyZSByZXNlcnZlZCBmb3Ig bG9jYWwgdXNlDQogMjUyCT8/CQllbnRyaWVzIGZyb20gMjAwLTI1MiBhcmUg cmVzZXJ2ZWQgZm9yIGxvY2FsIHVzZQ0KIDI1MwltZnMJCVVzZWQgYnkgTUZT DQpJbmRleDogbW9kdWxlcy9NYWtlZmlsZQ0KPT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PQ0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL3N5cy9tb2R1bGVzL01h a2VmaWxlLHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS4xMzcNCmRpZmYgLXcg LXUgLXIxLjEzNyBNYWtlZmlsZQ0KLS0tIG1vZHVsZXMvTWFrZWZpbGUJMjAw MC8wOS8wMSAwNzo1MToyNAkxLjEzNw0KKysrIG1vZHVsZXMvTWFrZWZpbGUJ MjAwMC8wOS8wNSAxMzo0NjowMw0KQEAgLTEzLDYgKzEzLDcgQEANCiAJbndm cyBwb3J0YWwgcHJvY2ZzICR7X3JhbmRvbWRldn0gXA0KIAlybCBycCBzZiBz aXMgc2sgc24gc291bmQgc3RlIHN5c2NvbnMgdGkgdGwgdHdlIHR4IFwNCiAJ dWRicCB1Z2VuIHVoaWQgdWtiZCB1bHB0IHVtYXBmcyB1bWFzcyB1bW9kZW0g dW1zIHVuaW9uIHVyaW8gdXNiIFwNCisJdXNjYW5uZXIgXA0KIAl2aW51bSB2 biB2cG8gdnIgd2Igd3ggeGwNCiANCiAjIFhYWCBzb21lIG9mIHRoZXNlIGNh biBtb3ZlIHRvIHRoZSBnZW5lcmFsIGNhc2Ugd2hlbiBkZS1pMzg2J2VkDQo= --0-1557275625-968264149=:54419-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 12:12: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 9CC9E37B43E for ; Wed, 6 Sep 2000 12:11:56 -0700 (PDT) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 793192CE76 for ; Wed, 6 Sep 2000 21:11:44 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.0/8.11.0) id e86JBnV00266 for freebsd-current@freebsd.org; Wed, 6 Sep 2000 21:11:49 +0200 (EET) (envelope-from vallo) Date: Wed, 6 Sep 2000 21:11:49 +0200 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: Reliable panic: Filesystem goof Message-ID: <20000906211149.A224@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I've found reliable way to crash my box, install latest vim6h alpha and set it to your default editor for mutt, I'm using 1.2.5i. Then write something and try to save it :wq vop_panic[vop_getacl] panic: Filesystem goof mp_lock = 00000001 ; cpuid = 0 ; lapic.id = 00000000 Debugger("panic") At this point I can type and symbols appear on the console, but system is completely dead, do not respond to ping etc. Here's what my machine looks like, sources are from Sep 5 17:19 UTC. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Sep 5 21:36:04 EET 2000 root@myhakas.matti.ee:/usr/src/sys/compile/Myhakas Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x383fbff real memory = 268435456 (262144K bytes) avail memory = 257568768 (251532K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0387000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc038709c. Pentium Pro MTRR support enabled VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6954 (c0006954) VESA: Matrox Graphics Inc. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 16 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 Timecounter "PIIX" frequency 3579545 Hz pci0: at 7.3 ahc0: port 0xe400-0xe4ff mem 0xfebfe000-0xfebfefff irq 16 at device 11.0 on pci0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 16 at device 11.1 on pci0 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 32/255 SCBs pcm0: port 0xef00-0xef3f irq 18 at device 12.0 on pci0 fxp0: port 0xee80-0xeebf mem 0xfea00000-0xfeafffff,0xfebfd000-0xfebfdfff irq 19 at device 13.0 on pci0 fxp0: Ethernet address 00:e0:81:10:50:32 fxp1: port 0xed80-0xedbf mem 0xfe800000-0xfe8fffff,0xfebfc000-0xfebfcfff irq 17 at device 15.0 on pci0 fxp1: Ethernet address 00:90:27:54:57:26 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <9 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 BRIDGE 990810, have 3 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.e0.81.10.50.32 -- index 2 type 6 phy 0 addrl 6 addr 00.90.27.54.57.26 SMP: AP CPU #1 Launched! ad0: 14649MB [29765/16/63] at ata0-master using UDMA33 ad1: 35772MB [72680/16/63] at ata1-master using UDMA33 Waiting 5 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit) da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit) da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) Mounting root from ufs:/dev/da0s1a cd0 at ahc1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15) da2: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) WARNING: / was not properly dismounted # Myhakas machine i386 ident Myhakas maxusers 64 makeoptions CONF_CFLAGS=-fno-builtin #Don't allow use of memcmp, etc. makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options PQ_CACHESIZE=512 # color for 512k/16k cache options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O cpu I686_CPU # aka Pentium Pro(tm) options NO_F00F_HACK options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options DDB # options DDB_UNATTENDED options INVARIANTS options INVARIANT_SUPPORT options UCONSOLE options INET #Internet communications protocols device ether #Generic Ethernet device loop 1 #Network loopback device device bpf #Berkeley packet filter device tun #Tunnel driver (ppp(8), nos-tun(8)) options BRIDGE options FFS #Fast filesystem options NFS #Network File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES # options FFS_EXTATTR options RANDOMDEV options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options HZ=1000 device scbus #base SCSI code device da #SCSI direct access devices (aka disks) device cd #SCSI CD-ROMs device pt #SCSI processor device targ #SCSI Target Mode Code device targbh #SCSI Target Mode Blackhole Device device pass #CAM passthrough driver options SCSI_DELAY=5000 # Be pessimistic about Joe SCSI device device pty #Pseudo ttys device vn #Vnode driver (turns a file into a device) device snp #Snoop device - to look at pty/vty/etc.. options MSGBUF_SIZE=40960 device isa options COMPAT_OLDISA #Use ISA shims and glue for old drivers device pci options COMPAT_OLDPCI #Use PCI shims and glue for old drivers device atkbdc 1 device atkbd device psm device vga options VESA device splash device sc 1 options MAXCONS=9 # number of virtual consoles options SC_DISABLE_REBOOT # disable reboot key sequence options SC_HISTORY_SIZE=800 # number of history buffer lines device npx device ahc options AHC_ALLOW_MEMIO device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_ENABLE_ATAPI_DMA device fdc device sio device miibus device ed device fxp # Intel EtherExpress PRO/100B (82557, 82558) device pcm options DONTPROBE_1284 # Avoid boot detection of PnP parallel devices device ppc device ppbus device lpt device plip device ppi options COMPAT_LINUX options SHMMAX=(64*1024*1024) options SHMMNI=4096 options SHMSEG=256 -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 12:18:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gplsucks.org (mail.gplsucks.org [63.227.213.93]) by hub.freebsd.org (Postfix) with ESMTP id B974037B422 for ; Wed, 6 Sep 2000 12:18:21 -0700 (PDT) Received: from localhost (bwoods2@localhost) by mail.gplsucks.org (8.11.0/8.11.0) with ESMTP id e86JIQa05870 for ; Wed, 6 Sep 2000 12:18:26 -0700 (PDT) Date: Wed, 6 Sep 2000 12:18:26 -0700 (PDT) From: William Woods To: freebsd-current@freebsd.org Subject: PERL 5.6 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 Can anyoine give me an idea when Perl 5.6 will be merged from current into stable? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 13: 7:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id C0C0237B422; Wed, 6 Sep 2000 13:07:19 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 13WlTa-000DBm-0B; Wed, 6 Sep 2000 20:07:18 +0000 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 VAA04054; Wed, 6 Sep 2000 21:08:22 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 6 Sep 2000 21:08:17 +0100 (BST) From: Doug Rabson To: Stephen Hocking Cc: multimedia@freebsd.org, current@freebsd.org, dfr@freebsd.org Subject: Re: Strange problems with AGP driver & sound. In-Reply-To: <200009061753.e86Hr3G00359@bloop.craftncomp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, Stephen Hocking wrote: > > With very recent current sources, the agp driver doesn't probe when loaded as > a module, but works OK when compiled into the kernel. Oh. I thought that was only a problem in 4.x. Can I see a verbose bootlog for a kernel where this is a problem. > > However, when compiled into the kernel, it seems to mess up the sound driver > (pcm, crystal cs23x) such that no sound or garbled sound at a low volume comes > out. Has anyone else seen this? I'm using the mga driver from the XFree86 cvs > tree to do 3D work, which is why I'm using the AGP driver. No idea about this one. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 13:13:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 28DF737B423; Wed, 6 Sep 2000 13:13:26 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 13WlZK-0005Nb-0K; Wed, 6 Sep 2000 20:13:14 +0000 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 VAA04101; Wed, 6 Sep 2000 21:13:53 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 6 Sep 2000 21:13:49 +0100 (BST) From: Doug Rabson To: "David O'Brien" Cc: Jason Evans , current@freebsd.org, smp@freebsd.org Subject: Re: HEADS UP: SMP code commit iminent In-Reply-To: <20000905183738.A87381@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 Tue, 5 Sep 2000, David O'Brien wrote: > On Tue, Sep 05, 2000 at 05:58:32PM -0700, Jason Evans wrote: > > this email is a minimum 24 hour notice that SMP code will be committed > > to -current. > > What is the status of the Alpha bits? Will we have a working kernel > after the commit, or should we site tight for a week while the Alpha bits > are tweaked into working status? The code should boot - if not, I will follow up with a few cleanup commits. The next job for the alpha is to overhaul the interrupt code to support irq threads. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 13:14:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id E6DEB37B423 for ; Wed, 6 Sep 2000 13:14:32 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id D224E1925A for ; Wed, 6 Sep 2000 15:14:31 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id PAA29205 for current@freebsd.org; Wed, 6 Sep 2000 15:14:31 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Wed, 6 Sep 2000 15:14:31 -0500 From: "Jacques A. Vidrine" To: current@freebsd.org Subject: HEADS UP: nsswitch meets current Message-ID: <20000906151431.A26152@hamlet.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HEADS UP: nsswitch meets current Hello, I have just commited nsswitch support to FreeBSD-current. The code is based on NetBSD 1.4.2's nsswitch and I attempted to keep the implementations as close as possible. By creating an /etc/nsswitch.conf file, you can configure FreeBSD so that various databases such as passwd and group can be looked up using flat files, NIS, or Hesiod. To summarize, = Hesiod has been added to libc (see hesiod(3)). = A library routine for parsing nsswitch.conf and invoking callback functions as specified has been added to libc (see nsdispatch(3)). = The following C library functions have been modified to use nsdispatch: . getgrent, getgrnam, getgrgid . getpwent, getpwnam, getpwuid . getusershell . getaddrinfo . gethostbyname, gethostbyname2, gethostbyaddr . getnetbyname, getnetbyaddr . getipnodebyname, getipnodebyaddr, getnodebyname, getnodebyaddr As a side effect, by Hajimu UMEMOTO 's suggestion (thanks!), the default for the resolver is now files, then dns. This is different than the traditional default of dns, then files. HOWEVER, note that since November 1998 we have installed a default host.conf that causes lookup to be files, then dns anyway. = host.conf has been removed from src/etc. rc.network has been modified to warn that host.conf is no longer used at boot time. In addition, if there is a host.conf but no nsswitch.conf, the latter is created at boot time from the former. See also hesiod.conf(5) and nsswitch.conf(5). Thanks to Luke Mewburn for writing this freely distributable name-service switch implementation for the NetBSD Project. Thanks to those who sent in reports/suggestions/patches! Note that patches adding this support to 4.1-RELEASE and 4.1-STABLE are available at http://www.nectar.com/freebsd/nsswitch, as well as the patches that have been committed to -CURRENT. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 13:17:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id EF13237B423 for ; Wed, 6 Sep 2000 13:17:11 -0700 (PDT) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id BC9E82CE76; Wed, 6 Sep 2000 22:17:05 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.0/8.11.0) id e86KHA711891; Wed, 6 Sep 2000 22:17:10 +0200 (EET) (envelope-from vallo) Date: Wed, 6 Sep 2000 22:17:10 +0200 From: Vallo Kallaste To: Vallo Kallaste Cc: freebsd-current@FreeBSD.ORG Subject: Re: Reliable panic: Filesystem goof Message-ID: <20000906221710.A11871@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000906211149.A224@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000906211149.A224@myhakas.matti.ee>; from vallo@matti.ee on Wed, Sep 06, 2000 at 09:11:49PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 06, 2000 at 09:11:49PM +0200, Vallo Kallaste wrote: > I've found reliable way to crash my box, install latest vim6h alpha and > set it to your default editor for mutt, I'm using 1.2.5i. Then write > something and try to save it :wq > > vop_panic[vop_getacl] > panic: Filesystem goof > mp_lock = 00000001 ; cpuid = 0 ; lapic.id = 00000000 > Debugger("panic") Nevermind, I've found the answer in my mailbox two minutes after posting. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 13:40:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from sm3.texas.rr.com (sm3.texas.rr.com [24.93.35.210]) by hub.freebsd.org (Postfix) with ESMTP id 2154A37B43F; Wed, 6 Sep 2000 13:40:26 -0700 (PDT) Received: from bleep.craftncomp.com (cs2777-164.houston.rr.com [24.27.77.164]) by sm3.texas.rr.com (8.9.3/8.8.7) with ESMTP id PAA19287; Wed, 6 Sep 2000 15:40:17 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86KeEV01647; Wed, 6 Sep 2000 15:40:14 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86KeCG19351; Wed, 6 Sep 2000 15:40:12 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009062040.e86KeCG19351@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Rabson Cc: multimedia@freebsd.org, current@freebsd.org Subject: Re: Strange problems with AGP driver & sound. In-Reply-To: Your message of "Wed, 06 Sep 2000 21:08:17 BST." Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Sep 2000 15:40:12 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > With very recent current sources, the agp driver doesn't probe when loaded as > > a module, but works OK when compiled into the kernel. > > Oh. I thought that was only a problem in 4.x. Can I see a verbose bootlog > for a kernel where this is a problem. > OK - I'm away from the machine at the moment (it's back at home) - I'll boot the old kernel verbosely and send the results back. Mind you, when I start to fire up the X server and have it load up DRI & glx modules, it crashes the machine. The mga module (when I preload it) complains that it needs the agp module in the bootup messages. > > > > However, when compiled into the kernel, it seems to mess up the sound driver > > (pcm, crystal cs23x) such that no sound or garbled sound at a low volume comes > > out. Has anyone else seen this? I'm using the mga driver from the XFree86 cvs > > tree to do 3D work, which is why I'm using the AGP driver. > > No idea about this one. > Yeah - I think there's some warts lurking in the sound code somewhere. It's odd, becuase the interrupts from the sound device are still coming in at the expected rate - just not any sound, like it's bufferring from some random chunk of clear memory. Stephen Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 13:43:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id B560237B424; Wed, 6 Sep 2000 13:43:33 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id NAA73340; Wed, 6 Sep 2000 13:43:21 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009062043.NAA73340@pike.osd.bsdi.com> Subject: Re: HEADS UP: SMP code commit iminent In-Reply-To: from Doug Rabson at "Sep 6, 2000 09:13:49 pm" To: Doug Rabson Date: Wed, 6 Sep 2000 13:43:20 -0700 (PDT) Cc: "David O'Brien" , Jason Evans , current@FreeBSD.ORG, smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 Doug Rabson wrote: > On Tue, 5 Sep 2000, David O'Brien wrote: > > > On Tue, Sep 05, 2000 at 05:58:32PM -0700, Jason Evans wrote: > > > this email is a minimum 24 hour notice that SMP code will be committed > > > to -current. > > > > What is the status of the Alpha bits? Will we have a working kernel > > after the commit, or should we site tight for a week while the Alpha bits > > are tweaked into working status? > > The code should boot - if not, I will follow up with a few cleanup > commits. The next job for the alpha is to overhaul the interrupt code to > support irq threads. The current patchset finished a 3-hour buildworld w/o problems. Sometime after the world had finished while I was asleep it had a kernel trap with a memory management fault however. :( 3 hours of reliable uptime in multi- user should be enough stability for development however. > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 20 8348 3944 -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 15:14:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7E82737B423 for ; Wed, 6 Sep 2000 15:14:43 -0700 (PDT) Received: (from jkh@localhost) by winston.osd.bsdi.com (8.11.0/8.9.3) id e86MELs29321 for current@freebsd.org; Wed, 6 Sep 2000 15:14:21 -0700 (PDT) (envelope-from jkh) Date: Wed, 6 Sep 2000 15:14:21 -0700 (PDT) From: Jordan Hubbard Message-Id: <200009062214.e86MELs29321@winston.osd.bsdi.com> To: current@freebsd.org Subject: nsswitch changes break world build Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG .. during the depend phase.. /usr/src/lib/libc/../libc/gen/getgrent.c:48: nsswitch.h: No such file or directo ry /usr/src/lib/libc/../libc/gen/getpwent.c:54: nsswitch.h: No such file or directo - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 15:21:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 32AE337B423 for ; Wed, 6 Sep 2000 15:21:16 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA25602; Wed, 6 Sep 2000 15:21:13 -0700 Date: Wed, 6 Sep 2000 15:21:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: nsswitch changes break world build In-Reply-To: <200009062214.e86MELs29321@winston.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you sure you don't have a partial update? On Wed, 6 Sep 2000, Jordan Hubbard wrote: > .. during the depend phase.. > > /usr/src/lib/libc/../libc/gen/getgrent.c:48: nsswitch.h: No such file or directo > ry > /usr/src/lib/libc/../libc/gen/getpwent.c:54: nsswitch.h: No such file or directo > > - Jordan > > > 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 Sep 6 15:28:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 6DB6337B422 for ; Wed, 6 Sep 2000 15:28:57 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA29460; Wed, 6 Sep 2000 15:28:34 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: nsswitch changes break world build In-Reply-To: Message from Matthew Jacob of "Wed, 06 Sep 2000 15:21:00 PDT." Date: Wed, 06 Sep 2000 15:28:34 -0700 Message-ID: <29456.968279314@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep, I checked before complaining. Nathan Ahlstrom just sent me a patch to include/Makefile which I'm just testing now. - Jordan > > Are you sure you don't have a partial update? > > > On Wed, 6 Sep 2000, Jordan Hubbard wrote: > > > .. during the depend phase.. > > > > /usr/src/lib/libc/../libc/gen/getgrent.c:48: nsswitch.h: No such file or di recto > > ry > > /usr/src/lib/libc/../libc/gen/getpwent.c:54: nsswitch.h: No such file or di recto > > > > - Jordan > > > > > > 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 Sep 6 15:30:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.infospace.com (mail2.infospace.com [206.29.197.32]) by hub.freebsd.org (Postfix) with ESMTP id 9D39D37B422 for ; Wed, 6 Sep 2000 15:30:16 -0700 (PDT) Received: from exchangeimc.infospace.com (exchange.infospace.com [206.29.197.30]) by mail2.infospace.com (8.9.3/8.9.3) with ESMTP id PAA12373 for ; Wed, 6 Sep 2000 15:30:24 -0700 (PDT) Received: by exchange.infospace.com with Internet Mail Service (5.5.2650.21) id ; Wed, 6 Sep 2000 15:30:04 -0700 Message-ID: <9117CCE51A38D411A85F00508BCFCFC41255AD@exchangemail.inspinc.ad> From: "Paul Petersen (InfoSpace Inc)" To: "'current@freebsd.org'" Subject: RE: nsswitch changes break world build Date: Wed, 6 Sep 2000 15:30:28 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just did a new cvsup on a newly installed 4.1-RELEASE box with src-all so go the complete new tree and go the same error. Paul Petersen Infospace, Inc. 425-201-8966 -----Original Message----- From: Matthew Jacob [mailto:mjacob@feral.com] Sent: Wednesday, September 06, 2000 3:21 PM To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: nsswitch changes break world build Are you sure you don't have a partial update? On Wed, 6 Sep 2000, Jordan Hubbard wrote: > .. during the depend phase.. > > /usr/src/lib/libc/../libc/gen/getgrent.c:48: nsswitch.h: No such file or directo > ry > /usr/src/lib/libc/../libc/gen/getpwent.c:54: nsswitch.h: No such file or directo > > - Jordan > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 15:54:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id B62B637B628; Wed, 6 Sep 2000 15:54:24 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 6 Sep 2000 17:56:08 -0500 Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86MsKV01743; Wed, 6 Sep 2000 17:54:20 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e86MsIG00366; Wed, 6 Sep 2000 17:54:18 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009062254.e86MsIG00366@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug Rabson Cc: Stephen Hocking , multimedia@FreeBSD.ORG, current@FreeBSD.ORG, dfr@FreeBSD.ORG Subject: Re: Strange problems with AGP driver & sound. In-Reply-To: Message from Doug Rabson of "Wed, 06 Sep 2000 21:08:17 BST." Reply-To: shocking@houston.rr.com Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_19822812510" Date: Wed, 06 Sep 2000 17:54:18 -0500 From: Stephen Hocking Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_19822812510 Content-Type: text/plain; charset=us-ascii Ok, here's the two dmesg listing from verbose boots, one with the agp code as a module, and the other built in. Stephen --==_Exmh_19822812510 Content-Type: text/plain ; name="agp.as.module"; charset=us-ascii Content-Description: agp.as.module Content-Disposition: attachment; filename="agp.as.module" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Sep 6 17:42:22 CDT 2000 toor@bloop.craftncomp.com:/usr/src/sys/compile/bloop Calibrating clock(s) ... TSC clock: 501156139 Hz, i8254 clock: 1193229 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 501138511 Hz CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 128M bytes Write Allocate 15-16M bytes: Disable real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x003a3000 - 0x07fe5fff, 130297856 bytes (31811 pages) avail memory = 127025152 (124048K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fb020 bios32: Entry = 0xfb4a0 (c00fb4a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xb4d0 pnpbios: Found PnP BIOS data at 0xc00fc0a0 pnpbios: Entry = f0000:c0c8 Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel "kernel.ko" at 0xc038a000. Preloaded elf module "mga.ko" at 0xc038a0ac. Preloaded elf module "agp.ko" at 0xc038a148. Preloaded elf module "drm.ko" at 0xc038a1e4. nulldev: random: mem: K6-family MTRR support enabled (2 registers) VESA: information block 56 45 53 41 00 02 ca 6c 00 c0 01 00 00 00 74 69 00 c0 00 02 05 01 df 6c 00 c0 e6 6c 00 c0 f2 6c 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 11 mode(s) found VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6974 (c0006974) VESA: Matrox Graphics Inc. VESA: Matrox Matrox G400 00 npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 84090144 bytes/sec bzero() bandwidth = 119488588 bytes/sec pcib0: on motherboard pci0: physical bus=0 found-> vendor=0x1106, dev=0x0598, revid=0x04 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base e0000000, size 26, enabled found-> vendor=0x1106, dev=0x8598, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1106, dev=0x0586, revid=0x47 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x0571, revid=0x06 bus=0, slot=7, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 00006400, size 4, enabled found-> vendor=0x1106, dev=0x3040, revid=0x10 bus=0, slot=7, func=3 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x11ad, dev=0x0002, revid=0x20 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 4, range 32, base 00006c00, size 8, enabled map[14]: type 1, range 32, base eb000000, size 8, enabled pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: physical bus=1 found-> vendor=0x102b, dev=0x0525, revid=0x04 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 3, range 32, base e8000000, size 25, enabled map[14]: type 1, range 32, base e4000000, size 14, enabled map[18]: type 1, range 32, base e5000000, size 23, enabled pci1: on pcib1 drm0: mem 0xe5000000-0xe57fffff,0xe4000000-0xe4003fff,0xe8000000-0xe9ffffff irq 11 at device 0.0 on pci1 info: [drm] The mga drm module requires the agp module to function correctly Please load the agp module before you load the mga module device_probe_and_attach: drm0 attach returned 12 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x6400-0x640f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x6400 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x6408 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x1 ata1: at 0x170 irq 15 on atapci0 dc0: <82c169 PNIC 10/100BaseTX> port 0x6c00-0x6cff mem 0xeb000000-0xeb0000ff irq 10 at device 9.0 on pci0 dc0: Ethernet address: 00:a0:cc:56:31:9a miibus0: on dc0 ukphy0: on miibus0 ukphy0: OUI 0x001018, model 0x0021, rev. 2 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: dc0 attached Trying Read_Port at 203 CSC0000: start dependant CSC0000: adding dma mask 0x2 CSC0000: adding dma mask 0x9 CSC0000: adding irq mask 0x20 CSC0000: adding io range 0x534-0x537, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x22f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xa CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0x9aa0 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x26f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0x9aa0 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x3fb, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x30f, size=0x10, align=0x20 CSC0000: end dependant CSC0001: start dependant CSC0001: adding io range 0x200-0x207, size=0x8, align=0x8 CSC0001: start dependant CSC0001: adding io range 0x208-0x20f, size=0x8, align=0x8 CSC0001: end dependant CSC0010: adding io range 0x120-0xfff, size=0x8, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x200 CSC0003: adding io range 0x330-0x331, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x9a00 CSC0003: adding io range 0x330-0x361, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding io range 0x330-0x3e1, size=0x2, align=0x8 CSC0003: end dependant pnpbios: 16 devices, largest 69 bytes PNP0000: adding irq mask 0x4 PNP0000: adding io range 0x20-0x21, size=0x2, align=0 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0 PNP0000: end config pnpbios: handle 0 device ID PNP0000 (0000d041) PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x81-0x83, size=0x3, align=0 PNP0200: adding io range 0x87-0x87, size=0x1, align=0 PNP0200: adding io range 0x89-0x8b, size=0x3, align=0 PNP0200: adding io range 0x8f-0x91, size=0x3, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 PNP0200: end config pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: end config pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: end config pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 PNP0303: end config pnpbios: handle 4 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 PNP0800: end config pnpbios: handle 5 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 PNP0c04: end config pnpbios: handle 6 device ID PNP0c04 (040cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: end config pnpbios: handle 7 device ID PNP0c01 (010cd041) PNP0c02: adding fixed memory32 range 0xf0000-0xf3fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf4000-0xf7fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf8000-0xfbfff, size=0x4000 PNP0c02: adding fixed memory32 range 0xfc000-0xfffff, size=0x4000 PNP0c02: end config pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: adding io range 0x480-0x48f, size=0x10, align=0 PNP0a03: adding io range 0x5000-0x507f, size=0x80, align=0 PNP0a03: adding io range 0x5080-0x50ff, size=0x80, align=0 PNP0a03: end config pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 10 device ID PNP0f13 (130fd041) PNP0c02: adding io range 0x208-0x20f, size=0x8, align=0 PNP0c02: end config pnpbios: handle 11 device ID PNP0c02 (020cd041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: end config pnpbios: handle 12 device ID PNP0501 (0105d041) PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 PNP0700: adding irq mask 0x40 PNP0700: end config pnpbios: handle 13 device ID PNP0700 (0007d041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 PNP0400: end config pnpbios: handle 14 device ID PNP0400 (0004d041) PNP0501: adding irq mask 0x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 PNP0501: end config pnpbios: handle 16 device ID PNP0501 (0105d041) sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 90 03 3c psm: status 90 03 3c psm: status 90 03 3c psm: data 08 00 00 psm: status 00 00 28 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x61 0x71 0x61 0x61 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1: irq maps: 0x61 0x69 0x61 0x61 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A opl0 failed to probe at port 0x388 on isa0 mpu0 failed to probe at port 0x330 irq 9 on isa0 css0 failed to probe at port 0x534 irq 5 drq 1 flags 0x8 on isa0 joy0 failed to probe at port 0x201 on isa0 sc1: no video adapter is found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 pcm: setmap 30000, ff00; 0xc7505000 -> 30000 pcm: setmap 40000, ff00; 0xc7515000 -> 40000 unknown: failed to probe at port 0x200-0x207 on isa0 unknown: failed to probe at port 0x120-0x127 on isa0 unknown: failed to probe at port 0x330-0x331 irq 9 on isa0 unknown: can't assign resources unknown: at port 0x60 on isa0 atspeaker0: at port 0x61 on isa0 unknown: can't assign resources unknown: at irq 12 on isa0 unknown: can't assign resources unknown: at port 0x3f8-0x3ff on isa0 unknown: can't assign resources unknown: at port 0x3f2-0x3f5 on isa0 unknown: failed to probe at port 0x378-0x37f irq 7 on isa0 unknown: can't assign resources unknown: at port 0x2f8-0x2ff on isa0 BIOS Geometries: 0:03ff0f3f 0..1023=1024 cylinders, 0..15=16 heads, 1..63=63 sectors 1:020bfe3f 0..523=524 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: ds0 attached bpf: lo0 attached ata0-master: success setting UDMA2 on VIA chip ad0: ATA-4 disk at ata0 as master ad0: 6179MB (12656448 sectors), 12556 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 stray irq 7 ata1-master: success setting UDMA2 on VIA chip ad1: ATA-4 disk at ata1 as master ad1: 4112MB (8421840 sectors), 8912 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad1: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad1 Mounting root from ufs:/dev/ad0a ad0s4: type 0xa5, start 1, end = 12656447, size 12656447 : OK start_init: trying /sbin/init ad1: invalid primary partition table: no magic Linux-ELF exec handler installed --==_Exmh_19822812510 Content-Type: text/plain ; name="agp.builtin"; charset=us-ascii Content-Description: agp.builtin Content-Disposition: attachment; filename="agp.builtin" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Sep 6 12:14:57 CDT 2000 toor@bloop.craftncomp.com:/usr/src/sys/compile/bloop Calibrating clock(s) ... TSC clock: 501152654 Hz, i8254 clock: 1193221 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 501138398 Hz CPU: AMD-K6(tm) 3D processor (501.14-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 128M bytes Write Allocate 15-16M bytes: Disable real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0037c000 - 0x07fe5fff, 130457600 bytes (31850 pages) avail memory = 127184896 (124204K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fb020 bios32: Entry = 0xfb4a0 (c00fb4a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xb4d0 pnpbios: Found PnP BIOS data at 0xc00fc0a0 pnpbios: Entry = f0000:c0c8 Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel "kernel.ko" at 0xc0363000. nulldev: random: mem: K6-family MTRR support enabled (2 registers) VESA: information block 56 45 53 41 00 02 ca 6c 00 c0 01 00 00 00 74 69 00 c0 00 02 05 01 df 6c 00 c0 e6 6c 00 c0 f2 6c 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 11 mode(s) found VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6974 (c0006974) VESA: Matrox Graphics Inc. VESA: Matrox Matrox G400 00 npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 84061869 bytes/sec bzero() bandwidth = 119061793 bytes/sec pcib0: on motherboard pci0: physical bus=0 found-> vendor=0x1106, dev=0x0598, revid=0x04 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base e0000000, size 26, enabled found-> vendor=0x1106, dev=0x8598, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1106, dev=0x0586, revid=0x47 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x0571, revid=0x06 bus=0, slot=7, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 4, range 32, base 00006400, size 4, enabled found-> vendor=0x1106, dev=0x3040, revid=0x10 bus=0, slot=7, func=3 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x11ad, dev=0x0002, revid=0x20 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 4, range 32, base 00006c00, size 8, enabled map[14]: type 1, range 32, base eb000000, size 8, enabled pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 agp0: allocating GATT for aperture of size 256M pcib1: at device 1.0 on pci0 pci1: physical bus=1 found-> vendor=0x102b, dev=0x0525, revid=0x04 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 3, range 32, base e8000000, size 25, enabled map[14]: type 1, range 32, base e4000000, size 14, enabled map[18]: type 1, range 32, base e5000000, size 23, enabled pci1: on pcib1 pci1: (vendor=0x102b, dev=0x0525) at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x6400-0x640f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x6400 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x6408 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x1 ata1: at 0x170 irq 15 on atapci0 dc0: <82c169 PNIC 10/100BaseTX> port 0x6c00-0x6cff mem 0xeb000000-0xeb0000ff irq 10 at device 9.0 on pci0 dc0: Ethernet address: 00:a0:cc:56:31:9a miibus0: on dc0 ukphy0: on miibus0 ukphy0: OUI 0x001018, model 0x0021, rev. 2 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: dc0 attached Trying Read_Port at 203 CSC0000: start dependant CSC0000: adding dma mask 0x2 CSC0000: adding dma mask 0x9 CSC0000: adding irq mask 0x20 CSC0000: adding io range 0x534-0x537, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x22f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xa CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0x9aa0 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x26f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0x9aa0 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x3fb, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x30f, size=0x10, align=0x20 CSC0000: end dependant CSC0001: start dependant CSC0001: adding io range 0x200-0x207, size=0x8, align=0x8 CSC0001: start dependant CSC0001: adding io range 0x208-0x20f, size=0x8, align=0x8 CSC0001: end dependant CSC0010: adding io range 0x120-0xfff, size=0x8, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x200 CSC0003: adding io range 0x330-0x331, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x9a00 CSC0003: adding io range 0x330-0x361, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding io range 0x330-0x3e1, size=0x2, align=0x8 CSC0003: end dependant pnpbios: 16 devices, largest 69 bytes PNP0000: adding irq mask 0x4 PNP0000: adding io range 0x20-0x21, size=0x2, align=0 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0 PNP0000: end config pnpbios: handle 0 device ID PNP0000 (0000d041) PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x81-0x83, size=0x3, align=0 PNP0200: adding io range 0x87-0x87, size=0x1, align=0 PNP0200: adding io range 0x89-0x8b, size=0x3, align=0 PNP0200: adding io range 0x8f-0x91, size=0x3, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 PNP0200: end config pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: end config pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: end config pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 PNP0303: end config pnpbios: handle 4 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 PNP0800: end config pnpbios: handle 5 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 PNP0c04: end config pnpbios: handle 6 device ID PNP0c04 (040cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: end config pnpbios: handle 7 device ID PNP0c01 (010cd041) PNP0c02: adding fixed memory32 range 0xf0000-0xf3fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf4000-0xf7fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf8000-0xfbfff, size=0x4000 PNP0c02: adding fixed memory32 range 0xfc000-0xfffff, size=0x4000 PNP0c02: end config pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: adding io range 0x480-0x48f, size=0x10, align=0 PNP0a03: adding io range 0x5000-0x507f, size=0x80, align=0 PNP0a03: adding io range 0x5080-0x50ff, size=0x80, align=0 PNP0a03: end config pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 10 device ID PNP0f13 (130fd041) PNP0c02: adding io range 0x208-0x20f, size=0x8, align=0 PNP0c02: end config pnpbios: handle 11 device ID PNP0c02 (020cd041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: end config pnpbios: handle 12 device ID PNP0501 (0105d041) PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 PNP0700: adding irq mask 0x40 PNP0700: end config pnpbios: handle 13 device ID PNP0700 (0007d041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 PNP0400: end config pnpbios: handle 14 device ID PNP0400 (0004d041) PNP0501: adding irq mask 0x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 PNP0501: end config pnpbios: handle 16 device ID PNP0501 (0105d041) sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 90 03 3c psm: status 90 03 3c psm: status 90 03 3c psm: data 08 00 00 psm: status 00 00 28 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x61 0x71 0x61 0x61 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1: irq maps: 0x61 0x69 0x61 0x61 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A opl0 failed to probe at port 0x388 on isa0 mpu0 failed to probe at port 0x330 irq 9 on isa0 css0 failed to probe at port 0x534 irq 5 drq 1 flags 0x8 on isa0 joy0 failed to probe at port 0x201 on isa0 sc1: no video adapter is found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 pcm: setmap 59c000, ff00; 0xcb556000 -> 59c000 pcm: setmap 5ac000, ff00; 0xcb566000 -> 5ac000 unknown: failed to probe at port 0x200-0x207 on isa0 unknown: failed to probe at port 0x120-0x127 on isa0 unknown: failed to probe at port 0x330-0x331 irq 9 on isa0 unknown: can't assign resources unknown: at port 0x60 on isa0 atspeaker0: at port 0x61 on isa0 unknown: can't assign resources unknown: at irq 12 on isa0 unknown: can't assign resources unknown: at port 0x3f8-0x3ff on isa0 unknown: can't assign resources unknown: at port 0x3f2-0x3f5 on isa0 unknown: failed to probe at port 0x378-0x37f irq 7 on isa0 unknown: can't assign resources unknown: at port 0x2f8-0x2ff on isa0 BIOS Geometries: 0:03ff0f3f 0..1023=1024 cylinders, 0..15=16 heads, 1..63=63 sectors 1:020bfe3f 0..523=524 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: ds0 attached bpf: lo0 attached ata0-master: success setting UDMA2 on VIA chip ad0: ATA-4 disk at ata0 as master ad0: 6179MB (12656448 sectors), 12556 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 ata1-master: success setting UDMA2 on VIA chip ad1: ATA-4 disk at ata1 as master ad1: 4112MB (8421840 sectors), 8912 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad1: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad1 Mounting root from ufs:/dev/ad0a ad0s4: type 0xa5, start 1, end = 12656447, size 12656447 : OK start_init: trying /sbin/init ad1: invalid primary partition table: no magic Linux-ELF exec handler installed --==_Exmh_19822812510 Content-Type: text/plain; charset=us-ascii The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California --==_Exmh_19822812510-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 16:50:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 54B7E37B422; Wed, 6 Sep 2000 16:50:31 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e86No6H40455; Wed, 6 Sep 2000 20:50:07 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 6 Sep 2000 20:50:06 -0300 (ADT) From: The Hermit Hacker To: freebsd-smp@freebsd.org Cc: freebsd-current@freebsd.org Subject: Installed SMP patch and now mouse doesn't work? 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 nothing else to go on yet ... I updated both the current source code and installed the SMP patch from Sept 5th. Everything installed great, rebooted and I can work in character mode ... go to X, and the mouse gives me no activity, where it did just before the upgrade ... Am still investigating at this end, but if anyone else has experience similar and knows how to fix? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 16:55:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 69C2A37B422; Wed, 6 Sep 2000 16:55:52 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id QAA81102; Wed, 6 Sep 2000 16:55:37 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009062355.QAA81102@pike.osd.bsdi.com> Subject: Re: Installed SMP patch and now mouse doesn't work? In-Reply-To: from The Hermit Hacker at "Sep 6, 2000 08:50:06 pm" To: The Hermit Hacker Date: Wed, 6 Sep 2000 16:55:37 -0700 (PDT) Cc: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 The Hermit Hacker wrote: > > Have nothing else to go on yet ... I updated both the current source code > and installed the SMP patch from Sept 5th. Everything installed great, > rebooted and I can work in character mode ... go to X, and the mouse gives > me no activity, where it did just before the upgrade ... > > Am still investigating at this end, but if anyone else has experience > similar and knows how to fix? Uh, all of the SMPng boxes so far haven't had mice. :P Is your mouse a serial mouse? There seem to be some problems with input on the sio devices. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 17: 6:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 7042E37B424; Wed, 6 Sep 2000 17:06:50 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e8706Qw41783; Wed, 6 Sep 2000 21:06:26 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 6 Sep 2000 21:06:26 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Cc: freebsd-smp@freebsd.org Subject: 'interrupt-level buffer overflows' for sio device? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this corresponds to the device I have the mouse on ... the machine has only been up 18hrs ... not sure where else to look ... I'm referencing /dev/ttyd1, like I've always done for my mouse, and just checked /dev (ran MAKEDEV ttyd1) to make sure nothing has changed there ... Help? sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: 32 more interrupt-level buffer overflows (total 32) sio1: 123 more interrupt-level buffer overflows (total 155) sio1: 135 more interrupt-level buffer overflows (total 290) sio1: 134 more interrupt-level buffer overflows (total 424) sio1: 30 more interrupt-level buffer overflows (total 454) sio1: 12 more interrupt-level buffer overflows (total 466) sio1: 40 more interrupt-level buffer overflows (total 506) sio1: 133 more interrupt-level buffer overflows (total 639) sio1: 135 more interrupt-level buffer overflows (total 774) sio1: 134 more interrupt-level buffer overflows (total 908) sio1: 135 more interrupt-level buffer overflows (total 1043) sio1: 68 more interrupt-level buffer overflows (total 1111) sio1: 118 more interrupt-level buffer overflows (total 1229) sio1: 14 more interrupt-level buffer overflows (total 1243) sio1: 20 more interrupt-level buffer overflows (total 1263) sio1: 119 more interrupt-level buffer overflows (total 1382) sio1: 134 more interrupt-level buffer overflows (total 1516) sio1: 135 more interrupt-level buffer overflows (total 1651) sio1: 57 more interrupt-level buffer overflows (total 1708) sio1: 3 more interrupt-level buffer overflows (total 1711) sio1: 31 more interrupt-level buffer overflows (total 1742) Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 17:15:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 81FEF37B422; Wed, 6 Sep 2000 17:15:05 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e870Ecd41859; Wed, 6 Sep 2000 21:14:38 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 6 Sep 2000 21:14:38 -0300 (ADT) From: The Hermit Hacker To: John Baldwin Cc: freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Installed SMP patch and now mouse doesn't work? In-Reply-To: <200009062355.QAA81102@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, John Baldwin wrote: > The Hermit Hacker wrote: > > > > Have nothing else to go on yet ... I updated both the current source code > > and installed the SMP patch from Sept 5th. Everything installed great, > > rebooted and I can work in character mode ... go to X, and the mouse gives > > me no activity, where it did just before the upgrade ... > > > > Am still investigating at this end, but if anyone else has experience > > similar and knows how to fix? > > Uh, all of the SMPng boxes so far haven't had mice. :P Is your mouse a > serial mouse? There seem to be some problems with input on the sio > devices. That would be her ... :) Its my home machine, which is why I run -current on it ... am willing to try anything/everything towards debugging and repairing it ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 17:51: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from titan.cc.wwu.edu (titan.cc.wwu.edu [140.160.240.18]) by hub.freebsd.org (Postfix) with ESMTP id E068E37B43E for ; Wed, 6 Sep 2000 17:51:04 -0700 (PDT) Received: from localhost by titan.cc.wwu.edu (8.9.1/8.9.1) with ESMTP id RAA09946 for ; Wed, 6 Sep 2000 17:51:04 -0700 (PDT) Date: Wed, 6 Sep 2000 17:51:04 -0700 (PDT) From: Ryan Shannon To: freebsd-current@freebsd.org Subject: HPT370 to stable 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 Any idea how long it will be before the HPT370 support comes to stable? I'm fairly new to freebsd, so it might not be the wisest maneuver for me to CVSup to current :) Thanks, Ryan Shannon shannor@cc.wwu.edu Please reply directly - I'm not on -current. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 17:53: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id 2BD9637B424 for ; Wed, 6 Sep 2000 17:52:59 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id DC63620F01; Wed, 6 Sep 2000 19:57:58 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id D4CE41D101 for ; Wed, 6 Sep 2000 19:57:58 -0500 (CDT) Date: Wed, 6 Sep 2000 19:57:55 -0500 (CDT) From: Visigoth To: current@freebsd.org Subject: cold boot in -STABLE Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-167374078-968288275=:345" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-167374078-968288275=:345 Content-Type: TEXT/PLAIN; charset=US-ASCII -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 -stable (world and kernel) built today seems to be causing the system to cold boot when attempting to mount floppy disk on 2 of my systems (held off on building the others) . This happens for both ufs and msdos filesystems, and happens weather the machines are booted from SMP kernels or not, SOFTUPDATES makes no difference either (just thought I'd check). I have attempted hardware relpacement and that also makes no difference. I figure since it is on 2 machines of the same kind (with fresh bios flashes, tried that too ;) and just started after booting on to new kernel and world built today that it is software, not hardware.. I have attached a dmesg, and will open a formal PR tomorrow if nobody just seems to know off the top of their head what's going on. (ok, put on your telepathy hat) If there is more info that would be helpful, I would be happy to provide it. I would attach a kernel dump, but the machine just goes dead... Last time world and kernel was built on these machines was 32 days ago... Help.. ;) Visigoth Ps. I use tripwire from a ro floppy so my fd's are important on servers. Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBObbaBjnmC/+RTnGeEQKC6gCgwdG21L66l5y/7NpVnJIUdlYWs2wAn0SH ukY7OYH284ushqnUFP8tv+zk =NmF0 -----END PGP SIGNATURE----- --0-167374078-968288275=:345 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.txt" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: dmesg output Content-Disposition: attachment; filename="dmesg.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDQuMS1TVEFCTEUgIzA6IFdlZCBTZXAgIDYgMTI6 Mjg6MDIgQ0RUIDIwMDANCiAgICB2aXNpZ290aEBtYWlsLnRlbGVtZXJlLm5l dDovdXNyL3NyYy9zeXMvY29tcGlsZS9NQUlMDQpUaW1lY291bnRlciAiaTgy NTQiICBmcmVxdWVuY3kgMTE5MzE4MiBIeg0KQ1BVOiBQZW50aXVtIElJSS9Q ZW50aXVtIElJSSBYZW9uL0NlbGVyb24gKDU1MC4wMi1NSHogNjg2LWNsYXNz IENQVSkNCiAgT3JpZ2luID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHg2NzMg IFN0ZXBwaW5nID0gMw0KICBGZWF0dXJlcz0weDM4M2ZiZmY8RlBVLFZNRSxE RSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxBUElDLFNFUCxNVFJSLFBHRSxN Q0EsQ01PVixQQVQsUFNFMzYsTU1YLEZYU1IsWE1NPg0KcmVhbCBtZW1vcnkg ID0gMTA3MzczMzYzMiAoMTA0ODU2OEsgYnl0ZXMpDQpjb25maWc+IHENCmF2 YWlsIG1lbW9yeSA9IDEwNDIzNjY0NjQgKDEwMTc5MzZLIGJ5dGVzKQ0KQ2hh bmdpbmcgQVBJQyBJRCBmb3IgSU8gQVBJQyAjMCBmcm9tIDAgdG8gMiBvbiBj aGlwDQpQcm9ncmFtbWluZyAyNCBwaW5zIGluIElPQVBJQyAjMA0KSU9BUElD ICMwIGludHBpbiAyIC0+IGlycSAwDQpGcmVlQlNEL1NNUDogTXVsdGlwcm9j ZXNzb3IgbW90aGVyYm9hcmQNCiBjcHUwIChCU1ApOiBhcGljIGlkOiAgMSwg dmVyc2lvbjogMHgwMDA0MDAxMSwgYXQgMHhmZWUwMDAwMA0KIGNwdTEgKEFQ KTogIGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAwMDQwMDExLCBhdCAweGZl ZTAwMDAwDQogaW8wIChBUElDKTogYXBpYyBpZDogIDIsIHZlcnNpb246IDB4 MDAxNzAwMTEsIGF0IDB4ZmVjMDAwMDANClByZWxvYWRlZCBlbGYga2VybmVs ICJrZXJuZWwiIGF0IDB4YzAzNzAwMDAuDQpQcmVsb2FkZWQgdXNlcmNvbmZp Z19zY3JpcHQgIi9ib290L2tlcm5lbC5jb25mIiBhdCAweGMwMzcwMDljLg0K UGVudGl1bSBQcm8gTVRSUiBzdXBwb3J0IGVuYWJsZWQNCm1kMDogTWFsbG9j IGRpc2sNCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24gbW90aGVyYm9hcmQN Cm5weDA6IElOVCAxNiBpbnRlcmZhY2UNCnBjaWIwOiA8SW50ZWwgODI0NTRO WCBQWEIjMCwgQnVzI0E+IG9uIG1vdGhlcmJvYXJkDQpwY2kwOiA8UENJIGJ1 cz4gb24gcGNpYjANCmlzYWIwOiA8SW50ZWwgODIzNzFBQiBQQ0kgdG8gSVNB IGJyaWRnZT4gYXQgZGV2aWNlIDIuMCBvbiBwY2kwDQppc2EwOiA8SVNBIGJ1 cz4gb24gaXNhYjANCnBjaTA6IDxJbnRlbCBQSUlYNCBBVEEgY29udHJvbGxl cj4gYXQgMi4xDQpwY2kwOiA8SW50ZWwgODIzNzFBQi9FQiAoUElJWDQpIFVT QiBjb250cm9sbGVyPiBhdCAyLjIgaXJxIDANClRpbWVjb3VudGVyICJQSUlY IiAgZnJlcXVlbmN5IDM1Nzk1NDUgSHoNCmNoaXAwOiA8SW50ZWwgODIzNzFB QiBQb3dlciBtYW5hZ2VtZW50IGNvbnRyb2xsZXI+IHBvcnQgMHg4NTAtMHg4 NWYgYXQgZGV2aWNlIDIuMyBvbiBwY2kwDQpwY2kwOiA8QVRJIE1hY2g2NC1H SSBncmFwaGljcyBhY2NlbGVyYXRvcj4gYXQgNC4wDQpmeHAwOiA8SW50ZWwg UHJvIDEwLzEwMEIvMTAwKyBFdGhlcm5ldD4gcG9ydCAweGQ4YzAtMHhkOGZm IG1lbSAweGZlNDAwMDAwLTB4ZmU0ZmZmZmYsMHhmZTYwMDAwMC0weGZlNjAw ZmZmIGlycSAxNCBhdCBkZXZpY2UgOC4wIG9uIHBjaTANCmZ4cDA6IEV0aGVy bmV0IGFkZHJlc3MgMDA6ZDA6Yjc6MmM6MzI6MzcNCmRwdDA6IDxEUFQgQ2Fj aGluZyBTQ1NJIFJBSUQgQ29udHJvbGxlcj4gcG9ydCAweGQ4YTAtMHhkOGJm IGlycSAxMSBhdCBkZXZpY2UgMTAuMCBvbiBwY2kwDQpkcHQwOiBEUFQgUE0z MzM0VVcgRlcgUmV2LiAwN00wLCAxIGNoYW5uZWwsIDY0IENDQnMNCnBjaWIz OiA8SW50ZWwgODI0NTROWCBQQ0kgRXhwYW5kZXIgQnJpZGdlPiBhdCBkZXZp Y2UgMTguMCBvbiBwY2kwDQpwY2liNDogPEludGVsIDgyNDU0TlggUENJIEV4 cGFuZGVyIEJyaWRnZT4gYXQgZGV2aWNlIDE5LjAgb24gcGNpMA0KcGNpYjU6 IDxJbnRlbCA4MjQ1NE5YIFBDSSBFeHBhbmRlciBCcmlkZ2U+IGF0IGRldmlj ZSAyMC4wIG9uIHBjaTANCnBjaWIxOiA8SW50ZWwgODI0NTROWCBQWEIjMCwg QnVzI0I+IG9uIG1vdGhlcmJvYXJkDQpwY2kxOiA8UENJIGJ1cz4gb24gcGNp YjENCmFoYzA6IDxBZGFwdGVjIGFpYzc4OTAvOTEgVWx0cmEyIFNDU0kgYWRh cHRlcj4gcG9ydCAweGVjMDAtMHhlY2ZmIG1lbSAweGZlODAyMDAwLTB4ZmU4 MDJmZmYgaXJxIDIxIGF0IGRldmljZSA0LjAgb24gcGNpMQ0KYWhjMDogYWlj Nzg5MC85MSBXaWRlIENoYW5uZWwgQSwgU0NTSSBJZD03LCAxNi8yNTUgU0NC cw0KYWhjMTogPEFkYXB0ZWMgYWljNzg5MC85MSBVbHRyYTIgU0NTSSBhZGFw dGVyPiBwb3J0IDB4ZTgwMC0weGU4ZmYgbWVtIDB4ZmU4MDEwMDAtMHhmZTgw MWZmZiBpcnEgMjIgYXQgZGV2aWNlIDYuMCBvbiBwY2kxDQphaGMxOiBhaWM3 ODkwLzkxIFdpZGUgQ2hhbm5lbCBBLCBTQ1NJIElkPTcsIDE2LzI1NSBTQ0Jz DQphaGMyOiA8QWRhcHRlYyBhaWM3ODYwIFNDU0kgYWRhcHRlcj4gcG9ydCAw eGU0MDAtMHhlNGZmIG1lbSAweGZlODAwMDAwLTB4ZmU4MDBmZmYgaXJxIDIw IGF0IGRldmljZSA4LjAgb24gcGNpMQ0KYWhjMjogYWljNzg2MCBTaW5nbGUg Q2hhbm5lbCBBLCBTQ1NJIElkPTcsIDMvMjU1IFNDQnMNCnBjaWIyOiA8SW50 ZWwgODI0NTROWCBQWEIjMSwgQnVzI0E+IG9uIG1vdGhlcmJvYXJkDQpwY2ky OiA8UENJIGJ1cz4gb24gcGNpYjINCmZ4cDE6IDxJbnRlbCBQcm8gMTAvMTAw Qi8xMDArIEV0aGVybmV0PiBwb3J0IDB4ZmNjMC0weGZjZmYgbWVtIDB4ZmU5 MDAwMDAtMHhmZTlmZmZmZiwweGZlYjAwMDAwLTB4ZmViMDBmZmYgaXJxIDE5 IGF0IGRldmljZSAxLjAgb24gcGNpMg0KZnhwMTogRXRoZXJuZXQgYWRkcmVz cyAwMDpkMDpiNzoyYzoyOTpkNQ0KZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xv bmU+IGF0IHBvcnQgMHgzZjAtMHgzZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24g aXNhMA0KZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0K ZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZlPiBvbiBmZGMwIGRyaXZlIDANCmF0 a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+IGF0IHBvcnQg MHg2MCwweDY0IG9uIGlzYTANCmF0a2JkMDogPEFUIEtleWJvYXJkPiBmbGFn cyAweDEgaXJxIDEgb24gYXRrYmRjMA0Ka2JkMCBhdCBhdGtiZDANCnBzbTA6 IDxQUy8yIE1vdXNlPiBpcnEgMTIgb24gYXRrYmRjMA0KcHNtMDogbW9kZWwg R2VuZXJpYyBQUy8yIG1vdXNlLCBkZXZpY2UgSUQgMA0KdmdhMDogPEdlbmVy aWMgSVNBIFZHQT4gYXQgcG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEwMDAw LTB4YmZmZmYgb24gaXNhMA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZs YWdzIDB4MTAwIG9uIGlzYTANCnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNv bGVzLCBmbGFncz0weDMwMD4NCnNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBp cnEgNCBmbGFncyAweDEwIG9uIGlzYTANCnNpbzA6IHR5cGUgMTY1NTBBDQpz aW8xIGF0IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMA0Kc2lvMTog dHlwZSAxNjU1MEENCnBwYzA6IDxQYXJhbGxlbCBwb3J0PiBhdCBwb3J0IDB4 Mzc4LTB4MzdmIGlycSA3IG9uIGlzYTANCnBwYzA6IFNNQy1saWtlIGNoaXBz ZXQgKEVDUC9FUFAvUFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlDQpw cGMwOiBGSUZPIHdpdGggMTYvMTYvOCBieXRlcyB0aHJlc2hvbGQNCmxwdDA6 IDxQcmludGVyPiBvbiBwcGJ1czANCmxwdDA6IEludGVycnVwdC1kcml2ZW4g cG9ydA0KcHBpMDogPFBhcmFsbGVsIEkvTz4gb24gcHBidXMwDQpwbGlwMDog PFBMSVAgbmV0d29yayBpbnRlcmZhY2U+IG9uIHBwYnVzMA0KQVBJQ19JTzog VGVzdGluZyA4MjU0IGludGVycnVwdCBkZWxpdmVyeQ0KQVBJQ19JTzogcm91 dGluZyA4MjU0IHZpYSBJT0FQSUMgIzAgaW50cGluIDINCklQIEZpbHRlcjog djMuNC44IGluaXRpYWxpemVkLiAgRGVmYXVsdCA9IHBhc3MgYWxsLCBMb2dn aW5nID0gZW5hYmxlZA0KV2FpdGluZyAxNSBzZWNvbmRzIGZvciBTQ1NJIGRl dmljZXMgdG8gc2V0dGxlDQpTTVA6IEFQIENQVSAjMSBMYXVuY2hlZCENCnBh c3MxIGF0IGRwdDAgYnVzIDAgdGFyZ2V0IDYgbHVuIDANCnBhc3MxOiA8REVM TCAxeDggVTJXIFNDU0kgQlAgNS4yMz4gRml4ZWQgUHJvY2Vzc29yIFNDU0kt MiBkZXZpY2UgDQpkYTAgYXQgZHB0MCBidXMgMCB0YXJnZXQgMCBsdW4gMA0K ZGEwOiA8RFBUIFJBSUQtNSAwN00wPiBGaXhlZCBEaXJlY3QgQWNjZXNzIFND U0ktMiBkZXZpY2UgDQpkYTA6IDM0NzMyTUIgKDcxMTMxOTA0IDUxMiBieXRl IHNlY3RvcnM6IDI1NUggNjNTL1QgNDQyN0MpDQpNb3VudGluZyByb290IGZy b20gdWZzOi9kZXYvZGEwczFhDQpjZDAgYXQgYWhjMiBidXMgMCB0YXJnZXQg NSBsdW4gMA0KY2QwOiA8TkVDIENELVJPTSBEUklWRTo0NjYgMS4wNj4gUmVt b3ZhYmxlIENELVJPTSBTQ1NJLTIgZGV2aWNlIA0KY2QwOiAyMC4wMDBNQi9z IHRyYW5zZmVycyAoMjAuMDAwTUh6LCBvZmZzZXQgMTUpDQpjZDA6IEF0dGVt cHQgdG8gcXVlcnkgZGV2aWNlIHNpemUgZmFpbGVkOiBOT1QgUkVBRFksIE1l ZGl1bSBub3QgcHJlc2VudA0KV0FSTklORzogLyB3YXMgbm90IHByb3Blcmx5 IGRpc21vdW50ZWQNCmZkMGM6IGhhcmQgZXJyb3IgcmVhZGluZyBmc2JuIDE2 IG9mIDE2LTMxIChObyBzdGF0dXMpDQo= --0-167374078-968288275=:345-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 18:35:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id A4DC237B42C for ; Wed, 6 Sep 2000 18:35:17 -0700 (PDT) Received: (qmail 27704 invoked by uid 1142); 7 Sep 2000 01:35:17 -0000 Date: 6 Sep 2000 18:35:17 -0700 Date: Wed, 6 Sep 2000 18:07:43 -0700 From: Jason Evans To: smp@freebsd.org, current@freebsd.org Subject: SMP mega-commit complete Message-ID: <20000906180743.O437@blitz.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches have now been committed. There are a number of known issues, and we are actively tracking them on the SMP web page at: http://people.freebsd.org/~jasone/smp/ If you run into issues that appear related to the SMP changes, and they aren't listed as known issues, please bring them up on the -smp or -current mailing list. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 19: 7:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id A65A837B422 for ; Wed, 6 Sep 2000 19:07:25 -0700 (PDT) Received: (qmail 1160 invoked from network); 7 Sep 2000 02:07:19 -0000 Received: from lcp196.cvzoom.net (208.230.68.196) by ns.cvzoom.net with SMTP; 7 Sep 2000 02:07:19 -0000 Date: Wed, 6 Sep 2000 22:07:19 -0400 (EDT) From: Donn Miller To: Nick Hibma Cc: USB BSD list , freebsd-current@freebsd.org Subject: Re: uscanner driver 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 Wed, 6 Sep 2000, Nick Hibma wrote: > I've quickly thrown together a driver for USB scanners. Unforunately, I > don't have a scanner available that is supported by SANE, so I can't > test it. How about parallel scanners? I have a UMAX Astra 2000p PPT scanner. I've heard that UMAX didn't want to release the specs, because they've got a proprietary ASIC in there. If anyone's willing to discuss this matter on a different list, I'm willing to do so. -Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 20: 2:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 52A9037B424 for ; Wed, 6 Sep 2000 20:02:14 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 9028A1925A; Wed, 6 Sep 2000 22:02:13 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id WAA00871; Wed, 6 Sep 2000 22:02:13 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Wed, 6 Sep 2000 22:02:13 -0500 From: "Jacques A. Vidrine" To: Matthew Jacob Cc: Jordan Hubbard , current@FreeBSD.ORG Subject: Re: nsswitch changes break world build Message-ID: <20000906220213.B844@hamlet.nectar.com> References: <200009062214.e86MELs29321@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Wed, Sep 06, 2000 at 03:21:00PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 06, 2000 at 03:21:00PM -0700, Matthew Jacob wrote: > Are you sure you don't have a partial update? He's sure. I boo-boo'd :-) I merrily went out to eat after committing my changes, then checking out -CURRENT and watching it `make -j 4 buildworld' to completion. Of course I already had /usr/include/nsswitch.h, so it didn't blow up for me. Sorry! -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 22:15:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 15D6837B424 for ; Wed, 6 Sep 2000 22:15:21 -0700 (PDT) Received: from castle2.jp.FreeBSD.org (castle2.jp.FreeBSD.org [210.226.20.120]) by updraft.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id OAA99750 for ; Thu, 7 Sep 2000 14:15:19 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by castle2.jp.FreeBSD.org (8.11.0+3.3W/8.11.0) with ESMTP/inet id e875FHX40743 for ; Thu, 7 Sep 2000 14:15:17 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <200009062346.QAA88345@freefall.freebsd.org> References: <200009062346.QAA88345@freefall.freebsd.org> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Molpe) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 9 From: Makoto MATSUSHITA To: current@FreeBSD.ORG Subject: USA_RESIDENT variable is no longer needed ? Date: Thu, 07 Sep 2000 14:15:06 +0900 Message-Id: <20000907141506O.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IIRC, the only file that uses USA_RESIDENT is src/secure/lib/Makefile, and now it is gone away. Does this change imply that we are free from defining USA_RESIDENT when building the FreeBSD world ? Moreover, can we also throw USA_RESIDENT variable away from ports ? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 23:11:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id E1A0737B422 for ; Wed, 6 Sep 2000 23:11:50 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e876BRV02418 for ; Thu, 7 Sep 2000 03:11:27 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Sep 2000 03:11:27 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: SMP changes committed ... ? 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 thought one of the SMP developers announced that it was now committed, yet I haven't seen any commit messages for it ... I'm running the newest patch, so am waiting for the commit messages before I actually do my next upgrade ... Did I mis-read a message from earlier today? thanks .. Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 6 23:17: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from radon.gryphonsoft.com (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 8DBAD37B422 for ; Wed, 6 Sep 2000 23:17:03 -0700 (PDT) Received: by radon.gryphonsoft.com (Postfix, from userid 1000) id E3B211AB2; Thu, 7 Sep 2000 01:14:52 -0500 (EST) Date: Thu, 7 Sep 2000 01:14:52 -0500 From: Will Andrews To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP changes committed ... ? Message-ID: <20000907011452.K23702@radon.gryphonsoft.com> Reply-To: Will Andrews References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Thu, Sep 07, 2000 at 03:11:27AM -0300 X-Operating-System: FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 07, 2000 at 03:11:27AM -0300, The Hermit Hacker wrote: > I thought one of the SMP developers announced that it was now committed, > yet I haven't seen any commit messages for it ... I'm running the newest > patch, so am waiting for the commit messages before I actually do my next > upgrade ... They were committed about 4 hours ago. -- 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 Wed Sep 6 23:37:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7442037B422 for ; Wed, 6 Sep 2000 23:37:25 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA69415; Thu, 7 Sep 2000 08:39:05 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009070639.IAA69415@freebsd.dk> Subject: Re: HPT370 to stable In-Reply-To: from Ryan Shannon at "Sep 6, 2000 05:51:04 pm" To: shannor@cc.wwu.edu (Ryan Shannon) Date: Thu, 7 Sep 2000 08:39:05 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Ryan Shannon wrote: > Any idea how long it will be before the HPT370 support comes to stable? > I'm fairly new to freebsd, so it might not be the wisest maneuver for me > to CVSup to current :) It is in stable: |date: 2000/08/22 08:41:28; author: sos; state: Exp; lines: +105 -67 |MFC: | |Update with latest fixes from -current. | |ATA100 support. |New improved probe. |Multisector setup more restrictive ata-disk. |New error recovery in ata-disk. |Remove sequence checks in atapi-cd | |Brings -stable functionality up to and including following -current revisions: -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 Sep 7 0: 2:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-152.telepath.com [216.14.0.152]) by hub.freebsd.org (Postfix) with SMTP id 4337937B42C for ; Thu, 7 Sep 2000 00:02:41 -0700 (PDT) Received: (qmail 44456 invoked by uid 100); 7 Sep 2000 07:02:02 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14775.15722.421064.322187@guru.mired.org> Date: Thu, 7 Sep 2000 02:02:02 -0500 (CDT) To: Jason Evans Cc: current@freebsd.org Subject: Re: cvs commit: src/bin/ps print.c src/share/man/man9 mutex.9 Makefile src/usr.bin/top machine.c src/sys/alpha/alpha mp_machdep.c synch_machdep.c clock.c genassym.c interrupt.c ipl_funcs.c locore.s machdep.c mem.c pmap.c prom.c support.s swtch.s trap.c ... In-Reply-To: <88260720@toto.iv> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans writes: > jasone 2000/09/06 18:33:03 PDT > > Modified files: > bin/ps print.c [...] Nice try, but you didn't fool me. That's the SMP patch, even if the first change in the first modified file is a spelling fix in a comment in userland code! Nice to see it's here, though. Thanks guys, To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: USA_RESIDENT variable is no longer needed ? In-Reply-To: <20000907141506O.matusita@jp.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, 7 Sep 2000, Makoto MATSUSHITA wrote: > IIRC, the only file that uses USA_RESIDENT is src/secure/lib/Makefile, > and now it is gone away. Does this change imply that we are free from > defining USA_RESIDENT when building the FreeBSD world ? I believe so - I'm going to go over the crypto infrastructure and clean it up now that we've got RSA enabled the quick and dirty way. > Moreover, can we also throw USA_RESIDENT variable away from ports ? Perhaps..I'm not immediately sure. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 1:32:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from titan.cc.wwu.edu (titan.cc.wwu.edu [140.160.240.18]) by hub.freebsd.org (Postfix) with ESMTP id 2AC0937B422 for ; Thu, 7 Sep 2000 01:32:18 -0700 (PDT) Received: from localhost by titan.cc.wwu.edu (8.9.1/8.9.1) with ESMTP id BAA22042 for ; Thu, 7 Sep 2000 01:32:17 -0700 (PDT) Date: Thu, 7 Sep 2000 01:32:17 -0700 (PDT) From: Ryan Shannon To: freebsd-current@freebsd.org Subject: Re: HPT370 to stable In-Reply-To: <200009070639.IAA69415@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *ahem* oops... Thanks. :) Is it still writing in ATA66 mode? Thanks again, Ryan On Thu, 7 Sep 2000, Soren Schmidt wrote: > It seems Ryan Shannon wrote: > > Any idea how long it will be before the HPT370 support comes to stable? > > I'm fairly new to freebsd, so it might not be the wisest maneuver for m= e > > to CVSup to current :) >=20 > It is in stable: > |date: 2000/08/22 08:41:28; author: sos; state: Exp; lines: +105 -67 > |MFC: > | > |Update with latest fixes from -current. > | > |ATA100 support. > |New improved probe. > |Multisector setup more restrictive ata-disk. > |New error recovery in ata-disk. > |Remove sequence checks in atapi-cd > | > |Brings -stable functionality up to and including following -current revi= sions: >=20 >=20 > -S=F8ren >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 1:53:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 63C9D37B422 for ; Thu, 7 Sep 2000 01:53:43 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA01113; Thu, 7 Sep 2000 10:55:25 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009070855.KAA01113@freebsd.dk> Subject: Re: HPT370 to stable In-Reply-To: from Ryan Shannon at "Sep 7, 2000 01:32:17 am" To: shannor@cc.wwu.edu (Ryan Shannon) Date: Thu, 7 Sep 2000 10:55:25 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Ryan Shannon wrote: >*ahem* oops... Thanks. :) > >Is it still writing in ATA66 mode? Well, sortof, I havn't been able to make it go as fast as I want, even when using HPTs method, thats why it done like it is. However it does go faster than when using ATA66... I'm investigating this issue, but for present disks its more than fast enough... -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 Sep 7 2:27:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 0D64237B422 for ; Thu, 7 Sep 2000 02:27:36 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13Wxxv-0002p0-00; Thu, 07 Sep 2000 11:27:27 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id LAA08136; Thu, 7 Sep 2000 11:27:26 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 7958; Thu Sep 7 11:26:02 2000 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e879RCD12185; Thu, 7 Sep 2000 11:27:13 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009070927.e879RCD12185@grimreaper.grondar.za> To: William Woods Cc: freebsd-current@FreeBSD.ORG Subject: Re: PERL 5.6 References: In-Reply-To: ; from William Woods "Wed, 06 Sep 2000 12:18:26 MST." Date: Thu, 07 Sep 2000 11:27:11 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can anyoine give me an idea when Perl 5.6 will be merged from current into > stable? Real Soon Now(tm). 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 Sep 7 2:33:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id E31C237B422 for ; Thu, 7 Sep 2000 02:33:07 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13Wy3D-0002vR-00; Thu, 07 Sep 2000 11:32:55 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id LAA09031; Thu, 7 Sep 2000 11:32:54 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 8605; Thu Sep 7 11:30:31 2000 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e879VjD12267; Thu, 7 Sep 2000 11:31:48 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009070931.e879VjD12267@grimreaper.grondar.za> To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: USA_RESIDENT variable is no longer needed ? References: <20000907141506O.matusita@jp.FreeBSD.org> In-Reply-To: <20000907141506O.matusita@jp.FreeBSD.org> ; from Makoto MATSUSHITA "Thu, 07 Sep 2000 14:15:06 +0900." Date: Thu, 07 Sep 2000 11:31:44 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > IIRC, the only file that uses USA_RESIDENT is src/secure/lib/Makefile, > and now it is gone away. Does this change imply that we are free from > defining USA_RESIDENT when building the FreeBSD world ? > > Moreover, can we also throw USA_RESIDENT variable away from ports ? I believe we can start doing that. The only Crypto issue outstanding at the monent is IDEA, and as far as I can work out, the patent there expires in 2007. IDEA is well covered by WANT_IDEA (or whatever its called). 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 Sep 7 2:52:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from venus.cs.put.poznan.pl (vega.cs.put.poznan.pl [150.254.30.30]) by hub.freebsd.org (Postfix) with ESMTP id 02E6B37B422 for ; Thu, 7 Sep 2000 02:52:44 -0700 (PDT) Received: from cs.put.poznan.pl (dcs-430x-pw.cs.put.poznan.pl [150.254.31.188]) by venus.cs.put.poznan.pl (8.10.2/8.10.2) with ESMTP id e879kTU18493 for ; Thu, 7 Sep 2000 11:46:29 +0200 (CEST) Message-ID: <39B76512.CCC0DFFA@cs.put.poznan.pl> Date: Thu, 07 Sep 2000 11:51:14 +0200 From: Piotr =?iso-8859-1?Q?Wo=9Fniak?= X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: XFree86 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have installed XFree86 and there is no XF86Setup. Have you any idea - why? I want to increase depth of color and modifing /etc/XF86Config has no result. How can I do it? Piotr Wozniak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 3:41:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from calcaphon.demon.co.uk (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 6180E37B505 for ; Thu, 7 Sep 2000 03:41:15 -0700 (PDT) Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by calcaphon.demon.co.uk (8.9.3/8.9.1) with ESMTP id LAA63311; Thu, 7 Sep 2000 11:40:57 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id LAA57150; Thu, 7 Sep 2000 11:39:41 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Thu, 7 Sep 2000 11:39:41 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Donn Miller Cc: USB BSD list , freebsd-current@freebsd.org Subject: Re: uscanner driver 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 Did you check on the SANE home page whether your scanner is supported? This is a USB driver and a trivial driver at that, with no vendor specific code. So I won't be able to help. Nick > > I've quickly thrown together a driver for USB scanners. Unforunately, I > > don't have a scanner available that is supported by SANE, so I can't > > test it. > > How about parallel scanners? I have a UMAX Astra 2000p PPT scanner. I've > heard that UMAX didn't want to release the specs, because they've got a > proprietary ASIC in there. If anyone's willing to discuss this matter on > a different list, I'm willing to do so. > > -Donn > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 4: 6:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 4748C37B424; Thu, 7 Sep 2000 04:06:33 -0700 (PDT) Received: from work.mzaki.nom (191.pool9.ipctokyo.att.ne.jp [165.76.205.191]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id UAA22859; Thu, 7 Sep 2000 20:06:21 +0900 (JST) Date: Thu, 07 Sep 2000 20:06:20 +0900 Message-ID: <86ya14ihqr.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: jasone@canonware.com Cc: smp@freebsd.org, current@freebsd.org Subject: Re: SMP mega-commit complete In-Reply-To: In your message of "6 Sep 2000 18:35:17 -0700" <20000906180743.O437@blitz.canonware.com> References: <20000906180743.O437@blitz.canonware.com> X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6 Sep 2000 18:35:17 -0700, Jason Evans wrote: > If you run into issues that appear related to the SMP changes, and they > aren't listed as known issues, please bring them up on the -smp or -current > mailing list. this breaks building GENERIC kernel. 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/opt/usr/src/sys -I/opt/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /opt/usr/src/sys/i386/i386/genassym.c In file included from /opt/usr/src/sys/sys/signalvar.h:42, from /opt/usr/src/sys/sys/user.h:59, from /opt/usr/src/sys/i386/i386/genassym.c:66: machine/smp.h:19: #error SMP not supported with I386_CPU *** Error code 1 -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 4: 9:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay2.inwind.it (relay2.inwind.it [212.141.53.73]) by hub.freebsd.org (Postfix) with ESMTP id 1ABC837B422 for ; Thu, 7 Sep 2000 04:09:51 -0700 (PDT) Received: from bartequi.ottodomain.org (212.141.79.254) by relay2.inwind.it (5.1.046) id 39AF9CE300064821; Thu, 7 Sep 2000 13:09:43 +0200 From: Salvo Bartolotta Date: Thu, 07 Sep 2000 12:09:50 GMT Message-ID: <20000907.12095000@bartequi.ottodomain.org> Subject: Re: XFree86 To: Piotr =?ISO-8859-1?Q?Wo=9Fniak?= Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <39B76512.CCC0DFFA@cs.put.poznan.pl> References: <39B76512.CCC0DFFA@cs.put.poznan.pl> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 9/7/00, 10:51:14 AM, Piotr Wo=9Fniak = =20 wrote regarding XFree86: > Hi, > I have installed XFree86 and there is no XF86Setup. Have you any idea = - > why? > I want to increase depth of color and modifing /etc/XF86Config has no > result. > How can I do it? > Piotr Wozniak Dear Piotr Wozniak, When I installed XFree86 3.3.6 (via the ports mechanism), I had the=20 opportunity of installing the VGA server(s). More precisely: [...] Which servers do you wish to build, you can save a lot of disk space by only compiling the server you will be using. It will also save you considerable compile time. *** If you want to use XF86Setup to set the INITIAL configuration, *** then you must build the VGA server Do you want to build the VGA16 server? [YES] Y Do you want to build the VGA16Dual server? [YES] Y [...] =20 As to modeline "hacking", you may wish to have a look at=20 http://www.linux.org/docs/ldp/howto/XFree86-Video-Timings-HOWTO.html,=20 and/or at Greg's excellent book (The Complete FreeBSD). =20 HTH, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 4:18:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 78FB937B42C for ; Thu, 7 Sep 2000 04:18:50 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13Wzgg-0004k2-00; Thu, 07 Sep 2000 13:17:46 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA28479; Thu, 7 Sep 2000 13:17:45 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 28337; Thu Sep 7 13:16:57 2000 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e87BI8D12655; Thu, 7 Sep 2000 13:18:08 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009071118.e87BI8D12655@grimreaper.grondar.za> To: Piotr =?iso-8859-1?Q?Wo=9Fniak?= Cc: freebsd-current Subject: Re: XFree86 References: <39B76512.CCC0DFFA@cs.put.poznan.pl> In-Reply-To: <39B76512.CCC0DFFA@cs.put.poznan.pl> ; from Piotr =?iso-8859-1?Q?Wo=9Fniak?= "Thu, 07 Sep 2000 11:51:14 +0200." Date: Thu, 07 Sep 2000 13:18:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I have installed XFree86 and there is no XF86Setup. Have you any idea - > why? > I want to increase depth of color and modifing /etc/XF86Config has no > result. Tcl/Tk. Build X, clean it out. Build Tcl/Tk 8.2. Build X again. You'll have XF86Setup. BTW - there is no XF86Setup in XFree86-4 yet. 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 Sep 7 4:58: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay2.inwind.it (relay2.inwind.it [212.141.53.73]) by hub.freebsd.org (Postfix) with ESMTP id EB26637B422 for ; Thu, 7 Sep 2000 04:58:05 -0700 (PDT) Received: from bartequi.ottodomain.org (212.141.79.254) by relay2.inwind.it (5.1.046) id 39AF9CE300066284; Thu, 7 Sep 2000 13:57:13 +0200 From: Salvo Bartolotta Date: Thu, 07 Sep 2000 12:57:19 GMT Message-ID: <20000907.12571900@bartequi.ottodomain.org> Subject: Re: XFree86 To: Mark Murray Cc: piotr.wozniak@cs.put.poznan.pl, freebsd-current@FreeBSD.ORG In-Reply-To: <200009071118.e87BI8D12655@grimreaper.grondar.za> References: <39B76512.CCC0DFFA@cs.put.poznan.pl> <200009071118.e87BI8D12655@grimreaper.grondar.za> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 9/7/00, 12:18:07 PM, Mark Murray wrote regarding=20 Re: XFree86 : > > Hi, > > I have installed XFree86 and there is no XF86Setup. Have you any ide= a=20 - > > why? > > I want to increase depth of color and modifing /etc/XF86Config has n= o > > result. > Tcl/Tk. > Build X, clean it out. Build Tcl/Tk 8.2. Build X again. You'll have=20 XF86Setup. > BTW - there is no XF86Setup in XFree86-4 yet. > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org Dear Mark Murray, from my installation.log, just to add another datapoint: =3D=3D=3D> Configuring for XFree86-3.3.6 Using tk-8.3 Which servers do you wish to build, you can save a lot of disk space by only compiling the server you will be using. It will also save you considerable compile time. *** If you want to use XF86Setup to set the INITIAL configuration, *** then you must build the VGA server Do you want to build the VGA16 server? [YES] Y Do you want to build the VGA16Dual server? [YES] Y IMHE, the configuration is possible via [a] few different versions;=20 mine is, er, are currently tcl-8.3.1 and tcl-8.2.3; I recall=20 installing XFree86-3.3.6 immediately after I had installed tk-8.3 (ie=20 which, in turn, installed tcl-8.3.1). Also, as a quick look at the PLIST confirms, different versions of Tcl=20 -- Tool Command Language -- can (should) happily coexist :-) Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 5:32:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 78F5F37B422 for ; Thu, 7 Sep 2000 05:32:11 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13X0qY-0005sg-00; Thu, 07 Sep 2000 14:32:02 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id OAA12280; Thu, 7 Sep 2000 14:31:59 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 12212; Thu Sep 7 14:31:29 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13X0q1-000NlQ-00; Thu, 07 Sep 2000 14:31:29 +0200 From: Sheldon Hearn To: Visigoth Cc: current@freebsd.org Subject: Re: cold boot in -STABLE In-reply-to: Your message of "Wed, 06 Sep 2000 19:57:55 EST." Date: Thu, 07 Sep 2000 14:31:29 +0200 Message-ID: <91351.968329889@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 06 Sep 2000 19:57:55 EST, Visigoth wrote: > -stable (world and kernel) built today seems to be causing the > system to cold boot when attempting to mount floppy disk on 2 of my > systems (held off on building the others) . It's odd that you should send this STABLE-related report to the -current mailing list. :-) Evben odder is that I thought for a moment that you might be seeing what I'm seeing in -current with spontaneous reboots. Could you confirm that you're really talking about STABLE? If not, I'll post some datapoints about the spontaneous reboots in CURRENT. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 5:58:56 2000 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 6A20037B422 for ; Thu, 7 Sep 2000 05:58:53 -0700 (PDT) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.11.0/8.9.3) id e87Cwhr10918; Thu, 7 Sep 2000 19:58:43 +0700 (NOVST) (envelope-from nnd) Date: Thu, 7 Sep 2000 19:58:43 +0700 (NOVST) Message-Id: <200009071258.e87Cwhr10918@wint.itfs.nsk.su> From: Nickolay Dudorov To: current@FreeBSD.ORG Subject: Re: cvs commit: src/bin/ps print.c src/share/man/man9 mutex.9 Makefile src/usr.bin/top machine.c src/sys/alpha/alpha mp_machdep.c synch_machdep.c clock.c genassym.c interrupt.c ipl_funcs.c locore.s machdep.c mem.c pmap.c prom.c support.s swtch.s trap.c ... In-Reply-To: <200009070133.SAA10582@freefall.freebsd.org> X-Newsgroups: itfs.freebsd.cvs.all User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009070133.SAA10582@freefall.freebsd.org> you wrote: > jasone 2000/09/06 18:33:03 PDT > > Modified files: ..... > 1.7 +39 -5 src/sys/i386/include/globals.h One of the changes is at line 107 : #define currentldt GLOBAL_LVALUE(currentldt, int) was changed to #define currentldt GLOBAL_RVALUE(currentldt, int) whereas in 'sys/i386/i386/machdep.c' at line 1914 we have currentldt = _default_ldt; and it leads to error while making kernel. All this lines are guarded by USER_LDT option, so you can make your kernel but my is not buildable ;-( After reverting this L->RVALUE change I at least can build kernel. Let's see how (if ever) it will work. 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 Sep 7 6:21:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id 43B2937B423 for ; Thu, 7 Sep 2000 06:21:30 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id 3594820F01; Thu, 7 Sep 2000 08:26:29 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id 24F8E1D102; Thu, 7 Sep 2000 08:26:29 -0500 (CDT) Date: Thu, 7 Sep 2000 08:26:20 -0500 (CDT) From: Visigoth To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: cold boot in -STABLE In-Reply-To: <91351.968329889@axl.fw.uunet.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Sep 2000, Sheldon Hearn wrote: > > It's odd that you should send this STABLE-related report to the -current > mailing list. :-) Yea, sorry, -current is where I am subscribed, as well as where I KNOW people pay attention ;) I'll keep it in mind... > Evben odder is that I thought for a moment that you might be seeing what > I'm seeing in -current with spontaneous reboots. As was in my dmesg: FreeBSD 4.1-STABLE #0: Wed Sep 6 12:28:02 CDT 2000 visigoth@mail.telemere.net:/usr/src/sys/compile/MAIL Yup, stable it is (or was ;) Visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBObeJdDnmC/+RTnGeEQLvLACg5XZo1k7zXEM0rp12+WWoeVDlRFwAninS 3mYV3sc3EAQcFgtO6fX5iYRf =R3T1 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 6:56:48 2000 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 007D437B422 for ; Thu, 7 Sep 2000 06:56:36 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.11.0/8.11.0) id e87DuNQ16523 for freebsd-current@FreeBSD.ORG; Thu, 7 Sep 2000 15:56:23 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200009071356.e87DuNQ16523@zibbi.mikom.csir.co.za> Subject: USER_LDT broken in current To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Thu, 7 Sep 2000 15:56:22 +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 Hi, I got this error when trying to build a kernel with USER_LDT and -current source. Its not a problem because I'm not using it at the moment, I just thought I'll mention it. cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/machdep.c ../../i386/i386/machdep.c: In function `init386': ../../i386/i386/machdep.c:1914: invalid lvalue in assignment *** Error code 1 John -- John Hay -- John.Hay@icomtek.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 Thu Sep 7 7: 5:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 780F637B422 for ; Thu, 7 Sep 2000 07:05:52 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13X2JJ-0007Sk-00 for current@freebsd.org; Thu, 07 Sep 2000 16:05:49 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA00512 for ; Thu, 7 Sep 2000 16:05:48 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 288; Thu Sep 7 16:04:11 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13X2Hj-0000B3-00 for current@FreeBSD.org; Thu, 07 Sep 2000 16:04:11 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: HEADS UP: linux module breaks current Date: Thu, 07 Sep 2000 16:04:11 +0200 Message-ID: <684.968335451@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Just a warning to anyone wanting to try out SMPng -- make sure that you hdon't have ``linux_enable="YES"'' in /etc/rc.conf. I got a kernel trap when /etc/rc tried to load the linux module. I haven't had time to get a panic and backtrace to Marcel, but I thought I'd send this warning for now. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 9:32:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 2B8E537B42C; Thu, 7 Sep 2000 09:32:33 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA30137; Thu, 7 Sep 2000 12:32:32 -0400 (EDT) (envelope-from wollman) Date: Thu, 7 Sep 2000 12:32:32 -0400 (EDT) From: Garrett Wollman Message-Id: <200009071632.MAA30137@khavrinen.lcs.mit.edu> To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: USA_RESIDENT variable is no longer needed ? In-Reply-To: References: <20000907141506O.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> Moreover, can we also throw USA_RESIDENT variable away from ports ? > Perhaps..I'm not immediately sure. This is almost certainly not the last patent issue we'll have to deal with. Unfortunately, it is probably the last one which can be dealt with so simply (since the U.S. has now managed to stick its idiotic patents on everybody else). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 9:33:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id BFDA437B422 for ; Thu, 7 Sep 2000 09:33:50 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-213-168-64-75.netcologne.de [213.168.64.75]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id SAA06650; Thu, 7 Sep 2000 18:33:33 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e87GXKe01107; Thu, 7 Sep 2000 18:33:20 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Thu, 7 Sep 2000 18:33:20 +0200 (CEST) From: Paul Herman To: freebsd-current@freebsd.org Cc: Vivek Khera Subject: call for testers: init securelevel patch 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, Here is a patch which will allow init(8) (or rather, any process with PID 1) to lower the securelevel to 0 when going into single-user maintenence mode. This has no effect if securelevel is -1. Feedback welcome -- there may be security implications I'm not aware of. If this is well recieved, I will tack it onto bin/20974 for further review and commit into -CURRENT. -Paul. begin 644 init_securelevel.patch.gz M'XL(")&]MSD"`VEN:71?G%V^[@[T) MT^.U9=XZW0;"%B_!0=M.51,LN-]VIX/)!$D'?]RZ>#ELN;EK*_3C"J1:%@3/ MGR%C9*GB77(:MWY1C@NAG9SZ@W0P2I.C#^4TWB6G?OKIA9R.ATY-;,=>2_%5 M%3#/SROBS3+ETJYXCEHCEXL%:5*VX To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: HEADS UP: linux module breaks current In-Reply-To: <684.968335451@axl.fw.uunet.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 On Thu, 7 Sep 2000, Sheldon Hearn wrote: > Just a warning to anyone wanting to try out SMPng -- make sure that you > hdon't have ``linux_enable="YES"'' in /etc/rc.conf. > > I got a kernel trap when /etc/rc tried to load the linux module. I > haven't had time to get a panic and backtrace to Marcel, but I thought > I'd send this warning for now. This is usually a pretty good sign of an out of date linux module. Be sure you are up to date, especially since modules now live in a different location. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 11:57:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 3D5F537B423 for ; Thu, 7 Sep 2000 11:57:51 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 528A0E8D1; Thu, 7 Sep 2000 14:57:38 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.0/8.11.0) id e87IvbK45009; Thu, 7 Sep 2000 14:57:37 -0400 (EDT) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14775.58657.905594.704448@onceler.kciLink.com> Date: Thu, 7 Sep 2000 14:57:37 -0400 (EDT) To: Paul Herman Cc: freebsd-current@freebsd.org Subject: Re: call for testers: init securelevel patch In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your patch does seem to do the right thing for me. Now I can run the system at a securelevel and when I go to single user mode, I can still do necessary system maintenance. The only thing I saw that was a bit unexpected is that when I went to single user mode and typed "reboot" it went back to securelevel 1 before it killed off the remaining processes. Not a big deal, but juse a bit unexpected. I think the only thing to watch for is that process ID 1 cannot be re-used even if init dies and the system magically still keeps running. If pid 1 cannot ever be reassigned, I think it should be a safe patch. In any case, I'm going to use it on my systems even if it doesn't get MFC'd back to -stable (it applied perfectly cleanly.) Thanks! -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 12:31:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from volatile.chemicals.tacorp.com (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id CE2B637B424; Thu, 7 Sep 2000 12:31:12 -0700 (PDT) Received: (from morganw@localhost) by volatile.chemicals.tacorp.com (8.11.0/8.11.0) id e87JV7f31509; Thu, 7 Sep 2000 15:31:07 -0400 (EDT)?g (envelope-from morganw)œ Date: Thu, 7 Sep 2000 15:31:06 -0400 (EDT) From: Wesley Morgan To: Jason Evans Cc: smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SMP mega-commit complete In-Reply-To: <20000906180743.O437@blitz.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, Jason Evans wrote: > A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches > have now been committed. Is it safe to follow src-sys from PRE_SMPNG and everything else as -current? -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ wesleymorgan@home.com _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 12:38: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 7740537B422 for ; Thu, 7 Sep 2000 12:38:01 -0700 (PDT) Received: (qmail 73504 invoked by uid 1142); 7 Sep 2000 19:38:00 -0000 Date: 7 Sep 2000 12:38:00 -0700 Date: Thu, 7 Sep 2000 12:37:53 -0700 From: Jason Evans To: Wesley Morgan Cc: current@FreeBSD.ORG Subject: Re: SMP mega-commit complete Message-ID: <20000907123753.Q437@blitz.canonware.com> References: <20000906180743.O437@blitz.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from morganw@chemicals.tacorp.com on Thu, Sep 07, 2000 at 03:31:06PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 07, 2000 at 03:31:06PM -0400, Wesley Morgan wrote: > On Wed, 6 Sep 2000, Jason Evans wrote: > > > A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches > > have now been committed. > > Is it safe to follow src-sys from PRE_SMPNG and everything else as > -current? top and ps won't work quite right if you do that. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 13:26:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from uffdaonline.net (host21.uffdaonline.net [207.109.235.21]) by hub.freebsd.org (Postfix) with ESMTP id DACF537B423 for ; Thu, 7 Sep 2000 13:26:29 -0700 (PDT) Received: by uffdaonline.net (Postfix, from userid 1000) id B59A31FA7; Thu, 7 Sep 2000 20:29:23 +0000 (GMT) Date: Thu, 7 Sep 2000 15:29:23 -0500 From: "Zach N. Heilig" To: Paul Herman Cc: freebsd-current@freebsd.org, Vivek Khera Subject: Re: call for testers: init securelevel patch Message-ID: <20000907152923.A57609@murkwood.znh.org> References: <27A0189D7DCC8869C6B714D2@mail.uffdaonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <27A0189D7DCC8869C6B714D2@mail.uffdaonline.net>; from pherman@frenchfries.net on Thu, Sep 07, 2000 at 06:33:20PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 07, 2000 at 06:33:20PM +0200, Paul Herman wrote: > Here is a patch which will allow init(8) (or rather, any process with > PID 1) to lower the securelevel to 0 when going into single-user > maintenence mode. This has no effect if securelevel is -1. > > Feedback welcome -- there may be security implications I'm not aware > of. If this is well recieved, I will tack it onto bin/20974 for > further review and commit into -CURRENT. This was the behavior a while back. It was removed on purpose. (because an attacker could attach to PID 1 with a debugger and cause it to lower secure level without going to single user mode.) -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 14:29:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 20BC537B422; Thu, 7 Sep 2000 14:29:14 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA39022; Thu, 7 Sep 2000 15:29:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA06098; Thu, 7 Sep 2000 15:29:03 -0600 (MDT) Message-Id: <200009072129.PAA06098@harmony.village.org> To: The Hermit Hacker Subject: Re: 'interrupt-level buffer overflows' for sio device? Cc: freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG In-reply-to: Your message of "Wed, 06 Sep 2000 21:06:26 -0300." References: Date: Thu, 07 Sep 2000 15:29:02 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message The Hermit Hacker writes: : sio1: 32 more interrupt-level buffer overflows (total 32) From the man page: sio%d: interrupt-level buffer overflow. Problem in the bottom half of the driver. This likely means that the bottom half of sio isn't running fast enough to harvest the characters in the interrupt level buffers. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 14:32: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 7A99F37B424 for ; Thu, 7 Sep 2000 14:31:58 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id OAA18333; Thu, 7 Sep 2000 14:31:13 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009072131.OAA18333@pike.osd.bsdi.com> Subject: Re: SMP mega-commit complete In-Reply-To: <20000907123753.Q437@blitz.canonware.com> from Jason Evans at "Sep 7, 2000 12:37:53 pm" To: Jason Evans Date: Thu, 7 Sep 2000 14:31:13 -0700 (PDT) Cc: Wesley Morgan , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 Jason Evans wrote: > On Thu, Sep 07, 2000 at 03:31:06PM -0400, Wesley Morgan wrote: > > On Wed, 6 Sep 2000, Jason Evans wrote: > > > > > A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches > > > have now been committed. > > > > Is it safe to follow src-sys from PRE_SMPNG and everything else as > > -current? > > top and ps won't work quite right if you do that. Err, no. They will work perfectly fine, they just won't compile. :) > Jason -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 14:58: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2E20237B423 for ; Thu, 7 Sep 2000 14:58:00 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id IAA07604; Fri, 8 Sep 2000 08:57:34 +1100 Date: Fri, 8 Sep 2000 08:57:30 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Zach N. Heilig" Cc: Paul Herman , freebsd-current@FreeBSD.ORG, Vivek Khera Subject: Re: call for testers: init securelevel patch In-Reply-To: <20000907152923.A57609@murkwood.znh.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, 7 Sep 2000, Zach N. Heilig wrote: > On Thu, Sep 07, 2000 at 06:33:20PM +0200, Paul Herman wrote: > > Here is a patch which will allow init(8) (or rather, any process with > > PID 1) to lower the securelevel to 0 when going into single-user > > maintenence mode. This has no effect if securelevel is -1. > > > > Feedback welcome -- there may be security implications I'm not aware > > of. If this is well recieved, I will tack it onto bin/20974 for > > further review and commit into -CURRENT. > > This was the behavior a while back. It was removed on purpose. (because > an attacker could attach to PID 1 with a debugger and cause it to lower > secure level without going to single user mode.) RCS file: /home/ncvs/src/sys/kern/kern_mib.c,v Working file: kern_mib.c head: 1.37 ... ---------------------------- revision 1.9 date: 1997/06/25 07:31:47; author: joerg; state: Exp; lines: +2 -2 Don't ever allow lowering the securelevel at all. Allowing it does nothing good except of opening a can of (potential or real) security holes. People maintaining a machine with higher security requirements need to be on the console anyway, so there's no point in not forcing them to reboot before starting maintenance. Agreed by: hackers, guido ---------------------------- Index: kern_mib.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mib.c,v retrieving revision 1.8 retrieving revision 1.9 diff -c -2 -r1.8 -r1.9 *** kern_mib.c 1997/03/04 18:31:54 1.8 --- kern_mib.c 1997/06/25 07:31:47 1.9 *************** *** 38,42 **** * * @(#)kern_sysctl.c 8.4 (Berkeley) 4/14/94 ! * $Id: kern_mib.c,v 1.7 1997/03/03 12:58:19 bde Exp $ */ --- 38,42 ---- * * @(#)kern_sysctl.c 8.4 (Berkeley) 4/14/94 ! * $Id: kern_mib.c,v 1.8 1997/03/04 18:31:54 bde Exp $ */ *************** *** 124,128 **** if (error || !req->newptr) return (error); ! if (level < securelevel && req->p->p_pid != 1) return (EPERM); securelevel = level; --- 124,128 ---- if (error || !req->newptr) return (error); ! if (level < securelevel) return (EPERM); securelevel = level; Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 15: 0:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 6645837B42C for ; Thu, 7 Sep 2000 15:00:17 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-213-168-64-238.netcologne.de [213.168.64.238]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id AAA20060; Fri, 8 Sep 2000 00:00:05 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e87Lxr900419; Thu, 7 Sep 2000 23:59:53 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Thu, 7 Sep 2000 23:59:52 +0200 (CEST) From: Paul Herman To: "Zach N. Heilig" Cc: freebsd-current@FreeBSD.ORG, Vivek Khera Subject: Re: call for testers: init securelevel patch In-Reply-To: <20000907152923.A57609@murkwood.znh.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, 7 Sep 2000, Zach N. Heilig wrote: > On Thu, Sep 07, 2000 at 06:33:20PM +0200, Paul Herman wrote: > > > Here is a patch which will allow init(8) (or rather, any process with > > PID 1) to lower the securelevel to 0 when going into single-user > > maintenence mode. This has no effect if securelevel is -1. > > This was the behavior a while back. It was removed on purpose. (because > an attacker could attach to PID 1 with a debugger and cause it to lower > secure level without going to single user mode.) You can't trace PID 1 when securelevel > 0. /src/sys/kern/subr_process.c So I think it's still safe... -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 15:54:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 2FDE637B43E; Thu, 7 Sep 2000 15:54:48 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-213-168-64-109.netcologne.de [213.168.64.109]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id AAA23711; Fri, 8 Sep 2000 00:54:46 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e87MscP00647; Fri, 8 Sep 2000 00:54:39 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Fri, 8 Sep 2000 00:54:38 +0200 (CEST) From: Paul Herman To: freebsd-hackers@FreeBSD.ORG Subject: the ol' init securelevel thread 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, [ Bcc'ed to -current ] Perhaps it was a mistake :) but I took up someone else's cause and started a thread on -current which now probably belongs on -hackers. So: What are the dangers of having init lower the securelevel to 0 when the system goes into single user? Looking at the mailing list archive, this seems to be a re-occuring thread which always ended up open-ended with no real answer. Already established: * you _can't_ ptrace(2) init when securelevel > 0 * rev1.9 of kern_mib.c unfortunately states nothing concrete * both NetBSD and OpenBSD allow this behaviour * Easy, I'm not married to this idea :-) Just interested "academicaly" So, what dangers are there? -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 16: 0:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1]) by hub.freebsd.org (Postfix) with ESMTP id A35F237B423; Thu, 7 Sep 2000 16:00:26 -0700 (PDT) Received: from berserker.bsdi.com (cp@LOCALHOST [127.0.0.1]) by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA24702; Thu, 7 Sep 2000 17:00:15 -0600 (MDT) Message-Id: <200009072300.RAA24702@berserker.bsdi.com> To: Warner Losh Cc: The Hermit Hacker , freebsd-current@freebsd.org, freebsd-smp@freebsd.org Subject: Re: 'interrupt-level buffer overflows' for sio device? From: Chuck Paterson Date: Thu, 07 Sep 2000 17:00:15 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, this is very likely not caused by the heavy weight interrupt threads, but rather because the interrupt threads can't be run because the giant lock is held by a process running in the kernel. Once we get drivers to have their own locking and pulled out from under the giant lock this problem should deminish greatly. Before we can do this there are various infrastructure pieces which must be made mp safe, such as the lockmanger. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 16:42:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from neodymium.btinternet.com (neodymium.btinternet.com [194.73.73.83]) by hub.freebsd.org (Postfix) with ESMTP id A543E37B423 for ; Thu, 7 Sep 2000 16:42:28 -0700 (PDT) Received: from host213-1-170-68.btinternet.com ([213.1.170.68] helo=btinternet.com) by neodymium.btinternet.com with esmtp (Exim 3.03 #83) id 13XBJG-0005tI-00 for freebsd-current@freebsd.org; Fri, 08 Sep 2000 00:42:23 +0100 Message-ID: <39B8230F.65C05246@btinternet.com> Date: Fri, 08 Sep 2000 00:21:51 +0100 From: John Toon X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: XFree86 References: <39B76512.CCC0DFFA@cs.put.poznan.pl> <200009071118.e87BI8D12655@grimreaper.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > BTW - there is no XF86Setup in XFree86-4 yet. No, but there is xf86cfg, which is even better ;^) It correctly autodetected both my Monitor and Video card, meaning that I was able to get maximum performance out of both (proper Modelines). Though 1962x1440 is pushing it on a 19" monitor ;^) I think I'll stick to 1600x1200. -- "I'm entirely unaccountable for any moments of sanity contained herein." :s/Windows/UNIX John Toon | j.a.toon@btinternet.com | "Sonnilon" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 17: 9:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C173437B424 for ; Thu, 7 Sep 2000 17:09:47 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8809bP89049; Fri, 8 Sep 2000 09:39:37 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 09:39:37 +0930 From: Greg Lehey To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP changes committed ... ? Message-ID: <20000908093937.B83632@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from scrappy@hub.org on Thu, Sep 07, 2000 at 03:11:27AM -0300 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 September 2000 at 3:11:27 -0300, The Hermit Hacker wrote: > > I thought one of the SMP developers announced that it was now committed, > yet I haven't seen any commit messages for it ... I'm running the newest > patch, so am waiting for the commit messages before I actually do my next > upgrade ... > > Did I mis-read a message from earlier today? There were only two relatively short commit messages. 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 Thu Sep 7 17:13:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id C23A837B423 for ; Thu, 7 Sep 2000 17:13:25 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e880CW201464; Thu, 7 Sep 2000 21:12:36 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 7 Sep 2000 21:12:32 -0300 (ADT) From: The Hermit Hacker To: Greg Lehey Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP changes committed ... ? In-Reply-To: <20000908093937.B83632@wantadilla.lemis.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, 8 Sep 2000, Greg Lehey wrote: > On Thursday, 7 September 2000 at 3:11:27 -0300, The Hermit Hacker wrote: > > > > I thought one of the SMP developers announced that it was now committed, > > yet I haven't seen any commit messages for it ... I'm running the newest > > patch, so am waiting for the commit messages before I actually do my next > > upgrade ... > > > > Did I mis-read a message from earlier today? > > There were only two relatively short commit messages. ah, okay, the patch I applied before teh commits felt like there should be a bunch of messages ;( thanks for confirming :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 17:14:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 3FBE037B42C for ; Thu, 7 Sep 2000 17:14:08 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e880Dp991238; Fri, 8 Sep 2000 09:43:51 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 09:43:51 +0930 From: Greg Lehey To: Motomichi Matsuzaki Cc: FreeBSD current users Subject: Re: SMP mega-commit complete Message-ID: <20000908094351.C83632@wantadilla.lemis.com> References: <20000906180743.O437@blitz.canonware.com> <86ya14ihqr.wl@tkc.att.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86ya14ihqr.wl@tkc.att.ne.jp>; from mzaki@e-mail.ne.jp on Thu, Sep 07, 2000 at 08:06:20PM +0900 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 September 2000 at 20:06:20 +0900, Motomichi Matsuzaki wrote: > > At 6 Sep 2000 18:35:17 -0700, > Jason Evans wrote: >> If you run into issues that appear related to the SMP changes, and they >> aren't listed as known issues, please bring them up on the -smp or -current >> mailing list. > > this breaks building GENERIC kernel. > > 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/opt/usr/src/sys -I/opt/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /opt/usr/src/sys/i386/i386/genassym.c > In file included from /opt/usr/src/sys/sys/signalvar.h:42, > from /opt/usr/src/sys/sys/user.h:59, > from /opt/usr/src/sys/i386/i386/genassym.c:66: > machine/smp.h:19: #error SMP not supported with I386_CPU > *** Error code 1 Sorry, my bad. Pass the pointy hat. I didn't know that smp.h was included in a non-SMP system. I see that John Baldwin has already committed a fix. 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 Thu Sep 7 17:19:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id A592137B422 for ; Thu, 7 Sep 2000 17:19:14 -0700 (PDT) Received: (from steve@localhost) by virtual-voodoo.com (8.11.0.Beta3/8.11.0.Beta3) id e880JD606566 for freebsd-current@freebsd.org; Thu, 7 Sep 2000 19:19:13 -0500 (EST) Date: Thu, 7 Sep 2000 19:19:13 -0500 From: Steve Ames To: freebsd-current@freebsd.org Subject: microuptime() went backwards Message-ID: <20000907191913.A93124@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just upgraded to -CURRENT as of about noon (EST) today. At reboot I got a lot of these: microuptime() went backwards (1.7682417 -> 1.997434) I recall reading in -current earlier this week that someone was looking for victims getting this. What further information can I provide? -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 17:23:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 602E937B422; Thu, 7 Sep 2000 17:23:25 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e880MsN95987; Fri, 8 Sep 2000 09:52:54 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 09:52:54 +0930 From: Greg Lehey To: Chuck Paterson Cc: Warner Losh , The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: 'interrupt-level buffer overflows' for sio device? Message-ID: <20000908095254.E83632@wantadilla.lemis.com> References: <200009072300.RAA24702@berserker.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009072300.RAA24702@berserker.bsdi.com>; from cp@bsdi.com on Thu, Sep 07, 2000 at 05:00:15PM -0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 September 2000 at 17:00:15 -0600, Chuck Paterson wrote: > FYI, this is very likely not caused by the heavy weight > interrupt threads, but rather because the interrupt threads can't > be run because the giant lock is held by a process running in the > kernel. Once we get drivers to have their own locking and pulled out > from under the giant lock this problem should deminish greatly. Before > we can do this there are various infrastructure pieces which must > be made mp safe, such as the lockmanger. We're running sio as a fast interrupt, so it's definitely not because of a heavyweight thread :-) I think fast interrupts also completely bypass mutexes, though something might have changed since I last looked. 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 Thu Sep 7 17:28:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id CF79437B422 for ; Thu, 7 Sep 2000 17:28:19 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id RAA26021; Thu, 7 Sep 2000 17:28:02 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009080028.RAA26021@pike.osd.bsdi.com> Subject: Re: microuptime() went backwards In-Reply-To: <20000907191913.A93124@virtual-voodoo.com> from Steve Ames at "Sep 7, 2000 07:19:13 pm" To: Steve Ames Date: Thu, 7 Sep 2000 17:28:02 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 Steve Ames wrote: > Just upgraded to -CURRENT as of about noon (EST) today. At reboot > I got a lot of these: > > microuptime() went backwards (1.7682417 -> 1.997434) > > I recall reading in -current earlier this week that someone was > looking for victims getting this. What further information can I provide? This is a SMPng issue on UP machines. > -Steve -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 17:40:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 2401537B423 for ; Thu, 7 Sep 2000 17:40:17 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e880e2M04876; Fri, 8 Sep 2000 10:10:02 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 10:10:02 +0930 From: Greg Lehey To: John Baldwin Cc: Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards Message-ID: <20000908101001.G83632@wantadilla.lemis.com> References: <20000907191913.A93124@virtual-voodoo.com> <200009080028.RAA26021@pike.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009080028.RAA26021@pike.osd.bsdi.com>; from jhb@pike.osd.bsdi.com on Thu, Sep 07, 2000 at 05:28:02PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 September 2000 at 17:28:02 -0700, John Baldwin wrote: > Steve Ames wrote: >> Just upgraded to -CURRENT as of about noon (EST) today. At reboot >> I got a lot of these: >> >> microuptime() went backwards (1.7682417 -> 1.997434) >> >> I recall reading in -current earlier this week that someone was >> looking for victims getting this. What further information can I provide? > > This is a SMPng issue on UP machines. Yes, but it's not the only cause. We've also seen it on pre-SMPng stuff, and Athlons seem to be particularly capable of doing it. phk is looking at it at the moment, and he has an idea what's causing it. I'd guess, however, that this *is* the SMPng problem. It's subtly different from other manifestations in that the first time typically has 7 digits after the decimal point. 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 Thu Sep 7 17:48:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8FFE737B422 for ; Thu, 7 Sep 2000 17:48:34 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id RAA26766; Thu, 7 Sep 2000 17:48:07 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009080048.RAA26766@pike.osd.bsdi.com> Subject: Re: microuptime() went backwards In-Reply-To: <20000908101001.G83632@wantadilla.lemis.com> from Greg Lehey at "Sep 8, 2000 10:10:02 am" To: Greg Lehey Date: Thu, 7 Sep 2000 17:48:06 -0700 (PDT) Cc: Steve Ames , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 Greg Lehey wrote: > On Thursday, 7 September 2000 at 17:28:02 -0700, John Baldwin wrote: > > Steve Ames wrote: > >> Just upgraded to -CURRENT as of about noon (EST) today. At reboot > >> I got a lot of these: > >> > >> microuptime() went backwards (1.7682417 -> 1.997434) > >> > >> I recall reading in -current earlier this week that someone was > >> looking for victims getting this. What further information can I provide? > > > > This is a SMPng issue on UP machines. > > Yes, but it's not the only cause. We've also seen it on pre-SMPng > stuff, and Athlons seem to be particularly capable of doing it. phk > is looking at it at the moment, and he has an idea what's causing it. > > I'd guess, however, that this *is* the SMPng problem. It's subtly > different from other manifestations in that the first time typically > has 7 digits after the decimal point. Most definitely an SMPng issue. If you take a SMP machine and compile a UP and an SMP kernel on it, the SMP kernel will boot fine, whereas the UP kernel will generate these warnings. > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 17:51: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 6DE3337B423 for ; Thu, 7 Sep 2000 17:50:54 -0700 (PDT) Received: (qmail 2174 invoked from network); 8 Sep 2000 00:50:50 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 8 Sep 2000 00:50:50 -0000 Date: Fri, 8 Sep 2000 11:50:45 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: 'interrupt-level buffer overflows' for sio device? In-Reply-To: <200009072129.PAA06098@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Sep 2000, Warner Losh wrote: > In message The Hermit Hacker writes: > : sio1: 32 more interrupt-level buffer overflows (total 32) > > >From the man page: > sio%d: interrupt-level buffer overflow. Problem in the bottom half of > the driver. > > This likely means that the bottom half of sio isn't running fast > enough to harvest the characters in the interrupt level buffers. This means that fast interrupt handlers aren't actually fast. Especially if it occurs for slow devices like mouses. Even slow interrupt handlers had about 10 times lower latency than necessary for 1200 bps serial mouses. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 17:51:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id A9BDE37B424 for ; Thu, 7 Sep 2000 17:51:18 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e880p4v10499; Fri, 8 Sep 2000 10:21:04 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 10:21:04 +0930 From: Greg Lehey To: John Baldwin Cc: Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards Message-ID: <20000908102104.H83632@wantadilla.lemis.com> References: <20000908101001.G83632@wantadilla.lemis.com> <200009080048.RAA26766@pike.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009080048.RAA26766@pike.osd.bsdi.com>; from jhb@pike.osd.bsdi.com on Thu, Sep 07, 2000 at 05:48:06PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 September 2000 at 17:48:06 -0700, John Baldwin wrote: > Greg Lehey wrote: >> On Thursday, 7 September 2000 at 17:28:02 -0700, John Baldwin wrote: >>> Steve Ames wrote: >>>> Just upgraded to -CURRENT as of about noon (EST) today. At reboot >>>> I got a lot of these: >>>> >>>> microuptime() went backwards (1.7682417 -> 1.997434) >>>> >>>> I recall reading in -current earlier this week that someone was >>>> looking for victims getting this. What further information can I provide? >>> >>> This is a SMPng issue on UP machines. >> >> Yes, but it's not the only cause. We've also seen it on pre-SMPng >> stuff, and Athlons seem to be particularly capable of doing it. phk >> is looking at it at the moment, and he has an idea what's causing it. >> >> I'd guess, however, that this *is* the SMPng problem. It's subtly >> different from other manifestations in that the first time typically >> has 7 digits after the decimal point. > > Most definitely an SMPng issue. If you take a SMP machine and compile a UP > and an SMP kernel on it, the SMP kernel will boot fine, whereas the UP kernel > will generate these warnings. The point I'm making is that we've had these problems before SMPng, and that you can't automatically assume that it's SMPng just because you get the messages. On the other hand, the 7 digits seem to be a pretty reliable signature. 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 Thu Sep 7 18:39: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CCB9037B422 for ; Thu, 7 Sep 2000 18:39:00 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA40218 for ; Thu, 7 Sep 2000 19:38:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA49048 for ; Thu, 7 Sep 2000 19:38:49 -0600 (MDT) Message-Id: <200009080138.TAA49048@harmony.village.org> To: current@freebsd.org Subject: world broken Date: Thu, 07 Sep 2000 19:38:49 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG looks like the boot loader is killing -current. I have a patch, but it just cuts all the offending references. Comments? Warner cc -nostdlib -static -Ttext 0x0 -o loader.sym /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o isapnp.o pnp.o interp_forth.o vers.o /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../../ficl/libficl.a /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../libi386/libi386.a -lstand /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In function `pxe_enable': pxe.o(.text+0x552): undefined reference to `nfs_root_node' *** Error code 1 Stop in /home/imp/FreeBSD/src/sys/boot/i386/loader. *** Error code 1 Stop in /home/imp/FreeBSD/src/sys/boot/i386. *** Error code 1 ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 19:49:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 453EC37B423 for ; Thu, 7 Sep 2000 19:49:46 -0700 (PDT) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA18108; Thu, 7 Sep 2000 22:49:31 -0400 (EDT) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id WAA27002; Thu, 7 Sep 2000 22:49:30 -0400 (EDT) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA26998; Thu, 7 Sep 2000 22:49:30 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Thu, 7 Sep 2000 22:49:30 -0400 (EDT) From: Kenneth Wayne Culver To: Greg Lehey Cc: John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: <20000908102104.H83632@wantadilla.lemis.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 > The point I'm making is that we've had these problems before SMPng, > and that you can't automatically assume that it's SMPng just because > you get the messages. On the other hand, the 7 digits seem to be a > pretty reliable signature. > I'm getting this error while starting XFree86 4.0.1 on my laptop computer, and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff that's causing it. Ken (it's a 600 MHz coppermine based celeron BTW with a mobile BX chipset) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 20: 2:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9217837B424; Thu, 7 Sep 2000 20:02:24 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA40597; Thu, 7 Sep 2000 21:02:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA50459; Thu, 7 Sep 2000 21:02:11 -0600 (MDT) Message-Id: <200009080302.VAA50459@harmony.village.org> To: Bruce Evans Subject: Re: 'interrupt-level buffer overflows' for sio device? Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Sep 2000 11:50:45 +1100." References: Date: Thu, 07 Sep 2000 21:02:10 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also, this is interrupt level overflows. We can run the fast interrupts fast enough to harvest characters from the hardware. What's not happening is that sio's bottom half isn't being run fast enough so the interrupt level buffers overflow. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 20: 6:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6487437B422; Thu, 7 Sep 2000 20:06:34 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA40617; Thu, 7 Sep 2000 21:06:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA50544; Thu, 7 Sep 2000 21:06:23 -0600 (MDT) Message-Id: <200009080306.VAA50544@harmony.village.org> To: Mike Smith Subject: Re: world broken Cc: current@freebsd.org In-reply-to: Your message of "Thu, 07 Sep 2000 20:19:10 PDT." <200009080319.UAA00442@mass.osd.bsdi.com> References: <200009080319.UAA00442@mass.osd.bsdi.com> Date: Thu, 07 Sep 2000 21:06:23 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009080319.UAA00442@mass.osd.bsdi.com> Mike Smith writes: : > : > looks like the boot loader is killing -current. I have a patch, but : > it just cuts all the offending references. : > : > Comments? : : rebuild/reinstall libstand. Sorry; should have HEADS-UPped that one. I can't reinstall libstand. I'm building current on my stable machine, which must always work so our upgrade path works. Can you fix things to remove this necessity please? Or do I misunderstand what you are saying. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 20: 9:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id B666137B422 for ; Thu, 7 Sep 2000 20:09:18 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8838dX86721; Fri, 8 Sep 2000 12:38:39 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 12:38:39 +0930 From: Greg Lehey To: Kenneth Wayne Culver Cc: John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards Message-ID: <20000908123838.U83632@wantadilla.lemis.com> References: <20000908102104.H83632@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from culverk@wam.umd.edu on Thu, Sep 07, 2000 at 10:49:30PM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote: >> The point I'm making is that we've had these problems before SMPng, >> and that you can't automatically assume that it's SMPng just because >> you get the messages. On the other hand, the 7 digits seem to be a >> pretty reliable signature. > > I'm getting this error while starting XFree86 4.0.1 on my laptop computer, > and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff > that's causing it. Right, but you're not getting the 7 digit microsecond count, right? You should contact phk. 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 Thu Sep 7 20:10: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id BB3B537B422; Thu, 7 Sep 2000 20:10:03 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e8839AD04714; Fri, 8 Sep 2000 00:09:10 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 00:09:10 -0300 (ADT) From: The Hermit Hacker To: Warner Losh Cc: Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: 'interrupt-level buffer overflows' for sio device? In-Reply-To: <200009080302.VAA50459@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Sep 2000, Warner Losh wrote: > Also, this is interrupt level overflows. We can run the fast > interrupts fast enough to harvest characters from the hardware. > What's not happening is that sio's bottom half isn't being run fast > enough so the interrupt level buffers overflow. Okay, I'm a little confused here ... from what I'm reading/following, this isn't a new problem ... or is it? If not, why has it suddenly manifested itself with the new SMP code? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 20:15:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 689CF37B424; Thu, 7 Sep 2000 20:15:10 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA40667; Thu, 7 Sep 2000 21:15:08 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA50701; Thu, 7 Sep 2000 21:14:58 -0600 (MDT) Message-Id: <200009080314.VAA50701@harmony.village.org> To: The Hermit Hacker Subject: Re: 'interrupt-level buffer overflows' for sio device? Cc: Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Sep 2000 00:09:10 -0300." References: Date: Thu, 07 Sep 2000 21:14:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message The Hermit Hacker writes: : Okay, I'm a little confused here ... from what I'm reading/following, this : isn't a new problem ... or is it? If not, why has it suddenly manifested : itself with the new SMP code? It seems to be new with the SMP code. At least that's what my reading of the original message is. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 20:29:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id DEE8437B424; Thu, 7 Sep 2000 20:29:28 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e883SrK05070; Fri, 8 Sep 2000 00:28:53 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 00:28:53 -0300 (ADT) From: The Hermit Hacker To: Warner Losh Cc: Bruce Evans , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: 'interrupt-level buffer overflows' for sio device? In-Reply-To: <200009080314.VAA50701@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Sep 2000, Warner Losh wrote: > In message The Hermit Hacker writes: > : Okay, I'm a little confused here ... from what I'm reading/following, this > : isn't a new problem ... or is it? If not, why has it suddenly manifested > : itself with the new SMP code? > > It seems to be new with the SMP code. At least that's what my reading > of the original message is. That was what I thought when I wrote the original message ... it just scares me sometimes how quickly things get acknowledged as a problem in the Open Source community, especially after dealign with tech support at Sun and getting the complete run around ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 21: 6:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 0AFB137B422 for ; Thu, 7 Sep 2000 21:06:36 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e88467K07568 for ; Fri, 8 Sep 2000 01:06:07 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 01:06:07 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: docs on how to upgraded boot loader ... 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 How do I upgrade it 'with the new kernel', as the UPDATING file suggests? I've looked at the man pages for loader, and it doesn't suggest anything ... help? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 21:17:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 37F2837B423 for ; Thu, 7 Sep 2000 21:17:49 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id VAA32639; Thu, 7 Sep 2000 21:17:14 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009080417.VAA32639@pike.osd.bsdi.com> Subject: Re: 'interrupt-level buffer overflows' for sio device? In-Reply-To: from Bruce Evans at "Sep 8, 2000 11:50:45 am" To: Bruce Evans Date: Thu, 7 Sep 2000 21:17:14 -0700 (PDT) Cc: Warner Losh , The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORGG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Thu, 7 Sep 2000, Warner Losh wrote: > > > In message The Hermit Hacker writes: > > : sio1: 32 more interrupt-level buffer overflows (total 32) > > > > >From the man page: > > sio%d: interrupt-level buffer overflow. Problem in the bottom half of > > the driver. > > > > This likely means that the bottom half of sio isn't running fast > > enough to harvest the characters in the interrupt level buffers. > > This means that fast interrupt handlers aren't actually fast. Especially > if it occurs for slow devices like mouses. Even slow interrupt handlers > had about 10 times lower latency than necessary for 1200 bps serial mouses. > > Bruce Well unfortunately this doesn't make sense since the sio interrupt _is_ still fast, and thus is not run as a thread as other interrupts, but is run just like old fast interrupts were. However, there is an issue with sio right now in that it's not getting any input (actually, on my test machines, I can't get the stupid hardware to set the actual DCD bit, so I can't even open the devices *sigh*). My guess then is that we aren't scheduling the soft interrupt to harvest the data in the top half from the bottom half. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 21:18:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 2894F37B423 for ; Thu, 7 Sep 2000 21:18:22 -0700 (PDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA27815; Fri, 8 Sep 2000 00:18:08 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA28523; Fri, 8 Sep 2000 00:18:07 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA28519; Fri, 8 Sep 2000 00:18:07 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Fri, 8 Sep 2000 00:18:07 -0400 (EDT) From: Kenneth Wayne Culver To: Greg Lehey Cc: John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: <20000908123838.U83632@wantadilla.lemis.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 Well, here is one of the messeges: Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121) this is bad.. right ? :-) ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 8 Sep 2000, Greg Lehey wrote: > On Thursday, 7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote: > >> The point I'm making is that we've had these problems before SMPng, > >> and that you can't automatically assume that it's SMPng just because > >> you get the messages. On the other hand, the 7 digits seem to be a > >> pretty reliable signature. > > > > I'm getting this error while starting XFree86 4.0.1 on my laptop computer, > > and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff > > that's causing it. > > Right, but you're not getting the 7 digit microsecond count, right? > You should contact phk. > > 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 Thu Sep 7 21:21:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0C2FA37B422 for ; Thu, 7 Sep 2000 21:21:31 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA40903; Thu, 7 Sep 2000 22:21:19 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA51278; Thu, 7 Sep 2000 22:21:09 -0600 (MDT) Message-Id: <200009080421.WAA51278@harmony.village.org> To: John Baldwin Subject: Re: 'interrupt-level buffer overflows' for sio device? Cc: Bruce Evans , The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORGG In-reply-to: Your message of "Thu, 07 Sep 2000 21:17:14 PDT." <200009080417.VAA32639@pike.osd.bsdi.com> References: <200009080417.VAA32639@pike.osd.bsdi.com> Date: Thu, 07 Sep 2000 22:21:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009080417.VAA32639@pike.osd.bsdi.com> John Baldwin writes: : My guess then is that we aren't scheduling the : soft interrupt to harvest the data in the top half from the bottom half. That's what I think as well. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 21:24:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 4297137B424 for ; Thu, 7 Sep 2000 21:24:51 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e884OXZ31155; Fri, 8 Sep 2000 13:54:33 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 13:54:33 +0930 From: Greg Lehey To: Kenneth Wayne Culver Cc: John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards Message-ID: <20000908135433.V83632@wantadilla.lemis.com> References: <20000908123838.U83632@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from culverk@wam.umd.edu on Fri, Sep 08, 2000 at 12:18:07AM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 8 September 2000 at 0:18:07 -0400, Kenneth Wayne Culver wrote: > On Fri, 8 Sep 2000, Greg Lehey wrote: > >> On Thursday, 7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote: >>>> The point I'm making is that we've had these problems before SMPng, >>>> and that you can't automatically assume that it's SMPng just because >>>> you get the messages. On the other hand, the 7 digits seem to be a >>>> pretty reliable signature. >>> >>> I'm getting this error while starting XFree86 4.0.1 on my laptop computer, >>> and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff >>> that's causing it. >> >> Right, but you're not getting the 7 digit microsecond count, right? >> You should contact phk. > > Well, here is one of the messeges: > > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121) > > this is bad.. right ? :-) Well, at any rate it looks very funny. If this is a laptop, try building a kernel without apm and see if that helps. 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 Thu Sep 7 21:35:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B46F137B422 for ; Thu, 7 Sep 2000 21:35:21 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA40958; Thu, 7 Sep 2000 22:35:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA52280; Thu, 7 Sep 2000 22:35:08 -0600 (MDT) Message-Id: <200009080435.WAA52280@harmony.village.org> To: The Hermit Hacker Subject: Re: docs on how to upgraded boot loader ... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Sep 2000 01:06:07 -0300." References: Date: Thu, 07 Sep 2000 22:35:08 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message The Hermit Hacker writes: : How do I upgrade it 'with the new kernel', as the UPDATING file : suggests? I've looked at the man pages for loader, and it doesn't suggest : anything ... help? cd /usr/src make buildworld make buildkernel make installkernel cd sys make install cd .. Optionally reboot in single user mode cd /usr/src make installworld Or if you like taking chances, and with the fixes I just committed: # assume that /usr/obj exists from prior run cd /usr/src/lib/libstand make depend && make all # add install here w/o my fixes cd ../../sys make depend && make all install cd i386/conf config FOO cd ../../compile/FOO make depend && make all install But we've had enough changes in sys recently that you'll need new libkvm utilities, so you might as well do the first series of commands. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 7 22:36:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1F16537B422; Thu, 7 Sep 2000 22:36:25 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e885aKA67706; Fri, 8 Sep 2000 15:06:20 +0930 (CST) (envelope-from grog) Date: Fri, 8 Sep 2000 15:06:20 +0930 From: Greg Lehey To: Mike Smith Cc: Kenneth Wayne Culver , John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards Message-ID: <20000908150620.Y83632@wantadilla.lemis.com> References: <20000908135433.V83632@wantadilla.lemis.com> <200009080543.WAA01815@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009080543.WAA01815@mass.osd.bsdi.com>; from msmith@FreeBSD.ORG on Thu, Sep 07, 2000 at 10:43:11PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 7 September 2000 at 22:43:11 -0700, Mike Smith wrote: >>> Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121)y >>> >>> this is bad.. right ? :-) >> >> Well, at any rate it looks very funny. If this is a laptop, try >> building a kernel without apm and see if that helps. > > It only helps "hide" the problem. There's either *extremely* bogus data > coming in, or an arithmetic or sequencing error that's allowing a corrupt > timecounter to be seen. Correct. As I mentioned earlier in the thread, phk has an idea what the problem is, and he's asked for people with it to contact him. 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 Thu Sep 7 23:35:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D5DEB37B422 for ; Thu, 7 Sep 2000 23:35:40 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA41280 for ; Fri, 8 Sep 2000 00:35:39 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.0/8.8.3) with ESMTP id e886aCG18672 for ; Fri, 8 Sep 2000 00:36:12 -0600 (MDT) Message-Id: <200009080636.e886aCG18672@billy-club.village.org> To: current@freebsd.org Subject: SMPNG kernel on UP Date: Fri, 08 Sep 2000 00:36:12 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed a few things wrong with the SMPNG code. These are mostly impressions. As I learn more about them, I'll file more formal bug reports. This is an FYI to fellow travelers along the path. 1) You can't have I386_CPU at all. This is likely bad in the long run, but OK for now. 2) APM is now broken. It worked after the ACPI integration, but after the SMPNG stuff neither apm -z nor the BIOS keys seems to suspend. 3) Linux emuation is panics the machine in linux_open on a normal boot. 4) Need to rebuild all libkvm things, yet again, but make world fixed that :-) 5) USB ethernet is more likely to hang the machine than it was before. This hand is transient, however. I have seen one crash removing the USB adapter that I didn't used to see, but wasn't in a position to look at it in detail. 6) Switching virtual termintals from the X server to the console is busted. 7) SSH to a machine on my local network is dog slow sometimes. I can type about one line or two lines ahead of it in email when it happens. It feels like a network pause of about 1-2 seconds. Local windows behave well during these episodes. 8) The machine seems to pause more often than it used to for reasons totally unknown at this time. These pauses last for several seconds and then things are good again. This might be related to #7, but the total machine pauses happen w/o any network connections. Next time this happens, I'll hit capslock to see if the interrupts are blocked or not. But other than that, the system is usable. I've been able to build world on my laptop running this afternoon's tree. I've also been able to do some development with it as well, both in X and on the console. Things are much more stable than I had feared, but less stable than I like them. Since I knew what I was getting into, it isn't a huge deal, but I wanted to give feedback to people about this. Now is a bad time to be thinking about cuting a production machine/snapshot from the -current branch. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 0: 2:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E679337B42C for ; Fri, 8 Sep 2000 00:02:08 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id AAA36477; Fri, 8 Sep 2000 00:01:54 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009080701.AAA36477@pike.osd.bsdi.com> Subject: Re: SMPNG kernel on UP In-Reply-To: <200009080636.e886aCG18672@billy-club.village.org> from Warner Losh at "Sep 8, 2000 00:36:12 am" To: Warner Losh Date: Fri, 8 Sep 2000 00:01:54 -0700 (PDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 Warner Losh wrote: > > I've noticed a few things wrong with the SMPNG code. These are mostly > impressions. As I learn more about them, I'll file more formal bug > reports. This is an FYI to fellow travelers along the path. > 1) You can't have I386_CPU at all. This is likely bad in > the long run, but OK for now. Err, this should be fixed now. Do you have the latest i386/include/smp.h? > 2) APM is now broken. It worked after the ACPI integration, > but after the SMPNG stuff neither apm -z nor the BIOS keys > seems to suspend. Hmm. > 3) Linux emuation is panics the machine in linux_open on > a normal boot. Hate to ask, but are you sure it is loading the right module? With the kernel.ko change, modules don't live in the same place anymore, and I haven't seen any commits to kldload, /etc/rc, or linux.sh that takes this into account. > 5) USB ethernet is more likely to hang the machine than it was > before. This hand is transient, however. I have seen > one crash removing the USB adapter that I didn't used to > see, but wasn't in a position to look at it in detail. Hmm, ok. > 7) SSH to a machine on my local network is dog slow > sometimes. I can type about one line or two lines ahead of > it in email when it happens. It feels like a network pause > of about 1-2 seconds. Local windows behave well during > these episodes. Hmm, haven't seen this. > 8) The machine seems to pause more often than it used to for > reasons totally unknown at this time. These pauses last > for several seconds and then things are good again. This > might be related to #7, but the total machine pauses happen > w/o any network connections. Next time this happens, I'll > hit capslock to see if the interrupts are blocked or not. Haven't seen this either. :( Here are some of the known issues that are gotchas: 1) sio is broken. It doesn't receieve any data, although Greg has just fixed this and should be committing a fix shortly. 2) There seem to be some problems with possibly the ahc controller (haven't tried ata yet) where after several hours of heavy load (-j 256 buildworlds and the like) the disk driver will hang. The machine will run fine, top still runs over ssh, for example. However, any process that accesses the disk hangs since it blocks forever waiting on the disk, thus rendering the machine useless. Note that this only happens with SMP. UP seems to be very stable. I haven't had a UP kernel panic or freeze in weeks. 3) The alpha is not entirely stable. I'm working on adding interrupt threads to the alpha right now, which will hopefully help. I think there are some areas in the kernel that are assuming we have the type of locking we have on x86 with ithreads, and am hoping that alpha ithreads will fix those assumptions. Also, there are many changes in dfr's alpha patches that I at least do not understand, and it possibly some of them are incomplete/bogus. > Now is a bad time to be thinking about cuting a production > machine/snapshot from the -current branch. Are there good times for this? ;-) > Warner -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 0: 5:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 18E9D37B422; Fri, 8 Sep 2000 00:05:41 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA25388; Fri, 8 Sep 2000 18:05:22 +1100 Date: Fri, 8 Sep 2000 18:05:18 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: 'interrupt-level buffer overflows' for sio device? In-Reply-To: <200009080302.VAA50459@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Sep 2000, Warner Losh wrote: > Also, this is interrupt level overflows. We can run the fast > interrupts fast enough to harvest characters from the hardware. > What's not happening is that sio's bottom half isn't being run fast > enough so the interrupt level buffers overflow. Not surprising, since sio's bottom half scheduler (schedsofttty()) is now null. The top half apparently only gets scheduled if there is an output interrupt, a fake output interrupt (flags 0x8) a modem status change, or urgent data. Urgent data probably keeps it going for slip and pppd, but there is no urgent data in the termios line discipline. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 3:25:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 57A8837B422 for ; Fri, 8 Sep 2000 03:25:25 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13XLLV-00028b-00; Fri, 08 Sep 2000 12:25:21 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id MAA29638; Fri, 8 Sep 2000 12:25:20 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 29413; Fri Sep 8 12:24:06 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13XLKH-00040h-00; Fri, 08 Sep 2000 12:24:05 +0200 From: Sheldon Hearn To: Warner Losh Cc: current@freebsd.org Subject: Re: SMPNG kernel on UP In-reply-to: Your message of "Fri, 08 Sep 2000 00:36:12 CST." <200009080636.e886aCG18672@billy-club.village.org> Date: Fri, 08 Sep 2000 12:24:05 +0200 Message-ID: <15418.968408645@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 08 Sep 2000 00:36:12 CST, Warner Losh wrote: > 6) Switching virtual termintals from the X server to the > console is busted. This does not appear to be a problem here, with SMPng and XFree86-3.3.6. > 7) SSH to a machine on my local network is dog slow > sometimes. I can type about one line or two lines ahead of > it in email when it happens. It feels like a network pause > of about 1-2 seconds. Local windows behave well during > these episodes. I also haven't noticed this. Have you managed to determine that it's SSH and not your X11 terminal emulator? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 4:14:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from venus.cs.put.poznan.pl (vega.cs.put.poznan.pl [150.254.30.30]) by hub.freebsd.org (Postfix) with ESMTP id 55AC337B423 for ; Fri, 8 Sep 2000 04:14:07 -0700 (PDT) Received: from cs.put.poznan.pl (dcs-430x-pw.cs.put.poznan.pl [150.254.31.188]) by venus.cs.put.poznan.pl (8.10.2/8.10.2) with ESMTP id e88B85U23752 for ; Fri, 8 Sep 2000 13:08:05 +0200 (CEST) Message-ID: <39B8C973.98F4F51E@cs.put.poznan.pl> Date: Fri, 08 Sep 2000 13:11:47 +0200 From: Piotr =?iso-8859-1?Q?Wo=9Fniak?= X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current Subject: netscape Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have installed netscape4-navigator and I can't launch its. I've got following message: ld.so failed: Can't find shared library "libXt.so.6.0" What can I do? Piotr Wozniak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 4:34:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 4644937B423 for ; Fri, 8 Sep 2000 04:34:55 -0700 (PDT) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id HAA12473; Fri, 8 Sep 2000 07:34:38 -0400 (EDT) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id HAA10869; Fri, 8 Sep 2000 07:34:38 -0400 (EDT) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id HAA10864; Fri, 8 Sep 2000 07:34:37 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Fri, 8 Sep 2000 07:34:37 -0400 (EDT) From: Kenneth Wayne Culver To: Greg Lehey Cc: John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: <20000908135433.V83632@wantadilla.lemis.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 If I build the kernel without apm, then there is no clock because the statclock is broken on this computer. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 8 Sep 2000, Greg Lehey wrote: > On Friday, 8 September 2000 at 0:18:07 -0400, Kenneth Wayne Culver wrote: > > On Fri, 8 Sep 2000, Greg Lehey wrote: > > > >> On Thursday, 7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote: > >>>> The point I'm making is that we've had these problems before SMPng, > >>>> and that you can't automatically assume that it's SMPng just because > >>>> you get the messages. On the other hand, the 7 digits seem to be a > >>>> pretty reliable signature. > >>> > >>> I'm getting this error while starting XFree86 4.0.1 on my laptop computer, > >>> and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff > >>> that's causing it. > >> > >> Right, but you're not getting the 7 digit microsecond count, right? > >> You should contact phk. > > > > Well, here is one of the messeges: > > > > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121) > > > > this is bad.. right ? :-) > > Well, at any rate it looks very funny. If this is a laptop, try > building a kernel without apm and see if that helps. > > 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 Sep 8 4:36:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id A507437B424 for ; Fri, 8 Sep 2000 04:36:43 -0700 (PDT) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id VAA97472; Fri, 8 Sep 2000 21:06:40 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.11.0/8.9.3) id e88Baau80511; Fri, 8 Sep 2000 21:06:36 +0930 (CST) (envelope-from darius) Message-Id: <200009081136.e88Baau80511@guppy.dons.net.au> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <39B8C973.98F4F51E@cs.put.poznan.pl> Date: Fri, 08 Sep 2000 21:06:35 +0930 (CST) From: "Daniel O'Connor" To: Piotr =?iso-8859-1?Q?Wo=9Fniak?= Subject: RE: netscape Cc: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Sep-00 Piotr WoŸniak wrote: > Hi, > I have installed netscape4-navigator and I can't launch its. > I've got following message: > > ld.so failed: Can't find shared library "libXt.so.6.0" You are using the FreeBSD a.out version of Netscape. For this to work you need the 2.2/3.x compat distribution installed. You can install this with sysinstall. Another option is to use the Linux version (ports/www/linux-netscape47-communicator) which has the added advantage of having more plugins (eg flash) available. --- 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 Fri Sep 8 4:39:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 97CF337B422 for ; Fri, 8 Sep 2000 04:39:47 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13XMVU-00038y-00 for current@freebsd.org; Fri, 08 Sep 2000 13:39:44 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA08911 for ; Fri, 8 Sep 2000 13:39:44 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 8672; Fri Sep 8 13:38:33 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13XMUK-00007R-00 for current@FreeBSD.org; Fri, 08 Sep 2000 13:38:32 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Re: HEADS UP: linux module breaks current In-reply-to: Your message of "Thu, 07 Sep 2000 16:04:11 +0200." <684.968335451@axl.fw.uunet.co.za> Date: Fri, 08 Sep 2000 13:38:32 +0200 Message-ID: <460.968413112@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 07 Sep 2000 16:04:11 +0200, Sheldon Hearn wrote: > Just a warning to anyone wanting to try out SMPng -- make sure that you > hdon't have ``linux_enable="YES"'' in /etc/rc.conf. > > I got a kernel trap when /etc/rc tried to load the linux module. I > haven't had time to get a panic and backtrace to Marcel, but I thought > I'd send this warning for now. I'd like to feed back that this was pilot error. Although I had up-to-date modules in /boot/kernel, I still had stale modules in /modules. The bottom line? Be sure to remove your /modules when you upgrade. If you want to keep your old modules around to support an old kernel, do this: if [ ! -d /boot/kernel.old ]; then mv /modules /boot/kernel.old chflags noschg /kernel mv /kernel /boot/kernel.old/kernel.ko chflags noschg /boot/kernel.old/kernel.ko fi The linuxulator is working just fine for me under the new SMPng. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 4:41:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 0304B37B631 for ; Fri, 8 Sep 2000 04:41:52 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13XMXT-0003Aq-00; Fri, 08 Sep 2000 13:41:47 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA09255; Fri, 8 Sep 2000 13:41:45 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 9219; Fri Sep 8 13:41:30 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13XMXB-00008E-00; Fri, 08 Sep 2000 13:41:29 +0200 From: Sheldon Hearn To: John Baldwin Cc: Warner Losh , current@freebsd.org Subject: Re: SMPNG kernel on UP In-reply-to: Your message of "Fri, 08 Sep 2000 00:01:54 MST." <200009080701.AAA36477@pike.osd.bsdi.com> Date: Fri, 08 Sep 2000 13:41:29 +0200 Message-ID: <509.968413289@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 08 Sep 2000 00:01:54 MST, John Baldwin wrote: > > 3) Linux emuation is panics the machine in linux_open on > > a normal boot. > > Hate to ask, but are you sure it is loading the right module? With > the kernel.ko change, modules don't live in the same place anymore, > and I haven't seen any commits to kldload, /etc/rc, or linux.sh that > takes this into account. I got annoyed when I read your question, so I set out to reproduce the fatal trap. Of course, since I got the trap, I've deleted my /modules directory. So you're aboslutely right. :-) See my reply to my own message with the subject "HEADS UP: linux module breaks current" to this list. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 4:46:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C457537B42C; Fri, 8 Sep 2000 04:46:44 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA90969; Fri, 8 Sep 2000 13:48:41 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009081148.NAA90969@freebsd.dk> Subject: New ATA tagged queuing patch available To: current@freebsd.org, hackers@freebsd.org Date: Fri, 8 Sep 2000 13:48:40 +0200 (CEST) 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 From the README: ATA-tagged-queueing-diff-0908: Add support for ATA channels with both a master and a slave, even combos where only on of them supports tagged queuing should work now. Also only switch on tagged queuing on IBM DPTA & DTLA series drives, the older DJNA has firmware problems. I am working on a SW solution to that, but for now only enable tagged queuing on drives that is known to work. Get it from http://freebsd.dk, and let me know your results If I dont get any serious problem reports I'll commit this shortly, making FreeBSD the first OS that has tagged Queuing support for ATA drives :) -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 Sep 8 4:50:30 2000 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 532E437B422; Fri, 8 Sep 2000 04:50:24 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e88ANvm31966; Fri, 8 Sep 2000 11:23:57 +0100 (BST) (envelope-from nik) Date: Fri, 8 Sep 2000 11:23:56 +0100 From: Nik Clayton To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, freebsd-doc@freebsd.org Subject: Re: CFR: acpi userland manpages Message-ID: <20000908112356.B31852@canyon.nothing-going-on.org> References: <20000901000931V.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000901000931V.iwasaki@jp.FreeBSD.org>; from iwasaki@jp.FreeBSD.org on Fri, Sep 01, 2000 at 12:09:31AM +0900 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 01, 2000 at 12:09:31AM +0900, Mitsuru IWASAKI wrote: > Hi, I've just imported acpi userland tools and writing manpages for > them with contributers in Japan. > Please review them and send any comments (or diffs) for me > (iwasaki@jp.FreeBSD.org) in terms of English/roff or whatever. > > The draft version of manpages are available at > http://people.FreeBSD.org/~iwasaki/acpi/acpidump.8 > http://people.FreeBSD.org/~iwasaki/acpi/amldb.8 I've just found the time to give them a quick once over, and I'd have no problem with them going in as they are. There are some grammar changes, and possibly terminology changes that might be appropriate, but I haven't got the time to enumerate them all at the moment, and I'm sure the wider community can make suggestions as time goes on. Sheldon can probably render an opinion on their usage of the macros. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 5:12:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 15D7437B423 for ; Fri, 8 Sep 2000 05:12:44 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e88CCWv19317; Fri, 8 Sep 2000 08:12:33 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id IAA27887; Fri, 8 Sep 2000 08:12:31 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id IAA59526; Fri, 8 Sep 2000 08:12:30 -0400 (EDT) Date: Fri, 8 Sep 2000 08:12:30 -0400 (EDT) From: Thomas David Rivers Message-Id: <200009081212.IAA59526@lakes.dignus.com> To: freebsd-current@FreeBSD.ORG, piotr.wozniak@cs.put.poznan.pl Subject: Re: netscape In-Reply-To: <39B8C973.98F4F51E@cs.put.poznan.pl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi, > I have installed netscape4-navigator and I can't launch its. > I've got following message: > > ld.so failed: Can't find shared library "libXt.so.6.0" > > What can I do? > Piotr Wozniak You need to install the XFree86 a.out library package. It's in the packages directory from the 4.1-RELEASE.. I bet there's something there for -current as well. - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 5:14: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 11BEF37B424 for ; Fri, 8 Sep 2000 05:14:06 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e88CDWo44170; Fri, 8 Sep 2000 09:13:34 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 09:13:32 -0300 (ADT) From: The Hermit Hacker To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: docs on how to upgraded boot loader ... In-Reply-To: <200009080435.WAA52280@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah, okay, for some reason I was looking at the 'disklabel -B' stuff, but that never worked :( I've gotten into the habit of doing the whole 'buildkernel/buildworld/etc' procedure, and just hadn['t gotten to the point doing the 'installworld' :( thanks ... On Thu, 7 Sep 2000, Warner Losh wrote: > In message The Hermit Hacker writes: > : How do I upgrade it 'with the new kernel', as the UPDATING file > : suggests? I've looked at the man pages for loader, and it doesn't suggest > : anything ... help? > > cd /usr/src > make buildworld > make buildkernel > make installkernel > cd sys > make install > cd .. > Optionally reboot in single user mode > cd /usr/src > make installworld > > Or if you like taking chances, and with the fixes I just committed: > # assume that /usr/obj exists from prior run > cd /usr/src/lib/libstand > make depend && make all # add install here w/o my fixes > cd ../../sys > make depend && make all install > cd i386/conf > config FOO > cd ../../compile/FOO > make depend && make all install > > > But we've had enough changes in sys recently that you'll need new > libkvm utilities, so you might as well do the first series of > commands. > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 6:11:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta01.mail.mel.aone.net.au (mta01.mail.au.uu.net [203.2.192.81]) by hub.freebsd.org (Postfix) with ESMTP id 617DD37B422 for ; Fri, 8 Sep 2000 06:11:12 -0700 (PDT) Received: from camtech.net.au ([203.55.245.95]) by mta01.mail.mel.aone.net.au with ESMTP id <20000908131109.YBDB350.mta01.mail.mel.aone.net.au@camtech.net.au> for ; Fri, 8 Sep 2000 23:11:09 +1000 Message-ID: <39B8E5C3.CE61B6B9@camtech.net.au> Date: Fri, 08 Sep 2000 22:42:35 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Oddities with the new binutils Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Repost of old mail now that I've made my ISP register their mail relays (which took three months for them to understand!). I know this is ancient but being in the archives may help someone. It was a kernel problem. I made a new kernel from sources of about 8 hours ago and the problem has dissappeared from my home machine (have to wait until after the long weekend [- in Oz] to test the work machine). It seems that something in the May 29th kernel was causing problems for X. Matthew Thyer wrote: > > It may not be FP itself. > > In fact I have seen some other strange graphic corruption at home > when running xplanet in the background and xanim. When the planet > turns, the top 20 or so rows of the root window get corrupted with > some of the image of the currently playing animation in xanim. > > I haven't mentioned this yet because I've only been running xplanet > since post-binutils so I cant compare it with previous behaviour. > > It would appear to be an Xserver problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 6:22:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta03.mail.mel.aone.net.au (mta03.mail.au.uu.net [203.2.192.83]) by hub.freebsd.org (Postfix) with ESMTP id 457B237B422 for ; Fri, 8 Sep 2000 06:22:27 -0700 (PDT) Received: from camtech.net.au ([203.55.245.95]) by mta03.mail.mel.aone.net.au with ESMTP id <20000908132221.YTGQ359.mta03.mail.mel.aone.net.au@camtech.net.au> for ; Fri, 8 Sep 2000 23:22:21 +1000 Message-ID: <39B8E865.B77012B@camtech.net.au> Date: Fri, 08 Sep 2000 22:53:49 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: /usr/local/etc/rc.d and /etc/rc.d Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I know this was discussed a couple of months ago but since nothings been committed yet I throw in my 3 month old email that I haven't been able to send due to my stupid ISP with unregistered mail relays] Please read as I have done a fair bit of thinking on this matter as the sysadmin of many commercial UNIX systems (SunOS, Solaris, IRIX, HP-UX, True64) plus FreeBSD and Linux (we'll just call it UNIX even though that's debatable). [NOTE I'm 750 behind on my cvs-all mail so dont hassle me as I haven't read this thread yet but feel the need to respond before we end up with some wierd non backward compatible system that's totally different from common UNIX systems]. I would like to see startup and shutdown scripts exist in a single directory ("/usr/local/etc/rc.d/" for ports and eventually "/etc/rc.d" when the system migrates to the same scheme). The startup and shutdown functionality would be in the same script and the scripts should be named starting with a capital 'S' for startup and a capital 'K' for shutdown (I'm also keen on the HPUX startmsg and stopmsg one liners). There's no need for the seperate SYSV init.d directory as scripts will be off if they dont start with the right naming convention. As for runlevels... thats not BSD and I dont know any SYSV admin who uses them (I dont count the RedHat hack to turn on X). The scripts will be differentiated from existing scripts (the old system) as the new system will only act on scripts that have a digit in the second character of their name (there could be a backward compatability process to act on all the others afterwards which would be disabled by default... presumably "disabled.S99rc.compat" or some such name). Stop scripts will be a symbolic link to their startup script counterpart (and would simply not be executed if the K* file doesn't exist). Symbolic links make it clear they are the same script. Scripts would be executed in alphabetical order (after the S or K) so the sysadmin has control over the execution order which is important. Scripts would source common functions from a system file so we have control over future changes in functionality/reporting. This would also make the template script very simple. Eventually I would like the system to migrate to such a scheme but maintain the backward compatibility scripts /etc/netstart which could be implemented either by simply 'knowing' which rc scripts do network functionality or by reserving a range of numbers for network startup <--- HACK! I'd really like the system to allow stuff like "/etc/rc.d/S84named reread" (or "restart", "reload" whatever is acceptable). I'd also really like at least named and perl to be removed from the base system but that's another thread. One of the big turn offs to FreeBSD in the System V world is: "What!, why do I need to know which signal to send blah to reload it ?". The backward compatibilty hack script in "/usr/local/etc/rc.d/" would ignore files starting with "README" and "disabled" (and maybe other typical disabling naming methods). This is not too much of a hack as the backward compatibility script would go away in a release or two. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 6:34:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 7198037B423 for ; Fri, 8 Sep 2000 06:34:33 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13XOIQ-000F9S-00; Fri, 08 Sep 2000 15:34:22 +0200 Date: Fri, 8 Sep 2000 15:34:22 +0200 From: Neil Blakey-Milner To: Matthew Thyer Cc: current@freebsd.org Subject: Re: /usr/local/etc/rc.d and /etc/rc.d Message-ID: <20000908153421.A58134@mithrandr.moria.org> References: <39B8E865.B77012B@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39B8E865.B77012B@camtech.net.au>; from thyerm@camtech.net.au on Fri, Sep 08, 2000 at 10:53:49PM +0930 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2000-09-08 (22:53), Matthew Thyer wrote: > I would like to see startup and shutdown scripts exist in a single > directory ("/usr/local/etc/rc.d/" for ports and eventually > "/etc/rc.d" when the system migrates to the same scheme). I don't think we should move away from the 'base' system and 'extra' stuff differentiation. Any script that can support /etc/rc.d can probably support /usr/local/etc/rc.d, /usr/X11R6/etc/rc.d, and others based on a variable in /etc/rc.conf. > The startup and shutdown functionality would be in the same script > and the scripts should be named starting with a capital 'S' for > startup and a capital 'K' for shutdown (I'm also keen on the HPUX > startmsg and stopmsg one liners). Why not just use chmod +x or chmod -x, like we do already? This means not having to rename things. > The scripts will be differentiated from existing scripts (the old > system) as the new system will only act on scripts that have a digit > in the second character of their name (there could be a backward > compatability process to act on all the others afterwards which > would be disabled by default... presumably "disabled.S99rc.compat" > or some such name). I prefer chmod +x and chmod -x. > Stop scripts will be a symbolic link to their startup script > counterpart (and would simply not be executed if the K* file doesn't > exist). Symbolic links make it clear they are the same script. I don't see the point. > Scripts would be executed in alphabetical order (after the S or K) > so the sysadmin has control over the execution order which is > important. I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at http://people.FreeBSD.org/~eivind/newrc.tar.gz) > Scripts would source common functions from a system file so we have > control over future changes in functionality/reporting. This would > also make the template script very simple. I imagine that's the way to do it. > Eventually I would like the system to migrate to such a scheme but > maintain the backward compatibility scripts /etc/netstart which > could be implemented either by simply 'knowing' which rc scripts > do network functionality or by reserving a range of numbers for > network startup <--- HACK! This is why you want dependencies. > I'd really like the system to allow stuff like "/etc/rc.d/S84named > reread" (or "restart", "reload" whatever is acceptable). That's a natural extension to the current method, yes. We should be sure to fail on something we don't understand, and not (like we may do now) run the default start script. > I'd also really like at least named and perl to be removed from the > base system but that's another thread. I'll comment when you bring it up. Warning: perl is necessary for kernel builds. > One of the big turn offs to FreeBSD in the System V world is: > "What!, why do I need to know which signal to send blah to reload > it ?". I agree. We need a simpler system. Simple, and obvious. None of this complex symlink stuff. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 6:36:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84]) by hub.freebsd.org (Postfix) with ESMTP id E71A837B42C for ; Fri, 8 Sep 2000 06:36:22 -0700 (PDT) Received: from camtech.net.au ([203.55.245.95]) by mta04.mail.mel.aone.net.au with ESMTP id <20000908133618.VEMA374.mta04.mail.mel.aone.net.au@camtech.net.au> for ; Fri, 8 Sep 2000 23:36:18 +1000 Message-ID: <39B8EB92.DF0407A8@camtech.net.au> Date: Fri, 08 Sep 2000 23:07:22 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Please consider some cosmetic changes in boot messages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone else noticed how FreeBSD is inconsistent with the use of words like "Doing", "setting" and "starting" in the boot messages ? For instance, I think the following fragment of my boot should change from: Additional routing options: tcp extensions=NO TCP keepalive=YES. routing daemons:. Mounting NFS file systems. additional daemons: syslogd. checking for core dump...savecore: no core dump Doing additional network setup: portmap. Starting final network daemons: mountd nfsd rpc.statd nfsiod NFS access cache ti me=2. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout starting standard daemons: inetd cron usbd. Initial rc.i386 initialization: apm apmd. rc.i386 configuring syscons: font8x16 font8x14 font8x8 blank_time allscreens. additional ABI support:. Local package initialization: fkeys SETI@home xfstt. Additional TCP options:. To: (I've put * against the changed lines) Additional routing options: tcp extensions=NO TCP keepalive=YES. routing daemons:. Mounting NFS file systems. additional daemons: syslogd. checking for core dump...savecore: no core dump * additional network setup: portmap. * final network daemons: mountd nfsd rpc.statd nfsiod NFS access cache time=2. * ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib * a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout * standard daemons: inetd cron usbd. * rc.i386 initialization: apm apmd. rc.i386 configuring syscons: font8x16 font8x14 font8x8 blank_time allscreens. additional ABI support:. Local package initialization: fkeys SETI@home xfstt. Additional TCP options:. And finally, for filesystems with >= 10^6 blocks free, the fsck -p output (second line) hits exactly 80 chars which makes syscons leave a blank line before the next line of output. Call me pedantic but could we change the word "fragmentation" to "fragmented" to give room for many more blocks in the filesystem before wrapping. I'm sure the answer is no due to histerical raisins but its worth a try ;) /dev/ad0s2e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s2e: clean, 5929804 free (2252 frags, 740944 blocks, 0.0% fragmentation) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 6:47:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84]) by hub.freebsd.org (Postfix) with ESMTP id 4C1B137B422 for ; Fri, 8 Sep 2000 06:47:17 -0700 (PDT) Received: from camtech.net.au ([203.55.245.95]) by mta04.mail.mel.aone.net.au with ESMTP id <20000908134715.VGOX374.mta04.mail.mel.aone.net.au@camtech.net.au> for ; Fri, 8 Sep 2000 23:47:15 +1000 Message-ID: <39B8EE3A.A6B77351@camtech.net.au> Date: Fri, 08 Sep 2000 23:18:42 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: /usr/local/etc/rc.d and /etc/rc.d References: <39B8E865.B77012B@camtech.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Replying to my own message. In summary, the main things the scheme I describe gives us are: - control over startup/shutdown order with the numbers - accomodates older scripts (by just not having the K script linked to the S, script things wont be started again at shutdown time). - enough similarity to SYSV to not confuse - ability to easily disable scripts (rename to not start with S[0-9] or K[0-9]) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 6:56:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 8300A37B423 for ; Fri, 8 Sep 2000 06:56:08 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 90A57E881 for ; Fri, 8 Sep 2000 09:56:07 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.0/8.11.0) id e88Du7K85400; Fri, 8 Sep 2000 09:56:07 -0400 (EDT) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14776.61431.463710.288320@onceler.kciLink.com> Date: Fri, 8 Sep 2000 09:56:07 -0400 (EDT) To: freebsd-current@FreeBSD.ORG Subject: Re: call for testers: init securelevel patch In-Reply-To: References: <20000907152923.A57609@murkwood.znh.org> X-Mailer: VM 6.72 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "BE" == Bruce Evans writes: BE> revision 1.9 BE> date: 1997/06/25 07:31:47; author: joerg; state: Exp; lines: +2 -2 BE> Don't ever allow lowering the securelevel at all. Allowing it does BE> nothing good except of opening a can of (potential or real) security BE> holes. People maintaining a machine with higher security requirements BE> need to be on the console anyway, so there's no point in not forcing BE> them to reboot before starting maintenance. That last sentence makes me think that the person who decided this does not use a network to update that machine, ie NFS mounting /usr/src. It is a royal PITA to get networking up and going after a single-user reboot to get out of secure level. Perhaps one of the secure level restrictions should be that you cannot attach to pid 1 via the debugger. Does the kernel have an idea of single user mode or is that purely a user space thing? Perhaps the kernel could drop the restrictions when in single user mode itself. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 7: 4:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 754F037B422 for ; Fri, 8 Sep 2000 07:04:44 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13XOlb-00055N-00; Fri, 08 Sep 2000 16:04:31 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id QAA03562; Fri, 8 Sep 2000 16:04:30 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 3420; Fri Sep 8 16:03:49 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13XOkv-0000iZ-00; Fri, 08 Sep 2000 16:03:49 +0200 From: Sheldon Hearn To: Matthew Thyer Cc: current@freebsd.org Subject: Re: Please consider some cosmetic changes in boot messages In-reply-to: Your message of "Fri, 08 Sep 2000 23:07:22 +0930." <39B8EB92.DF0407A8@camtech.net.au> Date: Fri, 08 Sep 2000 16:03:49 +0200 Message-ID: <2762.968421829@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 08 Sep 2000 23:07:22 +0930, Matthew Thyer wrote: > Anyone else noticed how FreeBSD is inconsistent with the use of words > like "Doing", "setting" and "starting" in the boot messages ? Yes, but I wouldn't worry about it at this stage. I have a plan to revamp the way that the startup process's output is presented and stored for later viewing. I need to chat to some folks first about the best way to do this, first. Be patient, and look forward to something interesting in 5.0-RELEASE. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 7: 4:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id E4C6137B509 for ; Fri, 8 Sep 2000 07:04:49 -0700 (PDT) Received: from host62-6-66-155.btinternet.com ([62.6.66.155] helo=btinternet.com) by tungsten.btinternet.com with esmtp (Exim 3.03 #83) id 13XOlo-00005A-00 for freebsd-current@freebsd.org; Fri, 08 Sep 2000 15:04:48 +0100 Message-ID: <39B8E82C.57C4ED7@btinternet.com> Date: Fri, 08 Sep 2000 14:22:52 +0100 From: John Toon X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: microuptime() went backwards / SHMSEG References: <20000907191913.A93124@virtual-voodoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Ames wrote: > > Just upgraded to -CURRENT as of about noon (EST) today. At reboot > I got a lot of these: > > microuptime() went backwards (1.7682417 -> 1.997434) > > I recall reading in -current earlier this week that someone was > looking for victims getting this. What further information can I provide? > > -Steve If it is of any relevance, I got hundreds of these messages from 4.0-RELEASE, on my Athlon 1Ghz, Abit KA7-100 system. So many, in fact, that every time it happened, I was left with no choice but to reboot, as it slowly brought the system to its knees. Building the kernel without apm fixed the problem, and I have since had no problems. -- "I'm entirely unaccountable for any moments of sanity contained herein." :s/Windows/UNIX John Toon | j.a.toon@btinternet.com | "Sonnilon" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 7:34: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta02.mail.mel.aone.net.au (mta02.mail.au.uu.net [203.2.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 55E8837B422 for ; Fri, 8 Sep 2000 07:33:56 -0700 (PDT) Received: from camtech.net.au ([203.55.241.98]) by mta02.mail.mel.aone.net.au with ESMTP id <20000908143353.WSMC348.mta02.mail.mel.aone.net.au@camtech.net.au>; Sat, 9 Sep 2000 01:33:53 +1100 Message-ID: <39B8F928.C9F4339@camtech.net.au> Date: Sat, 09 Sep 2000 00:05:20 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Neil Blakey-Milner Cc: current@freebsd.org Subject: Re: /usr/local/etc/rc.d and /etc/rc.d References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > > On Fri 2000-09-08 (22:53), Matthew Thyer wrote: > > The startup and shutdown functionality would be in the same script > > and the scripts should be named starting with a capital 'S' for > > startup and a capital 'K' for shutdown (I'm also keen on the HPUX > > startmsg and stopmsg one liners). > > Why not just use chmod +x or chmod -x, like we do already? This means > not having to rename things. You could do either with my scheme. > > Stop scripts will be a symbolic link to their startup script > > counterpart (and would simply not be executed if the K* file doesn't > > exist). Symbolic links make it clear they are the same script. > > I don't see the point. The point is that people are worried about scripts that aren't aware of the "start" and "stop" argument trying to start apps again at shutdown time. With my scheme, the script wont be executed at shutdown time if the K* script doesn't exist. > > Scripts would be executed in alphabetical order (after the S or K) > > so the sysadmin has control over the execution order which is > > important. > > I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at > http://people.FreeBSD.org/~eivind/newrc.tar.gz) I haven't looked at this yet but off the top of my head, a dependency based system sounds overly complicated (consider ports authors) and unecessarily different from other systems. > > I'd also really like at least named and perl to be removed from the > > base system but that's another thread. > > I'll comment when you bring it up. Warning: perl is necessary for > kernel builds. I know but I'm pretty keen on awk and would like all the perl dependencies to be re-written with awk or other tools as I dislike FreeBSD being dependent on such a beast as perl which should only exist as a port. Just look at the pain of getting perl 5.6.0 into the system. I know the perl lovers will hate me but I thinks its worth having some ugly awk to get away from elegant perl being required in the base system. I'd go further to say that the whole base OS needs to be more modularised ala Solaris and Linux especially since we dont have an established binary patch process. Its pretty hard to sell FreeBSD to my work masters when the only patch method is source code patches or a complete rebuild of -STABLE or just wait until the next release. A more modular system could be upgraded more easily. > Neil > -- > Neil Blakey-Milner > Sunesi Clinical Systems > nbm@mithrandr.moria.org Matthew Thyer who needs a new .sig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 7:47:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 30E3337B423 for ; Fri, 8 Sep 2000 07:47:32 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13XPQx-000FVU-00; Fri, 08 Sep 2000 16:47:15 +0200 Date: Fri, 8 Sep 2000 16:47:15 +0200 From: Neil Blakey-Milner To: Matthew Thyer Cc: current@freebsd.org Subject: Re: /usr/local/etc/rc.d and /etc/rc.d Message-ID: <20000908164715.A59499@mithrandr.moria.org> References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> <39B8F928.C9F4339@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39B8F928.C9F4339@camtech.net.au>; from thyerm@camtech.net.au on Sat, Sep 09, 2000 at 12:05:20AM +0930 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat 2000-09-09 (00:05), Matthew Thyer wrote: > > > Stop scripts will be a symbolic link to their startup script > > > counterpart (and would simply not be executed if the K* file doesn't > > > exist). Symbolic links make it clear they are the same script. > > > > I don't see the point. > > The point is that people are worried about scripts that aren't aware > of the "start" and "stop" argument trying to start apps again at > shutdown time. With my scheme, the script wont be executed at shutdown > time if the K* script doesn't exist. If it's there, it gets executed. If it's there, it was put there. If it was put there, it'll have support for "start" and "stop". If an administrator puts a script in there that does the wrong thing, that's his fault. He could use the fall-back rc.local method. We needn't support stupid behaviour by complicating the matter. > > > Scripts would be executed in alphabetical order (after the S or K) > > > so the sysadmin has control over the execution order which is > > > important. > > > > I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at > > http://people.FreeBSD.org/~eivind/newrc.tar.gz) > > I haven't looked at this yet but off the top of my head, a dependency > based system sounds overly complicated (consider ports authors) and > unecessarily different from other systems. I am considering port authors, and I think that dependency-based systems will be _much_ better for them. Thanks for bringing it up. # before zope # before apache # after networking # after nfs is much better than: S10.networking.sh S20.nfs.sh S40.zope.sh S45.apache.sh and then figuring to use S43.foo.sh. > > > I'd also really like at least named and perl to be removed from the > > > base system but that's another thread. > > > > I'll comment when you bring it up. Warning: perl is necessary for > > kernel builds. > > I know but I'm pretty keen on awk and would like all the perl dependencies > to be re-written with awk or other tools as I dislike FreeBSD being > dependent on such a beast as perl which should only exist as a port. > Just look at the pain of getting perl 5.6.0 into the system. I know the > perl lovers will hate me but I thinks its worth having some ugly awk to > get away from elegant perl being required in the base system. I'm not particularly attached to perl, but it has a convenience in some sections, like ports, that is unmatched by sed and awk. Note the excessive use of "perl -i -pe 's/foo/bar/'" for in-place substitution. I've asked on at least two occasions for a simple, easy-to-use, thing to do it without doing a two-liner that copies to another file, and then replaces the old file with the new file. > I'd go further to say that the whole base OS needs to be more modularised > ala Solaris and Linux especially since we dont have an established binary > patch process. Its pretty hard to sell FreeBSD to my work masters when the > only patch method is source code patches or a complete rebuild of -STABLE > or just wait until the next release. A more modular system could be > upgraded more easily. I agree. I'd suggest you check out the freebsd-libh mailing list, and ask there about how to check out the libh sources. Your contributions to the libh project will aid development of the next-generation package management and installer. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 8:13:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta01.mail.mel.aone.net.au (mta01.mail.au.uu.net [203.2.192.81]) by hub.freebsd.org (Postfix) with ESMTP id 0A97337B443 for ; Fri, 8 Sep 2000 08:13:07 -0700 (PDT) Received: from camtech.net.au ([203.55.241.98]) by mta01.mail.mel.aone.net.au with ESMTP id <20000908151303.YVLU350.mta01.mail.mel.aone.net.au@camtech.net.au>; Sat, 9 Sep 2000 01:13:03 +1000 Message-ID: <39B90256.4E4B3D60@camtech.net.au> Date: Sat, 09 Sep 2000 00:44:30 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Neil Blakey-Milner Cc: current@freebsd.org Subject: Re: /usr/local/etc/rc.d and /etc/rc.d References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> <39B8F928.C9F4339@camtech.net.au> <20000908164715.A59499@mithrandr.moria.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > > On Sat 2000-09-09 (00:05), Matthew Thyer wrote: > > The point is that people are worried about scripts that aren't aware > > of the "start" and "stop" argument trying to start apps again at > > shutdown time. With my scheme, the script wont be executed at shutdown > > time if the K* script doesn't exist. > > If it's there, it gets executed. If it's there, it was put there. If > it was put there, it'll have support for "start" and "stop". > > If an administrator puts a script in there that does the wrong thing, > that's his fault. He could use the fall-back rc.local method. > > We needn't support stupid behaviour by complicating the matter. I'm behind on cvs-all and freebsd-current so forgive me but I'm basing my comments on rc.shutdown executing /usr/local/etc/rc.d/* with argument "stop". Which seems very dangerous given that people may not have rebuilt their ports for a long time. With my way the old scripts may not even be run until the admin reads up on the new scheme. > # before zope > # before apache > # after networking > # after nfs > > is much better than: > > S10.networking.sh > S20.nfs.sh > S40.zope.sh > S45.apache.sh > > and then figuring to use S43.foo.sh. We'll have to disagree on this point. Given that we've had no order control in the past and that ports are generally (yes its bad to generalise) not dependent on each other, should the situation arise I think that any admin worth his/her pay can work out how to change the order with the numbers. Remember that I'm trying to stay remotely compatible with other systems. We dont have to re-invent the wheel. I still think a dependency based system is way more complicated than what is required. > I'm not particularly attached to perl, but it has a convenience in some > sections, like ports, that is unmatched by sed and awk. Note the > excessive use of "perl -i -pe 's/foo/bar/'" for in-place substitution. > I've asked on at least two occasions for a simple, easy-to-use, thing to > do it without doing a two-liner that copies to another file, and then > replaces the old file with the new file. My point is that its worth some ugly awk and sed to get away from the base OS depending on perl. I dont care how elegant perl is. Thats about all I'll say on this thread.... got to sleep. > Neil > -- > Neil Blakey-Milner > Sunesi Clinical Systems > nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 8:14:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2562E37B424 for ; Fri, 8 Sep 2000 08:14:19 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA17540; Sat, 9 Sep 2000 02:14:04 +1100 Date: Sat, 9 Sep 2000 02:14:00 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Vivek Khera Cc: freebsd-current@FreeBSD.ORG Subject: Re: call for testers: init securelevel patch In-Reply-To: <14776.61431.463710.288320@onceler.kciLink.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, 8 Sep 2000, Vivek Khera wrote: > >>>>> "BE" == Bruce Evans writes: > > BE> revision 1.9 > BE> holes. People maintaining a machine with higher security requirements > BE> need to be on the console anyway, so there's no point in not forcing > BE> them to reboot before starting maintenance. > > That last sentence makes me think that the person who decided this > does not use a network to update that machine, ie NFS mounting > /usr/src. It is a royal PITA to get networking up and going after a > single-user reboot to get out of secure level. He would probably say that using nfs is inconsistent with being secure. If you only use nfs for updating the machine, then the PITA for securing it then may be larger than the PITA for starting networking. > Perhaps one of the secure level restrictions should be that you cannot > attach to pid 1 via the debugger. This was implemented at about the same time as rev.1.9. > Does the kernel have an idea of single user mode or is that purely a > user space thing? Perhaps the kernel could drop the restrictions when > in single user mode itself. It's almost pure user space. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 8:25: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 2FD0837B505 for ; Fri, 8 Sep 2000 08:25:05 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-213-168-64-62.netcologne.de [213.168.64.62]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id RAA26087; Fri, 8 Sep 2000 17:25:02 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e88FOqf00461; Fri, 8 Sep 2000 17:24:52 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Fri, 8 Sep 2000 17:24:52 +0200 (CEST) From: Paul Herman To: Vivek Khera Cc: freebsd-current@FreeBSD.ORG Subject: Re: call for testers: init securelevel patch In-Reply-To: <14776.61431.463710.288320@onceler.kciLink.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, 8 Sep 2000, Vivek Khera wrote: > >>>>> "BE" == Bruce Evans writes: > > BE> revision 1.9 > BE> date: 1997/06/25 07:31:47; author: joerg; state: Exp; lines: +2 -2 > BE> Don't ever allow lowering the securelevel at all. Allowing it does > BE> nothing good except of opening a can of (potential or real) security > BE> holes. People maintaining a machine with higher security requirements > BE> need to be on the console anyway, so there's no point in not forcing > BE> them to reboot before starting maintenance. > > Perhaps one of the secure level restrictions should be that you cannot > attach to pid 1 via the debugger. You can't. Ever since Apr 1997 you couldn't attach gdb to init. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 9:11:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ztxmail05.ztx.compaq.com (ztxmail05.ztx.compaq.com [161.114.1.209]) by hub.freebsd.org (Postfix) with ESMTP id 3DAE537B42C for ; Fri, 8 Sep 2000 09:11:25 -0700 (PDT) Received: by ztxmail05.ztx.compaq.com (Postfix, from userid 12345) id CD77916BB; Fri, 8 Sep 2000 11:11:24 -0500 (CDT) Received: from fedex-s1.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by ztxmail05.ztx.compaq.com (Postfix) with ESMTP id 90F8815F6 for ; Fri, 8 Sep 2000 11:11:24 -0500 (CDT) From: Bruce Burden Posted-Date: Fri, 8 Sep 2000 11:11:37 -0500 (CDT) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id LAA03091 for freebsd-current@freebsd.org; Fri, 8 Sep 2000 11:11:23 -0500 (CDT) Message-Id: <200009081611.LAA03091@panther.txn.cpqcorp.net> Subject: Re: netscape To: freebsd-current@freebsd.org Date: Fri, 8 Sep 2000 11:11:22 -0500 (CDT) Reply-To: bruce.burden@compaq.com In-Reply-To: <39B8C973.98F4F51E@cs.put.poznan.pl> from "Piotr Woniak" at Sep 08, 2000 01:11:47 PM 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 installed netscape4-navigator and I can't launch its. > I've got following message: > > ld.so failed: Can't find shared library "libXt.so.6.0" > Assuming you have the a.out libraries installed as per the other messages, you probably need to assign the LD_LIBRARY_PATH in the "which netscape" file to be your LD_LIBRARY_AOUT_PATH (I believe that is the correct name for it). assign LD_LIBRARY_PATH=${LD_LIBRARY_AOUT_PATH} since the native netscape doesn't bother to read any library path but the "standard" one, which of course points to ELF libraries, and not a.out ones... Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 9:23:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id D3F7937B43F for ; Fri, 8 Sep 2000 09:23:32 -0700 (PDT) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id BAA99086; Sat, 9 Sep 2000 01:53:30 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.11.0/8.9.3) id e88GNSX41440; Sat, 9 Sep 2000 01:53:28 +0930 (CST) (envelope-from darius) Message-Id: <200009081623.e88GNSX41440@guppy.dons.net.au> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200009081611.LAA03091@panther.txn.cpqcorp.net> Date: Sat, 09 Sep 2000 01:53:27 +0930 (CST) From: "Daniel O'Connor" To: Bruce Burden Subject: Re: netscape Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Sep-00 Bruce Burden wrote: > since the native netscape doesn't bother to read any library path > but the "standard" one, which of course points to ELF libraries, > and not a.out ones... You're supposed to use ldconfig -aout for that.. --- 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 Fri Sep 8 10:18:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from Den.BOFH.Halifax.NS.Ca (Den.BOFH.Halifax.ns.Ca [129.173.46.183]) by hub.freebsd.org (Postfix) with ESMTP id 5B4C737B42C for ; Fri, 8 Sep 2000 10:18:15 -0700 (PDT) Received: (from hume@localhost) by Den.BOFH.Halifax.NS.Ca (8.9.3+Sun/8.9.1) id OAA29932 for freebsd-current@freebsd.org; Fri, 8 Sep 2000 14:18:09 -0300 (ADT) From: Brandon Hume Message-Id: <200009081718.OAA29932@Den.BOFH.Halifax.NS.Ca> Subject: SMPng CPU states To: freebsd-current@freebsd.org Date: Fri, 8 Sep 2000 14:17:58 -0300 (ADT) X-Mailer: ELM [version 2.4ME+ PL42 (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 built world and kernel yesterday, and was delighted to see the AIC7xxx problems had gone away. I actually got tripped up by having Linux emulation enabled and forgetting to remove old modules, but that was fixed quick. All-in-all, I'm not having a rough time at all with the new code. My machine has been up for 7.5 hours now without a hiccup. I DID notice that I can't load X without a hang, which I think is the same AGP problem someone else mentioned. The only other thing I've noticed is top telling me that the CPU is steady at 50.0% system and 50.0% idle. The box is completely quiescent, except for me ssh'd in and running top. vmstat says sy=50 and id=50 as well. If I start a CPU-chewing process (sh -c 'while true; do true; done') the resultant CPU usage in %user seems to come from %system. -- Brandon Hume - hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 11:14:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 4794C37B506 for ; Fri, 8 Sep 2000 11:14:34 -0700 (PDT) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id LAA09049; Fri, 8 Sep 2000 11:12:06 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id LAA45491; Fri, 8 Sep 2000 11:12:05 -0700 (PDT) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id LAA07171; Fri, 8 Sep 2000 11:12:03 -0700 (PDT) From: Don Lewis Message-Id: <200009081812.LAA07171@salsa.gv.tsc.tdk.com> Date: Fri, 8 Sep 2000 11:12:02 -0700 In-Reply-To: <39B8F928.C9F4339@camtech.net.au> References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> <39B8F928.C9F4339@camtech.net.au> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Matthew Thyer , Neil Blakey-Milner Subject: Re: /usr/local/etc/rc.d and /etc/rc.d Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 9, 12:05am, Matthew Thyer wrote: } Subject: Re: /usr/local/etc/rc.d and /etc/rc.d } Neil Blakey-Milner wrote: } > I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at } > http://people.FreeBSD.org/~eivind/newrc.tar.gz) How does this compare with what NetBSD implemented? } I haven't looked at this yet but off the top of my head, a dependency } based system sounds overly complicated (consider ports authors) and } unecessarily different from other systems. NetBSD switched to a dependency based system a while back. Judging by the traffic on their mail lists, it was somewhat controversial ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 11:40:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 2E0EA37B42C for ; Fri, 8 Sep 2000 11:40:18 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13XT26-000G5f-00; Fri, 08 Sep 2000 20:37:50 +0200 Date: Fri, 8 Sep 2000 20:37:50 +0200 From: Neil Blakey-Milner To: Don Lewis Cc: Matthew Thyer , current@FreeBSD.ORG Subject: Re: /usr/local/etc/rc.d and /etc/rc.d Message-ID: <20000908203750.A61727@mithrandr.moria.org> References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> <39B8F928.C9F4339@camtech.net.au> <200009081812.LAA07171@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200009081812.LAA07171@salsa.gv.tsc.tdk.com>; from Don.Lewis@tsc.tdk.com on Fri, Sep 08, 2000 at 11:12:02AM -0700 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2000-09-08 (11:12), Don Lewis wrote: > On Sep 9, 12:05am, Matthew Thyer wrote: > } Subject: Re: /usr/local/etc/rc.d and /etc/rc.d > } Neil Blakey-Milner wrote: > > } > I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at > } > http://people.FreeBSD.org/~eivind/newrc.tar.gz) > > How does this compare with what NetBSD implemented? > > } I haven't looked at this yet but off the top of my head, a dependency > } based system sounds overly complicated (consider ports authors) and > } unecessarily different from other systems. > > NetBSD switched to a dependency based system a while back. Judging by > the traffic on their mail lists, it was somewhat controversial ... Eivind's system is almost exactly the same. I wonder if they used it as a base. (they also seem to use etc/default from March this year) Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 11:46:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8B4F337B42C for ; Fri, 8 Sep 2000 11:46:33 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id LAA55201; Fri, 8 Sep 2000 11:45:08 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009081845.LAA55201@pike.osd.bsdi.com> Subject: Re: SMPng CPU states In-Reply-To: <200009081718.OAA29932@Den.BOFH.Halifax.NS.Ca> from Brandon Hume at "Sep 8, 2000 02:17:58 pm" To: Brandon Hume Date: Fri, 8 Sep 2000 11:45:08 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (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 Brandon Hume wrote: > I've built world and kernel yesterday, and was delighted to see the AIC7xxx > problems had gone away. I actually got tripped up by having Linux emulation > enabled and forgetting to remove old modules, but that was fixed quick. > > All-in-all, I'm not having a rough time at all with the new code. My > machine has been up for 7.5 hours now without a hiccup. I DID notice that > I can't load X without a hang, which I think is the same AGP problem someone > else mentioned. > > The only other thing I've noticed is top telling me that the CPU is steady > at 50.0% system and 50.0% idle. The box is completely quiescent, except for > me ssh'd in and running top. vmstat says sy=50 and id=50 as well. If I > start a CPU-chewing process (sh -c 'while true; do true; done') the resultant > CPU usage in %user seems to come from %system. Process accounting is somewhat broken. The actual runtime of each process (p_runtime, or TIME in top) is accurate, but many of the other statistics are broken at the moment since statclock() no longer has a proper stackframe to work with. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 11:50: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B3DB37B423 for ; Fri, 8 Sep 2000 11:50:01 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id NAA57072; Fri, 8 Sep 2000 13:48:38 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 8 Sep 2000 13:48:37 -0500 (CDT) From: Chris Dillon To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: New ATA tagged queuing patch available In-Reply-To: <200009081148.NAA90969@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 On Fri, 8 Sep 2000, Soren Schmidt wrote: > If I dont get any serious problem reports I'll commit this > shortly, making FreeBSD the first OS that has tagged Queuing > support for ATA drives :) Wow, even before Windows? :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 12:38:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 461EF37B446 for ; Fri, 8 Sep 2000 12:38:03 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id WAA01815; Thu, 7 Sep 2000 22:43:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009080543.WAA01815@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: Kenneth Wayne Culver , John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-reply-to: Your message of "Fri, 08 Sep 2000 13:54:33 +0930." <20000908135433.V83632@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 22:43:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121)y > > > > this is bad.. right ? :-) > > Well, at any rate it looks very funny. If this is a laptop, try > building a kernel without apm and see if that helps. It only helps "hide" the problem. There's either *extremely* bogus data coming in, or an arithmetic or sequencing error that's allowing a corrupt timecounter to be seen. It might help to see the negative number as hex... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 12:38:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 1DE3437B42C for ; Fri, 8 Sep 2000 12:38:19 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id UAA00442; Thu, 7 Sep 2000 20:19:10 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009080319.UAA00442@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: world broken In-reply-to: Your message of "Thu, 07 Sep 2000 19:38:49 MDT." <200009080138.TAA49048@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 20:19:10 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > looks like the boot loader is killing -current. I have a patch, but > it just cuts all the offending references. > > Comments? rebuild/reinstall libstand. Sorry; should have HEADS-UPped that one. > Warner > > cc -nostdlib -static -Ttext 0x0 -o loader.sym /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o isapnp.o pnp.o interp_forth.o vers.o /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../../ficl/libficl.a /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../libi386/libi386.a -lstand > /usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In function `pxe_enable': > pxe.o(.text+0x552): undefined reference to `nfs_root_node' > *** Error code 1 > > Stop in /home/imp/FreeBSD/src/sys/boot/i386/loader. > *** Error code 1 > > Stop in /home/imp/FreeBSD/src/sys/boot/i386. > *** Error code 1 > > ... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 12:42:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id BA4DA37B43F for ; Fri, 8 Sep 2000 12:42:31 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id MAA57127 for current@FreeBSD.org; Fri, 8 Sep 2000 12:42:18 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009081942.MAA57127@pike.osd.bsdi.com> Subject: Dirty buffers on reboot.. To: current@FreeBSD.org Date: Fri, 8 Sep 2000 12:42:18 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (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 Ok, an update on the dirty buffers on reboot: If you use the reboot command, you will get dirty buffers. If you use 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a workaround for now, use the shutdown command to reboot your box until we can track this down. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 12:43: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 1FF3C37B423; Fri, 8 Sep 2000 12:43:01 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e88JgrN82051; Fri, 8 Sep 2000 21:42:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Greg Lehey , Kenneth Wayne Culver , John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: Your message of "Thu, 07 Sep 2000 22:43:11 PDT." <200009080543.WAA01815@mass.osd.bsdi.com> Date: Fri, 08 Sep 2000 21:42:53 +0200 Message-ID: <82049.968442173@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009080543.WAA01815@mass.osd.bsdi.com>, Mike Smith writes: >> > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121)y >> > >> > this is bad.. right ? :-) >> >> Well, at any rate it looks very funny. If this is a laptop, try >> building a kernel without apm and see if that helps. > >It only helps "hide" the problem. There's either *extremely* bogus data >coming in, or an arithmetic or sequencing error that's allowing a corrupt >timecounter to be seen. > >It might help to see the negative number as hex... I have collected all the emails I've received and I have identified at least two different causes: There is a bogus i8254 implementation on certain Athlon Mobos, this is a non-brainer since they should not use the i8254 but the TSC. There are negative numbers coming in from both the i8254 and in a few cases from the TSC. NTIMECOUNTER may be too low for certain systems, I'm still waiting for some feedback on that. Either way, I have a patch which I need to burn in in my lab, but right now I have a hard time getting my SMP box to even print out "Copyright..." when it boots :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 12:48:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id 3560337B440; Fri, 8 Sep 2000 12:48:16 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 13XU8D-000EeV-0V; Fri, 8 Sep 2000 20:48:13 +0100 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 UAA12959; Fri, 8 Sep 2000 20:49:42 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 8 Sep 2000 20:49:07 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: The Hermit Hacker , freebsd-smp@freebsd.org, freebsd-current@freebsd.org Subject: Re: Installed SMP patch and now mouse doesn't work? In-Reply-To: <200009062355.QAA81102@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, John Baldwin wrote: > The Hermit Hacker wrote: > > > > Have nothing else to go on yet ... I updated both the current source code > > and installed the SMP patch from Sept 5th. Everything installed great, > > rebooted and I can work in character mode ... go to X, and the mouse gives > > me no activity, where it did just before the upgrade ... > > > > Am still investigating at this end, but if anyone else has experience > > similar and knows how to fix? > > Uh, all of the SMPng boxes so far haven't had mice. :P Is your mouse a > serial mouse? There seem to be some problems with input on the sio > devices. This is because the schedsofttty() call is commented out so the high-level interrupt routine in sio is never entered. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 13:13:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 735FF37B507 for ; Fri, 8 Sep 2000 13:13:23 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA01217; Fri, 8 Sep 2000 13:24:33 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009082024.NAA01217@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-reply-to: Your message of "Fri, 08 Sep 2000 21:42:53 +0200." <82049.968442173@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Sep 2000 13:24:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have collected all the emails I've received and I have identified > at least two different causes: > > There is a bogus i8254 implementation on certain Athlon Mobos, this > is a non-brainer since they should not use the i8254 but the TSC. s/TSC/ACPI timer/ It might even work on those systems. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 13:45: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 919B437B43E; Fri, 8 Sep 2000 13:45:01 -0700 (PDT) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA07014; Fri, 8 Sep 2000 16:44:37 -0400 (EDT) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id QAA25295; Fri, 8 Sep 2000 16:44:37 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA25288; Fri, 8 Sep 2000 16:44:37 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Fri, 8 Sep 2000 16:44:37 -0400 (EDT) From: Kenneth Wayne Culver To: Poul-Henning Kamp Cc: Mike Smith , Greg Lehey , John Baldwin , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: <82049.968442173@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could all this be in any way related to the statclock not working on certain systems (like my Dell Inspiron)?? Also, could the "rtc" device as listed in systat -vm not being there (I'm assuming this is the statclock) be causing scheduling anomalies? I ask because I am trying to get gaim (multi-threaded, and using gtk which is threaded as well) to work on my laptop. It works on my desktop (-CURRENT), and on my friend's desktop (-STABLE) but not on my laptop (-STABLE). Just wondering... Thanks. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 8 Sep 2000, Poul-Henning Kamp wrote: > In message <200009080543.WAA01815@mass.osd.bsdi.com>, Mike Smith writes: > >> > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 10412, -694583121)y > >> > > >> > this is bad.. right ? :-) > >> > >> Well, at any rate it looks very funny. If this is a laptop, try > >> building a kernel without apm and see if that helps. > > > >It only helps "hide" the problem. There's either *extremely* bogus data > >coming in, or an arithmetic or sequencing error that's allowing a corrupt > >timecounter to be seen. > > > >It might help to see the negative number as hex... > > I have collected all the emails I've received and I have identified > at least two different causes: > > There is a bogus i8254 implementation on certain Athlon Mobos, this > is a non-brainer since they should not use the i8254 but the TSC. > > There are negative numbers coming in from both the i8254 and in a > few cases from the TSC. NTIMECOUNTER may be too low for certain > systems, I'm still waiting for some feedback on that. > > Either way, I have a patch which I need to burn in in my lab, but > right now I have a hard time getting my SMP box to even print out > "Copyright..." when it boots :-( > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 14:38:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id 6D7D437B506 for ; Fri, 8 Sep 2000 14:38:45 -0700 (PDT) Received: from localhost (trish@localhost) by superconductor.rush.net (8.9.3/8.9.3) with ESMTP id RAA00059; Fri, 8 Sep 2000 17:38:18 -0400 (EDT) Date: Fri, 8 Sep 2000 17:38:12 -0400 (EDT) From: Siobhan Patricia Lynch X-Sender: trish@superconductor.rush.net To: John Baldwin Cc: Greg Lehey , Steve Ames , freebsd-current@FreeBSD.ORG Subject: Re: microuptime() went backwards In-Reply-To: <200009080048.RAA26766@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Sep 2000, John Baldwin wrote: > > Most definitely an SMPng issue. If you take a SMP machine and compile a UP > and an SMP kernel on it, the SMP kernel will boot fine, whereas the UP kernel > will generate these warnings. > John, not quite, I have an SMP box that I got these warnings on, spent the better part of the day trying to reproduce them (after the machine became unresponsive last night) the machine is a N440BX Night (Intel) motherboard, with two PII 333's. the board has everything onboard except the disks. the only change besides building an SMPng kernel was to take out COMPAT_OLDPCI. If I can find out more for you I will, however I'm leaving for vacation at 7:30 AM tomorrow morning. -Trish __ Trish Lynch FreeBSD - The Power to Serve trish@bsdunix.net Rush Networking trish@rush.net VA Linux Systems trish@valinux.com O|S|D|N trish@osdn.com --- Q: Have you guys ever been on Sesame Street as special guests? A (from Geddy): No. Much to the dismay of my daughter. Q: Would you be on Sesame Street if you were asked? A (again from Geddy): G: Yes. How could you turn Sesame Street down? That borders on criminal. -Geddy Lee From Rush, on Rockline. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 15:48:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 3E92937B50F; Fri, 8 Sep 2000 15:48:30 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e88Mm0601620; Fri, 8 Sep 2000 19:48:00 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 19:48:00 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Cc: freebsd-smp@freebsd.org Subject: mouse works!! 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 serial mouse works with currrent sources ... thanks guys Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 16:47:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id C653337B505 for ; Fri, 8 Sep 2000 16:47:50 -0700 (PDT) Received: by gw.nectar.com (Postfix, from userid 1001) id 45DCB1925A; Fri, 8 Sep 2000 18:47:49 -0500 (CDT) Date: Fri, 8 Sep 2000 18:47:49 -0500 From: "Jacques A. Vidrine" To: Neil Blakey-Milner Cc: Matthew Thyer , current@freebsd.org Subject: Re: /usr/local/etc/rc.d and /etc/rc.d Message-ID: <20000908184749.C1317@spawn.nectar.com> References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> <39B8F928.C9F4339@camtech.net.au> <20000908164715.A59499@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000908164715.A59499@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Fri, Sep 08, 2000 at 04:47:15PM +0200 X-Url: http://www.nectar.com/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 08, 2000 at 04:47:15PM +0200, Neil Blakey-Milner wrote: > Note the excessive use of "perl -i -pe 's/foo/bar/'" for in-place > substitution. I've asked on at least two occasions for a simple, > easy-to-use, thing to do it without doing a two-liner that copies to > another file, and then replaces the old file with the new file. If it weren't for perl, we'd probably already have `sed -i' :-) -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@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 Sep 8 16:56: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id B1AE737B43F; Fri, 8 Sep 2000 16:55:55 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e88Np8e57686; Sat, 9 Sep 2000 00:51:08 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e88Nogn57839; Sat, 9 Sep 2000 00:50:42 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009082350.e88Nogn57839@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wes Peters Cc: Seigo Tanimura , current@FreeBSD.org, net@FreeBSD.org, brian@Awfulhak.org Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr In-Reply-To: Message from Wes Peters of "Tue, 05 Sep 2000 00:13:50 MDT." <39B48F1E.4C193F79@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Sep 2000 00:50:42 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Seigo Tanimura wrote: > > > > I have been suffering from this problem for almost 2 months. When I > > remove a pcmcia ethernet card from my laptop PC, routed(8) announces > > updated routing information by multicast, leading to a kernel > > panic. > > Ejecting an interface configured up will do that. ifconfig the interface > `down' and then `delete' before ejecting it. Interfaces in promiscuous mode will always result in a reboot. I *usually* get away with ejecting an active card if it's not in promiscuous mode. > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > wes@softweyr.com http://softweyr.com/ -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 18:43: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 8D12737B505 for ; Fri, 8 Sep 2000 18:43:00 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e891f9K06081; Sat, 9 Sep 2000 11:11:09 +0930 (CST) (envelope-from grog) Date: Sat, 9 Sep 2000 11:11:09 +0930 From: Greg Lehey To: Chris Dillon Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: New ATA tagged queuing patch available Message-ID: <20000909111108.C5876@wantadilla.lemis.com> References: <200009081148.NAA90969@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Fri, Sep 08, 2000 at 01:48:37PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 8 September 2000 at 13:48:37 -0500, Chris Dillon wrote: > On Fri, 8 Sep 2000, Soren Schmidt wrote: > >> If I dont get any serious problem reports I'll commit this >> shortly, making FreeBSD the first OS that has tagged Queuing >> support for ATA drives :) > > Wow, even before Windows? :-) He did say "OS". 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 Sep 8 18:49:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 5B46737B43F for ; Fri, 8 Sep 2000 18:49:37 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e891nRi06122; Sat, 9 Sep 2000 11:19:27 +0930 (CST) (envelope-from grog) Date: Sat, 9 Sep 2000 11:19:26 +0930 From: Greg Lehey To: Brandon Hume Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMPng CPU states Message-ID: <20000909111926.D5876@wantadilla.lemis.com> References: <200009081718.OAA29932@Den.BOFH.Halifax.NS.Ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200009081718.OAA29932@Den.BOFH.Halifax.NS.Ca>; from hume@Den.BOFH.Halifax.NS.Ca on Fri, Sep 08, 2000 at 02:17:58PM -0300 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 8 September 2000 at 14:17:58 -0300, Brandon Hume wrote: > I've built world and kernel yesterday, and was delighted to see the AIC7xxx > problems had gone away. I actually got tripped up by having Linux emulation > enabled and forgetting to remove old modules, but that was fixed quick. > > All-in-all, I'm not having a rough time at all with the new code. My > machine has been up for 7.5 hours now without a hiccup. I DID notice that > I can't load X without a hang, which I think is the same AGP problem someone > else mentioned. FWIW, I've had no trouble running X on my development box. Well, the monitor can only do 640x480, but that's not an OS issue. 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 Sep 8 18:54:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta02.mail.mel.aone.net.au (mta02.mail.au.uu.net [203.2.192.82]) by hub.freebsd.org (Postfix) with ESMTP id B2E2F37B440 for ; Fri, 8 Sep 2000 18:54:06 -0700 (PDT) Received: from camtech.net.au ([203.55.245.90]) by mta02.mail.mel.aone.net.au with ESMTP id <20000909015402.BJS348.mta02.mail.mel.aone.net.au@camtech.net.au>; Sat, 9 Sep 2000 12:54:02 +1100 Message-ID: <39B99893.EE5DDF65@camtech.net.au> Date: Sat, 09 Sep 2000 11:25:31 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Don Lewis Cc: Neil Blakey-Milner , current@FreeBSD.ORG Subject: Re: /usr/local/etc/rc.d and /etc/rc.d References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> <39B8F928.C9F4339@camtech.net.au> <200009081812.LAA07171@salsa.gv.tsc.tdk.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don Lewis wrote: > > On Sep 9, 12:05am, Matthew Thyer wrote: > } Subject: Re: /usr/local/etc/rc.d and /etc/rc.d > } Neil Blakey-Milner wrote: > > } > I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at > } > http://people.FreeBSD.org/~eivind/newrc.tar.gz) > > How does this compare with what NetBSD implemented? > > } I haven't looked at this yet but off the top of my head, a dependency > } based system sounds overly complicated (consider ports authors) and > } unecessarily different from other systems. > > NetBSD switched to a dependency based system a while back. Judging by > the traffic on their mail lists, it was somewhat controversial ... I'd consider it overly complicated because: - The OS vendor can work out the correct order for system component startup and set the numbers right once per release so who needs the overhead and complexity of a dependency based system ? - The ports collection is so huge these days that we need to make it easier rather than harder for non-hardcore FreeBSD users to submit and maintain their own ports. Its already hard enough to do a port right especially if it should have ifdefs on the version of FreeBSD to work correctly in -STABLE and -CURRENT. Port authors really need -CURRENT and -STABLE installed and maintain a copy of the repository to DTRT. - The SysV style number based system is fine in that port authors can all use the same number (say S50myport) unless it needs to be changed due to the unlikely need for ordering (remember we haven't had ordering to date and there are ~3700 ports). - Dont think of /usr/local/etc/rc.d being just for the ports collection, people will put there own startup scripts there too and will find it very easy to just pick the right numbers ala SysV. I do admin SysV systems of all types (mainly Solaris, HPUX, IRIX, True64 - yes I work for Defence) as my paid job so I know how easy the number order system is to use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 19: 8:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 8DBE537B424 for ; Fri, 8 Sep 2000 19:08:30 -0700 (PDT) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id EAA69984; Sat, 9 Sep 2000 04:08:23 +0200 (CEST) Message-Id: <200009090208.EAA69984@midten.fast.no> To: jhb@pike.osd.bsdi.com Cc: current@FreeBSD.ORG Subject: Re: Dirty buffers on reboot.. From: Tor.Egge@fast.no In-Reply-To: Your message of "Fri, 8 Sep 2000 12:42:18 -0700 (PDT)" References: <200009081942.MAA57127@pike.osd.bsdi.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 09 Sep 2000 04:08:22 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, an update on the dirty buffers on reboot: > > If you use the reboot command, you will get dirty buffers. If you use > 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a workaround > for now, use the shutdown command to reboot your box until we can track this > down. I suggest using some method to allow interrupt threads to run during the shutdown. Perhaps the current process priority should be elevated so it is guaranteed to be scheduled after the last interrupt thread instead of some unrelated process. Index: kern_shutdown.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v retrieving revision 1.80 diff -u -r1.80 kern_shutdown.c --- kern_shutdown.c 2000/09/07 01:32:51 1.80 +++ kern_shutdown.c 2000/09/09 01:42:20 @@ -220,6 +220,7 @@ if (!cold && (howto & RB_NOSYNC) == 0 && waittime < 0) { register struct buf *bp; int iter, nbusy; + int subiter; waittime = 0; printf("\nsyncing disks... "); @@ -247,7 +248,18 @@ break; printf("%d ", nbusy); sync(&proc0, NULL); - DELAY(50000 * iter); + + if (curproc != NULL) { + for (subiter = 0; subiter < 50 * iter; subiter++) { + mtx_enter(&sched_lock, MTX_SPIN); + setrunqueue(curproc); + mi_switch(); /* Allow interrupt threads to run */ + mtx_exit(&sched_lock, MTX_SPIN); + DELAY(1000); + } + } else + DELAY(50000 * iter); + } printf("\n"); /* - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 19:31:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id C133937B446 for ; Fri, 8 Sep 2000 19:31:20 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13XaPy-000Heh-00; Sat, 09 Sep 2000 04:30:58 +0200 Date: Sat, 9 Sep 2000 04:30:58 +0200 From: Neil Blakey-Milner To: Matthew Thyer Cc: Don Lewis , current@FreeBSD.ORG Subject: Re: /usr/local/etc/rc.d and /etc/rc.d Message-ID: <20000909043057.A67715@mithrandr.moria.org> References: <39B8E865.B77012B@camtech.net.au> <20000908153421.A58134@mithrandr.moria.org> <39B8F928.C9F4339@camtech.net.au> <200009081812.LAA07171@salsa.gv.tsc.tdk.com> <39B99893.EE5DDF65@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39B99893.EE5DDF65@camtech.net.au>; from thyerm@camtech.net.au on Sat, Sep 09, 2000 at 11:25:31AM +0930 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat 2000-09-09 (11:25), Matthew Thyer wrote: > Don Lewis wrote: > > > > On Sep 9, 12:05am, Matthew Thyer wrote: > > } Subject: Re: /usr/local/etc/rc.d and /etc/rc.d > > } Neil Blakey-Milner wrote: > > > > } > I'd prefer a dependency based system. (cf. Eivind Eklund's newrc, at > > } > http://people.FreeBSD.org/~eivind/newrc.tar.gz) > > > > How does this compare with what NetBSD implemented? > > > > } I haven't looked at this yet but off the top of my head, a dependency > > } based system sounds overly complicated (consider ports authors) and > > } unecessarily different from other systems. > > > > NetBSD switched to a dependency based system a while back. Judging by > > the traffic on their mail lists, it was somewhat controversial ... > > I'd consider it overly complicated because: > > - The OS vendor can work out the correct order for system component > startup and set the numbers right once per release so who needs > the overhead and complexity of a dependency based system ? We don't work with machines "once per release". Keeping those numbered files in CVS will also suck if we rearrange things. You're making an assumption that there is overhead and complexity in a dependency-based system. The NetBSD one seems incredibly no-nonsense and direct - the core of /etc/rc is: files=`rcorder -s nostart /etc/rc.d/*` for i in $files; do run_rc_script $i start done Here's a simple dependency example: /---- #!/bin/sh # # $NetBSD: timed,v 1.2 2000/03/13 04:04:10 lukem Exp $ # # PROVIDE: timed # REQUIRE: DAEMON . /etc/rc.subr name="timed" command="/usr/sbin/${name}" load_rc_config $name run_rc_command "$1" \---- Or a more complex on: /---- #!/bin/sh # # $NetBSD: postfix,v 1.3 2000/04/30 12:21:00 lukem Exp $ # # PROVIDE: mail # REQUIRE: LOGIN # we could do this, but make mail start late, so that things like # .forward's are not processed until the system is fully operational ## REQUIRE: DAEMON . /etc/rc.subr name="postfix" required_files="/etc/${name}/main.cf" extra_commands="reload" start_precmd="checkyesno postfix" start_cmd="postfix start" stop_precmd=$start_precmd stop_cmd="postfix stop" reload_precmd=$start_precmd reload_cmd="postfix reload" load_rc_config $name run_rc_command "$1" \---- This is really easy to understand and document, and the few people of all levels of proficiency I've just asked think this is cool. > - The ports collection is so huge these days that we need to make it > easier rather than harder for non-hardcore FreeBSD users to > submit and maintain their own ports. Its already hard enough to > do a port right especially if it should have ifdefs on the version > of FreeBSD to work correctly in -STABLE and -CURRENT. Port authors > really need -CURRENT and -STABLE installed and maintain a copy of the > repository to DTRT. Most of the ports submitters I know personally only have -RELEASE machines. They seem to do fine. I don't see how the SysV way is any easier than the dependency-based system. The dependency-based system means you can set it up, and then leave it alone and never worry about renumbering. > - The SysV style number based system is fine in that port authors can > all use the same number (say S50myport) unless it needs to be changed > due to the unlikely need for ordering (remember we haven't had > ordering > to date and there are ~3700 ports). This applies equally to a dependency-based system. Most will use the PORTS requirement, I imagine, which'd be equivalent to the current system, and which we could tweak from a central place if needs be, without changing every single port. > - Dont think of /usr/local/etc/rc.d being just for the ports collection, > people will put there own startup scripts there too and will find it > very easy to just pick the right numbers ala SysV. Only to have the vendor re-number things in the next release, and spoil their carefully-located numbers? Dependencies are a big win here too. All in all I'm delighted with the NetBSD dependency-based system that has been pointed out to me. It'd be great to synchronise with their system, and share and help develop their code (which, from casual inspection, is great, and looks like it may never need changes). It kinda makes me wonder what I'll do when I see that RedHat machine at work. (: Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 8 23:38:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 9AD6F37B507 for ; Fri, 8 Sep 2000 23:38:54 -0700 (PDT) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id OAA22972 for ; Sat, 9 Sep 2000 14:37:58 +0800 Received: from jules.elischer.org (reggae-20-229.nv.iinet.net.au [203.59.85.229]) by muzak.iinet.net.au (8.8.5/8.8.5) with SMTP id OAA03953 for ; Sat, 9 Sep 2000 14:37:55 +0800 Message-ID: <39B9DABD.167EB0E7@elischer.org> Date: Fri, 08 Sep 2000 23:37:49 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Vmware (1.x) port broken in -current References: <20000908154320.J12231@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a warning, that the current vmware 1.x port doesn;t compile under -current. I'm looking at it at the moment (as I only have a licence for 1.x) julian -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 0: 1:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C2BC37B5AF for ; Sat, 9 Sep 2000 00:01:10 -0700 (PDT) Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8519A6E2B8A for ; Fri, 8 Sep 2000 23:58:57 -0700 (PDT) Received: from jules.elischer.org (reggae-20-229.nv.iinet.net.au [203.59.85.229]) by urban.iinet.net.au (8.8.7/8.8.7) with SMTP id OAA25201 for ; Sat, 9 Sep 2000 14:57:52 +0800 Message-ID: <39B9DF6A.2781E494@elischer.org> Date: Fri, 08 Sep 2000 23:57:46 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: more on: Vmware (1.x) port broken in -current References: <20000908154320.J12231@fw.wintelcom.net> <39B9DABD.167EB0E7@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Just a warning, that the current vmware 1.x port doesn;t compile > under -current. > I'm looking at it at the moment (as I only have a licence for 1.x) > responding to myself: the linux include files that have moved to /sys/compat/linux need to be changed in a couple of files: ./work/vmware-distrib/vmnet-only/freebsd/vmnet_linux.c ./work/vmware-distrib/vmmon-only/freebsd/linux_emu.c the following change needs to be made to ./work/vmware-distrib/vmnet-only/freebsd/vmnet.c: #if (__FreeBSD__ == 5) ether_ifattach(ifp, 1); #else /* ORIGINAL CODE */ if_attach(ifp); ether_ifattach(ifp); bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); #endif After that, it all compiles but it doesn't run due to: sh vmware.sh start kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec format error kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec format error I have NO idea wha that means.. (how can a module I just compile 30 seconds before be in the wrong format?) -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 0: 4: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from gadolinium.btinternet.com (gadolinium.btinternet.com [194.73.73.111]) by hub.freebsd.org (Postfix) with ESMTP id 663F737B50B for ; Sat, 9 Sep 2000 00:04:01 -0700 (PDT) Received: from host62-6-66-155.btinternet.com ([62.6.66.155] helo=btinternet.com) by tantalum with esmtp (Exim 3.03 #83) id 13XOza-0005cS-00 for freebsd-current@freebsd.org; Fri, 08 Sep 2000 15:18:58 +0100 Message-ID: <39B8F56A.F8F77651@btinternet.com> Date: Fri, 08 Sep 2000 15:19:22 +0100 From: John Toon X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Please consider some cosmetic changes in boot messages References: <2762.968421829@axl.fw.uunet.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > I have a plan to revamp the way that the startup process's output is > presented and stored for later viewing. I need to chat to some folks > first about the best way to do this, first. Be patient, and look > forward to something interesting in 5.0-RELEASE. :-) > > Ciao, > Sheldon. On that subject, can you give me a rough projection as to when 5.0-RELEASE is likely to arrive? -- "I'm entirely unaccountable for any moments of sanity contained herein." :s/Windows/UNIX John Toon | j.a.toon@btinternet.com | "Sonnilon" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 0:26:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id D0C5337B423 for ; Sat, 9 Sep 2000 00:26:43 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13XezD-0005zq-00 for freebsd-current@freebsd.org; Sat, 09 Sep 2000 07:23:39 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e897OWX00878 for freebsd-current@freebsd.org; Sat, 9 Sep 2000 09:24:32 +0200 (CEST) (envelope-from wkb) Date: Sat, 9 Sep 2000 09:24:32 +0200 From: Wilko Bulte To: "FreeBSD_current, mailing list" Subject: loader build dies on alpha? Message-ID: <20000909092432.A858@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> alpha/loader ld -o loader.sym -M -e start -N -Ttext 0x2000c000 start.o setdef0.o main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o interp_forth.o setdef1.o vers.o -L/usr/lib -lstand /usr/obj/usr/src/sys/boot/alpha/loader/../libalpha/libalpha.a /usr/obj/usr/src/sys/boot/alpha/loader/../../ficl/libficl.a -lstand >/usr/obj/usr/src/sys/boot/alpha/loader/loader.list /usr/obj/usr/src/sys/boot/alpha/loader/../../ficl/libficl.a(loader.o): In function `ficlPnpdevices': loader.c(.text+0xa1c): undefined reference to `pnp_devices' loader.c(.text+0xa44): undefined reference to `pnp_devices' /usr/obj/usr/src/sys/boot/alpha/loader/../../ficl/libficl.a(loader.o): In function `ficlPnphandlers': loader.c(.text+0xab4): undefined reference to `pnphandlers' *** Error code 1 Stop in /usr/src/sys/boot/alpha/loader. *** Error code 1 Stop in /usr/src/sys/boot/alpha. *** Error code 1 Stop in /usr/src/sys/boot. This is a freshly supped current -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 1:52:23 2000 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 EF1D037B440 for ; Sat, 9 Sep 2000 01:52:19 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Sep 2000 09:51:24 +0100 (BST) Date: Sat, 9 Sep 2000 09:51:24 +0100 From: David Malone To: Julian Elischer Cc: current@freebsd.org Subject: Re: more on: Vmware (1.x) port broken in -current Message-ID: <20000909095124.A45853@walton.maths.tcd.ie> References: <20000908154320.J12231@fw.wintelcom.net> <39B9DABD.167EB0E7@elischer.org> <39B9DF6A.2781E494@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39B9DF6A.2781E494@elischer.org>; from julian@elischer.org on Fri, Sep 08, 2000 at 11:57:46PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote: > sh vmware.sh start > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec > format error > kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec > format error > > I have NO idea wha that means.. (how can a module I just compile > 30 seconds before be in the wrong format?) I thought this was the generic error that loading a module gave if anything unusual went wrong (like missing symbols and so on). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 2: 4:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from Den.BOFH.Halifax.NS.Ca (Den.BOFH.Halifax.ns.Ca [129.173.46.183]) by hub.freebsd.org (Postfix) with ESMTP id 237A037B505 for ; Sat, 9 Sep 2000 02:04:57 -0700 (PDT) Received: (from hume@localhost) by Den.BOFH.Halifax.NS.Ca (8.9.3+Sun/8.9.1) id GAA01899 for freebsd-current@freebsd.org; Sat, 9 Sep 2000 06:04:00 -0300 (ADT) From: Brandon Hume Message-Id: <200009090904.GAA01899@Den.BOFH.Halifax.NS.Ca> Subject: Re: SMPng CPU states In-Reply-To: <20000909111926.D5876@wantadilla.lemis.com> from Greg Lehey at "Sep 9, 2000 11:19:26 am" To: freebsd-current@freebsd.org Date: Sat, 9 Sep 2000 06:03:54 -0300 (ADT) X-Mailer: ELM [version 2.4ME+ PL42 (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 > FWIW, I've had no trouble running X on my development box. Well, the > monitor can only do 640x480, but that's not an OS issue. I was able to get X going initially... its when I attempt to make use of DRI that the box hangs, which may not be a problem that anyone can do anything about here, since the mga and drm .ko's come from the XFree-4 source. I can load the modules via kldload just fine, without trouble. Its when I actually try and launch into X with DRI enabled that doom befalls me. I'll have to do a bit more science with it. -- Brandon Hume - hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 3:17:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id 3A93137B506 for ; Sat, 9 Sep 2000 03:17:29 -0700 (PDT) Received: from [212.159.21.148] (helo=bladerunner) by mailhost.netbenefit.co.uk with smtp (NetBenefit 1.5) id 13XheT-0000RR-00 ; Sat, 09 Sep 2000 11:14:25 +0100 From: "Pierre Y. Dampure" To: "Brandon Hume" , Subject: RE: SMPng CPU states Date: Sat, 9 Sep 2000 11:14:26 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: <200009090904.GAA01899@Den.BOFH.Halifax.NS.Ca> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, it looks like VESA support broke after the SMPng commit. I used to run my VTYs in VESA_800x600 mode, but just after the commit it hung the machine (this is on a dual-processor system, with a Voodoo 5500). PYD -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Brandon Hume Sent: 09 September 2000 10:04 To: freebsd-current@freebsd.org Subject: Re: SMPng CPU states > FWIW, I've had no trouble running X on my development box. Well, the > monitor can only do 640x480, but that's not an OS issue. I was able to get X going initially... its when I attempt to make use of DRI that the box hangs, which may not be a problem that anyone can do anything about here, since the mga and drm .ko's come from the XFree-4 source. I can load the modules via kldload just fine, without trouble. Its when I actually try and launch into X with DRI enabled that doom befalls me. I'll have to do a bit more science with it. -- Brandon Hume - hume -> BOFH.Halifax.NS.Ca, http://WWW.BOFH.Halifax.NS.Ca/ 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 Sep 9 6:15:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id AA16B37B422 for ; Sat, 9 Sep 2000 06:15:26 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13XkTW-000IMj-00; Sat, 09 Sep 2000 15:15:18 +0200 Date: Sat, 9 Sep 2000 15:15:18 +0200 From: Neil Blakey-Milner To: John Toon Cc: freebsd-current@freebsd.org Subject: Re: Please consider some cosmetic changes in boot messages Message-ID: <20000909151518.A70536@mithrandr.moria.org> References: <2762.968421829@axl.fw.uunet.co.za> <39B8F56A.F8F77651@btinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39B8F56A.F8F77651@btinternet.com>; from j.a.toon@btinternet.com on Fri, Sep 08, 2000 at 03:19:22PM +0100 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 2000-09-08 (15:19), John Toon wrote: > > I have a plan to revamp the way that the startup process's output is > > presented and stored for later viewing. I need to chat to some folks > > first about the best way to do this, first. Be patient, and look > > forward to something interesting in 5.0-RELEASE. :-) > > On that subject, can you give me a rough projection as to when > 5.0-RELEASE is likely to arrive? FreeBSD 2.2.1 1997-04-xx [FBD] FreeBSD 3.0 1998-10-16 [FBD] FreeBSD 4.0 2000-03-13 [FBD] So we're talking 2001-07 to 2001-11, at a wild guess. We have lots of new developments, but also a much more streamlined system. It's anyone's guess when it'll be deemed stable and complete enough to roll. (and please don't quote me, since this is only my guess) Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 9: 1:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id BB97F37B422 for ; Sat, 9 Sep 2000 09:01:20 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA67927; Sat, 9 Sep 2000 11:59:54 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 9 Sep 2000 11:59:54 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Baldwin Cc: current@FreeBSD.org Subject: Re: Dirty buffers on reboot.. In-Reply-To: <200009081942.MAA57127@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Sep 2000, John Baldwin wrote: > Ok, an update on the dirty buffers on reboot: > > If you use the reboot command, you will get dirty buffers. If you use > 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a > workaround for now, use the shutdown command to reboot your box until we > can track this down. Um. Nope. :-) I only use shutdown -r now, and I still get dirty buffers. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 9: 6:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id F2FED37B423; Sat, 9 Sep 2000 09:06:54 -0700 (PDT) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.0/8.11.0) with ESMTP id e89G6rg93669; Sat, 9 Sep 2000 09:06:53 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <5.0.0.19.2.20000909090502.00a74d98@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.19 (Beta) Date: Sat, 09 Sep 2000 09:06:53 -0700 To: Robert Watson , John Baldwin From: Manfred Antar Subject: Re: Dirty buffers on reboot.. Cc: current@FreeBSD.ORG In-Reply-To: References: <200009081942.MAA57127@pike.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:59 AM 9/9/2000 -0400, Robert Watson wrote: >On Fri, 8 Sep 2000, John Baldwin wrote: > >> Ok, an update on the dirty buffers on reboot: >> >> If you use the reboot command, you will get dirty buffers. If you use >> 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a >> workaround for now, use the shutdown command to reboot your box until we >> can track this down. > >Um. Nope. :-) I only use shutdown -r now, and I still get dirty >buffers. I too only use "shutdown -r now" and still get dirty buffers. Tor Egge posted a patch and with the patch to kern_shutdown.c I no longer have the problem. Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 9:17:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2245B37B423; Sat, 9 Sep 2000 09:17:26 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id MAA68157; Sat, 9 Sep 2000 12:16:39 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 9 Sep 2000 12:16:39 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Brian Somers Cc: Wes Peters , Seigo Tanimura , current@FreeBSD.org, net@FreeBSD.org Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr In-Reply-To: <200009082350.e88Nogn57839@hak.lan.Awfulhak.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 Sat, 9 Sep 2000, Brian Somers wrote: > > Seigo Tanimura wrote: > > > > > > I have been suffering from this problem for almost 2 months. When I > > > remove a pcmcia ethernet card from my laptop PC, routed(8) announces > > > updated routing information by multicast, leading to a kernel > > > panic. > > > > Ejecting an interface configured up will do that. ifconfig the interface > > `down' and then `delete' before ejecting it. > > Interfaces in promiscuous mode will always result in a reboot. I > *usually* get away with ejecting an active card if it's not in > promiscuous mode. A while back I committed patches to use bpf_detach(), which elminated the struct ifnet pointer in the bpf described at detach time. This removed most of the panics I experience on ejecting pccards. This should be in 5.0-CURRENT and 4.1-STABLE. If you're still experiencing panics, we should track it down some more as presumably there is another reference (it could also be a race condition, or in-use mbuf during detach?) Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 10:25:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 2D65437B422 for ; Sat, 9 Sep 2000 10:25:29 -0700 (PDT) Received: (from steve@localhost) by virtual-voodoo.com (8.11.0.Beta3/8.11.0.Beta3) id e89HPSk70429 for freebsd-current@freebsd.org; Sat, 9 Sep 2000 12:25:28 -0500 (EST) Date: Sat, 9 Sep 2000 12:25:28 -0500 From: Steve Ames To: freebsd-current@freebsd.org Subject: fwd: [root: security check] Message-ID: <20000909122528.A88592@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > virtual-voodoo.com changes in mounted filesystems: > 6d5 > < /dev/ad1s1g /source ufs rw 0 2 > 8a8 > > /dev/ad1s1g /source ufs rw 0 2 Got this is this morning's security check. This doesn't really show a change. The actual change was from normal to soft-updates. Any way this can show what actually changed? 'mount -p' (which /etc/security uses) doesn't show things such as soft-updates. In fact I don't see a single mount option that does show everything... -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 10:32: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id 3C28B37B423 for ; Sat, 9 Sep 2000 10:32:00 -0700 (PDT) Received: (qmail 26771 invoked by uid 666); 9 Sep 2000 17:31:56 -0000 Received: from reggae-12-250.nv.iinet.net.au (HELO jules.elischer.org) (203.59.92.250) by mail.m.iinet.net.au with SMTP; 9 Sep 2000 17:31:56 -0000 Message-ID: <39BA7405.41C67EA6@elischer.org> Date: Sat, 09 Sep 2000 10:31:49 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: David Malone Cc: current@freebsd.org Subject: Re: more on: Vmware (1.x) port broken in -current References: <20000908154320.J12231@fw.wintelcom.net> <39B9DABD.167EB0E7@elischer.org> <39B9DF6A.2781E494@elischer.org> <20000909095124.A45853@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > > On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote: > > > sh vmware.sh start > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec > > format error > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec > > format error > > > > I have NO idea wha that means.. (how can a module I just compile > > 30 seconds before be in the wrong format?) > > I thought this was the generic error that loading a module gave if > anything unusual went wrong (like missing symbols and so on). I believe so too, but there is no clue as to what might be failing. > > David. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 10:34:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id 7C25537B42C for ; Sat, 9 Sep 2000 10:34:40 -0700 (PDT) Received: (qmail 27108 invoked by uid 666); 9 Sep 2000 17:34:38 -0000 Received: from reggae-12-250.nv.iinet.net.au (HELO jules.elischer.org) (203.59.92.250) by mail.m.iinet.net.au with SMTP; 9 Sep 2000 17:34:38 -0000 Message-ID: <39BA74A6.167EB0E7@elischer.org> Date: Sat, 09 Sep 2000 10:34:30 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: David Malone , current@freebsd.org Subject: Re: more on: Vmware (1.x) port broken in -current References: <20000908154320.J12231@fw.wintelcom.net> <39B9DABD.167EB0E7@elischer.org> <39B9DF6A.2781E494@elischer.org> <20000909095124.A45853@walton.maths.tcd.ie> <39BA7405.41C67EA6@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > David Malone wrote: > > > > On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote: > > > > > sh vmware.sh start > > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec > > > format error > > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec > > > format error > > > > > > I have NO idea wha that means.. (how can a module I just compile > > > 30 seconds before be in the wrong format?) > > > > I thought this was the generic error that loading a module gave if > > anything unusual went wrong (like missing symbols and so on). > > I believe so too, but there is no clue as to what might be failing. I just noticed... buried in the logs.... linux_ioctl_register_handler is the symbol not found. I wonder what it's been replaced with?  > > > > > David. > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Perth > v > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 10:55:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id E1A2137B43F for ; Sat, 9 Sep 2000 10:55:16 -0700 (PDT) Received: (qmail 29605 invoked by uid 666); 9 Sep 2000 17:55:13 -0000 Received: from reggae-12-250.nv.iinet.net.au (HELO jules.elischer.org) (203.59.92.250) by mail.m.iinet.net.au with SMTP; 9 Sep 2000 17:55:13 -0000 Message-ID: <39BA797B.446B9B3D@elischer.org> Date: Sat, 09 Sep 2000 10:55:07 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: David Malone , current@freebsd.org Subject: Re: more on: [kldload] Vmware (1.x) port broken in -current References: <20000908154320.J12231@fw.wintelcom.net> <39B9DABD.167EB0E7@elischer.org> <39B9DF6A.2781E494@elischer.org> <20000909095124.A45853@walton.maths.tcd.ie> <39BA7405.41C67EA6@elischer.org> <39BA74A6.167EB0E7@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Julian Elischer wrote: > > > > David Malone wrote: > > > > > > On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote: > > > > > > > sh vmware.sh start > > > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec > > > > format error > [...] > > I believe so too, but there is no clue as to what might be failing. > > I just noticed... buried in the logs.... > > linux_ioctl_register_handler is the symbol not found. > > I wonder what it's been replaced with? The plot thickens.. the linker is unable to find the symbol if linux is a module. it would appear that it is unable to link cross module symbols.. > >  > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 12:12:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id EFD3237B422 for ; Sat, 9 Sep 2000 12:12:38 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13Xopm-000ONl-00; Sat, 09 Sep 2000 18:54:34 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id SAA09125; Sat, 9 Sep 2000 18:54:34 +0100 (BST) (envelope-from ben) Date: Sat, 9 Sep 2000 18:54:34 +0100 From: Ben Smithurst To: Steve Ames Cc: freebsd-current@freebsd.org Subject: Re: fwd: [root: security check] Message-ID: <20000909185434.C77593@strontium.scientia.demon.co.uk> References: <20000909122528.A88592@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000909122528.A88592@virtual-voodoo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Ames wrote: >> virtual-voodoo.com changes in mounted filesystems: >> 6d5 >> < /dev/ad1s1g /source ufs rw 0 2 >> 8a8 >>> /dev/ad1s1g /source ufs rw 0 2 > > Got this is this morning's security check. This doesn't really > show a change. The actual change was from normal to soft-updates. > > Any way this can show what actually changed? 'mount -p' (which > /etc/security uses) doesn't show things such as soft-updates. In > fact I don't see a single mount option that does show everything... This is because the filesystem just moved in the mount list. I've seen this a few times. The fix is trivial, I think: --- security 2000/08/07 09:08:35 1.41 +++ security 2000/09/09 17:38:26 @@ -64,7 +64,7 @@ # Show changes in the way filesystems are mounted # [ -n "$ignore" ] && cmd="egrep -v ${ignore#|}" || cmd=cat -if mount -p | $cmd > $TMP; then +if mount -p | $cmd | sort > $TMP; then if [ ! -f $LOG/mount.today ]; then separator echo "no $LOG/mount.today" -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 12:12:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 00B1B37B42C for ; Sat, 9 Sep 2000 12:12:43 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13Xpmf-000OPA-00 for current@FreeBSD.org; Sat, 09 Sep 2000 19:55:25 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id TAA35279 for current@FreeBSD.org; Sat, 9 Sep 2000 19:55:25 +0100 (BST) (envelope-from ben) Date: Sat, 9 Sep 2000 19:55:25 +0100 From: Ben Smithurst To: current@FreeBSD.org Subject: page fault in sched_ithd Message-ID: <20000909195525.E77593@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A kernel from the latest sources gets a page fault in sched_ithd. DDB says: Stopped at: sched_ithd+0x3c: movl $0x01,0x14(%edi) Any ideas what's wrong? I'll try to get a serial console working at some point so hopefully I can get some more useful information. Here's the kernel config for that machine... ## $BCPS: conf/kern/LITHIUM,v 1.32 2000/08/27 17:02:20 ben Exp $ machine i386 cpu I486_CPU ident LITHIUM maxusers 16 makeoptions DEBUG=-g options ATA_STATIC_ID options COMPAT_43 options DDB options DEVFS options FFS options FFS_ROOT options INET options INET6 options INVARIANTS options INVARIANT_SUPPORT options KTRACE options P1003_1B options SOFTUPDATES options SYSVSHM options UCONSOLE options _KPOSIX_PRIORITY_SCHEDULING device ata device atadisk device atkbd device atkbdc 1 device bpf device ep device ether device fdc device isa device loop device npx device pty device sc 1 device sio device splash device vga device vn 4 -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 12:41:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 33E8837B43F; Sat, 9 Sep 2000 12:41:24 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13WTsX-0003I6-00; Tue, 05 Sep 2000 19:19:53 -0600 Message-ID: <39B59BB9.22C4BDFE@softweyr.com> Date: Tue, 05 Sep 2000 19:19:53 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Seigo Tanimura Cc: current@freebsd.org, net@freebsd.org Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr References: <14772.34738.630468.85559N@rina> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote: > > In ip_output(), imo->imo_multicast_ifp points to the removed > interface, which is passed to IN_LOOKUP_MULTI() to cause a panic. This > problem also occurs when we attempt to delete a multicast address from > a removed interface. if_delmulti() derefers an ifp to the removed > interface, ending up with a panic. The problem does not occur for > unicast. > > http://people.FreeBSD.org/~tanimura/patches/mcastif.diff.gz is a > workround patch. The idea is to track all of the active ifps, confirm > an ifp to be active prior to dereferencing it, and free orphaned > ifmultiaddrs attached to a removed ifp. It would be much more elegant > if we could clean up the multicast information related to a removed > interface, though. Warner Losh pointed out to me: > Tanimura-san did contribute patches. This problem isn't a race at the > eject, but rather the network layer incompletely cleaning up after a > device has gone away. This is, of course, exactly the problem you're looking at. There are several of these cached ifp's hanging around, all causing problems. Robert Watson and I had a nice discussion about how to approach that problem a while back. I've since gotten busy and forgotten about it, as has he (apparently). The quick (-ish) fix I came up with is to double all those cache ifp's all over the code, and always check the first pointer for a null reference before diving off through it. The disadvantage is the check and dereference on every access, the advantage is being able to nullify one pointer in the interface take-down and automagically have all the cached references die. You would leak a single pointer for every interface detach, unless you did reference counting or something like that. The full solution would be to implement ifs a full objects, and to always check the state of the interface before trying to exercise an associated function. It's an ugly problem with no real simple solutions (in C). -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 12:41:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 806C937B506; Sat, 9 Sep 2000 12:41:26 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13WS4m-0003Gf-00; Tue, 05 Sep 2000 17:24:24 -0600 Message-ID: <39B580A8.CE59B5CF@softweyr.com> Date: Tue, 05 Sep 2000 17:24:24 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Seigo Tanimura , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: the ifp to a removed pcmcia ethernet card is left in struct ip_moptions and struct ifmultiaddr References: <39B51375.4DE4C6FA@softweyr.com> <39B48F1E.4C193F79@softweyr.com> <14772.34738.630468.85559N@rina> <200009050609.AAA58464@harmony.village.org> <200009051535.JAA60822@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 <39B51375.4DE4C6FA@softweyr.com> Wes Peters writes: > : state the code is in now, and if someone wants it to be better, we await > : their patches. As always. ;^) > > Tanimura-san did contribute patches. This problem isn't a race at the > eject, but rather the network layer incompletely cleaning up after a > device has gone away. Robert Watson and I had a nice discussion about how to approach that problem a while back. I've since gotten busy and forgotten about it, as has he (apparently). The quick (-ish) fix I came up with is to double all those cache ifp's all over the code, and always check the first pointer for a null reference before diving off through it. The disadvantage is the check and dereference on every access, the advantage is being able to nullify one pointer in the interface take-down and automagically have all the cached references die. You would leak a single pointer for every interface detach, unless you did reference counting or something like that. The full solution would be to implement reference counting in the if objects, and to always check the state of the interface before trying to exercise an associated function. It's an ugly problem with no real simple solutions (in C). -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 13:12:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id E6A9937B423 for ; Sat, 9 Sep 2000 13:12:07 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13XqtI-000OT0-00 for current@FreeBSD.org; Sat, 09 Sep 2000 21:06:20 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id VAA36100 for current@FreeBSD.org; Sat, 9 Sep 2000 21:06:19 +0100 (BST) (envelope-from ben) Date: Sat, 9 Sep 2000 21:06:19 +0100 From: Ben Smithurst To: current@FreeBSD.org Subject: Re: page fault in sched_ithd Message-ID: <20000909210619.F77593@strontium.scientia.demon.co.uk> References: <20000909195525.E77593@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000909195525.E77593@strontium.scientia.demon.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Ben Smithurst wrote: > A kernel from the latest sources gets a page fault in sched_ithd. DDB says: > > Stopped at: sched_ithd+0x3c: movl $0x01,0x14(%edi) > > Any ideas what's wrong? After poking around a bit with remote GDB, this seems to be caused by a stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. The attached rather crude patch has "fixed" the problem for now, but does anyone have any suggestions for a real fix? -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ithread.diff" Index: ithread.c =================================================================== RCS file: /usr/cvs/src/sys/i386/isa/ithread.c,v retrieving revision 1.1 diff -u -r1.1 ithread.c --- ithread.c 2000/09/07 01:32:48 1.1 +++ ithread.c 2000/09/09 19:58:46 @@ -144,6 +144,9 @@ } #endif + if (ir == NULL) + return; + /* * Set it_need so that if the thread is already running but close * to done, it will do another go-round. Then get the sched lock --sm4nu43k4a2Rpi4c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 14:22:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 6F46A37B422 for ; Sat, 9 Sep 2000 14:22:15 -0700 (PDT) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA66573 for ; Sat, 9 Sep 2000 14:22:15 -0700 (PDT) Date: Sat, 9 Sep 2000 14:22:14 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: oddness with new bootblock sources. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG with newly CVSup'd sources (I cannot compile the bootblocks..) (also with everything checked out to PRE_SMPNG) It get's the following error: ===> i386/loader cc -nostdlib -static -Ttext 0x0 -o loader.sym /usr/obj/usr/src/sys/boot/i386/loa der/../btx/lib/crt0.o main.o conf.o bcache.o boot.o commands.o console.o devopen .o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o isapnp.o pnp.o interp_forth.o vers.o /usr/obj/usr/src/sys/boo t/i386/loader/../../ficl/libficl.a /usr/obj/usr/src/sys/boot/i386/loader/../libi 386/libi386.a /usr/obj/usr/src/sys/boot/i386/loader/../../../../lib/libstand/lib stand.a /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In function ` pxe_enable': pxe.o(.text+0x552): undefined reference to `nfs_root_node' *** Error code 1 Stop in /usr/src/sys/boot/i386/loader. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. any suggestions gratefully accepted, as teh UPDATING file says we should recompile this..... (yes I deleted /sys/boot and re-checked it out) Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 14:40:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from c3-dbn-102.dial-up.net (c3-dbn-102.dial-up.net [196.33.200.102]) by hub.freebsd.org (Postfix) with ESMTP id D40CC37B422 for ; Sat, 9 Sep 2000 14:40:48 -0700 (PDT) Received: (from rnordier@localhost) by c3-dbn-102.dial-up.net (8.8.7/8.6.12) id XAA13372; Sat, 9 Sep 2000 23:39:50 +0200 (SAST) From: Robert Nordier Message-Id: <200009092139.XAA13372@c3-dbn-102.dial-up.net> Subject: Re: oddness with new bootblock sources. In-Reply-To: "from Julian Elischer at Sep 9, 2000 02:22:14 pm" To: Julian Elischer Date: Sat, 9 Sep 2000 23:39:47 +0200 (SAST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > with newly CVSup'd sources (I cannot compile the bootblocks..) > (also with everything checked out to PRE_SMPNG) > > It get's the following error: > /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In > function ` > pxe_enable': > pxe.o(.text+0x552): undefined reference to `nfs_root_node' You need to build and install libstand first. Robert Nordier rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 14:57:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 301E437B423 for ; Sat, 9 Sep 2000 14:57:30 -0700 (PDT) Received: from jules.elischer.org (reggae-12-161.nv.iinet.net.au [203.59.92.161]) by urban.iinet.net.au (8.8.7/8.8.7) with SMTP id FAA15831; Sun, 10 Sep 2000 05:57:06 +0800 Message-ID: <39BAB22B.167EB0E7@elischer.org> Date: Sat, 09 Sep 2000 14:56:59 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Robert Nordier Cc: current@FreeBSD.ORG Subject: Re: oddness with new bootblock sources. References: <200009092139.XAA13372@c3-dbn-102.dial-up.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote: > > Julian Elischer wrote: > > > with newly CVSup'd sources (I cannot compile the bootblocks..) > > (also with everything checked out to PRE_SMPNG) > > > > It get's the following error: > > > /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In > > function ` > > pxe_enable': > > pxe.o(.text+0x552): undefined reference to `nfs_root_node' > > You need to build and install libstand first. I think this should go in UPDATING > > Robert Nordier > > rnordier@FreeBSD.org -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 15:16:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from c3-dbn-102.dial-up.net (c3-dbn-102.dial-up.net [196.33.200.102]) by hub.freebsd.org (Postfix) with ESMTP id 451D537B423; Sat, 9 Sep 2000 15:16:19 -0700 (PDT) Received: (from rnordier@localhost) by c3-dbn-102.dial-up.net (8.8.7/8.6.12) id AAA14138; Sun, 10 Sep 2000 00:15:38 +0200 (SAST) From: Robert Nordier Message-Id: <200009092215.AAA14138@c3-dbn-102.dial-up.net> Subject: Re: oddness with new bootblock sources. In-Reply-To: <39BAB22B.167EB0E7@elischer.org> "from Julian Elischer at Sep 9, 2000 02:56:59 pm" To: Julian Elischer Date: Sun, 10 Sep 2000 00:15:36 +0200 (SAST) Cc: imp@FreeBSD.org, current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > Robert Nordier wrote: > > > > Julian Elischer wrote: > > > > > with newly CVSup'd sources (I cannot compile the bootblocks..) > > > (also with everything checked out to PRE_SMPNG) > > > > > > It get's the following error: > > > > > /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In > > > function ` > > > pxe_enable': > > > pxe.o(.text+0x552): undefined reference to `nfs_root_node' > > > > You need to build and install libstand first. > > I think this should go in UPDATING Maybe so. I've cc-ed Warner. Robert Nordier rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 15:36: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 8B01B37B42C for ; Sat, 9 Sep 2000 15:36:02 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA05935; Sat, 9 Sep 2000 15:35:09 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009092235.PAA05935@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: Robert Nordier , current@FreeBSD.ORG Subject: Re: oddness with new bootblock sources. In-reply-to: Your message of "Sat, 09 Sep 2000 14:56:59 PDT." <39BAB22B.167EB0E7@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Sep 2000 15:35:09 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Robert Nordier wrote: > > > > Julian Elischer wrote: > > > > > with newly CVSup'd sources (I cannot compile the bootblocks..) > > > (also with everything checked out to PRE_SMPNG) > > > > > > It get's the following error: > > > > > /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In > > > function ` > > > pxe_enable': > > > pxe.o(.text+0x552): undefined reference to `nfs_root_node' > > > > You need to build and install libstand first. > > I think this should go in UPDATING No. You should have built the world, not just the loader. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 15:47:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id C69C137B423; Sat, 9 Sep 2000 15:47:26 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA06004; Sat, 9 Sep 2000 15:46:48 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009092246.PAA06004@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Julian Elischer , Robert Nordier , current@freebsd.org Subject: Re: oddness with new bootblock sources. In-reply-to: Your message of "Sat, 09 Sep 2000 15:35:09 PDT." <200009092235.PAA05935@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Sep 2000 15:46:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Robert Nordier wrote: > > > > > > Julian Elischer wrote: > > > > > > > with newly CVSup'd sources (I cannot compile the bootblocks..) > > > > (also with everything checked out to PRE_SMPNG) > > > > > > > > It get's the following error: > > > > > > > /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In > > > > function ` > > > > pxe_enable': > > > > pxe.o(.text+0x552): undefined reference to `nfs_root_node' > > > > > > You need to build and install libstand first. > > > > I think this should go in UPDATING > > No. You should have built the world, not just the loader. Sorry, I should have been more clear here. There was a window a few hours wide in which it was possible that the world might not build if the loader was built before libstand was installed. This is no longer a problem. A standalone build of the loader has always been dependant on the installed version of libstand. This doesn't qualify as UPDATING fodder. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 15:58:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id D1D7137B422; Sat, 9 Sep 2000 15:58:30 -0700 (PDT) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e89MwSr19880; Sun, 10 Sep 2000 07:58:28 +0900 (JST) (envelope-from iwasaki@jp.freebsd.org) To: nik@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-doc@freebsd.org Subject: Re: CFR: acpi userland manpages In-Reply-To: <20000908112356.B31852@canyon.nothing-going-on.org> References: <20000901000931V.iwasaki@jp.FreeBSD.org> <20000908112356.B31852@canyon.nothing-going-on.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000910075826F.iwasaki@jp.freebsd.org> Date: Sun, 10 Sep 2000 07:58:26 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The draft version of manpages are available at > > http://people.FreeBSD.org/~iwasaki/acpi/acpidump.8 > > http://people.FreeBSD.org/~iwasaki/acpi/amldb.8 > > I've just found the time to give them a quick once over, and I'd have no > problem with them going in as they are. There are some grammar changes, > and possibly terminology changes that might be appropriate, but I haven't > got the time to enumerate them all at the moment, and I'm sure the wider > community can make suggestions as time goes on. Thanks. I got mails from kind guys including some grammar changes, but my main NotePC has a problem with keyboard and it's in repairing (yes, revised version of manpages are in that PC...) :-< > Sheldon can probably render an opinion on their usage of the macros. OK, I'm looking forward to see it :-) Thanks again To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 22:14:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id 9F60737B424 for ; Sat, 9 Sep 2000 22:14:42 -0700 (PDT) Received: (qmail 17113 invoked by uid 666); 10 Sep 2000 05:14:39 -0000 Received: from reggae-34-121.nv.iinet.net.au (HELO jules.elischer.org) (203.59.167.121) by mail.m.iinet.net.au with SMTP; 10 Sep 2000 05:14:39 -0000 Message-ID: <39BB18BE.167EB0E7@elischer.org> Date: Sat, 09 Sep 2000 22:14:38 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: lack of block devices and VMWARE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone managed to fake out vmware WRT block devices? it REQUIRES a block device to be able to read raw disks, and in fact, if you manage to divert the read to raw devices, the performance SUCKS because they don't cache. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 22:18:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id 06D7B37B424 for ; Sat, 9 Sep 2000 22:18:19 -0700 (PDT) Received: (qmail 17334 invoked by uid 666); 10 Sep 2000 05:18:16 -0000 Received: from reggae-34-121.nv.iinet.net.au (HELO jules.elischer.org) (203.59.167.121) by mail.m.iinet.net.au with SMTP; 10 Sep 2000 05:18:16 -0000 Message-ID: <39BB1997.2781E494@elischer.org> Date: Sat, 09 Sep 2000 22:18:15 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith Cc: Robert Nordier , current@freebsd.org Subject: Re: oddness with new bootblock sources. References: <200009092246.PAA06004@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > Robert Nordier wrote: > > > > > > > > Julian Elischer wrote: > > > > > > > > > with newly CVSup'd sources (I cannot compile the bootblocks..) > > > > > (also with everything checked out to PRE_SMPNG) > > > > > > > > > > It get's the following error: > > > > > > > > > /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In > > > > > function ` > > > > > pxe_enable': > > > > > pxe.o(.text+0x552): undefined reference to `nfs_root_node' > > > > > > > > You need to build and install libstand first. > > > > > > I think this should go in UPDATING > > > > No. You should have built the world, not just the loader. it was a neccesary step for me to just do teh boot related stuff before I could do make world (special local conditions). The situation is now fine since I was told about libstand. > > Sorry, I should have been more clear here. There was a window a few > hours wide in which it was possible that the world might not build if the > loader was built before libstand was installed. This is no longer a > problem. > > A standalone build of the loader has always been dependant on the > installed version of libstand. This doesn't qualify as > UPDATING fodder. Personally I think it could have rated a few words on the end of the annoncement that was already there that told you to make new bootblocks. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 22:23:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-025.telepath.com [216.14.0.25]) by hub.freebsd.org (Postfix) with SMTP id 0A79837B423 for ; Sat, 9 Sep 2000 22:23:53 -0700 (PDT) Received: (qmail 21250 invoked by uid 100); 10 Sep 2000 05:23:15 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14779.6851.88867.359611@guru.mired.org> Date: Sun, 10 Sep 2000 00:23:15 -0500 (CDT) To: Ben Smithurst Cc: current@FreeBSD.ORG Subject: Re: page fault in sched_ithd In-Reply-To: <20000909210619.F77593@strontium.scientia.demon.co.uk> References: <20000909195525.E77593@strontium.scientia.demon.co.uk> <20000909210619.F77593@strontium.scientia.demon.co.uk> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst writes: > After poking around a bit with remote GDB, this seems to be caused by a > stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. > > The attached rather crude patch has "fixed" the problem for now, but > does anyone have any suggestions for a real fix? Isn't a stray IRQ a hardware glitch? If so, I'd say that logging it and then ignoring it would be the right thing. ; Sat, 9 Sep 2000 22:50:23 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.net ([24.201.203.136]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G0N00G8ZPJSPD@falla.videotron.net> for current@freebsd.org; Sun, 10 Sep 2000 01:50:16 -0400 (EDT) Date: Sun, 10 Sep 2000 01:53:40 -0400 (EDT) From: Bosko Milekic Subject: Re: page fault in sched_ithd In-reply-to: <14779.6851.88867.359611@guru.mired.org> X-Sender: bmilekic@jehovah.technokratis.com To: current@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I catch this page fault (described in topic) following an: `ifconfig de0 down' Unfortunately, I don't have much more information to provide for now. I'm in the middle of debugging something else. More info can be provided on request (let me know if you want to look at it and cannot reproduce it). Sources of last friday (evening). On Sun, 10 Sep 2000, Mike Meyer wrote: > Ben Smithurst writes: > > After poking around a bit with remote GDB, this seems to be caused by a > > stray IRQ 7, since irq == 7, ir == ithds[irq] == NULL, ir->foo == BOOM. > > > > The attached rather crude patch has "fixed" the problem for now, but > > does anyone have any suggestions for a real fix? > > Isn't a stray IRQ a hardware glitch? If so, I'd say that logging it > and then ignoring it would be the right thing. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 23: 8:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 5FC8137B423; Sat, 9 Sep 2000 23:08:30 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.net ([24.201.203.136]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G0N00G0AQE40V@field.videotron.net>; Sun, 10 Sep 2000 02:08:28 -0400 (EDT) Date: Sun, 10 Sep 2000 02:11:52 -0400 (EDT) From: Bosko Milekic Subject: mbuf system with mutexes X-Sender: bmilekic@jehovah.technokratis.com To: current@freebsd.org Cc: net@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 For those interested, I have a preliminary patch that will add mutex locking in the mbuf subsystem and get rid of the splimp()s. It also fixes some race conditions previously existing and in relation to tsleep() (i.e. the wait routines). The patch is rough and early, but watch the same space for updates (soon), and please, if you have an SMP machine, give it a whirl (because I don't!). http://www.technokratis.com/code/mbuf/mbuf_mtx.patch Please note that this will only work for i386 for now. I have yet to clean up the initialization code such that it will run decently and as advertised. :-) Also, I plan to tackle as follows, and not necessarily in order: (roughly) a* sendfile(2) stuff SMP-izing b* cleanup mbuf_mtx, fix and tweak c* make sure m_reclaim is okay d* test for exhaustion e* test on real SMP machine f* make sure callers don't hold mutexes when calling with M_WAIT g* make sure the kmem_malloc() stuff has Giant h* atomic (real atomic) manipulation of mbstat * etc... Suggestions, as usual, are always welcome. Please don't consider anything in the above code final, it's the first and very early version. Finally, I'm trying to do this as closly as possible with Alfred's work, so Alfred, maybe you can also glance at point (f) above as well... :-) Cheers, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 9 23:47:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 6B2D837B423; Sat, 9 Sep 2000 23:47:14 -0700 (PDT) Received: (from pete@localhost) by ns.altadena.net (8.11.0/8.8.8) id e8A6l4N26872; Sat, 9 Sep 2000 23:47:04 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200009100647.e8A6l4N26872@ns.altadena.net> Subject: MSDOSFS oddity To: current@freebsd.org Date: Sat, 9 Sep 2000 23:47:04 -0700 (PDT) Cc: fs@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably not many -current users use msdosfs; I use it only for the occasional floppy (extremely rare now) and the flash cards from my electronic cameras. On trying to mount one of these today, I ran into a problem (apparently in the msdosfs_vnops change of Sept 2, since a system made the previous Wed didn't have this problem) where any msdosfs system (I mount it 'ro,longnames,noauto') comes mounted with perms d--------- (so noone but root can reference it) and names translated to lower case. I've come to count on that last not happening (besides if you wanted win95 behavior it would leave the first letter capital). The perms thing is a real problem. The name translation could be too (It is for me since I sort files together with previous reads so the change will really mess things up.) (unless longnames implies uc-lc conversion; this really shouldn't happen since win95 actually supports mixed case correctly (though doesn't default to generating it). I see no new mount option to control the name conversion. Hopefully there is no new attempt at text file conversion built into the filesystem too since there is no real way to tell what is a text file or not... On trying this with 'shortnames', it still has both problems... I presume that my flashcard doesn't have a win95 directory structure present but don't really know. It only works right if the camera formats it :-) I can get around it for now but as with basename(1), gratuitous changes to long-standing behavior is vexing at best. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message