Re: current.freebsd.org problems?
matusita> When I backout this change, the problem seems disappeared...
This is sample shell script to reproduce recent kernel hungup:
#!/bin/sh
dd of=/tmp/image if=/dev/zero count=1440 bs=1k
awk 'BEGIN {printf "%c%c", 85, 170}' | \
dd of=/tmp/image obs=1 seek=510 conv=notrunc
vnconfig -s labels -c /dev/rvn0 /tmp/image
disklabel -Brw /dev/rvn0 fd1440
newfs -i 8 -T fd1440 -o space /dev/rvn0c
mount /dev/vn0c /mnt
cp /etc/rc /mnt
umount /mnt
vnconfig -u /dev/rvn0
exit 0
If you are running recent (at least Sep/30/2000) -current kernel, and
your newfs(8) is newer mkfs.c (rev 1.30) it will hungup as soon as
cp(1) is invoked.
-- -
Makoto `MAR' MATSUSHITA
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
jhay> It looks like I spoke too soon. My 2000-10-05 kernel that previously jhay> worked also now panics. It must be somewhere when the floppies are jhay> made. Maybe there is a problem in newfs(8). peter 2000/10/16 17:41:37 PDT Modified files: sbin/newfs mkfs.c Log: Implement simple write combining for newfs - this is particularly useful for large scsi disks with WCE = 0. This yields around a 7 times speedup on elapsed newfs time on test disks here. 64k clusters seems to be the sweet spot for scsi disks using our present drivers. Revision ChangesPath 1.30 +38 -1 src/sbin/newfs/mkfs.c When I backout this change, the problem seems disappeared... -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
> > jhay> For now I just went back to an older kernel that works for me. > > Would you please explain "an older kernel" ? I'm using a kernel as of > Sep/30/2000 and it panics. > > *** > > Note that this (Sep/30/2000) kernel doesn't panic until Oct/13/2000. > Between Oct/14/2000 and Oct/17/2000, "make release" was failed at > buildworld. Oct/18/2000, panic. Oct/19/2000, also panic. > It looks like I spoke too soon. My 2000-10-05 kernel that previously worked also now panics. It must be somewhere when the floppies are made. On the serial console I see: Oct 21 04:44:49 beast /boot/kernel/kernel: /mnt: optimization changed from SPACE to TIME /mnt: bad dir ino 2 at offset 0: mangled entry panic: ufs_dirbad: bad dir cpuid = 0; lapic.id = 0100 boot() called on cpu#0 Does the mangled entry on /mnt mean there is something wrong in the /mnt filesystem? That would be the floppy image. Also it does not reboot after the panic. It just get stuck after printing a lot of "microuptime() went backwards (28431.4508250 -> 28431.2820885)" messages. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
> > $ For now I just went back to an older kernel that works for me. > > How older is your kernel? > My kernel build 2000-09-21 JST. It panic when "make release". Not that old. 2000-10-05. The machine is a dual 266MHz PII. I have no problem building releases using "NODOC=YES WORLD_FLAGS=-j4" when the source is not broken. :-) I'm trying now again after the bktr fix went in. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
From: John Hay <[EMAIL PROTECTED]> Subject: Re: current.freebsd.org problems? Date: Fri, 20 Oct 2000 10:07:14 +0200 (SAT) $ For now I just went back to an older kernel that works for me. How older is your kernel? My kernel build 2000-09-21 JST. It panic when "make release". --- Masanori Kanaoka [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
jhay> For now I just went back to an older kernel that works for me. Would you please explain "an older kernel" ? I'm using a kernel as of Sep/30/2000 and it panics. *** Note that this (Sep/30/2000) kernel doesn't panic until Oct/13/2000. Between Oct/14/2000 and Oct/17/2000, "make release" was failed at buildworld. Oct/18/2000, panic. Oct/19/2000, also panic. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
> $ I'm very interested if current.jp.freebsd.org was hung up when "make > $ release" procedure was running. current.jp.freebsd.org was hung up in > $ these two days, when making a boot floppy (the hungup was occured > $ *exactly* the same point). > > I have same experience.My current-box was hung up when "make release". > then, log is below: > > sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/mfsfd >8000 minimum2 > disklabel: ioctl DIOCWLABEL: Operation not supported by device > Warning: Block size restricts cylinders per group to 6. > Warning: 2432 sector(s) in last cylinder unallocated > /dev/rvnn0c:5760 sectors in 2 cylinders of 1 tracks, 4096 sectors > 2.8MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) > super-block backups (for fsck -b #) at: > 32 > 3700 blocks > Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on > /dev/vnn0c 2803 1868 71172% 67 31518% /mnt > >>> Filesystem is 2880 K, 711 left > >>> 8000 bytes/inode, 315 left > mfsroot: 71.4% > I have also seen this on my current box when building -current snaps. At the same time I see 10 or so "kernel trap 12 with interrupts disabled" messages on the console before it wedges really good. For now I just went back to an older kernel that works for me. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
kana> I have same experience.My current-box was hung up when "make release". kana> then, log is below: Ya, exactly the same point of current.jp.FreeBSD.org. The same story should be applied to current.FreeBSD.org. We cannot make a -current distribution now. Changes from Oct/10/2000 to now cause this problem. This logfile denotes that some commands (expr, rm, mknod, umount, vnconfig) in src/release/doFS.sh causes kernel hungup. Is there any fatal changes, committers ? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
From: Makoto MATSUSHITA <[EMAIL PROTECTED]> Subject: Re: current.freebsd.org problems? Date: Fri, 20 Oct 2000 15:30:30 +0900 $ I'm very interested if current.jp.freebsd.org was hung up when "make $ release" procedure was running. current.jp.freebsd.org was hung up in $ these two days, when making a boot floppy (the hungup was occured $ *exactly* the same point). I have same experience.My current-box was hung up when "make release". then, log is below: sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/mfsfd 8000 minimum2 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 2432 sector(s) in last cylinder unallocated /dev/rvnn0c:5760 sectors in 2 cylinders of 1 tracks, 4096 sectors 2.8MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) super-block backups (for fsck -b #) at: 32 3700 blocks Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on /dev/vnn0c 2803 1868 71172% 67 31518% /mnt >>> Filesystem is 2880 K, 711 left >>> 8000 bytes/inode, 315 left mfsroot: 71.4% --- Masanori Kanaoka [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
jkh> I'll look into this tomorrow morning, thanks. I'm very interested if current.jp.freebsd.org was hung up when "make release" procedure was running. current.jp.freebsd.org was hung up in these two days, when making a boot floppy (the hungup was occured *exactly* the same point). -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
I'll look into this tomorrow morning, thanks. > Bill G <[EMAIL PROTECTED]> writes: > > I have been trying to download a current snapshot from > > current.freebsd.org for the past few days without success. > > The error message I receive is 'Login incorrect' - I am > > doing a standard anonymous ftp, as always. Just wanted > > to make sure someone was aware of the problem, if not > > already. > > root@des /home/des# fetch ftp://current.freebsd.org/etc/ftpmotd > scheme: [ftp] > user: [] > password: [] > host: [current.freebsd.org] > port: [0] > document: [/etc/ftpmotd] > ---> current.freebsd.org:21 > <<< 220 usw2.freebsd.org FTP server (Version wu-2.6.0(1) Thu Jul 6 03:57:36 C DT 2000) ready. > >>> USER ftp > <<< 331 Guest login ok, send your complete e-mail address as password. > >>> PASS [EMAIL PROTECTED] > <<< 530 Login incorrect. > fetch: ftpmotd: Not logged in > > Hmm, weird. JKH, current is your baby, isn't it? > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
Bill G <[EMAIL PROTECTED]> writes: > I have been trying to download a current snapshot from > current.freebsd.org for the past few days without success. > The error message I receive is 'Login incorrect' - I am > doing a standard anonymous ftp, as always. Just wanted > to make sure someone was aware of the problem, if not > already. root@des /home/des# fetch ftp://current.freebsd.org/etc/ftpmotd scheme: [ftp] user: [] password: [] host: [current.freebsd.org] port: [0] document: [/etc/ftpmotd] ---> current.freebsd.org:21 <<< 220 usw2.freebsd.org FTP server (Version wu-2.6.0(1) Thu Jul 6 03:57:36 CDT 2000) ready. >>> USER ftp <<< 331 Guest login ok, send your complete e-mail address as password. >>> PASS [EMAIL PROTECTED] <<< 530 Login incorrect. fetch: ftpmotd: Not logged in Hmm, weird. JKH, current is your baby, isn't it? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current.freebsd.org problems?
I have been trying to download a current snapshot from current.freebsd.org for the past few days without success. The error message I receive is 'Login incorrect' - I am doing a standard anonymous ftp, as always. Just wanted to make sure someone was aware of the problem, if not already. Thanks, Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
