RE: RE: Dign Remote under Fedora 3

[Tim D. <ti...@op...>]

Hi,

It looks like the preemptible kernel is causing this.  The usb_unlink_urb
causes a crash when asynchronous (outside a lock).

I replicated your problem, and made a small change to the driver which seems
to have fixed it.  It also fixed the disconnect problem I was having.

The new patch is in the same place
(http://www.frogstorm.info/lirc-0.7.0-lirc_sasem.diff).  Make sure it is
different to the last patch, as it might get cached.

By the way, there is a config file in the LIRC distro, in
lirc-0.7.0/remotes/sasem/lircd.conf.dignhv5.

Cheers,

Tim.
 

-----Original Message-----
From: lir...@li...
[mailto:lir...@li...] On Behalf Of jv...@ci...
Sent: Tuesday, 28 December 2004 4:30 AM
To: lir...@li...
Subject: RE: RE: Dign Remote under Fedora 3 
Importance: High

Hi Tim,

I've downloaded your update from
http://www.frogstorm.info/lirc-0.7.0-lirc_sasem.diff and got it compiling
on Fedora Core 3, on a 2.6.9-1.715 kernel. It looks very promising.
However when I use irrecord to verify the working I get the following on
my main terminal:
------------------------------------------------------------
[<021e5500>] poke_blanked_console+0x91/0x9e
[<021e4892>] vt_console_print+0x284/0x292
[<021156ea>] __call_console_drivers+0x39/0x45
[<02110d8a>] do_page_fault+0x0/0x4f8
[<021123ba>] dequeue_task+0xe/0x3f
[<02112623>] deactivate_task+0x1f/0x2b
[<0229e144>] schedule+0x10c/0x38e
[<022305d2>] usb_kill_urb+0xb4/0xce
[<02113998>] autoremove_wake_function+0x0/0x3a
[<02113998>] autoremove_wake_function+0x0/0x3a
[<02115a1a>] vprintk+0x108/0x112
[<022304f3>] usb_unlink_urb+0x19/0x44
[<1294e69b>] s_SasemCallbackIn+0x1d6/0x1f3 [lirc_sasem]
[<12948bde>] td_free+0x50/0x55 [ohci_hcd]
[<02230079>] usb_hcd_giveback_urb+0x17/0x44
[<12948d1b>] finish_urb+0x85/0xab [ohci_hcd]
[<129499f0>] finish_unlinks+0xf3/0x1db [ohci_hcd]
[<1294a413>] ohci_irq+0xf0/0x133 [ohci_hcd]
[<022300cd>] usb_hcd_irq+0x27/0x4e
[<02106342>] handle_IRQ_event+0x24/0x4f
[<02106723>] do_IRQ+0x62/0xcd
[<021030bf>] default_idle+0x23/0x26
[<02103110>] cpu_idle+0x1f/0x34
[<02338640>] start_kernel+0x17b/0x17f
------------------------------------------------------------

It looks like the kernel has crashed completely after some seconds. It
does so after receiving some commands, and timing out.

Kind Regards,


ir. Jaap van Ekris
Senior Advisor Mission Critical Systems
CIBIT|SERC ICT Advisors
Utrecht, The Netherlands


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/