Request for explanation of error message

classic Classic list List threaded Threaded
74 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Bret Busby <[hidden email]> wrote:

> On 29/07/2019, Bret Busby <[hidden email]> wrote:
>> On 29/07/2019, Bret Busby <[hidden email]> wrote:
>>> On 29/07/2019, Paul Smith <[hidden email]> wrote:
>>>> On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
>>>>> > The first one is simple enough.  It might have been because your
>>>>> > disk
>>>>> > is full, in which case it's a symptom not a cause.  What are the
>>>>> > permissions on these files?  Run this command:
>>>>> >
>>>>> >    ls -ald /tmp /tmp/.tX0-lock
>>>>> >
>>>>> > and let us know the results.
>>>>>
>>>>> "
>>>>> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
>>>>> ls: cannot access '/tmp/.tX0-lock': No such file or directory
>>>>> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
>>>>
>>>> This looks correct.  That most likely means that this error is a
>>>> symptom of your disk being full, and not the cause of the problem.
>>>>
>>>> After you have cleared out space on your disk, please keep an eye on
>>>> the size of the /var/log/lightdm/x-0.log file.  If it continues to
>>>> grow, send along the last 50 or so lines of output from that file and
>>>> we'll see what it has to say.
>>>>
>>>
>>> I have posted a message, that is awaiting moderation - a few kB too
>>> large.
>>>
>>> If you look at this output;
>>>
>>> "
>>> bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>>>
>>> X.Org X Server 1.19.6
>>> Release Date: 2017-12-20
>>> X Protocol Version 11, Revision 0
>>> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
>>> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
>>> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
>>> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
>>> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
>>> vt.handoff=1
>>> Build Date: 03 June 2019  08:10:35AM
>>> xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
>>> http://www.ubuntu.com/support)
>>> Current version of pixman: 0.34.0
>>> Before reporting problems, check http://wiki.x.org
>>> to make sure that you have the latest version.
>>> Markers: (--) probed, (**) from config file, (==) default setting,
>>> (++) from command line, (!!) notice, (II) informational,
>>> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>>> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
>>> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>>> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>>> _XSERVTransSocketUNIXAccept: accept() failed
>>> _XSERVTransSocketUNIXAccept: accept() failed
>>> _XSERVTransSocketUNIXAccept: accept() failed
>>> _XSERVTransSocketUNIXAccept: accept() failed
>>> _XSERVTransSocketUNIXAccept: accept() failed
>>> _XSERVTransSocketUNIXAccept: accept() failed
>>> _XSERVTransSocketUNIXAccept: accept() failed
>>> "
>>>
>>> that last line is an endless loop.
>>>
>>>> Also, you did show you're using an 18.04.2 based system, but if you're
>>>> using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
>>>> the output of the "lsb_release -a" command which would tell us (I
>>>> think) if you're using a spin or similar.
>>>>
>>>> What distribution did you actually install here?
>>>>
>>>
>>> I had posted the output, in response to a previous post by Ralf;
>>>
>>> "
>>> bret@bret-MD34045-2521:~$ lsb_release -a
>>> No LSB modules are available.
>>> Distributor ID: Ubuntu
>>> Description:    Ubuntu 18.04.2 LTS
>>> Release:        18.04
>>> Codename:       bionic
>>> "
>>>
>>> It is UbuntuMATE - I believe that had posted that way much earlier in
>>> the thread.
>>>
>>> Also,
>>>
>>> "
>>> "
>>> uname -v
>>> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
>>> bret@bret-MD34045-2521:~$ uname -a
>>> Linux bret-MD34045-2521 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
>>> 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>>> "
>>> "
>>>
>>> Now, I need to see what I can do before the log file crashes my system
>>> again.
>>>
>>> I think that a defect exists in the creating of the log -file -
>>> whatever is inputting to the log file should not be in an endless
>>> loop. It ism destructive.
>>>
>>
>> "
>> bret@bret-MD34045-2521:~$ sudo ls -l /var/log/lightdm/x-0.log
>> -rw------- 1 root root 130020644 Jul 29 04:53 /var/log/lightdm/x-0.log
>> "
>>
>
> "
> bret@bret-MD34045-2521:~$ sudo ls -l /var/log/lightdm/x-0.log
> -rw------- 1 root root 130020644 Jul 29 04:53 /var/log/lightdm/x-0.log
> bret@bret-MD34045-2521:~$ sudo rm  /var/log/lightdm/x-0.log
> bret@bret-MD34045-2521:~$ sudo ls -l /var/log/lightdm/x-0.log
> ls: cannot access '/var/log/lightdm/x-0.log': No such file or directory
> '
>


Well, running the rm command on the file, appears to have temporarily
stopped the attack on my system.

The file is still there, somewhere - hidden from the administrator
role, as the reduced free space is still reduced; it is just that the
reducing appears to have been temporarily stopped. Until the software
finds a way around it.

--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
In reply to this post by Bret Busby-2
On Mon, Jul 29, 2019 at 05:06:16AM +0800, Bret Busby wrote:

> On 29/07/2019, Paul Smith <[hidden email]> wrote:
> > On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
> >> > The first one is simple enough.  It might have been because your disk
> >> > is full, in which case it's a symptom not a cause.  What are the
> >> > permissions on these files?  Run this command:
> >> >
> >> >    ls -ald /tmp /tmp/.tX0-lock
> >> >
> >> > and let us know the results.
> >>
> >> "
> >> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
> >> ls: cannot access '/tmp/.tX0-lock': No such file or directory
> >> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
> >
> > This looks correct.  That most likely means that this error is a
> > symptom of your disk being full, and not the cause of the problem.
> >
> > After you have cleared out space on your disk, please keep an eye on
> > the size of the /var/log/lightdm/x-0.log file.  If it continues to
> > grow, send along the last 50 or so lines of output from that file and
> > we'll see what it has to say.
> >
>
> I have posted a message, that is awaiting moderation - a few kB too large.
>
> If you look at this output;
>
> "
> bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>
> X.Org X Server 1.19.6
> Release Date: 2017-12-20
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
> vt.handoff=1
> Build Date: 03 June 2019  08:10:35AM
> xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
> http://www.ubuntu.com/support)
> Current version of pixman: 0.34.0
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> "
>
> that last line is an endless loop.

If googling the IOPL error did not work  there is stuff like this too,

http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html

you could lsof and grep for the process, check what it has open,  or just make the changes and see what happens.

I guess you could itry  " ps ax -f | grep lightdm " and see if it is root or has the right user for any needed  permissions.


I guess it managed to write a few lines before even with "no" disk space :)




>
> > Also, you did show you're using an 18.04.2 based system, but if you're
> > using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
> > the output of the "lsb_release -a" command which would tell us (I
> > think) if you're using a spin or similar.
> >
> > What distribution did you actually install here?
> >
>
> I had posted the output, in response to a previous post by Ralf;
>
> "
> bret@bret-MD34045-2521:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:    Ubuntu 18.04.2 LTS
> Release:        18.04
> Codename:       bionic
> "
>
> It is UbuntuMATE - I believe that had posted that way much earlier in
> the thread.
>
> Also,
>
> "
> "
> uname -v
> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
> bret@bret-MD34045-2521:~$ uname -a
> Linux bret-MD34045-2521 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
> 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> "
> "
>
> Now, I need to see what I can do before the log file crashes my system again.
>
> I think that a defect exists in the creating of the log -file -
> whatever is inputting to the log file should not be in an endless
> loop. It ism destructive.
>
> >
> > --
> > ubuntu-users mailing list
> > [hidden email]
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> >
>
>
> --
> Bret Busby
> Armadale
> West Australia
> ..............
>
> "So once you do know what the question actually is,
>  you'll know what the answer means."
> - Deep Thought,
>  Chapter 28 of Book 1 of
>  "The Hitchhiker's Guide to the Galaxy:
>  A Trilogy In Four Parts",
>  written by Douglas Adams,
>  published by Pan Books, 1992
>
> ....................................................
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Mon, Jul 29, 2019 at 05:06:16AM +0800, Bret Busby wrote:
>> On 29/07/2019, Paul Smith <[hidden email]> wrote:
>> > On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
>> >> > The first one is simple enough.  It might have been because your disk
>> >> > is full, in which case it's a symptom not a cause.  What are the
>> >> > permissions on these files?  Run this command:
>> >> >
>> >> >    ls -ald /tmp /tmp/.tX0-lock
>> >> >
>> >> > and let us know the results.
>> >>
>> >> "
>> >> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
>> >> ls: cannot access '/tmp/.tX0-lock': No such file or directory
>> >> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
>> >
>> > This looks correct.  That most likely means that this error is a
>> > symptom of your disk being full, and not the cause of the problem.
>> >
>> > After you have cleared out space on your disk, please keep an eye on
>> > the size of the /var/log/lightdm/x-0.log file.  If it continues to
>> > grow, send along the last 50 or so lines of output from that file and
>> > we'll see what it has to say.
>> >
>>
>> I have posted a message, that is awaiting moderation - a few kB too large.
>>
>> If you look at this output;
>>
>> "
>> bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>>
>> X.Org X Server 1.19.6
>> Release Date: 2017-12-20
>> X Protocol Version 11, Revision 0
>> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
>> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
>> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
>> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
>> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
>> vt.handoff=1
>> Build Date: 03 June 2019  08:10:35AM
>> xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
>> http://www.ubuntu.com/support)
>> Current version of pixman: 0.34.0
>> Before reporting problems, check http://wiki.x.org
>> to make sure that you have the latest version.
>> Markers: (--) probed, (**) from config file, (==) default setting,
>> (++) from command line, (!!) notice, (II) informational,
>> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
>> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> "
>>
>> that last line is an endless loop.
>
> If googling the IOPL error did not work  there is stuff like this too,
>
> http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
>
> you could lsof and grep for the process, check what it has open,  or just
> make the changes and see what happens.
>

At
http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
is

"
Thanks to #openbsd's epony and oldlaptop, the resolution is to:

1. increase daemon openfiles-max to 2048 and openfiles-cur to 1024 in
/etc/login.conf
2. cap_mkdb /etc/login.conf
3. re-login.

Thanks
"

However, ...

"
bret@bret-MD34045-2521:~$ sudo cat /etc/login.conf
[sudo] password for bret:
cat: /etc/login.conf: No such file or directory

