Bug#827506:

2016-08-10 Thread Erika D Glaub 
Hope you got my Letter

Processed: Re: Bug#833326: pulseaudio: Lenovo Ideapad 300 - volume of the internal microphone is very low

2016-08-10 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 linux-image-4.6.0-1-amd64
Bug #833326 [pulseaudio] pulseaudio: Lenovo Ideapad 300 - volume of the 
internal microphone is very low
Bug reassigned from package 'pulseaudio' to 'linux-image-4.6.0-1-amd64'.
No longer marked as found in versions pulseaudio/9.0-1.1.
Ignoring request to alter fixed versions of bug #833326 to the same values 
previously set

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

Re: Bug#833326: pulseaudio: Lenovo Ideapad 300 - volume of the internal microphone is very low

2016-08-10 Thread Felipe Sateler 
Control: reassign -1 linux-image-4.6.0-1-amd64


On 10 August 2016 at 14:16, Florent Mazzone  wrote:
>
> Hello Felipe,
>
> Thanks for your answer. I'm currently  using pavucontrol, as soon as I
> disable one channel from the microphone (for example the left chanel level
> is 0%), the microphone will work normally. I've found on the Ubuntu an issue
> that looks similar to the one I've noticed with this laptop (
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 ). Maybe
> the problem is specific to this type of microphone ?

So, it looks like that problem indeed. Reassigning to the kernel then,
as the problem is there.

Please attach the alsa-info as documented at
https://wiki.ubuntu.com/Audio/AlsaInfo

-- 

Saludos,
Felipe Sateler

Re: machine checks on Dell R815 under jessie

2016-08-10 Thread Jeffrey Mark Siskind 
   From: Ritesh Raj Sarraf 

   I (still) have MCE errors on my new laptop [1]. But so far, hasn't created
   any problem.

It causes my servers to halt.

Jeff (http://engineering.purdue.edu/~qobi)

Bug#833925: nfs-kernel-server: no_root_squash broken on amd64

2016-08-10 Thread Greg Wooledge 
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: normal

The no_root_squash option appears to work on i386, but not on amd64.

wooledg@wooledg:~$ grep '^[^#]' /etc/exports
/home   -no_subtree_check arc1(ro,no_root_squash,sync)

arc1:~# ls /net/hosts/wooledg/home/wooledg/.bash*
/net/hosts/wooledg/home/wooledg/.bash_history
/net/hosts/wooledg/home/wooledg/.bash_logout
/net/hosts/wooledg/home/wooledg/.bashrc
arc1:~# ls /net/hosts/wooledg/home/wooledg/Maildir
ls: cannot open directory /net/hosts/wooledg/home/wooledg/Maildir: Permission 
denied

This is somewhat similar to bug #492970, but it's architecture specific
and it appears to be on the server side, not the client side.  I've
confirmed with NFSv3 and NFSv4 mounts from other Debian systems, and
with an HP-UX client.

See also:
https://lists.debian.org/debian-user/2016/08/msg00245.html
https://lists.debian.org/debian-user/2016/08/msg00275.html

I filed the bug report from "wooledg" (my desktop box) because it has an
absolutely minimal configuration that still demonstrates the problem.
The real problem that I care about is on a server with many other exports
as well.  Same problem: jessie, amd64, no_root_squash is ignored.

Jessie i386 systems work fine.

-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
1000241   udp  55248  status
1000241   tcp  48807  status
132   tcp   2049  nfs
133   tcp   2049  nfs
134   tcp   2049  nfs
1002272   tcp   2049
1002273   tcp   2049
132   udp   2049  nfs
133   udp   2049  nfs
134   udp   2049  nfs
1002272   udp   2049
1002273   udp   2049
1000211   udp  55895  nlockmgr
1000213   udp  55895  nlockmgr
1000214   udp  55895  nlockmgr
1000211   tcp  38500  nlockmgr
1000213   tcp  38500  nlockmgr
1000214   tcp  38500  nlockmgr
151   udp  43131  mountd
151   tcp  49060  mountd
152   udp  47185  mountd
152   tcp  49686  mountd
153   udp  52717  mountd
153   tcp  35670  mountd
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/home   -no_subtree_check arc1(ro,no_root_squash,sync)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nfs-kernel-server depends on:
ii  libblkid1 2.25.2-6
ii  libc6 2.19-18+deb8u4
ii  libcap2   1:2.24-8
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libtirpc1 0.2.5-1
ii  libwrap0  7.6.q-25
ii  lsb-base  4.1+Debian13+nmu1
ii  nfs-common1:1.2.8-9
ii  ucf   3.0030

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- debconf-show failed

Bug#833918: linux: Please enable cdc_ncm and cdc_mbim in d-i to support 'Dell 4-in-1 Adapter' Ethernet

2016-08-10 Thread Bjørn Mork 
John Paul Adrian Glaubitz  writes:

> This adapter uses the cdc_ncm/cdc_mbim kernel modules which are currently 
> being disabled for
> debian-installer as those were suspected to be used by modems only [2], which 
> is not the
> case, however.

cdc_mbim is modem-only. cdc_ncm is not.

The reason you see cdc_mbim loaded is because of an oddity in the MBIM
spec, allowing an USB interface to be both NCM and MBIM depening on the
active altsetting. The cdc_mbim driver is therefore matching NCM
interfaces to be able to detect this sort of dual function.  But that's
completely irrelevant to your ethernet adapter.  MBIM cannot be used on
an ethernet (it has no no L2 headers).

By avoiding cdc_mbim, you can also drop the cdc_wdm dependency.


> [ 9105.605635] cdc_ncm 2-1.1:1.5: MAC-Address: 9c:eb:e8:20:f5:5b
> [ 9105.605640] cdc_ncm 2-1.1:1.5: setting rx_max = 16384
> [ 9105.605743] cdc_ncm 2-1.1:1.5: setting tx_max = 16384
> [ 9105.605991] cdc_ncm 2-1.1:1.5 usb0: register 'cdc_ncm' at 
> usb-:00:14.0-1.1, CDC NCM, 9c:eb:e8:20:f5:5b
> [ 9105.680400] cdc_ncm 2-1.1:1.5 enx9cebe820f55b: renamed from usb0

See?  This is only using cdc_ncm and will work fine even if cdc_mbim is 
unavailable.


Bjørn

Bug#833918: linux: Please enable cdc_ncm and cdc_mbim in d-i to support 'Dell 4-in-1 Adapter' Ethernet

2016-08-10 Thread John Paul Adrian Glaubitz 
Source: linux
Version: 4.6.4-1
Severity: normal

Hi!

While reinstalling my Dell XPS-13 9343 yesterday, I ran into the problem that 
the Ethernet
adapter in my external 'Dell 4-in-1 Adapter' [1] was not detected. This adapter 
is necessary
because the XPS ultrabook series do not have an internal Ethernet adapter but 
require an
external USB Ethernet adapter, with the 4-in-1 adapter from Dell being the 
standard
accessory.

This adapter uses the cdc_ncm/cdc_mbim kernel modules which are currently being 
disabled for
debian-installer as those were suspected to be used by modems only [2], which 
is not the
case, however.

Here's the relevant output of lsusb, lsmod and dmesg after attaching the 
adapter my XPS-13
after installing with d-i Alpha 7 with a workaround. After plugging the adapter 
in, no
additional configuration is necessary. The Ethernet adapter just works out of 
the box
and we should therefore enable these modules in d-i, I think.

glaubitz@ikarus:~$ lsusb |grep Bus\ 002
Bus 002 Device 005: ID 17e9:436f DisplayLink
Bus 002 Device 004: ID 2109:0210 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
glaubitz@ikarus:~$ lsmod |grep cdc
cdc_mbim   16384  0
cdc_wdm20480  1 cdc_mbim
cdc_ncm32768  1 cdc_mbim
cdc_ether  16384  0
usbnet 40960  3 cdc_mbim,cdc_ncm,cdc_ether
usbcore   241664  14 
btusb,snd_usb_audio,uvcvideo,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,usbnet,cdc_mbim,cdc_ncm,cdc_wdm,xhci_hcd,xhci_pci,cdc_ether
glaubitz@ikarus:~$ dmesg | tail -n30
[ 9104.050604] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[ 9104.06] usb 2-1: New USB device found, idVendor=2109, idProduct=0210
[ 9104.067782] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9104.067785] usb 2-1: Product: USB3.0 Hub
[ 9104.067786] usb 2-1: Manufacturer: VIA Labs, Inc.
[ 9104.069404] hub 2-1:1.0: USB hub found
[ 9104.069854] hub 2-1:1.0: 1 port detected
[ 9104.178489] usb 1-1: new high-speed USB device number 11 using xhci_hcd
[ 9104.511724] usb 1-1: New USB device found, idVendor=2109, idProduct=2210
[ 9104.511731] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9104.511734] usb 1-1: Product: USB2.0 Hub
[ 9104.511736] usb 1-1: Manufacturer: VIA Labs, Inc.
[ 9104.512978] hub 1-1:1.0: USB hub found
[ 9104.514078] hub 1-1:1.0: 4 ports detected
[ 9105.578571] usb 2-1.1: new SuperSpeed USB device number 5 using xhci_hcd
[ 9105.595153] usb 2-1.1: New USB device found, idVendor=17e9, idProduct=436f
[ 9105.595157] usb 2-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 9105.595160] usb 2-1.1: Product: Dell 4-in-1 Adapter
[ 9105.595162] usb 2-1.1: Manufacturer: DisplayLink
[ 9105.595164] usb 2-1.1: SerialNumber: 1505140265
[ 9105.602515] usb 2-1.1: Warning! Unlikely big volume range (=511), cval->res 
is probably wrong.
[ 9105.602522] usb 2-1.1: [14] FU [Dell USB Audio Playback Volume] ch = 6, val 
= -8176/0/16
[ 9105.605635] cdc_ncm 2-1.1:1.5: MAC-Address: 9c:eb:e8:20:f5:5b
[ 9105.605640] cdc_ncm 2-1.1:1.5: setting rx_max = 16384
[ 9105.605743] cdc_ncm 2-1.1:1.5: setting tx_max = 16384
[ 9105.605991] cdc_ncm 2-1.1:1.5 usb0: register 'cdc_ncm' at 
usb-:00:14.0-1.1, CDC NCM, 9c:eb:e8:20:f5:5b
[ 9105.680400] cdc_ncm 2-1.1:1.5 enx9cebe820f55b: renamed from usb0
[ 9105.757799] IPv6: ADDRCONF(NETDEV_UP): enx9cebe820f55b: link is not ready
[ 9105.757884] IPv6: ADDRCONF(NETDEV_UP): enx9cebe820f55b: link is not ready
[ 9108.770155] cdc_ncm 2-1.1:1.5 enx9cebe820f55b: network connection: 
disconnected
glaubitz@ikarus:~$

