Re: DPT revision....(broken drivers in -STABLE)
"Matthew N. Dodd" wrote: Not having a test system with PCI DPT boards somewhat limits my ability to wring these things out. I won't refuse a rackmounted compaq with PCI and EISA slots and a brace of DPT and Smart2 RAID cards if someone sends me one. Who knows? I might even be able to beat a bit on the management tools then. Hi Matthew, If you remember - we spoke a while ago about some problems the DPT's had with the CAMified driver? - I did offer you a PCI DPT to try, but you thought you'd be OK at the time... I can hopefully still sort that out for you, if your interested - mail me off list... -Karl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest currents 'hang' on biord? [ Appears only on my system? :( ]
Matthew Dillon wrote: Make sure you have the absolute latest CURRENT. There was a situation that broken current a week or so ago for 2 days that could result in processes getting stuck in biord on SMP boxes. -Matt Matt, Like I thought - it doesn't seem to be affecting anyone else :( - I last cvsup'd and built the world on Friday 9th of July @ 22.10 - I had heard about the SMP machines getting stuck before, but was sure it was fixed by now... I'm re-cvsup'ing at the moment and running another buildworld to see if that works... Cheers, -Karl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Hang on biord? [ Appears only on my system? :( ] - Update
Karl Pielorz wrote: Matthew Dillon wrote: Make sure you have the absolute latest CURRENT. There was a situation that broken current a week or so ago for 2 days that could result in processes getting stuck in biord on SMP boxes. OK, source as of 10/Jul/99, 11.20am (BST) - SMP kernel hangs on 'biord', non-SMP kernel boots fine Anything I can try to trace this further? -Kp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Difference between building and running under -current vs. 3.2-Release?
Hi All, The combination of Apache + PHP + FreeTDS I use under 3.2-Release without problems, segfaults when it's built and run under -current (current as of about 2 weeks ago). i.e. I get "Segmentation fault - core dumped" when I try to run it. If I try to run gdb through the core file, that also segfaults as well, and dies... :( I'm no expert on debugging things, hence this email... By running httpd with gdb, I get the following output: " Program received signal SIGSEGV, Segmentation fault. 0x281c0177 in strncpy () from /usr/lib/libc.so.3 (gdb) bt #0 0x281c0177 in strncpy () from /usr/lib/libc.so.3 #1 0x2812de51 in tds_set_server (tds_login=0x6374652f, server=0x0) at login.c:57 #2 0x2812a3b9 in dbopen (login=0x281d894b, server=0x0) at dblib.c:398 #3 0x28199118 in endpwent () from /usr/lib/libc.so.3 #4 0x28198e83 in getpwnam () from /usr/lib/libc.so.3 #5 0x80c2185 in ap_uname2id (name=0x8101dc8 "nobody") at util.c:1799 #6 0x80ad4b1 in init_config_globals (p=0x815b00c) at http_config.c:1388 #7 0x80ad754 in ap_read_config (p=0x815b00c, ptemp=0x815e00c, confname=0x81575a0 "/usr/local/etc/apache/conf/httpd.conf") at http_config.c:1466 #8 0x80b6f26 in main (argc=3, argv=0xbfbfdba4) at http_main.c:4574 " Anyone got any suggestions as to why it builds and runs under 3.2, builds and faults under 4.0-current?. If I copy the httpd built on 3.2 and run that on -current, it also segfaults... Any suggestions where to go next? (i.e. who I should be talking to, the FreeBSD people, the Apache people, the PHP people, or the FreeTDS people?) The machine running this isn't production, but it does get very busy when it is used... It would have been nice to keep it as 4.0, but if I can't get it to build and run at all, I'll have to back it down to 3.2-Release... The machine is a P2-450, w/512mb RAM. The 3.2-Release box is a Pentium 233 with 64Mb of RAM. If it can't be fixed, or no one has any time I'll just back the box down to 3.2 - I just thought it would be nice to try :) Thanks, -Karl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Latest currents 'hang' on biord? [ Appears only on my system? :( ]
Hi, Any current's more recent than about a month ago on my main system seem to 'hang' on biord whenever they access the IDE drives... The system boots of SCSI, has a number of SCSI drives - but as soon as it either tries to mount, or fsck an IDE drive it just hangs... Breaking into DDB at the time and running PS shows either fsck, or mount in "biord" - even a simple DD results in the same hang... Hitting CTRL-C will quit the mount/fsck/dd command - but the system just doesn't seem to be able to access it's IDE drives? Has anyone got any suggestions? - I noticed this a while ago, and posted accordingly - but no one responded... If I boot an old kernel (like a month old) the system comes up OK, but any newer kernels and they just hang... I've tried rebuilding the kernel config from GENERIC, but it does the same :( System is an SMP dual P-Pro200, running on a SuperMicro P6DNF w/256Mb RAM, 3 x 2940's, and 4xIDE drives... Kernel config just says: controller wdc0at isa? port IO_WD1 irq 14 diskwd0 at wdc0 drive 0 diskwd1 at wdc0 drive 1 controller wdc1at isa? port IO_WD2 irq 15 diskwd2 at wdc1 drive 0 diskwd3 at wdc1 drive 1 dmesg for the above drives is below (I'd post the whole -v dmesg, but it's very long :( wdc0 at 0x1f0-0x1f7 irq 14 flags 0xff00ff on isa wdc0: unit 0 (wd0): QUANTUM FIREBALL SE4.3A, multi-block-16 wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc0: unit 1 (wd1): QUANTUM FIREBALL ST2.1A, multi-block-16 wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1 at 0x170-0x177 irq 15 flags 0xff00ff on isa wdc1: unit 0 (wd2): QUANTUM FIREBALL SE4.3A, multi-block-16 wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1: unit 1 (wd3): QUANTUM SIROCCO2550A, multi-block-8 wd3: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S wd3: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = Any suggestions? - I'd guess it's not a very prolific problem, as no one else seems to have the same symptoms? :( -Karl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: something's wrong with the in the last 24 hours with the sources
Tomer Weller wrote: doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop Same here... I got the error and decided it was be being out of date on all the egcs stuff going around (I've been away recently)... I just did a straight 'buildworld' -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
Kris Kennaway wrote: For about the past week I've been getting spontaneous reboots on my machine. As far as I can tell, there's no obvious common connection - most recently my box was under load at the time, but the time before that all I did was move the mouse (shades of Windows :-) and nothing else much was running. This does only seem to happen when I'm using the machine - after a few hours, a reboot is pretty much guaranteed (sounds like a resource leak of some kind to me). Beyond that, I don't know. My kernel and machine config haven't changed recently. Has anyone else been seeing this? What kind of information would help to narrow the problem down? The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? Also, you say when I moved the mouse - does that mean your machine lives in X-Windows all the time? - Does it crash when it's not running X etc? What type of video card does your machine have? The more detail you can provide (without going too OTT :-) - The more likely someone will be able to help :-) I have two boxes here tracking 4.0-current, and so far (looking for a nice piece of wood to touch), I've not seen any reboots on either for quite a long time (i.emonths) :) -Karl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
FTP client dies when not in passive mode?
This may have been covered before (searching the archives for 'ftp' wasn't such a hot idea :) Is there any way to stop the FTP client from either taking _ages_, or just dying stone dead (i.e. CTRL-\ is the only way out - forcing a core dump) when connecting through Firewalls that only allow Passive FTP? The moment you do an 'ls' or 'get' after having forgotten to do a 'pas' (to switch to passive mode) you suddenly find yourself unable to CTRL-C out of the FTP client - admittedly it does quit after around 5 minutes with 425 Can't build data connection: Connection timeout - Or should I just be grateful we have a passive mode, unlike some other Win/NT versions? :) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: FTP client dies when not in passive mode?
Sheldon Hearn wrote: See the ftp(1) manpage for an explanation. I know about the command line/environment variables that can be used to override this - but it's still annoying (see below)... In future, please refer general questions related to FreeBSD to the freebsd-questions mailing list -- freebsd-current is for issues relating specifically to CURRENT (4.0-CURRENT at the moment). It happens on -current as well as the past versions... I seem to remember someone mentioned it before, but I can't remember the outcome (I think it was mentioned on -current)... Surely it's behaviour should be consistant? - i.e. CTRL-C should abort the current transfer/command (which it does), _unless_ your the other side of a firewall without PASSIVE then CTRL-C does nothing, and your forced to wait, and wait - or dump core... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: zone: entry not free - Default of state of Invariants
Chuck Robey wrote: That's completely true, but nearly all users simply couldn't care less. They don't see the long view, they only see what's happening right now. With that I will agree... :) It's the reason that your attitude is totally correct healthy for a developer ... but the only thing that most users will see is the fact that FreeBSD panics more often. They won't even bother to make of note of why a panic occurred, all they will ever note is that a panic *did* occur. Why not make the default 'OFF' for non -current, and just tell the users it's there? I know quite a few FreeBSD users, and out of the bunch I reckon ~3 of them would turn it on, and be happy - the other 9 or so would leave it off, and still be happy... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Matthew Dillon wrote: I've been using -O2 kernels for over a year. Works fine as far as I can tell. I've had a few failures with -O2 ages ago, though I can't guess how long ages was - I definitely remember tracing one problem down to '-O' vs. '-O2', I stick to '-0' now religiously... (at least it rules it out of the equation - I hope g) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Luke wrote: === share/doc/psd/title [snip] groff: can't find `DESC' file groff:fatal error: invalid device `ascii' This has happened to me many times with various versions of current and 3.x , and its always fixed by lowering the -O# # , I don't know why I just know it works :). I re cvsupped several times once, and erased obj, and it always did it until i lowered the -O. Thanks! - That just fixed my problem... I was going to post a similar message along the lines of -current broken? - but you just saved me the embarassment! :)... I usually keep -O to just '-O' - I had been upping it recently, but then it started breaking even some of my simple programs, so leasson learn't, it's staying at just '-O' from now on in... (safety first? :-) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Maxim Sobolev wrote: Here is output (checked 2 times) :( groff: can't find `DESC' file groff:fatal error: invalid device `ascii' [super-snip] | groff -mtty-char -Tascii -t -s -me -o1- /dev/null groff: can't find `DESC' file groff:fatal error: invalid device `ascii' Ugh, did you have to send so much output? :-) - What -O setting are you using to build with? - Someone reported (and I've seen myself) - upping it will cause the problems above... (I'm not saying it's the only cause, but it got me :) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: adding DHCP client to src/contrib/
Sean Eric Fagan wrote about the security implications of making the bpf device the default in GENERIC etc. I'm sorry, but that's a complete non-issue: 1. /dev/bpf0 is mode 400, root.wheel -- to read it, you need to break root. 2. If you can break root, you can rebuild a kernel with BPF *anyway*. Sorry - I disagree with that... We run an ISP on FreeBSD, and we'd damn well notice someone _rebooting_ (or even trying to reboot one of our machines (to get their new kernel to work it's magic) - Heck, our machines _don't_ reboot from a 'shutdown -r'! - they're AST's! :) Whilst the argument about removing the source tree / kernel source etc. has always been pretty mute (what hackers not worth their salt don't come prepared? :) - I don't like the idea of every root exploiter just being able to 'instantly' sit there and run BPF! (Without even things like tripwire having a chance of detecting a kernel change). I'd much rather having the hacker either blocked from doing this, or having to spend time doing it (e.g. getting the source / new kernel to the machine etc. - the longer the better)... I think having bpf compiled in by default is going to be a Bad Move (tm). It _usually_ follows if some new user has the ability to recompile the kernel with it 'in' - they have enough sense to know the implications, put it in by default and you'll be giving every root hacker (or box where root access is sadly routine - and I know probably shouldn't be) an instant christmas present on those kind of machines... (I know theres probably ways of doing this with kern_secure_level, but that defaults to 'NO' at the moment :) Just my $0.04! (and no, it's not on fire... :) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
LD problems... (Pilot error no doubt)
I have a 4.0-current system which has been upgraded from 3.0-current... I keep getting errors such as: /usr/libexec/ld-elf.so.1: Shared object libmysqlclient.so.5.2 not found (There are numerous other ones for other libraries)... This stops anything that's in '/etc/rc.d' from starting (e.g. Apache, Samba, Squid etc.) If I manually run the /etc/rc.d/ contents after the machine has come up it all works fine... I'm guessing I've missed something - but I can't figure what? - As far as I can see ldconfig has no config file on FreeBSd, and it's confusing me (doesn't take much)... If I run 'ldconfig -elf -R -v' I get no output... If I run 'ldconfig -aout -R -v' I get a stream of all the libraries it found... Any help gratefuly received (as always :-) -Karl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Scsi chatty'ness can be good..
Geoff Buckingham wrote: Hopefully this isn't becoming a democracy, but just in case, the verbose reporting is a valued feature here. I'm pretty sure it's never going to go... The worst that seems to be threatened is that it's made an option (which is fine by me, I'd leave it turned on... All the time G)... I think one of the major advantages of *nix / linux is that it is so verbose... Maybe a new topic for -chat? G -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Celeron 333 kernel panic
Mike Zanker wrote: Having just upgraded my motherboard/CPU to a BX chip set and Celeron 333 I attempted to boot into my 3.0-STABLE system. However, as soon as the kernel starts to boot I get panic: cpu class not configured and the machine reboots (and so on...) Is this cpu supported? AFAIK it is support - are you sure you had cpu I686_CPU In your kernel config? -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: wd0: DMA failure, DMA status 0
Poul-Henning Kamp wrote: Is wd0: DMA failure, DMA status 0 something which needs looked at ? Poul-Henning Søren Schmidt posted a patch for this (was in the list a few days ago), if you look through the mail archives you should see it... I don't know if it's been comitted - I'm running it here fine though... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
Hi, Just finsihed upgrading to 4.0-Current, and both my machines now come up with: wd0: DMA failure, DMA status 0 wd0: DMA failure, DMA status 0 wd2: DMA failure, DMA status 0 wd2: DMA failure, DMA status 0 wd1: DMA failure, DMA status 0 wd3: DMA failure, DMA status 0 wd3: DMA failure, DMA status 0 wd1: DMA failure, DMA status 0 wd1: DMA failure, DMA status 0 (basically that error for all IDE drives installed). Both motherboards are P-Pro's (ones a dual, ones a single) - using Intel 440FX chipset's... DMesg shows: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x20002000 on isa wdc0: unit 0 (wd0): QUANTUM FIREBALL SE4.3A, DMA wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): QUANTUM FIREBALL ST2.1A, DMA wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x20002000 on isa wdc1: unit 0 (wd2): QUANTUM FIREBALL SE4.3A, DMA wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): QUANTUM SIROCCO2550A, DMA wd3: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S I never got these 'failures' before... (They keep popping up on the console as well :-( Can they be ignored? Can they be fixed? :) - The drives appear to work OK... The more the drives get access, the more messages I get (I guess understandably)... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE DMA problems? (4.0-current as of 01/24/99 ~01:10)
Søren Schmidt wrote: This is due to Julians commit in 1.183 (IIRC) of wd.c, its bogus :( The following patchh cures the mess, and fixes a couble of other nits as well: [snip] Thanks, the patch fixed the problem... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! New swapper and VM changes have been committed to -4.x
Boris Staeblow wrote: Make sure your /usr/src/lib/libkvm is updated. Also update /usr/src/include/kvm.h. Then update and recompile top, systat, and pstat. What about an kvmrebuild-target in the main Makefile? Would have the effect of a make build/install world actually do this? (working on the principal if it's needed by the world it should be built with the 'make buildworld' / installworld etc. -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems with new IDE's -current
Andrew Atrens wrote: On Sun, 17 Jan 1999, Karl Pielorz wrote: Karl, Let's see your (dmesg) probe messages ... :) they may shed some light on what's happening. I don't claim to be an expert on wd.c but from what I can tell it seems that controller and drive capabilities are probed separately, its conceivable you've hit upon an untested code path. ide_pci.c has been changing a lot lately (probably four times in the last seven days) - after capturing your dmesg output, try a fresh kernel and look for differences in probed controller/drive capabilities... Andrew. OK, I didn't want to post the dmesg as it's quite long, and I couldn't see anything relevant in it - but here goes... :) The machines running fairly recent -current from ~7th Jan... I've been trying to update recently but run into the same problems everyone else has... I'm hoping to get another build done today/tomorrow... re: Probed controller/drive capabilities - from the look of it (and assuming the Neptune is as old as it is) - it seems to be finding no g'o faster stripes', multiblock, DMA or anything (which is what I'd expect) - so I don't think it's getting the 'wrong mode' for the drives... -Kp --- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #1: Thu Jan 14 12:49:14 GMT 1999 r...@magpie.dmpriest.com:/usr/src/sys/compile/SMP-MAGPIE Timecounter i8254 frequency 1193182 Hz cost 4354 ns CPU: Pentium/P54C (586-class CPU) Origin = GenuineIntel Id = 0x521 Stepping=1 Features=0x7bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC,oldMTRR real memory = 16777216 (16384K bytes) avail memory = 14397440 (14060K bytes) Programming 16 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 eisa0: AST681 (System Board) Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: Intel 82434NX (Neptune) PCI cache memory controller rev 0x11 on pci0.0.0 ncr0: ncr 53c810 fast10 scsi rev 0x01 int a irq 15 on pci0.1.0 chip1: Intel 82375EB PCI-EISA bridge rev 0x04 on pci0.2.0 vga0: Cirrus Logic GD5446 SVGA controller rev 0x00 int a irq 10 on pci0.4.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color 16 virtual consoles, flags=0x0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x278-0x27f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): IBM-DTTA-351680 wd0: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): IBM-DTTA-351680 wd1: 16124MB (33022080 sectors), 32760 cyls, 16 heads, 63 S/T, 512 B/S lnc0 at 0x340-0x357 irq 9 drq 7 on isa lnc0: PCnet-ISA address 00:40:1c:60:36:ab npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 ccd0-1: Concatenated disk drivers SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: SEAGATE ST32430N 0510 Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problems with new IDE's -current
Hi, I have a system that's meant as a 'backup disk spool' - it has a 2Gb SCSI drive to boot from, and then 2 x 16Gb IDE drives (IBM-DTTA-351680's). The system works fine so long as I stick to using the SCSI drives... If I use the IDE's (e.g. backup another machine to them, tar / untar 'usr/src' to them) I start getting problems, e.g. Jan 14 13:01:42 magpie /kernel: wd0: interrupt timeout: Jan 14 13:01:42 magpie /kernel: wd0: status 58rdy,seekdone,drq error 0 Jan 15 17:56:52 magpie /kernel: lnc0: Missed packet -- no receive buffer Jan 15 17:57:43 magpie /kernel: lnc0: Missed packet -- no receive buffer The machine also has an NE-2100 embedded network card. We have 4 other identical machines to this, all SCSI based - all work without any problems... Is there anything that can be done? - at a guess I'd say the IDE's/wcd0 are timing out on interrupts, which is then stuffing the network (as the systems been waiting around too long for wcd0's IRQ's?)... The machine is a dual P90 (running SMP) - I get the problems even with a single CPU kernel... It's running Neptune chipset (quite old) - and only has 1 IDE channel. Any pointers? - The drives do appear to work OK, i.e. no corruption, but the _whole_ machine appears to 'stall' when the above occurs = not good... :-( I've tried 3.0-Release and 3.0-Current as of 7th Jan, '99 - Both exhibit identical symptoms... -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Heavy on the Verbosity (was) Re: Annoying messages on startup..
jack wrote: Nowhere near as annoying as tagged openings now xx. Perhaps `|| 1' could be changed to `|| crs-openings some critical number' in cam_xpt.c. As it is now a boy and a wolf come to mind. Coming from someone who's spent the best part of last week trying to diagnose various hardware software problems on NT Win'95 machines (to almost no avail), I'd appreciate as much verbosity being left _in_ the kernel FreeBSD as possible... I'm fed up with seeing Unknown error, or Unknown errors occured or Service Failed and the like on competitor / other products... Make them only 'if verbose' if you need to - just don't lose them alltogether!... :) -Karl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems with new IDE's -current
Lee Cremeans wrote: The machine is a dual P90 (running SMP) - I get the problems even with a single CPU kernel... It's running Neptune chipset (quite old) - and only has 1 IDE channel. I would say that this has something to do with the DMA support, but since Neptune's IDE controller isn't DMA capable and PCI, that doesn't follow. Chances are that there's a not-quite-bad spot on your drive -- does it always seem to happen in the same place on the disk? Nope, it's more 'load' oriented than 'spot' oriented (i.e. the harder you push them - the more of the above you get)... Both drives are brand new out the box (for what it's worth), so I doub't they're 'bad'... DMA is disabled in the kernel config as well, and the dmesg shows no hints of either multi-block or DMA transfers... Thinking that way I've tried another cable since (brand new out the bag - again 'for what it's worth') - and that has the same symptoms... So does running only 1 drive on the bus... :-( soapbox I have no love lost for Neptune boards; we have two of them at work, and it's like trying to work with a 486 board with an OverDrive chip on it. I'm also wary of Intel boards in general, since they tend to think they're smarter than you. /soapbox True, my second Pentium board was Neptune based (Plato-90?), and it had it's fare share of problems - but to be honest we've had no problems with these ones - their all in AST Premmia GX's - which are the backbone of our business systems at the moment... They work fine, except for this one (which is the only one using IDE). -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heavy on the Verbosity (was) Re: Annoying messages on startup..
Jordan K. Hubbard wrote: You can always have verbosity as a selective option. We're talking about what to do for the great majority of users who aren't in your shoes at all and don't want to be. True, although the messages (OK, admitadly not the ones we're talking about at the moment) are also usefull to others trying to diagnose the problem e.g. My hard drive doesn't work - help vs. My hard drive doesn't work, what does 'timed out during SCB mean?' ;-) You can always boot with -v to have the messages in question, I'm not talking about removing them so much as not making them the _default_. Don't worry, I don't want this to become NT either. :) That would suite me, and by the look of it - the majority of people... I'm pretty confident we'll never see the day of the likes of inetd[]: An unknown error occured while loading the pop3 service. The return data is the result code, 0x0f 0x02 0xff 0xfe. G -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems with new IDE's -current
On Mon, 18 Jan 1999, Bruce Evans wrote: New models of IBM IDE drives are fast enough to consume a significant fraction (perhaps 100%) of PIO mode 4 bandwidth (16.6 MB/s). Don't use them without DMA. Don't use them without UltraDMA (33.3 MB/s) if you want full performance. I presume the last don't should have been a 'do', i.e. _do_ use them with UltraDMA if you want full performance...? Also, the controller their running off isn't _Any_ DMA capable, at a guess it's going to be PIO4 tops, in which case (and as EIDA/UltraDMA are mean't to be 'backwards' compatible) - does this point to a bug/problem with the wdc driver? (i.e. drive too fast = wdc interrupt timeouts?) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Still safe to do a remote 'installworld'?
Am I still safe to do the equivalent of a 'remote' install world? - I have 2 x 3.0 boxes, one which is fresh 3.0-RELEASE, the other which is 3.0-CURRENT... If I take the /usr/src /usr/obj directories from sucsessful 'buildworld' on the -current machine can I run an 'installworld' on the -release machine? Or is it highly likely to stuff up because of all the recent elven changes etc? - Unfortunately the -release box isn't meaty enough to build the world... I gave up after around 16 hours a time and a few failures (which have been posted here, and subsequently fixed) - I'd kinda not like to have to wait another 16 hours to find any more problems ;-) - especially when the faster box can munch through it in around an hour flat... :) Regards, Karl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can the bootloader create a file or set a flag in the bootblocks?
Poul-Henning Kamp wrote: Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and have at least some assurance that I'll eventually be able to get back to a kernel I could use. Hmmm... This does rely on the 'stuffed-kernel' eventually cleanly rebooting the machine, we don't want anyone getting a 'false sense of confidence' out of this ;-) - A lot of the machines we use don't even reboot on a 'shutdown -r' :-( -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
