Bug #1275116 “lowlatency-flavour crashes and locks up alot” : Bugs : linux-lowlatency package : Ubuntu

Revision history for this message

Søren Holm (sgh) wrote on 2014-01-31:

#1

AlsaInfo.txt Edit (38.6 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (60.1 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (581 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (10.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (707 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (100 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.7 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (22.1 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (250 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (145.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (323.0 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (795.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2014-01-31: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-01:

#3

Download full text (31.1 KiB)

4,996,3231003672,-;------------[ cut here ]------------
2,997,3231003700,-;kernel BUG at /build/buildd/linux-3.13.0/kernel/seccomp.c:449!
4,998,3231003733,-;invalid opcode: 0000 [#1] PREEMPT SMP
4,999,3231003759,c;Modules linked in: configfs ctr ccm pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) joydev vboxdrv(OF) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi crc32_pclmul aesni_intel snd_hda_codec_realtek parport_pc aes_i586 xts ppdev lrw gf128mul ablk_helper cryptd snd_hda_intel rfcomm snd_hda_codec bnep btusb bluetooth snd_hwdep uvcvideo videobuf2_vmalloc snd_pcm thinkpad_acpi cdc_mbim snd_page_alloc videobuf2_memops cdc_ncm nvram videobuf2_core videodev snd_seq_midi usbnet arc4 cdc_acm mii cdc_wdm snd_seq_midi_event iwldvm snd_rawmidi mac80211 snd_seq snd_seq_device psmouse iwlwifi binfmt_misc snd_timer serio_raw microcode lpc_ich snd cfg80211 soundcore mac_hid mei_me mei lp parport i915 i2c_algo_bit drm_kms_helper e1000e sdhci_pci ahci drm libahci
4,1000,3231004149,+; sdhci ptp pps_core wmi video
0,1001,3231004168,-;CPU: 1 PID: 13597 Comm: EMT-1 Tainted: GF O 3.13.0-6-lowlatency #23-Ubuntu
0,1002,3231004209,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1003,3231004244,-;task: c2a20000 ti: d532a000 task.ti: cd378000
4,1004,3231004270,-;EIP: 0060:[<c10e8078>] EFLAGS: 00010293 CPU: 1
1,1005,3231004319,-;BUG: unable to handle kernel paging request at 946d8e89
1,1006,3231004362,-;IP: [<946d8e89>] 0x946d8e89
4,1007,3231004383,-;*pdpt = 00000000350c6001 *pde = 0000000173938067
4,1008,3231004412,-;Oops: 0011 [#2] PREEMPT SMP
4,1009,3231004433,c;Modules linked in: configfs ctr ccm pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) joydev vboxdrv(OF) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi crc32_pclmul aesni_intel snd_hda_codec_realtek parport_pc aes_i586 xts ppdev lrw gf128mul ablk_helper cryptd snd_hda_intel rfcomm snd_hda_codec bnep btusb bluetooth snd_hwdep uvcvideo videobuf2_vmalloc snd_pcm thinkpad_acpi cdc_mbim snd_page_alloc videobuf2_memops cdc_ncm nvram videobuf2_core videodev snd_seq_midi usbnet arc4 cdc_acm mii cdc_wdm snd_seq_midi_event iwldvm snd_rawmidi mac80211 snd_seq snd_seq_device psmouse iwlwifi binfmt_misc snd_timer serio_raw microcode lpc_ich snd cfg80211 soundcore mac_hid mei_me mei lp parport i915 i2c_algo_bit drm_kms_helper e1000e sdhci_pci ahci drm libahci
4,1010,3231004817,+; sdhci ptp pps_core wmi video
0,1011,3231004834,-;CPU: 1 PID: 13597 Comm: EMT-1 Tainted: GF O 3.13.0-6-lowlatency #23-Ubuntu
0,1012,3231004874,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1013,3231004909,-;task: c2a20000 ti: d532a000 task.ti: cd378000
4,1014,3231004934,-;EIP: 0060:[<946d8e89>] EFLAGS: 00010092 CPU: 1
4,1015,3231004961,-;EIP is at 0x946d8e89
4,1016,3231004976,-;EAX: 0000002e EBX: d532bf2c ECX: 00000006 EDX: 00000007
4,1017,3231005005,-;ESI: 00000001 EDI: d532bf68 EBP: f7b9f648 ESP: d532bddc
4,1018,3231005034,-; DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
4,1019,3231005059,-;CR0: 80050033 CR2: 946d8e89 CR3: 2bd8e000 CR4: 001427f0
0,1020,3231005088,-;Stack:
...

4,996,3231003672,-;------------[ cut here ]------------
2,997,3231003700,-;kernel BUG at /build/buildd/linux-3.13.0/kernel/seccomp.c:449!
4,998,3231003733,-;invalid opcode: 0000 [#1] PREEMPT SMP 
4,999,3231003759,c;Modules linked in: configfs ctr ccm pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) joydev vboxdrv(OF) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi crc32_pclmul aesni_intel snd_hda_codec_realtek parport_pc aes_i586 xts ppdev lrw gf128mul ablk_helper cryptd snd_hda_intel rfcomm snd_hda_codec bnep btusb bluetooth snd_hwdep uvcvideo videobuf2_vmalloc snd_pcm thinkpad_acpi cdc_mbim snd_page_alloc videobuf2_memops cdc_ncm nvram videobuf2_core videodev snd_seq_midi usbnet arc4 cdc_acm mii cdc_wdm snd_seq_midi_event iwldvm snd_rawmidi mac80211 snd_seq snd_seq_device psmouse iwlwifi binfmt_misc snd_timer serio_raw microcode lpc_ich snd cfg80211 soundcore mac_hid mei_me mei lp parport i915 i2c_algo_bit drm_kms_helper e1000e sdhci_pci ahci drm libahci
4,1000,3231004149,+; sdhci ptp pps_core wmi video
0,1001,3231004168,-;CPU: 1 PID: 13597 Comm: EMT-1 Tainted: GF          O 3.13.0-6-lowlatency #23-Ubuntu
0,1002,3231004209,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1003,3231004244,-;task: c2a20000 ti: d532a000 task.ti: cd378000
4,1004,3231004270,-;EIP: 0060:[<c10e8078>] EFLAGS: 00010293 CPU: 1
1,1005,3231004319,-;BUG: unable to handle kernel paging request at 946d8e89
1,1006,3231004362,-;IP: [<946d8e89>] 0x946d8e89
4,1007,3231004383,-;*pdpt = 00000000350c6001 *pde = 0000000173938067 
4,1008,3231004412,-;Oops: 0011 [#2] PREEMPT SMP 
4,1009,3231004433,c;Modules linked in: configfs ctr ccm pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) joydev vboxdrv(OF) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi crc32_pclmul aesni_intel snd_hda_codec_realtek parport_pc aes_i586 xts ppdev lrw gf128mul ablk_helper cryptd snd_hda_intel rfcomm snd_hda_codec bnep btusb bluetooth snd_hwdep uvcvideo videobuf2_vmalloc snd_pcm thinkpad_acpi cdc_mbim snd_page_alloc videobuf2_memops cdc_ncm nvram videobuf2_core videodev snd_seq_midi usbnet arc4 cdc_acm mii cdc_wdm snd_seq_midi_event iwldvm snd_rawmidi mac80211 snd_seq snd_seq_device psmouse iwlwifi binfmt_misc snd_timer serio_raw microcode lpc_ich snd cfg80211 soundcore mac_hid mei_me mei lp parport i915 i2c_algo_bit drm_kms_helper e1000e sdhci_pci ahci drm libahci
4,1010,3231004817,+; sdhci ptp pps_core wmi video
0,1011,3231004834,-;CPU: 1 PID: 13597 Comm: EMT-1 Tainted: GF          O 3.13.0-6-lowlatency #23-Ubuntu
0,1012,3231004874,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1013,3231004909,-;task: c2a20000 ti: d532a000 task.ti: cd378000
4,1014,3231004934,-;EIP: 0060:[<946d8e89>] EFLAGS: 00010092 CPU: 1
4,1015,3231004961,-;EIP is at 0x946d8e89
4,1016,3231004976,-;EAX: 0000002e EBX: d532bf2c ECX: 00000006 EDX: 00000007
4,1017,3231005005,-;ESI: 00000001 EDI: d532bf68 EBP: f7b9f648 ESP: d532bddc
4,1018,3231005034,-; DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
4,1019,3231005059,-;CR0: 80050033 CR2: 946d8e89 CR3: 2bd8e000 CR4: 001427f0
0,1020,3231005088,-;Stack:
4,1021,3231005098,-; 00000371 f545c800 000a4592 00000000 d532be30 c1088290 f545c800 c2af4ea4
4,1022,3231005140,-; 000a4592 d532be44 c108831b 00000000 00000000 00000000 000026f9 f7b9f648
4,1023,3231005181,-; 94956614 00000371 f545c800 0000089a 00000000 d532be74 c1088290 f545c800
0,1024,3231005223,-;Call Trace:
4,1025,3231005241,-; [<c1088290>] ? update_curr+0xb0/0x210
4,1026,3231005264,-; [<c108831b>] ? update_curr+0x13b/0x210
4,1027,3231005289,-; [<c1088290>] ? update_curr+0xb0/0x210
4,1028,3231005313,-; [<c10856ed>] ? __enqueue_entity+0x6d/0x80
4,1029,3231005339,-; [<c109710b>] ? cpuacct_charge+0x4b/0x60
4,1030,3231005363,-; [<c108831b>] ? update_curr+0x13b/0x210
4,1031,3231005388,-; [<c10856ed>] ? __enqueue_entity+0x6d/0x80
4,1032,3231005414,-; [<c108a222>] ? put_prev_task_fair+0xd2/0x540
4,1033,3231005441,-; [<c1086c61>] ? set_next_entity+0xb1/0xe0
4,1034,3231005473,-; [<c108972a>] ? check_preempt_wakeup+0x1aa/0x250
4,1035,3231005523,-; [<c100fe4f>] ? __switch_to+0xff/0x350
4,1036,3231005561,-; [<c107c901>] ? finish_task_switch+0x41/0xc0
4,1037,3231005593,-; [<c1648402>] ? __schedule+0x342/0x760
4,1038,3231005618,-; [<c1018118>] ? ___preempt_schedule+0xc/0x14
4,1039,3231005644,-; [<c1081df0>] ? try_to_wake_up+0x150/0x240
4,1040,3231005670,-; [<c1648843>] ? schedule+0x23/0x60
4,1041,3231005692,-; [<c164bd32>] ? work_resched+0x5/0x20
4,1042,3231005717,-; [<c1640000>] ? arch_local_irq_save+0x5/0x15
0,1043,3231005741,-;Code:  Bad EIP value.
0,1044,3231005758,-;EIP: [<0044d695>] 0x44d695 SS:ESP 0068:d532bddc
4,1045,3231005790,-;CR2: 00000000946d8e89
1,1046,3231011669,-;BUG: unable to handle kernel NULL pointer dereference at   (null)
1,1047,3231012984,-;IP: [<  (null)>]   (null)
4,1048,3231014278,-;*pdpt = 000000002bead001 *pde = 0000000000000000 
4,1049,3231015550,-;Oops: 0010 [#3] PREEMPT SMP 
4,1050,3231017056,c;Modules linked in: configfs ctr ccm pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) joydev vboxdrv(OF) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi crc32_pclmul aesni_intel snd_hda_codec_realtek parport_pc aes_i586 xts ppdev lrw gf128mul ablk_helper cryptd snd_hda_intel rfcomm snd_hda_codec bnep btusb bluetooth snd_hwdep uvcvideo videobuf2_vmalloc snd_pcm thinkpad_acpi cdc_mbim snd_page_alloc videobuf2_memops cdc_ncm nvram videobuf2_core videodev snd_seq_midi usbnet arc4 cdc_acm mii cdc_wdm snd_seq_midi_event iwldvm snd_rawmidi mac80211 snd_seq snd_seq_device psmouse iwlwifi binfmt_misc snd_timer serio_raw microcode lpc_ich snd cfg80211 soundcore mac_hid mei_me mei lp parport i915 i2c_algo_bit drm_kms_helper e1000e sdhci_pci ahci drm libahci
4,1051,3231024049,+; sdhci ptp pps_core wmi video
0,1052,3231025919,-;CPU: 1 PID: 13597 Comm: EMT-1 Tainted: GF          O 3.13.0-6-lowlatency #23-Ubuntu
0,1053,3231028005,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1054,3231030004,-;task: c2a20000 ti: d532a000 task.ti: cd378000
4,1055,3231032502,-;EIP: 017d:[<00000000>] EFLAGS: 00000000 CPU: 1
4,1056,3231034740,-;EIP is at 0x0
4,1057,3231036597,-;EAX: 00000000 EBX: 00000000 ECX: d532bd18 EDX: f009d400
4,1058,3231039711,-;ESI: d532bcb8 EDI: d532bcc4 EBP: c108c9c9 ESP: d532bc50
4,1059,3231042802,-; DS: 007b ES: 007b FS: 0495 GS: 00e0 SS: 0068
4,1060,3231045651,-;CR0: 80050033 CR2: 00000000 CR3: 2bd8e000 CR4: 001427f0
0,1061,3231048409,-;Stack:
4,1062,3231050868,-; f0137120 00000114 00000916 00000000 00000000 00000000 00000000 00000000
4,1063,3231052806,-; c1088290 f545ee00 c2af4ea4 0000183e d532bcc4 c108831b 00000000 00000073
4,1064,3231054642,-; 00000082 00000082 f9db26f3 000002e9 f7b83648 f545ee00 f545ee00 f7b83648
0,1065,3231056468,-;Call Trace:
4,1066,3231058249,-; [<c1088290>] ? update_curr+0xb0/0x210
4,1067,3231060046,-; [<c108831b>] ? update_curr+0x13b/0x210
4,1068,3231061833,-; [<c108cf4e>] ? load_balance+0x10e/0x7e0
4,1069,3231063520,-; [<c1087046>] ? update_blocked_averages+0x296/0x840
4,1070,3231065578,-; [<c10891d6>] ? dequeue_task_fair+0x416/0x7c0
4,1071,3231068306,-; [<c10856ed>] ? __enqueue_entity+0x6d/0x80
4,1072,3231071046,-; [<c108a9af>] ? enqueue_entity+0x31f/0xed0
4,1073,3231072956,-; [<c107cec8>] ? update_rq_clock.part.74+0x18/0x50
4,1074,3231074719,-; [<c108bb39>] ? enqueue_task_fair+0x5d9/0x7e0
4,1075,3231076448,-; [<c108bb39>] ? enqueue_task_fair+0x5d9/0x7e0
4,1076,3231078114,-; [<c10171c8>] ? sched_clock+0x8/0x10
4,1077,3231079835,-; [<c1085fe2>] ? select_task_rq_fair+0x1e2/0x710
4,1078,3231081517,-; [<c10bbc8f>] ? get_futex_key+0x18f/0x260
4,1079,3231082655,-; [<c1648843>] ? schedule+0x23/0x60
4,1080,3231083816,-; [<c10bbe33>] ? futex_wait_queue_me+0xd3/0x130
4,1081,3231085250,-; [<c10bc4e4>] ? futex_wait+0x154/0x240
4,1082,3231086398,-; [<c10bce1d>] ? futex_wake+0x13d/0x160
4,1083,3231087464,-; [<c157aef5>] ? sk_run_filter+0x225/0x600
4,1084,3231088520,-; [<c10bdfbb>] ? do_futex+0xcb/0x530
4,1085,3231089713,-; [<c107c901>] ? finish_task_switch+0x41/0xc0
4,1086,3231091296,-; [<c1648402>] ? __schedule+0x342/0x760
4,1087,3231092419,-; [<c10be4ac>] ? SyS_futex+0x8c/0x140
4,1088,3231093631,-; [<c164bc93>] ? syscall_call+0x7/0xb
4,1089,3231094686,-; [<c1640000>] ? arch_local_irq_save+0x5/0x15
0,1090,3231095950,-;Code:  Bad EIP value.
0,1091,3231097398,-;EIP: [<000000b3>] 0xb3 SS:ESP d648:0002380f
4,1092,3231099137,-;CR2: 0000000000000000
4,1093,3231100856,-;---[ end trace fb04b7d650f82668 ]---
4,1094,3250470706,-;------------[ cut here ]------------
4,1095,3250471797,-;WARNING: CPU: 1 PID: 13579 at /build/buildd/linux-3.13.0/kernel/watchdog.c:245 watchdog_overflow_callback+0xac/0xd0()
4,1096,3250472907,-;Watchdog detected hard LOCKUP on cpu 1
4,1097,3250472923,c;Modules linked in:
4,1098,3250474013,+; configfs ctr ccm pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) joydev vboxdrv(OF) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi crc32_pclmul aesni_intel snd_hda_codec_realtek parport_pc aes_i586 xts ppdev lrw gf128mul ablk_helper cryptd snd_hda_intel rfcomm snd_hda_codec bnep btusb bluetooth snd_hwdep uvcvideo videobuf2_vmalloc snd_pcm thinkpad_acpi cdc_mbim snd_page_alloc videobuf2_memops cdc_ncm nvram videobuf2_core videodev snd_seq_midi usbnet arc4 cdc_acm mii cdc_wdm snd_seq_midi_event iwldvm snd_rawmidi mac80211 snd_seq snd_seq_device psmouse iwlwifi binfmt_misc snd_timer serio_raw microcode lpc_ich snd cfg80211 soundcore mac_hid mei_me mei lp parport i915 i2c_algo_bit drm_kms_helper e1000e sdhci_pci ahci drm libahci sdhci ptp pps_core
4,1099,3250480988,+; wmi video
4,1100,3250482967,-;CPU: 1 PID: 13579 Comm: Watcher Tainted: GF     D    O 3.13.0-6-lowlatency #23-Ubuntu
4,1101,3250484936,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
4,1102,3250486836,-; 00000000 00000000 edcdfbac c16454da edcdfbec edcdfbdc c10559de c1823438
4,1103,3250488833,-; edcdfc08 0000350b c1823460 000000f5 c10e7a9c c10e7a9c f0158000 c10e79f0
4,1104,3250490770,-; 00000000 edcdfbf4 c1055a33 00000009 edcdfbec c1823438 edcdfc08 edcdfc0c
4,1105,3250492646,-;Call Trace:
4,1106,3250494485,-; [<c16454da>] dump_stack+0x48/0x69
4,1107,3250496274,-; [<c10559de>] warn_slowpath_common+0x7e/0xa0
4,1108,3250497771,-; [<c10e7a9c>] ? watchdog_overflow_callback+0xac/0xd0
4,1109,3250498925,-; [<c10e7a9c>] ? watchdog_overflow_callback+0xac/0xd0
4,1110,3250500250,-; [<c10e79f0>] ? restart_watchdog_hrtimer+0x50/0x50
4,1111,3250501924,-; [<c1055a33>] warn_slowpath_fmt+0x33/0x40
4,1112,3250503570,-; [<c10e7a9c>] watchdog_overflow_callback+0xac/0xd0
4,1113,3250505177,-; [<c111953d>] __perf_event_overflow+0xad/0x280
4,1114,3250506824,-; [<c1119cd5>] perf_event_overflow+0x15/0x20
4,1115,3250508383,-; [<c102a194>] intel_pmu_handle_irq+0x1f4/0x3f0
4,1116,3250510001,-; [<c12edbf8>] ? cpumask_next_and+0x28/0x40
4,1117,3250511615,-; [<c164d77c>] perf_event_nmi_handler+0x2c/0x50
4,1118,3250513169,-; [<c164ceaf>] nmi_handle.isra.2+0x5f/0x1c0
4,1119,3250514472,-; [<c1088290>] ? update_curr+0xb0/0x210
4,1120,3250515757,-; [<c164d1f7>] do_nmi+0x1e7/0x3d0
4,1121,3250517339,-; [<c1088850>] ? dequeue_entity+0x160/0x6d0
4,1122,3250518859,-; [<c164c557>] nmi_stack_correct+0x2f/0x34
4,1123,3250520483,-; [<c10800d8>] ? sched_ttwu_pending+0x8/0x50
4,1124,3250522197,-; [<c164cc06>] ? oops_begin+0xc6/0xe0
4,1125,3250523913,-; [<c108a222>] ? put_prev_task_fair+0xd2/0x540
4,1126,3250525638,-; [<c1086c61>] ? set_next_entity+0xb1/0xe0
4,1127,3250527361,-; [<c1086cd7>] ? pick_next_task_fair+0x47/0x120
4,1128,3250529066,-; [<c12f80cc>] ? sprintf+0x1c/0x20
4,1129,3250530727,-; [<c10a2642>] ? print_prefix+0x62/0xb0
4,1130,3250532433,-; [<c10910cb>] ? prepare_to_wait_event+0x6b/0xd0
4,1131,3250534103,-; [<c1648843>] ? schedule+0x23/0x60
4,1132,3250535770,-; [<c10a4649>] ? do_syslog+0x489/0x530
4,1133,3250536992,-; [<c1091130>] ? prepare_to_wait_event+0xd0/0xd0
4,1134,3250538549,-; [<c11d9270>] ? kmsg_poll+0x50/0x50
4,1135,3250539798,-; [<c11d92b5>] ? kmsg_read+0x45/0x60
4,1136,3250541396,-; [<c11cbe48>] ? proc_reg_read+0x48/0x80
4,1137,3250543001,-; [<c11cbe00>] ? proc_reg_write+0x80/0x80
4,1138,3250544488,-; [<c11784f8>] ? vfs_read+0x78/0x140
4,1139,3250546061,-; [<c1191c3f>] ? fget_light+0x6f/0xc0
4,1140,3250547621,-; [<c1178c69>] ? SyS_read+0x49/0x90
4,1141,3250549294,-; [<c165234d>] ? sysenter_do_call+0x12/0x28
4,1142,3250550882,-;---[ end trace fb04b7d650f82669 ]---
4,1143,3250552515,-;perf samples too long (640485 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
6,1144,3250554277,-;INFO: NMI handler (perf_event_nmi_handler) took too long to run: 83.570 msecs
4,1145,3260329244,-;perf samples too long (635511 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
3,1146,3263077960,-;ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
6,1147,3263079807,-;sr 1:0:0:0: CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:1:0:0:0
4,1148,3263081604,-;Get event status notification: 4a 01 00 00 10 00 00 00 08 00
3,1149,3263083743,-;ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in\x0a         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
3,1150,3263086498,-;ata2.00: status: { DRDY }
6,1151,3263088500,-;ata2: hard resetting link
6,1152,3263394053,-;ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
3,1153,3268048284,-;ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x6 frozen
3,1154,3268049312,-;ata1.00: failed command: WRITE FPDMA QUEUED
3,1155,3268050228,-;ata1.00: cmd 61/48:00:a8:c6:05/00:00:0a:00:00/40 tag 0 ncq 36864 out\x0a         res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
3,1156,3268052141,-;ata1.00: status: { DRDY }
3,1157,3268053399,-;ata1.00: failed command: WRITE FPDMA QUEUED
3,1158,3268054741,-;ata1.00: cmd 61/58:08:00:20:18/01:00:04:00:00/40 tag 1 ncq 176128 out\x0a         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
3,1159,3268056808,-;ata1.00: status: { DRDY }
3,1160,3268058211,-;ata1.00: failed command: WRITE FPDMA QUEUED
3,1161,3268059468,-;ata1.00: cmd 61/18:10:50:eb:c4/00:00:00:00:00/40 tag 2 ncq 12288 out\x0a         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
3,1162,3268061581,-;ata1.00: status: { DRDY }
6,1163,3268062661,-;ata1: hard resetting link
6,1164,3268370402,-;ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
4,1165,3268396393,-;ata2.00: qc timeout (cmd 0xa1)
4,1166,3268398388,-;ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
3,1167,3268399312,-;ata2.00: revalidation failed (errno=-5)
6,1168,3268400297,-;ata2: hard resetting link
6,1169,3268708485,-;ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
4,1170,3269647952,-;perf samples too long (630575 > 10000), lowering kernel.perf_event_max_sample_rate to 13000
4,1171,3273372740,-;ata1.00: qc timeout (cmd 0xec)
4,1172,3273375745,-;ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
3,1173,3273377382,-;ata1.00: revalidation failed (errno=-5)
6,1174,3273378899,-;ata1: hard resetting link
6,1175,3273684832,-;ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
4,1176,3278711177,-;ata2.00: qc timeout (cmd 0xa1)
4,1177,3278713181,-;ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
3,1178,3278714217,-;ata2.00: revalidation failed (errno=-5)
4,1179,3278715451,-;ata2: limiting SATA link speed to 1.5 Gbps
6,1180,3278716445,-;ata2: hard resetting link
4,1181,3278840630,-;perf samples too long (625681 > 19230), lowering kernel.perf_event_max_sample_rate to 7000
6,1182,3279024286,-;ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
4,1183,3283688532,-;ata1.00: qc timeout (cmd 0xec)
4,1184,3283691525,-;ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
3,1185,3283693059,-;ata1.00: revalidation failed (errno=-5)
4,1186,3283694377,-;ata1: limiting SATA link speed to 3.0 Gbps
6,1187,3283696000,-;ata1: hard resetting link
6,1188,3284002620,-;ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
4,1189,3288005980,-;perf samples too long (620818 > 35714), lowering kernel.perf_event_max_sample_rate to 4000
3,1190,3291098514,-;INFO: rcu_preempt detected stalls on CPUs/tasks: { 1} (detected by 2, t=60002 jiffies, g=76532, c=76531, q=1800)
6,1191,3291099672,-;sending NMI to all CPUs:
4,1192,3291100770,-;NMI backtrace for cpu 0
4,1193,3291100771,-;perf samples too long (615977 > 62500), lowering kernel.perf_event_max_sample_rate to 2000
0,1194,3291103848,-;CPU: 0 PID: 0 Comm: swapper/0 Tainted: GF     D W  O 3.13.0-6-lowlatency #23-Ubuntu
0,1195,3291105352,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1196,3291106865,-;task: c190ea00 ti: c1902000 task.ti: c1902000
4,1197,3291108349,-;EIP: 0060:[<c1366049>] EFLAGS: 00200046 CPU: 0
4,1198,3291109853,-;EIP is at intel_idle+0xa9/0xf0
4,1199,3291111300,-;EAX: 00000001 EBX: 00000002 ECX: 00000001 EDX: 00000000
4,1200,3291112751,-;ESI: 00000002 EDI: 00000001 EBP: c1903f50 ESP: c1903f3c
4,1201,3291114214,-; DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
4,1202,3291115672,-;CR0: 80050033 CR2: ac36d000 CR3: 137b9000 CR4: 001427f0
0,1203,3291117108,-;Stack:
4,1204,3291118562,-; 06cc9ea3 00000000 c194f800 f7b87200 c194f8a8 c1903f70 c1524a81 00000002
4,1205,3291120041,-; 06cc9ea3 000002fe 5af76149 0008f800 00000002 c1903f90 c1524bb9 c194f800
4,1206,3291121508,-; 00000000 f7b87200 5af76149 0008f800 c1902000 c1903f98 c101896d c1903fbc
0,1207,3291122969,-;Call Trace:
4,1208,3291124449,-; [<c1524a81>] cpuidle_enter_state+0x31/0xd0
4,1209,3291125996,-; [<c1524bb9>] cpuidle_idle_call+0x99/0x200
4,1210,3291127536,-; [<c101896d>] arch_cpu_idle+0xd/0x30
4,1211,3291129050,-; [<c10a5351>] cpu_startup_entry+0x211/0x260
4,1212,3291130580,-; [<c163c281>] rest_init+0x71/0x80
4,1213,3291132071,-; [<c19a0af0>] start_kernel+0x3ba/0x3c0
4,1214,3291133542,-; [<c19a056d>] ? repair_env_string+0x51/0x51
4,1215,3291135040,-; [<c19a0394>] i386_start_kernel+0x137/0x13a
0,1216,3291136508,-;Code: 89 e0 25 00 e0 ff ff 31 d2 83 c0 08 89 d1 0f 01 c8 0f ae f0 89 f6 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 07 b1 01 89 f8 0f 01 c9 <85> 1d dc f7 94 c1 75 0d 8d 55 f0 b8 05 00 00 00 e8 92 22 d5 ff
4,1217,3291139599,-;NMI backtrace for cpu 2
0,1218,3291141142,-;CPU: 2 PID: 0 Comm: swapper/2 Tainted: GF     D W  O 3.13.0-6-lowlatency #23-Ubuntu
0,1219,3291142687,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1220,3291144277,-;task: f0102730 ti: f0108000 task.ti: f0108000
4,1221,3291145872,-;EIP: 0060:[<c12f88ca>] EFLAGS: 00200006 CPU: 2
4,1222,3291147429,-;EIP is at __const_udelay+0xa/0x20
4,1223,3291148978,-;EAX: 00418958 EBX: 00002710 ECX: fffff000 EDX: 002c26f2
4,1224,3291150533,-;ESI: c1927840 EDI: f7b9a800 EBP: f0109da0 ESP: f0109da0
4,1225,3291152095,-; DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
4,1226,3291153652,-;CR0: 80050033 CR2: b77ac000 CR3: 2dda3000 CR4: 001427f0
0,1227,3291155187,-;Stack:
4,1228,3291156698,-; f0109db0 c103de45 c1810165 c1927840 f0109df8 c10af243 c181fe50 00000002
4,1229,3291158266,-; 0000ea62 00012af4 00012af3 00000708 00000001 c1927840 00200046 c1999c0c
4,1230,3291159832,-; 00000001 00000708 00000002 f0102730 00000000 00000002 f0109e0c c1062b9c
0,1231,3291161400,-;Call Trace:
4,1232,3291162949,-; [<c103de45>] arch_trigger_all_cpu_backtrace+0x55/0x70
4,1233,3291164522,-; [<c10af243>] rcu_check_callbacks+0x633/0x650
4,1234,3291166087,-; [<c1062b9c>] update_process_times+0x3c/0x60
4,1235,3291167696,-; [<c10ba246>] tick_sched_handle.isra.12+0x26/0x60
4,1236,3291169287,-; [<c10ba2b7>] tick_sched_timer+0x37/0x70
4,1237,3291170808,-; [<c1076718>] ? __remove_hrtimer+0x38/0x90
4,1238,3291172350,-; [<c107697f>] __run_hrtimer+0x6f/0x210
4,1239,3291173861,-; [<c10ba280>] ? tick_sched_handle.isra.12+0x60/0x60
4,1240,3291175406,-; [<c1077645>] hrtimer_interrupt+0x1f5/0x2b0
4,1241,3291176910,-; [<c103bf2f>] local_apic_timer_interrupt+0x2f/0x60
4,1242,3291178467,-; [<c105a99f>] ? irq_enter+0x5f/0x70
4,1243,3291179968,-; [<c1652b13>] smp_apic_timer_interrupt+0x33/0x50
4,1244,3291181456,-; [<c164c0b8>] apic_timer_interrupt+0x34/0x3c
4,1245,3291182915,-; [<c1524a8e>] ? cpuidle_enter_state+0x3e/0xd0
4,1246,3291184380,-; [<c1524bb9>] cpuidle_idle_call+0x99/0x200
4,1247,3291185838,-; [<c101896d>] arch_cpu_idle+0xd/0x30
4,1248,3291187249,-; [<c10a5351>] cpu_startup_entry+0x211/0x260
4,1249,3291188668,-; [<c103ba43>] ? setup_APIC_timer+0xe3/0x130
4,1250,3291190072,-; [<c103a048>] start_secondary+0x218/0x2e0
0,1251,3291191430,-;Code: 00 48 75 fd 48 5d c3 8d 76 00 8d bc 27 00 00 00 00 55 89 e5 3e 8d 74 26 00 ff 15 f0 bc 94 c1 5d c3 55 89 e5 64 8b 15 1c 61 a7 c1 <c1> e0 02 69 d2 fa 00 00 00 f7 e2 8d 42 01 ff 15 f0 bc 94 c1 5d
4,1252,3291194482,-;NMI backtrace for cpu 3
6,1253,3291194485,-;INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) took too long to run: 93.712 msecs
0,1254,3291197613,-;CPU: 3 PID: 0 Comm: swapper/3 Tainted: GF     D W  O 3.13.0-6-lowlatency #23-Ubuntu
0,1255,3291199157,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1256,3291200705,-;task: f0103440 ti: f010a000 task.ti: f010a000
4,1257,3291202335,-;EIP: 0060:[<c1366049>] EFLAGS: 00200046 CPU: 3
4,1258,3291203890,-;EIP is at intel_idle+0xa9/0xf0
4,1259,3291205416,-;EAX: 00000020 EBX: 00000008 ECX: 00000001 EDX: 00000000
4,1260,3291206957,-;ESI: 00000004 EDI: 00000020 EBP: f010bf24 ESP: f010bf10
4,1261,3291208537,-; DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
4,1262,3291210062,-;CR0: 80050033 CR2: a9f80000 CR3: 01a80000 CR4: 001427f0
0,1263,3291211603,-;Stack:
4,1264,3291213228,-; 00000003 00000003 c194f800 f7bb1200 c194f940 f010bf44 c1524a81 00000004
4,1265,3291214826,-; 06da83ca 000002fe 3dd4ee57 00000000 00000004 f010bf64 c1524bb9 c194f800
4,1266,3291216412,-; 00000003 f7bb1200 3dd4ee57 00000000 f010a000 f010bf6c c101896d f010bf90
0,1267,3291218010,-;Call Trace:
4,1268,3291219588,-; [<c1524a81>] cpuidle_enter_state+0x31/0xd0
4,1269,3291221283,-; [<c1524bb9>] cpuidle_idle_call+0x99/0x200
4,1270,3291222830,-; [<c101896d>] arch_cpu_idle+0xd/0x30
4,1271,3291224363,-; [<c10a5351>] cpu_startup_entry+0x211/0x260
4,1272,3291225817,-; [<c103ba43>] ? setup_APIC_timer+0xe3/0x130
4,1273,3291227253,-; [<c103a048>] start_secondary+0x218/0x2e0
0,1274,3291228670,-;Code: 89 e0 25 00 e0 ff ff 31 d2 83 c0 08 89 d1 0f 01 c8 0f ae f0 89 f6 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 07 b1 01 89 f8 0f 01 c9 <85> 1d dc f7 94 c1 75 0d 8d 55 f0 b8 05 00 00 00 e8 92 22 d5 ff
4,1275,3291231768,-;NMI backtrace for cpu 1
6,1276,3291231770,-;INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) took too long to run: 130.998 msecs
0,1277,3291234511,-;CPU: 1 PID: 13579 Comm: Watcher Tainted: GF     D W  O 3.13.0-6-lowlatency #23-Ubuntu
0,1278,3291235734,-;Hardware name: LENOVO 2356GCG/2356GCG, BIOS G7ET31WW (1.13 ) 07/02/2012
0,1279,3291236963,-;task: c2a25b70 ti: edcde000 task.ti: ebdec000
4,1280,3291238292,-;EIP: 71c8:[<edcdfdfc>] EFLAGS: edcdfe24 CPU: 1
4,1281,3291239500,-;EIP is at 0xedcdfdfc
4,1282,3291240704,-;EAX: 00000001 EBX: 4cb83400 ECX: 000002fe EDX: eda6e400
4,1283,3291241998,-;ESI: 00000001 EDI: 000002fe EBP: f7bad648 ESP: edcdfe00
4,1284,3291243777,-; DS: 0000 ES: fe38 FS: 91d6 GS: 00e0 SS: 0068
4,1285,3291245566,-;CR0: 80050033 CR2: 0e8f2c0d CR3: 2bd88000 CR4: 001427f0
0,1286,3291247222,-;Stack:
4,1287,3291248810,-; f7bad600 c10171c8 c182b621 c182b622 edcdfe30 c12f5a93 f7bad670 000002fe
4,1288,3291250635,-; edbc3484 edbc348c f7bad648 edcdfe4c c1086c61 0001ef76 000013f8 00000000
4,1289,3291252471,-; f7bad648 edbc3484 edbc3484 edcdfe68 c1086cd7 00000000 f7bad600 f7bad600
0,1290,3291254317,-;Call Trace:
4,1291,3291256152,-; [<c10171c8>] ? sched_clock+0x8/0x10
4,1292,3291257474,-; [<c12f5a93>] ? format_decode+0x323/0x390
4,1293,3291258758,-; [<c1086c61>] ? set_next_entity+0xb1/0xe0
4,1294,3291260509,-; [<c1086cd7>] ? pick_next_task_fair+0x47/0x120
4,1295,3291262210,-; [<c12f80cc>] ? sprintf+0x1c/0x20
4,1296,3291264022,-; [<c10a2642>] ? print_prefix+0x62/0xb0
4,1297,3291265690,-; [<c10910cb>] ? prepare_to_wait_event+0x6b/0xd0
4,1298,3291267593,-; [<c1648843>] ? schedule+0x23/0x60
4,1299,3291269273,-; [<c10a4649>] ? do_syslog+0x489/0x530
4,1300,3291270964,-; [<c1091130>] ? prepare_to_wait_event+0xd0/0xd0
4,1301,3291272664,-; [<c11d9270>] ? kmsg_poll+0x50/0x50
4,1302,3291274240,-; [<c11d92b5>] ? kmsg_read+0x45/0x60
4,1303,3291275999,-; [<c11cbe48>] ? proc_reg_read+0x48/0x80
4,1304,3291277818,-; [<c11cbe00>] ? proc_reg_write+0x80/0x80
4,1305,3291279547,-; [<c11784f8>] ? vfs_read+0x78/0x140
4,1306,3291281065,-; [<c1191c3f>] ? fget_light+0x6f/0xc0
4,1307,3291282125,-; [<c1178c69>] ? SyS_read+0x49/0x90
4,1308,3291283505,-; [<c165234d>] ? sysenter_do_call+0x12/0x28
0,1309,3291285094,-;Code: 00 00 00 fe 02 00 00 48 d6 ba f7 01 00 00 00 00 00 00 00 38 fe cd ed d6 91 08 c1 00 d6 ba f7 01 00 00 00 fc fd cd ed c8 71 01 c1 <24> fe cd ed 00 d6 ba f7 c8 71 01 c1 21 b6 82 c1 22 b6 82 c1 30
4,1310,3309033383,-;ata2.00: qc timeout (cmd 0xa1)
4,1311,3309036370,-;ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
3,1312,3309037532,-;ata2.00: revalidation failed (errno=-5)
4,1313,3309038655,-;ata2.00: disabled
6,1314,3309050388,-;ata2: hard resetting link
6,1315,3309356471,-;ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
6,1316,3309368494,-;ata2: EH complete
4,1317,3314011718,-;ata1.00: qc timeout (cmd 0xec)
4,1318,3314014725,-;ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
3,1319,3314016269,-;ata1.00: revalidation failed (errno=-5)
4,1320,3314017952,-;ata1.00: disabled
4,1321,3314029724,-;ata1.00: device reported invalid CHS sector 0
4,1322,3314030981,-;ata1.00: device reported invalid CHS sector 0
4,1323,3314032052,-;ata1.00: device reported invalid CHS sector 0
6,1324,3314033131,-;ata1: hard resetting link
6,1325,3314338821,-;ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
6,1326,3314350821,-;ata1: EH complete
6,1327,3314352431,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
6,1328,3314353941,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1329,3314355096,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1330,3314356341,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1331,3314357650,-;Write(10): 2a 00 00 c4 eb 50 00 00 18 00
3,1332,3314358622,-;end_request: I/O error, dev sda, sector 12905296
6,1333,3314359559,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
3,1334,3314359560,-;Aborting journal on device sda1-8.
6,1335,3314359577,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
6,1336,3314359578,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1337,3314359579,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1338,3314359580,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1339,3314359584,-;Write(10): 2a 00 00 c4 24 00 00 00 08 00
3,1340,3314359585,-;end_request: I/O error, dev sda, sector 12854272
3,1341,3314359586,-;Buffer I/O error on device sda1, logical block 1606528
4,1342,3314359587,-;lost page write due to I/O error on sda1
3,1343,3314359592,-;JBD2: Error -5 detected when updating journal superblock for sda1-8.
2,1344,3314360957,-;EXT4-fs error (device sda1) in ext4_reserve_inode_write:4842: Journal has aborted
6,1345,3314360977,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
6,1346,3314360978,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1347,3314360979,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1348,3314360980,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1349,3314360984,-;Write(10): 2a 00 00 00 08 00 00 00 08 00
3,1350,3314360985,-;end_request: I/O error, dev sda, sector 2048
3,1351,3314360987,-;Buffer I/O error on device sda1, logical block 0
4,1352,3314360987,-;lost page write due to I/O error on sda1
2,1353,3314360995,-;EXT4-fs (sda1): Remounting filesystem read-only
6,1354,3314385638,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1355,3314386987,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1356,3314388325,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1357,3314389692,-;Write(10): 2a 00 04 18 20 00 00 01 58 00
3,1358,3314391149,-;end_request: I/O error, dev sda, sector 68689920
4,1359,3314392635,-;EXT4-fs warning (device sda5): ext4_end_bio:317: I/O error writing to inode 9044313 (offset 0 size 176128 starting block 8586240)
3,1360,3314394185,-;Buffer I/O error on device sda5, logical block 4923904
3,1361,3314395758,-;Buffer I/O error on device sda5, logical block 4923905
3,1362,3314397313,-;Buffer I/O error on device sda5, logical block 4923906
3,1363,3314398855,-;Buffer I/O error on device sda5, logical block 4923907
3,1364,3314400320,-;Buffer I/O error on device sda5, logical block 4923908
3,1365,3314401693,-;Buffer I/O error on device sda5, logical block 4923909
3,1366,3314402802,-;Buffer I/O error on device sda5, logical block 4923910
3,1367,3314403742,-;Buffer I/O error on device sda5, logical block 4923911
3,1368,3314404929,-;Buffer I/O error on device sda5, logical block 4923912
3,1369,3314406110,-;Buffer I/O error on device sda5, logical block 4923913
6,1370,3314407431,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
6,1371,3314408724,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1372,3314409801,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1373,3314410870,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1374,3314411734,-;Write(10): 2a 00 0a 05 c6 a8 00 00 48 00
3,1375,3314412575,-;end_request: I/O error, dev sda, sector 168150696
3,1376,3314413647,-;Aborting journal on device sda5-8.
6,1377,3314414950,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
6,1378,3314416161,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1379,3314417314,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1380,3314418462,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1381,3314419689,-;Write(10): 2a 00 0a 03 10 00 00 00 08 00
3,1382,3314420865,-;end_request: I/O error, dev sda, sector 167972864
3,1383,3314422055,-;Buffer I/O error on device sda5, logical block 17334272
4,1384,3314423219,-;lost page write due to I/O error on sda5
3,1385,3314424568,-;JBD2: Error -5 detected when updating journal superblock for sda5-8.
6,1386,3314425872,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
6,1387,3314427759,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1388,3314429617,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1389,3314431044,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1390,3314432420,-;Write(10): 2a 00 01 bf 10 00 00 00 08 00
3,1391,3314433821,-;end_request: I/O error, dev sda, sector 29298688
3,1392,3314435226,-;Buffer I/O error on device sda5, logical block 0
4,1393,3314436622,-;lost page write due to I/O error on sda5
2,1394,3314438030,-;EXT4-fs error (device sda5): ext4_journal_check_start:56: Detected aborted journal
2,1395,3314439105,-;EXT4-fs (sda5): Remounting filesystem read-only
3,1396,3314440058,-;EXT4-fs (sda5): previous I/O error to superblock detected
6,1397,3314441158,-;sd 0:0:0:0: [sda] Unhandled error code
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
6,1398,3314442612,-;sd 0:0:0:0: [sda]  
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1399,3314443979,-;Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
6,1400,3314445163,-;sd 0:0:0:0: [sda] CDB: 
 SUBSYSTEM=scsi
 DEVICE=+scsi:0:0:0:0
4,1401,3314446086,-;Write(10): 2a 00 01 bf 10 00 00 00 08 00
3,1402,3314447052,-;end_request: I/O error, dev sda, sector 29298688
3,1403,3314447959,-;Buffer I/O error on device sda5, logical block 0
4,1404,3314448845,-;lost page write due to I/O error on sda5

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-01:

#4

IMAG0496.jpg Edit (1.2 MiB, image/jpeg)

Crash during web-site access using chromium.

description:

updated

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-01:

#5

IMAG0497.jpg Edit (1.1 MiB, image/jpeg)

After the prebvious crash I powercycled the computer and got a stall here.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-01:

#6

Same problem here. Whole system locks sudently. I'm using same dist and kernel.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-01:

#7

I'm using arch amd64

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-01:

#8

I have tried setting up netconsole to cash what the kernel might think is happening but wireless is not supported.

https://wiki.ubuntu.com/Kernel/Netconsole

Jaime, maybe you have a wired setup and can try to set it up?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-01:

#9

Jaime, are you running virtualbox or some other virtualization software?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#10

I'm quite sure that this relates to running virtualbox - the system crashes within 5 minuttes. Not running virtualbox does not make the system unstable.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#11

IMAG0504.jpg Edit (953.9 KiB, image/jpeg)

Another crash

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-02:

#12

I'm running not virtualized ubuntu. I have wired conexion, but i don't know what is net console. I'm going to read the link you posted and I'll try to do something.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-02:

#13

However in my netbook I'm running lowlatency kernel and it seems to work fine. Perhaps is a driver issue or something.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-02:

#14

Ok its logging. I'm going to leave it for a while. Computer is blocked and still pasing info by netconsole. If log is too big i will compress it.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-02:

#15

kernel panic trace Edit (140.0 KiB, text/plain)

Here it is. I thing that it was in a loop, because some info seems to reappear. If more information its needed I can do this again.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#16

We seem some more skilled people than me on this. It seem like the error start at one thing, but then progresses and pull the IO subsystem down (the IO-error that I also get).

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#17

Download full text (3.6 KiB)

diff --git a/boot/config-3.13.0-6-generic b/boot/config-3.13.0-6-lowlatency
index 2684575..e86aff9 100644
--- a/boot/config-3.13.0-6-generic
+++ b/boot/config-3.13.0-6-lowlatency
@@ -1,6 +1,6 @@
#
# Automatically generated file; DO NOT EDIT.
-# Linux/i386 3.13.0-6-generic Kernel Configuration
+# Linux/i386 3.13.0-6-lowlatency Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
@@ -64,7 +64,7 @@ CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
-CONFIG_VERSION_SIGNATURE="Ubuntu 3.13.0-6.23-generic 3.13.0"
+CONFIG_VERSION_SIGNATURE="Ubuntu 3.13.0-6.23-lowlatency 3.13.0"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
@@ -86,7 +86,7 @@ CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
-# CONFIG_IRQ_FORCED_THREADING_DEFAULT is not set
+CONFIG_IRQ_FORCED_THREADING_DEFAULT=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_KTIME_SCALAR=y
@@ -121,14 +121,15 @@ CONFIG_TASK_IO_ACCOUNTING=y
#
# RCU Subsystem
#
-CONFIG_TREE_RCU=y
-# CONFIG_PREEMPT_RCU is not set
+CONFIG_TREE_PREEMPT_RCU=y
+CONFIG_PREEMPT_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
CONFIG_RCU_FAST_NO_HZ=y
# CONFIG_TREE_RCU_TRACE is not set
+# CONFIG_RCU_BOOST is not set
# CONFIG_RCU_NOCB_CPU is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
@@ -222,7 +223,6 @@ CONFIG_HAVE_OPROFILE=y
CONFIG_OPROFILE_NMI_TIMER=y
CONFIG_KPROBES=y
CONFIG_JUMP_LABEL=y
-CONFIG_OPTPROBES=y
CONFIG_KPROBES_ON_FTRACE=y
CONFIG_UPROBES=y
# CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set
@@ -342,11 +342,6 @@ CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PADATA=y
CONFIG_ASN1=y
CONFIG_UNINLINE_SPIN_UNLOCK=y
-CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
-CONFIG_INLINE_READ_UNLOCK=y
-CONFIG_INLINE_READ_UNLOCK_IRQ=y
-CONFIG_INLINE_WRITE_UNLOCK=y
-CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=y

@@ -438,8 +433,9 @@ CONFIG_NR_CPUS=8
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
-CONFIG_PREEMPT_VOLUNTARY=y
-# CONFIG_PREEMPT is not set
+# CONFIG_PREEMPT_VOLUNTARY is not set
+CONFIG_PREEMPT=y
+CONFIG_PREEMPT_COUNT=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
@@ -534,10 +530,10 @@ CONFIG_EFI_STUB=y
CONFIG_SECCOMP=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_HZ_100 is not set
-CONFIG_HZ_250=y
+# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
-# CONFIG_HZ_1000 is not set
-CONFIG_HZ=250
+CONFIG_HZ_1000=y
+CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
@@ -4881,7 +4877,6 @@ CONFIG_DRM_NOUVEAU=m
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
-CONFIG_DRM_I810=m
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
CONFIG_DRM_I915_FBDEV=y
@@ -7191,6 +7186,7 @@ CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
+# CONFIG_DEBUG_PREEMPT is not set

#
# Lock Debugging (spinlocks, mutexes, etc...)
@@ -7217,9 +7213,11 @@ CONFIG_DEBUG_BUGVERBOSE=y
#
# RCU Debugging
#
+# CONFIG_PROV...

diff --git a/boot/config-3.13.0-6-generic b/boot/config-3.13.0-6-lowlatency
index 2684575..e86aff9 100644
--- a/boot/config-3.13.0-6-generic
+++ b/boot/config-3.13.0-6-lowlatency
@@ -1,6 +1,6 @@
 #
 # Automatically generated file; DO NOT EDIT.
-# Linux/i386 3.13.0-6-generic Kernel Configuration
+# Linux/i386 3.13.0-6-lowlatency Kernel Configuration
 #
 # CONFIG_64BIT is not set
 CONFIG_X86_32=y
@@ -64,7 +64,7 @@ CONFIG_KERNEL_GZIP=y
 # CONFIG_KERNEL_LZO is not set
 # CONFIG_KERNEL_LZ4 is not set
 CONFIG_DEFAULT_HOSTNAME="(none)"
-CONFIG_VERSION_SIGNATURE="Ubuntu 3.13.0-6.23-generic 3.13.0"
+CONFIG_VERSION_SIGNATURE="Ubuntu 3.13.0-6.23-lowlatency 3.13.0"
 CONFIG_SWAP=y
 CONFIG_SYSVIPC=y
 CONFIG_SYSVIPC_SYSCTL=y
@@ -86,7 +86,7 @@ CONFIG_GENERIC_IRQ_CHIP=y
 CONFIG_IRQ_DOMAIN=y
 # CONFIG_IRQ_DOMAIN_DEBUG is not set
 CONFIG_IRQ_FORCED_THREADING=y
-# CONFIG_IRQ_FORCED_THREADING_DEFAULT is not set
+CONFIG_IRQ_FORCED_THREADING_DEFAULT=y
 CONFIG_SPARSE_IRQ=y
 CONFIG_CLOCKSOURCE_WATCHDOG=y
 CONFIG_KTIME_SCALAR=y
@@ -121,14 +121,15 @@ CONFIG_TASK_IO_ACCOUNTING=y
 #
 # RCU Subsystem
 #
-CONFIG_TREE_RCU=y
-# CONFIG_PREEMPT_RCU is not set
+CONFIG_TREE_PREEMPT_RCU=y
+CONFIG_PREEMPT_RCU=y
 CONFIG_RCU_STALL_COMMON=y
 CONFIG_RCU_FANOUT=32
 CONFIG_RCU_FANOUT_LEAF=16
 # CONFIG_RCU_FANOUT_EXACT is not set
 CONFIG_RCU_FAST_NO_HZ=y
 # CONFIG_TREE_RCU_TRACE is not set
+# CONFIG_RCU_BOOST is not set
 # CONFIG_RCU_NOCB_CPU is not set
 # CONFIG_IKCONFIG is not set
 CONFIG_LOG_BUF_SHIFT=17
@@ -222,7 +223,6 @@ CONFIG_HAVE_OPROFILE=y
 CONFIG_OPROFILE_NMI_TIMER=y
 CONFIG_KPROBES=y
 CONFIG_JUMP_LABEL=y
-CONFIG_OPTPROBES=y
 CONFIG_KPROBES_ON_FTRACE=y
 CONFIG_UPROBES=y
 # CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set
@@ -342,11 +342,6 @@ CONFIG_PREEMPT_NOTIFIERS=y
 CONFIG_PADATA=y
 CONFIG_ASN1=y
 CONFIG_UNINLINE_SPIN_UNLOCK=y
-CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
-CONFIG_INLINE_READ_UNLOCK=y
-CONFIG_INLINE_READ_UNLOCK_IRQ=y
-CONFIG_INLINE_WRITE_UNLOCK=y
-CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
 CONFIG_MUTEX_SPIN_ON_OWNER=y
 CONFIG_FREEZER=y
 
@@ -438,8 +433,9 @@ CONFIG_NR_CPUS=8
 CONFIG_SCHED_SMT=y
 CONFIG_SCHED_MC=y
 # CONFIG_PREEMPT_NONE is not set
-CONFIG_PREEMPT_VOLUNTARY=y
-# CONFIG_PREEMPT is not set
+# CONFIG_PREEMPT_VOLUNTARY is not set
+CONFIG_PREEMPT=y
+CONFIG_PREEMPT_COUNT=y
 CONFIG_X86_LOCAL_APIC=y
 CONFIG_X86_IO_APIC=y
 CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
@@ -534,10 +530,10 @@ CONFIG_EFI_STUB=y
 CONFIG_SECCOMP=y
 CONFIG_CC_STACKPROTECTOR=y
 # CONFIG_HZ_100 is not set
-CONFIG_HZ_250=y
+# CONFIG_HZ_250 is not set
 # CONFIG_HZ_300 is not set
-# CONFIG_HZ_1000 is not set
-CONFIG_HZ=250
+CONFIG_HZ_1000=y
+CONFIG_HZ=1000
 CONFIG_SCHED_HRTICK=y
 CONFIG_KEXEC=y
 CONFIG_CRASH_DUMP=y
@@ -4881,7 +4877,6 @@ CONFIG_DRM_NOUVEAU=m
 CONFIG_NOUVEAU_DEBUG=5
 CONFIG_NOUVEAU_DEBUG_DEFAULT=3
 CONFIG_DRM_NOUVEAU_BACKLIGHT=y
-CONFIG_DRM_I810=m
 CONFIG_DRM_I915=m
 CONFIG_DRM_I915_KMS=y
 CONFIG_DRM_I915_FBDEV=y
@@ -7191,6 +7186,7 @@ CONFIG_PANIC_ON_OOPS_VALUE=0
 CONFIG_SCHED_DEBUG=y
 CONFIG_SCHEDSTATS=y
 CONFIG_TIMER_STATS=y
+# CONFIG_DEBUG_PREEMPT is not set
 
 #
 # Lock Debugging (spinlocks, mutexes, etc...)
@@ -7217,9 +7213,11 @@ CONFIG_DEBUG_BUGVERBOSE=y
 #
 # RCU Debugging
 #
+# CONFIG_PROVE_RCU_DELAY is not set
 # CONFIG_SPARSE_RCU_POINTER is not set
 # CONFIG_RCU_TORTURE_TEST is not set
 CONFIG_RCU_CPU_STALL_TIMEOUT=60
+# CONFIG_RCU_CPU_STALL_VERBOSE is not set
 # CONFIG_RCU_CPU_STALL_INFO is not set
 # CONFIG_RCU_TRACE is not set
 # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
@@ -7254,6 +7252,7 @@ CONFIG_FTRACE=y
 CONFIG_FUNCTION_TRACER=y
 CONFIG_FUNCTION_GRAPH_TRACER=y
 # CONFIG_IRQSOFF_TRACER is not set
+# CONFIG_PREEMPT_TRACER is not set
 CONFIG_SCHED_TRACER=y
 CONFIG_FTRACE_SYSCALLS=y
 CONFIG_TRACER_SNAPSHOT=y

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#18

The diff does not reveal any huge differences between lowlatency and generic, but looking at it maybe others can gen an ideas as to wht might be causing this all-over-the-place panic.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-02:

#19

It seems that CPU gets blocked, so perhaps is something of theese:
+CONFIG_IRQ_FORCED_THREADING_DEFAULT=y
-CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
-CONFIG_INLINE_READ_UNLOCK=y
-CONFIG_INLINE_READ_UNLOCK_IRQ=y
-CONFIG_INLINE_WRITE_UNLOCK=y
-CONFIG_INLINE_WRITE_UNLOCK_IRQ=y

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#20

Apparently CONFIG_IRQ_FORCED_THREADING_DEFAULT is not an upstream config flag.

The resulting param force_irqthreads is not set no true unless "threadirqs" are on the kernel commandline.

In the problematic kernel it is set to true by default - something that will never happen on a vanilla kernel.

It can be turned off using "nothreadirqs" on the commandline - which is exactly what I'm going to try now.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#21

Well - nothreadirq has the effect that my virtualbox crashes. Someway around the time where I would expect the whole system to crash.

Jaime - I thing adding "nothreadirqs" would be something that you should try also.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-02: Re: [Bug 1275116] Re: lowlatency-flavour crashes and locks up alot

#23

ok i will try tomorrow

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-02:

#22

Ok, I will try tomorrow

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-02:

#24

I can add that my system locked up in the end but the characteristics of that crash was for sure different. So no real cure for me. Looking forward to hearing what it does to your side of things.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#25

How can I add the "nothreadsirqs" setting? I open grub console and type it, but I got an error. So I put it in /etc/grub/defaults and execute update-grub. It's that ok?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-03:

#26

Problably.... but I just press and hold "shift" to get the bootmenu. This I press 'e' to edit the current entry and add "nothreadirqs" to the linux-line.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#27

I think I have done it in the wrong way. I will check when I return home.

Søren Holm <email address hidden> wrote:

Problably.... but I just press and hold "shift" to get the bootmenu.
This I press 'e' to edit the current entry and add "nothreadirqs" to the
linux-line.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1275116

Title:
lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

I will add crashdumps when I get crashes that do not just lockup the
machine but currently I have only seem complete lockups with 3.13

So the essense is :

3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text.
3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: sgh 2176 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic N/A
   linux-firmware 1.123
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions

I think I have done it in the wrong way. I will check when I return home.

Søren Holm <sgh@sgh.dk> wrote:

Problably.... but I just press and hold "shift" to get the bootmenu.
This I press 'e' to edit the current entry and add "nothreadirqs" to the
linux-line.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1275116

Title:
  lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

I will add crashdumps when I get crashes that do not just lockup the
  machine but currently I have only seem complete lockups with 3.13

So the essense is :

3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text.
  3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked.

ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  sgh        2176 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic  N/A
   linux-firmware                            1.123
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#28

Ok, it seems to be working. However I will be checking if it breaks.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#29

This is working fine. You are using ubuntu through virtualbox? Perhaps if you use only one processor the problem goes off.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-03:

#30

No I'm running Ubuntu on the host system. I run Wintendo in virtualbox.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#31

Ah ok! isn't there any change in config related to virtualization?

Søren Holm <email address hidden> wrote:

No I'm running Ubuntu on the host system. I run Wintendo in virtualbox.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1275116

Title:
lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

I will add crashdumps when I get crashes that do not just lockup the
machine but currently I have only seem complete lockups with 3.13

So the essense is :

3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text.
3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: sgh 2176 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic N/A
   linux-firmware 1.123
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions

Ah ok! isn't there any change in config related to virtualization?

Søren Holm <sgh@sgh.dk> wrote:

No I'm running Ubuntu on the host system. I run Wintendo in virtualbox.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1275116

Title:
  lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

I will add crashdumps when I get crashes that do not just lockup the
  machine but currently I have only seem complete lockups with 3.13

So the essense is :

3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text.
  3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked.

ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  sgh        2176 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic  N/A
   linux-firmware                            1.123
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions

Joseph Salisbury (jsalisbury) on 2014-02-03

Changed in linux (Ubuntu):
importance:	Undecided → High
tags:	added: kernel-da-key linux-lowlatency

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-03:

#32

I built an amd64 lowlatency test kernel with PREEMPT disabled. This kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1275116/

Can you test this kernel and see if it also exhibits this bug? Please note, this is a diagnostic kernel and not a fix.

Thanks in advance!

tags:

added: kernel-key

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-03:

#33

@Soren, I see you have an i686 machine, so I'll build a 32 bit kernel as well.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#34

I will test it. Should I put the kernel option off?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#35

Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.13.0-6-lowlatency.postinst line 1025.
dpkg: error processing package linux-image-3.13.0-6-lowlatency (--install):
subprocess installed post-installation script returned error exit status 2
Setting up linux-tools-3.13.0-6-lowlatency (3.13.0-6.23~lp1275116PREEMPTDISABLED) ...
Errors were encountered while processing:
linux-image-3.13.0-6-lowlatency

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#36

Ok sorry I put my foot on it. Ignore last message.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#37

It seems to work all right. But I thought it was due to someone of theese options:
+CONFIG_IRQ_FORCED_THREADING_DEFAULT=y
-CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
-CONFIG_INLINE_READ_UNLOCK=y
-CONFIG_INLINE_READ_UNLOCK_IRQ=y
-CONFIG_INLINE_WRITE_UNLOCK=y
-CONFIG_INLINE_WRITE_UNLOCK_IRQ=y

It seems I was wrong.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-03:

#38

@Soren, there is an i386 kernel available at that link now as well.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-03:

#39

I can't see it - am I looking the wrong place?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-03:

#40

I thought preemtible kernel wasn't the problem. I don't know, but the fix worked for me, so thanks!

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-03:

#41

But preemptiveness is the whole point of lowlatency.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-04:

#42

Sorry, Soren. The kernel is here now:
http://kernel.ubuntu.com/~jsalisbury/lp1275116/

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#43

Bad news, kernel got stuck again.

Joseph can you pass me a link where I can learn how to build a ubuntu's style kernel? I can try some changes by my own and report the results. I have built some kernels by my own, so I know how to do it with make-kpkg. But I think i must use debian/config style.

Thanks!

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-04:

#44

@Jamie Perez,

There is some information on building Ubuntu kernels here:

https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-04:

#45

For me it for sure improves the situation. But problably my system will crash again like Jaime. I'll leave it to die and report back in around 6 hours with the result.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#46

disable CONFIG_IRQ_FORCED_THREADING_DEFAULT Edit (372 bytes, text/plain)

I will try those changes and report.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#47

Ok perhaps it was a bad idea trying it by my own

/linux-source-3.13.0 is not clean, please run 'make mrproper'
in the '/home/jaime/linux-source-3.13.0/linux-source-3.13.0' directory.
make[4]: *** [prepare3] Error 1
make[3]: *** [sub-make] Error 2
make[2]: *** [prepare] Error 2
make[1]: *** [sub-make] Error 2

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#48

Should I change this?
CONFIG_VERSION_SIGNATURE=""

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-04:

#49

I'll also see if I can reproduce this bug. Is there a specific test case that causes the bug to happen? Do you run a certain application or workload?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#50

It hapens when I overload PC, i think.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#51

I have been able to build the kernel ^^. However I put version 23 and I think that's the version you used, too. I will try the new kernel and tell you how it was.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#52

blocked Edit (4.5 KiB, text/plain)

Nah, it got blocked again

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#53

Ah! sorry, but the change I made wasn't made in the kernel. I don't know why. I'm rebuilding.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-04:

#54

I'm using the new kernel and it seems to work properly.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-04:

#55

Thanks for the update, Jamie. Did you modify specific config options with your new kernel? If so, can you post the details?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-04:

#56

The problem is NOT fixed in linux-image-3.13.0-7-lowlatency

Ubuntu Foundations Team Bug Bot (crichton) on 2014-02-05

tags:

added: patch

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#57

I have uploaded a patch file in post #46 . I only changed a thing.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-05:

#58

Jospeh: Your lowlatency kernel locks up in my dual-screen configuration at work. ;(

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#59

I will upload a kernel this afternoon

Søren Holm <email address hidden> wrote:

Jospeh: Your lowlatency kernel locks up in my dual-screen configuration
at work. ;(

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1275116

Title:
lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

I will add crashdumps when I get crashes that do not just lockup the
machine but currently I have only seem complete lockups with 3.13

So the essense is :

3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text.
3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: sgh 2176 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic N/A
   linux-firmware 1.123
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions

I will upload a kernel this afternoon

Søren Holm <sgh@sgh.dk> wrote:

Jospeh: Your lowlatency kernel locks up in my dual-screen configuration
at work. ;(

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1275116

Title:
  lowlatency-flavour crashes and locks up alot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
  this morning. I have the crashdums, but I figured that it might have
  been solved in 3.13. Unfortunatly it seems like it is not.

I will add crashdumps when I get crashes that do not just lockup the
  machine but currently I have only seem complete lockups with 3.13

So the essense is :

3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text.
  3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked.

ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-6-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  sgh        2176 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 31 23:38:10 2014
  InstallationDate: Installed on 2013-12-24 (38 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224)
  MachineType: LENOVO 2356GCG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-6-generic N/A
   linux-backports-modules-3.13.0-6-generic  N/A
   linux-firmware                            1.123
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET31WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356GCG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2356GCG
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#60

My "fix" failed.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#61

new config Edit (330 bytes, text/plain)

Testing new config

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#62

only1000HZ(seems to be working).patch Edit (1.1 KiB, text/plain)

This seems to be working on my case. But nearly all pros of lowlatency are lost

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-05:

#63

Thanks, Jamie. Was the fix that failed in comment #60 the same fix in comment #62?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#64

1000HZ enabled, irqforced enabled preempt disabled (doesn't work) Edit (538 bytes, text/plain)

no, in #62 one i only activated the 1000Hz option. Now I will try another change.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#65

Joseph, I think the last one is the same than the one you uploaded, so I'm going to omit this check.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#66

disable irq forced (doesn't work) Edit (519 bytes, text/plain)

I think this one was the first I tried and didn't worked

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#67

My PC has been switched on for 6 hours and still works with patch in #62.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-05:

#68

Thanks for the added information, Jamie. Have you tried various combinations of the three parameters:

CONFIG_IRQ_FORCED_THREADING_DEFAULT=n
CONFIG_PREEMPT=n
CONFIG_PREEMPT_RCU=n

It would be good to know if we only need to disable one of these parameters. In particular it would be good to know if setting CONFIG_IRQ_FORCED_THREADING_DEFAULT to n and the two PREEMPT options to y also resolves the bug. I know we tried using the nothreadirqs option, but it would be good to confirm by disabling it in the config.

I can build you a kernel with CONFIG_IRQ_FORCED_THREADING_DEFAULT un-set, unless you want to build one yourself?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#69

I have tryed than option too, I think

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#70

Well I'm having issues with writing the version string, because I change it and nothing happens. I suppose you mean the patch in #64. I think that we have check that one, but I'm not sure.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#71

yes in #46 i upload changes and I think I made what you say.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-05:

#72

So the only config that is working until now is #62

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#73

https://bugzilla.kernel.org/show_bug.cgi?id=65871

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#74

commit1.txt Edit (3.6 KiB, text/plain)

In this change they say something about CPU lockups, so perhaps they have found the solution

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#75

bug 1004313

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#76

They say that using acpì=off, idle=poll or maxcpus=0 the problem is gone.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-07:

#77

I'll try that ASAP

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#78

idle=poll is working, but I have read that CPU can overheat with that option.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#79

idle=poll doesn't work

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#80

acpi=off and maxcpus=0 don't work either. I have filled a bug in bugzilla.kernel.com

https://bugzilla.kernel.org/show_bug.cgi?id=70211

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#81

vboxdisabled2.log Edit (4.8 KiB, text/plain)

cat /etc/modprobe.d/blacklist
blacklist vboxpci
blacklist vboxnetadp
blacklist vboxnetflt
blacklist vboxdrv

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-07:

#82

Yeah - I experience most crashes when virtualbox is running.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#83

but it didn't work:S

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-07:

#84

The latest mainline 3.14-rc1 kernel is now available. It might be a good test to see if this bug is already fixed in mainline. The 3.14-rc1 kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc1-trusty/

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-07:

#85

Same thing. Running virtual box and loading both host and guest system 100% crashes the system.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#86

I'm downloading and installing

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#87

But Søren, your system only breaks when you use virtualbox?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#88

I can use virtualbox without any problem

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-07:

#89

That's right. So maybe I'm no experiencing the same problem as you. Nevertheless the crashdumps we posted in the beginning looked similar....... so I don't know.

Have you tried running virtualbox with some cpu load on both host and guest os? nothreadirqs did make a difference in the time it took before a crash occurred..

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-07:

#90

I get a crash sudently, doing nothing especial.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-08:

#91

v3.14-rc1-trusty gets blocked too.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-08:

#92

testing 3.13.0-8-lowlatency

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-08:

#93

.13.0-8-lowlatency crashes for me.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-08:

#94

For me too

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-08:

#95

My ubuntu has broken up when trying to fix another bug. I'm reinstalling, so I will tell you if that fix the problem.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-08:

#96

I will install ubuntu 14.04 in virtualbox, because I want to be able to use my PC and I was having too much bugs with 14.04. So I will tell you if I still have the problem.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-08:

#97

That's a VERY good idea. I mean if you have an issue in virtualbox then everyone will have that same issue.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-09:

#98

Ubuntu is installed with lowlatency kernel and seems to work properly. I will tell you if something happens.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-10:

#99

The upstream 3.13.2 kernel is now available. Can you test this kernel to see if it still exhibits the bug? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.2-trusty/

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-10:

#100

My ubuntu crashed and i had to reinstal. no im running 13.10 instead of
14.04 but i will try the kernel and tell you.
On Feb 10, 2014 3:15 PM, "Joseph Salisbury" <email address hidden>
wrote:

> The upstream 3.13.2 kernel is now available. Can you test this kernel to
> see if it still exhibits the bug? It can be downloaded from:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.2-trusty/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1275116
>
> Title:
> lowlatency-flavour crashes and locks up alot
>
> Status in "linux" package in Ubuntu:
> Confirmed
>
> Bug description:
> The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
> this morning. I have the crashdums, but I figured that it might have
> been solved in 3.13. Unfortunatly it seems like it is not.
>
> I will add crashdumps when I get crashes that do not just lockup the
> machine but currently I have only seem complete lockups with 3.13
>
> So the essense is :
>
> 3.11-lowlatency crashed 10 time today most of the crashes reached the
> console so I could see the panic text.
> 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich.
> During next reboot it also locked.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: linux-image-3.13.0-6-lowlatency (not installed)
> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
> Uname: Linux 3.13.0-6-generic i686
> ApportVersion: 2.13.2-0ubuntu2
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: sgh 2176 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Fri Jan 31 23:38:10 2014
> InstallationDate: Installed on 2013-12-24 (38 days ago)
> InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386
> (20131224)
> MachineType: LENOVO 2356GCG
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic
> root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.13.0-6-generic N/A
> linux-backports-modules-3.13.0-6-generic N/A
> linux-firmware 1.123
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 07/02/2012
> dmi.bios.vendor: LENOVO
> dmi.bios.version: G7ET31WW (1.13 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 2356GCG
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: No Asset Information
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: Not Available
> dmi.modalias:
> dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
> dmi.product.name: 2356GCG
> dmi.product.version: ThinkPad T430s
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions
>

My ubuntu crashed and i had to reinstal. no im running 13.10 instead of
14.04 but i will try the kernel and tell you.
On Feb 10, 2014 3:15 PM, "Joseph Salisbury" <joseph.salisbury@canonical.com>
wrote:

> The upstream 3.13.2 kernel is now available. Can you test this kernel to
> see if it still exhibits the bug? It can be downloaded from:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.2-trusty/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1275116
>
> Title:
>   lowlatency-flavour crashes and locks up alot
>
> Status in "linux" package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
>   this morning. I have the crashdums, but I figured that it might have
>   been solved in 3.13. Unfortunatly it seems like it is not.
>
>   I will add crashdumps when I get crashes that do not just lockup the
>   machine but currently I have only seem complete lockups with 3.13
>
>   So the essense is :
>
>   3.11-lowlatency crashed 10 time today most of the crashes reached the
> console so I could see the panic text.
>   3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich.
> During next reboot it also locked.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-6-lowlatency (not installed)
>   ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
>   Uname: Linux 3.13.0-6-generic i686
>   ApportVersion: 2.13.2-0ubuntu2
>   Architecture: i386
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  sgh        2176 F.... pulseaudio
>   CurrentDesktop: KDE
>   Date: Fri Jan 31 23:38:10 2014
>   InstallationDate: Installed on 2013-12-24 (38 days ago)
>   InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386
> (20131224)
>   MachineType: LENOVO 2356GCG
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic
> root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>    linux-restricted-modules-3.13.0-6-generic N/A
>    linux-backports-modules-3.13.0-6-generic  N/A
>    linux-firmware                            1.123
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/02/2012
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G7ET31WW (1.13 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 2356GCG
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 2356GCG
>   dmi.product.version: ThinkPad T430s
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions
>

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-10:

#101

Ok, I'm testing it. I'll tell you how it was.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-10:

#102

It seems to work properly. But virtual-box drivers are not installed, because dkms failed. Perhaps there lays the problem.

Jaime Pérez (jaime-91) on 2014-02-10

affects:

linux → virtualbox

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-11:

#103

So the 3.13.2 kernel does not seem to exhibit this bug? Is that only in virtual-box? Can you test to see if it also resolves the bug on bare-metal as well?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-11:

#104

The test I made was without virtualbox (bare-metal). In the virtualized one I don't even have the problem with 3.13.1. So, in my view, the problem has to do with virtual-box drivers or something related to it.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-11:

#105

v3.14-rc2-trusty also crashes.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-11:

#106

@Soren, @Jamie,

Ok, so just to confirm, this bug only happens if the virtualbox drivers are installed and loaded? If they are not, the bug does not happen on a bare-metal system?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-11:

#107

I can't try it without changing of distro. @Soren, can you make a blacklist for vboxpci vboxnetadp vboxnetflt vboxdrv, please? I tryied it once, but I should had done something badly, because it didn't seem to work.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-11:

#108

@Joseph thats problably correct. I won't need virtualbox tomorrow. So I will uninstall it and use the latest lowlatency kernel and report back.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-11:

#109

Oh welll .... I can now conclude that my system can lock during boot like in #5. And that even if virtual box is not at all installed.

So virtualbox clearly pushes thing, but the preempt-stuff can tip by itself also.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-12:

#110

you have uninstalled vb? but are its modules disabled?
On Feb 12, 2014 12:16 AM, "Søren Holm" <email address hidden> wrote:

> Oh welll .... I can now conclude that my system can lock during boot
> like in #5. And that even if virtual box is not at all installed.
>
> So virtualbox clearly pushes thing, but the preempt-stuff can tip by
> itself also.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1275116
>
> Title:
> lowlatency-flavour crashes and locks up alot
>
> Status in Virtualbox:
> New
> Status in "linux" package in Ubuntu:
> Confirmed
>
> Bug description:
> The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
> this morning. I have the crashdums, but I figured that it might have
> been solved in 3.13. Unfortunatly it seems like it is not.
>
> I will add crashdumps when I get crashes that do not just lockup the
> machine but currently I have only seem complete lockups with 3.13
>
> So the essense is :
>
> 3.11-lowlatency crashed 10 time today most of the crashes reached the
> console so I could see the panic text.
> 3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich.
> During next reboot it also locked.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: linux-image-3.13.0-6-lowlatency (not installed)
> ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
> Uname: Linux 3.13.0-6-generic i686
> ApportVersion: 2.13.2-0ubuntu2
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: sgh 2176 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Fri Jan 31 23:38:10 2014
> InstallationDate: Installed on 2013-12-24 (38 days ago)
> InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386
> (20131224)
> MachineType: LENOVO 2356GCG
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic
> root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.13.0-6-generic N/A
> linux-backports-modules-3.13.0-6-generic N/A
> linux-firmware 1.123
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 07/02/2012
> dmi.bios.vendor: LENOVO
> dmi.bios.version: G7ET31WW (1.13 )
> dmi.board.asset.tag: Not Available
> dmi.board.name: 2356GCG
> dmi.board.vendor: LENOVO
> dmi.board.version: Not Defined
> dmi.chassis.asset.tag: No Asset Information
> dmi.chassis.type: 10
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: Not Available
> dmi.modalias:
> dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
> dmi.product.name: 2356GCG
> dmi.product.version: ThinkPad T430s
> dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/virtualbox/+bug/1275116/+subscriptions
>

you have uninstalled vb? but are its modules disabled?
On Feb 12, 2014 12:16 AM, "Søren Holm" <sgh@sgh.dk> wrote:

> Oh welll .... I can now conclude that my system can lock during boot
> like in #5. And that even if virtual box is not at all installed.
>
> So virtualbox clearly pushes thing, but the preempt-stuff can tip by
> itself also.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1275116
>
> Title:
>   lowlatency-flavour crashes and locks up alot
>
> Status in Virtualbox:
>   New
> Status in "linux" package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The 3.11 flavour that where upgraded to 3.13 today crashed 10 times
>   this morning. I have the crashdums, but I figured that it might have
>   been solved in 3.13. Unfortunatly it seems like it is not.
>
>   I will add crashdumps when I get crashes that do not just lockup the
>   machine but currently I have only seem complete lockups with 3.13
>
>   So the essense is :
>
>   3.11-lowlatency crashed 10 time today most of the crashes reached the
> console so I could see the panic text.
>   3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich.
> During next reboot it also locked.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-6-lowlatency (not installed)
>   ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
>   Uname: Linux 3.13.0-6-generic i686
>   ApportVersion: 2.13.2-0ubuntu2
>   Architecture: i386
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  sgh        2176 F.... pulseaudio
>   CurrentDesktop: KDE
>   Date: Fri Jan 31 23:38:10 2014
>   InstallationDate: Installed on 2013-12-24 (38 days ago)
>   InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386
> (20131224)
>   MachineType: LENOVO 2356GCG
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic
> root=UUID=6376d4d7-bb9e-4488-bb5f-798e6c41f3fc ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>    linux-restricted-modules-3.13.0-6-generic N/A
>    linux-backports-modules-3.13.0-6-generic  N/A
>    linux-firmware                            1.123
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/02/2012
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: G7ET31WW (1.13 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 2356GCG
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 2356GCG
>   dmi.product.version: ThinkPad T430s
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/virtualbox/+bug/1275116/+subscriptions
>

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-12:

#111

Well ... virtualbox (and virtualbox-dkms) is uninstalled. Soe the modules are simply not there anymore.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-12:

#112

ohh then i was wrong:( if you install ubuntu 13.10 and upgrade the kernel
does the problem fade away?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-12:

#113

Yes - I ran 13.10 from august 2013 until december 2013 with no issues at all.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-12:

#114

But, I mean, did you ran 13.10 with 3.13-lowlatency kernel? Or with the 3.11-lowlatency one?

no longer affects:

virtualbox

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-12:

#115

The version that was in 13.10 at that time - problably 3.11-lowlatency.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-12:

#116

in my view it has to do with ubuntu 14.04, not with the kernel

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-12:

#117

I got a lock in Ubuntu 13.10, when playing half life. 2 on a row. I was using lowlatency, so perhaps its the same error. I have to install netconsole again.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-13:

#118

As an additional data point, can you see if this bug also happens if you boot the -generic kernel with the threadirqs boot parameter?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-13:

#119

Crash with 3.13.0-8-generic #28 booted with "threadirqs" Edit (1.2 MiB, image/jpeg)

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-13:

#120

Crash with 3.13.0-8-generic #28 booted with "threadirqs" Edit (1.2 MiB, image/jpeg)

Great suggestion. It crashes 4 out of 5 boots for me. All of them with simmilar lock during some systemd-udev thing and a stuck CPU.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-13:

#121

My new attachment is btw. created with the virtualbox driver out of the way just to be sure.

https://launchpadlibrarian.net/166218408/IMAG0510.jpg

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-13:

#122

ah is the same problem! you only put the irq thing?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-13:

#123

My cpu bloqued with nothreadirqs

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-13:

#124

Welll .... I removed "splash" and "quiet" to be able to see what is going on and then added "threadirqs".

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-13:

#125

It seems to be nothreadirqs. I'm reading some info about IRQ:

http://lwn.net/Articles/302043/

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-13:

#126

Well, I think I've understood. This command does that events can stop what the cpu was doing without making a thread(I don't know what exactly is that). So it seems that some event is blocking one of the CPUs because it kidnaps the CPU?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-14:

#127

My system blocked without nothreadirqs activated, so perhaps that wasn't the problem. I'm using generic now.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-14:

#128

CPU got stucked Edit (19.9 KiB, text/plain)

It's the same problem. CPU got stucked. But now I'm using generic and in kernel options I have only "debug ignore_loglevel".

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-14:

#129

netlog.txt Edit (19.9 KiB, text/plain)

Net console kernel trace output

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-14:

#130

http://pastebin.com/nJsi7ZGE

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-14:

#131

I'm changing a few things.

affects:

linux (Ubuntu) → linux-lowlatency (Ubuntu)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-02-14:

#132

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status:	New → Confirmed

Jaime Pérez (jaime-91) on 2014-02-14

affects:

linux-meta (Ubuntu) → linux (Ubuntu)

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-14:

#133

http://pastebin.com/Bt6DS7xS

I have gathered all kernel options related to IRQ. So perhaps one of these options fix the problem. Any idea?

Revision history for this message

Brad Figg (brad-figg) wrote on 2014-02-14: Status changed to Confirmed

#134

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-14:

#135

I get the lockup using fglrx but not xorg-radeon

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-18:

#136

Just to confirm, you can reproduce this bug with the -generic kernel if you add the threadirqs boot parameter? If that is the case, we may be able to test some older kernels with threadirqs and see if this is a regression. If it is, we can then bisect to identify the commit that introduced this regression.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-19:

#137

3.13.0-9.29 and well as 3.13.0-10 contains this change

[Config] lowlatency -- turn CONFIG_IRQ_FORCED_THREADING_DEFAULT off temporarily

I wonder if Andy Witcroft could add a comment wheather it relates to this bug.

Revision history for this message

Kaj Ailomaa (zequence) wrote on 2014-02-19: Re: [Bug 1275116] Re: lowlatency-flavour crashes and locks up alot

#138

On Wed, Feb 19, 2014, at 07:52 AM, Søren Holm wrote:
> 3.13.0-9.29 and well as 3.13.0-10 contains this change
>
> [Config] lowlatency -- turn CONFIG_IRQ_FORCED_THREADING_DEFAULT off
> temporarily
>
> I wonder if Andy Witcroft could add a comment wheather it relates to
> this bug.
>

We don't know yet. There is another bug that is affected by threadirqs.

Could you please make tests using lowlatency without threadirqs to see
if your problems disappear, and -generic with threadirqs, to see if the
problems there appears?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-19:

#139

For what it's worth running virtualbox I'm seeing the following.

* NO CRASH with generic kernel.
* CRASH with generic kernel with "threadirqs".
* NO CRASH with latest lowlatency kernel. Running 3 hours now. With previous lowlatency kernel a crash would happen within minutes..
* CRASH wqith previous lowlatency kernels with "nothreadirqs"

I hope it it is clear :)

Revision history for this message

Kaj Ailomaa (zequence) wrote on 2014-02-19:

#140

I'm the maintainer of the config for linux-lowlatency, btw. And, I had the kernel freeze only when a certain driver was loaded, with threadirqs enabled. Here's the bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1279081

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-19:

#141

we have made it and I think results are up

Revision history for this message

Kaj Ailomaa (zequence) wrote on 2014-02-19:

#142

On Wed, Feb 19, 2014, at 11:12 AM, Jaime Pérez wrote:
> we have made it and I think results are up
>
> --

I can't see if you tried running linux-generic with threadirqs though.
It seems to have made a difference for Søren.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-20:

#143

It would be good to know if when using the threadirqs parameter is a regression. If that is the case, we can bisect to identify the commit that introduced this.

Can you test the following kernels with the threadirqs parameter enabled and post back if any do not exhibit the bug:

v3.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/
v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/
v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring
v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

You don't have to test every kernel, just up until the kernel that first has this bug. If 3.2 has the bug, no need to test the rest.

Thanks in advance!

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-20:

#144

Trying

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-20:

#145

netconsole.log Edit (34.1 KiB, text/plain)

3.2 kernel failed

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-20:

#146

netconsole3.2.log Edit (34.1 KiB, text/plain)

Log

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-20:

#147

http://pastebin.com/TJ2f83ai

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-20:

#148

v3.12-trusty/ seems to work for me. So to me it seem to have broken between 3.12 and 3.13. For sure it did break since where saucy where around christmas, because I ran that with it's lowlatency until then.

I'll try v3.13-rc1-trusty to check.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-20:

#149

IMAG0515.jpg Edit (953.9 KiB, image/jpeg)

v3.13-rc1-trusty with "threadirqs"crashes with this trace.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-20:

#150

https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1275116/+attachment/3988700/+files/IMAG0515.jpg

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-20:

#151

Søren does 3.11 works for you with threadirqs, because i had some errors. I'm going to try it again.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-20:

#152

Yes indeed. But that sort of follows the fact that the saucy kernel - in all version until christmas ran perfectly. That means 3.11 only. There are 3.12 kernel at the her [1] but it does not look like they ever got into saucy for real.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-21:

#153

And have you tried actual 3.11 kernel? perhaps now it fails too and we can find the change that produce the error.

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-21:

#154

If you mean v3.11.10.4-saucy then it works without problems.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-21:

#155

BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-lowlatency root=UUID=94224f17-82cd-44ee-91a4-2243806ae66c ro debug ignore_loglevel threadirqs

has been up for 8 hours. Until now no probs.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-21:

#156

I have a doubt. In http://kernel.ubuntu.com/~kernel-ppa/mainline/ do developers of ubuntu post their kernels? Ubuntu uses those kernels later? I mean, changes done in the ppa are the same that in the ubuntu-kernel?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-21:

#157

And soren you said

The 3.11 flavour that where upgraded to 3.13 today crashed 10 times this morning. I have the crashdums, but I figured that it might have been solved in 3.13. Unfortunatly it seems like it is not.

I will add crashdumps when I get crashes that do not just lockup the machine but currently I have only seem complete lockups with 3.13

So the essense is :

3.11-lowlatency crashed 10 time today most of the crashes reached the console so I could see the panic text.
3.13-lowlatency crash 1 time 10 minuttes after first boot. No VT swtich. During next reboot it also locked.

but then 3.11 works OK?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-21:

#158

v3.11.10.4-saucy + "threadirqs" works OK, but the 3.11-lowlatency that trusty had back in January did not. This issue is getting me down as far as managing all the different version. :)

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-21:

#159

so the change that produced the error is there, no?

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-21:

#160

I don't know what changes has gone into the trusty 3.11 or 3.12 kernel. but if I should bisect based in "threadirqs" I would make 3.12 as good and 3.13 as bad based on my comment from yesterday :

<quote>
v3.12-trusty/ seems to work for me. So to me it seem to have broken between 3.12 and 3.13. For sure it did break since where saucy where around christmas, because I ran that with it's lowlatency until then.
</quote>

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-22:

#161

3.13.0-generic stucks with threadirqs

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-22:

#162

But 3.11.0-17-generic seems to work fine with threadirqs

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-24:

#163

Well then it's clear. Do we have a kernel bug on this?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-24:

#164

yes, I filled one. the link is somewhere upwards

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-24:

#165

There is some other bug reports that indicate this may be fixed in the mainline kernel. Can you see if that is the case by testing 3.14-rc4:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc4-trusty/

If the bug still exists there, then the other bug report may not be related.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-24:

#166

Testing

Revision history for this message

Søren Holm (sgh) wrote on 2014-02-24:

#167

If 3.14-rc4-lowlatency is as good to set with "threadirqs" as the generic kernel I can say that 3.14 works as a charm.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-24:

#168

It seems to be working for me, but it can fail it any moment...

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-24:

#169

The only bad point is that I don't have HDMI audio

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-02-25:

#170

That is good news that the bug appears to be fixed in 3.14-rc4. If it is stable and the bug is in fact gone after some time, we can perform a reverse bisect to identify the commit that fixes this in 3.14-rc4.

@jamie, it should be ok that HDMI is not working with this kernel. We are only interested in testing it to identify the commit that fixes this original bug. Once we find the fix, we will backport or cherry pick it into Trusty.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-25:

#171

nd how can we find the change?

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-02-26:

#172

https://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv3.x%2Ftesting%2Fpatch-3.14-rc4.xz;z=8642

This one says something about locks:
https://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv3.x%2Ftesting%2Fpatch-3.14-rc4.xz;z=8643

https://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv3.x%2Ftesting%2Fpatch-3.14-rc4.xz;z=2699

https://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv3.x%2Ftesting%2Fpatch-3.14-rc4.xz;z=2757

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-01:

#173

A backport to saucy is needed too.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-03-03:

#174

The following commit has landed in upstream v3.14-rc5:

commit a1227f3c1030e96ebc51d677d2f636268845c5fb
Author: Stanislaw Gruszka <email address hidden>
Date: Wed Feb 19 10:29:01 2014 +0100

usb: ehci: fix deadlock when threadirqs option is used

It has also been cc'd to stable, so it will make it's way into the stable releases through the usual stable update process.

Changed in linux (Ubuntu):
importance:	Undecided → High

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-03:

#175

Great!=)

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-03:

#176

Thanks for your help Joseph

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-03:

#177

Changes-for-ehci Edit (6.9 KiB, text/plain)

The solution of 3.14-rc5

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-03-03:

#178

I built a Trusty test kernel that has a cherry pick of commit a1227f3c1030e96ebc51d677d2f636268845c5fb. This test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1275116/

Can you test this kernel and confirm it resolves this bug? I built an i386 and amd_64 version of the kernel. You will need to install both the linux-image and linux-image-extra packages.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-03:

#179

I suppose that we have to test them with "threadirqs"

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-03-03:

#180

Yes, that would be great. I'll also build a lowlatency specific kernel and post it shortly.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-03-03:

#181

There are also lowlatency kernels available for testing at the link:
http://kernel.ubuntu.com/~jsalisbury/lp1275116/

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-04:

#182

It seems to work OK.

Joseph Salisbury (jsalisbury) on 2014-03-04

Changed in linux (Ubuntu):
status:	Confirmed → Fix Committed
Changed in linux-lowlatency (Ubuntu):
status:	Confirmed → Fix Committed

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-04:

#183

My system blocked again :( This time screen got black.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-03-05:

#184

Per comments #167 and #168, it sounds like this bug is resolved in v3.14-rc4. It also sounds like commit a1227f3c is not what fixes this. It is probably best for us to perform a reverse bisect to identify the real commit that fixes this in 3.14. The first step is to identify the first 3.14 kernel version that fixes the bug. We know 3.14-rc4 has the fix, so can you test 3.14-rc3:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc3-trusty/

If v3.14-rc3 also has the fix, then we would want to test 3.14-rc2, etc until we find the first kernel that exhibits the bug again.

Changed in linux-lowlatency (Ubuntu):
status:	Fix Committed → Confirmed
Changed in linux (Ubuntu):
status:	Fix Committed → Confirmed

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-05:

#185

The thing is that perhaps 3.14-rc4 has the error too, because with the patch my pc was switched on for all day and got stucked at night. I will try 3.14-rc3

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-05:

#186

Im testing rc5 again, only to see if it has the error and I didn't wait enogh

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-05:

#187

Changes related with deadlock Edit (9.7 KiB, text/plain)

I have looked for changes related with deadlocks. In 3.14-rc2 there is no-one, so we can avoid testing that one.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-05:

#188

netconsole3.2.log
[ 31.830432] usb 2-3.3: USB disconnect, device number 3
[ 71.972061] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 2, t=15002 jiffies)

3.14-rc1
Paul E. McKenney (54):
rcu: Break call_rcu() deadlock involving scheduler and perf

comment 3
1,1046,3231011669,-;BUG: unable to handle kernel NULL pointer dereference at (null)

netconsole.log
[ 11.924118] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
this bug appear before lockup

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-05:

#189

Now Im using rc5 and it seems to work fine.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-06:

#190

I had a lockup with rc4, so the change must be between rc4 and rc5, but it seems is not the one of ehci.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-06:

#191

Does http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc5-trusty/CHANGES show all changes, or only those produced by ubuntu team?

Revision history for this message

Søren Holm (sgh) wrote on 2014-03-06:

#192

3.13.0-16-lowlatency has no issues for me as far as I can see. At least I virtualbox running all day - no crashes.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-06:

#193

but you have issues with previous version?

Revision history for this message

Søren Holm (sgh) wrote on 2014-03-06:

#194

I've been busy, so I did not try the last versions that Joseph posted.

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-07:

#195

I have upgraded to 14.04 again. I'll download rc5, rc4 etc

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-07:

#196

Well, first I will test 3.13.0-16-lowlatency

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-07:

#197

3.13.0-16-lowlatency seems to be working fine

Revision history for this message

Jaime Pérez (jaime-91) wrote on 2014-03-08:

#198

Still works, so it seems fix has been released.

Jaime Pérez (jaime-91) on 2014-03-08

Changed in linux-lowlatency (Ubuntu):
status:	Confirmed → Fix Released
Changed in linux (Ubuntu):
status:	Confirmed → Fix Released

Ubuntu
linux-lowlatency package

lowlatency-flavour crashes and locks up alot

Bug Description

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	High	Unassigned
	linux-lowlatency (Ubuntu)	Fix Released	High	Unassigned

Ubuntulinux-lowlatency package

lowlatency-flavour crashes and locks up alot

Bug Description

Other bug subscribers

Patches

Bug attachments

Remote bug watches

Ubuntu
linux-lowlatency package