Hi Ben,
On 13/01/16 22:49, Ben Hutchings wrote:
Control: found -1 3.16.7-ckt20-1+deb8u1
Control: found -1 3.16.7-ckt11-1+deb8u3
On Wed, 2016-01-13 at 22:35 +1100, Shaddy Baddah wrote:
[...]
OK, problem is not due to the update. I tried both 3.16.7-ckt20-1+deb8u1
and 3.16.7-ckt11-1+deb8u3 and they both have the same issue.
I don't remember this happening previously, so maybe the hardware itself
has gone bad :-( or my memory has... either way, I can accept the bug
being closed. As the premise is that the upgrade caused it.
We can keep this open until we're sure it's a hardware fault. I've
just added your results so we know it's not a recent regression.
If you use the firmware_ohci.debug parameter that allowed the kernel to
finish booting, does the Firewire port work properly?
I've never really tried that port. I don't know if I have any such
devices left, but if I find them I'll do a test.
--
Regards,
Shaddy
