From: Alexey Zaytsev <alexey.zaytsev@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Rodrigo Vivi <rodrigo.vivi@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@gmail.com>,
stable <stable@vger.kernel.org>
Subject: Re: Linux 3.8-rc2
Date: Fri, 4 Jan 2013 01:40:24 +0200 [thread overview]
Message-ID: <CAB9v_DE0qMdQ2poxv++FGd2zo+Tw5_m6kgTOoBZSCUOGZf+fNA@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFw5hnByqQHhsOYgc14DHTejHqmWV=fW2pm4LuzF6UxwCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Fri, Jan 4, 2013 at 1:18 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Jan 3, 2013 at 3:12 PM, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
>>
>> Chris: The patch does not seem to have any effect on the problem.
>>
>> Peter: I've attached the dmesgs, as well as the diff between the
>> interesting parts. The patch does not seem to make any difference
>> there.
>
> Alexey, what happens if you just avoid the divide-by-zero? There might
> be other complications downstream, but something like the attached
> patch should at least avoid doing the "divide-by-clock" when clock is
> zero..
>
> Linus
This one actually seems to work just fine. Dmesg attached.
[-- Attachment #2: dmesg-working-patched.gz --]
[-- Type: application/x-gzip, Size: 20456 bytes --]
next prev parent reply other threads:[~2013-01-03 23:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 3:36 Linus Torvalds
2013-01-03 21:09 ` Alexey Zaytsev
2013-01-03 21:32 ` Linus Torvalds
2013-01-03 22:06 ` Peter Ujfalusi
2013-01-03 22:45 ` Chris Wilson
2013-01-03 23:12 ` Alexey Zaytsev
2013-01-03 23:18 ` Linus Torvalds
2013-01-03 23:40 ` Alexey Zaytsev [this message]
2013-01-04 11:39 ` [PATCH] drm/i915: Treat crtc->mode.clock == 0 as disabled Chris Wilson
2013-01-04 14:58 ` Alexey Zaytsev
2013-01-06 20:56 ` Daniel Vetter
2013-01-07 10:11 ` Chris Wilson
2013-01-07 16:40 ` Daniel Vetter
2013-01-06 20:55 ` Linux 3.8-rc2 Daniel Vetter
2013-01-03 23:56 ` Shuah Khan
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=CAB9v_DE0qMdQ2poxv++FGd2zo+Tw5_m6kgTOoBZSCUOGZf+fNA@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=rodrigo.vivi@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®