Bug#883413: src:linux: Still reproducible with linux-image-4.15.0-rc8-amd64

2018-01-29 Thread Chris Boot 
Package: src:linux
Followup-For: Bug #883413

Hi Ben,

Unfortunately I can still reproduce this problem on 4.15-rc8 from
experimental.

The cmdline for this boot was:

BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8-amd64
root=/dev/mapper/vg_tarquin-rootfs ro intel_iommu=on vsyscall=emulate
scsi_mod.use_blk_mq=Y dm_mod.use_blk_mq=Y intel_pstate=passive
i915.disable_display=Y i915.enable_gvt=Y apparmor=0
systemd.unified_cgroup_hierarchy=1 console=ttyS1,115200n8 console=tty0

This triggers with DefaultMemoryAccounting=yes enabled in
/etc/systemd/system.conf, and NUT seems to regularly be involved in the
crash on my system. Sadly the systemd unit is very simple indeed, and
because my UPS is network-connected I'm not even doing dodgy things like
USB from within NUT.

Quite how the kernel thinks that nut-server.service is using 16 ZiB of
memory is beyond me; presumably this is a slightly negative 64-bit int
bring cast unsigned. The following also feels like a smoking gun:

[ 2982.158622] percpu ref (css_release) <= 0 (-197) after switching to atomic

The kernel log is:

[ 2611.549862] WARNING: CPU: 0 PID: 20830 at 
/build/linux-b8fmzT/linux-4.15~rc8/mm/page_counter.c:27 
page_counter_cancel+0x17/0x20
[ 2611.561360] Modules linked in: binfmt_misc fuse vhost_net vhost tap tun 
devlink bridge 8021q garp mrp stp llc nls_ascii nls_cp437 vfat fat intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel i915 kvm ast irqbypass 
crct10dif_pclmul crc32_pclmul ttm drm_kms_helper ghash_clmulni_intel 
intel_cstate sg efi_pstore mei_me intel_uncore iTCO_wdt evdev 
iTCO_vendor_support intel_rapl_perf efivars pcspkr drm mei cdc_acm 
intel_pch_thermal shpchp joydev ie31200_edac video acpi_power_meter button 
acpi_pad nfsd nfs_acl lockd grace auth_rpcgss ipmi_si ipmi_devintf sunrpc 
ipmi_msghandler efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 
crc32c_generic fscrypto ecb dm_mod ses enclosure scsi_transport_sas sd_mod 
hid_generic usbhid hid xhci_pci xhci_hcd ahci crc32c_intel ixgbe libahci igb 
i2c_algo_bit
[ 2611.633015]  aesni_intel aes_x86_64 dca ptp usbcore megaraid_sas crypto_simd 
libata cryptd glue_helper i2c_i801 pps_core usb_common mdio scsi_mod fan thermal
[ 2611.647163] CPU: 0 PID: 20830 Comm: check_ups Not tainted 4.15.0-rc8-amd64 
#1 Debian 4.15~rc8-1~exp1
[ 2611.656338] Hardware name: Supermicro Super Server/X11SSH-F, BIOS 2.0c 
10/06/2017
[ 2611.663857] RIP: 0010:page_counter_cancel+0x17/0x20
[ 2611.668765] RSP: 0018:a74c8433fc70 EFLAGS: 00010097
[ 2611.674017] RAX:  RBX: 8bc863c0b4c0 RCX: 
[ 2611.681186] RDX: 3b83ba4109d0 RSI: 0001 RDI: 8bc863c0b4c0
[ 2611.688370] RBP: 0001 R08: 8bc8c50da8a0 R09: 0001
[ 2611.695556] R10: a74c8433fd48 R11: 0100 R12: 8bc863c0b400
[ 2611.702740] R13: 8bc89c092800 R14: 8bc8a1270e10 R15: 8bc76955ec30
[ 2611.709924] FS:  7f0669316fc0() GS:8bc8c500() 
knlGS:
[ 2611.718063] CS:  0010 DS:  ES:  CR0: 80050033
[ 2611.723853] CR2: 7f0668550930 CR3: 00075ce30005 CR4: 003626f0
[ 2611.731036] DR0:  DR1:  DR2: 
[ 2611.738218] DR3:  DR6: fffe0ff0 DR7: 0400
[ 2611.745397] Call Trace:
[ 2611.747881]  page_counter_uncharge+0x1d/0x30
[ 2611.752195]  drain_stock.isra.37+0x32/0xa0
[ 2611.756327]  refill_stock+0x41/0x70
[ 2611.759855]  __sk_mem_reduce_allocated+0x83/0xd0
[ 2611.764508]  tcp_write_queue_purge+0x1a7/0x1d0
[ 2611.768990]  tcp_v4_destroy_sock+0x3f/0x180
[ 2611.773208]  tcp_v6_destroy_sock+0xe/0x20
[ 2611.777257]  inet_csk_destroy_sock+0x47/0x100
[ 2611.781650]  tcp_rcv_state_process+0x980/0xe20
[ 2611.786130]  ? tcp_v6_do_rcv+0x1a7/0x3e0
[ 2611.790090]  tcp_v6_do_rcv+0x1a7/0x3e0
[ 2611.793880]  __release_sock+0x76/0xc0
[ 2611.797581]  release_sock+0x2b/0x90
[ 2611.801107]  tcp_close+0x165/0x3f0
[ 2611.804547]  inet_release+0x36/0x60
[ 2611.808075]  sock_release+0x1a/0x70
[ 2611.811601]  sock_close+0xe/0x20
[ 2611.814861]  __fput+0xd5/0x210
[ 2611.819465]  task_work_run+0x84/0xa0
[ 2611.824577]  exit_to_usermode_loop+0xb9/0xc0
[ 2611.830383]  syscall_return_slowpath+0x88/0x90
[ 2611.836364]  system_call_fast_compare_end+0x73/0x75
[ 2611.842741] RIP: 0033:0x7f0668ac8d84
[ 2611.847774] RSP: 002b:7ffe23f9c7b8 EFLAGS: 0246 ORIG_RAX: 
0003
[ 2611.856787] RAX:  RBX:  RCX: 7f0668ac8d84
[ 2611.865332] RDX: 1fff RSI: 7ffe23f9c800 RDI: 
[ 2611.873833] RBP: 0006 R08:  R09: 
[ 2611.882405] R10:  R11: 0246 R12: 7ffe23f9e800
[ 2611.890813] R13: 7ffe23f9c800 R14: 2000 R15: 
[ 2611.899185] Code: e8 39 b5 eb ff e9 49 ff ff ff 90 90 90 90 90 90 90 90 90 
90 0f 1f 44 00 00 48 89 f0 48 f7 d8 f0 48 0f c1 07 48 39 f0 78 02 f3 c3 <0f> ff

Bug#875621: X1 Carbon trackpoint / Debian Bug#875621

2018-01-26 Thread Chris Boot 
On 19/01/18 13:20, Tony Power wrote:
> Hi Chris,
> 
> Didn't the suggestion in reply to your question helo?
> https://www.spinics.net/lists/linux-input/msg53757.html

I didn't try it. I didn't feel like I was missing out by giving up and
just disabling it.

As a user, I shouldn't have to care and the kernel should do the right
thing for me.

Chris

-- 
Chris Boot
bo...@debian.org

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

2018-01-04 Thread Chris Boot 
On 30/12/17 23:24, Chris Boot wrote:
> What makes me suspicious that these are related is that neither happens
> with a 4.13 kernel, but I get both of these cgroup-related problems with
> 4.14.
> 
> I wouldn't mind trying to bisect this, but I haven't done that for many
> years. Is there a nice way to do this with the Debian packaging or am I
> better off seeing if I can reproduce with vanilla upstream kernels and
> bisecting that? Or shall I give 4.15~rc5 from experimental a whirl instead?

I tried with linux-image-4.15.0-rc5-amd64_4.15~rc5-1~exp1 and my cgroup
issues no longer happen, so I think this is likely fixed in 4.15.

Unfortunately I'm now running into a KVM instability that feels like
#885166, so I'm going to go back to 4.13 shortly.

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org

GPG: 8467 53CB 1921 3142 C56D  C918 F5C8 3C05 D9CE

Bug#875621: X1 Carbon trackpoint / Debian Bug#875621

2018-01-02 Thread Chris Boot 
On 02/01/18 02:06, jus...@justin.sh wrote:
> I'm running Debian testing on an X1 Carbon 5th gen with the following kernel,
> 
>> Linux debian 4.14.0-2-amd64 #1 SMP Debian 4.14.7-1 (2017-12-22) x86_64 
>> GNU/Linux
> 
> I'm experiencing latency issues with the trackpoint and I came across your 
> messages regarding Debian Bug#875621
> 
> Did you ever end up resolving your issues? If so, how? Please be specific as 
> I don't have much experience dealing with hardware issues like this.

I didn't really have any latency issues on my X270 at all, I just
noticed the dmesg output because I routinely check dmesg when I upgrade
the kernel - I'm a bit sad like that. So I raised #875621 to have the
options enabled.

In fact with CONFIG_RMI4_SMB enabled and psmouse.synaptics_intertouch=1
(needed because my TouchPad isn't in the whitelist) I ran into issues
where my TrackPoint stopped working. I mailed
linux-in...@vger.kernel.org[1] and all I got was someone suggesting
loading the modules in a specific order to restore functionality. I
ended up just disabling psmouse.synaptics_intertouch again.

1. https://www.spinics.net/lists/linux-input/msg53749.html

Then #880471 comes along where enabling CONFIG_RMI4_SMB breaks the
TouchPad on the ThinkPad X11e. I noticed that bug and commented that
because nothing improved for me, the new config may as well just be
disabled to avoid further regressions.

Not sure what to suggest here unless someone who is actually involved in
maintaining this stuff (and who knows how it works) steps up to help.

HTH,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

2017-12-30 Thread Chris Boot 
On 25/12/17 23:09, Ben Hutchings wrote:
> On Sat, 2017-12-23 at 12:42 +0000, Chris Boot wrote:
>> Severity: serious
>> Justification: kernel panic
>>
>> I experimented a little and disabled cgroupv2 on that server. Because I 
>> had some issues during boot I attempted to enable 
>> NetworkManager-wait-online.service using systemd, but that instantly 
>> resulted in the following kernel panic:
> [...]
>> I don't know that this is the same bug at all, but I'm keeping it on
>> this report for now as it seems at least related somehow.
> 
> The log messages don't look even slightly related, so please move this 
> to a separate bug report.

I'm still not so certain - both sets of stack dumps fall somewhere
within cgroup space, and disabling systemd's cgroup accounting (not
enabled by default) avoids these conditions.

I like to run this system with the following all enabled in
/etc/systemd/system.conf:

DefaultCPUAccounting=yes
DefaultIOAccounting=yes
DefaultBlockIOAccounting=yes
DefaultMemoryAccounting=yes

These are useful for tools like systemd-cgtop for example.

With cgroupv2, I can avoid the error by disabling
DefaultMemoryAccounting. I was running for nearly 48 hours with this
configuration before rebooting to try without cgroupv2.

Without cgroupv2, it's DefaultCPUAccounting I need to disable to avoid
the panics when I run 'systemd daemon-reload'. I have yet to run into
the warning or OOM killer with memory accounting enabled but I'll let
you know if it happens.

What makes me suspicious that these are related is that neither happens
with a 4.13 kernel, but I get both of these cgroup-related problems with
4.14.

I wouldn't mind trying to bisect this, but I haven't done that for many
years. Is there a nice way to do this with the Debian packaging or am I
better off seeing if I can reproduce with vanilla upstream kernels and
bisecting that? Or shall I give 4.15~rc5 from experimental a whirl instead?

Thanks,
Chris

-- 
Chris Boot
bo...@debian.org

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

2017-12-23 Thread Chris Boot 
pmi_si ipmi_devintf ipmi_msghandler nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc efivarfs ip_tables x_tables autofs4 ext4
[   69.914840]  crc16 mbcache jbd2 crc32c_generic fscrypto ecb dm_mod ses 
enclosure sd_mod scsi_transport_sas hid_generic usbhid xhci_pci crc32c_intel 
xhci_hcd igb ixgbe i2c_algo_bit aesni_intel ahci dca aes_x86_64 libahci usbcore 
ptp crypto_simd libata cryptd megaraid_sas glue_helper usb_common i2c_i801 
pps_core mdio scsi_mod fan thermal i2c_hid hid
[   69.946865] CPU: 1 PID: 1 Comm: systemd Tainted: GW   
4.14.0-2-amd64 #1 Debian 4.14.7-1
[   69.956360] Hardware name: Supermicro Super Server/X11SSH-F, BIOS 2.0b 
07/27/2017
[   69.964301] task: a0552173a040 task.stack: b46243168000
[   69.970681] RIP: 0010:pids_free+0x15/0x40
[   69.975149] RSP: 0018:b4624316bd48 EFLAGS: 00010246
[   69.980829] RAX: a054fb9b3878 RBX:  RCX: 000a
[   69.988420] RDX: 000a RSI: 000b RDI: a054db731410
[   69.996002] RBP: b4624316bd50 R08: 1000 R09: 000c
[   70.003585] R10: 0020 R11: a054b84a500b R12: a054db731410
[   70.011169] R13: bc85c1a0 R14: a054fb9b3878 R15: a0551d8bcc00
[   70.018754] FS:  7f18193e4980() GS:a0554504() 
knlGS:
[   70.027298] CS:  0010 DS:  ES:  CR0: 80050033
[   70.033521] CR2: 00b0 CR3: 0008603ae003 CR4: 003626e0
[   70.041364] DR0:  DR1:  DR2: 
[   70.048974] DR3:  DR6: fffe0ff0 DR7: 0400
[   70.056702] Call Trace:
[   70.059618]  cgroup_free+0x62/0xe0
[   70.063491]  __put_task_struct+0x42/0x150
[   70.067961]  css_task_iter_next+0x74/0x80
[   70.072432]  cgroup_procs_next+0x16/0x20
[   70.076820]  cgroup_seqfile_next+0x1a/0x20
[   70.081377]  kernfs_seq_next+0x27/0x60
[   70.085590]  seq_read+0x2ce/0x3f0
[   70.089368]  kernfs_fop_read+0x134/0x180
[   70.093753]  ? security_file_permission+0x9b/0xc0
[   70.098970]  __vfs_read+0x18/0x40
[   70.102741]  vfs_read+0x8e/0x130
[   70.106424]  SyS_read+0x55/0xc0
[   70.110021]  system_call_fast_compare_end+0xc/0x97
[   70.115316] RIP: 0033:0x7f1818d0076d
[   70.119344] RSP: 002b:7ffc19d1a880 EFLAGS: 0293 ORIG_RAX: 

[   70.127360] RAX: ffda RBX: 5582ad1d9440 RCX: 7f1818d0076d
[   70.134936] RDX: 1000 RSI: 5582ad1f60e0 RDI: 001d
[   70.142502] RBP: 7f1818fbc440 R08: 7f1818fc0188 R09: 1010
[   70.150067] R10: 0020 R11: 0293 R12: 
[   70.157675] R13:  R14: 001d R15: 5582ad0a15c0
[   70.165233] Code: b0 00 00 00 00 75 e7 5b 5d c3 66 90 66 2e 0f 1f 84 00 00 
00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 8b 87 70 08 00 00 48 8b 58 50 <48> 83 
bb b0 00 00 00 00 74 19 48 89 df e8 e9 fc ff ff 48 8b 9b 
[   70.184961] RIP: pids_free+0x15/0x40 RSP: b4624316bd48
[   70.190878] CR2: 00b0
[   70.194615] ---[ end trace 29e4513e3e58325a ]---
[   71.923126] systemd: 49 output lines suppressed due to ratelimiting
[   71.929864] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
[   71.929864] 
[   71.940121] Kernel Offset: 0x3ac0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[   75.216438] Rebooting in 120 seconds..

For the avoidance of doubt, this was obtained with the following kernel cmdline:

BOOT_IMAGE=/boot/vmlinuz-4.14.0-2-amd64 root=/dev/mapper/vg_tarquin-rootfs ro 
intel_iommu=on vsyscall=emulate scsi_mod.use_blk_mq=Y dm_mod.use_blk_mq=Y 
intel_pstate=passive i915.disable_display=Y apparmor=0 console=ttyS1,115200n8 
console=tty0

And the trigger for this was running:

systemctl enable NetworkManager-wait-online.service

I don't know that this is the same bug at all, but I'm keeping it on this 
report for now as it seems at least related somehow.

HTH,
Chris

-- 
Chris Boot
bo...@debian.org

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

2017-12-23 Thread Chris Boot 
Package: src:linux
Version: 4.14.7-1
Followup-For: Bug #883413

Dear kernel maintainers,

This problem is still occuring with the latest 4.14 upload. Once this
warning has happened, prolonged operation leads to spurious OOM kills of
system processes which makes the system unusable.

Best regards,
Chris

-- Package-specific info:
** Version:
Linux version 4.14.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 
7.2.0 (Debian 7.2.0-18)) #1 SMP Debian 4.14.7-1 (2017-12-22)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.14.0-2-amd64 root=/dev/mapper/vg_tarquin-rootfs ro 
intel_iommu=on vsyscall=emulate scsi_mod.use_blk_mq=Y dm_mod.use_blk_mq=Y 
intel_pstate=passive i915.disable_display=true apparmor=0 
systemd.unified_cgroup_hierarchy=1 quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[ 2457.473503] [ cut here ]
[ 2457.473507] WARNING: CPU: 6 PID: 19171 at 
/build/linux-NHzxYj/linux-4.14.7/mm/page_counter.c:27 
page_counter_cancel+0x1b/0x20
[ 2457.473508] Modules linked in: binfmt_misc vhost_net vhost tap tun 
xt_multiport iptable_filter devlink bridge 8021q garp mrp stp llc fuse 
nls_ascii nls_cp437 vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul hci_uart 
ghash_clmulni_intel ast btqca intel_cstate btintel intel_uncore ttm efi_pstore 
evdev joydev bluetooth drm_kms_helper intel_rapl_perf cdc_acm sg pcspkr efivars 
iTCO_wdt iTCO_vendor_support drm mei_me intel_pch_thermal shpchp mei 
ie31200_edac drbg ansi_cprng ecdh_generic rfkill battery intel_lpss_acpi 
intel_lpss mfd_core video acpi_als kfifo_buf acpi_power_meter acpi_pad 
industrialio button nfsd nfs_acl lockd ipmi_si auth_rpcgss grace ipmi_devintf 
ipmi_msghandler sunrpc efivarfs ip_tables x_tables autofs4 ext4 crc16
[ 2457.473536]  mbcache jbd2 crc32c_generic fscrypto ecb dm_mod ses enclosure 
sd_mod scsi_transport_sas hid_generic usbhid crc32c_intel aesni_intel 
aes_x86_64 crypto_simd cryptd glue_helper ahci libahci i2c_i801 xhci_pci 
xhci_hcd igb ixgbe i2c_algo_bit libata dca usbcore megaraid_sas ptp usb_common 
pps_core mdio scsi_mod fan thermal i2c_hid hid
[ 2457.473550] CPU: 6 PID: 19171 Comm: check_ups Not tainted 4.14.0-2-amd64 #1 
Debian 4.14.7-1
[ 2457.473551] Hardware name: Supermicro Super Server/X11SSH-F, BIOS 2.0b 
07/27/2017
[ 2457.473551] task: 96625ad34000 task.stack: a50a43ad8000
[ 2457.473553] RIP: 0010:page_counter_cancel+0x1b/0x20
[ 2457.473553] RSP: 0018:a50a43adbb90 EFLAGS: 00010097
[ 2457.473554] RAX:  RBX: 9662ed1948c0 RCX: 
[ 2457.473554] RDX: 2ea6fa404338 RSI: 0001 RDI: 9662ed1948c0
[ 2457.473555] RBP: a50a43adbb90 R08: 966345012200 R09: 
[ 2457.473555] R10: a50a43adbcb0 R11: 0100 R12: 0001
[ 2457.473556] R13: 9662ed194800 R14: 96631d201000 R15: 9662570fe600
[ 2457.473556] FS:  7fcb1ac90480() GS:96634518() 
knlGS:
[ 2457.473557] CS:  0010 DS:  ES:  CR0: 80050033
[ 2457.473557] CR2: 7ffeba7085e8 CR3: 0007b6aba005 CR4: 003626e0
[ 2457.473558] DR0:  DR1:  DR2: 
[ 2457.473558] DR3:  DR6: fffe0ff0 DR7: 0400
[ 2457.473559] Call Trace:
[ 2457.473562]  page_counter_uncharge+0x22/0x40
[ 2457.473563]  drain_stock.isra.37+0x38/0xa0
[ 2457.473564]  refill_stock+0x47/0x80
[ 2457.473565]  mem_cgroup_uncharge_skmem+0x27/0x40
[ 2457.473567]  __sk_mem_reduce_allocated+0x7a/0xe0
[ 2457.473568]  __sk_mem_reclaim+0x1e/0x20
[ 2457.473570]  tcp_v4_destroy_sock+0x213/0x230
[ 2457.473572]  tcp_v6_destroy_sock+0x12/0x20
[ 2457.473573]  inet_csk_destroy_sock+0x4b/0x110
[ 2457.473574]  tcp_done+0x8d/0x90
[ 2457.473575]  tcp_rcv_state_process+0x9d3/0xe80
[ 2457.473577]  ? sk_reset_timer+0x18/0x30
[ 2457.473577]  ? tcp_schedule_loss_probe+0x12f/0x170
[ 2457.473579]  tcp_v6_do_rcv+0x1c4/0x410
[ 2457.473580]  ? tcp_v6_do_rcv+0x1c4/0x410
[ 2457.473581]  __release_sock+0x83/0xd0
[ 2457.473582]  release_sock+0x30/0xa0
[ 2457.473583]  tcp_close+0x16d/0x3f0
[ 2457.473585]  inet_release+0x3c/0x60
[ 2457.473586]  inet6_release+0x30/0x40
[ 2457.473587]  sock_release+0x1f/0x80
[ 2457.473588]  sock_close+0x12/0x20
[ 2457.473589]  __fput+0xe7/0x220
[ 2457.473590]  fput+0xe/0x10
[ 2457.473592]  task_work_run+0x97/0xc0
[ 2457.473593]  exit_to_usermode_loop+0xc0/0xd0
[ 2457.473594]  syscall_return_slowpath+0x8d/0x90
[ 2457.473596]  system_call_fast_compare_end+0x95/0x97
[ 2457.473597] RIP: 0033:0x7fcb1a446390
[ 2457.473597] RSP: 002b:7ffeba709f28 EFLAGS: 0246 ORIG_RAX: 
0003
[ 2457.473598] RAX:  RBX:  RCX: 7fcb1a446390
[ 2457.473598] RDX: 1fff RSI: 7ffeba709f70 RDI: 
[ 2457.473599] RBP: 0006 R08:  R09: 
[ 2457.473599] R10:  R11:

Bug#883413: linux-image-4.14.0-1-amd64: WARN_ON_ONCE in page_counter_cancel() in mm/page_counter.c

2017-12-03 Thread Chris Boot 
Package: src:linux
Version: 4.14.2-1
Severity: important
Tags: upstream

Hi kernel maintainers,

I've just switched to the 4.14 kernel and pretty quickly hit a strange
(to me) sequence of WARN_ON_ONCE() followed by NUT's upsd getting killed
by the OOM killer despite it not being in a restricted cgroup.

Probably the most relevant tweak for this issue is my use of cgroupv2
(systemd.unified_cgroup_hierarchy=1).

I have not yet tried to reboot my system since running into this (aside
from upsd getting repeatedly killed, it seems to work).

Please let me know if there is anything I can do to help debug this.

Thanks,
Chris

-- Package-specific info:
** Version:
Linux version 4.14.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
7.2.0 (Debian 7.2.0-16)) #1 SMP Debian 4.14.2-1 (2017-11-30)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.14.0-1-amd64 root=/dev/mapper/vg_tarquin-rootfs ro 
intel_iommu=on vsyscall=emulate scsi_mod.use_blk_mq=Y dm_mod.use_blk_mq=Y 
intel_pstate=passive systemd.unified_cgroup_hierarchy=1 quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[ 2420.733243] [ cut here ]
[ 2420.733247] WARNING: CPU: 5 PID: 20290 at 
/build/linux-ZSFHrj/linux-4.14.2/mm/page_counter.c:27 
page_counter_cancel+0x1b/0x20
[ 2420.733248] Modules linked in: dm_crypt loop algif_skcipher af_alg 
kyber_iosched bfq binfmt_misc vhost_net vhost tap tun xt_multiport 
iptable_filter bridge devlink 8021q garp mrp stp llc fuse intel_rapl nls_ascii 
nls_cp437 x86_pkg_temp_thermal intel_powerclamp coretemp vfat fat kvm_intel kvm 
hci_uart btqca irqbypass btintel bluetooth crct10dif_pclmul crc32_pclmul i915 
ghash_clmulni_intel ast intel_cstate efi_pstore j
oydev evdev intel_uncore ttm sg drbg intel_rapl_perf cdc_acm pcspkr 
drm_kms_helper ansi_cprng efivars drm iTCO_wdt shpchp mei_me 
iTCO_vendor_support mei intel_pch_thermal ie31200_edac battery ecdh_generic 
intel_lpss_acpi intel_lpss rfkill mfd_core video acpi_als acpi_power_meter 
kfifo_buf industrialio acpi_pad button ipmi_si ipmi_devintf ipmi_msghandler 
nfsd nfs_acl lockd auth_rpcgss
[ 2420.733274]  grace sunrpc efivarfs ip_tables x_tables autofs4 ext4 crc16 
mbcache jbd2 crc32c_generic fscrypto ecb dm_mod ses enclosure 
scsi_transport_sas sd_mod hid_generic usbhid crc32c_intel aesni_intel 
aes_x86_64 crypto_simd cryptd glue_helper i2c_i801 ahci xhci_pci igb ixgbe 
libahci xhci_hcd i2c_algo_bit dca libata usbcore megaraid_sas ptp usb_common 
pps_core mdio scsi_mod fan thermal i2c_hid hid
[ 2420.733289] CPU: 5 PID: 20290 Comm: check_ups Not tainted 4.14.0-1-amd64 #1 
Debian 4.14.2-1
[ 2420.733290] Hardware name: Supermicro Super Server/X11SSH-F, BIOS 2.0b 
07/27/2017
[ 2420.733290] task: 9f6d3af50040 task.stack: bb78c6948000
[ 2420.733292] RIP: 0010:page_counter_cancel+0x1b/0x20
[ 2420.733292] RSP: 0018:bb78c694bb90 EFLAGS: 00010097
[ 2420.733293] RAX:  RBX: 9f6d29fcdcc0 RCX: 
[ 2420.733293] RDX: 3c0b3a402678 RSI: 0001 RDI: 9f6d29fcdcc0
[ 2420.733294] RBP: bb78c694bb90 R08: 9f6d850120f0 R09: 
[ 2420.733294] R10: bb78c694bcb0 R11: 0100 R12: 0001
[ 2420.733295] R13: 9f6d29fcdc00 R14: 9f6d4e353000 R15: 9f6d43bc3780
[ 2420.733295] FS:  7f1043d50480() GS:9f6d8514() 
knlGS:
[ 2420.733296] CS:  0010 DS:  ES:  CR0: 80050033
[ 2420.733296] CR2: 7ffe7c8c8628 CR3: 00078c404003 CR4: 003626e0
[ 2420.733297] DR0:  DR1:  DR2: 
[ 2420.733297] DR3:  DR6: fffe0ff0 DR7: 0400
[ 2420.733298] Call Trace:
[ 2420.733300]  page_counter_uncharge+0x22/0x40
[ 2420.733301]  drain_stock.isra.37+0x38/0xa0
[ 2420.733302]  refill_stock+0x47/0x80
[ 2420.733303]  mem_cgroup_uncharge_skmem+0x27/0x40
[ 2420.733305]  __sk_mem_reduce_allocated+0x7a/0xe0
[ 2420.733306]  __sk_mem_reclaim+0x1e/0x20
[ 2420.733308]  tcp_v4_destroy_sock+0x213/0x230
[ 2420.733310]  tcp_v6_destroy_sock+0x12/0x20
[ 2420.733311]  inet_csk_destroy_sock+0x4b/0x100
[ 2420.733312]  tcp_done+0x8d/0x90
[ 2420.733313]  tcp_rcv_state_process+0x9d3/0xe80
[ 2420.733314]  ? sk_reset_timer+0x18/0x30
[ 2420.733315]  ? tcp_schedule_loss_probe+0x11e/0x160
[ 2420.733316]  tcp_v6_do_rcv+0x1c4/0x410
[ 2420.733317]  ? tcp_v6_do_rcv+0x1c4/0x410
[ 2420.733318]  __release_sock+0x83/0xd0
[ 2420.733319]  release_sock+0x30/0xa0
[ 2420.733320]  tcp_close+0x167/0x3f0
[ 2420.733322]  inet_release+0x3c/0x60
[ 2420.733323]  inet6_release+0x30/0x40
[ 2420.733325]  sock_release+0x1f/0x80
[ 2420.733326]  sock_close+0x12/0x20
[ 2420.733327]  __fput+0xe7/0x220
[ 2420.733328]  fput+0xe/0x10
[ 2420.70]  task_work_run+0x97/0xc0
[ 2420.71]  exit_to_usermode_loop+0xc0/0xd0
[ 2420.72]  syscall_return_slowpath+0x8d/0x90
[ 2420.73]  system_call_fast_compare_end+0x95/0x97
[ 2420.74] RIP: 0033:0x7f1043506390
[ 2420.75] RSP:

Bug#880471: Touchpad doesn't work anymore

2017-11-11 Thread Chris Boot 
On 11/11/17 19:44, Daniel Leidert wrote:
>> [  164.712261] psmouse serio1: synaptics: queried max coordinates: x 
>> [..5676], y [..4732]
>> [  164.759543] psmouse serio1: synaptics: queried min coordinates: x 
>> [1356..], y [1214..]
>> [  164.759556] psmouse serio1: synaptics: Trying to set up SMBus access
>> [  164.784566] rmi4_smbus 1-002c: registering SMbus-connected sensor
>> [  164.841110] rmi4_f01 rmi4-01.fn01: found RMI device, manufacturer: 
>> Synaptics, product: s3203_ver5, fw id: 1569351
>> [  164.903005] input: Synaptics s3203_ver5 as /devices/rmi4-01/input/input25

Hi Daniel,

This must definitely be because of the config options enabled recently
at my request: the rmi4_smbus module wasn't enabled until then. Perhaps
booting with 'psmouse.synaptics_intertouch=0' on the kernel command-line
can allow this to work normally for now?

Unfortunately I don't know enough about how this works to help much;
perhaps linux-in...@vger.kernel.org can help you further.

Ben / Debian kernel maintainers: perhaps this module would be better off
disabled, or this functionality disabled by default. Given that this
hasn't had the expected result on my X270 anyway that doesn't seem like
a bad option to me.

HTH,
Chris

-- 
Chris Boot
bo...@debian.org

Bug#880471: Touchpad doesn't work anymore

2017-11-11 Thread Chris Boot 
On 31 Oct 2017, at 22:29, Daniel Leidert <dleid...@debian.org> wrote:
> With linux kernel linux-image-4.12.0-2-amd64 4.12.13-1 I have this output.
> 
> hwinfo --short:
> 
>  /dev/input/mice  SynPS/2 Synaptics TouchPad
>  /dev/input/mice  ATML1000:00 03EB:8C1F
> 
> syslog:
> 
>  kernel: [3.520469] input: SynPS/2 Synaptics TouchPad as 
> /devices/platform/i8042/serio1/input/input2
> 
> There seems to be a major difference between kernels 4.12 and 4.13.

I wonder if this is somehow related to #875621 where I asked for some 
additional options to be enabled. Daniel, could you please include a full dmesg 
output from the 4.13 kernel? In particular I’m looking for lines containing 
“psmouse” or “rmi4”.

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org

Bug#875621: ThinkPad X270 Synaptics Touchpad, RMI4 SMB

2017-10-30 Thread Chris Boot 
Hi folks,

