attaching USB DisplayLink device procuded oops in dmesg

Bug #519799 reported by Oliver Grawert
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Lucid
Expired
Undecided
Unassigned

Bug Description

plugging an ArkView usb -> VGA/HDMI/DVI display adapter in with the recent lucid archive kernel produces an oops in dmesg.

Revision history for this message
Oliver Grawert (ogra) wrote :
Download full text (9.0 KiB)

[220382.292065] usb 2-2: new high speed USB device using ehci_hcd and address 7
[220382.428036] usb 2-2: configuration #1 chosen from 1 choice
[220382.448684] udlfb: module is from the staging directory, the quality is unknown, you have been warned.
[220382.451245] DisplayLink device attached
[220382.451449] ret control msg 0: 4 0500fffffff0
[220382.531582] EDID XRES 1920 YRES 1200
[220382.531589] INIT VIDEO 0 800 480
[220382.531593] INIT VIDEO 1 1024 768
[220382.531597] INIT VIDEO 2 1280 1024
[220382.531601] INIT VIDEO 3 1400 1050
[220382.531605] INIT VIDEO 0 800 480
[220382.531609] INIT VIDEO 1 1024 768
[220382.531613] INIT VIDEO 2 1280 1024
[220382.533225] ret control msg 1 (STD_CHANNEL): 16
[220382.533322] ret bulk 2: 156 156
[220382.533443] ret bulk 3: 0
[220382.533447] found valid mode...6493
[220382.535023] screen base allocated !!!
[220382.541190] modprobe: page allocation failure. order:10, mode:0xc0d0
[220382.541200] Pid: 5868, comm: modprobe Tainted: G C 2.6.32-12-generic-pae #17-Ubuntu
[220382.541206] Call Trace:
[220382.541223] [<c05bbc3b>] ? printk+0x1d/0x22
[220382.541236] [<c01cf46e>] __alloc_pages_slowpath+0x46e/0x4a0
[220382.541245] [<c01cf5da>] __alloc_pages_nodemask+0x13a/0x170
[220382.541253] [<c01cf62c>] __get_free_pages+0x1c/0x30
[220382.541261] [<c01ff3d6>] __kmalloc+0xe6/0x190
[220382.541269] [<c01eed35>] ? vmalloc_to_page+0xe5/0x150
[220382.541280] [<f87b171c>] dlfb_probe+0x2bc/0x4e4 [udlfb]
[220382.541290] [<c04718d0>] usb_probe_interface+0xc0/0x180
[220382.541298] [<c0261047>] ? sysfs_create_link+0x17/0x20
[220382.541307] [<c03e7845>] really_probe+0x55/0x150
[220382.541316] [<c03edc2e>] ? pm_runtime_barrier+0x4e/0xc0
[220382.541323] [<c03e797c>] driver_probe_device+0x3c/0x60
[220382.541330] [<c03e7a21>] __driver_attach+0x81/0x90
[220382.541337] [<c03e6e53>] bus_for_each_dev+0x53/0x80
[220382.541344] [<c03e770e>] driver_attach+0x1e/0x20
[220382.541350] [<c03e79a0>] ? __driver_attach+0x0/0x90
[220382.541357] [<c03e70d5>] bus_add_driver+0xd5/0x280
[220382.541364] [<c03e7d1a>] driver_register+0x6a/0x120
[220382.541372] [<c01aa3e6>] ? ftrace_update_code+0x86/0xf0
[220382.541380] [<f87b0011>] ? dlfb_setcolreg+0x11/0x90 [udlfb]
[220382.541388] [<c0470e01>] usb_register_driver+0x81/0xf0
[220382.541395] [<c01a8087>] ? tracepoint_module_notify+0x27/0x30
[220382.541404] [<f829d1a7>] dlfb_init+0x1a7/0x1d0 [udlfb]
[220382.541411] [<c0101131>] do_one_initcall+0x31/0x190
[220382.541419] [<f829d000>] ? dlfb_init+0x0/0x1d0 [udlfb]
[220382.541426] [<c0182850>] sys_init_module+0xb0/0x210
[220382.541434] [<c010344c>] syscall_call+0x7/0xb
[220382.541439] Mem-Info:
[220382.541443] DMA per-cpu:
[220382.541447] CPU 0: hi: 0, btch: 1 usd: 0
[220382.541452] CPU 1: hi: 0, btch: 1 usd: 0
[220382.541455] Normal per-cpu:
[220382.541459] CPU 0: hi: 186, btch: 31 usd: 0
[220382.541464] CPU 1: hi: 186, btch: 31 usd: 0
[220382.541468] HighMem per-cpu:
[220382.541472] CPU 0: hi: 186, btch: 31 usd: 0
[220382.541476] CPU 1: hi: 186, btch: 31 usd: 0
[220382.541486] active_anon:210328 inactive_anon:50225 isolated_anon:390
[220382.541488] active_file:176582 inactive_file:...

Read more...

Revision history for this message
Oliver Grawert (ogra) wrote :
Revision history for this message
Oliver Grawert (ogra) wrote :

whoops, sorry disregard the last comment, it's actually: http://www.arkview.com/eshop/goods.php?id=18

tags: added: kernel-series-unknown
Revision history for this message
Mark Cariaga (mzc) wrote : Re: [Bug 519799] Re: attaching USB DisplayLink device procuded oops in dmesg

The bug applies to all displaylink certified usb diaplay adapter. Mine
is a diamond bvu195

On Mar 10, 2010, at 12:44 PM, Jeremy Foshee
<email address hidden> wrote:

> ** Tags added: kernel-series-unknown
>
> --
> attaching USB DisplayLink device procuded oops in dmesg
> https://bugs.launchpad.net/bugs/519799
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
> Status in “linux” source package in Lucid: New
>
> Bug description:
> plugging an ArkView usb -> VGA/HDMI/DVI display adapter in with the
> recent lucid archive kernel produces an oops in dmesg.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/519799/+subscribe

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Oliver,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 519799

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 519799

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Lucid):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Lucid) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Lucid):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.