search for: genfs_contexts

...mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary SELinux: Completing initialization. SELinux: Setting up existing superblocks. SELinux: initialized (dev dm-0, type ext3), uses xattr SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialize...

...****** Continuing... security: 3 users, 4 roles, 316 types, 20 bools security: 53 classes, 9815 rules SELinux: Completing initialization. SELinux: Setting up existing superblocks. SELinux: initialized (dev hda7, type ext3), uses xattr SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), not configured for labeling SELinux: initialized (dev hugetlbfs, type hugetlbfs), not configured for labeling SELinux: initialized (dev devpts, type devpts), uses transition SIDs SELinux: initialized (dev eventpollfs, type eventpollfs), uses genfs_c...

At the risk of angering the crash Gods, my sustem has NOT crashed again since I downgraded the kernel from 2.6.18-1.2239.fc5 to 2.6.18-1.2200.fc5. Given that newfound stability, and my lack of time, I'm going to put on hold any further diagnostics, until the next kernel revision is released. I have submitted a report at bugzilla.redhat.com (bug 218128). (Ah, nuts; accidentally created a

...g. http://www.centos.org/modules/newbb/viewtopic.php?topic_id=2307 I'm running the latest samba-client & samba-common on CentOS 4.2. SELinux is in warn mode. Here's the /var/log/messages when I mount: Feb 2 19:42:16 sol kernel: SELinux: initialized (dev smbfs, type smbfs), uses genfs_contexts Feb 2 19:42:16 sol kernel: smb_retry: no connection process Feb 2 19:42:46 sol kernel: smb_add_request: request [c554bee0, mid=0] timed out! Feb 2 19:42:46 sol kernel: smb_delete_inode: could not close inode 2 Feb 2 19:42:46 sol kernel: SELinux: initialized (dev smbfs, type smbfs), uses genfs...

