-Truncate the commit log, because previous commit log is too long.
There are no too long commit messages. ;-)
> ---
> drivers/watchdog/sp5100_tco.c | 321
> +++++++---
> drivers/watchdog/sp5100_tco.h | 46 --
> 2 files changed, 306 insertions(+), 61 deletions(-)
[…]
Tested-by: Paul Menzel
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
/show_bug.cgi?id=43176
> > Signed-off-by: Takahisa Tanaka
>
> Added to linux-watchdog-next.
Is it allowed to rewrite history of linux-watchdog-next? If yes, could
you please add `CC: sta...@vger.kernel.org` to both of Takahisa’s
patches and also add my
Tested-by: Paul Menzel
Dear Takahisa,
Am Samstag, den 23.02.2013, 20:31 +0900 schrieb Takahisa Tanaka:
> The critical problem which can't boot OS until the power is completely
> cut off found on PC with SB700 chipset.
all SB700 boards or just a specific one?
> This patch fix the problem, but, this patch prevents the
Dear Tim,
thanks for the patch.
Am Mittwoch, den 20.02.2013, 13:31 -0700 schrieb Tim Gardner:
Noting the `gcc` version and build environment is never wrong. ;-)
> drivers/md/dm-raid.c: In function 'raid_ctr':
> drivers/md/dm-raid.c:453:53: warning: 'rebuilds_per_group' may be used
> uninitia
Dear Tim,
Am Mittwoch, den 20.02.2013, 23:16 +0100 schrieb Paul Menzel:
> Am Mittwoch, den 20.02.2013, 13:31 -0700 schrieb Tim Gardner:
>
> Noting the `gcc` version and build environment is never wrong. ;-)
>
> > drivers/md/dm-raid.c: In function 'raid_ctr':
>
Dear Inki Dae,
Am Donnerstag, den 06.09.2012, 11:35 +0900 schrieb InKi Dae:
> 2012/9/6 Mandeep Singh Baines :
> > The double invocations are incorrect but seem to be safe so I don't
> > think this will fix any bugs.
> >
> > Before:
> >
> > [7.639366] drm_prime_init_file ee3675d0
> > [7.6
Dear Jim,
Am Donnerstag, den 08.11.2012, 13:47 -0800 schrieb Jim Kukunas:
> Optimize RAID6 recovery functions to take advantage of
> the 256-bit YMM integer instructions introduced in AVX2.
in my experiencing optimizations always have to be back up by
benchmarks. Could you add those to the commi
Am Freitag, den 09.11.2012, 12:39 +0100 schrieb H. Peter Anvin:
> Sorry, we cannot share those at this time since the hardwarenis not yet
> released.
Too bad. Then I suggest an additional run time switch to enable and
disable that code path. So people later can easily test themselves.
Thanks,
Dear Dave,
Am Freitag, den 09.08.2013, 05:53 +0100 schrieb Dave Airlie:
[…]
> The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:
>
> Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)
>
> are available in the git repository at:
>
> git://people.freedesktop.org/~airlied/
zero.
However, the sp5100_tco driver should use the correct bitmask value.
[1] http://support.amd.com/us/Embedded_TechDocs/45482.pdf
Signed-off-by: Takahisa Tanaka
CC: sta...@vger.kernel.org
Signed-off-by: Paul Menzel
---
v2: Hopefully improved the commit message.
drivers/watchdog/sp5100_tco.h
Dear Takahisa,
thank you for your patch.
Am Sonntag, den 03.03.2013, 14:52 +0900 schrieb Takahisa Tanaka:
> The critical problem which can't boot OS until the power is completely
> cut off found on PC with SB700 chipset.
As commented in my first reply – at least I think – please add the
mainbo
ch: 8.28s
>
> Signed-off-by: Paul Taysom
> ---
> drivers/md/dm-verity.c | 29 +++++++--
> 1 file changed, 27 insertions(+), 2 deletions(-)
Acked-by: Paul Menzel
Thanks,
Paul
[1] https://code.google.com/p/chromium-os/issues/detail?id=39148
signature.asc
Description: This is a digitally signed message part
a);
> + flip->chan->data)
> return true;
> usleep_range(1, 2);
> return false;
Acked-by: Paul Menzel
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
or are there any problems
with stack sizes on some systems?
(This patch would be good alone for decreasing the number of code
lines. ;-))
> Signed-off-by: Kees Cook
> ---
> drivers/gpu/drm/drm_encoder_slave.c |6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
Ack
}
> - continue;
> - }
> -
> /* Not one of the known troublemakers, check the EDID */
> list_for_each_entry(connector, &dev->mode_config.connector_list,
> head) {
Acked-by: Paul Menzel
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
d setup the watchdog timer
>
> This patch has worked fine on my test environment(ASUS M4A89GTD-PRO/USB3 and
> DL165G7). therefore I believe that it's no problem to re-program the MMIO
> address for watchdog timer to chipset during disabled watchdog. However,
> I'm not
tic int radeon_ttm_debugfs_init(struct radeon_device *rdev);
With the clarification above
Acked-by: Paul Menzel
can be added to your patch.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
Dear Huacai,
Am Montag, den 13.08.2012, 15:16 +0800 schrieb Huacai Chen:
> On Mon, Aug 13, 2012 at 3:00 PM, Paul Menzel wrote:
> > thanks for your patch.
> >
> > Firstly, is Chen your first or last name? If it is your first name, your
> > From address should be switch
Am Montag, den 13.08.2012, 16:04 +0800 schrieb Huacai Chen:
> On Mon, Aug 13, 2012 at 3:50 PM, Paul Menzel wrote:
> > Am Montag, den 13.08.2012, 15:16 +0800 schrieb Huacai Chen:
> >> On Mon, Aug 13, 2012 at 3:00 PM, Paul Menzel wrote:
[…]
> >> > Am Montag, den 1
Dear Eldad,
thanks a lot for the patch.
Am Sonntag, den 13.01.2013, 22:00 +0100 schrieb Eldad Zack:
[…]
> From 5817128d2761f60051b069d2bb31209c909b6a04 Mon Sep 17 00:00:00 2001
> From: Eldad Zack
> Date: Sun, 13 Jan 2013 21:14:08 +0100
> Subject: [PATCH] drm/radeon: fix evergreen brightness
story to spot
a certain fix.
>
> Reported-by: Eldad Zack
> Signed-off-by: Alex Deucher
With the above,
Acked-by: Paul Menzel
> ---
> drivers/gpu/drm/radeon/evergreen.c |6 ++
> drivers/gpu/drm/radeon/ni.c|6 ++
> drivers/gpu/drm/radeon/r600.c
; return 0;
> - fb = entry->base.crtc.fb;
> + fb = crtc->fb;
>
> return vmw_kms_write_svga(dev_priv, w, h, fb->pitches[0],
> fb->bits_per_pixel, fb->depth);
Acked-by: Paul Menzel
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
Dear Eric,
Some nit picks where stuff contradicts the coding style.
Am Freitag, den 13.10.2017, 17:12 -0700 schrieb Eric Anholt:
> VC4's DSI1 has a bug where the AXI connection is broken for 32-bit
> writes from the CPU, so we use the DMA engine to DMA 32-bit values
> into registers instead. Th
Dear Linux folks,
If I want to output the Linux kernel messages to the serial console, but
the `console=ttyS…` line is missing on the Linux command line, is there
a way to activate that during run-time by, for example, using the sysfs
interface?
Kind regards,
Paul
Dear Linux folks,
The Linux serial console documentation [1] says that 115200 is the
maximum supported baudrate.
> The maximum baudrate is 115200.
Is that still accurate? If yes, where should I look to support higher
values?
Kind regards,
Paul
[1] https://www.kernel.org/doc/html/v4.13
Dear Greg,
Am 02.11.2017 um 17:53 schrieb Greg KH:
On Thu, Nov 02, 2017 at 04:39:36PM +0100, Paul Menzel wrote:
If I want to output the Linux kernel messages to the serial console, but the
`console=ttyS…` line is missing on the Linux command line, is there a way to
activate that during run
Dear Linux folks,
Using `sleepgraph.py` [1][2] to profile the suspend to RAM (STR) times,
shows that `ksys_enter` takes a noticeable amount of time.
13 ms on a TUXEDO Book BU1406 with the NVMe device *SAMSUNG
MZVKW512HMJP-0*, which is quite good, and over a 60 ms on ASRock
E350M1 with a
Dear Linux folks,
On 08/28/18 07:27, Paul Menzel wrote:
> Using `sleepgraph.py` [1][2] to profile the suspend to RAM (STR)
> times, shows that `ksys_enter` takes a noticeable amount of time.
>
> 13 ms on a TUXEDO Book BU1406 with the NVMe device *SAMSUNG
> MZVKW512HMJP-0*,
Dear Thomas,
Am 18.07.2018 um 21:00 schrieb Thomas Gleixner:
On Wed, 18 Jul 2018, Paul Menzel wrote:
On 07/18/18 17:39, Thomas Gleixner wrote:
Bah. Could you please enable GENERIC_IRQ_DEBUGFS and after a successful
boot up provide me the content of all files in /sys/kernel/debug/irq/ and
Dear Thomas,
On 07/18/18 22:05, Paul Menzel wrote:
> Am 18.07.2018 um 21:00 schrieb Thomas Gleixner:
>
>> On Wed, 18 Jul 2018, Paul Menzel wrote:
>>> On 07/18/18 17:39, Thomas Gleixner wrote:
>>>> Bah. Could you please enable GENERIC_IRQ_DEBUGFS and after a s
Dear Thomas,
On 07/19/18 15:48, Thomas Gleixner wrote:
> On Thu, 19 Jul 2018, Paul Menzel wrote:
>
>> I had to copy the files, and then was able to create an archive with
>> non-zero files. Please find the tar archive attached.
>
> Thanks for providing the data. All lo
Dear Linux folks,
Enabling the undefined behavior sanitizer and building GNU/Linux
4.18-rc5+ (with some unrelated commits) with GCC 8.1.0 from Debian
Sid/unstable, the warning below is shown.
[1.945853]
[
Dear Linux folks,
Enabling the undefined behavior sanitizer and building GNU/Linux
4.18-rc5+ (with some unrelated commits) with GCC 8.1.0 from Debian
Sid/unstable, the warning below is shown.
[2.111913]
[
Dear Linux folks,
Enabling the undefined behavior sanitizer and building GNU/Linux
4.18-rc5+ (with some unrelated commits) with GCC 8.1.0 from Debian
Sid/unstable, the warning below is shown.
[0.958688]
[
Dear Thomas,
Am 20.07.2018 um 10:39 schrieb Thomas Gleixner:
On Fri, 20 Jul 2018, Paul Menzel wrote:
Enabling the undefined behavior sanitizer and building GNU/Linux 4.18-rc5+
(with some unrelated commits) with GCC 8.1.0 from Debian Sid/unstable, the
warning below is shown.
[2.111913
Dear Jörg,
On 07/20/18 14:31, Jörg Rödel wrote:
> On Tue, Jul 17, 2018 at 06:02:07PM +0200, Paul Menzel wrote:
>> $ dmesg
>> […]
>> [0.145696] calling pci_iommu_init+0x0/0x3f @ 1
>> [0.145719] AMD-Vi: Unable to write to IOMMU perf counter.
>
> This i
Date: Sun, 8 Jul 2018 09:11:34 +0200
Defining `ATA_DEBUG` nothing can be really seen, as the log is spammed
with CDB messages.
Therefore, guard the print by `ATA_VERBOSE_DEBUG`.
Signed-off-by: Paul Menzel
---
drivers/ata/libata-scsi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions
Date: Sun, 8 Jul 2018 09:18:21 +0200
Defining `ATA_DEBUG` there are a lof of messages like below in the log.
[ 16.345472] ata_sg_setup: 1 sg elements mapped
As that is too verbose, only output these messages in verbose debug.
Signed-off-by: Paul Menzel
---
drivers/ata/libata-core.c | 2
handed over
control to the init process.
Signed-off-by: Paul Menzel
---
Ingo, hopefully it’s fine, putting you in Cc. I do not know, who the
right person is.
init/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/init/main.c b/init/main.c
index 3b4ada11ed52..3821bb55c787 100644
Dear Keith,
Thank you for your reply.
Am 22.01.2018 um 22:30 schrieb Keith Busch:
On Mon, Jan 22, 2018 at 10:02:12PM +0100, Paul Menzel wrote:
Benchmarking the ACPI S3 suspend and resume times with `sleepgraph.py
-config config/suspend-callgraph.cfg` [1], shows that the NVMe disk SAMSUNG
Dear Dmitry,
On 01/30/18 19:07, Dmitry Torokhov wrote:
On Tue, Jan 30, 2018 at 09:52:45AM -0800, Dmitry Torokhov wrote:
On Tue, Jan 30, 2018 at 06:36:34PM +0100, Paul Menzel wrote:
I do not know, when it started, but with Linux 4.14-rc8 and 4.15,
benchmarking suspend and resume time with
Dear Johannes,
On 01/04/18 16:08, Johannes Berg wrote:
Hi,
Can you reproduce this?
[ 54.426491] UBSAN: Undefined behaviour in net/wireless/nl80211.c:718:4
[ 54.426492] signed integer overflow:
[ 54.426493] -1665903437 * 100 cannot be represented in type 'int'
Obviously.
However, it
Dear Linux folks,
On 01/17/18 15:20, Paul Menzel wrote:
Testing Linux 4.15-rc8 on a Lenovo T60 (32 bit) and Dell XPS 13 9360 (64
bit) suspend to and resume from ACPI S3 doesn’t work anymore.
`./sleepgraph.py -config config/suspend-callgraph.cfg` [1] is used to
enable the FTRACE framework
Dear Steven,
On 01/17/18 17:25, Steven Rostedt wrote:
On Wed, 17 Jan 2018 11:19:43 -0500
Steven Rostedt wrote:
On Wed, 17 Jan 2018 11:10:31 -0500
Steven Rostedt wrote:
It's been fixed, and the the patch is in Linus's tree already:
https://git.kernel.org/pub/scm/linux/kernel/git/torva
Dear Linux folks,
On 12/13/17 14:13, Paul Menzel wrote:
I enabled the undefined behavior sanitizer, and built Linus’ master
branch under Ubuntu 17.10 with gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0.
```
$ grep UBSAN /boot/config-4.15.0-rc3+
CONFIG_ARCH_HAS_UBSAN_SANITIZE_ALL=y
Dear Jarkko,
On 03/12/18 11:17, Jarkko Sakkinen wrote:
On Sat, 2018-03-10 at 10:45 +, Thiebaud Weksteen wrote:
On Fri, Mar 9, 2018 at 5:54 PM Jeremy Cline wrote:
and it's hanging at "memset(log_tbl, 0, sizeof(*log_tbl) + log_size);"
Thanks. Well, it looks like the memory that is suppos
Dear Geert,
Sorry for writing you directory, but I saw you created the module
*string_selftest* in commit d6b28e09 (lib: add module support to string
tests).
I believe, I only did `make olddefconfig`, and the option is selected.
```
$ grep STRING_SELFTEST .config
CONFIG_STRING_SELFTEST=y
``
Dear Ard,
According to `initcall_debug`, `efisubsys_init` takes more than a few
milliseconds to execute on a Dell XPS 13 9370 (Intel(R) Core(TM)
i7-8550U CPU @ 1.80GHz).
```
[…]
[0.144474] calling efisubsys_init+0x0/0x2cf @ 1
[0.144474] Registered efivars operations
[0.173690]
Dear Ard,
Thank you for the quick reply.
On 03/24/2018 11:35 PM, Ard Biesheuvel wrote:
On 24 March 2018 at 22:10, Paul Menzel wrote:
Dear Ard,
According to `initcall_debug`, `efisubsys_init` takes more than a few
milliseconds to execute on a Dell XPS 13 9370 (Intel(R) Core(TM) i7-8550U
Dear Ard,
On 03/25/2018 09:41 AM, Paul Menzel wrote:
On 03/24/2018 11:35 PM, Ard Biesheuvel wrote:
On 24 March 2018 at 22:10, Paul Menzel wrote:
According to `initcall_debug`, `efisubsys_init` takes more than a few
milliseconds to execute on a Dell XPS 13 9370 (Intel(R) Core(TM)
i7
Dear Linux folks,
Commit 1455cf8 (driver core: emit uevents when device is bound to a
driver) [1], introduced in Linux 4.14-rc1, causes a regression in user
space.
After disconnecting USB devices, they are still shown as plugged in [2][3].
I seem to be having a similar issue, but with an iP
Dear Greg,
On 04/06/18 15:18, Greg Kroah-Hartman wrote:
On Fri, Apr 06, 2018 at 02:20:40PM +0200, Paul Menzel wrote:
Commit 1455cf8 (driver core: emit uevents when device is bound to a
driver) [1], introduced in Linux 4.14-rc1, causes a regression in user
space.
After disconnecting USB
Dear Linux folks,
On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
```
[2.338094] calling uvc_init+0x0/0x1000 [uvcvideo] @ 295
[2.338569] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 280
[2.338570] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[2.3
Dear Laurent,
On 03/20/18 14:30, Laurent Pinchart wrote:
On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below.
```
[…]
[2.340736] input: Integrated_Webcam_HD: Integrate as
/devices/pci:00/:00:14.0/usb1
Dear Laurent,
On 03/21/2018 10:25 AM, Laurent Pinchart wrote:
On Tuesday, 20 March 2018 18:46:24 EET Paul Menzel wrote:
On 03/20/18 14:30, Laurent Pinchart wrote:
On Tuesday, 20 March 2018 14:20:14 EET Paul Menzel wrote:
On the Dell XPS 13 9370, Linux 4.16-rc6 outputs the messages below
Dear Rui,
On 03/14/2018 08:32 AM, Zhang Rui wrote:
On 二, 2018-03-13 at 20:39 +0100, Paul Menzel wrote:
Booting the Dell XPS 13 9370 with Linux 4.16-rc4+ and
`initcall_debug`,
shows it is shown that int3403_driver_init needs over 330 ms to run.
[2.524839] initcall
Dear Linux folks,
What driver is recommended for current AMD Ryzen based processors
like *AMD Ryzen 5 PRO 1500 Quad-Core Processor* or *AMD EPYC 7601
32-Core Processor*?
Only from the acpi-cpufreq Kconfig description, I assume, that that
driver should be used.
> config X86_ACPI_CPUFREQ
>
; >> $(dot-target).cmd; \
This completes commit 9564a8cf (Kbuild: fix # escaping in .cmd files for
future Make).
Link: https://bugzilla.kernel.org/show_bug.cgi?id=197847
Cc: Randy Dunlap
Cc: Rasmus Villemoes
Cc: Masahiro Yamada
Cc: sta...@vger.kernel.org
Signed-off-by:
; >> $(dot-target).cmd; \
This completes commit 9564a8cf (Kbuild: fix # escaping in .cmd files for
future Make).
Link: https://bugzilla.kernel.org/show_bug.cgi?id=197847
Cc: Randy Dunlap
Cc: Rasmus Villemoes
Cc: Masahiro Yamada
Cc: sta...@vger.kernel.org
Signed-off-by: Paul
Dear Linux folks,
Building the configuration created with `make tinyconfig` on the Power 8
system IBM S822LC with Ubuntu 18.04 fails with the error below.
```
$ git describe --dirty
v4.17-rc6-296-gbc2dbc5420e8
$ git log --oneline -1
bc2dbc5420e8 (HEAD -> master, origin/master, origin/HEAD) Me
Dear Christophe,
Am 26.05.2018 um 18:02 schrieb christophe leroy:
Le 26/05/2018 à 06:35, Paul Menzel a écrit :
Building the configuration created with `make tinyconfig` on the Power
8 system IBM S822LC with Ubuntu 18.04 fails with the error below.
```
$ git describe --dirty
v4.17-rc6-296
Dear Linux folks,
In QEMU 2.11 a disk is only detected by the AHCI driver and not by
libata. On QEMU’s Standard PC (i440FX + PIIX, 1996), that causes an
attached drive not to be detected as that machine doesn’t support AHCI.
Here is the output with the machine Standard PC (Q35 + ICH9, 2009),
Dear Linux folks,
On 05/13/18 10:34, Paul Menzel wrote:
In QEMU 2.11 a disk is only detected by the AHCI driver and not by
libata. On QEMU’s Standard PC (i440FX + PIIX, 1996), that causes an
attached drive not to be detected as that machine doesn’t support AHCI.
Here is the output with the
Dear Dominik,
Thank you for your quick response.
Am 11.12.18 um 07:51 schrieb Dominik Brodowski:
On Mon, Dec 10, 2018 at 04:30:05PM +0100, Paul Menzel wrote:
With Linux 4.14.76, the scaling governor *powersave* is shown as
being available despite being disabled in the configuration
Dear Linux folks,
Using *powersave* as P-state selection algorithm, on an idle system
with an Intel i7-6700 (Sandy Bridge), the frequency only goes down to
900 MHz instead of the minimum frequency of 800 MHz.
$ uname -a
Linux keineahnung.molgen.mpg.de 4.20.0-rc5.mx64.234 #1 SMP Mon Dec 3 16:58
Dear Doug,
Thank you for your reply.
On 12/13/18 00:06, Doug Smythies wrote:
> On 2018.12.12 13:40 Paul Menzel wrote:
>
>> Using *powersave* as P-state selection algorithm, on an idle system
>
> Define "idle system".
> If your computer is running a GUI, or is ev
Dear Rafael,
On 12/13/18 11:39, Rafael J. Wysocki wrote:
> On Thu, Dec 13, 2018 at 10:54 AM Paul Menzel wrote:
>> On 12/13/18 00:06, Doug Smythies wrote:
>>> On 2018.12.12 13:40 Paul Menzel wrote:
>>>
>>>> Using *powersave* as P-state selection algorithm,
Dear Linux folks,
With Linux 4.14.76, the scaling governor *powersave* is shown as
being available despite being disabled in the configuration.
```
$ uname -a
Linux xxx.molgen.mpg.de 4.14.76.mx64.228 #1 SMP Tue Oct 16 19:20:58 CEST 2018
x86_64 GNU/Linux
$ zcat /proc/config.gz |grep CONFIG_CPU_F
Dear Thomas,
On 01/07/19 16:24, Thomas Gleixner wrote:
> On Mon, 31 Dec 2018, Paul Menzel wrote:
>
>> Linux 4.19.13 from Debian Sid/unstable logs the message below on the board
>> MSI
>> MS-7A37/B350M MORTAR with the processor AMD Ryzen 3 2200G.
>>
>> As a
Dear Linux folks,
Linux 4.19.13 from Debian Sid/unstable logs the message below on the
board MSI MS-7A37/B350M MORTAR with the processor AMD Ryzen 3 2200G.
As a result, the early time stamps do not seem to be working.
[0.00] Linux version 4.19.0-1-amd64 (debian-ker...@lists.debian.o
Dear Linux folks,
On 01/03/19 22:45, Paul Menzel wrote:
> On the server board Asus KGPE-D16 with AMD Opteron 6278 processor updating
> the microcode update in the firmware from 0x0600062e to 0x0600063e seems to
> cause a general protection fault with Linux 4.14.87 and 4.20-rc7.
>
Dear Thomas,
As always thank you for the quick reply.
On 10/17/18 18:39, Thomas Gleixner wrote:
> On Wed, 17 Oct 2018, Paul Menzel wrote:
>>
>> Please find the debug patches attached. The `random: %i` messages are from
>> `crng_fast_load()`.
>>
>> My questi
not in the context of
the WX checking output.
Reported-by: Paul Menzel
Signed-off-by: Thomas Gleixner
Cc: Joerg Roedel
Cc: Kees Cook
Cc: Bjorn Helgaas
---
arch/x86/mm/dump_pagetables.c | 35 +++
1 file changed, 27 insertions(+), 8 deletions(-)
Thank you for
Dear Borislav,
Am 03.10.2018 um 23:22 schrieb Borislav Petkov:
On Fri, Sep 28, 2018 at 04:55:19PM +0200, Thomas Gleixner wrote:
Sorry for the delay and thanks for the data. A quick diff did not reveal
anything obvious. I'll have a closer look and we probably need more (other)
information to nai
Dear Arnaldo,
Am 03.10.2018 um 22:57 schrieb Arnaldo Carvalho de Melo:
Em Wed, Oct 03, 2018 at 10:42:39PM +0200, Paul Menzel escreveu:
For profiling the boot on my Debian Sid/unstable system (32-bit user space),
the following service unit is used.
You forgot to mention what is the version
Dear Borislav,
On 10/04/18 10:14, Borislav Petkov wrote:
> On Thu, Oct 04, 2018 at 10:03:21AM +0200, Joerg Roedel wrote:
>> I also triggered this when working in the PTI-x32 code. It always
>> happens on a 32-bit PAE kernel for me.
>>
>> Tracking it down I ended up in (iirc) arch/x86/mm/pageattr.
Dear Borislav,
On 10/04/18 10:49, Borislav Petkov wrote:
> On Thu, Oct 04, 2018 at 10:40:49AM +0200, Paul Menzel wrote:
>> Do you have a commit, I could test.
>
> Not yet
I meant just the test you did.
> but I have a question for you: why are you running 32-bit and
> ha
Dear Borislav,
On 10/04/18 12:54, Borislav Petkov wrote:
> On Thu, Oct 04, 2018 at 10:59:18AM +0200, Paul Menzel wrote:
>> I meant just the test you did.
>
> https://lkml.kernel.org/r/20181003212255.gb28...@zn.tnic
I see. But there you write, the machine does boot.
While her
Dear Thomas,
On 10/05/18 11:27, Thomas Gleixner wrote:
> On Thu, 4 Oct 2018, Joerg Roedel wrote:
>
>> On Wed, Oct 03, 2018 at 11:22:55PM +0200, Borislav Petkov wrote:
>>> On Fri, Sep 28, 2018 at 04:55:19PM +0200, Thomas Gleixner wrote:
Sorry for the delay and thanks for the data. A quick di
Dear Josh, dear Linux folks,
Trying to decrease the boot time of the 64-bit Linux kernel (Linux
4.19-rc7 (0238df64)) on a Asus F2A85-M PRO with an AMD processor, I
noticed `unwind_init()` called from `setup_arch()`
`arch/x86/kernel/setup.c` takes over 100 ms to initialize according to
Linux
Dear Linux folks,
On a MSI B350M MORTAR with AMD Ryzen 3 2200g (Raven) with Linux 4.18-rc5+
and Debian Sid/unstable the system freezes with the messages below.
```
$ git log --oneline -1
30b06abfb92b (HEAD -> master, origin/master, origin/HEAD) Merge tag
'pinctrl-v4.18-3' of
git://git.kernel.o
Dear Linux,
Loading the amdgpu module on Ryzen 3 2{2,4}00G (Raven) systems sometimes
causes a general protection fault [1]. At least on my system I am unable
to reliably reproduce the issue.
```
[ 35.265941] kfd kfd: kgd2kfd_probe failed
[ 35.537445] general protection fault: [#1] SMP N
Dear Thomas, dear Bjorn,
Thank you for your quick responses.
On 07/18/18 17:02, Thomas Gleixner wrote:
> On Wed, 18 Jul 2018, Bjorn Helgaas wrote:
>> [+cc Marc, Thomas]
>
> Uurgh. That's definitely what I need right now ... :)
>
>> On Wed, Jul 18, 2018 at 03:28:
[I removed the folks from the unrelated patches.]
Dear Thomas,
On 07/18/18 17:39, Thomas Gleixner wrote:
> On Wed, 18 Jul 2018, Paul Menzel wrote:
>> On 07/18/18 17:02, Thomas Gleixner wrote:
>>>>> 93.885: [ 23.020572] BUG: unable to handle kernel NULL point
Dear Anna-Maria,
Thank you very much for the support. I was finally able to collect the
data you asked for.
Am 09.04.24 um 09:57 schrieb Anna-Maria Behnsen:
Paul Menzel writes:
[…]
Am 08.04.24 um 12:10 schrieb Anna-Maria Behnsen:
Paul Menzel writes:
On Dell XPS 13 9360/0596KF, BIOS
[Added URLs for files.]
Am 21.08.24 um 10:20 schrieb Paul Menzel:
Dear Anna-Maria,
Thank you very much for the support. I was finally able to collect the
data you asked for.
Am 09.04.24 um 09:57 schrieb Anna-Maria Behnsen:
Paul Menzel writes:
[…]
Am 08.04.24 um 12:10 schrieb Anna
Dear Linux folks,
All the way up to QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-5) and
Linux 5.10.13, Linux logs the warning below:
acpi PNP0A03:00: fail to add MMCONFIG information, can't access
extended PCI configuration space under this bridge.
One way to reproduce it:
qemu-
Dear Linux folks,
Using Linux 5.10.13 (and before), looking at the Linux kernel warnings,
the CPU numbers show up. For example with 12 cpus/threads:
```
$ sudo dmesg --level=warn
[0.216103] #2
[0.220105] #3
[0.224103] #4
[0.228104] #5
[0.232110] #6
[0.236101]
Dear Petr,
Thank you for the quick reply.
Am 16.02.21 um 10:49 schrieb Petr Mladek:
On Mon 2021-02-15 20:22:34, Paul Menzel wrote:
Using Linux 5.10.13 (and before), looking at the Linux kernel warnings, the
CPU numbers show up. For example with 12 cpus/threads:
```
$ sudo dmesg --level
Dear Borislav, dear Petr,
Am 16.02.21 um 11:14 schrieb Borislav Petkov:
On Tue, Feb 16, 2021 at 10:49:04AM +0100, Petr Mladek wrote:
Also you should add '\n' into the previous string to make the behavior
clear. It will always be printed on a new line when pr_info()
is used.
This was made to
[CC’ing coreboot, GRUB, SeaBIOS, Syslinux project and Linux kernel]
Am Montag, den 16.03.2015, 11:38 +0100 schrieb Kay Sievers:
> On Mon, Mar 16, 2015 at 11:29 AM, Umut Tezduyar Lindskog wrote:
> > I would like to pass the time it was spent in bootloader to systemd.
> > Is there a kernel command l
Dear Linux folks,
I am trying to decrease the boot time of the Linux kernel so the LUKS
passphrase dialog (in the initrd) is shown as quickly as possible. The
devices I test with is a Lenovo X60 and ASRock E350M1 both running with
coreboot and the GRUB payload. The goal is to do this without
Dear Yazen, Eric, Tom,
On 02/26/18 17:42, Tom Lendacky wrote:
On 2/26/2018 10:37 AM, Morton, Eric wrote:
Yazen dug out PLAT-21393 as sounding like this issue. I haven't had
a chance to digest it.
Yes, internally to AMD, that was the bug that tracked the issue I
was referring to.
If you c
Dear Linux folks,
I am trying to reduce the start-up time of the Linux kernel on an old
Lenovo X60. Looking through the time stamps of Linux 4.16-rc7+, the
modules `lp` and `ppdev` both take more than ten milliseconds to
initialize according to `initcall_debug`.
```
[8.337692] calling
Dear Joel, dear Linux folks,
We have an IBM S822LC system (Firestone(?)). Building of OpenBMC
currently fails, as the not everything was ported from dev-4.10 to
dev-4.13 [1], and therefore a file cannot be found.
Looking at upstream Linux, there are BMCs for Power 8 systems, like
Palmetto,
Dear Linux folks,
Linux 4.17-rc5 shows the error below on the Dell XPS 13 9370 with Debian
Sid/unstable.
```
[…]
[0.440240] usb: port power management may be unreliable
[0.441358] usbcore: registered new interface driver usb-storage
[0.441367] usbcore: registered new interface dri
Dear Greg,
As always, thank you for the prompt response.
On 05/15/18 18:00, Greg KH wrote:
On Tue, May 15, 2018 at 04:34:03PM +0200, Paul Menzel wrote:
Linux 4.17-rc5 shows the error below on the Dell XPS 13 9370 with Debian
Sid/unstable.
```
[…]
[0.440240] usb: port power management
Dear Heikki,
On 05/16/18 13:58, Heikki Krogerus wrote:
On Wed, May 16, 2018 at 10:02:26AM +0200, Greg KH wrote:
On Tue, May 15, 2018 at 06:47:37PM +0200, Paul Menzel wrote:
On 05/15/18 18:00, Greg KH wrote:
On Tue, May 15, 2018 at 04:34:03PM +0200, Paul Menzel wrote:
Linux 4.17-rc5
Dear Bart,
On 04/24/18 19:31, Bart Van Assche wrote:
On Tue, 2018-04-24 at 19:10 +0200, Paul Menzel wrote:
Please find the configuration file attached. The log only has
`initcall_debug no_console_suspend` added.
What I was looking for in the .config is the following:
CONFIG_SCSI_MQ_DEFAULT
Dear Bart,
Am 24.04.2018 um 23:17 schrieb Bart Van Assche:
On Tue, 2018-04-24 at 23:04 +0200, Paul Menzel wrote:
I applied your change, and rebuilt the Linux kernel. Unfortunately, it
looks like, it didn’t make a difference.
In that case I don't know what is causing the failure. Can yo
1 - 100 of 370 matches
Mail list logo
