Led control BUG: scheduling while atomic:

Led control BUG: scheduling while atomic:

Postby vesas » Wed Aug 29, 2018 4:10 pm

Hi,

Led control has some issues with Lacie NS vs2 lite. Led on/off is inverted and dmesg get these:

Code: Select all
[ 1842.155422] note: led[2469] exited with preempt_count 1
[ 1845.695476] BUG: scheduling while atomic: led/2504/0x00000002
[ 1845.701212] Modules linked in: iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi usblp usb_storage ehci_orion ehci_hcd
[ 1845.712190] Preemption disabled at:[<c050d31c>] ns2l_led_set_mode+0x20/0xa8
[ 1845.719147]
[ 1845.720642] CPU: 0 PID: 2504 Comm: led Tainted: G        W       4.6.6 #7
[ 1845.727400] Hardware name: LaCie Network Space Lite v2
[ 1845.732543] [<c0019a98>] (unwind_backtrace) from [<c0016814>] (show_stack+0x10/0x14)
[ 1845.740278] [<c0016814>] (show_stack) from [<c003ea60>] (__schedule_bug+0x90/0xb8)
[ 1845.747832] [<c003ea60>] (__schedule_bug) from [<c06c0a80>] (__schedule+0x5c/0x438)
[ 1845.755466] [<c06c0a80>] (__schedule) from [<c06c0f08>] (schedule+0xac/0xc4)
[ 1845.762500] [<c06c0f08>] (schedule) from [<c0016448>] (do_work_pending+0x24/0xc4)
[ 1845.769972] [<c0016448>] (do_work_pending) from [<c0013708>] (slow_work_pending+0xc/0x20)
[ 1853.728130] BUG: scheduling while atomic: led/2606/0x00000002
[ 1853.733864] Modules linked in: iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi usblp usb_storage ehci_orion ehci_hcd
[ 1853.744843] Preemption disabled at:[<c050d31c>] ns2l_led_set_mode+0x20/0xa8
[ 1853.751805]
[ 1853.753302] CPU: 0 PID: 2606 Comm: led Tainted: G        W       4.6.6 #7
[ 1853.760060] Hardware name: LaCie Network Space Lite v2
[ 1853.765204] [<c0019a98>] (unwind_backtrace) from [<c0016814>] (show_stack+0x10/0x14)
[ 1853.772938] [<c0016814>] (show_stack) from [<c003ea60>] (__schedule_bug+0x90/0xb8)
[ 1853.780492] [<c003ea60>] (__schedule_bug) from [<c06c0a80>] (__schedule+0x5c/0x438)
[ 1853.788125] [<c06c0a80>] (__schedule) from [<c06c0f08>] (schedule+0xac/0xc4)
[ 1853.795158] [<c06c0f08>] (schedule) from [<c0016448>] (do_work_pending+0x24/0xc4)
[ 1853.802623] [<c0016448>] (do_work_pending) from [<c0013708>] (slow_work_pending+0xc/0x20)
[ 1853.892124] note: led[2609] exited with preempt_count 1
[ 1860.722214] note: led[2645] exited with preempt_count 1


What behaviour red led should be? Currently red is off and blue sometimes blinks.
vesas
 
Posts: 7
Joined: Fri Aug 24, 2018 5:40 am

Re: Led control BUG: scheduling while atomic:

Postby vesas » Sat Oct 13, 2018 4:52 pm

Hi,

it seems that this led bug is fixed in fvdw-sl-17.0-update-kernel-21mar2018.zip. Bug is in 17.0 with latest patches. So release notes for kernel update is not correct, for Network Sapce2 lite it also fixes led driver crash.
vesas
 
Posts: 7
Joined: Fri Aug 24, 2018 5:40 am

Re: Led control BUG: scheduling while atomic:

Postby Jocko » Sat Oct 13, 2018 5:06 pm

Hi vesas

Thank you for your feedback but it is amazing. :scratch

Indeed, the required fix has just been identified by fvdw this morning!

The bug should be present also on kernel version 3.14.2
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Led control BUG: scheduling while atomic:

Postby fvdw » Sat Oct 13, 2018 5:09 pm

Hi, it is a kernel bug.
We traced the problem an have a solution (modify led driver). As such a recompiled kernel is required. It will become available in next firmware upgrade. If someone wants it earlier please let us know

Ps the current kernel doesn't crash only spit out this error message.

Code: Select all
 BUG: scheduling while atomic: led/2606/0x00000002


Just switch off and on the led via web interface and check dmesg you will see the error message
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands


Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: Bing Bot and 7 guests