thr3ads.net - freebsd stable - (Seemingly) Spontaneous rebooting [Nov 2006]

If this information is useful, please help other people find it:
Share via:

Joe Holden

2006-Nov-17 07:05 UTC

(Seemingly) Spontaneous rebooting

Hi, i'm observing random reboots on a dedicated machine I have with 1&1.

I have included as much information as I can think of, if there is 
anything else I can provide, please ask.

dmesg:
claire# dmesg
Copyright (c) 1992-2006 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-PRERELEASE #1: Sun Nov  5 14:16:45 UTC 2006
     root@claire.ber.rewt.org.uk:/usr/obj/usr/src/sys/claire
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2404.12-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
 
Features=0xbfebf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
   Features2=0x400<CNTX-ID>
real memory  = 1065353216 (1016 MB)
avail memory = 1033650176 (985 MB)
kbd1 at kbdmux0
cpu0 on motherboard
pcib0: <Host to PCI bridge> pcibus 0 on motherboard
pir0: <PCI Interrupt Routing Table: 4 Entries> on motherboard
pci0: <PCI bus> on pcib0
$PIR: No matching entry for 0.16.INTA
$PIR: No matching entry for 0.16.INTB
$PIR: No matching entry for 0.16.INTD
$PIR: No matching entry for 0.18.INTA
agp0: <VIA 8703 (P4M266x/P4N266) host to PCI bridge> mem 
0xea000000-0xea3fffff at device 0.0 on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
pci0: <serial bus, USB> at device 16.0 (no driver attached)
pci0: <serial bus, USB> at device 16.1 (no driver attached)
pci0: <serial bus, USB> at device 16.3 (no driver attached)
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 8235 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xdc00-0xdc0f at device 17.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xe000-0xe0ff mem 
0xea401000-0xea4010ff irq 15 at device 18.0 on pci0
miibus0: <MII bus> on vr0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:40:63:c3:72:02
orm0: <ISA Option ROMs> at iomem 
0xc0000-0xcbfff,0xcc000-0xcffff,0xd0000-0xd17ff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0c01> can't assign resources (memory)
unknown: <PNP0c02> can't assign resources (memory)
unknown: <PNP0501> can't assign resources (port)
Timecounter "TSC" frequency 2404116192 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 76319MB <Seagate ST380021A 3.05> at ata0-master UDMA100
Trying to mount root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
/usr: mount pending error: blocks 556 files 20
WARNING: /var was not properly dismounted
uhci0: <VIA 83C572 USB controller> port 0xd000-0xd01f irq 15 at device 
16.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 12 at device 
16.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ehci0: <VIA VT6202 USB 2.0 controller> mem 0xea400000-0xea4000ff irq 11 
at device 16.3 on pci0
ehci0: [GIANT-LOCKED]
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <VIA VT6202 USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 4 ports with 4 removable, self powered

pciconf -lv:
claire# pciconf -lv
agp0@pci0:0:0:  class=0x060000 card=0xa0031106 chip=0x31481106 rev=0x00 
hdr=0x00
     vendor   = 'VIA Technologies Inc'
     device   = 'VT8751 ProSavageDDR P4M266 System Controller'
     class    = bridge
     subclass = HOST-PCI
pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0xb0911106 rev=0x00 
hdr=0x01
     vendor   = 'VIA Technologies Inc'
     device   = 'VT8633 Apollo Pro 266 CPU to AGP Controller'
     class    = bridge
     subclass = PCI-PCI
uhci0@pci0:16:0:        class=0x0c0300 card=0x30381106 chip=0x30381106 
rev=0x80 hdr=0x00
     vendor   = 'VIA Technologies Inc'
     device   = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)'
     class    = serial bus
     subclass = USB
uhci1@pci0:16:1:        class=0x0c0300 card=0x30381106 chip=0x30381106 
rev=0x80 hdr=0x00
     vendor   = 'VIA Technologies Inc'
     device   = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)'
     class    = serial bus
     subclass = USB
ehci0@pci0:16:3:        class=0x0c0320 card=0x31041106 chip=0x31041106 
rev=0x82 hdr=0x00
     vendor   = 'VIA Technologies Inc'
     device   = 'VT6202 USB 2.0 Enhanced Host Controller'
     class    = serial bus
     subclass = USB
isab0@pci0:17:0:        class=0x060100 card=0xa0031106 chip=0x31771106 
rev=0x00 hdr=0x00
     vendor   = 'VIA Technologies Inc'
     device   = 'VT8235 PCI to ISA Bridge'
     class    = bridge
     subclass = PCI-ISA
atapci0@pci0:17:1:      class=0x01018a card=0xa0031106 chip=0x05711106 
rev=0x06 hdr=0x00
     vendor   = 'VIA Technologies Inc'
     device   = 'VT82xxxx EIDE Controller (All VIA Chipsets)'
     class    = mass storage
     subclass = ATA
vr0@pci0:18:0:  class=0x020000 card=0x01061106 chip=0x30651106 rev=0x74 
hdr=0x00
     vendor   = 'VIA Technologies Inc'
     device   = 'VT6102 Rhine II PCI Fast Ethernet Controller'
     class    = network
     subclass = ethernet
