[SOLVED] High disk activity after kernel boot

Hi,
after kernel loading (just before getty starts) i notice extremely high disk activity for ~20 seconds for no reason. I think that it is something related to systemd and mount services.
When i set rootfs to read-only in syslinux kernel parameters then the system starts normally without delay. So, i think that something is constantly writing to (or checking?) my hard disk right after boot sequence.
I'm using kernel 3.7.9-1-ARCH.
$ systemd --version
systemd 197
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
$ systemd-analyze
Startup finished in 3121ms (kernel) + 6238ms (userspace) = 9360ms
$ systemd-analyze blame
1289ms NetworkManager.service
1173ms colord.service
812ms systemd-logind.service
722ms systemd-binfmt.service
660ms systemd-udevd.service
639ms systemd-sysctl.service
314ms tmp.mount
305ms systemd-remount-fs.service
300ms upower.service
219ms systemd-tmpfiles-setup.service
168ms polkit.service
160ms dev-sda2.swap
156ms systemd-vconsole-setup.service
129ms wpa_supplicant.service
125ms dev-mqueue.mount
121ms dev-hugepages.mount
108ms systemd-udev-trigger.service
101ms verynice.service
59ms systemd-user-sessions.service
48ms boot.mount
47ms hpfall.service
46ms home.mount
43ms cpupower.service
27ms sys-kernel-config.mount
4ms proc-sys-fs-binfmt_misc.mount
Syslinux kernel parameters (either ro or rw has the same result)
APPEND root=/dev/sda3 rw nomodeset vga=current clocksource=acpi_pm libahci.ignore_sss=1
Tried also with fsck hook and removing sda3 from fstab
APPEND root=/dev/sda3 rw nomodeset vga=current clocksource=acpi_pm libahci.ignore_sss=1 rootflags=noatime,barrier=0
my fstab:
# UUID=925aba97-6805-442b-bb51-3ea6c16a5a86
/dev/sda3 / ext4 rw,noatime,barrier=0 0 0
# UUID=dd60df02-7992-43c1-a0e0-79441e23268e
/dev/sda1 /boot ext4 rw,noatime 0 0
# UUID=d2621666-f2c5-4f36-8da3-c0f21a23246c
/dev/sda4 /home ext4 rw,noatime 0 0
# UUID=3d70bc7d-5b0c-4adc-ba84-f32c9d132bcc
/dev/sda2 none swap defaults 0 0
Thanks for your time.
Last edited by anelehto (2013-02-23 14:27:41)

It was a problem with preload and its configuration.. I removed it and everything went back to normal!

Similar Messages

[SOLVED] Black screen after kernel boot after pacman -Syu

Hi, after full system upgrade with pacman -Syu, I get after the kernel boot black screen and everything is freezing. Then need to manually shut down the power button!
Normally when my system starts up after the kernel boot I get straight to the command line terminal login.
Can anybody help me how to fix this? Any clues? Any advice is welcome!
The problem is solved by downgrading to kernel 3.6.11.-1
Many thanks for the help from the people on #archlinux !
Last edited by OpenEye (2013-01-29 05:14:04)

jasonwryan wrote:
Please stop bumping your thread: use the edit button
https://wiki.archlinux.org/index.php/Fo … te#Bumping
What have you done about the errors being printed to your logs? You could start by fixing the network error and the broken udev rule...
Are you still using intiscripts? They are no longer supported: https://www.archlinux.org/news/end-of-i … s-support/
# edit: not a pacman issue, moving to Newbie Corner
I have searched for many hours and days for solutions on the internet and forums, tried some things, but with no results! I don't know how to fix the errors! Do you know how to fix that? I'm a total n00b! I'm doing my best as I can! Need help, thanks!

FF 18.0.1 constant disk activity after 1 minute with no tabs open

FF 18.0.1 on Windows XP SP3.
Within 1 minute of starting FF I observe constant and excessive disk activity.
I am unable to use any other applications due to the response time.
I have closed all tabs and disabled all plugins.
I have just started a FF "reset to factory default", but pop-up window for "Please wait while Firefox cleans up your old data" has been running for 15 minutes.
Any ideas?

It sounds like you've got some other problems on your computer as well.
Restart your PC, then try the steps at http://www.microsoft.com/atwork/maintenance/speed.aspx#fbid=6pXkdz7T_94 to try to clean your computer up.
After that, Try to reset Firefox again.

[Solved] systemd creates autofs after unmounting /boot

After logging in, i unmount /boot, so that i can unplug the usb drive where it resides, then systemd creates this mount:
# mount | grep /boot
systemd-1 on /boot type autofs (rw,relatime,fd=26,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
Typing this hangs forever:
ls /boot
/etc/fstab
UUID=2D75-67FC /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,nodev,nosuid,noexec 0 2
I don't really know what to make of this. Seems like a bug, given that ls hangs forever instead of showing nothing.
Last edited by teateawhy (2014-09-12 10:48:38)

My bad, i really masked the mount unit. Will try again tomorrow.
EDIT:
After masking the automount unit, it looks like this:
* /boot is mounted correctly at startup
* after unmounting /boot manually, no autofs mount shows up anymore
* ls does not hang and immediatly shows nothing, as expected
# systemctl status boot.automount
● boot.automount
Loaded: masked (/dev/null)
Active: inactive (dead)
# mount | grep /boot
(No output)
Last edited by teateawhy (2014-09-12 10:16:50)

[SOLVED] nfsroot install broken after kernel upgrade 3.5.6 to 3.6.2

It seems my nfsroot installations have broken after the kernel upgrade to 3.6.2.
This is as far as the boot process gets now (hand copied from the screen):
IP-Config: eth0 complete (from 10.48.50.20):
address: 10.48.50.240 broadcast: 10.48.50.255 netmask: 255.255.255.0
gateway: 0.0.0.0 dns0 : 0.0.0.0 dns1: 0.0.0.0
domain : local
rootserver: 10.48.50.20 rootpath:
filename : /var/tftpboot/pxelinux.0
NFS-Mount: 10.48.50.20:/srv/nfs4/kvmhost0-rootfs
Waiting 10 seconds for device /dev/nfs ...
mount: Protocol not supported
:: running cleanup hook [udev]
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
[rootfs /]#
On the server this is what is logged:
Oct 16 21:10:04 tuon dhcpd: DHCPDISCOVER from 00:21:70:eb:02:25 via san
Oct 16 21:10:04 tuon dhcpd: DHCPOFFER on 10.48.50.240 to 00:21:70:eb:02:25 via san
Oct 16 21:10:04 tuon dhcpd: DHCPREQUEST for 10.48.50.240 (10.48.50.20) from 00:21:70:eb:02:25 via san
Oct 16 21:10:04 tuon dhcpd: DHCPACK on 10.48.50.240 to 00:21:70:eb:02:25 via san
Oct 16 21:10:14 tuon rpc.mountd[1323]: authenticated mount request from 10.48.50.240:684 for /srv/nfs4/kvmhost0-rootfs (/srv/nfs4/kvmhost0-rootfs)
Oct 16 21:10:14 tuon rpc.mountd[1323]: refused unmount request from 10.48.50.240 for /new_root (/): not exported
It looks to me like the client is sending the mount request, the server accepts and then for some reason the client thinks it has failed. I can't even see anything strange in the wireshark traces comparing the working client (3.5.6) to the broken one (3.6.2).
Anyone else using nfsroot successfully with the latest kernel?
Any other ideas?
(by the way - despite my directory names, this is using nfs v3 for the rootfs)
Last edited by kmshanah (2012-10-18 03:18:07)

mikep wrote:
Just to confirm that I also have this problem with nfsroot (nfs4 this time) with 3.6.2. Downgrading the kernel does make it go away.
When it is working normally I do seem to get refused unmount messages at shutdown for some reason
refused unmount request from 192.168.1.86 for / (/): not exported
, but the /new_root bit is new and I have no idea where it comes from.
refused unmount request from 192.168.1.86 for /new_root (/): not exported
So I wonder if it asking for the wrong path.
That unmount issue will be solved by FS#32021.
Unfortunately, that doesn't help with mounting in the first place with 3.6.2

[SOLVED] Address space collision after kernel 3.0 upgrade

After upgrading to linux 3.0.1 I get the following error messages from kernel:
kernel: [ 0.313527] pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000cc000-0x000cffff] conflicts with Video ROM [mem 0x000c0000-0x000ce9ff]
kernel: [ 0.313537] pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000d0000-0x000d3fff] conflicts with Adapter ROM [mem 0x000cf000-0x000d0fff]
Anyone having similar issues? What could this be related to?
Everything seems to work fine so far... but this message is making me a little nervous....
Last edited by king.flasher.dave (2011-08-31 14:20:33)

