http://bugzilla.suse.com/show_bug.cgi?id=1044294 Johannes Thumshirn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jthumshirn@suse.com Assignee|kernel-maintainers@forge.pr |jthumshirn@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c2 --- Comment #2 from Holger Schranz --- Hello, how to continue with this bug please? Meanwhile, the error occurs in shortest time. An update is available vor Leap to 4.4.72. Should we install this update and restart the test? Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c4 --- Comment #4 from Johannes Thumshirn --- (In reply to Holger Schranz from comment #3)

after some tests I think I have found an important hint: The mutex.c issue occur immediately when a virtual machine, which is connect via fcoe, is destroyed with force by qemu (virsh destroy <vm>). In case of a normal shutdown only a message in der traget system is written to the message file that the rport is blocked for a while, but you can reconnect by the startup/power on of the system.

This hardens my assumption of the VN2VN timeout. I'm working on a test setup to reproduce the issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c6 --- Comment #6 from Johannes Thumshirn --- (In reply to Holger Schranz from comment #5)

Hello Mr. Thumshirn,

thats great. I'm happy that can I help. If you want, I can start a test with a fix from you in parallel. The test environment is already installed.

Can you try booting with a -debug flavor kernel? Maybe we can get more information what's going on with the locking out of it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c8 --- Comment #8 from Holger Schranz --- Hi Johannes, I have to apologize, but I was in action for other issues. So let's continue next week. Anyway, one information: To recreate it is enough to execute the command: fcoeadm -r eth(x) onto the target system. The mutex:97 occur promptly. But I will try to boot with a -debug kernel next wek. Please wait. Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c13 Johannes Thumshirn changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sweet_f_a@gmx.de) --- Comment #13 from Johannes Thumshirn --- (In reply to Ruediger Meier from comment #9)

Seems I have the same issue

[ 72.229523] BUG: sleeping function called from invalid context at ../kernel/locking/mutex.c:97 [ 72.229538] in_atomic(): 1, irqs_disabled(): 0, pid: 2387, name: mdadm [ 72.229544] CPU: 2 PID: 2387 Comm: mdadm Not tainted 4.4.73-18.17-default #1 [ 72.229547] Hardware name: LENOVO 346034G/346034G, BIOS G6ETB5WW (2.75 ) 09/01/2016

I can reproduce it 100%, but only on that Lenovo machine above not on Qemu (I haven't tested other real machines yet.)

For me this kernel needs to run to trigger the bug: kernel-default-4.4.73-18.17.1.x86_64

The previous kernel 4.4.72 works

I run util-linux test-suite:

$ cd util-linux/ $ make -j4 fdisk blkid losetup $ sudo ./tests/ts/blkid/md-raid1-whole

Mostly the system freezes completely.

Do I understand you correctly that there is no FCoE involved? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 Björn Voigt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjoernv@arcor.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 Ruediger Meier changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sweet_f_a@gmx.de) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c21 --- Comment #21 from Holger Schranz --- Created attachment 732515 --> http://bugzilla.suse.com/attachment.cgi?id=732515&action=edit /var/log/message second -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c23 --- Comment #23 from Holger Schranz --- Hi Johannes, sorry for the long delay. I have reproduce the phenomena with a debug kernel. I have 2 /var/log/message from 2 different system. But always the same configuration: 3 Virtual System : One Target-VM (involved system) 2 Initiator-VM's. After a first/second investigation in the /var/log/messages (started in DEC/2016) the error occoured many times: 1) In many cases when the startup of the FC[oE] by read the config file from lio 2) Always when the Initator VM system stopped with virsh destroy <name> 3) A additional issue found by last week and today: The config file for the disk scsi.target.lio is overwritten (also attached). 4) If the problem occur the shutdown of the system (init 0) needs 12 minutes minimum and stop with messages from dracut (some times). The original config file for scsi_target_lio i will send in next time. I you want (and may be it is more helpful) we can held a Skype-Session to start an online investigation onto the involved system(s). I believe this make more sense. Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c25 --- Comment #25 from Holger Schranz --- Hi Johannes, sorry for so many comments. Today morning I have reproduce the issue about mutex.97. Please forget the /var/log/messages from 2017-07-15 ... I believe it is to much. The new information is done from 3 systems .. all have the same behavior. But all 3 system was started with the debug kernel. What is strange (in my case) the mutex issue occure always during the startup first. As written in the old information: Later the problem occur in the runnig sessions when one of the two initiator is stopped (destroyed). All three diagnose files contain: 1) hostnamctl 2) /var/log/messages (reduced to the last occourence) 3) iscsi-lio config 4) targetcli ls Best regards Holger P.s.: The overwritten scsi_target_lio behavior in the comments before is further opend. To compare the correct the scsi_target_lio please use the config file from here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c27 --- Comment #27 from Holger Schranz --- Created attachment 732519 --> http://bugzilla.suse.com/attachment.cgi?id=732519&action=edit summary of diagnose informatiom form VM M3 content see M1 please -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c29 --- Comment #29 from Holger Schranz --- Any news please? How is the status? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c31 Johannes Thumshirn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |holger@fam-schranz.de Flags| |needinfo?(holger@fam-schran | |z.de) --- Comment #31 from Johannes Thumshirn --- Holger, you're running an MD RAID here, don't you? A colleague of mine mentioned it has nothing to do with FCoE but MD and he already has a fix: https://build.opensuse.org/project/monitor?project=home%3Amorbidrsa%3Absc104... Should be done in some minutes for you to try. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c33 --- Comment #33 from Johannes Thumshirn --- (In reply to Holger Schranz from comment #32)

