Re: 40% slowdown with dynamic /bin/sh
./Scott Long wrote: Please, read : http://www.netmeister.org/news/learn2quote.html > Also, I'm really starting to resent you using the FreeBSD mailing > lists as an advocacy channel for DragonFly. I fail to see how FreeBSD > 4.x and DFBSD relate to FreeBSD 5-current, which is the overall topic > of this mailing list at the moment. This comment is so ridiculous I can't resist. He has explained a very clever and nice solution for the problem, rather than bitching about it which is what the 95% of the thread is about. By bashing him, not only you're doing a great job for inter-camp relations, you're making the absurd assumption that such a solution (once/if it appears in DragonFly) cannot/will not be easily ported to FreeBSD. Cheers, -- Miguel Mendez <[EMAIL PROTECTED]> http://www.energyhq.es.eu.org PGP Key: 0xDC8514F1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Instant panic when trying to unload nvidia.ko
Hi, I'm running -CURRENT from yesterday. In a futile attempt to make some use of my rusty RivaTNT card, I installed the nvidia kernel port, but it seems to be doing some weird stuff with memory. This appeared in the messages log: ... Oct 28 16:04:33 scienide kernel: malloc() of "32" with the following non-sleepable locks held: Oct 28 16:04:33 scienide kernel: exclusive sleep mutex dev.mtx_api r = 0 (0xc39d478c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidi a_subr.c:753 Oct 28 16:04:33 scienide kernel: malloc() of "32" with the following non-sleepable locks held: Oct 28 16:04:33 scienide kernel: exclusive sleep mutex dev.mtx_api r = 0 (0xc39d478c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidi a_subr.c:753 Oct 28 16:04:33 scienide kernel: malloc() of "4096" with the following non-sleepable locks held: Oct 28 16:04:33 scienide kernel: exclusive sleep mutex dev.mtx_api r = 0 (0xc39d478c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidi a_subr.c:753 ... And now, the fun part. After booting, if I try to unload the module I get the attached panic. I know the nvidia kernel is proprietary code and yada yada, but the problem seems to be in the open source part of the code, so I have some hope I can get to fix it with a little help :-) Cheers, -- Miguel Mendez <[EMAIL PROTECTED]> http://www.energyhq.es.eu.org debug.log Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-beta2 failed upgrade install
On Tue, 03 Jun 2003 23:52:38 +0900 (JST)
Masachika ISHIZUKA <[EMAIL PROTECTED]> wrote:
> Are there anybody who can upgrade to 5.1-RC1 successfully with Xeon
> or Pentium4 ? I can newly install 5.1-RC1, but I can not upgrade from
> 5.1-BETA or 5.1-RC1 to 5.1-RC1 with Xeon or Pentium4 without panics.
Here, here. I was doing installworld and got a double fault. After
rebooting with the new kernel (5.1-RC1) and running fsck it installed
fine. Funnyly enough, make was gone, so I had to run the one in
/usr/obj. Otherwise seems to work fine so far.
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
EnergyHQ :: http://www.energyhq.tk
Tired of Spam? -> http://www.trustic.com
pgp0.pgp
Description: PGP signature
Re: Anyone working on fsck?
On Tue, 18 Mar 2003 10:59:14 +0100 [EMAIL PROTECTED] (Dag-Erling Smørgrav) wrote: Howdy, > Let's rather work on getting a working log-structured filesystem > committed so we don't *need* fsck for filesystems that large. Rather than reinventing the wheel, how about porting NetBSD's LFS to FreeBSD? Granted it's not 100% reliable yet, but it's improving. I'd rather have that than wait for JFS4BSD to be ready. In fact, I'd volunteer to work with my (limited) knowledge. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! Tired of Spam? -> http://www.trustic.com pgp0.pgp Description: PGP signature
Re: Anyone working on fsck?
On Mon, 17 Mar 2003 12:22:33 -0800 (PST) Julian Elischer <[EMAIL PROTECTED]> wrote: Howdy, > It wouldn;t be super fast but at least it COULD be used to check a > 30TB array, > where the in-memory version would beed a process VM space > of 24MB which is clearly > impossible on a x86. I'm sure most of us have computers with more than 24MB :-P, sorry couldn't resist. It's an interesting problem anyway, does anyone have insight on how other OSs and FS handle these kind of problems? e.g. Solaris with vxfs or Linux with XFS/JFS/this week's FS. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! Tired of Spam? -> http://www.trustic.com pgp0.pgp Description: PGP signature
Re: printf....!
On Sat, 8 Feb 2003 16:23:21 -0600 David Leimbach <[EMAIL PROTECTED]> wrote: Howdy. > Isn't it ultimately interrupt 08 on the PC with an index in the EAX > register for the write "subroutine"? > > I am pretty sure that's correct. I might have the interrupt value > wrong though. s/08/0x80/ :-) Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! msg52019/pgp0.pgp Description: PGP signature
Re: 5.0 without swap
On Sat, 11 Jan 2003 01:58:31 -0800 "Lucky Green" <[EMAIL PROTECTED]> wrote: Hi, > I am about to set up a FreeBSD 5.0 machine without a swap partition. > The server has 1GB of RAM. Are there any caveats that I need to > consider during installation or configuration? Having no swap will prevent you from getting crashdumps in case of panic which, if you run 5.0, is not that unusual. Besides these days harddrives cost $1/GB, so why not setup the swap partition anyway? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! msg49986/pgp0.pgp Description: PGP signature
Re: buildworld fails building boot2
On Tue, 31 Dec 2002 09:33:15 -0500 Matt Emmerton <[EMAIL PROTECTED]> wrote: > I just cvsup'd the latest -CURRENT sources (8 hours ago) and I'm having trouble >doing a buildworld. cvsup again, I just build world and it works :) flynn@christine# uname -a FreeBSD christine.energyhq.tk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Dec 31 14:56:19 CET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CHRISTINE i386 Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP kernel on 5.0-release ISO's?
On Mon, 16 Dec 2002 14:44:57 -0500 Garance A Drosihn <[EMAIL PROTECTED]> wrote: Hi, > ISO's? Do people think that would be a useful item to include? Yes and no, let me explain. The first thing I do just after I install FreBSD on a box (given it has enough cpu power) is rebuild world and kernel after tweaking /etc/make.conf. So I set the appropriate CPUTYPE flags and rebuild everything. As long as there's enough spare space to include an extra SMP-enabled kernel, I'm all for it, but my wild guess is that most people running SMP systems either rebuild their kernel for SMP + custom settings and/or rebuild world after install. > I was thinking of just having a /boot/kernel-smp directory, for > people to load in if they want to try it. I just want it on > the CD's, it doesn't need to be automatically installed. If there's free space on the first CD, I'd say go for it. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfw userland breaks again.
On Sun, 15 Dec 2002 10:26:22 -0800 (PST) Matthew Dillon <[EMAIL PROTECTED]> wrote: Hi, must...resist... > So don't give me this bullshit about the patch being a security > issue. YOU KNOW IT ISN'T. No, Warner has a point, that patch is simply bandaid (albeit a good one). > Now you are forcing me to go to core. It's absolutely ridiculous > and you know it. Goddamn it, next time I won't even bother > posting if all I get is this sort of crap. I know I'm gonna get flamed for this, but you know what's ridiculous? All the flamage you've brought up on the issue. You're a great hacker Matt, just keep it easy and don't take it so personal. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current issues
On 10 Dec 2002 16:02:14 -0500 Joe Marcus Clarke <[EMAIL PROTECTED]> wrote: Hi, > Evo isn't a C++ application. I haven't seen any build logs for it, > either. I'm doing a build on my i386 machine now just to be sure. I built it a couple of days ago on my 5.0-RC system, works okay. flynn@christine# pkg_info|grep evo evolution-1.2.0_2 An integrated mail, calendar and address book distributed s gal-0.21A collection of widgets taken from GNOME gnumeric and evolu flynn@christine# uname -a FreeBSD christine.energyhq.tk 5.0-RC FreeBSD 5.0-RC #0: Sat Dec 7 22:56:40 CET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CHRISTINE i386 Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: '-ax' option in gcc
On Sat, 23 Nov 2002 18:21:09 +0100 Jens Rehsack <[EMAIL PROTECTED]> wrote: Hi, > The "-ax" option generates code for profiling. The "-ax" options > doesn't appears in the current info documentation, which is an actual > one (AFAIK). So I assume, "-ax" is not supported anymore. So the man page needs to be updated then :) > You may also read http://gcc.gnu.org/ for details 'bout the new > compiler and http://gcc.gnu.org/news/profiledriven.html for > information about the new "Infrastructure for Profile Driven > Optimizations". Yes, thanks for the info, FWIW I think it's quite against POLA to remove an option yet keep it documented in the man page :) Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
'-ax' option in gcc
Hi, subject says it all...
A -CURRENT system as of 11/15:
flynn@christine# cat hello.c
#include
#include
int main(int argc, char **argv)
{
printf("Hello, foo!\n");
exit(0);
}
flynn@christine# env CFLAGS="-pg -ax" make hello
cc -pg -ax -march=pentiumpro hello.c -o hello
cc1: unrecognized option `-ax'
*** Error code 1
Stop in /usr/home/flynn.
Is the -ax option deprecated? It's still present in the man page. No
problem building such program in a -STABLE box with 2.95
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
Of course it runs NetBSD!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Booting from floppies
On Tue, 19 Nov 2002 12:42:18 +0100 "Willem Jan Withagen" <[EMAIL PROTECTED]> wrote: Hi, > My guess is that nobody use 1.44 floppies any more to boot. > But when I wanted to fire up an old box which only has a floppy > it did not grock the msfroot floppy: > > '/mfsroot not found' I just had that problem last week booting a -STABLE jpsnap. Having had bad experiences with floppy disks reliability I just dd'ed it again, just in case. The second time it worked. Could be a faulty disk. FWIW I think a lot of people use boot floppies to do net installs. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk Of course it runs NetBSD! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Is RAIDframe currently usable?
Hi,
Yesterday I installed a jpsnap (FreeBSD christine.energyhq.tk
5.0-CURRENT-20021115-JPSNAP i386), and tried to setup a RAID0 config
with two disks. raidctl -C goes fine, so does -I and -iv. Then fdisk'ed
and disklabelled. But when I tried to newfs the newly created partition
I started getting a bunch of errors like this:
---
Nov 16 00:04:59 christine kernel: raid0: node (R ) returned fail,
rolling backward
Nov 16 00:04:59 christine kernel: raid0: DAG failure: r addr 0x40 (64)
nblk 0x20 (32) buf 0xcdd50ea0
Nov 16 00:04:59 christine kernel: raid0: node (R ) returned fail,
rolling backw byte 76893
---
and so on.
Anyway, the newfs process finishes, then a simple piped tar to move the
old /usr to the RAID partition creates a myriad of those messages, to a
point where the system spends all the time logging those errors and tar
no longer continues.
The system is a dual P3 box, running a slightly modified GENERIC (added
SMP, raidframe and pcm), with INVARIANTS and WITNESS enabled (tried
without them too, no success).
So, any known issues with RAIDframe? I can supply more detailed info if
needed.
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
Of course it runs NetBSD!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: libc size
gt; Knobs are dangerous because you have to test > all of the settings. Knobs are hard, let's go shopping :) Seriously, of course it would need testing, just because it requires work doesn't mean it's not worth doing it. rcNG has been in work for a long time. Is it worth it? Absolutely, try it once and you'll wonder how you could live with the old system, or even with the sysV symlink crazyness. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk NetBSD :: Unix without hype 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 14:19:39 -0500 (EST)
Wesley Morgan <[EMAIL PROTECTED]> wrote:
Hi,
> 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
^^
Why? I'd love to hear some real reasons for this. NetBSD-current has
just gone fully dynamic, let's see how much space that needs...
christine: {16} uname -srnm
NetBSD christine.energyhq.tk 1.6J i386
christine: {17} du -h /bin /sbin /lib
999K/bin
1.7M/sbin
2.0M/lib
/lib keeps the required shared libs for those programs residing in
/[s]bin.
IMHO it would be beneficial to, at least, have the option to build a
fully dynamic system on FreeBSD.
NetBSD now defaults to fully dynamic, but you can set a knob in
/etc/mk.conf to get the old behaviour, how about something like that?
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
NetBSD :: Unix without hype
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org
On Tue, Jun 04, 2002 at 08:39:41AM -0400, Mike wrote:
Hi,
> I have been trying for several days now to access current.freebsd.org so I
> can get the latest -CURRENT snapshot instead of my usual DP1 -> cvsup ->
> buildworld, but I am unable to get in.. Is this not a public server?
There seems to be some problems with that server, you can use
snapshots.jp.freebsd.org in the meantime.
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg39152/pgp0.pgp
Description: PGP signature
Re: Seeking OK to commit KSE MIII
On Thu, May 30, 2002 at 12:43:22AM -0700, Terry Lambert wrote: Hi, > Rules are what seperate us from the apes. And even with them, some computer users still resemble them ;-)º > Apes with Internet access, degrees in CS, a working knowledge of > CVS, an ability to code, mailing list access, and commit bits. Put a large enough number of apes to type in emacs, and you'll eventually end up with a kernel, albeit one with a borken VM subsystem :-) Now to keep on-topic... > Hell, if it makes things easier for Julian to put in more code, > then it's OK with me. He's done the lion's share of work on > getting KSE into FreeBSD so far (IMO). Agreed. I also completely agree with what Matt said in another message about coding style, although it was my idea that it was obvious enough for everybody already, as per style(9) Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38989/pgp0.pgp Description: PGP signature
Re: gcc3.1 problems: undefined reference to `__gxx_personality_v0'
On Wed, May 29, 2002 at 09:27:50AM -0700, Dan Trainor wrote: Hi, > Being that -CURRENT's C++ compiler is b0rked, how long will it be until > it's problems have been resolved? I've seen many problems with it > lately, and it kinda made me worried, almost to the point where I > thought a re-install from the 4.5 release would be appropriate. Short answer, when it's ready. Long answer: David is making a very good job with the update of gcc and related tools, give him the time needed. IMHO, the stuff David is dealing with is total PITA, so be grateful he is doing it, I can't think of a better person to do it right now. -CURRENT is not for the weak, if you run it be ready to find broken stuff, from minor things in buildworld to total breakage, but the handbook already warns you about that, right? :-) FWIW, I've found last weekend's -CURRENT to be perfectly usable, but, as always, YMMV. My 0.02EUR is, if it's not a production box, and you want to play with new stuff and don't mind the (lack of) stability and think you can (possibly) help with debugging, go for -CURRENT, the more people who test it, the better, else keep running -STABLE. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38941/pgp0.pgp Description: PGP signature
Re: gcc3.1 problems: undefined reference to `__gxx_personality_v0'
On Wed, May 29, 2002 at 12:12:02PM -0400, Alexander Kabaev wrote: Hi, > Martin is using GCC 3.1 from ports. It sounds like GCC tries to use some > library left over from the previous version of GCC, which does not > provide this symbol. g++13 -v should tell you what parameters GCC passes > to the linker and what libraries it tries to link. This should be enough > to track down what older library shadows the new one. The usual suspects > are libgcc and libstdc++. Don't quote me on this, but I'm almost sure David made sure that the port's installed gcc compiler used it's own libgcc and libstd++. At least I can recall some comment about it in the port's Makefile. º Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38937/pgp0.pgp Description: PGP signature
Re: gcc3.1 problems: undefined reference to `__gxx_personality_v0'
On Wed, May 29, 2002 at 06:08:58PM +0200, Martin Blapp wrote:
Hi,
> And this doesn't work anymore. I see this with a fresh 3.1 port too now.
Martin, I don't doubt about your answer, but, can you verify you are
indeed using the ports g++ compiler? I can't reproduce the bug here.
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg38935/pgp0.pgp
Description: PGP signature
Re: gcc3.1 problems: undefined reference to `__gxx_personality_v0'
On Wed, May 29, 2002 at 05:56:28PM +0200, Martin Blapp wrote: Hi Martin, > /usr/ports/editors/openoffice/work/oo_1.0_src/config_office/configure:3620: > undefined reference to `__gxx_personality_v0' I've seen this problem too. I don't know if it has been solved, but -CURRENT's C++ compiler has been broken for a while. The workaround has been to install the gcc31 port and use it, e.g make CXX=/usr/local/bin/g++31 Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38932/pgp0.pgp Description: PGP signature
Re: Problems with DP1
On Thu, May 23, 2002 at 09:44:45AM -0400, John Baldwin wrote: Hi again, > Well, maybe. :) If the bug is reproducible, it would be nice to see if the > submitter can reproduce it on current -current. I upgraded this box yesterday: flynn@kajsa# uname -a FreeBSD kajsa.energyhq.tk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri May 24 17:50:00 CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KAJSA i386 I've stress-tested it quite a bit. Built world 3 times, built gnome2 and some other big ports, and so far it's rock solid. I can't reproduce the problem I was having with DP1, so yes, I assume the bug is gone, and this version feels incredibly stable btw :) Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38785/pgp0.pgp Description: PGP signature
Re: Problems with DP1
On Thu, May 23, 2002 at 09:44:45AM -0400, John Baldwin wrote: Hi, > > Oh, good then. My favorite kind of bug: the already-fixed kind :) > > Well, maybe. :) If the bug is reproducible, it would be nice to see if the > submitter can reproduce it on current -current. Fair enough, John, thanks for the info. Like I've said, this is just one of my desktop boxen, so, if you think it can help, I can cvsup to recent -CURRENT and try. My question is, is today's -CURRENT buildable? :-) With the recent gcc31 import by David things are a bit unstable, but I'll know in about 40 mins or so :) /me launches cvsup Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38727/pgp0.pgp Description: PGP signature
Re: Problems with DP1
On Tue, May 21, 2002 at 03:27:46PM -0700, Kris Kennaway wrote: Hi, > That's not actually where the panic is occurring (it's a second panic > caused by the kernel trying to sync disks after it panics the first > time). Please provide a full traceback so it can be investigated. I've attached both a backtrace and my dmesg. Is any extra info needed? Kernel was built from a modified GENERIC with SMP enabled, WITNESS and INVARIANTS disabled, and device pcm. The rest is off the shelf 5.0-DP1 stuff. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD at phsyical address 0x00467000 initial pcb at physical address 0x00378b00 panicstr: bwrite: buffer is not busy??? panic messages: --- panic: setrunnable(2) cpuid = 1; lapic.id = 0100 boot() called on cpu#1 syncing disks... panic: bwrite: buffer is not busy??? cpuid = 1; lapic.id = 0100 boot() called on cpu#1 Uptime: 5h34m33s /dev/vmmon: Module vmmon: unloaded dumping to dev da1s1b, offset 131328 dump 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at ../../../kern/kern_shutdown.c:505 505 if (!dodump) (kgdb) bt #0 dumpsys () at ../../../kern/kern_shutdown.c:505 #1 0xc01d53a8 in boot (howto=260) at ../../../kern/kern_shutdown.c:337 #2 0xc01d5899 in panic (fmt=0xc030292b "bwrite: buffer is not busy???") at ../../../kern/kern_shutdown.c:647 #3 0xc020ade7 in bwrite (bp=0xc9323ae8) at ../../../kern/vfs_bio.c:747 #4 0xc020c1f6 in vfs_bio_awrite (bp=0xc9323ae8) at ../../../kern/vfs_bio.c:1606 #5 0xc01ac878 in spec_fsync (ap=0xd0412ae8) at ../../../fs/specfs/spec_vnops.c:403 #6 0xc01ac435 in spec_vnoperate (ap=0xd0412ae8) at ../../../fs/specfs/spec_vnops.c:121 #7 0xc028a02c in ffs_sync (mp=0xc2cb5800, waitfor=2, cred=0xc102eb80, td=0xc0344920) at vnode_if.h:441 #8 0xc02184a1 in sync (td=0xc0344920, uap=0x0) at ../../../kern/vfs_syscalls.c:669 #9 0xc01d4ff0 in boot (howto=256) at ../../../kern/kern_shutdown.c:246 #10 0xc01d5899 in panic (fmt=0xc02fed34 "setrunnable(2)") at ../../../kern/kern_shutdown.c:647 #11 0xc01dbde2 in setrunnable (td=0xd21952a0) at ../../../kern/kern_synch.c:800 #12 0xc01d8547 in psignal (p=0xd21951a0, sig=23) at ../../../kern/kern_sig.c:1517 #13 0xc01d9ac0 in pgsigio (sigio=0xc306b860, sig=23, checkctty=0) at ../../../kern/kern_sig.c:2095 #14 0xc02049f3 in sowakeup (so=0xd0593fa0, sb=0xd0593ff0) at ../../../kern/uipc_socket2.c:344 #15 0xc0235c99 in tcp_input (m=0xc1039100, off0=20) at ../../../netinet/tcp_input.c:1028 #16 0xc0231700 in ip_input (m=0xc1039100) at ../../../netinet/ip_input.c:845 #17 0xc02317be in ipintr () at ../../../netinet/ip_input.c:870 #18 0xc01c64f4 in swi_net (dummy=0x0) at ../../../kern/kern_intr.c:644 #19 0xc01c6220 in ithread_loop (arg=0xc102e680) at ../../../kern/kern_intr.c:533 #20 0xc01c5432 in fork_exit (callout=0xc01c607c , arg=0xc102e680, frame=0xd0412d48) at ../../../kern/kern_fork.c:799 (kgdb) Copyright (c) 1992-2002 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-DP1 #0: Wed May 15 19:35:03 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/KAJSA Preloaded elf kernel "
Problems with DP1
Hi,
Like I've reported before, I'm getting a panic with DP1 about once a day
in dumpsys () at ../../../kern/kern_shutdown.c:505. My question is, is
there any patch/workaround for this, or am I SOL and the only way is to
upgrade to a more recent -CURRENT? I don't mind if the box goes down
once a day, as is just a desktop, and not doing any production work,
just feel curious.
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg38615/pgp0.pgp
Description: PGP signature
Re: cannot link C++ apps any more (GCC 3.1)
On Tue, May 21, 2002 at 02:26:57PM +0200, Georg-W. Koltermann wrote: Hi, > Is there any estimate to when the new libstdc++ will be in -current? Is > there a port (lang/gcc31 ?) that I should use in the meantime? This is a known issue, David is working on it. I'm not sure about the lang/gcc thing, but system's supplied compiler doesn't work for C++ code. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38614/pgp0.pgp Description: PGP signature
panic in 5.0-DP1
Hi, I get this kind of panic about once a day, some days it doesn't happen, some days it happens twice. -> kajsa# gdb -k /usr/src/sys/i386/compile/KAJSA/kernel.debug vmcore.5 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD at phsyical address 0x00467000 initial pcb at physical address 0x00378b00 panicstr: bwrite: buffer is not busy??? panic messages: --- panic: setrunnable(2) cpuid = 0; lapic.id = boot() called on cpu#0 syncing disks... panic: bwrite: buffer is not busy??? cpuid = 0; lapic.id = boot() called on cpu#0 Uptime: 11h3m27s /dev/vmmon: Module vmmon: unloaded dumping to dev da1s1b, offset 131328 dump 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at ../../../kern/kern_shutdown.c:505 505 if (!dodump) (kgdb) bt #0 dumpsys () at ../../../kern/kern_shutdown.c:505 #1 0xc01d53a8 in boot (howto=260) at ../../../kern/kern_shutdown.c:337 #2 0xc01d5899 in panic (fmt=0xc030292b "bwrite: buffer is not busy???") at ../../../kern/kern_shutdown.c:647 #3 0xc020ade7 in bwrite (bp=0xc9323ae8) at ../../../kern/vfs_bio.c:747 #4 0xc020c1f6 in vfs_bio_awrite (bp=0xc9323ae8) at ../../../kern/vfs_bio.c:1606 #5 0xc01ac878 in spec_fsync (ap=0xd0412ad4) at ../../../fs/specfs/spec_vnops.c:403 #6 0xc01ac435 in spec_vnoperate (ap=0xd0412ad4) at ../../../fs/specfs/spec_vnops.c:121 #7 0xc028a02c in ffs_sync (mp=0xc2cbe800, waitfor=2, cred=0xc102eb80, td=0xc0344920) at vnode_if.h:441 #8 0xc02184a1 in sync (td=0xc0344920, uap=0x0) at ../../../kern/vfs_syscalls.c:669 #9 0xc01d4ff0 in boot (howto=256) at ../../../kern/kern_shutdown.c:246 #10 0xc01d5899 in panic (fmt=0xc02fed34 "setrunnable(2)") at ../../../kern/kern_shutdown.c:647 #11 0xc01dbde2 in setrunnable (td=0xd20eb740) at ../../../kern/kern_synch.c:800 #12 0xc01d8547 in psignal (p=0xd20eb640, sig=23) at ../../../kern/kern_sig.c:1517 #13 0xc01d9ac0 in pgsigio (sigio=0xc317e160, sig=23, checkctty=0) at ../../../kern/kern_sig.c:2095 #14 0xc02049f3 in sowakeup (so=0xd0596fc0, sb=0xd0597010) at ../../../kern/uipc_socket2.c:344 #15 0xc02045fa in soisconnected (so=0xd0596fc0) at ../../../kern/uipc_socket2.c:135 #16 0xc0235e46 in tcp_input (m=0xc103b500, off0=20) at ../../../netinet/tcp_input.c:1138 #17 0xc0231700 in ip_input (m=0xc103b500) at ../../../netinet/ip_input.c:845 #18 0xc02317be in ipintr () at ../../../netinet/ip_input.c:870 #19 0xc01c64f4 in swi_net (dummy=0x0) at ../../../kern/kern_intr.c:644 #20 0xc01c6220 in ithread_loop (arg=0xc102e680) at ../../../kern/kern_intr.c:533 #21 0xc01c5432 in fork_exit (callout=0xc01c607c , arg=0xc102e680, frame=0xd0412d48) at ../../../kern/kern_fork.c:799 (kgdb) ---> I've also attached the dmesg output. TIA Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! Copyright (c) 1992-2002 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-DP1 #0: Wed May 15 19:35:03 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/KAJSA Preloaded elf kernel "/boot/kernel/kernel" at 0xc0448000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04480a8. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (551.25-M
Re: The future of perl on FreeBSD
On Thu, May 09, 2002 at 12:55:42PM -0400, John Baldwin wrote:
Hi,
> Ports should avoid messing with stuff outside of ${PREFIX} if they can
> help it. Existing systems will already have a /usr/bin/perl on them
> unless the user goes and removes it. People writing or executing scripts for
> new systems can easily figure out something is wrong when they get:
Now that I think of it, you are absolutely right, John. Just let's make
a big big banner saying "Perl is no longer in base" so everybody notices
:)
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg38107/pgp0.pgp
Description: PGP signature
Re: Problems with Dell Inspiron 2500/NEWCARD/Xircom CBEM56G
On Mon, May 06, 2002 at 08:54:01PM +1000, Scott Penno wrote: Hi, > Just an update. I've tried three different 32 bit cards and every time the > card was inserted the laptop locked up. I recompiled the kernel without the > miibus and dc and then inserted the Xircom card the laptop would appear to > lock up, that is, everything that was running just stopped. When the card > was re-inserted, everything would come back to life and a console message > would appear reporting 'pccbb0: Cardbus card activation failed'. A similar > result was experienced with the other cards. With that said, I'm still no > closer to identifying the cause of these problems. Any ideas? Well, I've used different versions of 5.0 on my laptop, and my experience is that Cardbus devices don't like to be pulled out. Everytime I've done it the system has hung, so my assumption is: Patient: When I remove a 32bit card the system freezes. Doctor: Don't remove 32bit cards. About inserting it, well, I never had success with that either. The only way for it to work is to have the card already there *before* booting the system. I don't know if that's the expected behaviour or not, it works flawlessly with 16bit stuff. My hardware is a Thinkpad 300E, a 16bit ne2k clone and a RealJunk 8139 Cardbus NIC. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg38068/pgp0.pgp Description: PGP signature
problem building libh
Hi,
When trying to build libh (from CVS) on a 5.0-DP1 system I get the
following error:
===> disk
c++ -pipe -g -I/usr/local/include/tcl8.3 -fpic -DPIC
-I/pub/devel/libh/lib/disk/../../include -Wall -c
/pub/devel/libh/lib/disk/Disk.cc -o Disk.o
In file included from /pub/devel/libh/lib/disk/Disk.cc:39:
/usr/include/sys/disklabel.h:191: `lp' was not declared in this scope
/usr/include/sys/disklabel.h:192: syntax error before `*'
/usr/include/sys/disklabel.h:189: warning: `u_int16_t dkcksum(disklabel
*)' declared `static' but never defined
*** Error code 1
However, looking at the code one can apply the following (trivial)
patch:
flynn@saioa# diff -ruN disklabel.h.old disklabel.h
--- disklabel.h.old Wed Apr 17 19:03:59 2002
+++ disklabel.h Wed Apr 17 19:04:39 2002
@@ -188,8 +188,7 @@
static __inline u_int16_t dkcksum __P((struct disklabel *lp));
static __inline u_int16_t
-dkcksum(lp)
- struct disklabel *lp;
+dkcksum(struct disklabel * lp)
{
u_int16_t *start, *end;
u_int16_t sum = 0;
-
Has this been fixed in recent -CURRENT includes?
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg37329/pgp0.pgp
Description: PGP signature
Re: sh dies w/ sig 12
On Thu, Apr 11, 2002 at 11:36:49AM -0700, Seth Hettich wrote: > Trying to update to -current, in SU mode, doing the make installworld: > > [ ! -e /usr/bin/passwd ] || echo foo > > will make sh die > > This is even with the "new" sh from my buildworld (I am running the new > kernel). > > Ideas? Are you upgrading from -stable to -current? I had that same problem. My (crap) workaround, was to create a Makefile for the points were sh failed (iirc was chpass and some other command) that looked like this: all: install install: echo foo That enabled me to successfully installworld, I took note of the faulty places and installed them afterwards. I know it's not the 'kosher' solution, but it worked for me. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg37166/pgp0.pgp Description: PGP signature
5.0-DP1
Hi, I've just installed the DP1 snapshot on my laptop, and, so far, I'm very happy with it. I haven't experienced a single hang or problem with the system, even though my kernel is compiled without WITNESS and INVARIANTS. I've stress tested the system by building all software using ports, testing the background fsck and so on. Everything runs fine. The only two things that prevented this from being a perfect experience were (and not really the system's fault) - Somehow XF4.x that one can install from sysinstall now doesn't like the 8bit display from this computer, and all the window managers I installed had problems allocating colours with it (xfce, fvwm-themes, fluxbox). Installing 3.3.6 solved the problem. - If possible, I think it would be nice if a newcard.flp floppy image was included in future snapshots and maybe in the 5.0-R cdrom and ftp files, a la NetBSD's laptop floppy images, so users of CARDBUS nics can do a net install without having to use a PCCARD device first. As I said, other than these two minor giltches, a very smooth install. Kudos to all that work on this. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg37156/pgp0.pgp Description: PGP signature
Re: Card has no functions
On Mon, Apr 01, 2002 at 07:42:59AM -0800, Shizuka Kudo wrote: Hi there, > I'm having problem with the TI cardbus bridge to > recognize PCCARD in "NEWCARD" kernel. I have a desktop > with TI PCI1250 adaptor and an IBM Thinkpad with TI > 1450. Both recognize PC Cards in "GENERIC" kernel, but > get "Card has no functions" in NEWCARD. I checked the > maillist and found no answer. The same kernel ran fine > in a Toshiba Portege with ToPIC100 cardbus bridge. Is > this something unique to TI chips? Any suggestion I > should try? My Thinkpad 310 is running -CURRENT as of the 29th of March. I normally use a CARDBUS nic, but I've just inserted a PCCARD nic on the second slot and it's recognized as ed0. My hardware has a TI1131 PCI-CardBus Bridge. It seems to work here, when did you last cvsup your src? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36863/pgp0.pgp Description: PGP signature
Re: Bus error compiling thefish 0.2 on -current
On Sat, Mar 30, 2002 at 01:31:09PM -0800, Kris Kennaway wrote: Hi Terry and Kris, > Sounds like it could be the malloc.conf defaults on -current exposing > a bug in the program code. Yes, there was a bug in my code, it just didn't show up on -STABLE. Apparently, when one uses efence, allocated memory is zeroed, which would explain why the program worked when linked with efence. I've built a debug version of libdialog and found something interesting... #0 0x28324253 in dialog_checklist (title=0x80bcf54 "Knobs Menu", prompt=0x80bcf60 "A checked entry means that knob is set to YES", height=-1,width=-1, list_height=15, cnt=-1697, it=0x81e6014, result=0x0) at checklist.c:82 82 status[i] = ditems[i].checked ? ditems[i].checked(&ditems[i]) : FALSE; There is something odd in that cnt value, as there aren't 1697 entries in the menu. The problem is the way the dialog structure is built, I malloc memory but don't zero it, so when I call the function that in the end calls dialog, it erroneously assumes that there are more entries than there really are, since it simply checks for !=0 data. The garbage present in the malloc'ed mem is the cause. Why this problem doesn't show on -STABLE is still beyond my comprehension, default malloc behaviour maybe? Anyway, problem solved, thanks for all. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36803/pgp0.pgp Description: PGP signature
Re: Bus error compiling thefish 0.2 on -current
On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote: Just for the record, and to make things more fun, the program works when linked with efence. Could this narrow the problem to libc? Any ideas? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36788/pgp0.pgp Description: PGP signature
Bus error compiling thefish 0.2 on -current
Hi,
I'm finishing the new version of sysutils/thefish, and doing some
development on a -current box. For the ncurses/dialog frontend, I'm
using a couple of functions from the sysinstall code, and this program
works perfectly well on a 4.5-STABLE system. If I take the binary and
run it on -CURRENT, it works as well, but, if I compile that code on
-CURRENT, the program dies with a Bus Error the moment I enter the Knobs
menu. I've seen this problem both with the 11th of March snapshot and
with a world I built yesterday, cvsupped at 1500 UTC. The current box
specs are these:
flynn@saioa# uname -a
FreeBSD saioa.energyhq.tk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Mar 30
00:37:49 GMT 2002 root@:/usr/obj/usr/src/sys/SAIOA i386
flynn@saioa# cc -v
Using builtin specs.
gcc version 2.95.4 20020320 [FreeBSD]
The gdb trace when the program fails:
(gdb) bt
#0 0x280da10a in dialog_menu () from /usr/lib/libdialog.so.4
#1 0x804e0a7 in dmenuOpen (menu=0x81d5000, choice=0xbfbff8bc,
scroll=0xbfbff8c0, curr=0xbfbff8c4, max=0xbfbff8c8, buttons=0)
at ncurses_ui.c:249
#2 0x804df6a in dmenuOpenSimple (menu=0x81d5000, buttons=0)
at ncurses_ui.c:191
#3 0x804deff in dmenuSubmenu (tmp=0x80bb6f4) at
ncurses_ui.c:175
#4 0x280db1ae in dialog_menu () from /usr/lib/libdialog.so.4
#5 0x804e0a7 in dmenuOpen (menu=0x80bb680,choice=0xbfbffa5c,
scroll=0xbfbffa60, curr=0xbfbffa64, max=0xbfbffa68,buttons=1)
at ncurses_ui.c:249
#6 0x804debf in create_ncurses_ui(rc_knobs=0x817b000, num_knobs=96,
rc_strings=0x8197000, num_str=138) at ncurses_ui.c:163
#7 0x804b2ed in main (argc=0, argv=0xbfbffb18) at main.c:216
#8 0x804a5c5 in _start ()
(gdb)
The program tarball can be found at
http://energyhq.homeip.net/files/thefish-0.2.tar.gz
My question is, is it a bug in my program that only shows in -CURRENT or
is the compiler in current broken?
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg36776/pgp0.pgp
Description: PGP signature
Re: BTX halted
On Mon, Mar 25, 2002 at 01:14:57PM -0500, John Baldwin wrote: Hi again, > > I don't have a debug kernel, those are the boot floppies downloaded from > > current.freebsd.org. If it helps, the snapshot floppies from 11th of > > March work, every floppy made after that date fails with the same error. > > I'm going to install that snapshot, upgrade the system and try to > > reproduce the error with a debug kernel. > > Ok. If you can figure out what kernel commit broke things that would be very > helpful. Thanks! As someone else pointed out, it seems to be a problem with corrupted floppy images. I've succesfully built kernels from the 20th and 21st of March (using those ssys tarballs), and they boot fine. There seems to be a problem with the floppy images generated after the 11th of March. I'm not sure what can be causing this, but the kernel problem can be discarded, those kernels boot fine from harddisk. I'm going to build a floppy image when I get some time and report my results here. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36589/pgp0.pgp Description: PGP signature
Re: BTX halted
On Mon, Mar 25, 2002 at 11:40:36AM -0500, John Baldwin wrote: > > int=0006 err= efl=00010092 eip=c0309927 > > eax=c082e000 ebx=0082cc00 ecx= edx=0002 > > esi=0082c000 edi=00834000 ebp=c082fd94 esp=c082fd78 > > cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 > > cs:eip=ff ff a1 a4 48 37 c0 a3 - ac aa 38 c0 a1 a8 48 37 > >c0 a3 84 ab 38 c0 05 a0 - 1d ff ff a3 60 ab 38 c0 > > > > ss:esp=00 40 83 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > >00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > > BTX halted > > Weird, it looks like you actually got into the kernel before blowing up. > Did you have debug copy of the kernel with you. If so, can you do a > listing of the address in %eip? I don't have a debug kernel, those are the boot floppies downloaded from current.freebsd.org. If it helps, the snapshot floppies from 11th of March work, every floppy made after that date fails with the same error. I'm going to install that snapshot, upgrade the system and try to reproduce the error with a debug kernel. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36554/pgp0.pgp Description: PGP signature
Re: BTX halted
On Mon, Mar 25, 2002 at 06:05:14AM -0800, Hiten Pandya wrote:
> Could you please send us the register dump. Someone will analyse it and
> will get back to you. Or could you please file a Problem Report for this
> issue. :)
Here's the dump, I want to open a PR too, what the category would be?
i386?
int=0006 err= efl=00010092 eip=c0309927
eax=c082e000 ebx=0082cc00 ecx= edx=0002
esi=0082c000 edi=00834000 ebp=c082fd94 esp=c082fd78
cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010
cs:eip=ff ff a1 a4 48 37 c0 a3 - ac aa 38 c0 a1 a8 48 37
c0 a3 84 ab 38 c0 05 a0 - 1d ff ff a3 60 ab 38 c0
ss:esp=00 40 83 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
BTX halted
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg36544/pgp0.pgp
Description: PGP signature
BTX halted
Hi,
I've tried to install two snapshots (20th and 21st of March) on my
Thinkpad laptop, and after the loader has finished reading mfsroot.flp I
get a register dump and a message saying BTX halted. Any hints of what
could be causing this? The problem didn't show last time I used a
snapshost, last December or 4.5-R install disks.
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg36542/pgp0.pgp
Description: PGP signature
Re: rtld messing up?
On Wed, Mar 20, 2002 at 05:47:32PM +, Mark Murray wrote: > In ports/lang/gcl, a program is "undumped", and the resultant binary > dumps core _very_ early in the startup. I can't get debugging info, > because the undumping also seems to strip the program. I've also have had that same problem when I tried to build the port, but was never able to find the reason for the program to segfault, I even opened a PR on that. The program seems to work on NetBSD btw. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36393/pgp0.pgp Description: PGP signature
Re: Patch to improve mutex collision performance
On Thu, Feb 21, 2002 at 01:49:09AM -0800, David O'Brien wrote: I'm not a commiter, but here comes my very humble opinion... > Users of Perforce are starting to force the rest of us to learn and use > it. That is totally not acceptable for the general FreeBSD population. This argument is pretty weak, learning perforce takes 15-20 minutes. > Those that chose to use it because they feel the tool is useful for > THEMSELVES are of course free to use it. HOWEVER, Perforce is NOT the CM > system of the FreeBSD project. Thus users of Perforce are expected to > share their bits via posting patches, not forcing everyone to pull them > out of the Perforce depot. Well, if all developers started using p4, things would be easier and work better in the long term. p4 is lightyears ahead of cvs, and, from what I've read in this thread, developers are not exactly happy with cvs now, as it's limitations have become evident. So, why not give it a try? Just my 0.02 Eur Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg35021/pgp0.pgp Description: PGP signature
Re: more -current testers
On Tue, Feb 19, 2002 at 12:50:11PM -0500, Michael Lucas wrote: Hi Michael, > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. Agreed. I think there are people out there willing to help and become testers, they're just afraid of -CURRENT 'horror histories'. Running -current is not a walk in the park, and no one should attempt to do any serious work with it, but imho it's stable enough for your average mp3 listening, web browsing and kde/gnome/whathaveyou usage. > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. Sounds very good, and yes, most people disable witness so their system doesn't crawl like a 286 :) > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. I don't think it's too early, IMHO it's a very good idea, having specific info on how to use -CURRENT will be beneficial for the community and atract more users to it. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg34919/pgp0.pgp Description: PGP signature
Problem with a carbus Realtek 8139 card
Hi people,
I installed -CURRENT on my laptop:
FreeBSD saioa.energyhq.tk 5.0-CURRENT-20020204-JPSNAP FreeBSD
5.0-CURRENT-20020204-JPSNAP #0: Fri Feb 8 13:09:05 CET 2002
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/SAIOA i386
And compiled a kernel modifying the NEWCARD template. Everything works
fine , except from time to time the network stops working. If I do a
ifconfig rl0 down and then ifconfig rl0 up it starts working again. Any
idea why is this happening? If I use the 16bit pcmcia nic this doesn't
happen, and it also didn't happen when this computer was running NetBSD
1.5.2
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg34720/pgp0.pgp
Description: PGP signature
current.freebsd.org down?
Hi,
I know this is probably offtopic but is there any problem with
current.freebsd.org at the moment? I've been unable to log in for almost an
hour, the ftp daemon is up, it just doesn't allow me in and I was about to
load -CURRENT on my laptop.
Any idea?
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
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
current.freebsd.org down?
Hi,
I know this is probably offtopic but is there any problem with
current.freebsd.org at the moment? I've been unable to log in for almost an
hour, the ftp daemon is up, it just doesn't allow me in and I was about to
load -CURRENT on my laptop.
Any idea?
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Junior Annoying Hacker Task
On Sun, 3 Feb 2002 00:38:34 +0800 (MYT) Dinesh Nair <[EMAIL PROTECTED]> wrote: Hi, > > times, well, not with the registry paradigm, but some sort of > > graphical admin tool based on GTK. I'm doing exams this week but may > > take a go at it after I finish them. > > why not use something like webmin ? webmin requires a web browser, 'foo' won't :) My idea is that it will work both on console (ncurses) and X (GTK), and because freedom of choice is a good thing. And I don't like webmin at all :-) Cheers, -- Miguel Mendez - [EMAIL PROTECTED] Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Junior Annoying Hacker Task
On Sat, 02 Feb 2002 03:29:50 -0800
Terry Lambert <[EMAIL PROTECTED]> wrote:
Hi Terry et al,
> Let me know the form you want the hierarchy to take, so
> you can stick it into the GTK hierarchy thingy; I'll be
> happy to crank out some quick yacc and lex code to do
> the parsing of the file into that format for you. A
> structure definition, with links, and how you want it
> linked, would be ideal. 8-).
I've been thinking about it and I'd like to provide two frontends, a GTK one and a
ncurses one, what do you think?
>
> Something like:
>
> typedef enum _nodekind {
> NK_VALUE, /* Path component */
> NK_KEY, /* Key */
> [.]
> struct node *child;
> int intval;
> char *strval;
> struct wcval *wcval;
> } u;
> };
>
It looks fine to me.
Is your idea to manage rc.conf from there or maybe sysctl variables could be added too
(once a working version of the rc.conf thing is made, of course).
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://energyhq.homeip.net
FreeBSD - The power to serve!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Junior Annoying Hacker Task
On Fri, Feb 01, 2002 at 04:26:13PM -0800, Terry Lambert wrote: Hi Terry, > Who is a GTK hacker? I've done some GTK programs in the past. > > Does someone want to write a "registry editor" program? > > The point of the program would be to edit the "FreeBSD > Registry", rc.conf, and make it look just like the Windows > Registry in the editor, using "_" as the implied path > component/terminal component (key) seperator. > > Then we can all be honest with ourselves that the only > difference between it an the Windows Registry is that > the Windows registry is accessible/modifiable from > kernel mode, and the path component and key names. > Are you really serious about this? :) I've thought about that many times, well, not with the registry paradigm, but some sort of graphical admin tool based on GTK. I'm doing exams this week but may take a go at it after I finish them. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! msg34032/pgp0.pgp Description: PGP signature
Re: pkg_version on -CURRENT
On Thursday 31 January 2002 21:24, Kris Kennaway wrote:
Hi Kris,
> If you installed it from the port, reinstall the port.
>
> portupgrade -f p5-\*
>
> should do the trick.
That did it, thanks!
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://energyhq.homeip.net
FreeBSD - The power to serve!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
pkg_version on -CURRENT
Hi there, Some days ago I upgraded a 4.4-RC box to 5.0-CURRENT, and pkg_version is no longer working. Being it a perl script, is this due to the fact that current uses 5.6? How to fix this then? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
