The issue is not resolved yet in 3.16.7-ckt20-1+deb8u3 of
linux-image-3.16.0-4-amd64.
Although I didn't do test with Debian's 3.16 tree yet, the following
commits to AUFS should fix the issue:
*
https://github.com/sfjro/aufs3-linux/commit/565ce4aa61963ebfd90b7768b1ba6c7d6af53c88
*
https://githu
Including missing arm header references from the arm64 headers:
asm/opcodes.h:#include <../../arm/include/asm/opcodes.h>
asm/xen/hypervisor.h:#include <../../arm/include/asm/xen/hypervisor.h>
asm/xen/page.h:#include <../../arm/include/asm/xen/page.h>
asm/xen/page-coherent.h:#include <../../arm/incl
Package: src:linux
Version: 4.5.1-1
Severity: normal
When I upgraded to linux 4.5.1 I found that switching from a gdm Xorg
vt to normal virtual console corrupts the display until I reboot. The
display corruption is not static and is mostly black with some fuzz
around the sides and sometimes pixels
On Apr 18, 2016, at 09:40 PM, James McCoy wrote:
>I've been seeing something similar. Am I right to assume that these are
>union-type=overlay? If so, this seems to be a change in the kernel.
Yep, union-type=overlay.
pgpyziTxZW8nO.pgp
Description: OpenPGP digital signature
On Mon, Apr 18, 2016 at 02:14:58PM -0400, Barry Warsaw wrote:
> With today's dist-upgrade, I am unable to enter an existing or newly
> created chroot, nor am I able to sbuild or adt-run with the chroot.
>
> I had an existing sid-amd64 chroot which I could not enter. I then
> removed the chroot an
Package: linux-perf-4.6
Version: 4.6~rc3-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because
On Mon, 2016-04-18 at 14:57 -0400, Daniel Kahn Gillmor wrote:
> Version: 20160110-1
>
> Thanks for the quick response, Ben.
>
> On Mon 2016-04-18 09:49:27 -0400, Ben Hutchings wrote:
> >
> > >
> > > It looks to me like the brcmfmac_sdio kernel module is expecting this
> > > .txt file is suppose
Your message dated Mon, 18 Apr 2016 14:57:57 -0400
with message-id <87fuui68y2@alice.fifthhorseman.net>
and subject line Re: Bug#821400: firmware-brcm80211: brcmfmac_sdio wants
brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied
has caused the Debian Bug report #821400,
regarding firmwar
Version: 20160110-1
Thanks for the quick response, Ben.
On Mon 2016-04-18 09:49:27 -0400, Ben Hutchings wrote:
>> It looks to me like the brcmfmac_sdio kernel module is expecting this
>> .txt file is supposed to be shipped alongside the .bin, but it isn't
>> present.
>
> That's board-specific con
Processing control commands:
> tag -1 wontfix
Bug #821400 [firmware-brcm80211] firmware-brcm80211: brcmfmac_sdio wants
brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied
Added tag(s) wontfix.
--
821400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821400
Debian Bug Tracking System
Co
Control: tag -1 wontfix
On Mon, 2016-04-18 at 09:22 -0400, Daniel Kahn Gillmor wrote:
> Package: firmware-brcm80211
> Version: 20160110-1
> Severity: normal
>
> On an Asus X205T, dmesg says:
>
> brcmfmac_sdio mmc1:0001:1: firmware: direct-loading firmware
> brcm/brcmfmac43340-sdio.bin
> brcmfma
Package: firmware-brcm80211
Version: 20160110-1
Severity: normal
On an Asus X205T, dmesg says:
brcmfmac_sdio mmc1:0001:1: firmware: direct-loading firmware
brcm/brcmfmac43340-sdio.bin
brcmfmac_sdio mmc1:0001:1: firmware: failed to load brcm/brcmfmac43340-sdio.txt
(-2)
brcmfmac_sdio mmc1:0001:1:
Package: src:linux
Version: 4.4.6-1~bpo8+1
Severity: normal
Dear Maintainer,
Each time that I run "xrandr -s 800x600" or "xrandr -s 1024x600", syslog logs
debug messages saying about issues of the kernel (see below).
No other effects out of this log.
xrandr seems to work fine.
$ xrandr
Screen 0:
13 matches
Mail list logo
