public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Reuben Farrelly <reuben-lkml@reub.net>
To: Andrew Morton <akpm@osdl.org>
Cc: dtor_core@ameritech.net, rmk+lkml@arm.linux.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc1-mm3
Date: Thu, 26 May 2005 22:11:26 +1200	[thread overview]
Message-ID: <4295A0CE.3020005@reub.net> (raw)
In-Reply-To: <20050525212044.67271b83.akpm@osdl.org>

Hi,

On 26/05/2005 4:20 p.m., Andrew Morton wrote:
> Reuben Farrelly <reuben-lkml@reub.net> wrote:
> 
>>>Reuben, could you please try the patch below? Thanks!
>>>
>>>Russell, could you please tell me if ldisc->write_wakeup (tty_wakwup) and
>>>ldisc->read are allowed to be called from an IRQ context? IOW I wonder if
>>>I can use spil_lock_bh instead of spil_lock_irqsave to protect serport
>>>flags.
>>>
>>>--
>>>Dmitry
>>>
>>> serport.c |   98 
>>>+++++++++++++++++++++++++++++++++++++++++++-------------------
>>> 1 files changed, 68 insertions(+), 30 deletions(-)
>>>
>>>Index: dtor/drivers/input/serio/serport.c
>>>===================================================================
>>>--- dtor.orig/drivers/input/serio/serport.c
>>>+++ dtor/drivers/input/serio/serport.c
>>>@@ -27,11 +27,15 @@ MODULE_LICENSE("GPL");
>>> MODULE_ALIAS_LDISC(N_MOUSE);
>>
>>
>>I've done some testing this afternoon and it seems that this patch 
>>fixes the problem in -mm4.  I don't even have a serial 
>>mouse/keyboard, but do have a serial PCI card onboard.  The box has a 
>>USB connection to a Belkin KVM instead of directly attached input devices.
>>
>>I also note that it is occurring on kernel-smp-2.6.11-1.1219_FC4 - so 
>>it is probably a problem in mainline as well as -mm.
> 
> 
> Can you please confirm that the above fix is present in 2.6.12-rc5 and that
> 2.6.12-rc5 is working OK?

The fix is definitely in -rc5 (thanks), and without doubt fixed the problem I 
was seeing (thanks Dmitry).  I haven't tested on a vanilla 2.6.12-rc5, but I 
can confirm that 2.6.12-rc4-mm* releases have not had the problem.  The patch 
was of course in -rc4-mm* and possibly earlier?

> >>Now I'm crashing a bit further through the shutdown, here's the stacktrace:
> 
> 
> Is this still occurring in either 2.6.12-rc5 or 2.6.12-rc5-mm1?

2.6.12-rc4-mm* releases have been stable, I haven't seen any oopses for a few 
weeks now.

If confirmation is required in -rc5 then I'm happy to attempt this, but I 
don't think it's at all likely given I haven't seen any oopses at all since 
that patch was included in -mm, and the patch is now in upstream.

Btw, I didn't see a lkml-announce message about -rc5-mm1 being released :(  No 
big deal really...

reuben

  reply	other threads:[~2005-05-26 10:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.h3qui0k.n6uf30@ifi.uio.no>
2005-03-28 10:30 ` 2.6.12-rc1-mm3 Reuben Farrelly
2005-03-28 11:02   ` 2.6.12-rc1-mm3 Russell King
2005-03-30 18:41     ` 2.6.12-rc1-mm3 Dmitry Torokhov
2005-04-02  3:46       ` 2.6.12-rc1-mm3 Reuben Farrelly
2005-05-26  4:20         ` 2.6.12-rc1-mm3 Andrew Morton
2005-05-26 10:11           ` Reuben Farrelly [this message]
2005-03-29  6:29   ` 2.6.12-rc1-mm3 Dmitry Torokhov
     [not found] <fa.e0rq9h4.h02o3e@ifi.uio.no>
     [not found] ` <fa.dhfu5qn.1l68cj1@ifi.uio.no>
2005-03-28 11:03   ` 2.6.12-rc1-mm3 Reuben Farrelly
2005-03-26  4:23 2.6.12-rc1-mm3 Paul Blazejowski
  -- strict thread matches above, loose matches on Subject: below --
2005-03-25  9:37 2.6.12-rc1-mm3 Chuck Ebbert
2005-03-25  8:21 2.6.12-rc1-mm3 Andrew Morton
2005-03-25 10:46 ` 2.6.12-rc1-mm3 Brice Goglin
2005-03-25 16:46 ` 2.6.12-rc1-mm3 Borislav Petkov
2005-03-31 13:05   ` 2.6.12-rc1-mm3 Borislav Petkov
2005-03-31 20:11     ` 2.6.12-rc1-mm3 Andrew Morton
2005-03-31 20:57       ` 2.6.12-rc1-mm3 Borislav Petkov
2005-03-25 18:17 ` 2.6.12-rc1-mm3 Barry K. Nathan
2005-03-26  1:43 ` 2.6.12-rc1-mm3 Jason Uhlenkott

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=4295A0CE.3020005@reub.net \
    --to=reuben-lkml@reub.net \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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