From: Antti Palosaari <crope@iki.fi>
To: poma <pomidorabelisima@gmail.com>
Cc: Josh Boyer <jwboyer@redhat.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
kernel@lists.fedoraproject.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Stephen Hemminger <shemminger@vyatta.com>,
Stephen Hemminger <shemminger@osdl.org>
Subject: Re: 3.9 merge window kernels
Date: Tue, 26 Feb 2013 10:54:49 +0200 [thread overview]
Message-ID: <512C7859.6090304@iki.fi> (raw)
In-Reply-To: <512C698E.7070306@iki.fi>
On 02/26/2013 09:51 AM, Antti Palosaari wrote:
> On 02/26/2013 04:18 AM, poma wrote:
>> On 02/26/13 02:12, Josh Boyer wrote:
>>> On Tue, Feb 26, 2013 at 01:05:05AM +0100, poma wrote:
>>>> On 02/25/13 01:22, Antti Palosaari wrote:
>>>> […]
>>>>>>> Poma, you should probably just start filing bugs for things you hit.
>>>>>>> In this case, the skge backtrace is just a warning but it can be
>>>>>>> fixed
>>>>>>> up relatively easily.
>>>>>>>
>>>>>>
>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=914994
>>>>>> Josh, Mauro thanks for the overview. :)
>>>>>> Antti, cheers. ;)
>>>>>>
>>>>>> poma
>>>>>
>>>>> I cannot see these warnings at all. What is Kernel option to enable
>>>>> those debug(?) warnings? From which menu it could be located when make
>>>>> menuconfig ?
>>>>>
>>>>
>>>> http://kojipkgs.fedoraproject.org/packages/kernel/3.9.0/0.rc0.git7.1.fc19/data/logs/x86_64/build.log
>>>>
>>>> Even after reapplying Stephen's "skge: check for PCI dma mapping
>>>> errors"[1] from David's 'net-next' tree, no luck.
>>>> …
>>>> WARNING: at lib/dma-debug.c:933 check_unmap+0x47b/0x960()
>>>> skge 0000:01:09.0: DMA-API: device driver failed to check map
>>>> error[device address=0x000000010287094a] [size=90 bytes] [mapped as
>>>> single]
>>>> …
>>>
>>> I'm confused. You pointed to the build I did this morning, which
>>> definitely doesn't include the commit you mentioned. Are you saying you
>>> took this morning's build and applied the patch yourself? If so, did it
>>> really get applied? Do you have logs? Do you have more than just that
>>> tiny snippet of error message?
>>>
>>
>> build.log is for Antti's eyes only. :)
>> Logs are virtually the same, with or without that *old* commit, which is
>> actually replaced by this one[1].
>> So of course it isn't in 3.9.0-0.rc0.git7.1.fc19.x86_64. ;)
>> Building particular module groups(skge & Co.) rather than build an
>> entire kernel tree isn't big deal, likewise.
>> You know that better than me. ;)
>> The real question is whether someone will help squeeze this bug.
>
> I want just know if I could reproduce that AF9015 error message or was
> it just warning. Is it something I have to fix for Kernel 3.10 or
> earlier. I am running Fedora 17 AMD64 and could surely compile any
> Kernel needed.
OK, found it finally.
Kernel hacking ---> Enable debugging of DMA-API usage
There was rather many DVB USB drivers using USB bulk buffers from the
stack. I will fix at least some of those, lets say for 3.10.
regards
Antti
--
http://palosaari.fi/
prev parent reply other threads:[~2013-02-26 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130222151634.GA1015@hansolo.jdub.homelinux.org>
[not found] ` <20130222181552.GA7308@wolff.to>
[not found] ` <5127FF54.1010906@gmail.com>
[not found] ` <20130222234825.GB2419@hansolo.jdub.homelinux.org>
[not found] ` <20130222210938.4f62cede@redhat.com>
[not found] ` <512816AD.9050406@gmail.com>
[not found] ` <20130222223014.1b9a2cc0@redhat.com>
[not found] ` <512857FB.3050803@gmail.com>
[not found] ` <20130223090148.4a4bd5e0@redhat.com>
[not found] ` <CA+5PVA46LfV-WTkJVF7fz9nrz1Qrib894fqMo+8GL8AjuW8_Yg@mail.gmail.com>
[not found] ` <5129491A.5020406@gmail.com>
[not found] ` <512AAED8.3070205@iki.fi>
[not found] ` <512AAED8.3070205-X3B1VOXEql0@public.gmane.org>
2013-02-26 0:05 ` 3.9 merge window kernels poma
2013-02-26 1:12 ` Josh Boyer
2013-02-26 2:18 ` poma
2013-02-26 7:51 ` Antti Palosaari
2013-02-26 8:54 ` Antti Palosaari [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=512C7859.6090304@iki.fi \
--to=crope@iki.fi \
--cc=davem@davemloft.net \
--cc=jwboyer@redhat.com \
--cc=kernel@lists.fedoraproject.org \
--cc=mchehab@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pomidorabelisima@gmail.com \
--cc=shemminger@osdl.org \
--cc=shemminger@vyatta.com \
--cc=stephen@networkplumber.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).