5.3: iostat does not know anything about acd

2005-03-18 Thread Andriy Gapon

I've just upgraded to 5.3-RELEASE-p5 and noticed that neither iostat nor
systat -vmstat show statistics about acd devices, although I can use
them perfectly well. If I enable atapicam then I can see statistic for
cd and pass devices, but still nothing for acd. In 4.X I've never had a
problem with that.
ATA relate devices in kernel:
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
#device atapicam

Am I missing anything ?

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


Re: need ISO-image for a new machine install

2005-03-18 Thread Pertti Kosunen
Emanuel Strobl wrote:
Unfortunately there is no mini-inst anymore since install and fixit CD is 
combined now. You have to download the whole 780MB.

Why 780MB? It doesn't fit on normal 700MB CD.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: PPP routing failure

2005-03-18 Thread bob

Check out the install guide at
http://www.unixguide.net/freebsd/fbsd_installguide/index.php
it has the best step by step instructions for using userppp.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Peter C.
Lai
Sent: Thursday, March 17, 2005 8:37 PM
To: freebsd-questions@freebsd.org; freebsd-net@freebsd.org;
freebsd-stable@freebsd.org
Subject: PPP routing failure


Hi everyone -
I'm experiencing some funky routing failures when I dialup netscape
internet
via user-level PPP:
I can negotiate IPCP fine; get a point-to-point link via tun0:
myaddr: 172.143.224.146; hisaddr: 63.152.0.70
When the default route is setup to 63.152.0.70, all of my packets
are
blackholed after the first router hop. I am not using NAT.
The PPP link works perfectly fine in windows dialup networking. So I
dunno
what is wrong. When I look at the routing table in windows, it seems
backwards:

DESTNM  GW  IF
default 0   myaddr  ppp
hisaddr 0x  myaddr  ppp
localhost   0xff00  localhost   localhost
myaddr  0x  localhost   localhost
myaddr.255.255* 0x  myaddr  ppp
multicast   multicast   myaddr  ppp

*this is the first 2 dotted quads of myaddr appended with 255.255

If I try to manually set these routes in 5.3-R, I still can't get
out :(
Setting ADD DEFAULT MYADDR doesn't work, because ppp will still
think MYADDR
is 0.0.0.0. Either I need sleep or something is funky here...

--
Peter C. Lai
University of Connecticut
Dept. of Molecular and Cell Biology
Yale University School of Medicine
SenseLab | Research Assistant
http://cowbert.2y.net/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
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]


Building snapshot CDs

2005-03-18 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I tried to build a local snapshot from a fresh cvsup today, it
failed with touch not found, so I patched /usr/src/Makefile.inc1 as
follows:
*** Makefile.inc1~  Wed Mar  2 08:22:57 2005
- --- Makefile.inc1   Fri Mar 18 12:11:15 2005
***
*** 558,564 
~for prog in [ awk cap_mkdb cat chflags chmod chown \
~date echo egrep find grep \
~ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
!   test true uname wc zic; do \
~cp `which $$prog` ${INSTALLTMP}; \
~done
~${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}
- --- 558,564 
~for prog in [ awk cap_mkdb cat chflags chmod chown \
~date echo egrep find grep \
~ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
!   test touch true uname wc zic; do \
~cp `which $$prog` ${INSTALLTMP}; \
~done
~${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}
Did I miss something?
Michael Butler CISSP
Security Consultant
PGP Key ID: 0x5E873CC5
Fingerprint: 2CFF 581F D192 F885 7ED9 3C44 889C A479 5E87 3CC5
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (MingW32)
iD8DBQFCOxfRiJykeV6HPMURAluuAKCgX4qkRNhItlQU4cfYOsGmY9fRFQCgqaC8
T5Ou1IUqDRJ3I9tdARitw7Q=
=EndD
-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: Building snapshot CDs

2005-03-18 Thread Kent Stewart
On Friday 18 March 2005 10:02 am, Michael Butler wrote:
 When I tried to build a local snapshot from a fresh cvsup today, it
 failed with touch not found, so I patched /usr/src/Makefile.inc1 as
 follows:

 *** Makefile.inc1~  Wed Mar  2 08:22:57 2005
 --- Makefile.inc1   Fri Mar 18 12:11:15 2005
 ***
 *** 558,564 
 ~for prog in [ awk cap_mkdb cat chflags chmod chown \
 ~date echo egrep find grep \
 ~ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
 !   test true uname wc zic; do \
 ~cp `which $$prog` ${INSTALLTMP}; \
 ~done
 ~${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}
 --- 558,564 
 ~for prog in [ awk cap_mkdb cat chflags chmod chown \
 ~date echo egrep find grep \
 ~ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
 !   test touch true uname wc zic; do \
 ~cp `which $$prog` ${INSTALLTMP}; \
 ~done
 ~${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}

 Did I miss something?


Having touch show up in a post buildworld is frequently a sign of a 
system clock running behind time. It creates a file but the file is 
older than the files you cvsuped. Make thinks it needs to remake the 
file it created and away you go.

Kent

-- 
Kent Stewart
Richland, WA

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


page fault in sched_add_internal on RELENG_5 with ULE + PREEMPTION

2005-03-18 Thread Kris Kennaway
quad-cpu amd64 package machine running RELENG_5 with ULE and
PREEMPTION, panicked with:

Mar 17 19:51:58 fbsd-amd64 kernel: pid 8261 (try), uid 0: exited on
signal 10 (core dumped)
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0x230
fault code  = supervisor read, page not present
instruction pointer = 0x8:0x8039080f
stack pointer   = 0x10:0xbe420a60
frame pointer   = 0x10:0xff03e1380c60
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 44 (irq30: mpt1)
trap number = 12
panic: page fault
cpuid = 2
panic: mi_switch: switch in a critical section
cpuid = 2
panic: mi_switch: switch in a critical section
cpuid = 2
[...]

readelf shows that the IP is in:

803907d0 sched_add_internal

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


USB disk hang - 5.4PRE - gstripe

2005-03-18 Thread John Pettitt

I just upgraded a box to 5.4PRE and started experiencing regular system
hangs at exactly 1AM - I traced it to BackupPC which was starting it's
run at that time backing up to a gstripe set made from two 300GB USB disks.

The first thing I assumed was that something in Samba or perl didn't
like the 5.4 upgrade so I rebuilt my entire ports tree (portupgrade -fa)
to be sure I had no old libs.  It still fails.

Next I moved the two drives out of their USB housings and put them on
the IDE controller (disconnecting the CD burner to make space).  It's
working fine like that (all be it with disks hanging out the side of the
machine).

So it looks like USB is the culprit.  A few data points:

1) It worked fine on 5.3
2) Motherboard is an Intel D845GVSR with a Celeron D 2.9Ghz and 512Mb Ram
3) USB disk interfaces are from a couple of WD external drives (although
the drives are in fact Maxtor because I upgraded them WD boxes)
4) A single WD250GB disk also on USB seems to work fine  it's only the
stripe set that has a problem
5) When it fails the entire disk system locks (including IDE) but the
machines keeps running until each process locks as it needs to talk to
the disk
6) No meaningful syslog log entries

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