On 2012-10-11, Илья Шипицин <chipits...@gmail.com> wrote:
> 2012/10/11 Kenneth R Westerback <kwesterb...@rogers.com>
>
>> On Thu, Oct 11, 2012 at 12:30:56PM +0600, ???? ??????? wrote:
>> > Hello!
>> >
>> > we recently installed OpenBSD/amd64 on Supermicro X9DR3-F, it hangs
>> about 1
>> > times a day.
>> > 5.1 does not understand i350 chip, so we put external "Intel PRO/1000 MT
>> > (82574L)" nic.
>> >
>> > we have ddb.panic=1, but no ddb appears on screen on hang.
>> > also, it says "savecore: no core dump" during boot.
>> >
>> > we tested RAM with memtest, so we do not suspect it for memory related
>> > issue.
>> >
>> >
>> > how can we diagnose those hangs ?
>> > is it ok to run 5.1 on X9DR3-F ?
>> >
>> > do I need to provide dmesg output ? any other kind of diagnostics ?
>> >
>> > Cheers,
>> > Ilya Shipitsin
>> >
>>
>> http://openbsd.org/report.html
>>
>> .... Ken
>>
>
>
> it just hangs silently.
> from http://openbsd.org/report.html point of view it is useless.
Before reporting bugs/problems with released versions, go through this
checklist:
1. First check for patches and notes regarding the release.
2. Next find out if there is a newer release available.
3. The last thing to check is for changes made between OpenBSD
versions.
"check...for changes made between OpenBSD versions" could mean "dig
through commit logs looking for something which might help", or it could
mean "try it with -current".
another thing you could try is comparing i386/amd64. and when you
test -current, you can compare using the i350 with using the external
nic. (I only have limited experience of supermicro but some of the
experience I do have tells me not to trust them to get things right
every time when add-on cards are used).
> the only thing I have is "dmesg output".
3. The OpenBSD kernel output. You can get this with the dmesg command,
but it is possible that your dmesg output does not contain all the
information that is captured in /var/run/dmesg.boot. If this is the
case, include information from both. *Please include this in all bug
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
reports.*
^^^^^^^^
> so, I'm asking, how to collect information in case of "silent hang
> behaviour"
> it will be very useless bug report without that information.
>
> like "blah-blah-blah, it hangs about once a day. silently"
you can add to this easily with a bit of testing and thinking about
what information might be useful. "blah-blah-blah, here is a dmesg,
it hangs about once a day silently, this happens at <various times
| always the same time each day>, it <does | doesn't> seem to be
affected by high levels of network traffic / disk io / ...
it <does | doesn't> happen if I leave the machine idle and
disconnected from the network".
basically try and think of more things which might possibly help,
test them, then make a nice list of things which you've tried..
