From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
Date: Tue, 11 Feb 2014 16:00:38 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from mail.kernel.org (mail.kernel.org [198.145.19.201])
by gabe.freedesktop.org (Postfix) with ESMTP id 326E9FA9E9
for ;
Tue, 11 Feb 2014 08:00:43 -0800 (PST)
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 23A70201FE
for ;
Tue, 11 Feb 2014 16:00:42 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org
[172.20.200.51])
by mail.kernel.org (Postfix) with ESMTP id 6CE0D20211
for ;
Tue, 11 Feb 2014 16:00:40 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces@lists.freedesktop.org
Errors-To: dri-devel-bounces@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugzilla.kernel.org/show_bug.cgi?id=70171
--- Comment #42 from Alex Deucher ---
Just google for "git bisect howto". There are lots of good examples. Here's
one: http://webchick.net/node/99
You need a kernel git tree. The closer you can narrow the breakage down, the
faster it will be. Basically, if you know that 3.12 was good and 3.13 was
broken, you'd start like this:
git bisect start
git bisect bad v3.13
git bisect good v3.12
Then build and test the kernel for each iteration until it arrives at the
problematic commit.
--
You are receiving this mail because:
You are watching the assignee of the bug.