Dear Robert,
Thank you for looking into this.
On 2017-04-12 17:54, Moore, Robert wrote:
And probably the dmesg if error messages appear in there.
Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please
find the output of `sudo acpidump` attached.
[…]
Kind regards,
Pau
Dear Linux folks,
Measuring where time is spent during boot with `systemd-bootchart` on an
Asus A780FullHD, it turns out that half a second is spent in
`pci_apply_final_quirks()`.
Here are the times copied from the SVG:
init_ladder 0.012s
init_menu 0.012s
pm_sysrq_init 0.012s
acpi_i
Dear Jarkko,
On 2017-04-07 22:13, Jarkko Sakkinen wrote:
On Thu, Apr 06, 2017 at 01:10:13PM -0600, Jason Gunthorpe wrote:
On Thu, Apr 06, 2017 at 08:26:22PM +0200, Paul Menzel wrote:
> >We added direct ACPI binding to the driver in addition to PNP, so if
> >you have an ACPI table
On 2017-04-06 18:55, Jason Gunthorpe wrote:
On Thu, Apr 06, 2017 at 08:18:33AM +0200, Paul Menzel wrote:
Indeed, that improves the situation. I still need to pass `force=1` to
the
module to get `/dev/tpm0`. No idea, why it’s not in included in Linux
4.9
yet.
Fair point.. Jarkko - could you
Dear Maciej,
On 2017-04-05 13:03, Maciej S. Szmigiero wrote:
tpm tpm0: Unable to read burstcount
tpm tpm0: tpm_transmit: tpm_send: error -16
tpm_tis tpm_tis: Could not get TPM timeouts and durations
This looks like a regression I had on ThinkPad X61S.
You can try with a patch from the follo
Dear Jason,
Thank you for your reply.
On 2017-04-04 19:15, Jason Gunthorpe wrote:
On Tue, Apr 04, 2017 at 06:29:06PM +0200, Paul Menzel wrote:
Unfortunately, there seems to have been a regression between Linux
3.16
and 4.8 and 4.9, so that the Linux kernel doesn’t create the TPM
device
Dear Linux folks,
Currently, TPM support is added to the coreboot project for the Lenovo
X60 [1].
Unfortunately, there seems to have been a regression between Linux 3.16
and 4.8 and 4.9, so that the Linux kernel doesn’t create the TPM device.
```
$ more /proc/version Linux version 3.16.0-4
Dear Zoltán,
Am Samstag, den 01.04.2017, 12:13 +0200 schrieb Boszormenyi Zoltan:
[…]
> and have split the patch into three pieces now (USB quirks, i2c-piix4
> and sp5100_tco) and they were sent to the relevant mailing lists.
Could you please add me to the receiver list of these patches, so th
Dear Wolfram,
Thank you for the reply, which we talked about briefly at the
Chemnitzer LinuxTage.
Am Freitag, den 03.03.2017, 11:17 +0100 schrieb Wolfram Sang:
> > Unfortunately, commit 2fee61d22e (i2c: piix4: Add support for
> > multiplexed main adapter in SB800) [1] caused a regression. Tim
>
Dear Josh,
On 03/27/17 17:01, Paul Menzel wrote:
On 03/27/17 16:54, Josh Poimboeuf wrote:
On x86-32, with CONFIG_FIRMWARE and multiple CPUs, if you enable
function graph tracing and then suspend to RAM, it will triple fault and
reboot when it resumes.
The first fault happens when booting a
ould break.)
- Track down load_ucode_ap()'s entire callee tree and mark all the
functions 'notrace'. (Probably not realistic.)
- Pause graph tracing in ftrace_suspend_notifier_call() or bringup_cpu()
or __cpu_up(), and ensure that the pause facility can be queried from
re
Dear Josh,
On 2017-03-21 21:44, Paul Menzel wrote:
On 2017-03-16 14:56, Josh Poimboeuf wrote:
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer
Dear Josh,
On 2017-03-16 14:56, Josh Poimboeuf wrote:
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer: expected f6919d98, received f6919db0
from
Dear Joe,
Am Sonntag, den 19.03.2017, 01:31 -0700 schrieb Joe Perches:
> On Sat, 2017-03-18 at 13:15 +0100, Paul Menzel wrote:
> > Dear checkpatch developers,
> >
> >
> > The coreboot project started using checkpatch.pl, and now some effort
> > is going
Dear checkpatch developers,
The coreboot project started using checkpatch.pl, and now some effort
is going into fixing issues pointed out by `checkpatch.pl`.
The file `src/arch/x86/acpi_s3.c` in coreboot contains the code below.
```
205 void (*acpi_do_wakeup)(uintptr_t vector, u32 backup_so
Dear Josh,
On 03/10/17 00:04, Josh Poimboeuf wrote:
On Thu, Mar 09, 2017 at 09:43:47PM +0100, Paul Menzel wrote:
On 2017-03-09 17:29, Steven Rostedt wrote:
On Thu, 9 Mar 2017 10:16:02 -0600 Josh Poimboeuf wrote:
On Thu, Mar 09, 2017 at 09:36:30AM -0500, Steven Rostedt wrote:
On Thu, 9 Mar
On 2017-03-09 17:29, Steven Rostedt wrote:
On Thu, 9 Mar 2017 10:16:02 -0600
Josh Poimboeuf wrote:
On Thu, Mar 09, 2017 at 09:36:30AM -0500, Steven Rostedt wrote:
> On Thu, 9 Mar 2017 13:12:28 +0100
> Paul Menzel wrote:
> > Hopefully, I am contacting the right people
Dear Steven, dear Ingo,
Hopefully, I am contacting the right people for my issue.
Suspending a system with Linux 4.9.13 with tracing enabled, it fails
with the screen still enabled, and the LED blinking. Attaching a serial
console to the dock, shows the messages below.
> […]
[ 59.063238]
Dear Linux folks,
Unfortunately, commit 2fee61d22e (i2c: piix4: Add support for
multiplexed main adapter in SB800) [1] caused a regression. Tim
reported that to the Linux Kernel Bugtracker as bug #170741 last
September [2], but it looks like the affected subsystems don’t use it.
So I just copy h
[Please CC me, as I am not subscribed.]
Dear OpenBMC people,
If you haven’t heard yet, there is a crowdfunding campaign going on to
fund a port of OpenBMC to the Asus KGPE-D16 [1].
The free firmware coreboot [2] runs on that board, and no BLOBs have to
be used with it. Having OpenBMC run on tha
Dear Matthews, dear Pali,
Installing Debian 9 (Stretch/testing) with Linux 4.9.6 on the Dell
Latitude E6510, the warnings below are shown.
```
$ more /proc/version
Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc
version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-
Dear Linux folks,
since some time, at Linux 4.8, 4.9, and 4.10-rc6, the OOM kicks in on a
8 GB machine.
```
Feb 12 08:21:50 asrocke350m1 kernel: updatedb.mlocat invoked oom-killer:
gfp_mask=0x16040d0(GFP_TEMPORARY|__GFP_COMP|__GFP_NOTRACK), nodemask=
Feb 12 08:21:50 asrocke350m1 kernel: updated
Dear Borislav, dear Mario,
On 01/27/17 18:16, mario.limoncie...@dell.com wrote:
-Original Message-
From: Borislav Petkov [mailto:b...@alien8.de]
Sent: Friday, January 27, 2017 11:11 AM
To: Paul Menzel
Cc: Ashok Raj ; Linux Kernel Mailing List ; Thorsten Leemhuis ; Len
Brown ; Tony
Dear Ashok,
On 01/09/17 20:23, Raj, Ashok wrote:
On Mon, Jan 09, 2017 at 12:53:33PM +0100, Paul Menzel wrote:
On 01/05/17 02:12, Raj, Ashok wrote:
CPUID Vendor Intel Family 6 Model 142
This is Kabylake Mobile
Hardware event. This is not a software error.
MCE 1
CPU 0 BANK 7
MISC
he OS.
That is fine, but then it shouldn’t be the default, until most of these
bugs are identified and fixed.
Also, the commit message should make that more clear, and in my opinion
the tested devices be listed.
-Original Message-
From: Paul Menzel [mailto:pmen...@molgen.mpg.de]
Sent: Tu
Dear Greg,
On 2017-01-13 14:00, Greg Kroah-Hartman wrote:
On Wed, Jan 11, 2017 at 03:26:06PM +0100, Paul Menzel wrote:
On 01/11/17 15:12, Winkler, Tomas wrote:
> > > On 01/11/17 10:24, Winkler, Tomas wrote:
> > > > >
> > > > > On Wed, Jan 11, 2017 a
On 01/11/17 10:49, Winkler, Tomas wrote:
Subject: Re: Dell XPS13 does not suspend with Linux 4.10-rc3
On 01/11/17 10:36, Greg Kroah-Hartman wrote:
On Wed, Jan 11, 2017 at 09:53:38AM +0100, Paul Menzel wrote:
On 01/10/17 23:24, Jan Niehusmann wrote:
On Tue, Jan 10, 2017 at 09:43:31PM +0100
Dear Tomas,
On 01/11/17 15:12, Winkler, Tomas wrote:
On 01/11/17 10:24, Winkler, Tomas wrote:
On Wed, Jan 11, 2017 at 01:27:21AM +0200, Tomas Winkler wrote:
On older platforms the command should be just ignored by the
firmware but some older platforms misbehave so it's safer to send
the com
Dear Tomas,
On 01/11/17 10:24, Winkler, Tomas wrote:
On Wed, Jan 11, 2017 at 01:27:21AM +0200, Tomas Winkler wrote:
On older platforms the command should be just ignored by the firmware
but some older platforms misbehave so it's safer to send the command
only if required.
Thanks! This fixes
On 01/11/17 10:36, Greg Kroah-Hartman wrote:
On Wed, Jan 11, 2017 at 09:53:38AM +0100, Paul Menzel wrote:
On 01/10/17 23:24, Jan Niehusmann wrote:
On Tue, Jan 10, 2017 at 09:43:31PM +0100, Jan Niehusmann wrote:
And I bisected the issue to commit 7279b238ba, "mei: send OS type to t
Dear Linux folks,
On 01/10/17 23:24, Jan Niehusmann wrote:
On Tue, Jan 10, 2017 at 09:43:31PM +0100, Jan Niehusmann wrote:
And I bisected the issue to commit 7279b238ba, "mei: send OS type to the
FW"
Indeed, just disabling the FIXUP implemented by that commit fixes
suspend for me, with 4.10.
Dear Ashosk, dear Borislav,
On 01/05/17 02:12, Raj, Ashok wrote:
CPUID Vendor Intel Family 6 Model 142
This is Kabylake Mobile
Hardware event. This is not a software error.
MCE 1
CPU 0 BANK 7
MISC 7880018086 ADDR fef1ce40
TIME 1483543069 Wed Jan 4 16:17:49 2017
MCG status:
MCi status:
Erro
Dear Boris,
On 01/09/17 12:05, Borislav Petkov wrote:
On Mon, Jan 09, 2017 at 11:55:41AM +0100, Paul Menzel wrote:
[…]
Also, is that just for MacBookPro11,3? The MCE for the Dell XPS13 looks
different from what I see, doesn’t it?
Yes, yours is different. I'm still waiting for y
On 01/06/17 17:54, Borislav Petkov wrote:
On Fri, Jan 06, 2017 at 07:58:31AM -0800, Raj, Ashok wrote:
Looks like we don't need a return value from therm_throt_process(),
we can fix that as void as well.
Right you are, here's v2:
---
From a8151fa6f18c2605eb7972061234f05e79b372c4 Mon Sep 17 00:
Dear Linux folks,
The logs contain the following messages.
From Linux 4.10-rc2+ (0f64df301240 Merge branch 'parisc-4.10-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux):
Jan 04 16:17:51 xps13 kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0
Bank 6: ee4
Dear Thorsten,
On 12/27/16 08:48, Thorsten Leemhuis wrote:
Lo! On 23.12.2016 13:36, Paul Menzel wrote:
I heard that you both have a Dell XPS13. I got the “revision” 9360, and
installed Debian Stretch/testing on it with Linux 4.8.15 and Linux 4.9-rc8.
When pressing the power button the GNOME
Dear Linus, dear Len,
I heard that you both have a Dell XPS13. I got the “revision” 9360, and
installed Debian Stretch/testing on it with Linux 4.8.15 and Linux 4.9-rc8.
When pressing the power button the GNOME dialog, asking what to do
(restart, power off, …) doesn’t appear.
Neither `xev`
On 11/30/16 12:54, Paul E. McKenney wrote:
> On Wed, Nov 30, 2016 at 03:53:20AM -0800, Paul E. McKenney wrote:
>> On Wed, Nov 30, 2016 at 12:09:44PM +0100, Michal Hocko wrote:
>>> [CCing Paul]
>>>
>>> On Wed 30-11-16 11:28:34, Donald Buczek wrote:
>>> [...]
shrink_active_list gets and releases
630 @ 2.30GHz. So that
shouldn’t have been a problem.
Kind regards,
Paul Menzel
that.
> >
> > I would be interested to see some reclaim tracepoints enabled. Could you
> > try that out? At least mm_shrink_slab_{start,end} and
> > mm_vmscan_lru_shrink_inactive. This should tell us more about how the
> > reclaim behaved.
>
> We'll try that tomorrow!
Unfortunately, looking today at `trace`, the corresponding messages have
already been thrown out the buffer. We continue trying.
Kind regards,
Paul Menzel
Dear Linux folks,
On 11/16/16 22:24, Donald Buczek wrote:
On 10.11.2016 14:59, Martin K. Petersen wrote:
"Paul" == Paul Menzel writes:
Linux does not provide device discovery ordering guarantees. You need
to fix your scripts to use UUIDs, filesystem labels, or DM devices to
On 11/14/16 18:28, David Miller wrote:
From: Paul Menzel
Date: Mon, 14 Nov 2016 09:25:47 +0100
On 11/13/16 06:01, Baoquan He wrote:
This is v2 post.
In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
firmware requesting code was moved from open stage to probe
Dear Baoquan,
On 11/13/16 06:01, Baoquan He wrote:
This is v2 post.
In commit 3e1be7a ("bnx2: Reset device during driver initialization"),
firmware requesting code was moved from open stage to probe stage.
The reason is in kdump kernel hardware iommu need device be reset in
driver probe stage,
inclusion into the stable Linux kernel.
Acked-by: Paul Menzel
Thanks,
Paul
Dear Jay,
On 11/10/16 19:19, Jay Rouman wrote:
Did this get pushed upstream? I see a new patch for 4.8.7 but the BNX2
regression doesn't seem to be fixed. Or am I missing something?
I don’t think Baoquan’s patch is ready yet.
I guess he will put you in the receivers list, once he sends it
Dear Linux folks,
Running the Firmware Test Suite (fwts) [1] on an ASRock E350M1, it
suggests that ASPM should be enabled.
The module r8169 disables ASPM since the commit below.
commit ba04c7c93bbcb48ce880cf75b6e9dffcd79d4c7b
Author: Stanislaw Gruszka
Date: Tue Feb 22 02:00:11 2011 +
Dear Ivan, dear Jeann,
There is an unwanted regression due to commit d7f96f97 (firmware:
dmi_scan: add SBMIOS entry and DMI tables).
Since Linux kernel 4.2 the utility `cbmem`, used to access information
stored in memory, from the coreboot project [1] does not work anymore
on a lot of systems as
[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 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/
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
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
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
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
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,
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,
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 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
/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
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
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
-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
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 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
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
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 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
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
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
}
> - 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
; 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
301 - 370 of 370 matches
Mail list logo
