Debian-facile

anonyme

Invité

[resolu]plantage au boot avec kernel 4.4

Bonjour

ma passerelle ne fonctionne plus apres un upgrade et passage au noyau 4.4
selection manuelle et demarrage normal sur noyau 4.3 tout est correct  jusqu au bureau

je ne trouve rien dans les logs , donc j'ai récupéré quelques infos a la main

AMD-VI event logged [IO-page-fault device=00:11.0 domain=0x0009  => (une a 2 pages d'ecran avec cette erreur )
modprobe: module microcode not found in modules.dep
[11.924363] ata3: softreset failed (1st FIS failed)
[21.925273] ata3: softreset failed (1st FIS failed)
gave up winting for root device . common problemes
boot args (cat /proc/cmdline)
-check rootdelay = (did the system wait long enough ?)
-check root = (did the system wait for the right device ?)
missing modules (cat /proc/modules; ls /dev)
Alert UUID=c1cd3912-e7e4-43e7-ab13-87dd0499ac39  does not exist  dropping to a shell

(initramfs)

[un chiffre ] ata3: softreset failed (1st FIS failed)
etc ...
etc .....

 

ce n'est pas un probleme de disque , puisque les versions anterieures du noyau fonctionne
je vais essayer de poster un extrait de syslog , mais pas sur que ça corresponde (je me suis fier au reset par ctrl+alt+supp ) apres plantage
je ne trouve rien dans le log du kernel , je pense qu il doit etre impossible d ecrire sur le disque
voici le syslog

Mar 27 11:48:45 debian10 systemd[1]: Started User Manager for UID 124.
Mar 27 11:48:45 debian10 systemd[1]: Started User Manager for UID 124.
Mar 27 11:48:45 debian10 isc-dhcp-server[717]: Starting ISC DHCPv4 server: dhcpd.
Mar 27 11:48:45 debian10 isc-dhcp-server[717]: Starting ISC DHCPv4 server: dhcpd.
Mar 27 11:48:45 debian10 systemd[1]: Started LSB: DHCP server.
Mar 27 11:48:45 debian10 systemd[1]: Started LSB: DHCP server.
Mar 27 11:48:45 debian10 systemd[1]: Reached target Multi-User System.
Mar 27 11:48:45 debian10 systemd[1]: Reached target Multi-User System.
Mar 27 11:48:45 debian10 systemd[1]: Reached target Graphical Interface.
Mar 27 11:48:45 debian10 systemd[1]: Reached target Graphical Interface.
Mar 27 11:48:45 debian10 systemd[1]: Starting Update UTMP about System Runlevel Changes...
Mar 27 11:48:45 debian10 systemd[1]: Starting Update UTMP about System Runlevel Changes...
Mar 27 11:48:45 debian10 systemd[1]: Started Update UTMP about System Runlevel Changes.
Mar 27 11:48:45 debian10 systemd[1]: Started Update UTMP about System Runlevel Changes.
Mar 27 11:48:45 debian10 systemd[1]: Startup finished in 3.424s (kernel) + 15.165s (userspace) = 18.589s.
Mar 27 11:48:45 debian10 systemd[1]: Startup finished in 3.424s (kernel) + 15.165s (userspace) = 18.589s.
Mar 27 11:49:02 debian10 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
Mar 27 11:49:02 debian10 lightdm: pam_unix(lightdm:session): session opened for user robert by (uid=0)
Mar 27 11:49:02 debian10 systemd[1]: Created slice User Slice of robert.
Mar 27 11:49:02 debian10 systemd[1]: Created slice User Slice of robert.
Mar 27 11:49:02 debian10 systemd[1]: Starting User Manager for UID 1000...
Mar 27 11:49:02 debian10 systemd[1]: Starting User Manager for UID 1000...
Mar 27 11:49:02 debian10 systemd-logind[428]: New session 1 of user robert.
Mar 27 11:49:02 debian10 systemd[1]: Started Session 1 of user robert.
Mar 27 11:49:02 debian10 systemd[1]: Started Session 1 of user robert.

Mar 27 11:49:02 debian10 systemd: pam_unix(systemd-user:session): session opened for user robert by (uid=0)
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Timers.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Timers.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Sockets.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Sockets.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Paths.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Paths.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Basic System.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Default.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Basic System.
Mar 27 11:49:02 debian10 systemd[1106]: Reached target Default.
Mar 27 11:49:02 debian10 systemd[1106]: Startup finished in 36ms.
Mar 27 11:49:02 debian10 systemd[1106]: Startup finished in 36ms.
Mar 27 11:49:02 debian10 systemd[1]: Started User Manager for UID 1000.
Mar 27 11:49:02 debian10 systemd[1]: Started User Manager for UID 1000.
Mar 27 11:49:04 debian10 x-session-manager[1114]: WARNING: Unable to find provider '' of required component 'dock'
Mar 27 11:49:04 debian10 x-session-manager[1114]: WARNING: Unable to find provider '' of required component 'dock'
Mar 27 11:49:06 debian10 gnome-keyring-daemon[1112]: The PKCS#11 component was already initialized
Mar 27 11:49:06 debian10 gnome-keyring-daemon[1112]: The Secret Service was already initialized
Mar 27 11:49:07 debian10 dbus[429]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Mar 27 11:49:07 debian10 dbus[429]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Mar 27 11:49:07 debian10 polkitd(authority=local): Registered Authentication Agent for unix-session:1 (system bus name :1.14 [/usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-a$
Mar 27 11:49:07 debian10 systemd[1]: Starting Disk Manager...


Mar 27 11:49:07 debian10 udisksd[1205]: udisks daemon version 2.1.7 starting
Mar 27 11:49:07 debian10 dbus[429]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Mar 27 11:49:07 debian10 dbus[429]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Mar 27 11:49:07 debian10 systemd[1]: Started Disk Manager.
Mar 27 11:49:07 debian10 systemd[1]: Started Disk Manager.
Mar 27 11:49:07 debian10 udisksd[1205]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Mar 27 11:49:07 debian10 udisksd[1205]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Mar 27 11:49:07 debian10 x-session-manager[1114]: WARNING: Could not launch application 'restorecond.desktop': Unable to start application: L'exécution du processus fils « /usr/$
Mar 27 11:49:07 debian10 x-session-manager[1114]: WARNING: Could not launch application 'restorecond.desktop': Unable to start application: L'exécution du processus fils « /usr/$
Mar 27 11:49:07 debian10 gnome-keyring-daemon[1112]: The SSH agent was already initialized
Mar 27 11:49:08 debian10 dbus[429]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Mar 27 11:49:08 debian10 dbus[429]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Mar 27 11:49:08 debian10 systemd[1]: Starting Daemon for power management...
Mar 27 11:49:08 debian10 systemd[1]: Starting Daemon for power management...
Mar 27 11:49:09 debian10 org.gtk.vfs.AfcVolumeMonitor[1136]: Volume monitor alive
Mar 27 11:49:09 debian10 org.gtk.vfs.AfcVolumeMonitor[1136]: Volume monitor alive
Mar 27 11:49:09 debian10 dbus[429]: [system] Successfully activated service 'org.freedesktop.UPower'
Mar 27 11:49:09 debian10 dbus[429]: [system] Successfully activated service 'org.freedesktop.UPower'
Mar 27 11:49:09 debian10 systemd[1]: Started Daemon for power management.
Mar 27 11:49:09 debian10 systemd[1]: Started Daemon for power management.
Mar 27 11:49:11 debian10 dbus[429]: [system] Activating service name='org.mate.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Mar 27 11:49:11 debian10 dbus[429]: [system] Activating service name='org.mate.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Mar 27 11:49:11 debian10 dbus[429]: [system] Successfully activated service 'org.mate.SettingsDaemon.DateTimeMechanism'
Mar 27 11:49:11 debian10 dbus[429]: [system] Successfully activated service 'org.mate.SettingsDaemon.DateTimeMechanism'
Mar 27 11:49:11 debian10 org.a11y.atspi.Registry[1200]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 27 11:49:11 debian10 org.a11y.atspi.Registry[1200]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry


Mar 27 11:49:11 debian10 org.a11y.atspi.Registry[1200]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 27 11:49:11 debian10 org.a11y.atspi.Registry[1200]: ** (at-spi2-registryd:1299): WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistere$
Mar 27 11:49:11 debian10 org.a11y.atspi.Registry[1200]: ** (at-spi2-registryd:1299): WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistere$
Mar 27 11:49:11 debian10 org.a11y.atspi.Registry[1200]: ** (at-spi2-registryd:1299): WARNING **: Unable to register client with session manager
Mar 27 11:49:11 debian10 org.a11y.atspi.Registry[1200]: ** (at-spi2-registryd:1299): WARNING **: Unable to register client with session manager
Mar 27 11:49:36 debian10 polkitd(authority=local): Operator of unix-session:1 successfully authenticated as unix-user:root to gain ONE-SHOT authorization for action com.ubuntu.p$
Mar 27 11:49:36 debian10 pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Mar 27 11:49:36 debian10 pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
Mar 27 11:49:36 debian10 pkexec[1305]: robert: Executing command [USER=root] [TTY=unknown] [CWD=/home/robert] [COMMAND=/usr/sbin/synaptic]
Mar 27 11:53:06 debian10 kernel: [  280.062658] device-mapper: uevent: version 1.0.3
Mar 27 11:53:06 debian10 kernel: [  280.062806] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18) initialised: dm-devel@redhat.com
Mar 27 11:53:06 debian10 kernel: [  280.062658] device-mapper: uevent: version 1.0.3
Mar 27 11:53:06 debian10 kernel: [  280.062806] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18) initialised: dm-devel@redhat.com
Mar 27 11:53:08 debian10 kernel: [  281.751124] SGI XFS with ACLs, security attributes, realtime, no debug enabled
Mar 27 11:53:08 debian10 kernel: [  281.751124] SGI XFS with ACLs, security attributes, realtime, no debug enabled
Mar 27 11:53:08 debian10 kernel: [  281.765737] JFS: nTxBlock = 8192, nTxLock = 65536
Mar 27 11:53:08 debian10 kernel: [  281.765737] JFS: nTxBlock = 8192, nTxLock = 65536
Mar 27 11:53:08 debian10 kernel: [  281.830450] ntfs: driver 2.1.32 [Flags: R/W MODULE].
Mar 27 11:53:08 debian10 kernel: [  281.830450] ntfs: driver 2.1.32 [Flags: R/W MODULE].
Mar 27 11:53:08 debian10 kernel: [  281.880500] QNX4 filesystem 0.2.3 registered.
Mar 27 11:53:08 debian10 kernel: [  281.880500] QNX4 filesystem 0.2.3 registered.
Mar 27 11:53:08 debian10 kernel: [  281.962045] raid6: sse2x1   gen()  2149 MB/s
Mar 27 11:53:08 debian10 kernel: [  281.962045] raid6: sse2x1   gen()  2149 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.030091] raid6: sse2x1   xor()  1743 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.030091] raid6: sse2x1   xor()  1743 MB/s

