| Summary: | Tomoyo does not start (was: makes kernel panic) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jacques Pronchery <jacques.pronchery> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | MGA2TOO | ||
| Source RPM: | tomoyo-tools | CVE: | |
| Status comment: | |||
|
Description
Jacques Pronchery
2011-11-05 13:46:08 CET
Hi, do you have log of this Kernel panic ? In /var/log/kernel/errors.log I guess. Thomas, was I on the right trick ? Keywords:
(none) =>
NEEDINFO When I stop the system I have : Nov 6 13:49:26 localhost kernel: CIFS VFS: Received no data, expecting 4 Nov 6 13:51:26 localhost kernel: CIFS VFS: Received no data, expecting 4 Nov 6 23:35:10 localhost kernel: ACPI: [Package] has zero elements (edcaaa00) Nov 6 23:35:10 localhost kernel: 5:2: cannot get min/max values for control 2 (id 5) Nov 6 23:35:15 localhost kernel: CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.2 Nov 6 23:35:15 localhost kernel: CIFS VFS: Send error in SETFSUnixInfo = -5 Nov 6 23:35:15 localhost kernel: CIFS VFS: Negotiating Unix capabilities with the server failed. Consider mounting with the Unix Extensions Nov 6 23:35:15 localhost kernel: disabled, if problems are found, by specifying the nounix mount option. Nov 7 08:33:49 localhost kernel: ACPI: [Package] has zero elements (edfc2ec0) Nov 7 08:33:49 localhost kernel: 5:2: cannot get min/max values for control 2 (id 5) Nov 7 08:33:54 localhost kernel: CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.2 Nov 7 08:33:54 localhost kernel: CIFS VFS: Send error in SETFSUnixInfo = -5 Nov 7 08:33:54 localhost kernel: CIFS VFS: Negotiating Unix capabilities with the server failed. Consider mounting with the Unix Extensions Nov 7 08:33:54 localhost kernel: disabled, if problems are found, by specifying the nounix mount option. And when I reboot : Nov 6 13:49:26 localhost kernel: CIFS VFS: Received no data, expecting 4 Nov 6 13:51:26 localhost kernel: CIFS VFS: Received no data, expecting 4 Nov 6 23:35:10 localhost kernel: ACPI: [Package] has zero elements (edcaaa00) Nov 6 23:35:10 localhost kernel: 5:2: cannot get min/max values for control 2 (id 5) Nov 6 23:35:15 localhost kernel: CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.2 Nov 6 23:35:15 localhost kernel: CIFS VFS: Send error in SETFSUnixInfo = -5 Nov 6 23:35:15 localhost kernel: CIFS VFS: Negotiating Unix capabilities with the server failed. Consider mounting with the Unix Extensions Nov 6 23:35:15 localhost kernel: disabled, if problems are found, by specifying the nounix mount option. Nov 7 08:33:49 localhost kernel: ACPI: [Package] has zero elements (edfc2ec0) Nov 7 08:33:49 localhost kernel: 5:2: cannot get min/max values for control 2 (id 5) Nov 7 08:33:54 localhost kernel: CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.2 Nov 7 08:33:54 localhost kernel: CIFS VFS: Send error in SETFSUnixInfo = -5 Nov 7 08:33:54 localhost kernel: CIFS VFS: Negotiating Unix capabilities with the server failed. Consider mounting with the Unix Extensions Nov 7 08:33:54 localhost kernel: disabled, if problems are found, by specifying the nounix mount option. In the boot.log I have Setting up hotplug. Loading nouveau module unless booted with failsafe or nokmsboot option 1 %Gcannot open file delete Creating block device nodes. Creating character device nodes. Loading ext4 module Loading crc-t10dif module Loading scsi_mod module Loading sd_mod module Loading libata module Loading ata_generic module Loading pata_acpi module Loading ide-core module Loading ide-disk module Loading ide-pci-generic module Loading sata_nv module Loading pata_amd module waiting for device sdc7 to appear (timeout 1min) waiting for device sdc4 to appear (timeout 1min) Creating root device. Mounting root filesystem. Setting up other filesystems. Switching to new root and running init. INIT: version 2.86 booting Bienvenue sous [1;36mMageia[0;39m 2 Pressez 'I' pour entrer dans le mode interactif Starting udev: udevd[123]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev' [85G[[1;32m OK [0;39m] %GAffectation du nom de machine localhost : [85G[[1;32m OK [0;39m] Vérification du système de fichiers racine sda7: clean, 125221/2583616 files, 1032075/10325770 blocks [85G[[1;32m OK [0;39m] Remontage du système de fichiers racine en écriture : [85G[[1;32m OK [0;39m] Invalidating stale software suspend images... done. Vérification des systèmes de fichiers [85G[[1;32m OK [0;39m] Montage des systèmes de fichiers locaux : WARNING: "include /lib/module-init-tools/modprobe.compat" is deprecated, please use /etc/modprobe.d WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. [85G[[1;31mÃCHEC [0;39m] WARNING: "include /lib/module-init-tools/modprobe.compat" is deprecated, please use /etc/modprobe.d WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Vérification des systèmes de fichiers loopback[85G[[1;32m OK [0;39m] Montage des systèmes de fichiers loopback : [85G[[1;32m OK [0;39m] Activation des espaces d'échange de /etc/fstab : [85G[[1;32m OK [0;39m] Activation des espaces d'échange : Lancement de netprofile : [85G[[1;32m OK [0;39m] The default is the current profile. [85G[[1;32m OK [0;39m] nvidia-current (285.05.09-1.mga2.nonfree): Already installed on this kernel. Recherche de nouveaux périphériques [85G[[1;32m OK [0;39m] INIT: Entering runlevel: 5 Début du mode non interactif Vérification si les partitions disposent d'assez d'espace libre : [85G[[1;32m OK [0;39m] Le pilote ALSA est déjà lancé.Restauration des réglages du mixer ALSA via alsactl : [85G[[1;32m OK [0;39m] Lancement du verrouillage numérique : [85G[[1;32m OK [0;39m] Lancement de atd : [85G[[1;32m OK [0;39m] acpid: starting up with proc fs Lancement du service acpi : [85G[[1;32m OK [0;39m] acpid: 2 rules loaded acpid: waiting for events: event logging is off Lancement de la journalisation système : [85G[[1;32m OK [0;39m] Lancement de irqbalance : [85G[[1;32m OK [0;39m] Lancement de crond : [85G[[1;32m OK [0;39m] Lancement de resolvconf : [85G[[1;32m OK [0;39m] Failed to get D-Bus connection: No connection to service manager. Lancement du bus de messages système : [85G[[1;32m OK [0;39m] Redéclencher les évènements udev ayant échoué--type=failed is deprecated and will be removed from a future udev release. [85G[[1;32m OK [0;39m] Lancement de mdadm : [85G[[1;32m OK [0;39m] WARNING: "include /lib/module-init-tools/modprobe.compat" is deprecated, please use /etc/modprobe.d WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Démarrage de l'interface loopback : [85G[[1;32m OK [0;39m] Activation de l'interface eth0 : [85G[[1;32m OK [0;39m] Lancement du service HAL : [85G[[1;32m OK [0;39m] Lancement du gestionnaire d'affichage : [85G[[1;32m OK [0;39m] Nov 7 08:33:53 localhost NET[2443]: /sbin/dhclient-script : updated /etc/resolv.conf Now there is kernel panic only on reboot. The last messages are : .... dracut: switching root Calling /sbin/tomoyo-init to load policy. Please wait 2 domains. 8 ACL entries.
Marja Van Waes
2012-01-21 13:05:23 CET
Keywords:
NEEDINFO =>
(none) Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher. Is this one still valid for Mageia 2 rc? If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. If it wasn't assigned correctly, please assign back to Bug Squad and explain. Now Tomoyo does not make kernel panic. But on my PC it does not start, because : 2 domains 0 ACL entry If I test : [root@localhost jacques]# service tomoyo-auditd status tomoyo-auditd.service - LSB: TOMOYO Linux MAC logging daemon Loaded: loaded (/etc/rc.d/init.d/tomoyo-auditd) Active: failed (Result: exit-code) since Sat, 12 May 2012 10:28:26 +0200; 2min 3s ago Process: 706 ExecStart=/etc/rc.d/init.d/tomoyo-auditd start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/tomoyo-auditd.service [root@localhost jacques]#
Marja Van Waes
2012-05-12 10:37:25 CEST
Summary:
Tomoyo make kernel panic =>
2_rc Tomoyo does not start (was: makes kernel panic) Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO This bug is still valid for Mageia 2. Whiteboard:
(none) =>
MGA2TOO
Marja Van Waes
2012-06-14 19:53:43 CEST
Keywords:
NEEDINFO =>
(none) Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D Sorry, but this bug saw no action since over 2 yrs ago. No cauldron package has stayed the same since then. Closing as OLD Please reopen if this report is still valid for _current_ cauldron and/or fully updated Mageia 4 Status:
NEW =>
RESOLVED |