Re: UPDATE: ATA mkIII first official patches - please test!

2005-02-10 Thread Søren Schmidt
Emanuel Strobl wrote:
Am Mittwoch, 9. Februar 2005 15:00 schrieb Søren Schmidt:
[...]
As always, enjoy and let me know how it goes...

It's running here on several RELENG_5 machines. Like with j I also can't find 
any problems with k :)
But the strange 16MB/s limit on my ICH2 (i815 B-step (tualatin)) machine still 
exists and still if I use the command atacontrol mode 0 udma5 udma5 the 
limit vanishes but only when typed interactively, no go by setting the udma5 
mode (which is actualy already set at probing) in any rc script.
Still reproducale but I have absolutely no idea how this can be :(
Hmm, strange, anyhow I've managed to scavenge an ICH2 based board here, 
I just need to locate a CPU that fits then I'll look into this mess..

--
-Søren
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: UPDATE: ATA mkIII first official patches - please test!

2005-02-10 Thread Søren Schmidt
Tim Welch wrote:
A problem still exists with 48-bit addressing. This url details a fix
I've been using for the last 4 months or so with no issues yet.
http://lists.freebsd.org/pipermail/freebsd-hackers/2004-October/008821.html
Are you stil experiencing problems with atamkIII ?
In that case its a different problem since atamkIII (as well as current) 
has this fixed..

--
-Søren
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: UPDATE: ATA mkIII first official patches - please test!

2005-02-10 Thread Dag-Erling Smørgrav
Søren Schmidt [EMAIL PROTECTED] writes:
 New version that fixes known problems so far etc now available:

ah, just commit it already.  it works for me, so it must be good enough ;)

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re[2]: interrupt routing

2005-02-10 Thread dima
 Ah, so they are all on the same bus.  Yuck, performance is going to be
 sucky. Bad Tyan, no cookie.  That'll also explain the limited number
 of interrupts available.  I don't think there's anything we can do to
 help the situation, sadly.
 
 Buy a PCI-X SCSI/GigE card, and use that instead of the on-board one?
 Neither of our S288[12]'s are sharing any IRQ's; we're using Adaptec
 2120S RAID cards, and they have a bus and IRQ to themselves.
Thanks for your suggestion; I will think about purchasing a NIC.

 MySQL performance still sucks on our FreeBSD machine, but that's an OS
 problem; the hardware looks fine to me.  If you have suggestions for a
 better dual Opteron motherboard I'm all ears :)
I didnt have a chance to try MSI stuff yet; it contains a single channel SCSI 
onboard though. Its not that good for future HD expansion in my deployment. I 
set up 4 drives (60MB/s*4 is quite ok for a SCSI-320) for database now and 
directed the 2nd SCSI channel to the backplane.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: compile kernel problem

2005-02-10 Thread Ivan Roth
Kris Kennaway wrote:
On Thu, Feb 10, 2005 at 02:39:38AM +0100, Ivan Roth wrote:
 

no, I don't think so. I read carefully the handbook's section and I 
quote it:
   

I said to read the comments in the GENERIC kernel, not the handbook.
e.g.  if you commented out SCSI support, you probably left in the USB
mass storage device (umass), which requires SCSI and will leave your
kernel uncompilable.
Kris
 

ok. I didn't know that and should have read more carrefully :)
but it doesn't matter since I realized I need the SCSI support.
But for example, do I need to keep all the lines for the SCSI 
peripherals or can I keep just some of them. How to know if iPod need 
this one or this other line?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


5.3-Stable network issue

2005-02-10 Thread Martin Minkus
I seem to have been having a rather strange networking issue in FreeBSD
5.3-Stable (it started happening immediately after 5.2.1 and has persisted
since.. I keep ³hoping² that next time I cvsup it will be fixed, but no).

I downgraded back to 5.2.1-p13 and it is perfectly fine once again.


*** Some background information:

My FreeBSD box is my home NAT router, server, firewall, etc. It does DHCP,
MX for some of my domains, secondary DNS (I got primary elsewhere), apache
for some webhosting, blah blah blah. Nothing really special. It is a Dual
PIII-500, 512mb ram, and a couple ATA hdd¹s. Had 3 realtek network
interfaces, but down to 2 now.

*** The problem:

Networking simply stops or locks up. Why, I don't know. I believe
initially it happened for all 3 network cards... I thought tcp/ip processing
or something in the kernel got locked. It happens every 30 minutes to an
hour, and lasts about 60 seconds to 120 seconds. Unfortunately, 60 seconds
to 120 seconds is long enough to kill messenger (my gf does not like),
online gaming, etc etc.

Lately, I had taken one of the realtek cards out (it was for a several km
long wireless link) and moved the server to my gf's place (where I am now
100% of the time). So now that I have the server locally and rely on it for
my internet connection, this has become a real PAIN.

I've noticed that I can remain ssh'd into diablo, do whatever I want while
this lock issue occurs. So the lan interface rl0 is fine. The internet
interface, rl1 (which goes to the cable modem) locks up. (btw, its not the
cable modem as I am using my gf's now, and it did this at my place on my
cable modem too, which is a different brand. Nortel at my place, motorola at
my gfs).

*** Attempts:

I've attempted switching out network cards, and places 3 other realtek cards
in. Different brands, all with different revisions (D instead of B, etc,
etc).

No matter what I try, nothing fixes it. The machine seems perfectly
repsonsive, and I am still ssh'd in and can do whatever I want on it... But
the network card going to the cable modem has stopped responding?!

This never happened during 5.0-Current all throughout 5.2.1-STABLE, but
anywhere beyond 5.2.1 it craps itself.


*** Dmesg output:

Copyright (c) 1992-2004 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.2.1-RELEASE-p13 #2: Thu Feb 10 18:39:33 CST 2005
[EMAIL PROTECTED]:/junk/obj/junk/src/sys/DIABLO
Preloaded elf kernel /boot/kernel/kernel at 0xc076c000.
MPTable: OEM0 PROD
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Pentium III/Pentium III Xeon/Celeron (504.72-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x673  Stepping = 3
  
Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
CMOV,PAT,PSE36,PN,MMX,FXSR,SSE
real memory  = 536870912 (512 MB)
avail memory = 516034560 (492 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Assuming intbase of 0
ioapic0 Version 1.1 irqs 0-23 on motherboard
Pentium Pro MTRR support enabled
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 7 entries at 0xc00fdcf0
pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on
motherboard
pci0: PCI bus on pcib0
pci_cfgintr: 0:10 INTA BIOS irq 10
pci_cfgintr: 0:12 INTA BIOS irq 11
agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xd3ff
at device 0.0 on pci0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 UDMA33 controller port 0xf000-0xf00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f at
device 7.2 on pci0
pci_cfgintr: 0:7 INTD routed to irq 11
usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
piix0: PIIX Timecounter port 0x5000-0x500f at device 7.3 on pci0
Timecounter PIIX frequency 3579545 Hz quality 0
pci0: display, VGA at device 8.0 (no driver attached)
rl0: RealTek 8139 10/100BaseTX port 0xe400-0xe4ff mem
0xd700-0xd7ff irq 10 at device 10.0 on pci0
rl0: Ethernet address: 00:00:21:f2:a5:47
miibus0: MII bus on rl0
rlphy0: RealTek internal media interface on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl1: RealTek 8139 10/100BaseTX port 0xe800-0xe8ff mem
0xd7001000-0xd70010ff irq 11 at device 12.0 on pci0
rl1: Ethernet address: 00:40:f4:90:1c:4b
miibus1: MII bus on rl1
rlphy1: RealTek internal media interface on miibus1
rlphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
orm0: Option ROMs at iomem 0xc8000-0xcbfff,0xc-0xc7fff 

Re: ULE status

2005-02-10 Thread Simon Barner
Frode Nordahl wrote:
 I was surprised by the actual difference in system performance and 
 usability between 4BSD and ULE under such loads!
 
 If you haven't tried it on your heavy trafic server yet, go and do it 
 right now! :-)

Just a short me too. In my case it isn't a heavy traffic server but a
(slow) UP desktop system which feels substantially smoother with ULE.

Simon


pgpxff4gfPK9c.pgp
Description: PGP signature


Re: Save the Demon!

2005-02-10 Thread Godwin Stewart
On Wed, 9 Feb 2005 16:21:32 -0800, Freddie Cash [EMAIL PROTECTED] wrote:

 On February 9, 2005 04:13 pm, Ivan Roth wrote:
  sorry to ask that but which software could I use to produce vectorial
  graphics? Quite newbie to freebsd, don't know such free software.
 
 Inkscape is supposed to be a very nice vector drawing program.

There's also $PORTS/graphics/sodipodi

-- 
G. Stewart - [EMAIL PROTECTED]

drug, n:
A substance which, when injected into a rat, produces a
scientific paper.


pgpnPi4fcMDZn.pgp
Description: PGP signature


Re: Save the Demon!

2005-02-10 Thread Bob Bishop
At 06:32 10/02/2005, Peter Jeremy wrote:
On 2005-Feb-10 04:39:13 +0100, Bj?rn K?nig [EMAIL PROTECTED] wrote:
David Magda wrote:

It's daemon, not demon.
Or even dæmon
It's a question whether you are British or American or understand it as
a proper name. ;-)
My dictionary has both as headwords with a reference from demon to
daemon (but not vice versa) and lists a service program that is
called into action by the operating system under daemon.  The
etymology is from greek daimon via latin daemon.
FWIW, Concise Oxford has:
demon n.
...
5 (also daemon) a) an inner or attendant spirit; a genius (the demon of 
creativity). b) a divinity or supernatural being in ancient Greece.

--
Bob Bishop  +44 (0)118 940 1243
[EMAIL PROTECTED]   fax +44 (0)118 940 1295
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.3-Stable network issue

2005-02-10 Thread Emanuel Strobl
Am Donnerstag, 10. Februar 2005 11:00 schrieb Martin Minkus:
 I seem to have been having a rather strange networking issue in FreeBSD
 5.3-Stable (it started happening immediately after 5.2.1 and has persisted
 since.. I keep ³hoping² that next time I cvsup it will be fixed, but no).

 I downgraded back to 5.2.1-p13 and it is perfectly fine once again.


 *** Some background information:

 My FreeBSD box is my home NAT router, server, firewall, etc. It does DHCP,
 MX for some of my domains, secondary DNS (I got primary elsewhere), apache
 for some webhosting, blah blah blah. Nothing really special. It is a Dual
 PIII-500, 512mb ram, and a couple ATA hdd¹s. Had 3 realtek network
 interfaces, but down to 2 now.

 *** The problem:

 Networking simply stops or locks up. Why, I don't know. I believe
 initially it happened for all 3 network cards... I thought tcp/ip
 processing or something in the kernel got locked. It happens every 30
 minutes to an hour, and lasts about 60 seconds to 120 seconds.
 Unfortunately, 60 seconds to 120 seconds is long enough to kill messenger
 (my gf does not like), online gaming, etc etc.

Just a wils guess: Try setteing 'debug.mpsafet=0' in /boot/loader.conf
I had similar problems with pf and RELENG_5 

No soultion though :(

-Harry


 Lately, I had taken one of the realtek cards out (it was for a several km
 long wireless link) and moved the server to my gf's place (where I am now
 100% of the time). So now that I have the server locally and rely on it for
 my internet connection, this has become a real PAIN.

 I've noticed that I can remain ssh'd into diablo, do whatever I want while
 this lock issue occurs. So the lan interface rl0 is fine. The internet
 interface, rl1 (which goes to the cable modem) locks up. (btw, its not the
 cable modem as I am using my gf's now, and it did this at my place on my
 cable modem too, which is a different brand. Nortel at my place, motorola
 at my gfs).

 *** Attempts:

 I've attempted switching out network cards, and places 3 other realtek
 cards in. Different brands, all with different revisions (D instead of B,
 etc, etc).

 No matter what I try, nothing fixes it. The machine seems perfectly
 repsonsive, and I am still ssh'd in and can do whatever I want on it... But
 the network card going to the cable modem has stopped responding?!

 This never happened during 5.0-Current all throughout 5.2.1-STABLE, but
 anywhere beyond 5.2.1 it craps itself.


 *** Dmesg output:

 Copyright (c) 1992-2004 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.2.1-RELEASE-p13 #2: Thu Feb 10 18:39:33 CST 2005
 [EMAIL PROTECTED]:/junk/obj/junk/src/sys/DIABLO
 Preloaded elf kernel /boot/kernel/kernel at 0xc076c000.
 MPTable: OEM0 PROD
 Timecounter i8254 frequency 1193182 Hz quality 0
 CPU: Pentium III/Pentium III Xeon/Celeron (504.72-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x673  Stepping = 3

 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
, CMOV,PAT,PSE36,PN,MMX,FXSR,SSE
 real memory  = 536870912 (512 MB)
 avail memory = 516034560 (492 MB)
 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
 ioapic0: Assuming intbase of 0
 ioapic0 Version 1.1 irqs 0-23 on motherboard
 Pentium Pro MTRR support enabled
 npx0: [FAST]
 npx0: math processor on motherboard
 npx0: INT 16 interface
 pcibios: BIOS version 2.10
 Using $PIR table, 7 entries at 0xc00fdcf0
 pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on
 motherboard
 pci0: PCI bus on pcib0
 pci_cfgintr: 0:10 INTA BIOS irq 10
 pci_cfgintr: 0:12 INTA BIOS irq 11
 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xd3ff
 at device 0.0 on pci0
 pcib1: PCI-PCI bridge at device 1.0 on pci0
 pci1: PCI bus on pcib1
 isab0: PCI-ISA bridge at device 7.0 on pci0
 isa0: ISA bus on isab0
 atapci0: Intel PIIX4 UDMA33 controller port 0xf000-0xf00f at device 7.1
 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata0: [MPSAFE]
 ata1: at 0x170 irq 15 on atapci0
 ata1: [MPSAFE]
 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f at
 device 7.2 on pci0
 pci_cfgintr: 0:7 INTD routed to irq 11
 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
 usb0: USB revision 1.0
 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 piix0: PIIX Timecounter port 0x5000-0x500f at device 7.3 on pci0
 Timecounter PIIX frequency 3579545 Hz quality 0
 pci0: display, VGA at device 8.0 (no driver attached)
 rl0: RealTek 8139 10/100BaseTX port 0xe400-0xe4ff mem
 0xd700-0xd7ff irq 10 at device 10.0 on pci0
 rl0: Ethernet address: 00:00:21:f2:a5:47
 miibus0: MII bus on rl0
 rlphy0: RealTek internal media interface on miibus0
 rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 rl1: RealTek 8139 10/100BaseTX port 

login delay

2005-02-10 Thread Willem Jan Withagen
Hi,
Running 5.3-Stable from december, this server has a login delay which I 
can not really explain.
Both ssh and ftp react almost direct, only after entering the passwd the 
connections sits idle for  15 secs.

So something is is taking a while, and since it is both with ssh and 
ftp, I would assume it is the actual passwd verification itself.

Any suggestions as where to look?
Thanx,
--WjW
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: login delay

2005-02-10 Thread Andrey V. Elsukov
Hi, [EMAIL PROTECTED],

Thursday, February 10, 2005, 4:14:18 PM:
WJW Both ssh and ftp react almost direct, only after entering the passwd the
WJW connections sits idle for  15 secs.
WJW So something is is taking a while, and since it is both with ssh and
WJW ftp, I would assume it is the actual passwd verification itself.

Reverse DNS lookups. Check your /etc/resolv.conf, /etc/hosts

--
WBR, Andrey V. Elsukov


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.3-Stable network issue

2005-02-10 Thread Martin Minkus
On 10/2/2005 23:55, Freddie Cash [EMAIL PROTECTED] wrote:

 I seem to have been having a rather strange networking issue in
 FreeBSD 5.3-Stable (it started happening immediately after 5.2.1 and
 has persisted since.. I keep ³hoping² that next time I cvsup it will
 be fixed, but no).
 
 I downgraded back to 5.2.1-p13 and it is perfectly fine once again.
 
 *** Some background information:
 
 My FreeBSD box is my home NAT router, server, firewall, etc. It does
 DHCP, MX for some of my domains, secondary DNS (I got primary
 elsewhere), apache for some webhosting, blah blah blah. Nothing
 really special. It is a Dual PIII-500, 512mb ram, and a couple ATA
 hdd¹s. Had 3 realtek network interfaces, but down to 2 now.
 
 Any chance of using non-RealTek cards?  They are notorious for
 performing poorly at the best of times.
 
 My laptop has one of these internally, and every now and then it'll
 drop the connection.  Usually with an error about an oversize frame
 being discarded.  An ifconfig down ifconfig up will fix the issue.
 
 Enabling polling support (either via the kernel config option
 DEVICE_POLLING or the sysctl) helps some.
 
 The best solution, though, is to get better NICs.
 
 For run, read the man page for rl(4) and the comments in the rl
 source.  Quite enlightening about the issues the RealTek chipsets
 have.  :)

Yeah, I've thought about it. But I got no non realtek cards on me, so I'd
have to buy them. And there's always a chance this has nothing to do with
network cards or the driver (after all, it has worked flawlessly for me
since the FreeBSD 3.x days).

I am wondering if it is related to my motherboard, or something else? I have
a Epox dual cpu board... K something, I'd have to dig it up. Perhaps there
is some issue with that, causing the kernel to do funny things?

What will enabling polling support do?

Martin.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: UPDATE: ATA mkIII first official patches - please test!

2005-02-10 Thread Freddie Cash
 New version that fixes known problems so far etc now available:

Just curious if this includes support for new chipsets or not.  Not a
big deal if it doesn't, just curious.

I've got a Toshiba laptop that, unfortunately, uses the ATI IGP/IXP
chipset, which only gets detected as UDMA33 (which is fine for my
uses, so I'm not complaining).  If this is supported, I'd be more than
willing to lose ATAPICAM support to use it.  :)

