Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 27/08/2014, à 20:29

ceropegia

"panic occurred, switching back to text console"

Bonjour,

Depuis environ un mois, mon ordi plante tous les jours systématiquement au premier démarrage, parfois après 20 secondes, d'autres fois après 10 minutes. En général on a le temps de lancer firefox et après ça plante, mais pas toujours, des fois il plante avant. (au deuxième démarrage, en général tout va bien) L'écran devient tout noir, et à partir de là les messages d'erreurs varient. Impossible de copier quoi que ce soit. Parfois ALT+SYST+S puis E, I, U, B nous donne quelque chose mais plus souvent rien du tout.

Mais revient souvent (d'où le titre de ma discussion) :

panic occurred, switching back to text console

On a aussi du :

kernel panic - not syncing : fatal exception in interrupt

Des fois il ne va même pas jusqu'au GRUB et ne fait rien du tout, juste écran noir et curseur.

Je travaille sur un "vieux" laptop Nec de 2007 (ça me parait pas si vieux que ça...), avec Ubuntu 12.04 (32 bits), Noyau Linux 3.13.0-34 et Gnome 3.4.2.

Ma racine est à 25%, mon home à 83%. On a eu un dual boot il y a longtemps, mais maintenant on n'a que Linux.

Voilà. Je me demande surtout à quoi c'est dû, si c'est un problème matériel ou autre... Et si c'est un problème matériel, est-ce que je peux faire quelque chose sans racheter un ordi ??
Merci de vos conseils wink

PS : j'ajoute des infos sur ma config après avoir vu un fil de discussion similaire :

lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
03:07.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b4)
03:07.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 18)
03:07.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 09)
03:07.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 04)

Et pour la carte mère, bios et cpu :

 *-core
       description: Carte mère
       produit: KW3
       fabriquant: NEC Computers SAS
       identifiant matériel: 0
       version: CD3A
       numéro de série: QPCYEK72500080
     *-firmware
          description: BIOS
          fabriquant: NEC Computers SAS
          identifiant matériel: 0
          version: NOTE BIOS Version Q3A24
          date: 09/15/2006
          taille: 1MiB
          fonctionnalités: isa pci pcmcia pnp apm upgrade shadowing escd cdboot acpi usb agp biosbootspecification
     *-cpu:0
          description: CPU
          produit: Intel(R) Core(TM) Duo CPU      T2450  @ 2.00GHz
          fabriquant: Intel Corp.
          identifiant matériel: 4
          information bus: cpu@0
          version: 6.14.12
          numéro de série: 0000-06EC-0000-0000-0000-0000
          emplacement: U2E1
          taille: 2GHz
          capacité: 2048MHz
          bits: 32 bits
          fonctionnalités: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts aperfmperf pni monitor est tm2 xtpr pdcm dtherm cpufreq
          configuration: id=1

Edit :
En me référant à ce fil de discussion-là, je suis allée piocher dans kern.log, et voici ce que j'y ai trouvé pour le plantage de ce matin (arrivé à 8h11, mais plus rien après 8h04...) :