The kernel is reporting a BIOS bug (in the DSDT table). Many BIOS tables say nonsense things like two pieces of hardware being addressable at the same location of memory. Most likely it's been that way all along, but over time the kernel devs check for more of these things, thus new error messages come out.
If all of your hardware still works, then you can ignore it. Otherwise, you can try upgrading BIOS firmware in the hope that a newer version doesn't have the bug. (Or you can correct the table yourself and get the kernel to use the corrected copy from disk instead of the one in firmware, but I've found that to be very hard to accomplish.)

[SOLVED] Huge power consumption after kernel upgrade.

Dear All,
I have recently bought the new lenovo thinkpad X1 equipped with a Core I5 processors and 4GB of RAM.
I am quite satisfied with this machine except for the fact that the fan is extremely loud (but perhaps a bios upgrade will fix problem).
Now my problem:
When I first installed Arch (first days of August) I ran powertop and the power consumption was around 10 Watts when idle with wifi card turned off.
Now, after some upgrades, the power consumption raises to 18W in idle and consequently the battery lasts less than 2h.
Here my current configuration:
Linux think-x1 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011 x86_64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux
and here the powertop output obtained with the cpu frequency governor set to "On demand":
Cn Avg residency P-states (frequencies)
C0 (cpu running) ( 5.3%) Turbo Mode 0.1%
polling 0.0ms ( 0.0%) 2.50 Ghz 0.0%
C1 mwait 0.2ms ( 0.1%) 2.21 Ghz 0.0%
C2 mwait 0.3ms ( 0.0%) 1200 Mhz 0.1%
C3 mwait 2.4ms ( 0.0%) 800 Mhz 99.8%
C4 mwait 13.1ms (94.6%)
Wakeups-from-idle per second : 76.1 interval: 3.0s
Power usage (ACPI estimate): 15.7W (2.8 hours)
Top causes for wakeups:
46.5% (135.7) kworker/0:0
17.7% ( 51.7) PS/2 keyboard/mouse/touchpad interrupt
11.9% ( 34.7) [kernel scheduler] Load balancing tick
8.6% ( 25.0) [iwlagn] <interrupt>
2.9% ( 8.3) [i915] <interrupt>
2.6% ( 7.7) [acpi] <interrupt>
1.8% ( 5.3) chromium
1.6% ( 4.7) [kernel core] hrtimer_start (tick_sched_timer)
1.5% ( 4.3) kworker/0:1
0.7% ( 2.0) minilogd
0.7% ( 2.0) [kernel core] iwl_bg_watchdog (iwl_bg_watchdog)
0.6% ( 1.7) X
0.6% ( 1.7) [kernel core] intel_gpu_idle_timer (intel_gpu_idle_timer)
0.3% ( 1.0) Terminal
0.3% ( 1.0) [kernel core] tpt_trig_timer (tpt_trig_timer)
0.2% ( 0.7) [mmc0, mei, ehci_hcd:usb3] <interrupt>
0.2% ( 0.7) upowerd
0.1% ( 0.3) init
0.1% ( 0.3) gpg-agent
0.1% ( 0.3) [kernel core] ieee80211_sta_reset_conn_monitor (ieee80211_sta_conn_mon_timer)
0.1% ( 0.3) wicd-client
0.1% ( 0.3) kworker/u:3
0.1% ( 0.3) watchdog/0
I have also tried to disable most of the running daemons and unload some modules, but I have never got less than 14/15W when idle, which in my opinion is definitely too much!
As far as I'm concerned, the kworker process is responsible most of the wakeups.
Any ideas?
Last edited by jacopo_c (2011-09-05 13:12:16)

