On Thu, Dec 13, 2018 at 02:24:14PM +0200, Mathias Nyman wrote:
> On 13.12.2018 09:36, Greg Kroah-Hartman wrote:
> > On Wed, Dec 12, 2018 at 11:53:34PM +0100, Thomas Zeitlhofer wrote:
> > > Hello,
> > >
> > > On Thu, Nov 29, 2018 at 03:11:45PM +0100, Greg Kroa
Hello Hui,
On Thu, Dec 13, 2018 at 08:23:40AM +0800, Hui Wang wrote:
> Hello Thomas,
>
> I have sent a new patch to fix this LED regression, after applying
> this patch (ALSA: hda/realtek - fix the pop noise on headphone for
> lenovo laptops) and the new patch (ALSA: hda/realtek - Fix the mute
>
Hello,
On Tue, Dec 04, 2018 at 11:49:37AM +0100, Greg Kroah-Hartman wrote:
> 4.19-stable review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Hui Wang
>
> commit c4cfcf6f4297c9256b53790bacbbbd6901fef468 upstream.
>
> We have several Lenovo
Hello,
On Thu, Nov 29, 2018 at 03:11:45PM +0100, Greg Kroah-Hartman wrote:
> 4.19-stable review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Mathias Nyman
>
> commit 2f31a67f01a8beb22cae754c53522cb61a005750 upstream.
[...]
on a current Thinkpad
On Sun, Jan 07, 2018 at 09:53:19AM +0100, Thomas Zeitlhofer wrote:
> On Sun, Jan 07, 2018 at 09:17:18AM +0100, Greg Kroah-Hartman wrote:
> > On Sat, Jan 06, 2018 at 10:38:38PM +0100, Thomas Zeitlhofer wrote:
[...]
> > > While solving the previous problem, this patch also introdu
On Sun, Jan 07, 2018 at 09:53:19AM +0100, Thomas Zeitlhofer wrote:
> On Sun, Jan 07, 2018 at 09:17:18AM +0100, Greg Kroah-Hartman wrote:
> > On Sat, Jan 06, 2018 at 10:38:38PM +0100, Thomas Zeitlhofer wrote:
[...]
> > > While solving the previous problem, this patch also introdu
On Sun, Jan 07, 2018 at 09:17:18AM +0100, Greg Kroah-Hartman wrote:
> On Sat, Jan 06, 2018 at 10:38:38PM +0100, Thomas Zeitlhofer wrote:
> > On Thu, Jan 04, 2018 at 07:38:00PM +0100, Thomas Zeitlhofer wrote:
> > > On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
&
On Sun, Jan 07, 2018 at 09:17:18AM +0100, Greg Kroah-Hartman wrote:
> On Sat, Jan 06, 2018 at 10:38:38PM +0100, Thomas Zeitlhofer wrote:
> > On Thu, Jan 04, 2018 at 07:38:00PM +0100, Thomas Zeitlhofer wrote:
> > > On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
&
On Thu, Jan 04, 2018 at 07:38:00PM +0100, Thomas Zeitlhofer wrote:
> On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
> > On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > > > Yes:
> > > >
> > > >BUG: using smp_
On Thu, Jan 04, 2018 at 07:38:00PM +0100, Thomas Zeitlhofer wrote:
> On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
> > On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > > > Yes:
> > > >
> > > >BUG: using smp_
On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
> On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > > Yes:
> > >
> > >BUG: using smp_processor_id() in preemptible [] code:
> > > ovsdb-server/4498
> > >caller is native_flush_tlb_single+0x57/0xc0
On Thu, Jan 04, 2018 at 06:07:12PM +0100, Peter Zijlstra wrote:
> On Thu, Jan 04, 2018 at 04:37:24PM +0100, Thomas Gleixner wrote:
> > > Yes:
> > >
> > >BUG: using smp_processor_id() in preemptible [] code:
> > > ovsdb-server/4498
> > >caller is native_flush_tlb_single+0x57/0xc0
On Thu, Jan 04, 2018 at 01:55:28PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 04, 2018 at 01:43:20PM +0100, Thomas Zeitlhofer wrote:
> > On Thu, Jan 04, 2018 at 11:51:11AM +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Jan 04, 2018 at 11:20:29AM +0100, Thomas Zeitlhofer wro
On Thu, Jan 04, 2018 at 01:55:28PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 04, 2018 at 01:43:20PM +0100, Thomas Zeitlhofer wrote:
> > On Thu, Jan 04, 2018 at 11:51:11AM +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Jan 04, 2018 at 11:20:29AM +0100, Thomas Zeitlhofer wro
On Thu, Jan 04, 2018 at 11:51:11AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 04, 2018 at 11:20:29AM +0100, Thomas Zeitlhofer wrote:
> > On Thu, Jan 04, 2018 at 02:59:06AM +0100, Thomas Zeitlhofer wrote:
> > > Hello,
> > >
> > > on an Ivybridge CPU, I g
On Thu, Jan 04, 2018 at 11:51:11AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 04, 2018 at 11:20:29AM +0100, Thomas Zeitlhofer wrote:
> > On Thu, Jan 04, 2018 at 02:59:06AM +0100, Thomas Zeitlhofer wrote:
> > > Hello,
> > >
> > > on an Ivybridge CPU, I g
On Thu, Jan 04, 2018 at 02:59:06AM +0100, Thomas Zeitlhofer wrote:
> Hello,
>
> on an Ivybridge CPU, I get with 4.14.11:
>
>BUG: using smp_processor_id() in preemptible [] code:
> ovsdb-server/4510
>caller is native_flush_tlb_single+0x57/0xc0
>CPU:
On Thu, Jan 04, 2018 at 02:59:06AM +0100, Thomas Zeitlhofer wrote:
> Hello,
>
> on an Ivybridge CPU, I get with 4.14.11:
>
>BUG: using smp_processor_id() in preemptible [] code:
> ovsdb-server/4510
>caller is native_flush_tlb_single+0x57/0xc0
>CPU:
Hello,
on an Ivybridge CPU, I get with 4.14.11:
BUG: using smp_processor_id() in preemptible [] code:
ovsdb-server/4510
caller is native_flush_tlb_single+0x57/0xc0
CPU: 3 PID: 4510 Comm: ovsdb-server Not tainted
4.14.11-kvm-00434-gcd0b8eb84f5c #3
Hardware name: MSI
Hello,
on an Ivybridge CPU, I get with 4.14.11:
BUG: using smp_processor_id() in preemptible [] code:
ovsdb-server/4510
caller is native_flush_tlb_single+0x57/0xc0
CPU: 3 PID: 4510 Comm: ovsdb-server Not tainted
4.14.11-kvm-00434-gcd0b8eb84f5c #3
Hardware name: MSI
On Fri, Jul 05, 2013 at 11:43:30AM +0800, Jason Wang wrote:
> On 07/03/2013 02:11 PM, Thomas Zeitlhofer wrote:
> > Hello Jason,
> >
> > On Wed, Jul 03, 2013 at 10:44:32AM +0800, Jason Wang wrote:
[...]
> >> Which regression did you see?
> > a kernel pa
On Fri, Jul 05, 2013 at 11:43:30AM +0800, Jason Wang wrote:
On 07/03/2013 02:11 PM, Thomas Zeitlhofer wrote:
Hello Jason,
On Wed, Jul 03, 2013 at 10:44:32AM +0800, Jason Wang wrote:
[...]
Which regression did you see?
a kernel panic on the host machine. The details are in the first
Hello Jason,
On Wed, Jul 03, 2013 at 10:44:32AM +0800, Jason Wang wrote:
> On 07/03/2013 06:06 AM, Thomas Zeitlhofer wrote:
> > On Tue, Jul 02, 2013 at 06:01:12PM -0300, Fabio Estevam wrote:
> >> On Tue, Jul 2, 2013 at 4:59 PM, Thomas Zeitlhofer
> >> wrote
Hello Jason,
On Wed, Jul 03, 2013 at 10:44:32AM +0800, Jason Wang wrote:
On 07/03/2013 06:06 AM, Thomas Zeitlhofer wrote:
On Tue, Jul 02, 2013 at 06:01:12PM -0300, Fabio Estevam wrote:
On Tue, Jul 2, 2013 at 4:59 PM, Thomas Zeitlhofer
thomas.zeitlho...@nt.tuwien.ac.at wrote:
Commit
On Tue, Jul 02, 2013 at 06:01:12PM -0300, Fabio Estevam wrote:
> On Tue, Jul 2, 2013 at 4:59 PM, Thomas Zeitlhofer
> wrote:
> > Commit "tuntap: set SOCK_ZEROCOPY flag during open" introduces a
> > regression which is observed with live migration of qemu/kv
Commit "tuntap: set SOCK_ZEROCOPY flag during open" introduces a
regression which is observed with live migration of qemu/kvm based
virtual machines that are connected to an openvswitch bridge.
Reverting this commit (b26c93c46a3dec25ed236d4ba6107eb4ed5d9401 in
v3.9.8 and accordingly
Commit tuntap: set SOCK_ZEROCOPY flag during open introduces a
regression which is observed with live migration of qemu/kvm based
virtual machines that are connected to an openvswitch bridge.
Reverting this commit (b26c93c46a3dec25ed236d4ba6107eb4ed5d9401 in
v3.9.8 and accordingly
On Tue, Jul 02, 2013 at 06:01:12PM -0300, Fabio Estevam wrote:
On Tue, Jul 2, 2013 at 4:59 PM, Thomas Zeitlhofer
thomas.zeitlho...@nt.tuwien.ac.at wrote:
Commit tuntap: set SOCK_ZEROCOPY flag during open introduces a
regression which is observed with live migration of qemu/kvm based
29 matches
Mail list logo
