Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #63707 > unrolled thread

Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?

Back to article view | Back to linux.debian.kernel

Contents

  Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics? "Werner D." <werner@aloah-from-hell.de> - 2019-03-28 15:30 +0100
    Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics? Daniel Lewart <lewart3@gmail.com> - 2019-03-28 17:40 +0100
    Bug#925918: marked as done (linux-image-amd64: linux-image-3.16.0-8-amd64  - unpredictable reboots / kernel panics?) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-04-02 01:00 +0200

#63707 — Bug#925918: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?

Package: linux-image-amd64
Version: linux-image-3.16.0-8-amd64
Severity: important

Dear Maintainer,

after upgrading to the latest linux-image-adm64 on jessie we're experiencing several issues which led us 
to downgrade to linux-image-3.16.0-7-amd64 again and deinstall linux-image-3.16.0-8-amd64. It's happened
until now on a COROSYNC/DRBD Cluster where standby node has been upgraded and after the upgrade the system
froze, see [1]. 

On another MySQL-Slave where we applied this kernel - the system - after running some time rebooted due to
a kernel panic. I wasn't fast enough to catch the kernel panic on the screen as VMware HA-features instantly 
rebooted the system. Both systems run in a VMware HA-Cluster on different ESXi runhosts.

So for me, linux-image-3.16.0-8-amd64 smells fishy and i was wondering if there are other users which have
problems? 

Cheers,
Werner



[1]
Mar 28 13:35:38 nfs02 kernel: [  191.925130] block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0
Mar 28 13:35:38 nfs02 kernel: [  191.927389] block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:40 nfs02 kernel: [  194.306334] drbd r0: Wrong magic value 0x00000000 in protocol version 101
Mar 28 13:35:40 nfs02 kernel: [  194.306407] drbd r0: peer( Primary -> Unknown ) conn( Connected -> ProtocolError ) pdsk( UpToDate -> DUnknown ) 
Mar 28 13:35:40 nfs02 kernel: [  194.306432] drbd r0: asender terminated
Mar 28 13:35:40 nfs02 kernel: [  194.306436] drbd r0: Terminating drbd_a_r0
Mar 28 13:35:40 nfs02 kernel: [  194.306828] drbd r0: Connection closed
Mar 28 13:35:40 nfs02 kernel: [  194.306845] drbd r0: conn( ProtocolError -> Unconnected ) 
Mar 28 13:35:40 nfs02 kernel: [  194.306847] drbd r0: receiver terminated
Mar 28 13:35:40 nfs02 kernel: [  194.306848] drbd r0: Restarting receiver thread
Mar 28 13:35:40 nfs02 kernel: [  194.306850] drbd r0: receiver (re)started
Mar 28 13:35:40 nfs02 kernel: [  194.306860] drbd r0: conn( Unconnected -> WFConnection ) 
Mar 28 13:35:41 nfs02 kernel: [  194.805238] drbd r0: Handshake successful: Agreed network protocol version 101
Mar 28 13:35:41 nfs02 kernel: [  194.805243] drbd r0: Agreed to support TRIM on protocol level
Mar 28 13:35:41 nfs02 kernel: [  194.805274] drbd r0: conn( WFConnection -> WFReportParams ) 
Mar 28 13:35:41 nfs02 kernel: [  194.805277] drbd r0: Starting asender thread (from drbd_r_r0 [1367])
Mar 28 13:35:41 nfs02 kernel: [  194.869215] block drbd0: drbd_sync_handshake:
Mar 28 13:35:41 nfs02 kernel: [  194.869221] block drbd0: self E2641EEB9E133204:0000000000000000:0DD839919AA45372:0DD739919AA45373 bits:0 flags:0
Mar 28 13:35:41 nfs02 kernel: [  194.869225] block drbd0: peer 14F96DC2D3D2E20D:E2641EEB9E133205:0DD839919AA45373:0DD739919AA45373 bits:23 flags:0
Mar 28 13:35:41 nfs02 kernel: [  194.869228] block drbd0: uuid_compare()=-1 by rule 50
Mar 28 13:35:41 nfs02 kernel: [  194.869236] block drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) disk( UpToDate -> Outdated ) pdsk( DUnknown -> UpToDate ) 
Mar 28 13:35:41 nfs02 kernel: [  194.876039] block drbd0: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  194.882431] block drbd0: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  194.882445] block drbd0: conn( WFBitMapT -> WFSyncUUID ) 
Mar 28 13:35:41 nfs02 kernel: [  194.887016] block drbd0: updated sync uuid E2651EEB9E133204:0000000000000000:0DD839919AA45372:0DD739919AA45373
Mar 28 13:35:41 nfs02 kernel: [  194.887489] block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0
Mar 28 13:35:41 nfs02 kernel: [  194.889641] block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:41 nfs02 kernel: [  194.889656] block drbd0: conn( WFSyncUUID -> SyncTarget ) disk( Outdated -> Inconsistent ) 
Mar 28 13:35:41 nfs02 kernel: [  194.889666] block drbd0: Began resync as SyncTarget (will sync 92 KB [23 bits set]).
Mar 28 13:35:41 nfs02 kernel: [  194.900324] drbd r0: Wrong magic value 0x84a1785a in protocol version 101
Mar 28 13:35:41 nfs02 kernel: [  194.900381] drbd r0: peer( Primary -> Unknown ) conn( SyncTarget -> ProtocolError ) pdsk( UpToDate -> DUnknown ) 
Mar 28 13:35:41 nfs02 kernel: [  194.900392] drbd r0: asender terminated
Mar 28 13:35:41 nfs02 kernel: [  194.900394] drbd r0: Terminating drbd_a_r0
Mar 28 13:35:41 nfs02 kernel: [  194.911438] drbd r0: Connection closed
Mar 28 13:35:41 nfs02 kernel: [  194.911456] drbd r0: conn( ProtocolError -> Unconnected ) 
Mar 28 13:35:41 nfs02 kernel: [  194.911458] drbd r0: receiver terminated
Mar 28 13:35:41 nfs02 kernel: [  194.911460] drbd r0: Restarting receiver thread
Mar 28 13:35:41 nfs02 kernel: [  194.911461] drbd r0: receiver (re)started
Mar 28 13:35:41 nfs02 kernel: [  194.911471] drbd r0: conn( Unconnected -> WFConnection ) 
Mar 28 13:35:41 nfs02 kernel: [  195.409791] drbd r0: Handshake successful: Agreed network protocol version 101
Mar 28 13:35:41 nfs02 kernel: [  195.409796] drbd r0: Agreed to support TRIM on protocol level
Mar 28 13:35:41 nfs02 kernel: [  195.409849] drbd r0: conn( WFConnection -> WFReportParams ) 
Mar 28 13:35:41 nfs02 kernel: [  195.409852] drbd r0: Starting asender thread (from drbd_r_r0 [1367])
Mar 28 13:35:41 nfs02 kernel: [  195.429466] block drbd0: drbd_sync_handshake:
Mar 28 13:35:41 nfs02 kernel: [  195.429473] block drbd0: self E2651EEB9E133204:0000000000000000:0DD839919AA45372:0DD739919AA45373 bits:21 flags:0
Mar 28 13:35:41 nfs02 kernel: [  195.429477] block drbd0: peer 14F96DC2D3D2E20D:E2651EEB9E133205:E2641EEB9E133205:0DD839919AA45373 bits:23 flags:0
Mar 28 13:35:41 nfs02 kernel: [  195.429480] block drbd0: uuid_compare()=-1 by rule 50
Mar 28 13:35:41 nfs02 kernel: [  195.429482] block drbd0: Becoming sync target due to disk states.
Mar 28 13:35:41 nfs02 kernel: [  195.429489] block drbd0: peer( Unknown -> Primary ) conn( WFReportParams -> WFBitMapT ) pdsk( DUnknown -> UpToDate ) 
Mar 28 13:35:41 nfs02 kernel: [  195.452578] block drbd0: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  195.459661] block drbd0: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 39(1), total 39; compression: 100.0%
Mar 28 13:35:41 nfs02 kernel: [  195.459677] block drbd0: conn( WFBitMapT -> WFSyncUUID ) 
Mar 28 13:35:41 nfs02 kernel: [  195.465210] block drbd0: updated sync uuid E2661EEB9E133204:0000000000000000:0DD839919AA45372:0DD739919AA45373
Mar 28 13:35:41 nfs02 kernel: [  195.465663] block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0
Mar 28 13:35:41 nfs02 kernel: [  195.467430] block drbd0: helper command: /sbin/drbdadm before-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:41 nfs02 kernel: [  195.467451] block drbd0: conn( WFSyncUUID -> SyncTarget ) 
Mar 28 13:35:41 nfs02 kernel: [  195.467464] block drbd0: Began resync as SyncTarget (will sync 92 KB [23 bits set]).
Mar 28 13:35:41 nfs02 kernel: [  195.486698] block drbd0: Resync done (total 1 sec; paused 0 sec; 92 K/sec)
Mar 28 13:35:41 nfs02 kernel: [  195.486705] block drbd0: updated UUIDs 14F96DC2D3D2E20C:0000000000000000:E2661EEB9E133204:E2651EEB9E133205
Mar 28 13:35:41 nfs02 kernel: [  195.486712] block drbd0: conn( SyncTarget -> Connected ) disk( Inconsistent -> UpToDate ) 
Mar 28 13:35:41 nfs02 kernel: [  195.486980] block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0
Mar 28 13:35:41 nfs02 kernel: [  195.488776] block drbd0: helper command: /sbin/drbdadm after-resync-target minor-0 exit code 0 (0x0)
Mar 28 13:35:44 nfs02 kernel: [  197.913875] BUG: unable to handle kernel NULL pointer dereference at           (null)
Mar 28 13:35:44 nfs02 kernel: [  197.913929] IP: [<ffffffff81157935>] put_page+0x5/0x30
Mar 28 13:35:44 nfs02 kernel: [  197.913961] PGD 0 
Mar 28 13:35:44 nfs02 kernel: [  197.913975] Oops: 0000 [#1] SMP 
Mar 28 13:35:44 nfs02 kernel: [  197.913997] Modules linked in: binfmt_misc vmw_vsock_vmci_transport vsock crc32_pclmul aesni_intel vmw_balloon ppdev evdev aes_x86_64 lrw serio_raw pcspkr gf128mul glue_helper ablk_helper cryptd vmwgfx processor thermal_sys parport_pc parport shpchp ttm drm_kms_helper battery vmw_vmci drm ac button drbd lru_cache libcrc32c crc32c_generic autofs4 ext4 crc16 mbcache jbd2 dm_mod sr_mod cdrom sg ata_generic sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common crc32c_intel psmouse floppy ata_piix libata vmxnet3 vmw_pvscsi i2c_piix4 i2c_core scsi_mod
Mar 28 13:35:44 nfs02 kernel: [  197.914358] CPU: 0 PID: 1367 Comm: drbd_r_r0 Not tainted 3.16.0-8-amd64 #1 Debian 3.16.64-1








We're wondering if any other users have issues with this kernel-release?



*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

Kernel: Linux 3.16.0-7-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[toc] | [next] | [standalone]

#63710

Debian Kernel Team,

WD> So for me, linux-image-3.16.0-8-amd64 smells fishy and i was wondering
WD> if there are other users which have problems?

Yes!  My Jessie MySQL database server updated to linux-image-3.16.0-8-amd64,
rebooted, and crashed within 47 minutes.  Below are the syslog messages.

Please change Severity to "Critical" and merge Bugs #925918 and #925919.

Thank you and good luck!
Dan
-------
Mar 28 07:13:11 bd kernel: [ 2836.042567] mysqld: Corrupted page table
at address 7fae5da486ac
Mar 28 07:13:11 bd kernel: [ 2836.042601] PGD 800000042bf68067 PUD
42be4a067 PMD 42c78a067 PTE 61662d796e616d2d
Mar 28 07:13:11 bd kernel: [ 2836.042628] Bad pagetable: 000d [#1] SMP
Mar 28 07:13:11 bd kernel: [ 2836.042655] Modules linked in: xt_recent
iptable_nat nf_nat_ipv4 xt_comment ipt_REJECT xt_addrtype xt_mark
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ipt_ULOG xt_NFLOG
nfnetlink_log xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp
nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323
nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_nat
nf_conntrack_sane nf_conntrack_tftp nf_conntrac
######

[toc] | [prev] | [next] | [standalone]

#63744 — Bug#925918: marked as done (linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 01 Apr 2019 23:53:01 +0100
with message-id <6eefa25522113e991313dc887231b3f113bf6559.camel@decadent.org.uk>
and subject line Re: linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?
has caused the Debian Bug report #925919,
regarding linux-image-amd64: linux-image-3.16.0-8-amd64 - unpredictable reboots / kernel panics?
to be marked as done.

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

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


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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web