WO2011063756A1 - 一种用于诊断设备的方法和*** - Google Patents
一种用于诊断设备的方法和*** Download PDFInfo
- Publication number
- WO2011063756A1 WO2011063756A1 PCT/CN2010/079142 CN2010079142W WO2011063756A1 WO 2011063756 A1 WO2011063756 A1 WO 2011063756A1 CN 2010079142 W CN2010079142 W CN 2010079142W WO 2011063756 A1 WO2011063756 A1 WO 2011063756A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- diagnostic
- diagnosis
- program
- bios
- mode
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/2221—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test input/output devices or peripheral units
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2284—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by power-on test, e.g. power-on self test [POST]
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a device diagnostic method and system.
- BACKGROUND In the field of IT and electronic communication, in order to improve the reliability of equipment operation and enhance the maintainability of equipment, the equipment is generally diagnosed and detected, and if there is an error, relevant error information is output, and the equipment is subsequently maintained according to the error information. operating.
- the X86-based device starts the system through the BIOS (Basic Input Output System) or EFI (Extensible Firmware Interface) to complete the initialization and diagnosis of the hardware device, and then enter the operating system.
- BIOS Basic Input Output System
- EFI Extensible Firmware Interface
- the prior art in order to diagnose the hardware device, the prior art often adopts a debugging program in the BIOS, and outputs a debugging information method to the 0x80 port by running the debugging program.
- These diagnostic information are often relatively simple, and the amount of information given is Fewer, unable to make a more accurate judgment of the fault.
- the prior art operates under a operating system through a special diagnostic program or through special key triggers during BIOS startup.
- the BIOS program execution first initializes the CPU, and then initializes the memory, PCI/PCIE, VGA, etc., and then determines whether there is a designated key to press. If there is, enter the diagnostic mode for diagnosis. It can include diagnosis of keyboard, memory, PCI device, hard disk and other devices; if no key is pressed, then the BIOS starts and enters 0S. Since the memory, VGA and other devices have been initialized before entering the diagnostic mode, the information is displayed in detail through the display after the diagnosis is completed, which allows the user to more accurately locate the device fault, which makes maintenance more convenient.
- Embodiments of the present invention provide a device diagnosis method and system, which are used for accurately diagnosing a device, and can also implement a diagnosis function when a device such as a memory or a PCI/PCIE device fails.
- a device diagnosis method includes:
- the device When it is judged to enter the diagnosis mode, the device is diagnosed by executing a diagnostic program
- a device diagnosis system includes: a determining unit, configured to determine whether to perform a diagnosis mode after the system is started;
- a diagnosis unit configured to: after the determining unit determines to perform the diagnosis mode, perform diagnosis on the device by executing a diagnostic program;
- the conventional startup unit is configured to perform a normal BIOS or EFI startup when the determining unit determines not to enter the diagnostic mode.
- the embodiment of the present invention determines whether to enter the diagnosis mode after the system is started, and if yes, enters the diagnosis mode, and if not, continues to perform BIOS or EFI startup, which can implement accurate diagnosis of the device; and when the device has memory or PCI
- BIOS or EFI startup which can implement accurate diagnosis of the device
- the device has memory or PCI
- BIOS or EFI startup which can implement accurate diagnosis of the device
- the diagnostic program since the diagnostic program is loaded before the BIOS is started, the diagnosis of the fault can also be realized.
- FIG. 1 is a flow chart of a method for diagnosing a device in the prior art
- FIG. 3 is a flowchart of a method according to Embodiment 2 of the present invention.
- 4 is a flowchart of a method in step S204 according to Embodiment 2 of the present invention;
- FIG. 5 is a schematic diagram of a system according to a third embodiment of the present invention.
- FIG. 6 is a schematic diagram of a specific application scenario according to Embodiment 3 of the present invention. DETAILED DESCRIPTION OF THE INVENTION
- a first embodiment of the present invention provides a device diagnosis method. Referring to FIG. 2, the method includes the following steps:
- Sioi when the system is started, determine whether to enter the diagnostic mode
- the diagnostic program code may be located in the same memory as the original conventional BIOS or EFI of the system, such as Flash, E2PR0M, etc.; or may be located in a different memory from the BIOS or EFI, for example, adding a memory to the system for storing the diagnosis.
- the code of the program Regardless of which storage method is used, the diagnostic code is independent of the BIOS code (or EFI program code).
- BIOS mainly refers to the BIOS (or EFI) having the original system BIOS function.
- BIOS generally refers to a section started before the operating system (OS).
- OS operating system
- the program, the code of the original BIOS function, the newly added diagnostic code and the judgment program code are all before the operating system is started. Therefore, the original BIOS function code, diagnostic code, and judgment program code can also be regarded as A new BI0S.
- the embodiment of the present invention describes the original BIOS portion and the new diagnostic module as two parts.
- the method of judging whether to enter the diagnostic mode can be triggered by an external level or by software setting. After entering the diagnostic mode, in order to speed up the execution of the program, the program code in the memory can also be loaded into the Cache for execution.
- the diagnosis mainly includes diagnosis of some hardware devices such as memory and PCI/PCIE.
- the specific diagnosis can be based on the actual application.
- the relevant diagnostic information can be output through the serial port. Since the diagnostic content can be customized, the diagnostic function can be made richer and more accurate.
- the embodiment of the present invention determines whether to enter the diagnosis mode after the system is started, and if yes, enters the diagnosis mode, and if not, continues to perform BIOS or EFI startup, which can implement accurate diagnosis of the device; and when the device has memory or PCI When the /PCIE bus error occurs, since the diagnostic program is loaded before the BIOS is started, the diagnosis of the fault can also be realized.
- Embodiment 2
- An embodiment of the present invention provides a device diagnosis method, which is an example in which a device uses a BIOS boot. Referring to FIG. 3, the following steps are included:
- the S20U stores the diagnostic program and the BIOS program in two separate modules.
- the BIOS program here is consistent with the existing regular BIOS program and is used to complete the device startup function, usually stored in Flash, E2PR0M and other memories.
- the diagnostic program is independent of the existing BIOS program, ie executing the diagnostic program alone or the BIOS program does not affect the other program.
- the diagnostic program can be implemented in C language or other languages. After compiling, a binary computer executable program can be generated, which can then be stored in the same memory as the BIOS, or it can be stored in a memory separately from the BIOS.
- the memory can be flash, or E2PR0M.
- bootloader in the memory that is used to select which program module to run when the system is just started.
- boot program BIOS program, and diagnostics can be placed in the same memory.
- BIOS mainly refers to a BIOS having the function of the original system BIOS.
- the BIOS generally refers to a program that is started before the operating system (OS), and the original BIOS function.
- the code, the newly added diagnostic code, and the judgment program code are all before the operating system is started. Therefore, the original BIOS function code, diagnostic code, and judgment program code can also be regarded as a new BIOS;
- the BIOS first determine whether to go to the diagnostic program, if it is, run the diagnostic program code, if not, perform a regular BIOS boot such as device initialization.
- the embodiment of the present invention describes the original BIOS portion and the new diagnostic module as two parts.
- Methods for determining whether to enter the diagnostic mode include, but are not limited to, a few:
- Trigger by external level For example, if the user wants to perform the diagnostic mode, it can trigger a GPIO (General Purpose Input/Output) pin level, and the level value will be reflected to a register in the device (such as the GPI0 register). Value, the system's boot loader can check whether the device enters the diagnostic module or performs a normal BIOS boot by checking the status of these registers on the device. It can be set to use the BIOS for the normal startup process by default. When the user's command is detected (triggering the GPI0 pin level), the diagnostic mode is entered.
- GPIO General Purpose Input/Output
- CMOS Complementary Metal Oxide Semiconductor
- the CMOS value is read first when the next startup, if the value is a valid value (such as 1), then the diagnostic mode is performed, and vice versa, the normal BIOS startup is performed; after reading the value in CMOS , Clear the valid value to prevent the automatic entry to the diagnostic mode the next time.
- Cache is a cache memory and is generally integrated into the CPU.
- the program runs much faster in the Cache than it does in external memory, so the diagnostics diagnostics module can be loaded into the Cache to increase operational efficiency.
- the boot loader can be loaded into the Cache to run, but because the boot loader runs for a short time, no matter where it runs, it will not have much impact on performance; and the diagnostic program starts the bootloader. It takes much longer to execute, so loading it into the Cache can significantly improve the efficiency of the program.
- Loading the diagnostics into the Cache can be done as follows:
- the address in the memory is mapped to the address in the Cache; secondly, the CPU directly accesses the Flash address, and then the CPU finds in the Cache whether there is a code segment backup located at the Flash address just accessed; if not, the Flash address to be accessed The code snippet is loaded into the Cache.
- the Cache In order to allow the program to be loaded into the Cache, the Cache needs to be configured as conventional memory.
- the Cache can be configured into conventional memory by setting the CPU related registers.
- a part of the Cache is used to store the program code, that is, during the running of the program. Stores program code loaded from external memory; another part of the Cache is configured as a stack area in the software, which makes it easy to program in a high-level language such as C (a high-level language generally requires a stack).
- the CPU can fetch instructions from the Cache instead of fetching instructions from external memory each time, and the fetching speed in the Cache is much faster than fetching instructions from the external memory. Therefore, the access time is greatly reduced, so that the speed of the program running in the Cache is greatly improved compared to the external operation, and the execution efficiency is improved.
- this step is not necessary. If some CPUs do not support configuring the Cache as regular memory or do not strictly require the running speed, you can also fetch the instructions from the external memory each time. At the same time, if not You need to use the stack function (such as not using a high-level language), or you can not configure a part of the Cache as a stack in the software.
- the size of the loaded program cannot exceed the maximum value of the Cache configuration. If it is exceeded, only the maximum value of the Cache configuration can be loaded, and the rest is run in the external memory.
- running the diagnostic program can include the following steps:
- Memory diagnosis can be performed by reading SPD (Serial Presence Detect) to determine which DIMMs (Dual Inl ine Memory Module) have memory modules on the slot; through DQS (Bidirectional data) The strobe bidirectional data strobe is checked to determine which DI bus has a problem with the data line or address line.
- SPD Serial Presence Detect
- DQS Bit Inl ine Memory Module
- the strobe bidirectional data strobe is checked to determine which DI bus has a problem with the data line or address line.
- it is also possible to diagnose which chip on the memory module is faulty by reading and writing data (write a data in and read it to determine whether it is consistent).
- PCI/PCIE diagnostics check the manufacturer number and device number on the device, check if there are more devices, check the control registers, 10 and Memory registers, and so on.
- the diagnostic program begins by creating a table that includes information about all PCI/PCIE devices on the device, including device name, PCI bus number, device number, feature number, chip silkscreen, etc., by checking if an error is found, based on this information.
- the table finds out which chip has failed, and specifically obtains the name and silkscreen of the chip.
- the diagnostic hardware of the diagnostic program is not limited to the above memory and PCI/PCIE. Users can customize the hardware devices that need to be diagnosed according to actual needs.
- This step is similar to the conventional BIOS boot of the prior art, including memory initialization, PCI/PCIE initialization, VGA initialization; after booting the BIOS, it enters the operating system 0S.
- the specific operation procedure described above is similar to the prior art and will not be described here.
- the program may be suspended and wait for the user to perform an operation; or may determine whether to enter the BIOS according to the diagnosis result, for example, when the problem is found, the BIOS is not entered; if there is no problem, the normal BIOS is performed. start up.
- the above steps may also be referred to.
- S021 separates the diagnostic program from the EFI module and then determines whether to enter the diagnostic mode. If yes, the device is diagnosed; if not, the normal EFI start is performed.
- the embodiment of the invention determines whether to enter the diagnosis mode after the system is started, and if yes, enters the diagnosis mode. If not, the BIOS or EFI startup is continued, and the device can be accurately diagnosed; meanwhile, the diagnostic program is The BIOS boot is executed separately, and diagnostics can be performed even if there is a problem with hardware such as memory or PCI/PCIE.
- the embodiment of the present invention also configures the Cache of the CPU into conventional memory.
- the diagnostic program is first loaded from the memory to the Cache, and then the program is run in the Cache, thereby speeding up the operation and improving the diagnostic efficiency.
- An embodiment of the present invention provides a device diagnosis system, including:
- the determining unit 31 is configured to determine whether to perform a diagnosis mode after the system is started;
- the diagnosis unit 32 is configured to: after the determining unit determines to perform the diagnosis mode, perform diagnosis on the device by executing a diagnostic program;
- the conventional startup unit 33 is configured to perform a normal BIOS or EFI startup when the determining unit determines not to enter the diagnostic mode.
- the embodiment of the present invention may further include a storage unit 34, configured to store a program code, where the storage unit includes: a first storage unit 341, configured to store a code that the determining unit executes the program;
- a third storage unit 343, configured to store a BIOS or an EFI program code;
- the storage unit may use a memory such as Flash, or E2PR0M; wherein the code of the diagnostic program and the code of the BIOS or EFI program are two separate program codes.
- the second storage unit 342 and the third storage unit 343 may use the same memory or may be implemented using different memories.
- the first memory unit 341, the second memory unit 342, and the third memory unit 343 can all be implemented using the same memory.
- the method for determining whether the determination unit 31 enters the diagnosis mode may be triggered by an external level or by a method set by a software.
- the CPU Cache can also be configured into conventional memory, and the program code in the second storage unit is loaded into the Cache to run.
- the diagnosis of the device by the diagnostic unit 32 mainly includes diagnosis of some hardware devices such as memory, PCI/PCIE, etc.
- the specific content may be determined according to the actual application. Since the diagnostic content can be customized, the diagnostic function can be made richer and more accurate. .
- the diagnostic unit 32 can also suspend the program after the diagnosis is completed, wait for the user to operate; or judge whether to enter the BIOS startup according to the diagnosis result.
- the embodiment of the present invention further includes an output unit 35 for outputting related information after the diagnosis is completed: the output unit 35 can output by using a serial port, and if there are other possible information output methods, other methods can also be used for information output.
- the above-mentioned judging unit, diagnostic unit, conventional starting unit, output unit and the like can be implemented by using a hardware processor or related logic device, for example, using a CPU or other chip having processing functions, wherein one unit can be used separately for each unit.
- the processor can also use a hardware processor in combination with multiple units.
- FIG. 6 is a block diagram of a specific application in an x86 system according to an embodiment of the present invention
- the foregoing determining unit, the diagnostic unit, and the conventional starting unit can all be implemented by a CPU, the storage unit is implemented by using a flash memory, and the output unit is implemented by a serial port;
- the CPU When the system is started, the CPU first determines whether to perform the diagnostic mode.
- the external level triggering causes the change of the register value of the south bridge, and the value of these registers is detected to determine whether to enter the diagnostic mode; if it is judged to enter the diagnostic mode, then Related hardware devices for diagnosis, mainly including memory, PCI/PCIE, etc., and may also include other devices such as a keyboard and a display; after the diagnosis is completed, the related information is output through the serial port; if it is judged that the diagnostic mode is not entered, the routine is performed. BIOS or EFI boot.
- BIOS or EFI boot The storage unit here is implemented by using Flash.
- the code of the diagnostic program and the code of the BIOS or EFI program are two separate codes, but all are stored in the same Flash. In actual applications, two Flash can also be used for storage. ; Flash can also be replaced with other memory such as E2PR0M.
- the embodiment of the invention determines whether to enter the diagnosis mode after the system is started, and if yes, enters the diagnosis mode. If not, the BIOS or EFI startup is continued, and the device can be accurately diagnosed; meanwhile, the diagnostic program is The BIOS boot is executed separately, and diagnostics can be performed even if there is a problem with hardware such as memory or PCI/PCIE.
- the embodiment of the present invention also configures the Cache of the CPU into conventional memory.
- the diagnostic program is first loaded from the memory to the Cache, and then the program is run in the Cache, thereby speeding up the operation and improving the diagnostic efficiency.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
- Stored Programmes (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BRPI1014150A BRPI1014150A2 (pt) | 2009-11-30 | 2010-11-25 | método e sistema de diagnose de aparelho. |
EP10832663A EP2453358A4 (en) | 2009-11-30 | 2010-11-25 | METHOD AND SYSTEM FOR DEVICE DIAGNOSIS |
RU2012113830/08A RU2012113830A (ru) | 2009-11-30 | 2010-11-25 | Способ и система для диагностирования устройства |
US13/338,842 US8719644B2 (en) | 2009-11-30 | 2011-12-28 | Method and system for diagnosing apparatus |
US14/209,786 US20140195855A1 (en) | 2009-11-30 | 2014-03-13 | Method and system for diagnosing apparatus |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2009101884850A CN102081562A (zh) | 2009-11-30 | 2009-11-30 | 一种设备诊断方法及*** |
CN200910188485.0 | 2009-11-30 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/338,842 Continuation US8719644B2 (en) | 2009-11-30 | 2011-12-28 | Method and system for diagnosing apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011063756A1 true WO2011063756A1 (zh) | 2011-06-03 |
Family
ID=44065872
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/079142 WO2011063756A1 (zh) | 2009-11-30 | 2010-11-25 | 一种用于诊断设备的方法和*** |
Country Status (6)
Country | Link |
---|---|
US (2) | US8719644B2 (zh) |
EP (1) | EP2453358A4 (zh) |
CN (1) | CN102081562A (zh) |
BR (1) | BRPI1014150A2 (zh) |
RU (1) | RU2012113830A (zh) |
WO (1) | WO2011063756A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108107307A (zh) * | 2018-01-22 | 2018-06-01 | 杭州春来科技有限公司 | 串行接口线束故障检测装置及方法 |
Families Citing this family (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102855176A (zh) * | 2011-06-29 | 2013-01-02 | 联想(北京)有限公司 | 计算机、网卡和调试信息处理方法 |
KR101805627B1 (ko) * | 2011-11-28 | 2017-12-08 | 삼성전자주식회사 | 컴퓨터 시스템의 부팅 제어 방법 및 이를 수행하는 부팅 제어 장치 |
TW201417001A (zh) * | 2012-10-23 | 2014-05-01 | Hon Hai Prec Ind Co Ltd | 電子設備工作模式切換系統及方法 |
WO2015083226A1 (ja) * | 2013-12-02 | 2015-06-11 | 富士通株式会社 | 情報処理装置及び情報処理装置制御プログラム |
CN103744689A (zh) * | 2013-12-04 | 2014-04-23 | 苏州佳世达光电有限公司 | 电子装置及其启动方法 |
US9798625B2 (en) * | 2015-06-23 | 2017-10-24 | Dell Products, L.P. | Agentless and/or pre-boot support, and field replaceable unit (FRU) isolation |
CN108073481B (zh) * | 2016-11-16 | 2021-02-12 | 佛山市顺德区顺达电脑厂有限公司 | 可提供硬件运作信息的服务器***及其处理方法 |
CN108614752A (zh) * | 2016-12-09 | 2018-10-02 | 北京京存技术有限公司 | 基于NANDflash的故障排除方法和装置 |
IT201700050166A1 (it) * | 2017-05-09 | 2018-11-09 | St Microelectronics Srl | Sistema di elaborazione, relativo circuito integrato, dispositivo e procedimento |
CN107644256A (zh) * | 2017-09-14 | 2018-01-30 | 郑州云海信息技术有限公司 | 一种基于机器学习方式形成故障规则库的方法 |
CN107608813A (zh) * | 2017-09-14 | 2018-01-19 | 郑州云海信息技术有限公司 | 一种基于linux操作***信息自动分析故障的方法 |
CN109344005B (zh) * | 2018-09-20 | 2022-03-22 | 浪潮电子信息产业股份有限公司 | 一种基本输入输出***bios冗余备份方法和装置 |
CN109471763B (zh) * | 2018-11-01 | 2022-02-18 | 郑州云海信息技术有限公司 | 抓取NVME硬盘trace的方法、装置、设备及*** |
CN109683965B (zh) * | 2018-12-03 | 2022-03-04 | 郑州云海信息技术有限公司 | 一种bios状态查看方法及装置 |
CN110162436A (zh) * | 2019-04-25 | 2019-08-23 | 深圳市同泰怡信息技术有限公司 | 一种bios post的常规模式和诊断模式切换方法 |
CN113064774B (zh) * | 2021-03-10 | 2023-02-28 | 山东英信计算机技术有限公司 | 基于服务器的内存一体化刷新诊断方法、***及存储介质 |
CN113099148B (zh) * | 2021-03-10 | 2023-02-24 | 山东英信计算机技术有限公司 | 一种vga输出信号分析装置、***及使用方法 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1704763A (zh) * | 2004-06-01 | 2005-12-07 | 阿尔卡特公司 | 电子设备诊断方法和*** |
US20080010486A1 (en) * | 2006-07-06 | 2008-01-10 | Asustek Computer Inc. | Personal computer diagnostic test before executing operating system |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7010723B2 (en) * | 2002-02-11 | 2006-03-07 | Intel Corporation | Method to couple integrated circuit packages to bonding pads having vias |
US20050033952A1 (en) * | 2003-08-07 | 2005-02-10 | International Business Machines Corporation | Dynamic scheduling of diagnostic tests to be performed during a system boot process |
CN100590600C (zh) | 2004-05-20 | 2010-02-17 | 佛山市顺德区顺达电脑厂有限公司 | 电脑***的启动前期排错装置 |
CN100375056C (zh) | 2005-03-09 | 2008-03-12 | 北京软通科技有限责任公司 | 计算机***硬件设备自动检测的方法 |
CN1952909A (zh) | 2005-10-21 | 2007-04-25 | 鸿富锦精密工业(深圳)有限公司 | 电脑报错方法和*** |
CN101276303B (zh) | 2007-03-30 | 2010-11-10 | 联想(北京)有限公司 | 一种计算机诊断方法及诊断*** |
US7877639B2 (en) * | 2008-11-06 | 2011-01-25 | Dell Products L.P. | Systems and methods to provide failover support for booting embedded hypervisor from an internal non-volatile memory card |
US8132055B2 (en) * | 2009-11-20 | 2012-03-06 | International Business Machines Corporation | Operating system-firmware interface update recovery |
US8161322B2 (en) * | 2009-12-07 | 2012-04-17 | Intel Corporation | Methods and apparatus to initiate a BIOS recovery |
-
2009
- 2009-11-30 CN CN2009101884850A patent/CN102081562A/zh active Pending
-
2010
- 2010-11-25 EP EP10832663A patent/EP2453358A4/en not_active Withdrawn
- 2010-11-25 BR BRPI1014150A patent/BRPI1014150A2/pt not_active IP Right Cessation
- 2010-11-25 RU RU2012113830/08A patent/RU2012113830A/ru unknown
- 2010-11-25 WO PCT/CN2010/079142 patent/WO2011063756A1/zh active Application Filing
-
2011
- 2011-12-28 US US13/338,842 patent/US8719644B2/en active Active
-
2014
- 2014-03-13 US US14/209,786 patent/US20140195855A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1704763A (zh) * | 2004-06-01 | 2005-12-07 | 阿尔卡特公司 | 电子设备诊断方法和*** |
US20080010486A1 (en) * | 2006-07-06 | 2008-01-10 | Asustek Computer Inc. | Personal computer diagnostic test before executing operating system |
Non-Patent Citations (1)
Title |
---|
See also references of EP2453358A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108107307A (zh) * | 2018-01-22 | 2018-06-01 | 杭州春来科技有限公司 | 串行接口线束故障检测装置及方法 |
Also Published As
Publication number | Publication date |
---|---|
US20120096319A1 (en) | 2012-04-19 |
US8719644B2 (en) | 2014-05-06 |
EP2453358A1 (en) | 2012-05-16 |
RU2012113830A (ru) | 2013-10-20 |
CN102081562A (zh) | 2011-06-01 |
EP2453358A4 (en) | 2012-07-11 |
BRPI1014150A2 (pt) | 2016-04-26 |
US20140195855A1 (en) | 2014-07-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011063756A1 (zh) | 一种用于诊断设备的方法和*** | |
US9501289B2 (en) | Method of a UEFI firmware and computer system thereof | |
US20180267920A1 (en) | Expansion component | |
US8468342B2 (en) | Computer system and method for performing integrity detection on the same | |
EP2329365B1 (en) | Turbo boot systems and methods | |
JP6124994B2 (ja) | レガシーos環境から統合拡張可能ファームウェア・インターフェース(uefi)ブート前環境への復元を行うための方法およびシステム、ならびにコンピュータ・プログラム | |
US8812828B2 (en) | Methods and apparatuses for recovering usage of trusted platform module | |
US10909247B2 (en) | Computing device having two trusted platform modules | |
US8296528B2 (en) | Methods and systems for microcode patching | |
US10606677B2 (en) | Method of retrieving debugging data in UEFI and computer system thereof | |
WO2016074127A1 (zh) | 计算机设备及计算机设备内存启动的方法 | |
WO2013074107A1 (en) | Method, apparatus and system for memory validation | |
US7356684B2 (en) | Booting system and/or method for initializing peripherals | |
US11704198B2 (en) | Method and apparatus for providing recovery from a computing device boot up error | |
EP3698251B1 (en) | Error recovery in non-volatile storage partitions | |
US20180275731A1 (en) | Processor reset vectors | |
US10491736B2 (en) | Computer system and method thereof for bluetooth data sharing between UEFI firmware and OS | |
US20110296072A1 (en) | System and method for controlling pci-e slots of computer | |
US10777296B2 (en) | Information handling system and method to dynamically detect and recover from thermally induced memory failures | |
US9361123B2 (en) | Boot from logical volume spanning plurality of PCI devices | |
TW201734800A (zh) | 設定磁碟陣列的方法 | |
WO2022199622A1 (zh) | 一种电子设备的启动程序的运行方法和电子设备 | |
CN113646745A (zh) | 禁用软件持久性 | |
US20240211602A1 (en) | Bmc based hrot implementation establishing chain of trust in a secured server system | |
WO2022173439A1 (en) | Status information of auxiliary devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10832663 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010832663 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 9968/CHENP/2011 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012113830 Country of ref document: RU |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: PI1014150 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: PI1014150 Country of ref document: BR Kind code of ref document: A2 Effective date: 20111228 |