From won.derick at yahoo.com  Mon Dec  1 00:00:17 2008
From: won.derick at yahoo.com (Won De Erick)
Date: Mon Dec  1 00:00:36 2008
Subject: Watchdog for Boser (HS-7001)
Message-ID: <547602.79284.qm@web45809.mail.sp1.yahoo.com>

Hello,

I was trying the assembly language program that is specified in the following document (p24) to set, reset the built-in watchdog timer for the Boser Box.

http://www.boser.com.tw/manual/HS-7001v1.1.pdf

I then installed nasm in FreeBSD 6.2, and added the following lines at the beginning.

section .text
  global _start

  _start:

I did assemble, link (ld) and got no error. But when I run, I got the following error:

# ./watchdog.out
Bus error (core dumped)

I noticed that the port addresses used are similar with the following used by Super Micro Computer. I don't know if these are standards or not. I suspect that the boards are using same controller chips from Intel. I've been googling the web for more documentations on these but I could hardly find one.

http://www.stinkfoot.org/wdt.txt

How should I make this program works?

Thanks,

Won


# dmesg
Copyright (c) 1992-2007 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 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007
    root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: <IntelR AWRDACPI>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2799.21-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
  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=0x4400<CNTX-ID,<b14>>
real memory  = 528416768 (503 MB)
avail memory = 507666432 (484 MB)
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <IntelR AWRDACPI> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <Intel 82845G (845G GMCH) SVGA controller> mem 0xe0000000-0xe7ffffff,0xec700000-0xec77ffff irq 16 at device 2.0 on pci0
agp0: detected 8060k stolen memory
agp0: aperture size is 128M
uhci0: <Intel 82801DB (ICH4) USB controller USB-A> port 0xe200-0xe21f irq 16 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 82801DB (ICH4) USB controller USB-B> port 0xe000-0xe01f irq 19 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 82801DB (ICH4) USB controller USB-C> port 0xe100-0xe11f irq 18 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0: <Intel 82801DB/L/M (ICH4) USB 2.0 controller> mem 0xec780000-0xec7803ff irq 23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: <Intel 82801DB/L/M (ICH4) USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 6 ports with 6 removable, self powered
pcib1: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci1: <ACPI PCI bus> on pcib1
fxp0: <Intel 82801DB (ICH4) Pro/100 Ethernet> port 0xd100-0xd13f mem 0xec680000-0xec680fff irq 20 at device 8.0 on pci1
miibus0: <MII bus> on fxp0
inphy0: <i82562ET 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:50:b7:f2:40:ea
em0: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port 0xd000-0xd03f mem 0xec620000-0xec63ffff,0xec600000-0xec61ffff irq 18 at device 9.0 on pci1
em0: Ethernet address: 00:50:b7:f2:40:eb
pci1: <network> at device 12.0 (no driver attached)
pci1: <network> at device 13.0 (no driver attached)
pcib2: <PCI-PCI bridge> at device 15.0 on pci1
pci2: <PCI bus> on pcib2
fxp1: <Intel 82559 Pro/100 Ethernet> port 0xc000-0xc03f mem 0xec502000-0xec502fff,0xec000000-0xec0fffff irq 23 at device 0.0 on pci2
miibus1: <MII bus> on fxp1
inphy1: <i82555 10/100 media interface> on miibus1
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:50:b7:f2:37:74
fxp2: <Intel 82559 Pro/100 Ethernet> port 0xc100-0xc13f mem 0xec500000-0xec500fff,0xec100000-0xec1fffff irq 20 at device 1.0 on pci2
miibus2: <MII bus> on fxp2
inphy2: <i82555 10/100 media interface> on miibus2
inphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp2: Ethernet address: 00:50:b7:f2:37:73
fxp3: <Intel 82559 Pro/100 Ethernet> port 0xc200-0xc23f mem 0xec503000-0xec503fff,0xec200000-0xec2fffff irq 21 at device 2.0 on pci2
miibus3: <MII bus> on fxp3
inphy3: <i82555 10/100 media interface> on miibus3
inphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp3: Ethernet address: 00:50:b7:f2:37:72
fxp4: <Intel 82559 Pro/100 Ethernet> port 0xc300-0xc33f mem 0xec501000-0xec501fff,0xec300000-0xec3fffff irq 22 at device 3.0 on pci2
miibus4: <MII bus> on fxp4
inphy4: <i82555 10/100 media interface> on miibus4
inphy4:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp4: Ethernet address: 00:50:b7:f2:37:71
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH4 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
pci0: <multimedia, audio> at device 31.5 (no driver attached)
acpi_tz0: <Thermal Zone> on acpi0
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0: <Standard parallel printer port> port 0x378-0x37f,0x778-0x77b irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sio2: <16550A-compatible COM port> port 0x3e8-0x3ef irq 10 on acpi0
sio2: type 16550A
sio3: <16550A-compatible COM port> port 0x2e8-0x2ef irq 11 on acpi0
sio3: type 16550A
pmtimer0 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
Timecounter "TSC" frequency 2799213056 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 1946MB <TOSHIBA THNCF2G04QG 3.00> at ata0-master PIO4
Trying to mount root from ufs:/dev/ad0s1a
pid 17016 (watchdog.out), uid 0: exited on signal 10 (core dumped)
pid 17032 (watchdog.out), uid 0: exited on signal 10 (core dumped)



      

From christoph.mallon at gmx.de  Mon Dec  1 01:05:35 2008
From: christoph.mallon at gmx.de (Christoph Mallon)
Date: Mon Dec  1 01:05:42 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
Message-ID: <4933A29B.8060907@gmx.de>

Won De Erick schrieb:
> Hello,
> 
> I was trying the assembly language program that is specified in the following document (p24) to set, reset the built-in watchdog timer for the Boser Box.
> 
> http://www.boser.com.tw/manual/HS-7001v1.1.pdf
> 
> I then installed nasm in FreeBSD 6.2, and added the following lines at the beginning.
> 
> section .text
>   global _start
> 
>   _start:
> 
> I did assemble, link (ld) and got no error. But when I run, I got the following error:
> 
> # ./watchdog.out
> Bus error (core dumped)

> MOV DX, 2EH
> MOV AL, 87H
> OUT DX, AL
> OUT DX, AL

Userland is not allowed to write to ports. That's the bus error you see. 
Also without a call to the exit syscall at the end, it will segfault.

Regards
	Christoph
From won.derick at yahoo.com  Mon Dec  1 01:20:16 2008
From: won.derick at yahoo.com (Won De Erick)
Date: Mon Dec  1 01:20:29 2008
Subject: Watchdog for Boser (HS-7001)
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu>
Message-ID: <611173.7111.qm@web45805.mail.sp1.yahoo.com>

> ----- Original Message ----

> From: Rink Springer <rink@FreeBSD.org>
> 
> 
On Mon, Dec 01, 2008 at 09:38:51AM +0100, Christoph Mallon wrote:
> > Userland is not allowed to write to ports. That's the bus error you see. 
> > Also without a call to the exit syscall at the end, it will segfault.
> 
> Note that you can write to ports from userland by opening /dev/io - if
> you have it opened, you can write to the ports.
> 

I've added the following at the end

  mov eax, 1 ; SYS_exit
  call doint

  doint:
     int 0x80
     ret

Besides, I can see the following at /dev
crw-------   1 root   wheel       0,  16 Nov 27 01:53 io

How should I make this open? do i need to %include this?


> -- 
> Rink P.W. Springer                                - http://rink.nu
> "Anyway boys, this is America. Just because you get more votes doesn't
>  mean you win." - Fox Mulder
> 



      

From rink at FreeBSD.org  Mon Dec  1 01:22:20 2008
From: rink at FreeBSD.org (Rink Springer)
Date: Mon Dec  1 01:22:25 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <4933A29B.8060907@gmx.de>
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de>
Message-ID: <20081201090421.GA99082@rink.nu>

On Mon, Dec 01, 2008 at 09:38:51AM +0100, Christoph Mallon wrote:
> Userland is not allowed to write to ports. That's the bus error you see. 
> Also without a call to the exit syscall at the end, it will segfault.

Note that you can write to ports from userland by opening /dev/io - if
you have it opened, you can write to the ports.

-- 
Rink P.W. Springer                                - http://rink.nu
"Anyway boys, this is America. Just because you get more votes doesn't
 mean you win." - Fox Mulder
From rink at FreeBSD.org  Mon Dec  1 01:26:46 2008
From: rink at FreeBSD.org (Rink Springer)
Date: Mon Dec  1 01:26:53 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <611173.7111.qm@web45805.mail.sp1.yahoo.com>
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu>
	<611173.7111.qm@web45805.mail.sp1.yahoo.com>
Message-ID: <20081201092720.GB99082@rink.nu>

On Mon, Dec 01, 2008 at 01:20:14AM -0800, Won De Erick wrote:
> Besides, I can see the following at /dev
> crw-------   1 root   wheel       0,  16 Nov 27 01:53 io
> 
> How should I make this open? do i need to %include this?

No, you need to invoke an open syscall just in the same way you did the
previous system call. Try looking at
http://goodfellas.shellcode.com.ar/docz/asm/aslenguage.html, which is a
tutorial for exactly this sort of thing.

You don't have to read or write to it; just opening it is enough to get
the I/O access you need.

Regards,

-- 
Rink P.W. Springer                                - http://rink.nu
"Anyway boys, this is America. Just because you get more votes doesn't
 mean you win." - Fox Mulder

> 
> 
> > -- 
> > Rink P.W. Springer                                - http://rink.nu
> > "Anyway boys, this is America. Just because you get more votes doesn't
> >  mean you win." - Fox Mulder
> > 
> 
> 
> 
>       
> 
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
From christoph.mallon at gmx.de  Mon Dec  1 01:35:36 2008
From: christoph.mallon at gmx.de (Christoph Mallon)
Date: Mon Dec  1 01:35:47 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <611173.7111.qm@web45805.mail.sp1.yahoo.com>
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>	<4933A29B.8060907@gmx.de>
	<20081201090421.GA99082@rink.nu>
	<611173.7111.qm@web45805.mail.sp1.yahoo.com>
Message-ID: <4933AFD4.3070501@gmx.de>

Won De Erick schrieb:
>> ----- Original Message ----
> 
>> From: Rink Springer <rink@FreeBSD.org>
>>
>>
> On Mon, Dec 01, 2008 at 09:38:51AM +0100, Christoph Mallon wrote:
>>> Userland is not allowed to write to ports. That's the bus error you see. 
>>> Also without a call to the exit syscall at the end, it will segfault.
>> Note that you can write to ports from userland by opening /dev/io - if
>> you have it opened, you can write to the ports.
>>
> 
> I've added the following at the end
> 
>   mov eax, 1 ; SYS_exit
>   call doint
> 
>   doint:
>      int 0x80
>      ret
> 
> Besides, I can see the following at /dev
> crw-------   1 root   wheel       0,  16 Nov 27 01:53 io
> 
> How should I make this open? do i need to %include this?

You're probably better of writing this in C. Here is a wrapper for the 
out instruction:

static inline outb(unsigned short port, unsigned char data)
{
   asm("outb %0, %1" : : "a" (data), "dN" (port));
}

As Rink mentioned, you have to open /dev/io. The process must have 
super-user privileges, see io(4).

Regards
	Christoph
From des at des.no  Mon Dec  1 04:14:53 2008
From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=)
Date: Mon Dec  1 04:15:02 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <4933AFD4.3070501@gmx.de> (Christoph Mallon's message of "Mon, 01
	Dec 2008 10:35:16 +0100")
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu>
	<611173.7111.qm@web45805.mail.sp1.yahoo.com> <4933AFD4.3070501@gmx.de>
Message-ID: <86fxl8qf8i.fsf@ds4.des.no>

Christoph Mallon <christoph.mallon@gmx.de> writes:
> You're probably better of writing this in C.

He's probably better off writing a watchdog(4) driver for the Boser (or
getting someone to write one for him - not easy to do without hardware
to test on, though)

DES
-- 
Dag-Erling Sm?rgrav - des@des.no
From gary.jennejohn at freenet.de  Mon Dec  1 04:19:16 2008
From: gary.jennejohn at freenet.de (Gary Jennejohn)
Date: Mon Dec  1 04:19:23 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <4933A29B.8060907@gmx.de>
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de>
Message-ID: <20081201131912.355b8356@ernst.jennejohn.org>

On Mon, 01 Dec 2008 09:38:51 +0100
Christoph Mallon <christoph.mallon@gmx.de> wrote:

> Won De Erick schrieb:
> > Hello,
> > 
> > I was trying the assembly language program that is specified in the following document (p24) to set, reset the built-in watchdog timer for the Boser Box.
> > 
> > http://www.boser.com.tw/manual/HS-7001v1.1.pdf
> > 
> > I then installed nasm in FreeBSD 6.2, and added the following lines at the beginning.
> > 
> > section .text
> >   global _start
> > 
> >   _start:
> > 
> > I did assemble, link (ld) and got no error. But when I run, I got the following error:
> > 
> > # ./watchdog.out
> > Bus error (core dumped)
> 
> > MOV DX, 2EH
> > MOV AL, 87H
> > OUT DX, AL
> > OUT DX, AL
> 
> Userland is not allowed to write to ports. That's the bus error you see. 
> Also without a call to the exit syscall at the end, it will segfault.
> 

See io(4), i386_get_ioperm(2), i386_set_ioperm(2), mem(4).

---
Gary Jennejohn
From won.derick at yahoo.com  Mon Dec  1 04:48:34 2008
From: won.derick at yahoo.com (Won De Erick)
Date: Mon Dec  1 04:48:44 2008
Subject: Watchdog for Boser (HS-7001)
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu>
	<611173.7111.qm@web45805.mail.sp1.yahoo.com>
	<4933AFD4.3070501@gmx.de> <86fxl8qf8i.fsf@ds4.des.no>
Message-ID: <576032.29521.qm@web45815.mail.sp1.yahoo.com>

> ----- Original Message ----

> From: Dag-Erling Sm?rgrav <des@des.no>
> Christoph Mallon <christoph.mallon@gmx.de> writes:
> > You're probably better of writing this in C.
maybe i get this as an option.
> 
> He's probably better off writing a watchdog(4) driver for the Boser (or
> getting someone to write one for him - not easy to do without hardware
> to test on, though)
> 
this is a great info. i am used to settings like the following when using ipmi-compliant platform.
#bmc-watchdog -s -a 1 -i 100    (#set timeout action to hard reset after a timeout of 100 seconds)
then daemonize to constantly reset the timer, and prevent the box from restarting.

I installed watchdog(/usr/ports/sysutils/watchdog) from ports, then noticed the following from the manual.
     watchdog [-d] [-t timeout]

# watchdog -d -t 50
Timeout is 2^36 nanoseconds
watchdog: patting the dog: Operation not supported

but I don't know how it is linked with watchdogd(8).

Little more explanation is appreciated, and/or an example.

> DES
> -- 
> Dag-Erling Sm?rgrav - des@des.no


      

From won.derick at yahoo.com  Mon Dec  1 04:52:44 2008
From: won.derick at yahoo.com (Won De Erick)
Date: Mon Dec  1 04:52:51 2008
Subject: Watchdog for Boser (HS-7001)
Message-ID: <838497.65099.qm@web45808.mail.sp1.yahoo.com>

>----- Original Message ----

>From: Christoph Mallon <christoph.mallon@gmx.de>
>
>
Won De Erick schrieb:
>>> ----- Original Message ----
>> 
>>> From: Rink Springer <rink@FreeBSD.org>
>>> 
>>> 
>> On Mon, Dec 01, 2008 at 09:38:51AM +0100, Christoph Mallon wrote:
>>>> Userland is not allowed to write to ports. That's the bus error you see. Also without a call to the exit syscall at the end, it will segfault.
>>> Note that you can write to ports from userland by opening /dev/io - if
>>> you have it opened, you can write to the ports.
>>> 
>> 
>> I've added the following at the end
>> 
>>   mov eax, 1 ; SYS_exit
>>   call doint
>> 
>>   doint:
>>      int 0x80
>>      ret
>> 
>> Besides, I can see the following at /dev
>> crw-------   1 root   wheel       0,  16 Nov 27 01:53 io
>> 
>> How should I make this open? do i need to %include this?
>
>You're probably better of writing this in C. Here is a wrapper for the out instruction:
>
>static inline outb(unsigned short port, unsigned char data)
>{
>  asm("outb %0, %1" : : "a" (data), "dN" (port));
>}
>
>As Rink mentioned, you have to open /dev/io. The process must have super-user privileges, see io(4).

