From: Stefan Bauer <stefan.bauer@cs.tu-chemnitz.de>
To: Jarod Wilson <jwilson@redhat.com>
Cc: linux-kernel@vger.kernel.org, Janne Grunau <j@jannau.net>,
Christoph Bartelmus <lirc@bartelmus.de>
Subject: Re: [PATCH 02/18] lirc serial port receiver/transmitter device driver
Date: Fri, 19 Sep 2008 20:05:11 +0200 [thread overview]
Message-ID: <200809192005.12068.stefan.bauer@cs.tu-chemnitz.de> (raw)
In-Reply-To: <200809160008.43218.jwilson@redhat.com>
On Tuesday 16 September 2008 06:08, Jarod Wilson wrote:
> Current git tree works for receiving IR signals via lirc_serial (tested by
> Janne) and via lirc_mceusb2 (tested by me). Something is still slightly
> haywire with lirc_i2c though. It registers fine, but IR signals simply
> aren't making it to lircd. Probably unrelated to the dynamic device num
> changes, looking into it.
Thank you for keeping me up to date, here are my test results with todays
(36e60bd457588b2a2fd37e0c1d0652a9fe214d85) git:
- Compiles fine, except some warnings:
drivers/input/lirc/lirc_dev.h:60:
warning: 'lirc_buffer_available' defined but not used
drivers/input/lirc/lirc_dev.h:72:
warning: 'lirc_buffer_write' defined but not used
drivers/input/lirc/lirc_dev.h:56:
warning: 'lirc_buffer_empty' defined but not used
drivers/input/lirc/lirc_dev.h:60:
warning: 'lirc_buffer_available' defined but not used
drivers/input/lirc/lirc_dev.h:66:
warning: 'lirc_buffer_read' defined but not used
- Module loads fine, with this messages:
lirc_dev: IR Remote Control driver registered, major 252
lirc_serial: auto-detected active low receiver
lirc_dev: lirc_register_driver: sample_rate: 0
- But lircd crashes immediately every time irexec/irw tries to connect:
BUG: unable to handle kernel NULL pointer dereference at 0000000c
IP: [<cabc9006>] :lirc_dev:lirc_buffer_clear+0x6/0x17
*pde = 00000000
Oops: 0002 [#1]
Modules linked in: lirc_serial lirc_dev ves1820 arc4 ecb crypto_blkcipher
cryptomgr crypto_algapi rt61pci rt2x00pci rt2x00lib led_class dvb_ttpci
saa7146_vv saa7146 videobuf_dma_sg videobuf_core mac80211 videodev
v4l1_compat ttpci_eeprom ehci_hcd uhci_hcd cfg80211 eeprom_93cx6
Pid: 2501, comm: lircd Not tainted (2.6.27-rc5 #7)
EIP: 0060:[<cabc9006>] EFLAGS: 00010046 CPU: 0
EIP is at lirc_buffer_clear+0x6/0x17 [lirc_dev]
EAX: 00000000 EBX: c7825cc0 ECX: cabc94f1 EDX: 00000246
ESI: fffffff0 EDI: c726537c EBP: c6bdf000 ESP: c6b73eac
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process lircd (pid: 2501, ti=c6b72000 task=c72ef7a0 task.ti=c6b72000)
Stack: cabc958f 00000000 c7825d3c c014e15c 00000000 c6bdf000 c726537c 00000000
c014e09b c014b052 c78c2900 c759fd80 c6b73f14 c6bdf000 c6b73f14 00000003
c014b156 c6bdf000 00000000 00000000 00000000 c01544ae 00000002 00000026
Call Trace:
[<cabc958f>] irctl_open+0x9e/0x131 [lirc_dev]
[<c014e15c>] chrdev_open+0xc1/0xf6
[<c014e09b>] chrdev_open+0x0/0xf6
[<c014b052>] __dentry_open+0xf2/0x1da
[<c014b156>] nameidata_to_filp+0x1c/0x2c
[<c01544ae>] do_filp_open+0x28b/0x545
[<c015bc37>] alloc_fd+0x46/0xad
[<c014ae8d>] do_sys_open+0x42/0xb6
[<c014af45>] sys_open+0x1e/0x23
[<c010297d>] sysenter_do_call+0x12/0x25
[<c02f0000>] ioctl_standard_iw_point+0x12d/0x200
=======================
Code: <c7> 40 0c 00 00 00 00 c7 40 08 00 00 00 00 52 9d c3 53 89 c3 8b 40
EIP: [<cabc9006>] lirc_buffer_clear+0x6/0x17 [lirc_dev] SS:ESP 0068:c6b73eac
---[ end trace 782e5196b9791a10 ]---
If wanted I could start a bisect on this.
Regards,
Stefan
next prev parent reply other threads:[~2008-09-19 18:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 19:49 Stefan Bauer
2008-09-12 16:24 ` Jarod Wilson
2008-09-13 0:26 ` Janne Grunau
2008-09-13 8:41 ` Stefan Bauer
2008-09-15 3:55 ` Jarod Wilson
2008-09-15 18:20 ` Jarod Wilson
2008-09-16 4:08 ` Jarod Wilson
2008-09-18 14:00 ` Jarod Wilson
2008-09-19 18:05 ` Stefan Bauer [this message]
2008-09-19 18:26 ` Janne Grunau
2008-09-19 18:53 ` Stefan Bauer
2008-09-19 19:24 ` Janne Grunau
2008-09-20 0:10 ` Janne Grunau
2008-09-26 19:42 ` Stefan Bauer
2008-09-19 18:54 ` Jarod Wilson
2008-09-19 19:12 ` Stefan Bauer
2008-09-13 7:09 ` Christoph Bartelmus
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 4:05 [PATCH 0/18] linux infrared remote control drivers Jarod Wilson
2008-09-09 4:05 ` [PATCH 01/18] lirc core device driver infrastructure Jarod Wilson
2008-09-09 4:05 ` [PATCH 02/18] lirc serial port receiver/transmitter device driver Jarod Wilson
2008-09-09 16:14 ` Jonathan Corbet
2008-09-09 19:51 ` Stefan Lippers-Hollmann
2008-09-09 19:56 ` Jarod Wilson
2008-09-10 17:40 ` Jarod Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200809192005.12068.stefan.bauer@cs.tu-chemnitz.de \
--to=stefan.bauer@cs.tu-chemnitz.de \
--cc=j@jannau.net \
--cc=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lirc@bartelmus.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®