[prev in list] [next in list] [prev in thread] [next in thread]
List: linux1394-devel
Subject: Re: Yet another firewire_ohci: Register access failure
From: cyril <cyril42e () gmail ! com>
Date: 2012-06-26 22:08:41
Message-ID: 4FEA32E9.9070700 () gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
On 2012/06/26 21:52, Stefan Richter wrote:
> On Jun 13 cyril wrote:
>> on a Dell
>> Precision M4600 with O2 Micro firewire card. My current kernel is
>> 3.3.5-gentoo x86-64, but I also tried with 3.4.1-vanilla and
>> 3.0.6-gentoo and there was the same problem. Funny thing is that it was
>> working with 3.0.6-gentoo before, but I had to recompile it to be able
>> to start the X server so maybe it changed something else.
> What /is/ the problem? Camera not detected by the kernel? I guess so,
> since your subsequent log messages contain something about fw0 (the local
> node = the Dell itself) but not fw1 (a remote node = the camera).
Sorry, you are right, the camera is not detected. When I plug the camera
I expect something like:
Mar 22 19:41:31 localhost, kernel: [ 418.784509] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Mar 22 19:41:33 localhost, kernel: [ 420.781578] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Mar 22 19:41:34 localhost, kernel: [ 421.811685] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Mar 22 19:41:35 localhost, kernel: [ 422.752171] firewire_core: created
device fw1: GUID 00b09d01009f7929, S400, 1 config ROM retries
>> Here is exactly what happens in dmesg when I'm trying to use the camera :
>>
>> [ 7.293867] firewire_ohci: Added fw-ohci device 0000:0b:00.0, OHCI
>> v1.10, 8 IR + 8 IT contexts, quirks 0x10
>> [ 7.794274] firewire_core: created device fw0: GUID 00d31701344fc000,
>> S400
>>
>> plugging the cable
>>
>> [ 403.490494] firewire_ohci: Register access failure - please notify
>> linux1394-devel@lists.sf.net
> Interesting; in the other reports, the message occurred immediately when
> firewire-ohci was loaded or at PM resume.
Well sometimes it happens during boot but this is when the camera
remained plugged in, otherwise when camera is plugged in. Actually I
parsed my /var/log/kern.log file and I found similar events that
happened before, when I still was able to make it work (at least Dec 14
and Jan 27) :
Dec 14 12:14:26 accretion kernel: [ 4162.030784] firewire_ohci: Register
access failure - please notify linux1394-devel@lists.sf.net
Jan 27 08:54:49 localhost, kernel: [238342.517692] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Mar 22 19:40:02 localhost, kernel: [ 330.692883] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
May 9 15:03:07 localhost, kernel: [192835.423708] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
May 9 15:04:37 localhost, kernel: [192925.083009] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
May 9 15:06:08 localhost, kernel: [193016.107836] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 19:34:15 localhost, kernel: [1233519.234418] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 19:37:04 localhost, kernel: [1233688.021752] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 19:37:57 localhost, kernel: [1233741.516142] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 19:54:33 localhost, kernel: [ 403.490494] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 19:55:30 localhost, kernel: [ 461.176585] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 20:21:37 localhost, kernel: [ 6.438797] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 20:23:06 localhost, kernel: [ 7.986116] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 20:40:41 localhost, kernel: [ 6.190244] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 20:42:56 localhost, kernel: [ 8.084477] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 21:15:24 localhost, kernel: [ 7.251075] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 21:24:33 localhost, kernel: [ 7.700420] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 21:54:05 localhost, kernel: [ 7.787515] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 22:15:16 localhost, kernel: [ 233.276249] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 22:18:08 localhost, kernel: [ 7.896444] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 13 22:19:42 localhost, kernel: [ 6.732909] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 18 17:11:12 localhost, kernel: [ 478.060026] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 18 17:42:39 localhost, kernel: [ 2362.174581] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 26 22:43:45 localhost, kernel: [546936.411936] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
On Dec 24, more precisely (grep firewire), we can see that it created
fw1 5 seconds after the same error (at 12:14), so it has not always been
a fatal error... but it was not producing this error systematically.
Dec 14 10:34:13 accretion kernel: [ 6.090010] firewire_ohci
0000:0b:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Dec 14 10:34:13 accretion kernel: [ 6.090019] firewire_ohci
0000:0b:00.0: setting latency timer to 64
Dec 14 10:34:13 accretion kernel: [ 6.140406] firewire_ohci: Added
fw-ohci device 0000:0b:00.0, OHCI v1.10, 8 IR + 8 IT contexts, quirks 0x10
Dec 14 10:34:13 accretion kernel: [ 6.640860] firewire_core: created
device fw0: GUID 00d31701344fc000, S400
Dec 14 10:59:30 accretion kernel: [ 1059.714271] firewire_ohci
0000:0b:00.0: restoring config space at offset 0xf (was 0x100, writing
0x10a)
Dec 14 10:59:30 accretion kernel: [ 1059.714300] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x3 (was 0x800000,
writing 0x800010)
Dec 14 10:59:30 accretion kernel: [ 1059.714309] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x1 (was 0x100000,
writing 0x100006)
Dec 14 10:59:30 accretion kernel: [ 1059.765971] firewire_core: skipped
bus generations, destroying all nodes
Dec 14 10:59:30 accretion kernel: [ 1060.266427] firewire_core:
rediscovered device fw0
Dec 14 11:27:34 accretion kernel: [ 1390.997040] firewire_ohci
0000:0b:00.0: restoring config space at offset 0xf (was 0x100, writing
0x10a)
Dec 14 11:27:34 accretion kernel: [ 1390.997069] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x3 (was 0x800000,
writing 0x800010)
Dec 14 11:27:34 accretion kernel: [ 1390.997078] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x1 (was 0x100000,
writing 0x100006)
Dec 14 11:27:34 accretion kernel: [ 1391.060893] firewire_core: skipped
bus generations, destroying all nodes
Dec 14 11:27:34 accretion kernel: [ 1391.561239] firewire_core:
rediscovered device fw0
Dec 14 11:33:10 accretion kernel: [ 1703.247971] firewire_ohci
0000:0b:00.0: restoring config space at offset 0xf (was 0x100, writing
0x10a)
Dec 14 11:33:10 accretion kernel: [ 1703.247999] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x3 (was 0x800000,
writing 0x800010)
Dec 14 11:33:10 accretion kernel: [ 1703.248008] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x1 (was 0x100000,
writing 0x100006)
Dec 14 11:33:10 accretion kernel: [ 1703.299720] firewire_core: skipped
bus generations, destroying all nodes
Dec 14 11:33:10 accretion kernel: [ 1703.800049] firewire_core:
rediscovered device fw0
Dec 14 11:59:34 accretion kernel: [ 3287.943541] firewire_core: skipped
bus generations, destroying all nodes
Dec 14 11:59:34 accretion kernel: [ 3288.443918] firewire_core:
rediscovered device fw0
Dec 14 11:59:34 accretion kernel: [ 3288.745021] firewire_core: created
device fw1: GUID 00b09d01009f7929, S400
Dec 14 11:59:34 accretion kernel: [ 3288.745033] firewire_core: phy
config: card 0, new root=ffc0, gap_count=7
Dec 14 11:59:36 accretion kernel: [ 3289.945262] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Dec 14 12:10:24 accretion kernel: [ 3920.070761] firewire_core: skipped
bus generations, destroying all nodes
Dec 14 12:10:25 accretion kernel: [ 3920.570392] firewire_core:
rediscovered device fw0
Dec 14 12:10:27 accretion kernel: [ 3922.781553] firewire_core: phy
config: card 0, new root=ffc1, gap_count=5
Dec 14 12:10:28 accretion kernel: [ 3923.556920] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Dec 14 12:10:30 accretion kernel: [ 3925.549214] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Dec 14 12:10:31 accretion kernel: [ 3926.579319] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Dec 14 12:10:31 accretion kernel: [ 3927.065729] firewire_core: created
device fw1: GUID 00b09d01009f7929, S400, 1 config ROM retries
Dec 14 12:14:25 accretion kernel: [ 4160.227019] firewire_core: skipped
bus generations, destroying all nodes
Dec 14 12:14:25 accretion kernel: [ 4160.727505] firewire_core:
rediscovered device fw0
Dec 14 12:14:26 accretion kernel: [ 4162.030784] firewire_ohci: Register
access failure - please notify linux1394-devel@lists.sf.net
Dec 14 12:14:27 accretion kernel: [ 4163.013874] firewire_core: phy
config: card 0, new root=ffc1, gap_count=5
Dec 14 12:14:28 accretion kernel: [ 4163.789321] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Dec 14 12:14:30 accretion kernel: [ 4165.782579] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Dec 14 12:14:31 accretion kernel: [ 4166.812834] firewire_core: phy
config: card 0, new root=ffc2, gap_count=7
Dec 14 12:14:32 accretion kernel: [ 4167.297568] firewire_core: created
device fw1: GUID 00b09d01009f7929, S400, 1 config ROM retries
Dec 14 19:25:51 accretion kernel: [28256.045464] firewire_ohci
0000:0b:00.0: restoring config space at offset 0xf (was 0x100, writing
0x10a)
Dec 14 19:25:51 accretion kernel: [28256.045492] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x3 (was 0x800000,
writing 0x800010)
Dec 14 19:25:51 accretion kernel: [28256.045501] firewire_ohci
0000:0b:00.0: restoring config space at offset 0x1 (was 0x100000,
writing 0x100006)
Dec 14 19:25:51 accretion kernel: [28256.098264] firewire_core: skipped
bus generations, destroying all nodes
Dec 14 19:25:51 accretion kernel: [28256.598606] firewire_core:
rediscovered device fw0
>> modprobe -r firewire_ohci; modprobe -r firewire_core; modprobe -r crc_itu_t;
>>
>> [ 449.748465] firewire_ohci: Removed fw-ohci device.
>>
>> modprobe firewire_ohci
>>
>> [ 461.176585] firewire_ohci: Register access failure - please notify
>> linux1394-devel@lists.sf.net
>> [ 461.176608] firewire_ohci: Added fw-ohci device 0000:0b:00.0, OHCI
>> v1.10, 8 IR + 8 IT contexts, quirks 0x10
>> [ 461.677032] firewire_core: created device fw0: GUID 00d31701344fc000,
>> S400
> What if you do "modprobe firewire-ohci debug=-1" instead? (Load it
> withoutr camera connected, get the kernel log, connect the camera, and
> collect the subsequently log messages.)
When I modprobe I get this:
Jun 26 23:13:58 localhost, kernel: [548747.399244] firewire_ohci: IRQ
00040000 regAccessFail
Jun 26 23:13:58 localhost, kernel: [548747.399246] firewire_ohci:
Register access failure - please notify linux1394-devel@lists.sf.net
Jun 26 23:13:58 localhost, kernel: [548747.399299] firewire_ohci: Added
fw-ohci device 0000:0b:00.0, OHCI v1.10, 8 IR + 8 IT contexts, quirks 0x10
Jun 26 23:13:58 localhost, kernel: [548747.399315] firewire_ohci: IRQ
00030010 selfID AR_req busReset
Jun 26 23:13:58 localhost, kernel: [548747.399326] firewire_ohci: AR
evt_bus_reset, generation 1
Jun 26 23:13:58 localhost, kernel: [548747.399332] firewire_ohci: IRQ
00020000 busReset
Jun 26 23:13:58 localhost, kernel: [548747.399346] firewire_ohci: IRQ
00020000 busReset
Jun 26 23:13:58 localhost, kernel: [548747.399368] firewire_ohci: IRQ
00020000 busReset
Jun 26 23:13:58 localhost, kernel: [548747.399389] firewire_ohci: IRQ
00020000 busReset
Jun 26 23:13:58 localhost, kernel: [548747.399411] firewire_ohci: IRQ
00020000 busReset
Jun 26 23:13:58 localhost, kernel: [548747.399440] firewire_ohci: IRQ
00020000 busReset
Jun 26 23:13:58 localhost, kernel: [548747.399446] firewire_ohci: 1
selfIDs, generation 1, local node ID ffc0
Jun 26 23:13:58 localhost, kernel: [548747.399454] firewire_ohci: selfID
0: 807f8842, phy 0 [-..] S400 gc=63 +0W Lci
Jun 26 23:13:58 localhost, kernel: [548747.899774] firewire_core:
created device fw0: GUID 00d0510000000001, S400
When I plug the cable nothing more happens.
It always does that, the first time the error occurs when I plug the
cable, then directly when I load the modules.
>> Do you know why it wouldn't work with the same kernel version it was
>> working before?
> I have no idea. Well, maybe the timing of driver initialization of the
> two or three different functions of this O2Micro combo controller
> changed...?
>
> Are drivers bound to all of the subdevices ("Kernel driver in use:..."
> output in lspci -v)?
No, this one has no driver:
0b:00.2 Mass storage controller: O2 Micro, Inc. Device 8330 (rev 05)
Subsystem: Dell Device 04a3
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at dd110000 (32-bit, non-prefetchable) [size=1K]
Memory at dd100000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [a0] Power Management version 3
Capabilities: [48] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [200] Advanced Error Reporting
But I don't know what this device is?
Best,
Cyril
["signature.asc" (application/pgp-signature)]
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
mailing list linux1394-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic