From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
Date: Mon, 10 Feb 2014 16:34:38 +0000 [thread overview]
Message-ID: <bug-70171-2300-7bADIBpfUy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70171-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=70171
--- Comment #38 from Andreas <andreas.thalhammer@linux.com> ---
(In reply to Takashi Iwai from comment #34)
> For the tick-broadcast.c, try to bisect.
To summarize:
[SOLVED] sound issue
[SOLVED] overscan issue
[ ] kernel/time/tick-broadcast.c:668
The thing is: I don’t know how to bisect.
Question: I now run this kernel with this exception. At least I think it is an
exception. Nevertheless, the kernel runs stable. Which leads me to the
questions: Can I live with it? Do I really need to bother about it?
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-02-10 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-70171-2300@https.bugzilla.kernel.org/>
2014-02-10 9:24 ` [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound bugzilla-daemon
2014-02-10 15:31 ` bugzilla-daemon
2014-02-10 16:27 ` bugzilla-daemon
2014-02-10 16:31 ` bugzilla-daemon
2014-02-10 16:34 ` bugzilla-daemon [this message]
2014-02-10 17:02 ` bugzilla-daemon
2014-02-10 18:06 ` bugzilla-daemon
2014-02-11 15:52 ` bugzilla-daemon
2014-02-11 16:00 ` bugzilla-daemon
2014-02-11 18:36 ` bugzilla-daemon
2014-02-11 19:19 ` bugzilla-daemon
2014-02-11 19:28 ` bugzilla-daemon
2014-02-11 20:56 ` bugzilla-daemon
2014-02-20 18:50 ` bugzilla-daemon
2014-03-21 16:29 ` bugzilla-daemon
2014-03-21 16:30 ` [Bug 70171] 3.13.x: kernel/time/tick-broadcast.c:668 exception, no sound, HDMI overscan issue bugzilla-daemon
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=bug-70171-2300-7bADIBpfUy@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.