From: Jan Buecken <jbuecken@gmx.de>
To: Tobias Jakobi <liquid.acid@gmx.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
bugzilla-daemon@bugzilla.kernel.org,
Michal Januszewski <spock@gentoo.org>,
bugme-daemon@bugzilla.kernel.org, jb.faq@gmx.de,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 13509] New: VT switch causes system to lockup
Date: Fri, 12 Jun 2009 12:26:56 +0200 [thread overview]
Message-ID: <4A322D70.50702@gmx.de> (raw)
In-Reply-To: <4A321414.20703@gmx.net>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
Tobias Jakobi schrieb:
> Andrew Morton wrote:
>
>> hm, 2.6.27->2.6.30 is a large hop.
>>
> Hi Andrew!
>
> Yeah, I know. I was going to build a 2.6.29 though, since the fglrx
> driver seems to have some problems with the 30 one.
> I'm going to check then if the problem also occurs with 29.
>
I used the 29 before with uvesafb: There it was not a problem.
Seems to be a regression between 29 and 30.
>
>
>> Perhaps you were using vesafb in 2.6.27 and you're now using uvesafb?
>>
>>
> Nope, I can assure you that. :)
> The 27 kernel has uvesafb activated and is also using it. In fact I just
> used make oldconfig to port the 27 config over to 30 (I'm not using any
> distro tools for kernel compiling, just plain make).
>
> Greets,
> Tobias
>
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
[-- Attachment #2: Type: text/plain, Size: 79 bytes --]
------------------------------------------------------------------------------
[-- Attachment #3: Type: text/plain, Size: 182 bytes --]
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
prev parent reply other threads:[~2009-06-12 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13509-10286@http.bugzilla.kernel.org/>
2009-06-11 23:04 ` [Bugme-new] [Bug 13509] New: VT switch causes system to lockup Andrew Morton
2009-06-12 8:38 ` Tobias Jakobi
2009-06-12 10:26 ` Jan Buecken [this message]
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=4A322D70.50702@gmx.de \
--to=jbuecken@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=jb.faq@gmx.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=liquid.acid@gmx.net \
--cc=spock@gentoo.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;
as well as URLs for NNTP newsgroup(s).