Request for explanation of error message

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

Request for explanation of error message

Bret Busby-2
Hello.

Can someone please advise as to what the following error indicates?

The below is a subset of multiple repetitions of the error, with the
number in the square brackets, immediately after the word "kernel",
progressively increasing in each line.

The error message appearsat the command line console ( <CTRL><ALT><F1>
), and, in /var/log/syslog , from whence the extract is copied.

"
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)
Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
0000:00:1d.0: AER: Corrected error received: id=00e8
Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e8(Receiver ID)
Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
0000:00:1d.0:    [ 0] Receiver Error         (First)
Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
0000:00:1d.0: AER: Corrected error received: id=00e8
Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
id=00e8(Receiver ID)
Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
0000:00:1d.0:    [ 0] Receiver Error         (First)
"

"
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
"

Whilst I do not know how to get uname to show the Ubuntu version
number, the console shows it as 18.04.2 .


Thank you in anticipation.

--
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

Compdoc@hotrodpc.com
On 7/27/19 6:54 AM, Bret Busby wrote:

> Can someone please advise as to what the following error indicates?


I was curious if the motherboard's bios has a setting for 'PCI latency
timer' ?


--
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 Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not for general discussions" <[hidden email]> wrote:

>
> Hello.
>
> Can someone please advise as to what the following error indicates?
>
> The below is a subset of multiple repetitions of the error, with the
> number in the square brackets, immediately after the word "kernel",
> progressively increasing in each line.
>
> The error message appearsat the command line console ( <CTRL><ALT><F1>
> ), and, in /var/log/syslog , from whence the extract is copied.
>
> "
> 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)
> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
> 0000:00:1d.0: AER: Corrected error received: id=00e8
> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
> id=00e8(Receiver ID)
> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
> 0000:00:1d.0:    [ 0] Receiver Error         (First)
> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
> 0000:00:1d.0: AER: Corrected error received: id=00e8
> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
> id=00e8(Receiver ID)
> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
> 0000:00:1d.0:    [ 0] Receiver Error         (First)
> "
>
> "
> 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
> "
>
> Whilst I do not know how to get uname to show the Ubuntu version
> number, the console shows it as 18.04.2 .

What does

lspci

display?

Specificly, what sort of device is at

00:1d.0

?

It looks like whatever is at the point of the PCI bus is having trouble.

Also: what does the dmesg command display?

>
>
> Thank you in anticipation.
>

--
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
On 27/07/2019, Robert Heller <[hidden email]> wrote:

> At Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not for
> general discussions" <[hidden email]> wrote:
>
>>
>> Hello.
>>
>> Can someone please advise as to what the following error indicates?
>>
>> The below is a subset of multiple repetitions of the error, with the
>> number in the square brackets, immediately after the word "kernel",
>> progressively increasing in each line.
>>
>> The error message appearsat the command line console ( <CTRL><ALT><F1>
>> ), and, in /var/log/syslog , from whence the extract is copied.
>>
>> "
>> 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)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> "
>>
>> "
>> 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
>> "
>>
>> Whilst I do not know how to get uname to show the Ubuntu version
>> number, the console shows it as 18.04.2 .
>
> What does
>
> lspci
>
> display?
>
> Specificly, what sort of device is at
>
> 00:1d.0
>
> ?

"
bret@bret-MD34045-2521:~$ lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host
Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core
Processor Gaussian Mixture Model
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 /
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller
00:14.2 Signal processing controller: Intel Corporation 200 Series PCH
Thermal Subsystem
00:15.0 Signal processing controller: Intel Corporation 200 Series PCH
Serial IO I2C Controller #0
00:15.1 Signal processing controller: Intel Corporation 200 Series PCH
Serial IO I2C Controller #1
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #6 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)
00:1e.0 Signal processing controller: Intel Corporation 200
Series/Z370 Chipset Family Serial IO UART Controller #0
00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset
Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
"


>
> It looks like whatever is at the point of the PCI bus is having trouble.
>
> Also: what does the dmesg command display?
>

