[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#810769: linux-image-3.16.0-4-586: boot now mostly either hangs or repeats, firewire_ohci on older laptop




Hi again,

On 13/01/16 10:13, Shaddy Baddah wrote:
Hi Ben,

On 13/01/16 00:07, Ben Hutchings wrote:
Control: tag -1 moreinfo

On Tue, 2016-01-12 at 13:41 +1100, Shaddy Baddah wrote:
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u2
Severity: important

Dear Maintainer,

After upgrade of linux-image-3.16.0-4-586:i386 from
3.16.7-ckt20-1+deb8u1 to 3.16.7-ckt20-1+deb8u2 on my old Fujitsu P
Series Lifebook, an older Pentium M 1GHz laptop, the kernel boot up
mostly hangs. Mostly with a cleared screen with no information at all,
or otherwise with a message something like (hard to capture):

   firewire_ohci 0000:02:00.0: IRQ 00030010 selfID AR_req busReset

continually being output to the console with no let-up.

Obviously from this bug report, you can see that I have managed to boot
with this kernel image. However, I had to append firmware_ohci.debug to
the kernel command line to do so. This unexpectedly worked around the
problem. Maybe it suggests a timing/race condition issue that is reduced
by having console I/O operations intermingle in the kernel operations.
[...]

We didn't change anything related to firewire in this version, so I
really doubt this is a regression.

Have you tried a full power-cycle of the laptop?

Definitely performed a full power-cycle. Just starting the day here in
Sydney, and the laptop's been off overnight. Same thing all over. Didn't
come right until firewire_ohci.debug=1 set. For completeness, this may
not have set it right at first attempt (I am unsure if I typed it
right first time).

Also, the message being output (when it appears) is more like this one:

firewire_ohci: IRQ 00020000 busReset

Just to be doubly sure that this is a valid bug report, I'm going to go
back to the previous kernel and see if it was as bullet-proof as I
remembered it.

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.

--
Regards,
Shaddy


Reply to: