启动过不了PCI检测怎么回事？

xuyong · March 17, 2010, 5:44am

我使用的工控机在重启的过程中，是用shutdown热启动,image中有到以下的步骤就过不去了
seedres
pci-bios&
waitfor /dev/pci 30

可是关机重新启动系统就好啦

xuyong · March 29, 2010, 5:51am

系统的日志如下，哪位能帮助分析一下：
Time Jan 15 22:19:51 Jan 15 22:19:51 2 19 Jan 15 22:19:51 2 19 86, did 27df, Jan 15 22:19:51 2 19 3f4, irq e, Jan 15 22:19:51 2 19 error 0
Jan 15 22:19:51 2 19 error 0
Jan 15 22:19:51 2 19 able 40, max ma -1, pio 0, mblk 1
Jan 15 22:19:51 2 19 0, udma -1, Jan 15 22:19:51 2 19 086, did 27c0, Jan 15 22:19:51 2 19 18c4, irq a, Jan 15 22:19:51 2 19 error ff
Jan 15 22:19:51 2 19 086, did 27c0, Jan 15 22:19:51 2 19 18c0, irq a, Jan 15 22:19:51 2 19 error ff
Jan 15 22:19:51 2 19 d 27df, class Jan 15 22:19:51 2 19 374, irq f, Jan 15 22:19:51 2 19 error ff
Jan 15 22:19:51 2 19 error ff
Jan 15 22:19:53 1 Jan 15 22:19:53 1 Jan 15 22:19:54 5 14 Jan 15 22:19:54 3 14 tion
Jan 15 22:19:55 4 Jan 15 22:19:55 1 Jan 15 22:19:55 1 Jan 15 22:19:55 7 15 ng Sev Major Minor Args
2 19 1500 devb-ahci 1.00A (Sep 14 2006 15:38:41)
0 devb-eide 1.00A (Sep 14 2006 15:35:04)
0 eide_identify_devices: Intel 82801GB IDE vid 80
class 1018a rev 1, busno 0, dfunc f9
0 eide_identify_devices: cmd_addr 1f0, cntl_addr
chnl 0, udma 5, mdma 2, sdma 0, pio 4
0 eide_identify_devices: probing dev 0 status 50,
0 eide_identify_devices: probing dev 1 status 0,
0 eide_display_devices: Industrial CF Ca tid 0, c
udma -1, cur udma -1, max mdma -1, cur mdma -1, max sdma -1, cur sd
0 eide_init_devices: Industrial CF Ca path 0, tid
mdma -1, sdma -1, pio 0, mblk 1
0 eide_identify_devices: Intel 82801GB SATA vid 8
class 1018f rev 1, busno 0, dfunc fa
0 eide_identify_devices: cmd_addr 18d0, cntl_addr
chnl 0, udma 5, mdma 2, sdma 0, pio 4
0 eide_identify_devices: probing dev 0 status 7f,
0 eide_identify_devices: Intel 82801GB SATA vid 8
class 1018f rev 1, busno 0, dfunc fa
0 eide_identify_devices: cmd_addr 18c8, cntl_addr
chnl 1, udma 5, mdma 2, sdma 0, pio 4
0 eide_identify_devices: probing dev 0 status 7f,
0 eide_identify_devices: Generic IDE vid 8086, di
1018a rev 1, busno 0, dfunc f9
0 eide_identify_devices: cmd_addr 170, cntl_addr
chnl 1, udma -1, mdma -1, sdma -1, pio 0
0 eide_identify_devices: probing dev 0 status ff,
0 eide_identify_devices: probing dev 1 status ff,
8 0 phfont_init
8 0 phfontXX started OK
0 tcpip starting
0 Using pseudo random generator. See “random” op
8 0 Legacy mode config file found.
8 0 phfont_init
8 0 phfontXX started OK
0 npm-qnet(L4): qnet_birth(): qnet_init() - calli

Jan 15 22:19:55 7 15 0 npm-qnet(L4): en_ionet_rx_ctrl(): new interface
: en0: index 0 cell 0 endpt 0 iface 0 mac addr 00:E0:4C:50:2C:EF

Jan 15 22:19:55 7 15 0 npm-qnet(QOS): nd_change_notify(): Node Up: n
d 0 pmu.net.intra

Jan 15 22:19:55 7 15 0 npm-qnet(L4): en_ionet_rx_ctrl(): new interface
: en1: index 1 cell 0 endpt 1 iface 0 mac addr 00:E0:4C:50:2C:F0

Jan 15 22:19:55 7 15 0 npm-qnet(L4): en_ionet_rx_ctrl(): too many inte
rfaces, increase MAX_L4

Jan 15 22:19:55 7 15 0 npm-qnet(L4): qnet_birth(): qnet_init() - compl
ete: 0

Jan 15 22:19:55 7 15 0 npm-qnet(L4): lr_verify_my_name_and_domain(): s
tarting resolution of our hostname pmu.net.intra to ensure unique

Jan 15 22:19:55 6 8 0 SetDisplayOffset pos: 0 0
Jan 15 22:19:55 6 8 0 SetDisplayOffset pos: 0 0
Jan 15 22:19:55 6 8 0 ServBIOSSetPalette First: 0 Num: 256
Jan 15 22:19:55 5 8 0 Attached /dev/io-graphics/crt00, id = 3
Jan 15 22:19:55 7 15 0 npm-qnet(L4): lr_verify_my_name_and_domain(): q
net going online

Jan 15 22:19:55 5 8 0 Process fontsleuth initialized.
Jan 15 22:19:58 7 15 0 npm-qnet(L4): lr_verify_my_name_and_domain(): s
tarting resolution of our hostname 63.net.intra to ensure unique

Jan 15 22:19:59 7 15 0 npm-qnet(L4): lr_verify_my_name_and_domain(): q
net going online

Jan 15 22:20:13 1 8 0 FatalError
Jan 15 22:20:13 1 8 0 Unable to start error thread - unable to set up
resource manager 08 phfont.so
Jan 15 22:20:13 1 8 0 Received terminate request, exiting - EOK