Bug#852493: Please enable Thunder NIC virtual function driver

2017-01-24 Thread Ben Hutchings 
Control: tag -1 moreinfo

On Tue, 2017-01-24 at 22:13 +, Punit Agrawal wrote:
> Source: linux
> Severity: wishlist
> Tags: patch
> 
> While testing device passthrough with a debian guest on a Cavium
> Thunder, I found that the virtual function(VF) driver for the built in
> nic is not available.
> 
> Please enable CONFIG_THUNDER_NIC_VF in the debian kernel config.

So long as this hardware is part of specific SoCs, we should only
enable it for the CPU architectures used in those SoCs.  That's arm64,
right?  (Possibly also mips64, but we don't support Cavium MIPS SoCs at
all yet.)

Shouldn't we also enable CONFIG_THUNDER_NIC_{PF,BGX,RGX} along with
this?

Ben.

-- 
Ben Hutchings
It is easier to write an incorrect program than to understand a correct
one.


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

Processed: Re: Bug#852493: Please enable Thunder NIC virtual function driver

2017-01-24 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #852493 [src:linux] Please enable Thunder NIC virtual function driver
Added tag(s) moreinfo.

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

Bug#852505: linux-image-4.8.0-2-amd64: Realtek Ethernet controller vanishes on reboot

2017-01-24 Thread Andrea Zuccherelli 
Package: src:linux
Version: 4.8.15-2
Severity: normal
Tags: upstream

Dear Maintainer,

The Ethernet controller RTL8105e in my Toshiba C660 notebook had a very strange 
behaviour.
It worked once but not after, being not even seen by BIOS for LAN boot on next 
reboot.
A hardware issue?

I disabled the controller in Debian "interfaces" file so that it was not 
configured.
Doing this the problem was solved: the device appeared on every boot, but it 
was unusable as it was down.
Then after boot up I manually configured the device, used and then disabled it:

root@zbox:~# ip addr add 192.168.0.2/24 dev lan0
root@zbox:~# ip link set dev lan0 up
root@zbox:~# ping 192.168.69.254
PING 192.168.69.254 (192.168.69.254) 56(84) bytes of data.
64 bytes from 192.168.69.254: icmp_seq=1 ttl=64 time=1.37 ms
64 bytes from 192.168.69.254: icmp_seq=2 ttl=64 time=1.04 ms
^C
--- 192.168.69.254 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.044/1.210/1.376/0.166 ms

root@zbox:~# ip link set dev lan0 down
root@zbox:~# modprobe -r r8169

But after a reboot/poweroff the controller again was not there.
Enabling/disabling WOL in BIOS, disabling link auto-negotiation and WOL using 
ethtool... There was no way.
Searching for a solution I found that only a PCI reset, after unloading the 
driver could help:

root@zbox:~# echo 1 >/sys/bus/pci/devices/:01:00.0/reset

So I added this to my "post-down" interface configuration.

Obviously this is just a workaround: so what is happening here?
Is my hardware not resetting the PCI bus on an ACPI poweroff event?
Should the kernel or driver do it?
Where is the best place to force a device PCI reset so that no problem could 
arise on hibernate/suspend?


Best regards

Andrea Zuccherelli



-- Package-specific info:
** Version:
Linux version 4.8.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 
20161202 (Debian 5.4.1-4) ) #1 SMP Debian 4.8.15-2 (2017-01-04)

** Command line:
BOOT_IMAGE=/vmlinuz-4.8.0-2-amd64 
root=UUID=5a0b32cc-2aaf-4c3f-a33a-425168aab3e7 ro intel_pstate=disable 
pcie_aspm=force "acpi_osi=Windows 2009" "acpi_os_name=Windows 2009"

** Not tainted

