linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Tresidder <rtresidd@tresar-electronics.com.au>
To: Steven Toth <stoth@kernellabs.com>
Cc: Linux-Media <linux-media@vger.kernel.org>
Subject: Re: Hauppauge WinTV-HVR2205 driver feedback
Date: Mon, 5 Oct 2015 09:59:23 +0800	[thread overview]
Message-ID: <5611D97B.9020101@tresar-electronics.com.au> (raw)
In-Reply-To: <CALzAhNWuOhQNQFu-baXy6QzhV3AxCknh7XeKOBjp943nz66Qyw@mail.gmail.com>

Hi Steven
    Nope standard x86_64
kernel 3.10.0-229.14.1.el7.x86_64

Was rather surprised as all my quick reading indicates that the kernel 
should quite happily do this...
Though looks like its the largest chunk you can request? I'm not well 
enough up to speed with the nitty gritty..

There is mention of something similar against this card on www linuxtv 
org wiki index.php  Hauppauge_WinTV-HVR-2200

********
Note: Some kernels will not have enough free memory available for the 
driver. The dmesg error will start with a message like this:
] modprobe: page allocation failure: order:10, mode:0x2000d0
followed by a stack trace and other debugging information. While the 
driver will load, no devices will be registered.
The simple workaround is to allocate more memory for the kernel:
sudo /bin/echo 16384 > /proc/sys/vm/min_free_kbytes
sudo rmmod saa7164
sudo modprobe saa7164
********

log snippet and trace from my system before the path I made...
***********
Oct  3 18:43:09 richos kernel: CORE saa7164[0]: subsystem: 0070:f120, 
board: Hauppauge WinTV-HVR2205 [card=13,autodetected]
Oct  3 18:43:09 richos kernel: saa7164[0]/0: found at 0000:04:00.0, rev: 
129, irq: 18, latency: 0, mmio: 0xf7800000
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() no first image
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() Waiting for 
firmware upload (NXP7164-2010-03-10.1.fw)
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() firmware read 
4019072 bytes.
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() firmware loaded.
Oct  3 18:43:09 richos kernel: Firmware file header part 1:
Oct  3 18:43:09 richos kernel: .FirmwareSize = 0x0
Oct  3 18:43:09 richos kernel: .BSLSize = 0x0
Oct  3 18:43:09 richos kernel: .Reserved = 0x3d538
Oct  3 18:43:09 richos kernel: .Version = 0x3
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() 
SecBootLoader.FileSize = 4019072
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() FirmwareSize = 
0x1fd6
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() BSLSize = 0x0
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() Reserved = 0x0
Oct  3 18:43:09 richos kernel: saa7164_downloadfirmware() Version = 
0x1661c00
Oct  3 18:43:09 richos kernel: modprobe: page allocation failure: 
order:10, mode:0x10c0d0
Oct  3 18:43:09 richos kernel: CPU: 1 PID: 23702 Comm: modprobe Tainted: 
GF          O--------------   3.10.0-229.14.1.el7.x86_64 #1
Oct  3 18:43:09 richos kernel: Hardware name: System manufacturer System 
Product Name/P7H55-M/USB3, BIOS 0312    05/26/2010
Oct  3 18:43:09 richos kernel: 000000000010c0d0 00000000a89d2ba5 
ffff8801011d7810 ffffffff81604516
Oct  3 18:43:09 richos kernel: ffff8801011d78a0 ffffffff8115c5c0 
0000000000000000 00000000ffffffff
Oct  3 18:43:09 richos kernel: ffff880117fd6000 ffffffff8115efa6 
ffff8801011d7870 00000000a89d2ba5
Oct  3 18:43:09 richos kernel: Call Trace:
Oct  3 18:43:09 richos kernel: [<ffffffff81604516>] dump_stack+0x19/0x1b
Oct  3 18:43:09 richos kernel: [<ffffffff8115c5c0>] 
warn_alloc_failed+0x110/0x180
Oct  3 18:43:09 richos kernel: [<ffffffff8115efa6>] ? 
drain_local_pages+0x16/0x20
Oct  3 18:43:09 richos kernel: [<ffffffff81160d48>] 
__alloc_pages_nodemask+0x9a8/0xb90
Oct  3 18:43:09 richos kernel: [<ffffffff8119f3a9>] 
alloc_pages_current+0xa9/0x170
Oct  3 18:43:09 richos kernel: [<ffffffff8115b53e>] 
__get_free_pages+0xe/0x50
Oct  3 18:43:09 richos kernel: [<ffffffff811aa13e>] 
kmalloc_order_trace+0x2e/0xa0
Oct  3 18:43:09 richos kernel: [<ffffffffa082b3b1>] 
saa7164_downloadimage+0x9f/0x486 [saa7164]
Oct  3 18:43:09 richos kernel: [<ffffffffa0820212>] 
saa7164_downloadfirmware+0x882/0xbe0 [saa7164]
Oct  3 18:43:09 richos kernel: [<ffffffff8110d78c>] ? 
request_threaded_irq+0xcc/0x170
Oct  3 18:43:09 richos kernel: [<ffffffffa081d843>] 
saa7164_initdev+0x583/0xfd0 [saa7164]
Oct  3 18:43:09 richos kernel: [<ffffffff813087a5>] 
local_pci_probe+0x45/0xa0
*******************

On 4/10/2015 10:03 PM, Steven Toth wrote:
>> Seems the kzalloc(4 * 1048576, GFP_KERNEL) in saa7164-fw.c  was failing..
>> kept getting:  kernel: modprobe: page allocation failure: order:10,
>> mode:0x10c0d0
> I don't think I've ever seen or heard of that in the entire history of
> the driver.
>
> Are you running on traditional x86/x86 hardware, or something embedded/custom?
>


  reply	other threads:[~2015-10-05  2:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04  4:55 Hauppauge WinTV-HVR2205 driver feedback Richard Tresidder
2015-10-04 14:03 ` Steven Toth
2015-10-05  1:59   ` Richard Tresidder [this message]
2015-10-05 14:22     ` Steven Toth
2015-10-05 14:35       ` Richard Tresidder
2015-10-05 14:39         ` Richard Tresidder
2015-10-05 14:43         ` Steven Toth
2015-10-05 15:26           ` Richard Tresidder
2015-10-05 15:32             ` Steven Toth
2015-10-05 12:45 ` Tycho Lürsen
2015-10-05 14:22   ` Richard Tresidder
2015-10-05 16:03   ` Richard Tresidder
2015-10-11  6:18   ` Richard Tresidder
2015-10-11  7:33     ` Tycho Lürsen
  -- strict thread matches above, loose matches on Subject: below --
2015-06-03  3:55 Stephen Allan
2015-06-03  7:55 ` Antti Palosaari
2015-06-03  8:02   ` Antti Palosaari
2015-06-03  9:29     ` Olli Salonen
2015-06-03 14:30       ` Steven Toth
2015-06-04 12:46         ` Steven Toth
2015-06-03 15:34       ` Antti Palosaari
2015-06-03 19:08         ` Olli Salonen
2015-06-03 19:46           ` Antti Palosaari
2015-06-04  8:07             ` Olli Salonen
2015-06-04  0:38     ` Stephen Allan
2015-06-04  1:22       ` faulkner-ball
2015-06-03 14:31   ` Steven Toth
2015-06-03 21:50     ` Peter Faulkner-Ball
2015-06-03 22:16       ` Steven Toth

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=5611D97B.9020101@tresar-electronics.com.au \
    --to=rtresidd@tresar-electronics.com.au \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@kernellabs.com \
    /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).