From: David R <david@industrialstrengthsolutions.com>
To: linux-kernel@vger.kernel.org
Subject: Re: DMA broken in mainline 2.6.13.2 _AND_ opensuse vendor 2.6.13-15 - oopsers
Date: Thu, 22 Sep 2005 11:19:02 -0400 [thread overview]
Message-ID: <4332CB66.7090107@industrialstrengthsolutions.com> (raw)
In-Reply-To: <1127398965.18840.88.camel@localhost.localdomain>
Alan Cox wrote:
>On Mer, 2005-09-21 at 22:28 -0400, David R wrote:
>
>
>>DMA is broken in 2.6.13.2 and opensuse 2.6.13-15, for my cdrom/dvd
>>burner.
>>
>>
>The trace you posted looks like your .config is totally changed, in
>
>
>particular that you turned off IDE PCI
>
>
>
>
You are totaly correct and I apologize for that, the last thing I want
to do is increase the noise level. I spent several hours trying to get
netconsole to work with this, but I spose it just happens to soon. Im
getting an oops now. (The oops was happening a week or so ago when I
first tried to upgrade from .12 to .13 by simply using make oldconfig
and going from there, then I started poking around and eventualy the
drive worked but with no dma) Attached is my current oops generating
config. Here is a digicam shot of my screen:
http://rawdod.com/photo20050922-12:05:56-0007.JPG
Again my drive is a:
LITE-ON DVDRW SOHW-1693S, FwRev=KS09
And my IDE chip is a:
VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 06)
Thanks!
-David
ps. Your beard rocks!
next prev parent reply other threads:[~2005-09-22 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 2:28 DMA broken in mainline 2.6.13.2 _AND_ opensuse vendor 2.6.13-15 David R
2005-09-22 13:25 ` Lennart Sorensen
2005-09-22 14:22 ` Alan Cox
2005-09-22 15:19 ` David R [this message]
2005-09-22 15:47 ` DMA broken in mainline 2.6.13.2 _AND_ opensuse vendor 2.6.13-15 - oopsers Randy.Dunlap
2005-09-22 16:24 ` David R
2005-09-22 15:22 ` DMA broken in mainline 2.6.13.2 _AND_ opensuse vendor 2.6.13-15 David R
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=4332CB66.7090107@industrialstrengthsolutions.com \
--to=david@industrialstrengthsolutions.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;
as well as URLs for NNTP newsgroup(s).