On 2 Jan, Lars Kristiansen wrote:
Attempting to catch up with my backlog of unread email, only 12K unread
messages to go ...
On 24 Nov, Rob wrote:
I have cvsup'ed the sources to STABLE as of Nov. 23rd
2005.
After recompiling/installing world and debug-kernel,
I again get a kernel
Attempting to catch up with my backlog of unread email, only 12K unread
messages to go ...
On 24 Nov, Rob wrote:
I have cvsup'ed the sources to STABLE as of Nov. 23rd
2005.
After recompiling/installing world and debug-kernel,
I again get a kernel deadlock when using swapfile:
On 17 Nov, Kris Kennaway wrote:
On Thu, Nov 17, 2005 at 04:33:50PM -0800, Rob wrote:
--- Kris Kennaway [EMAIL PROTECTED] wrote:
I commented on it elsewhere in this thread.
Do you mean your comment on the swap_pager error:
Quote:
AFAICT that is just a trigger-happy timer..it's
Attempting to catch up with my backlog of unread email, only 12K unread
messages to go ...
On 24 Nov, Rob wrote:
I have cvsup'ed the sources to STABLE as of Nov. 23rd
2005.
After recompiling/installing world and debug-kernel,
I again get a kernel deadlock when using swapfile:
Peter Jeremy wrote:
On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote:
The only way I know of how to trigger the deadlock,
is to compile
a new kernel and the 'linking kernel' stage will
lock-up the PC.
With a regular kernel, this takes 2.5 hours until
deadlock, but with
a fully equipped debug
Rob wrote:
--- Peter Jeremy PeterJeremy at optushome.com.au
wrote:
Basically, wait until your system deadlocks. BREAK
into DDB.
As a start, run 'show lockedvnods', 'ps'. My guess
is that you'll see a lock that has a number of
waiters
which is probably the culprit.
Use 'panic' to get a
Lars Kristiansen wrote:
Hello again, I am the me too-guy with console-access.
Hi Lars,
I'm the one who started this thread, when I could not compile a new
kernel after I upgraded to 6 (Pentium-1, 150 MHz, 32 MB Ram).
How do you trigger the deadlock?
The only way I know of how to
On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote:
The only way I know of how to trigger the deadlock, is to compile
a new kernel and the 'linking kernel' stage will lock-up the PC.
With a regular kernel, this takes 2.5 hours until deadlock, but with
a fully equipped debug kernel it takes about 8
Peter Jeremy wrote:
On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote:
The only way I know of how to trigger the deadlock, is to compile
a new kernel and the 'linking kernel' stage will lock-up the PC.
With a regular kernel, this takes 2.5 hours until deadlock, but with
a fully equipped debug
Lars Kristiansen wrote:
Hello again, I am the me too-guy with console-access.
Hi Lars,
I'm the one who started this thread, when I could not compile a new
kernel after I upgraded to 6 (Pentium-1, 150 MHz, 32 MB Ram).
How do you trigger the deadlock?
The only way I know of how
--- Peter Jeremy [EMAIL PROTECTED] wrote:
Basically, wait until your system deadlocks. BREAK
into DDB.
As a start, run 'show lockedvnods', 'ps'. My guess
is that you'll see a lock that has a number of
waiters
which is probably the culprit.
Use 'panic' to get a crashdump and then you can
On Thu, Nov 17, 2005 at 02:52:12PM -0800, Rob wrote:
--- Peter Jeremy [EMAIL PROTECTED] wrote:
Basically, wait until your system deadlocks. BREAK
into DDB.
As a start, run 'show lockedvnods', 'ps'. My guess
is that you'll see a lock that has a number of
waiters
which is probably
--- Kris Kennaway [EMAIL PROTECTED] wrote:
I commented on it elsewhere in this thread.
Do you mean your comment on the swap_pager error:
Quote:
AFAICT that is just a trigger-happy timer..it's
supposed to detect when a swap operation took too
long to complete, but it also triggers on
On Thu, Nov 17, 2005 at 04:33:50PM -0800, Rob wrote:
--- Kris Kennaway [EMAIL PROTECTED] wrote:
I commented on it elsewhere in this thread.
Do you mean your comment on the swap_pager error:
Quote:
AFAICT that is just a trigger-happy timer..it's
supposed to detect when a swap
--- Peter Jeremy [EMAIL PROTECTED] wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
options GDB
Is that enough?
If your system is headless, you
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
options GDB
Is that enough?
If your system is headless, you probably want 'options BREAK_TO_DEBUGGER'
as well.
First
On Wed, Nov 16, 2005 at 04:01:36PM +0100, Lars Kristiansen wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
options GDB
Is that enough?
If your
On Wed, Nov 16, 2005 at 04:01:36PM +0100, Lars Kristiansen wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
options GDB
Is that enough?
If your
On Wed, 2005-Nov-16 04:21:09 -0800, Rob wrote:
If not, then what should I remove/keep from the
above list, to allow the deadlock to reappear and
still be able to debug the problem?
The minimum you need to get into DDB and use GDB off-line is
makeoptions DEBUG=-g
options KDB
options DDB
On Wed, Nov 16, 2005 at 04:01:36PM +0100, Lars Kristiansen wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
options GDB
Is that enough?
If your
--- Peter Jeremy [EMAIL PROTECTED] wrote:
Since your /home is almost empty, how about
(temporarily) moving the contents into /usr and
swapping onto ad0s1e rather than into a
swapfile. This should at least enable you to
build a debug kernel.
I'm now indeed building a new kernel, without
One more thing, for those who are reading this thread.
Concerning my kernel locking up while using a
swapfile:
I had an infinite while loop running during the
kernel compilation, printing out 'swapinfo' every
15 seconds. The last output before the machine goes
dead is this:
/dev/ad0s1b
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
options GDB
Is that enough?
If your system is headless, you probably want 'options BREAK_TO_DEBUGGER'
as well.
First
Rob [EMAIL PROTECTED] wrote:
Kris Kennaway [EMAIL PROTECTED] wrote:
Since you can compile a kernel without it, add DDB,
WITNESS and INVARIANTS support, then trigger the
deadlock with the swapfile, break to DDB and
examine the state of the machine. See the chapter
on kernel
--- Peter Jeremy [EMAIL PROTECTED] wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
options GDB
Is that enough?
If your system is headless, you
On Tue, Nov 15, 2005 at 07:16:47AM -0800, Rob wrote:
--- Peter Jeremy [EMAIL PROTECTED] wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
On Tue, Nov 15, 2005 at 02:15:37AM -0800, Rob wrote:
One more thing, for those who are reading this thread.
Concerning my kernel locking up while using a
swapfile:
I had an infinite while loop running during the
kernel compilation, printing out 'swapinfo' every
15 seconds. The last
On Tue, Nov 15, 2005 at 07:16:47AM -0800, Rob wrote:
--- Peter Jeremy [EMAIL PROTECTED] wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
makeoptions DEBUG=-g
options INVARIANTS
options WITNESS
options WITNESS_KDB
options KDB
options DDB
options DDB_NUMSYM
On Tue, Nov 15, 2005 at 02:15:37AM -0800, Rob wrote:
One more thing, for those who are reading this thread.
Concerning my kernel locking up while using a
swapfile:
I had an infinite while loop running during the
kernel compilation, printing out 'swapinfo' every
15 seconds. The last
On Tue, Nov 15, 2005 at 09:49:57PM +0100, Lars Kristiansen wrote:
On Tue, Nov 15, 2005 at 02:15:37AM -0800, Rob wrote:
One more thing, for those who are reading this thread.
Concerning my kernel locking up while using a
swapfile:
I had an infinite while loop running during the
On Tue, Nov 15, 2005 at 09:44:12PM +0100, Lars Kristiansen wrote:
A couple of the times but not everytime the following message was
repeatedly displayed at the console before freezing:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 273427, size: 4096
AFAICT that is just a
On 11/16/05 07:49, Lars Kristiansen wrote:
I had an infinite while loop running during the
kernel compilation, printing out 'swapinfo' every
15 seconds. The last output before the machine goes
dead is this:
/dev/ad0s1b 39848118203984830%
/dev/md0 131072 5908
On Wed, Nov 16, 2005 at 09:26:43AM +1100, Johny Mattsson wrote:
On 11/16/05 07:49, Lars Kristiansen wrote:
I had an infinite while loop running during the
kernel compilation, printing out 'swapinfo' every
15 seconds. The last output before the machine goes
dead is this:
/dev/ad0s1b
--- Peter Jeremy [EMAIL PROTECTED] wrote:
On Tue, 2005-Nov-15 02:08:12 -0800, Rob wrote:
2) Is such debugging possible on a headless PC
without a keyboard attached?
I do have serial console access.
Yes. See above URL. The advantage is that you can
(hopefully) capture a log of
On Tue, Nov 15, 2005 at 06:09:33PM -0800, Rob wrote:
...
Yes. See above URL. The advantage is that you can
(hopefully) capture a log of your debug session.
Send a serial BREAK and you should get a DDB
prompt.
What is this serial BREAK?
How do I send a serial BREAK at the serial
On Tue, Nov 15, 2005 at 07:18:35PM -0800, David Wolfskill wrote:
On Tue, Nov 15, 2005 at 06:09:33PM -0800, Rob wrote:
...
Yes. See above URL. The advantage is that you can
(hopefully) capture a log of your debug session.
Send a serial BREAK and you should get a DDB
prompt.
Kris Kennaway wrote this message on Tue, Nov 15, 2005 at 22:35 -0500:
What is this serial BREAK?
How do I send a serial BREAK at the serial
console? Is this some magic key combination?
I'm probably saying something about my age by doing this :-}
A BREAK (in serial
On Tue, Nov 15, 2005 at 07:18:35PM -0800, David Wolfskill wrote:
On Tue, Nov 15, 2005 at 06:09:33PM -0800, Rob wrote:
...
What is this serial BREAK?
How do I send a serial BREAK at the serial
console? Is this some magic key combination?
I'm probably saying something about my age
--- Rob [EMAIL PROTECTED] wrote:
Hi,
I have upgraded a Pentium-1 PC from 5 to 6-Stable,
which went smoothly.
Now I'm running 6 with GENERIC kernel, and I want
to compile a new kernel. When I start a new kernel
compilation, this process *always* freezes the PC
(no crash) when reaching
On Mon, Nov 14, 2005 at 05:52:42PM -0800, Rob wrote:
--- Rob [EMAIL PROTECTED] wrote:
Hi,
I have upgraded a Pentium-1 PC from 5 to 6-Stable,
which went smoothly.
Now I'm running 6 with GENERIC kernel, and I want
to compile a new kernel. When I start a new kernel
compilation,
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Mon, Nov 14, 2005 at 05:52:42PM -0800, Rob wrote:
Problem kind of solved:
As this PC has only 32 MB Ram, I add a swapfile.
However, when I compile the new kernel without the
swapfile, all goes well.
Since the freeze is very
On Mon, Nov 14, 2005 at 06:08:27PM -0800, Rob wrote:
I left it overnight twice for performing this
'kernel linking' stage. In both cases the machine
remained dead.
Without the swapfile, this 'kernel linking' stage
completes in just about less than a minute.
So I think it's not my
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Mon, Nov 14, 2005 at 06:08:27PM -0800, Rob wrote:
I left it overnight twice for performing this
'kernel linking' stage. In both cases the machine
remained dead.
Without the swapfile, this 'kernel linking' stage
completes in just about
On Mon, 2005-Nov-14 22:38:59 -0800, Rob wrote:
--- Kris Kennaway [EMAIL PROTECTED] wrote:
Since you can compile a kernel without it, add DDB,
WITNESS and INVARIANTS support, then trigger the
deadlock with the swapfile, break to DDB and
examine the state of the machine. See the chapter
on
44 matches
Mail list logo
