On Fri, 21 Jul 2023, Matthew Wilcox wrote:
>
> You've misunderstood. Google have decided to subject the entire kernel
> (including obsolete unmaintained filesystems) to stress tests that it's
> never had before. IOW these bugs have been there since the code was
> merged. There's nothing to
On Fri, 21 Jul 2023, Dave Chinner wrote:
> > I suspect that this is one of those catch-22 situations: distros are
> > going to enable every feature under the sun. That doesn't mean that
> > anyone is actually _using_ them these days.
I think the value of filesystem code is not just a question o
On Fri, 6 Aug 2021, Stan Johnson wrote:
> $ egrep '(CONFIG_PPC_KUAP|CONFIG_VMAP_STACK)' .config
> CONFIG_PPC_KUAP=y
> CONFIG_PPC_KUAP_DEBUG=y
> CONFIG_VMAP_STACK=y
> $ strings vmlinux | fgrep "Linux version"
> Linux version 5.13.0-pmac-4-g63e3756d1bd ...
> $ cp vmlinux ../vmlinux-5.13.0-pmac
On Fri, 6 Aug 2021, Christophe Leroy wrote:
>
> I have cooked a tentative fix for that KUAP stuff.
> Could you try the branch 'bugtest' at https://github.com/chleroy/linux.git
>
Thanks, Christophe.
Stan, please test the following build.
$ git remote add chleroy-linux https://github.com/chlero
On Fri, 6 Aug 2021, Christophe Leroy wrote:
> > > > >
> > > > > Can you check if they DO NOT happen at preceding commit c16728835~
> > > > >
> > >
> > > $ git checkout c16728835~
> > > Previous HEAD position was c16728835eec powerpc/32: Manage KUAP in C
> > > HEAD is now at 0b45359aa2df powerpc
On Tue, 3 Aug 2021, Christophe Leroy wrote:
>
> Looks like the memory errors are linked to KUAP (Kernel Userspace Access
> Protection). Based on the places the problems happen, I don't think
> there are any invalid access, so there must be something wrong in the
> KUAP logic, probably linked
On Tue, 3 Aug 2021, Stan Johnson wrote:
>
> I'm not sure of the issue you are referencing. If it's the Wallstreet
> issue, I believe we were waiting to hear back from you regarding the
> memory errors that crop up with CONFIG_VMAP_STACK=y and mem >464M.
> Finn, if that is not correct, please l
On Sun, 27 Jan 2019, John Paul Adrian Glaubitz wrote:
> The last discussion we had was:
>
> Date: Fri, 23 Jan 2015 12:30:56 +1100 (AEDT)
> From: Finn Thain
> To: John Paul Adrian Glaubitz
> Subject: Re: Booting 3.16 on a Powerbook 3400 with CONFIG_BOOTX_TEXT
>
> whe
On Sat, 26 Jan 2019, John Paul Adrian Glaubitz wrote:
>
> The correct mirror is: http://ftp.ports.debian.org
>
> Directory is: debian-ports/
>
> Debian Ports uses different mirrors, you cannot use the standard
> mirrors that you are using when installing a normal Debian release.
>
> A lot of u
On Tue, 8 Jan 2019, Mathieu Malaterre wrote:
> Hi there,
>
> Has anyone tried to remove the annoying boing startup ound on a Mac
> Mini G4 system. I have deleted the macosx partition on this machine.
>
> Thanks,
>
The ROM makes the chime sound to indicate successful POST. There's a
different
On Mon, 23 Dec 2013, Thorsten Glaser wrote:
> Finn Thain dixit:
>
> >Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was
>
> See the discussion in the thread before this message.
I've seen no discussion of this on debian-68k or linux-m68k. What
discussion are
On Mon, 23 Dec 2013, Thorsten Glaser wrote:
> > CONFIG_EARLY_PRINTK=y and CONFIG_SERIAL_PMACZILOG=n
Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was
CONFIG_EARLY_PRINTK disabled?
> I think we need to file bugs in the BTS for each of these instances in
> the future, instead of trying
12 matches
Mail list logo
