Re: powerd broken
Alexander Motin wrote: > Dominic Fandrey wrote: >> I can rule out drm0 as the cause, because uhci0 is the only common >> presence in all occurrences of this problem. > > You have other examples? If you mean "irq16: hdac0 uhci+" string, then > "+" there means "and some other devices", which in this case is probably > drm0. > > There were some drm related commits last time and there are also some > IRQ related problems were reported/patched in CURRENT recently. So I > would not ignore this possibility without additional testing. > Is there anything I can do, apart from turning off drm? This is really annoying (well, it eats a whole core while I'm compiling and it keeps the fans going, when the machine should be idle). Is there somehow I can generate useful information? Someone to send a kernel dump to? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_7/i386: ZFS constant panic on file system writes
On Thu, Apr 2, 2009 at 22:32, Dmitry Morozovsky wrote: > Pawel, > > could you please help me a bit with *very* unpleasant situation: one of my > servers with very large ZFS reboots on most write requests to one (largest, > which effectively prohibits recreating) ZFS file system with > > panic: avl_find() succeeded inside avl_add() > > (kgdb) bt > #0 doadump () at pcpu.h:196 > #1 0xc0533227 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 > #2 0xc0533535 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:574 > #3 0xc0836a20 in avl_add (tree=Variable "tree" is not available. > ) at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/common/avl/avl.c:635 > #4 0xc088c39f in zap_lockdir (os=0xc555a590, obj=6108, tx=0x0, lti=RW_READER, > fatreader=1, zapp=0xfc6907f8) > at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap_micro.c:231 > #5 0xc088cc0f in zap_lookup (os=0xc555a590, zapobj=6108, name=0xfc6908bc > "daily.20080701.gz", integer_size=8, num_integers=1, buf=0xfc69083c) > at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap_micro.c:509 > #6 0xc089e25d in zfs_dirent_lock (dlpp=0xfc690878, dzp=0xc709f570, > name=0xfc6908bc "daily.20080701.gz", zpp=0xfc690874, flag=Variable "flag" is > not available. > ) > at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_dir.c:173 > #7 0xc089e43e in zfs_dirlook (dzp=0xc709f570, name=0xfc6908bc > "daily.20080701.gz", vpp=0xfc690b5c) > at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_dir.c:271 > #8 0xc08a8653 in zfs_freebsd_lookup (ap=0xfc690a00) > at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1080 > #9 0xc06dab42 in VOP_CACHEDLOOKUP_APV (vop=0xc08ba7e0, a=0xfc690a00) at > vnode_if.c:153 > #10 0xc05a402c in vfs_cache_lookup (ap=0xfc690a84) at vnode_if.h:83 > #11 0xc06dc816 in VOP_LOOKUP_APV (vop=0xc08ba7e0, a=0xfc690a84) at > vnode_if.c:99 > #12 0xc05aa681 in lookup (ndp=0xfc690b48) at vnode_if.h:57 > #13 0xc05ab308 in namei (ndp=0xfc690b48) at /usr/src/sys/kern/vfs_lookup.c:215 > #14 0xc05ba07f in kern_lstat (td=0xc5186af0, path=0xbfbfd088 0xbfbfd088 out of bounds>, pathseg=UIO_USERSPACE, sbp=0xfc690c18) > at /usr/src/sys/kern/vfs_syscalls.c:2184 > #15 0xc05ba22f in lstat (td=0xc5186af0, uap=0xfc690cfc) at > /usr/src/sys/kern/vfs_syscalls.c:2167 > #16 0xc06d0288 in syscall (frame=0xfc690d38) at > /usr/src/sys/i386/i386/trap.c:1090 > #17 0xc06b5bc0 in Xint0x80_syscall () at > /usr/src/sys/i386/i386/exception.s:255 > #18 0x0033 in ?? () > Previous frame inner to this frame (corrupt stack?) > > this is fresh RELENG_7/i386 with (I suppose, unrelated) patch to ata from mav@ > > Thanks in advance. Hi Dmitry, I think the line numbers are misleading, see: http://fxr.watson.org/fxr/source/cddl/contrib/opensolaris/uts/common/fs/zfs/zap_micro.c?v=FREEBSD7;im=bigexcerpts#L262 Could you build a kernel with -O1 or -O0 perhaps that will help. I have no other clue about your situation except maybe try 8-current? - Marius ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: powerd broken
Dominic Fandrey wrote: > Alexander Motin wrote: >> Dominic Fandrey wrote: >>> I can rule out drm0 as the cause, because uhci0 is the only common >>> presence in all occurrences of this problem. >> You have other examples? If you mean "irq16: hdac0 uhci+" string, then >> "+" there means "and some other devices", which in this case is probably >> drm0. >> >> There were some drm related commits last time and there are also some >> IRQ related problems were reported/patched in CURRENT recently. So I >> would not ignore this possibility without additional testing. > > Is there anything I can do, apart from turning off drm? This is really > annoying (well, it eats a whole core while I'm compiling and it keeps > the fans going, when the machine should be idle). As first, try to disable DRI/DRM just to investigate the problem better. If it is related, try to ask Robert Noland , he is our DRI/DRM man. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Check out my photos on Facebook
I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile. -- hello! -- Thanks, Vahid To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=1485341899&k=3VL2Z65234ZM5DLAYDVYU3&r sta...@freebsd.org was invited to join Facebook by Vahid Chitsazzadeh. If you do not wish to receive this type of email from Facebook in the future, please click on the link below to unsubscribe. http://www.facebook.com/o.php?k=936fd1&u=1681869548&mid=3fe309G643f4aecG0G8 Facebook's offices are located at 156 University Ave., Palo Alto, CA 94301. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELENG_7 ata panic on atacontrol attach
Dmitry Morozovsky wrote: > On Thu, 2 Apr 2009, Alexander Motin wrote: > AM> Dmitry Morozovsky wrote: > AM> > On Thu, 2 Apr 2009, Alexander Motin wrote: > AM> > > AM> > AM> > ata7: reset tp2 stat0=50 stat1=00 devices=0x1^M > AM> > AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M > AM> > AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M > AM> > AM> > ad: ad14 already exists; skipping it^M > AM> > AM> > ad: ad14 already exists; skipping it^M > AM> > AM> > ^M > AM> > AM> > ^M > AM> > AM> > Fatal trap 12: page fault while in kernel mode^M > AM> > AM> AM> It looks alike to crash I have already fixed on CURRENT: > AM> > AM> http://svn.freebsd.org/changeset/base/188464 > AM> > > AM> > Seems to be. Would you please ask re@ for MFC approval? > AM> > AM> This is not actually a fix for original problem, but it may help to avoid > AM> system crash. Can you confirm that it helps you, as I haven't tested it on > AM> STABLE yet, I am doing it now. If it helps, I will ask r...@. > > Well, partially. Machine survived a dozed of detach-remove-insert-attach > cycles (which it definitly could not before). Merged. > However, it it still paniced on hot-remove-insert (could not dump): > Some other hot reinserts finished successfully. It is probably an ATA code problem. I have reworked that part in HEAD. > Well, at least now it is significally better that before, if one does not > forget to detach ata channel before reinserting the device. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.2-BETA1 Available
On Fri, 2009-04-03 at 00:43 -0400, Ken Smith wrote: > The first of the test builds for the FreeBSD 7.2-RELEASE cycle is now > available. Well, sort of. Sorry, it's been a couple months since I uploaded something bigger than 2Gb (the dvd images) and I forgot the mechanism that some mirrors use to sync with the master site chokes on files over 2Gb. So the mirrors that use that mechanism to sync won't have it for another couple of hours (I just gzip-ed the dvd images now). If the place you normally get it from doesn't have it at the point you want to download it I know ftp10.us.freebsd.org has got it. By tomorrow all the mirrors should have it. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: RELENG_7 ata panic on atacontrol attach
On Fri, 3 Apr 2009, Alexander Motin wrote: AM> > AM> This is not actually a fix for original problem, but it may help to avoid AM> > AM> system crash. Can you confirm that it helps you, as I haven't tested it on AM> > AM> STABLE yet, I am doing it now. If it helps, I will ask r...@. AM> > AM> > Well, partially. Machine survived a dozed of detach-remove-insert-attach AM> > cycles (which it definitly could not before). AM> AM> Merged. Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Le nettoyage de hottes discount
This is the text that will appear if the recipient cannot view HTML messages. Replace this with a plain text version of your message. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Check out my photos on Facebook
On Fri, 2009-04-03 at 03:32 -0700, Vahid Chitsazzadeh wrote: > I set up a Facebook profile where I can post my pictures, videos and events > and I want to add you as a friend so you can see it. First, you need to join > Facebook! Once you join, you can also create your own profile. On behalf of FreeBSD-STABLE, "not on your fucking life". :) -- Horst signature.asc Description: This is a digitally signed message part
Re: Check out my photos on Facebook
hehehe i got yelled at so much for facebook sending mail to mailing lists because theyre in my address book and I imported my address book to facebook. -Adele (sent from my gphone!) On Apr 3, 2009 9:00 AM, "Horst Günther Burkhardt III" wrote: On Fri, 2009-04-03 at 03:32 -0700, Vahid Chitsazzadeh wrote: > I set up a Facebook profile where I c... On behalf of FreeBSD-STABLE, "not on your fucking life". :) -- Horst ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: powerd broken
On Fri, 2009-04-03 at 11:43 +0200, Dominic Fandrey wrote: > Alexander Motin wrote: > > Dominic Fandrey wrote: > >> I can rule out drm0 as the cause, because uhci0 is the only common > >> presence in all occurrences of this problem. > > > > You have other examples? If you mean "irq16: hdac0 uhci+" string, then > > "+" there means "and some other devices", which in this case is probably > > drm0. > > > > There were some drm related commits last time and there are also some > > IRQ related problems were reported/patched in CURRENT recently. So I > > would not ignore this possibility without additional testing. > > > > Is there anything I can do, apart from turning off drm? This is really > annoying (well, it eats a whole core while I'm compiling and it keeps > the fans going, when the machine should be idle). > > Is there somehow I can generate useful information? Someone to send a > kernel dump to? Use a radeon? ;( I've been working on the Intel vblank / irq issues. Every time I commit something thinking that I have it resolved, it isn't. So I'm waiting on hardware to arrive that will let me test this all more thoroughly. I do have a patch that I think fixes most of the issues on Intel, but the ddx driver is still doing some silly things that cause issues in some cases. I *think* the only outstanding issue I have with Intel is if something is rendering (synced to vblank or not) when the display goes into dpms sleep, there isn't anything to block that app, so it renders as hard as it can even though it isn't being displayed. In reality, this probably isn't a huge issue, but running gears while the display is asleep keeps the cpu at 100%, which isn't ideal. Normal apps that aren't trying to draw as fast as they can, shouldn't cause an issue. The other issue with my current patches is that I had to change around a fair amount of infrastructure code to try and fix Intel's brain damage, so I have to finish fixing the rest of the drivers so they don't break. I have Intel and radeon fixed, I just have to hit the more obscure drivers. robert. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: FreeBSD 7.2-BETA1 Available
At 12:43 AM 4/3/2009, Ken Smith wrote: The first of the test builds for the FreeBSD 7.2-RELEASE cycle is now available. Testing of two recent changes to the system would be Just tried out the i386 DVD and all worked great on a shiny new X58 MB from supermicro! And as a bonus, the watchdog actually works! However there are some acpi errors as well as Enhanced SpeedStep doesnt seem to work either. Note, the BIOS version is 1.0 (nothing else available) so it might be the issue. But even without the power saving, the server idles at around 100Watts!! And doing several cat /dev/urandom | md5 pushes it upto just 160W. i7# dmesg Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-BETA1 #0: Tue Mar 31 21:01:09 UTC 2009 r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (2660.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a4 Stepping = 4 Features=0xbfebfbff Features2=0x98e3bd AMD Features=0x2810 AMD Features2=0x1 Cores per package: 8 Logical CPUs per core: 2 real memory = 3212312576 (3063 MB) avail memory = 3137855488 (2992 MB) ACPI APIC Table: <030609 APIC0930> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 em0: port 0xdc00-0xdc1f mem 0xfaee-0xfaef,0xfaedc000-0xfaed irq 16 at device 0.0 on pci1 em0: Using MSIX interrupts em0: [ITHREAD] em0: [ITHREAD] em0: [ITHREAD] em0: Ethernet address: 00:30:48:d7:c1:6e pcib2: at device 2.0 on pci0 pci2: on pcib2 em1: port 0xec00-0xec1f mem 0xfafe-0xfaff,0xfafdc000-0xfafd irq 16 at device 0.0 on pci2 em1: Using MSIX interrupts em1: [ITHREAD] em1: [ITHREAD] em1: [ITHREAD] em1: Ethernet address: 00:30:48:d7:c1:6f pcib3: at device 3.0 on pci0 pci3: on pcib3 pcib4: at device 7.0 on pci0 pci4: on pcib4 pcib5: at device 9.0 on pci0 pci5: on pcib5 pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) pci0: at device 20.0 (no driver attached) pci0: at device 20.1 (no driver attached) pci0: at device 20.2 (no driver attached) pci0: at device 20.3 (no driver attached) pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) pci0: at device 22.2 (no driver attached) pci0: at device 22.3 (no driver attached) pci0: at device 22.4 (no driver attached) pci0: at device 22.5 (no driver attached) pci0: at device 22.6 (no driver attached) pci0: at device 22.7 (no driver attached) uhci0: port 0xcc00-0xcc1f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xc880-0xc89f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xc800-0xc81f irq 19 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfadde000-0xfadde3ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered uhci3: port 0xc480-0xc49f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xc400-0xc41f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered uhci5: port 0xc080-0xc09f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered ehci1: mem 0xfaddc000-0xfaddc3ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb7: EHCI version 1.0 usb7: companion controllers, 2 po
Re: Check out my photos on Facebook
This is actually a Conficker signature I believe (a Conficker variant spoofs Facebook mails to socially engineer Facebook users to download itself). On 2009-04-03 09:22:46AM -0700, Paige Thompson wrote: > hehehe i got yelled at so much for facebook sending mail to mailing lists > because theyre in my address book and I imported my address book to > facebook. > > -Adele > (sent from my gphone!) > > On Apr 3, 2009 9:00 AM, "Horst Günther Burkhardt III" > wrote: > > On Fri, 2009-04-03 at 03:32 -0700, Vahid Chitsazzadeh wrote: > I set up a > Facebook profile where I c... > On behalf of FreeBSD-STABLE, "not on your fucking life". > > :) > > -- Horst > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- === Peter C. Lai | Bard College at Simon's Rock Systems Administrator| 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.1-R to RELENG_7 upgrade breaks re nic
On Tuesday 31 March 2009 04:52:54 Steve Wills wrote: > Hi, > > On Feb 25, 2009, at 7:38 PM, Pyun YongHyeon wrote: > > On Tue, Feb 24, 2009 at 08:12:18PM -0500, Steve Wills wrote: > >> Hi, > >> > >> I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after > >> booting, re0 works for only a short time, then gives "re0: PHY read > >> failed" over and over. Does anyone have a suggestion on how to debug? > > > > I need more information for your hardware revision. > > Would you show me dmesg output and revision number of if_re.c? > > For the record, and if anyone else is having this issue, SVN rev > 190587 fixes this. > > Thanks for taking care of it! > > Steve > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" This seems to fix it for me too. At least I've had no messages for the last hour (usually 6-10/hour). Good work, now let's get this in 7.2. -- ian j hart ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.2-BETA1 Available
Hello maillist. Can somewhere see release notes for 7.2 now? Thanks! > At 12:43 AM 4/3/2009, Ken Smith wrote: > >The first of the test builds for the FreeBSD 7.2-RELEASE cycle is now > >available. Testing of two recent changes to the system would be ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 7.0 and Samba 3.3.2 crash over ZFS share
Hi, I have small home file server running FreeBSD 7.0 and 4x500 GBytes ZFS volume. Currently I have Samba 3.0.34 from ports working fine. When I install latest Samba 3.3.2 from ports any access to shares residing on ZFS volume cause panic in samba. Access to UFS share is fine. Any body see same problem? Is it possible to fix? uname -a FreeBSD 7.0-RELEASE-p11 #25: Fri Mar 27 19:13:25 EDT 2009 r...@storage:/usr/obj/usr/src/sys/VIAC7 i386 Thank you, Alex ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Radeon r6/7xx support merged to -STABLE
On Sun, 15 Mar 2009, Robert Noland wrote: I went ahead and merged the Radeon R6/7xx code to -STABLE a while ago. The current xorg drivers will not enable it by default on R600+ chips. You will need to be using xf86-video-ati-6.12.0, xf86-video-radeonhd-devel or possibly even better git master of either. You will need to add the following to the Device section of your xorg.conf to enable it. If you are experiencing issues, commenting these two options out, will prevent Xorg from auto-loading the kernel module. Options "DRI" Options "AccelMethod" "EXA" robert. I know it's been a few weeks, but thanks for this work! I'm using a Radeon HD 4350 and tracking -STABLE. Ever since the big xorg update, my system has been crippled. I like to use startx, restart X, and switch consoles with the function keys. The only driver I could find that didn't completely lock up the system when I did these things was the vesa driver, so I've been using it. Even now vesa throws "failed to set mtrr: Invalid argument" on startup and the screen gets corrupted when I change consoles with the function keys, but it doesn't freeze my system, so I've been using it. Today I finally got around to trying out the radeon changes listed above, and now my system is crippled no more! Plus I have graphics acceleration! Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.0 and Samba 3.3.2 crash over ZFS share
2009/4/4 Alex > Hi, > I have small home file server running FreeBSD 7.0 and 4x500 GBytes ZFS > volume. Currently I have Samba 3.0.34 from ports working fine. When I > install latest Samba 3.3.2 from ports any access to shares residing on ZFS > volume cause panic in samba. Access to UFS share is fine. > Any body see same problem? > Is it possible to fix? > > uname -a > FreeBSD 7.0-RELEASE-p11 #25: Fri Mar 27 19:13:25 EDT 2009 > r...@storage:/usr/obj/usr/src/sys/VIAC7 > i386 > > Thank you, > Alex read this guide... http://wiki.freebsd.org/ZFSTuningGuide Upgrade to FreeBSD 7.2 this branch has some patches that improve ZFS, even that .. is not the same as the branch 8 ;) -- "Linux is for people who hate Windows, BSD is for people who love UNIX" "Social Engineer -> Because there is no patch for human stupidity" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Check out my photos on Facebook
On Fri, 2009-04-03 at 14:41 -0400, Peter C. Lai wrote: > This is actually a Conficker signature I believe (a Conficker variant > spoofs Facebook mails to socially engineer Facebook users to download > itself). I've been reading about Conficker. I honestly didn't think it affected FreeBSD So much for the virus having a classical infection vector :p So has the FreeBSD Security Team done anything about the clear menace of a Windows worm pwning people? ;-) -- Horst signature.asc Description: This is a digitally signed message part
