From: poma <pomidorabelisima-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Antti Palosaari <crope-X3B1VOXEql0@public.gmane.org>
Cc: Mauro Carvalho Chehab
<mchehab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
kernel-TuqUDEhatI4ANWPb/1PvSmm0pvjS0E/A@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"David S. Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
Stephen Hemminger
<stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>,
Stephen Hemminger
<shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>,
Stephen Hemminger <shemminger-3NddpPZAyC0@public.gmane.org>
Subject: Re: 3.9 merge window kernels
Date: Tue, 26 Feb 2013 01:05:05 +0100 [thread overview]
Message-ID: <512BFC31.7010800@gmail.com> (raw)
In-Reply-To: <512AAED8.3070205-X3B1VOXEql0@public.gmane.org>
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]
…
Cheers,
poma
[1]
http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;a=commit;h=d0249e44432aa0ffcf710b64449b8eaa3722547e
_______________________________________________
kernel mailing list
kernel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kernel
next parent reply other threads:[~2013-02-26 0:05 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 ` poma [this message]
2013-02-26 1:12 ` 3.9 merge window kernels Josh Boyer
2013-02-26 2:18 ` poma
2013-02-26 7:51 ` Antti Palosaari
2013-02-26 8:54 ` Antti Palosaari
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=512BFC31.7010800@gmail.com \
--to=pomidorabelisima-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=crope-X3B1VOXEql0@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=kernel-TuqUDEhatI4ANWPb/1PvSmm0pvjS0E/A@public.gmane.org \
--cc=mchehab-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shemminger-3NddpPZAyC0@public.gmane.org \
--cc=shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org \
--cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.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).