From: Martin Zwickel <martin.zwickel@novabasedigitaltv.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Martin Zwickel <martin.zwickel@novabasedigitaltv.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: FDTI-SIO: kernel-oops after resume
Date: Wed, 10 Jun 2009 10:24:17 +0200 [thread overview]
Message-ID: <20090610082417.GA32313@novabasedigitaltv.de> (raw)
In-Reply-To: <20090610005018.2c84d229.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
On Wed, Jun 10, 2009 at 08:50:18AM +0100, <Andrew Morton> bubbled:
> On Tue, 9 Jun 2009 08:39:48 +0200 Martin Zwickel <martin.zwickel@novabasedigitaltv.de> wrote:
>
> > My kernel runs with SMP and HIGHMEM if it matters:
> > Linux tt-business 2.6.29.4 #3 SMP PREEMPT Fri Jun 5 00:03:39 WEST 2009 i686 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux
> >
>
> The oops is very very similar to the one which Daniel Mack reported,
> and which was fixed by
>
> commit c16199fcd341f10147eb2e29a60aed41ceca55b4
> Author: Alan Stern <stern@rowland.harvard.edu>
> Date: Thu Apr 30 10:06:19 2009 -0400
>
> usb-serial: ftdi_sio: fix reference counting of ftdi_private
>
> but your 2.6.29.4 contained that fix, so it seems that we still have a
> problem here?
Could be, or I'm doing something wrong.
I will clean the kernel, rebuild 2.6.29.4, reboot, try to crash it and
let you know.
If I should try some patches, please let me know.
Best regards and thanks,
Martin
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-10 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 6:39 Martin Zwickel
2009-06-10 7:50 ` Andrew Morton
2009-06-10 8:24 ` Martin Zwickel [this message]
2009-06-10 11:18 ` Martin Zwickel
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=20090610082417.GA32313@novabasedigitaltv.de \
--to=martin.zwickel@novabasedigitaltv.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®