Bug#840128: linux-perf-4.7: dependency module installation issue

[Raphaël Halimi]

Le 09/10/2016 à 16:06, Thomas Koch a écrit :
>> Unfortunately, I don't currently have at my disposal one of those
>> newer ThinkPads that would be able to load the acpi-call module
> acpi_call is not ThinkPad specific by any means. It loads on every
> hardware.

Indeed, I never thought to try it, but it works.

Good to know, thanks.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#840128: linux-perf-4.7: dependency module installation issue

[Thomas Koch]

> Unfortunately, I don't currently have at my disposal one of those
> newer ThinkPads that would be able to load the acpi-call module
acpi_call is not ThinkPad specific by any means. It loads on every
hardware.

Regards, Thomas

Bug#840128: linux-perf-4.7: dependency module installation issue

[Raphaël Halimi]

Le 09/10/2016 à 09:05, shirish शिरीष a écrit :
> Btw how did you know that I have a newer thinkpad or anything of that
> sort. I looked up and didn't see anything which talks about the lappy
> being a thinkpad or it being an older or later.  Look forward for more
> details.

Educated guess. acpi-call and tp-smapi are mainly installed by ThinkPad
users, to set battery (dis)charge thresholds. tp-smapi is for older
models, acpi-call for newer ones.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#840128: linux-perf-4.7: dependency module installation issue

[shirish शिरीष]

at bottom :-

