From: "Gabor Z. Papp" <gzp@papp.hu>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Mark Haverkamp <markh@osdl.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.4 and aacraid dmesg
Date: Wed, 22 Jun 2005 17:25:11 +0200 [thread overview]
Message-ID: <x6ll5276so@gzp> (raw)
In-Reply-To: 60807403EABEB443939A5A7AA8A7458B0152136F@otce2k01.adaptec.com
* "Salyzyn, Mark" <mark_salyzyn@adaptec.com>:
| The message is coming from the PCI subsystem. Yes it is triggered by the
| pending driver load and requesting card pci resources, but such messages
| are usually a result of issues with the Motherboard BIOS or Hardware.
The system is working fine, stable, without errors. I was just
courious about this kernel msg flood.
| on PCI address 03:0d.0 and 03:09.0 are sharing IRQ 4. The 'info' message
| is printed every time the pcibios_enable_device() call is made. The
| interrupt sharing is assigned by the Motherboard BIOS and if you have
| subsequent problems with the operation of the card(s) or the system, you
| should investigate updating the Motherboard BIOS or go into the
| motherboard BIOS setup and see if you can reassign the PCI (IRQ)
| resources.
Okay. The other device at 03:09.0 is a:
Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
| The spurious 8259A interrupt message *may* be viewed as a problem.
I'm getting this sh*t from 2.4.18 or so... I think its another story.
Anyway, I love this 2120S, boots quite slooowly, but works fine and
stable.
Ah, the chip is *very* *very* *very* hot on the card, is that normal?
next parent reply other threads:[~2005-06-22 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60807403EABEB443939A5A7AA8A7458B0152136F@otce2k01.adaptec.com>
2005-06-22 15:25 ` Gabor Z. Papp [this message]
2005-06-22 15:43 2.4 and aacraid dmesg Salyzyn, Mark
2005-06-22 15:59 ` Gabor Z. Papp
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=x6ll5276so@gzp \
--to=gzp@papp.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=markh@osdl.org \
/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