Hi all,
The '(CTRL-C to abort)' which gets printed while dumping is irritating me
because EC2's console has a very limited buffer and having this spammed
makes it impossible to see any printfs immediately prior. (Turning off
dumping solves the problem, but creates a worse problem, namely a lack
As my old PATA hard disk was failing, I had to replace it with a new SATA
drive where I moved my FreeBSDs installations, as PATA drives are not easy
to
find these days.
So I had to move one of my data drive from a VIA8237A SATA controller to the
last free SATA slot on a Marvell 88SX6121 to
Hi there.
Everything was fine with kernel dated 14.12, but now it's impossible to
run smartd without panic. Smartmontools rebuilded with this release
still produces panic. Everything else seems working fine.
core.txt is here:
http://pastebin.com/grcw6dqG
--
Bartosz Stec
Hi there.
Everything was fine with kernel dated 14.12, but now it's impossible to
run smartd without panic. Smartmontools rebuilded with this relaese
still produes panic. Everything else seems working fine.
core.txt and info.0 attached.
--
Bartosz Stec
dump.tar.bz2
Description: Binary
On Tue, Dec 28, 2010 at 1:33 PM, Bartosz Stec bartosz.s...@it4pro.plwrote:
Hi there.
Everything was fine with kernel dated 14.12, but now it's impossible to run
smartd without panic. Smartmontools rebuilded with this release still
produces panic. Everything else seems working fine.
core.txt
Hi all,
On 12/28/10 07:37, Colin Percival wrote:
The '(CTRL-C to abort)' which gets printed while dumping is irritating me
because EC2's console has a very limited buffer and having this spammed
makes it impossible to see any printfs immediately prior.
Never mind, I've had pointed out to me
