From ltning at anduin.net Sat Aug 1 07:21:12 2009 From: ltning at anduin.net (=?iso-8859-1?Q?Eirik_=D8verby?=) Date: Sat Aug 1 07:21:20 2009 Subject: Driver for 3ware 9690SA, FreeBSD 8 In-Reply-To: <26ddd1750907181747g4608b4aai7ef145197bfc580d@mail.gmail.com> References: <26ddd1750907181747g4608b4aai7ef145197bfc580d@mail.gmail.com> Message-ID: <0C4ED569-22EF-4640-8C90-1011FDF45AC1@anduin.net> Hi, we use these in all our (I/O-sensitive) servers, and they perform very well. We've upgraded the firmware of all of them to the latest release (as of about 2 months ago), though I'm not sure if that was done from FreeBSD or in other systems prior to installation. We use the 3dm package to manage the boards; it's available in ports or through pkg_add -r 3dm . It's a version of the web-based management tool from 3ware; however it's an old version, and I haven't been able to extract the current version from the installation package provided by 3ware (plus, it requires Java, but so does other software we use). /Eirik On 19. juli 2009, at 02.47, Maxim Khitrov wrote: > Hello all, > > This is the first time I'm setting up hardware raid under FreeBSD. The > card is 3ware 9690SA (twa driver) and I'm running FreeBSD 8.0-BETA2. > > I'm a bit confused about the driver situation. The twa driver that > comes with FreeBSD is at version 3.70.05.001 (listed during boot). I > cannot find this version anywhere on the 3ware site. There is, > however, a reference to 3.70.05.003 [1], which is from 9.5.1 code set > for FreeBSD 7.x. Is there some disconnect between what 3ware releases > for FreeBSD and what actually makes it into the source tree? If so, is > it a better idea to use the driver that comes with FreeBSD 8 or > download the latest source from 3ware and compile that myself (note > that FreeBSD 8.x is not listed anywhere, so my guess is to use the 7.x > version)? > > The reason I ask is because I'd like to update the firmware on the > controller, but I have no idea what is the latest version that the > current driver supports. For that matter, I don't know if the firmware > that came with the card is supported, though it appears to be working > for now. Basically, I'm just looking for advice on how to deal with > drivers that are primarily maintained outside of the FreeBSD source > tree. > > If anyone else is using the same controller, I'd also appreciate any > advice on setting up the CLI (my guess is that I should use the > sysutils/tw_cli port) and e-mail notifications for things like the > loss of a drive. > > - Max > > [1] http://www.3ware.com/kb/article.aspx?id=14847 > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org > " > From mkhitrov at gmail.com Sat Aug 1 14:44:07 2009 From: mkhitrov at gmail.com (Maxim Khitrov) Date: Sat Aug 1 14:44:13 2009 Subject: Driver for 3ware 9690SA, FreeBSD 8 In-Reply-To: <0C4ED569-22EF-4640-8C90-1011FDF45AC1@anduin.net> References: <26ddd1750907181747g4608b4aai7ef145197bfc580d@mail.gmail.com> <0C4ED569-22EF-4640-8C90-1011FDF45AC1@anduin.net> Message-ID: <26ddd1750908010743j44e2882amf3a4e6bbc36fd2e@mail.gmail.com> 2009/8/1 Eirik ?verby : > On 19. juli 2009, at 02.47, Maxim Khitrov wrote: > >> Hello all, >> >> This is the first time I'm setting up hardware raid under FreeBSD. The >> card is 3ware 9690SA (twa driver) and I'm running FreeBSD 8.0-BETA2. >> >> I'm a bit confused about the driver situation. The twa driver that >> comes with FreeBSD is at version 3.70.05.001 (listed during boot). I >> cannot find this version anywhere on the 3ware site. There is, >> however, a reference to 3.70.05.003 [1], which is from 9.5.1 code set >> for FreeBSD 7.x. Is there some disconnect between what 3ware releases >> for FreeBSD and what actually makes it into the source tree? If so, is >> it a better idea to use the driver that comes with FreeBSD 8 or >> download the latest source from 3ware and compile that myself (note >> that FreeBSD 8.x is not listed anywhere, so my guess is to use the 7.x >> version)? >> >> The reason I ask is because I'd like to update the firmware on the >> controller, but I have no idea what is the latest version that the >> current driver supports. For that matter, I don't know if the firmware >> that came with the card is supported, though it appears to be working >> for now. Basically, I'm just looking for advice on how to deal with >> drivers that are primarily maintained outside of the FreeBSD source >> tree. >> >> If anyone else is using the same controller, I'd also appreciate any >> advice on setting up the CLI (my guess is that I should use the >> sysutils/tw_cli port) and e-mail notifications for things like the >> loss of a drive. >> >> - Max >> > > Hi, > > we use these in all our (I/O-sensitive) servers, and they perform very well. > We've upgraded the firmware of all of them to the latest release (as of > about 2 months ago), though I'm not sure if that was done from FreeBSD or in > other systems prior to installation. > > We use the 3dm package to manage the boards; it's available in ports or > through pkg_add -r 3dm . It's a version of the web-based management tool > from 3ware; however it's an old version, and I haven't been able to extract > the current version from the installation package provided by 3ware (plus, > it requires Java, but so does other software we use). > > /Eirik I got everything working using the 3ware 9.5.2 code set. Firmware update was performed through dos, though you can also do it from FreeBSD once you have tw_cli or 3DM2 installed. For the driver, take twa.tgz file from packages/drivers/freebsd/src/7.x on the complete 9.5.2 code set CD, extract it somewhere, then copy all tw_* files to /sys/dev/twa, overwriting the files already there. The provided Makefile is the same that is in FreeBSD source tree, so nothing to do with that. To prevent csup from overwriting the new driver code on the next source update, create a /var/db/sup/refuse file with a single "src/sys/dev/twa*" line. The command-line tw_cli utility can be installed from ports, since it's the latest version. 3DM2, however, is outdated, so I also installed this from the code set CD. Simply copy packages/installers/tools/freebsd/7.x/x86_64/setupFreeBSD7_x64.sh to your server and run `./setupFreeBSD7_x64.sh -console`. That launches the 3DM2 installation. At the end of it, the web server will be listening on localhost:888, default password is 3ware. An rc script is placed into /etc/rc.d to launch 3DM2 after reboot. There is no need to have java installed from ports because the installer will use its own version when another one isn't available. That's all there is to it, just wanted to provide this overview for anyone else that may be trying to get the card working. By the way, I decided to go back to FreeBSD 7.2 instead of 8.0 until there is official 8.0 support from 3ware. - Max From achilov-rn at askd.ru Mon Aug 3 02:44:22 2009 From: achilov-rn at askd.ru (Rashid N. Achilov) Date: Mon Aug 3 02:44:37 2009 Subject: Intel 024B server deadlock In-Reply-To: <200907310855.n6V8tEBU088592@banyan.cs.ait.ac.th> References: <200907311505.43450.achilov-rn@askd.ru> <200907310855.n6V8tEBU088592@banyan.cs.ait.ac.th> Message-ID: <200908030947.16780.achilov-rn@askd.ru> On Friday 31 July 2009, Olivier Nicole wrote: > Hi, > > > Intel server (configuration below) with 4 SCSI and one IDE > > drives. When I try to READ big archive file (i.e. 150-180 Mb) > > idependently, through tar -xf filename.tar or reading through Samba, > > from IDE drive (ad0) box throws a message > > > > Jul 30 16:11:38 svr-63 kernel: ad0: TIMEOUT - READ_DMA retrying (1 > > retry left) LBA=151318527 > > Just a wild guess, but what about trying to change your BIOS settings > for the IDE disk, like disable DMA? Or a firware upgrade of that > ServerWorks ROSB4 UDMA33 controller? Probably, I'll try to do this. But I'm confused that - it isn't new server, on the contrary, about 3-4 years it was our Windows Domain Controller and works fine. -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), JID: citycat4@jabber.org OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A From whizzter at gmail.com Mon Aug 3 14:20:53 2009 From: whizzter at gmail.com (Jonas Lund) Date: Mon Aug 3 14:21:30 2009 Subject: Intel 024B server deadlock In-Reply-To: <200908030947.16780.achilov-rn@askd.ru> References: <200907311505.43450.achilov-rn@askd.ru> <200907310855.n6V8tEBU088592@banyan.cs.ait.ac.th> <200908030947.16780.achilov-rn@askd.ru> Message-ID: <436c7eda0908030651j37263783h2a4157da49230011@mail.gmail.com> Tried checking smart stats on the disk? these timeout messages are quite common to happen when a disk is nearing death (Ignored it myself once.. stupid move) 2009/8/3 Rashid N. Achilov : > On Friday 31 July 2009, Olivier Nicole wrote: >> Hi, >> >> > Intel server (configuration below) with 4 SCSI and one IDE >> > drives. When I try to READ big archive file (i.e. 150-180 Mb) >> > idependently, through tar -xf filename.tar or reading through Samba, >> > from IDE drive (ad0) box throws a message >> > >> > Jul 30 16:11:38 svr-63 kernel: ad0: TIMEOUT - READ_DMA retrying (1 >> > retry left) LBA=151318527 >> >> Just a wild guess, but what about trying to change your BIOS settings >> for the IDE disk, like disable DMA? Or a firware upgrade of that >> ServerWorks ROSB4 UDMA33 controller? > > Probably, I'll try to do this. But I'm confused that - it isn't new server, on > the contrary, about 3-4 years it was our Windows Domain Controller and works > fine. > -- > ? With Best Regards. > ? Rashid N. Achilov (RNA1-RIPE), JID: citycat4@jabber.org > ? OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru > ? PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From frank at undermydesk.org Tue Aug 4 23:29:38 2009 From: frank at undermydesk.org (Frank Reppin) Date: Tue Aug 4 23:29:50 2009 Subject: [if_re.c] INTEL mini/itx DE945GSEJT Message-ID: <4A78C0B5.8080808@undermydesk.org> 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 ( 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 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 whizzter at gmail.com Wed Aug 5 15:20:16 2009 From: whizzter at gmail.com (Jonas Lund) Date: Wed Aug 5 15:20:24 2009 Subject: [if_re.c] INTEL mini/itx DE945GSEJT In-Reply-To: <4A78C0B5.8080808@undermydesk.org> References: <4A78C0B5.8080808@undermydesk.org> Message-ID: <436c7eda0908050820g5a610a9dk6b1b1cf20afe2be8@mail.gmail.com> 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 > > 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 > ? ? ( 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 > > 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 > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From mav at FreeBSD.org Sat Aug 8 21:39:57 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Sat Aug 8 21:40:09 2009 Subject: Do we still need ATA disk CHS addressing? Message-ID: <4A7DF076.4070203@FreeBSD.org> 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? -- Alexander Motin From bjb at darco.dk Sun Aug 9 09:18:05 2009 From: bjb at darco.dk (Bjarne) Date: Sun Aug 9 09:18:12 2009 Subject: dwa-547 - atheros chip not recognized Message-ID: <4A7E8ECD.8010208@darco.dk> 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 nyan at jp.FreeBSD.org Sun Aug 9 11:25:56 2009 From: nyan at jp.FreeBSD.org (Takahashi Yoshihiro) Date: Sun Aug 9 11:26:02 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <4A7DF076.4070203@FreeBSD.org> References: <4A7DF076.4070203@FreeBSD.org> Message-ID: <20090809.202549.27838630.nyan@jp.FreeBSD.org> 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 alireza.torabi at gmail.com Sun Aug 9 12:58:33 2009 From: alireza.torabi at gmail.com (Alireza Torabi) Date: Sun Aug 9 12:58:39 2009 Subject: 8. Current Intel 5100 AGN wifi Message-ID: 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 ed at 80386.nl Sun Aug 9 13:47:26 2009 From: ed at 80386.nl (Ed Schouten) Date: Sun Aug 9 13:47:38 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <20090809.202549.27838630.nyan@jp.FreeBSD.org> References: <4A7DF076.4070203@FreeBSD.org> <20090809.202549.27838630.nyan@jp.FreeBSD.org> Message-ID: <20090809134724.GX1292@hoeg.nl> * 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? -- Ed Schouten WWW: http://80386.nl/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20090809/ce8390fc/attachment.pgp From mav at FreeBSD.org Sun Aug 9 14:15:52 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Sun Aug 9 14:15:59 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <20090809134724.GX1292@hoeg.nl> References: <4A7DF076.4070203@FreeBSD.org> <20090809.202549.27838630.nyan@jp.FreeBSD.org> <20090809134724.GX1292@hoeg.nl> Message-ID: <4A7ED9DF.1080007@FreeBSD.org> 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 sam at freebsd.org Sun Aug 9 20:48:40 2009 From: sam at freebsd.org (Sam Leffler) Date: Sun Aug 9 20:48:47 2009 Subject: dwa-547 - atheros chip not recognized In-Reply-To: <4A7E8ECD.8010208@darco.dk> References: <4A7E8ECD.8010208@darco.dk> Message-ID: <4A7F2EDA.3070506@freebsd.org> 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 jhs at berklix.com Mon Aug 10 09:32:45 2009 From: jhs at berklix.com (Julian H. Stacey) Date: Mon Aug 10 09:32:58 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: Your message "Sun, 09 Aug 2009 00:39:02 +0300." <4A7DF076.4070203@FreeBSD.org> Message-ID: <200908100904.n7A94BAB044505@fire.js.berklix.net> > 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 mav at FreeBSD.org Mon Aug 10 09:43:03 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Aug 10 09:43:10 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <200908100904.n7A94BAB044505@fire.js.berklix.net> References: <200908100904.n7A94BAB044505@fire.js.berklix.net> Message-ID: <4A7FEBA2.5090106@FreeBSD.org> 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 jhs at berklix.com Mon Aug 10 16:38:33 2009 From: jhs at berklix.com (Julian H. Stacey) Date: Mon Aug 10 16:38:40 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: Your message "Mon, 10 Aug 2009 12:42:58 +0300." <4A7FEBA2.5090106@FreeBSD.org> Message-ID: <200908101640.n7AGeYH0054650@fire.js.berklix.net> 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 mav at FreeBSD.org Mon Aug 10 17:44:12 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Aug 10 17:44:19 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <200908101640.n7AGeYH0054650@fire.js.berklix.net> References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> Message-ID: <4A805C2E.8020300@FreeBSD.org> 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 jhs at berklix.com Mon Aug 10 18:52:44 2009 From: jhs at berklix.com (Julian H. Stacey) Date: Mon Aug 10 18:52:55 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: Your message "Mon, 10 Aug 2009 20:38:16 +0200." <86eirjbjl3.fsf@ds4.des.no> Message-ID: <200908101854.n7AIseFv056967@fire.js.berklix.net> > 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 des at des.no Mon Aug 10 18:53:34 2009 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Mon Aug 10 18:53:41 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <200908101640.n7AGeYH0054650@fire.js.berklix.net> (Julian H. Stacey's message of "Mon, 10 Aug 2009 18:40:34 +0200") References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> Message-ID: <86eirjbjl3.fsf@ds4.des.no> "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 > 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. 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 -- Dag-Erling Sm?rgrav - des@des.no From imp at bsdimp.com Mon Aug 10 18:57:27 2009 From: imp at bsdimp.com (Warner Losh) Date: Mon Aug 10 18:57:34 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <86eirjbjl3.fsf@ds4.des.no> References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> <86eirjbjl3.fsf@ds4.des.no> Message-ID: <20090810.125403.74653324.imp@bsdimp.com> From: Dag-Erling Sm?rgrav 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 (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. > > 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. 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 ertr1013 at student.uu.se Mon Aug 10 19:20:05 2009 From: ertr1013 at student.uu.se (Erik Trulsson) Date: Mon Aug 10 19:20:16 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <86eirjbjl3.fsf@ds4.des.no> References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> <86eirjbjl3.fsf@ds4.des.no> Message-ID: <20090810190258.GA25641@owl.midgard.homeip.net> On Mon, Aug 10, 2009 at 08:38:16PM +0200, Dag-Erling Sm?rgrav 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"? > > > 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. > > 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. 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.) -- Erik Trulsson ertr1013@student.uu.se From mav at FreeBSD.org Mon Aug 10 19:59:27 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Aug 10 19:59:38 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <20090810.125403.74653324.imp@bsdimp.com> References: <200908101640.n7AGeYH0054650@fire.js.berklix.net> <86eirjbjl3.fsf@ds4.des.no> <20090810.125403.74653324.imp@bsdimp.com> Message-ID: <4A807BDD.6040709@FreeBSD.org> 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 imp at bsdimp.com Mon Aug 10 22:27:20 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Aug 10 22:27:39 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <4A807BDD.6040709@FreeBSD.org> References: <86eirjbjl3.fsf@ds4.des.no> <20090810.125403.74653324.imp@bsdimp.com> <4A807BDD.6040709@FreeBSD.org> Message-ID: <20090810.162424.846948847.imp@bsdimp.com> 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 frank at undermydesk.org Mon Aug 10 23:25:11 2009 From: frank at undermydesk.org (Frank Reppin) Date: Mon Aug 10 23:25:19 2009 Subject: [if_re.c] INTEL mini/itx DE945GSEJT In-Reply-To: <436c7eda0908050820g5a610a9dk6b1b1cf20afe2be8@mail.gmail.com> References: <4A78C0B5.8080808@undermydesk.org> <436c7eda0908050820g5a610a9dk6b1b1cf20afe2be8@mail.gmail.com> Message-ID: <4A80AC41.8050003@undermydesk.org> 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 mav at FreeBSD.org Tue Aug 11 07:35:14 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Tue Aug 11 07:35:26 2009 Subject: Do we still need ATA disk CHS addressing? In-Reply-To: <20090810.162424.846948847.imp@bsdimp.com> References: <86eirjbjl3.fsf@ds4.des.no> <20090810.125403.74653324.imp@bsdimp.com> <4A807BDD.6040709@FreeBSD.org> <20090810.162424.846948847.imp@bsdimp.com> Message-ID: <4A811F2B.7050402@FreeBSD.org> 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 nyan at jp.FreeBSD.org Tue Aug 11 10:56:12 2009 From: nyan at jp.FreeBSD.org (Takahashi Yoshihiro) Date: Tue Aug 11 10:56:19 2009 Subject: Do we still need ATA disk CHS addressing? 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> Message-ID: <20090811.195559.61406403.nyan@jp.FreeBSD.org> 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 pyunyh at gmail.com Wed Aug 12 21:36:27 2009 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Wed Aug 12 21:36:34 2009 Subject: [if_re.c] INTEL mini/itx DE945GSEJT In-Reply-To: <4A78C0B5.8080808@undermydesk.org> References: <4A78C0B5.8080808@undermydesk.org> Message-ID: <20090812211102.GE55129@michelle.cdnetworks.com> 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 frank at undermydesk.org Wed Aug 12 22:07:59 2009 From: frank at undermydesk.org (Frank Reppin) Date: Wed Aug 12 22:08:05 2009 Subject: [if_re.c] INTEL mini/itx DE945GSEJT In-Reply-To: <20090812211102.GE55129@michelle.cdnetworks.com> References: <4A78C0B5.8080808@undermydesk.org> <20090812211102.GE55129@michelle.cdnetworks.com> Message-ID: <4A833D1B.80405@undermydesk.org> 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 seklecki at noc.cfi.pgh.pa.us Thu Aug 13 16:26:22 2009 From: seklecki at noc.cfi.pgh.pa.us (Brian A. Seklecki) Date: Thu Aug 13 16:26:32 2009 Subject: Dell PowerEdge R710 dmesg Message-ID: <1250179879.2306.7.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> 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 info at pleasureholidayz.com Sat Aug 15 09:48:30 2009 From: info at pleasureholidayz.com (pleasureholidayz) Date: Sat Aug 15 09:48:37 2009 Subject: Happy Independence Day Message-ID: <00fb89e1232b88f0e1a34c76408066ab@pleasureholidayz.com> 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 -- From seklecki at noc.cfi.pgh.pa.us Mon Aug 17 20:40:54 2009 From: seklecki at noc.cfi.pgh.pa.us (Brian A. Seklecki) Date: Mon Aug 17 20:41:01 2009 Subject: Dell PowerEdge R710 dmesg In-Reply-To: <1250179879.2306.7.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> References: <1250179879.2306.7.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Message-ID: <1250541653.2306.379.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> On Thu, 2009-08-13 at 12:11 -0400, Brian A. Seklecki wrote: > All: > > Can someone with an 1st generation R710 please post a dmesg(1) to the > dmesgd at: > Arrived within four days: http://www.nycbug.org/?NAV=dmesgd;f_dmesg=;f_bsd=;f_nick=;f_descr=;dmesgid=2007#2007 ~BAS From lists at freebsdonline.com Wed Aug 19 16:59:41 2009 From: lists at freebsdonline.com (Ovi) Date: Wed Aug 19 16:59:47 2009 Subject: iwn driver for 4965AGN in FreeBSD 7.2 stable Message-ID: <4A8C29B2.8090405@freebsdonline.com> Hello, Anybody use iwn driver for intel 4965AGN wifi card with freebsd 7.2? none1@pci0:2:0:0: class=0x028000 card=0x10018086 chip=0x42298086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Wireless WiFi Link 4965AGN(supporting 802.11a/b/g/Draft-N) (Intel 4965AGN)' class = network FreeBSD laptop 7.2-STABLE FreeBSD 7.2-STABLE #3: Fri Aug 14 21:17:58 EEST 2009 root@laptop:/usr/obj/usr/src/sys/LAPTOP i386 I've tried the driver from preforce and is not working. best regards, ovi From david at esn.org.za Thu Aug 20 09:50:59 2009 From: david at esn.org.za (David Peall) Date: Thu Aug 20 09:51:06 2009 Subject: Intel DP45SG motherboard problem Message-ID: <0807767D2D53E649827BC55A3A53B067015C3ACD5269@exchange.ct.esn.org.za> Hi I'm having such trouble trying to get FreeBSD onto the PC. I've googled and found the following old thread: http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg03470.html And the following forum post: http://forums.freebsd.org/showthread.php?t=3048 But there is no solution proposed. I've tried everything I can think of. I have a pxeboot setup and could boot custom kernels but I'm just not sure what to change. I've tried 7.0, 7.2, 7.2-p3, 8 beta, 8-current all amd64 and none of them will get to the sysinstall screen. If I try install the i386 version I can get to the sysinstall screen but if I push up/down once it scrolls to the top/bottom and then its locked all keys are dead I've tried two different USB keyboards. There are no PS2 ports on this motherboard. Is available to guide me to try solve this problem. Kind Regards -- David Peall From rb at gid.co.uk Thu Aug 20 10:35:25 2009 From: rb at gid.co.uk (Bob Bishop) Date: Thu Aug 20 10:35:31 2009 Subject: Intel DP45SG motherboard problem In-Reply-To: <0807767D2D53E649827BC55A3A53B067015C3ACD5269@exchange.ct.esn.org.za> References: <0807767D2D53E649827BC55A3A53B067015C3ACD5269@exchange.ct.esn.org.za> Message-ID: Hi, On 20 Aug 2009, at 10:16, David Peall wrote: > Hi > > I'm having such trouble trying to get FreeBSD onto the PC. I've > googled and found the following old thread: > http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg03470.html > > And the following forum post: > http://forums.freebsd.org/showthread.php?t=3048 > > But there is no solution proposed. I've tried everything I can > think of. [etc] Is the BIOS up to date? See: http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2932&OSFullname=OS+Independent&lang=eng&strOSs=38 -- Bob Bishop rb@gid.co.uk From david at esn.org.za Thu Aug 20 11:04:26 2009 From: david at esn.org.za (David Peall) Date: Thu Aug 20 11:04:33 2009 Subject: Intel DP45SG motherboard problem In-Reply-To: References: <0807767D2D53E649827BC55A3A53B067015C3ACD5269@exchange.ct.esn.org.za> Message-ID: <0807767D2D53E649827BC55A3A53B067015C3ACD527A@exchange.ct.esn.org.za> > > Hi > > > > I'm having such trouble trying to get FreeBSD onto the PC. I've > > googled and found the following old thread: > > http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg03470.html > > > > And the following forum post: > > http://forums.freebsd.org/showthread.php?t=3048 > > > > But there is no solution proposed. I've tried everything I can > > think of. [etc] > > Is the BIOS up to date? See: > > http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=293 > 2&OSFullname=OS+Independent&lang=eng&strOSs=38 Yes it is. -- David Peall :: IT Manager e-Schools' Network :: http://www.esn.org.za/ Phone +27 (021) 674-9140 From david at esn.org.za Thu Aug 20 15:36:00 2009 From: david at esn.org.za (David Peall) Date: Thu Aug 20 15:36:07 2009 Subject: swapping DP45SG for Supermicro X7SBL-LN2 Message-ID: <0807767D2D53E649827BC55A3A53B067015C3ACD528E@exchange.ct.esn.org.za> I just wanted to know if anyone had used this board as we are going to swap the DP45SG out due to the problems with running FreeBSD am64 on it. Website: http://www.supermicro.com/products/motherboard/Xeon3000/3200/X7SBL-LN2.cfm Many thanks -- David Peall From avg at freebsd.org Tue Aug 25 16:54:42 2009 From: avg at freebsd.org (Andriy Gapon) Date: Tue Aug 25 16:54:54 2009 Subject: GA-MA780G-UD3H motherboard Message-ID: <4A9412ED.6080309@freebsd.org> I have become to own Gigabyte GA-MA780G-UD3H motherboard: http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H It is based on AMD 780G + SB700. BTW, CPU I am using is Athlon II X2 250. Sorry for the broadcast announcement, but this is my first AMD-based system in many years, so I eagerly started exploring it and hacking for it. For this reason please expect a number of questions from me as well as some reports and hopefully code related to this motherboard. I am going to post them as follow-ups to this email. Meanwhile, if you interested in any information about this motherboard - data dumps, outputs from tools, etc - please let me know, I will try my best to provide that. -- Andriy Gapon From sfourman at gmail.com Tue Aug 25 19:00:38 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Tue Aug 25 19:00:55 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <4A9412ED.6080309@freebsd.org> References: <4A9412ED.6080309@freebsd.org> Message-ID: <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> > Meanwhile, if you interested in any information about this motherboard - data > dumps, outputs from tools, etc - please let me know, I will try my best to provide > that. it would be interesting to see a dmesg as a starting point. Sam Fourman Jr. From thierry.herbelot at free.fr Tue Aug 25 19:46:21 2009 From: thierry.herbelot at free.fr (Thierry Herbelot) Date: Tue Aug 25 19:46:41 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> References: <4A9412ED.6080309@freebsd.org> <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> Message-ID: <200908252127.48214.thierry.herbelot@free.fr> Le Tuesday 25 August 2009, Sam Fourman Jr. a ?crit : > > Meanwhile, if you interested in any information about this motherboard - > > data dumps, outputs from tools, etc - please let me know, I will try my > > best to provide that. > > it would be interesting to see a dmesg as a starting point. > here you are ;-) I have plugged a PCI sound board in the machine, but it does seem to be detected (there could be some issue with PCI bus enumeration : I also include a pciconf log) TfH > > Sam Fourman Jr. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-STABLE #12: Mon Jul 6 09:37:34 CEST 2009 XXX@YYY:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (3106.64-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f TSC: P-state invariant Cores per package: 2 usable memory = 4008947712 (3823 MB) avail memory = 3836862464 (3659 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bfce0000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xee00-0xeeff mem 0xd0000000-0xdfffffff,0xfdfe0000-0xfdfeffff,0xfde00000-0xfdefffff irq 18 at device 5.0 on pci1 hdac0: mem 0xfdffc000-0xfdffffff irq 19 at device 5.1 on pci1 hdac0: HDA Driver Revision: 20090329_0131 hdac0: [ITHREAD] pcib2: irq 18 at device 10.0 on pci0 pci2: on pcib2 re0: port 0xde00-0xdeff mem 0xfdaff000-0xfdafffff,0xfdae0000-0xfdaeffff irq 18 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1f:d0:56:75:23 re0: [FILTER] atapci0: port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 6 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ata6: on atapci0 ata6: [ITHREAD] ata7: on atapci0 ata7: [ITHREAD] ohci0: mem 0xfe02e000-0xfe02efff irq 16 at device 18.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfe02d000-0xfe02dfff irq 16 at device 18.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfe02c000-0xfe02c0ff irq 17 at device 18.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 6 ports with 6 removable, self powered ohci2: mem 0xfe02b000-0xfe02bfff irq 18 at device 19.0 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: on ohci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 3 ports with 3 removable, self powered ohci3: mem 0xfe02a000-0xfe02afff irq 18 at device 19.1 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 3 ports with 3 removable, self powered ehci1: mem 0xfe029000-0xfe0290ff irq 19 at device 19.2 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 3 ports each: usb3 usb4 usb5: on ehci1 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 6 ports with 6 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] hdac1: mem 0xfe024000-0xfe027fff irq 16 at device 20.2 on pci0 hdac1: HDA Driver Revision: 20090329_0131 hdac1: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 fwohci0: mem 0xfdcff000-0xfdcff7ff,0xfdcf8000-0xfdcfbfff irq 22 at device 14.0 on pci3 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:70:c0:59:00:00:1f:d0 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:70:c0:00:1f:d0 fwe0: Ethernet address: 02:70:c0:00:1f:d0 fwip0: on firewire0 fwip0: Firewire address: 00:70:c0:59:00:00:1f:d0 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xb6e80000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode ohci4: mem 0xfe028000-0xfe028fff irq 18 at device 20.5 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb6: OHCI version 1.0, legacy support usb6: SMM does not respond, resetting usb6: on ohci4 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered amdtemp0: on hostb4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio2: configured irq 5 not in bitmap of probed irqs 0 sio2: port may not be enabled sio3: configured irq 9 not in bitmap of probed irqs 0 sio3: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad4: 238474MB at ata2-master SATA150 ZFS filesystem version 13 ZFS storage pool version 13 ad6: 238475MB at ata3-master SATA150 ad8: 238475MB at ata4-master SATA150 acd0: DVDR at ata7-master SATA150 hdac0: HDA Codec #0: ATI RS690/780 HDMI pcm0: at cad 0 nid 1 on hdac0 hdac1: HDA Codec #0: Realtek ALC885 pcm1: at cad 0 nid 1 on hdac1 pcm2: at cad 0 nid 1 on hdac1 pcm3: at cad 0 nid 1 on hdac1 GEOM_LABEL: Label for provider ad4s1a is ufsid/4895a4a721182022. GEOM_LABEL: Label for provider ad4s1d is ufsid/4895a4b3b6d4e02e. GEOM_LABEL: Label for provider ad4s1e is ufsid/4895a4b54799f68b. GEOM_LABEL: Label for provider ad4s1f is ufsid/4895a4b724bcb48f. GEOM_LABEL: Label for provider ad4s2a is ufsid/49185b60bbfa4d50. GEOM_LABEL: Label for provider ad6s1 is ext2fs//. GEOM_LABEL: Label for provider ad6s2 is ext2fs//1. GEOM_LABEL: Label for provider ad8s1a is ufsid/4895a498589c3d5f. GEOM_LABEL: Label for provider ad8s1d is ufsid/4895a48d5fd2f14b. GEOM_LABEL: Label for provider ad8s1e is ufsid/4895a48489eb6120. GEOM_LABEL: Label for provider ad8s1f is ufsid/4895a48a019d7151. GEOM_LABEL: Label for provider ad8s2a is ufsid/4729b57b020c7526. GEOM_LABEL: Label for provider ad8s2d is ufsid/4729b587458f5554. GEOM_LABEL: Label for provider ad8s2e is ufsid/4729b58af29c6330. SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s2a GEOM_LABEL: Label ufsid/49185b60bbfa4d50 removed. machine# pciconf -lv hostb0@pci0:0:0:0: class=0x060000 card=0x96001022 chip=0x96001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x96021022 chip=0x96021022 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' class = bridge subclass = PCI-PCI pcib2@pci0:0:10:0: class=0x060400 card=0x96001022 chip=0x96091022 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' class = bridge subclass = PCI-PCI atapci0@pci0:0:17:0: class=0x010601 card=0xb0021458 chip=0x43911002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 SATA Controller [AHCI mode]' class = mass storage subclass = SATA ohci0@pci0:0:18:0: class=0x0c0310 card=0x50041458 chip=0x43971002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI0 Controller' class = serial bus subclass = USB ohci1@pci0:0:18:1: class=0x0c0310 card=0x50041458 chip=0x43981002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI1 Controller' class = serial bus subclass = USB ehci0@pci0:0:18:2: class=0x0c0320 card=0x50041458 chip=0x43961002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB EHCI Controller' class = serial bus subclass = USB ohci2@pci0:0:19:0: class=0x0c0310 card=0x50041458 chip=0x43971002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI0 Controller' class = serial bus subclass = USB ohci3@pci0:0:19:1: class=0x0c0310 card=0x50041458 chip=0x43981002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI1 Controller' class = serial bus subclass = USB ehci1@pci0:0:19:2: class=0x0c0320 card=0x50041458 chip=0x43961002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB EHCI Controller' class = serial bus subclass = USB none0@pci0:0:20:0: class=0x0c0500 card=0x43851458 chip=0x43851002 rev=0x3a hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI SMBus (ATI RD600/RS600)' class = serial bus subclass = SMBus atapci1@pci0:0:20:1: class=0x01018a card=0x50021458 chip=0x439c1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'PATA 133 Controller (SB7xx)' class = mass storage subclass = ATA hdac1@pci0:0:20:2: class=0x040300 card=0xa0021458 chip=0x43831002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'IXP SB600 High Definition Audio Controller' class = multimedia subclass = HDA isab0@pci0:0:20:3: class=0x060100 card=0x43831002 chip=0x439d1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 LPC host controller' class = bridge subclass = PCI-ISA pcib3@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 rev=0x00 hdr=0x01 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'IXP SB600 PCI to PCI Bridge' class = bridge subclass = PCI-PCI ohci4@pci0:0:20:5: class=0x0c0310 card=0x50041458 chip=0x43991002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 USB OHCI2 Controller' class = serial bus subclass = USB hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) DRAM Controller' class = bridge subclass = HOST-PCI hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon64/Opteron/Sempron (K8 Family) Miscellaneous Control' class = bridge subclass = HOST-PCI vgapci0@pci0:1:5:0: class=0x030000 card=0xd0001458 chip=0x96101002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'Radeon HD 3200 Integrated Graphics Processor (780G)' class = display subclass = VGA hdac0@pci0:1:5:1: class=0x040300 card=0x960f1002 chip=0x960f1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' class = multimedia subclass = HDA re0@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111)' class = network subclass = ethernet fwohci0@pci0:3:14:0: class=0x0c0010 card=0x10001458 chip=0x8024104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller' class = serial bus subclass = FireWire From rnoland at FreeBSD.org Tue Aug 25 20:08:54 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Tue Aug 25 20:09:07 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <200908252127.48214.thierry.herbelot@free.fr> References: <4A9412ED.6080309@freebsd.org> <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> <200908252127.48214.thierry.herbelot@free.fr> Message-ID: <1251230025.45706.280.camel@balrog.2hip.net> On Tue, 2009-08-25 at 21:27 +0200, Thierry Herbelot wrote: > Le Tuesday 25 August 2009, Sam Fourman Jr. a ?crit : > > > Meanwhile, if you interested in any information about this motherboard - > > > data dumps, outputs from tools, etc - please let me know, I will try my > > > best to provide that. > > > > it would be interesting to see a dmesg as a starting point. > > > here you are ;-) > > I have plugged a PCI sound board in the machine, but it does seem to be > detected (there could be some issue with PCI bus enumeration : I also include > a pciconf log) I'm curious why you would plug in a pci sound card? You already have both a standard hda codec as well as the hda codec for the hdmi port of the video. If you are discovering that it isn't working... set hw.snd.default_unit=1 which is typcially your normal analog audio port. The hdmi port on radeon chips tends to be enumerated before the normal system codecs, so people tend to think that sound isn't working. robert. > TfH > > > > Sam Fourman Jr. > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.2-STABLE #12: Mon Jul 6 09:37:34 CEST 2009 > XXX@YYY:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (3106.64-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 > > Features=0x178bfbff > Features2=0x2001 > AMD Features=0xea500800 > AMD Features2=0x11f > TSC: P-state invariant > Cores per package: 2 > usable memory = 4008947712 (3823 MB) > avail memory = 3836862464 (3659 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > This module (opensolaris) contains code covered by the > Common Development and Distribution License (CDDL) > see http://opensolaris.org/os/licensing/opensolaris_license/ > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, bfce0000 (3) failed > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0xee00-0xeeff mem > 0xd0000000-0xdfffffff,0xfdfe0000-0xfdfeffff,0xfde00000-0xfdefffff irq 18 at > device 5.0 on pci1 > hdac0: mem 0xfdffc000-0xfdffffff > irq 19 at device 5.1 on pci1 > hdac0: HDA Driver Revision: 20090329_0131 > hdac0: [ITHREAD] > pcib2: irq 18 at device 10.0 on pci0 > pci2: on pcib2 > re0: Ethernet> port 0xde00-0xdeff mem 0xfdaff000-0xfdafffff,0xfdae0000-0xfdaeffff > irq 18 at device 0.0 on pci2 > re0: Using 1 MSI messages > re0: Chip rev. 0x3c000000 > re0: MAC rev. 0x00400000 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > re0: Ethernet address: 00:1f:d0:56:75:23 > re0: [FILTER] > atapci0: port > 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem > 0xfe02f000-0xfe02f3ff irq 22 at device 17.0 on pci0 > atapci0: [ITHREAD] > atapci0: AHCI Version 01.10 controller with 6 ports detected > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > ata4: on atapci0 > ata4: [ITHREAD] > ata5: on atapci0 > ata5: [ITHREAD] > ata6: on atapci0 > ata6: [ITHREAD] > ata7: on atapci0 > ata7: [ITHREAD] > ohci0: mem 0xfe02e000-0xfe02efff irq 16 at > device 18.0 on pci0 > ohci0: [GIANT-LOCKED] > ohci0: [ITHREAD] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 3 ports with 3 removable, self powered > ohci1: mem 0xfe02d000-0xfe02dfff irq 16 at > device 18.1 on pci0 > ohci1: [GIANT-LOCKED] > ohci1: [ITHREAD] > usb1: OHCI version 1.0, legacy support > usb1: SMM does not respond, resetting > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 3 ports with 3 removable, self powered > ehci0: mem 0xfe02c000-0xfe02c0ff irq 17 at > device 18.2 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb2: EHCI version 1.0 > usb2: companion controllers, 3 ports each: usb0 usb1 > usb2: on ehci0 > usb2: USB revision 2.0 > uhub2: on usb2 > uhub2: 6 ports with 6 removable, self powered > ohci2: mem 0xfe02b000-0xfe02bfff irq 18 at > device 19.0 on pci0 > ohci2: [GIANT-LOCKED] > ohci2: [ITHREAD] > usb3: OHCI version 1.0, legacy support > usb3: on ohci2 > usb3: USB revision 1.0 > uhub3: on usb3 > uhub3: 3 ports with 3 removable, self powered > ohci3: mem 0xfe02a000-0xfe02afff irq 18 at > device 19.1 on pci0 > ohci3: [GIANT-LOCKED] > ohci3: [ITHREAD] > usb4: OHCI version 1.0, legacy support > usb4: SMM does not respond, resetting > usb4: on ohci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 3 ports with 3 removable, self powered > ehci1: mem 0xfe029000-0xfe0290ff irq 19 at > device 19.2 on pci0 > ehci1: [GIANT-LOCKED] > ehci1: [ITHREAD] > usb5: EHCI version 1.0 > usb5: companion controllers, 3 ports each: usb3 usb4 > usb5: on ehci1 > usb5: USB revision 2.0 > uhub5: on usb5 > uhub5: 6 ports with 6 removable, self powered > pci0: at device 20.0 (no driver attached) > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 20.1 on pci0 > ata0: on atapci1 > ata0: [ITHREAD] > hdac1: mem 0xfe024000-0xfe027fff > irq 16 at device 20.2 on pci0 > hdac1: HDA Driver Revision: 20090329_0131 > hdac1: [ITHREAD] > isab0: at device 20.3 on pci0 > isa0: on isab0 > pcib3: at device 20.4 on pci0 > pci3: on pcib3 > fwohci0: mem > 0xfdcff000-0xfdcff7ff,0xfdcf8000-0xfdcfbfff irq 22 at device 14.0 on pci3 > fwohci0: [FILTER] > fwohci0: OHCI version 1.10 (ROM=0) > fwohci0: No. of Isochronous channels is 4. > fwohci0: EUI64 00:70:c0:59:00:00:1f:d0 > fwohci0: Phy 1394a available S400, 3 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:70:c0:00:1f:d0 > fwe0: Ethernet address: 02:70:c0:00:1f:d0 > fwip0: on firewire0 > fwip0: Firewire address: 00:70:c0:59:00:00:1f:d0 @ 0xfffe00000000, S400, > maxrec 2048 > sbp0: on firewire0 > dcons_crom0: on firewire0 > dcons_crom0: bus_addr 0xb6e80000 > fwohci0: Initiate bus reset > fwohci0: BUS reset > fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode > ohci4: mem 0xfe028000-0xfe028fff irq 18 at > device 20.5 on pci0 > ohci4: [GIANT-LOCKED] > ohci4: [ITHREAD] > usb6: OHCI version 1.0, legacy support > usb6: SMM does not respond, resetting > usb6: on ohci4 > usb6: USB revision 1.0 > uhub6: on usb6 > uhub6: 2 ports with 2 removable, self powered > amdtemp0: on hostb4 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: [FILTER] > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > sio0: [FILTER] > ppc0: port 0x378-0x37f irq 7 on acpi0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppbus0: on ppc0 > ppbus0: [ITHREAD] > plip0: on ppbus0 > plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ppc0: [GIANT-LOCKED] > ppc0: [ITHREAD] > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: [ITHREAD] > psm0: model Generic PS/2 mouse, device ID 0 > cpu0: on acpi0 > powernow0: on cpu0 > cpu1: on acpi0 > powernow1: on cpu1 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio2: configured irq 5 not in bitmap of probed irqs 0 > sio2: port may not be enabled > sio3: configured irq 9 not in bitmap of probed irqs 0 > sio3: port may not be enabled > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > WARNING: ZFS is considered to be an experimental feature in FreeBSD. > Timecounters tick every 1.000 msec > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > firewire0: bus manager 0 (me) > ad4: 238474MB at ata2-master SATA150 > ZFS filesystem version 13 > ZFS storage pool version 13 > ad6: 238475MB at ata3-master SATA150 > ad8: 238475MB at ata4-master SATA150 > acd0: DVDR at ata7-master SATA150 > hdac0: HDA Codec #0: ATI RS690/780 HDMI > pcm0: at cad 0 nid 1 on hdac0 > hdac1: HDA Codec #0: Realtek ALC885 > pcm1: at cad 0 nid 1 on hdac1 > pcm2: at cad 0 nid 1 on hdac1 > pcm3: at cad 0 nid 1 on hdac1 > GEOM_LABEL: Label for provider ad4s1a is ufsid/4895a4a721182022. > GEOM_LABEL: Label for provider ad4s1d is ufsid/4895a4b3b6d4e02e. > GEOM_LABEL: Label for provider ad4s1e is ufsid/4895a4b54799f68b. > GEOM_LABEL: Label for provider ad4s1f is ufsid/4895a4b724bcb48f. > GEOM_LABEL: Label for provider ad4s2a is ufsid/49185b60bbfa4d50. > GEOM_LABEL: Label for provider ad6s1 is ext2fs//. > GEOM_LABEL: Label for provider ad6s2 is ext2fs//1. > GEOM_LABEL: Label for provider ad8s1a is ufsid/4895a498589c3d5f. > GEOM_LABEL: Label for provider ad8s1d is ufsid/4895a48d5fd2f14b. > GEOM_LABEL: Label for provider ad8s1e is ufsid/4895a48489eb6120. > GEOM_LABEL: Label for provider ad8s1f is ufsid/4895a48a019d7151. > GEOM_LABEL: Label for provider ad8s2a is ufsid/4729b57b020c7526. > GEOM_LABEL: Label for provider ad8s2d is ufsid/4729b587458f5554. > GEOM_LABEL: Label for provider ad8s2e is ufsid/4729b58af29c6330. > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad4s2a > GEOM_LABEL: Label ufsid/49185b60bbfa4d50 removed. > > > > machine# pciconf -lv > hostb0@pci0:0:0:0: class=0x060000 card=0x96001022 chip=0x96001022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > class = bridge > subclass = HOST-PCI > pcib1@pci0:0:1:0: class=0x060400 card=0x96021022 chip=0x96021022 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices (AMD)' > class = bridge > subclass = PCI-PCI > pcib2@pci0:0:10:0: class=0x060400 card=0x96001022 chip=0x96091022 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices (AMD)' > class = bridge > subclass = PCI-PCI > atapci0@pci0:0:17:0: class=0x010601 card=0xb0021458 chip=0x43911002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 SATA Controller [AHCI mode]' > class = mass storage > subclass = SATA > ohci0@pci0:0:18:0: class=0x0c0310 card=0x50041458 chip=0x43971002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI0 Controller' > class = serial bus > subclass = USB > ohci1@pci0:0:18:1: class=0x0c0310 card=0x50041458 chip=0x43981002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI1 Controller' > class = serial bus > subclass = USB > ehci0@pci0:0:18:2: class=0x0c0320 card=0x50041458 chip=0x43961002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB EHCI Controller' > class = serial bus > subclass = USB > ohci2@pci0:0:19:0: class=0x0c0310 card=0x50041458 chip=0x43971002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI0 Controller' > class = serial bus > subclass = USB > ohci3@pci0:0:19:1: class=0x0c0310 card=0x50041458 chip=0x43981002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI1 Controller' > class = serial bus > subclass = USB > ehci1@pci0:0:19:2: class=0x0c0320 card=0x50041458 chip=0x43961002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB EHCI Controller' > class = serial bus > subclass = USB > none0@pci0:0:20:0: class=0x0c0500 card=0x43851458 chip=0x43851002 > rev=0x3a hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'ATI SMBus (ATI RD600/RS600)' > class = serial bus > subclass = SMBus > atapci1@pci0:0:20:1: class=0x01018a card=0x50021458 chip=0x439c1002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'PATA 133 Controller (SB7xx)' > class = mass storage > subclass = ATA > hdac1@pci0:0:20:2: class=0x040300 card=0xa0021458 chip=0x43831002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'IXP SB600 High Definition Audio Controller' > class = multimedia > subclass = HDA > isab0@pci0:0:20:3: class=0x060100 card=0x43831002 chip=0x439d1002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 LPC host controller' > class = bridge > subclass = PCI-ISA > pcib3@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 > rev=0x00 hdr=0x01 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'IXP SB600 PCI to PCI Bridge' > class = bridge > subclass = PCI-PCI > ohci4@pci0:0:20:5: class=0x0c0310 card=0x50041458 chip=0x43991002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'SB700 USB OHCI2 Controller' > class = serial bus > subclass = USB > hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) HyperTransport > Technology Configuration' > class = bridge > subclass = HOST-PCI > hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) Address Map' > class = bridge > subclass = HOST-PCI > hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) DRAM Controller' > class = bridge > subclass = HOST-PCI > hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon64/Opteron/Sempron (K8 Family) Miscellaneous Control' > class = bridge > subclass = HOST-PCI > vgapci0@pci0:1:5:0: class=0x030000 card=0xd0001458 chip=0x96101002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'Radeon HD 3200 Integrated Graphics Processor (780G)' > class = display > subclass = VGA > hdac0@pci0:1:5:1: class=0x040300 card=0x960f1002 chip=0x960f1002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > class = multimedia > subclass = HDA > re0@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x02 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111)' > class = network > subclass = ethernet > fwohci0@pci0:3:14:0: class=0x0c0010 card=0x10001458 chip=0x8024104c > rev=0x00 hdr=0x00 > vendor = 'Texas Instruments (TI)' > device = 'TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller' > class = serial bus > subclass = FireWire > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" -- Robert Noland FreeBSD From thierry at herbelot.com Tue Aug 25 20:31:19 2009 From: thierry at herbelot.com (Thierry Herbelot) Date: Tue Aug 25 20:31:37 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <1251230025.45706.280.camel@balrog.2hip.net> References: <4A9412ED.6080309@freebsd.org> <200908252127.48214.thierry.herbelot@free.fr> <1251230025.45706.280.camel@balrog.2hip.net> Message-ID: <200908252214.22667.thierry@herbelot.com> Le Tuesday 25 August 2009, Robert Noland a ?crit : > On Tue, 2009-08-25 at 21:27 +0200, Thierry Herbelot wrote: > > Le Tuesday 25 August 2009, Sam Fourman Jr. a ?crit : > > > > Meanwhile, if you interested in any information about this > > > > motherboard - data dumps, outputs from tools, etc - please let me > > > > know, I will try my best to provide that. > > > > > > it would be interesting to see a dmesg as a starting point. > > > > here you are ;-) > > > > I have plugged a PCI sound board in the machine, but it does seem to be > > detected (there could be some issue with PCI bus enumeration : I also > > include a pciconf log) > > I'm curious why you would plug in a pci sound card? You already have > both a standard hda codec as well as the hda codec for the hdmi port of > the video. If you are discovering that it isn't working... set Initially, this was the issue, before other people sent various howtos around the probe of the hdmi hda port (which by the way sounds *much* better than my previous cmi board). Afterwards, the PCI board remained in the machine (leftover from a previous box), but it is still *not* seen by the PCI enumeration (I'm a bit too lazy to find another spare PCI board and plug it in see what happens : is it also ignored by the BIOS/ACPI/whatever and/or the kernel ?). It seems that it is not either detected by a Linux kernel. TfH > hw.snd.default_unit=1 which is typcially your normal analog audio port. > The hdmi port on radeon chips tends to be enumerated before the normal > system codecs, so people tend to think that sound isn't working. > > robert. > From rnoland at FreeBSD.org Tue Aug 25 21:28:23 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Tue Aug 25 21:28:40 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <200908252214.22667.thierry@herbelot.com> References: <4A9412ED.6080309@freebsd.org> <200908252127.48214.thierry.herbelot@free.fr> <1251230025.45706.280.camel@balrog.2hip.net> <200908252214.22667.thierry@herbelot.com> Message-ID: <1251235695.45706.375.camel@balrog.2hip.net> On Tue, 2009-08-25 at 22:14 +0200, Thierry Herbelot wrote: > Le Tuesday 25 August 2009, Robert Noland a ?crit : > > On Tue, 2009-08-25 at 21:27 +0200, Thierry Herbelot wrote: > > > Le Tuesday 25 August 2009, Sam Fourman Jr. a ?crit : > > > > > Meanwhile, if you interested in any information about this > > > > > motherboard - data dumps, outputs from tools, etc - please let me > > > > > know, I will try my best to provide that. > > > > > > > > it would be interesting to see a dmesg as a starting point. > > > > > > here you are ;-) > > > > > > I have plugged a PCI sound board in the machine, but it does seem to be > > > detected (there could be some issue with PCI bus enumeration : I also > > > include a pciconf log) > > > > I'm curious why you would plug in a pci sound card? You already have > > both a standard hda codec as well as the hda codec for the hdmi port of > > the video. If you are discovering that it isn't working... set > > Initially, this was the issue, before other people sent various howtos around > the probe of the hdmi hda port (which by the way sounds *much* better than my > previous cmi board). > > Afterwards, the PCI board remained in the machine (leftover from a previous > box), but it is still *not* seen by the PCI enumeration (I'm a bit too lazy > to find another spare PCI board and plug it in see what happens : is it also > ignored by the BIOS/ACPI/whatever and/or the kernel ?). > > It seems that it is not either detected by a Linux kernel. Perhaps it isn't seated properly? Or possibly a different slot might help. robert. > TfH > > > hw.snd.default_unit=1 which is typcially your normal analog audio port. > > The hdmi port on radeon chips tends to be enumerated before the normal > > system codecs, so people tend to think that sound isn't working. > > > > robert. > > -- Robert Noland FreeBSD From sfourman at gmail.com Tue Aug 25 21:59:20 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Tue Aug 25 21:59:26 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <4A9412ED.6080309@freebsd.org> References: <4A9412ED.6080309@freebsd.org> Message-ID: <11167f520908251459r7477fac3kdf3ff6e603a313dd@mail.gmail.com> On Tue, Aug 25, 2009 at 11:35 AM, Andriy Gapon wrote: > > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H > It is based on AMD 780G + SB700. > BTW, CPU I am using is Athlon II X2 250. are you using a i386 or AMD64 kernel? maybe I am blind but I didnt see it in your dmesg Sam Fourman Jr. From bernt at bah.homeip.net Tue Aug 25 22:06:15 2009 From: bernt at bah.homeip.net (Bernt Hansson) Date: Tue Aug 25 22:06:27 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <4A9412ED.6080309@freebsd.org> References: <4A9412ED.6080309@freebsd.org> Message-ID: <4A945DC1.8070202@bah.homeip.net> Andriy Gapon said the following on 2009-08-25 18:35: > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H > It is based on AMD 780G + SB700. > BTW, CPU I am using is Athlon II X2 250. > > Sorry for the broadcast announcement, but this is my first AMD-based system in > many years, so I eagerly started exploring it and hacking for it. > > For this reason please expect a number of questions from me as well as some > reports and hopefully code related to this motherboard. I am going to post them as > follow-ups to this email. > > Meanwhile, if you interested in any information about this motherboard - data > dumps, outputs from tools, etc - please let me know, I will try my best to provide > that. > It would be interesting to know if you can have usb devices connected and detected during boot. With SB600 you can not. From thierry at herbelot.com Wed Aug 26 04:11:08 2009 From: thierry at herbelot.com (Thierry Herbelot) Date: Wed Aug 26 04:11:15 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <4A945DC1.8070202@bah.homeip.net> References: <4A9412ED.6080309@freebsd.org> <4A945DC1.8070202@bah.homeip.net> Message-ID: <200908260610.45849.thierry@herbelot.com> Le Tuesday 25 August 2009, Bernt Hansson a ?crit : > Andriy Gapon said the following on 2009-08-25 18:35: > > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassV > >alue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H It is based on > > AMD 780G + SB700. > > BTW, CPU I am using is Athlon II X2 250. > > > > Sorry for the broadcast announcement, but this is my first AMD-based > > system in many years, so I eagerly started exploring it and hacking for > > it. > > > > For this reason please expect a number of questions from me as well as > > some reports and hopefully code related to this motherboard. I am going > > to post them as follow-ups to this email. > > > > Meanwhile, if you interested in any information about this motherboard - > > data dumps, outputs from tools, etc - please let me know, I will try my > > best to provide that. > > It would be interesting to know if you can have usb devices connected > and detected during boot. With SB600 you can not. This maybe the explanation why I have to re-plug the USB mouse each time the machine is restarted ;-) (with an SB700) TfH From mureninc at gmail.com Wed Aug 26 05:07:13 2009 From: mureninc at gmail.com (Constantine A. Murenin) Date: Wed Aug 26 05:07:20 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <200908260610.45849.thierry@herbelot.com> References: <4A9412ED.6080309@freebsd.org> <4A945DC1.8070202@bah.homeip.net> <200908260610.45849.thierry@herbelot.com> Message-ID: On 26/08/2009, Thierry Herbelot wrote: > Le Tuesday 25 August 2009, Bernt Hansson a ?crit : > > > Andriy Gapon said the following on 2009-08-25 18:35: > > > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > > > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassV > > >alue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H It is based on > > > AMD 780G + SB700. > > > BTW, CPU I am using is Athlon II X2 250. > > > > > > Sorry for the broadcast announcement, but this is my first AMD-based > > > system in many years, so I eagerly started exploring it and hacking for > > > it. > > > > > > For this reason please expect a number of questions from me as well as > > > some reports and hopefully code related to this motherboard. I am going > > > to post them as follow-ups to this email. > > > > > > Meanwhile, if you interested in any information about this motherboard - > > > data dumps, outputs from tools, etc - please let me know, I will try my > > > best to provide that. > > > > It would be interesting to know if you can have usb devices connected > > and detected during boot. With SB600 you can not. > > > This maybe the explanation why I have to re-plug the USB mouse each time the > machine is restarted ;-) (with an SB700) FYI: My rum(4) on GA-MA78GM-S2H (780G / SB700) is always detected by OpenBSD without having to be re-plugged, so this must be a FreeBSD driver issue. C. From avg at freebsd.org Wed Aug 26 08:46:10 2009 From: avg at freebsd.org (Andriy Gapon) Date: Wed Aug 26 08:46:16 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <4A945DC1.8070202@bah.homeip.net> References: <4A9412ED.6080309@freebsd.org> <4A945DC1.8070202@bah.homeip.net> Message-ID: <4A94F649.6010804@freebsd.org> on 26/08/2009 00:55 Bernt Hansson said the following: > It would be interesting to know if you can have usb devices connected > and detected during boot. With SB600 you can not. Yes, this works perfectly with USB thumb drive. -- Andriy Gapon From avg at freebsd.org Wed Aug 26 08:53:42 2009 From: avg at freebsd.org (Andriy Gapon) Date: Wed Aug 26 08:54:00 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> References: <4A9412ED.6080309@freebsd.org> <11167f520908251134u7454267fl7a4e1e4657405a6f@mail.gmail.com> Message-ID: <4A94F811.8020705@freebsd.org> on 25/08/2009 21:34 Sam Fourman Jr. said the following: >> Meanwhile, if you interested in any information about this motherboard - data >> dumps, outputs from tools, etc - please let me know, I will try my best to provide >> that. > > it would be interesting to see a dmesg as a starting point. Please see http://people.freebsd.org/~avg/ga-ma780g-ud3h/ Replying to the other email - I use amd64 arch. -- Andriy Gapon From mav at FreeBSD.org Wed Aug 26 21:06:26 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Wed Aug 26 21:06:32 2009 Subject: Small SATA performance contest Message-ID: <4A95A3CA.3060306@FreeBSD.org> I've just made several tests, comparing older SATA 1.x SiI3114 (32bit/66MHz PCIX), newer SATA 2.x JMicron JMB363 and SiI3132 (PCIe x1) cards and on-board ICH8 AHCI with two fast drives connected to each: Linear read with 1MB block from two drives, summary: SiI3114 in PCI 32/33 slot: 120MB/s. SiI3114 in PCIX 32/66 slot: 190MB/s. <-- near to SATA 1.x limit SiI3132 in PCIe x1 slot: 150MB/s JMB363 in PCIe x1 slot: 188MB/s ICH8 AHCI on-board: 310MB/s <-- drives limit So, faster bus can be a significant bonus even to old card. Inefficient design can kill even new bus. Same time fastest internal connections of ICH8, combined with effective design can give unique results. Linear read with 512B block: SiI3114 in PCIX 32/66 slot: 16Ktps. SiI3132 in PCIe x1 slot: 17Ktps ICH8 AHCI on-board: 17Ktps 10 streams linear reads with 512B block: SiI3114 in PCIX 32/66 slot: 10Ktps. SiI3132 in PCIe x1 slot: 25Ktps ICH8 AHCI on-board: 25Ktps But even slower newer card can win in some situations, just because of additional functionality, such as command queuing in this case. -- Alexander Motin From wjw at withagen.nl Fri Aug 28 19:34:31 2009 From: wjw at withagen.nl (Willem Jan Withagen) Date: Fri Aug 28 19:34:39 2009 Subject: enable ECC in OS code? In-Reply-To: <864ort1lw0.fsf@ds4.des.no> References: <200908262253.n7QMrauP063683@wattres.watt.com> <200908271130.18073.erich@apsara.com.sg> <20090827112229.GB14987@britannica.bec.de> <864ort1lw0.fsf@ds4.des.no> Message-ID: <4A983147.8080906@withagen.nl> Dag-Erling Sm?rgrav wrote: > Joerg Sonnenberger writes: >> Erich Dollansky writes: >>> how should it be done at OS level at all when the OS is loaded >>> into RAM? >> Copy the kernel to the video RAM, jump to it, enable ECC, copy back. > > Not just the kernel - you have to copy all the memory that is currently > in use, including interrupt tables, the BIOS configuration space, shadow > copies of various ROMs... The CPU will probably not look too kindly on > having interrupt descriptors, segment descriptors, page tables etc. in > memory accessed through the I/O controller instead of the memory > controller. > > The machine might not even have video RAM! > > On systems that support ECC, I suspect that the BIOS enables it at the > same time as it configures the memory controller, which is one of the > very first things it does - literally within a few dozen (or perhaps a > few hundred) instructions from CPU reset - using only CPU registers, ROM > code, and configuration variables loaded from NVRAM. The way we did it when we were building Unix Systems in the 80's is that the output of the EEC checker on the memoryboards was gated to an High Prio Intr of an Open collectorline to the m68k. And that OC had a gate that was only enabled once we were sure that the whole memory had been test written. Remember that usually the memory in extention systems don't have EEC either. This holds for I/O registers, video memory, memory on networkcontrollers etc, unless we build the devices outselves... These memories also connects to the gate to allow access without triggering an EEC error. I have not ever looked into the HW of a current ECC controller but I expect there is a big chance that EEC parity always gets written. Not doing so will require extra gates in an already too long path from the XOR devices to the ECC cells (Thus reducing the writecycle time). ECC errors will only be flagged if EEC is enabled,but very likely EEC is always tested and/or written. So I would expect it to be "relatively simpele" read/write all the physical memory then enable the ECC intr/trap mechanism. --WjW