"


> I guess you could itry  " ps ax -f | grep lightdm " and see if it is root or
> has the right user for any needed  permissions.
>

"
bret@bret-MD34045-2521:~$ ps ax -f | grep lightdm
root      1256     1  0 03:29 ?        SLsl   0:00 /usr/sbin/lightdm
root      1269  1256  2 03:29 tty7     Ssl+   3:34 /usr/lib/xorg/Xorg
-core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
-novtswitch
root      1458  1256  0 03:29 ?        Sl     0:00 lightdm --session-child 13 20
bret     15899  5719  0 06:07 pts/0    S+     0:00 grep --color=auto lightdm
bret@bret-MD34045-2521:~$
"

I do not understand the output.


>
> I guess it managed to write a few lines before even with "no" disk space :)
>

No - the file was only about 130MB - that was created after the reboot.

Now, about an hour after running the rm command against the file, the
software still has not found a way to get around it, and I have not
yet lost any more free space.

--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
On Mon, Jul 29, 2019 at 06:12:15AM +0800, Bret Busby wrote:

> On 29/07/2019, Mike Marchywka <[hidden email]> wrote:
> > On Mon, Jul 29, 2019 at 05:06:16AM +0800, Bret Busby wrote:
> >> On 29/07/2019, Paul Smith <[hidden email]> wrote:
> >> > On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
> >> >> > The first one is simple enough.  It might have been because your disk
> >> >> > is full, in which case it's a symptom not a cause.  What are the
> >> >> > permissions on these files?  Run this command:
> >> >> >
> >> >> >    ls -ald /tmp /tmp/.tX0-lock
> >> >> >
> >> >> > and let us know the results.
> >> >>
> >> >> "
> >> >> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
> >> >> ls: cannot access '/tmp/.tX0-lock': No such file or directory
> >> >> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
> >> >
> >> > This looks correct.  That most likely means that this error is a
> >> > symptom of your disk being full, and not the cause of the problem.
> >> >
> >> > After you have cleared out space on your disk, please keep an eye on
> >> > the size of the /var/log/lightdm/x-0.log file.  If it continues to
> >> > grow, send along the last 50 or so lines of output from that file and
> >> > we'll see what it has to say.
> >> >
> >>
> >> I have posted a message, that is awaiting moderation - a few kB too large.
> >>
> >> If you look at this output;
> >>
> >> "
> >> bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
> >>
> >> X.Org X Server 1.19.6
> >> Release Date: 2017-12-20
> >> X Protocol Version 11, Revision 0
> >> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
> >> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
> >> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
> >> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> >> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
> >> vt.handoff=1
> >> Build Date: 03 June 2019  08:10:35AM
> >> xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
> >> http://www.ubuntu.com/support)
> >> Current version of pixman: 0.34.0
> >> Before reporting problems, check http://wiki.x.org
> >> to make sure that you have the latest version.
> >> Markers: (--) probed, (**) from config file, (==) default setting,
> >> (++) from command line, (!!) notice, (II) informational,
> >> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> >> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
> >> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> >> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> >> _XSERVTransSocketUNIXAccept: accept() failed
> >> _XSERVTransSocketUNIXAccept: accept() failed
> >> _XSERVTransSocketUNIXAccept: accept() failed
> >> _XSERVTransSocketUNIXAccept: accept() failed
> >> _XSERVTransSocketUNIXAccept: accept() failed
> >> _XSERVTransSocketUNIXAccept: accept() failed
> >> _XSERVTransSocketUNIXAccept: accept() failed
> >> "
> >>
> >> that last line is an endless loop.
> >
> > If googling the IOPL error did not work  there is stuff like this too,
> >
> > http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
> >
> > you could lsof and grep for the process, check what it has open,  or just
> > make the changes and see what happens.
> >
>
> At
> http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
> is
>
> "
> Thanks to #openbsd's epony and oldlaptop, the resolution is to:
>
> 1. increase daemon openfiles-max to 2048 and openfiles-cur to 1024 in
> /etc/login.conf
> 2. cap_mkdb /etc/login.conf
> 3. re-login.
>
> Thanks
> "
>
> However, ...
>
> "
> bret@bret-MD34045-2521:~$ sudo cat /etc/login.conf
> [sudo] password for bret:
> cat: /etc/login.conf: No such file or directory
>
> "
>
>
> > I guess you could itry  " ps ax -f | grep lightdm " and see if it is root or
> > has the right user for any needed  permissions.
> >
>
> "
> bret@bret-MD34045-2521:~$ ps ax -f | grep lightdm
> root      1256     1  0 03:29 ?        SLsl   0:00 /usr/sbin/lightdm
> root      1269  1256  2 03:29 tty7     Ssl+   3:34 /usr/lib/xorg/Xorg
> -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
> -novtswitch
> root      1458  1256  0 03:29 ?        Sl     0:00 lightdm --session-child 13 20
> bret     15899  5719  0 06:07 pts/0    S+     0:00 grep --color=auto lightdm
> bret@bret-MD34045-2521:~$
> "
>
> I do not understand the output.

Well, it is running as root. If googling did not work, you could see if
it managed to open anything. For example,

sudo netstat -anp | grep lightdm
unix  3      [ ]         STREAM     CONNECTED     24081    1191/lightdm        
unix  2      [ ]         DGRAM                    28837    1332/lightdm        
unix  3      [ ]         STREAM     CONNECTED     27936    1191/lightdm        
unix  3      [ ]         STREAM     CONNECTED     24319    1332/lightdm        
unix  3      [ ]         STREAM     CONNECTED     26915    1191/lightdm        


with or without the wc,

sudo lsof | grep lightdm  | wc


There are only two error messages...

I guess I'd still start in single user mode, try to start it by hand.

/usr/sbin/lightdm

or try to start X by hand and see what happens.
I was just through this with openbox trying to get 'Beaver to run
on old emachines. There were a bunch of little things I think playing
with xinit or something similar. It finally ran but can't remember
what happened.  


>
>
> >
> > I guess it managed to write a few lines before even with "no" disk space :)
> >
>
> No - the file was only about 130MB - that was created after the reboot.
>
> Now, about an hour after running the rm command against the file, the
> software still has not found a way to get around it, and I have not
> yet lost any more free space.
>
> --
> Bret Busby
> Armadale
> West Australia
> ..............
>
> "So once you do know what the question actually is,
>  you'll know what the answer means."
> - Deep Thought,
>  Chapter 28 of Book 1 of
>  "The Hitchhiker's Guide to the Galaxy:
>  A Trilogy In Four Parts",
>  written by Douglas Adams,
>  published by Pan Books, 1992
>
> ....................................................
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Robert Heller
In reply to this post by Bret Busby-2
At Mon, 29 Jul 2019 02:51:44 +0800 "Ubuntu user technical support,  not for general discussions" <[hidden email]> wrote:

>
> On 29/07/2019, Mike Marchywka <[hidden email]> wrote:
> > On Mon, Jul 29, 2019 at 01:01:03AM +0800, Bret Busby wrote:
> >> And, as I got a no free space warning, although I can't find where
> >> there is no free space, apart from the snap (?) area,
> >>
> >> "
> >> bret@bret-MD34045-2521:~$ df -h
> >> Filesystem      Size  Used Avail Use% Mounted on
> >> udev             16G     0   16G   0% /dev
> >> tmpfs           3.2G  1.6M  3.2G   1% /run
> >> /dev/sda7        92G   58G   30G  67% /
> >> tmpfs            16G  469M   16G   3% /dev/shm
> >> tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> >> tmpfs            16G     0   16G   0% /sys/fs/cgroup
> >> /dev/loop0      128K  128K     0 100% /snap/software-boutique/39
> >> /dev/loop1      8.0M  8.0M     0 100% /snap/pulsemixer/23
> >> /dev/loop7       88M   88M     0 100% /snap/core/5328
> >> /dev/loop2      161M  161M     0 100% /snap/midori/451
> >> /dev/loop3       72M   72M     0 100% /snap/software-boutique/31
> >> /dev/loop4       87M   87M     0 100% /snap/ubuntu-mate-welcome/335
> >> /dev/loop5       89M   89M     0 100% /snap/core/7270
> >> /dev/loop8      8.0M  8.0M     0 100% /snap/pulsemixer/250
> >> /dev/loop6       88M   88M     0 100% /snap/ubuntu-mate-welcome/199
> >> /dev/sda1        96M   31M   66M  32% /boot/efi
> >> /dev/sda8        92G   63G   25G  73% /home
> >> tmpfs           3.2G   64K  3.2G   1% /run/user/1000
> >> /dev/sda9        92G   61M   87G   1% /media/bret/Data1
> >> /dev/sda10       92G   61M   87G   1% /media/bret/Data2
> >> "
> >>
> >>
> >> so I looked in the /var area, I noticed that the 48GB log file has
> >> much smaller zipped predecessors;
> >
> > This is probably log rotate. From the sizes, absent some activity you know
> > about,
> > things probably went bad between 16th and 22nd and then escalated.
> >
> >>
> >> "
> >> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
> >> -rw------- 1 root root 48233766147 Jul 28 02:49 /var/log/lightdm/x-0.log
> >> -rw------- 1 root root     9770700 Jul 23 03:45
> >> /var/log/lightdm/x-0.log.3.gz
> >> -rw------- 1 root root    26392833 Jul 22 23:42
> >> /var/log/lightdm/x-0.log.4.gz
> >> -rw------- 1 root root         768 Jul 16 20:13
> >> /var/log/lightdm/x-0.log.5.gz
> >> -rw------- 1 root root         784 Jul 15 16:42
> >> /var/log/lightdm/x-0.log.6.gz
> >> -rw------- 1 root root         144 Jul 14 21:33
> >> /var/log/lightdm/x-0.log.7.gz
> >> -rw------- 1 root root         100 Jul 13 01:14
> >> /var/log/lightdm/x-0.log.8.gz
> >> "
> >>
> >> Weirdness abounds.
> >>
> >> I note that, in the /var/log/lightdm directory, the other log files
> >> have log1.gz and log2.gz , but, that one does not;
> >>
> >> "
> >> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/
> >> total 47138780
> >> -rw------- 1 root root           0 Jul 28 02:53 lightdm.log
> >> -rw------- 1 root root        2822 Jul 28 02:50 lightdm.log.1.gz
> >> -rw------- 1 root root        2130 Jul 23 03:46 lightdm.log.2.gz
> >> -rw------- 1 root root         121 Jul 22 23:42 lightdm.log.3.gz
> >> -rw------- 1 root root        2252 Jul 16 20:13 lightdm.log.4.gz
> >> -rw------- 1 root root        1747 Jul 15 16:43 lightdm.log.5.gz
> >> -rw------- 1 root root        1691 Jul  7 01:09 lightdm.log.6.gz
> >> -rw------- 1 root root        1673 Jul  6 23:23 lightdm.log.7.gz
> >> -rw------- 1 root root           0 Jul 28 02:53 seat0-greeter.log
> >> -rw------- 1 root root        2294 Jul 28 02:50 seat0-greeter.log.1.gz
> >> -rw------- 1 root root        1912 Jul 23 03:46 seat0-greeter.log.2.gz
> >> -rw------- 1 root root        1934 Jul 16 20:13 seat0-greeter.log.3.gz
> >> -rw------- 1 root root        1459 Jul 15 16:43 seat0-greeter.log.4.gz
> >> -rw------- 1 root root        1501 Jul  7 01:09 seat0-greeter.log.5.gz
> >> -rw------- 1 root root        1432 Jul  6 23:23 seat0-greeter.log.6.gz
> >> -rw------- 1 root root        1429 Jul  6 23:33 seat0-greeter.log.7.gz
> >> -rw------- 1 root root 48233766147 Jul 28 02:49 x-0.log
> >> -rw------- 1 root root     9770700 Jul 23 03:45 x-0.log.3.gz
> >> -rw------- 1 root root    26392833 Jul 22 23:42 x-0.log.4.gz
> >> -rw------- 1 root root         768 Jul 16 20:13 x-0.log.5.gz
> >> -rw------- 1 root root         784 Jul 15 16:42 x-0.log.6.gz
> >> -rw------- 1 root root         144 Jul 14 21:33 x-0.log.7.gz
> >> -rw------- 1 root root         100 Jul 13 01:14 x-0.log.8.gz
> >> "
> >>
> >> So, I am assuming that that file corrupted, on or about 23 July, or,
> >> whatever automatically compacts and archives it, and, starts a new log
> >> file, failed, at about that time.
> >
> > Again, that is probably logrotate but the easiest thing to do is look at the
> > last few lines
> > in any of the larger files and find similar lines farther up to establish a
> > period of
> > error messages ( while they could all be unrelated as if being attacked
> > likely it is in an
> > infinite loop trying to get something restarted ). Once you have a full
> > period it
> > may be obvious what the problem is. Alternative, if you unzip the
> > x-0.log.4.gz file to the
> > console and just "more" it probably a few lines in you will see whatver
> > started it
> > as the earlier gzip files are quite small.
> >
> > If you boot in single user mode and have the console messages pop up, you
> > may
> > be able to execute some of the failed steps by hand and see if it triggers
> > any error messages.
> >
>
> Whatever is happeing, I now have
>
> "
> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
> -rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
> "
>
> and no space left on the / partition.
>
> So, whatever is happening, the file, as it stands, has to be deleted,
> as it has rendered the system unusable.

