linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: 2.6.32-rc1/2, arm and usb
Date: Wed, 30 Sep 2009 14:36:25 +0200	[thread overview]
Message-ID: <87ocos4njq.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <19138.34019.987851.150679@pilspetsen.it.uu.se> (Mikael Pettersson's message of "Wed\, 30 Sep 2009 00\:06\:27 +0200")

Mikael Pettersson <mikpe@it.uu.se> writes:

Hi,

> Arnaud Patard (Rtp) writes:
>  > I wanted yesterday to check that my iop sanmina support was still fine on
>  > latest -rc kernel and found out that it was not booting anymore and last
>  > thing printed on the serial console is "done. Booting the kernel". After
>  > bisecting, the culprit is commit
>  > db8be50c4307dac2b37305fc59c8dc0f978d09ea (in linus tree). Reverting it
>  > allows to boot so this confirms the git bisect result.
>  > 
>  > The commit does this in drivers/usb/host/pci-quirks.c :
>  > -DECLARE_PCI_FIXUP_FINAL(PCI_ANY_ID, PCI_ANY_ID, quirk_usb_early_handoff);
>  > +DECLARE_PCI_FIXUP_HEADER(PCI_ANY_ID, PCI_ANY_ID, quirk_usb_early_handoff);
>  > 
>  > Now, before collecting informations to report the problem to usb folks
>  > and trying to debug further, I'm wondering if anyone else got this bug
>  > or if I'm just unlucky and has a hardware-specific issue. Also, if
>  > someone has an idea of what the problem may be or in which direction I
>  > should look at, please share.
>
> My iop n2100 shows the exact same problem with 2.6.32-rc1,
> and reverting the commit mentioned above fixes it.
>
> None of my other machines (including two non-iop arms, x86,
> and ultrasparc) have this problem even though they all have
> PCI usb controllers. So the problem looks iop-specific.

fyi, I've taken a look at linux-usb today and found :
http://marc.info/?l=linux-usb&m=125426642829044&w=2

So this bug is not iop specific. Even if it doesn't look arch specific,
I'm surprised to see that so few machines are affected. I was hoping
that all arm machines with usb host on pci were affected but according
to your tests it's not the case.


Arnaud

  reply	other threads:[~2009-09-30 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29  8:29 2.6.32-rc1/2, arm and usb Arnaud Patard (Rtp)
2009-09-29 22:06 ` Mikael Pettersson
2009-09-30 12:36   ` Arnaud Patard (Rtp) [this message]
2009-09-30 13:18     ` Mikael Pettersson
2009-10-02 19:11   ` Mikael Pettersson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ocos4njq.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).