From: dAgeCKo <dagecko@free.fr>
To: Andreas Herrmann <andreas.herrmann3@amd.com>,
"H. Peter Anvin" <hpa@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: Linux - AMD SB950 USB Regression
Date: Fri, 11 Jan 2013 16:59:11 +0100 [thread overview]
Message-ID: <50F036CF.7010109@free.fr> (raw)
In-Reply-To: <50E6AD77.1000707@free.fr>
Hi,
the bug has been resolved after a BIOS upgrade. Since the mainboard
constructor said me that it's impossible that the BIOS was an issue
since their Windows users do not face the same issue, I beleived it
could have come from the Linux kernel.
Bye.
Le 04/01/2013 11:22, dAgeCKo a écrit :
>
> Hello,
>
> Some months ago I noticed that my USB controler (and also my network
> controler) does not work anymore on newer kernels from my debian wheezy
> distribution.
>
> I then reported a bug for the former one here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=47791
>
> With some helps and time, I could locate the source of the regression,
> that is an old commit from the year 2010 you seem to commit. Git
> besection identified the commit as:
>
> git bisect bad 5c80cc78de46aef6cd5e714208da05c3f7f548f8
>
> Someone from the usb kernel mailing list (Alan Stern) then asked me to
> write an email to you, in my hope the bug to be solved.
>
> Some informations were said on the bug tracker, but if you need any
> other information that could help you in any manner, please let me know.
>
> Please note that the regression only involves USB2 ports of the
> mainboard, not the USB3 ports.
>
> Regards.
>
> ---
> Jean-Dominique Frattini
next prev parent reply other threads:[~2013-01-11 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50C9FCD6.6050809@free.fr>
2013-01-04 10:22 ` Fwd: Linux - AMD SB950 USB Regression dAgeCKo
2013-01-11 15:59 ` dAgeCKo [this message]
2013-01-17 21:36 ` Borislav Petkov
2013-01-19 14:47 ` dAgeCKo
2013-01-19 16:35 ` Borislav Petkov
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=50F036CF.7010109@free.fr \
--to=dagecko@free.fr \
--cc=andreas.herrmann3@amd.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.