Prev: media: dvb/af9015, factor out remote setting
Next: [Patch] Orion: Add Buffalo Linkstation LS-HGL support
From: Takashi Iwai on 26 Jan 2010 01:50
At Tue, 26 Jan 2010 00:59:15 +0000,
Sid Boyce wrote:
>
> On 25/01/10 21:55, Takashi Iwai wrote:
> > At Mon, 25 Jan 2010 22:54:23 +0100,
> > I wrote:
> >>
> >> At Mon, 25 Jan 2010 22:39:02 +0100,
> >> Rafael J. Wysocki wrote:
> >>>
> >>> On Monday 25 January 2010, Sid Boyce wrote:
> >>>> On 15/01/10 01:24, Sid Boyce wrote:
> >>>> This is the only outstanding bug. No problems up 2.6.32-git1, but I get
> >>>> a solid lock-up on 2.6.32-git2 through 2.6.33-rc5 if the on-board audio
> >>>> is not disabled in the BIOS.
> >>>
> >>> I guess we should let Takashi know.
> >>
> >> Thanks.
> >>
> >>>>> tindog:~ # uname -r
> >>>>> 2.6.33-rc4-smp
> >>>>> On 2.6.32-git1 which boots, hwinfo shows:-
> >>>>> oss.card_id = 'HDA NVidia'
> >>>>> oss.card_id = 'HDA NVidia'
> >>>>> oss.card_id = 'HDA NVidia'
> >>>>> alsa.card_id = 'HDA NVidia'
> >>>>> alsa.card_id = 'HDA NVidia'
> >>>>> alsa.card_id = 'HDA NVidia'
> >>>>> alsa.card_id = 'HDA NVidia'
> >>>>> info.product = 'HDA NVidia ALSA hardware specific Device'
> >>>>> alsa.card_id = 'HDA NVidia'
> >>>>> info.product = 'HDA NVidia ALSA Control Device'
> >>>>> alsa.card_id = 'HDA NVidia'
> >>>>> info.product = 'HDA NVidia Sound Card'
> >>>>> sound.card_id = 'HDA NVidia'
> >>>>> info.linux.driver = 'HDA Intel'
> >>>>> 22: 489835 578 IO-APIC-fasteoi sata_nv, HDA Intel
> >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> >>>>> HDA Intel: module = snd_hda_intel
> >>>>> irq:0 22 ( 490413) "sata_nv" "HDA Intel"
> >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> >>>>> HDA Intel: module = snd_hda_intel
> >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> >>>>> HDA Intel: module = snd_hda_intel
> >>>>> E: DRIVER=HDA Intel
> >>>>> <6>HDA Intel 0000:00:0e.1: PCI INT B -> Link[AAZA] -> GSI 22 (level,
> >>>>> low) -> IRQ 22
> >>>>> <7>HDA Intel 0000:00:0e.1: setting latency timer to 64
> >>>>> Driver: "HDA Intel"
> >>
> >> What I'd try first is to pass enable_msi=0 option.
> >
> > Just to be sure -- it's an option for snd-hda-intel module.
> >
> >
> > Takashi
> >
>
> I passed "modprobe snd-hda-intel enable_msi=0" on the kernel command
> line, still locks up as before.

OK, are you sure that the lock-up happens at snd-hda-intel module?
How about blacklist it once?


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Takashi Iwai on 26 Jan 2010 02:00
At Tue, 26 Jan 2010 07:40:03 +0100,
I wrote:
>
> At Tue, 26 Jan 2010 00:59:15 +0000,
> Sid Boyce wrote:
> >
> > On 25/01/10 21:55, Takashi Iwai wrote:
> > > At Mon, 25 Jan 2010 22:54:23 +0100,
> > > I wrote:
> > >>
> > >> At Mon, 25 Jan 2010 22:39:02 +0100,
> > >> Rafael J. Wysocki wrote:
> > >>>
> > >>> On Monday 25 January 2010, Sid Boyce wrote:
> > >>>> On 15/01/10 01:24, Sid Boyce wrote:
> > >>>> This is the only outstanding bug. No problems up 2.6.32-git1, but I get
> > >>>> a solid lock-up on 2.6.32-git2 through 2.6.33-rc5 if the on-board audio
> > >>>> is not disabled in the BIOS.
> > >>>
> > >>> I guess we should let Takashi know.
> > >>
> > >> Thanks.
> > >>
> > >>>>> tindog:~ # uname -r
> > >>>>> 2.6.33-rc4-smp
> > >>>>> On 2.6.32-git1 which boots, hwinfo shows:-
> > >>>>> oss.card_id = 'HDA NVidia'
> > >>>>> oss.card_id = 'HDA NVidia'
> > >>>>> oss.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> info.product = 'HDA NVidia ALSA hardware specific Device'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> info.product = 'HDA NVidia ALSA Control Device'
> > >>>>> alsa.card_id = 'HDA NVidia'
> > >>>>> info.product = 'HDA NVidia Sound Card'
> > >>>>> sound.card_id = 'HDA NVidia'
> > >>>>> info.linux.driver = 'HDA Intel'
> > >>>>> 22: 489835 578 IO-APIC-fasteoi sata_nv, HDA Intel
> > >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> > >>>>> HDA Intel: module = snd_hda_intel
> > >>>>> irq:0 22 ( 490413) "sata_nv" "HDA Intel"
> > >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> > >>>>> HDA Intel: module = snd_hda_intel
> > >>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> > >>>>> HDA Intel: module = snd_hda_intel
> > >>>>> E: DRIVER=HDA Intel
> > >>>>> <6>HDA Intel 0000:00:0e.1: PCI INT B -> Link[AAZA] -> GSI 22 (level,
> > >>>>> low) -> IRQ 22
> > >>>>> <7>HDA Intel 0000:00:0e.1: setting latency timer to 64
> > >>>>> Driver: "HDA Intel"
> > >>
> > >> What I'd try first is to pass enable_msi=0 option.
> > >
> > > Just to be sure -- it's an option for snd-hda-intel module.
> > >
> > >
> > > Takashi
> > >
> >
> > I passed "modprobe snd-hda-intel enable_msi=0" on the kernel command
> > line,

Oh, I overlooked this text. Of course, this can't work :)

