Re: Latest -current complete lockup (tcp changes?)

Garrett Cooper wrote:
> Andre Oppermann wrote:
>> Andrey Chernov wrote:
>>> On Tue, Mar 27, 2007 at 09:28:10AM +0400, Andrey Chernov wrote:
>>>> On Tue, Mar 27, 2007 at 10:11:01PM +0000, Garrett Cooper wrote:
>>>>>> The problem is deeper than that (((
>>>>>> I still got the same lockup, just with more net activity.
>>>>>> I even try to completely disable sack, with the same result, so
>>>>>> probem is somewhere else. Last working kernel still from Mar 22.
>>>>> I'll give a CVSup / upgrade a try and see what happens.
>>>> Additional non-default details from my machine which may (or may not)
>>>> affect the thing:
>>> Yet one detail about lockup: external pings to the machine works in
>>> the lockup situation, but no any TCP services is available.
>> I can only think of a TCP_INFO_LOCK() leak here blocking any further
>> progress.  When I'm back in the office in about an hour I'll prepare
>> a test patch.
>>
>>> Attempting to press power button to initiate soft reboot says that
>>> "acpi ... not ready yet".
> 
> 	I noticed that my machine's been locking up a bit lately (kernel core
> dumps in /var/crash), so I'll investigate a bit more if this situation
> persists (did a clean rebuild with world and kernel this evening).
> 
> 	If you want some of my info, please let me know, but I'm not entirely
> sure if the issue is net related or another panic to be honest now
> (didn't build kernel with debug symbols until now ><).
> -Garrett

Nevermind my comments about the kernel panic and possible TCP
involvement. The issues are probably all related to my SCSI card in the
PC (which may or may not be failing).

-Garrett