From: Ben Hutchings <ben@decadent.org.uk>
To: bo.li.liu@oracle.com
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: e1000 crash on 3.15.0-rc4
Date: Sun, 11 May 2014 13:12:12 +0100 [thread overview]
Message-ID: <1399810332.11946.127.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20140507053245.GB15783@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]
On Wed, 2014-05-07 at 13:32 +0800, Liu Bo wrote:
> Hi,
>
> I'm using qemu to load kernel of 3.15.0-rc4, and with CONFIG_E1000=y,
> everying is ok, but with CONFIG_E1000=m, I got the following crash:
>
> [...]
> [ 6.020409] tsc: Refined TSC clocksource calibration: 2491.912 MHz
> [ 6.074925] floppy: Unknown symbol mutex_lock (err 0)
> [ 6.128579] virtio_blk: Unknown symbol mutex_lock (err 0)
> [ 6.141264] i2c_core: Unknown symbol mutex_lock (err 0)
Really???
> [ 6.167490] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
> [ 6.168240] e1000: Copyright (c) 1999-2006 Intel Corporation.
> [ 6.171078] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
> [ 6.190295] BUG: spinlock bad magic on CPU#3, systemd-udevd/208
[...]
I think you may have rebuilt the kernel with lockdep enabled, but
haven't also rebuilt and installed the modules with lockdep enabled.
You should enable symbol versions to catch such mistakes.
Ben.
--
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
[-- Attachment #2: Type: text/plain, Size: 346 bytes --]
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
[-- Attachment #3: Type: text/plain, Size: 257 bytes --]
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
prev parent reply other threads:[~2014-05-11 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 5:32 e1000 crash on 3.15.0-rc4 Liu Bo
2014-05-11 12:12 ` Ben Hutchings [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=1399810332.11946.127.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=bo.li.liu@oracle.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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