system wedges running dd with of=/dev/fd0
On a -current cvsuped on Jan2-2003 uname -a FreeBSD k7.jibe.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Jan 8 09:21:54 MST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 To reproduce error... cd /somedir where somedir has a valid floppy image file like kern.flp Then... dd if=kern.flp of=/dev/fd0 and machine wedges. In the best cases using a GENERIC kernel the screen goes blank, keyboard is inactive, hard drive light is on 100%. Have to recycle input power to get back in control. WARNING..WARNING..WARNING... In worst cases like the 1st time I noticed this, I was running a custom kernel and using the /sysutils/sdd port. In addition to all the above nasty symptoms on subsequent power up the machine was dead. BIOS had been butchered. I had to go onto the motherboard and force a BIOS reset to factory defaults and then reconfig the BIOS to get the system back to a usable state. VERY UGLY I've tried a lot of test permutations that i'll not go into here, but the above dd incantation fails every invocation. Also note that on this same harddrive I have a partition that runs FreeBSD 4.7R and dd and sdd to/from the floppy work flawlessly. Which makes me tend to believe that this is not a hardware problem. In GENERIC these are all on options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN Yet nothing is trapped and I see nothing logged in /var/log/messages. I also have dumpdev=/dev/ad4s4b dumpdir=/usr/flameout in my /etc/rc.conf and nothing is getting picked up by savecore in there on reboot. Can anyone else duplicate this? If so then a PR is in order. If not I'll re-cvsup and rebuild and test again and repost for further help. As the cusp of 5.0 Release draws near I am distressed to have run into a problem of this severity. -bob- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
installworld dies .../usr/share/examples/ipfw/change_rules.sh
I cvsup'd sources at about 13:00 MST 6-Jun-2001 make -j6 -DNOPROFILE=true buildworld --- Completed successfully make -DNOPROFILE=true installworld --- Failed as follows. install -c -o root -g wheel -m 644 ipfw/change_rules.sh /usr/share/examples/ipfw/change_rules.sh install: /usr/share/examples/ipfw/change_rules.sh: No such file or directory *** Error code 71 Stop in /usr/src/share/examples. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Went to /usr/share/examples and found that the ipfw directory did not exist. My successful work-around was to create it manually and re-run the installworld. I only track -current on occasion. Previous upgrade was Mar18,2001. src/share/examples/ipfw/change_rules.sh was new to the tree as of yesterday. This failure smacks of a Makefile deficiency. Is this a valid problem? Did I grab my cvsup at an unlucky time in relation to this file being recently committed? Did I commit an egregious error by using the -j6 switch in the buildworld? 1 3 o 1 3 13o13 BoB To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld failed
I'll chime in here with a "me too". My make buildworld(s) failed with
the *identical* error as originally posted by daniel
[EMAIL PROTECTED] on 16-Aug-2000.
I tried #make -j4 buildworld and another attempt of #make buildworld.
Both attempts failed with the same error.
I tried this on a 3.4-RELEASE system with -current cvsup'd on
20-Aug-2000 @ 07:00 (MST).
OK, now there are 2 of us with the identical symptom. Where did we go
astray?
BoB KoT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