-- 
Freddie Cash, CCNT CCLPHelpdesk / Network Support Tech.
School District 73 (250) 377-HELP [377-4357]
[EMAIL PROTECTED]   [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re[4]: interrupt routing

2005-02-10 Thread dima
 Ah, so they are all on the same bus.  Yuck, performance is going to be
 sucky. Bad Tyan, no cookie.  That'll also explain the limited number of
 interrupts available.  I don't think there's anything we can do to help
 the situation, sadly.
 I cannot affect the company equipment purchase policy either :/
 2 more servers on Tyan motherboards perform pretty bad also.
 Well this IS PC hardware we're talkinga bout here. :)
 
 If you can show that some other OS is able to confgiure an alternate
 interrupt then it might just be something up with ACPI.
I actually want the NICs and SCSI controllers run in different kernel threads.
I have found a year-old discussion on -current
http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019964.html
about assigning physical IRQ lines to PCI devices;
so I wanted to know if there is a way to force ACPI assign virtual interrupts a 
similar way.
I hope I would have some vacant time this weekend to dig in the ACPI code a 
bit; I think it is not natural to assign a virtual IRQ for 2 devices if there 
are a plenty of free lines left...

 Well, I dont experience any problems with the base system (the server
 has 4G of physical RAM btw). The ports collection isnt amd64-ready
 though. I compiled some ports patching their makefiles but some of them
 dont compile at all. Say, I failed to build vnc server from ports (I
 needed it to install Oracle) the only one I managed to build was an
 ancient realvnc (3.3.7), but I couldnt connect to it. I tried to compile
 realvnc 4.x from sources but ran into namespace issues (they were
 discussed on another thread here regarding some software package; seems
 to be a buggy gcc). So, Ive given up and happily installed an i386
 version.
 Well, thats not a failing of the ports system itself :-)  Did you report
 your problems to the port maintainers?
Some of them before I have given up...

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.x concerns

2005-02-10 Thread Chris
If this helps, I noticed this recently on the machine that has had tcp lockups.

rl0: discard oversize frame (ether type c49b flags 3 len 47956  max 1514)
rl0: discard oversize frame (ether type 98b4 flags 3 len 17725  max 1514)
rl0: discard oversize frame (ether type 8be6 flags 3 len 38514  max 1514)
rl0: discard oversize frame (ether type 5c60 flags 3 len 2270  max 1514)
rl0: discard oversize frame (ether type a338 flags 3 len 58392  max 1514)
rl0: discard oversize frame (ether type 8680 flags 3 len 22762  max 1514)
rl0: discard oversize frame (ether type 2ffa flags 3 len 61086  max 1514)
rl0: discard oversize frame (ether type fc52 flags 3 len 55028  max 1514)

It is still online tho.

Chris


On Mon, 7 Feb 2005 16:29:23 -0800, Kris Kennaway [EMAIL PROTECTED] wrote:
 On Mon, Feb 07, 2005 at 09:40:48PM -0200, T?rgan Flores de Siqueira wrote:
  On Sun, Feb 06, 2005 at 03:01:49PM +, Chris wrote:
  
  4 - compatiblity, I remember using 5.2.1 and pretty much all software
  worked well in that and then they did the bind defaulting to base and
  libs version jump, why wasnt this done in 5.0 so 3rd party apps could
  adjust, now we have a situation where most stuff that worked in 4.x
  worked well in 5.1 and 5.2.1 but then broke in 5.3 so effectively 5.3
  was liek a new major version over 5.2.1.
  
  5.2.1 was clearly marked as a developer preview release and you were
  warned not to rely on it for production use.  As a snapshot of
  FreeBSD-CURRENT, binary compatibility is not guaranteed and often
  needs to be broken in the course of development.
  
  Kris
 
  Just adding a note: I regularly use FreeBSD on a Toshiba notebook, and
  switched from 4.x to 5.x to benefit from cardbus support.
  Well, I started with 5.2.1 and all things did well. Since then, I'm
  trying to track 5-STABLE with no success. Starting with 5.3-RELEASE,
  the ACPI stopped to work, as well as did the rl driver.
  So, I switched back to 5.2.1.
 
 Sorry to hear that - I hope you submitted bug reports so that someone
 can try to fix this, otherwise you might be stuck with 5.2.1 forever.
 
 Kris
 
 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re[5]: interrupt routing -- moving to acpi@

2005-02-10 Thread dima
Thanks to all who tried to help. I decided to move the discussion to acpi@

  Ah, so they are all on the same bus.  Yuck, performance is going to be
  sucky. Bad Tyan, no cookie.  That'll also explain the limited number of
  interrupts available.  I don't think there's anything we can do to help
  the situation, sadly.
  I cannot affect the company equipment purchase policy either :/
  2 more servers on Tyan motherboards perform pretty bad also.
  Well this IS PC hardware we're talkinga bout here. :)
  
  If you can show that some other OS is able to confgiure an alternate
  interrupt then it might just be something up with ACPI.
 I actually want the NICs and SCSI controllers run in different kernel threads.
 I have found a year-old discussion on -current
 http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019964.html
 about assigning physical IRQ lines to PCI devices;
 so I wanted to know if there is a way to force ACPI assign virtual interrupts 
 a similar way.
 I hope I would have some vacant time this weekend to dig in the ACPI code a 
 bit; I think it is not natural to assign a virtual IRQ for 2 devices if there 
 are a plenty of free lines left...
 
  Well, I dont experience any problems with the base system (the server
  has 4G of physical RAM btw). The ports collection isnt amd64-ready
  though. I compiled some ports patching their makefiles but some of them
  dont compile at all. Say, I failed to build vnc server from ports (I
  needed it to install Oracle) the only one I managed to build was an
  ancient realvnc (3.3.7), but I couldnt connect to it. I tried to compile
  realvnc 4.x from sources but ran into namespace issues (they were
  discussed on another thread here regarding some software package; seems
  to be a buggy gcc). So, Ive given up and happily installed an i386
  version.
  Well, thats not a failing of the ports system itself :-)  Did you report
  your problems to the port maintainers?
 Some of them before I have given up...
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE status

2005-02-10 Thread Frode Nordahl
On Feb 10, 2005, at 16:30, Randy Bush wrote:
how about stability?  last time i tried ule, the system died in
a few days.
Don't know yet.
I will keep trashing the server and post here if it crashes.
Regards,
Frode Nordahl
randy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


[5-STABLE] : CDRW burning problem - acd0: FAILURE - READ_BIG ILLEGAL REQUEST

2005-02-10 Thread Marwan Burelle
Hi,

I have a CDRW burner that use to work (with 5.2.1 the last time.)

But since one of my last RELENG_5_2 update I encounter errors when
burning CDRW (I don't have CDR to test, but I rember having strange
behaviour with CDR also.) Switching to RELENG-5 (re-install 5.3 and
cvsup after) a week ago doesn't change anything.

burncd dies with message :

[EMAIL PROTECTED] 17:05 FreeBSD-5.3]# burncd -e -v -f /dev/acd0 data 
5.3-RELEASE-i386-disc1.iso fixate
adding type 0x08 file 5.3-RELEASE-i386-disc1.iso size 660384 KB 330192 blocks
burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Input/output error

($status : 74)

And I have those messages in my log :

kernel: acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 
error=4ABORTED
kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 
error=4ABORTED
last message repeated 3 times

I have tried with cdrecord and atapicam, but again it fails with
message :

cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent 
defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01 (i386-unknown-freebsd5.3) Copyright (C) 1995-2004 Jörg 
Schilling
scsidev: '1,0,0'
scsibus: 1 target: 0 lun: 0
Using libscg version 'schily-0.8'.
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities   : 
Vendor_info: 'HL-DT-ST'
Identifikation : 'RW/DVD GCC-4481B'
Revision   : 'C103'
Device seems to be: Generic mmc2 DVD-ROM.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-2 SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
cdrecord: Drive needs to reload the media to return to proper status.
cdrecord: Cannot get next writable address for 'invisible' track.
cdrecord: This means that we are checking recorded media.
cdrecord: This media cannot be written in streaming mode anymore.
cdrecord: If you like to write to 'preformatted' RW media, try to blank the 
media first.
Starting to write CD/DVD at speed 10 in real TAO mode for single session.
Last chance to quit, starting real write0 seconds. Operation starts.
Turning BURN-Free off
cdrecord: Input/output error. read track info: scsi sendcmd: retryable error
CDB:  52 01 00 00 00 FF 00 00 1C 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.003s timeout 240s
cdrecord: Cannot get next writable address for 'invisible' track.
cdrecord: This means that we are checking recorded media.
cdrecord: This media cannot be written in streaming mode anymore.
cdrecord: If you like to write to 'preformatted' RW media, try to blank the 
media first.
cdrecord: Cannot get next writable address.

Of course, I have erased and blanked the CDRW before (with burncd and
without any error ... )

I have no READ_BIG error in my log with cdrecord.

I tried to switch drive in PIO4 or UDMA33, the result is the same ...

I saw PR 75875, but it is still open and I have no mounting/reading problem.

My kernel is a Generic without some adaptors, with atapicam and some
color for the console, but I've got the same problem with a generic
kernel.

Here my dmesg :

Copyright (c) 1992-2005 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.3-STABLE #0: Fri Feb  4 18:45:33 CET 2005
root@:/usr/home/obj/usr/src/sys/KER_pc5-179
MPTable: DELL WS 360  
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3192.02-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf29  Stepping = 9
  
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
real memory  = 1073168384 (1023 MB)
avail memory = 1036431360 (988 MB)
ioapic0: Changing APIC ID to 1
ioapic0: Assuming intbase of 0
ioapic0 Version 2.0 irqs 0-23 on motherboard
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard
pci0: PCI bus on pcib0
agp0: Intel 82875P host to AGP bridge mem 0xe800-0xefff at device 0.0 
on pci0
pcib1: MPTable PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
nvidia0: Quadro FX 500/600 PCI mem 
0xf000-0xf7ff,0xfd00-0xfdff irq 16 at device 0.0 on pci1
nvidia0: [GIANT-LOCKED]
uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xff80-0xff9f irq 16 at 
device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801EB (ICH5) USB 

Re: [5-STABLE] : CDRW burning problem - acd0: FAILURE - READ_BIG ILLEGAL REQUEST

2005-02-10 Thread Scott Robbins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Feb 10, 2005 at 05:23:46PM +0100, Marwan Burelle wrote:
 Hi,
 
 I have a CDRW burner that use to work (with 5.2.1 the last time.)
 
 But since one of my last RELENG_5_2 update I encounter errors when
 burning CDRW (I don't have CDR to test, but I rember having strange
 behaviour with CDR also.) Switching to RELENG-5 (re-install 5.3 and
 cvsup after) a week ago doesn't change anything.
 
 burncd dies with message :
 
 [EMAIL PROTECTED] 17:05 FreeBSD-5.3]# burncd -e -v -f /dev/acd0 data 
 5.3-RELEASE-i386-disc1.iso fixate
 adding type 0x08 file 5.3-RELEASE-i386-disc1.iso size 660384 KB 330192 blocks
 burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Input/output error

I get the same error on two machines, did some googling and found no
answers that helped.  (I fear I don't remember the details now.)  As I
don't have the error on another machine (all running 5.3 STABLE) I
figured it was something to do with the CD drive, a Plexor.


However, in my case at least, the burn is successful.  It does it's
thing, gives me that error message, I wait a few moments, eject the CD
and it is a good one.




- -- 

Scott

GPG KeyID EB3467D6
( 1B848 077D 66F6 9DB0 FDC2  A409 FA54 D575 EB34 67D6)
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Xander: I can not stress enough how much I don't have plans. 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCC4wD+lTVdes0Z9YRAgaTAJ9/QU1OXOZo3JcZ5q507fFdLRIRfwCfdNv0
nDfbCDo5226vzqy5T/aynW0=
=Ci8W
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE status

2005-02-10 Thread Julio Capote
I upgraded to 5-STABLE + ULE + PREEMPT last night, been using my desktop
system heavily for about 6 hours, and no crashing, AWESOME performance
under heavy load. Im curious to see some 1(O) vs ULE benches..



On Thu, 2005-02-10 at 17:00 +0100, Frode Nordahl wrote:
 On Feb 10, 2005, at 16:30, Randy Bush wrote:
  how about stability?  last time i tried ule, the system died in
  a few days.
 
 Don't know yet.
 
 I will keep trashing the server and post here if it crashes.
 
 
 Regards,
 Frode Nordahl
 
  randy
 
 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [5-STABLE] : CDRW burning problem - acd0: FAILURE - READ_BIG ILLEGAL REQUEST

2005-02-10 Thread Marwan Burelle
On Thu, Feb 10, 2005 at 11:29:55AM -0500, Scott Robbins wrote:
 I get the same error on two machines, did some googling and found no
 answers that helped.  (I fear I don't remember the details now.)  As I
 don't have the error on another machine (all running 5.3 STABLE) I
 figured it was something to do with the CD drive, a Plexor.
 
 
 However, in my case at least, the burn is successful.  It does it's
 thing, gives me that error message, I wait a few moments, eject the CD
 and it is a good one.

Chance you have. The burn failed a few seconds after I hit the return
key ...

What is strange is that I have the same behaviour with the same drive,
but a different CDRW (a 1x-4x) but at that time with a 8x-12x it was
working. I lead to thing to some strange behaviour of CDRW, but ...

I have think also of mechanical problem, but I have the same error on
another machine (with 5.2.1, but I've just done one try ... )

-- 
Burelle Marwan,
Equipe Bases de Donnees - LRI
http://www.cduce.org
([EMAIL PROTECTED] | [EMAIL PROTECTED])

pgpZj3BDnsxQS.pgp
Description: PGP signature


Server reboots when silo overflows - FreeBSD 4.11

2005-02-10 Thread Lefteris Tsintjelis
Hi,

There seems to be a serious problem with the puc device driver. When the driver
expiriences overflows the server simply reboots!

device  puc
options PUC_FASTINTR

I have tried to rebuild a new kernel without the PUC_FASTINTR option but without
much luck. It still keeps on rebooting right after a few silo overflow errors.

PS: Please CC

Thanks,
Lefteris

# dmesg
sio5: 1 more silo overflow (total 1)
sio5: 1 more silo overflow (total 2)
sio5: 1 more silo overflow (total 3)
sio5: 1 more silo overflow (total 4)
sio5: 1 more silo overflow (total 5)
sio5: 1 more silo overflow (total 6)
sio5: 1 more silo overflow (total 7)
Copyright (c) 1992-2005 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.11-STABLE #0: Sat Jan 29 01:56:42 EET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM
Timecounter i8254  frequency 1193182 Hz
CPU: Intel(R) Pentium(R) 4 CPU 3.06GHz (3073.65-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf27  Stepping = 7
  
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Hyperthreading: 2 logical CPUs
real memory  = 536788992 (524208K bytes)
avail memory = 517283840 (505160K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs
 cpu0 (BSP): apic id:  0, version: 0x00050014, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00050014, at 0xfee0
 io0 (APIC): apic id:  4, version: 0x00178020, at 0xfec0
Preloaded elf kernel kernel at 0xc04cc000.
Preloaded elf module agp.ko at 0xc04cc09c.
Warning: Pentium 4 CPU: PSE disabled
VESA: v3.0, 131072k memory, flags:0x1, mode table:0xc04251a2 (122)
VESA: NVidia
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 9 entries at 0xc00f1be0
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge on motherboard
IOAPIC #0 intpin 19 - irq 2
IOAPIC #0 intpin 23 - irq 5
pci0: PCI bus on pcib0
agp0: Intel 82850 host to AGP bridge mem 0xf800-0xfbff at device 0.0 
on pci0
pcib1: PCI to PCI bridge (vendor=8086 device=2532) at device 1.0 on pci0
IOAPIC #0 intpin 16 - irq 9
pci1: PCI bus on pcib1
pci1: NVidia model 0171 graphics accelerator at 0.0 irq 9
pcib2: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0
IOAPIC #0 intpin 21 - irq 10
IOAPIC #0 intpin 22 - irq 11
IOAPIC #0 intpin 20 - irq 14
pci2: PCI bus on pcib2
ohci0: NEC uPD 9210 USB controller mem 0xed80-0xed800fff irq 10 at device 
4.0 on pci2
usb0: OHCI version 1.0
usb0: NEC uPD 9210 USB controller on ohci0
usb0: USB revision 1.0
uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1: NEC uPD 9210 USB controller mem 0xed00-0xed000fff irq 11 at device 
4.1 on pci2
usb1: OHCI version 1.0
usb1: NEC uPD 9210 USB controller on ohci1
usb1: USB revision 1.0
uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
pci2: USB controller at 4.2 irq 5
ahc0: Adaptec 29160 Ultra160 SCSI adapter port 0xd800-0xd8ff mem 
0xec00-0xec000fff irq 11 at device 10.0 on pci2
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
fxp0: Intel 82559 Pro/100 Ethernet port 0xd400-0xd43f mem 
0xeb00-0xeb0f,0xeb80-0xeb800fff irq 5 at device 11.0 on pci2
fxp0: Ethernet address 00:d0:b7:23:19:8c
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
puc0: VScom PCI-200L port 
0xb000-0xb007,0xb400-0xb407,0xb800-0xb807,0xd000-0xd007 mem 
0xea80-0xea80003f irq 14 at device 12.0 on pci2
sio4: configured irq 14 not in bitmap of probed irqs 0x8000
sio4: type 16550A
sio5: configured irq 14 not in bitmap of probed irqs 0x8000
sio5: type 16550A
isab0: Intel 82801BA/BAM (ICH2) PCI to LPC bridge at device 31.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel ICH2 ATA100 controller at device 31.1 on pci0
atapci0: ATA channel disabled by BIOS
uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xa400-0xa41f irq 2 
at device 31.2 on pci0
usb2: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xa000-0xa01f irq 5 
at device 31.4 on pci0
usb3: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
pmtimer0 on isa0
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
ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata1 at port 0x170-0x177,0x376 irq 15 on isa0
atkbdc0: Keyboard 

Does this mean trouble?

2005-02-10 Thread Mipam
Hi,

I am noticing many warnings:

calcru: negative runtime of -891485461 usec for pid 45 (swi5: clock sio)

in ps waux:
root45  0.0  0.0 08  ??  WL   Tue03PM -2341058:-22.07 
[swi5: clock sio]

I am seeing lots more of these messages.
Also from other processes i see the same message.
Does this mean trouble or not?
I am running an smp kernel with options PREEMPTION and the 4bsd scheduler.
Version is RELENG_5, feb 8 i fetch the latest source and compiled it so 
the system is running from that source.
Here is dmesg output of the system:

Copyright (c) 1992-2005 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.3-STABLE #4: Tue Feb  8 14:41:10 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/Mipam
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) III CPU family  1133MHz (1125.78-MHz 
686-class CPU)
  Origin = GenuineIntel  Id = 0x6b1  Stepping = 1
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM
OV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 2147467264 (2047 MB)
avail memory = 2095861760 (1998 MB)
ACPI APIC Table: COMPAQ 0083
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  3
 cpu1 (AP): APIC ID:  0
MADT: Forcing active-low polarity and level trigger for SCI
ioapic1 Version 1.1 irqs 16-31 on motherboard
ioapic0 Version 1.1 irqs 0-15 on motherboard
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: COMPAQ P24 on motherboard
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x240-0x243 on acpi0
cpu0: ACPI CPU on acpi0
cpu1: ACPI CPU on acpi0
pcib0: ACPI Host-PCI bridge on acpi0
pci0: ACPI PCI bus on pcib0
ciss0: Compaq Smart Array 5i port 0x2000-0x20ff mem 
0xf5ef-0xf5ef3fff,0xf7
dc-0xf7df irq 16 at device 1.0 on pci0
fxp0: Intel 82559 Pro/100 Ethernet port 0x2400-0x243f mem 
0xf7c0-0xf7c
f,0xf7db-0xf7db0fff irq 18 at device 2.0 on pci0
miibus0: MII bus on fxp0
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:02:a5:da:70:0d
fxp1: Intel 82559 Pro/100 Ethernet port 0x2440-0x247f mem 
0xf7a0-0xf7a
f,0xf7bf-0xf7bf0fff irq 20 at device 4.0 on pci0
miibus1: MII bus on fxp1
inphy1: i82555 10/100 media interface on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:02:a5:da:70:0c
pci0: display, VGA at device 5.0 (no driver attached)
pci0: base peripheral at device 6.0 (no driver attached)
isab0: PCI-ISA bridge at device 15.0 on pci0
atapci0: ServerWorks ROSB4 UDMA33 controller port 
0x2c00-0x2c0f,0x376,0x170-0x
177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ohci0: OHCI (generic) USB controller mem 0xf5fd-0xf5fd0fff irq 22 at 
devic
e 15.2 on pci0
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: OHCI (generic) USB controller on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
pcib1: ACPI Host-PCI bridge on acpi0
pci1: ACPI PCI bus on pcib1
pcib2: ACPI Host-PCI bridge on acpi0
pci7: ACPI PCI bus on pcib2
em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 
0x3000-0x303f
 mem 0xf7f8-0xf7fb,0xf7fe-0xf7ff irq 28 at device 3.0 on 
pci7
em0: Ethernet address: 00:04:23:ab:a1:3c
em0:  Speed:N/A  Duplex:N/A
em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 
0x3040-0x307f
 mem 0xf7f0-0xf7f3,0xf7f6-0xf7f7 irq 28 at device 3.1 on 
pci7
em1: Ethernet address: 00:04:23:ab:a1:3d
em1:  Speed:N/A  Duplex:N/A
pci7: base peripheral at device 7.0 (no driver attached)
acpi_tz0: Thermal Zone on acpi0
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
fdc0: floppy drive controller port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
fd0: 1440-KB 3.5 drive on fdc0 drive 0
orm0: ISA Option ROMs at iomem 
0xee000-0xe,0xcc000-0xcd7ff,0xc8000-0xcbfff
,0xc-0xc7fff on isa0
pmtimer0 on isa0
ppc0: parallel port not found.
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
acd0: CDROM Compaq CRN-8241B/2.23 at ata0-master PIO4
SMP: AP CPU #1 Launched!
da0 at ciss0 bus 0 target 0 lun 0
da0: COMPAQ RAID 5  VOLUME OK Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 104183MB (213367680 512 byte sectors: 255H 32S/T 26148C)
Mounting root from 

Re: [5-STABLE] : CDRW burning problem - acd0: FAILURE - READ_BIG ILLEGAL REQUEST

2005-02-10 Thread Kevin Oberman
 Date: Thu, 10 Feb 2005 17:41:21 +0100
 From: Marwan Burelle [EMAIL PROTECTED]
 Sender: [EMAIL PROTECTED]
 
 
 --neYutvxvOLaeuPCA
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Thu, Feb 10, 2005 at 11:29:55AM -0500, Scott Robbins wrote:
  I get the same error on two machines, did some googling and found no
  answers that helped.  (I fear I don't remember the details now.)  As I
  don't have the error on another machine (all running 5.3 STABLE) I
  figured it was something to do with the CD drive, a Plexor.
 =20
 =20
  However, in my case at least, the burn is successful.  It does it's
  thing, gives me that error message, I wait a few moments, eject the CD
  and it is a good one.
 
 Chance you have. The burn failed a few seconds after I hit the return
 key ...
 
 What is strange is that I have the same behaviour with the same drive,
 but a different CDRW (a 1x-4x) but at that time with a 8x-12x it was
 working. I lead to thing to some strange behaviour of CDRW, but ...
 
 I have think also of mechanical problem, but I have the same error on
 another machine (with 5.2.1, but I've just done one try ... )

Is the firmware on the drive current? Many drives, some only a year old,
have problems working with newer media.

I have a DVD burner that suddenly would not burn a disk. The only change
was a new spindle of disks. It would only burn them at 1x and the
resulting disk was mountable and I could list files, but I could not
read the files.

A problem I had was that the firmware updater is Windows-only, so I had
to remove the drive and take it to a Windows system to do the update.
After the update, I re-installed it and it ran perfectly again.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: UPDATE: ATA mkIII first official patches - please test!

2005-02-10 Thread Nick Gustas
Dag-Erling Smørgrav wrote:
Søren Schmidt [EMAIL PROTECTED] writes:
 

New version that fixes known problems so far etc now available:
   

ah, just commit it already.  it works for me, so it must be good enough ;)
DES
 

heh :)
Works for me, but one problem, slaves attached to a Seagate master, 
don't show up :/ Tried a verbose boot, but it hung. Controller is a 4 
port highpoint rocketraid in jbod mode.

Drives are cabled and jumpered correctly, also tried CS mode, no difference.
This was on 5.3 stable, may try MK3 on 6.0 tonight, vanilla 6.0 is fine.
MK3 patched 5.3 dmesg from yesterday
FreeBSD 5.3-STABLE #20: Wed Feb  9 17:51:03 EST 2005 
root@:/usr/src/sys/i386/compile/OPPRESSION
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) Processor (1200.05-MHz 686-class CPU)
Origin = AuthenticAMD  Id = 0x662  Stepping = 2
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
AMD Features=0xc048MP,AMIE,DSP,3DNow!
real memory  = 1073217536 (1023 MB)
avail memory = 1044873216 (996 MB)
MPTable: TYAN PAULANER
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID:  1
cpu1 (AP): APIC ID:  0
ioapic0: Assuming intbase of 0
ioapic0 Version 1.1 irqs 0-23 on motherboard
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard
pci0: PCI bus on pcib0
agp0: AMD 762 host to AGP bridge port 0x1050-0x1053 mem 
0xea10-0xea100fff,0xec00-0xefff at device 0.0 on pci0
pcib1: MPTable PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: display, VGA at device 5.0 (no driver attached)
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: AMD 768 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0
x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0: ATA channel 0 on atapci0
ata1: ATA channel 1 on atapci0
pci0: bridge, PCI-unknown at device 7.3 (no driver attached)
em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 
0x1000-0x103f mem 0xe800-0xe801,0xe802-0xe803 irq 16 at 
device 8.0 on pci0
em0: Ethernet address: 00:07:e9:00:ae:36
em0:  Speed:N/A  Duplex:N/A
pcib2: MPTable PCI-PCI bridge at device 16.0 on pci0
pci2: PCI bus on pcib2
atapci1: HighPoint HPT374 (channel 0+1) UDMA133 controller port 
0x2000-0x20ff,0x2880-0x2883,0x2888-0x288f,0x2884-0x2887,0x2890-0x2897 
irq 17 at device 5.0 on pci2
ata2: ATA channel 0 on atapci1
ata3: ATA channel 1 on atapci1
atapci2: HighPoint HPT374 (channel 2+3) UDMA133 controller port 
0x2400-0x24ff,0x2898-0x289b,0x28a0-0x28a7,0x289c-0x289f,0x28a8-0x28af 
irq 17 at device 5.1 on pci2
ata4: ATA channel 0 on atapci2
ata5: ATA channel 1 on atapci2
pci2: network, ethernet at device 8.0 (no driver attached)
cpu0 on motherboard
cpu1 on motherboard
pmtimer0 on isa0
orm0: ISA Option ROMs at iomem 
0xe-0xe3fff,0xcc000-0xc,0xcb000-0xcbfff,0xca800-0xcafff,0xc-0xca7ff 
on isa0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
ppc0: parallel port not found.
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0303 can't assign resources (port)
unknown: PNP0c02 can't assign resources (memory)
fdc1: cannot allocate I/O port (6 ports)
Timecounters tick every 10.000 msec
ad0: 76319MB WDC WD800BB-00DKA0 77.07W77 at ata0-master UDMA100
ad4: 381554MB Seagate ST3400832A 3.01 at ata2-master UDMA100
ad6: 190782MB Seagate ST3200822A 3.01 at ata3-master UDMA100
ad8: 176700MB IC35L180AVV207 1 V26OA63A at ata4-master UDMA100
ad9: 95396MB WDC WD1000BB-32CCB0 22.04A22 at ata4-slave UDMA100
ad10: 156334MB Maxtor 6Y160P0 YAR41BW0 at ata5-master UDMA133
ad11: 381554MB Seagate ST3400832A 3.01 at ata5-slave UDMA100
SMP: AP CPU #1 Launched!
Mounting root from ufs:/dev/ad0s1a

As you can see the hitachi and maxtor mastered slaves showed up
I don't have a recent non mk3 5.3 dmesg handy, but here is a working 
plain 6.0 dmesg from the same machine

FreeBSD 6.0-CURRENT #1: Thu Feb 10 10:37:33 EST 2005
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/OP6
MPTable: TYAN PAULANER
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) Processor (1200.05-MHz 686-class CPU)
 Origin = AuthenticAMD  Id = 0x662  Stepping = 2
 
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
 AMD Features=0xc048MP,AMIE,DSP,3DNow!
real memory  = 1073217536 (1023 MB)
avail memory = 1041399808 (993 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID:  1
cpu1 (AP): APIC ID:  0
ioapic0: Assuming intbase of 0

Re: Server reboots when silo overflows - FreeBSD 4.11

2005-02-10 Thread Mike Tancsa
At 11:42 AM 10/02/2005, Lefteris Tsintjelis wrote:
Hi,
There seems to be a serious problem with the puc device driver. When the 
driver
expiriences overflows the server simply reboots!

device  puc
options PUC_FASTINTR
I have tried to rebuild a new kernel without the PUC_FASTINTR option but 
without
much luck. It still keeps on rebooting right after a few silo overflow errors.
puc0: VScom PCI-200L port 
0xb000-0xb007,0xb400-0xb407,0xb800-0xb807,0xd000-0xd007 mem 
0xea80-0xea80003f irq 14 at device 12.0 on pci2
sio4: configured irq 14 not in bitmap of probed irqs 0x8000
sio4: type 16550A
sio5: configured irq 14 not in bitmap of probed irqs 0x8000
sio5: type 16550A

How do you have device sio configured in your kernel ?  Are you trying to 
specify the ports for the puc attached serial ports ?  All you need is

device  sio
device  puc
Also, enable crash dumps and build a debug kernel.  Add
makeoptionsDEBUG=-g
to your kernel config
and at bootup time add
dumpdev=/dev/da0s1b   # Device name to crashdump to (or NO).
dumpdir=/var/crash# Directory where crash dumps are to be stored
Assuming your swap is on da0s1b
---Mike 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE status

2005-02-10 Thread Doug Poland
On Thu, February 10, 2005 10:39 am, Julio Capote said:
 I upgraded to 5-STABLE + ULE + PREEMPT last night, been using my
 desktop system heavily for about 6 hours, and no crashing, AWESOME
 performance under heavy load. Im curious to see some 1(O) vs ULE
 benches..

Precisely how does one upgrade 5-STABLE to include ULE + PREMPT? 
Obviously I'll cvsup RELENG_5, but don't know how to set ULE + PREMPT.

Many thanks.

-- 
Regards,
Doug

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE status

2005-02-10 Thread Julio Capote
Cvsup to RELENG_5, and change your kernel config ot include ULE and
PREMPTION support; I suggest reading the keeping up to date and
kernel compiling chapters on the handbook, if you haven't done so
already.

-Julio



On Thu, 2005-02-10 at 11:32 -0600, Doug Poland wrote:
 On Thu, February 10, 2005 10:39 am, Julio Capote said:
  I upgraded to 5-STABLE + ULE + PREEMPT last night, been using my
  desktop system heavily for about 6 hours, and no crashing, AWESOME
  performance under heavy load. Im curious to see some 1(O) vs ULE
  benches..
 
 Precisely how does one upgrade 5-STABLE to include ULE + PREMPT? 
 Obviously I'll cvsup RELENG_5, but don't know how to set ULE + PREMPT.
 
 Many thanks.
 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE status

2005-02-10 Thread Doug Poland
On Thu, February 10, 2005 11:43 am, Kevin Oberman said:
 Date: Thu, 10 Feb 2005 11:32:34 -0600 (CST) From: Doug Poland
 Precisely how does one upgrade 5-STABLE to include ULE + PREMPT?
 Obviously I'll cvsup RELENG_5, but don't know how to set ULE +
 PREMPT.

 Put them in your configuration. Rebuild kernel. See /sys/cong/NOTES
 and /sys/i386/conf/NOTES. (I you are not running on an i386, look for
 the MD arch file in the obvious places.)

Thanks, I didn't know about /sys/conf/NOTES.  I grep'd for ULE in
/sys/conf/i386/* but no hits.

-- 
Regards,
Doug

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Server reboots when silo overflows - FreeBSD 4.11

2005-02-10 Thread Dmitry Liakh
On Thu, Feb 10, 2005 at 06:42:01PM +0200, Lefteris Tsintjelis wrote:
 Hi,
 
 There seems to be a serious problem with the puc device driver. When the 
 driver
 expiriences overflows the server simply reboots!
 
 device  puc
 options PUC_FASTINTR
 
 I have tried to rebuild a new kernel without the PUC_FASTINTR option but 
 without
 much luck. It still keeps on rebooting right after a few silo overflow errors.
 
 PS: Please CC
 
 Thanks,
 Lefteris
 
 # dmesg
 sio5: 1 more silo overflow (total 1)
 sio5: 1 more silo overflow (total 2)
 sio5: 1 more silo overflow (total 3)
 sio5: 1 more silo overflow (total 4)
 sio5: 1 more silo overflow (total 5)
 sio5: 1 more silo overflow (total 6)
 sio5: 1 more silo overflow (total 7)
 Copyright (c) 1992-2005 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.11-STABLE #0: Sat Jan 29 01:56:42 EET 2005
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM
 Timecounter i8254  frequency 1193182 Hz
 CPU: Intel(R) Pentium(R) 4 CPU 3.06GHz (3073.65-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0xf27  Stepping = 7
   
 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
   Hyperthreading: 2 logical CPUs
^^
Try non-SMP kernel or disable HTT.

-- 
WBR
Dmitry

xmpp:[EMAIL PROTECTED] tel. +380 44 463-7134
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE status

2005-02-10 Thread Frode Nordahl
On Feb 10, 2005, at 18:22, Mipam wrote:
I noticed this:
You're running RELENG_5 on a dual Xeon 3.06GHz box
You enabled DEVICE_POLLING and ULE as well.
But normally compiling the kernel with SMP and polling won't work.
Don't you use a SMP kernel or?
I saw several pages stating that DEVICE_POLLING actually works with 
SMP, so I just commented out the #error in 
/usr/src/sys/kern/kern_poll.c. Seems to work like a charm!

For example:
http://www.mail-archive.com/freebsd-questions@freebsd.org/msg89703.html
http://silverwraith.com/papers/freebsd-tuning.php
Regards,
Frode Nordahl
Bye,
Mipam.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE status

2005-02-10 Thread Frode Nordahl
On Feb 10, 2005, at 18:32, Doug Poland wrote:
On Thu, February 10, 2005 10:39 am, Julio Capote said:
I upgraded to 5-STABLE + ULE + PREEMPT last night, been using my
desktop system heavily for about 6 hours, and no crashing, AWESOME
performance under heavy load. Im curious to see some 1(O) vs ULE
benches..
Precisely how does one upgrade 5-STABLE to include ULE + PREMPT?
Obviously I'll cvsup RELENG_5, but don't know how to set ULE + PREMPT.
Comment out this line:
options SCHED_4BSD  # 4BSD scheduler
And add this:
options SCHED_ULE
For other options, have a look at /sys/conf/NOTES and 
/sys/i386/conf/NOTES.

(Replace i386 with your arch if different)
Regards,
Frode Nordahl
Many thanks.
--
Regards,
Doug
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Adding an usb harddisk

2005-02-10 Thread Jack Raats
I want to add an usb harddisk.
Acoording to fdisk it's formatted as a NTFS/HPFS/QNX disk
Can I add this disk and still using this file system?
What kind of dev/fstab do I need to add?
Do I need an extra swap slice?  How to make one?
I'm using FreeBSD 4.11.

Thank you

Jack Raats
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Adding an usb harddisk

2005-02-10 Thread Doug White
On Thu, 10 Feb 2005, Jack Raats wrote:

 I want to add an usb harddisk.
 Acoording to fdisk it's formatted as a NTFS/HPFS/QNX disk
 Can I add this disk and still using this file system?

NTFS is a Windows filesystem. You can't install FreeBSD to it but you can
mount and use the volume.  See the mount_ntfs manpage for restrictions on
our NTFS support.

You can mount it using 'mount -t ntfs /dev/da /' if you don't want
to make a UFS filesystem. (replace  with device name and  with
desired mountpoint.)

If you do want to reformat it for UFS, see the article on formatting media
at www.freebsd.org for instructions.

 What kind of dev/fstab do I need to add?

Its like an existing one, just change the filesystem type from 'ufs' to
'ntfs'.

 Do I need an extra swap slice?  How to make one?

Not unless you want one, but if you do you probably need to destroy the
NTFS filesystem to make space.

 I'm using FreeBSD 4.11.

NTFS support there may not be as mature as the one in 5.x.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Adding an usb harddisk

2005-02-10 Thread Ivan Roth
Doug White a écrit :
On Thu, 10 Feb 2005, Jack Raats wrote:
 

I want to add an usb harddisk.
Acoording to fdisk it's formatted as a NTFS/HPFS/QNX disk
Can I add this disk and still using this file system?
   

NTFS is a Windows filesystem. You can't install FreeBSD to it but you can
mount and use the volume.  See the mount_ntfs manpage for restrictions on
our NTFS support.
You can mount it using 'mount -t ntfs /dev/da /' if you don't want
to make a UFS filesystem. (replace  with device name and  with
desired mountpoint.)
If you do want to reformat it for UFS, see the article on formatting media
at www.freebsd.org for instructions.
 

What kind of dev/fstab do I need to add?
   

Its like an existing one, just change the filesystem type from 'ufs' to
'ntfs'.
 

Do I need an extra swap slice?  How to make one?
   

Not unless you want one, but if you do you probably need to destroy the
NTFS filesystem to make space.
 

I'm using FreeBSD 4.11.
   

NTFS support there may not be as mature as the one in 5.x.
 

just note that it could not be /dev/da but /dev/ad, e.g, da is 
only for SCSI disks and ad is for IDE ones.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Adding an usb harddisk

2005-02-10 Thread John Pettitt

Ivan Roth wrote:
just note that it could not be /dev/da but /dev/ad, e.g, da is 
only for SCSI disks and ad is for IDE ones.

Actually no - usb disks look like scsi disks - so my 250GB usb drive 
is   /dev/da0

John
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


ULE issue on i386 5.3-STABLE

2005-02-10 Thread Doug Poland

Hello,

After following the ULE status thread with some interest, I decided to
enable on my i386, hyperthread-enabled, UNP machine.  Perhaps not the
best test bed, but a test none the less.

I'm running a series of make -jX buildworld to put load on the system
and running X with XFCE4 to get an idea of system responsiveness.  

The issue I'm seeing, seconds after launching gnome-terminal,
gnome-terminal terminal completely froze.  I can move and resize the
window, but cannot kill or close it.  A quick look at top shows:


38043 djp   200 21040K 16456K RUN1   0:01  0.00%  0.00% 
gnome-terminal

Also, gkrellmd and gkrellm have also both froze.  Here's that info:

39481 djp   200 16624K 13948K RUN1   0:02  0.00%  0.00% gkrellm
39321 djp   200  4324K  2220K RUN1   0:00  0.00%  0.00% gkrellmd 

In my kernel, I've added:

options SCHED_ULE   # ULE scheduler
options SMP # Symmetric MultiProcessor 
Kernel
options PREEMPTION

Is there any info I can provide that would shed some light on this?


-- 
Regards,
Doug,

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Adding an usb harddisk

2005-02-10 Thread Godwin Stewart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 11 Feb 2005 00:03:33 +0100, Ivan Roth [EMAIL PROTECTED] wrote:

 just note that it could not be /dev/da but /dev/ad, e.g, da is 
 only for SCSI disks and ad is for IDE ones.

Only for *internal* IDE drives.

USB drives use umass which presents them to the system as SCSI drives, so 
/dev/da* is accurate.

- -- 
G. Stewart - [EMAIL PROTECTED]

Sign spotted in a Laundromat:
AUTOMATIC WASHING MACHINES: PLEASE REMOVE ALL YOUR
CLOTHES WHEN THE LIGHT GOES OUT
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCC+tkK5oiGLo9AcYRAlB5AKC2vQuegEEfPRNa0+Gx8lUeW3agTQCcC8zu
PBWw26duuP4rA1jLDheNQwA=
=iHmL
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


5.2.1 - Freenet6 TSPC Client dumps core

2005-02-10 Thread Karl M. Joch
Hello,

i had the verion 1 of the freenet6 client running for a long time. now,
after upgrading to 2.1.1 on a 5.2.1 box the tspc client dumps core. it
sometime sets the tunnel up and the the tunnel works fine and it is possible
to ping6 www.kame.net and also access it via the http proxy. but tspc notes
going into daemon mode and instead of running in the background it
crashes. the tunnel is still alive after this, but no background checking
after tspc stops.

i havnt found any related posting in the groups and mailing archives and it
would be very interesting to upgrade to 2.1.1 because of the 3ffe addies are
more or less unsopported now and with 2.1.1 it is possible to get a 2001/48
routing.

many thanks for any hints,

karl

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ULE issue on i386 5.3-STABLE

2005-02-10 Thread Doug Poland
On Thu, Feb 10, 2005 at 05:10:22PM -0600, Doug Poland wrote:
 
 The issue I'm seeing, seconds after launching gnome-terminal,
 gnome-terminal terminal completely froze.  I can move and resize the
 window, but cannot kill or close it.  A quick look at top shows:
 
 38043 djp   200 21040K 16456K RUN1   0:01  0.00%  0.00% 
 gnome-terminal
 39481 djp   200 16624K 13948K RUN1   0:02  0.00%  0.00% gkrellm
 39321 djp   200  4324K  2220K RUN1   0:00  0.00%  0.00% gkrellmd 
 
 In my kernel, I've added:
 
 options   SCHED_ULE   # ULE scheduler
 options   SMP # Symmetric MultiProcessor 
 Kernel
 options   PREEMPTION
 
In addition, both mozilla and firefox hung moments after entering
the command from an aterm.  They were both in the same state as above.

I was pushing loads of about 15 and using Xorg quite smoothly (with
Nvidia drivers), also decoding mp3 stream with no skips or
interruptions.  Then I launched OpenOffice.org-1.1.4.  I got the splash
screen and the entire interface froze, no pings, nothing.  Forced to
perform a software reset.

Is this information useful?  Is there something else I can do as a ULE
tester to make these data more useful?

-- 
Regards,
Doug
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


atapci VIA 82C596B UDMA66 controller: problem for 5.X ?

2005-02-10 Thread Rob

Hi,

I have two PCs, with apparently a somewhat old
motherboard, since there's a maximum support for
UDMA66 by the harddisk controller.
The attached harddisks are newer and allow a
higher speed of UDMA100.

This combination of older motherboard and newer
harddisk causes great problems with 5.X (it never
did with 4.X). I have irregular crashes of X and
even crashes at initial bootup. All this is solved
by using  hw.ata.ata_dma=0, which forces the
harddisk to use the very low speed of PIO4 :(.

Both PCs have a VIA 82C596B UDMA66 controller.
I wonder if that is the problem for 5.X ?

On these two PCs, the output is of
   grep -i ata /var/run/dmesg.boot
is:

-- PC1 ---
atapci0: VIA 82C596B UDMA66 controller port
  0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7
  at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 43979MB IBM-DTLA-307045/TX6OA50C [89355/16/63]
 at ata0-master PIO4
acd0: CDROM CRD-8520B/1.00 at ata1-master PIO4


-- PC2 ---
atapci0: VIA 82C596B UDMA66 controller port
  0xc000-0xc00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7
  at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 76319MB WDC WD800JB-00CRA1/17.07W17
[155061/16/63] at ata0-master PIO4
ad1: 16448MB WDC WD172AA/05.05B05 [33420/16/63] at
 ata0-slave PIO4
acd0: CDRW HL-DT-ST RW/DVD GCC-4320B/1.00 at
 ata1-master UDMA33

-

I consider this a serious drawback of 5.3.

Any idea how this can be resolved?

Best regards,
Rob.



__ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


WAP gateway config

2005-02-10 Thread Matt Herzog
Hello.

I have an Atheros PCI card in my firewall/gateway machine.
It seems fully configured because the clients see a good strong signal 
but I can't get a dhcp lease from it. I'm not bothering with WEP just yet.

I followed the instructions found here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html

I ran these commands:
sysctl net.link.ether.bridge.enable=1
sysctl net.link.ether.bridge.config=wi0,vr0
sysctl net.inet.ip.forwarding=1

The ath0 is bridged with the vr0 which is the internal NIC.
dhcpd is running on vr0. I have the following in my ipf.conf:
pass in quick on ath0 from any to any
pass out quick on ath0 from any to any

un /root# wicontrol ath0
NIC serial number:  [  ]
Station name:   [ unaligned.com ]
SSID for IBSS creation: [ wap ]
Current netname (SSID): [ wap ]
Desired netname (SSID): [ wap ]
Current BSSID:  [ 00:0f:3d:ae:36:e0 ]
Channel list:   [ ffe ]
IBSS channel:   [ 11 ]
Current channel:[ 11 ]
Comms quality/signal/noise: [ 0 13 0 ]
Promiscuous mode:   [ Off ]
Intersil-Prism2 based card: [ 1 ]
Port type (1=BSS, 3=ad-hoc):[ 6 ]
MAC address:[ 00:0f:3d:ae:36:e0 ]
TX rate (selection):[ 11 ]
TX rate (actual speed): [ 11 ]
RTS/CTS handshake threshold:[ 2312 ]
Create IBSS:[ Off ]
Access point density:   [ 1 ]
Power Mgmt (1=on, 0=off):   [ 0 ]
Max sleep time: [ 100 ]
WEP encryption: [ Off ]
TX encryption key:  [ 1 ]
Encryption keys:[  ][  ][  ][  ]

My entire ifconfig:

fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=8VLAN_MTU
inet 24.98.219.30 netmask 0xfe00 broadcast 255.255.255.255
ether 00:03:47:0b:74:7b
media: Ethernet autoselect (100baseTX full-duplex)
status: active
ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
ether 00:0f:3d:ae:36:e0
media: IEEE 802.11 Wireless Ethernet DS/11Mbps hostap (autoselect 
hostap)
status: associated
ssid mycod 1:mycod
channel 11 authmode OPEN powersavemode OFF powersavesleep 100
rtsthreshold 2312 protmode CTS
wepmode OFF weptxkey 1
vr0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500
inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255
ether 00:d0:68:01:55:a3
media: Ethernet autoselect (100baseTX full-duplex)
status: active
plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet 127.0.0.1 netmask 0xff00 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: WAP gateway config

2005-02-10 Thread Mark Andrews

 Hello.
 
 I have an Atheros PCI card in my firewall/gateway machine.
 It seems fully configured because the clients see a good strong signal 
 but I can't get a dhcp lease from it. I'm not bothering with WEP just yet.
 
 I followed the instructions found here:
 
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.ht
 ml
 
 I ran these commands:
 sysctl net.link.ether.bridge.enable=1
 sysctl net.link.ether.bridge.config=wi0,vr0

Shouldn't that be:

sysctl net.link.ether.bridge.config=ath0,vr0

 sysctl net.inet.ip.forwarding=1
 
 The ath0 is bridged with the vr0 which is the internal NIC.
 dhcpd is running on vr0. I have the following in my ipf.conf:
 pass in quick on ath0 from any to any
 pass out quick on ath0 from any to any
 
 un /root# wicontrol ath0
 NIC serial number:  [  ]
 Station name:   [ unaligned.com ]
 SSID for IBSS creation: [ wap ]
 Current netname (SSID): [ wap ]
 Desired netname (SSID): [ wap ]
 Current BSSID:  [ 00:0f:3d:ae:36:e0 ]
 Channel list:   [ ffe ]
 IBSS channel:   [ 11 ]
 Current channel:[ 11 ]
 Comms quality/signal/noise: [ 0 13 0 ]
 Promiscuous mode:   [ Off ]
 Intersil-Prism2 based card: [ 1 ]
 Port type (1=BSS, 3=ad-hoc):[ 6 ]
 MAC address:[ 00:0f:3d:ae:36:e0 ]
 TX rate (selection):[ 11 ]
 TX rate (actual speed): [ 11 ]
 RTS/CTS handshake threshold:[ 2312 ]
 Create IBSS:[ Off ]
 Access point density:   [ 1 ]
 Power Mgmt (1=on, 0=off):   [ 0 ]
 Max sleep time: [ 100 ]
 WEP encryption: [ Off ]
 TX encryption key:  [ 1 ]
 Encryption keys:[  ][  ][  ][  ]
 
 My entire ifconfig:
 
 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
   options=8VLAN_MTU
   inet 24.98.219.30 netmask 0xfe00 broadcast 255.255.255.255
   ether 00:03:47:0b:74:7b
   media: Ethernet autoselect (100baseTX full-duplex)
   status: active
 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
   inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
   ether 00:0f:3d:ae:36:e0
   media: IEEE 802.11 Wireless Ethernet DS/11Mbps hostap (autoselect ho
 stap)
   status: associated
   ssid mycod 1:mycod
   channel 11 authmode OPEN powersavemode OFF powersavesleep 100
   rtsthreshold 2312 protmode CTS
   wepmode OFF weptxkey 1
 vr0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500
   inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255
   ether 00:d0:68:01:55:a3
   media: Ethernet autoselect (100baseTX full-duplex)
   status: active
 plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
   inet 127.0.0.1 netmask 0xff00 
 ___
 freebsd-stable@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Server reboots when silo overflows - FreeBSD 4.11

2005-02-10 Thread Lefteris Tsintjelis
 sio5: 1 more silo overflow (total 7)
 puc0: VScom PCI-200L port
 0xb000-0xb007,0xb400-0xb407,0xb800-0xb807,0xd000-0xd007 mem
 0xea80-0xea80003f irq 14 at device 12.0 on pci2
 sio4: configured irq 14 not in bitmap of probed irqs 0x8000
 sio4: type 16550A
 sio5: configured irq 14 not in bitmap of probed irqs 0x8000
 sio5: type 16550A
 
 How do you have device sio configured in your kernel ?  Are you trying to
 specify the ports for the puc attached serial ports ?  All you need is
 
 device  sio
 device  puc

device  sio0at isa? port IO_COM1 flags 0x10 irq 4
device  sio1at isa? port IO_COM2 irq 3
device  sio2at isa? disable port IO_COM3 irq 5
device  sio3at isa? disable port IO_COM4 irq 9

device  puc

No other sio specific devices for puc other than the kernel's default.
The sio0/1 never gave me any trouble though. Its the sio4/5 (puc)
that fail me. BTW this bug is old and run to it again about a year ago.

 Also, enable crash dumps and build a debug kernel.

I enabled the debug symbols already and I have a few crash dumps.
What can do I do next?

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: atapci VIA 82C596B UDMA66 controller: problem for 5.X ?

2005-02-10 Thread Mark Kirkwood
Rob,
I am currently running 5.3 Release on a Tyan Trinity 400 (VIA 82C596B 
UDMA66) with 2 x Seagate Barracude IV (UDMA100) and have no stability 
issues. e.g from dmesg:

atapci0: VIA 82C596B UDMA66 controller port 
0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 19092MB ST320011A/3.10 [38792/16/63] at ata0-master UDMA66
ad1: 19092MB ST320011A/3.10 [38792/16/63] at ata0-slave UDMA66
acd0: CDRW CREATIVE CD-RW RW8439E/1R09 at ata1-master PIO4

What does your dmesg show if you dont force ata_dma=0?
H - you have an IBM disk in one pc and WDs in the other, hard to 
believe that the disks are the issue. Do both pcs have the same mobo? 
(if so what is it).

Something else - did you upgrade from 4.x or fresh install?
With respect to attempting a fix, you could try
$ atacontrol mode 0 UDMA66 UDMA66
immediately after boot, to see if you can force a sensible transfer mode 
setting.

regards
Mark
Rob wrote:
Hi,
I have two PCs, with apparently a somewhat old
motherboard, since there's a maximum support for
UDMA66 by the harddisk controller.
The attached harddisks are newer and allow a
higher speed of UDMA100.
This combination of older motherboard and newer
harddisk causes great problems with 5.X (it never
did with 4.X). I have irregular crashes of X and
even crashes at initial bootup. All this is solved
by using  hw.ata.ata_dma=0, which forces the
harddisk to use the very low speed of PIO4 :(.
Both PCs have a VIA 82C596B UDMA66 controller.
I wonder if that is the problem for 5.X ?
On these two PCs, the output is of
   grep -i ata /var/run/dmesg.boot
is:
-- PC1 ---
atapci0: VIA 82C596B UDMA66 controller port
  0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7
  at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 43979MB IBM-DTLA-307045/TX6OA50C [89355/16/63]
 at ata0-master PIO4
acd0: CDROM CRD-8520B/1.00 at ata1-master PIO4
-- PC2 ---
atapci0: VIA 82C596B UDMA66 controller port
  0xc000-0xc00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7
  at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 76319MB WDC WD800JB-00CRA1/17.07W17
[155061/16/63] at ata0-master PIO4
ad1: 16448MB WDC WD172AA/05.05B05 [33420/16/63] at
 ata0-slave PIO4
acd0: CDRW HL-DT-ST RW/DVD GCC-4320B/1.00 at
 ata1-master UDMA33
-
I consider this a serious drawback of 5.3.
Any idea how this can be resolved?
Best regards,
Rob.
		
__ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


5.3-stable doesn't ifconfig at startup

2005-02-10 Thread Kenneth W Cochran
Hello -stable:

Any idea(s) why (my) 5.3-stable (as of 9 February) isn't
configuring the network interface or setting up the default route?

I installed 5.3-release from CD and things worked fine.
Then I updated the system sources (via cvsup) to RELENG_5 and
went through {build,install}world/mergemaster/reboot as outlined
in /usr/src/UPDATING and now I get no network interfaces
configured  no default route set.  I've tracked RELENG_4 for
years with nothing like this ever happening.  Kernel has not been
reconfigured (yet), it's still GENERIC, albeit RELENG_5 now.

In looking through the rc scripts, it appears that network
interface(s) are being renamed but I see no references to this
in, say, UPDATING or errara or other documentation.  Any ideas?
Pointers to documentation are welcome. :)

Thanks,

-kc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 5.3-stable doesn't ifconfig at startup

2005-02-10 Thread Ion-Mihai Tetcu
On Fri, 11 Feb 2005 02:00:39 -0500 (EST)
Kenneth W Cochran [EMAIL PROTECTED] wrote:

 Hello -stable:
 
 Any idea(s) why (my) 5.3-stable (as of 9 February) isn't
 configuring the network interface or setting up the default route?
 
 I installed 5.3-release from CD and things worked fine.
 Then I updated the system sources (via cvsup) to RELENG_5 and
 went through {build,install}world/mergemaster/reboot as outlined
 in /usr/src/UPDATING and now I get no network interfaces
 configured  no default route set.  I've tracked RELENG_4 for
 years with nothing like this ever happening.  Kernel has not been
 reconfigured (yet), it's still GENERIC, albeit RELENG_5 now.
 
 In looking through the rc scripts, it appears that network
 interface(s) are being renamed but I see no references to this
 in, say, UPDATING or errara or other documentation.  Any ideas?

mergemaster pilot error ?
If you didn't changed something in them I'd suggest wiping /etc/rc.d/*
and /etc/defaults/* and do a mergermaster -i


-- 
IOnut
Unregistered ;) FreeBSD user


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]