[Bug 709440] New: BUG: unable to handle kernel NULL pointer dereference at (null)
https://bugzilla.novell.com/show_bug.cgi?id=709440 https://bugzilla.novell.com/show_bug.cgi?id=709440#c0 Summary: BUG: unable to handle kernel NULL pointer dereference at (null) Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: markus_stephan@freenet.de QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=443321) --> (http://bugzilla.novell.com/attachment.cgi?id=443321) dmesg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 after upgrading to kernel 3.0 from tumbleweed my DVB-S USB-Box stopped working. .. [ 6.365094] dvb-usb: downloading firmware from file 'dvb-usb-vp702x-02.fw' [ 6.381329] dvb-usb: found a 'TwinhanDTV StarBox DVB-S USB2.0 (VP7021)' in warm state. [ 6.381340] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 6.381468] DVB: registering new adapter (TwinhanDTV StarBox DVB-S USB2.0 (VP7021)) [ 6.381856] BUG: unable to handle kernel NULL pointer dereference at (null) [ 6.382125] IP: [<ffffffff8158ae3d>] __mutex_lock_slowpath+0xad/0x1b0 [ 6.382337] PGD 6aec5067 PUD 6aeb2067 PMD 0 [ 6.382435] Oops: 0002 [#1] PREEMPT SMP [ 6.382435] CPU 1 [ 6.382435] Modules linked in: arc4 dvb_usb_vp702x(+) dvb_usb dvb_core joydev snd_hda_codec_realtek snd_hda_intel(+) snd_hda_codec ir_lirc_codec lirc_dev snd_hwdep ir_sony_decoder snd_pcm ir_jvc_decoder ir_rc6_decoder sp5100_tco ath5k sr_mod ir_rc5_decoder i2c_piix4 edac_core k8temp snd_timer r8169 edac_mce_amd cdrom sg ath ir_nec_decoder rc_rc6_mce firewire_ohci ite_cir firewire_core rc_core snd mac80211 cfg80211 serio_raw pcspkr soundcore button snd_page_alloc rfkill shpchp pci_hotplug crc_itu_t radeon ttm drm_kms_helper i2c_algo_bit drm fan thermal processor thermal_sys ata_generic pata_atiixp [ 6.382435] [ 6.382435] Pid: 608, comm: modprobe Not tainted 3.0.0-38-desktop #1 Acer Aspire L5100/FRS690L [ 6.382435] RIP: 0010:[<ffffffff8158ae3d>] [<ffffffff8158ae3d>] __mutex_lock_slowpath+0xad/0x1b0 [ 6.382435] RSP: 0018:ffff88006b4d3bb0 EFLAGS: 00010246 [ 6.382435] RAX: 0000000000000000 RBX: ffff8800377a8e80 RCX: 0000000000000a7b [ 6.382435] RDX: ffff88006b4d3bc0 RSI: ffff88006b9ed148 RDI: ffff8800377a8e84 [ 6.382435] RBP: ffff8800377a8e84 R08: 0000000000000000 R09: 000000000000000a [ 6.386040] R10: 0000000000000000 R11: 0000000000000003 R12: 00000000ffffffff [ 6.386040] R13: 0000000000000001 R14: ffff880068f7a080 R15: ffff8800377a8e88 [ 6.386040] FS: 00007fef6e82e700(0000) GS:ffff88006fc80000(0000) knlGS:0000000000000000 [ 6.386040] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 6.386040] CR2: 0000000000000000 CR3: 000000006ad35000 CR4: 00000000000006e0 [ 6.386040] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 6.386040] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 6.386040] Process modprobe (pid: 608, threadinfo ffff88006b4d2000, task ffff880068f7a080) [ 6.386040] Stack: [ 6.386040] 0000000000000000 ffff88006c09b088 ffff8800377a8e88 0000000000000000 [ 6.386040] ffffffff81589501 ffff880000000010 ffff88006b4d3c38 ffff8800377a8e80 [ 6.386040] ffff88006b9ed118 ffff88006b9ec000 ffff88006b9ed0a8 ffff8800377a8e80 [ 6.386040] Call Trace: [ 6.386040] [<ffffffff8158aa6a>] mutex_lock+0x1a/0x40 [ 6.386040] [<ffffffffa039f259>] vp702x_read_mac_addr+0x39/0xb0 [dvb_usb_vp702x] [ 6.386040] [<ffffffffa045a274>] dvb_usb_adapter_dvb_init+0x84/0x1b0 [dvb_usb] [ 6.386040] [<ffffffffa0459723>] dvb_usb_adapter_init+0x103/0x2f0 [dvb_usb] [ 6.386040] [<ffffffffa0459a0d>] dvb_usb_init+0x9d/0x110 [dvb_usb] [ 6.386040] [<ffffffffa0459b82>] dvb_usb_device_init+0x102/0x1b0 [dvb_usb] [ 6.386040] [<ffffffffa039f0a5>] vp702x_usb_probe+0x35/0xb0 [dvb_usb_vp702x] [ 6.386040] [<ffffffff813ee302>] usb_probe_interface+0x142/0x270 [ 6.386040] [<ffffffff8138ff30>] really_probe+0x70/0x230 [ 6.403006] [<ffffffff813902f7>] driver_probe_device+0x47/0xb0 [ 6.403006] [<ffffffff813903f3>] __driver_attach+0x93/0xa0 [ 6.403006] [<ffffffff8138f03e>] bus_for_each_dev+0x4e/0x80 [ 6.403006] [<ffffffff8138f948>] bus_add_driver+0x148/0x280 [ 6.403006] [<ffffffff8139098a>] driver_register+0x6a/0x130 [ 6.403006] [<ffffffff813ed56a>] usb_register_driver+0xaa/0x160 [ 6.403006] [<ffffffffa000d01b>] vp702x_usb_module_init+0x1b/0x1000 [dvb_usb_vp702x] [ 6.403006] [<ffffffff810002ea>] do_one_initcall+0x3a/0x180 [ 6.403006] [<ffffffff8109a78e>] sys_init_module+0xce/0x240 [ 6.403006] [<ffffffff81593892>] system_call_fastpath+0x16/0x1b [ 6.403006] [<00007fef6e189d2a>] 0x7fef6e189d29 [ 6.403006] Code: 6b 04 4c 8d 7b 08 41 bc ff ff ff ff 48 89 ef e8 aa 18 00 00 48 8b 43 10 48 8d 54 24 10 4c 89 7c 24 10 48 89 53 10 48 89 44 24 18 [ 6.403006] 89 10 44 89 e0 4c 89 74 24 20 87 03 83 f8 01 74 58 44 89 e0 [ 6.403006] RIP [<ffffffff8158ae3d>] __mutex_lock_slowpath+0xad/0x1b0 [ 6.403006] RSP <ffff88006b4d3bb0> [ 6.403006] CR2: 0000000000000000 [ 6.403652] ---[ end trace ac58cc78bbecb347 ]--- Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c2
--- Comment #2 from Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c3
Jiri Slaby
unfortunately it's not applied to stable yet.
Yes, the bug was not accepted upstream yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c4
--- Comment #4 from Jiri Slaby
the bug
I mean the *patch*. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c5
--- Comment #5 from Markus Stephan
(In reply to comment #3)
the bug
I mean the *patch*.
Could it be applied to the tumbleweed kernel tree? So i could test and report back, as the author doesn't have the hardware for testing. Or Could you revert the broken 3.0 patches back to the 2.6.39 version of this driver for further tumbleweed kernels until fixed upstream? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c6
Jiri Slaby
(In reply to comment #4)
(In reply to comment #3)
the bug
I mean the *patch*.
Could it be applied to the tumbleweed kernel tree?
No, I won't apply patches which are not upstream yet, sorry. (Unless they are about security.) And DVB tree is sometimes slow to propagate :(.
So i could test and report back, as the author doesn't have the hardware for testing.
I can build you a kernel for testing, if you want.
Could you revert the broken 3.0 patches back to the 2.6.39 version of this driver for further tumbleweed kernels until fixed upstream?
I don't think so. Hopefully it won't be that long before it gets upstream. You can branch kernel:stable project to the revision just before 3.0 update, if you want. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c7
--- Comment #7 from Markus Stephan
(In reply to comment #5)
(In reply to comment #4)
(In reply to comment #3)
the bug
I mean the *patch*.
Could it be applied to the tumbleweed kernel tree?
No, I won't apply patches which are not upstream yet, sorry. (Unless they are about security.) And DVB tree is sometimes slow to propagate :(.
So i could test and report back, as the author doesn't have the hardware for testing.
I can build you a kernel for testing, if you want.
Yes, that would be great. I'm using the x86_64 desktop tumbleweed version.
Could you revert the broken 3.0 patches back to the 2.6.39 version of this driver for further tumbleweed kernels until fixed upstream?
I don't think so. Hopefully it won't be that long before it gets upstream. You can branch kernel:stable project to the revision just before 3.0 update, if you want.
I don't understand what you mean with "branch kernel:stable project". Can you give an example to me? Thank you -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c
Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c8
--- Comment #8 from Jiri Slaby
Yes, that would be great. I'm using the x86_64 desktop tumbleweed version.
It will appear at: http://download.opensuse.org/repositories/home:/jirislaby:/vp702x/standard/
I don't understand what you mean with "branch kernel:stable project". Can you give an example to me?
osc branch or osc linkpac with -r switch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c9
--- Comment #9 from Jiri Slaby
(In reply to comment #7)
Yes, that would be great. I'm using the x86_64 desktop tumbleweed version.
It will appear at: http://download.opensuse.org/repositories/home:/jirislaby:/vp702x/standard/
It's there. This patch is needed to build properly though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c10
--- Comment #10 from Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c11
Markus Stephan
It will appear at: http://download.opensuse.org/repositories/home:/jirislaby:/vp702x/standard/
I downloaded and installed the test kernel but unfortunately the patch did not fix the problem. The BUG seams to be now after the initialization phase of the driver: .. [ 21.042793] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found [ 21.458347] r8169 0000:03:00.0: eth0: link up [ 21.459145] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 32.314029] eth0: no IPv6 routers present [ 39.501763] BUG: unable to handle kernel NULL pointer dereference at (null) [ 39.501775] IP: [<ffffffff8158b9ed>] __mutex_lock_slowpath+0xad/0x1b0 [ 39.501786] PGD 37b63067 PUD 6a09f067 PMD 0 [ 39.501792] Oops: 0002 [#1] PREEMPT SMP [ 39.501797] CPU 0 [ 39.501799] Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 mperf fuse dm_mod snd_hda_codec_hdmi snd_hda_codec_realtek dvb_usb_vp702x dvb_usb dvb_core arc4 ir_lirc_codec lirc_dev joydev snd_hda_intel ir_sony_decoder ir_jvc_decoder sr_mod ir_rc6_decoder r8169 snd_hda_codec rc_rc6_mce ir_rc5_decoder firewire_ohci snd_hwdep snd_pcm ath5k firewire_core sg edac_core cdrom edac_mce_amd sp5100_tco i2c_piix4 ite_cir ir_nec_decoder rc_core k8temp pcspkr ath snd_timer shpchp snd pci_hotplug serio_raw mac80211 cfg80211 soundcore rfkill snd_page_alloc button crc_itu_t radeon ttm drm_kms_helper i2c_algo_bit drm fan thermal processor thermal_sys ata_generic pata_atiixp [ 39.501868] [ 39.501871] Pid: 2373, comm: mythbackend Not tainted 3.0.3-1-desktop #1 Acer Aspire L5100/FRS690L [ 39.501879] RIP: 0010:[<ffffffff8158b9ed>] [<ffffffff8158b9ed>] __mutex_lock_slowpath+0xad/0x1b0 [ 39.501887] RSP: 0018:ffff880037b87bf0 EFLAGS: 00010246 [ 39.501890] RAX: 0000000000000000 RBX: ffff880068fd9800 RCX: ffff88006b8f8007 [ 39.501895] RDX: ffff880037b87c00 RSI: 0000000000000001 RDI: ffff880068fd9804 [ 39.501899] RBP: ffff880068fd9804 R08: 00000000007cacd0 R09: 0000000000000002 [ 39.501903] R10: 00007ffff5928a60 R11: 0000000000000246 R12: 00000000ffffffff [ 39.501908] R13: 0000000000000001 R14: ffff880069fd2800 R15: ffff880068fd9808 [ 39.501913] FS: 00007f81de79f760(0000) GS:ffff88006fc00000(0000) knlGS:0000000000000000 [ 39.501918] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 39.501921] CR2: 0000000000000000 CR3: 0000000037b32000 CR4: 00000000000006f0 [ 39.501926] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 39.501931] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 39.501935] Process mythbackend (pid: 2373, threadinfo ffff880037b86000, task ffff880069fd2800) [ 39.501940] Stack: [ 39.501942] 0000000100000001 0000000000000001 ffff880068fd9808 0000000000000000 [ 39.501949] 0000000000000286 0000000000000001 00000000000000c3 ffff880068fd9800 [ 39.501955] ffff88006b8f8000 0000000000000001 ffff8800378b1c00 00000000ffffffa1 [ 39.501961] Call Trace: [ 39.501973] [<ffffffff8158b61a>] mutex_lock+0x1a/0x40 [ 39.501982] [<ffffffffa03ff9d7>] vp702x_fe_set_voltage+0x57/0xa0 [dvb_usb_vp702x] [ 39.502006] [<ffffffffa03ec8c6>] dvb_frontend_ioctl_legacy+0x516/0xa10 [dvb_core] [ 39.502008] [<ffffffffa03ed64a>] dvb_frontend_ioctl+0x11a/0x140 [dvb_core] [ 39.502008] [<ffffffffa03e2ab7>] dvb_usercopy+0xb7/0x1b0 [dvb_core] [ 39.502008] [<ffffffffa03e2be0>] dvb_generic_ioctl+0x30/0x40 [dvb_core] [ 39.502008] [<ffffffff8116efc4>] do_vfs_ioctl+0x84/0x2d0 [ 39.502008] [<ffffffff8116f2a8>] sys_ioctl+0x98/0xa0 [ 39.502008] [<ffffffff81594452>] system_call_fastpath+0x16/0x1b [ 39.502008] [<00007f81da5dbce7>] 0x7f81da5dbce6 [ 39.502008] Code: 6b 04 4c 8d 7b 08 41 bc ff ff ff ff 48 89 ef e8 aa 18 00 00 48 8b 43 10 48 8d 54 24 10 4c 89 7c 24 10 48 89 53 10 48 89 44 24 18 [ 39.502008] 89 10 44 89 e0 4c 89 74 24 20 87 03 83 f8 01 74 58 44 89 e0 [ 39.502008] RIP [<ffffffff8158b9ed>] __mutex_lock_slowpath+0xad/0x1b0 [ 39.502008] RSP <ffff880037b87bf0> [ 39.502008] CR2: 0000000000000000 [ 39.502154] ---[ end trace 684f0ea49186916b ]--- [ 39.502162] note: mythbackend[2373] exited with preempt_count 2 I will send a report to the author of the patch. Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c12
--- Comment #12 from Markus Stephan
Hi Florian,
I'm using OpenSuse 11.4 with the tumbleweed kernel 3.0, unfortunately my DVB-USB Box stopped working with this kernel.
I goggled and found your patch at: https://patchwork.kernel.org/patch/1029612/
Jiri Slaby from OpenSuse build a testing kernel for me with your patch applied, but the patch did not fix the problem, please have a look at:
https://bugzilla.novell.com/show_bug.cgi?id=709440
Thank you, Markus Stephan
Hi Markus! Thanks for testing that patch. Here is a fixup to it. Can you give that a try? It's not the final answer (the naming of the functions sucks) but should work (tm). (I forgot to fix up the usb_inout_op call sites in the vp702x-fe.c file and thus the buf_mutex was not initialized. With the attached patch applied, everything should work.) Maybe Jiri can whip another kernel up for you to test? Regards, Flo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c13
--- Comment #13 from Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c14
Jiri Slaby
Maybe Jiri can whip another kernel up for you to test?
Yes, it's there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c15
Markus Stephan
(In reply to comment #12)
Maybe Jiri can whip another kernel up for you to test?
Yes, it's there.
The test kernel did fix the BUG for me, the DVB-S USB-Box is working again. Hope to see the patch + fixup in stable soon. Thank you for building the test kernels! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c16
--- Comment #16 from Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c17
--- Comment #17 from Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c18
--- Comment #18 from Markus Stephan
Ok, I just submitted the patch to linux-media. You might want to retest it though, maybe I did some silly mistake...
Regarding the messages, can you turn on debugging in vp702x (modprobing it with module param debug 3 ) after applying this patch?
It will show where the device is not responding. I guess it's a problem in the protocol implementation, which is hard to fix without hw-specs. But let's see what that debugging turns up.
Regards, Flo
Final patch from Florian + debug patch for diagnosing annoying: vp702x: usb in operation failed. (-110) error messages. Maybe you could find some time for building an other test kernel for me ... Thank you, Markus Stephan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c19
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c20
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c21
Markus Stephan
Hi Florian,
Jiri made an other test kernel for me with your final + debug patch applied.
The box works fine and the message: vp702x: usb in operation failed. (-110)
seams to be triggered by: vp702x_fe_set_frontend+0x156/0x1a0 [dvb_usb_vp702x]
Full dmesg is attached.
Thank you, Markus Stephan
Hi! Here is a patch to check if that failing op is even necessary.
But even if it works I don't feel comfortable of suggesting this to be applied, since I don't have any overview about the hardware supported by this driver. Maybe Patrick has any opinion on this, he wrote this driver after all :)
Regards, Flo
Final patch works fine, debug patch turns out that the function: vp702x_fe_set_frontend() is the source of the: vp702x: usb in operation failed. (-110) error message storm. Florian made a patch to test if this failing usb in op is necessary on my box. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c22
--- Comment #22 from Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c23
--- Comment #23 from Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c24
Jiri Slaby
If you could find some time for building an other test kernel for me, i will report the testing results to Florian.
It's building at the usual place now... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c25
Markus Stephan
(In reply to comment #23)
If you could find some time for building an other test kernel for me, i will report the testing results to Florian.
It's building at the usual place now...
It did not show up ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c26
Jiri Slaby
It did not show up ...
Yes, due to build error. As this is the second time, ask him to provide you with patches that don't cause build errors. It's (hopefully) fixed and building now at the usual place. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c27
Markus Stephan
(In reply to comment #25)
It did not show up ...
Yes, due to build error. As this is the second time, ask him to provide you with patches that don't cause build errors. It's (hopefully) fixed and building now at the usual place.
No, it did not build ...
Hi Florian,
could you please check your above patch, Jiri got build errors while trying to build an other test kernel for me.
http://download.opensuse.org/repositories/home:/jirislaby:/vp702x/standard/
https://bugzilla.novell.com/show_bug.cgi?id=709440
Thank you, Markus
Oh, I'm sorry. vp702x_usb_out_op had to be exported too, for this to work. I actually had it in my tree (hence it compiled for me), but forgot to add it to the patch I send you.
From the bugzilla comment and Jiri's last sentence , I take it Jiri already corrected it and got it building?
(I attached the complete patch for reference.) Regards, Flo p.s.: Sorry jiri, will double check twice any patch I sent Markus from now on :-) Thanks for building these kernels for him. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c28
Markus Stephan
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c29
Jiri Slaby
(In reply to comment #26)
(In reply to comment #25)
It did not show up ...
Yes, due to build error. As this is the second time, ask him to provide you with patches that don't cause build errors. It's (hopefully) fixed and building now at the usual place.
No, it did not build ...
It does not look like it did not. See: https://build.opensuse.org/project/monitor?project=home%3Ajirislaby%3Avp702x -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c30
Markus Stephan
(In reply to comment #27)
(In reply to comment #26)
(In reply to comment #25)
It did not show up ...
Yes, due to build error. As this is the second time, ask him to provide you with patches that don't cause build errors. It's (hopefully) fixed and building now at the usual place.
No, it did not build ...
It does not look like it did not. See: https://build.opensuse.org/project/monitor?project=home%3Ajirislaby%3Avp702x
I probably was too impatient then ... However, the new test kernel works pretty good and reduces the 'vp702x: usb in operation failed. (-110)' messages a lot. But there are still some cases left in the driver, which seams to trigger the above error message. Hopefully Florian is able to submit one last patch to address this issue and we could finally close this bug as 'fixed'. Thank you, Markus Stephan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c31
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c32
Markus Stephan
Any updates on this? have you heard back from him?
No, no reply until now. New kernel 3.1 still oopses after loading the vp702x driver, even so a working and tested patch exists since months now. Since the real bug is fixed and only some cosmetic problems left, I think you could close this bug as resolved. Thank you, Markus Stephan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=709440
https://bugzilla.novell.com/show_bug.cgi?id=709440#c33
Jiri Slaby
participants (1)
-
bugzilla_noreply＠novell.com