From: Stefan Berndtsson <stefan@nocrew.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: Trouble compiling kernel for G5.
Date: Sun, 11 Jan 2004 02:58:35 +0100 [thread overview]
Message-ID: <873canb60k.fsf@hades.nocrew.org> (raw)
In-Reply-To: <1073784645.763.47.camel@gaston> (Benjamin Herrenschmidt's message of "Sun, 11 Jan 2004 12:30:46 +1100")
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
>>
>> ide0, timeout waiting for dbdma command stop
>> ide-cd: dma error
>> hda: DMA disabled
>> hda: dma error: status=0x50 { DriveReady SeekComplete }
>> hda: dma error: error=0x00
>> cdrom_newpc_intr: 4 residual after xfer
>> cdrom_newpc_intr: 4 residual after xfer
>>
>> And hdparm shows the drive to no longer have DMA turned on, which it did
>> before running growisofs.
>>
>> The same command on a B&W G3 runs fine with DMA (2.4.23 kernel).
>>
>> So, to answer your question, it seems it does not work, no.
>
> Look like an underrun again, or an alignement problem as there
> seem to be something weird with the DBDMA on the G5 at least
> (there is some "workaround" code in darwin that I haven't been
> able to understand fully yet).
Ok, I'll just sit tight and wait a bit then. :)
/Stefan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-01-11 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 17:24 Trouble compiling kernel for G5 Stefan Berndtsson
2004-01-10 23:44 ` Benjamin Herrenschmidt
2004-01-11 0:17 ` Stefan Berndtsson
2004-01-11 0:36 ` Benjamin Herrenschmidt
2004-01-11 1:16 ` Stefan Berndtsson
2004-01-11 1:30 ` Benjamin Herrenschmidt
2004-01-11 1:58 ` Stefan Berndtsson [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=873canb60k.fsf@hades.nocrew.org \
--to=stefan@nocrew.org \
--cc=axboe@suse.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.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 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.