Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 448921

Summary: "Kernel panic" at first boot on a Dell Latitude D430
Product: Red Hat Enterprise Linux 5 Reporter: Magnus Morén <magnus.moren>
Component: kernelAssignee: John Feeney <jfeeney>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: urgent Docs Contact:
Priority: low    
Version: 5.2CC: dzickus, jkysela
Target Milestone: rc   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-03 16:30:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Photo of console
none
Output of lspci -v
none
Output of cat /proc/asound/card0/codec#0 none

Description Magnus Morén 2008-05-29 14:28:29 UTC
Description of problem:

Newly installed RHEL 5.2 Desktop gives "Kernel panic" at first boot on a Dell
Latitude D430. The text "Starting udev" is displayed and then "Kernel panic".


Version-Release number of selected component (if applicable):

RHEL Desktop 5.2, kernel-2.6.18-92.el5.i686


How reproducible:

Always


Steps to Reproduce:
1. Install RHEL 5.2 Desktop on Dell Latitude D430
2. Reboot
3.
  
Actual results:

"Kernel Panic"

EIP is at snd_hda_input_mux_info+0x2a/0x36 [snd_hda_codec]
[STUFF DELETED]


Expected results:

A booting system.


Additional info:

Intel® CoreT 2 Duo

Comment 1 Prarit Bhargava 2008-06-02 12:45:28 UTC
Hi Magnus, could you please attach the entire boot log (including the panic)?

Thanks,

P.

Comment 2 Magnus Morén 2008-06-02 14:14:11 UTC
The system panics right after the "Starting udev" and then I have the panic text
on the console. I do not think there are any boot.log this early in the boot
process. Right?

Is there any other way I can get more information to help you solve this issue?
I can supply you with a screen shot (camera) if the console if this can help.


I have found a BIOS setting that make the system boot. Not obvious to find...

BIOS: D430, 05/16/2008, A07

Onboard Devices -> Microphone (enable or disable the internal/external microphone)

Microphone:
  Off => Kernel Panic
  Enabeled => System start ok

Magnus Morén


Comment 3 Prarit Bhargava 2008-06-02 14:18:24 UTC
Hi Magnus,

Then can you include the full panic output?

Thanks,

P.

Comment 4 Magnus Morén 2008-06-02 15:13:40 UTC
Created attachment 307377 [details]
Photo of console

Not a good photo, but it is readable.

Comment 5 John Feeney 2008-06-02 17:03:55 UTC
Magnus,
I was wondering if you could supply the output from lspci -v, as well as 
"cat"ting /proc/asound/card0/codec#0? 
 Thanks.
   John


Comment 6 Magnus Morén 2008-06-02 17:26:28 UTC
Created attachment 307538 [details]
Output of lspci -v

Comment 7 Magnus Morén 2008-06-02 17:27:14 UTC
Created attachment 307539 [details]
Output of cat /proc/asound/card0/codec#0

Comment 8 Magnus Morén 2008-06-02 17:29:00 UTC
Comment on attachment 307539 [details]
Output of cat /proc/asound/card0/codec#0

Please find the requested output.

Magnus Morén

Comment 9 Jaroslav Kysela 2008-06-12 14:07:18 UTC
Could you try to set module parameter for snd-hda-intel 'model=dell-m43' or
'model=dell-m44' and try again if it fixes kernel panic?

Comment 10 Magnus Morén 2008-06-16 11:38:01 UTC
(In reply to comment #9)
> Could you try to set module parameter for snd-hda-intel 'model=dell-m43' or
> 'model=dell-m44' and try again if it fixes kernel panic?

Sure, but I will need some assistance.

My /etc/modprobe.conf looks like this:
 alias ipv6 off
 alias net_pf-10 off
 alias eth0 tg3
 alias scsi_hostadapter ata_piix
 alias scsi_hostadapter1 usb-storage
 alias snd-card-0 snd-hda-intel
 options snd-hda-intel
 options snd-card-0 index=0
 options snd-hda-intel index=0
 #options snd-hda-intel model=dell-m43
 #options snd-hda-intel model=dell-m44
 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; \
  /sbin/modprobe -r --ignore-remove snd-hda-intel
 alias wmaster0 iwl4965

Is the syntax OK to set the test options? Is the order important in this file?
(obviously I will remove the comment when I test).


Comment 11 Jaroslav Kysela 2008-06-16 11:46:22 UTC
I think, all options should be on one line:

options snd-hda-intel index=0 model=dell-m43

Then reboot machine after change.


Comment 12 Magnus Morén 2008-06-18 22:29:12 UTC
(In reply to comment #11)
> options snd-hda-intel index=0 model=dell-m43
> 
> Then reboot machine after change.

I have now tried with both "dell-m43" and "dell-m44" and the result is the same,
ie "kernel panic".

My /etc/modprobe.conf

alias eth0 tg3
alias scsi_hostadapter ata_piix
alias scsi_hostadapter1 usb-storage
alias snd-card-0 snd-hda-intel
options snd-hda-intel index=0 model=dell-m44
options snd-card-0 index=0
remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin
/modprobe -r --ignore-remove snd-hda-intel
alias wmaster0 iwl4965


Comment 13 Jaroslav Kysela 2009-03-23 14:36:00 UTC
Please, try new HDA update test kernels from bug#483594 .

Comment 14 Magnus Morén 2009-04-03 14:36:26 UTC
(In reply to comment #13)
> Please, try new HDA update test kernels from bug#483594 .  

Right now this is not an easy test to do as I have switched to CentOS on my laptop since I submitted this bug. Sorry...

On the other hand I can report that the problem is *not* present in my current setup and this is:

# cat /etc/redhat-release
CentOS release 5.3 (Final)

# uname -a
Linux strider 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:19:18 EDT 2009 i686 i686 i386 GNU/Linux

Probably this is relevant to RHEL 5.3 also as of the close relationship between RHEL and CentOS. Right?

Comment 15 Jaroslav Kysela 2009-04-03 16:30:07 UTC
The fix cannot be verified from the reporter on RHEL 5.3 kernels.