Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
On Tue, May 17, 2016 at 12:12 PM, Ming Lei wrote:
> On Mon, May 16, 2016 at 5:25 PM, Ming Lei wrote:
>> On Fri, May 13, 2016 at 7:22 AM, dann frazier
>> wrote:
>>> I used ftrace to do some duration measuring of the timer function
>>> fb_flashcursor(). I noticed several places where this timer takes around
>>> 98 ms to complete. This time seems to be due to multiple calls to
>>> __memcpy_toio() in ast_dirty_update():
>>>
>>> for (i = y; i <= y2; i++) {
>>> /* assume equal stride for now */
>>> src_offset = dst_offset = i * afbdev->afb.base.pitches[0] +
>>> (x * bpp);
>>> memcpy_toio(bo->kmap.virtual + src_offset, afbdev->sysram +
>>> src_offset, (x2 - x + 1) * bpp);
>>>
>>>
>>> My theory is that this is causing mod_timer() to block on the other CPU,
>>> resulting in the soft lockup.
>>>
>>> Also - I built a custom d-i using pristine 4.6-rc7, and I am able to
>>> easily reproduce this. I think the next step here is to report this to
>>> upstream.
>>
>> Hi Dann,
>>
>> Andrew asked me to take a look at the issue, and from my tracing,
>> most of times, the cpu 'hangs' in the following line of code:
>>
>> __mod_timer():
>>
>> out_unlock:
>> spin_unlock_irqrestore(&base->lock, flags);
>>
>> If I added two trace points around the above line, most of times only
>> the trace point before the line is dumped, and the one after the line
>> can't dumped.
>
> Looks the above issue is caused by passing 'jiffies' to mod_timer,
> and 'ops->cur_blink_jiffies' is observed as zero in cursor_timer_handler()
> when the issue happened.
>
> The following patch(workaround) can make the issue disappeared:
>
> diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
> index 6e92917..5e880ee 100644
> --- a/drivers/video/console/fbcon.c
> +++ b/drivers/video/console/fbcon.c
> @@ -1095,6 +1095,8 @@ static void fbcon_init(struct vc_data *vc, int init)
> con_copy_unimap(vc, svc);
>
> ops = info->fbcon_par;
> + if (vc->vc_cur_blink_ms)
oops, it should be 'if (!vc->vc_cur_blink_ms)'
> + vc->vc_cur_blink_ms = 125;
> ops->cur_blink_jiffies = msecs_to_jiffies(vc->vc_cur_blink_ms);
> p->con_rotate = initial_rotation;
> set_blitting_type(vc, info);
>
> Thanks,
>
>>
>> Thanks,
>>
>>>
>>> --
>>> You received this bug notification because you are subscribed to linux
>>> in Ubuntu.
>>> https://bugs.launchpad.net/bugs/1574814
>>>
>>> Title:
>>> ThunderX: soft lockup in cursor_timer_handler() Edit
>>>
>>> Status in linux package in Ubuntu:
>>> Confirmed
>>>
>>> Bug description:
>>> I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso
>>> via virtual media:
>>>
>>> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>>>
>>> During boot I observed the following lockup on the serial console:
>>>
>>> [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using
>>> xhci_hcd
>>> [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s!
>>> [swapper/14:0]
>>> [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E)
>>> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E)
>>> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E)
>>> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
>>> [ 84.922749]
>>> [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E
>>> 4.4.0-21-generic #37-Ubuntu
>>> [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
>>> [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti:
>>> 801f6c9e8000
>>> [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
>>> [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
>>> [ 84.922778] pc : [] lr : [] pstate:
>>> 00400145
>>> [ 84.922781] sp : 801f6c9ebc20
>>> [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
>>> [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
>>> [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
>>> [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
>>> [ 84.922802] x21: 0100 x20: 8000f94398d8
>>> [ 84.922807] x19: 8000f9439800 x18: c76a5358
>>> [ 84.922811] x17: 97bbd2a8 x16: 802a5040
>>> [ 84.922816] x15: 3e4cf1e0 x14: 0008
>>> [ 84.922820] x13: x12: 003d0900
>>> [ 84.922824] x11: 003d0900 x10: 8090f200
>>> [ 84.922829] x9 : 3d09 x8 : 000e
>>> [ 84.922833] x7 : 801f7b3c5008 x6 :
>>> [ 84.922837] x5 : x4 : 0001
>>> [ 84.922842] x3 : x2 : 801f6c899e05
>>> [ 84.922846] x1 : 801f667d99e0 x0 :
>>> [ 84.922850]
>>> [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using
>>> xhci_hcd
>>> [ 101.180375] usb 1-1.1: reset high-spee
Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
On Mon, May 16, 2016 at 5:25 PM, Ming Lei wrote:
> On Fri, May 13, 2016 at 7:22 AM, dann frazier
> wrote:
>> I used ftrace to do some duration measuring of the timer function
>> fb_flashcursor(). I noticed several places where this timer takes around
>> 98 ms to complete. This time seems to be due to multiple calls to
>> __memcpy_toio() in ast_dirty_update():
>>
>> for (i = y; i <= y2; i++) {
>> /* assume equal stride for now */
>> src_offset = dst_offset = i * afbdev->afb.base.pitches[0] +
>> (x * bpp);
>> memcpy_toio(bo->kmap.virtual + src_offset, afbdev->sysram +
>> src_offset, (x2 - x + 1) * bpp);
>>
>>
>> My theory is that this is causing mod_timer() to block on the other CPU,
>> resulting in the soft lockup.
>>
>> Also - I built a custom d-i using pristine 4.6-rc7, and I am able to
>> easily reproduce this. I think the next step here is to report this to
>> upstream.
>
> Hi Dann,
>
> Andrew asked me to take a look at the issue, and from my tracing,
> most of times, the cpu 'hangs' in the following line of code:
>
> __mod_timer():
>
> out_unlock:
> spin_unlock_irqrestore(&base->lock, flags);
>
> If I added two trace points around the above line, most of times only
> the trace point before the line is dumped, and the one after the line
> can't dumped.
Looks the above issue is caused by passing 'jiffies' to mod_timer,
and 'ops->cur_blink_jiffies' is observed as zero in cursor_timer_handler()
when the issue happened.
The following patch(workaround) can make the issue disappeared:
diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index 6e92917..5e880ee 100644
--- a/drivers/video/console/fbcon.c
+++ b/drivers/video/console/fbcon.c
@@ -1095,6 +1095,8 @@ static void fbcon_init(struct vc_data *vc, int init)
con_copy_unimap(vc, svc);
ops = info->fbcon_par;
+ if (vc->vc_cur_blink_ms)
+ vc->vc_cur_blink_ms = 125;
ops->cur_blink_jiffies = msecs_to_jiffies(vc->vc_cur_blink_ms);
p->con_rotate = initial_rotation;
set_blitting_type(vc, info);
Thanks,
>
> Thanks,
>
>>
>> --
>> You received this bug notification because you are subscribed to linux
>> in Ubuntu.
>> https://bugs.launchpad.net/bugs/1574814
>>
>> Title:
>> ThunderX: soft lockup in cursor_timer_handler() Edit
>>
>> Status in linux package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via
>> virtual media:
>>
>> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>>
>> During boot I observed the following lockup on the serial console:
>>
>> [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
>> [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s!
>> [swapper/14:0]
>> [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E)
>> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E)
>> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E)
>> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
>> [ 84.922749]
>> [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic
>> #37-Ubuntu
>> [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
>> [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti:
>> 801f6c9e8000
>> [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
>> [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
>> [ 84.922778] pc : [] lr : [] pstate:
>> 00400145
>> [ 84.922781] sp : 801f6c9ebc20
>> [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
>> [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
>> [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
>> [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
>> [ 84.922802] x21: 0100 x20: 8000f94398d8
>> [ 84.922807] x19: 8000f9439800 x18: c76a5358
>> [ 84.922811] x17: 97bbd2a8 x16: 802a5040
>> [ 84.922816] x15: 3e4cf1e0 x14: 0008
>> [ 84.922820] x13: x12: 003d0900
>> [ 84.922824] x11: 003d0900 x10: 8090f200
>> [ 84.922829] x9 : 3d09 x8 : 000e
>> [ 84.922833] x7 : 801f7b3c5008 x6 :
>> [ 84.922837] x5 : x4 : 0001
>> [ 84.922842] x3 : x2 : 801f6c899e05
>> [ 84.922846] x1 : 801f667d99e0 x0 :
>> [ 84.922850]
>> [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using
>> xhci_hcd
>> [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using
>> xhci_hcd
>> [ 101.342677] random: nonblocking pool is initialized
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions
--
You re
Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
On Fri, May 13, 2016 at 7:22 AM, dann frazier
wrote:
> I used ftrace to do some duration measuring of the timer function
> fb_flashcursor(). I noticed several places where this timer takes around
> 98 ms to complete. This time seems to be due to multiple calls to
> __memcpy_toio() in ast_dirty_update():
>
> for (i = y; i <= y2; i++) {
> /* assume equal stride for now */
> src_offset = dst_offset = i * afbdev->afb.base.pitches[0] +
> (x * bpp);
> memcpy_toio(bo->kmap.virtual + src_offset, afbdev->sysram +
> src_offset, (x2 - x + 1) * bpp);
>
>
> My theory is that this is causing mod_timer() to block on the other CPU,
> resulting in the soft lockup.
>
> Also - I built a custom d-i using pristine 4.6-rc7, and I am able to
> easily reproduce this. I think the next step here is to report this to
> upstream.
Hi Dann,
Andrew asked me to take a look at the issue, and from my tracing,
most of times, the cpu 'hangs' in the following line of code:
__mod_timer():
out_unlock:
spin_unlock_irqrestore(&base->lock, flags);
If I added two trace points around the above line, most of times only
the trace point before the line is dumped, and the one after the line
can't dumped.
Thanks,
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1574814
>
> Title:
> ThunderX: soft lockup in cursor_timer_handler() Edit
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via
> virtual media:
>
> http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso
>
> During boot I observed the following lockup on the serial console:
>
> [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
> [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s!
> [swapper/14:0]
> [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E)
> usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E)
> drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E)
> ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
> [ 84.922749]
> [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic
> #37-Ubuntu
> [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
> [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti:
> 801f6c9e8000
> [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
> [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
> [ 84.922778] pc : [] lr : [] pstate:
> 00400145
> [ 84.922781] sp : 801f6c9ebc20
> [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
> [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
> [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
> [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
> [ 84.922802] x21: 0100 x20: 8000f94398d8
> [ 84.922807] x19: 8000f9439800 x18: c76a5358
> [ 84.922811] x17: 97bbd2a8 x16: 802a5040
> [ 84.922816] x15: 3e4cf1e0 x14: 0008
> [ 84.922820] x13: x12: 003d0900
> [ 84.922824] x11: 003d0900 x10: 8090f200
> [ 84.922829] x9 : 3d09 x8 : 000e
> [ 84.922833] x7 : 801f7b3c5008 x6 :
> [ 84.922837] x5 : x4 : 0001
> [ 84.922842] x3 : x2 : 801f6c899e05
> [ 84.922846] x1 : 801f667d99e0 x0 :
> [ 84.922850]
> [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
> [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
> [ 101.342677] random: nonblocking pool is initialized
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574814
Title:
ThunderX: soft lockup in cursor_timer_handler() Edit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
On Tue, May 3, 2016 at 1:14 PM, Radha Mohan Chintakuntla wrote: > Ming, > The "-I" option of tcpdump is monitoring mode typically applicable only to > wifi interfaces. So even if you run it on Thunder's NIC interfaces it will > return saying that this is not supported. > Even without the '-I', the issue still can be triggered. > And BTW, what is eth7 ? > >From 16.04 release all interfaces are coming up as "enP2x" Yeah, maybe this box isn't shipped with 16.04, and its kernel is ubuntu@arm64:~$ uname -a Linux arm64 4.2.0 #2 SMP Mon Dec 14 04:01:19 CST 2015 aarch64 aarch64 aarch64 GNU/Linux but the log is very similar with Dann's report: [337056.617650] PC is at _raw_spin_unlock_irqrestore+0x30/0x40 [337056.617657] LR is at mod_timer+0x110/0x238 > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1574814 > > Title: > ThunderX: soft lockup in cursor_timer_handler() Edit > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via > virtual media: > > http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso > > During boot I observed the following lockup on the serial console: > > [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd > [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! > [swapper/14:0] > [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) > usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) > drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) > ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E) > [ 84.922749] > [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic > #37-Ubuntu > [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT) > [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: > 801f6c9e8000 > [ 84.922771] PC is at cursor_timer_handler+0x30/0x58 > [ 84.922775] LR is at cursor_timer_handler+0x30/0x58 > [ 84.922778] pc : [] lr : [] pstate: > 00400145 > [ 84.922781] sp : 801f6c9ebc20 > [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8 > [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8 > [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00 > [ 84.922798] x23: 801f667d9800 x22: 804ec4c0 > [ 84.922802] x21: 0100 x20: 8000f94398d8 > [ 84.922807] x19: 8000f9439800 x18: c76a5358 > [ 84.922811] x17: 97bbd2a8 x16: 802a5040 > [ 84.922816] x15: 3e4cf1e0 x14: 0008 > [ 84.922820] x13: x12: 003d0900 > [ 84.922824] x11: 003d0900 x10: 8090f200 > [ 84.922829] x9 : 3d09 x8 : 000e > [ 84.922833] x7 : 801f7b3c5008 x6 : > [ 84.922837] x5 : x4 : 0001 > [ 84.922842] x3 : x2 : 801f6c899e05 > [ 84.922846] x1 : 801f667d99e0 x0 : > [ 84.922850] > [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd > [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd > [ 101.342677] random: nonblocking pool is initialized > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574814 Title: ThunderX: soft lockup in cursor_timer_handler() Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
On Tue, May 3, 2016 at 10:35 AM, dann frazier wrote: > On Fri, Apr 29, 2016 at 2:06 AM, Ming Lei <1574...@bugs.launchpad.net> wrote: >> It can be triggered 100% by running 'tcpdump -I ethX'. > > Thanks Ming. I let that run for a few hours, but was unable to > reproduce. Are you seeing the same traceback along w the softlockup > msg? Yes, it can be always triggered by 'tcpdump -I eth7' on cvm13. > >-dann > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1574814 > > Title: > ThunderX: soft lockup in cursor_timer_handler() Edit > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via > virtual media: > > http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso > > During boot I observed the following lockup on the serial console: > > [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd > [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! > [swapper/14:0] > [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) > usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) > drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) > ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E) > [ 84.922749] > [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic > #37-Ubuntu > [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT) > [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: > 801f6c9e8000 > [ 84.922771] PC is at cursor_timer_handler+0x30/0x58 > [ 84.922775] LR is at cursor_timer_handler+0x30/0x58 > [ 84.922778] pc : [] lr : [] pstate: > 00400145 > [ 84.922781] sp : 801f6c9ebc20 > [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8 > [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8 > [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00 > [ 84.922798] x23: 801f667d9800 x22: 804ec4c0 > [ 84.922802] x21: 0100 x20: 8000f94398d8 > [ 84.922807] x19: 8000f9439800 x18: c76a5358 > [ 84.922811] x17: 97bbd2a8 x16: 802a5040 > [ 84.922816] x15: 3e4cf1e0 x14: 0008 > [ 84.922820] x13: x12: 003d0900 > [ 84.922824] x11: 003d0900 x10: 8090f200 > [ 84.922829] x9 : 3d09 x8 : 000e > [ 84.922833] x7 : 801f7b3c5008 x6 : > [ 84.922837] x5 : x4 : 0001 > [ 84.922842] x3 : x2 : 801f6c899e05 > [ 84.922846] x1 : 801f667d99e0 x0 : > [ 84.922850] > [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd > [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd > [ 101.342677] random: nonblocking pool is initialized > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574814 Title: ThunderX: soft lockup in cursor_timer_handler() Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
On Fri, Apr 29, 2016 at 2:06 AM, Ming Lei <1574...@bugs.launchpad.net> wrote: > It can be triggered 100% by running 'tcpdump -I ethX'. Thanks Ming. I let that run for a few hours, but was unable to reproduce. Are you seeing the same traceback along w the softlockup msg? -dann -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574814 Title: ThunderX: soft lockup in cursor_timer_handler() Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit
It can be triggered 100% by running 'tcpdump -I ethX'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574814 Title: ThunderX: soft lockup in cursor_timer_handler() Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
