Re: -current hangs during boot
Did I miss something on the /dev/random hang? I don't know... During a `shutdown -r now`, the boot process hangs for more than an hour. I thought this was supposed to work. However, jwd's receipe for recovery works. I repeated this three times, although I only waited an hour the last time (dinner!). I am running a recent SMP system, uname and dmesg below. Are you _completely_ up to date with /etc/*? Dou you run mergemaster after each make world/make kernel? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
I cannot make mergemaster work. Tried twice earlier in the year and took several hours to recover... Don't know what my problem is. However, I have a script that compares and lists diffs in /etc/rc* and /etc/defaults/* to those in src/etc. Normally, I manually copy those files to /etc. # grep '$FreeBSD' /etc/rc /etc/rc.shutdown /etc/defaults/rc.conf /etc/rc:# $FreeBSD: src/etc/rc,v 1.239 2000/10/22 19:10:13 phk Exp $ /etc/rc.shutdown:# $FreeBSD: src/etc/rc.shutdown,v 1.15 2000/10/20 20:26:05 ache Exp$ /etc/defaults/rc.conf:# $FreeBSD: src/etc/defaults/rc.conf,v 1.83 2000/10/29 19:59:04 ume Exp $ These are the proper versions. After looking through rc.shutdown, 'Writing entropy file.' is not displayed. In /etc/defaults/rc.conf and /usr/src/etc/defaults/rc.conf, I have ... entrop^%]0y_file="/entropy" # Set to NO to disable caching entropy through reboots. ... Garble? Fixing this fixes the problem. Thanks Mark. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Did I miss something on the /dev/random hang? During a `shutdown -r now`, the boot process hangs for more than an hour. I thought this was supposed to work. However, jwd's receipe for recovery works. I repeated this three times, although I only waited an hour the last time (dinner!). I am running a recent SMP system, uname and dmesg below. tomdean = from the console = ... Doing additional network setup: portmap. Starting final network daemons: mountd nfsd rpc.statd nfsiod \ NFS access cache time=2. setting ELF ldconfig path: /usr/lib /usr/lib/compat \ /usr/X11R6/lib /usr/local/lib --- ^t at this point, after waiting an hour load: 0.00 cmd: ldconfig 137 [rndblk] 0.00u 0.00s 0% 104k ^\Reboot interrupted Nov 3 17:38:40 celebris /boot/kernel/kernel: pid 137 (ldconfig), \ uid 0: exited on signal 3 (core dumped) Enter full pathname of shell or RETURN for /bin/sh: # ls -al /etc /dev/random # exit Skipping disk checks ... Doing initial network setup:. ... uname -a == FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Nov 3 \ 16:30:23 PST 2000 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 === dmesg Copyright (c) 1992-2000 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.0-CURRENT #1: Fri Nov 3 16:30:23 PST 2000 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (122.68-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC real memory = 100663296 (98304K bytes) avail memory = 94740480 (92520K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc0314000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031409c. Intel Pentium detected, installing workaround for F00F bug npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 ncr0: ncr 53c810 fast10 scsi port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: Intel 82378IB PCI to ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 pci0: Matrox MGA Millennium 2064W graphics accelerator at 6.0 irq 9 de0: Digital 21041 Ethernet port 0xe880-0xe8ff mem 0xfedfbe80-0xfedfbeff irq 10 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 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 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: IBM Enhanced (101/102-key) KC can't assign resources unknown: Microsoft PS/2 Mouse can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: LPT printer port can't assign resources unknown: Floppy Controller can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 10 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1s1a da0 at ncr0 bus 0 target 0 lun 0 da0: QUANTUM FIREBALL1080S 1Q09 Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: QUANTUM EMPIRE_1080S 1240 Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: TOSHIBA CD-ROM XM-5401TA 3605 Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ncr0 bus 0 target 1 lun 0 da1: IBM DNES-309170 SAH0 Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) SMP: AP CPU #1 Launched! de0: enabling BNC port pid 137 (ldconfig), uid 0: exited on signal
Re: Need help to boot (was : -current hangs during boot)
Hello FreeBSD-hackers. I had my first CVSup-ed source tre d/loaded today. It compiled correctly (make buildworld) and installed correctly (make installworld). Mistake #1 was CVSuping -CURRENT. [...] NOTE #3. Your machine is probably totaly broke. And you will need to reinstall. This time I suggest you install 4.1.1-RELEASE and follow -STABLE *not* -CURRENT. Hey pal, don't chew me up like that ... I solved the problem myself look, I'm not here to bother you guys, I use FreeBSD for years now, and I always used -RELEASE, bought cds the rest. I've also built several ISDN-routers, all FreeBSD-based. I simply LOVE the FreeBSD project, and, since I have some spare time, I decided to start testing -CURRENT. I also built modified many PicoBSD installations on a floppy for custom purposes. Even if I am "green" to many subjects, it doesn't mean I am a complete idiot. I can learn, damnit, but I have to start with something. Geez Bye, Wyk'00 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Need help to boot (was : -current hangs during boot)
Hello FreeBSD-hackers. I had my first CVSup-ed source tre d/loaded today. It compiled correctly (make buildworld) and installed correctly (make installworld). But on rebooting the box, the loader fails to find a bootable kernel. It seems my loader.conf got trashed somewhere ... I get the list of the / partition, but the command load kernel gives me the "not found" message. I'm totally green on the subject, please, give me a bit of advice on how can I make the box boot again (or if you have some pointers to web resources, man pages etc.), and where I messed up the whole thing. Thanks guys! Bye, Wyk'00 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Need help to boot (was : -current hangs during boot)
I had my first CVSup-ed source tre d/loaded today. It compiled correctly (make buildworld) and installed correctly (make installworld). But on rebooting the box, the loader fails to find a bootable kernel. It seems my loader.conf got trashed somewhere ... I get the list of the / partition, but the command load kernel gives me the "not found" message. You should have build and installed a new kernel at the same time. Try 'boot /kernel'. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
re: -current hangs during boot (UPDATING entry)
It does look like an updating entry is needed for this badly. I did the following things, some of which may not be needed, and now my -current boxes boot OK. 1. update MAKEDEV from /usr/src/etc, run MAKEDEV all 2. update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc 3. add random_load="YES" to /boot/loader.conf 4. update /etc/login.conf from /usr/src/etc 5. do a "shutdown -r now" which creates the entropy file and reboots Now the system boot does not hang at the ldconfig spots. It does look like there is a lot to do to get back on course, enough to justify adding to UPDATING. Later Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
Thanks for the updates. A few questions below. -John - Mark Hittinger's Original Message - It does look like an updating entry is needed for this badly. I did the following things, some of which may not be needed, and now my -current boxes boot OK. 1. update MAKEDEV from /usr/src/etc, run MAKEDEV all 2. update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc 3. add random_load="YES" to /boot/loader.conf or add the random device to the kernel config file. 4. update /etc/login.conf from /usr/src/etc I don't remember having to do this... was there a specific reason? 5. do a "shutdown -r now" which creates the entropy file and reboots Now the system boot does not hang at the ldconfig spots. It does look like there is a lot to do to get back on course, enough to justify adding to UPDATING. Later Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. You can leave them in, with option "noauto", and mount them later with "mount -a -t mfs". -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
In message [EMAIL PROTECTED] Leif Neland writes: : Hi there, : : I've done a very recent week's make world(S) on -current, making : and installing world and kernel go fine, but all hang on boot, : with no error codes or msgs. : : Solution: Due to changes in the random/entropy stuff, you have to reboot : the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". : : (Why do we have a separate reboot command? Couldn't it just be an alias : for shutdown -r now?) reboot should be a seprate command. It should, however, cause the shutdown scripts to run unless it is run -f. shutdown implies sending all messages to all users of NFS filesystems, which isn't desirable in many cases. At least that's why my fingers type reboot to this day: On sunos 4.0 (really Solbourne OS/MP 4.0D) in a large company these messages would scare more people than they informed... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: devicerandom # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
It didn't work without the device line when I tested it last week(Thursday/Friday). -John - David O'Brien's Original Message - On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: device random # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
You need to put random_load="YES" into /boot/loader.conf. Optionally, you can load random.ko during the boot process. John W. De Boskey wrote: It didn't work without the device line when I tested it last week(Thursday/Friday). - David O'Brien's Original Message - On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: devicerandom # Entropy device Are you implying the random.ko module is broken? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, 23 Oct 2000, John W. De Boskey wrote: I'm beginning to think we need an updating entry. 1. Make sure /dev/random exists 'cd /dev sh MAKEDEV std' Unless you are using devfs. 2. Make sure your kernel includes: devicerandom # Entropy device Or the appropriate line in /boot/mumble.conf 3. Make sure /etc/rc is at rev 1.237 or higher. 4. Make sure /etc/rc.shutdown is at rev 1.13 or 1.15 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. A better solution would be to increase the granularity of the file system mounts so that the MFS systems were mounted after the entropy gathering. There are a couple of reasons I changed the ordering on the two reseeding attempts, one of the big ones was that for the "manual" reseed (i.e., no entropy file) we want more parts of the system mounted so that we have more potential entropy gathering tools. Rest sounds good... Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
I'm beginning to think we need an updating entry. 1. Make sure /dev/random exists 'cd /dev sh MAKEDEV std' 2. Make sure your kernel includes: device random # Entropy device 3. Make sure /etc/rc is at rev 1.237 or higher. 4. Make sure /etc/rc.shutdown is at rev 1.13 or 1.15 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. 6. Reboot your system via 'init 6' or 'shutdown -r now' (or similar). Do not use 'reboot'. 7. If at any time during the boot process a 'cntrl-t' shows a process hung in 'rndblk', hit 'cntrl-\', 'ls -al /etc /dev/random', and then 'exit'. This should get your machine to boot for this session until you figure out which of the above are not done. -John - Brian O'Shea's Original Message - On Sun, Oct 22, 2000 at 07:35:39PM -0400, John W. De Boskey wrote: - David O'Brien's Original Message - On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. I saw this the other day... I've been examining the mfs code, and I'm not really sure why it needs to use random values... When ldconfig hangs, it is in a mkstemp() call. The mkstemp() function probably uses random numbers to generate unique file names: #0 0x8054340 in read () #1 0x804c966 in mktemp () #2 0x804ca33 in arc4random_stir () #3 0x804cad9 in arc4random () #4 0x804c791 in mktemp () #5 0x804c692 in mkstemp () #6 0x804886a in write_elf_hints () #7 0x8048818 in update_elf_hints () #8 0x8048c61 in main () #9 0x8048139 in _start () -brian -- Brian O'Shea [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
jwd 5. At this time, remove ALL MFS filesystems from /etc/fstab. jwdThey can be hand mounted after bootup or via a local rc jwdstartup script. Is there any chance to mount MFS filesystem listed in /etc/fstab just after the /dev/random reseeding is done ? I cannot put up with that we cannot put 'mfs' line to /etc/fstab forever. Moreover, /tmp (common MFS candidate) is already used by X server after rebooting; you may not want to mount /tmp at hand later. Or, it's only for upgrading procedure, and we can put 'mfs' lines back? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
- Makoto MATSUSHITA's Original Message - jwd 5. At this time, remove ALL MFS filesystems from /etc/fstab. jwdThey can be hand mounted after bootup or via a local rc jwdstartup script. Is there any chance to mount MFS filesystem listed in /etc/fstab just after the /dev/random reseeding is done ? I cannot put up with that we cannot put 'mfs' line to /etc/fstab forever. Moreover, /tmp (common MFS candidate) is already used by X server after rebooting; you may not want to mount /tmp at hand later. Or, it's only for upgrading procedure, and we can put 'mfs' lines back? #5 above represents a bug in the current code. It needs to be fixed, but I don't know what the 'correct' thing to do is just yet. Does the FSIRAND code in mfs require crypto strength randomness? -John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
On Sun, 22 Oct 2000, Donny Lee wrote: Hi there, I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. When boot, all go fine at the beginning, and stop right after showing the msg: : : /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks, 0.1%fragmentation) then no more, I got to power off and on, and reboot using an old working kernel. metoo My hangs at loading ldconf. I can continue with ^C. It then hangs at loading aout-ldconf. I can continue with ^C It hangs a 3. time, where I again can continue with ^C. It then complains for missing .so's, naturally because the ldconf was interrupted, and some commands won't work because of that, but the system is at least somewhat working... /metoo I'll see if I can narrow it down somewhat. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
John W. De Boskey noticed me some points to check out, I now can boot my fbsd box with the recent built kernel. I disabled mfs, and random_load, these 2 made my fbsd box hangs (not really hangs, it looks like waiting for some jobs done) 2 times at boot. with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. -- // Donny Leif Neland wrote: When boot, all go fine at the beginning, and stop right after showing the msg: : /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks, 0.1%fragmentation) metoo My hangs at loading ldconf. I can continue with ^C. It then hangs at loading aout-ldconf. I can continue with ^C It hangs a 3. time, where I again can continue with ^C. It then complains for missing .so's, naturally because the ldconf was interrupted, and some commands won't work because of that, but the system is at least somewhat working... /metoo I'll see if I can narrow it down somewhat. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
leifn My hangs at loading ldconf. I can continue with ^C. Are you using MFS ? I suppose you are not. I've found that: - if /etc/fstab has 'mfs' line, system stops during mounting filesystem. Interrupting with CTRL-C works (and system goes to single user mode). - if /etc/fstab does not have 'mfs' line, system stops during ldconfig. Also interruptable. System is working (you can login from console), but something goes wrong (network interface doesn't work). Your case is the latter one, and previous email you have mentioned is the former one. I can reproduce both cases with a -current box cvsuped two days before. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. Solution: Due to changes in the random/entropy stuff, you have to reboot the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". not quite understand this... do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? (Why do we have a separate reboot command? Couldn't it just be an alias for shutdown -r now?) I don't know, it's there. :) try man reboot, it gives me lots. no it's not alias for any other commands. -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
- Leif Neland's Original Message - On Sun, 22 Oct 2000, Donny Lee wrote: Hi there, I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. Solution: Due to changes in the random/entropy stuff, you have to reboot the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". (Why do we have a separate reboot command? Couldn't it just be an alias for shutdown -r now?) See pr 14829 and: http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/rc revision 1.235 for a few additional comments. -John Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
- Original Message - From: "Donny Lee" [EMAIL PROTECTED] To: "Leif Neland" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, October 22, 2000 10:59 AM Subject: Re: -current hangs during boot Leif Neland wrote: I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. Solution: Due to changes in the random/entropy stuff, you have to reboot the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". not quite understand this... do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? Exactly. Except not just after make world/kernel, every time you want to reboot/halt. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? Exactly. Except not just after make world/kernel, every time you want to reboot/halt. Does this make any different? shutdown is fine, but ctrl-alt-del is not so good, whenever I did this, the next boot takes a long time on fixing filesystems. -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? Exactly. Except not just after make world/kernel, every time you want to reboot/halt. Does this make any different? shutdown is fine, but ctrl-alt-del is not so good, whenever I did this, the next boot takes a long time on fixing filesystems. You mean your system doesn't unmount the disks at ctrl-alt-del? Does it a hard reset instead? Strange... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: Does this make any different? shutdown is fine, but ctrl-alt-del is not so good, whenever I did this, the next boot takes a long time on fixing filesystems. You mean your system doesn't unmount the disks at ctrl-alt-del? Does it a hard reset instead? Strange... i might remember wrong, i haven't done so for a long time. Ok, i'm wrong... i'm just back from ctrl-alt-del. :) -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
- David O'Brien's Original Message - On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. I saw this the other day... I've been examining the mfs code, and I'm not really sure why it needs to use random values... Anyone know the history on the '#ifdef FSIRAND' code? -john ps: break out of the boot sequence, 'ls -al /etc/ /dev/random' and then 'exit' will get around this and other problems, but requires hands on reboots. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Anyone know the history on the '#ifdef FSIRAND' code? Randomized file generation numbers to make NFS attacks more difficult, as far as I can remember. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current hangs during boot
Hi there, I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. When boot, all go fine at the beginning, and stop right after showing the msg: : : /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks, 0.1%fragmentation) then no more, I got to power off and on, and reboot using an old working kernel. any idea? -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0-CURRENT hangs in ex_isa_identify() (was: current hangs during boot if ET/5025-16 card is installed)
On Mar 2, 4:09am, Don Lewis wrote: } Subject: current hangs during boot if ET/5025-16 card is installed } } I happened to try to install 4.0-CURRENT on a box that has an } Emerging Technologies ET/5025-16 ISA card installed and found that } the kernel wedges during boot. It hangs hard and won't respond to } anything except the reset switch. The motherboard is an Asus P3B-F } and I believe I have the BIOS propery configured with the correct } settings to match the IRQ and memory addresses used by the ET card. } } I also discovered that older versions of -CURRENT will boot correctly } on this box. I did a binary search on the -CURRENT snapshots and found } that the floppies from the January 12th and earlier snapshots boot, } while the floppies from the January 14th and later snapshots hang. By adding a whole bunch of printf statements to the code, I was able to track this problem to ex_isa_identify(). The ET card is jumpered to I/O address 0x240, and it appears to consume 32 bytes starting at this address. When the ioport loop in ex_isa_identify() gets to 0x250, look_for_card() appears to wedge. I don't see how that can happen unless the CPU gets stuck in inb(). I haven't looked at ISA hardware in ages, can an ISA I/O read really hang forever? What really sucks is that there is no way to disable the ex driver at boot time, so the standard install floppies can no longer be used to boot a box that contains one of these ET cards. Should the ex driver be doing all this stuff at identify time, or was the older method of doing this at probe time more correct? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs during boot if ET/5025-16 card is installed)
On Mar 3, 11:16am, "Matthew N. Dodd" wrote: } Subject: Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs du } On Fri, 3 Mar 2000, Don Lewis wrote: } What really sucks is that there is no way to disable the ex driver } at boot time, so the standard install floppies can no longer be used } to boot a box that contains one of these ET cards. } } Should the ex driver be doing all this stuff at identify time, or was } the older method of doing this at probe time more correct? } } Thats really the only place for such a routine. What needs to happen is } for if_ex to a little more selective about which addresses it } probes. While it is using a non-destructive probe (see } look_for_card()) it should also use the resource manager to check and see } if a port is assigned before it does anything else. Unfortunately the GENERIC kernel doesn't have a driver that could claim the ET card. Also ex_isa_identify() is called before the legacy ISA probes are done. IMHO, the best way to fix this would be for the dual-mode PnP/legacy drivers to identify any cards in PnP mode, then do legacy ISA probes using the old hard-wired port numbers, where legacy ISA probes can be controlled by userconfig. This is really ugly, but then we all agree that ISA sucks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current hangs during boot if ET/5025-16 card is installed
I happened to try to install 4.0-CURRENT on a box that has an Emerging Technologies ET/5025-16 ISA card installed and found that the kernel wedges during boot. It hangs hard and won't respond to anything except the reset switch. The motherboard is an Asus P3B-F and I believe I have the BIOS propery configured with the correct settings to match the IRQ and memory addresses used by the ET card. I also discovered that older versions of -CURRENT will boot correctly on this box. I did a binary search on the -CURRENT snapshots and found that the floppies from the January 12th and earlier snapshots boot, while the floppies from the January 14th and later snapshots hang. Here's the dmesg.boot file that I get by doing a "boot -v" with using late January kernel with the offending card removed. With the card installed, the boot process gets as far as Trying Read_Port at 3c3 but doesn't get to isa_probe_children: disabling PnP devices drtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base d800, size 4 found- vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=255 map[20]: type 1, range 32, base d400, size 5 found- vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[90]: type 1, range 32, base e800, size 4 found- vendor=0x8086, dev=0x1229, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base e180, size 12 map[14]: type 1, range 32, base d000, size 6 map[18]: type 1, range 32, base e100, size 20 found- vendor=0x8086, dev=0x1229, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base e080, size 12 map[14]: type 1, range 32, base b800, size 6 map[18]: type 1, range 32, base e000, size 20 found- vendor=0x8086, dev=0x1229, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base df80, size 12 map[14]: type 1, range 32, base b400, size 6 map[18]: type 1, range 32, base df00, size 20 found- vendor=0x8086, dev=0x1229, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base de80, size 12 map[14]: type 1, range 32, base b000, size 6 map[18]: type 1, range 32, base de00, size 20 pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 found- vendor=0x104c, dev=0x3d07, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e300, size 17 map[14]: type 1, range 32, base e280, size 23 map[18]: type 1, range 32, base e200, size 23 pci1: PCI bus on pcib1 vga-pci0: VGA-compatible display device mem 0xe200-0xe27f,0xe280-0xe2ff,0xe300-0xe301 irq 11 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 ATA-33 controller port 0xd800-0xd80f at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd800 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x9 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd808 ata1: mask=00 status0=ff status1=ff pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 4.2 chip1: Intel 82371AB Power management controller port 0xe800-0xe80f at device 4.3 on pci0 fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xd000-0xd03f mem 0xe100-0xe10f,0xe180-0xe1800fff irq 9 at device 9.0 on pci0 fxp0: Ethernet address 00:90:27:c6:bb:b8 bpf: fxp0 attached fxp1: Intel EtherExpress Pro 10/100B Ethernet port 0xb800-0xb83f mem 0xe000-0xe00f,0xe080-0xe0800fff irq 15 at device 10.0 on pci0 fxp1: Ethernet address 00:90:27:c6:bc:b9 bpf: fxp1 attached fxp2: Intel EtherExpress Pro 10/100B Ethernet port 0xb400-0xb43f mem 0xdf00-0xdf0f,0xdf80-0xdf800fff irq 10 at device 11.0 on pci0 fxp2: Ethernet address 00:90:27:c6:bc:c0 bpf: fxp2 attached fxp3: Intel EtherExpress Pro 10/100B Ethernet port 0xb000-0xb03f mem 0xde00-0xde0f,0xde80-0xde800fff irq 11 at device 12.0 on pci0 fxp3: Ethernet address 00:90:27:c6:a6:12 bpf: fxp3 attached Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3
