linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 205201] Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M
Date: Sat, 23 Nov 2019 11:28:00 +0000	[thread overview]
Message-ID: <bug-205201-206035-eiRGCNEHCg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205201-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205201

--- Comment #16 from Christian Zigotzky (chzigotzky@xenosoft.de) ---
Created attachment 286031
  --> https://bugzilla.kernel.org/attachment.cgi?id=286031&action=edit
dmesg of Christoph's Git kernel

Christoph Hellwig wrote:

I think we have two sorta overlapping issues here.  One is that I think
we need the bus_dma_limit, which should mostly help for something like
a SCSI controller that doesn't need streaming mappings (btw, do we
have more details on that somewhere?).

And something weird with the videobuf things.  Your change of the dma
masks suggests that the driver doesn't do the right allocations and thus
hits bounce buffering (swiotlb).  We should fix that for real, but the
fact that the bounce buffering itself also fails is even more interesting.

Can you try this git branch:

    git://git.infradead.org/users/hch/misc.git fsl-dma-debugging

Gitweb:

   
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/fsl-dma-debugging

and send me the dmesg with that with your TV adapter?

-----------------------------

Hello Christoph,

Here is the dmesg of your Git kernel.

Thanks,
Christian

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2019-11-23 11:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 14:36 [Bug 205201] New: Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M bugzilla-daemon
2019-10-16 21:48 ` [Bug 205201] " bugzilla-daemon
2019-10-29 23:45 ` bugzilla-daemon
2019-11-05 10:58 ` bugzilla-daemon
2019-11-05 14:33 ` bugzilla-daemon
2019-11-05 14:47 ` bugzilla-daemon
2019-11-06 19:36 ` bugzilla-daemon
2019-11-07  8:46 ` bugzilla-daemon
2019-11-07  9:11 ` bugzilla-daemon
2019-11-07  9:13 ` bugzilla-daemon
2019-11-07  9:18 ` bugzilla-daemon
2019-11-10  7:11 ` bugzilla-daemon
2019-11-11  7:38 ` bugzilla-daemon
2019-11-11 12:19 ` bugzilla-daemon
2019-11-13 11:01 ` bugzilla-daemon
2019-11-16  6:48 ` bugzilla-daemon
2019-11-23 11:28 ` bugzilla-daemon [this message]
2020-01-10 10:15 ` bugzilla-daemon
2020-01-10 10:16 ` bugzilla-daemon
2020-01-13 12:28 ` bugzilla-daemon

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=bug-205201-206035-eiRGCNEHCg@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).