dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 11 Feb 2014 19:19:50 +0000	[thread overview]
Message-ID: <bug-70171-2300-VN6LWR8oUM@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 #44 from Andreas <andreas.thalhammer@linux.com> ---
git log --oneline v3.12..v3.13 kernel/time/

7a06c41 sched_clock: Disable seqlock lockdep usage in sched_clock()
0e576ac nohz: Fix another inconsistency between CONFIG_NO_HZ=n and nohz=off
4be7739 time: Fix 1ns/tick drift w/ GENERIC_TIME_VSYSCALL_OLD
050ded1 tick: Document tick_do_timer_cpu
d689fe2 NOHZ: Check for nohz active instead of nohz enabled
8709382 Merge branch 'timers-core-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
891292a time: Fix signedness bug in sysfs_get_uname() and its callers
b7bc50e timekeeping: Fix some trivial typos in comments
98d6f4d alarmtimer: return EINVAL instead of ENOTSUPP if rtcdev doesn't exist
2cb7636 timer stats: Add a 'Collection: active/inactive' line to timer usage
statistics
8a749de Merge branch 'fortglx/3.13/time' of
git://git.linaro.org/people/jstultz/linux into timers/core
b4042ce sched_clock: Remove sched_clock_func() hook
68e9074 Merge branch 'clockevents/3.13' of
git://git.linaro.org/people/dlezcano/linux into timers/core
19f2988 Merge branch 'timers/core' of
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks into
timers/core
6c09f6d Merge tag 'v3.12-rc3' into timers/core
245a349 tick: broadcast: Deny per-cpu clockevents from being broadcast sources
ff3fb25 nohz: Drop generic vtime obsolete dependency on CONFIG_64BIT
554b000 vtime: Add HAVE_VIRT_CPU_ACCOUNTING_GEN Kconfig
233bcb4 clocksource: Fix 'ret' data type of sysfs_override_clocksource() and
sysfs_unbind_clocksource()
389e067 Merge branch 'fortglx/3.12/time' into fortglx/3.13/time
19c3205 Merge branch 'fortglx/3.12/sched-clock64-base' into fortglx/3.13/time
a97ad0c ntp: Make periodic RTC update more reliable
e7e3ff1 sched_clock: Add support for >32 bit sched_clock
a08ca5d sched_clock: Use an hrtimer instead of timer
85c3d2d sched_clock: Use seqcount instead of rolling our own
87d8b9e clocksource: Extract max nsec calculation into separate function
397bbf6 clocksource: Fix !CONFIG_CLOCKSOURCE_WATCHDOG compile


I only which I knew what to do with it. Right now I’m still trying to find out
how to actually compile the selected "bisect" kernel...

-- 
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

  parent reply	other threads:[~2014-02-11 19:19 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
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 [this message]
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-VN6LWR8oUM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox