#1 Le 06/11/2019, à 15:54
- xanmoo
des erreurs au boot, c'est grave docteur?
Bonjour,
Depuis quelques temps, je note un message d'erreur pendant le boot concernant un périphérique firewire:
$ dmesg -l err
[ 4.174246] firewire_ohci 0000:07:04.0: failed to read phy reg 4
En regardant de plus près cela donne:
$ dmesg -l err,crit,warn
[ 0.031820] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20181213/tbfadt-569)
[ 0.317895] ACPI BIOS Warning (bug): Incorrect checksum in table [TCPA] - 0x00, should be 0x7F (20181213/tbprint-177)
[ 0.317901] ACPI BIOS Warning (bug): Incorrect checksum in table [_RAT] - 0x00, should be 0x63 (20181213/tbprint-177)
[ 0.318058] DMAR-IR: This system BIOS has enabled interrupt remapping
on a chipset that contains an erratum making that
feature unstable. To maintain system stability
interrupt remapping is being disabled. Please
contact your BIOS vendor for an update
[ 0.453183] core: CPUID marked event: 'bus cycles' unavailable
[ 0.464543] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[ 0.464543] #5 #6 #7
[ 0.815314] Expanded resource Reserved due to conflict with PCI Bus 0000:00
[ 0.815314] Expanded resource Reserved due to conflict with PCI Bus 0000:00
[ 0.835013] pnp 00:00: disabling [io 0x0800-0x085f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x0800-0x087f]
[ 0.835015] pnp 00:00: disabling [io 0x0860-0x08ff] because it overlaps 0000:00:1f.0 BAR 13 [io 0x0800-0x087f]
[ 2.668084] platform eisa.0: EISA: Cannot allocate resource for mainboard
[ 2.668085] platform eisa.0: Cannot allocate resource for EISA slot 1
[ 2.668086] platform eisa.0: Cannot allocate resource for EISA slot 2
[ 2.668087] platform eisa.0: Cannot allocate resource for EISA slot 3
[ 2.668088] platform eisa.0: Cannot allocate resource for EISA slot 4
[ 2.668089] platform eisa.0: Cannot allocate resource for EISA slot 5
[ 2.668090] platform eisa.0: Cannot allocate resource for EISA slot 6
[ 2.668091] platform eisa.0: Cannot allocate resource for EISA slot 7
[ 2.668092] platform eisa.0: Cannot allocate resource for EISA slot 8
[ 2.858131] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
[ 2.898497] nvidia: loading out-of-tree module taints kernel.
[ 2.898508] nvidia: module license 'NVIDIA' taints kernel.
[ 2.898509] Disabling lock debugging due to kernel taint
[ 3.015257] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 418.87.01 Wed Sep 25 06:00:38 UTC 2019
[ 4.174246] firewire_ohci 0000:07:04.0: failed to read phy reg 4
[ 4.175471] CPU: 2 PID: 254 Comm: systemd-udevd Tainted: P IOE 5.0.0-32-generic #34~18.04.2-Ubuntu
[ 4.175472] Hardware name: Dell Inc. Precision WorkStation T5500 /0D883F, BIOS A02 05/28/2009
[ 4.175473] Call Trace:
[ 4.175479] dump_stack+0x63/0x85
[ 4.175482] read_phy_reg+0x8d/0xa0 [firewire_ohci]
[ 4.175485] update_phy_reg+0x20/0x50 [firewire_ohci]
[ 4.175487] ohci_update_phy_reg+0x3e/0x60 [firewire_ohci]
[ 4.175490] ohci_enable+0x1d1/0x4c0 [firewire_ohci]
[ 4.175494] fw_card_add+0x4f/0xa0 [firewire_core]
[ 4.175496] pci_probe+0x5c5/0x65f [firewire_ohci]
[ 4.175500] local_pci_probe+0x47/0xa0
[ 4.175502] pci_device_probe+0x10e/0x1c0
[ 4.175504] really_probe+0xfe/0x3f0
[ 4.175506] driver_probe_device+0x11a/0x130
[ 4.175507] __driver_attach+0x114/0x120
[ 4.175508] ? driver_probe_device+0x130/0x130
[ 4.175509] ? driver_probe_device+0x130/0x130
[ 4.175512] bus_for_each_dev+0x74/0xb0
[ 4.175515] ? kmem_cache_alloc_trace+0x1a6/0x1c0
[ 4.175516] driver_attach+0x1e/0x20
[ 4.175518] bus_add_driver+0x167/0x260
[ 4.175519] ? 0xffffffffc03c5000
[ 4.175520] driver_register+0x60/0x100
[ 4.175521] ? 0xffffffffc03c5000
[ 4.175523] __pci_register_driver+0x5a/0x60
[ 4.175525] fw_ohci_init+0x4f/0x1000 [firewire_ohci]
[ 4.175528] do_one_initcall+0x4a/0x1c9
[ 4.175530] ? _cond_resched+0x19/0x40
[ 4.175531] ? kmem_cache_alloc_trace+0x42/0x1c0
[ 4.175534] do_init_module+0x5f/0x216
[ 4.175535] load_module+0x1a80/0x20c0
[ 4.175538] __do_sys_finit_module+0xfc/0x120
[ 4.175539] ? __do_sys_finit_module+0xfc/0x120
[ 4.175541] __x64_sys_finit_module+0x1a/0x20
[ 4.175543] do_syscall_64+0x5a/0x120
[ 4.175545] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 4.175546] RIP: 0033:0x7fafe2488839
[ 4.175547] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 1f f6 2c 00 f7 d8 64 89 01 48
[ 4.175548] RSP: 002b:00007fffb81179b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[ 4.175550] RAX: ffffffffffffffda RBX: 000055ee0f8ae5d0 RCX: 00007fafe2488839
[ 4.175551] RDX: 0000000000000000 RSI: 00007fafe2167145 RDI: 000000000000000d
[ 4.175551] RBP: 00007fafe2167145 R08: 0000000000000000 R09: 00007fffb8117ad0
[ 4.175552] R10: 000000000000000d R11: 0000000000000246 R12: 0000000000000000
[ 4.175553] R13: 000055ee0f8970e0 R14: 0000000000020000 R15: 000055ee0f8ae5d0
[ 4.175862] firewire_ohci: probe of 0000:07:04.0 failed with error -16
[ 5.529953] ashmem_linux: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.223194] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000828-0x000000000000082D (\GLBC) (20181213/utaddress-213)
[ 6.223202] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x000000000000082A-0x000000000000082A (\SACT) (20181213/utaddress-213)
[ 6.223207] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000828-0x0000000000000828 (\SSTS) (20181213/utaddress-213)
[ 6.223257] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 6.349960] dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
[ 6.418999] resource sanity check: requesting [mem 0x000e0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000effff window]
[ 6.419328] caller os_map_kernel_space.part.9+0x74/0x90 [nvidia] mapping multiple BARs
[ 6.449029] kvm: disabled by bios
[ 6.781898] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000effff window]
[ 6.782146] caller os_map_kernel_space.part.9+0x74/0x90 [nvidia] mapping multiple BARs
[ 7.260556] kvm: disabled by bios
[ 7.376683] kvm: disabled by bios
[ 7.984146] kvm: disabled by bios
[ 8.041071] kvm: disabled by bios
[ 8.136913] kvm: disabled by bios
[ 8.180605] kvm: disabled by bios
[ 8.220394] kvm: disabled by bios
[ 8.268693] kvm: disabled by bios
Il est vrai que la version du bios, A2, est très ancienne. Des conseils?
merci
Dernière modification par xanmoo (Le 06/11/2019, à 15:56)
Portable IBM Thinkpad R50e 2 Go | 40 Go: MX Linux 19.4
Portable IBM Thinkpad T430 8 Go | 240 Go: endeavour OS
Dell Precision T5500, Xeon x5570, 24Go, GTX 960- 4Go, SSD 120Go, Ubuntu 22.04
http://dip4fish.blogspot.com/
Hors ligne
#2 Le 06/11/2019, à 16:15
- LeJediGris
Re : des erreurs au boot, c'est grave docteur?
Salut,
Bah si tu n'utilises pas le FireWire (IEEE 1394 pour les intimes) pas de PB. Ceci dit d'autres lignes du dmesg font effectivement penser à un BIOS obsolète. Il y a t-il un BIOS plus récent sur le site de Dell ?
A+
%NOINDEX%
Matos Asus Zenbook
"Home Made" Monstro: core i7 9700+32Go de mémoire+SSD QVO Samsung 1To +MoBo Asus Prime Z390P
+ "Terminator", core i5 3570, 16Go, SSD Intel 520 sous Mint 19.3, Freebox Revolution
Hors ligne
#3 Le 06/11/2019, à 16:20
- xanmoo
Re : des erreurs au boot, c'est grave docteur?
Oui, il y a des bios plus récents, mais à installer depuis windows 7 ou depuis une redhat entreprise. La mise à jour étant génératrice de sueurs froides ...je préfère m'abstenir de l'aventure si possible.
Dernière modification par xanmoo (Le 06/11/2019, à 16:29)
Portable IBM Thinkpad R50e 2 Go | 40 Go: MX Linux 19.4
Portable IBM Thinkpad T430 8 Go | 240 Go: endeavour OS
Dell Precision T5500, Xeon x5570, 24Go, GTX 960- 4Go, SSD 120Go, Ubuntu 22.04
http://dip4fish.blogspot.com/
Hors ligne
#4 Le 06/11/2019, à 16:32
- LeJediGris
Re : des erreurs au boot, c'est grave docteur?
Re-
A priori sur les BIOS bien élevés il y a possibilité d'upgrade depuis le BIOS lui-même en ayant la MaJ du BIOS sur une clé USB ou sur la racine du disque "C" pour windows (donc à priori le disque de boot).
Je le fais régulièrement et je n'ai jamais eu de PB, le seul truc c'est de ne pas éteindre/débrancher pendant la MaJ.
A+
%NOINDEX%
Matos Asus Zenbook
"Home Made" Monstro: core i7 9700+32Go de mémoire+SSD QVO Samsung 1To +MoBo Asus Prime Z390P
+ "Terminator", core i5 3570, 16Go, SSD Intel 520 sous Mint 19.3, Freebox Revolution
Hors ligne
#5 Le 06/11/2019, à 17:29
- xanmoo
Re : des erreurs au boot, c'est grave docteur?
je n'ai pas l'impression que le bios soit bien élevé, je n'ai rien vu ressemblant à la possibilité d'une mise à jour.
Portable IBM Thinkpad R50e 2 Go | 40 Go: MX Linux 19.4
Portable IBM Thinkpad T430 8 Go | 240 Go: endeavour OS
Dell Precision T5500, Xeon x5570, 24Go, GTX 960- 4Go, SSD 120Go, Ubuntu 22.04
http://dip4fish.blogspot.com/
Hors ligne