[Libdlo] Fedora 11 status report
bernie at berniethompson.com
Mon Nov 9 09:13:50 PST 2009
Took a quick look at the kernel oops. We obviously don't have people
running with debug kernels, since we hadn't seen that one -- clearly
still early days.
It looks like fbcon assumes that the fbdev driver under it will never
call a function that could sleep (that is, it will call the fbdev
driver while in interrupt context).
Unfortunately, none of the displaylink fbdev drivers are designed for
that constraint. Because they're unusual in that they've got another
complex subsystem under them (usb), it's not clear they can, without
queuing up the request for later execution. But this needs to be
looked into. Roberto, Jaya, others - anyone already thought this
So at least for the time being it looks like that workaround from the
last mail to disable fbcon is essential. But this should go on the
list of issues to deal with.
On Mon, Nov 9, 2009 at 8:19 AM, Bernie Thompson
<bernie at berniethompson.com> wrote:
> Hi Alexander,
> A temp workaround for that bug might be the steps at
> Best wishes,
> On Mon, Nov 9, 2009 at 7:40 AM, Alexander Todorov <atodorov at otb.bg> wrote:
>> Hi all,
>> I've started testing with UD-160-A device on latest Fedora 11. displaylink-mod
>> compiled without issues and works. The external display connected to the USB
>> dock goes green upon modprobe displaylink.
>> After reboot the system automatically loads the kernel module and recognizes the
>> hardware. While boot process is taking place the external monitor is showing the
>> same image as the main one.
>> Right after boot is complete and gdm starts I hit a kernel oops like this one:
>> My kernel is 2.6.30 and I've reported the oops via kerneloops-applet however
>> it's not visible from the website.
>> I'm off to compiling the xf86-driver-displaylink package which seems to work
>> only on Debian based systems for now.
>> Libdlo mailing list
>> Libdlo at lists.freedesktop.org
More information about the Libdlo