All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
@ 2014-02-10  9:24 ` bugzilla-daemon
  2014-02-10 15:31 ` bugzilla-daemon
                   ` (14 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-10  9:24 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

Takashi Iwai <tiwai@suse.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Sound(ALSA)                 |Video(DRI - non Intel)
           Assignee|perex@perex.cz              |drivers_video-dri@kernel-bu
                   |                            |gs.osdl.org

--- Comment #34 from Takashi Iwai <tiwai@suse.de> ---
OK, then I reassign to DRM.

For the tick-broadcast.c, try to bisect.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [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
                   ` (13 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-10 15:31 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com

--- Comment #35 from Alex Deucher <alexdeucher@gmail.com> ---
It looks like your monitor may be enabling overscan.  A lot of TVs enable this
automatically for hdmi.  See if you can disable it in your monitor's controls. 
You can disable hdmi packet generation in the radeon driver by appending
radeon.audio=0 to the kernel command line in grub.  If disabling audio in
radeon helps, then it's most likely your monitor enabling the overscan upon
detection of hdmi packets from the source device.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [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
                   ` (12 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-10 16:27 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #36 from Andreas <andreas.thalhammer@linux.com> ---
(In reply to Alex Deucher from comment #35)
> appending radeon.audio=0 to the kernel command line in grub.

Thanks!

Actually I have to apologize for my incompetence. With the new radeon driver
from 3.13+ my monitor did two things after initialization of X:
1) it automatically selected overscan (an option I did not see before)
2) it selected "Video Mode" (= HDMI) as audio source

The solution therefore is to add radeon.audio=0. With it I don’t even get the
overscan option on the monitor and audio defaults to "PC Mode" as intended.
(This restores the old behaviour I am used to up to kernel 3.12.)

Again, thanks!

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (2 preceding siblings ...)
  2014-02-10 16:27 ` bugzilla-daemon
@ 2014-02-10 16:31 ` bugzilla-daemon
  2014-02-10 16:34 ` bugzilla-daemon
                   ` (11 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-10 16:31 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #37 from Andreas <andreas.thalhammer@linux.com> ---
One more info with "nice to know" character:

Without radeon.audio=0 I also no longer see the color settings menu from the
monitor – it is grayed out. Seems that this is covered by the radeon driver and
the HDMI standard somehow?

Anyway, now with radeon.audio=0 I see the following possible color settings:
* sRGB
* 6500 K
* 7500 K
* 9300 K
* native
* user defined

I selected sRGB.
It would be interesting to know what is used when it is grayed out (without the
radeon.audio=0 option)...

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (3 preceding siblings ...)
  2014-02-10 16:31 ` bugzilla-daemon
@ 2014-02-10 16:34 ` bugzilla-daemon
  2014-02-10 17:02 ` bugzilla-daemon
                   ` (10 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-10 16:34 UTC (permalink / raw)
  To: dri-devel

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (4 preceding siblings ...)
  2014-02-10 16:34 ` bugzilla-daemon
@ 2014-02-10 17:02 ` bugzilla-daemon
  2014-02-10 18:06 ` bugzilla-daemon
                   ` (9 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-10 17:02 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #39 from Alex Deucher <alexdeucher@gmail.com> ---
In addition to the module parameter, you can adjust audio support at runtime
per connector with xrandr, e.g.,

xrandr --output HDMI-0 --set audio off
or
xrandr --output HDMI-0 --set audio auto

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (5 preceding siblings ...)
  2014-02-10 17:02 ` bugzilla-daemon
@ 2014-02-10 18:06 ` bugzilla-daemon
  2014-02-11 15:52 ` bugzilla-daemon
                   ` (8 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-10 18:06 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #40 from Andreas <andreas.thalhammer@linux.com> ---
(In reply to Alex Deucher from comment #39)
> In addition to the module parameter, you can adjust audio support at runtime
> per connector with xrandr, e.g.,

Thanks, I’ll try it on the next reboot. I tried it now but (most likely) due to
the module parameter I get an error:

$ xrandr --output HDMI-0 --set audio auto
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  139 (RANDR)
  Minor opcode of failed request:  11 (RRQueryOutputProperty)
  Serial number of failed request:  41
  Current serial number in output stream:  41


Anyway, I’m thinking if I did use xrandr to later on disable audio it will most
likely be too late, as the monitor will already be set to the wrong audio
source and possibly overscan will remain selected.

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (6 preceding siblings ...)
  2014-02-10 18:06 ` bugzilla-daemon
@ 2014-02-11 15:52 ` bugzilla-daemon
  2014-02-11 16:00 ` bugzilla-daemon
                   ` (7 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-11 15:52 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #41 from Andreas <andreas.thalhammer@linux.com> ---
I would not have believed it, but the xrandr option also works. Running

$ xrandr --output HDMI-0 --set audio off

actually resets the screen and everything is as it should be: Audio is
automatically switch from "Video Mode" to "PC Mode" and the color settings menu
gets accessible while overscan is off and disappears from the menu.

Thanks!

Which leaves only the tick-broadcast.c issue. I searched for bisect but I’m not
sure how to use this successfully. Also, I’m not a git expert. I take it I
should try to find the first commit that introduced this issue. Where do I
start? At the rc state of 3.13?

Is there a link to a good howto you can point me to? And a hint on how and
where to start?

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (7 preceding siblings ...)
  2014-02-11 15:52 ` bugzilla-daemon
@ 2014-02-11 16:00 ` bugzilla-daemon
  2014-02-11 18:36 ` bugzilla-daemon
                   ` (6 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-11 16:00 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #42 from Alex Deucher <alexdeucher@gmail.com> ---
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.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (8 preceding siblings ...)
  2014-02-11 16:00 ` bugzilla-daemon
@ 2014-02-11 18:36 ` bugzilla-daemon
  2014-02-11 19:19 ` bugzilla-daemon
                   ` (5 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-11 18:36 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #43 from Andreas <andreas.thalhammer@linux.com> ---
Should I git clone
1) git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
2) git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

I don’t really understand how to get kernel 3.13 and 3.12 and the commits in
between...

E.g. I found this:
http://www.project-insanity.org/blog/2013/02/13/how-i-found-a-kernel-regression-using-git-bisect/

But how will I find out commits like 49b8c695e331c9685e6ffdbf34872509d77c8459?

Anyway I git clone the linux-stable source now and I will use the bisect as you
suggested. And I understand I will have to reboot my system quite a lot...

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (9 preceding siblings ...)
  2014-02-11 18:36 ` bugzilla-daemon
@ 2014-02-11 19:19 ` bugzilla-daemon
  2014-02-11 19:28 ` bugzilla-daemon
                   ` (4 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-11 19:19 UTC (permalink / raw)
  To: dri-devel

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (10 preceding siblings ...)
  2014-02-11 19:19 ` bugzilla-daemon
@ 2014-02-11 19:28 ` bugzilla-daemon
  2014-02-11 20:56 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-11 19:28 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #45 from Andreas <andreas.thalhammer@linux.com> ---
Got it, working on it... Will report the result in a couple of days...

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (11 preceding siblings ...)
  2014-02-11 19:28 ` bugzilla-daemon
@ 2014-02-11 20:56 ` bugzilla-daemon
  2014-02-20 18:50 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-11 20:56 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #46 from Alan <alan@lxorguk.ukuu.org.uk> ---
(and the timer bug is unrelated but fix posted to lkml by Thomas Gleixner
WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:668
tick_broadcast_oneshot_control+0x17d/0x190())

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (12 preceding siblings ...)
  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
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-02-20 18:50 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

--- Comment #47 from Andreas <andreas.thalhammer@linux.com> ---
Hello again.

I’m sorry, but I won’t make it soon. I’ve got a lot of work to do right now and
since most issues are solved I can use my computer for now.

I will do the bisect, but it will take some more time. Weeks maybe. I won’t
forget it thou and hopefully I will be able to identify the commit before 3.14
is out.

Sorry for the delay.

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] kernel/time/tick-broadcast.c:668 exception and no sound
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (13 preceding siblings ...)
  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
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-03-21 16:29 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

Andreas <andreas.thalhammer@linux.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |OBSOLETE

--- Comment #48 from Andreas <andreas.thalhammer@linux.com> ---
Okay, I appologize, but I’ve been _very_ busy since my last message. I just
installed kernels 3.12.14 an 3.13.6 and I am now running on 3.13.6:

1) the kernel/time/tick-broadcast.c:668 error message is gone.
2) sound works, because I switched from the gray to the green Line Out jack as
proposed by Raymond in comment #15 – otherwise sound was still muted.

To summerize:
[SOLVED] sound issue
   +------- green jack on 3.13.x
   +------- gray/green jack on 3.12.x/earlier and 3.14-rc1/later
[SOLVED] overscan issue
   +------- disable audio for HDMI output
[SOLVED] kernel/time/tick-broadcast.c:668
   +------- gone in 3.13.6, not present in 3.12.x, unknown for 3.14-rc


Thanks for all your help!

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug 70171] 3.13.x: kernel/time/tick-broadcast.c:668 exception, no sound, HDMI overscan issue
       [not found] <bug-70171-2300@https.bugzilla.kernel.org/>
                   ` (14 preceding siblings ...)
  2014-03-21 16:29 ` bugzilla-daemon
@ 2014-03-21 16:30 ` bugzilla-daemon
  15 siblings, 0 replies; 16+ messages in thread
From: bugzilla-daemon @ 2014-03-21 16:30 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=70171

Andreas <andreas.thalhammer@linux.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|kernel/time/tick-broadcast. |3.13.x:
                   |c:668 exception and no      |kernel/time/tick-broadcast.
                   |sound                       |c:668 exception, no sound,
                   |                            |HDMI overscan issue

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2014-03-21 16:30 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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
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

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.