From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Dave Airlie <airlied@gmail.com>
Cc: Gerhard Pircher <gerhard_pircher@gmx.net>,
linux-kernel@vger.kernel.org, adaplas@gmail.com,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [2.6.25-rc6] possible regression: X server dying
Date: Thu, 24 Apr 2008 18:03:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0804241715320.7642@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.0804082256270.4987@axis700.grange>
On Tue, 8 Apr 2008, Guennadi Liakhovetski wrote:
> Hm, so looks like I'm not seeing some ghosts on mine either. 2.6.25-rc8
> xorg runs under etch, but enters a tight (no syscalls) loop woth 100% CPU
> load under lenny. A 2.6.24 based kernel works under both etch and lenny...
> Haven't had time to try to localize the problem. Glint xorg driver, DRM
> and AGP are off, CONFIG_FB_PM2=y.
Ok, here's more info. It DOES seem to be a regression. I spent half a day
yesterday trying to trace this down, with no success. Multiple bisect
attempts ended up with non-bootable kernels on the very first iteration.
Today I just wanted to post all possible logs / configs to Bugzilla and -
it "suddenly" worked... And the change that made it work was - I disabled
CONFIG_FB_PM2 in the kernel...
So, I think, this shall be qualified as a regression, although, I have no
idea where. pm2fb.c itself hasn't (effectively for little endian) changed
since 2.6.24. To make it visual
etch lenny
v2.6.24 works works
v2.6.25 works fails
/me thinks he should trade his ap400 to the Linux Kernel Testers Inc. for
LOTS of money.
Thanks
Guennadi
---
Guennadi Liakhovetski
parent reply other threads:[~2008-04-24 16:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.64.0804082256270.4987@axis700.grange>]
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=Pine.LNX.4.64.0804241715320.7642@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=adaplas@gmail.com \
--cc=airlied@gmail.com \
--cc=gerhard_pircher@gmx.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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