On Mon, Apr 10, 2000 at 07:48:45AM -0400, Brian Fundakowski Feldman wrote:
> On Sun, 9 Apr 2000, Alfred Perlstein wrote:
> > In otherwords, unplug your palm pilot and attach a console.
>
> I'm going to get my friend to get a traceback and whatever else is
> possible. He has a laptop and "null" s
On Mon, 10 Apr 2000, Jordan K. Hubbard wrote:
> > The syptoms are that the machine locks up. Hard. But there's a catch:
>
> Erm, Brian, You *know* nobody can debug a problem like this without
> hard information. It's like calling a mechanic on the phone and
> saying "My car won't go. It just
> The syptoms are that the machine locks up. Hard. But there's a catch:
Erm, Brian, You *know* nobody can debug a problem like this without
hard information. It's like calling a mechanic on the phone and
saying "My car won't go. It just doesn't move at all! Tell me what's
wrong!"
Compile in
On Sun, 9 Apr 2000, Alfred Perlstein wrote:
> This can happen when the kernel is stuck in an infinite loop
> somewhere, you're still responding to interrupts, just stuck
> somewhere.
>
> FYI:
> ~ % uname -a
> FreeBSD thumper 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sun Apr 2 16:29:20 PDT 2000
>
> Well, it seems that -CURRENT likes locking up nowdays. It started happening
> very recently, and I (as well as jlemon) do suspect that it's a problem
> with some of the changes that were made to the syscall mechanisms on
> 3/28/2000.
>
> Keep in mind that this problem is completely corroborate
* Brian Fundakowski Feldman <[EMAIL PROTECTED]> [000409 18:30] wrote:
> Well, it seems that -CURRENT likes locking up nowdays. It started happening
> very recently, and I (as well as jlemon) do suspect that it's a problem
> with some of the changes that were made to the syscall mechanisms on
> 3/
6 matches
Mail list logo
