ia64 r255488: spontaneous reboots, no panic, no trace in logs
On r255488 ia64 I get spontaneous reboots, which are more or less reproducible. These are triggered by nginx serving poudriere built packages. The is no panic, and no traces in the logs. The system just reboots. A similar issue was seen in about 2011, when we tried to build is64 packages on portscluster. I think marcel@ gave up on it. Has any new diagnostics been added since then? Anything else I could try to see what is going on prior to the reboot? Thanks Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Spontaneous reboots
Brian Feldman wrote: > It could. Ahem... are you absolutely certain there are no messages in > /var/log/messages that happen before the reboot? Completely certain, there was nothing in /var/log/all either (which as the name suggests, all syslog messages are written to). -- Ben Smithurst b...@scientia.demon.co.uk send a blank message to ben+...@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Spontaneous reboots
On Thu, 25 Mar 1999, Ben Smithurst wrote: > Kris Kennaway wrote: > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > This has happened a few times on my -stable box, though not very > often. It just happened a few minutes ago, I wasn't doing anything on > the machine, I wasn't even logged in. No core dump or anything. :-( I'd > think nothing of it on a -current box, but it seems a bit worrying that > this sort of thing happens on a supposedly "stable" version. Mind you, > it could be a hardware problem I suppose. It could. Ahem... are you absolutely certain there are no messages in /var/log/messages that happen before the reboot? > > Karl Pielorz wrote: > > > The sort of thing we're looking for is, Which version of FreeBSD > > (I'd assume something -current because you posted to the -current > > mailing list, but how current?), what hardware (i.e. CPU type > > [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive > > (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? > > FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got > any hardware I'd class as weird. Disk info, > > $ mount > /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) > /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) > /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) > /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) > /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) > procfs on /proc (local) > $ swapinfo > Device 1K-blocks UsedAvail Capacity Type > /dev/wd2s4b1606500 160522 0%Interleaved > > I'm not sure how recent, the machine had been up for nearly 22 days, and > I think I rebuilt the world soon before that, so it's as of around the > beginning of March. > > Brian Feldman wrote: > > > He should proviide a full dmesg from bootverbose mode. > > OK, I wonder if anyone can spot the problem in this (if indeed there is > something I've broken)... > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 > b...@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA > Calibrating clock(s) ... i8254 clock: 1193483 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CPU: Cyrix 6x86 (486-class CPU) > Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 > real memory = 50331648 (49152K bytes) > Physical memory chunk(s): > 0x1000 - 0x0009, 651264 bytes (159 pages) > 0x0020 - 0x02ffdfff, 48226304 bytes (11774 pages) > avail memory = 47013888 (45912K bytes) > Found BIOS32 Service Directory header at 0xf00fad20 > Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 > PCI BIOS entry at 0xb1d0 > Other BIOS signatures found: > ACPI: > $PnP: 000fbf50 > pci_open(1): mode 1 addr port (0x0cf8) is 0x805c > pci_open(1a): mode1res=0x8000 (0x8000) > pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=70308086) > Probing for devices on PCI bus 0: > found-> vendor=0x8086, dev=0x7030, revid=0x02 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0secondarybus=0 > chip0: rev 0x02 on pci0.0.0 > > PCI Concurrency: enabled > Cache: 256K pipelined-burst secondary; L1 enabled > DRAM: no memory hole, 66 MHz refresh > Read burst timing: x-2-2-2/x-3-3-3 > Write burst timing: x-3-3-3 > RAS-CAS delay: 3 clocks > found-> vendor=0x8086, dev=0x7000, revid=0x01 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0secondarybus=0 > chip1: rev 0x01 on pci0.7.0 > I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks > Extended BIOS: disabled > Lower BIOS: disabled > Coprocessor IRQ13: enabled > Mouse IRQ12: disabled > Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled > MB0: IRQ15, MB1: > found-> vendor=0x8086, dev=0x7010, revid=0x00 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0secondarybus=0 > map[0]: type 4, range 32, base f000, size 4 > ide_pci0: rev 0x00 on pci0.7.1 > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, > intel_piix_status: IORDY sampling disabled, > intel_piix_status: fast PIO disabled > ide_pci: busmaster 0 status: 04 from port: f002 > intel_piix_status: secondary master/slave sample = 3, master/slav
Re: Spontaneous reboots
There was another report of a similar problem on -hackers. Removing the 'pseudo-device splash' seemed to fix things. You might also try the patches in this thread. http://www.freebsd.org/cgi/getmsg.cgi?fetch=715663+0+archive/1999/freebsd-hackers/19990307.freebsd-hackers Nathan Ben Smithurst wrote: > Kris Kennaway wrote: > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > This has happened a few times on my -stable box, though not very > often. It just happened a few minutes ago, I wasn't doing anything on > the machine, I wasn't even logged in. No core dump or anything. :-( I'd > think nothing of it on a -current box, but it seems a bit worrying that > this sort of thing happens on a supposedly "stable" version. Mind you, > it could be a hardware problem I suppose. > > Karl Pielorz wrote: > > > The sort of thing we're looking for is, Which version of FreeBSD > > (I'd assume something -current because you posted to the -current > > mailing list, but how current?), what hardware (i.e. CPU type > > [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive > > (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? > > FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got > any hardware I'd class as weird. Disk info, > > $ mount > /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) > /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) > /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) > /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) > /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) > procfs on /proc (local) > $ swapinfo > Device 1K-blocks UsedAvail Capacity Type > /dev/wd2s4b1606500 160522 0%Interleaved > > I'm not sure how recent, the machine had been up for nearly 22 days, and > I think I rebuilt the world soon before that, so it's as of around the > beginning of March. > > Brian Feldman wrote: > > > He should proviide a full dmesg from bootverbose mode. > > OK, I wonder if anyone can spot the problem in this (if indeed there is > something I've broken)... > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 > b...@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA > Calibrating clock(s) ... i8254 clock: 1193483 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CPU: Cyrix 6x86 (486-class CPU) > Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 > real memory = 50331648 (49152K bytes) > Physical memory chunk(s): > 0x1000 - 0x0009, 651264 bytes (159 pages) > 0x0020 - 0x02ffdfff, 48226304 bytes (11774 pages) > avail memory = 47013888 (45912K bytes) > Found BIOS32 Service Directory header at 0xf00fad20 > Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 > PCI BIOS entry at 0xb1d0 > Other BIOS signatures found: > ACPI: > $PnP: 000fbf50 > pci_open(1): mode 1 addr port (0x0cf8) is 0x805c > pci_open(1a): mode1res=0x8000 (0x8000) > pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=70308086) > Probing for devices on PCI bus 0: > found-> vendor=0x8086, dev=0x7030, revid=0x02 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0secondarybus=0 > chip0: rev 0x02 on pci0.0.0 > > PCI Concurrency: enabled > Cache: 256K pipelined-burst secondary; L1 enabled > DRAM: no memory hole, 66 MHz refresh > Read burst timing: x-2-2-2/x-3-3-3 > Write burst timing: x-3-3-3 > RAS-CAS delay: 3 clocks > found-> vendor=0x8086, dev=0x7000, revid=0x01 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0secondarybus=0 > chip1: rev 0x01 on pci0.7.0 > I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks > Extended BIOS: disabled > Lower BIOS: disabled > Coprocessor IRQ13: enabled > Mouse IRQ12: disabled > Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled > MB0: IRQ15, MB1: > found-> vendor=0x8086, dev=0x7010, revid=0x00 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0secondarybus=0 > map[0]: type 4, range 32, base f000, size 4 > ide_pci0: rev 0x00 on pci0.7.1 > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 > intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, > intel_piix_status: IORDY sampling disabled, > intel_piix_status
Re: Spontaneous reboots
Kris Kennaway wrote: > Has anyone else been seeing this? What kind of information would help to > narrow the problem down? This has happened a few times on my -stable box, though not very often. It just happened a few minutes ago, I wasn't doing anything on the machine, I wasn't even logged in. No core dump or anything. :-( I'd think nothing of it on a -current box, but it seems a bit worrying that this sort of thing happens on a supposedly "stable" version. Mind you, it could be a hardware problem I suppose. Karl Pielorz wrote: > The sort of thing we're looking for is, Which version of FreeBSD > (I'd assume something -current because you posted to the -current > mailing list, but how current?), what hardware (i.e. CPU type > [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive > (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? FreeBSD 3.1-STABLE, Cyrix 6x86 133MHz, 48MB RAM. I don't think I've got any hardware I'd class as weird. Disk info, $ mount /dev/wd0s2a on / (local, noatime, writes: sync 5 async 17) /dev/wd0s3c on /home (local, soft-updates, writes: sync 2 async 61) /dev/wd2s1c on /tmp (local, soft-updates, writes: sync 2 async 31) /dev/wd2s2e on /usr (local, soft-updates, writes: sync 2 async 86) /dev/wd2s3e on /var (local, nosuid, soft-updates, writes: sync 318 async 470) procfs on /proc (local) $ swapinfo Device 1K-blocks UsedAvail Capacity Type /dev/wd2s4b1606500 160522 0%Interleaved I'm not sure how recent, the machine had been up for nearly 22 days, and I think I rebuilt the world soon before that, so it's as of around the beginning of March. Brian Feldman wrote: > He should proviide a full dmesg from bootverbose mode. OK, I wonder if anyone can spot the problem in this (if indeed there is something I've broken)... Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #104: Tue Mar 2 18:29:08 GMT 1999 b...@scientia.demon.co.uk:/usr/src/sys/compile/SCIENTIA Calibrating clock(s) ... i8254 clock: 1193483 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CPU: Cyrix 6x86 (486-class CPU) Origin = "CyrixInstead" DIR=0x2231 Stepping=2 Revision=2 real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0020 - 0x02ffdfff, 48226304 bytes (11774 pages) avail memory = 47013888 (45912K bytes) Found BIOS32 Service Directory header at 0xf00fad20 Entry = 0xfb1a0 (0xf00fb1a0) Rev = 0 Len = 1 PCI BIOS entry at 0xb1d0 Other BIOS signatures found: ACPI: $PnP: 000fbf50 pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=70308086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7030, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: rev 0x02 on pci0.0.0 PCI Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 66 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 2 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: disabled, C: IRQ11, D: disabled MB0: IRQ15, MB1: found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 4, range 32, base f000, size 4 ide_pci0: rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: f002 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status:
Re: Spontaneous reboots
On Tue, 23 Mar 1999, Karl Pielorz wrote: > Kris Kennaway wrote: > > > > For about the past week I've been getting spontaneous reboots on my machine. > > As far as I can tell, there's no obvious common connection - most recently > > my > > box was under load at the time, but the time before that all I did was move > > the mouse (shades of Windows :-) and nothing else much was running. > > > > This does only seem to happen when I'm using the machine - after a few > > hours, > > a reboot is pretty much guaranteed (sounds like a resource leak of some kind > > to me). Beyond that, I don't know. My kernel and machine config haven't > > changed recently. > > > > Has anyone else been seeing this? What kind of information would help to > > narrow the problem down? > > The sort of thing we're looking for is, Which version of FreeBSD (I'd assume > something -current because you posted to the -current mailing list, but how > current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much > memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' > hardware in there? > > Also, you say "when I moved the mouse" - does that mean your machine lives in > X-Windows all the time? - Does it crash when it's not running X etc? What type > of video card does your machine have? > > The more detail you can provide (without going too OTT :-) - The more likely > someone will be able to help :-) I have two boxes here tracking 4.0-current, > and so far (looking for a nice piece of wood to touch), I've not seen any > reboots on either for quite a long time (i.e>months) :) > > -Karl > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > He should proviide a full dmesg from bootverbose mode. One thing I've seen is that K6-2's in write allocated mode have big problems. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Spontaneous reboots
Sounds like a NMI generated by memory parity errors or motherboard malfunction. Good Luck, Jerry Hicks wghi...@bellsouth.net From: Kris Kennaway Subject: Spontaneous reboots Date: Tue, 23 Mar 1999 23:32:28 +0930 (CST) > For about the past week I've been getting spontaneous reboots on my machine. > As far as I can tell, there's no obvious common connection - most recently my > box was under load at the time, but the time before that all I did was move > the mouse (shades of Windows :-) and nothing else much was running. > > This does only seem to happen when I'm using the machine - after a few hours, > a reboot is pretty much guaranteed (sounds like a resource leak of some kind > to me). Beyond that, I don't know. My kernel and machine config haven't > changed recently. > > Has anyone else been seeing this? What kind of information would help to > narrow the problem down? > > Kris > > - > The Feynman problem-solving algorithm: 1. Write down the problem >2. Think real hard >3. Write down the solution > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Spontaneous reboots
Kris Kennaway wrote: > > For about the past week I've been getting spontaneous reboots on my machine. > As far as I can tell, there's no obvious common connection - most recently my > box was under load at the time, but the time before that all I did was move > the mouse (shades of Windows :-) and nothing else much was running. > > This does only seem to happen when I'm using the machine - after a few hours, > a reboot is pretty much guaranteed (sounds like a resource leak of some kind > to me). Beyond that, I don't know. My kernel and machine config haven't > changed recently. > > Has anyone else been seeing this? What kind of information would help to > narrow the problem down? The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? Also, you say "when I moved the mouse" - does that mean your machine lives in X-Windows all the time? - Does it crash when it's not running X etc? What type of video card does your machine have? The more detail you can provide (without going too OTT :-) - The more likely someone will be able to help :-) I have two boxes here tracking 4.0-current, and so far (looking for a nice piece of wood to touch), I've not seen any reboots on either for quite a long time (i.e>months) :) -Karl To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Spontaneous reboots
For about the past week I've been getting spontaneous reboots on my machine. As far as I can tell, there's no obvious common connection - most recently my box was under load at the time, but the time before that all I did was move the mouse (shades of Windows :-) and nothing else much was running. This does only seem to happen when I'm using the machine - after a few hours, a reboot is pretty much guaranteed (sounds like a resource leak of some kind to me). Beyond that, I don't know. My kernel and machine config haven't changed recently. Has anyone else been seeing this? What kind of information would help to narrow the problem down? Kris - The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
HEADS UP: Spontaneous reboots
Everybody who is experiencing spontaneous reboots under 3.0-STABLE or 4.0-CURRENT (and did not experience them with 2.2.8 or earlier) and cannot find any indication of what could be wrong (nothing on the console and nothing in syslog), please send me (in *private* mail) the output of "dmesg" on your machine and your kernel configuration file. Also send a list of all daemons that are running on a freshly booted system and any other information you think could be relevant. If you are a commiter or a networking guru, even better. :) Please send the above data, even if you have already responded to the "Spontaneous reboots" thread on this mailing list. I'm trying to compile a list of hardware and software configurations that experience the problem and see if there is something in common between them. If we want to fix the problem, we at least need a starting point. For now it looks like it is a problem with the networking code, so please send a description of what network activity is going on when you experience the reboots. I will summarize the responses I receive. Also if you have a good idea how we could attack the problem, please speak up. For now my idea is to find a common software and hardware configuration and then try to sistematically remove components that could cause the problem. I have separetely posted this message to both freebsd-current and freebsd-stable, as it seems to affect both branches. Please DO NOT respond to the mailing list. Thank you for your attention. Blaz Zupan, b...@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
