From: "Keith Warno" <keith.warno@valaran.com>
To: "lkml \(E-mail\)" <linux-kernel@vger.kernel.org>
Subject: 2.4.19 SCSI whoas.
Date: Tue, 6 Aug 2002 15:41:39 -0400 [thread overview]
Message-ID: <001b01c23d81$497b2d40$8806a8c0@kwvaio> (raw)
Greetings. I've poked around in the lkml archives with little luck re:
these issues so bear with me.
On an x86 system with:
abit kt7a mobo
(256*5)MB RAM
Adaptec 29160 controller
- Seagate ST336704LVC 34GB disk (LVD & running at 160MB/s)
- Yamaha CDW8424S (attached via 68pin Wide internal cable, running 20MB/s)
2 IDE disks (one UDMA33, another UDMA66, on the same ide channel, both with
dma enabled)
1 IDE DVDROM/CDRW as secondary master, using the kernel's ide-scsi driver.
I've started seeing the following kernel message over and over:
Warning - running *really* short on DMA buffers
which is emitted by drivers/scsu/scsi_merge.c:882
Why? This is my question. :) It seems to happen when there's a lot of
activity on the SCSI disk, ie, when generating ISO images via mkisofs. The
call to scsi_malloc() on drivers/scsu/scsi_merge.c:872 appears to fail but I
haven't a clue why.
In addition to this DMA message, I often see the following:
scsi0: PCI error Interrupt at seqaddr = 0x9
scsi0: Data Parity Error Detected during address or write data phase
The 'seqaddr' varies; it's most frequently 0x8 or 0x9. This message pops
up, it appears, when there is a lot of IDE disk activity. This has been
showing up since 2.4.16 or so.
Yes, SCSI termination is as it should be. I've also tried 3 different 29160
cards (various BIOS versions), 3 different LVD cables, 2 different 68pin
wide cables, all whilst bouncing the card around to different PCI slots.
The 29160 is the only device on irq 11.
ANy and all useful feedback will be much appreciated.
Regards,
kw.
reply other threads:[~2002-08-06 19:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001b01c23d81$497b2d40$8806a8c0@kwvaio' \
--to=keith.warno@valaran.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®