[Solved] Hal

Cannot obtain lock on /media/.hal-mtab
I tried today my camera docking station. It was working fine before and now I get this error. I tried my USB Stick and got the same error.
any ideas for a work around or fix this problem?
Last edited by JaDa (2007-08-08 00:20:42)

The answer found in the Archlinux Wiki
http://wiki.archlinux.org/index.php/HAL
USB sticks and drives do not automount correctly
If you are experiencing problems with automounting usb sticks and/or drives, but do not have problems with automounting CDs or DVDs, and if you are able to manually mount the USB device in question, then you should create the file "preferences.fdi" in the folder /etc/hal/fdi/policy and paste the following line into the file
<merge key="volume.ignore" type="bool">false</merge>
Problem solved. But I have no idea why it was happened and what was the problem. It was working fine before. Anyway, now it works and this is important

Similar Messages

[Solved][Hal and Partitions] Newbie problem with hal policy

Hello everybody,
As a new user of archlinux for less than a week I have experienced a great distribution after having been for 1 year on Linux.
After installation I was able to solve most of my problems with the wiki and the forums but there is one problem I cannot resolve.
I have installed Kde 4.2 on my computer and I can mount Usb drives, or CDs with hal (It is in the daemons section of my rc.conf) but strangely I cannot access my other partitions such as my Ubuntu partition (ext3), or the family's Windows partition (Nfts). I have installed nfts-3g for the nfts partition hal refuses to let me access it, I will give you what Dolphin says when I try to access the Nfts:
org.freedesktop.Hal.Device.PermissionDeniedByPolicy: hal-storage-mount-fixed-extra-options no <-- (actions,result)
And for the ext3
org.freedesktop.Hal.Device.PermissionDeniedByPolicy: hal-storage-mount-fixedauth_admin_keep_always <-- (actions,result)
I don't really understand what It means but normally I am allowed to mount partitions.
My /etc/PolycyKit/PolicyKit.conf: http://pastebin.com/m57e94025
And my /etc/dbus-1/system.d/hal.conf: http://pastebin.com/m62861179
I've already tried to configure these two with the wiki and the forums but nothing yet.
If you need more information ask me.
Thanks in advance.
Last edited by auratux (2009-02-23 21:24:29)

You might want to reread the Hal wiki re: Permission Denied with automounter. Your /etc/PolicyKit/PolicyKit.conf seems to be missing the lines mentioned in the wiki.
Edit: Or maybe it is similair to: http://bbs.archlinux.org/viewtopic.php?id=66008
Last edited by bgc1954 (2009-02-22 14:07:10)

[PARTIALLY SOLVED] HAL fails to start

** UPDATE: PARTIALLY SOLVED - SEE BOTTOM OF THE FIRST POST
HAL fails to start. I'm not exactly sure why this is, but I believe it has something to do with my attempts to get automounting working under gnome.
[zen@intellitech ~]$ sudo /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
[zen@intellitech ~]$ vim /etc/rc.conf
MODULES=(acpi-cpufreq cpufreq_ondemand e1000 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore thinkpad_acpi uinput vboxdrv)
DAEMONS=(syslog-ng @network !net-profiles @net-auto @netfs !samba !crond @acpid @dbus @hal @alsa !daemoot !avahi-daemon @cups @ddclient @bluetooth)
[zen@intellitech ~]$ pacman -Q | grep hal
hal 0.5.11-1
hal-info 0.20080508-1
[zen@intellitech ~]$ /usr/sbin/hald --daemon=no --verbose=yes
03:13:37.451 [i] hald.c:669: hal 0.5.11
03:13:37.451 [i] hald.c:734: Will not daemonize
03:13:37.451 [i] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-pdtZvbqaVq,guid=312b47921cba4c5cdbee099a48ec87d1
03:13:37.452 [E] ck-tracker.c:367: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
03:13:37.452 [E] ck-tracker.c:792: Could not get seats and sessions
03:13:37.452 [W] hald_dbus.c:5806: Could not initialize seats and sessions from ConsoleKit
Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
03:13:37.453 [i] hald_runner.c:301: Runner has pid 3675
03:13:37.453 [i] hald_runner.c:182: runner connection is 0x15bdec0
03:13:37.456 [W] osspec.c:373: Unable to open /proc/mdstat: No such file or directory
03:13:37.457 [D] util_helper.c:124: drop_privileges: could not set group id
[zen@intellitech ~]$ vim /etc/group
root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin
adm::4:root,daemon
tty::5:root,zen
disk::6:root,zen
lp::7:daemon
mem::8:
kmem::9:
wheel::10:root,zen
ftp::11:
mail::12:
log::19:root
smmsp::25:
games::50:
network:x:90:zen
video:x:91:zen
audio::92:root,zen
optical::93:root,zen
floppy:x:94:root,zen
storage:x:95:root,zen
power:x:98:root,zen
nobody::99:
users::100:zen
locate:x:21:
uucp:x:14:
http:x:33:
scanner:x:96:
dbus:x:81:root,zen
hal:x:82:root,zen
avahi:x:84:root,zen
camera:x:97:
gdm:x:101:
vboxusers:x:108:zen
samba:x:109:zen,root
* Yes, I know it is bad practice to have a normal user listed under the disk group. It is necessary, however, in order to have raw disk access for virtual box.
[zen@intellitech ~]$ sudo /etc/rc.d/dbus stop
:: Stopping D-BUS system messagebus [DONE]
[zen@intellitech ~]$ sudo /etc/rc.d/hal start
:: Starting D-BUS system messagebus [DONE]
:: Starting Hardware Abstraction Layer [FAIL]
It's odd, because D-BUS will start but hal will not... Anybody have any suggestions?
* UPDATE (10/08/08): Did a full system upgrade and removed dbus from daemons array in rc.conf. UDEV EVENTS Processing speed seems to be back to normal.
** SOLUTION UPDATE: After removing custom ntfs-3g fdi policies from /etc/hal/fdi/policy/, hal seems to load without any problems. This seems to be a bug, since my policies were working at one point, and I believe a hal update caused the problem. I'll see if I can track down the exact hal version that it breaks on, and submit a respective bug report for it.
** OFF-TOPIC UPDATE: Using hwdetect --modules to get a modules list, and using these modules in rc.conf with MOD_AUTOLOAD turned off (and also in mkinitcpio.conf and running mkinitcpio -g <path>), seems to have dramatically increased my "Load udev events" processing time. After doing this, my udev speed went from almost 4000ms to literally < 500ms.
Last edited by intellitech (2008-10-08 14:58:53)

koch wrote:
intellitech wrote:DAEMONS=(syslog-ng @network !net-profiles @net-auto @netfs !samba !crond @acpid @dbus @hal @alsa !daemoot !avahi-daemon @cups @ddclient @bluetooth)
you have dbus starting before hal but hal starts debus by default so please try this...
DAEMONS=(...@acpid @hal @alsa...)
and delete debus from that line.
Removed dbus from the daemons array and hal still won't start. Also, I noticed that the "Loading udev events" portion of the boot process seems to take a lot longer than it used to. Last boot, it took about 19130ms, whereas it used to take < 3000ms. Could these be related?
Also, I ran a full system upgrade, both udev and hal were upgraded.
[zen@intellitech ~]$ pacman -Q | grep hal
hal 0.5.11-4
hal-info 0.20080508-1
[zen@intellitech ~]$ pacman -Q | grep udev
klibc-udev 128-1
udev 128-5

(SOLVED) hal and automounting