will this be ok?

int fd = open("/dev/fido", O_RDWR);


>
>Regards
>    Christoph



      

From won.derick at yahoo.com  Mon Dec  1 05:07:39 2008
From: won.derick at yahoo.com (Won De Erick)
Date: Mon Dec  1 05:07:51 2008
Subject: Watchdog for Boser (HS-7001)
Message-ID: <839504.20277.qm@web45816.mail.sp1.yahoo.com>

>From: Won De Erick <won.derick@yahoo.com>

>>From: Christoph Mallon <christoph.mallon@gmx.de>
>>
>
>Won De Erick schrieb:
>>>> ----- Original Message ----
>>> 
>>>> From: Rink Springer <rink@FreeBSD.org>
>>>> 
>>>> 
>>> On Mon, Dec 01, 2008 at 09:38:51AM +0100, Christoph Mallon wrote:
>>>>> Userland is not allowed to write to ports. That's the bus error you see. Also without a call to the exit syscall at the end, it will segfault.
>>>> Note that you can write to ports from userland by opening /dev/io - if
>>>> you have it opened, you can write to the ports.
>>>> 
>>> 
>>> I've added the following at the end
>>> 
>>>   mov eax, 1 ; SYS_exit
>>>   call doint
>>> 
>>>   doint:
>>>      int 0x80
>>>      ret
>>> 
>>> Besides, I can see the following at /dev
>>> crw-------   1 root   wheel       0,  16 Nov 27 01:53 io
>>> 
>>> How should I make this open? do i need to %include this?
>>
>>You're probably better of writing this in C. Here is a wrapper for the out instruction:
>>
>>static inline outb(unsigned short port, unsigned char data)
>>{
>>  asm("outb %0, %1" : : "a" (data), "dN" (port));
>>}
>>
>>As Rink mentioned, you have to open /dev/io. The process must have super-user privileges, see io(4).
>
>will this be ok?
>int fd = open("/dev/fido", O_RDWR);
>
aww.. i mean int sio = open("/dev/io", O_RDWR);
>
>>
>>Regards
>>    Christoph


      

From des at des.no  Mon Dec  1 05:32:28 2008
From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=)
Date: Mon Dec  1 05:32:41 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <576032.29521.qm@web45815.mail.sp1.yahoo.com> (Won De Erick's
	message of "Mon, 1 Dec 2008 04:48:31 -0800 (PST)")
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu>
	<611173.7111.qm@web45805.mail.sp1.yahoo.com> <4933AFD4.3070501@gmx.de>
	<86fxl8qf8i.fsf@ds4.des.no>
	<576032.29521.qm@web45815.mail.sp1.yahoo.com>
Message-ID: <867i6kqavq.fsf@ds4.des.no>

Won De Erick <won.derick@yahoo.com> writes:
> this is a great info. i am used to settings like the following when using ipmi-compliant platform.
> #bmc-watchdog -s -a 1 -i 100    (#set timeout action to hard reset after a timeout of 100 seconds)
> then daemonize to constantly reset the timer, and prevent the box from restarting.
>
> I installed watchdog(/usr/ports/sysutils/watchdog) from ports,

Firt of all, that port won't help you; it only supports the AMD Elan
SoC.  Second, we've had kernel support for the Elan watchdog longer than
the port has existed.

> then noticed the following from the manual.
>      watchdog [-d] [-t timeout]

That's the base system watchdog(8); the port installs a watchdogd(8)
that works *only* for Elan chips.

There is a watchdogd(8) in the base system as well.

> # watchdog -d -t 50
> Timeout is 2^36 nanoseconds
> watchdog: patting the dog: Operation not supported

You need to load the appropriate watchdog driver first - and as far as I
know, we don't have one for the Boser HS-7001.

> but I don't know how it is linked with watchdogd(8).
>
> Little more explanation is appreciated, and/or an example.

man -k watchdog

DES
-- 
Dag-Erling Sm?rgrav - des@des.no
From des at des.no  Mon Dec  1 07:55:01 2008
From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=)
Date: Mon Dec  1 07:55:13 2008
Subject: Watchdog for Boser (HS-7001)
In-Reply-To: <867i6kqavq.fsf@ds4.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8rg?=
	=?utf-8?Q?rav=22's?= message of "Mon, 01 Dec 2008 14:32:25 +0100")
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu>
	<611173.7111.qm@web45805.mail.sp1.yahoo.com> <4933AFD4.3070501@gmx.de>
	<86fxl8qf8i.fsf@ds4.des.no>
	<576032.29521.qm@web45815.mail.sp1.yahoo.com>
	<867i6kqavq.fsf@ds4.des.no>
Message-ID: <86myffq4a4.fsf@ds4.des.no>

Dag-Erling Sm?rgrav <des@des.no> writes:
> You need to load the appropriate watchdog driver first - and as far as I
> know, we don't have one for the Boser HS-7001.

I can't find the 7001 on Boser's web site, but their other SBCs seem to
be ICH-based; try 'kldload ichwd'.

DES
-- 
Dag-Erling Sm?rgrav - des@des.no
From jhb at freebsd.org  Mon Dec  1 13:44:32 2008
From: jhb at freebsd.org (John Baldwin)
Date: Mon Dec  1 13:44:39 2008
Subject: ciss0 driver/routines
In-Reply-To: <49328F33.8080705@dannysplace.net>
References: <492D7814.2010302@ccstores.com> <49328F33.8080705@dannysplace.net>
Message-ID: <200812011507.55934.jhb@freebsd.org>

On Sunday 30 November 2008 08:03:47 am Danny Carroll wrote:
> Jim Pazarena wrote:
> > noticed a glaring spelling mistake on a CLI notification, and wasn't
> > sure who (or how) to report it.
> > 
> > message as follows:
> > 
> > ciss0: *** Parity/consistency initialization complete, logical drive 0
> > 
> > then,
> > 
> > ciss0: logical drive 0 c7 completed consistency initialisation
> >                                                ^^^^^^^^^^^^^^^^  s/b
> > initialization
> > 
> 
> 
> Perhaps this driver was written by both an American and a European or
> Australian....
> 
> >From my perspective the first message is the one spelt wrong.

My guess would be the first message is a string from the firmware (using 
American English).  The second message is from the driver which was 
originally written by an Australian.

-- 
John Baldwin
From janm at transactionware.com  Tue Dec  2 03:05:31 2008
From: janm at transactionware.com (Jan Mikkelsen)
Date: Tue Dec  2 03:05:44 2008
Subject: Areca vs. ZFS performance testing.
In-Reply-To: <alpine.BSF.2.00.0811170521320.1488@ibyngvyr.purzvxnyf.bet>
Message-ID: <C22DCA4BBFD54E3E9FE96197E64B0788@STUDYPC>

Hi,

Wes Morgan wrote:
> On Sun, 16 Nov 2008, Matt Simerson wrote:
> 
> > The Areca cards do NOT have the cache enabled by default. I 
> ordered the 
> > optional battery and RAM upgrade for my collection of 
> 1231ML cards. Even with 
> > the BBWC, the cache is not enabled by default. I had to go 
> out of my way to 
> > enable it, on every single controller.
> 
> Are you using these areca cards successfully with large 
> arrays? I found a 
> 1680i card for a decent price and installed it this weekend, 
> but since 
> then I'm seeing the raidz2 pool that it's running hang so 
> frequently that 
> I can't even trust using it. The hangs occur in both 7-stable and 
> 8-current with the new ZFS patch. Same exact settings that 
> have been rock 
> solid for me before now don't want to work at all. The drives 
> are just set 
> as JBOD -- the controller actually defaulted to this, so I 
> didn't have to 
> make any real changes in the BIOS.
> 
> Any tips on your setup? Did you have any similar problems?

I am seeing I/O related lockups on 7.1-PRE with an Areca ARC-1220 controller
and eight drives in a RAID-6 array.  The same hardware works fine with 6.3.

When I run gstat while it is happening I see I/O performance drop and the
time to service each write (ms/w) goes up, and then suddenly goes back down
to a sensible value.  I have seen it get to about 22000ms.

The system is essentially unusable for writes, which limits the utility a
bit.  Reads seem fine.

Is this similar to the behaviour you saw?

Thanks,

Jan Mikkelsen

From morganw at chemikals.org  Tue Dec  2 04:04:37 2008
From: morganw at chemikals.org (Wes Morgan)
Date: Tue Dec  2 04:04:49 2008
Subject: Areca vs. ZFS performance testing.
In-Reply-To: <C22DCA4BBFD54E3E9FE96197E64B0788@STUDYPC>
References: <C22DCA4BBFD54E3E9FE96197E64B0788@STUDYPC>
Message-ID: <alpine.BSF.2.00.0812020601290.96868@ibyngvyr.purzvxnyf.bet>

On Tue, 2 Dec 2008, Jan Mikkelsen wrote:

> Hi,
>
> Wes Morgan wrote:
>> On Sun, 16 Nov 2008, Matt Simerson wrote:
>>
>>> The Areca cards do NOT have the cache enabled by default. I
>> ordered the
>>> optional battery and RAM upgrade for my collection of
>> 1231ML cards. Even with
>>> the BBWC, the cache is not enabled by default. I had to go
>> out of my way to
>>> enable it, on every single controller.
>>
>> Are you using these areca cards successfully with large
>> arrays? I found a
>> 1680i card for a decent price and installed it this weekend,
>> but since
>> then I'm seeing the raidz2 pool that it's running hang so
>> frequently that
>> I can't even trust using it. The hangs occur in both 7-stable and
>> 8-current with the new ZFS patch. Same exact settings that
>> have been rock
>> solid for me before now don't want to work at all. The drives
>> are just set
>> as JBOD -- the controller actually defaulted to this, so I
>> didn't have to
>> make any real changes in the BIOS.
>>
>> Any tips on your setup? Did you have any similar problems?
>
> I am seeing I/O related lockups on 7.1-PRE with an Areca ARC-1220 controller
> and eight drives in a RAID-6 array.  The same hardware works fine with 6.3.
>
> When I run gstat while it is happening I see I/O performance drop and the
> time to service each write (ms/w) goes up, and then suddenly goes back down
> to a sensible value.  I have seen it get to about 22000ms.
>
> The system is essentially unusable for writes, which limits the utility a
> bit.  Reads seem fine.
>
> Is this similar to the behaviour you saw?

Not quite. The zfs deadlock/hang effected both reads and writes, blocking 
either of them indefinitely. They were "fixed" by the most recent set of 
patches in -current.

From todorov at paladin.bulgarpress.com  Wed Dec  3 01:01:24 2008
From: todorov at paladin.bulgarpress.com (Todorov)
Date: Wed Dec  3 01:01:37 2008
Subject: Request for testers: Option 3G cards, also Sierra,	Huawei and
 Novatel
In-Reply-To: <200811071453.07665.nick@van-laarhoven.org>
References: <200810092344.10388.nick@van-laarhoven.org>	<200811051548.mA5Fmsot040177@lava.sentex.ca>	<200811062203.mA6M3ij3048835@lava.sentex.ca>
	<200811071453.07665.nick@van-laarhoven.org>
Message-ID: <49364AE0.90206@paladin.bulgarpress.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I was trying to test my PCMCIA but I got this message :

link_elf: symbol ucom_attach_tty undefined

FreeBSD 7.0-RELEASE-p5 PCMCIA Huawei E630

Please comment,
Thanks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk2SuAACgkQibJkIG65HMdjsQCgjVPuwgymPtLjz6S7OlFSKgO4
OcAAn0Nj4iTky7l+Soj5SMmlQ5IU+bXo
=eAUA
-----END PGP SIGNATURE-----
From pluknet at gmail.com  Wed Dec  3 01:42:27 2008
From: pluknet at gmail.com (pluknet)
Date: Wed Dec  3 01:42:34 2008
Subject: Request for testers: Option 3G cards, also Sierra,
	Huawei and Novatel
In-Reply-To: <49364AE0.90206@paladin.bulgarpress.com>
References: <200810092344.10388.nick@van-laarhoven.org>
	<200811051548.mA5Fmsot040177@lava.sentex.ca>
	<200811062203.mA6M3ij3048835@lava.sentex.ca>
	<200811071453.07665.nick@van-laarhoven.org>
	<49364AE0.90206@paladin.bulgarpress.com>
Message-ID: <a31046fc0812030109s1a19fc01r2f1fe14d6cf54a8@mail.gmail.com>

2008/12/3 Todorov <todorov@paladin.bulgarpress.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I was trying to test my PCMCIA but I got this message :
>
> link_elf: symbol ucom_attach_tty undefined
>
> FreeBSD 7.0-RELEASE-p5 PCMCIA Huawei E630
>

Just for clarification: did you include device ucom in your kernel config?

-- 
wbr,
pluknet
From nick at van-laarhoven.org  Wed Dec  3 02:52:25 2008
From: nick at van-laarhoven.org (Nick Hibma)
Date: Wed Dec  3 02:52:30 2008
Subject: Request for testers: Option 3G cards, also Sierra, 	Huawei and
	Novatel
In-Reply-To: <49364AE0.90206@paladin.bulgarpress.com>
References: <200810092344.10388.nick@van-laarhoven.org>
	<200811071453.07665.nick@van-laarhoven.org>
	<49364AE0.90206@paladin.bulgarpress.com>
Message-ID: <200812031140.07605.nick@van-laarhoven.org>

You need to upgrade to a more recent FBSD 7 version. Like for example 
7.1-RC1 or 7-STABLE.

Nick

> Hi,
>
> I was trying to test my PCMCIA but I got this message :
>
> link_elf: symbol ucom_attach_tty undefined
>
> FreeBSD 7.0-RELEASE-p5 PCMCIA Huawei E630
>
> Please comment,
> Thanks.
> _______________________________________________
> freebsd-hardware@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to
> "freebsd-hardware-unsubscribe@freebsd.org"


From nick at van-laarhoven.org  Wed Dec  3 03:02:04 2008
From: nick at van-laarhoven.org (Nick Hibma)
Date: Wed Dec  3 03:02:10 2008
Subject: Request for testers: Option 3G cards, also Sierra, 	Huawei and
	Novatel
In-Reply-To: <200812031140.07605.nick@van-laarhoven.org>
References: <200810092344.10388.nick@van-laarhoven.org>
	<49364AE0.90206@paladin.bulgarpress.com>
	<200812031140.07605.nick@van-laarhoven.org>
Message-ID: <200812031201.49063.nick@van-laarhoven.org>

Or just could try updating only sys/dev/usb/ucom.c and ucomvar.h, but I am 
not sure whether that works.

Nick

> You need to upgrade to a more recent FBSD 7 version. Like for example
> 7.1-RC1 or 7-STABLE.
>
> Nick
>
> > Hi,
> >
> > I was trying to test my PCMCIA but I got this message :
> >
> > link_elf: symbol ucom_attach_tty undefined
> >
> > FreeBSD 7.0-RELEASE-p5 PCMCIA Huawei E630
> >
> > Please comment,
> > Thanks.
> > _______________________________________________
> > freebsd-hardware@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> > To unsubscribe, send any mail to
> > "freebsd-hardware-unsubscribe@freebsd.org"
>
> _______________________________________________
> freebsd-hardware@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to
> "freebsd-hardware-unsubscribe@freebsd.org"


From kungfujesus06 at gmail.com  Wed Dec  3 22:02:29 2008
From: kungfujesus06 at gmail.com (Adam Stylinski)
Date: Wed Dec  3 22:02:36 2008
Subject: Rosewill RC-218 Card
Message-ID: <96af083b0812032132g16a00863i71ca387f30223e83@mail.gmail.com>

It would be spectacular if somebody wrote a driver for the Rosewill RC-218
card. It uses a marvell based chipset and I believe is compatible with the
sata_mv linux drivers. At the moment on a reboot I actually get a kernel
panic if the card is installed. I believe this has something to do with a
conflicting Highpoint Rocket Raid module that is being inserted (which I
think shares or has a similar chipset with this card). Whatever needles need
to be poked, you can poke me with them. I would like to use this card with
my nasbox, which is hosting FreeBSD 7.0 AMD64 on a CF card.
From fhard at ccstores.com  Wed Dec  3 22:22:17 2008
From: fhard at ccstores.com (fhard)
Date: Wed Dec  3 22:22:42 2008
Subject: swap zone exhausted, increase kern.maxswzone
Message-ID: <49377719.2020605@ccstores.com>

"swap zone exhausted, increase kern.maxswzone"

I encountered this today on FreeBSD 7.1B2
With an HP DL165G5  dual quad-core AMD 64
8Gb ram .. 20Gb swap space

Google doesn't bring up much more than similar inquiries
in mid 2007, where the inquiry was met with "increase the value".

I cannot find anywhere how to determine the existing value or how
to alter it.

When running "sysctl kern.maxswzone"
I am greeted with sysctl: unknown oid 'kern.maxswzone'

What am I doing wrong?

TIA
Jim Pazarena
From nick at van-laarhoven.org  Thu Dec  4 02:31:50 2008
From: nick at van-laarhoven.org (Nick Hibma)
Date: Thu Dec  4 02:32:03 2008
Subject: swap zone exhausted, increase kern.maxswzone
In-Reply-To: <49377719.2020605@ccstores.com>
References: <49377719.2020605@ccstores.com>
Message-ID: <200812041131.37944.nick@van-laarhoven.org>

