Hi there,
On Mon, 09 Mar 2020, Thomas Schmitt wrote:
G.W. Haywood wrote:
> ... I am very happy to post the custom kernel .config as it stands,
> if anyone would like to see it.
I guess some readers would righteously complain if you send ~ 1 lines
here.
I did't mean that I was offering to
Hi,
G.W. Haywood wrote:
> Unfortunately my tweaks to the stock kernel configuration resembled
> wading through the jungle with a machete, and a diff between the stock
> Buster kernel .config and my own .config amounts to 7,173 lines. Most
> of these I am sure are irrelevant to this issue, because
Hi Marco,
Thanks very much for the trouble you have taken in your reply, I do
appreciate it very much.
On Sun, 8 Mar 2020, Marco Möller wrote:
Upgrading your OS could result in the indexed search database to
become rebuild, and this can take a very(!) long time and meanwhile
painfully renderin
Upgrading your OS could result in the indexed search database to become
rebuild, and this can take a very(!) long time and meanwhile painfully
rendering your system almost unresponsive until the database is fully
recreated. I am speaking about days, on old hardware. I have had this,
and diagnos
Hi there,
On Mon, 2 Mar 2020, Greg Wooledge wrote:
On Sat, Feb 29, 2020 at 11:50:09AM +, G.W. Haywood wrote:
> ...There were in fact three instances of Postgres running (9.4, 9.6
> and 11.7) after the two jumps from Jessie to Stretch to Buster...
I don't think this is related to your perfo
On Sat, Feb 29, 2020 at 11:50:09AM +, G.W. Haywood wrote:
> Yesterday more out of desperation than anything I moved the Postgres
> database (mainly the security camera stuff) from Postgres 9.4 to the
> 11.0 instance which Buster installed and started. There were in fact
> three instances of Po
On Du, 01 mar 20, 14:59:49, G.W. Haywood wrote:
>
> If there's any interest I can follow up with any significant findings
> but otherwise I won't spam the list.
In my opinion it would be good to have your findings on a public list to
be found by search engines.
Kind regards,
Andrei
--
http://wi
Hello again all,
For those of you who haven't been watching, here's the problem, er, in
a nutshell:
After a Debian upgrade in two steps from Jessie to Stretch and then
from Stretch to Buster on an old Intel E3815-powered box, performance
was degraded by at least one, and usually more than two or
On Sat, Feb 29, 2020, 7:08 AM Thomas Schmitt wrote:
> Hi,
>
> G.W. Haywood wrote:
> > It's just like the machine is
> > suddenly being powered by an 8080 instead of an E3815...
>
> Lacking any ideas what might be the problem, i'd try Live ISOs of
> Debian 9 and Debian 8 whether their systems show
Hi,
G.W. Haywood wrote:
> It's just like the machine is
> suddenly being powered by an 8080 instead of an E3815...
Lacking any ideas what might be the problem, i'd try Live ISOs of
Debian 9 and Debian 8 whether their systems show the same problem.
Older ISOs are at
https://cdimage.debian.org/m
Hi there,
Thanks Dan and Greg (again), Stefan, Tixy, Thomas, and as before keep
those ideas coming. I'm still baffled but we'll get there. I have to
say that I'm well impressed by the quality of all the responses, and
even where some of the suggestions have been to try things that I've
already
Tixy wrote:
> On Fri, 2020-02-28 at 06:45 -0500, Dan Ritter wrote:
> > Dan Ritter wrote:
> > > Go to /etc/nsswitch.conf
> > >
> > > If these lines look like this
> > >
> > > passwd: compat systemd
> > > group: compat systemd
> > > shadow: compat systemd
> > >
> > > rem
On Fri, 2020-02-28 at 06:45 -0500, Dan Ritter wrote:
> Dan Ritter wrote:
> > Go to /etc/nsswitch.conf
> >
> > If these lines look like this
> >
> > passwd: compat systemd
> > group: compat systemd
> > shadow: compat systemd
> >
> > remove the systemd references.
> >
>
Hello again,
On Fri, 28 Feb 2020, Dan Ritter wrote:
A ridiculously decelerated gzip is evidence of one of the
following:
- CPU throttling
- disk errors
- something interfering with the disk reading or writing
You've probably seen my reply to your first by now, it seems that disc
access probl
Hi there,
Thanks very much for the reply.
On Fri, 28 Feb 2020 Andrei POPESCU wrote:
What Desktop Environment? I believe GNOME is using Wayland by default
and needs hardware acceleration. Try something like LXDE instead.
Sorry, I did mean to mention that but I forgot. It's XFCE, and the
gree
> It would also be good to look after the basics, like running "uptime"
> to check the load average, "top" to see if there are processes running
> amok, "df" to see if a file system is unexpectedly full, and so on.
Yes, I'd recommend running `atop` on both machines during your test to
try and see
On Fri, Feb 28, 2020 at 02:34:19PM +, G.W. Haywood wrote:
> --
> On Thu, 27 Feb 2020, Dan Ritter wrote:
>
> > Go to /etc/nsswitch.conf
> >
> > If these lines look like this
> >
> > passwd: compat systemd
> > group:
Hi there,
Thanks Greg, Dan and Rico for the replies. Keep them coming, I'm
afraid we're not out of the woods yet.
On Thu, Feb 27, 2020 at 03:11:10PM +, G.W. Haywood wrote:
... Jessie to Stretch to Buster ... Immediately, the users started to
complain about performance. Not just a small
Dan Ritter wrote:
> Go to /etc/nsswitch.conf
>
> If these lines look like this
>
> passwd: compat systemd
> group: compat systemd
> shadow: compat systemd
>
> remove the systemd references.
>
> If performance improves immensely immediately after the edit,
> that was th
On Jo, 27 feb 20, 15:11:10, G.W. Haywood wrote:
> Hi there,
>
> Long time Linux user here, very familiar with tools for system
> administration but somewhat stumped by the behaviour of a system
> installed by me about six years ago at a local farm. It's an old
> Intel 'NUC' like this one:
>
> ht
Hi.
On Thu, Feb 27, 2020 at 03:11:10PM +, G.W. Haywood wrote:
> As the box was still running Jessie I had to do the move in two bites.
> First move from Jessie to Stretch, then from Stretch to Buster. The
> entire process was a bit long-winded and spread over a couple of days,
> but s
G.W. Haywood wrote:
>
> As the box was still running Jessie I had to do the move in two bites.
> First move from Jessie to Stretch, then from Stretch to Buster. The
> entire process was a bit long-winded and spread over a couple of days,
> but seemed to go smoothly enough. Immediately, the user
Hi there,
Long time Linux user here, very familiar with tools for system
administration but somewhat stumped by the behaviour of a system
installed by me about six years ago at a local farm. It's an old
Intel 'NUC' like this one:
https://ark.intel.com/content/www/us/en/ark/products/78577/intel-
On Thu, Feb 27, 2020 at 03:11:10PM +, G.W. Haywood wrote:
> As the box was still running Jessie I had to do the move in two bites.
> First move from Jessie to Stretch, then from Stretch to Buster.
OK.
> but seemed to go smoothly enough. Immediately, the users started to
> complain about perf
24 matches
Mail list logo
