[linux-dvb] Re: Driver crash (ARM Crash)

[Tim Schröder <tim.schroeder@epost.de>]

Hello,

thanks for your answer !!!

- maybe you're right and VIA chipset is causing some trouble. But at
least a driver shouldnt oops that bad by effects from outside. (BTW. i
am using one of the ibm harddrives and with or without tcq i get oopses)
- i pulled the cvs today again and installed the driver with 2.5.55
again. It runs much more stable.
The oopses occur much less frequently. i compiled the kernel whith
CONFIG_KALLSYMS so i get oopses with symbols. Is that enough or do the
developers need a ksymoops converted trace ? i did one but  my
/proc/ksyms file is missing and it looks quit meaningless to me.

thanks in advance 

Tim

Am Don, 2003-01-09 um 11.46 schrieb Michael Hunold:
> Hello Tim,
> 
> although I'm only the saa7146 author and not the av7110 guru,
> here are my thoughts:
> 
> > in my box (K6-2 300 on Apollo VP3) i always had a few problems with the
> > driver and my Hauppage card. Now i've been able to track it down a bit
> > and send some traces. 
> 
> Your box is quite slow -- I noticed that the cards are very sensitive 
> against interrupt or system delays of any kind.
> 
> > I am using the current version of dvb-kernel and a 2.5.54 kernel.
> > Everything is installed as described in the README. And i am using the
> > driver with vdr.
> 
> I recently fixed the i2c-transfer in the saa7146 driver. It tried to use 
> interrupts for the transfers to lower the system load -- but 
> unfortunately this resulted in "oops" messages and sometimes TS lockup.
> 
> > when i am using my harddrive with DMA (udma, mdma) i see ARM crashes
> > with kernel OOPS. If the drive is using PIO everything runs stable. the
> > rest of the systems runs stable now for years with udma !
> 
>  > <4>blk: queue c0398e1c, I/O limit 4095Mb (mask 0xffffffff)
>  > <6>hda: tagged command queueing enabled, command queue depth 32
> 
> Are you sure you want to run tcq on an ide drive? It's only fully 
> supported on some ibm(?) harddisks afaik. Does your drive support tcq at 
> all?
> 
> > With PIO i get a blocky picture when i hear the driver write data onto
> > the disk.With DMA i get a perfect picture till the hole machine goes
> > oops.
> 
> One problem is the via pci<->ide arbitration, in conjunction with pci 
> devices that create high pci bus loads. (Remember the via bug?) I have 
> had severe problems with saa7146 based cards and via chipsets (for me: 
> the kt133a on a ecs k7zva mainboard) -- I came to the conclusion to drop
> all via based systems and did not buy via again.
> 
> PIO creates a high cpu load (and probably pci bus, too), so it's likely 
> that the saa7146 cannot write to the gfx card's framebuffer as fast as 
> it should.
> 
> > If i am using timeshifting the driver oopses after a few seconds, if i
> > am just recording it runs a few minutes.
> 
> Again: the problem is the pci load that the saa7146 creates when writing 
> to the framebuffer. If you only record, then the load is much lower.
> 
> > On 2.4.20 with the cvs-driver i had the same problems except that i
> > didnt saw a kernel oops and after rmmod/insmod everything ran o.k.
> > again.
> 
> Please try again with the latest cvs driver. At least some of the oops 
Unable to handle kernel paging request at virtual address c89011c8
 printing eip:
c88f6078
*pde = 011b6067
*pte = 00000000
Oops: 0000
CPU:    0
EIP:    0060:[<c88f6078>]    Not tainted
EFLAGS: 00010282
EIP is at load_dram+0xe0/0x3770a068 [dvb_ttpci]
eax: 00000000   ebx: c89011c8   ecx: 00000300   edx: c63fc000
esi: c89011c8   edi: c63fc000   ebp: c6080000   esp: c6031f64
ds: 007b   es: 007b   ss: 0068
Process arm_mon (pid: 262, threadinfo=c6030000 task=c691c6e0)
Stack: 00002000 c88fed14 c63fc0a8 c6080000 00004400 2e000404 000009ec 00000052 
       00000000 c88f64df c6080000 c89011c8 0003e1ec c6080000 c6030000 00003b57 
       c6080000 c11b8d40 10325476 c88f2354 c6080000 c6080000 c88f23de c6080000 
