Re: AMD Geode LX crypto accelerator (glxsb)
Le Fri, 6 Jun 2008 23:41:35 +0200, Patrick Lamaizière <[EMAIL PROTECTED]> a écrit : Hello, > I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE > (via the NetBSD port). > " The glxsb driver supports the security block of the Geode LX > series processors. The Geode LX is a member of the AMD Geode family > of integrated x86 system chips. > > Driven by periodic checks for available data from the generator, > glxsb supplies entropy to the random(4) driver for common usage. > > glxsb also supports acceleration of AES-128-CBC operations for > crypto(4)." Well, I hope this is the final version. http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz I added a patch for FreeBSD 6 but i'am not able to test it. On 7-STABLE, I've tested with hundred openssl encryptions and some flood pings under ipsec in the background. Looks good for me. If someone can test and review it, it would be cool. Thanks, Regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nVidia nForce CK804 SATA300 controller
Le Fri, 20 Jun 2008 07:34:35 -0300, JoaoBR <[EMAIL PROTECTED]> a écrit : > my amd64 crashs under heavy disk i/o as each night at 0300 daily > cron, also often after some minutes when compiling world. Also with > kde and after some flash videos (youtube) or large file copying > > I do not see this problem with other sata controllers or same > hardware and a scsi adapter and this sata disabled what makes me > believe it is related to this specific sata controller > > this sata controller is part of some ASUS (M2N SLI Deluxe) or Epox > AM2 MBs > > there is no panic at all, some seconds of hard freeze, on desktop > machine the mouse still moves some seconds and reset, no log either, > no crash dump, nothing > > I have no irq conflict, latest bios onboard, I also exchanged other > hw parts with no success. > > Any idea? I've seen this kind of thing on the nvidia chipset, could you try without apic ? I'm not sure if you can disable the apic on amd64. It is just an idea! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AMD Geode LX crypto accelerator (glxsb)
Patrick Lamaizière wrote: Le Fri, 6 Jun 2008 23:41:35 +0200, Patrick Lamaizière <[EMAIL PROTECTED]> a écrit : Hello, I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE (via the NetBSD port). " The glxsb driver supports the security block of the Geode LX series processors. The Geode LX is a member of the AMD Geode family of integrated x86 system chips. Driven by periodic checks for available data from the generator, glxsb supplies entropy to the random(4) driver for common usage. glxsb also supports acceleration of AES-128-CBC operations for crypto(4)." Well, I hope this is the final version. http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz I added a patch for FreeBSD 6 but i'am not able to test it. On 7-STABLE, I've tested with hundred openssl encryptions and some flood pings under ipsec in the background. Looks good for me. If someone can test and review it, it would be cool. Hi, I'm having trouble testing it. My CPU is Geode LX: CPU: Geode(TM) Integrated Processor by AMD PCS (499.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2 Features=0x88a93d AMD Features=0xc040 When loading the driver, it attaches: Jun 22 18:49:41 ursaminor kernel: cryptosoft0: on motherboard Jun 22 18:49:41 ursaminor kernel: glxsb0: (AES-128-CBC,RNG)> mem 0xe021-0xe0213fff irq 11 at device 1.2 on pci0 I have the following klds loaded: 71 0xc3819000 4000 glxsb.ko 82 0xc389d000 23000crypto.ko 92 0xc38c a000 zlib.ko 101 0xc381e000 4000 cryptodev.ko Running openssl speed without cryptodev gives: > openssl speed aes-128-cbc To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 1005506 aes-128 cbc's in 0.98s Doing aes-128 cbc for 3s on 64 size blocks: 262185 aes-128 cbc's in 0.98s Doing aes-128 cbc for 3s on 256 size blocks: 66055 aes-128 cbc's in 0.97s Doing aes-128 cbc for 3s on 1024 size blocks: 16680 aes-128 cbc's in 0.98s Doing aes-128 cbc for 3s on 8192 size blocks: 2086 aes-128 cbc's in 0.98s OpenSSL 0.9.8e 23 Feb 2007 built on: Tue Apr 15 19:40:37 CEST 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=128 [sysconf value] timing function used: getrusage The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes aes-128 cbc 16465.91k17171.01k17422.55k17486.30k 17485.16k But running it with cryptodev gives: > openssl speed aes-128-cbc -engine cryptodev engine "cryptodev" set. To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 1007404 aes-128 cbc's in 0.97s Doing aes-128 cbc for 3s on 64 size blocks: 262177 aes-128 cbc's in 0.98s Doing aes-128 cbc for 3s on 256 size blocks: 66500 aes-128 cbc's in 0.98s Doing aes-128 cbc for 3s on 1024 size blocks: 16564 aes-128 cbc's in 0.97s Doing aes-128 cbc for 3s on 8192 size blocks: 2087 aes-128 cbc's in 0.98s OpenSSL 0.9.8e 23 Feb 2007 built on: Tue Apr 15 19:40:37 CEST 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=128 [sysconf value] timing function used: getrusage The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes aes-128 cbc 16545.20k17173.92k17417.71k17476.48k 17485.82k The results are practically the same. This is on 7-STABLE from April. signature.asc Description: OpenPGP digital signature
Re: AMD Geode LX crypto accelerator (glxsb)
Ivan Voras wrote: The results are practically the same. On the other hand: ursaminor:~/admin/glxsb> dd if=/dev/zero bs=4k count=10 | openssl enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij 10+0 records in 10+0 records out 40960 bytes transferred in 77.653939 secs (5274684 bytes/sec) ursaminor:~/admin/glxsb> dd if=/dev/zero bs=4k count=10 | openssl enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij -engine cryptodev engine "cryptodev" set. 10+0 records in 10+0 records out 40960 bytes transferred in 21.486846 secs (19062826 bytes/sec) So I guess it works. Any idea why "openssl speed" doesn't show it? signature.asc Description: OpenPGP digital signature
Re: AMD Geode LX crypto accelerator (glxsb)
Le Sun, 22 Jun 2008 19:40:04 +0200, Ivan Voras <[EMAIL PROTECTED]> a écrit : > Ivan Voras wrote: > > > The results are practically the same. > > On the other hand: > > ursaminor:~/admin/glxsb> dd if=/dev/zero bs=4k count=10 | openssl > enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij > 10+0 records in > 10+0 records out > 40960 bytes transferred in 77.653939 secs (5274684 bytes/sec) > > ursaminor:~/admin/glxsb> dd if=/dev/zero bs=4k count=10 | openssl > enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij -engine > cryptodev engine "cryptodev" set. > 10+0 records in > 10+0 records out > 40960 bytes transferred in 21.486846 secs (19062826 bytes/sec) > > So I guess it works. Any idea why "openssl speed" doesn't show it? On FreeBSD 7, OpenSSL does not use the cryptodev engine by default. This is a known problem. See http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-06/msg00076.html openssl speed -evp aes-128-cbc -elapsed -engine cryptodev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AMD Geode LX crypto accelerator (glxsb)
On Sun, Jun 22, 2008 at 6:05 PM, Patrick Lamaizière <[EMAIL PROTECTED]> wrote: > Le Fri, 6 Jun 2008 23:41:35 +0200, > Patrick Lamaizière <[EMAIL PROTECTED]> a écrit : > > Hello, > >> I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE >> (via the NetBSD port). >> " The glxsb driver supports the security block of the Geode LX >> series processors. The Geode LX is a member of the AMD Geode family >> of integrated x86 system chips. >> >> Driven by periodic checks for available data from the generator, >> glxsb supplies entropy to the random(4) driver for common usage. >> >> glxsb also supports acceleration of AES-128-CBC operations for >> crypto(4)." > > Well, I hope this is the final version. > > http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz > > I added a patch for FreeBSD 6 but i'am not able to test it. > > On 7-STABLE, I've tested with hundred openssl encryptions and some flood > pings under ipsec in the background. Looks good for me. > > If someone can test and review it, it would be cool. > > Thanks, Regards. It compiles on without a problem on 6.2 and loads on my Soekris Net5501-70 running pfSense (6.2-RELEASE-p11) glxsb0: mem 0xa000-0xa0003fff irq 10 at device 1.2 on pci0 Thanks!, Niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AMD Geode LX crypto accelerator (glxsb)
2008/6/22 Patrick Lamaizière <[EMAIL PROTECTED]>: > openssl speed -evp aes-128-cbc -elapsed -engine cryptodev I see the "-evp" parameter makes the difference in "openssl speed": > openssl speed -engine cryptodev -elapsed -evp aes-128-cbc aes-128-cbc engine "cryptodev" set. You have chosen to measure elapsed time instead of user CPU time. To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 1005992 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 64 size blocks: 262256 aes-128 cbc's in 3.01s Doing aes-128 cbc for 3s on 256 size blocks: 66470 aes-128 cbc's in 3.01s Doing aes-128 cbc for 3s on 1024 size blocks: 16575 aes-128 cbc's in 3.01s Doing aes-128 cbc for 3s on 8192 size blocks: 2087 aes-128 cbc's in 3.01s Doing aes-128-cbc for 3s on 16 size blocks: 74195 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 64 size blocks: 69208 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 256 size blocks: 64154 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 1024 size blocks: 44369 aes-128-cbc's in 3.01s Doing aes-128-cbc for 3s on 8192 size blocks: 9512 aes-128-cbc's in 3.01s OpenSSL 0.9.8e 23 Feb 2007 built on: Tue Apr 15 19:40:37 CEST 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=128 [sysconf value] timing function used: gettimeofday The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes aes-128 cbc 5359.57k 5577.49k 5654.53k 5639.81k 5679.65k aes-128-cbc394.62k 1471.97k 5457.89k15097.21k25895.72k ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NIC compatibility
Hello All, I have been trying to get FreeBSD 7.0 amd64 to run on my hardware: motherboard: ASUS P5N-EM-HDMI chipset: GeForce 7100 / nForce 630i processor: intel core2 quad Q6600 I have installed from the release ISO image, and everything seems to install fine. However, I can't seem to get the network card to be recognized. I have tried using both nfe and nve kernel modules, but neither one seems to identify with the onboard network card. dmesg reports: pci0: at device 15.0 (no driver attached) Is there another module that uses the drivers listed here?: http://www.nvidia.com/object/linux_nforce_1.25.html Or another way to get the network card working? I have also considered going the ndisgen route and trying to use the windows drivers that came w/ the motherboard, but I'm thinking that there's a better solution to this problem out there. Any Ideas? Thanks, Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NIC compatibility
On Sun, Jun 22, 2008 at 01:59:25PM -0700, Mike Derouen wrote: > I have been trying to get FreeBSD 7.0 amd64 to run on my hardware: > > motherboard: ASUS P5N-EM-HDMI > chipset: GeForce 7100 / nForce 630i > processor: intel core2 quad Q6600 > > I have installed from the release ISO image, and everything seems to install > fine. However, I can't seem to get the network card to be recognized. I > have tried using both nfe and nve kernel modules, but neither one seems to > identify with the onboard network card. dmesg reports: > > pci0: at device 15.0 (no driver attached) > > Is there another module that uses the drivers listed here?: > http://www.nvidia.com/object/linux_nforce_1.25.html Or another way to get > the network card working? I have also considered going the ndisgen route > and trying to use the windows drivers that came w/ the motherboard, but I'm > thinking that there's a better solution to this problem out there. > > Any Ideas? Provide the output from pciconf -lv. By the way, finding specification details for that motherboard appears to be difficult. Asus's own site has empty fields for each spec. detail, and all you can find on Google are vendors selling it. The closest thing I can find is the Windows driver page for the board: http://support.asus.com/download/download.aspx?SLanguage=en-us&model=P5N-EM%20HDMI The User Manual lists the NIC as "Gb LAN". Wow, thanks Asus. The BIOS listing in the Manual (which isn't 100% accurate, but it's the best we've got) shows a "Onboard nVidia LAN" item. I can't find any other details about the board. CC'ing PYUN YongHyeon, who should be able to help, since he assists in maintaining these drivers for FreeBSD. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NIC compatibility
Jeremy, Thanks for your reply. I wasn't able to find out much from the ASUS site either. Here is the pciconf output: [EMAIL PROTECTED]:0:0:0:class=0x06 card=0x chip=0x07c110de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:0:1:class=0x05 card=0x chip=0x07cb10de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:0:class=0x05 card=0x chip=0x07cd10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:1:class=0x05 card=0x chip=0x07ce10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:2:class=0x05 card=0x chip=0x07cf10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:3:class=0x05 card=0x chip=0x07d010de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:4:class=0x05 card=0x chip=0x07d110de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:5:class=0x05 card=0x chip=0x07d210de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:6:class=0x05 card=0x chip=0x07d310de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:2:0:class=0x05 card=0x chip=0x07d610de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:3:0:class=0x060100 card=0x82ae1043 chip=0x07d710de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = bridge subclass = PCI-ISA [EMAIL PROTECTED]:0:3:1:class=0x0c0500 card=0x82ae1043 chip=0x07d810de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = serial bus subclass = SMBus [EMAIL PROTECTED]:0:3:2:class=0x05 card=0x chip=0x07d910de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:3:4:class=0x05 card=0x chip=0x07c810de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = memory subclass = RAM [EMAIL PROTECTED]:0:4:0:class=0x0c0310 card=0x82ae1043 chip=0x07fe10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = serial bus subclass = USB [EMAIL PROTECTED]:0:4:1:class=0x0c0320 card=0x82ae1043 chip=0x056a10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = serial bus subclass = USB [EMAIL PROTECTED]:0:8:0:class=0x01018a card=0x82ae1043 chip=0x056c10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = mass storage subclass = ATA [EMAIL PROTECTED]:0:9:0:class=0x040300 card=0x829f1043 chip=0x07fc10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' class = multimedia [EMAIL PROTECTED]:0:10:0:class=0x060401 card=0xcb7310de chip=0x056d10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:11:0:class=0x060400 card=0x10de chip=0x056e10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:12:0:class=0x060400 card=0x10de chip=0x056f10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:13:0:class=0x060400 card=0x10de chip=0x056f10de rev=0xa1 hdr=0x01 vendor = 'Nvidia Corp' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:14:0:class=0x010185 card=0x82ae1043 chip=0x07f010de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = mass storage subclass = ATA [EMAIL PROTECTED]:0:15:0:class=0x02 card=0x82ae1043 chip=0x07dc10de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = network subclass = ethernet [EMAIL PROTECTED]:0:16:0:class=0x03 card=0x82ae1043 chip=0x07e110de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' class = display subclass = VGA [EMAIL PROTECTED]:1:6:0:class=0x010400 card=0x100113c1 chip=0x100113c1 rev=0x01 hdr=0x00 vendor = '3ware Inc.' device = '7000/8000 series ATA-133 Storage Controller' class = mass storage subclass = RAID Mike On Sun, Jun 22, 2008 at 2:37 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Sun, Jun 22, 2008 at 01:59:25PM -0700, Mike Derouen wrote: > > I have been trying to get FreeBSD 7.0 amd64 to run on my hardware: > > > > motherboard: ASUS P5N-EM-HDMI > > chipset: GeForce 7100 / nForce 630i > > processor: intel core2 quad Q6600 > > > > I have
Re: NIC compatibility
On Sun, Jun 22, 2008 at 04:28:32PM -0700, Mike Derouen wrote: > Jeremy, > > Thanks for your reply. I wasn't able to find out much from the ASUS site > either. Here is the pciconf output: > [...] > [EMAIL PROTECTED]:0:15:0:class=0x02 card=0x82ae1043 chip=0x07dc10de > rev=0xa2 hdr=0x00 > vendor = 'Nvidia Corp' > class = network > subclass = ethernet This looks like MCP73 ethernet controller. It's supported in 7-stable so you may have to update to latest 7-stable to use the ethernet controller. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NIC compatibility
On Mon, Jun 23, 2008 at 10:41:42AM +0900, Pyun YongHyeon wrote: > On Sun, Jun 22, 2008 at 04:28:32PM -0700, Mike Derouen wrote: > > Jeremy, > > > > Thanks for your reply. I wasn't able to find out much from the ASUS site > > either. Here is the pciconf output: > > > > [...] > > > [EMAIL PROTECTED]:0:15:0:class=0x02 card=0x82ae1043 chip=0x07dc10de > > rev=0xa2 hdr=0x00 > > vendor = 'Nvidia Corp' > > class = network > > subclass = ethernet > > This looks like MCP73 ethernet controller. It's supported in > 7-stable so you may have to update to latest 7-stable to use the > ethernet controller. Mike, you can download one of the RELENG_7 (7.0-STABLE) ISO snapshots from here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200806/ You probably want 7.0-STABLE-200806-i386-disc1.iso or amd64-disc1.iso depending upon if you want a 32-bit or 64-bit OS. (I'd recommend going with amd64, if at all possible.) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NIC compatibility
That did the trick! Thanks guys. Sorry for the n00b questions :). I was under the impression that I had the "latest" FreeBSD7 with the RELEASE build, but I was getting the RELEASE and STABLE meanings mixed up. Thanks! Mike On Sun, Jun 22, 2008 at 9:20 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Mon, Jun 23, 2008 at 10:41:42AM +0900, Pyun YongHyeon wrote: > > On Sun, Jun 22, 2008 at 04:28:32PM -0700, Mike Derouen wrote: > > > Jeremy, > > > > > > Thanks for your reply. I wasn't able to find out much from the ASUS > site > > > either. Here is the pciconf output: > > > > > > > [...] > > > > > [EMAIL PROTECTED]:0:15:0:class=0x02 card=0x82ae1043 > > chip=0x07dc10de > > > rev=0xa2 hdr=0x00 > > > vendor = 'Nvidia Corp' > > > class = network > > > subclass = ethernet > > > > This looks like MCP73 ethernet controller. It's supported in > > 7-stable so you may have to update to latest 7-stable to use the > > ethernet controller. > > Mike, you can download one of the RELENG_7 (7.0-STABLE) ISO snapshots > from here: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200806/ > > You probably want 7.0-STABLE-200806-i386-disc1.iso or amd64-disc1.iso > depending upon if you want a 32-bit or 64-bit OS. (I'd recommend going > with amd64, if at all possible.) > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Incorrect file size?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver Fromme wrote: > Ivan Voras wrote: > > Rink Springer wrote: > > > The 'vscan' user leads me assume this is SpamAssassin - I've seen this > > > behaviour at work, where our scripts were trying to backup a 1TB file > > > (which actually was ~vscan/.spamassassin/auto-whitelist). The result was > > > that the backup script died due to lack of disk space on the backup > > > server (as we don't use compression). > > > > > > When I was investigating why the file could be so large it, it turned > > > out the file was only a few hunderd 'real' MB's, so that is why I assume > > > this person is having the same issue as we do. The file is a Berkeley DB > > > file, by the way, so there's nothing textfile about it ;-) > > > > I learn something every day :) > > Didn't know BDB was smart enough to create sparse files. > > BTW, you can use "ls -ls" to display the number of physical > blocks allocated to the file, so you can easily see whether > a file is sparse or not: > > $ dd if=/dev/zero of=foo1 bs=1m count=1 > $ truncate -s 1m foo2 > $ ls -ls foo1 foo2 > 1040 -rw--- 1 olli olli 1048576 Jun 20 22:43 foo1 > 32 -rw--- 1 olli olli 1048576 Jun 20 22:43 foo2 # ls -lsk total 1247288 664064 -rw--- 1 vscan vscan 4398199488512 Jun 23 09:39 auto-whitelist 88 -rw--- 1 vscan vscan 89976 Jun 23 09:39 bayes_journal 566704 -rw--- 1 vscan vscan 1099639861248 Jun 23 09:39 bayes_seen 16432 -rw--- 1 vscan vscan 21454848 Jun 23 09:39 bayes_toks > > As you can see, the file size is the same, but the block > counts are different (I have BLOCKSIZE=K in my environment, > so the blocks are displayed in 1KB units). > > I've written a small script that can be used to detect > sparse files (it even displays the "sparseness" percentage): > > http://www.secnetix.de/olli/scripts/sparsecheck > > Best regards >Oliver > > PS: Of course it is still possible that a file system is > corrupt and needs fsck, no matter whether those files are > sparse or not. > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFIX0W+xJBWvpalMpkRAqrdAJ47eLQ+WMp6zBrme5gNyCSvzBtdUwCffYwT +37ul1gPqmk7rVKXRrha7fU= =uSGe -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Incorrect file size?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Ivan Voras wrote: > Rink Springer wrote: >> On Fri, Jun 20, 2008 at 03:54:22PM +0200, Ivan Voras wrote: >>> Except that the file in question should be, judging by the filename, a >>> simple text file. I don't really see how a whitelist could grow to such >>> monstrous sizes :) Most likely it's a file system corruption - fsck >>> should be the first thing to try. >> The 'vscan' user leads me assume this is SpamAssassin - I've seen this >> behaviour at work, where our scripts were trying to backup a 1TB file >> (which actually was ~vscan/.spamassassin/auto-whitelist). The result was >> that the backup script died due to lack of disk space on the backup >> server (as we don't use compression). Yes, it is SpamAssassin and I have the same problem with the backups. The Amanda complains with: xxx / lev 1 FAILED [dump larger than available tape space, 307256178 KB, skipping incremental] / lev 4 FAILED [dump larger than tape, 354005617 KB, skipping incremental] I don't think this is a file system corruption because there are no reasons for this. Also I have seen this on different machines. Any ideas how to fix this? >> >> When I was investigating why the file could be so large it, it turned >> out the file was only a few hunderd 'real' MB's, so that is why I assume >> this person is having the same issue as we do. The file is a Berkeley DB >> file, by the way, so there's nothing textfile about it ;-) > > I learn something every day :) > Didn't know BDB was smart enough to create sparse files. > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFIX0kwxJBWvpalMpkRAjkaAKCbF7sylsDyI2umCAoneqBqAYCNqwCgnQjA 9FkgJiVhqNI2NGCAlWpqfbg= =PQZ1 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
