From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 9 09:18:04 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E52E3106564A for ; Sun, 9 Aug 2009 09:18:04 +0000 (UTC) (envelope-from bjb@darco.dk) Received: from pasmtpB.tele.dk (pasmtpb.tele.dk [80.160.77.98]) by mx1.freebsd.org (Postfix) with ESMTP id A96D98FC19 for ; Sun, 9 Aug 2009 09:18:03 +0000 (UTC) Received: from v8.blichsoft.dk (0x503e00ba.cpe.ge-0-2-0-1101.banqu1.customer.tele.dk [80.62.0.186]) by pasmtpB.tele.dk (Postfix) with ESMTP id 7FD16E31E15 for ; Sun, 9 Aug 2009 10:54:40 +0200 (CEST) Received: by v8.blichsoft.dk (Postfix, from userid 110) id 525B1117D4; Sun, 9 Aug 2009 10:54:40 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on v8.blichsoft.dk X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50 autolearn=ham version=3.2.5 Received: from [192.168.1.200] (sussi [192.168.1.200]) by v8.blichsoft.dk (Postfix) with ESMTP id B7AF411402 for ; Sun, 9 Aug 2009 10:54:37 +0200 (CEST) Message-ID: <4A7E8ECD.8010208@darco.dk> Date: Sun, 09 Aug 2009 10:54:37 +0200 From: Bjarne User-Agent: Thunderbird 2.0.0.22 (X11/20090605) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Status: No X-Virus-Checker-Version: clamassassin 1.2.4 with clamdscan / ClamAV 0.95.2/9668/Fri Aug 7 23:36:10 2009 Subject: dwa-547 - atheros chip not recognized X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 09:18:05 -0000 Sorry if this comes trough twice.. Just installed a d-link dwa-547 in my server, but the ath driver does not recognize it. uname -a : FreeBSD v8.blichsoft.dk 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat Aug 8 15:30:35 CEST 2009 toor@machine:/usr/obj/usr/src-8aug2009/sys/V8 i386 cvsup from 7-aug-2009 pciconf -lv : none1@pci0:3:5:0: class=0x028000 card=0x3a781186 chip=0x0029168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network options AH_SUPPORT_AR5416 is set in the kernel config Good ideas are welcome. I am stuck on this one. In the manual for ath(4) it say all chips are supported, except AR5005VL, and I have seen other references to people using this particular card. I read it is a Atheros AR5416 chipset. >From the boot messages : Aug 8 15:57:07 v8 kernel: pcib3: at device 20.4 on pci0 Aug 8 15:57:07 v8 kernel: pcib3: domain 0 Aug 8 15:57:07 v8 kernel: pcib3: secondary bus 3 Aug 8 15:57:07 v8 kernel: pcib3: subordinate bus 3 Aug 8 15:57:07 v8 kernel: pcib3: I/O decode 0xf000-0xfff Aug 8 15:57:07 v8 kernel: pcib3: memory decode 0xfeb00000-0xfebfffff Aug 8 15:57:07 v8 kernel: pcib3: no prefetched decode Aug 8 15:57:07 v8 kernel: pcib3: Subtractively decoded bridge. Aug 8 15:57:07 v8 kernel: pci3: on pcib3 Aug 8 15:57:07 v8 kernel: pci3: domain=0, physical bus=3 Aug 8 15:57:07 v8 kernel: found-> vendor=0x168c, dev=0x0029, revid=0x01 (* Aug 8 15:57:07 v8 kernel: domain=0, bus=3, slot=5, func=0 Aug 8 15:57:07 v8 kernel: class=02-80-00, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0116, statreg=0x02b0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=10 Aug 8 15:57:07 v8 kernel: powerspec 2 supports D0 D3 current D0 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfebf0000, size 16, enabled Aug 8 15:57:07 v8 kernel: pcib3: requested memory range 0xfebf0000-0xfebfffff: good Aug 8 15:57:07 v8 kernel: pcib3: matched entry for 3.5.INTA Aug 8 15:57:07 v8 kernel: pcib3: slot 5 INTA hardwired to IRQ 20 Aug 8 15:57:07 v8 kernel: pci3: at device 5.0 (no driver attached) (* Which seems to be defined in /usr/src/sys/dev/ath/ath_hal/ah_devid.h However, there is also /usr/src/sys/contrib/dev/ath/ah_devid.h where the card is not defined. How do I make sure I get the right one ? Regards, Bjarne Verbose boot message : Aug 8 15:57:07 v8 syslogd: kernel boot file is /boot/kernel/kernel Aug 8 15:57:07 v8 kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done Aug 8 15:57:07 v8 kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Aug 8 15:57:07 v8 kernel: Waiting (max 60 seconds) for system process `syncer' to stop... Aug 8 15:57:07 v8 kernel: Syncing disks, vnodes remaining...5 1 4 4 0 0 done Aug 8 15:57:07 v8 kernel: All buffers synced. Aug 8 15:57:07 v8 kernel: Copyright (c) 1992-2009 The FreeBSD Project. Aug 8 15:57:07 v8 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 8 15:57:07 v8 kernel: The Regents of the University of California. All rights reserved. Aug 8 15:57:07 v8 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Aug 8 15:57:07 v8 kernel: FreeBSD 7.2-STABLE #0: Sat Aug 8 15:30:35 CEST 2009 Aug 8 15:57:07 v8 kernel: toor@v8.blichsoft.dk:/usr/obj/usr/src-8aug2009/sys/V8 Aug 8 15:57:07 v8 kernel: Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ea9000. Aug 8 15:57:07 v8 kernel: Preloaded elf module "/boot/kernel/wlan_xauth.ko" at 0xc0ea9188. Aug 8 15:57:07 v8 kernel: Preloaded elf module "/boot/kernel/cpufreq.ko" at 0xc0ea9238. Aug 8 15:57:07 v8 kernel: Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0ea92e4. Aug 8 15:57:07 v8 kernel: Calibrating clock(s) ... i8254 clock: 1193294 Hz Aug 8 15:57:07 v8 kernel: CLK_USE_I8254_CALIBRATION not specified - using default frequency Aug 8 15:57:07 v8 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Aug 8 15:57:07 v8 kernel: Calibrating TSC clock ... TSC clock: 2594290746 Hz Aug 8 15:57:07 v8 kernel: CPU: AMD Athlon(tm) Dual Core Processor 5050e (2594.29-MHz 686-class CPU) Aug 8 15:57:07 v8 kernel: Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 Aug 8 15:57:07 v8 kernel: Features=0x178bfbff Aug 8 15:57:07 v8 kernel: Features2=0x2001 Aug 8 15:57:07 v8 kernel: AMD Features=0xea500800 Aug 8 15:57:07 v8 kernel: AMD Features2=0x11f Aug 8 15:57:07 v8 kernel: TSC: P-state invariant Aug 8 15:57:07 v8 kernel: Cores per package: 2 Aug 8 15:57:07 v8 kernel: Data TLB: 32 entries, fully associative Aug 8 15:57:07 v8 kernel: Instruction TLB: 32 entries, fully associative Aug 8 15:57:07 v8 kernel: L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative Aug 8 15:57:07 v8 kernel: L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative Aug 8 15:57:07 v8 kernel: L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative Aug 8 15:57:07 v8 kernel: real memory = 3489333248 (3327 MB) Aug 8 15:57:07 v8 kernel: Physical memory chunk(s): Aug 8 15:57:07 v8 kernel: 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) Aug 8 15:57:07 v8 kernel: 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) Aug 8 15:57:07 v8 kernel: 0x0000000001025000 - 0x00000000cc4cdfff, 3410661376 bytes (832681 pages) Aug 8 15:57:07 v8 kernel: avail memory = 3409981440 (3252 MB) Aug 8 15:57:07 v8 kernel: Table 'FACP' at 0xcffb0200 Aug 8 15:57:07 v8 kernel: Table 'APIC' at 0xcffb0390 Aug 8 15:57:07 v8 kernel: MADT: Found table at 0xcffb0390 Aug 8 15:57:07 v8 kernel: MP Configuration Table version 1.4 found at 0xc00fca80 Aug 8 15:57:07 v8 kernel: APIC: Using the MADT enumerator. Aug 8 15:57:07 v8 kernel: MADT: Found CPU APIC ID 0 ACPI ID 1: enabled Aug 8 15:57:07 v8 kernel: SMP: Added CPU 0 (AP) Aug 8 15:57:07 v8 kernel: MADT: Found CPU APIC ID 1 ACPI ID 2: enabled Aug 8 15:57:07 v8 kernel: SMP: Added CPU 1 (AP) Aug 8 15:57:07 v8 kernel: MADT: Found CPU APIC ID 130 ACPI ID 3: disabled Aug 8 15:57:07 v8 kernel: MADT: Found CPU APIC ID 131 ACPI ID 4: disabled Aug 8 15:57:07 v8 kernel: ACPI APIC Table: <021609 APIC1645> Aug 8 15:57:07 v8 kernel: INTR: Adding local APIC 1 as a target Aug 8 15:57:07 v8 kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Aug 8 15:57:07 v8 kernel: cpu0 (BSP): APIC ID: 0 Aug 8 15:57:07 v8 kernel: cpu1 (AP): APIC ID: 1 Aug 8 15:57:07 v8 kernel: bios32: Found BIOS32 Service Directory header at 0xc00f0000 Aug 8 15:57:07 v8 kernel: bios32: Entry = 0xf0010 (c00f0010) Rev = 0 Len = 1 Aug 8 15:57:07 v8 kernel: pcibios: PCI BIOS entry at 0xf0000+0x31 Aug 8 15:57:07 v8 kernel: pnpbios: Found PnP BIOS data at 0xc00fa130 Aug 8 15:57:07 v8 kernel: pnpbios: Entry = f0000:5f6a Rev = 1.0 Aug 8 15:57:07 v8 kernel: Other BIOS signatures found: Aug 8 15:57:07 v8 kernel: APIC: CPU 0 has ACPI ID 1 Aug 8 15:57:07 v8 kernel: APIC: CPU 1 has ACPI ID 2 Aug 8 15:57:07 v8 kernel: ULE: setup cpu group 0 Aug 8 15:57:07 v8 kernel: ULE: setup cpu 0 Aug 8 15:57:07 v8 kernel: ULE: adding cpu 0 to group 0: cpus 1 mask 0x1 Aug 8 15:57:07 v8 kernel: ULE: setup cpu group 1 Aug 8 15:57:07 v8 kernel: ULE: setup cpu 1 Aug 8 15:57:07 v8 kernel: ULE: adding cpu 1 to group 1: cpus 1 mask 0x2 Aug 8 15:57:07 v8 kernel: ACPI: RSDP @ 0x0xfaf60/0x0014 (v 0 ACPIAM) Aug 8 15:57:07 v8 kernel: ACPI: RSDT @ 0x0xcffb0000/0x003C (v 1 021609 RSDT1645 0x20090216 MSFT 0x00000097) Aug 8 15:57:07 v8 kernel: ACPI: FACP @ 0x0xcffb0200/0x0084 (v 1 A M I OEMFACP 0x12000601 MSFT 0x00000097) Aug 8 15:57:07 v8 kernel: ACPI Warning (tbfadt-0505): Optional field "Pm2ControlBlock" has zero address or length: 0 0/1 [20070320] Aug 8 15:57:07 v8 kernel: ACPI: DSDT @ 0x0xcffb0440/0x8ECF (v 1 AS216 AS216101 0x00000101 INTL 0x20051117) Aug 8 15:57:07 v8 kernel: ACPI: FACS @ 0x0xcffc0000/0x0040 Aug 8 15:57:07 v8 kernel: ACPI: APIC @ 0x0xcffb0390/0x006C (v 1 021609 APIC1645 0x20090216 MSFT 0x00000097) Aug 8 15:57:07 v8 kernel: ACPI: MCFG @ 0x0xcffb0400/0x003C (v 1 021609 OEMMCFG 0x20090216 MSFT 0x00000097) Aug 8 15:57:07 v8 kernel: ACPI: OEMB @ 0x0xcffc0040/0x0072 (v 1 021609 OEMB1645 0x20090216 MSFT 0x00000097) Aug 8 15:57:07 v8 kernel: ACPI: AAFT @ 0x0xcffba440/0x0027 (v 1 021609 OEMAAFT 0x20090216 MSFT 0x00000097) Aug 8 15:57:07 v8 kernel: ACPI: SSDT @ 0x0xcffba470/0x028A (v 1 A M I POWERNOW 0x00000001 AMD 0x00000001) Aug 8 15:57:07 v8 kernel: MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 Aug 8 15:57:07 v8 kernel: ioapic0: Routing external 8259A's -> intpin 0 Aug 8 15:57:07 v8 kernel: MADT: Interrupt override: source 0, irq 2 Aug 8 15:57:07 v8 kernel: ioapic0: Routing IRQ 0 -> intpin 2 Aug 8 15:57:07 v8 kernel: MADT: Interrupt override: source 9, irq 9 Aug 8 15:57:07 v8 kernel: ioapic0: intpin 9 trigger: level Aug 8 15:57:07 v8 kernel: ioapic0: intpin 9 polarity: low Aug 8 15:57:07 v8 kernel: ioapic0 irqs 0-23 on motherboard Aug 8 15:57:07 v8 kernel: cpu0 BSP: Aug 8 15:57:07 v8 kernel: ID: 0x00000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Aug 8 15:57:07 v8 kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Aug 8 15:57:07 v8 kernel: timer: 0x000100ef therm: 0x00010000 err: 0x0001000f pcm: 0x00010000 Aug 8 15:57:07 v8 kernel: wlan_amrr: Aug 8 15:57:07 v8 kernel: wlan: <802.11 Link Layer> Aug 8 15:57:07 v8 kernel: random: Aug 8 15:57:07 v8 kernel: nfslock: pseudo-device Aug 8 15:57:07 v8 kernel: io: Aug 8 15:57:07 v8 kernel: kbd: new array size 4 Aug 8 15:57:07 v8 kernel: kbd1 at kbdmux0 Aug 8 15:57:07 v8 kernel: mem: Aug 8 15:57:07 v8 kernel: Pentium Pro MTRR support enabled Aug 8 15:57:07 v8 kernel: null: Aug 8 15:57:07 v8 kernel: hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Aug 8 2009 15:30:20) Aug 8 15:57:07 v8 kernel: npx0: INT 16 interface Aug 8 15:57:07 v8 kernel: acpi0: <021609 RSDT1645> on motherboard Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 Aug 8 15:57:07 v8 kernel: acpi0: [MPSAFE] Aug 8 15:57:07 v8 kernel: acpi0: [ITHREAD] Aug 8 15:57:07 v8 kernel: acpi0: Power Button (fixed) Aug 8 15:57:07 v8 kernel: acpi0: wakeup code va 0xc672f000 pa 0x1000 Aug 8 15:57:07 v8 kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x8000a078 Aug 8 15:57:07 v8 kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Aug 8 15:57:07 v8 kernel: pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=96001022) Aug 8 15:57:07 v8 kernel: pcibios: BIOS version 3.00 Aug 8 15:57:07 v8 kernel: AcpiOsDerivePciId: \_SB_.PCI0.RS78.NB2_ -> bus 0 dev 0 func 0 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: AcpiOsDerivePciId: \_SB_.PCI0.SATA.SACS -> bus 0 dev 17 func 0 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi0: reservation of fee00000, 1000 (3) failed Aug 8 15:57:07 v8 kernel: acpi0: reservation of ffb80000, 80000 (3) failed Aug 8 15:57:07 v8 kernel: acpi0: reservation of fec10000, 20 (3) failed Aug 8 15:57:07 v8 kernel: acpi0: reservation of 0, a0000 (3) failed Aug 8 15:57:07 v8 kernel: acpi0: reservation of 100000, cff00000 (3) failed Aug 8 15:57:07 v8 kernel: ACPI timer: 1/2 1/1 1/2 1/2 1/1 1/1 1/1 1/2 1/2 1/2 -> 10 Aug 8 15:57:07 v8 kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Aug 8 15:57:07 v8 kernel: acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 Aug 8 15:57:07 v8 kernel: pci_link0: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 7 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 7 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pci_link1: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 10 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 10 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pci_link2: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 10 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 10 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pci_link3: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 11 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 11 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pci_link4: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 10 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 10 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pci_link5: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pci_link6: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 11 N 0 4 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 11 N 0 4 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pci_link7: Index IRQ Rtd Ref IRQs Aug 8 15:57:07 v8 kernel: Initial Probe 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: Validation 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: After Disable 0 255 N 0 4 7 10 11 12 14 15 Aug 8 15:57:07 v8 kernel: pcib0: port 0xcf8-0xcff on acpi0 Aug 8 15:57:07 v8 kernel: pci0: on pcib0 Aug 8 15:57:07 v8 kernel: pci0: domain=0, physical bus=0 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1022, dev=0x9600, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=0, func=0 Aug 8 15:57:07 v8 kernel: class=06-00-00, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0006, statreg=0x2230, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1849, dev=0x9602, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=1, func=0 Aug 8 15:57:07 v8 kernel: class=06-04-00, hdrtype=0x01, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0107, statreg=0x0230, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x1a (6500 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1022, dev=0x9609, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=10, func=0 Aug 8 15:57:07 v8 kernel: class=06-04-00, hdrtype=0x01, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=10 Aug 8 15:57:07 v8 kernel: powerspec 3 supports D0 D3 current D0 Aug 8 15:57:07 v8 kernel: MSI supports 1 message Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.10.INTA Aug 8 15:57:07 v8 kernel: pcib0: slot 10 INTA hardwired to IRQ 18 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4390, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=17, func=0 Aug 8 15:57:07 v8 kernel: class=01-01-8f, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0107, statreg=0x0230, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=11 Aug 8 15:57:07 v8 kernel: powerspec 2 supports D0 D3 current D0 Aug 8 15:57:07 v8 kernel: MSI supports 4 messages, 64 bit Aug 8 15:57:07 v8 kernel: map[10]: type I/O Port, range 32, base 0xc000, size 3, enabled Aug 8 15:57:07 v8 kernel: map[14]: type I/O Port, range 32, base 0xb000, size 2, enabled Aug 8 15:57:07 v8 kernel: map[18]: type I/O Port, range 32, base 0xa000, size 3, enabled Aug 8 15:57:07 v8 kernel: map[1c]: type I/O Port, range 32, base 0x9000, size 2, enabled Aug 8 15:57:07 v8 kernel: map[20]: type I/O Port, range 32, base 0x8000, size 4, enabled Aug 8 15:57:07 v8 kernel: map[24]: type Memory, range 32, base 0xfe7ffc00, size 10, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.17.INTA Aug 8 15:57:07 v8 kernel: pcib0: slot 17 INTA hardwired to IRQ 22 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4397, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=18, func=0 Aug 8 15:57:07 v8 kernel: class=0c-03-10, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0102, statreg=0x02a0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=7 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfe7fe000, size 12, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.18.INTA Aug 8 15:57:07 v8 kernel: pcib0: slot 18 INTA hardwired to IRQ 16 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4398, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=18, func=1 Aug 8 15:57:07 v8 kernel: class=0c-03-10, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=7 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfe7fd000, size 12, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.18.INTA Aug 8 15:57:07 v8 kernel: pcib0: slot 18 INTA hardwired to IRQ 16 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4396, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=18, func=2 Aug 8 15:57:07 v8 kernel: class=0c-03-20, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0102, statreg=0x02b0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=b, irq=10 Aug 8 15:57:07 v8 kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfe7ff800, size 8, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.18.INTB Aug 8 15:57:07 v8 kernel: pcib0: slot 18 INTB hardwired to IRQ 17 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4397, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=19, func=0 Aug 8 15:57:07 v8 kernel: class=0c-03-10, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0102, statreg=0x02a0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=10 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfe7fc000, size 12, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.19.INTA Aug 8 15:57:07 v8 kernel: pcib0: slot 19 INTA hardwired to IRQ 18 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4398, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=19, func=1 Aug 8 15:57:07 v8 kernel: class=0c-03-10, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0117, statreg=0x02a0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=10 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfe7fb000, size 12, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.19.INTA Aug 8 15:57:07 v8 kernel: pcib0: slot 19 INTA hardwired to IRQ 18 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4396, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=19, func=2 Aug 8 15:57:07 v8 kernel: class=0c-03-20, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0102, statreg=0x02b0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=b, irq=11 Aug 8 15:57:07 v8 kernel: powerspec 2 supports D0 D1 D2 D3 current D0 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfe7ff400, size 8, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.19.INTB Aug 8 15:57:07 v8 kernel: pcib0: slot 19 INTB hardwired to IRQ 19 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4385, revid=0x3c Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=20, func=0 Aug 8 15:57:07 v8 kernel: class=0c-05-00, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0403, statreg=0xd230, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x439c, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=20, func=1 Aug 8 15:57:07 v8 kernel: class=01-01-8a, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0005, statreg=0x0230, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=255 Aug 8 15:57:07 v8 kernel: MSI supports 2 messages Aug 8 15:57:07 v8 kernel: map[20]: type I/O Port, range 32, base 0xff00, size 4, enabled Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x439d, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=20, func=3 Aug 8 15:57:07 v8 kernel: class=06-01-00, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4384, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=20, func=4 Aug 8 15:57:07 v8 kernel: class=06-04-01, hdrtype=0x01, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0107, statreg=0x02a0, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x40 (1920 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x4399, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=20, func=5 Aug 8 15:57:07 v8 kernel: class=0c-03-10, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0102, statreg=0x02a0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=c, irq=10 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfe7fa000, size 12, enabled Aug 8 15:57:07 v8 kernel: pcib0: matched entry for 0.20.INTC Aug 8 15:57:07 v8 kernel: pcib0: slot 20 INTC hardwired to IRQ 18 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1022, dev=0x1100, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=24, func=0 Aug 8 15:57:07 v8 kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1022, dev=0x1101, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=24, func=1 Aug 8 15:57:07 v8 kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1022, dev=0x1102, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=24, func=2 Aug 8 15:57:07 v8 kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: found-> vendor=0x1022, dev=0x1103, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=0, slot=24, func=3 Aug 8 15:57:07 v8 kernel: class=06-00-00, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: pcib1: at device 1.0 on pci0 Aug 8 15:57:07 v8 kernel: pcib1: domain 0 Aug 8 15:57:07 v8 kernel: pcib1: secondary bus 1 Aug 8 15:57:07 v8 kernel: pcib1: subordinate bus 1 Aug 8 15:57:07 v8 kernel: pcib1: I/O decode 0xd000-0xdfff Aug 8 15:57:07 v8 kernel: pcib1: memory decode 0xfe800000-0xfe9fffff Aug 8 15:57:07 v8 kernel: pcib1: prefetched decode 0xd0000000-0xdfffffff Aug 8 15:57:07 v8 kernel: pci1: on pcib1 Aug 8 15:57:07 v8 kernel: pci1: domain=0, physical bus=1 Aug 8 15:57:07 v8 kernel: found-> vendor=0x1002, dev=0x9610, revid=0x00 Aug 8 15:57:07 v8 kernel: domain=0, bus=1, slot=5, func=0 Aug 8 15:57:07 v8 kernel: class=03-00-00, hdrtype=0x00, mfdev=1 Aug 8 15:57:07 v8 kernel: cmdreg=0x0107, statreg=0x4010, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=10 Aug 8 15:57:07 v8 kernel: powerspec 3 supports D0 D1 D2 D3 current D0 Aug 8 15:57:07 v8 kernel: MSI supports 1 message, 64 bit Aug 8 15:57:07 v8 kernel: map[10]: type Prefetchable Memory, range 32, base 0xd0000000, size 28, enabled Aug 8 15:57:07 v8 kernel: pcib1: requested memory range 0xd0000000-0xdfffffff: good Aug 8 15:57:07 v8 kernel: map[14]: type I/O Port, range 32, base 0xd000, size 8, enabled Aug 8 15:57:07 v8 kernel: pcib1: requested I/O range 0xd000-0xd0ff: in range Aug 8 15:57:07 v8 kernel: map[18]: type Memory, range 32, base 0xfe9f0000, size 16, enabled Aug 8 15:57:07 v8 kernel: pcib1: requested memory range 0xfe9f0000-0xfe9fffff: good Aug 8 15:57:07 v8 kernel: map[24]: type Memory, range 32, base 0xfe800000, size 20, enabled Aug 8 15:57:07 v8 kernel: pcib1: requested memory range 0xfe800000-0xfe8fffff: good Aug 8 15:57:07 v8 kernel: pcib1: matched entry for 1.5.INTA Aug 8 15:57:07 v8 kernel: pcib1: slot 5 INTA hardwired to IRQ 18 Aug 8 15:57:07 v8 kernel: vgapci0: port 0xd000-0xd0ff mem 0xd0000000-0xdfffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1 Aug 8 15:57:07 v8 kernel: pcib2: irq 18 at device 10.0 on pci0 Aug 8 15:57:07 v8 kernel: pcib2: domain 0 Aug 8 15:57:07 v8 kernel: pcib2: secondary bus 2 Aug 8 15:57:07 v8 kernel: pcib2: subordinate bus 2 Aug 8 15:57:07 v8 kernel: pcib2: I/O decode 0xe000-0xefff Aug 8 15:57:07 v8 kernel: pcib2: memory decode 0xfea00000-0xfeafffff Aug 8 15:57:07 v8 kernel: pcib2: prefetched decode 0xfdf00000-0xfdffffff Aug 8 15:57:07 v8 kernel: pci2: on pcib2 Aug 8 15:57:07 v8 kernel: pci2: domain=0, physical bus=2 Aug 8 15:57:07 v8 kernel: found-> vendor=0x10ec, dev=0x8168, revid=0x03 Aug 8 15:57:07 v8 kernel: domain=0, bus=2, slot=0, func=0 Aug 8 15:57:07 v8 kernel: class=02-00-00, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=10 Aug 8 15:57:07 v8 kernel: powerspec 3 supports D0 D1 D2 D3 current D0 Aug 8 15:57:07 v8 kernel: MSI supports 1 message, 64 bit Aug 8 15:57:07 v8 kernel: MSI-X supports 4 messages in map 0x20 Aug 8 15:57:07 v8 kernel: map[10]: type I/O Port, range 32, base 0xe800, size 8, enabled Aug 8 15:57:07 v8 kernel: pcib2: requested I/O range 0xe800-0xe8ff: in range Aug 8 15:57:07 v8 kernel: map[18]: type Prefetchable Memory, range 64, base 0xfdfff000, size 12, enabled Aug 8 15:57:07 v8 kernel: pcib2: requested memory range 0xfdfff000-0xfdffffff: good Aug 8 15:57:07 v8 kernel: map[20]: type Prefetchable Memory, range 64, base 0xfdff8000, size 14, enabled Aug 8 15:57:07 v8 kernel: pcib2: requested memory range 0xfdff8000-0xfdffbfff: good Aug 8 15:57:07 v8 kernel: pcib2: matched entry for 2.0.INTA Aug 8 15:57:07 v8 kernel: pcib2: slot 0 INTA hardwired to IRQ 18 Aug 8 15:57:07 v8 kernel: re0: port 0xe800-0xe8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 18 at device 0.0 on pci2 Aug 8 15:57:07 v8 kernel: re0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xfdfff000 Aug 8 15:57:07 v8 kernel: re0: MSI count : 1 Aug 8 15:57:07 v8 kernel: re0: attempting to allocate 1 MSI vectors (1 supported) Aug 8 15:57:07 v8 kernel: msi: routing MSI IRQ 256 to vector 49 Aug 8 15:57:07 v8 kernel: re0: using IRQ 256 for MSI Aug 8 15:57:07 v8 kernel: re0: Using 1 MSI messages Aug 8 15:57:07 v8 kernel: re0: Chip rev. 0x28000000 Aug 8 15:57:07 v8 kernel: re0: MAC rev. 0x00000000 Aug 8 15:57:07 v8 kernel: miibus0: on re0 Aug 8 15:57:07 v8 kernel: rgephy0: PHY 1 on miibus0 Aug 8 15:57:07 v8 kernel: rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto Aug 8 15:57:07 v8 kernel: re0: bpf attached Aug 8 15:57:07 v8 kernel: re0: Ethernet address: 00:19:66:b7:53:27 Aug 8 15:57:07 v8 kernel: re0: [MPSAFE] Aug 8 15:57:07 v8 kernel: re0: [FILTER] Aug 8 15:57:07 v8 kernel: atapci0: port 0xc000-0xc007,0xb000-0xb003,0xa000-0xa007,0x9000-0x9003,0x8000-0x800f mem 0xfe7ffc00-0xfe7fffff irq 22 at device 17.0 on pci0 Aug 8 15:57:07 v8 kernel: atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x8000 Aug 8 15:57:07 v8 kernel: atapci0: Reserved 0x400 bytes for rid 0x24 type 3 at 0xfe7ffc00 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 22 (PCI IRQ 22) to vector 50 Aug 8 15:57:07 v8 kernel: atapci0: [MPSAFE] Aug 8 15:57:07 v8 kernel: atapci0: [ITHREAD] Aug 8 15:57:07 v8 kernel: atapci0: AHCI Version 01.10 controller with 4 ports detected Aug 8 15:57:07 v8 kernel: ata2: on atapci0 Aug 8 15:57:07 v8 kernel: ata2: SATA connect time=0ms Aug 8 15:57:07 v8 kernel: ata2: SIGNATURE: 00000101 Aug 8 15:57:07 v8 kernel: ata2: ahci_reset devices=0x1 Aug 8 15:57:07 v8 kernel: ata2: [MPSAFE] Aug 8 15:57:07 v8 kernel: ata2: [ITHREAD] Aug 8 15:57:07 v8 kernel: ata3: on atapci0 Aug 8 15:57:07 v8 kernel: ata3: SATA connect time=0ms Aug 8 15:57:07 v8 kernel: ata3: SIGNATURE: 00000101 Aug 8 15:57:07 v8 kernel: ata3: ahci_reset devices=0x1 Aug 8 15:57:07 v8 kernel: ata3: [MPSAFE] Aug 8 15:57:07 v8 kernel: ata3: [ITHREAD] Aug 8 15:57:07 v8 kernel: ata4: on atapci0 Aug 8 15:57:07 v8 kernel: ata4: SATA connect status=00000000 Aug 8 15:57:07 v8 kernel: ata4: ahci_reset devices=0x0 Aug 8 15:57:07 v8 kernel: ata4: [MPSAFE] Aug 8 15:57:07 v8 kernel: ata4: [ITHREAD] Aug 8 15:57:07 v8 kernel: ata5: on atapci0 Aug 8 15:57:07 v8 kernel: ata5: SATA connect status=00000000 Aug 8 15:57:07 v8 kernel: ata5: ahci_reset devices=0x0 Aug 8 15:57:07 v8 kernel: ata5: [MPSAFE] Aug 8 15:57:07 v8 kernel: ata5: [ITHREAD] Aug 8 15:57:07 v8 kernel: ohci0: mem 0xfe7fe000-0xfe7fefff irq 16 at device 18.0 on pci0 Aug 8 15:57:07 v8 kernel: ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fe000 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 16 (PCI IRQ 16) to vector 51 Aug 8 15:57:07 v8 kernel: ohci0: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: ohci0: [ITHREAD] Aug 8 15:57:07 v8 kernel: usb0: OHCI version 1.0, legacy support Aug 8 15:57:07 v8 kernel: usb0: on ohci0 Aug 8 15:57:07 v8 kernel: usb0: USB revision 1.0 Aug 8 15:57:07 v8 kernel: uhub0: on usb0 Aug 8 15:57:07 v8 kernel: uhub0: 3 ports with 3 removable, self powered Aug 8 15:57:07 v8 kernel: ohci1: mem 0xfe7fd000-0xfe7fdfff irq 16 at device 18.1 on pci0 Aug 8 15:57:07 v8 kernel: ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fd000 Aug 8 15:57:07 v8 kernel: ohci1: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: ohci1: [ITHREAD] Aug 8 15:57:07 v8 kernel: usb1: OHCI version 1.0, legacy support Aug 8 15:57:07 v8 kernel: usb1: on ohci1 Aug 8 15:57:07 v8 kernel: usb1: USB revision 1.0 Aug 8 15:57:07 v8 kernel: uhub1: on usb1 Aug 8 15:57:07 v8 kernel: uhub1: 3 ports with 3 removable, self powered Aug 8 15:57:07 v8 kernel: ehci0: mem 0xfe7ff800-0xfe7ff8ff irq 17 at device 18.2 on pci0 Aug 8 15:57:07 v8 kernel: ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe7ff800 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 17 (PCI IRQ 17) to vector 52 Aug 8 15:57:07 v8 kernel: ehci0: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: ehci0: [ITHREAD] Aug 8 15:57:07 v8 kernel: ehci0: Dropped interrupts workaround enabled Aug 8 15:57:07 v8 kernel: usb2: EHCI version 1.0 Aug 8 15:57:07 v8 kernel: usb2: companion controllers, 3 ports each: usb0 usb1 Aug 8 15:57:07 v8 kernel: usb2: on ehci0 Aug 8 15:57:07 v8 kernel: usb2: USB revision 2.0 Aug 8 15:57:07 v8 kernel: uhub2: on usb2 Aug 8 15:57:07 v8 kernel: uhub2: 6 ports with 6 removable, self powered Aug 8 15:57:07 v8 kernel: ohci2: mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.0 on pci0 Aug 8 15:57:07 v8 kernel: ohci2: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fc000 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 18 (PCI IRQ 18) to vector 53 Aug 8 15:57:07 v8 kernel: ohci2: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: ohci2: [ITHREAD] Aug 8 15:57:07 v8 kernel: usb3: OHCI version 1.0, legacy support Aug 8 15:57:07 v8 kernel: usb3: on ohci2 Aug 8 15:57:07 v8 kernel: usb3: USB revision 1.0 Aug 8 15:57:07 v8 kernel: uhub3: on usb3 Aug 8 15:57:07 v8 kernel: uhub3: 3 ports with 3 removable, self powered Aug 8 15:57:07 v8 kernel: ohci3: mem 0xfe7fb000-0xfe7fbfff irq 18 at device 19.1 on pci0 Aug 8 15:57:07 v8 kernel: ohci3: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fb000 Aug 8 15:57:07 v8 kernel: ohci3: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: ohci3: [ITHREAD] Aug 8 15:57:07 v8 kernel: usb4: OHCI version 1.0, legacy support Aug 8 15:57:07 v8 kernel: usb4: on ohci3 Aug 8 15:57:07 v8 kernel: usb4: USB revision 1.0 Aug 8 15:57:07 v8 kernel: uhub4: on usb4 Aug 8 15:57:07 v8 kernel: uhub4: 3 ports with 3 removable, self powered Aug 8 15:57:07 v8 kernel: ehci1: mem 0xfe7ff400-0xfe7ff4ff irq 19 at device 19.2 on pci0 Aug 8 15:57:07 v8 kernel: ehci1: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe7ff400 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 19 (PCI IRQ 19) to vector 54 Aug 8 15:57:07 v8 kernel: ehci1: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: ehci1: [ITHREAD] Aug 8 15:57:07 v8 kernel: ehci1: Dropped interrupts workaround enabled Aug 8 15:57:07 v8 kernel: usb5: EHCI version 1.0 Aug 8 15:57:07 v8 kernel: usb5: companion controllers, 3 ports each: usb3 usb4 Aug 8 15:57:07 v8 kernel: usb5: on ehci1 Aug 8 15:57:07 v8 kernel: usb5: USB revision 2.0 Aug 8 15:57:07 v8 kernel: uhub5: on usb5 Aug 8 15:57:07 v8 kernel: uhub5: 6 ports with 6 removable, self powered Aug 8 15:57:07 v8 kernel: pci0: at device 20.0 (no driver attached) Aug 8 15:57:07 v8 kernel: atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 Aug 8 15:57:07 v8 kernel: atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xff00 Aug 8 15:57:07 v8 kernel: ata0: on atapci1 Aug 8 15:57:07 v8 kernel: atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 Aug 8 15:57:07 v8 kernel: atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 Aug 8 15:57:07 v8 kernel: ata0: reset tp1 mask=03 ostat0=7f ostat1=7f Aug 8 15:57:07 v8 kernel: ata0: stat0=0x7f err=0xff lsb=0xff msb=0xff Aug 8 15:57:07 v8 last message repeated 21 times Aug 8 15:57:07 v8 kernel: ata0: stat1=0x7f err=0xff lsb=0xff msb=0xff Aug 8 15:57:07 v8 kernel: ata0: reset tp2 stat0=ff stat1=ff devices=0x0 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 14 (ISA IRQ 14) to vector 55 Aug 8 15:57:07 v8 kernel: ata0: [MPSAFE] Aug 8 15:57:07 v8 kernel: ata0: [ITHREAD] Aug 8 15:57:07 v8 kernel: isab0: at device 20.3 on pci0 Aug 8 15:57:07 v8 kernel: isa0: on isab0 Aug 8 15:57:07 v8 kernel: pcib3: at device 20.4 on pci0 Aug 8 15:57:07 v8 kernel: pcib3: domain 0 Aug 8 15:57:07 v8 kernel: pcib3: secondary bus 3 Aug 8 15:57:07 v8 kernel: pcib3: subordinate bus 3 Aug 8 15:57:07 v8 kernel: pcib3: I/O decode 0xf000-0xfff Aug 8 15:57:07 v8 kernel: pcib3: memory decode 0xfeb00000-0xfebfffff Aug 8 15:57:07 v8 kernel: pcib3: no prefetched decode Aug 8 15:57:07 v8 kernel: pcib3: Subtractively decoded bridge. Aug 8 15:57:07 v8 kernel: pci3: on pcib3 Aug 8 15:57:07 v8 kernel: pci3: domain=0, physical bus=3 Aug 8 15:57:07 v8 kernel: found-> vendor=0x168c, dev=0x0029, revid=0x01 Aug 8 15:57:07 v8 kernel: domain=0, bus=3, slot=5, func=0 Aug 8 15:57:07 v8 kernel: class=02-80-00, hdrtype=0x00, mfdev=0 Aug 8 15:57:07 v8 kernel: cmdreg=0x0116, statreg=0x02b0, cachelnsz=16 (dwords) Aug 8 15:57:07 v8 kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) Aug 8 15:57:07 v8 kernel: intpin=a, irq=10 Aug 8 15:57:07 v8 kernel: powerspec 2 supports D0 D3 current D0 Aug 8 15:57:07 v8 kernel: map[10]: type Memory, range 32, base 0xfebf0000, size 16, enabled Aug 8 15:57:07 v8 kernel: pcib3: requested memory range 0xfebf0000-0xfebfffff: good Aug 8 15:57:07 v8 kernel: pcib3: matched entry for 3.5.INTA Aug 8 15:57:07 v8 kernel: pcib3: slot 5 INTA hardwired to IRQ 20 Aug 8 15:57:07 v8 kernel: pci3: at device 5.0 (no driver attached) Aug 8 15:57:07 v8 kernel: ohci4: mem 0xfe7fa000-0xfe7fafff irq 18 at device 20.5 on pci0 Aug 8 15:57:07 v8 kernel: ohci4: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe7fa000 Aug 8 15:57:07 v8 kernel: ohci4: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: ohci4: [ITHREAD] Aug 8 15:57:07 v8 kernel: usb6: OHCI version 1.0, legacy support Aug 8 15:57:07 v8 kernel: usb6: on ohci4 Aug 8 15:57:07 v8 kernel: usb6: USB revision 1.0 Aug 8 15:57:07 v8 kernel: uhub6: on usb6 Aug 8 15:57:07 v8 kernel: uhub6: 2 ports with 2 removable, self powered Aug 8 15:57:07 v8 kernel: acpi_button0: on acpi0 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Aug 8 15:57:07 v8 kernel: atkbd0: irq 1 on atkbdc0 Aug 8 15:57:07 v8 kernel: atkbd: the current kbd controller command byte 0065 Aug 8 15:57:07 v8 kernel: atkbd: keyboard ID 0x41ab (2) Aug 8 15:57:07 v8 kernel: kbd0 at atkbd0 Aug 8 15:57:07 v8 kernel: kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 1 (ISA IRQ 1) to vector 56 Aug 8 15:57:07 v8 kernel: atkbd0: [GIANT-LOCKED] Aug 8 15:57:07 v8 kernel: atkbd0: [ITHREAD] Aug 8 15:57:07 v8 kernel: psm0: unable to allocate IRQ Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: psmcpnp0: irq 12 on acpi0 Aug 8 15:57:07 v8 kernel: psm0: current command byte:0065 Aug 8 15:57:07 v8 kernel: psm0: failed to reset the aux device. Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 Aug 8 15:57:07 v8 kernel: fdc0: ic_type 90 part_id 80 Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 6 (ISA IRQ 6) to vector 57 Aug 8 15:57:07 v8 kernel: fdc0: [FILTER] Aug 8 15:57:07 v8 kernel: acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Aug 8 15:57:07 v8 kernel: acpi_hpet0: vend: 0xffff rev: 0xff num: 31 hz: 232831 opts: legacy_route 64-bit Aug 8 15:57:07 v8 kernel: acpi_hpet0: HPET never increments, disabling Aug 8 15:57:07 v8 kernel: device_attach: acpi_hpet0 attach returned 6 Aug 8 15:57:07 v8 kernel: sio0: irq maps: 0x1 0x11 0x1 0x1 Aug 8 15:57:07 v8 kernel: sio0: irq maps: 0x1 0x11 0x1 0x1 Aug 8 15:57:07 v8 kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Aug 8 15:57:07 v8 kernel: sio0: type 16550A Aug 8 15:57:07 v8 kernel: ioapic0: routing intpin 4 (ISA IRQ 4) to vector 58 Aug 8 15:57:07 v8 kernel: sio0: [FILTER] Aug 8 15:57:07 v8 kernel: cpu0: on acpi0 Aug 8 15:57:07 v8 kernel: cpu0: switching to generic Cx mode Aug 8 15:57:07 v8 kernel: acpi_throttle0: on cpu0 Aug 8 15:57:07 v8 kernel: acpi_throttle0: P_CNT from P_BLK 0x810 Aug 8 15:57:07 v8 kernel: powernow0: on cpu0 Aug 8 15:57:07 v8 kernel: cpu1: on acpi0 Aug 8 15:57:07 v8 kernel: powernow1: on cpu1 Aug 8 15:57:07 v8 kernel: acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Aug 8 15:57:07 v8 kernel: acpi_hpet0: vend: 0xffff rev: 0xff num: 31 hz: 232831 opts: legacy_route 64-bit Aug 8 15:57:07 v8 kernel: acpi_hpet0: HPET never increments, disabling Aug 8 15:57:07 v8 kernel: device_attach: acpi_hpet0 attach returned 6 Aug 8 15:57:07 v8 kernel: unknown: status reg test failed ff Aug 8 15:57:07 v8 last message repeated 5 times Aug 8 15:57:07 v8 kernel: ahc_isa_probe 0: ioport 0xc00 alloc failed Aug 8 15:57:07 v8 kernel: ex_isa_identify() Aug 8 15:57:07 v8 kernel: ata: ata0 already exists; skipping it Aug 8 15:57:07 v8 kernel: atkbdc: atkbdc0 already exists; skipping it Aug 8 15:57:07 v8 kernel: fdc: fdc0 already exists; skipping it Aug 8 15:57:07 v8 kernel: sio: sio0 already exists; skipping it Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 203 Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 243 Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 283 Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 2c3 Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 303 Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 343 Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 383 Aug 8 15:57:07 v8 kernel: pnp_identify: Trying Read_Port at 3c3 Aug 8 15:57:07 v8 kernel: PNP Identify complete Aug 8 15:57:07 v8 kernel: sc: sc0 already exists; skipping it Aug 8 15:57:07 v8 kernel: vga: vga0 already exists; skipping it Aug 8 15:57:07 v8 kernel: isa_probe_children: disabling PnP devices Aug 8 15:57:07 v8 kernel: isa_probe_children: probing non-PnP devices Aug 8 15:57:07 v8 kernel: pmtimer0 on isa0 Aug 8 15:57:07 v8 kernel: adv0: not probed (disabled) Aug 8 15:57:07 v8 kernel: aha0: not probed (disabled) Aug 8 15:57:07 v8 kernel: aic0: not probed (disabled) Aug 8 15:57:07 v8 kernel: ata1 failed to probe at port 0x170 irq 15 on isa0 Aug 8 15:57:07 v8 kernel: bt0: not probed (disabled) Aug 8 15:57:07 v8 kernel: cs0: not probed (disabled) Aug 8 15:57:07 v8 kernel: ed0: not probed (disabled) Aug 8 15:57:07 v8 kernel: fe0: not probed (disabled) Aug 8 15:57:07 v8 kernel: ie0: not probed (disabled) Aug 8 15:57:07 v8 kernel: le0: not probed (disabled) Aug 8 15:57:07 v8 kernel: ppc0: parallel port not found. Aug 8 15:57:07 v8 kernel: ppc0: failed to probe at irq 7 on isa0 Aug 8 15:57:07 v8 kernel: sc0: at flags 0x100 on isa0 Aug 8 15:57:07 v8 kernel: sc0: VGA <16 virtual consoles, flags=0x300> Aug 8 15:57:07 v8 kernel: sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) Aug 8 15:57:07 v8 kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Aug 8 15:57:07 v8 kernel: sio1: port may not be enabled Aug 8 15:57:07 v8 kernel: sio1: irq maps: 0x1 0x1 0x1 0x1 Aug 8 15:57:07 v8 kernel: sio1: probe failed test(s): 0 1 2 4 6 7 9 Aug 8 15:57:07 v8 kernel: sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 Aug 8 15:57:07 v8 kernel: sio2: not probed (disabled) Aug 8 15:57:07 v8 kernel: sio3: not probed (disabled) Aug 8 15:57:07 v8 kernel: sn0: not probed (disabled) Aug 8 15:57:07 v8 kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Aug 8 15:57:07 v8 kernel: vt0: not probed (disabled) Aug 8 15:57:07 v8 kernel: isa_probe_children: probing PnP devices Aug 8 15:57:07 v8 kernel: Device configuration finished. Aug 8 15:57:07 v8 kernel: Reducing kern.maxvnodes 214565 -> 100000 Aug 8 15:57:07 v8 kernel: procfs registered Aug 8 15:57:07 v8 kernel: lapic: Divisor 2, Frequency 99780420 hz Aug 8 15:57:07 v8 kernel: Timecounter "TSC" frequency 2594290746 Hz quality -100 Aug 8 15:57:07 v8 kernel: Timecounters tick every 1.000 msec Aug 8 15:57:07 v8 kernel: lo0: bpf attached Aug 8 15:57:07 v8 kernel: hptrr: no controller detected. Aug 8 15:57:07 v8 kernel: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire Aug 8 15:57:07 v8 kernel: ad4: 476940MB at ata2-master SATA300 Aug 8 15:57:07 v8 kernel: ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue Aug 8 15:57:07 v8 kernel: GEOM: new disk ad4 Aug 8 15:57:07 v8 kernel: ad4: Silicon Image check1 failed Aug 8 15:57:07 v8 kernel: ad4: Adaptec check1 failed Aug 8 15:57:07 v8 kernel: ad4: LSI (v3) check1 failed Aug 8 15:57:07 v8 kernel: ad4: LSI (v2) check1 failed Aug 8 15:57:07 v8 kernel: ad4: FreeBSD check1 failed Aug 8 15:57:07 v8 kernel: ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire Aug 8 15:57:07 v8 kernel: ad6: 476940MB at ata3-master SATA300 Aug 8 15:57:07 v8 kernel: ad6: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue Aug 8 15:57:07 v8 kernel: ad6: Silicon Image check1 failed Aug 8 15:57:07 v8 kernel: ad6: Adaptec check1 failed Aug 8 15:57:07 v8 kernel: GEOM: new disk ad6 Aug 8 15:57:07 v8 kernel: ad6: LSI (v3) check1 failed Aug 8 15:57:07 v8 kernel: ad6: LSI (v2) check1 failed Aug 8 15:57:07 v8 kernel: ad6: FreeBSD check1 failed Aug 8 15:57:07 v8 kernel: ATA PseudoRAID loaded Aug 8 15:57:07 v8 kernel: SMP: AP CPU #1 Launched! Aug 8 15:57:07 v8 kernel: cpu1 AP: Aug 8 15:57:07 v8 kernel: ID: 0x01000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff Aug 8 15:57:07 v8 kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff Aug 8 15:57:07 v8 kernel: timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning ISA IRQ 1 to local APIC 0 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning ISA IRQ 4 to local APIC 1 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning ISA IRQ 6 to local APIC 0 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning ISA IRQ 9 to local APIC 1 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning ISA IRQ 14 to local APIC 0 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning PCI IRQ 16 to local APIC 1 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning PCI IRQ 17 to local APIC 0 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning PCI IRQ 18 to local APIC 1 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning PCI IRQ 19 to local APIC 0 Aug 8 15:57:07 v8 kernel: ioapic0: Assigning PCI IRQ 22 to local APIC 1 Aug 8 15:57:07 v8 kernel: msi: Assigning MSI IRQ 256 to local APIC 0 Aug 8 15:57:07 v8 kernel: Trying to mount root from ufs:/dev/ad4s1a Aug 8 15:57:07 v8 kernel: start_init: trying /sbin/init Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x5a Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x001 (8), val 0x7 Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0x30 Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x001 (8) Aug 8 15:57:07 v8 kernel: acpi: bad read from port 0x000 (8) Aug 8 15:57:07 v8 kernel: acpi: bad write to port 0x000 (8), val 0xa5 Aug 8 15:57:07 v8 kernel: Linux ELF exec handler installed Aug 8 15:57:07 v8 kernel: linprocfs registered Aug 8 15:57:07 v8 savecore: no dumps found Aug 8 15:57:08 v8 kernel: re0: link state changed to UP Aug 8 15:57:17 v8 ntpd[595]: ntpd 4.2.4p5-a Sat Jun 20 12:47:53 CEST 2009 (1) Aug 8 15:57:29 v8 postfix/postfix-script[908]: fatal: the Postfix mail system is already running Aug 8 15:58:33 v8 su: bjb to toor on /dev/ttyp1 Aug 8 16:00:00 v8 newsyslog[1063]: logfile turned over due to size>100K From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 9 11:25:55 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B899B106566B; Sun, 9 Aug 2009 11:25:55 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from sakura.ccs.furiru.org (sakura.ccs.furiru.org [IPv6:2001:2f0:104:8060::1]) by mx1.freebsd.org (Postfix) with ESMTP id 657028FC15; Sun, 9 Aug 2009 11:25:55 +0000 (UTC) Received: from localhost (authenticated bits=0) by sakura.ccs.furiru.org (unknown) with ESMTP id n79BPosG010117; Sun, 9 Aug 2009 20:25:53 +0900 (JST) (envelope-from nyan@jp.FreeBSD.org) Date: Sun, 09 Aug 2009 20:25:49 +0900 (JST) Message-Id: <20090809.202549.27838630.nyan@jp.FreeBSD.org> To: mav@freebsd.org From: Takahashi Yoshihiro In-Reply-To: <4A7DF076.4070203@FreeBSD.org> References: <4A7DF076.4070203@FreeBSD.org> X-Mailer: Mew version 6.2 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 11:25:56 -0000 In article <4A7DF076.4070203@FreeBSD.org> Alexander Motin writes: > While preparing wrapping ATA(4) low-level drivers code into CAM SIM, I > would like to remove CHS addressing support to make code cleaner. CHS > addressing is officially declared obsoleted and replaced by LBA. Since > ATA/ATAPI-6 specification (October 2001) it is even no longer > documented. > > Have anybody seen ATA drive without LBA support in last years? > Any other objections against removing it? PC98 uses CHS addressing because the internal interface works for very old HDD only, so I hope it remains if possible. But if you need a lot of works for CHS support, I agree to remove it. --- TAKAHASHI Yoshihiro From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 9 12:58:33 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FBD5106566B for ; Sun, 9 Aug 2009 12:58:33 +0000 (UTC) (envelope-from alireza.torabi@gmail.com) Received: from mail-ew0-f206.google.com (mail-ew0-f206.google.com [209.85.219.206]) by mx1.freebsd.org (Postfix) with ESMTP id DA7158FC16 for ; Sun, 9 Aug 2009 12:58:32 +0000 (UTC) Received: by ewy2 with SMTP id 2so2500856ewy.43 for ; Sun, 09 Aug 2009 05:58:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=WgFtMlOhPkFn6ml4M6qLlRuOCTm7lcyiBIuLD1ZROTY=; b=GT4OdtQN4nPxcVpqVL6/ARPCe3cwTLrMRu6wdGpUTKHHNV4xO9ulG+oRrusZ/yLDkz g+FlgVMM44lZHvD237eMiwR3U2vlYpdR3rn4q9ulnjDKZwMULfx53bjHmLbGyaOym+kF Wj1WHn3RNBZUNzbUXXrnhliMKCD0YRJAIZj8I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=VlA8xuqz0iE58lgsyK71Y6FhqIrKQ7ww9IsiKmrlOu+Lgehpii4Qx6+TgPPmQ/au8I i/wIaa7TEJry+GomTu89OH0zD2KMTGtP2ExIc/WyMaecv6J2w9BjPy09gbhRGUuyT5wO +vzPNxuXRCmaM0EZAhDEoL6Dh2tugWxhsgJMM= MIME-Version: 1.0 Received: by 10.216.93.141 with SMTP id l13mr621386wef.67.1249821492595; Sun, 09 Aug 2009 05:38:12 -0700 (PDT) Date: Sun, 9 Aug 2009 13:38:12 +0100 Message-ID: From: Alireza Torabi To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: 8. Current Intel 5100 AGN wifi X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 12:58:33 -0000 I was hoping 8 and iwn would do tried for Intel 5100 AGN wifi, however not true. Anyone can shed any light on this and where the development is as regard to support the above. Many thanks Alireza From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 9 13:47:25 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E95B106566B; Sun, 9 Aug 2009 13:47:25 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3618FC4B; Sun, 9 Aug 2009 13:47:25 +0000 (UTC) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 243531CD18; Sun, 9 Aug 2009 15:47:24 +0200 (CEST) Date: Sun, 9 Aug 2009 15:47:24 +0200 From: Ed Schouten To: Takahashi Yoshihiro Message-ID: <20090809134724.GX1292@hoeg.nl> References: <4A7DF076.4070203@FreeBSD.org> <20090809.202549.27838630.nyan@jp.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82NP6SxOLIStdcnZ" Content-Disposition: inline In-Reply-To: <20090809.202549.27838630.nyan@jp.FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: mav@freebsd.org, freebsd-hardware@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 13:47:26 -0000 --82NP6SxOLIStdcnZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Takahashi Yoshihiro wrote: > In article <4A7DF076.4070203@FreeBSD.org> > Alexander Motin writes: >=20 > > While preparing wrapping ATA(4) low-level drivers code into CAM SIM, I > > would like to remove CHS addressing support to make code cleaner. CHS > > addressing is officially declared obsoleted and replaced by LBA. Since > > ATA/ATAPI-6 specification (October 2001) it is even no longer > > documented. > >=20 > > Have anybody seen ATA drive without LBA support in last years? > > Any other objections against removing it? >=20 > PC98 uses CHS addressing because the internal interface works for very > old HDD only, so I hope it remains if possible. But if you need a lot > of works for CHS support, I agree to remove it. Wouldn't it be possible to keep the old ATA code in the tree for users who want to use stuff like this? --=20 Ed Schouten WWW: http://80386.nl/ --82NP6SxOLIStdcnZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkp+02sACgkQ52SDGA2eCwX+WgCfUg1hvFE15FXG3FU/VQz+khir ks4An2iOA1oAzUKd2O+oGONmX0hGacCM =xRVr -----END PGP SIGNATURE----- --82NP6SxOLIStdcnZ-- From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 9 14:15:52 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 822E8106566B; Sun, 9 Aug 2009 14:15:52 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id D0B048FC19; Sun, 9 Aug 2009 14:15:51 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 251066089; Sun, 09 Aug 2009 17:15:48 +0300 Message-ID: <4A7ED9DF.1080007@FreeBSD.org> Date: Sun, 09 Aug 2009 17:14:55 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: Ed Schouten References: <4A7DF076.4070203@FreeBSD.org> <20090809.202549.27838630.nyan@jp.FreeBSD.org> <20090809134724.GX1292@hoeg.nl> In-Reply-To: <20090809134724.GX1292@hoeg.nl> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org, Takahashi Yoshihiro , freebsd-arch@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 14:15:52 -0000 Ed Schouten wrote: > * Takahashi Yoshihiro wrote: >> In article <4A7DF076.4070203@FreeBSD.org> >> Alexander Motin writes: >>> While preparing wrapping ATA(4) low-level drivers code into CAM SIM, I >>> would like to remove CHS addressing support to make code cleaner. CHS >>> addressing is officially declared obsoleted and replaced by LBA. Since >>> ATA/ATAPI-6 specification (October 2001) it is even no longer >>> documented. >>> >>> Have anybody seen ATA drive without LBA support in last years? >>> Any other objections against removing it? >> PC98 uses CHS addressing because the internal interface works for very >> old HDD only, so I hope it remains if possible. But if you need a lot >> of works for CHS support, I agree to remove it. > > Wouldn't it be possible to keep the old ATA code in the tree for users > who want to use stuff like this? I am going to make it switchable via kernel option, until new code completely settle. It should be possible to keep CHS support in this legacy mode. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 9 20:48:39 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0630106564A for ; Sun, 9 Aug 2009 20:48:39 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id CA3108FC08 for ; Sun, 9 Aug 2009 20:48:39 +0000 (UTC) Received: from Macintosh-4.local ([10.0.0.198]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n79KHUkE055420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Aug 2009 13:17:31 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <4A7F2EDA.3070506@freebsd.org> Date: Sun, 09 Aug 2009 13:17:30 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Bjarne References: <4A7E8ECD.8010208@darco.dk> In-Reply-To: <4A7E8ECD.8010208@darco.dk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-DCC-x.dcc-servers-Metrics: ebb.errno.com; whitelist Cc: freebsd-hardware@freebsd.org Subject: Re: dwa-547 - atheros chip not recognized X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 20:48:40 -0000 Bjarne wrote: > Sorry if this comes trough twice.. > > > Just installed a d-link dwa-547 in my server, but the ath driver does not recognize it. > > uname -a : > FreeBSD v8.blichsoft.dk 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat Aug 8 15:30:35 CEST 2009 > toor@machine:/usr/obj/usr/src-8aug2009/sys/V8 i386 > cvsup from 7-aug-2009 > > pciconf -lv : > none1@pci0:3:5:0: class=0x028000 card=0x3a781186 chip=0x0029168c rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > class = network > > options AH_SUPPORT_AR5416 is set in the kernel config > > Good ideas are welcome. I am stuck on this one. In the manual for ath(4) it say all chips are > supported, except AR5005VL, and I have seen other references to people using this particular card. I > read it is a Atheros AR5416 chipset. device id 0x29 is a 9280: #define AR9280_DEVID_PCI 0x0029 /* AR9280 PCI Merlin */ (from ath/ath_hal/ah_devid.h). Definitely works in HEAD. As to supporting all cards the main chip not supported in HEAD at the moment is the 9285. I've been waiting for someone to send me one for >6 months and cannot add support w/o a device. Of course others can do the work too; I'm just scraping the crap out of the linux driver. Sam From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 09:32:45 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40BB6106566B; Mon, 10 Aug 2009 09:32:45 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 0BAB48FC21; Mon, 10 Aug 2009 09:32:43 +0000 (UTC) Received: from park.js.berklix.net (p549A4FFE.dip.t-dialin.net [84.154.79.254]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id n7A92dfM071047; Mon, 10 Aug 2009 09:02:41 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id n7A91xgO075873; Mon, 10 Aug 2009 11:01:59 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n7A94BAB044505; Mon, 10 Aug 2009 11:04:16 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200908100904.n7A94BAB044505@fire.js.berklix.net> To: Alexander Motin From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 09 Aug 2009 00:39:02 +0300." <4A7DF076.4070203@FreeBSD.org> Date: Mon, 10 Aug 2009 11:04:11 +0200 Sender: jhs@berklix.com Cc: freebsd-arch@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 09:32:45 -0000 > Have anybody seen ATA drive without LBA support in last years? Yes > Any other objections against removing it? Yes object sorry. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 09:43:02 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D85391065675; Mon, 10 Aug 2009 09:43:02 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2CF968FC43; Mon, 10 Aug 2009 09:43:01 +0000 (UTC) Received: from orphanage.alkar.net (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPA id 251128436; Mon, 10 Aug 2009 12:42:58 +0300 Message-ID: <4A7FEBA2.5090106@FreeBSD.org> Date: Mon, 10 Aug 2009 12:42:58 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.22 (X11/20090805) MIME-Version: 1.0 To: "Julian H. Stacey" References: <200908100904.n7A94BAB044505@fire.js.berklix.net> In-Reply-To: <200908100904.n7A94BAB044505@fire.js.berklix.net> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 09:43:03 -0000 Julian H. Stacey wrote: >> Have anybody seen ATA drive without LBA support in last years? > Yes What it is? Some ancient HDD or flash card? -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 16:38:33 2009 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AE341065674; Mon, 10 Aug 2009 16:38:33 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 9BFE78FC33; Mon, 10 Aug 2009 16:38:32 +0000 (UTC) Received: from park.js.berklix.net (p549A30CD.dip.t-dialin.net [84.154.48.205]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id n7AGcuup078141; Mon, 10 Aug 2009 16:38:57 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id n7AGcL4a080340; Mon, 10 Aug 2009 18:38:21 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n7AGeYH0054650; Mon, 10 Aug 2009 18:40:39 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200908101640.n7AGeYH0054650@fire.js.berklix.net> To: Alexander Motin From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 10 Aug 2009 12:42:58 +0300." <4A7FEBA2.5090106@FreeBSD.org> Date: Mon, 10 Aug 2009 18:40:34 +0200 Sender: jhs@berklix.com Cc: freebsd-hardware@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 16:38:33 -0000 Hi Alexander, > Julian H. Stacey wrote: > >> Have anybody seen ATA drive without LBA support in last years? > > Yes > What it is? Some ancient HDD or flash card? Sorry my first reply was short, a holding reply, ( A server died, & 2nd reserve needed time, still does ) I run 20+ assorted hosts from 4.11 to 7.2 Uni & Dual proc, i386 (real 386!) to 686 & amd64, so I guess I'm A) Pretty vulnerable to legacy scare. B) A litmus tesst for a wider community of others, some with older kit, not on lists or with bleeding edge latest hardware, but will get hit when stuff eg HCS gets declared legacy=dumped. (hardware@ & arch@ are more likely mostly high enders, lower percentage of legacy hardware users I guess) If I have to pull the lid on 20/25 hosts, to check disk sticky labels, I will if I must, but could you please reccomend people syntax to run on 4 5 6 7 RELEASES to check if a host is susceptible ? (Yes I know 4 is declares dead, but I still have lots of hosts with it & I suspect quite a lot of others do, be nice to know if any of those boxes are doomed to only upgarde to 7 not 8 ) BTW My configs & dmesg extract: http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/jhs/sys/i386/conf/HOLZ The genuine 386 host uses config name MINI. The config name SCAN represents a class of scanners with embedded FreeBSD inside that a bunch of people have http://berklix.com/scanjet/ I will turn on more verbose boot to increase http://berklix.com/scanjet/dmesg/4.11/ from its too minimal current ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 17:44:12 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56FC71065678; Mon, 10 Aug 2009 17:44:12 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id A91988FC16; Mon, 10 Aug 2009 17:44:11 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 251187247; Mon, 10 Aug 2009 20:44:08 +0300 Message-ID: <4A805C2E.8020300@FreeBSD.org> Date: Mon, 10 Aug 2009 20:43:10 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: "Julian H. Stacey" References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> In-Reply-To: <200908101640.n7AGeYH0054650@fire.js.berklix.net> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 17:44:12 -0000 Julian H. Stacey wrote: >> Julian H. Stacey wrote: >>>> Have anybody seen ATA drive without LBA support in last years? >>> Yes >> What it is? Some ancient HDD or flash card? > > I run 20+ assorted hosts from 4.11 to 7.2 Uni & Dual proc, i386 (real 386!) > to 686 & amd64, so I guess I'm > A) Pretty vulnerable to legacy scare. > B) A litmus tesst for a wider community of others, some with older kit, > not on lists or with bleeding edge latest hardware, but will > get hit when stuff eg HCS gets declared legacy=dumped. > (hardware@ & arch@ are more likely mostly high enders, > lower percentage of legacy hardware users I guess) Are you administering computer hardware museum? ;) I have tested all drives I have and found none requiring CHS support. Even most ancient 850MB HDD and 16MB CompactFlash card I have support LBA. I have doubts that something even older that this is still working in production and require system there to be upgraded to 8.x. > If I have to pull the lid on 20/25 hosts, to check disk sticky > labels, I will if I must, but could you please reccomend people > syntax to run on 4 5 6 7 RELEASES to check if a host is susceptible ? > (Yes I know 4 is declares dead, but I still have lots of > hosts with it & I suspect quite a lot of others do, > be nice to know if any of those boxes are doomed to only > upgarde to 7 not 8 ) `atacontrol cap adX` can show you if LBA is supported. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 18:52:43 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF95A106566B; Mon, 10 Aug 2009 18:52:43 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 44A818FC16; Mon, 10 Aug 2009 18:52:42 +0000 (UTC) Received: from park.js.berklix.net (p549A30CD.dip.t-dialin.net [84.154.48.205]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id n7AIr7FR080193; Mon, 10 Aug 2009 18:53:08 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id n7AIqXTb081324; Mon, 10 Aug 2009 20:52:33 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n7AIseFv056967; Mon, 10 Aug 2009 20:54:45 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200908101854.n7AIseFv056967@fire.js.berklix.net> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 10 Aug 2009 20:38:16 +0200." <86eirjbjl3.fsf@ds4.des.no> Date: Mon, 10 Aug 2009 20:54:40 +0200 Sender: jhs@berklix.com Cc: Alexander Motin , freebsd-hardware@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 18:52:44 -0000 > From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= wrote: > "Julian H. Stacey" writes: > > Alexander Motin writes: > > > Have anybody seen ATA drive without LBA support in last years? > > Yes > > Have you really, or did you just assume that "old" means "no LBA"? Yes, I just assumed. > CHS doesn't scale past > 504 MB, so any ATA disk larger than that must peforce support LBA. Ah! If so, then no problem here, Thanks Dag-Erling :-) Alexander Motin wrote: > `atacontrol cap adX` can show you if LBA is supported. Thanks Alexander, I will check that tomorrow on every host I have. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 18:53:34 2009 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CE021065679 for ; Mon, 10 Aug 2009 18:53:34 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 29F0E8FC3A for ; Mon, 10 Aug 2009 18:53:33 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 9428A6D418; Mon, 10 Aug 2009 18:38:16 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 5EA75844CC; Mon, 10 Aug 2009 20:38:16 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Julian H. Stacey" References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> Date: Mon, 10 Aug 2009 20:38:16 +0200 In-Reply-To: <200908101640.n7AGeYH0054650@fire.js.berklix.net> (Julian H. Stacey's message of "Mon, 10 Aug 2009 18:40:34 +0200") Message-ID: <86eirjbjl3.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Alexander Motin , freebsd-arch@FreeBSD.org, freebsd-hardware@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 18:53:34 -0000 "Julian H. Stacey" writes: > Alexander Motin writes: > > Have anybody seen ATA drive without LBA support in last years? > Yes Have you really, or did you just assume that "old" means "no LBA"? > I run 20+ assorted hosts from 4.11 to 7.2 Uni & Dual proc, i386 (real 386= !) > to 686 & amd64 so I guess I'm=20 > A) Pretty vulnerable to legacy scare. > B) A litmus tesst for a wider community of others, some with older kit= ,=20 > not on lists or with bleeding edge latest hardware, but will=20 > get hit when stuff eg HCS gets declared legacy=3Ddumped. Do you seriously intend to run FreeBSD 9 on kit that is too old to support LBA? We're talking early nineties here. CHS doesn't scale past 504 MB, so any ATA disk larger than that must peforce support LBA. I bought my first 1 GB drive (Connor CFP1080) in 1995. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 18:57:27 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26C8A106566C; Mon, 10 Aug 2009 18:57:27 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id BF5718FC16; Mon, 10 Aug 2009 18:57:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n7AIs3EW097288; Mon, 10 Aug 2009 12:54:03 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 10 Aug 2009 12:54:03 -0600 (MDT) Message-Id: <20090810.125403.74653324.imp@bsdimp.com> To: des@des.no From: Warner Losh In-Reply-To: <86eirjbjl3.fsf@ds4.des.no> References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> <86eirjbjl3.fsf@ds4.des.no> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: jhs@berklix.com, freebsd-hardware@freebsd.org, mav@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 18:57:27 -0000 From: Dag-Erling Sm=F8rgrav Subject: Re: Do we still need ATA disk CHS addressing? Date: Mon, 10 Aug 2009 20:38:16 +0200 > "Julian H. Stacey" writes: > > Alexander Motin writes: > > > Have anybody seen ATA drive without LBA support in last years? > > Yes > = > Have you really, or did you just assume that "old" means "no LBA"? > = > > I run 20+ assorted hosts from 4.11 to 7.2 Uni & Dual proc, i386 (re= al 386!) > > to 686 & amd64 so I guess I'm = > > A) Pretty vulnerable to legacy scare. > > B) A litmus tesst for a wider community of others, some with old= er kit, = > > not on lists or with bleeding edge latest hardware, but will = > > get hit when stuff eg HCS gets declared legacy=3Ddumped. > = > Do you seriously intend to run FreeBSD 9 on kit that is too old to > support LBA? We're talking early nineties here. CHS doesn't scale p= ast > 504 MB, so any ATA disk larger than that must peforce support LBA. I= > bought my first 1 GB drive (Connor CFP1080) in 1995. Is that also true in the pc98 realm? There's a number of weird combinations there which use CHS addressing, but that's kinda forced onto it by weird pc98 disk label format. I don't know if this is required, and older stuff just won't work or not, but I do know that there be dragons there. I know, at the very least, that the system requires that the CHS geometry reported by the drive be faithfully preserved. It is something we should ask nyan-san about at the very least... As for the 'are you seriously going to run FreeBSD 9 on them' argument, there's a rather large number of systems that people said would be too slow to run FreeBSD 7 or 8, yet they are running them better than anticipated. They said that about many of the same systems that Julian is running today. My question, and maybe I missed this earlier in the thread, is what's the benefit to removing this support? How much code is saved? Having said all that, I think it is OK, but I'd definitely poll the pc98 guys first... Just to make sure they don't need it and re-fork the ata driver to get it :) Warner From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 19:20:04 2009 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EBB710656C6 for ; Mon, 10 Aug 2009 19:20:04 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id CD9A78FC35 for ; Mon, 10 Aug 2009 19:20:03 +0000 (UTC) Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:61557 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Maa97-00077C-9Q for freebsd-hardware@FreeBSD.org; Mon, 10 Aug 2009 21:03:04 +0200 Received: (qmail 63177 invoked from network); 10 Aug 2009 21:02:58 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 10 Aug 2009 21:02:58 +0200 Received: (qmail 33871 invoked by uid 1001); 10 Aug 2009 21:02:58 +0200 Date: Mon, 10 Aug 2009 21:02:58 +0200 From: Erik Trulsson To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20090810190258.GA25641@owl.midgard.homeip.net> References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> <86eirjbjl3.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <86eirjbjl3.fsf@ds4.des.no> User-Agent: Mutt/1.5.20 (2009-06-14) X-Originating-IP: 83.255.48.78 X-Scan-Result: No virus found in message 1Maa97-00077C-9Q. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1Maa97-00077C-9Q 80298c5fb6d2928d8ffb58495b90f2a5 Cc: "Julian H. Stacey" , freebsd-hardware@FreeBSD.org, Alexander Motin , freebsd-arch@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 19:20:05 -0000 On Mon, Aug 10, 2009 at 08:38:16PM +0200, Dag-Erling Sm=F8rgrav wrote: > "Julian H. Stacey" writes: > > Alexander Motin writes: > > > Have anybody seen ATA drive without LBA support in last years? > > Yes >=20 > Have you really, or did you just assume that "old" means "no LBA"? >=20 > > I run 20+ assorted hosts from 4.11 to 7.2 Uni & Dual proc, i386 (real 3= 86!) > > to 686 & amd64 so I guess I'm=20 > > A) Pretty vulnerable to legacy scare. > > B) A litmus tesst for a wider community of others, some with older k= it,=20 > > not on lists or with bleeding edge latest hardware, but will=20 > > get hit when stuff eg HCS gets declared legacy=3Ddumped. >=20 > Do you seriously intend to run FreeBSD 9 on kit that is too old to > support LBA? We're talking early nineties here. CHS doesn't scale past > 504 MB, so any ATA disk larger than that must peforce support LBA. I > bought my first 1 GB drive (Connor CFP1080) in 1995. Actually I believe even the very first version of the ATA standard (long before support for LBA or any other modern features was added) could handle larger disks than 504MiB. I think the original limit of ATA was 2.1 GB.=20 The 504MiB limit was actually the intersection between the limits of the PC BIOS and the limits of the ATA standard. (ATA and the BIOS had different number of bits used to indicate each of cylinder, head and sector. When you took the lower number of bits for each you ended up with the 504MiB limit.) --=20 Erik Trulsson ertr1013@student.uu.se From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 19:59:23 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C66161065693; Mon, 10 Aug 2009 19:59:23 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 1F7F28FC25; Mon, 10 Aug 2009 19:59:22 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 251192793; Mon, 10 Aug 2009 22:59:19 +0300 Message-ID: <4A807BDD.6040709@FreeBSD.org> Date: Mon, 10 Aug 2009 22:58:21 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: Warner Losh References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> <86eirjbjl3.fsf@ds4.des.no> <20090810.125403.74653324.imp@bsdimp.com> In-Reply-To: <20090810.125403.74653324.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: des@des.no, jhs@berklix.com, freebsd-hardware@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 19:59:27 -0000 Warner Losh wrote: > My question, and maybe I missed this earlier in the thread, is what's > the benefit to removing this support? How much code is saved? It is not about code size, but about code structurization. ATA(4) has too much cross-level relations, making it cryptic. I am trying to unroll some of them to simplify code. > Having said all that, I think it is OK, but I'd definitely poll the > pc98 guys first... Just to make sure they don't need it and re-fork > the ata driver to get it :) GEOM has no terms of cylinders/heads/sectors, in fact it works only with LBA. CHS translation is only needed for drives, that have no native LBA support. It is not about disk partitioning or label format. It is just a method to linearize nonlinear address space of ancient drives. For last 10 years, since drives lost their classic geometry, drives are doing this translation on firmware level. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 22:27:19 2009 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE7F1106564A; Mon, 10 Aug 2009 22:27:19 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6AE4C8FC16; Mon, 10 Aug 2009 22:27:19 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n7AMNT4S003113; Mon, 10 Aug 2009 16:23:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 10 Aug 2009 16:24:24 -0600 (MDT) Message-Id: <20090810.162424.846948847.imp@bsdimp.com> To: mav@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <4A807BDD.6040709@FreeBSD.org> References: <86eirjbjl3.fsf@ds4.des.no> <20090810.125403.74653324.imp@bsdimp.com> <4A807BDD.6040709@FreeBSD.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: nyan@FreeBSD.org, freebsd-hardware@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 22:27:20 -0000 In message: <4A807BDD.6040709@FreeBSD.org> Alexander Motin writes: : Warner Losh wrote: : > My question, and maybe I missed this earlier in the thread, is what's : > the benefit to removing this support? How much code is saved? : : It is not about code size, but about code structurization. ATA(4) has : too much cross-level relations, making it cryptic. I am trying to unroll : some of them to simplify code. Can you explain a bit more here... How pervasive is it, etc... I'm not saying this is a bad change, but I think people wishing to remove stuff should at least have a good result that's expected... : > Having said all that, I think it is OK, but I'd definitely poll the : > pc98 guys first... Just to make sure they don't need it and re-fork : > the ata driver to get it :) : : GEOM has no terms of cylinders/heads/sectors, in fact it works only with : LBA. CHS translation is only needed for drives, that have no native LBA : support. It is not about disk partitioning or label format. It is just a : method to linearize nonlinear address space of ancient drives. For last : 10 years, since drives lost their classic geometry, drives are doing : this translation on firmware level. GEOM does have terms of CHS when it reports the classic geometry of the device. That can't be lost, or pc98 partitioning breaks. And the geometry reported must be massaged too, but that's a different issue. The disk requests can be LBA, since the driver is responsible for changing that anyway... I don't think that there's any supported pc98 hardware that would break, but I'm not 100% sure... There's also some oddities at the lowest levels for pc98 controllers, but I don't think this change would affect that. However, like I said, ask the pc98 guys for sure. I've cc'd nyan@, since he can answer the question: "What breaks in pc98 if we lose support for CHS-based disk I/O?" Warner From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 10 23:25:11 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70B72106566B for ; Mon, 10 Aug 2009 23:25:11 +0000 (UTC) (envelope-from frank@undermydesk.org) Received: from amazone.undermydesk.org (amazone.undermydesk.org [213.211.198.100]) by mx1.freebsd.org (Postfix) with ESMTP id 2D0758FC25 for ; Mon, 10 Aug 2009 23:25:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by amazone.undermydesk.org (Postfix) with ESMTP id 9514D5D7A; Tue, 11 Aug 2009 01:24:31 +0200 (CEST) Received: from amazone.undermydesk.org ([213.211.198.100]) by localhost (amazone.undermydesk.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O20oVwdEK6bH; Tue, 11 Aug 2009 01:24:23 +0200 (CEST) Received: from [192.168.0.74] (p4FD5C52D.dip.t-dialin.net [79.213.197.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by amazone.undermydesk.org (Postfix) with ESMTPSA id EAC685D69; Tue, 11 Aug 2009 01:24:22 +0200 (CEST) Message-ID: <4A80AC41.8050003@undermydesk.org> Date: Tue, 11 Aug 2009 01:24:49 +0200 From: Frank Reppin User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4A78C0B5.8080808@undermydesk.org> <436c7eda0908050820g5a610a9dk6b1b1cf20afe2be8@mail.gmail.com> In-Reply-To: <436c7eda0908050820g5a610a9dk6b1b1cf20afe2be8@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jonas Lund Subject: Re: [if_re.c] INTEL mini/itx DE945GSEJT X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 23:25:11 -0000 Hi all and hi Jonas! Jonas Lund wrote: > If you've just purchased a new board i think you could try it out as > you install it. Apart from the mentioned things boards usually > contains the same chipsets as other boards so chances are it'll work. > And if not directly then under some compat mode (Altho could be with > reduced speed) > > And if realtek does provide source for their drivers i'd prolly not be > too worried. The shitties drivers i've used was some crap produced by > some random chineese chip-shop that had delay(10000) or something > alike it inside kernel-code (That's right.. it waited 10 seconds in > kernel for no apperant reason!) but the code was functional with this > removed. > > 2009/8/5 Frank Reppin : >> Hi all, >> >> just purchased the above mentioned board: >> >> http://www.intel.com/products/desktop/motherboards/D945GSEJT/D945GSEJT-overview.htm Thankyou so far... and thankyou to if_re.c maintainer(s)... the mainboard in question is indeed supported by FreeBSD' if_re.c in at least -CURRENT (I've performed an initial install using the latest [2009-06] current snapshot ISO and I've later [2009-08-10... late evening] upgraded to 8.2 beta. coretemp (4) seems to also work as intended as well as powerd without any flaws... at a first glance. Cheers, frank -- http://www.undermydesk.org From owner-freebsd-hardware@FreeBSD.ORG Tue Aug 11 07:35:13 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12E07106566C; Tue, 11 Aug 2009 07:35:13 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 28A4F8FC20; Tue, 11 Aug 2009 07:35:11 +0000 (UTC) Received: from orphanage.alkar.net (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPA id 251229963; Tue, 11 Aug 2009 10:35:08 +0300 Message-ID: <4A811F2B.7050402@FreeBSD.org> Date: Tue, 11 Aug 2009 10:35:07 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.22 (X11/20090805) MIME-Version: 1.0 To: "M. Warner Losh" References: <86eirjbjl3.fsf@ds4.des.no> <20090810.125403.74653324.imp@bsdimp.com> <4A807BDD.6040709@FreeBSD.org> <20090810.162424.846948847.imp@bsdimp.com> In-Reply-To: <20090810.162424.846948847.imp@bsdimp.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: nyan@FreeBSD.org, freebsd-hardware@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 07:35:14 -0000 M. Warner Losh wrote: > In message: <4A807BDD.6040709@FreeBSD.org> > Alexander Motin writes: > : Warner Losh wrote: > : > My question, and maybe I missed this earlier in the thread, is what's > : > the benefit to removing this support? How much code is saved? > : > : It is not about code size, but about code structurization. ATA(4) has > : too much cross-level relations, making it cryptic. I am trying to unroll > : some of them to simplify code. > > Can you explain a bit more here... How pervasive is it, etc... I'm > not saying this is a bad change, but I think people wishing to remove > stuff should at least have a good result that's expected... Do you really wish to touch it? Fine... CHS translation is now done on ATA controller drivers level. To work properly it needs data from drive IDENTIFY structure fetched from drive and stored on higher level. To wrap legacy ATA into CAM SIM I need to break that dependency either with dropping this functionality or reimplementing it on higher level. I would prefer first. > : > Having said all that, I think it is OK, but I'd definitely poll the > : > pc98 guys first... Just to make sure they don't need it and re-fork > : > the ata driver to get it :) > : > : GEOM has no terms of cylinders/heads/sectors, in fact it works only with > : LBA. CHS translation is only needed for drives, that have no native LBA > : support. It is not about disk partitioning or label format. It is just a > : method to linearize nonlinear address space of ancient drives. For last > : 10 years, since drives lost their classic geometry, drives are doing > : this translation on firmware level. > > GEOM does have terms of CHS when it reports the classic geometry of > the device. That can't be lost, or pc98 partitioning breaks. And the > geometry reported must be massaged too, but that's a different issue. That's completely different, and I am not going to touch it. > The disk requests can be LBA, since the driver is responsible for > changing that anyway... I don't think that there's any supported > pc98 hardware that would break, but I'm not 100% sure... > > There's also some oddities at the lowest levels for pc98 controllers, > but I don't think this change would affect that. However, like I > said, ask the pc98 guys for sure. As you could see reading above thread, I have agreed keep it in legacy ATA mode. But it looks pointless to support it in new development. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Tue Aug 11 10:56:11 2009 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE274106564A; Tue, 11 Aug 2009 10:56:11 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from sakura.ccs.furiru.org (sakura.ccs.furiru.org [IPv6:2001:2f0:104:8060::1]) by mx1.freebsd.org (Postfix) with ESMTP id 5021F8FC20; Tue, 11 Aug 2009 10:56:11 +0000 (UTC) Received: from localhost (authenticated bits=0) by sakura.ccs.furiru.org (unknown) with ESMTP id n7BAtxmr022632; Tue, 11 Aug 2009 19:56:02 +0900 (JST) (envelope-from nyan@jp.FreeBSD.org) Date: Tue, 11 Aug 2009 19:55:59 +0900 (JST) Message-Id: <20090811.195559.61406403.nyan@jp.FreeBSD.org> To: imp@bsdimp.com From: Takahashi Yoshihiro In-Reply-To: <20090810.162424.846948847.imp@bsdimp.com> References: <20090810.125403.74653324.imp@bsdimp.com> <4A807BDD.6040709@FreeBSD.org> <20090810.162424.846948847.imp@bsdimp.com> X-Mailer: Mew version 6.2 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: mav@FreeBSD.org, freebsd-hardware@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 10:56:12 -0000 In article <20090810.162424.846948847.imp@bsdimp.com> "M. Warner Losh" writes: > There's also some oddities at the lowest levels for pc98 controllers, > but I don't think this change would affect that. However, like I > said, ask the pc98 guys for sure. > > I've cc'd nyan@, since he can answer the question: "What breaks in > pc98 if we lose support for CHS-based disk I/O?" The following document in Japanese says: "PC-98 usually use CHS addressing. PC-98 does not use LBA addressing." http://www.webtech.co.jp/company/doc/undocumented_mem/io_ide.txt But I could use 400MB HDD with LBA addressing on my pc98, so it seems that my pc98 supports LBA addressing at least. I don't know older pc98 supports it or not. --- TAKAHASHI Yoshihiro From owner-freebsd-hardware@FreeBSD.ORG Wed Aug 12 21:36:26 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C211C10656C2 for ; Wed, 12 Aug 2009 21:36:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181]) by mx1.freebsd.org (Postfix) with ESMTP id 74DF78FC41 for ; Wed, 12 Aug 2009 21:36:26 +0000 (UTC) Received: by yxe11 with SMTP id 11so462269yxe.3 for ; Wed, 12 Aug 2009 14:36:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=x+d2s1zhERfFcTDBhc+0H5B4wGmMV/ZPvhOtPzi/fsc=; b=b1uZkfPbtQ32RVniuy/qpPCU3vE6JwZK7W/VXoJx/89qNviX7mcYHAquVKlYMHjfFk HUOFAqesZE1UPdzedn2+P08/vIxS3Zed3DVJzWEIYQNa90ZtF377owpT/yPfz3O6UOPh ljtJtbNsxa702bVRPTVE8ap9/o9L66FaAKbNk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=RmV5g/V3t8Ux5ljYsGmvqhKfjtzjsMU1Hj6b81tcP3eq/xo4z8Kkv9VIi5/9lDzKh+ a3sBuiffm8QPO0M/vOXm3LpKDqQ8PY1Hm4h0erx2QGznJmlpksHylFzixpTyQZ/0UBKh hsfI7oQjig6n/Rjg/RtobCBDqFK95qTdBufRs= Received: by 10.90.129.15 with SMTP id b15mr259968agd.64.1250111528358; Wed, 12 Aug 2009 14:12:08 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 20sm573786agb.35.2009.08.12.14.12.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 12 Aug 2009 14:12:07 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 12 Aug 2009 14:11:02 -0700 From: Pyun YongHyeon Date: Wed, 12 Aug 2009 14:11:02 -0700 To: Frank Reppin Message-ID: <20090812211102.GE55129@michelle.cdnetworks.com> References: <4A78C0B5.8080808@undermydesk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A78C0B5.8080808@undermydesk.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hardware@freebsd.org Subject: Re: [if_re.c] INTEL mini/itx DE945GSEJT X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 21:36:27 -0000 On Wed, Aug 05, 2009 at 01:13:57AM +0200, Frank Reppin wrote: > Hi all, > > just purchased the above mentioned board: > > http://www.intel.com/products/desktop/motherboards/D945GSEJT/D945GSEJT-overview.htm > > and this board claims to come with a so called: > > Realtek 8111D > > network (10/100/1000m) chipset onboard. > > Digging in -current and google.com/ncr revealed that this certain > board/nic seems to be not supported by the -CURRENT- if_re.c provided > by FreeBSD. Some further investigations reveals that OpenBSD claims to > support this (most prolly) precious chipset (8111D) within their 4.5 > release: > > http://www.openbsd.org/45.html > (searching for 8111D will point you to re(4)) > > My question(s) is(are): > > a) does anyone run this board without flaws on fbsd-current > with its intergrated 8111D NIC re(4) man page requires major update for its supported chipsets and features. All known RealTek PCIe wired controllers(up to 8168D) should be supported. > ( my 'failover' option is to run this board using xl thanks to > it's pci slot) > > b) if a) doesn't apply - how did you get it working on current/stable > without another driver > > c) OpenBSD mentions this one ( 8111D support ) in their release notes > for a _stable_ version ( 4.5 )- but I cannot even see support for > this specific device in FreeBSD trunk/head > > d) realtek itself does provide drivers for even FreeBSD (sources)... > ... are there any experiences using those drivers > Vendor's FreeBSD driver lacks a lot of nice hardware features and its performance is suboptimal. Use it only when you have no choice for your controller. > To make a long story short/and to be honest... > > ... I'd like to see native support in at least -current. > > TIA, > > frank reppin > > -- > > http://www.undermydesk.org From owner-freebsd-hardware@FreeBSD.ORG Wed Aug 12 22:07:59 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12CB6106564A for ; Wed, 12 Aug 2009 22:07:59 +0000 (UTC) (envelope-from frank@undermydesk.org) Received: from amazone.undermydesk.org (amazone.undermydesk.org [213.211.198.100]) by mx1.freebsd.org (Postfix) with ESMTP id C41138FC16 for ; Wed, 12 Aug 2009 22:07:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by amazone.undermydesk.org (Postfix) with ESMTP id 60D0A1D7B17; Thu, 13 Aug 2009 00:07:56 +0200 (CEST) X-Virus-Scanned: amavisd-new at undermydesk.org Received: from amazone.undermydesk.org ([213.211.198.100]) by localhost (amazone.undermydesk.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjMGeDopotXP; Thu, 13 Aug 2009 00:07:50 +0200 (CEST) Received: from [192.168.0.74] (p4FD5CAE9.dip.t-dialin.net [79.213.202.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by amazone.undermydesk.org (Postfix) with ESMTPSA id F3B511D7B15; Thu, 13 Aug 2009 00:07:49 +0200 (CEST) Message-ID: <4A833D1B.80405@undermydesk.org> Date: Thu, 13 Aug 2009 00:07:23 +0200 From: Frank Reppin User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: pyunyh@gmail.com References: <4A78C0B5.8080808@undermydesk.org> <20090812211102.GE55129@michelle.cdnetworks.com> In-Reply-To: <20090812211102.GE55129@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: [if_re.c] INTEL mini/itx DE945GSEJT X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 22:07:59 -0000 Hi list! Hi Pyun, Pyun YongHyeon wrote: [...] > re(4) man page requires major update for its supported chipsets > and features. All known RealTek PCIe wired controllers(up to 8168D) > should be supported. aye - with regards to my question I'd second this. I've already figured out that this NIC is support by the (at least) current i386 snapshot ISO and our 8.0-beta2 (current) - but thankyou for coming back to me on this issue! Thankyou! -- From owner-freebsd-hardware@FreeBSD.ORG Thu Aug 13 16:26:22 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1EC71065688 for ; Thu, 13 Aug 2009 16:26:22 +0000 (UTC) (envelope-from seklecki@noc.cfi.pgh.pa.us) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id 670938FC45 for ; Thu, 13 Aug 2009 16:26:22 +0000 (UTC) Received: from [192.168.2.161] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Thu, 13 Aug 2009 11:49:54 -0400 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::265 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: freebsd-hardware@freebsd.org X-SMFBL: ZnJlZWJzZC1oYXJkd2FyZUBmcmVlYnNkLm9yZw== DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=noc.cfi.pgh.pa.us; s=noc_cfi_pgh_pa_us_key_dkim; l=256; t=1250178594; i=@noc.cfi.pgh.pa.us; h=Subject:From:To: Content-Type:Date:Message-Id:Mime-Version:X-Mailer: Content-Transfer-Encoding; bh=luDdjQrTiSy/dPHQrF3UKyEP+6o=; b=uP Jfclb9mlIYODuMfe/EPJwUC4VwJu2uOnuY4ogUqfS3U6grpcYLTZi5LVrBCBeJnE mOZaWgZCLKU2hGmELHaMDpFXaL6WJmn7Ud8Ma6vJNfaYpQaWP5OzZozCxpxNvf From: "Brian A. Seklecki" To: freebsd-hardware@freebsd.org Content-Type: text/plain Date: Thu, 13 Aug 2009 12:11:19 -0400 Message-Id: <1250179879.2306.7.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit Subject: Dell PowerEdge R710 dmesg X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Aug 2009 16:26:22 -0000 All: Can someone with an 1st generation R710 please post a dmesg(1) to the dmesgd at: http://www.nycbug.org/index.php?NAV=dmesgd;SQLIMIT=20 We're hoping that all of the mfi(4) and bnx(4) bugs have been fixed in RELENG_8. Thnaks, ~BAS From owner-freebsd-hardware@FreeBSD.ORG Sat Aug 15 09:48:30 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89E151065691 for ; Sat, 15 Aug 2009 09:48:30 +0000 (UTC) (envelope-from httpd@www1.oolz.net) Received: from www1.oolz.net (web1.oolz.net [202.146.198.20]) by mx1.freebsd.org (Postfix) with ESMTP id B23668FC41 for ; Sat, 15 Aug 2009 09:48:28 +0000 (UTC) Received: by www1.oolz.net (Postfix, from userid 109) id 1F08D21FEA; Sat, 15 Aug 2009 14:55:36 +0530 (IST) To: freebsd-hardware@freebsd.org X-PHP-Script: pleasureholidayz.com/phplist/admin/index.php for 117.206.39.230 Date: Sat, 15 Aug 2009 14:55:36 +0580 From: pleasureholidayz Message-ID: <00fb89e1232b88f0e1a34c76408066ab@pleasureholidayz.com> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] X-Mailer: phplist v2.10.5 X-MessageID: 48 X-ListMember: freebsd-hardware@freebsd.org Precedence: bulk MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Subject: Happy Independence Day X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Aug 2009 09:48:30 -0000 Dear Friends HAPPY INDEPENDENCE DAY!!! Slums to Skyscrapers... Crowded yet spacious... Where peace entails... Never losing hope...Unity in diversity... Striving for peace...Realzing the dream... Thats Our India... Where enchanment persist against all odds........ Jai Hind ************************** Please contact us at Pleasure Holidayz, 1st Floor, Pallath Business Center, Kurishupally Road, Ravipuram, Cochin, Kerala – 682 015, India. Mob: +91 9961040050, +91 9539040906 Phone: +91 484 3077234, Fax: +91 484 3061977 Website : www.pleasureholidayz.com email:pleasureholidayz@gmail.com, info@pleasureholidayz.com Chat Id: pleasureholidayz (Msn/Yahoo/gmail/skype) -- If you do not want to receive any more newsletters, http://www.pleasureholidayz.com/phplist/?p=unsubscribe&uid=35f787d7a773d60d1755f028a6f293d3 To update your preferences and to unsubscribe visit http://www.pleasureholidayz.com/phplist/?p=preferences&uid=35f787d7a773d60d1755f028a6f293d3 Forward a Message to Someone http://www.pleasureholidayz.com/phplist/?p=forward&uid=35f787d7a773d60d1755f028a6f293d3&mid=48 -- Powered by PHPlist, www.phplist.com --