Re: Any working ichsmb(4) platforms out there?
On Thu, 11.09.2008 at 15:14:52 +0100, Bruce M Simpson wrote: Does anyone have ichsmb(4) actually seeing SMBus devices? e.g. you run smbmsg -p on your FreeBSD-STABLE system and see something. I just tried it again on my IBM ThinkPad T43 and saw nothing, all I get is: ichsmb0: device timeout, status=0x41 ...in dmesg. No luck with an ICH5, here: ichsmb0: Intel 82801EB (ICH5) SMBus controller port 0x2400-0x241f irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: System Management Bus on ichsmb0 smb0: SMBus generic I/O on smbus0 ichsmb0: device timeout, status=0x41 ichsmb0: device timeout, status=0x41 ichsmb0: device timeout, status=0x41 ichsmb0: device timeout, status=0x41 ... # uname -rsm FreeBSD 6.3-STABLE i386 # devinfo -v|grep smb ichsmb0 pnpinfo vendor=0x8086 device=0x24d3 subvendor=0x1734 subdevice=0x101c class=0x0c0500 at slot=31 function=3 handle=\_SB_.PCI0.PM__ # kenv|grep smb smbios.bios.reldate=11/25/2004 smbios.bios.vendor=FUJITSU SIEMENS // Phoenix Technologies Ltd. smbios.bios.version=5.00 R2.14.1534.01 smbios.chassis.maker=FUJITSU SIEMENS smbios.chassis.serial=YBFC445826 smbios.chassis.tag= smbios.chassis.version=SCEE smbios.planar.maker=FUJITSU SIEMENS smbios.planar.product=D1534 smbios.planar.serial= smbios.planar.version=S26361-D1534 smbios.socket.enabled=1 smbios.socket.populated=1 smbios.system.maker=FUJITSU SIEMENS smbios.system.product=SCENIC E smbios.system.serial=YBFC445826 smbios.system.uuid=93D4A7A3-705F-11D9-8688-00300577E7A0 smbios.system.version= Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: alpm(4) I/O range is claimed by ACPI
On Friday 12 September 2008 10:13:27 pm Bruce M Simpson wrote: John Baldwin wrote: Umm, ACPI will allow children devices to allocate their resources out of the sysresource pool. IPMI has to do this on some systems where ACPI claims the IPMI I/O ports as a system resource. But surely if alpm(4) were to attach to such a range in this way, it would need to be a child of the acpi bus device, yes? No, the code in acpi_alloc_resources() does _not_ check for that. Any child device with a specific allocation that falls in a system resource range will succeed the allocation. The IPMI driver probes for a specific ACPI ID in the DSDT. The IPMI driver also attaches on the isa0 device via the SMBIOS tables, and that is the case where the resources clash with ACPI's system resources. IPMI devices listed in the ACPI namespace don't have their resources listed in ACPI's system resources. PCI ID looks like this: [EMAIL PROTECTED]:0:30:1: class=0x068000 card=0x81561043 chip=0x710110b9 rev=0x00 hdr=0x00 So I grabbed the M1543 datasheet off the web and looked in CSR space. Guess what: the AMI BIOS on the ASUS Vintage AH-1 does NOT set up the PMU. The function is still visible, it just has no active I/O mappings. No wonder alpm(4) does not attach. I tried looking for this device in the DSDT, I don't see anything which obviously resembles it. The equivalent Linux driver has a means of forcing the mapping to be set up if it isn't available: http://www.kernel.org/doc/Documentation/i2c/busses/i2c-ali15x3 It looks like there used to be a means of doing this in the FreeBSD driver but it got nuked. And that ASUS didn't much care about power management support in this machine... If you can re-enable it in such a way that it uses bus_alloc_resource(), then the driver will probably work fine. Oh well! I know ichsmb works on at least one machine that I have. cheers BMS -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 7.1-BETA/6.4-BETA Available...
The FreeBSD 7.1-BETA and 6.4-BETA builds are now available on the
FreeBSD FTP mirror sites. This is the first step in the release process
for FreeBSD-7.1 and FreeBSD-6.4. This set of builds do not include
pre-built packages. The ISOs are available from:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/7.1/
ftp://ftp.freebsd.org/pub/FreeBSD/releases/${arch}/ISO-IMAGES/6.4/
where $arch is one of alpha, amd64, i386, ia64, pc98, powerpc, or
sparc64. For the Tier-2 architectures ia64 and powerpc only the
7.1-BETA builds are available. For the Tier-2 architecture alpha only
the 6.4-BETA builds are available.
We encourage people to help out with the testing. Problems can be
reported through Gnats or on the freebsd-stable@freebsd.org mailing
list. At this point we expect the 6.4-RC1 builds to start in about two
weeks, and the 7.1-RC1 builds a week after that.
Checksums for the ISOs:
MD5 (6.4-BETA-alpha-bootonly.iso) = 3e222422a6c029b8b1922dbbfeb4b040
MD5 (6.4-BETA-alpha-disc1.iso) = 94a7df84eaa9111ee34ab849c9211560
MD5 (6.4-BETA-alpha-docs.iso) = 8a4606e35db9c2dc0ae1b6a6ea17eed2
SHA256 (6.4-BETA-alpha-bootonly.iso) =
f11dcdf0d8eb549a273ac15ce4b2434a4ac90990565d8bd45f1901b01a818936
SHA256 (6.4-BETA-alpha-disc1.iso) =
244b65286c8c8c6b7270320506eb2fd233f0cf4ca968613384496aa10a706f75
SHA256 (6.4-BETA-alpha-docs.iso) =
49d753dfb3cfd80b137b2b10f34e30799a0765e03561863279de420119f02333
MD5 (7.1-BETA-amd64-bootonly.iso) = 72fdf9c01667c99bb6153101b188122d
MD5 (7.1-BETA-amd64-disc1.iso) = 87f7e93ca707b08a08accf989ff7060b
MD5 (7.1-BETA-amd64-disc2.iso) = 707fdd5281a66268eb72fa975caeada5
MD5 (7.1-BETA-amd64-disc3.iso) = cc100e18c8790d66fe192e7f71f4e5aa
MD5 (7.1-BETA-amd64-docs.iso) = 98e21ba5a44912fbf9dcdc4b8cf23a7a
MD5 (7.1-BETA-amd64-livefs.iso) = e9a4a8c20db73408990c70fdac3c3d22
SHA256 (7.1-BETA-amd64-bootonly.iso) =
ec9054b879cf154e553776233c3bbe31e93c613778e1d107897528d1f63cf4fb
SHA256 (7.1-BETA-amd64-disc1.iso) =
b3ddcab735c4ea3f096d92d212940216859bbd47403896eb2e741d5ad2db6d7c
SHA256 (7.1-BETA-amd64-disc2.iso) =
b9ffb599f849a3ba8d2354c847d7c9715e954f2d1aa179a530238ee462ca8014
SHA256 (7.1-BETA-amd64-disc3.iso) =
c8b9d99239481339001aeda45c06104ccfa93e6e11f682fff054c30e612106aa
SHA256 (7.1-BETA-amd64-docs.iso) =
e92d6c5858aa540588775d2eb3708e3fc85078ddaba860c5c2704523a54728cb
SHA256 (7.1-BETA-amd64-livefs.iso) =
fb733dbdd3c755215e80678706a76963254decff6800d3b2adde4b55e90dee59
MD5 (6.4-BETA-amd64-bootonly.iso) = ac3b2b39cd8c875be4dbc7a7ccbcce24
MD5 (6.4-BETA-amd64-disc1.iso) = ec5c1df7a0b4be9a8f5ecdd1d23d1209
MD5 (6.4-BETA-amd64-disc2.iso) = 37e54556eabf8df7514aecc7134b53b3
MD5 (6.4-BETA-amd64-disc3.iso) = 636fded834831e7f60a75f83537b30a7
MD5 (6.4-BETA-amd64-docs.iso) = 2e435bcc934600fb1ddedf0102c70e01
SHA256 (6.4-BETA-amd64-bootonly.iso) =
e13fe3e4b8c7fab0d433e38fdf5de27bf8ffdfa996d3b6c68459a8fda7100a9a
SHA256 (6.4-BETA-amd64-disc1.iso) =
a6a8dbfaf34d404058e0a62dce29526d30d86a15aca1c46521e01d976b36d651
SHA256 (6.4-BETA-amd64-disc2.iso) =
58470a464d57658aaf5b7c5783684a20b64d0078c1007b50a332efdf1ce761a9
SHA256 (6.4-BETA-amd64-disc3.iso) =
af3e2447b87a97c78f4e59fc3f083ceaeaa9f4c3e466411d55250d9a354d6d6d
SHA256 (6.4-BETA-amd64-docs.iso) =
009292acad493678e540c9209407df7b63dfaf689f35b04cb846fbdbba4b801c
MD5 (7.1-BETA-i386-bootonly.iso) = a3885274226f96f21ddf22b3047c858d
MD5 (7.1-BETA-i386-disc1.iso) = f06c2453309e001cd67f72bb954a4b4a
MD5 (7.1-BETA-i386-disc2.iso) = 38cfeeb16db98c37189336f055b41756
MD5 (7.1-BETA-i386-disc3.iso) = af70d157f064e39bf790505f185e565f
MD5 (7.1-BETA-i386-docs.iso) = 23adf38460f2f1febaa58c294f03b120
MD5 (7.1-BETA-i386-livefs.iso) = 26d91e9a60243db9e28113a391d80e8f
SHA256 (7.1-BETA-i386-bootonly.iso) =
87eba44221e41a0928bc3ebdd753e28c3c66315fc58954a3a79b261dee94cc5a
SHA256 (7.1-BETA-i386-disc1.iso) =
096ad85048a660684731ec4fd1f4a384ae4a76c3256726dfb61b4a4d8213d107
SHA256 (7.1-BETA-i386-disc2.iso) =
22a6207200978cafee5aa186275e1e0b60fc8f8a75f1351a1377a5f3bca14b76
SHA256 (7.1-BETA-i386-disc3.iso) =
e4241590f10315be2e1b4b51e36d882e287d97654f5a9e13f9089ade87a91541
SHA256 (7.1-BETA-i386-docs.iso) =
c2caa0a0d2151866c7b24f49944dab55cede84b209dfd2036e4745dc7b89b9e9
SHA256 (7.1-BETA-i386-livefs.iso) =
eef80a184b5b2d1d2504dd80e2ca000612b8a0139e059cbe12c7122774159537
MD5 (6.4-BETA-i386-bootonly.iso) = f71aeb1bfc51ce9c744eebf9e542c52a
MD5 (6.4-BETA-i386-disc1.iso) = 3710f169c1b29d9aee64b883ba7ae481
MD5 (6.4-BETA-i386-disc2.iso) = 8959ecb31dd11a635dc8758bfa8b37a7
MD5 (6.4-BETA-i386-disc3.iso) = fa95fc7842598e00a4d7ff853e406dfc
MD5 (6.4-BETA-i386-docs.iso) = 3a95e60589bef780e2166adeed0e
SHA256 (6.4-BETA-i386-bootonly.iso) =
00fba46869644b4ac52bc7ec4b69b2d5bbe17a9ff423d4e1d899f59bc824bb80
SHA256 (6.4-BETA-i386-disc1.iso) =
dba12bb568328e284cd75ff9f6b69fb52a7ec34be9a38c3c0be1d44adf8f9dcf
SHA256 (6.4-BETA-i386-disc2.iso) =
52dd575e05bdf4626a5353329e7a92d9e2f8562640df3b82d21cedda86d86640
SHA256 (6.4-BETA-i386-disc3.iso) =
ipfw uid regression
I've updated from 7.0 to RELENG_7 today. ipfw uid rules have caused problems in the past with PREEMPTION enabled. This was fixed in 7.0, at least for me. In RELENG_7 the old problems are back: Total freeze within some seconds/minutes after the first network access. With WITNESS I get a LOR, see at the end of dmesg. Copyright (c) 1992-2008 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.1-PRERELEASE #58: Sat Sep 13 19:38:47 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TAXMAN WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) XP 2700+ (2166.44-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x681 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc0400800SYSCALL,MMX+,3DNow!+,3DNow! real memory = 1073725440 (1023 MB) avail memory = 1032847360 (985 MB) ACPI APIC Table: ASUS A7V8X-X ioapic0: Changing APIC ID to 2 ioapic0 Version 0.3 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: ASUS A7V8X-X on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display mem 0xd700-0xd7ff,0xe000-0xefff,0xd600-0xd6ff irq 16 at device 0.0 on pci1 nvidia0: GeForce 6200 on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] pcm0: Envy24 audio (M Audio Audiophile 2496) port 0xd800-0xd81f,0xd400-0xd40f,0xd000-0xd00f,0xb800-0xb83f irq 16 at device 13.0 on pci0 pcm0: [ITHREAD] pcm0: system configuration SubVendorID: 0x1412, SubDeviceID: 0xd634 XIN2 Clock Source: 22.5792MHz(44.1kHz*512) MPU-401 UART(s) #: 1 AC'97 codec: not exist ADC #: 1 DAC #: 1 Multi-track converter type: I2S(96KHz support, 24bit resolution, ID#0x2) S/PDIF(IN/OUT): 1/1 ID# 0x00 GPIO(mask/dir/state): 0x04/0xfb/0xfe pci0: multimedia, video at device 15.0 (no driver attached) uhci0: VIA 83C572 USB controller port 0xb400-0xb41f at device 16.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xb000-0xb01f at device 16.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: VIA 83C572 USB controller port 0xa800-0xa81f at device 16.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: VIA VT6202 USB 2.0 controller mem 0xd580-0xd58000ff at device 16.3 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: VIA VT6202 USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb3 uhub3: 6 ports with 6 removable, self powered isab0: PCI-ISA bridge at device 17.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 8235 UDMA133 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xa400-0xa40f at device 17.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] vr0: VIA VT6102 Rhine II 10/100BaseTX port 0xa000-0xa0ff mem 0xd500-0xd5ff at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x74 miibus0: MII bus on vr0 rlphy0: RTL8201L 10/100 media interface PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:0e:a6:40:3f:d0 vr0: [ITHREAD] cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 fdc0: floppy drive controller port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xd-0xd5fff pnpid ORM on isa0 sc0: System console at flags 0x100 on isa0
