public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>, colin@colino.net
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6 : cdc_acm problem
Date: Mon, 10 Nov 2003 04:21:38 -0800	[thread overview]
Message-ID: <3FAF82D2.2050004@pacbell.net> (raw)
In-Reply-To: <20031109225027.GA2425@kroah.com>

>>The problem is that cdc_acm calls a "softirq-only" routine
>>in a hardirq context.  See this patch:
>>
>>http://marc.theaimsgroup.com/?l=linux-usb-devel&m=106764585001038&w=2
>>
>>It's not clear that'll make it into 2.6.0-final.
> 
> 
> I've not planned to submit it for 2.6.0 as it's a relativly big change,
> and I don't have the hardware to test it out.  Anyone have any other
> thoughts about this?

Doesn't seem big to me.  It could be shrunk a smidgeon, but
that's the version that's gotten the positive test results.

The folk who have this kind of hardware have reported this
happening for quite a few months now, and it does seem to
fill up log buffers with catastrophic-seeming stack traces.

Colin, does it fix your problem?  Can you eke more than
twenty minutes from your laptop battery now?  :)

- Dave


  reply	other threads:[~2003-11-10 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09 17:21 kernel 2.6 : cdc_acm problem David Brownell
2003-11-09 22:50 ` Greg KH
2003-11-10 12:21   ` David Brownell [this message]
2003-11-11 12:39     ` Colin Leroy
     [not found] <Q1or.1EU.17@gated-at.bofh.it>
     [not found] ` <Q6Hy.T5.11@gated-at.bofh.it>
2003-11-10 19:16   ` Peter Matthias
     [not found] <20031109122039.47e78a91.colin@colino.net>
2003-11-09 11:11 ` Benjamin Herrenschmidt

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=3FAF82D2.2050004@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=benh@kernel.crashing.org \
    --cc=colin@colino.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@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