Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> "Francisco Reyes" writes:
: For one they are missing the references about genassym.

No.  They aren't.  You don't need to build genassym.  Buildkernel
takes care of all of that.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> "Francisco Reyes" writes:
: clarification...  I mean to say if someone would send-prg to
: update /usr/src/UPDATING.

What update is needed?  The instructions worked fine for me last time
I tried it?

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> "Francisco Reyes" writes:
: Would someone please send-pr the current instructsions to go
: from 3.4 to 4.X Stable.

cvsup 
cat /usr/src/UPDATING

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> Joe Royce writes:
: An alternative method of building a kernel is:
: 
: cd /usr/src/usr.bin/genassym
: make depend all install clean
: cd ../../usr.sbin/config
: make depend all install clean
: cd ../../sys/i386/conf
: config YOUR_KERNEL_HERE
: cd ../../compile/YOUR_KERNEL_HERE
: make depend && make
: make install
: 
: Then continue with the rest of the instructions.

This alternative method has been known to have problems, which is why
I replaced it with the method that currently is in UPDATING.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> "Francisco Reyes" writes:
: /usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found

UPDATING says:
[5] If you get warnings from ld-elf.so that it cannot load
libc.so, run 'ldconfig -R /usr/obj/usr/src/lib/libc' and repeat
the installworld target.

But you may need to substitute your own values of "/usr/obj" and
"/usr/src" in the above path.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: pcmcia fails to identify cards (4.0-stable cvsup 2000-06-26)

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> Alan Clegg writes:
: Any ideas?

Almost certainly a memory conflict.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Annoying reverse hylighting in `more' 4.0-STsnap0624

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> Harry Putnam writes:
: Good info here, I'm still bogged down trying to get a network up on a
: laptop with FreeBSD so getting tired of the obnoxious highlighting
: since I'm pooring thru manpages constantly right now.   Not that
: familiar with FreeBSD and its just enough different from Linux that
: most tools don't act quite the same.

If you are trying to install from scratch on a laptop, and don't have
a NetGear pccard card (or anything cardbus), then I'd suggest
installing from the latest 4.0-stable snapshot rather than from 4.0
release.  If you do have a netgear card, I'm sorry.  Some of the newer 
ones just don't work yet and need a lot of help.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: FreeBSD 3.5 now available for x86

2000-06-26 Thread Warner Losh

In message <4.3.2.7.0.2627022543.00ab0cc0@vivaldi> Sergei Vyshenski writes:
: So FreeBSD has two stable branches?
: Which one is more stable among stable for i386?
: Say for use at a site that need reliable round-the-clock
: gatewaing, named and mail operation?

I'd use 4.0-stable.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Almost serial consoles.

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> David Gilbert writes:
: While we have for some time used serial consoles from realweasel.com,
: we are faced with a number of server motherboards without ISA slots.
: I found it fairly easy to get the kernel to boot against the serial
: console and there is an option in the kernel config to set the console 
: speed.
: 
: It is also possible to set console="comconsole" in /boot/loader.conf,
: but I can't see a setting for the serial speed.  Is that possible?

Yes, but you must build bootblocks yourself.  Look in
sys/boot/${arch}/lib${arch}/comconsole.c for the COMSPEED parameter.

I have boot blocks that boot at 115200 over COM3 in an embedded SBC we 
at Timing Solutions have.  It works great, although we might not ship
the final proudct like this for other reasons.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: 4.0-Stable boot hangs

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> "Karel J. Bosschaart" writes:
: On 06/17 there was a change in sys/dev/ed/if_ed.c, which causes my ISA
: NE2000 compatible to hang at boot time, just like in your case. I contacted
: Paul Saab, who commited the change, about it and hope he will have a
: solution. As a quick workaround, you might try replacing if_ed.c with an
: 'old' one and recompile your kernel. I didn't try this myself. Instead
: I replaced my ISA NIC with a PCI NIC (also using ed0...) which works fine.
: If you go into config mode during boot and disable the ed driver the system
: will boot again - without network of course :-(. 
: (The change in if_ed.c had to do with probing newer cards).

Yes.  We really need to split up the ed driver into three new drivers: 
ne (for the ne2000), smc (for the smc based card) and ls (for linksys, 
although my off the cuff name sucks).  Probing is becoming much harder 
for these beasts and order is getting harder and harder to get right
for every card on the planet :-(

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Compatibility Question

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> Matt 
Heckaman writes:
: comparison to some, but I have a machine here running 512M of non-ECC for
: over a year now without any ram-related problems. (HD did die once though)

Without any ram-related problems that were detected you mean.  without 
ECC or parity, you may have some that go undetected...

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread Warner Losh

In message <[EMAIL PROTECTED]> "Francisco Reyes" writes:
: When I get to the point of building the kernel I get a number
: of syntax errors and the last line reports:

did you accidentally update to -current where lots of things changed?

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: microuptime() going backwards

2000-06-26 Thread Wilko Bulte

On Tue, Jun 27, 2000 at 12:03:49PM +1000, Greg Lehey wrote:
> [Format recovered--see http://www.lemis.com/email/email-format.html]
> 
> On Monday, 26 June 2000 at 22:56:29 +0200, Wilko Bulte wrote:
> > I just got tons and tons of
> >
> > Jun 26 22:06:33 freebie /kernel: microuptime() went backwards (18951.226366 -> 1 
>8951,199762)
> > Jun 26 22:06:34 freebie /kernel: microuptime() went backwards (18951.226366 -> 1 
>8951,210275)
> >
> > (approx 10Mb worth of them). This was during a mpeg video playing operation.
> >
> > FreeBSD freebie.wbnet 4.0-STABLE FreeBSD 4.0-STABLE #2: Sat Jun 24 16:52:41 CEST 
>2000 [EMAIL PROTECTED]:/usr/src/sys/compile/FREEBIE  i386
> >
> > System is an Athlon 700Mc, dmesg.boot available if required.
> >
> > Any idea what is causing this?
> 
> Yup.  Is this an Epox board?  I think it's a bug in the APM code.  It
> even bites if APM is disabled.  Try completely removing APM from the
> kernel.

No, it is an Abit KA7. But I will try removing apm, it is indeed in the
kernel. I'll see what happens next. Why does apm influence the time stuff?

-- 
Wilko Bulte http://www.freebsd.org  "Do, or do not. There is no try"
[EMAIL PROTECTED]   http://www.nlfug.nl Yoda - The Empire Strikes Back


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: 4.0-Stable boot hangs

2000-06-26 Thread John Holland

At 04:36 PM 6/26/00 +0200, Karel J. Bosschaart wrote:
>On Mon, Jun 26, 2000 at 10:06:03AM -0400, John Holland wrote:
> > Sunday, I did a fresh cvsup of RELENG_4, made and installed world and a 
> new
> > kernel.  The reboot hangs at the point the old kernel gets to the two ed*
> > devices (old Thomas Conrad NE2000 NICs).  Before this, the system was
> > working perfectly.
> >
> > Did something break in the ed driver in the two months since I last built
> > the system from source?
> >
>On 06/17 there was a change in sys/dev/ed/if_ed.c, which causes my ISA
>NE2000 compatible to hang at boot time, just like in your case. I contacted
>Paul Saab, who commited the change, about it and hope he will have a
>solution. As a quick workaround, you might try replacing if_ed.c with an
>'old' one and recompile your kernel. I didn't try this myself. Instead
>I replaced my ISA NIC with a PCI NIC (also using ed0...) which works fine.
>If you go into config mode during boot and disable the ed driver the system
>will boot again - without network of course :-(.
>(The change in if_ed.c had to do with probing newer cards).

Thanks.  That's exactly what I needed to know.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Fixing PCI device locations

2000-06-26 Thread Remy Nonnenmacher


I recently upgraded a server from 3.4 to 4-stable and was hurted by the
PCI device scanning not done in the same order on the two versions.

Mainly, the server have 6 SCSI busses over 3 devices and two PCI
busses. (da0 on 3.4 ended up on da52 under 4-stable)

While provisions are made for fixing SCSI controlers to busses (ieg: ahc
to scbus) and disks to scbuses, is there a way to fix SCSI controlers
to PCI locations ?

(something like "device ahc0 on pci0.11.1")

Thanks.

RN.
ItM




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: 4.0-Stable boot hangs

2000-06-26 Thread Karel J. Bosschaart

On Mon, Jun 26, 2000 at 10:06:03AM -0400, John Holland wrote:
> Sunday, I did a fresh cvsup of RELENG_4, made and installed world and a new 
> kernel.  The reboot hangs at the point the old kernel gets to the two ed* 
> devices (old Thomas Conrad NE2000 NICs).  Before this, the system was 
> working perfectly.
> 
> Did something break in the ed driver in the two months since I last built 
> the system from source?
>
On 06/17 there was a change in sys/dev/ed/if_ed.c, which causes my ISA
NE2000 compatible to hang at boot time, just like in your case. I contacted
Paul Saab, who commited the change, about it and hope he will have a
solution. As a quick workaround, you might try replacing if_ed.c with an
'old' one and recompile your kernel. I didn't try this myself. Instead
I replaced my ISA NIC with a PCI NIC (also using ed0...) which works fine.
If you go into config mode during boot and disable the ed driver the system
will boot again - without network of course :-(. 
(The change in if_ed.c had to do with probing newer cards).

Karel.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Compatibility Question

2000-06-26 Thread Matt Heckaman

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, 26 Jun 2000, Brad Knowles wrote:
: 
:   Ouch.  That is quite a lot of money, but then a shell server is 
: usually the sort of machine that gets pounded on the worst, and in 
: the worst ways -- all sorts of bizarre things that users try, some of 
: which are actively trying to break security and exceed their 
: authorized level of access, others that are just curious about this 
: new thing they just heard about, some who are just plain clueless, 
: etc

Yep tell me about it.

... 
:   Once you have a full list of all potential costs, you can then 
: assign estimates to their values.  Once you've done that, you can 
: then compare that total cost to the cost of the ECC RAM, and you can 
: figure out whether it really is worth it or not.

I think that since this is a leasing deal, the price of ECC ram sounded
alot more scary then it really is. When it comes down to monthly cost,
it's rather nominal in my opinion.

:   But your shop may be entirely different.

It is, but your practice is very sound. After all the discussion that has
been going on here in private e-mail, I've decided to go for the ECC mem
once I figured out that it wasn't really that bad when done with a lease
which is how we were going to do the server anyways :) Thanks for your
advice and suggestions.
 
: --
:These are my opinions -- not to be taken as official Skynet policy
: ==
: Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV
: Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
: Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
: http://www.skynet.be || Belgium
: 

* Matt Heckaman   - mailto:[EMAIL PROTECTED]  http://www.lucida.qc.ca/ *
* GPG fingerprint - A9BC F3A8 278E 22F2 9BDA  BFCF 74C3 2D31 C035 5390 *

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (FreeBSD)
Comment: http://www.lucida.qc.ca/pgp

iD8DBQE5V2iUdMMtMcA1U5ARAiQiAKCTB/wpJ0jmodwxGxYKO7VTm+vm5ACfXnuS
RAuTqcPHsyndRXnInRk8aX0=
=KWO2
-END PGP SIGNATURE-




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



4.0-Stable boot hangs

2000-06-26 Thread John Holland

Sunday, I did a fresh cvsup of RELENG_4, made and installed world and a new 
kernel.  The reboot hangs at the point the old kernel gets to the two ed* 
devices (old Thomas Conrad NE2000 NICs).  Before this, the system was 
working perfectly.

Did something break in the ed driver in the two months since I last built 
the system from source?



Here is the dmesg from the OLD, functioning kernel.

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-STABLE #1: Fri Jun  9 13:16:20 EDT 2000
 [EMAIL PROTECTED]:/usr/src/sys/compile/PIPPIN
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 132632297 Hz
CPU: Pentium/P54C (132.63-MHz 586-class CPU)
   Origin = "GenuineIntel"  Id = 0x52c  Stepping = 12
   Features=0x1bf
real memory  = 33554432 (32768K bytes)
avail memory = 29941760 (29240K bytes)
Preloaded elf kernel "kernel.orig" at 0xc02d3000.
Intel Pentium detected, installing workaround for F00F bug
md0: Malloc disk
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
isab0:  at device 7.0 on pci0
isa0:  on isab0
atapci0:  port 0xffa0-0xffaf at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0:  at 15.0
fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  at port 0x60,0x64 on isa0
atkbd0:  irq 1 on atkbdc0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppi0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
plip0:  on ppbus0
ed0 at port 0x320-0x33f iomem 0xd8000 irq 5 on isa0
ed0: address 00:80:13:c5:8c:25, type NE2000 (16 bit)
ed1 at port 0x300-0x31f iomem 0xd8000 irq 3 on isa0
ed1: address 00:80:13:49:6c:e2, type NE2000 (16 bit)
device_probe_and_attach: ex0 attach returned -1
IP Filter: v3.4.4 initialized.  Default = block all, Logging = enabled
ad0: 1033MB  [2100/16/63] at ata0-master using WDMA2
ad1: 1549MB  [3148/16/63] at ata0-slave using WDMA2
acd0: CDROM  at ata1-slave using PIO3
Mounting root from ufs:/dev/ad0s1a



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread Joe

On Mon, Jun 26, 2000 at 07:27:01AM -0400, Francisco Reyes wrote:
> Following the instructions from UPDATING.
> When I get to the point of building the kernel I get a number
> of syntax errors and the last line reports:
> 
> Specify machine type, e.g. ``machine vax''
> 
> I tried to put single and double quotes to my "machine" line
> with no luck.
> The archives returned two questions on this and one answer
> suggesting to put quotes which I already did.
> 
> Francisco
> 

I believe 4.x does not require quotes. Try without.

-Joe


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: lockups

2000-06-26 Thread Dave Boers

On Thu, Jun 22, 2000 at 11:39:47AM -0500, Pete Fritchman wrote:
> If it's up long enough, pretty high load.   Once people get a chance to
> get their processes back up, around 400-500 processes.  The machine can
> handle this though, it's a dual 550 MHz, with 768 MB ram.

Is the machine by any chance an Abit BP6 with dual Celeron's?

I recently solved my lockups (check the archives, also in the -smp
list, for details) by slightly increasing the processor voltage. The
machine was not overclocked, but it would crash at irregular intervals,
with an average uptime of about 1 week. The lockups I got sound exactly the
same as the ones you describe: not even Ctrl-Alt-Esc works. 

I increased the processor voltage from 2.00 to 2.05 volts in the bios and
the problem has gone away. The Abit BP6 mainboards have a history of power
stabilization problems.

Hope this helps, 

Dave Boers. 

-- 
   [EMAIL PROTECTED]  [EMAIL PROTECTED]
   PGP Key:   ftp://relativity.student.utwente.nl/pub/pgpkeys/djb.asc


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Kernel problem building from 3.4 stable to 4.X stable

2000-06-26 Thread andrew



On Mon, 26 Jun 2000, Francisco Reyes wrote:

> When I get to the point of building the kernel I get a number
> of syntax errors and the last line reports:
> 
> Specify machine type, e.g. ``machine vax''

I got this when I accidently cvsuped 3-STABLE rather than 4-STABLE on a
4.0-RELEASE box. Have you rebuilt config?

Andrew



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Serious stability problems (with my dmesg)

2000-06-26 Thread Morten A. Middelthon


Sorry, forgot the dmesg-output in my previous posting.
Here it is.

--
Morten A. Middelthon
Freenix Norge
http://www.freenix.no/


Jun 26 12:32:06 atreides /kernel: Copyright (c) 1992-2000 The FreeBSD Project.
Jun 26 12:32:06 atreides /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jun 26 12:32:06 atreides /kernel: The Regents of the University of California. All 
rights reserved.
Jun 26 12:32:06 atreides /kernel: FreeBSD 4.0-STABLE #1: Mon Jun 19 16:15:47 CEST 2000
Jun 26 12:32:06 atreides /kernel: root@atreides:/usr/src/sys/compile/atreides
Jun 26 12:32:06 atreides /kernel: Timecounter "i8254"  frequency 1193182 Hz
Jun 26 12:32:06 atreides /kernel: Timecounter "TSC"  frequency 499032503 Hz
Jun 26 12:32:06 atreides /kernel: CPU: AMD-K7(tm) Processor (499.03-MHz 686-class CPU)
Jun 26 12:32:06 atreides /kernel: Origin = "AuthenticAMD"  Id = 0x612  Stepping = 2
Jun 26 12:32:06 atreides /kernel: 
Features=0x81f9ff
Jun 26 12:32:06 atreides /kernel: AMD Features=0xc040
Jun 26 12:32:06 atreides /kernel: real memory  = 201261056 (196544K bytes)
Jun 26 12:32:06 atreides /kernel: config> q
Jun 26 12:32:06 atreides /kernel: avail memory = 192794624 (188276K bytes)
Jun 26 12:32:06 atreides /kernel: Preloaded elf kernel "kernel" at 0xc02c1000.
Jun 26 12:32:06 atreides /kernel: Preloaded userconfig_script "/boot/kernel.conf" at 
0xc02c109c.
Jun 26 12:32:06 atreides /kernel: Pentium Pro MTRR support enabled
Jun 26 12:32:06 atreides /kernel: npx0:  on motherboard
Jun 26 12:32:06 atreides /kernel: npx0: INT 16 interface
Jun 26 12:32:06 atreides /kernel: pcib0:  on motherboard
Jun 26 12:32:06 atreides /kernel: pci0:  on pcib0
Jun 26 12:32:06 atreides /kernel: pcib1:  at device 1.0 
on pci0
Jun 26 12:32:06 atreides /kernel: pci1:  on pcib1
Jun 26 12:32:06 atreides /kernel: isab0:  
at device 7.0 on pci0
Jun 26 12:32:06 atreides /kernel: isa0:  on isab0
Jun 26 12:32:06 atreides /kernel: pci0:  at 7.1
Jun 26 12:32:06 atreides /kernel: chip1:  at device 7.3 on pci0
Jun 26 12:32:06 atreides /kernel: pci0:  at 7.4 irq 11
Jun 26 12:32:06 atreides /kernel: pci0:  at 8.0 
irq 11
Jun 26 12:32:06 atreides /kernel: ahc0:  port 
0xdc00-0xdcff mem 0xebfef000-0xebfe irq 10 at device 10.0 on pci0
Jun 26 12:32:06 atreides /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
Jun 26 12:32:06 atreides /kernel: vr0:  port 
0xd400-0xd47f mem 0xebfedf80-0xebfedfff irq 9 at device 13.0 on pci0
Jun 26 12:32:06 atreides /kernel: vr0: Ethernet address: 00:80:c8:d9:f0:62
Jun 26 12:32:06 atreides /kernel: miibus0:  on vr0
Jun 26 12:32:06 atreides /kernel: amphy0:  on miibus0
Jun 26 12:32:06 atreides /kernel: amphy0:  10baseT, 10baseT-FDX, 100baseTX, 
100baseTX-FDX, auto
Jun 26 12:32:06 atreides /kernel: atkbdc0:  at port 
0x60,0x64 on isa0
Jun 26 12:32:06 atreides /kernel: atkbd0:  irq 1 on atkbdc0
Jun 26 12:32:06 atreides /kernel: vga0:  at port 0x3c0-0x3df iomem 
0xa-0xb on isa0
Jun 26 12:32:06 atreides /kernel: sc0:  on isa0
Jun 26 12:32:06 atreides /kernel: sc0: VGA <16 virtual consoles, flags=0x200>
Jun 26 12:32:06 atreides /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
Jun 26 12:32:06 atreides /kernel: sio0: type 16550A
Jun 26 12:32:06 atreides /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0
Jun 26 12:32:06 atreides /kernel: sio1: type 16550A
Jun 26 12:32:06 atreides /kernel: ppc0:  at port 0x378-0x37f irq 7 on 
isa0
Jun 26 12:32:06 atreides /kernel: ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in 
COMPATIBLE mode
Jun 26 12:32:06 atreides /kernel: ppc0: FIFO with 16/16/9 bytes threshold
Jun 26 12:32:06 atreides /kernel: Waiting 8 seconds for SCSI devices to settle
Jun 26 12:32:06 atreides /kernel: sa0 at ahc0 bus 0 target 0 lun 0
Jun 26 12:32:06 atreides /kernel: sa0:  Removable Sequential 
Access SCSI-2 device 
Jun 26 12:32:06 atreides /kernel: sa0: 3.846MB/s transfers (3.846MHz, offset 8)
Jun 26 12:32:06 atreides /kernel: da1 at ahc0 bus 0 target 6 lun 0
Jun 26 12:32:06 atreides /kernel: da1:  Fixed Direct 
Access SCSI-3 device 
Jun 26 12:32:06 atreides /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 
16bit), Tagged Queueing Enabled
Jun 26 12:32:06 atreides /kernel: da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 
2233C)
Jun 26 12:32:06 atreides /kernel: da0 at ahc0 bus 0 target 4 lun 0
Jun 26 12:32:06 atreides /kernel: da0:  Fixed Direct Access 
SCSI-2 device 
Jun 26 12:32:06 atreides /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 
16bit), Tagged Queueing Enabled
Jun 26 12:32:06 atreides /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 
1106C)
Jun 26 12:32:06 atreides /kernel: Mounting root from ufs:/dev/da0s1a
Jun 26 12:32:06 atreides /kernel: WARNING: / was not properly dismounted



Serious stability problems

2000-06-26 Thread Morten A. Middelthon


Recently I've experienced stability problems with one of my 4.0-STABLE
boxes. When it freezes/locks up I can still ping it, and I can change
between virtual consoles, but everything else is dead. Ctrl-alt-del
doesn't work, or any other input on the console, except for print-screen.

As far as I can tell there are no messages in the logs or on the console
telling me what's wrong. 

I just went through a 'make -j 4 world' with the source I updated a few
days ago in single-user mode, and that seemed to work without any
complaints.

I've attached the dmesg-output, so I probably don't have to explain what
hardware I've got. /usr and /home is using soft-updates.

The box is running apache 1.3.12 + php4, lotsof screens with irc and
pine/mutt, does email for a few domains, but doesn't have a significantly
high load. Usually 10-20 users are logged in, via ssh.

--
Morten A. Middelthon
Freenix Norge
http://www.freenix.no/




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Compatibility Question

2000-06-26 Thread Matt Heckaman

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, 26 Jun 2000, Douglas G. Allen wrote:
...
: I suggest you go look at http://www.crucial.com for memory.  It's Crucial's
: website, which means it's Micron memory.  I think they had 256M ECC modules
: for the PowerEdge listed for about $500 a piece.  I would say that the
: price you were quoted is rather high.

Sorry, I neglected to mention that the price I quoted was in Canadian
dollars. Which roughly works out to, 1,400$ USD I'll look at that though.

: Hope this helps with your questions.

Yes, thanks :)
 
:   Doug Allen
:   Tech Coordinator
:   Regional Offices of Education
:   #35 and #43
:   (LaSalle, Marshall, Putnam, and
:Woodford Counties Illinois)
: 

* Matt Heckaman   - mailto:[EMAIL PROTECTED]  http://www.lucida.qc.ca/ *
* GPG fingerprint - A9BC F3A8 278E 22F2 9BDA  BFCF 74C3 2D31 C035 5390 *

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.1 (FreeBSD)
Comment: http://www.lucida.qc.ca/pgp

iD8DBQE5V1JSdMMtMcA1U5ARAnWHAKCRf5M2HgaYHLP7uBYmFiOeifYAXACgxM2v
81LqnDTm0eTcui9rHX0L+rw=
=UDln
-END PGP SIGNATURE-




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Compatibility Question

2000-06-26 Thread Jim King


- Original Message -
From: "Matt Heckaman" <[EMAIL PROTECTED]>
To: "Brad Knowles" <[EMAIL PROTECTED]>
Cc: "FreeBSD-STABLE" <[EMAIL PROTECTED]>
Sent: Monday, June 26, 2000 6:42 AM
Subject: Re: Compatibility Question

Matt Heckaman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, 26 Jun 2000, Brad Knowles wrote:
>
> : It's been my experience that when you start talking about
> : significant amounts of RAM (anything over 128-256MB), you really,
> : *really*, *REALLY* want to be using ECC.
>
> Interesting, I've always personally thought ECC to be somewhat overrated
> and certaintly overpriced. Granted I do not have that much expierence in
> comparison to some, but I have a machine here running 512M of non-ECC for
> over a year now without any ram-related problems. (HD did die once though)
>
> ...
> : Depending on what you're doing, how much down time results, how
> : much your time costs per hour, and how much work is lost by all your
> : customers, a single crash could cost you more than the ECC RAM that
> : could have prevented that crash.
>
> I don't know, 512M (2x256) of ECC RAM will cost me 2,200$ - that's an
> awful nasty hit to be taking for what the server will do, which is a
> generally nasty business called shell services. In other words, there is
> no single client paying thousands of dollars for web hosting of their
> company's core page that will cost them (and me) a fortune for any
> downtime :) Given this situation, I've a hard time justifying that cost,
> which is only a few hundred dollars less then the *entire* machine is
> going to cost me, especially for it's role :)

Where are you buying your memory!?  Crucial (http://www.crucial.com) has
2x256MB ECC registered SDRAM for about $800; I'm sure other places have
similar (or better) prices.  Well worth it, IMHO.

Jim




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Announce: -stable commit lists

2000-06-26 Thread Sheldon Hearn



On Tue, 30 May 2000 07:52:09 -0400, David Miller wrote:

> I've setup freebsd-stable-3 and freebsd-stable-4 majordomo lists at
> sparks.net.  These use procmail to filter the RELENG_[3|4] messages out of
> cvs-all, so one can easily tell which commits affect them.

Are you using the new X-FreeBSD-CVS-Branch mail header?

Ciao,
Sheldon.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: Compatibility Question

2000-06-26 Thread Douglas G. Allen

Matt,

>Interesting, I've always personally thought ECC to be somewhat overrated
>and certaintly overpriced. Granted I do not have that much expierence in
>comparison to some, but I have a machine here running 512M of non-ECC for
>over a year now without any ram-related problems. (HD did die once though)

I'm moving all servers to ECC memory.  I think if you were running True
Parity (where the second number is divisible by 9), you'd be ok though -
based upon my machine at home.

>I don't know, 512M (2x256) of ECC RAM will cost me 2,200$ - that's an
>awful nasty hit to be taking for what the server will do, which is a
>generally nasty business called shell services. In other words, there is
>no single client paying thousands of dollars for web hosting of their
>company's core page that will cost them (and me) a fortune for any
>downtime :) Given this situation, I've a hard time justifying that cost,
>which is only a few hundred dollars less then the *entire* machine is
>going to cost me, especially for it's role :)

I suggest you go look at http://www.crucial.com for memory.  It's Crucial's
website, which means it's Micron memory.  I think they had 256M ECC modules
for the PowerEdge listed for about $500 a piece.  I would say that the
price you were quoted is rather high.

Hope this helps with your questions.

Doug Allen
Tech Coordinator
Regional Offices of Education
#35 and #43
(LaSalle, Marshall, Putnam, and
 Woodford Counties Illinois)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message