100%|nick@hind:/sys-CURRENT % grep -r maxswzone .
./conf/NOTES:# 2.  In /boot/loader.conf, set the tunables kern.maxswzone,
./kern/.svn/text-base/subr_param.c.svn-base:int 
maxswzone;                      /* max swmeta KVA storage */
./kern/.svn/text-base/subr_param.c.svn-base:SYSCTL_INT(_kern, OID_AUTO, 
maxswzone, CTLFLAG_RDTUN, &maxswzone, 0,
./kern/.svn/text-base/subr_param.c.svn-base:    maxswzone = 
VM_SWZONE_SIZE_MAX;
./kern/.svn/text-base/subr_param.c.svn-base:    
TUNABLE_INT_FETCH("kern.maxswzone", &maxswzone);
./kern/subr_param.c:int maxswzone;                      /* max swmeta KVA 
storage */
./kern/subr_param.c:SYSCTL_INT(_kern, OID_AUTO, maxswzone, CTLFLAG_RDTUN, 
&maxswzone, 0,
./kern/subr_param.c:    maxswzone = VM_SWZONE_SIZE_MAX;
./kern/subr_param.c:    TUNABLE_INT_FETCH("kern.maxswzone", &maxswzone);
./boot/forth/.svn/text-base/loader.conf.svn-base:#kern.maxswzone=""             
# Set the max swmeta KVA storage
./boot/forth/loader.conf:#kern.maxswzone=""             # Set the max swmeta 
KVA storage
./boot/common/.svn/text-base/loader.8.svn-base:.It Va kern.maxswzone
./boot/common/loader.8:.It Va kern.maxswzone


So:

It is a kenv var not a sysctl. It's default is VM_SWZONE_SIZE_MAX I think 
and you can find more documentation in loader(8).

So type in

	man loader

and off you go!

Nick


> "swap zone exhausted, increase kern.maxswzone"
>
> I encountered this today on FreeBSD 7.1B2
> With an HP DL165G5  dual quad-core AMD 64
> 8Gb ram .. 20Gb swap space
>
> Google doesn't bring up much more than similar inquiries
> in mid 2007, where the inquiry was met with "increase the value".
>
> I cannot find anywhere how to determine the existing value or how
> to alter it.
>
> When running "sysctl kern.maxswzone"
> I am greeted with sysctl: unknown oid 'kern.maxswzone'
>
> What am I doing wrong?
>
> TIA
> Jim Pazarena
> _______________________________________________
> freebsd-hardware@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to
> "freebsd-hardware-unsubscribe@freebsd.org"


From ivoras at freebsd.org  Thu Dec  4 02:44:53 2008
From: ivoras at freebsd.org (Ivan Voras)
Date: Thu Dec  4 02:45:05 2008
Subject: swap zone exhausted, increase kern.maxswzone
In-Reply-To: <200812041131.37944.nick@van-laarhoven.org>
References: <49377719.2020605@ccstores.com>
	<200812041131.37944.nick@van-laarhoven.org>
Message-ID: <gh8cap$425$1@ger.gmane.org>

Nick Hibma wrote:
> 100%|nick@hind:/sys-CURRENT % grep -r maxswzone .
> ./conf/NOTES:# 2.  In /boot/loader.conf, set the tunables kern.maxswzone,
> ./kern/.svn/text-base/subr_param.c.svn-base:int 
> maxswzone;                      /* max swmeta KVA storage */
> ./kern/.svn/text-base/subr_param.c.svn-base:SYSCTL_INT(_kern, OID_AUTO, 
> maxswzone, CTLFLAG_RDTUN, &maxswzone, 0,
> ./kern/.svn/text-base/subr_param.c.svn-base:    maxswzone = 
> VM_SWZONE_SIZE_MAX;
> ./kern/.svn/text-base/subr_param.c.svn-base:    
> TUNABLE_INT_FETCH("kern.maxswzone", &maxswzone);
> ./kern/subr_param.c:int maxswzone;                      /* max swmeta KVA 
> storage */
> ./kern/subr_param.c:SYSCTL_INT(_kern, OID_AUTO, maxswzone, CTLFLAG_RDTUN, 
> &maxswzone, 0,
> ./kern/subr_param.c:    maxswzone = VM_SWZONE_SIZE_MAX;
> ./kern/subr_param.c:    TUNABLE_INT_FETCH("kern.maxswzone", &maxswzone);
> ./boot/forth/.svn/text-base/loader.conf.svn-base:#kern.maxswzone=""             
> # Set the max swmeta KVA storage
> ./boot/forth/loader.conf:#kern.maxswzone=""             # Set the max swmeta 
> KVA storage
> ./boot/common/.svn/text-base/loader.8.svn-base:.It Va kern.maxswzone
> ./boot/common/loader.8:.It Va kern.maxswzone
> 
> 
> So:
> 
> It is a kenv var not a sysctl. It's default is VM_SWZONE_SIZE_MAX 

Which is:
/sys> grep -rn VM_SWZONE_SIZE_MAX *
amd64/include/param.h:129:#ifndef VM_SWZONE_SIZE_MAX
amd64/include/param.h:130:#define	VM_SWZONE_SIZE_MAX	(32 * 1024 * 1024)

If I'm reading this correctly in the context of the OP, it costs more
than 32 MB to keep track of 20 GB of swap space :)

(I'm not suprised, just noticing)



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20081204/6375021c/signature.pgp
From fhard at ccstores.com  Thu Dec  4 07:46:49 2008
From: fhard at ccstores.com (Jim Pazarena)
Date: Thu Dec  4 07:46:56 2008
Subject: swap zone exhausted, increase kern.maxswzone
In-Reply-To: <200812041131.37944.nick@van-laarhoven.org>
References: <49377719.2020605@ccstores.com>
	<200812041131.37944.nick@van-laarhoven.org>
Message-ID: <4937FB67.8000100@ccstores.com>

Nick Hibma wrote:
>
> So:
>
> It is a kenv var not a sysctl. It's default is VM_SWZONE_SIZE_MAX I think
> and you can find more documentation in loader(8).
>
> So type in
>
> 	man loader
>
> and off you go!
>
> Nick

thank you!

All my googleing, manning & apropos-ing was fruitless.
but I after re-read "man sysctl" I don't see how I missed it!

Thanks again.   Jim
From jhb at freebsd.org  Thu Dec  4 13:24:57 2008
From: jhb at freebsd.org (John Baldwin)
Date: Thu Dec  4 13:25:05 2008
Subject: swap zone exhausted, increase kern.maxswzone
In-Reply-To: <4937FB67.8000100@ccstores.com>
References: <49377719.2020605@ccstores.com>
	<200812041131.37944.nick@van-laarhoven.org>
	<4937FB67.8000100@ccstores.com>
Message-ID: <200812041355.39285.jhb@freebsd.org>

On Thursday 04 December 2008 10:46:47 am Jim Pazarena wrote:
> Nick Hibma wrote:
> >
> > So:
> >
> > It is a kenv var not a sysctl. It's default is VM_SWZONE_SIZE_MAX I think
> > and you can find more documentation in loader(8).
> >
> > So type in
> >
> > 	man loader
> >
> > and off you go!
> >
> > Nick
> 
> thank you!
> 
> All my googleing, manning & apropos-ing was fruitless.
> but I after re-read "man sysctl" I don't see how I missed it!

What I typically do for this panic is get the 'swapinfo' from the crash dump, 
and use (number of blocks in use) * (total swap blocks) / (maxswzone) to 
compute a new value for kern.maxswzone.

-- 
John Baldwin
From todorov at paladin.bulgarpress.com  Fri Dec  5 01:12:32 2008
From: todorov at paladin.bulgarpress.com (Todorov)
Date: Fri Dec  5 01:12:38 2008
Subject: Request for testers: Option 3G cards, also Sierra, Huawei and
 Novatel
In-Reply-To: <200812031140.07605.nick@van-laarhoven.org>
References: <200810092344.10388.nick@van-laarhoven.org>	<200811071453.07665.nick@van-laarhoven.org>	<49364AE0.90206@paladin.bulgarpress.com>
	<200812031140.07605.nick@van-laarhoven.org>
Message-ID: <4938ECCD.1040700@paladin.bulgarpress.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nick Hibma ??????:
| You need to upgrade to a more recent FBSD 7 version. Like for example
| 7.1-RC1 or 7-STABLE.
|
| Nick
|
|> Hi,
|>
|> I was trying to test my PCMCIA but I got this message :
|>
|> link_elf: symbol ucom_attach_tty undefined
|>
|> FreeBSD 7.0-RELEASE-p5 PCMCIA Huawei E630
|>
|> Please comment,
|> Thanks.
|> _______________________________________________
|> freebsd-hardware@freebsd.org mailing list
|> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
|> To unsubscribe, send any mail to
|> "freebsd-hardware-unsubscribe@freebsd.org"
|
|
| _______________________________________________
| freebsd-hardware@freebsd.org mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
| To unsubscribe, send any mail to
"freebsd-hardware-unsubscribe@freebsd.org"


Thanks! I will..

Regards,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk47M0ACgkQibJkIG65HMcxOACfQM3Bk18kpUPDvSJzNWOVqIDl
KQ4AoLXQir1OfbGA7eWy2JHMGsLh6SsA
=wG3L
-----END PGP SIGNATURE-----
From lijimlee at gmail.com  Fri Dec  5 11:06:41 2008
From: lijimlee at gmail.com (Ji)
Date: Fri Dec  5 11:06:48 2008
Subject: interrupt problem when enabling serial console
Message-ID: <8fd8f02c0812051044u1e9cde4mbe47eb49c100c3c9@mail.gmail.com>

Hi all,

( I posted the following on freebsd-questions, and Mel suggested me to
post it here.)

I ran into a weird problem when enabling serial console on the
FreeBSD7.0. Your help is really appreciated.
I installed FreeBSD 7.0 amd64 (from the CD) on a Dell R200, and then
enabled the serial console by adding the following to
/boot/loader.conf

hint.sio.0.flags="0x30"
console="comconsole vidconsole"
comconsole_speed="9600"
boot_multicons="yes"

And also replaced the following line on /etc/ttys,

ttyd0  "/usr/libexec/getty std.9600"   dialup  off secure

with

ttyd0   "/usr/libexec/getty std.9600"  vt220  on   secure.

During rebooting, I found that the system hangs with the following
messages and actually all devices can NOT get interrupt resource (see
the attached message part 2 in the lower part of this email ).

"
...
Trying to mount root from ufs:/dev/ad4s1a

Manual root filesystem specification:
 <fstype>:<device>  Mount <device> using filesystem <fstype>
                      eg. ufs:da0s1a
 ?                  List valid disk boot devices
 <empty line>       Abort manual input
..."
(I tried type ?, there is nothing)

And it confused me that if I keep rebooting again and again without
doing any fixing, the problem comes and goes. When the problem is not
present, the serial console works fine.
Below, I attached booting message 1)  with disabling serial,  2) with
serial and problem showing up and 3) with serial and problem not
showing up.

Can anyone help me with that? Thanks a lot.

Jim

 (The kernel configuration file is the original GENERIC on FBSD7 amd64
installation CD)

> =============== 1) dmesg without enabling serial console ===================
> Copyright (c) 1992-2008 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>        The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008
>    root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(R) CPU           E3110  @ 3.00GHz (3000.23-MHz K8-class CPU)
>  Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
>  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=0x8e3fd<SSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,<b19>>
>  AMD Features=0x20100800<SYSCALL,NX,LM>
>  AMD Features2=0x1<LAHF>
>  Cores per package: 2
> usable memory = 2133360640 (2034 MB)
> avail memory  = 2058694656 (1963 MB)
> ACPI APIC Table: <DELL   PE_SC3  >
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
>  cpu0 (BSP): APIC ID:  0
>  cpu1 (AP): APIC ID:  1
> ioapic0: Changing APIC ID to 2
> ioapic0 <Version 2.0> irqs 0-23 on motherboard
> kbd1 at kbdmux0
> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
> hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18)
> acpi0: <DELL PE_SC3> 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 0x808-0x80b on acpi0
> acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
> Timecounter "HPET" frequency 14318180 Hz quality 900
> cpu0: <ACPI CPU> on acpi0
> est0: <Enhanced SpeedStep Frequency Control> on cpu0
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: cpu_vendor GenuineIntel, msr 613091f06000613
> device_attach: est0 attach returned 6
> p4tcc0: <CPU Frequency Thermal Control> on cpu0
> cpu1: <ACPI CPU> on acpi0
> est1: <Enhanced SpeedStep Frequency Control> on cpu1
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: cpu_vendor GenuineIntel, msr 613091f06000613
> device_attach: est1 attach returned 6
> p4tcc1: <CPU Frequency Thermal Control> on cpu1
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
> pci1: <ACPI PCI bus> on pcib1
> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
> 0xece0-0xecff mem 0xdfbc0000-0xdfbdffff,0xdfbe0000-0xdfbfffff irq 16
> at device 0.0 on pci1
> em0: Using MSI interrupt
> em0: Ethernet address: 00:15:17:37:11:06
> em0: [FILTER]
> pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
> pci2: <ACPI PCI bus> on pcib2
> em1: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
> 0xdce0-0xdcff mem 0xdfcc0000-0xdfcdffff,0xdfce0000-0xdfcfffff irq 16
> at device 0.0 on pci2
> em1: Using MSI interrupt
> em1: Ethernet address: 00:15:17:36:19:d4
> em1: [FILTER]
> pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
> pci3: <ACPI PCI bus> on pcib3
> bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x4201> mem 0xdfdf0000-0xdfdfffff irq 16 at device 0.0 on pci3
> miibus0: <MII bus> on bge0
> brgphy0: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus0
> brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> bge0: Ethernet address: 00:1e:c9:ff:58:48
> bge0: [ITHREAD]
> pcib4: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
> pci4: <ACPI PCI bus> on pcib4
> bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x4201> mem 0xdfef0000-0xdfefffff irq 17 at device 0.0 on pci4
> miibus1: <MII bus> on bge1
> brgphy1: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus1
> brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> bge1: Ethernet address: 00:1e:c9:ff:58:49
> bge1: [ITHREAD]
> uhci0: <UHCI (generic) USB controller> port 0xbc60-0xbc7f irq 21 at
> device 29.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 0xbc80-0xbc9f irq 20 at
> device 29.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
> uhci2: <UHCI (generic) USB controller> port 0xbca0-0xbcbf irq 21 at
> device 29.2 on pci0
> uhci2: [GIANT-LOCKED]
> uhci2: [ITHREAD]
> usb2: <UHCI (generic) USB controller> on uhci2
> usb2: USB revision 1.0
> uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
> uhub2: 2 ports with 2 removable, self powered
> ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdfaffc00-0xdfafffff
> irq 21 at device 29.7 on pci0
> ehci0: [GIANT-LOCKED]
> ehci0: [ITHREAD]
> usb3: EHCI version 1.0
> usb3: companion controllers, 2 ports each: usb0 usb1 usb2
> usb3: <EHCI (generic) USB 2.0 controller> on ehci0
> usb3: USB revision 2.0
> uhub3: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
> uhub3: 6 ports with 6 removable, self powered
> umass0: <Sony DRX-810UL, class 0/0, rev 2.00/1.00, addr 2> on uhub3
> uhub4: <vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 3> on uhub3
> uhub4: multiple transaction translators
> uhub4: 4 ports with 4 removable, self powered
> pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
> pci5: <ACPI PCI bus> on pcib5
> vgapci0: <VGA-compatible display> port 0xcc00-0xccff mem
> 0xd0000000-0xd7ffffff,0xdfff0000-0xdfffffff irq 19 at device 5.0 on
> pci5
> isab0: <PCI-ISA bridge> at device 31.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Intel ICH9 SATA300 controller> port
> 0xbc30-0xbc37,0xbc28-0xbc2b,0xbc38-0xbc3f,0xbc2c-0xbc2f,0xbc40-0xbc4f,0xbc50-0xbc5f
> irq 23 at device 31.2 on pci0
> atapci0: [ITHREAD]
> ata2: <ATA channel 0> on atapci0
> ata2: [ITHREAD]
> ata3: <ATA channel 1> on atapci0
> ata3: [ITHREAD]
> fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
> fdc0: does not respond
> device_attach: fdc0 attach returned 6
> sio0: configured irq 4 not in bitmap of probed irqs 0
> sio0: port may not be enabled
> sio0: configured irq 4 not in bitmap of probed irqs 0
> sio0: port may not be enabled
> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
> sio0: type 16550A
> sio0: [FILTER]
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> 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]
> fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
> fdc0: does not respond
> device_attach: fdc0 attach returned 6
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> orm0: <ISA Option ROMs> at iomem
> 0xc0000-0xc8fff,0xc9000-0xc9fff,0xca000-0xcb7ff,0xec000-0xeffff on
> isa0
> ppc0: cannot reserve I/O port range
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> Timecounters tick every 1.000 msec
> hptrr: no controller detected.
> ad4: 76293MB <WDC WD800AAJS-18TDA1 01.00A04> at ata2-master SATA300
> SMP: AP CPU #1 Launched!
> cd0 at umass-sim0 bus 0 target 0 lun 0
> cd0: <SONY DVD RW DRU-810A 2.0e> Removable CD-ROM SCSI-0 device
> cd0: 40.000MB/s transfers
> cd0: Attempt to query device size failed: NOT READY, Medium not present
> Trying to mount root from ufs:/dev/ad4s1a
>
> === 2) problematic booting After enabling serial (copied from serial console)=====
> 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.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008
>    root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(R) CPU           E3110  @ 3.00GHz (3000.22-MHz K8-class CPU)
>  Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
>  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=0x8e3fd<SSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,<b19>>
>  AMD Features=0x20100800<SYSCALL,NX,LM>
>  AMD Features2=0x1<LAHF>
>  Cores per package: 2
> usable memory = 2133360640 (2034 MB)
> avail memory  = 2058747904 (1963 MB)
> kbd1 at kbdmux0
> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
> hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18)
> cpu0 on motherboard
> est0: <Enhanced SpeedStep Frequency Control> on cpu0
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: cpu_vendor GenuineIntel, msr 613091f06000613
> device_attach: est0 attach returned 6
> p4tcc0: <CPU Frequency Thermal Control> on cpu0
> pcib0: <Host to PCI bridge> pcibus 0 on motherboard
> pci0: <PCI bus> on pcib0
> pcib1: <PCI-PCI bridge> irq 15 at device 1.0 on pci0
> pci1: <PCI bus> on pcib1
> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
> 0xece0-0xecff mem 0xdfbc0000-0xdfbdffff,0xdfbe0000-0xdfbfffff irq 15
> at device 0.0 on pci1
> em0: Unable to allocate bus resource: interrupt
> em0: Allocation of PCI resources failed
> device_attach: em0 attach returned 6
> pcib2: <PCI-PCI bridge> irq 15 at device 28.0 on pci0
> pci2: <PCI bus> on pcib2
> em1: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
> 0xdce0-0xdcff mem 0xdfcc0000-0xdfcdffff,0xdfce0000-0xdfcfffff irq 15
> at device 0.0 on pci2
> em1: Unable to allocate bus resource: interrupt
> em1: Allocation of PCI resources failed
> device_attach: em1 attach returned 6
> pcib3: <PCI-PCI bridge> irq 15 at device 28.4 on pci0
> pci3: <PCI bus> on pcib3
> bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x4201> mem 0xdfdf0000-0xdfdfffff irq 15 at device 0.0 on pci3
> bge0: couldn't map interrupt
> device_attach: bge0 attach returned 6
> pcib4: <PCI-PCI bridge> irq 14 at device 28.5 on pci0
> pci4: <PCI bus> on pcib4
> bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x4201> mem 0xdfef0000-0xdfefffff irq 14 at device 0.0 on pci4
> bge1: couldn't map interrupt
> device_attach: bge1 attach returned 6
> uhci0: <UHCI (generic) USB controller> port 0xbc60-0xbc7f irq 11 at
> device 29.0 on pci0
> uhci0: Could not allocate irq
> device_attach: uhci0 attach returned 6
> uhci1: <UHCI (generic) USB controller> port 0xbc80-0xbc9f irq 10 at
> device 29.1 on pci0
> uhci1: Could not allocate irq
> device_attach: uhci1 attach returned 6
> uhci2: <UHCI (generic) USB controller> port 0xbca0-0xbcbf irq 11 at
> device 29.2 on pci0
> uhci2: Could not allocate irq
> device_attach: uhci2 attach returned 6
> ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdfaffc00-0xdfafffff
> irq 11 at device 29.7 on pci0
> ehci0: Could not allocate irq
> device_attach: ehci0 attach returned 6
> pcib5: <PCI-PCI bridge> at device 30.0 on pci0
> pci5: <PCI bus> on pcib5
> vgapci0: <VGA-compatible display> port 0xcc00-0xccff mem
> 0xd0000000-0xd7ffffff,0xdfff0000-0xdfffffff irq 5 at device 5.0 on
> pci5
> isab0: <PCI-ISA bridge> at device 31.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Intel ICH9 SATA300 controller> port
> 0xbc30-0xbc37,0xbc28-0xbc2b,0xbc38-0xbc3f,0xbc2c-0xbc2f,0xbc40-0xbc4f,0xbc50-0xbc5f
> irq 6 at device 31.2 on pci0
> atapci0: unable to map interrupt
> device_attach: atapci0 attach returned 6
> orm0: <ISA Option ROMs> at iomem
> 0xc0000-0xc8fff,0xc9000-0xc9fff,0xca000-0xcb7ff,0xec000-0xeffff on
> isa0
> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> fdc0: cannot reserve interrupt line
> ppc0: cannot reserve I/O port range
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> 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 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0
> sio0: type 16550A, console
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> Timecounter "TSC" frequency 3000222630 Hz quality 800
> Timecounters tick every 1.000 msec
> hptrr: no controller detected.
> Trying to mount root from ufs:/dev/ad4s1a
>
> Manual root filesystem specification:
>  <fstype>:<device>  Mount <device> using filesystem <fstype>
>                       eg. ufs:da0s1a
>  ?                  List valid disk boot devices
>  <empty line>       Abort manual input
>
> mountroot> ?
>
> List of GEOM managed disk devices:
>
>
> Manual root filesystem specification:
>  <fstype>:<device>  Mount <device> using filesystem <fstype>
>                       eg. ufs:da0s1a
>  ?                  List valid disk boot devices
>  <empty line>       Abort manual input
>
> mountroot> ufs:/dev/ad4s1a
> Trying to mount root from ufs:/dev/ad4s1a
>
> Manual root filesystem specification:
>  <fstype>:<device>  Mount <device> using filesystem <fstype>
>                       eg. ufs:da0s1a
>  ?                  List valid disk boot devices
>  <empty line>       Abort manual input
>
> mountroot>
> panic: Root mount failed, startup aborted.
> cpuid = 0
> Uptime: 1s
> Cannot dump. No dump device defined.
> Automatic reboot in 15 seconds - press a key on the console to abort
> --> Press a key on the console to reboot,
> --> or switch off the system now.
> Rebooting...
>
> ==== 3) normal booting after enabling serial (copied from serial console)=========
> Copyright (c) 1992-2008 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>        The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008
>    root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(R) CPU           E3110  @ 3.00GHz (3000.22-MHz K8-class CPU)
>  Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
>  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=0x8e3fd<SSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,<b19>>
>  AMD Features=0x20100800<SYSCALL,NX,LM>
>  AMD Features2=0x1<LAHF>
>  Cores per package: 2
> usable memory = 2133360640 (2034 MB)
> avail memory  = 2058694656 (1963 MB)
> ACPI APIC Table: <DELL   PE_SC3  >
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
>  cpu0 (BSP): APIC ID:  0
>  cpu1 (AP): APIC ID:  1
> ioapic0: Changing APIC ID to 2
> ioapic0 <Version 2.0> irqs 0-23 on motherboard
> kbd1 at kbdmux0
> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
> hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18)
> acpi0: <DELL PE_SC3> 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 0x808-0x80b on acpi0
> acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
> Timecounter "HPET" frequency 14318180 Hz quality 900
> cpu0: <ACPI CPU> on acpi0
> est0: <Enhanced SpeedStep Frequency Control> on cpu0
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: cpu_vendor GenuineIntel, msr 613091f06000613
> device_attach: est0 attach returned 6
> p4tcc0: <CPU Frequency Thermal Control> on cpu0
> cpu1: <ACPI CPU> on acpi0
> est1: <Enhanced SpeedStep Frequency Control> on cpu1
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: cpu_vendor GenuineIntel, msr 613091f06000613
> device_attach: est1 attach returned 6
> p4tcc1: <CPU Frequency Thermal Control> on cpu1
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
> pci1: <ACPI PCI bus> on pcib1
> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
> 0xece0-0xecff mem 0xdfbc0000-0xdfbdffff,0xdfbe0000-0xdfbfffff irq 16
> at device 0.0 on pci1
> em0: Using MSI interrupt
> em0: Ethernet address: 00:15:17:37:11:06
> em0: [FILTER]
> pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
> pci2: <ACPI PCI bus> on pcib2
> em1: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port
> 0xdce0-0xdcff mem 0xdfcc0000-0xdfcdffff,0xdfce0000-0xdfcfffff irq 16
> at device 0.0 on pci2
> em1: Using MSI interrupt
> em1: Ethernet address: 00:15:17:36:19:d4
> em1: [FILTER]
> pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
> pci3: <ACPI PCI bus> on pcib3
> bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x4201> mem 0xdfdf0000-0xdfdfffff irq 16 at device 0.0 on pci3
> miibus0: <MII bus> on bge0
> brgphy0: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus0
> brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> bge0: Ethernet address: 00:1e:c9:ff:58:48
> bge0: [ITHREAD]
> pcib4: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
> pci4: <ACPI PCI bus> on pcib4
> bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
> 0x4201> mem 0xdfef0000-0xdfefffff irq 17 at device 0.0 on pci4
> miibus1: <MII bus> on bge1
> brgphy1: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus1
> brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> bge1: Ethernet address: 00:1e:c9:ff:58:49
> bge1: [ITHREAD]
> uhci0: <UHCI (generic) USB controller> port 0xbc60-0xbc7f irq 21 at
> device 29.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 0xbc80-0xbc9f irq 20 at
> device 29.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
> uhci2: <UHCI (generic) USB controller> port 0xbca0-0xbcbf irq 21 at
> device 29.2 on pci0
> uhci2: [GIANT-LOCKED]
> uhci2: [ITHREAD]
> usb2: <UHCI (generic) USB controller> on uhci2
> usb2: USB revision 1.0
> uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
> uhub2: 2 ports with 2 removable, self powered
> ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdfaffc00-0xdfafffff
> irq 21 at device 29.7 on pci0
> ehci0: [GIANT-LOCKED]
> ehci0: [ITHREAD]
> usb3: EHCI version 1.0
> usb3: companion controllers, 2 ports each: usb0 usb1 usb2
> usb3: <EHCI (generic) USB 2.0 controller> on ehci0
> usb3: USB revision 2.0
> uhub3: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
> uhub3: 6 ports with 6 removable, self powered
> umass0: <Sony DRX-810UL, class 0/0, rev 2.00/1.00, addr 2> on uhub3
> uhub4: <vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 3> on uhub3
> uhub4: multiple transaction translators
> uhub4: 4 ports with 4 removable, self powered
> pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
> pci5: <ACPI PCI bus> on pcib5
> vgapci0: <VGA-compatible display> port 0xcc00-0xccff mem
> 0xd0000000-0xd7ffffff,0xdfff0000-0xdfffffff irq 19 at device 5.0 on
> pci5
> isab0: <PCI-ISA bridge> at device 31.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Intel ICH9 SATA300 controller> port
> 0xbc30-0xbc37,0xbc28-0xbc2b,0xbc38-0xbc3f,0xbc2c-0xbc2f,0xbc40-0xbc4f,0xbc50-0xbc5f
> irq 23 at device 31.2 on pci0
> atapci0: [ITHREAD]
> ata2: <ATA channel 0> on atapci0
> ata2: [ITHREAD]
> ata3: <ATA channel 1> on atapci0
> ata3: [ITHREAD]
> fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
> fdc0: does not respond
> device_attach: fdc0 attach returned 6
> 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 0x30 on acpi0
> sio0: type 16550A, console
> sio0: [FILTER]
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> 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]
> fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
> fdc0: does not respond
> device_attach: fdc0 attach returned 6
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> orm0: <ISA Option ROMs> at iomem
> 0xc0000-0xc8fff,0xc9000-0xc9fff,0xca000-0xcb7ff,0xec000-0xeffff on
> isa0
> ppc0: cannot reserve I/O port range
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> sio1: configured irq 3 not in bitmap of probed irqs 0
> sio1: port may not be enabled
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> Timecounters tick every 1.000 msec
> hptrr: no controller detected.
> ad4: 76293MB <WDC WD800AAJS-18TDA1 01.00A04> at ata2-master SATA300
> SMP: AP CPU #1 Launched!
> cd0 at umass-sim0 bus 0 target 0 lun 0
> cd0: <SONY DVD RW DRU-810A 2.0e> Removable CD-ROM SCSI-0 device
> cd0: 40.000MB/s transfers
> cd0: Attempt to query device size failed: NOT READY, Medium not present
> Trying to mount root from ufs:/dev/ad4s1a
> Loading configuration files.
> kernel dumps on /dev/ad4s3b
> Entropy harvesting: interrupts ethernet point_to_point kickstart.
> swapon: adding /dev/ad4s3b as swap device
> Starting file system checks:
> /dev/ad4s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/ad4s1a: clean, 12820246 free (58710 frags, 1595192 blocks, 0.4%
> fragmentation)
> Setting hostuuid: 44454c4c-3400-1053-8059-b7c04f484831.
> Setting hostid: 0x0188e958.
> Mounting local file systems:.
> Setting hostname: .fastsoft.com.
> net.inet6.ip6.auto_linklocal: 1 -> 0
> bge0: link state changed to DOWN
> bge0: no link .....bge0: link state changed to UP
>  got link
> DHCPREQUEST on bge0 to 255.255.255.255 port 67
> DHCPACK from 172.16.0.22
> bound to 172.16.1.16 -- renewal in 345600 seconds.
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
>        inet6 ::1 prefixlen 128
>        inet 127.0.0.1 netmask 0xff000000 b
> bge0: flags=884g3<UP,BROADCAST,ReUNNING,SIMPLEX,M1ULTICAST> metric: 0 mtu 1500
>        op tions=9b<RXCSUM,lTXCSUM,VLAN_MTU,iVLAN_HWTAGGING,VnLAN_HWCSUM>
>        etkher 00:1e:c9:ff: 58:48
>        inet 172s.16.1.16 netmaskt 0xffff0000 broaadcast 172.16.255t.255
>        media: Etehernet autoselec t (1000baseTX <fcull-duplex>)
>        shtatus: active
> aAdditional routinng options:.
> Stgarting devd.
> ed to UP
> hw.acpi.cpu.cx_lowest: C1
> sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
> Additional IP options:.
> Mounting NFS file systems:.
> Creating and/or trimming log files:.
> Starting syslogd.
> Checking for core dump on /dev/ad4s3b...
> savecore: no dumps found
> ELF ldconfig path: /lib /usr/lib /usr/lib/compat
> 32-bit compatibility ldconfig path:
> Initial amd64 initialization:.
> Additional ABI support:.
> Clearing /tmp (X related).
> Starting local daemons:.
> Updating motd.
> Mounting late file systems:.
> Configuring syscons: blanktime.
> Starting sshd.
> Starting cron.
> Local package initialization:.
> Starting background file system checks in 60 seconds.
>
> Tue Dec  2 16:58:50 UTC 2008
>
> FreeBSD/amd64 (xxxxx) (ttyd0)
>
> login:
>
From lev at FreeBSD.org  Fri Dec  5 11:33:02 2008
From: lev at FreeBSD.org (Lev Serebryakov)
Date: Fri Dec  5 11:33:08 2008
Subject: em0: watchdog timeout -- resetting
Message-ID: <785999360.20081205221324@serebryakov.spb.ru>

Hello, .

System:
FreeBSD xxx.xxx.xx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Dec  5 20:37:31 MSK 2008     lev@xxx.xxx.xx:/usr/obj/usr/src/sys/BLOB  amd64

Hardware:
% dmesg | grep em0
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0xe880-0xe89f mem 0xfea40000-0xfea5ffff,0xfea7a000-0xfea7afff irq 20 at device 25.0 on pci0
em0: [FILTER]
em0: Ethernet address: 00:1e:8c:75:03:0d
% pciconf -lv | grep
em0@pci0:0:25:0:        class=0x020000 card=0x82681043 chip=0x10bd8086 rev=0x02 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82566DM-2 Gigabit Network Connection'
    class      = network
    subclass   = ethernet
% ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9014
        options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
        ether 00:1e:8c:75:03:0d
        inet 192.168.134.3 netmask 0xffffff00 broadcast 192.168.134.255
        media: Ethernet autoselect (1000baseTX <full-duplex>)
        status: active
%

Hardware is ASUS P5E-VM DO motherboard with integrated controller.

Network is connected to HP ProCurce 1400-8G gigabit switch.

I'm getting "em0: watchdog timeout -- resetting" (and all connections
are lost!) very often. If here are network load it could be every 5
minutes sometimes... For example:

==============================================================
Dec  5 22:01:39 blob kernel: em0: watchdog timeout -- resetting
Dec  5 22:01:39 blob kernel: em0: link state changed to DOWN
Dec  5 22:01:42 blob kernel: em0: link state changed to UP
Dec  5 22:01:56 blob kernel: em0: watchdog timeout -- resetting
Dec  5 22:01:56 blob kernel: em0: link state changed to DOWN
Dec  5 22:01:59 blob kernel: em0: link state changed to UP
Dec  5 22:02:01 blob kernel: em0: link state changed to DOWN
Dec  5 22:02:03 blob kernel: em0: link state changed to UP
Dec  5 22:06:07 blob kernel: em0: watchdog timeout -- resetting
Dec  5 22:06:07 blob kernel: em0: link state changed to DOWN
Dec  5 22:06:09 blob kernel: em0: link state changed to UP
Dec  5 22:07:18 blob kernel: em0: watchdog timeout -- resetting
Dec  5 22:07:18 blob kernel: em0: link state changed to DOWN
Dec  5 22:07:24 blob kernel: em0: link state changed to UP
==============================================================

 I could provide any additional information.

-- 
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>

From n0oct at sbcglobal.net  Sat Dec  6 13:38:50 2008
From: n0oct at sbcglobal.net (jim smith)
Date: Sat Dec  6 13:38:56 2008
Subject: Western Digital hard disks and ATA timeouts
Message-ID: <20081206152649.e991d54b.n0oct@sbcglobal.net>

On 7Nov, 2008, at 20:12 , Peter Wemm wrote:

> On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick =20
> <koitsu@freebsd.org> wrote:
> [..]
>> As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds, =20=

>> and
>> is not adjustable without editing the ATA code yourself and =20
>> increasing
>> the value. 

. . .and where in the code is this?  I've got some drives I'd like to
experiment with.  Thanks.

-- 
jim smith <n0oct@sbcglobal.net>
From dudu at dudu.ro  Wed Dec 10 07:26:21 2008
From: dudu at dudu.ro (Vlad GALU)
Date: Wed Dec 10 07:26:27 2008
Subject: bce(4) and rx errors
Message-ID: <ad79ad6b0812100659i33db659ewc022b0100f8b097f@mail.gmail.com>

  Hello. Sorry for crossposting, but I wasn't sure which mailing list
