From: Sergei Organov <osv@javad.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: moxa serial driver testing
Date: Wed, 27 Dec 2006 14:48:13 +0300 [thread overview]
Message-ID: <87mz595zlu.fsf@javad.com> (raw)
In-Reply-To: <552766292581216610@wsc.cz> (Jiri Slaby's message of "Sat, 23 Dec 2006 02:35:46 +0100 (CET)")
Jiri Slaby <jirislaby@gmail.com> writes:
> osv@javad.com wrote:
>> Hi Jiri,
>>
>> I've figured out that both old and new mxser drivers have two similar
>> problems:
>>
>> 1. When there are data coming to a port, sometimes opening of the port
>> entirely locks the box. This is quite reproducible. Any idea what's
>> wrong and how can I help to debug it?
>
> Could you test the patch below, if something changes?
Just tested with low_latency commented out. Still oopses:
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000008
printing eip:
f8f1730f
*pde = 00000000
Oops: 0000 [#1]
SMP
Modules linked in: nvidia agpgart ipv6 nfs lockd nfs_acl sunrpc dm_mod sr_mod sbp2 ieee1394 ide_generic ide_disk e1000 snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer i2c_i801 tsdev psmouse snd soundcore snd_page_alloc i2c_core serio_raw parport_pc parport mxser_new evdev floppy pcspkr rtc ext3 jbd mbcache usb_storage usbhid ide_cd cdrom sd_mod uhci_hcd piix usbcore skge ata_piix libata scsi_mod generic ide_core thermal processor fan
CPU: 0
EIP: 0060:[<f8f1730f>] Tainted: P VLI
EFLAGS: 00010046 (2.6.18-3-686 #1)
EIP is at mxser_receive_chars+0x21b/0x249 [mxser_new]
eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000286
esi: f8f1c79c edi: 00000001 ebp: c1be6000 esp: c0313efc
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, ti=c0312000 task=c02c76a0 task.ti=c0312000)
Stack: c0313f48 f8f1c8a8 0000903d 00000000 00000fff 000000ff 00000286 0000007b
f8f1c79c 00000006 0000007f 000000c6 f8f17d7a 00000007 00000008 00000080
00000000 00000000 f8f1bdc0 00000060 df985500 00000000 00000000 0000003a
Call Trace:
[<f8f17d7a>] mxser_interrupt+0x15f/0x1e6 [mxser_new]
[<c013fb83>] handle_IRQ_event+0x23/0x49
[<c013fc3c>] __do_IRQ+0x93/0xe8
[<c01050e5>] do_IRQ+0x43/0x52
[<c01036b6>] common_interrupt+0x1a/0x20
[<c0101b91>] mwait_idle+0x25/0x38
[<c0101b52>] cpu_idle+0x9f/0xb9
[<c03186fd>] start_kernel+0x379/0x380
Code: ed ff ff eb 1f 8b 06 83 78 18 00 75 17 8b 56 08 83 c2 05 ec 8b 14 24 0f b6 c0 a8 01 89 02 0f 85 d4 fe ff ff 8b 46 04 8b 54 24 18 <8b> 40 08 01 3c 85 c4 ec f1 f8 8b 44 24 04 01 be f4 00 00 00 01
EIP: [<f8f1730f>] mxser_receive_chars+0x21b/0x249 [mxser_new] SS:ESP 0068:c0313efc
<0>Kernel panic - not syncing: Fatal exception in interrupt
BUG: warning at arch/i386/kernel/smp.c:547/smp_call_function()
[<c010f5a3>] smp_call_function+0x53/0xfe
[<c011d97e>] printk+0x14/0x18
[<c010f661>] smp_send_stop+0x13/0x1c
[<c011cfc6>] panic+0x4c/0xe2
[<c0104013>] die+0x256/0x28a
[<c01156e0>] do_page_fault+0x3b4/0x481
[<c01f9f8d>] tty_buffer_request_room+0x107/0x112
[<c011532c>] do_page_fault+0x0/0x481
[<c01037f9>] error_code+0x39/0x40
[<f8f1730f>] mxser_receive_chars+0x21b/0x249 [mxser_new]
[<f8f17d7a>] mxser_interrupt+0x15f/0x1e6 [mxser_new]
[<c013fb83>] handle_IRQ_event+0x23/0x49
[<c013fc3c>] __do_IRQ+0x93/0xe8
[<c01050e5>] do_IRQ+0x43/0x52
[<c01036b6>] common_interrupt+0x1a/0x20
[<c0101b91>] mwait_idle+0x25/0x38
[<c0101b52>] cpu_idle+0x9f/0xb9
[<c03186fd>] start_kernel+0x379/0x380
next prev parent reply other threads:[~2006-12-27 11:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45222E7E.3040904@gmail.com>
[not found] ` <87wt7hw97c.fsf@javad.com>
[not found] ` <4522ABC3.2000604@gmail.com>
[not found] ` <878xjx6xtf.fsf@javad.com>
[not found] ` <4522B5C2.3050004@gmail.com>
[not found] ` <87mz8borl2.fsf@javad.com>
[not found] ` <45251211.7010604@gmail.com>
[not found] ` <87zmcaokys.fsf@javad.com>
[not found] ` <45254F61.1080502@gmail.com>
[not found] ` <87vemyo9ck.fsf@javad.com>
[not found] ` <4af2d03a0610061355p5940a538pdcbd2cda249161e8@mail.gmail.com>
[not found] ` <87vemtnbyg.fsf@javad.com>
[not found] ` <452A1862.9030502@gmail.com>
[not found] ` <87r6urket6.fsf@javad.com>
2006-12-22 19:54 ` moxa serial driver testing Jiri Slaby
2006-12-23 1:09 ` Jiri Slaby
2006-12-23 1:35 ` Jiri Slaby
2006-12-23 9:09 ` Sergei Organov
2006-12-25 11:26 ` Sergei Organov
2006-12-25 13:41 ` Sergei Organov
2006-12-25 18:39 ` Jiri Slaby
2006-12-25 18:49 ` Sergei Organov
2006-12-25 16:17 ` moxa serial driver testing (oopses) Sergei Organov
2006-12-27 11:09 ` moxa serial driver testing Sergei Organov
2006-12-27 11:48 ` Sergei Organov [this message]
2006-12-27 13:36 ` Jiri Slaby
2006-12-27 14:00 ` Sergei Organov
2006-12-27 15:29 ` Sergei Organov
2006-12-28 17:14 ` Sergei Organov
2006-12-28 23:32 ` Jiri Slaby
2006-12-29 8:56 ` Sergei Organov
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=87mz595zlu.fsf@javad.com \
--to=osv@javad.com \
--cc=akpm@osdl.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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