Hallo. I am e newbie of Arch. Two months ago I installed Arch on pc without problem and with a very few customisation. I tryed to do the same with my laptop. Installation with the last set was found on web was ok, but now ... I am unable to see hotplugged usb pen drives, external usb disk, internal partition. I can mount them manually by fstab edit or just console, but I see them as folder :-(
What seems strange to me is that on Arch pc all is right, and I can see the drives in dolphin even if not mounted.
Last edited by Yagi858 (2008-12-18 00:17:20)

Really sorry ... The laptop is HP Pav dv2000 series, the PC is HP too. The desktop environment for both is KDE4 from extra repo. I made just a bit of manually setting ... rc.conf and lcd-font. It' s a really clean standard installation following the cd menu.
OK. SOLVED !!!
Removed and reinstalled udev. Strange that pacman -Suy didn't see the new version ...
Last edited by Yagi858 (2008-12-18 00:16:46)

[SOLVED] HAL don't start-

Hello!
It appears that my HAL now [FAIL] at startup even if it is in my rc.conf.
I've tried
# /etc/rc.d/hal restart
:: Stopping Hardware Abstraction Layer [FAIL]
:: Starting Hardware Abstraction Layer [FAIL]
DBUS is also installed…
The weird thing is that worked great before… and not even because of an upgrade, it fails…
Have you some ideas ?
Last edited by jiehong (2009-06-18 21:40:03)

It also says [FAIL] for me, yet HAL still functions correctly (automounts drives, etc). Are you sure the daemon doesn't work anyway?

[solved] hal won't mount volumes after update

Every time I try to mount it, hal gives me an error:
Rejected send message, 1 matched rules; type="method_call", sender=":1.12" (uid=1000 pid=3528 comm="pcmanfm) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3228 comm="/usr/sbin/hald))
Followed by:
Directory doesn't exist!
I really don't know what the deal is, and google doesn't turn up much of anything.
Edit: This is for all drives not mounted at boot, same error.
Drives can be manually mounted with no problems.
Edit: This happens regardless of file manager used.
Solution: In my case I needed ck-launch-session added to my ~/.xinitrc for mounting to work. So, this:
exec openbox-session
Became this:
exec ck-launch-session openbox-session
If this doesn't work for you, following the instructions on the hal wiki page as seen in anonymous_user's post (#11) most likely will.
Last edited by z.s.tar.gz (2009-11-12 12:32:57)

skottish wrote:
simongmzlj wrote:
I had this problem to (running Xfce).
I fixed it by removing policykit from my machine and restarting. The new version of hal drops policykit as a dependency. I don't know whats the reasoning behind this, as hal doesn't seem to support polkit integration (at least there is no compile flag for it). So policykit now seems to interfere with the new hal package.
Edit: Spelling
hal requires consolekit and polkit is required by it. How the disable consolekit integration bit works I don't understand.
You can disable consolekit by editing the PKGBUILD:
--disable-console-kit --disable-policy-kit --disable-acl-management
EDIT: When building the package from scratch, it seems --enable-consolekit needs --enable-policykit, i might be wrong
EDIT: I was wrong
Last edited by simongmzlj (2009-11-11 04:48:26)

[SOLVED] Hal daemon causing 3 keystrokes instead of 1

I've installed arch several times before and I've never had this problem. I'm pretty sure it's the hal daemon because "sudo /etc/rc.d/hal stop" fixes the problem. Also, the keystrokes only repeat while in X and it doesn't matter what window manager I use.
Any ideas?
Last edited by siodine (2008-12-23 23:38:29)

http://bugs.archlinux.org/task/12519
your xorg.conf isn't configured well
Last edited by wonder (2008-12-23 10:49:19)

[SOLVED]Hal refuse to stop: FAIL. Using quick-init

When i try to restart hal to see if my policy configuration file are ok (for automount), i have this issue:
:: Stopping Hardware Abstraction Layer [FAIL]
:: Starting Hardware Abstraction Layer [FAIL]
i'm using kdemod 4 and quickinit-scripts... Is there a solution? i intend to not restart dbus, but ONLY hal..thanks
Last edited by chesterfork (2009-07-14 18:23:49)

obviously answer:yes i'm root.... ; on the logs there's no errors...hal works fine, apart automountig ntfs in kdemod (i have to click in dolphi to activate the device)....but when i change policy i have: or to restart dbus or reboot.....
me too can't start to troubleshooting...i miss something....at the start no errors, no problems.....????!!!
Last edited by chesterfork (2009-07-13 12:49:43)

[solved] HAL fails repeatedly..

My HAL is failing on every boot and if I try to start it manually:
[shane@Shane-Arch log]$ sudo /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
Also... there is something else failing on boot, but it goes too fast. I can't seem to find a boot-up log. I'm sure it's somewhere, can someone point me in the right direction?
Thanks,
Shane
Last edited by krazyshane (2007-12-01 19:23:08)

Hmm... it's not pretty CPU Soft lockups? But I see nothing about HAL
[shane@Shane-Arch ~]$ dmesg
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Time: tsc clocksource has been installed.
pnp: 00:00: iomem range 0x0-0x9fbff could not be reserved
pnp: 00:00: iomem range 0x9fc00-0x9ffff could not be reserved
pnp: 00:00: iomem range 0xc0000-0xcffff could not be reserved
pnp: 00:00: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:02: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:02: ioport range 0x800-0x805 has been reserved
pnp: 00:02: ioport range 0x808-0x80f has been reserved
pnp: 00:03: ioport range 0xf400-0xf4fe has been reserved
pnp: 00:03: ioport range 0x806-0x807 has been reserved
pnp: 00:03: ioport range 0x810-0x85f has been reserved
pnp: 00:03: ioport range 0x860-0x87f has been reserved
pnp: 00:03: ioport range 0x880-0x8bf has been reserved
pnp: 00:03: ioport range 0x8c0-0x8df has been reserved
pnp: 00:08: ioport range 0x900-0x97f has been reserved
PCI: Bridge: 0000:00:01.0
IO window: c000-cfff
MEM window: fc000000-fdffffff
PREFETCH window: d0000000-dfffffff
PCI: Bus 3, cardbus bridge: 0000:02:01.0
IO window: 0000d000-0000d0ff
IO window: 0000d400-0000d4ff
PREFETCH window: 40000000-43ffffff
MEM window: 48000000-4bffffff
PCI: Bridge: 0000:00:1e.0
IO window: d000-efff
MEM window: f6000000-fbffffff
PREFETCH window: 40000000-43ffffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
PCI: Enabling device 0000:02:01.0 (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 1499k freed
apm: BIOS not found.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 [email protected]).
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Boot video device is 0000:01:00.0
isapnp: Scanning for PnP cards...
Switched to high resolution mode on CPU 0
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7
PCI: setting IRQ 7 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.6[b] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
ACPI: PCI interrupt for device 0000:00:1f.6 disabled
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: module loaded
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
Freeing unused kernel memory: 296k freed
libata version 2.21 loaded.
ata_piix 0000:00:1f.1: version 2.12
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1f.1 to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001bfa0 irq 14
ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001bfa8 irq 15
ata1.00: ATA-6: HTS726060M9AT00, MH4OA68A, max UDMA/100
ata1.00: 117210240 sectors, multi 8: LBA48
ata1.00: configured for UDMA/100
ata2.00: ATAPI: QSI CD-RW/DVD-ROM SBW242U, UD25, max UDMA/33
ata2.00: configured for UDMA/33
scsi 0:0:0:0: Direct-Access ATA HTS726060M9AT00 MH4O PQ: 0 ANSI: 5
scsi 1:0:0:0: CD-ROM QSI CDRW/DVD SBW242U UD25 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 117210240 512-byte hardware sectors (60012 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 117210240 512-byte hardware sectors (60012 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
sr0: scsi3-mmc drive: 4x/24x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
b44.c:v1.01 (Jun 16, 2006)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
eth0: Broadcom 4400 10/100BaseT Ethernet 00:0f:1f:27:e6:5b
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <[email protected]>
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
ipw2100: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
Clocksource tsc unstable (delta = 279234988 ns)
Time: acpi_pm clocksource has been installed.
ACPI: PCI Interrupt 0000:00:1f.5[b] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 52775 usecs
intel8x0: clocking to 48000
ACPI: PCI Interrupt 0000:00:1f.6[b] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
PCI: Setting latency timer of device 0000:00:1f.6 to 64
MC'97 1 converters and GPIO not ready (0xff00)
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
Marking TSC unstable due to: possible TSC halt in C2.
ACPI: AC Adapter [AC] (off-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Battery Slot [BAT1] (battery absent)
input: Lid Switch as /devices/virtual/input/input2
ACPI: Lid Switch [LID]
input: Power Button (CM) as /devices/virtual/input/input3
ACPI: Power Button (CM) [PBTN]
input: Sleep Button (CM) as /devices/virtual/input/input4
ACPI: Sleep Button (CM) [SBTN]
ACPI: Thermal Zone [THM] (25 C)
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 1:0:0:0: Attached scsi generic sg1 type 5
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 11, io base 0x0000bf80
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[b] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 11, io base 0x0000bf40
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
Linux agpgart interface v0.102
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 11, io base 0x0000bf20
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
agpgart: Detected an Intel 855PM Chipset.
agpgart: AGP aperture is 128M @ 0xe0000000
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 11, io mem 0xf4fffc00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
intel_rng: FWH not detected
input: PS/2 Mouse as /devices/virtual/input/input5
input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input6
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one day
ACPI: PCI Interrupt 0000:02:01.1[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
input: Video Bus as /devices/virtual/input/input7
ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] MMIO=[faffd800-faffdfff] Max Packet=[2048] IR/IT contexts=[4/8]
Yenta: CardBus bridge found at 0000:02:01.0 [1028:0191]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:01.0, mfunc 0x012c1202, devctl 0x64
Yenta: ISA IRQ mask 0x0478, PCI irq 11
Socket status: 30000086
Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
pcmcia: parent PCI bridge I/O window: 0xd000 - 0xefff
cs: IO port probe 0xd000-0xefff: clean.
pcmcia: parent PCI bridge Memory window: 0xf6000000 - 0xfbffffff
pcmcia: parent PCI bridge Memory window: 0x40000000 - 0x43ffffff
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x3e0-0x4ff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
ieee1394: Host added: ID:BUS[0-00:1023] GUID[5b4fc0003fffffff]
EXT3 FS on sda3, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1542232k swap on /dev/sda2. Priority:-1 extents:1 across:1542232k
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
[drm] Initialized radeon 1.28.0 20060524 on minor 0
ieee80211_crypt: registered algorithm 'WEP'
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Setting GART location based on new memory map
[drm] Loading R300 Microcode
[drm] writeback test succeeded in 3 usecs
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
eth1: no IPv6 routers present
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<c0360000>] wait_for_completion+0x30/0xa0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e006 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e006 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e006 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e006 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e006 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e006 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0x86 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e006 <keycode>' to make it known.
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c018fdce>] dput+0xee/0x100
[<c0104ee7>] common_interrupt+0x23/0x28
[<c013af01>] sys_setpriority+0x1/0x1e0
[<c0104482>] sysenter_past_esp+0x6b/0xa1
[<c0360000>] wait_for_completion+0x30/0xa0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<c017007b>] try_to_unmap+0xdb/0x480
[<c017f663>] sys_llseek+0x3/0xb0
[<c017f751>] sys_read+0x41/0x70
[<c0104482>] sysenter_past_esp+0x6b/0xa1
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c010ac33>] sched_clock+0x13/0x30
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================
BUG: soft lockup detected on CPU#0!
[<c0157d9a>] softlockup_tick+0xea/0x120
[<c0135853>] update_process_times+0x33/0x80
[<c0149077>] tick_sched_timer+0x77/0xf0
[<c0143fc3>] hrtimer_interrupt+0x163/0x1f0
[<c0149000>] tick_sched_timer+0x0/0xf0
[<c0107d61>] timer_interrupt+0x31/0x40
[<c0158140>] handle_IRQ_event+0x30/0x60
[<c0159a9d>] handle_level_irq+0x7d/0xf0
[<c010717b>] do_IRQ+0x3b/0x70
[<c0104ee7>] common_interrupt+0x23/0x28
[<f09880b0>] acpi_processor_idle+0x29c/0x434 [processor]
[<c0102453>] cpu_idle+0x73/0xe0
[<c0435a6a>] start_kernel+0x30a/0x3a0
[<c0435140>] unknown_bootoption+0x0/0x1f0
=======================

