Hi,
after 1-3 hours with -test12 system hangs up with
- no response from mouse
- no response from keyboard (no sysrq, only sysrq+'b' works ...)
- no response from network (ICMP, TCP)
- nothing on console, nothing in logs (ie. nothing interesting or relevant
to crash).
System was not under load (1 user, X, no swapping ...)
( -test11 was up for 3 weeks with no problems and so do 2.2.17 ... )
slightly modified Red Hat 7.0:
Linux sarah.xxxxxxxxxxxxxxxxx 2.4.0-test11 #4 Sat Dec 9 14:24:20 CET
2000 i586 unknown
Kernel modules 2.3.21
Gnu C 2.96
Gnu Make 3.79.1
Binutils 2.10.0.18
Linux C Library > libc.2.2
Dynamic linker ldd (GNU libc) 2.2
Procps 2.0.7
Mount 2.10m
Net-tools 1.56
Console-tools 0.3.3
Sh-utils 2.0
Modules Loaded nls_iso8859-2 nls_cp852 vfat mad16 ad1848 sb_lib
uart401
DMESG: http://kocour.ms.mff.cuni.cz/~macok/kernel/dmesg
(Abit PX5, P166 (ovrclckd to 166), 128MB RAM, 2x IDE HDD, 3com509b ISA, Opti931)
.config: http://kocour.ms.mff.cuni.cz/~macok/kernel/.config
(with IPv6 + tunneling, iptables (ipv4/ipv6), no devfsd).
Have a nice day
P.S. I'm not subscribed, please Cc: me eventually ...
--
Martin Ma?ok
underground.cz
openbsd.cz
Same here... this thing started to happen right after upgrading to test12
(from test11). I am still being able to work on console for hours but when
I start using X the system dies silently. No oops, keyboard inactive
(can't do sysrq), and the LED on the monitor is orange, not green. This
happens under almost no load at all even after a fresh start. I have plenty
of free memory, swap file not used at all.
Just a 'me too'
Regards,
Petr
----- Original Message -----
From: "Martin Macok" <[email protected]>
Newsgroups: linux.kernel
Sent: Wednesday, December 13, 2000 10:53 AM
Subject: 2.4.0-test12 randomly hangs up
> Hi,
> after 1-3 hours with -test12 system hangs up with
> - no response from mouse
> - no response from keyboard (no sysrq, only sysrq+'b' works ...)
> - no response from network (ICMP, TCP)
> - nothing on console, nothing in logs (ie. nothing interesting or relevant
> to crash).
>
> System was not under load (1 user, X, no swapping ...)
On Wed, Dec 13, 2000 at 12:01:46PM +0100, Petr Sebor wrote:
> From: "Martin Macok" <[email protected]>
> > after 1-3 hours with -test12 system hangs up with
> > - no response from mouse
> > - no response from keyboard (no sysrq, only sysrq+'b' works ...)
> > - no response from network (ICMP, TCP)
> > - nothing on console, nothing in logs (ie. nothing interesting or relevant
> > to crash).
> >
> > System was not under load (1 user, X, no swapping ...)
>
> Same here... this thing started to happen right after upgrading to test12
> (from test11). I am still being able to work on console for hours but when
> I start using X the system dies silently. No oops, keyboard inactive
> (can't do sysrq), and the LED on the monitor is orange, not green. This
> happens under almost no load at all even after a fresh start. I have plenty
> of free memory, swap file not used at all.
>
> Just a 'me too'
I can (re)confirm that. I work several hours on console without any
problem ... then I start X session and after several minutes system
hangs.
Red Hat 7.0, XFree-3.3.6 (SVGA server), S3Virge/G2 (4MB)
(no problems with -test11 and 2.2.x before ...)
Have a nice day
(P.S. Thanks for Cc:'ing me ...)
--
Martin Ma?ok
underground.cz
openbsd.cz
Mine too did this 15 minutes ago.Just moving the mouse around in X and
suddenly complete freeze.No response to ping either.Such a thing didn't
happen for a long time to me.The only thing I've changed since test11 is
compiling fb+fbvesa in.
Martin Macok wrote:
>
> Hi,
> after 1-3 hours with -test12 system hangs up with
> - no response from mouse
> - no response from keyboard (no sysrq, only sysrq+'b' works ...)
> - no response from network (ICMP, TCP)
> - nothing on console, nothing in logs (ie. nothing interesting or relevant
> to crash).
>
> System was not under load (1 user, X, no swapping ...)
>
> ( -test11 was up for 3 weeks with no problems and so do 2.2.17 ... )
>
> slightly modified Red Hat 7.0:
>
> Linux sarah.xxxxxxxxxxxxxxxxx 2.4.0-test11 #4 Sat Dec 9 14:24:20 CET
> 2000 i586 unknown
> Kernel modules 2.3.21
> Gnu C 2.96
> Gnu Make 3.79.1
> Binutils 2.10.0.18
> Linux C Library > libc.2.2
> Dynamic linker ldd (GNU libc) 2.2
> Procps 2.0.7
> Mount 2.10m
> Net-tools 1.56
> Console-tools 0.3.3
> Sh-utils 2.0
> Modules Loaded nls_iso8859-2 nls_cp852 vfat mad16 ad1848 sb_lib
> uart401
>
> DMESG: http://kocour.ms.mff.cuni.cz/~macok/kernel/dmesg
> (Abit PX5, P166 (ovrclckd to 166), 128MB RAM, 2x IDE HDD, 3com509b ISA, Opti931)
Overclocking is a guaranteed way to get random hangups. Put it back to
its recommended clock and it might work fine. Keep in mind that while
this may not have shown up before, overclocking gradually degrades a
processor's stability (trust me, I ran several 486 and pentiums and even
a k6-2 down to where they wouldn't even work at the normal clock). Try
sticking it back to normal.
In article <[email protected]> you wrote:
> I can (re)confirm that. I work several hours on console without any
> problem ... then I start X session and after several minutes system
> hangs.
I can confirm that, too.
Todaye, crashed two difference machines
One: AMD-K6 3D, 300 MHz, RH 7.0 + updates, 64MB RAM
Second one: AMD Athlon 600, 600MHz with, 128MB RAM, RH 7.0+updates
> Red Hat 7.0, XFree-3.3.6 (SVGA server), S3Virge/G2 (4MB)
> (no problems with -test11 and 2.2.x before ...)
Exactly
--
*[ ?ukasz Tr?bi?ski ]*
SysAdmin @wsisiz.edu.pl
On Wed, 13 Dec 2000, Lukasz Trabinski wrote:
> In article <[email protected]> you wrote:
>
> > I can (re)confirm that. I work several hours on console without any
> > problem ... then I start X session and after several minutes system
> > hangs.
>
> I can confirm that, too.
> Todaye, crashed two difference machines
> One: AMD-K6 3D, 300 MHz, RH 7.0 + updates, 64MB RAM
> Second one: AMD Athlon 600, 600MHz with, 128MB RAM, RH 7.0+updates
>
> > Red Hat 7.0, XFree-3.3.6 (SVGA server), S3Virge/G2 (4MB)
I've been running 2.4.0-test12 patched with only the O_SYNC bug fix and I have
_not_ experienced any lockups on this machine.
Classic Athlon 825(750) MHz, 128MB Ram,
RH 7.0 based w/glibc 2.2, XFree-3.3.6 (S3 Trio 64 accel server), gcc 2.95.2
Not sure what the problem is yet... keep trying folks. :)
-Byron
--
Byron Stanoszek Ph: (330) 644-3059
Systems Programmer Fax: (330) 644-8110
Commercial Timesharing Inc. Email: [email protected]
On Wed, 13 Dec 2000, Lukasz Trabinski wrote:
> In article <[email protected]> you wrote:
>
> > I can (re)confirm that. I work several hours on console without any
> > problem ... then I start X session and after several minutes system
> > hangs.
>
> I can confirm that, too.
> Todaye, crashed two difference machines
> One: AMD-K6 3D, 300 MHz, RH 7.0 + updates, 64MB RAM
> Second one: AMD Athlon 600, 600MHz with, 128MB RAM, RH 7.0+updates
>
> > Red Hat 7.0, XFree-3.3.6 (SVGA server), S3Virge/G2 (4MB)
>
> > (no problems with -test11 and 2.2.x before ...)
>
> Exactly
Not here. I've been seeing occasional hard freezes since test10.
Mostly after a period of idle cpu (reading kernel code.. reader
enters catatonic state with smoke pouring out ears;) X isn't running.
-Mike
Byron Stanoszek wrote:
>
> On Wed, 13 Dec 2000, Lukasz Trabinski wrote:
>
> > In article <[email protected]> you wrote:
> >
> > > I can (re)confirm that. I work several hours on console without any
> > > problem ... then I start X session and after several minutes system
> > > hangs.
> >
> > I can confirm that, too.
> > Todaye, crashed two difference machines
> > One: AMD-K6 3D, 300 MHz, RH 7.0 + updates, 64MB RAM
> > Second one: AMD Athlon 600, 600MHz with, 128MB RAM, RH 7.0+updates
> >
> > > Red Hat 7.0, XFree-3.3.6 (SVGA server), S3Virge/G2 (4MB)
>
> I've been running 2.4.0-test12 patched with only the O_SYNC bug fix and I have
> _not_ experienced any lockups on this machine.
>
> Classic Athlon 825(750) MHz, 128MB Ram,
> RH 7.0 based w/glibc 2.2, XFree-3.3.6 (S3 Trio 64 accel server), gcc 2.95.2
>
> Not sure what the problem is yet... keep trying folks. :)
>
Maybe it's the 3.3.6. RH 7.0 comes with 4.0.1, and a newer glibc.
Perhaps try recompiling XFree86 against the latest RH 7.0 glibc (2.1.94)
and see what happens, or upgrade your XFree86 to the standard RH 7.0
XFree86 4.0.1.
--
Matthew Vanecek
perl -e 'print
$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
********************************************************************************
For 93 million miles, there is nothing between the sun and my shadow
except me.
I'm always getting in the way of something...
> Maybe it's the 3.3.6. RH 7.0 comes with 4.0.1, and a newer glibc.
> Perhaps try recompiling XFree86 against the latest RH 7.0 glibc (2.1.94)
> and see what happens, or upgrade your XFree86 to the standard RH 7.0
> XFree86 4.0.1.
>
> --
> Matthew Vanecek
Nope, it dies even with my handbuilt XFree86 4.0.1 DRI (Slack7.0) on
plain KDE2.0.1. I have no extra patches in kernel and quite common HW
[ Celeron 433, 192MB of RAM, 13GB HDD ( ext2 & vfat partitioned ),
PCI NE2000 NIC, ES1371 sound, Intel BX chipset board and ATI
Radeon32DDR - maybe the new MTRR stuff is not working right ? ] At
least it was running fine with test11 and with test11-ac4
Regards,
Petr
On Wed, Dec 13, 2000 at 05:27:03PM -0500, David Riley wrote:
> > DMESG: http://kocour.ms.mff.cuni.cz/~macok/kernel/dmesg (Abit
> > PX5, P166 (ovrclckd to 166), 128MB RAM, 2x IDE HDD, 3com509b ISA,
> > Opti931)
>
> Overclocking is a guaranteed way to get random hangups. Put it back
> to its recommended clock and it might work fine. Keep in mind that
> while this may not have shown up before, overclocking gradually
> degrades a processor's stability (trust me, I ran several 486 and
> pentiums and even a k6-2 down to where they wouldn't even work at
> the normal clock). Try sticking it back to normal.
I know it, but it's P150 overclocked to 166 and it can run even on 200
with 2.4.0-test11 and 2.2.x for several weeks without hanging up. But it
hangs up with -test12 several minutes after I start X server and
several people have already confirm that ...
(I'm going to try latest -test13-pre ... I cannot see Changelog or
test13.log anywhere ...)
Have a nice day
(Thank you for Cc:'ing me, I'm not subscribed)
--
Martin Ma?ok
underground.cz
openbsd.cz
Here too. :((
My CPU: Pentium 150 (NO overclock). 64 MB RAM.
Linux freeze (no keyboard, no disk activity) 5-10 minutes after I load X.
No freezing with other 2.4.0-testxx kernels.
Please note: I'm not subscribed.
Ciao
Ale
--
Alessandro Airaghi | e-mail: [email protected]
| [email protected]
|
| home page: http://web.tiscalinet.it/airaghi