Bug 201055 - dvb-usb-v2: General Protection Fault shortly after boot
Summary: dvb-usb-v2: General Protection Fault shortly after boot
Status: NEW
Alias: None
Product: v4l-dvb
Classification: Unclassified
Component: dvb-usb (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: dvb-usb
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-09 00:05 UTC by Dan Ziemba
Modified: 2018-10-25 14:05 UTC (History)
6 users (show)

See Also:
Kernel Version: 4.18
Tree: Mainline
Regression: Yes


Attachments

Description Dan Ziemba 2018-09-09 00:05:15 UTC
Starting with the first 4.18 RC kernel, my system experiences general protection faults leading to kernel panic shortly after the login prompt appears on most boots.  Occasionally that doesn't happen and instead numerous other seemingly random stack traces are printed (bad page map, scheduling while atomic, null pointer deref, etc), but either way the system is unusable.  This bug remains up through the latest mainline kernel 4.19-rc2.

Booting with my USB ATSC tv tuner disconnected prevents the bug from happening.


Kernel bisection between v4.17 and 4.18-rc1 shows problem is caused by:

1a0c10ed7bb1 media: dvb-usb-v2: stop using coherent memory for URBs


Building both 4.18.6 and 4.19-rc2 with that commit reverted resolves the bug for me.  


My DVB hardware uses driver mxl111sf:

Bus 002 Device 003: ID 2040:c61b Hauppauge 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x2040 Hauppauge
  idProduct          0xc61b 
  bcdDevice            0.00
  iManufacturer           1 Hauppauge
  iProduct                2 WinTV Aero-M

Other system info:

Arch Linux x86_64
Intel i7-3770
16 GB ram
Comment 1 Victor Toso 2018-10-25 14:05:38 UTC
You could try to see if it fixes the issue for you.
https://www.mail-archive.com/linux-media@vger.kernel.org/msg135901.html

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