mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jengelh@linux01.gwdg.de
Cc: andrew@walrond.org, linux-kernel@vger.kernel.org
Subject: Re: Sparc64 kernel message: BUG: soft lockup detected on CPU#3!
Date: Mon, 16 Oct 2006 17:41:00 -0700 (PDT)	[thread overview]
Message-ID: <20061016.174100.48529083.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0610170053280.30479@yvahk01.tjqt.qr>

From: Jan Engelhardt <jengelh@linux01.gwdg.de>
Date: Tue, 17 Oct 2006 00:56:26 +0200 (MEST)

> 
> >> I have not seen this soft lockup so far, though I run a 2.6.16, most 
> >> likely using CONFIG_PROM_CONSOLE (redirected to ttya by prom) because
> >> the machine is not a SUN4V (which SUNHV seems to be for).
> >
> >You could be using one of the other serial drivers.
> >Check the boot messages and your kernel config.
> 
> Thanks for the hint. I am still a bit puzzled why there are so many 
> serial ports detected even though there is only ttya and ttyb on the 
> back:

What kind of system is this?

The two SU serial ports are usually for keyboard and mouse.

If you have 4 SAB ports, I'm guessing this is an Ultra250.
The 3rd and 4th SAB port are usually used for RSC on the
Ultra250 machines, the 1st and 2nd for normal ttya and ttyb
serial.

  reply	other threads:[~2006-10-17  0:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 14:11 andrew
2006-10-16 16:41 ` andrew
2006-10-16 20:54   ` David Miller
2006-10-16 22:02     ` Jan Engelhardt
2006-10-16 22:37       ` David Miller
2006-10-16 22:56         ` Jan Engelhardt
2006-10-17  0:41           ` David Miller [this message]
2006-10-17 16:53             ` Jan Engelhardt
2006-10-17 21:40               ` David Miller
2006-10-16 20:48 ` David Miller

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=20061016.174100.48529083.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@walrond.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®