pogeymanz wrote:I read somewhere that the kernel devs really don't see this as an issue. They just expect that laptop owners should know to try these boot parameters. So, definitely not by 3.1.
from https://bugzilla.redhat.com/show_bug.cgi?id=727579:
Dave Jones 2011-08-03 15:32:21 EDT
enabling it by default in 3.0 caused regressions for some people, so it was
disabled. Hopefully Intel figures it out, and we can switch it back on by
default in 3.1 / 2.6.41 (until then, you'll have to set it by hand).
Interesting stuff, also recommend this thread on phoronix:
http://phoronix.com/forums/showthread.p … Regression
Last edited by masteryod (2011-09-12 00:30:00)

[SOLVED] No sound modules after kernel update

Hello,
after updating my kernel, I have no sound modules. Alsaconf can't detect card. My lspci sound card:
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
My lsmod:
Module Size Used by
joydev 9895 0
usbhid 35352 0
hid 82435 1 usbhid
nvidia 12069499 40
broadcom 7270 0
tg3 133684 0
ehci_hcd 40794 0
intel_ips 11245 0
psmouse 55501 0
libphy 16985 2 broadcom,tg3
i7core_edac 16231 0
serio_raw 4294 0
i2c_i801 8187 0
pcspkr 1819 0
evdev 9530 10
usbcore 144144 3 usbhid,ehci_hcd
edac_core 37552 3 i7core_edac
i2c_core 20460 2 nvidia,i2c_i801
sg 25429 0
iTCO_wdt 11789 0
button 4470 0
iTCO_vendor_support 1961 1 iTCO_wdt
processor 24224 0
fuse 66858 2
ext4 375413 3
mbcache 5881 1 ext4
jbd2 70667 1 ext4
crc16 1359 1 ext4
raid0 7958 2
md_mod 100392 3 raid0
sr_mod 14951 0
cdrom 36553 1 sr_mod
sd_mod 28275 8
pata_acpi 3376 0
ata_piix 22077 6
libata 166724 2 pata_acpi,ata_piix
scsi_mod 132794 4 sg,sr_mod,sd_mod,libata
And my kernel:
Linux nekroman 3.1.2-1-ARCH #1 SMP PREEMPT Tue Nov 22 09:17:56 CET 2011 x86_64 Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz GenuineIntel GNU/Linux
Thanks for help.
//edit:
Reinstalled kernel and it works!
Last edited by Nekroman (2011-11-25 15:08:32)

how did you re-install the kernel? I've never done that, and am too experiencing sound issues.
--nixIT

High CPU temps after kernel panic.

Recently I've seen my Mac Pro 8-core CPU temps rise pretty considerably, between 10°-15°C after a bone head move on my part.
After setting up a new Vista x64 virtual machine in VMWare Fusion 2, I was trying to get a Linksys USB to Ethernet adapter (USB200M) to work inside this virtual machine, but with little success. After tracking down a driver online which I thought at the time was a match for the chip on the adapter, I tried to load the driver manually in the virtual machine. This unfortunately resulted in an immediate OS X kernel panic; my first and only on this machine.
Since then, my CPU temps have been on the rise. Not sure if its even possible for a kernel panic to damage hardware, but I’m wondering if any low-level software damage resulting from the kernel panic could be causing the higher temps?
I tried a simple restart which did nothing. I have since run the extended Apple Diagnostics and everything appeared OK. Also, ran a “fsck” check and everything appeared OK there as well.
Any feedback, suggestions or advice?
P.S. This is an Early ’08 2.8GHz 8-core Mac Pro with 10GB third-party RAM. RAM has been thoroughly tested and running in the machine for over a year now without incident.
Thanks

No, ethernet ports work fine.
I use the adapter to connect a VMWare Virtual Machine directly to a VPN Netgear router which runs a remote VoIP service, available on Windows only. To make a long story short, I ran into all kinds of performance issues when connecting the Mac via Ethernet directly to this crappy little Netgear VPN router.
So, the alternative was to use the USB to Ethernet adapter to connect only the VM directly to this router. Definitely not ideal, but worked fine with XP.
It was when I upgraded the VM to Vista x64 and tried to install the driver for the adapter that I got the kernel panic and now higher CPU temps.
Still just curious if I could have damaged any hardware?

[SOLVED] Low quality windows after kernel upgrading

Hello,
I've got such a weird situation. After I upgraded to 3.12-2, my KDE windows got a low quality style. You can figure out better what I mean with this screenshot.
I did try to reinstall the video driver (I'm using the integrated gpu currently), delete and recreate the KDE cache, and downgrade the kernel. But an even stranger thing is that although I downgraded the kernel, the system kept using the 3.12.2-2; I was able to use neither dhcpcd nor X too.
I strongly think it's an hardware compatibility problem, don't you?
Last edited by Grant (2013-12-07 12:23:46)

berbae wrote:
Grant wrote:I did try to re-install the video driver, delete and recreate the KDE cache, and downgrade the kernel.
It would have been better to post the exact commands you used and their result (what video driver? what KDE cache? what kernel? )
I strongly think it's an hardware compatibility problem, don't you?
How could that prevent you from downgrading the kernel?
So you say that you downgraded the kernel, to 3.12.1-3 I presume, you rebooted and the machine still uses the 3.12.2-1 kernel!
It's very strange : did the downgrading finished normally? Look into the pacman.log file and the kernel log messages in dmesg; and the xorg server log also, if possible with the new kernel and with the previous one. There is also the .xsession-errors file in $HOME.
I know it's strange! I've never come across a similiar problem. And I'm gonna tell you more: it kept doing that even when the *.3-1 came out. I had to use the brute force. I manually removed the kernel images, the packages in the cache, and upgraded with --force, all that in live mode, and it worked fine.

[solved] Problems with display after kernel update.

After using pacman -Syu and getting the newest kernel and Nvidia drivers I experience some major problems.
My Arch freezes when I try to run some apps. Firefox, konqueror and some others work fine, but when I type "glxinfo | grep direct" or try to execute something using wine the problems begin. Terminal doesn't return any errors (it doesn't get a chance to do so, freeze is instant).
Edit:
I've used script from nvidia.com
Last edited by dcfighter (2008-08-11 00:42:51)

I examined /etc/fonts/conf.avail and found 2 files
70-no-bitmaps.conf and
70-yes-bitmaps.conf
But the content of this files the same! Defined value was set to "false"
I delete "no" file and correct "yes" file
<fontconfig>
<Accept>
<selectfont>
<acceptfont>
<pattern>
<patelt><bool>true</bool></patelt>
</pattern>
</acceptfont>
</selectfont>
</fontconfig>
After this, Helvetica fonts became more likely

Unusual hard disk activity after "Erase free space"

I have two partitions on my hard disk - a small partition for the system software and a big partition for everything else. A few days ago, I backed up a few files from my big partition and then used Disk Utility "Erase free space". Since then, my hard disk is behaving oddly. I can hear it, as if it continuously reading and writting data. At first, I thought it was an auto-update in progress or some sort of automatic system maintenance. But the odd behavior never stopped. I scanned my files with an anti-virus software - nothing wrong. I scanned my files with Disk Utility - nothing wrong. I used Onyx to check the system - nothing wrong. I even erased and reinstalled the system software - no changes! So what could possibly force my hard disk to behave like that? Is something messed up because of "Erase free space"?

You could run fs_usage
To view file activity for all processes with the fs_usage tool, you would enter the following at the Terminal prompt.
sudo fs_usage
If you wanted to limit the display to files accessed by a particular process, you could redirect the output through the grep tool. For example, to display file behavior for the TextEdit application, you would enter the following at the Terminal prompt:
% sudo fs_usage | grep TextEdit
Once your application finishes launching, stop fs_usage by typing Control-C in your Terminal window.
Look for all writes. Might be mdworker (Spotlight)
Try reindexing Spotlight by dragging the HD icon into the Privacy window. Leave it there for a minute and remove it using the minus button.

[SOLVED]Tuner stoped working after kernel update (2.6.25)

I upgraded kernel 2.6.24 to 2.6.25 and my Hauppauge WINTV tuner stopped working. Although it was recognized as I show in dmesg I had the following error "tuner 1-0061: tuner type not set". I downgraded to kernel 2.6.24 (and also downgraded nvidia and lirc packages which were dependencies) and the tuner works fine. This time tuner type is set correctly "tuner 1-0061: type set to Philips PAL/SECAM m" What should I do to make it work with newest kernel?
This is some info from dmesg relevant to my tuner card.
cx88[0]: subsystem: 0070:3401, board: Hauppauge WinTV 34xxx models [card=1,autodetected]
cx88[0]: TV tuner type -1, Radio tuner type -1
cx2388x alsa driver version 0.0.6 loaded
tveeprom 1-0050: Hauppauge model 34519, rev J260, serial# 10439851
tveeprom 1-0050: tuner model is LG S001D MK3 (idx 60, type 38)
tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
tveeprom 1-0050: audio processor is CX880 (idx 30)
tveeprom 1-0050: has radio
cx88[0]: hauppauge eeprom: model=34519
input: cx88 IR (Hauppauge WinTV 34xxx as /devices/pci0000:00/0000:00:1e.0/0000:05:00.0/input/input6
lp0: using parport0 (interrupt-driven).
cx88[0]/0: found at 0000:05:00.0, rev: 5, irq: 23, latency: 32, mmio: 0xfa000000
tuner 1-0043: chip found @ 0x86 (cx88[0])
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 1-0043: type set to tda9887
tuner 1-0061: chip found @ 0xc2 (cx88[0])
tuner-simple 1-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
tuner 1-0061: type set to Philips PAL/SECAM m
tuner-simple 1-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3))
tuner 1-0061: type set to Philips PAL/SECAM m
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
NVRM: loading NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008
Last edited by axel (2008-06-16 18:13:23)

