Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@linux-mips.org, jblache@debian.org,
	rmk+serial@arm.linux.org.uk
Subject: Re: IP22 doesn't shutdown properly
Date: Fri, 24 Feb 2006 20:05:17 +0100	[thread overview]
Message-ID: <20060224190517.GA28013@lst.de> (raw)
In-Reply-To: <20060223221350.GA5239@deprecation.cyrius.com>

On Thu, Feb 23, 2006 at 10:13:50PM +0000, Martin Michlmayr wrote:
> * Martin Michlmayr <tbm@cyrius.com> [2006-02-17 22:58]:
> > When you try to shutdown or reboot an IP22 with 2.6.15 or 2.6.16-rc2,
> > you see that the TERM signal is sent but then nothing happens.  At the
> > beginning, the light on the Indy is green but after about 20 seconds
> > it turns red.  Nothing happens on the console and the machine doesn't
> > turn off.  Seen on Indy and Indigo2.
> [and, as mentioned later, this only happens on serial, not when using
> the bf]
> 
> I've tracked down now while the old 2.6.12 Debian package shut down
> correctly while no recent git does.  The following simple change to
> the serial driver makes the difference for me:
> 
> --- a/drivers/serial/serial_core.c~	2006-02-23 21:58:51.000000000 +0000
> +++ b/drivers/serial/serial_core.c	2006-02-23 21:59:14.000000000 +0000
> @@ -108,7 +108,8 @@
>  static void uart_tasklet_action(unsigned long data)
>  {
>  	struct uart_state *state = (struct uart_state *)data;
> -	tty_wakeup(state->info->tty);
> +	if (state->info->tty)
> +		tty_wakeup(state->info->tty);
>  }
>  
>  static inline void
> 
> I cannot easily check why this change was in Debian's 2.6.12 package
> nor why it's not in Linus' git.  Russell, can you say whether this
> change looks obviously good to you?  If not, I can dig some more and
> see why this change was in our 2.6.12 package.

This patch was dropped when a real fix went into one of the sun serial
drivers with which this issue was seen before.  Please look through
the drivers/serial/sun* changelogs and see what fix needs to be
ported to the ip22zilog driver.

  parent reply	other threads:[~2006-02-24 18:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 22:58 IP22 doesn't shutdown properly Martin Michlmayr
2006-02-18  1:19 ` Kumba
2006-02-18  1:27   ` Martin Michlmayr
2006-02-18 10:36     ` Julien BLACHE
2006-02-19 16:52 ` Ralf Baechle
2006-02-20 18:12   ` Martin Michlmayr
2006-02-20 21:55     ` Ralf Baechle
2006-02-21 13:59     ` Thiemo Seufer
2006-02-21 14:23       ` Stephen P. Becker
2006-02-21 14:31         ` Thiemo Seufer
2006-02-23 21:14           ` Martin Michlmayr
2006-02-23 22:13 ` Martin Michlmayr
2006-02-23 22:43   ` Russell King
2006-02-24  0:39     ` Martin Michlmayr
2006-02-24  1:30       ` Kumba
2006-02-24  8:31       ` Russell King
2006-02-27 10:54         ` Martin Michlmayr
2006-02-24 19:05   ` Christoph Hellwig [this message]
2006-02-27 10:51     ` Martin Michlmayr
2006-02-27 10:52     ` Martin Michlmayr
2006-02-27 11:22       ` Geert Uytterhoeven
2006-02-27 11:25         ` Martin Michlmayr
2006-02-27 12:53         ` Ralf Baechle
2006-02-27 18:30         ` Martin Michlmayr
2006-03-25 17:34       ` Russell King
2006-04-07 16:21         ` Martin Michlmayr

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=20060224190517.GA28013@lst.de \
    --to=hch@lst.de \
    --cc=jblache@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=rmk+serial@arm.linux.org.uk \
    --cc=tbm@cyrius.com \
    /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