> 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():
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
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
> an
11 matches
Mail list logo
