Processed: tagging 867634

[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 messages - even after replacing most components.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

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

[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 was effective (or
  ineffective)?
The following actions have been taken so far, none of which are 
successful:
- Upgraded Dell R210 II's BIOS
- Purchased an entirely new Sandisk TowerRAID TR8M+B
- Replaced the eSATA card - moving from SIL chipset to Marvell
- Replaced all hard drives with brand new 3TB drives.

Did you try replacing the eSATA cables yet?


- Upgraded OS from Debian Jessie to Debian Stretch
- Ensured BIOS was set for maximum performance and not power saving.
- Added noapic, acpi=off, and apm=off kernel parameter options.

These parameters were once useful with old hardware and kernel
versions, but now will usually only make things worse.


- Performed a full on-board health check (part of the Dell on-board 
management abilities), finding no issues.
- Performed an extensive memory test, finding no issues.

[...]

Ben.

Bug#844056: hard coded mac address

[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

[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
Added tag(s) upstream.
> reassign -1 src:linux
Bug #869658 [lm-sensors] Debian 9.1 stretch: command 'sensors' freeze 
temporarily the whole system
Bug reassigned from package 'lm-sensors' to 'src:linux'.
No longer marked as found in versions lm-sensors/1:3.4.0-4.
Ignoring request to alter fixed versions of bug #869658 to the same values 
previously set
> retitle -1 linux: system freezes when dell-smm-hwmon reads fan speed
Bug #869658 [src:linux] Debian 9.1 stretch: command 'sensors' freeze 
temporarily the whole system
Changed Bug title to 'linux: system freezes when dell-smm-hwmon reads fan 
speed' from 'Debian 9.1 stretch: command 'sensors' freeze temporarily the whole 
system'.

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

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

[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 I
> ran "strace -o strace_sensors_output -tt sensors", attached the output...

Indeed, the strace shows that the freeze is not related to the radeon
module, but rather to the dell-smm-hwmon module. You can try to unload
it, the issue should then disappear.

[ snip ]

> 10:18:08.029849 write(1, "dell_smm-virtual-0\n", 19) = 19
> 10:18:08.029908 write(1, "Adapter: Virtual device\n", 24) = 24

[ snip ]

> 10:18:08.049666 open("/sys/class/hwmon/hwmon2/fan1_label", O_RDONLY) = 3
> 10:18:08.049718 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:08.049759 read(3, "Processor Fan\n", 4096) = 14
> 10:18:08.049801 read(3, "", 4096)   = 0
> 10:18:08.049838 close(3)= 0
> 10:18:08.049882 open("/sys/class/hwmon/hwmon2/fan1_input", O_RDONLY) = 3
> 10:18:08.049937 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:08.049978 read(3, "2844\n", 4096) = 5
> 10:18:09.956833 close(3)= 0
> 10:18:09.956891 write(1, "Processor Fan: 2844 RPM\n", 24) = 24

Here you can see that reading the fan speed almost take 2 seconds.

> 10:18:09.956950 open("/sys/class/hwmon/hwmon2/fan2_label", O_RDONLY) = 3
> 10:18:09.957009 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:09.957052 read(3, 0xbfdec67c, 4096) = -1 EINVAL (Invalid argument)
> 10:18:09.957093 close(3)= 0
> 10:18:09.957138 open("/sys/class/hwmon/hwmon2/fan2_input", O_RDONLY) = 3
> 10:18:09.957191 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:09.957250 read(3, "2844\n", 4096) = 5
> 10:18:11.860890 close(3)= 0
> 10:18:11.860939 write(1, "fan2:  2844 RPM\n", 24) = 24

Same here.

> 10:18:11.860990 open("/sys/class/hwmon/hwmon2/fan3_label", O_RDONLY) = 3
> 10:18:11.861046 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:11.861088 read(3, 0xbfdec67c, 4096) = -1 EINVAL (Invalid argument)
> 10:18:11.861128 close(3)= 0
> 10:18:11.861172 open("/sys/class/hwmon/hwmon2/fan3_input", O_RDONLY) = 3
> 10:18:11.861237 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:11.861278 read(3, "2840\n", 4096) = 5
> 10:18:13.779559 close(3)= 0
> 10:18:13.779666 write(1, "fan3:  2840 RPM\n", 24) = 24

Same here.

> 10:18:13.779738 open("/sys/class/hwmon/hwmon2/temp1_label", O_RDONLY) = 3
> 10:18:13.779947 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:13.780021 read(3, "CPU\n", 4096)  = 4
> 10:18:13.789029 read(3, "", 4096)   = 0
> 10:18:13.789087 close(3)= 0
> 10:18:13.789148 open("/sys/class/hwmon/hwmon2/temp1_input", O_RDONLY) = 3
> 10:18:13.789228 fstat64(3, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
> 10:18:13.789280 read(3, "37000\n", 4096) = 6
> 10:18:13.799076 close(3)= 0

While reading a temperature is done in less than 1 millisecond.


The problem you observe is similar to the following one:
  
  https://bugzilla.kernel.org/show_bug.cgi?id=112021

As it the root of the problem is a BIOS issue, I would first suggest to
upgrade it. If it doesn't work the next step is probably to use the 
blacklist implemented in the dell-smm-hwmon module to disable the fans
when running on a Dell system similar to yours.

In anycase this is definitely a kernel related issue, so I am
reassigning the bug.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

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

[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:
Install: firebird3.0-server-core:i386 (3.0.2.32703.ds4-4, automatic), 
libgltf-0.1-1:i386 
(0.1.0-2, automatic), libzmf-0.0-0:i386 (0.0.1-4, auto

After this update, libreoffice won't start any more. As someone pointed me to 
java, I 
downgraded openjdk with no success. 

Maybe this might help to look, what might have changed.

Best regards

Hans

Bug#869824: missing package

[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.

[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.

[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 it says:
> 
> "
> When I boot my system with Xen, I get the following section in 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.588392] CPU: 18 PID: 1 Comm: swapper/0 Not tainted 4.8.0-2-amd64 #1 
> Debian 4.8.15-2
> [...]
> But when I boot my system 'normally', ie without Xen, the error does
> not
> show up."
> He clearly states it isn't booting.  It is crashing.

The original bug report was running the same kernel as the splat at the
point where reportbug was run, so it is booting at least far enough to
do that. See the "Kernel: Linux 4.8.0-2-amd64" in the original report,
which is also in the warning message.

There is no suggestion anywhere that it isn't booting in the original
report, just that when it does boot this message appears in the logs.
All he says is that this warning (he says "error", but that doesn't
imply a boot failure either) doesn't appear with the normal kernel.

See also the logs at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
852324#25 which show the system continuing to successfully boot after
the splat.

> How could that not be related?

Because you are experiencing some other bug later on, or perhaps the
check which resulting in a WARNING for the original poster has a bug in
it which is causing a hang for you, please provide us with the
information we need in order to diagnose which it is rather than
continuing to assert that it is the same issue, otherwise no progress
is going to happen here.

Ian.

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

[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 effective (or
 ineffective)?
 Rollbacked to kernel from Jessie.
   * What was the outcome of this action?
 System is back online but this bug report is probably useless.
   * What outcome did you expect instead?
 To be fixed since this bug was reported in January and no actions were
taken.

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26)

** Command line:
root=/dev/xvda1

** Not tainted

** Kernel log:

** Model information
not available

** Loaded modules:
dm_mod
nfnetlink_log
nfnetlink
binfmt_misc
ip6t_REJECT
xt_hl
ip6t_rt
nf_conntrack_ipv6
nf_defrag_ipv6
ipt_REJECT
xt_comment
xt_LOG
xt_limit
xt_tcpudp
xt_addrtype
thermal_sys
coretemp
crct10dif_pclmul
crct10dif_common
crc32_pclmul
nf_conntrack_ipv4
nf_defrag_ipv4
crc32c_intel
xt_conntrack
aesni_intel
evdev
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
xen_netfront
pcspkr
cryptd
ip6table_filter
ip6_tables
nf_conntrack_netbios_ns
nf_conntrack_broadcast
nf_nat_ftp
nf_nat
nf_conntrack_ftp
nf_conntrack
iptable_filter
loop
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
xen_blkfront

** PCI devices:

** USB devices:
not available


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-3.16.0-4-amd64 depends on:
ii  debconf [debconf-2.0]   1.5.61
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-3.16.0-4-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-3.16.0-4-amd64 suggests:
pn  debian-kernel-handbook 
pn  grub-pc | grub-efi | extlinux  
pn  linux-doc-3.16 

Versions of packages linux-image-3.16.0-4-amd64 is related to:
pn  firmware-atheros
pn  firmware-bnx2   
pn  firmware-bnx2x  
pn  firmware-brcm80211  
pn  firmware-intelwimax 
pn  firmware-ipw2x00
pn  firmware-ivtv   
pn  firmware-iwlwifi
pn  firmware-libertas   
pn  firmware-linux  
pn  firmware-linux-nonfree  
pn  firmware-myricom
pn  firmware-netxen 
pn  firmware-qlogic 
pn  firmware-ralink 
pn  firmware-realtek
pn  xen-hypervisor  

-- debconf information:
  linux-image-3.16.0-4-amd64/postinst/mips-initrd-3.16.0-4-amd64:
  linux-image-3.16.0-4-amd64/prerm/removing-running-kernel-3.16.0-4-amd64:
true
  linux-image-3.16.0-4-amd64/postinst/depmod-error-initrd-3.16.0-4-amd64:
false

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

[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
/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.588388] Modules linked in:
[   13.588392] CPU: 18 PID: 1 Comm: swapper/0 Not tainted
4.8.0-2-amd64 #1 Debian 4.8.15-2
[   13.588392] Hardware name: ASUSTeK COMPUTER INC. Z10PA-D8
Series/Z10PA-D8 Series, BIOS 3202 04/18/2016
[   13.588394]  0200 043f1514 8131f925
8802806b3de0
[   13.588397]   81074ffe 8802806b3ed0
8802806b3e38
[   13.588399]  0004  8802806b3ed0

[   13.588401] Call Trace:
[   13.588406]  [] ? dump_stack+0x5c/0x77
[   13.588409]  [] ? __warn+0xbe/0xe0
[   13.588412]  [] ? warn_slowpath_fmt+0x5f/0x80
[   13.588415]  [] ? vprintk_emit+0x349/0x530
[   13.588417]  [] ? note_page+0x5e8/0x790
[   13.588419]  [] ? ptdump_walk_pgd_level_core+0x2d5/0x400
[   13.588423]  [] ? kernel_init+0x26/0x100
[   13.588425]  [] ? ret_from_fork+0x1f/0x40
[   13.588427]  [] ? rest_init+0x80/0x80
[   13.588428] ---[ end trace 98efce8be234f5b3 ]---
[   13.608867] x86/mm: Checked W+X mappings: FAILED, 4602 W+X pages found.

But when I boot my system 'normally', ie without Xen, the error does not
show up."

He clearly states it isn't booting.  It is crashing.

How could that not be related?

Abs,
Helio Loureiro
http://helio.loureiro.eng.br
https://se.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro

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

[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 boot.

Please boot a working kernel and use reportbug to file a new bug,
describing your configuration (e.g. version of Xen etc) and please then
attach your serial logs of the issue occurring.

> So it isn't a new bug.

Yes, it is.

Ian.

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

[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,
Helio Loureiro
http://helio.loureiro.eng.br
https://se.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro

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

[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
http://twitter.com/helioloureiro

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

[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 describing your
specific circumstances and your failure mode.

Ian.

On Wed, 2017-07-26 at 18:32 +0200, Helio Loureiro wrote:
> 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
> https://se.linkedin.com/in/helioloureiro
> http://twitter.com/helioloureiro
> 
> 
> 2017-07-26 17:56 GMT+02:00 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 option to toggle enabled or not.
> > >
> > > From my point of view as user, you should never break backward
> > > compatibility, as bad is sounds in terms of security.  And you
> > should
> > > never enforce it to users.
> > 
> > Other than a single warning printed to dmesg during boot, what is
> > actually broken for you?
> > 
> > Ian.
> > 
> 
> 

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

[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
https://se.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro


2017-07-26 17:56 GMT+02:00 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 option to toggle enabled or not.
> >
> > From my point of view as user, you should never break backward
> > compatibility, as bad is sounds in terms of security.  And you should
> > never enforce it to users.
>
> Other than a single warning printed to dmesg during boot, what is
> actually broken for you?
>
> Ian.
>

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

[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 option to toggle enabled or not.
> 
> From my point of view as user, you should never break backward
> compatibility, as bad is sounds in terms of security.  And you should
> never enforce it to users.

Other than a single warning printed to dmesg during boot, what is
actually broken for you?

Ian.

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

[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 option to toggle enabled or not.
> 
> From my point of view as user, you should never break backward
> compatibility, as bad is sounds in terms of security.  And you should never
> enforce it to users.

Whatever compatibility problem you're talking about, I don't believe
it's related to CONFIG_DEBUG_WX.  That only enables a warning at boot.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.



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

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

[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 should never break backward
compatibility, as bad is sounds in terms of security.  And you should never
enforce it to users.

Best Regards,
Helio Loureiro
http://helio.loureiro.eng.br
https://se.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro


2017-07-26 16:20 GMT+02:00 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:
> >
> > https://lkml.org/lkml/2015/12/14/670
> >
> > Checking standard Debian kernel settings, I can see it is indeed enabled.
> >
> > # grep CONFIG_DEBUG_WX /boot/config-4.9.0-3-amd64
> > CONFIG_DEBUG_WX=y
> >
> > So is possible to delivery a correction kernel package with such
> parameter
> > disabled?
>
> This check catches a real security weakness in Xen.  We won't disable
> checking for it.  Note that I did downgrade the severity of the warning
> when running on Xen, since we know about it and don't expect it to be
> fixed soon.
>
> Ben.
>
> --
> Ben Hutchings
> Reality is just a crutch for people who can't handle science fiction.
>
>

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

[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 found in versions linux/4.11.11-1.
Ignoring request to alter fixed versions of bug #869670 to the same values 
previously set
> forcemerge 869511 869670
Bug #869511 [src:linux] linux: binNMU-unsafe dependency on 
linux-headers-*-common
Bug #869670 [src:linux] Depends: linux-headers-4.11.0-2-common ... but it is 
not going to be installed
Severity set to 'grave' from 'normal'
866389 was blocked by: 869357 826505 826473 869602 867213 867210 867514 869580 
866978 869433 869578 809352 869583 865893 865020 865380 865898 865224 866934 
866944 867984 826471 865045 869579 865888 826489 827640 869139 826502 867046 
865034 869436 869511 869576 866317 869504 865033 866315 865482 869383 826497 
865477 869418
866389 was not blocking any bugs.
Added blocking bug(s) of 866389: 869670
865614 was blocked by: 867257 869511
865614 was not blocking any bugs.
Added blocking bug(s) of 865614: 869670
Marked as found in versions linux/4.11.11-1.
Added tag(s) pending.
Merged 869511 869670
> thanks
Stopping processing here.

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

Bug#869613: libreoffice write crashes (Debian 9)

[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 Hutchings
Reality is just a crutch for people who can't handle science fiction.



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

Re: CONFIG_CGROUPS_BPF in kernel 4.9

[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) generally aren't
suitable for stable updates.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.



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

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

[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:
> 
> https://lkml.org/lkml/2015/12/14/670
> 
> Checking standard Debian kernel settings, I can see it is indeed enabled.
> 
> # grep CONFIG_DEBUG_WX /boot/config-4.9.0-3-amd64
> CONFIG_DEBUG_WX=y
> 
> So is possible to delivery a correction kernel package with such parameter
> disabled?

This check catches a real security weakness in Xen.  We won't disable
checking for it.  Note that I did downgrade the severity of the warning
when running on Xen, since we know about it and don't expect it to be
fixed soon.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.



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

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

[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 alter fixed versions of bug #869649 to the same values 
previously set
> severity 869649 grave
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Severity set to 'grave' from 'normal'
> forcemerge 865303 869649
Bug #865303 [src:linux] libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Bug #869613 [src:linux] libreoffice write crashes (Debian 9)
Added tag(s) unreproducible and moreinfo.
Added tag(s) moreinfo and unreproducible.
Added tag(s) unreproducible and moreinfo.
Added tag(s) moreinfo and unreproducible.
Bug #865866 [src:linux] libreoffice-writer crash on startup Debian 9 i386 arch
Removed indication that 865866 affects libreoffice-base, libreoffice, 
security.debian.org, rustc, openjdk-8-jre, jsvc, and libreoffice-writer
Added indication that 865866 affects 
libreoffice,libreoffice-writer,libreoffice-base,rustc,security.debian.org,openjdk-8-jre,jsvc
Removed indication that 865303 affects rustc, libreoffice-writer, 
openjdk-8-jre, jsvc, libreoffice, libreoffice-base, and security.debian.org
Added indication that 865303 affects 
libreoffice,libreoffice-writer,libreoffice-base,rustc,security.debian.org,openjdk-8-jre,jsvc
Removed indication that 869161 affects jsvc, openjdk-8-jre, libreoffice-writer, 
rustc, security.debian.org, libreoffice, and libreoffice-base
Added indication that 869161 affects 
libreoffice,libreoffice-writer,libreoffice-base,rustc,security.debian.org,openjdk-8-jre,jsvc
Removed indication that 869613 affects libreoffice-writer, openjdk-8-jre, jsvc, 
rustc, security.debian.org, libreoffice-base, and libreoffice
Added indication that 869613 affects 
libreoffice,libreoffice-writer,libreoffice-base,rustc,security.debian.org,openjdk-8-jre,jsvc
Bug #869649 [src:linux] Debian 9 i386 - Libreoffice write crash
Added indication that 869649 affects 
libreoffice,libreoffice-writer,libreoffice-base,rustc,security.debian.org,openjdk-8-jre,jsvc
The source linux and version 3.2.89-1 do not appear to match any binary packages
Marked as found in versions linux/3.16.43-2+deb8u1, linux/3.2.89-1, 
linux/4.11.6-1, linux/4.9.30-2+deb9u1, and linux/4.9.30-2+deb9u2.
Added tag(s) upstream and confirmed.
Bug #869161 [src:linux] libreoffice-base crashes with code 139 when creating a 
new base or opening an existing one
Merged 865303 865866 869161 869613 869649
> thanks
Stopping processing here.

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