Bug 82258

Summary: A lot of messages in logind after boot or in term after every hardware event.
Product: systemd Reporter: Александр <Alex.Armoken>
Component: generalAssignee: systemd-bugs
Status: RESOLVED NOTABUG QA Contact: systemd-bugs
Severity: minor    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Example of messages
Example of messages

Description Александр 2014-08-06 17:56:12 UTC
Created attachment 104164 [details]
Example of messages

I think ,that is not very good, because in other init systems there is no such problem.
Comment 1 Александр 2014-08-06 18:04:09 UTC
Comment on attachment 104164 [details]
Example of messages

>*** End of the configuration.
>*** Execute 'make' to start the build or try 'make help'.
>
>*         >> Compiling 3.12.21-gentoo-r1 bzImage...
>*         >> Not installing firmware as it's included in the kernel already (CONFIG_FIRMWARE_IN_KERNEL=y)...
>*         >> Compiling 3.12.21-gentoo-r1 modules...
>*         >> Generating module dependency data...
>* Copying config for successful build to /etc/kernels/kernel-config-x86_64-3.12.21-gentoo-r1
>* busybox: >> Using cache
>* initramfs: >> Initializing...
>*         >> Appending base_layout cpio data...
>*         >> Appending udev cpio data...
>cp: cannot stat â /etc/modprobe.d/blacklist.confâ : No such file or directory
>* cannot copy /etc/modprobe.d/blacklist.conf from udev
>cp: cannot stat â /lib/systemd/network/99-default.linkâ : No such file or directory
>* cannot copy /lib/systemd/network/99-default.link from udev
>*         >> Appending auxilary cpio data...
>*         >> Copying keymaps
>*         >> Appending busybox cpio data...
>*         >> Appending modules cpio data...
>*         >> Appending blkid cpio data...
>*         >> Appending ld_so_conf cpio data...
>* ldconfig: adding /sbin/ldconfig...
>* ld.so.conf: adding /etc/ld.so.conf{.d/*,}...
>cpio: lib64 not created: newer or same age version exists
>cpio: lib64 not created: newer or same age version exists
>cpio: lib64/libuuid.so.1 not created: newer or same age version exists
>cpio: lib64/ld-linux-x86-64.so.2 not created: newer or same age version exists
>cpio: lib64/libc.so.6 not created: newer or same age version exists
>cpio: lib64/libblkid.so.1 not created: newer or same age version exists
>*         >> Finalizing cpio...
>*         >> Compressing cpio data (.xz)...
>*
>* Kernel compiled successfully!
>*
>* Required Kernel Parameters:
>*     root=/dev/$ROOT
>*
>*     Where $ROOT is the device node for your root partition as the
>*     one specified in /etc/fstab
>*
>* If you require Genkernel's hardware detection features; you MUST
>* tell your bootloader to use the provided INITRAMFS file.
>
>* WARNING... WARNING... WARNING...
>* Additional kernel cmdline arguments that *may* be required to boot properly...
>* With support for several ext* filesystems available, it may be needed to
>* add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
>
>* Do NOT report kernel bugs as genkernel bugs unless your bug
>* is about the default genkernel configuration...
>*
>* Make sure you have the latest ~arch genkernel before reporting bugs.
>
>
>
>
>
>
>
>
>
>r8169 0000:08:00.0 enp8s0: link up
>IPv6: ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
>
>
>
>
>
>
>Generating grub.cfg ...
>Found linux image: /boot/kernel-genkernel-x86_64-3.12.21-gentoo-r1
>Found initrd image: /boot/initramfs-genkernel-x86_64-3.12.21-gentoo-r1
>  No volume groups found
>EXT3-fs (sda3): error: unable to read superblock
>EXT2-fs (sda3): error: unable to read superblock
>EXT4-fs (sda3): unable to read superblock
>FAT-fs (sda3): bogus number of reserved sectors
>FAT-fs (sda3): Can't find a valid FAT filesystem
>FAT-fs (sda3): bogus number of reserved sectors
>FAT-fs (sda3): Can't find a valid FAT filesystem
>isofs_fill_super: bread failed, dev=sda3, iso_blknum=16, block=32
>UDF-fs: error (device sda3): udf_read_tagged: read failed, block=256, location=256
>UDF-fs: error (device sda3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
>UDF-fs: error (device sda3): udf_read_tagged: read failed, block=512, location=512
>UDF-fs: error (device sda3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
>UDF-fs: error (device sda3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
>UDF-fs: warning (device sda3): udf_load_vrs: No anchor found
>UDF-fs: Rescanning with blocksize 2048
>UDF-fs: error (device sda3): udf_read_tagged: read failed, block=256, location=256
>UDF-fs: error (device sda3): udf_read_tagged: read failed, block=512, location=512
>UDF-fs: warning (device sda3): udf_load_vrs: No anchor found
>UDF-fs: warning (device sda3): udf_fill_super: No partition found (1)
>Found Windows 7 (loader) on /dev/sda2
>done
>
>
>
>
>
> sudo blkid
>/dev/sda6: UUID="21a112bb-fc7d-4940-ab6f-a58c4f412f59" TYPE="ext4" PARTUUID="00013d45-06"
>/dev/sda1: UUID="ca10acb0-44f7-4a7f-bd18-efcf5eb86b89" TYPE="ext4" PARTUUID="00013d45-01"
>/dev/sda2: UUID="ECAA946FAA943852" TYPE="ntfs" PARTUUID="00013d45-02"
>/dev/sda5: UUID="585c1195-df9a-4506-8879-0f594ae3d1ec" TYPE="swap" PARTUUID="00013d45-05"
>/dev/sda7: UUID="899416ff-1ef4-49fd-b9ff-e0cb3b42b123" TYPE="ext4" PARTUUID="00013d45-07"
>/dev/sda8: UUID="a263fb3d-cf36-4f0a-bc01-bf9453311da9" TYPE="ext4" PARTUUID="00013d45-08"
>/dev/sda9: UUID="f44943c5-3391-41ee-956b-89fb2d4102f7" TYPE="ext4" PARTUUID="00013d45-09"
>/dev/sdc1: UUID="4341-FA8F" TYPE="vfat" PARTUUID="3b6906fe-b843-49ce-9e65-8dc12e3919ef"
>armoken@armoken-laptop ~ $ fdisk -l /dev/sda
>-bash: fdisk: command not found
>armoken@armoken-laptop ~ $ sudo fdisk -l /dev/sda
>
>Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
>Units: sectors of 1 * 512 = 512 bytes
>Sector size (logical/physical): 512 bytes / 4096 bytes
>I/O size (minimum/optimal): 4096 bytes / 4096 bytes
>Disklabel type: dos
>Disk identifier: 0x00013d45
>Partition 1 does not start on physical sector boundary.
>
>Device    Boot      Start        End    Blocks  Id System
>/dev/sda1 *            63    1992059    995998+  7 HPFS/NTFS/exFAT
>/dev/sda2         1992704  101996543  50001920   7 HPFS/NTFS/exFAT
>/dev/sda3       101996544 1953523711 925763584   5 Extended
>/dev/sda5       101998592  110387199   4194304  83 Linux
>/dev/sda6       110389248  183789567  36700160  83 Linux
>/dev/sda7       183791616  257191935  36700160  83 Linux
>/dev/sda8       257193984 1305769983 524288000  83 Linux
>/dev/sda9      1305772032 1953523711 323875840  83 Linux
>
>armoken@armoken-laptop ~ $ grep -v "#\|^$" /etc/fstab
>/dev/sda1               /boot           ext4            defaults,noatime                0 2
>/dev/sda6               /               ext4            noatime                         0 1
>/dev/sda5               none            swap            sw                              0 0
>/dev/sda7               /home           ext4            defaults                        0 0
>/dev/sda8               /mnt/all        ext4            defaults                        0 0
>/dev/sda9               /mnt/films      ext4            defaults                        0 0
>/dev/sda2               /windows        ntfs            defaults                        0 0
>
>
>
>
>GRUB_DISTRIBUTOR="Gentoo"
>
>GRUB_DEFAULT=0
>GRUB_HIDDEN_TIMEOUT=0
>GRUB_HIDDEN_TIMEOUT_QUIET=true
>GRUB_TIMEOUT=10
>
># Append parameters to the linux kernel command line
>GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd"
>
># Append parameters to the linux kernel command line for non-recovery entries
>GRUB_CMDLINE_LINUX_DEFAULT="video=uvesafb:mtrr:3,ywrap,1366x768-32@75"
>
># Uncomment to disable graphical terminal (grub-pc only)
>#GRUB_TERMINAL=console
>
># The resolution used on graphical terminal.
># Note that you can use only modes which your graphic card supports via VBE.
># You can see them in real GRUB with the command `vbeinfo'.
>#GRUB_GFXMODE=640x480
>
># Path to theme spec txt file.
># The starfield is by default provided with use truetype.
># NOTE: when enabling custom theme, ensure you have required font/etc.
>#GRUB_THEME="/boot/grub/themes/starfield/theme.txt"
>
># Background image used on graphical terminal.
># Can be in various bitmap formats.
>#GRUB_BACKGROUND="/boot/grub/mybackground.png"
>
># Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to kernel
>#GRUB_DISABLE_LINUX_UUID=true
># Uncomment to disable generation of recovery mode menu entries
>#GRUB_DISABLE_RECOVERY=true
>
>
>
>
>This is armoken-laptop. Now 22:04:57 Mon Aug 4  2014
>
>armoken-laptop login: r8169 0000:08:00.0 enp8s0: link down
>r8169 0000:08:00.0 enp8s0: link down
>IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
>iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
>iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
>IPv6: ADDRCONF(NETDEV_UP): wlp9s0: link is not ready
>r8169 0000:08:00.0 enp8s0: link up
>IPv6: ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
>usb 1-2: new high-speed USB device number 5 using xhci_hcd
>usb 1-2: New USB device found, idVendor=0951, idProduct=1624
>usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>usb 1-2: Product: DataTraveler G2
>usb 1-2: Manufacturer: Kingston
>usb 1-2: SerialNumber: 001CC0EC34D1F9C126A00CB4
>usb 1-2: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
>usb 1-2: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
>usb-storage 1-2:1.0: USB Mass Storage device detected
>scsi5 : usb-storage 1-2:1.0
>scsi 5:0:0:0: Direct-Access     Kingston DataTraveler G2  1.00 PQ: 0 ANSI: 2
>sd 5:0:0:0: Attached scsi generic sg2 type 0
>sd 5:0:0:0: [sdb] 31252024 512-byte logical blocks: (16.0 GB/14.9 GiB)
>sd 5:0:0:0: [sdb] Write Protect is off
>sd 5:0:0:0: [sdb] Incomplete mode parameter data
>sd 5:0:0:0: [sdb] Assuming drive cache: write through
>sd 5:0:0:0: [sdb] Incomplete mode parameter data
>sd 5:0:0:0: [sdb] Assuming drive cache: write through
> sdb: sdb1
>sd 5:0:0:0: [sdb] Incomplete mode parameter data
>sd 5:0:0:0: [sdb] Assuming drive cache: write through
>sd 5:0:0:0: [sdb] Attached SCSI removable disk
>armoken
>Password:
>Last login: Mon Aug  4 21:41:25 FET 2014 on tty1
>
>
>
>#  This file is part of systemd.
>#
>#  systemd is free software; you can redistribute it and/or modify it
>#  under the terms of the GNU Lesser General Public License as published by
>#  the Free Software Foundation; either version 2.1 of the License, or
>#  (at your option) any later version.
>#
># See journald.conf(5) for details
>
>[Journal]
>Storage=auto
>Compress=no
>Seal=yes
>#SplitMode=uid
>#SyncIntervalSec=5m
>#RateLimitInterval=30s
>#RateLimitBurst=1000
>SystemMaxUse=100M
>#SystemKeepFree=
>#SystemMaxFileSize=
>#RuntimeMaxUse=
>#RuntimeKeepFree=
>#RuntimeMaxFileSize=
>#MaxRetentionSec=
>#MaxFileSec=1month
>ForwardToSyslog=no
>ForwardToKMsg=no
>ForwardToConsole=yes
>ForwardToWall=no
>TTYPath=/dev/tty12
>#MaxLevelStore=debug
>#MaxLevelSyslog=debug
>#MaxLevelKMsg=notice
>MaxLevelConsole=notice
>#MaxLevelWall=emerg
>
>
>
>
>
>[    6.721583] input: PC Speaker as /devices/platform/pcspkr/input/input12
>[    6.732756] ACPI Warning: SystemIO range 0x0000000000006040-0x000000000000605f conflicts with OpRegion 0x0000000000006040-0x000000000000604f (\_SB_.PCI0.SBUS.SMBI) (20131218/utaddress-258)
>[    6.732845] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>[    6.758698] r8169 0000:08:00.0 eth0: link down
>[    6.758710] r8169 0000:08:00.0 eth0: link down
>[    6.758721] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>[    6.862348] iwlwifi 0000:09:00.0: loaded firmware version 22.1.7.0 op_mode iwlmvm
>[    6.862357] iwlwifi 0000:09:00.0: Detected Intel(R) Wireless N 7260, REV=0x144
>[    6.862404] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
>[    6.862632] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
>[    6.994724] nvidia: module license 'NVIDIA' taints kernel.
>[    6.994749] Disabling lock debugging due to kernel taint
>[    7.004155] nvidia 0000:07:00.0: enabling device (0006 -> 0007)
>[    7.004479] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:07:00.0 on minor 1
>[    7.004484] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.24  Wed Jul  2 14:24:20 PDT 2014
>[    7.056811] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
>[    7.066385] nvidia 0000:07:00.0: irq 51 for MSI/MSI-X
>[    7.068907] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.068994] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.069060] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.069134] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.069199] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.069262] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.069343] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.069408] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>[    7.108104] systemd-udevd[2142]: renamed network interface wlan0 to wlp9s0
>[    7.134276] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
>[    7.134509] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
>[    7.146050] IPv6: ADDRCONF(NETDEV_UP): wlp9s0: link is not ready
>[    8.467737] r8169 0000:08:00.0 eth0: link up
>[    8.467744] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>[   11.218236] ACPI Warning: \_SB_.PCI0.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
>
Comment 2 Александр 2014-08-06 18:07:42 UTC
Created attachment 104169 [details]
Example of messages
Comment 3 Lennart Poettering 2014-08-11 10:07:48 UTC
You probably have configured your kernel to write log messages directly to the console when they happen. Try "quiet" on the kernel command line, which will make them go away.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.