ethtool_4.15-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Apr 2018 12:47:40 +0200
Source: ethtool
Binary: ethtool
Architecture: source
Version: 1:4.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Description:
 ethtool- display or change Ethernet device settings
Changes:
 ethtool (1:4.15-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/control: Point Vcs URLs to Salsa
   * debian/control: Update Standards-Version to 4.1.3; no changes needed
   * debian/control: Set Maintainer to kernel team; add Anibal to Uploaders
Checksums-Sha1:
 d07d14a0cfb6e453567abba5727b06665298b030 1955 ethtool_4.15-1.dsc
 beb94fd3953290f8a06da5647281e9807eb0918e 219408 ethtool_4.15.orig.tar.xz
 e4faab88ec051137fa86ac5ceab34508c76167a0 7084 ethtool_4.15-1.debian.tar.xz
 14209784ac10fa636db654cd9761d8cab935f4f9 5768 ethtool_4.15-1_source.buildinfo
Checksums-Sha256:
 ade5e1ee2cfe61110271b1838168b566cce810c67ab9077449bd9cdab4807a93 1955 
ethtool_4.15-1.dsc
 71f7fd32483ffdc7c6c4d882e230714eb101df0a46cbe396dbeb8ac78f1ef91a 219408 
ethtool_4.15.orig.tar.xz
 d0d182f0c2e8294811a718913e0c08bf18d26fbfc2dbaa7043a6f68df6be34d5 7084 
ethtool_4.15-1.debian.tar.xz
 0b3f5a05f41e42cc18dd00f3eb48df5ae8100d7fffdcb47afbeda0bc22122a3a 5768 
ethtool_4.15-1_source.buildinfo
Files:
 6a13f4771727384754887acd2a5dda80 1955 net optional ethtool_4.15-1.dsc
 1d9a82de6c9131d1caa626f77c6cdb57 219408 net optional ethtool_4.15.orig.tar.xz
 f893a0dbba3c74f2fec8433f7b1d7367 7084 net optional ethtool_4.15-1.debian.tar.xz
 124cfdb8aa3e65c03684bbdd229d1b29 5768 net optional 
ethtool_4.15-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlrIpAUACgkQ57/I7JWG
EQnNORAAiVVcc6f8NrIU9fbdqTtYYGxtRs5Yi02Ufp6OLQUj6HUixEHdpwhGNhGs
Hu/RSfepYa8hdIJ1W0DwgT6VA4goj2X/uW1XsTePlOT2nu345ZTR6ApI8CK//mFC
lDX9gNncJxajiNQpMd9/Iz0wK0qoCjyAmEVwU0s46mU3Bglp1GkTPOBU+aPjeikT
dPhS/oznwJyvJSWcZx4HIhK228wI2lI9UJ8fl77Snq9M/jz/C1o0Jyl0D4+48jmt
1YN9BxdJFwi8AxuWm6cbj3mIeVXKzsiUnH5eMrmqI5ifEOwvQGcb4IffW/Y5edNi
WGo0XVTjBl2ACQfwcnmZ8uIcZM43RP+fn/zJsCUsjf/FDGxB+MqcRFvsdKb/LdbN
YMHBc2K84KJxoYt0kbHViq7EEwvH/EnIBLz3XksdH/DN2Ul7a9wkynys2QxaQ4G9
fIbvkf3/cY03MXx/X+6NL6LE5lRTIiq9sz3OQ4iq3Wxiv4D7Z9XEC0mRWK6r2Knn
UtAS9EX725Tp06j1iYAuBpuPkPzbghjyrkjKFkg38JFN1kb8XdoHAXRFno1Sfgld
djoR/SH4Zi+8g74FqY+V4Iy56EfUezfO8OJzJsyiQ30Kb8eA+qKDkI4HfGiOV+A4
NuecCteW5gi+dhY+/yq2J9GBVkIGZnCr3pCbMxV14dkocVo4Ar4=
=S1L3
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#895129: linux: Battery not detected on Lamina 2-in-1 tablet

[Marcus Lundblad]

Source: linux
Severity: normal

Dear Maintainer,

I have a Lamina T-1016B 2-in-1 tablet where the battery is not detected
(the top bar in GNOME shows only the power icon, like on the desktop machine).
Checking in /var/log/messages I could see the following (grep:ing on ACPI):

Apr  6 09:17:21 eridanus kernel: [5.663167] ACPI: AC: found native INT33F4 
PMIC, not loading
Apr  6 09:17:21 eridanus kernel: [5.956763] ACPI: AC: found native INT33F4 
PMIC, not loading
Apr  6 08:20:24 eridanus kernel: [5.720266] ACPI: AC: found native INT33F4 
PMIC, not loading
Apr  6 08:20:24 eridanus kernel: [6.020086] ACPI: AC: found native INT33F4 
PMIC, not loading
Apr  6 08:23:09 eridanus kernel: [5.656934] ACPI: AC: found native INT33F4 
PMIC, not loading
Apr  6 08:23:09 eridanus kernel: [5.979635] ACPI: AC: found native INT33F4 
PMIC, not loading
Apr  6 08:25:49 eridanus kernel: [5.849791] ACPI: AC: found native INT33F4 
PMIC, not loading
Apr  6 08:25:49 eridanus kernel: [6.150902] ACPI: AC: found native INT33F4 
PMIC, not loading

Checking in the kernel sources, I could see the following:
In https://github.com/torvalds/linux/blob/master/drivers/acpi/battery.c

There is a blacklist of ACPI HIDs at line 101:

/* Lists of PMIC ACPI HIDs with an (often better) native battery driver */
static const char * const acpi_battery_blacklist[] = {
"INT33F4", /* X-Powers AXP288 PMIC */
};

Further down there's a section for bailing out on blacklisted HIDs at 1491:

for (i = 0; i < ARRAY_SIZE(acpi_battery_blacklist); i++)
if (acpi_dev_present(acpi_battery_blacklist[i], "1", -1)) {
pr_info(PREFIX ACPI_BATTERY_DEVICE_NAME
": found native %s PMIC, not loading\n",
acpi_battery_blacklist[i]);
return;
}

In __init acpi_battery_init_async

I suppose enabling the approriate module(s) would maybe solve this.
In the make menuconfig I could see the following drivers:

AXP288_ADC, AXP288_CHARGER, and AXP288_FUEL_GAUGE

I tried building a custom kernel, but upon booting in panics,
but it seems to be because the initrams fs is not able to mount, I guess
the image wasn't properly installed in GRUB, or something like that.

By the way, the info below shows kernel 4.14, but that's because I ran
reportbug from my desktop, and haven't rebooted into the newest kernel yet
I hope this doesn't create a hassle.

Thanks!
Regards,
Marcus Lundblad

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), 
LANGUAGE=sv_SE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processing of ethtool_4.15-1_source.changes

