Date: Sun, 24 Feb 2013 13:58:46 -0600 From: cpet <cpet@SDF.ORG> To: <freebsd-current@freebsd.org> Subject: Re: panic =?UTF-8?Q?bus=5Fdma?= Message-ID: <80b5ac01b7e7c6418c1b305501f6e3ed@SDF.ORG> In-Reply-To: <20130224060144.GG2454@kib.kiev.ua> References: <7ebe4b8082cbfa2b61936dc06de65a41@SDF.ORG> <20130224060144.GG2454@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-02-24 00:01, Konstantin Belousov wrote:
> On Sat, Feb 23, 2013 at 07:41:18PM -0600, cpet wrote:
>> Seems like my issue was imposed by commit 246713
>>
>> tested using 246712 boots
>> tested using 246713 panics
>>
>> keeping all the current debug stuff made the system keep going but
>> reset the 3ware
>> removing all the debug info made the system instantly panic with
>> latest
>> rev 247203
>>
>>
>> panic: _bus_dmama_load_ccb Unsupported Func Code 0 rev 246713
>>
>
> I am very sorry that I did not develop my mentiferous abilities far
> enough
> in time of your report arrival, so we unfortunately need to resort to
> some
> burdensome methods of properly reporting an issue.
>
> Specify the exact driver you use, preferrably demonstrating the
> fragment
> of the verbose dmesg related to the controller attachment.
>
> Show exact printout on the console at the time of panic. The grep of
> the kernel sources for 'Unsupported Func Code' finds nothing. This is
> probably panic("_bus_dmamap_load_ccb: Unsupported func code %d") in
> the _bus_dmamap_load_ccb().
>
> Show the backtrace from ddb and kgdb for the panic.
Hi I will get the bt later tonight as i had to remember how to do it :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80b5ac01b7e7c6418c1b305501f6e3ed>