From owner-freebsd-stable@FreeBSD.ORG Fri May 25 11:39:57 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 979E816A41F for ; Fri, 25 May 2007 11:39:57 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 168EA13C44B for ; Fri, 25 May 2007 11:39:56 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l4PBdqjf085371; Fri, 25 May 2007 08:39:52 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-stable@freebsd.org Date: Fri, 25 May 2007 08:38:56 -0300 User-Agent: KMail/1.9.6 References: <200705251021.l4PALOIa068649@lurza.secnetix.de> In-Reply-To: <200705251021.l4PALOIa068649@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200705250838.57254.joao@matik.com.br> X-Spam-Status: No, score=-100.5 required=5.0 tests=ALL_TRUSTED, AWL, MR_DIFF_MID, SMILEY,USER_IN_WHITELIST autolearn=unavailable version=3.1.8 X-Spam-Checker-Version: Antispam Datacenter Matik msrv.matik.com.br X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: Oliver Fromme Subject: Re: atapicam cd error from freebsd-stable Digest, Vol 207, Issue 6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 11:39:57 -0000 On Friday 25 May 2007 07:21:24 Oliver Fromme wrote: > > First, I don't think atapicam is an "exotic" driver. > I'm using it for several years (in fact, since it was an > inofficial patch, before it hit the repository). It's > working perfectly fine for me, including with today's > RELENG_6. > > Second, if you run a mission-critical mail cluster (or > similar things) and update it along RELENG_6 without > proper testing, then you deserve to be shot in the foot. thank you for your consideration (or as serious or even as stupid) but it = was=20 ment to be kind of sarcastic input (don't shoot me, gotcha ... ) and keep smiling! :) anyway, beside of this confusing dmesg error I can write a cd with cdrecord but my k3b still crashs with this pthread/libpthread advice and don't get i= t=20 right, I rebuild at night k3b with -R and finished fine but soon I put a cd= =20 into the drive k3b still crashes, it also crashes when a cd is in when=20 starting it seems that Andy and Robert can use k3b on amd64 on their systems somebody has an idea what might be wrong here on my computer (beside the=20 latter consideration of course)? =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br