Bug 10666 - cfag12864bfb messing up vc on load
Summary: cfag12864bfb messing up vc on load
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Console/Framebuffers (show other bugs)
Hardware: All Linux
: P1 low
Assignee: James Simmons
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-11 05:10 UTC by Roland Kletzing
Modified: 2010-02-16 16:00 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.21+
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Roland Kletzing 2008-05-11 05:10:41 UTC
Latest working kernel version: n/a

Earliest failing kernel version: at least 2.6.21

Distribution: opensuse 10.3

Hardware Environment: vmware

Software Environment: opensuse 10.3 + kernel 2.6.26rc1

Problem Description:
when doing some module regression testing (load/unload most available modules), cfag12864bfb driver always kills the local console on load and locks you out. visible area of vc shrinks to 16x4 and output freezing. this happens if you don`t have appropriate hardware attached, cannot test with hw attached (don`t own such). no vc switching afterwards. cannot unload module from remote (ssh) either. need reboot.

Steps to reproduce:
save all of your important data, switch to textconsole, modprobe cfag12864bfb 

dmesg shows:
Console: switching to mono frame buffer device 16x8
fb0: cfag12864b frame buffer device

contacted the author who confirmed the issue and tells that this didn`t happen initially. iirc, he thinks this is a regression due to change in framebuffer layer. didn`t get a response since then, maybe he`s lacking time.
i`m putting it here so it`s being marked as a ToDo and won`t get lost.
Comment 1 Anonymous Emailer 2008-05-11 11:07:30 UTC
Reply-To: akpm@linux-foundation.org

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Sun, 11 May 2008 05:10:41 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=10666
> 
>            Summary: cfag12864bfb messing up vc on load
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.21+
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: low
>           Priority: P1
>          Component: Console/Framebuffers
>         AssignedTo: jsimmons@infradead.org
>         ReportedBy: devzero@web.de
> 
> 
> Latest working kernel version: n/a
> 
> Earliest failing kernel version: at least 2.6.21
> 
> Distribution: opensuse 10.3
> 
> Hardware Environment: vmware
> 
> Software Environment: opensuse 10.3 + kernel 2.6.26rc1
> 
> Problem Description:
> when doing some module regression testing (load/unload most available
> modules),
> cfag12864bfb driver always kills the local console on load and locks you out.
> visible area of vc shrinks to 16x4 and output freezing. this happens if you
> don`t have appropriate hardware attached, cannot test with hw attached (don`t
> own such). no vc switching afterwards. cannot unload module from remote (ssh)
> either. need reboot.
> 
> Steps to reproduce:
> save all of your important data, switch to textconsole, modprobe cfag12864bfb 
> 
> dmesg shows:
> Console: switching to mono frame buffer device 16x8
> fb0: cfag12864b frame buffer device
> 
> contacted the author who confirmed the issue and tells that this didn`t
> happen
> initially. iirc, he thinks this is a regression due to change in framebuffer
> layer. didn`t get a response since then, maybe he`s lacking time.
> i`m putting it here so it`s being marked as a ToDo and won`t get lost.
> 
> 
> -- 
> Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
Comment 2 Roland Kletzing 2008-10-31 05:40:51 UTC
apparently, i cannot reproduce this on 2.6.28-rc2-git3

as nothing appropriate changed in the driver code, there must be some change in the console/framebuffer-layer which has fixed that.
Comment 3 Miguel Ojeda Sandonis 2008-11-02 02:42:46 UTC
I tested long ago the driver at 2.6.25 (even sooner, but that is the first time I remember clearly) and it worked nicely again. I will perform a re-test on 2.6.27.

Roland Kletzing is right, the code hasn't changed since years ago (as far as I know), so maybe someone changed some fb layer behaviour for a couple of months?
Comment 4 James Simmons 2010-02-16 16:00:59 UTC
It appears to have been resolved

Note You need to log in before you can comment on or make changes to this bug.