From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 02:34:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0B3816A41F for ; Sun, 7 Aug 2005 02:34:37 +0000 (GMT) (envelope-from chsing@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09DD743D48 for ; Sun, 7 Aug 2005 02:34:35 +0000 (GMT) (envelope-from chsing@gmail.com) Received: by zproxy.gmail.com with SMTP id z6so466643nzd for ; Sat, 06 Aug 2005 19:34:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=MQsc5yd7YfiwRGGQ4FgML8d+h104nZuBYnjiAFxHqlODHCjQkwYxHqI7ZhE6mqLRnQmDRTvnF7sn7J/iV4Yy5xvkYI/mRV0+HoedrypKMKfOWn4W9l3j+Bv3S8DVk0C33FJVRJUk6ncX6O0tn+LUXEDq7PuinGTN4VvNVlp/Qnk= Received: by 10.37.18.41 with SMTP id v41mr1832213nzi; Sat, 06 Aug 2005 19:34:26 -0700 (PDT) Received: by 10.36.91.5 with HTTP; Sat, 6 Aug 2005 19:34:26 -0700 (PDT) Message-ID: Date: Sun, 7 Aug 2005 10:34:26 +0800 From: Jhih-Sing Chen To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Disk usage problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 02:34:38 -0000 Hi all, I'm using 4.11 version of FreeBSD and I have a problem with the / partition disk usage. Actually the / partition was 90% usage, but after reboot, it turned into 31% usage. Jschen# df -h Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 20G 5.6G 13G 31% / /dev/da0s1e 418G 184G 201G 48% /home Any ideas? Thanks. -jschen From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 03:43:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C61BD16A41F for ; Sun, 7 Aug 2005 03:43:22 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D83043D55 for ; Sun, 7 Aug 2005 03:43:22 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from glenn-mobile.antimatter.net (cpe-66-27-86-22.san.res.rr.com [66.27.86.22]) (authenticated bits=0) by cobalt.antimatter.net (8.13.4/8.13.4) with ESMTP id j773hL2W007177 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO); Sat, 6 Aug 2005 20:43:21 -0700 Message-Id: <6.1.0.6.2.20050806204112.111b1eb0@cobalt.antimatter.net> X-Sender: lists@cobalt.antimatter.net X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Sat, 06 Aug 2005 20:44:04 -0700 To: Jhih-Sing Chen , freebsd-stable@freebsd.org From: Glenn Dawson In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: Disk usage problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 03:43:22 -0000 At 07:34 PM 8/6/2005, Jhih-Sing Chen wrote: >Hi all, > >I'm using 4.11 version of FreeBSD and I have a problem with the / >partition disk usage. >Actually the / partition was 90% usage, but after reboot, it turned >into 31% usage. > >Jschen# df -h >Filesystem Size Used Avail Capacity Mounted on >/dev/da0s1a 20G 5.6G 13G 31% / >/dev/da0s1e 418G 184G 201G 48% /home > >Any ideas? >Thanks. You probably deleted a file out from under something that still had the file open. The space freed by removing the file won't show up as free until the process that had the file opened closes it. A typical example would be deleting a large log file in /var/log that syslogd still has open. -Glenn >-jschen >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 15:50:52 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1691016A41F for ; Sun, 7 Aug 2005 15:50:52 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi [195.197.172.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2713743D48 for ; Sun, 7 Aug 2005 15:50:50 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [62.142.71.181] (KMMLXXXI.dsl.saunalahti.fi [62.142.71.181]) by gw01.mail.saunalahti.fi (Postfix) with ESMTP id 6CB04F0575 for ; Sun, 7 Aug 2005 18:50:48 +0300 (EEST) Message-ID: <42F62DDD.8000902@pp.nic.fi> Date: Sun, 07 Aug 2005 18:50:53 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 5.4-STABLE X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" References: <42E12A3B.8040804@pp.nic.fi> In-Reply-To: <42E12A3B.8040804@pp.nic.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: dhclient: send_packet: No buffer space available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 15:50:52 -0000 Pertti Kosunen wrote: > What could cause dhclient sometimes to fail renew the lease? I updated > world and moved to pf from ipfw same time so i don't know which to blame. > > This happens from twice a day to every few days. > > Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available > Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available > Jul 21 03:45:02 myserver dhclient: New IP Address (xl0): x.x.x.x > Jul 21 03:45:02 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 > Jul 21 03:45:02 myserver dhclient: New Broadcast Address (xl0): x.x.x.x > Jul 21 03:45:02 myserver dhclient: New Routers: x.x.x.x > > Pf.conf & dmesg: > http://www.saunalahti.fi/~pkosunen/pf.conf > http://www.saunalahti.fi/~pkosunen/dmesg Anyone know what what could be the problem with dhclient? Some buffer is full but what? Nic is 3Com 3c905B-TX, FreeBSD 5.4-STABLE & PF. "vmstat -m" output: http://www.saunalahti.fi/~pkosunen/vmstat.txt # grep dhclient /var/log/messages: Jul 25 20:46:55 myserver dhclient: New IP Address (xl0): 62.142.70.119 Jul 25 20:46:55 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 25 20:46:55 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 25 20:46:56 myserver dhclient: New Routers: 62.142.70.1 Jul 25 20:51:28 myserver dhclient: New IP Address (xl0): 62.142.70.119 Jul 25 20:51:28 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 25 20:51:28 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 25 20:51:28 myserver dhclient: New Routers: 62.142.70.1 Jul 26 21:59:20 myserver dhclient: send_packet: No buffer space available Jul 26 21:59:51 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 26 21:59:51 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 26 21:59:51 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 26 21:59:51 myserver dhclient: New Routers: 62.142.70.1 Jul 30 23:34:05 myserver dhclient: send_packet: No buffer space available Jul 30 23:34:05 myserver dhclient: send_packet: No buffer space available Jul 30 23:34:13 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 30 23:34:13 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 30 23:34:13 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 30 23:34:13 myserver dhclient: New Routers: 62.142.70.1 Jul 31 02:09:06 myserver dhclient: send_packet: No buffer space available Jul 31 02:09:06 myserver dhclient: send_packet: No buffer space available Jul 31 02:09:10 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 31 02:09:10 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 31 02:09:10 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 31 02:09:10 myserver dhclient: New Routers: 62.142.70.1 Aug 1 20:11:26 myserver dhclient: send_packet: No buffer space available Aug 1 20:11:26 myserver dhclient: send_packet: No buffer space available Aug 1 20:11:31 myserver dhclient: New IP Address (xl0): 62.142.70.200 Aug 1 20:11:31 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 1 20:11:31 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 1 20:11:31 myserver dhclient: New Routers: 62.142.70.1 Aug 2 23:03:11 myserver dhclient: send_packet: No buffer space available Aug 2 23:03:11 myserver dhclient: send_packet: No buffer space available Aug 2 23:03:19 myserver dhclient: New IP Address (xl0): 62.142.70.200 Aug 2 23:03:19 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 2 23:03:19 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 2 23:03:19 myserver dhclient: New Routers: 62.142.70.1 Aug 3 22:29:12 myserver dhclient: send_packet: No buffer space available Aug 3 22:29:12 myserver dhclient: send_packet: No buffer space available Aug 3 22:29:21 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 3 22:29:21 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 3 22:29:21 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 3 22:29:21 myserver dhclient: New Routers: 62.142.70.1 Aug 4 01:05:46 myserver dhclient: send_packet: No buffer space available Aug 4 01:05:46 myserver dhclient: send_packet: No buffer space available Aug 4 01:05:55 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 4 01:05:55 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 4 01:05:55 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 4 01:05:55 myserver dhclient: New Routers: 62.142.70.1 Aug 6 16:53:32 myserver dhclient: send_packet: No buffer space available Aug 6 16:53:32 myserver dhclient: send_packet: No buffer space available Aug 6 16:53:37 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 6 16:53:37 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 6 16:53:37 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 6 16:53:37 myserver dhclient: New Routers: 62.142.70.1 Aug 7 06:49:07 myserver dhclient: send_packet: No buffer space available Aug 7 06:49:07 myserver dhclient: send_packet: No buffer space available Aug 7 06:49:12 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 7 06:49:12 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 7 06:49:12 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 7 06:49:12 myserver dhclient: New Routers: 62.142.70.1 Aug 7 14:22:17 myserver dhclient: send_packet: No buffer space available Aug 7 14:22:46 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 7 14:22:46 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 7 14:22:46 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 7 14:22:46 myserver dhclient: New Routers: 62.142.70.1 Aug 7 16:57:26 myserver dhclient: send_packet: No buffer space available Aug 7 16:57:26 myserver dhclient: send_packet: No buffer space available Aug 7 16:57:35 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 7 16:57:35 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 7 16:57:35 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 7 16:57:35 myserver dhclient: New Routers: 62.142.70.1 From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 16:51:13 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07A1716A41F for ; Sun, 7 Aug 2005 16:51:13 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from tirith.ics.muni.cz (tirith.ics.muni.cz [147.251.4.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4631544133 for ; Sun, 7 Aug 2005 16:51:11 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (w54-186.fi.muni.cz [147.251.54.186]) (user=hopet@META mech=LOGIN bits=0) by tirith.ics.muni.cz (8.13.2/8.13.2) with ESMTP id j77Gp83Z027716 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 7 Aug 2005 18:51:10 +0200 From: "Petr Holub" To: Date: Sun, 7 Aug 2005 18:51:09 +0200 Message-ID: <000401c59b70$3627fd40$ba36fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Muni-Spam-TestIP: 147.251.54.186 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Virus-Test: Clean Cc: Subject: kernel panic on 5.4-RELEASE-p6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 16:51:13 -0000 Hi all, I've encoutnered the follwing kernel panic on 5.4-RELEASE-p6. However, as the machine is production and not development one, I don't have debugger analysis. The panic might *theoretically* be due to problems accessing faulty CD-R media in the ATAPI DVD/CD-RW drive (that was the only unusual thing which happened before the panic). Kernel config and dmesg are attached below, the machine is IBM T41p laptop. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x300f0 fault code = supervisor read, page not present instruction pointer = 0x8:0x300f0 stack pointer = 0x10:0xe67cdb1c frame pointer = 0x10:0xe67cdb34 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1337 (vim) trap number = 12 panic: page fault Uptime: 14m43s. Best, Petr ================================================================ Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 4 Institute of Compt. Science 162 00 Praha 6, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: Petr.Holub@cesnet.cz phone: +420-549493944 fax: +420-541212747 e-mail: hopet@ics.muni.cz machine i386 cpu I686_CPU ident KLOBOUCEK # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. options SCHED_4BSD # 4BSD scheduler # options SCHED_ULE options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs. device em # Intel PRO/1000 adapter Gigabit Ethernet Card # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support # Wireless NIC cards device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) # IBM 41p device smbus device radeondrm # options DRM_DEBUG device atapicam device sound device snd_ich options NTFS options NDISAPI # device ndis # Zda se, ze tahle netgraph/bluetooth potvora panikari kernel! # options NETGRAPH #netgraph(4) system # options NETGRAPH_BLUETOOTH # ng_bluetooth(4) # options NETGRAPH_BLUETOOTH_BT3C # ng_bt3c(4) # options NETGRAPH_BLUETOOTH_H4 # ng_h4(4) # options NETGRAPH_BLUETOOTH_HCI # ng_hci(4) # options NETGRAPH_BLUETOOTH_L2CAP # ng_l2cap(4) # options NETGRAPH_BLUETOOTH_SOCKET # ng_btsocket(4) # options NETGRAPH_BLUETOOTH_UBT # ng_ubt(4) # options NETGRAPH_BLUETOOTH_UBTBCMFW # ubtbcmfw(4) # S55 device ucom device uplcom # Dalsi vychytavky options PREEMPTION options PSM_HOOKRESUME #hook the system resume event, useful options PSM_RESETAFTERSUSPEND #reset the device at the resume event Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE-p6 #11: Thu Jul 28 17:11:27 CEST 2005 toor@kloboucek.ics.muni.cz:/usr/src/sys/i386/compile/KLOBOUCEK Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1700MHz (1694.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Features=0xa7e9f9bf real memory = 536215552 (511 MB) avail memory = 515047424 (491 MB) npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi_ec0: port 0x66,0x62 on acpi0 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 cbb0: mem 0xb0000000-0xb0000fff irq 11 at device 0.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0xb1000000-0xb1000fff irq 11 at device 0.1 on pci2 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 em0: port 0x8000-0x803f mem 0xc0200000-0xc020ffff,0xc0220000-0xc023ffff irq 11 at device 1.0 on pci2 em0: Ethernet address: 00:0d:60:89:a1:da em0: Speed:N/A Duplex:N/A ndis0: mem 0xc0210000-0xc0210fff irq 11 at device 2.0 on pci2 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:0c:f1:1c:bf:83 ndis0: 11b rates: 11Mbps 2Mbps 1Mbps 5.5Mbps isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) pcm0: port 0x18c0-0x18ff,0x1c00-0x1cff mem 0xc0000800-0xc00008ff,0xc0000c00-0xc0000dff irq 11 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 8250 or not responding ppc0: port 0x3bc-0x3be irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled acpi_cmbat0: on acpi0 acpi_acad0: on acpi0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xdc000-0xdffff,0xd1000-0xd1fff,0xd0000-0xd0fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1694511100 Hz quality 800 Timecounters tick every 10.000 msec ad0: 53959MB [109632/16/63] at ata0-master UDMA100 acd0: CDRW at ata1-master PIO4 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Mounting root from ufs:/dev/ad0s2a ndis0: link up ndis0: couldn't change DS config to 2437000kHz: 19 ndis0: link up From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 17:43:52 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A02FF16A41F for ; Sun, 7 Aug 2005 17:43:52 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 418D343D45 for ; Sun, 7 Aug 2005 17:43:52 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 5D7B85E3A; Sun, 7 Aug 2005 13:43:51 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02474-01; Sun, 7 Aug 2005 13:43:46 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 017FB5C67; Sun, 7 Aug 2005 13:43:44 -0400 (EDT) Message-ID: <42F64856.2010506@mac.com> Date: Sun, 07 Aug 2005 13:43:50 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Subscribers to FreeBSD-Stable References: <42E12A3B.8040804@pp.nic.fi> <42F62DDD.8000902@pp.nic.fi> In-Reply-To: <42F62DDD.8000902@pp.nic.fi> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: Subject: Re: dhclient: send_packet: No buffer space available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 17:43:52 -0000 Pertti Kosunen wrote: > Pertti Kosunen wrote: >> What could cause dhclient sometimes to fail renew the lease? I updated >> world and moved to pf from ipfw same time so i don't know which to blame. >> >> This happens from twice a day to every few days. >> >> Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available >> Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available >> Jul 21 03:45:02 myserver dhclient: New IP Address (xl0): x.x.x.x >> Jul 21 03:45:02 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 >> Jul 21 03:45:02 myserver dhclient: New Broadcast Address (xl0): x.x.x.x >> Jul 21 03:45:02 myserver dhclient: New Routers: x.x.x.x >> >> Pf.conf & dmesg: >> http://www.saunalahti.fi/~pkosunen/pf.conf >> http://www.saunalahti.fi/~pkosunen/dmesg > > > Anyone know what what could be the problem with dhclient? Some buffer is > full but what? > > Nic is 3Com 3c905B-TX, FreeBSD 5.4-STABLE & PF. Typically, that sort of message indicates that the firewall rules are preventing traffic from going out, or packets are getting stuck in a queue until it fills up, or maybe even a bug somewhere in the particular combination of kernel firewall options enabled, high optimization or CPUTYPE settings, and your particular hardware, depending on how lucky you are. :-) Does the problem go away if you use a trivial "permit all" PF ruleset? Does the problem go away if you use a trivial IPFW "permit all" instead of PF? Does the problem go away if you use a stock 5.4 release kernel? The 3Com 3c905B-TX is an OK NIC, apparently the later C revision or the 918/920's are pretty decent, but anyway-- ...does the problem go away if you switch to another (known good) NIC? -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 21:05:24 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8387716A41F for ; Sun, 7 Aug 2005 21:05:21 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2433343F38 for ; Sun, 7 Aug 2005 21:05:13 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E1sKW-00070u-NQ for freebsd-stable@freebsd.org; Sun, 07 Aug 2005 21:05:12 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E1sKU-000EPx-Qr for freebsd-stable@freebsd.org; Sun, 07 Aug 2005 11:05:10 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17142.30598.428221.864901@roam.psg.com> Date: Sun, 7 Aug 2005 11:05:10 -1000 To: FreeBSD Stable Subject: 4.11 to RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 21:05:24 -0000 any peculiarities/clues for upgrading an antique from 4.11 to RELENG_6 beyond the "To upgrade in-place from 5.x-stable to current" in UPDATING? randy From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 23:44:00 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2723B16A494 for ; Sun, 7 Aug 2005 23:43:58 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62DE143E89 for ; Sun, 7 Aug 2005 23:26:28 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-37-29.dynamic.qsc.de [212.202.37.29]) by efacilitas.de (Postfix) with ESMTP id 8C23F4AE58; Mon, 8 Aug 2005 01:32:08 +0000 (UTC) Received: from localhost (eurystheus.local [192.168.1.67]) by eurystheus.local (Postfix) with ESMTP id 0CE5612B101; Mon, 8 Aug 2005 01:25:43 +0200 (CEST) Received: from eurystheus.local ([192.168.1.67]) by localhost (eurystheus.locaL [192.168.1.67]) (amavisd-new, port 10024) with ESMTP id 84169-10; Mon, 8 Aug 2005 01:25:36 +0200 (CEST) Received: from [192.168.1.67] (eurystheus.local [192.168.1.67]) by eurystheus.local (Postfix) with ESMTP id B2B5A12B0FF; Mon, 8 Aug 2005 01:25:35 +0200 (CEST) Message-ID: <42F6986E.8090508@cs.tu-berlin.de> Date: Mon, 08 Aug 2005 01:25:34 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050517 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Randy Bush References: <17142.30598.428221.864901@roam.psg.com> In-Reply-To: <17142.30598.428221.864901@roam.psg.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at example.com Cc: FreeBSD Stable Subject: Re: 4.11 to RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 23:44:01 -0000 Randy Bush wrote: > any peculiarities/clues for upgrading an antique from 4.11 to > RELENG_6 beyond the "To upgrade in-place from 5.x-stable to > current" in UPDATING? I guess not. From the release notes of 6.0-BETA2: "Source upgrades to FreeBSD 6.0-CURRENT are only supported from FreeBSD 5.3-RELEASE or later. Users of older systems wanting to upgrade 6.0-CURRENT will need to update to FreeBSD 5.3 or newer first, then to FreeBSD 6.0-CURRENT." Björn -- Björn König (bkoenig@cs.tu-berlin.de) student at the Technische Universität Berlin http://bkoenig.alpha-tierchen.de/ From owner-freebsd-stable@FreeBSD.ORG Sun Aug 7 23:44:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2EA116A438 for ; Sun, 7 Aug 2005 23:44:39 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F22B43D49 for ; Sun, 7 Aug 2005 23:44:39 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E1uop-000AtD-9N; Sun, 07 Aug 2005 23:44:39 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E1uon-000EcO-Bw; Sun, 07 Aug 2005 13:44:37 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17142.40164.863985.695732@roam.psg.com> Date: Sun, 7 Aug 2005 13:44:36 -1000 To: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= References: <17142.30598.428221.864901@roam.psg.com> <42F6986E.8090508@cs.tu-berlin.de> Cc: FreeBSD Stable Subject: Re: 4.11 to RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Aug 2005 23:44:39 -0000 > "Source upgrades to FreeBSD 6.0-CURRENT are only supported from FreeBSD > 5.3-RELEASE or later. Users of older systems wanting to upgrade > 6.0-CURRENT will need to update to FreeBSD 5.3 or newer first, then to > FreeBSD 6.0-CURRENT." sigh. on that path now. it has rocks. randy From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 09:21:47 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBB2816A41F for ; Mon, 8 Aug 2005 09:21:47 +0000 (GMT) (envelope-from anne@wasabi.apnic.net) Received: from apnic.net (cumin.apnic.net [202.12.29.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56D1943D45 for ; Mon, 8 Aug 2005 09:21:47 +0000 (GMT) (envelope-from anne@wasabi.apnic.net) Received: from wasabi.apnic.net (wasabi.apnic.net [202.12.29.250]) by apnic.net (8.12.8/8.12.8) with ESMTP id j789Lj6g026833 for ; Mon, 8 Aug 2005 19:21:45 +1000 Received: from wasabi.apnic.net (localhost.localdomain [127.0.0.1]) by wasabi.apnic.net (8.12.8/8.12) with ESMTP id j789LidB005152 for ; Mon, 8 Aug 2005 19:21:44 +1000 Received: (from anne@localhost) by wasabi.apnic.net (8.12.8/8.12.1/Submit) id j789LiEV005147; Mon, 8 Aug 2005 19:21:44 +1000 Date: Mon, 8 Aug 2005 19:21:44 +1000 From: Anne Lord Message-Id: <200508080921.j789LiEV005147@wasabi.apnic.net> To: freebsd-stable@freebsd.org References: <200508080921.j789LZ6g026818@apnic.net> In-Reply-To: <200508080921.j789LZ6g026818@apnic.net> Precedence: junk X-Loop: anne@apnic.net X-Scanned-By: MIMEDefang 2.15 (www dot roaringpenguin dot com slash mimedefang) X-AP-Spam-Status: No, hits=-104.901 required=6 X-AP-Spam-Score: -104.901 (notspam) BAYES_00,USER_IN_WHITELIST Subject: Re: error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 09:21:48 -0000 Hello there! Many thanks for your mail. I am away from my mail until Friday 22nd July tand will not be reading my email during this time. Apologies for any inconvenience this may cause. If your email or query is urgent, please contact the APNIC Helpdesk directly on +61 7 3858 3188 or email . Best wishes, Anne _____________________________________________________________________ Anne Lord, Communications Director Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 --------------------------------------------------------------------- See you at APNIC 20, Hanoi, Vietnam, 6-9 Sep 2005 http://www.apnic.net/meetings --------------------------------------------------------------------- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 09:46:30 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B76B716A41F for ; Mon, 8 Aug 2005 09:46:30 +0000 (GMT) (envelope-from rene@82-168-75-155-bbxl.xdsl.tiscali.nl) Received: from 82-168-75-155-bbxl.xdsl.tiscali.nl (82-168-75-155-bbxl.xdsl.tiscali.nl [82.168.75.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF2F043D45 for ; Mon, 8 Aug 2005 09:46:29 +0000 (GMT) (envelope-from rene@82-168-75-155-bbxl.xdsl.tiscali.nl) Received: from 82-168-75-155-bbxl.xdsl.tiscali.nl (localhost [127.0.0.1]) by 82-168-75-155-bbxl.xdsl.tiscali.nl (8.13.4/8.13.4) with ESMTP id j789kQq2026341 for ; Mon, 8 Aug 2005 11:46:26 +0200 (CEST) (envelope-from rene@82-168-75-155-bbxl.xdsl.tiscali.nl) Received: (from rene@localhost) by 82-168-75-155-bbxl.xdsl.tiscali.nl (8.13.4/8.13.1/Submit) id j789kQ43026340 for stable@freebsd.org; Mon, 8 Aug 2005 11:46:26 +0200 (CEST) (envelope-from rene) Date: Mon, 8 Aug 2005 11:46:25 +0200 From: Rene Ladan To: stable@freebsd.org Message-ID: <20050808094625.GA26224@82-168-75-155-bbxl.xdsl.tiscali.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: some sysctls not preserved across suspend X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 09:46:30 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've noticed that the net.wlan.0.debug sysctl is always reset to 0 if I resume from a suspend with zzz(8) (acpi version). I'm running FreeBSD 6.0-BETA2 #2: Wed Aug 3 17:18:44 CEST 2005 root@82= -168-75-155-bbxl.xdsl.tiscali.nl:/usr/obj/usr/src/sys/RENE More info is available at ftp://82.168.75.155/pub/{conf|log} Is this by design? Regards, Rene --=20 GPG fingerprint =3D 5FFA 3959 3377 C697 8428 24D0 BF3E F4A9 AE33 5DCC "It won't fit on the line." -- me, 2001 --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFC9ynwvz70qa4zXcwRAkPUAJ9rZlRyOriO4M5SsE30s+8jr3F6IwCfVZxy jhSkLcxIB0/7ul5nSrABE7A= =fMao -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 10:25:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6440B16A41F for ; Mon, 8 Aug 2005 10:25:30 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id F28FF43D46 for ; Mon, 8 Aug 2005 10:25:29 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [62.142.71.181] (KMMLXXXI.dsl.saunalahti.fi [62.142.71.181]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 65A53D1193; Mon, 8 Aug 2005 13:25:26 +0300 (EEST) Message-ID: <42F7331B.6000707@pp.nic.fi> Date: Mon, 08 Aug 2005 13:25:31 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 5.4-STABLE X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" References: <42E12A3B.8040804@pp.nic.fi> <42F62DDD.8000902@pp.nic.fi> <42F64856.2010506@mac.com> In-Reply-To: <42F64856.2010506@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: dhclient: send_packet: No buffer space available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 10:25:30 -0000 Chuck Swiger wrote: > Typically, that sort of message indicates that the firewall rules are > preventing traffic from going out, or packets are getting stuck in a > queue until it fills up, or maybe even a bug somewhere in the > particular combination of kernel firewall options enabled, high > optimization or CPUTYPE settings, and your particular hardware, > depending on how lucky you are. :-) > > Does the problem go away if you use a trivial "permit all" PF ruleset? > Does the problem go away if you use a trivial IPFW "permit all" > instead of PF? > Does the problem go away if you use a stock 5.4 release kernel? > > The 3Com 3c905B-TX is an OK NIC, apparently the later C revision or > the 918/920's are pretty decent, but anyway-- > > ...does the problem go away if you switch to another (known good) NIC? > System was ok with 5.3-RELEASE & custom kernel with ipfw. PF logs all block rules and nothing gets to pflog on those dhclient errors. I try those tips you gave, thanks. Stuck in a queue sounds most likely to be the case. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 12:49:39 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 539FB16A41F for ; Mon, 8 Aug 2005 12:49:39 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5D5643D45 for ; Mon, 8 Aug 2005 12:49:38 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (zwtcfq@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j78CnZU6021086 for ; Mon, 8 Aug 2005 14:49:36 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j78CnZOF021085; Mon, 8 Aug 2005 14:49:35 +0200 (CEST) (envelope-from olli) Date: Mon, 8 Aug 2005 14:49:35 +0200 (CEST) Message-Id: <200508081249.j78CnZOF021085@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <42F6986E.8090508@cs.tu-berlin.de> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: 4.11 to RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 12:49:39 -0000 Björn König wrote: > Randy Bush wrote: > > any peculiarities/clues for upgrading an antique from 4.11 to > > RELENG_6 beyond the "To upgrade in-place from 5.x-stable to > > current" in UPDATING? > > I guess not. From the release notes of 6.0-BETA2: > > "Source upgrades to FreeBSD 6.0-CURRENT are only supported from FreeBSD > 5.3-RELEASE or later. Users of older systems [...] Unfortunately, that statement is ambiguous: FreeBSD 4.11 (Jan. 2005) is _not_ older than 5.3 (Nov. 2004). However, I guess that's not what the release notes really mean. For the mentioned update from 4.x to 6.x, I would go via a binary upgrade, which has probably fewer pitfalls and is finished a lot faster than a source upgrade. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "It combines all the worst aspects of C and Lisp: a billion different sublanguages in one monolithic executable. It combines the power of C with the readability of PostScript." -- Jamie Zawinski, when asked: "What's wrong with perl?" From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 15:26:11 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F00F016A41F for ; Mon, 8 Aug 2005 15:26:11 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-04.nyroc.rr.com (ms-smtp-04.nyroc.rr.com [24.24.2.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95E0143D45 for ; Mon, 8 Aug 2005 15:26:11 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.2] (cpe-24-198-203-97.maine.res.rr.com [24.198.203.97]) by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id j78FQ8pm013027 for ; Mon, 8 Aug 2005 11:26:09 -0400 (EDT) Date: Mon, 8 Aug 2005 08:26:04 -0400 (EDT) From: Brad Miele To: stable@freebsd.org Message-ID: <20050808082509.V714@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Subject: bge watchdog errors in -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 15:26:12 -0000 Hi, Last week, i cvsupped two HP Proliant DL380 G4 machines to the most recent stable, which replaced the bge driver from mid may with the one committed on or around June 24. Since updating, my cards, Broadcom BCM5704C have been throwing occasional watchdog timeout errors on their shared 1000basetx net. These errors do not currently seem to be effecting much, and there have only been 6 since last friday, but I would like to clear them up. I noted that the current version of the bge driver had code backed out from the previous one, and an option "BGE_FAKE_AUTONEG" was added. I have tried enabling this option, as it seems to pertain to this chipset, but the errors are still occuring. I am thinking of switching the cards from autoselect to explicit 1000basetx, with one of them set to link0. Please confirm that this is a reasonable next step and let me know any other information that will be useful. Regards, Brad ------------------------------------------------------------ Brad Miele Technology Director IPNStock (866) 476-7862 x902 bmiele@ipnstock.com From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 15:51:18 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0963316A41F for ; Mon, 8 Aug 2005 15:51:18 +0000 (GMT) (envelope-from grafan@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id A09E543D6D for ; Mon, 8 Aug 2005 15:51:14 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by wproxy.gmail.com with SMTP id i22so1027953wra for ; Mon, 08 Aug 2005 08:51:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ehk44Uc1hvYTPJKj9tHyIZUDA8OulBeqLugN9pQFaEqliBLIfxAnVqPO7Fm3bKEZ/t/wgJ6arWdh9GFG796Gw6kgtrUeSpfki+rPXCYMpSx2LPTxg0AdEXAhA3SqGgW0NbBWnyy2bkxyjvBiscnevPlNX77UMIekrLUy0qhE9AY= Received: by 10.54.111.11 with SMTP id j11mr4341591wrc; Mon, 08 Aug 2005 08:51:13 -0700 (PDT) Received: by 10.54.7.20 with HTTP; Mon, 8 Aug 2005 08:51:13 -0700 (PDT) Message-ID: <6eb82e050808085132807d80@mail.gmail.com> Date: Mon, 8 Aug 2005 23:51:13 +0800 From: Rong-En Fan To: Robert Watson In-Reply-To: <20050729001511.O60522@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6eb82e0507241001615f7490@mail.gmail.com> <20050729001511.O60522@fledge.watson.org> Cc: stable@freebsd.org, A.S.Usov@kvi.nl Subject: Re: panic: sbflush_locked on 5.4-p5/i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 15:51:18 -0000 Hi After upgrading to 5-STABLE (about Aug 6), it works very good. With mpsafenet=3D1, it can work more than one day without panic. For 5.4-p5, it will panic at most half day or so. This bug seems fixed after 5.4 is released. I'll keep watching this machine. Will let you know if it still have similar panics ;-) Regards, Rong-En Fan On 7/29/05, Robert Watson wrote: > On Mon, 25 Jul 2005, Rong-En Fan wrote: > > I have a 5.4-p5 running on i386. Got a panic: panic: sbflush_locked: cc > > 0 || mb 0xc33bf000 || mbcnt 4294967040 It is an web server running > > Apache and Postfix as a backup MX. I'm using gmirror on all partitions > > and thus cannot get a dump (swap is on gmirror). Some ddb outputs are > > below. > From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 16:27:31 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9499A16A41F for ; Mon, 8 Aug 2005 16:27:31 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4330243D46 for ; Mon, 8 Aug 2005 16:27:31 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 7ACBC46B46; Mon, 8 Aug 2005 12:27:30 -0400 (EDT) Date: Mon, 8 Aug 2005 17:30:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Rong-En Fan In-Reply-To: <6eb82e050808085132807d80@mail.gmail.com> Message-ID: <20050808171707.E34546@fledge.watson.org> References: <6eb82e0507241001615f7490@mail.gmail.com> <20050729001511.O60522@fledge.watson.org> <6eb82e050808085132807d80@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, A.S.Usov@kvi.nl Subject: Re: panic: sbflush_locked on 5.4-p5/i386 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 16:27:31 -0000 On Mon, 8 Aug 2005, Rong-En Fan wrote: > After upgrading to 5-STABLE (about Aug 6), it works very good. With > mpsafenet=1, it can work more than one day without panic. For 5.4-p5, it > will panic at most half day or so. This bug seems fixed after 5.4 is > released. I'll keep watching this machine. Will let you know if it still > have similar panics ;-) If you can confirm that the problem really is fixed in -STABLE, there are two sets of changes that may be relevant: - There are a number of SACK-related bug fixes in RELENG_5 that are not in the RELENG_5_4 branch. - There are a number of TCP/inpcb-related locking fixes (one in particular for IPv6) that are in RELENG_5 but not RELENG_5_4. We can then try and figure out which change it is that's helping, and get that merged to RELENG_5_4 as an errata item. If you have IPv6 traffic, there are some fixes I made a month or two ago that might be particularly relevant during connection tear-down. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 18:15:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCC6216A420; Mon, 8 Aug 2005 18:15:27 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8232E43D55; Mon, 8 Aug 2005 18:15:27 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from dhcp-168-0-23.packetdesign.com (dns.packetdesign.com [65.192.41.10]) (authenticated bits=0) by b.mail.sonic.net (8.13.3/8.13.3) with ESMTP id j78IFQcq031211 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 8 Aug 2005 11:15:27 -0700 From: "Bruce A. Mah" To: freebsd-stable@freebsd.org In-Reply-To: <200508081249.j78CnZOF021085@lurza.secnetix.de> References: <200508081249.j78CnZOF021085@lurza.secnetix.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-5D1JRzTMGTx2FzmD1LvX" Date: Mon, 08 Aug 2005 11:15:23 -0700 Message-Id: <1123524923.20430.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Cc: bmah@freebsd.org Subject: Re: 4.11 to RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 18:15:27 -0000 --=-5D1JRzTMGTx2FzmD1LvX Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Oliver Fromme wrote: > Bj=F6rn K=F6nig wrote: > > Randy Bush wrote: > > > any peculiarities/clues for upgrading an antique from 4.11 to > > > RELENG_6 beyond the "To upgrade in-place from 5.x-stable to=20 > > > current" in UPDATING? > >=20 > > I guess not. From the release notes of 6.0-BETA2: > >=20 > > "Source upgrades to FreeBSD 6.0-CURRENT are only supported from FreeBS= D=20 > > 5.3-RELEASE or later. Users of older systems [...] >=20 > Unfortunately, that statement is ambiguous: FreeBSD 4.11 > (Jan. 2005) is _not_ older than 5.3 (Nov. 2004). However, > I guess that's not what the release notes really mean. Sorry. :-( The case of someone trying to upgrade from 4.X to 6.X hadn't occurred to me when I wrote that (because, as noted, 4.X to 5.X is non-trivial). > For the mentioned update from 4.x to 6.x, I would go via > a binary upgrade, which has probably fewer pitfalls and > is finished a lot faster than a source upgrade. I'd advise that as well. Bruce. --=-5D1JRzTMGTx2FzmD1LvX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC96E72MoxcVugUsMRAoZ1AKDIGxSlK2j5wBKIyRsDFEHp3esYGwCfVuY6 OKGeuuJj12Kjcqprb3dFxB0= =MW1X -----END PGP SIGNATURE----- --=-5D1JRzTMGTx2FzmD1LvX-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 20:10:28 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E59A16A4C9 for ; Mon, 8 Aug 2005 20:10:28 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E8DC43D48 for ; Mon, 8 Aug 2005 20:10:27 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 45163 invoked by uid 399); 8 Aug 2005 20:10:26 -0000 Received: from 69-175-228-47.vnnyca.adelphia.net (HELO ?192.168.1.101?) (dougb@dougbarton.net@69.175.228.47) by mail1.fluidhosting.com with SMTP; 8 Aug 2005 20:10:26 -0000 Message-ID: <42F7BC2E.9000501@FreeBSD.org> Date: Mon, 08 Aug 2005 13:10:22 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frank McConnell References: <200507290034.j6T0YLdZ014411@lots.reanimators.org> <20050729091624.R74149@fledge.watson.org> <200507291809.j6TI9p37035628@lots.reanimators.org> <200508021726.j72HQPQG051111@lots.reanimators.org> <200508022220.j72MKvUt056654@lots.reanimators.org> <200508050514.j755EWpH019403@lots.reanimators.org> <20050806105211.I15658@shared10.hosting.flyingcroc.net> <200508062051.j76KphGm063013@lots.reanimators.org> In-Reply-To: <200508062051.j76KphGm063013@lots.reanimators.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Chris Gabe , dpk , Ted Wisniewski Subject: Re: RELENG_5 PAE panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 20:10:28 -0000 Frank McConnell wrote: > I have two ways to provoke the failure: starting named (a modified > BIND 8 As a general rule, it would be a good idea to start thinking about moving toward BIND 9. The 9.4 series will have better performance, DNSSEC, and other attractive features. If you start thinking about it now, you will hopefully be prepared down the road. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 20:44:08 2005 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B77BA16A41F for ; Mon, 8 Aug 2005 20:44:08 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 879DC43D55 for ; Mon, 8 Aug 2005 20:44:07 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.40.201] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 08 Aug 2005 16:58:53 -0400 From: John Baldwin To: stable@FreeBSD.org Date: Mon, 8 Aug 2005 16:44:36 -0400 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508081644.37510.jhb@FreeBSD.org> Cc: Subject: Any el(4) users out there? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 20:44:08 -0000 Is there anyone who has el(4) hardware that can test some patches for adding MPSAFE locking in current? Thanks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 21:08:21 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A0C616A41F for ; Mon, 8 Aug 2005 21:08:21 +0000 (GMT) (envelope-from jendries@pragmeta.com) Received: from mx2.pragmeta.com (mx2.pragmeta.com [216.230.164.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4032E43D62 for ; Mon, 8 Aug 2005 21:08:16 +0000 (GMT) (envelope-from jendries@pragmeta.com) Received: from [192.168.0.154] (host-64-246-146-151.ubr0.alb1.inoc.net [64.246.146.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.pragmeta.com (Postfix) with ESMTP id ADE0C1DD23 for ; Mon, 8 Aug 2005 17:08:13 -0400 (EDT) Message-ID: <42F7C8AF.8060608@pragmeta.com> Date: Mon, 08 Aug 2005 17:03:43 -0400 From: Josh Endries User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050405) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: twa0 errors and system lockup on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 21:08:21 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Just a little while ago I got this on a test 5.4-stable dual Opteron box I'm setting up (9500S-LP RAID 5 with a hot spare): Aug 8 15:58:21 kernel: twa0: ERROR: (0x05: 0x210b): Request timed out!: request = 0xffffffff80a67700 Aug 8 15:58:21 kernel: twa0: INFO: (0x16: 0x1108): Resetting controller...: Aug 8 15:58:21 kernel: twa0: ERROR: (0x15: 0x110b): Can't drain AEN queue after reset: error = 60 Aug 8 15:58:21 kernel: twa0: ERROR: (0x16: 0x1105): Controller reset failed: error = 60; attempt 1 It attempted twice and then just sat there after that. I couldn't log in at all so I did a hard reset after probably 30+ minutes. I didn't find much online other than driver source code or twe(4) man pages, which suggests that it's a problem between the driver and card. Has anyone else seen this problem? Is it a sign of a flaky card or could it be something else? Maybe it's something to do with AMD64? This system was supposed to go into production tomorrow. I guess it's good that it died today... Josh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC98ivV/+PyAj2L+IRAvjBAJsFpObq5a7M41YvfXSSM4uJ4QnODgCfZqqF y4ipPqIJIgJVxYm1UUeP4WQ= =sbYn -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 21:29:04 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8498816A41F for ; Mon, 8 Aug 2005 21:29:04 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE18B43D5A for ; Mon, 8 Aug 2005 21:29:01 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j78LWA4R002474; Mon, 8 Aug 2005 17:32:10 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Mon, 8 Aug 2005 17:28:38 -0400 User-Agent: KMail/1.6.2 References: <42F7C8AF.8060608@pragmeta.com> In-Reply-To: <42F7C8AF.8060608@pragmeta.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200508081728.41755.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.85.1/1008/Sun Aug 7 18:59:27 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Josh Endries Subject: Re: twa0 errors and system lockup on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 21:29:04 -0000 On Monday 08 August 2005 05:03 pm, Josh Endries wrote: > Hello, > > Just a little while ago I got this on a test 5.4-stable dual > Opteron box I'm setting up (9500S-LP RAID 5 with a hot spare): > > Aug 8 15:58:21 kernel: twa0: ERROR: (0x05: 0x210b): Request timed > out!: request = 0xffffffff80a67700 > Aug 8 15:58:21 kernel: twa0: INFO: (0x16: 0x1108): Resetting > controller...: > Aug 8 15:58:21 kernel: twa0: ERROR: (0x15: 0x110b): Can't drain > AEN queue after reset: error = 60 > Aug 8 15:58:21 kernel: twa0: ERROR: (0x16: 0x1105): Controller > reset failed: error = 60; attempt 1 > > It attempted twice and then just sat there after that. I couldn't > log in at all so I did a hard reset after probably 30+ minutes. I > didn't find much online other than driver source code or twe(4) man > pages, which suggests that it's a problem between the driver and > card. Has anyone else seen this problem? Is it a sign of a flaky > card or could it be something else? Maybe it's something to do with > AMD64? This system was supposed to go into production tomorrow. I > guess it's good that it died today... I have seen it with 9500S-8, which is the same controller with 8 ports. In fact, I am seeing other problems. twa0: INFO: (0x04: 0x000b): Rebuild started: unit=0 twa0: ERROR: (0x04: 0x0002): Degraded unit: unit=0, port=5 twa0: INFO: (0x04: 0x000b): Rebuild started: unit=0 twa0: INFO: (0x04: 0x003b): Rebuild paused: unit=0 twa0: INFO: (0x04: 0x000b): Rebuild started: unit=0 twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=5 twa0: INFO: (0x04: 0x003b): Rebuild paused: unit=0 twa0: INFO: (0x04: 0x000b): Rebuild started: unit=0 twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=5 twa0: INFO: (0x04: 0x0005): Rebuild completed: unit=0 twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=5 twa0: ERROR: (0x04: 0x0002): Degraded unit: unit=0, port=5 I have rebuilt this array many times but it's happening again and again. It seems this controller/driver has issues with amd64. FYI, UP kernel or replacing cables didn't fix the problem. Good luck, Jung-uk Kim > Josh From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 22:06:16 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93B5C16A41F for ; Mon, 8 Aug 2005 22:06:16 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 403B543D53 for ; Mon, 8 Aug 2005 22:06:16 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E2Fl9-000HwT-TV for freebsd-stable@freebsd.org; Mon, 08 Aug 2005 22:06:16 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E2Fl9-0000Yy-Am for freebsd-stable@freebsd.org; Mon, 08 Aug 2005 12:06:15 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17143.55126.928714.853442@roam.psg.com> Date: Mon, 8 Aug 2005 12:06:14 -1000 To: FreeBSD Stable Subject: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 22:06:16 -0000 at the make installworld step in the 4->5 upgrade sequence. /usr/share/man/man3/item_value.3.gz -> /usr/share/man/man3/mitem_value.3.gz /usr/share/man/man3/set_item_value.3.gz -> /usr/share/man/man3/mitem_value.3.gz /usr/share/man/man3/item_visible.3.gz -> /usr/share/man/man3/mitem_visible.3.gz ===> lib/libmilter install -C -o root -g wheel -m 444 libmilter.a /usr/lib install: libmilter.a: No such file or directory *** Error code 71 how can i get past this to get a clean enough system to be able to build again? randy From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 23:56:26 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A066516A41F for ; Mon, 8 Aug 2005 23:56:26 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F1F043D45 for ; Mon, 8 Aug 2005 23:56:25 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id i11so825583wra for ; Mon, 08 Aug 2005 16:56:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LyQ7eZgCz/zn9OvGi0RgEcojVB1x1+GSGoq5uvZpQ0Y3BrKH3WbPWl3KSL8YgiM+KGdQbC8JEPP5Sk6xKlfjYO7rq+Y03+mnOEiqZQhkmZcQG8UTU36E4wdo0iwtwXACHL7nGphs5B6hScJTfF8Nt9PPeQcSDsIbfJKwnUes/S0= Received: by 10.54.158.13 with SMTP id g13mr5233603wre; Mon, 08 Aug 2005 16:56:24 -0700 (PDT) Received: by 10.54.29.26 with HTTP; Mon, 8 Aug 2005 16:56:24 -0700 (PDT) Message-ID: <790a9fff05080816561c653e73@mail.gmail.com> Date: Mon, 8 Aug 2005 18:56:24 -0500 From: Scot Hetzel To: Randy Bush In-Reply-To: <17143.55126.928714.853442@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17143.55126.928714.853442@roam.psg.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 23:56:26 -0000 On 8/8/05, Randy Bush wrote: > at the make installworld step in the 4->5 upgrade sequence. >=20 > /usr/share/man/man3/item_value.3.gz -> /usr/share/man/man3/mitem_value.3.= gz > /usr/share/man/man3/set_item_value.3.gz -> /usr/share/man/man3/mitem_valu= e.3.gz > /usr/share/man/man3/item_visible.3.gz -> /usr/share/man/man3/mitem_visibl= e.3.gz > =3D=3D=3D> lib/libmilter > install -C -o root -g wheel -m 444 libmilter.a /usr/lib > install: libmilter.a: No such file or directory > *** Error code 71 >=20 > how can i get past this to get a clean enough system to be able to build > again? Did you do a 'make buildworld -DNO_SENDMAIL'? If you did, then you need to do a 'make installworld -DNO_SENDMAIL'. Scot --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 23:57:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D38ED16A41F for ; Mon, 8 Aug 2005 23:57:08 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4044043D64 for ; Mon, 8 Aug 2005 23:57:06 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E2HUQ-000KjC-Lf; Mon, 08 Aug 2005 23:57:06 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E2HUQ-0000ka-20; Mon, 08 Aug 2005 13:57:06 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17143.61777.552270.95710@roam.psg.com> Date: Mon, 8 Aug 2005 13:57:05 -1000 To: Scot Hetzel References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 23:57:09 -0000 > Did you do a 'make buildworld -DNO_SENDMAIL'? If you did, then you > need to do a 'make installworld -DNO_SENDMAIL'. NO_SENDMAIL is in /etc/make.conf From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 00:05:21 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4715116A41F for ; Tue, 9 Aug 2005 00:05:21 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF4D143D46 for ; Tue, 9 Aug 2005 00:05:20 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id i8so1098277wra for ; Mon, 08 Aug 2005 17:05:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tFXHlPAjmLx/pZgbzl7Cvyta8o7aRinSizS4189pZCvdaE6lcQnE6sJ20zfypjFoKM0CIpOMfS4y/xYoTKPfgYvZnHuv29Jp3wwZowyXtBeR6jYDimeExI9u3xpkeWbJd1eaq7kxFTSngjqgDqLTxhEBur+QQ1uKdwLv/g4g43A= Received: by 10.54.29.72 with SMTP id c72mr5135177wrc; Mon, 08 Aug 2005 17:05:20 -0700 (PDT) Received: by 10.54.29.26 with HTTP; Mon, 8 Aug 2005 17:05:20 -0700 (PDT) Message-ID: <790a9fff05080817054ff9e1d8@mail.gmail.com> Date: Mon, 8 Aug 2005 19:05:20 -0500 From: Scot Hetzel To: Randy Bush In-Reply-To: <17143.61777.552270.95710@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 00:05:21 -0000 On 8/8/05, Randy Bush wrote: > > Did you do a 'make buildworld -DNO_SENDMAIL'? If you did, then you > > need to do a 'make installworld -DNO_SENDMAIL'. >=20 > NO_SENDMAIL is in /etc/make.conf >=20 >=20 Hmm, then it shouldn't have even tried to install libmilter.a. Is the install system the same system as the build system? If they are not, then make sure the install system /etc/make.conf has NO_SENDMAIL defined. Check your src/lib/Makefile, it should have: .if !defined(NO_SENDMAIL) _libmilter=3D=09libmilter _libsm=3D=09=09libsm _libsmdb=3D=09libsmdb _libsmutil=3D=09libsmutil .endif which only builds, and installs the above libraries when NO_SENDMAIL is not defined. Scot --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 00:25:26 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA76916A41F; Tue, 9 Aug 2005 00:25:26 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF99843D49; Tue, 9 Aug 2005 00:25:25 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.89.24] (manz-d9b95918.pool.mediaWays.net [217.185.89.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 19F82300081E; Tue, 9 Aug 2005 02:25:19 +0200 (CEST) Message-ID: <42F7F7E8.1020507@mail.uni-mainz.de> Date: Tue, 09 Aug 2005 02:25:12 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Content-Type: multipart/mixed; boundary="------------080106050108050606000207" X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: Subject: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 00:25:26 -0000 This is a multi-part message in MIME format. --------------080106050108050606000207 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello. My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 boxed (see dmesg). One of my SATA disks, the SAMSUNG SP2004C seems to show errors during operation (and also showd under 5.4-RELEASE-p3). Sometimes I get this error: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 while the machine still keeps working. Other days the box crashes completely. Is this a operating system bug or is this message an evidence of defective hardware? By the way, DMA support is enabled: hw.ata.ata_dma: 1 hw.ata.atapi_dma: 1 Thanks in advance,\ Oliver --------------080106050108050606000207 Content-Type: text/plain; name="dmesg.out" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.out" Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-BETA2 #23: Sun Aug 7 23:32:03 UTC 2005 root@thor.schanze.de:/usr/backup/obj/usr/src/sys/THOR Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3500+ (2211.34-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 Features=0x78bfbff AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 2147418112 (2047 MB) avail memory = 2064375808 (1968 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard netsmb_dev: loaded acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR pci_link0: irq 10 on acpi0 pci_link1: on acpi0 pci_link2: irq 5 on acpi0 pci_link3: on acpi0 pci_link4: on acpi0 pci_link5: irq 5 on acpi0 pci_link6: on acpi0 pci_link7: irq 11 on acpi0 pci_link8: irq 3 on acpi0 pci_link9: on acpi0 pci_link10: irq 11 on acpi0 pci_link11: irq 3 on acpi0 pci_link12: on acpi0 pci_link13: irq 11 on acpi0 pci_link14: irq 10 on acpi0 pci_link15: on acpi0 pci_link16: irq 0 on acpi0 pci_link17: irq 0 on acpi0 pci_link18: irq 0 on acpi0 pci_link19: irq 0 on acpi0 pci_link20: irq 16 on acpi0 pci_link21: irq 0 on acpi0 pci_link22: irq 0 on acpi0 pci_link23: irq 0 on acpi0 pci_link24: irq 0 on acpi0 pci_link25: irq 0 on acpi0 pci_link26: irq 0 on acpi0 pci_link27: irq 0 on acpi0 pci_link28: irq 0 on acpi0 pci_link29: irq 0 on acpi0 pci_link30: irq 0 on acpi0 pci_link31: irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link26: BIOS IRQ 11 for -2145766612.1.INTA is invalid pci_link21: BIOS IRQ 5 for -2145766612.2.INTA is invalid pci_link27: BIOS IRQ 3 for -2145766612.2.INTB is invalid pci_link23: BIOS IRQ 11 for -2145766612.10.INTA is invalid pci_link24: BIOS IRQ 3 for -2145766612.4.INTA is invalid pci_link29: BIOS IRQ 11 for -2145766612.7.INTA is invalid pci_link30: BIOS IRQ 10 for -2145766612.8.INTA is invalid pci0: on pcib0 pci_link26: Unable to choose an IRQ pci_link21: Unable to choose an IRQ pci_link27: Unable to choose an IRQ pci_link24: Unable to choose an IRQ pci_link29: Unable to choose an IRQ pci_link30: Unable to choose an IRQ pci_link23: Unable to choose an IRQ pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 ichsmb0: port 0xe400-0xe41f,0x4c00-0x4c3f,0x4c40-0x4c7f irq 20 at device 1.1 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 ohci0: mem 0xd8104000-0xd8104fff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered pcm0: port 0xdc00-0xdcff,0xe000-0xe0ff mem 0xd8103000-0xd8103fff irq 23 at device 4.0 on pci0 pcm0: [GIANT-LOCKED] pcm0: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd8102000-0xd8102fff irq 21 at device 7.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd8101000-0xd8101fff irq 22 at device 8.0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib1: at device 9.0 on pci0 pci_link17: BIOS IRQ 21 for 0.7.INTA is invalid pci_link18: BIOS IRQ 22 for 0.8.INTA is invalid pci_link19: BIOS IRQ 23 for 0.10.INTA is invalid pci5: on pcib1 pci_link16: Unable to choose an IRQ fwohci0: mem 0xd8004000-0xd80047ff,0xd8000000-0xd8003fff irq 16 at device 11.0 on pci5 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:00:12:53:30 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) nve0: port 0xb000-0xb007 mem 0xd8100000-0xd8100fff irq 23 at device 10.0 on pci0 nve0: Ethernet address 00:11:d8:92:a3:15 miibus0: on nve0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:11:d8:92:a3:15 nve0: [GIANT-LOCKED] pcib2: at device 11.0 on pci0 pci4: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci2: on pcib4 pcib5: at device 14.0 on pci0 pci1: on pcib5 pci_link18: Unable to choose an IRQ pci1: at device 0.0 (no driver attached) acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sc0: at flags 0x100 on isa0 sc0: VGA <8 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0 at vga0 Timecounter "TSC" frequency 2211343498 Hz quality 800 Timecounters tick every 1.000 msec Fast IPsec: Initialized Security Association Processing. acd0: DVDR at ata0-master UDMA33 ad8: 194481MB at ata4-master SATA150 ad10: 190782MB at ata5-master SATA150 cd0 at ata0 bus 0 target 0 lun 0 cd0: <_NEC DVD_RW ND-3500AG 2.19> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [2295104 x 2048 byte records] GEOM_LABEL: Label for provider acd0 is iso9660/CDROM. Trying to mount root from ufs:/dev/ad8s1a pflog0: promiscuous mode enabled WARNING pid 525 (nasd): ioctl sign-extension ioctl ffffffffc0106924 ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 --------------080106050108050606000207-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 00:25:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A29F16A430 for ; Tue, 9 Aug 2005 00:25:38 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A40743D45 for ; Tue, 9 Aug 2005 00:25:37 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E2Hw1-000Lbx-2c; Tue, 09 Aug 2005 00:25:37 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E2Hw0-0000n8-9b; Mon, 08 Aug 2005 14:25:36 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17143.63487.787071.348531@roam.psg.com> Date: Mon, 8 Aug 2005 14:25:35 -1000 To: Scot Hetzel References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> <790a9fff05080817054ff9e1d8@mail.gmail.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 00:25:38 -0000 my error. i hacked /etc/make.conf between build and install. so i can use ed to unhack it, but when i try to install again -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /usr/src; /usr/obj/usr/src/make.i386/make -f Makefile.inc1 hierarchy cd /usr/src/etc; /usr/obj/usr/src/make.i386/make distrib-dirs mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / /usr/libexec/ld-elf.so.1: Shared object "libmd.so.2" not found, required by "mtr ee" From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 00:48:56 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 014D816A41F for ; Tue, 9 Aug 2005 00:48:56 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8392843D45 for ; Tue, 9 Aug 2005 00:48:55 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id i11so832338wra for ; Mon, 08 Aug 2005 17:48:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lGFOaLldUfj7aE6cHr6WAGtQNexF5lEltXQR45TkDAtTJvWGrBkobVZGwVR5YVg9A8uCYhqApzJUe3g2Rptgwy6Gq7flzxvM69/cHOaCvb1WrF8Jqo+Vkp4lrqtblBQbrju66M6KO7sCvx5aKuHnintk5rTiFZILutAV9kWlh1I= Received: by 10.54.49.48 with SMTP id w48mr5240778wrw; Mon, 08 Aug 2005 17:48:54 -0700 (PDT) Received: by 10.54.29.26 with HTTP; Mon, 8 Aug 2005 17:48:54 -0700 (PDT) Message-ID: <790a9fff05080817482a42256f@mail.gmail.com> Date: Mon, 8 Aug 2005 19:48:54 -0500 From: Scot Hetzel To: Randy Bush In-Reply-To: <17143.63487.787071.348531@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> <790a9fff05080817054ff9e1d8@mail.gmail.com> <17143.63487.787071.348531@roam.psg.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 00:48:56 -0000 On 8/8/05, Randy Bush wrote: > my error. i hacked /etc/make.conf between build and install. > so i can use ed to unhack it, but when i try to install again >=20 > -------------------------------------------------------------- > >>> Making hierarchy > -------------------------------------------------------------- > cd /usr/src; /usr/obj/usr/src/make.i386/make -f Makefile.inc1 hierarchy > cd /usr/src/etc; /usr/obj/usr/src/make.i386/make distrib-d= irs > mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / > /usr/libexec/ld-elf.so.1: Shared object "libmd.so.2" not found, required = by "mtr > ee" >=20 you may have to go into the src/lib/libmd and do a 'make install' from there. Or you may need to get the libmd.so.2 from a system with FreeBSD 4.x. Scot --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 01:03:02 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E02C016A41F for ; Tue, 9 Aug 2005 01:03:02 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id A58AC43D46 for ; Tue, 9 Aug 2005 01:03:02 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E2IWE-000Mqb-BS; Tue, 09 Aug 2005 01:03:02 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E2IWD-0000sl-O3; Mon, 08 Aug 2005 15:03:01 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17144.197.240197.415758@roam.psg.com> Date: Mon, 8 Aug 2005 15:03:01 -1000 To: Scot Hetzel References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> <790a9fff05080817054ff9e1d8@mail.gmail.com> <17143.63487.787071.348531@roam.psg.com> <790a9fff05080817482a42256f@mail.gmail.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 01:03:03 -0000 > you may have to go into the src/lib/libmd and do a 'make install' from > there. # pwd /usr/src # cd lib/libmd # make install install -C -o root -g wheel -m 444 libmd.a /usr/lib install -C -o root -g wheel -m 444 libmd_p.a /usr/lib install: libmd_p.a: No such file or directory *** Error code 71 > Or you may need to get the libmd.so.2 from a system with > FreeBSD 4.x. backups here i come randy From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 01:15:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73FAD16A41F for ; Tue, 9 Aug 2005 01:15:14 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 017AD43D45 for ; Tue, 9 Aug 2005 01:15:13 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so1134347wra for ; Mon, 08 Aug 2005 18:15:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cJWgTYH9fVobAUBBEdbEepbQyEjIUKcPD6dI1XF0uAqDJ6SRL2ZVXKL7AJ5IiYLKBjgiumdGlfuxYH5vkdmcpaVrBSt5SpB/y8D3aHcB40Zu6BrXpyqBphYNjvdfZqITvEBz+eNjtxXh0wSJeeSicAdV8n5VmWW3d/Mhvt+hkK8= Received: by 10.54.53.63 with SMTP id b63mr5069085wra; Mon, 08 Aug 2005 18:15:13 -0700 (PDT) Received: by 10.54.29.26 with HTTP; Mon, 8 Aug 2005 18:15:13 -0700 (PDT) Message-ID: <790a9fff050808181546df29ed@mail.gmail.com> Date: Mon, 8 Aug 2005 20:15:13 -0500 From: Scot Hetzel To: Randy Bush In-Reply-To: <17144.197.240197.415758@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> <790a9fff05080817054ff9e1d8@mail.gmail.com> <17143.63487.787071.348531@roam.psg.com> <790a9fff05080817482a42256f@mail.gmail.com> <17144.197.240197.415758@roam.psg.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 01:15:14 -0000 On 8/8/05, Randy Bush wrote: > > you may have to go into the src/lib/libmd and do a 'make install' from > > there. >=20 > # pwd > /usr/src > # cd lib/libmd > # make install > install -C -o root -g wheel -m 444 libmd.a /usr/lib > install -C -o root -g wheel -m 444 libmd_p.a /usr/lib > install: libmd_p.a: No such file or directory > *** Error code 71 >=20 Add NOPROFILE to get rid of the *_p.a libraries, and try again. Scot --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 02:27:23 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E75D16A41F for ; Tue, 9 Aug 2005 02:27:23 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD1E943D45 for ; Tue, 9 Aug 2005 02:27:22 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E2Jpp-000OuP-Lj; Tue, 09 Aug 2005 02:27:22 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E2Jpp-0000zT-2j; Mon, 08 Aug 2005 16:27:21 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17144.5256.577223.319732@roam.psg.com> Date: Mon, 8 Aug 2005 16:27:20 -1000 To: Scot Hetzel References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> <790a9fff05080817054ff9e1d8@mail.gmail.com> <17143.63487.787071.348531@roam.psg.com> <790a9fff05080817482a42256f@mail.gmail.com> <17144.197.240197.415758@roam.psg.com> <790a9fff050808181546df29ed@mail.gmail.com> Cc: FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 02:27:23 -0000 >> # pwd >> /usr/src >> # cd lib/libmd >> # make install >> install -C -o root -g wheel -m 444 libmd.a /usr/lib >> install -C -o root -g wheel -m 444 libmd_p.a /usr/lib >> install: libmd_p.a: No such file or directory >> *** Error code 71 >> > Add NOPROFILE to get rid of the *_p.a libraries, and try again. so, i could make install in that dir, see appended. but same error in /usr/src >>> Making hierarchy -------------------------------------------------------------- cd /usr/src; /usr/obj/usr/src/make.i386/make -f Makefile.inc1 hierarchy cd /usr/src/etc; /usr/obj/usr/src/make.i386/make distrib-dirs mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / /usr/libexec/ld-elf.so.1: Shared object "libmd.so.2" not found, required by "mtree" *** Error code 1 randy --- # make -DNOPROFILE install install -C -o root -g wheel -m 444 libmd.a /usr/lib install -s -o root -g wheel -m 444 libmd.so.2 /lib ln -fs libmd.so.2 /lib/libmd.so install -C -o root -g wheel -m 444 /usr/src/lib/libmd/md2.h /usr/src/lib/libmd/ md4.h /usr/src/lib/libmd/md5.h /usr/src/lib/libmd/ripemd.h /usr/src/lib/libmd/sh a.h /usr/src/lib/libmd/sha256.h /usr/include install -o root -g wheel -m 444 md2.3.gz /usr/share/man/man3 install -o root -g wheel -m 444 md4.3.gz /usr/share/man/man3 install -o root -g wheel -m 444 md5.3.gz /usr/share/man/man3 install -o root -g wheel -m 444 ripemd.3.gz /usr/share/man/man3 install -o root -g wheel -m 444 sha.3.gz /usr/share/man/man3 install -o root -g wheel -m 444 sha256.3.gz /usr/share/man/man3 /usr/share/man/man3/MD2Init.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2Update.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2Final.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2End.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2File.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2FileChunk.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD2Data.3.gz -> /usr/share/man/man3/md2.3.gz /usr/share/man/man3/MD4Init.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4Update.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4Final.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4End.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4File.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4FileChunk.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD4Data.3.gz -> /usr/share/man/man3/md4.3.gz /usr/share/man/man3/MD5Init.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Update.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Final.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5End.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5File.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5FileChunk.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/MD5Data.3.gz -> /usr/share/man/man3/md5.3.gz /usr/share/man/man3/RIPEMD160_Init.3.gz -> /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Update.3.gz -> /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Final.3.gz -> /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_Data.3.gz -> /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_End.3.gz -> /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_File.3.gz -> /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/RIPEMD160_FileChunk.3.gz -> /usr/share/man/man3/ripemd.3.gz /usr/share/man/man3/SHA_Init.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Update.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Final.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_End.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_File.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_FileChunk.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA_Data.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Init.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Update.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Final.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_End.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_File.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_FileChunk.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA1_Data.3.gz -> /usr/share/man/man3/sha.3.gz /usr/share/man/man3/SHA256_Init.3.gz -> /usr/share/man/man3/sha256.3.gz /usr/share/man/man3/SHA256_Update.3.gz -> /usr/share/man/man3/sha256.3.gz /usr/share/man/man3/SHA256_Final.3.gz -> /usr/share/man/man3/sha256.3.gz /usr/share/man/man3/SHA256_End.3.gz -> /usr/share/man/man3/sha256.3.gz /usr/share/man/man3/SHA256_File.3.gz -> /usr/share/man/man3/sha256.3.gz /usr/share/man/man3/SHA256_FileChunk.3.gz -> /usr/share/man/man3/sha256.3.gz /usr/share/man/man3/SHA256_Data.3.gz -> /usr/share/man/man3/sha256.3.gz From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 02:28:40 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6510416A41F for ; Tue, 9 Aug 2005 02:28:40 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.61]) by mx1.FreeBSD.org (Postfix) with SMTP id A1F2C43D45 for ; Tue, 9 Aug 2005 02:28:38 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 99899 invoked by uid 399); 9 Aug 2005 02:28:38 -0000 Received: from 69-175-228-47.vnnyca.adelphia.net (HELO ?192.168.1.101?) (dougb@dougbarton.net@69.175.228.47) by mail1.fluidhosting.com with SMTP; 9 Aug 2005 02:28:38 -0000 Message-ID: <42F814D2.5010901@FreeBSD.org> Date: Mon, 08 Aug 2005 19:28:34 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Randy Bush References: <17142.30598.428221.864901@roam.psg.com> In-Reply-To: <17142.30598.428221.864901@roam.psg.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: 4.11 to RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 02:28:40 -0000 Randy Bush wrote: > any peculiarities/clues for upgrading an antique from 4.11 to > RELENG_6 beyond the "To upgrade in-place from 5.x-stable to > current" in UPDATING? Back up important data, and do a clean install of 6. At minimum, by trying to upgrade in place you'll not get UFS2 partitions. And unless you've bumped the default partition sizes since you installed 4.x, you'll probably not be happy with life in a 6-stable world. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 03:28:25 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A92316A41F; Tue, 9 Aug 2005 03:28:25 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37E9843D46; Tue, 9 Aug 2005 03:28:24 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j793RSP0097686; Mon, 8 Aug 2005 23:27:28 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.3/8.13.3) with ESMTP id j793SMIF067229; Mon, 8 Aug 2005 23:28:22 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id j793SKSX026113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Aug 2005 23:28:21 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.1.2.0.20050808232304.03deb4b8@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Mon, 08 Aug 2005 23:30:28 -0400 To: "O. Hartmann" , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org From: Mike Tancsa In-Reply-To: <42F7F7E8.1020507@mail.uni-mainz.de> References: <42F7F7E8.1020507@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.51 on 64.7.153.26 Cc: Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 03:28:25 -0000 At 08:25 PM 08/08/2005, O. Hartmann wrote: >Hello. > >My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 boxed >(see dmesg). >One of my SATA disks, the SAMSUNG SP2004C seems to show errors during >operation (and also showd under 5.4-RELEASE-p3). >Sometimes I get this error: >ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 >while the machine still keeps working. >Other days the box crashes completely. > >Is this a operating system bug or is this message an evidence of defective >hardware? You can probably confirm a hardware issue with the smartmon tools. (/usr/ports/sysutils/smartmontools). It was quite handy the other day for us to narrow down a problem between a drive tray and the actual drive. We started to see Aug 3 02:02:49 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=391423 Aug 3 02:03:00 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2304319 Aug 3 02:03:10 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2312927 Aug 3 02:03:17 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2308639 Aug 3 02:03:26 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2309855 Aug 3 02:03:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=2348359 Aug 4 12:12:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1528639 Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=1530031 Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=1528639 Aug 4 12:13:04 verify1 kernel: ad0: FAILURE - READ_DMA timed out Aug 4 12:13:04 verify1 kernel: spec_getpages:(ad0s1a) I/O read failure: (error=5) bp 0xd630b4fc vp 0xc2640d68 Yet when we read the actual error info off the drive via smartctl -a ad0, it was clean. So it pointed to the drive tray which we swapped and all was well. In other situations however, the smart info will often tell you if the drive is starting to fail. Its not 100% reliable, but since we started using it, it generally gave us some sort of heads up as to whether or not a drive is in trouble. ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 03:40:30 2005 Return-Path: X-Original-To: FreeBSD-stable@FreeBSD.org Delivered-To: FreeBSD-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D43616A420 for ; Tue, 9 Aug 2005 03:40:30 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from vette.gigo.com (vette.gigo.com [216.218.228.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 373D443D49 for ; Tue, 9 Aug 2005 03:40:30 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from 201.24.48.30 (unknown [201.24.48.30]) by vette.gigo.com (Postfix) with ESMTP id 956DB546C for ; Mon, 8 Aug 2005 20:40:28 -0700 (PDT) Received: (qmail 63598 invoked from network); 9 Aug 2005 03:38:36 -0000 Received: from qmail by qscan (mail filter); 9 Aug 2005 03:38:14 +0000 Received: from unknown (HELO exxodus.fedaykin.here) (127.0.0.1) by exxodus.fedaykin.here with SMTP; 9 Aug 2005 03:38:36 -0000 Date: Tue, 09 Aug 2005 03:38:06 +0000 From: Mario Sergio Fujikawa Ferreira To: FreeBSD-stable@FreeBSD.org X-Mailer: Balsa 2.3.4 Message-Id: <1123558716l.19636l.0l@exxodus.fedaykin.here> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-BGKQrxbcY2nSwPwie/Tw" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: mldonkey kqueue patch (replace select/poll) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 03:40:30 -0000 --=-BGKQrxbcY2nSwPwie/Tw Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, mldonkey is a OCAML/GTK client for a number of peer-to-peer networks =20 including edonkey, overnet and kademlia. I just wrote a patch against ports/net/mldonkey-devel version 2.6.0 =20 to support kqueue(2) FreeBSD kernel event notification mechanism. It is =20 meant to replace select/poll inside mldonkey. kqueue scales better than select/poll not to mention that it should =20 be faster. I am having a little bit of trouble with this patch. mldonkey loads =20 and I am able to connect to the daemon through both the web interface =20 and kmldonkey. However, I am unable to connect to servers. I am pretty sure I am assuming something wrong about the interaction of the ml_fd_* C functions and mldonkey ocaml code. Are there any =20 takers to help me on this one? It should really improve performance =20 under FreeBSD and possibly other *BSD platforms. Regards, MSFF ps: Please, include on CC: replies since I am no longer subscribed to =20 this mailing list. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC+CU8rxEiaFLzGQwRAluiAJ90Ncly7vZSeL3sopjpDuZeC0YuBQCeLisH VWwvMSk0pD8ZwZKbTHUD9WA=3D =3D8XLv -----END PGP SIGNATURE----- --=-BGKQrxbcY2nSwPwie/Tw-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 05:33:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 148C616A41F for ; Tue, 9 Aug 2005 05:33:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DD2143D48 for ; Tue, 9 Aug 2005 05:33:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j795X2vf025885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Aug 2005 01:33:02 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j795Wx6P014177; Tue, 9 Aug 2005 01:32:59 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1883651333; Tue, 9 Aug 2005 01:32:59 -0400 (EDT) Date: Tue, 9 Aug 2005 01:32:58 -0400 From: Kris Kennaway To: "Jason C. Wells" Message-ID: <20050809053258.GA21061@xor.obsecurity.org> References: <41255F11A4AE1233ABAB094C@[10.254.254.253]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline In-Reply-To: <41255F11A4AE1233ABAB094C@[10.254.254.253]> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_6 kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 05:33:03 -0000 --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 06, 2005 at 12:06:39PM -0700, Jason C. Wells wrote: > While compiling bash for my new 6.0-BETA2 system, I received this error: >=20 > ad4: detached > panic: vm_fault >=20 > I don't have a dump for you and I really must be going to work now. Mor= e=20 > later if I can get myself trained up on crash dumps. See the chapter on kernel debugging in the developers' handbook. Kris --SUOF0GtieIMvvwua Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC+EAKWry0BWjoQKURAsWpAJ9V+/dNDKB7XDJFqZ1RYa9xUfWFZQCfWNuZ KH83AMkyHaXdDYTCtYqURB4= =8Zu/ -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 06:41:49 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B48416A41F for ; Tue, 9 Aug 2005 06:41:49 +0000 (GMT) (envelope-from uzi@bmby.com) Received: from dev.bmby.co.il (l192-114-46-204.broadband.actcom.net.il [192.114.46.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46EFA43D45 for ; Tue, 9 Aug 2005 06:41:47 +0000 (GMT) (envelope-from uzi@bmby.com) Received: from [192.168.0.2] ([192.168.0.2]) by dev.bmby.co.il (8.12.9/8.12.9) with ESMTP id j796fnPS012906; Tue, 9 Aug 2005 09:41:54 +0300 Message-ID: <42F85DFA.6040609@bmby.com> Date: Tue, 09 Aug 2005 09:40:42 +0200 From: Uzi Klein Organization: B.M.B.Y Software Systems Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brad Miele References: <20050808082509.V714@localhost> In-Reply-To: <20050808082509.V714@localhost> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070401010201030708050402" Cc: stable@freebsd.org Subject: Re: bge watchdog errors in -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 06:41:49 -0000 This is a cryptographically signed message in MIME format. --------------ms070401010201030708050402 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Brad Miele wrote: > Hi, > > Last week, i cvsupped two HP Proliant DL380 G4 machines to the most > recent stable, which replaced the bge driver from mid may with the one > committed on or around June 24. Since updating, my cards, Broadcom > BCM5704C have been throwing occasional watchdog timeout errors on their > shared 1000basetx net. These errors do not currently seem to be > effecting much, and there have only been 6 since last friday, but I > would like to clear them up. I'm experiencing the same issue with the exact same hardware ever since 5.4-RELEASE-p3, with no "real" affection. > > I noted that the current version of the bge driver had code backed out > from the previous one, and an option "BGE_FAKE_AUTONEG" was added. I > have tried enabling this option, as it seems to pertain to this chipset, > but the errors are still occuring. I am thinking of switching the cards > from autoselect to explicit 1000basetx, with one of them set to link0. > > Please confirm that this is a reasonable next step and let me know any > other information that will be useful. > > Regards, > > Brad > ------------------------------------------------------------ > Brad Miele > Technology Director > IPNStock > (866) 476-7862 x902 > bmiele@ipnstock.com > -- Uzi Klein Software Development Executive B.M.B.Y Software Systems Ltd. --------------ms070401010201030708050402 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIHzTCC AkEwggGqoAMCAQICAw8T9jANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDUwNzA1MTUwNTQ3WhcNMDYwNzA1MTUwNTQ3 WjA+MR8wHQYDVQQDExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMRswGQYJKoZIhvcNAQkBFgx1 emlAYm1ieS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAM/hjHCQv3zDBkfXTm8o k6hGvfoKzjQJUEgDBgrzd8PNmYvp4uYCPDaisap1a9paS0Tc32YN+HASs7BsKBjfvtLSKa0m 1aERkUCrxTDFiC8QDgXJ3b+V2MPcrulkKsZ0+kQM3/kLCAEhYJ5bhX0vHFBsCrDgH0fx4rkd E4MSLJHnAgMBAAGjKTAnMBcGA1UdEQQQMA6BDHV6aUBibWJ5LmNvbTAMBgNVHRMBAf8EAjAA MA0GCSqGSIb3DQEBBAUAA4GBAE+tVNP9WuPEjpG85/75Av1CAuo+BQRvU0vGvEjuL0LPVSGd +/2gL+l3yc7dlksptdQpAhb89wph+EHvah7I3roie6s3IkgA9GTl93EJtMWfmVy+qiGcaEH3 pE17rK5/1Lwau4TwsytYFfQdN4DAxaZT9k2lvml8a49bzBfUO4RXMIICQTCCAaqgAwIBAgID DxP2MA0GCSqGSIb3DQEBBAUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQTAeFw0wNTA3MDUxNTA1NDdaFw0wNjA3MDUxNTA1NDdaMD4xHzAdBgNVBAMT FlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxGzAZBgkqhkiG9w0BCQEWDHV6aUBibWJ5LmNvbTCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAz+GMcJC/fMMGR9dObyiTqEa9+grONAlQSAMG CvN3w82Zi+ni5gI8NqKxqnVr2lpLRNzfZg34cBKzsGwoGN++0tIprSbVoRGRQKvFMMWILxAO Bcndv5XYw9yu6WQqxnT6RAzf+QsIASFgnluFfS8cUGwKsOAfR/HiuR0TgxIskecCAwEAAaMp MCcwFwYDVR0RBBAwDoEMdXppQGJtYnkuY29tMAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEE BQADgYEAT61U0/1a48SOkbzn/vkC/UIC6j4FBG9TS8a8SO4vQs9VIZ37/aAv6XfJzt2WSym1 1CkCFvz3CmH4Qe9qHsjeuiJ7qzciSAD0ZOX3cQm0xZ+ZXL6qIZxoQfekTXusrn/UvBq7hPCz K1gV9B03gMDFplP2TaW+aXxrj1vMF9Q7hFcwggM/MIICqKADAgECAgENMA0GCSqGSIb3DQEB BQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlD YXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZp Y2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20w HhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSm PFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO 3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSF D0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNV HR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVl bWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZh dGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FD lpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRix9sncVcl jd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VPMYIC ujCCArYCAQEwaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3Vpbmcg Q0ECAw8T9jAJBgUrDgMCGgUAoIIBpzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqG SIb3DQEJBTEPFw0wNTA4MDkwNzQwNDJaMCMGCSqGSIb3DQEJBDEWBBTI1Mdiq36SpNE5KEc/ BBhcLKitKDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDAN BggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB4BgkrBgEEAYI3EAQxazBp MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIDDxP2MHoG CyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1 bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElz c3VpbmcgQ0ECAw8T9jANBgkqhkiG9w0BAQEFAASBgKTvoCezSs0dceVlRy3/yjfSErLlLZIJ F2L3uLe+HKS50M7CNm/dfoV3cCZJrvjsT0NN8kZ9LAoYdkNetQZQ1Y7kAZOZQNsvTAA+pAVy 61VFg0+nVUeMX+6GZcWGaqDBRTdtb16tRS2FlBlmCctjCdWAPR5Z1wOxJ2FLIZYXCt9LAAAA AAAA --------------ms070401010201030708050402-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 08:23:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3F1416A41F; Tue, 9 Aug 2005 08:23:35 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E52A43D48; Tue, 9 Aug 2005 08:23:35 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id F1B613000C5F; Tue, 9 Aug 2005 10:23:33 +0200 (CEST) Message-ID: <42F86816.6070706@mail.uni-mainz.de> Date: Tue, 09 Aug 2005 10:23:50 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050722) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Tancsa References: <42F7F7E8.1020507@mail.uni-mainz.de> <6.2.1.2.0.20050808232304.03deb4b8@64.7.153.2> In-Reply-To: <6.2.1.2.0.20050808232304.03deb4b8@64.7.153.2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 08:23:36 -0000 Mike Tancsa wrote: > At 08:25 PM 08/08/2005, O. Hartmann wrote: > >> Hello. >> >> My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 >> boxed (see dmesg). >> One of my SATA disks, the SAMSUNG SP2004C seems to show errors during >> operation (and also showd under 5.4-RELEASE-p3). >> Sometimes I get this error: >> ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 >> while the machine still keeps working. >> Other days the box crashes completely. >> >> Is this a operating system bug or is this message an evidence of >> defective hardware? > > > You can probably confirm a hardware issue with the smartmon tools. > (/usr/ports/sysutils/smartmontools). > > It was quite handy the other day for us to narrow down a problem between > a drive tray and the actual drive. We started to see > > Aug 3 02:02:49 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=391423 > Aug 3 02:03:00 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=2304319 > Aug 3 02:03:10 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=2312927 > Aug 3 02:03:17 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=2308639 > Aug 3 02:03:26 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=2309855 > Aug 3 02:03:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=2348359 > Aug 4 12:12:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=1528639 > Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 > retries left) LBA=1530031 > Aug 4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (1 > retry left) LBA=1528639 > Aug 4 12:13:04 verify1 kernel: ad0: FAILURE - READ_DMA timed out > Aug 4 12:13:04 verify1 kernel: spec_getpages:(ad0s1a) I/O read failure: > (error=5) bp 0xd630b4fc vp 0xc2640d68 > > Yet when we read the actual error info off the drive via smartctl -a > ad0, it was clean. So it pointed to the drive tray which we swapped and > all was well. In other situations however, the smart info will often > tell you if the drive is starting to fail. Its not 100% reliable, but > since we started using it, it generally gave us some sort of heads up as > to whether or not a drive is in trouble. > > > ---Mike Dear Mike. Thanks a lot for this info. I will use this tool and try to report what I found out. I also use trays for my drives (like I did with SCSI and SCA2 on our servers at the lab). Maybe this could be an issue. Oliver From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 08:57:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5A2116A41F for ; Tue, 9 Aug 2005 08:57:08 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from raven.kierun.org (raven.yorksj.ac.uk [193.61.234.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F09F43D45 for ; Tue, 9 Aug 2005 08:57:07 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from yann by raven.kierun.org with local (Exim 4.52 (FreeBSD)) id 1E2Puy-000Cxu-7O for stable@freebsd.org; Tue, 09 Aug 2005 09:57:04 +0100 Date: Tue, 9 Aug 2005 09:57:04 +0100 From: Yann Golanski To: stable@freebsd.org Message-ID: <20050809085704.GA49451@kierun.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Fba/0zbH8Xs+Fj9o" Content-Disposition: inline User-Agent: Mutt/1.5.9i Sender: "Yann Golanski, University of York, +44(0)1904-433088" Cc: Subject: Xorg, Radeon X800PRO problem. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 08:57:09 -0000 --Fba/0zbH8Xs+Fj9o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I am stuck on getting this graphics card working with stable. Attached are xorg.conf and Xorg.log.0. The versions are: # uname -a FreeBSD rubicon.york.ac.uk 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Aug 8 16:18:46 BST 2005 root@rubicon.york.ac.uk:/usr/obj/usr/src/sys/SMP i386 # pkg_info -Ia | grep xorg xorg-6.8.2 X.Org distribution metaport Any help would be most welcome. -- yann@kierun.org -=*=- www.kierun.org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 --Fba/0zbH8Xs+Fj9o Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="xorg.conf" Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/TTF/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/webfonts/" FontPath "/usr/X11R6/lib/X11/fonts/freefont" FontPath "/usr/X11R6/lib/X11/fonts/local" FontPath "/usr/home/yann/.fonts/proggy" EndSection Section "Module" Load "dbe" Load "dri" load "extmod" Load "glx" Load "record" Load "xtrap" Load "freetype" Load "speedo" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbLayout" "gb" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5" option "Buttons" "6" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Sony" ModelName "LCD" HorizSync 28.0 - 80.0 VertRefresh 48.0 - 75.0 EndSection Section "Device" Identifier "Card0" Driver "ati" #VendorName "ATI Technologies Inc" #BoardName "Radeon X800PRO" #BusID "PCI:5:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 8 #SubSection "Display" # Depth 1 #EndSubSection #SubSection "Display" # Depth 4 #EndSubSection SubSection "Display" Depth 8 Modes "800x600" EndSubSection SubSection "Display" Depth 15 Modes "1152x764" EndSubSection SubSection "Display" Depth 16 Modes "1152x764" EndSubSection SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection EndSection --Fba/0zbH8Xs+Fj9o Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="Xorg.0.log" Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.7 Build Operating System: FreeBSD 5.3 i386 [ELF] Current Operating System: FreeBSD rubicon.york.ac.uk 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Aug 8 16:18:46 BST 2005 root@rubicon.york.ac.uk:/usr/obj/usr/src/sys/SMP i386 Build Date: 16 October 2004 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 8 09:49:51 2005 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "XkbLayout" "gb" (**) XKB: layout: "gb" (==) Keyboard: CustomKeycode disabled (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/Speedo/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/Speedo/"). (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/CID/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/CID/"). (WW) The directory "/usr/X11R6/lib/X11/fonts/webfonts/" does not exist. Entry deleted from font path. (WW) The directory "/usr/X11R6/lib/X11/fonts/freefont" does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local"). (WW) The directory "/usr/home/yann/.fonts/proggy" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:06:0: chip 1022,7460 card 0000,0000 rev 07 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1022,7468 card 1022,7468 rev 05 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1022,7469 card 1022,7469 rev 03 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1022,746a card 1022,746a rev 02 class 0c,05,00 hdr 00 (II) PCI: 00:07:3: chip 1022,746b card 1022,746b rev 05 class 06,80,00 hdr 00 (II) PCI: 00:07:5: chip 1022,746d card 10f1,2885 rev 03 class 04,01,00 hdr 00 (II) PCI: 00:0a:0: chip 1022,7450 card 0000,0000 rev 12 class 06,04,00 hdr 81 (II) PCI: 00:0a:1: chip 1022,7451 card 1022,36c0 rev 01 class 08,00,10 hdr 00 (II) PCI: 00:0b:0: chip 1022,7450 card 0000,0000 rev 12 class 06,04,00 hdr 81 (II) PCI: 00:0b:1: chip 1022,7451 card 1022,36c0 rev 01 class 08,00,10 hdr 00 (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:19:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:19:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:19:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:19:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 02:09:0: chip 14e4,16a7 card 10f1,2885 rev 02 class 02,00,00 hdr 00 (II) PCI: 03:00:0: chip 1022,7464 card 1022,7464 rev 0b class 0c,03,10 hdr 80 (II) PCI: 03:00:1: chip 1022,7464 card 1022,7464 rev 0b class 0c,03,10 hdr 00 (II) PCI: 03:0b:0: chip 1095,3114 card 1095,3114 rev 02 class 01,80,00 hdr 00 (II) PCI: 03:0c:0: chip 104c,8023 card 10f1,2885 rev 00 class 0c,00,10 hdr 00 (II) PCI: 04:00:0: chip 1022,7454 card 1022,7454 rev 14 class 06,00,00 hdr 00 (II) PCI: 04:01:0: chip 1022,7455 card 0000,0000 rev 14 class 06,04,00 hdr 01 (II) PCI: 05:00:0: chip 1002,4a49 card 1002,0002 rev 00 class 03,00,00 hdr 80 (II) PCI: 05:00:1: chip 1002,4a69 card 1002,0003 rev 00 class 03,80,00 hdr 00 (II) PCI: End of PCI scan (II) PCI-to-PCI bridge: (II) Bus 3: bridge is at (0:6:0), (0,3,3), BCTRL: 0x0006 (VGA_EN is cleared) (II) Bus 3 I/O range: [0] -1 0 0x00009000 - 0x000090ff (0x100) IX[B] [1] -1 0 0x00009400 - 0x000094ff (0x100) IX[B] [2] -1 0 0x00009800 - 0x000098ff (0x100) IX[B] [3] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B] [4] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B] [5] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B] [6] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B] [7] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B] (II) Bus 3 non-prefetchable memory range: [0] -1 0 0xff200000 - 0xff3fffff (0x200000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:10:0), (0,2,2), BCTRL: 0x0005 (VGA_EN is cleared) (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xff100000 - 0xff1fffff (0x100000) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xce900000 - 0xce9fffff (0x100000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:11:0), (0,1,1), BCTRL: 0x0005 (VGA_EN is cleared) (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:24:0), (0,0,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:24:1), (-1,-1,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:24:2), (-1,-1,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:24:3), (-1,-1,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:25:0), (-1,-1,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:25:1), (-1,-1,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:25:2), (-1,-1,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:25:3), (-1,-1,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Host-to-PCI bridge: (II) Bus 4: bridge is at (4:0:0), (4,4,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 4 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 4 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 4 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 5: bridge is at (4:1:0), (4,5,5), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 5 I/O range: [0] -1 0 0x0000c000 - 0x0000cfff (0x1000) IX[B] (II) Bus 5 non-prefetchable memory range: [0] -1 0 0xff500000 - 0xff5fffff (0x100000) MX[B] (II) Bus 5 prefetchable memory range: [0] -1 0 0xceb00000 - 0xeeafffff (0x20000000) MX[B] (--) PCI:*(5:0:0) ATI Technologies Inc unknown chipset (0x4a49) rev 0, Mem @ 0xe0000000/27, 0xff5f0000/16, I/O @ 0xc800/8, BIOS @ 0xff5c0000/17 (--) PCI: (5:0:1) ATI Technologies Inc unknown chipset (0x4a69) rev 0, Mem @ 0xd8000000/27, 0xff5e0000/16 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xf0000000 from 0xffffffff to 0xefffffff (II) Active PCI resource ranges: [0] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]EO [1] -1 0 0xff3f8000 - 0xff3fffff (0x8000) MX[B]E [2] -1 0 0xff3ff000 - 0xff3fffff (0x1000) MX[B]E [3] -1 0 0xff3ffc00 - 0xff3fffff (0x400) MX[B]E [4] -1 0 0xff3fe000 - 0xff3fffff (0x2000) MX[B]E [5] -1 0 0xff3fd000 - 0xff3fdfff (0x1000) MX[B]E [6] -1 0 0xff1f0000 - 0xff1fffff (0x10000) MX[B]E [7] -1 0 0xff4ff000 - 0xff4fffff (0x1000) MX[B]E [8] -1 0 0xff4fe000 - 0xff4fffff (0x2000) MX[B]E [9] -1 0 0xff5e0000 - 0xff5effff (0x10000) MX[B](B) [10] -1 0 0xd8000000 - 0xdfffffff (0x8000000) MX[B](B) [11] -1 0 0xff5c0000 - 0xff5dffff (0x20000) MX[B](B) [12] -1 0 0xff5f0000 - 0xff5fffff (0x10000) MX[B](B) [13] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [14] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B]E [15] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]E [16] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]E [17] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]E [18] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]E [19] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [20] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]E [21] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]E [22] -1 0 0x0000ffa0 - 0x0000ffbf (0x20) IX[B]E [23] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[B](B) (II) PCI Memory resource overlap reduced 0xff3f8000 from 0xff3fffff to 0xff3fbfff (II) PCI Memory resource overlap reduced 0xff3ff000 from 0xff3fffff to 0xff3ff7ff (II) PCI Memory resource overlap reduced 0xff3fe000 from 0xff3fffff to 0xff3fefff (II) PCI Memory resource overlap reduced 0xff4fe000 from 0xff4fffff to 0xff4fefff (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]EO [1] -1 0 0xff3f8000 - 0xff3fbfff (0x4000) MX[B]E [2] -1 0 0xff3ff000 - 0xff3ff7ff (0x800) MX[B]E [3] -1 0 0xff3ffc00 - 0xff3fffff (0x400) MX[B]E [4] -1 0 0xff3fe000 - 0xff3fefff (0x1000) MX[B]E [5] -1 0 0xff3fd000 - 0xff3fdfff (0x1000) MX[B]E [6] -1 0 0xff1f0000 - 0xff1fffff (0x10000) MX[B]E [7] -1 0 0xff4ff000 - 0xff4fffff (0x1000) MX[B]E [8] -1 0 0xff4fe000 - 0xff4fefff (0x1000) MX[B]E [9] -1 0 0xff5e0000 - 0xff5effff (0x10000) MX[B](B) [10] -1 0 0xd8000000 - 0xdfffffff (0x8000000) MX[B](B) [11] -1 0 0xff5c0000 - 0xff5dffff (0x20000) MX[B](B) [12] -1 0 0xff5f0000 - 0xff5fffff (0x10000) MX[B](B) [13] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [14] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B]E [15] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]E [16] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]E [17] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]E [18] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]E [19] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [20] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]E [21] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]E [22] -1 0 0x0000ffa0 - 0x0000ffbf (0x20) IX[B]E [23] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]EO [6] -1 0 0xff3f8000 - 0xff3fbfff (0x4000) MX[B]E [7] -1 0 0xff3ff000 - 0xff3ff7ff (0x800) MX[B]E [8] -1 0 0xff3ffc00 - 0xff3fffff (0x400) MX[B]E [9] -1 0 0xff3fe000 - 0xff3fefff (0x1000) MX[B]E [10] -1 0 0xff3fd000 - 0xff3fdfff (0x1000) MX[B]E [11] -1 0 0xff1f0000 - 0xff1fffff (0x10000) MX[B]E [12] -1 0 0xff4ff000 - 0xff4fffff (0x1000) MX[B]E [13] -1 0 0xff4fe000 - 0xff4fefff (0x1000) MX[B]E [14] -1 0 0xff5e0000 - 0xff5effff (0x10000) MX[B](B) [15] -1 0 0xd8000000 - 0xdfffffff (0x8000000) MX[B](B) [16] -1 0 0xff5c0000 - 0xff5dffff (0x20000) MX[B](B) [17] -1 0 0xff5f0000 - 0xff5fffff (0x10000) MX[B](B) [18] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B) [19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [21] -1 0 0x00009c00 - 0x00009cff (0x100) IX[B]E [22] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[B]E [23] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[B]E [24] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[B]E [25] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[B]E [26] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [27] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]E [28] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]E [29] -1 0 0x0000ffa0 - 0x0000ffbf (0x20) IX[B]E [30] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[B](B) (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/freebsd/libdrm.a (II) Module drm: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension FontCache (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension RECORD (II) LoadModule: "xtrap" (II) Loading /usr/X11R6/lib/modules/extensions/libxtrap.a (II) Module xtrap: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension DEC-XTRAP (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 6.7.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font FreeType (II) LoadModule: "speedo" (II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a (II) Module speedo: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.1 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Speedo (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "ati" (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor="X.Org Foundation" compiled for 6.7.0, module version = 6.5.6 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) ATI: ATI driver (version 6.5.6) for chipsets: ati, ativga (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP), ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP), ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP), ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI), ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP), ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP), ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP), ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP), ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP), ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI), ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI), ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP), ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP), ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP), ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI), ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP), ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP), ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP), ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP), ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP), ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP), ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?), ATI Rage 128 Pro ULTRA TU (AGP?) (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI), ATI Radeon Mobility M7 LW (AGP), ATI Mobility FireGL 7800 M7 LX (AGP), ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP), ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon IGP330M/340M/350M (U2) 4337, ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437, ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP), ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI), ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI), ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP), ATI Radeon Mobility 9000 (M9) Lf (AGP), ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9100 IGP (A5) 5834, ATI Radeon Mobility 9100 IGP (U3) 5835, ATI Radeon 9200PRO 5960 (AGP), ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP), ATI Radeon Mobility 9200 (M9+) 5C61 (AGP), ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP), ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP), ATI FireGL X1 NG (AGP), ATI Radeon 9600 AP (AGP), ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP), ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI FireGL RV360 AV (AGP), ATI Radeon Mobility 9600 (M10) NP (AGP), ATI Radeon Mobility 9600 (M10) NQ (AGP), ATI Radeon Mobility 9600 (M11) NR (AGP), ATI Radeon Mobility 9600 (M10) NS (AGP), ATI FireGL Mobility T2 (M10) NT (AGP), ATI FireGL Mobility T2 (M11) NV (AGP), ATI Radeon 9800SE AH (AGP), ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP), ATI FireGL X2 AK (AGP), ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP) (II) Primary Device is: PCI 05:00:0 (II) ATI: Candidate "Device" section "Card0". (--) Assigning device section with no busID to primary device (WW) RADEON: No matching Device section for instance (BusID PCI:5:0:1) found (EE) No devices detected. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. --Fba/0zbH8Xs+Fj9o-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 09:02:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45CB816A41F for ; Tue, 9 Aug 2005 09:02:59 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66A1D43D48 for ; Tue, 9 Aug 2005 09:02:58 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail10.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j7992sRq026292 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 9 Aug 2005 19:02:55 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id j7992sSR012200; Tue, 9 Aug 2005 19:02:54 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j7992qXj012199; Tue, 9 Aug 2005 19:02:52 +1000 (EST) (envelope-from pjeremy) Date: Tue, 9 Aug 2005 19:02:52 +1000 From: Peter Jeremy To: Randy Bush Message-ID: <20050809090252.GE9970@cirb503493.alcatel.com.au> References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> <790a9fff05080817054ff9e1d8@mail.gmail.com> <17143.63487.787071.348531@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17143.63487.787071.348531@roam.psg.com> User-Agent: Mutt/1.4.2i Cc: Scot Hetzel , FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 09:02:59 -0000 On Mon, 2005-Aug-08 14:25:35 -1000, Randy Bush wrote: >my error. i hacked /etc/make.conf between build and install. >so i can use ed to unhack it, but when i try to install again > >-------------------------------------------------------------- >>>> Making hierarchy >-------------------------------------------------------------- >cd /usr/src; /usr/obj/usr/src/make.i386/make -f Makefile.inc1 hierarchy >cd /usr/src/etc; /usr/obj/usr/src/make.i386/make distrib-dirs >mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / >/usr/libexec/ld-elf.so.1: Shared object "libmd.so.2" not found, required by "mtree" Apart from the other suggested solutions: At the beginning of the installworld, make stashes a selection of utilities (including mtree) into a temporary directory (${INSTALLTMP} in Makefile.inc1). The exact name varies but is something like /tmp/install.XXXXXXXX If you haven't lost the directory from the first installworld, you can always copy mtree (any any other over-written utilities) back where they started. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 09:35:34 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3690F16A41F; Tue, 9 Aug 2005 09:35:34 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3E0343D45; Tue, 9 Aug 2005 09:35:33 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1E2QW9-0001nZ-00; Tue, 09 Aug 2005 11:35:29 +0200 Date: Tue, 9 Aug 2005 11:35:29 +0200 To: Tijl Coosemans Message-ID: <20050809093529.GG852@poupinou.org> References: <200508020022.02992.tijl@ulyssis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200508020022.02992.tijl@ulyssis.org> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: acpi@FreeBSD.org, freebsd-stable@freebsd.org Subject: Re: 5-STABLE cpufreq hotter than est from ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 09:35:34 -0000 On Tue, Aug 02, 2005 at 12:22:02AM +0200, Tijl Coosemans wrote: > A couple days ago I updated my system and was excited to see cpufreq > and powerd in 5-stable. Since then however I noticed that my laptop > temperature is about 5°C higher than with est and estctrl. I found that > cpufreq when setting 200MHz for example set the absolute frequency to > 1600MHz (max for this laptop) and the relative frequency (p4tcc) to > 12.5% instead of using a more power conserving setting like 800MHz/25%. > > The problem is that cpufreq_expand_set() (sys/kern/kern_cpu.c) > traverses freq levels from high to low when adding relative levels and > skips duplicates. When it wants to add 800MHz/25% it sees this setting > as a duplicate of 1600MHz/12.5% it has found before. This can be fixed > by letting cpufreq_expand_set() traverse freq levels in reverse order > (and still skipping duplicates). Then each frequency level has the > lowest possible absolute setting. This is a one line change in > sys/kern/kern_cpu.c (line 653). It's a well known bug. Someday I think I will have enough time to fix that one if Nate don't bite me. > With this patch temperature is almost as low as with est again (only > 1°C hotter). However, there are still such levels like 1400/12.5 > (175MHz) which are lower than let's say 600/37.5 (225MHz), but consume > a lot more power. On my laptop this problem doesn't really occur > because of the way powerd works, only the absolute levels 1600, 800 and > 600 are ever used. I can imagine somebody with a 1700MHz cpu not being > so lucky though. So, I've worked out a patch (attached) that makes sure > that a lower frequency level has at most the same absolute setting > (preferably less of course). This eliminates quite a few levels so > somebody with a better knowledge of cpufreq should check if this patch > really does something good. This is the first time I've taken a look at > FreeBSD source code by the way. It's in my todo list in a so long time that I must admit I must be blamed to have not fixed that already. > Also, somewhat related, the p4tcc driver doesn't recognise > acpi_throttle, which means that when you load the cpufreq module after > booting, the freq levels are messed up. I'm not sure what the best > solution for this is. Let p4tcc detect acpi_throttle and don't attach > if it's present (like acpi_throttle does now if it finds p4tcc) or > detach it before attaching? Or maybe p4tcc and acpi_throttle should be > merged into one driver? > > Finally, is the kernel config option CPU_ENABLE_TCC still relevant? > Because it's still listed in NOTES. Right. I forgot to kill that option. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 10:27:43 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 424D016A41F for ; Tue, 9 Aug 2005 10:27:43 +0000 (GMT) (envelope-from mail@mm-bounce4.metarewardmail.com) Received: from mm-bounce4.metarewardmail.com (mm-bounce4.metarewardmail.com [66.110.182.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B63E43D5A for ; Tue, 9 Aug 2005 10:27:41 +0000 (GMT) (envelope-from mail@mm-bounce4.metarewardmail.com) Received: from mm-bounce4.metarewardmail.com (mm-bounce4 [127.0.0.1] (may be forged)) by mm-bounce4.metarewardmail.com (8.12.11/8.11.6) with ESMTP id j79ARfBx030484 for ; Tue, 9 Aug 2005 03:27:41 -0700 Received: (from mail@localhost) by mm-bounce4.metarewardmail.com (8.12.11/8.12.11/Submit) id j79ARe6a030481; Tue, 9 Aug 2005 03:27:40 -0700 Date: Tue, 9 Aug 2005 03:27:40 -0700 Message-Id: <200508091027.j79ARe6a030481@mm-bounce4.metarewardmail.com> To: freebsd-stable@freebsd.org References: <200508091027.j79ARSjA030363@mm-bounce4.metarewardmail.com> In-Reply-To: <200508091027.j79ARSjA030363@mm-bounce4.metarewardmail.com> X-Loop: flipmail@netflipmail.com From: Flipmail Subject: Re: Returned mail: see transcript for details X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Flipmail List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 10:27:43 -0000 Dear Member, Thank you for your interest in our offer. Unfortunately your inquiry was not received. We are very interested in hearing from you. If you would like to contact our Member Services Team, please go to www.netflip.com and click the Contact Us link. We will respond to your inquiry within 48 hours. We look forward to working with you towards our goal for 100% customer satisfaction. Regards, Member Services Team www.netflip.com From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 10:27:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21BB216A41F for ; Tue, 9 Aug 2005 10:27:45 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED62543D62 for ; Tue, 9 Aug 2005 10:27:40 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (DialupBdg253-240.centrin.net.id [202.146.253.240]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id j79ARFVi085489 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 9 Aug 2005 19:57:34 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 9 Aug 2005 17:26:48 +0700 User-Agent: KMail/1.8.1 MIME-Version: 1.0 Message-Id: <200508091726.55805.doconnor@gsoft.com.au> Content-Type: multipart/signed; boundary="nextPart6462642.tQgiqJT8v9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.05 () FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Subject: Firewire oddity.. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 10:27:45 -0000 --nextPart6462642.tQgiqJT8v9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I got the following while trying to rsync a large number of files over=20 the network to a firewire HD (FAT32 FS) on a 6.0-BETA1 system. Aug 9 12:48:17 inchoate kernel: firewire0: split transaction timeout dst= =3D0xffc0 tl=3D0x36 state=3D3 Aug 9 12:48:17 inchoate kernel: sbp_orb_pointer_callback: xfer->resp =3D 60 Aug 9 12:48:17 inchoate kernel: fw_rcv: unknown response WRES(2) src=3D0xf= fc0 tl=3D0x36 rt=3D1 data=3D0x84513864 Aug 9 12:48:17 inchoate kernel: try ad-hoc work around!! Aug 9 12:48:17 inchoate kernel: no use... Aug 9 12:48:19 inchoate kernel: firewire0: split transaction timeout dst= =3D0xffc0 tl=3D0x8 state=3D3 Aug 9 12:48:19 inchoate kernel: sbp_orb_pointer_callback: xfer->resp =3D 60 Aug 9 12:48:19 inchoate kernel: fw_rcv: unknown response WRES(2) src=3D0xf= fc0 tl=3D0x8 rt=3D1 data=3D0x84518aad Aug 9 12:48:19 inchoate kernel: try ad-hoc work around!! Aug 9 12:48:19 inchoate kernel: no use... da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Simplified Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) My interactive performance has gone down the tube too :( here is a systat -vmstat snapshot 2 users Load 13.14 7.58 4.75 Aug 9 16:06 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 273168 43380 749572 105288 20760 count 1 All 497356 51660 17265484 156920 pages 2 zfod Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt cow 1514 total 1 1134 1505 44 2374 2005 240 1 69176 wire 1007 0: clk 273368 act 1: at= kb 92.4%Sys 1.5%Intr 2.3%User 0.0%Nice 3.8%Idl 137800 inact 3: si= o1 | | | | | | | | | | 19780 cache 4: si= o0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+> 980 = free 7: ppc0 daefr 129 8: rtc Namei Name-cache Dir-cache prcfr 9: pc= m0 Calls hits % hits % react 350 11: n= vi 2276 2189 96 pdwak 12: p= sm pdpgs 13: n= px Disks ad0 da0 cd0 pass0 pass1 1 intrn 28 14: a= ta KB/t 4.07 4.00 0.00 0.00 0.00 61024 buf 15: a= ta tps 28 70 0 0 0 268 dirtybuf MB/s 0.11 0.27 0.00 0.00 0.00 35360 desiredvnodes % busy 69 32 0 0 0 10098 numvnodes 6637 freevnodes IRQ 11 is my "super fun IRQ" with 90% of my hardware attached.. I am copying about 17000 45k files. The controller is the one built into my Dell Inspiron 8600 -> Aug 9 11:29:24 inchoate kernel: fwohci0: <1394 Open Host Controller Interf= ace> mem 0xfaffd800-0xfaffdfff,0xfaff8000-0xfaffbfff irq 11 at device 1.1 o= n pci2 Aug 9 11:29:24 inchoate kernel: fwohci0: [GIANT-LOCKED] Aug 9 11:29:24 inchoate kernel: fwohci0: OHCI version 1.10 (ROM=3D0) Aug 9 11:29:24 inchoate kernel: fwohci0: No. of Isochronous channels is 4. Aug 9 11:29:24 inchoate kernel: fwohci0: EUI64 43:4f:c0:00:08:17:a4:38 Aug 9 11:29:24 inchoate kernel: fwohci0: Phy 1394a available S400, 2 ports. Aug 9 11:29:24 inchoate kernel: fwohci0: Link S400, max_rec 2048 bytes. When I tried this earlier with 65000 much larger files I managed to get=20 rsync to use 125% of the CPU (no HT/SMP here).. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart6462642.tQgiqJT8v9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC+ITv5ZPcIHs/zowRAtJfAJ9Nl4o9bvUrJ2sv6JsrO/FlvtJrxgCggu0E u/SOdM6BARUzdpF7AcFdKCA= =CdP1 -----END PGP SIGNATURE----- --nextPart6462642.tQgiqJT8v9-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 12:50:13 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6229D16A41F; Tue, 9 Aug 2005 12:50:13 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E297E43D46; Tue, 9 Aug 2005 12:50:12 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id CD90D997564; Tue, 9 Aug 2005 14:50:09 +0200 (CEST) Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 91013-07; Tue, 9 Aug 2005 14:50:03 +0200 (CEST) Received: from [80.98.156.20] (catv-50629c14.catv.broadband.hu [80.98.156.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.t-hosting.hu (Postfix) with ESMTP id 725BA99741D; Tue, 9 Aug 2005 14:50:03 +0200 (CEST) Message-ID: <42F8A673.1030805@t-hosting.hu> Date: Tue, 09 Aug 2005 14:49:55 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at t-hosting.hu Cc: Subject: Summary about nve network interface driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 12:50:13 -0000 Hi, I've experineced serious errors with the nve driver and I've seen quite many people would like to use it, but they also experiences these error. There are open PR's and unfortunately nobody has volunteered to fix this issue, the PR's have the default Responsible field, nobody has changed it. Maxime Henrion has tried to fix the crashes, however, and asked me to test his commits in HEAD, but unfortunately things haven't become better. I've also seen, that Quinton Dolan, the original developer of this driver, has also committed something to HEAD, he was the last committer to that file when I checked HEAD, but unfortunately at moment RELENG_6 has this buggy version and so has HEAD. I've checked both. The problem is complicated, the experineced errors are quite different: - Sometimes it crashes with an attempted use of a free mbuf. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=83943 I've experineced and reported this issue in RELENG_6. There is an another report by Dmitry Selin: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/82555 - I've also exprienced a general protection fault and I suspect it must be related to the nve driver. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=84133 I've experineced this issue in RELENG_6 and in HEAD. - Some people have device timeouts with nve. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/84027 I've also experienced it, but haven't reported, I wanted to get the crashes fixed first. I'm very interested in fixing this driver, because I would like to use FreeBSD 6.0 as my desktop os, but unfortunately I don't have the knowledge to fix this driver. If somebody would volunteer to take care, I'd do the testing in RELENG_6 or HEAD or I'd do what I'd been told to do. It would be really nice if it got fixed by the time 6.0-RELEASE gets released. Cheers, Gábor Kövesdán From owner-freebsd-stable@FreeBSD.ORG Mon Aug 8 22:53:55 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC8816A41F; Mon, 8 Aug 2005 22:53:55 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ED9943D46; Mon, 8 Aug 2005 22:53:55 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-187-230.dsl.snfc21.pacbell.net [64.171.187.230]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j78Mrqo5028030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 8 Aug 2005 15:53:56 -0700 Message-ID: <42F7E27E.9090302@root.org> Date: Mon, 08 Aug 2005 15:53:50 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tijl Coosemans References: <200508020022.02992.tijl@ulyssis.org> In-Reply-To: <200508020022.02992.tijl@ulyssis.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 09 Aug 2005 15:31:00 +0000 Cc: acpi@FreeBSD.org Subject: Re: 5-STABLE cpufreq hotter than est from ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 22:53:56 -0000 Tijl Coosemans wrote: > A couple days ago I updated my system and was excited to see cpufreq > and powerd in 5-stable. Since then however I noticed that my laptop > temperature is about 5°C higher than with est and estctrl. I found that > cpufreq when setting 200MHz for example set the absolute frequency to > 1600MHz (max for this laptop) and the relative frequency (p4tcc) to > 12.5% instead of using a more power conserving setting like 800MHz/25%. > > The problem is that cpufreq_expand_set() (sys/kern/kern_cpu.c) > traverses freq levels from high to low when adding relative levels and > skips duplicates. When it wants to add 800MHz/25% it sees this setting > as a duplicate of 1600MHz/12.5% it has found before. This can be fixed > by letting cpufreq_expand_set() traverse freq levels in reverse order > (and still skipping duplicates). Then each frequency level has the > lowest possible absolute setting. This is a one line change in > sys/kern/kern_cpu.c (line 653). You have some valid issues but I need some time to analyze your patch to be sure it doesn't introduce new problems. There may be some issues with traversing the list backwards. > Also, somewhat related, the p4tcc driver doesn't recognise > acpi_throttle, which means that when you load the cpufreq module after > booting, the freq levels are messed up. I'm not sure what the best > solution for this is. Let p4tcc detect acpi_throttle and don't attach > if it's present (like acpi_throttle does now if it finds p4tcc) or > detach it before attaching? Or maybe p4tcc and acpi_throttle should be > merged into one driver? cpufreq is not set up for loading after boot currently. It must be loaded at boot. There are architectural issues that need to be solved to make this happen, namely real arbitration between drivers loaded that support the same feature through different mechanisms. p4tcc and acpi_throttle on some architectures is such a combo that needs special attention. > Finally, is the kernel config option CPU_ENABLE_TCC still relevant? > Because it's still listed in NOTES. The old option should be removed. I'll try to review this patch and commit it sometime soon. -- Nate From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 15:54:57 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69E5016A41F for ; Tue, 9 Aug 2005 15:54:57 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83D6743D6E for ; Tue, 9 Aug 2005 15:54:55 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AAC2A9.dip0.t-ipconnect.de [84.170.194.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id A29263357F; Tue, 9 Aug 2005 17:57:44 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j79Fswg8000749; Tue, 9 Aug 2005 17:54:58 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j79Fst1Q000748; Tue, 9 Aug 2005 17:54:55 +0200 (CEST) (envelope-from mkb) Date: Tue, 9 Aug 2005 17:54:55 +0200 From: Matthias Buelow To: Yann Golanski Message-ID: <20050809155455.GA653@drjekyll.mkbuelow.net> References: <20050809085704.GA49451@kierun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050809085704.GA49451@kierun.org> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Xorg, Radeon X800PRO problem. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 15:54:57 -0000 >Section "Device" > Identifier "Card0" > Driver "ati" > #VendorName "ATI Technologies Inc" > #BoardName "Radeon X800PRO" > #BusID "PCI:5:0:0" >EndSection ... >(--) Assigning device section with no busID to primary device >(WW) RADEON: No matching Device section for instance (BusID PCI:5:0:1) found >(EE) No devices detected. Have you tried specifying that BusID as in the commented out line above (only PCI:5:0:1 instead of PCI:5:0:0)? mkb. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 16:39:23 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FECF16A41F for ; Tue, 9 Aug 2005 16:39:23 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id CABE543D48 for ; Tue, 9 Aug 2005 16:39:22 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AAC2A9.dip0.t-ipconnect.de [84.170.194.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 3C45433F2D; Tue, 9 Aug 2005 18:42:12 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j79GdSCZ001010; Tue, 9 Aug 2005 18:39:28 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j79GdRl4001009; Tue, 9 Aug 2005 18:39:27 +0200 (CEST) (envelope-from mkb) Date: Tue, 9 Aug 2005 18:39:27 +0200 From: Matthias Buelow To: Yann Golanski Message-ID: <20050809163927.GC653@drjekyll.mkbuelow.net> References: <20050809085704.GA49451@kierun.org> <20050809155455.GA653@drjekyll.mkbuelow.net> <20050809160030.GA54131@kierun.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050809160030.GA54131@kierun.org> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Xorg, Radeon X800PRO problem. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 16:39:23 -0000 Yann Golanski wrote: >Yes, it gives me the same error. The warning changes the PCI slot to >PCI:5:0:0... > >Anyway, I used an older card. It works. *shrugs* Odd.. I've got an X800SE and it works without problems; don't think there's so much of a difference concerning the Xorg driver with the two cards.. ... Errm! Upon looking at your original mail again.. you're running Xorg 6.7? I don't think it'll work with that version. I had to apply patches back then to get 6.7 to work with my card. Try upgrading to the current version that is in ports (6.8.2 iirc). mkb. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 16:41:58 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DECE816A41F for ; Tue, 9 Aug 2005 16:41:58 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73C2943D49 for ; Tue, 9 Aug 2005 16:41:58 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j79Gfvvf023297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Aug 2005 12:41:57 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j79Gfv6P018315; Tue, 9 Aug 2005 12:41:57 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CA916512BD; Tue, 9 Aug 2005 12:41:56 -0400 (EDT) Date: Tue, 9 Aug 2005 12:41:56 -0400 From: Kris Kennaway To: Petr Holub Message-ID: <20050809164156.GA5516@xor.obsecurity.org> References: <000401c59b70$3627fd40$ba36fb93@KLOBOUCEK> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <000401c59b70$3627fd40$ba36fb93@KLOBOUCEK> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: kernel panic on 5.4-RELEASE-p6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 16:41:59 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 07, 2005 at 06:51:09PM +0200, Petr Holub wrote: > Hi all, >=20 > I've encoutnered the follwing kernel panic on 5.4-RELEASE-p6. However, > as the machine is production and not development one, I don't have > debugger analysis. The panic might *theoretically* be due to problems > accessing faulty CD-R media in the ATAPI DVD/CD-RW drive (that was the > only unusual thing which happened before the panic). Kernel config > and dmesg are attached below, the machine is IBM T41p laptop. >=20 > Fatal trap 12: page fault while in kernel mode > fault virtual address =3D 0x300f0 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0x300f0 > stack pointer =3D 0x10:0xe67cdb1c > frame pointer =3D 0x10:0xe67cdb34 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 1337 (vim) > trap number =3D 12 > panic: page fault > Uptime: 14m43s. You need to follow the instructions in the chapter on kernel debugging in the developers handbook in order for anyone to be able to begin investigating this. Kris --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC+NzUWry0BWjoQKURAuMoAJ9ykQ4M4p6AJuW/Rat71xP5XyvojQCfVL1i BsnZb8WDhh9gMMVibCq63D0= =gJOV -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 16:43:21 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEA0016A41F for ; Tue, 9 Aug 2005 16:43:21 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5337543D55 for ; Tue, 9 Aug 2005 16:43:21 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j79GhJvf023408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Aug 2005 12:43:19 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j79GhJ6P018426; Tue, 9 Aug 2005 12:43:19 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 149B8512BD; Tue, 9 Aug 2005 12:43:19 -0400 (EDT) Date: Tue, 9 Aug 2005 12:43:18 -0400 From: Kris Kennaway To: Derrick Edwards Message-ID: <20050809164318.GB5516@xor.obsecurity.org> References: <200508030847.44415.dantavious@comcast.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="A6N2fC+uXW/VQSAv" Content-Disposition: inline In-Reply-To: <200508030847.44415.dantavious@comcast.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Panic on FreeBSD 6.0BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 16:43:21 -0000 --A6N2fC+uXW/VQSAv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 03, 2005 at 08:47:43AM -0400, Derrick Edwards wrote: > ???Hi all, > I decided to try and help with testing 6-BETA1, after updating sources an= d=20 > recompiling i get the following during boot up. I am tried booting withou= t=20 > hyperthreading enabled in the bios and I still get the same panic. >=20 > Fatal trap 12: page fault while in kernel mode > cpuid =3D 0; apic id =3D00 > fault virtual address =3D 0x480008 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x20:0xc06923cc > stack pointer =3D 0x28:0xc10208ec >=20 > Code segment =3D base 0x0, limit 0xfffff, type 0x1b > ? ? ? ? ? ? ?=3D DPL 0, pres 1, def32 1, gran 1 >=20 > processor eflags =3D interrupt enabled, resyne, IOPL =3D 0 > current process =3D 0 (swapper) > [thread pid 0tid0] > Stopped at strlen+0x8: cmpb $0,0(%edx) >=20 > I left all the debugging features in the current however, I am not sure= =20 > exactly how to trace this problem. If someone could point me to any doc t= hat=20 > would allow to provide more information that would ?be great. I updated m= y=20 > pen 400MHZ using the same procedures and all went well. Please help See the chapter on kernel debugging in the developers handbook. Kris P.S. I need to make a macro to type the answer to this FAQ.=20 --A6N2fC+uXW/VQSAv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC+N0mWry0BWjoQKURAp8eAJ4ksTLomkrdewccvrhgbqVki3BRhQCgiDON n8rTkOYEbC5TUXDqrpqcbhE= =8nmb -----END PGP SIGNATURE----- --A6N2fC+uXW/VQSAv-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 17:22:42 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7428816A41F for ; Tue, 9 Aug 2005 17:22:42 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from tirith.ics.muni.cz (tirith.ics.muni.cz [147.251.4.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6F2843D48 for ; Tue, 9 Aug 2005 17:22:41 +0000 (GMT) (envelope-from hopet@ics.muni.cz) Received: from KLOBOUCEK (kloboucek.ics.muni.cz [147.251.3.38]) (user=hopet@META mech=LOGIN bits=0) by tirith.ics.muni.cz (8.13.2/8.13.2) with ESMTP id j79HMd59015801 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 9 Aug 2005 19:22:40 +0200 From: "Petr Holub" To: "Kris Kennaway" Date: Tue, 9 Aug 2005 19:22:39 +0200 Message-ID: <005a01c59d06$f182c150$2603fb93@KLOBOUCEK> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <20050809164156.GA5516@xor.obsecurity.org> Importance: Normal X-Muni-Spam-TestIP: 147.251.3.38 X-Muni-Envelope-From: hopet@ics.muni.cz X-Muni-Virus-Test: Clean Cc: stable@freebsd.org Subject: RE: kernel panic on 5.4-RELEASE-p6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 17:22:42 -0000 > You need to follow the instructions in the chapter on kernel debugging > in the developers handbook in order for anyone to be able to begin > investigating this. I though that - alas at the time of the panic, that machine didn't have dump partition configured. :(( Anyway, I've configured that partition, built kernel.debug and I'm just waiting if that happens again. Thanks, Petr ================================================================ Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 4 Institute of Compt. Science 162 00 Praha 6, CZ Masaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: Petr.Holub@cesnet.cz phone: +420-549493944 fax: +420-541212747 e-mail: hopet@ics.muni.cz From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 17:28:50 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55A6716A41F for ; Tue, 9 Aug 2005 17:28:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9220743D46 for ; Tue, 9 Aug 2005 17:28:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j79HSnvf027975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Aug 2005 13:28:49 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j79HSm6P023118; Tue, 9 Aug 2005 13:28:48 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8ABFF5130F; Tue, 9 Aug 2005 13:28:48 -0400 (EDT) Date: Tue, 9 Aug 2005 13:28:48 -0400 From: Kris Kennaway To: Petr Holub Message-ID: <20050809172848.GB21952@xor.obsecurity.org> References: <20050809164156.GA5516@xor.obsecurity.org> <005a01c59d06$f182c150$2603fb93@KLOBOUCEK> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BwCQnh7xodEAoBMC" Content-Disposition: inline In-Reply-To: <005a01c59d06$f182c150$2603fb93@KLOBOUCEK> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, Kris Kennaway Subject: Re: kernel panic on 5.4-RELEASE-p6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 17:28:50 -0000 --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 09, 2005 at 07:22:39PM +0200, Petr Holub wrote: > > You need to follow the instructions in the chapter on kernel debugging > > in the developers handbook in order for anyone to be able to begin > > investigating this. >=20 > I though that - alas at the time of the panic, that machine didn't have > dump partition configured. :(( Anyway, I've configured that partition, > built kernel.debug and I'm just waiting if that happens again. That chapter also describes a fallback you can use if you don't have a kernel.debug or dump to at least get the name of the function in which the panic occurred. Kris --BwCQnh7xodEAoBMC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC+OfQWry0BWjoQKURAhTiAKCcVbXGZi26GzECoclM1SaRTbz4JACfXZhk TCi8wvQ4NG5nKTodPQgdtEo= =cu0N -----END PGP SIGNATURE----- --BwCQnh7xodEAoBMC-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 18:39:30 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC55016A41F; Tue, 9 Aug 2005 18:39:30 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from sdcexchange01.amcc.com (gatekeeper-out.amcc.com [198.137.200.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61C4E43D45; Tue, 9 Aug 2005 18:39:30 +0000 (GMT) (envelope-from vkashyap@amcc.com) Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.326 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 9 Aug 2005 11:39:26 -0700 Message-ID: <2B3B2AA816369A4E87D7BE63EC9D2F2659F844@SDCEXCHANGE01.ad.amcc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: twa0 errors and system lockup on amd64 thread-index: AcWcX9bP3vACA8qpScGtvyt6TUk32gAr4cVg From: "Vinod Kashyap" To: "Jung-uk Kim" , Cc: Josh Endries Subject: RE: twa0 errors and system lockup on amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 18:39:30 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org=20 > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Jung-uk Kim > Sent: Monday, August 08, 2005 2:29 PM > To: freebsd-stable@FreeBSD.org > Cc: Josh Endries > Subject: Re: twa0 errors and system lockup on amd64 >=20 > On Monday 08 August 2005 05:03 pm, Josh Endries wrote: > > Hello, > > > > Just a little while ago I got this on a test 5.4-stable=20 > dual Opteron=20 > > box I'm setting up (9500S-LP RAID 5 with a hot spare): > > > > Aug 8 15:58:21 kernel: twa0: ERROR: (0x05: 0x210b): Request timed > > out!: request =3D 0xffffffff80a67700 > > Aug 8 15:58:21 kernel: twa0: INFO: (0x16: 0x1108): Resetting > > controller...: > > Aug 8 15:58:21 kernel: twa0: ERROR: (0x15: 0x110b): Can't=20 > drain AEN=20 > > queue after reset: error =3D 60 Aug 8 15:58:21 kernel: twa0: ERROR: = > > (0x16: 0x1105): Controller reset failed: error =3D 60; attempt 1 > > > > It attempted twice and then just sat there after that. I=20 > couldn't log=20 > > in at all so I did a hard reset after probably 30+ minutes.=20 > I didn't=20 > > find much online other than driver source code or twe(4) man pages,=20 > > which suggests that it's a problem between the driver and card. Has=20 > > anyone else seen this problem? Is it a sign of a flaky card=20 > or could=20 > > it be something else? Maybe it's something to do with AMD64? This=20 > > system was supposed to go into production tomorrow. I guess=20 > it's good=20 > > that it died today... >=20 This should have nothing to do with amd64. The firmware seems to have gotten into a bad state. Can you reproduce this consistently? If you can, please run 'tw_cli /cX show diag', and send the output. > I have seen it with 9500S-8, which is the same controller=20 > with 8 ports. In fact, I am seeing other problems. >=20 > twa0: INFO: (0x04: 0x000b): Rebuild started: unit=3D0 > twa0: ERROR: (0x04: 0x0002): Degraded unit: unit=3D0, port=3D5 > twa0: INFO: (0x04: 0x000b): Rebuild started: unit=3D0 > twa0: INFO: (0x04: 0x003b): Rebuild paused: unit=3D0 > twa0: INFO: (0x04: 0x000b): Rebuild started: unit=3D0 > twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=3D5 > twa0: INFO: (0x04: 0x003b): Rebuild paused: unit=3D0 > twa0: INFO: (0x04: 0x000b): Rebuild started: unit=3D0 > twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=3D5 > twa0: INFO: (0x04: 0x0005): Rebuild completed: unit=3D0 > twa0: ERROR: (0x04: 0x0009): Drive timeout detected: port=3D5 > twa0: ERROR: (0x04: 0x0002): Degraded unit: unit=3D0, port=3D5 >=20 > I have rebuilt this array many times but it's happening again=20 > and again. It seems this controller/driver has issues with=20 > amd64. FYI, UP kernel or replacing cables didn't fix the problem. >=20 You seem to have a bad drive/cable at port 5. > Good luck, >=20 > Jung-uk Kim >=20 > > Josh > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to=20 > "freebsd-stable-unsubscribe@freebsd.org" > -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, = is for the sole use of the intended recipient(s) and contains = information that is confidential and proprietary to Applied Micro = Circuits Corporation or its subsidiaries. It is to be used solely for = the purpose of furthering the parties' business relationship. All = unauthorized review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply = e-mail and destroy all copies of the original message. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 9 22:23:56 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9550F16A429; Tue, 9 Aug 2005 22:23:56 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4369E43FCF; Tue, 9 Aug 2005 19:14:41 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 5AF895D08; Tue, 9 Aug 2005 15:14:40 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23243-07; Tue, 9 Aug 2005 15:14:38 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 3E21A5D28; Tue, 9 Aug 2005 15:14:38 -0400 (EDT) Message-ID: <42F9009E.3030601@mac.com> Date: Tue, 09 Aug 2005 15:14:38 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "O. Hartmann" References: <42F7F7E8.1020507@mail.uni-mainz.de> In-Reply-To: <42F7F7E8.1020507@mail.uni-mainz.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 22:23:57 -0000 O. Hartmann wrote: [ ... ] > One of my SATA disks, the SAMSUNG SP2004C seems to show errors during > operation (and also showd under 5.4-RELEASE-p3). > Sometimes I get this error: > ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 > while the machine still keeps working. > Other days the box crashes completely. > > Is this a operating system bug or is this message an evidence of > defective hardware? Back up any data you care about now. Use the smartmontools port or hunt down a utility from Samsung which'll do a surface test (read only, nondestructive). You can also run a "dd if=/dev/ad10 of=/dev/null bs=8192" to do a full read test under FreeBSD, and see how many CRC errors show up. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 02:03:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05ACC16A41F for ; Wed, 10 Aug 2005 02:03:39 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from audi.websitewelcome.com (audi.websitewelcome.com [67.19.210.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7AEE45A98 for ; Wed, 10 Aug 2005 02:03:38 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from adsl-065-013-105-239.sip.tys.bellsouth.net ([65.13.105.239]:2205 helo=[192.168.1.33]) by audi.websitewelcome.com with esmtpa (Exim 4.50) id 1E2fwH-00081y-9K for freebsd-stable@freebsd.org; Tue, 09 Aug 2005 21:03:29 -0500 Message-ID: <42F9609E.1010207@goldsword.com> Date: Tue, 09 Aug 2005 22:04:14 -0400 From: "J. T. Farmer" Organization: GoldSword Systems User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.7) Gecko/20050414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> In-Reply-To: <42F9009E.3030601@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - audi.websitewelcome.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - goldsword.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 02:03:39 -0000 Chuck Swiger wrote: > O. Hartmann wrote: > [ ... ] > >> One of my SATA disks, the SAMSUNG SP2004C seems to show errors >> during operation (and also showd under 5.4-RELEASE-p3). >> Sometimes I get this error: >> ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 >> while the machine still keeps working. >> Other days the box crashes completely. >> >> Is this a operating system bug or is this message an evidence of >> defective hardware? > > Back up any data you care about now. Use the smartmontools port or > hunt down a utility from Samsung which'll do a surface test (read > only, nondestructive). > > You can also run a "dd if=/dev/ad10 of=/dev/null bs=8192" to do a full > read test under FreeBSD, and see how many CRC errors show up. Actually, I would go with the "it's an operating system error." That's exactly the same error quite a few people (myself included) have been reporting under 5.4 and 5-STABLE. In my case, I just installed the smartmontools port and it's reporting that my drive is behaving perfectly. This is 6.0-Beta? I have a couple spare drives here (destined to be part of a RAID array on another machine). Perhaps after I get rid of some of the current RL overloads, I will try it on this machine. John ---------------------------------------------------------------------- John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 02:17:40 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5604016A474 for ; Wed, 10 Aug 2005 02:17:29 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFE8845848 for ; Wed, 10 Aug 2005 01:45:56 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E2ffE-000Bgi-5L; Wed, 10 Aug 2005 01:45:52 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E2ffD-0002pn-Jb; Tue, 09 Aug 2005 15:45:51 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17145.23631.3020.228401@roam.psg.com> Date: Tue, 9 Aug 2005 15:45:51 -1000 To: Peter Jeremy References: <17143.55126.928714.853442@roam.psg.com> <790a9fff05080816561c653e73@mail.gmail.com> <17143.61777.552270.95710@roam.psg.com> <790a9fff05080817054ff9e1d8@mail.gmail.com> <17143.63487.787071.348531@roam.psg.com> <20050809090252.GE9970@cirb503493.alcatel.com.au> Cc: Scot Hetzel , FreeBSD Stable Subject: Re: 4->5 libmilter.a install failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 02:17:40 -0000 fwiw, we gave up and are cold installing 6 randy From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 02:31:13 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95CE516A41F for ; Wed, 10 Aug 2005 02:31:13 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2256343D72 for ; Wed, 10 Aug 2005 02:31:12 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j7A2VCXP003091 for ; Tue, 9 Aug 2005 21:31:12 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Tue Aug 9 21:31:12 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j7A2VB61003088 for freebsd-stable@freebsd.org; Tue, 9 Aug 2005 21:31:11 -0500 (CDT) (envelope-from karl) Date: Tue, 9 Aug 2005 21:31:11 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050810023111.GA2913@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42F9609E.1010207@goldsword.com> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 02:31:13 -0000 Post your "dmesg" output from boot. If the SATA controller has a SII chipset, you're in trouble. Get that board out of there - or if its on the motherboard, get something else in there and use it instead. SII chipsets were ok in 4.x, but the newer ATA code broke badly with them. I've had a PR open on this since February, and many others have reported similar issues. The problems still exist in the 6.x-BETA releases I've checked out, and are in some cases MORE severe (for me anyway) than they are in 5.4. You CAN AND WILL lose data if you're not careful. Be careful! A BIG disappointment to me is that FreeBSD has not CONSPICUOUSLY stated in the hardware notes for 5.4 (and beyond) that these controllers DO NOT work reliably with 5.x and later, or undertaken to do whatever is needed to make them work as they did in 4.x (I had no problems with the same hardware under the 4.x releases) As these controllers are widely available and very inexpensive, not to mention showing up in all manner of boards from various vendors (including Adaptec, Bustek and on some motherboards!) this is quite a disappointment. I finally gave up kvetching on the list and bought a 3ware 8502 card. Same disks, same system, same load, no problems. Smartmontools declared all my disks as perfectly healthy in my case, and has for several others as well.... YMMV. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind On Tue, Aug 09, 2005 at 10:04:14PM -0400, J. T. Farmer wrote: > Chuck Swiger wrote: > > >O. Hartmann wrote: > >[ ... ] > > > >>One of my SATA disks, the SAMSUNG SP2004C seems to show errors > >>during operation (and also showd under 5.4-RELEASE-p3). > >>Sometimes I get this error: > >>ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 > >>while the machine still keeps working. > >>Other days the box crashes completely. > >> > >>Is this a operating system bug or is this message an evidence of > >>defective hardware? > > > >Back up any data you care about now. Use the smartmontools port or > >hunt down a utility from Samsung which'll do a surface test (read > >only, nondestructive). > > > >You can also run a "dd if=/dev/ad10 of=/dev/null bs=8192" to do a full > >read test under FreeBSD, and see how many CRC errors show up. > > > Actually, I would go with the "it's an operating system error." That's > exactly > the same error quite a few people (myself included) have been reporting > under > 5.4 and 5-STABLE. In my case, I just installed the smartmontools port and > it's reporting that my drive is behaving perfectly. > > This is 6.0-Beta? I have a couple spare drives here (destined to be part of > a RAID array on another machine). Perhaps after I get rid of some of the > current RL overloads, I will try it on this machine. > > John > > ---------------------------------------------------------------------- > John T. Farmer Owner & CTO GoldSword Systems > jfarmer@goldsword.com 865-691-6498 Knoxville TN > Consulting, Design, & Development of Networks & Software > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > %SPAMBLOCK-SYS: Matched [@freebsd.org+], message ok From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 03:05:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E780316A41F for ; Wed, 10 Aug 2005 03:05:20 +0000 (GMT) (envelope-from christias@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF22D44B6B for ; Tue, 9 Aug 2005 23:18:03 +0000 (GMT) (envelope-from christias@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so14080rna for ; Tue, 09 Aug 2005 16:18:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=glQLjks8wdgknq5bl6MfUT+lr0omWG9qssWSqfLyljbgNRUg+PxobOiv1FBH34jTGghtg73m8J5d9sVIpBPf8myw4UjCqHzXA4w3mAUSixw6kMfBZgDCj97n3PRXuXaMT4eQy/VcVI1iWm1c6DatKEi2ofgtjOXIYicxVJkmMSo= Received: by 10.39.1.40 with SMTP id d40mr40574rni; Tue, 09 Aug 2005 16:18:03 -0700 (PDT) Received: by 10.39.1.55 with HTTP; Tue, 9 Aug 2005 16:18:03 -0700 (PDT) Message-ID: Date: Wed, 10 Aug 2005 02:18:03 +0300 From: Panagiotis Christias To: Kris Kennaway In-Reply-To: <20050809164318.GB5516@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200508030847.44415.dantavious@comcast.net> <20050809164318.GB5516@xor.obsecurity.org> Cc: freebsd-stable@freebsd.org Subject: Re: Panic on FreeBSD 6.0BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 03:05:21 -0000 On 8/9/05, Kris Kennaway wrote: > On Wed, Aug 03, 2005 at 08:47:43AM -0400, Derrick Edwards wrote: > > ???Hi all, > > I decided to try and help with testing 6-BETA1, after updating sources = and > > recompiling i get the following during boot up. I am tried booting with= out > > hyperthreading enabled in the bios and I still get the same panic. > > > > Fatal trap 12: page fault while in kernel mode > > cpuid =3D 0; apic id =3D00 > > fault virtual address =3D 0x480008 > > fault code =3D supervisor read, page not present > > instruction pointer =3D 0x20:0xc06923cc > > stack pointer =3D 0x28:0xc10208ec > > > > Code segment =3D base 0x0, limit 0xfffff, type 0x1b > > ? ? ? ? ? ? ?=3D DPL 0, pres 1, def32 1, gran 1 > > > > processor eflags =3D interrupt enabled, resyne, IOPL =3D 0 > > current process =3D 0 (swapper) > > [thread pid 0tid0] > > Stopped at strlen+0x8: cmpb $0,0(%edx) > > > > I left all the debugging features in the current however, I am not sure > > exactly how to trace this problem. If someone could point me to any doc= that > > would allow to provide more information that would ?be great. I updated= my > > pen 400MHZ using the same procedures and all went well. Please help >=20 > See the chapter on kernel debugging in the developers handbook. >=20 > Kris >=20 > P.S. I need to make a macro to type the answer to this FAQ. IMHO I think that the average FreeBSD user/fan could use some help when he/she deals with kernel panics/crashes/dumps/kgdb/kernel.debug etc. First step, the debug kernel and modules could be included in the base system. What is it, 50 to 60MB disk space? That should be no(?) problem. Being there and correctly built by "The Source" would be the first step for the average user (not the "I wrote the kernel" developer) to use them and provide correct, complete and thus useful feedback. The one that you developers ask for. Second step, the procedure of extracting the useful data from the crash dumps using the "wat doez diz program do?" kgdb program is not efficient to be left in hands of the average user. He/she is probably a great guy, afterall he/she is using FreeBSD and certainly willing to contribute but dealing with kgdb is too much to ask for. Except if he/she has the guidance of kernel developer through this mailing list or others. It is not an efficient way to investigate and report serious problems. I am wondering if possible to write some kgdb-wrapper scripts which would do the dirty job of analyzing the crash dump using kgdb and the proper command (backtrace, list xx, print yy, up nn, down mm, voodoo etc.). This procedure can be as detailed as needed or wanted. The results could be sent automatically (send-pr) to the FreeBSD Team. That way, every user would be able to easily send proper reports without mistakes or missing data and benefit the FreeBSD Project. Any thoughts? Panagiotis From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 03:26:11 2005 Return-Path: X-Original-To: FreeBSD-stable@FreeBSD.org Delivered-To: FreeBSD-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A42EC16A41F for ; Wed, 10 Aug 2005 03:26:11 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from vette.gigo.com (vette.gigo.com [216.218.228.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6956A45BB2 for ; Wed, 10 Aug 2005 03:26:11 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from 201.24.48.30 (unknown [201.24.48.30]) by vette.gigo.com (Postfix) with ESMTP id 404BA55B4 for ; Tue, 9 Aug 2005 20:26:10 -0700 (PDT) Received: (qmail 81570 invoked from network); 10 Aug 2005 03:22:44 -0000 Received: from unknown (HELO exxodus.fedaykin.here) (127.0.0.1) by exxodus.fedaykin.here with SMTP; 10 Aug 2005 03:22:44 -0000 Date: Wed, 10 Aug 2005 03:22:21 +0000 From: Mario Sergio Fujikawa Ferreira To: FreeBSD-stable@FreeBSD.org In-Reply-To: <1123642735l.19636l.1l@exxodus.fedaykin.here> (from lioux@FreeBSD.org on Tue Aug 9 23:58:26 2005) X-Mailer: Balsa 2.3.4 Message-Id: <1123644163l.19636l.8l@exxodus.fedaykin.here> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: mldonkey kqueue patch (replace select/poll) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 03:26:11 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, My previous email did not have enough information. MLDonkey is a OCAML/GTK client for a number of peer-to-peer networks including edonkey, overnet and kademlia. It can be found on the FreeBSD ports tree under both net/mldonkey and net/mldonkey-devel. I just wrote a patch against ports/net/mldonkey-devel version 2.6.1 to support kqueue(2) FreeBSD kernel event notification mechanism. It is meant to replace select/poll inside mldonkey. kqueue scales better than select/poll not to mention that it should be faster. I am having a little bit of trouble with this patch. MLDonkey daemon loads and I am able to connect to the daemon through both the web interface and kmldonkey. However, it seems unable to connect to eDonkey servers. Are there any takers to help me on this one? It should really improve performance under FreeBSD and possibly other *BSD platforms. A sample port with the current patch included can be found at http://people.FreeBSD.org/~lioux/mldonkey-kqueue.tgz It is not meant for general use since MLDonkey will not connect to any servers but it is good enough for someone to have an idea of what I want to do. If you only want the patch, it can be found at http://people.FreeBSD.org/~lioux/mldonkey-kqueue-patch.zip My current hypotheses are: 1) The MLDonkey C stubs used to interface the kqueue code with the ocaml code are not behaving as expected; i.e., MLDonkey is not calling the stubs C at each and every needed place (at every addition, removal and updating of file descriptors which will, in turn, result in similar changes to the kqueue filters). 2) The kqueue code is not correctly written. I think that most people can help with option (2). :) All and any help is appreciated. This discussion can be followed at MLDonkey's patch manager at: http://savannah.nongnu.org/patch/index.php?func=3Ddetailitem&item_id=3D4293 Regards, MSFF ps: Please, include me on CC: replies since I am no longer subscribed to this mailing list. keywords: select, poll, kqueue, kevent, FreeBSD, NetBSD, OpenBSD, epoll -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFC+XMDrxEiaFLzGQwRAqLOAJ91g28fIz95wpmPnd2xp/VcEBlC2ACaArlN f1kspvvVMum/7zYRoNrkIlI=3D =3D6BDw -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 03:40:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D343116A42B for ; Wed, 10 Aug 2005 03:40:36 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42AB3455EA for ; Wed, 10 Aug 2005 02:46:11 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AAC2A9.dip0.t-ipconnect.de [84.170.194.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id A6A6033DD5 for ; Wed, 10 Aug 2005 04:49:02 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7A2kJ9c008335 for ; Wed, 10 Aug 2005 04:46:19 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7A2kJ6W008334 for freebsd-stable@freebsd.org; Wed, 10 Aug 2005 04:46:19 +0200 (CEST) (envelope-from mkb) Date: Wed, 10 Aug 2005 04:46:18 +0200 From: Matthias Buelow To: freebsd-stable@freebsd.org Message-ID: <20050810024618.GA8198@drjekyll.mkbuelow.net> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050810023111.GA2913@FS.denninger.net> User-Agent: Mutt/1.4.2.1i Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 03:40:38 -0000 Karl Denninger wrote: >SII chipsets were ok in 4.x, but the newer ATA code broke badly with them. >I've had a PR open on this since February, and many others have reported >similar issues. The problems still exist in the 6.x-BETA releases I've >checked out, and are in some cases MORE severe (for me anyway) than they are >in 5.4. Well, it doesn't affect just the SII chips.. I see the same on an Intel ICH6 chipset but never after the kernel has mounted the root fs. Sometimes it takes several attempts until it manages to do so, though. The machine works w/o any such problems on other OSes. I've deferred update of another machine (which is a hosted box and cannot afford random hangs at boot) because of general flakeyness of the ATA/SATA code in 5.4 (significantly worse than with 5.3, imho). If these issues don't go away completely soon (in 6.x) I'll have to look for some alternative system which doesn't make such a fuss with mainstream hardware. mkb. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 05:53:20 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0399316A4F2 for ; Wed, 10 Aug 2005 05:52:53 +0000 (GMT) (envelope-from sascha@serverbitch.de) Received: from serverbitch.de (serverbitch.de [212.227.60.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 831A944E13 for ; Tue, 9 Aug 2005 23:32:35 +0000 (GMT) (envelope-from sascha@serverbitch.de) Received: from p54a3fcdd.dip.t-dialin.net ([84.163.252.221] helo=localhost.localdomain) by serverbitch.de with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.52 (FreeBSD)) id 1E2daB-00056y-2o; Wed, 10 Aug 2005 01:32:32 +0200 From: Sascha Holzleiter To: Yann Golanski In-Reply-To: <20050809085704.GA49451@kierun.org> References: <20050809085704.GA49451@kierun.org> Content-Type: text/plain Date: Wed, 10 Aug 2005 01:32:30 +0200 Message-Id: <1123630350.32342.4.camel@dreamland.chief.home> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: stable@freebsd.org Subject: Re: Xorg, Radeon X800PRO problem. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 05:53:26 -0000 On Tue, 2005-08-09 at 09:57 +0100, Yann Golanski wrote: > I am stuck on getting this graphics card working with stable. > I had the same problem with the standard server port. Replacing it with the xorg-server-snap port solved it. Seems these cards are just to new for the "stable" release ;) Thanks to our xorg maintainers for providing up-to-date servers! -- Sascha From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 05:53:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41C3216A6CF for ; Wed, 10 Aug 2005 05:53:12 +0000 (GMT) (envelope-from alanbryan1234@yahoo.com) Received: from web50304.mail.yahoo.com (web50304.mail.yahoo.com [206.190.38.58]) by mx1.FreeBSD.org (Postfix) with SMTP id 2137745E56 for ; Wed, 10 Aug 2005 04:28:45 +0000 (GMT) (envelope-from alanbryan1234@yahoo.com) Received: (qmail 67175 invoked by uid 60001); 10 Aug 2005 04:28:45 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=g6QihKfG/uV1VvG6qwmePed1lDYNSgyX7sICcxmj4wB3rC3GKogvHH5Pm0S94iyxnnt7JOdDwZHmGhJuqJLu38dQPUvlje3ptkwYrDIzHdTM578umPXyHHNYKtwt60Hk6ZtLlJpcNKQY8He9AXayTNDqxhsNYUCZd66K+Y3JWXs= ; Message-ID: <20050810042845.67173.qmail@web50304.mail.yahoo.com> Received: from [67.99.246.2] by web50304.mail.yahoo.com via HTTP; Tue, 09 Aug 2005 21:28:45 PDT Date: Tue, 9 Aug 2005 21:28:45 -0700 (PDT) From: alan bryan To: "Kövesdán" "Gábor" , freebsd-stable@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <42F8A673.1030805@t-hosting.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Summary about nve network interface driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 05:53:43 -0000 --- Kövesdán Gábor wrote: > Hi, > > I've experineced serious errors with the nve driver > and I've seen quite > many people would like to use it, but they also > experiences these error. I too would love it if this can be solved. I'm also willing to test and help wherever I can. In my case I get device timeouts and have just gotten used to rebooting about once per day when it runs out of buffer space and ceases to function. (If there's a way to re-initialize without a reboot that would help too). Thanks, Alan Bryan ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 05:55:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1579C16A570; Wed, 10 Aug 2005 05:54:39 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB1A9443F6; Tue, 9 Aug 2005 22:36:38 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.89.38] (manz-d9b95926.pool.mediaWays.net [217.185.89.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 8C9B030000AE; Wed, 10 Aug 2005 00:36:36 +0200 (CEST) Message-ID: <42F92FEE.8060305@mail.uni-mainz.de> Date: Wed, 10 Aug 2005 00:36:30 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Swiger References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> In-Reply-To: <42F9009E.3030601@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 05:55:16 -0000 Chuck Swiger wrote: > O. Hartmann wrote: > [ ... ] > >> One of my SATA disks, the SAMSUNG SP2004C seems to show errors >> during operation (and also showd under 5.4-RELEASE-p3). >> Sometimes I get this error: >> ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 >> while the machine still keeps working. >> Other days the box crashes completely. >> >> Is this a operating system bug or is this message an evidence of >> defective hardware? > > You can also run a "dd if=/dev/ad10 of=/dev/null bs=8192" to do a full > read test under FreeBSD, and see how many CRC errors show up. > I did so and I ran into a crash of the system ... I changed the cabling, did it again and until now nothing happend ... hope it was only a cabling issue. The first time I use ATA/SATA and now these experiences ... When is SCSI back for desktops? From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 07:21:28 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BAF716A420 for ; Wed, 10 Aug 2005 07:21:28 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: from proxy.ddcom.co.jp (proxy.ddcom.co.jp [211.121.191.163]) by mx1.FreeBSD.org (Postfix) with SMTP id 50ABB43D46 for ; Wed, 10 Aug 2005 07:21:24 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: (qmail 7091 invoked by alias); 10 Aug 2005 07:30:19 -0000 Received: from unknown (HELO ?172.16.1.133?) (10.10.10.11) by mail.ddcom.local with SMTP; 10 Aug 2005 07:30:19 -0000 In-Reply-To: <42F92FEE.8060305@mail.uni-mainz.de> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=UTF-8; format=flowed Message-Id: <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> Content-Transfer-Encoding: quoted-printable From: Joel Rees Date: Wed, 10 Aug 2005 16:19:28 +0900 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.733) Cc: freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 07:21:28 -0000 On =E5=B9=B3=E6=88=90 17/08/10, at 7:36, O. Hartmann wrote: > [...] When is SCSI back for desktops? I vote for that. In my opinion, ATA is primarily for home media systems, if that. Joel Rees digitcom, inc. =E6=A0=AA=E5=BC=8F=E4=BC=9A=E7=A4=BE=E3=83=87=E3=82=B8=E3= =82=B3=E3=83=A0 Kobe, Japan +81-78-672-8800 ** ** From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 09:26:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 945E316A41F for ; Wed, 10 Aug 2005 09:26:04 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 23EBE43D48 for ; Wed, 10 Aug 2005 09:26:03 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 22695 invoked from network); 10 Aug 2005 09:26:03 -0000 Received: from unknown (HELO ?192.168.1.11?) (unknown) by unknown with SMTP; 10 Aug 2005 09:26:03 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42F9C827.6080601@dominique-werner.com> Date: Wed, 10 Aug 2005 11:25:59 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> In-Reply-To: <20050810024618.GA8198@drjekyll.mkbuelow.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 09:26:04 -0000 Matthias Buelow wrote: >Karl Denninger wrote: > > > >>SII chipsets were ok in 4.x, but the newer ATA code broke badly with them. >>I've had a PR open on this since February, and many others have reported >>similar issues. The problems still exist in the 6.x-BETA releases I've >>checked out, and are in some cases MORE severe (for me anyway) than they are >>in 5.4. >> >> > >Well, it doesn't affect just the SII chips.. I see the same on an >Intel ICH6 chipset but never after the kernel has mounted the root >fs. Sometimes it takes several attempts until it manages to do so, >though. The machine works w/o any such problems on other OSes. I've >deferred update of another machine (which is a hosted box and cannot >afford random hangs at boot) because of general flakeyness of the >ATA/SATA code in 5.4 (significantly worse than with 5.3, imho). If >these issues don't go away completely soon (in 6.x) I'll have to >look for some alternative system which doesn't make such a fuss >with mainstream hardware. > >mkb. > >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > i knew about the problems with the sii chipset, had no idea it was just as bad with the ich6 chipset, I have a Seagate 160gb SATA drive on an Intel SATA controller so far no problems though in 5.4-stable, my system did not like 6 at all, 7 was fine again.. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 09:31:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38AB716A420 for ; Wed, 10 Aug 2005 09:31:35 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6F96D43D48 for ; Wed, 10 Aug 2005 09:31:34 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 24762 invoked from network); 10 Aug 2005 09:31:33 -0000 Received: from unknown (HELO ?192.168.1.11?) (unknown) by unknown with SMTP; 10 Aug 2005 09:31:33 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42F9C971.9070206@dominique-werner.com> Date: Wed, 10 Aug 2005 11:31:29 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joel Rees References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> In-Reply-To: <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 09:31:35 -0000 Joel Rees wrote: > > On å¹³æˆ 17/08/10, at 7:36, O. Hartmann wrote: > >> [...] When is SCSI back for desktops? > > > I vote for that. > > In my opinion, ATA is primarily for home media systems, if that. > > Joel Rees > digitcom, inc. æ ªå¼ä¼šç¤¾ãƒ‡ã‚¸ã‚³ãƒ  > Kobe, Japan +81-78-672-8800 > ** ** > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > I thought the WD Raptors were supposed to replace the SCSI for that purpose. I used to run one in a Powermac and performance wise it behaved very well, unfortunately I haven't had the chance to test the 30 or 70 GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 or server use anyway, they die after a while, in my case, two 80gb seagate drives after 1.5 yrs with proper cooling...thing is that SCSI drives are not affordable to the regular home server user...if they were, I bet more people would use them so that's why the current alternatives are ATA and SATA and SATA Raptors. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 09:33:33 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B57EC16A420 for ; Wed, 10 Aug 2005 09:33:33 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57B4943D5F for ; Wed, 10 Aug 2005 09:33:29 +0000 (GMT) (envelope-from pertti.kosunen@pp.nic.fi) Received: from [62.142.71.181] (KMMLXXXI.dsl.saunalahti.fi [62.142.71.181]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id E13DCD127F; Wed, 10 Aug 2005 12:33:24 +0300 (EEST) Message-ID: <42F9C9EA.60801@pp.nic.fi> Date: Wed, 10 Aug 2005 12:33:30 +0300 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 1.0.2 / FreeBSD 5.4-STABLE X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Swiger References: <42E12A3B.8040804@pp.nic.fi> <42F62DDD.8000902@pp.nic.fi> <42F64856.2010506@mac.com> In-Reply-To: <42F64856.2010506@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subscribers to FreeBSD-Stable Subject: Re: dhclient: send_packet: No buffer space available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 09:33:33 -0000 Chuck Swiger wrote: > Does the problem go away if you use a trivial "permit all" PF ruleset? When i took off scrub & altq "No buffer space available" messages were gone, but dhclient did still renew the same address. > Does the problem go away if you use a trivial IPFW "permit all" > instead of PF? Old ipfw rules seem to be working ok. So it's probably something in my pf-rules, have to rewrite and test again. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 09:38:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 600A016A41F for ; Wed, 10 Aug 2005 09:38:44 +0000 (GMT) (envelope-from bu7cher@yandex.ru) Received: from mail.rdu.kirov.ru (ns.rdu.kirov.ru [217.9.151.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id A677043D46 for ; Wed, 10 Aug 2005 09:38:43 +0000 (GMT) (envelope-from bu7cher@yandex.ru) Received: from kirov.so-cdu.ru (kirov [172.21.81.1]) by mail.rdu.kirov.ru (Postfix) with ESMTP id B345F115636; Wed, 10 Aug 2005 13:38:41 +0400 (MSD) Received: from kirov.so-cdu.ru (localhost [127.0.0.1]) by rdu.kirov.ru (Postfix) with SMTP id 94FEF15C2E; Wed, 10 Aug 2005 13:38:41 +0400 (MSD) Received: by rdu.kirov.ru (Postfix, from userid 1014) id 5E72C15C5A; Wed, 10 Aug 2005 13:38:41 +0400 (MSD) Received: from [172.21.81.52] (elsukov.kirov.so-cdu.ru [172.21.81.52]) by rdu.kirov.ru (Postfix) with ESMTP id 46CDB15C50; Wed, 10 Aug 2005 13:38:41 +0400 (MSD) Message-ID: <42F9CB0B.1090403@yandex.ru> Date: Wed, 10 Aug 2005 13:38:19 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "O. Hartmann" , FreeBSD Mailing List References: <42F7F7E8.1020507@mail.uni-mainz.de> In-Reply-To: <42F7F7E8.1020507@mail.uni-mainz.de> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 09:38:44 -0000 O. Hartmann wrote: > Sometimes I get this error: > ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 > while the machine still keeps working. Check your disks with MHDD (http://mhdd.com/). -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 10:37:41 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A141616A41F for ; Wed, 10 Aug 2005 10:37:41 +0000 (GMT) (envelope-from dmitry.mityugov@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id A101D43D53 for ; Wed, 10 Aug 2005 10:37:40 +0000 (GMT) (envelope-from dmitry.mityugov@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so101960wra for ; Wed, 10 Aug 2005 03:37:39 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Fh7UEIbP1XXjWPo22jI98mB7paJlsBdOZZqql445U7wpoTFY7JUSwzA7EecwIxz3ugqG/gczegas8ABanUvA2kAeSh0DgLbBYYTg6qcnJmTbDK31IZ0h888C9Y6wlLe5oaiTlmKiSgBmsN90BH3o1uz388dbAAW9TgKj0+0Upr8= Received: by 10.54.57.32 with SMTP id f32mr351580wra; Wed, 10 Aug 2005 03:37:39 -0700 (PDT) Received: by 10.54.56.33 with HTTP; Wed, 10 Aug 2005 03:37:38 -0700 (PDT) Message-ID: Date: Wed, 10 Aug 2005 14:37:38 +0400 From: Dmitry Mityugov To: Unix In-Reply-To: <42F9C971.9070206@dominique-werner.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 10:37:41 -0000 On 8/10/05, Unix wrote: ... > I thought the WD Raptors were supposed to replace the SCSI for that > purpose. I used to run one in a Powermac and performance wise it behaved > very well, unfortunately I haven't had the chance to test the 30 or 70 > GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 > or server use anyway ... There are Maxtor MaXLine II and III, and perhaps several other models, that are supposed to work 24/7. --=20 Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements "We live less by imagination than despite it" - Rockwell Kent, "N by E" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 10:39:23 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FA2916A41F for ; Wed, 10 Aug 2005 10:39:23 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 58BC143D67 for ; Wed, 10 Aug 2005 10:39:18 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 42571 invoked from network); 10 Aug 2005 10:39:17 -0000 Received: from unknown (HELO ?192.168.1.11?) (unknown) by unknown with SMTP; 10 Aug 2005 10:39:17 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42F9D951.8030407@dominique-werner.com> Date: Wed, 10 Aug 2005 12:39:13 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Mityugov References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 10:39:23 -0000 Dmitry Mityugov wrote: >On 8/10/05, Unix wrote: >... > > >>I thought the WD Raptors were supposed to replace the SCSI for that >>purpose. I used to run one in a Powermac and performance wise it behaved >>very well, unfortunately I haven't had the chance to test the 30 or 70 >>GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 >>or server use anyway >> >> >... > >There are Maxtor MaXLine II and III, and perhaps several other models, >that are supposed to work 24/7. > > > Yes, but I don't like Maxtor drives, the ones I've used always failed after a year or less than a year... From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 10:53:05 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6105716A420 for ; Wed, 10 Aug 2005 10:53:05 +0000 (GMT) (envelope-from dmitry.mityugov@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9667E43D49 for ; Wed, 10 Aug 2005 10:53:04 +0000 (GMT) (envelope-from dmitry.mityugov@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so103948wra for ; Wed, 10 Aug 2005 03:53:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=i2P3/nptpffXO4QAoukI92D8fMiLQxPDgDmlBUt25vXD2sBawj/KYs6Lqskik+0FLUsMykCEcb+vISccbBIbuMsrubFxuiOI8HP1qCFIO4MgDqxJKkb2iUTBPNwrZIEukSRMphPw3GAJPgjULJ2vG7aZKtLMkrbnGpHr35TTjBY= Received: by 10.54.43.48 with SMTP id q48mr378178wrq; Wed, 10 Aug 2005 03:53:03 -0700 (PDT) Received: by 10.54.56.33 with HTTP; Wed, 10 Aug 2005 03:53:03 -0700 (PDT) Message-ID: Date: Wed, 10 Aug 2005 14:53:03 +0400 From: Dmitry Mityugov To: Unix In-Reply-To: <42F9D951.8030407@dominique-werner.com> Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> <42F9D951.8030407@dominique-werner.com> Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 10:53:05 -0000 T24gOC8xMC8wNSwgVW5peCA8dW5peEBkb21pbmlxdWUtd2VybmVyLmNvbT4gd3JvdGU6Cj4gRG1p dHJ5IE1pdHl1Z292IHdyb3RlOgo+IAo+ID5PbiA4LzEwLzA1LCBVbml4IDx1bml4QGRvbWluaXF1 ZS13ZXJuZXIuY29tPiB3cm90ZToKPiA+Li4uCj4gPgo+ID4KPiA+PkkgdGhvdWdodCB0aGUgV0Qg UmFwdG9ycyB3ZXJlIHN1cHBvc2VkIHRvIHJlcGxhY2UgdGhlIFNDU0kgZm9yIHRoYXQKPiA+PnB1 cnBvc2UuIEkgdXNlZCB0byBydW4gb25lIGluIGEgUG93ZXJtYWMgYW5kIHBlcmZvcm1hbmNlIHdp c2UgaXQgYmVoYXZlZAo+ID4+dmVyeSB3ZWxsLCB1bmZvcnR1bmF0ZWx5IEkgaGF2ZW4ndCBoYWQg dGhlIGNoYW5jZSB0byB0ZXN0IHRoZSAzMCBvciA3MAo+ID4+R0IgV0QgUmFwdG9yIFNBVEEgaW4g RnJlZUJTRC4uUy9BVEEgZHJpdmVzIHNob3VsZCBuZXZlciBiZSB1c2VkIGZvciAyNC83Cj4gPj5v ciBzZXJ2ZXIgdXNlIGFueXdheQo+ID4+Cj4gPj4KPiA+Li4uCj4gPgo+ID5UaGVyZSBhcmUgTWF4 dG9yIE1hWExpbmUgSUkgYW5kIElJSSwgYW5kIHBlcmhhcHMgc2V2ZXJhbCBvdGhlciBtb2RlbHMs Cj4gPnRoYXQgYXJlIHN1cHBvc2VkIHRvIHdvcmsgMjQvNy4KPiA+Cj4gPgo+ID4KPiBZZXMsIGJ1 dCBJIGRvbid0IGxpa2UgTWF4dG9yIGRyaXZlcywgdGhlIG9uZXMgSSd2ZSB1c2VkIGFsd2F5cyBm YWlsZWQKPiBhZnRlciBhIHllYXIgb3IgbGVzcyB0aGFuIGEgeWVhci4uLgoKV2VzdGVybiBEaWdp dGFsIHByb2R1Y2VzIHNpbWlsYXIgZHJpdmVzIGFzIHdlbGwgLSBmcm9tCmh0dHA6Ly9zdG9yZS53 ZXN0ZXJuZGlnaXRhbC5jb20vcHJvZHVjdC5hc3A/c2t1PTI3MDA3Mjk6IC4uLiIyNHg3IDEwMCUK ZHV0eSBjeWNsZZZ0aGUgaGlnaGVzdCBhdmFpbGFibGUgcmVsaWFiaWxpdHkgcmF0aW5nIG9uIGhp Z2ggY2FwYWNpdHkKZHJpdmVzIi4uLgoKLS0gCkRtaXRyeSBNaXR5dWdvdiwgU3QuIFBldGVyc2J1 cmcsIFJ1c3NpYQpJIGlnbm9yZSBhbGwgbWVzc2FnZXMgd2l0aCBjb25maWRlbnRpYWxpdHkgc3Rh dGVtZW50cwoKIldlIGxpdmUgbGVzcyBieSBpbWFnaW5hdGlvbiB0aGFuIGRlc3BpdGUgaXQiIC0g Um9ja3dlbGwgS2VudCwgIk4gYnkgRSIK From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 10:55:05 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D911E16A420 for ; Wed, 10 Aug 2005 10:55:05 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 03E9743D46 for ; Wed, 10 Aug 2005 10:55:04 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 14628 invoked from network); 10 Aug 2005 10:55:03 -0000 Received: from unknown (HELO ?192.168.1.11?) (unknown) by unknown with SMTP; 10 Aug 2005 10:55:03 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42F9DD04.9010703@dominique-werner.com> Date: Wed, 10 Aug 2005 12:55:00 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Mityugov References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> <42F9D951.8030407@dominique-werner.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 10:55:06 -0000 Dmitry Mityugov wrote: >On 8/10/05, Unix wrote: > > >>Dmitry Mityugov wrote: >> >> >> >>>On 8/10/05, Unix wrote: >>>... >>> >>> >>> >>> >>>>I thought the WD Raptors were supposed to replace the SCSI for that >>>>purpose. I used to run one in a Powermac and performance wise it behaved >>>>very well, unfortunately I haven't had the chance to test the 30 or 70 >>>>GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 >>>>or server use anyway >>>> >>>> >>>> >>>> >>>... >>> >>>There are Maxtor MaXLine II and III, and perhaps several other models, >>>that are supposed to work 24/7. >>> >>> >>> >>> >>> >>Yes, but I don't like Maxtor drives, the ones I've used always failed >>after a year or less than a year... >> >> > >Western Digital produces similar drives as well - from >http://store.westerndigital.com/product.asp?sku=2700729: ..."24x7 100% >duty cycle–the highest available reliability rating on high capacity >drives"... > > > thanks, I need to get some new drives anyway...and WD was on my list... From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 11:01:12 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 046B316A41F; Wed, 10 Aug 2005 11:01:12 +0000 (GMT) (envelope-from mathijs@brands.name) Received: from amsfep19-int.chello.nl (amsfep11-int.chello.nl [213.46.243.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4905543D53; Wed, 10 Aug 2005 11:01:09 +0000 (GMT) (envelope-from mathijs@brands.name) Received: from crooked.net ([62.108.23.9]) by amsfep19-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050810110108.TIIE18546.amsfep19-int.chello.nl@crooked.net>; Wed, 10 Aug 2005 13:01:08 +0200 Received: from [62.58.162.149] (unknown [62.58.162.149]) by crooked.net (Postfix) with ESMTP id 16050506AE6; Wed, 10 Aug 2005 13:01:07 +0200 (CEST) Message-ID: <42F9DE71.20607@brands.name> Date: Wed, 10 Aug 2005 13:01:05 +0200 From: Mathijs Brands User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Unix References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com><42F92FEE.8060305@mail.uni-mainz.de><90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp><42F9C971.9070206@dominique-werner.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request)LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 11:01:12 -0000 On 8/10/05, Unix wrote: >I thought the WD Raptors were supposed to replace the SCSI for that >purpose. I used to run one in a Powermac and performance wise it behaved >very well, unfortunately I haven't had the chance to test the 30 or 70 >GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 >or server use anyway > I have a FreeBSD 6.0-BETA2 machine that's using a WD Raptor 36 GB using the on-board controller (VIA 8237) of the Asus A7V880 motherboard and it works perfectly. The most taxing thing it runs is the occasional buildworld or (re)build of KDE3 though... Cheers, Mathijs From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 11:55:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99D4E16A41F for ; Wed, 10 Aug 2005 11:55:20 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id F017243D46 for ; Wed, 10 Aug 2005 11:55:19 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j7ABtIPQ009766 for ; Wed, 10 Aug 2005 06:55:18 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Wed Aug 10 06:55:18 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j7ABtIXS009764 for freebsd-stable@freebsd.org; Wed, 10 Aug 2005 06:55:18 -0500 (CDT) (envelope-from karl) Date: Wed, 10 Aug 2005 06:55:18 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050810115518.GA9703@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050810024618.GA8198@drjekyll.mkbuelow.net> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 11:55:20 -0000 On Wed, Aug 10, 2005 at 04:46:18AM +0200, Matthias Buelow wrote: > Karl Denninger wrote: > > >SII chipsets were ok in 4.x, but the newer ATA code broke badly with them. > >I've had a PR open on this since February, and many others have reported > >similar issues. The problems still exist in the 6.x-BETA releases I've > >checked out, and are in some cases MORE severe (for me anyway) than they are > >in 5.4. > > Well, it doesn't affect just the SII chips.. I see the same on an > Intel ICH6 chipset but never after the kernel has mounted the root > fs. Sometimes it takes several attempts until it manages to do so, > though. The machine works w/o any such problems on other OSes. I've > deferred update of another machine (which is a hosted box and cannot > afford random hangs at boot) because of general flakeyness of the > ATA/SATA code in 5.4 (significantly worse than with 5.3, imho). If > these issues don't go away completely soon (in 6.x) I'll have to > look for some alternative system which doesn't make such a fuss > with mainstream hardware. > > mkb. Yep. 4.x was perfectly stable on the hardware in question here. The "feature set" of the newer ATA code may be better, but the stability is significantly worse. IMHO "requiring" 3ware cards for drives to work right is such a huge step backwards that for the lower-end server user, and virtually all desktop users, it will basically kill FreeBSD off. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 12:13:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E31DE16A41F for ; Wed, 10 Aug 2005 12:13:45 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E7C643D58 for ; Wed, 10 Aug 2005 12:13:43 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice6.sentex.ca (pumice6.sentex.ca [64.7.153.21]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j7ACCjgu084191 for ; Wed, 10 Aug 2005 08:12:45 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice6.sentex.ca (8.13.3/8.13.3) with ESMTP id j7ACDgWT050007; Wed, 10 Aug 2005 08:13:42 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id j7ACDdsb031439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Aug 2005 08:13:39 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Wed, 10 Aug 2005 08:15:50 -0400 To: Matthias Buelow , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050810024618.GA8198@drjekyll.mkbuelow.net> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.51 on 64.7.153.21 Cc: Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 12:13:46 -0000 At 10:46 PM 09/08/2005, Matthias Buelow wrote: >Karl Denninger wrote: > > >SII chipsets were ok in 4.x, but the newer ATA code broke badly with them. > >I've had a PR open on this since February, and many others have reported > >similar issues. The problems still exist in the 6.x-BETA releases I've > >checked out, and are in some cases MORE severe (for me anyway) than they are > >in 5.4. > >Well, it doesn't affect just the SII chips.. I see the same on an >Intel ICH6 chipset but never after the kernel has mounted the root >fs. Sometimes it takes several attempts until it manages to do so, >though. The machine works w/o any such problems on other OSes. I've I have ICH6 boxes and they run just fine without issue. Have you checked to see if it actually has bad sectors or is a problem with your tray (if you use one) [verify1]% dmesg | grep -i ich uhci0: port 0xe000-0xe01f at device 29.0 on pci0 usb0: on uhci0 uhci1: port 0xe100-0xe11f at device 29.1 on pci0 usb1: on uhci1 uhci2: port 0xe200-0xe21f at device 29.2 on pci0 usb2: on uhci2 uhci3: port 0xe300-0xe31f at device 29.3 on pci0 usb3: on uhci3 fxp0: port 0xd000-0xd03f mem 0xd0000000-0xd0000fff irq 10 at device 8.0 on pci1 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.2 on pci0 [verify1]% Master: ad0 Serial ATA v1.0 ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 13:32:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06ED316A41F for ; Wed, 10 Aug 2005 13:32:01 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70CB043D46 for ; Wed, 10 Aug 2005 13:32:00 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j7ADVxZY010968 for ; Wed, 10 Aug 2005 08:31:59 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Wed Aug 10 08:31:59 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j7ADVxqR010966 for freebsd-stable@freebsd.org; Wed, 10 Aug 2005 08:31:59 -0500 (CDT) (envelope-from karl) Date: Wed, 10 Aug 2005 08:31:59 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050810133159.GA10150@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 13:32:01 -0000 On Wed, Aug 10, 2005 at 08:15:50AM -0400, Mike Tancsa wrote: > At 10:46 PM 09/08/2005, Matthias Buelow wrote: > >Karl Denninger wrote: > > > >>SII chipsets were ok in 4.x, but the newer ATA code broke badly with them. > >>I've had a PR open on this since February, and many others have reported > >>similar issues. The problems still exist in the 6.x-BETA releases I've > >>checked out, and are in some cases MORE severe (for me anyway) than they > >are > >>in 5.4. > > > >Well, it doesn't affect just the SII chips.. I see the same on an > >Intel ICH6 chipset but never after the kernel has mounted the root > >fs. Sometimes it takes several attempts until it manages to do so, > >though. The machine works w/o any such problems on other OSes. I've > > I have ICH6 boxes and they run just fine without issue. Have you checked > to see if it actually has bad sectors or is a problem with your tray (if > you use one) > > [verify1]% dmesg | grep -i ich > uhci0: port > 0xe000-0xe01f at device 29.0 on pci0 > usb0: on uhci0 > uhci1: port > 0xe100-0xe11f at device 29.1 on pci0 > usb1: on uhci1 > uhci2: port > 0xe200-0xe21f at device 29.2 on pci0 > usb2: on uhci2 > uhci3: port > 0xe300-0xe31f at device 29.3 on pci0 > usb3: on uhci3 > fxp0: port 0xd000-0xd03f mem 0xd0000000-0xd0000fff > irq 10 at device 8.0 on pci1 > atapci0: port > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.2 on pci0 > [verify1]% I have an ICH5 on my motherboard and it works fine - it is under heavy use and has had no trouble. atapci1: port 0xfea0-0xfeaf,0xfe30-0xfe33,0xfe20 -0xfe27,0xfe10-0xfe13,0xfe00-0xfe07 irq 18 at device 31.2 on pci0 There's two potential issues here - if it is failing during the boot process that's a completely different set of code - and thus potential problem - than failing while running. I've not had booting problems with the ICH5, and no failures while running. On the other hand the SII chipset boards I have (two of them) can be RELIABLY forced to fail within minutes. If there are no drives in the mirror set on something else, the data on the disk(s) is toast - if so they detach and the non-SII-attached disks end up carrying the data. This is across two different manufacturers of drives (Hitachi and Maxtor) and FOUR separate disks, all four of which smartmontools bless as operating properly and all of which ran just fine under 4.x. Oh, and all of which work just fine on a 3ware 8502 card. I've read the reports that basically boil down to "the SII chipset sucks, don't use it" BUT (1) it works under 4.x, (2) it works under other operating systems and (3) the FreeBSD folks who are saying it doesn't work don't have the courage of their statements to make them in the official release documents (e.g. the release notes, hardware compatability guide or erratta.) So while the chipset may or may not be "less desireable", what is clear is that the problems with it are not insurmountable - they've just not been taken care of in the newer ATA code. Arguments that this is about resources (e.g. the developers don't have a card and need anything from a board to a complete system to have any chance of fixing it) ring pretty hollow to me. This is an EXTREMELY popular chipset, is on both the Adaptec and Bustek cards commonly sold with machines and at retail, and cards with that chipset can be had for as little as $30 (and up, of course.) In addition I've yet to find a SATA drive that WON'T fail with this board - or a motherboard that is stable with it on FreeBSD 5.4 or 6.x - it is definitely NOT linked to the drive and I have no confidence its linked to the motherboard chipset in any way. Further, smartmontools says the disks that do fail aren't defective, and it worked just fine under 4.x. Also, I've yet to see a developer commit on the list that they WILL fix it if such a controller board is forthcoming (and will return the board when they're done) - I've got two of these cards here (choose between Adaptec and Bustek) and would be happy to UPS one to someone IF I had a firm commitment that 6.x would NOT go out without this being addressed and that the board would be returned to me when work was complete. Finally, while the 3ware card works fine, it doesn't support hot plug. The SII chipset claims to, and so does the ATA code, but the 3ware card runs on a different driver - which doesn't (either claim to or actually accomplish it.) So while using a 3ware card solves the "blows chunks and dies" problem, you are back to the lack of functionality that was present in 4.x - no hot drive swap support. (This is mitigated somewhat by the 3ware management tools, which do allow reconnection and work - but its a manual operation.) This entirely voids the argument for ATAng being a "step forward" - support of hot plug and other functionality improvements - in the first place, since you can't actually USE that capability if you are forced to a 3ware board! Again, I think the ATA-xx issues are of a magnitude sufficient to basically kill FreeBSD going forward in the desktop application arena. If all FreeBSD as an organization cares about is the large server marketplace, I guess that works. But small office / home office file servers are going to be SATA based and moderately-data systems with low entropy (e.g. 300-600gb) are FAR more cost effective to deploy on SATA than on SCSI, and easily meet the performance and data stability requirements. If FreeBSD is unstable on those systems without putting in specialized, vendor-supported hardware, then FreeBSD may well be ceding those segments of the Unix marketplace to something else (e.g. Linux.) I believe that would be most unfortunate - I have been supporting FreeBSD as a platform for the code I sell in these environments exclusively for more than five years, and ran it as the only Unix OS we used at the ISP I used to own. My stance has been for the last five years (since selling my ISP) that if you want me to support code that I sell you have to be running it on FreeBSD. FreeBSD has earned this position by being a superior solution in all respects, but most particularly in the area that is most important - operating stability. If I start having customers run into stability problems with 5.x and beyond on hardware that properly worked under 4.x, I will be forced to port the code over to Linux, as I cannot force people to run 4.x as the base OS when its been EOL'd (other than for security fixes) and yet their hardware simply doesn't work right with the current FreeBSD code. As things stand I am adding a STRONG warning in my product release notes stating that if you have a SII chipset SATA controller and run any version of FreeBSD from 5.4 onward you are doing so at your own risk and against my specific recommendations. The warning will be removed from my products when the PR that I filed in February is addressed OR FreeBSD places an equally strong warning in their release notes, rendering the warning unnecessary. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 13:48:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E56516A41F for ; Wed, 10 Aug 2005 13:48:59 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C622443D48 for ; Wed, 10 Aug 2005 13:48:58 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j7ADm1WT090863 for ; Wed, 10 Aug 2005 09:48:01 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.3/8.13.3) with ESMTP id j7ADmvJ5034526 for ; Wed, 10 Aug 2005 09:48:57 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id j7ADmse1031700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 10 Aug 2005 09:48:56 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Wed, 10 Aug 2005 09:51:03 -0400 To: freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20050810133159.GA10150@FS.denninger.net> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.51 on 64.7.153.26 Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 13:48:59 -0000 At 09:31 AM 10/08/2005, Karl Denninger wrote: >Also, I've yet to see a developer commit on the list that they WILL fix it if >such a controller board is forthcoming (and will return the board when >they're >done) - I've got two of these cards here (choose between Adaptec and Bustek) >and would be happy to UPS one to someone IF I had a firm commitment that 6.x >would NOT go out without this being addressed and that the board would be >returned to me when work was complete. You demand to see support for this chipset fixed, yet, you cant pony up a measly hundred bucks to donate the card to the developer who is not being paid to develop anything. ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 14:41:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51B9316A41F for ; Wed, 10 Aug 2005 14:41:50 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 861FE43D48 for ; Wed, 10 Aug 2005 14:41:49 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j7AEfmFv011942 for ; Wed, 10 Aug 2005 09:41:48 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Wed Aug 10 09:41:48 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j7AEfmgH011940 for freebsd-stable@freebsd.org; Wed, 10 Aug 2005 09:41:48 -0500 (CDT) (envelope-from karl) Date: Wed, 10 Aug 2005 09:41:48 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050810144148.GB10150@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 14:41:50 -0000 On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote: > At 09:31 AM 10/08/2005, Karl Denninger wrote: > > >Also, I've yet to see a developer commit on the list that they WILL fix it > >if > >such a controller board is forthcoming (and will return the board when > >they're > >done) - I've got two of these cards here (choose between Adaptec and > >Bustek) > >and would be happy to UPS one to someone IF I had a firm commitment that > >6.x > >would NOT go out without this being addressed and that the board would be > >returned to me when work was complete. > > You demand to see support for this chipset fixed, yet, you cant pony up a > measly hundred bucks to donate the card to the developer who is not being > paid to develop anything. > > ---Mike I have "demanded" nothing Mike. I have stated VERY clearly, however, that I've been one of FreeBSD's loudest evangelists, to the point that I won't support the code I both give away and sell on ANYTHING OTHER THAN FreeBSD - at least so far. That evangalism dates back to the mid 90s when I ran my own ISP, and refused multiple "requests" (sweetened with various offers) to run my back office on all sorts of things. One of those "requests" came from Microsoft (to run on NT, specifcally for our back office functions.) I assure you that their offer, made in confidence in my conference room, was quite "sweet" - and was flatly turned down. I do not believe that it is unreasonable in any way, shape or form to expect that hardware that is in mass circulation (that is, NOT deprecated stuff that nobody sells or makes anymore) will NOT be broken from one release to the next when it was working just fine previously. I expect FreeBSD to magically support every piece of crap that comes down the pipe, and am well-aware that there's a lot of that sort of thing out there. But this isn't the case in this instance. This is hardware that worked perfectly well on 4.x (and in fact still does) but broke immediately and severely with the newer ATA code. The FreeBSD team KNOWS THIS, in that I filed a PR on it in February, yet there is nothing in the Errata or hardware notes (as of AUGUST!) warning people that they risk severe data corruption if they attempt to use these controllers on releases 5.4 and beyond. In addition, the "fix" propounded upon for this problem (buy a 3ware card), which I finally did after watching my PR sit unattended for six months, led to a SECOND surprise - that the much-touted reason for the ATA-ng code in the first place, that is, a more rich feature environment (specifically hot plug support) IS NOT IN THE FIX PROPOUNDED UPON! That is, I get to go BACK to the 4.x feature set in pursuit of the fix! Nonetheless I'm willing to SEND A BOARD to the developer IF I get in return a commitment (in public, right here) from the development/release teams that 6.x WILL NOT GO OUT THE DOOR UNTIL THIS PROBLEM IS ADDRESSED. I am requesting the board back after the fix is purportedly in the source tree , and drop the warnings from my product documentation. UPSing the board back to me (or sending it first class US mail) will cost all of a couple of bucks. What I get in return for this offer (I own the board, I will pay the UPS charge anywhere in the US to send it out) is a personal attack that I'm too "miserly" to not pony up MONEY - when I've already offered to send what the money would BUY. Is it REALLY true that the developers DO NOT HAVE a card that has this problem? If so I have TWO which exhibit the problem (pick your brand, Adaptec or Bustek) and have offered to send ONE of the two to a developer. So why do they want MONEY, when I have and am offering better - a KNOWN TROUBLESOME BOARD? What is the money going to BUY Mike? A board - or beer? If a board, I have one. If beer, be honest enough to say so. I ALSO (about two weeks ago) offered to give any developer who wanted to work on this a login on my Sandbox machine, configured with the bad controller and a disk exhibiting the problem in it, plus a boot disk on a "SAFE" controller in the same box. Gmirror appears to insure (from my testing) that if/when the disk disconnects and blows chunks that operating system integrity is not compromised. Therefore, said developer(s) could work SAFELY on this problem (without risk to their development machines - it'd be at MY risk to MY environment) until they are satisfied that its fixed. At that point I will once again run my validation tests on the box and see if it remains stable, as a further verification that it truly is fixed. If it passes THAT test, then of course the final verification would come from the community at large. That machine has 6.0-BETA on it and they are free to have at it at will via SSH. It also has a full CVS set on it so the FULL development environment is available to whoever wishes to work on it and other than sharing a network connection with production machines is entirely isolated - so there is no risk to my production machines as a consequence of what someone does to this box. (That is, I won't be pissed off if you blow it up and I have to reload it from scratch - that's its PURPOSE.) If it gets wedged to the point that it can't be rebooted remotely a quick email, phone call or SMS message to my cell phone will elicit a push on the big red switch for them. Said box is a Dell PowerEDGE 400SC - plenty of beef to get the job done (2.4ghz HT P4) THAT offer drew no response - not a "no thanks", not a "sure, contact me to setup a login and password" - nothing. That says to me that there is no intent - or desire - to actually fix it. Again, if the goal is to FIX IT, I've now offered TWO paths for the developers to do so, at my expense - one a couple of weeks ago, and a second now (that I've gone out and bought a 3ware board, and thus have TWO of the troublesome cards around.) What I get back is a request for MONEY instead of a known environment that exhibits the problem?! Uh, why do I think that's a request to throw money down a black hole instead of actually solving the problem? I understand if the developers simply do not want to support the SiI chipset AT ALL, and have declared it "broken". That's cool, even though I believe that such a step will lead to mass-defections among the desktop and small-office server marketplace for FreeBSD. BUT IF THIS IS THE APPROACH BEING TAKEN THE DEVELOPMENT AND RELEASE TEAMS HAVE AN OBLIGATION TO PROPERLY AND HONESTLY REPRESENT THIS IN THE RELEASE NOTES SO THAT I, AND OTHERS, DO NOT GET A "SURPRISE" AND CHASE OUR TAILS ASSUMING WE HAVE DEFECTIVE DISK DRIVES WHEN THE REAL PROBLEM IS UNSUPPORTED HARDWARE! -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 15:36:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C65416A41F for ; Wed, 10 Aug 2005 15:36:35 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from audi.websitewelcome.com (audi.websitewelcome.com [67.19.210.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id B88AC43D53 for ; Wed, 10 Aug 2005 15:36:33 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from adsl-065-013-105-239.sip.tys.bellsouth.net ([65.13.105.239]:2659 helo=[192.168.1.33]) by audi.websitewelcome.com with esmtpa (Exim 4.50) id 1E2sd2-0005iC-Po for freebsd-stable@freebsd.org; Wed, 10 Aug 2005 10:36:28 -0500 Message-ID: <42FA1F16.7000204@goldsword.com> Date: Wed, 10 Aug 2005 11:36:54 -0400 From: "J. T. Farmer" Organization: GoldSword Systems User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.7) Gecko/20050414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> In-Reply-To: <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - audi.websitewelcome.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - goldsword.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 15:36:35 -0000 Mike Tancsa wrote: > At 09:31 AM 10/08/2005, Karl Denninger wrote: > >> Also, I've yet to see a developer commit on the list that they WILL >> fix it if >> such a controller board is forthcoming (and will return the board >> when they're >> done) - I've got two of these cards here (choose between Adaptec and >> Bustek) >> and would be happy to UPS one to someone IF I had a firm commitment >> that 6.x >> would NOT go out without this being addressed and that the board >> would be >> returned to me when work was complete. > > > You demand to see support for this chipset fixed, yet, you cant pony > up a measly hundred bucks to donate the card to the developer who is > not being paid to develop anything. Why? It was claimed that the code was developed to support this chipset. Was that done in the dark, without hardware? And why must it be a hardware donation? Karl has offered access to the hardware. Asking to get it back afterwards is a reasonable thing. If the developer wants to keep the card as part of a verification hardware suite, then they should open their mouth and say so. I suspect that Karl, and many other people, would be more forthcoming with such donations if 1.) They were asked in a reasonable manner, 2.) The hardware in question have not already been listed as working under 5.x, and 3.) They had some assurance that the problem would be fixed. And finally, the problem has been reported in 5.4 and apparently in 6.0-Beta _not _only_ for the SII chipset & SATA, but also for some of the Intel ICH chipsets. And others, such as myself, are seeing the same problem with plain PATA drives and controllers that are listed as being supported by the ata driver. In my case, a vanilla, OLD but working Via KT266A/8235 chipset MB _will_not_boot an install kernel unless booted in safe mode. I don't have the resources to just give away hardware or buy replacements, just to run FreeBSD as my desktop/development machine. It runs WinXP and Linux just fine. However I _want_ to run FreeBSD. Part of the that machine's rational is so that I can contribute in my areas of interest (sound & video editing/production tools, documentation). I chose to install 5.4, the PRODUCTION version, because I did not want any surprises, did not want to be hacking a basic system functions. At what point do I give up and just reformat the FreeBSD partition and either release it to use with WinXP or install Linux? Now mind you, I've used FreeBSD, as a production platform, since 2.0.X. I've survived a fair number of "bumps." But I'm at the point that I really want the things that are claimed to work to just work. I continue to run my servers under 4.X because or all the upheaval in 5.0/5.1/etc. But 5.4 was supposed to have those teething problems behind it. And the so far the only answer I get is try the ATA MkIII patches for a partial fix, move to 6.0 for a real solution. So when will 6.X really be Stable? Yes, I understand that the RE is working on getting 6.0 out the door. But what users are trying to tell you is that we need an answer for these problems. If the production release is broken for certain hardware, say so. If FreeBSD developers would rather work on big hairy server oriented problems, then say so. If we have to run beta code to get old hardware to work, then say so. Then we can make a choice as to what we run or try to use. If no one is interested in making FreeBSD work on the vanilla hardware that is out there, then say so. If FreeBSD is only going to run on expensive hand picked hardware (the Sun approach) then say so. Those of us who want to switch desktops and light duty servers to FreeBSD will give up and move to Linux. OR back to WinXP. John ---------------------------------------------------------------------- John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 15:44:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B54B16A41F for ; Wed, 10 Aug 2005 15:44:22 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D5F243D46 for ; Wed, 10 Aug 2005 15:44:21 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so159207wra for ; Wed, 10 Aug 2005 08:44:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=M9DX5p/RxbDgpBxcmdmdGeK8SXfs/7X5vC+hm7p8sU2w4JZRV2JU6LMylpOf1YURn/0JnSnz2aeK+Wvnd/jBuEC4pbSS2pNLlQHAWMDdQb4UtU0Cyem7Ke18m+Tu+YQJWMJjfkzfN9GAnW6Vkh7sOwclHjmKW/aT/x0RUVETw4c= Received: by 10.54.48.76 with SMTP id v76mr529514wrv; Wed, 10 Aug 2005 08:44:20 -0700 (PDT) Received: by 10.54.29.26 with HTTP; Wed, 10 Aug 2005 08:44:20 -0700 (PDT) Message-ID: <790a9fff0508100844a7e5435@mail.gmail.com> Date: Wed, 10 Aug 2005 10:44:20 -0500 From: Scot Hetzel To: freebsd-stable@freebsd.org In-Reply-To: <20050810144148.GB10150@FS.denninger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> Cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 15:44:22 -0000 On 8/10/05, Karl Denninger wrote: > On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote: > > At 09:31 AM 10/08/2005, Karl Denninger wrote: > > > > >Also, I've yet to see a developer commit on the list that they WILL fi= x it > > >if > > >such a controller board is forthcoming (and will return the board when > > >they're > > >done) - I've got two of these cards here (choose between Adaptec and > > >Bustek) > > >and would be happy to UPS one to someone IF I had a firm commitment th= at > > >6.x > > >would NOT go out without this being addressed and that the board would= be > > >returned to me when work was complete. > > > > You demand to see support for this chipset fixed, yet, you cant pony up= a > > measly hundred bucks to donate the card to the developer who is not bei= ng > > paid to develop anything. > > > > ---Mike >=20 > I have "demanded" nothing Mike. >=20 I agree Mike's wording was a little strong, but we have seen you request strongly that some one fix this problem. Have you contacted S=F8ren, to see if he has the troublesome hardware? Also contact S=F8ren directly with your offer to supply a troublesome board, and/or access to a system that displays the problem. More than likely he would agree to return the board once he has a proper fix for the problem. Currently, he is the only one I am aware of who is actively working on the ATA code (ata-ng, ata-mkIII). Scot --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 15:46:24 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7975D16A41F for ; Wed, 10 Aug 2005 15:46:24 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id C49A843D53 for ; Wed, 10 Aug 2005 15:46:23 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 34533 invoked from network); 10 Aug 2005 15:46:22 -0000 Received: from unknown (HELO ?192.168.1.10?) (unknown) by unknown with SMTP; 10 Aug 2005 15:46:22 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42FA213D.1070401@dominique-werner.com> Date: Wed, 10 Aug 2005 17:46:05 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "J. T. Farmer" References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <42FA1F16.7000204@goldsword.com> In-Reply-To: <42FA1F16.7000204@goldsword.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 15:46:24 -0000 Yes, I agree. I don't think anyone wants to blame the entire FreeBSD community for not being up to date on everything but if it is a known problem we should know. I know that the developers work for free and I, for one, appreciate all the work they've done. I know I would help if I could..but my programming knowledges are too poor..if there is a problem though, like the one with the SII and ICH chipsets maybe a FreeBSD developer should send an email asking for our help and I bet there would be plenty of people to test and script and like... J. T. Farmer wrote: > Mike Tancsa wrote: > >> At 09:31 AM 10/08/2005, Karl Denninger wrote: >> >>> Also, I've yet to see a developer commit on the list that they WILL >>> fix it if >>> such a controller board is forthcoming (and will return the board >>> when they're >>> done) - I've got two of these cards here (choose between Adaptec and >>> Bustek) >>> and would be happy to UPS one to someone IF I had a firm commitment >>> that 6.x >>> would NOT go out without this being addressed and that the board >>> would be >>> returned to me when work was complete. >> >> >> >> You demand to see support for this chipset fixed, yet, you cant pony >> up a measly hundred bucks to donate the card to the developer who is >> not being paid to develop anything. > > > Why? It was claimed that the code was developed to support this chipset. > Was that done in the dark, without hardware? And why must it be a > hardware donation? Karl has offered access to the hardware. Asking to > get it back afterwards is a reasonable thing. If the developer wants to > keep the card as part of a verification hardware suite, then they should > open their mouth and say so. I suspect that Karl, and many other people, > would be more forthcoming with such donations if 1.) They were asked > in a reasonable manner, 2.) The hardware in question have not already > been listed as working under 5.x, and 3.) They had some assurance that > the problem would be fixed. > > And finally, the problem has been reported in 5.4 and apparently in > 6.0-Beta _not _only_ for the SII chipset & SATA, but also for some > of the Intel ICH chipsets. And others, such as myself, are seeing the > same problem with plain PATA drives and controllers that are listed > as being supported by the ata driver. > > In my case, a vanilla, OLD but working Via KT266A/8235 chipset MB > _will_not_boot an install kernel unless booted in safe mode. I don't > have > the resources to just give away hardware or buy replacements, just to > run FreeBSD as my desktop/development machine. It runs WinXP and > Linux just fine. However I _want_ to run FreeBSD. Part of the that > machine's rational is so that I can contribute in my areas of interest > (sound & video editing/production tools, documentation). I chose to > install 5.4, the PRODUCTION version, because I did not want any > surprises, did not want to be hacking a basic system functions. > > At what point do I give up and just reformat the FreeBSD partition > and either release it to use with WinXP or install Linux? Now mind > you, I've used FreeBSD, as a production platform, since 2.0.X. I've > survived a fair number of "bumps." But I'm at the point that I really > want the things that are claimed to work to just work. I continue to > run my servers under 4.X because or all the upheaval in 5.0/5.1/etc. > But 5.4 was supposed to have those teething problems behind it. > And the so far the only answer I get is try the ATA MkIII patches for > a partial fix, move to 6.0 for a real solution. > So when will 6.X really be Stable? Yes, I understand that the RE is > working on getting 6.0 out the door. But what users are trying to tell > you is that we need an answer for these problems. If the production > release is broken for certain hardware, say so. If FreeBSD developers > would rather work on big hairy server oriented problems, then say so. > If we have to run beta code to get old hardware to work, then say so. > Then we can make a choice as to what we run or try to use. If > no one is interested in making FreeBSD work on the vanilla hardware > that is out there, then say so. If FreeBSD is only going to run on > expensive hand picked hardware (the Sun approach) then say so. > Those of us who want to switch desktops and light duty servers > to FreeBSD will give up and move to Linux. OR back to WinXP. > > John > > ---------------------------------------------------------------------- > John T. Farmer Owner & CTO GoldSword Systems > jfarmer@goldsword.com 865-691-6498 Knoxville TN > Consulting, Design, & Development of Networks & Software > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 16:27:16 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E15516A41F for ; Wed, 10 Aug 2005 16:27:16 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D77143D46 for ; Wed, 10 Aug 2005 16:27:15 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA8B1D.dip0.t-ipconnect.de [84.170.139.29]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 12B9E33DD5; Wed, 10 Aug 2005 18:30:02 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7AGRKU9001130; Wed, 10 Aug 2005 18:27:21 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7AGRKnI001129; Wed, 10 Aug 2005 18:27:20 +0200 (CEST) (envelope-from mkb) Date: Wed, 10 Aug 2005 18:27:20 +0200 From: Matthias Buelow To: "J. T. Farmer" Message-ID: <20050810162720.GA675@drjekyll.mkbuelow.net> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <42FA1F16.7000204@goldsword.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42FA1F16.7000204@goldsword.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 16:27:16 -0000 J. T. Farmer wrote: >Those of us who want to switch desktops and light duty servers >to FreeBSD will give up and move to Linux. OR back to WinXP. I myself am just waiting for NetBSD 3.0, which will hopefully support the ICH6 SATA stuff I have here (2.0.2 doesn't support it) and then I'll move some machines to it. I don't want to start a flamewar but they seem to have a somewhat higher quality output as of lately.. that is, when they advertise something as "working", one can be pretty confident that it actually does work. mkb. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 16:34:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A7CA16A42B for ; Wed, 10 Aug 2005 16:34:27 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DB7343D55 for ; Wed, 10 Aug 2005 16:34:26 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 49827 invoked from network); 10 Aug 2005 16:34:25 -0000 Received: from unknown (HELO ?192.168.1.10?) (unknown) by unknown with SMTP; 10 Aug 2005 16:34:25 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42FA2C80.50507@dominique-werner.com> Date: Wed, 10 Aug 2005 18:34:08 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <42FA1F16.7000204@goldsword.com> <20050810162720.GA675@drjekyll.mkbuelow.net> In-Reply-To: <20050810162720.GA675@drjekyll.mkbuelow.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 16:34:27 -0000 Matthias Buelow wrote: >J. T. Farmer wrote: > > > >>Those of us who want to switch desktops and light duty servers >>to FreeBSD will give up and move to Linux. OR back to WinXP. >> >> > >I myself am just waiting for NetBSD 3.0, which will hopefully support >the ICH6 SATA stuff I have here (2.0.2 doesn't support it) and then >I'll move some machines to it. I don't want to start a flamewar but >they seem to have a somewhat higher quality output as of lately.. >that is, when they advertise something as "working", one can be pretty >confident that it actually does work. > >mkb. >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > NetBSD 3.0 is also supposed to work somewhat with the Intel HD Audio controller..at least it gets detected...I'm in the same boat..I love FreeBSD and I'd prefer to keep it, I want to buy a Fujitsu MO Drive and I heard it only works in FreeBSD..but if I can't get good audio support in the near future and a stable S/ATA controller I'll consider switching... From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 17:24:07 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86D7B16A41F for ; Wed, 10 Aug 2005 17:24:07 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC5F343D48 for ; Wed, 10 Aug 2005 17:24:06 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from [194.192.25.136] (mac.deepcore.dk [194.192.25.136]) by spider.deepcore.dk (8.13.3/8.13.3) with ESMTP id j7AH9ieY071475; Wed, 10 Aug 2005 19:09:44 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) In-Reply-To: <790a9fff0508100844a7e5435@mail.gmail.com> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Date: Wed, 10 Aug 2005 19:24:01 +0200 To: Scot Hetzel X-Mailer: Apple Mail (2.733) X-mail-scanned: by DeepCore Virus & Spam killer v1.12 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 17:24:07 -0000 On 10/08/2005, at 17:44, Scot Hetzel wrote: > On 8/10/05, Karl Denninger wrote: > >> On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote: >> >>> At 09:31 AM 10/08/2005, Karl Denninger wrote: >>> >>> >>>> Also, I've yet to see a developer commit on the list that they =20 >>>> WILL fix it >>>> if >>>> such a controller board is forthcoming (and will return the =20 >>>> board when >>>> they're >>>> done) - I've got two of these cards here (choose between Adaptec =20= >>>> and >>>> Bustek) >>>> and would be happy to UPS one to someone IF I had a firm =20 >>>> commitment that >>>> 6.x >>>> would NOT go out without this being addressed and that the board =20= >>>> would be >>>> returned to me when work was complete. >>>> >>> >>> You demand to see support for this chipset fixed, yet, you cant =20 >>> pony up a >>> measly hundred bucks to donate the card to the developer who is =20 >>> not being >>> paid to develop anything. >>> >>> ---Mike >>> >> >> I have "demanded" nothing Mike. >> >> > I agree Mike's wording was a little strong, but we have seen you > request strongly that some one fix this problem. > > Have you contacted S=F8ren, to see if he has the troublesome hardware? > > Also contact S=F8ren directly with your offer to supply a troublesome > board, and/or access to a system that displays the problem. More than > likely he would agree to return the board once he has a proper fix for > the problem. Since I came in late in this, I need to know what kind of controller =20 we are talking about, and if the problem is still present in 6.0. I plan to backport ATA from 6.0 to 5-stable when it has settled, so =20 6.0 is the one and only (pre)release to test with and get back to me =20 with the result. - S=F8ren From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 17:35:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18AD616A420 for ; Wed, 10 Aug 2005 17:35:22 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.FreeBSD.org (Postfix) with SMTP id 80B5143D5E for ; Wed, 10 Aug 2005 17:35:17 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 99453 invoked from network); 10 Aug 2005 17:35:16 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; b=hRwwJsnrU3ACtfxZUtC+UFVC453BVZajJ4X3eQArKtu5JFFbfflM2Kwq5lJAGA4p887CDWsNoMfPqMuGVMaCiH59/Qi1K9FV7tXVThxIsh+BLcIr9aQ9TOVoKK55IHjFsBuPxZmERfwIMZEXubcaPK/+wumjN6D3GuI00XFmlFA= ; Received: from unknown (HELO 172.16.0.1) (mikej@70.31.50.81 with login) by smtp102.rog.mail.re2.yahoo.com with SMTP; 10 Aug 2005 17:35:16 -0000 Received: from 172.16.0.199 (SquirrelMail authenticated user mikej) by 172.16.0.1 with HTTP; Wed, 10 Aug 2005 13:35:10 -0400 (EDT) Message-ID: <2420.172.16.0.199.1123695310.squirrel@172.16.0.1> In-Reply-To: References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> Date: Wed, 10 Aug 2005 13:35:10 -0400 (EDT) From: "Mike Jakubik" To: "Dmitry Mityugov" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, Unix , freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 17:35:22 -0000 On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: > There are Maxtor MaXLine II and III, and perhaps several other models, > that are supposed to work 24/7. Right, i have a dead 250GB Maxline Plus II drive on my desk, only after about 1.5 years. At least its still on warranty. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 17:42:55 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D8E416A420 for ; Wed, 10 Aug 2005 17:42:55 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 7017743D53 for ; Wed, 10 Aug 2005 17:42:54 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 72415 invoked from network); 10 Aug 2005 17:42:53 -0000 Received: from unknown (HELO ?192.168.1.10?) (unknown) by unknown with SMTP; 10 Aug 2005 17:42:53 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42FA3C8B.5030001@dominique-werner.com> Date: Wed, 10 Aug 2005 19:42:35 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> <2420.172.16.0.199.1123695310.squirrel@172.16.0.1> In-Reply-To: <2420.172.16.0.199.1123695310.squirrel@172.16.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, Dmitry Mityugov Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 17:42:55 -0000 It's sad isn't it, Mike..I don't know what the hd manufacturers are doing to the HD drives..ok, the systems get faster, there's usually bad cooling unless you build your own system...but even if you get enough cooling that won't change a thing some hds are prone to die an early death such as the Maxtors..I used to love Maxtor and hated Seagate now it's the other way around but my #1 HD still is Western Digital...I have an old Maxtor drive here 6 gb that's still running perfectly, just like 3 40gb Seagate Barracuda and Western Digital Caviar...I had a 120gb Hitachi that died after 1 yr of use... Mike Jakubik wrote: >On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: > > > >>There are Maxtor MaXLine II and III, and perhaps several other models, >>that are supposed to work 24/7. >> >> > >Right, i have a dead 250GB Maxline Plus II drive on my desk, only after >about 1.5 years. At least its still on warranty. > > > > > From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 17:45:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C7616A41F; Wed, 10 Aug 2005 17:45:15 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84E7243D55; Wed, 10 Aug 2005 17:45:14 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 24B6C300029F; Wed, 10 Aug 2005 19:45:13 +0200 (CEST) Message-ID: <42FA3D44.2020502@mail.uni-mainz.de> Date: Wed, 10 Aug 2005 19:45:40 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050722) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> <2420.172.16.0.199.1123695310.squirrel@172.16.0.1> In-Reply-To: <2420.172.16.0.199.1123695310.squirrel@172.16.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org, Unix , Dmitry Mityugov Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 17:45:15 -0000 Mike Jakubik wrote: > On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: > > >>There are Maxtor MaXLine II and III, and perhaps several other models, >>that are supposed to work 24/7. > > > Right, i have a dead 250GB Maxline Plus II drive on my desk, only after > about 1.5 years. At least its still on warranty. On the other hand: In the department for physics of the athmosphere, where I built six years ago a server for meteorological data, a RAID-5 with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem! From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 17:48:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34BC016A420 for ; Wed, 10 Aug 2005 17:48:59 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 57FD143D5C for ; Wed, 10 Aug 2005 17:48:58 +0000 (GMT) (envelope-from unix@dominique-werner.com) Received: (qmail 74071 invoked from network); 10 Aug 2005 17:48:57 -0000 Received: from unknown (HELO ?192.168.1.10?) (unknown) by unknown with SMTP; 10 Aug 2005 17:48:57 -0000 X-pair-Authenticated: 82.141.44.113 Message-ID: <42FA3DF7.2040800@dominique-werner.com> Date: Wed, 10 Aug 2005 19:48:39 +0200 From: Unix User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "O. Hartmann" References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9009E.3030601@mac.com> <42F92FEE.8060305@mail.uni-mainz.de> <90CD1F31-6893-4367-A21C-05866DEA5855@ddcom.co.jp> <42F9C971.9070206@dominique-werner.com> <2420.172.16.0.199.1123695310.squirrel@172.16.0.1> <42FA3D44.2020502@mail.uni-mainz.de> In-Reply-To: <42FA3D44.2020502@mail.uni-mainz.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Jakubik , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org, Dmitry Mityugov Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 17:48:59 -0000 O. Hartmann wrote: > Mike Jakubik wrote: > >> On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: >> >> >>> There are Maxtor MaXLine II and III, and perhaps several other models, >>> that are supposed to work 24/7. >> >> >> >> Right, i have a dead 250GB Maxline Plus II drive on my desk, only after >> about 1.5 years. At least its still on warranty. > > > On the other hand: In the department for physics of the athmosphere, > where I built six years ago a server for meteorological data, a RAID-5 > with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem! > I still own old 1-2 GB old SCSI disks and these are still working, I also had an old 500mb SCSI disk that was in an old Mac that also worked but I trashed it since it was that old and no longer of use... From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 18:05:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2888516A41F for ; Wed, 10 Aug 2005 18:05:51 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45EB243D46 for ; Wed, 10 Aug 2005 18:05:50 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id i5so189875wra for ; Wed, 10 Aug 2005 11:05:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UwsUY8/Nk1kq525u0mpy2xKrq5t8sHSVeOjvrtGfGApoKc/XZYeMwGWgo0WZaFX5vQzJ316YSTaqyj9TzeRw0BbSLZZk7FT7SvrqP2SmlYKpabEnbUlejl+5ljJFKGif+3sXlt1zSIxi2U4kLZpQuRho4DssjF+lI9v4UpDlwLg= Received: by 10.54.34.33 with SMTP id h33mr632193wrh; Wed, 10 Aug 2005 11:05:49 -0700 (PDT) Received: by 10.54.29.26 with HTTP; Wed, 10 Aug 2005 11:05:49 -0700 (PDT) Message-ID: <790a9fff05081011053b4b91a0@mail.gmail.com> Date: Wed, 10 Aug 2005 13:05:49 -0500 From: Scot Hetzel To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= In-Reply-To: <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> Cc: freebsd-stable@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 18:05:51 -0000 On 8/10/05, S=F8ren Schmidt wrote: >=20 > On 10/08/2005, at 17:44, Scot Hetzel wrote: >=20 > > On 8/10/05, Karl Denninger wrote: > > > >> On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote: > >> > >>> At 09:31 AM 10/08/2005, Karl Denninger wrote: > >>> > >>> > >>>> Also, I've yet to see a developer commit on the list that they > >>>> WILL fix it > >>>> if > >>>> such a controller board is forthcoming (and will return the > >>>> board when > >>>> they're > >>>> done) - I've got two of these cards here (choose between Adaptec > >>>> and > >>>> Bustek) > >>>> and would be happy to UPS one to someone IF I had a firm > >>>> commitment that > >>>> 6.x > >>>> would NOT go out without this being addressed and that the board > >>>> would be > >>>> returned to me when work was complete. > >>>> > >>> > >>> You demand to see support for this chipset fixed, yet, you cant > >>> pony up a > >>> measly hundred bucks to donate the card to the developer who is > >>> not being > >>> paid to develop anything. > >>> > >>> ---Mike > >>> > >> > >> I have "demanded" nothing Mike. > >> > >> > > I agree Mike's wording was a little strong, but we have seen you > > request strongly that some one fix this problem. > > > > Have you contacted S=F8ren, to see if he has the troublesome hardware? > > > > Also contact S=F8ren directly with your offer to supply a troublesome > > board, and/or access to a system that displays the problem. More than > > likely he would agree to return the board once he has a proper fix for > > the problem. >=20 > Since I came in late in this, I need to know what kind of controller > we are talking about, and if the problem is still present in 6.0. > I plan to backport ATA from 6.0 to 5-stable when it has settled, so > 6.0 is the one and only (pre)release to test with and get back to me > with the result. >=20 They have been talking about SII and Intel ICH6 chips. And a few have stated that they are having problems with the 6.0-Beta releases with these chips. --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 18:29:07 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF68716A41F; Wed, 10 Aug 2005 18:29:07 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from audi.websitewelcome.com (audi.websitewelcome.com [67.19.210.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C1C643D75; Wed, 10 Aug 2005 18:28:58 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from adsl-065-013-105-239.sip.tys.bellsouth.net ([65.13.105.239]:4419 helo=[192.168.1.33]) by audi.websitewelcome.com with esmtpa (Exim 4.50) id 1E2vJs-0000zd-6S; Wed, 10 Aug 2005 13:28:52 -0500 Message-ID: <42FA4778.3010303@goldsword.com> Date: Wed, 10 Aug 2005 14:29:12 -0400 From: "J. T. Farmer" Organization: GoldSword Systems User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.7) Gecko/20050414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scot Hetzel References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <790a9fff05081011053b4b91a0@mail.gmail.com> In-Reply-To: <790a9fff05081011053b4b91a0@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - audi.websitewelcome.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - goldsword.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-stable@freebsd.org, =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 18:29:07 -0000 Scot Hetzel wrote: >On 8/10/05, Søren Schmidt wrote: > > >> Since I came in late in this, I need to know what kind of controller >> >>we are talking about, and if the problem is still present in 6.0. >>I plan to backport ATA from 6.0 to 5-stable when it has settled, so >>6.0 is the one and only (pre)release to test with and get back to me >>with the result. >> >They have been talking about SII and Intel ICH6 chips. And a few have >stated that they are having problems with the 6.0-Beta releases with >these chips. > What, I'm chopped liver? :^> I'm getting these errors with a standard, _very_ not "state of the art", Via KT266A/8235 chipset. PATA WDC 800 drive. All very standard stuff for a desktop. Was running WinXP without a problem for quite some time. Generic kernel. In fact when I tried to install 5.4 (and 5.4-SNAP from 5 July & 9 July), it errored out as soon as the install kernel tried to write to the disk. FS's do not work when you can't write the superblocks out... Oh yeah, writing the disklabel also generated the same error. So it's not just the SATA raid type chipsets. It's plain vanilla ATA controllers, also. John ---------------------------------------------------------------------- John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 18:36:45 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04C5916A41F for ; Wed, 10 Aug 2005 18:36:45 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 561DA43D46 for ; Wed, 10 Aug 2005 18:36:44 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from [194.192.25.136] (mac.deepcore.dk [194.192.25.136]) by spider.deepcore.dk (8.13.3/8.13.3) with ESMTP id j7AIMMB2072287; Wed, 10 Aug 2005 20:22:23 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) In-Reply-To: <790a9fff05081011053b4b91a0@mail.gmail.com> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <790a9fff05081011053b4b91a0@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <22762A08-E466-4C29-85A8-9DA50F2852D8@FreeBSD.ORG> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Date: Wed, 10 Aug 2005 20:36:39 +0200 To: Scot Hetzel X-Mailer: Apple Mail (2.733) X-mail-scanned: by DeepCore Virus & Spam killer v1.12 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 18:36:45 -0000 On 10/08/2005, at 20:05, Scot Hetzel wrote: >> >> Since I came in late in this, I need to know what kind of controller >> we are talking about, and if the problem is still present in 6.0. >> I plan to backport ATA from 6.0 to 5-stable when it has settled, so >> 6.0 is the one and only (pre)release to test with and get back to me >> with the result. >> >> > > They have been talking about SII and Intel ICH6 chips. And a few have > stated that they are having problems with the 6.0-Beta releases with > these chips. Well, both work wonderfully here YMMV of course.. No, seriously I need *much* more accurate info than that, I need the =20 dmesg from the failing system, and I need an exact description of the =20= problem, preferably with logs, dumbs etc etc. - S=F8ren From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 18:38:46 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06CC616A41F for ; Wed, 10 Aug 2005 18:38:46 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3094043D49 for ; Wed, 10 Aug 2005 18:38:45 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from [194.192.25.136] (mac.deepcore.dk [194.192.25.136]) by spider.deepcore.dk (8.13.3/8.13.3) with ESMTP id j7AIONjt072294; Wed, 10 Aug 2005 20:24:23 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) In-Reply-To: <42FA4778.3010303@goldsword.com> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <790a9fff05081011053b4b91a0@mail.gmail.com> <42FA4778.3010303@goldsword.com> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <7379C950-62D7-42F4-BD6A-D7DABA0AA667@FreeBSD.ORG> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Date: Wed, 10 Aug 2005 20:38:40 +0200 To: "J. T. Farmer" X-Mailer: Apple Mail (2.733) X-mail-scanned: by DeepCore Virus & Spam killer v1.12 Cc: Scot Hetzel , freebsd-stable@FreeBSD.ORG Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 18:38:46 -0000 On 10/08/2005, at 20:29, J. T. Farmer wrote: > Scot Hetzel wrote: > > >> On 8/10/05, S=F8ren Schmidt wrote: >> >> >>> Since I came in late in this, I need to know what kind of controller >>> >>> we are talking about, and if the problem is still present in 6.0. >>> I plan to backport ATA from 6.0 to 5-stable when it has settled, so >>> 6.0 is the one and only (pre)release to test with and get back to me >>> with the result. >>> >>> >> They have been talking about SII and Intel ICH6 chips. And a few =20 >> have >> stated that they are having problems with the 6.0-Beta releases with >> these chips. >> >> > > What, I'm chopped liver? :^> I'm getting these errors with a =20 > standard, _very_ > not "state of the art", Via KT266A/8235 chipset. PATA WDC 800 =20 > drive. All very standard stuff for a desktop. Was running WinXP =20 > without a > problem for quite some time. Generic kernel. In fact when I tried =20= > to install 5.4 > (and 5.4-SNAP from 5 July & 9 July), it errored out as soon as the =20 > install kernel > tried to write to the disk. FS's do not work when you can't write =20= > the superblocks > out... Oh yeah, writing the disklabel also generated the same error. > > So it's not just the SATA raid type chipsets. It's plain vanilla ATA > controllers, also. As I said I need reports on 6.0, the ATA driver as is in 5.4 is not =20 supported by me unless you use the ATA mkIII patches.. - S=F8ren From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 20:13:31 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A89716A41F; Wed, 10 Aug 2005 20:13:31 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1502243D48; Wed, 10 Aug 2005 20:13:30 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Wed, 10 Aug 2005 13:13:29 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id C6B6D5D07; Wed, 10 Aug 2005 13:13:29 -0700 (PDT) To: Bruno Ducrot In-reply-to: Your message of "Tue, 09 Aug 2005 11:35:29 +0200." <20050809093529.GG852@poupinou.org> Date: Wed, 10 Aug 2005 13:13:29 -0700 From: "Kevin Oberman" Message-Id: <20050810201329.C6B6D5D07@ptavv.es.net> Cc: acpi@FreeBSD.org, freebsd-stable@freebsd.org Subject: Re: 5-STABLE cpufreq hotter than est from ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 20:13:31 -0000 > Date: Tue, 9 Aug 2005 11:35:29 +0200 > From: Bruno Ducrot > Sender: owner-freebsd-stable@freebsd.org > > On Tue, Aug 02, 2005 at 12:22:02AM +0200, Tijl Coosemans wrote: > > A couple days ago I updated my system and was excited to see cpufreq > > and powerd in 5-stable. Since then however I noticed that my laptop > > temperature is about 5°C higher than with est and estctrl. I found that > > cpufreq when setting 200MHz for example set the absolute frequency to > > 1600MHz (max for this laptop) and the relative frequency (p4tcc) to > > 12.5% instead of using a more power conserving setting like 800MHz/25%. > > > > The problem is that cpufreq_expand_set() (sys/kern/kern_cpu.c) > > traverses freq levels from high to low when adding relative levels and > > skips duplicates. When it wants to add 800MHz/25% it sees this setting > > as a duplicate of 1600MHz/12.5% it has found before. This can be fixed > > by letting cpufreq_expand_set() traverse freq levels in reverse order > > (and still skipping duplicates). Then each frequency level has the > > lowest possible absolute setting. This is a one line change in > > sys/kern/kern_cpu.c (line 653). > > It's a well known bug. Someday I think I will have enough time to fix > that one if Nate don't bite me. I have been running with Tijl's patch set for several days with great results. Testing has shown that the patches resolve both issues and I now see only 11 CPU speeds, all of those below the lower CPU clock speed are at that lower speed. Thus far I have seen no negative issues. The temperature of my system is noticeably cooler when not running something that is compute intensive. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 20:51:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DA2816A41F for ; Wed, 10 Aug 2005 20:51:03 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B1BD43D53 for ; Wed, 10 Aug 2005 20:51:02 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j7AKp1qP017638 for ; Wed, 10 Aug 2005 15:51:01 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Wed Aug 10 15:51:01 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j7AKp1FQ017636; Wed, 10 Aug 2005 15:51:01 -0500 (CDT) (envelope-from karl) Date: Wed, 10 Aug 2005 15:51:01 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050810205101.GA17483@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org, sos@freebsd.org References: <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Cc: sos@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 20:51:03 -0000 On Wed, Aug 10, 2005 at 07:24:01PM +0200, S?ren Schmidt wrote: > > On 10/08/2005, at 17:44, Scot Hetzel wrote: > > >On 8/10/05, Karl Denninger wrote: > > > >>On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote: > >> > >>>At 09:31 AM 10/08/2005, Karl Denninger wrote: > >>> > >>> > >>>>Also, I've yet to see a developer commit on the list that they > >>>>WILL fix it > >>>>if > >>>>such a controller board is forthcoming (and will return the > >>>>board when > >>>>they're > >>>>done) - I've got two of these cards here (choose between Adaptec > >>>>and > >>>>Bustek) > >>>>and would be happy to UPS one to someone IF I had a firm > >>>>commitment that > >>>>6.x > >>>>would NOT go out without this being addressed and that the board > >>>>would be > >>>>returned to me when work was complete. > >>>> > >>> > >>>You demand to see support for this chipset fixed, yet, you cant > >>>pony up a > >>>measly hundred bucks to donate the card to the developer who is > >>>not being > >>>paid to develop anything. > >>> > >>> ---Mike > >>> > >> > >>I have "demanded" nothing Mike. > >> > >> > >I agree Mike's wording was a little strong, but we have seen you > >request strongly that some one fix this problem. > > > >Have you contacted S?ren, to see if he has the troublesome hardware? > > > >Also contact S?ren directly with your offer to supply a troublesome > >board, and/or access to a system that displays the problem. More than > >likely he would agree to return the board once he has a proper fix for > >the problem. > > Since I came in late in this, I need to know what kind of controller > we are talking about, and if the problem is still present in 6.0. > I plan to backport ATA from 6.0 to 5-stable when it has settled, so > 6.0 is the one and only (pre)release to test with and get back to me > with the result. > > - S?ren 6.0 BETA1 AND 5.4 BOTH fail with the SiI 3112 chipsets. Reliably. I have two controllers here that are from different manufacturers and both exhibit the same problem. The SAME disks (two different manufacturers - hitachi and maxtor) on a motherboard ICH5 adapter work perfectly, smartmontools says all 4 (I have two examples of each) are healthy, and both ALSO work perfectly on and are declared healthy by a 3ware 8502's internal diags and operating kernel (smartmontools won't talk to them on the 8502.) This is the subject of the PR I filed back in February. Again, if you want either a controller shipped to you OR access to a development machine (e.g. ssh in and play) which has the suspect configuration on it, the latter of which is probably the best option (since making it fail is simple) I'm willing to provide either - my only caveat is that if I send hardware I want it back when you're done, and I believe its reasonable to expect that 6.0 will get HELD in its release cycle until this is resolved. The latter offer (ssh access) has been on the table for several months. The former I just put on the table as I threw up my hands and bought a 3ware card - which means I now have TWO of the suspect cards and need only one for my own testing (in the sandbox) I'm willing to go WELL out of my way to make it possible for this to get fixed, since there appears to be an issue with access to hardware that breaks reliably. However, I, and others, would like to know that we're going to see the problem get resolved. Again - this is hardware that is STABLE and works under 4.x - in the case of my specific configuration I ran under 4.x for over a year without a single incident. With 5.4 and 6.0-BETA I can kill it inside of 2 minutes with nothing more complicated than a "make -j4 buildworld". Let me know if you'd like to take me up on either of my offers. Note that with 6.0-BETA (what's currently on the sandbox machine) when it blows up it does so in such a way that a reboot FAILS (it hangs during the shutdown sequence!) so you need to hit the red button to get a clean restart (and wait for the FSCK) I have a PATA drive in the sandbox machine on the motherboard adapter that is part of a mirror with the "bad" controller, so there is no risk of data corruption - when it fails the "bad" disk disconnects from the array but the boot drive remains "safe". -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 20:54:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD1D216A41F for ; Wed, 10 Aug 2005 20:54:38 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FCE443D7E for ; Wed, 10 Aug 2005 20:54:23 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j7AKsN7L017765 for ; Wed, 10 Aug 2005 15:54:23 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Wed Aug 10 15:54:23 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j7AKsNlF017763; Wed, 10 Aug 2005 15:54:23 -0500 (CDT) (envelope-from karl) Date: Wed, 10 Aug 2005 15:54:23 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050810205423.GB17483@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org, sos@freebsd.org References: <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <790a9fff05081011053b4b91a0@mail.gmail.com> <22762A08-E466-4C29-85A8-9DA50F2852D8@FreeBSD.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <22762A08-E466-4C29-85A8-9DA50F2852D8@FreeBSD.ORG> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Cc: sos@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 20:54:38 -0000 On Wed, Aug 10, 2005 at 08:36:39PM +0200, S?ren Schmidt wrote: > > On 10/08/2005, at 20:05, Scot Hetzel wrote: > >> > >>Since I came in late in this, I need to know what kind of controller > >>we are talking about, and if the problem is still present in 6.0. > >>I plan to backport ATA from 6.0 to 5-stable when it has settled, so > >>6.0 is the one and only (pre)release to test with and get back to me > >>with the result. > >> > >> > > > >They have been talking about SII and Intel ICH6 chips. And a few have > >stated that they are having problems with the 6.0-Beta releases with > >these chips. > > Well, both work wonderfully here YMMV of course.. > > No, seriously I need *much* more accurate info than that, I need the > dmesg from the failing system, and I need an exact description of the > problem, preferably with logs, dumbs etc etc. > > - S?ren http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/83974 Filed on July 24th. Again, happy to give you SSH access to if it will work towards getting this resolved. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 21:13:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44CDF16A41F; Wed, 10 Aug 2005 21:13:22 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id D270843D58; Wed, 10 Aug 2005 21:13:16 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn [127.0.0.1]) by gwyn.kn-bremen.de (8.13.4/8.13.4/Debian-3) with ESMTP id j7ALDEsb023669; Wed, 10 Aug 2005 23:13:14 +0200 Received: from saturn.kn-bremen.de (uucp@localhost) by gwyn.kn-bremen.de (8.13.4/8.13.4/Submit) with UUCP id j7ALDE5j023667; Wed, 10 Aug 2005 23:13:14 +0200 Received: from saturn.kn-bremen.de (localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.1/8.13.1) with ESMTP id j7AL8Xhm009539; Wed, 10 Aug 2005 23:08:33 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.1/8.13.1/Submit) id j7AL8UPM009538; Wed, 10 Aug 2005 23:08:30 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Wed, 10 Aug 2005 23:08:30 +0200 To: bzeeb+freebsd+sk4@zabbadoz.net Message-ID: <20050810210830.GA9197@saturn.kn-bremen.de> Mail-Followup-To: bzeeb+freebsd+sk4@zabbadoz.net, freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: if_sk no PHY found, next iteration X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 21:13:22 -0000 Thanks for the info on your http://sources.zabbadoz.net/freebsd/if_sk.html page. Here is a dmesg snippet of another sk problem (Asus A8V deluxe, 5.4-R amd64): skc0: port 0xa000-0xa0ff mem 0xfba00000-0xfba03fff irq 17 at device 10.0 on pci0 skc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfba00000 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: on skc0 sk0: bpf attached sk0: Ethernet address: 00:11:d8:a9:d5:6d skc0: no PHY found! device_attach: sk0 attach returned 6 skc0: [MPSAFE] Under TODO you have `unkown rev. 0x9 for Yukon Lite', seems this is it? Btw i also installed xp on the box and for that i had to fetch the latest driver off the marvell.com site too (yk51x86.sys), the one distributed by Asus didnt work. (nice, eh?) Linux's sk98lin driver (2.6.11 kernel) seems to have no problems tho. Any patches/info welcome... Juergen From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 21:16:54 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B78DA16A421 for ; Wed, 10 Aug 2005 21:16:54 +0000 (GMT) (envelope-from cabal@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78AB343D46 for ; Wed, 10 Aug 2005 21:16:54 +0000 (GMT) (envelope-from cabal@u.washington.edu) Received: from aagaard01.u.washington.edu (aagaard01.u.washington.edu [140.142.13.113]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7ALGrpl020891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 10 Aug 2005 14:16:54 -0700 Received: from localhost (cabal@localhost) by aagaard01.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.07) with ESMTP id j7ALGrdg254290 for ; Wed, 10 Aug 2005 14:16:53 -0700 Date: Wed, 10 Aug 2005 14:16:53 -0700 (PDT) From: "J. Nyhuis" To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Q: How do I suggest a change to a FreeBSD Man page? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 21:16:54 -0000 Greetings, I would like to suggest a change to the FreeBSD man page for pf.conf. Since pf is now part of the FreeBSD source core, where do I go to make my suggestion? No contact info is listed in the man page, as there is for ports. I'm a little hesitant to just make a change and submit it via cvs; I'd prefer to just make my suggestion for a change and get the opinions of others far more experienced then I. Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 cabal@u.washington.edu From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 21:20:10 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A781B16A41F; Wed, 10 Aug 2005 21:20:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39BE743D45; Wed, 10 Aug 2005 21:20:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 066651FF91D; Wed, 10 Aug 2005 23:20:08 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 9764E1FF90C; Wed, 10 Aug 2005 23:20:05 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 3A132153C4; Wed, 10 Aug 2005 21:19:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2E4EB15329; Wed, 10 Aug 2005 21:19:41 +0000 (UTC) Date: Wed, 10 Aug 2005 21:19:41 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Juergen Lock In-Reply-To: <20050810210830.GA9197@saturn.kn-bremen.de> Message-ID: References: <20050810210830.GA9197@saturn.kn-bremen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: if_sk no PHY found, next iteration X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 21:20:10 -0000 On Wed, 10 Aug 2005, Juergen Lock wrote: Hi, > Thanks for the info on your http://sources.zabbadoz.net/freebsd/if_sk.html > page. Here is a dmesg snippet of another sk problem (Asus A8V deluxe, > 5.4-R amd64): > > skc0: port 0xa000-0xa0ff mem 0xfba00000-0xfba03fff irq 17 at device 10.0 on pci0 > skc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfba00000 > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > sk0: on skc0 > sk0: bpf attached > sk0: Ethernet address: 00:11:d8:a9:d5:6d > skc0: no PHY found! > device_attach: sk0 attach returned 6 > skc0: [MPSAFE] > > Under TODO you have `unkown rev. 0x9 for Yukon Lite', seems this is it? > Btw i also installed xp on the box and for that i had to fetch the > latest driver off the marvell.com site too (yk51x86.sys), the one > distributed by Asus didnt work. (nice, eh?) Linux's sk98lin driver > (2.6.11 kernel) seems to have no problems tho. > > Any patches/info welcome... I am currently fixing another problem but in the meantime you can use this one which should: * fix your problem * catch a bus attach error * improve locking http://sources.zabbadoz.net/freebsd/patchset/EXPERIMENTAL/if_sk.c-rev1.108.diff -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 21:28:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DBC916A41F for ; Wed, 10 Aug 2005 21:28:01 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FE7243D45 for ; Wed, 10 Aug 2005 21:28:00 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr15.xs4all.nl (8.13.3/8.13.3) with ESMTP id j7ALRw6f067646; Wed, 10 Aug 2005 23:27:58 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.3/8.13.3) with ESMTP id j7ALRwqs016894; Wed, 10 Aug 2005 23:27:58 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.3/8.13.1/Submit) id j7ALRwq9016893; Wed, 10 Aug 2005 23:27:58 +0200 (CEST) (envelope-from wb) Date: Wed, 10 Aug 2005 23:27:57 +0200 From: Wilko Bulte To: "J. Nyhuis" Message-ID: <20050810212757.GA16867@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: Q: How do I suggest a change to a FreeBSD Man page? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 21:28:01 -0000 On Wed, Aug 10, 2005 at 02:16:53PM -0700, J. Nyhuis wrote.. > Greetings, > > I would like to suggest a change to the FreeBSD man page for > pf.conf. Since pf is now part of the FreeBSD source core, where do I go > to make my suggestion? No contact info is listed in the man page, as > there is for ports. I'm a little hesitant to just make a change and > submit it via cvs; I'd prefer to just make my suggestion for a change and > get the opinions of others far more experienced then I. If I am not mistaken Max Laier (mlaier@FreeBSD.org) takes care of pf -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 21:34:17 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B09A116A41F for ; Wed, 10 Aug 2005 21:34:17 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C51F43D48 for ; Wed, 10 Aug 2005 21:34:16 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3D832.dip.t-dialin.net [84.163.216.50] (helo=donor.laier.local) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0ML2Dk-1E2yDD0mbS-0001yR; Wed, 10 Aug 2005 23:34:11 +0200 From: Max Laier To: Ulf Lilleengen Date: Wed, 10 Aug 2005 23:33:29 +0200 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9095194.am68nxp1lp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200508102333.42540.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-stable@freebsd.org Subject: Re: Q: How do I suggest a change to a FreeBSD Man page? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 21:34:17 -0000 --nextPart9095194.am68nxp1lp Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 10 August 2005 23:16, J. Nyhuis wrote: > I would like to suggest a change to the FreeBSD man page for > pf.conf. Since pf is now part of the FreeBSD source core, where do I go > to make my suggestion? No contact info is listed in the man page, as > there is for ports. I'm a little hesitant to just make a change and > submit it via cvs; I'd prefer to just make my suggestion for a change and > get the opinions of others far more experienced then I. The place to discuss things like this is freebsd-doc@ As for contact=20 information you can always look at cvs log to get an idea who did commit to= =20 the file before (in this case it'd turn up my name). There is also=20 freebsd-pf@ to discuss pf related topics. As for the request itself. As f= or=20 the request itself, I am very reluctant to take manpages off the vendor=20 branch too much without very good reason. Everything you change you have t= o=20 catch up manually once we import new code ... so this is a long term=20 commitment. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart9095194.am68nxp1lp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBC+nK2XyyEoT62BG0RAqrrAJ0dzedpV65vfb2kEPM0wfjtpgqVUQCdEytd 08qcj0gAF/do1FUcsO9XiAU= =/put -----END PGP SIGNATURE----- --nextPart9095194.am68nxp1lp-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 22:13:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A595D16A41F for ; Wed, 10 Aug 2005 22:13:03 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4AD0343D46 for ; Wed, 10 Aug 2005 22:13:01 +0000 (GMT) (envelope-from Emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 10 Aug 2005 22:13:01 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) [62.245.232.135] by mail.gmx.net (mp023) with SMTP; 11 Aug 2005 00:13:01 +0200 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Thu, 11 Aug 2005 00:12:44 +0200 User-Agent: KMail/1.8.1 References: <42F7F7E8.1020507@mail.uni-mainz.de> <42FA3D44.2020502@mail.uni-mainz.de> <42FA3DF7.2040800@dominique-werner.com> In-Reply-To: <42FA3DF7.2040800@dominique-werner.com> X-Birthday: Oct. 6th 1972 X-CelPhone: +49 (0) 173 9967781 X-Tel: +49 (0) 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4198030.vcGQEuDQAQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200508110012.55575@harrymail> X-Y-GMX-Trusted: 0 Cc: Mike Jakubik , "O. Hartmann" , Dmitry Mityugov , Unix , freebsd-questions@freebsd.org Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 22:13:03 -0000 --nextPart4198030.vcGQEuDQAQ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Mittwoch, 10. August 2005 19:48 CEST schrieb Unix: > O. Hartmann wrote: > > Mike Jakubik wrote: > >> On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said: > >>> There are Maxtor MaXLine II and III, and perhaps several other > >>> models, that are supposed to work 24/7. > >> > >> Right, i have a dead 250GB Maxline Plus II drive on my desk, only > >> after about 1.5 years. At least its still on warranty. > > > > On the other hand: In the department for physics of the athmosphere, > > where I built six years ago a server for meteorological data, a RAID-5 > > with 4 older IBM U160 SCSI discs still works - 24/7. Never had a > > problem! > > I still own old 1-2 GB old SCSI disks and these are still working, I > also had an old 500mb SCSI disk that was in an old Mac that also worked > but I trashed it since it was that old and no longer of use... I have an old 700 MB WD IDE drive that still works fine and has about 6=20 years 24/7 survived. And I also had a 2000$ 73G SCSI IBM drive that lasted= =20 for about 5 monthas and was that damadged that Convar sent it back without= =20 one byte recovered! And I don't want to remember the 80GB WD drive that=20 lasted for 2 months...... Please, don't discuss about SCSI/ATA reliability, there are bad=20 designed/produced drives and there are good ones. You can't tell before,=20 only experience counts. I can say only good things about Seagates Barracuda 7200.8 drives for=20 example. Some dozends are running for two years without _any_ single drive= =20 failed. Also the Samsung (p)ATA drives are still running without any=20 single failure. And WDs once were perfect drices, but they also produced=20 crap. So you can't even be sure by vendor! =2DHarry P.S.: I'm planning to bring up a FreeBSD site which reflects hardware=20 compatibility experiences as well as long term experiences. I'll be back=20 if I have more... --nextPart4198030.vcGQEuDQAQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC+nvnBylq0S4AzzwRApQzAJsEw4AJBkTHgPbTdlaTGEEfwKNRMwCeLl/5 RrbKp35UoGr65kMdGXJFg84= =fy0W -----END PGP SIGNATURE----- --nextPart4198030.vcGQEuDQAQ-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 22:26:15 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6880516A41F for ; Wed, 10 Aug 2005 22:26:15 +0000 (GMT) (envelope-from msergeant@snsonline.net) Received: from xyzzy.snsonline.net (office-fw.iexec.net.au [210.18.210.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11C4E43D48 for ; Wed, 10 Aug 2005 22:26:14 +0000 (GMT) (envelope-from msergeant@snsonline.net) Received: from [127.0.0.1] (localhost [127.0.0.1]) by xyzzy.snsonline.net (Postfix) with ESMTP id 8EA32448717 for ; Thu, 11 Aug 2005 08:26:00 +1000 (EST) Mime-Version: 1.0 (Apple Message framework v733) Content-Transfer-Encoding: 7bit Message-Id: <15A7EAD2-5BA9-47A5-B181-1AC221ED88BA@snsonline.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@FreeBSD.ORG From: Mark Sergeant Date: Thu, 11 Aug 2005 08:25:58 +1000 X-Mailer: Apple Mail (2.733) Cc: Subject: VIA vt6202 controller not recognised by FreeBSD 5.4-Release (ehci) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 22:26:15 -0000 Output from pciconf -lv none@pci2:7:2 class=0x0c0320 card=0x12340925 chip=0x31041106 rev=0x51 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6202 USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB The same card has it's usb 1.0 component recognised as a VIA VT82xxxxxx UHCI USB 1.1 Controller, it also has the ehci part recognised by ubuntu. Any ideas ? Cheers, Mark From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 22:28:33 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EEDC16A421; Wed, 10 Aug 2005 22:28:33 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEDE843D48; Wed, 10 Aug 2005 22:28:32 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtp (Exim 4.51 (FreeBSD)) id 1E2z3o-000Lh1-C5; Wed, 10 Aug 2005 22:28:32 +0000 Received: from [127.0.0.1] (helo=roam.psg.com.psg.com) by roam.psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1E2z3n-0004dX-Pw; Wed, 10 Aug 2005 12:28:31 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17146.32654.940230.202238@roam.psg.com> Date: Wed, 10 Aug 2005 12:28:30 -1000 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <790a9fff05081011053b4b91a0@mail.gmail.com> <42FA4778.3010303@goldsword.com> <7379C950-62D7-42F4-BD6A-D7DABA0AA667@FreeBSD.ORG> Cc: Scot Hetzel , freebsd-stable@FreeBSD.ORG Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 22:28:33 -0000 > As I said I need reports on 6.0, the ATA driver as is in 5.4 is not > supported by me unless you use the ATA mkIII patches.. you know, we just upgraded a system from 4.11 to 7.0 and see problems. we have been chasing cables, and never considered that we could blame all our problems on you and demand service! :-) ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=729217 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=729217 ad2: FAILURE - WRITE_DMA status=51 error=84 LBA=7 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=729222 ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=729222 ad2: FAILURE - WRITE_DMA status=51 error=84 LBA=2 atapci0: port 0x5020-0x5027,0x5014-0x50175 ata2: on atapci0 ata3: on atapci0 pci4: at device 30.0 (no driver attache) pcib6: at device 31.0 on pci4 pci6: on pcib6 atapci1: port 0x6020-0x6027,0x6014-0x60176 ata4: on atapci1 ata5: on atapci1 pci0: at device 29.0 (no driver attached) pci0: at device 29.1 (no driver attached) pci0: at device 29.2 (no driver attached) pcib7: at device 30.0 on pci0 pci7: on pcib7 pci7: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x30 ata0: on atapci2 ata1: on atapci2 hmmmm i demand a full refund!!!! randy, still chasing cables From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 22:46:47 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B2BE16A431 for ; Wed, 10 Aug 2005 22:46:45 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98E4F43D62 for ; Wed, 10 Aug 2005 22:46:25 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from [194.192.25.136] (mac.deepcore.dk [194.192.25.136]) by spider.deepcore.dk (8.13.3/8.13.3) with ESMTP id j7AMViHa074917; Thu, 11 Aug 2005 00:31:44 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) In-Reply-To: <20050810205101.GA17483@FS.denninger.net> References: <42F9009E.3030601@mac.com> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <20050810205101.GA17483@FS.denninger.net> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Date: Thu, 11 Aug 2005 00:46:04 +0200 To: Karl Denninger X-Mailer: Apple Mail (2.733) X-mail-scanned: by DeepCore Virus & Spam killer v1.12 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 22:46:49 -0000 On 10/08/2005, at 22:51, Karl Denninger wrote: >> >> Since I came in late in this, I need to know what kind of controller >> we are talking about, and if the problem is still present in 6.0. >> I plan to backport ATA from 6.0 to 5-stable when it has settled, so >> 6.0 is the one and only (pre)release to test with and get back to me >> with the result. >> >> - S?ren >> > > 6.0 BETA1 AND 5.4 BOTH fail with the SiI 3112 chipsets. Reliably. > I have two controllers here that are from different manufacturers =20 > and both > exhibit the same problem. The SAME disks (two different =20 > manufacturers - > hitachi and maxtor) on a motherboard ICH5 adapter work perfectly, > smartmontools says all 4 (I have two examples of each) are healthy, =20= > and > both ALSO work perfectly on and are declared healthy by a 3ware 8502's > internal diags and operating kernel (smartmontools won't talk to =20 > them on > the 8502.) > > This is the subject of the PR I filed back in February. > > Again, if you want either a controller shipped to you OR access to a > development machine (e.g. ssh in and play) which has the suspect > configuration on it, the latter of which is probably the best =20 > option (since > making it fail is simple) I'm willing to provide either - my only =20 > caveat is > that if I send hardware I want it back when you're done, and I =20 > believe its > reasonable to expect that 6.0 will get HELD in its release cycle =20 > until this > is resolved. I have plenty of the sii3112's around, so thats not needed, however =20 I've not managed to get ahold of a machine in which it fails reliably =20= with ATA as is in 6.0. > The latter offer (ssh access) has been on the table for several =20 > months. The > former I just put on the table as I threw up my hands and bought a =20 > 3ware > card - which means I now have TWO of the suspect cards and need =20 > only one > for my own testing (in the sandbox) > > I'm willing to go WELL out of my way to make it possible for this =20 > to get > fixed, since there appears to be an issue with access to hardware that > breaks reliably. However, I, and others, would like to know that =20 > we're > going to see the problem get resolved. I've already gone WAY out of my way to try to support the sii3112, =20 and I'm not inclined to waste more of my precious spare time on it. =20 However, if it really is that important to enough people to try to =20 workaround the silicon bugs (which very likely isn't possible), get =20 together and get me failing HW on my desk and time to work on it. > Again - this is hardware that is STABLE and works under 4.x - in =20 > the case of > my specific configuration I ran under 4.x for over a year without a =20= > single > incident. With 5.4 and 6.0-BETA I can kill it inside of 2 minutes =20 > with > nothing more complicated than a "make -j4 buildworld". First. you cannot by any degree of the word call the sii3112 for =20 STABLE hardware, its broken beyond repair or workarounds, and even =20 the supplier acknowledges that fact. Second, you cannot possibly have used gmirror (as in the PR) on 4.x =20 so what was the config back then ? Third, please get gmirror out of the loop (use atacontrol to create a =20= mirror if need be) and let me know if that changes anything. Forth, another thing to try is fumbling with BIOS settings, some =20 setups has been reported to start working when PCI timings is changed =20= YMMV.. - S=F8ren From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 22:47:14 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F6C316A51A for ; Wed, 10 Aug 2005 22:46:54 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 652FA43F6B for ; Wed, 10 Aug 2005 22:40:27 +0000 (GMT) (envelope-from sos@FreeBSD.ORG) Received: from [194.192.25.136] (mac.deepcore.dk [194.192.25.136]) by spider.deepcore.dk (8.13.3/8.13.3) with ESMTP id j7AMPx08074858; Thu, 11 Aug 2005 00:25:59 +0200 (CEST) (envelope-from sos@FreeBSD.ORG) In-Reply-To: <17146.32654.940230.202238@roam.psg.com> References: <42F7F7E8.1020507@mail.uni-mainz.de> <42F9609E.1010207@goldsword.com> <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <790a9fff05081011053b4b91a0@mail.gmail.com> <42FA4778.3010303@goldsword.com> <7379C950-62D7-42F4-BD6A-D7DABA0AA667@FreeBSD.ORG> <17146.32654.940230.202238@roam.psg.com> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <33EA562F-4921-4DA1-82E1-C426BD8C0233@FreeBSD.ORG> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Date: Thu, 11 Aug 2005 00:40:18 +0200 To: Randy Bush X-Mailer: Apple Mail (2.733) X-mail-scanned: by DeepCore Virus & Spam killer v1.12 Cc: Scot Hetzel , freebsd-stable@FreeBSD.ORG Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 22:47:14 -0000 On 11/08/2005, at 0:28, Randy Bush wrote: >> As I said I need reports on 6.0, the ATA driver as is in 5.4 is not >> supported by me unless you use the ATA mkIII patches.. >> > > you know, we just upgraded a system from 4.11 to 7.0 and see problems. > we have been chasing cables, and never considered that we could blame > all our problems on you and demand service! :-) > I'd rather put it like this: "you got what you payed for" ;) > ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3D729217= > ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3D729217= > ad2: FAILURE - WRITE_DMA status=3D51 =20 > error=3D84 LBA=3D7 > ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3D729222= > ad2: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=3D729222= > ad2: FAILURE - WRITE_DMA status=3D51 =20 > error=3D84 LBA=3D2 > > atapci0: port =20 > 0x5020-0x5027,0x5014-0x50175 > ata2: on atapci0 > ata3: on atapci0 > pci4: at device 30.0 (no =20 > driver attache) > pcib6: at device 31.0 on pci4 > pci6: on pcib6 > atapci1: port =20 > 0x6020-0x6027,0x6014-0x60176 > ata4: on atapci1 > ata5: on atapci1 > pci0: at device 29.0 (no driver attached) > pci0: at device 29.1 (no driver attached) > pci0: at device 29.2 (no driver attached) > pcib7: at device 30.0 on pci0 > pci7: on pcib7 > pci7: at device 1.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci2: port =20 > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x30 > ata0: on atapci2 > ata1: on atapci2 Could I have the *complete* dmesg please ? > > hmmmm > > i demand a full refund!!!! granted! just get it from where you bought it :) - S=F8ren From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 23:10:57 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCF6916A41F; Wed, 10 Aug 2005 23:10:57 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29CA743D49; Wed, 10 Aug 2005 23:10:50 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn [127.0.0.1]) by gwyn.kn-bremen.de (8.13.4/8.13.4/Debian-3) with ESMTP id j7ANAfvt001843; Thu, 11 Aug 2005 01:10:41 +0200 Received: from saturn.kn-bremen.de (uucp@localhost) by gwyn.kn-bremen.de (8.13.4/8.13.4/Submit) with UUCP id j7ANAfDo001841; Thu, 11 Aug 2005 01:10:41 +0200 Received: from saturn.kn-bremen.de (localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.1/8.13.1) with ESMTP id j7AN6kR9013343; Thu, 11 Aug 2005 01:06:46 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.1/8.13.1/Submit) id j7AN6gFN013342; Thu, 11 Aug 2005 01:06:42 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Thu, 11 Aug 2005 01:06:42 +0200 To: "Bjoern A. Zeeb" Message-ID: <20050810230642.GA11794@saturn.kn-bremen.de> Mail-Followup-To: "Bjoern A. Zeeb" , freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org References: <20050810210830.GA9197@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: if_sk no PHY found, next iteration X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 23:10:58 -0000 On Wed, Aug 10, 2005 at 09:19:41PM +0000, Bjoern A. Zeeb wrote: > On Wed, 10 Aug 2005, Juergen Lock wrote: > > Hi, > > > Thanks for the info on your http://sources.zabbadoz.net/freebsd/if_sk.html > > page. Here is a dmesg snippet of another sk problem (Asus A8V deluxe, > > 5.4-R amd64): > > > > skc0: port 0xa000-0xa0ff mem 0xfba00000-0xfba03fff irq 17 at device 10.0 on pci0 > > skc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfba00000 > > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > > sk0: on skc0 > > sk0: bpf attached > > sk0: Ethernet address: 00:11:d8:a9:d5:6d > > skc0: no PHY found! > > device_attach: sk0 attach returned 6 > > skc0: [MPSAFE] > > > > Under TODO you have `unkown rev. 0x9 for Yukon Lite', seems this is it? > > Btw i also installed xp on the box and for that i had to fetch the > > latest driver off the marvell.com site too (yk51x86.sys), the one > > distributed by Asus didnt work. (nice, eh?) Linux's sk98lin driver > > (2.6.11 kernel) seems to have no problems tho. > > > > Any patches/info welcome... > > I am currently fixing another problem but in the meantime you can use > this one which should: > > * fix your problem > * catch a bus attach error > * improve locking > > http://sources.zabbadoz.net/freebsd/patchset/EXPERIMENTAL/if_sk.c-rev1.108.diff Thanx. I had to MFC it, but it seems to get the nic working. I haven't tested networking extensively yet tho. (will do that later :) boot -v dmesg: skc0: port 0xa000-0xa0ff mem 0xfba00000-0xfba03fff irq 17 at device 10.0 on pci0 skc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfba00000 skc0: interrupt moderation is 100 us skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) skc0: PN: Yukon 88E8001 skc0: EC: Rev. 1.3 skc0: MN: Marvell skc0: SN: AbCdEfG334454 skc0: chip ver = 0xb1 skc0: chip rev = 0x09 skc0: SK_EPROM0 = 0x10 skc0: SRAM size = 0x010000 sk0: on skc0 sk0: bpf attached sk0: Ethernet address: 00:11:d8:a9:d5:6d miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto skc0: [MPSAFE] Diff against RELENG_5_4_0_RELEASE: Index: if_sk.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_sk.c,v retrieving revision 1.83.2.9 diff -u -r1.83.2.9 if_sk.c --- if_sk.c 28 Mar 2005 16:21:16 -0000 1.83.2.9 +++ if_sk.c 10 Aug 2005 22:54:19 -0000 @@ -94,12 +94,14 @@ #include #include #include +#include #include #include #include #include #include +#include #include @@ -195,8 +197,10 @@ static int sk_encap(struct sk_if_softc *, struct mbuf *, u_int32_t *); static void sk_start(struct ifnet *); +static void sk_start_locked(struct ifnet *); static int sk_ioctl(struct ifnet *, u_long, caddr_t); static void sk_init(void *); +static void sk_init_locked(struct sk_if_softc *); static void sk_init_xmac(struct sk_if_softc *); static void sk_init_yukon(struct sk_if_softc *); static void sk_stop(struct sk_if_softc *); @@ -242,6 +246,9 @@ static void sk_setmulti(struct sk_if_softc *); static void sk_setpromisc(struct sk_if_softc *); +static int sysctl_int_range(SYSCTL_HANDLER_ARGS, int low, int high); +static int sysctl_hw_sk_int_mod(SYSCTL_HANDLER_ARGS); + #ifdef SK_USEIOSPACE #define SK_RES SYS_RES_IOPORT #define SK_RID SK_PCI_LOIO @@ -474,6 +481,7 @@ free(sc->sk_vpd_readonly, M_DEVBUF); sc->sk_vpd_prodname = NULL; sc->sk_vpd_readonly = NULL; + sc->sk_vpd_readonly_len = 0; sk_vpd_read_res(sc, &res, pos); @@ -491,10 +499,12 @@ pos += sizeof(res); sc->sk_vpd_prodname = malloc(res.vr_len + 1, M_DEVBUF, M_NOWAIT); - for (i = 0; i < res.vr_len; i++) - sc->sk_vpd_prodname[i] = sk_vpd_readbyte(sc, i + pos); - sc->sk_vpd_prodname[i] = '\0'; - pos += i; + if (sc->sk_vpd_prodname != NULL) { + for (i = 0; i < res.vr_len; i++) + sc->sk_vpd_prodname[i] = sk_vpd_readbyte(sc, i + pos); + sc->sk_vpd_prodname[i] = '\0'; + } + pos += res.vr_len; sk_vpd_read_res(sc, &res, pos); @@ -508,6 +518,7 @@ sc->sk_vpd_readonly = malloc(res.vr_len, M_DEVBUF, M_NOWAIT); for (i = 0; i < res.vr_len; i++) sc->sk_vpd_readonly[i] = sk_vpd_readbyte(sc, i + pos); + sc->sk_vpd_readonly_len = res.vr_len; return; } @@ -790,6 +801,7 @@ struct ifmultiaddr *ifma; u_int8_t dummy[] = { 0, 0, 0, 0, 0 ,0 }; + SK_IF_LOCK_ASSERT(sc_if); /* First, zot all the existing filters. */ switch(sc->sk_type) { @@ -877,6 +889,8 @@ struct sk_softc *sc = sc_if->sk_softc; struct ifnet *ifp = &sc_if->arpcom.ac_if; + SK_IF_LOCK_ASSERT(sc_if); + switch(sc->sk_type) { case SK_GENESIS: if (ifp->if_flags & IFF_PROMISC) { @@ -1086,15 +1100,16 @@ sk_free_jumbo_mem(sc_if) struct sk_if_softc *sc_if; { - int retval = 0; struct sk_jpool_entry *entry; SK_JLIST_LOCK(sc_if); - /* Wait for the "inuse" list to drain. */ - if (!SLIST_EMPTY(&sc_if->sk_jinuse_listhead)) - retval = msleep(sc_if, &sc_if->sk_jlist_mtx, PZERO, - "skfjm", 5 * hz); + /* We cannot release external mbuf storage while in use. */ + if (!SLIST_EMPTY(&sc_if->sk_jinuse_listhead)) { + printf("sk%d: will leak jumbo buffer memory!\n", sc_if->sk_unit); + SK_JLIST_UNLOCK(sc_if); + return; + } while (!SLIST_EMPTY(&sc_if->sk_jfree_listhead)) { entry = SLIST_FIRST(&sc_if->sk_jfree_listhead); @@ -1230,13 +1245,15 @@ switch(command) { case SIOCSIFMTU: + SK_IF_LOCK(sc_if); if (ifr->ifr_mtu > SK_JUMBO_MTU) error = EINVAL; else { ifp->if_mtu = ifr->ifr_mtu; ifp->if_flags &= ~IFF_RUNNING; - sk_init(sc_if); + sk_init_locked(sc_if); } + SK_IF_UNLOCK(sc_if); break; case SIOCSIFFLAGS: SK_IF_LOCK(sc_if); @@ -1248,7 +1265,7 @@ sk_setmulti(sc_if); } } else - sk_init(sc_if); + sk_init_locked(sc_if); } else { if (ifp->if_flags & IFF_RUNNING) sk_stop(sc_if); @@ -1259,12 +1276,12 @@ break; case SIOCADDMULTI: case SIOCDELMULTI: + SK_IF_LOCK(sc_if); if (ifp->if_flags & IFF_RUNNING) { - SK_IF_LOCK(sc_if); sk_setmulti(sc_if); - SK_IF_UNLOCK(sc_if); error = 0; } + SK_IF_UNLOCK(sc_if); break; case SIOCGIFMEDIA: case SIOCSIFMEDIA: @@ -1343,7 +1360,10 @@ * register represents 18.825ns, so to specify a timeout in * microseconds, we have to multiply by 54. */ - sk_win_write_4(sc, SK_IMTIMERINIT, SK_IM_USECS(200)); + if (bootverbose) + printf("skc%d: interrupt moderation is %d us\n", + sc->sk_unit, sc->sk_int_mod); + sk_win_write_4(sc, SK_IMTIMERINIT, SK_IM_USECS(sc->sk_int_mod)); sk_win_write_4(sc, SK_IMMR, SK_ISR_TX1_S_EOF|SK_ISR_TX2_S_EOF| SK_ISR_RX1_EOF|SK_ISR_RX2_EOF); sk_win_write_1(sc, SK_IMTIMERCTL, SK_IMCTL_START); @@ -1609,6 +1629,25 @@ goto fail; } + SYSCTL_ADD_PROC(device_get_sysctl_ctx(dev), + SYSCTL_CHILDREN(device_get_sysctl_tree(dev)), + OID_AUTO, "int_mod", CTLTYPE_INT|CTLFLAG_RW, + &sc->sk_int_mod, 0, sysctl_hw_sk_int_mod, "I", + "SK interrupt moderation"); + + /* Pull in device tunables. */ + sc->sk_int_mod = SK_IM_DEFAULT; + error = resource_int_value(device_get_name(dev), unit, + "int_mod", &sc->sk_int_mod); + if (error == 0) { + if (sc->sk_int_mod < SK_IM_MIN || + sc->sk_int_mod > SK_IM_MAX) { + printf("skc%d: int_mod value out of range; " + "using default: %d\n", unit, SK_IM_DEFAULT); + sc->sk_int_mod = SK_IM_DEFAULT; + } + } + /* Reset the adapter. */ sk_reset(sc); @@ -1639,7 +1678,7 @@ break; default: printf("skc%d: unknown ram size: %d\n", - sc->sk_unit, sk_win_read_1(sc, SK_EPROM0)); + sc->sk_unit, skrs); error = ENXIO; goto fail; } @@ -1752,16 +1791,74 @@ revstr = ""; } - /* Announce the product name. */ - device_printf(dev, "%s rev. %s(0x%x)\n", pname, revstr, sc->sk_rev); + /* Announce the product name and more VPD data if there. */ + device_printf(dev, "%s rev. %s(0x%x)\n", + pname != NULL ? pname : "", revstr, sc->sk_rev); + + if (bootverbose) { + if (sc->sk_vpd_readonly != NULL && + sc->sk_vpd_readonly_len != 0) { + char buf[256]; + char *dp = sc->sk_vpd_readonly; + uint16_t l, len = sc->sk_vpd_readonly_len; + + while (len >= 3) { + if ((*dp == 'P' && *(dp+1) == 'N') || + (*dp == 'E' && *(dp+1) == 'C') || + (*dp == 'M' && *(dp+1) == 'N') || + (*dp == 'S' && *(dp+1) == 'N')) { + l = 0; + while (l < *(dp+2)) { + buf[l] = *(dp+3+l); + ++l; + } + buf[l] = '\0'; + device_printf(dev, "%c%c: %s\n", + *dp, *(dp+1), buf); + len -= (3 + l); + dp += (3 + l); + } else { + len -= (3 + *(dp+2)); + dp += (3 + *(dp+2)); + } + } + } + device_printf(dev, "chip ver = 0x%02x\n", sc->sk_type); + device_printf(dev, "chip rev = 0x%02x\n", sc->sk_rev); + device_printf(dev, "SK_EPROM0 = 0x%02x\n", skrs); + device_printf(dev, "SRAM size = 0x%06x\n", sc->sk_ramsize); + } + sc->sk_devs[SK_PORT_A] = device_add_child(dev, "sk", -1); + if (sc->sk_devs[SK_PORT_A] == NULL) { + device_printf(dev, "failed to add child for PORT_A\n"); + error = ENXIO; + goto fail; + } port = malloc(sizeof(int), M_DEVBUF, M_NOWAIT); + if (port == NULL) { + device_printf(dev, "failed to allocate memory for " + "ivars of PORT_A\n"); + error = ENXIO; + goto fail; + } *port = SK_PORT_A; device_set_ivars(sc->sk_devs[SK_PORT_A], port); if (!(sk_win_read_1(sc, SK_CONFIG) & SK_CONFIG_SINGLEMAC)) { sc->sk_devs[SK_PORT_B] = device_add_child(dev, "sk", -1); + if (sc->sk_devs[SK_PORT_B] == NULL) { + device_printf(dev, "failed to add child for PORT_B\n"); + error = ENXIO; + goto fail; + } port = malloc(sizeof(int), M_DEVBUF, M_NOWAIT); + if (port == NULL) { + device_printf(dev, "failed to allocate memory for " + "ivars of PORT_B\n"); + error = ENXIO; + goto fail; + } *port = SK_PORT_B; device_set_ivars(sc->sk_devs[SK_PORT_B], port); } @@ -1769,7 +1866,11 @@ /* Turn on the 'driver is loaded' LED. */ CSR_WRITE_2(sc, SK_LED, SK_LED_GREEN_ON); - bus_generic_attach(dev); + error = bus_generic_attach(dev); + if (error) { + device_printf(dev, "failed to attach port(s)\n"); + goto fail; + } /* Hook interrupt last to avoid having to lock softc */ error = bus_setup_intr(dev, sc->sk_irq, INTR_TYPE_NET|INTR_MPSAFE, @@ -1930,6 +2031,21 @@ sk_start(ifp) struct ifnet *ifp; { + struct sk_if_softc *sc_if; + + sc_if = ifp->if_softc; + + SK_IF_LOCK(sc_if); + sk_start_locked(ifp); + SK_IF_UNLOCK(sc_if); + + return; +} + +static void +sk_start_locked(ifp) + struct ifnet *ifp; +{ struct sk_softc *sc; struct sk_if_softc *sc_if; struct mbuf *m_head = NULL; @@ -1938,7 +2054,7 @@ sc_if = ifp->if_softc; sc = sc_if->sk_softc; - SK_IF_LOCK(sc_if); + SK_IF_LOCK_ASSERT(sc_if); idx = sc_if->sk_cdata.sk_tx_prod; @@ -1973,7 +2089,6 @@ /* Set a timeout in case the chip goes out to lunch. */ ifp->if_timer = 5; } - SK_IF_UNLOCK(sc_if); return; } @@ -1988,8 +2103,10 @@ sc_if = ifp->if_softc; printf("sk%d: watchdog timeout\n", sc_if->sk_unit); + SK_IF_LOCK(sc_if); ifp->if_flags &= ~IFF_RUNNING; - sk_init(sc_if); + sk_init_locked(sc_if); + SK_IF_UNLOCK(sc_if); return; } @@ -2358,9 +2475,9 @@ CSR_WRITE_4(sc, SK_IMR, sc->sk_intrmask); if (ifp0 != NULL && !IFQ_DRV_IS_EMPTY(&ifp0->if_snd)) - sk_start(ifp0); + sk_start_locked(ifp0); if (ifp1 != NULL && !IFQ_DRV_IS_EMPTY(&ifp1->if_snd)) - sk_start(ifp1); + sk_start_locked(ifp1); SK_UNLOCK(sc); @@ -2546,7 +2663,7 @@ ifp = &sc_if->arpcom.ac_if; if (sc->sk_type == SK_YUKON_LITE && - sc->sk_rev == SK_YUKON_LITE_REV_A3) { + sc->sk_rev >= SK_YUKON_LITE_REV_A3) { /* Take PHY out of reset. */ sk_win_write_4(sc, SK_GPIO, (sk_win_read_4(sc, SK_GPIO) | SK_GPIO_DIR9) & ~SK_GPIO_DAT9); @@ -2650,21 +2767,32 @@ void *xsc; { struct sk_if_softc *sc_if = xsc; + + SK_IF_LOCK(sc_if); + sk_init_locked(sc_if); + SK_IF_UNLOCK(sc_if); + + return; +} + +static void +sk_init_locked(sc_if) + struct sk_if_softc *sc_if; +{ struct sk_softc *sc; struct ifnet *ifp; struct mii_data *mii; u_int16_t reg; + u_int32_t imr; - SK_IF_LOCK(sc_if); + SK_IF_LOCK_ASSERT(sc_if); ifp = &sc_if->arpcom.ac_if; sc = sc_if->sk_softc; mii = device_get_softc(sc_if->sk_miibus); - if (ifp->if_flags & IFF_RUNNING) { - SK_IF_UNLOCK(sc_if); + if (ifp->if_flags & IFF_RUNNING) return; - } /* Cancel pending I/O and free all RX/TX buffers. */ sk_stop(sc_if); @@ -2746,11 +2874,21 @@ printf("sk%d: initialization failed: no " "memory for rx buffers\n", sc_if->sk_unit); sk_stop(sc_if); - SK_IF_UNLOCK(sc_if); return; } sk_init_tx_ring(sc_if); + /* Set interrupt moderation if changed via sysctl. */ + /* SK_LOCK(sc); */ + imr = sk_win_read_4(sc, SK_IMTIMERINIT); + if (imr != SK_IM_USECS(sc->sk_int_mod)) { + sk_win_write_4(sc, SK_IMTIMERINIT, SK_IM_USECS(sc->sk_int_mod)); + if (bootverbose) + printf("skc%d: interrupt moderation is %d us\n", + sc->sk_unit, sc->sk_int_mod); + } + /* SK_UNLOCK(sc); */ + /* Configure interrupt handling */ CSR_READ_4(sc, SK_ISSR); if (sc_if->sk_port == SK_PORT_A) @@ -2783,8 +2921,6 @@ ifp->if_flags |= IFF_RUNNING; ifp->if_flags &= ~IFF_OACTIVE; - SK_IF_UNLOCK(sc_if); - return; } @@ -2796,7 +2932,7 @@ struct sk_softc *sc; struct ifnet *ifp; - SK_IF_LOCK(sc_if); + SK_IF_LOCK_ASSERT(sc_if); sc = sc_if->sk_softc; ifp = &sc_if->arpcom.ac_if; @@ -2867,6 +3003,29 @@ } ifp->if_flags &= ~(IFF_RUNNING|IFF_OACTIVE); - SK_IF_UNLOCK(sc_if); + return; } + +static int +sysctl_int_range(SYSCTL_HANDLER_ARGS, int low, int high) +{ + int error, value; + + if (!arg1) + return (EINVAL); + value = *(int *)arg1; + error = sysctl_handle_int(oidp, &value, 0, req); + if (error || !req->newptr) + return (error); + if (value < low || value > high) + return (EINVAL); + *(int *)arg1 = value; + return (0); +} + +static int +sysctl_hw_sk_int_mod(SYSCTL_HANDLER_ARGS) +{ + return (sysctl_int_range(oidp, arg1, arg2, req, SK_IM_MIN, SK_IM_MAX)); +} Index: if_skreg.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_skreg.h,v retrieving revision 1.20.2.5 diff -u -r1.20.2.5 if_skreg.h --- if_skreg.h 28 Mar 2005 16:21:16 -0000 1.20.2.5 +++ if_skreg.h 10 Aug 2005 22:23:38 -0000 @@ -376,6 +376,10 @@ #define SK_IMTIMER_TICKS 54 #define SK_IM_USECS(x) ((x) * SK_IMTIMER_TICKS) +#define SK_IM_MIN 10 +#define SK_IM_DEFAULT 100 +#define SK_IM_MAX 10000 + /* * The SK_EPROM0 register contains a byte that describes the * amount of SRAM mounted on the NIC. The value also tells if @@ -1437,10 +1441,12 @@ u_int8_t spare; char *sk_vpd_prodname; char *sk_vpd_readonly; + uint16_t sk_vpd_readonly_len; u_int32_t sk_rboff; /* RAMbuffer offset */ u_int32_t sk_ramsize; /* amount of RAM on NIC */ u_int32_t sk_pmd; /* physical media type */ u_int32_t sk_intrmask; + int sk_int_mod; struct sk_if_softc *sk_if[2]; device_t sk_devs[2]; struct mtx sk_mtx; From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 23:16:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 552FA16A41F for ; Wed, 10 Aug 2005 23:16:44 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from tensor.xs4all.nl (tensor.xs4all.nl [194.109.160.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9C0D43D48 for ; Wed, 10 Aug 2005 23:16:43 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from kilgore.dim (kilgore.dim [192.168.0.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.xs4all.nl (Postfix) with ESMTP id CFACCB80C; Thu, 11 Aug 2005 01:16:41 +0200 (CEST) Date: Thu, 11 Aug 2005 01:16:37 +0200 From: Dimitry Andric X-Mailer: The Bat! (v3.51.10) Professional X-Priority: 3 (Normal) Message-ID: <476320185.20050811011637@andric.com> To: Max Laier In-Reply-To: <200508102333.42540.max@love2party.net> References: <200508102333.42540.max@love2party.net> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="----------641C21251AB402D3" Cc: "J. Nyhuis" , freebsd-stable@freebsd.org Subject: Re: Q: How do I suggest a change to a FreeBSD Man page? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dimitry Andric List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 23:16:44 -0000 ------------641C21251AB402D3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable [Max, did you really direct your reply to instead of ? Probably pushed the wrong button...] On 2005-08-10 at 23:33:29 Max Laier wrote: > As for the request itself. As for > the request itself, I am very reluctant to take manpages off the vendor > branch too much without very good reason. Everything you change you have= to > catch up manually once we import new code ... so this is a long term=20 > commitment. Another suggestion would be to submit such pf manpage suggestions upstream, i.e. directly to the OpenBSD people; then they'll trickle down almost automagically. :) It's usually best to mail misc at openbsd.org for stuff like this. ------------641C21251AB402D3 Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFC+orVsF6jCi4glqMRAnVVAJ9Y+WgrwEVxzvGaXbsBR3Ck8cSBZQCdGaTX sjqteFYLkCEGLWJbjMnd2lM= =HvBQ -----END PGP MESSAGE----- ------------641C21251AB402D3-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 10 23:47:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8B9116A420 for ; Wed, 10 Aug 2005 23:47:01 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-68-15-213-52.at.at.cox.net [68.15.213.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7921B43D48 for ; Wed, 10 Aug 2005 23:47:00 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.3/8.13.1) with SMTP id j7ANkxC5020548 for ; Wed, 10 Aug 2005 18:46:59 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Wed Aug 10 18:46:59 2005 Received: (from karl@localhost) by FS.denninger.net (8.13.3/8.13.1/Submit) id j7ANkxo4020546 for freebsd-stable@freebsd.org; Wed, 10 Aug 2005 18:46:59 -0500 (CDT) (envelope-from karl) Date: Wed, 10 Aug 2005 18:46:59 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20050810234659.GA19768@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20050810023111.GA2913@FS.denninger.net> <20050810024618.GA8198@drjekyll.mkbuelow.net> <6.2.1.2.0.20050810081251.05298ff0@64.7.153.2> <20050810133159.GA10150@FS.denninger.net> <6.2.1.2.0.20050810094204.06c46098@64.7.153.2> <20050810144148.GB10150@FS.denninger.net> <790a9fff0508100844a7e5435@mail.gmail.com> <4A1BF8DF-EC50-4067-A69B-84D9BE5B22C7@FreeBSD.ORG> <20050810205101.GA17483@FS.denninger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 23:47:01 -0000 On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote: > > On 10/08/2005, at 22:51, Karl Denninger wrote: > > > >This is the subject of the PR I filed back in February. > > > >Again, if you want either a controller shipped to you OR access to a > >development machine (e.g. ssh in and play) which has the suspect > >configuration on it, the latter of which is probably the best > >option (since > >making it fail is simple) I'm willing to provide either - my only > >caveat is > >that if I send hardware I want it back when you're done, and I > >believe its > >reasonable to expect that 6.0 will get HELD in its release cycle > >until this > >is resolved. > > I have plenty of the sii3112's around, so thats not needed, however > I've not managed to get ahold of a machine in which it fails reliably > with ATA as is in 6.0. I have two which reliably fail if you put TWO disks on them in a gmirror config within minutes of starting a "make buildworld". With one disk it takes a bit longer and more effort, but can still be forced to fail. It appears to require a mix of read and write operations and a fairly heavy - but not horiffically so - I/O load to make it blow up. All reads or all writes do NOT fail. For example, you can do a gmirror rebuild and it will succeed. That's all writes (to the new disks) until complete. Seconds to minutes after the rebuilds complete if the system is under heavy random I/O load it will fail. >From this and other tests I've concluded that a MIX of read and write operations are required, and the total load must be substantial. Either reads alone or writes alone do not appear to provoke it, even with 100% disk utilization. > >The latter offer (ssh access) has been on the table for several > >months. The > >former I just put on the table as I threw up my hands and bought a > >3ware > >card - which means I now have TWO of the suspect cards and need > >only one > >for my own testing (in the sandbox) > > > >I'm willing to go WELL out of my way to make it possible for this > >to get > >fixed, since there appears to be an issue with access to hardware that > >breaks reliably. However, I, and others, would like to know that > >we're > >going to see the problem get resolved. > > I've already gone WAY out of my way to try to support the sii3112, > and I'm not inclined to waste more of my precious spare time on it. > However, if it really is that important to enough people to try to > workaround the silicon bugs (which very likely isn't possible), get > together and get me failing HW on my desk and time to work on it. Ok, then do the RIGHT THING and document that the SiI chips are declared BROKEN by FreeBSD and likely to cause people trouble - including irrevocable data corruption. This would have saved me COUNTLESS hours when I first ran into this issue. Indeed, it was not until someone else started posting excerpts from commit logs (months after I filed the PR originally!) that I was aware FreeBSD developers considered these chipsets "damaged goods". Where is fair warning in the hardware compatability guide? Second, your requirement for hardware simply can't be met. It is not possible for anyone to manufacture or deliver time. Is it thus necessary for us "mere users" to consider this an issue that will simply not be addressed? If so, then just say so up front > >Again - this is hardware that is STABLE and works under 4.x - in > >the case of > >my specific configuration I ran under 4.x for over a year without a > >single > >incident. With 5.4 and 6.0-BETA I can kill it inside of 2 minutes > >with > >nothing more complicated than a "make -j4 buildworld". > > First. you cannot by any degree of the word call the sii3112 for > STABLE hardware, its broken beyond repair or workarounds, and even > the supplier acknowledges that fact. Well then how about if FreeBSD officially DECLARES this hardware to be broken beyond repair and workaround, and simply says "if this doesn't work for you, don't bitch or complain, because we have nothing further we can do about it"? That is acceptable, although I bet it costs 'ya a fair number of users, particularly in the small server and workstation markets. Of course since its not "money lost", that may be perfectly OK to the FreeBSD team. It definitely will change MY focus as a developer of software often run on small office and home network machines though. It HAS TO Soren. This isn't a matter of me not wanting to be a FreeBSD evangelist - but if I try to tell people that half of the machines out there that they might run FreeBSD on are likely to fail, and if they do my only recommendation is "sorry, I can't do anything about it other than sell you this hardware", the obvious next reply is that they will want the software to be made available on an operating system that DOESN'T blow up like this. Linux ends up being something I have to support of necessity down that road...... (a thing I've studiously avoided now for five years, by the way.) I have a 3ware card in my production machine now and the "allegedly broken" disks are magically just fine. Guess the disks are fine eh? Of course I lost the functionality that I thought I was getting with the newer ATA code anyway, since the 3ware software doesn't support hot plug, and I also lost access to the disk statistics and self-test capabilities that smartmontools has, since 3ware's board doesn't pass that through cleanly either. But all this begs the question - why did it work on 4.x, and how come the same timing constraints and code paths that worked on 4.x can't / weren't incorporated into what's there now? > Second, you cannot possibly have used gmirror (as in the PR) on 4.x > so what was the config back then ? I didn't NEED gmirror back then. Attempting to use these disks on a SiI controller WITHOUT gmirror in 5.4 or even 6.0 is asking to have to reload the machine as the errors cause irrevocable data corruption. I'm not about to subject myself to having to reload a machine a few hundred times while troubleshooting it, and I suspect you know that is a completely unreasonable request. Gmirror was added to my config in an attempt to stop the crashes during testing - with at least one disk in the mirror on the ICH5 adapter the system (and data) survives. It turns out that on 5.x this is much more "reasonable" to use than vinum, which was severely broken in 5.x (may be fixed now as "gvinum", I didn't give it anoyther crack after pulling my hair out for quite a long time with THAT one.) I assure you that the load profiles that generate BOOMs on 5.4 and 6.0-BETA do NOT under 4.x with the IDENTICAL hardware in use. Over a year of heavy production use of 4.x with ZERO trouble is my evidence for this. > Third, please get gmirror out of the loop (use atacontrol to create a > mirror if need be) and let me know if that changes anything. Uh, if the abstraction done by GEOM is hardware-independant, and the error comes from the DRIVER, how can GEOM be involved? GEOM (gmirror in this case) prevents me from having to reload the machine every time it blows up due to data corruption that cannot be fixed. Never mind that others are reporting irrevocable data loss and crashes - they aren't mirrored..... I've managed to keep my data intact.... "atacontrol" doesn't help me as there is no rebuild mechanism available for "garden variety" controllers (at least the last time I tried it that did nothing.) So you can build the array but after the first crash you had no way to recover. That's only marginally better than having the crash wipe the sidewalk with the data on your drive, in terms of troubleshooting effort. > Forth, another thing to try is fumbling with BIOS settings, some > setups has been reported to start working when PCI timings is changed > YMMV.. > > - S?ren I can play with this.... but if the hardware is the cause and requires tweaking timing in the PCI BIOS config, how come 4.x works without any tweaking on the same hardware? In short, what's changed in the DRIVER timing that provokes this sort of thing , and does it NEED to have changed? Again, I can easily set up ssh access to a machine that has problems with this, and the "BOOM"s are VERY repeatable. >From the other postings here, I am by no means an isolated user with an isolated problem - the issue is fairly widespread. I suspect, but of course cannot prove, that if you find the issue with my machine, you will likely fix a lot of other people's issues with similar problems...... I could be wrong, but I bet not...... In any event the ATA code changes have hurt a LOT of people Soren and led to a huge amount of wasted time. If it was known that the SiI chipsets simply were never going to get full support (because they are considered "unsupportable") then it is only right for the development team to DOCUMENT THIS rather than letting people find out for themselves the hard way, pulling their hair out looking for phantom bad disk drives and phantom problems with cables - neither of which has anything to do with it. If there is going to be no path out of this mess then just say so and we'll realign our expectations of where FreeBSD fits in terms of what environments it is reasonable to consider it for. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Thu Aug 11 00:55:34 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8027816A41F for ; Thu, 11 Aug 2005 00:55:34 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3387843D46 for ; Thu, 11 Aug 2005 00:55:34 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 345A667800 for ; Thu, 11 Aug 2005 00:55:33 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.3/8.13.1) with ESMTP id j7B0tNOp047256 for ; Thu, 11 Aug 2005 10:55:23 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200508110055.j7B0tNOp047256@drugs.dv.isc.org> To: stable@freebsd.org From: Mark Andrews Date: Thu, 11 Aug 2005 10:55:23 +1000 Sender: Mark_Andrews@isc.org Cc: Subject: IPv6 router solicitation not being received X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2005 00:55:34 -0000 I have a problem in that the router solicitations are not being received by my FreeBSD IPv6 router unless I enable promiscuous mode on the tx0 interface. This causes delays to autoconf for other IPv6 boxes on the net until the periodic router announcement is sent. This leads me to believe that either the multicast hash function is wrong or the request for multicast reception on the interface is not getting through to the driver. "rtadvd tx0" is running so theoretically it should be getting through. Anyone aware of any issues in this area? Yes the kernel is a bit old and needs to be updated. Mark tx0: flags=28943 mtu 1500 inet 192.168.191.233 netmask 0xffffff00 broadcast 192.168.191.255 inet6 fe80::2e0:29ff:fe19:c02d%tx0 prefixlen 64 scopeid 0x1 inet6 2001:470:1f00:820:2e0:29ff:fe19:c02d prefixlen 64 inet6 2001:470:1f00:820:: prefixlen 64 anycast ether 00:e0:29:19:c0:2d media: Ethernet autoselect (10baseT/UTP) status: active sis0: flags=8843 mtu 1500 inet6 fe80::209:5bff:fe1e:e13e%sis0 prefixlen 64 scopeid 0x2 inet 220.237.98.197 netmask 0xffffff00 broadcast 220.237.98.255 ether 00:09:5b:1e:e1:3e media: Ethernet autoselect (100baseTX ) status: active lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 inet 10.53.0.1 netmask 0xffffffff inet 10.53.0.2 netmask 0xffffffff inet 10.53.0.3 netmask 0xffffffff inet 10.53.0.4 netmask 0xffffffff inet 10.53.0.5 netmask 0xffffffff inet 10.53.0.6 netmask 0xffffffff inet 10.53.0.7 netmask 0xffffffff inet 10.53.0.8 netmask 0xffffffff ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 faith0: flags=8002 mtu 1500 gif0: flags=8051 mtu 1280 tunnel inet 220.237.98.197 --> 64.71.128.82 inet6 fe80::2e0:29ff:fe19:c02d%gif0 prefixlen 64 scopeid 0x8 inet6 2001:470:1f00:ffff::5a1 --> 2001:470:1f00:ffff::5a0 prefixlen 128 FreeBSD bsdi.dv.isc.org 4.11-STABLE FreeBSD 4.11-STABLE #22: Mon Jan 3 22:18:47 EST 2005 marka@bsdi.dv.isc.org:/usr/obj/usr/src/sys/BSDI i386 Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.11-STABLE #22: Mon Jan 3 22:18:47 EST 2005 marka@bsdi.dv.isc.org:/usr/obj/usr/src/sys/BSDI Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (298.65-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) config> di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> q avail memory = 125607936 (122664K bytes) Preloaded elf kernel "kernel" at 0xc04e3000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04e309c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xc00fdf30 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff at d evice 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1c20-0x1c2f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1c00-0x1c1f irq 9 at dev ice 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip0: port 0x7000-0x700f at device 7.3 on pci0 pci0: (vendor=0x1013, dev=0x6001) at 11.0 irq 9 pci0: at 13.0 irq 11 ahc0: port 0x1000-0x10ff mem 0xf4805000-0xf480 5fff irq 15 at device 14.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs tx0: port 0x1400-0x14ff mem 0xf4806000-0xf4806fff irq 9 at device 15.0 on pci0 qsphy0: on miibus0 qsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto tx0: address 00:e0:29:19:c0:2d, type SMC9432TX sis0: port 0x1800-0x18ff mem 0xf4807000-0xf4807ff f irq 9 at device 16.0 on pci0 sis0: Ethernet address: 00:09:5b:1e:e1:3e miibus1: on sis0 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: