Corrupted filesystem with new Firewire stack

["Gregor Jasny" <gjasny@googlemail.com>]

Hi,

today I got the "status write for unknown orb" during early boot
sequence. This corrupted somehow my root filesystem which is
completely located at the external disk.

Aug 15 23:06:02 Mini kernel: firewire_sbp2: logged in to sbp2 unit
fw1.0 (0 retries)
Aug 15 23:06:02 Mini kernel: firewire_sbp2:  -
management_agent_address:    0xfffff0030000
Aug 15 23:06:02 Mini kernel: firewire_sbp2:  -
command_block_agent_address: 0xfffff0100000
Aug 15 23:06:02 Mini kernel: firewire_sbp2:  - status write address:
     0x000100000000
...
Aug 15 23:06:02 Mini kernel: Freeing unused kernel memory: 252k freed
Aug 15 23:06:02 Mini kernel: firewire_sbp2: status write for unknown orb
Aug 15 23:06:02 Mini kernel: firewire_sbp2: sbp2_scsi_abort

After this error with timeout the kernel complained about missing
symbols in the intel agp module and udev behave strange.

After the next reboot I found the following lines in the kernel logfile:

Aug 15 23:09:52 Mini kernel: firewire_core: created new fw device fw1
(0 config rom retries)
Aug 15 23:09:52 Mini kernel: firewire_core: phy config: card 0, new
root=ffc1, gap_count=5
Aug 15 23:09:52 Mini kernel: firewire_ohci: context_stop: still active
(0x00000411)
Aug 15 23:09:52 Mini kernel: firewire_sbp2: management write failed, rcode 0x11

Sometimes rcode is 0x12:
Aug 13 22:24:13 Mini kernel: firewire_core: phy config: card 0, new
root=ffc0, gap_count=5
Aug 13 22:24:13 Mini kernel: firewire_sbp2: management write failed, rcode 0x12
Aug 13 22:24:13 Mini kernel: firewire_sbp2: reconnected to unit fw1.0
(1 retries)

The system is an early Mac Mini with C2D CPU. The external disk is a
Formax Oxygen 250 with Oxford OXFW_911 chipset. The Kernel was a
vanilla 2.6.22.2 with the mactel patches applied.

Is there anything I can do to help debugging this problem?

Thanks,
Gregor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/