Deng XueFeng wrote: >> Updated my RELENG_5 machines today and one of them did not survive the >> reboot. When the loader tries to load the kernel, the machine instantly >> reboots. I thought it might be due to using CPUTYPE?=athlon-xp in >> /etc/make.conf, but it still happens on a kernel compiled with CPUTYPE >> commented out. I also tried versions of the loader compiled with and >> without CPUTYPE; both loaders were able to successfully load a kernel >> from 3 days ago but neither of them succeeded with various kernels >> compiled today. >> > same thing with me. > when update my src today, then do make world. make kernel. > after reboot. the loader will instantly reboot (with a flash info seems > loading kernel) > > then i try the old loader. loader worked, and the new kernel can load. > but after i type "boot" > system hang. only show "/". > I MUST TO manually power it. > > PS: MY box is HP NX7000 LAPTOP. By any chance are you defining CPUTYPE? I've narrowed down my problem to building the loader (as part of world) with CPUTYPE?=athlon-xp. I figured this out by grabbing the 5.3-RC1 mini-iso and doing a binary upgrade to clean up the system. I then did a full buildworld + kernel (my custom config) + installworld without CPUTYPE defined. Everything worked great. I then defined CPUTYPE and rebuilt only the kernel. Again, everything fine. Finally, I did a full buildworld + kernel + installworld with CPUTYPE defined and suddenly I got instant reboots... HOWEVER, restoring *just* the old loader got rid of the reboots and everything worked great again. I'm not sure if it's just the loader that can't be compiled with CPUTYPE or if gcc is actually being corrupted when it is compiled with CPUTYPE. I just did another binary upgrade to clean up the system and I'm in the middle of a full buildworld + kernel + installworld without CPUTYPE defined. My next step is to build just the loader with CPUTYPE defined (but with a gcc binary that was compiled without defining CPUTYPE). Hopefully that will clarify things... Jon >> This machine has an Asus A7N266 motherboard and an Athlon XP 1800 >> processor. For a while now it has needed ACPI disabled as it will >> instantly reboot with ACPI enabled. I was using the latest BIOS (1004) >> but updated the latest beta (1005.005) after this started happening. >> The beta doesn't appear to change anything that I can tell. >> >> The machine also recently developed the annoying habit of not coming >> back up after a reboot. I have to go power cycle it or press reset. >> This is similar to behavior I've seen on motherboards with dying >> capacitors, but the difference here is that it *always* succeeds when I >> manually power it up/reset it. Machines with dying capacitors would >> sometimes fail at that time too. >> >> Jon >> >> $ dmesg >> Copyright (c) 1992-2004 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.3-BETA7 #4: Tue Oct 12 14:36:37 CDT 2004 >> root_at_proxy.concordiacrusaders.org:/usr/obj/usr/src/sys/PROXY >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> CPU: AMD Athlon(TM) XP 1800+ (1536.83-MHz 686-class CPU) >> Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 >> >> Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> >> AMD Features=0xc0400000<AMIE,DSP,3DNow!> >> real memory = 1065271296 (1015 MB) >> avail memory = 1036959744 (988 MB) >> npx0: [FAST] >> npx0: <math processor> on motherboard >> npx0: INT 16 interface >> pcib0: <Host to PCI bridge> pcibus 0 on motherboard >> pir0: <PCI Interrupt Routing Table: 14 Entries> on motherboard >> pci0: <PCI bus> on pcib0 >> $PIR: No matching entry for 0.1.INTA >> agp0: <NVIDIA nForce AGP Controller> mem 0xf8000000-0xfbffffff at device >> 0.0 on pci0 >> pci0: <memory, RAM> at device 0.1 (no driver attached) >> pci0: <memory, RAM> at device 0.2 (no driver attached) >> pci0: <memory, RAM> at device 0.3 (no driver attached) >> isab0: <PCI-ISA bridge> at device 1.0 on pci0 >> isa0: <ISA bus> on isab0 >> pci0: <serial bus, SMBus> at device 1.1 (no driver attached) >> pcib1: <PCIBIOS PCI-PCI bridge> at device 8.0 on pci0 >> pci1: <PCI bus> on pcib1 >> $PIR: No matching entry for 1.10.INTA >> ahc0: <Adaptec 29160N Ultra160 SCSI adapter> port 0xc800-0xc8ff mem >> 0xe5000000-0xe5000fff irq 7 at device 8.0 on pci1 >> ahc0: [GIANT-LOCKED] >> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs >> fxp0: <Intel 82550 Pro/100 Ethernet> port 0xc400-0xc43f mem >> 0xe4000000-0xe401ffff,0xe4800000-0xe4800fff irq 5 at device 10.0 on pci1 >> miibus0: <MII bus> on fxp0 >> inphy0: <i82555 10/100 media interface> on miibus0 >> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> fxp0: Ethernet address: 00:02:b3:28:44:a0 >> atapci0: <nVidia nForce UDMA100 controller> port >> 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0 >> ata0: channel #0 on atapci0 >> ata1: channel #1 on atapci0 >> pcib2: <PCIBIOS PCI-PCI bridge> at device 30.0 on pci0 >> pci2: <PCI bus> on pcib2 >> pci2: <display, VGA> at device 0.0 (no driver attached) >> cpu0 on motherboard >> orm0: <ISA Option ROM> at iomem 0xd8000-0xd97ff on isa0 >> pmtimer0 on isa0 >> atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0 >> atkbd0: <AT Keyboard> irq 1 on atkbdc0 >> kbd0 at atkbd0 >> atkbd0: [GIANT-LOCKED] >> psm0: <PS/2 Mouse> irq 12 on atkbdc0 >> psm0: [GIANT-LOCKED] >> psm0: model IntelliMouse, device ID 3 >> fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5 irq 6 drq 2 on >> isa0 >> fdc0: [FAST] >> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >> sc0: <System console> at flags 0x100 on isa0 >> sc0: VGA <16 virtual consoles, flags=0x300> >> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >> sio0: type 16550A >> sio1: configured irq 3 not in bitmap of probed irqs 0 >> sio1: port may not be enabled >> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on >> isa0 >> unknown: <PNP0501> can't assign resources (port) >> unknown: <PNP0700> can't assign resources (port) >> unknown: <PNP0f13> can't assign resources (irq) >> ahc1: No resources allocated. >> ahc1: No resources allocated. >> unknown: <PNP0303> can't assign resources (port) >> unknown: <PNP0c02> can't assign resources (port) >> Timecounter "TSC" frequency 1536825688 Hz quality 800 >> Timecounters tick every 1.000 msec >> ad0: 78533MB <IC35L080AVVA07-0/VA4OA50K> [159560/16/63] at ata0-master >> UDMA100 >> acd0: DVDROM <LITEON DVD-ROM LTD163D/GHR3> at ata1-master UDMA33 >> Waiting 15 seconds for SCSI devices to settle >> da0 at ahc0 bus 0 target 0 lun 0 >> da0: <QUANTUM ATLAS V 9 SCA 0201> Fixed Direct Access SCSI-3 device >> da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged >> Queueing Enabled >> da0: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) >> da1 at ahc0 bus 0 target 1 lun 0 >> da1: <QUANTUM ATLAS V 9 SCA 0201> Fixed Direct Access SCSI-3 device >> da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged >> Queueing Enabled >> da1: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) >> Mounting root from ufs:/dev/ad0s1a >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe_at_freebsd.org" > > -- > Deng XueFeng <dsnofe_at_yahoo.com.cn>Received on Sun Oct 31 2004 - 11:11:14 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:20 UTC