Processed: Re: Bug#800343: debian-maintainers: chrome_laptop module stops working after hibernate

2015-09-28 Thread Debian Bug Tracking System
Processing control commands:

> reassign 800343 linux
Bug #800343 [debian-maintainers] debian-maintainers: chrome_laptop module stops 
working after hibernate
Bug reassigned from package 'debian-maintainers' to 'linux'.
Ignoring request to alter found versions of bug #800343 to the same values 
previously set
Ignoring request to alter fixed versions of bug #800343 to the same values 
previously set

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



Bug#800316: Removed package(s) from unstable

2015-09-28 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

cramfs |  1.1-6 | source
cramfsprogs |  1.1-6 | amd64, arm64, armel, armhf, i386, mips64el, powerpc, 
ppc64el, s390x
cramfsprogs |   1.1-6+b1 | mips, mipsel

--- Reason ---
ROM; obsoleted by squashfs and initramfs
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 800...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/800316

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)



Bug#799838: linux-image-3.16.0-4-amd64: NFS rename sometimes hangs for 15 seconds

2015-09-28 Thread Vincent Lefevre
According to Peter Ludikovsky in the debian-user list:


Am 25.09.2015 um 14:04 schrieb Vincent Lefevre:
> On 2015-09-25 10:11:10 +0200, Peter Ludikovsky wrote:
>> My guess is: Due to the rather large wsize/rsize, the clients
>> create a rather large attribute cache. As a result, when you cat
>> a file on the second machine it updates the atime in the cache,
>> but doesn't yet transfer that information to the server. When you
>> do the mv on the first machine, the client tries to get the
>> current attributes on the files involved, which prompts the
>> server to wait until the second client runs into some kind of
>> timeout and updates the attributes. Only then is the second file
>> "unlocked" to be overwritten.
>>
>> Further proof of that: when setting noatime as a mount option,
>> instead of noac, there's also no delay on the mv.
>
> Thanks for the explanations. But the second client, though it
> doesn't update the attributes immediately, seems to do it quickly
> when asked by the server, otherwise the problem would also be
> visible on Debian 7 machines. I think that on Debian 8, when the
> rename cannot be done immediately, the client retries after 15
> seconds instead of retrying earlier.
>
> Is this related to the following patch?
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8478eaa16e701ecfe054b62ec764bc1291b79e19

Can't say if it's related. I have, however, managed to capture the
related network traffic (see attachments).

The big difference happens at packets 58/54 (Deb7/Deb8). For Deb7, the
RENAME call is immediately answered by an NFS4_OK, whereas for Deb8 as
the client it's an NFS4ERR_DELAY. I haven't seen any reason on the
client communication that would explain that, however this is far
beyond my knowledge of the NFS internals.


See https://lists.debian.org/debian-user/2015/09/msg01120.html for his
message and the attachments.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#800316: Removed package(s) from unstable

2015-09-28 Thread Debian FTP Masters
Version: 1.1-6+rm

Dear submitter,

as the package cramfs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/800316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)



Bug#432155: marked as done (cramfsprogs: mkcramfs sometimes crashes (bus error in zlib))

2015-09-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Sep 2015 15:59:00 +
with message-id 
and subject line Bug#800316: Removed package(s) from unstable
has caused the Debian Bug report #432155,
regarding cramfsprogs: mkcramfs sometimes crashes (bus error in zlib)
to be marked as done.

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

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


-- 
432155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cramfsprogs
Version: 1.1-6
Severity: normal

mkcramfs sometimes crashes due to a bus error, but if I run the same
command again, it doesn't crash.

ay:~> gdb mkcramfs core
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld.so.1...
(no debugging symbols found)...done.
Loaded symbols for /lib/ld.so.1
Failed to read a valid object file image from memory.