...771] SELinux: 8 users, 82 roles, 4552 types, 259 bools, 1 sens, 1024 cats [ 12.339787] SELinux: 83 classes, 95736 rules [ 12.344755] SELinux: Completing initialization. [ 12.344759] SELinux: Setting up existing superblocks. [ 12.344768] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts [ 12.344774] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts [ 12.344786] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts [ 12.344793] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 12.344802] SELinux: initialized (dev tmpfs, type tmpfs...

...932] SELinux: 8 users, 82 roles, 4552 types, 259 bools, 1 sens, 1024 cats [ 13.236949] SELinux: 83 classes, 95736 rules [ 13.241940] SELinux: Completing initialization. [ 13.241944] SELinux: Setting up existing superblocks. [ 13.241952] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts [ 13.241960] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts [ 13.241971] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts [ 13.241978] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 13.241993] SELinux: initialized (dev tmpfs, type tmpfs...

This may not be the proper place to raise this question but I've had little luck elsewhere. After trying again, unsuccessfully this time, to install the proprietary NVIDIA driver, I've decided to focus my efforts on the open source Nouveau driver. I've seen video drivers blamed for varying degrees of "freeze on resume" but I'm not certain that's what I'm up

...d,intr 0 0 This is causing some issues with some of my scripts. Both the client and server are 6.2 servers. The client is a virtual image running on the server. The only clue that i have is system logger shows: Mar 6 13:44:39 clienthost kernel: SELinux: initialized (dev 0:14, type nfs4), uses genfs_contexts Mar 6 13:44:39 clienthost kernel: SELinux: initialized (dev 0:15, type nfs4), uses genfs_contexts I can't find any errors anywhere else on either my client or server. There is nothing in the audit logs on either host. Does anybody have any ideas? Brad -- Bradley Leonard EMail: bradley at...

...s, 1024 cats SELinux: 81 classes, 212877 rules SELinux: Completing initialization. SELinux: Setting up existing superblocks. SELinux: initialized (dev md2, type ext3), uses xattr SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs SELinux: initialized (dev devpts, type devpts), uses transition SIDs SELinux: ini...

...[sdd] Mode Sense: 04 00 00 00 sd 8:0:0:1: [sdd] Assuming drive cache: write through sd 8:0:0:1: [sdd] Assuming drive cache: write through sdd: sdd1 sd 8:0:0:1: [sdd] Assuming drive cache: write through sd 8:0:0:1: [sdd] Attached SCSI removable disk SELinux: initialized (dev sdc, type vfat), uses genfs_contexts SELinux: initialized (dev sdd1, type vfat), uses genfs_contexts -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

..., 1024 cats SELinux: 77 classes, 200977 rules SELinux: Completing initialization. SELinux: Setting up existing superblocks. SELinux: initialized (dev sda3, type ext3), uses xattr SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs SELinux: initialized (dev devpts, type devpts), uses transition SIDs SELinux: ini...

...ress (6) This is part of my dmesg audit(1172747900.510:5): avc: denied { net_bind_service } for pid=1657 comm="hidd" capability=10 scontext=system_u:system_r:bluetooth_t:s0 tcontext=system_u:system_r:bluetooth_t:s0 tclass=capability SELinux: initialized (dev autofs, type autofs), uses genfs_contexts eth0: no IPv6 routers present [drm] Initialized drm 1.1.0 20060810 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 19 [drm] Initialized r128 2.5.0 20030725 on minor 0 agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0. agpgart: Device is in legacy mode, falling back...

I wrote a bunch of files to a backup DVD about two months ago and now neither of my drives will read it. I get mount errors from "not a directory" to something like "unrecognized file system type" and so on, usually after a really long wait and a notice about how the drive is write-protected (duh). Here's what happened most recently: # mount /dev/hdc /mnt mount: block

...94967295 security: 3 users, 6 roles, 1587 types, 172 bools, 1 sens, 1024 cats security: 59 classes, 49762 rules SELinux: Completing initialization. SELinux: Setting up existing superblocks. SELinux: initialized (dev dm-0, type ext3), uses xattr SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialize...

...s, 1024 cats SELinux: 81 classes, 251092 rules SELinux: Completing initialization. SELinux: Setting up existing superblocks. SELinux: initialized (dev md2, type ext3), uses xattr SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs SELinux: initialized (dev devpts, type devpts), uses transition SIDs SELinux: ini...

...ows at the time indicated. What is it complaining about? What should I do about it? I got some information from dmesg. It mentions IRQ 17, but the only error is from before the most recent hibernation. Here are some excerpts, in order from dmesg: SELinux: initialized (dev proc, type proc), uses genfs_contexts hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj. fuse init (API version 7.13) [Hardware Error]: Machine check events logged SELinux: initialized (dev sdc1, type vfat), uses genfs_contexts PM: Syncing filesystems ... done. ata_piix 0000:00:1f.1: PCI INT A di...

...l_anon_super+0x12/0x20 [<ffffffffa041827b>] nfs_kill_super+0x1b/0x30 [nfs] [<ffffffff811c962d>] deactivate_locked_super+0x3d/0x60 [<ffffffff811c9c36>] deactivate_super+0x46/0x60 [<ffffffff811e6ac5>] mntput_no_expire+0xc5/0x120 SELinux: initialized (dev 0:40, type nfs4), uses genfs_contexts [<ffffffff811e7bff>] SyS_umount+0x9f/0x3c0 [<ffffffff81614de9>] system_call_fastpath+0x16/0x1b Code: 00 00 48 8b 40 28 4c 8b 08 48 8b 43 30 48 85 c0 74 1b 48 8b 50 40 48 89 34 24 48 c7 c7 20 f1 83 81 48 89 de 31 c0 e8 f0 0a 42 00 <0f> 0b 31 d2 eb e5 0f 0b 66 66 66 2e 0f 1f 84 00 0...

...2-2:1.0 [ 2353.930584] scsi 6:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 2353.933129] sr 6:0:0:0: [sr1] scsi-1 drive [ 2353.935258] sr 6:0:0:0: Attached scsi CD-ROM sr1 [ 2354.156240] ISO 9660 Extensions: RRIP_1991A [ 2354.156261] SELinux: initialized (dev sr1, type iso9660), uses genfs_contexts [root at jvermeulen ~]# tail -f /var/log/messages May 11 21:05:04 jvermeulen kernel: usb 2-1: Product: HUAWEI Mobile May 11 21:05:04 jvermeulen kernel: usb 2-1: Manufacturer: Vodafone(Huawei) May 11 21:05:04 jvermeulen kernel: usb 2-1: SerialNumber: FFFFFFFFFFFFFFFF May 11 21:05:04 jvermeule...

...rnel=auto rhgb quiet LANG=en_US.UTF-8 systemd.debug [ 0.940176] ehci-pci 0000:00:12.2: debug port 1 [ 0.946472] ehci-pci 0000:00:13.2: debug port 1 [ 1.238335] systemd[1]: Unknown kernel switch systemd.debug. Ignoring. [ 5.083981] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts [ 5.206423] systemd[1]: Unknown kernel switch systemd.debug. Ignoring. Which I found interesting. So, can anyone point me to a detailed guide to debugging what's going on with my build that will help me solve my locking problem? BTW, I think it might be my wireless Atheros equipped PCI...

..._CMD) push 0x00406040 [28164.156831] nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 7 [multiwinia.bin.[17032]] get 0x0020164bc8 put 0x0020165248 ib_get 0x0000030e ib_put 0x0000030f state 0x80000024 (err: INVALID_CMD) push 0x00406040 [28282.019598] SELinux: initialized (dev proc, type proc), uses genfs_contexts -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20131222/9e0d27cd/attachment.html>