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

2019-03-28 Thread Werner D.
Package: linux-image-amd64
Version: linux-image-3.16.0-8-amd64
Severity: important

Dear Maintainer,

here we go again, i hope this time we get a bug nummer for this report :) 

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 
0x 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::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::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

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

2019-03-28 Thread Werner D.
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 
0x 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::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::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 -> 

Bug#416662: same here

2008-10-08 Thread Werner D.
Hi,

same her on my test-system. Module ist not loaded bei
the init-script.

Regards,
Werner



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]