public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Nitin Dhingra <nitin.dhingra@dcmtech.co.in>
Cc: "'Florin Andrei'" <florin@sgi.com>,
	linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: noapic strikes back
Date: Thu, 19 Jul 2001 01:30:20 -0400	[thread overview]
Message-ID: <3B56706C.893FD2AE@redhat.com> (raw)
In-Reply-To: <7FADCB99FC82D41199F9000629A85D1A01C6506A@dcmtechdom.dcmtech.co.in>

Nitin Dhingra wrote:
> 
> I guess the problem is mostly of the scsi driver.
> Get the latest version scsi driver of that particular
> card and then try again.

No, this has been gone over a thousand times already.  It's the interrupt
routing table in these particular Intel motherboard is busted.

> -----Original Message-----
> From: Florin Andrei [mailto:florin@sgi.com]
> Sent: Thursday, July 19, 2001 1:05 AM
> To: linux-xfs@oss.sgi.com; seawolf-list@redhat.com; dledford@redhat.com;
> linux-kernel@vger.kernel.org
> Subject: noapic strikes back
> 
> I have a SGI 1200 (L440GX+ motherboard, dual PIII) and i'm trying to
> install at least one version of Red Hat 7.1 on it.
> The problem is, while booting up the installer, when it comes to loading
> up the SCSI driver (AIC7xxx) the system is frozen.
> 
> I tried the following boot disks:
> - stock Red Hat 7.1
> - Doug Ledford's updates from people.redhat.com
> - SGI XFS 1.0.1
> 
> I tried to boot the installer with and without "noapic" option.
> 
> I tried to enable and disable the APIC option in BIOS ("PCI IRQs to
> IO-APIC Mapping").
> 
> I tried all the combinations of these. No luck. :-(
> 
> Please, is there anything to do about this problem? I *have* to install
> something newer than RH7.0 on that system.
> 
> Guys, i will try whatever boot disks you will send to me. I'm willing to
> be you guinea pig. :-) Just let's kill the APIC problem for good!
> 
> --
> Florin Andrei
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

 Doug Ledford <dledford@redhat.com>  http://people.redhat.com/dledford
      Please check my web site for aic7xxx updates/answers before
                      e-mailing me about problems

  reply	other threads:[~2001-07-19  5:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19  4:00 noapic strikes back Nitin Dhingra
2001-07-19  5:30 ` Doug Ledford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18 19:35 Florin Andrei
2001-07-18 19:46 ` Doug Ledford
2001-07-18 23:34   ` Florin Andrei
2001-07-19  4:26     ` Doug Ledford
2001-07-18 20:10 ` Jure Pecar
2001-07-18 21:04 ` daniel

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=3B56706C.893FD2AE@redhat.com \
    --to=dledford@redhat.com \
    --cc=florin@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=nitin.dhingra@dcmtech.co.in \
    /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