Re: yep, umass still broken
On Fri, 26 Sep 2003, Brian Fundakowski Feldman wrote: I can get fdisk to read the MBR, but when I try mdir, I get this trace back (of course, no crash dump because those haven't worked for me in a year): trap 0xc memcpy() ohci_softintr() usb_schedsoftintr() ohci_intr1() ohci_intr() ithread_loop() Anyone have any clued? I'll include my dmesg, of course. It was unbroken for a while, but has been broken for at least a month (seem my earlier post about it). The umass driver has been a constant source of frustation for me and suffers from constant breakage and neglect. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
USB / VM-related panic (vm_fault)
When attempting to copy files from my digital camera I get this panic in what appears to be the VM system, however I don't get a traditional panic message or a kernel dump, just a ddb backtrace. This is copied by hand so I hope there are no errors: panic: vm_fault: fault on nofault entry, addr: d3b5c000 Stack backtrace: backtrace(c0336a41, c038ac00, c03402ac, d677c9f8, 100) at backtrace+0x17 panic(c03402ac, d3b5c000, 2, d677cb0c, d677cafc) at panic+0xb7 vm_fault(c082f000, d3b50010, 10, d3b5c000, dcafa000) at trap+0x30f calltrap at calltrap+0x5 --- trap 0xc eip=0xc02fad50, esp = 0xd677cc38, ebp = 0xd677cc64 --- memcpy(c3f88300, c3fc4ed0, 0, 1, 0) at memcpy+0x14 ohci_softintr(c3e6, d677ccc0, c018ff11, c3e6, 1848ef30) at ohci_softintr+0xc3 usb_schedsoftintr(c3e6, 1848ef30, d677, 52, c3e06700) at usb_schedsoftintr+0x12 ohci_intr1(c3e6000, d677cd08, c01ce6c8, c3e6, c630758b) at ohci_intr1+0x181 ohci_intr(c3e6000, c630758b, 74740107, 8d14558b, c3e55000) at ohci_intr+0x2f ithread_loop(c3e6f680, d677ed48, 14558b3b, 8dc00c8d, 80028a4c) at ithread_loop+0x1d8 fork_exit(c01ce4f0, c3e6f680, d677cd48) at fork_exit+0xb1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1 eip=0, esp=0xd677cd7c, ebp = 0 --- Debugger (panic) Stopped at Debugger+0x54:xchgl %ebx,in_Debugger,0 -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Text file busy
On Thu, 4 Sep 2003, Scott M. Likens wrote: On Thu, 2003-09-04 at 07:44, Paul Richards wrote: Overwriting a file that's currently executing results in a Text file busy error. When did this start happening? This was something that was fixed way back on FreeBSD but it seems to be a problem again. Paul. this feature has always existed in FreeBSD for as long as I remember. Of course there are ways to bypass this feature but it's there for your protection. You shouldn't be upgrading a program that's in resident memory. That's like trying to reinstall X while running in X. You're just asking for problems. turnoff postfix, install the new version and be happy. Every single 'flavor' of Unix/Unices has always had this feature. I've seen it on HP-UX box's on Solaris Servers, Linux, NetBSD, OpenBSD, FreeBSD. Maybe you wern't paying attention but, that is one of those things I think should fall under duh, i shouldn't do that it might make things crash hard. It's also unfortunate that this protection does not seem to extend to libaries. I've had some in-use X libraries get overwritten with some very colorful results. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
On Sun, 24 Aug 2003, Matt wrote: This did work perfectly with the old ATA, but the new ATA panic's. I have found that it is due to having device atapicam for the SCSI emulation. If I recompile the kernel with this option commented out the kernel boots and everything works normally (except the SCSI emulation). I can confirm that atapicam causes my system to hang, but not panic, on boot where the kernel would normally be detecting cd0. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lucent Technologies Orinoco Gold WiFi errors
On Thu, 21 Aug 2003, Michael Goffin wrote: Does anyone know if Orinoco Gold cards just don't work in 5.1-current, or if there is something special you have to do? I had the card working when I had 5.0-release without having to compile with OLDCARD. That install got really bad so I went to 5.1-release and cvsup'd to 5.1-current this morning compiling without OLDCARD. When I kill dhclient, set my ssid, then attempt to run dhclient again, it fails. I have received several error messages about bytes not clearing, the device being busy, and the input type being wrong. My gold card works fine and has for as long as I can remember. Try upgrading to the latest firmware. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: We have ath, now what about Broadcom?
On Sat, 26 Jul 2003, Doug White wrote: On Fri, 25 Jul 2003, M. Warner Losh wrote: : Can they now take they took relevant steps as a defence in a law court? That's a very interesting question. Which might get answered since some industrious folks aligned with a certain other open source operating system are in the process of reverse engineering said devices. Would not said software be illegal to distribute in the US? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: world breakage in pam_echo
On Wed, 16 Jul 2003, Christian Brueffer wrote: === lib/libpam/modules/pam_echo cc -O2 -pipe -march=pentium2 -I/usr/src/lib/libpam/modules/pam_echo/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_echo/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c /usr/src/lib/libpam/modules/pam_echo/pam_echo.c: In function `_pam_echo': /usr/src/lib/libpam/modules/pam_echo/pam_echo.c:92: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 I was just about to report this myself. The breakage only occurs with optimization levels of -O2 (and maybe higher). Officially -O2 is not supported for world, but in my experience there are real problems with code (warnings in this case) that do not show up until the optimizer takes a closer look at them. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Unkillable processes with libKSE
Thought I would give libKSE a try making use of the 'libmap.conf' library translations. KDE loads fine, but when I tried to run Firebird I get a process with 3 threads, and it is completely unkillable. It also is holding some kind of lock on it's own directory that has caused a couple of ls's to hang unkillable in lstat(): [EMAIL PROTECTED]:/usr/X11R6/lib/firebird/lib$]: ls ^C^C^Z^Z^Z^C^C^Z^C^Z^C^Z The offending threads are: 887 morganw -40 39120K 30972K ufs 0:02 0.00% 0.00% MozillaFirebi 887 morganw 760 39120K 30972K WAIT 0:02 0.00% 0.00% MozillaFirebi 887 morganw -80 39120K 30972K RUN 0:02 0.00% 0.00% MozillaFirebi Kernel has ddb in it and I'll leave the processes running as they don't seem to be causing any harm so if there is any information I can provide to help debug, let me know. Truss/strace/ktrace produce no output. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unkillable processes with libKSE
On Tue, 24 Jun 2003, Julian Elischer wrote: what about kill -9 887 ? The signals in libKSE are known to be 'delicate'. We are working on (well, actually David Xu is working on) a set of code to make the signal more robust. Hopefully this will fix the problem you are seeing.. Kill -9 doesn't work. Any other comments? Other than not being able to kill it, how as the experience? KDE seems fine... Firebird died before it got far enough to open any windows. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unkillable processes with libKSE
On Tue, 24 Jun 2003, Julian Elischer wrote: I can not duplicate this.. ON a system (SMP) compiled this afternoon (checked out this afternoon too), ksetest responds immediatly to ^C and ^Z in the expected manner. I am using the csh as my shell and was running as root AND as myself for the tests. %cd /usr/src/tools/KSE/ksetest/ % make %./ksetest main() : 0x804c000 [...] I just ran this test here and it locked my system hard. The zombie processes were stil around, I guess that may have had something to do with it. When I get some free time I'll try it again with everything mounted RO. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Libthr stable enough for testing
On Wed, 28 May 2003, Lars Eggert wrote: The machine (SMP) would sometimes freeze solid (no panic). I symlinked libc_r back to the original library, and from then on, starting gnomepanel and some other gnome pieces would fail due to errors about libthr. I couldn't find them in any log file right now, but I think I remember one was about getpwuid_r not being found. (The ports that caused problems were gnome 2.3 beta ports from the marcuscom CVS tree.) From what I understand, libthr should be a drop-in replacement for libc_r, so I was surprised to see this, but maybe I misunderstood? It's sort of a one-way street with libthr. It will drop in to replace libc_r, but it is more complete. When you built gnome it detected reentrant functions in libthr that are not present in libc_R, so you cannot go backwards (ie, libc_r is NOT a drop-in replacement for libthr). -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
modules vs kernel CFLAGS
I just noted that my kernel modules seem to be building with CFLAGS instead of COPTFLAGS as I would expect. Is this intentional? I always build my kernel with more safe optimization, and figured that the modules would naturally inherit the same. WNM -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ATA problems
This morning I booted a kernel built last night, and it panicked when trying to mount the root filesystem after this: ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ad0: removed from configuration done cvsup'd, built a new kernel, and now instead of a panic I get (with some extra stuff): atapci0: AcerLabs Aladdin UDMA66 controller port 0xeff0-0xefff at device 4.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ata1-slave: timeout waiting for interrupt ata1-slave: ATAPI identify failed ad0: 28615MB TOSHIBA MK3017GAP [58140/16/63] at ata0-master UDMA66 acd0: CD-RW UJDA720 DVD/CDRW at ata1-master PIO4 ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done Mounting root from ufs:/dev/ad0s2a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot ufs:ad0s2a Mounting root from ufs:ad0s2a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 :( -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: UFS2 regression tests?
On Wed, 19 Feb 2003, John De Boskey wrote: Hi Folks, I've just put together a 1.7TB filesystem and was looking for some regression tests to run against it. Looking through the mailing lists doesn't turn up anything, nor does a websearch (at least for the keywords I tried). So, does anyone have any comments/ideas on a good way to test the new system? How about getting some tarballs full of tons of files, extracting them, deleting and randomly powering down forcing an fsck... :p Not sure how much regression this provides but you're fairly likely to break something! -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC 3.2.2 import -- questions
On Wed, 12 Feb 2003, leafy wrote: Anders Yes I noticed it this morning too. The funny thing is that. If you use a non-P4 optmized GCC to compile lcms with P4 opt, then it passes the test. But with a P4 opted GCC, it borks. Looks like P4 opted GCC itself is bogus. That's odd. Does the FreeBSD build skill the stage2 compiler rebuild? I thought the gcc build process tested itself against itself. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2.2 is coming
On Mon, 10 Feb 2003, Rahul Siddharthan wrote: Alexander Kabaev wrote: The import should be complete now. Please let us know if you see any problems introduced with this GCC version. cc -O -pipe -mcpu=i686 -march=i686 -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/i386/usr\ -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp -I. -c /usr/src/contrib/gcc/cp/decl.c /usr/src/contrib/gcc/cp/decl.c: In function `cxx_init_decl_processing': /usr/src/contrib/gcc/cp/decl.c:6671: `c_size_type_node' undeclared (first use in this function) /usr/src/contrib/gcc/cp/decl.c:6671: (Each undeclared identifier is reported only once /usr/src/contrib/gcc/cp/decl.c:6671: for each function it appears in.) *** Error code 1 I just finished a make world after the import. No such problems here. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GCC 3.2.2 import -- questions
The import of gcc 3.2.2 brings a question to mind... Many people have mentioned problems with SSE / SSE2 instructions, optimizer problems etc that are supposedly fixed with 3.2.2... My question is, should I consider rebuilding my ports with this new compiler because of stability and/or speed improvements? Or is this point release not worth the effort. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC 3.2.2 import -- questions
On Mon, 10 Feb 2003, Craig Rodrigues wrote: Many people are upgrading from 4.7.x to -current for the first time these days, so I thought I would mention that for reference. GCC 3.2.2 was an incremental bugfix over GCC 3.2.1, and there are no earth-shattering performance improvements. I have not done such benchmarking myself, so have no empirical evidence to support this, but I am basing this on the traffic I have been watching on the GCC mailing list, and by reading the release notes at http://gcc.gnu.org/gcc-3.2/changes.html . Well what I am really interested in is whether or not higher levels of optimization are more reliable now than before. Previously we have been warned against using many of the CPU specific optimizations, especially for the pentium 4, and the release notes offer little to support any conclusions... So without digging through mountains of GCC mailing list archives... Are these optimizations SAFER now? -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: State of the Union Report (backout request department)
On Fri, 31 Jan 2003, Mike Barcroft wrote: The archives might not be telling the whole story. A lot of times these things get handled behind closed doors, whether private e-mail or developer-only lists. Thankfully though, most conflicts *do* get resolved. :) I have always LOVED watching the commits and backouts. I find it much more exciting to watch the actual development commit by commit, watch the brainiacs audit each other, and resolve to the best course. It seems much better than the way Linux traditionally did it (although they seem to have moved to bitkeeper) and much more like a professional development team. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic on boot with yesterday's -current
IPsec: Initialized Security Association Processing. IP Filter: v3.4.29 initialized. Default = pass all, Logging = enabled wi0: WaveLAN/IEEE at port 0x100-0x13f irq 11 function 0 config 1 on pccard0 wi0: 802.11 address: 00:02:2d:04:df:e4 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station 8.10.01 ata1-slave: timeout waiting for interrupt ata1-slave: ATAPI identify failed Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1 fault code = supervisor write, page not present instruction pointer = 0x8:0xc04a9c28 stack pointer = 0x10:0xd4e32c94 frame pointer = 0x10:0xd4e32ccc 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 = 12 (swi6: tty:sio clock) panic: from debugger The instruction pointer seems bogus, all the kernel symbols are in c03x. I think it might be in the ATA code. The 'double panic' looks like this at the end: panic: from debugger Uptime: 12s Terminate ACPI ad0: 28615MB TOSHIBA MK3017GAP [58140/16/63] at ata0-master UDMA66 Automatic reboot in 15 seconds - press a key on the console to abort -- Press a key on the console to reboot, -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GEOM + GRUB = ??
Trying to install a new version of GRUB not having much success. I'm wondering if GEOM is interacting with it in some strange way. I am fairly certain grub reads the partitions itself, but this would be through the geom layer would it not? The port might need to be marked broken for 5.0, or someone with geom know-how submit a patch to the grub folks (if that is really the problem). Can anyone else verify this? I'm using grub with a device-map file that used to work just fine. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM + GRUB = ??
On Wed, 4 Dec 2002, Terry Lambert wrote: The GRUB stuff does not use GEOM, because GEOM is an abstraction that lives in FreeBSD only. GRUB reads the data directly, itself. To do this, it has to have some knowledge of how to at least get at the code in the boot1/boot2 case (try booting one of the files in /boot instead of /kernel), and it needs to understand the FS layout for where the files are stored, and/or use a sector map. It will need to be updated for UFS2, when that becomes an issue. It's not the booting that is a problem. That was working fine until I had to wipe out the MBR when my disklabel was chomped last week.. It's the grub command-line shell/installer that won't work now (admittedly I have not updated my grub boot blocks in a while either, so it may be a pre-GEOM issue). Would not accessing /dev/adX with open() or so go through GEOM? -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Harry Potter and the Disappearing Disklabel
Yesterday morning I was having some trouble with XFree consuming much more cpu time than necessary... A truss showed that some kind of shared memory issue going on, but also froze my system hard. After rebooting (kernel was from Nov 26 or 27) fsck could not check my one dirty UFS2 partition. Had to newfs and mtree to recreate /var. No big deal, and I saved an image of it beforehand. After rebooting, there was... NOTHING. GRUB errored out and wouldn't boot. Nothing could see my partitions. After a minimal 4.7-R install (DP2 disklabel whined about offsets and some other STRANGE error messages, so I went with 4.7) on a small fat32 partition, I discovered that the disklabel was empty. Had to edit it by hand... Booted up fine, made a backup, rebooted, and nothing. Not only was there NOTHING, but the disklabel on the new 4.7 install had vanished as well. This time the disklabel had to be recreated with -w -r AND the boot blocks had to be reinstalled. I've seen one post similar to this, but not much else. I think maybe the UFS2 problem had to do with Kirk's recent changes, but the disklabel issue... I'm wary to reboot my machine! What in the hell could be causing this? I'm tempted to point the finger at GEOM, but hate to say anything like that. WNM -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Harry Potter and the Disappearing Disklabel
On Fri, 29 Nov 2002, Steve Kargl wrote: On Fri, Nov 29, 2002 at 09:41:56AM -0500, Wesley Morgan wrote: I've seen one post similar to this, but not much else. I think maybe the UFS2 problem had to do with Kirk's recent changes, but the disklabel issue... I'm wary to reboot my machine! What in the hell could be causing this? I'm tempted to point the finger at GEOM, but hate to say anything like that. Are your world and kernel in sync (post-kirk commit)? They are now, but were not before. However I fail to see what world has to do with disappearing disklabels between boots. Unless specifically asked to, nothing except the kernel should ever read it (at least, I am guessing this). -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Trashed Disk Labels
On Fri, 29 Nov 2002, Kirk McKusick wrote: I have had a report of a disk label getting trashed after booting up to a kernel with the new UFS2 superblock format. I have just checked in an update to ufs/ffs/ffs_vfsops.c (version 1.198) that explicitly checks to make sure that it will not trash your disk label. I highly recommend that you update to this version, even if you are only running with UFS1 filesystems. Kirk McKusick Great! Any tools available to extract my var/db/pkg dirs from this image of my trashed UFS2 filesystem? : -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DISABLE_PSE DISABLE_PG_G still needed?
On Fri, 15 Nov 2002, Vallo Kallaste wrote: Just finished '-j2 buildworld' and it did well with kernel which had the options enabled. Therefore I suppose that those options are still absolutely necessary to make use of -current system. These This may be a bit overstated. I removed those options from my kernel a few weeks ago and have no problems at all. Are you certain the problem is not specific to a particular CPU? options should be uncommented in NOTES and added to GENERIC otherwise new users will be trapped. All old -current users have those options probably enabled for a while, that's because there are no complaints. Actually, I'm not complaining, just testing out the bad things I have encountered in the near past. This darn 5.0-RELEASE is nearing way too fast considering the state of -current today. While I am just a small, small voice among many... I must agree :/... The few things that remain broken for me would be enough to sour testing 5.0 if I wasnt used to working around it. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DISABLE_PSE DISABLE_PG_G still needed?
Based on this, are you recommending that the DISABLE_* still be used? Will I never see the problem with 512mb of ram? On Fri, 15 Nov 2002, Terry Lambert wrote: The amount of RAM will also affect it. It can also happen on P3's and AMD K6's. It is a CPU bug related to the use of 4M pages. Let's not dance around the issue. Software has bugs. Hardware has defects. Bosko understands the problem (I have explained it to him under non-disclosure), and he has a patch which avoids it without really disclosing the problem, which I'm OK with. Using the patch cranks So basically, there is a DEFECT in something that either Intel or AMD has some me (you, everyone) and they will not disclose the defect, honor any warranties, or provide fixes for the problem? How... crappy. Reminds me of the Redhat/DMCA suppressed patch. I think consumers have a right to know about any defects in something they have bought. And I also think that the marketer should assume some liability for selling defective hardware (even though software makers seem to be able to get away with it). But this is getting way off topic :P -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Cannot find my Linux partition
On Thu, 31 Oct 2002, Craig Rodrigues wrote: On Thu, Oct 31, 2002 at 06:33:13PM +0100, Poul-Henning Kamp wrote: Please try this patch: I am also attaching the dmesg.boot file. I can now mount my Linux partition with: mount -r -t ext2fs /dev/da1s7 /linuxmount This might be a dumb question, but would the GEOM layer enable freebsd to be installed on an extended partition (with the proper mods to the bootloader??) -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libc size
On Thu, 31 Oct 2002, Tim Kientzle wrote: I agree with David Schultz that dynamically linking /bin and /sbin is playing with fire. I, too, have had ugly experiences on systems that did this: When /usr won't mount, it is not pleasant to be stuck with no tools. (Consider a network environment where /usr is NFS-mounted as an extreme example.) And of course the answer to that is to create a /lib. Something that I would *never ever* want to see. Sure, a few people might throw around the idea of an extremely light-weight set of libraries to go into /lib blah blah. But I just don't like the idea. Why not create a minimalist C library, build with -nostdlib and staticly link against exactly what you need. I usually create a 128 or 64mb root, and the only time this gets tight is when I keep too many kernels around in /boot. I seem to recall other arguments being settled by the disk space is extremely cheap issue. Call me crazy, but FreeBSD just has this zen feeling to it, and making this kind of change doesnt feel very zennish. I'm sure there are greater minds than mine working over this issue, but thats my $0.02. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kern/42417 cannot probe Olympus digital camera, C-1
On Fri, 1 Nov 2002, Ian Dowse wrote: In message [EMAIL PROTECTED], Nate Lawson wri tes: I looked at the change and it seems good. Can someone more familiar with the USB system verify this? Done - I have a C-1 here, so I was able to test it - obviously I haven't accessed the camera from -current in a while! Anyone care to take a look at kern/43462 and maybe get umass/da working before 5.0-R? Brian Feldman reported that the ohci was not working for him either (it appears to be not camera/umass related, but rather to the ohci driver). I've not had much luck contacting anyone related to USB. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Type1 font problem (Was: Re: mozilla-devel problems)
On Sat, 26 Oct 2002, Ollivier Robert wrote: According to Ollivier Robert: During its reading of all fonts available, it get a segv... Any idea ? Found that at least one of the Type1 fonts I had (installed by XFree86) does bad things to freetype and it was getting a segv. The interesting point is that it happens even if you have disabled the loading of the type1 module. Having the font in /usr/X11R6/lib/X11/fonts/type1 is enough... Im my many hours of playing with fonts, I seem to recall that the Freetype / XFT module is perfectly capable of rendering the Type1 fonts. Make sure you take the PATH out of your XftConfig in addition to the XF86Config -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mozilla-devel problems
On Thu, 24 Oct 2002, Adam Weinberger wrote: (10.24.2002 @ 1036 PST): Adam Weinberger said, in 2.2K: I'll put in a screenshot after I get moz recompiled with XFT. end of Re: mozilla-devel problems from Adam Weinberger FWIW, this is a screenshot of my -STABLE machine: http://people.freebsd.org/~adamw/smacky_ss_20021024.jpg I just finished a build of mozilla-devel, and the fonts look just as gorgeous as they do in Konqueror. If anyone is having problems with these fonts, try removing the Type1 module from your X config, and/or altering the fontpath so that directories with truetype fonts are listed first. I've been told that the directory order does matter, but I do not know how much this applies with the new font-config/Xft2 system. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X problems 5.0... -RELEASE?
On Sat, 19 Oct 2002, Juli Mallett wrote: Note that during these, mp3s keep playing, gtk-gnutella keeps downloading things, etc., it seems X just isn't updating the display... Even a resize of a sizable gtk frame I did while it was frozen took affect when it unfroze... Have you tried loggign into a system during such a freeze to see if it's sleeping or such? I would, except ENOSPAREBOX and if I try to switch to a console the screen getsd this black-and-green wooshy colour and then it sticks there. I have... The XFree86 process was runing wildly. Was able to kill it and regain the system. Did not think to gdb anything.. Truss coredumps trying to attach to it. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
X problems 5.0... -RELEASE?
The last tentative date for 5.0-RELEASE I have seen is late November, early December... This does seem odd since I haven't seen a DP2, but... Quite a few people seem to be having serious problems with XFree86 for 3-4 weeks, everything from sig 6's, the bezier crashes, to strange freezes that sometimes correct themselves. The bezier bug is somehow related to a problem with the Type1 module, and disabling it helps a little. I have rebuilt my kernel, world, QT, KDE, and X system with-mpentiumpro instead of pentium3. I have not yet seen any SIGABRT's, but I am getting unrecoverable crashes (console stuck) and the freezes that will pass after 5-10 minutes of nail-biting wait. During those freezes, I have logged in via the network and attempted to use ktrace and truss on the wildly out-of-control XFree86 process. truss dumps core (probably a thread issue?) and ktrace generates no output. I'm going to try to rebuild with debugging symbols to attach with GDB, which was successful but produced no meaningful output. The temporary freeze seems to always occurr in the Konqueror location bar when it attempts to complete a URL as I key it in, but the runaway process is XFree86. I know there is some work being done on the recent signal changes to fix some things, but are we sure this is the problem? I would hate to see release schedules pushed back because these problems are lost in the noise, and I can't see a release being made that has a known unstable X. Thanks WNM -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X problems 5.0... -RELEASE?
On Sun, 13 Oct 2002, Kris Kennaway wrote: On Sun, Oct 13, 2002 at 11:28:51PM -0400, Wesley Morgan wrote: I know there is some work being done on the recent signal changes to fix some things, but are we sure this is the problem? I would hate to see release schedules pushed back because these problems are lost in the noise, and I can't see a release being made that has a known unstable X. I thought this was believed to be a bug in X that was exposed by kernel changes. The Type1/bezier problems supposedly are, but as for the rest... I don't know. That's what my concern is -- if we uncovered a bug, even though its an X problem, the OS will still be blamed. Could the X server be doing something so absolutely completely braindamaged that these new-fangled signal things cause it to simply quit working? Surely an X bug of this magnitude would not be so localized and would have turned up on other platforms and even 4.x. I have a lot of faith in the RE team, and faith in 5.0 being a great new branch... It has some features that are a MUST for desktops and laptops -- firewire, acpi, cardbus, to name a few -- but a stable X is also a must. We don't want to become like Apache 2 ;) -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE 3.0 broken in current??
On Wed, 9 Oct 2002, Alex Zepeda wrote: I'm quite suprised how this managed to avoid detection for so long (webcvs.kde.org indicated that the last commit to this branch was 12 months ago). It's that whole feeling of fixing the same problems over and over again. Most likely this is a problem that was uncovered by some change in our headers. I've seen a lot of commits come down the pipes removing unneeded includes from one header or another... Which of course is the correct thing to do and it encourages better coding practices to make people put headers in the right order. Admittedly I run development versions of both FreeBSD and KDE, and the kde-freebsd team uses stable overwhelmingly so the combination doesn't receive the testing that others do. Last I checked, Will was at the very least testing each release on -current. KDE is such a big package I can't imagine it being very popular with testers, although with the new GCC snapshot imported I will probably rebuilt it. Would it be possible to modify the bento cluster to have another slice with the minimal -current install, and (using boot0cfg, or modifying a GRUB boot menu) reboot into -current for an automated package build? Or maybe this is already done. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
On Tue, 8 Oct 2002, Alexander Leidinger wrote: To fix signal 6, I think you need to rebuild your X server. Do you think I have to rebuild or do you know I have to rebuild? I've rebuilt several times. I'm guessing NO, since I still have the problems periodically. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
This sounds very similar to a problem I am seeing that does not result in a fatal lockup, but rather several minutes of complete unresponsiveness. It only seems to happen when Konqueror tries to autocomplete from the location bar. On Mon, 7 Oct 2002, Andrew Gallatin wrote: Every so often, my X server locks up. It seems to be in a tight loop, 95% user time, and making only these ktrace'able calls: 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.39 CALL sigreturn(0xbd9e7b0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019951 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.15 CALL sigreturn(0xbd9e6e0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019980 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 Anybody have a workaround for this? The whole system (2.53 Ghz P4) was compiled from sources late last week... Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic trying to utilize a da(4)/umass(4) device withohci(4)
Hi. See pr kern/43462. Happens to me. I wish it would get fixed :) On Sun, 6 Oct 2002, Brian Fundakowski Feldman wrote: I can't get more info because crash dumps don't work when this happens, but for what it's worth, here's a traceback which shows what happens when I attempt to use my da0: SanDisk ImageMate II 1.30 Removable Direct Access SCSI-2 device on an OHCI-based controller. This was working just a few days ago with a UHCI controller, so ... The crash is from an invalid read at 0xbff3e000, which is PTmap plus some offset. The trace as far as I can get it, from a kernel with USB but no options enabled, would be: ohci_alloc_std_chain+0xf5 (calling a DMAADDR() function, I believe) ohci_device_bulk_start+0x0d ohci_device_bulk_transfer+0x27 usbd_transfer+0xc0 umass_setup_transfer+0x4f umass_bbb_state usb_transfer_complete ohci_softintr Can anyone confirm if this is normal or I have an exceptional system? I have two completely unrelated OHCI-based controllers in my system and neither works. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The official GEOM is in the tree speech.
So I guess you want to change the behavior of sort to be POSIX... :P On Sat, 5 Oct 2002, Poul-Henning Kamp wrote: Ok, we've reached a milestone which have been on the radar for 8½ years, at least for some of us: GEOM is far from done yet, but unless I have overlooked something, it now meets and in may areas exceeds the capabilities of the previous code, and therefore the time is ripe for the change. Throughout history, there has always been a tradition for rallying the forces with a bit of pep-talk on the eve of a battle, so bear with me if this email gets to be a bit philosphical, but I have some things I want to say to you guys. get misunderstood: -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel boot messages absent
My sc0 device was at flags until I changed the hints line to: hint.sc.0.at=acpi A few days ago... On Thu, 3 Oct 2002, Bruce Evans wrote: On Thu, 3 Oct 2002, Bernd Walter wrote: On Thu, Oct 03, 2002 at 03:55:17AM +0200, Alexander Langer wrote: Also sprach Bernd Walter ([EMAIL PROTECTED]): You can verify with conscontrol. It should list consolectl for vga console and Muting off. from dmesg: sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 Now that you wrote it isolated - the flags are missing: sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 flags is a very unusual place for a device to be at. This happens on systems with working consoles too: vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 There is no sign of the keyboard ports where the keyboard part of sc0 really is at. This is a very old bug -- keyboard ports were not configured normally in 386BSD-0.0. My sc0 flags actually are 0x100. The virtual console flags seem to be unrelated to config flags. sc0 has been at flags here since at least 8 July. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)
Does this bug effect -stable? It only showed up in -current recently. Isn't it a bigger chance that something on the FreeBSD side made this bug much more visible? On Sun, 29 Sep 2002, Maxim Sobolev wrote: I think it should be fixed in FreeBSD ports before 4.7, because it is really annoying when server crashes without any particular reason. Eric, what do you think about it? -Maxim On Sun, Sep 29, 2002 at 03:17:41PM +0200, Frode Nordahl wrote: Hey, On Sun, 2002-09-29 at 14:51, walt wrote: [snip] I wonder if it could find the very annoying crashes in the X server. -- I'm sick of hearing about how big my Beziers are! I found this on the Xpert mailinglist: http://www.xfree86.org/pipermail/xpert/2002-June/018300.html Seems like this won't get fixed until XFree86 4.3.0, but the bug seems to be in the Type1 font handler only. (a call to abort()) I have removed it from my XFree86 config now, and I'm hoping for no more Bezier crashes :) Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)
Yes, i don't see any -stable systems bombing out. But it _always_ occurrs when typing. No matter what app... Sometimes in the linux opera, sometimes in the konq address bar. I dont think it ever happened when typing in an Xterm though. On 29 Sep 2002, Frode Nordahl wrote: On Sun, 2002-09-29 at 21:17, Eric Anholt wrote: From what I had heard on the lists it was only a thing that happened when people upgraded kernels, and that it had stopped after some date of kernel. I hadn't experienced it, so I ignored it. I don't know about that link posted, I thought that was a mozilla bug that was supposed to be fixed. It seems like the bug has been present in XFree86 all the time. But some thing has changed in CURRENT that tickles this bug. I started to experience this after I removed all ports and recompiled XFree86 with the new GCC 3.2.1. X also dies with signal 11 some times, so theres more to it than the Bezier bug. But if it is a CURRENT kernel or compiler issue, I don't understand why / how this should affect -STABLE / -RELEASE. I'll take a backup of my current X installation and do some tests and comparisons against the Aug 24 port build of XFree86. I'll have to find a sure way to reproduce the abort() and / or SIGSEGV failure first though. -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/dri/ -- Mvh, Frode Nordahl -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: troubles with recent -current
I thought it was just me, but since last week sometime I have been seeing several strange crashes in X. It usually has something to do with the keyboard. X will bomb out saying it caught a sig11, and the message in my system log shows a sig6. At first I thought this was due to using XFree that I had built with ICC, but I reverted that and lowered the optimizations and I still see it. My kernel is from Sept 21, and i was going to update last night until I saw all those scary VFS commits come down the pipe. On Wed, 25 Sep 2002, Mikhail Teterin wrote: X-server was working fine up to a few weeks ago. With Sep 17th kernel it began crashing every few days. With today's kernel the whole machine reboots after a few minutes in X11, although it can go through kernel (and/or XFree86-4) build in text only mode. I rebuilt XFree86-4-libraries and -Server to be sure, but it is not helping :-\ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
Yep, I'm seeing this using the new native Opera binary, when doing some font-related things. On Wed, 25 Sep 2002, Eric Hodel wrote: walt ([EMAIL PROTECTED]) wrote: WTF is a bezier? A bezier is a type of curve drawn by endpoints and anchor points to bend it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: X server crashes?
That precisely describes my crashes. _always_ when i was typing something. On Wed, 25 Sep 2002, Peter Wemm wrote: This was a few days ago. I was typing something at the time. Mozilla was running but it is an old linux binary, not a freebsd-native binary. Unless exmh/wish or xterm are threaded, I think that clears libc_r. This machine has not had an X server crash in over 6 months - until that one. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trouble building XFree86-4-Server under yesterday's current
I have built XFree86 at least 3 times in the past week, all with varying levels of optimization, from -O to -O3 and ALWAYS with -march=pentium3. All of the builds succeeded, although I had stability problems with -O2 and above. Are you _certain_ this is a compiler bug? On Tue, 24 Sep 2002, Vallo Kallaste wrote: On Mon, Sep 23, 2002 at 03:13:15PM -0700, Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Sep 23, 2002 at 01:55:18PM +0300, Vallo Kallaste wrote: This isn't a yesterdays problem, I've had this for a month or so. The problem is explicit declaration of -march=p[234], use CPUTYPE=i686 in /etc/make.conf and you get further. The second way is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will set -mcpu to what appears to fit. That's not true; it adds -mcpu=pentiumpro by default to optimize instruction scheduling for 686-class CPUs (without breaking binary compatibility down to i386s), but it doesnt autodetect anything, and you'll get better performance on a 686-class CPU by specifying it in CPUTYPE (since you'll then also get pentium pro instructions). -mcpu != -march Yes I know and it was what I meant to say. By setting CPUTYPE=p[234] excplicitly in /etc/make.conf you'll get the build failure in XFree86-4-Server because bsd.cpu.mk will set excplicit -march, not -mcpu. But the build error happens _only_ if one sets CPUTYPE=p[234] and not in case CPUTYPE=i686, the latter sets -march=pentiumpro, not -march=pentium[234]. Hope this is all clear now and sorry about confusion, english isn't my native tongue after all. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: `lorder' problem
You may already know this, but the GNU sort also check for the environment variable _POSIX2_VERSION, and according to the docs setting it to 199209 will revert to the old style usage (and unbreak world I am guessing) On Tue, 24 Sep 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Garrett Wollman writes: Anyone experiencing this problem might want to try the following (beware cutpaste). I still don't understand why it is that I don't see it. Is there a hidden build dependency? (I.e., does `sort' need to be added to the list of build-tools?) It's because sort is not in build-tools and you havn't done an installworld. cd /usr/src/usr.bin/sort make obj make depend make all install should make you see it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 machine/endian.h
I've been playing around with lang/icc a bit, and find it quite vexing that machine/endian.h has macros that are ifdef'd around __GNUC__. The intel compiler does not like the macros, partly because they are split across multiple lines and possibly for other reasons. It seems to me that making a header actually _require_ gcc-isms is something that the FreeBSD team should be working away from... Would it not be possible to put make some more generic macros available as well? I'm sure it's not the only instance of similar issues, but making one header less gcc-dependent is a step in the right direction is it not? WNM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: i386 machine/endian.h
As far as I can tell there are no __bswap* macros in the libraries; they are defined as bswap*. Whatever should be happening, the network byte swapping functions are creeping in using the __hton* and __ntoh* macros. These are pulling in the __bswap* functions that are of course undefined. Unless I'm doing something completely wrong here... Just dropping in icc to replace gcc/g++. On Mon, 23 Sep 2002, Bruce Evans wrote: On Sun, 22 Sep 2002, Wesley Morgan wrote: I've been playing around with lang/icc a bit, and find it quite vexing that machine/endian.h has macros that are ifdef'd around __GNUC__. The intel compiler does not like the macros, partly because they are split across multiple lines and possibly for other reasons. The Intel compiler shouldn't see these macros, so it should emit calls to the corresponding library functions. The macros work correctly with Tendra because it doesn't see them. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failure in openssl?
Nope, but i see that here. DES reported it too, but we get some many 'tinderbox failures' from him that some people might just ignore them =) On Thu, 19 Sep 2002, Andrew Gallatin wrote: I'm trying to upgrade a ~March -current machine to a more modern version. Buildworld is dying like this: stage 4: building libraries -- .. === secure/lib/libssl mkdir -p openssl sh /usr/src/tools/install.sh -C -m 444 /usr/src/secure/lib/libssl/../../../crypto/openssl/crypto/dso/dso.h openssl mkdir -p openssl sh /usr/src/tools/install.sh -C -m 444 /usr/src/secure/lib/libssl/../../../crypto/openssl/crypto/conf/conf_api.h openssl make: don't know how to make openssl/ssl.h. Stop *** Error code 2 I've gone so far as to rm -rf my source tree and re-check it out. Nothing in UPDATING jumps out at me. Does anybody have any ideas? Thanks, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ssl.h world breakage... fix coming??
This has been mentioned several times now... Surely the fix is trivial :) Is anything in the works? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: slapd dumping core with today's current.
Boot from a kernel from a day or two ago and you should be fine. Unless you build every day, your kernel.old/kernel should be in agreement with libc_r On Wed, 18 Sep 2002, Julian Elischer wrote: threads is broken right now.. due to a miscommunicatin,. the kernel and the threads library have a disagreement regarding something.. Unfortunatly the person to slap up over this is offline for aday or so.. please be patient for a day or so (we hope). On Wed, 18 Sep 2002, Edwin Culp wrote: I just realized that slapd dumps core with: Fatal error '_pq_insert_head: prioq not protected!' at line 185 in file /usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 22) Abort (core dumped) I have recompiled openldap and db3 but it didn't help. Any suggestions would be appreciated. I also get the same error with mozilla but I see that has already been reported. Thanks, ed -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: bad pte
I haven't been paying much attention to the issues lately... BUT...
I have the same problem on my p3. But it's not just during the openoffice
built.. It occurrs at other times too. Unfortunately it seems to be a hard
freeze because I don't get any dumps (or maybe its breaking to ddb and I
need to panic it myself).
I *thought* it was a problem with suspending a process that had children,
but I did some suspending today and had no problems.
On Wed, 11 Sep 2002, Martin Blapp wrote:
Hi all,
This is current from yesterday.
I get all the time the same panics while building openoffice
on my PIV machine. Some are due the fg/bg issue.
My machine panics instantly if I have a sleeping openoffice
build and try it to invoke it again with fg.
But this one here happened during compile ... It's the first
time for this one.
Before gcc3.2 came in, I never had _that_ many panics. Current
seems to be in a very bad shape today.
If you like to see this, please build openoffice and see Current
crash ... Yes - openoffice is the ultimative regression tool.
My box survives buildworlds with -l 100, but not a simple openoffice
build.
#10 0xc01ed998 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:479
#11 0xc02fe2a5 in pmap_remove_pages (pmap=0xc1f97e04, sva=0, eva=3217031168)
at /usr/src/sys/i386/i386/pmap.c:2946
#12 0xc01d91f6 in exit1 (td=0xcc51e600, rv=0) at vm_map.h:226
#13 0xc01d8d64 in exit1 (td=0xcc51e600, rv=-391697172)
at /usr/src/sys/kern/kern_exit.c:112
---Type return to continue, or q return to quit---
#14 0xc0300944 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077938328, tf_esi = -10779
38312, tf_ebp = -1077938536, tf_isp = -391697036, tf_ebx = 3, tf_edx = 134581045
, tf_ecx = 1, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = 134703471, tf_cs
= 31, tf_eflags = 662, tf_esp = -1077938676, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1050
#15 0xc02f384d in Xint0x80_syscall () at {standard input}:140
(kgdb) frame 11
#11 0xc02fe2a5 in pmap_remove_pages (pmap=0xc1f97e04, sva=0, eva=3217031168)
at /usr/src/sys/i386/i386/pmap.c:2946
2946panic(bad pte);
(kgdb) list
2941tpte = *pte;
2942
2943if (tpte == 0) {
2944printf(TPTE at %p IS ZERO @ VA %08x\n,
2945pte, pv-pv_va);
2946panic(bad pte);
2947}
2948
2949/*
2950 * We cannot remove wired pages from a process' mapping at this time
(kgdb) p pte
$1 = (pt_entry_t *) 0xbfc20370
(kgdb) p tpte
$2 = 0
(kgdb) p pv-pv_va
$3 = 135118848
Martin
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
_ __ ___ ___ ___ ___
Wesley N Morgan _ __ ___ | _ ) __| \
[EMAIL PROTECTED] _ __ | _ \._ \ |) |
FreeBSD: The Power To Serve _ |___/___/___/
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
sio problems?
The sio driver was touched recently for the PUC stuff... Not sure if that is the source of my problem, but suddenly I am seeing many many many of these: sio1: 22 more interrupt-level buffer overflows (total 2943) Just started recently. Seems to happen most often when I cvsup. Happens with and without ACPI, with and without using a shared interrupt. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: When will PCI_ENABLE_IO_MODES be default?
So, how much does this have to do with my laptop's sound (DSP) dumping out after about 10 seconds? (Toshiba had the great idea of hard-wiring most everything through IRQ 11, although pccardd seems to be able to use others) Longer Answer: For some time now MS has had the notion of a Plug and Play OS at the BIOS level. Most BIOSes had the ability to say This OS is a Plug and Play OS and would refrain from assigning resources to the pci cards that might be a pita for the PnP OS to deal with down the road. In a Plug and Play OS, it deals with resource issues compeletely and totally (except for devices required to boot the system, iirc). In a non PnP OS, like FreeBSD, the OS expects the BIOS to have assigned all the resources and activated all the cards. For years, this worked great. ACPI can be viewed as an even more extensive attempt to get the OS to assign all the resources to the cards. Now with ACPI in more and more BIOSes, they are shipping w/o the ability to turn off PnP OS. They assume that the OS will be at least PnP, if not fully use the ACPI paradigm[*] to do its resource thing. FreeBSD has to cope with this better in general. PCI_ENABLE_IO_MODES is a kludge that only kinda makes things better. NetBSD does a better job at this by enumerating things at boot time and assigning resources when the big picture is being looked at. FreeBSD should do this as well. We will have to deal with assigning things that could need more resources later, like cardbus and cPCI bridges, big chunks of space that they can later dole out as needed. pci bridges make this problem more interesting because some of them will only decode certain address ranges (which is the cause of another kludge in the pci code). You can do a web search for the pc99 design guide (and newer ones). They go into some of this. The ACPI standards docs also go into this as well, although the 1.0 verion didn't do it very well (imho). There are a number of other places to look for information too. The mindshare books might be good. I'm not aware of one place the ties all of these customs together into a coherent hole :-(. Warner [*] These are wesil words for The OS does all the resource assignment. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: php4 -DWITH_APACHE2 breaks on -current
The standalone php cgi is a little borked too. It won't work with squirrelmail unless you remove a configure option. I cant remember which one right now, but I figured it out before :) On Thu, 11 Jul 2002, Edwin Culp wrote: Simon, Alex Dupre [EMAIL PROTECTED] submitted mod_php-dev with PR ports/39623 on July 7 that I have been using and works great There is/was a copy of the port at: http://www.gufi.org/~alex/php-dev.tar.gz Alex has done a several updates on this and I think it has never been committed. I have used every version with no problems. It has always worked as expected with both apache2 and apache13. It uses a snapshot of php 4.3.0 w/PEAR. Hopefully it will be committed soon. ed Quoting Simon 'corecode' Schubert [EMAIL PROTECTED]: | hello, | | just wanted to note that php4 breaks with -DWITH_APACHE2 on latest | -CURRENT: | | [...] | Making all in apache2filter | /bin/sh /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/libtool --silent | --mode=compile cc -I. | -I/usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/sapi/apache2filter | -I/usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/main | -I/usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1 | -I/usr/local/include/apache2 | -I/usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/Zend | -I/usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/ext/xml/expat | -D_REENTRANT -D_THREAD_SAFE | -I/usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/TSRM | -I/usr/local/include/pth -O -pipe -march=athlon -I/usr/local/include | -pthread -DZTS -prefer-pic -c sapi_apache2.c | In file included from /usr/local/include/apache2/apr_portable.h:90, | from /usr/local/include/apache2/http_protocol.h:64, | from sapi_apache2.c:38: | /usr/local/include/pth/pthread.h:504:1: warning: fork redefined | In file included from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/TSRM/TSRM.h:40, | from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/Zend/zend_alloc.h:26, | from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/Zend/zend.h:154, | from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/main/php.h:34, | from sapi_apache2.c:23: | /usr/local/include/pth/pth.h:507:1: warning: this is the location of the | previous definition | [...] | In file included from /usr/local/include/apache2/apr_portable.h:90, | from /usr/local/include/apache2/http_protocol.h:64, | from sapi_apache2.c:38: | /usr/local/include/pth/pthread.h:521:1: warning: pwrite redefined | In file included from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/TSRM/TSRM.h:40, | from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/Zend/zend_alloc.h:26, | from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/Zend/zend.h:154, | from | /usr/obj/k7/usr/ports/www/mod_php4/work/php-4.2.1/main/php.h:34, | from sapi_apache2.c:23: | /usr/local/include/pth/pth.h:526:1: warning: this is the location of the | previous definition | sapi_apache2.c: In function `php_input_filter': | sapi_apache2.c:287: structure has no member named `__pthread_read' | *** Error code 1 | | this is because pth's pthread.h re#defines several funtions to | __pthread_funtions but apache's bucket stuff uses a struct with a member | variable called ``read''. so this gets replaced and boom. | | cheers | simon | | -- | /\ http://corecode.ath.cx/#donate | \ / | \ ASCII Ribbon Campaign | / \ Against HTML Mail and News -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE status report
After reading this... I got to thinking, and I copied the old headers into the wrong place. After rebuilding, it works fine :)... That's what I get for doing it at 2am! My fault, you guys could have fixed this almost immediately except for some bad info from me. Good idea. Unforunatly someone tried to complie a libc_r with the old queue.h and it had the same problem (or so they said). On Tue, 2 Jul 2002, Ian Dowse wrote: In message [EMAIL PROTECTED], Ju lian Elischer writes: The big problem at the moment is that something in the source tree as a whole, and probably something that came in with KSE is stopping us from successfully compiling a working libc_r. (a bit ironic really). Is the new (elm)-field.tqe_next = (void *)-1; in TAILQ_REMOVE a likely candidate? That could easily tickle old bugs in other code. The libc_r code does use a lot of TAILQ macros. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KSE status report
KDE is working fine. GIMP GNUCash are the only two gnome apps I am using, and they both work. Everybuddy now works... In short, it all seems to work. I am using rev 1.225 of proc.h and 1.48 of queue.h. Last cvsup was Jul 1 17:13 MDT. ok, so you are saying that GNOME stuff works fine? What do yuo have running and is there still anything that does the wrong thing? On Tue, 2 Jul 2002, Wesley Morgan wrote: After reading this... I got to thinking, and I copied the old headers into the wrong place. After rebuilding, it works fine :)... That's what I get for doing it at 2am! My fault, you guys could have fixed this almost immediately except for some bad info from me. Good idea. Unforunatly someone tried to complie a libc_r with the old queue.h and it had the same problem (or so they said). On Tue, 2 Jul 2002, Ian Dowse wrote: In message [EMAIL PROTECTED], Ju lian Elischer writes: The big problem at the moment is that something in the source tree as a whole, and probably something that came in with KSE is stopping us from successfully compiling a working libc_r. (a bit ironic really). Is the new (elm)-field.tqe_next = (void *)-1; in TAILQ_REMOVE a likely candidate? That could easily tickle old bugs in other code. The libc_r code does use a lot of TAILQ macros. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Post-KSE disaster with libc_r
Reverting to: uthread_sigpending.c 1.8 uthread_sigsuspend.c 1.11 Makefile.inc 1.32 Has no effect. As far as I can tell theres no more changes... Looking at some ktrace / gdb output shows the funny business starting right after kdeinit tries to fork into something else: 2723 kdeinit CALL gettimeofday(0x28e94ab8,0) 2723 kdeinit RET gettimeofday 0 2723 kdeinit CALL wait4(0x,0,0x1,0) 2723 kdeinit RET wait4 2724/0xaa4 2723 kdeinit CALL poll(0x8059000,0x1,0) 2723 kdeinit RET poll 1 2723 kdeinit PSIG SIGSEGV SIG_DFL 2723 kdeinit NAMI kdeinit.core Both the kdeinit and a child it forks are dying... Setting a breakpoint of fork() in the binary shows: Breakpoint 1, 0x28eda7d4 in fork () from /usr/lib/libc.so.5 (gdb) bt #0 0x28eda7d4 in fork () from /usr/lib/libc.so.5 #1 0x28e83a5c in fork () from /usr/lib/libc_r.so.5 #2 0x0804e8d5 in QGListIterator::~QGListIterator() () #3 0x0804add1 in QGListIterator::~QGListIterator() () (gdb) s Single stepping until exit from function fork, which has no line number information. 0x28e83a5c in fork () from /usr/lib/libc_r.so.5 (gdb) Single stepping until exit from function fork, which has no line number information. warning: Cannot insert breakpoint 0: Error accessing memory address 0xd0d0d0d0: Bad address. (gdb) the 0xd0d0d0d0 is the same as in the coredump earlier. Rebuilt libc_r with debugging symbols and... (gdb) bt #0 thread_kern_poll (wait_reqd=0) at /usr/src/lib/libc_r/uthread/uthread_kern.c:862 #1 0x28e8c8d7 in _thread_kern_scheduler () at /usr/src/lib/libc_r/uthread/uthread_kern.c:372 #2 0xd0d0d0d0 in ?? () #3 0x0001 in ?? () #4 0x5f28 in ?? () Error accessing memory address 0xbecf2000: Bad address. Hope some of this is useful to anyone out there! On Sun, 30 Jun 2002, Julian Elischer wrote: Can someone please check out a libc_r tree as of 3 days ago and try that... There was a commit in libc_r/uthreads 2 days ago that might be relevant. failing that, can someone try newly compiled utilities on an older pre-KSE kernel? We need to eliminate one of these two changes... I think it's likely that it's breakage in signals from KSE but I'd like to know that before I tear even more hair out chasing this.. SO, I'm suffering from brain fade now.. but please, signals is known to be in dire need of cleanup after the KSE edit, (signals are delivered to processes but can effect individual threads. yuck) Anyone who can help identify the problem please do.. I'm off to bed before my head explodes.. I'll be back tomorrow AM. I'm going to spend as much of msuspension sleeping as possible :-) On Mon, 1 Jul 2002, Wesley Morgan wrote: I see this problem too. Luckily I have my entire KDE and QT system build with debugging symbols... However, the problem is definitely in the libc_r... I get virtually the same dump as Michael. #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x0001 in ?? () #4 0x5f28 in ?? () On Sun, 30 Jun 2002, Bill Huey wrote: On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x080570b0 in ?? () This is unlikely to be a KSE problem. What do the rest of the threads look like ? Try info threads in gdb and then progressively walking through the thread list with thread N, N being the thread number. I ran into a funny create at thread start up time crash and I'm wondering if it could be the same thing. bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED
Re: Post-KSE disaster with libc_r
Ktracing with context switches look the same as before
Stepping into libc_r leads me on a merry chase through what appears to be
normal execution, until somewhere in uthread_sig.c about line 552...
(gdb) r
Starting program: /usr/local/bin/kdeinit
Breakpoint 1 at 0x28e839f6: file
/usr/src/lib/libc_r/uthread/uthread_fork.c, line 49.Breakpoint 1, 0x28eda7d4 in fork
() from /usr/lib/libc.so.5
(gdb) b /usr/src/lib/libc_r/uthread/uthread_sig.c:546
Breakpoint 2 at 0x28e8723d: file
/usr/src/lib/libc_r/uthread/uthread_sig.c, line 546.(gdb) c
Continuing.
Breakpoint 2, thread_sig_handle_special (sig=20)
at /usr/src/lib/libc_r/uthread/uthread_sig.c:546
546 for (pthread = TAILQ_FIRST(_waitingq);
(gdb) print _waitingq
$1 = {tqh_first = 0x8054000, tqh_last = 0x8054210}
(gdb) s
0x28e8723e in thread_sig_handle_special (sig=20)
at /usr/src/lib/libc_r/uthread/uthread_sig.c:546
546 for (pthread = TAILQ_FIRST(_waitingq);
Program received signal SIGSEGV, Segmentation fault.
0x28e8723e in thread_sig_handle_special (sig=20)
at /usr/src/lib/libc_r/uthread/uthread_sig.c:546
546 for (pthread = TAILQ_FIRST(_waitingq);
Odd... Now if I set a breakpoint inside of the for() loop at line 552, it
will actually get past that:
Breakpoint 2, thread_sig_handle_special (sig=20)
at /usr/src/lib/libc_r/uthread/uthread_sig.c:552
552 pthread_next = TAILQ_NEXT(pthread, pqe);
(gdb) s
558 if (pthread-state == PS_WAIT_WAIT) {
(gdb) s
Program received signal SIGSEGV, Segmentation fault.
thread_sig_handle_special (sig=20)
at /usr/src/lib/libc_r/uthread/uthread_sig.c:558
558 if (pthread-state == PS_WAIT_WAIT) {
(gdb) print pthread
$1 = (struct pthread *) 0x210
That definitely is not right!
Backing up, this is the content of the pthread struct before it gets
munched into 0x210 (re-ran the process of course)$1 = {magic = 3499860245,
name = 0x8056030 _thread_initial, uniqueid = 0, lock = {access_lock = 686322256,
lock_owner = 0, fname = 0x0, lineno = 0},
tle = {tqe_next = 0x0, tqe_prev = 0x28e94a88}, dle = {tqe_next = 0x0,
tqe_prev = 0x0}, start_routine = 0, arg = 0x0, stack = 0xbfb0,
attr = {sched_policy = 3, sched_inherit = 0, sched_interval = 2, prio = 15,
suspend = 0, flags = 0, arg_attr = 0x0, cleanup_attr = 0,
stackaddr_attr = 0xbfb0, stacksize_attr = 1048576,
guardsize_attr = 4096}, ctx = {jb = {{_jb = {686343554, 686378132,
-1077939364, -1077939336, -1, 134561792, 4735, 0, 0, 0, 0, 0}}},
uc = {uc_sigmask = {__bits = {686343554, 686378132, 3217027932,
3217027960}}, uc_mcontext = {mc_onstack = -1, mc_gs = 134561792,
mc_fs = 4735, mc_es = 0, mc_ds = 0, mc_edi = 0, mc_esi = 0,
mc_ebp = 0, mc_isp = 0, mc_ebx = 0, mc_edx = 0, mc_ecx = 0,
mc_eax = 0, mc_trapno = 0, mc_err = 0, mc_eip = 0, mc_cs = 0,
mc_eflags = 0, mc_esp = 0, mc_ss = 0, mc_fpregs = {
0 repeats 28 times}, mc_flags = 0, __spare__ = {
0 repeats 16 times}}, uc_link = 0x0, uc_stack = {ss_sp = 0x0,
ss_size = 0, ss_flags = 0}, __spare__ = {0, 0, 0, 0, 0, 0, 0, 0}}},
curframe = 0x0, cancelflags = 4, continuation = 0, sigmask = {__bits = {0,
0, 0, 0}}, sigpend = {__bits = {0, 0, 0, 0}}, sigmask_seqno = 0,
check_pending = 0, state = PS_FDR_WAIT, last_active = 0, last_inactive = 0,
slice_usec = -1, wakeup_time = {tv_sec = -1, tv_nsec = -1}, timeout = 0,
error = 0, joiner = 0x0, join_status = {thread = 0x0, ret = 0x0, error =
0}, pqe = {tqe_next = 0x0, tqe_prev = 0x28e9a8d0}, sqe = {tqe_next =
0x0,tqe_prev = 0x0}, qe = {tqe_next = 0x0, tqe_prev = 0x28e97080}, data = {
mutex = 0x7, cond = 0x7, sigwait = 0x7, fd = {fd = 7, branch = 0,
fname = 0x0}, fp = 0x7, poll_data = 0x7, spinlock = 0x7, thread = 0x7},
poll_data = {nfds = 0, fds = 0x0}, interrupted = 0, signo = 0,
sig_defer_count = 0, yield_on_sig_undefer = 0, flags = 20,
base_priority = 15 '\017', inherited_priority = 0 '\0',
active_priority = 15 '\017', priority_mutex_count = 0, mutexq = {
tqh_first = 0x0, tqh_last = 0x8054254}, ret = 0x0, specific = 0x0,
specific_data_count = 0, cleanup = 0x0,
fname = 0x28e925a0 /usr/src/lib/libc_r/uthread/uthread_read.c, lineno
= 81}
Of course all this means absolutely nothing to me :) ... Setting the
breakpoint just past the for() loop give me the same old crash as before:
#0 thread_kern_poll (wait_reqd=0)
at /usr/src/lib/libc_r/uthread/uthread_kern.c:862
#1 0x28e8c8d7 in _thread_kern_scheduler ()
at /usr/src/lib/libc_r/uthread/uthread_kern.c:372
#2 0xd0d0d0d0 in ?? ()
(gdb) print pthread
$2 = (struct pthread *) 0x
That's all I've got for now. Someone please tell me if posting this much
junk to -current is frowned upon. I'm looking for an old libc_r now, but
there could be some problems with the GCC changeout since DP1 that won't
work too well
Re: Post-KSE disaster with libc_r
Reverting proc.h and queue.h do nothing. Booting a kernel from 20020624, still crashes all threaded systems. Same behavior on a 20020620 kernel. I don't change any of those. On Mon, 1 Jul 2002, Daniel Eischen wrote: I'd suspect that it is something to do with the layout of the fpregs, mcontext or something like that. Libc_r mucks about in jmp_buf (userland) and ucontext/mcontext, so anything that changed those would cause problems. It's still unclear if a KSE kernel works with an old libc_r or visa versa. I'd like to see if a new libc_r works with an old kernel (someone who can boot kernel.back and test...) to check if you have a non KSE kernel, sysctl kern.threads will only succeed in a new kernel. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Post-KSE disaster with libc_r
I already tried that this morning, it had no effect ... Unless you would like me to try an old kernel with it On Mon, 1 Jul 2002, Julian Elischer wrote: can you try compiling a new libc_r with th efollowing change suggested by Dan Eischen: --begin quote: I also made changes to uthread_sigpending.c and uthread_sigsuspend.c 3 days ago (lib/libc_r/uthread/...). You can try reverting those changes and go back to revisions 1.18 and 1.11 respectively. --end quote.. so that is uthread_sigpending.c version 1.18 and uthread_sigsuspend.c version 1.11 Thanks Julian On Mon, 1 Jul 2002, Wesley Morgan wrote: Reverting proc.h and queue.h do nothing. Booting a kernel from 20020624, still crashes all threaded systems. Same behavior on a 20020620 kernel. I don't change any of those. On Mon, 1 Jul 2002, Daniel Eischen wrote: I'd suspect that it is something to do with the layout of the fpregs, mcontext or something like that. Libc_r mucks about in jmp_buf (userland) and ucontext/mcontext, so anything that changed those would cause problems. It's still unclear if a KSE kernel works with an old libc_r or visa versa. I'd like to see if a new libc_r works with an old kernel (someone who can boot kernel.back and test...) to check if you have a non KSE kernel, sysctl kern.threads will only succeed in a new kernel. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Post-KSE desaster
I see this problem too. Luckily I have my entire KDE and QT system build with debugging symbols... However, the problem is definitely in the libc_r... I get virtually the same dump as Michael. #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x0001 in ?? () #4 0x5f28 in ?? () On Sun, 30 Jun 2002, Bill Huey wrote: On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x080570b0 in ?? () This is unlikely to be a KSE problem. What do the rest of the threads look like ? Try info threads in gdb and then progressively walking through the thread list with thread N, N being the thread number. I ran into a funny create at thread start up time crash and I'm wondering if it could be the same thing. bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-current panic in suser_cred()
At some point between 20 Jun and (by my best guest) 22 Jun there has been
a problem introduced somewhere... How much more vague can you get? :)...
File creation works fine, but attempting to rm causes a panic.
config and dmesg (of a non-panicking kernel) are attached, panic message
and gdb stuff below... Hope it's enough info to get a fix in the works!
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x4
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc019249c
stack pointer = 0x10:0xdb467b4c
frame pointer = 0x10:0xdb467b50
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 = 145 (rm)
panic: from debugger
#0 0xc019614b in doadump ()
#1 0xc01965db in boot (howto=260)
#2 0xc01967fb in panic ()
#3 0xc0139452 in db_panic ()
#4 0xc01393d2 in db_command (last_cmdp=0xc02fd2e0, cmd_table=0xc02fd100,
aux_cmd_tablep=0xc02f4c7c, aux_cmd_tablep_end=0xc02f4c80)
#5 0xc01394e6 in db_command_loop ()
#6 0xc013c07a in db_trap (type=12, code=0) at ../../../ddb/db_trap.c:76
#7 0xc0298dfe in kdb_trap (type=12, code=0, regs=0xdb467b0c)
at ../../../i386/i386/db_interface.c:214
#8 0xc02a9153 in trap_fatal (frame=0xdb467b0c, eva=4)
#9 0xc02a8e62 in trap_pfault (frame=0xdb467b0c, usermode=0, eva=4)
#10 0xc02a885a in trap (frame=
{tf_fs = -1013055464, tf_es = 196624, tf_ds = 16, tf_edi = -1, tf_esi
= -1012546560, tf_ebp = -616137904, tf_isp = -616137928, tf_ebx = 0, tf_edx
= 0, tf_ecx = -1012854016, tf_eax = 1, tf_trapno = 12, tf_err = 0, tf_eip =
-1072094052, tf_cs = 8, tf_eflags = 66050, tf_esp = -1012854016, tf_ss =
-616137864})at ../../../i386/i386/trap.c:659
--- begin interesting stuff ---
#11 0xc019249c in suser_cred (cred=0x0, flag=0)
#12 0xc025dab5 in chkiq (ip=0xc3a5c400, change=4294967295, cred=0x0,
flags=0)#13 0xc025b57f in ufs_inactive (ap=0xdb467be0)
at ../../../ufs/ufs/ufs_inode.c:132
#14 0xc0263a08 in ufs_vnoperate (ap=0xdb467be0)
#15 0xc01e01e5 in vput (vp=0xc3a59c00)
#16 0xc01e77c4 in unlink (td=0xc393c41c, uap=0xdb467d10)
#17 0xc02a948a in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077936696, tf_esi = 0,
tf_ebp = -1077936776, tf_isp = -616137356, tf_ebx = -1077936553, tf_edx =
-1077936508, tf_ecx = 47, tf_eax = 10, tf_trapno = 12, tf_err = 2, tf_eip =
134524795, tf_cs = 31, tf_eflags = 582, tf_esp = -1077936916, tf_ss = 47})
#18 0xc029a57d in syscall_with_err_pushed () at {standard input}:128
#19 0x0804839a in ?? ()
#20 0x08048145 in ?? ()
CATALYST
Description: Binary data
dmesg
Description: Binary data
Re: UFS2 related message?
By chance, is this a new installation? A month or so ago I was adding a drive to a -current system and I discovered that the newfs defaults were setting insanely large block/fragment/inode sizes and I could not even do a 'make world' on that partition. Had to completely reinstall and override the defaults. On Sat, 22 Jun 2002, Munehiro Matsuda wrote: Hello all, After the import of UFS2 patch into -current, I get the following messages. pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes pid 397 (perl), uid 123 inumber 682496 on /home: out of inodes Is it related to UFS2 by anyway? FYI, here's what got with my disks. % df -i Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on /dev/ad0s2a254063 91341 14239739%2615 608714% / devfs 1 1 0 100% 0 0 100% /dev /dev/ad0s3e 7185161 4473874 213647568% 227116 1574354 13% /home /dev/ad0s2f 2787666 1668475 89617865% 176288 522078 25% /usr /dev/ad0s2e254063 10456 223282 4%1653 618333% /var procfs 4 4 0 100% 1 0 100% /proc linprocfs 4 4 0 100% 1 0 100% /usr/compat/linux/proc /dev/ad0s13663652 2542176 112147669% 0 0 100% /dos % Thanks in advance, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MySQL 3.23.51 Error
I get this same error, and was able to fix it by disabling tcp wrappers in the config (this is a non-production system), and adding -lstdc++ to the libraries for linking. Strange that you were able to compile .49, I couldn't build it without massaging the code either. As another data point, I was able to build .51 on my -stable box. On Friday 21 June 2002 06:12 am, you wrote: Hi! On Thu, Jun 20, 2002 at 09:54:23AM -0800, Beech Rintoul wrote: Compile of mysql323 server fails with the following: cc -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME=\/usr/local\ -DDATADIR=\/var/db/mysql\ -DSHAREDIR=\/usr/local/share/mysql\ -DHAVE_CONFIG_H -I../bdb/build_unix -I../innobase/include -I./../include -I./../regex -I. -I../include -I.. -I.-DDBUG_OFF -O -pipe -felide-constructors -fno-rtti -fno-exceptions -fno-implicit-templates -fno-exceptions -fno-rtti -DMYSQLD_NET_RETRY_COUNT=100 -c mysqld.cc /usr/include/tcpd.h: In function `void* handle_connections_sockets(void*)': /usr/include/tcpd.h:137: too many arguments to function `void sock_host()' mysqld.cc:2428: at this point in file /usr/include/tcpd.h:75: too many arguments to function `int hosts_access()' mysqld.cc:2429: at this point in file /usr/include/tcpd.h:130: too many arguments to function `char* eval_client()' mysqld.cc:2437: at this point in file *** Error code 1 Stop in /usr/ports/databases/mysql323-server/work/mysql-3.23.51/sql. *** Error code 1 uname -a FreeBSD nova.anchoragerescue.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Regards Dirk Jun 20 02:06:12 AKDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA i386 Did version 3.23.49 compile on your system? Yes it did, that's what I upgraded from. This seems to be an issue with -current only. The same code compiled ok on two of my 4.6 Boxes. Beech -- --- Beech Rintoul - SysAdmin - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
C++ problems
I cleaned up my /usr/lib and /usr/include file of stale headers/libs left after the libstdc++ upgrade (maybe this should be in src/UPDATING??), and now any port that uses C++ autoconf fails to configure... checking if STL implementation is SGI like... no checking if STL implementation is HP like... no configure: error: no known STL type found - did you forget to install libstdc++-devel ? However, the configure script WILL succeed if I manually run configure with the same options (grabbed from ps). Weird... Anyone have some thoughts on this? It's a little annoying :) -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI problems on -current
I am running -current with NEWCARD on a thinkpad x20. The system has a builtin 3com ethernet card that attaches on the xl driver, and I have a wavelan card. Neither network card functions when the ACPI module is loaded, but work perfectly with no acpi. Anyone have any ideas what the problem may be? The error messages I see from the wavelan card seem to indicate an interrupt problem, but it gets the same irq w/o the module and works fine. WNM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI problems on -current
I placed the verbose boot dmesg's at www.chemikals.org/acpi and www.chemikals.org/no-acpi Thanks in advance for any help rendered! On Tue, 20 Nov 2001, Warner Losh wrote: In message [EMAIL PROTECTED] Wesley Morgan writes: : Anyone have any ideas what the problem may be? The error messages I see : from the wavelan card seem to indicate an interrupt problem, but it gets : the same irq w/o the module and works fine. With all due respect, this report is too vague to do anything useful with. At the very least, we need the error messages, and likely a full boot -v dmesg to even begin to track down the problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-mobile in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Accton EN2242 MiniPCI 10/100 (dc0) not working.
My Xircom (cardbus) nic is nonfunctional in -current as well, however it hangs the system when dhclient tries to set it up. On Thu, 18 Oct 2001, Trent Nelson wrote: I have a Sharp AR50 laptop. It has an Accton EN2242 MiniPCI 10/100 NIC that's producing the following: pci0: bridge, PCI-unknown at device 7.3 (no driver attached) dc0: Accton EN2242 MiniPCI 10/100BaseTX irq 11 at device 11.0 on pci0 dc0: couldn't map ports/memory device_probe_and_attach: dc0 attach returned 6 I've read through the mailing lists and one other person reported similar failure not quite on the same lines back in March 2000. I don't have any PnP BIOS options -- so how long am I going to be out of luck for? What's actually required to get this working? If I aquire a PCMCIA NIC in the interim, am I likely to have similar problems? Trent. % uname -a FreeBSD current.ar50.udt 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Wed Oct 17 12:13:59 WST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/current_17Oct2001 i386 % pciconf -lv hostb0@pci0:0:0:class=0x06 card=0x chip=0x71908086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82443BX/ZX 440BX/ZX AGPset Host Bridge' class= bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x chip=0x71918086 rev=0x03 hdr=0x01 vendor = 'Intel Corporation' device = '82443BX/ZX 440BX/ZX AGPset PCI-to-PCI bridge' class= bridge subclass = PCI-PCI isab0@pci0:7:0: class=0x068000 card=0x chip=0x71108086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB PIIX4 ISA Bridge' class= bridge subclass = PCI-unknown atapci0@pci0:7:1: class=0x010180 card=0x chip=0x71118086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB PIIX4 IDE Controller' class= mass storage subclass = ATA none0@pci0:7:2: class=0x0c0300 card=0x chip=0x71128086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB PIIX4 USB Interface' class= serial bus subclass = USB none1@pci0:7:3: class=0x068000 card=0x chip=0x71138086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB PIIX4 Power Management Controller' class= bridge subclass = PCI-unknown none2@pci0:11:0:class=0x02 card=0x00121468 chip=0x12161113 rev=0x11 hdr=0x00 vendor = 'Accton Technology Corporation' class= network subclass = ethernet none3@pci0:12:0:class=0x060700 card=0x101913bd chip=0xac42104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments' device = 'PCI4451 PC card CardBus Controller' class= bridge subclass = PCI-CardBus none4@pci0:12:1:class=0x060700 card=0x101913bd chip=0xac42104c rev=0x00 hdr=0x02 none5@pci0:12:2:class=0x0c0010 card=0x101913bd chip=0x8027104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments' class= serial bus subclass = FireWire none6@pci0:14:0:class=0x040100 card=0x101913bd chip=0x1988125d rev=0x12 hdr=0x00 vendor = 'ESS Technology' device = 'ES1989 Allegro-1 Audiodrive' class= multimedia subclass = audio none7@pci0:14:1:class=0x078000 card=0x101913bd chip=0x1989125d rev=0x12 hdr=0x00 vendor = 'ESS Technology' device = 'ES1989 Allegro-1.COMM ES56CVM-PI PCI Voice+Fax Modem' class= simple comms none8@pci1:0:0: class=0x03 card=0x101913bd chip=0x4c4d1002 rev=0x64 hdr=0x00 vendor = 'ATI Technologies' device = 'Rage P/M Mobility AGP 2x' class= display subclass = VGA % dmesg Copyright (c) 1992-2001 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 5.0-CURRENT #1: Wed Oct 17 12:13:59 WST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/current_17Oct2001 Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 846328227 Hz CPU: Pentium III/Pentium III Xeon/Celeron (846.33-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA T,PSE36,MMX,FXSR,SSE real memory = 268369920 (262080K bytes) avail memory = 256413696 (250404K bytes) Preloaded elf kernel /boot/kernel/kernel at 0xc03a8000. Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf50 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xfcf0-0xfcff
Re: ACPI??? was - Re: -current TCP performance hosed?
FYI -- this has happened on my laptop (Toshiba Tecra 8000) ever since the ACPI was first introduced (months and months ago) On Fri, 14 Sep 2001, Mike Smith wrote: It seems that, on Fri, Sep 14, 2001 at 03:18:47PM -0700, in message [EMAIL PROTECTED], Mike Smith wrote: Nope, no debug options, but I am getting loads of microuptime() went backwards (29804.3839847 - 29804.925730) ALi chipset? Try turning off the ACPI timer if you haven't already; set debug.acpi.disable=timer at the loader prompt. If this works, please let me know (with ACPI in the subject line so I don't miss it). Tried that, also tried set hint.acpi.0.disable=1 - neither had any effect. Can you explicitly disable the ACPI module? unset acpi_load at the loader prompt. If it still happens with that, then something else is b0rked and I can stop panicking. 8) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
removal of diskcheckd.conf breaks mergemaster
Subject says it all. /usr/src/etc/Makefile still refers to diskcheckd.conf... -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Sound broken on -current again...
My sound is broken as well. On both an SBLIVE card and a Yamaha OPL-SA chipset. The time frame for the breakage is definitely within the last 10 days as my previous world/kernel was from 8/5 and the current world is 8/16. On Sun, 19 Aug 2001, Maxim Sobolev wrote: On Sat, 18 Aug 2001 21:10:40 -0500, Daniel M . Kurry wrote: On Wed, Aug 15, 2001 at 07:01:46PM +0200, some SMTP stream spewed forth: One gets the first DMA buffer full, then the process hangs... Due to the lack of replies, I'll go ahead. I am seeing sound breakage also. My card is a Creative Labs SoundBlaster Live!. xmms will play a short (less than a second) spurt of audio and then stop responding. mpg123 will not play (any audio to the speakers) at all. I ran a buildworld today which apparently broke it. That puts the breakage between today and sometime less than 2 months ago. (I really cannot be more specific.) Suggestions gladly welcomed. -Søren The same is here (OPL3-SA driver on Toshiba Satellite Pro 445CDX notebook). I found that after reverting the following deltas (jhb's 10 August commit) sound starts working again: src/sys/i386/i386/sys_machdep.c,v 1.60 src/sys/i386/i386/trap.c,v 1.198 src/sys/i386/include/cpu.h,v 1.63 src/sys/i386/isa/ipl.s,v 1.51 src/sys/i386/isa/npx.c,v 1.108 src/sys/kern/kern_clock.c,v 1.128 src/sys/kern/kern_intr.c,v 1.61 src/sys/kern/kern_lock.c,v 1.47 src/sys/kern/kern_synch.c,v 1.155 src/sys/kern/kern_timeout.c,v 1.69 src/sys/kern/subr_prof.c,v 1.47 src/sys/kern/subr_smp.c,v 1.157 src/sys/kern/subr_trap.c,v 1.197 src/sys/kern/subr_witness.c,v 1.82 src/sys/posix4/ksched.c,v 1.14 src/sys/sys/callout.h,v 1.21 src/sys/sys/proc.h,v 1.174 src/sys/sys/resourcevar.h,v 1.23 Please fix. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
fstab weirdness / UPDATING
My understanding is that there have been some changes regarding fstab, fsck, etc. recently. On boot, I find that only first two filesystems are listed as "clean", and on a recent un-clean shutdown only the first two were properly fsck'd (although the system was allowed to boot and mount read-write the unclean filesystems). I can only assume that some change to the boot procedure was made, since I made no changes. Are we going to see an UPDATING entry regarding this? I can't seem to find any explicit instructions in the mailing lists either. It worries me a bit when unclean filesystems are being mounted rw. WNM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dirty buffers on reboot again?
Not here. Just using ad and friends. On Fri, 23 Feb 2001, Matthew Jacob wrote: Hmm... Good question. On Fri, 23 Feb 2001, David O'Brien wrote: On Thu, Feb 22, 2001 at 03:20:10PM -0800, Matthew Jacob wrote: login: (da0:ahc0:0:0:0): tagged openings now 16 ... syncing disks... 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up on 3 buffers ... I'm seeing a lot of this again. Anyone else? Yep. ahc controller also. By chance is that the commonality to this problem? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
name resolution problems
Since the big shake-up with -current, I find that mozilla and galeon can no longer function (both up to date), but lynx has no problems. Mozilla seems stuck resolving hostnames, yet tcpdump shows no traffic and truss indicates that it is simply looping around a poll(). The biggest difference between lynx and mozilla in terms of name resolution is that mozilla is linked against libc_r... Could there be some problem here? Is anyone else seeing this? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DEVFS
With devfs "default" in -current, I have a question about permissions. I know that rc.devfs will set up custom permissions at boot... But what about a device that detaches? When you re-attach, it goes back to the default permissions. This is a bit annoying; is there a workaround for it? Should this be handled by something that does the re-attaching? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PROCTREE_LOCK() vs. gdb hang
On Sun, 31 Dec 2000, User Sja wrote: I don't really know my way around the kernel so I'm just guessing here: Is there a proctree lock release operation missing in kern_sig.c, function issignal()? There seems to be one lock operation more than there are release operations. I tried putting one in and now gdb doesn't hang the whole machine (at least as easily as before.) I don't know anything about the kernel either, but I locked up in gdb the other day and every process eventually became stuck in proctree... Just my $0.02US -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PalmPilot emulators don't work on CURRENT
On Fri, 29 Dec 2000, Juriy Goloveshkin wrote: Hello, Can anybody run any PalmPilot emulator on CURRENT? pose and xcopilot don't work. Nope. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: PalmPilot emulators don't work on CURRENT
On Fri, 29 Dec 2000, Daniel O'Connor wrote: On 29-Dec-00 Juriy Goloveshkin wrote: Can anybody run any PalmPilot emulator on CURRENT? pose and xcopilot don't work. Perhaps if you submitted a bug report worthy of the name someone might be able to help. Does it core? panic the machine? Run but not work as intended? Have you tried recompiling the application and dependancies? It cores, in a getsockname() call from the fltk libraries. I dropped a note to the port maintainer a couple weeks ago and never heard anything. The same problem exists if you build independent of ports. It could be an issue with the fltk port though... -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI says: too many dependant configs(?)
Since we are on the subject of ACPI, it is working great except for one thing, it can't attach my sound card to the pcm device (does that sound correct?). It definitely sees it: unknown: YMH0021 can't assign resources Looks like the yamaha chipset to me. If I could get sound working, I'd definitely be using acpica all the time. I think the thermal management has been improved since the last time I tried it -- it kept the temp 356K. Is there any way to set a temperature to be maintained? Or some way to actually query the current temperature? (lmmon doesnt work) -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
this just in: kernel broken
Source from latest cvs. World builds A-OK, kernel bombs, looks like it needs to include sys/lock.h: cc -c -O -pipe -mpentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 ../../kern/kern_synch.c ../../kern/kern_synch.c: In function `schedcpu': ../../kern/kern_synch.c:289: warning: implicit declaration of function `lockmgr' ../../kern/kern_synch.c:289: `LK_SHARED' undeclared (first use in this function) ../../kern/kern_synch.c:289: (Each undeclared identifier is reported only once ../../kern/kern_synch.c:289: for each function it appears in.) ../../kern/kern_synch.c:349: `LK_RELEASE' undeclared (first use in this function) *** Error code 1 -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
linux emulation
Anyone having problems with the linuxulator the past couple days? Module fails to load for me, with this message: link_elf: symbol makebdev undefined -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new pccard beep code not quite right
While I'm sure the new beeps for pccard insert/remove are quite charming on some laptops, they are a bit broken on mine... The new beeps are nothing more than a barely audible click or two... But the real problem is that if the speaker wants to beep afterwards, my ears are assaulted by not one but a nearly endless stream of beeps. They continue for different lengths depending on when they begin... They seem to stop when a card is identified though -- but it only requires another beep to set it off again, and they continue until a card is either ejected or another is identified (they don't stop if I break to ddb). Any debugging info needed will be happily provided! -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
On Thu, 26 Oct 2000, Poul-Henning Kamp wrote: I don't really care that much how good my random bits are right after boot, but I do care about my machine coming up quickly. I don't know about that, look at your boot logs: Oct 26 17:32:19 catalyst /boot/kernel/kernel: Copyright (c) 1992-2000 The FreeBSD Project. Oct 26 17:32:19 catalyst /boot/kernel/kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 26 17:32:23 catalyst sshd[193]: Generating 768 bit RSA key. Oct 26 17:32:23 catalyst sshd[193]: RSA key generation complete. Those times aren't correct I'm sure, but if I can't get enough entropy for a 768 bit key _very soon_ after boot, we could have a problem. Somehow, I think everyone should care about that. Add a /etc/rc.conf knob which says wait_until_entropy_collected=YES Why not be secure by default and have i_dont_care_about_entropy=NO -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
I'm not knocking anyone or any code, especially considering this IS -current... BUT... I don't need to read the code to know that I am seeing the same fortunes on first login after reboot more often than I can attribute to random chance. Maybe nanotime is being harvested, but it seems that there is a time lag between system startup and reaching a state of "true pseudo-entropy". Also, every reboot has entropy caching failing to work. I don't know if this is a product of the broken reseeding or what, because the /etc/rc files seem to be fine. On Wed, 25 Oct 2000, Mark Murray wrote: 2) Reseeding state may not preserve across the boot due to various reasons like panic, etc. Since _time_ is ignored, all other data /etc/rc tries to collect now can be non-random _easily_! Unless _time_ will be used, /dev/random is plain unusable for production usage. Andrey, read the code; nanotime is all over the harvested entropy. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
Ok, I rebooted once and the entropy caching did not work. Changed entropy_file to point to /var/db/entropy, rebooted. Did not work. Commented out the entropy_file setting and rebooted... And it worked. Rebooted 5 times, worked every time. Laptop is working now. cvsup'd my desktop, ran mergemaster and it worked for 3 reboots... Now, the problem I am seeing is that not only do I get the same fortunes between reboots, but it is _always_ the same one: "Be ALERT (the world needs more lerts" has shown up first nearly every time for the past week. Waiting a few minutes to log in has no effect... Still the same one. Now I'm no expert on randomness and the like, but surely this can't be very random. I'll be eating my words tonight, but I swear it wasn't working for me :) (and yes i had the latest rc files). On Wed, 25 Oct 2000, Mark Murray wrote: I am not seeing this, and I am unable to reproduce it. i terefore need better info than "it is so" to do anything about it. Please get a complete log of the boot process (put a set -x in /etc/rc while you are about it) and get that over to me. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: savecore cannot find device?
Mine has been saying something similar for a week or so now. I just figured it was me and ignored it. Manually running savecore gives no error and works fine. On Wed, 11 Oct 2000, Jun Kuriyama wrote: My boot message of today said: Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No such file or directory And swap entry in /etc/fstab is: /dev/ad0s1b noneswapsw 0 0 This is non-DEVFS environment. Am I missing some point of updating? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make installkernel broken by recent manpage changes
Since we are on the subject of installing kernels, i noticed last night that the target "make kernel-install" (not part of world) will cause your modules to be moved into modules.old. It looks like the routine that moved the kernel - kernel.old was not changed or something like that. Or maybe this is what was intended... But it surely was not what I expected. Shouldnt the tree be pushed over to "old" under different circumstances (like a new module installation, and of course for the install target)? On Sat, 7 Oct 2000, Tony Fleisher wrote: I just ran through this myself trying to update to newest -current. I am not exactly sure what caused the breakage (perhaps some changes inthe share/mk/* files?), nor what the "proper" fix is, however I was able to get the kernel to install properly by adding NOMANCOMPRESS=true in the following Makefiles: -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcmcia and ed
Some recent change to either the ed device or pccard support is making the kernel hiccup on my ethernet card: ed0 at port 0x300-0x31f irq 10 slot 1 on pccard1 ed0: address 00:e0:98:88:db:09, type Linksys (16 bit) module_register: module isa/ed already exists! Module isa/ed failed to register: 17 module_register: module isa/ed already exists! Module isa/ed failed to register: 17 module_register: module pccard/ed already exists! Module pccard/ed failed to register: 17 module_register: module pci/ed already exists! Module pci/ed failed to register: 17 the driver is compiled in the kernel, but it is loading the KLD anyway. Everything still functions, however. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in ufs_extattr_uepm_destroy()
I'm getting a panic in ufs_extattr_uepm_destroy() because in ffs_vfsops.c it is being called (line 788) with ump NULL: ufs_extattr_uepm_destroy(ump-um_extattr); Of course disabling FFS_EXTATTR gets rid of this:) -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA DMA support is broken
I'm seeing the same problem on my Tecra 8000: atapci0: Intel PIIX4 ATA33 controller port 0xfe60-0xfe6f at device 5.1 on pci0 atapci0: Busmastering DMA enabled ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ata1-master: identify retries exceeded ad0: 6194MB IBM-DBCA-206480 [13424/15/63] at ata0-master BIOSPIO Before adding the hints to /boot/device.hints, only the atapci0 was detected. Works fine with the hints though. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in kernel configuration menu
When the kernel configuration menu comes up with the three possible selections, pressing ctrl-alt-del ends up with this message: panic: spin lock (null) held by 0x0 for 5 seconds sounds like one that should be an easy fix -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sound breakage
Something committed in the last 16 hours or so (seems to have) hosed mp3 playback on my laptop (OPL-SA3)... It stutters on the first 1/2 second of the mp3 over and over. The cvs-all archives for last week look like they are in limbo right now or else I would look for a specific commit. Is anyone else seeing this breakage? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PRE_SMPNG snap
On Sat, 16 Sep 2000, John Baldwin wrote: Err, AFAIK, the only instability atm is that under heavy load some ahc controllers seem to hang (or possibly the ahc driver is getting out of sorts and hanging.) However, the problem is not so bad that you can't build world in at most 2 boots, and it also seems to only manifest itself on SMP machines AFAIK. The only other bugs at this point are in cosmetic statistics, and in catching the alpha arch up to the x86 arch. If you have other stability problems we'd appreciate some bug reports. :-P Are there any filesystem-hosing issues with the "instability"? I'll try anything if my FS is in no danger :) -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP mega-commit complete
On Wed, 6 Sep 2000, Jason Evans wrote: A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches have now been committed. Is it safe to follow src-sys from PRE_SMPNG and everything else as -current? -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -current Performance Drop?
Actually in the past week or two I have seen a make buildworld drop from 205-210 minutes to 180-190 minutes. But I would be more inclined to attribute that to changes in the source tree itself, not performance. On Tue, 11 Jul 2000, Thomas D. Dean wrote: I don't know if this belongs in -current or -smp, so here goes. I am running -current SMP, cvsup, etc. late last night PDT. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Jul 11 09:53:15 PDT 2000 \ tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 I have been using 'make world' as a stability/performance indicator. The stability has been good. I have had no recent panics, etc., during 'make world'. I choose the times to update carefully. Good work core team. I seem to see somewhat of a performance drop in the past week. I save the output of 'make world' I know this is not a benchmark nor a very accurate indicator. However, I believe 'make world' is a pretty good torque tool for a lightly loaded, interactive, 'play' system. And, disk I/O, compiling and executing user code is what interactive users do. If 'make world' puts out approximately the same number of lines, I think it is doing about the same amount of work. I see an increase in 'make world' time over the past week, or so. The number of lines of output has gone up slightly. The time elapsed has gone up more. # world_time.sh Make World Statistics -current SMP, 2xP133, 96MB RAM, IBM Superstor 9G disk. Lines is the number of lines of output produced by 'make world'. Date Lines Make Time Lines/Minute - - 19991018 35281 6h40m16s 88.20 2401 39490 7h56m18s 82.96 2402 39427 7h28m41s 88.01 2412 39404 7h10m21s 91.64 2621 38679 7h20m20s 87.91 2630 39530 7h56m20s 83.05 2709 39679 8h40m28s 76.31 2710 39568 9h13m46s 71.55 2711 41178 9h22m05s 73.27 tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
