From: Bernard Pidoux F6BVP <f6bvp@free.fr>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
Ralf Baechle DL5RB <ralf@linux-mips.org>
Subject: Re: ax25 rose Re: kernel panic linux-2.6.27-rc7
Date: Tue, 30 Sep 2008 22:59:35 +0200 [thread overview]
Message-ID: <48E29337.2080400@free.fr> (raw)
In-Reply-To: <20080930111733.GB6290@ff.dom.local>
Jarek,
Yes I am using n2kpci/8390 driver.
The second patch seems to have removed the inconsistent lock state.
But the kernel panic still occured systematically.
However I did not catch netconsole messages since the patch prevented
transmission to remote console via ethernet.
Before the machine rebooted I only noted the following information at
the bottom of the local console page :
EIP: [<.....>] datagram_poll + 0xe9/0xf0
Does it help ?
Bernard
Jarek Poplawski wrote:
> On Tue, Sep 30, 2008 at 10:10:30AM +0000, Jarek Poplawski wrote:
>> On Tue, Sep 30, 2008 at 11:40:39AM +0200, Bernard Pidoux F6BVP wrote:
>>> Hi Jarek,
>> Hi Bernard,
>>
>>> Yes this is a vanilla kernel, which makes it interesting to debug.
>>> I forgot to Cc: Ralf and put it now on copy of this message.
>>> Thank you for the patch I applied.
>>> Collected data includes both events I already reported, first the
>>> inconsistent lock state,
>> I guess this netconsole is on ne2k_pci/8390 driver?
>
> If so, try this patch, please.
>
> Jarek P.
>
> ---
>
> drivers/net/lib8390.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/lib8390.c b/drivers/net/lib8390.c
> index 00d59ab..f80dcc1 100644
> --- a/drivers/net/lib8390.c
> +++ b/drivers/net/lib8390.c
> @@ -530,9 +530,9 @@ static irqreturn_t __ei_interrupt(int irq, void *dev_id)
> #ifdef CONFIG_NET_POLL_CONTROLLER
> static void __ei_poll(struct net_device *dev)
> {
> - disable_irq_lockdep(dev->irq);
> + disable_irq(dev->irq);
> __ei_interrupt(dev->irq, dev);
> - enable_irq_lockdep(dev->irq);
> + enable_irq(dev->irq);
> }
> #endif
>
>
>
next prev parent reply other threads:[~2008-09-30 20:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 12:49 kernel panic linux-2.6.27-rc7 Bernard Pidoux F6BVP
2008-09-29 12:30 ` ax25 rose " Jarek Poplawski
2008-09-30 9:40 ` Bernard Pidoux F6BVP
2008-09-30 10:10 ` Jarek Poplawski
2008-09-30 11:17 ` Jarek Poplawski
2008-09-30 20:59 ` Bernard Pidoux F6BVP [this message]
2008-09-30 21:30 ` Jarek Poplawski
2008-09-30 22:49 ` Bernard Pidoux F6BVP
2008-10-01 5:58 ` Jarek Poplawski
2008-10-02 18:20 ` Bernard, f6bvp
2008-10-02 19:48 ` Jarek Poplawski
2008-10-03 7:34 ` Jarek Poplawski
2008-10-03 7:43 ` Jarek Poplawski
2008-10-04 18:30 ` Bernard, f6bvp
2008-10-04 19:11 ` Jarek Poplawski
2008-10-04 20:09 ` Jarek Poplawski
2008-10-05 15:40 ` Bernard, f6bvp
2008-10-05 20:33 ` Jarek Poplawski
2008-10-05 21:09 ` Jarek Poplawski
2008-10-05 18:31 ` Bernard, f6bvp
2008-10-05 20:40 ` Jarek Poplawski
2008-10-05 21:18 ` Bernard, f6bvp
2008-10-05 22:05 ` [PATCH to REVERT] " Jarek Poplawski
2008-10-06 20:05 ` David Miller
2008-10-05 22:16 ` [PATCH] netrom: Fix sock_orphan() use in nr_release Jarek Poplawski
2008-10-05 13:04 ` ax25 rose Re: kernel panic linux-2.6.27-rc7 Jarek Poplawski
2008-10-01 6:58 ` [PATCH] lib8390: Fix locking in ei_poll (poll controller) Jarek Poplawski
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=48E29337.2080400@free.fr \
--to=f6bvp@free.fr \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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).