New: VT switch causes system to lockup
A message that is not in the archive (sent off-list or not yet received): [email protected]/
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface).
Quoted 28 lines · On Thu, 11 Jun 2009 18:42:30 GMT [email protected] 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: [email protected] ReportedBy: [email protected] Regression: YesHi 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).
Quoted 6 lines
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
Quoted 2 lines · Andrew Morton
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.
Quoted 3 lines
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
------------------------------------------------------------------------------
Quoted 10 lines · Tobias Jakobi
Quoted 2 lines · Andrew Morton
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.
Quoted 5 lines
Quoted 5 lines
Perhaps you were using vesafb in 2.6.27 and you're now using uvesafb?
Quoted 9 lines
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
------------------------------------------------------------------------------
_______________________________________________
Linux-fbdev-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel