Nabble - freebsd-hardware

Re: kern/139654: CD-boot failure on newer IBM server

2009-12-10T07:45:43Z

John Baldwin wrote:

> On Wednesday 09 December 2009 10:02:21 am Charles Owens wrote:
>> Charles Owens wrote:
>>> Hello,
>>>
>>> As detailed in the PR, we are unable to get FreeBSD (7.1) to boot with
>>> an IBM System x3250 M2 server. I'm not sure what steps to take next,
>>> and would greatly appreciate assistance.
>>>
>>> We've also submitted kern/139653 which deal with different hardware (HP)
>>> and is not quite as critical (very poor performance, as opposed to
>>> complete failure)... any suggestions with this also welcome.
>>>
>>> PR links:
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139654
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139653
>>
>> Tying up this loose thread... PR kern/139654 turns out to be duplicate
>> of kern/103602. Patch in PR from Alexander Motin (mav@) appears to
>> resolve our issue (works fine in 7.1 but must be applied by hand). Our
>> thanks to him for his generous support.
>
> Does the same patch address 139653 at all?
>

As yet unknown. We'll be testing this case shortly. Thanks.

Charles Owens
Great Bay Software, Inc.

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: kern/139654: CD-boot failure on newer IBM server

2009-12-10T05:32:51Z

On Wednesday 09 December 2009 10:02:21 am Charles Owens wrote:

> Charles Owens wrote:
> > Hello,
> >
> > As detailed in the PR, we are unable to get FreeBSD (7.1) to boot with
> > an IBM System x3250 M2 server. I'm not sure what steps to take next,
> > and would greatly appreciate assistance.
> >
> > We've also submitted kern/139653 which deal with different hardware (HP)
> > and is not quite as critical (very poor performance, as opposed to
> > complete failure)... any suggestions with this also welcome.
> >
> > PR links:
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139654
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139653
>
>
> Tying up this loose thread... PR kern/139654 turns out to be duplicate
> of kern/103602. Patch in PR from Alexander Motin (mav@) appears to
> resolve our issue (works fine in 7.1 but must be applied by hand). Our
> thanks to him for his generous support.

Does the same patch address 139653 at all?

--
John Baldwin
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: kern/139654: CD-boot failure on newer IBM server

2009-12-09T06:58:51Z

Charles Owens wrote:

> Hello,
>
> As detailed in the PR, we are unable to get FreeBSD (7.1) to boot with
> an IBM System x3250 M2 server. I'm not sure what steps to take next,
> and would greatly appreciate assistance.
>
> We've also submitted kern/139653 which deal with different hardware (HP)
> and is not quite as critical (very poor performance, as opposed to
> complete failure)... any suggestions with this also welcome.
>
> PR links:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139654
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/139653

Tying up this loose thread... PR kern/139654 turns out to be duplicate
of kern/103602. Patch in PR from Alexander Motin (mav@) appears to
resolve our issue (works fine in 7.1 but must be applied by hand). Our
thanks to him for his generous support.

Charles Owens
Great Bay Software, Inc.

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Can you recommend a scanner for normal use?

2009-12-09T00:39:14Z

Hello list.

I've used a friends Epson Perfection 2450 scanner with sane with good
results. Unfortunately the scanner has broken down and I'm looking for a
new scanner.

I'm often scanning invoices, this is my main use at the moment. I do
scan pictures as well and I have a plan to scan all my negatives to have
them digitally to preserve quality. I'm open to any suggestions of brand
and function. I focus on Epson because I'm currently of the opinion that
it's good value for the money

The 2450 is not in the market any longer so a new model must be chosen.
The 4990 would be nice but I can't find it at my dealer. The 4490 can be
found but it's not supported by SANE!

I can see that the Epson Perfection V700 Photo and Epson Perfection V750
Photo has good support in SANE. But it's not described what's not working?

How about the Epson Perfection V500 Photo and Epson Perfection V600 Photo?

I've asked this on the sane mailing list but I got no answers. I hope
that someone here will suggest a good solution that works well on FreeBSD.

Any feedback welcome. Thank you :-)

/Leslie
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: USB bus setup error with PAE (was USB keyboard flaky with PAE kernel, 7.1)

2009-12-02T07:59:51Z

John Baldwin wrote:

> On Tuesday 01 December 2009 2:20:32 pm Charles Owens wrote:
>
>> Charles Owens wrote:
>>
>>> Howdy,
>>>
>>> I'm still digging into it, put preliminary testing is showing that
>>> with a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only
>>> occasionally, if you're lucky. This flakiness is being seen with
>>> several different server models that we support (HP and IBM, all Xeon
>>> based). If we boot a non-PAE kernel then the USB keyboard is rock solid.
>>>
>> My initial report was entirely too broad --- an unrelated problem was
>> confusing things. I can now report that this problem appears limited to
>> only the IBM System x3550 M2. With a PAE-enabled kernel initialization
>> of some of the USB buses fails. From an external perspective, this
>> results in the rear USB port being non-functional, while the two front
>> USB ports work fine. For some reason, though, when booting the same PAE
>> kernel from a CD none of the USB ports function.
>>
>> In previous posting (
>> http://docs.freebsd.org/cgi/mid.cgi?4B0D14CB.1010000 ) I included output
>> of usbdevs and boot log when running the PAE-enabled kernel. Note the
>> "root hub error" messages in boot log.
>>
>> Below I'll repeat the same info when running a non-PAE kernel.
>>
>> Any thoughts as to what the story is here... and suggestions for
>> resolution? Thanks in advance.
>>
>
> Would you be able to test an 8.0 kernel with PAE enabled? 8.0 has a
> completely rewritten USB stack, so there is a chance that the bug in 7 might
> not be present in 8. You can also try posting on freebsd-usb@ since the folks
> working on the USB drivers tend to hang out on that list.
>

Good suggestions... I'll proceed with both. Thanks,

Charles

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: USB bus setup error with PAE (was USB keyboard flaky with PAE kernel, 7.1)

2009-12-02T06:43:15Z

On Tuesday 01 December 2009 2:20:32 pm Charles Owens wrote:

> Charles Owens wrote:
> > Howdy,
> >
> > I'm still digging into it, put preliminary testing is showing that
> > with a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only
> > occasionally, if you're lucky. This flakiness is being seen with
> > several different server models that we support (HP and IBM, all Xeon
> > based). If we boot a non-PAE kernel then the USB keyboard is rock solid.
>
> My initial report was entirely too broad --- an unrelated problem was
> confusing things. I can now report that this problem appears limited to
> only the IBM System x3550 M2. With a PAE-enabled kernel initialization
> of some of the USB buses fails. From an external perspective, this
> results in the rear USB port being non-functional, while the two front
> USB ports work fine. For some reason, though, when booting the same PAE
> kernel from a CD none of the USB ports function.
>
> In previous posting (
> http://docs.freebsd.org/cgi/mid.cgi?4B0D14CB.1010000 ) I included output
> of usbdevs and boot log when running the PAE-enabled kernel. Note the
> "root hub error" messages in boot log.
>
> Below I'll repeat the same info when running a non-PAE kernel.
>
> Any thoughts as to what the story is here... and suggestions for
> resolution? Thanks in advance.

Would you be able to test an 8.0 kernel with PAE enabled? 8.0 has a
completely rewritten USB stack, so there is a chance that the bug in 7 might
not be present in 8. You can also try posting on freebsd-usb@ since the folks
working on the USB drivers tend to hang out on that list.

--
John Baldwin
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

USB bus setup error with PAE (was USB keyboard flaky with PAE kernel, 7.1)

2009-12-01T11:17:22Z

Charles Owens wrote:
> Howdy,
>
> I'm still digging into it, put preliminary testing is showing that
> with a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only
> occasionally, if you're lucky. This flakiness is being seen with
> several different server models that we support (HP and IBM, all Xeon
> based). If we boot a non-PAE kernel then the USB keyboard is rock solid.

My initial report was entirely too broad --- an unrelated problem was
confusing things. I can now report that this problem appears limited to
only the IBM System x3550 M2. With a PAE-enabled kernel initialization
of some of the USB buses fails. From an external perspective, this
results in the rear USB port being non-functional, while the two front
USB ports work fine. For some reason, though, when booting the same PAE
kernel from a CD none of the USB ports function.

In previous posting (
http://docs.freebsd.org/cgi/mid.cgi?4B0D14CB.1010000 ) I included output
of usbdevs and boot log when running the PAE-enabled kernel. Note the
"root hub error" messages in boot log.

Below I'll repeat the same info when running a non-PAE kernel.

Any thoughts as to what the story is here... and suggestions for
resolution? Thanks in advance.

[root@dmz55 /usr/home/muck]# usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
port 1 powered
port 2 addr 2: low speed, power 100 mA, config 1, Comfort Curve Keyboard 2000(0x00dd), Microsoft(0x045e), rev 1.73
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb2:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
port 3 powered
port 4 powered
port 5 powered
port 6 powered
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
port 1 powered
port 2 addr 2: full speed, power 100 mA, config 1, RNDIS/CDC ETHER(0x4010), IBM(0x04b3), rev 2.15
Controller /dev/usb4:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb5:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb6:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00
port 1 addr 2: high speed, power 2 mA, config 2, IBM Composite Device-0(0x4012), IBM(0x04b3), rev 0.00
port 2 powered
port 3 powered
port 4 powered
port 5 powered
port 6 addr 3: high speed, power 450 mA, config 1, product 0x1a00(0x1a00), vendor 0x2001(0x2001), rev 10.01

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.1-RELEASE-p8 #0: Wed Nov 18 11:22:57 EST 2009
muck@...:/usr/obj/usr/src/sys/DMZ55
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (2000.08-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x106a5 Stepping = 5
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x9ce3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT>
AMD Features=0x28100000<NX,RDTSCP,LM>
AMD Features2=0x1<LAHF>
Cores per package: 8
Logical CPUs per core: 2
real memory = 2137583616 (2038 MB)
avail memory = 2081480704 (1985 MB)
ACPI APIC Table: <IBM THURLEY >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 2
cpu2 (AP): APIC ID: 4
cpu3 (AP): APIC ID: 6
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <IBM THURLEY> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "HPET" frequency 14318180 Hz quality 900
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x588-0x58b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 28 at device 1.0 on pci0
pci11: <ACPI PCI bus> on pcib1
pci11: <network, ethernet> at device 0.0 (no driver attached)
pci11: <network, ethernet> at device 0.1 (no driver attached)
pcib2: <PCI-PCI bridge> irq 29 at device 2.0 on pci0
pci16: <PCI bus> on pcib2
pci16: <network, ethernet> at device 0.0 (no driver attached)
pci16: <network, ethernet> at device 0.1 (no driver attached)
pcib3: <ACPI PCI-PCI bridge> irq 24 at device 3.0 on pci0
pci21: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 30 at device 7.0 on pci0
pci26: <ACPI PCI bus> on pcib4
pci0: <base peripheral, interrupt controller> at device 16.0 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 16.1 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 17.0 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 17.1 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.0 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.1 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.2 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.3 (no driver attached)
pci0: <base peripheral> at device 22.0 (no driver attached)
pci0: <base peripheral> at device 22.1 (no driver attached)
pci0: <base peripheral> at device 22.2 (no driver attached)
pci0: <base peripheral> at device 22.3 (no driver attached)
pci0: <base peripheral> at device 22.4 (no driver attached)
pci0: <base peripheral> at device 22.5 (no driver attached)
pci0: <base peripheral> at device 22.6 (no driver attached)
pci0: <base peripheral> at device 22.7 (no driver attached)
uhci0: <UHCI (generic) USB controller> port 0x20a0-0x20bf irq 17 at device 26.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0x2080-0x209f irq 18 at device 26.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0x9ba21400-0x9ba217ff irq 19 at device 26.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: wrong number of companions (3 != 2)
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 6 ports with 6 removable, self powered
pcib5: <PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci1: <PCI bus> on pcib5
mpt0: <LSILogic SAS/SATA Adapter> port 0x1000-0x10ff mem 0x9b910000-0x9b913fff,0x9b900000-0x9b90ffff irq 16 at device 0.0 on pci1
mpt0: [ITHREAD]
mpt0: MPI Version=1.5.20.0
mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 )
mpt0: 0 Active Volumes (2 Max)
mpt0: 0 Hidden Drive Members (14 Max)
pcib6: <PCI-PCI bridge> irq 16 at device 28.4 on pci0
pci6: <PCI bus> on pcib6
pcib7: <PCI-PCI bridge> irq 16 at device 0.0 on pci6
pci7: <PCI bus> on pcib7
vgapci0: <VGA-compatible display> mem 0x9a000000-0x9affffff,0x9b800000-0x9b803fff,0x9b000000-0x9b7fffff irq 16 at device 0.0 on pci7
uhci2: <UHCI (generic) USB controller> port 0x2060-0x207f irq 17 at device 29.0 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb3: <UHCI (generic) USB controller> on uhci2
usb3: USB revision 1.0
uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
uhci3: <UHCI (generic) USB controller> port 0x2040-0x205f irq 18 at device 29.1 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb4: <UHCI (generic) USB controller> on uhci3
usb4: USB revision 1.0
uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
uhci4: <UHCI (generic) USB controller> port 0x2020-0x203f irq 19 at device 29.2 on pci0
uhci4: [GIANT-LOCKED]
uhci4: [ITHREAD]
usb5: <UHCI (generic) USB controller> on uhci4
usb5: USB revision 1.0
uhub5: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5
uhub5: 2 ports with 2 removable, self powered
ehci1: <EHCI (generic) USB 2.0 controller> mem 0x9ba21000-0x9ba213ff irq 17 at device 29.7 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb6: EHCI version 1.0
usb6: companion controllers, 2 ports each: usb3 usb4 usb5
usb6: <EHCI (generic) USB 2.0 controller> on ehci1
usb6: USB revision 2.0
uhub6: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb6
uhub6: 6 ports with 6 removable, self powered
ukbd0: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on uhub6
kbd2 at ukbd0
ums0: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on uhub6
ums0: X report 0x0002 not supported
device_attach: ums0 attach returned 6
ums0: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on uhub6
ums0: 3 buttons and Z dir.
umass0: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on uhub6
umass1: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on uhub6
axe0: <vendor 0x2001 product 0x1a00, class 2/0, rev 2.00/10.01, addr 3> on uhub6
axe0: AX88172, bufsz 1536, boundary 64
miibus0: <MII bus> on axe0
rlphy0: <IC Plus 10/100 PHY> PHY 3 on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
axe0: WARNING: using obsoleted if_watchdog interface
axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag
axe0: Ethernet address: 00:80:c8:38:15:ff
pcib8: <PCI-PCI bridge> at device 30.0 on pci0
pci31: <PCI bus> on pcib8
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ATA controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20f0-0x20ff,0x20e0-0x20ef irq 16 at device 31.2 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
atapci1: <Intel ATA controller> port 0x2108-0x210f,0x2124-0x2127,0x2100-0x2107,0x2120-0x2123,0x20d0-0x20df,0x20c0-0x20cf irq 21 at device 31.5 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A, console
sio0: [FILTER]
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ukbd1: <Microsoft Comfort Curve Keyboard 2000, class 0/0, rev 2.00/1.73, addr 2> on uhub0
kbd3 at ukbd1
uhid0: <Microsoft Comfort Curve Keyboard 2000, class 0/0, rev 2.00/1.73, addr 2> on uhub0
cdce0: <IBM RNDIS/CDC ETHER, class 2/0, rev 2.00/2.15, addr 2> on uhub3
cdce0: faking MAC address
cdce0: WARNING: using obsoleted IFF_NEEDSGIANT flag
cdce0: Ethernet address: 2a:00:00:00:00:00
Timecounters tick every 1.000 msec
acd0: CDRW <HL-DT-STCD-RW/DVD DRIVE GCC-T20N/1.00> at ata0-master UDMA33
da0 at mpt0 bus 0 target 1 lun 0
da0: <ATA WD3000BLFS-23YBU 4V04> Fixed Direct Access SCSI-5 device
da0: 300.000MB/s transfers
da0: Command Queueing Enabled
da0: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C)
da1 at mpt0 bus 0 target 2 lun 0
da1: <ATA WD3000BLFS-23YBU 4V04> Fixed Direct Access SCSI-5 device
da1: 300.000MB/s transfers
da1: Command Queueing Enabled
da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C)
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
da2 at umass-sim1 bus 1 target 0 lun 0
da2: <Linux Virtual Floppy 0316> Removable Direct Access SCSI-0 device
da2: 40.000MB/s transfers
da2: Attempt to query device size failed: NOT READY, Medium not present
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: <Linux Virtual CD/DVD 0316> Removable CD-ROM SCSI-0 device
cd0: 40.000MB/s transfers
da3 at umass-sim1 bus 1 target 0 lun 1
da3: <Linux Virtual Floppy 0316> Removable Direct Access SCSI-0 device
da3: 40.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present
Trying to mount root from ufs:/dev/da0s1a

Charles Owens
Great Bay Software| www.GreatBaySoftware.com

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: No "boot0" menu on Soekris, net5501 vs net4521

2009-12-01T08:49:09Z

Charles Owens wrote:

> Hello,
>
> We're working with two different Soekris models (net5501 and net4521),
> working withFreeBSD 7.1 (nanobsd). We've found that the two models
> exhibit different boot behavior. Summary: the 4521 works fine, and
> the 5501 doesn't seem right. Here's what we see when we boot either:
>
> net4521 (BIOS ver 1.33) --
>
> * "boot0" menu appears (letting you pick either of two FreeBSD slices)
> * OS loads properly from chosen or default slice
>
>
> net5501 (BIOS ver 1.33c) --
>
> * "boot0" menu does _not_ appear.
> * system boots directly to slice 1 or 2, as chosen via BIOS option
> BootPartition
>
>
> Have others seen this behavior? For our application, we really need
> the 5501 to boot just like the 4521. Is this a bug (in BIOS, I'm
> guessing), or am I doing something wrong? It seems like there should
> be a way to clear the BootPartition setting, or set it to "MBR" or
> somesuch.
>

Issue resolved. The syntax for resetting the BootPartition parameter in
BIOS was non-obvious (to me). This can be accomplished with:

set BootPartition=Disabled

... my thanks to maintainer of wiki:
http://wiki.soekris.info/What_do_all_those_BIOS_settings_do%3F

...

Charles Owens
Great Bay Software

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE

2009-12-01T04:13:52Z

Stephane LAPIE wrote:

> Dieter wrote:
>> In message <4B13159D.9010504@...>, Stephane LAPIE writes:
>> And there are these, which you didn't mention:
>>> ad1: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
>>> ad12: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
>> (No, I don't know what that means, sorry.)
>
> Ah, actually I do have an idea as to what these are about : These two
> disks are SSDs I'm using in my ZFS pool as cache devices. So I guess
> this is the kind of error that says "I tried to use an access mode this
> device was not designed for".

It is probably result of bug in ata(4) code. It was fixed recently by
r199749. It is not critical when drive operates in DMA mode.

--
Alexander Motin
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE

2009-11-30T22:08:46Z

Dieter wrote:
> That sounds like a major clue that you probably have a very bad stick
> of memory (probably a hard error). I would try booting with just 1 stick
> at a time (or whatever the minimum is for your board) and isolate the bad
> stick.
>
> Most likely with 7.2 something landed on the bad location that doesn't
> actually get used, but with 8.0 something disk related lands there.

I'll try that the next time I have a chance to reboot that server.

> Let me guess, "Phoenix - AwardBIOS"?

...The very one.

As per kenv output :

smbios.bios.reldate="11/18/2008"
smbios.bios.vendor="Phoenix Technologies Ltd."
smbios.bios.version="2004Q3"
smbios.chassis.maker="TYAN Computer Corp"
smbios.memory.enabled="2097152"
smbios.planar.maker="Tyan Computer Corporation"
smbios.planar.product="S2895"
smbios.planar.serial="0123456789"
smbios.planar.version="TYAN Thunder K8WE S2895"
smbios.socket.enabled="2"
smbios.socket.populated="2"
smbios.system.maker="TYAN Computer Corp."
smbios.system.product="S2895"
smbios.system.serial="0123456789"
smbios.system.version="TYAN Thunder K8WE S2895"
smbios.version="2.33"

> On mine they can't even spell the name of the board correctly:
> "TYAN Tomact K8E BIOS V1.00 022105"
> (should be Tomcat) Such quality control.

Ouch.

> Mine hangs in boot if I have 2 JMB363 cards in the 2 PCIe x1 slots.
> Moved one to the x16 slot and it boots. I've been blaming the
> JMB363 cards but maybe the Phoenix AwardBIOS is the problem child?

In my case I guess that would be it. I have never seen FreeBSD freeze on
BTX level when loading from media, on any other computer.

> Most of the time one of the cards doesn't do it's display the drives
> and give me 5.1 nanoseconds to hit some control character to
> enter a setup-a-raid thingy. And frequently FreeBSD doesn't see
> one of the controllers and thus doesn't make it to multiuser. I'd

I also happen to have these ones, but with my Intel NICs (no way I'm
using the Marvell default ones, I get lost interrupt messages all over
the place when I crank up network I/O a bit)

> expect these events to be correlated but oddly they don't seem to be.
> Sometimes it takes several reboots to get all the controllers seen.
> I haven't seen an "out of memory" message, but the way things fly by
> perhaps I just missed it. It always works correctly the first time
> after a power cycle, so my theory is that the expansion cards aren't
> getting reset properly. I have a firewire PCI card that got into
> a funky mode and rebooting didn't fix it but a power cycle did.

Just for the recall, it's more like "Could not load Option ROM" (I
recall it was because it was out of memory buffers for these, but I
don't have the exact message text available at hand), and it pops up
randomly ; sometimes as you said, full power cycles do help. Sometimes
they don't.

> Tyan is supposed to be tier 1 but they aren't doing themselves
> any favors with that pathetic excuse for firmware.

Definitely not...
--
Stephane LAPIE, EPITA SRS, Promo 2005
"Even when they have digital readouts, I can't understand them."
--MegaTokyo

signature.asc (269 bytes) Download Attachment

Re: Hardware Support for new MB

2009-11-30T21:47:10Z

Oliver Lehmann wrote:

> I wonder if FreeBSD supports
>
> Audio:
> - ALC690 (ASRock)
> - ALC88S / ALC889 (MSI)
>
> SATA
> - ICH10R Southbridge
>
> I guess since the ICH10R also can do AHCI this is at least supported by
> the new (and old) ahci driver.

It is supported by both old ata(4) drives, and new ahci(4). I've
recently tested it in my lab.

> But what about sound?

All Realtek HDA codecs are supported fine. There can be some surprises
from motherboard vendor, but usually they work out of the box.

--
Alexander Motin
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE

2009-11-30T18:31:32Z

In message <4B1392CF.5090600@...>, Stephane LAPIE writes:

> >> Therefore, I am inclined to think the motherboard/memory (a "TYAN
> >> Thunder K8WE S2895") would be at fault here,
> >=20
> > I have been told that Tyan does a good job with memory, although even
> > assuming that's true it could still be a memory problem. My Tyan
> > board has a memory scrubbing feature that can be turned on in
> > firmware, but I've never tried it. Also, you could try rotating the
> > SIMMs and see if anything changes.
>
> The memory is brand new, from Corsair. I tried swapping the sticks
> (while still using the same slots) and strangely enough, some
> combinations just... don't boot at all.

That sounds like a major clue that you probably have a very bad stick
of memory (probably a hard error). I would try booting with just 1 stick
at a time (or whatever the minimum is for your board) and isolate the bad
stick.

Most likely with 7.2 something landed on the bad location that doesn't
actually get used, but with 8.0 something disk related lands there.

> Also, completely unrelated to the SATA controller, some quirks on this
> motherboard (though at BIOS level) have been annoying me quite a lot :
> - Booting FreeBSD from anything besides an IDE device has a 80% chance
> of freezing the computer at BTX level.
> - Sometimes the Option ROMs (this including the VGA card) are not loaded
> properly because of an "out of memory" problem at BIOS level.
>
> However, once the system is booted, it can go on for several months.
> (Though, I have witnessed one "Fatal error 12: Page fault"-type kernel
> panic in six months)

Let me guess, "Phoenix - AwardBIOS"?
On mine they can't even spell the name of the board correctly:
"TYAN Tomact K8E BIOS V1.00 022105"
(should be Tomcat) Such quality control.

Mine hangs in boot if I have 2 JMB363 cards in the 2 PCIe x1 slots.
Moved one to the x16 slot and it boots. I've been blaming the
JMB363 cards but maybe the Phoenix AwardBIOS is the problem child?

Most of the time one of the cards doesn't do it's display the drives
and give me 5.1 nanoseconds to hit some control character to
enter a setup-a-raid thingy. And frequently FreeBSD doesn't see
one of the controllers and thus doesn't make it to multiuser. I'd
expect these events to be correlated but oddly they don't seem to be.
Sometimes it takes several reboots to get all the controllers seen.
I haven't seen an "out of memory" message, but the way things fly by
perhaps I just missed it. It always works correctly the first time
after a power cycle, so my theory is that the expansion cards aren't
getting reset properly. I have a firewire PCI card that got into
a funky mode and rebooting didn't fix it but a power cycle did.

Tyan is supposed to be tier 1 but they aren't doing themselves
any favors with that pathetic excuse for firmware.
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE

2009-11-30T01:39:27Z

Dieter wrote:

> In message <4B13159D.9010504@...>, Stephane LAPIE writes:
>
>> On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O
>> bursts (confirmed with zpool iostat), before totally freezing down and
>> locking the ZFS pool (the system is still up and only ZFS based file
>> systems are unusable in this state), probably to avoid data corruption.
>> Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)"
>> error message showing up, on a random hard disk.
>
> And there are these, which you didn't mention:
>> ad1: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
>> ad12: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
> (No, I don't know what that means, sorry.)

Ah, actually I do have an idea as to what these are about : These two
disks are SSDs I'm using in my ZFS pool as cache devices. So I guess
this is the kind of error that says "I tried to use an access mode this
device was not designed for". In the same fashion, I also get such error
messages when trying SMART checks on ad0, which is a flash card.

ad0: FAILURE - SMART status=51<READY,DSC,ERROR> error=4<ABORTED>

So, I think these could safely be discarded under "not a normal disk
device". (Unless I'm completely mistaken about this...)

>> ad18: 1430799MB <Seagate ST31500341AS CC1H> at ata9-master SATA300
>> ad20: 1430799MB <Seagate ST31500341AS SD1A> at ata10-master SATA300
>
> How old is the SD1A disk? As you may know, Seagate had various troubles
> with the .11 firmware. I have some of the ST31500341AS CC1H and mine are
> new enough that they are supposed to be ok.

I bought all these disks at roughly the same time around April, but
strangely got an odd one in the lot and didn't bother to change it.

From what I checked with the Seagate page about the firmware issues,
SD1A is not affected. I also have three spare disks in a drawer in case
a problem occurs.

>> Therefore, I am inclined to think the motherboard/memory (a "TYAN
>> Thunder K8WE S2895") would be at fault here,
>
> I have been told that Tyan does a good job with memory, although even
> assuming that's true it could still be a memory problem. My Tyan
> board has a memory scrubbing feature that can be turned on in
> firmware, but I've never tried it. Also, you could try rotating the
> SIMMs and see if anything changes.

The memory is brand new, from Corsair. I tried swapping the sticks
(while still using the same slots) and strangely enough, some
combinations just... don't boot at all.

Also, completely unrelated to the SATA controller, some quirks on this
motherboard (though at BIOS level) have been annoying me quite a lot :
- Booting FreeBSD from anything besides an IDE device has a 80% chance
of freezing the computer at BTX level.
- Sometimes the Option ROMs (this including the VGA card) are not loaded
properly because of an "out of memory" problem at BIOS level.

However, once the system is booted, it can go on for several months.
(Though, I have witnessed one "Fatal error 12: Page fault"-type kernel
panic in six months)

Thanks again for your time.
--
Stephane LAPIE, EPITA SRS, Promo 2005
"Even when they have digital readouts, I can't understand them."
--MegaTokyo

signature.asc (269 bytes) Download Attachment

Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE

2009-11-29T21:01:11Z

In message <4B13159D.9010504@...>, Stephane LAPIE writes:

> On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O
> bursts (confirmed with zpool iostat), before totally freezing down and
> locking the ZFS pool (the system is still up and only ZFS based file
> systems are unusable in this state), probably to avoid data corruption.
> Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)"
> error message showing up, on a random hard disk.

And there are these, which you didn't mention:
> ad1: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
> ad12: FAILURE - SET_MULTI status=3D51<READY,DSC,ERROR> error=3D4<ABORTED>
(No, I don't know what that means, sorry.)

> ad18: 1430799MB <Seagate ST31500341AS CC1H> at ata9-master SATA300
> ad20: 1430799MB <Seagate ST31500341AS SD1A> at ata10-master SATA300

How old is the SD1A disk? As you may know, Seagate had various troubles
with the .11 firmware. I have some of the ST31500341AS CC1H and mine are
new enough that they are supposed to be ok.

> Therefore, I am inclined to think the motherboard/memory (a "TYAN
> Thunder K8WE S2895") would be at fault here,

I have been told that Tyan does a good job with memory, although even
assuming that's true it could still be a memory problem. My Tyan
board has a memory scrubbing feature that can be turned on in
firmware, but I've never tried it. Also, you could try rotating the
SIMMs and see if anything changes.
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Marvell MV88SX6081 on FreeBSD 8.0-RELEASE

2009-11-29T16:45:17Z

Hello,

did anyone have the opportunity to test operation with a MV88SX6081 SATA
controller on FreeBSD 8.0 ? My amd64 dual-Opteron (using 4G ECC RAM)
system just works fine with it on FreeBSD 7.2, but can't handle any
high-speed disk I/O when booting with a FreeBSD 8.0 kernel.

I have two controllers as follow :
atapci1@pci0:17:4:0: class=0x010000 card=0x11ab11ab chip=0x608111ab
rev=0x09 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = 'MV88SX6081 8-port SATA II PCI-X Controller'
class = mass storage
subclass = SCSI
atapci2@pci0:18:4:0: class=0x010000 card=0x11ab11ab chip=0x608111ab
rev=0x09 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = 'MV88SX6081 8-port SATA II PCI-X Controller'
class = mass storage
subclass = SCSI

http://www.supermicro.com/products/accessories/addon/AOC-SAT2-MV8.cfm

On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O
bursts (confirmed with zpool iostat), before totally freezing down and
locking the ZFS pool (the system is still up and only ZFS based file
systems are unusable in this state), probably to avoid data corruption.
Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)"
error message showing up, on a random hard disk.

I already gave the hard disks a thorough check and they work just fine.

On FreeBSD 7.2-STABLE, the scrub proceeds nicely and the I/O peaks at
300MB/s (confirmed with zpool iostat) on the pool without a hitch. I
could also confirm that attempts at booting a FreeBSD 8.0-RELEASE kernel
did not damage my ZFS pool checksums or anything.

Therefore, I am inclined to think the motherboard/memory (a "TYAN
Thunder K8WE S2895") would be at fault here, and that "something" in
FreeBSD 8.0 brings out this very specific problem, but I would first
like to hear about any tests of the aforementioned controller on FreeBSD
8.0 on another environment before upgrading the hardware.

Thanks in advance for your time,

P.S. : Here is the dmesg trace for FreeBSD 8.0.

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 8.0-RELEASE #8: Wed Nov 25 03:48:44 JST 2009

darksoul@...:/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/obj/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/src/sys/DARK-2009KERN
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Dual Core AMD Opteron(tm) Processor 275 (2210.20-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x20f12 Stepping = 2

Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x1<SSE3>
AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!>
AMD Features2=0x3<LAHF,CMP>
real memory = 5100273664 (4864 MB)
avail memory = 4109283328 (3918 MB)
ACPI APIC Table: <PTLTD APIC >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 2 package(s) x 2 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
ioapic0 <Version 1.1> irqs 0-23 on motherboard
ioapic1 <Version 1.1> irqs 24-27 on motherboard
ioapic2 <Version 1.1> irqs 28-31 on motherboard
ioapic3 <Version 1.1> irqs 32-55 on motherboard
kbd1 at kbdmux0
iscsi: version 2.1.0
acpi0: <PTLTD RSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
nfsmb0: <nForce2/3/4 MCP SMBus Controller> port
0xa000-0xa03f,0xa040-0xa07f at device 1.1 on pci0
smbus0: <System Management Bus> on nfsmb0
smb0: <SMBus generic I/O> on smbus0
nfsmb1: <nForce2/3/4 MCP SMBus Controller> on nfsmb0
smbus1: <System Management Bus> on nfsmb1
smb1: <SMBus generic I/O> on smbus1
ohci0: <OHCI (generic) USB controller> mem 0xdd800000-0xdd800fff irq 20
at device 2.0 on pci0
ohci0: [ITHREAD]
usbus0: <OHCI (generic) USB controller> on ohci0
atapci0: <nVidia nForce CK804 UDMA133 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1400-0x140f at device 6.0 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0x2000-0x207f mem
0xde000000-0xde7fffff,0xdd900000-0xdd90ffff at device 4.0 on pci1
pcib2: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci2: <ACPI PCI bus> on pcib2
amdtemp0: <AMD K8 Thermal Sensors> on hostb3
amdtemp1: <AMD K8 Thermal Sensors> on hostb7
pcib3: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci16: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 10.0 on pci16
pci17: <ACPI PCI bus> on pcib4
atapci1: <Marvell 88SX6081 SATA300 controller> port 0x3000-0x30ff mem
0xde900000-0xde9fffff,0xdec00000-0xdeffffff irq 24 at device 4.0 on pci17
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci1
ata5: [ITHREAD]
ata6: <ATA channel 4> on atapci1
ata6: [ITHREAD]
ata7: <ATA channel 5> on atapci1
ata7: [ITHREAD]
ata8: <ATA channel 6> on atapci1
ata8: [ITHREAD]
ata9: <ATA channel 7> on atapci1
ata9: [ITHREAD]
pcib5: <ACPI PCI-PCI bridge> at device 11.0 on pci16
pci18: <ACPI PCI bus> on pcib5
atapci2: <Marvell 88SX6081 SATA300 controller> port 0x4000-0x40ff mem
0xdf400000-0xdf4fffff,0xdf000000-0xdf3fffff irq 28 at device 4.0 on pci18
atapci2: [ITHREAD]
ata10: <ATA channel 0> on atapci2
ata10: [ITHREAD]
ata11: <ATA channel 1> on atapci2
ata11: [ITHREAD]
ata12: <ATA channel 2> on atapci2
ata12: [ITHREAD]
ata13: <ATA channel 3> on atapci2
ata13: [ITHREAD]
ata14: <ATA channel 4> on atapci2
ata14: [ITHREAD]
ata15: <ATA channel 5> on atapci2
ata15: [ITHREAD]
ata16: <ATA channel 6> on atapci2
ata16: [ITHREAD]
ata17: <ATA channel 7> on atapci2
ata17: [ITHREAD]
em0: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x4400-0x443f
mem 0xdf500000-0xdf51ffff irq 29 at device 9.0 on pci18
em0: [FILTER]
em0: Ethernet address: 00:07:e9:0f:a3:80
em1: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x4440-0x447f
mem 0xdf520000-0xdf53ffff irq 30 at device 9.1 on pci18
em1: [FILTER]
em1: Ethernet address: 00:07:e9:0f:a3:81
pcib6: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci128: <ACPI PCI bus> on pcib6
pci128: <memory> at device 0.0 (no driver attached)
pci128: <memory> at device 1.0 (no driver attached)
pcib7: <ACPI PCI-PCI bridge> at device 14.0 on pci128
pci129: <ACPI PCI bus> on pcib7
pcib8: <ACPI PCI-PCI bridge> at device 0.0 on pci129
pci130: <ACPI PCI bus> on pcib8
em2: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x5000-0x503f
mem 0xdfb40000-0xdfb5ffff,0xdfb00000-0xdfb3ffff irq 48 at device 4.0 on
pci130
em2: [FILTER]
em2: Ethernet address: 00:0e:0c:70:7d:1e
em3: <Intel(R) PRO/1000 Network Connection 6.9.14> port 0x5040-0x507f
mem 0xdfb60000-0xdfb7ffff,0xdfb80000-0xdfbbffff irq 49 at device 4.1 on
pci130
em3: [FILTER]
em3: Ethernet address: 00:0e:0c:70:7d:1f
pcib9: <PCI-PCI bridge> at device 0.2 on pci129
pci131: <PCI bus> on pcib9
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
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]
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0
uart0: [FILTER]
fdc1: <floppy drive controller> port 0-0x5,0 on acpi0
fdc1: cannot reserve interrupt line
device_attach: fdc1 attach returned 6
cpu0: <ACPI CPU> on acpi0
powernow0: <Cool`n'Quiet K8> on cpu0
cpu1: <ACPI CPU> on acpi0
powernow1: <Cool`n'Quiet K8> on cpu1
cpu2: <ACPI CPU> on acpi0
powernow2: <Cool`n'Quiet K8> on cpu2
cpu3: <ACPI CPU> on acpi0
powernow3: <Cool`n'Quiet K8> on cpu3
fdc1: <floppy drive controller> port 0-0x5,0 on acpi0
fdc1: cannot reserve interrupt line
device_attach: fdc1 attach returned 6
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is
present;
to enable, add "vfs.zfs.prefetch_disable=0" to
/boot/loader.conf.
ZFS filesystem version 13
ZFS storage pool version 13
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
ad0: DMA limited to UDMA33, device found non-ATA66 cable
ad0: 3823MB <TRANSCEND 20070831> at ata0-master UDMA33
ugen0.1: <nVidia> at usbus0
uhub0: <nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ad1: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>
ad1: 61136MB <TS64GSSD25 M V090331> at ata0-slave UDMA133
ad4: 1430799MB <Seagate ST31500341AS CC1H> at ata2-master SATA300
ad6: 1430799MB <Seagate ST31500341AS CC1H> at ata3-master SATA300
ad8: 1430799MB <Seagate ST31500341AS CC1H> at ata4-master SATA300
ad10: 1430799MB <Seagate ST31500341AS CC1H> at ata5-master SATA300
uhub0: 10 ports with 10 removable, self powered
ad12: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>
ad12: 61136MB <TS64GSSD25S M V090216> at ata6-master SATA300
ad14: 1430799MB <Seagate ST31500341AS CC1H> at ata7-master SATA300
ad16: 1430799MB <Seagate ST31500341AS CC1H> at ata8-master SATA300
ad18: 1430799MB <Seagate ST31500341AS CC1H> at ata9-master SATA300
ad20: 1430799MB <Seagate ST31500341AS SD1A> at ata10-master SATA300
ad22: 1430799MB <Seagate ST31500341AS CC1H> at ata11-master SATA300
ad24: 1430799MB <Seagate ST31500341AS CC1H> at ata12-master SATA300
ad26: 1430799MB <Seagate ST31500341AS CC1H> at ata13-master SATA300
ad28: 1430799MB <Seagate ST31500341AS CC1H> at ata14-master SATA300
ugen0.2: <Chicony> at usbus0
uhub1: <Chicony Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2> on usbus0
ad30: 1430799MB <Seagate ST31500341AS CC1H> at ata15-master SATA300
ad32: 1430799MB <Seagate ST31500341AS CC1H> at ata16-master SATA300
ad34: 1430799MB <Seagate ST31500341AS CC1H> at ata17-master SATA300
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
Root mount waiting for: usbus0
uhub1: 3 ports with 2 removable, bus powered
ugen0.3: <Chicony> at usbus0
ukbd0: <Chicony PFU-68 USB Keyboard, class 0/0, rev 1.10/1.00, addr 3>
on usbus0
kbd2 at ukbd0
Trying to mount root from zfs:prana

P.P.S. : Here is the FreeBSD 7.2-STABLE dmesg trace.

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 #3: Thu Aug 6 20:59:13 JST 2009

darksoul@...:/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/obj/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/src/sys/DARK-2009KERN
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Dual Core AMD Opteron(tm) Processor 275 (2210.20-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x20f12 Stepping = 2

Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x1<SSE3>
AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow!>
AMD Features2=0x3<LAHF,CMP>
Cores per package: 2
usable memory = 4282880000 (4084 MB)
avail memory = 4110327808 (3919 MB)
ACPI APIC Table: <PTLTD APIC >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
This module (opensolaris) contains code covered by the
Common Development and Distribution License (CDDL)
see http://opensolaris.org/os/licensing/opensolaris_license/
ioapic0 <Version 1.1> irqs 0-23 on motherboard
ioapic1 <Version 1.1> irqs 24-27 on motherboard
ioapic2 <Version 1.1> irqs 28-31 on motherboard
ioapic3 <Version 1.1> irqs 32-55 on motherboard
kbd1 at kbdmux0
smbios0: <System Management BIOS> at iomem 0xf7850-0xf786e on motherboard
smbios0: Version: 2.33
acpi0: <PTLTD RSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
nfsmb0: <nForce2/3/4 MCP SMBus Controller> port
0xa000-0xa03f,0xa040-0xa07f at device 1.1 on pci0
smbus0: <System Management Bus> on nfsmb0
smb0: <SMBus generic I/O> on smbus0
nfsmb1: <nForce2/3/4 MCP SMBus Controller> on nfsmb0
smbus1: <System Management Bus> on nfsmb1
smb1: <SMBus generic I/O> on smbus1
ohci0: <OHCI (generic) USB controller> mem 0xdd800000-0xdd800fff irq 20
at device 2.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 10 ports with 10 removable, self powered
atapci0: <nVidia nForce CK804 UDMA133 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1400-0x140f at device 6.0 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0x2000-0x207f mem
0xde000000-0xde7fffff,0xdd900000-0xdd90ffff at device 4.0 on pci1
pcib2: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci2: <ACPI PCI bus> on pcib2
amdtemp0: <AMD K8 Thermal Sensors> on hostb3
amdtemp1: <AMD K8 Thermal Sensors> on hostb7
pcib3: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci16: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 10.0 on pci16
pci17: <ACPI PCI bus> on pcib4
atapci1: <Marvell 88SX6081 SATA300 controller> port 0x3000-0x30ff mem
0xde900000-0xde9fffff,0xdec00000-0xdeffffff irq 24 at device 4.0 on pci17
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci1
ata5: [ITHREAD]
ata6: <ATA channel 4> on atapci1
ata6: [ITHREAD]
ata7: <ATA channel 5> on atapci1
ata7: [ITHREAD]
ata8: <ATA channel 6> on atapci1
ata8: [ITHREAD]
ata9: <ATA channel 7> on atapci1
ata9: [ITHREAD]
pcib5: <ACPI PCI-PCI bridge> at device 11.0 on pci16
pci18: <ACPI PCI bus> on pcib5
atapci2: <Marvell 88SX6081 SATA300 controller> port 0x4000-0x40ff mem
0xdf400000-0xdf4fffff,0xdf000000-0xdf3fffff irq 28 at device 4.0 on pci18
atapci2: [ITHREAD]
ata10: <ATA channel 0> on atapci2
ata10: [ITHREAD]
ata11: <ATA channel 1> on atapci2
ata11: [ITHREAD]
ata12: <ATA channel 2> on atapci2
ata12: [ITHREAD]
ata13: <ATA channel 3> on atapci2
ata13: [ITHREAD]
ata14: <ATA channel 4> on atapci2
ata14: [ITHREAD]
ata15: <ATA channel 5> on atapci2
ata15: [ITHREAD]
ata16: <ATA channel 6> on atapci2
ata16: [ITHREAD]
ata17: <ATA channel 7> on atapci2
ata17: [ITHREAD]
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x4400-0x443f mem
0xdf500000-0xdf51ffff irq 29 at device 9.0 on pci18
em0: [FILTER]
em0: Ethernet address: 00:07:e9:0f:a3:80
em1: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x4440-0x447f mem
0xdf520000-0xdf53ffff irq 30 at device 9.1 on pci18
em1: [FILTER]
em1: Ethernet address: 00:07:e9:0f:a3:81
pcib6: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci128: <ACPI PCI bus> on pcib6
pci128: <memory> at device 0.0 (no driver attached)
pci128: <memory> at device 1.0 (no driver attached)
pcib7: <ACPI PCI-PCI bridge> at device 14.0 on pci128
pci129: <ACPI PCI bus> on pcib7
pcib8: <ACPI PCI-PCI bridge> at device 0.0 on pci129
pci130: <ACPI PCI bus> on pcib8
em2: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x5000-0x503f mem
0xdfb40000-0xdfb5ffff,0xdfb00000-0xdfb3ffff irq 48 at device 4.0 on pci130
em2: [FILTER]
em2: Ethernet address: 00:0e:0c:70:7d:1e
em3: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x5040-0x507f mem
0xdfb60000-0xdfb7ffff,0xdfb80000-0xdfbbffff irq 49 at device 4.1 on pci130
em3: [FILTER]
em3: Ethernet address: 00:0e:0c:70:7d:1f
pcib9: <PCI-PCI bridge> at device 0.2 on pci129
pci131: <PCI bus> on pcib9
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]
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, console
sio0: [FILTER]
fdc0: <floppy drive controller> port 0-0x5,0 on acpi0
fdc0: cannot reserve interrupt line
device_attach: fdc0 attach returned 6
cpu0: <ACPI CPU> on acpi0
powernow0: <Cool`n'Quiet K8> on cpu0
cpu1: <ACPI CPU> on acpi0
powernow1: <Cool`n'Quiet K8> on cpu1
cpu2: <ACPI CPU> on acpi0
powernow2: <Cool`n'Quiet K8> on cpu2
cpu3: <ACPI CPU> on acpi0
powernow3: <Cool`n'Quiet K8> on cpu3
fdc0: <floppy drive controller> port 0-0x5,0 on acpi0
fdc0: cannot reserve interrupt line
device_attach: fdc0 attach returned 6
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ppc0: cannot reserve I/O port range
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
uhub1: <Chicony Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2> on uhub0
uhub1: 3 ports with 2 removable, bus powered
ukbd0: <Chicony PFU-68 USB Keyboard, class 0/0, rev 1.10/1.00, addr 3>
on uhub1
kbd2 at ukbd0
WARNING: ZFS is considered to be an experimental feature in FreeBSD.
Timecounters tick every 1.000 msec
ad0: DMA limited to UDMA33, device found non-ATA66 cable
ZFS filesystem version 13
ZFS storage pool version 13
ad0: 3823MB <TRANSCEND 20070831> at ata0-master UDMA33
ad1: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>
ad1: 61136MB <TS64GSSD25 M V090331> at ata0-slave UDMA133
ad4: 1430799MB <Seagate ST31500341AS CC1H> at ata2-master SATA300
ad6: 1430799MB <Seagate ST31500341AS CC1H> at ata3-master SATA300
ad8: 1430799MB <Seagate ST31500341AS CC1H> at ata4-master SATA300
ad10: 1430799MB <Seagate ST31500341AS CC1H> at ata5-master SATA300
ad12: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>
ad12: 61136MB <TS64GSSD25S M V090216> at ata6-master SATA300
ad14: 1430799MB <Seagate ST31500341AS CC1H> at ata7-master SATA300
ad16: 1430799MB <Seagate ST31500341AS CC1H> at ata8-master SATA300
ad18: 1430799MB <Seagate ST31500341AS CC1H> at ata9-master SATA300
ad20: 1430799MB <Seagate ST31500341AS SD1A> at ata10-master SATA300
ad22: 1430799MB <Seagate ST31500341AS CC1H> at ata11-master SATA300
ad24: 1430799MB <Seagate ST31500341AS CC1H> at ata12-master SATA300
ad26: 1430799MB <Seagate ST31500341AS CC1H> at ata13-master SATA300
ad28: 1430799MB <Seagate ST31500341AS CC1H> at ata14-master SATA300
ad30: 1430799MB <Seagate ST31500341AS CC1H> at ata15-master SATA300
ad32: 1430799MB <Seagate ST31500341AS CC1H> at ata16-master SATA300
ad34: 1430799MB <Seagate ST31500341AS CC1H> at ata17-master SATA300
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
Trying to mount root from zfs:prana

The full pciconf -lv output :

none0@pci0:0:0:0: class=0x058000 card=0x289510f1 chip=0x005e10de
rev=0xa4 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 Memory Controller'
class = memory
isab0@pci0:0:1:0: class=0x060100 card=0x289510f1 chip=0x005110de
rev=0xb1 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 ISA Bridge'
class = bridge
subclass = PCI-ISA
nfsmb0@pci0:0:1:1: class=0x0c0500 card=0x289510f1 chip=0x005210de
rev=0xa2 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 SMBus'
class = serial bus
subclass = SMBus
ohci0@pci0:0:2:0: class=0x0c0310 card=0x289510f1 chip=0x005a10de
rev=0xa2 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 USB Controller'
class = serial bus
subclass = USB
atapci0@pci0:0:6:0: class=0x01018a card=0x289510f1 chip=0x005310de
rev=0xf3 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 Parallel ATA Controller'
class = mass storage
subclass = ATA
pcib1@pci0:0:9:0: class=0x060401 card=0x00000000 chip=0x005c10de
rev=0xa2 hdr=0x01
vendor = 'Nvidia Corp'
device = 'nForce4 PCI Bridge'
class = bridge
subclass = PCI-PCI
pcib2@pci0:0:14:0: class=0x060400 card=0x00000000 chip=0x005d10de
rev=0xa3 hdr=0x01
vendor = 'Nvidia Corp'
device = 'nForce4 PCIe Bridge'
class = bridge
subclass = PCI-PCI
hostb0@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon64/Opteron/Sempron (K8 Family) HyperTransport
Technology Configuration'
class = bridge
subclass = HOST-PCI
hostb1@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon64/Opteron/Sempron (K8 Family) Address Map'
class = bridge
subclass = HOST-PCI
hostb2@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon64/Opteron/Sempron (K8 Family) DRAM Controller'
class = bridge
subclass = HOST-PCI
hostb3@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'Athlon64/Opteron/Sempron (K8 Family) Miscellaneous
Control'
class = bridge
subclass = HOST-PCI
hostb4@pci0:0:25: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
hostb5@pci0:0:25: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
hostb6@pci0:0:25: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
hostb7@pci0:0:25: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:4:0: class=0x030000 card=0x63261039 chip=0x63261039
rev=0x0b hdr=0x00
vendor = 'Silicon Integrated Systems (SiS)'
device = 'SiS6326 GUI Accelerator'
class = display
subclass = VGA
pcib4@pci0:16:10:0: class=0x060400 card=0x00000000 chip=0x74501022
rev=0x13 hdr=0x01
vendor = 'Advanced Micro Devices (AMD)'
device = 'PCI-X Bridge (AMD-8131)'
class = bridge
subclass = PCI-PCI
ioapic0@pci0:16:10:1: class=0x080010 card=0x289510f1 chip=0x74511022
rev=0x01 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'PCI-X IOAPIC (AMD-8131)'
class = base peripheral
subclass = interrupt controller
pcib5@pci0:16:11:0: class=0x060400 card=0x00000000 chip=0x74501022
rev=0x13 hdr=0x01
vendor = 'Advanced Micro Devices (AMD)'
device = 'PCI-X Bridge (AMD-8131)'
class = bridge
subclass = PCI-PCI
ioapic1@pci0:16:11:1: class=0x080010 card=0x289510f1 chip=0x74511022
rev=0x01 hdr=0x00
vendor = 'Advanced Micro Devices (AMD)'
device = 'PCI-X IOAPIC (AMD-8131)'
class = base peripheral
subclass = interrupt controller
atapci1@pci0:17:4:0: class=0x010000 card=0x11ab11ab chip=0x608111ab
rev=0x09 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = 'MV88SX6081 8-port SATA II PCI-X Controller'
class = mass storage
subclass = SCSI
atapci2@pci0:18:4:0: class=0x010000 card=0x11ab11ab chip=0x608111ab
rev=0x09 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = 'MV88SX6081 8-port SATA II PCI-X Controller'
class = mass storage
subclass = SCSI
em0@pci0:18:9:0: class=0x020000 card=0x10128086 chip=0x10128086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'Dual Port Gigabit Ethernet Controller (Fiber) (82546EB)'
class = network
subclass = ethernet
em1@pci0:18:9:1: class=0x020000 card=0x10128086 chip=0x10128086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'Dual Port Gigabit Ethernet Controller (Fiber) (82546EB)'
class = network
subclass = ethernet
none1@pci0:128:0:0: class=0x058000 card=0x289510f1 chip=0x005e10de
rev=0xa4 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 Memory Controller'
class = memory
none2@pci0:128:1:0: class=0x058000 card=0x289510f1 chip=0x00d310de
rev=0xb1 hdr=0x00
vendor = 'Nvidia Corp'
device = 'nForce4 Memory Controller'
class = memory
pcib7@pci0:128:14:0: class=0x060400 card=0x00000000 chip=0x005d10de
rev=0xa3 hdr=0x01
vendor = 'Nvidia Corp'
device = 'nForce4 PCIe Bridge'
class = bridge
subclass = PCI-PCI
pcib8@pci0:129:0:0: class=0x060400 card=0x00000000 chip=0x03408086
rev=0x09 hdr=0x01
vendor = 'Intel Corporation'
device = '41210 [Lanai] Serial to Parallel PCI Bridge A-segment
Bridge'
class = bridge
subclass = PCI-PCI
pcib9@pci0:129:0:2: class=0x060400 card=0x00000000 chip=0x03418086
rev=0x09 hdr=0x01
vendor = 'Intel Corporation'
device = '41210 [Lanai] Serial to Parallel PCI Bridge B-segment
Bridge'
class = bridge
subclass = PCI-PCI
em2@pci0:130:4:0: class=0x020000 card=0x108a8086 chip=0x108a8086
rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'PRO/1000 P'
class = network
subclass = ethernet
em3@pci0:130:4:1: class=0x020000 card=0x108a8086 chip=0x108a8086
rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'PRO/1000 P'
class = network
subclass = ethernet

Here is my ZFS pool status :

pool: prana
state: ONLINE
scrub: scrub completed after 10h37m with 0 errors on Fri Nov 27
09:12:08 2009
config:

NAME STATE READ WRITE CKSUM
prana ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ad16 ONLINE 0 0 0
ad30 ONLINE 0 0 0
ad28 ONLINE 0 0 0
ad18 ONLINE 0 0 0
ad14 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ad26 ONLINE 0 0 0
ad4 ONLINE 0 0 0
ad6 ONLINE 0 0 0
ad8 ONLINE 0 0 0
ad10 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ad20 ONLINE 0 0 0
ad22 ONLINE 0 0 0
ad24 ONLINE 0 0 0
ad32 ONLINE 0 0 0
ad34 ONLINE 0 0 0
cache
ad12 ONLINE 0 0 0
ad1 ONLINE 0 0 0

errors: No known data errors

--
Stephane LAPIE, EPITA SRS, Promo 2005
"Even when they have digital readouts, I can't understand them."
--MegaTokyo

signature.asc (269 bytes) Download Attachment

Re: Hardware Support for new MB

2009-11-29T13:46:32Z

On Sun, Nov 29, 2009 at 11:04:32AM +0100, Oliver Lehmann wrote:

> Hi,
>
> I'd like to upgrade my Athlon64 3500+ system to a new intel i7 1366
> system. I tend between aa MSI and an ASRock board:
>
> http://www.msi.com/index.php?func=proddesc&maincat_no=1&cat2_no=170&prod_no=1796
> http://www.asrock.com/mb/overview.asp?Model=X58%20Extreme&s=1366
>
> I wonder if FreeBSD supports
>
> Audio:
> - ALC690 (ASRock)
> - ALC88S / ALC889 (MSI)
>
> LAN:
> - RTL 8111DL (ASRock)
> - RTL 8111C (MSI)
>
> SATA
> - ICH10R Southbridge
>
> I guess since the ICH10R also can do AHCI this is at least supported by
> the new (and old) ahci driver.
> But what about sound and LAN? RTL8111C I was able to found in if_re.c but
> RTL8111DL? Unfortunally I was not able to find the device IDs of this

I'm not sure but generally I could make it work if you can give me
the output value of Tx config register. Normally the value is
printed by re(4) even if re(4) does not recognize the controller.

> devices to look them up in the FreeBSD drivers - not even in the Windows
> drivers :(
>

RealTek tends to use the same PCI device id for a family so knowing
the PCI device id does not help.
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Hardware Support for new MB

2009-11-29T02:04:32Z

Hi,

I'd like to upgrade my Athlon64 3500+ system to a new intel i7 1366
system. I tend between aa MSI and an ASRock board:

http://www.msi.com/index.php?func=proddesc&maincat_no=1&cat2_no=170&prod_no=1796
http://www.asrock.com/mb/overview.asp?Model=X58%20Extreme&s=1366

I wonder if FreeBSD supports

Audio:
- ALC690 (ASRock)
- ALC88S / ALC889 (MSI)

LAN:
- RTL 8111DL (ASRock)
- RTL 8111C (MSI)

SATA
- ICH10R Southbridge

I guess since the ICH10R also can do AHCI this is at least supported by
the new (and old) ahci driver.
But what about sound and LAN? RTL8111C I was able to found in if_re.c but
RTL8111DL? Unfortunally I was not able to find the device IDs of this
devices to look them up in the FreeBSD drivers - not even in the Windows
drivers :(

--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

hptraidconf for freebsd

2009-11-29T00:22:29Z

where did htpraidconf go? i used to have it but it seems to have flown
the coop from ports. i have a 2340 which needs a bit of attention.

randy
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Panic possibly related to glabel/geom and siis(4)

2009-11-26T17:08:54Z

This is similar to what I have fight on last two weeks (was 8.0-RC USB/FS).
My back trace from the panic is some different from yours, but the behave is the same.

When access USB drives from 8.0-RC and 8.0-R will cause drives dead, vanish or reset, thus causing panic.
>From both cases, it looks like a hotplug/automount related problem.

--- On Tue, 11/24/09, Steve Polyack <korvus@...> wrote:

> From: Steve Polyack <korvus@...>
> Subject: Panic possibly related to glabel/geom and siis(4)
> To: freebsd-hardware@..., "freebsd-stable" <freebsd-stable@...>, freebsd-geom@...
> Date: Tuesday, November 24, 2009, 5:40 PM
> I have a system running
> 8.0-PRERELEASE with multiple drives and SATA port
> multipliers (siis controllers and PMPs). All of the
> attached drives are labeled via glabel(8) and then included
> into a ZFS pool. During some testing to determine how
> the system would react to a dead drive (simulated by
> physically removing a drive during operation), I was
> able to produce a panic.
>
> Now, I know that the SATA PMP and siis(4) code to handle
> and recover from device errors is incomplete, but I believe
> the crash may be particular to using glabel'd drives.
> Basically, after removing a drive while the zpool is in use
> and issues 'camcontrol reset' and 'rescan' on the
> appropriate bus, the physical device associated with the
> drive disappears. In this case:
> (pass5:siisch7:0:15:0): lost device
> (pass5:siisch7:0:15:0): removing device entry
> (ada2:siisch7:0:0:0): lost device
>
> and /dev/ada2 disappears. However, the associated
> glabel /dev/label/bigdisk07 remains. Since my ZFS pool
> is created based on the drive glabels, I believe this is why
> ZFS never notices the drives disappear either.
>
> Do glabels typically go away after a physical device is
> lost? Should this not be the case?
>
>
> After some runtime with the physical device missing, a
> kernel panic is produced:
>
> ada2:siisch7:0:0:0): Synchronize cache failed
> (ada2:siisch7:0:0:0): removing device entry
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 2; apic id = 14
> fault virtual address = 0x48
> fault code
> = supervisor write data, page not present
> instruction pointer =
> 0x20:0xffffffff8035f375
> stack pointer
> = 0x28:0xffffff800006db60
> frame pointer
> = 0x28:0xffffff800006db70
> code segment =
> base 0x0, limit 0xfffff, type 0x1b
>
> = DPL 0, pres 1, long 1,
> def32 0, gran 1
> processor eflags = interrupt
> enabled, resume, IOPL = 0
> current process = 2
> (g_event)
> [thread pid 2 tid 100014 ]
> Stopped at
> _mtx_lock_flags+0x15: lock
> cmpxchgq %rsi,0x18(%rdi)
> db> bt
> Tracing pid 2 tid 100014 td 0xffffff00014d4ab0
> _mtx_lock_flags() at _mtx_lock_flags+0x15
> vdev_geom_release() at vdev_geom_release+0x33
> vdev_geom_orphan() at vdev_geom_orphan+0x15c
> g_run_events() at g_run_events+0x104
> g_event_procbody() at g_event_procbody+0x55
> fork_exit() at fork_exit+0x118
> fork_trampoline() at fork_trampoline+0xe
> --- trap 0, rip = 0, rsp = 0xffffff800006dd30, rbp = 0 ---
>
>
> I'm open to try patches and other suggestions.
> Thanks.
> _______________________________________________
> freebsd-hardware@...
> mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."
>

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

ATA check power status?

2009-11-26T10:52:29Z

Hi all,

I'm still playing with my WD Hard Drive WD10EADS (Caviar Green 1TB):

> === START OF INFORMATION SECTION ===
> Device Model: WDC WD10EADS-00M2B0
> Serial Number: WD-WCAV51538624
> Firmware Version: 01.00A01
> User Capacity: 1,000,204,886,016 bytes
> Device is: Not in smartctl database [for details use: -P
> showall]
> ATA Version is: 8
> ATA Standard is: Exact ATA specification draft version not indicated
> Local Time is: Thu Nov 26 18:50:44 2009 CET
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled

I'm trying to configure smartctl so that it won't wake the HD up for
testing, using "-n standby":

> /dev/ad6 -H -m root -a -n standby -o on -S on -s (S/../.././02|
> L/../../6/03)

But smartd won't accept:

> smartd[94230]: Device: /dev/ad6, no ATA CHECK POWER STATUS support,
> ignoring -n Directive

I just don't know why. Is it:

- the HD that doesn't support ata check power status?
- the FreeBSD ata driver?
- smartd that is too old for this new HD?

regards,
patpro
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: USB keyboard flaky with PAE kernel, 7.1

2009-11-25T03:25:36Z

Charles Owens wrote:

> Howdy,
>
> I'm still digging into it, put preliminary testing is showing that with
> a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only
> occasionally, if you're lucky. This flakiness is being seen with
> several different server models that we support (HP and IBM, all Xeon
> based). If we boot a non-PAE kernel then the USB keyboard is rock solid.
>
> For what it's worth (probably little) I can run the same PAE kernel on
> an old Pentium II system and a USB keyboard works fine.
>
> What is the best way to dig into this? Any and all assistance greatly
> appreciated. I can provide remote access to a testbed of these systems
> if useful.
>

Following is some detail for one of the systems, an IBM System x3550 M2.

>From dmidecode:

System Information
Manufacturer: IBM
Product Name: IBM System x -[7946AC1]-
Version: 00

[root@dmz55 ~]# usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 powered
port 2 addr 2: low speed, power 100 mA, config 1, Comfort Curve
Keyboard 2000(0x00dd), Microsoft(0x045e), rev 1.73
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
Controller /dev/usb2:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 powered
port 2 powered
port 3 powered
port 4 powered
port 5 powered
port 6 powered
usbdevs: /dev/usb3: Input/output error
usbdevs: /dev/usb4: Input/output error
usbdevs: /dev/usb5: Input/output error
Controller /dev/usb6:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),
Intel(0x0000), rev 1.00
port 1 addr 2: high speed, power 2 mA, config 2, IBM Composite
Device-0(0x4012), IBM(0x04b3), rev 0.00
port 2 powered
port 3 powered
port 4 powered
port 5 powered
port 6 addr 3: high speed, power 450 mA, config 1, product
0x1a00(0x1a00), vendor 0x2001(0x2001), rev 10.01

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.1-RELEASE-p8 #3: Thu Nov 19 15:24:03 EST 2009
muck@...:/usr/obj/usr/src/sys/DMZ55
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (2000.08-MHz
686-class CPU)
Origin = "GenuineIntel" Id = 0x106a5 Stepping = 5

Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>

Features2=0x9ce3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,SSE4.2,POPCNT>
AMD Features=0x28100000<NX,RDTSCP,LM>
AMD Features2=0x1<LAHF>
Cores per package: 8
Logical CPUs per core: 2
real memory = 6442450944 (6144 MB)
avail memory = 4150349824 (3958 MB)
ACPI APIC Table: <IBM THURLEY >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 2
cpu2 (AP): APIC ID: 4
cpu3 (AP): APIC ID: 6
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
kbd1 at kbdmux0
acpi0: <IBM THURLEY> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on
acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x588-0x58b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 28 at device 1.0 on pci0
pci11: <ACPI PCI bus> on pcib1
pci11: <network, ethernet> at device 0.0 (no driver attached)
pci11: <network, ethernet> at device 0.1 (no driver attached)
pcib2: <PCI-PCI bridge> irq 29 at device 2.0 on pci0
pci16: <PCI bus> on pcib2
pci16: <network, ethernet> at device 0.0 (no driver attached)
pci16: <network, ethernet> at device 0.1 (no driver attached)
pcib3: <ACPI PCI-PCI bridge> irq 24 at device 3.0 on pci0
pci21: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 30 at device 7.0 on pci0
pci26: <ACPI PCI bus> on pcib4
pci0: <base peripheral, interrupt controller> at device 16.0 (no driver
attached)
pci0: <base peripheral, interrupt controller> at device 16.1 (no driver
attached)
pci0: <base peripheral, interrupt controller> at device 17.0 (no driver
attached)
pci0: <base peripheral, interrupt controller> at device 17.1 (no driver
attached)
pci0: <base peripheral, interrupt controller> at device 20.0 (no driver
attached)
pci0: <base peripheral, interrupt controller> at device 20.1 (no driver
attached)
pci0: <base peripheral, interrupt controller> at device 20.2 (no driver
attached)
pci0: <base peripheral, interrupt controller> at device 20.3 (no driver
attached)
pci0: <base peripheral> at device 22.0 (no driver attached)
pci0: <base peripheral> at device 22.1 (no driver attached)
pci0: <base peripheral> at device 22.2 (no driver attached)
pci0: <base peripheral> at device 22.3 (no driver attached)
pci0: <base peripheral> at device 22.4 (no driver attached)
pci0: <base peripheral> at device 22.5 (no driver attached)
pci0: <base peripheral> at device 22.6 (no driver attached)
pci0: <base peripheral> at device 22.7 (no driver attached)
uhci0: <UHCI (generic) USB controller> port 0x20a0-0x20bf irq 17 at
device 26.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0x2080-0x209f irq 18 at
device 26.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0x9ba21400-0x9ba217ff irq
19 at device 26.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: wrong number of companions (3 != 2)
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 6 ports with 6 removable, self powered
pcib5: <PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci1: <PCI bus> on pcib5
mpt0: <LSILogic SAS/SATA Adapter> port 0x1000-0x10ff mem
0x9b910000-0x9b913fff,0x9b900000-0x9b90ffff irq 16 at device 0.0 on pci1
mpt0: [ITHREAD]
mpt0: MPI Version=1.5.20.0
mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 )
mpt0: 0 Active Volumes (2 Max)
mpt0: 0 Hidden Drive Members (14 Max)
pcib6: <PCI-PCI bridge> irq 16 at device 28.4 on pci0
pci6: <PCI bus> on pcib6
pcib7: <PCI-PCI bridge> irq 16 at device 0.0 on pci6
pci7: <PCI bus> on pcib7
vgapci0: <VGA-compatible display> mem
0x9a000000-0x9affffff,0x9b800000-0x9b803fff,0x9b000000-0x9b7fffff irq 16
at device 0.0 on pci7
uhci2: <UHCI (generic) USB controller> port 0x2060-0x207f irq 17 at
device 29.0 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb3: <UHCI (generic) USB controller> on uhci2
usb3: USB revision 1.0
usb3: root hub problem, error=4
uhci3: <UHCI (generic) USB controller> port 0x2040-0x205f irq 18 at
device 29.1 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb4: <UHCI (generic) USB controller> on uhci3
usb4: USB revision 1.0
usb4: root hub problem, error=4
uhci4: <UHCI (generic) USB controller> port 0x2020-0x203f irq 19 at
device 29.2 on pci0
uhci4: [GIANT-LOCKED]
uhci4: [ITHREAD]
usb5: <UHCI (generic) USB controller> on uhci4
usb5: USB revision 1.0
usb5: root hub problem, error=4
ehci1: <EHCI (generic) USB 2.0 controller> mem 0x9ba21000-0x9ba213ff irq
17 at device 29.7 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb6: EHCI version 1.0
usb6: companion controllers, 2 ports each: usb3 usb4 usb5
usb6: <EHCI (generic) USB 2.0 controller> on ehci1
usb6: USB revision 2.0
uhub3: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb6
uhub3: 6 ports with 6 removable, self powered
ukbd0: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on
uhub3
kbd2 at ukbd0
uhid0: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on
uhub3
uhid1: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2> on
uhub3
umass0: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2>
on uhub3
umass1: <IBM IBM Composite Device-0, class 0/0, rev 2.00/0.00, addr 2>
on uhub3
axe0: <vendor 0x2001 product 0x1a00, class 2/0, rev 2.00/10.01, addr 3>
on uhub3
axe0: AX88172, bufsz 1536, boundary 64
miibus0: <MII bus> on axe0
rlphy0: <IC Plus 10/100 PHY> PHY 3 on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
axe0: WARNING: using obsoleted if_watchdog interface
axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag
axe0: Ethernet address: 00:80:c8:38:15:ff
pcib8: <PCI-PCI bridge> at device 30.0 on pci0
pci31: <PCI bus> on pcib8
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ATA controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20f0-0x20ff,0x20e0-0x20ef irq 16
at device 31.2 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
atapci1: <Intel ATA controller> port
0x2108-0x210f,0x2124-0x2127,0x2100-0x2107,0x2120-0x2123,0x20d0-0x20df,0x20c0-0x20cf
irq 21 at device 31.5 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A, console
sio0: [FILTER]
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
cpu3: <ACPI CPU> on acpi0
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ukbd1: <Microsoft Comfort Curve Keyboard 2000, class 0/0, rev 2.00/1.73,
addr 2> on uhub0
kbd3 at ukbd1
uhid2: <Microsoft Comfort Curve Keyboard 2000, class 0/0, rev 2.00/1.73,
addr 2> on uhub0
Timecounters tick every 1.000 msec
da0 at mpt0 bus 0 target 1 lun 0
da0: <ATA WD3000BLFS-23YBU 4V04> Fixed Direct Access SCSI-5 device
da0: 300.000MB/s transfers
da0: Command Queueing Enabled
da0: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C)
cd0 at umass-sim0 bus 0 target 0 lun 0
cd0: <Linux Virtual CD/DVD 0316> Removable CD-ROM SCSI-0 device
cd0: 40.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
da1 at mpt0 bus 0 target 2 lun 0
da1: <ATA WD3000BLFS-23YBU 4V04> Fixed Direct Access SCSI-5 device
da1: 300.000MB/s transfers
da1: Command Queueing Enabled
da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C)
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
da2 at umass-sim1 bus 1 target 0 lun 0
da2: <Linux Virtual Floppy 0316> Removable Direct Access SCSI-0 device
da2: 40.000MB/s transfers
da2: Attempt to query device size failed: NOT READY, Medium not present
da3 at umass-sim1 bus 1 target 0 lun 1
da3: <Linux Virtual Floppy 0316> Removable Direct Access SCSI-0 device
da3: 40.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present
Trying to mount root from ufs:/dev/da0s1a

Charles Owens
Great Bay Software

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Panic possibly related to glabel/geom and siis(4)

2009-11-24T09:40:02Z

I have a system running 8.0-PRERELEASE with multiple drives and SATA
port multipliers (siis controllers and PMPs). All of the attached
drives are labeled via glabel(8) and then included into a ZFS pool.
During some testing to determine how the system would react to a dead
drive (simulated by physically removing a drive during operation), I
was able to produce a panic.

Now, I know that the SATA PMP and siis(4) code to handle and recover
from device errors is incomplete, but I believe the crash may be
particular to using glabel'd drives. Basically, after removing a drive
while the zpool is in use and issues 'camcontrol reset' and 'rescan' on
the appropriate bus, the physical device associated with the drive
disappears. In this case:
(pass5:siisch7:0:15:0): lost device
(pass5:siisch7:0:15:0): removing device entry
(ada2:siisch7:0:0:0): lost device

and /dev/ada2 disappears. However, the associated glabel
/dev/label/bigdisk07 remains. Since my ZFS pool is created based on the
drive glabels, I believe this is why ZFS never notices the drives
disappear either.

Do glabels typically go away after a physical device is lost? Should
this not be the case?

After some runtime with the physical device missing, a kernel panic is
produced:

ada2:siisch7:0:0:0): Synchronize cache failed
(ada2:siisch7:0:0:0): removing device entry

Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 14
fault virtual address = 0x48
fault code = supervisor write data, page not present
instruction pointer = 0x20:0xffffffff8035f375
stack pointer = 0x28:0xffffff800006db60
frame pointer = 0x28:0xffffff800006db70
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 2 (g_event)
[thread pid 2 tid 100014 ]
Stopped at _mtx_lock_flags+0x15: lock cmpxchgq %rsi,0x18(%rdi)
db> bt
Tracing pid 2 tid 100014 td 0xffffff00014d4ab0
_mtx_lock_flags() at _mtx_lock_flags+0x15
vdev_geom_release() at vdev_geom_release+0x33
vdev_geom_orphan() at vdev_geom_orphan+0x15c
g_run_events() at g_run_events+0x104
g_event_procbody() at g_event_procbody+0x55
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff800006dd30, rbp = 0 ---

I'm open to try patches and other suggestions. Thanks.
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: PCIe-x1 SATA controllers (was: Re: Adaptec 1405 on FreeBSD )

2009-11-24T01:00:10Z

Dieter wrote:

>>From what I can see, FreeBSD does not support the Marvell 88SE61xx
> SATA controllers?
>
> For example, the SATA2-PCIE1x12 has 4 SATA ports + 1 PATA channel,
> for US$30.13
> http://www.span.com/product_info.php?cPath=24_714_2502&products_id=16957
> There is a similar SATA2-PCIE1X11 board with all ports internal.
>
> http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets
> points to a patch for OpenBSD:
> http://www.webservertalk.com/message2133676.html
> and apparently penguinix supports them.

I have merged support for 88SE61xx SATA to 8-STABLE last days. I have no
plans to merge it lower.

--
Alexander Motin
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

PCIe-x1 SATA controllers (was: Re: Adaptec 1405 on FreeBSD )

2009-11-23T18:57:51Z

In message <4B027C3E.7020700@...>, Alexander Motin writes:
> >>>>> - SiI3124-based - fast and functional. It is actually PCI-X one, but
> >>>>> there are many boards with built-in PCIe bridges.
> >>> Do any of these fit in a x1 slot?
> >> I was surprised, but yes.
> >
> > My google-fu fails me. Any make/model, URLs, or keywords?
>
> Syba PCI Express SATA II 4 x Ports RAID Controller Card SY-PEX40008

Does anyone other than Syba make these? I'm a bit leery of Syba
after my experience with some of their other fine products.

Reviews on newegg say it "Gets a bit hot" and "gets quite hot under load",
despite that big heatsink.
http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16816124027
----------
> The interesting fact I have seen yesterday, SiI3132 is able to read
> 150MB/s, but write 170MB/s. I am not PCIe expert, but looks like
> transfer capabilities could be asymmetric. Also, and as soon as PCIe is
> duplex, I've also seen 110MB/s read from one drive, plus 100MB/s write
> to another, running at the same time.

Seems odd.
----------
>From what I can see, FreeBSD does not support the Marvell 88SE61xx
SATA controllers?

For example, the SATA2-PCIE1x12 has 4 SATA ports + 1 PATA channel,
for US$30.13
http://www.span.com/product_info.php?cPath=24_714_2502&products_id=16957
There is a similar SATA2-PCIE1X11 board with all ports internal.

http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets
points to a patch for OpenBSD:
http://www.webservertalk.com/message2133676.html
and apparently penguinix supports them.
----------
Then we have this oddball, 2 SATA-300 ports + 2 SATA-150 ports:
SYBA SY-PEX40013
http://www.newegg.com/Product/Product.aspx?Item=N82E16816124029
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

No "boot0" menu on Soekris, net5501 vs net4521

2009-11-23T08:47:18Z

Hello,

We're working with two different Soekris models (net5501 and net4521),
working withFreeBSD 7.1 (nanobsd). We've found that the two models
exhibit different boot behavior. Summary: the 4521 works fine, and
the 5501 doesn't seem right. Here's what we see when we boot either:

net4521 (BIOS ver 1.33) --

* "boot0" menu appears (letting you pick either of two FreeBSD slices)
* OS loads properly from chosen or default slice

net5501 (BIOS ver 1.33c) --

* "boot0" menu does _not_ appear.
* system boots directly to slice 1 or 2, as chosen via BIOS option
BootPartition

Have others seen this behavior? For our application, we really need the
5501 to boot just like the 4521. Is this a bug (in BIOS, I'm guessing),
or am I doing something wrong? It seems like there should be a way to
clear the BootPartition setting, or set it to "MBR" or somesuch.

Thanks very much,

Charles

--

**Charles Owens**
*Great Bay Software*******

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Pulse Meter with Cellular communication

2009-11-21T18:37:45Z

This is a message in multipart MIME format. Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly.

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

USB keyboard flaky with PAE kernel, 7.1

2009-11-20T13:47:56Z

Howdy,

I'm still digging into it, put preliminary testing is showing that with
a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only
occasionally, if you're lucky. This flakiness is being seen with
several different server models that we support (HP and IBM, all Xeon
based). If we boot a non-PAE kernel then the USB keyboard is rock solid.

For what it's worth (probably little) I can run the same PAE kernel on
an old Pentium II system and a USB keyboard works fine.

What is the best way to dig into this? Any and all assistance greatly
appreciated. I can provide remote access to a testbed of these systems
if useful.

Charles

(And, yes, I do know that amd64 is better than PAE for various obvious
reasons. ;-) )

--

**Charles Owens**
*Great Bay Software**|** ***www.GreatBaySoftware.com****

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Looking for a tiny embedded system that supports *BSD

2009-11-19T22:51:54Z

On 2009-Nov-17 20:32:06 -0500, Maxim Khitrov <mkhitrov@...> wrote:
>A project I'm working on requires a really small box (at most 15x9x3cm
>in size, but ideally smaller) that's capable of running one of the
>four BSDs.
>
>The catch is that it must have its own battery supply capable of
>powering the system for at least 5 hours. The other major requirements
>are one RS-232 and at least one USB ports.

If (as I read it), the battery needs to be inside the 15x9x3cm box,
the 5hr battery requirement is going to make this very difficult using
x86 hardware. You probably need to look at something ARM based or
maybe something like gumstix.com (though I don't know if the latter is
supported by any *BSD).

> The battery should be
>recharged through the USB port.

This implies quite a low power consumption since USB 2 is restricted
to 500mA per port - or 2.5W to charge the battery and presumably power
the device.

Is there a specific requirement for BSD? Based on what you've said,
it would be far easier to meet the physical dimension and power
requirements using something like a PIC or Atmel microcontroller.

--
Peter Jeremy

attachment0 (203 bytes) Download Attachment

Re: what is the good geometry for disk WD10EADS

2009-11-19T06:10:38Z

few more info:

On 19 nov. 2009, at 14:46, Patrick Proniewski wrote:

> And mounting the formated disk fails (121601/255/63):
>
> # mount /dev/ad6s1c /backup
> mount: /dev/ad6s1c on /backup: incorrect super block

This is obviously wrong, 'c' partition represents the slice, and
should not be available for mounting. I've messed up with fdisk/
disklabel (forgot to quit sysinstall between the two steps).

I've found a japanese site <http://d.hatena.ne.jp/sillywalk7/20090307>
that states that the correct geometry for WD10EADS could be
16383/16/63 (if the google translation is ok).
I've tried, and so far the disk properly mounts.

I'm still interested in a way to get the right geometry on FreeBSD,
for this drive.

patpro

what is the good geometry for disk WD10EADS

2009-11-19T05:46:10Z

Hello,

I've just added a WD10EADS disk in my FreeBSD box (<http://www.wdc.com/en/products/Products.asp?DriveID=559
>)

My mother board is few years old and supports only SATA I, so the
drive is recognized as SATA150 (which is fine):

ad6: 953869MB <WDC WD10EADS-00M2B0 01.00A01> at ata3-master SATA150

Unfortunately, I'm unable to find the right geometry in order to
format/label the disk. Using sysintall interface to handle the new
disk yields to this kind of alerts:

(1st alert) WARNING: A geometry of 1938021/16/63 for ad6 is
incorrect ...
(2nd alert) WARNING: A geometry of 121601/255/63 for ad6 is
incorrect ...
(3rd alert) WARNING: A geometry of 121601/255/63 for ad6 is
incorrect ...
(ad lib)

So, the software tries to guess the right geometry, but fails and
stick with wrong numbers (121601/255/63)

I have this:

# diskinfo -v ad6
ad6
512 # sectorsize
1000204886016 # mediasize in bytes (932G)
1953525168 # mediasize in sectors
1938021 # Cylinders according to firmware.
16 # Heads according to firmware.
63 # Sectors according to firmware.

But fdisk thinks it's not good.

And mounting the formated disk fails (121601/255/63):

# mount /dev/ad6s1c /backup
mount: /dev/ad6s1c on /backup: incorrect super block

I don't know where to look, the BIOS says nothing about the geometry
(unless I've missed something). It's on LBA mode.

patpro

Re: Looking for a tiny embedded system that supports *BSD

2009-11-18T10:32:32Z

In message <alpine.BSF.2.00.0911181232270.10412@...>, Peter Beckman
writes:
>On Wed, 18 Nov 2009, Maxim Khitrov wrote:

> http://www.epn-online.com/page/35052/130w-battery-backup-psu.html

For the effects we are talking about, this is much more relevant:

http://www.mini-box.com/DC-DC

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@... | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Looking for a tiny embedded system that supports *BSD

2009-11-18T09:35:08Z

On Wed, 18 Nov 2009, Maxim Khitrov wrote:

> These weren't designed for use with a battery. That's the most
> difficult part of finding what I need. There are plenty boards out
> there that have all the right features, but so far I couldn't find
> anything that can work for a few hours without an AC power source.

Don't look for a whole computer that meets your needs, start looking for
computers that meet your needs and then look for a PSU that can accept a
battery input.

http://www.epn-online.com/page/35052/130w-battery-backup-psu.html

Not sure if Google uses a PSU from a commercial manufacturer or rolls
their own, but their PSU's have a built in battery for each racked
computer.

---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman@... http://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Re: Looking for a tiny embedded system that supports *BSD

2009-11-18T03:20:19Z

2009/11/18 Jiří Smejkal <Jiri.Smejkal@...>:

> -----Original Message-----
> From: owner-freebsd-hardware@... [mailto:owner-freebsd-hardware@...] On Behalf Of Maxim Khitrov
> Sent: Wednesday, November 18, 2009 2:32 AM
> To: freebsd-hardware@...
> Subject: Looking for a tiny embedded system that supports *BSD
>
> Hello all,
>
> A project I'm working on requires a really small box (at most 15x9x3cm
> in size, but ideally smaller) that's capable of running one of the
> four BSDs.
>
> The catch is that it must have its own battery supply capable of
> powering the system for at least 5 hours. The other major requirements
> are one RS-232 and at least one USB ports. The battery should be
> recharged through the USB port. If there is a separate power cord, I
> will have to somehow join it and the usb cable into a single non-usb
> connector (which I'd like to avoid if at all possible). Finally, it
> must support some kind of removable storage (e.g. CF card).
>
> This system will essentially be a portable translator of one type of
> communication protocol to another with data flowing between the RS-232
> and USB ports. Obviously, I don't need any video output or any kind of
> input. Just need a tiny box with two cables coming out of it. Do you
> know of anything that might work?
>
> - Max
>
> Hi Maxim,
>
> What about ALIX 3D board www.pcengines.ch - 160x100x25mm, 500MHz AMD Geode LX2. I'm using it with FBSD 6,7,8. Single power supply 7-20V - ideal for Pb accu.
>
> Jiri Smejkal

These weren't designed for use with a battery. That's the most
difficult part of finding what I need. There are plenty boards out
there that have all the right features, but so far I couldn't find
anything that can work for a few hours without an AC power source.

- Max
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

RE: Looking for a tiny embedded system that supports *BSD

2009-11-18T01:36:56Z

Hi Maxim,

What about ALIX 3D board www.pcengines.ch - 160x100x25mm, 500MHz AMD Geode LX2. I'm using it with FBSD 6,7,8. Single power supply 7-20V - ideal for Pb accu.

Jiri Smejkal

-----Original Message-----
From: owner-freebsd-hardware@... [mailto:owner-freebsd-hardware@...] On Behalf Of Maxim Khitrov
Sent: Wednesday, November 18, 2009 2:32 AM
To: freebsd-hardware@...
Subject: Looking for a tiny embedded system that supports *BSD

Hello all,

A project I'm working on requires a really small box (at most 15x9x3cm
in size, but ideally smaller) that's capable of running one of the
four BSDs.

The catch is that it must have its own battery supply capable of
powering the system for at least 5 hours. The other major requirements
are one RS-232 and at least one USB ports. The battery should be
recharged through the USB port. If there is a separate power cord, I
will have to somehow join it and the usb cable into a single non-usb
connector (which I'd like to avoid if at all possible). Finally, it
must support some kind of removable storage (e.g. CF card).

This system will essentially be a portable translator of one type of
communication protocol to another with data flowing between the RS-232
and USB ports. Obviously, I don't need any video output or any kind of
input. Just need a tiny box with two cables coming out of it. Do you
know of anything that might work?

- Max
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."

Looking for a tiny embedded system that supports *BSD

2009-11-17T17:32:06Z

Hello all,

A project I'm working on requires a really small box (at most 15x9x3cm
in size, but ideally smaller) that's capable of running one of the
four BSDs.

The catch is that it must have its own battery supply capable of
powering the system for at least 5 hours. The other major requirements
are one RS-232 and at least one USB ports. The battery should be
recharged through the USB port. If there is a separate power cord, I
will have to somehow join it and the usb cable into a single non-usb
connector (which I'd like to avoid if at all possible). Finally, it
must support some kind of removable storage (e.g. CF card).

This system will essentially be a portable translator of one type of
communication protocol to another with data flowing between the RS-232
and USB ports. Obviously, I don't need any video output or any kind of
input. Just need a tiny box with two cables coming out of it. Do you
know of anything that might work?

- Max
_______________________________________________
freebsd-hardware@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@..."