做桌面用的FreeBSD频繁死机重启，查找原因应由何处入手？

zhengwei_zw

请用排除法！先禁止com lpt nic 等等……再不进入xwindow看看……

zhengwei_zw

1. Apr 22 12:05:49 z6a kernel: WARNING: / was not properly dismounted
   
2. Apr 22 12:05:49 z6a kernel: WARNING: /home was not properly dismounted
   
3. Apr 22 12:05:49 z6a kernel: /home: mount pending error: blocks 56 files 3
   
4. Apr 22 12:05:49 z6a kernel: WARNING: /tmp was not properly dismounted
   
5. Apr 22 12:05:49 z6a kernel: WARNING: /usr was not properly dismounted
   
6. Apr 22 12:05:49 z6a kernel: WARNING: /var was not properly dismounted

复制代码

1. Apr 24 19:07:34 z6a kernel: WARNING: / was not properly dismounted
   
2. Apr 24 19:07:34 z6a kernel: WARNING: /home was not properly dismounted
   
3. Apr 24 19:07:34 z6a kernel: /home: mount pending error: blocks 124 files 4
   
4. Apr 24 19:07:34 z6a kernel: WARNING: /tmp was not properly dismounted
   
5. Apr 24 19:07:34 z6a kernel: WARNING: /usr was not properly dismounted
   
6. Apr 24 19:07:34 z6a kernel: WARNING: /var was not properly dismounted
   
7. Apr 24 19:07:34 z6a kernel: /var: mount pending error: blocks 28 files 8
   
8. Apr 24 19:07:34 z6a root: /etc/rc: WARNING: /usr/local/etc/mpd.conf is not readable.
   
9. Apr 24 00:38:09 z6a root: /etc/rc: WARNING: /usr/local/etc/mpd.conf is not readable.
   
10. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154200 (190016 should be 189312) (CORRECTED)
    
11. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154207 (427488 should be 427296) (CORRECTED)
    
12. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154208 (418208 should be 418016) (CORRECTED)
    
13. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154224 (728832 should be 728224) (CORRECTED)
    
14. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154232 (274144 should be 273728) (CORRECTED)
    
15. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154244 (1037984 should be 1037376) (CORRECTED)
    
16. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154252 (315648 should be 314912) (CORRECTED)
    
17. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154265 (267520 should be 266272) (CORRECTED)
    
18. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1154266 (167712 should be 167648) (CORRECTED)
    
19. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1201153 (241344 should be 240864) (CORRECTED)
    
20. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1201157 (144640 should be 144384) (CORRECTED)
    
21. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1201159 (322752 should be 322240) (CORRECTED)
    
22. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1201165 (307584 should be 306240) (CORRECTED)
    
23. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1201166 (109888 should be 109408) (CORRECTED)
    
24. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1248260 (37888 should be 37472) (CORRECTED)
    
25. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1248282 (191136 should be 189536) (CORRECTED)
    
26. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1248285 (97760 should be 96704) (CORRECTED)
    
27. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: INCORRECT BLOCK COUNT I=1248288 (44064 should be 43552) (CORRECTED)
    
28. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: Reclaimed: 0 directories, 0 files, 2856 fragments
    
29. Apr 24 00:40:10 z6a fsck: /dev/ad4s1g: 541 files, 2661492 used, 31964169 free (425 frags, 3995468 blocks, 0.0% fragmentation)
    
30. Apr 24 00:40:12 z6a fsck: /dev/ad4s1d: 10 files, 3433 used, 28174 free (46 frags, 3516 blocks, 0.1% fragmentation)
    
31. Apr 24 00:41:32 z6a fsck: /dev/ad4s1f: 200816 files, 988582 used, 1549937 free (21137 frags, 191100 blocks, 0.8% fragmentation)
    
32. Apr 24 00:41:38 z6a fsck: /dev/ad4s1e: Reclaimed: 0 directories, 1 files, 6 fragments
    
33. Apr 24 00:41:38 z6a fsck: /dev/ad4s1e: 18091 files, 38639 used, 88194 free (658 frags, 10942 blocks, 0.5% fragmentation)
    
34. Apr 24 19:07:33 z6a syslogd: kernel boot file is /boot/kernel/kernel
    
35. 
    

复制代码

不知道什么原因，你盘有坏道不？

SimonCheung

显卡驱动是从ports安装的，有否问题？

你说的排除法，可否提供一些具体步骤？多谢！

硬盘的记录，我认为是死机后check文件系统造成的。坏道的可能比较小，毕竟使用不久，强度也不大。坏了多半也是FreeBSD常死机造成的，呵呵。

mingyanguo

怀疑是硬件问题或者你装的驱动的问题。如果有条件可以编译一个有调试选项与调试器的kernel(options ddb 等等，看/sys/conf/NOTES 中关于调试的说明)，这样如果是panic，能找找原因，如果直接重启……就不知道了。

SimonCheung

多谢回复了！
我只是个用户而已，搞调试什么的明显超越能力了。呵呵
先将就用着，哪天实在厌烦了就装回windows看是不是硬件问题。
不过，能不能先定义一下问题？如果windows使用完全没有异常，但FreeBSD不行，算不算硬件不过关？

mingyanguo

原帖由 SimonCheung 于 2007-4-24 22:17 发表
多谢回复了！
我只是个用户而已，搞调试什么的明显超越能力了。呵呵
先将就用着，哪天实在厌烦了就装回windows看是不是硬件问题。
不过，能不能先定义一下问题？如果windows使用完全没有异常，但FreeBSD不行， ...

如果有调试信息别人好定位问题，不是要你自己去调试。只是莫名其妙的重启没有其他信息的话，不好找问题。
至于用什么系统，还是各人看自己的需求。没什么万全之策。

SimonCheung

汇报一下情况。
昨天晚上用选项二启动，满负荷（开boinc让CPU跑100%，开rtorrent以200k速度下载--我的宽带只有这么宽了）跑了一夜，今早去看还没有死机。欧耶！看来是那个ACPI的问题。出门的时候机器没关，晚上回去看有没有异常。
看了下手册里面关于ACPI的11.16，晕晕的。呵呵
另外问一下，在FreeBSD下面有没有可以刷BIOS的软件？google了一下一无所获。

lsstarboy

Freebsd下好象没有可以刷bios的软件。顺便说一下，非intel系列的主板在使用是很可能会出莫名奇妙的问题。
并且，Freebsd的硬件要求要比windows高多了，在windows下半天才出问题的机器，在freebsd下一般启动不了。我有一块主板，在windows下就跑photoshop等大程序时死机，在freebsd下，启动都过不了，运气好的时候，刚登录进系统就死机。

SimonCheung

我昨天晚上回去的时候，发现机器早在上午10点多的时候已经重启。不过我接着使用到深夜2点多，没有死机。这时候是正常选项启动。
大家都这么说，我也觉得是自己的硬件不过关了。呵呵