On Sat, Aug 21, 2010 at 07:20:18PM +0300, Andriy Gapon wrote:
> on 30/07/2010 17:36 Anton Shterenlikht said the following:
> > On Fri, Jul 30, 2010 at 04:31:44PM +0300, Andriy Gapon wrote:
> >> Just a one thing to try - can you please add hdac_reset(sc, 1) call in
> >> hdac_attach() right before hd
on 30/07/2010 17:36 Anton Shterenlikht said the following:
> On Fri, Jul 30, 2010 at 04:31:44PM +0300, Andriy Gapon wrote:
>> Just a one thing to try - can you please add hdac_reset(sc, 1) call in
>> hdac_attach() right before hdac_get_capabilities() call?
>> The idea is to reset the controller bef
On Tue, 27 Jul 2010, Anton Shterenlikht wrote:
> On Tue, Jul 27, 2010 at 05:53:25PM +0100, Gavin Atkinson wrote:
> > On Tue, 2010-07-27 at 15:47 +0100, Anton Shterenlikht wrote:
> > > db> bt
> > > Tracing pid 0 tid 10 td 0x80b40de0
> > > kdb_enter() at kdb_enter+0x3d
> > > panic() at p
On Fri, Jul 30, 2010 at 04:31:44PM +0300, Andriy Gapon wrote:
> on 30/07/2010 16:02 Anton Shterenlikht said the following:
> > % dmesg | fgrep -i hda
> > hdac0: irq 16 at device 20.2
> > on pci0
> > hdac0: HDA Driver Revision: 20100226_0142
> > hdac0: Lazy allocation of 0x4000 bytes rid 0x10 type
on 30/07/2010 16:02 Anton Shterenlikht said the following:
> % dmesg | fgrep -i hda
> hdac0: irq 16 at device 20.2 on
> pci0
> hdac0: HDA Driver Revision: 20100226_0142
> hdac0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0xb7fb
> hdac0: [MPSAFE]
> hdac0: [ITHREAD]
> hdac0: hdac_get_ca
On Fri, Jul 30, 2010 at 03:05:34PM +0300, Andriy Gapon wrote:
> on 30/07/2010 14:57 Anton Shterenlikht said the following:
> > On Wed, Jul 28, 2010 at 08:17:47PM +0300, Andriy Gapon wrote:
> >> Change it to if (1) { ...}.
> >
> > did that, and did a cold reboot:
> >
> > % dmesg | fgrep -i hda
> >
on 30/07/2010 14:57 Anton Shterenlikht said the following:
> On Wed, Jul 28, 2010 at 08:17:47PM +0300, Andriy Gapon wrote:
>> Change it to if (1) { ...}.
>
> did that, and did a cold reboot:
>
> % dmesg | fgrep -i hda
> hdac0: irq 16 at device 20.2 on
> pci0
> hdac0: HDA Driver Revision: 201002
On Wed, Jul 28, 2010 at 08:17:47PM +0300, Andriy Gapon wrote:
> on 28/07/2010 20:13 Anton Shterenlikht said the following:
> > On Wed, Jul 28, 2010 at 07:51:08PM +0300, Andriy Gapon wrote:
> >> on 28/07/2010 19:44 Anton Shterenlikht said the following:
> >> > But I just rebooted again, and reset
>
on 28/07/2010 20:13 Anton Shterenlikht said the following:
> On Wed, Jul 28, 2010 at 07:51:08PM +0300, Andriy Gapon wrote:
>> on 28/07/2010 19:44 Anton Shterenlikht said the following:
>> > But I just rebooted again, and reset
>>> to defaults in BIOS, now I get:
>>>
>>> % dmesg | fgrep -i hda
>>>
On Wed, Jul 28, 2010 at 07:51:08PM +0300, Andriy Gapon wrote:
> on 28/07/2010 19:44 Anton Shterenlikht said the following:
> > But I just rebooted again, and reset
> > to defaults in BIOS, now I get:
> >
> > % dmesg | fgrep -i hda
> > hdac0: irq 16 at device 20.2
> > on pci0
> > hdac0: HDA Driv
on 28/07/2010 19:59 Pyun YongHyeon said the following:
>
> When I started to write snd_audiocs(4) for sparc64 I also noticed
> that. The practice of sound driver was to explicitly allocate softc
> structure in device attach routine and release it after use. I
> don't remember details but other par
On Wed, Jul 28, 2010 at 04:14:10PM +0300, Andriy Gapon wrote:
> on 27/07/2010 19:53 Gavin Atkinson said the following:
> >
> > Thanks. Can you try
> > http://people.freebsd.org/~gavin/mexas-hda-panic.diff
> >
> > and see if that solves things for you?
> >
> > (Credit goes to avg@ for looking in
on 28/07/2010 19:44 Anton Shterenlikht said the following:
> But I just rebooted again, and reset
> to defaults in BIOS, now I get:
>
> % dmesg | fgrep -i hda
> hdac0: irq 16 at device 20.2 on
> pci0
> hdac0: HDA Driver Revision: 20100226_0142
> hdac0: [ITHREAD]
> hdac0: hdac_get_capabilities:
On Wed, Jul 28, 2010 at 07:33:44PM +0300, Andriy Gapon wrote:
> on 28/07/2010 19:17 Anton Shterenlikht said the following:
> > On Wed, Jul 28, 2010 at 07:07:34PM +0300, Andriy Gapon wrote:
> >> on 28/07/2010 19:01 Anton Shterenlikht said the following:
> >>> here it is:
> >> So did it work? :)
> >
on 28/07/2010 19:17 Anton Shterenlikht said the following:
> On Wed, Jul 28, 2010 at 07:07:34PM +0300, Andriy Gapon wrote:
>> on 28/07/2010 19:01 Anton Shterenlikht said the following:
>>> here it is:
>> So did it work? :)
>
> not as far as I can tell
>
>>> % dmesg|fgrep -i hda
>>> pci0: at devi
On Wed, Jul 28, 2010 at 07:07:34PM +0300, Andriy Gapon wrote:
> on 28/07/2010 19:01 Anton Shterenlikht said the following:
> > here it is:
>
> So did it work? :)
not as far as I can tell
>
> > % dmesg|fgrep -i hda
> > pci0: at device 20.2 (no driver attached)
> > pci0: at device 20.2 (no driv
on 28/07/2010 19:01 Anton Shterenlikht said the following:
> here it is:
So did it work? :)
> % dmesg|fgrep -i hda
> pci0: at device 20.2 (no driver attached)
> pci0: at device 20.2 (no driver attached)
> hdac0: irq 16 at device 20.2 on
> pci0
> hdac0: HDA Driver Revision: 20100226_0142
> hda
On Wed, Jul 28, 2010 at 03:56:34PM +0300, Andriy Gapon wrote:
> on 27/07/2010 20:20 Anton Shterenlikht said the following:
> > yes, thanks, the panic has gone away.
> > There still seems to be a problem with this device:
> >
> >
> > hd...@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x438310
On Wed, Jul 28, 2010 at 04:14:10PM +0300, Andriy Gapon wrote:
> on 27/07/2010 19:53 Gavin Atkinson said the following:
> >
> > Thanks. Can you try
> > http://people.freebsd.org/~gavin/mexas-hda-panic.diff
> >
> > and see if that solves things for you?
> >
> > (Credit goes to avg@ for looking in
on 27/07/2010 19:53 Gavin Atkinson said the following:
>
> Thanks. Can you try
> http://people.freebsd.org/~gavin/mexas-hda-panic.diff
>
> and see if that solves things for you?
>
> (Credit goes to avg@ for looking into this before me :)
BTW, it seems that there is an epidemic of "free(sc, M_D
on 27/07/2010 20:20 Anton Shterenlikht said the following:
> yes, thanks, the panic has gone away.
> There still seems to be a problem with this device:
>
>
> hd...@pci0:0:20:2:class=0x040300 card=0x30c2103c chip=0x43831002 rev=0x00
> hdr=0x00
> vendor = 'ATI Technologies Inc. / Adva
On 07/27/10 18:09, Anton Shterenlikht wrote:
> On Tue, Jul 27, 2010 at 05:37:49PM +1000, Lawrence Stewart wrote:
>> On 07/27/10 02:07, Anton Shterenlikht wrote:
>>> On Mon, Jul 26, 2010 at 02:24:52PM +0100, Anton Shterenlikht wrote:
On amd64 r210496 I get this panic when booting a kernel
On Tue, Jul 27, 2010 at 05:53:25PM +0100, Gavin Atkinson wrote:
> On Tue, 2010-07-27 at 15:47 +0100, Anton Shterenlikht wrote:
> > On Tue, Jul 27, 2010 at 02:52:17PM +0100, Gavin Atkinson wrote:
> > > On Tue, 2010-07-27 at 12:58 +0100, Anton Shterenlikht wrote:
> > > > On Tue, Jul 27, 2010 at 11:23
On Tue, 2010-07-27 at 15:47 +0100, Anton Shterenlikht wrote:
> On Tue, Jul 27, 2010 at 02:52:17PM +0100, Gavin Atkinson wrote:
> > On Tue, 2010-07-27 at 12:58 +0100, Anton Shterenlikht wrote:
> > > On Tue, Jul 27, 2010 at 11:23:24AM +0100, Gavin Atkinson wrote:
> > > > On Mon, 2010-07-26 at 14:24 +
On Tue, Jul 27, 2010 at 02:52:17PM +0100, Gavin Atkinson wrote:
> On Tue, 2010-07-27 at 12:58 +0100, Anton Shterenlikht wrote:
> > On Tue, Jul 27, 2010 at 11:23:24AM +0100, Gavin Atkinson wrote:
> > > On Mon, 2010-07-26 at 14:24 +0100, Anton Shterenlikht wrote:
> > > > On amd64 r210496 I get this p
On Tue, 2010-07-27 at 12:58 +0100, Anton Shterenlikht wrote:
> On Tue, Jul 27, 2010 at 11:23:24AM +0100, Gavin Atkinson wrote:
> > On Mon, 2010-07-26 at 14:24 +0100, Anton Shterenlikht wrote:
> > > On amd64 r210496 I get this panic when booting a kernel
> > > with snd_hda(4). I haven't used this dr
On Tue, Jul 27, 2010 at 11:23:24AM +0100, Gavin Atkinson wrote:
> On Mon, 2010-07-26 at 14:24 +0100, Anton Shterenlikht wrote:
> > On amd64 r210496 I get this panic when booting a kernel
> > with snd_hda(4). I haven't used this driver before, so
> > can't say if this is a regression.
> >
> > (copi
On Mon, 2010-07-26 at 14:24 +0100, Anton Shterenlikht wrote:
> On amd64 r210496 I get this panic when booting a kernel
> with snd_hda(4). I haven't used this driver before, so
> can't say if this is a regression.
>
> (copied by hand)
>
> hdac0: irq 16 at device 20.2 on
> pci0
> hdac0: HDA Drive
On Tue, Jul 27, 2010 at 05:37:49PM +1000, Lawrence Stewart wrote:
> On 07/27/10 02:07, Anton Shterenlikht wrote:
> > On Mon, Jul 26, 2010 at 02:24:52PM +0100, Anton Shterenlikht wrote:
> >> On amd64 r210496 I get this panic when booting a kernel
> >> with snd_hda(4). I haven't used this driver befo
On 07/27/10 02:07, Anton Shterenlikht wrote:
> On Mon, Jul 26, 2010 at 02:24:52PM +0100, Anton Shterenlikht wrote:
>> On amd64 r210496 I get this panic when booting a kernel
>> with snd_hda(4). I haven't used this driver before, so
>> can't say if this is a regression.
>>
>> (copied by hand)
>>
>>
On Mon, Jul 26, 2010 at 02:24:52PM +0100, Anton Shterenlikht wrote:
> On amd64 r210496 I get this panic when booting a kernel
> with snd_hda(4). I haven't used this driver before, so
> can't say if this is a regression.
>
> (copied by hand)
>
> hdac0: irq 16 at device 20.2 on
> pci0
> hdac0: HD
On amd64 r210496 I get this panic when booting a kernel
with snd_hda(4). I haven't used this driver before, so
can't say if this is a regression.
(copied by hand)
hdac0: irq 16 at device 20.2 on
pci0
hdac0: HDA Driver Revision: 20100226_0142
hdac0: [ITHREAD]
hdac0: hdac_get_capabilities: Invali
32 matches
Mail list logo
