Andrew Morton schrieb: > Michael Thonke wrote: >> here again I have two problems. With 2.6.13-rc3-mm3 I have problems >> using my SATA drives on Intel ICH6. >> The kernel can't route there IRQs or can't discover them. the option >> irqpoll got them to work now. >> The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems. > > OK. Please generate the full dmesg output for -mm2 and for -mm3 and run > `diff -u dmesg.mm2 dmesg.mm3' and send it? And keep those files because we > may end up needing to add them to an acpi bugzilla entry ;) Well I did a little mistake..it only worked correctly up to 2.6.13-rc3-mm1 but this dmesg output I have. Well as I save mm[2,3] are unable to setup the correct IRQs for the devices..and please note that 2.6.13-rc3-mm3 only booted with irqpoll so its in the dmesg output "dmesg.mm3" Normaly the IRQ routed to something about 1xx now they are 1-21?! Caused by irqpoll? > >> The SATA drives are Samsung HD160JJ SATAII. The mainboard I use is a >> ASUS P4GPL-X. >> >> Second one is about Intel HD-Codec (snd-hda-intel) on modprobe when >> loading the module it gives me >> >> ---> snip >> hda_codec: Unknown model for ALC880, trying auto-probe from BIOS... > > Does -mm2 print that `unknown model' message? Yes and mm1 it's a wide problem as I found many posts on ALSA Forums But the big problem behind is...after it oops My Linux Raid (md) goes bad then..at reboot it gives me more oops and all changes on FS (reiser4) lost..and if I wouldn't use snd-hda-intel as modul the hole system hung at boot. > >> Unable to handle kernel NULL pointer dereference at virtual address 00000000 >> printing eip: >> f88713f4 >> *pde = 00000000 >> Oops: 0002 [#1] >> PREEMPT >> last sysfs file: >> Modules linked in: snd_hda_intel snd_hda_codec nvidia >> CPU: 0 >> EIP: 0060:[] Tainted: P VLI > > Please verify that it happens without the nvidia module loaded. > >> EFLAGS: 00010293 (2.6.13-rc3-mm3pm) >> eax: fffffffe ebx: f3b33548 ecx: 00000000 edx: 00000000 >> esi: f3b33400 edi: 00000000 ebp: 00000006 esp: f0371ddc >> ds: 007b es: 007b ss: 0068 >> Process modprobe (pid: 7398, threadinfo=f0370000 task=f4183560) >> Stack: 00000000 00000000 00000000 00000000 f3b33400 f3b33548 f0f1d000 >> f8871933 >> f3b33400 f0f1d000 f8871bbd f8875478 f88748f6 00000001 f886d77e >> 00000f00 >> 00000005 00000000 f0f1d000 f54d04c0 00000000 f886d984 00000f00 >> 00000002 >> Call Trace: >> [] >> [] > > Odd trace. Do you have CONFIG_KALLSYMS enabled? If not, please turn it on. Mh I tried but my system freezes on boot then. And screen leaves blank. > Thank you Andrew and the other for the great help up to here. Greets Best regards Michael