Thanks,
Adrian

> [1] 
> http://accessories.us.dell.com/sna/productdetail.aspx?c=us=19=en=470-ABHH
> [2] 
> https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian/installer/modules/nic-usb-modules

--
 .''`.  John Paul Adrian Glaubitz
 : :' :  Debian Developer - glaub...@debian.org
 `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#831410: (no subject)

2016-08-10 Thread Arthur Lutz 
Am trying to make aufs work on a 4.6.0-0.bpo.1-amd64 kernel, so would be
interested in this fix too.


-- 
Arthur Lutz - Logilab
http://www.logilab.fr/  http://www.logilab.fr/id/arthur.lutz
Téléphone +33 1 45 32 03 12
Twitter   @arthurlutz https://twitter.com/arthurlutz
  @logilab https://twitter.com/logilab

Re: machine checks on Dell R815 under jessie

2016-08-10 Thread Ritesh Raj Sarraf 
On Tue, 2016-08-09 at 20:43 -0400, Jeffrey Mark Siskind wrote:
> I upgraded four Dell R815s from wheezy to jessie a few weeks ago. Prior to the
> upgrade, they were running reliably for about 5 years. Since the upgrade, two
> machines have been getting periodic machine checks. The machines boot fine and
> run for a day or more. The machine checks appear to happen sporadically. I
> can't determine a correlation with anything in particular.
> 
> The front panel on the first machine says the machine check was on CPU #4. The
> front panel on the second machine said the first machine check was on CPU #1
> and the second machine check was on CPU #2.
> 
> I am suspicious that this is really a hardware problem. Three CPUs begin
> exhibiting machine checks within a few weeks of each other, all immediately
> after upgrading wheezy to jessie, after working reliably for five years.
> 
> Has anybody else encountered this issue? Any suggestions on how to debug and
> fix?

I (still) have MCE errors on my new laptop [1]. But so far, hasn't created any
problem.

[1] https://www.researchut.com/blog/lenovo-yoga-2-13-debian


-- 
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response

signature.asc
Description: This is a digitally signed message part