On Sun, Feb 14, 2021 at 02:45:13PM -0800, Linus Torvalds wrote:
> Nothing unexpected or particularly scary happened this week, so here
> we are - with 5.11 tagged and pushed out.
>
> In fact, it's a smaller-than-average set of commits from rc7 to final,
> which makes me happy. And I already have s
On 14:45 Sun 14 Feb 2021, Linus Torvalds wrote:
Nothing unexpected or particularly scary happened this week, so here
we are - with 5.11 tagged and pushed out.
In fact, it's a smaller-than-average set of commits from rc7 to final,
which makes me happy. And I already have several pull requests lin
On Sun, Feb 07, 2021 at 02:32:37PM -0800, Linus Torvalds wrote:
> So it's the biggest sporting day of the year here in the US, when
> everybody is getting ready to watch the yearly top TV commercials,
> occasionally interrupted by some odd handegg carrying competition that
> I still haven't figured
On 2/7/21 2:32 PM, Linus Torvalds wrote:
> So it's the biggest sporting day of the year here in the US, when
> everybody is getting ready to watch the yearly top TV commercials,
> occasionally interrupted by some odd handegg carrying competition that
> I still haven't figured out the rules for afte
On 14:32 Sun 07 Feb 2021, Linus Torvalds wrote:
and hopefully life goes on with the weekly celebration involving
compiling and testing new kernels instead.
Right?
Yup, that's the standard ritual! Now, time to spin this RC fellow too side by
side :)
~Bhaskar
Linus
---
Ahmed S.
On Thu, Feb 04, 2021 at 10:32:56AM -0800, Linus Torvalds wrote:
> On Thu, Feb 4, 2021 at 10:19 AM Mike Rapoport wrote:
> >
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > >
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don'
On Thu, Feb 4, 2021 at 10:19 AM Mike Rapoport wrote:
>
> On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> >
> > Mike: should we perhaps revert the first patch too (commit
> > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
>
> Unfortunately, I was too optimistic
On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson
> wrote:
>
> Mike: should we perhaps revert the first patch too (commit
> bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
Unfortunately, I was too optimistic and did
On 2/3/21 1:06 PM, Linus Torvalds wrote:
On Wed, Feb 3, 2021 at 11:58 AM Shuah Khan wrote:
ld: arch/x86/built-in.a: member arch/x86/kernel/pci-swiotlb.o in archive
is not an object
make: *** [Makefile:1170: vmlinux] Error 1
That honestly sounds like something went wrong earlier - things like
On 2/3/21 11:58 AM, Shuah Khan wrote:
> I am seeing the following compile error on Linux 5.11-rc6.
> No issues on 5.11.0-rc5 with the same config.
>
> ld: arch/x86/built-in.a: member arch/x86/kernel/pci-swiotlb.o in archive is
> not an object
> make: *** [Makefile:1170: vmlinux] Error 1
>
> CONF
On Wed, Feb 3, 2021 at 11:58 AM Shuah Khan wrote:
>
> ld: arch/x86/built-in.a: member arch/x86/kernel/pci-swiotlb.o in archive
> is not an object
> make: *** [Makefile:1170: vmlinux] Error 1
That honestly sounds like something went wrong earlier - things like
doing a system upgrade in the middle
On Sun, Jan 31, 2021 at 02:01:43PM -0800, Linus Torvalds wrote:
> Things look a little calmer than last week, and over-all very average
> for rc6. So - like always this late in the release schedule - I'd
> certainly have liked things to be even calmer, but nothing here really
> stands out.
>
> The
Hi!
/-/blob/master/kconfig/debug
> > >
> > > Here's a boot dmesg from some affected machines from just before the merge
> > > with rc5:
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/shard-skl1/boot18.txt
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-skl-6600u/boot.htm
On Tue, Jan 26, 2021 at 10:45:10AM -0800, Linus Torvalds wrote:
> On Tue, Jan 26, 2021 at 8:25 AM Mike Rapoport wrote:
> >
> > On Mon, Jan 25, 2021 at 09:46:19PM +, Chris Wilson wrote:
> > >
> > > CI does confirm that the revert of d3921cb8be29 brings the machines back
> > > to life.
> >
> > I
On Tue, Jan 26, 2021 at 8:25 AM Mike Rapoport wrote:
>
> On Mon, Jan 25, 2021 at 09:46:19PM +, Chris Wilson wrote:
> >
> > CI does confirm that the revert of d3921cb8be29 brings the machines back
> > to life.
>
> I still cannot see what could possibly go wrong, so let's revert
> d3921cb8be29 f
On Mon, Jan 25, 2021 at 09:13:59PM +, Chris Wilson wrote:
> Quoting Mike Rapoport (2021-01-25 21:04:56)
> > On Mon, Jan 25, 2021 at 08:34:34PM +, Chris Wilson wrote:
> > > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > > Mike Rapoport (3):
> > > ...
> > > > mm: fix initialization
On Mon, Jan 25, 2021 at 09:46:19PM +, Chris Wilson wrote:
> Quoting Mike Rapoport (2021-01-25 21:33:48)
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > > On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson
> > > wrote:
> > > >
> > > > Quoting Linus Torvalds (2021-01-25 01:06
Quoting Chris Wilson (2021-01-25 21:46:19)
> Quoting Mike Rapoport (2021-01-25 21:33:48)
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
> >
On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson
> wrote:
> >
> > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > Mike Rapoport (3):
> > ...
> > > mm: fix initialization of struct page for holes in memory layout
> >
> > We ha
Quoting Mike Rapoport (2021-01-25 21:33:48)
> On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson
> > wrote:
> > >
> > > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > > Mike Rapoport (3):
> > > ...
> > > > mm: fix initializa
Quoting Mike Rapoport (2021-01-25 21:04:56)
> On Mon, Jan 25, 2021 at 08:34:34PM +, Chris Wilson wrote:
> > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > Mike Rapoport (3):
> > ...
> > > mm: fix initialization of struct page for holes in memory layout
> >
> > We have half a dozen or
On Mon, Jan 25, 2021 at 08:34:34PM +, Chris Wilson wrote:
> Quoting Linus Torvalds (2021-01-25 01:06:40)
> > Mike Rapoport (3):
> ...
> > mm: fix initialization of struct page for holes in memory layout
>
> We have half a dozen or so different machines in CI that are silently
> failing t
On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson wrote:
>
> Quoting Linus Torvalds (2021-01-25 01:06:40)
> > Mike Rapoport (3):
> ...
> > mm: fix initialization of struct page for holes in memory layout
>
> We have half a dozen or so different machines in CI that are silently
> failing to boot,
Quoting Linus Torvalds (2021-01-25 01:06:40)
> Mike Rapoport (3):
...
> mm: fix initialization of struct page for holes in memory layout
We have half a dozen or so different machines in CI that are silently
failing to boot, that we believe is bisected to this patch.
17:56 tsa :
On 20:06 Sun 24 Jan 2021, Guenter Roeck wrote:
On 1/24/21 7:56 PM, Bhaskar Chowdhury wrote:
On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
So this rc looked fairly calm and small, all the way up until today.
In fact, over 40% of
On 1/24/21 7:56 PM, Bhaskar Chowdhury wrote:
> On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
>> On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
>>> So this rc looked fairly calm and small, all the way up until today.
>>>
>>> In fact, over 40% of the non-merge commits came in today,
On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
So this rc looked fairly calm and small, all the way up until today.
In fact, over 40% of the non-merge commits came in today, as people
unloaded their work for the week on me. The end
On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
> So this rc looked fairly calm and small, all the way up until today.
>
> In fact, over 40% of the non-merge commits came in today, as people
> unloaded their work for the week on me. The end result is a slightly
> larger than usual
On 1/18/21 7:35 PM, Paul Zimmerman wrote:
> On Mon, Jan 18, 2021 at 14:35:20 -0800, Guenter Roeck wrote:
>> On Sun, Jan 17, 2021 at 04:56:46PM -0800, Linus Torvalds wrote:
>>> Things continue to look fairly normal for this release: 5.11-rc4 is
>>> solidly average in size, and nothing particularly s
On Mon, Jan 18, 2021 at 14:35:20 -0800, Guenter Roeck wrote:
> On Sun, Jan 17, 2021 at 04:56:46PM -0800, Linus Torvalds wrote:
>> Things continue to look fairly normal for this release: 5.11-rc4 is
>> solidly average in size, and nothing particularly scary stands out.
>>
>> In the diff itself, the
On Sun, Jan 17, 2021 at 04:56:46PM -0800, Linus Torvalds wrote:
> Things continue to look fairly normal for this release: 5.11-rc4 is
> solidly average in size, and nothing particularly scary stands out.
>
> In the diff itself, the new ampere modesetting support shows up fairly
> clearly - it's on
On Sun, Jan 10, 2021 at 02:48:47PM -0800, Linus Torvalds wrote:
[ ... ]
> So please go out and test, and report any issues you find,
Build results:
total: 153 pass: 151 fail: 2
Failed builds:
arm64:allmodconfig
ia64:defconfig
Qemu test results:
total: 430 pass: 428
On Fri, Jan 8, 2021 at 3:12 AM Christopher William Snowhill
wrote:
>
> There appears to be a regression with the filesystem NLS modules. I cannot
> load any of them. They all produce:
>
> modprobe: ERROR: could not insert 'nls_cp437': Invalid argument
>
> The system journal reports:
>
> Jan 08 02
There appears to be a regression with the filesystem NLS modules. I cannot load
any of them. They all produce:
modprobe: ERROR: could not insert 'nls_cp437': Invalid argument
The system journal reports:
Jan 08 02:04:56 mrgency kernel: BPF:No data
Jan 08 02:04:56 mrgency kernel: failed to valida
On Tue, Jan 5, 2021 at 12:57 PM Guenter Roeck wrote:
>
> NP. The test are running automatically anyway, so I figured I might
> as well report the results. Does that make sense, or is it just noise ?
Definitely not noise. I very much like seeing the results.
In fact, even in situations like this,
On Tue, Jan 05, 2021 at 11:55:20AM -0800, Linus Torvalds wrote:
> On Tue, Jan 5, 2021 at 10:46 AM Guenter Roeck wrote:
> >
> > Problems are as already reported against v5.11-rc1.
>
> Yes. Thanks for keeping on top of this, I'm expecting to get the fixes
> as people get back from vacations.
>
NP
On Tue, Jan 5, 2021 at 10:46 AM Guenter Roeck wrote:
>
> Problems are as already reported against v5.11-rc1.
Yes. Thanks for keeping on top of this, I'm expecting to get the fixes
as people get back from vacations.
Linus
On Sun, Jan 03, 2021 at 04:13:08PM -0800, Linus Torvalds wrote:
> Ok, let's be honest - not a lot has happened in the last week or two.
>
> The merge window itself may not have been hugely impacted by the
> holiday season, but that's because all the new code should already
> have been ready before
On Sun, Jan 03, 2021 at 05:45:16PM +, David Laight wrote:
> From: Ilkka Prusi
> > Note that /sbin is now just a symlink to /usr/sbin on Debian since 10
> > (Buster) as per FHS[1][2].
> >
> > [1] https://wiki.linuxfoundation.org/lsb/fhs
> > [2]
> > https://arstechnica.com/information-technolo
From: Ilkka Prusi
> Sent: 02 January 2021 23:27
>
> > PATH for the root on Debian is
> > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> >
>
> Note that /sbin is now just a symlink to /usr/sbin on Debian since 10
> (Buster) as per FHS[1][2].
>
> [1] https://wiki.linuxfoundation.o
From: Bernd Petrovitsch
> Sent: 02 January 2021 11:05
>
> On Sat, 2021-01-02 at 10:13 +0100, Sedat Dilek wrote:
> [...]
> > To be honest I wondered why there were no more reports on this.
>
> Perhaps I'm not the only one who has /sbin and /usr/sbin in the
> $PATH of normal accounts too (and idk w
PATH for the root on Debian is
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Note that /sbin is now just a symlink to /usr/sbin on Debian since 10 (Buster)
as per FHS[1][2].
[1] https://wiki.linuxfoundation.org/lsb/fhs
[2]
https://arstechnica.com/information-technology/2019/09
On Sat, Jan 2, 2021 at 4:51 PM Masahiro Yamada wrote:
>
> On Sat, Jan 2, 2021 at 3:55 AM Sedat Dilek wrote:
> >
> > On Fri, Jan 1, 2021 at 5:14 PM Pavel Machek wrote:
> > >
> > > Hi!
> > > > >
> > > > > > $ dpkg -L kmod | grep bin | grep depmod
> > > > > > /sbin/depmod
> > > > > >
> > > > > > $
> > IMHO users should not need to fix their environment.
> > ( The discussion is a bit obsolete as we now have a fix. )
>
> FWIW, I have no (and don't see any) problems simply appending
> /sbin:/usr/sbin to the $PATH in/for the kernel's scripts.
>
Another workaround is to pass DEPMOD=/path/to/depm
On Sat, 2021-01-02 at 12:26 +0100, Sedat Dilek wrote:
> On Sat, Jan 2, 2021 at 12:05 PM Bernd Petrovitsch
> wrote:
> > On Sat, 2021-01-02 at 10:13 +0100, Sedat Dilek wrote:
> > [...]
> > > To be honest I wondered why there were no more reports on this.
> >
> > Perhaps I'm not the only one who has
On Sat, Jan 2, 2021 at 12:05 PM Bernd Petrovitsch
wrote:
>
> On Sat, 2021-01-02 at 10:13 +0100, Sedat Dilek wrote:
> [...]
> > To be honest I wondered why there were no more reports on this.
>
> Perhaps I'm not the only one who has /sbin and /usr/sbin in the
> $PATH of normal accounts too (and idk
On Sat, 2021-01-02 at 10:13 +0100, Sedat Dilek wrote:
[...]
> To be honest I wondered why there were no more reports on this.
Perhaps I'm not the only one who has /sbin and /usr/sbin in the
$PATH of normal accounts too (and idk what's the default
behaviour of distributions is - my .bashrc "fixes"
On Sat, Jan 2, 2021 at 8:52 AM Masahiro Yamada wrote:
>
> On Sat, Jan 2, 2021 at 3:55 AM Sedat Dilek wrote:
> >
> > On Fri, Jan 1, 2021 at 5:14 PM Pavel Machek wrote:
> > >
> > > Hi!
> > > > >
> > > > > > $ dpkg -L kmod | grep bin | grep depmod
> > > > > > /sbin/depmod
> > > > > >
> > > > > > $
On Sat, Jan 2, 2021 at 3:55 AM Sedat Dilek wrote:
>
> On Fri, Jan 1, 2021 at 5:14 PM Pavel Machek wrote:
> >
> > Hi!
> > > >
> > > > > $ dpkg -L kmod | grep bin | grep depmod
> > > > > /sbin/depmod
> > > > >
> > > > > $ which depmod
> > > > > [ empty ]
> > > > >
> > > > > $ echo $PATH
> > > > > /
On Fri, Jan 1, 2021 at 7:55 PM Sedat Dilek wrote:
>
> On Fri, Jan 1, 2021 at 5:14 PM Pavel Machek wrote:
> >
> > Hi!
> > > >
> > > > > $ dpkg -L kmod | grep bin | grep depmod
> > > > > /sbin/depmod
> > > > >
> > > > > $ which depmod
> > > > > [ empty ]
> > > > >
> > > > > $ echo $PATH
> > > > > /
On Fri, Jan 1, 2021 at 5:14 PM Pavel Machek wrote:
>
> Hi!
> > >
> > > > $ dpkg -L kmod | grep bin | grep depmod
> > > > /sbin/depmod
> > > >
> > > > $ which depmod
> > > > [ empty ]
> > > >
> > > > $ echo $PATH
> > > > /opt/proxychains-ng/bin:/home/dileks/bin:/usr/local/bin:/usr/bin:/bin:/usr/loc
Hi!
> >
> > > $ dpkg -L kmod | grep bin | grep depmod
> > > /sbin/depmod
> > >
> > > $ which depmod
> > > [ empty ]
> > >
> > > $ echo $PATH
> > > /opt/proxychains-ng/bin:/home/dileks/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>
> Ok, I think this is a broken setup that has a sep
On Mon, Dec 28, 2020 at 12:59 PM Linus Torvalds
wrote:
>
> On Mon, Dec 28, 2020 at 7:51 AM Guenter Roeck wrote:
> >
> > Build results:
> > total: 153 pass: 151 fail: 2
>
> Thanks for doing these for the mainline rc's too. I've seen them for
> the stable kernels, but it's lovely to see it
On Mon, Dec 28, 2020 at 12:04 AM Sedat Dilek wrote:
>
> > $ dpkg -L kmod | grep bin | grep depmod
> > /sbin/depmod
> >
> > $ which depmod
> > [ empty ]
> >
> > $ echo $PATH
> > /opt/proxychains-ng/bin:/home/dileks/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
Ok, I think this is a
On Mon, Dec 28, 2020 at 8:40 PM Linus Torvalds
wrote:
>
> On Mon, Dec 28, 2020 at 12:04 AM Sedat Dilek wrote:
> >
> > > $ dpkg -L kmod | grep bin | grep depmod
> > > /sbin/depmod
> > >
> > > $ which depmod
> > > [ empty ]
> > >
> > > $ echo $PATH
> > > /opt/proxychains-ng/bin:/home/dileks/bin:/us
On 12/28/20 11:37 AM, Kalesh Singh wrote:
[ ... ]
>>> parisc: Failed to execute /sbin/init (error -12)
>>>
>>> Caused by: c49dd3401802 ("mm: speedup mremap on 1GB or larger regions")
>>
>> Looks like Kalesh is looking at it.
>>
>> I don't think that was supposed to matter at all on parisc, but
>>
On Mon, Dec 28, 2020 at 7:26 AM Sedat Dilek wrote:
>
> I also tested with LLVM toolchain v11.0.1-rc2 together with passing
> LLVM=1 and LLVM_IAS=1 to my make line.
>
> I had one ERROR:
>
> error: too few operands for instruction in arch/x86/kvm/svm/sev.c
Looks like Paolo already picked up the fix
On Mon, Dec 28, 2020 at 8:45 PM Linus Torvalds
wrote:
>
> On Mon, Dec 28, 2020 at 7:26 AM Sedat Dilek wrote:
> >
> > I also tested with LLVM toolchain v11.0.1-rc2 together with passing
> > LLVM=1 and LLVM_IAS=1 to my make line.
> >
> > I had one ERROR:
> >
> > error: too few operands for instruct
On Mon, Dec 28, 2020 at 7:51 AM Guenter Roeck wrote:
>
> Build results:
> total: 153 pass: 151 fail: 2
Thanks for doing these for the mainline rc's too. I've seen them for
the stable kernels, but it's lovely to see it for rc1.
> ERROR: modpost: "irq_check_status_bit" [drivers/perf/arm_sp
On Sun, Dec 27, 2020 at 04:04:11PM -0800, Linus Torvalds wrote:
> Two weeks have passed, Christmas is over, and so is the merge window.
>
> I want to thank all the maintainers who sent in their pull requests
> early: we all wanted to get things done before the holidays really
> hit, and mostly it
[ Please CC me I am not subscribed to LKML and linux-kbuild ML ]
Hi Linus,
I also tested with LLVM toolchain v11.0.1-rc2 together with passing
LLVM=1 and LLVM_IAS=1 to my make line.
I had one ERROR:
error: too few operands for instruction in arch/x86/kvm/svm/sev.c
The issue was reported in Cla
On Mon, Dec 28, 2020 at 9:04 AM Sedat Dilek wrote:
>
> On Mon, Dec 28, 2020 at 8:30 AM Sedat Dilek wrote:
> >
> > [ Please CC me I am not subscribed to LKML and linux-kbuild ML ]
> >
> > Hi Linus, Hi Mashiro,
> >
> > thanks for the Linux v5.11-rc1 release.
> >
> > With a new release I always do m
On Mon, Dec 28, 2020 at 8:30 AM Sedat Dilek wrote:
>
> [ Please CC me I am not subscribed to LKML and linux-kbuild ML ]
>
> Hi Linus, Hi Mashiro,
>
> thanks for the Linux v5.11-rc1 release.
>
> With a new release I always do my first builds with my distro's
> default compiler and linker (GCC v10.2
[ Please CC me I am not subscribed to LKML and linux-kbuild ML ]
Hi Linus, Hi Mashiro,
thanks for the Linux v5.11-rc1 release.
With a new release I always do my first builds with my distro's
default compiler and linker (GCC v10.2.1 and GNU/ld BFD v2.35.1).
( It's approx. 40% faster than LLVM too
64 matches
Mail list logo
