From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 8 10:43:56 2008 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01F6F1065746 for ; Sat, 8 Nov 2008 10:43:56 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3E21C8FC14 for ; Sat, 8 Nov 2008 10:43:55 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from p578b68b8.dip0.t-ipconnect.de ([87.139.104.184] helo=lt011.nfv) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1KylIH-0004xB-Da; Sat, 08 Nov 2008 11:43:54 +0100 Message-ID: <49156D65.7010807@gwdg.de> Date: Sat, 08 Nov 2008 11:43:49 +0100 From: Rainer Hurling User-Agent: Thunderbird 2.0.0.17 (X11/20081024) MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <200811080043.mA80hZls002194@www.freebsd.org> <49153DC7.1040201@gwdg.de> <20081108082434.GA7042@icarus.home.lan> <56E257FD-8D6F-4C77-8524-CC78D592825C@FreeBSD.ORG> In-Reply-To: <56E257FD-8D6F-4C77-8524-CC78D592825C@FreeBSD.ORG> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Jeremy Chadwick , freebsd-amd64@FreeBSD.ORG, Hans Subject: Re: amd64/128686: can't detect SATA Disk on 8.0-Current with NF550 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2008 10:43:56 -0000 Hello Søren, hello Jeremy, Søren Schmidt schrieb: > On 8Nov, 2008, at 9:24 , Jeremy Chadwick wrote: > >> Apologies for top-posting. > > Well, I dunno of any problems (yet), I'll dig out my only nVidia system > when time permits and see if anything shows up there.. > > -Søren > >> >> >> Soren, is this a known regression in CURRENT? (Possibly related to the >> modularisation of the ata(4) chipset pieces?) >> >> -- >> | Jeremy Chadwick jdc at parodius.com | >> | Parodius Networking http://www.parodius.com/ | >> | UNIX Systems Administrator Mountain View, CA, USA | >> | Making life hard for others since 1977. PGP: 4BD6C0CB | >> >> On Sat, Nov 08, 2008 at 08:20:39AM +0100, Rainer Hurling wrote: >>> Same here. >>> >>> With older kernel (april 2008) under amd64 (CURRENT) all disks are >>> found, with actual kernels not. So I am not able to boot any >>> more('Trying to mount root ...'). >>> >>> This error came in some weeks ago. I found no time to analyse and >>> report. With i386 mode on the same system there are no problems. >>> >>> >>> dmesg shows older nvidia chipset: >>> atapci0: port >>> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 4 >>> .0 on pci0 >>> ata0: on atapci0 >>> ata0: [ITHREAD] >>> ata1: on atapci0 >>> ata1: [ITHREAD] >>> atapci1: port >>> 0xc480-0xc487,0xc400-0xc403,0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc0f >>> mem 0xfbef9000-0xfbef9fff irq 23 at device 5.0 on pci0 >>> atapci1: [ITHREAD] >>> ata2: on atapci1 >>> ata2: [ITHREAD] >>> ata3: on atapci1 >>> ata3: [ITHREAD] >>> atapci2: port >>> 0xb880-0xb887,0xb800-0xb803,0xb480-0xb487,0xb400-0xb403,0xb080-0xb08f >>> mem 0xfbef8000-0xfbef8fff irq 20 at device 5.1 on pci0 >>> atapci2: [ITHREAD] >>> ata4: on atapci2 >>> ata4: [ITHREAD] >>> ata5: on atapci2 >>> ata5: [ITHREAD] >>> >>> >>> Tell me if I can help. >>> >>> Thank you, >>> Rainer >>> >>> >>> On 08.11.2008 01:43 (UTC+1), Hans wrote: >>>>> Number: 128686 >>>>> Category: amd64 >>>>> Synopsis: can't detect SATA Disk on 8.0-Current with NF550 >>>>> Confidential: no >>>>> Severity: critical >>>>> Priority: low >>>>> Responsible: freebsd-amd64 >>>>> State: open >>>>> Quarter: Keywords: Date-Required: >>>>> Class: sw-bug >>>>> Submitter-Id: current-users >>>>> Arrival-Date: Sat Nov 08 00:50:01 UTC 2008 >>>>> Closed-Date: >>>>> Last-Modified: >>>>> Originator: Hans >>>>> Release: 8.0-Current >>>>> Organization: >>>>> Environment: >>>>> Description: >>>> i had today update current kernel after reboot than failed detect disk >>>> but few month ago kernel not problem >>>> >>>> pciconv -l -v >>>> >>>> none0@pci0:0:0:0: class=0x050000 card=0xcb8410de chip=0x036910de >>>> rev=0xa1 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 Memory Controller' >>>> class = memory >>>> subclass = RAM >>>> isab0@pci0:0:1:0: class=0x060100 card=0xcb8410de chip=0x036010de >>>> rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 LPC Bridge' >>>> class = bridge >>>> subclass = PCI-ISA >>>> none1@pci0:0:1:1: class=0x0c0500 card=0xcb8410de chip=0x036810de >>>> rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 SMBus' >>>> class = serial bus >>>> subclass = SMBus >>>> ohci0@pci0:0:2:0: class=0x0c0310 card=0xcb8410de chip=0x036c10de >>>> rev=0xa1 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 USB Controller' >>>> class = serial bus >>>> subclass = USB >>>> ehci0@pci0:0:2:1: class=0x0c0320 card=0xcb8410de chip=0x036d10de >>>> rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 USB Controller' >>>> class = serial bus >>>> subclass = USB >>>> atapci0@pci0:0:4:0: class=0x01018a card=0xcb8410de >>>> chip=0x036e10de rev=0xa1 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 IDE' >>>> class = mass storage >>>> subclass = ATA >>>> atapci1@pci0:0:5:0: class=0x010185 card=0xcb8410de >>>> chip=0x037f10de rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 SATA Controller' >>>> class = mass storage >>>> subclass = ATA >>>> atapci2@pci0:0:5:1: class=0x010185 card=0xcb8410de >>>> chip=0x037f10de rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 SATA Controller' >>>> class = mass storage >>>> subclass = ATA >>>> atapci3@pci0:0:5:2: class=0x010185 card=0xcb8410de >>>> chip=0x037f10de rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 SATA Controller' >>>> class = mass storage >>>> subclass = ATA >>>> pcib1@pci0:0:6:0: class=0x060401 card=0xcb8410de chip=0x037010de >>>> rev=0xa2 hdr=0x01 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 PCI bridge' >>>> class = bridge >>>> subclass = PCI-PCI >>>> none2@pci0:0:6:1: class=0x040300 card=0x889116f3 chip=0x037110de >>>> rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'ADI 1988B 8 Channel High Definition Audio' >>>> class = multimedia >>>> subclass = HDA >>>> nfe0@pci0:0:8:0: class=0x068000 card=0xcb8410de chip=0x037310de >>>> rev=0xa2 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 Ethernet' >>>> class = bridge >>>> pcib2@pci0:0:10:0: class=0x060400 card=0x000010de chip=0x037610de >>>> rev=0xa2 hdr=0x01 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 PCIe bridge' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib3@pci0:0:11:0: class=0x060400 card=0x000010de chip=0x037410de >>>> rev=0xa2 hdr=0x01 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 PCIe bridge' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib4@pci0:0:12:0: class=0x060400 card=0x000010de chip=0x037410de >>>> rev=0xa2 hdr=0x01 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 PCIe bridge' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib5@pci0:0:13:0: class=0x060400 card=0x000010de chip=0x037810de >>>> rev=0xa2 hdr=0x01 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 PCIe bridge' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib6@pci0:0:14:0: class=0x060400 card=0x000010de chip=0x037510de >>>> rev=0xa2 hdr=0x01 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 PCIe bridge' >>>> class = bridge >>>> subclass = PCI-PCI >>>> pcib7@pci0:0:15:0: class=0x060400 card=0x000010de chip=0x037710de >>>> rev=0xa2 hdr=0x01 >>>> vendor = 'Nvidia Corp' >>>> device = 'MCP55 PCIe bridge' >>>> class = bridge >>>> subclass = PCI-PCI >>>> hostb0@pci0:0:24:0: class=0x060000 card=0x00000000 >>>> chip=0x11001022 rev=0x00 hdr=0x00 >>>> vendor = 'Advanced Micro Devices (AMD)' >>>> device = '(K8) Athlon 64/Opteron HyperTransport Technology >>>> Configuration' >>>> class = bridge >>>> subclass = HOST-PCI >>>> hostb1@pci0:0:24:1: class=0x060000 card=0x00000000 >>>> chip=0x11011022 rev=0x00 hdr=0x00 >>>> vendor = 'Advanced Micro Devices (AMD)' >>>> device = '(K8) Athlon 64/Opteron Address Map' >>>> class = bridge >>>> subclass = HOST-PCI >>>> hostb2@pci0:0:24:2: class=0x060000 card=0x00000000 >>>> chip=0x11021022 rev=0x00 hdr=0x00 >>>> vendor = 'Advanced Micro Devices (AMD)' >>>> device = '(K8) Athlon 64/Opteron DRAM Controller' >>>> class = bridge >>>> subclass = HOST-PCI >>>> hostb3@pci0:0:24:3: class=0x060000 card=0x00000000 >>>> chip=0x11031022 rev=0x00 hdr=0x00 >>>> vendor = 'Advanced Micro Devices (AMD)' >>>> device = '(K8) Athlon 64/Opteron Miscellaneous Control' >>>> class = bridge >>>> subclass = HOST-PCI >>>> none3@pci0:1:7:0: class=0x040000 card=0x046219b8 chip=0x880014f1 >>>> rev=0x05 hdr=0x00 >>>> vendor = 'Conexant Systems, Inc.' >>>> device = '23880 Conexant 23880 Video Capture (NTSC)' >>>> class = multimedia >>>> subclass = video >>>> none4@pci0:1:7:1: class=0x048000 card=0x046219b8 chip=0x881114f1 >>>> rev=0x05 hdr=0x00 >>>> vendor = 'Conexant Systems, Inc.' >>>> device = 'CX2388x TV Capture Chip' >>>> class = multimedia >>>> none5@pci0:1:7:2: class=0x048000 card=0x046219b8 chip=0x880214f1 >>>> rev=0x05 hdr=0x00 >>>> vendor = 'Conexant Systems, Inc.' >>>> device = 'CX2388x TV Capture Chip' >>>> class = multimedia >>>> none6@pci0:1:9:0: class=0x0c0010 card=0x30441106 chip=0x30441106 >>>> rev=0x80 hdr=0x00 >>>> vendor = 'VIA Technologies Inc' >>>> device = 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer >>>> Controller' >>>> class = serial bus >>>> subclass = FireWire >>>> vgapci0@pci0:7:0:0: class=0x030000 card=0x00000000 >>>> chip=0x040210de rev=0xa1 hdr=0x00 >>>> vendor = 'Nvidia Corp' >>>> device = 'GeForce 8600 GT' >>>> class = display >>>> subclass = VGA >>>> >>>>> How-To-Repeat: >>>> >>>>> Fix: >>>> >>>> >>>>> Release-Note: >>>>> Audit-Trail: >>>>> Unformatted: >>> >>> _______________________________________________ >>> freebsd-amd64@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >>> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >> >> >> > > -Søren thank you for taking this up. I build todays amd64 and when booting verbose I get the following messages: ----------------------------- ... atapci0: port 0x1f0-0x1f7,0x3f6, 0x170-0x177,0x376,0xffa0-0xffaf at device 4.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 ioapic0: routing inpin 14 (ISA IRQ 14) to vector 49 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ioapic0: routing intpin 15 (ISA IRQ 15) to vector 50 ata1: [MPSAFE] ata1: [ITHREAD] atapci1: port 0xc480-0xc487,0xc400-0xc403,0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc0f mem 0xfbef9000-0xfbef9fff irq 23 at device 5.0 on pci 0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xbc00 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 51 atapci1: [MPSAFE] atapci1: [ITHREAD] atapci1: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfbef9000 ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xc480 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xc400 ata2: SATA connect time=0ms ata2: reset tp1 mask=01 ostat0=50 ostat1=00 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xc080 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xc000 ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=50 ostat1=00 ata3: stat0=0x50 stat1=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] ata3: [ITHREAD] atapci2: port 0xb880-0xb887,0xb800-0xb803,0xb480-0xb487,0xb400-0xb403,0xb080-0xb08f mem 0xfbef8000-0xfbef8fff irq 20 at device 5.1 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xb080 ioapic0: routing intpin 20 (PCI IRQ 20) to vector 52 atapci2: [MPSAFE] atapci2: [ITHREAD] atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfbef8000 ata4: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0xb880 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xb800 ata4: SATA connect status=00000000 ata4: [MPSAFE] ata4: [ITHREAD] ata5: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0xb480 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb400 ata5: SATA connect status=00000000 ata5: [MPSAFE] ata5: [ITHREAD] ... ata0: identify ch->devices=00010000 ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=80 wire acd0 ... ... ata1: identify ch->devices=00000000 ata2: identify ch->devices=00000001 ata2: reiniting channel .. ata2: SATA connect time=0ms ata2: reset tp1 mask=01 ostat0=58 ostat1=00 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: reinit done .. ata2: reiniting channel .. ata2: SATA connect time=0ms ata2: reset tp1 mask=01 ostat0=58 ostat1=00 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: reinit done .. ata3: identify ch->devices=00000001 ata3: reiniting channel .. ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=58 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: reinit done .. ... ata3: reiniting channel .. ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=58 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: reinit done .. ata4: identify ch->devices=00000000 ata5: identify ch->devices=00000000 ... Manual root filesystem specification: : Mount using filesystem eg. ufs:da0s1a ? List valid disk boot devices Abort manual input ----------------------------- It seems that ata(4) is not able to initiating the SATA drives correct? BTW, this is a 4GByte system. Rainer