From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alexey Dobriyan <adobriyan@mail.ru>
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 14:02:00 -0500 [thread overview]
Message-ID: <d120d50005032911027c13436e@mail.gmail.com> (raw)
In-Reply-To: <200503292128.20140.adobriyan@mail.ru>
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?
Btw, what happen if you try to kill inputattach or GPM or both without
rebooting?
--
Dmitry
next prev parent reply other threads:[~2005-03-29 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 17:26 2.6.12-rc1-bk2+PREEMPT_BKL: Oops at serio_interrupt Alexey Dobriyan
2005-03-29 6:27 ` Dmitry Torokhov
2005-03-29 17:28 ` Alexey Dobriyan
2005-03-29 19:02 ` Dmitry Torokhov [this message]
2005-03-29 19:49 ` Alexey Dobriyan
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=d120d50005032911027c13436e@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=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