[solved] HAL problem

Hi everyone!
I booted my main machine this morning to find no network connection, further investigation reveals that HAL is not running.
I checked out a few threads on the forum regarding using the verbose switch to get some output and here is what I get (shortened because there is a lot!)
device_info.c:1109: Unhandled rule (0) !
device_info.c:1109: Unhandled rule (312) !
Segmentation fault
I don't think anything has changed since it worked yesterday, I moved some partitions around and changed their sizes but everything else seems fine and I cant see how that would affect HAL? (or maybe it would??)
Thanks in advance for any advice
Edit: Removed HAL and re-installed for about the 7th time worked for some reason. (Persistence pays off!)
Last edited by scottuss (2009-03-03 15:59:24)

wonder wrote:because you merged a default /etc/group file with you current group file. BIG MISTAKE
you can try to add missing groups and then add your username to them.
also i think /etc/group- is a backup and you can rename it to /etc/group
I added the missing entries from my group file to group.pacsave file, and then moved the pacsave file to /etc/group.
I compared with /etc/group- and those files are identical.

(SOLVED) Hal and dbus, do I need dbus?

I read the wiki and it says if I don't use hal in my daemons then I need to add dbus.
I haven't been using hal, and I haven't added dbus either. My system seems to be working right, but I guess something could be wrong. Reading the wiki brings me here to ask if I need dbus and why?
My daemons,
DAEMONS=(@syslog-ng @network !netfs @alsa @mpd @crond)
Last edited by Google (2010-07-03 11:21:11)

sudo pacman -R dbus
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: avahi: requires dbus>=1.1.20-1
:: awesome: requires dbus
:: gconf: requires dbus
:: qt: requires dbus
I assume I should add it to daemons?
Last edited by Google (2010-07-03 10:08:18)

[SOLVED]HAL and multiple mount attempts

Recently I managed to break my HD and so had to reinstall everything. Everything is working about the way they used to BUT:
Everytime I put CD or DVD into my DVD-drive or try to use USB-stick HAL for some reason tries to mount the media 3 times. Discs give two error messages for mount point being allready in use but otherwise work fine, USB-sticks doesn't give any errors but open three filemanager windows. Problem is mainly cosmetic because everything works, it's just annoying...
Anybody have a clue what I might have done wrong?
Last edited by FrozenSoil (2008-03-28 13:15:03)

Seems like it wasn't HAL problem after all. I had turned on automounting from XFCE settings and that was causing multiple attempts. I unchecked everything from XFCE automount options and now it's working as it should.

[SOLVED] HAL doesn't work, so I can't suspend/hibernate?

I've placed (atleast what I think) to be the necessary daemons in rc.conf:
DAEMONS=(syslog-ng dbus md fam hal alsa network netfs crond)
FAM for XFCE..
When I run the suspend command, it states
"Failed to suspend: Suspend and hibernate are only supported by HAL and is not available."
#sudo /etc/rc.d/hal start:
:: Starting Hardware Abstraction Layer [FAIL]
This happens in root, and when I attempt to start and stop it....
It took endless configurations to get ndiswrapper to work, I've changed only but files required for network, why could hal not work? I can't find much online about how to fix it, and what steps there are if it fails to restart..
Last edited by Nullw0rm (2010-01-30 05:42:58)