Lets see the tail first.  Deleting it won't free any disk space until you
reboot.

>

--
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
[hidden email]       -- Webhosting Services
                       

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Robert Heller
In reply to this post by Bret Busby-2
At Mon, 29 Jul 2019 03:19:48 +0800 "Ubuntu user technical support,  not for general discussions" <[hidden email]> wrote:

>
> On 29/07/2019, Bret Busby <[hidden email]> wrote:
> > On 29/07/2019, Mike Marchywka <[hidden email]> wrote:
> >> On Mon, Jul 29, 2019 at 01:01:03AM +0800, Bret Busby wrote:
> >>> And, as I got a no free space warning, although I can't find where
> >>> there is no free space, apart from the snap (?) area,
> >>>
> >>> "
> >>> bret@bret-MD34045-2521:~$ df -h
> >>> Filesystem      Size  Used Avail Use% Mounted on
> >>> udev             16G     0   16G   0% /dev
> >>> tmpfs           3.2G  1.6M  3.2G   1% /run
> >>> /dev/sda7        92G   58G   30G  67% /
> >>> tmpfs            16G  469M   16G   3% /dev/shm
> >>> tmpfs           5.0M  4.0K  5.0M   1% /run/lock
> >>> tmpfs            16G     0   16G   0% /sys/fs/cgroup
> >>> /dev/loop0      128K  128K     0 100% /snap/software-boutique/39
> >>> /dev/loop1      8.0M  8.0M     0 100% /snap/pulsemixer/23
> >>> /dev/loop7       88M   88M     0 100% /snap/core/5328
> >>> /dev/loop2      161M  161M     0 100% /snap/midori/451
> >>> /dev/loop3       72M   72M     0 100% /snap/software-boutique/31
> >>> /dev/loop4       87M   87M     0 100% /snap/ubuntu-mate-welcome/335
> >>> /dev/loop5       89M   89M     0 100% /snap/core/7270
> >>> /dev/loop8      8.0M  8.0M     0 100% /snap/pulsemixer/250
> >>> /dev/loop6       88M   88M     0 100% /snap/ubuntu-mate-welcome/199
> >>> /dev/sda1        96M   31M   66M  32% /boot/efi
> >>> /dev/sda8        92G   63G   25G  73% /home
> >>> tmpfs           3.2G   64K  3.2G   1% /run/user/1000
> >>> /dev/sda9        92G   61M   87G   1% /media/bret/Data1
> >>> /dev/sda10       92G   61M   87G   1% /media/bret/Data2
> >>> "
> >>>
> >>>
> >>> so I looked in the /var area, I noticed that the 48GB log file has
> >>> much smaller zipped predecessors;
> >>
> >> This is probably log rotate. From the sizes, absent some activity you
> >> know
> >> about,
> >> things probably went bad between 16th and 22nd and then escalated.
> >>
> >>>
> >>> "
> >>> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
> >>> -rw------- 1 root root 48233766147 Jul 28 02:49 /var/log/lightdm/x-0.log
> >>> -rw------- 1 root root     9770700 Jul 23 03:45
> >>> /var/log/lightdm/x-0.log.3.gz
> >>> -rw------- 1 root root    26392833 Jul 22 23:42
> >>> /var/log/lightdm/x-0.log.4.gz
> >>> -rw------- 1 root root         768 Jul 16 20:13
> >>> /var/log/lightdm/x-0.log.5.gz
> >>> -rw------- 1 root root         784 Jul 15 16:42
> >>> /var/log/lightdm/x-0.log.6.gz
> >>> -rw------- 1 root root         144 Jul 14 21:33
> >>> /var/log/lightdm/x-0.log.7.gz
> >>> -rw------- 1 root root         100 Jul 13 01:14
> >>> /var/log/lightdm/x-0.log.8.gz
> >>> "
> >>>
> >>> Weirdness abounds.
> >>>
> >>> I note that, in the /var/log/lightdm directory, the other log files
> >>> have log1.gz and log2.gz , but, that one does not;
> >>>
> >>> "
> >>> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/
> >>> total 47138780
> >>> -rw------- 1 root root           0 Jul 28 02:53 lightdm.log
> >>> -rw------- 1 root root        2822 Jul 28 02:50 lightdm.log.1.gz
> >>> -rw------- 1 root root        2130 Jul 23 03:46 lightdm.log.2.gz
> >>> -rw------- 1 root root         121 Jul 22 23:42 lightdm.log.3.gz
> >>> -rw------- 1 root root        2252 Jul 16 20:13 lightdm.log.4.gz
> >>> -rw------- 1 root root        1747 Jul 15 16:43 lightdm.log.5.gz
> >>> -rw------- 1 root root        1691 Jul  7 01:09 lightdm.log.6.gz
> >>> -rw------- 1 root root        1673 Jul  6 23:23 lightdm.log.7.gz
> >>> -rw------- 1 root root           0 Jul 28 02:53 seat0-greeter.log
> >>> -rw------- 1 root root        2294 Jul 28 02:50 seat0-greeter.log.1.gz
> >>> -rw------- 1 root root        1912 Jul 23 03:46 seat0-greeter.log.2.gz
> >>> -rw------- 1 root root        1934 Jul 16 20:13 seat0-greeter.log.3.gz
> >>> -rw------- 1 root root        1459 Jul 15 16:43 seat0-greeter.log.4.gz
> >>> -rw------- 1 root root        1501 Jul  7 01:09 seat0-greeter.log.5.gz
> >>> -rw------- 1 root root        1432 Jul  6 23:23 seat0-greeter.log.6.gz
> >>> -rw------- 1 root root        1429 Jul  6 23:33 seat0-greeter.log.7.gz
> >>> -rw------- 1 root root 48233766147 Jul 28 02:49 x-0.log
> >>> -rw------- 1 root root     9770700 Jul 23 03:45 x-0.log.3.gz
> >>> -rw------- 1 root root    26392833 Jul 22 23:42 x-0.log.4.gz
> >>> -rw------- 1 root root         768 Jul 16 20:13 x-0.log.5.gz
> >>> -rw------- 1 root root         784 Jul 15 16:42 x-0.log.6.gz
> >>> -rw------- 1 root root         144 Jul 14 21:33 x-0.log.7.gz
> >>> -rw------- 1 root root         100 Jul 13 01:14 x-0.log.8.gz
> >>> "
> >>>
> >>> So, I am assuming that that file corrupted, on or about 23 July, or,
> >>> whatever automatically compacts and archives it, and, starts a new log
> >>> file, failed, at about that time.
> >>
> >> Again, that is probably logrotate but the easiest thing to do is look at
> >> the
> >> last few lines
> >> in any of the larger files and find similar lines farther up to establish
> >> a
> >> period of
> >> error messages ( while they could all be unrelated as if being attacked
> >> likely it is in an
> >> infinite loop trying to get something restarted ). Once you have a full
> >> period it
> >> may be obvious what the problem is. Alternative, if you unzip the
> >> x-0.log.4.gz file to the
> >> console and just "more" it probably a few lines in you will see whatver
> >> started it
> >> as the earlier gzip files are quite small.
> >>
> >> If you boot in single user mode and have the console messages pop up, you
> >> may
> >> be able to execute some of the failed steps by hand and see if it
> >> triggers
> >> any error messages.
> >>
> >
> > Whatever is happeing, I now have
> >
> > "
> > bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
> > -rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
> > "
> >
> > and no space left on the / partition.
> >
> > So, whatever is happening, the file, as it stands, has to be deleted,
> > as it has rendered the system unusable.
> >
>
>
> And, after having run
> sudo rm /var/log/lightdm/x-0.log
> whilst the file no longer shows as being present, the space has not
> been freed; still no free space in the / partition.

