Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*can\'t\s+enter\s+KDB\s+after\s+panic\?\s*$/: 14 ]

Total 14 documents matching your query.

1. can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Wed, 21 Feb 2001 20:37:37 -0600
I'm using kdb-v1.7-2.4.0.gz off the FTP site on a 2.4.1 kernel. I have a serial console for my machine setup (with mingetty on the tty device to keep it open). When the machine is running, I can use
/archives/kdb/2001-02/msg00004.html (7,581 bytes)

2. Re: can't enter KDB after panic? (score: 1)
Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Thu, 22 Feb 2001 15:13:28 +1100
If the machine is spinning with interrupts disabled then the IRQ from the serial line is not being processed so ctrl-A does not get in. This is a standard problem with the serial line and keyboard, y
/archives/kdb/2001-02/msg00005.html (8,731 bytes)

3. Re: can't enter KDB after panic? (score: 1)
Author: Alan Jones <alan.jones@xxxxxxx>
Date: Thu, 22 Feb 2001 18:36:09 +0000 (UTC)
I'm using kdb-v1.7-2.4.2-pre1 with 2.4.1 (which applied cleanly!) on a UP system and it makes it into kdb on panic. I'm also using getty, not minigetty but getty, but I've also disabled it in the pas
/archives/kdb/2001-02/msg00006.html (9,780 bytes)

4. Re: can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Thu, 22 Feb 2001 17:31:22 -0600
No version of KDB I've ever used has automaticaly dropped into KDB on a panic() call. An oops, yes, but not a panic. I did a bit more research. I only see this problem on SMP 2.4 machines. A UP 2.4 m
/archives/kdb/2001-02/msg00007.html (9,219 bytes)

5. Re: can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Thu, 22 Feb 2001 17:48:20 -0600
This may be true if KDB automatically breaks because of an oops. But there are cases where you get your kernel into some sort of deadlock state, and you need to force a break manually. You need to ha
/archives/kdb/2001-02/msg00008.html (8,681 bytes)

6. Re: can't enter KDB after panic? (score: 1)
Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Fri, 23 Feb 2001 15:12:43 +1100
True. See patch below. panic() disables the APICs which turns off all interrupts, including the NMI watchdog. panic() also disables all the other cpus. This patch renames the existing kdb panic to oo
/archives/kdb/2001-02/msg00011.html (15,247 bytes)

7. Re: can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Fri, 23 Feb 2001 14:24:10 -0600
Sweet! Thanks for you help. -- Ken Preslan <kpreslan@xxxxxxxxxxx> Code Monkey Sistina Software, Inc.
/archives/kdb/2001-02/msg00012.html (8,669 bytes)

8. can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Wed, 21 Feb 2001 20:37:37 -0600
Hi, I'm using kdb-v1.7-2.4.0.gz off the FTP site on a 2.4.1 kernel. I have a serial console for my machine setup (with mingetty on the tty device to keep it open). When the machine is running, I can
/archives/kdb/2001-02/msg00020.html (7,581 bytes)

9. Re: can't enter KDB after panic? (score: 1)
Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Thu, 22 Feb 2001 15:13:28 +1100
If the machine is spinning with interrupts disabled then the IRQ from the serial line is not being processed so ctrl-A does not get in. This is a standard problem with the serial line and keyboard, y
/archives/kdb/2001-02/msg00021.html (8,759 bytes)

10. Re: can't enter KDB after panic? (score: 1)
Author: Alan Jones <alan.jones@xxxxxxx>
Date: Thu, 22 Feb 2001 18:36:09 +0000 (UTC)
I'm using kdb-v1.7-2.4.2-pre1 with 2.4.1 (which applied cleanly!) on a UP system and it makes it into kdb on panic. I'm also using getty, not minigetty but getty, but I've also disabled it in the pas
/archives/kdb/2001-02/msg00022.html (9,803 bytes)

11. Re: can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Thu, 22 Feb 2001 17:31:22 -0600
No version of KDB I've ever used has automaticaly dropped into KDB on a panic() call. An oops, yes, but not a panic. I did a bit more research. I only see this problem on SMP 2.4 machines. A UP 2.4 m
/archives/kdb/2001-02/msg00023.html (9,334 bytes)

12. Re: can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Thu, 22 Feb 2001 17:48:20 -0600
This may be true if KDB automatically breaks because of an oops. But there are cases where you get your kernel into some sort of deadlock state, and you need to force a break manually. You need to ha
/archives/kdb/2001-02/msg00024.html (8,808 bytes)

13. Re: can't enter KDB after panic? (score: 1)
Author: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date: Fri, 23 Feb 2001 15:12:43 +1100
True. See patch below. panic() disables the APICs which turns off all interrupts, including the NMI watchdog. panic() also disables all the other cpus. This patch renames the existing kdb panic to oo
/archives/kdb/2001-02/msg00027.html (15,274 bytes)

14. Re: can't enter KDB after panic? (score: 1)
Author: Ken Preslan <kpreslan@xxxxxxxxxxx>
Date: Fri, 23 Feb 2001 14:24:10 -0600
Sweet! Thanks for you help. -- Ken Preslan <kpreslan@xxxxxxxxxxx> Code Monkey Sistina Software, Inc.
/archives/kdb/2001-02/msg00028.html (8,781 bytes)


This search system is powered by Namazu