Processed: Re: Bug#902946: Fails to load autofs module through autofs4 alias

2018-07-06 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 src:linux 4.18~rc3-1~exp1
Bug #902946 [systemd] Fails to load autofs module through autofs4 alias
Bug reassigned from package 'systemd' to 'src:linux'.
No longer marked as found in versions systemd/238-5 and systemd/239-3.
Ignoring request to alter fixed versions of bug #902946 to the same values 
previously set
Bug #902946 [src:linux] Fails to load autofs module through autofs4 alias
Marked as found in versions linux/4.18~rc3-1~exp1.
> tag -1 pending
Bug #902946 [src:linux] Fails to load autofs module through autofs4 alias
Added tag(s) pending.

-- 
902946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode

2018-07-06 Thread Phil 
On Fri, 29 Jun 2018 10:17:20 +0200 =?utf-8?Q?Bj=C3=B8rn_Mork?= 
 wrote:

> This issue should be fixed by commit
>  49c2c3f246e2 ("cdc_ncm: avoid padding beyond end of skb")
>  https://patchwork.kernel.org/patch/10453923/
> Please check again with one of those kernel versions (or newer).

Hi, thank you for your quick response.

I had to wait a bit for the 4.17-3 being released in ArchLinux repos.

I've tested uploading again and couldn't reproduce the crash anymore.
I experienced a single crash - but I'm not sure if it was related to 
uploading. I'll reach out to you if I experience any further crash 
related to modem.


> [...] we get the fix into "stretch" too. Thanks for reminding me.

Thank you for your work, this issue has been super exhausting and I'm 
really thankful that it appears finally to be fixed.


Best wishes,
Phil.

Bug#903128: linux-image-4.16.0-2-amd64: bridge stops passing non-local traffic (reversion from 4.16.0-1-amd64)

2018-07-06 Thread Scott Bailey 
Package: src:linux
Version: 4.16.16-2
Severity: important

Dear Maintainer,

This system hosts several KVM guests and a simh VAX, all of which connect to
the local network using bridge br0:

buzz:~# brctl show br0
bridge name bridge id   STP enabled interfaces
br0 8000.aa0004000308   no  eth1
tap0
vnet0
vnet1
vnet2
buzz:~#

Here, eth1 is the physical NIC, tap0 is owned by my simh VAX, and vnet# are
my KVM guests.

Following the upgrade to 4.16.0-2-amd64, none of these guests can
communicate
with anything except buzz (the host). Rebooting back to 4.16.0-1-amd64
restores
normal connectivity.

Studying the arp table on one of the guests suggests that arp resolution
succeeds (since the arp table contains valid MAC addresses vs ""
and the guest was restarted when buzz rebooted, so these can't be entries
from before the problem onset).

tcpdump on the guest while attempting to ping an external physical system on
the same network shows outgoing ICMP echo request packets, but no responses.
The same behavior is observed attempting to ping one of the other guests. I
also see unrelated other traffic (STP packets, ARP and DNS traffic from
other
systems on this subnet, etc.) 

Thanks,
-Scott

-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/vg00-root ro
elevator=deadline

** Not tainted