I tried the latest 2.26.5.6 kernel and I get the same tuner 1-0061: tuner type not set message. This time when I open xawtv I can watch the first channel in my list, but I can't change between channels. Radio doesn't work at all.
Below I include modules that are loaded in kernel .25 and after that those loaded with the working .24 one. Any ideas?
kernel 2.6.25
Module Size Used by
ac 4484 0
acpi_cpufreq 7692 0
agpgart 28244 2 intel_agp,nvidia
ahci 25224 0
ata_generic 5636 0
ata_piix 17668 5
battery 10372 0
btcx_risc 4488 3 cx8800,cx88_alsa,cx88xx
button 6416 0
cdrom 33952 1 sr_mod
compat_ioctl32 1536 1 cx8800
coretemp 6400 0
cpufreq_ondemand 7180 2
crc_itu_t 2304 1 firewire_core
cx8800 28956 0
cx88_alsa 10504 1
cx88xx 59560 2 cx8800,cx88_alsa
dock 7952 1 libata
ehci_hcd 33804 0
evdev 9472 4
ext3 124040 4
fan 4356 0
ff_memless 5128 1 usbhid
firewire_core 36928 1 firewire_ohci
firewire_ohci 16512 0
freq_table 4112 2 cpufreq_ondemand,acpi_cpufreq
hid 39296 1 usbhid
hwmon_vid 3328 1 it87
i2c_algo_bit 6020 1 cx88xx
i2c_core 19348 17 tuner,tea5767,tda8290,tda18271,tda827x,tuner_xc2028,xc5000,tda9887,tuner_simple,mt20xx,tea5761,cx88xx,i2c_algo_bit,tveeprom,v4l2_common,i2c_i801,nvidia
i2c_i801 9232 0
ieee1394 79288 1 ohci1394
intel_agp 23740 0
ipv6 256196 10
ir_common 32772 1 cx88xx
it87 19856 0
jbd 44052 1 ext3
libata 142096 5 pata_acpi,ata_piix,ahci,ata_generic,pata_jmicron
lp 9444 0
mbcache 7172 1 ext3
mt20xx 12040 1 tuner
nvidia 7096356 30
ohci1394 28720 0
parport 31596 3 parport_pc,ppdev,lp
parport_pc 34884 1
pata_acpi 4992 0
pata_jmicron 4224 0
pcspkr 2816 0
ppdev 7556 0
ppp_generic 24348 0
processor 32096 2 thermal,acpi_cpufreq
r8169 25476 0
rtc_cmos 9120 0
rtc_core 15516 1 rtc_cmos
rtc_lib 2944 1 rtc_core
scsi_mod 92204 4 sg,sd_mod,sr_mod,libata
sd_mod 23320 6
sg 27188 0
slhc 6016 1 ppp_generic
snd 46628 14 cx88_alsa,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
snd_hda_intel 336440 1
snd_hwdep 7428 1 snd_hda_intel
snd_mixer_oss 14848 1 snd_pcm_oss
snd_page_alloc 8072 2 snd_hda_intel,snd_pcm
snd_pcm 68228 3 cx88_alsa,snd_hda_intel,snd_pcm_oss
snd_pcm_oss 38656 0
snd_seq 48432 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6796 2 snd_seq_oss,snd_seq
snd_seq_midi_event 6656 1 snd_seq_oss
snd_seq_oss 30336 0
snd_timer 19848 2 snd_seq,snd_pcm
soundcore 6496 1 snd
sr_mod 15300 0
tda18271 31496 1 tda8290
tda827x 10116 1 tda8290
tda8290 12676 1 tuner
tda9887 9348 1 tuner
tea5761 4868 1 tuner
tea5767 6404 1 tuner
thermal 15260 0
tuner 35296 0
tuner_simple 8712 1 tuner
tuner_xc2028 19984 1 tuner
tveeprom 14608 1 cx88xx
uhci_hcd 22288 0
usbcore 129776 4 usbhid,ehci_hcd,uhci_hcd
usbhid 42944 0
v4l1_compat 13956 1 videodev
v4l2_common 10624 2 tuner,cx8800
videobuf_core 15876 3 cx8800,cx88xx,videobuf_dma_sg
videobuf_dma_sg 11396 3 cx8800,cx88_alsa,cx88xx
videodev 31616 3 tuner,cx8800,cx88xx
xc5000 10244 1 tuner
kernel 2.6.24
Module Size Used by
ac 4612 0
acpi_cpufreq 11292 0
agpgart 28120 2 nvidia,intel_agp
ahci 23812 0
ata_generic 5380 0
ata_piix 14852 5
battery 10756 0
btcx_risc 4488 3 cx88_alsa,cx8800,cx88xx
button 6544 0
cdrom 34080 1 sr_mod
compat_ioctl32 1536 1 cx8800
cpufreq_ondemand 7180 2
crc_itu_t 2304 1 firewire_core
cx8800 29104 0
cx88_alsa 10376 1
cx88xx 58792 2 cx88_alsa,cx8800
ehci_hcd 33804 0
evdev 9344 4
ext3 124040 4
fan 3844 0
ff_memless 5128 1 usbhid
firewire_core 36800 1 firewire_ohci
firewire_ohci 16000 0
freq_table 4112 2 cpufreq_ondemand,acpi_cpufreq
hid 38272 1 usbhid
hwmon_vid 3328 1 it87
i2c_algo_bit 6020 1 cx88xx
i2c_core 19584 11 tuner,tea5767,tda8290,tuner_simple,mt20xx,tea5761,cx88xx,i2c_algo_bit,tveeprom,i2c_i801,nvidia
i2c_i801 8848 0
ieee1394 81464 1 ohci1394
intel_agp 22164 0
ipv6 253764 10
ir_common 30724 1 cx88xx
it87 18060 0
jbd 44308 1 ext3
libata 141424 5 pata_acpi,ata_piix,ahci,ata_generic,pata_jmicron
lp 9220 0
mbcache 7168 1 ext3
mt20xx 11912 1 tuner
nvidia 7817696 28
ohci1394 28976 0
parport 31560 3 parport_pc,ppdev,lp
parport_pc 35300 1
pata_acpi 5248 0
pata_jmicron 4352 0
pcspkr 2944 0
ppdev 7556 0
ppp_generic 24596 0
processor 29144 2 thermal,acpi_cpufreq
r8169 25732 0
rtc_cmos 7712 0
rtc_core 15752 1 rtc_cmos
rtc_lib 3072 1 rtc_core
sd_mod 23168 6
sg 26896 0
slhc 6016 1 ppp_generic
snd 46436 14 cx88_alsa,snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
snd_hda_intel 292000 1
snd_hwdep 7556 1 snd_hda_intel
snd_mixer_oss 14848 1 snd_pcm_oss
snd_page_alloc 8072 2 snd_hda_intel,snd_pcm
snd_pcm 70404 3 cx88_alsa,snd_hda_intel,snd_pcm_oss
snd_pcm_oss 38432 0
snd_seq 48464 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6796 2 snd_seq_oss,snd_seq
snd_seq_midi_event 6656 1 snd_seq_oss
snd_seq_oss 30336 0
snd_timer 19588 2 snd_seq,snd_pcm
soundcore 6496 1 snd
sr_mod 15268 0
tda8290 11140 1 tuner
tea5761 4740 1 tuner
tea5767 5636 1 tuner
thermal 12956 0
tuner 40224 0
tuner_simple 8584 1 tuner
tveeprom 14736 1 cx88xx
uhci_hcd 23312 0
usbcore 128620 4 usbhid,uhci_hcd,ehci_hcd
usbhid 42560 0
v4l1_compat 13828 1 videodev
v4l2_common 16256 4 tuner,cx8800,cx88xx,videodev
videobuf_core 15620 3 cx8800,cx88xx,videobuf_dma_sg
videobuf_dma_sg 11524 3 cx88_alsa,cx8800,cx88xx
videodev 26624 2 cx8800,cx88xx

