RR "%s(): %s: state=%d, current state=%d\n",
> __FUNCTION__, pci_name(dev), state, dev->current_state);
> return -EINVAL;
> } [...else...]
From: Stefan Richter <[EMAIL PROTECTED]>
Subject: firewire: fw-ohci: ignore failure of pci_set_power_s
On 5 Sep, Andrew Morton wrote:
>> On Wed, 05 Sep 2007 19:47:42 +0200 Stefan Richter <[EMAIL PROTECTED]> wrote:
>> >>> Trying to free already-free IRQ 40
>> >>> pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
>> >>> firewire_ohci: pci_set_power_state failed with
>> >>> -22<3>pci_devi
> On Wed, 05 Sep 2007 19:47:42 +0200 Stefan Richter <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> >>> Trying to free already-free IRQ 40
> >>> pci_set_power_state(): 0002:20:0e.0: state=3, current state=5
> >>> firewire_ohci: pci_set_power_state failed with
> >>> -22<3>pci_device_suspend():
>>> On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <[EMAIL PROTECTED]> wrote:
>>> The kernel is:
Linux kismet 2.6.22-1-powerpc #1 Sun Jul 29 13:58:06 CEST 2007 ppc
GNU/Linux
>>> The relveant debian package:
linux-image-2.6.22-1-powerpc_2.6.22-3_powerpc.deb
>>> I'm running a mixture of
Rogério Brito wrote on 2007-08-27:
> If things progress well, I will incrementally include features on the
> kernel that I need (I left out, for instance, the Firewire subsystem, so
> that compilation wouldn't take more than an hour here, despite the fact
> that I do need Firewire support on the ke
From: Stefan Richter <[EMAIL PROTECTED]>
Subject: firewire: fw-ohci: ignore failure of pci_set_power_state (fix suspend
regression)
Fixes "Sleep problems with kernels >= 2.6.21 on powerpc",
http://lkml.org/lkml/2007/8/25/155.
Like it was suggested earlier in http://lkml.org
Stefan Richter wrote:
Randy Dunlap wrote:
On Wed, 5 Sep 2007 10:07:54 -0700 Andrew Morton wrote:
So here is the output from dmesg that suggested to me that firewire
might be a problem:
Straightforward regression, two reporters, nothing happening.
(material for ksummit discussion, e.g.)
It's
Andrew Morton wrote:
>> On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <[EMAIL PROTECTED]> wrote:
>> Hello!
>>
>>> I don't have traces at hand and due to lack of time cannot reproduce it
>>> up to tomorrow. However this hint may speed up your analysis!
>> Sorry for the delay, but my desktop PC had a
Randy Dunlap wrote:
> On Wed, 5 Sep 2007 10:07:54 -0700 Andrew Morton wrote:
>>> So here is the output from dmesg that suggested to me that firewire
>>> might be a problem:
>> Straightforward regression, two reporters, nothing happening.
>
> (material for ksummit discussion, e.g.)
It's a simple
On Wed, 5 Sep 2007 10:07:54 -0700 Andrew Morton wrote:
> > On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <[EMAIL PROTECTED]> wrote:
> > Hello!
> >
> > > I don't have traces at hand and due to lack of time cannot reproduce it
> > > up to tomorrow. However this hint may speed up your analysis!
> >
> On 30 Aug 2007 22:42:46 +0200 "Tim Teulings" <[EMAIL PROTECTED]> wrote:
> Hello!
>
> > I don't have traces at hand and due to lack of time cannot reproduce it
> > up to tomorrow. However this hint may speed up your analysis!
>
> Sorry for the delay, but my desktop PC had an urgent hard disk pr
Hello!
I don't have traces at hand and due to lack of time cannot reproduce it
up to tomorrow. However this hint may speed up your analysis!
Sorry for the delay, but my desktop PC had an urgent hard disk problem I
had to fix ASASP.
So here is the output from dmesg that suggested to me that
Hi!
> I didn't know who to include as the wizards of the matter.
>
> > > If I, on the other hand, use Debian's kernel 2.6.22 or compile my own
> > > kernel with just the necessary parts for my work (version 2.6.23-rc3
> > > taken from kernel.org), then I can't make the machine sleep: when I
> >
On Mon, 2007-08-27 at 03:52 -0300, Rogério Brito wrote:
>
> I did 13 compiles with git bisect and some of them were unsucessfuly
> compiled, which I am afraid that may miss the real cause if I tag them as
> being "bad" (which I did).
Yes, don't mark such cases as bad or good but look for a nearby
Hallo!
I also have 800MHz iBook (2.2, 2 USB) and had the same problem with the
21.6.22 kernel a while ago and reverted back to 2.6.21. I'm not a kernel
guy but I think I remember from kernel traces that it looked like (wise
chosen words ;-)) that the problems had something to do with
deactiva
Hi, Thanks, Michal.
I didn't know who to include as the wizards of the matter.
On Aug 27 2007, Michal Piotrowski wrote:
> [Adding STR wizards to CC]
>
> On 26/08/07, Rogério Brito <[EMAIL PROTECTED]> wrote:
> > If I, on the other hand, use Debian's kernel 2.6.22 or compile my own
> > kernel with
Hi
[Adding STR wizards to CC]
On 26/08/07, Rogério Brito <[EMAIL PROTECTED]> wrote:
> Hi.
>
> Unfortunately, it seems that kernels later than 2.6.21 have problems
> letting my powerpc iBook (G3 processor) going to sleep (suspend to
> ram).
>
> The userland that I am using is a Debian testing (len
Hi.
Unfortunately, it seems that kernels later than 2.6.21 have problems
letting my powerpc iBook (G3 processor) going to sleep (suspend to
ram).
The userland that I am using is a Debian testing (lenny) and the
default kernel that comes with it is 2.6.22, with some patches applied
and pbbuttonsd
18 matches
Mail list logo