"
[20358.639179] systemd-journald[340]: Failed to open system journal:
No space left on device
[20358.639292] systemd-journald[340]: Failed to open system journal:
No space left on device
[20358.639536] systemd-journald[340]: Failed to open system journal:
No space left on device
[20358.639646] systemd-journald[340]: Failed to open system journal:
No space left on device
[20358.639880] systemd-journald[340]: Failed to open system journal:
No space left on device
[20358.639993] systemd-journald[340]: Failed to open system journal:
No space left on device
[20358.640853] systemd-journald[340]: Failed to open system journal:
No space left on device
[20358.640976] systemd-journald[340]: Failed to open system journal:
No space left on device
[20359.041667] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[20359.041681] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[20359.041691] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[20359.041697] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[20361.857409] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[20361.857424] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[20361.857435] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[20361.857443] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[20383.115075] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[20383.115091] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[20383.115102] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[20383.115109] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[20383.119565] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.119699] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.120356] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.120467] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.121037] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.121148] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.121705] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.121815] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.122721] systemd-journald[340]: Failed to open system journal:
No space left on device
[20383.122838] systemd-journald[340]: Failed to open system journal:
No space left on device
[20387.218354] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[20387.218369] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[20387.218379] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[20387.218387] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[20391.294040] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[20391.294052] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[20391.294062] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[20391.294070] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[20391.298595] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.298727] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.299371] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.299482] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.300048] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.300160] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.300714] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.300826] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.301672] systemd-journald[340]: Failed to open system journal:
No space left on device
[20391.301801] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.628485] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[20405.628493] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[20405.628498] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[20405.628502] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[20405.632735] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.632809] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.633172] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.633235] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.633559] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.633621] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.633928] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.633990] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.634442] systemd-journald[340]: Failed to open system journal:
No space left on device
[20405.634505] systemd-journald[340]: Failed to open system journal:
No space left on device
"

>>
>>
>> Thank you in anticipation.
>>
>
> --
> 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
>


Whatever is happening, something has filled the partition for /

After sending this message, I will try a reboot to find whether that
clears the muck from the / partition.

--
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 Robert Heller
On 27/07/2019, Robert Heller <[hidden email]> wrote:

> At Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not for
> general discussions" <[hidden email]> wrote:
>
>>
>> Hello.
>>
>> Can someone please advise as to what the following error indicates?
>>
>> The below is a subset of multiple repetitions of the error, with the
>> number in the square brackets, immediately after the word "kernel",
>> progressively increasing in each line.
>>
>> The error message appearsat the command line console ( <CTRL><ALT><F1>
>> ), and, in /var/log/syslog , from whence the extract is copied.
>>
>> "
>> 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)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> "
>>
>> "
>> 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
>> "
>>
>> Whilst I do not know how to get uname to show the Ubuntu version
>> number, the console shows it as 18.04.2 .
>
> What does
>
> lspci
>
> display?
>
> Specificly, what sort of device is at
>
> 00:1d.0
>
> ?

"
bret@bret-MD34045-2521:~$ lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host
Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core
Processor Gaussian Mixture Model
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 /
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller
00:14.2 Signal processing controller: Intel Corporation 200 Series PCH
Thermal Subsystem
00:15.0 Signal processing controller: Intel Corporation 200 Series PCH
Serial IO I2C Controller #0
00:15.1 Signal processing controller: Intel Corporation 200 Series PCH
Serial IO I2C Controller #1
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #6 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)
00:1e.0 Signal processing controller: Intel Corporation 200
Series/Z370 Chipset Family Serial IO UART Controller #0
00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset
Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
"

>
> It looks like whatever is at the point of the PCI bus is having trouble.
>
> Also: what does the dmesg command display?
>

Lots of this;

"
[13744.281025] systemd-journald[340]: Failed to open system journal:
No space left on device
[13744.281051] systemd-journald[340]: Failed to open system journal:
No space left on device
[13744.281189] systemd-journald[340]: Failed to open system journal:
No space left on device
[13744.281215] systemd-journald[340]: Failed to open system journal:
No space left on device
[13744.281343] systemd-journald[340]: Failed to open system journal:
No space left on device
[13744.281369] systemd-journald[340]: Failed to open system journal:
No space left on device
[13810.468140] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[13810.468146] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[13810.468149] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[13810.468151] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[13810.472244] systemd-journald[340]: Failed to open system journal:
No space left on device
[13810.472273] systemd-journald[340]: Failed to open system journal:
No space left on device
[13810.472424] systemd-journald[340]: Failed to open system journal:
No space left on device

"

>>
>>
>> Thank you in anticipation.
>>
>
> --
> 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
>

Whatever is happening, something has filled the / partition.

df -f shows the / partition to be 92GB (from memory, I sought to set
the partitions to each be 100GB); the /home partition is a separate
partition.

When I came back to the computer, to check the email messages, a Low
Space Warning was present, indicating only 2GB left on the /
partition; I closed that, then a no free space warning for the /
partition, appeared.

So, something has been progressively filling the / partition.

After sending this message, I will try to reboot, and, find whether
that clears the muck from the / partition.


--
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 Robert Heller
On 27/07/2019, Robert Heller <[hidden email]> wrote:

> At Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not for
> general discussions" <[hidden email]> wrote:
>
>>
>> Hello.
>>
>> Can someone please advise as to what the following error indicates?
>>
>> The below is a subset of multiple repetitions of the error, with the
>> number in the square brackets, immediately after the word "kernel",
>> progressively increasing in each line.
>>
>> The error message appearsat the command line console ( <CTRL><ALT><F1>
>> ), and, in /var/log/syslog , from whence the extract is copied.
>>
>> "
>> 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)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> "
>>
>> "
>> 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
>> "
>>
>> Whilst I do not know how to get uname to show the Ubuntu version
>> number, the console shows it as 18.04.2 .
>
> What does
>
> lspci
>
> display?
>
> Specificly, what sort of device is at
>
> 00:1d.0
>
> ?
>
> It looks like whatever is at the point of the PCI bus is having trouble.
>
> Also: what does the dmesg command display?
>
>>
>>
>> Thank you in anticipation.
>>
>
> --
> 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
>

I have made two attempts to reply to the above message. They have
apparently failed.

My / partition has been progressively filled, over the last few hours;
df -h shows the partition size to be 92GB.

The /home partition is a separate partition, of about the same (92GB) size.

I will try to reboot, to find whether that clears the muck from the / partition.

--
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 Robert Heller
I am trying again to reply to the message below, as the previous
attempts to answer the questions, failed, but, my last message appears
to have got through, by clicking on a different Send button...

On 27/07/2019, Robert Heller <[hidden email]> wrote:

> At Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not for
> general discussions" <[hidden email]> wrote:
>
>>
>> Hello.
>>
>> Can someone please advise as to what the following error indicates?
>>
>> The below is a subset of multiple repetitions of the error, with the
>> number in the square brackets, immediately after the word "kernel",
>> progressively increasing in each line.
>>
>> The error message appearsat the command line console ( <CTRL><ALT><F1>
>> ), and, in /var/log/syslog , from whence the extract is copied.
>>
>> "
>> 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)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> "
>>
>> "
>> 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
>> "
>>
>> Whilst I do not know how to get uname to show the Ubuntu version
>> number, the console shows it as 18.04.2 .
>
> What does
>
> lspci
>
> display?
>
> Specificly, what sort of device is at
>
> 00:1d.0
>
> ?
>

"
bret@bret-MD34045-2521:~$ lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host
Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core
Processor Gaussian Mixture Model
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 /
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller
00:14.2 Signal processing controller: Intel Corporation 200 Series PCH
Thermal Subsystem
00:15.0 Signal processing controller: Intel Corporation 200 Series PCH
Serial IO I2C Controller #0
00:15.1 Signal processing controller: Intel Corporation 200 Series PCH
Serial IO I2C Controller #1
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #6 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)
00:1e.0 Signal processing controller: Intel Corporation 200
Series/Z370 Chipset Family Serial IO UART Controller #0
00:1f.0 ISA bridge: Intel Corporation Z370 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset
Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
"

> It looks like whatever is at the point of the PCI bus is having trouble.
>
> Also: what does the dmesg command display?
>

Screens of the following;

"
[14818.547186] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[14818.551259] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551289] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551443] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551470] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551601] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551627] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551757] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551783] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.551974] systemd-journald[340]: Failed to open system journal:
No space left on device
[14818.552000] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811149] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811179] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811418] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811445] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811510] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811536] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811590] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811617] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811672] systemd-journald[340]: Failed to open system journal:
No space left on device
[14850.811699] systemd-journald[340]: Failed to open system journal:
No space left on device
[14924.519548] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[14924.519554] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[14924.519556] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[14924.519558] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[14924.523631] systemd-journald[340]: Failed to open system journal:
No space left on device
[14924.523660] systemd-journald[340]: Failed to open system journal:
No space left on device
[14924.523807] systemd-journald[340]: Failed to open system journal:
No space left on device
"


>>
>>
>> Thank you in anticipation.
>>
>
> --
> 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
>


As stated, something has filled my / partition.

After trying to send this message, I will try to reboot, to find what happens.

--
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 Robert Heller
On 27/07/2019, Robert Heller <[hidden email]> wrote:

> At Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not for
> general discussions" <[hidden email]> wrote:
>
>>
>> Hello.
>>
>> Can someone please advise as to what the following error indicates?
>>
>> The below is a subset of multiple repetitions of the error, with the
>> number in the square brackets, immediately after the word "kernel",
>> progressively increasing in each line.
>>
>> The error message appearsat the command line console ( <CTRL><ALT><F1>
>> ), and, in /var/log/syslog , from whence the extract is copied.
>>
>> "
>> 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)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>> id=00e8(Receiver ID)
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>> "
>>
>> "
>> 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
>> "
>>
>> Whilst I do not know how to get uname to show the Ubuntu version
>> number, the console shows it as 18.04.2 .
>
> What does
>
> lspci
>
> display?
>
> Specificly, what sort of device is at
>
> 00:1d.0
>
> ?

00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)


>
> It looks like whatever is at the point of the PCI bus is having trouble.
>
> Also: what does the dmesg command display?
>

Screens of stuff - can't send it - system is temporarily broken.

>>
>>
>> Thank you in anticipation.
>>
>
> --
> 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
>


--
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 Bret Busby-2
On 28/07/2019, Bret Busby <[hidden email]> wrote:

> On 27/07/2019, Robert Heller <[hidden email]> wrote:
>> At Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not
>> for
>> general discussions" <[hidden email]> wrote:
>>
>>>
>>> Hello.
>>>
>>> Can someone please advise as to what the following error indicates?
>>>
>>> The below is a subset of multiple repetitions of the error, with the
>>> number in the square brackets, immediately after the word "kernel",
>>> progressively increasing in each line.
>>>
>>> The error message appearsat the command line console ( <CTRL><ALT><F1>
>>> ), and, in /var/log/syslog , from whence the extract is copied.
>>>
>>> "
>>> 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)
>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
>>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
>>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>>> id=00e8(Receiver ID)
>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
>>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
>>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
>>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
>>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>>> id=00e8(Receiver ID)
>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
>>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
>>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>>> "
>>>
>>> "
>>> 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
>>> "
>>>
>>> Whilst I do not know how to get uname to show the Ubuntu version
>>> number, the console shows it as 18.04.2 .
>>
>> What does
>>
>> lspci
>>
>> display?
>>
>> Specificly, what sort of device is at
>>
>> 00:1d.0
>>
>> ?
>>
>> It looks like whatever is at the point of the PCI bus is having trouble.
>>
>> Also: what does the dmesg command display?
>>
>>>
>>>
>>> Thank you in anticipation.
>>>
>>
>> --
>> 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
>>
>
> I have made two attempts to reply to the above message. They have
> apparently failed.
>
> My / partition has been progressively filled, over the last few hours;
> df -h shows the partition size to be 92GB.
>
> The /home partition is a separate partition, of about the same (92GB) size.
>
> I will try to reboot, to find whether that clears the muck from the /
> partition.
>


I rebooted the computer, and, it did not go to the GUI lohin screen -
it stopped at a console login screen.

So, I logged in at the console, and then ran
sudo apt autoclean
and then it went straight to the GUI login screen.

The autoclean appears to have freed up 2.3GB out of the 60-odd GB that
nappears to be full of muck.

"
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   85G  2.2G  98% /
tmpfs            16G  4.0M   16G   1% /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   44K  3.2G   1% /run/user/1000
"

Well, it appears to have been overturned, because, then, I got a no
free space left on device warning - 0GB left on /  .


--
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 28/07/2019, Bret Busby <[hidden email]> wrote:

> On 28/07/2019, Bret Busby <[hidden email]> wrote:
>> On 27/07/2019, Robert Heller <[hidden email]> wrote:
>>> At Sat, 27 Jul 2019 20:54:19 +0800 "Ubuntu user technical support,  not
>>> for
>>> general discussions" <[hidden email]> wrote:
>>>
>>>>
>>>> Hello.
>>>>
>>>> Can someone please advise as to what the following error indicates?
>>>>
>>>> The below is a subset of multiple repetitions of the error, with the
>>>> number in the square brackets, immediately after the word "kernel",
>>>> progressively increasing in each line.
>>>>
>>>> The error message appearsat the command line console ( <CTRL><ALT><F1>
>>>> ), and, in /var/log/syslog , from whence the extract is copied.
>>>>
>>>> "
>>>> 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)
>>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996887] pcieport
>>>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996893] pcieport
>>>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>>>> id=00e8(Receiver ID)
>>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996896] pcieport
>>>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>>>> Jul 27 00:07:08 bret-MD34045-2521 kernel: [332515.996898] pcieport
>>>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059307] pcieport
>>>> 0000:00:1d.0: AER: Corrected error received: id=00e8
>>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059314] pcieport
>>>> 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,
>>>> id=00e8(Receiver ID)
>>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059316] pcieport
>>>> 0000:00:1d.0:   device [8086:a298] error status/mask=00000001/00002000
>>>> Jul 27 00:07:28 bret-MD34045-2521 kernel: [332536.059318] pcieport
>>>> 0000:00:1d.0:    [ 0] Receiver Error         (First)
>>>> "
>>>>
>>>> "
>>>> 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
>>>> "
>>>>
>>>> Whilst I do not know how to get uname to show the Ubuntu version
>>>> number, the console shows it as 18.04.2 .
>>>
>>> What does
>>>
>>> lspci
>>>
>>> display?
>>>
>>> Specificly, what sort of device is at
>>>
>>> 00:1d.0
>>>
>>> ?
>>>
>>> It looks like whatever is at the point of the PCI bus is having trouble.
>>>
>>> Also: what does the dmesg command display?
>>>
>>>>
>>>>
>>>> Thank you in anticipation.
>>>>
>>>
>>> --
>>> 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
>>>
>>
>> I have made two attempts to reply to the above message. They have
>> apparently failed.
>>
>> My / partition has been progressively filled, over the last few hours;
>> df -h shows the partition size to be 92GB.
>>
>> The /home partition is a separate partition, of about the same (92GB)
>> size.
>>
>> I will try to reboot, to find whether that clears the muck from the /
>> partition.
>>
>
>
> I rebooted the computer, and, it did not go to the GUI lohin screen -
> it stopped at a console login screen.
>
> So, I logged in at the console, and then ran
> sudo apt autoclean
> and then it went straight to the GUI login screen.
>
> The autoclean appears to have freed up 2.3GB out of the 60-odd GB that
> nappears to be full of muck.
>
> "
> 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   85G  2.2G  98% /
> tmpfs            16G  4.0M   16G   1% /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   44K  3.2G   1% /run/user/1000
> "
>
> Well, it appears to have been overturned, because, then, I got a no
> free space left on device warning - 0GB left on /  .
>


In looking at folders in / , I find
/var is 81.5GB

/var/log is 78.9GB

/var/log/lightdm is 48.3GB

/var/log/journal is 1.5GB

and

Xorg.0.log.old is 29.1GB (can I delete that?)

Should that lightdm thing really be that big?

--
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
hi,
Am Sonntag, den 28.07.2019, 03:17 +0800 schrieb Bret Busby:


> In looking at folders in / , I find
> /var is 81.5GB
>
> /var/log is 78.9GB
>
> /var/log/lightdm is 48.3GB
>
> /var/log/journal is 1.5GB
>
> and
>
> Xorg.0.log.old is 29.1GB (can I delete that?)
yes, it will be re-created on next Xorg startup

>
> Should that lightdm thing really be that big?

no, it should definitely not ...

do you have logrotate installed (this is typically in every default
ubuntu install and makes sure to compress logs and rotate them so not
too much space gets used up in /var/log)

check with:

dpkg -l | grep logrotate

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 Sat, Jul 27, 2019 at 09:26:41PM +0200, Oliver Grawert wrote:

> hi,
> Am Sonntag, den 28.07.2019, 03:17 +0800 schrieb Bret Busby:
> > 
> > In looking at folders in / , I find
> > /var is 81.5GB
> >
> > /var/log is 78.9GB
> >
> > /var/log/lightdm is 48.3GB
> >
> > /var/log/journal is 1.5GB
> >
> > and
> >
> > Xorg.0.log.old is 29.1GB (can I delete that?)
>
> yes, it will be re-created on next Xorg startup
>
> >
> > Should that lightdm thing really be that big?
>
> no, it should definitely not ...
>
> do you have logrotate installed (this is typically in every default
> ubuntu install and makes sure to compress logs and rotate them so not
> too much space gets used up in /var/log)
>
> check with:
>
> dpkg -l | grep logrotate
These are the directory sizes, while logrotate can compress old ones there is not
a good reason for Gb of log messages. The pci problem suggests
an infinite mesage loop -I used to get that all the time from
misconfigured nullmaileri this may be a hardware issue. Just tail the most recent file in the directories
and see if it is a repeated message.

It may be worth reducing runlevel or booting single user etc until
you can kill whatever generates this and sort it out.







>
> ciao
> oli



> --
> 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
In reply to this post by Oliver Grawert
On 28/07/2019, Oliver Grawert <[hidden email]> wrote:

> hi,
> Am Sonntag, den 28.07.2019, 03:17 +0800 schrieb Bret Busby:
>>
>> In looking at folders in / , I find
>> /var is 81.5GB
>>
>> /var/log is 78.9GB
>>
>> /var/log/lightdm is 48.3GB
>>
>> /var/log/journal is 1.5GB
>>
>> and
>>
>> Xorg.0.log.old is 29.1GB (can I delete that?)
>
> yes, it will be re-created on next Xorg startup
>
>>
>> Should that lightdm thing really be that big?
>
> no, it should definitely not ...
>
> do you have logrotate installed (this is typically in every default
> ubuntu install and makes sure to compress logs and rotate them so not
> too much space gets used up in /var/log)
>
> check with:
>
> dpkg -l | grep logrotate
>
> ciao
> oli
>

"
:~$ dpkg -l | grep logrotate
ii  logrotate                                     3.11.0-0.1ubuntu1
                       amd64        Log rotation utility
"


--
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

ubuntu-users mailing list
In reply to this post by Bret Busby-2
On Sat, 27 Jul 2019 20:54:19 +0800, Bret Busby wrote:
>Whilst I do not know how to get uname to show the Ubuntu version
>number, the console shows it as 18.04.2 .

http://manpages.ubuntu.com/manpages/bionic/man1/lsb_release.1.html

[weremouse@moonstudio ~]$ lsb_release -a
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial


--
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 28/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Sat, Jul 27, 2019 at 09:26:41PM +0200, Oliver Grawert wrote:
>> hi,
>> Am Sonntag, den 28.07.2019, 03:17 +0800 schrieb Bret Busby:
>> >
>> > In looking at folders in / , I find
>> > /var is 81.5GB
>> >
>> > /var/log is 78.9GB
>> >
>> > /var/log/lightdm is 48.3GB
>> >
>> > /var/log/journal is 1.5GB
>> >
>> > and
>> >
>> > Xorg.0.log.old is 29.1GB (can I delete that?)
>>
>> yes, it will be re-created on next Xorg startup
>>
>> >
>> > Should that lightdm thing really be that big?
>>
>> no, it should definitely not ...
>>
>> do you have logrotate installed (this is typically in every default
>> ubuntu install and makes sure to compress logs and rotate them so not
>> too much space gets used up in /var/log)
>>
>> check with:
>>
>> dpkg -l | grep logrotate
> These are the directory sizes, while logrotate can compress old ones there
> is not
> a good reason for Gb of log messages. The pci problem suggests
> an infinite mesage loop -I used to get that all the time from
> misconfigured nullmaileri this may be a hardware issue. Just tail the most
> recent file in the directories
> and see if it is a repeated message.
>
> It may be worth reducing runlevel or booting single user etc until
> you can kill whatever generates this and sort it out.
>


The PCI error is repeated, and, is for a single device;

device [8086:a298]

from

"
[ 3518.680157] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
[ 3518.680163] pcieport 0000:00:1d.0: PCIe Bus Error:
severity=Corrected, type=Physical Layer, id=00e8(Receiver ID)
[ 3518.680166] pcieport 0000:00:1d.0:   device [8086:a298] error
status/mask=00000001/00002000
[ 3518.680168] pcieport 0000:00:1d.0:    [ 0] Receiver Error         (First)
[ 3583.968465] pcieport 0000:00:1d.0: AER: Corrected error received: id=00e8
"

"
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root
Port #9 (rev f0)
"

I have no idea as to what is that device; othe than a "PCI bridge" (?).

--
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 ubuntu-users mailing list
On 28/07/2019, Ralf Mardorf via ubuntu-users
<[hidden email]> wrote:

> On Sat, 27 Jul 2019 20:54:19 +0800, Bret Busby wrote:
>>Whilst I do not know how to get uname to show the Ubuntu version
>>number, the console shows it as 18.04.2 .
>
> http://manpages.ubuntu.com/manpages/bionic/man1/lsb_release.1.html
>
> [weremouse@moonstudio ~]$ lsb_release -a
> LSB
> Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
> Distributor ID: Ubuntu
> Description: Ubuntu 16.04.6 LTS
> Release: 16.04
> Codename: xenial
>
>

Thank you for that.

"
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
"


--
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 Mike Marchywka
On 28/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Sat, Jul 27, 2019 at 09:26:41PM +0200, Oliver Grawert wrote:
>> hi,
>> Am Sonntag, den 28.07.2019, 03:17 +0800 schrieb Bret Busby:
>> >
>> > In looking at folders in / , I find
>> > /var is 81.5GB
>> >
>> > /var/log is 78.9GB
>> >
>> > /var/log/lightdm is 48.3GB
>> >
>> > /var/log/journal is 1.5GB
>> >
>> > and
>> >
>> > Xorg.0.log.old is 29.1GB (can I delete that?)
>>
>> yes, it will be re-created on next Xorg startup
>>
>> >
>> > Should that lightdm thing really be that big?
>>
>> no, it should definitely not ...
>>
>> do you have logrotate installed (this is typically in every default
>> ubuntu install and makes sure to compress logs and rotate them so not
>> too much space gets used up in /var/log)
>>
>> check with:
>>
>> dpkg -l | grep logrotate
> These are the directory sizes, while logrotate can compress old ones there
> is not
> a good reason for Gb of log messages.

In /var/log/lightdm , is
x-0.log
size: 48.2GB





The pci problem suggests
> an infinite mesage loop -I used to get that all the time from
> misconfigured nullmaileri this may be a hardware issue. Just tail the most
> recent file in the directories
> and see if it is a repeated message.

"
bret@bret-MD34045-2521:~$ tail /var/log/lightdm/x-0.log
tail: cannot open '/var/log/lightdm/x-0.log' for reading: Permission denied
bret@bret-MD34045-2521:~$ sudo tail /var/log/lightdm/x-0.log
[sudo] password for bret:
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: Sun Jul 28 02:49:58 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
bret@bret-MD34045-2521:~$ sudo tail -30 /var/log/lightdm/x-0.log
         at http://wiki.x.org
 for help.
(EE)
(EE)
Fatal server error:
(EE) Could not write pid to lock file in /tmp/.tX0-lock
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE)

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: Sun Jul 28 02:49:58 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
"





--
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 28/07/2019, Bret Busby <[hidden email]> wrote:

> On 28/07/2019, Mike Marchywka <[hidden email]> wrote:
>> On Sat, Jul 27, 2019 at 09:26:41PM +0200, Oliver Grawert wrote:
>>> hi,
>>> Am Sonntag, den 28.07.2019, 03:17 +0800 schrieb Bret Busby:
>>> >
>>> > In looking at folders in / , I find
>>> > /var is 81.5GB
>>> >
>>> > /var/log is 78.9GB
>>> >
>>> > /var/log/lightdm is 48.3GB
>>> >
>>> > /var/log/journal is 1.5GB
>>> >
>>> > and
>>> >
>>> > Xorg.0.log.old is 29.1GB (can I delete that?)
>>>
>>> yes, it will be re-created on next Xorg startup
>>>
>>> >
>>> > Should that lightdm thing really be that big?
>>>
>>> no, it should definitely not ...
>>>
>>> do you have logrotate installed (this is typically in every default
>>> ubuntu install and makes sure to compress logs and rotate them so not
>>> too much space gets used up in /var/log)
>>>
>>> check with:
>>>
>>> dpkg -l | grep logrotate
>> These are the directory sizes, while logrotate can compress old ones
>> there
>> is not
>> a good reason for Gb of log messages.
>
> In /var/log/lightdm , is
> x-0.log
> size: 48.2GB
>
>


Can and should I delete that file?

Years ago,  a partition size of 20GB for / was regarded as quite
adequate, and, this file, alone, takes more space than the rest of the
content of the / partition.

--
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 Sun, Jul 28, 2019 at 04:06:45AM +0800, Bret Busby wrote:
> On 28/07/2019, Mike Marchywka <[hidden email]> wrote:
> > On Sat, Jul 27, 2019 at 09:26:41PM +0200, Oliver Grawert wrote:
> >>
> >> dpkg -l | grep logrotate

I thought you had dirs there, I always use du -sbc on directories to hunt down :)

Installation is not the same as functioning, you should be able to see the old
versions gzipped if it is working and configured right. Again though
burning through that much disk space that fast and having a file that big
for "normal" usage is odd although I don't know your history.


> > These are the directory sizes, while logrotate can compress old ones there
> > is not
> > a good reason for Gb of log messages.
>
> In /var/log/lightdm , is
> x-0.log
> size: 48.2GB
>
>
>
>
>
> The pci problem suggests
> > an infinite mesage loop -I used to get that all the time from
> > misconfigured nullmaileri this may be a hardware issue. Just tail the most
> > recent file in the directories
> > and see if it is a repeated message.
>
> "
> bret@bret-MD34045-2521:~$ tail /var/log/lightdm/x-0.log
> tail: cannot open '/var/log/lightdm/x-0.log' for reading: Permission denied
> bret@bret-MD34045-2521:~$ sudo tail /var/log/lightdm/x-0.log
> [sudo] password for bret:
> 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: Sun Jul 28 02:49:58 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> bret@bret-MD34045-2521:~$ sudo tail -30 /var/log/lightdm/x-0.log
> at http://wiki.x.org
>  for help.
> (EE)
> (EE)
> Fatal server error:
> (EE) Could not write pid to lock file in /tmp/.tX0-lock

I'm not really sure what to make of this as bad locks can lead to bizarre problems
.   I guess you could check the obvious,
the logs should be readable by all too,

ls -al /var/log | grep X
-rw-r--r--  1 root              root    37198 Jul 20 20:41 Xorg.0.log
-rw-r--r--  1 root              root    42732 Jul  8 17:35 Xorg.0.log.old
-rw-r--r--  1 root              root    32892 Jul  5 17:52 Xorg.1.log
-rw-r--r--  1 root              root    32892 Jul  5 17:14 Xorg.1.log.old
marchywka@happy:/home/documents/latex/proj/happyheart$ ls -al /tmp | head -n 2
total 1164
drwxrwxrwt 19 root      root      1081344 Jul 27 17:01 .


And I'm not sure the Xorg thing is rotated by default,

more /etc/logrotate.d/
apport               iptraf-ng            speech-dispatcher
apt                  lightdm              ufw
cups-daemon          pm-utils             unattended-upgrades
dpkg                 ppp                  upstart
hibernate            rsyslog              



> (EE)
> (EE)
> Please consult the The X.Org Foundation support
> at http://wiki.x.org
>  for help.
> (EE)
>
> 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: Sun Jul 28 02:49:58 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> "
>
>
>
>
>
> --
> 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 28/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Sun, Jul 28, 2019 at 04:06:45AM +0800, Bret Busby wrote:
>> On 28/07/2019, Mike Marchywka <[hidden email]> wrote:
>> > On Sat, Jul 27, 2019 at 09:26:41PM +0200, Oliver Grawert wrote:
>> >>
>> >> dpkg -l | grep logrotate
>
> I thought you had dirs there, I always use du -sbc on directories to hunt
> down :)
>
> Installation is not the same as functioning, you should be able to see the
> old
> versions gzipped if it is working and configured right. Again though
> burning through that much disk space that fast and having a file that big
> for "normal" usage is odd although I don't know your history.
>
>
>> > These are the directory sizes, while logrotate can compress old ones
>> > there
>> > is not
>> > a good reason for Gb of log messages.
>>
>> In /var/log/lightdm , is
>> x-0.log
>> size: 48.2GB
>>
>>
>>
>>
>>
>> The pci problem suggests
>> > an infinite mesage loop -I used to get that all the time from
>> > misconfigured nullmaileri this may be a hardware issue. Just tail the
>> > most
>> > recent file in the directories
>> > and see if it is a repeated message.
>>
>> "
>> bret@bret-MD34045-2521:~$ tail /var/log/lightdm/x-0.log
>> tail: cannot open '/var/log/lightdm/x-0.log' for reading: Permission
>> denied
>> bret@bret-MD34045-2521:~$ sudo tail /var/log/lightdm/x-0.log
>> [sudo] password for bret:
>> 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: Sun Jul 28 02:49:58 2019
>> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>> bret@bret-MD34045-2521:~$ sudo tail -30 /var/log/lightdm/x-0.log
>> at http://wiki.x.org
>>  for help.
>> (EE)
>> (EE)
>> Fatal server error:
>> (EE) Could not write pid to lock file in /tmp/.tX0-lock
>
> I'm not really sure what to make of this as bad locks can lead to bizarre
> problems
> .   I guess you could check the obvious,
> the logs should be readable by all too,
>
> ls -al /var/log | grep X
> -rw-r--r--  1 root              root    37198 Jul 20 20:41 Xorg.0.log
> -rw-r--r--  1 root              root    42732 Jul  8 17:35 Xorg.0.log.old
> -rw-r--r--  1 root              root    32892 Jul  5 17:52 Xorg.1.log
> -rw-r--r--  1 root              root    32892 Jul  5 17:14 Xorg.1.log.old
> marchywka@happy:/home/documents/latex/proj/happyheart$ ls -al /tmp | head -n
> 2
> total 1164
> drwxrwxrwt 19 root      root      1081344 Jul 27 17:01 .
>
>
> And I'm not sure the Xorg thing is rotated by default,
>
> more /etc/logrotate.d/
> apport               iptraf-ng            speech-dispatcher
> apt                  lightdm              ufw
> cups-daemon          pm-utils             unattended-upgrades
> dpkg                 ppp                  upstart
> hibernate            rsyslog
>
>
>


"
bret@bret-MD34045-2521:~$ more /etc/logrotate.d/

*** /etc/logrotate.d/: directory ***

bret@bret-MD34045-2521:~$ ls -al /var/log | grep X
-rw-r--r--   1 root              root               46756 Jul 28 02:50
Xorg.0.log

bret@bret-MD34045-2521:~$ ls -al /tmp | head -n 2
total 80
drwxrwxrwt 18 root root 4096 Jul 28 04:46 .
"

--
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
1234