Core was generated by `mkcramfs public_html public_html.cramfs.be'.
Program terminated with signal 7, Bus error.
#0  0x0ffccb3c in adler32 () from /usr/lib/libz.so.1
(gdb) bt
#0  0x0ffccb3c in adler32 () from /usr/lib/libz.so.1
#1  0x0ffd0c5c in ?? () from /usr/lib/libz.so.1
#2  0x0ffd1718 in ?? () from /usr/lib/libz.so.1
#3  0x0ffd1e84 in deflate () from /usr/lib/libz.so.1
#4  0x0ffcce24 in compress2 () from /usr/lib/libz.so.1
#5  0x10002e34 in ?? ()
#6  0x1000302c in ?? ()
#7  0x10003054 in ?? ()
#8  0x10003054 in ?? ()
#9  0x10003658 in ?? ()
#10 0x0fe70d60 in ?? () from /lib/libc.so.6
#11 0x0fe70fb8 in __libc_start_main () from /lib/libc.so.6
#12 0x in ?? ()
(gdb)

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (200, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.18-3-powerpc
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages cramfsprogs depends on:
ii  libc6 2.5-9  GNU C Library: Shared libraries
ii  zlib1g1:1.2.3-15 compression library - runtime

cramfsprogs recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.1-6+rm

Dear submitter,

as the package cramfs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/800316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#266327: marked as done (cramfs tools on big-endian architecture)

2015-09-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Sep 2015 15:59:00 +
with message-id 
and subject line Bug#800316: Removed package(s) from unstable
has caused the Debian Bug report #266327,
regarding cramfs tools on big-endian architecture
to be marked as done.

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

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


-- 
266327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cramfs
Version: 1.1-6
Severity: wishlist 


 The cramfstools cteares WRONG ENDIANITY filesystem
on the big-endian architectures (i.e. the mips-eb)

  David Schleef  wrote:
"According to Linus, big endian cramfs doesn't exist. "
http://lists.debian.org/debian-devel/2001/07/msg01161.html

 However, mkcramfs creates big-endin file imeges in the
big-endian hosts:

big-endian.host$ mkcramfs dir  image.cramfs

little-endian.host$ mkcramfs dir image.cramfs

 The "mkcramfs" produces DIFFERENT file images.

big-endian.host$ od -ha image.cramfs
000 cd28 453d 0010   0500  
  (   M   =   E dle nul nul nul nul nul nul enq nul nul nul nul
020 6f43 706d 6572 7373 6465 5220 4d4f 5346
  C   o   m   p   r   e   s   s   e   d  sp   R   O   M   F   S


little-endian.host$ od -ha image.cramfs
000 3d45 28cd 5000 0001 0003   
  E   =   M   ( nul   P soh nul etx nul nul nul nul nul nul nul
020 6f43 706d 6572 7373 6465 5220 4d4f 5346
  C   o   m   p   r   e   s   s   e   d  sp   R   O   M   F   S


 There are a lot of patches for the linux kernel :
http://www.ussg.iu.edu/hypermail/linux/kernel/0202.3/0365.html
Access to the constants reworked as :
...
#define CRAMFS_32(x) swab32(x) 
...
if (super.magic != CRAMFS_32(CRAMFS_MAGIC))

Another kernel patches (JFYI):
http://lists.infradead.org/pipermail/linux-mtd/2003-August/008471.html
http://www.linux-mips.org/archives/linux-mips/2001-09/msg00259.html


Is it possible to implement endianness-aware cramfs tools like:
http://seclists.org/linux-kernel/2001/Dec/0760.html




--- End Message ---
--- Begin Message ---
Version: 1.1-6+rm

Dear submitter,

as the package cramfs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/800316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#377565: marked as done (mkcramfs should not be in sbin)

2015-09-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Sep 2015 15:59:00 +
with message-id 
and subject line Bug#800316: Removed package(s) from unstable
has caused the Debian Bug report #377565,
regarding mkcramfs should not be in sbin
to be marked as done.

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

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


-- 
377565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cramfsprogs
Version: 1.1-6
Severity: normal
File: /usr/sbin/mkcramfs

mkcramfs is useful to non-sysadmins --- software developers, in
particular. It should probably really be in /usr/bin.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-amd64-k8-smp
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages cramfsprogs depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  zlib1g1:1.2.3-11 compression library - runtime

cramfsprogs recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.1-6+rm

Dear submitter,

as the package cramfs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/800316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#252745: marked as done (cramfsprogs: Extremely inefficient performance on large trees)

2015-09-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Sep 2015 15:59:00 +
with message-id 
and subject line Bug#800316: Removed package(s) from unstable
has caused the Debian Bug report #252745,
regarding cramfsprogs: Extremely inefficient performance on large trees
to be marked as done.

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

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


-- 
252745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cramfsprogs
Version: 1.1-5
Severity: normal

I have a tree with over 200,000 files that will be able to compress down
to a size that cramfs can handle.  These files will tend to have similar
sizes.

mkcramfs has been chugging on this for hours and has still not written a
single byte of output.

Looking at the source, it appears that it opens every input file of the
same size as every other input file of that size, and compares their
contents.

This is hideous.  If I wanted the files matched like that, I'd hardlink
them.

Not only that, but it could at least read all files once and store
md5sums for them or something.

Better yet, it should have a switch to disable this overagressive check.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.4
Locale: LANG=C, LC_CTYPE=en_US

Versions of packages cramfsprogs depends on:
ii  libc6   2.3.2.ds1-12 GNU C Library: Shared libraries an
ii  zlib1g  1:1.2.1.1-3  compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.1-6+rm

Dear submitter,

as the package cramfs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/800316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#800213: marked as done (cramfs: Please migrate a supported debhelper compat level)

2015-09-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Sep 2015 15:59:00 +
with message-id 
and subject line Bug#800316: Removed package(s) from unstable
has caused the Debian Bug report #800213,
regarding cramfs: Please migrate a supported debhelper compat level
to be marked as done.

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

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


-- 
800213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cramfs
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package cramfs is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 1.1-6+rm

Dear submitter,

as the package cramfs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/800316

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---


Bug#799250: linux-image-4.1.0-2-amd64: sporadic freezes overnight

2015-09-28 Thread Thorsten Glaser
Dixi quod…

> I’m trying now with linux-image-4.1.0-1-amd64:amd64 (= 4.1.3-1)

Linux tglase.lan.tarent.de 4.1.0-1-amd64 #1 SMP Debian 4.1.3-1 (2015-08-03) 
x86_64 GNU/Linux

The problem indeed does not appear to happen here (up 6 days).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg



Bug#800324: linux-image-4.2.0-1-amd64: Recurring traces from kernel/sched/core.c:1975 wake_up_process+0x31/0x50()

2015-09-28 Thread Ben Hutchings
On Mon, 2015-09-28 at 12:21 +0300, Roman Lebedev wrote:
> On Sun, Sep 27, 2015 at 11:57 PM, Ben Hutchings  wrote:
[...]
> > > snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_codec_hdmi
> > > crct10dif_pclmul crc32_pclmul eeepc_wmi ghash_clmulni_intel asus_wmi
> > > snd_hda_intel sha256_ssse3 sha256_generic ohci_pci sparse_keymap hmac
> > > rfkill video ohci_hcd drbg mxm_wmi ehci_pci ehci_hcd snd_hda_codec
> > > snd_hda_core ansi_cprng aesni_intel aes_x86_64 evdev xhci_pci lrw
> > > gf128mul glue_helper serio_raw xhci_hcd snd_hwdep ablk_helper usbcore
> > > snd_pcm cryptd snd_timer snd sp5100_tco pcspkr usb_common
> > > edac_mce_amd edac_core fam15h_power k10temp i2c_piix4 e1000e wmi
> > > soundcore acpi_cpufreq
> > > [39595.406818]  button ptp pps_core tpm_infineon shpchp sg processor
> > > tpm_tis tpm thermal_sys tcp_yeah tcp_vegas pcore(O) it87 hwmon_vid
> > 
> > [...]
> > 
> > What is pcore?
> That is a  AMD CodeXL Power Profiler Linux kernel module
> from http://developer.amd.com/tools-and-sdks/opencl-zone/codexl/
> -> amdcodexl_1.8-9654_amd64.deb

Can you try removing that?

Ben.

-- 
Ben Hutchings
All extremists should be taken out and shot.

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


Bug#800324: linux-image-4.2.0-1-amd64: Recurring traces from kernel/sched/core.c:1975 wake_up_process+0x31/0x50()

2015-09-28 Thread Roman Lebedev
On Mon, Sep 28, 2015 at 2:10 PM, Ben Hutchings  wrote:
> On Mon, 2015-09-28 at 12:21 +0300, Roman Lebedev wrote:
>> On Sun, Sep 27, 2015 at 11:57 PM, Ben Hutchings  wrote:
> [...]
>> > > snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_codec_hdmi
>> > > crct10dif_pclmul crc32_pclmul eeepc_wmi ghash_clmulni_intel asus_wmi
>> > > snd_hda_intel sha256_ssse3 sha256_generic ohci_pci sparse_keymap hmac
>> > > rfkill video ohci_hcd drbg mxm_wmi ehci_pci ehci_hcd snd_hda_codec
>> > > snd_hda_core ansi_cprng aesni_intel aes_x86_64 evdev xhci_pci lrw
>> > > gf128mul glue_helper serio_raw xhci_hcd snd_hwdep ablk_helper usbcore
>> > > snd_pcm cryptd snd_timer snd sp5100_tco pcspkr usb_common
>> > > edac_mce_amd edac_core fam15h_power k10temp i2c_piix4 e1000e wmi
>> > > soundcore acpi_cpufreq
>> > > [39595.406818]  button ptp pps_core tpm_infineon shpchp sg processor
>> > > tpm_tis tpm thermal_sys tcp_yeah tcp_vegas pcore(O) it87 hwmon_vid
>> >
>> > [...]
>> >
>> > What is pcore?
>> That is a  AMD CodeXL Power Profiler Linux kernel module
>> from http://developer.amd.com/tools-and-sdks/opencl-zone/codexl/
>> -> amdcodexl_1.8-9654_amd64.deb
>
> Can you try removing that?
Yes, already did, waiting...
Though, during that time when those traces occurred in dmesg,
i was not using amdcodexl, so pcore.ko shouldn't be the reason.

>
> Ben.
Roman.

>
> --
> Ben Hutchings
> All extremists should be taken out and shot.



Bug#800324: linux-image-4.2.0-1-amd64: Recurring traces from kernel/sched/core.c:1975 wake_up_process+0x31/0x50()

2015-09-28 Thread Roman Lebedev
On Sun, Sep 27, 2015 at 11:57 PM, Ben Hutchings  wrote:
> Control: tag -1 moreinfo
>
> On Sun, 2015-09-27 at 22:53 +0300, Roman Lebedev wrote:
>> Package: src:linux
>> Version: 4.2.1-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> This is a regression, i have not seen those traces on previous
>> kernels (4.1.0, 4.0.0, etc).
>>
>> [39595.406732] [ cut here ]
>> [39595.406744] WARNING: CPU: 2 PID: 9740 at /build/linux-18yw6z/linux
>> -4.2.1/kernel/sched/core.c:1975 wake_up_process+0x31/0x50()
>> [39595.406746] Modules linked in: binfmt_misc cpufreq_userspace
>> cpufreq_stats cpufreq_powersave cpufreq_conservative nfsd auth_rpcgss
>> oid_registry nfs_acl nfs lockd grace fscache sunrpc joydev nls_utf8
>> hid_generic nls_cp437 usbhid vfat fat hid kvm_amd fglrx(PO)
>
>
> Have you tried using radeon instead of fglrx?
On this particular hardware and on this machine - no.
Generally, i need OpenCL, (and not just-for-fun OpenGL, if possible), and
AFAIC radeon is not there yet.

>
>> snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_codec_hdmi
>> crct10dif_pclmul crc32_pclmul eeepc_wmi ghash_clmulni_intel asus_wmi
>> snd_hda_intel sha256_ssse3 sha256_generic ohci_pci sparse_keymap hmac
>> rfkill video ohci_hcd drbg mxm_wmi ehci_pci ehci_hcd snd_hda_codec
>> snd_hda_core ansi_cprng aesni_intel aes_x86_64 evdev xhci_pci lrw
>> gf128mul glue_helper serio_raw xhci_hcd snd_hwdep ablk_helper usbcore
>> snd_pcm cryptd snd_timer snd sp5100_tco pcspkr usb_common
>> edac_mce_amd edac_core fam15h_power k10temp i2c_piix4 e1000e wmi
>> soundcore acpi_cpufreq
>> [39595.406818]  button ptp pps_core tpm_infineon shpchp sg processor
>> tpm_tis tpm thermal_sys tcp_yeah tcp_vegas pcore(O) it87 hwmon_vid
>
> [...]
>
> What is pcore?
That is a  AMD CodeXL Power Profiler Linux kernel module
from http://developer.amd.com/tools-and-sdks/opencl-zone/codexl/
-> amdcodexl_1.8-9654_amd64.deb

>
> Ben.
Roman.

>
>
> --
> Ben Hutchings
> I say we take off; nuke the site from orbit.  It's the only way to be sure.



Bug#800154: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#800154: linux-source: custom built embedded kernel with slob-allocation runs too unstable, boot-problems)

2015-09-28 Thread Andreas Glaeser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

O> This is an automatic notification regarding your Bug report
> which was filed against the linux-source package:
> 
> #800154: linux-source: custom built embedded kernel with slob-allocation runs 
> too
> unstable, boot-problems
> 
> It has been closed by Ben Hutchings .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings
>  by replying to this email.
> 
> 
> -- 
> 800154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800154
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> 
> From: Ben Hutchings 
> To: 800154-d...@bugs.debian.org
> Subject: Re: Bug#800154: linux-source: custom built embedded kernel with
> slob-allocation runs too unstable, boot-problems Date: Sun, 27 Sep 2015 
> 18:27:46 +0100
> X-Mailer: Evolution 3.16.5-1 
> 
> Then don't use CONFIG_SLOB.  We're certainly not going to do anything
> to fix it.
> 
> Ben.
> 
> -- 
> Ben Hutchings
> I say we take off; nuke the site from orbit.  It's the only way to be sure.

Oh, well, 

I understand it's not Debian's problem, but my PC is an embedded system, so in 
principle

the embedded feature and SLOB should definitely work.

So should I take action myself in order to forward this upstream ??

Greetings

Andreas

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYJQEIACgkQ5+rBHyUt5wuU0QCgkiXaN75ku3X2D5xP8KuAf01Q
KAEAn09r0xq9C+N6g5+dLmsyfOL2RcNr
=uOiB
-END PGP SIGNATURE-


Bug#800154: closed by Ben Hutchings <b...@decadent.org.uk> (Re: Bug#800154: linux-source: custom built embedded kernel with slob-allocation runs too unstable, boot-problems)

2015-09-28 Thread Ben Hutchings
On Mon, 2015-09-28 at 15:27 +0200, Andreas Glaeser wrote:
> Oh, well, 
> 
> I understand it's not Debian's problem, but my PC is an embedded
> system, so in principle
> 
> the embedded feature and SLOB should definitely work.

So far as I know, SLOB is only suitable for really small systems,
probably not any PC and certainly not embedded systems in general.

> So should I take action myself in order to forward this upstream ??

Yes.

Ben.

-- 
Ben Hutchings
All extremists should be taken out and shot.


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