[Xen-devel] RE: Network stops responding after some time

[Adnan Khaleel <adnan@xxxxxxxxxx>]

Hello Ian,

Thanks for your response. I haven't had much luck with unstable. I cannot even 
boot into Dom0 and I get the following message 
"waiting for /dev/hda2 to appear .... exiting to /bin/sh" (the OS is installed 
in /dev/hda2)

It won't let me mount /dev/hda2 and I do not see /dev/hda2 either, however when 
I exit I see a message "/dev/hda2 - Busy" - Strange!

I'm not sure why this is happening as the boot messages that appear earlier 
indicate  all IDE devices are properly identified etc. Any guesses?

Coming back to the original problem, as for dmesg, I had posted the dmesg on an 
earlier post on xen-devel - "RE: [Xen-devel] Network stops responding after 
some time" in which you had mentioned that the IRQ routing maybe causing the 
problem.
How can I enable the debug messages for the eth IRQ? Are there any debug 
switches or other debug monitors I can enable to give me a better picture of 
whats happening?

I am in need of desperate assistance as I am at my wits end :)

Sincerely,

Adnan



----- Original Message -----
From: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
To: adnan@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Ian.Pratt@xxxxxxxxxxxx
Sent: Tue, 25 Jul 2006 10:08:18 -0500
Subject: RE: Network stops responding after some time


> > I need help in trying to understand why the ethernet driver has locked
> up
> > and how I can go about outputting debug messages. I see in
> > /proc/interrrupts that the interrupt count of eth0 just stops
> incrementing.
> > I've tried different (3Com, Realtek 8169, Realtek 8139) based network
> cards
> > and this happens with all. I'm not sure what is so unique about my
> system
> > that might be causing this to lockup, its a regular Nforce3 based
> system
> > with 512MB ram. This problem does not happen if I'm not using a Xen
> enabled
> > kernel. This is entirely happening in dom0 and there aren't any user
> > domains so its not a bridging issue. I've also disabled the Xen
> backend
> > drivers (netbk.ko and netloop.ko) so its talking to the network chip
> > directly.
> 
> Which xen version? Can you repro on unstable? Is there anything
> interesting in 'dmesg'?
> Best,
> Ian
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel