On Sat, 20 Jul 2019, Heiner Kallweit wrote:
On 19.07.2019 23:12, Thomas Voegtle wrote:
On Fri, 19 Jul 2019, Heiner Kallweit wrote:
On 18.07.2019 20:50, Thomas Voegtle wrote:
Hello,
I'm having network problems with the commits on r8169 since v5.2. There are
ping packet loss, sometime
On Fri, 19 Jul 2019, Heiner Kallweit wrote:
On 18.07.2019 20:50, Thomas Voegtle wrote:
Hello,
I'm having network problems with the commits on r8169 since v5.2. There are
ping packet loss, sometimes 100%, sometimes 50%. In the end network is unusable.
v5.2 is fine, I bisected it do
Hello,
I'm having network problems with the commits on r8169 since v5.2. There
are ping packet loss, sometimes 100%, sometimes 50%. In the end network is
unusable.
v5.2 is fine, I bisected it down to:
a2928d28643e3c064ff41397281d20c445525032 is the first bad commit
commit a2928d28643e3c064
On Fri, 23 Nov 2018, Greg Kroah-Hartman wrote:
On Thu, Nov 22, 2018 at 09:53:35PM +0100, Thomas Voegtle wrote:
Doesn't compile for me on OpenSuSE 15.0 (gcc 7.3.1):
CALLscripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
CC [M] drivers/gpu/drm
On Thu, 22 Nov 2018, Thomas Voegtle wrote:
Doesn't compile for me on OpenSuSE 15.0 (gcc 7.3.1):
CALLscripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
CC [M] drivers/gpu/drm/i915/i915_gem_gtt.o
drivers/gpu/drm/i915/i915_gem_gtt.c: In fun
On Tue, 28 Aug 2018, Thomas Gleixner wrote:
On Tue, 28 Aug 2018, Thomas Voegtle wrote:
Kernel 4.18.5 with old microcode:
[0.00] microcode: microcode updated early to revision 0x2c, date =
2017-03-25
cat /sys/devices/system/cpu/vulnerabilities/meltdown
Mitigation: PTI
Kernel 4.18.5
Hello,
Kernel 4.18.5 with old microcode:
[0.00] microcode: microcode updated early to revision 0x2c, date =
2017-03-25
cat /sys/devices/system/cpu/vulnerabilities/meltdown
Mitigation: PTI
Kernel 4.18.5 with new microcode (microcode-20180807.tgz), same config:
[0.00] microcod
On Wed, 23 May 2018, Ben Hutchings wrote:
On Mon, 2018-05-21 at 17:54 -0400, Konrad Rzeszutek Wilk wrote:
The X86_FEATURE_SSBD is an synthetic CPU feature - that is
it bit location has no relevance to the real CPUID 0x7.EBX[31]
bit position. For that we need the new CPU feature name.
Fixes: 52
On Thu, 15 Feb 2018, Greg KH wrote:
On Thu, Feb 15, 2018 at 11:15:41AM +0100, Thomas Voegtle wrote:
Hello,
On Tue, 6 Feb 2018, David Woodhouse wrote:
I've put together a linux-4.9.y branch at
http://git.infradead.org/retpoline-stable.git/shortlog/refs/heads/linux-4.9.y
Are ther
Hello,
On Tue, 6 Feb 2018, David Woodhouse wrote:
I've put together a linux-4.9.y branch at
http://git.infradead.org/retpoline-stable.git/shortlog/refs/heads/linux-4.9.y
Are there any plans for a backport to v4.4?
I would volunteer for testing ;)
Thomas
On Fri, 5 Jan 2018, Greg Kroah-Hartman wrote:
On Thu, Jan 04, 2018 at 08:38:23PM +0100, Thomas Voegtle wrote:
When I start 4.4.110-rc1 on a virtual machine (qemu) init throws a
segfault and the kernel panics (attempted to kill init).
The VM host is a Haswell system.
The same kernel binary
On Thu, 4 Jan 2018, Greg Kroah-Hartman wrote:
On Thu, Jan 04, 2018 at 08:38:23PM +0100, Thomas Voegtle wrote:
When I start 4.4.110-rc1 on a virtual machine (qemu) init throws a
segfault and the kernel panics (attempted to kill init).
The VM host is a Haswell system.
The same kernel binary
When I start 4.4.110-rc1 on a virtual machine (qemu) init throws a
segfault and the kernel panics (attempted to kill init).
The VM host is a Haswell system.
The same kernel binary boots fine on a (other) Haswell system.
I tried:
4.4.110-rc1 broken
4.4.109 ok
4.9.75-rc1 ok
All
te Cc: list for regression fixes.
Cc: # v4.14+
Reported-by: Thomas Voegtle
Reviewed-by: Daniel Vetter
But please confirm with the reporter that it indeed fixes the issue before
pushing.
-Daniel
I re-checked the latest version of the patch and it indeed fixes the
problem.
Thanks,
Thomas
On Tue, 28 Nov 2017, Maarten Lankhorst wrote:
Op 27-11-17 om 19:09 schreef Thomas Voegtle:
Hello,
with v4.14 I recognized that my file server (headless haswell system)
doesn't enter packages pc3 anymore and only enters pc2 according to
powertop.
In v4.13 the system used pc2 and pc3.
Hello,
with v4.14 I recognized that my file server (headless haswell system)
doesn't enter packages pc3 anymore and only enters pc2 according to
powertop.
In v4.13 the system used pc2 and pc3.
So I bisected that down to:
ca91a2758fcef6635626993557dd51cfbb6dd134 is the first bad commit
commit c
On Thu, 14 Sep 2017, Andy Lutomirski wrote:
On Wed, Sep 13, 2017 at 5:59 AM, Thomas Voegtle wrote:
On Sun, 10 Sep 2017, Andy Lutomirski wrote:
On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel
wrote:
Dear Linux folks,
With Linux built from commit 4dfc2788033d (Merge tag
'iommu-updates-
On Sun, 10 Sep 2017, Andy Lutomirski wrote:
On Sat, Sep 9, 2017 at 11:48 PM, Paul Menzel wrote:
Dear Linux folks,
With Linux built from commit 4dfc2788033d (Merge tag 'iommu-updates-v4.14'
of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu), I get the
warning below on a Lenovo X60t
On Wed, 24 May 2017, Greg Kroah-Hartman wrote:
On Wed, May 24, 2017 at 11:26:25AM +0200, Thomas Voegtle wrote:
On Wed, 24 May 2017, Greg Kroah-Hartman wrote:
On Tue, May 23, 2017 at 10:59:35PM -0700, kernelci.org bot wrote:
stable-rc/linux-4.4.y boot: 54 boots: 0 failed, 54 passed
(v4.4.69
On Wed, 24 May 2017, Greg Kroah-Hartman wrote:
On Tue, May 23, 2017 at 10:59:35PM -0700, kernelci.org bot wrote:
stable-rc/linux-4.4.y boot: 54 boots: 0 failed, 54 passed
(v4.4.69-104-g2ebff3b7590b)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4
On Wed, 20 Jul 2016, Michal Kubecek wrote:
On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote:
And that one?
Happens while trying to start a firewall script with iptables-restore.
[ 180.071999] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
[iptables-restor:2338
On Wed, 20 Jul 2016, Michal Kubecek wrote:
On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote:
And that one?
Happens while trying to start a firewall script with iptables-restore.
[ 180.071999] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
[iptables-restor:2338
On Fri, 15 Jul 2016, Sasha Levin wrote:
On 07/15/2016 07:38 AM, Thomas Voegtle wrote:
On Wed, 13 Jul 2016, Sasha Levin wrote:
I'm announcing the release of the 4.1.28 kernel.
I have a serious memleak with 4.1.28 (like 20mb/s)
I stripped down my kernel config and started a bisect,
On Wed, 13 Jul 2016, Sasha Levin wrote:
I'm announcing the release of the 4.1.28 kernel.
I have a serious memleak with 4.1.28 (like 20mb/s)
I stripped down my kernel config and started a bisect, which came to:
# first bad commit: [c5ad33184354260be6d05de57e46a5498692f6d6] mm/swap.c:
flush lru
On Wed, 3 Feb 2016, Longepe, Philippe wrote:
Hi Thomas,
Thank you for sharing this test. I just did a quick test and yes this is
really interesting !
Without the scale option, the load is close to 100% for each cpus (so
the pstates are increasing up to the turbo frequency) but with
scale=3
On Wed, 3 Feb 2016, Longepe, Philippe wrote:
Thank you for sharing this test. I just did a quick test and yes this is
really interesting !
Without the scale option, the load is close to 100% for each cpus (so
the pstates are increasing up to the turbo frequency) but with
scale=320:208, the l
On Tue, 2 Feb 2016, Longepe, Philippe wrote:
Hi Thomas,
Yes, this new algorithm is intented to improve the performance versus power
efficiency.
Can you please provide us the exact instructions to reproduce your test ?
Hi,
my benchmark which I used is a little bit weird, so I tried to stri
Hi,
I have a Celeron J1900 system (Asrock Q1900B-ITX) always running the
latest kernel.
Since running the 4.5-rc2 kernel I have a performance drop in a ffmpeg
benchmark compared to 4.4. Converting a piece of mpeg to mp4 (to
/dev/null).
4.1 made the benchmark in 74s, 4.4 in 75s and now the 4.5-
On Wed, 4 Mar 2015, Jiang Liu wrote:
Hi all,
Could anybody help to dump an ACPI table from those failure
systems so we could archive it?
and here is the DSDT from a Asrock-Q1900B-ITX mainboard.
Thanks again,
Thomas
DSDT-Asrock-Q1900B-ITX
Description: Binary data
On Mon, 2 Mar 2015, Jiang Liu wrote:
Hi Thomas,
According to the dmesg, it seems that BIOS reports malformed
ACPI resource descriptors. The new code enforces stricter checks for
ACPI resource descriptors, so it skips some malformed ACPI resource
descriptors. Could you please to try this
On Mon, 2 Mar 2015, Jiang Liu wrote:
Hi Thomas,
I still can't figure out why the last resource entry "pci_bus
:00: root bus resource [mem 0x8000-0xd0716ffe]" gets ignored
by new code. Could you please help to apply these two patches and send
me back dmesg?
No problem, dmesg att
On Sat, 28 Feb 2015, Jiang Liu wrote:
On 2015/2/28 6:24, Rafael J. Wysocki wrote:
On Friday, February 27, 2015 03:50:32 PM Thomas Voegtle wrote:
Hi,
I have the same problem with a Asrock Q1900B-ITX mainboard with
a Intel Celeron J1900 onboard.
I did a bisect and ended up with
Hi,
I have the same problem with a Asrock Q1900B-ITX mainboard with
a Intel Celeron J1900 onboard.
I did a bisect and ended up with:
593669c2ac0fe18baee04a3cd5539a148aa48574 is the first bad commit
commit 593669c2ac0fe18baee04a3cd5539a148aa48574
Author: Jiang Liu
Date: Thu Feb 5 13:44:46
On Tue, 13 Jan 2015, Luis Henriques wrote:
On Tue, Jan 13, 2015 at 12:35:58AM +0100, Thomas Voegtle wrote:
On Mon, 12 Jan 2015, Luis Henriques wrote:
On Mon, Jan 12, 2015 at 09:30:45PM +0100, Thomas Voegtle wrote:
On Mon, 12 Jan 2015, Luis Henriques wrote:
This is the start of the review
On Mon, 12 Jan 2015, Luis Henriques wrote:
On Mon, Jan 12, 2015 at 09:30:45PM +0100, Thomas Voegtle wrote:
On Mon, 12 Jan 2015, Luis Henriques wrote:
This is the start of the review cycle for the Linux 3.16.7-ckt4 stable kernel.
This version contains 216 new patches, summarized below. The
On Mon, 12 Jan 2015, Luis Henriques wrote:
This is the start of the review cycle for the Linux 3.16.7-ckt4 stable kernel.
This version contains 216 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
http://kernel.ubuntu.
On Tue, 14 Aug 2007, Rafael J. Wysocki wrote:
> On Tuesday, 14 August 2007 00:12, Thomas Voegtle wrote:
> > On Mon, 13 Aug 2007, Rafael J. Wysocki wrote:
> >
> > > On Monday, 13 August 2007 23:31, Thomas Voegtle wrote:
> > > > On Mon, 13 Aug 2007, Rafael J.
On Mon, 13 Aug 2007, Rafael J. Wysocki wrote:
> On Monday, 13 August 2007 23:31, Thomas Voegtle wrote:
> > On Mon, 13 Aug 2007, Rafael J. Wysocki wrote:
> >
> > > On Sunday, 12 August 2007 21:39, Thomas Voegtle wrote:
> > > >
> > > > Hi,
> >
On Mon, 13 Aug 2007, Rafael J. Wysocki wrote:
> On Sunday, 12 August 2007 21:39, Thomas Voegtle wrote:
> >
> > Hi,
> >
> > today I saw this (output from my suspend script):
> >
> > -> woke up at Sun Aug 12 11:39:17 CEST 2007
> > -> uptime
Hi,
today I saw this (output from my suspend script):
-> woke up at Sun Aug 12 11:39:17 CEST 2007
-> uptime is
11:39am up 8 days 0:41, 10 users, load average: 26.12, 6.35, 2.17
Then I did a software suspend. After waking up, I saw this:
-> woke up at Sun Aug 12 14:41:56 CEST 2007
-> upt
Hi,
I want to use 2.6.16.y on the Intel DG965SS mainboard, but the kernel
stops booting:
...
ACPI: bus type pci registered
PCI: Using MMCONFIG
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
ACPI: Assume
Hi,
On Thu, 31 May 2007, Thomas Voegtle wrote:
> ==
[...]
> <06>2007 May 30 14:21:40 cbs kern: Sedlbauer: PCI base adr 0xa800
> <03>2007 May 30 14:21:40 cbs kern: irq 11: nobody cared (try booting
Hi Robert,
On Thu, 31 May 2007, Robert Hancock wrote:
> Thomas Voegtle wrote:
> >
> > ==
[...]
> > <03>2007 May 30 14:21:40 cbs kern: irq 11: nobody cared (try booting with
> > the \"ir
Hi,
after finally upgrading our systems from Kernel 2.4 to 2.6 we experienced
problems with the ISDN cards, a hisax driven Sedlbauer Speed Fax+.
A "modprobe hisax type=28 protocol=2" ends in this mess:
==
<05>2007 May 30 1
Hi,
Yesterday evening me an my friend had to shut down our most beloved
server. It had run for 6 years, 2 months and 25 days non stop. Nothing
could harm this little mailserver: y2k, electricity problems in the house
and no hacker found it.
We had to shut it down because of renovation of the r
On Wed, 19 Jan 2005, Herbert Xu wrote:
> On Tue, Jan 18, 2005 at 01:07:47PM -0500, John W. Linville wrote:
> >
> > No, that does not fix it. :-( In fact, it doesn't seem to alter the
> > problem at all...
>
> OK. In that case I agree with your patch. The overruns that I
> attributed to it wer
On Mon, 17 Jan 2005, John W. Linville wrote:
> Offset LVI past CIV when starting DAC/ADC in order to prevent
> stalled start.
> ---
> Here is the (working) patch I'm using against a later 2.4. This makes
> sound work fine with Enemy Territory.
>
This patch, hand-modified for 2.6.10 enabled soun
47 matches
Mail list logo
