| View previous topic :: View next topic |
| Author |
Message |
chiwi
Tux's lil' helper
Joined: 25 Apr 2004
Posts: 135
Location: Buenos Aires, Argentina
|
 Posted: Sun Oct 08, 2006 5:43 am Post subject: pc suddenly reboots |
 |
|
Hi there, i have a really annoying problem. I've just installed gentoo on an old pc tu use as a file server at home. After i installed everything, booted into the brand new gentoo, it started to reboot itself with no reason at all, from one moment to another, bam! blank screen with the bios version showing on the screen. No error msg, no logging, nothing. I'm just clueless about what is happening.
At first I thought it was a hardware problem with one of the components. But i tested each independently and they don't seem to have any problems, in fact, i booted with the gentoo live-cd, mounted the installed partitions, chrooted and it's been running fine for about 2 hours (too much), So I think it's gotta be something with my gentoo installation, may be the kernel, or some other thing, but the question is..what? there are so many places to look at, that i don't know where to start. that's why i come to you guys, Is there anything you could point me, I'd be *very* appreciated.
The pc is a soyo SY-VBA133 mobo with a P3 933mhz. 128 MB pc100/133, a cd-rw , a 80GB samsung HD and a 250W atx power
my dmesg messages are these:
| Code: |
Oct 7 23:44:18 PaqueServer syslog-ng[3354]: syslog-ng version 1.6.9 starting
Oct 7 23:44:18 PaqueServer syslog-ng[3354]: Changing permissions on special file /dev/tty12
Oct 7 23:44:18 PaqueServer Linux version 2.6.17-gentoo-r8PaqueServer (root@livecd) (gcc version 4.1.1 (Gentoo 4.1.1)) #1 Fri Oct 6 10:16:03 ART 2006
Oct 7 23:44:18 PaqueServer BIOS-provided physical RAM map:
Oct 7 23:44:18 PaqueServer BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
Oct 7 23:44:18 PaqueServer BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Oct 7 23:44:18 PaqueServer BIOS-e820: 0000000000100000 - 0000000007ff0000 (usable)
Oct 7 23:44:18 PaqueServer BIOS-e820: 0000000007ff0000 - 0000000007ff3000 (ACPI NVS)
Oct 7 23:44:18 PaqueServer BIOS-e820: 0000000007ff3000 - 0000000008000000 (ACPI data)
Oct 7 23:44:18 PaqueServer BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Oct 7 23:44:18 PaqueServer 127MB LOWMEM available.
Oct 7 23:44:18 PaqueServer On node 0 totalpages: 32752
Oct 7 23:44:18 PaqueServer DMA zone: 4096 pages, LIFO batch:0
Oct 7 23:44:18 PaqueServer Normal zone: 28656 pages, LIFO batch:7
Oct 7 23:44:18 PaqueServer DMI 2.2 present.
Oct 7 23:44:18 PaqueServer ACPI: RSDP (v000 SOYO ) @ 0x000f80f0
Oct 7 23:44:18 PaqueServer ACPI: RSDT (v001 SOYO AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x07ff3000
Oct 7 23:44:18 PaqueServer ACPI: FADT (v001 SOYO AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x07ff3040
Oct 7 23:44:18 PaqueServer ACPI: DSDT (v001 SOYO AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
Oct 7 23:44:18 PaqueServer ACPI: PM-Timer IO Port: 0x4008
Oct 7 23:44:18 PaqueServer Allocating PCI resources starting at 10000000 (gap: 08000000:f7ff0000)
Oct 7 23:44:18 PaqueServer Built 1 zonelists
Oct 7 23:44:18 PaqueServer Kernel command line: root=/dev/hda3
Oct 7 23:44:18 PaqueServer Local APIC disabled by BIOS -- you can enable it with "lapic"
Oct 7 23:44:18 PaqueServer mapped APIC to ffffd000 (01101000)
Oct 7 23:44:18 PaqueServer Enabling fast FPU save and restore... done.
Oct 7 23:44:18 PaqueServer Enabling unmasked SIMD FPU exception support... done.
Oct 7 23:44:18 PaqueServer Initializing CPU#0
Oct 7 23:44:18 PaqueServer PID hash table entries: 512 (order: 9, 2048 bytes)
Oct 7 23:44:18 PaqueServer Detected 931.245 MHz processor.
Oct 7 23:44:18 PaqueServer Using pmtmr for high-res timesource
Oct 7 23:44:18 PaqueServer Console: colour VGA+ 80x25
Oct 7 23:44:18 PaqueServer Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Oct 7 23:44:18 PaqueServer Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Oct 7 23:44:18 PaqueServer Memory: 126796k/131008k available (1748k kernel code, 3752k reserved, 555k data, 144k init, 0k highmem)
Oct 7 23:44:18 PaqueServer Checking if this processor honours the WP bit even in supervisor mode... Ok.
Oct 7 23:44:18 PaqueServer Calibrating delay using timer specific routine.. 1864.23 BogoMIPS (lpj=3728463)
Oct 7 23:44:18 PaqueServer Mount-cache hash table entries: 512
Oct 7 23:44:18 PaqueServer CPU: After generic identify, caps: 0387f9ff 00000000 00000000 00000000 00000000 00000000 00000000
Oct 7 23:44:18 PaqueServer CPU: After vendor identify, caps: 0387f9ff 00000000 00000000 00000000 00000000 00000000 00000000
Oct 7 23:44:18 PaqueServer CPU: L1 I cache: 16K, L1 D cache: 16K
Oct 7 23:44:18 PaqueServer CPU: L2 cache: 256K
Oct 7 23:44:18 PaqueServer CPU serial number disabled.
Oct 7 23:44:18 PaqueServer CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Oct 7 23:44:18 PaqueServer Intel machine check architecture supported.
Oct 7 23:44:18 PaqueServer Intel machine check reporting enabled on CPU#0.
Oct 7 23:44:18 PaqueServer CPU: Intel Pentium III (Coppermine) stepping 0a
Oct 7 23:44:18 PaqueServer Checking 'hlt' instruction... OK.
Oct 7 23:44:18 PaqueServer SMP alternatives: switching to UP code
Oct 7 23:44:18 PaqueServer Freeing SMP alternatives: 0k freed
Oct 7 23:44:18 PaqueServer ACPI: setting ELCR to 0080 (from 1c80)
Oct 7 23:44:18 PaqueServer NET: Registered protocol family 16
Oct 7 23:44:18 PaqueServer ACPI: bus type pci registered
Oct 7 23:44:18 PaqueServer PCI: PCI BIOS revision 2.10 entry at 0xfb410, last bus=1
Oct 7 23:44:18 PaqueServer Setting up standard PCI resources
Oct 7 23:44:18 PaqueServer ACPI: Subsystem revision 20060127
Oct 7 23:44:18 PaqueServer ACPI: Interpreter enabled
Oct 7 23:44:18 PaqueServer ACPI: Using PIC for interrupt routing
Oct 7 23:44:18 PaqueServer ACPI: PCI Root Bridge [PCI0] (0000:00)
Oct 7 23:44:18 PaqueServer PCI: Probing PCI hardware (bus 00)
Oct 7 23:44:18 PaqueServer ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Oct 7 23:44:18 PaqueServer PCI quirk: region 4000-40ff claimed by vt82c586 ACPI
Oct 7 23:44:18 PaqueServer PCI quirk: region 6000-607f claimed by vt82c686 HW-mon
Oct 7 23:44:18 PaqueServer PCI quirk: region 5000-500f claimed by vt82c686 SMB
Oct 7 23:44:18 PaqueServer Boot video device is 0000:01:00.0
Oct 7 23:44:18 PaqueServer ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Oct 7 23:44:18 PaqueServer ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 11 *12 14 15)
Oct 7 23:44:18 PaqueServer ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 7 23:44:18 PaqueServer ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
Oct 7 23:44:18 PaqueServer ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
Oct 7 23:44:18 PaqueServer Linux Plug and Play Support v0.97 (c) Adam Belay
Oct 7 23:44:18 PaqueServer SCSI subsystem initialized
Oct 7 23:44:18 PaqueServer PCI: Using ACPI for IRQ routing
Oct 7 23:44:18 PaqueServer PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Oct 7 23:44:18 PaqueServer PCI: Bridge: 0000:00:01.0
Oct 7 23:44:18 PaqueServer IO window: c000-cfff
Oct 7 23:44:18 PaqueServer MEM window: d0000000-d1ffffff
Oct 7 23:44:18 PaqueServer PREFETCH window: d2800000-d2ffffff
Oct 7 23:44:18 PaqueServer PCI: Setting latency timer of device 0000:00:01.0 to 64
Oct 7 23:44:18 PaqueServer NET: Registered protocol family 2
Oct 7 23:44:18 PaqueServer IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Oct 7 23:44:18 PaqueServer TCP established hash table entries: 4096 (order: 2, 16384 bytes)
Oct 7 23:44:18 PaqueServer TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
Oct 7 23:44:18 PaqueServer TCP: Hash tables configured (established 4096 bind 2048)
Oct 7 23:44:18 PaqueServer TCP reno registered
Oct 7 23:44:18 PaqueServer NTFS driver 2.1.27 [Flags: R/O].
Oct 7 23:44:18 PaqueServer io scheduler noop registered
Oct 7 23:44:18 PaqueServer io scheduler cfq registered (default)
Oct 7 23:44:18 PaqueServer PCI: Disabling Via external APIC routing
Oct 7 23:44:18 PaqueServer Real Time Clock Driver v1.12ac
Oct 7 23:44:18 PaqueServer Linux agpgart interface v0.101 (c) Dave Jones
Oct 7 23:44:18 PaqueServer Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Oct 7 23:44:18 PaqueServer serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Oct 7 23:44:18 PaqueServer serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Oct 7 23:44:18 PaqueServer PNP: No PS/2 controller found. Probing ports directly.
Oct 7 23:44:18 PaqueServer serio: i8042 AUX port at 0x60,0x64 irq 12
Oct 7 23:44:18 PaqueServer serio: i8042 KBD port at 0x60,0x64 irq 1
Oct 7 23:44:18 PaqueServer mice: PS/2 mouse device common for all mice
Oct 7 23:44:18 PaqueServer loop: loaded (max 8 devices)
Oct 7 23:44:18 PaqueServer 8139too Fast Ethernet driver 0.9.27
Oct 7 23:44:18 PaqueServer ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 12
Oct 7 23:44:18 PaqueServer PCI: setting IRQ 12 as level-triggered
Oct 7 23:44:18 PaqueServer ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKA] -> GSI 12 (level, low) -> IRQ 12
Oct 7 23:44:18 PaqueServer eth0: RealTek RTL8139 at 0xc8802000, 00:e0:7d:b5:a3:9d, IRQ 12
Oct 7 23:44:18 PaqueServer eth0: Identified 8139 chip type 'RTL-8139C'
Oct 7 23:44:18 PaqueServer Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Oct 7 23:44:18 PaqueServer ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Oct 7 23:44:18 PaqueServer VP_IDE: IDE controller at PCI slot 0000:00:07.1
Oct 7 23:44:18 PaqueServer PCI: VIA IRQ fixup for 0000:00:07.1, from 255 to 0
Oct 7 23:44:18 PaqueServer VP_IDE: chipset revision 16
Oct 7 23:44:18 PaqueServer VP_IDE: not 100% native mode: will probe irqs later
Oct 7 23:44:18 PaqueServer VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci0000:00:07.1
Oct 7 23:44:18 PaqueServer ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
Oct 7 23:44:18 PaqueServer ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Oct 7 23:44:18 PaqueServer Probing IDE interface ide0...
Oct 7 23:44:18 PaqueServer hda: SAMSUNG SP0842N, ATA DISK drive
Oct 7 23:44:18 PaqueServer ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 7 23:44:18 PaqueServer Probing IDE interface ide1...
Oct 7 23:44:18 PaqueServer hda: max request size: 512KiB
Oct 7 23:44:18 PaqueServer hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(66)
Oct 7 23:44:18 PaqueServer hda: cache flushes supported
Oct 7 23:44:18 PaqueServer hda: hda1 hda2 hda3 hda4
Oct 7 23:44:18 PaqueServer TCP bic registered
Oct 7 23:44:18 PaqueServer NET: Registered protocol family 1
Oct 7 23:44:18 PaqueServer NET: Registered protocol family 17
Oct 7 23:44:18 PaqueServer Using IPI Shortcut mode
Oct 7 23:44:18 PaqueServer EXT3-fs: INFO: recovery required on readonly filesystem.
Oct 7 23:44:18 PaqueServer EXT3-fs: write access will be enabled during recovery.
Oct 7 23:44:18 PaqueServer kjournald starting. Commit interval 5 seconds
Oct 7 23:44:18 PaqueServer EXT3-fs: recovery complete.
Oct 7 23:44:18 PaqueServer EXT3-fs: mounted filesystem with ordered data mode.
Oct 7 23:44:18 PaqueServer VFS: Mounted root (ext3 filesystem) readonly.
Oct 7 23:44:18 PaqueServer Freeing unused kernel memory: 144k freed
Oct 7 23:44:18 PaqueServer EXT3 FS on hda3, internal journal
Oct 7 23:44:18 PaqueServer device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
Oct 7 23:44:18 PaqueServer kjournald starting. Commit interval 5 seconds
Oct 7 23:44:18 PaqueServer EXT3 FS on dm-0, internal journal
Oct 7 23:44:18 PaqueServer EXT3-fs: mounted filesystem with ordered data mode.
Oct 7 23:44:18 PaqueServer kjournald starting. Commit interval 5 seconds
Oct 7 23:44:18 PaqueServer EXT3 FS on dm-1, internal journal
Oct 7 23:44:18 PaqueServer EXT3-fs: mounted filesystem with ordered data mode.
Oct 7 23:44:18 PaqueServer kjournald starting. Commit interval 5 seconds
Oct 7 23:44:18 PaqueServer EXT3 FS on dm-2, internal journal
Oct 7 23:44:18 PaqueServer EXT3-fs: mounted filesystem with ordered data mode.
Oct 7 23:44:18 PaqueServer kjournald starting. Commit interval 5 seconds
Oct 7 23:44:18 PaqueServer EXT3 FS on dm-3, internal journal
Oct 7 23:44:18 PaqueServer EXT3-fs: mounted filesystem with ordered data mode.
Oct 7 23:44:18 PaqueServer kjournald starting. Commit interval 5 seconds
Oct 7 23:44:18 PaqueServer EXT3 FS on dm-4, internal journal
Oct 7 23:44:18 PaqueServer EXT3-fs: mounted filesystem with ordered data mode.
Oct 7 23:44:18 PaqueServer Adding 506036k swap on /dev/hda2. Priority:-1 extents:1 across:506036k
Oct 7 23:44:20 PaqueServer eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Oct 7 23:44:24 PaqueServer sshd[3939]: Server listening on 0.0.0.0 port 22.
Oct 7 23:44:25 PaqueServer cron[4006]: (CRON) STARTUP (V5.0) |
do you see anything strange ? because i don't... :/
please, any help is appreciated.
Thanks. |
|
| Back to top |
|
 |
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Sun Oct 08, 2006 6:14 am Post subject: |
|
|
| Laziness, properly applied, is a virtue. Copy the kernel configuration from the live CD build a kernel based on that, adding any additional device support you want, boot it and post the results. |
|
| Back to top |
|
|
chiwi
Tux's lil' helper
Joined: 25 Apr 2004
Posts: 135
Location: Buenos Aires, Argentina
|
| Posted: Sun Oct 08, 2006 6:17 am Post subject: |
|
|
great idea...will do that.
thankss |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Sun Oct 08, 2006 6:33 am Post subject: |
|
|
| For diagnostic purposes, retaining a copy of the old (currently installed) kernel configuration could be useful. |
|
| Back to top |
|
|
chiwi
Tux's lil' helper
Joined: 25 Apr 2004
Posts: 135
Location: Buenos Aires, Argentina
|
| Posted: Sun Oct 08, 2006 10:45 pm Post subject: |
|
|
| Code: |
PaqueServer ~ # uptime
19:41:06 up 15:05, 1 user, load average: 0.00, 0.00, 0.00
|
it's been running for 15 hours...  great, great desultory. I've taken the config.gz from the running live-cd kernel and compiled that kernel in my gentoo, it worked right away...the only problem is that that kernel is too generic. All modules are compiled and it has almost everthing built into the kernel. It's not a problem actually, but...you know.
what shoud I do next ? i'd like to find the root cause of this, so i know for future installations. will a diff .confg1 .config2 do ? I think there will be a lot of diferences
any thought ?
thanks |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Mon Oct 09, 2006 12:13 am Post subject: |
|
|
| chiwi wrote: | | what shoud I do next ? |
Check for watchdog timer support in the configuration of the kernel with the rebooting problem, grep WATCHDOG .config should at least show whether it is enabled or not.
Compare the configurations of the present and failed kernels, specifically the options under 'General setup --->' and 'Processor type and features ---> '.
| chiwi wrote: | | will a diff .confg1 .config2 do ? I think there will be a lot of diferences |
Presently, maybe. The information you seek would likely be lost in the clutter. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
