Processed: [bts-link] source package src:linux

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #775615 (http://bugs.debian.org/775615)
> # Bug title: i915: GPU HANG: ecode -1:0x, reason: Kicking stuck 
> semaphore on render ring, action: continue
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=54226
> #  * remote status changed: ASSIGNED -> CLOSED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 775615 + fixed-upstream
Bug #775615 [src:linux] i915: GPU HANG: ecode -1:0x, reason: Kicking 
stuck semaphore on render ring, action: continue
Added tag(s) fixed-upstream.
> usertags 775615 - status-ASSIGNED
Usertags were: status-ASSIGNED.
Usertags are now: .
> usertags 775615 + status-CLOSED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-CLOSED.
> # remote status report for #846492 (http://bugs.debian.org/846492)
> # Bug title: vblank wait timed out on crtc error from linux-image-4.8.0-1
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=93782
> #  * remote status changed: NEEDINFO -> REOPENED
> usertags 846492 - status-NEEDINFO
Usertags were: status-NEEDINFO.
Usertags are now: .
> usertags 846492 + status-REOPENED
There were no usertags set.
Usertags are now: status-REOPENED.
> thanks
Stopping processing here.

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

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

[Hans]

Hi,

just FYI: latest version of libreoffice in debian/testing is also still 
crashing.

Thought, you should be informed.

Best

Hans

Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

[Sven Hartge]

On 03.08.2017 15:34, Patrick Matthäi wrote:
> Am 16.07.2017 um 23:42 schrieb Ben Hutchings:
>> On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:

 Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?
>> Note that this has been root-caused as a bug in the virtual device, not
>> the driver.  (Though it would be nice if the driver could work around
>> it.)

> I can confirm, that the VMs do not crash anymore with vSphere 6.5 build
> 5969303 from 27.07.2017, that is why I lowered the severity.

This is the version from 6.5u1, right?

Still: Stretch is basically unusable with HW13 on ESX6.5 below Update1.

Grüße,
Sven.





signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

[Debian Bug Tracking System]

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

> severity #864642 normal
Bug #864642 [src:linux] vmxnet3: Reports suspect GRO implementation on vSphere 
hosts / one VM crashes
Severity set to 'normal' from 'important'
> thanks
Stopping processing here.

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

Bug#864642: vmxnet3: Reports suspect GRO implementation on vSphere hosts / one VM crashes

[Patrick Matthäi]

severity #864642 normal
thanks


Am 16.07.2017 um 23:42 schrieb Ben Hutchings:
> Control: tag -1 moreinfo
>
> Sven asked this, but forgot to add you to the recipients:
>
> On Thu, 2017-07-06 at 21:50 +0200, Sven Hartge wrote:
>> Hi!
>>
>>> Could this be https://bugzilla.kernel.org/show_bug.cgi?id=191201 ?
> Note that this has been root-caused as a bug in the virtual device, not
> the driver.  (Though it would be nice if the driver could work around
> it.)
>
> Ben.

I can confirm, that the VMs do not crash anymore with vSphere 6.5 build
5969303 from 27.07.2017, that is why I lowered the severity.

But we have got still the issue with "Driver has suspect GRO
implementation, TCP performance may be compromised" and the fact, that
4.9.18-1 wasn't crashing and has not this message, while 4.9.30-1 was
crashing with the message.

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/




signature.asc
Description: OpenPGP digital signature

Bug#867486: Issue with the audit subsystem

[Laurent Bigonville]

Le 03/08/17 à 07:46, Salvatore Bonaccorso a écrit :

Hi Laurent,


Hi,


Sorry for the lack of time and no reply to this.

On Fri, Jul 14, 2017 at 02:40:02PM +0200, Laurent Bigonville wrote:

Le 09/07/17 à 21:58, Salvatore Bonaccorso a écrit :

Hi

Hi,


Unconfirmed, but the behaviour you are seen might be related to the
changes which went in in 4.11 around
264d509637d95f9404e52ced5003ad352e0f6a26 .

https://git.kernel.org/linus/264d509637d95f9404e52ced5003ad352e0f6a26


I posted on the linux-audit mailing list and I get the following reply from
Paul Moore:


On Mon, Jul 10, 2017 at 10:59 AM, Laurent Bigonville  wrote:

Hi,

With 4.11.6 (that has been uploaded in debian unstable) I get a lot of
messages in dmesg like

