Date: Tue, 25 Jul 1995 09:21:15 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: hackers@freebsd.org Subject: Ultrastor unhappiness/crashing Message-ID: <199507242351.JAA01116@genesis.atrad.adelaide.edu.au>
next in thread | raw e-mail | index | archive | help
Hiho peoples; this is a quick runpast for comments before spending gobs of time digging deeper. The relevant bits : Jul 25 00:23:58 borax /kernel: uha0: reading board settings, dma=5 int=11 id=7 Jul 25 00:23:58 borax /kernel: uha0 at 0x330-0x33f irq 11 drq 5 on isa Jul 25 00:23:58 borax /kernel: (uha0:0:0): "SEAGATE ST11200N 9300" type 0 fixed SCSI 2 Jul 25 00:23:58 borax /kernel: sd0(uha0:0:0): Direct-Access 1005MB (2059140 512 byte sectors) Jul 25 00:23:58 borax /kernel: (uha0:1:0): "MICROP 4110-09TBCU0322L HT01" type 0 fixed SCSI 2 Jul 25 00:23:58 borax /kernel: sd1(uha0:1:0): Direct-Access 1002MB (2053880 512 byte sectors) Jul 25 00:23:58 borax /kernel: (uha0:4:0): "TANDBERG TDC 3600 =08:" type 1 remo vable SCSI 2 Jul 25 00:23:58 borax /kernel: st0(uha0:4:0): Sequential-Access st0: Tandberg td c3600 is a known rogue Jul 25 00:23:59 borax /kernel: density code 0x0, drive empty Jul 25 00:23:59 borax /kernel: (uha0:6:0): "MATSHITA CD-ROM CR-503 1.0f" type 5 removable SCSI 2 Jul 25 00:23:59 borax /kernel: cd0(uha0:6:0): CD-ROM cd present.[1057708 x 512 b yte records] Jul 25 00:03:59 borax /kernel: sd0(uha0:0:0): host adapter code inconsistency Jul 25 00:03:59 borax /kernel: cd0(uha0:6:0): host adapter code inconsistency Jul 25 00:04:00 borax /kernel: cd0(uha0:6:0): host adapter code inconsistency Jul 25 00:23:54 borax /kernel: cd0(uha0:6:0): UNIT ATTENTION asc:29,0 Jul 25 00:23:54 borax /kernel: cd0(uha0:6:0): Power on, reset, or bus device re set occurred Jul 25 00:23:54 borax /kernel: panic: free: multiple frees Jul 25 00:23:54 borax /kernel: Jul 25 00:23:54 borax /kernel: syncing disks... 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 giving up There are lots of the code inconsistency messages (maybe 20 or so, for both sd0 and cd0), and the system does the auto-reboot thing. The same hardware was running 2.0R without any problems. The message appears to be generated when the driver returns XS_DRIVER_STUFFUP /* driver failed to perform operation */ which is a bit ominous 8) Looking through isa/ultra14.c, there aren't a great number of these returns without additional printfs; I don't have GOTTABEJOKING defined, so its possible that uha_get_mscp() is failing. I'm late for work, so I can't chase this further just now, but anything that anyone has to contribute would be useful. This is the first time I've had this crash, although the inconsistency messages have been piling up ever since 2.0.5 (one of the last ALPHAS) was installed. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507242351.JAA01116>