public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leonid Mamtchenkov <leonid@francoudi.com>
To: Paul Cassella <pwc@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12.
Date: Thu, 29 Mar 2001 10:37:14 +0300	[thread overview]
Message-ID: <20010329103714.A31363@francoudi.com> (raw)
In-Reply-To: <Pine.SGI.3.96.1010328165432.10707A-100000@fsgi626.americas.sgi.com>
In-Reply-To: <Pine.SGI.3.96.1010328165432.10707A-100000@fsgi626.americas.sgi.com>; from pwc@sgi.com on Wed, Mar 28, 2001 at 05:08:36PM -0600

Hello Paul Cassella,

Once you wrote about "Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12.":
PC> [1.] One line summary of the problem:    
PC> Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12.

I have similar problem with 2.4.0, 2.4.1, 2.4.2.  I tried running -ac24,25,26
and 2.4.3-pre6 and I don't have any problems so far.

PC> [2.] Full description of the problem/report:
PC> I have had hangs under 2.4.2-ac18, -ac19, and -ac24, after uptimes of
PC> 36 hours, 12 hours, and 10 hours, respectively.  -ac12 has twice run
PC> for a week without crashing.  I didn't see anything in the later -ac
PC> changelogs that looks responsible, but I haven't actually tried them.

My uptimes were bigger, but each of them was 16 days + X hours (X being 0-20)

PC> All the crashes were under X.  The machine did not respond to pings,
PC> and no sysrq keys other than B worked; I didn't hear disk activity
PC> after S, and the disks weren't unmounted.  Nothing made it to the
PC> logs.  In the -ac19 crash, I had run at the console for about 12
PC> hours, and then started X; it crashed within 15 minutes.

I also have all these troubles under X.

PC> In the one crash that happened while I was at the console, X
PC> completely froze, and sound output stopped.  In the others, the
PC> monitor was in power-save mode and didn't wake up.

I had it twice.

PC> The hangs don't appear to be related to IO load or anything else I can
PC> think of besides X.  Each time, there was a distributed.net client
PC> running, and nothing else that was in any way intensive.  I don't
PC> believe any sort of updatedb or makewhatis was running during the
PC> crashes, and it never hung overnight when these jobs run.

No distributed.net client here ;)

PC> I ran with -ac12 with nearly 1300 lines of diff narrowed down from
PC> [...skip...]
PC> - i810, (Debian unstable) X 4.0.2, with DRI

I think that the problem might be somewhere he.  I am running i810, 
(RedHat 7...not original anymore :)) X 4.0.1.

PC> I'll be happy to try out patches, configuration changes, and other
PC> suggestions, but I won't be able to tell for three or four days
PC> whether or not it helped.

With regular uptime of 16 days I will be very slow responsive for the testing
phase, though I am willing to try too ;)

-- 
 Best regards,
 Leonid Mamtchenkov
 System Administrator


  parent reply	other threads:[~2001-03-29  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-28 23:08 Hangs under 2.4.2-ac{18,19,24} that do not happen under -ac12 Paul Cassella
2001-03-29  0:52 ` Paul Cassella
2001-03-29  4:10 ` Alan Cox
2001-03-29  4:55   ` Paul Cassella
2001-03-29  7:37 ` Leonid Mamtchenkov [this message]
2001-04-03 18:43 ` Paul Cassella

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010329103714.A31363@francoudi.com \
    --to=leonid@francoudi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pwc@sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox