[mythtv-users] kernel oops! PVR 250 on 7NIF2 -- ideas?

john lawler maillist at tgice.com
Fri Mar 19 11:34:04 EST 2004


(2nd repost--can't seem to get this to start it's own thread--augh!)

Hi guys, sorry to come back with basically the same question, but I
guess it really is a bit different now.  Since I read your helpful
posts, I removed APIC and ACPI support from my kernel, and initially
this seemed to help things.  What I mean is recording shows on the pvr
250 went from locking up after only 5-10 minutes to now doing a kernel
oops after a much longer time, perhaps 3-5 hours, but also successfully
recording programs.

This new behavior also allows at least one or two shows (30-60 minutes)
to complete successfully before dying.  And like I said, I'm now getting
the flashing lights on the keyboard indicating a kernel oops.

(See the most recent kernel oops message and the same message ksymoops
decoded at the bottom of the message).

And yes, my BIOS firmware is up to date (9/something/2003).  But since I
now have APIC and ACPI turned off completely in the kernel, I wonder
what else could be causing this lockup? (I also passed the:
     acpi=off acpi_irq_nobalance noapic
kernel options on my Grub 'kernel <path> <options>' line)

Might I2C have anything to do with this?  I've tried the testing without
lircd even running (and thus the lirc modules not modprobed) and also
running, and it doesn't seem to have any effect.

I've had virtually this identical kernel oops two nights in a row.  Most
recently, the system had an uptime of approximately 9 hours; at the
beginning, it was recording from a single channel for 5 straight hours,
with no problems.  I quickly reviewed the resulting file and it looks
fine.  Then nothing else was recorded for roughly 4 hours, I guess and
then, for apparently no reason, it blows up.  It's possible that another
recording was gearing up to start at that point, but I have no evidence
of that in the logs, and not one byte of a new file was written.

This seems to be the pattern for me this week, after I figured out the
apic acpi options--everything looks fine in the short run and all the
functions seem to work, but then it'll lockup, always within a few to
several hours.

Any one have a clue about this kernel oops?  I googled, of course, but
didn't find much that seemed to match--exactly, anyway.

Thanks for your help and experience.

jl

==========================================================================
    kernel oops raw output from terminal
==========================================================================
kernel BUG at sched.c:1265!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c01c714c>]    Tainted: P
EFLAGS: 00010202
eax: 00000001   ebx: ce048000   ecx: 84000ef7   edx: 00000001
esi: c014d100   edi: c65ea000   ebp: ce049ef0   esp: ce049ecc
ds: 0018   es: 0018   ss: 0018
Process mythbackend (pid: 3948, stackpage=ce049000)
Stack: ce049f00 c01459c8 c01459c8 ce048000 00000000 fffffffe ce048000
c014d100
         c65ea000 ce049efc c01c7184 ce048000 ce049f20 c01c63c1 c65ea000
0022634d
         00000001 00000282 ce048000 c65ea000 c01d4410 ce049f30 c01c6496
c65ea000
Call Trace:    [<c01c7184>] [<c01c63c1>] [<c01d4410>] [<c01c6496>]
[<c01d403d>]
    [<c01cfe93>] [<c01cfd66>] [<c01cfb95>] [<c01bac30>] [<c01bd2f3>]

Code: 0f 0b f1 04 25 94 39 c0 e9 07 fb ff ff 8d b4 26 00 00 00 00
   <0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
==========================================================================

==========================================================================
    the above, run through ksymoops
==========================================================================
ksymoops 2.4.9 on i686 2.4.22-gentoo-r7.  Options used
       -V (default)
       -k /proc/ksyms (default)
       -l /proc/modules (default)
       -o /lib/modules/2.4.22-gentoo-r7/ (default)
       -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

kernel BUG at sched.c:1265!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c01c714c>]    Tainted: P
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 00000001   ebx: ce048000   ecx: 84000ef7   edx: 00000001
esi: c014d100   edi: c65ea000   ebp: ce049ef0   esp: ce049ecc
ds: 0018   es: 0018   ss: 0018
Process mythbackend (pid: 3948, stackpage=ce049000)
Stack: ce049f00 c01459c8 c01459c8 ce048000 00000000 fffffffe ce048000
c014d100
         c65ea000 ce049efc c01c7184 ce048000 ce049f20 c01c63c1 c65e000
0022634d
         00000001 00000282 ce048000 c65ea000 c01d4410 ce049f30 c01c6496
c65ea000
Call Trace:    [<c01c7184>] [<c01c63c1>] [<c01d4410>] [<c01c6496>]
[<c01d403d>]
    [<c01cfe93>] [<c01cfd66>] [<c01cfb95>] [<c01bac30>] [<c01bd2f3>]
Code: 0f 0b f1 04 25 94 39 c0 e9 07 fb ff ff 8d b4 26 00 00 00 00


  >>EIP; c01c714c <schedule+52c/540>   <=====

  >>ebx; ce048000 <_end+dc75a50/1c82eab0>
  >>esi; c014d100 <runqueues+0/940>
  >>edi; c65ea000 <_end+6217a50/1c82eab0>
  >>ebp; ce049ef0 <_end+dc77940/1c82eab0>
  >>esp; ce049ecc <_end+dc7791c/1c82eab0>

Trace; c01c7184 <preempt_schedule+24/40>
Trace; c01c63c1 <try_to_wake_up+131/1f0>
Trace; c01d4410 <process_timeout+0/10>
Trace; c01c6496 <wake_up_process+16/20>
Trace; c01d403d <timer_bh+18d/3d0>
Trace; c01cfe93 <bh_action+53/90>
Trace; c01cfd66 <tasklet_hi_action+46/70>
Trace; c01cfb95 <do_softirq+c5/d0>
Trace; c01bac30 <do_IRQ+e0/f0>
Trace; c01bd2f3 <call_do_IRQ+5/a>

Code;  c01c714c <schedule+52c/540>
00000000 <_EIP>:
Code;  c01c714c <schedule+52c/540>   <=====
     0:   0f 0b                     ud2a      <=====
Code;  c01c714e <schedule+52e/540>
     2:   f1                        icebp
Code;  c01c714f <schedule+52f/540>
     3:   04 25                     add    $0x25,%al
Code;  c01c7151 <schedule+531/540>
     5:   94                        xchg   %eax,%esp
Code;  c01c7152 <schedule+532/540>
     6:   39 c0                     cmp    %eax,%eax
Code;  c01c7154 <schedule+534/540>
     8:   e9 07 fb ff ff            jmp    fffffb14 <_EIP+0xfffffb14>
Code;  c01c7159 <schedule+539/540>
     d:   8d b4 26 00 00 00 00      lea    0x0(%esi,1),%esi

   <0>Kernel panic: Aiee, killing interrupt handler!

1 warning issued.  Results may not be reliable.
==========================================================================


More information about the mythtv-users mailing list