Re: RELENG_7 jerky mouse and skipping sound (still a problem -BETA3)
On Friday 11 January 2008, Kris Kennaway wrote: > Anish Mistry wrote: > > On Friday 04 January 2008, Kris Kennaway wrote: > >> Kris Kennaway wrote: > >>> David E. Thiel wrote: > On Sun, Dec 30, 2007 at 11:12:26PM +0100, Kris Kennaway wrote: > >> FWIW, the problem remains for me. Still terrible performance > >> during compiles. > > > > OK. Instead of going over all of the usual questions again, > > can you point me to a previous mail in which you explain your > > observations and test results in detail? > > The most recent is > http://marc.info/?l=freebsd-stable&m=119428719505129&w=2, but > it started way back at > http://marc.info/?l=freebsd-current&m=118998090512027&w=2. > > I've tried a lot of stuff in between, and all I've been able > to narrow it down to is that it's not a display driver issue, > and that none of my swap partition is getting used, so that's > not the problem. During compiles, my UP system with ULE still > gets very unresponsive when compiling, sometimes taking up to > 10 seconds just to draw a new terminal window. Even changing > focus with the window manager can take several seconds. I'd > like to provide more info, but I'm not sure what stats are > useful for this particular issue. Please let me know. dmesg is > at http://redundancy.redundancy.org/dmesg.txt, and kernel > config is at http://redundancy.redundancy.org/DEEPTHOUGHT. > Even though I'm still getting reported 80-95% memory > utilization and no paging, I'm going to get an extra gig of > RAM on order to see if that improves things. 2G of ram for a > desktop, what's the world coming to? ;) > >>> > >>> OK, can you obtain a schedgraph trace when the problem is > >>> manifesting? See /usr/src/tools/sched/ and previous discussion > >>> in this or related threads. > >> > >> Anyone? Time is rapidly running out to get this fixed in time > >> for 7.0-RELEASE, so we need this trace ASAP. > > > > http://am-productions.biz/docs/ktr.out.gz > > > > Is there a way to export the graph once I'm looking in it in > > schedgraph.py? > > The above trace does not show any compiler activity. What was the > process that was interfering with X performance in your case? > > You also have a CPU load of up to 17, which is rather high. I am > not sure it is reasonable to expect your machine to stay perfectly > responsive while it is under that kind of load. http://am-productions.biz/docs/ktr-2.out.gz Here is another run while compiling thunderbird, though it might just show the same thing. It lasted about 20 seconds and hopefully I caught some of it. -- Anish Mistry signature.asc Description: This is a digitally signed message part.
Re: Kernel panic when kldunload acpi_video
On Wed, 16 Jan 2008 14:04:39 +1100 (EST)
Ian Smith <[EMAIL PROTECTED]> wrote:
> Beto, hi,
>
> not to detract from the seriousness of the problem,
Hey Ian,
> two dumb questions:
>
> 1) why would you need to unload it?
no reason at all really - other than I wanted to see if it made any difference
and I stumbled upon it...or rather the whole system stumbled and crashed...
> ie did loading it fix the problem?
nope - it doesn't seem to be related to the ACPI brightness control.
>
> 2) does this mean the acpi_ibm brightness controls aren't working in X?
means exactly that, for me. ACPI msgs are triggered - the tpb util brings up
the meter on the screen, but nothing actually changes. I need to double check
with DRI disabled, but I think it wasnt working either. Tpb has never actually
changed the meter of brightness, as it does with Volume - it has always been
stuck in 0 ... never bothered to chase that down because the brightness changes
happened anyway.
It does work fine on text mode.
PS : finally hit 31+ in Syd... i will need a separate AC unit to cool down the
'breathing' of the servers on my desk :P Luckily i'm not in Melb ;)...
B
_
{Beto|Norberto|Numard} Meijome
"Unix is very simple, but it takes a genius to understand the simplicity."
Dennis Ritchie
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic when kldunload acpi_video
On Wed, 16 Jan 2008, Norberto Meijome wrote: > Hi guys, > I am not sure if this is acpi related or due to other issues. > > running latest FreeBSD (built yesterday from fresh sources : > > FreeBSD ayiin.xxx.com.au 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #14: > Wed Jan 16 01:38:57 EST 2008 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYIIN i386 > > Hardware is Thinkpad z60m , 1.5 GB of RAM. dmesg (non verbose) is @ > end of this mail > > I had : > > Id Refs AddressSize Name > 1 30 0xc040 63b77c kernel > 21 0xc0a3c000 84a0 linprocfs.ko > 33 0xc0a45000 28878linux.ko > 41 0xc0a6e000 10328if_iwi.ko > 51 0xc0a7f000 155c4snd_hda.ko > 62 0xc0a95000 4a36csound.ko > 72 0xc0ae 6a184acpi.ko > 81 0xc0b4b000 4ff4 acpi_ibm.ko > 91 0xc0b5 2f338iwi_ibss.ko > 101 0xc0b8 2f4b0iwi_monitor.ko > 111 0xc0bb 22c98radeon.ko > 122 0xc0bd3000 10e98drm.ko > 131 0xc4b22000 d000 ipfw.ko > 141 0xccd23000 2000 rtc.ko > > PLUS acpi_video.ko loaded in /boot/loader.conf.local. > > doing a kldunload acpi_video would panic the kernel. Also happened in > single user. > > I have crash dumps, but unfortunately, i wiped the kernel.debug after > starting a full clean rebuild of kernel + world for today's changes. > > I don't know whether this problem happened before 7 - i only started > loading acpi_video for a few weeks when I realised I couldn't change > the brightness on the screen anymore when under X (works ok in a > vconsole) Beto, hi, not to detract from the seriousness of the problem, two dumb questions: 1) why would you need to unload it? ie did loading it fix the problem? 2) does this mean the acpi_ibm brightness controls aren't working in X? cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic when kldunload acpi_video
On Tue, 15 Jan 2008 19:20:37 -0500
Nathan Lay <[EMAIL PROTECTED]> wrote:
> This happens to me as well on a Thinkpad T43...both on 6.2 and 7.0-RC1.
thanks for the info.
I rebuilt the kernel (but not world yet) with latest src :
FreeBSD ayiin.xxx.com.au 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #15: Wed Jan 16
10:28:53 EST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYIIN i386
i rebooted into single user mode. Loaded acpi_video (I took it out of my
loader.conf.local), I removed it and Boom!, panic.
B
_
{Beto|Norberto|Numard} Meijome
"Humans die and turn to dust, but writing makes us remembered"
4000-year-old words of an Egyptian scribe
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fwd: FreeBSD 6.3 and Intel G33
On Wed, 16 Jan 2008, Eric Anholt wrote: > I took a quick review of the docs again and I think it's almost > complete. The gtt_size detection is broken, though. We should have > gtt_size (the amount of graphics stolen memory used for storing the > GTT data) equal to zero on this hardware, instead of using the G965 > path. However, this also requires current xf86-video-intel, which > fixes the mistaken assumption we originally had for xf86-video-intel > and linux agp that the gtt stolen memory was stolen out of graphics > stolen memory. OK.. Not sure what GTT is though :) > Updating just the AGP driver for fixing the bad stolen memory > assumption means that the 2d driver tries to bind memory lower than > the AGP driver will let you, and your server won't start. The > "proper" fix would be for us to remember the stolen memory address in > the GTT and let you bind over them, but restore them on unbind. Some > day we would love to release this memory to the general page > allocator and get rid of this stolen memory disaster. > > To test, install xf86-video-intel from ports, uncomment those PCI > IDs, and start X. If things are working, then it probably means > you're good to go and we can enable it by default. If you're getting > the "agp0: trying to bind into stolen memory" complaint, you need > current 2D from > git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel and we > should cherry-pick the relevant patch into our ports. I've back ported the AGP driver (and vgapci) and I get.. vgapci0: port 0x1c60-0x1c67 mem 0xd230-0xd237,0xc000-0xcfff,0xd200-0xd20f irq 16 at device 2.0 on pci0 Looking at devid 0x29c28086 Matched Intel G33 SVGA controller agp_i810_probe called Looking at devid 0x29c28086 Matched Intel G33 SVGA controller Looking at devid 0x29c28086 Matched Intel G33 SVGA controller agp_i810_probe called Looking at devid 0x29c28086 Matched Intel G33 SVGA controller Looking at devid 0x29c28086 Matched Intel G33 SVGA controller agp0: on vgapci0 Looking at devid 0x29c28086 Matched Intel G33 SVGA controller Looking at devid 0x29c28086 Matched Intel G33 SVGA controller agp0: detected 7676k stolen memory agp0: aperture size is 256M (excuse the spam - I kept adding stuff to it trying to work out why it wasn't doing anything then realised the new AGP needed vgapci) With the ports xf86-video-intel I get.. (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x006ff000 (pgoffset 1791) (WW) intel(0): xf86BindGARTMemory: binding of gart memory with key 1 at offset 0x6ff000 failed (Invalid argument) Fatal server error: Couldn't bind memory for front buffer I tried to build your git repo of the driver but I am getting.. gmake[3]: Entering directory `/local0/tmp/xf86-video-intel/src' /usr/local/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..-Wall -Wpointer-arith -Wstrict-prototypes-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_THREAD_SAFE -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -DI830_XV -DI830_USE_XAA -DI830_USE_EXA -g -O2 -MT i810_driver.lo -MD -MP -MF .deps/i810_driver.Tpo -c -o i810_driver.lo i810_driver.c gcc -DHAVE_CONFIG_H -I. -I.. -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_THREAD_SAFE -I/usr/local/include/xorg -I/usr/local/include/pixman-1 -I/usr/local/include -I/usr/local/include -I/usr/local/include/drm -I/usr/local/include/X11/dri -DI830_XV -DI830_USE_XAA -DI830_USE_EXA -g -O2 -MT i810_driver.lo -MD -MP -MF .deps/i810_driver.Tpo -c i810_driver.c -fPIC -DPIC -o .libs/i810_driver.o i810_driver.c:456: error: `PACKAGE_VERSION_MAJOR' undeclared here (not in a function) i810_driver.c:456: error: initializer element is not constant i810_driver.c:456: error: (near initialization for `intelVersRec.majorversion') i810_driver.c:456: error: `PACKAGE_VERSION_MINOR' undeclared here (not in a function) i810_driver.c:456: error: initializer element is not constant i810_driver.c:456: error: (near initialization for `intelVersRec.minorversion') i810_driver.c:456: error: `PACKAGE_VERSION_PATCHLEVEL' undeclared here (not in a function) ... I modified config.h to add those #defines and the man Makefile (configure is fun!) and installed but now I get.. (==) intel(0): Write-combining range (0xa,0x1) was already clear (II) EXA(0): Offscreen pixmap area of 3072 bytes (II) EXA(0): Driver registered support for the following operations: (II) Solid (II) Copy (II) Composite (RENDER acceleration) (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): xf86BindGARTMemory: bind key 8
Re: Kernel panic when kldunload acpi_video
Norberto Meijome wrote:
Hi guys,
I am not sure if this is acpi related or due to other issues.
running latest FreeBSD (built yesterday from fresh sources :
FreeBSD ayiin.xxx.com.au 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #14: Wed Jan 16
01:38:57 EST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYIIN i386
Hardware is Thinkpad z60m , 1.5 GB of RAM. dmesg (non verbose) is @ end of this
mail
I had :
Id Refs AddressSize Name
1 30 0xc040 63b77c kernel
21 0xc0a3c000 84a0 linprocfs.ko
33 0xc0a45000 28878linux.ko
41 0xc0a6e000 10328if_iwi.ko
51 0xc0a7f000 155c4snd_hda.ko
62 0xc0a95000 4a36csound.ko
72 0xc0ae 6a184acpi.ko
81 0xc0b4b000 4ff4 acpi_ibm.ko
91 0xc0b5 2f338iwi_ibss.ko
101 0xc0b8 2f4b0iwi_monitor.ko
111 0xc0bb 22c98radeon.ko
122 0xc0bd3000 10e98drm.ko
131 0xc4b22000 d000 ipfw.ko
141 0xccd23000 2000 rtc.ko
PLUS acpi_video.ko loaded in /boot/loader.conf.local.
doing a kldunload acpi_video would panic the kernel. Also happened in single
user.
I have crash dumps, but unfortunately, i wiped the kernel.debug after starting
a full clean rebuild of kernel + world for today's changes.
I don't know whether this problem happened before 7 - i only started loading
acpi_video for a few weeks when I realised I couldn't change the brightness on
the screen anymore when under X (works ok in a vconsole)
Anyway, I followed the steps in the handbook to get some info about the crash.
I've included 2 crashes here, both caused with kldunload acpi_video:
[EMAIL PROTECTED] [Wed Jan 16 10:08:47 2008]
/usr/obj/usr/src/sys/AYIINESC[0m^B
ESCkESC\# ^Gkgdb kernel.debug /var/crash/vmc^Gore.8
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x10
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0ae1889
stack pointer = 0x28:0xf384fb4c
frame pointer = 0x28:0xf384fb58
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 2395 (kldunload)
trap number = 12
panic: page fault
Uptime: 3m30s
Physical memory: 1526 MB
Dumping 283 MB: 268 252 236 220 204 188 172 156 140 124 108 92 76 60 44 28 12
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc0ae1889
No source file for address 0xc0ae1889.
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc05f17d3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc05f19d4 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3 0xc086d8bc in trap_fatal (frame=0xf384fb0c, eva=16)
at /usr/src/sys/i386/i386/trap.c:899
#4 0xc086db2b in trap_pfault (frame=0xf384fb0c, usermode=0, eva=16)
at /usr/src/sys/i386/i386/trap.c:812
#5 0xc086e4f6 in trap (frame=0xf384fb0c) at /usr/src/sys/i386/i386/trap.c:490
#6 0xc085720b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0ae1889 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) ^M
[EMAIL PROTECTED] [Wed Jan 16 10:12:15 2008]
/usr/obj/usr/src/sys/AYIINESC[0m^B
ESCkESC\# ESC[Kkgdb kernel.debug /var/crash/vmcore.7
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x10
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0ae1889
stack pointer = 0x28:0xf37b8b4c
frame pointer = 0x28:0xf37b8b58
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor efla
Kernel panic when kldunload acpi_video
Hi guys,
I am not sure if this is acpi related or due to other issues.
running latest FreeBSD (built yesterday from fresh sources :
FreeBSD ayiin.xxx.com.au 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #14: Wed Jan 16
01:38:57 EST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYIIN i386
Hardware is Thinkpad z60m , 1.5 GB of RAM. dmesg (non verbose) is @ end of this
mail
I had :
Id Refs AddressSize Name
1 30 0xc040 63b77c kernel
21 0xc0a3c000 84a0 linprocfs.ko
33 0xc0a45000 28878linux.ko
41 0xc0a6e000 10328if_iwi.ko
51 0xc0a7f000 155c4snd_hda.ko
62 0xc0a95000 4a36csound.ko
72 0xc0ae 6a184acpi.ko
81 0xc0b4b000 4ff4 acpi_ibm.ko
91 0xc0b5 2f338iwi_ibss.ko
101 0xc0b8 2f4b0iwi_monitor.ko
111 0xc0bb 22c98radeon.ko
122 0xc0bd3000 10e98drm.ko
131 0xc4b22000 d000 ipfw.ko
141 0xccd23000 2000 rtc.ko
PLUS acpi_video.ko loaded in /boot/loader.conf.local.
doing a kldunload acpi_video would panic the kernel. Also happened in single
user.
I have crash dumps, but unfortunately, i wiped the kernel.debug after starting
a full clean rebuild of kernel + world for today's changes.
I don't know whether this problem happened before 7 - i only started loading
acpi_video for a few weeks when I realised I couldn't change the brightness on
the screen anymore when under X (works ok in a vconsole)
Anyway, I followed the steps in the handbook to get some info about the crash.
I've included 2 crashes here, both caused with kldunload acpi_video:
[EMAIL PROTECTED] [Wed Jan 16 10:08:47 2008]
/usr/obj/usr/src/sys/AYIINESC[0m^B
ESCkESC\# ^Gkgdb kernel.debug /var/crash/vmc^Gore.8
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x10
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0ae1889
stack pointer = 0x28:0xf384fb4c
frame pointer = 0x28:0xf384fb58
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 2395 (kldunload)
trap number = 12
panic: page fault
Uptime: 3m30s
Physical memory: 1526 MB
Dumping 283 MB: 268 252 236 220 204 188 172 156 140 124 108 92 76 60 44 28 12
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc0ae1889
No source file for address 0xc0ae1889.
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc05f17d3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc05f19d4 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3 0xc086d8bc in trap_fatal (frame=0xf384fb0c, eva=16)
at /usr/src/sys/i386/i386/trap.c:899
#4 0xc086db2b in trap_pfault (frame=0xf384fb0c, usermode=0, eva=16)
at /usr/src/sys/i386/i386/trap.c:812
#5 0xc086e4f6 in trap (frame=0xf384fb0c) at /usr/src/sys/i386/i386/trap.c:490
#6 0xc085720b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0ae1889 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) ^M
[EMAIL PROTECTED] [Wed Jan 16 10:12:15 2008]
/usr/obj/usr/src/sys/AYIINESC[0m^B
ESCkESC\# ESC[Kkgdb kernel.debug /var/crash/vmcore.7
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x10
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0ae1889
stack pointer = 0x28:0xf37b8b4c
frame pointer = 0x28:0xf37b8b58
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enab
Re: Why does firefox keep locking up on me?
> Hey all, > > On Tue, 15 Jan 2008, Christian Walther wrote: > > > Hello Bob, > > > > On 15/01/2008, Bob Vaughan <[EMAIL PROTECTED]> wrote: > >> I've been having a problem on one particular machine with Firefox locking > >> up > >> on me, requiring a hard kill to get rid of it. > >> > >> The problem is thus: Firefox starts normally, but as soon as I go to a > >> site that requires authentication, or any other form of user input, > >> It will freeze as soon as I start entering my userid. > > [...] > >> > >> Any ideas where to start looking? > > > > Since you've done nearly everything that could affect a binary working > > properly, I think we can rule out a problem with the base system, X or > > the browser itself. > > I guess the problem might be related to your ~/.mozilla directory. I > > noticed that a large variety of problems might be related to something > > been broken inside it. > > This might be an extension that might be incompatible and that isn't > > installed on any of the other machines. > > I'd recommend you to shut down firefox, open a terminal window and > > rename the directory to something different. Please note that it > > contains all settings you've made in *any* mozilla product (sunbird, > > thunderbird). > > Start firefox again and give it a try. > > Another neat trick that I oddly enough learned using OS-X is to just setup > a new user on the box and reserve it for checking out odd problems that > might be caused by any user-specific settings. This has really helped me > out a number of times. Very different OSes, but both end up with a ton of > user-specific stuff in $HOME... > > Charles > > > HTH > > Christian Thanks for the tip.. I didn't have any extentions, but moving .mozilla/ out of the way did seem to clear up the problem.. It's my lab machine, so I don't have that much on it. Thanks all.. -- -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie @ tantivy.net | | P.O. Box 19792, Stanford, Ca 94309 | -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup solution suggestions
On Jan 15, 2008, at 22:09 , Aristedes Maniatis wrote: On 15/01/2008, at 8:52 PM, Johan Ström wrote: I'm looking to invest in some new hardware for backup. probably some kind of NAS (a 4-disk 1U NAS or something in that size). The thing is that I won't be the only one with access to this box, thus I would like to secure my data. What I would like is encryption both for the transfer to the box, and encrypted on disk. The data on disk should not be readable by anyone but me (ie the other user(s) of the box should not be able to read it, at least not without a big effort). Take a look at bacula. It is a proper backup system, meaning that it does incremental backups, etc. Storage pools can be encrypted. Not sure if the network stream can be, but that could be solved with an ssh tunnel. And it is open source, reliable and runs nicely on FreeBSD. My main problem with existing solutions is this "gap" of encryption on the backup server side. I dont want it to be readable outside of my box (without encryption keys ofcourse), so as soon as I send it of from my box I want it to be encrypted over the link, and down on the disk. Not decrypted on the remote box, to then be encrypted again (with keys available on that box) and then stored to disk. That would allow any users of that box (yes sure you can have file permissions but lets assume someone else have root access there) to read my files. Simple Example: I create regular tarball (gziped maybee) with some files i want to backup, Then i encrypt this file with ie gpg. Then i send of this file using some unspecified network protocol to the storage server. Encrypted all the way, from my end to the remote disk.. The downside is that it is a static file.. not a "dynamic filesystem", nothing I can mount and have easy access to individual files from. *Thats* what I'm looking for. -- Johan___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_7 2008/01/10 desktop system also periodically freezes
On Sun, 13.01.2008 at 17:25:24 -0500, J.R. Oldroyd wrote: > David's suggestion re powerd may be relevant. I'd noticed that the > problem seems to happen when the system is idle. I posted earlier that > it seems like I can do all sorts of work without a problem then I stop for > a phone call and when I resume it hangs. I tend to notice a lot of hangs > when typing an email. Try with running/looping some MP3 or WAV files. My system never, ever froze during sound playback. Only when "idle". But since I'm running multiple wmdocklets that update periodically "idle" is not really true. Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0BETA4 desktop system also periodically freezes
On Wed, 09.01.2008 at 14:18:59 -0500, J.R. Oldroyd wrote: > I believe this same problem may also be present on 7.0, at least on > the BETA releases; BETA4 is the latest I have here. > > I have the same problem on two systems here: periodically the systems > will stop dead (no mouse action, no ping responses from other systems, > processes with windows on the screen also freeze); the hangs can be > anything from a few seconds to several MINUTES; then it all comes back > "as if nothing happened" except that keyboard input during the freeze > is lost. Most of my freezes are a few seconds long, some are in the > 15-60 second range, but (fortunately, rarely) I have seen some that > lasted 10-15 MINUTES! > [...] > > But the phone might ring, so I'll stop doing things, the system will > become pretty-much idle, then I'll go to move the mouse and it might be > frozen. When it comes back, the small load peak shows, but top and ps > show nothing unusual. Sorry for the late reply, I'm behind with reading mails. But to let you know that you are not the only person, I witnessed pretty much the same thing. It happens *very* rarely but it does happen from time to time. I'm running 7.0-PRERELEASE with SCHED_ULE on i386 with 1GB RAM and ZFS on a GELI provider. The system is running Xorg7.3 with the radeon driver (I've come to blame Xorg 7.3 for all my recent problems ...) Anyway, it did *never* happen when I'm playing MP3s, but leaving mplayer paused for a couple of minutes I would return and the system was basically frozen. Sometimes after a couple of minutes it would unfreeze and replay all keystrokes and mouse movements but most of the time I'm too impatient to wait. I press the power button and nothing happens. A few minutes later it would do a regular shutdown. Strange things, indeed. The only way, I think I could track this down would be to hook up remote debugging via firewire and break to ddb, but I lack a second firewire laptop :( Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why does firefox keep locking up on me?
Hey all, On Tue, 15 Jan 2008, Christian Walther wrote: Hello Bob, On 15/01/2008, Bob Vaughan <[EMAIL PROTECTED]> wrote: I've been having a problem on one particular machine with Firefox locking up on me, requiring a hard kill to get rid of it. The problem is thus: Firefox starts normally, but as soon as I go to a site that requires authentication, or any other form of user input, It will freeze as soon as I start entering my userid. [...] Any ideas where to start looking? Since you've done nearly everything that could affect a binary working properly, I think we can rule out a problem with the base system, X or the browser itself. I guess the problem might be related to your ~/.mozilla directory. I noticed that a large variety of problems might be related to something been broken inside it. This might be an extension that might be incompatible and that isn't installed on any of the other machines. I'd recommend you to shut down firefox, open a terminal window and rename the directory to something different. Please note that it contains all settings you've made in *any* mozilla product (sunbird, thunderbird). Start firefox again and give it a try. Another neat trick that I oddly enough learned using OS-X is to just setup a new user on the box and reserve it for checking out odd problems that might be caused by any user-specific settings. This has really helped me out a number of times. Very different OSes, but both end up with a ton of user-specific stuff in $HOME... Charles HTH Christian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fwd: FreeBSD 6.3 and Intel G33
On Tue, 2008-01-15 at 20:12 +1030, Daniel O'Connor wrote: > I just checked the CVS logs and found that you added G33 support but > left it disconnected due to a lack of testing... Huh, I forgot. > How can I test it? :) I took a quick review of the docs again and I think it's almost complete. The gtt_size detection is broken, though. We should have gtt_size (the amount of graphics stolen memory used for storing the GTT data) equal to zero on this hardware, instead of using the G965 path. However, this also requires current xf86-video-intel, which fixes the mistaken assumption we originally had for xf86-video-intel and linux agp that the gtt stolen memory was stolen out of graphics stolen memory. Updating just the AGP driver for fixing the bad stolen memory assumption means that the 2d driver tries to bind memory lower than the AGP driver will let you, and your server won't start. The "proper" fix would be for us to remember the stolen memory address in the GTT and let you bind over them, but restore them on unbind. Some day we would love to release this memory to the general page allocator and get rid of this stolen memory disaster. To test, install xf86-video-intel from ports, uncomment those PCI IDs, and start X. If things are working, then it probably means you're good to go and we can enable it by default. If you're getting the "agp0: trying to bind into stolen memory" complaint, you need current 2D from git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel and we should cherry-pick the relevant patch into our ports. To be sure that everything's working, also enable DRI by installing updated DRM from git://anongit.freedesktop.org/git/mesa/drm (bsd-core directory, make all install). It may complain if you have witness enabled, since I haven't brought over the witness fix from -current yet. > email message attachment (forwarded message), ""Daniel O'Connor" > <[EMAIL PROTECTED]>: FreeBSD 6.3 and Intel G33" > > Forwarded Message > > From: Daniel O'Connor <[EMAIL PROTECTED]> > > To: freebsd-stable@freebsd.org > > Cc: Hiroshi Nishida <[EMAIL PROTECTED]> > > Subject: FreeBSD 6.3 and Intel G33 > > Date: Tue, 15 Jan 2008 17:01:04 +1030 > > > > Hi, > > I'm trying to get a system with an Intel G33 video chipset in it > > (Supermicro C2SBA) working with the Intel driver but I'm not having much > > luck.. > > > > I took the patch from Hiroshi Nishida and added the G33 PCI ID's for it > > now I get agp/i810 attaching to it.. > > Matched G33 > > Matched for Intel G33 IG SVGA controller > > Matched G33 > > Matched for Intel G33 IG SVGA controller > > agp0: port 0x1c60-0x1c67 mem > > 0xd230-0xd237,0xc000-0xcfff,0xd200-0xd20f irq 16 at > > device 2.0 on pci0 > > agp_i810_attach() called > > Attaching G33 > > Chip Type: 5, rid:10 > > agp0: detected 7676k stolen memory > > agp0: aperture size is 256M > > > > I tried running X and got this in dmesg.. > > agp0: trying to bind into stolen memory > > > > and this in the X log... > > (==) intel(0): Backing store disabled > > (==) intel(0): Silken mouse enabled > > (II) intel(0): Initializing HW Cursor > > (II) intel(0): xf86BindGARTMemory: bind key 6 at 0x006ff000 (pgoffset 1791) > > (WW) intel(0): xf86BindGARTMemory: binding of gart memory with key 6 > > at offset 0x6ff000 failed (Invalid argument) > > > > Fatal server error: > > Couldn't bind memory for front buffer > > > > I then added the PCI ID (0x8086 / 0x29c2) to > > /usr/src/sys/dev/drm/drm_pciids.h > > and now I get this in dmesg.. > > drmsub0: : (child of agp_i810.c) on agp0 > > info: [drm] AGP at 0xd230 0MB > > info: [drm] Initialized i915 1.5.0 20060119 > > > > but that does not affect the error from X. > > > > I see a NetBSD patch at > > http://mail-index.netbsd.org/netbsd-bugs/2007/09/05/0015.html but I haven't > > tried shoe horning that in yet.. > > -- Eric Anholt [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Backup solution suggestions
On 15/01/2008, at 8:52 PM, Johan Ström wrote: I'm looking to invest in some new hardware for backup. probably some kind of NAS (a 4-disk 1U NAS or something in that size). The thing is that I won't be the only one with access to this box, thus I would like to secure my data. What I would like is encryption both for the transfer to the box, and encrypted on disk. The data on disk should not be readable by anyone but me (ie the other user(s) of the box should not be able to read it, at least not without a big effort). Take a look at bacula. It is a proper backup system, meaning that it does incremental backups, etc. Storage pools can be encrypted. Not sure if the network stream can be, but that could be solved with an ssh tunnel. And it is open source, reliable and runs nicely on FreeBSD. Ari Maniatis --> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very bad performances with wpi and 7.0-RC1
Hi Nicolas! My card on Dell Latitude D830 is somewhat different (note subdevice): # sysctl -a |grep wpi net.wlan.0.%parent: wpi0 debug.wpi: 0 dev.wpi.0.%desc: Intel(R) PRO/Wireless 3945ABG dev.wpi.0.%driver: wpi dev.wpi.0.%location: slot=0 function=0 handle=\_SB_.PCI0.RP02.PXS2 dev.wpi.0.%pnpinfo: vendor=0x8086 device=0x4222 subvendor=0x8086 subdevice=0x1021 class=0x028000 dev.wpi.0.%parent: pci12 # uname -v FreeBSD 7.0-PRERELEASE #6: Wed Jan 9 20:57:45 EET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC aside this, everything else is quite the same. I had bad performance with syslink (I believe, could be wrong at hotel) and everything is good with DLink DI-524. PS. Also seeing messages while associating/DHCPing: wpi0: wpi_cmd: cmd 72 not sent, busy wpi0: wpi_cmd: cmd 72 not sent, busy wpi0: discard frame w/o packet header 2008/1/15, Nicolas Letellier <[EMAIL PROTECTED]>: > Hello, > > I use FreeBSD 7.0-RC1 with my laptop (Asustek A6000 Series). > Performances with wpi are very very bad: in my LAN, I download a file at > 4 k/s. In Internet, I would believe I use a 56 k connection :-) > > In this laptop, I have a NIC (chipset re), and I don't have any problem > with. The connection is very very stable. The problem is juste with wpi > and my Wireless NIC. > > I test OpenBSD-current, and I didn't have any problem with wpi. The > problem is juste with FreeBSD 7.0-RC1. I have any firewalls, nothing. > All is perfect with my NIC re. > > I test with GENERIC, and I build my own kernel (with wpi support build > into kernel). The problem is the same. > > See more informations here: > > numenor# cat /boot/loader.conf > nvidia_load="YES" > wpifw_load="YES" > legal.intel_wpi.license_ack=1 > > > numenor# cat /etc/rc.conf > defaultrouter="192.168.1.249" > hostname="numenor." > ifconfig_wpi0="inet 192.168.1.4 ssid Nicoelro_Wifi" > > numenor# ifconfig wpi0 > wpi0: flags=8843 metric 0 mtu 1500 > ether 00:13:02:dd:05:5f > inet 192.168.1.4 netmask 0xff00 broadcast 192.168.1.255 > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) > status: associated > ssid Nicoelro_Wifi channel 10 (2457 Mhz 11g) bssid 00:0f:b5:b9:9f:cc > authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 > protmode CTS > > > Sometimes, I see this message: > wpi0: discard frame w/o packet header > > numenor# sysctl -a | grep wpi > net.wlan.0.%parent: wpi0 > debug.wpi: 0 > dev.wpi.0.%desc: Intel(R) PRO/Wireless 3945ABG > dev.wpi.0.%driver: wpi > dev.wpi.0.%location: slot=0 function=0 handle=\_SB_.PCI0.P0P7.WLAN > dev.wpi.0.%pnpinfo: vendor=0x8086 device=0x4222 subvendor=0x8086 > subdevice=0x1001 class=0x028000 > dev.wpi.0.%parent: pci3 > > > numenor# dmesg > *Copyright (c) 1992-2008 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.0-RC1 #1: Mon Jan 14 18:12:58 CET 2008 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NUMENOR > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Genuine Intel(R) CPU T2300 @ 1.66GHz (1662.52-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x6e8 Stepping = 8 > > Features=0xbfe9fbff > Features2=0xc189 > AMD Features=0x10 > Cores per package: 2 > real memory = 1073545216 (1023 MB) > avail memory = 1032773632 (984 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > hptrr: HPT RocketRAID controller driver v1.1 (Jan 14 2008 18:12:38) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a (3) failed > acpi0: reservation of 10, 3ff0 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > acpi_ec0: port 0x62,0x66 on acpi0 > cpu0: on acpi0 > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > est: cpu_vendor GenuineIntel, msr 6130a2c06000613 > device_attach: est0 attach returned 6 > p4tcc0: on cpu0 > cpu1: on acpi0 > ACPI Warning (tbutils-0243): Incorrect checksum in table [SSDT] - D6, > should be 9C [20070320] > est1: on cpu1 > p4tcc1: on cpu1 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > nvidia0: mem > 0xfd00-0xfdff,0xc000-0xcfff,0xfc00-0xfcff irq 16 > at device 0.0 on pci1 > nvidia0: [GIANT-LOCKED] > nvidia0: [ITHREAD] > pcm0: mem > 0xfebfc000-0xfebf irq 21 at device 27.0 on pci0 > pcm0: [ITHREAD] > pcib2: irq 16 at device 28.0 on pci0 > pci2: on pcib2 > re0: port 0xc800-0xc8ff mem > 0xfe0ff000-0xfe0f irq 16 at device 0.0 on pci2 > re0: Using 2 MSI messages > miibus0: on re0 > rgephy0: PHY 1 on miib
Re: 6.3-RELEASE
On Jan 15, 2008 10:25 PM, Mark Linimon <[EMAIL PROTECTED]> wrote: > On Tue, Jan 15, 2008 at 09:51:13PM +0200, George Kontostanos wrote: > > So may I guess that we have a release ? > > This question happens every time we get near a release. > > There will be a release when, and only when, a signed email is sent from > the Release Engineering team to the various mailing lists. In the meantime, > final preparations are being made, such as giving the mirrors time to get > the bits, so that they will be there when the announcement goes out. > > Please be patient. > > mcl > Sorry Mark, I just got a bit enthusiastic with it! George ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.3-RELEASE
On Jan 15, 2008 10:23 PM, Royce Williams <[EMAIL PROTECTED]> wrote: > George Kontostanos wrote, on 1/15/2008 10:51 AM: > > So may I guess that we have a release ? > > > > 6.3-RELEASE FreeBSD 6.3-RELEASE #1: Tue Jan 15 21:25:07 EET 2008 > > Not quite yet ... > > # sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade > Looking up update.FreeBSD.org mirrors... 1 mirrors found. > Fetching metadata signature for 6.3-RC2 from update1.FreeBSD.org... done. > Fetching metadata index... done. > Fetching 1 metadata patches. done. > Applying metadata patches... done. > Inspecting system... done. > > [snip] > > Does this look reasonable (y/n)? y > > Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... > failed. > No mirrors remaining, giving up. > > > Royce > > -- > Royce D. Williams- IP Engineering, ACS > http://www.tycho.org/royce/ - PGP: 3FC087DB/1776A531 > Reproof should not exhaust its power upon petty failings. - S.Johnson > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > Well, I followed the old traditional way of syncing my code and then doing the the build world & kernel thing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: G965 patch for 6.3-Beta
On Wed, 16 Jan 2008, Hiroshi Nishida wrote: > The patch is based on the outdated FreeBSD 7-current, so we should > look at the latest one. OK, I see. I sent an email to Eric about it because according to the commit logs (which I only noticed later) G33 support is there but disconnected due to a lack of testing. > Fortunately I have 8 G33 machines (Intel DG33BU M/B) but they are > going to be used for long long experiments with FreeBSD 7.0 or > Solaris very soon. > > If I have a chance, I'll try to check with G33. That would be great, thanks. > Sorry for no immediate help. No problem, it is not critical, just one of those "It would be nice" things :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: 6.3-RELEASE
George Kontostanos wrote, on 1/15/2008 10:51 AM: So may I guess that we have a release ? 6.3-RELEASE FreeBSD 6.3-RELEASE #1: Tue Jan 15 21:25:07 EET 2008 Not quite yet ... # sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 6.3-RC2 from update1.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Inspecting system... done. [snip] Does this look reasonable (y/n)? y Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... failed. No mirrors remaining, giving up. Royce -- Royce D. Williams- IP Engineering, ACS http://www.tycho.org/royce/ - PGP: 3FC087DB/1776A531 Reproof should not exhaust its power upon petty failings. - S.Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.3-RELEASE
On Tue, Jan 15, 2008 at 09:51:13PM +0200, George Kontostanos wrote: > So may I guess that we have a release ? This question happens every time we get near a release. There will be a release when, and only when, a signed email is sent from the Release Engineering team to the various mailing lists. In the meantime, final preparations are being made, such as giving the mirrors time to get the bits, so that they will be there when the announcement goes out. Please be patient. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What current Dell Systems are supported/work
On Tuesday 15 January 2008 10:25:14 am Vivek Khera wrote: > > On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: > > >> *: This is the default behavior for 7.0, I have not encountered the > >> problem mentioned above on any 1950/2950 boxes so far I have tested. > > > > I will enable MSI by default on 6.x now (so will take affect for 6.4). > > We've also enabled it by default on 6.x at work. > > > > Where can one go to read up on what MSI is and how it helps us? > > Is enabling it just setting a sysctl? Does that have to be done in > loader.conf or can it happen later? loader.conf (though it is now default on in RELENG_6). hw.pci.msi_enable=1 hw.pci.msix_enable=1 -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.3-RELEASE
So may I guess that we have a release ? 6.3-RELEASE FreeBSD 6.3-RELEASE #1: Tue Jan 15 21:25:07 EET 2008 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup solution suggestions
On Jan 15, 2008, at 13:44 , Jeremy Chadwick wrote: On Tue, Jan 15, 2008 at 12:40:02PM +0100, Vladimir Botka wrote: Dne Tue, 15 Jan 2008 10:52:56 +0100 Johan Ström <[EMAIL PROTECTED]> napsal(a): Hello I'm looking to invest in some new hardware for backup. probably some kind of NAS (a 4-disk 1U NAS or something in that size). The thing is that I won't be the only one with access to this box, thus I would like to secure my data. What I would like is encryption both for the transfer to the box, and encrypted on disk. The data on disk should not be readable by anyone but me (ie the other user(s) of the box should not be able to read it, at least not without a big effort). So, I'm wondering what the best solution might be.. Tar'balling all my stuff and encrypt it with GPG or something and just dump it there with NFS would be the easiest solution, but maybe not the best. I've been thinking about running a GELI image on my box, and store that on the NAS over NFS.. would that be doable/secure/stable? Another idea would be to go with some regular 1U box running some FBSD, doing scp to the box and geli local on the box but that would require me to have the encryption keys on that box (which would be shared so thus no good idea). Any other ideas? Being able to rsync to the backup storage instead of just sending big encrypted tarballs would be very nice (and I guess that would be possible with geli version) Maybe not the perfect list for this, but it is somewhat freebsd specific and I'm sure some other ppl on the list have had simliar situations :) -- Johan Ström Stromnet [EMAIL PROTECTED] http://www.stromnet.se/ Hello, As of the encryption on the transfer I use security/sfs to mount remote directory for backup and then rsync in the local. I thought SFS looked pretty neat until I saw this in the documentation: Finally, you must export all the local-directorys in your sfsrwsd_config to localhost via NFS version 3. See my mail to Johan, as it documents a known "issue" with nfsd/mountd/portmap on FreeBSD (re: binding to INADDR_ANY and using dynamically-allocated port numbers). This circles back to my "if you HAVE to use NFS, do so on a dedicated network which has no public access" statement. SFS indeed looked very nice, but didnt provide me with the encrypted- on-disk feature I need as I understand?. As mentioned earlier I don't want to store crypto keys on the backup machine itself, otherwise I could have used geli or something. Thanks -- Johan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup solution suggestions
On Jan 15, 2008, at 15:03 , Ronald Klop wrote: This sounds like a problem for 'tarsnap'. It's from the same author as portsnap. http://www.daemonology.net/blog/2006-09-13-encrypted-backup.html http://www.daemonology.net/blog/2007-08-29-tarsnap-update.html http://www.tarsnap.com/ I never used it so I don't know more about it than you can find in these url's. Indeed, sounds like that could be what I'm looking for. But however nothing public yet, only "private" beta.. And from the sound of it, only a hosted service? Nothing that one will be able to put up themself. http://news.ycombinator.com/item?id=81221 And a remotely hosted service I can have at home, but it's the bandwith of the internet link that limits me.. -- Johan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: G965 patch for 6.3-Beta
Hi, The patch is based on the outdated FreeBSD 7-current, so we should look at the latest one. Fortunately I have 8 G33 machines (Intel DG33BU M/B) but they are going to be used for long long experiments with FreeBSD 7.0 or Solaris very soon. If I have a chance, I'll try to check with G33. Sorry for no immediate help. -- Hiroshi Nishida [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Very bad performances with wpi and 7.0-RC1
Hello, I use FreeBSD 7.0-RC1 with my laptop (Asustek A6000 Series). Performances with wpi are very very bad: in my LAN, I download a file at 4 k/s. In Internet, I would believe I use a 56 k connection :-) In this laptop, I have a NIC (chipset re), and I don't have any problem with. The connection is very very stable. The problem is juste with wpi and my Wireless NIC. I test OpenBSD-current, and I didn't have any problem with wpi. The problem is juste with FreeBSD 7.0-RC1. I have any firewalls, nothing. All is perfect with my NIC re. I test with GENERIC, and I build my own kernel (with wpi support build into kernel). The problem is the same. See more informations here: numenor# cat /boot/loader.conf nvidia_load="YES" wpifw_load="YES" legal.intel_wpi.license_ack=1 numenor# cat /etc/rc.conf defaultrouter="192.168.1.249" hostname="numenor." ifconfig_wpi0="inet 192.168.1.4 ssid Nicoelro_Wifi" numenor# ifconfig wpi0 wpi0: flags=8843 metric 0 mtu 1500 ether 00:13:02:dd:05:5f inet 192.168.1.4 netmask 0xff00 broadcast 192.168.1.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: associated ssid Nicoelro_Wifi channel 10 (2457 Mhz 11g) bssid 00:0f:b5:b9:9f:cc authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 protmode CTS Sometimes, I see this message: wpi0: discard frame w/o packet header numenor# sysctl -a | grep wpi net.wlan.0.%parent: wpi0 debug.wpi: 0 dev.wpi.0.%desc: Intel(R) PRO/Wireless 3945ABG dev.wpi.0.%driver: wpi dev.wpi.0.%location: slot=0 function=0 handle=\_SB_.PCI0.P0P7.WLAN dev.wpi.0.%pnpinfo: vendor=0x8086 device=0x4222 subvendor=0x8086 subdevice=0x1001 class=0x028000 dev.wpi.0.%parent: pci3 numenor# dmesg *Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RC1 #1: Mon Jan 14 18:12:58 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NUMENOR Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Genuine Intel(R) CPU T2300 @ 1.66GHz (1662.52-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6e8 Stepping = 8 Features=0xbfe9fbff Features2=0xc189 AMD Features=0x10 Cores per package: 2 real memory = 1073545216 (1023 MB) avail memory = 1032773632 (984 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 hptrr: HPT RocketRAID controller driver v1.1 (Jan 14 2008 18:12:38) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 6130a2c06000613 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 ACPI Warning (tbutils-0243): Incorrect checksum in table [SSDT] - D6, should be 9C [20070320] est1: on cpu1 p4tcc1: on cpu1 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 nvidia0: mem 0xfd00-0xfdff,0xc000-0xcfff,0xfc00-0xfcff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] pcm0: mem 0xfebfc000-0xfebf irq 21 at device 27.0 on pci0 pcm0: [ITHREAD] pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 re0: port 0xc800-0xc8ff mem 0xfe0ff000-0xfe0f irq 16 at device 0.0 on pci2 re0: Using 2 MSI messages miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:18:f3:5b:f6:31 re0: [FILTER] re0: [FILTER] pcib3: irq 19 at device 28.3 on pci0 pci3: on pcib3 wpi0: mem 0xfe1ff000-0xfe1f irq 19 at device 0.0 on pci3 bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_alloc failed to align memory properly. bus_dmamem_
Re: What current Dell Systems are supported/work
On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup solution suggestions
This sounds like a problem for 'tarsnap'. It's from the same author as portsnap. http://www.daemonology.net/blog/2006-09-13-encrypted-backup.html http://www.daemonology.net/blog/2007-08-29-tarsnap-update.html http://www.tarsnap.com/ I never used it so I don't know more about it than you can find in these url's. Ronald. On Tue, 15 Jan 2008 10:52:56 +0100, Johan Ström <[EMAIL PROTECTED]> wrote: Hello I'm looking to invest in some new hardware for backup. probably some kind of NAS (a 4-disk 1U NAS or something in that size). The thing is that I won't be the only one with access to this box, thus I would like to secure my data. What I would like is encryption both for the transfer to the box, and encrypted on disk. The data on disk should not be readable by anyone but me (ie the other user(s) of the box should not be able to read it, at least not without a big effort). So, I'm wondering what the best solution might be.. Tar'balling all my stuff and encrypt it with GPG or something and just dump it there with NFS would be the easiest solution, but maybe not the best. I've been thinking about running a GELI image on my box, and store that on the NAS over NFS.. would that be doable/secure/stable? Another idea would be to go with some regular 1U box running some FBSD, doing scp to the box and geli local on the box but that would require me to have the encryption keys on that box (which would be shared so thus no good idea). Any other ideas? Being able to rsync to the backup storage instead of just sending big encrypted tarballs would be very nice (and I guess that would be possible with geli version) Maybe not the perfect list for this, but it is somewhat freebsd specific and I'm sure some other ppl on the list have had simliar situations :) -- Johan Ström Stromnet [EMAIL PROTECTED] http://www.stromnet.se/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup solution suggestions
First of all, thanks for your extensive answer! On Jan 15, 2008, at 13:34 , Jeremy Chadwick wrote: On Tue, Jan 15, 2008 at 10:52:56AM +0100, Johan Ström wrote: I'm looking to invest in some new hardware for backup. probably some kind of NAS (a 4-disk 1U NAS or something in that size). The thing is that I won't be the only one with access to this box, thus I would like to secure my data. In my experience, your best bet when it comes to backups like what you want (1U box with 4 disks, or a 2U box with 8 or more) is to simply buy a server with the specifications you want, and run FreeBSD on it. I cannot recommend commercial products for something of this "scale" (e.g. small/medium). I could list off all the reasons why [as a small hosting provider] I avoid proprietary backup solutions, but the list is quite long. The two main reasons: 1) Proprietary solutions often use proprietary hardware. How do you know what's inside of that mystery box? What if it uses a SATA controller you know has h/w-level bugs in it? What if something in the device fails; are you going to be charged an arm and a leg for a replacement part? Does it even HAVE user-servicable parts? etc... I feel much more confident relying on hardware that I'm familiar with, e.g. I know what motherboard is in the server I buy or build, I know who makes it, I know if it's compatible with FreeBSD or Linux, I know the SATA controller works and isn't flaky, I know the SATA backplane actually works properly and supports hot-swapping, and I know if I need replacement parts I can get them promptly. Also, if the h/w I buy turns out to have compatibility problems or performance issues, I can always return it, get my money back, and try other h/w; with a proprietary solution you're "stuck with it", and if something's broken about it which the vendor can't/won't fix, you're screwed. 2) Proprietary solutions also means proprietary software. This is pretty much guaranteed regardless of what h/w is used. What if the volume manager used for your array has a bug and your data is corrupt? You have no way of really "knowing" this until it's too late, and you only have one person to turn to: the vendor. All good points there, cannot argue against that. Certainly something to think about before doing any purchases. The only thing against that right now is size (we've got "cheap" access to a rack with limited depth), havent realy found any good 1U chassis that arent to deep. Admittedly I haven't spent veery much time looking yet but.. :) I prefer to have freedom of choice when it comes to backup methods. "Hmm, dump/restore isn't working out very well, so maybe I'll try ZFS, or bacula, or tar over NFS, or rsync, or...". What I would like is encryption both for the transfer to the box, and encrypted on disk. The data on disk should not be readable by anyone but me (ie the other user(s) of the box should not be able to read it, at least not without a big effort). I'm curious what the reason is for on-disk encryption? Is it necessary for something *only you* will have access to? What's the concern here? I think I wrote that I *wont* be the only one with access to the box. Sorry if that wasn't clear. It will be shared with a friend (or rather his company) of mine. I do trust him, but to keep some level of security I don't want him (or rather, someone with access to his box) to be able to read my files (and the other way arround for his files). So, I'm wondering what the best solution might be.. Tar'balling all my stuff and encrypt it with GPG or something and just dump it there with NFS would be the easiest solution, but maybe not the best. I've been thinking about running a GELI image on my box, and store that on the NAS over NFS.. would that be doable/secure/stable? I would recommend avoiding NFS unless the machine you're running nfsd/mountd/portmap on has no direct way to talk to the Internet. It's impossible to get NFS-related daemons to bind solely to one IP/ interface on FreeBSD, which imposes a security risk. If the machine is behind NAT, you're very likely safe (unless the public has some way of accessing another machine on that NAT network). Thus, if you choose to go the NFS route, have it on a segregated network. The box will be on a separate LAN only accessible by our two boxes. No internet connectivity. But the client boxes ofcourse have internet connectivty (but that would only be NFS clients, not servers). That said -- what we use in our production environment is dump/restore over SSH over a dedicated LAN. I wrote a series of scripts that do this, using SSH keys for the SSH portion. Incrementals are done 6 days a week, with fulls done once a week. I use a similar scheme now, using BackupPC. However that is to my box at home which is not a very good solution due to bandwidth limitations (5MBit only).. The first copy takes ages, the i
Re: Backup solution suggestions
On Tue, Jan 15, 2008 at 12:40:02PM +0100, Vladimir Botka wrote: > Dne Tue, 15 Jan 2008 10:52:56 +0100 > Johan Ström <[EMAIL PROTECTED]> napsal(a): > > > Hello > > > > I'm looking to invest in some new hardware for backup. probably some > > kind of NAS (a 4-disk 1U NAS or something in that size). The thing > > is that I won't be the only one with access to this box, thus I > > would like to secure my data. > > What I would like is encryption both for the transfer to the box, > > and encrypted on disk. The data on disk should not be readable by > > anyone but me (ie the other user(s) of the box should not be able to > > read it, at least not without a big effort). > > > > So, I'm wondering what the best solution might be.. Tar'balling all > > my stuff and encrypt it with GPG or something and just dump it there > > with NFS would be the easiest solution, but maybe not the best. I've > > been thinking about running a GELI image on my box, and store that > > on the NAS over NFS.. would that be doable/secure/stable? > > Another idea would be to go with some regular 1U box running some > > FBSD, doing scp to the box and geli local on the box but that would > > require me to have the encryption keys on that box (which would be > > shared so thus no good idea). > > > > Any other ideas? Being able to rsync to the backup storage instead > > of just sending big encrypted tarballs would be very nice (and I > > guess that would be possible with geli version) > > > > Maybe not the perfect list for this, but it is somewhat freebsd > > specific and I'm sure some other ppl on the list have had simliar > > situations :) > > > > -- > > Johan Ström > > Stromnet > > [EMAIL PROTECTED] > > http://www.stromnet.se/ > > > > Hello, > > As of the encryption on the transfer I use security/sfs to mount remote > directory for backup and then rsync in the local. I thought SFS looked pretty neat until I saw this in the documentation: Finally, you must export all the local-directorys in your sfsrwsd_config to localhost via NFS version 3. See my mail to Johan, as it documents a known "issue" with nfsd/mountd/portmap on FreeBSD (re: binding to INADDR_ANY and using dynamically-allocated port numbers). This circles back to my "if you HAVE to use NFS, do so on a dedicated network which has no public access" statement. -- | 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: Backup solution suggestions
On Tue, Jan 15, 2008 at 10:52:56AM +0100, Johan Ström wrote: > I'm looking to invest in some new hardware for backup. probably some kind > of NAS (a 4-disk 1U NAS or something in that size). The thing is that I > won't be the only one with access to this box, thus I would like to secure > my data. In my experience, your best bet when it comes to backups like what you want (1U box with 4 disks, or a 2U box with 8 or more) is to simply buy a server with the specifications you want, and run FreeBSD on it. I cannot recommend commercial products for something of this "scale" (e.g. small/medium). I could list off all the reasons why [as a small hosting provider] I avoid proprietary backup solutions, but the list is quite long. The two main reasons: 1) Proprietary solutions often use proprietary hardware. How do you know what's inside of that mystery box? What if it uses a SATA controller you know has h/w-level bugs in it? What if something in the device fails; are you going to be charged an arm and a leg for a replacement part? Does it even HAVE user-servicable parts? etc... I feel much more confident relying on hardware that I'm familiar with, e.g. I know what motherboard is in the server I buy or build, I know who makes it, I know if it's compatible with FreeBSD or Linux, I know the SATA controller works and isn't flaky, I know the SATA backplane actually works properly and supports hot-swapping, and I know if I need replacement parts I can get them promptly. Also, if the h/w I buy turns out to have compatibility problems or performance issues, I can always return it, get my money back, and try other h/w; with a proprietary solution you're "stuck with it", and if something's broken about it which the vendor can't/won't fix, you're screwed. 2) Proprietary solutions also means proprietary software. This is pretty much guaranteed regardless of what h/w is used. What if the volume manager used for your array has a bug and your data is corrupt? You have no way of really "knowing" this until it's too late, and you only have one person to turn to: the vendor. I prefer to have freedom of choice when it comes to backup methods. "Hmm, dump/restore isn't working out very well, so maybe I'll try ZFS, or bacula, or tar over NFS, or rsync, or...". Here's a little story in regards to "enterprise-ready" solutions, in case you're considering a piece of hardware intended for backups that was engineered by a vendor/manufacturer and is intended for corporations or very large businesses: At my workplace we have 12 very expensive TDM-to-VoIP converters used by the core of our telco platform. After a few weeks of the first couple being installed in our production environment, we began seeing what appeared to be large amounts of packet loss coming from the actual Ethernet interfaces on the VoIP translator cards. We spent ~3 months working with the manufacturer/vendor to try and find out why this was happening, and more importantly, was the problem affecting actual VoIP traffic in any way (garbled audio, jitter, etc.)? The vendor focused on two things: possible configuration problem, and faulty hardware. Replacing the translator cards with new ones (newer firmware, etc.) did not fix the problem. Our configuration was also fine. A few months later, we finally got an answer from someone who was very low-level (a hardware engineer): the Broadcom Ethernet ICs used in the translator cards were known to drop packets under certain circumstances. The vendor claimed to have communicated with Broadcom over the problem, but Broadcom had was not very forthcoming with details of the issue, and pretty much stonewalled them in the end (that's how I interpret it, anyways). Thus, our vendor didn't know what to tell us, because "their hands were tied" (yet they engineered the hardware. Hmm...) The recommended solution? "Yeah, um, so you should buy our new translator cards! They use a different vendors' IC which don't have that problem!" > What I would like is encryption both for the transfer to the box, and > encrypted on disk. The data on disk should not be readable by anyone but me > (ie the other user(s) of the box should not be able to read it, at least > not without a big effort). I'm curious what the reason is for on-disk encryption? Is it necessary for something *only you* will have access to? What's the concern here? > So, I'm wondering what the best solution might be.. Tar'balling all my > stuff and encrypt it with GPG or something and just dump it there with NFS > would be the easiest solution, but maybe not the best. I've been thinking > about running a GELI image on my box, and store that on the NAS over NFS.. > would that be doable/secure/stable? I would recommend avoiding NFS unless the machine you're running nfsd/mountd/portmap on has no direct way to talk to the Internet. It's impossible to get NFS-related daemons to bind solely to one IP/interface on FreeBSD, which imposes a security risk.
Re: Backup solution suggestions
Dne Tue, 15 Jan 2008 10:52:56 +0100 Johan Ström <[EMAIL PROTECTED]> napsal(a): > Hello > > I'm looking to invest in some new hardware for backup. probably some > kind of NAS (a 4-disk 1U NAS or something in that size). The thing > is that I won't be the only one with access to this box, thus I > would like to secure my data. > What I would like is encryption both for the transfer to the box, > and encrypted on disk. The data on disk should not be readable by > anyone but me (ie the other user(s) of the box should not be able to > read it, at least not without a big effort). > > So, I'm wondering what the best solution might be.. Tar'balling all > my stuff and encrypt it with GPG or something and just dump it there > with NFS would be the easiest solution, but maybe not the best. I've > been thinking about running a GELI image on my box, and store that > on the NAS over NFS.. would that be doable/secure/stable? > Another idea would be to go with some regular 1U box running some > FBSD, doing scp to the box and geli local on the box but that would > require me to have the encryption keys on that box (which would be > shared so thus no good idea). > > Any other ideas? Being able to rsync to the backup storage instead > of just sending big encrypted tarballs would be very nice (and I > guess that would be possible with geli version) > > Maybe not the perfect list for this, but it is somewhat freebsd > specific and I'm sure some other ppl on the list have had simliar > situations :) > > -- > Johan Ström > Stromnet > [EMAIL PROTECTED] > http://www.stromnet.se/ > Hello, As of the encryption on the transfer I use security/sfs to mount remote directory for backup and then rsync in the local. -vlado Vladimir Botka ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Backup solution suggestions
Hello I'm looking to invest in some new hardware for backup. probably some kind of NAS (a 4-disk 1U NAS or something in that size). The thing is that I won't be the only one with access to this box, thus I would like to secure my data. What I would like is encryption both for the transfer to the box, and encrypted on disk. The data on disk should not be readable by anyone but me (ie the other user(s) of the box should not be able to read it, at least not without a big effort). So, I'm wondering what the best solution might be.. Tar'balling all my stuff and encrypt it with GPG or something and just dump it there with NFS would be the easiest solution, but maybe not the best. I've been thinking about running a GELI image on my box, and store that on the NAS over NFS.. would that be doable/secure/stable? Another idea would be to go with some regular 1U box running some FBSD, doing scp to the box and geli local on the box but that would require me to have the encryption keys on that box (which would be shared so thus no good idea). Any other ideas? Being able to rsync to the backup storage instead of just sending big encrypted tarballs would be very nice (and I guess that would be possible with geli version) Maybe not the perfect list for this, but it is somewhat freebsd specific and I'm sure some other ppl on the list have had simliar situations :) -- Johan Ström Stromnet [EMAIL PROTECTED] http://www.stromnet.se/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Swapping caused by very large (regular) file size
Thomas Hurst wrote: * John Baldwin ([EMAIL PROTECTED]) wrote: We have noticed an issue at work but only on faster controllers (e.g. certain mfi(4) drive configurations) when doing I/O to a single file like the dd command mentioned causes the buffer cache to fill up. The problem being that we can't lock the vm object to recycle pages when we hit the limit that is supposed to prevent this because all the pages in the cache are for the file (vm object) we are working on. Stephan (ups@) says this is fixed in 7. Excellent. I've been seeing this behavior for a long time, mostly on backup runs (RAID-1 amr SATA -> 1 disk Marvell ata). It's pretty odd seeing a system with 8G of memory, 60% of which is just cache, swap out half a dozen things for no apparant reason. And to think, people on FreeNode ##freebsd just insisted I had a misconfigured system ;) My other IO related issue with 6 is IO to independent amr arrays blocking each other; e.g. daily run's find over amrd0 will invariably cause reads from amrd1 and amrd2 to freeze for seconds at a time (pr 114438). I'll be very interested to see if 7 fixes that. Sounds like it might be due to Giant contention, which I think is indeed fixed in 7. Can you try it? Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/usr/lib/compat and updates
Hi all, I've been doing a number of 4.11 -> 5.5 -> 6.2 upgrades. All of them I've done have gone very well. One that was handled by someone else following my step-by-step directions ended up missing some items from /usr/lib/compat and all the timestamps on the files in that directory are quite old (2002 and 2005). As best I can tell "COMPAT4X" was set in /etc/make.conf on the machine in question. Can anyone help me understand where in the update process the compat libs are updated and which files correspond to which release? Thanks, Charles ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why does firefox keep locking up on me?
Hello Bob, On 15/01/2008, Bob Vaughan <[EMAIL PROTECTED]> wrote: > I've been having a problem on one particular machine with Firefox locking up > on me, requiring a hard kill to get rid of it. > > The problem is thus: Firefox starts normally, but as soon as I go to a > site that requires authentication, or any other form of user input, > It will freeze as soon as I start entering my userid. [...] > > Any ideas where to start looking? Since you've done nearly everything that could affect a binary working properly, I think we can rule out a problem with the base system, X or the browser itself. I guess the problem might be related to your ~/.mozilla directory. I noticed that a large variety of problems might be related to something been broken inside it. This might be an extension that might be incompatible and that isn't installed on any of the other machines. I'd recommend you to shut down firefox, open a terminal window and rename the directory to something different. Please note that it contains all settings you've made in *any* mozilla product (sunbird, thunderbird). Start firefox again and give it a try. HTH Christian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
