On Fri, 2013-03-29 at 22:07 +, Ben Hutchings wrote:
Control: tag -1 unreproducible
Until you find a *reliable* way to reproduce the bug, bisection cannot
find the fix. I'm sorry I can't be more helpful.
I haven't found a way to reliably reproduce, but I have found a way to
ensure that
After several long and painful 'git bisect drivers/net/wireless/ath*'
sessions (too many false positives), I think I've come to the conclusion
that the issues in this bug disappear starting with
On Sun, 2013-01-20 at 15:42 +, Ben Hutchings wrote:
I've looked for changes to the drive that seem related to power and
reset sequencing. Could you test whether applying the attached patches
to Debian's 3.2 kernel fixes the problem? See the instructions at
After looking at this some more, my bisect has left me between these two
commits:
The last good commit:
[db9d8c60266a5010e905829e10cd722519e14777] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
The last bad commit:
[45e7715922217493f01c8238d8c9eff5c3fea5a2] Merge tag
Package: alsa-utils
Version: 1.0.25-3
Severity: important
File: /usr/bin/speaker-test
Dear Maintainer,
* What led up to the situation?
Can't get any sound out of my computer, so I check alsamixer for the volume and
tried the speaker-test utility to see if I could get any sound at all.
*
After compiling kernel 3.7 from kernel.org, sound is working fine.
Perhaps this should be moved to the kernel component?? I would if I
knew how, but this is only my 4th day with Debian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
* Joel Diaz joeld...@earthlink.net [2012-12-13 17:41 -0500]:
After compiling kernel 3.7 from kernel.org, sound is working fine.
Perhaps this should be moved to the kernel component?? I would if I
knew how, but this is only my 4th day with Debian.
I swear I'm losing my mind I booted
Package: gnome-shell
Version: 3.4.2-3
Severity: important
Dear Maintainer,
* What led up to the situation?
Issued /etc/init.d/network-manager restart as root while logged into Gnome as a
regular user.
* What was the outcome of this action?
gnome-shell process crashes then restarts. And of
Package: src:linux
Version: 3.2.35-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Just using the computer normally. For unrelated reasons, the actual network
traffic was being routed through eth0 and not wlan0 (even though wlan0 had a
valid IP address).
Ran my machine
Package: src:linux
Version: 3.2.35-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Just using the computer while both wlan0 and eth0 were active and eth0 was the
prefered route.
This also ocurred yesterday, so I built upstream linux-3.7 and ran it overnight
and all day
Sorry, close this bug. Bug 695968 was already opened for the issue
described here. reportbug crashed during bug submission of 695968, so I
figured it didn't go through and redid the bug report and this one is
therefore a dupe.
--
To UNSUBSCRIBE, email to
A patch has been posted to linux-wireless which accomplishes the
workaround of disabling wireless power saving (ie. iw dev wlan0 set
power_save off) by disabling power saving in the ath9k driver itself.
http://marc.info/?l=linux-wirelessm=137005085710866w=2
I applied it to Debian's 3.2.41 kernel
12 matches
Mail list logo
