mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@mail.ru>
To: dtor_core@ameritech.net
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt
Date: Tue, 29 Mar 2005 23:49:55 +0400	[thread overview]
Message-ID: <200503292349.55319.adobriyan@mail.ru> (raw)
In-Reply-To: <d120d50005032911027c13436e@mail.gmail.com>

On Tuesday 29 March 2005 23:02, Dmitry Torokhov wrote:
> On Tue, 29 Mar 2005 21:28:20 +0400, Alexey Dobriyan <adobriyan@mail.ru> wrote:
> > On Tuesday 29 March 2005 10:27, Dmitry Torokhov wrote:
> > > On Monday 28 March 2005 12:26, Alexey Dobriyan wrote:
> > > > Steps to reproduce for me:
> > > >     * Boot CONFIG_PREEMPT_BKL=y kernel (.config, dmesg are attached)
> > > >     * Start rebooting
> > > >     * Start moving serial mouse (I have Genius NetMouse Pro)
> > > >     * Right after gpm is shut down I see the oops
> > > >     * The system continues to reboot
> > >
> > > Could you try the patch below, please? Thanks!
> > 
> > > Input: serport - fix an Oops when closing port - should not call
> > >        serio_interrupt when serio port is being unregistered.
> > 
> > Doesn't work, sorry. Even worse: rebooting now also produces many pages of
> > oopsen, then hang the system. I'm willing to test any new patches.
> 
> Does it oops at the same place with this patch or at some other place?

I manage to find this in the logs (nothing more :-( ):
============================================================================
Unable to handle kernel NULL pointer dereference at virtual address 00000068
 printing eip:
c0202947
*pde = 00000000
Oops: 0000 [#1]
PREEMPT 
Modules linked in: ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables binfmt_misc uhci_hcd snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd soundcore snd_page_alloc floppy
CPU:    0
EIP:    0060:[<c0202947>]    Not tainted VLI
EFLAGS: 00010282   (2.6.12-rc1-bk2-serio) 
============================================================================
According to vmlinux, c0202947 is at:

c020293e <serport_ldisc_write_wakeup>:
c020293e:       8b 80 78 09 00 00       mov    0x978(%eax),%eax
c0202944:       8b 40 0c                mov    0xc(%eax),%eax
c0202947:       8b 50 68                mov    0x68(%eax),%edx		<<<<====
c020294a:       85 d2                   test   %edx,%edx
c020294c:       74 07                   je     c0202955 <serport_ldisc_write_wakeup+0x17>
c020294e:       8b 52 10                mov    0x10(%edx),%edx
c0202951:       85 d2                   test   %edx,%edx
c0202953:       75 01                   jne    c0202956 <serport_ldisc_write_wakeup+0x18>
c0202955:       c3                      ret
c0202956:       ff d2                   call   *%edx

  reply	other threads:[~2005-03-29 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 17:26 Alexey Dobriyan
2005-03-29  6:27 ` Dmitry Torokhov
2005-03-29 17:28   ` Alexey Dobriyan
2005-03-29 19:02     ` Dmitry Torokhov
2005-03-29 19:49       ` Alexey Dobriyan [this message]
2005-03-29 20:20         ` Dmitry Torokhov
2005-03-30  6:30         ` Dmitry Torokhov
2005-03-30  9:14           ` Alexey Dobriyan
2005-03-30 18:35             ` Dmitry Torokhov

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=200503292349.55319.adobriyan@mail.ru \
    --to=adobriyan@mail.ru \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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®