[100052.120468] audit: audit_lost=66041 audit_rate_limit=0
audit_backlog_limit=8192
[100052.120470] audit: kauditd hold queue overflow

And it also seems that the messages are not stored in auditd logs anymore.

https://git.kernel.org/linus/264d509637d95f9404e52ced5003ad352e0f6a26  seems
to be included in this release

An idea?

I'm going to assume that your backlog limit is set to a sane value for
your system's configuration, so that leaves me with two commits that
may be of interest:

* 1df30f8264b8 ("audit: fix the RCU locking for the auditd_connection
structure")

This was a manual backport of a v4.12 patch to v4.11, looking now, I
see it should be in +v4.11.5 so that probably isn't your problem ...

* c81be52a3ac0 ("audit: fix a race condition with the auditd tracking code")

This patch is relatively new and was just sent up to Linus during the
next merge window; it's a race condition fix so reproducing it can be
tricky, although it may be easily reproducible on your system at the
moment (luck you!).  If you aren't in a position to apply the patch,
the workaround is rather simple: restart auditd.

If none of the above works, let me know, but I strongly suspect you're
tripping over the race condition fixed in that last patch.

I still should test the last patch he mentioned

Did you manage to test the last patch he mentioned? And does it
resolve the issue?


I didn't had the time to recompile the kernel with that patch included.

I can just confirm that it still happening with the kernel currently in 
experimental (4.12.2-1~exp1)

Bug#864714: task crm_node:13269 blocked for more than 120 seconds.

[Russell Mosemann]

Package: src:linux
Version: 4.9.30-2+deb9u2~bpo8+1
Severity: important

Dear Maintainer,

Aug 03 03:35:05 vhost082 lrmd[1336]: warning: p-vs1-2_stop_0 process (PID 
13403) timed out
Aug 03 03:35:05 vhost082 lrmd[1336]: warning: p-vs1-2_stop_0:13403 - timed out 
after 6ms
Aug 03 03:35:05 vhost082 crmd[1340]: error: Result of stop operation for 
p-vs1-2 on vhost082: Timed Out
Aug 03 03:35:47 vhost082 kernel: INFO: task crm_node:13269 blocked for more 
than 120 seconds.
Aug 03 03:35:47 vhost082 kernel:   Not tainted 4.9.0-0.bpo.3-amd64 #1 
Debian 4.9.30-2+deb9u2~bpo8+1
Aug 03 03:35:47 vhost082 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 03 03:35:47 vhost082 kernel: crm_nodeD0 13269  1 0x0004
Aug 03 03:35:47 vhost082 kernel:  990b8bc54800  
991bb856f000 990d8527f080
Aug 03 03:35:47 vhost082 kernel:  991bbf2587c0 b3e764cf3780 
87c02a4d 02091220
Aug 03 03:35:47 vhost082 kernel:  02091220 b5ee4e30 
991bb5ee4e00 990d8527f080
Aug 03 03:35:47 vhost082 kernel: Call Trace:
Aug 03 03:35:47 vhost082 kernel:  [] ? __schedule+0x23d/0x6d0
Aug 03 03:35:47 vhost082 kernel:  [] ? 
bit_wait_timeout+0x90/0x90
Aug 03 03:35:47 vhost082 kernel:  [] ? schedule+0x32/0x80
Aug 03 03:35:47 vhost082 kernel:  [] ? 
schedule_timeout+0x249/0x300
Aug 03 03:35:47 vhost082 kernel:  [] ? sg_init_table+0x1c/0x40
Aug 03 03:35:47 vhost082 kernel:  [] ? 
__sg_free_table+0x71/0x80
Aug 03 03:35:47 vhost082 kernel:  [] ? 
bit_wait_timeout+0x90/0x90
Aug 03 03:35:47 vhost082 kernel:  [] ? 
io_schedule_timeout+0xb4/0x130
Aug 03 03:35:47 vhost082 kernel:  [] ? 
prepare_to_wait_exclusive+0x57/0x80
Aug 03 03:35:47 vhost082 kernel:  [] ? bit_wait_io+0x17/0x60
Aug 03 03:35:47 vhost082 kernel:  [] ? 
__wait_on_bit_lock+0x7f/0xb0
Aug 03 03:35:47 vhost082 kernel:  [] ? __lock_page+0x7f/0xa0
Aug 03 03:35:47 vhost082 kernel:  [] ? 
autoremove_wake_function+0x40/0x40
Aug 03 03:35:47 vhost082 kernel:  [] ? 
pagecache_get_page+0x21b/0x2b0
Aug 03 03:35:47 vhost082 kernel:  [] ? 
shmem_unused_huge_shrink+0x1eb/0x360
Aug 03 03:35:47 vhost082 kernel:  [] ? 
super_cache_scan+0x184/0x190
Aug 03 03:35:47 vhost082 kernel:  [] ? shrink_slab+0x24a/0x450
Aug 03 03:35:47 vhost082 kernel:  [] ? shrink_node+0x10a/0x320
Aug 03 03:35:47 vhost082 kernel:  [] ? 
do_try_to_free_pages+0xfb/0x330
Aug 03 03:35:47 vhost082 kernel:  [] ? 
try_to_free_pages+0xfc/0x1b0
Aug 03 03:35:47 vhost082 kernel:  [] ? 
__alloc_pages_slowpath+0x319/0xb60
Aug 03 03:35:47 vhost082 kernel:  [] ? 
__alloc_pages_nodemask+0x208/0x270
Aug 03 03:35:47 vhost082 kernel:  [] ? 
alloc_pages_current+0x8a/0x110
Aug 03 03:35:47 vhost082 kernel:  [] ? pte_alloc_one+0x13/0x40
Aug 03 03:35:47 vhost082 kernel:  [] ? __pte_alloc+0x19/0x100
Aug 03 03:35:47 vhost082 kernel:  [] ? 
alloc_set_pte+0x521/0x590
Aug 03 03:35:47 vhost082 kernel:  [] ? 
handle_mm_fault+0x801/0x16b0
Aug 03 03:35:47 vhost082 kernel:  [] ? 
__do_page_fault+0x253/0x510
Aug 03 03:35:47 vhost082 kernel:  [] ? page_fault+0x28/0x30


-- Package-specific info:
** Version:
Linux version 4.9.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.9.30-2+deb9u2~bpo8+1 (2017-06-27)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-0.bpo.3-amd64 
root=UUID=d5af0e4a-1889-47a8-a7c6-9650ce868f02 ro console=tty0 
console=ttyS1,115200n8 quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: P2.10
board_vendor: ASRockRack
board_name: EPC612D4I
board_version:

** Loaded modules:
vhost_net
vhost
macvtap
macvlan
tun
ocfs2
quota_tree
veth
iptable_filter
ip_tables
x_tables
nfsd
auth_rpcgss
oid_registry
nfs_acl
nfs
lockd
grace
fscache
sunrpc
ocfs2_dlmfs
ocfs2_stack_o2cb
ocfs2_dlm
ocfs2_nodemanager
ocfs2_stackglue
configfs
bridge
stp
llc
bonding
ipmi_watchdog
intel_rapl
sb_edac
edac_core
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
crct10dif_pclmul
crc32_pclmul
iTCO_wdt
iTCO_vendor_support
mxm_wmi
evdev
ghash_clmulni_intel
ast
intel_cstate
ttm
drm_kms_helper
intel_uncore
drm
igb
intel_rapl_perf
dca
e1000e
i2c_algo_bit
pcspkr
xhci_pci
xhci_hcd
ehci_pci
ehci_hcd
ptp
usbcore
mei_me
lpc_ich
usb_common
i2c_i801
sg
shpchp
mei
i2c_smbus
mfd_core
pps_core
acpi_power_meter
wmi
acpi_pad
button
ipmi_si
ipmi_poweroff
ipmi_devintf
ipmi_msghandler
fuse
drbd
lru_cache
libcrc32c
crc32c_generic
autofs4
ext4
crc16
jbd2
fscrypto
mbcache
dm_mod
md_mod
sd_mod
crc32c_intel
aesni_intel
aes_x86_64
glue_helper
lrw
gf128mul
ablk_helper
cryptd
ahci
libahci
libata
scsi_mod

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Haswell-E DMI2 [8086:2f00] (rev 
02)

Bug#870598: linux-image-4.9.0-3-amd64: DRBD regression from debian 8 to debian 9, SCSI errors in log and drbd going diskless

[Harald Dunkel]

I would suggest to post /etc/lvm/lvm.conf as well.

Regards
Harri

Bug#868902: Backported patch

[Salvatore Bonaccorso]

Hi,

On Wed, Jul 19, 2017 at 02:48:01PM -0300, Tulio Magno Quites Machado Filho 
wrote:
> The patch fixing this issue was backported to linux-stable 4.9 as
> 2cfdf4fd3292d05eeca5d59307bf231b94df1d4b and is available in Linux 4.9.32.

Thank you. Applied in the stretch-branch as

https://anonscm.debian.org/cgit/kernel/linux.git/commit/?h=stretch=b0fc78bf8d9c1f4b35337da275dca21d7dd51efb

Regards,
Salvatore

Bug#870598: linux-image-4.9.0-3-amd64: DRBD regression from debian 8 to debian 9, SCSI errors in log and drbd going diskless

[Daniel Sobe]

And here's the relevant part of the kernel log file.




part_of_kern.log
Description: part_of_kern.log

Bug#870598: linux-image-4.9.0-3-amd64: DRBD regression from debian 8 to debian 9, SCSI errors in log and drbd going diskless

[Daniel Sobe]

Example DRBD configuration file


sw_headless.res
Description: sw_headless.res

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

[Debian Bug Tracking System]

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

> reassign 870132 src:linux
Bug #870132 [linux-headers-amd64] linux-headers-amd64 broken, can't install
Bug reassigned from package 'linux-headers-amd64' to 'src:linux'.
No longer marked as found in versions linux-latest/83.
Ignoring request to alter fixed versions of bug #870132 to the same values 
previously set
> forcemerge 869511 870132
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
Bug #870298 [src:linux] 4.11.0-2-amd64 headers cannot be installed
Bug #870298 [src:linux] 4.11.0-2-amd64 headers cannot be installed
Added tag(s) newcomer.
Added tag(s) newcomer.
Added tag(s) newcomer.
Bug #870132 [src:linux] linux-headers-amd64 broken, can't install
866389 was blocked by: 865020 826489 866934 867046 865477 865482 867210 869578 
869579 826497 869357 869436 809352 869504 869418 865898 865034 826502 865888 
867213 865380 865033 827640 869602 869583 869139 869670 866978 869511 826505 
867984 826471 866317 865045 870298 865893 869433 866944 865224 869383 826473 
869580 867514 869576 866315
866389 was not blocking any bugs.
Added blocking bug(s) of 866389: 870132
865614 was blocked by: 869511 869670 867257 870298
865614 was not blocking any bugs.
Added blocking bug(s) of 865614: 870132
Marked as found in versions linux/4.11.11-1.
Added tag(s) pending.
Bug #869670 [src:linux] Depends: linux-headers-4.11.0-2-common ... but it is 
not going to be installed
Merged 869511 869670 870132 870298
> 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
870132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870132
870298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): forcibly merging 869511 870132

