Re: lock up

Kris Kennaway wrote:
> Joao Pedras wrote:
>> Hi again,
>>
>> hope this info sheds some light on this. A similar system is getting
>> setup to reproduce the problem there as well.
>>
>> Thanks!
>>
>> Joao
>>
>> Kris Kennaway wrote:
>>> Joao Pedras wrote:
>>>> Greetings all!
>>>>
>>>> A system (Tyan S2932) I am testing CURRENT amd64 with is experiencing a
>>>> strange lock up. No panic, not much on the console, just a lock up,
>>>> freeze.
>>>>
>>>> I first noticed the issue while tailing a build in a ssh session over a
>>>> vpn connection. On the local network the issue doesn't seem to occur.
>>>> I can reproduce the lock up all the time.
>>>>
>>>> Last I tried, the system was running CURRENT from a couple hours ago.
>>>>
>>>> I have tried:
>>>>
>>>> - 4BSD and ULE
>>>> - switching network cards
>>>> - taking the IPMI card out (seems to work locally with freeipmi and
>>>> ipmitoll remotely)
>>>> - enabled/disabled "redirection after post" (BIOS setting)
>>>> - without debug
>>>> - without IPv6 and friends (see rtfree below)
>>>>
>>>> dmesg and pciconf attached. The dmesg is after a lock up.
>>>> rtfree pops a few times before the lock up. I noticed from a recent
>>>> post
>>>> some action was taken and the related patch is there (ie. today's
>>>> CURRENT).
>>>>
>>>> The system had a fresh install this past weekend and the LSI MegaRAID
>>>> array doesn't contain any data, it is just mounted. The system boots
>>>> off
>>>> the onboard LSI SAS (couple disks in RAID 1).
>>>>
>>>> Thank you for your input.
>>> Break to DDB and obtain process traces, etc.  See the developers
>>> handbook.
>>>
>>> Kris
>>>
> 
> Well that's a start, but you need to trace other processes too, e.g. the
> running ones.  Do an 'alltrace' to trace everything.
> 
> Kris
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"

Thank you for your help Kris. I am not very familiar with these tasks.

I got the 'alltrace' and I also saved a crash dump.
The session output is here http://pedras.webvolution.net/s2932-9.txt.

I was able to reproduce the issue on a similar system (a vanilla Tyan
S2932, one SATA disc only) and it exhibits the exact same problem.

Thanks again.

Joao