[Bug 2063435] Re: Radeon stacktrace during boot

2024-05-08 Thread Piotr Parczewski
Yes - apologies for the delay. Same result I'm afraid:

[Wed May  8 23:34:29 2024] [ cut here ]
[Wed May  8 23:34:29 2024] UBSAN: array-index-out-of-bounds in 
/build/linux-yrLejD/linux-6.8.0/drivers/gpu/drm/radeon/radeon_atombios.c:2718:34
[Wed May  8 23:34:29 2024] index 16 is out of range for type 'UCHAR [1]'
[Wed May  8 23:34:29 2024] CPU: 0 PID: 370 Comm: (udev-worker) Not tainted 
6.8.0-31-generic #31-Ubuntu
[Wed May  8 23:34:29 2024] Hardware name: To Be Filled By O.E.M. To Be Filled 
By O.E.M./E350M1, BIOS P2.10 03/06/2014
[Wed May  8 23:34:29 2024] Call Trace:
[Wed May  8 23:34:29 2024]  
[Wed May  8 23:34:29 2024]  dump_stack_lvl+0x48/0x70
[Wed May  8 23:34:29 2024]  dump_stack+0x10/0x20
[Wed May  8 23:34:29 2024]  __ubsan_handle_out_of_bounds+0xc6/0x110
[Wed May  8 23:34:29 2024]  radeon_atombios_parse_power_table_6+0x3ba/0x3e0 
[radeon]
[Wed May  8 23:34:29 2024]  radeon_atombios_get_power_modes+0x247/0x270 [radeon]
[Wed May  8 23:34:29 2024]  radeon_pm_init_dpm+0x8e/0x2f0 [radeon]
[Wed May  8 23:34:29 2024]  radeon_pm_init+0xd0/0x100 [radeon]
[Wed May  8 23:34:29 2024]  evergreen_init+0x158/0x400 [radeon]
[Wed May  8 23:34:29 2024]  radeon_device_init+0x540/0xa90 [radeon]
[Wed May  8 23:34:29 2024]  radeon_driver_load_kms+0xcc/0x2f0 [radeon]
[Wed May  8 23:34:29 2024]  drm_dev_register+0x12b/0x2a0
[Wed May  8 23:34:29 2024]  radeon_pci_probe+0xec/0x180 [radeon]
[Wed May  8 23:34:29 2024]  local_pci_probe+0x47/0xb0
[Wed May  8 23:34:29 2024]  pci_call_probe+0x55/0x1a0
[Wed May  8 23:34:29 2024]  pci_device_probe+0x84/0x120
[Wed May  8 23:34:29 2024]  really_probe+0x1c7/0x410
[Wed May  8 23:34:29 2024]  __driver_probe_device+0x8c/0x180
[Wed May  8 23:34:29 2024]  driver_probe_device+0x24/0xd0
[Wed May  8 23:34:29 2024]  __driver_attach+0x10b/0x210
[Wed May  8 23:34:29 2024]  ? __pfx___driver_attach+0x10/0x10
[Wed May  8 23:34:29 2024]  bus_for_each_dev+0x8d/0xf0
[Wed May  8 23:34:29 2024]  driver_attach+0x1e/0x30
[Wed May  8 23:34:29 2024]  bus_add_driver+0x156/0x260
[Wed May  8 23:34:29 2024]  driver_register+0x5e/0x130
[Wed May  8 23:34:29 2024]  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
[Wed May  8 23:34:29 2024]  __pci_register_driver+0x5e/0x70
[Wed May  8 23:34:29 2024]  radeon_module_init+0x4c/0xff0 [radeon]
[Wed May  8 23:34:29 2024]  do_one_initcall+0x5e/0x340
[Wed May  8 23:34:29 2024]  do_init_module+0xc0/0x2c0
[Wed May  8 23:34:29 2024]  load_module+0xba1/0xcf0
[Wed May  8 23:34:29 2024]  init_module_from_file+0x96/0x100
[Wed May  8 23:34:29 2024]  ? init_module_from_file+0x96/0x100
[Wed May  8 23:34:29 2024]  idempotent_init_module+0x11c/0x2b0
[Wed May  8 23:34:29 2024]  __x64_sys_finit_module+0x64/0xd0
[Wed May  8 23:34:29 2024]  x64_sys_call+0x1d6e/0x25c0
[Wed May  8 23:34:29 2024]  do_syscall_64+0x7f/0x180
[Wed May  8 23:34:29 2024]  ? do_syscall_64+0x8c/0x180
[Wed May  8 23:34:29 2024]  ? do_syscall_64+0x8c/0x180
[Wed May  8 23:34:29 2024]  ? do_syscall_64+0x8c/0x180
[Wed May  8 23:34:29 2024]  ? do_syscall_64+0x8c/0x180
[Wed May  8 23:34:29 2024]  ? do_syscall_64+0x8c/0x180
[Wed May  8 23:34:29 2024]  ? common_interrupt+0x54/0xb0
[Wed May  8 23:34:29 2024]  entry_SYSCALL_64_after_hwframe+0x73/0x7b
[Wed May  8 23:34:29 2024] RIP: 0033:0x77c1c092725d
[Wed May  8 23:34:29 2024] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 
1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 
05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b bb 0d 00 f7 d8 64 89 01 48
[Wed May  8 23:34:29 2024] RSP: 002b:7fffafec3788 EFLAGS: 0246 
ORIG_RAX: 0139
[Wed May  8 23:34:29 2024] RAX: ffda RBX: 6368501302c0 RCX: 
77c1c092725d
[Wed May  8 23:34:29 2024] RDX: 0004 RSI: 77c1c0c1c07d RDI: 
001e
[Wed May  8 23:34:29 2024] RBP: 7fffafec3840 R08: 0040 R09: 
7fffafec37d0
[Wed May  8 23:34:29 2024] R10: 77c1c0a03b20 R11: 0246 R12: 
77c1c0c1c07d
[Wed May  8 23:34:29 2024] R13: 0002 R14: 636850130260 R15: 
636850138fc0
[Wed May  8 23:34:29 2024]  
[Wed May  8 23:34:29 2024] ---[ end trace ]---
[Wed May  8 23:34:29 2024] [ cut here ]
[Wed May  8 23:34:29 2024] UBSAN: array-index-out-of-bounds in 
/build/linux-yrLejD/linux-6.8.0/drivers/gpu/drm/radeon/radeon_atombios.c:2706:39
[Wed May  8 23:34:29 2024] index 2 is out of range for type 
'ATOM_PPLIB_NONCLOCK_INFO [1]'
[Wed May  8 23:34:29 2024] CPU: 0 PID: 370 Comm: (udev-worker) Not tainted 
6.8.0-31-generic #31-Ubuntu
[Wed May  8 23:34:29 2024] Hardware name: To Be Filled By O.E.M. To Be Filled 
By O.E.M./E350M1, BIOS P2.10 03/06/2014
[Wed May  8 23:34:29 2024] Call Trace:
[Wed May  8 23:34:29 2024]  
[Wed May  8 23:34:29 2024]  dump_stack_lvl+0x48/0x70
[Wed May  8 23:34:29 2024]  dump_stack+0x10/0x20
[Wed May  8 23:34:29 2024]  __ubsan_handle_out_of_bounds+0xc6/0x110
[Wed May  8 23:34:29 2024]  radeon_atombios_parse_power_table_6+0x3d2/0x3e0 
[radeon]
[Wed May  8 

[Bug 2063435] [NEW] Radeon stacktrace during boot

2024-04-25 Thread Piotr Parczewski
Public bug reported:

Noble beta:

[Thu Apr 25 11:13:28 2024] [drm] radeon kernel modesetting enabled.
[Thu Apr 25 11:13:28 2024] radeon :00:01.0: vgaarb: deactivate vga console
[Thu Apr 25 11:13:28 2024] [drm] initializing kernel modesetting (PALM 
0x1002:0x9802 0x1849:0x9802 0x00).
[Thu Apr 25 11:13:28 2024] ATOM BIOS: AMD
[Thu Apr 25 11:13:28 2024] radeon :00:01.0: VRAM: 32M 0x - 
0x01FF (32M used)
[Thu Apr 25 11:13:28 2024] radeon :00:01.0: GTT: 1024M 0x0200 - 
0x41FF
[Thu Apr 25 11:13:28 2024] [drm] Detected VRAM RAM=32M, BAR=32M
[Thu Apr 25 11:13:28 2024] [drm] RAM width 32bits DDR
[Thu Apr 25 11:13:28 2024] [drm] radeon: 32M of VRAM memory ready
[Thu Apr 25 11:13:28 2024] [drm] radeon: 1024M of GTT memory ready.
[Thu Apr 25 11:13:28 2024] [drm] Loading PALM Microcode
[Thu Apr 25 11:13:29 2024] [drm] Internal thermal controller without fan control
[Thu Apr 25 11:13:29 2024] [ cut here ]
[Thu Apr 25 11:13:29 2024] UBSAN: array-index-out-of-bounds in 
/build/linux-OjsR9e/linux-6.8.0/drivers/gpu/drm/radeon/radeon_atombios.c:2718:34
[Thu Apr 25 11:13:29 2024] index 16 is out of range for type 'UCHAR [1]'
[Thu Apr 25 11:13:29 2024] CPU: 1 PID: 366 Comm: (udev-worker) Not tainted 
6.8.0-11-generic #11-Ubuntu
[Thu Apr 25 11:13:29 2024] Hardware name: To Be Filled By O.E.M. To Be Filled 
By O.E.M./E350M1, BIOS P2.10 03/06/2014
[Thu Apr 25 11:13:29 2024] Call Trace:
[Thu Apr 25 11:13:29 2024]  
[Thu Apr 25 11:13:29 2024]  dump_stack_lvl+0x48/0x70
[Thu Apr 25 11:13:29 2024]  dump_stack+0x10/0x20
[Thu Apr 25 11:13:29 2024]  __ubsan_handle_out_of_bounds+0xc6/0x110
[Thu Apr 25 11:13:29 2024]  radeon_atombios_parse_power_table_6+0x3ba/0x3e0 
[radeon]
[Thu Apr 25 11:13:29 2024]  radeon_atombios_get_power_modes+0x247/0x270 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_pm_init_dpm+0x8e/0x2f0 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_pm_init+0xd0/0x100 [radeon]
[Thu Apr 25 11:13:29 2024]  evergreen_init+0x158/0x400 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_device_init+0x540/0xa90 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_driver_load_kms+0xcc/0x2f0 [radeon]
[Thu Apr 25 11:13:29 2024]  drm_dev_register+0x12b/0x2a0
[Thu Apr 25 11:13:29 2024]  radeon_pci_probe+0xec/0x180 [radeon]
[Thu Apr 25 11:13:29 2024]  local_pci_probe+0x47/0xb0
[Thu Apr 25 11:13:29 2024]  pci_call_probe+0x55/0x1a0
[Thu Apr 25 11:13:29 2024]  pci_device_probe+0x84/0x120
[Thu Apr 25 11:13:29 2024]  really_probe+0x1c7/0x410
[Thu Apr 25 11:13:29 2024]  __driver_probe_device+0x8c/0x180
[Thu Apr 25 11:13:29 2024]  driver_probe_device+0x24/0xd0
[Thu Apr 25 11:13:29 2024]  __driver_attach+0x10b/0x210
[Thu Apr 25 11:13:29 2024]  ? __pfx___driver_attach+0x10/0x10
[Thu Apr 25 11:13:29 2024]  bus_for_each_dev+0x8d/0xf0
[Thu Apr 25 11:13:29 2024]  driver_attach+0x1e/0x30
[Thu Apr 25 11:13:29 2024]  bus_add_driver+0x156/0x260
[Thu Apr 25 11:13:29 2024]  driver_register+0x5e/0x130
[Thu Apr 25 11:13:29 2024]  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
[Thu Apr 25 11:13:29 2024]  __pci_register_driver+0x5e/0x70
[Thu Apr 25 11:13:29 2024]  radeon_module_init+0x4c/0xff0 [radeon]
[Thu Apr 25 11:13:29 2024]  do_one_initcall+0x5e/0x340
[Thu Apr 25 11:13:29 2024]  do_init_module+0xc0/0x2c0
[Thu Apr 25 11:13:29 2024]  load_module+0xba1/0xcf0
[Thu Apr 25 11:13:29 2024]  init_module_from_file+0x96/0x100
[Thu Apr 25 11:13:29 2024]  ? init_module_from_file+0x96/0x100
[Thu Apr 25 11:13:29 2024]  idempotent_init_module+0x11c/0x2b0
[Thu Apr 25 11:13:29 2024]  __x64_sys_finit_module+0x64/0xd0
[Thu Apr 25 11:13:29 2024]  do_syscall_64+0x77/0x140
[Thu Apr 25 11:13:29 2024]  ? do_syscall_64+0x83/0x140
[Thu Apr 25 11:13:29 2024]  ? switch_fpu_return+0x55/0xf0
[Thu Apr 25 11:13:29 2024]  ? syscall_exit_to_user_mode+0x97/0x1e0
[Thu Apr 25 11:13:29 2024]  ? do_syscall_64+0x83/0x140
[Thu Apr 25 11:13:29 2024]  ? switch_fpu_return+0x55/0xf0
[Thu Apr 25 11:13:29 2024]  ? syscall_exit_to_user_mode+0x97/0x1e0
[Thu Apr 25 11:13:29 2024]  ? do_syscall_64+0x83/0x140
[Thu Apr 25 11:13:29 2024]  ? sysvec_apic_timer_interrupt+0x4b/0xd0
[Thu Apr 25 11:13:29 2024]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[Thu Apr 25 11:13:29 2024] RIP: 0033:0x717ba4f2725d
[Thu Apr 25 11:13:29 2024] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 
1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 
05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b bb 0d 00 f7 d8 64 89 01 48
[Thu Apr 25 11:13:29 2024] RSP: 002b:7ffd5fa93148 EFLAGS: 0246 
ORIG_RAX: 0139
[Thu Apr 25 11:13:29 2024] RAX: ffda RBX: 5fbbfc5b3710 RCX: 
717ba4f2725d
[Thu Apr 25 11:13:29 2024] RDX: 0004 RSI: 717ba50fa07d RDI: 
001f
[Thu Apr 25 11:13:29 2024] RBP: 7ffd5fa93200 R08: 0040 R09: 
7ffd5fa93190
[Thu Apr 25 11:13:29 2024] R10: 717ba5003b20 R11: 0246 R12: 
717ba50fa07d
[Thu Apr 25 11:13:29 2024] R13: 0002 R14: 

[Bug 1632743] Re: Missing files from python-magnum 3.1.1-0~cloud0

2016-12-08 Thread Piotr Parczewski
I agree that 3.1.1-1 would come very useful in the main repo - currently
Openstack Kolla binary installation using Ubuntu is failing because of
this bug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632743

Title:
  Missing files from python-magnum 3.1.1-0~cloud0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1632743/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1607298] Re: auplink segfaults during docker engine startup

