[sle-beta] assert in dmi_check_system
Hui-Zhi
hui.zhi.zhao at suse.com
Wed Aug 29 02:50:21 MDT 2018
Hi Vincent,
Here's the issue on Bugzilla:
https://bugzilla.novell.com/show_bug.cgi?id=1105597
--Regards,Hui-Zhi
On Wed, 2018-08-29 at 10:28 +0200, Vincent Moutoussamy wrote:
> Hi,
> Could you please create a bug report for this issue?
> Here is the direct link to do so:
>
https://bugzilla.suse.com/enter_bug.cgi?product=Beta%20SUSE%20Linux%20Enterprise%20Server%2012%20SP4
>
> Thank you,
>
> Regards,
>
> --
> Vincent Moutoussamy
> SUSE Beta Program, JeOS and SDK Project Manager
>
>
>
> > On 29 Aug 2018, at 09:03, tiantao (H) <tiantao6 at huawei.com> wrote:
> >
> >
> > HI :
> >
> > I found a bug on Hi1616. Using beta3 on sles12sp4
> >
> > The system will encounter the following warning when it start up on
> > beta3.but the system will boot ok using the sle12sp3 or sle15 on
> > same platform
> >
> >
> > [ 0.000986] dmi check: not initialized yet.
> > [ 0.001000] ------------[ cut here ]------------
> > [ 0.001011] WARNING: CPU: 0 PID: 0 at
> > ../drivers/firmware/dmi_scan.c:832 dmi_check_system+0x8c/0x94
> > [ 0.001012] Modules linked in:
> > [ 0.001015] Supported: Yes
> > [ 0.001018] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.12.14-
> > 94.33-default #1 SLE12-SP4
> > [ 0.001019] Hardware name: (null) (DT)
> > [ 0.001021] task: ffff000008e22980 task.stack: ffff000008e10000
> > [ 0.001023] PC is at dmi_check_system+0x8c/0x94
> > [ 0.001025] LR is at dmi_check_system+0x8c/0x94
> > [ 0.001027] pc : [<ffff00000872ba88>] lr : [<ffff00000872ba88>]
> > pstate: 60000005
> > [ 0.001028] sp : ffff000008e13f70
> > [ 0.001030] x29: ffff000008e13f70 x28: 0000000000c80018
> > [ 0.001033] x27: 000000000000015a x26: 000000003ed67828
> > [ 0.001036] x25: 0000000000000000 x24: ffff80affbfffd00
> > [ 0.001039] x23: ffff000008e19000 x22: ffff000008f7a000
> > [ 0.001042] x21: ffff000008d3f828 x20: ffff000008f7a000
> > [ 0.001045] x19: ffff000008d4a0f8 x18: 000000000000000b
> > [ 0.001048] x17: 0000000000000000 x16: 0000000000000000
> > [ 0.001051] x15: ffffffffffffffff x14: 662072656d697420
> > [ 0.001054] x13: 676e697375206465 x12: 0000000000000000
> > [ 0.001057] x11: 00000000000000fc x10: 0000000000000004
> > [ 0.001060] x9 : 00000000000000fd x8 : ffff000008e1a488
> > [ 0.001063] x7 : ffff0000085fb018 x6 : ffff000008fd493e
> > [ 0.001065] x5 : ffff801ffbe38e00 x4 : 0000000000000000
> > [ 0.001068] x3 : 0000000000000001 x2 : ffffffffffffffff
> > [ 0.001071] x1 : ffff000008e42338 x0 : 000000000000001f
> > [ 0.001075] Call trace:
> > [ 0.001077] Exception stack(0xffff000008e13e30 to
> > 0xffff000008e13f70)
> > [ 0.001079] 3e20:
> > 000000000000001f ffff000008e42338
> > [ 0.001081] 3e40: ffffffffffffffff 0000000000000001
> > 0000000000000000 ffff801ffbe38e00
> > [ 0.001083] 3e60: ffff000008fd493e ffff0000085fb018
> > ffff000008e1a488 00000000000000fd
> > [ 0.001084] 3e80: 0000000000000004 00000000000000fc
> > 0000000000000000 676e697375206465
> > [ 0.001086] 3ea0: 662072656d697420 ffffffffffffffff
> > 0000000000000000 0000000000000000
> > [ 0.001087] 3ec0: 000000000000000b ffff000008d4a0f8
> > ffff000008f7a000 ffff000008d3f828
> > [ 0.001089] 3ee0: ffff000008f7a000 ffff000008e19000
> > ffff80affbfffd00 0000000000000000
> > [ 0.001091] 3f00: 000000003ed67828 000000000000015a
> > 0000000000c80018 ffff000008e13f70
> > [ 0.001092] 3f20: ffff00000872ba88 ffff000008e13f70
> > ffff00000872ba88 0000000060000005
> > [ 0.001094] 3f40: ffff00000987c000 0000000000000001
> > ffffffffffffffff ffff801ffbe38e00
> > [ 0.001095] 3f60: ffff000008e13f70 ffff00000872ba88
> > [ 0.001098] [<ffff00000872ba88>] dmi_check_system+0x8c/0x94
> > [ 0.001102] [<ffff000008cc78f4>] acpi_early_init+0x58/0xd8
> > [ 0.001104] [<ffff000008c80d54>] start_kernel+0x38c/0x3fc
> > [ 0.001108] ---[ end trace f68728a0d3053b52 ]---
> > [ 0.004534] ACPI: 1 ACPI AML tables successfully acquired and
> > loaded
> >
> >
> > As you can see from the code below,the above callstack is because
> > the dmi_initialized is not assigned a value of 1.
> >
> > 827 int dmi_check_system(const struct dmi_system_id *list)
> > 828 {
> > 829 int count = 0;
> > 830 const struct dmi_system_id *d;
> > 831
> > 832 WARN(!dmi_initialized, KERN_ERR "dmi check: not
> > initialized yet.\n");
> > 833
> > 834 for (d = list; !dmi_is_end_of_table(d); d++)
> > 835 if (dmi_matches(d)) {
> > 836 count++;
> > 837 if (d->callback && d->callback(d))
> > 838 break;
> > 839 }
> > 840
> > 841 return count;
> > 842 }
> >
> > but the dmi_initialized will be assigned the value of 1 in
> > dmi_scan_machine function under any condition . I notice the
> > dmi_scan_machine is different from the latest kernel.
> >
> > -----------------------------------------------------------------
> > ------------
> > Best Regards,
> >
> > tiantao6 at huawei.com
> > Turing Architecture and Design Dept, Hisilicon
> >
> > -----------------------------------------------------------------
> > -----
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄
> > 露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> > This e-mail and its attachments contain confidential information
> > from HUAWEI, which is intended only for the person or entity whose
> > address is listed above. Any use of the information contained
> > herein in any way (including, but not limited to, total or partial
> > disclosure, reproduction, or dissemination) by persons other than
> > the intended recipient(s) is prohibited. If you receive this e-mail
> > in error, please notify the sender by phone or email immediately
> > and delete it!
> >
> > _______________________________________________
> > sle-beta mailing list
> > sle-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sle-beta
>
> _______________________________________________sle-beta mailing
> listsle-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sle-beta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20180829/4b4a1800/attachment.htm>
More information about the sle-beta
mailing list