Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-19-2019, 04:14 PM
|
#1
|
|
LQ Newbie
Registered: Dec 2006
Posts: 10
Rep: 
|
Ubunt 18.04 start up errors.
I do not understand these errors. What can I do about them?
dmesg | grep error
[ 4.439358] ACPI Error: Aborting method \_SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
[ 4.439396] ACPI Error: Aborting method \_SB.PCI0.VGA.ATCS due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
[ 7.523297] usb 10-1: device descriptor read/64, error -110
[ 23.011293] usb 10-1: device descriptor read/64, error -110
[ 28.387291] usb 10-1: device descriptor read/64, error -110
[ 43.875289] usb 10-1: device descriptor read/64, error -110
[ 49.763292] usb 10-1: device descriptor read/64, error -110
[ 65.251290] usb 10-1: device descriptor read/64, error -110
[ 70.627294] usb 10-1: device descriptor read/64, error -110
[ 86.115294] usb 10-1: device descriptor read/64, error -110
[ 87.001713] print_req_error: I/O error, dev sr0, sector 0 flags 80700
[ 87.023669] print_req_error: I/O error, dev sr0, sector 0 flags 0
[ 87.023674] Buffer I/O error on dev sr0, logical block 0, async page read
[ 96.483320] usb 10-1: device descriptor read/64, error -110
|
|
|
|
|
09-19-2019, 04:42 PM
|
#2
|
|
LQ Veteran
Registered: Feb 2013
Location: Tucson, AZ, USA
Distribution: Rocky 9.5
Posts: 5,885
|
Quote:
Originally Posted by robbyx
I do not understand these errors. What can I do about them?
Code:
dmesg | grep error
[ 4.439358] ACPI Error: Aborting method \_SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
[ 4.439396] ACPI Error: Aborting method \_SB.PCI0.VGA.ATCS due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
[ 7.523297] usb 10-1: device descriptor read/64, error -110
[ 23.011293] usb 10-1: device descriptor read/64, error -110
[ 28.387291] usb 10-1: device descriptor read/64, error -110
[ 43.875289] usb 10-1: device descriptor read/64, error -110
[ 49.763292] usb 10-1: device descriptor read/64, error -110
[ 65.251290] usb 10-1: device descriptor read/64, error -110
[ 70.627294] usb 10-1: device descriptor read/64, error -110
[ 86.115294] usb 10-1: device descriptor read/64, error -110
[ 87.001713] print_req_error: I/O error, dev sr0, sector 0 flags 80700
[ 87.023669] print_req_error: I/O error, dev sr0, sector 0 flags 0
[ 87.023674] Buffer I/O error on dev sr0, logical block 0, async page read
[ 96.483320] usb 10-1: device descriptor read/64, error -110
|
Is there anything plugged into that usb port? What? |
|
|
|
|
09-20-2019, 07:44 AM
|
#3
|
|
Senior Member
Registered: Oct 2008
Distribution: Debian sid
Posts: 2,683
|
looks like it could be an external optical drive
with a bad cd/dvd/br or faulty usb/power cable
|
|
|
|
|
09-21-2019, 10:32 AM
|
#4
|
|
LQ Newbie
Registered: Dec 2006
Posts: 10
Original Poster
Rep:
|
Thany you for your comment.
The following shows that the 10-1 device is not currently giving a fault. I hope it stays that way.
Quote:
dmesg | grep error
[ 4.412823] ACPI Error: Aborting method \_SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
[ 4.412862] ACPI Error: Aborting method \_SB.PCI0.VGA.ATCS due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
[ 5.283019] print_req_error: I/O error, dev sr0, sector 0 flags 80700
[ 5.304997] print_req_error: I/O error, dev sr0, sector 0 flags 0
[ 5.305002] Buffer I/O error on dev sr0, logical block 0, async page read
[ 1624.422208] qtdemux0:sink[5626]: segfault at 7f3a8000c000 ip 00007f3ad127e170 sp 00007f3a7906b698 error 6 in libc-2.27.so[7f3ad1110000+1e7000]
|
The reference to SR0 implies a dvd problem, as you suggested. I do not have an external dvd drive.
lsusb
Bus 015 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd External HD
Bus 015 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 014 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 013 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 012 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Unclear but may be a usb hub
Bus 012 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 002: ID 2109:0811 VIA Labs, Inc. Hub ditto
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 12d1:107e Huawei Technologies Co., Ltd. mobile phone
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 046d:c247 Logitech, Inc. mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
BTW I often find my screen freezes together with the mouse, and I have to wait 5-10 mins for it to be defrosted.
does this help?
Quote:
sudo blkid
[sudo] password for robins:
/dev/nvme0n1p1: UUID="ff16fdbe-9a30-4c73-89a4-bf10cd1b1974" UUID_SUB="8bbadc12-83ab-476b-92c3-a09c49dc1484" TYPE="btrfs" PARTUUID="36bdb116-01"
/dev/nvme0n1p2: UUID="5bb8aa95-b657-4297-be5b-4352a09596b0" UUID_SUB="12d8a1ae-9e45-4467-99d1-bae0e01b1c53" TYPE="btrfs" PARTUUID="36bdb116-02"
/dev/nvme0n1p4: LABEL="Data" UUID="f5ab46ce-b3da-4e59-8f18-3418fe272a09" UUID_SUB="62eb831e-e336-455d-9804-afed243f3c28" TYPE="btrfs" PARTUUID="36bdb116-04"
/dev/nvme0n1p5: LABEL="SWAP" UUID="4ec66d43-75bf-4f9e-8f36-13275a0f3258" TYPE="swap" PARTUUID="36bdb116-05"
/dev/nvme0n1p6: LABEL="EFI" UUID="C649-2797" TYPE="vfat" PARTUUID="36bdb116-06"
/dev/sda2: UUID="0414cae8-b4fe-48d6-b06f-9509c3f9f8cb" TYPE="ext4" PARTUUID="00083267-02"
/dev/sda3: UUID="bf95a4fd-9e7a-4a06-afed-e82fdb82ac63" TYPE="ext4" PARTUUID="00083267-03"
/dev/sda5: LABEL="mydocs" UUID="8d99bfc8-90ab-4488-b7da-87e7676aff19" TYPE="ext4" PARTUUID="00083267-05"
/dev/sda6: LABEL="Data inc AV" UUID="1a2e8d10-7b93-4de1-b551-31db6a621276" TYPE="ext4" PARTUUID="00083267-06"
/dev/sda7: UUID="B1BA-7E06" TYPE="vfat" PARTUUID="00083267-07"
/dev/sda8: UUID="02c1d09e-54db-4346-863d-1097ff0ed637" TYPE="swap" PARTUUID="00083267-08"
/dev/sdb1: LABEL="hitachi 750gb" UUID="3c4f4688-4bd7-4262-a2b8-86f71bbd6d0b" TYPE="ext4" PARTUUID="0008ffd0-01"
/dev/sdb2: LABEL="Deju_dup_backup" UUID="c79b648e-48c5-45db-949f-a835928f3816" TYPE="ext4" PARTUUID="0008ffd0-02"
/dev/sdc1: SEC_TYPE="msdos" LABEL="xhd_vfat" UUID="5933-1C4A" TYPE="vfat" PARTUUID="846a1f97-01"
/dev/sdc2: LABEL="xhd system data" UUID="23fcb4e3-c94e-44de-b7a9-105da58918c6" TYPE="ext4" PARTUUID="846a1f97-02"
/dev/sdc3: LABEL="xhd old bacs" UUID="c99be12f-3a2d-4411-ab7c-5696167482dc" TYPE="ext4" PARTUUID="846a1f97-03"
/dev/sdc4: LABEL="spare4" UUID="84a9cb0b-6006-4996-8b4a-2edc07cc25c4" TYPE="ext4" PARTUUID="846a1f97-04"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
/dev/loop21: TYPE="squashfs"
/dev/loop22: TYPE="squashfs"
/dev/loop23: TYPE="squashfs"
/dev/nvme0n1: PTUUID="36bdb116" PTTYPE="dos"
|
Last edited by robbyx; 09-21-2019 at 10:34 AM.
|
|
|
|
|
09-21-2019, 10:52 AM
|
#5
|
|
Senior Member
Registered: Oct 2008
Distribution: Debian sid
Posts: 2,683
|
if the screen froze, how do you know the mouse froze ?
the blkid won't help diagnose a problem with a frozen screen
https://gstreamer.freedesktop.org/do...4/qtdemux.html
are you working with .mov files on a possibly faulty dvd drive/disk ? |
|
|
|
|
09-21-2019, 01:04 PM
|
#6
|
|
LQ Newbie
Registered: Dec 2006
Posts: 10
Original Poster
Rep:
|
Quote:
Originally Posted by Firerat
if the screen froze, how do you know the mouse froze ?
|
i can not do anything with the screen via the mouse, so I assumed that both were in trouble.
the blkid won't help diagnose a problem with a frozen screen
https://gstreamer.freedesktop.org/do...4/qtdemux.html
are you working with .mov files on a possibly faulty dvd drive/disk ?
I have been watching streaming videos so the dvd drive/disk does not come into the problem |
|
|
|
|
09-21-2019, 02:02 PM
|
#7
|
|
Senior Member
Registered: Oct 2008
Distribution: Debian sid
Posts: 2,683
|
what are we trying to fix ?
|
|
|
|
|
09-21-2019, 03:01 PM
|
#8
|
|
LQ Newbie
Registered: Dec 2006
Posts: 10
Original Poster
Rep:
|
Quote:
Originally Posted by Firerat
what are we trying to fix ?
|
It started because I was getting those error messages from "dmesg | grep error" shown in the first post above.
Noting your comments I realised that another problem that I am also experiencing being that of the screen and mouse freezing may just be related to the first post so I included it in a response in case it could also be solved.
|
|
|
|
|
09-21-2019, 03:36 PM
|
#9
|
|
Senior Member
Registered: Oct 2008
Distribution: Debian sid
Posts: 2,683
|
well, qtdemux crashing like that may do screwy things and confuse the video cards drivers
so the mouse was probably fine, your video output froze
Code:
ACPI Error: Aborting method \_SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND)
but ..
what video card?
what drivers are you using?
Code:
print_req_error: I/O error, dev sr0, sector 0 flags 80700
this might just be that you have no disk in the drive |
|
|
|
|
09-22-2019, 07:08 AM
|
#10
|
|
LQ Addict
Registered: Dec 2013
Posts: 19,872
|
If you want to find as many errors as possible, you should grep case-insensitively:
Code:
dmesg | grep -i error
It's an interesting pastime.
That said, the usb errors from post #1 could have something to do with the mouse; could also be you un/plugged a USB stick sometinme during your session.
So this command:
Code:
dmesg | grep -i error
is best run immediately after a reboot.
Or immediately after a certain problem occurs.
If your computer freezes and you have to reboot, you might be better off looking at the journal:
only for errors
and
for the previous boot.
Combine to taste. |
|
|
|
|
09-22-2019, 07:57 AM
|
#11
|
|
Senior Member
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
|
Quote:
Originally Posted by robbyx
Code:
...
[ 87.001713] print_req_error: I/O error, dev sr0, sector 0 flags 80700
[ 87.023669] print_req_error: I/O error, dev sr0, sector 0 flags 0
[ 87.023674] Buffer I/O error on dev sr0, logical block 0, async page read
...
|
Since "sr0" refers to a CD/DVD drive, then first; does the CD/DVD play alright? Is the CD/DVD in the drive scratched?
It would appear the most likely reason for the above errors is that the CD/DVD in the drive is scratched/bad. |
|
|
|
All times are GMT -5. The time now is 07:04 AM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
