From Feisal.O.Mohammed@uwi.tt  Fri Jul 21 06:59:25 2000
Return-Path: <Feisal.O.Mohammed@uwi.tt>
Received: from enggate.uwi.tt (enggate.uwi.tt [196.3.139.34])
	by hub.freebsd.org (Postfix) with SMTP id 2BED737B937
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 21 Jul 2000 06:59:19 -0700 (PDT)
	(envelope-from Feisal.O.Mohammed@uwi.tt)
Received: (qmail 12169 invoked by uid 0); 21 Jul 2000 13:56:23 -0000
Received: from ldc.eng.uwi.tt (192.168.20.31)
  by bsd.eng.uwi.tt with SMTP; 21 Jul 2000 13:56:23 -0000
Received: from feisalpc.eng.uwi.tt (router.eng.uwi.tt [192.168.20.195])
	by ldc.eng.uwi.tt (8.9.1/8.9.1) with SMTP id JAA02161
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 21 Jul 2000 09:52:10 +0400 (GMT)
Received: (qmail 596 invoked by uid 1001); 21 Jul 2000 13:59:07 -0000
Message-Id: <20000721135907.595.qmail@feisalpc.eng.uwi.tt>
Date: 21 Jul 2000 13:59:07 -0000
From: Feisal.O.Mohammed@uwi.tt
Reply-To: feisal@feisalpc.eng.uwi.tt
To: FreeBSD-gnats-submit@freebsd.org
Subject: Drive on Advansys controller not seen 
X-Send-Pr-Version: 3.2

>Number:         20085
>Category:       kern
>Synopsis:       Drive on Advansys controller not seen
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 21 07:00:01 PDT 2000
>Closed-Date:    Fri Jul 21 07:44:54 PDT 2000
>Last-Modified:  Fri Jul 21 07:50:01 PDT 2000
>Originator:     Feisal Mohammed
>Release:        FreeBSD 4.0-RELEASE i386
>Organization:
University of the West Indies
>Environment:
	Results of dmesg running 3.4 Release
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California. All rights reserved.
FreeBSD 3.4-RELEASE #2: Sat Jul 15 14:14:22 AST 2000
    root@feisalpc.eng.uwi.tt:/usr/src/sys/compile/NEW
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 120273419 Hz
CPU: Pentium/P54C (120.27-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x526  Stepping = 6
  Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory  = 67108864 (65536K bytes)
avail memory = 62951424 (61476K bytes)
Probing for devices on PCI bus 0:
chip0: <Intel 82439HX PCI cache memory controller> rev 0x03 on pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
vga0: <S3 ViRGE VX graphics accelerator> rev 0x02 int a irq 9 on pci0.10.0
xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x30 int a irq 9 on pci0.11.0
xl0: Ethernet address: 00:10:5a:0d:b8:1e
xl0: autoneg complete, link status good (half-duplex, 10Mbps)
adv0: <AdvanSys ASC3050 Ultra SCSI controller> rev 0x03 int a irq 12 on pci0.12.
0
adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 240
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 flags 0x10 on isa
sio1: type 16550A
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 not found at 0x1f0
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (wd2): <QUANTUM BIGFOOT2550A>
wd2: 2457MB (5033952 sectors), 4994 cyls, 16 heads, 63 S/T, 512 B/S
ppc0 at 0x378 irq 7 flags 0x40 on isa
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 10 on isa
ep0: utp/bnc[*BNC*] address 00:60:08:40:56:af
aic0 at 0x340-0x35f irq 11 on isa
aic0: aic6360, dma, disconnection, parity check
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
Intel Pentium detected, installing workaround for F00F bug
Waiting 15 seconds for SCSI devices to settle
(sa0:aic0:0:4:0): found quirk entry 4
sa0 at aic0 bus 0 target 4 lun 0
sa0: <HP T4000s 1.10> Removable Sequential Access SCSI-2 device 
sa0: 3.300MB/s transfers
cd0 at aic0 bus 0 target 3 lun 0
cd0: <PLEXTOR CD-ROM PX-12TS 1.01> Removable CD-ROM SCSI-2 device 
cd0: 5.000MB/s transfers (5.000MHz, offset 8)
cd0: cd present [1282356 x 512 byte records]
changing root device to da0s4a
da0 at adv0 bus 0 target 6 lun 0
da0: <IBM DNES-309170 SA30> Fixed Direct Access SCSI-3 device 
da0: 20.000MB/s transfers (20.000MHz, offset 15)
da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C)
changing root device to da0a

>Description:

	When booting with the install disks for 4.0 RELEASE, and
	selecting either upgrade or normal install the disk connected
	to the Advansys controller is not seen when the partition editor
	is entered.  The boot messages show the controller and disk being
	recognized but only the disk connected to the IDE controller
	is visible in the partion editor.


>How-To-Repeat:

	Redo install.
>Fix:
	
	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Fri Jul 21 07:44:54 PDT 2000 
State-Changed-Why:  
unrouteable mail domain "feisalpc.eng.uwi.tt" 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20085 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: feisal@feisalpc.eng.uwi.tt
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/20085: Drive on Advansys controller not seen 
Date: Fri, 21 Jul 2000 16:43:51 +0200

 On 21 Jul 2000 13:59:07 GMT, Feisal.O.Mohammed@uwi.tt wrote:
 
 > 	When booting with the install disks for 4.0 RELEASE, and
 > 	selecting either upgrade or normal install the disk connected
 > 	to the Advansys controller is not seen when the partition editor
 > 	is entered.  The boot messages show the controller and disk being
 > 	recognized but only the disk connected to the IDE controller
 > 	is visible in the partion editor.
 
 Is the dmesg(8) output which you sent from the 4.0-RELEASE kernel?  If
 not, please try to send _that_ rather.
 
 Did this happen in the FDISK partition editor or in the disk label
 screen?  The FDISK partition editor is applied to each disk in
 succession that you select from a check-box dialogue box.  Unless
 there's actually a serious problem with sysinstall, it sounds to me like
 you just forgot to select both drives from that check-box dialogue.
 
 Are you saying that the disk isn't available from the dialogue box.  If
 so, which drive wasn't available?  I assume da0?
 
 The disk label screen then allows you to label _all_ the disks that you
 selected earlier.  The disks available are listed at the top of the
 screen.  So if you'd gotten the selection right earlier, they'd both be
 visible in this window.  But what you see here is not as significant as
 what you see in that dialogue box.
 
 Could you provide feedback?  I'm not an expert in this area, but I have
 fallen into the trap of forgetting to select all the disks that I'm
 interested in from the fdisk selection dialogue check-box list.
 
 Ciao,
 Sheldon.
 
>Unformatted:
