Bug 226903 - 2.6.19-1.2895.fc6 crashes on boot with intel audio chipsets
2.6.19-1.2895.fc6 crashes on boot with intel audio chipsets
Status: CLOSED DUPLICATE of bug 225046
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2007-02-01 17:31 EST by Aurelien Bompard
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-11 13:59:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Picture of the backtrace (1.38 MB, image/png)
2007-02-01 17:31 EST, Aurelien Bompard
no flags Details

  None (edit)
Description Aurelien Bompard 2007-02-01 17:31:21 EST
Description of problem:
After upgrading to the 2.6.19-1.2895, my Lenovo 3000 C200 won't boot. The boot
hangs while initializing Udev and I get a kernel backtrace.
2.6.18-1.2869 boots, I have sound only with a headset at a very low volume, but
that's another problem.

Since I have no idea how to save this backtrace, I've just used my digital
camera, the picture is attached (3 pictures, grouped together in a single file)

It seems to come from snd_hda_codec.

Version-Release number of selected component (if applicable):
2.6.19-1.2895.fc6, all updates as of 2006-02-01.

How reproducible:

Steps to Reproduce:
1. Upgrade to 2.6. on this hardware
2. Reboot.
Comment 1 Aurelien Bompard 2007-02-01 17:31:22 EST
Created attachment 147162 [details]
Picture of the backtrace
Comment 2 Aurelien Bompard 2007-02-02 02:19:40 EST
I forgot : this is the relevant lspci line:
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller (rev 02)
Comment 3 Chuck Ebbert 2007-02-11 13:59:24 EST

*** This bug has been marked as a duplicate of 225046 ***

Note You need to log in before you can comment on or make changes to this bug.