Re: An L2TP client for OpenBSD?
On Saturday, March 2, 2013 03:15 CET, Matt matt.schwart...@gmail.com wrote: I love the L2TP functionality of npppd! In fact, the entire setup is elegant. It would also be great for OpenBSD to be able to function as an L2TP client. Is there any program out there or in development that implements the client side of L2TP? In -current ports tree there is net/xl2tpd, but nothing in base what I'm aware of. Sebastian Thanks much, Matt
Re: Summer Code
On Sat, Mar 02, 2013 at 12:41:28AM -0500, Shoufu Luo wrote: Is there any google summer code project in obsd community? -Shoufu Read the archives for a history of failed attempts to get Google to let OpenBSD sponsers in. Short answer: no. Long answer: maybe in the future. Ken
Re: An L2TP client for OpenBSD?
On 2013-03-02, Matt matt.schwart...@gmail.com wrote: I love the L2TP functionality of npppd! In fact, the entire setup is elegant. It would also be great for OpenBSD to be able to function as an L2TP client. Is there any program out there or in development that implements the client side of L2TP? Thanks much, Matt xl2tpd is in -current ports, and will *probably* work on 5.2 (though I have not tested it there and will not spend any time helping fix it if not). It works though I have only used it lightly. However you are out of luck if you want IPv6 in the tunnel as neither npppd nor our version of pppd (which xl2tpd uses for the actual transfer) support it.
Xorg + wsudl(4) DL-165 consumes a lot of cpu
Hi Everybody, On OpenBSD 5.3/amd64 (full dmesg(8) at the end), while watching Youtube videos through Minitube, Xorg(1) and Minitube consume a lot of CPU (see top(1) below), and the video is lagging. My below xorg.conf is a 3-screen configuration with 3 USB2DVI devices (DisplayLink CONV-USB2DVI, with a DL-165 chip) and the wsudl(4) driver. I have also tested with one DL-195 only and I had the same result. All is working fine with the embedded graphic chip of the computer : vga1 at pci0 dev 2 function 0 Intel HD Graphics 3000 rev 0x09 Is it a hardware or driver limitation, or misconfiguration ? Thanks a lot for your help. # top load averages: 3.34, 1.63, 0.71 test.temp.com 16:25:21 35 processes: 34 idle, 1 on processor CPU0 states: 14.0% user, 0.0% nice, 13.6% system, 37.7% interrupt, 34.7% idle CPU1 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU2 states: 0.0% user, 0.0% nice, 2.2% system, 0.0% interrupt, 97.8% idle CPU3 states: 0.4% user, 0.0% nice, 1.4% system, 0.0% interrupt, 98.2% idle CPU4 states: 0.8% user, 0.0% nice, 5.8% system, 0.0% interrupt, 93.3% idle CPU5 states: 3.6% user, 0.0% nice, 33.3% system, 0.0% interrupt, 63.1% idle CPU6 states: 7.8% user, 0.0% nice, 35.1% system, 0.0% interrupt, 57.1% idle CPU7 states: 14.5% user, 0.0% nice, 37.2% system, 0.0% interrupt, 48.3% idle Memory: Real: 109M/327M act/tot Free: 7547M Cache: 130M Swap: 0K/8197M PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 29293 alexis 20 101M 78M sleep/3 poll 3:22 129.83% minitube 12128 _x11 20 10M 31M sleep/3 select1:13 52.88% Xorg 17482 _sndio 2 -20 480K 944K sleep/0 poll 0:13 3.32% sndiod 11665 alexis 20 544K 1556K idle select0:01 0.00% dbus-launch 1 root 100 660K 420K idle wait 0:01 0.00% init 29037 _pflogd40 716K 376K sleep/5 bpf 0:01 0.00% pflogd 22491 root 280 1188K 2556K onproc/6 - 0:01 0.00% top 1717 root 180 760K 1756K idle pause 0:01 0.00% xdm 31119 root 20 3640K 3356K sleep/4 select0:01 0.00% sshd 8338 alexis 20 976K 2892K idle select0:01 0.00% fvwm 21735 _syslogd 20 668K 840K sleep/4 poll 0:00 0.00% syslogd 12279 root 20 1776K 1816K sleep/4 select0:00 0.00% sendmail 16253 root 20 2204K 1332K idle netio 0:00 0.00% Xorg 6310 alexis 20 776K 1380K idle poll 0:00 0.00% dbus-daemon 14644 root 100 1396K 5348K idle wait 0:00 0.00% xdm 18751 root 20 752K 1420K idle select0:00 0.00% sshd 31544 root 20 652K 520K idle netio 0:00 0.00% pflogd 6195 _ntp 20 800K 1148K idle poll 0:00 0.00% ntpd 14903 alexis 20 564K 1944K idle select0:00 0.00% FvwmPager 3900 root 20 744K 980K idle poll 0:00 0.00% ntpd 16024 alexis 30 1200K 2332K idle ttyin 0:00 0.00% bash 9219 root 20 652K 848K idle netio 0:00 0.00% syslogd 3583 root 20 736K 1016K sleep/5 select0:00 0.00% cron 10791 alexis 20 1888K 4468K idle select0:00 0.00% xterm 19389 root 20 504K 904K idle netio 0:00 0.00% xconsole 9006 _x11 20 632K 2804K idle poll 0:00 0.00% xconsole 7848 root 30 364K 972K idle ttyin 0:00 0.00% getty 7890 alexis180 584K 528K idle pause 0:00 0.00% sh 4067 root 100 1352K 2392K idle wait 0:00 0.00% bash 12627 _ntp 20 924K 1032K idle poll 0:00 0.00% ntpd 23233 root 30 456K 976K idle ttyin 0:00 0.00% getty 21623 root 30 508K 968K idle ttyin 0:00 0.00% getty 19287 root 30 324K 960K idle ttyin 0:00 0.00% getty 24107 root 30 488K 960K idle ttyin 0:00 0.00% getty 1580 root 20 460K 904K idle select0:00 0.00% inetd # cat /etc/X11/xorg.conf Section ServerLayout Identifier 3-screen Screen 0 1-Middle 0 0 Screen 1 0-Left LeftOf 1-Middle Screen 2 2-Right RightOf 1-Middle Option Xinerama On EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb FontPath unix/:7100 EndSection Section Module Load dbe Load extmod Load fbdevhw Load glx Load record Load freetype Load type1 #Load dri EndSection Section Monitor Identifier Monitor0 EndSection Section Monitor Identifier Monitor1 EndSection Section Monitor Identifier Monitor2 EndSection Section Screen Identifier 0-Left Device
Re: Xorg + wsudl(4) DL-165 consumes a lot of cpu
It is better to attach Xorg.0.log Shoufu On Mar 2, 2013, at 12:05 PM, Alexis de BRUYN wrote: hardware
Re: Xorg + wsudl(4) DL-165 consumes a lot of cpu
On 02.03.2013 18:24, Shoufu Luo wrote: It is better to attach Xorg.0.log # cat /var/log/Xorg.0.log [ 155.269] (--) checkDevMem: using aperture driver /dev/xf86 [ 155.286] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [ 155.399] X.Org X Server 1.12.3 Release Date: 2012-07-09 [ 155.399] X Protocol Version 11, Revision 0 [ 155.399] Build Operating System: OpenBSD 5.3 amd64 [ 155.399] Current Operating System: OpenBSD test.temp.com 5.3 GENERIC.MP#1 amd64 [ 155.399] Build Date: 27 February 2013 04:57:01PM [ 155.399] [ 155.399] Current version of pixman: 0.28.0 [ 155.399]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 155.399] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 155.399] (==) Log file: /var/log/Xorg.0.log, Time: Sat Mar 2 16:22:24 2013 [ 155.413] (==) Using config file: /etc/X11/xorg.conf [ 155.413] (==) Using system config directory /usr/X11R6/share/X11/xorg.conf.d [ 155.433] Parse error on line 10 of section Files in file /etc/X11/xorg.conf Ignoring obsolete keyword RgbPath. [ 155.433] (==) ServerLayout 3-screen [ 155.440] (**) |--Screen 1-Middle (0) [ 155.440] (**) | |--Monitor Monitor1 [ 155.447] (**) | |--Device 1-usb-dl165 [ 155.447] (**) |--Screen 0-Left (1) [ 155.447] (**) | |--Monitor Monitor0 [ 155.447] (**) | |--Device 0-usb-dl165 [ 155.447] (**) |--Screen 2-Right (2) [ 155.447] (**) | |--Monitor Monitor2 [ 155.448] (**) | |--Device 2-usb-dl165 [ 155.448] (**) Option Xinerama On [ 155.448] (==) Disabling SIGIO handlers for input devices [ 155.448] (==) Automatically adding devices [ 155.448] (==) Automatically enabling devices [ 155.450] (**) Xinerama: enabled [ 155.550] (**) FontPath set to: unix/:7100, /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [ 155.550] (==) ModulePath set to /usr/X11R6/lib/modules [ 155.550] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [ 155.555] (II) Loader magic: 0x1930565b53e0 [ 155.555] (II) Module ABI versions: [ 155.555]X.Org ANSI C Emulation: 0.4 [ 155.555]X.Org Video Driver: 12.0 [ 155.555]X.Org XInput driver : 16.0 [ 155.555]X.Org Server Extension : 6.0 [ 155.558] (--) PCI:*(0:0:2:0) 8086:0116:106b:00e7 rev 9, Mem @ 0xa000/4194304, 0x9000/268435456, I/O @ 0x2000/64 [ 155.558] (II) extmod will be loaded. This was enabled by default and also specified in the config file. [ 155.558] (II) dbe will be loaded. This was enabled by default and also specified in the config file. [ 155.558] (II) glx will be loaded. This was enabled by default and also specified in the config file. [ 155.558] (II) record will be loaded. This was enabled by default and also specified in the config file. [ 155.558] (II) dri will be loaded by default. [ 155.558] (II) dri2 will be loaded by default. [ 155.558] (II) LoadModule: dbe [ 155.596] (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.so [ 155.611] (II) Module dbe: vendor=X.Org Foundation [ 155.611]compiled for 1.12.3, module version = 1.0.0 [ 155.611]Module class: X.Org Server Extension [ 155.611]ABI class: X.Org Server Extension, version 6.0 [ 155.611] (II) Loading extension DOUBLE-BUFFER [ 155.611] (II) LoadModule: extmod [ 155.611] (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.so [ 155.623] (II) Module extmod: vendor=X.Org Foundation [ 155.623]compiled for 1.12.3, module version = 1.0.0 [ 155.623]Module class: X.Org Server Extension [ 155.623]ABI class: X.Org Server Extension, version 6.0 [ 155.623] (II) Loading extension MIT-SCREEN-SAVER [ 155.623] (II) Loading extension XFree86-VidModeExtension [ 155.623] (II) Loading extension XFree86-DGA [ 155.623] (II) Loading extension DPMS [ 155.623] (II) Loading extension XVideo [ 155.629] (II) Loading extension XVideo-MotionCompensation [ 155.629] (II) Loading extension X-Resource [ 155.629] (II) LoadModule: fbdevhw [ 155.639] (II) Loading /usr/X11R6/lib/modules/libfbdevhw.so [ 155.650] (EE) LoadModule: Module fbdevhw does not have a fbdevhwModuleData data object. [ 155.650] (II) UnloadModule: fbdevhw [ 155.650] (II) Unloading fbdevhw [ 155.650] (EE) Failed to load module fbdevhw (invalid module, 0) [ 155.650] (II) LoadModule: glx [ 155.651] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [ 155.656] (II) Module glx: vendor=X.Org Foundation [ 155.656]compiled for 1.12.3,
Re: Xorg + wsudl(4) DL-165 consumes a lot of cpu
On Sat, Mar 02, 2013 at 06:05:27PM +0100, Alexis de BRUYN wrote: Hi Everybody, On OpenBSD 5.3/amd64 (full dmesg(8) at the end), while watching Youtube videos through Minitube, Xorg(1) and Minitube consume a lot of CPU (see top(1) below), and the video is lagging. My below xorg.conf is a 3-screen configuration with 3 USB2DVI devices (DisplayLink CONV-USB2DVI, with a DL-165 chip) and the wsudl(4) driver. I have also tested with one DL-195 only and I had the same result. All is working fine with the embedded graphic chip of the computer : vga1 at pci0 dev 2 function 0 Intel HD Graphics 3000 rev 0x09 Is it a hardware or driver limitation, or misconfiguration ? Your resolution is 1600*1200*3 bytes (lets ignore whatever protocol the driver uses, probably not 3 byte words), so 1 full frame update, without the large USB overhead, means pushing out 5.5MB/s. At just 25fps that is 138MB/s or around 1.2Gbit/s. Now, USB2 has a theoretical bandwidth of 480Mbit/s, DVI has 4Gbit/s (dedicated, with no protocol that also supports mice and stuff). And DVI gets replaced by DP (8Gbit/s and more) because it can't keep up. Even if OpenBSD was super-awesome at graphics, video and usb (which it clearly is not), it could not overcome the hardware limitations. Unless the chip itself could do video decoding in hardware, but that is clearly not something supported by a framebuffer driver. So... no way is this ever going to work. Your graphics card does nothing here, afaict. It's all purely done on the CPU. Actually I find it kind of amazing that it works at all... Thanks a lot for your help. # top load averages: 3.34, 1.63, 0.71 test.temp.com 16:25:21 35 processes: 34 idle, 1 on processor CPU0 states: 14.0% user, 0.0% nice, 13.6% system, 37.7% interrupt, 34.7% idle CPU1 states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle CPU2 states: 0.0% user, 0.0% nice, 2.2% system, 0.0% interrupt, 97.8% idle CPU3 states: 0.4% user, 0.0% nice, 1.4% system, 0.0% interrupt, 98.2% idle CPU4 states: 0.8% user, 0.0% nice, 5.8% system, 0.0% interrupt, 93.3% idle CPU5 states: 3.6% user, 0.0% nice, 33.3% system, 0.0% interrupt, 63.1% idle CPU6 states: 7.8% user, 0.0% nice, 35.1% system, 0.0% interrupt, 57.1% idle CPU7 states: 14.5% user, 0.0% nice, 37.2% system, 0.0% interrupt, 48.3% idle Memory: Real: 109M/327M act/tot Free: 7547M Cache: 130M Swap: 0K/8197M PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 29293 alexis 20 101M 78M sleep/3 poll 3:22 129.83% minitube 12128 _x11 20 10M 31M sleep/3 select1:13 52.88% Xorg 17482 _sndio 2 -20 480K 944K sleep/0 poll 0:13 3.32% sndiod 11665 alexis 20 544K 1556K idle select0:01 0.00% dbus-launch 1 root 100 660K 420K idle wait 0:01 0.00% init 29037 _pflogd40 716K 376K sleep/5 bpf 0:01 0.00% pflogd 22491 root 280 1188K 2556K onproc/6 - 0:01 0.00% top 1717 root 180 760K 1756K idle pause 0:01 0.00% xdm 31119 root 20 3640K 3356K sleep/4 select0:01 0.00% sshd 8338 alexis 20 976K 2892K idle select0:01 0.00% fvwm 21735 _syslogd 20 668K 840K sleep/4 poll 0:00 0.00% syslogd 12279 root 20 1776K 1816K sleep/4 select0:00 0.00% sendmail 16253 root 20 2204K 1332K idle netio 0:00 0.00% Xorg 6310 alexis 20 776K 1380K idle poll 0:00 0.00% dbus-daemon 14644 root 100 1396K 5348K idle wait 0:00 0.00% xdm 18751 root 20 752K 1420K idle select0:00 0.00% sshd 31544 root 20 652K 520K idle netio 0:00 0.00% pflogd 6195 _ntp 20 800K 1148K idle poll 0:00 0.00% ntpd 14903 alexis 20 564K 1944K idle select0:00 0.00% FvwmPager 3900 root 20 744K 980K idle poll 0:00 0.00% ntpd 16024 alexis 30 1200K 2332K idle ttyin 0:00 0.00% bash 9219 root 20 652K 848K idle netio 0:00 0.00% syslogd 3583 root 20 736K 1016K sleep/5 select0:00 0.00% cron 10791 alexis 20 1888K 4468K idle select0:00 0.00% xterm 19389 root 20 504K 904K idle netio 0:00 0.00% xconsole 9006 _x11 20 632K 2804K idle poll 0:00 0.00% xconsole 7848 root 30 364K 972K idle ttyin 0:00 0.00% getty 7890 alexis180 584K 528K idle pause 0:00 0.00% sh 4067 root 100 1352K 2392K idle wait 0:00 0.00% bash 12627 _ntp 20 924K 1032K idle poll 0:00 0.00% ntpd 23233 root 30 456K 976K idle ttyin 0:00 0.00% getty 21623 root 30 508K
Re: Xorg + wsudl(4) DL-165 consumes a lot of cpu
On 02.03.2013 19:24, Tobias Ulmer wrote: Your resolution is 1600*1200*3 bytes (lets ignore whatever protocol the driver uses, probably not 3 byte words), so 1 full frame update, without the large USB overhead, means pushing out 5.5MB/s. At just 25fps that is 138MB/s or around 1.2Gbit/s. Now, USB2 has a theoretical bandwidth of 480Mbit/s, DVI has 4Gbit/s (dedicated, with no protocol that also supports mice and stuff). And DVI gets replaced by DP (8Gbit/s and more) because it can't keep up. Even if OpenBSD was super-awesome at graphics, video and usb (which it clearly is not), it could not overcome the hardware limitations. Unless the chip itself could do video decoding in hardware, but that is clearly not something supported by a framebuffer driver. So... no way is this ever going to work. Thanks for the technical clarification. Your graphics card does nothing here, afaict. It's all purely done on the CPU. Actually I find it kind of amazing that it works at all... Yes it is ! It is sufficient for me in many cases. -- Alexis de BRUYN
Disk layout: OpenBSD OT
Hi folks, just wonder in a typical hard drive nowadays (SATA/SAS), the sector 0 is in the inner or outter track ? Which tracks are faster: the inner ones or the outter ? Thanks in advance.
Re: Disk layout: OpenBSD OT
just wonder in a typical hard drive nowadays (SATA/SAS), the sector 0 is in the inner or outter track ? Which tracks are faster: the inner ones or the outter ? Only the manufacturer knows. Disks have been reporting fake geometries since more than 20 years. The electronic on the disk will do the necessary work to use the disk physical characteristic (with a varying number of sector per track) as cleverly as it can. Nowadays, you can't even be sure a given `software' is even contiguous on the disk. Just trust the disk and don't try to outsmart it, for it knows more about the actual hardware than you do. Miod
Re: Disk layout: OpenBSD OT
Am 02.03.2013 20:59, schrieb Miod Vallat: just wonder in a typical hard drive nowadays (SATA/SAS), the sector 0 is in the inner or outter track ? Which tracks are faster: the inner ones or the outter ? Only the manufacturer knows. Disks have been reporting fake geometries since more than 20 years. The electronic on the disk will do the necessary work to use the disk physical characteristic (with a varying number of sector per track) as cleverly as it can. Nowadays, you can't even be sure a given `software' is even contiguous on the disk. So, how is defrag (or avoiding fragmentation) done, if you can't be certain how the blocks are aligned? AFAIK, the last blocks are on the outside of the platters so, given a CAV, the speed is higher. The different speeds are measurablebut I don't know if noticeable (but I dont think so!) How SSDs handle block alignment is anoter story (wear-leveling et.al.) Regards, Matthias
USB repeater cable on Soekris net5501
Hi, I have a problem with a Digitus USB 2.0 repeater cable in combination with a Soekris net5501 running OpenBSD 5.2 (see full dmesg at the very end of this mail). The aim is to improve the position of a UTMS stick (Option GlobeTrotter HSDPA ICON225 USB) via the repeater cable. The UMTS stick works when directly attached to the Soekris net5501: umsm0 at uhub1 port 1 configuration 1 interface 0 Option N.V. Globetrotter HSDPA Modem rev 1.10/0.00 addr 2 umsm0 detached umsm0 at uhub1 port 1 configuration 1 interface 0 Option N.V. Globetrotter HSDPA Modem rev 1.10/0.00 addr 2 ucom0 at umsm0 umsm1 at uhub1 port 1 configuration 1 interface 1 Option N.V. Globetrotter HSDPA Modem rev 1.10/0.00 addr 2 ucom1 at umsm1 umsm2 at uhub1 port 1 configuration 1 interface 2 Option N.V. Globetrotter HSDPA Modem rev 1.10/0.00 addr 2 ucom2 at umsm2 usbdevs -v: Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), AMD(0x1022), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x1022), rev 1.00 port 1 addr 2: full speed, power 500 mA, config 1, Globetrotter HSDPA Modem(0x6971), Option N.V.(0x0af0), rev 0.00, iSerialNumber Serial Number port 2 powered port 3 powered port 4 powered Attaching the repeater cable alone works as well: uhub2 at uhub0 port 1 Terminus Technology product 0x0101 rev 2.00/1.11 addr 2 usbdevs -v: Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), AMD(0x1022), rev 1.00 port 1 addr 2: high speed, self powered, config 1, USB 2.0 Hub(0x0101), Terminus Technology(0x1a40), rev 1.11 port 1 powered port 2 powered port 3 powered port 4 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x1022), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered However, the problem occurs when I attach the repeater cable with the UMTS stick at its end. The stick is not recognized anymore. uhub2 at uhub0 port 1 Terminus Technology product 0x0101 rev 2.00/1.11 addr 2 If I boot with the repeater cable and UMTS stick already attached: uhub2 at uhub0 port 1 Terminus Technology product 0x0101 rev 2.00/1.11 addr 2 uhub2: device problem, disabling port 1 Do you have any ideas how to address this? (Yes, I have tested the repeater cable on a different machine (running Linux) and it works there with the same combination of cable and UMTS stick). Thanks! Best regards, Ingo dmesg: OpenBSD 5.2 (GENERIC) #278: Wed Aug 1 10:04:16 MDT 2012 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by AMD PCS (AuthenticAMD 586-class) 434 MHz cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW real mem = 267972608 (255MB) avail mem = 252731392 (241MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 20/80/26, BIOS32 rev. 0 @ 0xfac40 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0xa800 cpu0 at mainbus0: (uniprocessor) amdmsr0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) io address conflict 0x6100/0x100 io address conflict 0x6200/0x200 pchb0 at pci0 dev 1 function 0 AMD Geode LX rev 0x30 glxsb0 at pci0 dev 1 function 2 AMD Geode LX Crypto rev 0x00: RNG AES vr0 at pci0 dev 6 function 0 VIA VT6105M RhineIII rev 0x96: irq 11, address 00:00:24:c9:31:80 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr1 at pci0 dev 7 function 0 VIA VT6105M RhineIII rev 0x96: irq 5, address 00:00:24:c9:31:81 ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr2 at pci0 dev 8 function 0 VIA VT6105M RhineIII rev 0x96: irq 9, address 00:00:24:c9:31:82 ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 vr3 at pci0 dev 9 function 0 VIA VT6105M RhineIII rev 0x96: irq 12, address 00:00:24:c9:31:83 ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 glxpcib0 at pci0 dev 20 function 0 AMD CS5536 ISA rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c gpio0 at glxpcib0: 32 pins iic0 at glxpcib0 pciide0 at pci0 dev 20 function 2 AMD CS5536 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SanDisk SDCFB-512 wd0: 4-sector PIO, LBA, 488MB, 1000944 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 pciide0: channel 1 ignored (disabled) ohci0 at pci0 dev 21 function 0 AMD CS5536 USB rev 0x02: irq 15, version 1.0, legacy support ehci0 at pci0 dev 21 function 1 AMD CS5536 USB rev 0x02: irq 15 usb0 at ehci0: USB revision
Re: Disk layout: OpenBSD OT
usually, the inner tracks are fast, as I know -Shoufu Live, Love, Laugh On Mar 2, 2013, at 14:55, Friedrich Locke friedrich.lo...@gmail.com wrote: Hi folks, just wonder in a typical hard drive nowadays (SATA/SAS), the sector 0 is in the inner or outter track ? Which tracks are faster: the inner ones or the outter ? Thanks in advance.
Re: Softraid 3TB Problems
On Sat, Mar 02, 2013 at 01:18:09PM -0600, Brandon Tanner wrote: Anyone else having trouble getting bioctl to see more than 2TB when creating softraid0? I've got 2 x 3TB drives, BIOS sees them fine. dmesg on bootup: sd1 at scsibus0 targ 3 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e0bcda5 sd1: 2861588MB, 512 bytes/sector, 5860533168 sectors sd2 at scsibus0 targ 4 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e15ec80 sd2: 2861588MB, 512 bytes/sector, 5860533168 sectors notice the correct # of sectors above. disklabel -E sd1 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused disklabel -E sd2 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused # bioctl -c 1 -l /dev/sd1a,/dev/sd2a softraid0 softraid0: SR RAID 1 volume attached as sd3 sd3 at scsibus2 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed sd3: 2097148MB, 512 bytes/sector, 4294961093 sectors Yet, bioctl only sees it for 4294961093 sectors :( Softraid apparently truncates at 32 bits somewhere along the line. You might try instrumenting places where ssd_size is set, and where READ_CAPACITY/READ_CAPACITY_16 are processed. A quick scan did not cause a 32 bit truncation to leap out at me. Ken # bioctl -h sd3 Volume Status Size Device softraid0 0 Online 2.0T sd3 RAID1 0 Online 2.0T 0:0.0 noencl sd1a 1 Online 2.0T 0:1.0 noencl sd2a I have been troubleshooting this issue with the help of Scott McEachern extensively, and we are both stumped. He suggested I put this on misc to see if jsing might know anything. I have an Intel Desktop Motherboard model DP43TF. I can newfs the drives individually and mount them as 2.7TB, it's only when trying to make a softraid volume that it doesn't see more than 2TB. I am using the Feb 21, 2013 snapshot of 5.3, and my dmesg is at: http://pastebin.com/jqnpSsnC Anyone else experiencing this? http://search.gmane.org/?author=Scott+McEachernsort=date
Re: Disk layout: OpenBSD OT
On Sat, Mar 02, 2013 at 10:04:50PM +0100, Matthias Appel wrote: Am 02.03.2013 20:59, schrieb Miod Vallat: just wonder in a typical hard drive nowadays (SATA/SAS), the sector 0 is in the inner or outter track ? Which tracks are faster: the inner ones or the outter ? Only the manufacturer knows. Disks have been reporting fake geometries since more than 20 years. The electronic on the disk will do the necessary work to use the disk physical characteristic (with a varying number of sector per track) as cleverly as it can. Nowadays, you can't even be sure a given `software' is even contiguous on the disk. So, how is defrag (or avoiding fragmentation) done, if you can't be certain how the blocks are aligned? You can't. You can only de-frag the 'view' the hardware provides you. You can't outsmart it, so just be happy. Ken AFAIK, the last blocks are on the outside of the platters so, given a CAV, the speed is higher. The different speeds are measurablebut I don't know if noticeable (but I dont think so!) How SSDs handle block alignment is anoter story (wear-leveling et.al.) Regards, Matthias
Re: Softraid 3TB Problems
By the way, does softraid on amd64 support 4096 bytes per sector? On Sat, Mar 2, 2013 at 5:05 PM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 02, 2013 at 01:18:09PM -0600, Brandon Tanner wrote: Anyone else having trouble getting bioctl to see more than 2TB when creating softraid0? I've got 2 x 3TB drives, BIOS sees them fine. dmesg on bootup: sd1 at scsibus0 targ 3 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e0bcda5 sd1: 2861588MB, 512 bytes/sector, 5860533168 sectors sd2 at scsibus0 targ 4 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e15ec80 sd2: 2861588MB, 512 bytes/sector, 5860533168 sectors notice the correct # of sectors above. disklabel -E sd1 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused disklabel -E sd2 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused # bioctl -c 1 -l /dev/sd1a,/dev/sd2a softraid0 softraid0: SR RAID 1 volume attached as sd3 sd3 at scsibus2 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed sd3: 2097148MB, 512 bytes/sector, 4294961093 sectors Yet, bioctl only sees it for 4294961093 sectors :( Softraid apparently truncates at 32 bits somewhere along the line. You might try instrumenting places where ssd_size is set, and where READ_CAPACITY/READ_CAPACITY_16 are processed. A quick scan did not cause a 32 bit truncation to leap out at me. Ken # bioctl -h sd3 Volume Status Size Device softraid0 0 Online 2.0T sd3 RAID1 0 Online 2.0T 0:0.0 noencl sd1a 1 Online 2.0T 0:1.0 noencl sd2a I have been troubleshooting this issue with the help of Scott McEachern extensively, and we are both stumped. He suggested I put this on misc to see if jsing might know anything. I have an Intel Desktop Motherboard model DP43TF. I can newfs the drives individually and mount them as 2.7TB, it's only when trying to make a softraid volume that it doesn't see more than 2TB. I am using the Feb 21, 2013 snapshot of 5.3, and my dmesg is at: http://pastebin.com/jqnpSsnC Anyone else experiencing this? http://search.gmane.org/?author=Scott+McEachernsort=date
Re: Softraid 3TB Problems
On Sat, Mar 02, 2013 at 07:25:18PM -0600, Brandon Tanner wrote: By the way, does softraid on amd64 support 4096 bytes per sector? No matter what the architecture is softraid to date does not support devices with anything other than 512 bytes/sector. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: Softraid 3TB Problems
On Sat, Mar 02, 2013 at 07:25:18PM -0600, Brandon Tanner wrote: By the way, does softraid on amd64 support 4096 bytes per sector? I don't think so, but I haven't refreshed my memory of that recently. Ken On Sat, Mar 2, 2013 at 5:05 PM, Kenneth R Westerback kwesterb...@rogers.com wrote: On Sat, Mar 02, 2013 at 01:18:09PM -0600, Brandon Tanner wrote: Anyone else having trouble getting bioctl to see more than 2TB when creating softraid0? I've got 2 x 3TB drives, BIOS sees them fine. dmesg on bootup: sd1 at scsibus0 targ 3 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e0bcda5 sd1: 2861588MB, 512 bytes/sector, 5860533168 sectors sd2 at scsibus0 targ 4 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e15ec80 sd2: 2861588MB, 512 bytes/sector, 5860533168 sectors notice the correct # of sectors above. disklabel -E sd1 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused disklabel -E sd2 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused # bioctl -c 1 -l /dev/sd1a,/dev/sd2a softraid0 softraid0: SR RAID 1 volume attached as sd3 sd3 at scsibus2 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed sd3: 2097148MB, 512 bytes/sector, 4294961093 sectors Yet, bioctl only sees it for 4294961093 sectors :( Softraid apparently truncates at 32 bits somewhere along the line. You might try instrumenting places where ssd_size is set, and where READ_CAPACITY/READ_CAPACITY_16 are processed. A quick scan did not cause a 32 bit truncation to leap out at me. Ken # bioctl -h sd3 Volume Status Size Device softraid0 0 Online 2.0T sd3 RAID1 0 Online 2.0T 0:0.0 noencl sd1a 1 Online 2.0T 0:1.0 noencl sd2a I have been troubleshooting this issue with the help of Scott McEachern extensively, and we are both stumped. He suggested I put this on misc to see if jsing might know anything. I have an Intel Desktop Motherboard model DP43TF. I can newfs the drives individually and mount them as 2.7TB, it's only when trying to make a softraid volume that it doesn't see more than 2TB. I am using the Feb 21, 2013 snapshot of 5.3, and my dmesg is at: http://pastebin.com/jqnpSsnC Anyone else experiencing this? http://search.gmane.org/?author=Scott+McEachernsort=date
Re: Softraid 3TB Problems
On Sun, 3 Mar 2013, Brandon Tanner wrote: Anyone else having trouble getting bioctl to see more than 2TB when creating softraid0? I've got 2 x 3TB drives, BIOS sees them fine. dmesg on bootup: sd1 at scsibus0 targ 3 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e0bcda5 sd1: 2861588MB, 512 bytes/sector, 5860533168 sectors sd2 at scsibus0 targ 4 lun 0: ATA, ST3000DM001-1CH1, CC24 SCSI3 0/direct fixed naa.5000c5005e15ec80 sd2: 2861588MB, 512 bytes/sector, 5860533168 sectors notice the correct # of sectors above. disklabel -E sd1 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused disklabel -E sd2 p T OpenBSD area: 64-5860533168; size: 2.7T; free: 0.0T #size offset fstype [fsize bsize cpg] a: 2.7T 64RAID c: 2.7T0 unused # bioctl -c 1 -l /dev/sd1a,/dev/sd2a softraid0 softraid0: SR RAID 1 volume attached as sd3 This will assemble the volume from existing metadata if it exists. Any chance you created a 2TB 'a' partition to start with and created a softraid volume with it, then resized/recreated the disklabels? I'd certainly suggest zeroing the drives (via dd or similar), or using -C force (dd is more certain). The size is read directly from the disklabel, but only when the metadata is first created (after the metadata exists, we read the size from the metadata). All of the variables involved appear to be 64-bit types so I do not think that 32-bit truncation is occurring, although there are some signed/unsigned issues that should be addressed at some point. If zeroing and recreating the metadata fails to solve the issue, I can provide a diff that adds some debug info. sd3 at scsibus2 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed sd3: 2097148MB, 512 bytes/sector, 4294961093 sectors Yet, bioctl only sees it for 4294961093 sectors :( # bioctl -h sd3 Volume Status Size Device softraid0 0 Online 2.0T sd3 RAID1 0 Online 2.0T 0:0.0 noencl sd1a 1 Online 2.0T 0:1.0 noencl sd2a I have been troubleshooting this issue with the help of Scott McEachern extensively, and we are both stumped. He suggested I put this on misc to see if jsing might know anything. I have an Intel Desktop Motherboard model DP43TF. I can newfs the drives individually and mount them as 2.7TB, it's only when trying to make a softraid volume that it doesn't see more than 2TB. I am using the Feb 21, 2013 snapshot of 5.3, and my dmesg is at: http://pastebin.com/jqnpSsnC Anyone else experiencing this? http://search.gmane.org/?author=Scott+McEachernsort=date -- Reason is not automatic. Those who deny it cannot be conquered by it. Do not count on them. Leave them alone. -- Ayn Rand
Re: Softraid 3TB Problems
On Sun, 3 Mar 2013, Brandon Tanner wrote: By the way, does softraid on amd64 support 4096 bytes per sector? No. There is a large amount of work required to fix this since everything in softraid was originally designed around 512-byte blocks. It is somewhere on my TODO list, however I do not currently even have the hardware for development/testing. -- Reason is not automatic. Those who deny it cannot be conquered by it. Do not count on them. Leave them alone. -- Ayn Rand