"modprobe..." isn't for the kernel command line but for modprobe
configs, usually specified in /etc/modprobe.d/* file.

And... is this report for 2.6.32 or for 2.6.33?
If it's with 2.6.32, enable_msi=1 may help instead.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Sid Boyce on 26 Jan 2010 07:10
On 26/01/10 06:58, Takashi Iwai wrote:
> At Tue, 26 Jan 2010 07:40:03 +0100,
> I wrote:
>>
>> At Tue, 26 Jan 2010 00:59:15 +0000,
>> Sid Boyce wrote:
>>>
>>> On 25/01/10 21:55, Takashi Iwai wrote:
>>>> At Mon, 25 Jan 2010 22:54:23 +0100,
>>>> I wrote:
>>>>>
>>>>> At Mon, 25 Jan 2010 22:39:02 +0100,
>>>>> Rafael J. Wysocki wrote:
>>>>>>
>>>>>> On Monday 25 January 2010, Sid Boyce wrote:
>>>>>>> On 15/01/10 01:24, Sid Boyce wrote:
>>>>>>> This is the only outstanding bug. No problems up 2.6.32-git1, but I get
>>>>>>> a solid lock-up on 2.6.32-git2 through 2.6.33-rc5 if the on-board audio
>>>>>>> is not disabled in the BIOS.
>>>>>>
>>>>>> I guess we should let Takashi know.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>>>> tindog:~ # uname -r
>>>>>>>> 2.6.33-rc4-smp
>>>>>>>> On 2.6.32-git1 which boots, hwinfo shows:-
>>>>>>>> oss.card_id = 'HDA NVidia'
>>>>>>>> oss.card_id = 'HDA NVidia'
>>>>>>>> oss.card_id = 'HDA NVidia'
>>>>>>>> alsa.card_id = 'HDA NVidia'
>>>>>>>> alsa.card_id = 'HDA NVidia'
>>>>>>>> alsa.card_id = 'HDA NVidia'
>>>>>>>> alsa.card_id = 'HDA NVidia'
>>>>>>>> info.product = 'HDA NVidia ALSA hardware specific Device'
>>>>>>>> alsa.card_id = 'HDA NVidia'
>>>>>>>> info.product = 'HDA NVidia ALSA Control Device'
>>>>>>>> alsa.card_id = 'HDA NVidia'
>>>>>>>> info.product = 'HDA NVidia Sound Card'
>>>>>>>> sound.card_id = 'HDA NVidia'
>>>>>>>> info.linux.driver = 'HDA Intel'
>>>>>>>> 22: 489835 578 IO-APIC-fasteoi sata_nv, HDA Intel
>>>>>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
>>>>>>>> HDA Intel: module = snd_hda_intel
>>>>>>>> irq:0 22 ( 490413) "sata_nv" "HDA Intel"
>>>>>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
>>>>>>>> HDA Intel: module = snd_hda_intel
>>>>>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
>>>>>>>> HDA Intel: module = snd_hda_intel
>>>>>>>> E: DRIVER=HDA Intel
>>>>>>>> <6>HDA Intel 0000:00:0e.1: PCI INT B -> Link[AAZA] -> GSI 22 (level,
>>>>>>>> low) -> IRQ 22
>>>>>>>> <7>HDA Intel 0000:00:0e.1: setting latency timer to 64
>>>>>>>> Driver: "HDA Intel"
>>>>>
>>>>> What I'd try first is to pass enable_msi=0 option.
>>>>
>>>> Just to be sure -- it's an option for snd-hda-intel module.
>>>>
>>>>
>>>> Takashi
>>>>
>>>
>>> I passed "modprobe snd-hda-intel enable_msi=0" on the kernel command
>>> line,
>
> Oh, I overlooked this text. Of course, this can't work :)
>
> "modprobe..." isn't for the kernel command line but for modprobe
> configs, usually specified in /etc/modprobe.d/* file.
>
I had already tried that... it locks up at the same point also with
"enable_msi=1".
tindog:/etc/modprobe.d # less 50-sound.conf

options snd slots=snd-hda-intel,enable_msi=0
# mDsH.vLXC8EvZgR7:MCP55 High Definition Audio
alias snd-card-0 snd-hda-intel

> And... is this report for 2.6.32 or for 2.6.33?
> If it's with 2.6.32, enable_msi=1 may help instead.
>
>
The motherboard giving the problem is the Asus M2N32-SLI deluxe.
00:0e.1 Audio device: nVidia Corporation MCP55 High Definition Audio
(rev a2)

No such problem with the Asus CROSSHAIR II FORMULA motherboard which
also has the
00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S
High Definition Audio (rev a1)

For any kernel >2.6.32-git1 it hangs, i.e 2.6.32-git2 to 2.6.33-rc5.
Disabling the sound chip in the BIOS, they all boot.
tindog:/etc/modprobe.d # uname -r
2.6.32-git1-smp
tindog:/etc/modprobe.d # l /dev/dsp*
crw-rw-rw- 1 root audio 14, 3 Jan 26 11:46 /dev/dsp
crw-rw-rw- 1 root audio 14, 35 Jan 26 11:46 /dev/dsp2

> Takashi
>
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Takashi Iwai on 26 Jan 2010 08:00
At Tue, 26 Jan 2010 12:02:44 +0000,
Sid Boyce wrote:
>
> On 26/01/10 06:58, Takashi Iwai wrote:
> > At Tue, 26 Jan 2010 07:40:03 +0100,
> > I wrote:
> >>
> >> At Tue, 26 Jan 2010 00:59:15 +0000,
> >> Sid Boyce wrote:
> >>>
> >>> On 25/01/10 21:55, Takashi Iwai wrote:
> >>>> At Mon, 25 Jan 2010 22:54:23 +0100,
> >>>> I wrote:
> >>>>>
> >>>>> At Mon, 25 Jan 2010 22:39:02 +0100,
> >>>>> Rafael J. Wysocki wrote:
> >>>>>>
> >>>>>> On Monday 25 January 2010, Sid Boyce wrote:
> >>>>>>> On 15/01/10 01:24, Sid Boyce wrote:
> >>>>>>> This is the only outstanding bug. No problems up 2.6.32-git1, but I get
> >>>>>>> a solid lock-up on 2.6.32-git2 through 2.6.33-rc5 if the on-board audio
> >>>>>>> is not disabled in the BIOS.
> >>>>>>
> >>>>>> I guess we should let Takashi know.
> >>>>>
> >>>>> Thanks.
> >>>>>
> >>>>>>>> tindog:~ # uname -r
> >>>>>>>> 2.6.33-rc4-smp
> >>>>>>>> On 2.6.32-git1 which boots, hwinfo shows:-
> >>>>>>>> oss.card_id = 'HDA NVidia'
> >>>>>>>> oss.card_id = 'HDA NVidia'
> >>>>>>>> oss.card_id = 'HDA NVidia'
> >>>>>>>> alsa.card_id = 'HDA NVidia'
> >>>>>>>> alsa.card_id = 'HDA NVidia'
> >>>>>>>> alsa.card_id = 'HDA NVidia'
> >>>>>>>> alsa.card_id = 'HDA NVidia'
> >>>>>>>> info.product = 'HDA NVidia ALSA hardware specific Device'
> >>>>>>>> alsa.card_id = 'HDA NVidia'
> >>>>>>>> info.product = 'HDA NVidia ALSA Control Device'
> >>>>>>>> alsa.card_id = 'HDA NVidia'
> >>>>>>>> info.product = 'HDA NVidia Sound Card'
> >>>>>>>> sound.card_id = 'HDA NVidia'
> >>>>>>>> info.linux.driver = 'HDA Intel'
> >>>>>>>> 22: 489835 578 IO-APIC-fasteoi sata_nv, HDA Intel
> >>>>>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> >>>>>>>> HDA Intel: module = snd_hda_intel
> >>>>>>>> irq:0 22 ( 490413) "sata_nv" "HDA Intel"
> >>>>>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> >>>>>>>> HDA Intel: module = snd_hda_intel
> >>>>>>>> HDA Intel: /devices/pci0000:00/0000:00:0e.1
> >>>>>>>> HDA Intel: module = snd_hda_intel
> >>>>>>>> E: DRIVER=HDA Intel
> >>>>>>>> <6>HDA Intel 0000:00:0e.1: PCI INT B -> Link[AAZA] -> GSI 22 (level,
> >>>>>>>> low) -> IRQ 22
> >>>>>>>> <7>HDA Intel 0000:00:0e.1: setting latency timer to 64
> >>>>>>>> Driver: "HDA Intel"
> >>>>>
> >>>>> What I'd try first is to pass enable_msi=0 option.
> >>>>
> >>>> Just to be sure -- it's an option for snd-hda-intel module.
> >>>>
> >>>>
> >>>> Takashi
> >>>>
> >>>
> >>> I passed "modprobe snd-hda-intel enable_msi=0" on the kernel command
> >>> line,
> >
> > Oh, I overlooked this text. Of course, this can't work :)
> >
> > "modprobe..." isn't for the kernel command line but for modprobe
> > configs, usually specified in /etc/modprobe.d/* file.
> >
> I had already tried that... it locks up at the same point also with
> "enable_msi=1".
> tindog:/etc/modprobe.d # less 50-sound.conf
>
> options snd slots=snd-hda-intel,enable_msi=0

This is the option for module snd, not snd-hda-intel.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Rafael J. Wysocki on 26 Jan 2010 08:00
On Tuesday 26 January 2010, Sid Boyce wrote:
> On 26/01/10 06:58, Takashi Iwai wrote:
....
> > And... is this report for 2.6.32 or for 2.6.33?
> > If it's with 2.6.32, enable_msi=1 may help instead.
> >
> >
> The motherboard giving the problem is the Asus M2N32-SLI deluxe.
> 00:0e.1 Audio device: nVidia Corporation MCP55 High Definition Audio
> (rev a2)
>
> No such problem with the Asus CROSSHAIR II FORMULA motherboard which
> also has the
> 00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S
> High Definition Audio (rev a1)
>
> For any kernel >2.6.32-git1 it hangs, i.e 2.6.32-git2 to 2.6.33-rc5.
> Disabling the sound chip in the BIOS, they all boot.
> tindog:/etc/modprobe.d # uname -r
> 2.6.32-git1-smp
> tindog:/etc/modprobe.d # l /dev/dsp*
> crw-rw-rw- 1 root audio 14, 3 Jan 26 11:46 /dev/dsp
> crw-rw-rw- 1 root audio 14, 35 Jan 26 11:46 /dev/dsp2

Is your adapter build as a module or is it compiled directly into the kernel?

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: media: dvb/af9015, factor out remote setting
Next: [Patch] Orion: Add Buffalo Linkstation LS-HGL support