I have a Lenovo ThinkPad X270 and noticed that my kernel (Debian
buster/testing stock kernel) was suggesting that my Touchpad would
benefit from having CONFIG_RMI4_SMB enabled, so I raised this Debian bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875621

This was closed today with an updated Debian kernel upload,
linux_4.13.10-1 (thanks Ben). The new kernel now says:

Oct 30 22:13:49 muta kernel: [3.557065] hid-generic
0003:1050:0407.0002: hiddev0,hidraw1: USB HID v1.10 Device [Yubico
Yubikey 4 OTP+U2F+CCID] on usb-:00:14.0-6/input1
Oct 30 22:13:49 muta kernel: [3.574540] psmouse serio1: synaptics:
queried max coordinates: x [..5712], y [..4780]
Oct 30 22:13:49 muta kernel: [3.608224] psmouse serio1: synaptics:
queried min coordinates: x [1232..], y [1074..]
Oct 30 22:13:49 muta kernel: [3.608238] psmouse serio1: synaptics:
Your touchpad (PNP: LEN2049 PNP0f13) says it can support a different
bus. If i2c-hid and hid-rmi are not used, you might want to try setting
psmouse.synaptics_intertouch to 1 and report this to
linux-in...@vger.kernel.org.
Oct 30 22:13:49 muta kernel: [3.674976] psmouse serio1: synaptics:
Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps:
0xf407a3/0x943300/0x12e800/0x41, board id: 3075, fw id: 2477413
Oct 30 22:13:49 muta kernel: [3.674997] psmouse serio1: synaptics:
serio: Synaptics pass-through port at isa0060/serio1/input0
Oct 30 22:13:49 muta kernel: [3.717820] input: SynPS/2 Synaptics
TouchPad as /devices/platform/i8042/serio1/input/input2
Oct 30 22:13:49 muta kernel: [4.393051] psmouse serio2: trackpoint:
IBM TrackPoint firmware: 0x0e, buttons: 3/3
Oct 30 22:13:49 muta kernel: [4.620327] input: TPPS/2 IBM TrackPoint
as /devices/platform/i8042/serio1/serio2/input/input4

So I enabled psmouse.synaptics_intertouch=1 on my kernel command line
and voila, rmi4_smbus is used and my Touchpad is apparently much better
off for it. Great! Except I can't use my TrackPoint now, it no longer
shows up at all:

Oct 30 22:17:20 muta kernel: [3.478867] psmouse serio1: synaptics:
queried max coordinates: x [..5712], y [..4780]
Oct 30 22:17:20 muta kernel: [3.513094] psmouse serio1: synaptics:
queried min coordinates: x [1232..], y [1074..]
Oct 30 22:17:20 muta kernel: [3.513098] psmouse serio1: synaptics:
Trying to set up SMBus access
Oct 30 22:17:20 muta kernel: [9.163140] rmi4_smbus 0-002c:
registering SMbus-connected sensor
Oct 30 22:17:20 muta kernel: [9.262824] rmi4_f01 rmi4-00.fn01: found
RMI device, manufacturer: Synaptics, product: TM3075-007, fw id: 2477413
Oct 30 22:17:20 muta kernel: [9.375014] input: Synaptics TM3075-007
as /devices/rmi4-00/input/input10

So I'm emailing both about having to enable synaptics_intertouch for my
Touchpad as instructed in dmesg, and also that enabling it makes my
TrackPoint disappear.

Please CC me on all replies, I'm not subscribed to linux-input@v.k.o.

Thanks,
Chris

-- 
Chris Boot
bo...@boo.tc

Bug#875621: linux: ThinkPad X270 Synaptics touchpad: please enable CONFIG_RMI4_SMB

2017-09-12 Thread Chris Boot 
Source: linux
Version: 4.12.6-1
Severity: wishlist

Dear Maintainer,

During boot, the 4.12 kernel suggests some additional kernel options
should be enabled to improve touchpad support:

Sep  8 14:18:15 muta kernel: [4.089833] psmouse serio1: synaptics:
queried max coordinates: x [..5712], y [..4780]
Sep  8 14:18:15 muta kernel: [4.121930] psmouse serio1: synaptics:
queried min coordinates: x [1232..], y [1074..]
Sep  8 14:18:15 muta kernel: [4.121939] psmouse serio1: synaptics:
The touchpad can support a better bus than the too old PS/2 protocol.
Make sure MOUSE_PS2_SYNAPTICS_SMBUS and RMI4_SMB are enabled to get a
better touchpad experience.
Sep  8 14:18:15 muta kernel: [4.184718] psmouse serio1: synaptics:
Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps:
0xf407a3/0x943300/0x12e800/0x41, board id: 3075, fw id: 2477413
Sep  8 14:18:15 muta kernel: [4.184735] psmouse serio1: synaptics:
serio: Synaptics pass-through port at isa0060/serio1/input0

Please consider enabling CONFIG_RMI4_SMB.
CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS is already enabled:

bootc@muta ~ $ egrep 'MOUSE_PS2_SYNAPTICS_SMBUS|RMI4_SMB'
/boot/config-4.12.0-1-amd64
CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y
# CONFIG_RMI4_SMB is not set

Thanks,
Chris

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#790953: i40e: internal packet reflection breaks bridging

2015-07-03 Thread Chris Boot 
Package: linux-image-4.0.0-2-amd64
Severity: important

Dear Maintainer,

I have run into a bug while using Intel X710 NICs with the i40e driver.
This bug does *not* affect 3.16, but does affect the 4.0 kernel in sid.

The bug means that when in promiscuous mode, packets sent out the NIC
are also reflected back in. When adding a port to a bridge, the port is
put into promisc mode, and the reflected packets wreak havoc with the
FDB.

The problem is easily detectable when running a packet capture: any
packets sent out appear to be duplicated in the capture. When a VM is
part of a bridge its outgoing packets are forwarded out but also
reflected back in. This updates the bridge's FDB which now thinks the
VM's MAC is on the uplink port. The response then arrives but is
dropped because it arrives on the same port the bridge thinks it should
forward it out on (and hairpinning is disabled, and wouldn't help
here anyway).

When running lldpd, the local machine also appears as a remote machine
in its database.

The issue is discussed in https://communities.intel.com/message/305975

A patch working around the issue has gone into 4.1 as commit
fc60861e9b00388fd11d7995a60bf0b1e61dba93.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fc60861e9b00388fd11d7995a60bf0b1e61dba93

Hope this helps!

Best regards,
Chris

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

Kernel: Linux 4.0.0-2.tcl.1-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/559659b1.2040...@tiger-computing.co.uk

Bug#764804: linux-image-3.16-2-amd64: BUG in qla2xxx qlt_create_sess_from_atio

2014-10-11 Thread Chris Boot 
Package: src:linux
Version: 3.16.3-2
Severity: important
Tags: upstream patch

Hi kernel maintainers,

I am affected by a bug in the qla2xxx driver, which manifests itself when I use
it in target mode. Having dome some investigation I believe this bug is already
fixed upstream in linux.git commit 78c2106a50e067f7168ee8c0944baaeb0e988272.

The commit is in git master and CCed to stable, but is not yet included in any
tagged release including 3.17-rc releases. It would be great if this fix was
included in the Debian kernel soon. I have tested and have the same problem on
3.16.5-1 as well.

The BUG looks like:

[ 4925.760391] qla2xxx [:05:00.0]-505f:9: Link is operational (4 Gbps).
[ 4925.792942] BUG: unable to handle kernel NULL pointer dereference at 
01a0
[ 4925.809975] IP: [a036d2b3] qlt_create_sess_from_atio+0x33/0x170 
[qla2xxx]
[ 4925.826832] PGD 0 
[ 4925.837184] Oops:  [#1] SMP 
[ 4925.848882] Modules linked in: binfmt_misc ib_srpt ib_cm ib_sa ib_mad 
ib_core ib_addr tcm_qla2xxx tcm_loop tcm_fc libfc target_core_pscsi 
target_core_file target_core_iblock target_core_mod configfs xt_multiport 
iptable_filter ip_tables x_tables nfsd auth_rpcgss oid_registry nfs_acl nfs 
lockd fscache sunrpc 8021q garp stp mrp llc dm_cache_mq nls_utf8 nls_cp437 vfat 
fat dm_cache dm_persistent_data dm_bio_prison dm_bufio libcrc32c 
x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm_intel kvm 
crc32_pclmul ghash_clmulni_intel aesni_intel iTCO_wdt ppdev iTCO_vendor_support 
ttm drm_kms_helper aes_x86_64 lrw gf128mul drm glue_helper ablk_helper cryptd 
efi_pstore pcspkr efivars i2c_i801 i2c_algo_bit joydev i2c_core evdev cdc_acm 
lpc_ich mfd_core tpm_tis tpm winbond_cir rc_core parport_pc battery shpchp 
parport video ac processor button ipmi_watchdog ipmi_si ipmi_poweroff 
ipmi_devintf ipmi_msghandler autofs4 ext4 crc16 mbcache jbd2 dm_mod hid_generic 
usbhid hid raid1 md_mod sg sd
 _mod crc_t10dif crct10dif_generic ehci_pci crct10dif_pclmul crct10dif_common 
ehci_hcd crc32c_intel ahci libahci qla2xxx libata e1000e scsi_transport_fc ptp 
3w_sas usbcore scsi_tgt pps_core scsi_mod netxen_nic usb_common thermal fan 
thermal_sys
[ 4926.093879] CPU: 2 PID: 287 Comm: kworker/2:2 Not tainted 3.16-2-amd64 #1 
Debian 3.16.3-2
[ 4926.113718] Hardware name: Intel Corporation S1200BTL/S1200BTL, BIOS 
S1200BT.86B.02.00.0041.120520121743 12/05/2012
[ 4926.146971] Workqueue: qla_tgt_wq qlt_create_sess_from_atio [qla2xxx]
[ 4926.165106] task: 880425d8e150 ti: 88042862 task.ti: 
88042862
[ 4926.184338] RIP: 0010:[a036d2b3]  [a036d2b3] 
qlt_create_sess_from_atio+0x33/0x170 [qla2xxx]
[ 4926.217277] RSP: 0018:880428623de8  EFLAGS: 00010296
[ 4926.234192] RAX: 00ef RBX: 880406edea08 RCX: a0386ff8
[ 4926.253172] RDX: f022 RSI: 5040 RDI: 880406edea08
[ 4926.272022] RBP:  R08: 1000 R09: 
[ 4926.290760] R10: dfef6c4c5ecdea08 R11: 0005 R12: 880406ede9c0
[ 4926.309362] R13: 88043e65b500 R14:  R15: 0080
[ 4926.327774] FS:  () GS:88043e64() 
knlGS:
[ 4926.347318] CS:  0010 DS:  ES:  CR0: 80050033
[ 4926.364144] CR2: 01a0 CR3: 01a13000 CR4: 000407e0
[ 4926.382454] Stack:
[ 4926.394767]  88043e654240 880409866840  
880406edea08
[ 4926.413309]  880425082880 88043e653a40 88043e65b500 

[ 4926.431791]  0080 8107f4a2 25d8e150 
88043e653a40
[ 4926.450243] Call Trace:
[ 4926.462873]  [8107f4a2] ? process_one_work+0x172/0x420
[ 4926.479550]  [8107fb35] ? worker_thread+0x115/0x520
[ 4926.495991]  [81508591] ? __schedule+0x2b1/0x710
[ 4926.511921]  [8107fa20] ? rescuer_thread+0x2d0/0x2d0
[ 4926.528051]  [81085dcd] ? kthread+0xbd/0xe0
[ 4926.543078]  [81085d10] ? kthread_create_on_node+0x180/0x180
[ 4926.559573]  [8150c1bc] ? ret_from_fork+0x7c/0xb0
[ 4926.574787]  [81085d10] ? kthread_create_on_node+0x180/0x180
[ 4926.590937] Code: c7 c1 f8 6f 38 a0 ba 22 f0 00 00 41 56 41 55 41 54 4c 8d 
67 b8 55 53 48 89 fb 48 83 ec 18 0f b6 47 cf 48 8b 6f b8 44 0f b6 4f cd 4c 8b 
b5 a0 01 00 00 44 0f b7 85 88 01 00 00 48 89 ee 89 44 24 
[ 4926.639383] RIP  [a036d2b3] qlt_create_sess_from_atio+0x33/0x170 
[qla2xxx]
[ 4926.656819]  RSP 880428623de8
[ 4926.669225] CR2: 01a0
[ 4926.694230] ---[ end trace f78a641ca511f866 ]---

Thanks,
Chris

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Intel Corporation
product_name: S1200BTL
product_version: 
chassis_vendor: Supermicro
chassis_version: SC846BE16-R920B
bios_vendor: Intel Corp.
bios_version: S1200BT.86B.02.00.0041.120520121743
board_vendor: Intel Corporation

Bug#721316: base: NETDEV WATCHDOG: eth0 (igb): transmit queue 0 timed out

2014-01-08 Thread Chris Boot 
 Range, 
 EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
   LnkSta2: Current De-emphasis Level: -6dB, 
 EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, 
 LinkEqualizationRequest-
   Capabilities: [100 v2] Advanced Error Reporting
   UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
 RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
   UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
 RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
   UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
 RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
   CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
   CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
   AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [140 v1] Device Serial Number 00-25-90-ff-ff-4e-ae-18
   Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI)
   ARICap: MFVC- ACS-, Next Function: 0
   ARICtl: MFVC- ACS-, Function Group: 0
   Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)
   IOVCap: Migration-, Interrupt Message Number: 000
   IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy-
   IOVSta: Migration-
   Initial VFs: 8, Total VFs: 8, Number of VFs: 8, Function 
 Dependency Link: 01
   VF offset: 384, stride: 4, Device ID: 1520
   Supported Page Size: 0553, System Page Size: 0001
   Region 0: Memory at fbd6 (32-bit, non-prefetchable)
   Region 3: Memory at fbd4 (32-bit, non-prefetchable)
   VF Migration: offset: , BIR: 0
   Capabilities: [1a0 v1] Transaction Processing Hints
   Device specific mode supported
   Steering table in TPH capability structure
   Capabilities: [1d0 v1] Access Control Services
   ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- 
 EgressCtrl- DirectTrans-
   ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- 
 EgressCtrl- DirectTrans-
   Kernel driver in use: igb

Please let me know if I can provide any further information.

Best regards,
Chris

-- 
Chris Boot
Tiger Computing Ltd
Linux for Business

Tel: 01600 483 484
Web: http://www.tiger-computing.co.uk
Follow us on Facebook: http://www.facebook.com/TigerComputing

Registered in England. Company number: 3389961
Registered address: Wyastone Business Park,
 Wyastone Leys, Monmouth, NP25 3SR


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52cd4f3d.8000...@tiger-computing.co.uk

Bug#734376: linux: Please enable accelerated variants of crypto modules

2014-01-06 Thread Chris Boot 
Source: linux
Version: 3.12.6-2
Severity: normal

Dear Maintainer,

Please consider enabling more of the accelerated variants of the crypto
modules available in the kernel. For example, the current kernel config
contains:

CONFIG_CRYPTO_CRCT10DIF=m
# CONFIG_CRYPTO_CRCT10DIF_PCLMUL is not set

CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA1_SSSE3=m
# CONFIG_CRYPTO_SHA256_SSSE3 is not set
# CONFIG_CRYPTO_SHA512_SSSE3 is not set
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m

CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAMELLIA_X86_64=m
# CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64 is not set

CONFIG_CRYPTO_CAST5=m
# CONFIG_CRYPTO_CAST5_AVX_X86_64 is not set
CONFIG_CRYPTO_CAST6=m
# CONFIG_CRYPTO_CAST6_AVX_X86_64 is not set

CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_SERPENT_SSE2_X86_64=m
CONFIG_CRYPTO_SERPENT_AVX_X86_64=m
# CONFIG_CRYPTO_SERPENT_AVX2_X86_64 is not set

For x86_64/amd64 at least, it would be nice to enable all of the options
marked as 'not set' above.

Thanks,
Chris

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

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Chris Boot
deb...@bootc.net
GPG: 1DE8 6AB0 1897 A330 D973  D77C 50DD 5A29 FB09 


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52cac80f.1070...@bootc.net

Re: The effect of the kernel version on am-utils

