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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

Debian Bug Tracking System
Your message dated Mon, 01 Apr 2019 23:53:01 +0100
with message-id <[hidden email]>
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 [hidden email]
immediately.)


--
925919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925919
Debian Bug Tracking System
Contact [hidden email] with problems

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)

Version: 3.16.64-2

I believe this is fixed, as mentioned in the changelog for 3.16.64-2:

  * [x86] Driver: Vmxnet3: Fix regression caused by 5738a09 (regression
    in 3.16.60) (Closes: #925919)

Ben.

--
Ben Hutchings
Life is what happens to you while you're busy making other plans.
                                                          - John Lennon



signature.asc (849 bytes) Download Attachment