Re: today's current: boot/loader and console
Are your loader and 4th files in sync? There was a change to the 4th scripts that I thought I sent a heads up about. Anyways, do this to get the error message: go into /sys/boot/i386/loader, edit main.c, and change the exit() function to do a while(1); loop before callign __exit(). Compile a new loader and install it and then see what message you get. Well, interestingly enough, the problem disappeared after I simply did make make install in /sys/boot/i386/ ... All I did before was the usual buildworld, installworld, buidlkernel, installkernel, mergemaster, reboot. Yours, -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: today's current: boot/loader and console
This works, but there is no console output (it goes from spinner straight into the login prompt). I guess, the console output is being sent down sio0, where there is an external modem now. Turning the modem off does not change anything... What's in your /boot/device.hints ? A couple of weeks ago I trimmed too much out of it, removed ' hint.sc.0.at=isa ' ' hint.sc.0.flags=0x100 ' and then lost all of my console output, just exactly like you have, from spinner to login prompt. Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices [snip] isa_probe_children: probing PnP devices [ many more errors failures below ] What's all this - any clues here? Disables, then probes again? There's a lot of errors and failures in your dmesg below. I'm not guru enough to know them all, but see if any of them is familiar. Dave -- On Thu, 3 Jan 2002, Mikhail Teterin wrote: After 25 days of uptime I rebuilt the world, and can no longer boot as usual. Both boot/loader and boot/loader.old (from Oct 30) flash the list of devices and immediately reset the computer. My only way to bring it up is to press space at the right moment, get the Boot: prompt and load/boot kernel directly bypassing the loader. Dmesg output follows (note, that the ``calcru: negative time...'' messages are still here!). What have I done to deserve this? ad4: success setting UDMA4 on Promise chip Creating DISK ad4 Promise check1 failed ad4: QUANTUM FIREBALLP LM30.0/A35.0700 ATA-5 disk at ata2-master ad4: 28629MB (58633344 sectors), 58168 C, 16 H, 63 S, 512 B ad4: 16 secs/int, 1 depth queue, UDMA66 ad4: piomode=4 dmamode=2 udmamode=4 cblid=1 ad6: success setting UDMA4 on Promise chip Creating DISK ad6 Promise check1 failed ad6: QUANTUM FIREBALLP LM30.0/A35.0700 ATA-5 disk at ata3-master ad6: 28629MB (58633344 sectors), 58168 C, 16 H, 63 S, 512 B ad6: 16 secs/int, 1 depth queue, UDMA66 ad6: piomode=4 dmamode=2 udmamode=4 cblid=1 ata1-master: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 ata1-master: success setting PIO3 on generic chip acd0: NEC CD-ROM DRIVE:282/3.05 CDROM drive at ata1 as master acd0: read 1376KB/s (32504KB/s), 128KB buffer, PIO3 acd0: Reads: CD-DA acd0: Writes: acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: CD-ROM unknown Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. (probe0:sym0:0:0:0): Retrying Command (probe17:sym1:0:2:0): error 22 (probe17:sym1:0:2:0): Unretryable Error Creating DISK cd0 Creating DISK da0 pass0 at sym0 bus 0 target 0 lun 0 pass0: SEAGATE ST34371W 0440 Fixed Direct Access SCSI-2 device pass0: Serial Number JDR614250M11T1 pass0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled pass1 at sym1 bus 0 target 2 lun 0 pass1: NEC CD-ROM DRIVE:500 2.5 Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers Mounting root from ufs:da0a da0 at sym0 bus 0 target 0 lun 0 da0: SEAGATE ST34371W 0440 Fixed Direct Access SCSI-2 device da0: Serial Number JDR614250M11T1 da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4148MB (8496884 512 byte sectors: 255H 63S/T 528C) (cd0:sym1:0:2:0): error 6 (cd0:sym1:0:2:0): Unretryable Error cd0 at sym1 bus 0 target 2 lun 0 cd0: NEC CD-ROM DRIVE:500 2.5 Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0s1: type 0xa5, start 0, end = 8496883, size 8496884 da0s1: C/H/S end 528/231/11 (1350007) != end 8496883: invalid SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff SMP: AP CPU #1 Launched! start_init: trying /sbin/init microuptime() went backwards (10.3931180 - 9.512351) ad6: invalid primary partition table: no magic ad4: invalid primary partition table: no magic WARNING: /ccd was not properly dismounted bpf: tun0 attached md0: Malloc disk Creating DISK md0 md0: invalid primary partition table: no magic md0: invalid primary partition table: no magic md0: invalid primary partition table: no magic md0: invalid primary partition table: no magic fxp0: promiscuous mode enabled (da0:sym0:0:0:0): tagged openings now 63 (da0:sym0:0:0:0): Retrying Command calcru: negative time of 392153083 usec for pid 370 (setiathome) 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: today's current: boot/loader and console
On 3 Jan, John Baldwin wrote: On 04-Jan-02 Mikhail Teterin wrote: After 25 days of uptime I rebuilt the world, and can no longer boot as usual. Both boot/loader and boot/loader.old (from Oct 30) flash the list of devices and immediately reset the computer. Any chance you could setup a serial console and catch the output? This is my only computer... My only way to bring it up is to press space at the right moment, get the Boot: prompt and load/boot kernel directly bypassing the loader. This works, but there is no console output (it goes from spinner straight into the login prompt). I guess, the console output is being sent down sio0, where there is an external modem now. Turning the modem off does not change anything... No, you have no console because you have no hints. If you statically compile your hints into your kernel, you will have a console again. Why did it change all of a sudden? Did hints get blown away by installworld at's the point? Why is the serial console default? Thanks! -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: today's current: boot/loader and console
On 04-Jan-02 Mikhail Teterin wrote: On 3 Jan, John Baldwin wrote: On 04-Jan-02 Mikhail Teterin wrote: After 25 days of uptime I rebuilt the world, and can no longer boot as usual. Both boot/loader and boot/loader.old (from Oct 30) flash the list of devices and immediately reset the computer. Any chance you could setup a serial console and catch the output? This is my only computer... Are your loader and 4th files in sync? There was a change to the 4th scripts that I thought I sent a heads up about. Anyways, do this to get the error message: go into /sys/boot/i386/loader, edit main.c, and change the exit() function to do a while(1); loop before callign __exit(). Compile a new loader and install it and then see what message you get. My only way to bring it up is to press space at the right moment, get the Boot: prompt and load/boot kernel directly bypassing the loader. This works, but there is no console output (it goes from spinner straight into the login prompt). I guess, the console output is being sent down sio0, where there is an external modem now. Turning the modem off does not change anything... No, you have no console because you have no hints. If you statically compile your hints into your kernel, you will have a console again. Why did it change all of a sudden? Did hints get blown away by installworld at's the point? Why is the serial console default? Err, hints are normally loaded by the loader from /boot/device.hints. boot2 doesn't load hints when it loads a kenrel, it just loads the kernel and boots. You don't have a seiral console, you have _no_ kernel console. :) Since you are booting from boot2 and not the loader, your hints aren't getting loaded, so you aren't getting a kernel console. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: today's current: boot/loader and console
Are your loader and 4th files in sync? There was a change to the 4th scripts that I thought I sent a heads up about. The hints did not change since forever: -r--r--r-- 1 root wheel2030 Feb 10 2001 device.hints Everything else seems fresh: -r--r--r-- 1 root wheel7721 Jan 3 20:34 loader.4th -r--r--r-- 1 root wheel 35097 Jan 3 20:34 support.4th -r-xr-xr-x 1 root wheel 174080 Jan 3 20:34 pxeboot -r-xr-xr-x 1 root wheel 176128 Jan 3 20:34 liloboot drwxr-xr-x 2 root wheel 512 Jan 3 20:34 defaults -r-xr-xr-x 1 root wheel 172032 Jan 3 20:34 loader Anyways, do thisto get the errormessage: go into /sys/boot/i386/loader, edit main.c, and change the exit() function to do a while(1); loop before callign __exit(). Compile a new loader and install it and then see what message you get. Mmm, Ok... Next time I reboot, I'll post the results... Thanks! You don't have a seiral console, you have _no_ kernel console. :) Since you are booting from boot2 and not the loader, your hints aren't getting loaded, so you aren't getting a kernel console. There was time, when direct booting of the kernel was working... -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: today's current: boot/loader and console
On 04-Jan-02 Mikhail Teterin wrote: Are your loader and 4th files in sync? There was a change to the 4th scripts that I thought I sent a heads up about. The hints did not change since forever: -r--r--r-- 1 root wheel2030 Feb 10 2001 device.hints Everything else seems fresh: -r--r--r-- 1 root wheel7721 Jan 3 20:34 loader.4th -r--r--r-- 1 root wheel 35097 Jan 3 20:34 support.4th -r-xr-xr-x 1 root wheel 174080 Jan 3 20:34 pxeboot -r-xr-xr-x 1 root wheel 176128 Jan 3 20:34 liloboot drwxr-xr-x 2 root wheel 512 Jan 3 20:34 defaults -r-xr-xr-x 1 root wheel 172032 Jan 3 20:34 loader Anyways, do thisto get the errormessage: go into /sys/boot/i386/loader, edit main.c, and change the exit() function to do a while(1); loop before callign __exit(). Compile a new loader and install it and then see what message you get. Mmm, Ok... Next time I reboot, I'll post the results... Thanks! You don't have a seiral console, you have _no_ kernel console. :) Since you are booting from boot2 and not the loader, your hints aren't getting loaded, so you aren't getting a kernel console. There was time, when direct booting of the kernel was working... Hints used to be statically compiled in by default sort of but on longer are. They haven't been for quite some time. Direct booting works great if you compiler your hints using hints foo.hints in your kernel config file. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: today's current: boot/loader and console
On 04-Jan-02 Mikhail Teterin wrote: After 25 days of uptime I rebuilt the world, and can no longer boot as usual. Both boot/loader and boot/loader.old (from Oct 30) flash the list of devices and immediately reset the computer. Any chance you could setup a serial console and catch the output? My only way to bring it up is to press space at the right moment, get the Boot: prompt and load/boot kernel directly bypassing the loader. This works, but there is no console output (it goes from spinner straight into the login prompt). I guess, the console output is being sent down sio0, where there is an external modem now. Turning the modem off does not change anything... No, you have no console because you have no hints. If you statically compile your hints into your kernel, you will have a console again. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