Aug 29 08:03:09 Gipsy kernel: [   26.472256] Bluetooth: HCI device and connection manager initialized
Aug 29 08:03:09 Gipsy kernel: [   26.472608] Bluetooth: HCI socket layer initialized
Aug 29 08:03:09 Gipsy kernel: [   26.472612] Bluetooth: L2CAP socket layer initialized
Aug 29 08:03:09 Gipsy kernel: [   26.472619] Bluetooth: SCO socket layer initialized
Aug 29 08:03:10 Gipsy kernel: [   26.787606] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Aug 29 08:03:10 Gipsy kernel: [   26.787613] Bluetooth: BNEP filters: protocol multicast
Aug 29 08:03:10 Gipsy kernel: [   26.787627] Bluetooth: BNEP socket layer initialized
Aug 29 08:03:10 Gipsy kernel: [   26.856746] Bluetooth: RFCOMM TTY layer initialized
Aug 29 08:03:10 Gipsy kernel: [   26.856764] Bluetooth: RFCOMM socket layer initialized
Aug 29 08:03:10 Gipsy kernel: [   26.856774] Bluetooth: RFCOMM ver 1.11
Aug 29 08:03:10 Gipsy kernel: [   27.106264] type=1400 audit(1409292190.512:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=936 comm="apparmor_parser"
Aug 29 08:03:10 Gipsy kernel: [   27.106279] type=1400 audit(1409292190.512:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=936 comm="apparmor_parser"
Aug 29 08:03:10 Gipsy kernel: [   27.106287] type=1400 audit(1409292190.512:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=936 comm="apparmor_parser"
Aug 29 08:03:10 Gipsy kernel: [   27.107103] type=1400 audit(1409292190.512:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=936 comm="apparmor_parser"
Aug 29 08:03:10 Gipsy kernel: [   27.107110] type=1400 audit(1409292190.512:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=936 comm="apparmor_parser"
Aug 29 08:03:10 Gipsy kernel: [   27.107538] type=1400 audit(1409292190.512:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=936 comm="apparmor_parser"
Aug 29 08:03:10 Gipsy kernel: [   27.425041] type=1400 audit(1409292190.832:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=935 comm="apparmor_parser"
Aug 29 08:03:15 Gipsy kernel: [   32.541010] iwl3945 0000:02:00.0: loaded firmware version 15.32.2.9
Aug 29 08:03:16 Gipsy kernel: [   32.610500] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 29 08:03:16 Gipsy kernel: [   32.610920] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 29 08:03:16 Gipsy kernel: [   32.624827] r8169 0000:03:00.0 eth0: link down
Aug 29 08:03:16 Gipsy kernel: [   32.624841] r8169 0000:03:00.0 eth0: link down
Aug 29 08:03:16 Gipsy kernel: [   32.624887] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 29 08:03:16 Gipsy kernel: [   32.625348] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 29 08:03:17 Gipsy kernel: [   34.474354] r8169 0000:03:00.0 eth0: link up
Aug 29 08:03:17 Gipsy kernel: [   34.474375] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 29 08:04:03 Gipsy kernel: [   84.049309] audit_printk_skb: 135 callbacks suppressed
Aug 29 08:04:03 Gipsy kernel: [   84.049316] type=1400 audit(1409292243.800:75): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/usr/share/gvfs/remote-volume-monitors/" pid=1945 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Et pour syslog :

Aug 29 08:03:26 Gipsy rtkit-daemon[1632]: Watchdog thread running.
Aug 29 08:03:26 Gipsy rtkit-daemon[1632]: Successfully made thread 1630 of process 1630 (n/a) owned by '104' high priority at nice level -11.
Aug 29 08:03:26 Gipsy rtkit-daemon[1632]: Supervising 1 threads of 1 processes of 1 users.
Aug 29 08:03:28 Gipsy rtkit-daemon[1632]: Successfully made thread 1647 of process 1630 (n/a) owned by '104' RT at priority 5.
Aug 29 08:03:28 Gipsy rtkit-daemon[1632]: Supervising 2 threads of 1 processes of 1 users.
Aug 29 08:03:28 Gipsy rtkit-daemon[1632]: Successfully made thread 1649 of process 1630 (n/a) owned by '104' RT at priority 5.
Aug 29 08:03:28 Gipsy rtkit-daemon[1632]: Supervising 3 threads of 1 processes of 1 users.
Aug 29 08:03:28 Gipsy rtkit-daemon[1632]: Successfully made thread 1652 of process 1652 (n/a) owned by '104' high priority at nice level -11.
Aug 29 08:03:28 Gipsy rtkit-daemon[1632]: Supervising 4 threads of 2 processes of 1 users.
Aug 29 08:03:28 Gipsy pulseaudio[1652]: [pulseaudio] pid.c: Daemon already running.
Aug 29 08:03:34 Gipsy NetworkManager[945]: <info> (eth0): IP6 addrconf timed out or failed.
Aug 29 08:03:34 Gipsy NetworkManager[945]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Aug 29 08:03:34 Gipsy NetworkManager[945]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Aug 29 08:03:34 Gipsy NetworkManager[945]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Aug 29 08:03:43 Gipsy rtkit-daemon[1632]: Successfully made thread 1802 of process 1802 (n/a) owned by '1000' high priority at nice level -11.
Aug 29 08:03:43 Gipsy rtkit-daemon[1632]: Supervising 4 threads of 2 processes of 2 users.
Aug 29 08:03:44 Gipsy rtkit-daemon[1632]: Successfully made thread 1805 of process 1802 (n/a) owned by '1000' RT at priority 5.
Aug 29 08:03:44 Gipsy rtkit-daemon[1632]: Supervising 5 threads of 2 processes of 2 users.
Aug 29 08:03:44 Gipsy rtkit-daemon[1632]: Successfully made thread 1806 of process 1802 (n/a) owned by '1000' RT at priority 5.
Aug 29 08:03:44 Gipsy rtkit-daemon[1632]: Supervising 6 threads of 2 processes of 2 users.
Aug 29 08:03:48 Gipsy gnome-session[1719]: WARNING: Failed to start app: Unable to start application: L'exécution du processus fils « fusion-icon » a échoué (Aucun fichier ou dossier de ce type)
Aug 29 08:03:48 Gipsy dbus[853]: [system] Activating service name='org.freedesktop.UDisks' (using servicehelper)
Aug 29 08:03:48 Gipsy dbus[853]: [system] Successfully activated service 'org.freedesktop.UDisks'
Aug 29 08:04:03 Gipsy kernel: [   84.049309] audit_printk_skb: 135 callbacks suppressed
Aug 29 08:04:03 Gipsy kernel: [   84.049316] type=1400 audit(1409292243.800:75): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/usr/share/gvfs/remote-volume-monitors/" pid=1945 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Aug 29 08:04:04 Gipsy goa[1950]: goa-daemon version 3.4.0 starting [main.c:112, main()]
Aug 29 08:04:59 Gipsy dbus[853]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Aug 29 08:04:59 Gipsy AptDaemon: INFO: Initializing daemon
Aug 29 08:05:00 Gipsy AptDaemon.PackageKit: INFO: Initializing PackageKit compat layer
Aug 29 08:05:00 Gipsy dbus[853]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Aug 29 08:05:00 Gipsy AptDaemon.PackageKit: INFO: Initializing PackageKit transaction
Aug 29 08:05:00 Gipsy AptDaemon.Worker: INFO: Simulating trans: /org/debian/apt/transaction/9235d437ec4a4fa9a4b2267ddb95ba8b
Aug 29 08:05:00 Gipsy AptDaemon.Worker: INFO: Processing transaction /org/debian/apt/transaction/9235d437ec4a4fa9a4b2267ddb95ba8b
Aug 29 08:05:07 Gipsy AptDaemon.PackageKit: INFO: Get updates()
Aug 29 08:05:08 Gipsy AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/9235d437ec4a4fa9a4b2267ddb95ba8b
Aug 29 08:08:10 Gipsy anacron[998]: Job `cron.daily' started
Aug 29 08:08:10 Gipsy anacron[2081]: Updated timestamp for job `cron.daily' to 2014-08-29
Aug 29 08:08:43 Gipsy kernel: [  363.632566] type=1400 audit(1409292523.384:76): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=890 comm="cupsd" capability=36  capname="block_suspend"
Aug 29 08:09:11 Gipsy dbus[853]: [system] Activating service name='com.ubuntu.SystemService' (using servicehelper)
Aug 29 08:09:12 Gipsy dbus[853]: [system] Successfully activated service 'com.ubuntu.SystemService'

Alors bien sûr je n'y comprends pas grand chose... Si quelqu'un a des idées, des conseils, ou juste un petit diagnostic, ce serait génial !

Dernière modification par ceropegia (Le 29/08/2014, à 09:02)

Hors ligne