2.6.30.1-4 kernels freezes dual pentium-3 system
Quoted 5 lines
Box works works fine and very stable under 2.6.29.5 kernel, although it is angry of buggy MP table (see app. #2 below). But sometimes, this kernel correctly reboots the system at all, but this happens very rarely. In most cases, nobody detects the box was rebooted. And this is satisfactory for me.
so, what is it - stable or not stable ?
if sometimes "this kernel correctly reboots the system", do you mean that happens spontaneously, i.e. without being actively triggered ?
how can this box work fine then or at least being considered "stable" then ?
there is already an issue there, and if it behaves different with 2.6.30, it may be that the newer kernel triggers the existing problem in a different way.
Quoted 2 lines
As I said earlier, bisecting may be unpractical, because each iteration may take days or weeks.
afaik, you can also bisect on a different (i.e. faster) box.
i think it would be more interesting if there is anything in dmesg on such lockup. if not, maybe you can hook up a serial console or netconsole and trigger sysrq when you have another lockup.
regards
roland
List: linux-kernel Subject: 2.6.30.1-4 kernels freezes dual pentium-3 system From: ÐÑОпПв СÑаМОÑлав Date: 2009-08-03 8:44:26 Message-ID: 569920565.20090803124426 () mail ! ru
[Download message RAW]
I have a dual Pentium-3 system. It based on Asus CUR-DLS mainboard with 2 Pentium-3EB 1000MHz (133 MHz FSB) installed. Also, i'm using hardware RAID controller 3ware Escalade 7506-4LP, installed in the PCI-X expansion slot. This RAID is only one disk system in the box (RAID-5 on 4 IDE HDD 120GB from Seagate).
Box works works fine and very stable under 2.6.29.5 kernel, although it is angry of buggy MP table (see app. #2 below). But sometimes, this kernel correctly reboots the system at all, but this happens very rarely. In most cases, nobody detects the box was rebooted. And this is satisfactory for me.
But under 2.6.30.x kernels box freezes without any alerts. TTL before freezing is about 5-30 mins. I don't know why that shit happens. I'm ready to send any debug informations about this custom trouble, but if the specialists will request it with instructions for me.
Appendix #1: lspci
======================================================================
00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 05)
00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 05)
00:02.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev \
08) 00:04.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] 00:07.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
00:0f.1 IDE interface: Broadcom OSB4 IDE Controller
01:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet \
(rev 15) 01:03.0 RAID bus controller: 3ware Inc 7xxx/8xxx-series PATA/SATA-RAID (rev \
01) 01:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 Ultra3 SCSI \
Adapter (rev 01) 01:05.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 \
Ultra3 SCSI Adapter (rev 01)
________________________________________________________________
Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/02/
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
"devzero" == devzero <[email protected]> writes:
Box works works fine and very stable under 2.6.29.5 kernel, although it is angry of buggy MP table (see app. #2 below). But sometimes, this kernel correctly reboots the system at all, but this happens very rarely. In most cases, nobody detects the box was rebooted. And this is satisfactory for me.
devzero> so, what is it - stable or not stable ?
In my case, it's been stable under 2.6.29 (though with a Raid crash after 30+ days of uptime...). Under anything newer, it hasn't been stable, though I admit I haven't tried 2.6.29.x yet, though maybe 2.6.29.1 was ok. Not sure.
devzero> if sometimes "this kernel correctly reboots the system", do devzero> you mean that happens spontaneously, i.e. without being devzero> actively triggered ?
Kernel never reboots, the system locks up hard and *nothing* gets it back beyond the reset button. SysRq is total hosed, doesn't do anything.
devzero> i think it would be more interesting if there is anything in devzero> dmesg on such lockup. if not, maybe you can hook up a serial devzero> console or netconsole and trigger sysrq when you have another devzero> lockup.
There's notthing in dmesg, nothing on the screen (it's a server and not usually connected to a screen) and my other main machine is the NFS client of this box, so it's kinda painful to monitor.
I need to try rigging up a completely standalone system to do both netconsole and serial port console to see if I catch anything.
John
Just a quick followup, I've been doing a git bisect run over the past week or so trying to narrow this down. It's slow, since the system doesn't hang at any one point reliably. So I far, here's my git log:
Quoted 1 line
git bisect log
git bisect start
# bad: [f4b9a988685da6386d7f9a72df3098bcc3270526] Merge branch 'for-linus' of git://git.infradead.org/ubi-2.6
git bisect bad f4b9a988685da6386d7f9a72df3098bcc3270526
# good: [8e0ee43bc2c3e19db56a4adaa9a9b04ce885cd84] Linux 2.6.29 git bisect good 8e0ee43bc2c3e19db56a4adaa9a9b04ce885cd84
# bad: [095342389e2ed8deed07b3076f990260ce3c7c9f] perf_counter, x86:
generic use of cpuc->active
git bisect bad 095342389e2ed8deed07b3076f990260ce3c7c9f
# bad: [095342389e2ed8deed07b3076f990260ce3c7c9f] perf_counter, x86:
generic use of cpuc->active
git bisect bad 095342389e2ed8deed07b3076f990260ce3c7c9f
# bad: [095342389e2ed8deed07b3076f990260ce3c7c9f] perf_counter, x86:
generic use of cpuc->active
git bisect bad 095342389e2ed8deed07b3076f990260ce3c7c9f
# bad: [095342389e2ed8deed07b3076f990260ce3c7c9f] perf_counter, x86:
generic use of cpuc->active
git bisect bad 095342389e2ed8deed07b3076f990260ce3c7c9f
# bad: [ebc8eca169be0283d5a7ab54c4411dd59cfb0f27] Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc
Part of what slows me down is having to apply my patch to a scsi driver to ratelimit printks, otherwise I can spend over 30+ minutes waiting just for the console to scoll an endless stream of messages before it will continue to boot. Or even longer. :]
More as I get closer.
John
I just wanted to add, I am seeing similar freezes on an ancient dual Pentium Pro system I have. I've been having issues tracking down the problem as well; often it locks up before I can complete building a kernel.
Do you have perf enabled? I hope the lockup isn't somehow due to the enable p6 perf counters patches.
Vince