Second release-candidate for 0.17.4 -- please test!

[Nicolas Boullis]

Hi,

Jan Willies discovered a problem with the first RC, that was published
yesterday.
Hence, I just packed a new release candidate for 0.17.4.
As usual you can get it from
  http://dxr3.sourceforge.net/download/em8300-0.17.4-rc2.tar.gz

All comments are welcome. Please give it a try and report. (Even if you
don't use a bleeding-edge kernel, things may be broken for old kernels
as well.)


Cheers,

Nicolas

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Jan Willies]

Hi Nicolas,

Am 16.09.2009 00:29, schrieb Nicolas Boullis:
> All comments are welcome. Please give it a try and report. (Even if you
> don't use a bleeding-edge kernel, things may be broken for old kernels
> as well.)

Works fine with 2.6.30 and I even got my colors in vdr-dxr3-plugin back.
Had to switch back to .30 because my filesystem didn't like the new
kernel too much.


thanks,

  - jan

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Nicolas Boullis]

Hi Jan,

On Fri, Sep 18, 2009 at 08:20:35AM +0200, Jan Willies wrote:

> Hi Nicolas,
>
> Am 16.09.2009 00:29, schrieb Nicolas Boullis:
> > All comments are welcome. Please give it a try and report. (Even if you
> > don't use a bleeding-edge kernel, things may be broken for old kernels
> > as well.)
>
> Works fine with 2.6.30 and I even got my colors in vdr-dxr3-plugin back.
> Had to switch back to .30 because my filesystem didn't like the new
> kernel too much.

Thanks for your report.
Anyone else wants to give it a try?
Unless I get some negative feedback, I'd like to release 0.17.4 ASAP
(probably tomorrow).


Regards,

Nicolas

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

Am Samstag, 19. September 2009 23:12:07 schrieb Nicolas Boullis:

> Hi Jan,
>
> On Fri, Sep 18, 2009 at 08:20:35AM +0200, Jan Willies wrote:
> > Hi Nicolas,
> >
> > Am 16.09.2009 00:29, schrieb Nicolas Boullis:
> > > All comments are welcome. Please give it a try and report. (Even if you
> > > don't use a bleeding-edge kernel, things may be broken for old kernels
> > > as well.)
> >
> > Works fine with 2.6.30 and I even got my colors in vdr-dxr3-plugin back.
> > Had to switch back to .30 because my filesystem didn't like the new
> > kernel too much.
>
> Thanks for your report.
> Anyone else wants to give it a try?
> Unless I get some negative feedback, I'd like to release 0.17.4 ASAP
> (probably tomorrow).
>
>
> Regards,
>
> Nicolas
>
> ---------------------------------------------------------------------------
> --- Come build with us! The BlackBerry® Developer Conference in SF, CA
>  is the only developer event you need to attend this year. Jumpstart your
>  developing skills, take BlackBerry mobile applications to market and stay
>  ahead of the curve. Join us from November 9-12, 2009. Register
>  now! http://p.sf.net/sfu/devconf
> _______________________________________________
> Dxr3-devel mailing list
> Dxr3-devel@...
> https://lists.sourceforge.net/lists/listinfo/dxr3-devel
>

Hello,

I tried the rc2 with kernel 2.6.31 yesterday, but I got various kernel OOPSes
and wrong OSD colours with VDR.
This could be an issue not related to the dxr3 driver, I don't know. I'll try
again this evening with a debug kernel.

S.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Nicolas Boullis]

Hi Sebastian,

On Sun, Sep 20, 2009 at 10:36:34AM +0200, Sebastian Frei wrote:
>
> Hello,
>
> I tried the rc2 with kernel 2.6.31 yesterday, but I got various kernel OOPSes
> and wrong OSD colours with VDR.
> This could be an issue not related to the dxr3 driver, I don't know. I'll try
> again this evening with a debug kernel.

Thanks for your report, although this certainly is bad news.
You made no change to the userspace applications you are using, did you?
It certainly looks like the problem Jan Willies described a little while
ago. But he also reported that his problem vanished when switching back
to 2.6.30, while I'm pretty confident the source code for the em8300,
adv717x and bt865 modules is excatly the same for kernels 2.6.30 and
2.6.31...
It would be nice if you could send a backtrace of your kernel OOPSes,
with the hope it is related to the color problem you have...


Cheers,

Nicolas

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Adam-51]

Nicolas Boullis pisze:
> Thanks for your report.
> Anyone else wants to give it a try?
> Unless I get some negative feedback, I'd like to release 0.17.4 ASAP
> (probably tomorrow).