2013-09-09 Thread Chris Boot 
On 09/09/13 14:07, Yoram Bar Haim wrote:
 this work-around will make program think they run on top of 2.6.x
 kernel, which might be a bug if the program does have special behavior
 for 3.x.y

With all due respect, it's a bug in a program if it crashes with a 3.x
uname string. If it then also misbehaves if it's given a 2.6.x string,
it's no more or less a bug in the program. In either case, the broken
program needs fixing.

The option to present a 2.6.x uname was done mostly as a hack for 3rd
party software for which it can be difficult to obtain updates. There's
no excuse to use this hack for software that can be built from source.

Personally, I have run into this issue with the 3ware/LSI RAID admin
tools, tw_cli and 3dm2, both of which crash unless there are 3
dot-separated components in the kernel uname string. This annoys me
enough that I build my own kernel with the 3rd element added in (among
other tweaks), but I don't really expect Debian to go back to having
this. What would be welcome is a documented way of building your own
kernel that has this, as currently my hacks to do this are a bit ugly.

I'm pretty sure software developers have been told not to attempt to
parse uname strings as they could be in any format, but that clearly
hasn't stopped anyone. It's still their problem, not the kernel's! :-)

HTH,
Chris

 On Mon, Sep 9, 2013 at 3:49 PM, Ben Hutchings b...@decadent.org.uk
 mailto:b...@decadent.org.uk wrote:
 
 On Mon, 2013-09-09 at 14:12 +0200, Yoram Bar Haim wrote:
  using 3.x instead of 3.x.0 (when minor-minor version is 0) is done by
  kernel.org http://kernel.org, so I suppose it makes sense for
 Debian to follow this
  scheme.
 
 Actually, the '.0' is still included if you build a kernel without any
 stable updates and without Debian patches.  But the '3.2.0' in wheezy
 sometimes confuses people into thinking we aren't applying any stable
 updates.  I reckoned that userland in wheezy would be ready for 3.x
 releases and so it would be safe to drop the third part in jessie.
 
 By the way, the kernel has a workaround for programs that can't handle
 3.x.y releases, which also works for 3.x.  Use setarch with the
 --uname-2.6 option.
 
 Ben.
 
  it may be a good idea to run a test that logs all components calling
  uname, so they can be checked for version scheme bugs.
 
 
 
  On Sun, Sep 8, 2013 at 5:46 PM, Lior Kaplan kap...@debian.org
 mailto:kap...@debian.org wrote:
  Hi,
 
 
 
  Just FYI, as you might be interested in
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722145
 
 
  Kaplan
 
 
 
 
 --
 Ben Hutchings
 Man invented language to satisfy his deep need to complain. - Lily
 Tomlin
 
 

-- 
Chris Boot
bo...@bootc.net


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/522defe1.1060...@bootc.net

Re: Flaky SSD or issue with kernel

2013-08-04 Thread Chris Boot 
On 02/08/2013 21:28, Brian Paterni wrote:
 Hi
 
 I've experienced this twice now. Once yesterday and again today. What
 happens is, out of the blue, the system will get out of whack. Programs
 will unexpectedly stall or shutdown, then all of a sudden the system is
 no longer usable, and any attempt to start another process or execute
 basic commands results in a segfault or IO error. The only thing that
 sets the system straight again is a cold reboot.
 
 I did not send a bug report because I'm starting to think it is a
 hardware problem, but I wanted to ask here for a second opinion anyway
 in the hopes it might be some kernel issue.
 
 SSD is a Crucial M4-CT128M4SSD2
 
 Attached should be a portion of the kernel/syslog related to the problem.
 
 Please let me know what you think
 

What firmware version do you have on your SSD? The M4 series were
plagued by bad firmware until fairly recently, and your symptoms sound
very much like what I experienced myself. Please make sure you are on at
least 040H firmware, which fixes the issue.

HTH,
Chris

-- 
Chris Boot
bo...@bootc.net


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51fe8d19.2040...@bootc.net

[PATCH] New upstream release (3.10)

2013-07-06 Thread Chris Boot 
This patch updates the linux-tools package for linux-3.10. This was relatively
straightforward except for the CONFIG_SYMBOL_PREFIX rework; I believe I have
kept with the spirit of the v3.9 version of the package.

HTH,
Chris

---
 debian/changelog   |6 ++
 debian/patches/modpost-symbol-prefix.patch |   23 ---
 debian/patches/tools-perf-version.patch|   20 
 3 files changed, 26 insertions(+), 23 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index f30d4cd..033aad1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+linux-tools (3.10-1) UNRELEASED; urgency=low
+
+  * New upstream release
+
+ -- Chris Boot deb...@bootc.net  Mon, 01 Jul 2013 22:07:42 +0100
+
 linux-tools (3.9.4-1) unstable; urgency=low
 
   * New upstream release
diff --git a/debian/patches/modpost-symbol-prefix.patch 
b/debian/patches/modpost-symbol-prefix.patch
index 7fc7e7a..07cfd4d 100644
--- a/debian/patches/modpost-symbol-prefix.patch
+++ b/debian/patches/modpost-symbol-prefix.patch
@@ -1,19 +1,12 @@
 a/scripts/mod/modpost.c
-+++ b/scripts/mod/modpost.c
-@@ -16,15 +16,11 @@
- #include ctype.h
- #include string.h
+Index: linux-tools/scripts/mod/modpost.c
+===
+--- linux-tools.orig/scripts/mod/modpost.c 2013-06-30 23:13:29.0 
+0100
 linux-tools/scripts/mod/modpost.c  2013-07-01 22:11:53.450887929 +0100
+@@ -18,7 +18,6 @@
+ #include limits.h
+ #include stdbool.h
  #include modpost.h
 -#include ../../include/generated/autoconf.h
  #include ../../include/linux/license.h
+ #include ../../include/linux/export.h
  
- /* Some toolchains use a `_' prefix for all user symbols. */
--#ifdef CONFIG_SYMBOL_PREFIX
--#define MODULE_SYMBOL_PREFIX CONFIG_SYMBOL_PREFIX
--#else
-+/* No Debian architecture currently does this. */
- #define MODULE_SYMBOL_PREFIX 
--#endif
- 
- 
- /* Are we using CONFIG_MODVERSIONS? */
diff --git a/debian/patches/tools-perf-version.patch 
b/debian/patches/tools-perf-version.patch
index 8dc5971..1a04222 100644
--- a/debian/patches/tools-perf-version.patch
+++ b/debian/patches/tools-perf-version.patch
@@ -1,6 +1,8 @@
 a/tools/perf/Makefile
