msdosfs borked ?
Hi. Just upgraded my system today to the latest -current, after my last venture into -current in May. Has MS-Dos filesystem support been broken ? I can't see any commits or notes in UPDATING, and hadn't read anything in -current about it. I am running devfs. Debugging output below : FreeBSD bofh.fw.uunet.co.za 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Aug 7 12:21:52 SAST 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BOFH4 i386 ad0: 4126MB ST34311A [8944/15/63] at ata0-master UDMA33 ad1: DMA limited to UDMA33, non-ATA66 compliant cable ad1: 19574MB IBM-DPTA-372050 [39770/16/63] at ata1-master UDMA33 The disk I'm interesting in mounting is ad1. 2=[root@bofh] ~# ls -al /dev/ad* crw-r- 1 root operator 116, 0x00010002 Aug 7 13:00 /dev/ad0 crw-r- 1 root operator 116, 0x0002 Aug 7 15:00 /dev/ad0s1a crw-r- 1 root operator 116, 0x00020001 Aug 7 13:00 /dev/ad0s1b crw-r- 1 root operator 116, 0x00020004 Aug 7 15:00 /dev/ad0s1e crw-r- 1 root operator 116, 0x00020005 Aug 7 15:00 /dev/ad0s1f crw-r- 1 root operator 116, 0x00020006 Aug 7 15:00 /dev/ad0s1g crw-r- 1 root operator 116, 0x0001000a Aug 7 13:00 /dev/ad1 crw-r- 1 root operator 116, 10 Aug 7 13:00 /dev/ad1c Fdisk reports : 3=[root@bofh] ~# fdisk ad1 *** Working on device /dev/ad1 *** parameters extracted from in-core disklabel are: cylinders=2495 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2495 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 12,(DOS or Windows 95 with 32 bit FAT, LBA) start 63, size 40082112 (19571 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED 5=[root@bofh] ~# mount_msdosfs /dev/ad1 /mnt/mnt mount_msdosfs: /dev/ad1: Invalid argument 6=[root@bofh] ~# kldstat Id Refs AddressSize Name 1 10 0xc010 262588 kernel 21 0xc1571000 7000 if_fxp.ko 31 0xc1579000 14000miibus.ko 41 0xc15c1000 4nfs.ko 51 0xc1625000 1a000usb.ko 61 0xc1657000 4000 logo_saver.ko 71 0xc1663000 4000 md.ko 81 0xc166d000 8000 cd9660.ko 111 0xc17db000 d000 msdosfs.ko Khetan Gajjar. --- [EMAIL PROTECTED]* Direct - +27 21 658 8723 UUNET South Africa * Mobile - +27 82 416 0105 http://www.za.uu.net* CSC- 08600 UUNET (88638) Systems Team* PGP Key- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Oddity after SMPNG kernel
Hi. I've upgraded my -current box from a pre-SMPNG kernel (an August vintage) to a post-SMPNG kernel (built today), and have noticed behaviour I haven't seen discussed in -current. I followed the instructions in UPDATING as well as discussed on the -current list, and the system boots with nothing out of the ordinary. There is no /modules, and the host is a UP machine. However, after approximately 20-30 minutes, it appears to slow down immensely, until it basically halts. Keyboard input at the console appears not to have any effect (although Caps, Scroll and Num lock work). The machine is pingable, and I can change VT's, but no input is accepted. All services on the box get as far as the Connected stage, but no banner appears. I left it for several minutes, and saw microuptime() went backwards (2757.4076411 - 2757.992648), with the right hand side number increasing periodically. After I hard-boot the machine it carries on as normal again for 20-30 minutes before reverting to it's zombie state. Booting a kernel prior to the SMPNG changes does not have the same problems. Should I revert to PRE_SMPNG days, with a cvsup tag of *default release=cvs tag=PRE_SMPNG ? Here is the output of dmesg : Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sun Oct 1 13:41:45 SAST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/CHAIN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200456354 Hz CPU: Pentium/P54C (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 117440512 (114688K bytes) config port sbc 0x220 config q avail memory = 110428160 (107840K bytes) Preloaded elf kernel "kernel" at 0xc039d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc039d09c. Intel Pentium detected, installing workaround for F00F bug ccd0-1: Concatenated disk drivers VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c1bfc (c0001bfc) VESA: S3 Incorporated. Trio64V+ npx0: math processor on motherboard npx0: INT 16 interface pcib0: SiS 5591 host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 atapci0: SiS 5591 ATA33 controller port 0x4000-0x400f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 irq 14 at devic e 0.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 isab0: SiS 85c503 PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: unknown card (vendor=0x1039, dev=0x0009) at 1.1 pcib1: PCI to PCI bridge (vendor=1039 device=0001) at device 2.0 on pci0 pci1: PCI bus on pcib1 pci0: S3 Trio graphics accelerator at 9.0 irq 5 de0: Digital 21041 Ethernet port 0xe000-0xe07f mem 0xea00-0xea7f irq 9 at device 11.0 on pci0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:f9:2f:c8 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 plip0: PLIP network interface on ppbus0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. de0: enabling 10baseT port ad0: 8693MB WDC AC29100D [17662/16/63] at ata0-master UDMA33 ad1: 1033MB WDC AC21000H [2100/16/63] at ata1-master WDMA2 Mounting root from ufs:/dev/ad0s1a Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenSSL and Apache+ModSSL
Around Yesterday, "Kris Kennaway" wrote : KK I'll take a closer look at this tonight and try and commit it to internat KK (and freefall), lag willing (if it passes a world build). If someone can KK confirm the world build for me in the meantime, it would save me the KK trouble. I didn't apply the patch, but hand pasted the line, and it survived a make world -DNOCLEAN and more importantly, works! Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OpenSSL and Apache+ModSSL
81 e7 06 ..so.}$.+w..0... 0290 - 03 55 1d 23 04 81 df 30-81 dc 80 14 3b 63 2e 78 .U.#...0;c.x 02a0 - 2b 36 dd 15 05 ea 73 6f-b3 7d 24 10 2b 77 02 c5 +6so.}$.+w.. 02b0 - a1 81 c0 a4 81 bd 30 81-ba 31 0b 30 09 06 03 55 ..0..1.0...U 02c0 - 04 06 13 02 5a 41 31 16-30 14 06 03 55 04 08 13 ZA1.0...U... 02d0 - 0d 43 61 70 65 20 50 72-6f 76 69 6e 63 65 31 12 .Cape Province1. 02e0 - 30 10 06 03 55 04 07 13-09 43 61 70 65 20 54 6f 0...UCape To 02f0 - 77 6e 31 17 30 15 06 03-55 04 0a 13 0e 4f 53 20 wn1.0...UOS 0300 - 55 73 65 72 73 20 47 72-6f 75 70 31 1e 30 1c 06 Users Group1.0.. 0310 - 03 55 04 0b 13 15 53 79-73 74 65 6d 20 41 64 6d .USystem Adm 0320 - 69 6e 69 73 74 72 61 74-69 6f 6e 31 1d 30 1b 06 inistration1.0.. 0330 - 03 55 04 03 13 14 62 6f-66 68 2e 6f 70 73 2e 75 .U.xxx.x 0340 - 75 6e 65 74 2e 63 6f 2e-7a 61 31 27 30 25 06 09 .xx.xx1'0%.. 0350 - 2a 86 48 86 f7 0d 01 09-01 16 1820489:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_lib.c:215: 6b 68 65 74 61 *.Hkheta 0360 - 6e 40 66 72 65 65 62 73-64 2e 6f 73 2e 6f 72 67 [EMAIL PROTECTED] 0370 - 2e 7a 61 82 01 00 30 0c-06 03 55 1d 13 04 05 30 .za...0...U0 0380 - 03 01 01 ff 30 0d 06 09-2a 86 48 86 f7 0d 01 01 0...*.H. 0390 - 04 05 00 03 81 81 00 62-00 38 25 f7 5d 35 4c b6 ...b.8%.]5L. 03a0 - 41 af 41 2f 46 57 90 a2-ae 19 a5 f8 A.A/FW.. read from 0807F4C0 [080953B1] (107 bytes = 0 (0x0)) Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
Around Today, "Donn Miller" wrote : DM I got disgusted with RP 5 because all of my favorite programs updated DM to G2 format, so I nuked it. Today I installed the latest linux-base DM port, downloaded the binary (non-rpm) version of linux RP 7 and it DM worked great. video and all. This is on an up-to-the-minute 5.0-Current. DM DM I think I found the problem -- it had "disable custom sampling rates" DM checked in the preferences section. I unchecked that, and at least I had it checked, and it wasn't an issue (on my SB Vibra 16). Oh well. The only issue is that the RealAudio plugin doesn't work with Netscape :-( Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: yes, current is broke...
Around Yesterday, "Jeffrey J. Mountin" wrote : Need to wait for him to either run out of code to commit or steam or Dew or smokes or whatever's keeping him going. Then we can all resume building. 1. There no end of code to commit 2. His car uses 97 Octane 3. He doesn't drink Mountain Dew (at least, not a significant enough amount that I'd notice) 4. He doesn't smoke I think it's driven by a desire to see ssh in the tree ;-) Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: So, tell me again why we can't read audio CDs in SCSI drives?
Around Yesterday, "Kenneth D. Merry" wrote : Many of the opinions I've seen recently are that you jitter correction isn't necessary for most newer CDROM drives. If you want jitter correction, you can port cdd to CAM. cdda2wav does jitter correction - -P sectors --set-overlap sets the initial number of overlap sectors for jit- ter correction Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za/ * http://www.freebsd.org/ * information at System Administration * http://link.os.org.za/ * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm and non-PnP SoundBlaster Vibra 16 4.13
Hi. I have been following the thread(s) about getting the SoundBlaster Vibra 16 sound-cards working in -current, and it appears that if you have a PnP card, it seems to be working. I do not have a PnP version of this card, and the last time I was able to get the sound card recognised was October 2nd. A verbose boot of that kernel reveals sb_probe: no addr, trying (0x220, 0x240) pcm: SoundBlaster 16 4.13) at irq 10 drq 3 flags 0x17 on isa0 sb_probe: no addr, trying (0x220, 0x240) pcm: setmap 4c, ff00; 0xc80b500 - 4c000 pcm: setmap 4d, ff00; 0xc80c500 - 4d000 and /dev/sndstat reveals FreeBSD Audio Driver (newpcm) Oct 2 1999 14:30:27 Installed devices: pcm0: SoundBlaster 16 4.13 at io 0x220 irq 10 drq 3:7 (1/1 channels duplex) With subsequent kernels, including a -current kernel from 20 Dec, the sound card is not detected. The definitions I'm using in my kernel currently (no pun intended :) are #sound card device pcm0 device sbc0 at isa? port ? irq 10 drq 3 flags 0x17 as compared to what I had device pcm0 at isa? port ? irq 10 drq 3 flags 0x17 The card is probed if the machine is booted with a kernel of Oct 2, and not probed if the machine is botted with a kernel of Dec 20. The only other thing I can think of is that the old kernel had support for PnP, whereas the new ones doesn't. This shouldn't matter though if I'm supplying the parameters directly to the card. Khetan Gajjar. --- [EMAIL PROTECTED] * [EMAIL PROTECTED]* PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za/ * http://www.freebsd.org/ * information at System Administration * http://link.os.org.za/ * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CMAP2 busy ?
Hi. I've been experiencing problems with my machine crashing when in X, when idle overnight. Normally it panics with XF86_S3. Today however the machine returned something a little different, which I haven't seen before. I hope this helps someone. The machine worlds with no problems, and is perfectly stable when in console mode. X has been rebuilt several times. GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 3559424 initial pcb at 29d280 panicstr: pmap_zero_page: CMAP2 busy panic messages: --- panic: pmap_zero_page: CMAP2 busy syncing disks... 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 done dumping to dev #wd/0x20001, offset 77824 dump 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 280 dumppcb.pcb_cr3 = rcr3(); (kgdb) quit --- Khetan Gajjar (!kg1779) * [EMAIL PROTECTED] http://khetan.os.org.za/ * Talk/Finger [EMAIL PROTECTED] FreeBSD enthusiast* http://www2.za.freebsd.org/ /dev/random output : Nihil est--in vita priore ego imperator Romanus fui. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
Around Yesterday, "David Scheidt" wrote : DS I had a panic tuesday, due to trying to load a broken module. I got the DS same panic: Timeout table full message. Interestingly, savecore seems to I've been getting these really odd panics as well (which I reported but no-one seemed interested), with that error. In the one case where I provoked it (by loading a kld that was out of sync with the kernel), I also got that error. I'm using the "experimental" ATA code though; are you using IDE disks with the ATA or old WD driver, or are you using SCSI disks ? --- Khetan Gajjar (!kg1779) * [EMAIL PROTECTED] http://khetan.os.org.za/ * Talk/Finger [EMAIL PROTECTED] FreeBSD enthusiast* http://www2.za.freebsd.org/ /dev/random output : I am under the influence of sugar, caffeine, and lack of sleep, and should not be held responsible for my behavior. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trap 12's with various programs over the last 4 weeks
On Sun, 3 Oct 1999, Khetan Gajjar wrote: Vibra 16 sound card, but this hasn't worked since newpcm. I lied; I never noticed that was working again : pcm0: SoundBlaster 16 4.13 at irq 10 drq 3 flags 0x17 on isa0 Missed it because I only use the soundcard occasionally sp!. --- Khetan Gajjar (!kg1779) * [EMAIL PROTECTED] ; [EMAIL PROTECTED] http://www.os.org.za/~khetan * Talk/Finger [EMAIL PROTECTED] FreeBSD enthusiast* http://www2.za.freebsd.org/ Stupidest quote heard : Who is this BSD, and why should we free him ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Different SCSI probe behavior
On Sat, 15 May 1999, Bret A. Ford wrote: Waiting 10 seconds for SCSI devices to settle aha0: ahafetchtransinfo - Inquire Setup Info Failed (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out (probe20:aha0:0:5:0): CCB 0xc553b450 - timed out aha0: No longer in timeout I'm seeing the same thing, but for 3 of my devices on a chain with 4 devices. It takes quite long, but doesn't appear to do any damage or decrease functionality (so far that is). Do I need to update something for normal behavior? I've been following freebsd-current and cvs-all, though I might have missed something that would have clued me in. I've seen Werner Losch discovering a problem with the aha driver in -stable, and he committed a fix for that. Is it possible for that fix to be MFS ? --- Khetan Gajjar (!kg1779) * khe...@iafrica.com ; khe...@os.org.za http://www.os.org.za/~khetan * Talk/Finger khe...@chain.freebsd.os.org.za FreeBSD enthusiast* http://www2.za.freebsd.org/ Security-wise, NT is a OS with a kick me sign taped to it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: PCI VGA card becomes ISA
Around Today, Doug Rabson wrote : DR Its harmless and it should go away soon if we can reorganise syscons' vga DR driver slightly. I'm seeing this as well, but as you've said, it's harmless. What I am concerned about is from sources last night, the error haveseen_isadev() called - FIXME! after the isa0 bus has been probed, and something I haven't seen before : (cd1:aha0:0:6:0): CCB 0xc51952e0 - timed out indicating a problem with my Yamaha CD-RW. Is this something serious ? As an aside, I'm trying Soren's ATA code, and it combined with the new-bus changes (neither of which I was using before) has made a dramatic difference speed-wise (or maybe it's just a placebo effect). Nice work :) Dmesg below. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Apr 20 13:00:36 SAST 1999 khe...@chain.freebsd.os.org.za:/usr/src/sys/compile/CHAIN Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 200455994 Hz CPU: Pentium/P54C (200.46-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping=12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 100663296 (98304K bytes) avail memory = 94699520 (92480K bytes) Preloaded elf kernel kernel at 0xc02d9000. ccd0-1: Concatenated disk drivers Probing for PnP devices: npx0: math processor on motherboard npx0: INT 16 interface pcib0: PCI host bus adapter on motherboard pci0: PCI bus on pcib0 chip0: Host to PCI bridge (vendor=1039 device=5591) at device 0.0 on pci0 ata0: Unknown PCI IDE controller at device 0.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 isab0: SiS 85c503 PCI-ISA bridge at device 1.0 on pci0 pcib1: PCI to PCI bridge (vendor=1039 device=0001) at device 2.0 on pci0 pci1: PCI bus on pcib1 de0: Digital 21041 Ethernet at device 11.0 on pci0 de0: interrupting at irq 5 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:f9:2f:c8 isa0: ISA bus on motherboard haveseen_isadev() called - FIXME! aha0 at port 0x330-0x333 irq 11 drq 6 on isa0 aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs aha0: interrupting at irq 11 atkbdc0: keyboard controller (i8042) at port 0x60 on isa0 atkbd0: AT Keyboard on atkbdc0 atkbd0: interrupting at irq 1 psm0: PS/2 Mouse on atkbdc0 psm0: model IntelliMouse, device ID 3 psm0: interrupting at irq 12 vga0: Generic ISA VGA on isa0 sc0: System console on isa0 sc0: VGA color 16 virtual consoles, flags=0x0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ppc0 at port 0x378 irq 7 on isa0 ppc0: Winbond chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 ppc0: interrupting at irq 7 de0: enabling 10baseT port Intel Pentium detected, installing workaround for F00F bug ata0: master: settting up generic WDMA2 mode OK ad0: WDC AC21000H/21.15T71 ATA-? disk at ata0 as master ad0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=-1 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: settting up generic WDMA2 mode OK ad1: QUANTUM FIREBALL1080A/A1M.0900 ATA-? disk at ata0 as slave ad1: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=-1 ad1: 8 secs/int, 0 depth queue, DMA mode ata1: master: settting up generic WDMA2 mode OK ad2: ST32140A/07.07.01 ATA-? disk at ata1 as master ad2: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=-1 ad2: 16 secs/int, 0 depth queue, DMA mode Waiting 15 seconds for SCSI devices to settle changing root device to wd1s1a da0 at aha0 bus 0 target 2 lun 0 da0: QUANTUM LPS540S 5900 Fixed Direct Access SCSI-2 device aha0: ahafetchtransinfo - Inquire Setup Info Failed da0: 3.300MB/s transfers da0: 516MB (1057616 512 byte sectors: 64H 32S/T 516C) da1 at aha0 bus 0 target 4 lun 0 da1: CONNER CFA540S 14B1 Fixed Direct Access SCSI-2 device da1: 3.300MB/s transfers da1: 515MB (1056708 512 byte sectors: 64H 32S/T 515C) cd0 at aha0 bus 0 target 5 lun 0 cd0: NEC CD-ROM DRIVE:502 2.0r Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [325725 x 2048 byte records] (cd1:aha0:0:6:0): CCB 0xc51952e0 - timed out (cd1:aha0:0:6:0): CCB 0xc51952e0 - timed out aha0: No longer in timeout cd1 at aha0 bus 0 target 6 lun 0 cd1: YAMAHA CRW4260 1.0q Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems in VM structure ?
On Tue, 16 Feb 1999, Matthew Dillon wrote: MD Try reducing maxusers to 128. Another person reported similar behavior MD to me and after a bunch of work he tried going back to a basic MD distribution -- and everything started working again. Hmmm, ok. MD It turned out that a maxusers value of 256 and 512 were causing his machine MD to go poof, but a maxusers value of 128 worked fine. Ok. I'm glad, in a way, that I'm not the only one seeing this. The really weird thing though is that since reporting the problem, it hasn't re-occured. If it occurs again, I'll mail the results of the gdb -core /var/crash/blah, a trace and then try reducing the number of maxusers. This is the longest uptime I've had in almost two weeks - 14 hours. Here's hoping :) MD I haven't tracked the problem down yet. Please try reducing your maxusers MD to 128 and email the results to current. If the problem re-occurs, I'll do so :) --- Khetan Gajjar (!kg1779) * khe...@iafrica.com ; khe...@os.org.za http://www.os.org.za/~khetan * Talk/Finger khe...@chain.freebsd.os.org.za FreeBSD enthusiast* http://www2.za.freebsd.org/ Security-wise, NT is a OS with a kick me sign taped to it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problems in VM structure ?
at ppbus? device ppi0at ppbus? --- Khetan Gajjar (!kg1779) * khe...@iafrica.com ; khe...@os.org.za http://www.os.org.za/~khetan * Talk/Finger khe...@chain.freebsd.os.org.za FreeBSD enthusiast* http://www2.za.freebsd.org/ Security-wise, NT is a OS with a kick me sign taped to it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld FAILS for 2 days!!!!
-BEGIN PGP SIGNED MESSAGE- On Tue, 9 Feb 1999, Maxim Sobolev wrote: MS It seems to me that most of all people in the developer list carried MS away with DHCP issue and just ignore that buildworld fails continuously MS for 2 days in /usr/src/sys/i386/ibcs2/ibcs2_ipc.c. Please get rid of MS it!!! I'm a FreeBSD user. I can't code, so I don't contribute in the code sense to the project. However, your e-mail (and many of it's ilk) raises my hackles, and I'll tell you why : 1. If you have a problem, and you're running -current, and you are 100% sure that this is affecting everyone, format a nice e-mail with sufficient details, and mail it to the list (assuming you've read the list to ensure that the problem isn't specific to you, or hasn't already been fixed). Or ask someone else you know who is running -current if they're experiencing the same problem. Or check your commit mail to see what has changed in the file(s) that is affecting you. 2. This is a co-operative project; no-one is getting paid for this, and no-one appreciates getting moaned at for something they've done for (economically speaking) free. 3. You're running -current. This assumes that you're enough of a developer (and NOT a user) to fix problems. If you can't, run - -stable or -release. 4. The people in the developer list (note: DEVELOPer list) are discussing a relatively important question about something entering the source tree. Unlike other free OS projects, in this one, most things get a good airing and people can air their views. It's a kind of a democratic autocracy. I love FreeBSD; I like the support I've received, and the lack of support at times is frustrating, but it's taught me to look for information before banging on my keyboard to the nearest @freebsd.org mailing list. I suggest you realise that unless you're paying for support and development, you're not guarenteed access to or quality of either. I can recommend a fair, commercially supported NOS - NT; you'll pay for (and sometimes receive) support, but bear in mind you can't reach their developers. EXTREMELY satisfied 4.0-current and 2.2.6-release user. - --- Khetan Gajjar (!kg1779) * khe...@iafrica.com ; khe...@os.org.za http://www.os.org.za/~khetan * Talk/Finger khe...@chain.freebsd.os.org.za FreeBSD enthusiast* http://www2.za.freebsd.org/ Security-wise, NT is a OS with a kick me sign taped to it -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBNsCxCV0slw2AMOJdAQEq0wP/bYO1capvfoUugmFrxKiqui2k0V6M9vPB xeEmmUdbfnWanyvImKVoD1bB27gd8yXAnCkYd86UXCORQ+Kfvb36xKswK8MK88BY kFadnmCS636vvs5his6uOeVHmWKMwO5D+DiOghvlXJUvmluAL6lQ3FM0/Gq8mguw PgaZchYvdbE= =w674 -END PGP SIGNATURE- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