Hello,

Works with 2.6.31

Thanks again

--
Regards,
Adam

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Nicolas Boullis]

Hi,

On Mon, Sep 21, 2009 at 07:40:51PM +0200, Adam wrote:
>
> Works with 2.6.31

Thanks for your report.
Jan and Sebastian both reported problems with 2.6.31 using vdr. What
application do you use?


Regards,

Nicolas

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

Hello,

this crash occured after loading the module and starting VDR.

Sigma Designs EM8300 0000:00:0d.0: enabling device (0004 -> 0006)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
em8300-0: EM8300 8300 (rev 1)
bus: 0, devfn: 104, irq: 11,
memory: 0xf4000000.
em8300-0: mapped-memory at 0xc4c80000
em8300-0: using MTRR
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs
em8300-0: detected card: Hollywood+ type 2.
em8300-0: Chip revision: 2
unable to register OSS PCM device 0:0
BUG: unable to handle kernel NULL pointer dereference at 00000024
IP: [<c4c498ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
*pde = 00000000
Oops: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: em8300 lirc_serial lirc_dev uhci_hcd usbcore floppy evdev

Pid: 962, comm: vdr Not tainted (2.6.31-VDR2 #13)
EIP: 0060:[<c4c498ca>] EFLAGS: 00010296 CPU: 0
EIP is at em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
EAX: c3935600 EBX: 00000000 ECX: 00000005 EDX: 00000001
ESI: c39a8800 EDI: 00000005 EBP: c397fe30 ESP: c397fe24
 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process vdr (pid: 962, ti=c397e000 task=c384e090 task.ti=c397e000)
Stack:
 00000090 00000000 c39a8800 c397fe50 c4c4715e c397fe50 00000286 00000286
<0> c3b48000 c39a8800 00000000 c397fe84 c4c49574 0000010e c397fe98 c01435d2
<0> 00000001 c07ee7a0 09f5eea0 0000666e 00000001 c0806418 40084300 bfdc83b8
Call Trace:
 [<c4c4715e>] ? em8300_video_setup+0x3de/0x490 [em8300]
 [<c4c49574>] ? em8300_ioctl_init+0x74/0x220 [em8300]
 [<c01435d2>] ? validate_chain+0x3d2/0x4e0
 [<c4c490ba>] ? em8300_control_ioctl+0x78a/0xbd0 [em8300]
 [<c01837ec>] ? dput+0xcc/0xd0
 [<c0145feb>] ? __lock_release+0x3b/0x60
 [<c01896d6>] ? mntput_no_expire+0x16/0x80
 [<c4c43240>] ? em8300_io_ioctl+0x0/0x90 [em8300]
 [<c4c4329d>] ? em8300_io_ioctl+0x5d/0x90 [em8300]
 [<c0180918>] ? vfs_ioctl+0x48/0x70
 [<c01813b4>] ? do_vfs_ioctl+0x74/0x1c0
 [<c0181539>] ? sys_ioctl+0x39/0x60
 [<c0102d38>] ? sysenter_do_call+0x12/0x36
Code: ec 5d c3 89 96 9c 06 00 00 89 f0 bf 01 00 00 00 e8 dc e6 ff ff 8b 86 38 04 00 00 85 c0 74 c5 89
f6 8b 58 1c 89 f9 ba 01 00 00 00 <ff> 53 24 eb b4 90 85 d2 bf 05 00 00 00 74 93 e9 75 ff ff ff 89
EIP: [<c4c498ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300] SS:ESP 0068:c397fe24
CR2: 0000000000000024
---[ end trace 03568fd5c311d885 ]---

I don't have physical access to the machine until Saturday, so debugging is a bit complicated.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Nicolas Boullis]

Hi Sebastian,

On Tue, Sep 22, 2009 at 02:17:23PM +0200, Sebastian Frei wrote:
> Hello,
>
> this crash occured after loading the module and starting VDR.
>
> Modules linked in: em8300 lirc_serial lirc_dev uhci_hcd usbcore floppy evdev

Hmmm... No adv717x or bt865 module? That's strange...
Is it possible that the em8300 module tried to load the adv717x module
but did not find it?
A guess is that you did not install the modules in /lib/modules/... or
did not run depmod.

That would explain the Ooops (although it certainly has to be fixed)...


Regards,

--
Nicolas

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

Am Dienstag, 22. September 2009 22:47:28 schrieb Nicolas Boullis:

> Hi Sebastian,
>
> On Tue, Sep 22, 2009 at 02:17:23PM +0200, Sebastian Frei wrote:
> > Hello,
> >
> > this crash occured after loading the module and starting VDR.
> >
> > Modules linked in: em8300 lirc_serial lirc_dev uhci_hcd usbcore floppy
> > evdev
>
> Hmmm... No adv717x or bt865 module? That's strange...
> Is it possible that the em8300 module tried to load the adv717x module
> but did not find it?
> A guess is that you did not install the modules in /lib/modules/... or
> did not run depmod.
>
> That would explain the Ooops (although it certainly has to be fixed)...
>
>
> Regards,
>

I copied the modules into the /lib/modules/2.6.31-VDR2/kernel/drivers directory, where all the other
modules also are. Depmod did run.
I'll try tomorrow if everything works after loading the adv717x module manually.

S.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Nicolas Boullis]

Hi,

On Wed, Sep 23, 2009 at 09:54:52PM +0200, Sebastian Frei wrote:
> I copied the modules into the /lib/modules/2.6.31-VDR2/kernel/drivers directory, where all the other
> modules also are. Depmod did run.

Did you run it youself?
I just tried to "make install" the modules; make reported that "DEPMOD"
was run, but the modules.alias file and its friends were not updated.
Because of this, the em8300 module would not find the adv717x or bt865
modules.
I then ran "depmod -a" myself, and then everything was fine.
I have no idea why "make install" did not really run depmod...


> I'll try tomorrow if everything works after loading the adv717x module manually.

Any result?


Cheers,

Nicolas

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

Am Donnerstag, 24. September 2009 23:08:33 schrieb Nicolas Boullis:

> Hi,
>
> On Wed, Sep 23, 2009 at 09:54:52PM +0200, Sebastian Frei wrote:
> > I copied the modules into the /lib/modules/2.6.31-VDR2/kernel/drivers
> > directory, where all the other modules also are. Depmod did run.
>
> Did you run it youself?
> I just tried to "make install" the modules; make reported that "DEPMOD"
> was run, but the modules.alias file and its friends were not updated.
> Because of this, the em8300 module would not find the adv717x or bt865
> modules.
> I then ran "depmod -a" myself, and then everything was fine.
> I have no idea why "make install" did not really run depmod...
>

Yes I ran "depmod -a" myself after copying the modules into the modules directory.

> > I'll try tomorrow if everything works after loading the adv717x module
> > manually.
>
Some tests, stiill with rc2:

/lib/modules/2.6.31-VDR2>modprobe em8300

dmesg:
Sigma Designs EM8300 0000:00:0d.0: enabling device (0004 -> 0006)                                                                                                                                                                  
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11                                                                                                                                                                                  
PCI: setting IRQ 11 as level-triggered                                                                                                                                                                                              
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11                                                                                                                                        
em8300-0: EM8300 8300 (rev 1)                                                                                                                                                                                                      
bus: 0, devfn: 104, irq: 11,                                                                                                                                                                                                        
memory: 0xf4000000.                                                                                                                                                                                                                
em8300-0: mapped-memory at 0xc4c80000                                                                                                                                                                                              
em8300-0: using MTRR                                                                                                                                                                                                                
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs                                                                                                                                                                      
em8300-0: detected card: Hollywood+ type 2.                                                                                                                                                                                        
em8300-0: Chip revision: 2                                                                                                                                                                                                          
unable to register OSS PCM device 0:0

/lib/modules/2.6.31-VDR2>modprobe adv717x

dmesg:
adv717x.o: ADV7170 rev. 0 chip probed

/lib/modules/2.6.31-VDR2>em8300setup                                                                                                                                                                                                
Microcode uploaded to /dev/em8300-0                                                                                                                                                                                                
Current settings are:                                                                                                                                                                                                              
Video   Aspect  Audio   Spu                                                                                                                                                                                                        
PAL     4:3     ANALOG  OFF

dmesg:
em8300-0: Microcode version 0x29 loaded

/lib/modules/2.6.31-VDR2>rmmod adv717x em8300                                                                                                                                                                                      
Killed

dmesg:
 BUG: unable to handle kernel NULL pointer dereference at 00000024
IP: [<c4bf420a>] release_em8300+0x9a/0xd0 [em8300]
*pde = 00000000
Oops: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: em8300(-) uhci_hcd usbcore floppy evdev [last unloaded: adv717x]

Pid: 663, comm: rmmod Not tainted (2.6.31-VDR2 #13)
EIP: 0060:[<c4bf420a>] EFLAGS: 00010246 CPU: 0
EIP is at release_em8300+0x9a/0xd0 [em8300]
EAX: c3935600 EBX: 00000000 ECX: 00000000 EDX: 00000002
ESI: c3922800 EDI: c389b400 EBP: c3bcfedc ESP: c3bcfed4
 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process rmmod (pid: 663, ti=c3bce000 task=c388aa00 task.ti=c3bce000)
Stack:
 c3922800 c389b458 c3bcfef0 c4bfeb8d c389b400 c4c04e90 c4c04e90 c3bcfefc
<0> c02049aa c389b458 c3bcff0c c024fee4 c389b458 c389b48c c3bcff20 c024fff8
<0> c4c04e90 00000000 bff8f1d0 c3bcff2c c024f34d c4c04e90 c3bcff44 c0250387
Call Trace:
 [<c4bfeb8d>] ? em8300_remove+0x3d/0x60 [em8300]
 [<c02049aa>] ? pci_device_remove+0x3a/0x40
 [<c024fee4>] ? __device_release_driver+0x84/0xd0
 [<c024fff8>] ? driver_detach+0x88/0xc0
 [<c024f34d>] ? bus_remove_driver+0x3d/0x60
 [<c0250387>] ? driver_unregister+0x47/0x50
 [<c025014f>] ? driver_remove_file+0xf/0x20
 [<c0204a8a>] ? pci_unregister_driver+0x1a/0x30
 [<c4bfebc2>] ? em8300_exit+0x12/0x28 [em8300]
 [<c014c2f4>] ? sys_delete_module+0x164/0x170
 [<c0145feb>] ? __lock_release+0x3b/0x60
 [<c0102d6b>] ? sysenter_exit+0xf/0x18
 [<c0144072>] ? trace_hardirqs_on_caller+0xf2/0x130
 [<c01f8f44>] ? trace_hardirqs_on_thunk+0xc/0x10
 [<c0102d38>] ? sysenter_do_call+0x12/0x36
Code: 8b 80 38 01 00 00 e8 66 cc 55 fb 8b 46 5c 85 c0 75 3f 89 f0 e8 68 d5 57 fb 5b 5e 5d c3 8d 74
26 00 8b 58 1c 31 c9 ba 02 00 00 00 <ff> 53 24 8b 46 78 85 c0 0f 84 74 ff ff ff 90 8d b4 26 00 00 00
EIP: [<c4bf420a>] release_em8300+0x9a/0xd0 [em8300] SS:ESP 0068:c3bcfed4
CR2: 0000000000000024
---[ end trace 3528eaa7d6a88e3f ]---


another test, now I saw that em8300 and adv717x were blacklisted in the modprobe.conf file:

/etc/modprobe.d>modprobe em8300

/etc/modprobe.d>lsmod          
Module                  Size  Used by
adv717x                 9096  0      
em8300                 71316  0      
uhci_hcd               23832  0      
usbcore               131288  1 uhci_hcd
floppy                 56904  0        
evdev                  10884  0

/etc/modprobe.d>em8300setup                                                                                                                                                                                                        
Microcode uploaded to /dev/em8300-0                                                                                                                                                                                                
Current settings are:                                                                                                                                                                                                              
Video   Aspect  Audio   Spu                                                                                                                                                                                                        
PAL     4:3     ANALOG  OFF

/etc/modprobe.d>rmmod adv717x                                                                                                                                                                                                      

/etc/modprobe.d>lsmod                                                                                                                                                                                                              
Module                  Size  Used by                                                                                                                                                                                              
em8300                 71316  0                                                                                                                                                                                                    
uhci_hcd               23832  0                                                                                                                                                                                                    
usbcore               131288  1 uhci_hcd                                                                                                                                                                                            
floppy                 56904  0                                                                                                                                                                                                    
evdev                  10884  0

/etc/modprobe.d>modprobe adv717x
/etc/modprobe.d>em8300setup
Killed

dmesg:
Sigma Designs EM8300 0000:00:0d.0: enabling device (0004 -> 0006)                                                                                                                                                                  
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11                                                                                                                                                                                  
PCI: setting IRQ 11 as level-triggered                                                                                                                                                                                              
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11                                                                                                                                        
em8300-0: EM8300 8300 (rev 1)                                                                                                                                                                                                      
bus: 0, devfn: 104, irq: 11,                                                                                                                                                                                                        
memory: 0xf4000000.
em8300-0: mapped-memory at 0xc4c80000
em8300-0: using MTRR
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs
em8300-0: detected card: Hollywood+ type 2.
em8300-0: Chip revision: 2
unable to register OSS PCM device 0:0
adv717x.o: ADV7170 rev. 0 chip probed
Sigma Designs EM8300 0000:00:0d.0: PCI INT A disabled
Sigma Designs EM8300 0000:00:0d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
em8300-0: EM8300 8300 (rev 1)
bus: 0, devfn: 104, irq: 11,
memory: 0xf4000000.
em8300-0: mapped-memory at 0xc4f00000
em8300-0: using MTRR
IRQ 11/em8300: IRQF_DISABLED is not guaranteed on shared IRQs
em8300-0: detected card: Hollywood+ type 2.
em8300-0: Chip revision: 2
unable to register OSS PCM device 0:0
adv717x.o: ADV7170 rev. 0 chip probed
em8300-0: Microcode version 0x29 loaded
BUG: unable to handle kernel NULL pointer dereference at 00000024
IP: [<c4c3a8ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
*pde = 00000000
Oops: 0000 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: adv717x em8300 uhci_hcd usbcore floppy evdev [last unloaded: adv717x]

Pid: 734, comm: em8300setup Not tainted (2.6.31-VDR2 #13)
EIP: 0060:[<c4c3a8ca>] EFLAGS: 00010296 CPU: 0
EIP is at em8300_ioctl_setvideomode+0x9a/0xb0 [em8300]
EAX: c39d2000 EBX: 00000000 ECX: 00000005 EDX: 00000001
ESI: c3a67000 EDI: 00000005 EBP: c2c49e30 ESP: c2c49e24
 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process em8300setup (pid: 734, ti=c2c48000 task=c38809e0 task.ti=c2c48000)
Stack:
 00000090 00000000 c3a67000 c2c49e50 c4c3815e c2c49e50 00000286 00000286
<0> c3a90000 c3a67000 00000000 c2c49e84 c4c3a574 c0436980 c0436980 c3b0a1e0
<0> c396c0ac fffffffa 094dc008 0000666e 00000000 c2c49eb4 40084300 bfcadea8
Call Trace:
 [<c4c3815e>] ? em8300_video_setup+0x3de/0x490 [em8300]
 [<c4c3a574>] ? em8300_ioctl_init+0x74/0x220 [em8300]
 [<c4c3a0ba>] ? em8300_control_ioctl+0x78a/0xbd0 [em8300]
 [<c0144f9c>] ? __lock_acquire+0x22c/0x7f0
 [<c0173800>] ? fd_install+0x40/0x50
 [<c014414b>] ? trace_hardirqs_off+0xb/0x10
 [<c014673c>] ? debug_check_no_locks_freed+0x8c/0xc0
 [<c017173c>] ? kmem_cache_free+0x5c/0x80
 [<c0144072>] ? trace_hardirqs_on_caller+0xf2/0x130
 [<c4c34240>] ? em8300_io_ioctl+0x0/0x90 [em8300]
 [<c4c3429d>] ? em8300_io_ioctl+0x5d/0x90 [em8300]
 [<c0180918>] ? vfs_ioctl+0x48/0x70
 [<c01813b4>] ? do_vfs_ioctl+0x74/0x1c0
 [<c0181539>] ? sys_ioctl+0x39/0x60
 [<c0102d38>] ? sysenter_do_call+0x12/0x36
Code: ec 5d c3 89 96 9c 06 00 00 89 f0 bf 01 00 00 00 e8 dc e6 ff ff 8b 86 38 04 00 00 85 c0 74 c5 89
f6 8b 58 1c 89 f9 ba 01 00 00 00 <ff> 53 24 eb b4 90 85 d2 bf 05 00 00 00 74 93 e9 75 ff ff ff 89
EIP: [<c4c3a8ca>] em8300_ioctl_setvideomode+0x9a/0xb0 [em8300] SS:ESP 0068:c2c49e24
CR2: 0000000000000024
---[ end trace b423a404c69981b2 ]---


After a reboot without blacklisted modules, the em8300 and the adv717x module were loaded
automatically and VDR works but with wrong OSD colours.

S.

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel

[Adam-51]

Nicolas Boullis wrote:
> Hi,
>
> On Mon, Sep 21, 2009 at 07:40:51PM +0200, Adam wrote:
>> Works with 2.6.31
>
> Thanks for your report.
> Jan and Sebastian both reported problems with 2.6.31 using vdr. What
> application do you use?
>

Hello,

I'm using mplayer

Regards,
Adam

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Dxr3-devel mailing list
Dxr3-devel@...
https://lists.sourceforge.net/lists/listinfo/dxr3-devel