On Fri, Aug 12, 2011 at 12:53:52PM -0700, Keith Packard wrote:
> Can you send me your kernel .config file? I'm still not having any luck
> reproducing your problems, using an X201s with the 1.22 BIOS version.
>
> I'm wondering if the trouble is caused by the the selection of kernel config
>
On Thu, 14 Jul 2011 19:00:26 +0200, Francesco Allertsen wrote:
> I have tried to boot with the latest git with the commit
> 05bd42688dbc066d4e2689b6f73c0470601f788b reverted (so I have the 'Idling
> fix' and the rc6 enabled), but I have the same freeze.
Can you send me your kernel .config file?
On Thu, Jul 14, 2011 at 09:06:20AM -0700, Keith Packard wrote:
> We mentioned the 'Idling' fix as it may make RC6 work. Have you tried
> that with RC6 enabled on the command line (or with
> 05bd42688dbc066d4e2689b6f73c0470601f788b not applied)? Obviously, not
> enabling RC6 by default will 'fix'
On Tue, 12 Jul 2011 10:33:06 +0300, Pekka Enberg wrote:
>> AFAICT, this problem is still there in 3.0-rc7. Keith, isn't it time
>> to revert commit a51f7a6 ("drm/i915: enable rc6 by default") before
>> 3.0 is out?
On Tue, Jul 12, 2011 at 6:42 PM, Keith Packard wrote:
> Yes. I'll put together a
On Thu, 14 Jul 2011 19:00:26 +0200, Francesco Allertsen wrote:
> I have tried to boot with the latest git with the commit
> 05bd42688dbc066d4e2689b6f73c0470601f788b reverted (so I have the 'Idling
> fix' and the rc6 enabled), but I have the same freeze.
Thanks.
--
keith.packard at intel.com
On Thu, Jul 14, 2011 at 10:37:15AM +0300, Pekka Enberg wrote:
> This if fixed in mainline as of commit
> a94919eaddaa3fede1df8563ce4d761a75374645 ("Revert "drm/i915: enable
> rc6 by default"). Keith, it would have been nice to include a
> 'Reported-by' and/or a link to this discussion in the
On Thu, 14 Jul 2011 09:50:07 +0200, Francesco Allertsen wrote:
> The correct commit is 05bd42688dbc066d4e2689b6f73c0470601f788b, the one
> you mentioned is "Idling requires waiting for the ring to be empty".
We mentioned the 'Idling' fix as it may make RC6 work. Have you tried
that with RC6
On Thu, 14 Jul 2011 10:37:15 +0300, Pekka Enberg wrote:
> This if fixed in mainline as of commit
> a94919eaddaa3fede1df8563ce4d761a75374645 ("Revert "drm/i915: enable
> rc6 by default"). Keith, it would have been nice to include a
> 'Reported-by' and/or a link to this discussion in the changelog
On Tue, 12 Jul 2011 10:33:06 +0300, Pekka Enberg penb...@kernel.org wrote:
AFAICT, this problem is still there in 3.0-rc7. Keith, isn't it time
to revert commit a51f7a6 (drm/i915: enable rc6 by default) before
3.0 is out?
On Tue, Jul 12, 2011 at 6:42 PM, Keith Packard kei...@keithp.com wrote:
On Thu, Jul 14, 2011 at 10:37:15AM +0300, Pekka Enberg wrote:
This if fixed in mainline as of commit
a94919eaddaa3fede1df8563ce4d761a75374645 (Revert drm/i915: enable
rc6 by default). Keith, it would have been nice to include a
'Reported-by' and/or a link to this discussion in the changelog
On Thu, 14 Jul 2011 09:50:07 +0200, Francesco Allertsen fallert...@gmail.com
wrote:
The correct commit is 05bd42688dbc066d4e2689b6f73c0470601f788b, the one
you mentioned is Idling requires waiting for the ring to be empty.
We mentioned the 'Idling' fix as it may make RC6 work. Have you tried
On Thu, 14 Jul 2011 10:37:15 +0300, Pekka Enberg penb...@kernel.org wrote:
This if fixed in mainline as of commit
a94919eaddaa3fede1df8563ce4d761a75374645 (Revert drm/i915: enable
rc6 by default). Keith, it would have been nice to include a
'Reported-by' and/or a link to this discussion in
On Thu, Jul 14, 2011 at 09:06:20AM -0700, Keith Packard wrote:
We mentioned the 'Idling' fix as it may make RC6 work. Have you tried
that with RC6 enabled on the command line (or with
05bd42688dbc066d4e2689b6f73c0470601f788b not applied)? Obviously, not
enabling RC6 by default will 'fix'
On Thu, 14 Jul 2011 19:00:26 +0200, Francesco Allertsen fallert...@gmail.com
wrote:
I have tried to boot with the latest git with the commit
05bd42688dbc066d4e2689b6f73c0470601f788b reverted (so I have the 'Idling
fix' and the rc6 enabled), but I have the same freeze.
Thanks.
--
On Wed, Jul 6, 2011 at 2:01 AM, Francesco Allertsen
wrote:
> On Tue, Jun 21, 2011 at 12:01:34PM -0700, Keith Packard wrote:
>> Thanks. I'll see if I can't get an X201s upgraded to this version and
>> see if we can reproduce the problem you're having...
>
> Any news?
>
> I have found the time
On Wed, Jul 06, 2011 at 01:01:01AM +0200, Francesco Allertsen wrote:
> Any news?
Ping. Another -rc is out and I still cannot use this new kernel.
Bye
Francesco
On Tue, 12 Jul 2011 10:33:06 +0300, Pekka Enberg wrote:
> AFAICT, this problem is still there in 3.0-rc7. Keith, isn't it time
> to revert commit a51f7a6 ("drm/i915: enable rc6 by default") before
> 3.0 is out?
Yes. I'll put together a few tiny patches including this.
--
keith.packard at
On Tue, 12 Jul 2011 10:33:06 +0300, Pekka Enberg penb...@kernel.org wrote:
AFAICT, this problem is still there in 3.0-rc7. Keith, isn't it time
to revert commit a51f7a6 (drm/i915: enable rc6 by default) before
3.0 is out?
Yes. I'll put together a few tiny patches including this.
--
On Tue, Jun 21, 2011 at 12:01:34PM -0700, Keith Packard wrote:
> Thanks. I'll see if I can't get an X201s upgraded to this version and
> see if we can reproduce the problem you're having...
Any news?
I have found the time today for more debugging.
Attached there are 3 files.
dmesg-startup is
On Tue, Jun 21, 2011 at 09:12:48PM +0200, Marcin Slusarz wrote:
> Try to run dmesg -n 8 before loading the module.
I'm using the netconsole directly at the boot, because I got the freeze,
so I don't know how to pass that value directly appended to the kernel
(if it's possibile).
If you want I
On Tue, Jun 21, 2011 at 09:12:48PM +0200, Marcin Slusarz wrote:
Try to run dmesg -n 8 before loading the module.
I'm using the netconsole directly at the boot, because I got the freeze,
so I don't know how to pass that value directly appended to the kernel
(if it's possibile).
If you want I can
On Tue, Jun 21, 2011 at 08:48:55PM +0200, Francesco Allertsen wrote:
> On Tue, Jun 21, 2011 at 11:29:41AM -0700, Jesse Barnes wrote:
> > Use netconsole. Documentation/networking/netconsole.txt has all the
> > gory details.
>
> I have used netconsole, with that documentation, but it doesn't show
On Tue, Jun 21, 2011 at 11:29:41AM -0700, Jesse Barnes wrote:
> Use netconsole. Documentation/networking/netconsole.txt has all the
> gory details.
I have used netconsole, with that documentation, but it doesn't show me
the drm debug messages, only the other dmesg messages, and I don't know
why.
On Tue, Jun 21, 2011 at 11:04:15AM -0700, Keith Packard wrote:
> Btw, can you send along the output of dmidecode? I'm wondering what
> version of the BIOS you've got. We've seen some pretty strange behaviour
> on X201s with earlier BIOS versions which have been fixed with newer
> versions.
Here
On Tue, Jun 21, 2011 at 09:11:29AM -0700, Keith Packard wrote:
> I'm more interested in seeing how the dmesg output differs between the
> working state (rc6=0) and the broken state (rc6=1). Or is the machine
> not accessible over ssh once you've started X?
I got a complete freeze when I start X.
On Tue, Jun 21, 2011 at 08:28:17AM -0700, Keith Packard wrote:
> Given the number of X201s machines running this kernel (like the one I'm
> using right now), I'd love to get this fixed for you instead of
> disabling rc6 -- rc6 is worth a ton of power savings.
I didn't know that, anyway, I'm don't
Hi, I wanted to try the new 3.0 Linux Kernel, and I got stucked for a
freeze at the start of X.
I have bisected the problem and the error was on commit a51f7a6, wich
enable rc6 by default (some time ago I have sent another bug about
that).
I have reverted the commit (the complete patch is
On Tue, 21 Jun 2011 20:47:57 +0200, Francesco Allertsen wrote:
> Version: 6QET52WW (1.22 )
> Release Date: 08/23/2010
Thanks. I'll see if I can't get an X201s upgraded to this version and
see if we can reproduce the problem you're having...
--
keith.packard at intel.com
On Tue, 21 Jun 2011 11:04:15 -0700
Keith Packard wrote:
> On Tue, 21 Jun 2011 18:42:09 +0200, Francesco Allertsen gmail.com> wrote:
> > On Tue, Jun 21, 2011 at 09:11:29AM -0700, Keith Packard wrote:
> > > I'm more interested in seeing how the dmesg output differs between the
> > > working state
On Tue, 21 Jun 2011 18:42:09 +0200, Francesco Allertsen wrote:
> On Tue, Jun 21, 2011 at 09:11:29AM -0700, Keith Packard wrote:
> > I'm more interested in seeing how the dmesg output differs between the
> > working state (rc6=0) and the broken state (rc6=1). Or is the machine
> > not accessible
On Tue, 21 Jun 2011 17:52:05 +0200, Francesco Allertsen wrote:
> If you prefer that I open a bug on the kernel bugzilla to put all the
> informations no problem.
I'm more interested in seeing how the dmesg output differs between the
working state (rc6=0) and the broken state (rc6=1). Or is the
On Tue, 21 Jun 2011 16:21:33 +0200, Francesco Allertsen wrote:
Non-text part: multipart/mixed
> Now, I have a Lenovo X201s, and if you need more information for
> debugging purpose just let me know, otherwise just apply the patch
> attached (on top of -rc4).
Given the number of X201s machines
Hi, I wanted to try the new 3.0 Linux Kernel, and I got stucked for a
freeze at the start of X.
I have bisected the problem and the error was on commit a51f7a6, wich
enable rc6 by default (some time ago I have sent another bug about
that).
I have reverted the commit (the complete patch is
On Tue, 21 Jun 2011 16:21:33 +0200, Francesco Allertsen fallert...@gmail.com
wrote:
Non-text part: multipart/mixed
Now, I have a Lenovo X201s, and if you need more information for
debugging purpose just let me know, otherwise just apply the patch
attached (on top of -rc4).
Given the number
On Tue, 21 Jun 2011 17:52:05 +0200, Francesco Allertsen fallert...@gmail.com
wrote:
If you prefer that I open a bug on the kernel bugzilla to put all the
informations no problem.
I'm more interested in seeing how the dmesg output differs between the
working state (rc6=0) and the broken state
On Tue, Jun 21, 2011 at 09:11:29AM -0700, Keith Packard wrote:
I'm more interested in seeing how the dmesg output differs between the
working state (rc6=0) and the broken state (rc6=1). Or is the machine
not accessible over ssh once you've started X?
I got a complete freeze when I start X. I
On Tue, 21 Jun 2011 18:42:09 +0200, Francesco Allertsen fallert...@gmail.com
wrote:
On Tue, Jun 21, 2011 at 09:11:29AM -0700, Keith Packard wrote:
I'm more interested in seeing how the dmesg output differs between the
working state (rc6=0) and the broken state (rc6=1). Or is the machine
On Tue, 21 Jun 2011 11:04:15 -0700
Keith Packard kei...@keithp.com wrote:
On Tue, 21 Jun 2011 18:42:09 +0200, Francesco Allertsen
fallert...@gmail.com wrote:
On Tue, Jun 21, 2011 at 09:11:29AM -0700, Keith Packard wrote:
I'm more interested in seeing how the dmesg output differs between
On Tue, Jun 21, 2011 at 11:04:15AM -0700, Keith Packard wrote:
Btw, can you send along the output of dmidecode? I'm wondering what
version of the BIOS you've got. We've seen some pretty strange behaviour
on X201s with earlier BIOS versions which have been fixed with newer
versions.
Here is
On Tue, Jun 21, 2011 at 11:29:41AM -0700, Jesse Barnes wrote:
Use netconsole. Documentation/networking/netconsole.txt has all the
gory details.
I have used netconsole, with that documentation, but it doesn't show me
the drm debug messages, only the other dmesg messages, and I don't know
why.
On Tue, 21 Jun 2011 20:47:57 +0200, Francesco Allertsen fallert...@gmail.com
wrote:
Version: 6QET52WW (1.22 )
Release Date: 08/23/2010
Thanks. I'll see if I can't get an X201s upgraded to this version and
see if we can reproduce the problem you're having...
--
On Tue, Jun 21, 2011 at 08:48:55PM +0200, Francesco Allertsen wrote:
On Tue, Jun 21, 2011 at 11:29:41AM -0700, Jesse Barnes wrote:
Use netconsole. Documentation/networking/netconsole.txt has all the
gory details.
I have used netconsole, with that documentation, but it doesn't show me
the
42 matches
Mail list logo
