[Bug 7215] PCMCIA network card causes either X or kernel to freeze

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=7215





------- Additional Comments From ericabel at mit.edu  2006-10-25 13:09 -------
Hello,  I hope you haven't closed out this bug report because of the time lag
since my last email, but I just wanted to let you know that the problem still
persists, and I am out of ideas as to what to check.  It seems to be a kernel
problem, since when it freezes, the serial terminal becomes unresponsive, in
addition any running sub processes also hang.  I do think that the 
error occurs
before any error data can be logged, because I still can't find any 
trace of an
error in any log file.  Unfortunately going back to the 2.6.8 kernel isn't so
easy for me at this point, so I am dealing with the repeated system shutdowns
every time this happens.  Any ideas?

Erid

Quoting bugme-daemon at bugzilla.kernel.org:

> http://bugzilla.kernel.org/show_bug.cgi?id=7215
>
>
>
>
>
> ------- Additional Comments From ericabel at mit.edu  2006-10-16 08:36 -------
> OK, I've ascertained now that it is the kernel which seizes
> up...nothing works. The serial terminal freezes up when the computer
> freezes...and I still can't
> find any trace of error messages.
>
> Eric
>
> Quoting bugme-daemon at bugzilla.kernel.org:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=7215
>>
>>
>>
>>
>>
>> ------- Additional Comments From ericabel at mit.edu  2006-09-27 15:36 -------
>> Quoting bugme-daemon at bugzilla.kernel.org:
>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=7215
>>>
>>>
>>>
>>>
>>>
>>> ------- Additional Comments From akpm at osdl.org  2006-09-27 13:04 -------
>>> On Wed, 27 Sep 2006 13:07:00 -0700
>>> bugme-daemon at bugzilla.kernel.org wrote:
>>>
>>>> I can still connect through the ethernet port, which is unaffected by this
>>>> problem.
>>>
>>> You can?  That's interesting.
>>
>> Scratch that...I can't.  I meant, in theory, I can connect through the
>> ethernet
>> port, but I just tried, and the netconsole I was working on went dead
>> when the
>> computer froze.
>>
>>> When you do so, is there nothing interesting in the `dmesg' output?
>>
>> Even without doing this, I thought dmesg just printed the contents of
>> /var/log/messages, which has a time stamp, and I have tried looking
>> at the log
>> file right before it died (to see the last time stamp), then the next
>> series of
>> messages are associated with the new boot after restarting (starting 
>> with the
>> message "restart".  Basically there's nothing I can see no messages
>> which seem
>> to occur around the time the system freezes up, much less anything which
>> indicates a problem (in syslog either).  This is why the problem is so
>> perplexing to me.
>>
>>>
>>> This means that there's no point in setting up a serial console or 
>>> anything.
>>
>> I guess there is...but it'll be a while.  I'll need to get a serial
>> cable...haven't had need for one of those in years.
>>
>>>
>>> If you can still connect to the machine, then what do you mean by "it
>>> freezes"?  Just that the X interface is wedged up?
>>
>> At this point, I can say that I have no interaction with the machine, either
>> with the mouse or keyboard.
>>
>>>
>>> If so, run `top' and `ps aux', see if some process is stuck spinning in a
>>> loop or something.
>>>
>>> Could it just be that the keyboard/mouse have gone bad?
>>
>> No, the computer will run forever if I use only the ethernet 
>> connection, it's
>> only when I connect wirelessly that the problem manifests itself.
>>
>>>
>>> What happens if you do `sudo killall X' when logged in over the network?
>>> Does the X server terminate?  Can it be restarted?
>>
>> Don't know, haven't been able to interact with the computer once it's
>> frozen up
>> yet.
>>
>>>
>>> etcetera....
>>>
>>>
>>>
>>> ------- You are receiving this mail because: -------
>>> You reported the bug, or are watching the reporter.
>>>
>>
>>
>>
>>
>> ------- You are receiving this mail because: -------
>> You reported the bug, or are watching the reporter.
>>
>
>
>
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.