-+++ b/tools/perf/Makefile
-@@ -1141,7 +1141,7 @@ perfexec_instdir_SQ = $(subst ','\'',$(p
+Index: linux-tools/tools/perf/Makefile
+===
+--- linux-tools.orig/tools/perf/Makefile   2013-06-30 23:13:29.0 
+0100
 linux-tools/tools/perf/Makefile2013-07-01 22:13:20.073226760 +0100
+@@ -1172,7 +1172,7 @@
  
  install-bin: all
$(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(bindir_SQ)'
@@ -9,7 +11,7 @@
$(INSTALL) -d -m 755 
'$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/Perf-Trace-Util/lib/Perf/Trace'
$(INSTALL) -d -m 755 
'$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/bin'
$(INSTALL) $(OUTPUT)perf-archive -t 
'$(DESTDIR_SQ)$(perfexec_instdir_SQ)'
-@@ -1154,7 +1154,7 @@ install-bin: all
+@@ -1185,7 +1185,7 @@
$(INSTALL) scripts/python/*.py -t 
'$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python'
$(INSTALL) scripts/python/bin/* -t 
'$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/bin'
$(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(sysconfdir_SQ)/bash_completion.d'
@@ -18,7 +20,7 @@
$(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests'
$(INSTALL) tests/attr.py '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests'
$(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/attr'
-@@ -1167,7 +1167,7 @@ install-python_ext:
+@@ -1198,7 +1198,7 @@
  
  # 'make install-doc' should call 'make -C Documentation install'
  $(INSTALL_DOC_TARGETS):
@@ -27,9 +29,11 @@
  
  ### Cleaning rules
  
 a/tools/perf/Documentation/Makefile
-+++ b/tools/perf/Documentation/Makefile
-@@ -188,13 +188,15 @@ ifdef missing_tools
+Index: linux-tools/tools/perf/Documentation/Makefile
+===
+--- linux-tools.orig/tools/perf/Documentation/Makefile 2013-06-30 
23:13:29.0 +0100
 linux-tools/tools/perf/Documentation/Makefile  2013-07-01 
22:13:20.073226760 +0100
+@@ -188,13 +188,15 @@
$(error You need to install $(missing_tools) for man pages)
  endif
  
-- 
1.7.10.4


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1372716602-69171-1-git-send-email-deb...@bootc.net

Bug#712487: marked as done (linux-image-3.2.0-4-amd64: Modifying/deleting an EFI variable with efibootmgr causes kernel oops)

2013-06-16 Thread Chris Boot 
On 16 Jun 2013, at 18:51, Debian Bug Tracking System ow...@bugs.debian.org 
wrote:

 On Sun, 2013-06-16 at 17:27 +0100, Gary Hawkins wrote:
 It appears that OVMF r14423 which I've compiled just now (after I
 discovered that I wasn't on the latest OVMF as they'd move the svn
 repository) no longer causes the kernel to oops and seems to make
 efibootmgr work properly.
 
 So, not a kernel bug at all.
 
 Ben.

Ben,

Is it not a bug that this causes the kernel to panic? Or is that something that 
bad EFI code can do?

Cheers,
Chris

-- 
Chris Boot
bo...@bootc.net


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/6d595921-556a-426a-9c28-c7f8be568...@bootc.net

Bug#712062: Please enable X86_INTEL_PSTATE (P state power scaling driver)

2013-06-15 Thread Chris Boot 
On 15/06/13 04:55, Ben Hutchings wrote:
 On Wed, 2013-06-12 at 19:20 +0200, Carlos Alberto Lopez Perez wrote:
 Source: linux
 Version: 3.9.5-1
 Severity: wishlist


 Please consider enabling X86_INTEL_PSTATE on 3.9 or superior

 This is a new CPU power scaling driver specially optimized for the
 latest Intel CPUs (Sandy Bridge and Ivy Bridge)

 https://lwn.net/Articles/536017/
 
 I don't think it's ready yet.  I'll enable it in experimental though.
 
 Ben.

I agree. I have seen significant performance reductions on my Xeon
E3-1200 server with X86_INTEL_PSTATE enabled, though I admit I don't
have any figures to back this up.

HTH,
Chris

-- 
Chris Boot
deb...@bootc.net
GPG: 1DE8 6AB0 1897 A330 D973  D77C 50DD 5A29 FB09 



signature.asc
Description: OpenPGP digital signature

Bug#699361: linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and, CPU intensive

2013-04-16 Thread Chris Boot 
On 19/03/13 04:13, Ben Hutchings wrote:
 That's good, but I wonder whether this might also needed:
 
 commit 009673b439cf74d70a486fca0177e274febd81a7
 Author: J. Bruce Fields bfie...@redhat.com
 Date:   Mon Nov 7 17:40:10 2011 -0500

[snip]

 (That might also depend on:
 
 commit 16bfdaafa2c66d8cc81422a97a105a849ca65b3e
 Author: J. Bruce Fields bfie...@redhat.com
 Date:   Mon Nov 7 17:23:30 2011 -0500
 

[snip]

 
 though I think they're independent.)
 
 Ben.

We've been running a custom kernel based on
linux-image-3.2.0-0.bpo.4-amd64 3.2.39-2~bpo60+1 with the following
patches applied:

06f1f864d4ae5804e83785308d41f14a08e4b980
[PATCH] nfsd4: hash lockowners to simplify RELEASE_LOCKOWNER

64a284d07c7d84299a90826950079a8ef11e8204
[PATCH 1/1] nfsd4: maintain one seqid stream per (lockowner, file)

This list does not include the two patches you suggested above. For us,
the two patches we have applied have completely fixed the problems we
were experiencing, and the system has been stable for nearly 3 weeks now.

Please consider adding those patches to the Wheezy kernel (admittedly
they probably won't make it now, or at least not until the next point
release).

Best regards,
Chris

-- 
|Chris Boot
|Tiger Computing Ltd
|Linux for Business
|
|Tel: 033 0088 1511
|Web: http://www.tiger-computing.co.uk
|
|Registered in England. Company number: 3389961
|Registered address: Wyastone Business Park,
| Wyastone Leys, Monmouth, NP25 3SR


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/516d28e5.9080...@tiger-computing.co.uk

Bug#699361: linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and, CPU intensive

2013-03-15 Thread Chris Boot 

On 05/03/13 09:36, Chris Boot wrote:

On 03/03/13 01:56, Ben Hutchings wrote:

Control: tag -1 moreinfo fixed-upstream

On Thu, 2013-02-28 at 15:28 +, Chris Boot wrote:

We are also seeing this on an NFS server hosing home directories for a
fairly large deployment of Debian desktop systems. The symptoms and perf
top agree perfectly with what the reporter is experiencing.

Please consider backporting said patch to the 3.2 kernel for
wheezy/squeeze-backports.

Please test the attached backport as explained here:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official

Hi Ben,

I have been testing a 3.2 kernel with both the patch you backported as
well as 64a284d07c7d84299a90826950079a8ef11e8204 from upstream (nfsd4:
maintain one seqid stream per (lockowner, file)). These patches
together appear to have resolved the issues our client has been seeing,
though this is not running in a production environment just yet.

I think the other patch (64a284d07c7d84299a90826950079a8ef11e8204) is
also quite important in resolving this problem, as it reduces the number
of entries in the lockowner hash table. Would this be a patch you would
entertain to backport as well?


Hi Ben,

Did you have any further thoughts about the other patch I mentioned 
above? I still don't have this running in a production environment, but 
the testing I have performed looks good with both patches applied.


Best regards,
Chris

--
|Chris Boot
|Tiger Computing Ltd
|Linux for Business
|
|Tel: 033 0088 1511
|Web: http://www.tiger-computing.co.uk
|
|Registered in England. Company number: 3389961
|Registered address: Wyastone Business Park,
| Wyastone Leys, Monmouth, NP25 3SR


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5143494a.8020...@tiger-computing.co.uk

Bug#699361: linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and, CPU intensive

2013-03-05 Thread Chris Boot 
On 03/03/13 01:56, Ben Hutchings wrote:
 Control: tag -1 moreinfo fixed-upstream
 
 On Thu, 2013-02-28 at 15:28 +, Chris Boot wrote:
 We are also seeing this on an NFS server hosing home directories for a 
 fairly large deployment of Debian desktop systems. The symptoms and perf 
 top agree perfectly with what the reporter is experiencing.

 Please consider backporting said patch to the 3.2 kernel for 
 wheezy/squeeze-backports.
 
 Please test the attached backport as explained here:
 http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official

Hi Ben,

I have been testing a 3.2 kernel with both the patch you backported as
well as 64a284d07c7d84299a90826950079a8ef11e8204 from upstream (nfsd4:
maintain one seqid stream per (lockowner, file)). These patches
together appear to have resolved the issues our client has been seeing,
though this is not running in a production environment just yet.

I think the other patch (64a284d07c7d84299a90826950079a8ef11e8204) is
also quite important in resolving this problem, as it reduces the number
of entries in the lockowner hash table. Would this be a patch you would
entertain to backport as well?

Best regards,
Chris

-- 
|Chris Boot
|Tiger Computing Ltd
|Linux for Business
|
|Tel: 033 0088 1511
|Web: http://www.tiger-computing.co.uk
|
|Registered in England. Company number: 3389961
|Registered address: Wyastone Business Park,
| Wyastone Leys, Monmouth, NP25 3SR



signature.asc
Description: OpenPGP digital signature

Bug#699361: linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and, CPU intensive

2013-02-28 Thread Chris Boot 
We are also seeing this on an NFS server hosing home directories for a 
fairly large deployment of Debian desktop systems. The symptoms and perf 
top agree perfectly with what the reporter is experiencing.


Please consider backporting said patch to the 3.2 kernel for 
wheezy/squeeze-backports.



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/512f77a5.1030...@tiger-computing.co.uk