System hangs during heavy sequential write to mfi device

Ireneusz Pluta ipluta at wp.pl
Fri Jun 25 15:52:19 UTC 2010


John Baldwin pisze:
> On Friday 25 June 2010 7:57:41 am Ireneusz Pluta wrote:
>   
>> Hello,
>>
>> I already posted this to freebsd-questions, with no response, so far.
>> As this is rather a problem closer to hardware issues, so maybe here I 
>> have a better luck. Hope nobody blames me for crossposting.
>>
>> Jun 22 15:09:21 emu kernel: N<M2I> NISAM NIM I II3SS0A,A N  NE3MIMS0II3, 
>> N 0I ,ENSIMA NSI IEAMASI MI A IS3S A00 0,
>> Jun 22 15:09:21 emu kernel: I
>> Jun 22 15:09:21 emu kernel: A33
>>
>>     
> You are getting NMI's.  Have you tried checking the system's event log (if it 
> has one) for messages about hardware errors?
>
>   

Thank you, John, for paying attention.

The mb is intel S5520HC so it has event log.
 From your article 
http://www.bsdcan.org/2008/schedule/attachments/45_article.pdf I found 
that I yet needed impitool, so I installed it.

`impitool sel elist`

shows quite a lot of messages already stored like these:

 e05 | 06/24/2010 | 18:08:24 | Critical Interrupt PCIe Fat Sensor |
 e06 | 06/24/2010 | 18:09:28 | Critical Interrupt PCIe Fat Sensor |
 e07 | 06/25/2010 | 16:12:56 | Critical Interrupt PCIe Fat Sensor |
 e08 | 06/25/2010 | 17:34:16 | Critical Interrupt PCIe Fat Sensor |
 e09 | 06/25/2010 | 17:34:55 | Critical Interrupt PCIe Fat Sensor |

They seem to appear exactly at the moments of system lockups - the last 
two were appended after I made another try.

Intel document related to the motherboard
http://download.intel.com/support/motherboards/server/sb/e68105004_msu_s5520hc_s5500hcv_july_09.pdf
says something about these messages, but in the context completely 
unrelated to my case.

Any thoughts?


More information about the freebsd-hardware mailing list