From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Søren Renner" <soren.renner@gmail.com>
Cc: linux1394-user@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: request_mem_region failed (was: dv camera no longer recognized)
Date: Mon, 05 Nov 2007 22:23:12 +0100 [thread overview]
Message-ID: <472F89C0.80602@s5r6.in-berlin.de> (raw)
In-Reply-To: <a4280a600710281656s168aa64bge2ee8efaf13ea4c8@mail.gmail.com>
On 2007-10-29, Søren Renner wrote to linux1394-user:
> testlibraw provides some output but freezes the box and a reboot is
> necessary.
>
> dvgrab previously worked with this hardware. After the latest kernel upgrade
> it does not work. Booting to a previous kernel does not help.
>
>
> root@siduxbox:/home/sr# dmesg | grep 1394
> ohci1394: MMIO resource (0xfdffc000 - 0xfdffc800) unavailable
> ohci1394: probe of 0000:00:0c.0 failed with error -12
> ieee1394: raw1394: /dev/raw1394 device initialized
> root@siduxbox:/home/sr#
>
> root@siduxbox:/home/sr# infobash
> CPU[Dual Intel Core2 Duo E4400 @ clocked at 1000.000 Mhz] Kernel[Linux
> 2.6.23.1-slh64-smp-18 x86_64] Up[-18min-] Mem[-370.7/1510.3MB-]
> HDD[-330GB(48%used)-] Procs[-106-] Client[Shell]
[...]
The controller itself cannot be initialized anymore. The message "MMIO
resource... unavailable" is because ohci1394's call to
request_mem_region failed, i.e. when it tried to request the
memory-mapping of controller registers.
I have no idea how this could happen, therefore I Cc lkml. It's not a
problem with the IEEE 1394 drivers.
Besides the kernel update, did you change anything in the BIOS or even
the hardware? Do you boot the old kernels with the same boot parameters
as you did before you added the new kernel?
--
Stefan Richter
-=====-=-=== =-== ---=-
http://arcgraph.de/sr/
parent reply other threads:[~2007-11-05 21:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <a4280a600710281656s168aa64bge2ee8efaf13ea4c8@mail.gmail.com>]
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=472F89C0.80602@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-user@lists.sourceforge.net \
--cc=soren.renner@gmail.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
all inboxes | Powered by JetHome®