On Mon, 2011-05-09 at 21:38 -0700, Noah Meyerhans wrote:
quoted
On Tue, May 10, 2011 at 03:38:44AM +0100, Ben Hutchings wrote:
quoted
This is pretty weird. Debian version 2.6.38-3 has a few bridging
changes from stable 2.6.38.3 and 2.6.38.4, but they don't look like they
would cause this.
I have apparently filed the bug against the wrong version of Debian's
kernel. 2.6.38-3 is not affected, and works as expected. The change
was introduced in -4. That may have been clear from the report itself,
but the report was filed against -3. I've fixed that in the BTS.
I gathered that, and then made the same mistake in writing the above!
The version with the regression, 2.6.38-4, includes the changes from
stable 2.6.38.3 and 2.6.38.4
Ben.
We just hitted the very same problem yesterday, with debian too , BUT
with vanilla kernels (hand compiled from GIT, with a specific config).
I can confirm that 2.6.38.5 & 2.6.38.6 have this problem, but 2.6.38.3
works fine.
So this is not a debian specific bug as far as I can see.
Cheers,
--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@univ-nantes.fr