similar to: switching kdb off?

Hi, I have been trying to debug Xen using kdb. However, I am unable to successfully boot dom0 after compiling and installing kdb. Software/hardware config: Base distribution - Debian Lenny (64-bit) on a Dell desktop (Optiplex 780) with a serial cable to another machine. Xen 4.0.1 (without kdb) works fine. Here are the steps I followed to set up Xen-unstable with kdb. 1. Cloned code from

Hi Guys, Thanks for the interest in the xen hypervisor debugger, prev known as kdb. Btw. I''m gonna rename it to xdb for xen-debugger or hdb for hypervisor debugger. KDB is confusing people with linux kdb debugger and I often get emails where people think they need to apply linux kdb patch also... Anyways, attaching patch that is cleaned up of my debug code that I accidentally left in

I asked this a few weeks ago but didn''t get a response, so at the risk of being a nag, I''ll abbreviate and restate. I know there are other Xen specific debuggers, but I want to know if there''s any reason why SGI''s kdb, http://oss.sgi.com/projects/kdb, should not be included in a dom0 pv-ops kernel? While the patches apply cleanly and build, the result is that

On 24 Apr 2002, "Shirish H. Phatak" <shirish@tacitnetworks.com> wrote: > Since there appears to be a dedicated group of users and lots of > activity, maybe we can convince Martin to roll in these patches and make > a new release? I have been really lax in supporting librsync for the last few months, because of a new job and taking over maintenance of rsync

I admit I was scepticle of this suggestion - but it actually seems to have worked. COmpiling a straight GENERIC kernel with KDB and DDB included do seem to have made my irq22 interrupt storms go away. Certainly I have spent some time trying to provoke the problem and not managed to make it read it's ugly head again. The thing is though, this doen't make me particularly happy - as I am

[ Tried to check the archives but the website seems to be down or something ] On one of our installations, I am seeing messages such as: EXT3-fs warning (device ide0(3,9))): ext3_free_inode: bit already clearned for inode 14 Anybody know exactly what they mean? These would be on a 0.0.6a system. b.

Im intending use Ext3 file system in my web farm. Im using RedHat 6.2 (kernel 2.2.16-3) and Turbo Linux Cluster Server 6.0. I have NO SUCCESS in path my own kernel. I downloaded the following ext3 packages: ext3-0.0.2f.tar.gz (linux-2.2.16-3.kdb.diff , linux-2.2.16-3.ext3.diff ) e2fsprogs-1.20-0.WIP.i386.rpm e2fsprogs-1.20-0.WIP.src.rpm e2fsprogs-1.20-0ext3.i386.rpm

Please give me some pointers... Thanks a lot!

I am the author of BackupPC (http://backuppc.sourceforge.net) and I am working on adding rsync support to BackupPC. I am implementing the server-side in perl, and the client will run vanilla rsync. (BTW, is there the protocol documented? I've answered all my questions by looking at the source, but it would be great to check against any docs.) I started with librsync 0.9.3 and the

There is a patch for xen linux 2.6.10 that enables kdb. It works with the xen 2.0.3 and xen-2.0-testing. (I intend to keep it current with 2.0-testing, but I can''t guarantee instant currency every time there are changes to the test branch.) The patch and a brief HOWTO are located at http://www.ncultra.org/xen/kdb/ kdb works with both privileged and unprivileged kernels. Mike --

Fix the polling section of the hvc driver to use the global "last_hvc" variable, rather than the ttys. With this change debugging a xen dom0 kernel is possible via the following kernel parameter: kgdboc=hvc0 Signed-off-by: Ben Guthro <Benjamin.Guthro@citrix.com> diff --git a/drivers/tty/hvc/hvc_console.c b/drivers/tty/hvc/hvc_console.c index 2d691eb..3750e74 100644 ---

Hi, kdb: to debug xen hypervisor, could also debug guests gdbsx: to debug PV/HVM linux guests The tree is : http://xenbits.xensource.com/ext/debuggers.hg See README-dbg. You''ll need to setup serial access for kdb. Thanks, Mukesh > > Hi Dan, > > I''m currently using your version of ssplitd as it is. I haven''t tried > kdb. For some reason I

Hello All, I am running Linux 2.4.7-10, 2.4.18-4 and 2.4.19-pre9, I see the following oops quite often (mainly on 2.4.19-pre9 with kdb). All the kernels I use have the kdb patch installed. 1 kmem_cache_alloc (offset 0x125) get_unused_buffer_head journal_write_metadata_buffer journal_commit_transaction kjournald kernel_thread kmem_cache_alloc dis xchg %eax, (%ebx) cmp $0x5a2cf071, %eax (where

I see the following with a FreeBSD 5.3 DomU on 2.0.7 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xca7a0088 fault code = supervisor read, page not present instruction pointer = 0x819:0xc0183343 stack pointer = 0x821:0xca069d30 frame pointer = 0x821:0x0 code segment = base 0x235, limit 0x8485e7c3, type 0x9

Hello, Now that kernel 2.2.20 is out with security fixes, I'd be interested in using it with ext3. The latest patch for 2.2.19, 0.0.7a, applies with some offset (both with and without kdb), and even compiles (without kdb), but I scarcely know what I am doing so haven't tried it yet. Could people in the know enlighten me on that point? I guess there is little chance for another ext3

hi guys i just partially upgrade centos 3.4 to centos 4(using apt-get) and im having a problem removing kdb 1.08-10.2, kbd 1.12-2 is already installed and im trying to remove kdb 1.08 through apt-get and rpm -e here's what happened when i use apt-get: # apt-get remove kbd#1.08-10.2 Reading Package Lists... Done Building Dependency Tree... Done The following packages will be REMOVED:

Hi all, When i do ''xm dmesg'' the last statement says "*** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen)" (i have no clue what''s that supposed to mean??) But when i press ctrl-a three times at the serial console, nothing happens. Iam using minicom to connect to the serial port of xen machine. Once xen

I previously wrote: > I have come across what appears to be a bug in __invalidate_buffers() > w.r.t. the change in ext3-0.0.6 using BH_JDirty instead of BH_Dirty > for buffers held in the journal. If invalidate_buffers() is called > on a device (LVM likes to do this a lot, for whatever reason), it yanks > JDirty buffers out from underneath the journal layer, and causes an > oops

After booting from a 10-alpha2 disk I am seeing "lock order reversal" messages show up from time to time. Current logs have 35 entries. The machine normally is running 9.1 from zfs root and I have setup a separate disk (eSATA case connected through backplane port to onboard SATA port) that I have installed 10-alpha amd64 onto a ufs partition to test port building with. I started by

Working on the Dell R420 today, got most of it working, even the broadcom ethernet cards! However, I get the following when I reboot the system: Syncing disks, vnodes remaining...4 Sleeping thread (tid 100107, pid 9) owns a non-sleepable lock KDB: stack backtrace of thread 100107: sched_switch() at sched_switch+0x19f mi_switch() at mi_switch+0x208 sleepq_switch() at sleepq_switch+0xfc