Jonas Meurer wrote:

>hello,
>
>i'm trying to use my PVR-350 with ivtv 0.3.3y on a 2.6.11 amd64 (x86_64)
>debian/unstable system, but unfortunately every second time i load the
>ivtv modules, i get a "page allocation failture". 'modprobe ivtv' output
>is attached as failed-modprobe-ivtv.out.
>  
>

A little googling turned up this:
echo "vm.min_free_kbytes=16384" >> /etc/sysctl.conf
or you could buy more memory, or sometimes it helps to load ivtv earlier
during the boot process

>after this modprobe failure the system gets more and more unstable, the
>X server is mostly completely screwed up, and after some minutes i
>finally get a system oops with the following message:
>
>---SNIP---
>NMI Watchdog detected LOCKUP on CPU0CPU 0
>Modules linked in: ivtv thermal button processor ohci1394 w93627hf \
>       i2c_sensor 12c_alsa i2c_matroxfb i2c_algo_bit i2c_viapro i2c_core
>PID: 5714, comm: cupsd Tainted:  G  M  2.6.11-4-amd64
>RID: 0010:[<ffffffff80157736>] <ffffffff80157736> {cache_alloc_refill +1822>
>RSP: 0018:ffff81001a3e5c28 EFLAGS: 00000083
>RAX: ffff81001ffefc90 RBX: 000000000000000c RCX: ffff810017f67100
>RDX: ffff81001ffefc90 RSI: 0000000000000000 RDI: 0000000000000001
>RBX: ffff81001ffeb180 R08: ffff81001ffefca0 R09: ffff81001ffefcb0
>[... some more, to lazy to manually transcribe all the numbers ...]
>Code: 41 8b 44 24 68 39 44 20 73 4b ff cb 83 fb ff 74 44 48 8d 7d
>console shuts up ...
> <0> Kernel panic - not syncing: Aiee, killing interrupt handler!
>---SNIP---
>
>i don't think that this kernel oops has anything to do with cupsys at
>all, as it doesn't happen when i don't load ivtv, and cupsd is running
>all the time.
>  
>

Probably not, that's just where the kernel was when the shit finally hit
the fan.

>my modprobe.d/ivtv contains the following options:
>---SNIP---
>alias char-major-81 videodev
>alias char-major-81-0 ivtv
>options ivtv ivtv_std=2 tda9887=0 ivtv_debug=1 tuner=38
>options msp3400 once=1 simple=1
>options tuner pal=1
>install ivtv /sbin/modprobe tuner; /sbin/modprobe msp3400; \
>        /sbin/modprobe saa7115; /sbin/modprobe saa7127; \
>        /sbin/modprobe --ignore-install ivtv; \
>        /usr/local/bin/ivtvctl -d /dev/video0 -u 0x3000; \
>        /usr/local/bin/ivtvctl -d /dev/video0 -u 0xff; \
>        /usr/local/bin/ivtvctl -p 4; \
>        /usr/local/bin/ivtvctl -f width=720,height=480;
>---SNIP---
>  
>

All you really _should_ need is the 2 alias lines. The rest isn't needed
99% of the time.

>the output of an unsuccessful 'modprobe ivtv' is attached as
>failed-modprobe-ivtv.out.
>
>as already mentioned, this doesn't happen every time i try to load ivtv.
>when i try to load the modules directly after rebooting, modprobe often
>succeeds. the output of a successful 'modprobe ivtv' is attached as
>succeeded-modprobe-ivtv.out.
>
>i have a pvr-350 and i'm located in germany where tuner 38 seems
>correct. i don't know whether all module options are required or even
>correct, as i couldn't find much information about that. i even don't
>know wheter i need to load all the modules before loading ivtv as the
>'install ivtv ...' command does.
>
>bye
> jonas
>  
>



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to