was the most appropriate for this email.
I have an application pulling about 220Kpps from a bce(4) card
(details below). At what seems to be random times, errors start
showing up on that interface (I'm watching it with netstat -w1 -I), so
about 10% of the initial 220Kpps is reported as errors. Bringing the
interface down and then back up clears the errors, but they do
reappear at a later time. Before they reappear, the systems manages to
pull the full 220Kpps as before.
  This is a temporary setup, we'll very soon use an Intel fiber card,
but I thought this issue was worth mentioning, as I don't think it's a
hardware problem (the switch also reports no errors).

  The system is running a fresh (yesterday's) RELENG_7. The card is
onboard, on a HP DL380 G5. Here's the pciconf output:

-- cut here --
pcib13@pci0:2:0:0:      class=0x060400 card=0x00000000 chip=0x01031166
rev=0xc3 hdr=0x01
    vendor     = 'ServerWorks (Was: Reliance Computer Corp)'
    device     = 'BCM5715 Broadcom dual gigabit, pci bridge'
    class      = bridge
    subclass   = PCI-PCI
bce0@pci0:3:0:0:        class=0x020000 card=0x7038103c chip=0x164c14e4
rev=0x12 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = '5708C Broadcom NetXtreme II Gigabit Ethernet Adapter'
    class      = network
    subclass   = ethernet
-- and here --

  Regards,
  Vlad

-- 
~/.signature: no such file or directory
From jb000003 at mr-happy.com  Wed Dec 10 08:20:18 2008
From: jb000003 at mr-happy.com (Jeff Blank)
Date: Wed Dec 10 08:20:36 2008
Subject: bce(4) and rx errors
In-Reply-To: <ad79ad6b0812100659i33db659ewc022b0100f8b097f@mail.gmail.com>
References: <ad79ad6b0812100659i33db659ewc022b0100f8b097f@mail.gmail.com>
Message-ID: <20081210160325.GA72838@mr-happy.com>

On Wed, Dec 10, 2008 at 04:59:26PM +0200, Vlad GALU wrote:
> I have an application pulling about 220Kpps from a bce(4) card
> (details below). At what seems to be random times, errors start
> showing up on that interface (I'm watching it with netstat -w1 -I), so
> about 10% of the initial 220Kpps is reported as errors.

I'm also seeing a pretty steady stream of errors on both bce
interfaces in a Dell PowerEdge 2950 III.  In my case, the source
is RELENG_7_1 from ~14:00 UTC yesterday (9 Dec).  Throughput does not
seem to be affected.  "sysctl -a | egrep -i 'bce.*err'" yields all
zeroes, for whatever that's worth.

hostb0@pci0:0:0:0:	class=0x060000 card=0x80868086 chip=0x25c08086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000X Chipset Memory Controller Hub'
    class      = bridge
    subclass   = HOST-PCI
pcib1@pci0:0:2:0:	class=0x060400 card=0x00000000 chip=0x25e28086 rev=0x12 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset PCIe x4 Port 2'
    class      = bridge
    subclass   = PCI-PCI
pcib7@pci0:0:3:0:	class=0x060400 card=0x00000000 chip=0x25e38086 rev=0x12 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset PCIe x4 Port 3'
    class      = bridge
    subclass   = PCI-PCI
pcib8@pci0:0:4:0:	class=0x060400 card=0x00000000 chip=0x25f88086 rev=0x12 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset PCIe x8 Port 4-5'
    class      = bridge
    subclass   = PCI-PCI
pcib12@pci0:0:5:0:	class=0x060400 card=0x00000000 chip=0x25e58086 rev=0x12 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset PCIe x4 Port 5'
    class      = bridge
    subclass   = PCI-PCI
pcib13@pci0:0:6:0:	class=0x060400 card=0x00000000 chip=0x25f98086 rev=0x12 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset PCIe x8 Port 6-7'
    class      = bridge
    subclass   = PCI-PCI
pcib16@pci0:0:7:0:	class=0x060400 card=0x00000000 chip=0x25e78086 rev=0x12 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset PCIe x4 Port 7'
    class      = bridge
    subclass   = PCI-PCI
hostb1@pci0:0:16:0:	class=0x060000 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset Error Reporting Registers'
    class      = bridge
    subclass   = HOST-PCI
hostb2@pci0:0:16:1:	class=0x060000 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset Error Reporting Registers'
    class      = bridge
    subclass   = HOST-PCI
hostb3@pci0:0:16:2:	class=0x060000 card=0x01b21028 chip=0x25f08086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset Error Reporting Registers'
    class      = bridge
    subclass   = HOST-PCI
hostb4@pci0:0:17:0:	class=0x060000 card=0x80868086 chip=0x25f18086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset Reserved Registers'
    class      = bridge
    subclass   = HOST-PCI
hostb5@pci0:0:19:0:	class=0x060000 card=0x80868086 chip=0x25f38086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset Reserved Registers'
    class      = bridge
    subclass   = HOST-PCI
hostb6@pci0:0:21:0:	class=0x060000 card=0x80868086 chip=0x25f58086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset FBD Registers'
    class      = bridge
    subclass   = HOST-PCI
hostb7@pci0:0:22:0:	class=0x060000 card=0x80868086 chip=0x25f68086 rev=0x12 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '5000 Series Chipset FBD Registers'
    class      = bridge
    subclass   = HOST-PCI
pcib17@pci0:0:28:0:	class=0x060400 card=0x01b21028 chip=0x26908086 rev=0x09 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 PCIe Root Port 1'
    class      = bridge
    subclass   = PCI-PCI
uhci0@pci0:0:29:0:	class=0x0c0300 card=0x01b21028 chip=0x26888086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 Chipset USB Universal Host Controller'
    class      = serial bus
    subclass   = USB
uhci1@pci0:0:29:1:	class=0x0c0300 card=0x01b21028 chip=0x26898086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 Chipset USB Universal Host Controller'
    class      = serial bus
    subclass   = USB
uhci2@pci0:0:29:2:	class=0x0c0300 card=0x01b21028 chip=0x268a8086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 Chipset USB Universal Host Controller'
    class      = serial bus
    subclass   = USB
uhci3@pci0:0:29:3:	class=0x0c0300 card=0x01b21028 chip=0x268b8086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 Chipset USB Universal Host Controller'
    class      = serial bus
    subclass   = USB
ehci0@pci0:0:29:7:	class=0x0c0320 card=0x01b21028 chip=0x268c8086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 Chipset USB2 Enhanced Host Controller'
    class      = serial bus
    subclass   = USB
pcib19@pci0:0:30:0:	class=0x060401 card=0x00000000 chip=0x244e8086 rev=0xd9 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '82801 Family (ICH2/3/4/4/5/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge'
    class      = bridge
    subclass   = PCI-PCI
isab0@pci0:0:31:0:	class=0x060100 card=0x00000000 chip=0x26708086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 LPC Interface Controller'
    class      = bridge
    subclass   = PCI-ISA
atapci0@pci0:0:31:1:	class=0x01018a card=0x01b21028 chip=0x269e8086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB/3100 Ultra ATA Storage Controller'
    class      = mass storage
    subclass   = ATA
pcib2@pci0:4:0:0:	class=0x060400 card=0x00000000 chip=0x35008086 rev=0x01 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB PCIe Upstream Port'
    class      = bridge
    subclass   = PCI-PCI
pcib6@pci0:4:0:3:	class=0x060400 card=0x00000000 chip=0x350c8086 rev=0x01 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB PCIe to PCI-X Bridge'
    class      = bridge
    subclass   = PCI-PCI
pcib3@pci0:5:0:0:	class=0x060400 card=0x00000000 chip=0x35108086 rev=0x01 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB PCIe Downstream Port E1'
    class      = bridge
    subclass   = PCI-PCI
pcib5@pci0:5:1:0:	class=0x060400 card=0x00000000 chip=0x35148086 rev=0x01 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '631xESB/632xESB PCIe Downstream Port E2'
    class      = bridge
    subclass   = PCI-PCI
pcib4@pci0:6:0:0:	class=0x060400 card=0x00000000 chip=0x01031166 rev=0xc3 hdr=0x01
    vendor     = 'ServerWorks (Was: Reliance Computer Corp)'
    device     = 'BCM5715 Broadcom dual gigabit, pci bridge'
    class      = bridge
    subclass   = PCI-PCI
bce0@pci0:7:0:0:	class=0x020000 card=0x01b21028 chip=0x164c14e4 rev=0x12 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = '5708C Broadcom NetXtreme II Gigabit Ethernet Adapter'
    class      = network
    subclass   = ethernet
mpt0@pci0:1:0:0:	class=0x010000 card=0x1f101028 chip=0x00581000 rev=0x08 hdr=0x00
    vendor     = 'LSI Logic (Was: Symbios Logic, NCR)'
    device     = 'SAS 3000 series, 8-port with 1068E -StorPort'
    class      = mass storage
    subclass   = SCSI
pcib9@pci0:10:0:0:	class=0x060400 card=0x00000000 chip=0x8018111d rev=0x0e hdr=0x01
    vendor     = 'Integrated Device Technology Inc.'
    class      = bridge
    subclass   = PCI-PCI
pcib10@pci0:11:2:0:	class=0x060400 card=0x00000000 chip=0x8018111d rev=0x0e hdr=0x01
    vendor     = 'Integrated Device Technology Inc.'
    class      = bridge
    subclass   = PCI-PCI
pcib11@pci0:11:4:0:	class=0x060400 card=0x00000000 chip=0x8018111d rev=0x0e hdr=0x01
    vendor     = 'Integrated Device Technology Inc.'
    class      = bridge
    subclass   = PCI-PCI
igb0@pci0:12:0:0:	class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00
    vendor     = 'Intel Corporation'
    class      = network
    subclass   = ethernet
igb1@pci0:12:0:1:	class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00
    vendor     = 'Intel Corporation'
    class      = network
    subclass   = ethernet
igb2@pci0:13:0:0:	class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00
    vendor     = 'Intel Corporation'
    class      = network
    subclass   = ethernet
igb3@pci0:13:0:1:	class=0x020000 card=0x145a8086 chip=0x10d68086 rev=0x02 hdr=0x00
    vendor     = 'Intel Corporation'
    class      = network
    subclass   = ethernet
pcib14@pci0:15:0:0:	class=0x060400 card=0x00000000 chip=0x03298086 rev=0x09 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '6700PXH PCI Express-to-PCI Express Bridge A'
    class      = bridge
    subclass   = PCI-PCI
pcib15@pci0:15:0:2:	class=0x060400 card=0x00000000 chip=0x032a8086 rev=0x09 hdr=0x01
    vendor     = 'Intel Corporation'
    device     = '6700PXH PCI Express-to-PCI Express Bridge B'
    class      = bridge
    subclass   = PCI-PCI
pcib18@pci0:2:0:0:	class=0x060400 card=0x00000000 chip=0x01031166 rev=0xc3 hdr=0x01
    vendor     = 'ServerWorks (Was: Reliance Computer Corp)'
    device     = 'BCM5715 Broadcom dual gigabit, pci bridge'
    class      = bridge
    subclass   = PCI-PCI
bce1@pci0:3:0:0:	class=0x020000 card=0x01b21028 chip=0x164c14e4 rev=0x12 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = '5708C Broadcom NetXtreme II Gigabit Ethernet Adapter'
    class      = network
    subclass   = ethernet
vgapci0@pci0:19:13:0:	class=0x030000 card=0x01b21028 chip=0x515e1002 rev=0x02 hdr=0x00
    vendor     = 'ATI Technologies Inc'
    device     = 'Radeon ES1000 Radeon ES1000'
    class      = display
    subclass   = VGA
From won.derick at yahoo.com  Wed Dec 10 21:05:39 2008
From: won.derick at yahoo.com (Won De Erick)
Date: Wed Dec 10 21:05:45 2008
Subject: Watchdog for Boser (HS-7001)
References: <547602.79284.qm@web45809.mail.sp1.yahoo.com>
	<4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu>
	<611173.7111.qm@web45805.mail.sp1.yahoo.com>
	<4933AFD4.3070501@gmx.de>
Message-ID: <832968.75350.qm@web45816.mail.sp1.yahoo.com>

Christoph Mallon wrote:

>
>
Won De Erick schrieb:
>>> ----- Original Message ----
>> 
>>> From: Rink Springer <rink@FreeBSD.org>
>>> 
>>> 
>> On Mon, Dec 01, 2008 at 09:38:51AM +0100, Christoph Mallon wrote:
>>>> Userland is not allowed to write to ports. That's the bus error you see. Also without a call to the exit syscall at the end, it will segfault.
>>> Note that you can write to ports from userland by opening /dev/io - if
>>> you have it opened, you can write to the ports.
>>> 
>> 
>> I've added the following at the end
>> 
>>   mov eax, 1 ; SYS_exit
>>   call doint
>> 
>>   doint:
>>      int 0x80
>>      ret
>> 
>> Besides, I can see the following at /dev
>> crw-------   1 root   wheel       0,  16 Nov 27 01:53 io
>> 
>> How should I make this open? do i need to %include this?
>
> You're probably better of writing this in C. Here is a wrapper for the out instruction:
>
> static inline outb(unsigned short port, unsigned char data)
> {
>  asm("outb %0, %1" : : "a" (data), "dN" (port));
> }
>
> As Rink mentioned, you have to open /dev/io. The process must have super-user privileges, see io(4).
>
>

OK thanks for all the tips. I have now a working watchdog. :)


      

From lev at serebryakov.spb.ru  Sun Dec 14 01:58:04 2008
From: lev at serebryakov.spb.ru (Lev Serebryakov)
Date: Sun Dec 14 01:58:16 2008
Subject: MiniPCI WiFi (802.11g/11n) adapter with HostAP support -- please,
	advice models!
Message-ID: <73133587.20081214124019@serebryakov.spb.ru>

Hello, Freebsd-net.

  I need MiniPCI WiFi adapter with HostAP support (so, AFAIU, it
should NOT be Intel adapters). WPA2 will be a plus.

  Could somebody advice exact models (not chipsets!) to look up in
price lists and catalogs?

  Is VIA VT6655GMA00 (VIA MAC/BBP(VT6655) and Airoha
Transceiver(AL2230)) supported?

  Are here any Atheros-based (5212?) MiniPCI cards on marked?

  Is Atheros 802.11n chipset (as found on TP-Link TL-WN861N 300N) supported?

-- 
// Black Lion AKA Lev Serebryakov <lev@serebryakov.spb.ru>

From espartano.mail at gmail.com  Sun Dec 14 19:11:54 2008
From: espartano.mail at gmail.com (Espartano)
Date: Sun Dec 14 19:12:01 2008
Subject: MiniPCI WiFi (802.11g/11n) adapter with HostAP support --
	please, advice models!
In-Reply-To: <73133587.20081214124019@serebryakov.spb.ru>
References: <73133587.20081214124019@serebryakov.spb.ru>
Message-ID: <d353bd50812141848v25d17d63g6e166c140089f73f@mail.gmail.com>

On Sun, Dec 14, 2008 at 3:40 AM, Lev Serebryakov <lev@serebryakov.spb.ru> wrote:
> Hello, Freebsd-net.
>
>  I need MiniPCI WiFi adapter with HostAP support (so, AFAIU, it
> should NOT be Intel adapters). WPA2 will be a plus.
>
>  Could somebody advice exact models (not chipsets!) to look up in
> price lists and catalogs?
>

You can buy a Wistron CM9 Atheros 802.11a/b/g miniPCI wireless card to
acomplish an AP, here is the url to see the Specifications:
http://www.pcengines.ch/cm9.htm

if you want to buy this MiniPci card you can do it in this page:
http://www.pcengines.ch/order1.php search for the cm9 key word.

already i am using this MiniPCI card over FreeBSD 7.0 to acomplish an
AP and the card work very fine. :)


>  Is VIA VT6655GMA00 (VIA MAC/BBP(VT6655) and Airoha
> Transceiver(AL2230)) supported?
>
>  Are here any Atheros-based (5212?) MiniPCI cards on marked?
>
>  Is Atheros 802.11n chipset (as found on TP-Link TL-WN861N 300N) supported?
>
> --
> // Black Lion AKA Lev Serebryakov <lev@serebryakov.spb.ru>
>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>



-- 
"Linux is for people who hate Windows, BSD is for people who love UNIX".
"Social Engineer -> Because there is no patch for human stupidity"
"The Unix Guru's View of Sex unzip ; strip ; touch ; grep ; finger ;
mount ; fsck ; more ; yes ; umount ; sleep."
"Documentation is like sex: when it is good, it is very, very good;
and when it is bad, it is better than nothing."
From lev at FreeBSD.org  Sun Dec 14 23:30:57 2008
From: lev at FreeBSD.org (Lev Serebryakov)
Date: Sun Dec 14 23:31:09 2008
Subject: ath: is here full list of supported chipsets and chipsets
	comparsion?
Message-ID: <1988001541.20081215103053@serebryakov.spb.ru>

Hello, All.

  `man ath' on FreeBSD 7.1-PRE speaks only about WPA2 in AR5212 and
not-supported AR5005VL. But in "current" cars here are many other
chipsets -- 5213A, 5414, etc... And Atheros site is not very helpful
now  -- there are not 5212, 5213A, 5414 chipsets in both areas "WLAN
for Home, Office and Metro Wi-Fi" and "WLAN for Mobile" (BTW, link to
http://customerproducts.atheros.com/ doesn't work anymore).

  Is here full list of supported chipsets, and, maybe, some table with
chipsets features (AES, WPA2, AP mode, etc)?

-- 
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>

From bseklecki at collaborativefusion.com  Mon Dec 15 08:38:29 2008
From: bseklecki at collaborativefusion.com (Brian A. Seklecki)
Date: Mon Dec 15 08:38:35 2008
Subject: PERC5 (LSI MegaSAS) Patrol Read crashes
In-Reply-To: <1214840198.18670.43.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com>
References: <20071114122210.42E8613C4BB@mx1.freebsd.org>
	<1195160114.4042.154.camel@new-host>
	<1214840198.18670.43.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com>
Message-ID: <1229357507.1722.11.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com>

On Mon, 2008-06-30 at 11:36 -0400, Brian A. Seklecki wrote:
> On Thu, 2007-11-15 at 15:55 -0500, Brian A Seklecki (Mobile) wrote:

FYI -- everyone may want to have a look at the MegaCLI 2.x port that
Sean McAfee posted in ports/128848:

http://www.freebsd.org/cgi/query-pr.cgi?pr=128846

Comments and feedback are welcome.  This is tested against the PERC6.


~BAS
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20081215/a322f471/attachment.pgp
From glothlorien at mail.ru  Mon Dec 15 10:35:23 2008
From: glothlorien at mail.ru (Gennady Kudryashoff)
Date: Mon Dec 15 10:35:33 2008
Subject: FreeBSD 7.1-RC1 rl0 watchdog timeout with custom kernel
Message-ID: <341627524.20081215211656@tochka.ru>

Hello, all!

> A copy already sent to freebsd-questions.

I have Asus X51RL laptop with FreeBSD 7.1-RC1 installed. There were no
troubles with GENERIC kernel (both 7.0 and 7.1-RC1), but when I've
compiled custom kernel, rl ethernet driver tells to the console a lot
of errors:

rl0: link state changed to UP
rl0: watchdog timeout
rl0: watchdog timeout

Any mistake?

>uname -a:

FreeBSD asusbook.local 7.1-RC1 FreeBSD 7.1-RC1 #0: Mon Dec 15 08:40:11 MSK 2008     root@asusbook.local:/usr/obj/usr/src/sys/GENERIC  i386

>pciconf -lv:

rl0@pci0:8:7:0:	class=0x020000 card=0x10451043 chip=0x813910ec rev=0x10 hdr=0x00
    vendor     = 'Realtek Semiconductor'
    device     = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
    class      = network
    subclass   = ethernet

>dmesg from custom kernel (ASUSBOOK):

Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-RC1 #2: Sun Dec 14 20:13:33 MSK 2008
    root@asusbook.local:/usr/obj/usr/src/sys/ASUSBOOK
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(R) CPU          550  @ 2.00GHz (1995.14-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x10661  Stepping = 1
  Features=0xafebfbff<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,TM,PBE>
  Features2=0xe31d<SSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20000000<LM>
  AMD Features2=0x1<LAHF>
real memory  = 2012905472 (1919 MB)
avail memory = 1964134400 (1873 MB)
kbd1 at kbdmux0
ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417)
acpi0: <A.M.I OEMXSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 77f00000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_ec0: <Embedded Controller: GPE 0x11> port 0x62,0x66 on acpi0
acpi_asus0: Unsupported Asus laptop: X51RL
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci_link3: BIOS IRQ 10 for 0.19.INTD is invalid
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0x7800-0x78ff mem 0x90000000-0x9fffffff,0xf88f0000-0xf88fffff irq 5 at device 5.0 on pci1
pcib2: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci2: <ACPI PCI bus> on pcib2
ath0: <Atheros 5424/2424> mem 0xf89f0000-0xf89fffff irq 11 at device 0.0 on pci2
ath0: [ITHREAD]
ath0: WARNING: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:15:af:9e:d1:34
ath0: mac 14.2 phy 7.0 radio 10.2
pcib3: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci6: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pci7: <ACPI PCI bus> on pcib5
atapci0: <ATI IXP600 SATA300 controller> port 0xe800-0xe807,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd80f mem 0xfebffc00-0xfebfffff irq 3 at device 18.0 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: [ITHREAD]
ohci0: <OHCI (generic) USB controller> mem 0xfebfe000-0xfebfefff irq 11 at device 19.0 on pci0
ohci0: [GIANT-LOCKED]
ohci0: [ITHREAD]
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xfebfd000-0xfebfdfff irq 5 at device 19.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ohci2: <OHCI (generic) USB controller> mem 0xfebfc000-0xfebfcfff irq 4 at device 19.2 on pci0
ohci2: [GIANT-LOCKED]
ohci2: [ITHREAD]
usb2: OHCI version 1.0, legacy support
usb2: <OHCI (generic) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
ohci3: <OHCI (generic) USB controller> mem 0xfebfb000-0xfebfbfff irq 5 at device 19.3 on pci0
ohci3: [GIANT-LOCKED]
ohci3: [ITHREAD]
usb3: OHCI version 1.0, legacy support
usb3: <OHCI (generic) USB controller> on ohci3
usb3: USB revision 1.0
uhub3: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
ohci4: <OHCI (generic) USB controller> mem 0xfebfa000-0xfebfafff irq 4 at device 19.4 on pci0
ohci4: [GIANT-LOCKED]
ohci4: [ITHREAD]
usb4: OHCI version 1.0, legacy support
usb4: <OHCI (generic) USB controller> on ohci4
usb4: USB revision 1.0
uhub4: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfebff800-0xfebff8ff irq 9 at device 19.5 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb5: EHCI version 1.0
usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4
usb5: <EHCI (generic) USB 2.0 controller> on ehci0
usb5: USB revision 2.0
uhub5: <ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb5
uhub5: 10 ports with 10 removable, self powered
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci1: <ATI IXP600 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
pcm0: <ATI SB600 High Definition Audio Controller> mem 0xfebf4000-0xfebf7fff irq 11 at device 20.2 on pci0
pcm0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib6: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci8: <ACPI PCI bus> on pcib6
cbb0: <RF5C476 PCI-CardBus Bridge> irq 5 at device 1.0 on pci8
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb0: [ITHREAD]
pci8: <base peripheral> at device 1.1 (no driver attached)
pci8: <base peripheral> at device 1.2 (no driver attached)
rl0: <RealTek 8139 10/100BaseTX> port 0xb800-0xb8ff mem 0xfeaff400-0xfeaff4ff irq 5 at device 7.0 on pci8
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> PHY 0 on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:1f:c6:f1:38:ff
rl0: [ITHREAD]
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_acad0: <AC Adapter> on acpi0
battery0: <ACPI Control Method Battery> 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]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Synaptics Touchpad, device ID 3
cpu0: <ACPI CPU> on acpi0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
acpi_asus0: Unsupported Asus laptop: X51RL
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xccfff pnpid ORM0000 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: parallel port not found.
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 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
Timecounter "TSC" frequency 1995141435 Hz quality 800
Timecounters tick every 10.000 msec
acd0: DVDR <SlimtypeDVD A DS8A1P/CA24> at ata0-slave UDMA33
ad4: 152627MB <Seagate ST9160827AS 3.AAA> at ata2-master SATA150
pcm0: <HDA Codec: Realtek ALC660>
pcm0: <HDA Driver Revision: 20080420_0052>
Trying to mount root from ufs:/dev/ad4s2a
rl0: link state changed to UP
rl0: watchdog timeout
rl0: watchdog timeout
rl0: watchdog timeout
rl0: watchdog timeout
rl0: watchdog timeout
rl0: watchdog timeout

> dmesg from GENERIC kernel:

Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-RC1 #0: Mon Dec 15 08:40:11 MSK 2008
    root@asusbook.local:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(R) CPU          550  @ 2.00GHz (1995.14-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x10661  Stepping = 1
  Features=0xafebfbff<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,TM,PBE>
  Features2=0xe31d<SSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM>
  AMD Features=0x20000000<LM>
  AMD Features2=0x1<LAHF>
real memory  = 2012905472 (1919 MB)
avail memory = 1959628800 (1868 MB)
ACPI APIC Table: <A.M.I  OEMAPIC >
ioapic0 <Version 2.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417)
acpi0: <A.M.I OEMXSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 77f00000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_ec0: <Embedded Controller: GPE 0x11> port 0x62,0x66 on acpi0
acpi_asus0: Unsupported Asus laptop: X51RL
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0x7800-0x78ff mem 0x90000000-0x9fffffff,0xf88f0000-0xf88fffff irq 17 at device 5.0 on pci1
pcib2: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci2: <ACPI PCI bus> on pcib2
ath0: <Atheros 5424/2424> mem 0xf89f0000-0xf89fffff irq 16 at device 0.0 on pci2
ath0: [ITHREAD]
ath0: WARNING: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:15:af:9e:d1:34
ath0: mac 14.2 phy 7.0 radio 10.2
pcib3: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci6: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pci7: <ACPI PCI bus> on pcib5
atapci0: <ATI IXP600 SATA300 controller> port 0xe800-0xe807,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd80f mem 0xfebffc00-0xfebfffff irq 22 at device 18.0 on pci0
atapci0: [ITHREAD]
atapci0: AHCI Version 01.10 controller with 4 ports detected
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
ata4: <ATA channel 2> on atapci0
ata4: [ITHREAD]
ata5: <ATA channel 3> on atapci0
ata5: [ITHREAD]
ohci0: <OHCI (generic) USB controller> mem 0xfebfe000-0xfebfefff irq 16 at device 19.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: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xfebfd000-0xfebfdfff irq 17 at device 19.1 on pci0
ohci1: [GIANT-LOCKED]
ohci1: [ITHREAD]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ohci2: <OHCI (generic) USB controller> mem 0xfebfc000-0xfebfcfff irq 18 at device 19.2 on pci0
ohci2: [GIANT-LOCKED]
ohci2: [ITHREAD]
usb2: OHCI version 1.0, legacy support
usb2: SMM does not respond, resetting
usb2: <OHCI (generic) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
uhub2: 2 ports with 2 removable, self powered
ohci3: <OHCI (generic) USB controller> mem 0xfebfb000-0xfebfbfff irq 17 at device 19.3 on pci0
ohci3: [GIANT-LOCKED]
ohci3: [ITHREAD]
usb3: OHCI version 1.0, legacy support
usb3: SMM does not respond, resetting
usb3: <OHCI (generic) USB controller> on ohci3
usb3: USB revision 1.0
uhub3: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub3: 2 ports with 2 removable, self powered
ohci4: <OHCI (generic) USB controller> mem 0xfebfa000-0xfebfafff irq 18 at device 19.4 on pci0
ohci4: [GIANT-LOCKED]
ohci4: [ITHREAD]
usb4: OHCI version 1.0, legacy support
usb4: SMM does not respond, resetting
usb4: <OHCI (generic) USB controller> on ohci4
usb4: USB revision 1.0
uhub4: <ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub4: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfebff800-0xfebff8ff irq 19 at device 19.5 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb5: EHCI version 1.0
usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4
usb5: <EHCI (generic) USB 2.0 controller> on ehci0
usb5: USB revision 2.0
uhub5: <ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb5
uhub5: 10 ports with 10 removable, self powered
pci0: <serial bus, SMBus> at device 20.0 (no driver attached)
atapci1: <ATI IXP600 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0
ata0: <ATA channel 0> on atapci1
ata0: [ITHREAD]
pcm0: <ATI SB600 High Definition Audio Controller> mem 0xfebf4000-0xfebf7fff irq 16 at device 20.2 on pci0
pcm0: [ITHREAD]
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
pcib6: <ACPI PCI-PCI bridge> at device 20.4 on pci0
pci8: <ACPI PCI bus> on pcib6
cbb0: <RF5C476 PCI-CardBus Bridge> irq 21 at device 1.0 on pci8
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb0: [ITHREAD]
pci8: <base peripheral> at device 1.1 (no driver attached)
pci8: <base peripheral> at device 1.2 (no driver attached)
rl0: <RealTek 8139 10/100BaseTX> port 0xb800-0xb8ff mem 0xfeaff400-0xfeaff4ff irq 20 at device 7.0 on pci8
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> PHY 0 on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:1f:c6:f1:38:ff
rl0: [ITHREAD]
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_acad0: <AC Adapter> on acpi0
battery0: <ACPI Control Method Battery> 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]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Synaptics Touchpad, device ID 3
cpu0: <ACPI CPU> on acpi0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
acpi_asus0: Unsupported Asus laptop: X51RL
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xccfff pnpid ORM0000 on isa0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
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 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ums0: <Logitech USB Optical Mouse, class 0/0, rev 2.00/43.01, addr 2> on uhub2
ums0: 3 buttons and Z dir.
Timecounter "TSC" frequency 1995140715 Hz quality 800
Timecounters tick every 10.000 msec
acd0: DVDR <SlimtypeDVD A DS8A1P/CA24> at ata0-slave UDMA33
ad4: 152627MB <Seagate ST9160827AS 3.AAA> at ata2-master SATA150
pcm0: <HDA Codec: Realtek ALC660>
pcm0: <HDA Driver Revision: 20080420_0052>
Trying to mount root from ufs:/dev/ad4s2a
rl0: link state changed to UP

custom kernel (ASUSBOOK) config:

# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.15.2.1 2008/11/25 02:59:29 kensmith Exp $

cpu		I486_CPU
cpu		I586_CPU
cpu		I686_CPU
ident		ASUSBOOK

# To statically compile in device wiring instead of /boot/device.hints
#hints		"GENERIC.hints"		# Default places to look for devices.

makeoptions	DEBUG=-g		# Build kernel with gdb(1) debug symbols

options 	SCHED_ULE		# ULE scheduler
options 	PREEMPTION		# Enable kernel thread preemption
options 	INET			# InterNETworking
#options 	INET6			# IPv6 communications protocols
options 	SCTP			# Stream Control Transmission Protocol
options 	FFS			# Berkeley Fast Filesystem
options 	SOFTUPDATES		# Enable FFS soft updates support
options 	UFS_ACL			# Support for access control lists
options 	UFS_DIRHASH		# Improve performance on big directories
options 	UFS_GJOURNAL		# Enable gjournal-based UFS journaling
options 	MD_ROOT			# MD is a potential root device
options 	NFSCLIENT		# Network Filesystem Client
options 	NFSSERVER		# Network Filesystem Server
options 	NFSLOCKD		# Network Lock Manager
options 	NFS_ROOT		# NFS usable as /, requires NFSCLIENT
options 	MSDOSFS			# MSDOS Filesystem
options 	CD9660			# ISO 9660 Filesystem
options 	PROCFS			# Process filesystem (requires PSEUDOFS)
options 	PSEUDOFS		# Pseudo-filesystem framework
options 	GEOM_PART_GPT		# GUID Partition Tables.
options 	GEOM_LABEL		# Provides labelization
options 	COMPAT_43TTY		# BSD 4.3 TTY compat [KEEP THIS!]
options 	COMPAT_FREEBSD4		# Compatible with FreeBSD4
options 	COMPAT_FREEBSD5		# Compatible with FreeBSD5
options 	COMPAT_FREEBSD6		# Compatible with FreeBSD6
options 	SCSI_DELAY=5000		# Delay (in ms) before probing SCSI
options 	KTRACE			# ktrace(1) support
options 	STACK			# stack(9) support
options 	SYSVSHM			# SYSV-style shared memory
options 	SYSVMSG			# SYSV-style message queues
options 	SYSVSEM			# SYSV-style semaphores
options 	_KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev
options 	ADAPTIVE_GIANT		# Giant mutex is adaptive.
options 	STOP_NMI		# Stop CPUS using NMI instead of IPI
options 	AUDIT			# Security event auditing
#options 	KDTRACE_HOOKS		# Kernel DTrace hooks

# To make an SMP kernel, the next two lines are needed
#options 	SMP			# Symmetric MultiProcessor Kernel
#device		apic			# I/O APIC

# CPU frequency control
device		cpufreq

# Bus support.
device		eisa
device		pci

# Floppy drives
#device		fdc

# ATA and ATAPI devices
device		ata
device		atadisk		# ATA disk drives
device		ataraid		# ATA RAID drives
device		atapicd		# ATAPI CDROM drives
device		atapifd		# ATAPI floppy drives
device		atapist		# ATAPI tape drives
options 	ATA_STATIC_ID	# Static device numbering

# SCSI Controllers
#device		ahb		# EISA AHA1742 family
#device		ahc		# AHA2940 and onboard AIC7xxx devices
#options 	AHC_REG_PRETTY_PRINT	# Print register bitfields in debug
					# output.  Adds ~128k to driver.
#device		ahd		# AHA39320/29320 and onboard AIC79xx devices
#options 	AHD_REG_PRETTY_PRINT	# Print register bitfields in debug
					# output.  Adds ~215k to driver.
#device		amd		# AMD 53C974 (Tekram DC-390(T))
#device		hptiop		# Highpoint RocketRaid 3xxx series
#device		isp		# Qlogic family
#device 	ispfw		# Firmware for QLogic HBAs- normally a module
#device		mpt		# LSI-Logic MPT-Fusion
#device		ncr		# NCR/Symbios Logic
#device		sym		# NCR/Symbios Logic (newer chipsets + those of `ncr')
#device		trm		# Tekram DC395U/UW/F DC315U adapters

#device		adv		# Advansys SCSI adapters
#device		adw		# Advansys wide SCSI adapters
#device		aha		# Adaptec 154x SCSI adapters
#device		aic		# Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
#device		bt		# Buslogic/Mylex MultiMaster SCSI adapters

#device		ncv		# NCR 53C500
#device		nsp		# Workbit Ninja SCSI-3
#device		stg		# TMC 18C30/18C50

# SCSI peripherals
device		scbus		# SCSI bus (required for SCSI)
device		ch		# SCSI media changers
device		da		# Direct Access (disks)
device		sa		# Sequential Access (tape etc)
device		cd		# CD
device		pass		# Passthrough device (direct SCSI access)
device		ses		# SCSI Environmental Services (and SAF-TE)

# RAID controllers interfaced to the SCSI subsystem
#device		amr		# AMI MegaRAID
#device		arcmsr		# Areca SATA II RAID
#device		asr		# DPT SmartRAID V, VI and Adaptec SCSI RAID
#device		ciss		# Compaq Smart RAID 5*
#device		dpt		# DPT Smartcache III, IV - See NOTES for options
#device		hptmv		# Highpoint RocketRAID 182x
#device		hptrr		# Highpoint RocketRAID 17xx, 22xx, 23xx, 25xx
#device		iir		# Intel Integrated RAID
#device		ips		# IBM (Adaptec) ServeRAID
#device		mly		# Mylex AcceleRAID/eXtremeRAID
#device		twa		# 3ware 9000 series PATA/SATA RAID

# RAID controllers
#device		aac		# Adaptec FSA RAID
#device		aacp		# SCSI passthrough for aac (requires CAM)
#device		ida		# Compaq Smart RAID
#device		mfi		# LSI MegaRAID SAS
#device		mlx		# Mylex DAC960 family
#device		pst		# Promise Supertrak SX6000
#device		twe		# 3ware ATA RAID

# atkbdc0 controls both the keyboard and the PS/2 mouse
device		atkbdc		# AT keyboard controller
device		atkbd		# AT keyboard
device		psm		# PS/2 mouse

device		kbdmux		# keyboard multiplexer

device		vga		# VGA video card driver

device		splash		# Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device		sc

device		agp		# support several AGP chipsets

# Power management support (see NOTES for more options)
#device		apm
# Add suspend/resume support for the i8254.
device		pmtimer

# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
device		cbb		# cardbus (yenta) bridge
device		pccard		# PC Card (16-bit) bus
device		cardbus		# CardBus (32-bit) bus

# Serial (COM) ports
device		sio		# 8250, 16[45]50 based serial ports
device		uart		# Generic UART driver

# Parallel port
device		ppc
device		ppbus		# Parallel port bus (required)
device		lpt		# Printer
device		plip		# TCP/IP over parallel
device		ppi		# Parallel port interface device
#device		vpo		# Requires scbus and da

# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device		puc

# PCI Ethernet NICs.
#device		de		# DEC/Intel DC21x4x (``Tulip'')
#device		em		# Intel PRO/1000 Gigabit Ethernet Family
#device		igb		# Intel PRO/1000 PCIE Server Gigabit Family
#device		ixgb		# Intel PRO/10GbE Ethernet Card
#device		le		# AMD Am7900 LANCE and Am79C9xx PCnet
#device		txp		# 3Com 3cR990 (``Typhoon'')
#device		vx		# 3Com 3c590, 3c595 (``Vortex'')

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device		miibus		# MII bus support
#device		age		# Attansic/Atheros L1 Gigabit Ethernet
#device		ale		# Atheros AR8121/AR8113/AR8114 Ethernet
#device		bce		# Broadcom BCM5706/BCM5708 Gigabit Ethernet
#device		bfe		# Broadcom BCM440x 10/100 Ethernet
#device		bge		# Broadcom BCM570xx Gigabit Ethernet
#device		dc		# DEC/Intel 21143 and various workalikes
#device		et		# Agere ET1310 10/100/Gigabit Ethernet
#device		fxp		# Intel EtherExpress PRO/100B (82557, 82558)
#device		jme		# JMicron JMC250 Gigabit/JMC260 Fast Ethernet
#device		lge		# Level 1 LXT1001 gigabit Ethernet
#device		msk		# Marvell/SysKonnect Yukon II Gigabit Ethernet
#device		nfe		# nVidia nForce MCP on-board Ethernet
#device		nge		# NatSemi DP83820 gigabit Ethernet
#device		nve		# nVidia nForce MCP on-board Ethernet Networking
#device		pcn		# AMD Am79C97x PCI 10/100 (precedence over 'le')
#device		re		# RealTek 8139C+/8169/8169S/8110S
device		rl		# RealTek 8129/8139
#device		sf		# Adaptec AIC-6915 (``Starfire'')
#device		sis		# Silicon Integrated Systems SiS 900/SiS 7016
#device		sk		# SysKonnect SK-984x & SK-982x gigabit Ethernet
#device		ste		# Sundance ST201 (D-Link DFE-550TX)
#device		stge		# Sundance/Tamarack TC9021 gigabit Ethernet
#device		ti		# Alteon Networks Tigon I/II gigabit Ethernet
#device		tl		# Texas Instruments ThunderLAN
#device		tx		# SMC EtherPower II (83c170 ``EPIC'')
#device		vge		# VIA VT612x gigabit Ethernet
#device		vr		# VIA Rhine, Rhine II
#device		wb		# Winbond W89C840F
#device		xl		# 3Com 3c90x (``Boomerang'', ``Cyclone'')

# ISA Ethernet NICs.  pccard NICs included.
#device		cs		# Crystal Semiconductor CS89x0 NIC
# 'device ed' requires 'device miibus'
#device		ed		# NE[12]000, SMC Ultra, 3c503, DS8390 cards
#device		ex		# Intel EtherExpress Pro/10 and Pro/10+
#device		ep		# Etherlink III based cards
#device		fe		# Fujitsu MB8696x based cards
#device		ie		# EtherExpress 8/16, 3C507, StarLAN 10 etc.
#device		sn		# SMC's 9000 series of Ethernet chips
#device		xe		# Xircom pccard Ethernet

# Wireless NIC cards
device		wlan		# 802.11 support
device		wlan_wep	# 802.11 WEP support
device		wlan_ccmp	# 802.11 CCMP support
device		wlan_tkip	# 802.11 TKIP support
device		wlan_amrr	# AMRR transmit rate control algorithm
device		wlan_scan_ap	# 802.11 AP mode scanning
device		wlan_scan_sta	# 802.11 STA mode scanning
#device		an		# Aironet 4500/4800 802.11 wireless NICs.
device		ath		# Atheros pci/cardbus NIC's
device		ath_hal		# Atheros HAL (Hardware Access Layer)
device		ath_rate_sample	# SampleRate tx rate control for ath
#device		awi		# BayStack 660 and others
#device		ral		# Ralink Technology RT2500 wireless NICs.
#device		wi		# WaveLAN/Intersil/Symbol 802.11 wireless NICs.
#device		wl		# Older non 802.11 Wavelan wireless NIC.

# Pseudo devices.
device		loop		# Network loopback
device		random		# Entropy device
device		ether		# Ethernet support
device		sl		# Kernel SLIP
device		ppp		# Kernel PPP
device		tun		# Packet tunnel.
device		pty		# Pseudo-ttys (telnet etc)
device		md		# Memory "disks"
device		gif		# IPv6 and IPv4 tunneling
device		faith		# IPv6-to-IPv4 relaying (translation)
device		firmware	# firmware assist module

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device		bpf		# Berkeley packet filter

# USB support
device		uhci		# UHCI PCI->USB interface
device		ohci		# OHCI PCI->USB interface
device		ehci		# EHCI PCI->USB interface (USB 2.0)
device		usb		# USB Bus (required)
#device		udbp		# USB Double Bulk Pipe devices
device		ugen		# Generic
device		uhid		# "Human Interface Devices"
device		ukbd		# Keyboard
device		ulpt		# Printer
device		umass		# Disks/Mass storage - Requires scbus and da
device		ums		# Mouse
#device		ural		# Ralink Technology RT2500USB wireless NICs
#device		rum		# Ralink Technology RT2501USB wireless NICs
#device		urio		# Diamond Rio 500 MP3 player
device		uscanner	# Scanners
# USB Serial devices
device		ucom		# Generic com ttys
device		uark		# Technologies ARK3116 based serial adapters
device		ubsa		# Belkin F5U103 and compatible serial adapters
device		ubser		# BWCT console serial adapters
device		uftdi		# For FTDI usb serial adapters
device		uipaq		# Some WinCE based devices
device		uplcom		# Prolific PL-2303 serial adapters
device		uslcom		# SI Labs CP2101/CP2102 serial adapters
device		uvisor		# Visor and Palm devices
device		uvscom		# USB serial support for DDI pocket's PHS
# USB Ethernet, requires miibus
#device		aue		# ADMtek USB Ethernet
#device		axe		# ASIX Electronics USB Ethernet
#device		cdce		# Generic USB over Ethernet
#device		cue		# CATC USB Ethernet
#device		kue		# Kawasaki LSI USB Ethernet
#device		rue		# RealTek RTL8150 USB Ethernet

# FireWire support
#device		firewire	# FireWire bus code
#device		sbp		# SCSI over FireWire (Requires scbus and da)
#device		fwe		# Ethernet over FireWire (non-standard!)
#device		fwip		# IP over FireWire (RFC 2734,3146)
#device		dcons		# Dumb console driver
#device		dcons_crom	# Configuration ROM for dcons

Thank you for help.

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

__________ NOD32 3692 (20081215) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com


From sam at freebsd.org  Mon Dec 15 10:44:37 2008
From: sam at freebsd.org (Sam Leffler)
Date: Mon Dec 15 10:44:44 2008
Subject: ath: is here full list of supported chipsets and
	chipsets	comparsion?
In-Reply-To: <1988001541.20081215103053@serebryakov.spb.ru>
References: <1988001541.20081215103053@serebryakov.spb.ru>
Message-ID: <49469ED0.5070308@freebsd.org>

Lev Serebryakov wrote:
> Hello, All.
>
>   `man ath' on FreeBSD 7.1-PRE speaks only about WPA2 in AR5212 and
> not-supported AR5005VL. But in "current" cars here are many other
> chipsets -- 5213A, 5414, etc... And Atheros site is not very helpful
> now  -- there are not 5212, 5213A, 5414 chipsets in both areas "WLAN
> for Home, Office and Metro Wi-Fi" and "WLAN for Mobile" (BTW, link to
> http://customerproducts.atheros.com/ doesn't work anymore).
>
>   Is here full list of supported chipsets, and, maybe, some table with
> chipsets features (AES, WPA2, AP mode, etc)?
>
>   
HEAD supports most PCI/cardbus parts.  The main exceptions are the 9280 
and 9285.  The ath9k driver for linux supports them and anyone can add 
support using that.  11n parts only support legacy operation though w/ 
~10 line change to the driver you can get 11n RX + legacy TX.

RELENG_7 has a much older hal and lacks support for many cards.  I 
recommend using HEAD if wireless support is important to you.  No ETA on 
an update by me--others are welcome to supply the changes.

All ath cards support all features you listed (except for the 5210 which 
you're unlikely to care about).

    Sam

From lev at serebryakov.spb.ru  Mon Dec 15 12:27:34 2008
From: lev at serebryakov.spb.ru (Lev Serebryakov)
Date: Mon Dec 15 12:27:41 2008
Subject: ath: is here full list of supported chipsets and chipsets
	comparsion?
In-Reply-To: <49469ED0.5070308@freebsd.org>
References: <1988001541.20081215103053@serebryakov.spb.ru>
	<49469ED0.5070308@freebsd.org>
Message-ID: <1125132021.20081215232730@serebryakov.spb.ru>

Hello, Sam.
You wrote 15 ??????? 2008 ?., 21:15:44:


> RELENG_7 has a much older hal and lacks support for many cards.  I
> recommend using HEAD if wireless support is important to you.  No ETA on
> an update by me--others are welcome to supply the changes.
  As far as I understand, HEAD uses new HAL, so update is not simple
one... Or is RELENG_7 HAL build from same (Ok, previous version)
sources, as used in HEAD and HAL itself could be ported? (I understand,
that ath DRIVER could not be backported, because all massive wlan
changes).

  And using HEAD in production... Hmm. Is it good idea?

  Are current MiniPCI versions (AR5006[suffix]) supported by RELENG_7
 HAL?

-- 
// Black Lion AKA Lev Serebryakov <lev@serebryakov.spb.ru>

From desars at gmail.com  Tue Dec 16 14:35:58 2008
From: desars at gmail.com (Emmanuel de Sars)
Date: Tue Dec 16 14:36:05 2008
Subject: i5400 chipset based mainboard
Message-ID: <49480642.1060306@gmail.com>

Hi fellas,

I am about to buy the Tyan i5400XT motherboard for the pair of 
harpertown processors I already own.
No  need to specify that I also plan to install FreeBSD 7.x on it. 
However, as I prefer doing things in the
right way, I was wondering if some of you were aware of compatibility 
issues ?

Regards,
E.S
From Jeremy at FutureCIS.com  Thu Dec 18 09:36:26 2008
From: Jeremy at FutureCIS.com (ThinkDifferently)
Date: Thu Dec 18 09:36:33 2008
Subject: Vetting motherboard Gigabyte GA-MA78G-DS3H for FreeBSD 7.0-RELEASE
Message-ID: <21077464.post@talk.nabble.com>


I'm currently looking for an ATX motherboard that supports the AM2+ socket,
Phenom Quad-Core processor, 4 DDR2 RAM slots (800 MHz is fine), 6 SATA ports
with RAID, and Gigabit LAN.  Onboard VGA would be nice.

It needs to work well with FreeBSD 7.0-RELEASE, using a 2-disk SATA RAID1.

I'm currently looking at the Gigabyte GA-MA78G-DS3H.

Has anyone successfully operated 7.0 on this board?
Any booting issues?  Did you need to modify the ISO to get it to boot (if so
how)?
Did RAID work?  Did it require a special driver to be loaded (if so how)?

Do any other motherboards fit the bill, given the specifications I give
above?

I recently got a black eye &-( with the MSI K9N2G Neo-FD, using the GeForce
8200 (MCP78) chipset.  FreeBSD 7.0-RELEASE and CentOS 5.2 wouldn't even boot
on it, no matter what the BIOS config was.  Also, Vista wouldn't even
recognize the SATA disks, even if the SATA ports were in IDE, RAID or AHCI
modes (it requires a driver, even if you aren't doing RAID).

Also, I do not need HTPC quality video and sound from this thing.  I know
the mobo I mentioned has HTPC written all over it, but it's the base
qualities (processor, chipset, SATA, etc.) that really count.

All I need is basic VGA, and some stereo sound wouldn't be too bad.  I don't
really care if accelerated video or theater-quality sound output was bad or
flaky.

I'm going to operate it as a server and plug it into a VGA KVM that has a
max resolution of 1024x768.
-- 
View this message in context: http://www.nabble.com/Vetting-motherboard-Gigabyte-GA-MA78G-DS3H-for-FreeBSD-7.0-RELEASE-tp21077464p21077464.html
Sent from the freebsd-hardware mailing list archive at Nabble.com.

From yohimba at mail.ru  Thu Dec 18 23:02:10 2008
From: yohimba at mail.ru (Vyacheslav I.)
Date: Thu Dec 18 23:02:29 2008
Subject: Problem with FreeBSD for AMD64 & Mylex AcceleRAID
Message-ID: <E1LDZDJ-000Gxg-00.yohimba-mail-ru@f217.mail.ru>

Hi!

I used to use the FreeBSD on i386 architecture together with the controller Mylex AcceleRAID 170.There was RAID 0+1 configured on it out of 5 discs (Enhanced Mirroring).

# pciconf -lvc
...
mly0@pci0:6:1:0:        class=0x010400 card=0x00521069 chip=0x00501069 rev=0x02 hdr=0x00
    vendor     = 'Mylex Corp'
    device     = 'AcceleRAID Disk Array'
    class      = mass storage
    subclass   = RAID
    cap 01[80] = powerspec 2  supports D0 D3  current D0

I used this configuration on i386 architecture with the following versions FreeBSD: 4.x, 5.x, 6.x and 7.0. It always worked perfectly. But recently I got needed  8 GB RAM so I had to install the version FreeBSD for AMD64. First I tried the 7.0, and after all - RELENG_7_1 dated 12.12.2008. Both these systems work with the files system located on RAID unstabl?! Meanwhile the same hardware on i386 architecture works with RELENG_7_1 perfectly.

Hardware: MB INTEL DG33FB, CPU Intel(R) Core(TM)2 Quad CPU @ 2.40 GHz, RAM 8 GB.

The base system is installed on a separate IDE disc.

# df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad4s1a    496M    111M    345M    24%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad4s1d    3.9G     22K    3.6G     0%    /tmp
/dev/ad4s1f    333G     52G    255G    17%    /usr
/dev/ad4s1e     15G     41M     14G     0%    /var
/dev/da0s1d   70.7G    410K   70.1G     0%    /mnt/da0/d

I carried out the following test by creating 3 big sized files of 1 GB each, and then deleting them:
# cd /mnt/da0/d
# dd if=/dev/zero of=test1 bs=1024k count=1024
# dd if=/dev/zero of=test2 bs=1024k count=1024
# dd if=/dev/zero of=test5 bs=1024k count=1024
# rm test*

After that I tried to unmount the files system, but I get a message of the kernel panic:
# cd /
# umount /mnt/da0/d

...
bad block 123456789, ino 176
dev = da0s1d, block = 4, fs = /mnt/da0/d
panic: ffs_blkfree: freeing free block
cpuid = 3
Uptime: 34 min...

The test was successful when using the i386 architecture with the same hardware

Taking a piece of advice of my friend, I used a dirty patch:
=== [code] ===
diff -Nru src.orig/sys/cam/scsi/scsi_da.c src/sys/cam/scsi/scsi_da.c
--- src.orig/sys/cam/scsi/scsi_da.c     2008-12-10 10:01:40.000000000 +0800
+++ src/sys/cam/scsi/scsi_da.c  2008-12-19 12:18:27.000000000 +0800
@@ -1187,7 +1187,7 @@
        if (match != NULL)
                softc->quirks = ((struct da_quirk_entry *)match)->quirks;
        else
-               softc->quirks = DA_Q_NONE;
+               softc->quirks = DA_Q_NO_SYNC_CACHE; // Dirty hack for AMD64

        /* Check if the SIM does not want 6 byte commands */
        xpt_setup_ccb(&cpi.ccb_h, periph->path, /*priority*/1);
=== [/code] ===

This patch solved the problem and the systems stopped being panicking. But I assume that this solution is wrong as the hardware works on i386 architecture without this patch well. 


From peterjeremy at optushome.com.au  Thu Dec 18 23:52:11 2008
From: peterjeremy at optushome.com.au (Peter Jeremy)
Date: Thu Dec 18 23:52:17 2008
Subject: ath: is here full list of supported chipsets and
	chipsets comparsion?
In-Reply-To: <1125132021.20081215232730@serebryakov.spb.ru>
References: <1988001541.20081215103053@serebryakov.spb.ru>
	<49469ED0.5070308@freebsd.org>
	<1125132021.20081215232730@serebryakov.spb.ru>
Message-ID: <20081219073842.GB21468@server.vk2pj.dyndns.org>

On 2008-Dec-15 23:27:30 +0300, Lev Serebryakov <lev@serebryakov.spb.ru> wrote:
>  And using HEAD in production... Hmm. Is it good idea?

That's really an individual decision.  If you have the time, expertise
and facilities to adequately regression test a HEAD snapshot using
something similar to your production workload, and are willing to help
resolve any problems you encounter, then there's no particular reason
why you shouldn't run HEAD in production.  Looking at it another way,
the more people who stress 8-CURRENT in strange and varied ways (and
help fix any problems they encounter), the better 8-RELEASE will be
when it eventuates.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20081219/b3ebcd79/attachment.pgp
From ivan at careytech.com.au  Sat Dec 20 04:15:14 2008
From: ivan at careytech.com.au (Ivan Carey)
Date: Sat Dec 20 04:15:20 2008
Subject: Gigabyte Motherboard Bios Setup
Message-ID: <494CDE3E.4010003@careytech.com.au>

Hello,
I have a Gigabyte GA-965P-DS3P motherboard.
I am having troubles installing and running FreeBSD.
What are the preferred BIOS settings for this motherboard

Thanks,
Ivan
From programadorlinux at gmail.com  Tue Dec 23 07:03:04 2008
From: programadorlinux at gmail.com (Israel Miranda)
Date: Tue Dec 23 07:03:10 2008
Subject: Apple Powerbook G4 and some modem doubts
Message-ID: <4d3a76db0812230640i6aba7c43s525e17af011a3b8b@mail.gmail.com>

Hi there guys. I just acquired and used powerbook g4 on ebay, and I've been
planning to install freebsd on my machines for quite sometime.
Does any of you use freebsd on a powerpc machine ?
I'll install it anyway, but I just wonder if there is good support for
freebsd in the ppc platform. I mean, enough programs, I know ppc
architecture is on tyer 2 support, so I am asking if someone has freebsd
installed on a powerpc machine as a primary
operating system and is satisfied with it. Actually I am more worried about
skype because I need it, and maybe some other apps I'll need in the way.
My doubt is to use either freebsd or macos X leopard in my powerbook as
primary OS. At first Macos X leopard seems to have a lot of apps for ppc but
I am a new Macos X user too. Please, no suggestions of installing linux, I
am a long time linux user and I no longer want to use it for my personal
machines.

My second question is about modem support.
My desktop computer is a Pentium 4 478 socket 2.6ghz HT, on a intel D865
PERL motherboard and an intel 537EP modem.
Please recommend me any pci modem that is fully supported, because my modem
has no freebsd driver at all.

Thanks for the help guys.

-- 


Filosofia de software livre:

Informa??o ? de gra?a
pessoas n?o s?o
contribuidores n?o tem pre?o.

Israel Vin?cius Nogueira Miranda
From ibmed at mail.ru  Tue Dec 30 19:33:32 2008
From: ibmed at mail.ru (ibmed)
Date: Tue Dec 30 19:33:38 2008
Subject: em driver problems? taskq em goes up to 100% CPU
Message-ID: <21222039.post@talk.nabble.com>


Sorry - didn't know where to post my question to: here or freebsd-net:

The problem is as follows:
I have two FreeBSD boxes that do ipfw nat.
I got two Intel cards (Intel <EXPI9404PT> PRO/1000 PT Quad Port (OEM) PCI-E
x4 10/100/1000Mbps) - one for each box, since the msk cards that boxes had
onboard had problems like "kernel: msk0: Rx FIFO overrun!". em cards solved
the FIFO problem, BUT: there's now a problem with spontaneous peaks of
system load: irrelatively to anything I can guess the system processes taskq
em0/em2 begin to eat 100% of CPU (and stay like that for about 1 or 2
minutes). And when that happens, traffic stops to pass through the box. The
problem is there on both boxes.

I tried upgrading both of them to RELENG_7_0, RELENG_7_1 (RC2 currently),
RELENG_7 - the problem remains.

Any suggestions on what can I do to solve the problem?
I have just no idea on what causes that and what to do to fix it. I would
really appreciate your help..

And just to be thorough, here's my kernel options:
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=400
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPFIREWALL_FORWARD
options IPFIREWALL_NAT
options LIBALIAS
options DUMMYNET
options IPDIVERT

fastforwarding is on, polling is off:
net.inet.ip.fastforwarding: 1

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING, VLAN_HWCSUM,TSO4>
ether 00:00:10:01:1:01
inet 10.1.1.1 netmask 0xffffff00 broadcast 10.1.1.255
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active 
-- 
View this message in context: http://www.nabble.com/em-driver-problems--taskq-em-goes-up-to-100--CPU-tp21222039p21222039.html
Sent from the freebsd-hardware mailing list archive at Nabble.com.