From owner-freebsd-current@FreeBSD.ORG Sun Oct 12 00:30:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9731C1065688 for ; Sun, 12 Oct 2008 00:30:20 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by mx1.freebsd.org (Postfix) with ESMTP id 6A77A8FC14 for ; Sun, 12 Oct 2008 00:30:20 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1161294wfg.7 for ; Sat, 11 Oct 2008 17:30:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=Qvba4pjuDfkLzaD5ISZ4kfVKmnJBj5LPQj1UJcAOML8=; b=JTnWhMSkEYMvhLcIQQMC1v1jSPxwJO9MryKmHKJjaFmttHmnDTPVrHrT6rMyUvdhkv hpD2Zxy9efTvU8y/ffjQpqtsmV+W9WjrYjROzPJ6izcVh0rlgWVElXBuQT651OcBBS7J OYyRwawD11LSxaHXN9RSKU6+ogw6hoHQVDGCo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=ALrbASqxe5Mv7xA/ZOY/3XxMDkfuFM9yXCdAUwtZn6sRUQzzPMIxI03Kav7rGgAA1y ZNjsRAoPKEfTIkUN2eeURHaA4hbk3hUhiaf5hdt6/F8PLZFB3bpV6zDLCNivkDqlnaMh g8dl4TI5tC41zItBzIvvPu7J70dz5KX2F1LdE= Received: by 10.142.156.2 with SMTP id d2mr1706235wfe.271.1223771419361; Sat, 11 Oct 2008 17:30:19 -0700 (PDT) Received: by 10.142.204.17 with HTTP; Sat, 11 Oct 2008 17:30:19 -0700 (PDT) Message-ID: <47d0403c0810111730p41bb17feva35729f31d0d2f44@mail.gmail.com> Date: Sat, 11 Oct 2008 20:30:19 -0400 From: "Ben Kaduk" To: "FreeBSD Current" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: delayed panic loading atapicam (after failed burncd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2008 00:30:20 -0000 Hi all, I'm setting up my new thinkpad T400, and though FreeBSD installed fine and runs pretty well, I find myself trying to burn an Ubuntu CD, in order to see if there really is a native driver that works for my Intel WiFi Link 5300 card. However, burncd has been giving me trouble, so I installed cdrtools, which requires atapicam to access the device. With a disc in the drive (that I think is blank due to a failed burncd attempt), loading atapicam does not immediately recognize my drive; it seems to be taking a while to probe it, as I get several messages of the form acd0: FAILURE - SETFEATURES SET TRANSFER MODE status=51 error=b4 acd0: FAILURE - REQUEST_SENSE timed out then a READ_CAPACITY timed out, and (da0:ata1:0:0:0): got CAM status 0xb (da0:ata1:0:0:0): fatal error, failed to attach to device (da0:ata1:0:0:0): lost device followed after a few seconds by panic: g_read_data(): invalid length -557797922 cpuid - 0 [...] Stopped at kdb_enter+0x3d: movq $0,0x639908(%rip) db> bt [pid;td] kdb_enter() panic() g_read_data() at g_read_data+0x4a g_bsd_try() at g_bsd_try+0x4e g_bst_taste() at g_bsd_taste+0x288 g_new_provider_event() at +0xa5 g_run_events() at +0x217 g_event_procbody() at +0x6c fork_exit() at +0x12a fork_trampoline() at _0xe (hand transcribed) Hm, and that's all I get, because going out of scroll lock causes it to spin printing "atapi_poll called!" Hm, trying again after a clean boot doesn't panic, but it doesn't find /dev/cd0 either. It also makes the eject button on my drive stop working. I guess I just need to load atapicam from loader.conf, then. This is from the September monthly snapshot, and it's still the GENERIC kernel. dmesg and pciconf at http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/prolix/ I've also seen a fair number of LORs on this machine, but I think that most of them are known and/or have been around for a long time but were exposed by recent lock type changes. A few of them are in the dmesg, above. Actually, I get this during bg_fsck(), and I'm not sure I've seen it before: vnode interlock at ffs_snapshot.c:2540 snaplk at ffs_snapshot.c:2550 KDB backtrace db_trace_self_wrapper _witness_debugger witness_checkorder __lockmgr_args ffs_snapdata_acquire ffs_snapshot ffs_mount vfs_donmount nmount syscall Xfast_syscall -Ben Kaduk