All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olli Lounela <olli@mpoli.fi>
To: "Leonard N. Zubkoff" <lnz@dandelion.com>
Cc: linux-kernel@vger.kernel.org, support@mylex.com
Subject: Re: fwd: Mylex dac960 not SMP-safe?
Date: Tue, 13 Feb 2001 03:07:16 +0200	[thread overview]
Message-ID: <20010213030716.A31697@mpoli.fi> (raw)
In-Reply-To: <20010212134757.A18423@mpoli.fi> <200102121702.f1CH20U03841@dandelion.com> <20010213015501.J17002@mpoli.fi> <20010213022806.A31582@mpoli.fi>
In-Reply-To: <20010213022806.A31582@mpoli.fi>

On Tue, Feb 13, 2001 at 02:28:06AM +0200, Olli Lounela wrote:
>
> Okay, I goofed. The motherboard reset the interrupts to the same old stoopid
> values when I shuffled the cards. I have now separated them, no difference.

Progress: not only did I goof, I was wrong too.

This time it booted once the network timed out, but the eepro is not
functioning properly; it seems unable to receive. I can see it sends alright
from the dhcpserver log.

IRQ's are now

   Mylex    10
   aic7880  17
   eepro    18
   VGA      19

Mylex still hangs without nosmp. IRQ routing problem in APIC initialization,
maybe?

Darn this old piece of junk is slow to boot...

-- 
    Olli               ...and he thought I'm serious! Hahahaha...
-
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://vger.kernel.org/lkml/

      reply	other threads:[~2001-02-13  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010212134757.A18423@mpoli.fi>
2001-02-12 17:02 ` fwd: Mylex dac960 not SMP-safe? Leonard N. Zubkoff
2001-02-12 23:55   ` Olli Lounela
2001-02-13  0:28     ` Olli Lounela
2001-02-13  1:07       ` Olli Lounela [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=20010213030716.A31697@mpoli.fi \
    --to=olli@mpoli.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnz@dandelion.com \
    --cc=support@mylex.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 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.