public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Reuben Farrelly <reuben-lkml@reub.net>
To: unlisted-recipients:; (no To-header on input)
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, rmk+serial@arm.linux.org.uk
Subject: Re: 2.6.12-rc1-mm3
Date: Mon, 28 Mar 2005 23:03:45 +1200	[thread overview]
Message-ID: <4247E491.2070601@reub.net> (raw)
In-Reply-To: <fa.dhfu5qn.1l68cj1@ifi.uio.no>

Reuben Farrelly wrote:

> 
> I'm repeatably getting this crash on shutdown in -mm3, and a few 
> releases earlier (but I can't be certain it was the same crash..)
> 
> Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> ttyS4 at I/O 0xa400 (irq = 16) is a 16550A
> ttyS5 at I/O 0xa408 (irq = 16) is a 16550A
> 
> This _may_ be the culprit, but I'm not sure:
> 
> 03:03.0 Serial controller: Timedia Technology Co Ltd PCI2S550 (Dual 
> 16550 UART) (rev 01) (prog-if 02 [16550])
>         Subsystem: Timedia Technology Co Ltd: Unknown device 0002
>         Flags: stepping, medium devsel, IRQ 16
>         I/O ports at a400 [size=32]

Ugh.  I'm an idiot, that will teach me for having two sessions to boxes 
running at once.

Wrong info above, but the trace is still valid.

Correct info follows:

ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS14 at I/O 0xb400 (irq = 217) is a 16550A
ttyS15 at I/O 0xb000 (irq = 217) is a 16550A

06:02.0 Serial controller: NetMos Technology PCI 9835 Multi-I/O 
Controller (rev
01) (prog-if 02 [16550])
         Subsystem: LSI Logic / Symbios Logic 2S (16C550 UART)
         Flags: medium devsel, IRQ 217
         I/O ports at b400 [size=8]
         I/O ports at b000 [size=8]
         I/O ports at ac00 [size=8]
         I/O ports at a800 [size=8]
         I/O ports at a400 [size=8]
         I/O ports at a000 [size=16]


> The board is an Intel D925XCV.
> 
> Shutdown goes like this:   (yes, hyperterminal sucks for the ^M 
> characters, sorry)

<trace omitted>

reuben

       reply	other threads:[~2005-03-28 11:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.e0rq9h4.h02o3e@ifi.uio.no>
     [not found] ` <fa.dhfu5qn.1l68cj1@ifi.uio.no>
2005-03-28 11:03   ` Reuben Farrelly [this message]
     [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           ` 2.6.12-rc1-mm3 Reuben Farrelly
2005-03-29  6:29   ` 2.6.12-rc1-mm3 Dmitry Torokhov
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=4247E491.2070601@reub.net \
    --to=reuben-lkml@reub.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+serial@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