linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eddy Petrisor <eddy.petrisor@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	"debian-powerpc@lists.debian.org"
	<debian-powerpc@lists.debian.org>
Subject: Re: 2.6.14 USB vs. sleep issues
Date: Fri, 11 Nov 2005 23:47:46 +0200	[thread overview]
Message-ID: <43751182.1020009@gmail.com> (raw)
In-Reply-To: <1131229041.5229.29.camel@gaston>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=x-user-defined; format=flowed, Size: 1075 bytes --]



Benjamin Herrenschmidt wrote:
> On Sat, 2005-11-05 at 22:58 +0100, Bin Zhang wrote:
> 
>>On 11/3/05, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>>
>>>For those who experience crashes on sleep and/or wakeup (typically due
>>>to USB) with 2.6.14, I made a test patch that might help. Please let me
>>>know if it makes things more reliable.
>>>
>>
>>I've tried your patch with usb wifi dlink dwl-g122 (my eth1). It works.
>>There are some differences in /var/log/syslog :
> 
> 
> I have another patch tho:

With this patch the kernel panics on my PowerBook 5,2

I made a few pictures with my phone and I can put them smewhere, if needed.

I will try tonight the third patch you proposed and the kernel is 
compiling now...


BTW, is there any difference between the resulted .ko files when made with:

make SUBDIRS=drivers/usb/core

make SUBDIRS=drivers/usb/core modules

and what the make command ran from the root of the kernel source?

-- 
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein

  parent reply	other threads:[~2005-11-11 21:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  6:33 2.6.14 USB vs. sleep issues Benjamin Herrenschmidt
2005-11-03  9:03 ` Eddy Petrişor
2005-11-03 21:21   ` Benjamin Herrenschmidt
2005-11-04  7:13     ` Eddy Petrişor
2005-11-04  7:18       ` Benjamin Herrenschmidt
2005-11-04 19:32         ` Vivenzio Pagliari
2005-11-04 21:48           ` Benjamin Herrenschmidt
2005-11-05 21:58 ` Bin Zhang
2005-11-05 22:17   ` Benjamin Herrenschmidt
2005-11-06 10:54     ` Bin Zhang
2005-11-11 21:47     ` Eddy Petrisor [this message]
2005-11-11 21:52       ` Benjamin Herrenschmidt
2005-11-12  8:53         ` Eddy Petrisor
2005-11-12  9:45           ` Eddy Petrişor
2005-11-14  7:19         ` Arkadiusz Miskiewicz
2005-11-14  8:06           ` Benjamin Herrenschmidt
2005-11-23 21:55         ` Gaudenz Steinlin
2005-11-23 22:09           ` Benjamin Herrenschmidt
2005-11-07  9:13 ` Charles-Edouard Ruault
2005-11-07 14:54   ` Wolfram Quester
2005-11-07 21:00   ` Benjamin Herrenschmidt
2005-11-10  1:12     ` Eddy Petrişor
2005-11-10  1:51       ` Benjamin Herrenschmidt
2005-11-11  0:24 ` Wolfgang Pfeiffer
2005-11-16 18:09 ` Wolfgang Pfeiffer
2005-11-16 18:25   ` Wolfgang Pfeiffer
2005-11-16 21:01   ` Benjamin Herrenschmidt
2005-11-16 23:21     ` Eddy Petrisor

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=43751182.1020009@gmail.com \
    --to=eddy.petrisor@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@ozlabs.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).