[Debian FTP Masters]

ethtool_4.15-1_source.changes uploaded successfully to localhost
along with the files:
  ethtool_4.15-1.dsc
  ethtool_4.15.orig.tar.xz
  ethtool_4.15-1.debian.tar.xz
  ethtool_4.15-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#895131: linux-perf-4.16: Add libopencsd support to perf

[Wookey]

Package: linux-perf-4.16
Version: 4.16~rc6-1~exp1
Severity: wishlist
Tags: patch

In kernel 4.16 perf has support for libopencsd, which decodes arm
coresight trace packets.  This should be enabled in debian kernels so
that it 'just works' for users.  perf compilation picks up libopencsd
if it installed so enabling it is simply a matter of adding it to the
build-dependencies so that it is available at build time.

Attached is a patch that does this.

However note that, whilst libopencsd is now packaged for debian it has
not yet been uploaded to the archive (one build issue remains to be
fixed before it can be uploaded), and clearly this build-dep can't be
added until the library is actually available. So this bug is blocked
on #891955
diff -Nru linux-4.16~rc6/debian/changelog linux-4.16~rc6/debian/changelog
--- linux-4.16~rc6/debian/changelog 2018-03-20 13:52:03.0 +
+++ linux-4.16~rc6/debian/changelog 2018-04-06 21:12:15.0 +
@@ -1,3 +1,10 @@
+linux (4.16~rc6-1~exp2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * add build-dep on libopencsd for perf on arm
+
+ -- Wookey   Fri, 06 Apr 2018 22:12:15 +0100
+
 linux (4.16~rc6-1~exp1) experimental; urgency=medium
 
   * New upstream release candidate
diff -Nru linux-4.16~rc6/debian/config.defines.dump 
linux-4.16~rc6/debian/config.defines.dump
diff -Nru linux-4.16~rc6/debian/control linux-4.16~rc6/debian/control
diff -Nru linux-4.16~rc6/debian/control.md5sum 
linux-4.16~rc6/debian/control.md5sum
diff -Nru linux-4.16~rc6/debian/rules.gen linux-4.16~rc6/debian/rules.gen
diff -Nru linux-4.16~rc6/debian/templates/control.source.in 
linux-4.16~rc6/debian/templates/control.source.in
--- linux-4.16~rc6/debian/templates/control.source.in   2018-03-20 
13:46:09.0 +
+++ linux-4.16~rc6/debian/templates/control.source.in   2018-04-06 
21:12:15.0 +
@@ -45,6 +45,7 @@
  libnuma-dev [amd64 arm64 hppa i386 mips mips64 mips64el mipsel mipsn32 
mipsn32el mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el powerpc 
powerpcspe ppc64 ppc64el sparc x32] ,
  libperl-dev ,
  libunwind8-dev [amd64 armel armhf arm64 i386] ,
+ libopencsd-dev ,
  python-dev ,
 # used by upstream to build usbip
  autoconf ,

Processed: block 895131 with 889970

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 895131 with 889970
Bug #895131 [linux-perf-4.16] linux-perf-4.16: Add libopencsd support to perf
895131 was not blocked by any bugs.
895131 was not blocking any bugs.
Added blocking bug(s) of 895131: 889970
> thanks
Stopping processing here.

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

Bug#895129: linux: Battery not detected on Lamina 2-in-1 tablet

[Sebastian Reichel]

Hi,

On Sat, Apr 07, 2018 at 01:04:27PM +0200, Marcus Lundblad wrote:
> Source: linux
> Severity: normal
> 
> Dear Maintainer,
> 
> I have a Lamina T-1016B 2-in-1 tablet where the battery is not detected
> (the top bar in GNOME shows only the power icon, like on the desktop machine).
> Checking in /var/log/messages I could see the following (grep:ing on ACPI):
> 
> Apr  6 09:17:21 eridanus kernel: [5.663167] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> Apr  6 09:17:21 eridanus kernel: [5.956763] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> Apr  6 08:20:24 eridanus kernel: [5.720266] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> Apr  6 08:20:24 eridanus kernel: [6.020086] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> Apr  6 08:23:09 eridanus kernel: [5.656934] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> Apr  6 08:23:09 eridanus kernel: [5.979635] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> Apr  6 08:25:49 eridanus kernel: [5.849791] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> Apr  6 08:25:49 eridanus kernel: [6.150902] ACPI: AC: found native 
> INT33F4 PMIC, not loading
> 
> Checking in the kernel sources, I could see the following:
> In https://github.com/torvalds/linux/blob/master/drivers/acpi/battery.c
> 
> There is a blacklist of ACPI HIDs at line 101:
> 
> /* Lists of PMIC ACPI HIDs with an (often better) native battery driver */
> static const char * const acpi_battery_blacklist[] = {
>   "INT33F4", /* X-Powers AXP288 PMIC */
> };
> 
> Further down there's a section for bailing out on blacklisted HIDs at 1491:
> 
> for (i = 0; i < ARRAY_SIZE(acpi_battery_blacklist); i++)
>   if (acpi_dev_present(acpi_battery_blacklist[i], "1", -1)) {
>   pr_info(PREFIX ACPI_BATTERY_DEVICE_NAME
>   ": found native %s PMIC, not loading\n",
>   acpi_battery_blacklist[i]);
>   return;
> }
> 
> In __init acpi_battery_init_async
> 
> I suppose enabling the approriate module(s) would maybe solve this.
> In the make menuconfig I could see the following drivers:
> 
> AXP288_ADC, AXP288_CHARGER, and AXP288_FUEL_GAUGE
> 
> I tried building a custom kernel, but upon booting in panics,
> but it seems to be because the initrams fs is not able to mount, I guess
> the image wasn't properly installed in GRUB, or something like that.
> 
> By the way, the info below shows kernel 4.14, but that's because I ran
> reportbug from my desktop, and haven't rebooted into the newest kernel yet
> I hope this doesn't create a hassle.

Last year the blacklist was introduced for the ACPI battery driver:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/acpi/battery.c?id=dccfae6d4f4c2cfa1fdc3bf55755fcad02184b99

Enabling AXP288_FUEL_GAUGE (and dependencies) should result in
proper battery information. If there are still issues with your
system after enabling the config option, send a mail to the
following addresses:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?id=dccfae6d4f4c2cfa1fdc3bf55755fcad02184b99#n10012

-- Sebastian


signature.asc
Description: PGP signature

Re: armel/marvell kernel size

[Roger Shimizu]

Dear Rogério,

I'll reply to you later, in a separate email.


Dear kernel folks,

After all kinda tests recently, together with the patch from Leigh
Brown (CC-ed) that disabled VT, finally the armel/marvell can be
reduced under 2MB again, without introducing a new flavour.
So I already pushed the changes to master and sid branch in salsa.
qnap support will be back in next debian kernel release.

Cheers,
Roger

On Tue, Apr 3, 2018 at 2:37 PM, Rogério Brito  wrote:
> Dear Roger, Ben and others.
>
> On Sun, Apr 1, 2018 at 10:25 AM, Roger Shimizu  wrote:
>> On Wed, Jan 24, 2018 at 3:30 AM, Ben Hutchings  wrote:
>>> On Mon, 2018-01-22 at 22:38 +0900, Roger Shimizu wrote:
>>> There's an upstream change in cfg80211 that enables direct-loading of
>>> wireless rules, which requires public key crypto in the kernel.  There
>>> doesn't appear to be any option to disable that mode, even though we
>>> don't need it because crda still works.  Maybe you could disable
>>> wireless networking completely?
>>
>> I finally settled a solution, by introducing a new armel flavour:
>> mini, which doesn't support wireless.
>> There're still some users that need wireless, so I didn't remove
>> wireless from armel/marvell directly.
>
> I think that we should still strive to pretend that there's a hard 2MB
> limit and to shave some parts that can before we start creating a new
> flavor of the kernel... This would force us to think harder about
> disabling things in general... In general, I think that we can discuss
> a little bit more about what to include/exclude from such smaller
> kernels and which flavors to have.
>
> In other words, I agree with your end goal, but, perhaps, we can plan
> this a bit more...
>
>> So here I propose to have:
>> - marvell to support all generic feature and being able to tuned for
>> performance.
>> - mini without wireless and being minimum.
>>
>> Patches are all enclosed, and pushed to salsa rosh/armel_mini branch.
>> - 0001: Bring back qnap support by a new armel flavour: mini (Disable
>> WIRELESS, WLAN, etc)
>> - 0002: [armel/mini] Add flavour mini to installer
>> - 0003: [armel/mini] Further change a few features as module (I2C,
>> I2C_CHARDEV, I2C_MV64XXX,
>>   MTD, MTD_CMDLINE_PARTS, RTC_DRV_MV, and SPI_ORION)
>
> I would make your commits more granular, with one semantic change per
> commit, to revert and or/bisect in an easier fashion...
>
>> I tested on stretch by cross compiling, here's generated kernel size.
>> - original 4.16~rc6-1~exp2: 2142704
>> - After patch 0001: 2017088
>> - After patch 0002: 2017088
>> - After patch 0003: 1985896
>>
>> Here's my testing result regarding those features that changed to module:
>> (tested under stretch)
>
> I'm doing my tests under testing (buster). See more below.
>
>>> Some options that could possibly be changed from y to m:
>>>
>>> - I2C, I2C_CHARDEV, I2C_MV64XXX.  initramfs-tools should include I2C
>>> drivers to the initramfs if needed, but I'm not certain.
>>
>> No, i2c nor i2c_mv64xxx will be loaded. But my armel box seems fine
>> without them.
>> Of course, manually "modprobe i2c_mv64xxx" will load the module well.
>
> While I have compiled a kernel with those options all enabled as
> modules, I have not yet had time to boot it (in fact, I created a lot
> of kernels that I want to test all in one sitting), but I agree with
> the principle of your testing, Roger and, in the worst case, we can
> instruct the users to add those to /etc/modules if they absolutely
> need them.
>
> I would not qualify this as a change for only a new kernel flavor,
> that is, I would make this change in general...
>
>>> - MTD, MTD_CMDLINE_PARTS, etc.  But I'm pretty sure this will break
>>> some systems unless initramfs-tools is updated to include and load the
>>> cmdlinepart module.
>>>
>>> - RTC_DRV_MV (and disable RTC_HCTOSYS).  There's a udev rule that
>>> should load the system clock from the first RTC if its driver is a
>>> module.
>>>
>>> - SPI_ORION.  initramfs-tools should include this in the initramfs if
>>> needed, but I'm not certain.
>>
>> Yes, above 3 modules are loaded without glitch.
>
> All those are generic material that I would also make generic instead
> of only particular to a given flavor.
>
>>> Some options that could possibly be disabled:
>>>
>>> - AUDIT.  This is quite a niche feature.
>>
>> I tried, but couldn't. Maybe next time.
>
> You probably missed this, but I said in a previous message that AUDIT
> is automatically selected by AppArmor. In other words, you can have
> only the following options:
>
> * with AppArmor (and AUDIT)
> * without AppArmor (but with AUDIT)
> * without AppArmor and without AUDIT
>
> From my perception, Ben was mildly opposed to having AppArmor disabled
> by default and wanted to have the kernel as close as possible to other
> arches...
>
> For that reason, I would still keep AppArmor in the big, reference
> armel kernel, but opt to create a flavor 

Re: armel/marvell kernel size

[Roger Shimizu]

On Sat, Apr 7, 2018 at 11:16 PM, Roger Shimizu  wrote:
> Dear kernel folks,
>
> After all kinda tests recently, together with the patch from Leigh
> Brown (CC-ed) that disabled VT, finally the armel/marvell can be
> reduced under 2MB again, without introducing a new flavour.

Sorry, I forgot to mention the post that Leigh Brown provided the patch:
- https://lists.debian.org/debian-kernel/2018/03/msg00223.html

And the patch, reducing armel image size under 2MB, and pushed to
master branch is:
- https://salsa.debian.org/kernel-team/linux/commit/a4fdfa09

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

Processing of linux_4.15.11-1~bpo9+1_multi.changes

[Debian FTP Masters]

linux_4.15.11-1~bpo9+1_multi.changes uploaded successfully to localhost
along with the files:
  linux_4.15.11-1~bpo9+1.dsc
  linux_4.15.11-1~bpo9+1.debian.tar.xz
  linux_4.15.11-1~bpo9+1_source.buildinfo
  linux-doc-4.15_4.15.11-1~bpo9+1_all.deb
  linux-headers-4.15.0-0.bpo.2-common_4.15.11-1~bpo9+1_all.deb
  linux-source-4.15_4.15.11-1~bpo9+1_all.deb
  linux-support-4.15.0-0.bpo.2_4.15.11-1~bpo9+1_all.deb
  lockdep_4.15.11-1~bpo9+1_all.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

linux_4.15.11-1~bpo9+1_multi.changes is NEW

[Debian FTP Masters]

binary:acpi-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:acpi-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:acpi-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:affs-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:affs-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:affs-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:affs-modules-4.15.0-0.bpo.2-octeon-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-armmp-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:ata-modules-4.15.0-0.bpo.2-powerpc64le-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-armmp-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-octeon-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-powerpc64le-di is NEW.
binary:btrfs-modules-4.15.0-0.bpo.2-s390x-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-octeon-di is NEW.
binary:cdrom-core-modules-4.15.0-0.bpo.2-powerpc64le-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-armmp-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-octeon-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-powerpc64le-di is NEW.
binary:crc-modules-4.15.0-0.bpo.2-s390x-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-armmp-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-octeon-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-powerpc64le-di is NEW.
binary:crypto-dm-modules-4.15.0-0.bpo.2-s390x-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-armmp-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-octeon-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-powerpc64le-di is NEW.
binary:crypto-modules-4.15.0-0.bpo.2-s390x-di is NEW.
binary:dasd-extra-modules-4.15.0-0.bpo.2-s390x-di is NEW.
binary:dasd-modules-4.15.0-0.bpo.2-s390x-di is NEW.
binary:efi-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:efi-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:efi-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:efi-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:efi-modules-4.15.0-0.bpo.2-armmp-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-686-pae-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-amd64-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-arm64-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-armmp-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-loongson-3-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-octeon-di is NEW.
binary:event-modules-4.15.0-0.bpo.2-powerpc64le-di is NEW.
binary:ext4-modules-4.15.0-0.bpo.2-4kc-malta-di is NEW.
binary:ext4-modules-4.15.0-0.bpo.2-5kc-malta-di is NEW.
binary:ext4-modules-4.15.0-0.bpo.2-686-di is NEW.
binary:ext4-modules-4.15.0-0.bpo.2-686-pae-di is NEW.

Bug#895137: linux-image-4.15.0-2-armmp: Internal error: Oops: 80000005 [#1] SMP ARM on Odroid XU4

[Jochen Sprickerhof]

Package: src:linux
Version: 4.15.11-1
Severity: normal

Hi,

I found a regression in linux-image-4.15.0-2-armmp on Odroid XU4Q
resulting in the kernel log below. Downgrading to 4.14.0-3-armmp doesn't
show this behaviour, so I assume it's a regression. Also, restarting
udev takes along time, maybe related. The Odroid works fine otherwise.
I can reproduce this on two different Odroids and can try to bisect next
weekend.

[9.323839] random: crng init done
[9.421188] leds_pwm pwmleds: unable to request PWM for blue:heartbeat: -517
[9.427447] pwm-fan pwm-fan: Could not get PWM
[9.442181] Unable to handle kernel paging request at virtual address 
18e64938
[9.448016] pgd = 08aa549d
[9.450609] [18e64938] *pgd=
[9.454217] Internal error: Oops: 8005 [#1] SMP ARM
[9.459358] Modules linked in: evdev cpufreq_dt(+) pwm_fan leds_pwm 
binfmt_misc ip_tables x_tables autofs4 crc32c_generic ext4 crc16 mbcache jbd2 
fscrypto xhci_plat_hcd xhci_hcd dwc3 udc_core phy_generic clk_s2mps11 s2mps11 
dwc3_exynos phy_exynos_mipi_video phy_exynos_dp_video i2c_exynos5 ohci_exynos 
ohci_hcd ehci_exynos ehci_hcd dw_mmc_exynos dw_mmc_pltfm dw_mmc usbcore 
phy_exynos_usb2 phy_exynos5_usbdrd usb_common
[9.496115] CPU: 6 PID: 297 Comm: systemd-udevd Not tainted 4.15.0-2-armmp 
#1 Debian 4.15.11-1
[9.496121] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[9.496132] PC is at 0x18e64938
[9.496145] LR is at notifier_call_chain+0x58/0x94
[9.496152] pc : [<18e64938>]lr : []psr: 20070033
[9.496157] sp : ed0f19e0  ip : c0db550c  fp : ed0f1a04
[9.496163] r10: ee6b5b78  r9 : c0fe02d8  r8 : 
[9.496169] r7 :   r6 : ed0f1a64  r5 : 0004009c  r4 : 
[9.496175] r3 : 18e64939  r2 : ed0f1a64  r1 :   r0 : c0db550c
[9.496183] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment 
none
[9.496190] Control: 10c5387d  Table: 6d0f406a  DAC: 0051
[9.496199] Process systemd-udevd (pid: 297, stack limit = 0xef505769)
[9.496205] Stack: (0xed0f19e0 to 0xed0f2000)
[9.496217] 19e0:  c0fe02e0 ed0f1a64 ee6b5b00 c0fe0280 c0fe02d8 
ed0f1a2c ed0f1a08
[9.496228] 1a00: c0176eb4 c01764f0  c0fe04b0 ed0f1a2c ed0f1a64 
c1058588 
[9.496238] 1a20: ed0f1a5c ed0f1a30 c06f5838 c0176e6c ed0f1a5c ed0f1a40 
c06f37cc ee6b5b00
[9.496248] 1a40: c0f05dcc c0fe04b0 c1058588 c0fe0280 ed0f1b84 ed0f1a60 
c06f5eb8 c06f57c0
[9.496258] 1a60:  000f 000f 000f   
ed14d100 0013d620
[9.496268] 1a80: 00030d40 00025990 00030d40 0013d620 000c3500  
 
[9.496280] 1aa0:  c0fe04b0     
 ffe0
[9.496290] 1ac0: ee6b5b5c ee6b5b5c c06f5be0 00030d40 0013d620 ed14a300 
0001 c0fe02d8
[9.496300] 1ae0: c0fe02d8 ed14de80 ee6b5b84 ee6b5b84 ee34b0c0  
c0fe0310 ed14c120
[9.496310] 1b00: 0001 0003   ee6b5bac ee6b5bac 
0001 ee6b5bb8
[9.496320] 1b20: ee6b5bb8   cfccda00   
0001 
[9.496329] 1b40:     ee6b5bec ee6b5bec 
 ed14d400
[9.496339] 1b60: ed14d2c0 17d3bda1  ee6b5b00  c0fe02d8 
ed0f1bcc ed0f1b88
[9.496349] 1b80: c06f6498 c06f5e3c  c0f05dcc   
ee6b5bb4 60070013
[9.496359] 1ba0: c039841c  c0fd216c c0f05dcc ee28a300 ee28a338 
c0fe02c8 ee28a338
[9.496370] 1bc0: ed0f1bec ed0f1bd0 c06f66b4 c06f5f24 c05fa3a4 c088c258 
c0fe02c0 c0fe02c0
[9.496379] 1be0: ed0f1c2c ed0f1bf0 c05fb22c c06f6638 ee28a358 ee458734 
 17d3bda1
[9.496391] 1c00: c08a08c4 bf3f303c c1058588 ee6ea000 c0fe0280 bf3f30c0 
 0033
[9.496401] 1c20: ed0f1c54 ed0f1c30 c06f433c c05fb170 ed0f1c54 ed0f1c40 
 eed69018
[9.496412] 1c40: ee6ea000 fdfb ed0f1c74 ed0f1c58 bf3f1638 c06f41c4 
ee6ea010 ffed
[9.496423] 1c60: bf3f30c0 fdfb ed0f1c94 ed0f1c78 c05fec08 bf3f15b0 
ee6ea010 c10572f8
[9.496433] 1c80: c10572fc  ed0f1ccc ed0f1c98 c05fc7c0 c05febb4 
c08a08c4 c01ce7b4
[9.496443] 1ca0: ee6ea044 ee6ea044 ee6ea010 bf3f30c0 c0f05dcc bf3f6000 
bf3f31c0 c0f05dcc
[9.496453] 1cc0: ed0f1cec ed0f1cd0 c05fca04 c05fc4b8  bf3f30c0 
c05fc934 c0f05dcc
[9.496465] 1ce0: ed0f1d1c ed0f1cf0 c05fa230 c05fc940 ee28a76c ee28a758 
ee78af34 17d3bda1
[9.496475] 1d00: bf3f30c0 c0fd20e0 cfdcbb80  ed0f1d2c ed0f1d20 
c05fbf10 c05fa1cc
[9.496485] 1d20: ed0f1d54 ed0f1d30 c05fb89c c05fbef0 bf3f23b0 ed0f1d40 
bf3f30c0 
[9.496495] 1d40: e000 ed14da00 ed0f1d6c ed0f1d58 c05fd76c c05fb6f0 
c0f05dcc 
[9.496506] 1d60: ed0f1d7c ed0f1d70 c05feb50 c05fd6f0 ed0f1d8c ed0f1d80 
bf3f6024 c05feb0c
[9.496515] 1d80: ed0f1e04 ed0f1d90 c0102108 bf3f600c c02bd1c4 c08a08c4 
 0001
[9.496526] 1da0: ed0f1dc4 ed0f1db0 c08a08c4 c01ce7b4 014000c0 c02fb0a4 
ed0f1e04 

Bug#895137: linux-image-4.15.0-2-armmp: Internal error: Oops: 80000005 [#1] SMP ARM on Odroid XU4

[Jochen Sprickerhof]

Complete dmesg output attached, sorry this got lost on the way.
[0.00] Booting Linux on physical CPU 0x100
[0.00] Linux version 4.15.0-2-armmp (debian-kernel@lists.debian.org) 
(gcc version 7.3.0 (Debian 7.3.0-11)) #1 SMP Debian 4.15.11-1 (2018-03-20)
[0.00] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[0.00] CPU: div instructions available: patching division code
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] OF: fdt: Machine model: Hardkernel Odroid XU4
[0.00] Memory policy: Data cache writealloc
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 16 MiB at 0xbd80
[0.00] Samsung CPU ID: 0xe5422001
[0.00] On node 0 totalpages: 518656
[0.00]   Normal zone: 1728 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 196608 pages, LIFO batch:31
[0.00]   HighMem zone: 322048 pages, LIFO batch:31
[0.00] Running under secure firmware.
[0.00] random: fast init done
[0.00] percpu: Embedded 17 pages/cpu @(ptrval) s38028 r8192 d23412 
u69632
[0.00] pcpu-alloc: s38028 r8192 d23412 u69632 alloc=17*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 516928
[0.00] Kernel command line:   console=ttySAC2,115200n8 
root=/dev/mmcblk0p1 console=ttySAC2,115200n8 rw rootwait
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Memory: 2005464K/2074624K available (8192K kernel code, 1088K 
rwdata, 2440K rodata, 2048K init, 324K bss, 52776K reserved, 16384K 
cma-reserved, 1271808K highmem)
[0.00] Virtual kernel memory layout:
   vector  : 0x - 0x1000   (   4 kB)
   fixmap  : 0xffc0 - 0xfff0   (3072 kB)
   vmalloc : 0xf080 - 0xff80   ( 240 MB)
   lowmem  : 0xc000 - 0xf000   ( 768 MB)
   pkmap   : 0xbfe0 - 0xc000   (   2 MB)
   modules : 0xbf00 - 0xbfe0   (  14 MB)
 .text : 0x(ptrval) - 0x(ptrval)   (9184 kB)
 .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)
 .data : 0x(ptrval) - 0x(ptrval)   (1089 kB)
  .bss : 0x(ptrval) - 0x(ptrval)   ( 325 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[0.00] ftrace: allocating 31088 entries in 92 pages
[0.00] Hierarchical RCU implementation.
[0.00] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[0.00] GIC: Using split EOI/Deactivate mode
[0.00] Switching to timer-based delay loop, resolution 41ns
[0.00] clocksource: mct-frc: mask: 0x max_cycles: 0x, 
max_idle_ns: 79635851949 ns
[0.07] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 
89478484971ns
[0.32] genirq: irq_chip COMBINER did not update eff. affinity mask of 
irq 49
[0.006339] Console: colour dummy device 80x30
[0.006390] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 48.00 BogoMIPS (lpj=96000)
[0.006410] pid_max: default: 32768 minimum: 301
[0.006659] Security Framework initialized
[0.006675] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.006783] AppArmor: AppArmor initialized
[0.006893] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.006917] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.007995] CPU: Testing write buffer coherency: ok
[0.008909] CPU0: thread -1, cpu 0, socket 1, mpidr 8100
[0.009591] Setting up static identity map for 0x4010 - 0x401000a0
[0.010234] ARM CCI driver probed
[0.010462] Exynos MCPM support installed
[0.012862] Hierarchical SRCU implementation.
[0.017453] EFI services will not be available.
[0.018083] smp: Bringing up secondary CPUs ...
[0.019149] CPU1: thread -1, cpu 1, socket 1, mpidr 8101
[0.020373] CPU2: thread -1, cpu 2, socket 1, mpidr 8102
[0.021531] CPU3: thread -1, cpu 3, socket 1, mpidr 8103
[0.022704] CPU4: thread -1, cpu 0, socket 0, mpidr 8000
[0.023923] CPU5: thread -1, cpu 1, socket 0, mpidr 8001
[0.025166] CPU6: thread -1, cpu 2, socket 0, mpidr 8002
[0.026359] CPU7: thread -1, cpu 3, socket 0, mpidr 8003
[0.026539] smp: Brought up 1 node, 8 CPUs
[0.026581] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[0.026591] CPU: WARNING: CPU(s) started in wrong/inconsistent modes 
(primary CPU mode 0x1a)
[0.026600] CPU: This may indicate a broken bootloader or firmware.
[0.028657] devtmpfs: initialized
[

Bug#895164: linux: Power management support for GPD Pocket UMPC systems

[Jeremy Stanley]

Package: linux
Version: 4.16~rc5-1~exp2
Severity: wishlist

Power management for GPD Pocket UMPC systems requires kernel driver
modules built by setting CONFIG_PWM_LPSS_PLATFORM,
CONFIG_INTEL_INT0002_VGPIO, CONFIG_INTEL_CHT_INT33FE,
CONFIG_TYPEC_FUSB302, CONFIG_BATTERY_MAX17042 and
CONFIG_CHARGER_BQ24190 along with a variety of related dependencies.
These are all supported in current mainline 4.16 release candidates,
they just need to be enabled.

Processed: Re: Bug#895164

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 895164 +patch
Bug #895164 [linux] linux: Power management support for GPD Pocket UMPC systems
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#895164: Acknowledgement (linux: Power management support for GPD Pocket UMPC systems)

[Jeremy Stanley]

Proposed https://salsa.debian.org/kernel-team/linux/merge_requests/4
for this.
-- 
Jeremy Stanley