public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 18:29:47 +0300	[thread overview]
Message-ID: <87r6uluzkk.fsf@javad.com> (raw)
In-Reply-To: <554564654653216610@wsc.cz> (Jiri Slaby's message of "Wed, 27 Dec 2006 14:36:56 +0100 (CET)")

Jiri Slaby <jirislaby@gmail.com> writes:

>> Jiri Slaby <jirislaby@gmail.com> writes:
>> 
>> > 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]
>
> Yes, port->tty still somewhere becomes NULL -- does this patch help?

In addition to my previous answer. I've performed the same tests with
regular PC serial port. The issues with "Disabling Irq #N" and with I/O
error on open() exist with this port as well, so they aren't
mxser-specific.  I wasn't able to reproduce oopses, so they do seem to
be mxser-specific.

-- Sergei.

  parent reply	other threads:[~2006-12-27 15:30 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
2006-12-27 13:36                               ` Jiri Slaby
2006-12-27 14:00                                 ` Sergei Organov
2006-12-27 15:29                                 ` Sergei Organov [this message]
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=87r6uluzkk.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