From: Jesper Juhl <jesper.juhl@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dave Jones <davej@codemonkey.org.uk>,
Dave Airlie <airlied@linux.ie>
Subject: Re: 2.6.15-mm1 - locks solid when starting KDE (EDAC errors)
Date: Fri, 6 Jan 2006 01:40:53 +0100 [thread overview]
Message-ID: <9a8748490601051640s5a384dddga46d8106442d10c@mail.gmail.com> (raw)
In-Reply-To: <20060105162714.6ad6d374.akpm@osdl.org>
On 1/6/06, Andrew Morton <akpm@osdl.org> wrote:
> Jesper Juhl <jesper.juhl@gmail.com> wrote:
> >
> > On 1/5/06, Andrew Morton <akpm@osdl.org> wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm1/
> > >
> > >
> > <!-- snip -->
> >
> > Hi Andrew,
> >
> > 2.6.15-mm1 seems to be working less than perfect on my box.
> >
>
> ahem...
>
Ohh well, that's why we have -mm :)
> > Everything seems to be fine in console mode, but once I start X and
> > then login and KDE starts, the box locks up solid while loading KDE
> > (dies every time at the exact same spot, the "Initializing
> > peripherals" stage on the KDE splash screen).
>
> Various people have reported DRM/AGP oopses when starting X. It's probably
> that.
>
> Could you try reverting git-agpgart.patch?
>
Just did. Reverted that one patch, then rebuild/reinstalled the kernel
(with the same .config) and booted it - no change. It still locks up
in the exact same spot.
X starts & runs fine (sort of) since I can play around at the kdm
login screen all I want, it's only once I actually login and KDE
proper starts that it locks up.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-01-06 0:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 23:52 Jesper Juhl
2006-01-05 23:56 ` Jesper Juhl
2006-01-06 0:27 ` Andrew Morton
2006-01-06 0:40 ` Jesper Juhl [this message]
2006-01-06 0:59 ` Andrew Morton
2006-01-06 1:04 ` Jesper Juhl
2006-01-07 0:25 ` Jesper Juhl
2006-01-07 0:28 ` Dave Jones
2006-01-07 0:40 ` Andrew Morton
2006-01-07 0:57 ` Dave Jones
2006-01-07 1:20 ` Jesper Juhl
2006-01-07 1:28 ` Jesper Juhl
2006-01-07 1:53 ` Grant Coady
2006-01-07 2:51 ` Jesper Juhl
2006-01-07 3:13 ` Andrew Morton
2006-01-07 3:19 ` Jesper Juhl
2006-01-07 3:53 ` Dave Jones
2006-01-06 13:46 ` Alan Cox
2006-01-07 1:12 ` Jesper Juhl
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=9a8748490601051640s5a384dddga46d8106442d10c@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®