Re: Mounting / using /dev/ufs/name
On Wed, 2009-01-14 at 19:00 +0100, Václav Haisman wrote: > Hi, > I tried to mount root slice using the device nodes provided in /dev/ufs > directory. It works fine for other slices but not for the root slice. If I > try it I get prompt asking for root slice at boot time. It this not possible > at all or am I doing something wrong? If you don't have geom_label built into the kernel it's a chicken-egg problem. Even if you do, early startup almost certainly doesn't have devfs available yet. -- Frank Mayhar fr...@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* ___ 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"
panic: vm_page_unwire: invalid wire count: 0
This is on a very recent -stable (like, as of just a couple of days
ago). Doing nothing in particular, ZERO_COPY_SOCKETS _not_ specified in
the config. This has happened twice this morning; if it happens again
I'll drop back to my older kernel, built back in May.
I've attached my config and dmesg; the stack trace is here:
#20 0x80273e73 in doadump () at /usr/src/sys/kern/kern_shutdown.c:243
#21 0x80274485 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#22 0x80274b95 in panic (fmt=0xff005488f000 "")
at /usr/src/sys/kern/kern_shutdown.c:565
#23 0x803b4f9b in vm_page_unwire (m=0xff007d61f308,
activate=2118678981) at /usr/src/sys/vm/vm_page.c:1275
#24 0x802cf366 in vfs_vmio_release (bp=0xa18fdf88)
at /usr/src/sys/kern/vfs_bio.c:1489
#25 0x802d2a76 in getnewbuf (slpflag=0, slptimeo=0, size=0,
maxsize=16384) at /usr/src/sys/kern/vfs_bio.c:1798
#26 0x802d2eb4 in getblk (vp=0xff007a7431f0, blkno=0, size=2048,
slpflag=0, slptimeo=0, flags=0) at /usr/src/sys/kern/vfs_bio.c:2516
#27 0x802d496c in breadn (vp=0xff007a7431f0,
blkno=107449315523013, size=0, rablkno=0x0, rabsize=0x0, cnt=0, cred=0x0,
bpp=0x61b97e48a90e) at /usr/src/sys/kern/vfs_bio.c:742
#28 0x802d4dae in bread (vp=0xa, blkno=107449315523013, size=0,
cred=0x61b97e48cf58, bpp=0xff005488f000)
at /usr/src/sys/kern/vfs_bio.c:723
#29 0x8038514c in ffs_blkatoff (vp=0xa, offset=0, res=0x0,
bpp=0xb5ae4690) at /usr/src/sys/ufs/ffs/ffs_subr.c:87
#30 0x80391aa2 in ufs_lookup (ap=0xb5ae4780)
at /usr/src/sys/ufs/ufs/ufs_lookup.c:259
#31 0x80426aba in VOP_CACHEDLOOKUP_APV (vop=0x61b97e48a90e,
a=0x61b97e4879c5) at vnode_if.c:150
#32 0x802d6730 in vfs_cache_lookup (ap=0xa) at vnode_if.h:82
#33 0x804277fe in VOP_LOOKUP_APV (vop=0x805b7000,
a=0xb5ae4880) at vnode_if.c:99
#34 0x802db19b in lookup (ndp=0xb5ae4990) at vnode_if.h:56
#35 0x802dbf4b in namei (ndp=0xb5ae4990)
at /usr/src/sys/kern/vfs_lookup.c:216
#36 0x802eda9b in kern_lstat (td=0xff005488f000,
path=0x61b97e4879c5 ,
pathseg=UIO_USERSPACE, sbp=0xb5ae4af0)
at /usr/src/sys/kern/vfs_syscalls.c:2127
#37 0x802edf5a in lstat (td=0xa, uap=0xb5ae4bc0)
at /usr/src/sys/kern/vfs_syscalls.c:2110
#38 0x803dea02 in syscall (frame=
{tf_rdi = 8049928, tf_rsi = 7588984, tf_rdx = 4407994, tf_rcx = 0, tf_r8
= 410, tf_r9 = 0, tf_rax = 190, tf_rbx = 10, tf_rbp = 7589160, tf_r10 =
6625968, tf_r11 = 8044136, tf_r12 = 140737488350360, tf_r13 = 0, tf_r14 = 0,
tf_r15 = 0, tf_trapno = 22, tf_addr = 0, tf_flags = 7588928, tf_err = 2, tf_rip
= 1084076476, tf_cs = 43, tf_rflags = 582, tf_rsp = 7588944, tf_ss = 35})
at /usr/src/sys/amd64/amd64/trap.c:807
#39 0x803c4d98 in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:287
I'm happy to provide any other information requested.
--
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://www.gpsclock.com/
http://www.exit.com/blog/frank/
http://www.zazzle.com/fmayhar*
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 6.3-PRERELEASE #8: Thu Dec 27 15:34:56 PST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/JILL
ACPI APIC Table:
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Opteron(tm) Processor 248 (2190.72-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0x20f51 Stepping = 1
Features=0x78bfbff
AMD Features=0xe0500800
real memory = 2147418112 (2047 MB)
avail memory = 2063601664 (1968 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 irqs 0-23 on motherboard
ioapic1 irqs 24-27 on motherboard
ioapic2 irqs 28-31 on motherboard
kbd1 at kbdmux0
acpi0: on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_hpet0: iomem 0xfec01000-0xfec013ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
cpu0: on acpi0
acpi_throttle0: on cpu0
cpu1: on acpi0
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
pcib1: at device 6.0 on pci0
pci3: on pcib1
ohci0: mem 0xfeafc000-0xfeafcfff irq 19 at
device 0.0 on pci3
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: on ohci0
usb0: USB revision 1.0
uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr
Repeated crashes in 6.3-PRERELEASE
On Sat, 2007-12-29 at 11:28 -0800, Frank Mayhar wrote: > This is on a very recent -stable (like, as of just a couple of days > ago). Doing nothing in particular, ZERO_COPY_SOCKETS _not_ specified in > the config. This has happened twice this morning; if it happens again > I'll drop back to my older kernel, built back in May. Sigh. In the last three days I've had no fewer than four crashes: This one, another just like it that I didn't get a dump for, a "Fatal trap 12: page fault while in kernel mode" in buf_splay(): #27 0x802e2cb4 in buf_splay (lblkno=0, xflags=2 '\002', root=0x9000) at /usr/src/sys/kern/vfs_subr.c:1339 #28 0x802e2e08 in buf_vlist_remove (bp=0xa1919340) at /usr/src/sys/kern/vfs_subr.c:1371 #29 0x802e4dab in brelvp (bp=0xa1919340) at /usr/src/sys/kern/vfs_subr.c:1502 #30 0x802d28f1 in getnewbuf (slpflag=0, slptimeo=0, size=2, maxsize=16384) at /usr/src/sys/kern/vfs_bio.c:1801 (where bp->b_left is 0x9000) and a "panic: backgroundwritedone: lost buffer." I have a dump for each of the three unique scenarios. At the moment I've dropped back to the older kernel and am keeping my fingers crossed that it will run okay. I'm beginning to suspect hardware, although as two of the three are in the buf code there might be a problem there... If it continues with the older kernel then it is most likely hardware but if not then there's a problem. Has anyone else encountered anything like this in 6.3-PRERELEASE? -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pls.which.way.to.go?
On Thu, 2006-11-09 at 22:20 +0100, Kay Abendroth wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > I would upgrade to 5.5 first. > Then it's up to you, but waiting for 6.3 is probably not a bad idea, > before going further up the hill to 6.x. Please don't top-post. And I disagree. He should go straight to 6.2. If he's going to go to the trouble of upgrading, he should go straight to the latest, most stable release, which is (or shortly will be) 6.2. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Beastie/ how about Mozilla?
Rob wrote: > Hi, just had to comment on a related matter to this. I was talking to > my doctor who is a rabbid christian. The subject came to browsers and I > said "Why don't you try Mozilla?" His reply was "...I am a > Christian..."Was the first time I have known of anyone being > offended by a dragon ion. LOL. > I forgot to tell him that he could change it to something he liked > better. But it gives me shivers of joy just knowing how offensive free > Unix is. Like I said last night, if these idiots want to believe that "satan" lives in their computer, let them. I, for one, am past caring, and life is far too short to try to educate the uneducable. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Beastie/ how about Mozilla?
Jon Noack wrote: > Can we please stay on-topic? Stephan's email seems to have sparked a lot > of Christian-bashing, and I can't see how that is on-topic. Sure, he > probably deserved to be flamed for not finding the "beastie_disable" knob, > but I am offended by some of the emails I've seen. Since when is it > acceptable to ridicule a person's religious beliefs on [EMAIL PROTECTED] When their religious beliefs start affecting my life, I'm not going to remain silent about it. You can call that "ridiculing" or "Christian-bashing" if you want, but as far as I'm concerned it's impossible to ridicule someone who is shaken by a _picture_ of _cartoon_(!) on their computer. I would have been happy to remain silent on this, but it led to Scott's commit that removed the beastie menu and that was going too far. In that sense, yes, it is indeed relevant for stable. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: devfs rules
Ivan Voras wrote: [ Charset ISO-8859-2 unsupported, converting... ] > Is there a canonical way of preserving devfs rules (device permissions > actually) across reboots? >cat /etc/devfs.rules [devfsrules_local=15] add path 'bpf*' mode 0660 add path 'ugen*' mode 0664 add path 'cd*' mode 0664 For example. For some hints, 'man devfs' and /etc/defaults/devfs.rules. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: devfs rules
Frank Mayhar wrote: > Ivan Voras wrote: > [ Charset ISO-8859-2 unsupported, converting... ] > > Is there a canonical way of preserving devfs rules (device permissions > > actually) across reboots? > > >cat /etc/devfs.rules > [devfsrules_local=15] > add path 'bpf*' mode 0660 > add path 'ugen*' mode 0664 > add path 'cd*' mode 0664 > > For example. For some hints, 'man devfs' and /etc/defaults/devfs.rules. Oh, and for this example, don't forget to add devfs_system_ruleset="devfsrules_local" to /etc/rc.conf. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: virtual machines
Scott Lambert wrote: > On Tue, Apr 12, 2005 at 11:05:00AM +0100, Nick Barnes wrote: > > I run FreeBSD as my main desktop, but occasionally have to develop, > > build, or test software on a variety of other x86 operating systems > > (mainly Windows NT 4, Windows XP Pro, and Red Hat Linux). At the > > moment I have a row of mini-towers and a KVM switch. I'd much rather > > run these other machines as virtual machines under FreeBSD. Can > > anyone recommend virtualizing software for FreeBSD? I don't mind > > having to pay, as long as it really works. > > I have not used it, but it claims to support FreeBSD as the host: > > http://www.serenityvirtual.com/ > > I have had a good relationship with the company that is behind the > product. I just haven't used that particular product, especially now > that my primary workstation is a PowerBook. Note that SVISTA doesn't (currently) support 5-stable, or indeed anything past 4.x. There have been questions asked about that in the fora but they have gone unanswered, last I checked. I bought it for 4.x and it worked fine. Better in some ways than qemu, although in other ways it was not as good (qemu seems to have better display support, while SVISTA's networking is vastly better). Since I've gone to 5-stable, though, qemu is my only real alternative. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: truss missing some files or directories
On Wed, 2006-12-20 at 13:08 -0500, Ilya Vishnyakov wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Problem with truss, won't start. Please advise me what to do. > > truss /bin/echo hello truss: truss: cannot open /proc/42520/mem cannot > open /proc/curproc/mem: : No such file or directory > No such file or directory mount /proc In /etc/fstab: proc/proc procfs rw 0 0 -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Forcing a da* numbering scheme.
bOn Tue, 2006-02-21 at 22:59 -0800, Peter Losher wrote: > What's the proper method these days for defining a static naming scheme > for direct access devices (da*)? /boot/device.hints hint.scbus.0.at="ahc0" hint.da.0.at="scbus0" hint.da.0.target="0" hint.da.1.at="scbus0" hint.da.1.target="1" hint.scbus.1.at="ahc1" hint.da.100.at="scbus1" hint.da.100.target="0" hint.da.101.at="scbus1" hint.da.101.target="1" etc. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP support maturity? AMD64x2 or FX-57?
Brandon Fosdick wrote: SMP support in FreeBSD seems to be a perpetually favorite feature to gripe about, but every release seems to say that its getting better. I'm about to build a new server and am trying to determine if I should go with dual procs or just a single. The AMD64x2 is slightly cheaper than the FX-57 so I'm leaning that way, but it would be a rather pointless savings if SMP isn't well supported. So, is SMP in -STABLE ready for primetime? Can it really make use of two processors? Sigh. You know, I've been running with two processors since 4.1 or thereabouts. Sure, the BGL scheme is inefficient as far as the kernel itself is concerned, but for compute-bound user processes it worked just fine. Naturally I avoided 5.0/1/2 for my production boxen, waiting for the complete overhaul of SMP to stabilize, but when I booted 5.3, everything was fine and I haven't looked back. Personally I don't have the first clue what people have found to gripe about. It has been good, it got a _lot_ better in 5.x, and it's continuing to improve. Ports to new processor families are an entirely different kettle of fish and have their own sets of problems, virtually all of which have to do with the new architecture and not with the general SMP support itself. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Serious mouse problems on latest 5-stable.
After I returned from my vacation last week, I set about upgrading my systems to the latest -stable. The short version of the story is that I had to fall back to an earlier version, since the psm driver has been made essentially unusable. I saw a thread about psm-related panics but I didn't see those; rather I saw what appeared to be very serious loss of either characters or interrupts. I suspect the latter since "systat -vmstat" reported a tiny fraction of the number of interrupts that should have been generated by mouse movement (on the order of 5%). This was with a kernel and world as of 9/1. I dropped back to a kernel from 8/10 and all was well. I haven't had a chance to further narrow this down, but I just wanted to check whether this is a known problem...? -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: twa kernel panic under heavy IO
On Mon, 2005-10-24 at 11:13 -0500, Dan Rue wrote:
> At one point, I received the following error message just before the
> machine locked up:
>
> >Oct 12 11:36:13 leopard kernel: initiate_write_filepage: already started
>
> I grepped for that error message in the freebsd kernel source, and found
> it in sys/ufs/ffs/ffs_softdep.c on line 3580. What makes it really
> interesting is the comment above where the error is thrown:
>
> if (pagedep->pd_state & IOSTARTED) {
> /*
> * This can only happen if there is a driver that does not
> * understand chaining. Here biodone will reissue the call
> * to strategy for the incomplete buffers.
> */
> printf("initiate_write_filepage: already started\n");
> return;
> }
Fascinating. This is the same message I saw with the panic I reported
in kern/87861. I'll bet that your wedges and my panics are related
somehow. Unfortunately mine are not fixed in 6.0.
--
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://www.gpsclock.com/
http://www.exit.com/blog/frank/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How is the SRCU42X under 6.x ... ?
On Fri, 2005-11-25 at 19:34 -0400, Marc G. Fournier wrote: > Found that its supported by the amr vs iir driver ... anyone using/used > this with bad experiences? I've been trying to use it. The problem isn't _directly_ related to the driver itself, but I think it's indirectly related. Basically I get a panic in geom sometime after the damage was done. I've been trying to track this down off and on, but haven't had the time to really sit down and find the problem. See http://www.freebsd.org/cgi/query-pr.cgi?pr=87861. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How is the SRCU42X under 6.x ... ?
On Fri, 2005-11-25 at 22:17 -0400, Marc G. Fournier wrote: > On Fri, 25 Nov 2005, Frank Mayhar wrote: > > I've been trying to use it. The problem isn't _directly_ related to the > > driver itself, but I think it's indirectly related. Basically I get a > > panic in geom sometime after the damage was done. I've been trying to > > track this down off and on, but haven't had the time to really sit down > > and find the problem. > Why would you use GEOM instead of letting the card do the work? GEOM is ubiquitous at the lower layers. I'm not using it for RAID, hell, I'm not directly using it at all, but it still comes in below the block layer, as far as I can discern. All I know is that the panic is in g_vfs_(). -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [WARNING] RELENG_6 is broken
On Sat, 2005-11-26 at 13:58 +0300, Gleb Smirnoff wrote: > The ARP problem in RELENG_6 is fixed in revision 1.137.2.6 of if_ether.c. Does this problem cause an arp storm? If so, I ran into it last night and am very glad to see that it's fixed. (It was a new system and I just figured it was due to pilot error or bad hardware.) -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Release schedule for 2006
On Fri, 2005-12-16 at 09:57 +0100, Oliver Fromme wrote: > I've seen reports of a few people who had problems with > 6.0, but personally I didn't have any, and I wouldn't > want to go back. In fact I can't think of a single > reason why I wouldn't upgrade a FreeBSD machine to 6.x. Well, there is _one_ reason. I, too, have (almost) all of my machines up to 6-stable, with the very notable exception of the one that runs asterisk. Unfortunately, last I looked, the zaptel drivers hadn't been ported to 6. I found this out the hard way when I upgraded and my VOIP setup failed spectacularly. I then downgraded back to 5.4 and have been there ever since, siiigh. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Better to make XFree86-4 when XFree86-3 isn't running?
Dmitry Morozovsky wrote: > Hmm... Reading through, I did not find any very specific "it does not > work" cases. However, I see that many people found ATI cards as a PITA. > > ... the problem is that I have no spare hardware to test it thoroughly, > and my workstation works also as central monitoring point for our network > ;-) > > Maybe I'll try "ati*.o from 4.1" way... > > Stangely enough, there is no info about ATI<->XFree86 4.2 at > http://www.xfree86.org/4.2.0/Status6.html I'm using a Radeon 8500 128MB card. I had problems with 4.2.0 (it worked but a few things were a tad flaky, especially Xvideo), but I've been updating from the XFree86 CVS tree and it is working better and better. Just one data point. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADSUP: XFree86 4.3.0 update
Eric Anholt wrote: > Again, as I said in the message that began this thread, it is not going > to be updated. Follow the instructions at my DRI site to get the MFC of > the DRM (which supports that card) to -stable. Okay, well, I did this. And. After a couple of false starts, I got the proper kernel in, made sure all the old kernel modules were no longer being loaded, and rebooted. It hangs on boot. Wedges solid, just after printing the aperture size. It seems to initialize AGP and DRM, but then hangs completely. This is on a Tyan 2466N-4M motherboard (AMD chipset). I've attached dmesg output and my config, if that helps. I guess I should turn on DRM_DEBUG and see what comes of it. If there's any further info I can provide, please let me know. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # http://www.FreeBSD.ORG/> # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.140 1998/12/27 13:55:47 sos Exp $ machine i386 cpu "I686_CPU" ident REALTIME maxusers0 options CPU_ENABLE_SSE #optionsMATH_EMULATE#Support for x87 emulation options INET#InterNETworking #optionsINET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options NFS #Network Filesystem options MFS #Memory Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660"#ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SOFTUPDATES options USER_LDT#allow user-level control of i386 ldt options MROUTING# Multicast routing options RANDOM_IP_ID options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options _KPOSIX_VERSION=199309L #optionsPPS_SYNC options IPSEC options IPSEC_ESP options COMPAT_LINUX options DRM_LINUX config kernel options DDB #kernel debugger options DDB_UNATTENDED #Recover from panics. # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #optionsNCPU=2 # number of CPUs #optionsNBUS=3 # number of busses #optionsNAPIC=1 # number of IO APICs #optionsNINTR=24# number of INTs device isa0 device pci0 # AGP GART support # device agp device fdc0at isa? port "IO_FD1" irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # # The 'ATA' driver supports all ATA and ATAPI devices. # It can reuse the majors of wd.c for booting purposes. # You only need one "device ata" for it to find all # PCI ATA/ATAPI devices on modern machines. #device ata #device atadisk # ATA disk drives #device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. device ahc0# AHA2940 and onboard AIC7xxx devices device ahc1# AHA2940 and onboard AIC7xxx devices device ahc2# AHA2940 and onboard AIC7xxx devices device ahc3# AHA2940 and onboard AIC7xxx devices device ahc4# AHA2940 and onboard AIC7xxx devices #device sym0# NCR/Symbios Logic (newer chipsets) #device sym1# NCR/Symbios Logic (newer chipsets) # This controller offers a number of configuration option
Re: Vinum problems in 5.3-BETA7?
Paul Mather wrote: > Vinum is known broken in 5.3. :-) You should be using geom_vinum > instead. It will largely be a drop-in replacement for your above Vinum > configuration. (I am using it on a similar root-on-vinum setup.) The > main changes are these: What I need to know is whether the raid5 support in gvinum is solid, yet. I would dearly love to move my desktop system from 4-stable to RELENG_5, but I have two rather large vinum raid5 filesystems that I really need to keep. Is anyone actually using raid5 with gvinum on RELENG_5? If so, how stable is it? (The last I heard, there were still potential data corruption problems, but I'm hoping that those have been fixed by now.) -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem reporting build failure (rebuilding bootstrap, crtbeg in.c:33)
John Polstra wrote: > In article <3F69A3D5863ED211B31FF809353502D1DC84@FSUHHZ33>, > Lofthouse Andrew 2Lt WRALC/TIECT <[EMAIL PROTECTED]> wrote: > > > > I wish it were that simple. I just tried doing make upgrade last night with > > -STABLE, but the build crashed (an error with ioctl.c; there was an > > undefined function in ioctl.c and another problem with one of the include > > files; I didn't bring my script output with me today so I can't remember > > exactly what the problems were.) Perhaps that's because I didn't have > > 2.2.8-STABLE (just -RELEASE). Thanks for the tip on the cited website; I'll > > check it out. > > Use "make upgrade" to get from 2.2.8-stable to 3.0-release. Then > use "make world" to get from 3.0-release to 3.x-stable. "Make upgrade" doesn't exist in 3.0-release. There's just world, aout-to-elf, aout-to-elf-build, aout-to-elf-install and move-aout-libs. -- Frank Mayhar [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Sound Blaster Live! 4.0 (Re: 4.1 date?)
Bryan Bradsby wrote: > No problems here since Tuesday: 4.0-S, K7, SB Live, sony CD-RW > Plays music CDs great. No reboots. Do _you_ have ECC memory? (Otter didn't, btw; I'm just trying to establish a pattern.) -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pcm0 sblive and dodgy irq: 100000
Mike Hoskins wrote: > pcm0: at io 0x1060 irq 10 (4p/3r channels duplex) > But, after installing xmms, loading an mp3, and clicking 'play', the > system reboots. You have ECC memory, right? This is a known problem. Cameron will soon have some ECC memory himself so he can reproduce this and hopefully fix it. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
