From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Cedric Le Goater <clg@fr.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-kernel@vger.kernel.org, cornelia.huck@de.ibm.com,
heiko.carstens@de.ibm.com, sam@ravnborg.org,
Linux Containers <containers@lists.osdl.org>,
netdev@vger.kernel.org
Subject: Re: 2.6.23-mm1 s390 driver problem
Date: Fri, 19 Oct 2007 13:25:29 +0200 [thread overview]
Message-ID: <1192793129.25150.12.camel@localhost> (raw)
In-Reply-To: <47189242.8090006@fr.ibm.com>
On Fri, 2007-10-19 at 13:17 +0200, Cedric Le Goater wrote:
> > please cc netdev on network issues.
>
> yes.
>
> >> Bringing up interface eth0: ------------Ý cut here ¨------------
> >> Kernel BUG at 0000000000000002 Ýverbose debug info unavailable¨
> >> illegal operation: 0001 Ý#1¨
> >
> > that's a network issue ;)
> >
> >> 00000000002b3352 gives : include/linux/netdevice.h:819
> >>
> >
> > I have a feeling that we fixed this. But there's no BUG at 2.6.23-mm1's
> > include/linux/netdevice.h:819.
>
> but dev->header_ops is bogus. right ?
>
> > How about setting CONFIG_DEBUG_BUGVERBOSE=y?
>
> it is set :(
This is definitly a problem with the header_ops in the qeth network
driver. I've asked our network team to take care of it. Stay tuned..
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2007-10-19 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 20:01 2.6.23-mm1 s390 driver problem Serge E. Hallyn
2007-10-18 20:15 ` Christian Borntraeger
2007-10-18 20:31 ` Serge E. Hallyn
2007-10-19 7:47 ` Martin Schwidefsky
2007-10-19 9:16 ` Cedric Le Goater
2007-10-19 9:20 ` Martin Schwidefsky
2007-10-19 11:06 ` Cedric Le Goater
2007-10-19 9:27 ` Andrew Morton
2007-10-19 11:17 ` Cedric Le Goater
2007-10-19 11:25 ` Martin Schwidefsky [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=1192793129.25150.12.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=cornelia.huck@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=serge@hallyn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox