From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: bugzilla-daemon@bugzilla.kernel.org, liquid.acid@gmx.net,
Michal Januszewski <spock@gentoo.org>,
bugme-daemon@bugzilla.kernel.org, jb.faq@gmx.de
Subject: Re: [Bugme-new] [Bug 13509] New: VT switch causes system to lockup
Date: Thu, 11 Jun 2009 16:04:24 -0700 [thread overview]
Message-ID: <20090611160424.fd597dce.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-13509-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Thu, 11 Jun 2009 18:42:30 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13509
>
> Summary: VT switch causes system to lockup
> Product: Drivers
> Version: 2.5
> Kernel Version: 2.6.30-gentoo-r1
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Console/Framebuffers
> AssignedTo: jsimmons@infradead.org
> ReportedBy: liquid.acid@gmx.net
> Regression: Yes
>
>
> Hi there,
>
> I just updated my amd64 system from a 2.6.27 kernel to a fresh 2.6.30-gentoo-r1
> one. The system boots fine, but as soon as I switch to another VT the whole
> system lockups.
>
> The screen just freezes, still showing the old content of VT1. ACPI buttons
> don't work, and ctrl-alt-del doesn't cause a restart. I haven't tried remote
> ssh login yet, nor magic SysRq (going to do this next).
>
> To emphasize this: Just doing work on the first console is perfectly fine - the
> system is rockstable this way. So it's not some instability that is triggered
> by the VT switch.
>
> Anyway, I'm using uvesafb here (gfx card is a integrated Radeon HD 3200).
> More informations to follow.
hm, 2.6.27->2.6.30 is a large hop.
Perhaps you were using vesafb in 2.6.27 and you're now using uvesafb?
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
next parent reply other threads:[~2009-06-11 23:05 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 ` Andrew Morton [this message]
2009-06-12 8:38 ` [Bugme-new] [Bug 13509] New: VT switch causes system to lockup Tobias Jakobi
2009-06-12 10:26 ` Jan Buecken
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=20090611160424.fd597dce.akpm@linux-foundation.org \
--to=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).