none0@pci1:0:0: class=0x030000 card=0xa0031106 chip=0x8d045333 rev=0x00 
hdr=0x00
     vendor   = 'S3 Graphics Co., Ltd.'
     device   = '86C420 ProSavage DDR'
     class    = display
     subclass = VGA

uname -a:
claire# uname -a
FreeBSD claire.ber.rewt.org.uk 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: 
Sun Nov  5 14:16:45 UTC 2006 
root@claire.ber.rewt.org.uk:/usr/obj/usr/src/sys/claire  i386

df -h:
claire# df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad0s1a    496M     61M    395M    13%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad0s1e    496M     18K    456M     0%    /tmp
/dev/ad0s1f     70G    5.0G     59G     8%    /usr
/dev/ad0s1d    1.1G    102M    908M    10%    /var
devfs          1.0K    1.0K      0B   100%    /var/named/dev


As a side note: If anyone is wanting to know how to convert their evil 
1&1 linux machine to FreeBSD, send me an email and i'll send you the 
info (I intend to write an article on this eventually)


TIA,
Joe

Stefan Bethke

2006-Nov-17 07:33 UTC

head link

(Seemingly) Spontaneous rebooting

Am 17.11.2006 um 08:05 schrieb Joe Holden:
> Hi, i'm observing random reboots on a dedicated machine I have with  
> 1&1.
How do you know it's rebbots as opposed to crashes/panics? Enable  
crashdumps in rc.conf and see if you get a dump.


Stefan

-- 
Stefan Bethke <stb@lassitu.de>   Fon +49 170 346 0140

Joseph Koshy

2006-Nov-17 13:37 UTC

head link

(Seemingly) Spontaneous rebooting

jh> Hi, i'm observing random reboots on a dedicated machine I
jh> have with 1&1.

jh> I have included as much information as I can think of, if
jh> there is anything else I can provide, please ask.

Is the machine stable otherwise?  Does it pass its
builtin diagnostics?

A good way to check for bad memory/insufficient cooling
is to run a 'make -jN  buildworld' repeatedly for 24+hrs,
where you choose `N' according to the amount of CPU and
RAM you have.

-- 
FreeBSD Volunteer,     http://people.freebsd.org/~jkoshy

Joe Holden

2006-Nov-17 13:41 UTC

head link

(Seemingly) Spontaneous rebooting

Joseph Koshy wrote:> Is the machine stable otherwise?  Does it pass its
> builtin diagnostics?Hi Joseph,
It has coped sufficiently during the extensive number of 
make/buildworlds and day to day use, nothing seems to trigger it, its 
fairly random.

Ta,
Joe
-- 
finger joe@joeholden.co.uk

Stefan Bethke

2006-Nov-17 13:52 UTC

head link

(Seemingly) Spontaneous rebooting

Am 17.11.2006 um 14:35 schrieb Joe Holden:
> Dominic Marks wrote:
>> See if you can get temperature readings from the hardware. Is
>> the system busy?
> Hi Dominic, there is no sensors on said machine, it was up for 150  
> odd days running linux prior to the change.
If the system has ACPI, you might get some temperature information  
from the sysctl hw.acpi.thermal OIDs.

If the hard disk is recent enough, it might have a temperature  
sensors as well, see sysutils/smartmontools.


Stefan

-- 
Stefan Bethke <stb@lassitu.de>   Fon +49 170 346 0140

Joe Holden

2006-Nov-17 13:56 UTC

head link

(Seemingly) Spontaneous rebooting

Stefan Bethke wrote:> 
> If the system has ACPI, you might get some temperature information from 
> the sysctl hw.acpi.thermal OIDs.
> No acpi whatsoever, it is a very "stripped down" machine, looks like a
blade or something.
> If the hard disk is recent enough, it might have a temperature sensors 
> as well, see sysutils/smartmontools.
> 17 degrees C apparently.

Ta,
Joe
-- 
finger joe@joeholden.co.uk

Ivan Voras

2006-Dec-19 15:17 UTC

head link

(Seemingly) Spontaneous rebooting

Joe Holden wrote:
> It has coped sufficiently during the extensive number of
> make/buildworlds and day to day use, nothing seems to trigger it, its
> fairly random.
How about memtest86? You should also leave it for a few hours.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20061219/8e0c00eb/signature.pgp

2006-Dec-21 06:26 UTC

head link

(Seemingly) Spontaneous rebooting

It is really a bug. But in my case it seems to be the hardware problem after
serval days fight with this crash.
The old server even crashes before booting to the login prompt. :( I have to
changes to another server now.

2006/12/20, Martin Blapp <mb@imp.ch>:>
>
> Hi,
>
> Maybe you are experiencing similar crashes as I did in the tty code.
> I had 8 ! crashes in 4 days on a busy server ...
>
> Fix:
>
>
>
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/tty.c.diff?r1=1.266&r2=1.267
>
> I hope to commit this soon to RELENG_6_2
>
> Martin
>
> Martin Blapp, <mb@imp.ch> <mbr@FreeBSD.org>
> ------------------------------------------------------------------
> ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
> Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
> PGP: <finger -l mbr@freebsd.org>
> PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
> ------------------------------------------------------------------
>
>

-- 
Ma Jie

freebsd stable - Nov 2006 - (Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting

(Seemingly) Spontaneous rebooting