Участник с: 30 декабря 2011
|
У меня (руки из жопы) Я известный гуманитарий со стажем.
Можно было бы толерантненько наслаждаться обществом Билли, но давно уже предпочитаю проживать в персональном эцихе с гвоздями под лейблом Арч. Это умные не любят в гору ходить, а мы предпочитаем горы пробивать лбами.
Ну вот сегодня как раз появились "звёзды из глаз":
( ~ ) >> journalctl -b -p err
-- Logs begin at Fri 2017-06-30 20:42:40 +05, end at Wed 2017-07-05 16:25:06 +05. --
Jul 03 16:42:32 pampas kernel: ACPI Error: Needed type [Reference], found [Integer] ffff8801a84f1c18 (20170119/exresop-103)
Jul 03 16:42:32 pampas kernel: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170119/dswexec-461)
Jul 03 16:42:32 pampas kernel: ACPI Error: Method parse/execution failed [\_PR.CPU0._PDC] (Node ffff8801a84edaa0), AE_AML_OPERAND_TYPE (20170119/psparse-543)
Jul 03 19:38:50 pampas kernel: usb 1-1.1: device descriptor read/64, error -110
Jul 03 19:38:57 pampas kernel: Bluetooth: hci0 command 0x0c25 tx timeout
Jul 03 19:39:00 pampas kernel: Bluetooth: hci0 command 0x0c38 tx timeout
Jul 03 19:39:02 pampas kernel: Bluetooth: hci0 command 0x0c39 tx timeout
Jul 03 19:39:04 pampas kernel: Bluetooth: hci0 command 0x0c05 tx timeout
Jul 03 19:39:06 pampas kernel: Bluetooth: hci0 command tx timeout
Jul 03 20:55:09 pampas kernel: usb 1-1.1: device descriptor read/64, error -110
Jul 04 07:26:05 pampas kernel: usb 1-1.1: device descriptor read/64, error -110
Jul 04 07:26:15 pampas kernel: usb 1-1.1: device not accepting address 10, error -32
Jul 04 09:09:08 pampas kernel: usb 1-1.1: device descriptor read/64, error -110
Jul 04 09:09:19 pampas kernel: usb 1-1.1: device not accepting address 13, error -32
Jul 04 09:09:21 pampas kernel: Bluetooth: hci0 command 0x1009 tx timeout
Jul 04 15:53:06 pampas kernel: usb 1-1.1: device descriptor read/64, error -110
Jul 05 10:23:45 pampas kernel: usb 1-1.1: device descriptor read/64, error -110
Jul 05 11:49:54 pampas kernel: usb 1-1.1: device descriptor read/64, error -110
Jul 05 11:50:05 pampas kernel: usb 1-1.1: device not accepting address 22, error -32
Jul 05 12:53:39 pampas kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
Jul 05 12:53:39 pampas kernel: ata1.00: irq_stat 0x00400040, connection status changed
Jul 05 12:53:39 pampas kernel: ata1: SError: { HostInt PHYRdyChg 10B8B DevExch }
Jul 05 12:53:39 pampas kernel: ata1.00: failed command: FLUSH CACHE EXT
Jul 05 12:53:39 pampas kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 20
res 40/00:9c:28:f0:87/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
Jul 05 12:53:39 pampas kernel: ata1.00: status: { DRDY }
"ACPI", я так понимаю - это про неапгрейдинный БИОС. "Bluetooth и usb 1-1.1" - недоустановленный драйвер под "синий зуб" Но созерцая "ata1.00" - "что-то мне сыкотно" (С)
"ACPI" и "Bluetooth и usb 1-1.1" - это давно радует, а "а-та-та" - сегодня
Ну и история болезни:
( ~ ) >> uname -a
Linux pampas 4.11.7-1-ARCH #1 SMP PREEMPT Sat Jun 24 09:07:09 CEST 2017 x86_64 GNU/Linux
( ~ ) >> df -h
Filesystem Size Used Avail Use% Mounted on
dev 2.9G 0 2.9G 0% /dev
run 2.9G 776K 2.9G 1% /run
/dev/sda1 29G 9.7G 19G 34% /
tmpfs 2.9G 160K 2.9G 1% /dev/shm
tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup
tmpfs 2.9G 66M 2.8G 3% /tmp
/dev/sdb1 466G 100G 367G 22% /mnt/base
/dev/sda2 20G 7.0G 12G 37% /home
/dev/sda4 415G 89G 327G 22% /mnt/win
tmpfs 586M 16K 586M 1% /run/user/1000
( ~ ) >> lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 29.3G 0 part /
├─sda2 8:2 0 19.5G 0 part /home
├─sda3 8:3 0 2G 0 part
└─sda4 8:4 0 415G 0 part /mnt/win
sdb 8:16 0 465.8G 0 disk
└─sdb1 8:17 0 465.8G 0 part /mnt/base
sr0 11:0 1 1024M 0 rom
( ~ ) >> lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc.
Bus 001 Device 024: ID 13d3:3362 IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 15d9:0a4f Trust International B.V. Optical Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
( ~ ) >> lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 635M] (rev ff)
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
04:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10) P.S. Ага, про арч вей читал... не помогло
|