[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1659130373.1834747.1330645308581.JavaMail.root@zimbra-prod-mbox-2.vmware.com>
Date: Thu, 1 Mar 2012 15:41:48 -0800 (PST)
From: Andrei Warkentin <awarkentin@...are.com>
To: Jason Wessel <jason.wessel@...driver.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Andrei Warkentin <andreiw@...are.com>,
kgdb-bugreport@...ts.sourceforge.net,
Matt Mackall <mpm@...enic.com>,
Andrei Warkentin <andrey.warkentin@...il.com>
Subject: Re: [PATCHv3 1/3] NETPOLL: Extend rx_hook support.
Hi,
----- Original Message -----
> From: "Jason Wessel" <jason.wessel@...driver.com>
> To: "Andrei Warkentin" <awarkentin@...are.com>
> Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, "Andrei Warkentin" <andreiw@...are.com>,
> kgdb-bugreport@...ts.sourceforge.net, "Matt Mackall" <mpm@...enic.com>, "Andrei Warkentin"
> <andrey.warkentin@...il.com>
> Sent: Thursday, March 1, 2012 5:24:18 PM
> Subject: Re: [PATCHv3 1/3] NETPOLL: Extend rx_hook support.
> > I did have a question, because it seems you were using qemu / kvm.
> I have a number of test cases that use kvm, but the netkkgdb does
> not seem to work with the nc. My question is how am I supposed to
> actually use the netkgdb?
>
> Here is what I observe on the target system:
>
> insmod netkgdb.ko netkgdb=@/,@10.0.2.2/
> echo g > /proc/sysrq-trigger
>
> On my host system:
> nc.traditional -l -u -p 7777
>
> I will type help, and then the netkgdb is toast. It doesn't seem to
> respond anymore.
>
Strange. I've just repeated your steps (I didn't build as a ko before, but now I did)
and I don't see this problem. Can you tell me your qemu/kvm command line?
With qemu I've see odd behavior with ne2k_pci, which is the default
(qemu would wedge) occasionally. If you are using ne2000, can you try rtl8139?
Note: I just tried ne2k_pci, and other than having to specify a local
IP address (something I don't need to for rtl8139). I've also realized
that if you insert netkgdb as a module without any parameters, it
doesn't bind to existing netdevs - that's a bug.
Anything I should know about your network topology?
Can you also apply the multi-I/O-backend patch and boot with kgdboc=kbd, and
see if the VM is toast after you type "help".
A
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists