From: Lisa & Eric Malkowski <malk@charter.net>
To: Nerijus Baliunas <nerijusb@dtiltas.lt>
Cc: linux-smp@vger.kernel.org
Subject: Re: Problem with IBM X Series 220
Date: Wed, 21 Aug 2002 20:01:09 -0400 [thread overview]
Message-ID: <3D6429C5.F164CC2F@charter.net> (raw)
In-Reply-To: Mahogany-0.64.2-25191-20020821-222813.00@nerijus
This sounds awefully similar to a problem I had w/ an IBM 360 series w/
Pentium IV processors (although on a 2.2 kernel). Devices we're not
getting their interrupts and hence never get past SCSI disk detection.
Try booting the kernel with the "noapic" option so all interrupts are on
the first processor (the way a UP kernel would run).
You'll still have all processors for running processes.
Not the most efficient setup, but a good workaround until the APIC related
interrupt problems are fixed.
Since the system won't boot for you to run dmesg, boot with
'console=ttyS0,57600' option (assuming kernel has serial port console
support built in) and capture all the boot messages by connecting a
terminal to first serial port on the system at 57600 8n1. Then send the
captured output to this list so folks can examine the APIC detection and
setup results.
-Eric Malkowski
Nerijus Baliunas wrote:
> Hello,
>
> Both RH 2.4.18-5 and 2.4.19 SMP kernels cannot boot - Adaptec
> AHA-3960D (aic7xxx) cannot detect disks. It just tries and tries -
> I think it does not get interrupts.
>
> Regards,
> Nerijus
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-smp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2002-08-22 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 20:28 Problem with IBM X Series 220 Nerijus Baliunas
2002-08-22 0:01 ` Lisa & Eric Malkowski [this message]
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=3D6429C5.F164CC2F@charter.net \
--to=malk@charter.net \
--cc=linux-smp@vger.kernel.org \
--cc=nerijusb@dtiltas.lt \
/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