It won't be freed until the file is *closed*, and that won't happen
until lightdm dies or is killed.  You can *try* sudo kill -HUP <lightdm's
PID>, or reboot the system.

>
> In going through the folders displayed by caja, in the / partition, I
> note that proc shows as having about 875,000 items, "totalling 140.7TB
> (0 bytes on disk)" (magic?).
>
> The size of the HDD is 1TB.
>
> /root and /lost+found are both unreadable when I try to find their
> Properties, and, I can't find the deleted file anywhere else, to free
> up its space, to provide free space in the / partition.
>

Reboot the system.

>

--
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
[hidden email]       -- Webhosting Services
                                         

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Mike Marchywka
On 29/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Mon, Jul 29, 2019 at 06:12:15AM +0800, Bret Busby wrote:
>> On 29/07/2019, Mike Marchywka <[hidden email]> wrote:
>> > On Mon, Jul 29, 2019 at 05:06:16AM +0800, Bret Busby wrote:
>> >> On 29/07/2019, Paul Smith <[hidden email]> wrote:
>> >> > On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
>> >> >> > The first one is simple enough.  It might have been because your
>> >> >> > disk
>> >> >> > is full, in which case it's a symptom not a cause.  What are the
>> >> >> > permissions on these files?  Run this command:
>> >> >> >
>> >> >> >    ls -ald /tmp /tmp/.tX0-lock
>> >> >> >
>> >> >> > and let us know the results.
>> >> >>
>> >> >> "
>> >> >> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
>> >> >> ls: cannot access '/tmp/.tX0-lock': No such file or directory
>> >> >> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
>> >> >
>> >> > This looks correct.  That most likely means that this error is a
>> >> > symptom of your disk being full, and not the cause of the problem.
>> >> >
>> >> > After you have cleared out space on your disk, please keep an eye on
>> >> > the size of the /var/log/lightdm/x-0.log file.  If it continues to
>> >> > grow, send along the last 50 or so lines of output from that file and
>> >> > we'll see what it has to say.
>> >> >
>> >>
>> >> I have posted a message, that is awaiting moderation - a few kB too
>> >> large.
>> >>
>> >> If you look at this output;
>> >>
>> >> "
>> >> bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>> >>
>> >> X.Org X Server 1.19.6
>> >> Release Date: 2017-12-20
>> >> X Protocol Version 11, Revision 0
>> >> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
>> >> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
>> >> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
>> >> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
>> >> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
>> >> vt.handoff=1
>> >> Build Date: 03 June 2019  08:10:35AM
>> >> xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
>> >> http://www.ubuntu.com/support)
>> >> Current version of pixman: 0.34.0
>> >> Before reporting problems, check http://wiki.x.org
>> >> to make sure that you have the latest version.
>> >> Markers: (--) probed, (**) from config file, (==) default setting,
>> >> (++) from command line, (!!) notice, (II) informational,
>> >> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> >> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
>> >> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>> >> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>> >> _XSERVTransSocketUNIXAccept: accept() failed
>> >> _XSERVTransSocketUNIXAccept: accept() failed
>> >> _XSERVTransSocketUNIXAccept: accept() failed
>> >> _XSERVTransSocketUNIXAccept: accept() failed
>> >> _XSERVTransSocketUNIXAccept: accept() failed
>> >> _XSERVTransSocketUNIXAccept: accept() failed
>> >> _XSERVTransSocketUNIXAccept: accept() failed
>> >> "
>> >>
>> >> that last line is an endless loop.
>> >
>> > If googling the IOPL error did not work  there is stuff like this too,
>> >
>> > http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
>> >
>> > you could lsof and grep for the process, check what it has open,  or
>> > just
>> > make the changes and see what happens.
>> >
>>
>> At
>> http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
>> is
>>
>> "
>> Thanks to #openbsd's epony and oldlaptop, the resolution is to:
>>
>> 1. increase daemon openfiles-max to 2048 and openfiles-cur to 1024 in
>> /etc/login.conf
>> 2. cap_mkdb /etc/login.conf
>> 3. re-login.
>>
>> Thanks
>> "
>>
>> However, ...
>>
>> "
>> bret@bret-MD34045-2521:~$ sudo cat /etc/login.conf
>> [sudo] password for bret:
>> cat: /etc/login.conf: No such file or directory
>>
>> "
>>
>>
>> > I guess you could itry  " ps ax -f | grep lightdm " and see if it is
>> > root or
>> > has the right user for any needed  permissions.
>> >
>>
>> "
>> bret@bret-MD34045-2521:~$ ps ax -f | grep lightdm
>> root      1256     1  0 03:29 ?        SLsl   0:00 /usr/sbin/lightdm
>> root      1269  1256  2 03:29 tty7     Ssl+   3:34 /usr/lib/xorg/Xorg
>> -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
>> -novtswitch
>> root      1458  1256  0 03:29 ?        Sl     0:00 lightdm --session-child
>> 13 20
>> bret     15899  5719  0 06:07 pts/0    S+     0:00 grep --color=auto
>> lightdm
>> bret@bret-MD34045-2521:~$
>> "
>>
>> I do not understand the output.
>
> Well, it is running as root. If googling did not work, you could see if
> it managed to open anything. For example,
>
> sudo netstat -anp | grep lightdm
> unix  3      [ ]         STREAM     CONNECTED     24081    1191/lightdm
>
> unix  2      [ ]         DGRAM                    28837    1332/lightdm
>
> unix  3      [ ]         STREAM     CONNECTED     27936    1191/lightdm
>
> unix  3      [ ]         STREAM     CONNECTED     24319    1332/lightdm
>
> unix  3      [ ]         STREAM     CONNECTED     26915    1191/lightdm
>

"
bret@bret-MD34045-2521:~$ sudo netstat -anp | grep lightdm
[sudo] password for bret:
unix  2      [ ]         DGRAM                    26540    1458/lightdm
unix  3      [ ]         STREAM     CONNECTED     29759    1458/lightdm
unix  3      [ ]         STREAM     CONNECTED     24440    1256/lightdm
unix  3      [ ]         STREAM     CONNECTED     27958    1256/lightdm
unix  3      [ ]         STREAM     CONNECTED     25119    1256/lightdm
unix  2      [ ]         DGRAM                    25121    1256/lightdm
bret@bret-MD34045-2521:~$
"

>
>
> with or without the wc,
>
> sudo lsof | grep lightdm  | wc
>

"
bret@bret-MD34045-2521:~$ sudo lsof | grep lightdm  | wc
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
    128    1176   16202
bret@bret-MD34045-2521:~$
"


--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Oliver Grawert
In reply to this post by Bret Busby-2
hi,
Am Montag, den 29.07.2019, 06:12 +0800 schrieb Bret Busby:


> > >
> > > "
> > > bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
> > >
> > > X.Org X Server 1.19.6
> > > Release Date: 2017-12-20
> > > X Protocol Version 11, Revision 0
> > > Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
> > > Current Operating System: Linux bret-MD34045-2521 4.15.0-55-
> > > generic
> > > #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
> > > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> > > root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
> > > vt.handoff=1
> > > Build Date: 03 June 2019  08:10:35AM
> > > xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
> > > http://www.ubuntu.com/support)
> > > Current version of pixman: 0.34.0
> > > Before reporting problems, check http://wiki.x.org
> > > to make sure that you have the latest version.
> > > Markers: (--) probed, (**) from config file, (==) default
> > > setting,
> > > (++) from command line, (!!) notice, (II) informational,
> > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> > > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50
> > > 2019
> > > (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> > > xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
> > > permitted)
> > > _XSERVTransSocketUNIXAccept: accept() failed
> > > _XSERVTransSocketUNIXAccept: accept() failed
> > > _XSERVTransSocketUNIXAccept: accept() failed
> > > _XSERVTransSocketUNIXAccept: accept() failed
> > > _XSERVTransSocketUNIXAccept: accept() failed
> > > _XSERVTransSocketUNIXAccept: accept() failed
> > > _XSERVTransSocketUNIXAccept: accept() failed
> > > "
> > >
> > > that last line is an endless loop.
> >
...
> Thanks to #openbsd's epony and oldlaptop, the resolution is to:
>
... on openbsd ... which you are not running ;)

(and in general it is a bad idea to randomly change system defaults
while you are debugging an issue *only you* seem to have ... this
indicates that something you changed actually broke it ... this is
rarely caused by a system config everyone else uses too)

the error indicates that there are some broken file permissions ... 

what type of graphical session do you run ...

could it be that you ran some graphical app (for example a file
manager) as root that was not designed for this (so it changed the
permissions of a (potentially hidden) file to be only root readable
while it is normally used/written to by a user) ... 

do you have an ~/.xinitrc in your home dir ?

did you ever edit /etc/X11/xorg.xonf (either manually or by using a
tool like nvidia-config)

do you have any third party stuff installed from a PPA or elsewhere
that could have replaced system libs or apps in a broken way ... (note
that .deb packages give their creator 100% root access to your system,
installing foreign packages is always a matter of trust here (this is
why snap packages exist btw))

ciao
        oli
--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
On Mon, Jul 29, 2019 at 11:41:13AM +0200, Oliver Grawert wrote:

> hi,
> Am Montag, den 29.07.2019, 06:12 +0800 schrieb Bret Busby:
> > > > "
> > > > bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
> > > >
> > > > X.Org X Server 1.19.6
> > > > Release Date: 2017-12-20
> > > > X Protocol Version 11, Revision 0
> > > > Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
> > > > Current Operating System: Linux bret-MD34045-2521 4.15.0-55-
> > > > generic
> > > > #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
> > > > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> > > > root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
> > > > vt.handoff=1
> > > > Build Date: 03 June 2019  08:10:35AM
> > > > xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
> > > > http://www.ubuntu.com/support)
> > > > Current version of pixman: 0.34.0
> > > > Before reporting problems, check http://wiki.x.org
> > > > to make sure that you have the latest version.
> > > > Markers: (--) probed, (**) from config file, (==) default
> > > > setting,
> > > > (++) from command line, (!!) notice, (II) informational,
> > > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> > > > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50
> > > > 2019
> > > > (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> > > > xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
> > > > permitted)
> > > > _XSERVTransSocketUNIXAccept: accept() failed
> > > > _XSERVTransSocketUNIXAccept: accept() failed
> > > > _XSERVTransSocketUNIXAccept: accept() failed
> > > > _XSERVTransSocketUNIXAccept: accept() failed
> > > > _XSERVTransSocketUNIXAccept: accept() failed
> > > > _XSERVTransSocketUNIXAccept: accept() failed
> > > > _XSERVTransSocketUNIXAccept: accept() failed
> > > > "
> > > >
> > > > that last line is an endless loop.
> > >
> ...
> > Thanks to #openbsd's epony and oldlaptop, the resolution is to:
> >
> ... on openbsd ... which you are not running ;)
>
> (and in general it is a bad idea to randomly change system defaults
> while you are debugging an issue *only you* seem to have ... this
> indicates that something you changed actually broke it ... this is
> rarely caused by a system config everyone else uses too)

With only two messages that both return google hits it seemed like
an ok place to start but many systems don't have anyone else using
them so it is hard to get much from that.




>
> the error indicates that there are some broken file permissions ... 
>
From ps it appeared to be running as root and later with lsof had
some reasonable number of open files. netstat showed some connections.

You can go through and check the dates on the config files but
hopefully if you try to start it by hand with debug options,
either lightdm or X directly, you can get some idea
which files are most suspect. IIRC there was also a pci
error in this thread and you can see if anything triggers that.

There is probably a single user or recovery option if you get
a grub menu, select that one before it times out to normal boot.
You can use the prior ps output from your console command prompt,
iirc something like

/usr/sbin/lightdm

or the x command,

ps ax | grep lightdm
 1191 ?        SLsl   0:00 /usr/sbin/lightdm
 1243 tty7     Ssl+  79:47 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
 1332 ?        Sl     0:00 lightdm --session-child 12 19

if you "man lightdm" it seems to have a debug mode
and Xorg has a verbose option. You can check the dates on
any files they try to open again IIRC your logs exploded
between the 16th and 22nd or something.



> what type of graphical session do you run ...
>
> could it be that you ran some graphical app (for example a file
> manager) as root that was not designed for this (so it changed the
> permissions of a (potentially hidden) file to be only root readable
> while it is normally used/written to by a user) ... 
>
> do you have an ~/.xinitrc in your home dir ?
>
> did you ever edit /etc/X11/xorg.xonf (either manually or by using a
> tool like nvidia-config)
>
> do you have any third party stuff installed from a PPA or elsewhere
> that could have replaced system libs or apps in a broken way ... (note
> that .deb packages give their creator 100% root access to your system,
> installing foreign packages is always a matter of trust here (this is
> why snap packages exist btw))
>
> ciao
> oli



--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Oliver Grawert
hi,
Am Montag, den 29.07.2019, 10:30 +0000 schrieb Mike Marchywka:

> > the error indicates that there are some broken file permissions
> > ... 
> >
> From ps it appeared to be running as root and later with lsof had
> some reasonable number of open files. netstat showed some
> connections.
the next logical step would be to strace the Xorg startup inside
lightdm and see where it gets an EPERM error (it should actually expose
a loop at the same fequency the messages show up in the log) ... but
thats a pretty advanced task ...

>
> if you "man lightdm" it seems to have a debug mode
> and Xorg has a verbose option. You can check the dates on
> any files they try to open again IIRC your logs exploded
> between the 16th and 22nd or something. 
>
while the debug option might be helpful my guess is still on some
config file change, permission change of a socket in /tmp, /run or the
users home (lightdm also gets toplevel session errors typically) or
some new Xorg module that tries to be loaded due to a config change ...
so looking at timestamps of all the config files to see if there was a
change between these dates will surely also be helpful.

ciao
        oli
--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Oliver Grawert
On 29/07/2019, Oliver Grawert <[hidden email]> wrote:

> hi,
> Am Montag, den 29.07.2019, 06:12 +0800 schrieb Bret Busby:
>>
>> > >
>> > > "
>> > > bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>> > >
>> > > X.Org X Server 1.19.6
>> > > Release Date: 2017-12-20
>> > > X Protocol Version 11, Revision 0
>> > > Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
>> > > Current Operating System: Linux bret-MD34045-2521 4.15.0-55-
>> > > generic
>> > > #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
>> > > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
>> > > root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
>> > > vt.handoff=1
>> > > Build Date: 03 June 2019  08:10:35AM
>> > > xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
>> > > http://www.ubuntu.com/support)
>> > > Current version of pixman: 0.34.0
>> > > Before reporting problems, check http://wiki.x.org
>> > > to make sure that you have the latest version.
>> > > Markers: (--) probed, (**) from config file, (==) default
>> > > setting,
>> > > (++) from command line, (!!) notice, (II) informational,
>> > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> > > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50
>> > > 2019
>> > > (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>> > > xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
>> > > permitted)
>> > > _XSERVTransSocketUNIXAccept: accept() failed
>> > > _XSERVTransSocketUNIXAccept: accept() failed
>> > > _XSERVTransSocketUNIXAccept: accept() failed
>> > > _XSERVTransSocketUNIXAccept: accept() failed
>> > > _XSERVTransSocketUNIXAccept: accept() failed
>> > > _XSERVTransSocketUNIXAccept: accept() failed
>> > > _XSERVTransSocketUNIXAccept: accept() failed
>> > > "
>> > >
>> > > that last line is an endless loop.
>> >
> ...
>> Thanks to #openbsd's epony and oldlaptop, the resolution is to:
>>
> ... on openbsd ... which you are not running ;)
>
> (and in general it is a bad idea to randomly change system defaults
> while you are debugging an issue *only you* seem to have ... this
> indicates that something you changed actually broke it ... this is
> rarely caused by a system config everyone else uses too)
>
> the error indicates that there are some broken file permissions ...
>
> what type of graphical session do you run ...
>

The computer is running UbuntuMATE 18.04.2 so I assume that the MATE
context is what you are asking.

> could it be that you ran some graphical app (for example a file
> manager) as root that was not designed for this (so it changed the
> permissions of a (potentially hidden) file to be only root readable
> while it is normally used/written to by a user) ...
>

The file manager caja has an option in the File menu; "Open as
Administrator", which I have used, I may have used that to change the
permissions on two of the extra partitions that I had created at
system installation, changing the permissions on the partitions, to
allow me, as a user, to write to them.

> do you have an ~/.xinitrc in your home dir ?
>

Not shown;

"
bret@bret-MD34045-2521:~$ ls -l .x*
-rw------- 1 bret bret  211427 Jul 29 18:56 .xsession-errors
-rw------- 1 bret bret 2531811 Jul 29 03:23 .xsession-errors.old
bret@bret-MD34045-2521:~$
"

The GUI file manager caja also shows the presence of a file m.Xauthority .

> did you ever edit /etc/X11/xorg.xonf (either manually or by using a
> tool like nvidia-config)
>

No. I assume that the file extension that you meant, is  .conf .

The system is

"
MEDION® AKOYA® P40000 Multimedia PC System
"

with

"
8th generation Intel® Core™ i3-8100 processor
with integrated Intel® UHD Graphics 630
(3.6 GHz, 4 cores and 6 MB Intel® Smart Cache)
Windows 10 Home
Faster to done: start fast and finish first.
Windows gives you great multi-tasking features for quickly and
efficiently getting things done. The Start menu is better than ever.
Work easily with multiple apps open and benefit from the new ways to
stay organised
1 TB (1,000 GB) hard drive
Forget worries about running out of memory. The large 1000 GB hard
drive will always have plenty of space for your movies, photos, music
and other files.
8 GB DDR4 RAM memory
Modern DDR4 memory works at higher clock speed and lower voltage.
That's why DDR4 RAM is much faster than previous memory generations,
yet uses less power. Using DDR4 RAM makes your system more efficient
and noticeably more responsive.
Fast wireless LAN ac standard technology
with integrated Bluetooth® function
Multi-standard DVD/CD burner with DVD-RAM and dual-layer support
Enjoy your entertainment experience with the multi-standard DVD/CD
burner with DVD-RAM and dual-layer support.
Multi-card reader for SD/MS/MMC memory cards
Hot-swap mobile rack1
Swap your 2.5” and 3.5” SATA hard drives quickly and easily – even
while the PC is running. Perfect for data backups, data exchange and
alternative operating systems.
Gigabit LAN network controller (10/100/1000 Mbit/s.)
6-channel high-definition audio
USB keyboard and optical USB mouse
"

- https://aldi.medion.com/md34045/au/content/ausstattung.php

The RAM has been expanded to 32GB (to deal with web pages that use
javascript and other junk).

> do you have any third party stuff installed from a PPA or elsewhere
> that could have replaced system libs or apps in a broken way ... (note
> that .deb packages give their creator 100% root access to your system,
> installing foreign packages is always a matter of trust here (this is
> why snap packages exist btw))
>

Not as far as I am aware.

> ciao
> oli

Given the original error posted;

"
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053210] pcieport
0000:00:1d.0: AER: Corrected error received: id=00e8
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053216] pcieport
0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e8(Receiver ID)
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053219] pcieport
0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053221] pcieport
0000:00:1d.0:    [ 0] Receiver Error         (First)
"

and the

"
==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
"

and the

"integrated Intel® UHD Graphics 630"

I am wondering whether the error is from the combination of the three.

Is a command available, for use at the command line, or, otherwise, a
GUI application, that shows exactly what is
"
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)
"

?

A number of issues appear to be  involved, here, the first, is the
combination of the two errors (error sets ?) above, and, a second, is
the thing (?) that incessantly writes to the log files, compulsively
eating the free space, like a rabid PacMan - whatever is doing that,
as I have previously stated, appears to be defective and uncontrolled
and uncontrollable.


--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Bret Busby <[hidden email]> wrote:

> On 29/07/2019, Oliver Grawert <[hidden email]> wrote:
>> hi,
>> Am Montag, den 29.07.2019, 06:12 +0800 schrieb Bret Busby:
>>>
>>> > >
>>> > > "
>>> > > bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>>> > >
>>> > > X.Org X Server 1.19.6
>>> > > Release Date: 2017-12-20
>>> > > X Protocol Version 11, Revision 0
>>> > > Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
>>> > > Current Operating System: Linux bret-MD34045-2521 4.15.0-55-
>>> > > generic
>>> > > #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
>>> > > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
>>> > > root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
>>> > > vt.handoff=1
>>> > > Build Date: 03 June 2019  08:10:35AM
>>> > > xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
>>> > > http://www.ubuntu.com/support)
>>> > > Current version of pixman: 0.34.0
>>> > > Before reporting problems, check http://wiki.x.org
>>> > > to make sure that you have the latest version.
>>> > > Markers: (--) probed, (**) from config file, (==) default
>>> > > setting,
>>> > > (++) from command line, (!!) notice, (II) informational,
>>> > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>>> > > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50
>>> > > 2019
>>> > > (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>>> > > xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
>>> > > permitted)
>>> > > _XSERVTransSocketUNIXAccept: accept() failed
>>> > > _XSERVTransSocketUNIXAccept: accept() failed
>>> > > _XSERVTransSocketUNIXAccept: accept() failed
>>> > > _XSERVTransSocketUNIXAccept: accept() failed
>>> > > _XSERVTransSocketUNIXAccept: accept() failed
>>> > > _XSERVTransSocketUNIXAccept: accept() failed
>>> > > _XSERVTransSocketUNIXAccept: accept() failed
>>> > > "
>>> > >
>>> > > that last line is an endless loop.
>>> >
>> ...
>>> Thanks to #openbsd's epony and oldlaptop, the resolution is to:
>>>
>> ... on openbsd ... which you are not running ;)
>>
>> (and in general it is a bad idea to randomly change system defaults
>> while you are debugging an issue *only you* seem to have ... this
>> indicates that something you changed actually broke it ... this is
>> rarely caused by a system config everyone else uses too)
>>
>> the error indicates that there are some broken file permissions ...
>>
>> what type of graphical session do you run ...
>>
>
> The computer is running UbuntuMATE 18.04.2 so I assume that the MATE
> context is what you are asking.
>
>> could it be that you ran some graphical app (for example a file
>> manager) as root that was not designed for this (so it changed the
>> permissions of a (potentially hidden) file to be only root readable
>> while it is normally used/written to by a user) ...
>>
>
> The file manager caja has an option in the File menu; "Open as
> Administrator", which I have used, I may have used that to change the
> permissions on two of the extra partitions that I had created at
> system installation, changing the permissions on the partitions, to
> allow me, as a user, to write to them.
>
>> do you have an ~/.xinitrc in your home dir ?
>>
>
> Not shown;
>
> "
> bret@bret-MD34045-2521:~$ ls -l .x*
> -rw------- 1 bret bret  211427 Jul 29 18:56 .xsession-errors
> -rw------- 1 bret bret 2531811 Jul 29 03:23 .xsession-errors.old
> bret@bret-MD34045-2521:~$
> "
>
> The GUI file manager caja also shows the presence of a file m.Xauthority .
>
>> did you ever edit /etc/X11/xorg.xonf (either manually or by using a
>> tool like nvidia-config)
>>
>
> No. I assume that the file extension that you meant, is  .conf .
>
> The system is
>
> "
> MEDION® AKOYA® P40000 Multimedia PC System
> "
>
> with
>
> "
> 8th generation Intel® Core™ i3-8100 processor
> with integrated Intel® UHD Graphics 630
> (3.6 GHz, 4 cores and 6 MB Intel® Smart Cache)
> Windows 10 Home
> Faster to done: start fast and finish first.
> Windows gives you great multi-tasking features for quickly and
> efficiently getting things done. The Start menu is better than ever.
> Work easily with multiple apps open and benefit from the new ways to
> stay organised
> 1 TB (1,000 GB) hard drive
> Forget worries about running out of memory. The large 1000 GB hard
> drive will always have plenty of space for your movies, photos, music
> and other files.
> 8 GB DDR4 RAM memory
> Modern DDR4 memory works at higher clock speed and lower voltage.
> That's why DDR4 RAM is much faster than previous memory generations,
> yet uses less power. Using DDR4 RAM makes your system more efficient
> and noticeably more responsive.
> Fast wireless LAN ac standard technology
> with integrated Bluetooth® function
> Multi-standard DVD/CD burner with DVD-RAM and dual-layer support
> Enjoy your entertainment experience with the multi-standard DVD/CD
> burner with DVD-RAM and dual-layer support.
> Multi-card reader for SD/MS/MMC memory cards
> Hot-swap mobile rack1
> Swap your 2.5” and 3.5” SATA hard drives quickly and easily – even
> while the PC is running. Perfect for data backups, data exchange and
> alternative operating systems.
> Gigabit LAN network controller (10/100/1000 Mbit/s.)
> 6-channel high-definition audio
> USB keyboard and optical USB mouse
> "
>
> - https://aldi.medion.com/md34045/au/content/ausstattung.php
>
> The RAM has been expanded to 32GB (to deal with web pages that use
> javascript and other junk).
>

The RAM was changed on 15 July, from a Kingston 8GB DDR 4 2400MHz card, to
"
Corsair 32GB Kit (2x16GB) DDR4 Vengeance LPX
Ryzen Black C16 2400MHz (CMK32GX4M2Z2400C16)
"

I am including that, here, on the off-chance that that may have
something to do with this.

>> do you have any third party stuff installed from a PPA or elsewhere
>> that could have replaced system libs or apps in a broken way ... (note
>> that .deb packages give their creator 100% root access to your system,
>> installing foreign packages is always a matter of trust here (this is
>> why snap packages exist btw))
>>
>
> Not as far as I am aware.
>
>> ciao
>> oli
>
> Given the original error posted;
>
> "
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053210] pcieport
> 0000:00:1d.0: AER: Corrected error received: id=00e8
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053216] pcieport
> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
> id=00e8(Receiver ID)
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053219] pcieport
> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053221] pcieport
> 0000:00:1d.0:    [ 0] Receiver Error         (First)
> "
>
> and the
>
> "
> ==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> "
>
> and the
>
> "integrated Intel® UHD Graphics 630"
>
> I am wondering whether the error is from the combination of the three.
>
> Is a command available, for use at the command line, or, otherwise, a
> GUI application, that shows exactly what is
> "
> 00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
> Port #9 (rev f0)
> "
>
> ?
>
> A number of issues appear to be  involved, here, the first, is the
> combination of the two errors (error sets ?) above, and, a second, is
> the thing (?) that incessantly writes to the log files, compulsively
> eating the free space, like a rabid PacMan - whatever is doing that,
> as I have previously stated, appears to be defective and uncontrolled
> and uncontrollable.
>
>
> --
> Bret Busby
> Armadale
> West Australia
> ..............
>
> "So once you do know what the question actually is,
>  you'll know what the answer means."
> - Deep Thought,
>  Chapter 28 of Book 1 of
>  "The Hitchhiker's Guide to the Galaxy:
>  A Trilogy In Four Parts",
>  written by Douglas Adams,
>  published by Pan Books, 1992
>
> ....................................................
>


--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Oliver Grawert
In reply to this post by Bret Busby-2
hi,
Am Montag, den 29.07.2019, 19:43 +0800 schrieb Bret Busby:

> The computer is running UbuntuMATE 18.04.2 so I assume that the MATE
> context is what you are asking.

yeah, thats what i wanted to know ...

>
> > 
> The file manager caja has an option in the File menu; "Open as
> Administrator", which I have used, I may have used that to change the
> permissions on two of the extra partitions that I had created at
> system installation, changing the permissions on the partitions, to
> allow me, as a user, to write to them.

if the file manager itself offers such an option i'd assume this is
well tested to not break anythin (well ... beyond what you as a user
can break when using it in this mode ... we did have issues in the past
where when people ran something like "sudo nautilus" all session
related socket files changed to be root.root and only root
readable/writable for example, it took one release until nautilus got
fixed in that area ... but again, if the file manager itself offers
such a feature it should be well tested by the developers)

changing whole partitions for allowing user access is usually something
you should do via mount options, not with a file manger where you
potentially rip open quite a few security holes by making *everything*
user/world writable ... but thats unlikely to be related to the issue,
just a remark ...


> The GUI file manager caja also shows the presence of a file
> m.Xauthority .

whats the permissions of this file (should be owned by your user and
only read/writable by it) ?


> - https://aldi.medion.com/md34045/au/content/ausstattung.php
>

interesting, i didnt know aldi is active in australia :)

(see the next answer to your "ram changed on the 15th" for more ...)

ciao
        oli
--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Oliver Grawert
In reply to this post by Bret Busby-2
hi,
Am Montag, den 29.07.2019, 19:48 +0800 schrieb Bret Busby:


> >
> The RAM was changed on 15 July, from a Kingston 8GB DDR 4 2400MHz
> card, to
> "
> Corsair 32GB Kit (2x16GB) DDR4 Vengeance LPX
> Ryzen Black C16 2400MHz (CMK32GX4M2Z2400C16)
> "
>
> I am including that, here, on the off-chance that that may have
> something to do with this.
easy to test if you still have the old RAM around ... change it back
and see if the errors vanish ;)

seemingly this ram is "optimized for AMZ Ryzen CPUs" while it "can also
run on Intel X99, 100 und 200 series mainboards" 

your system is an intel i3 (sadly the HW description doesnt tell what
mainboard you have (sudo dmidecode should print that somewhere in its
output though), but probably not an X99, 100 or 200 series one) ... 

the date when you changed the ram matches the point in time when your
logs started growing, so try if moving back to the old one helps .. if
it does i'd assume your new ram is simply incompatible with that system
...

ciao
        oli
--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Oliver Grawert
hi,
Am Montag, den 29.07.2019, 14:34 +0200 schrieb Oliver Grawert:
> optimized for AMZ Ryzen CPUs

*AMD* Ryzen indeed :)

ciao
        oli
--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Oliver Grawert
On 29/07/2019, Oliver Grawert <[hidden email]> wrote:

> hi,
> Am Montag, den 29.07.2019, 19:43 +0800 schrieb Bret Busby:
>>
>> The computer is running UbuntuMATE 18.04.2 so I assume that the MATE
>> context is what you are asking.
>
> yeah, thats what i wanted to know ...
>
>>
>> >
>> The file manager caja has an option in the File menu; "Open as
>> Administrator", which I have used, I may have used that to change the
>> permissions on two of the extra partitions that I had created at
>> system installation, changing the permissions on the partitions, to
>> allow me, as a user, to write to them.
>
> if the file manager itself offers such an option i'd assume this is
> well tested to not break anythin (well ... beyond what you as a user
> can break when using it in this mode ... we did have issues in the past
> where when people ran something like "sudo nautilus" all session
> related socket files changed to be root.root and only root
> readable/writable for example, it took one release until nautilus got
> fixed in that area ... but again, if the file manager itself offers
> such a feature it should be well tested by the developers)
>
> changing whole partitions for allowing user access is usually something
> you should do via mount options, not with a file manger where you
> potentially rip open quite a few security holes by making *everything*
> user/world writable ... but thats unlikely to be related to the issue,
> just a remark ...
>
>>
>> The GUI file manager caja also shows the presence of a file
>> m.Xauthority .
>
> whats the permissions of this file (should be owned by your user and
> only read/writable by it) ?
>


"
bret@bret-MD34045-2521:~$ ls -l .Xauthority
-rw------- 1 bret bret 62 Jul 29 03:30 .Xauthority
bret@bret-MD34045-2521:~$
"

>>
>> - https://aldi.medion.com/md34045/au/content/ausstattung.php
>>
>
> interesting, i didnt know aldi is active in australia :)
>

A few years, now, I believe.

> (see the next answer to your "ram changed on the 15th" for more ...)
>
> ciao
> oli


--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Oliver Grawert
On 29/07/2019, Oliver Grawert <[hidden email]> wrote:

> hi,
> Am Montag, den 29.07.2019, 19:48 +0800 schrieb Bret Busby:
>>
>> >
>> The RAM was changed on 15 July, from a Kingston 8GB DDR 4 2400MHz
>> card, to
>> "
>> Corsair 32GB Kit (2x16GB) DDR4 Vengeance LPX
>> Ryzen Black C16 2400MHz (CMK32GX4M2Z2400C16)
>> "
>>
>> I am including that, here, on the off-chance that that may have
>> something to do with this.
>
> easy to test if you still have the old RAM around ... change it back
> and see if the errors vanish ;)
>
> seemingly this ram is "optimized for AMZ Ryzen CPUs" while it "can also
> run on Intel X99, 100 und 200 series mainboards"
>
> your system is an intel i3 (sadly the HW description doesnt tell what
> mainboard you have (sudo dmidecode should print that somewhere in its
> output though), but probably not an X99, 100 or 200 series one) ...
>

"
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: MEDION
        Product Name: Z370H4-EM
        Version: 1.0
        Serial Number: ME5100G74501135
        Asset Tag: Default string
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis: Default string
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0
"

?

Sorry - I thought the information that I had posted, included the
motherboard model.

From the above, and,, from
https://forums.whirlpool.net.au/archive/2702808

"
It is an ECS oem mobo. Z370H4-EM
"

> the date when you changed the ram matches the point in time when your
> logs started growing, so try if moving back to the old one helps .. if
> it does i'd assume your new ram is simply incompatible with that system
> ...
>
> ciao
> oli


I can't do anything much physically with the computer, and, I am not
confident to open it and do anything inside it - I am right-handed,
and, about half of my right hand has been numb for about two months,
now, and, I do not have much strength in my right hand.

The new RAM was installed by my local computer shop for me, and, the
man booted it into BIOS, to determine that the BIOS could see the 32GB
of RAM, and, as other UbuntuMATE utilities can see the RAM, including
the System Monitor, I had taken for granted, that the 32GB RAM is
compatible.

From the above command;

"
Handle 0x003D, DMI type 16, 23 bytes
Physical Memory Array
        Location: System Board Or Motherboard
        Use: System Memory
        Error Correction Type: None
        Maximum Capacity: 32 GB
        Error Information Handle: Not Provided
        Number Of Devices: 2

Handle 0x003E, DMI type 17, 40 bytes
Memory Device
        Array Handle: 0x003D
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 16384 MB
        Form Factor: DIMM
        Set: None
        Locator: ChannelA-DIMM0
        Bank Locator: BANK 0
        Type: DDR4
        Type Detail: Synchronous Unbuffered (Unregistered)
   Speed: 2400 MT/s
        Manufacturer: 029E
        Serial Number: 00000000
        Asset Tag: 9876543210
        Part Number: CMK32GX4M2Z2400C16
        Rank: 2
        Configured Clock Speed: 2400 MT/s
        Minimum Voltage: 1.2 V
        Maximum Voltage: 1.2 V
        Configured Voltage: 1.2 V

Handle 0x003F, DMI type 17, 40 bytes
Memory Device
        Array Handle: 0x003D
        Error Information Handle: Not Provided
        Total Width: 64 bits
        Data Width: 64 bits
        Size: 16384 MB
        Form Factor: DIMM
        Set: None
        Locator: ChannelB-DIMM0
        Bank Locator: BANK 2
        Type: DDR4
        Type Detail: Synchronous Unbuffered (Unregistered)
        Speed: 2400 MT/s
        Manufacturer: 029E
        Serial Number: 00000000
        Asset Tag: 9876543210
        Part Number: CMK32GX4M2Z2400C16
        Rank: 2
        Configured Clock Speed: 2400 MT/s
        Minimum Voltage: 1.2 V
"

I assume from that output, that the 32GB RAM is compatible?

--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
On Tue, Jul 30, 2019 at 12:33:14AM +0800, Bret Busby wrote:

> On 29/07/2019, Oliver Grawert <[hidden email]> wrote:
> > hi,
> > Am Montag, den 29.07.2019, 19:48 +0800 schrieb Bret Busby:
> >>
> >> >
> >> The RAM was changed on 15 July, from a Kingston 8GB DDR 4 2400MHz
> >> card, to
> >> "
> >> Corsair 32GB Kit (2x16GB) DDR4 Vengeance LPX
> >> Ryzen Black C16 2400MHz (CMK32GX4M2Z2400C16)
> >> "
> >>
> >> I am including that, here, on the off-chance that that may have
> >> something to do with this.
> >
> > easy to test if you still have the old RAM around ... change it back
> > and see if the errors vanish ;)
> >
> > seemingly this ram is "optimized for AMZ Ryzen CPUs" while it "can also
> > run on Intel X99, 100 und 200 series mainboards"
> >
> > your system is an intel i3 (sadly the HW description doesnt tell what
> > mainboard you have (sudo dmidecode should print that somewhere in its
> > output though), but probably not an X99, 100 or 200 series one) ...
> >
>
> "
> Handle 0x0002, DMI type 2, 15 bytes
> Base Board Information
>         Manufacturer: MEDION
>         Product Name: Z370H4-EM
>         Version: 1.0
>         Serial Number: ME5100G74501135
>         Asset Tag: Default string
>         Features:
>                 Board is a hosting board
>                 Board is replaceable
>         Location In Chassis: Default string
>         Chassis Handle: 0x0003
>         Type: Motherboard
>         Contained Object Handles: 0
> "
>
> ?
>
> Sorry - I thought the information that I had posted, included the
> motherboard model.
>
> From the above, and,, from
> https://forums.whirlpool.net.au/archive/2702808
>
> "
> It is an ECS oem mobo. Z370H4-EM
> "
>
> > the date when you changed the ram matches the point in time when your
> > logs started growing, so try if moving back to the old one helps .. if
> > it does i'd assume your new ram is simply incompatible with that system
> > ...
> >
> > ciao
> > oli
>
>
> I can't do anything much physically with the computer, and, I am not
> confident to open it and do anything inside it - I am right-handed,
> and, about half of my right hand has been numb for about two months,
> now, and, I do not have much strength in my right hand.
>
> The new RAM was installed by my local computer shop for me, and, the
> man booted it into BIOS, to determine that the BIOS could see the 32GB
> of RAM, and, as other UbuntuMATE utilities can see the RAM, including
> the System Monitor, I had taken for granted, that the 32GB RAM is
> compatible.
>
> From the above command;
>
> "
> Handle 0x003D, DMI type 16, 23 bytes
> Physical Memory Array
>         Location: System Board Or Motherboard
>         Use: System Memory
>         Error Correction Type: None
>         Maximum Capacity: 32 GB
>         Error Information Handle: Not Provided
>         Number Of Devices: 2
>
> Handle 0x003E, DMI type 17, 40 bytes
> Memory Device
>         Array Handle: 0x003D
>         Error Information Handle: Not Provided
>         Total Width: 64 bits
>         Data Width: 64 bits
>         Size: 16384 MB
>         Form Factor: DIMM
>         Set: None
>         Locator: ChannelA-DIMM0
>         Bank Locator: BANK 0
>         Type: DDR4
>         Type Detail: Synchronous Unbuffered (Unregistered)
>    Speed: 2400 MT/s
>         Manufacturer: 029E
>         Serial Number: 00000000
>         Asset Tag: 9876543210
>         Part Number: CMK32GX4M2Z2400C16
>         Rank: 2
>         Configured Clock Speed: 2400 MT/s
>         Minimum Voltage: 1.2 V
>         Maximum Voltage: 1.2 V
>         Configured Voltage: 1.2 V
>
> Handle 0x003F, DMI type 17, 40 bytes
> Memory Device
>         Array Handle: 0x003D
>         Error Information Handle: Not Provided
>         Total Width: 64 bits
>         Data Width: 64 bits
>         Size: 16384 MB
>         Form Factor: DIMM
>         Set: None
>         Locator: ChannelB-DIMM0
>         Bank Locator: BANK 2
>         Type: DDR4
>         Type Detail: Synchronous Unbuffered (Unregistered)
>         Speed: 2400 MT/s
>         Manufacturer: 029E
>         Serial Number: 00000000
>         Asset Tag: 9876543210
>         Part Number: CMK32GX4M2Z2400C16
>         Rank: 2
>         Configured Clock Speed: 2400 MT/s
>         Minimum Voltage: 1.2 V
> "
>
> I assume from that output, that the 32GB RAM is compatible?

Does your bios have a memory test? You could just check that.

How often do you get the PCI errors? Do you check dmesg often?

I'd still try to boot into single user mode and try to trigger
the PCI errors just by starting a few things manually
like lightdm with debug flag that seems to be the immediate problem.


>
> --
> Bret Busby
> Armadale
> West Australia
> ..............
>
> "So once you do know what the question actually is,
>  you'll know what the answer means."
> - Deep Thought,
>  Chapter 28 of Book 1 of
>  "The Hitchhiker's Guide to the Galaxy:
>  A Trilogy In Four Parts",
>  written by Douglas Adams,
>  published by Pan Books, 1992
>
> ....................................................
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 30/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Tue, Jul 30, 2019 at 12:33:14AM +0800, Bret Busby wrote:
>> On 29/07/2019, Oliver Grawert <[hidden email]> wrote:
>> > hi,
>> > Am Montag, den 29.07.2019, 19:48 +0800 schrieb Bret Busby:
>> >>
>> >> >
>> >> The RAM was changed on 15 July, from a Kingston 8GB DDR 4 2400MHz
>> >> card, to
>> >> "
>> >> Corsair 32GB Kit (2x16GB) DDR4 Vengeance LPX
>> >> Ryzen Black C16 2400MHz (CMK32GX4M2Z2400C16)
>> >> "
>> >>
>> >> I am including that, here, on the off-chance that that may have
>> >> something to do with this.
>> >
>> > easy to test if you still have the old RAM around ... change it back
>> > and see if the errors vanish ;)
>> >
>> > seemingly this ram is "optimized for AMZ Ryzen CPUs" while it "can also
>> > run on Intel X99, 100 und 200 series mainboards"
>> >
>> > your system is an intel i3 (sadly the HW description doesnt tell what
>> > mainboard you have (sudo dmidecode should print that somewhere in its
>> > output though), but probably not an X99, 100 or 200 series one) ...
>> >
>>
>> "
>> Handle 0x0002, DMI type 2, 15 bytes
>> Base Board Information
>>         Manufacturer: MEDION
>>         Product Name: Z370H4-EM
>>         Version: 1.0
>>         Serial Number: ME5100G74501135
>>         Asset Tag: Default string
>>         Features:
>>                 Board is a hosting board
>>                 Board is replaceable
>>         Location In Chassis: Default string
>>         Chassis Handle: 0x0003
>>         Type: Motherboard
>>         Contained Object Handles: 0
>> "
>>
>> ?
>>
>> Sorry - I thought the information that I had posted, included the
>> motherboard model.
>>
>> From the above, and,, from
>> https://forums.whirlpool.net.au/archive/2702808
>>
>> "
>> It is an ECS oem mobo. Z370H4-EM
>> "
>>
>> > the date when you changed the ram matches the point in time when your
>> > logs started growing, so try if moving back to the old one helps .. if
>> > it does i'd assume your new ram is simply incompatible with that system
>> > ...
>> >
>> > ciao
>> > oli
>>
>>
>> I can't do anything much physically with the computer, and, I am not
>> confident to open it and do anything inside it - I am right-handed,
>> and, about half of my right hand has been numb for about two months,
>> now, and, I do not have much strength in my right hand.
>>
>> The new RAM was installed by my local computer shop for me, and, the
>> man booted it into BIOS, to determine that the BIOS could see the 32GB
>> of RAM, and, as other UbuntuMATE utilities can see the RAM, including
>> the System Monitor, I had taken for granted, that the 32GB RAM is
>> compatible.
>>
>> From the above command;
>>
>> "
>> Handle 0x003D, DMI type 16, 23 bytes
>> Physical Memory Array
>>         Location: System Board Or Motherboard
>>         Use: System Memory
>>         Error Correction Type: None
>>         Maximum Capacity: 32 GB
>>         Error Information Handle: Not Provided
>>         Number Of Devices: 2
>>
>> Handle 0x003E, DMI type 17, 40 bytes
>> Memory Device
>>         Array Handle: 0x003D
>>         Error Information Handle: Not Provided
>>         Total Width: 64 bits
>>         Data Width: 64 bits
>>         Size: 16384 MB
>>         Form Factor: DIMM
>>         Set: None
>>         Locator: ChannelA-DIMM0
>>         Bank Locator: BANK 0
>>         Type: DDR4
>>         Type Detail: Synchronous Unbuffered (Unregistered)
>>    Speed: 2400 MT/s
>>         Manufacturer: 029E
>>         Serial Number: 00000000
>>         Asset Tag: 9876543210
>>         Part Number: CMK32GX4M2Z2400C16
>>         Rank: 2
>>         Configured Clock Speed: 2400 MT/s
>>         Minimum Voltage: 1.2 V
>>         Maximum Voltage: 1.2 V
>>         Configured Voltage: 1.2 V
>>
>> Handle 0x003F, DMI type 17, 40 bytes
>> Memory Device
>>         Array Handle: 0x003D
>>         Error Information Handle: Not Provided
>>         Total Width: 64 bits
>>         Data Width: 64 bits
>>         Size: 16384 MB
>>         Form Factor: DIMM
>>         Set: None
>>         Locator: ChannelB-DIMM0
>>         Bank Locator: BANK 2
>>         Type: DDR4
>>         Type Detail: Synchronous Unbuffered (Unregistered)
>>         Speed: 2400 MT/s
>>         Manufacturer: 029E
>>         Serial Number: 00000000
>>         Asset Tag: 9876543210
>>         Part Number: CMK32GX4M2Z2400C16
>>         Rank: 2
>>         Configured Clock Speed: 2400 MT/s
>>         Minimum Voltage: 1.2 V
>> "
>>
>> I assume from that output, that the 32GB RAM is compatible?
>
> Does your bios have a memory test? You could just check that.
>

I assume that the shop performed a BIOS memory test, when the new RAM
was fitted - he booted the computer, went into BIOS, and, the screen
was blue, with white text, and, displayed only inmformation about the
memory, including the (about) 32GB being recognised. Outputs show
31xxxMB for the memory.

"
bret@bret-MD34045-2521:~$ free -h
              total        used        free      shared  buff/cache   available
Mem:            31G        5.0G         21G        1.1G        4.5G         24G
Swap:           30G          0B         30G
bret@bret-MD34045-2521:~$
"

After installing memtester, and trying to run
sudo memtester 32G 2

the end of the output is

"
got  16MB (16781312 bytes), trying mlock ...too many pages, reducing...
got  16MB (16777216 bytes), trying mlock ...locked.
Loop 1/2:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Loop 2/2:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : ok
  Bit Flip            : ok
  Walking Ones        : ok
  Walking Zeroes      : ok
  8-bit Writes        : ok
  16-bit Writes       : ok

Done.

"

after it working its way down to the 16MB, with thememory quantity
decreasing each line, until it got down to the 16MB.

memtester appears to cope with no more than 16MB of RAM.

> How often do you get the PCI errors? Do you check dmesg often?
>

The PCI errors appear to be ongoing and incessant.

If I go to a console (<CTRL><ALT><F1>), each time I type a string ( to
log in, and, then, each "word", or, string of characters without a
space), it keeps outputting the PCI error.

dmesg , unfortunately, does not show timestamps

I think a significant thing, is to determine what exactly is the "PCI
bridge" that is at the address,
"00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)
"

to which the error relates;

"
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053210] pcieport
0000:00:1d.0: AER: Corrected error received: id=00e8
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053216] pcieport
0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e8(Receiver ID)
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053219] pcieport
0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053221] pcieport
0000:00:1d.0:    [ 0] Receiver Error         (First)
"


and, also, the Xorg error previously cited;

"
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
_XSERVTransSocketUNIXAccept: accept() failed
"

> I'd still try to boot into single user mode and try to trigger
> the PCI errors just by starting a few things manually
> like lightdm with debug flag that seems to be the immediate problem.
>
>


--
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
>
> > How often do you get the PCI errors? Do you check dmesg often?
> >
>
> The PCI errors appear to be ongoing and incessant.

This may be relevant,

https://askubuntu.com/questions/771899/pcie-bus-error-severity-corrected

I guess I'd try google for now but it could be a software issue
as described in that link. It is probably spurious, to get that many
bus errors and have anything work seems odd. But, there may be
other config problems for your display manager. If changing the
boot command line solves the PCI and it does not look flakey otherwise,
again tryin invoking the lightdm with debug options.

>
> If I go to a console (<CTRL><ALT><F1>), each time I type a string ( to
> log in, and, then, each "word", or, string of characters without a
> space), it keeps outputting the PCI error.
>
> dmesg , unfortunately, does not show timestamps
>
> I think a significant thing, is to determine what exactly is the "PCI
> bridge" that is at the address,
> "00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
> Port #9 (rev f0)
> "
>
> to which the error relates;
>
> "
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053210] pcieport
> 0000:00:1d.0: AER: Corrected error received: id=00e8
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053216] pcieport
> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
> id=00e8(Receiver ID)
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053219] pcieport
> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
> Jul 27 00:06:43 bret-MD34045-2521 kernel: [332491.053221] pcieport
> 0000:00:1d.0:    [ 0] Receiver Error         (First)
> "
>
>
> and, also, the Xorg error previously cited;
>
> "
> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 03:29:50 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> _XSERVTransSocketUNIXAccept: accept() failed
> "
>
> > I'd still try to boot into single user mode and try to trigger
> > the PCI errors just by starting a few things manually
> > like lightdm with debug flag that seems to be the immediate problem.
> >
> >
>
>
> --
> Bret Busby
> Armadale
> West Australia
> ..............
>
> "So once you do know what the question actually is,
>  you'll know what the answer means."
> - Deep Thought,
>  Chapter 28 of Book 1 of
>  "The Hitchhiker's Guide to the Galaxy:
>  A Trilogy In Four Parts",
>  written by Douglas Adams,
>  published by Pan Books, 1992
>
> ....................................................
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
1234