mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Rechberger <mrechberger@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, Greg KH <greg@kroah.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-usb@vger.kernel.org, werner@guyane.dyn-o-saur.com,
	Marcus Meissner <meissner@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.33 bugs (USBFS, Intel graphic)
Date: Sat, 27 Feb 2010 23:33:07 +0100	[thread overview]
Message-ID: <d9def9db1002271433x4cd27afagcf5bc135be50ec22@mail.gmail.com> (raw)
In-Reply-To: <d9def9db1002271008j197d9a57md500c1ba44fc81c6@mail.gmail.com>

On Sat, Feb 27, 2010 at 7:08 PM, Markus Rechberger
<mrechberger@gmail.com> wrote:
> On Sat, Feb 27, 2010 at 5:49 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>> On Sat, 27 Feb 2010 14:17:14 +0200
>> Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>>
>>> On Sat, Feb 27, 2010 at 2:15 PM, Pekka Enberg
>>> <penberg@cs.helsinki.fi> wrote:
>>> > On Sat, Feb 27, 2010 at 1:00 PM, Markus Rechberger
>>> > <mrechberger@gmail.com> wrote:
>>> >>> Linus, I know you didn't want to do a kzalloc, but it looks like
>>> >>> this is the easiest/simplest thing to do, unless you can think of
>>> >>> something else?
>>> >>
>>> >> do you have any idea what to cherrypick in order to get rid of that
>>> >> flickering with the intel GM45?
>>> >> The flickering itself occures randomly, it was not there with the
>>> >> original Ubuntu kernel (2.6.31 with alot patches)
>>> >> This is pretty much a standard graphicchip nowadays....
>>> >
>>> > Yeah, same here. I tried to bisect the damn thing but didn't find
>>> > any single commit. I think the problem was introduced in in the DRM
>>> > merge between 2.6.31 and 2.6.32-rc1. Some people suggested
>>> > privately that it might be related to frame buffer compression.
>>> > Unfortunately I wasn't able to revert that particular patch.
>>>
>>> Btw, after I reinstalled Ubuntu 9.10 from scratch for unrelated
>>> reasons, I haven't seen the flicker effect. Dunno if that's just a
>>> coincidence or if userspace has something to do with the bug.
>>
>> Some people reported ACPI related flicker due to lid detection taking a
>> long time and X periodically probing for it.  Maybe that's what you
>> were seeing?
>>
>
> little bit offtopic there's another bug with the intel driver. Seems
> like there's a memory pool which collects all the memory during the
> runtime and especially makes the memory usage go up:
> http://bugs.freedesktop.org/show_bug.cgi?id=26708
> Maybe someone at Intel can have a closer look at that one...
>
> another obvious bug seems to be offloading mpeg2 video to the GPU it
> takes more CPU than decoding mpeg2 with software. Offloading is quite
> important nowadays due HDTV. The only one which has working linux
> support is NVidia with their closed source drivers.
>

Intel Graphic seems to be the pure chaos with Linux ....
I booted the old kernel again and did some debugging because the load
of udevd sometimes goes up.. the netlink interface seems to flood udev
with following message with ubuntu karmic 2.6.31
LINE: change@/devices/pci0000:00/0000:00:02.0/drm/card0
LINE: ACTION=change
LINE: DEVPATH=/devices/pci0000:00/0000:00:02.0/drm/card0
LINE: SUBSYSTEM=drm
LINE: HOTPLUG=1
LINE: MAJOR=226
LINE: MINOR=0
LINE: DEVNAME=dri/card0
LINE: DEVTYPE=drm_minor
LINE: SEQNUM=47819

obviosly this seems to be solved with the newer kernel, but there we
have that flickering issue and OpenGL support is messy

Aside of that some people sent me emails offlist that intel stopped
working correctly for them starting from 2.6.27 on. Is anyone from
Intel still working on the graphicdriver?

Some of our business customers are now switching to HDTV compatible
systems and Intel seems to be a nogo right now, NVidia Tegra seems to
have potential.

Markus

  reply	other threads:[~2010-02-27 22:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27  3:42 Markus Rechberger
2010-02-27  3:56 ` Greg KH
2010-02-27  4:05   ` Markus Rechberger
2010-02-27  4:18     ` Greg KH
2010-02-27  4:29       ` Linus Torvalds
2010-02-27  4:34         ` Markus Rechberger
2010-02-27  5:17           ` Greg KH
2010-02-27  5:26             ` Greg KH
2010-02-27  5:38               ` Markus Rechberger
2010-02-27  5:48                 ` Greg KH
2010-02-27 11:00                   ` Markus Rechberger
2010-02-27 12:15                     ` Pekka Enberg
2010-02-27 12:17                       ` Pekka Enberg
2010-02-27 16:49                         ` Jesse Barnes
2010-02-27 18:08                           ` Markus Rechberger
2010-02-27 22:33                             ` Markus Rechberger [this message]
2010-02-27 17:20             ` Alan Stern
2010-03-03  0:09               ` Greg KH
2010-03-05 21:37                 ` Markus Rechberger
2010-03-06 16:30                 ` Markus Rechberger
2010-03-06 17:06                   ` Greg KH
2010-03-06 20:04                     ` Alan Stern
2010-02-27  4:11 ` Linus Torvalds

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=d9def9db1002271433x4cd27afagcf5bc135be50ec22@mail.gmail.com \
    --to=mrechberger@gmail.com \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=meissner@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@linux-foundation.org \
    --cc=werner@guyane.dyn-o-saur.com \
    /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

all inboxes | Powered by JetHome®