Skip to contentSkip to conversation

2.6.32, hda_codec: kernel gets stuck for 3 minutes at boot time

DISCUSSION Harald Dunkel 3 participants 4 messages Dec 4, 2009 – Dec 5, 2009

lore
Share & tools
lore
#0 lore raw

Hi folks,

2.6.32(amd64) gets stuck for about 3 minutes at boot time. dmesg says:

:

[   15.026892] HDA Intel 0000:00:08.0: power state changed by ACPI to D0
[   15.041001] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[   15.054443] HDA Intel 0000:00:08.0: PCI INT A -> Link[LAZA] -> GSI 20 (level, low) -> IRQ 20
[   15.067718] HDA Intel 0000:00:08.0: setting latency timer to 64
[   15.424080] hda_codec: ALC662 rev1: BIOS auto-probing.
[  190.728138] Adding 1959920k swap on /dev/sda2.  Priority:-1 extents:1 across:1959920k
[  191.268572] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: [email protected]

:

I get the same for 2.6.31.6. I cannot remember having seen this for kernel 2.6.29.x.

Hardware is an Acer Aspire Revo R3600. A bios update to the most recent version did not help.

Any helpful comment or hint would be highly appreciated.

Regards

Harri

#1 lore raw
Quoted 28 lines · Harald Dunkel

Hi folks,

2.6.32(amd64) gets stuck for about 3 minutes at boot time. dmesg says:

:

[ 15.026892] HDA Intel 0000:00:08.0: power state changed by ACPI to D0
[ 15.041001] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[ 15.054443] HDA Intel 0000:00:08.0: PCI INT A -> Link[LAZA] -> GSI 20
(level, low) -> IRQ 20
[ 15.067718] HDA Intel 0000:00:08.0: setting latency timer to 64
[ 15.424080] hda_codec: ALC662 rev1: BIOS auto-probing.
[ 190.728138] Adding 1959920k swap on /dev/sda2. Priority:-1 extents:1
across:1959920k
[ 191.268572] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01)

initialised: [email protected]
:

I get the same for 2.6.31.6. I cannot remember having seen this for kernel 2.6.29.x.

Hardware is an Acer Aspire Revo R3600. A bios update to the most recent version did not help.

Any helpful comment or hint would be highly appreciated.

Quoted 9 lines

Regards

Harri
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

probably not the same situation as I was experiencing, but over here I was getting a pause during boot, long story short it ended up being write_net_rules in /lib/udev you might try looking in there to see. (but could be wrong).

Justin P. Mattock

#2 lore raw
In reply to Harald Dunkel

At Fri, 04 Dec 2009 17:59:11 +0100,

Quoted 4 lines · Harald Dunkel

Hi folks,

2.6.32(amd64) gets stuck for about 3 minutes at boot time.

3 minutes is definitely too long.
Could you double-check whether it's a hd-audio stuff, e.g. by simply removing snd-hda-intel module?

Takashi

Quoted 32 lines

dmesg says:

:

[   15.026892] HDA Intel 0000:00:08.0: power state changed by ACPI to D0
[   15.041001] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[   15.054443] HDA Intel 0000:00:08.0: PCI INT A -> Link[LAZA] -> GSI 20 (level, low) -> IRQ 20
[   15.067718] HDA Intel 0000:00:08.0: setting latency timer to 64
[   15.424080] hda_codec: ALC662 rev1: BIOS auto-probing.
[  190.728138] Adding 1959920k swap on /dev/sda2.  Priority:-1 extents:1 across:1959920k
[  191.268572] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: [email protected]

:

I get the same for 2.6.31.6. I cannot remember having seen this for kernel 2.6.29.x.

Hardware is an Acer Aspire Revo R3600. A bios update to the most recent version did not help.

Any helpful comment or hint would be highly appreciated.

Regards

Harri
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#3 lore raw
Quoted 5 lines · Takashi Iwai

3 minutes is definitely too long.
Could you double-check whether it's a hd-audio stuff, e.g. by simply removing snd-hda-intel module?

Seems that this was a problem with udev (http://bugs.debian.org/559264).
As you suspected the line about hda_codec was just the last message before the problem came up. With the new udev package the problem is gone.

Many thanx anyway

Harri