Doehni wrote:
Try putting the network and netfs daemons before fam and hal.
Something like this:
DAEMONS=(syslog-ng dbus md alsa network netfs crond fam hal)
Hope it helps!
I tried this and it..sorta works, restarting HAL:
[me@myhost ~]$ sudo /etc/rc.d/hal restart
:: Stopping Hardware Abstraction Layer [DONE]
:: Starting Hardware Abstraction Layer [DONE]
(DONE instead of FAIL)
But going to suspend/hibernate it says HAL is not available still! I seem to not be able to set it up so well..
It says I already have pm-utils, but I ahead and installed that anyway (assuming mine wasn't dev release).
I can suspend with
$ sudo pm-suspend
But when I resume video doesn't start, my screen is black (not displaying black, more like off).. I'm on a laptop with an intel X3000 graphics chip, not a PC in case that helps.
Help
Last edited by Nullw0rm (2010-01-29 03:05:55)

[SOLVED] hal, udev, udisks, pcmanfm, policy kit, automount confusion

Hello all,
I'm having a problem getting pcmanfm to recognise my external HD in the left panel, although it can be mounted manually. Upon searching this forum and the wiki to find a solution all I have managed to do is confuse myself.
Any help is appreciated.
Last edited by guriinii (2010-09-26 00:53:53)

The pcmanfm in Arch currently uses gvfs/gnome-disk-utility for mounting. I'd suggest either install pcmanfm-0.5.2 which uses HAL directly, or a git version of pcmanfm which uses udisks directly. In either case though, you'll need ck-launch-session.

[SOLVED]hal and network not running on boot

My hal and network are not running on boot. I have to manually start them once I login. I have put them as Daemons in rc.conf and it still does not seem to help.
Thanks!
Last edited by Eman2005 (2010-02-06 00:42:29)

I figured out what was wrong, the D in Daemons for the rc.conf file was a lowercase d for whatever reason. But now I have a bigger problem, I seem to have lost the files for my sound card. I used to have the soundcard listed in alsamixer. Now it is not there. when I do a
$ cat /proc/asound/cards
it is not listed, although it used to. however I can still
modprobe snd-emu10k1
It is the Creative Labs SB Live! EMU10k1 I have tried to reinstall alsa. I reinstalled alsa-utils and alsa-oss, but I am not sure how to uninstall alsa-lib because of dependencies. PLEASE HELP.

[***Solved***] Hal

Similar Messages

Maybe you are looking for

[Solved] Hal