Package: firmware-atheros
Version: 20170823-1
Severity: normal
Starting from linux 4.12, wifi silently stops working after the second WPA
group rekeying (see #875362):
oct. 19 19:35:43 vicious wpa_supplicant[868]: wlp58s0: CTRL-EVENT-CONNECTED -
Connection to 14:cc:20:56:eb:94 completed [id=0 id_
This appears exactly when wpa_supplicant issues this message:
oct. 18 23:52:25 vicious wpa_supplicant[868]: wlp58s0: WPA: Key negotiation
completed with 16:cc:20:56:eb:95 [PTK=CCMP GTK=TKIP]
oct. 18 23:52:25 vicious wpa_supplicant[868]: wlp58s0: CTRL-EVENT-CONNECTED -
Connection to 16:cc:20:56:eb
Package: src:linux
Version: 4.12.6-1
Severity: normal
Since I upgraded to linux 4.12.0-1-amd64, my wifi at home (5.18GHz, WPA2-PSK)
frequently and silently fails. Manually re-connecting works. This issue does
not appear on linux 4.11.0-1, nor does it occur at my workplace, where I am
connected to
I updated to 4.11.0-trunk-armmp from experimental, and I am also using u-boot
from ALARM, as I have not seen this issue on my ALARM-running A20 boards yet…
… and it failed again, this time with no explicit MMC-related errors, but with
hung tasks instead, much like my previous kernel log.
To be ho
I keep experiencing this issue even with a brand new board (same model, newer
hw revision) and on linux-image-4.10.0-rc6-armmp.
I have been informed that this issue might have been fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers?id=2154d94b40ea2a5de05245
After a little less than two weeks running on 4.8, the second board finally
crashed during an “aptitude update” with:
1062229.158740] mmc0: Card stuck in programming state! mmc_do_erase
[1062229.933728] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout
[1062230.708711] sunxi-mmc 1c0f000.mmc: fat
I have made some more tests using the “spew” and “stress” packages, but it
doesn't seem to cause the issue. So far, it mainly happened during package
installation (thus causing the additional pain of leaving some packages in a
broken state).
I have been unable to reproduce the issue with older ker
severity 855911 critical
thanks
Changed the severity to critical, since it may make the whole system unusable
and cause data loss.
Package: linux-image-4.9.0-1-armmp
Severity: normal
I recently switched to linux 4.9.0 (jessie-backport package on one, package
from testing in the other) and latest u-boot on my two A20-OLinuXIno-LIME2
boards, which were running seriously outdated versions of linux until now (4.4
and 4.0).
Both
Package: src:linux
Version: 3.12-1~exp1
Severity: normal
Hi,
Since linux-image-3.12-rc7-amd64, shutting down (either from gdm3, lightdm,
xfce4 or by typing “poweroff”) results in the laptop rebooting in the two
seconds following the shutdown.
It is different from a normal (hard) reboot as the powe
Le dimanche 01 mai 2011 à 17:47 -0300, Lisandro Damián Nicanor Pérez
Meyer a écrit :
[snip]
> Did you mean the patch to tell dri to forget about bad checksums? If so, I
> already tried it and worked fine.
>
> If you are talking about something else, please give me some link :-)
I'm not talking a
Le dimanche 01 mai 2011 à 16:51 -0300, Lisandro Damián Nicanor Pérez
Meyer a écrit :
> On Dom 01 May 2011 16:40:39 Thibaut Girka escribió:
> > [Sorry for the duplicate mail sent earlier to debian-kernel]
> >
> > This whole bug really looks like #615598.
> > This migh
[Sorry for the duplicate mail sent earlier to debian-kernel]
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
Did the initial "breakage" of the screens occur with 2.6.38?
If so, you may want to try fixing your EDID info has explained in a
similar bug repo
This whole bug really looks like #615598.
This might be a bug in nouveau or in the kernel.
Did the initial "breakage" of the screens occur with 2.6.38?
If so, you may want to try fixing your EDID info has explained in a
similar bug report[1], but be careful, it may cause more harm if
something goe
Package: linux-2.6
Version: 2.6.37-1
Severity: normal
Tags: sid
I have been running Debian on my laptop for years, and soon (possibly 3 days)
after switching from testing/squeeze's version of the kernel (+Xorg + libdrm)
to sid's version, my laptop's screen suddenly turned black, and didn't work
up
Le mardi 08 juin 2010 à 14:15 +0100, Martin Michlmayr a écrit :
> * Thibaut Girka [2010-06-08 11:31]:
> > So, two questions: First, is it possible to have this flavour in Debian
> > after some more work? If yes, can I target the 2.6.32 kernel so it have
> > a chance to be in
I have found (at least on my computer) the origin of the problem.
It's in sound/pci/hda/patch_analog.c, in the ad1986a_automic function
(line 658 in the current lenny version).
If I disable this function, using an ugly "return" at the beginning, it
works fine.
However, I haven't the required knowle
Package: linux-image-2.6.26-1-686
Version: 2.6.26-5
Severity: normal
My microphone doesn't work with the 2.6.26 kernel.
I tried several times, with rec, audacity, and checking alsamixer.
The microphone is shown in alsamixer, the volume is ok.
When audacity or rec records from the microphone, it st
18 matches
Mail list logo
