Bug 15750 - Random lockups or reboots when actively using mantis module
Summary: Random lockups or reboots when actively using mantis module
Status: RESOLVED INSUFFICIENT_DATA
Alias: None
Product: v4l-dvb
Classification: Unclassified
Component: dvb-other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: dvb-other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-10 12:42 UTC by Vidar Tyldum Hansen
Modified: 2012-06-18 20:21 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31-20-generic (Ubuntu)
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Syslog corruption. mantis loaded with verbose=3. (19.02 KB, application/octet-stream)
2010-04-10 12:42 UTC, Vidar Tyldum Hansen
Details

Description Vidar Tyldum Hansen 2010-04-10 12:42:19 UTC
Created attachment 25940 [details]
Syslog corruption. mantis loaded with verbose=3.

Random lockups occur when the DVB card is being actively used by an application (mythtv and tvheadend tested). It takes from 1 to 24 hours before problem occurs, but it always does. On some occations there is a complete freeze requiring hard reboot, on other occations machine instantly reboots.

If the mantis module is loaded, but no DVB-application running no lockups or reboots are observed. Only when application is started. It can happen when no channel is being watched or when watching a channel.

Several different revisions of mantis and various stock Ubuntu kernels tested, same results.

On the very last occurence I had, syslog suddenly was filled with binary garbage and what appears to be function calls relating to the 9p protocol. This is not used on the machine, so it puzzles me. Possible memory corruption?

Not been able to locate a different card to test with. No other issues, segfaults or anything else besides the use of the mantis module.

lspci:
01:05.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)
        Subsystem: TERRATEC Electronic GmbH Device 1178
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 64 (2000ns min, 63750ns max)
        Interrupt: pin A routed to IRQ 5
        Region 0: Memory at dffff000 (32-bit, prefetchable) [size=4K]
        Kernel modules: mantis
Comment 1 Alan 2012-06-18 20:21:24 UTC
Not much we can do with the data here so closing. If you've seen it with a modern kernel please update the bug

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