From: Martin Lorenz <martin@lorenz.eu.org>
To: linux-thinkpad@linux-thinkpad.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ltp] do I have to worry?
Date: Tue, 12 Sep 2006 16:41:06 +0200 [thread overview]
Message-ID: <20060912144106.GT7767@gimli> (raw)
In-Reply-To: <20060912102844.GH7767@gimli>
On Tue, Sep 12, 2006 at 12:28:44PM +0200, Dipl.-Ing. Martin Lorenz wrote:
> Hi all,
>
> I found another error in my dmesg:
>
> [50219.992000] e1000: eth0: e1000_watchdog: NIC Link is Down
> [50225.266000] Trying to free already-free IRQ 201
> [50225.271000] bridge-eth0: disabling the bridge
> [50225.274000] bridge-eth0: down
> [50225.317000] IRQ handler type mismatch for IRQ 90
> [50225.318000] [<c0103d74>] show_trace_log_lvl+0x5b/0x14d
> [50225.318000] [<c01044a3>] show_trace+0xf/0x11
> [50225.318000] [<c01045a6>] dump_stack+0x15/0x17
> [50225.318000] [<c01403bf>] setup_irq+0x17d/0x190
> [50225.318000] [<c014044e>] request_irq+0x7c/0x98
> [50225.318000] [<c02514ea>] e1000_open+0xcd/0x1a4
> [50225.319000] [<c0295134>] dev_open+0x2b/0x62
> [50225.320000] [<c0293c59>] dev_change_flags+0x47/0xe4
> [50225.321000] [<c02c7791>] devinet_ioctl+0x252/0x556
> [50225.322000] [<c028b083>] sock_ioctl+0x19a/0x1be
> [50225.323000] [<c016b58b>] do_ioctl+0x1f/0x62
> [50225.324000] [<c016b813>] vfs_ioctl+0x245/0x257
> [50225.324000] [<c016b871>] sys_ioctl+0x4c/0x67
> [50225.324000] [<c0102dab>] syscall_call+0x7/0xb
> [50225.324000] DWARF2 unwinder stuck at syscall_call+0x7/0xb
> [50225.324000] Leftover inexact backtrace:
> [50225.324000] e1000: eth0: e1000_request_irq: Unable to allocate interrupt
> Error: -16
> [50226.370000] bridge-eth0: enabling the bridge
> [50226.370000] bridge-eth0: up
>
>
> I have no idea what it tries to tell me here.
> it happened on undocking my X60s from the ultrabay
>
now I saw the same one twice in the dmesg on resume
if I'm not very much mistaken this is an e1000 issue
here is the one on resume:
[65284.946000] Trying to free already-free IRQ 201
[65284.949000] bridge-eth0: disabling the bridge
[65284.952000] bridge-eth0: down
[65284.966000] IRQ handler type mismatch for IRQ 90
[65284.966000] [<c0103d74>] show_trace_log_lvl+0x5b/0x14d
[65284.966000] [<c01044a3>] show_trace+0xf/0x11
[65284.967000] [<c01045a6>] dump_stack+0x15/0x17
[65284.967000] [<c01403bf>] setup_irq+0x17d/0x190
[65284.967000] [<c014044e>] request_irq+0x7c/0x98
[65284.967000] [<c02514ea>] e1000_open+0xcd/0x1a4
[65284.968000] [<c0295134>] dev_open+0x2b/0x62
[65284.969000] [<c0293c59>] dev_change_flags+0x47/0xe4
[65284.970000] [<c02c7791>] devinet_ioctl+0x252/0x556
[65284.971000] [<c028b083>] sock_ioctl+0x19a/0x1be
[65284.972000] [<c016b58b>] do_ioctl+0x1f/0x62
[65284.972000] [<c016b813>] vfs_ioctl+0x245/0x257
[65284.973000] [<c016b871>] sys_ioctl+0x4c/0x67
[65284.973000] [<c0102dab>] syscall_call+0x7/0xb
[65284.973000] DWARF2 unwinder stuck at syscall_call+0x7/0xb
[65284.973000] Leftover inexact backtrace:
[65284.973000] e1000: eth0: e1000_request_irq: Unable to allocate interrupt
Error: -16
[65286.019000] IRQ handler type mismatch for IRQ 98
[65286.019000] [<c0103d74>] show_trace_log_lvl+0x5b/0x14d
[65286.019000] [<c01044a3>] show_trace+0xf/0x11
[65286.019000] [<c01045a6>] dump_stack+0x15/0x17
[65286.019000] [<c01403bf>] setup_irq+0x17d/0x190
[65286.019000] [<c014044e>] request_irq+0x7c/0x98
[65286.019000] [<c02514ea>] e1000_open+0xcd/0x1a4
[65286.020000] [<c0295134>] dev_open+0x2b/0x62
[65286.021000] [<c0293c59>] dev_change_flags+0x47/0xe4
[65286.021000] [<c02c7791>] devinet_ioctl+0x252/0x556
[65286.022000] [<c028b083>] sock_ioctl+0x19a/0x1be
[65286.023000] [<c016b58b>] do_ioctl+0x1f/0x62
[65286.023000] [<c016b813>] vfs_ioctl+0x245/0x257
[65286.023000] [<c016b871>] sys_ioctl+0x4c/0x67
[65286.024000] [<c0102dab>] syscall_call+0x7/0xb
[65286.024000] DWARF2 unwinder stuck at syscall_call+0x7/0xb
[65286.024000] Leftover inexact backtrace:
[65286.024000] e1000: eth0: e1000_request_irq: Unable to allocate interrupt
Error: -16
[65287.070000] bridge-eth0: enabling the bridge
[65287.070000] bridge-eth0: up
thanks
mlo
--
Dipl.-Ing. Martin Lorenz
They that can give up essential liberty
to obtain a little temporary safety
deserve neither liberty nor safety.
Benjamin Franklin
please encrypt your mail to me
GnuPG key-ID: F1AAD37D
get it here:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D
ICQ UIN: 33588107
next parent reply other threads:[~2006-09-12 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060912102844.GH7767@gimli>
2006-09-12 14:41 ` Martin Lorenz [this message]
2006-09-13 8:46 ` [ltp] do I have to worry? Thomas Gleixner
[not found] ` <450712D2.6080209@intel.com>
[not found] ` <20060912205154.GB7767@gimli>
[not found] ` <450720CA.3070303@intel.com>
[not found] ` <20060912214845.GE7767@gimli>
[not found] ` <45073051.1030708@intel.com>
2006-09-14 10:32 ` Martin Lorenz
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=20060912144106.GT7767@gimli \
--to=martin@lorenz.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-thinkpad@linux-thinkpad.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