Date: Wed, 6 Jun 2012 21:29:06 +0200 (CEST) From: Oliver Fromme <olli@lurza.secnetix.de> To: freebsd-stable@FreeBSD.ORG Subject: 9-stabe: cd device gone, ATA_CAM panics Message-ID: <201206061929.q56JT6Be027916@lurza.secnetix.de>
next in thread | raw e-mail | index | archive | help
Hi, I recently updated an amd64 machine from 8-stable to 9-stable, csupped on June 1st: $ uname -rsm FreeBSD 9.0-STABLE-20120601 amd64 When I merged my old kernel configuration, at first I kept "device atapicam" because this is still mentioned in NOTES. Config and compiling worked, but linking failed with missing symbols. I don't remember which symbols, but it's easy to reproduce if necessary. Anyway, I commented atapicam out because it seems that now "options ATA_CAM" does the same thing. This time the kernel linked, but during boot I got the following panic: atapci0: <Promise PDC20269 UDMA133 controller> port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xcc00-0xcc03,0xc880-0xc88f mem 0xfeaf8000-0xfeafbfff irq 21 at device 6.0 on pci3 ata2: <ATA channel> at channel 0 on atapci0 ata3: <ATA channel> at channel 1 on atapci0 [...] ata2: reset tp1 mask=03 ostat0=50 ostat1=00 ata2: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata2: stat1=0x00 err=0x04 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=00 stat1=00 devices=0x10000 (cd0:ata2:0:0:0): AutoSense failed (cd0:ata2:0:0:0): Error 5, Unretryable error (cd0:ata2:0:0:0): got CAM status 0x50 (cd0:ata2:0:0:0): fatal error, failed to attach to device (cd0:ata2:0:0:0): lost device ata2: reset tp1 mask=03 ostat0=50 ostat1=00 ata2: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata2: stat1=0x00 err=0x04 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=00 stat1=00 devices=0x10000 (cd0:ata2:0:0:0): AutoSense failed (cd0:ata2:0:0:0): Error 5, Unretryable error (cd0:ata2:0:0:0): removing device entry panic: cam_periph_release_locked_buses: release of 0xfffffe0007321700 when refcount is zero cpuid = 4 KDB: stack backtrace: #0 0xffffffff807a3c96 at kdb_backtrace+0x66 #1 0xffffffff8076d74e at panic+0x1ce #2 0xffffffff802a200e at cam_periph_release_locked_buses+0x3e #3 0xffffffff802a202e at cam_periph_release_locked+0x1e #4 0xffffffff802a2f52 at cam_periph_release+0x52 #5 0xffffffff802babcd at cdclose+0xbd #6 0xffffffff806d7332 at g_disk_access+0x242 #7 0xffffffff806db618 at g_access+0x188 #8 0xffffffff807110f8 at g_raid_md_taste_sii+0x188 #9 0xffffffff806e96d6 at g_raid_taste+0x126 #10 0xffffffff806db0cd at g_new_provider_event+0x6d #11 0xffffffff806d8c08 at g_run_events+0x1e8 #12 0xffffffff8073f00e at fork_exit+0x11e #13 0xffffffff809a2d4e at fork_trampoline+0xe Uptime: 48s Automatic reboot in 15 seconds - press any key on the console to abort Then I commented ATA_CAM out, too. This time there's no panic, and everything works fine, *except* that there are no cd devices whatsoever. $ ls /dev | grep cd $ There's no mention of any cd device in /var/run/dmesg.boot. Also, various invocations of atacontrol(8) don't change anything. "atacontrol list" claims there are no devices present. This is a Promise (P)ATA controller (UDMA-133) with a DVD-ROM/R/RW drive connected as master device to the first channel (ata2), nothing else. It worked fine with 8-stable. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Python is an experiment in how much freedom programmers need. Too much freedom and nobody can read another's code; too little and expressiveness is endangered." -- Guido van Rossum
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201206061929.q56JT6Be027916>