Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: Oops: saa7146_vv: saa7146_vv_init(): out of memory. aborting.



Martin Theodor Grewe wrote:
> Hi Johannes,
> 
> Johannes Stezenbach wrote:
> >>modprobe: page allocation failure. order:4, mode:0x20
> >>[<c0132882>] __alloc_pages+0x1c2/0x370
> >>[<c0132a4f>] __get_free_pages+0x1f/0x40
> >>[<c01084da>] dma_alloc_coherent+0xca/0x100
> >>[<e0d2c232>] saa7146_vv_init+0xa2/0x180 [saa7146_vv]
> >>[<e0f35ce4>] av7110_init_v4l+0x34/0x160 [dvb_ttpci]
> >
> >Well, that's not our fault...
> 
> Hm, I looked in my runvdr and found:
> 
> rmmod dvb_ttpci stv0299 dvb_core ttpci_eeprom saa7146_vv saa7146 2>/dev/null
> rmmod ves1820 tda8083 sp8870 ves1x93 video_buf videodev 2>/dev/null
> 
> Might it be possible that removing saa7146* stuff is not usefull?
> Only reloading dvb_ttpci (with firmware) is enough. Hm... I'll test this.

Doesn't make a difference, the memory allocation happens when a card
is detected, not whe the saa7146 driver is loaded.

Either you don't have enough RAM, or something else is eating it.

> >>Unable to handle kernel paging request at virtual address e0ce2f00
> >...but this one is. av7110_ir.c needs to be rewritten
> >properly, apparently the author only cared to provide
> >a quick & dirty hack.
> 
> I'am not using ir etc. on this maschine. Only vdradmin is working there 
> - no TV-equipment, Remote-control -> tty8, keyboard.
> This could really help?? If YES I'am going to test this.

The patch won't help with the memory issue, but it should prevent
the Oops that follows it. I would like to know if it does what
it should (so I can commit it to CVS), even if you might have to reboot
anyway before you can load the driver again because of your
out-of-memory problem.

Johannes




Home | Main Index | Thread Index