public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: florin@iucha.net (Florin Iucha)
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Helge Hafting <helgehaf@aitel.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.37 won't run X?
Date: Sat, 21 Sep 2002 11:17:02 -0500	[thread overview]
Message-ID: <20020921161702.GA709@iucha.net> (raw)
In-Reply-To: <591884585.1032594816@[10.10.2.3]>

[-- Attachment #1: Type: text/plain, Size: 716 bytes --]

On Sat, Sep 21, 2002 at 07:53:37AM -0700, Martin J. Bligh wrote:
> > X won't start on 2.5.37, but works with 2.5.36
> > The screen goes black as usual, but then nothing else happens.
> > ssh'ing in from another machine shows XFree86 using 50% cpu,
> > i.e. one of the two cpu's in this machine.
> 
> Looks like Linus fixed this already in his BK tree ... want
> to grab that and see if it fixes your problem?

What changeset do you think fixed this?

Anyway, I grabbed ftp://nl.linux.org/pub/linux/bk2patch/tagged-to-head.v2.5 
and patched it in. Same result X eating 99% cpu time.

florin

-- 

"If it's not broken, let's fix it till it is."

41A9 2BDE 8E11 F1C5 87A6  03EE 34B3 E075 3B90 DFE4

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-09-21 16:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-21 10:10 2.5.37 won't run X? Helge Hafting
2002-09-21 13:41 ` Florin Iucha
2002-09-21 14:53 ` Martin J. Bligh
2002-09-21 16:17   ` Florin Iucha [this message]
2002-09-21 16:25     ` Martin J. Bligh
2002-09-21 18:59       ` Florin Iucha
2002-09-21 20:23         ` Andries Brouwer
2002-09-21 20:41           ` William Lee Irwin III
2002-09-22  4:30           ` William Lee Irwin III
2002-09-22  6:27             ` Florin Iucha
2002-09-23  4:56               ` Florin Iucha
2002-09-23  4:56                 ` William Lee Irwin III
2002-09-22 12:18             ` Andries Brouwer

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=20020921161702.GA709@iucha.net \
    --to=florin@iucha.net \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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