Mar 27 11:53:08 debian10 kernel: [  282.098156] raid6: sse2x2   gen()  3596 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.098156] raid6: sse2x2   gen()  3596 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.166208] raid6: sse2x2   xor()  2677 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.166208] raid6: sse2x2   xor()  2677 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.234272] raid6: sse2x4   gen()  4604 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.234272] raid6: sse2x4   gen()  4604 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.302336] raid6: sse2x4   xor()  2896 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.302340] raid6: using algorithm sse2x4 gen() 4604 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.302342] raid6: .... xor() 2896 MB/s, rmw enabled
Mar 27 11:53:08 debian10 kernel: [  282.302345] raid6: using ssse3x2 recovery algorithm
Mar 27 11:53:08 debian10 kernel: [  282.302336] raid6: sse2x4   xor()  2896 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.302340] raid6: using algorithm sse2x4 gen() 4604 MB/s
Mar 27 11:53:08 debian10 kernel: [  282.302342] raid6: .... xor() 2896 MB/s, rmw enabled
Mar 27 11:53:08 debian10 kernel: [  282.302345] raid6: using ssse3x2 recovery algorithm
Mar 27 11:53:08 debian10 kernel: [  282.318819] xor: automatically using best checksumming function:
Mar 27 11:53:08 debian10 kernel: [  282.318819] xor: automatically using best checksumming function:
Mar 27 11:53:08 debian10 kernel: [  282.358378]    avx       :  1683.000 MB/sec
Mar 27 11:53:08 debian10 kernel: [  282.358378]    avx       :  1683.000 MB/sec
Mar 27 11:53:08 debian10 kernel: [  282.372781] Btrfs loaded
Mar 27 11:53:08 debian10 kernel: [  282.372781] Btrfs loaded
Mar 27 11:53:08 debian10 kernel: [  282.378750] fuse init (API version 7.23)
Mar 27 11:53:08 debian10 kernel: [  282.378750] fuse init (API version 7.23)
Mar 27 11:53:08 debian10 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
Mar 27 11:53:08 debian10 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
Mar 27 11:53:09 debian10 kernel: [  282.616662] EXT4-fs (sda2): unable to read superblock

Mar 27 11:53:09 debian10 kernel: [  282.616662] EXT4-fs (sda2): unable to read superblock
Mar 27 11:53:09 debian10 kernel: [  282.645874] EXT4-fs (sda2): unable to read superblock
Mar 27 11:53:09 debian10 kernel: [  282.645874] EXT4-fs (sda2): unable to read superblock
Mar 27 11:53:09 debian10 kernel: [  282.648639] EXT4-fs (sda2): unable to read superblock
Mar 27 11:53:09 debian10 kernel: [  282.648639] EXT4-fs (sda2): unable to read superblock
Mar 27 11:53:09 debian10 kernel: [  282.652161] XFS (sda2): Invalid superblock magic number
Mar 27 11:53:09 debian10 kernel: [  282.652161] XFS (sda2): Invalid superblock magic number
Mar 27 11:53:09 debian10 kernel: [  282.658924] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 27 11:53:09 debian10 kernel: [  282.659127] FAT-fs (sda2): invalid media value (0x00)
Mar 27 11:53:09 debian10 kernel: [  282.658924] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 27 11:53:09 debian10 kernel: [  282.659127] FAT-fs (sda2): invalid media value (0x00)
Mar 27 11:53:09 debian10 kernel: [  282.659134] FAT-fs (sda2): Can't find a valid FAT filesystem
Mar 27 11:53:09 debian10 kernel: [  282.661845] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 27 11:53:09 debian10 kernel: [  282.662023] FAT-fs (sda2): invalid media value (0x00)
Mar 27 11:53:09 debian10 kernel: [  282.662029] FAT-fs (sda2): Can't find a valid FAT filesystem
Mar 27 11:53:09 debian10 kernel: [  282.659134] FAT-fs (sda2): Can't find a valid FAT filesystem
Mar 27 11:53:09 debian10 kernel: [  282.661845] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 27 11:53:09 debian10 kernel: [  282.662023] FAT-fs (sda2): invalid media value (0x00)
Mar 27 11:53:09 debian10 kernel: [  282.662029] FAT-fs (sda2): Can't find a valid FAT filesystem
Mar 27 11:53:09 debian10 kernel: [  282.670202] MINIX-fs: unable to read superblock
Mar 27 11:53:09 debian10 kernel: [  282.670202] MINIX-fs: unable to read superblock
Mar 27 11:53:09 debian10 kernel: [  282.698891] attempt to access beyond end of device
Mar 27 11:53:09 debian10 kernel: [  282.698899] sda2: rw=16, want=3, limit=2
Mar 27 11:53:09 debian10 kernel: [  282.698904] hfsplus: unable to find HFS+ superblock
Mar 27 11:53:09 debian10 kernel: [  282.701860] qnx4: no qnx4 filesystem (no root dir).
Mar 27 11:53:09 debian10 kernel: [  282.698891] attempt to access beyond end of device
Mar 27 11:53:09 debian10 kernel: [  282.698899] sda2: rw=16, want=3, limit=2
Mar 27 11:53:09 debian10 kernel: [  282.698904] hfsplus: unable to find HFS+ superblock
Mar 27 11:53:09 debian10 kernel: [  282.701860] qnx4: no qnx4 filesystem (no root dir).
Mar 27 11:53:09 debian10 kernel: [  282.704545] ufs: You didn't specify the type of your ufs filesystem
Mar 27 11:53:09 debian10 kernel: [  282.704545]
Mar 27 11:53:09 debian10 kernel: [  282.704545] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Mar 27 11:53:09 debian10 kernel: [  282.704545]
Mar 27 11:53:09 debian10 kernel: [  282.704545] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Mar 27 11:53:09 debian10 kernel: [  282.704545] ufs: You didn't specify the type of your ufs filesystem
Mar 27 11:53:09 debian10 kernel: [  282.704545]
Mar 27 11:53:09 debian10 kernel: [  282.704545] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Mar 27 11:53:09 debian10 kernel: [  282.704545]
Mar 27 11:53:09 debian10 kernel: [  282.704545] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Mar 27 11:53:09 debian10 kernel: [  282.715593] hfs: can't find a HFS filesystem on dev sda2
Mar 27 11:53:09 debian10 kernel: [  282.715593] hfs: can't find a HFS filesystem on dev sda2
Mar 27 11:53:09 debian10 os-prober: debug: /dev/sda5: is active swap
Mar 27 11:53:09 debian10 os-prober: debug: /dev/sda5: is active swap
Mar 27 11:53:36 debian10 polkitd(authority=local): Unregistered Authentication Agent for unix-session:1 (system bus name :1.14, object path /org/mate/PolicyKit1/AuthenticationAg$
Mar 27 11:53:36 debian10 systemd-logind[428]: System is rebooting.
 

on voit le derniere ligne  "system is rebooting

la machine est assez light , un opteron + carte mere serveur + memoire ECC 16Go (4 barrettes de 4) , un disque sata 500Go assez récent , 2 cartes réseau eth0 et eth1
le BMC est désactivé , la carte video une GT8800 1Go PCIe avec nouveau et un bureau ligth Mate
une petite remarque , je suis pas content de firefox , je risque de passer a autre chose si iceweasel n'est plus proposé par debian (si un post existe je donnerai mon avis   )
pour l installation de stretch , tout sur un seul disque + swap (mode débutant   )
ps:c'est une jessie dist-upgrade en stretch mais il y a assez longtemp , j'ai encore le noyau 4.2 donc aucun rapport .

sur le syslog ci dessus les lignes qui commencent par RAID6  me semble bizzare et n existe pas avec le noyau 4.3 (je dois vérifier)

avec le noyau 4.3 voila le message pour AMD-VI

Mar 27 12:38:39 debian10 kernel: [    1.861723] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
Mar 27 12:38:39 debian10 kernel: [    1.861724] AMD-Vi: Interrupt remapping enabled
Mar 27 12:38:39 debian10 kernel: [    1.861859] AMD-Vi: Lazy IO/TLB flushing enabled
Mar 27 12:38:39 debian10 kernel: [    1.864351] perf: AMD NB counters detected
Mar 27 12:38:39 debian10 kernel: [    1.864482] microcode: CPU0: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864493] microcode: CPU1: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864505] microcode: CPU2: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864516] microcode: CPU3: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864526] microcode: CPU4: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864534] microcode: CPU5: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864546] microcode: CPU6: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864557] microcode: CPU7: patch_level=0x06000822
Mar 27 12:38:39 debian10 kernel: [    1.864630] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
 

ce qui a priori pose probleme avec le noyau 4.4 (je pourrai désactiver l option IOMMU pour test dans le bios )
c'est les premiers lignes d erreur qui apparaissent lors du boot en 4.4

AMD-VI event logged [IO-page-fault device=00:11.0 domain=0x0009  => (une a 2 pages d'ecran avec cette erreur )
 

Dernière modification par anonyme (27-03-2016 15:49:26)

raleur

Membre

Inscription : 03-10-2014

Re : [resolu]plantage au boot avec kernel 4.4

Si le disque n'est pas accessible, les logs ne risquent pas d'être enregistrés.
Dans le shell de secours lancé par l'initramfs, tu peux essayer d'enregistrer les logs du noyau sur une clé USB.

---

Il vaut mieux montrer que raconter.

anonyme

Invité

Re : [resolu]plantage au boot avec kernel 4.4

j'ai désinstallé l image et header du noyau 4.4 , grub c'est mit a jour , c'est bien un probleme du noyau (pas de la mise a jour des paquets)

pour l'instant j'en conclue que ce noyau ne prend plus en charge mon materiel ou contient un bug (pas assez barbu pour tout comprendre    )
peut etre je trouverai une explication sur le net , pour cette machine d'avoir le dernier noyau n'a peut etre pas un grand interet
j'ai l option de verrouiller l upgrade  du kernel

PS:la carte mere est une H8SGL-F-0  SuperMicro

Dernière modification par anonyme (27-03-2016 13:48:46)

anonyme

Invité

Re : [resolu]plantage au boot avec kernel 4.4

j'ai mit a une une machine Amd a base de cpu FX  (inactive depuis 4 semaines), un upgrade de tous les paquets (avec le driver non-free + cuda ) puis en dernier la mise a jour du noyau
tout est correct , je suis sur le bureau

un extrait du syslog

Mar 27 15:27:09 debian2 kernel: [    0.887961] pci 0000:01:00.0: Video device with shadowed ROM
Mar 27 15:27:09 debian2 kernel: [    0.888015] PCI: CLS 64 bytes, default 64
Mar 27 15:27:09 debian2 kernel: [    0.888055] Unpacking initramfs...
Mar 27 15:27:09 debian2 kernel: [    1.130706] Freeing initrd memory: 16200K (ffff88003604c000 - ffff88003701e000)
Mar 27 15:27:09 debian2 kernel: [    1.208913] iommu: Adding device 0000:00:00.0 to group 0
Mar 27 15:27:09 debian2 kernel: [    1.209285] iommu: Adding device 0000:00:02.0 to group 1
Mar 27 15:27:09 debian2 kernel: [    1.209656] iommu: Adding device 0000:00:04.0 to group 2
Mar 27 15:27:09 debian2 kernel: [    1.210024] iommu: Adding device 0000:00:05.0 to group 3
Mar 27 15:27:09 debian2 kernel: [    1.210417] iommu: Adding device 0000:00:06.0 to group 4
Mar 27 15:27:09 debian2 kernel: [    1.210784] iommu: Adding device 0000:00:07.0 to group 5
Mar 27 15:27:09 debian2 kernel: [    1.211152] iommu: Adding device 0000:00:11.0 to group 6
Mar 27 15:27:09 debian2 kernel: [    1.211528] iommu: Adding device 0000:00:12.0 to group 7
Mar 27 15:27:09 debian2 kernel: [    1.211542] iommu: Adding device 0000:00:12.2 to group 7
Mar 27 15:27:09 debian2 kernel: [    1.211919] iommu: Adding device 0000:00:13.0 to group 8
Mar 27 15:27:09 debian2 kernel: [    1.211934] iommu: Adding device 0000:00:13.2 to group 8
Mar 27 15:27:09 debian2 kernel: [    1.212316] iommu: Adding device 0000:00:14.0 to group 9
Mar 27 15:27:09 debian2 kernel: [    1.212683] iommu: Adding device 0000:00:14.2 to group 10
Mar 27 15:27:09 debian2 kernel: [    1.213049] iommu: Adding device 0000:00:14.3 to group 11
Mar 27 15:27:09 debian2 kernel: [    1.213415] iommu: Adding device 0000:00:14.4 to group 12
Mar 27 15:27:09 debian2 kernel: [    1.213782] iommu: Adding device 0000:00:14.5 to group 13
Mar 27 15:27:09 debian2 kernel: [    1.214157] iommu: Adding device 0000:00:16.0 to group 14
Mar 27 15:27:09 debian2 kernel: [    1.214173] iommu: Adding device 0000:00:16.2 to group 14
Mar 27 15:27:09 debian2 kernel: [    1.214556] iommu: Adding device 0000:01:00.0 to group 15
Mar 27 15:27:09 debian2 kernel: [    1.214579] iommu: Adding device 0000:01:00.1 to group 15
Mar 27 15:27:09 debian2 kernel: [    1.214947] iommu: Adding device 0000:02:00.0 to group 16
Mar 27 15:27:09 debian2 kernel: [    1.215315] iommu: Adding device 0000:03:00.0 to group 17
Mar 27 15:27:09 debian2 kernel: [    1.215683] iommu: Adding device 0000:04:00.0 to group 18
Mar 27 15:27:09 debian2 kernel: [    1.216061] iommu: Adding device 0000:05:00.0 to group 19
Mar 27 15:27:09 debian2 kernel: [    1.216063] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
Mar 27 15:27:09 debian2 kernel: [    1.216064] AMD-Vi: Interrupt remapping enabled
Mar 27 15:27:09 debian2 kernel: [    1.216169] AMD-Vi: Lazy IO/TLB flushing enabled
Mar 27 15:27:09 debian2 kernel: [    1.218342] perf: AMD NB counters detected
Mar 27 15:27:09 debian2 kernel: [    1.218443] microcode: CPU0: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218450] microcode: CPU1: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218455] microcode: CPU2: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218462] microcode: CPU3: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218469] microcode: CPU4: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218475] microcode: CPU5: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218483] microcode: CPU6: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218490] microcode: CPU7: patch_level=0x06000822
Mar 27 15:27:09 debian2 kernel: [    1.218541] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Mar 27 15:27:09 debian2 kernel: [    1.218545] LVT offset 0 assigned for vector 0x400
Mar 27 15:27:09 debian2 kernel: [    1.218588] perf: AMD IBS detected (0x000000ff)
Mar 27 15:27:09 debian2 kernel: [    1.218935] futex hash table entries: 2048 (order: 5, 131072 bytes)
 

j'ai l impression que le kernel avec nouveau n'apprecie pas ma GT8800 , ici c'est une GTX750TI
il me reste a tester le serveur avec une carte plus récente , pas la premiere fois que le noyau bug avec des gpu nvidia trop ancien
je me trompe peut etre , mais avec la serie 6xxx gros probleme avec le noyau 4.xx
je ferai un retour en cas d échec ou réussite

Dernière modification par anonyme (27-03-2016 15:02:54)

anonyme

Invité

Re : [resolu]plantage au boot avec kernel 4.4

Voila le retour
mise en place d une carte graphique sur PCIe  GTX750 (petit model sans le TI) a la place de la GT8800 toujours le plantage

désactivation de l option IOMMU dans le bios , la machine démarre normalement avec le noyau 4.4

je saurais pas le pourquoi en sachant que les plateformes Amd récente fonctionne avec cet option (a base de processeur FX derniere génération) peut etre un probleme de bios sur cette carte mere

la carte vidéo est bien reconnu

Mar 27 16:46:31 debian10 kernel: [    8.775066] nouveau 0000:01:00.0: NVIDIA GM107 (117010a2)
Mar 27 16:46:31 debian10 kernel: [    8.888759] nouveau 0000:01:00.0: bios: version 82.07.32.00.f6
Mar 27 16:46:31 debian10 kernel: [    8.890068] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
Mar 27 16:46:31 debian10 kernel: [    9.162856] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card0/input5
Mar 27 16:46:31 debian10 kernel: [    9.178791] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card0/input6
Mar 27 16:46:31 debian10 kernel: [    9.194790] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0
 

le chargement MMIO echoue

Mar 27 16:46:31 debian10 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Mar 27 16:46:31 debian10 kernel: [    0.000000] Linux version 4.4.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 20160307 (Debian 5.3.1-11) ) #1 SMP Debian 4.4.6-$
Mar 27 16:46:31 debian10 kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1-amd64 root=UUID=c1cd3912-e7e4-43e7-ab13-87dd0499ac39 ro quiet
Mar 27 16:46:31 debian10 systemd[1]: Started Load/Save Random Seed.
Mar 27 16:46:31 debian10 kernel: [    0.000000] tseg: 00c7f00000
Mar 27 16:46:31 debian10 kernel: [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Mar 27 16:46:31 debian10 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
Mar 27 16:46:31 debian10 systemd[1]: Started Create Volatile Files and Directories.
Mar 27 16:46:31 debian10 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
Mar 27 16:46:31 debian10 kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
Mar 27 16:46:31 debian10 systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Mar 27 16:46:31 debian10 kernel: [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Mar 27 16:46:31 debian10 kernel: [    0.000000] x86/fpu: Using 'lazy' FPU context switches.
Mar 27 16:46:31 debian10 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Mar 27 16:46:31 debian10 systemd[1]: Reached target System Time Synchronized.



Mar 27 16:46:32 debian10 systemd[1]: Started Light Display Manager.
Mar 27 16:46:31 debian10 kernel: [    6.885067] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
Mar 27 16:46:31 debian10 kernel: [    6.901602] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
Mar 27 16:46:31 debian10 kernel: [    6.901666] sp5100_tco: PCI Revision ID: 0x3d
Mar 27 16:46:31 debian10 kernel: [    6.901687] sp5100_tco: failed to find MMIO address, giving up.
Mar 27 16:46:31 debian10 kernel: [    6.939667] EDAC MC: Ver: 3.0.0
Mar 27 16:46:31 debian10 kernel: [    6.957676] MCE: In-kernel MCE decoding enabled.
Mar 27 16:46:31 debian10 kernel: [    6.965693] AMD64 EDAC driver v3.4.0
Mar 27 16:46:31 debian10 kernel: [    6.965717] EDAC amd64: DRAM ECC enabled.
Mar 27 16:46:31 debian10 kernel: [    6.965726] EDAC amd64: F15h detected (node 0).
Mar 27 16:46:31 debian10 kernel: [    6.965753] EDAC MC: DCT0 chip selects:
 

je trouve plus le message IOMMU dans le syslog comme quoi il est pas activé

j'ai toujour le message au démarrage que je n avait pas avec le 4.3

modprobe: module microcode not found in modules.dep
 

la commande

cat /proc/cmdline
 

retour

BOOT_IMAGE=/boot/vmlinuz-4.4.0-1-amd64 root=UUID=c1cd3912-e7e4-43e7-ab13-87dd0499ac39 ro quiet
 

les commandes  "cat /proc/modules" et "ls /dev"  me donne des retours que je sais pas interpréter  . 
pour le noyau 4.3
la commande

cat /proc/cmdline
 

le retour

BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 root=UUID=c1cd3912-e7e4-43e7-ab13-87dd0499ac39 ro quiet
 

je n'ai pas le message du module microcode no found
j'ai toujours le message ERST
plus de message IOMMU  avec toujours l option désactivé (il a disparut depuis la mise a jour du noyau a la version 4.xx ) , avec jessie (3.16 je l avais )

si je trouve pourquoi avec la 4.4 il ne trouve pas le module microcode (j'ai reinstallé le microcode amd sous le noyau 4.4 ça n a rien changé )

pour l instant je reste en 4.3 si quelqu un a une sugestion pour ce souci 

ps: pour info cette option IOMMU se trouve dans les parametres  "NorthBridge chipset"  qui contient tous les parametres memoire. (elle désactivé par defaut en bios usine)

Dernière modification par anonyme (27-03-2016 16:58:34)

anonyme

Invité

Re : [resolu]plantage au boot avec kernel 4.4

un petit retour sur le passage au noyau 4.4
pour intel j 'ai eu un message  "microcode absent" , j'ai supprimé les paquets intel-microcode et uicode-tool
pour amd meme message j'ai supprimé le paquet amd64-microcode
plus d'erreur du noyau (ce message n etait pas present avec le noyau 4.3 et les paquets installé)

pour IOMMU une seule plateforme a bugé (plantage systeme ) je l ai désactivé dans le bios (voir post au dessus))
j'ai 2 plateforme pc bureau amd ou IOMMU activé et microde present avec le noyau 4.4 ne pose pas de probleme (socket M3+)

voila si ça peut aider quelqu'un qui a ce souci