** Kernel log:
[0.00] microcode: microcode updated early to revision 0x4, date = 
2013-06-28
[0.00] Linux version 4.8.0-2-amd64 (debian-kernel@lists.debian.org) 
(gcc version 5.4.1 20161202 (Debian 5.4.1-4) ) #1 SMP Debian 4.8.15-2 
(2017-01-04)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-2-amd64 
root=UUID=5a0b32cc-2aaf-4c3f-a33a-425168aab3e7 ro intel_pstate=disable 
pcie_aspm=force "acpi_osi=Windows 2009" "acpi_os_name=Windows 2009"
[0.00] Disabled fast string operations
[0.00] x86/fpu: Legacy x87 FPU detected.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable
[0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xbb30efff] usable
[0.00] BIOS-e820: [mem 0xbb30f000-0xbb690fff] reserved
[0.00] BIOS-e820: [mem 0xbb691000-0xbb69efff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbb69f000-0xbb6a1fff] reserved
[0.00] BIOS-e820: [mem 0xbb6a2000-0xbb6a4fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbb6a5000-0xbb6acfff] reserved
[0.00] BIOS-e820: [mem 0xbb6ad000-0xbb6ccfff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbb6cd000-0xbb70efff] reserved
[0.00] BIOS-e820: [mem 0xbb70f000-0xbb70] ACPI NVS
[0.00] BIOS-e820: [mem 0xbb71-0xbb714fff] reserved
[0.00] BIOS-e820: [mem 0xbb715000-0xbb718fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbb719000-0xbb719fff] reserved
[0.00] BIOS-e820: [mem 0xbb71a000-0xbb71afff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbb71b000-0xbb71efff] reserved
[0.00] BIOS-e820: [mem 0xbb71f000-0xbb79efff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbb79f000-0xbb7fefff] ACPI data
[0.00] BIOS-e820: [mem 0xbb7ff000-0xbb7f] usable
[0.00] BIOS-e820: [mem 0xbb80-0xbbff] reserved
[0.00] BIOS-e820: [mem 0xbde0-0xbfff] reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed13fff] reserved
[0.00] BIOS-e820: [mem 0xfed16000-0xfed16fff] reserved
[0.00] BIOS-e820: [mem 0xfed19000-0xfed19fff] reserved
[

Bug#852493: [PATCH] Enable CONFIG_THUNDER_NIC_VF in the debian kernel config

2017-01-24 Thread Punit Agrawal 
NIC virtual function (VF) driver is required when using a passed
through NIC to a guest on the Thunder platform.

Enable this driver as a module in the debian config. Closes: #852493
---
 debian/config/config | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/config/config b/debian/config/config
index c744073f9..c40bb15c5 100644
--- a/debian/config/config
+++ b/debian/config/config
@@ -2852,7 +2852,7 @@ CONFIG_NET_CADENCE=y
 ##
 CONFIG_NET_VENDOR_CAVIUM=y
 # CONFIG_THUNDER_NIC_PF is not set
-# CONFIG_THUNDER_NIC_VF is not set
+CONFIG_THUNDER_NIC_VF=m
 # CONFIG_THUNDER_NIC_BGX is not set
 # CONFIG_THUNDER_NIC_RGX is not set
 CONFIG_LIQUIDIO=m
-- 
2.11.0

Bug#852493: Please enable Thunder NIC virtual function driver

2017-01-24 Thread Punit Agrawal 
Source: linux
Severity: wishlist
Tags: patch

While testing device passthrough with a debian guest on a Cavium
Thunder, I found that the virtual function(VF) driver for the built in
nic is not available.

Please enable CONFIG_THUNDER_NIC_VF in the debian kernel config.

Bug#852324: [Xen-devel] Is: EPT violations. Was:Re: Problems with pci/vga passthrough

2017-01-24 Thread Boris Ostrovsky 
On 01/24/2017 01:51 PM, Boris Ostrovsky wrote:
> On 01/24/2017 01:44 PM, Diederik de Haas wrote:
>> On dinsdag 24 januari 2017 13:28:28 CET Boris Ostrovsky wrote:
> Reported it at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852324
> but  given Ben Hutchings' reaction it seems to be a Xen problem after
> all.
>
> Relevant part of earlier attached dmesg:
>
> [   13.588386] WARNING: CPU: 18 PID: 1 at 
> /build/linux-zDY19G/linux-4.8.15/arch/x86/mm/dump_pagetables.c:225
> note_page+0x5e8/0x790 [   13.588388] x86/mm: Found insecure W+X mapping
> at address 8800/0x8800 ...
> [   13.608867] x86/mm: Checked W+X mappings: FAILED, 4602 W+X pages
> found.
 Now this is a know issue, but I'm pretty convinced one that's entirely
 unrelated to your problem.
>>> I thought we fixed this. That's what is_hypervisor_range() was
>>> introduced for, and I haven't seen this warning since then.


Actually, I do see the warnings (I usually don't set CONFIG_DEBUG_WX).
They are not for the hypervisor range though, so the commit below is not
relevant.

Nevertheless, as Jan said, it's unlikely to cause your problem.

-boris


>> When? Which commit?
>> Maybe it isn't (yet) in the Debian tree and/or I am using a kernel which 
>> doesn't contain that fix.
>
> Commit f4e342c87776884f0309942a3880ca7e835239f9.
>
> All it did was to prevent the walker from trying to verify pages in the
> hypervisor range so it doesn't really fix anything. It's just that I am
> surprised to see this warning again.




signature.asc
Description: OpenPGP digital signature

Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2

2017-01-24 Thread Vagrant Cascadian 
On 2017-01-24, Heinrich Schuchardt wrote:
> On 01/24/2017 05:47 PM, Ben Hutchings wrote:
>> On Sat, 21 Jan 2017 21:00:18 +0100 Heinrich Schuchardt
>>  wrote:
>>> please, add support for the Hardkernel Odroid C2 to the kernel 
>>> configuration.
>>>  
>>> For 4.9 kernels this involves:
>>>  
>>> CONFIG_ARCH_MESON=y
...
>>> CONFIG_COMMON_CLK_AMLOGIC=y
>> 
>> I can do all this, except I think the watchdog driver can and should be
>> a module.

Thanks for moving this forward! Was working on this too, and adding
support for u-boot, but the mainline u-boot support is still too
unreliable.


>>> For 4.10 kernels this involves
>>>  
>>> CONFIG_ARCH_MESON=y
...
>>> CONFIG_PHY_MESON8B_USB2=m
>>> CONFIG_MESON_SM=y
>>> CONFIG_COMMON_CLK_AMLOGIC=y
>> 
>> Given that we're going to be using 4.9 in Debian 9 'stretch', are you
>> interested in getting the Meson changes in 4.10 backported?
>
> USB is not yet really usable in 4.10. So what would deserve backporting
> is MMC and some networking patches.

I did have working USB with odroid-c2 in using linux-next tag
next-20170113, for what it's worth.


I'll try testing your patches against sid's kernel soon.


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Reassign back to src:linux

2017-01-24 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 852324 src:linux 4.8.15-2
Bug #852324 [xen-linux-system-4.8.0-2-amd64] x86/mm: Found insecure W+X mapping
Warning: Unknown package 'xen-linux-system-4.8.0-2-amd64'
Bug reassigned from package 'xen-linux-system-4.8.0-2-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.8.15-2.
Ignoring request to alter fixed versions of bug #852324 to the same values 
previously set
Bug #852324 [src:linux] x86/mm: Found insecure W+X mapping
Marked as found in versions linux/4.8.15-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2

2017-01-24 Thread Ben Hutchings 
On Tue, 2017-01-24 at 21:36 +0100, Heinrich Schuchardt wrote:
[...]
> Could you, please, indicate on which git repository/branch I should base
> any testing?

See

sections 4.3 and 4.4.

The branch name to use is sid.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.


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

Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2

2017-01-24 Thread Heinrich Schuchardt 
On 01/24/2017 05:47 PM, Ben Hutchings wrote:
> On Sat, 21 Jan 2017 21:00:18 +0100 Heinrich Schuchardt
>  wrote:
>> Package: linux-latest
>> Severity: wishlist
>>  
>> Dear Maintainer,
>>  
>> please, add support for the Hardkernel Odroid C2 to the kernel configuration.
>>  
>> For 4.9 kernels this involves:
>>  
>> CONFIG_ARCH_MESON=y
>> CONFIG_SERIAL_MESON=y
>> CONFIG_SERIAL_MESON_CONSOLE=y
>> CONFIG_HW_RANDOM_MESON=m
>> CONFIG_I2C_MESON=m
>> CONFIG_SPI_MESON_SPIFC=m
>> CONFIG_PINCTRL_MESON=y
>> CONFIG_MESON_GXBB_WATCHDOG=y
>> CONFIG_PWM_MESON=m
>> CONFIG_RESET_MESON=y
>> CONFIG_MESON_SM=y
>> CONFIG_COMMON_CLK_AMLOGIC=y
> 
> I can do all this, except I think the watchdog driver can and should be
> a module.
> 
>> For 4.10 kernels this involves
>>  
>> CONFIG_ARCH_MESON=y
>> CONFIG_DWMAC_MESON=y
>> CONFIG_MESON_GXL_PHY=y
>> CONFIG_SERIAL_MESON=y
>> CONFIG_SERIAL_MESON_CONSOLE=y
>> CONFIG_HW_RANDOM_MESON=m
>> CONFIG_I2C_MESON=m
>> CONFIG_SPI_MESON_SPIFC=m
>> CONFIG_PINCTRL_MESON=y
>> CONFIG_MESON_GXBB_WATCHDOG=y
>> CONFIG_MESON_WATCHDOG=y
>> CONFIG_DRM_MESON=m
>> CONFIG_MMC_MESON_GX=y
>> CONFIG_PWM_MESON=m
>> CONFIG_RESET_MESON=y
>> CONFIG_PHY_MESON8B_USB2=m
>> CONFIG_MESON_SM=y
>> CONFIG_COMMON_CLK_AMLOGIC=y
> 
> Given that we're going to be using 4.9 in Debian 9 'stretch', are you
> interested in getting the Meson changes in 4.10 backported?

USB is not yet really usable in 4.10. So what would deserve backporting
is MMC and some networking patches.

I append the patch series that should provide MMC. This week I am
without access to my Odroid C2 so I was only able to test that the
patches are applicable to v4.9 but not if they alone provide the
necessary functionality.

0903-0955 I only included to avoid any reworking of the other patches.
But maybe that is not your preferred way of backporting.

> 
>> The following patch is essential. It is queued for 4.10-rc6:
>>  
>> ARM64: dts: meson-gx: Add firmware reserved memory zones
>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ecb88f3001ed9ee8c53450d971de8c18bcbf7925
> 
> This is queued up for the next upload.  For 4.9 I had to change the
> filename to arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi

Probably that is due to missing appended patch
0903-ARM64-dts-amlogic-Add-Meson-GX-dtsi-from-GXBB.patch

Could you, please, indicate on which git repository/branch I should base
any testing?

Best regards

Heinrich



odroid-c2-mmc.tar.gz
Description: GNU Zip compressed data

Processed: severity of 852469 is important

2017-01-24 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 852469 important
Bug #852469 [src:linux] After kernel update lightdm hangs at start
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
852469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852472: linux-image-4.9.0-1-amd64 fails compiling xt_ACCOUNT.ko out of package xtables-addons-dkms

2017-01-24 Thread Karsten Wiborg 
Package: linux-image-4.9.0-1-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 183299
Maintainer: Debian Kernel Team 
Architecture: amd64
Source: linux-signed (4)
Version: 4.9.2-2
Replaces: linux-image-4.9.0-1-amd64-unsigned
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.110~) |
linux-initramfs-tool
Recommends: firmware-linux-free, irqbalance
Suggests: linux-doc-4.9, debian-kernel-handbook, grub-pc |
grub-efi-amd64 | extlinux
Breaks: initramfs-tools (<< 0.110~), xserver-xorg-input-vmmouse (<<
1:13.0.99)
Conflicts: linux-image-4.9.0-1-amd64-unsigned
Description: Linux 4.9 for 64-bit PCs (signed)
 The Linux kernel 4.9 and modules for use on PCs with AMD64, Intel 64 or
 VIA Nano processors.
 .
 This kernel also runs on a Xen hypervisor.  It supports both privileged
 (dom0) and unprivileged (domU) operation.
 .
 The kernel image and modules are signed for use with Secure Boot.
Built-Using: linux (= 4.9.2-2)
Homepage: https://www.kernel.org/


Package: xtables-addons-dkms
Status: install ok installed
Priority: extra
Section: kernel
Installed-Size: 1563
Maintainer: Pierre Chifflier 
Architecture: all
Source: xtables-addons
Version: 2.11-3
Depends: xtables-addons-common (>= 2.11), dkms (>= 2.1.0.0), make
Recommends: linux-headers
Description: Extensions targets and matches for iptables
 Xtables-addons provides extra modules for iptables not present in the
 kernel, and is the successor of patch-o-matic.
 Extensions includes new targets like TEE, TARPIT, CHAOS, or modules like
 geoip and account.
 .
 The dkms package will automatically compile the driver for your current
 kernel version.
Homepage: http://xtables-addons.sourceforge.net/


Calling Error-Message to reproduce:
---
# apt install xtables-addons-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  xtables-addons-common
Recommended packages:
  linux-headers
The following NEW packages will be installed:
  xtables-addons-common xtables-addons-dkms
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/343 kB of archives.
After this operation, 1914 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Selecting previously unselected package xtables-addons-common.
(Reading database ... 66169 files and directories currently installed.)
Preparing to unpack .../xtables-addons-common_2.11-3_amd64.deb ...
Unpacking xtables-addons-common (2.11-3) ...
Selecting previously unselected package xtables-addons-dkms.
Preparing to unpack .../xtables-addons-dkms_2.11-3_all.deb ...
Unpacking xtables-addons-dkms (2.11-3) ...
Setting up xtables-addons-common (2.11-3) ...
Processing triggers for libc-bin (2.24-8) ...
Setting up xtables-addons-dkms (2.11-3) ...
Loading new xtables-addons-2.11 DKMS files...
Building for 4.9.0-1-amd64
Building initial module for 4.9.0-1-amd64
Error!  Build of xt_ACCOUNT.ko failed for: 4.9.0-1-amd64 (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/xtables-addons/2.11/build/ for more information.
Processing triggers for man-db (2.7.6.1-2) ...


Make.log:
---
# cat /var/lib/dkms/xtables-addons/2.11/build/make.log
DKMS make.log for xtables-addons-2.11 for kernel 4.9.0-1-amd64 (x86_64)
Tue Jan 24 19:36:03 CET 2017
make: Entering directory '/usr/src/linux-headers-4.9.0-1-amd64'
make -C /usr/src/linux-headers-4.9.0-1-amd64
KBUILD_SRC=/usr/src/linux-headers-4.9.0-1-common \
-f /usr/src/linux-headers-4.9.0-1-common/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or
include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to
fix it.";   \
echo >&2 ;  \
/bin/false)
mkdir -p
/var/lib/dkms/xtables-addons/2.11/build/extensions/.tmp_versions ; rm -f
/var/lib/dkms/xtables-addons/2.11/build/extensions/.tmp_versions/*
make -f /usr/src/linux-headers-4.9.0-1-common/scripts/Makefile.build
obj=/var/lib/dkms/xtables-addons/2.11/build/extensions
   gcc-6
-Wp,-MD,/var/lib/dkms/xtables-addons/2.11/build/extensions/.compat_xtables.o.d
 -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/6/include
-I/usr/src/linux-headers-4.9.0-1-common/arch/x86/include
-I./arch/x86/include/generated/uapi -I./arch/x86/include/generated
-I/usr/src/linux-headers-4.9.0-1-common/include -I./include
-I/usr/src/linux-headers-4.9.0-1-common/arch/x86/include/uapi
-I/usr/src/linux-headers-4.9.0-1-common/include/uapi
-I./include/generated/uapi -include
/usr/src/linux-headers-4.9.0-1-common/include/linux/kconfig.h
-I/usr/src/linux-headers-4.9.0-1-common//var/lib/dkms/xtables-addons/2.11/build/extensions

Processed: Merge duplicates

2017-01-24 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 852472 xtables-addons-dkms
Bug #852472 [src:linux-signed (4)] linux-image-4.9.0-1-amd64 fails compiling 
xt_ACCOUNT.ko out of package xtables-addons-dkms
Warning: Unknown package '4'
Bug reassigned from package 'src:linux-signed (4)' to 'xtables-addons-dkms'.
No longer marked as found in versions 4.9.2-2.
Ignoring request to alter fixed versions of bug #852472 to the same values 
previously set
> forcemerge 851576 852472
Bug #851576 [xtables-addons-dkms] xtables-addons-dkms: Error building against 
Linux 4.9
Bug #852472 [xtables-addons-dkms] linux-image-4.9.0-1-amd64 fails compiling 
xt_ACCOUNT.ko out of package xtables-addons-dkms
Severity set to 'grave' from 'normal'
Marked as found in versions xtables-addons/2.11-3.
Merged 851576 852472
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851576
852472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852469: After kernel update lightdm hangs at start

2017-01-24 Thread Jörg Frings-Fürst 
Hello,

the infos:

the system is a fresh (yesterday) install of debian testing.

After the kernel update today lightdm starts, but only the console
shown. Lightdm also can't stop or restarted.

With the old kernel it's ok.


If you need more infos please ask me.


CU
Jörg


/var/log/apt/history.log:

Start-Date: 2017-01-24  13:13:16
Commandline: /usr/sbin/synaptic
Requested-By: jff (1000)
Install: debian-security-support:amd64 (2017.01.03)
End-Date: 2017-01-24  13:13:20

Start-Date: 2017-01-24  18:27:45
Commandline: apt-get dist-upgrade
Install: irqbalance:amd64 (1.1.0-2.2, automatic), firmware-linux-free:amd64 
(3.4, automatic), linux-image-4.9.0-1-amd64:amd64 (4.9.2-2, automatic)
Upgrade: linux-image-amd64:amd64 (4.8+77, 4.9+78)
End-Date: 2017-01-24  18:28:24

part of /var/log/daemon.log:

Jan 24 19:13:18 himalia systemd[1]: Starting Light Display Manager...
Jan 24 19:13:18 himalia systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Jan 24 19:13:18 himalia dbus[494]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Jan 24 19:13:18 himalia systemd[1]: Started Network Manager Script Dispatcher 
Service.
Jan 24 19:13:18 himalia sshd[598]: Could not load host key: 
/etc/ssh/ssh_host_dsa_key
Jan 24 19:13:18 himalia systemd[1]: Started OpenBSD Secure Shell server.
Jan 24 19:13:18 himalia dbus[494]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jan 24 19:13:18 himalia systemd[1]: Starting Hostname Service...
Jan 24 19:13:18 himalia systemd[1]: Started Light Display Manager.
Jan 24 19:13:18 himalia systemd[1]: Started Modem Manager.
Jan 24 19:13:18 himalia dbus[494]: [system] Successfully activated service 
'org.freedesktop.hostname1'
Jan 24 19:13:18 himalia systemd[1]: Started Hostname Service.
Jan 24 19:13:18 himalia nm-dispatcher: req:1 'hostname': new request (1 scripts)
Jan 24 19:13:18 himalia nm-dispatcher: req:1 'hostname': start running ordered 
scripts...
Jan 24 19:13:19 himalia dbus[494]: [system] Activating via systemd: service 
name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jan 24 19:13:19 himalia systemd[1]: Starting WPA supplicant...
Jan 24 19:13:19 himalia dbus[494]: [system] Successfully activated service 
'fi.w1.wpa_supplicant1'
Jan 24 19:13:19 himalia systemd[1]: Started WPA supplicant.
Jan 24 19:13:19 himalia wpa_supplicant[642]: Successfully initialized 
wpa_supplicant
Jan 24 19:13:20 himalia dhclient[643]: DHCPREQUEST of 10.10.7.101 on enp5s0 to 
255.255.255.255 port 67
Jan 24 19:13:20 himalia dhclient[643]: DHCPACK of 10.10.7.101 from 10.10.7.1
Jan 24 19:13:20 himalia avahi-daemon[485]: Joining mDNS multicast group on 
interface enp5s0.IPv4 with address 10.10.7.101.
Jan 24 19:13:20 himalia avahi-daemon[485]: New relevant interface enp5s0.IPv4 
for mDNS.
Jan 24 19:13:20 himalia avahi-daemon[485]: Registering new address record for 
10.10.7.101 on enp5s0.IPv4.
Jan 24 19:13:20 himalia nm-dispatcher: req:2 'connectivity-change': new request 
(1 scripts)
Jan 24 19:13:20 himalia nm-dispatcher: req:2 'connectivity-change': start 
running ordered scripts...
Jan 24 19:13:20 himalia dhclient[643]: bound to 10.10.7.101 -- renewal in 19800 
seconds.
Jan 24 19:13:20 himalia nm-dispatcher: req:3 'up' [enp5s0]: new request (1 
scripts)
Jan 24 19:13:20 himalia nm-dispatcher: req:3 'up' [enp5s0]: start running 
ordered scripts...
Jan 24 19:13:20 himalia dbus[494]: [system] Activating via systemd: service 
name='org.freedesktop.ColorManager' unit='colord.service'
Jan 24 19:13:20 himalia systemd[1]: Starting Manage, Install and Generate Color 
Profiles...
Jan 24 19:13:20 himalia systemd[1]: Reloading OpenBSD Secure Shell server.
Jan 24 19:13:20 himalia systemd[1]: Reloading.
Jan 24 19:13:20 himalia systemd[1]: apt-daily.timer: Adding 2h 46min 29.618430s 
random time.
Jan 24 19:13:20 himalia systemd[1]: Reloaded OpenBSD Secure Shell server.
Jan 24 19:13:20 himalia sshd[598]: Could not load host key: 
/etc/ssh/ssh_host_dsa_key
Jan 24 19:13:20 himalia dbus[494]: [system] Successfully activated service 
'org.freedesktop.ColorManager'
Jan 24 19:13:20 himalia systemd[1]: Started Manage, Install and Generate Color 
Profiles.
Jan 24 19:13:20 himalia systemd[1]: Reloading OpenBSD Secure Shell server.
Jan 24 19:13:20 himalia sshd[598]: Could not load host key: 
/etc/ssh/ssh_host_dsa_key
Jan 24 19:13:20 himalia systemd[1]: Reloaded OpenBSD Secure Shell server.
Jan 24 19:13:20 himalia systemd[1]: Reloading.
Jan 24 19:13:21 himalia wpa_supplicant[642]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-100 retry=1
Jan 24 19:13:21 himalia systemd[1]: apt-daily.timer: Adding 46min 1.642910s 
random time.
Jan 24 19:13:21 himalia avahi-daemon[485]: Joining mDNS multicast group on 
interface enp5s0.IPv6 with address fe80::e269:95ff:fe6b:c329.
Jan 24 19:13:21 himalia avahi-daemon[485]: New relevant interface enp5s0.IPv6 
for mDNS.
Jan 24 19:13:21 himalia avahi-daemon[485]: Registering new address record for

Bug#852469: After kernel update lightdm hangs at start

2017-01-24 Thread Jörg Frings-Fürst 
Package: src:linux
Version: 4.9.2-2
Severity: grave
File: linux-image-4.9.0

Hello,

I add some infos after bug is created.

CU
Jörg

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Micro-Star INT'L CO., LTD.
product_name: MS-16Y1
product_version: 1.0   
chassis_vendor: PEGATRON Computer Inc.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: E16Y1IMS.209
board_vendor: PEGATRON CORPORATION
board_name: P017
board_version: 1.0   

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family DRAM Controller [1462:109c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family Integrated Graphics Controller [1462:109c]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Micro-Star International Co., Ltd. [MSI] 6 Series/C200 
Series Chipset Family MEI Controller [1462:109c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd. [MSI] 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller [1462:109c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: Micro-Star International Co., Ltd. [MSI] 6 Series/C200 
Series Chipset Family High Definition Audio Controller [1462:109c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 1 [8086:1c10] (rev b5) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 2 [8086:1c12] (rev b5) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:

Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2

2017-01-24 Thread Ben Hutchings 
On Sat, 21 Jan 2017 21:00:18 +0100 Heinrich Schuchardt
 wrote:
> Package: linux-latest
> Severity: wishlist
> 
> Dear Maintainer,
> 
> please, add support for the Hardkernel Odroid C2 to the kernel configuration.
> 
> For 4.9 kernels this involves:
> 
> CONFIG_ARCH_MESON=y
> CONFIG_SERIAL_MESON=y
> CONFIG_SERIAL_MESON_CONSOLE=y
> CONFIG_HW_RANDOM_MESON=m
> CONFIG_I2C_MESON=m
> CONFIG_SPI_MESON_SPIFC=m
> CONFIG_PINCTRL_MESON=y
> CONFIG_MESON_GXBB_WATCHDOG=y
> CONFIG_PWM_MESON=m
> CONFIG_RESET_MESON=y
> CONFIG_MESON_SM=y
> CONFIG_COMMON_CLK_AMLOGIC=y

I can do all this, except I think the watchdog driver can and should be
a module.

> For 4.10 kernels this involves
> 
> CONFIG_ARCH_MESON=y
> CONFIG_DWMAC_MESON=y
> CONFIG_MESON_GXL_PHY=y
> CONFIG_SERIAL_MESON=y
> CONFIG_SERIAL_MESON_CONSOLE=y
> CONFIG_HW_RANDOM_MESON=m
> CONFIG_I2C_MESON=m
> CONFIG_SPI_MESON_SPIFC=m
> CONFIG_PINCTRL_MESON=y
> CONFIG_MESON_GXBB_WATCHDOG=y
> CONFIG_MESON_WATCHDOG=y
> CONFIG_DRM_MESON=m
> CONFIG_MMC_MESON_GX=y
> CONFIG_PWM_MESON=m
> CONFIG_RESET_MESON=y
> CONFIG_PHY_MESON8B_USB2=m
> CONFIG_MESON_SM=y
> CONFIG_COMMON_CLK_AMLOGIC=y

Given that we're going to be using 4.9 in Debian 9 'stretch', are you
interested in getting the Meson changes in 4.10 backported?

> The following patch is essential. It is queued for 4.10-rc6:
> 
> ARM64: dts: meson-gx: Add firmware reserved memory zones
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ecb88f3001ed9ee8c53450d971de8c18bcbf7925

This is queued up for the next upload.  For 4.9 I had to change the
filename to arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.


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

Re: why 4.9.2-2 didn't migrate to testing?

2017-01-24 Thread Roger Shimizu 
On Tue, Jan 24, 2017 at 11:40 PM, Julien Cristau  wrote:
> On 01/24/2017 03:20 PM, Roger Shimizu wrote:
>> Hi there,
>>
>> As title, may I know the reason why 4.9.2-2 didn't migrate to testing?
>>
> Who says it didn't?  4.9.2-2 *is* in testing.

I just saw the QA page says "11 days old (needed 10 days)"
Sorry for the noise.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

why 4.9.2-2 didn't migrate to testing?

2017-01-24 Thread Roger Shimizu 
Hi there,

As title, may I know the reason why 4.9.2-2 didn't migrate to testing?

QA page [0] shows some items, but all "never mind", and there's "Valid
candidate" at the end.

[0] https://qa.debian.org/excuses.php?package=linux

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Re: why 4.9.2-2 didn't migrate to testing?

2017-01-24 Thread Julien Cristau 
On 01/24/2017 03:20 PM, Roger Shimizu wrote:
> Hi there,
> 
> As title, may I know the reason why 4.9.2-2 didn't migrate to testing?
> 
Who says it didn't?  4.9.2-2 *is* in testing.

Cheers,
Julien

Bug#849640: Fix

2017-01-24 Thread Dylan Hanner 

Unplug all VGA monitors and reboot and you're good to go till they fix this.


--
*Dylan Hanner*
Developer
e:  d...@extravision.com 
p:  0161 817 2938
t:  @extravision 
w:  www.extravision.com 

Extravision - email worth seeing 
Registered in the UK at: 107 Timber Wharf, 33 Worsley Street, 
Manchester, M15 4LD.

Company Reg No: 0‌‌5017214 VAT: GB 8‌‌24 5386 19

This e-mail is intended solely for the person to whom it is addressed 
and may contain confidential or privileged information.
Any views or opinions presented in this e-mail are solely of the author 
and do not necessarily represent those of Extravision Ltd.

Bug#851533: NBD: exported files over something around 1 TiB get an insane device size on the client side and are actually empty

2017-01-24 Thread Roger Shimizu 
On Mon, Jan 16, 2017 at 11:37 AM, Ben Hutchings  wrote:
>
> This should possibly go to 4.9-stable, but in any case I've queued it
> up for our next upload.

After applying this patch, it fails to build on armel [0]
And I find it need another patch [1]

[0] https://lists.debian.org/debian-kernel/2017/01/msg00387.html
[1] https://git.kernel.org/linus/e88f72cb9f54f6d244e55f629fe5e2f34ca6f9ed

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Re: debian kernel builds failed under armel for the sid branch

2017-01-24 Thread Roger Shimizu 
On Tue, Jan 24, 2017 at 9:12 PM, Roger Shimizu  wrote:
> Hi there,
>
> I found debian kernel src builds failed under armel for the sid
> branch, while amd64 is fine.
> git bisect traced to the following commit:
>
> [a7f877c1f1d9ac05045e4a108e54dc5a40d842f1] nbd: use loff_t for
> blocksize and nbd_set_size args (Closes: #851533)
>
> armel build log shows:
> ERROR: "__aeabi_ldivmod" [drivers/block/nbd.ko] undefined!

Seems we also need to backport this patch:

commit e88f72cb9f54f6d244e55f629fe5e2f34ca6f9ed
Author: Jens Axboe 
AuthorDate: Sat Dec 3 12:08:03 2016 -0700
Commit: Jens Axboe 
CommitDate: Sat Dec 3 12:08:03 2016 -0700

nbd: fix 64-bit division

We have this:

ERROR: "__aeabi_ldivmod" [drivers/block/nbd.ko] undefined!
ERROR: "__divdi3" [drivers/block/nbd.ko] undefined!
nbd.c:(.text+0x247c72): undefined reference to `__divdi3'

due to a recent commit, that did 64-bit division. Use the proper
divider function so that 32-bit compiles don't break.

Fixes: ef77b515243b ("nbd: use loff_t for blocksize and nbd_set_size args")
Signed-off-by: Jens Axboe 

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

debian kernel builds failed under armel for the sid branch

2017-01-24 Thread Roger Shimizu 
Hi there,

I found debian kernel src builds failed under armel for the sid
branch, while amd64 is fine.
git bisect traced to the following commit:

[a7f877c1f1d9ac05045e4a108e54dc5a40d842f1] nbd: use loff_t for
blocksize and nbd_set_size args (Closes: #851533)

armel build log shows:
ERROR: "__aeabi_ldivmod" [drivers/block/nbd.ko] undefined!

BTW. I use the wiki page I created [0] to cross-build armel image
under amd64 host machine.

[0] https://wiki.debian.org/HowToCrossBuildAnOfficialDebianKernelPackage

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Re: [PATCH v2] [arm64] Add more options

2017-01-24 Thread Ben Hutchings 
On Tue, 2017-01-24 at 11:35 +0200, Riku Voipio wrote:
> On 24 January 2017 at 04:21, Ben Hutchings 
> wrote:
> > On Fri, 2017-01-13 at 16:41 +0200, riku.voi...@linaro.org wrote:
> > > From: Riku Voipio 
> > > 
> > > * Enable Cavium ThunderX server architecutre
> > > * Enable server related options
> > > * Enable CMA for DB410c DRM
> > 
> > CMA and NUMA both require an ABI bump (which we'll do at some point
> > before release, but probably not the next upload).
> > 
> > > * Some missing gpio driver enabled in upstream defconfig
> > > * DT cpufreq, spidev and missing DB410c audio setting
> > > ---
> > 
> > [...]
> > > +##
> > > +## file: drivers/base/Kconfig
> > > +##
> > > +CONFIG_DMA_CMA=y
> > > +CONFIG_CMA_SIZE_MBYTES=64
> > 
> > I notice this is higher than the default (16).  Is it a sensible
> > default for all/most platforms that will need CMA?  What about
> > platforms that don't use CMA at all, where the CMA zone will be
> > wasted?
> 
> CMA memory isn't wasted. It is populated with movable pages until a
> CMA user needs a continuous block from it. Userspace (unless mlocked)
> and cache/buffers are all movable, so I don't think CMA would be
> underutilized in memory pressure scenarios.

Oh, yes I see.

> 16M was not enough for getting DRM display on dragonboard 410c. I can
> check what is the minimum needed.

Given a single full-HD frame needs 8 MiB, I can see 16 MiB total would
be too small.  But then, multiply by 4 for 4K frames, and 64 MiB would
also be constraining.  (I don't know whether we currently support any
hardware with 4K output.)

Perhaps it would make sense to set a percentage instead (e.g.
CONFIG_CMA_SIZE_MBYTES=0, CONFIG_CMA_SIZE_PERCENTAGE=10)?

> > [...]
> > >  @@ -682,6 +734,18 @@ CONFIG_USB_DWC3_DUAL_ROLE=y
> > >  ## file: drivers/usb/gadget/Kconfig
> > >  ##
> > >  CONFIG_USB_GADGET=m
> > > +CONFIG_USB_CONFIGFS=m
> > 
> > I don't think that does anything useful unless we also enable some more
> > CONFIG_USB_CONFIGFS_* options.
> 
> Gah, the set of configfs, functionfs and gadgetfs is so confusing
> here..
[...]

Yes it is!

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.



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

[PATCH v3 1/3] builddeb: Update a few outdated and hardcoded strings

2017-01-24 Thread riku . voipio 
From: Riku Voipio 

The builddeb script has some hardcoded references to Linux version 2.6
which is ancient. Drop Provides as the virtual packages provided are not
useful anymore. Leave the Provides for linux-kernel-headers, as someone
might still be referring to it.

While at it, updated copyright date and drop Standards-Version field.

Cc: Timo Sigurdsson 
Cc: Ben Hutchings  
Signed-off-by: Riku Voipio 
---
v3: Drop Standards-Version instead of updating it.
---
 scripts/package/builddeb | 7 +--
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 3c575cd07888..6075392616de 100755
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -265,7 +265,7 @@ This is a packacked upstream version of the Linux kernel.
 The sources may be found at most Linux ftp sites, including:
 ftp://ftp.kernel.org/pub/linux/kernel
 
-Copyright: 1991 - 2015 Linus Torvalds and others.
+Copyright: 1991 - 2017 Linus Torvalds and others.
 
 The git repository for mainline kernel development is at:
 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
@@ -288,7 +288,6 @@ Section: kernel
 Priority: optional
 Maintainer: $maintainer
 Build-Depends: $build_depends
-Standards-Version: 3.8.4
 Homepage: http://www.kernel.org/
 EOF
 
@@ -296,7 +295,6 @@ if [ "$ARCH" = "um" ]; then
cat <> debian/control
 
 Package: $packagename
-Provides: linux-image, linux-image-2.6, linux-modules-$version
 Architecture: any
 Description: User Mode Linux kernel, version $version
  User-mode Linux is a port of the Linux kernel to its own system call
@@ -313,7 +311,6 @@ else
cat <> debian/control
 
 Package: $packagename
-Provides: linux-image, linux-image-2.6, linux-modules-$version
 Suggests: $fwpackagename
 Architecture: any
 Description: Linux kernel, version $version
@@ -346,7 +343,6 @@ rm -f "$objtree/debian/hdrsrcfiles" 
"$objtree/debian/hdrobjfiles"
 cat <> debian/control
 
 Package: $kernel_headers_packagename
-Provides: linux-headers, linux-headers-2.6
 Architecture: any
 Description: Linux kernel headers for $KERNELRELEASE on \${kernel:debarch}
  This package provides kernel header files for $KERNELRELEASE on 
\${kernel:debarch}
@@ -404,7 +400,6 @@ if [ -n "$BUILD_DEBUG" ] ; then
 
 Package: $dbg_packagename
 Section: debug
-Provides: linux-debug, linux-debug-$version
 Architecture: any
 Description: Linux kernel debugging symbols for $version
  This package will come in handy if you need to debug the kernel. It provides
-- 
2.11.0

Re: [PATCH v2] [arm64] Add more options

2017-01-24 Thread Riku Voipio 
On 24 January 2017 at 04:21, Ben Hutchings  wrote:
> On Fri, 2017-01-13 at 16:41 +0200, riku.voi...@linaro.org wrote:
>> From: Riku Voipio 
>>
>> * Enable Cavium ThunderX server architecutre
>> * Enable server related options
>> * Enable CMA for DB410c DRM
>
> CMA and NUMA both require an ABI bump (which we'll do at some point
> before release, but probably not the next upload).
>
>> * Some missing gpio driver enabled in upstream defconfig
>> * DT cpufreq, spidev and missing DB410c audio setting
>> ---
> [...]
>> +##
>> +## file: drivers/base/Kconfig
>> +##
>> +CONFIG_DMA_CMA=y
>> +CONFIG_CMA_SIZE_MBYTES=64
>
> I notice this is higher than the default (16).  Is it a sensible
> default for all/most platforms that will need CMA?  What about
> platforms that don't use CMA at all, where the CMA zone will be wasted?

CMA memory isn't wasted. It is populated with movable pages until a
CMA user needs a continuous block from it. Userspace (unless mlocked)
and cache/buffers are all movable, so I don't think CMA would be
underutilized in memory pressure scenarios.

16M was not enough for getting DRM display on dragonboard 410c. I can
check what is the minimum needed.

> [...]
>>  @@ -682,6 +734,18 @@ CONFIG_USB_DWC3_DUAL_ROLE=y
>>  ## file: drivers/usb/gadget/Kconfig
>>  ##
>>  CONFIG_USB_GADGET=m
>> +CONFIG_USB_CONFIGFS=m
>
> I don't think that does anything useful unless we also enable some more
> CONFIG_USB_CONFIGFS_* options.

Gah, the set of configfs, functionfs and gadgetfs is so confusing here..

>> +
>> +##
>> +## file: drivers/usb/gadget/legacy/Kconfig
>> +##
>> +CONFIG_USB_ETH=m
>> +CONFIG_USB_ETH_RNDIS=y
>> +CONFIG_USB_GADGETFS=m
>> +CONFIG_USB_FUNCTIONFS=m
>> +CONFIG_USB_FUNCTIONFS_ETH=y
>> +CONFIG_USB_FUNCTIONFS_RNDIS=y
>> +CONFIG_USB_FUNCTIONFS_GENERIC=y
> [...]
>
> I think the gadget config should be consolidated in
> debian/config/config, leaving individual architectures to enable only
> CONFIG_USB_GADGET and driver-specific symbols for gadget support.  Can
> you do that as a preparatory patch?

Ok, I'll have a look.

Riku

Re: Question about x86_energy_perf_policy

2017-01-24 Thread Raphaël Halimi 
Le 24/01/2017 à 04:58, Ben Hutchings a écrit :
>> But still, by sheer curiosity, I'd like to know : is there a reason for
>> Debian not providing this binary, and/or plans to change that ?
> 
> I'll add it to the linux-cpupower package.  Sorry that this is still
> different from Ubuntu, but I don't think their packaging is very
> sensible.

Thanks for the answer. I don't mind the two packages named differently
in Debian and Ubuntu, I settled this in my source package thanks to
Raphaël Hertzog's blog entry about this [1].

[1]
https://raphaelhertzog.com/2010/09/27/different-dependencies-between-debian-and-ubuntu-but-common-source-package/

My question was more about the reason why the binary was missing from
Debian, but then again, I was just curious.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature