[hardy][2.6.24-15] Failed to initialize HAL

[thom]

Hi There,

Updated from kernel 2.6.24-14 to 2.6.24-15 on 04-04-2008

2.6.24-14:
no problems at all (besides some minor fglrx related issues...grinnn...what's new ;-) )

2.6.24-15:
After logging in in Gnome the system reports "Failed to initialize HAL" and, of course, most of my hardware is virtually missing.
Alternatively the system not even gets to start gdm or X and hangs during probing USB devices.
Strangely enough a fresh install gives the same results.

Another strange thing: my other computer (which updates simultaneously) has no problem whatsoever (works like a charm) :-)

Unfortunately I am too much of a n00b to pinpoint the exact location of the bug so if you need any extra information please ask.

AFAIK It is not related to video-driver issues for both restricted and open source drivers make no difference at all.

Aside all of this: I am very very pleased/happy/joyful with the way Hardy is developing and I'll definitely stick to it
To all the developers of Hardy out there: Sometimes I can't believe Hardy is really happening. YOU GUYS ARE FABULOUS!! :-)

greetz, Tom

[kenmaster (giovanniutem)]

The same situation with the kernel 2.24.26-15, After logging in in Gnome the system reports "Failed to initialize HAL".

[thom (tsk)]

I don't know of any existing kernel 2.24.xx-xx , are you sure you didn't make a typo ? :-)

[Marius Meinert (supermunro)]

With 2.6.24-15 my system hangs at hardware detection too. Maybe the udev logs contain some useful information?

[thom (tsk)]

I rebooted in the -15 kernel and saved a copy of /var/log/udev to my $home but as far as i can see on the timestamp it hasn't been touched during boot time. Furthermore, I am too much of a noob to understad the log good enough to make sense of it. Nevertheless, here it is :-)

[jua ignacio (juancherru-hotmail)]

Same situation here. Kernel 2.6.24-15-generic

[Ariel O. Quarchioni (arieloq)]

this happen only in the x64 bits version or in x32 bits too?... cos in my x64 gives me the same problem, but in a x32 installation d´not

[jua ignacio (juancherru-hotmail)]

I can confirm this bug in x32 bits too.

[thom (tsk)]

Both my machines are running the x32 version of hardy. My desktop machine processor is a P4 model 640, my laptop processor is a P4 model 530, both do hyperthreading.
The Desktop machine chokes on 2.6.24-15, my laptop doesn't :-/

 The 640 is potentially capable of executing x64 instructions but I doubt if that has anything to do with it.

[Rick (masef)]

System hangs for me after probing USB printer: Kernel 2.6.24.14 works well on my setup however 2.6.24.15 hangs>>
Error msg below before I restarted machine.

Apr 5 18:55:41 machalogo kernel: [ 29.678225] ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 19
Apr 5 18:55:41 machalogo kernel: [ 30.311977] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x043D pid 0x009F
Apr 5 18:55:41 machalogo kernel: [ 30.312100] usbcore: registered new interface driver usblp
Apr 5 18:55:41 machalogo kernel: [ 203.472339] loop: module loaded
Apr 5 18:55:41 machalogo kernel: [ 203.519621] lp0: using parport0 (interrupt-driven).
Apr 5 18:55:41 machalogo kernel: [ 203.654342] Adding 2048248k swap on /dev/sdb1. Priority:-1 extents:1 across:2048248k
Apr 5 18:55:41 machalogo kernel: [ 249.730369] EXT3 FS on sdb2, internal journal
Apr 5 18:55:41 machalogo kernel: [ 274.515432] kjournald starting. Commit interval 5 seconds
Apr 5 18:55:41 machalogo kernel: [ 274.515778] EXT3 FS on sdb3, internal journal
Apr 5 18:55:41 machalogo kernel: [ 274.515788] EXT3-fs: mounted filesystem with ordered data mode.
Apr 5 18:55:41 machalogo kernel: [ 274.992036] ip_tables: (C) 2000-2006 Netfilter Core Team
Apr 5 18:55:41 machalogo kernel: [ 285.603172] No dock devices found.
Apr 5 18:55:43 machalogo dhcdbd: Started up.

[macsim (macsim)]

Hi, I can confirm the bug too, Hardy works fine with 2.6.24-14-generic but after the upgrade on 2.6.24-15-generic I have the "Failed to initialize HAL"

Ask if you want specific info about my config.
thanks

[Amran (amx109)]

i too can confirm this bug on 2.6.24-15

as with macsim, 2.6.24-14 works fine.

[bozza (jochen-borris)]

I can also confirm this bug - anybody who knows how to fix the problem?

Regards, Bozza

[Marcos Magalhães (marcos-daekdroom)]

I think this bug might be related to this one:
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/212271

Who here uses saa7134 module?

[jua ignacio (juancherru-hotmail)]

I have a Pinnacle PCI tvcard installed in mi pc. I´m at work right now, so i can´t confirm if that module is in use.

Thanks.

[Amran (amx109)]

@marcos i use sa7134 for my tv card. thanks for the additional info

On Mon, Apr 7, 2008 at 7:29 PM, Marcos Vinícius <email address hidden>
wrote:

> I think this bug might be related to this one:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/212271
>
> Who here uses saa7134 module?
>
> --
> [hardy][2.6.24-15] Failed to initialize HAL
> https://bugs.launchpad.net/bugs/212221
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Marius Meinert (supermunro)]

I use it too, I attached a list of saa-related modules that i loaded. I'll try to blacklist the saa ones, as I don't use this TV-Card.

[Marius Meinert (supermunro)]

The saa7134-modules are definitely related to the problem. Blacklisting them caused my -15-kernel-system to boot up normally.

[thom (tsk)]

Hey Marcos, Thanks!!

Yes, I too have a SAA7134 TV-tuner/capture card in my desktop pc.
Seems to me that it is highly likely to be the problem.
I will try to blacklist it and see if i can revive the system :-)

I'll be back ;-)

Good work!!

[bozza (jochen-borris)]

Hi Thom

I too have the SAA7134 card (Pinnacle tv card). - Could you briefly explain to me (as I my enthusiasm for linux is greater than my experience with it) what "blacklisting" is and how I can blacklist certain modules. Also, after blacklisting the SAA7134 module will I still be able to use that module, i.e. to watch TV?

Thank you for your help in advance.

Regards, Bozza

[Marius Meinert (supermunro)]

A module is an extension for your kernel that adds functionality to it, in this case the ability to use the saa7134 tv-card. Many modules are loaded automatically at boot time. You can forbid this by blacklisting them. To blacklist a module just add the line "blacklist modulename" to the /etc/modprobe.d/blacklist file. This will tell your system not to load the module.
In our case you would add the lines
blacklist saa7134
blacklist saa7134_dvb
to the blacklist file.
But by not loading the module you "remove" the functionality to use your tv-card. So you won't be abled to watch TV with this Card.
If you rely on your card it would be best to use the 2.6.24-14 kernel and wait until the problem is fixed.

[macsim (macsim)]

I have the saa73134 too I'll try with blacklist.

bozza, to blacklist a module just add this 2 line in /etc/modprobe.d/blacklist

# blacklist saa7134 https://bugs.launchpad.net/ubuntu/+bug/212221
blacklist saa7134

[thom (tsk)]

Hi Bozza,

Blacklisting will disable the loading of the modules you specify i.e. they will not be loaded automagically and the dependent hardware will NOT work if there aren't any replacement modules.
Of course this is not funny but it will help you to determine if the specified module is the metaphorical "sand in the engine" ;-)

To give you an idea what modules have been loaded on your machine type:

lsmod | less

this is, of course, a very long list so type :

lsmod | grep 7134 | less

now you see the modules of the saa 7134 driver
So, now we are going to check what has been blacklisted already:

less /etc/modprobe.d/blacklist

Got the idea ? ;-)
Now start editing:

sudo gedit /etc/modprobe.d/blacklist

and enter the following lines:

#this line is comment but will keep reminding me why i do the following stuff for my TV card
blacklist saa7134

now save it en reboot,

Happy Hacking ;-)

[thom (tsk)]

Hi all,

I can confirm that blacklisting the saa7134 solved the problem!!
My system boots up perfectly now.

Next question:

How do we get the saa7134 working ? :-(

[jua ignacio (juancherru-hotmail)]

Didn't work for me. saa7134 wasn't load in mi machine so black listing is not an option. Dmesg is attached.

[thom (tsk)]

Hey Jua,

[ 124.350690] end_request: I/O error, dev fd0, sector 0

It seems that this problem is unrelated to your TV card.
Do you, by any chance, have a buggy or detachable floppydrive ?

[jua ignacio (juancherru-hotmail)]

I do have a floppy drive since this is a desktop computer. I never use it. What is your suggestion?

[Rick (masef)]

Have a ComproMate TV card with saa7130 chipset on machine too.

Blacklisting saa7134 allows kernel to boot to desktop.

Problem solved for me for now.

[thom (tsk)]

Hi Jua,

Try to disable the floppydrive in your BIOS settings and see if you can boot up normally.

[thom (tsk)]

Hi all,

According to

https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/212271

The kernel team is working on it :-)

[bozza (jochen-borris)]

Hi everybody

indeed, on my PC, too, blacklisting of the saa7134 leads to faster booting but graphics start in low resolution mode (graphic card not recognized), there is still the error message "failed to initialize hal", connection to the internet via WLAN is not possible and shutdown of the system is terribly slow.

I restarted the system with kernel 2.6.24-14 (which works without problems) and installed the latest updates (9th April, ca. 7:00 pm) but this did not fix the problems with 2.6.24-15 at all.

Does anybody of you know whether the latest updates are at all supposed to bring along the fix?

Thanks again to the lively Ubuntu community for the support!

Bozza

[Juan C. Villa (juanqui)]

The latest updates have not fixed the issue yet. Go to this bug report https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/212960, they have a proposed patch that will fix the problem. You will need to recompile your alsa kernel modules. Let me know how that works out for you.

[thom (tsk)]

Hi Bozza,

could you attach the output of dmesg, lsmod and lspci ?

(although I'm still a bit of a n00b and not really tech savvy, I might find something)

[bozza (jochen-borris)]

Hi Thom

here is my dmesg, lsmod and lspci.

1. dmesg

[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled)
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] Allocating PCI resources starting at 30000000 (gap: 20000000:dec00000)
[ 0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
[ 0.000000] swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129906
[ 0.000000] Kernel command line: root=UUID=0eafdf36-1390-4e01-9401-525904fe33e6 ro quiet splash
[ 0.000000] mapped APIC to ffffb000 (fee00000)
[ 0.000000] mapped IOAPIC to ffffa000 (fec00000)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 2048 (order: 11, 8192 bytes)
[ 0.000000] Detected 2660.041 MHz processor.
[ 16.319149] Console: colour VGA+ 80x25
[ 16.319153] console [tty0] enabled
[ 16.319389] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 16.319617] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 16.329020] Memory: 506772k/523712k available (2164k kernel code, 16308k reserved, 1006k data, 364k init, 0k highmem)
[ 16.329029] virtual kernel memory layout:
[ 16.329031] fixmap : 0xfff4b000 - 0xfffff000 ( 720 kB)
[ 16.329032] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
[ 16.329033] vmalloc : 0xe0800000 - 0xff7fe000 ( 495 MB)
[ 16.329034] lowmem : 0xc0000000 - 0xdff70000 ( 511 MB)
[ 16.329035] .init : 0xc041f000 - 0xc047a000 ( 364 kB)
[ 16.329037] .data : 0xc031d1cd - 0xc0418dc4 (1006 kB)
[ 16.329038] .text : 0xc0100000 - 0xc031d1cd (2164 kB)
[ 16.329041] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[ 16.329076] SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
[ 16.408901] Calibrating delay using timer specific routine.. 5324.75 BogoMIPS (lpj=10649511)
[ 16.408925] Security Framework initialized
[ 16.408932] SELinux: Disabled at boot.
[ 16.408946] AppArmor: AppArmor initialized
[ 16.408951] Failure registering capabilities with primary security module.
[ 16.408960] Mount-cache hash table entries: 512
[ 16.409092] CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 00000000
[ 16.409106] CPU: Trace cac...

[thom (tsk)]

Hi Bozza,

Everything looks normal as far as i can see. According to the dmesg, lsmod and lspci output your system should be up and running without any hardware/driver abnormalities.

btw, this is the output with 2.6.24-15 as running kernel ??

If so than i don't have a clue on what goes wrong :-(

[datanytt-thomas (thomas-datanytt)]

I can confirm this bug on 2.6.24-15-generic (x86), and blacklisting the saa7134 fixed the problem.

My TV card is a hauppauge HVR-1100.

[frank (dallco)]

I also can confirm this bug on 2.6.24-15-generic (x86), and blacklisting the saa7134 fixed the problem.

its a fujitsu siemens (creatix saa 7134) that is

[bozza (jochen-borris)]

Hi Thom

you were right - I posted dmesg, lsmod and lspci output of the kernel ..14 which works fine. Sorry about that. Here now the corresponding data with the kernel ....16 (update of today) which still - at least in my case - has not fixed the issue:

1. Dmesg:

[ 16.196058] PCI: Using ACPI for IRQ routing
[ 16.196062] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
[ 16.220091] NET: Registered protocol family 8
[ 16.220093] NET: Registered protocol family 20
[ 16.220215] hpet clockevent registered
[ 16.220222] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 16.220227] hpet0: 3 64-bit timers, 14318180 Hz
[ 16.221269] AppArmor: AppArmor Filesystem Enabled
[ 16.224072] Time: tsc clocksource has been installed.
[ 16.232097] system 00:00: iomem range 0x0-0x9ffff could not be reserved
[ 16.232101] system 00:00: iomem range 0x100000-0xffffff could not be reserved
[ 16.232103] system 00:00: iomem range 0x1000000-0x1ff6ffff could not be reserved
[ 16.232106] system 00:00: iomem range 0xc0000-0xfffff could not be reserved
[ 16.232109] system 00:00: iomem range 0xfec00000-0xfec0ffff could not be reserved
[ 16.232112] system 00:00: iomem range 0xfee00000-0xfee0ffff could not be reserved
[ 16.232115] system 00:00: iomem range 0xfed20000-0xfed8ffff could not be reserved
[ 16.232118] system 00:00: iomem range 0xfecf0000-0xfecf0fff could not be reserved
[ 16.232120] system 00:00: iomem range 0xffb00000-0xffbfffff could not be reserved
[ 16.232123] system 00:00: iomem range 0xffc00000-0xffffffff could not be reserved
[ 16.232136] system 00:0b: ioport range 0x800-0x85f has been reserved
[ 16.232139] system 00:0b: ioport range 0xc00-0xc7f has been reserved
[ 16.232141] system 00:0b: ioport range 0x860-0x8ff could not be reserved
[ 16.262532] PCI: Bridge: 0000:00:01.0
[ 16.262534] IO window: disabled.
[ 16.262540] MEM window: fc000000-feafffff
[ 16.262545] PREFETCH window: d8000000-efffffff
[ 16.262550] PCI: Bridge: 0000:00:1e.0
[ 16.262554] IO window: d000-dfff
[ 16.262559] MEM window: fbf00000-fbffffff
[ 16.262563] PREFETCH window: disabled.
[ 16.262581] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[ 16.262593] NET: Registered protocol family 2
[ 16.299972] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 16.300210] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 16.300280] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
[ 16.300347] TCP: Hash tables configured (established 16384 bind 16384)
[ 16.300349] TCP reno registered
[ 16.311997] checking if image is initramfs... it is
[ 16.722851] Switched to high resolution mode on CPU 0
[ 16.955865] Freeing initrd memory: 7690k freed
[ 16.956029] Simple Boot Flag value 0x87 read from CMOS RAM was invalid
[ 16.956031] Simple Boot Flag at 0x7a set to 0x1
[ 16.956458] audit: initializing netlink socket (disabled)
[ 16.956474] audit(1208033003.460:1): initialized
[ 16.958659] VFS: Disk quotas dquot_6.5.1
[ 16.958745] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 16.958...

[thom (tsk)]

Hi Bozza,

AFAIK Your blacklisting was not done properly, see the first two lines where the driver *did* load, followed by a null pointer assignment in line 3 and a kernel oops in line 6.

[ 38.650559] saa7134 ALSA driver for DMA sound loaded
[ 38.650593] saa7134[0]/alsa: saa7134[0] at 0xfbffa400 irq 21 registered as card -2
[ 38.650682] BUG: unable to handle kernel NULL pointer dereference at virtual address 00000001
[ 38.650687] printing eip: e0de4745 *pde = 00000000
[ 38.650692] Oops: 0000 [#1] SMP
[ 38.650695] Modules linked in: saa7134_alsa

Nevermind that now....because there is a FIX!!...a real one!!!....so forget about blacklisting and start enjoying TV without HAL errors :-D

I installed linux-ubuntu-modules-2.6.24-16-generic_2.6.24-16.23ubuntu2, from http://ppa.launchpad.net/stefan-bader-canonical/ubuntu/ and it works. For the first time in hardy perfect recognition of the audio part and have xaw-tv running.
You can also wait until it is officially in the updates

more info on:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/212960