From owner-freebsd-alpha Sun Mar 11 8:30:56 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id BA6E337B71A for ; Sun, 11 Mar 2001 08:30:40 -0800 (PST) (envelope-from naddy@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14c8jw-0005z5-00; Sun, 11 Mar 2001 17:30:40 +0100 Received: (from naddy@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f2BFh8c05322 for freebsd-alpha@freebsd.org; Sun, 11 Mar 2001 16:43:08 +0100 (CET) (envelope-from naddy) Date: Sun, 11 Mar 2001 16:43:08 +0100 From: Christian Weisgerber To: freebsd-alpha@freebsd.org Subject: Unaligned access in vfs_object_create() Message-ID: <20010311164308.A3774@kemoauc.mips.inka.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Top of the tree, ca. March 10. My custom kernel suffers an unaligned access fault in vfs_object_create() at the end of kernel startup--presumably when attempting to mount the root or devfs filesystem. The GENERIC kernel does not have this problem. Attached: - boot log - kernel configuration -- Christian "naddy" Weisgerber naddy@mips.inka.de --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="session.log" ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.f3.f2.f1.f0. ef.b0.b1.b2.b3.ee.ed.ec.f4.eb.ea.e9.e8.e7. Digital AlphaPC 164 500 MHz Console V5.5-1, Jul 14 1999 12:37:45 CPU 0 booting (boot dka0.0.0.7.0 -flags a) block 0 of dka0.0.0.7.0 is a valid boot block reading 15 blocks from dka0.0.0.7.0 bootstrap code read in base = 180000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 172000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader *** no timer interrupts on CPU 0 *** Console: SRM firmware console VMS PAL rev: 0x1000900010115 OSF PAL rev: 0x1000800020117 Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 1.1 (naddy@kemoauc.mips.inka.de, Sun Mar 4 22:40:00 CET 2001) Memory: 262144 k Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x254df8+0x35d12 syms=[0x8+0x38dc0+0x8+0x29b8e] /boot/kernel/miibus.ko text=0x14b18 data=0x1a10+0x98 syms=[0x8+0x2550+0x8+0x197a] /boot/kernel/if_xl.ko text=0xc4e0 data=0xbf0+0x20 syms=[0x8+0x12a8+0x8+0xad8] /boot/kernel/snd_pcm.ko text=0x12298 data=0x28f0+0x1020 syms=[0x8+0x2c40+0x8+0x1d30] /boot/kernel/snd_sbc.ko text=0x3638 data=0x728+0x8 syms=[0x8+0xba0+0x8+0x6ec] /boot/kernel/snd_sb16.ko text=0x3988 data=0x780+0x8 syms=[0x8+0xe10+0x8+0x7f1] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Entering kernel at 0xfffffc0000329560... sio1: gdb debugging port Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sun Mar 11 04:51:20 CET 2001 naddy@kemoauc.mips.inka.de:/home/obj/usr/src/sys/KEMOAUC EB164 Digital AlphaPC 164 500 MHz, 500MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x1000800020117 real memory = 265904128 (259672K bytes) avail memory = 252952576 (247024K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000694000. Preloaded elf module "miibus.ko" at 0xfffffc00006940c0. Preloaded elf module "if_xl.ko" at 0xfffffc0000694188. Preloaded elf module "snd_pcm.ko" at 0xfffffc0000694250. Preloaded elf module "snd_sbc.ko" at 0xfffffc0000694318. Preloaded elf module "snd_sb16.ko" at 0xfffffc00006943e0. cia0: <2117x Core Logic chipset> cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x10200-0x1023f irq 2 at device 5.0 on pci0 xl0: interrupting at CIA irq 2 xl0: Ethernet address: 00:60:97:4b:1a:b9 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sym0: <810a> port 0x10100-0x101ff mem 0x82835100-0x828351ff irq 0 at device 6.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: interrupting at CIA irq 0 sym1: <875> port 0x10000-0x100ff mem 0x82834000-0x82834fff,0x82835000-0x828350ff irq 1 at device 7.0 on pci0 sym1: Tekram NVRAM, ID 7, Fast-20, SE, parity checking sym1: interrupting at CIA irq 1 isab0: at device 8.0 on pci0 isa0: on isab0 pci0: at 9.0 (no driver attached) pci0: at 11.0 (no driver attached) sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 mcclock0: at port 0x70-0x71 on isa0 ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Polled port ppc0: interrupting at ISA irq 7 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at ISA irq 3 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: interrupting at ISA irq 5 pcm0: on sbc0 Timecounter "i8254" frequency 1193182 Hz Timecounter "alpha" frequency 499995782 Hz Waiting 10 seconds for SCSI devices to settle sa0 at sym0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) Mounting root from ufs:/dev/da0a da1 at sym1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4146MB (8491920 512 byte sectors: 255H 63S/T 528C) da0 at sym1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) fatal kernel trap: trap entry = 0x4 (unaligned access fault) a0 = 0xe53c3c3e9f6ec9e1 a1 = 0x29 a2 = 0x1b pc = 0xfffffc00003fadd8 ra = 0xfffffc00003f6024 curproc = 0xfffffe0008a41be0 pid = 1, comm = init Stopped at vfs_object_create+0x38: jsr ra,(pv),vfs_object_create+0x3c db> trace vfs_object_create() at vfs_object_create+0x38 getnewvnode() at getnewvnode+0x564 devfs_allocv() at devfs_allocv+0xe0 devfs_root() at devfs_root+0x38 devfs_mount() at devfs_mount+0xf0 vfs_mount() at vfs_mount+0x910 mount() at mount+0xd8 syscall() at syscall+0x3f4 XentSys1() at XentSys1+0x10 db> --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=KEMOAUC # # KEMOAUC -- FreeBSD 5.0-CURRENT (alpha) # # $FreeBSD: src/sys/alpha/conf/GENERIC,v 1.107 2001/02/04 15:35:08 peter Exp $ # $Id: KEMOAUC,v 1.8 2001/03/05 21:16:53 naddy Exp $ machine alpha cpu EV5 ident KEMOAUC maxusers 32 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INCLUDE_CONFIG_FILE # Include this file in kernel # Platforms supported options DEC_EB164 # EB164, PC164, PC164LX, PC164SX options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options DEVFS #Device Filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=10000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) syscall trace support options DDB #Enable the kernel debugger options DDB_UNATTENDED #Don't drop into DDB for a panic options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING # Standard busses device isa device pci # Floppy drives device fdc # SCSI Controllers device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') # 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 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 options SC_ALT_MOUSE_IMAGE # simplified mouse cursor in text mode options SC_DISABLE_REBOOT # disable reboot key sequence # real time clock device mcclock # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device device loop # Network loopback device ether # Ethernet support 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 --r5Pyd7+fXNt84Ff3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 11 13:16:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id CD06637B718 for ; Sun, 11 Mar 2001 13:16:11 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id IAA01204 for ; Mon, 12 Mar 2001 08:16:08 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K13P9MKVE8P0963G@cim.alcatel.com.au> for freebsd-alpha@freebsd.org; Mon, 12 Mar 2001 08:16:02 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f2BLG5s11309 for freebsd-alpha@freebsd.org; Mon, 12 Mar 2001 08:16:05 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Mon, 12 Mar 2001 08:16:05 +1100 From: Peter Jeremy Subject: EISA support for AS2100 ("Sable") To: freebsd-alpha@freebsd.org Mail-Followup-To: freebsd-alpha@freebsd.org Message-id: <20010312081605.A11209@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have been offered an AS2100 with a collection of EISA cards, but I note that HARDWARE.TXT states "EISA slots are currently unsupported" for Sable. Is anyone currently working on this and/or can anyone tell me how much effort would be involved in supporting the EISA bus? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Mar 11 14:24:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 848F037B766; Sun, 11 Mar 2001 14:24:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA31810; Sun, 11 Mar 2001 14:24:42 -0800 Date: Sun, 11 Mar 2001 14:24:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "David O'Brien" Cc: alpha@FreeBSD.org Subject: 4100 confirmation for David.. In-Reply-To: <20010310160030.D18227@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'll make gzip'd dd image of my 2GB root disk and send it to you (send me a postal mail address if you aren't gonna be in SF any time soon) This is a 2 Host rawhide, and here also is the rear view of cards: top isp0 (differential Qlogic 1020) (to 3 disks) ---- ---- de0 (some generic tulip 100-BaseT) isp1 (Qlogic 2200) ---- ---- ---- Here's the screenlog of booting. This is for a March 9th buildworld/installworld/installkernel. The -current is da2. The onboard symbios has a cdrom and tape. FreeBSD 5.0-CURRENT #8: Fri Mar 9 14:37:29 PST 2001 mjacob@nellie.feral.com:/usr/obj/usr/src/sys/GENERIC AlphaServer 4100 AlphaServer 4100 5/533 4MB, 531MHz 8192 byte page size, 4 processors. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x4000100020117 real memory = 1608482816 (1570784K bytes) Physical memory chunk(s): 0x0085c000 - 0x5ffeffff, 1601781760 bytes (195530 pages) avail memory = 1559478272 (1522928K bytes) Preloaded elf kernel "kernel" at 0xfffffc000083c000. Preloaded elf module "ispfw.ko" at 0xfffffc000083c0c0. This message will repeat for the next 20 seconds WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in WARNING: size of kinfo_proc (912) should be 920!!! The kinfo_proc structure was changed incorrectly in null: random: mem: mcbus0: pcib0: at mcbus0 gid 7 mid 5 pcib0: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 pci0: physical bus=0 map[10]: type 4, range 32, base 01fffd00, size 8, enabled map[14]: type 1, range 32, base 07feee00, size 8, enabled found-> vendor=0x1000, dev=0x0001, revid=0x02 bus=0, slot=1, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=4 map[10]: type 4, range 32, base 01fffe00, size 7, enabled map[14]: type 1, range 32, base 07feef00, size 7, enabled found-> vendor=0x1011, dev=0x0009, revid=0x12 bus=0, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=8 map[10]: type 4, range 32, base 01ffff00, size 8, enabled map[14]: type 1, range 32, base 07fef000, size 12, enabled found-> vendor=0x1077, dev=0x1020, revid=0x05 bus=0, slot=5, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=20 pci0: on pcib0 sym0: <810> port 0x1fffd00-0x1fffdff mem 0x7feee00-0x7feeeff irq 4 at device 1.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using NCR-generic firmware. sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 00/00/00/00/00/00 sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 03/c8/00/00/08/00 sym0: Delay (GEN=11): 268 msec, 33165 KHz sym0: Delay (GEN=11): 283 msec, 31407 KHz sym0: Delay (GEN=11): 284 msec, 31296 KHz sym0: interrupting at IRQ 0x10 intA (vec 0xb40) de0: port 0x1fffe00-0x1fffe7f mem 0x7feef00-0x7feef7f irq 8 at device 2.0 on pci0 de0: interrupting at IRQ 0x0 intA (vec 0xb80) de0: DEC DE500-XA 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:f8:01:8b:d7 de0: enabling Full Duplex 100baseTX port bpf: de0 attached Qlogic ISP Driver, FreeBSD Version 5.6, Core Version 2.1 isp0: port 0x1ffff00-0x1ffffff mem 0x7fef000-0x7feffff irq 20 at device 5.0 on pci0 isp0: using Memory space register mapping isp0: interrupting at IRQ 0xc intA (vec 0xc40) isp0: Differential Mode isp0: Ultra Mode Capable isp0: Board Revision 1040B, loaded F/W Revision 4.66.0 isp0: Last F/W revision was 5.57.1 isp0: 243 max I/O commands supported isp0: Initiator ID is 7 on Channel 0 pcib1: at mcbus0 gid 7 mid 4 pcib1: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2 Attaching Real Console pci1: physical bus=0 found-> vendor=0x8086, dev=0x0482, revid=0x15 bus=0, slot=1, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 illegal PCI extended capability offset 256 map[10]: type 4, range 32, base 01ffff00, size 8, enabled map[14]: type 1, range 32, base 07fdf000, size 12, enabled found-> vendor=0x1077, dev=0x2200, revid=0x05 bus=0, slot=5, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=20 pci1: on pcib1 eisab0: at device 1.0 on pci1 isa0: on eisab0 isp1: port 0x1ffff00-0x1ffffff mem 0x7fdf000-0x7fdffff irq 20 at device 5.0 on pci1 isp1: using Memory space register mapping isp1: interrupting at IRQ 0xc intA (vec 0xa40) isp1: Board Revision 2200, loaded F/W Revision 2.1.26 isp1: Installed in 64-Bit PCI slot isp1: 986 max I/O commands supported isp1: NVRAM Port WWN 0x210000e08b016899 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 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 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 atkbd0: irq 1 on atkbdc0 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbd0: atkbd0, generic (0), config:0x0, flags:0x1f0000 atkbd0: interrupting at ISA irq 1 psm0: current command byte:0061 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. fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 mcclock0: at port 0x70-0x71 on isa0 Calibrating clock(s) ... PCC clock: 532794199 Hz (firmware 531914893 Hz) i8254 clock: 1193144 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency ppc0: using extended I/O port range ppc0: SPP ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: cannot reserve interrupt, failed. lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 ppc0: interrupting at ISA irq 7 sc0: no video adapter is found. sc0: failed to probe on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: irq maps: 0 0 0 0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o sio1 failed to probe at port 0x2f8-0x2ff irq 3 flags 0x50 on isa0 vga0: 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 Timecounter "i8254" frequency 1193182 Hz bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: lo0 attached bpf: ppp0 attached bpf: faith0 attached Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. isp0: driver initiated bus reset of bus 0 isp1: LIP occurred isp1: Loop UP isp1: Name Server Database Changed isp1: Name Server Database Changed isp1: Firmware State Ready> isp1: Target 126 (Loop 0x7e) Port ID 0xfffffe (role (none)) Arrived Port WWN 0x200100c0dd008073 Node WWN 0x100000c0dd008073 isp1: Loop ID 0, AL_PA 0xef, Port ID 0x1001ef, Loop State 0x2, Topology 'FL Port' isp1: Target 0 (Loop 0x0) Port ID 0x1001ef (role Initiator) Arrived Port WWN 0x210000e08b016899 Node WWN 0x200000e08b016899 isp1: NL_Port @ 0x1004d6, Node 0x200000203700955f Port 210000203700955f isp1: NL_Port @ 0x1004d9, Node 0x200000203700c39a Port 210000203700c39a isp1: NL_Port @ 0x1004da, Node 0x2000002037083e9b Port 2100002037083e9b isp1: NL_Port @ 0x1004dc, Node 0x200000203700c3ac Port 210000203700c3ac isp1: NL_Port @ 0x1004e0, Node 0x200000203700c3a0 Port 210000203700c3a0 isp1: NL_Port @ 0x1004e1, Node 0x2000002037083e13 Port 2100002037083e13 isp1: NL_Port @ 0x1004e2, Node 0x20000020370094e0 Port 21000020370094e0 isp1: NL_Port @ 0x1004e4, Node 0x200000203700c350 Port 210000203700c350 isp1: NL_Port @ 0x1004e8, Node 0x200000203700c338 Port 210000203700c338 isp1: NL_Port @ 0x1004ef, Node 0x20000020370096a1 Port 21000020370096a1 isp1: NL_Port @ 0x1001ef, Node 0x200000e08b016899 Port 210000e08b016899 isp1: Target 129 (Loop 0x81) Port ID 0x1004d6 (role Target) Arrived Port WWN 0x210000203700955f Node WWN 0x200000203700955f isp1: Target 130 (Loop 0x82) Port ID 0x1004d9 (role Target) Arrived Port WWN 0x210000203700c39a Node WWN 0x200000203700c39a isp1: Target 131 (Loop 0x83) Port ID 0x1004da (role Target) Arrived Port WWN 0x2100002037083e9b Node WWN 0x2000002037083e9b isp1: Target 132 (Loop 0x84) Port ID 0x1004dc (role Target) Arrived Port WWN 0x210000203700c3ac Node WWN 0x200000203700c3ac isp1: Target 133 (Loop 0x85) Port ID 0x1004e0 (role Target) Arrived Port WWN 0x210000203700c3a0 Node WWN 0x200000203700c3a0 isp1: Target 134 (Loop 0x86) Port ID 0x1004e1 (role Target) Arrived Port WWN 0x2100002037083e13 Node WWN 0x2000002037083e13 isp1: Target 135 (Loop 0x87) Port ID 0x1004e2 (role Target) Arrived Port WWN 0x21000020370094e0 Node WWN 0x20000020370094e0 isp1: Target 136 (Loop 0x88) Port ID 0x1004e4 (role Target) Arrived Port WWN 0x210000203700c350 Node WWN 0x200000203700c350 isp1: Target 137 (Loop 0x89) Port ID 0x1004e8 (role Target) Arrived Port WWN 0x210000203700c338 Node WWN 0x200000203700c338 isp1: Target 138 (Loop 0x8a) Port ID 0x1004ef (role Target) Arrived Port WWN 0x21000020370096a1 Node WWN 0x20000020370096a1 (probe5:sym0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:sym0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:sym0:0:5:0): Invalid field in CDB sks:c8,1 Creating DISK cd0 Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 Creating DISK da4 Creating DISK da5 Creating DISK da6 Creating DISK da7 Creating DISK da8 Creating DISK da9 Creating DISK da10 Creating DISK da11 Creating DISK da12 pass0 at sym0 bus 0 target 5 lun 0 pass0: Removable CD-ROM SCSI-2 device pass0: 10.000MB/s transfers (10.000MHz, offset 8) pass1 at sym0 bus 0 target 6 lun 0 pass1: Removable Sequential Access SCSI-2 device pass1: Serial Number 0003203169 pass1: 10.000MB/s transfers (10.000MHz, offset 8) pass2 at isp0 bus 0 target 0 lun 0 pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number 5U5Z9126 pass2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled pass3 at isp0 bus 0 target 1 lun 0 pass3: Fixed Direct Access SCSI-2 device pass3: Serial Number JDY591270SXELP pass3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled pass4 at isp0 bus 0 target 2 lun 0 pass4: Fixed Direct Access SCSI-2 device pass4: Serial Number 174708531988 pass4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled pass5 at isp0 bus 0 target 14 lun 0 pass5: Fixed Processor SCSI-2 device pass5: Serial Number 1 pass5: 3.300MB/s transfers pass6 at isp1 bus 0 target 129 lun 0 pass6: Fixed Direct Access SCSI-2 device pass6: Serial Number NJ1151800000H8440HED pass6: 100.000MB/s transfers, Tagged Queueing Enabled pass7 at isp1 bus 0 target 130 lun 0 pass7: Fixed Direct Access SCSI-2 device pass7: Serial Number LJ7625860000291908YL pass7: 100.000MB/s transfers, Tagged Queueing Enabled pass8 at isp1 bus 0 target 131 lun 0 pass8: Fixed Direct Access SCSI-2 device pass8: Serial Number LJA174130000292103HC pass8: 100.000MB/s transfers, Tagged Queueing Enabled pass9 at isp1 bus 0 target 132 lun 0 pass9: Fixed Direct Access SCSI-2 device pass9: Serial Number LJ7627710000291908DU pass9: 100.000MB/s transfers, Tagged Queueing Enabled pass10 at isp1 bus 0 target 133 lun 0 pass10: Fixed Direct Access SCSI-2 device pass10: Serial Number LJ762695000029190ACX pass10: 100.000MB/s transfers, Tagged Queueing Enabled pass11 at isp1 bus 0 target 134 lun 0 pass11: Fixed Direct Access SCSI-2 device pass11: Serial Number LJA19587000029210B5B pass11: 100.000MB/s transfers, Tagged Queueing Enabled pass12 at isp1 bus 0 target 135 lun 0 pass12: Fixed Direct Access SCSI-2 device pass12: Serial Number NJ1200430000H8450JP3 pass12: 100.000MB/s transfers, Tagged Queueing Enabled pass13 at isp1 bus 0 target 136 lun 0 pass13: Fixed Direct Access SCSI-2 device pass13: Serial Number LJ74959500002919083X pass13: 100.000MB/s transfers, Tagged Queueing Enabled pass14 at isp1 bus 0 target 137 lun 0 pass14: Fixed Direct Access SCSI-2 device pass14: Serial Number LJ7490660000291908CP pass14: 100.000MB/s transfers, Tagged Queueing Enabled pass15 at isp1 bus 0 target 138 lun 0 pass15: Fixed Direct Access SCSI-2 device pass15: Serial Number NJ11513800002918H5HW pass15: 100.000MB/s transfers, Tagged Queueing Enabled sa0 at sym0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: Serial Number 0003203169 sa0: 10.000MB/s transfers (10.000MHz, offset 8) pass5 at isp0 bus 0 target 14 lun 0 pass5: Fixed Processor SCSI-2 device pass5: Serial Number 1 pass5: 3.300MB/s transfers da1 at isp0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number JDY591270SXELP da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 5U5Z9126 da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at isp0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number 174708531988 da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4094MB (8385121 512 byte sectors: 255H 63S/T 521C) da3 at isp1 bus 0 target 129 lun 0 da3: Fixed Direct Access SCSI-2 device da3: Serial Number NJ1151800000H8440HED da3: 100.000MB/s transfers, Tagged Queueing Enabled da3: 8748MB (17917393 512 byte sectors: 255H 63S/T 1115C) da4 at isp1 bus 0 target 130 lun 0 da4: Fixed Direct Access SCSI-2 device da4: Serial Number LJ7625860000291908YL da4: 100.000MB/s transfers, Tagged Queueing Enabled da4: 8625MB (17664229 512 byte sectors: 255H 63S/T 1099C) da5 at isp1 bus 0 target 131 lun 0 da5: Fixed Direct Access SCSI-2 device da5: Serial Number LJA174130000292103HC da5: 100.000MB/s transfers, Tagged Queueing Enabled da5: 8625MB (17664229 512 byte sectors: 255H 63S/T 1099C) da6 at isp1 bus 0 target 132 lun 0 da6: Fixed Direct Access SCSI-2 device da6: Serial Number LJ7627710000291908DU da6: 100.000MB/s transfers, Tagged Queueing Enabled da6: 8625MB (17664229 512 byte sectors: 255H 63S/T 1099C) da7 at isp1 bus 0 target 133 lun 0 da7: Fixed Direct Access SCSI-2 device da7: Serial Number LJ762695000029190ACX da7: 100.000MB/s transfers, Tagged Queueing Enabled da7: 8748MB (17917393 512 byte sectors: 255H 63S/T 1115C) da8 at isp1 bus 0 target 134 lun 0 da8: Fixed Direct Access SCSI-2 device da8: Serial Number LJA19587000029210B5B da8: 100.000MB/s transfers, Tagged Queueing Enabled da8: 8625MB (17664229 512 byte sectors: 255H 63S/T 1099C) da9 at isp1 bus 0 target 135 lun 0 da9: Fixed Direct Access SCSI-2 device da9: Serial Number NJ1200430000H8450JP3 da9: 100.000MB/s transfers, Tagged Queueing Enabled da9: 8748MB (17917393 512 byte sectors: 255H 63S/T 1115C) da10 at isp1 bus 0 target 136 lun 0 da10: Fixed Direct Access SCSI-2 device da10: Serial Number LJ74959500002919083X da10: 100.000MB/s transfers, Tagged Queueing Enabled da10: 8748MB (17917393 512 byte sectors: 255H 63S/T 1115C) da11 at isp1 bus 0 target 137 lun 0 da11: Fixed Direct Access SCSI-2 device da11: Serial Number LJ7490660000291908CP da11: 100.000MB/s transfers, Tagged Queueing Enabled da11: 8625MB (17664229 512 byte sectors: 255H 63S/T 1099C) da12 at isp1 bus 0 target 138 lun 0 da12: Fixed Direct Access SCSI-2 device da12: Serial Number NJ11513800002918H5HW da12: 100.000MB/s transfers, Tagged Queueing Enabled da12: 8748MB (17917393 512 byte sectors: 255H 63S/T 1115C) Mounting root from ufs:/dev/da2a (cd0:sym0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:sym0:0:5:0): NOT READY asc:3a,0 (cd0:sym0:0:5:0): Medium not present cd0 at sym0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da2: invalid primary partition table: no magic start_init: trying /sbin/init Entropy harvesting: ethernet. swapon: adding /dev/da2b as swap device Automatic boot in progress... /dev/da2a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/da2a: clean, 860793 free (29593 frags, 103900 blocks, 1.2% fragmentation) Using /var/db/entropy/saved-entropy.1 as an entropy file Using /var/db/entropy/saved-entropy.2 as an entropy file Using /var/db/entropy/saved-entropy.3 as an entropy file Using /var/db/entropy/saved-entropy.4 as an entropy file Using /var/db/entropy/saved-entropy.5 as an entropy file Using /var/db/entropy/saved-entropy.6 as an entropy file Using /var/db/entropy/saved-entropy.7 as an entropy file Using /var/db/entropy/saved-entropy.8 as an entropy file Doing initial network setup: hostname domain. de0: flags=8843 mtu 1500 inet 192.67.166.18 netmask 0xffffff00 broadcast 192.67.166.255 inet6 fe80::200:f8ff:fe01:8bd7%de0 prefixlen 64 tentative scopeid 0x1 ether 00:00:f8:01:8b:d7 media: 100baseTX status: active supported media: 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 192.67.166.126 Additional routing options: tcp extensions=NO TCP keepalive=YES. Routing daemons:. Mounting NFS file systems:NFS Portmap: RPC: Port mapper failure - RPC: Unable to send . Clearing /tmp:. Additional daemons: syslogd. dumpon: crash dumps to /dev/da2b (13, 17) Checking for core dump: savecore: no core dump Doing additional network setup: ntpdate ntpd portmap ypbind. Starting final network daemons: nfsiod NFS access cache time=2. ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib Starting standard daemons: inetd cron sshd. Initial rc.alpha initialization:. Configuring syscons:. Additional ABI support:. Starting local daemons:. Local package initialization: Networker -s bird.feral.com -s antares.feral.com. Additional TCP options:. Sun Mar 11 14:15:48 PST 2001 FreeBSD/alpha (nellie.feral.com) (console) login: Mar 11 14:19:40 nellie halt: halted by mjacob Mar 11 14:19:40 nellie syslogd: exiting on signal 15 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 12 6:24:53 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id 1F49037B718 for ; Mon, 12 Mar 2001 06:24:51 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client33.quantum.net [192.168.56.33]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2CEOow13826 for ; Mon, 12 Mar 2001 09:24:50 -0500 (EST) Message-ID: <3AACDC31.3010406@videotron.ca> Date: Mon, 12 Mar 2001 09:24:49 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: Syslog reports weird things Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On FreeBSD 4.3-BETA, I get some weird reports from syslog about the kernel. It seems like the console's output is interpreted in the log... For example, when I use sysinstall, I get a whole bunch ansi codes reported to the the console. When I compile, I get some weird messages that looks like compilation commands from the makefiles and sometimes, I get junk ascii codes.. I even get those messages when I'm in vi! Why is syslog reporting all those messages? It is really annoying. Normand Leclerc leclercn@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 12 10:28: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 36D2537B719 for ; Mon, 12 Mar 2001 10:28:05 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01K14CQ4OZ22000JHE@research.kpn.com> for freebsd-alpha@FreeBSD.ORG; Mon, 12 Mar 2001 19:27:56 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Mar 2001 19:26:05 +0100 Content-return: allowed Date: Mon, 12 Mar 2001 19:21:19 +0100 From: "Koster, K.J." Subject: RE: Syslog reports weird things To: "'leclercn@videotron.ca'" Cc: freebsd-alpha@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Normand, > > On FreeBSD 4.3-BETA, I get some weird reports from syslog about the > kernel. It seems like the console's output is interpreted in the > log... For example, when I use sysinstall, I get a whole bunch ansi > codes reported to the the console. When I compile, I get some weird > messages that looks like compilation commands from the makefiles and > sometimes, I get junk ascii codes.. I even get those > messages when I'm in vi! > Hmm. You mean like this? http://www.freebsd.org/cgi/query-pr.cgi?pr=24663 I am in the process of trying (and failing *sigh*) to build the world to try and reproduce this. Someone suggested that by doing installworld properly (i.e. do installworld in single user mode) this problem can be fixed. Which brings me to a related point: as I understand UNIX file system semantics, when I overwrite a file by moving another one into its place (say, a lib*.* during installworld) the old file is still available to those processes that had it open already and that new calls to open() will return the new file instead of the old one. So, what difference does it make if I do installworld in single user mode? In order to installworld I have to mount all filesystems, including the NFS ones that hold /usr/src and /usr/obj. Apart from ntpd and sshd single user mode looks the same way as multiusermode. What part of the install would not work in multiuser mode? Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Mar 12 11:54:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from quark.ele.etsmtl.ca (quark.ele.etsmtl.ca [142.137.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 9D97837B718 for ; Mon, 12 Mar 2001 11:54:24 -0800 (PST) (envelope-from nospam@ele.etsmtl.ca) Received: from station1.ele.etsmtl.ca (station1 [142.137.19.101]) by quark.ele.etsmtl.ca (8.8.8/8.8.8) with ESMTP id OAA23466; Mon, 12 Mar 2001 14:53:25 -0500 (EST) Received: from ele.etsmtl.ca (localhost [127.0.0.1]) by station1.ele.etsmtl.ca (8.9.3+Sun/8.9.1) with ESMTP id OAA04889; Mon, 12 Mar 2001 14:54:12 -0500 (EST) Message-ID: <3AAD2964.B72D5CB1@ele.etsmtl.ca> Date: Mon, 12 Mar 2001 14:54:12 -0500 From: Normand Leclerc Reply-To: lecn1306@ele.etsmtl.ca X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Koster, K.J." , freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kees, > > On FreeBSD 4.3-BETA, I get some weird reports from syslog about the > > kernel. It seems like the console's output is interpreted in the > Hmm. You mean like this? http://www.freebsd.org/cgi/query-pr.cgi?pr=24663 > Kinda like it yes but it is clear text instead of hex dumps. The worst program that does this is lynx. As soon as I get down a page with lynx, my screen gets screwed. I have to ctrl-l it to read (and that it when there are no ansi codes changing colors) > and reproduce this. Someone suggested that by doing installworld properly > (i.e. do installworld in single user mode) this problem can be fixed. Hmmm I compiled and installed it in single user mode last night. I'll have to check it out tonight (as I'm not home 'till then). I'll come back to you on this. I had problems compiling world when I was using CPUTYPE=pca56 instead of ev56 ... Don't know why, it's supposed to be an SX machine. Anyway, this is a nother problem not related to this annoying one. My guess is that it won't change a thing. > Which brings me to a related point: as I understand UNIX file system > semantics, when I overwrite a file by moving another one into its place > > ones that hold /usr/src and /usr/obj. Apart from ntpd and sshd single user > mode looks the same way as multiusermode. What part of the install would not > work in multiuser mode? > You are right all along. There are still deamons depending on libraries when overwriting. I beleive there should be some other safest way to do things like copying everything in temp directories and then, while booting, replacing the old ones. I don't know how this could be done tough. It would require a lot more space in /usr ... I don't know what daemons are doing when replacing libraries on the fly... Normand Leclerc lecn1306@ele.etsmtl.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 8: 0:22 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from quark.ele.etsmtl.ca (quark.ele.etsmtl.ca [142.137.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 93FF737B72C for ; Tue, 13 Mar 2001 08:00:17 -0800 (PST) (envelope-from nospam@ele.etsmtl.ca) Received: from station1.ele.etsmtl.ca (station1 [142.137.19.101]) by quark.ele.etsmtl.ca (8.8.8/8.8.8) with ESMTP id KAA10397; Tue, 13 Mar 2001 10:59:23 -0500 (EST) Received: from ele.etsmtl.ca (localhost [127.0.0.1]) by station1.ele.etsmtl.ca (8.9.3+Sun/8.9.1) with ESMTP id LAA26011; Tue, 13 Mar 2001 11:00:11 -0500 (EST) Message-ID: <3AAE440B.495A2046@ele.etsmtl.ca> Date: Tue, 13 Mar 2001 11:00:11 -0500 From: Normand Leclerc Reply-To: lecn1306@ele.etsmtl.ca X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Koster, K.J." , freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things (WARNING, ANSI CODES IN THERE) References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> Content-Type: multipart/mixed; boundary="------------CEB0DB7D35CFE7FE25AE4DB2" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------CEB0DB7D35CFE7FE25AE4DB2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Kees Jan, Well, I told you I'd come back to you with a status update on my 164sx compiled in single user mode. I still have the problem. I am attaching an output of my syslog so you can see how badly it affects my system. This output was generated using lynx.. Like the url address you forwarded me, it occurs when large quantity of data is sent to the console. Just in case you are wondering what kind of optimization I am using, it is simply "-O -pipe" with arch ev56. Nothing more. I was having this problem also with 4.2 and tought it was going to be corrected in 4.3... Seems it is still a mistery or should I saw a misery... If only I had some knowledge on the kernel and interrelations with its components, I could be helpfull but I'm an ignorant when it comes to the FreeBSD kernel. Altough I know my way around code... Normand Leclerc leclercn@videotron.ca --------------CEB0DB7D35CFE7FE25AE4DB2 Content-Type: text/plain; charset=iso-8859-1; name="t.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="t.txt" Mar 13 07:59:10 atom lpd[197]: lpd startup: logging=3D0 Mar 13 08:00:00 atom /kernel: cd1 at ahc0 bus 0 target 6 lun 0 Mar 13 08:00:00 atom /kernel: cd1: Removable = CD-ROM SCSI-2 device = Mar 13 08:00:00 atom /kernel: cd1: 8.064MB/s transfers (8.064MHz, offset = 15) Mar 13 08:00:00 atom /kernel: cd1: Attempt to query device size failed: N= OT READY, Medium not present Mar 13 08:00:24 atom login: ROOT LOGIN (root) ON console Mar 13 08:02:36 atom /kernel: =1B[34m=1B[47mHelp Desk Software=1B[30m=1B[= 47m | =1B[34m=1B[47mInsurance Quotes=1B[30m=1B[47m |=1B[B =1B[34m=1B[4= 7mLegal=1B[30m=1B[47m | =1B[34m=1B[47mMortgage=1B[30m=1B[47m | =1B[34m=1B= [47mReal Estate=1B[30m=1B[47m | =1B[34m=1B[47mShopping=1B[30m=1B[47m | = =1B[34m=1B[47mMore Searches...=1B[16;4H=1B[35m=1B[47mResources=1B[17;4H=1B= [34m=1B[47mYellow Pages=1B[30m=1B[47m | =1B[34m=1B[47mWhite Pages=1B[30m= =1B[47m | =1B[34m=1B[47mMaps=1B[30m=1B[47m | =1B[34m=1B[47mJob Search=1B= [30m=1B[47m | =1B[34m=1B[47mClassifieds=1B[30m=1B[47m |=1B[B =1B[34m=1B= [47mPersonals=1B[30m=1B[47m | =1B[34m=1B[47mMetacrawler Radio=1B[30m=1B[= 47m | =1B[34m=1B[47mFind A Home=1B[30m=1B[47m | =1B[34m=1B[47mPeople Se= arch=1B[30m=1B[47m | =1B[34m=1B[47mMore=1B[19;4HResources...=1B[30m=1B[4= 7m =1B[34m=1B[47mClick here! =1B[20;4H=1B[35m=1B[47mShopping Partners=1B[= 21;4H=1B[34m=1B[47mGo Shopping=1B[30m=1B[47m | =1B[34m=1B[47mDiscount Ai= rfares=1B[30m=1B[47m | =1B[34m=1B[47mWebmaster Tools=1B[30m=1B[47m | =1B= [34m=1B[47mAmazon.com=1B[30m=1B[47m |=1B[B =1B[34m=1B[47mClick here! [t= extlink.gif] =08=1B[25d=1B[m=1B[39;49m=1B[37m=1B[40m Mar 13 08:02:36 atom /kernel: 7mContact Us=1B[30m=1B[47m | =1B[34m=1B[47= mPrivacy Policy=1B[30m=1B[47m |=1B[B Traded on NASDAQ: =1B[34m=1B[47mIN= SP=1B[30m=1B[47m =A9 2000 InfoSpace, Inc. All Rights Reserved.=1B[30m=1B[= 47m =1B[15;4H=1B[34m=1B[47mTerms of Use=1B[30m=1B[47m | =1B[34m=1B[47mPr= ivacy Policy=1B[30m=1B[47m | =1B[34m=1B[47mContact Us=1B[30m=1B[47m | =1B= [34m=1B[47mAbout InfoSpace=1B[30m=1B[47m | =1B[34m=1B[47mMC=1B[16;4HHisto= ry=1B[30m=1B[47m |=1B[B=1B[30m=1B[47m=1B[K=1B[B=1B[K=1B[B=1B[K=1B[B=1B[K=1B= [B=1B[K=1B[B=1B[K=1B[m=1B[39;49m=1B[37m=1B[40m Mar 13 08:02:36 atom /kernel: os=1B[30m=1B[47m | =1B[34m=1B[47mBoats=1B[= 30m=1B[47m | =1B[34m=1B[47mHealth=1B[30m=1B[47m | =1B[34m=1B[47mHelp De= sk Software=1B[30m=1B[47m | =1B[34m=1B[47mInsurance Quotes=1B[30m=1B[47m= |=1B[B =1B[34m=1B[47mLegal=1B[30m=1B[47m | =1B[34m=1B[47mMortgage=1B[= 30m=1B[47m | =1B[34m=1B[47mReal Estate=1B[30m=1B[47m | =1B[34m=1B[47mSh= opping=1B[30m=1B[47m | =1B[34m=1B[47mMore Searches...=1B[30m=1B[47m =1B[= 16;4H=1B[35m=1B[47mResources=1B[17;4H=1B[34m=1B[47mYellow Pages=1B[30m=1B= [47m | =1B[34m=1B[47mWhite Pages=1B[30m=1B[47m | =1B[34m=1B[47mMaps=1B[= 30m=1B[47m | =1B[34m=1B[47mJob Search=1B[30m=1B[47m | =1B[34m=1B[47mCla= ssifieds=1B[30m=1B[47m |=1B[B =1B[34m=1B[47mPersonals=1B[30m=1B[47m | = =1B[34m=1B[47mMetacrawler Radio=1B[30m=1B[47m | =1B[34m=1B[47mFind A Hom= e=1B[30m=1B[47m | =1B[34m=1B[47mPeople Search=1B[30m=1B[47m | =1B[34m=1B= [47mMore=1B[19;4HResources...=1B[30m=1B[47m =1B[34m=1B[47mClick here! =1B= [20;4H=1B[35m=1B[47mShopping Partners=1B[21;4H=1B[34m=1B[47mGo Shopping=1B= [30m=1B[47m | =1B[34m=1B[47mDiscount Airfares=1B[30m=1B[47m | =1B[34m=1B= [47mWebmaster Tools=1B[30m=1B[47m | =1B[34m=1B[47mAmazon.com=1B[30m=1B[4= 7m |=1B[B =1B[34m=1B[47mClick here! [textlink.gif] =08=1B[25d=1B[m=1B[3= 9;49m=1B[37m=1B[40m Mar 13 08:02:36 atom /kernel: 49m=1B[37m=1B[40m --------------CEB0DB7D35CFE7FE25AE4DB2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 13:32:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F068337B718; Tue, 13 Mar 2001 13:32:11 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09461; Tue, 13 Mar 2001 13:32:14 -0800 Date: Tue, 13 Mar 2001 13:32:11 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Cc: alpha@freebsd.org Subject: Re: new breakage in mounting root? a devfs issue? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To refresh memory: > fatal kernel trap: > > trap entry = 0x4 (unaligned access fault) > a0 = 0xc3615fe1a88f382 > a1 = 0x29 > a2 = 0x1b > pc = 0xfffffc0000467578 > ra = 0xfffffc00004627c4 > curproc = 0xfffffe0009f5dbe0 > pid = 1, comm = init > > Stopped at vfs_object_create+0x38: jsr ra,(pv),vfs_object_create+0x3c > > db> t > vfs_object_create() at vfs_object_create+0x38 > getnewvnode() at getnewvnode+0x564 > devfs_allocv() at devfs_allocv+0xe0 > devfs_root() at devfs_root+0x38 > devfs_mount() at devfs_mount+0xf0 > vfs_mount() at vfs_mount+0x910 > mount() at mount+0xd8 > syscall() at syscall+0x3f4 > XentSys1() at XentSys1+0x10 Interestingly enough, as Christian had also reported, a build of a GENERIC kernel seems to solve this problem. This is almost more alarming than a potential bug in vfs_object_create- as the difference between the config file I was using should not cause this. *I* sure can't spot what config option might be different. I also had done a complete removal of the build directory and complete fresh build of GPLUS. (sounds of hair tearing). Can anyone suggest what below might have caused this breakage? --- GENERIC Mon Feb 5 11:46:37 2001 +++ GPLUS Mon Mar 12 14:59:09 2001 @@ -19,56 +19,57 @@ # # For hardware specific information check HARDWARE.TXT # -# $FreeBSD: src/sys/alpha/conf/GENERIC,v 1.107 2001/02/04 15:35:08 peter Exp $ +# $FreeBSD: src/sys/alpha/conf/GENERIC,v 1.102 2000/11/07 22:09:33 obrien Exp $ machine alpha cpu EV4 cpu EV5 ident GENERIC -maxusers 32 +maxusers 128 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" -#makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols +makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # Platforms supported -options API_UP1000 # UP1000, UP1100 (Nautilus) +#options API_UP1000 # UP1000 (Nautilus) options DEC_AXPPCI_33 # UDB, Multia, AXPpci33, Noname options DEC_EB164 # EB164, PC164, PC164LX, PC164SX -options DEC_EB64PLUS # EB64+, Aspen Alpine, etc -options DEC_2100_A50 # AlphaStation 200, 250, 255, 400 -options DEC_2100_A500 # AlphaServer 2000, 2100, 2100A -options DEC_KN20AA # AlphaStation 500, 600 -options DEC_ST550 # Personal Workstation 433, 500, 600 +#options DEC_EB64PLUS # EB64+, Aspen Alpine, etc +#options DEC_2100_A50 # AlphaStation 200, 250, 255, 400 +#options DEC_2100_A500 # AlphaServer 2000, 2100, 2100A +#options DEC_KN20AA # AlphaStation 500, 600 +#options DEC_ST550 # Personal Workstation 433, 500, 600 options DEC_ST6600 # xp1000, dp264, ds20, ds10, family -options DEC_3000_300 # DEC3000/300* Pelic* family -options DEC_3000_500 # DEC3000/[4-9]00 Flamingo/Sandpiper family -options DEC_1000A # AlphaServer 1000, 1000A, 800 -options DEC_KN8AE # AlphaServer 8200/8400 (Turbolaser) +#options DEC_3000_300 # DEC3000/300* Pelic* family +#options DEC_3000_500 # DEC3000/[4-9]00 Flamingo/Sandpiper family +#options DEC_1000A # AlphaServer 1000, 1000A, 800 +#options DEC_KN8AE # AlphaServer 8200/8400 (Turbolaser) options DEC_KN300 # AlphaServer 4100 (Rawhide), 1200 (Tincup) options INET #InterNETworking -options INET6 #IPv6 communications protocols +#options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem 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_ROOT #NFS usable as root device -options MSDOSFS #MSDOS Filesystem +#options NFS_ROOT #NFS usable as root device +#options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options DEVFS #Device Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] -options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI +#options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI +options SCSI_DELAY=0 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores -options P1003_1B #Posix P1003_1B real-time extentions -options _KPOSIX_PRIORITY_SCHEDULING +#options P1003_1B #Posix P1003_1B real-time extentions +#options _KPOSIX_PRIORITY_SCHEDULING # Standard busses device isa @@ -81,8 +82,8 @@ device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives -device atapifd # ATAPI floppy drives -device atapist # ATAPI tape drives +#device atapifd # ATAPI floppy drives +#device atapist # ATAPI tape drives # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices @@ -99,21 +100,21 @@ device pass # Passthrough device (direct SCSI access) # RAID controllers -device amr # AMI MegaRAID -device mlx # Mylex DAC960 family +#device amr # AMI MegaRAID +#device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse -device atkbdc 1 # At keyboard controller -device atkbd # at keyboard -device psm # psm mouse +#device atkbdc 1 # At keyboard controller +#device atkbd # at keyboard +#device psm # psm mouse -device vga # VGA screen +#device vga # VGA screen # splash screen/screen saver -device splash +#device splash # syscons is the default console driver, resembling an SCO console -device sc 1 +#device sc 1 # real time clock device mcclock @@ -122,60 +123,66 @@ device sio # 8250, 16[45]50 based serial ports # Parallel port -device ppc -device ppbus # Parallel port bus (required) -device lpt # Printer -device plip # TCP/IP over parallel -device ppi # Parallel port interface device -#device vpo # Requires scbus and da +#device ppc +#device ppbus # Parallel port bus (required) +#device lpt # Printer +#device plip # TCP/IP over parallel +#device ppi # Parallel port interface device +##device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) -device le # Lance -device vx # 3Com 3c590, 3c595 (``Vortex'') +#device le # Lance +#device vx # 3Com 3c590, 3c595 (``Vortex'') device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support -device dc # DEC/Intel 21143 and workalikes -device pcn # AMD Am79C79x PCI 10/100 NICs -device rl # RealTek 8129/8139 -device sf # Adaptec AIC-6915 (``Starfire'') -device sis # Silicon Integrated Systems SiS 900/SiS 7016 -device ste # Sundance ST201 (D-Link DFE-550TX) -device tl # Texas Instruments ThunderLAN -device vr # VIA Rhine, Rhine II -device wb # Winbond W89C840F -device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') +#device dc # DEC/Intel 21143 and workalikes +#device pcn # AMD Am79C79x PCI 10/100 NICs +#device rl # RealTek 8129/8139 +#device sf # Adaptec AIC-6915 (``Starfire'') +#device sis # Silicon Integrated Systems SiS 900/SiS 7016 +#device ste # Sundance ST201 (D-Link DFE-550TX) +#device tl # Texas Instruments ThunderLAN +#device vr # VIA Rhine, Rhine II +#device wb # Winbond W89C840F +#device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device device loop # Network loopback device ether # Ethernet support -device sl # Kernel SLIP -device ppp 1 # Kernel PPP +#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) +#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 ugen # Generic -device uhid # "Human Interface Devices" -device ukbd # Keyboard -device ulpt # Printer -device umass # Disks/Mass storage - Requires scbus and da0 -device ums # Mouse +#device uhci # UHCI PCI->USB interface +#device ohci # OHCI PCI->USB interface +#device usb # USB Bus (required) +#device ugen # Generic +#device uhid # "Human Interface Devices" +#device ukbd # Keyboard +#device ulpt # Printer +#device umass # Disks/Mass storage - Requires scbus and da0 +#device ums # Mouse # USB Ethernet -device aue # ADMtek USB ethernet -device cue # CATC USB ethernet -device kue # Kawasaki LSI USB ethernet +#device aue # ADMtek USB ethernet +#device cue # CATC USB ethernet +#device kue # Kawasaki LSI USB ethernet +# +options CAMDEBUG +options DDB +options BREAK_TO_DEBUGGER +device ses +device ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 13:36:46 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3280137B719; Tue, 13 Mar 2001 13:36:42 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA04152; Tue, 13 Mar 2001 16:36:41 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f2DLaBE55962; Tue, 13 Mar 2001 16:36:11 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15022.37578.945278.371914@grasshopper.cs.duke.edu> Date: Tue, 13 Mar 2001 16:36:10 -0500 (EST) To: mjacob@feral.com Cc: current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: new breakage in mounting root? a devfs issue? In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > *I* sure can't spot what config option might be different. I also had done a > complete removal of the build directory and complete fresh build of GPLUS. > (sounds of hair tearing). > > Can anyone suggest what below might have caused this breakage? One WAG is that the loader's module-loading is hosed. I got a somewhat similar panic on alpha when loading random from the loader prompt. Are you loading anything from the loader that might already be built into a GENERIC kernel? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 13:46:30 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7F8C637B71A; Tue, 13 Mar 2001 13:46:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA09585; Tue, 13 Mar 2001 13:46:23 -0800 Date: Tue, 13 Mar 2001 13:46:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: current@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: new breakage in mounting root? a devfs issue? In-Reply-To: <15022.37578.945278.371914@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Matthew Jacob writes: > > > *I* sure can't spot what config option might be different. I also had done a > > complete removal of the build directory and complete fresh build of GPLUS. > > (sounds of hair tearing). > > > > Can anyone suggest what below might have caused this breakage? > > One WAG is that the loader's module-loading is hosed. WAG? > I got a somewhat similar panic on alpha when loading random from the > loader prompt. > > Are you loading anything from the loader that might already be built into > a GENERIC kernel? The only thing I'm loading is ispfw (it's not part of either GENERIC or GPLUS as a static module). The ethernet interface is de, so that's static also. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 13:54: 6 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 1677C37B718 for ; Tue, 13 Mar 2001 13:54:04 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2DLpJs84263; Tue, 13 Mar 2001 13:51:19 -0800 (PST) (envelope-from obrien) Date: Tue, 13 Mar 2001 13:49:58 -0800 From: "David O'Brien" To: Matthew Jacob Cc: alpha@FreeBSD.ORG Subject: Re: new breakage in mounting root? a devfs issue? Message-ID: <20010313134957.A84194@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <15022.37578.945278.371914@grasshopper.cs.duke.edu> 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 Tue, Mar 13, 2001 at 01:46:19PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 13, 2001 at 01:46:19PM -0800, Matthew Jacob wrote: > > One WAG is that the loader's module-loading is hosed. > > WAG? Wild Ass Guess. Often said as "SWAG" -- Scientific Wild Ass Guess. I've seen it used more in hardware than software settings. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 14:37:24 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 54A9837B718; Tue, 13 Mar 2001 14:37:18 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2DMb6G39399; Tue, 13 Mar 2001 14:37:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 13 Mar 2001 14:36:45 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: new breakage in mounting root? a devfs issue? Cc: alpha@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Mar-01 Matthew Jacob wrote: > > To refresh memory: > >> fatal kernel trap: >> >> trap entry = 0x4 (unaligned access fault) >> a0 = 0xc3615fe1a88f382 >> a1 = 0x29 >> a2 = 0x1b >> pc = 0xfffffc0000467578 >> ra = 0xfffffc00004627c4 >> curproc = 0xfffffe0009f5dbe0 >> pid = 1, comm = init >> >> Stopped at vfs_object_create+0x38: jsr >> ra,(pv),vfs_object_create+0x3c >> >> db> t >> vfs_object_create() at vfs_object_create+0x38 >> getnewvnode() at getnewvnode+0x564 >> devfs_allocv() at devfs_allocv+0xe0 >> devfs_root() at devfs_root+0x38 >> devfs_mount() at devfs_mount+0xf0 >> vfs_mount() at vfs_mount+0x910 >> mount() at mount+0xd8 >> syscall() at syscall+0x3f4 >> XentSys1() at XentSys1+0x10 > > > Interestingly enough, as Christian had also reported, a build of a GENERIC > kernel seems to solve this problem. > > This is almost more alarming than a potential bug in vfs_object_create- as > the > difference between the config file I was using should not cause this. > > *I* sure can't spot what config option might be different. I also had done a > complete removal of the build directory and complete fresh build of GPLUS. > (sounds of hair tearing). Can you possibly try to narrow the differences down by tring out various kernel configs in between GPLUS and GENERIC? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 14:44:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B687637B718; Tue, 13 Mar 2001 14:44:13 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA09944; Tue, 13 Mar 2001 14:44:16 -0800 Date: Tue, 13 Mar 2001 14:44:12 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org, current@FreeBSD.org Subject: Re: new breakage in mounting root? a devfs issue? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can you possibly try to narrow the differences down by tring out various kernel > configs in between GPLUS and GENERIC? Actually- look at the diffs at least and tell me which you think it might be. All of the diffs are either kernel support flavors for alpha, which shouldn't matter to devfs for a damn, or drivers. If nobody can get to this, I'll try and look at this further, but this is looking very very strange. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 15:39: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C0AC937B719; Tue, 13 Mar 2001 15:38:54 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2DNcjG41742; Tue, 13 Mar 2001 15:38:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 13 Mar 2001 15:38:25 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: new breakage in mounting root? a devfs issue? Cc: current@FreeBSD.org, alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Mar-01 Matthew Jacob wrote: >> Can you possibly try to narrow the differences down by tring out various >> kernel >> configs in between GPLUS and GENERIC? > > Actually- look at the diffs at least and tell me which you think it might > be. All of the diffs are either kernel support flavors for alpha, which > shouldn't matter to devfs for a damn, or drivers. > > If nobody can get to this, I'll try and look at this further, but this is > looking very very strange. It could be some driver screwing up with makedev() though one would think we'd have hit that before now. It could be something really odd relating to the size of the kernel. It could be the maxuers change resulting in kernel memory being laid out differently. *shrug* I didn't see anything in that diff that would have broken this either. Does it happen w/o devfs? I'm updating my alpha to today's current, so perhaps I'll run into this here. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 21:26:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from femail12.sdc1.sfba.home.com (femail12.sdc1.sfba.home.com [24.0.95.108]) by hub.freebsd.org (Postfix) with ESMTP id EE75137B718 for ; Tue, 13 Mar 2001 21:26:38 -0800 (PST) (envelope-from craig-burgess@home.net) Received: from tiger ([24.0.178.21]) by femail12.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010314052638.TVNC2254.femail12.sdc1.sfba.home.com@tiger>; Tue, 13 Mar 2001 21:26:38 -0800 From: "Craig Burgess" To: , "Koster, K.J." , Subject: RE: Syslog reports weird things Date: Tue, 13 Mar 2001 21:27:08 -0800 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.2911.0) In-Reply-To: <3AAE440B.495A2046@ele.etsmtl.ca> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I will be interested in the solution - this is exactly what i've been seeing on my PC164 with FreeBSD 4.2. The strangeness started after cvsup and kernel rebuild from 4.1.1. The machine seems to work okay, it just collects horrid garbage in /var/log/messages and dmesg. craig -----Original Message----- From: owner-freebsd-alpha@FreeBSD.ORG [mailto:owner-freebsd-alpha@FreeBSD.ORG]On Behalf Of Normand Leclerc Sent: Tuesday, March 13, 2001 8:00 AM To: Koster, K.J.; freebsd-alpha@FreeBSD.ORG Subject: Re: Syslog reports weird things (WARNING, ANSI CODES IN THERE) Hi Kees Jan, Well, I told you I'd come back to you with a status update on my 164sx compiled in single user mode. I still have the problem. I am attaching an output of my syslog so you can see how badly it affects my system. This output was generated using lynx.. Like the url address you forwarded me, it occurs when large quantity of data is sent to the console. Just in case you are wondering what kind of optimization I am using, it is simply "-O -pipe" with arch ev56. Nothing more. I was having this problem also with 4.2 and tought it was going to be corrected in 4.3... Seems it is still a mistery or should I saw a misery... If only I had some knowledge on the kernel and interrelations with its components, I could be helpfull but I'm an ignorant when it comes to the FreeBSD kernel. Altough I know my way around code... Normand Leclerc leclercn@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Mar 13 23:48: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 4942537B719; Tue, 13 Mar 2001 23:47:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2E7kYF91178; Tue, 13 Mar 2001 23:46:34 -0800 (PST) (envelope-from obrien) Date: Tue, 13 Mar 2001 23:45:12 -0800 From: "David O'Brien" To: stable@freebsd.org, alpha@freebsd.org Subject: Re: New 4.3 BETA (BETA2) release available Message-ID: <20010313234512.A91108@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010313191333C.jkh@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: <20010313191333C.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Tue, Mar 13, 2001 at 07:13:33PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 13, 2001 at 07:13:33PM -0800, Jordan Hubbard wrote: > Since there has been a sudden spate of changes post-BETA (not a huge > number, but more than the usual amount in -stable since the freeze) > I decided it would be a good idea to roll a BETA2 snapshot, and > it's now on: The Alpha version is now available at ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/4.3-BETA-20010313 I'll roll and ISO and copy it up ASAP. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 3:30:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 13C0637B718 for ; Wed, 14 Mar 2001 03:30:43 -0800 (PST) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14d9UH-0001Fy-00; Wed, 14 Mar 2001 12:30:41 +0100 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f2EBPY706809 for freebsd-alpha@freebsd.org; Wed, 14 Mar 2001 12:25:34 +0100 (CET) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: new breakage in mounting root? a devfs issue? Date: Wed, 14 Mar 2001 11:25:34 +0000 (UTC) Message-ID: <98nkfe$6hr$1@kemoauc.mips.inka.de> References: <15022.37578.945278.371914@grasshopper.cs.duke.edu> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > One WAG is that the loader's module-loading is hosed. I don't think so. > Are you loading anything from the loader that might already be built into > a GENERIC kernel? Normally yes, but I also tried unload load /boot/kernel/kernel and that crashed just the same. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 4:19:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id D3B0C37B71B for ; Wed, 14 Mar 2001 04:19:45 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01K16SGQB5Y0000IN8@research.kpn.com> for freebsd-alpha@FreeBSD.ORG; Wed, 14 Mar 2001 13:19:38 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Wed, 14 Mar 2001 13:19:38 +0100 Content-return: allowed Date: Wed, 14 Mar 2001 13:19:37 +0100 From: "Koster, K.J." Subject: RE: Syslog reports weird things To: freebsd-alpha@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E452205FD9A5F@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I will be interested in the solution - this is exactly what > i've been seeing > on my PC164 with FreeBSD 4.2. The strangeness started after > cvsup and kernel rebuild from 4.1.1. > This is beginning to sound like there really is a problem somewhere. I thought I'd just screwed the world building somewhere. By the way, I cannot get the (-stable) world to build on my box anymore. Am I the only one? > > The machine seems to work okay, it just collects horrid garbage in > /var/log/messages and dmesg. > Are the timestamps in the message lines intact? Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 8:18:57 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from femail13.sdc1.sfba.home.com (femail13.sdc1.sfba.home.com [24.0.95.140]) by hub.freebsd.org (Postfix) with ESMTP id CCAD137B726 for ; Wed, 14 Mar 2001 08:18:49 -0800 (PST) (envelope-from craig-burgess@home.net) Received: from tiger ([24.0.178.21]) by femail13.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010314161848.KSG2924.femail13.sdc1.sfba.home.com@tiger>; Wed, 14 Mar 2001 08:18:48 -0800 From: "Craig Burgess" To: "Koster, K.J." , Subject: RE: Syslog reports weird things Date: Wed, 14 Mar 2001 08:19:18 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9A5F@l04.research.kpn.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----Original Message----- From: owner-freebsd-alpha@FreeBSD.ORG [mailto:owner-freebsd-alpha@FreeBSD.ORG]On Behalf Of Koster, K.J. Sent: Wednesday, March 14, 2001 4:20 AM To: freebsd-alpha@FreeBSD.ORG Subject: RE: Syslog reports weird things > > I will be interested in the solution - this is exactly what > i've been seeing > on my PC164 with FreeBSD 4.2. The strangeness started after > cvsup and kernel rebuild from 4.1.1. > This is beginning to sound like there really is a problem somewhere. I thought I'd just screwed the world building somewhere. By the way, I cannot get the (-stable) world to build on my box anymore. Am I the only one? > > The machine seems to work okay, it just collects horrid garbage in > /var/log/messages and dmesg. > Are the timestamps in the message lines intact? Kees Jan Yes as: Mar 3 22:00:13 Felix /kernel:  Mar 3 22:00:43 Felix /kernel: FF>z^A^@^@^@^@^@v^A^@^@F [7m^@^@^@^@^D{^A^@^@^@^@^@}^A^ @^@F I would think that there has to be some common factor among these machines or the problem would be universal. If we discover what's common, at least someone will know where to look for the cause. Here's the current dmesg: " exceeded pid 6031 (locate.code), uid 65534 on /: file system full" -- that's the complete contents of dmesg.today -- and the message is why i rebooted. So here's a bit of /var/log/messages (starting with reboot): ========================= Mar 14 07:48:33 Felix syslogd: exiting on signal 15 Mar 14 07:49:29 Felix /kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Mar 14 07:49:29 Felix /kernel: Waiting (max 60 seconds) for system process `syncer' to stop...stopped Mar 14 07:49:29 Felix /kernel: Mar 14 07:49:29 Felix /kernel: syncing disks... Mar 14 07:49:29 Felix /kernel: done Mar 14 07:49:29 Felix /kernel: Uptime: 8d17h7m33s Mar 14 07:49:29 Felix /kernel: Rebooting... Mar 14 07:49:29 Felix /kernel: Copyright (c) 1992-2001 The FreeBSD Project. Mar 14 07:49:29 Felix /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 14 07:49:29 Felix /kernel: The Regents of the University of California. All rights reserved. Mar 14 07:49:29 Felix /kernel: FreeBSD 4.2-STABLE #9: Tue Jan 23 14:11:01 PST 2001 Mar 14 07:49:29 Felix /kernel: root@Felix:/usr/src/sys/compile/FELIX Mar 14 07:49:29 Felix /kernel: EB164 Mar 14 07:49:29 Felix /kernel: Digital AlphaPC 164 500 MHz, 500MHz Mar 14 07:49:29 Felix /kernel: 8192 byte page size, 1 processor. Mar 14 07:49:29 Felix /kernel: CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 Mar 14 07:49:29 Felix /kernel: OSF PAL rev: 0x1000800020117 Mar 14 07:49:29 Felix /kernel: real memory = 265904128 (259672K bytes) Mar 14 07:49:29 Felix /kernel: avail memory = 252493824 (246576K bytes) Mar 14 07:49:29 Felix /kernel: Preloaded elf kernel "kernel" at 0xfffffc0000662000. Mar 14 07:49:29 Felix /kernel: md0: Malloc disk Mar 14 07:49:29 Felix /kernel: cia0: ALCOR/ALCOR2, pass 3 Mar 14 07:49:29 Felix /kernel: cia0: extended capabilities: 21 Mar 14 07:49:29 Felix /kernel: pcib0: <2117x PCI host bus adapter> on cia0 Mar 14 07:49:29 Felix /kernel: pci0: on pcib0 Mar 14 07:49:29 Felix /kernel: xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x10180-0x101bf irq 2 at device 5.0 on pci0 Mar 14 07:49:29 Felix /kernel: xl0: interrupting at CIA irq 2 Mar 14 07:49:29 Felix /kernel: xl0: Ethernet address: 00:60:08:19:48:35 Mar 14 07:49:29 Felix /kernel: miibus0: on xl0 Mar 14 07:49:29 Felix /kernel: nsphy0: on miibus0 Mar 14 07:49:29 Felix /kernel: nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Mar 14 07:49:29 Felix /kernel: pci0: <3D Labs model 0009 graphics accelerator> at 6.0 irq 0 Mar 14 07:49:29 Felix /kernel: xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0x10100-0x1017f mem 0x830a0100-0x830a017f irq 1 at device 7.0 on pci0 Mar 14 07:49:29 Felix /kernel: xl1: interrupting at CIA irq 1 Mar 14 07:49:29 Felix /kernel: xl1: Ethernet address: 00:10:4b:9c:da:ee Mar 14 07:49:29 Felix /kernel: miibus1: on xl1 Mar 14 07:49:29 Felix /kernel: xlphy0: <3Com internal media interface> on miibus1 Mar 14 07:49:29 Felix /kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Mar 14 07:49:29 Felix /kernel: isab0: at device 8.0 on pci0 Mar 14 07:49:29 Felix /kernel: isa0: on isab0 Mar 14 07:49:29 Felix /kernel: sym0: <825> port 0x10000-0x100ff mem 0x830a0000-0x830a00ff irq 3 at device 9.0 on pci0 Mar 14 07:49:29 Felix /kernel: sym0: No NVRAM, ID 7, Fast-10, SE, parity checking Mar 14 07:49:29 Felix /kernel: sym0: interrupting at CIA irq 3 Mar 14 07:49:29 Felix /kernel: atapci0: port 0x101c0-0x101cf irq 5 at device 11.0 on pci0 Mar 14 07:49:29 Felix /kernel: ata0: at 0x1f0 irq 14 on atapci0 Mar 14 07:49:29 Felix /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Mar 14 07:49:29 Felix /kernel: fdc0: interrupting at ISA irq 6 Mar 14 07:49:29 Felix /kernel: fdc0: FIFO enabled, 8 bytes threshold Mar 14 07:49:29 Felix /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Mar 14 07:49:29 Felix /kernel: atkbdc0: at port 0x60,0x64 on isa0 Mar 14 07:49:29 Felix /kernel: atkbd0: irq 1 on atkbdc0 Mar 14 07:49:29 Felix /kernel: atkbd0: interrupting at ISA irq 1 Mar 14 07:49:29 Felix /kernel: psm0: irq 12 on atkbdc0 Mar 14 07:49:29 Felix /kernel: psm0: interrupting at ISA irq 12 Mar 14 07:49:29 Felix /kernel: psm0: model IntelliMouse, device ID 3 Mar 14 07:49:29 Felix /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Mar 14 07:49:29 Felix /kernel: sc0: on isa0 Mar 14 07:49:29 Felix /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Mar 14 07:49:29 Felix /kernel: mcclock0: at port 0x70-0x71 on isa0 Mar 14 07:49:29 Felix /kernel: sio0 at port 0x3f8-0x3ff irq 4 on isa0 Mar 14 07:49:29 Felix /kernel: sio0: type 16550A Mar 14 07:49:29 Felix /kernel: sio0: interrupting at ISA irq 4 Mar 14 07:49:29 Felix /kernel: sio1: reserved for low-level i/o Mar 14 07:49:29 Felix /kernel: ppc0: at port 0x3bc-0x3bf irq 7 on isa0 Mar 14 07:49:29 Felix /kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Mar 14 07:49:29 Felix /kernel: plip0: cannot reserve interrupt, failed. Mar 14 07:49:29 Felix /kernel: lpt0: on ppbus0 Mar 14 07:49:29 Felix /kernel: lpt0: Polled port Mar 14 07:49:29 Felix /kernel: ppi0: on ppbus0 Mar 14 07:49:29 Felix /kernel: ppc0: interrupting at ISA irq 7 Mar 14 07:49:29 Felix /kernel: Timecounter "alpha" frequency 499999140 Hz Mar 14 07:49:29 Felix /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging disabled Mar 14 07:49:29 Felix /kernel: ata0-slave: identify retries exceeded Mar 14 07:49:29 Felix /kernel: ad0: 2441MB [4960/16/63] at ata0-master WDMA2 Mar 14 07:49:30 Felix /kernel: Waiting 8 seconds for SCSI devices to settle Mar 14 07:49:30 Felix /kernel: Mounting root from ufs:/dev/da0a Mar 14 07:49:30 Felix /kernel: da0 at sym0 bus 0 target 6 lun 0 Mar 14 07:49:30 Felix /kernel: da0: Fixed Direct Access SCSI-3 device Mar 14 07:49:30 Felix /kernel: da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled Mar 14 07:49:30 Felix /kernel: da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) Mar 14 07:49:35 Felix sshd[164]: error: bind: Address already in use Mar 14 07:49:35 Felix sshd[164]: fatal: Bind to port 22 failed: Address already in use. ========================= craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 8:56:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 734A637B718; Wed, 14 Mar 2001 08:56:33 -0800 (PST) (envelope-from ume@FreeBSD.org) Received: from localhost (IDENT:ZEFIK18BbQVa3WWArQKdsXtS3LK8dhUm18+9RVaXWkhhB7Rcgo5AjvKfwd/5CsXU@localhost [::1]) (authenticated as ume with CRAM-MD5) by peace.mahoroba.org (8.11.3/8.11.3/peace) with ESMTP/inet6 id f2EGrG304494; Thu, 15 Mar 2001 01:53:18 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Thu, 15 Mar 2001 01:53:16 +0900 (JST) Message-Id: <20010315.015316.85344842.ume@FreeBSD.org> To: alpha@FreeBSD.org, net@FreeBSD.org Subject: IPv4 address is not unsigned int From: Hajimu UMEMOTO X-Mailer: Mew version 1.95b97 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Thu_Mar_15_01:53:16_2001_677)--" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ----Next_Part(Thu_Mar_15_01:53:16_2001_677)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I wish to close PR 9982. This PR suggests that IPv4 address is not unsigned int and fix it to 32bit long. So, I took in_addr_t changes from OpenBSD and made a patch. It may break binary compatibility on Alpha, where u_long is 64 bits but in_addr_t would still be 32 bits. It seems working well on my *Pentium* box. However, I have no 64 bits environment. Please review the changes. ----Next_Part(Thu_Mar_15_01:53:16_2001_677)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: in_addr_t.diff Content-Disposition: inline; filename="in_addr_t.diff" Index: include/arpa/inet.h =================================================================== RCS file: /home/ncvs/src/include/arpa/inet.h,v retrieving revision 1.11 diff -u -r1.11 inet.h --- include/arpa/inet.h 1999/08/27 23:45:00 1.11 +++ include/arpa/inet.h 2001/03/13 12:41:29 @@ -84,13 +84,13 @@ __BEGIN_DECLS int ascii2addr __P((int, const char *, void *)); char *addr2ascii __P((int, const void *, int, char *)); -unsigned long inet_addr __P((const char *)); +in_addr_t inet_addr __P((const char *)); int inet_aton __P((const char *, struct in_addr *)); -unsigned long inet_lnaof __P((struct in_addr)); -struct in_addr inet_makeaddr __P((u_long , u_long)); -char * inet_neta __P((u_long, char *, size_t)); -unsigned long inet_netof __P((struct in_addr)); -unsigned long inet_network __P((const char *)); +in_addr_t inet_lnaof __P((struct in_addr)); +struct in_addr inet_makeaddr __P((in_addr_t, in_addr_t)); +char * inet_neta __P((in_addr_t, char *, size_t)); +in_addr_t inet_netof __P((struct in_addr)); +in_addr_t inet_network __P((const char *)); char *inet_net_ntop __P((int, const void *, int, char *, size_t)); int inet_net_pton __P((int, const char *, void *, size_t)); char *inet_ntoa __P((struct in_addr)); Index: lib/libc/net/inet.3 =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet.3,v retrieving revision 1.11 diff -u -r1.11 inet.3 --- lib/libc/net/inet.3 2000/12/29 14:08:00 1.11 +++ lib/libc/net/inet.3 2001/03/13 12:41:29 @@ -55,9 +55,9 @@ .Fd #include .Ft int .Fn inet_aton "const char *cp" "struct in_addr *pin" -.Ft unsigned long +.Ft in_addr_t .Fn inet_addr "const char *cp" -.Ft unsigned long +.Ft in_addr_t .Fn inet_network "const char *cp" .Ft char * .Fn inet_ntoa "struct in_addr in" @@ -66,10 +66,10 @@ .Ft int .Fn inet_pton "int af" "const char *src" "void *dst" .Ft struct in_addr -.Fn inet_makeaddr "unsigned long net" "unsigned long lna" -.Ft unsigned long +.Fn inet_makeaddr "in_addr_t net" "in_addr_t lna" +.Ft in_addr_t .Fn inet_lnaof "struct in_addr in" -.Ft unsigned long +.Ft in_addr_t .Fn inet_netof "struct in_addr in" .Sh DESCRIPTION The routines Index: lib/libc/net/inet_addr.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet_addr.c,v retrieving revision 1.12 diff -u -r1.12 inet_addr.c --- lib/libc/net/inet_addr.c 1999/12/27 08:40:40 1.12 +++ lib/libc/net/inet_addr.c 2001/03/13 12:41:29 @@ -72,7 +72,7 @@ * ASCII internet address interpretation routine. * The value returned is in network order. */ -u_long /* XXX should be struct in_addr :( */ +in_addr_t /* XXX should be struct in_addr :( */ inet_addr(cp) register const char *cp; { @@ -96,7 +96,7 @@ struct in_addr *addr; { u_long parts[4]; - u_long val; + in_addr_t val; char *c; char *endptr; int gotend, n; Index: lib/libc/net/inet_lnaof.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet_lnaof.c,v retrieving revision 1.2 diff -u -r1.2 inet_lnaof.c --- lib/libc/net/inet_lnaof.c 1998/09/02 00:53:16 1.2 +++ lib/libc/net/inet_lnaof.c 2001/03/13 12:41:29 @@ -44,11 +44,11 @@ * internet address; handles class a/b/c network * number formats. */ -u_long +in_addr_t inet_lnaof(in) struct in_addr in; { - register u_long i = ntohl(in.s_addr); + register in_addr_t i = ntohl(in.s_addr); if (IN_CLASSA(i)) return ((i)&IN_CLASSA_HOST); Index: lib/libc/net/inet_makeaddr.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet_makeaddr.c,v retrieving revision 1.2 diff -u -r1.2 inet_makeaddr.c --- lib/libc/net/inet_makeaddr.c 1998/09/02 00:53:17 1.2 +++ lib/libc/net/inet_makeaddr.c 2001/03/13 12:41:29 @@ -45,9 +45,9 @@ */ struct in_addr inet_makeaddr(net, host) - u_long net, host; + in_addr_t net, host; { - u_long addr; + in_addr_t addr; if (net < 128) addr = (net << IN_CLASSA_NSHIFT) | (host & IN_CLASSA_HOST); Index: lib/libc/net/inet_neta.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet_neta.c,v retrieving revision 1.6 diff -u -r1.6 inet_neta.c --- lib/libc/net/inet_neta.c 1999/08/28 00:00:11 1.6 +++ lib/libc/net/inet_neta.c 2001/03/13 12:41:29 @@ -38,7 +38,7 @@ /* * char * * inet_neta(src, dst, size) - * format a u_long network number into presentation format. + * format a in_addr_t network number into presentation format. * return: * pointer to dst, or NULL if an error occurred (check errno). * note: @@ -48,7 +48,7 @@ */ char * inet_neta(src, dst, size) - u_long src; + in_addr_t src; char *dst; size_t size; { Index: lib/libc/net/inet_netof.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet_netof.c,v retrieving revision 1.2 diff -u -r1.2 inet_netof.c --- lib/libc/net/inet_netof.c 1998/09/02 00:53:17 1.2 +++ lib/libc/net/inet_netof.c 2001/03/13 12:41:29 @@ -43,11 +43,11 @@ * Return the network number from an internet * address; handles class a/b/c network #'s. */ -u_long +in_addr_t inet_netof(in) struct in_addr in; { - register u_long i = ntohl(in.s_addr); + register in_addr_t i = ntohl(in.s_addr); if (IN_CLASSA(i)) return (((i)&IN_CLASSA_NET) >> IN_CLASSA_NSHIFT); Index: lib/libc/net/inet_network.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/inet_network.c,v retrieving revision 1.6 diff -u -r1.6 inet_network.c --- lib/libc/net/inet_network.c 1999/11/04 04:30:44 1.6 +++ lib/libc/net/inet_network.c 2001/03/13 12:41:29 @@ -47,13 +47,14 @@ * The library routines call this routine to interpret * network numbers. */ -u_long +in_addr_t inet_network(cp) register const char *cp; { - register u_long val, base, n, i; + register in_addr_t val, base, n; register char c; - u_long parts[4], *pp = parts; + in_addr_t parts[4], *pp = parts; + register int i; again: val = 0; base = 10; Index: sys/netinet/in.h =================================================================== RCS file: /home/ncvs/src/sys/netinet/in.h,v retrieving revision 1.53 diff -u -r1.53 in.h --- sys/netinet/in.h 2001/02/21 06:39:56 1.53 +++ sys/netinet/in.h 2001/03/13 12:41:29 @@ -232,7 +232,7 @@ * Internet address (a structure for historical reasons) */ struct in_addr { - u_int32_t s_addr; + in_addr_t s_addr; }; /* Index: sys/sys/types.h =================================================================== RCS file: /home/ncvs/src/sys/sys/types.h,v retrieving revision 1.41 diff -u -r1.41 types.h --- sys/sys/types.h 2000/10/27 11:45:49 1.41 +++ sys/sys/types.h 2001/03/13 12:41:30 @@ -73,6 +73,7 @@ typedef u_int32_t u_daddr_t; /* unsigned disk address */ typedef u_int32_t fixpt_t; /* fixed point number */ typedef u_int32_t gid_t; /* group id */ +typedef u_int32_t in_addr_t; /* base type for internet address */ typedef u_int32_t ino_t; /* inode number */ typedef long key_t; /* IPC key (for Sys V IPC) */ typedef u_int16_t mode_t; /* permissions */ ----Next_Part(Thu_Mar_15_01:53:16_2001_677)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Description: My Signature Content-Disposition: inline; filename=".signature-world" Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ ----Next_Part(Thu_Mar_15_01:53:16_2001_677)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 9: 0:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 29A8E37B719; Wed, 14 Mar 2001 09:00:30 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA49232; Wed, 14 Mar 2001 12:00:29 -0500 (EST) (envelope-from wollman) Date: Wed, 14 Mar 2001 12:00:29 -0500 (EST) From: Garrett Wollman Message-Id: <200103141700.MAA49232@khavrinen.lcs.mit.edu> To: Hajimu UMEMOTO Cc: alpha@FreeBSD.ORG, net@FreeBSD.ORG Subject: IPv4 address is not unsigned int In-Reply-To: <20010315.015316.85344842.ume@FreeBSD.org> References: <20010315.015316.85344842.ume@FreeBSD.org> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > +in_addr_t inet_lnaof __P((struct in_addr)); > +struct in_addr inet_makeaddr __P((in_addr_t, in_addr_t)); > +in_addr_t inet_netof __P((struct in_addr)); If anything, these interfaces should be removed. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 12: 0:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from quark.ele.etsmtl.ca (quark.ele.etsmtl.ca [142.137.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 039B537B719 for ; Wed, 14 Mar 2001 12:00:45 -0800 (PST) (envelope-from nospam@ele.etsmtl.ca) Received: from station1.ele.etsmtl.ca (station1 [142.137.19.101]) by quark.ele.etsmtl.ca (8.8.8/8.8.8) with ESMTP id OAA05579; Wed, 14 Mar 2001 14:59:46 -0500 (EST) Received: from ele.etsmtl.ca (localhost [127.0.0.1]) by station1.ele.etsmtl.ca (8.9.3+Sun/8.9.1) with ESMTP id PAA14756; Wed, 14 Mar 2001 15:00:37 -0500 (EST) Message-ID: <3AAFCDE5.5C8144CF@ele.etsmtl.ca> Date: Wed, 14 Mar 2001 15:00:37 -0500 From: Normand Leclerc Reply-To: lecn1306@ele.etsmtl.ca X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Craig Burgess , freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Craig, I'm releaved to see that other poeple are getting this problem. I'd like to know if it is only on the PC164 tough... If only I had the knowledge on how the system works I could try to find the solution... I just don't know how syslog gets it's messages... Anyways, we'll see if they can find it out. Normand. lecn1306@ele.etsmtl.ca Craig Burgess wrote: > I will be interested in the solution - this is exactly what i've been seeing > on my PC164 with FreeBSD 4.2. The strangeness started after cvsup and kernel > rebuild from 4.1.1. > > The machine seems to work okay, it just collects horrid garbage in > /var/log/messages and dmesg. > > craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 15: 7:30 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 5398637B719; Wed, 14 Mar 2001 15:07:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2EN7Ps05270; Wed, 14 Mar 2001 15:07:25 -0800 (PST) (envelope-from obrien) Date: Wed, 14 Mar 2001 15:07:21 -0800 From: "David O'Brien" To: stable@freebsd.org, alpha@freebsd.org Subject: Re: New 4.3 BETA (BETA2) release available Message-ID: <20010314150721.A5250@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010313191333C.jkh@osd.bsdi.com> <20010313234512.A91108@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010313234512.A91108@dragon.nuxi.com>; from obrien@freebsd.org on Tue, Mar 13, 2001 at 11:45:12PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 13, 2001 at 11:45:12PM -0800, David O'Brien wrote: > The Alpha version is now available at > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/4.3-BETA-20010313 > > I'll roll and ISO and copy it up ASAP. Alpha ISO is now available as ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.3-beta-20010313.iso To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 15:22:26 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7FAD537B719 for ; Wed, 14 Mar 2001 15:22:24 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2ENMJG84958 for ; Wed, 14 Mar 2001 15:22:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 14 Mar 2001 15:21:59 -0800 (PST) From: John Baldwin To: alpha@FreeBSD.org Subject: Deadlocks, whee! Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I managed to deadlock my alpha yesterday with a -j 4 buildworld. Previously it would die when it trapped with a raised IPL as a blockable mtx_lock() of lockmgr in trap(). I'm not sure if these two things are related or not. I'll try a normal world without -j X today to see if it fairs better. Just FYI for those running current that heavy load may deadlock right now. :( -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 16:40:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 92A7D37B71D; Wed, 14 Mar 2001 16:40:42 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA29224; Wed, 14 Mar 2001 19:40:42 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F0eC609319; Wed, 14 Mar 2001 19:40:12 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.3948.98001.417245@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 19:40:12 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: Deadlocks, whee! In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > Hi all, > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. Previously it > would die when it trapped with a raised IPL as a blockable mtx_lock() of lockmgr > in trap(). I'm not sure if these two things are related or not. I'll try a > normal world without -j X today to see if it fairs better. Just FYI for those > running current that heavy load may deadlock right now. :( The machine is really deadlocked, or just one process is wedged and the buildworld stalled? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 16:49:10 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id ED8C737B718 for ; Wed, 14 Mar 2001 16:49:07 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2F0mSG88227; Wed, 14 Mar 2001 16:48:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15024.3948.98001.417245@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 16:48:09 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: Re: Deadlocks, whee! Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Mar-01 Andrew Gallatin wrote: > > John Baldwin writes: > > Hi all, > > > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. > Previously it > > would die when it trapped with a raised IPL as a blockable mtx_lock() of > lockmgr > > in trap(). I'm not sure if these two things are related or not. I'll try > a > > normal world without -j X today to see if it fairs better. Just FYI for > those > > running current that heavy load may deadlock right now. :( > > The machine is really deadlocked, or just one process is wedged and > the buildworld stalled? Well, no messages on the console, no ddb (I have vidconsole), no pings, etc. So interrupts aren't getting through, or if they are their threads aren't running, and since I use preemption on this alpha, that is very, very unlikely. I'm assuming it is genuinely deadlocked or possibly spinning somewhere with a raised IPL. > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 17: 5:51 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4459437B71A; Wed, 14 Mar 2001 17:05:49 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA29503; Wed, 14 Mar 2001 20:05:48 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F15IF09447; Wed, 14 Mar 2001 20:05:18 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.5454.615759.779564@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 20:05:18 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: Deadlocks, whee! In-Reply-To: References: <15024.3948.98001.417245@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > > On 15-Mar-01 Andrew Gallatin wrote: > > > > John Baldwin writes: > > > Hi all, > > > > > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. > > Previously it > > > would die when it trapped with a raised IPL as a blockable mtx_lock() of > > lockmgr > > > in trap(). I'm not sure if these two things are related or not. I'll try > > a > > > normal world without -j X today to see if it fairs better. Just FYI for > > those > > > running current that heavy load may deadlock right now. :( > > > > The machine is really deadlocked, or just one process is wedged and > > the buildworld stalled? > > Well, no messages on the console, no ddb (I have vidconsole), no pings, etc. > So interrupts aren't getting through, or if they are their threads aren't > running, and since I use preemption on this alpha, that is very, very unlikely. > I'm assuming it is genuinely deadlocked or possibly spinning somewhere with a > raised IPL. Do you have a halt button? If so, what does the console tell you your PC and RA are? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 17:22:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 305A937B719 for ; Wed, 14 Mar 2001 17:22:56 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2F1MJG89419; Wed, 14 Mar 2001 17:22:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15024.5454.615759.779564@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 17:22:00 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: Re: Deadlocks, whee! Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Mar-01 Andrew Gallatin wrote: > > John Baldwin writes: > > > > On 15-Mar-01 Andrew Gallatin wrote: > > > > > > John Baldwin writes: > > > > Hi all, > > > > > > > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. > > > Previously it > > > > would die when it trapped with a raised IPL as a blockable mtx_lock() > of > > > lockmgr > > > > in trap(). I'm not sure if these two things are related or not. > I'll try > > > a > > > > normal world without -j X today to see if it fairs better. Just FYI > for > > > those > > > > running current that heavy load may deadlock right now. :( > > > > > > The machine is really deadlocked, or just one process is wedged and > > > the buildworld stalled? > > > > Well, no messages on the console, no ddb (I have vidconsole), no pings, > etc. > > So interrupts aren't getting through, or if they are their threads aren't > > running, and since I use preemption on this alpha, that is very, very > unlikely. > > I'm assuming it is genuinely deadlocked or possibly spinning somewhere > with a > > raised IPL. > > Do you have a halt button? If so, what does the console tell you your > PC and RA are? I need to crack the case open and move the jumper over so that it does a halt instead of a reboot. :( I just need to get off my duff and do that (along with 10 million other things) and then take it from there. > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 17:32:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from diablo.OntheNet.com.au (diablo.OntheNet.com.au [203.10.89.2]) by hub.freebsd.org (Postfix) with ESMTP id AC29F37B71A; Wed, 14 Mar 2001 17:32:08 -0800 (PST) (envelope-from tonyg@OntheNet.com.au) Received: from lancia.OntheNet.com.au (lancia.OntheNet.com.au [203.13.70.41]) by diablo.OntheNet.com.au (8.9.3/8.9.3) with ESMTP id LAA75102; Thu, 15 Mar 2001 11:32:06 +1000 (EST) Date: Thu, 15 Mar 2001 11:32:07 +1000 (EST) From: Tony Griffiths To: John Baldwin Cc: Andrew Gallatin , Subject: Re: Deadlocks, whee! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 14 Mar 2001, John Baldwin wrote: > > On 15-Mar-01 Andrew Gallatin wrote: > > > > John Baldwin writes: > > > Hi all, > > > > > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. > > Previously it > > > would die when it trapped with a raised IPL as a blockable mtx_lock() of > > lockmgr > > > in trap(). I'm not sure if these two things are related or not. I'll try > > a > > > normal world without -j X today to see if it fairs better. Just FYI for > > those > > > running current that heavy load may deadlock right now. :( > > > > The machine is really deadlocked, or just one process is wedged and > > the buildworld stalled? > > Well, no messages on the console, no ddb (I have vidconsole), no pings, etc. > So interrupts aren't getting through, or if they are their threads aren't > running, and since I use preemption on this alpha, that is very, very unlikely. > I'm assuming it is genuinely deadlocked or possibly spinning somewhere with a > raised IPL. Looks like a "deadlock" to me! Actually, I'm surprised that the 'fine-grained' SMP project in FreeBSD has managed to get as far as it has without implementing some form of "sanity" checking. I worked for DEC (Digital Equipment Corp) in the Networking Group at the time Ultrix (BSD 4.2/4.3) was doing fine-grained SMP and we had the following sanity checks in the locking code as an aide to maintaining our own sanity! ;-) 1) Logging of request/release calls 2) Lock hierarchy (ie. take-out ordering) 3) Spin-lock timeout (ie. panic() after 5000000 failed attempts to gain lock) 4) something else that I can't remember 'cause it was too long ago!!! The lock hierarchy was a BIG WIN in detecting/preventing deadlock conditions since it forced an order in lock acquisition although it didn't stop deadlocks from occurring when the locks were at the same level. The spin count exceeded picked those up. We also found a few problems on tri/quad-cpu systems that didn't occur on dual-cpu systems. Of course the amount of checking was a compile-time setting so that production code didn't suffer too badly. We learnt a lot of hard lessons on Ultrix, the main one being that we were too ambitious in trying for a VERY FINE-GRAINED locking strategy (especially in the networking code) than was warrented by any possible payback. Our OSF/Tru-64 implementation was much cleaner with pretty much a single lock at each layer of the network code (eg. socket, tcp/ip, driver). The locking hierarchy caused a few problems between the socket layer and transport but we could get around by using reference counts on objects that needed to stick around even when there was no 'lock' on them! Hope you have more 'fun' then we did (NOT) ... Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 17:34:18 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 49B2637B718; Wed, 14 Mar 2001 17:34:16 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA15641; Wed, 14 Mar 2001 17:34:19 -0800 Date: Wed, 14 Mar 2001 17:34:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: Deadlocks, whee! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org btw- it's been true for quite some time that ithreads seem to get dropped and not addressed- at least I think that this might be what would explain isp timeouts during makeworlds. When you deadlock'd your alpha, did you go and brew a cup of tea? What's your quantum for determining deadlock? On Wed, 14 Mar 2001, John Baldwin wrote: > Hi all, > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. Previously it > would die when it trapped with a raised IPL as a blockable mtx_lock() of lockmgr > in trap(). I'm not sure if these two things are related or not. I'll try a > normal world without -j X today to see if it fairs better. Just FYI for those > running current that heavy load may deadlock right now. :( > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 18:53:41 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2AD4637B71A for ; Wed, 14 Mar 2001 18:53:39 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA00941; Wed, 14 Mar 2001 21:53:38 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F2r7A09668; Wed, 14 Mar 2001 21:53:07 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.11923.918574.297867@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 21:53:07 -0500 (EST) To: "Koster, K.J." Cc: "'leclercn@videotron.ca'" , freebsd-alpha@FreeBSD.ORG Subject: RE: Syslog reports weird things In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to track this down.. Can anybody reproduce this with a serial console? Or is it a graphics console only occurance? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 19: 6:22 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A841837B718 for ; Wed, 14 Mar 2001 19:06:19 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA01084; Wed, 14 Mar 2001 22:06:19 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F35nH09700; Wed, 14 Mar 2001 22:05:49 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.12685.98146.651504@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 22:05:49 -0500 (EST) To: "Koster, K.J." Cc: freebsd-alpha@FreeBSD.ORG Subject: RE: Syslog reports weird things In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9A5F@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E452205FD9A5F@l04.research.kpn.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Koster, K.J. writes: > > By the way, I cannot get the (-stable) world to build on my box anymore. Am > I the only one? > It built fine for me from sources as of 4am EST today... Can you describe where it is failing for you? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 19:28:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 06E9C37B719 for ; Wed, 14 Mar 2001 19:28:46 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id WAA93211; Wed, 14 Mar 2001 22:28:31 -0500 (EST) Date: Wed, 14 Mar 2001 22:28:31 -0500 (EST) From: "Matthew N. Dodd" To: Peter Jeremy Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: EISA support for AS2100 ("Sable") In-Reply-To: <20010312081605.A11209@gsmx07.alcatel.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Mar 2001, Peter Jeremy wrote: > I have been offered an AS2100 with a collection of EISA cards, but I > note that HARDWARE.TXT states "EISA slots are currently unsupported" > for Sable. Is anyone currently working on this and/or can anyone tell > me how much effort would be involved in supporting the EISA bus? As part of my work on the EISA bus code I intend to look at the Alpha stuff in more detail at some point in the future. As I don't have an Alpha with EISA slots I can't say when in the future that will be. NetBSD does have support and I'm fairly sure that we don't need the resource configuration code they use so it may be a simple matter of looking at their code and writing the correct platform bits for the 2100. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 19:33:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id EB9B837B719 for ; Wed, 14 Mar 2001 19:33:38 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client33.quantum.net [192.168.56.33]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2F3XAw20176; Wed, 14 Mar 2001 22:33:10 -0500 (EST) Message-ID: <3AB037F6.80405@videotron.ca> Date: Wed, 14 Mar 2001 22:33:10 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I did not try the serial console. I know FreeBSD has some serious problems with serial ports (silo overflows and dropouts even at 9600bps). Right now, the console is where I can see the mess... Normand Andrew Gallatin wrote: > I'm trying to track this down.. Can anybody reproduce this with a > serial console? Or is it a graphics console only occurance? > > Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 20:12:46 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id F387937B719 for ; Wed, 14 Mar 2001 20:12:43 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA01854; Wed, 14 Mar 2001 23:12:26 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F4BuI09827; Wed, 14 Mar 2001 23:11:56 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.16652.75941.750262@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 23:11:56 -0500 (EST) To: "Matthew N. Dodd" Cc: Peter Jeremy , freebsd-alpha@FreeBSD.ORG Subject: Re: EISA support for AS2100 ("Sable") In-Reply-To: References: <20010312081605.A11209@gsmx07.alcatel.com.au> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew N. Dodd writes: > On Mon, 12 Mar 2001, Peter Jeremy wrote: > > I have been offered an AS2100 with a collection of EISA cards, but I > > note that HARDWARE.TXT states "EISA slots are currently unsupported" > > for Sable. Is anyone currently working on this and/or can anyone tell > > me how much effort would be involved in supporting the EISA bus? > > As part of my work on the EISA bus code I intend to look at the Alpha > stuff in more detail at some point in the future. > > As I don't have an Alpha with EISA slots I can't say when in the future > that will be. NetBSD does have support and I'm fairly sure that we don't > need the resource configuration code they use so it may be a simple matter > of looking at their code and writing the correct platform bits for the > 2100. > Matt, I'll be happy to make you an account on the 2100 at BSDI; just say the word. I seem to remember that when we last talked about this, enabling the EISA code on that 2100 led to the fddi adapter being probed properly, but the EISA fddi driver was failing to attach the device. Nobody on the west coast could come up with another EISA board that they could eisacfg into the system & we didn't know if it was a fundamental EISA problem on alpha, or just a problem with the fddi driver.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 20:20:34 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DE65337B718 for ; Wed, 14 Mar 2001 20:20:31 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA01935; Wed, 14 Mar 2001 23:20:31 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F4K1j09838; Wed, 14 Mar 2001 23:20:01 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.17137.342441.45530@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 23:20:01 -0500 (EST) To: leclercn@videotron.ca Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things In-Reply-To: <3AB037F6.80405@videotron.ca> References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> <3AB037F6.80405@videotron.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tcn writes: > I did not try the serial console. I know FreeBSD has some serious > problems with serial ports (silo overflows and dropouts even at > 9600bps). Right now, the console is where I can see the mess... Can you at least try setting the console to serial and seeing if the "mess" goes away, please? This will make the boot process quite silent. Once you're up and running, please log into the graphics head and do whatever it is you do that causes the problem. Speaking of this -- what is it that you do & how reproducable is it? Will running 'yes' do it, for example? FWIW, I have nearly 20 alphas running 4.2 with serial consoles & they all work just dandy. None of them have graphics heads though. I'm planning to put a head on my test box and try to reproduce this tomorrow... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Mar 14 21:32:19 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 39A1637B718 for ; Wed, 14 Mar 2001 21:32:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id AAA94835; Thu, 15 Mar 2001 00:32:03 -0500 (EST) Date: Thu, 15 Mar 2001 00:32:02 -0500 (EST) From: "Matthew N. Dodd" To: Andrew Gallatin Cc: Peter Jeremy , freebsd-alpha@FreeBSD.ORG Subject: Re: EISA support for AS2100 ("Sable") In-Reply-To: <15024.16652.75941.750262@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 14 Mar 2001, Andrew Gallatin wrote: > I'll be happy to make you an account on the 2100 at BSDI; just say the > word. Have you got it hooked up to a serial console? > I seem to remember that when we last talked about this, enabling the > EISA code on that 2100 led to the fddi adapter being probed properly, > but the EISA fddi driver was failing to attach the device. Nobody on > the west coast could come up with another EISA board that they could > eisacfg into the system & we didn't know if it was a fundamental EISA > problem on alpha, or just a problem with the fddi driver.. Since I (re)wrote the EISA 'fea' front end I wouldn't be surprised if it was a problem with the driver. I'll put together an assortment of EISA cards and ship them to you at some point so we can have a few more test subjects available. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 1:17:57 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 2C13837B718 for ; Thu, 15 Mar 2001 01:17:55 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01K180EQG4RU000K4T@research.kpn.com> for freebsd-alpha@FreeBSD.ORG; Thu, 15 Mar 2001 10:17:53 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Thu, 15 Mar 2001 10:17:53 +0100 Content-return: allowed Date: Thu, 15 Mar 2001 10:17:51 +0100 From: "Koster, K.J." Subject: RE: Syslog reports weird things To: freebsd-alpha@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E452205FD9A61@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear All, > > I'm releaved to see that other poeple are getting this > problem. I'd like > to know if it is only on the PC164 tough... If only I had > the knowledge on how > the system works I could try to find the solution... I just > don't know how > syslog gets it's messages... Anyways, we'll see if they can > find it out. > My problems are on a 166MHz NoName Alpha. I reported it earlier on this list. dmesg available for those who are interested, but here is the head of it: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RC1 #0: Thu Feb 8 02:21:41 CET 2001 root@:/usr/src/sys/compile/SLUGOUT DEC AXPpci Alpha PC AXPpci33, 166MHz 8192 byte page size, 1 processor. CPU: LCA Family major=4 minor=2 OSF PAL rev: 0x100090002012d real memory = 31481856 (30744K bytes) avail memory = 25305088 (24712K bytes) This is a clean install from the 4.2 RC1 cdrom and it does not show any problems now. Last night I started another make world, but that takes 24 hours to complete, so I cannot try to reproduce this until tomorrow. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 1:31:57 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id C109E37B718 for ; Thu, 15 Mar 2001 01:31:55 -0800 (PST) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01K180W349YM000K4T@research.kpn.com> for freebsd-alpha@FreeBSD.ORG; Thu, 15 Mar 2001 10:31:53 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Thu, 15 Mar 2001 10:31:52 +0100 Content-return: allowed Date: Thu, 15 Mar 2001 10:31:52 +0100 From: "Koster, K.J." Subject: RE: Syslog reports weird things To: 'Andrew Gallatin' Cc: freebsd-alpha@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E452205FD9A62@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Andrew, > > > By the way, I cannot get the (-stable) world to build > > on my box anymore. Am I the only one? > > > > It built fine for me from sources as of 4am EST today... > > Can you describe where it is failing for you? > http://www.geocrawler.com/lists/3/FreeBSD/154/50/5303423/ This was starting make as: /usr/bin/nohup make buildworld -DNOGAMES -DNOINFO -DNO_FORTRAN -DNOMAN -DNOHTML & /usr/src is NFS mounted from my PC and /usr/obj is mounted from /usr/obj/alpha on my PC. From the past I dumly remember that building worlds on NFS mounts requires *extact* same mount points. I'm in the process of rebuilding now, with exact the same mountpoints on both machines and doing just: /usr/bin/nohup make buildworld & Hope it works this time, but I won't know until tonight or tomorrow morning. :-/ Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 1:51: 6 2001 Delivered-To: freebsd-alpha@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 21B0037B718; Thu, 15 Mar 2001 01:51:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 14dUPO-00073l-0Y; Thu, 15 Mar 2001 09:51:02 +0000 Received: from salmon.nlsystems.com (salmon [10.0.0.3]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f2F9nk469928; Thu, 15 Mar 2001 09:49:46 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 15 Mar 2001 09:49:46 +0000 (GMT) From: Doug Rabson To: Tony Griffiths Cc: John Baldwin , Andrew Gallatin , Subject: Re: Deadlocks, whee! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 15 Mar 2001, Tony Griffiths wrote: > 1) Logging of request/release calls > 2) Lock hierarchy (ie. take-out ordering) > 3) Spin-lock timeout (ie. panic() after 5000000 failed attempts to gain lock) > 4) something else that I can't remember 'cause it was too long ago!!! We have most of this in the KTR and WITNESS code but for performance reasons they are not always enabled. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 2:21: 9 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id E0B4F37B718 for ; Thu, 15 Mar 2001 02:21:07 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2FAKw811812; Thu, 15 Mar 2001 02:20:58 -0800 (PST) (envelope-from obrien) Date: Thu, 15 Mar 2001 02:20:58 -0800 From: "David O'Brien" To: "Matthew N. Dodd" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: EISA support for AS2100 ("Sable") Message-ID: <20010315022058.A11774@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: <20010312081605.A11209@gsmx07.alcatel.com.au> <15024.16652.75941.750262@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15024.16652.75941.750262@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 14, 2001 at 11:11:56PM -0500 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-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 11:11:56PM -0500, Andrew Gallatin wrote: > I'll be happy to make you an account on the 2100 at BSDI; just say the > word. Hell, I'd be happy to *ship* you the 2100 at BSDi. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 7: 0:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id BA30137B718 for ; Thu, 15 Mar 2001 07:00:22 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA09370; Thu, 15 Mar 2001 10:00:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2FExlI11030; Thu, 15 Mar 2001 09:59:47 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.55523.759280.862398@grasshopper.cs.duke.edu> Date: Thu, 15 Mar 2001 09:59:47 -0500 (EST) To: "Matthew N. Dodd" Cc: Peter Jeremy , freebsd-alpha@FreeBSD.ORG Subject: Re: EISA support for AS2100 ("Sable") In-Reply-To: References: <15024.16652.75941.750262@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew N. Dodd writes: > On Wed, 14 Mar 2001, Andrew Gallatin wrote: > > I'll be happy to make you an account on the 2100 at BSDI; just say the > > word. > > Have you got it hooked up to a serial console? Yes. Details in private email to follow. > > I seem to remember that when we last talked about this, enabling the > > EISA code on that 2100 led to the fddi adapter being probed properly, > > but the EISA fddi driver was failing to attach the device. Nobody on > > the west coast could come up with another EISA board that they could > > eisacfg into the system & we didn't know if it was a fundamental EISA > > problem on alpha, or just a problem with the fddi driver.. > > Since I (re)wrote the EISA 'fea' front end I wouldn't be surprised if it > was a problem with the driver. > > I'll put together an assortment of EISA cards and ship them to you at some > point so we can have a few more test subjects available. Eeek, no. Don't ship them to me. I'm in North Carolina, the AS2100 is at BSDI in California. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 7:55:29 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from quark.ele.etsmtl.ca (quark.ele.etsmtl.ca [142.137.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 5C4EF37B718 for ; Thu, 15 Mar 2001 07:55:26 -0800 (PST) (envelope-from nospam@ele.etsmtl.ca) Received: from station1.ele.etsmtl.ca (station1 [142.137.19.101]) by quark.ele.etsmtl.ca (8.8.8/8.8.8) with ESMTP id KAA22233; Thu, 15 Mar 2001 10:54:23 -0500 (EST) Received: from ele.etsmtl.ca (localhost [127.0.0.1]) by station1.ele.etsmtl.ca (8.9.3+Sun/8.9.1) with ESMTP id KAA05052; Thu, 15 Mar 2001 10:55:17 -0500 (EST) Message-ID: <3AB0E5E4.3951E240@ele.etsmtl.ca> Date: Thu, 15 Mar 2001 10:55:17 -0500 From: Normand Leclerc Reply-To: lecn1306@ele.etsmtl.ca X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> <3AB037F6.80405@videotron.ca> <15024.17137.342441.45530@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I will set it up this evening and I'll come back to you on this. I've always had trouble with the serial console on my Alpha... The kernel gets all messages through but every interactive output (i.e. shell output) looses at least 50% of all character sent. This is another problem that I had on 4.2, we'll see on 4.3... Right now, the best example I can give you to produce a console mess is to use sysinstall or lynx. Normand. Andrew Gallatin wrote: > tcn writes: > > I did not try the serial console. I know FreeBSD has some serious > > problems with serial ports (silo overflows and dropouts even at > > 9600bps). Right now, the console is where I can see the mess... > > Can you at least try setting the console to serial and seeing if the > "mess" goes away, please? This will make the boot process quite > silent. Once you're up and running, please log into the graphics head > and do whatever it is you do that causes the problem. > > Speaking of this -- what is it that you do & how reproducable is it? > Will running 'yes' do it, for example? > > FWIW, I have nearly 20 alphas running 4.2 with serial consoles & they > all work just dandy. None of them have graphics heads though. I'm > planning to put a head on my test box and try to reproduce this > tomorrow... > > Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 10:26:18 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 8EEEA37B718; Thu, 15 Mar 2001 10:26:13 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14dcRw-000EaL-00; Thu, 15 Mar 2001 18:26:12 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.2/8.11.2) id f2FISPi01027; Thu, 15 Mar 2001 19:28:25 +0100 (CET) (envelope-from wkb) Date: Thu, 15 Mar 2001 19:28:25 +0100 From: Wilko Bulte To: "David O'Brien" Cc: stable@freebsd.org, alpha@freebsd.org Subject: Re: New 4.3 BETA (BETA2) release available Message-ID: <20010315192825.A1013@freebie.demon.nl> References: <20010313191333C.jkh@osd.bsdi.com> <20010313234512.A91108@dragon.nuxi.com> <20010314150721.A5250@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: <20010314150721.A5250@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Mar 14, 2001 at 03:07:21PM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 14, 2001 at 03:07:21PM -0800, David O'Brien wrote: > On Tue, Mar 13, 2001 at 11:45:12PM -0800, David O'Brien wrote: > > The Alpha version is now available at > > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/4.3-BETA-20010313 > > > > I'll roll and ISO and copy it up ASAP. > > Alpha ISO is now available as > ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.3-beta-20010313.iso Eh... >>>boot dkc600 (boot dkc600.6.0.1009.0 -flags i) block 0 of dkc600.6.0.1009.0 is not a valid boot block bootstrap failure >>> on both Miata MX5 and Multia233. With 2 different CDR disks. My bad download, or a bad .iso? Wilko -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 10:37:57 2001 Delivered-To: freebsd-alpha@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 11B5537B71A for ; Thu, 15 Mar 2001 10:37:54 -0800 (PST) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14dcdE-0006QP-00; Thu, 15 Mar 2001 18:37:52 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.2/8.11.2) id f2FIe5g01179; Thu, 15 Mar 2001 19:40:05 +0100 (CET) (envelope-from wkb) Date: Thu, 15 Mar 2001 19:40:05 +0100 From: Wilko Bulte To: freebsd-alpha@freebsd.org Cc: "Matthew N. Dodd" Subject: Re: EISA support for AS2100 ("Sable") Message-ID: <20010315194005.F1013@freebie.demon.nl> References: <20010312081605.A11209@gsmx07.alcatel.com.au> <15024.16652.75941.750262@grasshopper.cs.duke.edu> <20010315022058.A11774@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: <20010315022058.A11774@dragon.nuxi.com>; from obrien@freebsd.org on Thu, Mar 15, 2001 at 02:20:58AM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 15, 2001 at 02:20:58AM -0800, David O'Brien wrote: > On Wed, Mar 14, 2001 at 11:11:56PM -0500, Andrew Gallatin wrote: > > I'll be happy to make you an account on the 2100 at BSDI; just say the > > word. > > Hell, I'd be happy to *ship* you the 2100 at BSDi. C'mon, they (2100s) make excellent tables to put your pizza on ;) -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 11:25: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E6B137B71C for ; Thu, 15 Mar 2001 11:24:59 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA14952; Thu, 15 Mar 2001 14:24:58 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2FJOSk77014; Thu, 15 Mar 2001 14:24:28 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.5868.345485.300691@grasshopper.cs.duke.edu> Date: Thu, 15 Mar 2001 14:24:28 -0500 (EST) To: lecn1306@ele.etsmtl.ca, :Kees Jan Koster , craig-burgess@home.net Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things In-Reply-To: <3AB0E5E4.3951E240@ele.etsmtl.ca> References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> <3AB037F6.80405@videotron.ca> <15024.17137.342441.45530@grasshopper.cs.duke.edu> <3AB0E5E4.3951E240@ele.etsmtl.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Normand Leclerc writes: > Right now, the best example I can give you to produce a console mess is to > use sysinstall or lynx. I've tried both of those things, and I also just did a buildworld with the output going to console as suggested by Kees Jan Koster & I never saw the problem. My setup is as follows: - API UP1000 (dmesg appended) - 4.3-BETA as of yesterday morning, GENERIC +sound drivers +ddb - console on (vga) graphics head - no console customizations via vidcontrol, kbdcontrol, etc. - no screen savers Are any of you who are seeing this customizing the console in any way? Colors, screensavers, fonts, etc? Or are you running a base 80x25 white-on-black console like me? How about kernel config options to syscons? I'd really like to fix this, but if I cannot reproduce it, fixing it is going to be next to impossible. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-BETA #0: Wed Mar 14 22:41:41 EST 2001 gallatin@thunder.cs.duke.edu:/.amd_mnt/muffin/export/ari_scratch2/gallatin/stable/sys/compile/THUNDER UP1000 API UP1000 598 MHz, 598MHz 8192 byte page size, 1 processor. CPU: major=11 minor=8 extensions=0x307 OSF PAL rev: 0x100010002013e real memory = 131481600 (128400K bytes) avail memory = 121061376 (118224K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000810000. md0: Malloc disk pcib0: on irongate0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci2: on pcib1 pci2: at 5.0 isab0: at device 7.0 on pci0 isa0: on isab0 dc0: port 0x10100-0x1017f mem 0x41353100-0x4135317f irq 10 at device 9.0 on pci0 dc0: interrupting at ISA irq 10 dc0: Ethernet address: 00:00:f8:07:b6:45 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sym0: <875> port 0x10000-0x100ff mem 0x41351000-0x41351fff,0x41353000-0x413530ff irq 9 at device 10.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: interrupting at ISA irq 9 fxp0: port 0x10180-0x1019f mem 0x41100000-0x411fffff,0x41352000-0x41352fff irq 10 at device 11.0 on pci0 fxp0: using i/o space access fxp0: interrupting at ISA irq 10 fxp0: Ethernet address 00:a0:c9:8a:ac:aa atapci0: port 0x101b0-0x101bf,0x374-0x377,0x170-0x17f,0x3f4-0x3f7,0x1f0-0x1ff irq 15 at device 16.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 chip1: port 0x1040-0x105f,0x1000-0x103f at device 17.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 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 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0 at vga0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: cannot reserve interrupt, failed. lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 ppc0: interrupting at ISA irq 7 sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 sbc0: interrupting at ISA irq 5 pcm0: on sbc0 Timecounter "alpha" frequency 598974745 Hz ad0: 6149MB [12495/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using PIO4 (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/ad0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 12: 1:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from femail13.sdc1.sfba.home.com (femail13.sdc1.sfba.home.com [24.0.95.140]) by hub.freebsd.org (Postfix) with ESMTP id C101E37B718 for ; Thu, 15 Mar 2001 12:01:21 -0800 (PST) (envelope-from craig-burgess@home.net) Received: from tiger ([24.0.178.21]) by femail13.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010315200121.UPND15887.femail13.sdc1.sfba.home.com@tiger>; Thu, 15 Mar 2001 12:01:21 -0800 From: "Craig Burgess" To: "Andrew Gallatin" , , ": Kees Jan Koster" Cc: Subject: RE: Syslog reports weird things Date: Thu, 15 Mar 2001 12:01:52 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0025_01C0AD47.B93363D0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <15025.5868.345485.300691@grasshopper.cs.duke.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C0AD47.B93363D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I am running no mods to console. I am attaching the kernel configuration file and dmesg in case they help. I suspect that **something** changed between 4.1.1 and 4.2 which is when I discovered the problem here. I have been running the same hardware since version 3. I'd send my system to you for testing purposes but would it be enough help if you had root access? It's the next best thing to sending the machine. craig -----Original Message----- From: Andrew Gallatin [mailto:gallatin@cs.duke.edu] Sent: Thursday, March 15, 2001 11:24 AM To: lecn1306@ele.etsmtl.ca; : Kees Jan Koster; craig-burgess@home.net Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things Normand Leclerc writes: > Right now, the best example I can give you to produce a console mess is to > use sysinstall or lynx. I've tried both of those things, and I also just did a buildworld with the output going to console as suggested by Kees Jan Koster & I never saw the problem. My setup is as follows: - API UP1000 (dmesg appended) - 4.3-BETA as of yesterday morning, GENERIC +sound drivers +ddb - console on (vga) graphics head - no console customizations via vidcontrol, kbdcontrol, etc. - no screen savers Are any of you who are seeing this customizing the console in any way? Colors, screensavers, fonts, etc? Or are you running a base 80x25 white-on-black console like me? How about kernel config options to syscons? I'd really like to fix this, but if I cannot reproduce it, fixing it is going to be next to impossible. Drew ---------------------------------------------------------------------------- -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-BETA #0: Wed Mar 14 22:41:41 EST 2001 gallatin@thunder.cs.duke.edu:/.amd_mnt/muffin/export/ari_scratch2/gallatin/s table/sys/compile/THUNDER UP1000 API UP1000 598 MHz, 598MHz 8192 byte page size, 1 processor. CPU: major=11 minor=8 extensions=0x307 OSF PAL rev: 0x100010002013e real memory = 131481600 (128400K bytes) avail memory = 121061376 (118224K bytes) Preloaded elf kernel "kernel" at 0xfffffc0000810000. md0: Malloc disk pcib0: on irongate0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci2: on pcib1 pci2: at 5.0 isab0: at device 7.0 on pci0 isa0: on isab0 dc0: port 0x10100-0x1017f mem 0x41353100-0x4135317f irq 10 at device 9.0 on pci0 dc0: interrupting at ISA irq 10 dc0: Ethernet address: 00:00:f8:07:b6:45 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sym0: <875> port 0x10000-0x100ff mem 0x41351000-0x41351fff,0x41353000-0x413530ff irq 9 at device 10.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: interrupting at ISA irq 9 fxp0: port 0x10180-0x1019f mem 0x41100000-0x411fffff,0x41352000-0x41352fff irq 10 at device 11.0 on pci0 fxp0: using i/o space access fxp0: interrupting at ISA irq 10 fxp0: Ethernet address 00:a0:c9:8a:ac:aa atapci0: port 0x101b0-0x101bf,0x374-0x377,0x170-0x17f,0x3f4-0x3f7,0x1f0-0x1ff irq 15 at device 16.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 chip1: port 0x1040-0x105f,0x1000-0x103f at device 17.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 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 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0 at vga0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: cannot reserve interrupt, failed. lpt0: on ppbus0 lpt0: Polled port ppi0: on ppbus0 ppc0: interrupting at ISA irq 7 sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 sbc0: interrupting at ISA irq 5 pcm0: on sbc0 Timecounter "alpha" frequency 598974745 Hz ad0: 6149MB [12495/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using PIO4 (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/ad0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) ------=_NextPart_000_0025_01C0AD47.B93363D0 Content-Type: application/octet-stream; name="FELIX" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="FELIX" #=0A= # GENERIC -- Generic kernel configuration file for FreeBSD/alpha=0A= #=0A= # For more information on this file, please read the handbook section on=0A= # Kernel Configuration Files:=0A= #=0A= # http://www.FreeBSD.org/handbook/kernelconfig-config.html=0A= #=0A= # $FreeBSD: src/sys/alpha/conf/GENERIC,v 1.71.2.7 2000/07/20 00:19:38 = obrien Exp $=0A= =0A= machine alpha=0A= #cpu EV4=0A= cpu EV5=0A= ident FELIX=0A= maxusers 256=0A= =0A= #makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug symbols=0A= =0A= # Platforms supported=0A= =0A= options DEC_EB164 # EB164, PC164, PC164LX, PC164SX=0A= =0A= =0A= options INET #InterNETworking=0A= options INET6 #IPv6 communications protocols=0A= options FFS #Berkeley Fast Filesystem=0A= options FFS_ROOT #FFS usable as root device [keep this!]=0A= options SOFTUPDATES #Enable FFS soft updates support=0A= options MFS #Memory Filesystem=0A= options MD_ROOT #MD is a potential root device=0A= options NFS #Network Filesystem=0A= options NFS_ROOT #NFS usable as root device=0A= options MSDOSFS #MSDOS Filesystem=0A= options CD9660 #ISO 9660 Filesystem=0A= options CD9660_ROOT #CD-ROM usable as root device=0A= options PROCFS #Process filesystem=0A= options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]=0A= options SCSI_DELAY=3D8000 #Delay (in ms) before probing SCSI =0A= options UCONSOLE #Allow users to grab the console=0A= options KTRACE #ktrace(1) syscall trace support=0A= options SYSVSHM #SYSV-style shared memory=0A= options SYSVMSG #SYSV-style message queues=0A= options SYSVSEM #SYSV-style semaphores=0A= options P1003_1B #Posix P1003_1B real-time extentions=0A= options _KPOSIX_PRIORITY_SCHEDULING=0A= options ICMP_BANDLIM #Rate limit bad replies=0A= =0A= # Standard busses=0A= device isa=0A= device pci=0A= =0A= # Floppy drives=0A= device fdc0 at isa? port IO_FD1 irq 6 drq 2=0A= device fd0 at fdc0 drive 0=0A= =0A= # ATA and ATAPI devices=0A= device ata=0A= device atadisk # ATA disk drives=0A= device atapicd # ATAPI CDROM drives=0A= device atapifd # ATAPI floppy drives=0A= device atapist # ATAPI tape drives=0A= =0A= # SCSI Controllers=0A= =0A= ##device ncr # NCR/Symbios Logic=0A= ## device mlx # Mylex RAID controller=0A= device sym # NCR/Symbios (new)=0A= =0A= # SCSI peripherals=0A= device scbus # SCSI bus (required)=0A= device da # Direct Access (disks)=0A= # device sa # Sequential Access (tape etc)=0A= device cd # CD=0A= device pass # Passthrough device (direct SCSI access)=0A= =0A= # atkbdc0 controls both the keyboard and the PS/2 mouse=0A= device atkbdc0 at isa? port IO_KBD=0A= device atkbd0 at atkbdc? irq 1=0A= device psm0 at atkbdc? irq 12=0A= =0A= device vga0 at isa?=0A= =0A= # splash screen/screen saver=0A= pseudo-device splash=0A= =0A= # syscons is the default console driver, resembling an SCO console=0A= device sc0 at isa?=0A= =0A= # real time clock=0A= device mcclock0 at isa? port 0x70=0A= =0A= # Serial (COM) ports=0A= device sio0 at isa? port IO_COM1 irq 4=0A= device sio1 at isa? port IO_COM2 irq 3 flags 0x50=0A= =0A= # Parallel port=0A= device ppc0 at isa? irq 7=0A= device ppbus # Parallel port bus (required)=0A= device lpt # Printer=0A= device plip # TCP/IP over parallel=0A= device ppi # Parallel port interface device=0A= device vpo # Requires scbus and da=0A= =0A= # PCI Ethernet NICs.=0A= =0A= # PCI Ethernet NICs that use the common MII bus controller code.=0A= device miibus # MII bus support=0A= device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')=0A= =0A= # Pseudo devices - the number indicates how many units to allocated.=0A= pseudo-device loop # Network loopback=0A= pseudo-device ether # Ethernet support=0A= pseudo-device sl 1 # Kernel SLIP=0A= pseudo-device ppp 1 # Kernel PPP=0A= pseudo-device tun # Packet tunnel.=0A= pseudo-device pty # Pseudo-ttys (telnet etc)=0A= pseudo-device md # Memory "disks"=0A= pseudo-device gif 4 # IPv6 and IPv4 tunneling=0A= pseudo-device faith 1 # IPv6-to-IPv4 relaying/(translation)=0A= =0A= # The `bpf' pseudo-device enables the Berkeley Packet Filter.=0A= # Be aware of the administrative consequences of enabling this!=0A= pseudo-device bpf #Berkeley packet filter=0A= =0A= # USB support=0A= # (if you add any USB devices to this list, they must be added to the = Alpha=0A= # section of src/release/scripts/dokern.sh)=0A= =0A= # USB Ethernet=0A= =0A= options IPDIVERT=0A= options IPFIREWALL=0A= ------=_NextPart_000_0025_01C0AD47.B93363D0 Content-Type: application/octet-stream; name="dmesg" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg" 118>felix-access.log maillog.0.gz plant-error.log wtmp=0A= pid 6031 (locate.code), uid 65534 on /: file system full=0A= Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped=0A= Waiting (max 60 seconds) for system process `syncer' to stop...stopped=0A= =0A= syncing disks... =0A= done=0A= Uptime: 8d17h7m33s=0A= Rebooting...=0A= Copyright (c) 1992-2001 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 4.2-STABLE #9: Tue Jan 23 14:11:01 PST 2001=0A= root@Felix:/usr/src/sys/compile/FELIX=0A= EB164=0A= Digital AlphaPC 164 500 MHz, 500MHz=0A= 8192 byte page size, 1 processor.=0A= CPU: EV56 (21164A) major=3D7 minor=3D2 extensions=3D0x1=0A= OSF PAL rev: 0x1000800020117=0A= real memory =3D 265904128 (259672K bytes)=0A= avail memory =3D 252493824 (246576K bytes)=0A= Preloaded elf kernel "kernel" at 0xfffffc0000662000.=0A= md0: Malloc disk=0A= cia0: ALCOR/ALCOR2, pass 3=0A= cia0: extended capabilities: 21=0A= pcib0: <2117x PCI host bus adapter> on cia0=0A= pci0: on pcib0=0A= xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x10180-0x101bf irq 2 at = device 5.0 on pci0=0A= xl0: interrupting at CIA irq 2=0A= xl0: Ethernet address: 00:60:08:19:48:35=0A= miibus0: on xl0=0A= nsphy0: on miibus0=0A= nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto=0A= pci0: <3D Labs model 0009 graphics accelerator> at 6.0 irq 0=0A= xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0x10100-0x1017f mem = 0x830a0100-0x830a017f irq 1 at device 7.0 on pci0=0A= xl1: interrupting at CIA irq 1=0A= xl1: Ethernet address: 00:10:4b:9c:da:ee=0A= miibus1: on xl1=0A= xlphy0: <3Com internal media interface> on miibus1=0A= xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto=0A= isab0: at device 8.0 on pci0=0A= isa0: on isab0=0A= sym0: <825> port 0x10000-0x100ff mem 0x830a0000-0x830a00ff irq 3 at = device 9.0 on pci0=0A= sym0: No NVRAM, ID 7, Fast-10, SE, parity checking=0A= sym0: interrupting at CIA irq 3=0A= atapci0: port 0x101c0-0x101cf irq 5 at device = 11.0 on pci0=0A= ata0: at 0x1f0 irq 14 on atapci0=0A= fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0=0A= fdc0: interrupting at ISA irq 6=0A= fdc0: FIFO enabled, 8 bytes threshold=0A= fd0: <1440-KB 3.5" drive> on fdc0 drive 0=0A= atkbdc0: at port 0x60,0x64 on isa0=0A= atkbd0: irq 1 on atkbdc0=0A= atkbd0: interrupting at ISA irq 1=0A= psm0: irq 12 on atkbdc0=0A= psm0: interrupting at ISA irq 12=0A= psm0: model IntelliMouse, device ID 3=0A= vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0A= sc0: on isa0=0A= sc0: VGA <16 virtual consoles, flags=3D0x200>=0A= mcclock0: at port 0x70-0x71 on isa0=0A= sio0 at port 0x3f8-0x3ff irq 4 on isa0=0A= sio0: type 16550A=0A= sio0: interrupting at ISA irq 4=0A= sio1: reserved for low-level i/o=0A= ppc0: at port 0x3bc-0x3bf irq 7 on isa0=0A= ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode=0A= plip0: cannot reserve interrupt, failed.=0A= lpt0: on ppbus0=0A= lpt0: Polled port=0A= ppi0: on ppbus0=0A= ppc0: interrupting at ISA irq 7=0A= Timecounter "alpha" frequency 499999140 Hz=0A= IP packet filtering initialized, divert enabled, rule-based forwarding = disabled, default to deny, logging disabled=0A= ata0-slave: identify retries exceeded=0A= ad0: 2441MB [4960/16/63] at ata0-master WDMA2=0A= Waiting 8 seconds for SCSI devices to settle=0A= Mounting root from ufs:/dev/da0a=0A= da0 at sym0 bus 0 target 6 lun 0=0A= da0: Fixed Direct Access SCSI-3 device =0A= da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing = Enabled=0A= da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C)=0A= xl1: transmission error: 90=0A= xl1: tx underrun, increasing tx start threshold to 120 bytes=0A= ------=_NextPart_000_0025_01C0AD47.B93363D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 12:32:50 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 337E837B71D for ; Thu, 15 Mar 2001 12:32:47 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2FKWIG20727; Thu, 15 Mar 2001 12:32:18 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 15 Mar 2001 12:32:13 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: Deadlocks, whee! Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Mar-01 Matthew Jacob wrote: > btw- it's been true for quite some time that ithreads seem to get dropped and > not addressed- at least I think that this might be what would explain isp > timeouts during makeworlds. Hmmmmmmmm. When an interrupt comes in we always mark it as needing to be serviced before we grab the scheduler lock, and in the main ithread loop we always check that flag after getting the scheduler lock before we switch out. That _should_ mean that interrupts shouldn't be lost. > When you deadlock'd your alpha, did you go and brew a cup of tea? What's your > quantum for determining deadlock? No interrupts. I.e. ctrl-alt-esc doesn't work, pings are dropped, etc. I think it locked up durng an overnight buildworld and I reset it the next day. > On Wed, 14 Mar 2001, John Baldwin wrote: > >> Hi all, >> >> I managed to deadlock my alpha yesterday with a -j 4 buildworld. Previously >> it >> would die when it trapped with a raised IPL as a blockable mtx_lock() of >> lockmgr >> in trap(). I'm not sure if these two things are related or not. I'll try a >> normal world without -j X today to see if it fairs better. Just FYI for >> those >> running current that heavy load may deadlock right now. :( >> >> -- >> >> John Baldwin -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-alpha" in the body of the message >> > -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 12:34:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3711B37B732 for ; Thu, 15 Mar 2001 12:34:05 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2FKXjG20792; Thu, 15 Mar 2001 12:33:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 15 Mar 2001 12:33:40 -0800 (PST) From: John Baldwin To: Matthew Jacob Subject: Re: Deadlocks, whee! Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Mar-01 Matthew Jacob wrote: > btw- it's been true for quite some time that ithreads seem to get dropped and > not addressed- at least I think that this might be what would explain isp > timeouts during makeworlds. Hmmmmmmmm. When an interrupt comes in we always mark it as needing to be serviced before we grab the scheduler lock, and in the main ithread loop we always check that flag after getting the scheduler lock before we switch out. That _should_ mean that interrupts shouldn't be lost. > When you deadlock'd your alpha, did you go and brew a cup of tea? What's your > quantum for determining deadlock? No interrupts. I.e. ctrl-alt-esc doesn't work, pings are dropped, etc. I think it locked up durng an overnight buildworld and I reset it the next day. > On Wed, 14 Mar 2001, John Baldwin wrote: > >> Hi all, >> >> I managed to deadlock my alpha yesterday with a -j 4 buildworld. Previously >> it >> would die when it trapped with a raised IPL as a blockable mtx_lock() of >> lockmgr >> in trap(). I'm not sure if these two things are related or not. I'll try a >> normal world without -j X today to see if it fairs better. Just FYI for >> those >> running current that heavy load may deadlock right now. :( >> >> -- >> >> John Baldwin -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-alpha" in the body of the message >> > -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 12:34:41 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D362937B718 for ; Thu, 15 Mar 2001 12:34:36 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2FKXjG20788; Thu, 15 Mar 2001 12:33:45 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 15 Mar 2001 12:33:39 -0800 (PST) From: John Baldwin To: Tony Griffiths Subject: Re: Deadlocks, whee! Cc: alpha@FreeBSD.org, Andrew Gallatin Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 15-Mar-01 Tony Griffiths wrote: > On Wed, 14 Mar 2001, John Baldwin wrote: > >> >> On 15-Mar-01 Andrew Gallatin wrote: >> > >> > John Baldwin writes: >> > > Hi all, >> > > >> > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. >> > Previously it >> > > would die when it trapped with a raised IPL as a blockable mtx_lock() >> > > of >> > lockmgr >> > > in trap(). I'm not sure if these two things are related or not. I'll >> > > try >> > a >> > > normal world without -j X today to see if it fairs better. Just FYI >> > > for >> > those >> > > running current that heavy load may deadlock right now. :( >> > >> > The machine is really deadlocked, or just one process is wedged and >> > the buildworld stalled? >> >> Well, no messages on the console, no ddb (I have vidconsole), no pings, etc. >> So interrupts aren't getting through, or if they are their threads aren't >> running, and since I use preemption on this alpha, that is very, very >> unlikely. >> I'm assuming it is genuinely deadlocked or possibly spinning somewhere with >> a >> raised IPL. > > Looks like a "deadlock" to me! Unfortunately. :-/ > Actually, I'm surprised that the 'fine-grained' SMP project in FreeBSD has > managed to get as far as it has without implementing some form of "sanity" > checking. I worked for DEC (Digital Equipment Corp) in the Networking Group > at > the time Ultrix (BSD 4.2/4.3) was doing fine-grained SMP and we had the > following sanity checks in the locking code as an aide to maintaining our own > sanity! ;-) Actually, we do have this sanity checking. We have taken code from BSD/OS that builds dynamic order lists of mutexes on the fly (for sleep mutexes, spin mutexes have to have their order statically defined) and warns of lock order reversals, sleeping with mutexes held, etc. It has proved valuable already and will continue to do so in the future. Currently I'm working to generalize it so that it will work with our reader/writer locks to ensure that a consistent lock order is maintained between them and mutexes as well as making it possible to build the spin lock order list on the fly, though I think I will still require the spinlock list to be static just because very few spinlocks should be used and only in certain cases. We also have a kernel event tracing facility that logs events of lock acquires/releases to a circular log buffer that can be examined from the in kernel debugger or via gdb for post-mortem crash dump analysis. > 1) Logging of request/release calls > 2) Lock hierarchy (ie. take-out ordering) > 3) Spin-lock timeout (ie. panic() after 5000000 failed attempts to gain lock) We also have this in that the spin mutexes will panic if they spin for more than about 3 seconds. > 4) something else that I can't remember 'cause it was too long ago!!! > > The lock hierarchy was a BIG WIN in detecting/preventing deadlock conditions > since it forced an order in lock acquisition although it didn't stop > deadlocks > from occurring when the locks were at the same level. The spin count > exceeded > picked those up. Yep, we've already found that the original VFS code we inherited from 4.4BSD contained a few lock order reversals that could lead to potential deadlocks. Fixing those will be part of fixing VFS, which will be a non-trivial task I'm afraid. :-/ > We also found a few problems on tri/quad-cpu systems that didn't occur on > dual-cpu systems. So far my test quad box here at work hasn't hit any weird bugs that the dual testboxes I have didn't eventually run into. It does run into some things quicker however. > Of course the amount of checking was a compile-time setting so that > production > code didn't suffer too badly. Yep, same here. You can also disable all or part of its operation by setting appropriate environment variables in the kernel loader. (Well, the new witness can be entirely disabled from the loader, the old one currently in the tree can only have its spinlock checking disabled.) > > We learnt a lot of hard lessons on Ultrix, the main one being that we were > too > ambitious in trying for a VERY FINE-GRAINED locking strategy (especially in > the > networking code) than was warrented by any possible payback. Our OSF/Tru-64 > implementation was much cleaner with pretty much a single lock at each layer > of > the network code (eg. socket, tcp/ip, driver). The locking hierarchy caused > a > few problems between the socket layer and transport but we could get around > by > using reference counts on objects that needed to stick around even when there > was no 'lock' on them! Hmm. Currently we have per-process stucture locks and I think per-mbuf locks. I'm aware that we can end up with too many locks, but I don't have the experience yet to make those judgement calls. I have a feeling we will be trying it both ways for some things until we have a good basis to make these decisions on. > Hope you have more 'fun' then we did (NOT) ... Heh, we are already having _loads_ of fun. :) > Tony -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 12:34:55 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BC7EE37B719; Thu, 15 Mar 2001 12:34:52 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA19075; Thu, 15 Mar 2001 12:34:55 -0800 Date: Thu, 15 Mar 2001 12:34:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: Deadlocks, whee! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On 15-Mar-01 Matthew Jacob wrote: > > btw- it's been true for quite some time that ithreads seem to get dropped and > > not addressed- at least I think that this might be what would explain isp > > timeouts during makeworlds. > > Hmmmmmmmm. When an interrupt comes in we always mark it as needing to be > serviced before we grab the scheduler lock, and in the main ithread loop > we always check that flag after getting the scheduler lock before we > switch out. That _should_ mean that interrupts shouldn't be lost. Indeed! > > > When you deadlock'd your alpha, did you go and brew a cup of tea? What's your > > quantum for determining deadlock? > > No interrupts. I.e. ctrl-alt-esc doesn't work, pings are dropped, etc. I > think it locked up durng an overnight buildworld and I reset it the next day. Hmm... The FreeBSD portion of what I do got swapped out to the /dev/drum, but it's due back in early next week. I'll see where we are then. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 12:36:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from utep.el.utwente.nl (utep.el.utwente.nl [130.89.30.10]) by hub.freebsd.org (Postfix) with ESMTP id 9311937B719 for ; Thu, 15 Mar 2001 12:36:31 -0800 (PST) (envelope-from A.Dergatchev@tn.utwente.nl) Received: from tn.utwente.nl (uttnb55.tn.utwente.nl [130.89.74.55]) by utep.el.utwente.nl (8.9.3/8.9.3) with ESMTP id VAA15532; Thu, 15 Mar 2001 21:37:05 +0100 Message-ID: <3AB127DD.B9E5BC90@tn.utwente.nl> Date: Thu, 15 Mar 2001 21:36:45 +0100 From: "Andrei A. Dergatchev" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,ru MIME-Version: 1.0 To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG, "Matthew N. Dodd" Subject: Re: EISA support for AS2100 ("Sable") References: <20010312081605.A11209@gsmx07.alcatel.com.au> <15024.16652.75941.750262@grasshopper.cs.duke.edu> <20010315022058.A11774@dragon.nuxi.com> <20010315194005.F1013@freebie.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte wrote: > On Thu, Mar 15, 2001 at 02:20:58AM -0800, David O'Brien wrote: > > On Wed, Mar 14, 2001 at 11:11:56PM -0500, Andrew Gallatin wrote: > > > I'll be happy to make you an account on the 2100 at BSDI; just say the > > > word. > > > > Hell, I'd be happy to *ship* you the 2100 at BSDi. > > C'mon, they (2100s) make excellent tables to put your pizza on ;) Hey, if you're short of pizza tables and use some Alphas instead we can arrange a nice deal ;-) > > > -- > | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org > |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 14:57:41 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id 970A037B718 for ; Thu, 15 Mar 2001 14:57:29 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client33.quantum.net [192.168.56.33]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2FMv1w22124; Thu, 15 Mar 2001 17:57:01 -0500 (EST) Message-ID: <3AB148BC.5020106@videotron.ca> Date: Thu, 15 Mar 2001 17:57:00 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> <3AB037F6.80405@videotron.ca> <15024.17137.342441.45530@grasshopper.cs.duke.edu> <3AB0E5E4.3951E240@ele.etsmtl.ca> <15025.5868.345485.300691@grasshopper.cs.duke.edu> Content-Type: multipart/mixed; boundary="------------050107070900010304000502" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------050107070900010304000502 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit > Are any of you who are seeing this customizing the console in any way? > Colors, screensavers, fonts, etc? Or are you running a base 80x25 > white-on-black console like me? How about kernel config options > to syscons? I am not customizing anything but keyboard rate. It is plain VGA 80x25. Kernel options on console are the GENERIC's. I just tried the serial console and I'm sorry, it is useless. I is not working properly; I am loosing too many characters at speed of 9600. My screen gets messed up pretty good (I can't even see the login prompt properly...) Tough, I was able to try lynx even if I wasn't seeing anything good, then got a peek at the /var/log/messages using ssh... Lynx output is still in syslog. I am sending you my dmesg (I don't think it would help you tough) and my config. After this bug, I'm gonna bug you guys for the serial console bug... ;) Maybe I can be of any help but I'd need guidance. I know my way around code. (I even tought about joining developpement for the Alpha platform but since my schedule is full...) Normand Leclerc leclercn@videotron.ca --------------050107070900010304000502 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" deny tcp from any to any 113 in\^[[11;1H01900 0 0 deny udp from any to any 137 in\^[[12;1H01900 0 0 deny tcp from any to any 139 in\^[[25;8H\^[[m\^[[7m sio1: 1 more silo overflow (total 3) Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 2 done Uptime: 2d9h11m3s Rebooting... Unrecognized boot flag '0'. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-BETA #2: Sun Mar 11 16:17:14 EST 2001 root@atom.quanta.ca:/usr/src/sys/compile/ATOM EB164 Digital AlphaPC 164SX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x1 OSF PAL rev: 0x1000600020117 real memory = 132046848 (128952K bytes) avail memory = 124321792 (121408K bytes) Preloaded elf kernel "kernel" at 0xfffffc000056c000. cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x1100-0x117f mem 0x82056000-0x8205607f irq 9 at device 5.0 on pci0 xl0: interrupting at CIA irq 9 xl0: Ethernet address: 00:50:04:75:94:0c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0x1000-0x10ff mem 0x82054000-0x82054fff irq 11 at device 6.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: interrupting at CIA irq 11 pci0: at 7.0 irq 10 isab0: at device 8.0 on pci0 isa0: on isab0 pci0: at 8.1 pci0: at 8.2 pci0: at 8.3 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 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 atkbd0: interrupting at ISA irq 1 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x20020 on isa0 sio0: type ST16650A sio0: interrupting at ISA irq 4 sio1 at port 0x2f8-0x2ff irq 3 flags 0x20000 on isa0 sio1: type ST16650A sio1: interrupting at ISA irq 3 sio2 at port 0x3e8-0x3ef irq 5 flags 0x20000 on isa0 sio2: type ST16650A sio2: interrupting at ISA irq 5 ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Polled port ppc0: interrupting at ISA irq 7 Timecounter "alpha" frequency 533169056 Hz Waiting 8 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1a da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2047MB (4194058 512 byte sectors: 64H 32S/T 2047C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed ccd0-3: Concatenated disk drivers cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 8.064MB/s transfers (8.064MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 12 1 done Uptime: 21m3s Rebooting... Unrecognized boot flag '0'. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-BETA #3: Thu Mar 15 17:29:49 EST 2001 root@atom.quanta.ca:/usr/src/sys/compile/ATOM EB164 Digital AlphaPC 164SX 533 MHz, 531MHz 8192 byte page size, 1 processor. CPU: PCA56 (21164PC) major=9 minor=2 extensions=0x1 OSF PAL rev: 0x1000600020117 real memory = 132046848 (128952K bytes) avail memory = 124338176 (121424K bytes) Preloaded elf kernel "kernel" at 0xfffffc000056e000. cia0: Pyxis, pass 1 cia0: extended capabilities: 1 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x1100-0x117f mem 0x82056000-0x8205607f irq 9 at device 5.0 on pci0 xl0: interrupting at CIA irq 9 xl0: Ethernet address: 00:50:04:75:94:0c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0x1000-0x10ff mem 0x82054000-0x82054fff irq 11 at device 6.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: interrupting at CIA irq 11 pci0: at 7.0 irq 10 isab0: at device 8.0 on pci0 isa0: on isab0 pci0: at 8.1 pci0: at 8.2 pci0: at 8.3 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 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 atkbd0: interrupting at ISA irq 1 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x20010 on isa0 sio0: type ST16650A, console sio0: interrupting at ISA irq 4 sio1 at port 0x2f8-0x2ff irq 3 flags 0x20000 on isa0 sio1: type ST16650A sio1: interrupting at ISA irq 3 sio2 at port 0x3e8-0x3ef irq 5 flags 0x20000 on isa0 sio2: type ST16650A sio2: interrupting at ISA irq 5 ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Polled port ppc0: interrupting at ISA irq 7 Timecounter "alpha" frequency 533170336 Hz Waiting 8 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1a da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2047MB (4194058 512 byte sectors: 64H 32S/T 2047C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed ccd0-3: Concatenated disk drivers xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 8.064MB/s transfers (8.064MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present --------------050107070900010304000502 Content-Type: text/plain; name="ATOM" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ATOM" machine alpha cpu EV5 ident GENERIC maxusers 32 options DEC_EB164 # EB164, PC164, PC164LX, PC164SX options INET #InterNETworking #options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options MFS #Memory Filesystem #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device #options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root device #options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=8000 #Delay (in ms) before probing SCSI #options UCONSOLE #Allow users to grab the console options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies # Standard busses device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # 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 # 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) #pseudo-device vinum 4 #pseudo-device ccd 4 # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 #device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # real time clock device mcclock0 at isa? port 0x70 # Serial (COM) ports device sio0 at isa? port IO_COM1 irq 4 flags 0x20010 device sio1 at isa? port IO_COM2 irq 3 flags 0x20000 device sio2 at isa? port IO_COM3 irq 5 flags 0x20000 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP #pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md # Memory "disks" #pseudo-device gif 4 # IPv6 and IPv4 tunneling #pseudo-device faith 1 # IPv6-to-IPv4 relaying/(translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf 4 #Berkeley packet filter --------------050107070900010304000502-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 15:26:18 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id DA9DF37B718 for ; Thu, 15 Mar 2001 15:26:15 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client33.quantum.net [192.168.56.33]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2FNPmw22193; Thu, 15 Mar 2001 18:25:48 -0500 (EST) Message-ID: <3AB14F7B.1040909@videotron.ca> Date: Thu, 15 Mar 2001 18:25:47 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> <3AB037F6.80405@videotron.ca> <15024.17137.342441.45530@grasshopper.cs.duke.edu> <3AB0E5E4.3951E240@ele.etsmtl.ca> <15025.5868.345485.300691@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry, forgot to write that the yes command is outputing ys in the syslog also. Normand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 16: 8:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9421337B719 for ; Thu, 15 Mar 2001 16:08:50 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA19655; Thu, 15 Mar 2001 19:08:50 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2G08Kd77777; Thu, 15 Mar 2001 19:08:20 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.22899.726589.350460@grasshopper.cs.duke.edu> Date: Thu, 15 Mar 2001 19:08:19 -0500 (EST) To: leclercn@videotron.ca Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things In-Reply-To: <3AB148BC.5020106@videotron.ca> References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> <3AB037F6.80405@videotron.ca> <15024.17137.342441.45530@grasshopper.cs.duke.edu> <3AB0E5E4.3951E240@ele.etsmtl.ca> <15025.5868.345485.300691@grasshopper.cs.duke.edu> <3AB148BC.5020106@videotron.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tcn writes: > > I am sending you my dmesg (I don't think it would help you tough) and > my config. After this bug, I'm gonna bug you guys for the serial > console bug... ;) My opinion on your serial bug is that your cabling, communications software, or tty settings are messed up. Again, I have 20 production machines (including a PC164) using serial consoles & I have _never_ seen problems like you describe with a serial console in -stable. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 16:11:26 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1DA2A37B718 for ; Thu, 15 Mar 2001 16:11:24 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA19676; Thu, 15 Mar 2001 19:11:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2G0Ar877784; Thu, 15 Mar 2001 19:10:53 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.23053.650507.211024@grasshopper.cs.duke.edu> Date: Thu, 15 Mar 2001 19:10:53 -0500 (EST) To: leclercn@videotron.ca Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Syslog reports weird things In-Reply-To: <3AB14F7B.1040909@videotron.ca> References: <59063B5B4D98D311BC0D0001FA7E452205FD9A4F@l04.research.kpn.com> <15024.11923.918574.297867@grasshopper.cs.duke.edu> <3AB037F6.80405@videotron.ca> <15024.17137.342441.45530@grasshopper.cs.duke.edu> <3AB0E5E4.3951E240@ele.etsmtl.ca> <15025.5868.345485.300691@grasshopper.cs.duke.edu> <3AB14F7B.1040909@videotron.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tcn writes: > Sorry, forgot to write that the yes command is outputing ys in the > syslog also. > This when run on a serial or vga console? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 16:20:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B18C37B71C for ; Thu, 15 Mar 2001 16:20:56 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA19764; Thu, 15 Mar 2001 19:20:52 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2G0KMW77803; Thu, 15 Mar 2001 19:20:22 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.23622.509745.469218@grasshopper.cs.duke.edu> Date: Thu, 15 Mar 2001 19:20:22 -0500 (EST) To: "Craig Burgess" Cc: , ": Kees Jan Koster" , Subject: RE: Syslog reports weird things In-Reply-To: References: <15025.5868.345485.300691@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Craig Burgess writes: > I am running no mods to console. I am attaching the kernel configuration > file and dmesg in case they help. I suspect that **something** changed > between 4.1.1 and 4.2 which is when I discovered the problem here. I have > been running the same hardware since version 3. I'd send my system to you > for testing purposes but would it be enough help if you had root access? > It's the next best thing to sending the machine. > About the only commonality that I see that your machines have and that mine lacks is the xl nic, but I really doubt that's the problem. Hmm.. What do your /etc/ttys files look like? Specifically, what are the settings for the console, vtyv0 and ttyd0 lines. Eg, I have: console none unknown off secure ttyv0 "/usr/libexec/getty Pc" cons25 on secure ttyd0 "/usr/libexec/getty std.9600" vt100 on secure What happens if you flip off the getty on your "console" device? Does this help? (reboot or kill -HUP 1 for it to take effect) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 17:39:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 9B9B637B718; Thu, 15 Mar 2001 17:39:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2G1deZ53045; Thu, 15 Mar 2001 17:39:40 -0800 (PST) (envelope-from obrien) Date: Thu, 15 Mar 2001 17:39:39 -0800 From: "David O'Brien" To: Wilko Bulte Cc: stable@freebsd.org, alpha@freebsd.org Subject: Re: New 4.3 BETA (BETA2) release available Message-ID: <20010315173939.A53027@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010313191333C.jkh@osd.bsdi.com> <20010313234512.A91108@dragon.nuxi.com> <20010314150721.A5250@dragon.nuxi.com> <20010315192825.A1013@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010315192825.A1013@freebie.demon.nl>; from wkb@freebie.demon.nl on Thu, Mar 15, 2001 at 07:28:25PM +0100 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-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 15, 2001 at 07:28:25PM +0100, Wilko Bulte wrote: > Eh... > > >>>boot dkc600 > (boot dkc600.6.0.1009.0 -flags i) > block 0 of dkc600.6.0.1009.0 is not a valid boot block > bootstrap failure > >>> I'm looking into this, plus testing some patches from JKH to fix the "Going now where with out my init" problem. But a really stupid single character typo on my part has destablized my release build. I'm kicking off another release build and will report back here in several hours. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 18:26:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id 20D5137B71A for ; Thu, 15 Mar 2001 18:26:09 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client32.quantum.net [192.168.56.32]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2G2Pew23025; Thu, 15 Mar 2001 21:25:41 -0500 (EST) Message-ID: <3AB179A4.8050909@videotron.ca> Date: Thu, 15 Mar 2001 21:25:40 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: Syslog reports weird things References: <15025.5868.345485.300691@grasshopper.cs.duke.edu> <15025.23622.509745.469218@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hmm.. What do your /etc/ttys files look like? Specifically, what are > the settings for the console, vtyv0 and ttyd0 lines. Eg, I have: > > console none unknown off secure > ttyv0 "/usr/libexec/getty Pc" cons25 on secure > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure Okay, I was using the console device. If switched off and using ttyv0 (that I had to create in the ttys file) it seems like the problem is gone. I browse lynx while yes running and nothing is sent to syslog. Seems you guessed right. (also, yes was sending outputs in both serial console and vga console) As for the serial communication problem, I don't beleive in a cabling one. The SRM console works fine, the booting process of FreeBSD is working fine. As soon as vinum kicks in, I am missing chars. I get the "l" from the login prompt... but the message for my cdroms saying that the medium is not present is very clear (this mesage comes after the prompt). It's as if kernel messages were sent correctly but processes are messed up... Normand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 18:43:54 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from femail13.sdc1.sfba.home.com (femail13.sdc1.sfba.home.com [24.0.95.140]) by hub.freebsd.org (Postfix) with ESMTP id D602737B71C for ; Thu, 15 Mar 2001 18:43:50 -0800 (PST) (envelope-from craig-burgess@home.net) Received: from tiger ([24.0.178.21]) by femail13.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010316024349.PFDR15887.femail13.sdc1.sfba.home.com@tiger>; Thu, 15 Mar 2001 18:43:49 -0800 From: "Craig Burgess" To: "Andrew Gallatin" Cc: , ": Kees Jan Koster" , Subject: RE: Syslog reports weird things Date: Thu, 15 Mar 2001 18:44:22 -0800 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.2911.0) In-Reply-To: <15025.23622.509745.469218@grasshopper.cs.duke.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----Original Message----- From: owner-freebsd-alpha@FreeBSD.ORG [mailto:owner-freebsd-alpha@FreeBSD.ORG]On Behalf Of Andrew Gallatin Sent: Thursday, March 15, 2001 4:20 PM To: Craig Burgess Cc: lecn1306@ele.etsmtl.ca; : Kees Jan Koster; freebsd-alpha@FreeBSD.ORG Subject: RE: Syslog reports weird things Craig Burgess writes: > I am running no mods to console. I am attaching the kernel configuration > file and dmesg in case they help. I suspect that **something** changed > between 4.1.1 and 4.2 which is when I discovered the problem here. I have > been running the same hardware since version 3. I'd send my system to you > for testing purposes but would it be enough help if you had root access? > It's the next best thing to sending the machine. > About the only commonality that I see that your machines have and that mine lacks is the xl nic, but I really doubt that's the problem. Hmm.. What do your /etc/ttys files look like? Specifically, what are the settings for the console, vtyv0 and ttyd0 lines. Eg, I have: console none unknown off secure ttyv0 "/usr/libexec/getty Pc" cons25 on secure ttyd0 "/usr/libexec/getty std.9600" vt100 on secure What happens if you flip off the getty on your "console" device? Does this help? (reboot or kill -HUP 1 for it to take effect) Drew I never looked here before.... The following is snipped from virgin /etc/getty: <--------- start --------------> # If console is marked "insecure", then init will ask for the root password # when going to single-user mode. # console "/usr/libexec/getty Pc" cons25 on secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" cons25 on secure .... ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure <---------- pause -------------> I have no ttyv0 and presume that ttyv8 is either a default or left from attempts to install XFree86. <---------- resume ------------> # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 "/usr/libexec/getty std.9600" dialup off secure ttyd1 "/usr/libexec/getty std.9600" dialup off secure <---------- pause -------------> There are several (way more than 3) pseudo terminals: <---------- resume ------------> # Pseudo terminals ttyp0 none network <----------- end --------------> What will (should) happen when they are turned 'off' ? craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 18:47: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6464137B718 for ; Thu, 15 Mar 2001 18:46:58 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA21504; Thu, 15 Mar 2001 21:46:57 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2G2kR978029; Thu, 15 Mar 2001 21:46:27 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.32387.734109.233946@grasshopper.cs.duke.edu> Date: Thu, 15 Mar 2001 21:46:27 -0500 (EST) To: leclercn@videotron.ca Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Syslog reports weird things In-Reply-To: <3AB179A4.8050909@videotron.ca> References: <15025.5868.345485.300691@grasshopper.cs.duke.edu> <15025.23622.509745.469218@grasshopper.cs.duke.edu> <3AB179A4.8050909@videotron.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tcn writes: > > Hmm.. What do your /etc/ttys files look like? Specifically, what are > > the settings for the console, vtyv0 and ttyd0 lines. Eg, I have: > > > > console none unknown off secure > > ttyv0 "/usr/libexec/getty Pc" cons25 on secure > > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > > Okay, I was using the console device. If switched off and using > ttyv0 (that I had to create in the ttys file) it seems like the problem > is gone. I browse lynx while yes running and nothing is sent to > syslog. Seems you guessed right. (also, yes was sending outputs in > both serial console and vga console) Woo hoo! > As for the serial communication problem, I don't beleive in a cabling > one. The SRM console works fine, the booting process of FreeBSD is Have you tried it since you turned off the getty on "console" I think that could be responsible for your serial problems too. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Mar 15 18:57:36 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id B958837B718 for ; Thu, 15 Mar 2001 18:57:33 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA21694; Thu, 15 Mar 2001 21:57:31 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2G2v1Y78042; Thu, 15 Mar 2001 21:57:01 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15025.33021.208534.712006@grasshopper.cs.duke.edu> Date: Thu, 15 Mar 2001 21:57:01 -0500 (EST) To: "Craig Burgess" Cc: , ": Kees Jan Koster" , Subject: getty on console (was RE: Syslog reports weird things) In-Reply-To: References: <15025.23622.509745.469218@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Craig Burgess writes: > I never looked here before.... The following is snipped from virgin > /etc/getty: You mean /etc/ttys.. <...> > What will (should) happen when they are turned 'off' ? > > craig See the ttys (5) man page. Basically, the daemon is not run. So, one might ask: "Why was getty enabled on console in the first place?" Serial consoles are (at least percentage wise) much more common on alphas than on i386. Getty was enabled by default on console a year ago to prevent a POLA violation for people who installed onto an alpha via a serial console & then couldn't login via the serial console because the default setting is off for the serial port. Since having a getty run on "console" seems to be causing problems, I think the best solution would be to turn it off & to teach sysinstall to notice you're using a serial console & enable ttyd0 for you. Opinions? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 1:37: 3 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 74C8F37B719; Fri, 16 Mar 2001 01:36:58 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f2G9atA90146; Fri, 16 Mar 2001 10:36:55 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.2/8.11.0) id f2G9ar312004; Fri, 16 Mar 2001 10:36:53 +0100 (CET) (envelope-from asmodai) Date: Fri, 16 Mar 2001 10:36:53 +0100 From: Jeroen Ruigrok/Asmodai To: Garrett Wollman Cc: Hajimu UMEMOTO , alpha@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: IPv4 address is not unsigned int Message-ID: <20010316103653.C11527@daemon.ninth-circle.org> References: <20010315.015316.85344842.ume@FreeBSD.org> <200103141700.MAA49232@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200103141700.MAA49232@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Wed, Mar 14, 2001 at 12:00:29PM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20010314 18:30], Garrett Wollman (wollman@khavrinen.lcs.mit.edu) wrote: >< said: >> +in_addr_t inet_lnaof __P((struct in_addr)); >> +struct in_addr inet_makeaddr __P((in_addr_t, in_addr_t)); >> +in_addr_t inet_netof __P((struct in_addr)); > >If anything, these interfaces should be removed. Then we need to fix some code first, since, for example, inet_makeaddr() is still used. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Seek, and ye shall find; knock, and it shall be opened unto you... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 4:53: 7 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id EC4E137B719 for ; Fri, 16 Mar 2001 04:53:04 -0800 (PST) (envelope-from fujimori@grafin.fujimori.cache.waseda.ac.jp) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.9.3/3.7W) with ESMTP id VAA27111 for ; Fri, 16 Mar 2001 21:53:03 +0900 Message-Id: <200103161253.VAA27111@grafin.fujimori.cache.waseda.ac.jp> To: freebsd-alpha@freebsd.org Subject: vm_page.c Date: Fri, 16 Mar 2001 21:53:03 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks, Sometime ago I posted that up1100 could not boot from HDD if it has got more than 512MB memory. Then, I got a patch for vm_page.c from Drew, and up1100 now boots fine with 768MB memory. I thank Drew much! I patched kernel sources of all alphapc164 and pc164lx here, and I guess new vm_page.c does not do any harm on older alphas. # I did not test eb64+, which has been stopped for a few months. So, my wish is this new vm_page.c will be included in future version of 4.3. I wonder if mcclock bug fix has been in 4.3-beta. Best, Yoriaki Fujimori To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 6:13:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5688F37B719 for ; Fri, 16 Mar 2001 06:13:39 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA28945; Fri, 16 Mar 2001 09:13:38 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2GED8U79177; Fri, 16 Mar 2001 09:13:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15026.8052.360366.388276@grasshopper.cs.duke.edu> Date: Fri, 16 Mar 2001 09:13:08 -0500 (EST) To: Yoriaki FUJIMORI Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: vm_page.c In-Reply-To: <200103161253.VAA27111@grafin.fujimori.cache.waseda.ac.jp> References: <200103161253.VAA27111@grafin.fujimori.cache.waseda.ac.jp> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yoriaki FUJIMORI writes: > Folks, > Sometime ago I posted that up1100 could not boot from HDD if it has > got more than 512MB memory. Then, I got a patch for vm_page.c from Drew, > and up1100 now boots fine with 768MB memory. I thank Drew much! You're welcome. I'm glad we finally figured this out. <...> > So, my wish is this new vm_page.c will be included in future version > of 4.3. Yes, it will be in 4.3 -- it was committed to -stable on March 3: > I wonder if mcclock bug fix has been in 4.3-beta. Yes, it should be in 4.3 -- it was committed to -stable on March 10. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 11:25:46 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id AF7ED37B718 for ; Fri, 16 Mar 2001 11:25:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2GJPdK95646; Fri, 16 Mar 2001 11:25:39 -0800 (PST) (envelope-from obrien) Date: Fri, 16 Mar 2001 11:25:38 -0800 From: "David O'Brien" To: Andrew Gallatin Cc: Craig Burgess , freebsd-alpha@FreeBSD.ORG Subject: Re: getty on console (was RE: Syslog reports weird things) Message-ID: <20010316112538.B93551@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <15025.23622.509745.469218@grasshopper.cs.duke.edu> <15025.33021.208534.712006@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15025.33021.208534.712006@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 15, 2001 at 09:57:01PM -0500 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-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 15, 2001 at 09:57:01PM -0500, Andrew Gallatin wrote: > Since having a getty run on "console" seems to be causing problems, I > think the best solution would be to turn it off & to teach sysinstall > to notice you're using a serial console & enable ttyd0 for you. > > Opinions? Well.... coming from Solaris and NetBSD/Sparc, if you install via graphics console, then switch to serial console, everything still works just fine. The only way to get that is to turn ttyd0 on always. But the potential security risks make that a no-no. I have not seen a problem with the getty active on the console on any of my Alphas. But from discussions with msmith and bde, I know some of the reasons why people feel it is wrong. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 14:22:31 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 162CB37B719; Fri, 16 Mar 2001 14:22:25 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA08753; Fri, 16 Mar 2001 17:22:24 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2GMLsA82142; Fri, 16 Mar 2001 17:21:54 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15026.37378.477855.889651@grasshopper.cs.duke.edu> Date: Fri, 16 Mar 2001 17:21:54 -0500 (EST) To: freebsd-alpha@freebsd.org Cc: jhb@freebsd.org Subject: user process faulting on kernel address X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When running a linuxthreads app which basically sits in a loop doing a pthread_create()/pthread_join() of a thread which just exits, I'll occasionally see a very interesting thing -- the app dies on an instruction fault on a kernel address. Enabling the DEBUG printtrap() calls in trap yeilds this information: login: fatal user trap: trap entry = 0x2 (memory management fault) a0 = 0xfffffc0000418be0 a1 = 0x1 a2 = 0xffffffffffffffff pc = 0xfffffc0000418be0 ra = 0x11ffbfc4 curproc = 0xfffffe0006824cc0 pid = 18788, comm = ex6 Note that it is an instruction fault (a2 == -1) and the faulting address maps to the bottom of witness_exit: (kgdb) l *0xfffffc0000418be0 0xfffffc0000418be0 is in witness_exit (../../kern/kern_mutex.c:1262). 1257 m->mtx_line = line; 1258 m->mtx_file = file; 1259 p = curproc; 1260 MPASS(m->mtx_held.le_prev == NULL); 1261 LIST_INSERT_HEAD(&p->p_heldmtx, (struct mtx*)m, mtx_held); 1262 } 1263 1264 void 1265 witness_exit(struct mtx *m, int flags, const char *file, int line) 1266 { The $ra looks reasonable, it is at least a userspace stack address. I think somebody saw this a while ago, but I cannot find their message.. Any ideas? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 14:29:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3675637B71A for ; Fri, 16 Mar 2001 14:29:52 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA24562; Fri, 16 Mar 2001 14:29:45 -0800 Date: Fri, 16 Mar 2001 14:29:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: user process faulting on kernel address In-Reply-To: <15026.37378.477855.889651@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hah. On a related note, the faulting address for dumps that SIGSEGV' is in fact, CURSIG in the kernel. Same ra range- user stack address. D'ya think they're related? Doug? > > When running a linuxthreads app which basically sits in a loop > doing a pthread_create()/pthread_join() of a thread which just > exits, I'll occasionally see a very interesting thing -- > the app dies on an instruction fault on a kernel address. > > Enabling the DEBUG printtrap() calls in trap yeilds this information: > > login: > fatal user trap: > > trap entry = 0x2 (memory management fault) > a0 = 0xfffffc0000418be0 > a1 = 0x1 > a2 = 0xffffffffffffffff > pc = 0xfffffc0000418be0 > ra = 0x11ffbfc4 > curproc = 0xfffffe0006824cc0 > pid = 18788, comm = ex6 > > > Note that it is an instruction fault (a2 == -1) and the faulting > address maps to the bottom of witness_exit: > > (kgdb) l *0xfffffc0000418be0 > 0xfffffc0000418be0 is in witness_exit (../../kern/kern_mutex.c:1262). > 1257 m->mtx_line = line; > 1258 m->mtx_file = file; > 1259 p = curproc; > 1260 MPASS(m->mtx_held.le_prev == NULL); > 1261 LIST_INSERT_HEAD(&p->p_heldmtx, (struct mtx*)m, mtx_held); > 1262 } > 1263 > 1264 void > 1265 witness_exit(struct mtx *m, int flags, const char *file, int line) > 1266 { > > > The $ra looks reasonable, it is at least a userspace stack address. > > I think somebody saw this a while ago, but I cannot find their > message.. > > Any ideas? > > Drew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 14:32:17 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id AB21337B718 for ; Fri, 16 Mar 2001 14:32:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2GMV6G66826; Fri, 16 Mar 2001 14:31:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15026.37378.477855.889651@grasshopper.cs.duke.edu> Date: Fri, 16 Mar 2001 14:31:18 -0800 (PST) From: John Baldwin To: Andrew Gallatin Subject: RE: user process faulting on kernel address Cc: freebsd-alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16-Mar-01 Andrew Gallatin wrote: > > When running a linuxthreads app which basically sits in a loop > doing a pthread_create()/pthread_join() of a thread which just > exits, I'll occasionally see a very interesting thing -- > the app dies on an instruction fault on a kernel address. > > Enabling the DEBUG printtrap() calls in trap yeilds this information: > > login: > fatal user trap: > > trap entry = 0x2 (memory management fault) > a0 = 0xfffffc0000418be0 > a1 = 0x1 > a2 = 0xffffffffffffffff > pc = 0xfffffc0000418be0 > ra = 0x11ffbfc4 > curproc = 0xfffffe0006824cc0 > pid = 18788, comm = ex6 > > > Note that it is an instruction fault (a2 == -1) and the faulting > address maps to the bottom of witness_exit: > > (kgdb) l *0xfffffc0000418be0 > 0xfffffc0000418be0 is in witness_exit (../../kern/kern_mutex.c:1262). > 1257 m->mtx_line = line; > 1258 m->mtx_file = file; > 1259 p = curproc; > 1260 MPASS(m->mtx_held.le_prev == NULL); > 1261 LIST_INSERT_HEAD(&p->p_heldmtx, (struct mtx*)m, mtx_held); > 1262 } > 1263 > 1264 void > 1265 witness_exit(struct mtx *m, int flags, const char *file, int line) > 1266 { > > > The $ra looks reasonable, it is at least a userspace stack address. > > I think somebody saw this a while ago, but I cannot find their > message.. > > Any ideas? Weird. This might be related to the panics in witness_exit() during a LIST_REMOVE of the same list. Perhaps we are on an interrupt stack, but there should be some frames below witness_enter() if that were the case. :( > Drew -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 14:33: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F7E537B718 for ; Fri, 16 Mar 2001 14:33:05 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA08934; Fri, 16 Mar 2001 17:33:03 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2GMWXs82163; Fri, 16 Mar 2001 17:32:33 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15026.38017.557679.510377@grasshopper.cs.duke.edu> Date: Fri, 16 Mar 2001 17:32:33 -0500 (EST) To: mjacob@feral.com Cc: Andrew Gallatin , freebsd-alpha@FreeBSD.ORG Subject: Re: user process faulting on kernel address In-Reply-To: References: <15026.37378.477855.889651@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > Hah. On a related note, the faulting address for dumps that SIGSEGV' is in > fact, CURSIG in the kernel. Same ra range- user stack address. > > D'ya think they're related? Doug? Ah.. it was dump. Yes, I certainly think they're related.. I like this one better because I can reproduce it in 2 seconds instead of 2 hours.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 14:35:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1520737B719 for ; Fri, 16 Mar 2001 14:35:41 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA24627; Fri, 16 Mar 2001 14:35:38 -0800 Date: Fri, 16 Mar 2001 14:35:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: user process faulting on kernel address In-Reply-To: <15026.38017.557679.510377@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Matthew Jacob writes: > > > > Hah. On a related note, the faulting address for dumps that SIGSEGV' is in > > fact, CURSIG in the kernel. Same ra range- user stack address. > > > > D'ya think they're related? Doug? > > Ah.. it was dump. Yes, I certainly think they're related.. > > I like this one better because I can reproduce it in 2 seconds instead > of 2 hours.. Oh, it doesn't take 2 hours for me to reproduce it. But now that I know of the linux emulation stuff, I can stop looking in userland entirely. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 15:44:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id F1C1537B719 for ; Fri, 16 Mar 2001 15:44:16 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client32.quantum.net [192.168.56.32]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2GNhjw26125; Fri, 16 Mar 2001 18:43:45 -0500 (EST) Message-ID: <3AB2A530.9050006@videotron.ca> Date: Fri, 16 Mar 2001 18:43:44 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Serial communication problems was: Syslog reports weird things References: <15025.5868.345485.300691@grasshopper.cs.duke.edu> <15025.23622.509745.469218@grasshopper.cs.duke.edu> <3AB179A4.8050909@videotron.ca> <15025.32387.734109.233946@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > is gone. I browse lynx while yes running and nothing is sent to > > syslog. Seems you guessed right. (also, yes was sending outputs in > > both serial console and vga console) > > Woo hoo! You bet! > > > As for the serial communication problem, I don't beleive in a cabling > > one. The SRM console works fine, the booting process of FreeBSD is > > Have you tried it since you turned off the getty on "console" > I think that could be responsible for your serial problems too. Sorry, this does not help at all. I see the problem not only on the console but on ttyd0 as well. I can't use the serial port for incomming communications. Outgoing is fine tough... Normand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 17:38:37 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id 47DD537B71C for ; Fri, 16 Mar 2001 17:38:33 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client32.quantum.net [192.168.56.32]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2H1caw26311 for ; Fri, 16 Mar 2001 20:38:37 -0500 (EST) Message-ID: <3AB2C01C.9080509@videotron.ca> Date: Fri, 16 Mar 2001 20:38:36 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: vinum & dhcp3 port problems Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org vinum) I am having difficulties with vinum. I recently had to recreate my plexes so I resetted the configuration and started a fresh one. I had a raid1 configuration. Whenever I try to reate the mirror, vinum throws a segmentation fault "eg. mirror -n mirror /dev/da0g /dev/da2f". When I set verbose on, I get a core dump (sig 11 - don't you say it's my hardware, I can reproduce this as often as I want and no other part of the system is having this behaviour). I then tried to print the config and had another dump after seeing this line: "drive ve0 device". ve0 should have been vinumdrive0. I also found that ve0 and ve1 links are created in the current directory pointing into /dev/vinum/drive/veX. The vinum directory in /dev doesn't change at all. No volume/plex/sd is created. This looks like a bad pointer or something. Has vinum changed since 4.3-BETA20000308 ? dhcp3 port) I tried this port and found that it cannot answer any queries. I suspect an int size problem. dhcp2 port works fine, dhcp3 drops bogus hlen packets. (and there aren't any!) Normand Leclerc leclercn@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 17:43:56 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A4A3037B718 for ; Fri, 16 Mar 2001 17:43:54 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA14176; Fri, 16 Mar 2001 20:43:53 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2H1hNX82471; Fri, 16 Mar 2001 20:43:23 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15026.49467.787748.276474@grasshopper.cs.duke.edu> Date: Fri, 16 Mar 2001 20:43:23 -0500 (EST) To: mjacob@feral.com Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: user process faulting on kernel address In-Reply-To: References: <15026.37378.477855.889651@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > Hah. On a related note, the faulting address for dumps that SIGSEGV' is in > fact, CURSIG in the kernel. Same ra range- user stack address. Where in CURSIG? Was witness enabled? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 17:44:55 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7CD8337B71A for ; Fri, 16 Mar 2001 17:44:51 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA25511; Fri, 16 Mar 2001 17:44:53 -0800 Date: Fri, 16 Mar 2001 17:44:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: user process faulting on kernel address In-Reply-To: <15026.49467.787748.276474@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org First instruction. No- unless it's on by default now. > > Matthew Jacob writes: > > > > Hah. On a related note, the faulting address for dumps that SIGSEGV' is in > > fact, CURSIG in the kernel. Same ra range- user stack address. > > Where in CURSIG? Was witness enabled? > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Mar 16 18: 3:59 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id CB7BE37B718 for ; Fri, 16 Mar 2001 18:03:55 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 44A2E6AC94; Sat, 17 Mar 2001 12:33:53 +1030 (CST) Date: Sat, 17 Mar 2001 12:33:53 +1030 From: Greg Lehey To: leclercn@videotron.ca Cc: freebsd-alpha@freebsd.org Subject: Vinum(8) segfault on alpha (was: vinum & dhcp3 port problems) Message-ID: <20010317123352.F89962@wantadilla.lemis.com> References: <3AB2C01C.9080509@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB2C01C.9080509@videotron.ca>; from nospam@videotron.ca on Fri, Mar 16, 2001 at 08:38:36PM -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-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 16 March 2001 at 20:38:36 -0500, tcn wrote: > vinum) > > I am having difficulties with vinum. I recently had to recreate my > plexes so I resetted the configuration and started a fresh one. I had a > raid1 configuration. Whenever I try to reate the mirror, vinum throws a > segmentation fault "eg. mirror -n mirror /dev/da0g /dev/da2f". When I > set verbose on, I get a core dump (sig 11 - don't you say it's my > hardware, I can reproduce this as often as I want and no other part of > the system is having this behaviour). I then tried to print the config > and had another dump after seeing this line: "drive ve0 device". ve0 > should have been vinumdrive0. I also found that ve0 and ve1 links are > created in the current directory pointing into /dev/vinum/drive/veX. > The vinum directory in /dev doesn't change at all. No volume/plex/sd is > created. This looks like a bad pointer or something. > > Has vinum changed since 4.3-BETA20000308 ? I don't know that reference. If you mean 20010308 as a date, then "no". What I need is a debug version of vinum(8). Do this: cd /usr/src/sbin/vinum make clean make DEBUG_FLAGS=-g make install STRIP= Then run vinum as before and collect the dump. At this point I have a problem: I don't have access to an alpha, so I won't be able to analyse the dump unless you (or somebody else) give me access to a machine. The obvious thing to do would be to look at it on your machine, if that's possible. > dhcp3 port) > > I tried this port and found that it cannot answer any queries. I > suspect an int size problem. dhcp2 port works fine, dhcp3 drops bogus > hlen packets. (and there aren't any!) You shouldn't mention two unrelated problems in one message. The second one is liable to get missed. 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-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 17 5:19:15 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id 08BC437B718 for ; Sat, 17 Mar 2001 05:19:14 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client32.quantum.net [192.168.56.32]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2HDJ1w32132; Sat, 17 Mar 2001 08:19:01 -0500 (EST) Message-ID: <3AB36445.1090505@videotron.ca> Date: Sat, 17 Mar 2001 08:19:01 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-alpha@freebsd.org Subject: Re: Vinum(8) segfault on alpha References: <3AB2C01C.9080509@videotron.ca> <20010317123352.F89962@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Greg, Just updated my vinum and recompiled it. No more sig 11 but can't create any raid1 configuration. When I execute the command above, I get an error "Can't get config for drive 0: invalid argument". Can't print config, can't work it it yet. vinum subdir is created correctly tough. (meaning volume is there and plexes also) Normand. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 17 5:20: 5 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id 1196137B719 for ; Sat, 17 Mar 2001 05:20:03 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client32.quantum.net [192.168.56.32]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2HDK1w32139 for ; Sat, 17 Mar 2001 08:20:01 -0500 (EST) Message-ID: <3AB36480.6070008@videotron.ca> Date: Sat, 17 Mar 2001 08:20:00 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: dhcp3 port failing Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I tried this port and found that it cannot answer any queries. I suspect an int size problem. dhcp2 port works fine, dhcp3 drops bogus hlen packets. (and there aren't any!) Normand Leclerc leclercn@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 17 9:56: 9 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id 8553C37B71A for ; Sat, 17 Mar 2001 09:56:07 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client32.quantum.net [192.168.56.32]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2HHtvw32639; Sat, 17 Mar 2001 12:55:57 -0500 (EST) Message-ID: <3AB3A52C.1030709@videotron.ca> Date: Sat, 17 Mar 2001 12:55:56 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-alpha@freebsd.org Subject: Re: Vinum(8) invalid ioctl References: <3AB2C01C.9080509@videotron.ca> <20010317123352.F89962@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org While vinum isn't core dumping anomore, I get invalid ioctl ... I saw in the Makefiles that one of the causes for this could be the DEBUG flag. The thing is that this flag is present in both kernel module and vinum executable. Anyway, this was just an update to help. Normand Leclerc leclercn@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 17 15:11: 2 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 83EFD37B718 for ; Sat, 17 Mar 2001 15:10:59 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 40D656AB61; Sun, 18 Mar 2001 09:40:57 +1030 (CST) Date: Sun, 18 Mar 2001 09:40:57 +1030 From: Greg Lehey To: leclercn@videotron.ca Cc: freebsd-alpha@freebsd.org Subject: Re: Vinum(8) segfault on alpha Message-ID: <20010318094057.L89962@wantadilla.lemis.com> References: <3AB2C01C.9080509@videotron.ca> <20010317123352.F89962@wantadilla.lemis.com> <3AB36445.1090505@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB36445.1090505@videotron.ca>; from nospam@videotron.ca on Sat, Mar 17, 2001 at 08:19:01AM -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-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Saturday, 17 March 2001 at 8:19:01 -0500, tcn wrote: > Hi Greg, > > Just updated my vinum and recompiled it. No more sig 11 but can't > create any raid1 configuration. When I execute the command above, I > get an error "Can't get config for drive 0: invalid argument". Can't > print config, can't work it it yet. vinum subdir is created correctly > tough. (meaning volume is there and plexes also) I'll bet you haven't looked at what's in /var/log/messages. You'll almost certainly find ioctl conflicts there, indicating that your vinum(8) is out of sync with the kernel. In any case, check http://www.vinumvm.org/vinum/how-to-debug.html and do what it suggests there. 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-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 17 17:37:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from neutrino.quantum.net (modemcable037.229-201-24.mtl.mc.videotron.ca [24.201.229.37]) by hub.freebsd.org (Postfix) with ESMTP id CA89837B718 for ; Sat, 17 Mar 2001 17:37:22 -0800 (PST) (envelope-from nospam@videotron.ca) Received: from videotron.ca (client32.quantum.net [192.168.56.32]) by neutrino.quantum.net (8.11.1/8.11.1) with ESMTP id f2I1XEw33407; Sat, 17 Mar 2001 20:33:14 -0500 (EST) Message-ID: <3AB4105A.2040902@videotron.ca> Date: Sat, 17 Mar 2001 20:33:14 -0500 From: tcn Reply-To: leclercn@videotron.ca User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20010131 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-alpha@freebsd.org Subject: Re: Vinum(8) segfault on alpha References: <3AB2C01C.9080509@videotron.ca> <20010317123352.F89962@wantadilla.lemis.com> <3AB36445.1090505@videotron.ca> <20010318094057.L89962@wantadilla.lemis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Greg, I have seen this message but can't find the cause of it. I checked moth makefiles (vinum module and vinum program) and they both show the -DVINUMDEBUG. I recompiled the kernel and the program and I an still not synchronized. I don't have a core anymore so I don't know how to find the cause of my problem. Any ideas on how to debug this other than with a serial ddb ? The only error I get is indeed an invalid ioctl for vinum process but how to find the cause and how do I correct it? Also, just so you know, your email address seems not to be working. I can't send you any mail. (or is it wanted) Normand Leclerc leclercn@videotron.ca > I'll bet you haven't looked at what's in /var/log/messages. You'll > almost certainly find ioctl conflicts there, indicating that your > vinum(8) is out of sync with the kernel. In any case, check > http://www.vinumvm.org/vinum/how-to-debug.html and do what it suggests > there. > > 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-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Mar 17 18:19:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id F406237B718 for ; Sat, 17 Mar 2001 18:19:08 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id D97EE6AB60; Sun, 18 Mar 2001 12:49:05 +1030 (CST) Date: Sun, 18 Mar 2001 12:49:05 +1030 From: Greg Lehey To: leclercn@videotron.ca Cc: freebsd-alpha@freebsd.org Subject: Re: Vinum(8) segfault on alpha Message-ID: <20010318124905.C764@wantadilla.lemis.com> References: <3AB2C01C.9080509@videotron.ca> <20010317123352.F89962@wantadilla.lemis.com> <3AB36445.1090505@videotron.ca> <20010318094057.L89962@wantadilla.lemis.com> <3AB4105A.2040902@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB4105A.2040902@videotron.ca>; from nospam@videotron.ca on Sat, Mar 17, 2001 at 08:33:14PM -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-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Saturday, 17 March 2001 at 20:33:14 -0500, tcn wrote: >> I'll bet you haven't looked at what's in /var/log/messages. You'll >> almost certainly find ioctl conflicts there, indicating that your >> vinum(8) is out of sync with the kernel. In any case, check >> http://www.vinumvm.org/vinum/how-to-debug.html and do what it suggests >> there. > > I have seen this message but can't find the cause of it. I checked > moth makefiles (vinum module and vinum program) and they both show the > -DVINUMDEBUG. I recompiled the kernel and the program and I an still > not synchronized. Have you reloaded the Vinum module? > I don't have a core anymore so I don't know how to find the cause of > my problem. Any ideas on how to debug this other than with a serial > ddb ? Yes, they're in the URL I quoted. > The only error I get is indeed an invalid ioctl for vinum process > but how to find the cause and how do I correct it? > > Also, just so you know, your email address seems not to be working. > I can't send you any mail. (or is it wanted) That's because your mail host is incorrectly configured: > From double-bounce@lemis.com Sat Mar 17 23:49:15 2001 > Return-Path: > Delivered-To: grog@lemis.com > Received: by wantadilla.lemis.com (Postfix) via NOTICE > id 14DE96AB61; Sat, 17 Mar 2001 23:49:15 +1030 (CST) > Date: Sat, 17 Mar 2001 23:49:15 +1030 (CST) > From: MAILER-DAEMON@lemis.com (Mail Delivery System) > To: postmaster@lemis.com (Postmaster) > Subject: Postfix SMTP server: errors from modemcable037.229-201-24.mtl.mc.videotron.ca[24.201.229.37] > Message-Id: <20010317131915.14DE96AB61@wantadilla.lemis.com> > > Transcript of session follows. > > Out: 220 wantadilla.lemis.com ESMTP Postfix > In: EHLO neutrino.quantum.net > Out: 250-wantadilla.lemis.com > Out: 250-PIPELINING > Out: 250-SIZE 10240000 > Out: 250-ETRN > Out: 250 8BITMIME > In: MAIL From: SIZE=923 > Out: 250 Ok > In: RCPT To: > Out: 450 : Helo command rejected: Host not found > In: RSET > Out: 250 Ok > In: QUIT > Out: 221 Bye > > No message was collected successfully. It claims to be neutrino.quantum.net, but there's no DNS entry for this name. 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-alpha" in the body of the message