Call Trace:
 [<c88fed14>] bootcode+0xa8/0x37701394 [dvb_ttpci]
 [<c88f64df>] bootarm+0x25f/0x37709d80 [dvb_ttpci]
 [<c88f2354>] recover_arm+0x48/0x3770dcf4 [dvb_ttpci]
 [<c88f23de>] arm_error+0x46/0x3770dc68 [dvb_ttpci]
 [<c88f2583>] arm_thread+0x19f/0x3770dc1c [dvb_ttpci]
 [<c88fbf7c>] +0x23c/0x377042c0 [dvb_ttpci]
 [<c88f23e4>] arm_thread+0x0/0x3770dc1c [dvb_ttpci]
 [<c0106fc9>] show_regs+0x5/0xc

Code: f3 a5 68 00 0c 00 00 53 8b 74 24 18 56 68 00 00 1e 00 55 e8 
root@video:~# ksymoops -v /usr/src/linux/vmlinux oops.txt                               
ksymoops 2.4.8 on i586 2.5.55.  Options used
     -v /usr/src/linux/vmlinux (specified)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.5.55/ (default)
     -m /usr/src/linux/System.map (default)

Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel paging request at virtual address c89011c8
c88f6078
*pde = 011b6067
Oops: 0000
CPU:    0
EIP:    0060:[<c88f6078>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 00000000   ebx: c89011c8   ecx: 00000300   edx: c63fc000
esi: c89011c8   edi: c63fc000   ebp: c6080000   esp: c6031f64
ds: 007b   es: 007b   ss: 0068
Stack: 00002000 c88fed14 c63fc0a8 c6080000 00004400 2e000404 000009ec 00000052 
       00000000 c88f64df c6080000 c89011c8 0003e1ec c6080000 c6030000 00003b57 
       c6080000 c11b8d40 10325476 c88f2354 c6080000 c6080000 c88f23de c6080000 
Call Trace:
 [<c88fed14>] bootcode+0xa8/0x37701394 [dvb_ttpci]
 [<c88f64df>] bootarm+0x25f/0x37709d80 [dvb_ttpci]
 [<c88f2354>] recover_arm+0x48/0x3770dcf4 [dvb_ttpci]
 [<c88f23de>] arm_error+0x46/0x3770dc68 [dvb_ttpci]
 [<c88f2583>] arm_thread+0x19f/0x3770dc1c [dvb_ttpci]
 [<c88fbf7c>] +0x23c/0x377042c0 [dvb_ttpci]
 [<c88f23e4>] arm_thread+0x0/0x3770dc1c [dvb_ttpci]
 [<c0106fc9>] show_regs+0x5/0xc
Code: f3 a5 68 00 0c 00 00 53 8b 74 24 18 56 68 00 00 1e 00 55 e8 


>>EIP; c88f6078 <END_OF_CODE+856ff84/????>   <=====

Trace; c88fed14 <END_OF_CODE+8578c20/????>
Trace; c88f64df <END_OF_CODE+85703eb/????>
Trace; c88f2354 <END_OF_CODE+856c260/????>
Trace; c88f23de <END_OF_CODE+856c2ea/????>
Trace; c88f2583 <END_OF_CODE+856c48f/????>
Trace; c88fbf7c <END_OF_CODE+8575e88/????>
Trace; c88f23e4 <END_OF_CODE+856c2f0/????>
Trace; c0106fc9 <kernel_thread_helper+5/c>

Code;  c88f6078 <END_OF_CODE+856ff84/????>
00000000 <_EIP>:
Code;  c88f6078 <END_OF_CODE+856ff84/????>   <=====
   0:   f3 a5                     repz movsl %ds:(%esi),%es:(%edi)   <=====
Code;  c88f607a <END_OF_CODE+856ff86/????>
   2:   68 00 0c 00 00            push   $0xc00
Code;  c88f607f <END_OF_CODE+856ff8b/????>
   7:   53                        push   %ebx
Code;  c88f6080 <END_OF_CODE+856ff8c/????>
   8:   8b 74 24 18               mov    0x18(%esp,1),%esi
Code;  c88f6084 <END_OF_CODE+856ff90/????>
   c:   56                        push   %esi
Code;  c88f6085 <END_OF_CODE+856ff91/????>
   d:   68 00 00 1e 00            push   $0x1e0000
Code;  c88f608a <END_OF_CODE+856ff96/????>
  12:   55                        push   %ebp
Code;  c88f608b <END_OF_CODE+856ff97/????>
  13:   e8 00 00 00 00            call   18 <_EIP+0x18> c88f6090 <END_OF_CODE+856ff9c/????>


1 error issued.  Results may not be reliable.