noon
I have continued to be plagued by a kernel hang or lockup since FC 2 on AMD
dual cpus with ATI radeon 7500. I am currently running FC 3 with the latset
released kernel (681).
Is there any hope for the problem by using one of the test kernels?
Thanks.
Tom Browder
2:47 p.m.
On Thursday 30 December 2004 13:00, Tom Browder wrote:
I have continued to be plagued by a kernel hang or lockup since FC 2
on AMD
dual cpus with ATI radeon 7500. I am currently running FC 3 with the
latset released kernel (681).
Is there any hope for the problem by using one of the test kernels?
Can you expend on your problem a bit?
I have a dual Athlon system running FC3 (never ran FC2 on it but FC1 did not
have problems) and it experiences a solid lockup at times (random events
maybe once a week or so). The system hard freezes and I have to do a
hardware reset to get it back up (cannot ssh into from another system).
--
Gene
4:18 p.m.
On Thu, 2004-12-30 at 15:47 -0500, Gene C. wrote:
I have a dual Athlon system running FC3 (never ran FC2 on it but FC1
did not
have problems) and it experiences a solid lockup at times (random events
maybe once a week or so). The system hard freezes and I have to do a
hardware reset to get it back up (cannot ssh into from another system).
--
Gene
FWIW I also have a dual athlon system; specifically, an asus a7m266-d.
I also have a radeon 7500, and the only problems I have seen are related
to the known issues with dual head and virtual terminals. Other than
that, my system has been completely stable.
Scott
4:48 p.m.
-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com
[mailto:fedora-test-list-bounces@redhat.com] On Behalf Of Gene C.
Sent: Thursday, December 30, 2004 2:47 PM
To: fedora-test-list(a)redhat.com
Subject: Re: FC 3 and Kernel Lock or Hang
Can you expend on your problem a bit?
I have a dual Athlon system running FC3 (never ran FC2 on it
but FC1 did not have problems) and it experiences a solid
lockup at times (random events maybe once a week or so). The
system hard freezes and I have to do a hardware reset to get
it back up (cannot ssh into from another system).
Sounds exactly like my problem, except it happens more often. I have three
other machines identically configured at work, and they exhibit the same
behavior (2 running FC 2, 1 running FC 3).
And never had the problem on any with FC 1.
-Tom
8:58 p.m.
-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com
[mailto:fedora-test-list-bounces@redhat.com] On Behalf Of Tom Browder
Sent: Thursday, December 30, 2004 4:51 PM
To: 'For testers of Fedora Core development releases'
Subject: RE: FC 3 and Kernel Lock or Hang
I just restarted with the test 715 kernel to see if things
are any better.
They aren't--locks up just the same.
-Tom
5:04 p.m.
On Thu, Dec 30, 2004, Tom Browder <tbrowder(a)cox.net> wrote:
> -----Original Message-----
> From: fedora-test-list-bounces(a)redhat.com
> [mailto:fedora-test-list-bounces@redhat.com] On Behalf Of Gene C.
> Sent: Thursday, December 30, 2004 2:47 PM
> To: fedora-test-list(a)redhat.com
> Subject: Re: FC 3 and Kernel Lock or Hang
> Can you expend on your problem a bit?
>
> I have a dual Athlon system running FC3 (never ran FC2 on it
> but FC1 did not have problems) and it experiences a solid
> lockup at times (random events maybe once a week or so). The
> system hard freezes and I have to do a hardware reset to get
> it back up (cannot ssh into from another system).
Sounds exactly like my problem, except it happens more often. I have three
other machines identically configured at work, and they exhibit the same
behavior (2 running FC 2, 1 running FC 3).
And never had the problem on any with FC 1.
I have a dual Athlon that mysteriously locks up too. I've had hardware
problems with it in the past, but I thought I had it fixed with FC1 a
while ago, but then started having lockups again when I upgraded to FC3.
I thought it was the hardware problems coming back again, but I guess
there might be an Athlon SMP bug with the FC3 kernels.
JE
2:11 a.m.
On Thu, 2004-12-30 at 15:04 -0800, Johannes Erdfelt wrote:
On Thu, Dec 30, 2004, Tom Browder <tbrowder(a)cox.net> wrote:
> > -----Original Message-----
> > From: fedora-test-list-bounces(a)redhat.com
> > [mailto:fedora-test-list-bounces@redhat.com] On Behalf Of Gene C.
> > Sent: Thursday, December 30, 2004 2:47 PM
> > To: fedora-test-list(a)redhat.com
> > Subject: Re: FC 3 and Kernel Lock or Hang
> > Can you expend on your problem a bit?
> >
> > I have a dual Athlon system running FC3 (never ran FC2 on it
> > but FC1 did not have problems) and it experiences a solid
> > lockup at times (random events maybe once a week or so). The
> > system hard freezes and I have to do a hardware reset to get
> > it back up (cannot ssh into from another system).
>
> Sounds exactly like my problem, except it happens more often. I have three
> other machines identically configured at work, and they exhibit the same
> behavior (2 running FC 2, 1 running FC 3).
>
> And never had the problem on any with FC 1.
I have a dual Athlon that mysteriously locks up too. I've had hardware
problems with it in the past, but I thought I had it fixed with FC1 a
while ago, but then started having lockups again when I upgraded to FC3.
1) we need oopses to be able to debug this.
just 'it locks up' isn't too usefull
2) All the people seeing this are NOT using a binary only nvidia or ATI
video driver, right?
(those who do anyway PLEASE always mention that in your reports)
6:36 a.m.
-----Original Message-----
From: fedora-test-list-bounces(a)redhat.com
[mailto:fedora-test-list-bounces@redhat.com] On Behalf Of
Arjan van de Ven
1) we need oopses to be able to debug this.
just 'it locks up' isn't too usefull
2) All the people seeing this are NOT using a binary only
nvidia or ATI
video driver, right?
(those who do anyway PLEASE always mention that in your reports)
No, no special driver. And I would love to get an oops, or use a specially
instrumented kernel, or something.
I have had occasion to be able to ssh in to one of my machines at work while
it was "locked" but couldn't find anything obvious. Reports of such to the
fedora list weren't of interest to anyone.
I see nothing unusual in the messages log after a reboot.
Any debugging or test ideas would be gratefully accepted.
-Tom
7:33 a.m.
On 2004 12 31 (Friday) 14:36, Tom Browder wrote:
> -----Original Message-----
> From: fedora-test-list-bounces(a)redhat.com
> [mailto:fedora-test-list-bounces@redhat.com] On Behalf Of
> Arjan van de Ven
> 1) we need oopses to be able to debug this.
> just 'it locks up' isn't too usefull
> 2) All the people seeing this are NOT using a binary only
> nvidia or ATI
> video driver, right?
> (those who do anyway PLEASE always mention that in your reports)
No, no special driver. And I would love to get an oops, or use a specially
instrumented kernel, or something.
I have had occasion to be able to ssh in to one of my machines at work while
it was "locked" but couldn't find anything obvious. Reports of such to
the
fedora list weren't of interest to anyone.
I see nothing unusual in the messages log after a reboot.
Any debugging or test ideas would be gratefully accepted.
My PC (Athlon 2000+) with nVidia driver locks up sometimes, but I
did not pay attention (nVidia binary driver), but my friend with FC2
and latest kernel had such problem without any binary drivers these
days after update. At work, with P4 machines, I have no problem with
FC3 (one of them running with nVidia driver about a month). It is
strange that my PC sometimes locks in such a way, that the socks proxy
works (running on my locked PC), routing works, pings, but ssh and
httpd do not (ports open but no traffic). Sometimes there is disk
activity also, but nothing in the log files, and it's difficult to
guess because it happens 2-3 times a month...
So... what can I do? I don't need the nVidia driver (screen savers)
and don't care about any performance losses at home - personal apache
and postfix only. Any tips?
PS: Please do not reply this year, have some fun! ;-]
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79 http://pgp.mit.edu
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
2:28 p.m.
On Friday 31 December 2004 03:11, Arjan van de Ven wrote:
1) we need oopses to be able to debug this.
just 'it locks up' isn't too usefull
2) All the people seeing this are NOT using a binary only nvidia or ATI
video driver, right?
(those who do anyway PLEASE always mention that in your reports)
1. Gigabyte GA-7DPXDW+ mobo with dual Athlon 2800+ and 2GB ram.
2. ATI Radeon 9200 running the "standard" xorg-X11 radeon driver.
--
Gene
8:10 p.m.
Woops, just saw this reply. Missed it while on vacation I guess.
On Fri, Dec 31, 2004, Arjan van de Ven <arjanv(a)redhat.com> wrote:
On Thu, 2004-12-30 at 15:04 -0800, Johannes Erdfelt wrote:
> I have a dual Athlon that mysteriously locks up too. I've had hardware
> problems with it in the past, but I thought I had it fixed with FC1 a
> while ago, but then started having lockups again when I upgraded to FC3.
1) we need oopses to be able to debug this.
just 'it locks up' isn't too usefull
Yes, I know. I'll be placing a serial console on it soon to see if I can
get an oops from it.
2) All the people seeing this are NOT using a binary only nvidia or
ATI
video driver, right?
(those who do anyway PLEASE always mention that in your reports)
Nope. Not even running X. The machine is a headless server.
JE
2:06 p.m.
On Thu, Jan 06, 2005, Johannes Erdfelt <johannes(a)erdfelt.com> wrote:
On Fri, Dec 31, 2004, Arjan van de Ven <arjanv(a)redhat.com>
wrote:
> On Thu, 2004-12-30 at 15:04 -0800, Johannes Erdfelt wrote:
> > I have a dual Athlon that mysteriously locks up too. I've had hardware
> > problems with it in the past, but I thought I had it fixed with FC1 a
> > while ago, but then started having lockups again when I upgraded to FC3.
>
> 1) we need oopses to be able to debug this.
> just 'it locks up' isn't too usefull
Yes, I know. I'll be placing a serial console on it soon to see if I can
get an oops from it.
No oops this lockup unfortunately. I only saw this message on the console:
hde: dma_timer_expiry: dma status == 0x21
hde: DMA timeout error
The messages didn't make it to the log on disk. I am using md raid5, so
it should have been possible to get the message to disk without hde
working. I can't say for sure if the message occured at the same time as
the lockup, or sometime before.
This was with kernel 2.6.9-1.724_FC3smp. hde is a disk hanging off a
PDC20268 PCI card.
I'm going to try connecting a PS/2 mouse to see if that makes a
difference.
JE
7043
days inactive
7054
days old
13 comments
6 participants
participants (6)
-
Arjan van de Ven -
Doncho N. Gunchev -
Gene C. -
Johannes Erdfelt -
Scott A Phipps -
Tom Browder