On 09/10/2016, shirish शिरीष  wrote:
> at bottom :-
>
> On 09/10/2016, Raphaël Halimi  wrote:
>> On Sat, 08 Oct 2016 22:32:00 +0100 Ben Hutchings 
>> wrote:
>>> Control: reassign -1 acpi-call-dkms 1.1.0-3
>>> Control: tag -1 moreinfo
>>
>> Indeed, I need more info on this one.
>>
>> I can't see what's wrong with my package, or the relation with
>> linux-perf, except that tlp (which I also maintain) recommends
>> linux-tools, which was replaced by linux-perf (I'll fix the dependency
>> for the next upload), and also suggests acpi-call-dkms.
>>
>> Unfortunately, I don't currently have at my disposal one of those newer
>> ThinkPads that would be able to load the acpi-call module. The ThinkPads
>> I currently own are older ones which still use the tp-smapi module to
>> set battery (dis)charge thresholds.
>>
>> Anyway, on my Sid box (which has acpi-call-dkms installed, but can't
>> load it, since it's not a ThinkPad), the module was correctly built and
>> installed by DKMS for Linux 4.7:
>>
>> raph@arche:~$ sudo dkms status
>> acpi-call, 1.1.0, 4.7.0-1-amd64, x86_64: installed
>>
>> Shirish, DKMS logs are available in /var/lib/dkms:
>>
>> raph@arche:~$ cat
>> /var/lib/dkms/acpi-call/1.1.0/4.7.0-1-amd64/x86_64/log/make.log
>> DKMS make.log for acpi-call-1.1.0 for kernel 4.7.0-1-amd64 (x86_64)
>> jeudi 1 septembre 2016, 03:35:05 (UTC+0200)
>> make : on entre dans le répertoire « /usr/src/linux-headers-4.7.0-1-amd64
>> »
>>   LD  /var/lib/dkms/acpi-call/1.1.0/build/built-in.o
>>   CC [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
>>   Building modules, stage 2.
>>   MODPOST 1 modules
>>   CC  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.mod.o
>>   LD [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.ko
>> make : on quitte le répertoire « /usr/src/linux-headers-4.7.0-1-amd64 »
>>
>> Unfortunately, I could only find the build log, which seems to have
>> worked on your machine, too.
>>
>> Could you please have a look at the contents of the /var/lib/dkms
>> directory and report if anything seems to have gone wrong ?
>>
>> Regards,
>>
>> --
>> Raphaël Halimi
>>
>>
>
>
> Dear Raphael,
>
> I also have tlp so maybe it is a dependency issue. Anyways, here's the
> log you requested, it is same as yours -
>
>  $ cat /var/lib/dkms/acpi-call/1.1.0/4.7.0-1-amd64/x86_64/log/make.log
> DKMS make.log for acpi-call-1.1.0 for kernel 4.7.0-1-amd64 (x86_64)
> Sat Oct  8 21:15:30 IST 2016
> make: Entering directory '/usr/src/linux-headers-4.7.0-1-amd64'
>   LD  /var/lib/dkms/acpi-call/1.1.0/build/built-in.o
>   CC [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.mod.o
>   LD [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.ko
> make: Leaving directory '/usr/src/linux-headers-4.7.0-1-amd64'
>
> --
>   Regards,
>   Shirish Agarwal  शिरीष अग्रवाल
>   My quotes in this email licensed under CC 3.0
> http://creativecommons.org/licenses/by-nc/3.0/
> http://flossexperiences.wordpress.com
> EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
>


Hi,

Btw how did you know that I have a newer thinkpad or anything of that
sort. I looked up and didn't see anything which talks about the lappy
being a thinkpad or it being an older or later.  Look forward for more
details.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#840128: linux-perf-4.7: dependency module installation issue

[shirish शिरीष]

at bottom :-

On 09/10/2016, Raphaël Halimi  wrote:
> On Sat, 08 Oct 2016 22:32:00 +0100 Ben Hutchings 
> wrote:
>> Control: reassign -1 acpi-call-dkms 1.1.0-3
>> Control: tag -1 moreinfo
>
> Indeed, I need more info on this one.
>
> I can't see what's wrong with my package, or the relation with
> linux-perf, except that tlp (which I also maintain) recommends
> linux-tools, which was replaced by linux-perf (I'll fix the dependency
> for the next upload), and also suggests acpi-call-dkms.
>
> Unfortunately, I don't currently have at my disposal one of those newer
> ThinkPads that would be able to load the acpi-call module. The ThinkPads
> I currently own are older ones which still use the tp-smapi module to
> set battery (dis)charge thresholds.
>
> Anyway, on my Sid box (which has acpi-call-dkms installed, but can't
> load it, since it's not a ThinkPad), the module was correctly built and
> installed by DKMS for Linux 4.7:
>
> raph@arche:~$ sudo dkms status
> acpi-call, 1.1.0, 4.7.0-1-amd64, x86_64: installed
>
> Shirish, DKMS logs are available in /var/lib/dkms:
>
> raph@arche:~$ cat
> /var/lib/dkms/acpi-call/1.1.0/4.7.0-1-amd64/x86_64/log/make.log
> DKMS make.log for acpi-call-1.1.0 for kernel 4.7.0-1-amd64 (x86_64)
> jeudi 1 septembre 2016, 03:35:05 (UTC+0200)
> make : on entre dans le répertoire « /usr/src/linux-headers-4.7.0-1-amd64 »
>   LD  /var/lib/dkms/acpi-call/1.1.0/build/built-in.o
>   CC [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.mod.o
>   LD [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.ko
> make : on quitte le répertoire « /usr/src/linux-headers-4.7.0-1-amd64 »
>
> Unfortunately, I could only find the build log, which seems to have
> worked on your machine, too.
>
> Could you please have a look at the contents of the /var/lib/dkms
> directory and report if anything seems to have gone wrong ?
>
> Regards,
>
> --
> Raphaël Halimi
>
>


Dear Raphael,

I also have tlp so maybe it is a dependency issue. Anyways, here's the
log you requested, it is same as yours -

 $ cat /var/lib/dkms/acpi-call/1.1.0/4.7.0-1-amd64/x86_64/log/make.log
DKMS make.log for acpi-call-1.1.0 for kernel 4.7.0-1-amd64 (x86_64)
Sat Oct  8 21:15:30 IST 2016
make: Entering directory '/usr/src/linux-headers-4.7.0-1-amd64'
  LD  /var/lib/dkms/acpi-call/1.1.0/build/built-in.o
  CC [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.mod.o
  LD [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.ko
make: Leaving directory '/usr/src/linux-headers-4.7.0-1-amd64'

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#840128: linux-perf-4.7: dependency module installation issue

[Raphaël Halimi]

On Sat, 08 Oct 2016 22:32:00 +0100 Ben Hutchings 
wrote:
> Control: reassign -1 acpi-call-dkms 1.1.0-3
> Control: tag -1 moreinfo

Indeed, I need more info on this one.

I can't see what's wrong with my package, or the relation with
linux-perf, except that tlp (which I also maintain) recommends
linux-tools, which was replaced by linux-perf (I'll fix the dependency
for the next upload), and also suggests acpi-call-dkms.

Unfortunately, I don't currently have at my disposal one of those newer
ThinkPads that would be able to load the acpi-call module. The ThinkPads
I currently own are older ones which still use the tp-smapi module to
set battery (dis)charge thresholds.

Anyway, on my Sid box (which has acpi-call-dkms installed, but can't
load it, since it's not a ThinkPad), the module was correctly built and
installed by DKMS for Linux 4.7:

raph@arche:~$ sudo dkms status
acpi-call, 1.1.0, 4.7.0-1-amd64, x86_64: installed

Shirish, DKMS logs are available in /var/lib/dkms:

raph@arche:~$ cat
/var/lib/dkms/acpi-call/1.1.0/4.7.0-1-amd64/x86_64/log/make.log
DKMS make.log for acpi-call-1.1.0 for kernel 4.7.0-1-amd64 (x86_64)
jeudi 1 septembre 2016, 03:35:05 (UTC+0200)
make : on entre dans le répertoire « /usr/src/linux-headers-4.7.0-1-amd64 »
  LD  /var/lib/dkms/acpi-call/1.1.0/build/built-in.o
  CC [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.mod.o
  LD [M]  /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.ko
make : on quitte le répertoire « /usr/src/linux-headers-4.7.0-1-amd64 »

Unfortunately, I could only find the build log, which seems to have
worked on your machine, too.

Could you please have a look at the contents of the /var/lib/dkms
directory and report if anything seems to have gone wrong ?

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#840128: linux-perf-4.7: dependency module installation issue

[Ben Hutchings]

Control: reassign -1 acpi-call-dkms 1.1.0-3
Control: tag -1 moreinfo

On Sun, 2016-10-09 at 02:19 +0530, shirish शिरीष wrote:
[...]
>  Although invoking dkms status got me this -
> 
> $ su -
> Password:
> root@think-debian:~# dkms status
> acpi-call, 1.1.0, 4.6.0-1-amd64, x86_64: installed
> acpi-call, 1.1.0, 4.7.0-1-amd64, x86_64: built
> nvidia-current, 367.44, 4.7.0-1-amd64, x86_64: installed
> open-vm-tools, 10.0.7, 4.7.0-1-amd64, x86_64: installed
> tp_smapi, 0.42, 4.7.0-1-amd64, x86_64: installed
> virtualbox, 5.1.6, 4.7.0-1-amd64, x86_64: installed
> virtualbox-guest, 5.1.6, 4.7.0-1-amd64, x86_64: installed
> 
> so guessing some issue in the acpi-call module perhaps or something ?
> 
> Please let me know how to give you the info. you need if it's not
> above.

Reassigning this accordingly.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug



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

Bug#840128: linux-perf-4.7: dependency module installation issue

[shirish शिरीष]

at bottom :-

On 09/10/2016, Ben Hutchings  wrote:
> Control: tag -1 moreinfo
>
> On Sat, 2016-10-08 at 21:24 +0530, shirish शिरीष wrote:
>> Package: linux-perf-4.7
>> Version: 4.7.5-1
>> Severity: normal
>>
>> Dear Maintainer,
>> I was installing/upgrading the kernel when I came across this -
>>
>> Setting up linux-headers-4.7.0-1-amd64 (4.7.5-1) ...
>> /etc/kernel/header_postinst.d/dkms:
>> Error! Problems with depmod detected.  Automatically uninstalling this
>> module.
>> DKMS: Install Failed (depmod problems).  Module rolled back to built
>> state.
> [...]
>
> This is strange but unrelated to linux-perf-4.7.
>
> Please send the dkms log so we can reassign this properly.
>
> Ben.
>
> --
> Ben Hutchings
> Every program is either trivial or else contains at least one bug
>
>


Dear Ben,

A cursory look at /var/log/ didn't show any dkms log. I did try
searching search-engines as well for the data but couldn't get
anything meaningful.

 Although invoking dkms status got me this -

$ su -
Password:
root@think-debian:~# dkms status
acpi-call, 1.1.0, 4.6.0-1-amd64, x86_64: installed
acpi-call, 1.1.0, 4.7.0-1-amd64, x86_64: built
nvidia-current, 367.44, 4.7.0-1-amd64, x86_64: installed
open-vm-tools, 10.0.7, 4.7.0-1-amd64, x86_64: installed
tp_smapi, 0.42, 4.7.0-1-amd64, x86_64: installed
virtualbox, 5.1.6, 4.7.0-1-amd64, x86_64: installed
virtualbox-guest, 5.1.6, 4.7.0-1-amd64, x86_64: installed

so guessing some issue in the acpi-call module perhaps or something ?

Please let me know how to give you the info. you need if it's not above.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#840128: linux-perf-4.7: dependency module installation issue

[Ben Hutchings]

Control: tag -1 moreinfo

On Sat, 2016-10-08 at 21:24 +0530, shirish शिरीष wrote:
> Package: linux-perf-4.7
> Version: 4.7.5-1
> Severity: normal
> 
> Dear Maintainer,
> I was installing/upgrading the kernel when I came across this -
> 
> Setting up linux-headers-4.7.0-1-amd64 (4.7.5-1) ...
> /etc/kernel/header_postinst.d/dkms:
> Error! Problems with depmod detected.  Automatically uninstalling this module.
> DKMS: Install Failed (depmod problems).  Module rolled back to built state.
[...]

This is strange but unrelated to linux-perf-4.7.

Please send the dkms log so we can reassign this properly.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug



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

Bug#840128: linux-perf-4.7: dependency module installation issue

[shirish शिरीष]

Package: linux-perf-4.7
Version: 4.7.5-1
Severity: normal

Dear Maintainer,
I was installing/upgrading the kernel when I came across this -

Setting up linux-headers-4.7.0-1-amd64 (4.7.5-1) ...
/etc/kernel/header_postinst.d/dkms:
Error! Problems with depmod detected.  Automatically uninstalling this module.
DKMS: Install Failed (depmod problems).  Module rolled back to built state.

The following NEW packages will be installed:
linux-headers-4.7.0-1-amd64{a} linux-headers-4.7.0-1-common{a}
linux-kbuild-4.7{a} linux-perf-4.7{a}
The following packages will be REMOVED:
  linux-perf-4.6{u}

As can be seen I am running kernel 4.7. I dunno why it didn't get
installed when the kernel was updated.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages linux-perf-4.7 depends on:
ii  libaudit1 1:2.6.5-1
ii  libc6 2.24-3
ii  libc6-i3862.24-3
ii  libc6-x32 2.24-3
ii  libdw10.166-2
ii  libelf1   0.166-2
ii  libnuma1  2.0.11-1
ii  libperl5.24   5.24.1~rc3-3
ii  libpython2.7  2.7.12-3
ii  libslang2 2.3.0-3
ii  libssl1.0.2   1.0.2h-1
ii  libunwind81.1-4.1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages linux-perf-4.7 recommends:
ii  linux-base  4.5

Versions of packages linux-perf-4.7 suggests:
pn  linux-doc-4.7  

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8