All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Pool <mbp@sourcefrog.net>
To: linux-ia64@vger.kernel.org
Subject: Re: oops in serial_out in 2.6.5
Date: Tue, 13 Apr 2004 23:55:45 +0000	[thread overview]
Message-ID: <20040413235544.GF13754@hp.com> (raw)
In-Reply-To: <20040413063757.GA11350@hp.com>

[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]

On 13 Apr 2004, Alex Williamson <alex.williamson@hp.com> wrote:
> 
>    What's in your /var/lib/setserial/autoserial.conf?  What does the
> kernel print out for serial ports on bootup?  I'm guessing they're out
> of sync.  It would be nice if we could stop the oops, but I'm guessing
> the quicker fix is to reconfigure setserial to "kernel" configuration. 
> Your ttyS0 on irq 49 is likely the builtin UART, not the MP UART.  If
> that fixes it, please report back the differences in config versus
> kernel serial port listings.  Thanks,

Autoserial.conf has

###PORT STATE GENERATED USING AUTOSAVE-ONCE###
###AUTOSAVE-ONCE###
###AUTOSAVE-ONCE###
###AUTOSAVE###
#
# If you want to configure this file by hand, use
# dpkg --configure setserial
# and change the configuration mode of the file to MANUAL. If you do not do this# this file may be overwritten automatically the next time you upgrade the
# package.
#
/dev/ttyS0 uart 16550A port 0x0000 irq 59 baud_base 115200 spd_normal skip_test
auto_irq
/dev/ttyS1 uart 16550A port 0x0000 irq 60 baud_base 115200 spd_normal skip_test
auto_irq
/dev/ttyS2 uart 16550A port 0x0000 irq 57 baud_base 115200 spd_normal skip_test
/dev/ttyS3 uart 16550A port 0x0000 irq 57 baud_base 115200 spd_normal skip_test
/dev/ttyS4 uart 16550A port 0x0000 irq 57 baud_base 115200 spd_normal skip_test
/dev/ttyS5 uart 16550A port 0x0000 irq 57 baud_base 115200 spd_normal skip_test

The kernel reported 

Apr 13 16:18:25 kate kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Apr 13 16:18:25 kate kernel: ttyS0 at MMIO 0xf4050000 (irq = 49) is a 16550A
Apr 13 16:18:25 kate kernel: GSI 0x22(high,edge) -> CPU 0x0000 vector 75
Apr 13 16:18:25 kate kernel: ttyS1 at MMIO 0xff5e0000 (irq = 75) is a 16550A
Apr 13 16:18:25 kate kernel: GSI 0x23(high,edge) -> CPU 0x0000 vector 76
Apr 13 16:18:25 kate kernel: ttyS2 at MMIO 0xff5e2000 (irq = 76) is a 16550A
Apr 13 16:18:25 kate kernel: PCI: Found IRQ 49 for device 0000:e0:01.0
Apr 13 16:18:25 kate kernel: IOSAPIC: vector 49 -> CPU 0x0100, enabled
Apr 13 16:18:25 kate kernel: ttyS3 at MMIO 0xf4051000 (irq = 49) is a 16450
Apr 13 16:18:25 kate kernel: PCI: Found IRQ 49 for device 0000:e0:01.1
Apr 13 16:18:25 kate kernel: IOSAPIC: vector 49 -> CPU 0x0000, enabled
Apr 13 16:18:25 kate kernel: Couldn't register serial port 0000:e0:01.1: -28


I got my machine working again by just removing setserial.  Does it
ever do anything useful on legacy-free ia64?  I wouldn't think people
ever set IRQs or IO addresses by hand after bootup.

-- 
Martin 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-04-13 23:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  6:37 oops in serial_out in 2.6.5 Martin Pool
2004-04-13 14:34 ` Alex Williamson
2004-04-13 16:21 ` Matthew Wilcox
2004-04-13 23:55 ` Martin Pool [this message]
2004-04-14 15:25 ` Bjorn Helgaas
2004-04-15  2:35 ` Martin Pool

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=20040413235544.GF13754@hp.com \
    --to=mbp@sourcefrog.net \
    --cc=linux-ia64@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.