public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Prasanna P Subash <psubash@turbolinux.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Dual Athlon on 2.2.19 ?
Date: Thu, 24 May 2001 15:36:54 -0400	[thread overview]
Message-ID: <20010524153653.A26439@sventech.com> (raw)
In-Reply-To: <20010522182740.A3125@turbolinux.com> <E152toh-0004uo-00@the-village.bc.nu> <20010524123030.B3485@turbolinux.com>
In-Reply-To: <20010524123030.B3485@turbolinux.com>; from Prasanna P Subash on Thu, May 24, 2001 at 12:30:30PM -0700

On Thu, May 24, 2001, Prasanna P Subash <psubash@turbolinux.com> wrote:
> I have a dual athlon on the 760MP chipset.
> 2.2.20pre1 and 2 dont work. I got it to work partly after applying Johannes
> Erdfel's 760MP patch in io_apic.c. Even after applying the patch, there
> are messages like

2.2.20pre1 and pre2 both have the patch I created already applied. If
you had to apply them yourself then something is wrong.

> hdc: IRQ probe failed(0)
> hdd: IRQ probe failed(0)
> hde: IRQ probe failed(0)
> 
> hdc: lost interrupt
> hdc: lost interrupt
> 
> and then the machine hangs randomly. I an guessing the io_apic does not
> route the interrupts correctly.

That would be the problem.

Which patch of mine did you apply? Which motherboard are you doing your
testing with?

JE


  reply	other threads:[~2001-05-24 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23  1:27 Dual Athlon on 2.2.19 ? Prasanna P Subash
2001-05-24 12:02 ` Alan Cox
2001-05-24 19:30   ` Prasanna P Subash
2001-05-24 19:36     ` Johannes Erdfelt [this message]
2001-05-24 19:45       ` Dan Hollis
2001-05-24 21:13       ` Prasanna P Subash
2001-05-24 21:16         ` Johannes Erdfelt

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=20010524153653.A26439@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psubash@turbolinux.com \
    /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