Please wait for a while.

No problem, I'll be on vacation the next two weeks anyways. Hoping to read good news when I'm back :-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c35 --- Comment #35 from Holger Schranz --- Hi Johannes, about this issue I have try to find an easy method to recreate and now I think I have found it: Use the ethtool and change the settings. Each usage of the ethtool to the FCoE used interfaces run into this problem. An example: eth2/eth3 are assign to FCoE ethtool -s eth2 autoneg off speed 100 duplex full and the problem occure Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c37 --- Comment #37 from Johannes Thumshirn --- (In reply to Holger Schranz from comment #35)

Hi Johannes,

about this issue I have try to find an easy method to recreate and now I think I have found it:

Use the ethtool and change the settings. Each usage of the ethtool to the FCoE used interfaces run into this problem.

An example: eth2/eth3 are assign to FCoE

ethtool -s eth2 autoneg off speed 100 duplex full

and the problem occure

Best regards

Holger

Just for confirmation, did you try the kernel from comment 31? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c39 --- Comment #39 from Holger Schranz --- At the moment I try to get the fix. Which sources I have to download and compile please? To create a new kernel. Best regards Holger P.s.: I asked some people to help about the link in the comment 31. Sorry but nobody is fit with the build-service .... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c41 --- Comment #41 from Holger Schranz --- Johannes, should I install an 42.2 original and adapt the modifyed kernel for MD for a test? Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c43 --- Comment #43 from Holger Schranz --- Hi Johannes, I have start the reproduction. Unfortunately it occurs again. See the Hardcopy. It is done with the newest kernel I got from the update. Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c45 --- Comment #45 from Johannes Thumshirn --- Created attachment 742989 --> http://bugzilla.suse.com/attachment.cgi?id=742989&action=edit proposed patch Holger, can you try above patch? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c47 --- Comment #47 from Johannes Thumshirn --- (In reply to Holger Schranz from comment #46)

Hi Johannes,

Sorry for the late reaction. I was in vacation and back today. I will try it latest tomorrow.

No problem, thanks a lot -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c50 --- Comment #50 from Holger Schranz --- Hello Johannes, please forget my comment #48. This was a mistake. About the patch you wrote in . It is possible to get this in a file? Meanwhile we update the system to 4.4.90-18.32.

From my point of view it looks better. A reboot with reconnect runs in 95% without problems. A hard broken (Crash of the Initator system) runs into the same behavior (a picture will be upload in parallel). Also the test which I have described in comment #35 occourd further. But his can be, because I don't use the patch from you.

About a description ... sorry ... it is a huge description and need a longer time. Short: The "RAID"-System is a LEAP 42.2 virtual system. There are 5 files via QEMU configured as HDD's. This 5 files are described as HDD's-RAID via tgtd. this is necessary because of VPD which we need. This internally mapped and forward to FCoE RAID:~ # lsscsi -g [0:0:0:0] disk LSI MR SAS 6G 1GB 2.5+ /dev/sda /dev/sg0 [1:0:0:1] disk QEMU QEMU HARDDISK 2.5+ /dev/sdf /dev/sg5 [1:0:0:2] disk QEMU QEMU HARDDISK 2.5+ /dev/sde /dev/sg4 [1:0:0:3] disk QEMU QEMU HARDDISK 2.5+ /dev/sdd /dev/sg3 [1:0:0:4] disk QEMU QEMU HARDDISK 2.5+ /dev/sdc /dev/sg2 [1:0:0:15] disk QEMU QEMU HARDDISK 2.5+ /dev/sdb /dev/sg1 [4:0:0:0] cd/dvd QEMU QEMU DVD-ROM 2.5+ /dev/sr0 /dev/sg6 [10:0:0:0] storage IET Controller 0001 - /dev/sg7 [10:0:0:1] disk FUJITSU ETERNUS_DXL 0000 /dev/sdi /dev/sg11 [10:0:0:2] disk FUJITSU ETERNUS_DXL 0000 /dev/sdk /dev/sg13 [10:0:0:3] disk FUJITSU ETERNUS_DXL 0000 /dev/sdm /dev/sg15 [10:0:0:4] disk FUJITSU ETERNUS_DXL 0000 /dev/sdo /dev/sg17 [10:0:0:15] disk FUJITSU ETERNUS_DXL 0000 /dev/sdp /dev/sg18 [11:0:0:0] storage IET Controller 0001 - /dev/sg8 [11:0:0:1] disk FUJITSU ETERNUS_DXL 0000 /dev/sdg /dev/sg9 [11:0:0:2] disk FUJITSU ETERNUS_DXL 0000 /dev/sdh /dev/sg10 [11:0:0:3] disk FUJITSU ETERNUS_DXL 0000 /dev/sdj /dev/sg12 [11:0:0:4] disk FUJITSU ETERNUS_DXL 0000 /dev/sdl /dev/sg14 [11:0:0:15] disk FUJITSU ETERNUS_DXL 0000 /dev/sdn /dev/sg16 RAID:~ # The first part is for QEMU the next 2 parts are for tgtd because of a 2 way connection. Both 10:0:0:15 and 11:0:0:15 are connect to 1:0:0:15 Present to FCoE is via lio/targetcli. I hope you are not so confused. Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c52 --- Comment #52 from Vladimir Anufriev --- 4.4.90-18.32-default works well with ocfs2. There is no previous mentioned bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c53 --- Comment #53 from Johannes Thumshirn --- Holger, I incorporated the patch into 42.2 and a test package will appear shortly here: https://build.opensuse.org/project/monitor?project=home%3Amorbidrsa%3Abranch... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c56 --- Comment #56 from Holger Schranz --- Hi Johannes, Ralf, meanwhile I have closed the test with Leap 42.3 and the fix proposal from Ralf. The result is o.k.. A normal reboot/shutdown also a hard stop (Poweroff / virsh destroy) of the Initiater systems (SLES11SP4/SLSES12SP2) doesn't shown the abnormal behavior which is reported. @Johannes: There are any further tests necessary to confirm? What is the next step please? At the moment I build my own kernel based on Leap 42.3. and the fix from Ralf. It is planed to takeover the fix from Ralf? When can I expect the fix, so it is no longer necessary to build my own kernel? Thanks anyone for the effort to solve this issue! Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c58 --- Comment #58 from Johannes Thumshirn --- (In reply to Holger Schranz from comment #57)

Hello @ all,

after some times now I can say it runs more stable than before with proposal of a fix from Ralf.

A similar issue occured after an timeout onto a connection after 500 sec.. A very rare situation.

How to continue with this issue now? What about the proposal for a fix from Ralf?

Ralf, can you please send to patch upstream (to the linux-scsi mailing-list the open-fcoe list is defunct). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c60 --- Comment #60 from Holger Schranz --- Hi Johannes, what is the next action for this issue? About the rare behavior (timeout 480 sec) it seems with last update to kernel 4.4.114 it occurs from time to time. Meanwhile also Ralf has continue the investigation and will write an additional comment. It would be nice if we get any information in next time. Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c62 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #742989|0 |1 is obsolete| | --- Comment #62 from Hannes Reinecke --- Created attachment 763809 --> http://bugzilla.suse.com/attachment.cgi?id=763809&action=edit 0001-scsi-fc-fcoe-don-t-hold-RCU-lock-when-doing-a-fc-rport.patch scsi: fc/fcoe: don't hold RCU lock when doing a fc_rport_{login,logoff] -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c64 --- Comment #64 from Holger Schranz --- Hallo Mr. Reinecke: I have download the patch and execute it. After that I build the kernel new. Restart the VM with the new kernel: Result: Black Screen at the start up and 100% CPU Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c66 --- Comment #66 from Holger Schranz --- Hello any news for this issue? Nice greetings Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c69 Johannes Thumshirn changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jthumshirn@suse.com |hare@suse.com --- Comment #69 from Johannes Thumshirn --- Hannes has been the last one working on it, reassigning -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c71 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #763809|0 |1 is obsolete| | --- Comment #71 from Hannes Reinecke --- Created attachment 776100 --> http://bugzilla.suse.com/attachment.cgi?id=776100&action=edit 0001-libfc-fixup-sleeping-function-called-from-invalid.patch libfc: fixup 'sleeping function called from invalid context' -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c73 --- Comment #73 from Holger Schranz --- Hello Mr. Reinecke, sorry for the question ... is this patch for Leap 42.3? Because, if I compare the source lines it isn't the same Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c75 --- Comment #75 from Holger Schranz --- Created attachment 776133 --> http://bugzilla.suse.com/attachment.cgi?id=776133&action=edit Test after changes in libfc/fc_disk.c Hello Mr. Reinecke, after rebuild and start the system I have done a first check. The result please see the screenshot (Attachment). Any additional material necessary? Nice greetings Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c77 --- Comment #77 from Holger Schranz --- Created attachment 776428 --> http://bugzilla.suse.com/attachment.cgi?id=776428&action=edit FCoE test with a fix from Mr. Reinecke Hello Mr. Reinecke, I stopped the test for the fix because the problem occurs further. For investigation I have upload the journal file from one of the involved systems. The problem occuers on: Jul 08 16:45:20 Jul 08 16:53:20 Jul 08 17:01:20 Jul 08 17:09:20 Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c79 --- Comment #79 from Hannes Reinecke --- I have posted a patchset on the linux-scsi mailing list (check for 'libfc/fcoe: disc_mutex fixes' and the follow-up fixes) which have since been accepted upstream. Can you check if thses patches solve your issue, too? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c81 --- Comment #81 from Holger Schranz --- Created attachment 783257 --> http://bugzilla.suse.com/attachment.cgi?id=783257&action=edit fcoe_ctlr_timer_work [libfcoe] crash with kernel Linux version 4.4.155-68-default Hello Mr. Reinecke, today morning I get the new distribution of Leap 42.3: Linux version 4.4.155-68-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP Tue Sep 11 13:07:19 UTC 2018 (4ecc783) I saw it contains your changes in the scsi environment. Result of the first test: Sep 17 07:26:04 RAID kernel: BUG: sleeping function called from invalid context at ../kernel/locking/mutex.c:97 Sep 17 07:26:04 RAID kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 19, name: kworker/2:0 Sep 17 07:26:04 RAID kernel: CPU: 2 PID: 19 Comm: kworker/2:0 Not tainted 4.4.155-68-default #1 Sep 17 07:26:04 RAID kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org 04/01/2014 Sep 17 07:26:04 RAID kernel: Workqueue: events fcoe_ctlr_timer_work [libfcoe] Sep 17 07:26:04 RAID kernel: 0000000000000000 ffffffff81346687 ffff88006878bc48 ffff88006878bc48 Sep 17 07:26:04 RAID kernel: ffffffff81642d6c ffff88006878bc00 ffffffffa0094971 ffff88006878bc00 Sep 17 07:26:04 RAID kernel: ffff8801775c34e0 000000010001d71e ffff88007a34e838 ffffffffa00afabe Sep 17 07:26:04 RAID kernel: Call Trace: Sep 17 07:26:04 RAID kernel: [<ffffffff8101a049>] dump_trace+0x59/0x350 Sep 17 07:26:04 RAID kernel: [<ffffffff8101a43a>] show_stack_log_lvl+0xfa/0x180 Sep 17 07:26:04 RAID kernel: [<ffffffff8101b201>] show_stack+0x21/0x40 Sep 17 07:26:04 RAID kernel: [<ffffffff81346687>] dump_stack+0x5c/0x85 Sep 17 07:26:04 RAID kernel: [<ffffffff81642d6c>] mutex_lock+0x1c/0x38 Sep 17 07:26:04 RAID kernel: [<ffffffffa0094971>] fc_rport_logoff+0x21/0xf0 [libfc] Sep 17 07:26:04 RAID kernel: [<ffffffffa00afabe>] fcoe_ctlr_timer_work+0x6ae/0xc10 [libfcoe] Sep 17 07:26:04 RAID kernel: [<ffffffff8109dd0b>] process_one_work+0x15b/0x450 Sep 17 07:26:04 RAID kernel: [<ffffffff8109e8d6>] worker_thread+0x116/0x4c0 Sep 17 07:26:04 RAID kernel: [<ffffffff810a3f34>] kthread+0xd4/0xf0 Sep 17 07:26:04 RAID kernel: [<ffffffff81645a55>] ret_from_fork+0x55/0x80 Sep 17 07:26:04 RAID kernel: DWARF2 unwinder stuck at ret_from_fork+0x55/0x80 Sep 17 07:26:04 RAID kernel: Sep 17 07:26:04 RAID kernel: Leftover inexact backtrace: Sep 17 07:26:04 RAID kernel: [<ffffffff810a3e60>] ? kthread_park+0x50/0x50 Sep 17 07:26:16 RAID kernel: Process accounting resumed The complete journal I have attached. If you need any additional material please let me know. Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c83 --- Comment #83 from Holger Schranz --- Hello, moved from 15.0 to 15.1 ... seems the same situation. No message shown , but the hang situation is given. Best regards Holger Schranz -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1044294 http://bugzilla.suse.com/show_bug.cgi?id=1044294#c85 Tomáš Chvátal changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WONTFIX --- Comment #85 from Tomáš Chvátal --- This is automated batch bugzilla cleanup. The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please feel free to reopen this bug against that version (!you must update the "Version" component in the bug fields, do not just reopen please), or alternatively create a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -- You are receiving this mail because: You are on the CC list for the bug.