From: Kip Macy <kip.macy@gmail.com>
To: Jon Mason <jdmason@us.ibm.com>
Cc: peter bier <peter_bier@web.de>, xen-devel@lists.xensource.com
Subject: Re: problem with the pro/1000 driver for intel gigabit ethernet card
Date: Wed, 11 May 2005 12:06:22 -0700 [thread overview]
Message-ID: <b1fa29170505111206230da1e3@mail.gmail.com> (raw)
In-Reply-To: <200505111348.53769.jdmason@us.ibm.com>
We're not seeing it on 2.0.5 either. The first thing I would do would
be to diff the driver between 2.6.10 and 2.6.11.
-Kip
On 5/11/05, Jon Mason <jdmason@us.ibm.com> wrote:
> I have been seeing the exact same problem for a while (on xen-unstable). I
> think I didn't see this problem on Xen 2.0.5 (but I'm not 100% sure).
>
> I can open a bug in bugzilla.xensource.com if no one else is willing.
>
> Thanks,
> Jon
>
> On Wednesday 11 May 2005 12:41 pm, Kip Macy wrote:
> > I can confirm that I've seen the exact same behaviour.
> >
> > -Kip
> >
> > On 5/11/05, peter bier <peter_bier@web.de> wrote:
> > > I encountered a problem with dom0 when rebooting and running an intel
> > > gigabit card using the pro/1000 driver. When the system tries to shut
> > > down I get the following output of an strace command :
> > >
> > > .........
> > > 17:10:49.063616 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 <0.000029>
> > > 17:10:49.063689 ioctl(3, 0x8913, 0xbffffc80) = 0 <0.000018>
> > > 17:10:49.063751 ioctl(3, 0x8914, 0xbffffc80) = 0 <535.114722>
> > > 17:19:44.178567 close(3) = 0 <0.000026>
> > > 17:19:44.178679 exit_group(0) = ?
> > >
> > > observe the more than 500 seconds it takes for the second ioctl to
> > > complete !! I have found out that any input on the console keyboard or
> > > network interface immediately causes the system call to return.
> > >
> > > Is there a problem with interrupt delivery ?
> > >
> > > Peter Bier
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2005-05-11 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 16:24 problem with the pro/1000 driver for intel gigabit ethernet card peter bier
2005-05-11 17:41 ` Kip Macy
2005-05-11 18:48 ` Jon Mason
2005-05-11 19:06 ` Kip Macy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1fa29170505111206230da1e3@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=jdmason@us.ibm.com \
--cc=peter_bier@web.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.