Re: loader from Nov 13 reboots instantly

2001-11-14 Thread David O'Brien

On Wed, Nov 14, 2001 at 07:09:18AM -0200, Daniel C. Sobral wrote:
> > This probably needs to be changed so that awk is a buildtool, and one
> > is built early to use when building the loader.

It doesn't need to be a build tool... unless you want to make 'ls' a
build tool also.  We had one bump in the road.  That is all.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: loader from Nov 13 reboots instantly

2001-11-14 Thread Daniel C. Sobral

Robert Watson wrote:
> 
> It's probably the awk bug.  You need to use /boot/loader.old to boot the
> system, build and install a fresh awk (gnu awk), then build and install a
> fresh loader.
> 
> You don't get bitten by this until the second upgrade after the bad awk
> version was introduced, since the awk used to build the loader is the
> system's native awk, not the awk in the build tree.  This probably needs
> to be changed so that awk is a buildtool, and one is built early to use
> when building the loader.

Is Perl a build tool? Awk was originally introduced when compiling FICL
so that boot wouldn't depend on that Evil Thing (Perl). But standard
FICL distribution uses a perl script instead of a awk one. OTOH, our awk
script removes more white space than the perl one, but that can easily
be corrected.

-- 
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

wow regex humor... I'm a geek

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: loader from Nov 13 reboots instantly

2001-11-13 Thread Robert Watson

It's probably the awk bug.  You need to use /boot/loader.old to boot the
system, build and install a fresh awk (gnu awk), then build and install a
fresh loader.

You don't get bitten by this until the second upgrade after the bad awk
version was introduced, since the awk used to build the loader is the
system's native awk, not the awk in the build tree.  This probably needs
to be changed so that awk is a buildtool, and one is built early to use
when building the loader.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services

On Tue, 13 Nov 2001 [EMAIL PROTECTED] wrote:

> I just rebuild my -current system. 
> 
> On executing /boot/loader the system rebooted instantly I have no
> idea what kind of debugging infos I might send, so I send the dmesg as a
> first idea (booted with loader.old). The system never gave me any
> troubles, I'm recompiling -current about once every two weeks and never
> ran into problems.
> 
> loader/main.c identifies as:  
> src/sys/boot/i386/loader/main.c,v 1.25 2001/11/05 19:03:01 jhb Exp
> 
> 
> 
> 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 #21: Tue Nov 13 17:51:39 CET 2001
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MP
> Preloaded elf kernel "/boot/kernel/kernel" at 0xc043.
> Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04300a8.
> Timecounter "i8254"  frequency 1193182 Hz
> Timecounter "TSC"  frequency 350797159 Hz
> CPU: Pentium II/Pentium II Xeon/Celeron (350.80-MHz 686-class CPU)
>   Origin = "GenuineIntel"  Id = 0x652  Stepping = 2
>   Features=0x183f9ff T,PSE36,MMX,FXSR>
> real memory  = 268423168 (262132K bytes)
> avail memory = 256774144 (250756K bytes)
> Pentium Pro MTRR support enabled
> Using $PIR table, 8 entries at 0xc00f0d10
> npx0:  on motherboard
> npx0: INT 16 interface
> acpi0:  on motherboard
> acpi0: power button is handled as a fixed feature programming model.
> Timecounter "ACPI"  frequency 3579545 Hz
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
> acpi_cpu0:  on acpi0
> acpi_button0:  on acpi0
> acpi_pcib0:  port 0xcf8-0xcff on acpi0
> pci0:  on acpi_pcib0
> agp0:  mem 0xe400-0xe7ff at d
> evice 0.0 on pci0
> pcib1:  at device 1.0 on pci0
> pci1:  on pcib1
> pci1:  at device 0.0 (no driver attached)
> isab0:  at device 4.0 on pci0
> isa0:  on isab0
> atapci0:  port 0xb800-0xb80f at device 4.1 on pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> pci0:  at device 4.2 (no driver attached)
> intpm0:  port 0xe800-0xe80f irq 9 at 
> device 4.3 on pci0
> intpm0: I/O mapped e800
> intpm0: intr IRQ 9 enabled revision 0
> smbus0:  on intsmb0
> smb0:  on smbus0
> intpm0: PM I/O mapped e400 
> fxp0:  port 0xb000-0xb01f mem 0xdc00-0xdc0f
> ,0xdf00-0xdf000fff irq 5 at device 7.0 on pci0
> fxp0: Ethernet address 00:e0:18:90:02:74
> inphy0:  on miibus0
> inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> pcm0:  port 0xa800-0xa83f irq 5 at device 10.0 on pci0
> bktr0:  mem 0xde00-0xde000fff irq 10 at device 11.0 on pci0
> bti2c0: 
> iicbb0:  on bti2c0
> iicbus0:  on iicbb0 master-only
> iicsmb0:  on iicbus0
> smbus1:  on iicsmb0
> smb1:  on smbus1
> smbus2:  on bti2c0
> smb2:  on smbus2
> bktr0: Hauppauge Model 61324 D129
> bktr0: Detected a MSP3410D-B4 at 0x80
> bktr0: Hauppauge WinCast/TV, Philips PAL I tuner, msp3400c stereo, remote contro
> l.
> pci0:  at device 11.1 (no driver attached)
> fdc0:  port 0x3f7,0x3f2-0x3f5 irq 6 on acpi0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> ppc0 port 0x378-0x37f irq 7 on acpi0
> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
> plip0:  on ppbus0
> lpt0:  on ppbus0
> lpt0: Interrupt-driven port
> ppi0:  on ppbus0
> sio0 port 0x3f8-0x3ff irq 4 on acpi0
> sio0: type 16550A
> sio1 port 0x2f8-0x2ff irq 3 on acpi0
> sio1: type 16550A
> atkbdc0:  port 0x64,0x60 irq 1 on acpi0
> atkbd0:  flags 0x1 irq 1 on atkbdc0
> kbd0 at atkbd0
> psm0:  irq 12 on atkbdc0
> psm0: model MouseMan+, device ID 0
> ata-: ata0 already exists, skipping it
> ata-: ata1 already exists, skipping it
> atkbdc-: atkbdc0 already exists, skipping it
> fdc-: fdc0 already exists, skipping it
> ppc-: ppc0 already exists, skipping it
> sio-: sio0 already exists, skipping it
> sio-: sio1 already exists, skipping it
> sc-: sc0 already exists, skipping it
> vga-: vga0 already exists, skipping it
> orm0:  at iomem 0xc-0xc7fff on isa0
> pmtimer0 on isa0
> sc0:  at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> ad0: 9671MB  [19650/16/63] at ata0-master UDMA33
> acd0: CDROM  at ata1-master PIO4
> Mounting root from ufs:/dev/ad0s1a
> fxp0: promiscuous mode enabled
> got bad cookie vp 0xd37bf300 bp 0xc77bfa34
> 
> 
> Cheers, Mathias
> -- 
> 

RE: loader from Nov 13 reboots instantly

2001-11-13 Thread John Baldwin


On 13-Nov-01 [EMAIL PROTECTED] wrote:
> I just rebuild my -current system. 
> 
> On executing /boot/loader the system rebooted instantly I have no
> idea what kind of debugging infos I might send, so I send the dmesg as a
> first idea (booted with loader.old). The system never gave me any
> troubles, I'm recompiling -current about once every two weeks and never
> ran into problems.

Please read the list, this was already discussed.  It was apparently due to the
awk breakage.  Rebuild the loader again and it should work fine.

Make sure you don't overwrite loader.old however when you install the new
loader just in case. :)  Probably should do a 'make clean' in /sys/boot before
rebuilding the loader as well.

-- 

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