2016-07-28 Thread Piotr Parczewski
** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1607298/+attachment/4708650/+files/journal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607298

Title:
  auplink segfaults during docker engine startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1607298/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1607298] Re: auplink segfaults during docker engine startup

2016-07-28 Thread Piotr Parczewski
** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1607298/+attachment/4708649/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607298

Title:
  auplink segfaults during docker engine startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1607298/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1607298] [NEW] auplink segfaults during docker engine startup

2016-07-28 Thread Piotr Parczewski
Public bug reported:

auplink segfault entries can be observed in dmesg and journal after
booting machine with docker engine installed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: aufs-tools 1:3.2+20130722-1.1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Jul 28 12:12:11 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libgcc1 1:6.0.1-0ubuntu1
InstallationDate: Installed on 2016-06-02 (56 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: aufs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: aufs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Summary changed:

- auplink segfaults
+ auplink segfaults during docker engine startup

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607298

Title:
  auplink segfaults during docker engine startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aufs-tools/+bug/1607298/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

2016-07-27 Thread Piotr Parczewski
Same issue with 4.4.0-31-generic, stack trace:

[443830.036000] divide error:  [#1] SMP 
[443830.036583] Modules linked in: nf_conntrack_netlink xt_multiport xt_CT 
xt_mac xt_physdev xt_set ip_set_hash_net ip_set nfnetlink vhost_net vhost 
macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark vport_vxlan xt_CHECKSUM 
ip6table_raw nf_conntrack_ipv6 ip6table_mangle xt_connmark xt_comment 
iptable_raw iptable_mangle dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag 
ebtable_filter ebtables ip6table_filter ip6_tables ip_vs openvswitch 
nf_defrag_ipv6 xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter 
bridge aufs mpt3sas raid_class scsi_transport_sas mptctl mptbase binfmt_misc 
bonding xfs nls_iso8859_1 intel_rapl ipmi_ssif joydev input_leds 
x86_pkg_temp_thermal
[443830.039865]  intel_powerclamp coretemp sb_edac mei_me mei edac_core lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp 8250_fintek acpi_power_meter mac_hid 
kvm_intel acpi_pad kvm irqbypass ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 8021q garp 
mrp stp llc sunrpc autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
ses enclosure hid_generic crct10dif_pclmul ast crc32_pclmul i2c_algo_bit ttm 
ixgbe drm_kms_helper aesni_intel dca aes_x86_64 vxlan lrw ip6_udp_tunnel 
gf128mul syscopyarea glue_helper udp_tunnel ablk_helper sysfillrect cryptd 
usbhid sysimgblt fb_sys_fops hid ahci ptp drm libahci megaraid_sas pps_core 
mdio wmi fjes
[443830.045336] CPU: 10 PID: 13866 Comm: ceph-osd Not tainted 4.4.0-31-generic 
#50-Ubuntu
[443830.046219] Hardware name: Supermicro PIO-628U-TR4T+-ST031/X10DRU-i+, BIOS 
2.0 12/17/2015
[443830.047112] task: 881fc1260dc0 ti: 881fc126c000 task.ti: 
881fc126c000
[443830.048073] RIP: 0010:[]  [] 
task_numa_find_cpu+0x23c/0x710
[443830.049023] RSP: :881fc126fbd8  EFLAGS: 00010206
[443830.050042] RAX:  RBX: 881fc126fc78 RCX: 

[443830.051023] RDX:  RSI: 0001 RDI: 
881fef0c0800
[443830.052067] RBP: 881fc126fc40 R08: 0001069be1a6 R09: 
0015
[443830.053080] R10: 03d2 R11: 0df4 R12: 
883b2e116e00
[443830.054174] R13: 000c R14:  R15: 
fca6
[443830.055146] FS:  7fe71a644700() GS:881fffa8() 
knlGS:
[443830.056197] CS:  0010 DS:  ES:  CR0: 80050033
[443830.057206] CR2: 0aea4980 CR3: 001feed55000 CR4: 
001426e0
[443830.058296] Stack:
[443830.059327]  881fc126fbf8 813f0f4f 0100 
881fc1260dc0
[443830.060462]  0063 0129 00016d00 
0063
[443830.061607]  881fc1260dc0 881fc126fc78 015f 
01c2
[443830.062721] Call Trace:
[443830.063831]  [] ? cpumask_next_and+0x2f/0x40
[443830.064965]  [] task_numa_migrate+0x43e/0x9b0
[443830.066136]  [] ? physflat_send_IPI_mask+0xe/0x10
[443830.067227]  [] ? sched_clock+0x9/0x10
[443830.068314]  [] numa_migrate_preferred+0x79/0x80
[443830.069490]  [] task_numa_fault+0x7f4/0xd40
[443830.070987]  [] ? should_numa_migrate_memory+0x55/0x130
[443830.072113]  [] handle_mm_fault+0xbc0/0x1820
[443830.073248]  [] ? do_futex+0xd3/0x540
[443830.074395]  [] __do_page_fault+0x197/0x400
[443830.075538]  [] do_page_fault+0x22/0x30
[443830.076708]  [] page_fault+0x28/0x30
[443830.077862] Code: 55 b0 4c 89 f7 e8 25 c8 ff ff 48 8b 55 b0 49 8b 4e 78 48 
8b 82 d8 01 00 00 48 83 c1 01 31 d2 49 0f af 86 b0 00 00 00 4c 8b 73 78 <48> f7 
f1 48 8b 4b 20 49 89 c0 48 29 c1 48 8b 45 d0 4c 03 43 48 
[443830.080280] RIP  [] task_numa_find_cpu+0x23c/0x710
[443830.081470]  RSP 
[443830.086523] ---[ end trace 0f566374d1589a3d ]---

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568729

Title:
  divide error:  [#1] SMP in task_numa_migrate - handle_mm_fault

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs