public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* All processes hung under 2.4.3
@ 2001-04-08 19:41 Steven Walter
  2001-04-08 21:09 ` Disconnect
  0 siblings, 1 reply; 2+ messages in thread
From: Steven Walter @ 2001-04-08 19:41 UTC (permalink / raw)
  To: linux-kernel

Earlier today, I tried to unlock xscreensaver on my desktop.  After
typing in the password, it said "Checking..." and then hung.  In
response, I hit Ctrl+Alt+Bksp, which killed X.  However, gdm did not
restart X.  I tried logging in on the console, but none of them were
responsive; characters would echo, but nothing else.

In hopes of finding the problem, I entered kdb, and did a bta.  All
processes were hung in exactly the same spot, schedule+0x268!  This code
is as follows:

0xc0110d50 <schedule+252>:	jne    0xc0110d7e <schedule+298>
0xc0110d52 <schedule+254>:	test   %eax,%eax
0xc0110d54 <schedule+256>:	jne    0xc0110d72 <schedule+286>
0xc0110d56 <schedule+258>:	mov    0xffffffe4(%ecx),%edx
0xc0110d59 <schedule+261>:	test   %edx,%edx
0xc0110d5b <schedule+263>:	je     0xc0110d7e <schedule+298>
0xc0110d5d <schedule+265>:	mov    0xfffffff0(%ecx),%eax
0xc0110d60 <schedule+268>:	cmp    0xfffffff0(%ebp),%eax
0xc0110d63 <schedule+271>:	je     0xc0110d69 <schedule+277>
0xc0110d65 <schedule+273>:	test   %eax,%eax
0xc0110d67 <schedule+275>:	jne    0xc0110d6a <schedule+278>
0xc0110d69 <schedule+277>:	inc    %edx
0xc0110d6a <schedule+278>:	add    $0x14,%edx
0xc0110d6d <schedule+281>:	sub    0x24(%esi),%edx
0xc0110d70 <schedule+284>:	jmp    0xc0110d7e <schedule+298>

Additionally, I did a "ps" in kdb and found dozens of "cron" and "sh"
started.  I suspect that these processes were somehow related to the
lockup, as the machine should've been idle for hours, and no cron jobs
were scheduled for the time.

The captured "bta" is availible if anyone is interested.  I don't know
of a way to reproduce this offhand.
-- 
-Steven
Freedom is the freedom to say that two plus two equals four.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: All processes hung under 2.4.3
  2001-04-08 19:41 All processes hung under 2.4.3 Steven Walter
@ 2001-04-08 21:09 ` Disconnect
  0 siblings, 0 replies; 2+ messages in thread
From: Disconnect @ 2001-04-08 21:09 UTC (permalink / raw)
  To: Steven Walter; +Cc: linux-kernel

Althought I was unable to do any debugging, I found the same thing earlier
today.  Syslog showed everything normal (uptimed reports, MARK, etc) and
ctrl-sysrq worked, but it had frozen hard.  I was using xlock, and it was
stopped in the middle of an opengl saver.  I had suspected it was related
to the nvidia drivers (I just got AGP enabled yesterday) but this looks a
lot like what I was seeing.

(On a side note, does anyone know if the K7 optimizations have been fixed
for those of us using the KK266 mobo?)

On Sun, 08 Apr 2001, Steven Walter did have cause to say:

> Earlier today, I tried to unlock xscreensaver on my desktop.  After
> typing in the password, it said "Checking..." and then hung.  In
> response, I hit Ctrl+Alt+Bksp, which killed X.  However, gdm did not
> restart X.  I tried logging in on the console, but none of them were
> responsive; characters would echo, but nothing else.
> 
> In hopes of finding the problem, I entered kdb, and did a bta.  All
> processes were hung in exactly the same spot, schedule+0x268!  This code
> is as follows:
> 
> 0xc0110d50 <schedule+252>:	jne    0xc0110d7e <schedule+298>
> 0xc0110d52 <schedule+254>:	test   %eax,%eax
> 0xc0110d54 <schedule+256>:	jne    0xc0110d72 <schedule+286>
> 0xc0110d56 <schedule+258>:	mov    0xffffffe4(%ecx),%edx
> 0xc0110d59 <schedule+261>:	test   %edx,%edx
> 0xc0110d5b <schedule+263>:	je     0xc0110d7e <schedule+298>
> 0xc0110d5d <schedule+265>:	mov    0xfffffff0(%ecx),%eax
> 0xc0110d60 <schedule+268>:	cmp    0xfffffff0(%ebp),%eax
> 0xc0110d63 <schedule+271>:	je     0xc0110d69 <schedule+277>
> 0xc0110d65 <schedule+273>:	test   %eax,%eax
> 0xc0110d67 <schedule+275>:	jne    0xc0110d6a <schedule+278>
> 0xc0110d69 <schedule+277>:	inc    %edx
> 0xc0110d6a <schedule+278>:	add    $0x14,%edx
> 0xc0110d6d <schedule+281>:	sub    0x24(%esi),%edx
> 0xc0110d70 <schedule+284>:	jmp    0xc0110d7e <schedule+298>
> 
> Additionally, I did a "ps" in kdb and found dozens of "cron" and "sh"
> started.  I suspect that these processes were somehow related to the
> lockup, as the machine should've been idle for hours, and no cron jobs
> were scheduled for the time.
> 
> The captured "bta" is availible if anyone is interested.  I don't know
> of a way to reproduce this offhand.
> -- 
> -Steven
> Freedom is the freedom to say that two plus two equals four.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
---
   _.-=<Disconnect>=-._
|     dis@sigkill.net    | And Remember...
\  shawn@healthcite.com  / He who controls Purple controls the Universe..
 PGP Key given on Request  Or at least the Purple parts!

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1 [www.ebb.org/ungeek]
GIT/CC/CM/AT d--(-)@ s+:-- a-->? C++++$ ULBS*++++$ P+>+++ L++++>+++++ 
E--- W+++ N+@ o+>$ K? w--->+++++ O- M V-- PS+() PE Y+@ PGP++() t 5--- 
X-- R tv+@ b++++>$ DI++++ D++(+++) G++ e* h(-)* r++ y++
------END GEEK CODE BLOCK------

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-04-08 21:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-04-08 19:41 All processes hung under 2.4.3 Steven Walter
2001-04-08 21:09 ` Disconnect

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox