From: Petr Matula <pem@informatics.muni.cz>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Petr Matula <pem@informatics.muni.cz>,
"Dunlap, Randy" <randy.dunlap@intel.com>,
MOLNAR Ingo <mingo@chiara.elte.hu>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: int. assignment on SMP + ServerWorks chipset
Date: Thu, 18 Jan 2001 08:43:40 +0100 [thread overview]
Message-ID: <20010118084340.A12255709@aisa.fi.muni.cz> (raw)
In-Reply-To: <20010117185047.A13171968@aisa.fi.muni.cz> <Pine.LNX.4.10.10101171332420.10151-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10101171332420.10151-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Wed, Jan 17, 2001 at 01:33:42PM -0800
On Wed, Jan 17, 2001 at 01:33:42PM -0800, Linus Torvalds wrote:
> Did you also remove the two lines that disabled pirq routing if an IO-APIC
> was enabled?
Yesterday not, today yes. But it's the same.
> > Kernel with these changes can't detect my SCSI drive. It prints these messages
> > in cycle:
>
> Which SCSI adapter is this? It may be that you have one of the drivers
> that does not do "pci_enable_dev()" at initialization time..
SCSI storage controller: Adaptec 7899P (rev 0).
IRQ 16.
Master Capable. Latency=72. Min Gnt=40.Max Lat=25.
I/O at 0x5800 [0x58ff].
Non-prefetchable 64 bit memory at 0xfd000000 [0xfd000fff].
Used kernel options:
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_SCSI_DEBUG_QUEUES=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_RESET_DELAY=10
Petr
---------------------------------------------------------------
Petr Matula pem@fi.muni.cz
http://www.fi.muni.cz/~pem
---------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-18 7:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D5E932F578EBD111AC3F00A0C96B1E6F07DBDF24@orsmsx31.jf.intel.com>
2001-01-16 4:49 ` Linus Torvalds
2001-01-16 5:35 ` Tim Hockin
2001-01-17 10:03 ` Overriding BIOS settings with kernel 2.4.0 bandit2
2001-01-18 3:23 ` Matt Kemner
2001-01-17 17:50 ` int. assignment on SMP + ServerWorks chipset Petr Matula
2001-01-17 18:11 ` Andre Hedrick
2001-01-17 21:33 ` Linus Torvalds
2001-01-18 7:43 ` Petr Matula [this message]
2001-01-17 1:39 Duncan Laurie
2001-01-17 17:53 ` Petr Matula
2001-01-18 8:58 ` Petr Matula
2001-01-22 4:54 ` Duncan Laurie
2001-01-22 22:05 ` Randy.Dunlap
2001-01-22 23:46 ` Duncan Laurie
2001-01-24 8:43 ` Petr Matula
2001-01-22 0:26 Dunlap, Randy
2001-01-22 17:01 Dunlap, Randy
2001-01-23 1:52 Dunlap, Randy
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=20010118084340.A12255709@aisa.fi.muni.cz \
--to=pem@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@chiara.elte.hu \
--cc=randy.dunlap@intel.com \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®