[Debian Bug Tracking System]

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

> forcemerge 869511 870132
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
Bug #870298 [src:linux] 4.11.0-2-amd64 headers cannot be installed
Unable to merge bugs because:
package of #870132 is 'linux-headers-amd64' not 'src:linux'
Failed to forcibly merge 869511: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Re: Common header files for Linux 4.11.0-2 missing

[Salvatore Bonaccorso]

Hi Norbert,

On Sat, Jul 29, 2017 at 11:17:56AM +0200, norbert.br...@oracle.com wrote:
> 
> 
> Hi there,
> 
> since a couple of days the package linux-headers-4.11.0-2-amd64-4.11.11-1+b1
> is available on download servers, but *linux-headers-4.11.0-2-common
> package is missing.*
> 
> Is there any good reason for it?

This is due to #869511, which has the fix pending in the packaging
repository.

Regards,
Salvatore

Processed: found 868902 in 4.9.30-1, fixed 868902 in 4.11.6-1

[Debian Bug Tracking System]

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

> found 868902 4.9.30-1
Bug #868902 [linux] Floating-point exception happens when exception is disabled
There is no source info for the package 'linux' at version '4.9.30-1' with 
architecture ''
Unable to make a source version for version '4.9.30-1'
Marked as found in versions 4.9.30-1.
> fixed 868902 4.11.6-1
Bug #868902 [linux] Floating-point exception happens when exception is disabled
There is no source info for the package 'linux' at version '4.11.6-1' with 
architecture ''
Unable to make a source version for version '4.11.6-1'
Marked as fixed in versions 4.11.6-1.
> thanks
Stopping processing here.

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