Processed: tagging 867634

2017-07-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 867634 - moreinfo Bug #867634 [src:linux] linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed messages - even after replacing most components. Bug #867636 [src:linux] linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed

Bug#867636: Bug#867634: linux-image-4.9.0-3-amd64: Repeated ESATA softreset failed messages - even after replacing most components.

2017-07-26 Thread Matthew Gillespie
eSATA cables were replaced, server has been replaced. On 07/20/2017 08:01 PM, Ben Hutchings wrote: Control: reopen -1 Control: tag -1 moreinfo [Retrying this with the other address given] On Fri, 2017-07-07 at 21:01 -0400, madsara wrote: [...] * What exactly did you do (or not do) that

Bug#844056: hard coded mac address

2017-07-26 Thread Joey Hess
My cubietruck needs this file for wifi to work. However, the MAC address hardcoded in the file is not used. -- see shy jo signature.asc Description: PGP signature

Processed: Re: Bug#869658: Debian 9.1 stretch: command 'sensors' freeze temporarily the whole system

2017-07-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #869658 [lm-sensors] Debian 9.1 stretch: command 'sensors' freeze temporarily the whole system Removed tag(s) moreinfo. > tag -1 + upstream Bug #869658 [lm-sensors] Debian 9.1 stretch: command 'sensors' freeze temporarily the whole system

Re: Bug#869658: Debian 9.1 stretch: command 'sensors' freeze temporarily the whole system

2017-07-26 Thread Aurelien Jarno
control: tag -1 - moreinfo control: tag -1 + upstream control: reassign -1 src:linux control: retitle -1 linux: system freezes when dell-smm-hwmon reads fan speed Hi, On 2017-07-26 10:34, Carmelo C wrote: > Hi Aurelien, > > I removed the code line "radeon.hw_i2c=1" but the freeze persists. Then

Bug#865866: libreoffice-writer crash on startup Debian 9 i386 arch

2017-07-26 Thread Hans
Hi Rene, maybe you should know, that libreoffice-writer ran fine since my last update, which was on 20th july 2017. I am running debian/testing, i386. And I do almost any day an upgrade. No kernel update! So, maybe it helps, when you see, which packages were updated. This is the list:

Bug#869824: missing package

2017-07-26 Thread Rudolf Polzer
Package: linux-headers-amd64 Version: 4.11.0-2-amd64 this package is missing

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, I don't owe the server. Just have a VM that was running flawless with Debian since Squeeze. And for the first time Debian became a sour option. I was going to compile another kernel when I found also kernel-package isn't released because of unwatched issues. Best Regards, Helio

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
On Wed, 2017-07-26 at 19:23 +0200, Helio Loureiro wrote: > Hi, > > I already sent. Please provide a full serial log when booting with the bad kernel. Also please let us know what version of Xen you are running and whether this was running as a guest or as dom0. > And in the first post in this

Bug#852324: linux-image-3.16.0-4-amd64: Info from `reportbug kernel` but probably useless.

2017-07-26 Thread Helio Loureiro
Package: src:linux Followup-For: Bug #852324 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Relesed Stretch kernel doesn't boot, crashing the system. * What exactly did you do (or not do) that was

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, I already sent. And in the first post in this bug it says: " When I boot my system with Xen, I get the following section in dmesg: [ 13.588381] [ cut here ] [ 13.588386] WARNING: CPU: 18 PID: 1 at

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
On Wed, 2017-07-26 at 18:51 +0200, Helio Loureiro wrote: > Hi, > > It can't be.  It is the same bug as describe in this one. > > If you read the first post, it can't boot and shows the same content > as in the bug I detected now on my system. Nowhere there does it say anything about failing to

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, It can't be. It is the same bug as describe in this one. If you read the first post, it can't boot and shows the same content as in the bug I detected now on my system. So it isn't a new bug. It was introduced since kernel 4.4 became available on upstream and not handled. Best Regards,

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, And `reportbug kernel` won't work cause it requires the system or kernel to be up and running. It isn't the case. This bug is leading the system to an outage on boot. Best Regards, Helio Loureiro http://helio.loureiro.eng.br https://se.linkedin.com/in/helioloureiro

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
This option does not (per its intent) present booting, it is just a check & warning. There may be a bug with the check which is causing a failure to boot, but you are the first to report that aspect and that isn't what #852324 was about until now. Please use `reportbug kernel` to report a fresh

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, VM doesn't boot with this parameter enabled, as confirmed by Linus mail. So my upgraded to Stretch leaded to a complete system outage because of this parameter. I held on kernel 3.19 from Jessie meanwhile. Best Regards, Helio Loureiro http://helio.loureiro.eng.br

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ian Campbell
On Wed, 2017-07-26 at 17:13 +0200, Helio Loureiro wrote: > Hi, > > As much it sounds correct to protect systems in this way, you broke > compatibility.  I'm back to kernel 3.19 until this is fixed. > > So in order to have such parameter enabled, you should at the least > provide a bootparam

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ben Hutchings
On Wed, 2017-07-26 at 17:13 +0200, Helio Loureiro wrote: > Hi, > > As much it sounds correct to protect systems in this way, you broke > compatibility.  I'm back to kernel 3.19 until this is fixed. > > So in order to have such parameter enabled, you should at the least provide > a bootparam

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Helio Loureiro
Hi, As much it sounds correct to protect systems in this way, you broke compatibility. I'm back to kernel 3.19 until this is fixed. So in order to have such parameter enabled, you should at the least provide a bootparam option to toggle enabled or not. >From my point of view as user, you

Processed: reassign 869670 to src:linux, forcibly merging 869511 869670

2017-07-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 869670 src:linux Bug #869670 [linux-headers-4.11.0-2-amd64] Depends: linux-headers-4.11.0-2-common ... but it is not going to be installed Bug reassigned from package 'linux-headers-4.11.0-2-amd64' to 'src:linux'. No longer marked as

Bug#869613: libreoffice write crashes (Debian 9)

2017-07-26 Thread Ben Hutchings
On Tue, 2017-07-25 at 07:33 -0400, Aaron Valdes wrote: > Thanks Rene, > > I installed Debian 9 AMD64 on my Asus Laptop the other > day.  libreoffice writer (lowriter) did not crash on that system. That's because this problem is specific to the Java implementation on i386. Ben. -- Ben

Re: CONFIG_CGROUPS_BPF in kernel 4.9

2017-07-26 Thread Ben Hutchings
On Tue, 2017-07-25 at 16:02 +, joe.gha...@dell.com wrote: > Hi Ben, > Would you please share your thoughts on the possibility of back- > porting support for CGROUPS_BPF and related code from kernel 4.10 to > kernel 4.9 for Debian Stretch? Feature backports (other than hardware enablement)

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

2017-07-26 Thread Ben Hutchings
On Mon, 2017-07-24 at 20:18 +0200, Helio Loureiro wrote: > Hi, > > First an errata: I don't see messages since March, not January as I stated > wrongly before. > > And I tracked similar messages on other distros and found a message from > Linus himself about a way to avoid such error: > >

Processed: Re: Bug#869649: Debian 9 i386 - Libreoffice write crash

2017-07-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 869649 src:linux Bug #869649 [libreoffice-gnome] Debian 9 i386 - Libreoffice write crash Bug reassigned from package 'libreoffice-gnome' to 'src:linux'. No longer marked as found in versions libreoffice/1:5.2.7-1. Ignoring request to