On Wed, Jun 17, 2020 at 12:00:14AM +0200, Gabriel C wrote:
> Am Di., 16. Juni 2020 um 23:25 Uhr schrieb Arvind Sankar
> :
> >
> > On Tue, Jun 16, 2020 at 11:17:08PM +0200, Gabriel C wrote:
> > > Am Di., 16. Juni 2020 um 22:33 Uhr schrieb Arvind Sankar
> > > :
> > > >
> > > > Can you attach the
Am Di., 16. Juni 2020 um 23:25 Uhr schrieb Arvind Sankar
:
>
> On Tue, Jun 16, 2020 at 11:17:08PM +0200, Gabriel C wrote:
> > Am Di., 16. Juni 2020 um 22:33 Uhr schrieb Arvind Sankar
> > :
> > >
> > > Can you attach the output of gcc -dumpspecs and gcc -v? I suspect your
> > > compiler enables
Am Di., 16. Juni 2020 um 23:17 Uhr schrieb Gabriel C
:
>
> Am Di., 16. Juni 2020 um 22:33 Uhr schrieb Arvind Sankar
> :
> > Does this patch help?
> >
>
> I'll test in a bit and let you know.
With the patch the kernel compiles fine.
> > diff --git a/arch/x86/purgatory/Makefile
On Tue, Jun 16, 2020 at 11:17:08PM +0200, Gabriel C wrote:
> Am Di., 16. Juni 2020 um 22:33 Uhr schrieb Arvind Sankar
> :
> >
> > Can you attach the output of gcc -dumpspecs and gcc -v? I suspect your
> > compiler enables stack protector by default. My distro compiler does
> > that too, but not if
Am Di., 16. Juni 2020 um 22:37 Uhr schrieb Borislav Petkov :
>
> On Tue, Jun 16, 2020 at 10:11:46PM +0200, Gabriel C wrote:
> > I didn't look closer at that but from the error, it seems to be,
> > some missing -fstack-protector* vs -fno-stack-protector* checks
> > somewhere.
>
> Can you give exact
Am Di., 16. Juni 2020 um 22:33 Uhr schrieb Arvind Sankar
:
>
> On Tue, Jun 16, 2020 at 10:11:46PM +0200, Gabriel C wrote:
> > * Am So., 14. Juni 2020 um 22:44 Uhr schrieb Linus Torvalds
> > :
> >
> > Hello,
> >
> > > So I didn't really expect this, but 5.8 looks to be one of our biggest
> > >
On Tue, Jun 16, 2020 at 10:11:46PM +0200, Gabriel C wrote:
> I didn't look closer at that but from the error, it seems to be,
> some missing -fstack-protector* vs -fno-stack-protector* checks
> somewhere.
Can you give exact .config?
Also, what compiler exactly?
I have
On Tue, Jun 16, 2020 at 10:11:46PM +0200, Gabriel C wrote:
> * Am So., 14. Juni 2020 um 22:44 Uhr schrieb Linus Torvalds
> :
>
> Hello,
>
> > So I didn't really expect this, but 5.8 looks to be one of our biggest
> > releases of all time.
> >
>
> I hit a compiler error caused by
* Am So., 14. Juni 2020 um 22:44 Uhr schrieb Linus Torvalds
:
Hello,
> So I didn't really expect this, but 5.8 looks to be one of our biggest
> releases of all time.
>
I hit a compiler error caused by e4160b2e4b02377c67f8ecd05786811598f39acd.
x86/purgatory: Fail the build if purgatory.ro has
On Mon, Jun 15, 2020 at 2:18 PM Shuah Khan wrote:
>
> Yeah. I should have thought about adding module path. With module path
> added, I get better results:
>
> [ 15.341267] ? snd_pcm_hw_params (./include/linux/string.h:391
> /home/shuah/lkml/linux_5.8/sound/core/pcm_native.c:759) snd_pcm
> [
On 6/15/20 2:55 PM, Linus Torvalds wrote:
On Mon, Jun 15, 2020 at 1:41 PM Shuah Khan wrote:
I have CONFIG_DEBUG_INFO enabled. Ran the stack trace through
scripts/decode_stacktrace.sh
Thanks. It looks like it isn't needed and people already know what the cause is.
Also, sadly the stack
On 6/15/20 2:53 PM, Shuah Khan wrote:
On 6/15/20 1:57 PM, Takashi Iwai wrote:
On Mon, 15 Jun 2020 20:48:11 +0200,
Shuah Khan wrote:
I am seeing the following problem on my system. I haven't started debug
yet. Is this a known issue?
Yes, the recent fix by David should paper over it:
On Mon, Jun 15, 2020 at 1:41 PM Shuah Khan wrote:
>
> I have CONFIG_DEBUG_INFO enabled. Ran the stack trace through
> scripts/decode_stacktrace.sh
Thanks. It looks like it isn't needed and people already know what the cause is.
Also, sadly the stack trace decoding didn't end up as useful as it
On 6/15/20 1:57 PM, Takashi Iwai wrote:
On Mon, 15 Jun 2020 20:48:11 +0200,
Shuah Khan wrote:
I am seeing the following problem on my system. I haven't started debug
yet. Is this a known issue?
Yes, the recent fix by David should paper over it:
On 6/15/20 1:48 PM, Linus Torvalds wrote:
On Mon, Jun 15, 2020 at 11:48 AM Shuah Khan wrote:
I am seeing the following problem on my system. I haven't started debug
yet. Is this a known issue?
[9.791309] BUG: unable to handle page fault for address:
b1e78165d000
[9.791328] #PF:
On Mon, 15 Jun 2020 20:48:11 +0200,
Shuah Khan wrote:
>
> I am seeing the following problem on my system. I haven't started debug
> yet. Is this a known issue?
Yes, the recent fix by David should paper over it:
On Mon, Jun 15, 2020 at 11:48 AM Shuah Khan wrote:
>
> I am seeing the following problem on my system. I haven't started debug
> yet. Is this a known issue?
>
> [9.791309] BUG: unable to handle page fault for address:
> b1e78165d000
> [9.791328] #PF: supervisor write access in kernel
On Mon, 15 Jun 2020, Shuah Khan wrote:
> I am seeing the following problem on my system. I haven't started debug
> yet. Is this a known issue?
>
> [9.791309] BUG: unable to handle page fault for address: b1e78165d000
> [9.791328] #PF: supervisor write access in kernel mode
> [
18 matches
Mail list logo