** Kernel log:
[  184.547886] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[  184.551012] docker0: port 2(vethd1c9441) entered disabled state
[  184.606709] docker0: port 3(vethc366df7) entered blocking state
[  184.606712] docker0: port 3(vethc366df7) entered disabled state
[  184.606749] device vethc366df7 entered promiscuous mode
[  184.607004] IPv6: ADDRCONF(NETDEV_UP): vethc366df7: link is not ready
[  184.607007] docker0: port 3(vethc366df7) entered blocking state
[  184.607009] docker0: port 3(vethc366df7) entered forwarding state
[  184.98] docker0: port 4(vethfea270f) entered blocking state
[  184.666703] docker0: port 4(vethfea270f) entered disabled state
[  184.666774] device vethfea270f entered promiscuous mode
[  184.667422] IPv6: ADDRCONF(NETDEV_UP): vethfea270f: link is not ready
[  184.667426] docker0: port 4(vethfea270f) entered blocking state
[  184.667428] docker0: port 4(vethfea270f) entered forwarding state
[  184.916492] eth0: renamed from veth11ac1d4
[  184.961777] docker0: port 3(vethc366df7) entered disabled state
[  184.961846] docker0: port 4(vethfea270f) entered disabled state
[  184.961873] IPv6: ADDRCONF(NETDEV_CHANGE): vethfbc6cd1: link becomes
ready
[  184.961912] docker0: port 1(vethfbc6cd1) entered blocking state
[  184.961914] docker0: port 1(vethfbc6cd1) entered forwarding state
[  185.008399] eth0: renamed from veth3b69021
[  185.030837] IPv6: ADDRCONF(NETDEV_CHANGE): vethd1c9441: link becomes
ready
[  185.030886] docker0: port 2(vethd1c9441) entered blocking state
[  185.030889] docker0: port 2(vethd1c9441) entered forwarding state
[  185.073249] eth0: renamed from veth0bc32af
[  185.107428] IPv6: ADDRCONF(NETDEV_CHANGE): vethc366df7: link becomes
ready
[  185.107481] docker0: port 3(vethc366df7) entered blocking state
[  185.107484] docker0: port 3(vethc366df7) entered forwarding state
[  185.138492] eth0: renamed from veth7410428
[  185.165175] IPv6: ADDRCONF(NETDEV_CHANGE): vethfea270f: link becomes
ready
[  185.165223] docker0: port 4(vethfea270f) entered blocking state
[  185.165226] docker0: port 4(vethfea270f) entered forwarding state
[  185.296071] virbr1: port 1(virbr1-nic) entered forwarding state
[  185.296074] virbr1: topology change detected, propagating
[  185.296127] IPv6: ADDRCONF(NETDEV_CHANGE): virbr1: link becomes ready
[  186.082642] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  186.082646] Bluetooth: BNEP filters: protocol multicast
[  186.082650] Bluetooth: BNEP socket layer initialized
[  186.902286] virbr1: port 1(virbr1-nic) entered disabled state
[  186.909553] virbr0: port 1(virbr0-nic) entered blocking state
[  186.909557] virbr0: port 1(virbr0-nic) entered disabled state
[  186.909613] device virbr0-nic entered promiscuous mode
[  187.074362] virbr0: port 1(virbr0-nic) entered blocking state
[  187.074366] virbr0: port 1(virbr0-nic) entered listening state
[  187.123796] virbr0: port 1(virbr0-nic) entered disabled state
[  187.129902] virbr2: port 1(virbr2-nic) entered blocking state
[  187.129906] virbr2: port 1(virbr2-nic) entered disabled state
[  187.135908] device virbr2-nic entered promiscuous mode
[  187.240511] virbr2: port 1(virbr2-nic) entered blocking state
[  187.240515] virbr2:

Bug#897618: marked as done (linux-image-4.17.0-rc3-amd64-unsigned: xrandr gives a black screen for some resolutions)

2018-07-06 Thread Debian Bug Tracking System 
Your message dated Fri, 06 Jul 2018 09:25:38 +0200
with message-id <7656829.07UMQSbNc0@apollon>
and subject line linux-image-4.17.0-rc3-amd64-unsigned: xrandr gives a black 
screen for some resolutions
has caused the Debian Bug report #897618,
regarding linux-image-4.17.0-rc3-amd64-unsigned: xrandr gives a black screen 
for some resolutions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
897618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.17~rc3-1~exp1
Severity: normal

My laptop has a resolution of 1920x1080.
xrandr -s 800x600 results in a black screen.
Using KDE, I can leave the session by typing ctrl-alt-delete
while the screen is black.
A resolution of 1360x768 is working.
/sys/kernel/debug/dri/0/framebuffer contains:
framebuffer[82]:
allocated by = Xorg
refcount=1
format=XR24 little-endian (0x34325258)
modifier=0x101
size=800x600
layers:
size[0]=800x600
pitch[0]=3584
offset[0]=0
obj[0]:(null)
--- End Message ---
--- Begin Message ---
fixed 897618 4.18~rc3-1~exp1
thanks--- End Message ---

Bug#897589: linux-image-4.17.0-rc3-amd64-unsigned: uvcvideo doesn't work, spams boot console

2018-07-06 Thread Reinhard Karcher 
reopen -1
found 4.17.3-1
thanks