[solved] pacman 4 hangs after "checking for file conflicts"

Like others, I removed yaourt and package-query because they conflicted with pacman4... not worried about that, I'll reinstall them later.
I put the new pacman.conf in place (my old one wasn't really customized). I left SigLevel = Never.
Now, I can run pacman -Sy fine, but if I try to install anything, I it just hangs:
sudo pacman -S audacity
resolving dependencies...
looking for inter-conflicts...
Targets (1): audacity-1.3.14-2
Total Download Size: 3.21 MiB
Total Installed Size: 15.29 MiB
Net Upgrade Size: -0.00 MiB
Proceed with installation? [Y/n]
:: Retrieving packages from extra...
audacity-1.3.14-2-x86_64 3.2 MiB 1397K/s 00:02 [###########################] 100%
(1/1) checking package integrity [###########################] 100%
(1/1) loading package files [###########################] 100%
(1/1) checking for file conflicts [###########################] 100%
I've waited up to 20 or 30 minutes and nothing happens. It's not just audacity, any package I try to install does this.
Suggestions?
Last edited by TheAmigo (2012-01-17 18:55:38)

With --debug switch it prints:
checking for file conflicts...
debug: looking for file conflicts
debug: searching for file conflicts: coreutils
debug: searching for filesystem conflicts: coreutils
debug: searching for file conflicts: ethtool
debug: searching for filesystem conflicts: ethtool
debug: searching for file conflicts: fail2ban
debug: searching for filesystem conflicts: fail2ban
debug: searching for file conflicts: gpgme
debug: searching for filesystem conflicts: gpgme
debug: searching for file conflicts: vim-runtime
debug: searching for filesystem conflicts: vim-runtime
debug: searching for file conflicts: gvim
debug: searching for filesystem conflicts: gvim
debug: searching for file conflicts: hdparm
debug: searching for filesystem conflicts: hdparm
debug: searching for file conflicts: inetutils
debug: searching for filesystem conflicts: inetutils
debug: searching for file conflicts: lib32-glibc
debug: searching for filesystem conflicts: lib32-glibc
debug: searching for file conflicts: lib32-gcc-libs
debug: searching for filesystem conflicts: lib32-gcc-libs
debug: searching for file conflicts: lib32-glib2
debug: searching for filesystem conflicts: lib32-glib2
debug: searching for file conflicts: lib32-gdk-pixbuf2
debug: searching for filesystem conflicts: lib32-gdk-pixbuf2
debug: searching for file conflicts: lib32-pango
debug: searching for filesystem conflicts: lib32-pango
debug: searching for file conflicts: lib32-gtk2
debug: searching for filesystem conflicts: lib32-gtk2
debug: searching for file conflicts: linux
debug: searching for filesystem conflicts: linux
debug: searching for file conflicts: nspluginwrapper
debug: searching for filesystem conflicts: nspluginwrapper
debug: searching for file conflicts: nvidia
debug: searching for filesystem conflicts: nvidia
debug: searching for file conflicts: qtwebkit
debug: searching for filesystem conflicts: qtwebkit
debug: searching for file conflicts: rpcbind
debug: searching for filesystem conflicts: rpcbind
debug: searching for file conflicts: unrar
debug: searching for filesystem conflicts: unrar
debug: searching for file conflicts: xscreensaver
debug: searching for filesystem conflicts: xscreensaver
checking available disk space...
debug: checking available disk space
Without the --debug switch
Proceed with installation? [Y/n]
(21/21) checking package integrity [############################] 100%
(21/21) loading package files [############################] 100%
(21/21) checking for file conflicts [############################] 100%
Note that the 'checking available disk space...' is not printed without the --debug option although it doesn't look like being 'debug output'.
I don't see much disk activity after that and the pacman process uses no CPU time and the process status goes to D in `ps` (man ps says: D: Uninterruptible sleep (usually IO)).
Last edited by drrossum (2012-01-18 21:58:28)

IPhone 3Gs stuck on 5.1.1 (6.15.01) waiting for activation after official unlock

Hello,
my iPhone became eligible for official At&T unlock and I restored it using iTunes as per AT&T instructions. However it had a baseband of 6.15.01. It is still on baseband 6.15.01 after upgrade to 5.1.1. The phone is not getting activated after it boots, it's stuck. Can someone please help.
thanks

No. If it was hacked before you had it unlocked, it's a paper-weight.
This is EXACTLY why Apple advises against it. Hacking and jailbreaking void the warranty and forfeit all rights to support from Apple and on these forums.
You might have some luck searching google, but don't count on it.

[SOLVED] High disk activity after kernel boot

Similar Messages

Maybe you are looking for