linux-kernel - request_mem_region failed (was: dv camera no longer recognized)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <472F89C0.80602@s5r6.in-berlin.de>
Date:	Mon, 05 Nov 2007 22:23:12 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Søren Renner <soren.renner@...il.com>
CC:	linux1394-user@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: request_mem_region failed (was: dv camera no longer recognized)

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@...uxbox:/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@...uxbox:/home/sr#
> 
> root@...uxbox:/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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/