Date: Tue, 5 Feb 2013 01:06:51 -0500 From: Kurt Lidl <lidl@pix.net> To: Marius Strobl <marius@alchemy.franken.de> Cc: mav@freebsd.org, freebsd-sparc64@freebsd.org Subject: Re: smartmontools panics 9.1-RELEASE on sunfire 240 Message-ID: <20130205060651.GA40942@pix.net> In-Reply-To: <20130123221024.GP85306@alchemy.franken.de> References: <20130104051914.GA22613@pix.net> <20130104235336.GB37999@alchemy.franken.de> <20130105013224.GA31361@pix.net> <20130105015242.GB26039@alchemy.franken.de> <20130106021923.GE1410@funkthat.com> <20130106031245.GC26039@alchemy.franken.de> <20130107090200.GA53424@pix.net> <20130123221024.GP85306@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 23, 2013 at 11:10:24PM +0100, Marius Strobl wrote: > Could you please revert the patches to sys/cam/cam_periph.c and smartd.cpp > of smartmontools and try with the following kernel patch instead? > http://people.freebsd.org/~marius/ata_pio_odd_buf.diff OK - I was finally able to test this out. I completely reverted a machine (sunfire V120) to a stock 9.1-RELEASE kernel. I completely reverted the smartmontools. I double-checked that the combination of that kernel, and that binary still caused the problem. Check. Then I applied your patch to the kernel and tried the smartd program again. No panic. It appears your patch fixes the problem. Thanks! -Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130205060651.GA40942>