From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Gerrit Renker <gerrit@erg.abdn.ac.uk>, netdev@vger.kernel.org
Subject: Re: Oops in e100_up
Date: Wed, 22 Aug 2007 13:47:23 -0300 [thread overview]
Message-ID: <20070822164723.GT10392@ghostprotocols.net> (raw)
In-Reply-To: <46CC65B8.1030006@intel.com>
Em Wed, Aug 22, 2007 at 09:35:04AM -0700, Kok, Auke escreveu:
> Gerrit Renker wrote:
> >With the davem-2.6.24 tree I get the following Oops in the e100 driver
> >(cribbed from console):
> >
> >Code: 6c ff ff ff 8b 48 0c ba 01 00 00 00 89 f0 e8 1b f2 ff ff c7 86 9c 00
> >00 00
> > 01 00 00 00 e9 4e ff ff ff 89 d0 e8 b3 f8 0b 00 eb 8e <0f> 0b eb fe
> > 55 89 e5
> > 56 53 83 ec 0c 8b 98 dc 01 00 00 e8 ff b9
> >
> >EIP: e100_up+0x11d/0x121
> >
> >SS:ESP 0068:f759ce38
> >
> >Stack: syscall_call -> sys_ioctl -> vfs_ioctl -> do_ioctl -> sock_ioctl ->
> >inet_ioctl -> devinet_ioctl ->
> > dev_change_flags -> dev_open -> e100_open -> oops
> >
> >The system log then goes on reporting "eth0: link up, 100Mbps,
> >full-duplex" and hangs while trying to
> >restore the serial console state (not sure that this is related).
>
> restore? Is this during resume from suspend or something?
This seems to have been fixed by a bug reported by akpm and fixed by
Thomas Graf, check a recent post with "netconsole" on the subject.
- Arnaldo
prev parent reply other threads:[~2007-08-22 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 8:56 Oops in e100_up Gerrit Renker
2007-08-22 9:17 ` David Miller
2007-08-22 16:35 ` Kok, Auke
2007-08-22 16:47 ` Arnaldo Carvalho de Melo [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=20070822164723.GT10392@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=auke-jan.h.kok@intel.com \
--cc=gerrit@erg.abdn.ac.uk \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).