Re: OpenSSL question for id_function()
Craig Rodrigues wrote: return static_cast(pthread_self()); pthread_self() returns something of type pthread_t. This code works under Linux, because pthread_t is mapped to an integer value. However, on FreeBSD, pthread_t is a pointer to struct pthread, so this code does not compile: OpenSSLPluginI.cpp: In function `long unsigned int IceSSL::idFunction()': OpenSSLPluginI.cpp:153: invalid static_cast from type `pthread*' to type `long unsigned int' Is there a way to implement the id_function() for OpenSSL so that it works portably across FreeBSD and Linux? return (unsigned long)(void *)(pthread_self()); -- Lev Walkin [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patch for the nVidia driver and -CURRENT
Thanks Mess On Thursday 27 February 2003 02:55, Mezz bsdforums.org wrote: > >I'm interested in applying this patch, because I've never done such > >precedure. > >Is anybody able to explane me, step by step, what should I do? > >Thanks in advance. > > % tar xfvz NVIDIA_FreeBSD-1.0-3203.tar.gz > % fetch http://mu.org/~mux/patches/nvidia.patch > % patch -p0 < nvidia.patch > % cd NVIDIA_FreeBSD-1.0-3203 > goes on by follow the readme.. > > BTW: Thanks Maxime! I haven't tried it yet, because I need to update my > -CURRENT (Feb 18) system tonight so I can use this patch. > > Cheers, > Mezz > > _ > Protect your PC - get McAfee.com VirusScan Online > http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Yet another ATA-related Kernel trap 12 :-(
It seems Vladimir Kushnir wrote: > Setup: Fujitsu MPG3409AT E disk on external CMD649 controller (the only > HD). Kernel trap while booting with timeout for ad0 device. Setting > "hw.ata.ata_dma=0" solves the problem. Sources last cvsupped last night > (after the last ATA-related commits). Dmesg output attached, but that's > about all I can provide - no serial console here. I just committed a fix for that. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patch for the nVidia driver and -CURRENT
I'm interested in applying this patch, because I've never done such precedure. Is anybody able to explane me, step by step, what should I do? Thanks in advance. % tar xfvz NVIDIA_FreeBSD-1.0-3203.tar.gz % fetch http://mu.org/~mux/patches/nvidia.patch % patch -p0 < nvidia.patch % cd NVIDIA_FreeBSD-1.0-3203 goes on by follow the readme.. BTW: Thanks Maxime! I haven't tried it yet, because I need to update my -CURRENT (Feb 18) system tonight so I can use this patch. Cheers, Mezz _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patch for the nVidia driver and -CURRENT
Hello,
I'm interested in applying this patch, because I've never done such precedure.
Is anybody able to explane me, step by step, what should I do?
Thanks in advance.
On Wednesday 26 February 2003 08:01, Maxime Henrion wrote:
> Jake Burkholder wrote:
> > Apparently, On Tue, Feb 25, 2003 at 10:49:16PM +0100,
> > Maxime Henrion said words to the effect of;
> >
> > > Morten Rodal wrote:
> > > > On Tue, Feb 25, 2003 at 07:28:09PM +0100, Maxime Henrion wrote:
> > > > [snip a lot of the patch]
> > > >
> > > > > @@ -1431,7 +1442,8 @@
> > > > > SLIST_FOREACH(at, &sc->alloc_list, list) {
> > > > > if (offset >= at->address &&
> > > > > offset < at->address + at->size)
> > > > > -return atop(vtophys(offset));
> > > > > +*paddr = vtophys(offset);
> > > > > +return 0;
> > > > > }
> > > > >
> > > > > return -1;
> > > >
> > > > Should the function return 0 even if the if (offset..) fails? I have
> > > > no clue about the nvidia kernel driver (or kernel stuff at all) but
> > > > it seems to me that the only way the function can return -1 is if the
> > > > list is empty.
> > >
> > > And this is consistant with what the code was doing before. This
> > > change is not a functional change, it's just a necessary update due to
> > > API changes.
> >
> > I think he's referring to missing braces around the if which was changed
> > from 1 statement to 2.
>
> Damnit. I've updated the patch at :
> http://mu.org/~mux/patches/nvidia.patch
>
> I've also added the removal of the #error in this patch, since people
> have been asking me about it.
>
> Cheers,
> Maxime
>
> 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: "NTLDR missing" after 5-RELEASE install
I have never emailed this list, and am only reading it to see how 5.0-RELEASE is shaping up. Sorry if I'm repeating stuff or commenting out of turn. This problem sounds like the one I've had on several occasions when repartitioning my HDD. My Windows2000 "boot.ini" invariably needs to be updated because the partition table has changed. (or at least what Windows thinks the partition table says has changed). That's why NTLDR is missing - Windows is looking at the wrong partition. The MS knowledge base article 102873 indicates that the boot.ini partition format is: multi(X)disk(Y)rdisk(Z)partition(W)\ From memory, you have to mess with partition(W) until you get the right partition. I've never done a systematic test to be more specific than this. I have always used FAT32 partitions so mounting the WinNT System partition (so that I can change boot.ini) is no problem. I have never used NTFS partitions so this might not be helpful for you. Maybe the Windows Emergency Boot Disk can help you out there You can search MS for other "boot.ini" articles. good-luck, SDH PS I seem to remember that I also had to delete "hiberfil.sys" from the WinNT system partition, but I can't remember what my theory for that was. Something to do with "boot.ini" being cached. I haven't systematically tested, but it works for me without resorting to Windows tools. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
Nuno Teixeira wrote: > > Hi, > > Just a little question: > > Does -march=k6-2 implies -m3dnow? Or -march=pentiumpro implies -mmmx? Pentium Pro doesn't support MMX; -march=pentiumpro (aka -march=i686) enables compiling with main i686 instruction set, no MMX\SSE or whatever. > > I always thought that when I use -march it will enable other > porcessor specific optimizations like mmx and 3dnow (if available). No way. Besides, only a dozen of open-source UNIX applications can really profit from MMX, so it's absurd to use -mmmx for day-by-day use. To be correct, MMX is only useful for real-time video\audio processing. A little example: consider some 16-bit pixel set that you need to increase brightness, i.e. to add some value to every pixel. You can load a word into integer register, process, and store. You can also load a quadword of four 16-bit values into MMX register which is mapped onto FPU register, process them at once, and store. Indeed to be faster. Enabling MMX usually results in about 50% performance increase for true CISC processors like P-MMX, and about 20% for PII and up. --- Regards, Rhett __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Vinum R5 [was: Re: background fsck deadlocks with ufs2 and big disk]
On Friday, 21 February 2003 at 1:56:56 -0800, Terry Lambert wrote: > Vallo Kallaste wrote: >> The crashes and anomalies with filesystem residing on R5 volume were >> related to vinum(R5)/softupdates combo. The vinum R5 and system as >> a whole were stable without softupdates. Only one problem remained >> after disabling softupdates, while being online and user I/O going >> on, rebuilding of failed disk corrupt the R5 volume completely. >> Don't know is it fixed or not as I don't have necessary hardware at >> the moment. The only way around was to quiesce the volume before >> rebuilding, umount it, and wait until rebuild finished. I'll suggest >> extensive testing cycle for everyone who's going to work with >> vinum R5. Concat, striping and mirroring has been a breeze but not >> so with R5. > > I think this is an expected problem with a lot of concatenation, > whether through Vinum, GEOM, RAIDFrame, or whatever. Can you be more specific? What you say below doesn't address any basic difference between virtual and real disks. > This comes about for the same reason that you can't "mount -u" > to turn Soft Updates from "off" to "on": Soft Updates does not > tolerate dirty buffers for which a dependency does not exist, and > will crap out when a pending dirty buffer causes a write. I don't understand what this has to do with virtual disks. > This could be fixed in the "mount -u" case for Soft Updates, and it > can also be fixed for Vinum (et. al.). > > The key is the difference between a "mount -u" vs. a "umount ; mount", > which comes down to flushing and invalidating all buffers on the > underlying device, e.g.: > > vn_lock(devvp, LK_EXCLUSIVE | LK_RETRY, p); > vinvalbuf(devvp, V_SAVE, NOCRED, p, 0, 0); > error = VOP_CLOSE(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p); > error = VOP_OPEN(devvp, ronly ? FREAD : FREAD|FWRITE, FSCRED, p); > VOP_UNLOCK(devvp, 0, p); > > ... Basically, after rebuilding, before allowing the mount to proceed, > the Vinum (and GEOM and RAIDFRame, etc.) code needs to cause all the > pending dirty buffers to be written. This will guarantee that there > are no outstanding dirty buffers at mount time, which in turn guarantees > that there will be no dirty buffers that the dependency tracking in > Soft Updates does not know about. I don't understand what you're assuming here. Certainly I can't see any relevance to Vinum, RAIDframe or any other virtual disk system. Greg -- See complete headers for address and phone numbers Please note: we block mail from major spammers, notably yahoo.com. See http://www.lemis.com/yahoospam.html for further details. pgp0.pgp Description: PGP signature
Re: Vinum R5 [was: Re: background fsck deadlocks with ufs2 and big disk]
On Friday, 21 February 2003 at 10:00:46 +0200, Vallo Kallaste wrote: > On Thu, Feb 20, 2003 at 02:28:45PM -0800, Darryl Okahata > <[EMAIL PROTECTED]> wrote: > >> Vallo Kallaste <[EMAIL PROTECTED]> wrote: >> >>> I'll second Brad's statement about vinum and softupdates >>> interactions. My last experiments with vinum were more than half a >>> year ago, but I guess it still holds. BTW, the interactions showed >>> up _only_ on R5 volumes. I had 6 disk (SCSI) R5 volume in Compaq >>> Proliant 3000 and the system was very stable before I enabled >>> softupdates.. and of course after I disabled softupdates. In between >>> there were crashes and nasty problems with filesystem. Unfortunately >>> it was production system and I hadn't chanche to play. >> >> Did you believe that the crashes were caused by enabling softupdates on >> an R5 vinum volume, or were the crashes unrelated to vinum/softupdates? >> I can see how crashes unrelated to vinum/softupdates might trash vinum >> filesystems. > > The crashes and anomalies with filesystem residing on R5 volume were > related to vinum(R5)/softupdates combo. Well, at one point we suspected that. But the cases I have seen were based on a misassumption. Do you have any concrete evidence that points to that particular combination? > The vinum R5 and system as a whole were stable without > softupdates. Only one problem remained after disabling softupdates, > while being online and user I/O going on, rebuilding of failed disk > corrupt the R5 volume completely. Yes, we've fixed a bug in that area. It had nothing to do with soft updates, though. > Don't know is it fixed or not as I don't have necessary hardware at > the moment. The only way around was to quiesce the volume before > rebuilding, umount it, and wait until rebuild finished. I'll suggest > extensive testing cycle for everyone who's going to work with vinum > R5. Concat, striping and mirroring has been a breeze but not so with > R5. IIRC the rebuild bug bit any striped configuration. Greg -- See complete headers for address and phone numbers Please note: we block mail from major spammers, notably yahoo.com. See http://www.lemis.com/yahoospam.html for further details. pgp0.pgp Description: PGP signature
Re: "NTLDR missing" after 5-RELEASE install
Darryl Okahata writes: > [EMAIL PROTECTED] (George Hartzell) wrote: > > > Only differences are which partition we mark active and what boot > > loader lives there. > > True, but that's the key point: "... and what boot loader lives > there." There are times when not touching the boot loader is desirable. > While GRUB, booteasy, and others are quite perfectly usable for many > people, some of us may be better off with an untouched MBR. But I'm not touching the MBR either. I run a stock sony vaio MBR, and install GRUB into the beginning of my freebsd partition. GRUB and LILO behave nicely there, the standard freebsd boot loader (booteasy?) seems to insist on being in the MBR. If I boot windows, my boot sequence goes MBR -> GRUB (because it's installed in the beginning of the partition that's marked active) -> the window's loader (because grub's been told to chainload to the loader that's in the beginning of the first partition) --> windows. FreeBSD goes something like MBR -> GRUB (ditto, above) --> /boot/loader from the freebsd filesystem (because that's what grub's been told to load for that "title" loader does the normal freebsd stuff, loading the kernel and going for it. It's also possible to have grub boot the freebsd kernel directly, but I like to have both boot up in as much of a native world as possible. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
Andre Guibert de Bruet wrote: On Wed, 26 Feb 2003, Nuno Teixeira wrote: Does -march=k6-2 implies -m3dnow? Or -march=pentiumpro implies -mmmx? I always thought that when I use -march it will enable other porcessor specific optimizations like mmx and 3dnow (if available). IIRC, 166 and 180 Mhz PPros don't support MMX. Neither do PPro's 200: CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xf9ff I'm seeing differences in compiled code between simple -march=athlon-xp and -march=athlon-xp -mmmx -m3dnow -msse. The documentation says the same: those options have to be enabled to use extended instruction sets. -march/-mcpu just optmizes boundaries of jump labels, variables, etc... - and sometimes the kind of instructions to use, eg. 'loop label' or 'dec bcx, jne label', but that's all, AFAIK. So long, Jens -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: <[EMAIL PROTECTED]> Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
On Wed, 26 Feb 2003, Nuno Teixeira wrote: > Does -march=k6-2 implies -m3dnow? Or -march=pentiumpro implies -mmmx? > > I always thought that when I use -march it will enable other > porcessor specific optimizations like mmx and 3dnow (if available). IIRC, 166 and 180 Mhz PPros don't support MMX. I'm seeing differences in compiled code between simple -march=athlon-xp and -march=athlon-xp -mmmx -m3dnow -msse. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld TARGET_ARCH=foobar seems to be broken
Most likely, some of your sources have modification date pointing to the future, or your computer's date is old. On Thu, Feb 27, 2003 at 03:59:28AM +0600, Max Khon wrote: > hi, there! > > Seems that for some reason gengenrtl is not built when doing 'make build-tools' > in gnu/usr.bin/cc/cc_tools. As a result 'make buildworld TARGET_ARCH=foobar' > is broken. > > Below is the output of 'make buildworld TARGET_ARCH=alpha' of recent > HEAD on 4.7-STABLE/i386 > > ===> gnu/usr.bin/cc/cc_tools > cc -O -pipe -mcpu=ev4 -mtune=ev5 -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" > -I/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -static > -DGENERATOR_FILE-c /usr/fbsd/HEAD/contrib/gcc/gengenrtl.c > cc -O -pipe -mcpu=ev4 -mtune=ev5 -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" > -I/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -static > -DGENERATOR_FILE -o gengenrtl gengenrtl.o > -O -pipe -mcpu=ev4 -mtune=ev5 -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" > -I/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc > -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -static > -DGENERATOR_FILE -o gengenrtl gengenrtl.o > ./gengenrtl > genrtl.c > ./gengenrtl: 6: Syntax error: ")" unexpected > *** Error code 2 > > Stop in /usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools. > *** Error code 1 > > Stop in /usr/fbsd/HEAD/gnu/usr.bin/cc. > *** Error code 1 > > Stop in /usr/fbsd/HEAD/gnu/usr.bin. > *** Error code 1 > > Stop in /usr/fbsd/HEAD/gnu. > *** Error code 1 > > Stop in /usr/fbsd/HEAD. > *** Error code 1 > > Stop in /usr/fbsd/HEAD. > *** Error code 1 > > Stop in /usr/fbsd/HEAD. > > Running file in object directory shows the following: > > [EMAIL PROTECTED]:/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools$file gen* | > grep '^gen[a-z]*:' > genattr:ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), > statically linked, not stripped > genattrtab: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), > statically linked, not stripped > [...] > gengenrtl: ELF 64-bit LSB executable, Alpha (unofficial), version 1 (FreeBSD), > statically linked, not stripped > [...] > genrecog: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), > statically linked, not stripped > > By the way why gengenrtl is executed at all? > > [EMAIL PROTECTED]:/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools$./gengenrtl > ./gengenrtl: Exec format error. Binary file not executable. > [EMAIL PROTECTED]:/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools$env FOO=bar > ./gengenrtl > ./gengenrtl: 6: Syntax error: ")" unexpected > > (the shell is tcsh) > > /fjoe > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age pgp0.pgp Description: PGP signature
Re: "NTLDR missing" after 5-RELEASE install
[EMAIL PROTECTED] (George Hartzell) wrote: > Only differences are which partition we mark active and what boot > loader lives there. True, but that's the key point: "... and what boot loader lives there." There are times when not touching the boot loader is desirable. While GRUB, booteasy, and others are quite perfectly usable for many people, some of us may be better off with an untouched MBR. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
On Wed, 26 Feb 2003 13:06:54 +0100 Jens Rehsack <[EMAIL PROTECTED]> wrote: > Dag-Erling Smorgrav wrote: > > It seems that with -O2 on ia32 (-march=k6-2 in my case), gcc will in > > some cases generate short jumps to targets too far away for the offset > > to fit in a single byte. A surefire way to reproduce this is to build > > Mesa (or XFree86-4-libraries, which includes parts of Mesa). > > > > Has anybody else run into this? > > > > I build world and ports on desktop machines usually using -O2 and never > got any problems, except with lang/ezm3. If you tell me, where you've > find the problems, I'll tell my gcc to keep the temporaries and check > them after a make build. you need to add "-fno-schedule-insns2" to your CFLAGS to compile ezm3 with -O2... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HyperThreading not working?
* De: Trish Lynch <[EMAIL PROTECTED]> [ Data: 2003-02-26 ] [ Subjecte: RE: HyperThreading not working? ] > On Wed, 26 Feb 2003, John Baldwin wrote: > > > > > On 26-Feb-2003 Slawek Zak wrote: > > > Hi, > > > > > > I'm in the process of installing 5.0-RELEASE-p3 on a Dell PowerEdge > > > 2600 server. It has two HyperThreading Xeon 2.4Ghz processors, but > > > HyperThreading is not working in FreeBSD. I guess that four > > > processors should be visible in the system after boot. Yes - I've > > > enabled `Logical Processors' in BIOS. BIOS revision is the latest > > > available. > > > > > > Any thoughts? I attach full dmesg and mptable output. Kernel > > > config too. > > > > 5.0 doesn't support HyperThreading. The upcoming 5.1 and 4.8 releases > > will support it. > > > > it doesn't? I have a 5.0-R box that surely does support HTT. Your BIOS puts the logical CPUs into the MPTable. -- Juli Mallett <[EMAIL PROTECTED]> - AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer - ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD - Never trust an ELF, COFF or Mach-O! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: HyperThreading not working?
On Wed, 26 Feb 2003, John Baldwin wrote: > > On 26-Feb-2003 Slawek Zak wrote: > > Hi, > > > > I'm in the process of installing 5.0-RELEASE-p3 on a Dell PowerEdge > > 2600 server. It has two HyperThreading Xeon 2.4Ghz processors, but > > HyperThreading is not working in FreeBSD. I guess that four > > processors should be visible in the system after boot. Yes - I've > > enabled `Logical Processors' in BIOS. BIOS revision is the latest > > available. > > > > Any thoughts? I attach full dmesg and mptable output. Kernel > > config too. > > 5.0 doesn't support HyperThreading. The upcoming 5.1 and 4.8 releases > will support it. > it doesn't? I have a 5.0-R box that surely does support HTT. -bash-2.05b$ uname -a FreeBSD ecelerity-s1-3 5.0-RELEASE FreeBSD 5.0-RELEASE #3: Mon Jan 20 16:59:08 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ECELERITY-5.0 i386 Copyright (c) 1992-2003 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-RELEASE #3: Mon Jan 20 16:59:08 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ECELERITY-5.0 Preloaded elf kernel "/boot/kernel/kernel" at 0xc069a000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc069a0a8. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium 4 (1796.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff> real memory = 1073217536 (1023 MB) avail memory = 1034719232 (986 MB) Programming 24 pins in IOAPIC #0 OAPIC #0 intpin 2 -> irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 6, version: 0x00050014, at 0xfee0 cpu2 (AP): apic id: 1, version: 0x00050014, at 0xfee0 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec0 io1 (APIC): apic id: 3, version: 0x00178020, at 0xfec8 io2 (APIC): apic id: 4, version: 0x00178020, at 0xfec80400 Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 24 entries at 0xc00fde40 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 IOAPIC #0 intpin 16 -> irq 2 IOAPIC #0 intpin 19 -> irq 10 IOAPIC #0 intpin 18 -> irq 11 pci0: at device 0.1 (no driver attached) pcib1: at device 2.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.HLB_ - AE_NOT_FOUND pci1: on pcib1 pci1: at device 28.0 (no driver attached ) pcib2: at device 29.0 on pci1 pci2: on pcib2 pci1: at device 30.0 (no driver attached ) pcib3: at device 31.0 on pci1 pci3: on pcib3 IOAPIC #1 intpin 4 -> irq 16 IOAPIC #1 intpin 5 -> irq 17 IOAPIC #1 intpin 7 -> irq 18 ahc0: port 0x3000-0x30ff mem 0xfc24-0xfc240fff irq 16 at device 2.0 on pci3 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0x3400-0x34ff mem 0xfc241000-0xfc241fff irq 17 at device 2.1 on pci3 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs em0: port 0x3800-0x381f mem 0xfc20-0xfc21,0xfc22-0xfc23 irq 18 at device 4.0 on pci3 em0: Speed:100 Mbps Duplex:Full uhci0: port 0x2000-0x201f irq 2 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2020-0x203f irq 10 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2040-0x205f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib4: at device 30.0 on pci0 pci4: on pcib4 IOAPIC #0 intpin 17 -> irq 19 pci4: at device 1.0 (no driver attached) fxp0: port 0x4400-0x443f mem 0xfc30-0xfc31 ,0xfc321000-0xfc321fff irq 19 at device 2.0 on pci4 fxp0: Ethernet address 00:30:48:24:da:d4 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x2060-0x206f,0x374-0x377,0x170-0x1 77,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xfc00-0xfc0003ff irq 0 at device 31.1 on pci 0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio
Re: -O2 considered harmful
On Wed, 26 Feb 2003, Dag-Erling Smorgrav wrote: > It seems that with -O2 on ia32 (-march=k6-2 in my case), gcc will in > some cases generate short jumps to targets too far away for the offset > to fit in a single byte. A surefire way to reproduce this is to build > Mesa (or XFree86-4-libraries, which includes parts of Mesa). > > Has anybody else run into this? > > DES > I have seen this as well, using -O2 -march=athlon-xp. The generated assembler tried to stuff -129 into a single byte. -- == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED]Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Yet another ATA-related Kernel trap 12 :-(
Setup: Fujitsu MPG3409AT E disk on external CMD649 controller (the only HD). Kernel trap while booting with timeout for ad0 device. Setting "hw.ata.ata_dma=0" solves the problem. Sources last cvsupped last night (after the last ATA-related commits). Dmesg output attached, but that's about all I can provide - no serial console here. Regards, VladimirCopyright (c) 1992-2003 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 #10: Wed Feb 26 08:31:54 EET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KUSHNIR Preloaded elf kernel "/boot/kernel/kernel" at 0xc0497000. Preloaded elf module "/boot/kernel/if_tun.ko" at 0xc04970a8. Preloaded elf module "/boot/kernel/snd_ds1.ko" at 0xc0497154. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0497200. Preloaded elf module "/boot/kernel/random.ko" at 0xc04972ac. Preloaded elf module "/boot/kernel/fdc.ko" at 0xc0497358. Preloaded elf module "/boot/kernel/lpt.ko" at 0xc0497400. Preloaded elf module "/boot/kernel/ppi.ko" at 0xc04974a8. Preloaded elf module "/boot/kernel/pps.ko" at 0xc0497550. Preloaded elf module "/boot/kernel/plip.ko" at 0xc04975f8. Preloaded elf module "/boot/kernel/mga.ko" at 0xc04976a4. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc049774c. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451024991 Hz CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387f9ff real memory = 201261056 (191 MB) avail memory = 190349312 (181 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdf10 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x5000-0x500f,0x4000-0x4041,0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: mem 0xe500-0xe57f,0xe400-0xe4003fff,0xe800-0xe9ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe000 64MB info: [drm] Initialized mga 3.0.2 20010321 on minor 0 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 2.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 2.2 (no driver attached) intpm0: port 0x5000-0x500f irq 9 at device 2.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 pci0: at device 14.0 (no driver attached) atapci1: port 0xe400-0xe40f,0xe000-0xe003,0xdc00-0xdc07,0xd800-0xd803,0xd400-0xd407 irq 9 at device 15.0 on pci0 ata2: at 0xd400 on atapci1 ata3: at 0xdc00 on atapci1 pcm0: mem 0xeb00-0xeb007fff irq 10 at device 16.0 on pci0 pcm0: fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pps0: on ppbus0 plip0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 orm0: at iomem 0xc-0xc8fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0 at vga0 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% ad0: 39093MB [79428/16/63] at ata2-master PIO4 acd0: CD-RW <_NEC CD-RW NR-9100A> at ata0-master UDMA33 acd1: CDROM at ata1-master UDMA33 MBREXT Slice 5 on ad0s3: [0] f:00 typ:131 s(CHS):255/254/255 e(CHS):255/254/255 s:63 l:15711507 [1] f:00 typ:5 s(CHS):255/254/255 e(CHS):255/254/255 s:15711570 l:851445 MBREXT Slice 6 on ad0s3: [0] f:00 typ:130 s(CHS):255/254/255 e(CHS):255/254/255 s:63 l:851382 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 Mounting root from ufs:/dev/ad0s2a cd1 at ata1 bus 0 target 0 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present cd0 at ata0 bus 0 target 0 lun 0 cd0: <_NEC CD-RW NR-9100A 2.12> Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not presen
Volunteer with genuine i386 cpu & lots of time wanted.
Is there anybody out there who can try to run a straight -current on a _real_ i386 class CPU ? Ie, not a i486, not a Cyrix, not an AMD but a genuine Intel i386DX (SX would be but too suicidal to be informative). I am also not interested in people running heavily modified source trees, it is -current I am interested in. (It's OK to fiddle the kernel config and hints of course.) If somebody has the time and inclination, I have a number of questions I would like answers to: 1. Does -current even boot on that vintage of hardware any more ? 2. Does it survive a kernel (GENERIC) build ? 2a. Does the clock track wall-clock time correctly while doing so ? 3. Does it survive a buildworld ? 3a. Does the clock track wall-clock time correctly while doing so ? 4. Can ntpd run against some random (but decent) NTP server steer the clock ? 1) If the machine is idle 2) During buildworld. Please notice if a) ntpd resorts to clock steps b) ntpd exits c) ntpd core dumps Thanks in advance! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make buildworld TARGET_ARCH=foobar seems to be broken
hi, there! Seems that for some reason gengenrtl is not built when doing 'make build-tools' in gnu/usr.bin/cc/cc_tools. As a result 'make buildworld TARGET_ARCH=foobar' is broken. Below is the output of 'make buildworld TARGET_ARCH=alpha' of recent HEAD on 4.7-STABLE/i386 ===> gnu/usr.bin/cc/cc_tools cc -O -pipe -mcpu=ev4 -mtune=ev5 -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" -I/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -static -DGENERATOR_FILE-c /usr/fbsd/HEAD/contrib/gcc/gengenrtl.c cc -O -pipe -mcpu=ev4 -mtune=ev5 -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" -I/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -static -DGENERATOR_FILE -o gengenrtl gengenrtl.o -O -pipe -mcpu=ev4 -mtune=ev5 -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" -I/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -static -DGENERATOR_FILE -o gengenrtl gengenrtl.o ./gengenrtl > genrtl.c ./gengenrtl: 6: Syntax error: ")" unexpected *** Error code 2 Stop in /usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools. *** Error code 1 Stop in /usr/fbsd/HEAD/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/fbsd/HEAD/gnu/usr.bin. *** Error code 1 Stop in /usr/fbsd/HEAD/gnu. *** Error code 1 Stop in /usr/fbsd/HEAD. *** Error code 1 Stop in /usr/fbsd/HEAD. *** Error code 1 Stop in /usr/fbsd/HEAD. Running file in object directory shows the following: [EMAIL PROTECTED]:/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools$file gen* | grep '^gen[a-z]*:' genattr:ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, not stripped genattrtab: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, not stripped [...] gengenrtl: ELF 64-bit LSB executable, Alpha (unofficial), version 1 (FreeBSD), statically linked, not stripped [...] genrecog: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, not stripped By the way why gengenrtl is executed at all? [EMAIL PROTECTED]:/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools$./gengenrtl ./gengenrtl: Exec format error. Binary file not executable. [EMAIL PROTECTED]:/usr/obj/alpha/usr/fbsd/HEAD/gnu/usr.bin/cc/cc_tools$env FOO=bar ./gengenrtl ./gengenrtl: 6: Syntax error: ")" unexpected (the shell is tcsh) /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
Hi, Just a little question: Does -march=k6-2 implies -m3dnow? Or -march=pentiumpro implies -mmmx? I always thought that when I use -march it will enable other porcessor specific optimizations like mmx and 3dnow (if available). Thanks, Nuno Teixeira On Wed, Feb 26, 2003 at 05:06:35PM -0300, Fred Souza wrote: > > I was recently a participant in a thread in another forum where all sorts > > of people, including a well respected gcc developer, said categorically > > that the latest (stock) gcc produces correct code with -O2 in all cases on > > ia32. If it doesn't, the gcc folks would like a bug report. > > I use -O3 -mmmx -m3dnow -march=k6-2 on nearly everything (things that > break with that many optimization, such as XFree86-4-libraries, I > "downgrade" to the highest optimization possible - usually -O2), and > I'm not noticing any bad impacts because of it. > > And by "nearly everything" I even meant the kernel (yes, I can respect > if anyone screams "[EMAIL PROTECTED]" ;-) > > > Fred > > > -- > Insulting a person's appearance: > > That's what they mean by dark and handsome. When it's dark, you're > handsome... -- /* PGP fingerprint: C6D1 06ED EB54 A99C 6B14 6732 0A5D 810D 727D F6C6 */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Hyperactive ICH2 sound (with workaround)
On a recently compiled current the sound from an Intel 82801BA integrated sound chip seems to be accelerated (high pitched and too fast). While it's amusing to listen to certain songs this way, I don't think it should be the default mode of operation ;) Relevant dmesg output: pcm0: port 0xdc40-0xdc7f,0xd800-0xd8ff irq 10 at device 31.5 on pci0 pcm0: pcm0: measured ac97 link rate at 51200 Hz and sysctl hw.snd.pcm0: hw.snd.pcm0.buffersize: 16384 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.ac97rate: 48000 Here is the output from another system with the same hardware running 5.0-RELEASE: pcm0: port 0xcc40-0xcc7f,0xc800-0xc8ff irq 10 at device 31.5 on pci0 pcm0: measured ac97 link rate at 55939 Hz and the sysctl: hw.snd.pcm0.buffersize: 16384 hw.snd.pcm0.vchans: 4 hw.snd.pcm0.ac97rate: 55939 So it looks like the AC97 link rate measurement isn't working right. Manually setting it with "sysctl hw.snd.pcm0.ac97rate=55939" seems to correct the problem. Current from about a week ago was working fine. A kernel from last night exhibits this problem, as does one cvsupped this morning. I'll go trawling through CVS when I have some free time. Not really a big deal, just wanted to make sure somebody was aware of the problem and also to get the workaround into the mailing list archives... Craig To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Low swap kernel panic
Hello, while recompiling all of my ports (portupgrade -a -f), I've had my notebook panic with the following messages (see at the bottom). I have a limited amount of swap (paging out of a 64Meg file : swapfile="/usr/swap0" in /etc/rc.conf), and I was running KDE at the time : noticing a konqueror window had been closed, I have relaunched one konqueror, then boom ! there was also a lock order reversal with : $FreeBSD: src/sys/kern/kern_synch.c,v 1.211 2003/02/17 09:55:09 julian Exp $ $FreeBSD: src/sys/vm/vm_pageout.c,v 1.226 2003/02/09 20:40:36 alc Exp $ the kernel and userland are in sync and have been cvsuped and recomplied on the day before yesterday : FreeBSD XXX 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Mon Feb 24 23:11:57 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 the kernel config file is plain GENERIC. /var/log/messages extract : -- Feb 26 21:15:16 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:15:16 portable-cur last message repeated 109 times Feb 26 21:15:16 portable-cur kernel: pid 59119 (kdeinit), uid 1001, was killed: out of swap space Feb 26 21:20:14 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:20:18 portable-cur last message repeated 144 times Feb 26 21:20:18 portable-cur kernel: pid 63079 (kdesktop_lock), uid 1001, was killed: out of swap space Feb 26 21:26:04 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:26:08 portable-cur last message repeated 97 times Feb 26 21:26:09 portable-cur kernel: pid 67198 (kdesktop_lock), uid 1001, was killed: out of swap space Feb 26 21:31:57 portable-cur kernel: swap_pager_getswapspace: failed Feb 26 21:33:19 portable-cur syslogd: kernel boot file is /boot/kernel/kernel Feb 26 21:33:20 portable-cur kernel: /usr/src/sys/kern/kern_synch.c:152: sleeping with "process lock" locked from /usr/src/sys/vm/vm_pageout.c:1184 Feb 26 21:33:20 portable-cur kernel: /usr/src/sys/kern/kern_synch.c:152: sleeping with "process lock" locked from /usr/src/sys/vm/vm_pageout.c:1184 Feb 26 21:33:20 portable-cur kernel: panic: sleeping thread owns a mutex Feb 26 21:33:20 portable-cur kernel: Feb 26 21:33:20 portable-cur kernel: syncing disks, buffers remaining... panic:bremfree: bp 0xc5b6dfe0 not locked Feb 26 21:33:20 portable-cur kernel: Uptime: 1d21h22m41s Feb 26 21:33:20 portable-cur kernel: Terminate ACPI Feb 26 21:33:20 portable-cur kernel: Automatic reboot in 15 seconds - press a key on the console to abort Feb 26 21:33:20 portable-cur kernel: Rebooting... /var/run/dmesg.boot : [741 "swap_pager_getswapspace: failed" lines deleted] swap_pager_getswapspace: failed swap_pager_getswapspace: failed swap_pager_getswapspace: failed pid 75533 (kdesktop_lock), uid 1001, was killed: out of swap space /usr/src/sys/kern/kern_synch.c:152: sleeping with "process lock" locked from /usr/src/sys/vm/vm_pageout.c:1184 /usr/src/sys/kern/kern_synch.c:152: sleeping with "process lock" locked from /usr/src/sys/vm/vm_pageout.c:1184 panic: sleeping thread owns a mutex syncing disks, buffers remaining... panic: bremfree: bp 0xc5b6dfe0 not locked Uptime: 1d21h22m41s Terminate ACPI Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-2003 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 #10: Mon Feb 24 23:11:57 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc070a000. Preloaded elf module "/boot/kernel/snd_ds1.ko" at 0xc070a0a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc070a154. Preloaded elf module "/boot/kernel/firewire.ko" at 0xc070a200. Preloaded elf module "/boot/kernel/sbp.ko" at 0xc070a2b0. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc070a358. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 595574279 Hz CPU: Intel Pentium III (595.57-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 201261056 (191 MB) avail memory = 187871232 (179 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00fdf40 Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0x4000-0x40ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.VID0 - AE_NOT_FOUND pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata
sparc64 tinderbox failure
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html -- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating >>> /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- ===> usr.bin/xlint/llib llib-lposix: stat.h(132): syntax error [249] stdio.h(79): warning: struct __sFILEX never defined [233] signal.h(207): warning: struct __siginfo never defined [233] *** Error code 1 Stop in /tinderbox/sparc64/src/usr.bin/xlint/llib. *** Error code 1 Stop in /tinderbox/sparc64/src/usr.bin/xlint. *** Error code 1 Stop in /tinderbox/sparc64/src/usr.bin. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
On Wed, Feb 26, 2003 at 05:06:35PM -0300, Fred Souza wrote: > > I was recently a participant in a thread in another forum where all sorts > > of people, including a well respected gcc developer, said categorically > > that the latest (stock) gcc produces correct code with -O2 in all cases on > > ia32. If it doesn't, the gcc folks would like a bug report. > > I use -O3 -mmmx -m3dnow -march=k6-2 on nearly everything (things that > break with that many optimization, such as XFree86-4-libraries, I > "downgrade" to the highest optimization possible - usually -O2), and > I'm not noticing any bad impacts because of it. > > And by "nearly everything" I even meant the kernel (yes, I can respect > if anyone screams "[EMAIL PROTECTED]" ;-) > Is it just me, or does mozilla break when things are compiled with -march=athlon-xp? I'm not sure what happens, but mozilla starts to load, a window flashes up briefly before mozilla quits. Running dbg on it says that it segfaults in WindowGetHeight() or some such function. When I recompile _everything_ back using -O -march=pentiumpro it works again. I'm sure I've compiled it for athlon-xp before on 5.0-RELEASE, has something changed to break it? Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X server stops working after recent 5.0-RELEASE -> 5.0-CURRENT upgrade
On Wed, Feb 26, 2003 at 02:15:44PM -0500, Andre Guibert de Bruet wrote: > > First off, I have no idea what might have caused X to break on your > systems. I guess I'm lucky to have not run into such problems... > > Would you mind doing a binary search (using date tags) to determine which > commit caused the breakage between 5.0-R and the date when you first > started having problems? Once it has been identified, a fix can be cooked > up. > The problem is already fixed in the XFree86 source tree, which is scheduled to be tagged for the 4.3 release on 27 Feb 03. Check the log history for the radeon driver: http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/\ drivers/ati/radeon_dri.c. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: build busted in xlint: stat.h related?
Andrew Gallatin <[EMAIL PROTECTED]> writes: > > I just tried to buildworld, and xlint crapped out like this: > > ===> usr.bin/xlint/llib > lint -cghapbx -Cposix /usr/src/usr.bin/xlint/llib/llib-lposix > lint -cghapbx -Cstdc /usr/src/usr.bin/xlint/llib/llib-lstdc > llib-lposix: > llib-lstdc: > stdio.h(79): warning: struct __sFILEX never defined [233] > Lint pass2: > stat.h(132): syntax error [249] > stdio.h(79): warning: struct __sFILEX never defined [233] > signal.h(207): warning: struct __siginfo never defined [233] > *** Error code 1 > > I'm rebuilding now with your latest stat.h change reverted.. I committed a fix. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "NTLDR missing" after 5-RELEASE install
Darryl Okahata writes: > [...] > I installed 5.0 with the booteasy MBR on my IBM laptop, and it > worked fine. The problem I had was that *ANY* MBR-based boot program > interfered with IBM's special "product recovery" software, and so I > instead decided to just use Win2K/XP's boot mechanism to boot FreeBSD > (as I explained in my previous message). > > [ Yes, FreeBSD and XP (in my case) would still have worked if I kept > booteasy, but I really wanted to keep IBM's product recovery software, > and so I switched to using 2K/XP's method. In hindsight, that's > probably the best approach, as it doesn't require any MBR changes or > boot floppies/CDs. ] What we're doing is almost the same thing. In your case, your windows partition is the active partition, so you run the vendor's MBR, which jumps to the Windows loader, which jumps to whatever you choose. MBR --> NTLR ---+--> FreeBSD | +--> Windows I mark the partition that contains grub active (these days have a freebsd world in my second slice/partition, with grub installed at the beginning of that) and use it to jump wherever. MBR --> GRUB ---+--> FreeBSD | +--> Windows Only differences are which partition we mark active and what boot loader lives there. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Checksum offload support for Intel 82550/82551
> I think my problem is not that hard. This bug only occurs when you are > using CURRENT (or 5.0 RELEASE) from (I think) the point where BPF changed. Actually, there's something else than changed. The ng_fec module tries to set ifp->if_output to ng_fec_output() so that it can do some output processing on frames, however, later it would call ether_ifattach(), which would set ifp->if_output to ether_output(), which wouldn't work. I just commited a fix for this. (I verified that I can successfully send packets via fec0.) I also modified the input handling so that it no longer uses the ng_ether_input_p hook. Now that FreeBSD 5.x has an ifp->if_input vector, it's not necessary to abuse this hook anymore. This avoids a collision with the ng_ether module, which is what was supposed to be using this hook in the first place. Let me know how this works. -Bill -- = -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu [EMAIL PROTECTED] | Wind River Systems = "If stupidity were a handicap, you'd have the best parking spot." = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
> I was recently a participant in a thread in another forum where all sorts > of people, including a well respected gcc developer, said categorically > that the latest (stock) gcc produces correct code with -O2 in all cases on > ia32. If it doesn't, the gcc folks would like a bug report. I use -O3 -mmmx -m3dnow -march=k6-2 on nearly everything (things that break with that many optimization, such as XFree86-4-libraries, I "downgrade" to the highest optimization possible - usually -O2), and I'm not noticing any bad impacts because of it. And by "nearly everything" I even meant the kernel (yes, I can respect if anyone screams "[EMAIL PROTECTED]" ;-) Fred -- Insulting a person's appearance: That's what they mean by dark and handsome. When it's dark, you're handsome... pgp0.pgp Description: PGP signature
build busted in xlint: stat.h related?
I just tried to buildworld, and xlint crapped out like this: ===> usr.bin/xlint/llib lint -cghapbx -Cposix /usr/src/usr.bin/xlint/llib/llib-lposix lint -cghapbx -Cstdc /usr/src/usr.bin/xlint/llib/llib-lstdc llib-lposix: llib-lstdc: stdio.h(79): warning: struct __sFILEX never defined [233] Lint pass2: stat.h(132): syntax error [249] stdio.h(79): warning: struct __sFILEX never defined [233] signal.h(207): warning: struct __siginfo never defined [233] *** Error code 1 I'm rebuilding now with your latest stat.h change reverted.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
On Wed, 26 Feb 2003, Dag-Erling Smorgrav wrote: > It seems that with -O2 on ia32 (-march=k6-2 in my case), gcc will in > some cases generate short jumps to targets too far away for the offset > to fit in a single byte. A surefire way to reproduce this is to build > Mesa (or XFree86-4-libraries, which includes parts of Mesa). I was recently a participant in a thread in another forum where all sorts of people, including a well respected gcc developer, said categorically that the latest (stock) gcc produces correct code with -O2 in all cases on ia32. If it doesn't, the gcc folks would like a bug report. Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "NTLDR missing" after 5-RELEASE install
[EMAIL PROTECTED] (George Hartzell) wrote: > I'm pretty sure that it's not operator error on my part, since it > happened several times. I suspect that there aren't that many people > playing with 5.0 that don't install the standard boot stuff, and so > that path isn't exercised too much. I installed 5.0 with the booteasy MBR on my IBM laptop, and it worked fine. The problem I had was that *ANY* MBR-based boot program interfered with IBM's special "product recovery" software, and so I instead decided to just use Win2K/XP's boot mechanism to boot FreeBSD (as I explained in my previous message). [ Yes, FreeBSD and XP (in my case) would still have worked if I kept booteasy, but I really wanted to keep IBM's product recovery software, and so I switched to using 2K/XP's method. In hindsight, that's probably the best approach, as it doesn't require any MBR changes or boot floppies/CDs. ] -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X server stops working after recent 5.0-RELEASE -> 5.0-CURRENTupgrade
On Wed, 26 Feb 2003, Andre Guibert de Bruet wrote: > > On Wed, 26 Feb 2003, Daniel Eischen wrote: > > > On Wed, 26 Feb 2003, Paul Mather wrote: > > > Yesterday evening I upgraded a Gateway 450 laptop from 5.0-RELEASE-p3 > > > to 5.0-CURRENT. Unfortunately, as a byproduct of that upgrade, > > > I can no longer start X. Instead, it now aborts with Signal 10. :-( > > > > [...] > > > > > Has anyone else experienced problems with X ceasing to work after a > > > 5.0-RELEASE -> 5.0-CURRENT upgrade?? I did not change X at all during > > > the upgrade. All I did was rebuilt world and kernel, as per > > > /usr/src/UPDATING. After discovering X no longer worked, I rebuilt my > > > X server and X libraries ports via portupgrade -f, but still have the > > > same problem. > > > > I posted the same exact problem on this list last week (see "What > > broke X between 5.0R and recent current?" as subject line). > > > > I got two suggestions. One was to upgrade to the latest > > version of XFree86, and the other was to add an explicit > > mode line for the screen size to your XF86Config file. > > Unfortunately, I didn't get the latter suggestion until > > I had went through the pain and effort of getting the > > latest version of XFree86 (right from the CVS repo, the > > last 4.3 release candidate did _not_ work) and rebuilding > > it and KDE. > > > > The good news is that it works with XFree86 from their CVS > > repo. I didn't use a port to build it, I just cvsup'd > > their tree and did a 'make World' and it just worked. > > First off, I have no idea what might have caused X to break on your > systems. I guess I'm lucky to have not run into such problems... > > Would you mind doing a binary search (using date tags) to determine which > commit caused the breakage between 5.0-R and the date when you first > started having problems? Once it has been identified, a fix can be cooked > up. Uh, yeah I would mind :-) I've got an up-to-date system with working X (that I can't do 'make package' on). I don't have the time to do a binary search and figure out exactly what broke it; I've got other FreeBSD chores to do. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UDMA66 vs ATAPI_DEVICE(atadev)?
Soeren Schmidt writes: > > ATAPI_DEVICE is used on those controllers that cannot do ATAPI DMA, > the test here is bogusly reversed, I'll fix asap... Aha! Thanks! Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't load if_gif.ko
* De: Brooks Davis <[EMAIL PROTECTED]> [ Data: 2003-02-26 ] [ Subjecte: Re: can't load if_gif.ko ] > On Wed, Feb 26, 2003 at 01:12:59PM -0600, Juli Mallett wrote: > > It's easy to change kldload to have something like "Failed to load module", > > but changing the result of strerror(errno) isn't possible in this case. It > > is possible, however, to check for obtuse errno values being used that we > > KNOW mean something in this context, and give something more informative. > > I wonder if we shouldn't add ENOSYMBOL translating to "Unresolved > symbol" for this case. Or we could just work with the contracts that the kld code has made with the world already, and just deal with them appropriately in our tools. -- Juli Mallett <[EMAIL PROTECTED]> - AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer - ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD - Never trust an ELF, COFF or Mach-O! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't load if_gif.ko
On Wed, Feb 26, 2003 at 01:12:59PM -0600, Juli Mallett wrote: > It's easy to change kldload to have something like "Failed to load module", > but changing the result of strerror(errno) isn't possible in this case. It > is possible, however, to check for obtuse errno values being used that we > KNOW mean something in this context, and give something more informative. I wonder if we shouldn't add ENOSYMBOL translating to "Unresolved symbol" for this case. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature
Re: X server stops working after recent 5.0-RELEASE -> 5.0-CURRENTupgrade
On Wed, 26 Feb 2003, Daniel Eischen wrote: > On Wed, 26 Feb 2003, Paul Mather wrote: > > Yesterday evening I upgraded a Gateway 450 laptop from 5.0-RELEASE-p3 > > to 5.0-CURRENT. Unfortunately, as a byproduct of that upgrade, > > I can no longer start X. Instead, it now aborts with Signal 10. :-( > > [...] > > > Has anyone else experienced problems with X ceasing to work after a > > 5.0-RELEASE -> 5.0-CURRENT upgrade?? I did not change X at all during > > the upgrade. All I did was rebuilt world and kernel, as per > > /usr/src/UPDATING. After discovering X no longer worked, I rebuilt my > > X server and X libraries ports via portupgrade -f, but still have the > > same problem. > > I posted the same exact problem on this list last week (see "What > broke X between 5.0R and recent current?" as subject line). > > I got two suggestions. One was to upgrade to the latest > version of XFree86, and the other was to add an explicit > mode line for the screen size to your XF86Config file. > Unfortunately, I didn't get the latter suggestion until > I had went through the pain and effort of getting the > latest version of XFree86 (right from the CVS repo, the > last 4.3 release candidate did _not_ work) and rebuilding > it and KDE. > > The good news is that it works with XFree86 from their CVS > repo. I didn't use a port to build it, I just cvsup'd > their tree and did a 'make World' and it just worked. First off, I have no idea what might have caused X to break on your systems. I guess I'm lucky to have not run into such problems... Would you mind doing a binary search (using date tags) to determine which commit caused the breakage between 5.0-R and the date when you first started having problems? Once it has been identified, a fix can be cooked up. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Checksum offload support for Intel 82550/82551
Hello,
> I can't easily drop everything and slap together a test setup with
> exactly the right software and hardware I need to debug everyone's
> particular problem.
That's clear.
> ("This bug only occurs in -CURRENT as of 30 seconds ago and on an
> UltraSPARC 10 with 16 if_dc interfaces and I need you to fix it _NOW_
> pleasepleasepleaseI'llevengiveyouahandjob.")
:)
I think my problem is not that hard. This bug only occurs when you are
using CURRENT (or 5.0 RELEASE) from (I think) the point where BPF changed.
> > You may know, or not it is now part of FreeBSD, the only problem is
> > that it does not work.
> I'm shocked. Shocked, I tell you.
Yes. That's very dramatic. :)
> This particular PR relates to using ng_fec with BPF (i.e. tcpdump fec0
> blows up). The code has evidently rotted quite a bit since it was
> imported. I just fixed it.
Thanks.
BTW, it still doesn't work.
I do:
kldload ng_fec
ifconfig fxp0 up; ifconfig fxp1 up
ngctl ... (exactly what's in sample_script)
ifconfig fec0 1.2.3.4 netmask 255.255.255.252 up
route add default 1.2.3.3
1.2.3.3 does not answer for ICMP pings.
The switch says:
Port-channel13 is down, line protocol is down
Hardware is EtherChannel, address is .. (bia ..)
MTU 1526 bytes, BW 1 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Auto-duplex, Auto-speed
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
I got two kernel messages regarding that the interfaces are up in the
etherchannel. If I pull out one of the cables and reconnect it I get the
down/up normally.
It seems that I can't crash now with tcpdump.
I see the incoming packets on fxp[0-1], I see the outgoing ones on fec0,
but there is no connection between the two groups.
> Like I said, it depends on time and availability of resources.
Sadfully, I can't provide you more time, but can provide remote access to
resources.
--[ Free Software ISOs - http://www.fsn.hu/?f=download ]--
Attila Nagy e-mail: [EMAIL PROTECTED]
Free Software Network (FSN.HU)phone @work: +361 210 1415 (194)
cell.: +3630 306 6758
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: can't load if_gif.ko
* De: Bruce Cran <[EMAIL PROTECTED]> [ Data: 2003-02-26 ] [ Subjecte: Re: can't load if_gif.ko ] > On Wed, Feb 26, 2003 at 03:30:30PM -0300, Daniel C. Sobral wrote: > > It seems something has gone wrong on current wrt if_gif: > > > > [EMAIL PROTECTED] etc]# ifconfig gif0 create > > ifconfig: SIOCIFCREATE: Invalid argument > > [EMAIL PROTECTED] etc]# kldload if_gif > > kldload: can't load if_gif: No such file or directory > > > > It works for vlan, so that's not a general module/ifmodule loading problem. > > > > Very recent current. > > > > It doesn't work on 4.7 either if IPv6 isn't compiled into the kernel. > If you look at the kernel messages it might > give you more information. It might be a different problem, but mine was > wanting IPv6, and refused to > load without it. This type of error reminds me of trying to run FreeBSD > binaries on Linux - you run ./bsd_app and it says 'No such file or directory' > which is less than helpful, while I generally find FreeBSD error messages to be a lot > more informative. Would it be possible for this message to be > reworded to be more helpful? The file does indeed exist, it's just that > the system cannot load it. Or, if a module fails to load, maybe prompt the > user to look at the kernel messages for any error messages? It's easy to change kldload to have something like "Failed to load module", but changing the result of strerror(errno) isn't possible in this case. It is possible, however, to check for obtuse errno values being used that we KNOW mean something in this context, and give something more informative. -- Juli Mallett <[EMAIL PROTECTED]> - AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer - ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD - Never trust an ELF, COFF or Mach-O! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't load if_gif.ko
On Wed, Feb 26, 2003 at 03:30:30PM -0300, Daniel C. Sobral wrote: > It seems something has gone wrong on current wrt if_gif: > > [EMAIL PROTECTED] etc]# ifconfig gif0 create > ifconfig: SIOCIFCREATE: Invalid argument > [EMAIL PROTECTED] etc]# kldload if_gif > kldload: can't load if_gif: No such file or directory > > It works for vlan, so that's not a general module/ifmodule loading problem. > > Very recent current. > It doesn't work on 4.7 either if IPv6 isn't compiled into the kernel. If you look at the kernel messages it might give you more information. It might be a different problem, but mine was wanting IPv6, and refused to load without it. This type of error reminds me of trying to run FreeBSD binaries on Linux - you run ./bsd_app and it says 'No such file or directory' which is less than helpful, while I generally find FreeBSD error messages to be a lot more informative. Would it be possible for this message to be reworded to be more helpful? The file does indeed exist, it's just that the system cannot load it. Or, if a module fails to load, maybe prompt the user to look at the kernel messages for any error messages? Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UDMA66 vs ATAPI_DEVICE(atadev)?
It seems Andrew Gallatin wrote: > > After recent ATA commits, my Promise UDMA66 controller is now running > its drives in PIO4 mode. Previously, UDMA66 was working fine. > > Here's a dmesg snippet: > > atapci0: port 0xdf00-0xdf3f,0xdfe0-0xdfe3,0xdfa8-0xd > faf,0xdfe4-0xdfe7,0xdff0-0xdff7 mem 0xfc8a-0xfc8b irq 2 at device 2.0 on > pci0 > ata2: at 0xdff0 on atapci0 > ata3: at 0xdfa8 on atapci0 > <..> > ad4: 19092MB [38792/16/63] at ata2-master PIO4 > > The controller itself looks like this: > > [EMAIL PROTECTED]:2:0: class=0x018000 card=0x4d33105a chip=0x4d38105a rev=0x01 > hdr=0x00 > vendor = 'Promise Technology Inc' > device = 'PDC20262 FastTrak66 EIDE Controller' > class= mass storage > > > I've found that I can recover from this problem by forcing > ATAPI_DEVICE() to always return 1. It seems to want to return 0 > for devices not on the primary ata controller. > > I'm confused.. What's the point of ATAPI_DEVICE()? Am I not allowed > to use extra controllers anymore? ATAPI_DEVICE is used on those controllers that cannot do ATAPI DMA, the test here is bogusly reversed, I'll fix asap... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: HyperThreading not working?
On 26-Feb-2003 Slawek Zak wrote: > Hi, > > I'm in the process of installing 5.0-RELEASE-p3 on a Dell PowerEdge > 2600 server. It has two HyperThreading Xeon 2.4Ghz processors, but > HyperThreading is not working in FreeBSD. I guess that four > processors should be visible in the system after boot. Yes - I've > enabled `Logical Processors' in BIOS. BIOS revision is the latest > available. > > Any thoughts? I attach full dmesg and mptable output. Kernel > config too. 5.0 doesn't support HyperThreading. The upcoming 5.1 and 4.8 releases will support it. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
UDMA66 vs ATAPI_DEVICE(atadev)?
Hi Soren, After recent ATA commits, my Promise UDMA66 controller is now running its drives in PIO4 mode. Previously, UDMA66 was working fine. Here's a dmesg snippet: atapci0: port 0xdf00-0xdf3f,0xdfe0-0xdfe3,0xdfa8-0xd faf,0xdfe4-0xdfe7,0xdff0-0xdff7 mem 0xfc8a-0xfc8b irq 2 at device 2.0 on pci0 ata2: at 0xdff0 on atapci0 ata3: at 0xdfa8 on atapci0 <..> ad4: 19092MB [38792/16/63] at ata2-master PIO4 The controller itself looks like this: [EMAIL PROTECTED]:2:0: class=0x018000 card=0x4d33105a chip=0x4d38105a rev=0x01 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20262 FastTrak66 EIDE Controller' class= mass storage I've found that I can recover from this problem by forcing ATAPI_DEVICE() to always return 1. It seems to want to return 0 for devices not on the primary ata controller. I'm confused.. What's the point of ATAPI_DEVICE()? Am I not allowed to use extra controllers anymore? Thanks, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X server stops working after recent 5.0-RELEASE -> 5.0-CURRENTupgrade
On Wed, 26 Feb 2003, Paul Mather wrote: > Yesterday evening I upgraded a Gateway 450 laptop from 5.0-RELEASE-p3 > to 5.0-CURRENT. Unfortunately, as a byproduct of that upgrade, > I can no longer start X. Instead, it now aborts with Signal 10. :-( [...] > Has anyone else experienced problems with X ceasing to work after a > 5.0-RELEASE -> 5.0-CURRENT upgrade?? I did not change X at all during > the upgrade. All I did was rebuilt world and kernel, as per > /usr/src/UPDATING. After discovering X no longer worked, I rebuilt my > X server and X libraries ports via portupgrade -f, but still have the > same problem. I posted the same exact problem on this list last week (see "What broke X between 5.0R and recent current?" as subject line). I got two suggestions. One was to upgrade to the latest version of XFree86, and the other was to add an explicit mode line for the screen size to your XF86Config file. Unfortunately, I didn't get the latter suggestion until I had went through the pain and effort of getting the latest version of XFree86 (right from the CVS repo, the last 4.3 release candidate did _not_ work) and rebuilding it and KDE. The good news is that it works with XFree86 from their CVS repo. I didn't use a port to build it, I just cvsup'd their tree and did a 'make World' and it just worked. Be forwarned though; upgrading to this version of X broke KDE and it needed to be rebuilt. KDE does not build cleanly under -current, but I only needed to make 3 small changes so that it would; I've lost them now, but I think all you really need to do is add includes of: #include #include #include to the files that break. If this helps you at all, send thanks to Steve Kargl <[EMAIL PROTECTED]>. -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
can't load if_gif.ko
It seems something has gone wrong on current wrt if_gif: [EMAIL PROTECTED] etc]# ifconfig gif0 create ifconfig: SIOCIFCREATE: Invalid argument [EMAIL PROTECTED] etc]# kldload if_gif kldload: can't load if_gif: No such file or directory It works for vlan, so that's not a general module/ifmodule loading problem. Very recent current. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] If you can get to the faulty part, you don't have the tool to get it off. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
can't load if_gif.ko
It seems something has gone wrong on current wrt if_gif: [EMAIL PROTECTED] etc]# ifconfig gif0 create ifconfig: SIOCIFCREATE: Invalid argument [EMAIL PROTECTED] etc]# kldload if_gif kldload: can't load if_gif: No such file or directory It works for vlan, so that's not a general module/ifmodule loading problem. Very recent current. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] If you can get to the faulty part, you don't have the tool to get it off. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA Tagged Queuing working again?
Hi Soeren, Hi all, it seems to me that ATA TQ is working again with -current as of yesterday :-) My disk is on "atapci0: port 0xc000-0xc00f \ at device 7.1 on pci0" It's an "ad0: 43979MB [89355/16/63] at ata0-master UDMA100" Even if it's obviously not reported as TAGGED, it seems to work as such: 'atacontrol cap 0 0' reports: "ATA channel 0, Master, device ad0: ATA/ATAPI revision5 device model IBM-DTLA-307045 serial number YMDYMH21528 firmware revision TX6OA50C cylinders 16383 heads 16 sectors/track 63 lba supported 90069840 sectors lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes no read ahead yes yes dma queued yes yes 31/1F SMART yes no microcode download no no security yes no power management yes yes advanced power management yes no 0/00 automatic acoustic management yes no 254/FE 128/80" So 'write cache' is disabled and 'dma queued' is enabled, right? At least my 'standard test' (which is a 'tar cvf /dev/null /disk/ports') is not able any more to switch the disk to PIO-Mode - which I tried repeatedly ;-) The only thing I saw were 1,2 stops of about 500ms during the listing of the tar-command but nothing worse happened. With earlier Kernels this indicated a soon lock and switch to PIO... Fine! I hope this stabilizes... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: TCP is still broken
In article you write: >This program, based on one from the Apache 2 configure script, still causes >-current to lock up solid despite the recent bug fixes to the tcptw code. >Explicitly closing connected_s before returning from main() seems to avoid >the problem. Thanks for the test case. I've just committed a fix for this to -current. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "NTLDR missing" after 5-RELEASE install
Andrew Boothman writes: > [...] > It's possible I guess that we both suffered from the same problem. I'd > be inclined to think that it must be operator error over something wrong > with sysinstall since I've not seen people complaining of these problems > before, yet there must be loads of people dual-booting. Having said > that, I still can't understand what I did differently or how to prevent > the same thing from happening in the future. > > I guess I'll just use GRUB or something instead. > > Looks like my Windows drive is heading for a reformat :-/ I'm pretty sure that it's not operator error on my part, since it happened several times. I suspect that there aren't that many people playing with 5.0 that don't install the standard boot stuff, and so that path isn't exercised too much. It happened repeatedly for me, and one of the things that's on my list of things to do is to recreate it and file a PR, but it hasn't risen to the top of the queue yet. It's a bit problematic because I don't really want to loose the contents of that drive (it takes *forever* to get windows and office updated after the intial installs: reboot, reboot, reboot...) and it's not hard to imagine that whatever's bitten me the past few times might get me irrecoverably the next time... GRUB is cool. Backup's of your partition/slice/disklabel info are extra cool. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata dumps broken again
On Wed, 26 Feb 2003, Dag-Erling Smorgrav wrote:
> Top-of-tree -CURRENT:
>
> db> call doadump
> Dumping 639 MB
> ata1: resetting devices ..
> mi_switch(c4fad9ec,f,f,1c,5f74e) at mi_switch+0x21b
> ithread_schedule(c48fb380,1,c4faea50,e99cf84c,c025850c) at ithread_schedule+0xf6
> sched_ithd(f) at sched_ithd+0x38
> Xintr15() at Xintr15+0x6c
> --- interrupt, eip = 0xc017388b, esp = 0xe99cf830, ebp = 0xe99cf84c ---
> critical_exit(0,c489f900,c489f92c,e99cf884,c0128324) at critical_exit+0x2b
> DELAY(a,256c,82,40267d87,0) at DELAY+0x47
> ata_wait(c489f92c,40,0,0,0) at ata_wait+0x84
> ata_command(c489f92c,c6,0,0,10) at ata_command+0x2c5
> ad_reinit(c489f92c,c489f92c,ec) at ad_reinit+0x30
> ata_reinit(c489f900,c489f900,1,e99cf960,e99cf9a8) at ata_reinit+0x265
> addump(c48f3764,c02f67c0,0,18003c00,0,200) at addump+0xe8
> dumpsys(c02cee20,c02cee40,b,e99cf9f8,c016eec0) at dumpsys+0x28b
> doadump(0,0,0,0,0,0,0,0,0,0) at doadump+0x20
> db_fncall(0,0,e99cfaa8,e99cfa60,0) at db_fncall+0x7c
> db_command(c02a3380,c02a31a0,c029de74,c029de78,c028024d) at db_command+0xfb
> db_command_loop(0,0,e99cfc28,c02c1ec8,e99cfb4c) at db_command_loop+0x5c
> db_trap(c,0,1,10,e99cfbe0) at db_trap+0x5e
> kdb_trap(c,0,e99cfbe0) at kdb_trap+0xe6
> trap_fatal(e99cfbe0,c4,c4faea50,12ab9a0,0) at trap_fatal+0x1cc
> trap_pfault(e99cfbe0,0,c4) at trap_pfault+0x154
> trap(18,10,10,c7886300,c4caf500) at trap+0x38b
> calltrap() at calltrap+0x5
> --- trap 0xc, eip = 0xc01e94fb, esp = 0xe99cfc20, ebp = 0xe99cfc60 ---
> in6_pcbbind(c4bc1390,c7886300,c4faea50) at in6_pcbbind+0x1fb
> tcp6_usr_bind(c4caf500,c7886300,c4faea50) at tcp6_usr_bind+0x9f
> sobind(c4caf500,c7886300,c4faea50,c4caf500,e99cfd14) at sobind+0x16
> kern_bind(c4faea50,3,c7886300,c7886300,0) at kern_bind+0x70
> bind(c4faea50) at bind+0x30
> syscall(2f,2f,2f,804a3e0,0) at syscall+0x310
> Xint0x80_syscall() at Xint0x80_syscall+0x1d
> --- syscall (104), eip = 0x280b1a63, esp = 0xbfbffa2c, ebp = 0xbfbffa88 ---
> Context switches not allowed in the debugger.
>
> (kgdb) l *(ad_reinit+0x30)
> 0xc0133770 is in ad_reinit (../../../dev/ata/ata-disk.c:874).
> 869
> 870 /* reinit disk parameters */
> 871 ad_invalidatequeue(atadev->driver, NULL);
> 872 ata_command(atadev, ATA_C_SET_MULTI, 0,
> 873 adp->transfersize / DEV_BSIZE, 0, ATA_WAIT_READY);
> 874 atadev->setmode(atadev, adp->device->mode);
> 875 }
> 876
> 877 void
> 878 ad_print(struct ad_softc *adp)
> (kgdb) l *(ata_command+0x2c5)
> 0xc01287a5 is in ata_command (../../../dev/ata/ata-all.c:1126).
> 1121break;
> 1122
> 1123case ATA_WAIT_READY:
> 1124atadev->channel->active |= ATA_WAIT_READY;
> 1125ATA_OUTB(atadev->channel->r_io, ATA_CMD, command);
> 1126if (ata_wait(atadev, ATA_S_READY) < 0) {
> 1127ata_prtdev(atadev, "timeout waiting for cmd=%02x s=%02x
> e=%02x\n",
> 1128 command,
> atadev->channel->status,atadev->channel->error);
> 1129error = -1;
> 1130}
This seems to be caused by a known bug in ddb itself. Try the following fix.
%%%
Index: db_interface.c
===
RCS file: /home/ncvs/src/sys/i386/i386/db_interface.c,v
retrieving revision 1.70
diff -u -2 -r1.70 db_interface.c
--- db_interface.c 22 Feb 2003 23:41:27 - 1.70
+++ db_interface.c 23 Feb 2003 09:51:52 -
@@ -78,4 +78,5 @@
kdb_trap(int type, int code, struct i386_saved_state *regs)
{
+ u_int ef;
volatile int ddb_mode = !(boothowto & RB_GDB);
@@ -97,4 +98,8 @@
}
+ /* XXX is this correctly placed? SMP stop/start doesn't seem to be. */
+ ef = read_eflags();
+ disable_intr();
+
switch (type) {
case T_BPTFLT: /* breakpoint */
@@ -217,4 +222,7 @@
regs->tf_cs = ddb_regs.tf_cs & 0x;
regs->tf_ds = ddb_regs.tf_ds & 0x;
+
+ write_eflags(ef);
+
return (1);
}
%%%
The ata driver apparently wants to wait (without sleeping), but an
interrupt occurs and the scheduler wants to switch. The patch fixes
letting interrupts occur withing ddb when ddb is entered for most fatal
traps (entrering ddb via a ddb trap doesn't have this bug). The only
obvious bug in the driver is the syntax error in the resetting message.
I don't understand why the scheduler wants to switch. kern_bind()
holds Giant and the interrupt is for ata and the ata interrupt handler
is not INTR_MPSAFE so it shouldn't be switched to. Maybe the interrupt
is shared and is attached to an INTR_MPSAFE handler. Any active
interrupt attached to an INTR_MPSAFE handler would cause this problem,
but the trace doesn't show any others.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Ethernet (xl) will not transmit or receive
> From: "Lucky Green" <[EMAIL PROTECTED]> > Date: Tue, 25 Feb 2003 20:07:45 -0800 > > Kevin wrote: > > I updated my 5.0 system built in late January to RELENG_5_0 on Sunday > > and the Ethernet was not working. I tried again last night with no > > change in behavior. > > > > The system is an AMD K6-2 on an ASUS P5A mobo. I have a 3Com 3c905B > > Ethernet which had been working fine on a kernel built in late > > January. > > > > The dmesg is not too meaningful, but the system shows no errors. It > > simply never receives a packet. ARPs are all incomplete and no packets > > are transmitted although netstat -in indicates that they are. The > > packets never actually reach the wire, though. > > > > I can't believe that no one else has this card, but I didn't find > > anything in the archives on it. > > I experienced the exact same behavior with my GF's GigaByte GA-5AN AMD > K6-2 motherboard. Both a 3COM and a Realtek (yeah, I know...) card > refused to pass packets, staying in hardware loopback. The link light on > both cards would remain on until it appears the device was probed. At > that point the link was lost permanently. The motherboard and both cards > work fine with FreeBSD 4.7, which I even re-tested after the futile > 5.0-RELEASE installation. I even flashed in the latest BIOS, but that > had no effect. (The hardware has since been re-tasked and is no longer > available for testing). Thanks for all of the responses, but there was no bug biting me, just a dumb error that resulted in my having out-of-sync sources and building the if_xl driver from RELENG_5_0 against sources for current. I won't bother going through how I messed things up so badly, but it's all better, now. Thanks again to all who replied and I hope you all figure out what is causing your problems. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "NTLDR missing" after 5-RELEASE install
walt <[EMAIL PROTECTED]> wrote: > For example, IIRC, I just went thru this myself (although it's all so routine > now I can't even remember what I do to bail out anymore) when I installed XP > on a brand new disk and then installed FBSD afterwards. I got the MBR screwed > up just like you, then ran the XP install disk in "Repair" mode which got XP > to boot again but overwrote the FBSD booter. So all I did was boot my trusty > GRUB floppy and reinstalled GRUB on the MBR in about 60 seconds and -- done. A better way is to *NOT* install any special boot loader, and just use Win2K/XP's boot mechanism to switch between 2K/XP and FreeBSD. The advantage here is that you don't have to touch the boot sector which, as we've seen, can cause problems with some desktops/laptops. For more information, see: http://bsdatwork.com/sections.php?op=viewarticle&artid=3 (This is for the case where Windows & FreeBSD are on the SAME drive.) (Also read the OpenBSD section for additional WinXP info.) http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
On Wed, 26 Feb 2003, Dag-Erling Smorgrav wrote: > It seems that with -O2 on ia32 (-march=k6-2 in my case), gcc will in > some cases generate short jumps to targets too far away for the offset > to fit in a single byte. A surefire way to reproduce this is to build > Mesa (or XFree86-4-libraries, which includes parts of Mesa). The assembler generates these. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HyperThreading not working?
Hi, I'm in the process of installing 5.0-RELEASE-p3 on a Dell PowerEdge 2600 server. It has two HyperThreading Xeon 2.4Ghz processors, but HyperThreading is not working in FreeBSD. I guess that four processors should be visible in the system after boot. Yes - I've enabled `Logical Processors' in BIOS. BIOS revision is the latest available. Any thoughts? I attach full dmesg and mptable output. Kernel config too. Thanks, /S machine i386 cpu I686_CPU ident W3 maxusers0 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=7000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev # output. Adds ~215k to driver. # Debugging for use in -current #optionsDDB #Enable the kernel debugger #optionsINVARIANTS #Enable calls of extra sanity checking #optionsINVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS #optionsWITNESS #Enable checks to detect deadlocks and cycles #optionsWITNESS_SKIPSPIN#Don't run witness on spinlocks for speed # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI peripherals device scbus # SCSI bus (required) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers device amr # AMI MegaRAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #optionsXSERVER # support for X server on a vt console #optionsFAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # PCI Ethernet NICs. device em # Intel PRO/1000 adapter Gigabit Ethernet Card # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop# Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) de
SCHED_ULE oddities
Hi Just for fun I tried out SCHED_ULE once again, using todays source. What I got was really odd situation that my newly installed kernel (and modules) didn't find the way to disk and loader complained about missing kernel on next boot. The /boot/kernel directory was simply missing and / filesystem dirty. Smells very similar to the problems with unclean shutdown (buffers not written out to disk) circulating in -current recently, but as I didn't have the serial console open while booting, can't say for sure. For the curious the procedure was as follows: checkout new sources buildworld/installworld build new kernel/install new kernel immediately do shutdown -r now repeat the last two steps as long as you wish or until the problem \ appears -- Vallo Kallaste To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: signals still broken ?
On Thu, Feb 27, 2003 at 01:10:03AM +1100, Tim Robbins wrote: > On Wed, Feb 26, 2003 at 06:25:39AM -0500, Mike Makonnen wrote: > > > The following program is stuck in pause(3) forever. I have reproduced the bug in > > 5.0-RELEASE, but 4.7-STABLE behaves as expected: the child resumes upon > > receiving SIGCONT. > > I spent a while trying to decipher the 5.x signal code and I think I have > spotted the code responsible for the difference in behaviour between > 5.x and 4.7. The difference is that 5.x drops SIGCONT when the process > is already "active" even when a handler is installed for that signal. > > Here is a patch to try: [...] Never mind, I guess David beat me to it (kern_sig.c 1.211). Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: signals still broken ?
On Wed, Feb 26, 2003 at 06:25:39AM -0500, Mike Makonnen wrote:
> The following program is stuck in pause(3) forever. I have reproduced the bug in
> 5.0-RELEASE, but 4.7-STABLE behaves as expected: the child resumes upon
> receiving SIGCONT.
I spent a while trying to decipher the 5.x signal code and I think I have
spotted the code responsible for the difference in behaviour between
5.x and 4.7. The difference is that 5.x drops SIGCONT when the process
is already "active" even when a handler is installed for that signal.
Here is a patch to try:
Do not drop SIGCONT signals when a process is not stopped and has
installed a handler for that signal.
Index: kern_sig.c
===
RCS file: /x/freebsd/src/sys/kern/kern_sig.c,v
retrieving revision 1.210
diff -u -r1.210 kern_sig.c
--- kern_sig.c 17 Feb 2003 09:58:11 - 1.210
+++ kern_sig.c 26 Feb 2003 13:41:01 -
@@ -1483,10 +1483,7 @@
* eventually hit thread_suspend_check().
*/
} else if (p->p_state == PRS_NORMAL) {
- if (prop & SA_CONT) {
- /*
-* Already active, don't need to start again.
-*/
+ if ((prop & SA_CONT) && action == SIG_DFL) {
SIGDELSET(p->p_siglist, sig);
goto out;
}
With this patch applied, your test program seems to work properly except
that wait() is called incorrectly (1st arg should be a pointer):
$ ./a.out
sleeping 3s
waiting
a.out: wait(): Bad address
Let me know whether it works for you.
Tim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
lock order reversal
Good day ladies and gents Cvsupping and rebuilding a 5.0 current box to release Monday resulted in the following curiousness: lock order reversal 1st 0xc1190068 process lock (process lock) @ /usr/src/sys/kern/kern_descrip.c:2 112 2nd 0xc11ac934 filedesc structure (filedesc structure) @ /usr/src/sys/kern/kern _descrip.c:2119 Uname -a: FreeBSD xxx.xxx.xxx 5.0-RELEASE-p3 FreeBSD 5.0-RELEASE-p3 #2: Tue Feb 25 14:45:28 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BINKY4 i386 I did try grabbing a more recent copy of the file in question yesterday, but diff produced no diff. This appears to prevent Postgres postmaster from starting. /src and /obj were cleaned out prior to the cvsup and build so sources were indeed new (yes, I realise recent recommendations oppose this sort of thing, but it is an old 586 box with limited space). Haven't seen any new commits regarding this either (the last that appeared to touch it seems to be from the 19th - between my last cvsup on the 18th and now). Suggestions, recommendations? Cheers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenSSL should define OPENSSL_THREADS?
"Jacques A. Vidrine" writes: > > Should the OpenSSL in FreeBSD be defining OPENSSL_THREADS? > > I think you may be right. OpenSSL 0.9.7's out-of-the box configure > creates an opensslconf.h that would define OPENSSL_THREADS on FreeBSD. > > Mark supplied the opensslconf.h's that are used in the FreeBSD build ... > let's see if this is intentional or not. [cc'd] Not intentional. If adding it breaks nothing, go ahead. I have Panic City right now on my devboxes, so I'm working on fixing that. M -- Mark Murray iumop ap!sdn w,I idlaH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: What broke X between 5.0R and recent current?
On Mon, 2003/02/24 at 17:28:57 -0500, Daniel Eischen wrote: > So I got a new Dell laptop, ATI Radeon 7500. Installed FreeBSD > 5.0-RELEASE, X 4.2.1, and KDE right off the FreeBSD Mall CD-ROM. > I configured X from the installation setup and was happily > running X and KDE @ 1400x1050. Cool. > > Then I cvsup'd to a recent -current from about a week ago, > which my other laptop and desktop are currently running just > fine (both use very old 3.x or 4.x built X's, probably XFree86 > 3.2.x and running with compat libraries). Now X refuses to > work. It's not the kernel because before installing world, > I installed the kernel and booted it to make sure everything > still worked. X was happy with the old kernel too 'cause > I went back and tried it again also. But after the installworld, > X didn't work, not even xf86cfg. I tried the installworld with > and without mergemaster'ing and X didn't work regardless. I > went back and did another fresh install of 5.0R and X worked > again, but after another installworld, I got the same problem. > The XFree86 log file is at the end. It aborts with: > > [...] > (II) LoadModule: "ddc" > (II) Reloading /usr/X11R6/lib/modules/libddc.a > (II) RADEON(0): VESA VBE DDC supported > (II) RADEON(0): VESA VBE DDC Level none > (II) RADEON(0): VESA VBE DDC transfer in appr. 2 sec. > (II) RADEON(0): VESA VBE DDC read failed > (==) RADEON(0): Write-combining range (0xfcff,0x8) was already clear > (==) RADEON(0): Write-combining range (0xe000,0x200) > (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12000 max=35000; xclk=16600 > (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) > > Fatal server error: > Caught signal 10. Server aborting > > Any ideas? I'm in the process of trying a more recent -current > and am also going to try and rebuild X (though we shouldn't > have to do that). I saw something like that on my notebook, too - in my case, it was a problem in the radeon driver which could be worked around by adding an explicit "Modes" line in the used Display subsection in XF86Config, like: Section "Screen" [...] DefaultColorDepth 24 [...] SubSection "Display" Depth 24 Modes "1024x768" EndSubSection EndSection - Thomas -- Thomas Moestl <[EMAIL PROTECTED]> http://www.tu-bs.de/~y0015675/ <[EMAIL PROTECTED]> http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Fwd: mkisofs | burncd not working in 5.0 ?]
On Tue, 25 Feb 2003 20:56:25 +0100 David Vidal Rodríguez <[EMAIL PROTECTED]> wrote: > Alexander Leidinger wrote: > > Please try the patch in from the mail to -current with the Message-ID > > <[EMAIL PROTECTED]> and report if it works for > > you. > > I've applied the patch included here, but it leads to an error (the .rej > file shows it). I infer from the reject that a "while" has to be > replaced by an "if", and so I've edited it by hand. > > The problem is that my system still shows the same behavior as before :( > > Maybe I've applied the wrong patch? No, but then the cause of the problem is not what I thought it is. Bye, Alexander. -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMBus support...
On Wed, Feb 26, 2003 at 07:33:40AM -0500, Paul A. Howes wrote: > Sergey, > > Thanks! Where is this documented? Looks like its not yet documented. If it works for you - i can make a patch for NOTES and ichsmb(4). Please notify me. > Try to use device ichsmb, maybe its helps you. This is your message: > [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x24c28086 chip=0x24c38086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801DB (ICH4) SMBus Controller' > class= serial bus > subclass = SMBus $ grep -i 0x24c38086 src/sys/dev/ichsmb/* also look at src/sys/dev/ichsmb/ichsmb_pci.c -- Rgdz,/"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MINCYLGRPS (was: 4-stable releases on -current?)
On Tue, Feb 25, 2003 at 09:52:02PM +0200, Ruslan Ermilov wrote:
> On Tue, Feb 25, 2003 at 08:02:19PM +0200, John Hay wrote:
[...]
> > Ok, with the patches below I can get to where it tries to build the
> > fixit floppy in release.10. It breaks because the floppy is too small.
> > I must still check to make sure it is true.
> >
> We'll know this in less than 1:30 -- I've just launched the
> snapshot build for 4.x/i386 on my fast -stable box.
>
> While I was writing it, it's already finished (successfully).
>
> ftp://ftp.sunbay.net/pub/FreeBSD/snapshots/i386/4.x-20030225-STABLE/
>
OK, I've tracked it down to the differences in newfs(8) between
4.x and 5.x. In 4.x, newfs'ing a 1.44MB floppy results in a
single cylinder group, but in 5.x there's a thing called
MINCYLGRPS, which results in fewer free space on a floppy:
: # uname -r
: 4.7-STABLE
: # ./x
: Warning: Block size restricts cylinders per group to 6.
: Warning: 1216 sector(s) in last cylinder unallocated
: /dev/vn0c:2880 sectors in 1 cylinders of 1 tracks, 4096 sectors
: 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g)
: super-block backups (for fsck -b #) at:
: 32
: Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on
: /dev/vn01363 01363 0% 1 3810%
: # uname -r
: 5.0-CURRENT
: # ./x
: /dev/md0c: 1.4MB (2880 sectors) block size 4096, fragment size 512
: using 4 cylinder groups of 0.36MB, 91 blks, 128 inodes.
: super-block backups (for fsck -b #) at:
: 32, 760, 1488, 2216
: Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on
: /dev/md01311 01311 0% 15090%
With this patch to newfs(8),
: Index: mkfs.c
: ===
: RCS file: /home/ncvs/src/sbin/newfs/mkfs.c,v
: retrieving revision 1.74
: diff -u -p -r1.74 mkfs.c
: --- mkfs.c22 Feb 2003 23:26:11 - 1.74
: +++ mkfs.c26 Feb 2003 11:20:57 -
: @@ -317,7 +317,7 @@ mkfs(struct partition *pp, char *fsys)
: for ( ; sblock.fs_fpg < maxblkspercg; sblock.fs_fpg += sblock.fs_frag) {
: sblock.fs_ipg = roundup(howmany(sblock.fs_fpg, fragsperinode),
: INOPB(&sblock));
: - if (sblock.fs_size / sblock.fs_fpg < MINCYLGRPS)
: + if (sblock.fs_size / sblock.fs_fpg < (Oflag == 2 ? MINCYLGRPS : 1))
: break;
: if (CGSIZE(&sblock) < (unsigned long)sblock.fs_bsize)
: continue;
I still don't get the same picture as on 4.x, but it's now at least
sufficient to make release.10 happy.
: # ./x
: /dev/md0c: 1.4MB (2880 sectors) block size 4096, fragment size 512
: using 1 cylinder groups of 1.41MB, 361 blks, 416 inodes.
: super-block backups (for fsck -b #) at:
: 32
: Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on
: /dev/md01359 01359 0% 14130%
John, I'm sending you the complete patchset in another email.
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
FSIMG=fixit.flp
FSSIZE=1440
FSLABEL=fd1440
FSINODE=4000
dd of=${FSIMG} if=/dev/zero count=${FSSIZE} bs=1k 2>/dev/null
case `uname -r` in
4.*)
DEVICE=vn0
vnconfig -s labels -c /dev/${DEVICE} ${FSIMG}
;;
5.*)
DEVICE=`mdconfig -a -t vnode -f ${FSIMG}`
;;
esac
disklabel -w -B ${DEVICE} ${FSLABEL}
newfs -i ${FSINODE} -o space -m 0 /dev/${DEVICE}c
#disklabel ${DEVICE}
df -i /dev/${DEVICE}
case `uname -r` in
4.*)
vnconfig -u ${DEVICE}
;;
5.*)
mdconfig -d -u ${DEVICE}
;;
esac
pgp0.pgp
Description: PGP signature
Re: SB Live goes silent after pcm commit
On Wed, 2003-02-26 at 01:49, Olivier Houchard wrote: > > The pcm driver is compiled into the kernel, i haven't tested loading as > > module. > > > > dmesg|grep pcm: > > pcm0: port 0x9400-0x941f irq 5 at device 13.0 on pci0 > > pcm0: > > > > Soundcard: Soundblaster Live 1024! Player > > Motherboard: Asus A7V133, Via Apollo KT133A chipset > > > > Soundcard is sharing irq with an Intel NIC and the onboard USB > > controller. > > Hi, > > Could you please try the attached patch (to be applied in > /sys/dev/sound/pci). > > Thanks, > > Olivier As far as I can hear, the patch fixed the problem :) Øyvind signature.asc Description: This is a digitally signed message part
panics and sometimes hard freezes as of recent builds
occurs on occasion with network activity. gtk-gnutella, which
generates a lot of network activity, used to make the machine freeze
solid, or panic/reboot.
The following occured while using slrn during a buildworld. Was not
running X at the time, although most of the time, the panics/freezes
occured while X was running.
Interestingly enough, I could switch vt's, despite the fact that ddb>
was on the first vc. Couldn't do anything but switch vt's. The
system wouldn't respond to keyboard input.
BTW, I just copied this down from the screen, so it may have some slight
errors:
panic: headlocked should be 0
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx, in_Debugger.0
Debugger(c0372e70,c03d7620,c037c2f9,cd28ab18,1) at Debugger+0x54
panic(c037c2f9,c135982a,cd28ab68,c0ed7c0b,5bc3) at panic+0xab
tcp_input(c0ed7c00,14,c01eo6dd,c03d86c0,1) at tcp_input+0x29ac
ip_input(c0ed7c00,0,c037bf08,3c2,2) at ip_input+0x7d6
ipintr(217,c037233f,c0ebf440,c0ec828d,c0ecaa5d) at ipintr+0x91
swi_net(0,0,c0370d36,217,c0ec99ec) at swi_net+0x2f
ithread_loop(c0ec8280,cd28ad48,c0370bab,35f,3c4eb) at ithread_loop+0x182
fork_exit(c01d7710,c0ec8280,cd28ad48) at fork_exit+0xc4
fork_trampoline() at fork_trampoline+0x1a
uname -a:
FreeBSD daemonstar.zoominternet.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Feb 26
03:29:07 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM i386
dmesg showing on of the panics (maybe not same one):
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01de7db
stack pointer = 0x10:0xcd2a0c14
frame pointer = 0x10:0xcd2a0c28
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 = 13 (swi7: tty:sio clock)
trap number = 12
panic: page fault
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Sis chipset
It seems Christoph P. Kukulies wrote: > I have two network cards plugged in. But board has the builtin 100MBit, > Soeren, it's the same board I sent to you. > > I will lookup in the bios (later) if I have disabled the on > board NIC inadvertently (if that's possible) but at present make world > is running. You must have disabled it (its possible in my BIOS but I upgraded to the latest in the hope that ACPI would work) I have: [EMAIL PROTECTED]:4:0: class=0x02 card=0x80a71043 chip=0x09001039 rev=0x91 hdr=0x00 sis0: port 0x9800-0x98ff mem 0xf500-0xf5000fff at dev ice 4.0 on pci0 pcib0: slot 4 INTA is routed to irq 5 sis0: Ethernet address: 00:e0:18:b5:0e:36 miibus0: on sis0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm breakage
I'm definitely seeing this, and I assumed it's related to my witness complain about cmi (though it only started recently -- but, then, this message has only been added recently, afaik). I have no sound problems, though. In between crashes for other problems, that is. La Temperanza wrote: I haven't seen a message about this show up yet, so I'm thinking it may be an isolated glitch. I rebuilt my system this morning to try and solve some spurious reboots while using X, and ended up with this message being spammed about ten times on startup. /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/sound.c:191 When I attempt to play any sound now, an annoying high-pitched whine comes out the speakers until the process is terminated, and the dmesg buffer is overwritten by hundreds of instances of this unhelpful message- "pcm0: pci error". XMMS quits properly, but console commands like 'cat /dev/urandom > /dev/dsp' seem to lock out Ctrl-C and need to be killed from another shell. My exact environment: FreeBSD tomoyo.sakura 5.0-CURRENT FreeBSD 5.0-CURRENT #17: Tue Feb 25 10:14:41 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TOMOYO i386 Some (possibly) relevant devices: acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00f7760 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcm0: port 0xd800-0xd81f irq 11 at device 11.0 on pci0 pcm0: I hope someone can figure this out. Let me know if I can do more to diagnose the problem. -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Outros: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] The secret of success is sincerity. Once you can fake that you've got it made. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SMBus support...
Sergey, Thanks! Where is this documented? -- Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergey A. Osokin Sent: Wednesday, February 26, 2003 7:10 AM To: Paul A. Howes Cc: [EMAIL PROTECTED] Subject: Re: SMBus support... Try to use device ichsmb, maybe its helps you. -- Rgdz,/"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sis chipset
On Wed, Feb 26, 2003 at 12:33:06PM +0100, Martin Blapp wrote: > > Hi, > > > [EMAIL PROTECTED]:8:0: class=0x02 card=0x chip=0x905010b7 rev=0x00 > > hdr=0x00 > > vendor = '3COM Corp, Networking Division' > > device = '3C905-TX Fast Etherlink XL PCI 10/100' > > class= network > > subclass = ethernet > > [EMAIL PROTECTED]:9:0: class=0x02 card=0x chip=0x802910ec rev=0x00 > > hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'RTL8029 NE2000 compatible Ethernet' > > class= network > > subclass = ethernet > > There is no sis900 ethernet on your mainboard. It looks like you have > a NE2000 compatible card. I have two network cards plugged in. But board has the builtin 100MBit, Soeren, it's the same board I sent to you. I will lookup in the bios (later) if I have disabled the on board NIC inadvertently (if that's possible) but at present make world is running. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMBus support...
On Wed, Feb 26, 2003 at 07:08:22AM -0500, Paul A. Howes wrote: > My motherboard has SMBus support: > > [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x24c28086 chip=0x24c38086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801DB (ICH4) SMBus Controller' > class= serial bus > subclass = SMBus > > ...but there is no driver. I didn't see a module in /boot/kernel that > looked likely, and there isn't a driver listed in > /usr/src/sys/i386/conf/NOTES for it. Is there a way to enable SMBus > support on 5.0-RELEASE? Try to use device ichsmb, maybe its helps you. -- Rgdz,/"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMBus support...
All, My motherboard has SMBus support: [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x24c28086 chip=0x24c38086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB (ICH4) SMBus Controller' class= serial bus subclass = SMBus ...but there is no driver. I didn't see a module in /boot/kernel that looked likely, and there isn't a driver listed in /usr/src/sys/i386/conf/NOTES for it. Is there a way to enable SMBus support on 5.0-RELEASE? Thanks! -- Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
Dag-Erling Smorgrav wrote: It seems that with -O2 on ia32 (-march=k6-2 in my case), gcc will in some cases generate short jumps to targets too far away for the offset to fit in a single byte. A surefire way to reproduce this is to build Mesa (or XFree86-4-libraries, which includes parts of Mesa). Has anybody else run into this? I build world and ports on desktop machines usually using -O2 and never got any problems, except with lang/ezm3. If you tell me, where you've find the problems, I'll tell my gcc to keep the temporaries and check them after a make build. Jens To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-O2 considered harmful
It seems that with -O2 on ia32 (-march=k6-2 in my case), gcc will in some cases generate short jumps to targets too far away for the offset to fit in a single byte. A surefire way to reproduce this is to build Mesa (or XFree86-4-libraries, which includes parts of Mesa). Has anybody else run into this? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sis chipset
Hi, > [EMAIL PROTECTED]:8:0: class=0x02 card=0x chip=0x905010b7 rev=0x00 > hdr=0x00 > vendor = '3COM Corp, Networking Division' > device = '3C905-TX Fast Etherlink XL PCI 10/100' > class= network > subclass = ethernet > [EMAIL PROTECTED]:9:0: class=0x02 card=0x chip=0x802910ec rev=0x00 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8029 NE2000 compatible Ethernet' > class= network > subclass = ethernet There is no sis900 ethernet on your mainboard. It looks like you have a NE2000 compatible card. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "NTLDR missing" after 5-RELEASE install
My experience with the FBSD boot manager is virtually zero, so I can't address it's workings, but I use GRUB as a booter just because it gets me out of so many jams like yours -- if something isn't where you thought it was you can point GRUB at your disks and let it do the looking for you. The secret is to make a boot floppy with GRUB installed on it. Once you have that there's no machine that's unbootable, and you can reinstall GRUB in seconds if it gets overwritten by Bill & Co. For example, IIRC, I just went thru this myself (although it's all so routine now I can't even remember what I do to bail out anymore) when I installed XP on a brand new disk and then installed FBSD afterwards. I got the MBR screwed up just like you, then ran the XP install disk in "Repair" mode which got XP to boot again but overwrote the FBSD booter. So all I did was boot my trusty GRUB floppy and reinstalled GRUB on the MBR in about 60 seconds and -- done. The next evil news is that I've never really gotten FBSD's incarnation of GRUB to work right for me, so I just install in on the floppy from a linux machine and use that for the FBSD machine. If you have access to GRUB and need instructions I'd be happy to help. Just let me know. Thanks for the tip! I'll give GRUB a try :) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata dumps broken again
Top-of-tree -CURRENT:
db> call doadump
Dumping 639 MB
ata1: resetting devices ..
mi_switch(c4fad9ec,f,f,1c,5f74e) at mi_switch+0x21b
ithread_schedule(c48fb380,1,c4faea50,e99cf84c,c025850c) at ithread_schedule+0xf6
sched_ithd(f) at sched_ithd+0x38
Xintr15() at Xintr15+0x6c
--- interrupt, eip = 0xc017388b, esp = 0xe99cf830, ebp = 0xe99cf84c ---
critical_exit(0,c489f900,c489f92c,e99cf884,c0128324) at critical_exit+0x2b
DELAY(a,256c,82,40267d87,0) at DELAY+0x47
ata_wait(c489f92c,40,0,0,0) at ata_wait+0x84
ata_command(c489f92c,c6,0,0,10) at ata_command+0x2c5
ad_reinit(c489f92c,c489f92c,ec) at ad_reinit+0x30
ata_reinit(c489f900,c489f900,1,e99cf960,e99cf9a8) at ata_reinit+0x265
addump(c48f3764,c02f67c0,0,18003c00,0,200) at addump+0xe8
dumpsys(c02cee20,c02cee40,b,e99cf9f8,c016eec0) at dumpsys+0x28b
doadump(0,0,0,0,0,0,0,0,0,0) at doadump+0x20
db_fncall(0,0,e99cfaa8,e99cfa60,0) at db_fncall+0x7c
db_command(c02a3380,c02a31a0,c029de74,c029de78,c028024d) at db_command+0xfb
db_command_loop(0,0,e99cfc28,c02c1ec8,e99cfb4c) at db_command_loop+0x5c
db_trap(c,0,1,10,e99cfbe0) at db_trap+0x5e
kdb_trap(c,0,e99cfbe0) at kdb_trap+0xe6
trap_fatal(e99cfbe0,c4,c4faea50,12ab9a0,0) at trap_fatal+0x1cc
trap_pfault(e99cfbe0,0,c4) at trap_pfault+0x154
trap(18,10,10,c7886300,c4caf500) at trap+0x38b
calltrap() at calltrap+0x5
--- trap 0xc, eip = 0xc01e94fb, esp = 0xe99cfc20, ebp = 0xe99cfc60 ---
in6_pcbbind(c4bc1390,c7886300,c4faea50) at in6_pcbbind+0x1fb
tcp6_usr_bind(c4caf500,c7886300,c4faea50) at tcp6_usr_bind+0x9f
sobind(c4caf500,c7886300,c4faea50,c4caf500,e99cfd14) at sobind+0x16
kern_bind(c4faea50,3,c7886300,c7886300,0) at kern_bind+0x70
bind(c4faea50) at bind+0x30
syscall(2f,2f,2f,804a3e0,0) at syscall+0x310
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (104), eip = 0x280b1a63, esp = 0xbfbffa2c, ebp = 0xbfbffa88 ---
Context switches not allowed in the debugger.
(kgdb) l *(ad_reinit+0x30)
0xc0133770 is in ad_reinit (../../../dev/ata/ata-disk.c:874).
869
870 /* reinit disk parameters */
871 ad_invalidatequeue(atadev->driver, NULL);
872 ata_command(atadev, ATA_C_SET_MULTI, 0,
873 adp->transfersize / DEV_BSIZE, 0, ATA_WAIT_READY);
874 atadev->setmode(atadev, adp->device->mode);
875 }
876
877 void
878 ad_print(struct ad_softc *adp)
(kgdb) l *(ata_command+0x2c5)
0xc01287a5 is in ata_command (../../../dev/ata/ata-all.c:1126).
1121break;
1122
1123case ATA_WAIT_READY:
1124atadev->channel->active |= ATA_WAIT_READY;
1125ATA_OUTB(atadev->channel->r_io, ATA_CMD, command);
1126if (ata_wait(atadev, ATA_S_READY) < 0) {
1127ata_prtdev(atadev, "timeout waiting for cmd=%02x s=%02x e=%02x\n",
1128 command,
atadev->channel->status,atadev->channel->error);
1129error = -1;
1130}
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
signals still broken ?
# uname -a
FreeBSD kokeb.ambesa.net 5.0-CURRENT FreeBSD 5.0-CURRENT #8: Tue Feb 25 16:45:54
EST 2003
[EMAIL PROTECTED]:/daemon/build/current/obj/daemon/build/current/src/sys/QUARK i386
The following program is stuck in pause(3) forever. I have reproduced the bug in
5.0-RELEASE, but 4.7-STABLE behaves as expected: the child resumes upon
receiving SIGCONT.
#include
#include
#include
#include
static void
cont_handler()
{ ; }
int main()
{
int child, status;
if (signal(SIGCONT, cont_handler) == SIG_ERR)
err(1, "signal()");
if ((child = fork()) == 0) {
pause();
exit(0);
} else if (child == -1)
err(1, "fork()");
printf("sleeping 3s\n");
sleep(3);
if (kill(child, SIGCONT) == -1)
err(1, "kill()");
printf("waiting\n");
if ((child = wait(status)) == -1)
err(1, "wait()");
printf("done\n");
return (0);
}
Cheers.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Sis chipset
On Wed, Feb 26, 2003 at 11:26:08AM +0100, Martin Blapp wrote: > > Hi, > > >Is there a chance to get the built in 100MBit network adapter in the chipset > >working somehow? > > I thought I've fixed the support so it should work ? If not, do you > have a "pciconf -lv" output for me ? > > Martin Here you are: [EMAIL PROTECTED]:0:0: class=0x06 card=0x80861043 chip=0x06481039 rev=0x02 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS648 Host-to-PCI Bridge' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0x00011039 rev=0x00 hdr=0x01 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS 530 Virtual PCI-to-PCI bridge (AGP)' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:2:0: class=0x060100 card=0x chip=0x09631039 rev=0x04 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' class= bridge subclass = PCI-ISA [EMAIL PROTECTED]:2:3: class=0x0c0010 card=0x809a1043 chip=0x70071039 rev=0x00 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS OHCI Compliant FireWire Controller' class= serial bus subclass = FireWire [EMAIL PROTECTED]:2:5: class=0x01018a card=0x80871043 chip=0x55131039 rev=0x00 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS5513 EIDE Controller (A,B step)' class= mass storage subclass = ATA [EMAIL PROTECTED]:2:7: class=0x040100 card=0x80961043 chip=0x70121039 rev=0xa0 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS7012 PCI Audio Accelerator' class= multimedia subclass = audio [EMAIL PROTECTED]:3:0: class=0x0c0310 card=0x80871043 chip=0x70011039 rev=0x0f hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS5597/8 Universal Serial Bus Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:3:1: class=0x0c0310 card=0x80871043 chip=0x70011039 rev=0x0f hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS5597/8 Universal Serial Bus Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:3:2: class=0x0c0310 card=0x80871043 chip=0x70011039 rev=0x0f hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS5597/8 Universal Serial Bus Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:3:3: class=0x0c0320 card=0x80871043 chip=0x70021039 rev=0x00 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS7002 USB 2.0 Enhanced Host Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:8:0: class=0x02 card=0x chip=0x905010b7 rev=0x00 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905-TX Fast Etherlink XL PCI 10/100' class= network subclass = ethernet [EMAIL PROTECTED]:9:0: class=0x02 card=0x chip=0x802910ec rev=0x00 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8029 NE2000 compatible Ethernet' class= network subclass = ethernet [EMAIL PROTECTED]:10:0:class=0x070300 card=0x545910a5 chip=0x545910b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' class= simple comms [EMAIL PROTECTED]:11:0: class=0x060700 card=0x010114ef chip=0x04751180 rev=0x80 hdr=0x02 vendor = 'Communication Automation Corporation' device = 'RL5C475 CardBus controller' class= bridge subclass = PCI-CardBus [EMAIL PROTECTED]:14:0: class=0x010400 card=0x809e1043 chip=0x3376105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20376 FastTrak 376 Controller' class= mass storage subclass = RAID [EMAIL PROTECTED]:0:0: class=0x03 card=0x chip=0x011010de rev=0xb2 hdr=0x00 vendor = 'Nvidia Corporation' device = 'NV11 GeForce2 MX / MX 400' class= display subclass = VGA If the network device is amongst it, what would be its device name? I'd guess sis0. -- Christoph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB Live goes silent after pcm commit
On 2003-02-26 01:49:14 (+0100), Olivier Houchard <[EMAIL PROTECTED]> wrote: > On Tue, Feb 25, 2003 at 11:13:23PM +0100, ?yvind Rakv?g wrote: > > I believe the commit Feb 20 17:31:11 2003 UTC on > > src/sys/dev/sound/pci/emu10k1.c broke something. > > > > With a kernel built from 17:00 sources sound works, from 19:00 there is > > only the sound of silence. Everything looks OK, xmms, mpg123 etc play, > > but no sound. > > > > The pcm driver is compiled into the kernel, i haven't tested loading as > > module. > > Could you please try the attached patch (to be applied in > /sys/dev/sound/pci). Patch seems to work. My sound appears to work again. I'm using the module though, and not the compiled-into-the-kernel version Øyvind is using. I don't suppose there's much difference between the two? - Philip -- Philip Paeps Please don't CC me, I am [EMAIL PROTECTED] subscribed to the list. Never say "oops" after you have submitted a job. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "NTLDR missing" after 5-RELEASE install
George Hartzell wrote: Andrew Boothman writes: > [...] > I didn't really change much about my system when I installed FreeBSD. > > Windows is installed on the whole of the first HDD, and FreeBSD on the whole of > the second. Prior to installing 5.0, the second disc had an old installation of > 4.6 that I wasn't using. > > When installing, I asked sysinstall to install booteasy on the first drive, but > otherwise leave it unchanged. I removed the existing slice on the second drive > and got sysinstall to create a new slice filling the drive, I then allowed > sysinstall to auto-size the partitions and complete the installation. > > I've tried every repair option that I can find on the Win2k CD. I've tried > the "fixboot" and "fixmbr" commands in the recovery console many times, and > despite fixmbr complaining about an "unusual" mbr every time, installing a new > one apparently makes no difference. I eventually managed to remove booteasy > from the first drive so that "NTLDR is missing" appears straight away, but that > is hardly a victory. I even followed Microsoft's instructions in knowledgebase > article 318728 and performed a brand new installation of windows into > c:\tempwin but even this new installation failed to boot with the same problem. > Therefore it would seem that whatever the problem is, Win2k's setup prog either > can't fix it or is oblivious to it. It's looking more and more like I'm going > to have to reformat this drive as I seem to have no way of getting Win2k > operating again, but I'd _really_ like to understand what happened here, not > least to ensure I don't repeat the same problems when I come to try and dual- > boot again! > > Apologies for this getting increasingly off-topic, but I can't understand what > I've done wrong here as I've done this many times before with 4.x. > > As ever, any light-shedding would be much appricated :) I had several problems installing 5.0 release onto my sandbox machine, and the solution might be relevant. My sandbox machine had a single disk, uses a "stock" (what came on the drive) master boot record, and had several primary partitions (aka slices). The first partition/slice contained a windows2000 install, the second partition had a linux installation w/ the GRUB boot loader installed in the beginning of the partition. The linux parition is marked active (using Partition Magic from windows), so the normal boot sequence goes: MBR --> GRUB ---+--> Linux | +--> Windows depending on the choice made in grub. I boot this way because the sandbox machine is a test environment for my laptop, and suspend to disk stuff doesn't seem to work on the laptop unless the vendor's MBR is in place. My intent was to add Freebsd to the third partition. I ran through the install and told the installer to just leave the MBR alone. Among the things that I discovered were: - both the linux partition *AND* the newly installed FreeBSD partition ended up marked active. - There was a problem with data somewhere in the BIOS/DOS partition table concerning CHS values and LBA values for various parts of the partition. (might have the acronym's wrong). Both of these rendered the machine unable to boot, I recovered it once by booting from a floppy, getting into windows, and running partition magic, and on a separate test run by booting from a live linux cd and playing with various fdisk-oid programs available there. So, all that said, maybe your partition table is slightly scrod, not so badly that it won't get through the MBR but badly enough that it can't find the NT partition? It'd be interesting to see what parition magic had to say about it. It's possible I guess that we both suffered from the same problem. I'd be inclined to think that it must be operator error over something wrong with sysinstall since I've not seen people complaining of these problems before, yet there must be loads of people dual-booting. Having said that, I still can't understand what I did differently or how to prevent the same thing from happening in the future. I guess I'll just use GRUB or something instead. Looks like my Windows drive is heading for a reformat :-/ Thanks anyway! :) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: patch for the nVidia driver and -CURRENT
Jake Burkholder wrote:
> Apparently, On Tue, Feb 25, 2003 at 10:49:16PM +0100,
> Maxime Henrion said words to the effect of;
>
> > Morten Rodal wrote:
> > > On Tue, Feb 25, 2003 at 07:28:09PM +0100, Maxime Henrion wrote:
> > > [snip a lot of the patch]
> > > > @@ -1431,7 +1442,8 @@
> > > > SLIST_FOREACH(at, &sc->alloc_list, list) {
> > > > if (offset >= at->address &&
> > > > offset < at->address + at->size)
> > > > -return atop(vtophys(offset));
> > > > +*paddr = vtophys(offset);
> > > > +return 0;
> > > > }
> > > >
> > > > return -1;
> > >
> > > Should the function return 0 even if the if (offset..) fails? I have
> > > no clue about the nvidia kernel driver (or kernel stuff at all) but it
> > > seems to me that the only way the function can return -1 is if the
> > > list is empty.
> >
> > And this is consistant with what the code was doing before. This change
> > is not a functional change, it's just a necessary update due to API
> > changes.
>
> I think he's referring to missing braces around the if which was changed
> from 1 statement to 2.
Damnit. I've updated the patch at :
http://mu.org/~mux/patches/nvidia.patch
I've also added the removal of the #error in this patch, since people
have been asking me about it.
Cheers,
Maxime
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: mac_mls still panics
Robert Watson wrote:
Question on both of these: could you inspect the struct ifnet pointer on
the mbuf and see what interface they originated from? Also, the dumps are
> still showing NULL local variables where it should not be possible --
does
> manual inspection of the variables in the debugger reveal different
values
> (ifnetlabel, mbuflabel, etc). You might want to see if compiling
with -O0
Doesn't make much sense to me. M. Well, have a peek:
(kgdb) up 10
#10 0xc0278d16 in mac_mls_check_ifnet_transmit (ifnet=0xc25ebc00,
ifnetlabel=0x0, m=0xc0ee1800, mbuflabel=0x0)
at /usr/src/sys/security/mac_mls/mac_mls.c:1462
1462return (mac_mls_single_in_range(p, i) ? 0 : EACCES);
(kgdb) p/x *ifnet
$1 = {if_softc = 0xc25ebc00, if_name = 0xc031d9bb, if_link = {tqe_next =
0xc25cde00, tqe_prev = 0xc0362f94},
if_addrhead = {tqh_first = 0xc2608400, tqh_last = 0xc2608e60},
if_klist = {slh_first = 0x0},
if_pcount = 0x0, if_bpf = 0x0, if_index = 0x1, if_unit = 0x0,
if_timer = 0x0, if_nvlans = 0x0,
if_flags = 0x8843, if_capabilities = 0x8, if_capenable = 0x0,
if_ipending = 0x0, if_linkmib = 0x0,
if_linkmiblen = 0x0, if_data = {ifi_type = 0x6, ifi_physical = 0x0,
ifi_addrlen = 0x6, ifi_hdrlen = 0x12,
ifi_recvquota = 0x0, ifi_xmitquota = 0x0, ifi_mtu = 0x5dc,
ifi_metric = 0x0, ifi_baudrate = 0x5f5e100,
ifi_ipackets = 0x10b22, ifi_ierrors = 0x0, ifi_opackets = 0x663,
ifi_oerrors = 0x0, ifi_collisions = 0x0,
ifi_ibytes = 0x9ef12c, ifi_obytes = 0x1be94, ifi_imcasts = 0x10201,
ifi_omcasts = 0x0, ifi_iqdrops = 0x0,
ifi_noproto = 0x0, ifi_hwassist = 0x0, ifi_unused = 0x0,
ifi_lastchange = {tv_sec = 0x0, tv_usec = 0x0}},
if_multiaddrs = {tqh_first = 0xc25c8640, tqh_last = 0xc25c8620},
if_amcount = 0x0, if_output = 0xc02527e0,
if_input = 0xc0252fb0, if_start = 0xc014b430, if_done = 0x0, if_ioctl
= 0xc014d570,
if_watchdog = 0xc014c140, if_poll_recv = 0x0, if_poll_xmit = 0x0,
if_poll_intren = 0x0,
if_poll_slowinput = 0x0, if_init = 0xc014c180, if_resolvemulti =
0xc02537e0, if_snd = {ifq_head = 0x0,
ifq_tail = 0x0, ifq_len = 0x0, ifq_maxlen = 0x7f, ifq_drops = 0x0,
ifq_mtx = {mtx_object = {
lo_class = 0xc035ab00, lo_name = 0xc031d9bb, lo_type =
0xc03339a6, lo_flags = 0x3, lo_list = {
tqe_next = 0xc260847c, tqe_prev = 0xc25d7274}, lo_witness =
0xc038c700}, mtx_lock = 0x4,
mtx_recurse = 0x0, mtx_blocked = {tqh_first = 0x0, tqh_last =
0xc25ebd08}, mtx_contested = {
le_next = 0x0, le_prev = 0x0}}}, if_poll_slowq = 0x0,
if_prefixhead = {tqh_first = 0x0,
tqh_last = 0xc25ebd1c}, if_broadcastaddr = 0xc0362fc0, if_label =
{l_flags = 0x1, l_perpolicy = {{
l_ptr = 0xc218b120, l_long = 0xc218b120}, {l_ptr = 0xc2605e80,
l_long = 0xc2605e80}, {
l_ptr = 0xc2605f00, l_long = 0xc2605f00}, {l_ptr = 0x0, l_long
= 0x0
(kgdb) p ifnetlabel
$2 = (struct label *) 0x0
(kgdb) p mbuflabel
$3 = (struct label *) 0x0
(kgdb) up
#11 0xc01dad8a in mac_check_ifnet_transmit (ifnet=0xc25ebc00,
mbuf=0xc0ee1800)
at /usr/src/sys/kern/kern_mac.c:2269
2269&mbuf->m_pkthdr.label);
(kgdb) p/x *ifnet
$4 = {if_softc = 0xc25ebc00, if_name = 0xc031d9bb, if_link = {tqe_next =
0xc25cde00, tqe_prev = 0xc0362f94},
if_addrhead = {tqh_first = 0xc2608400, tqh_last = 0xc2608e60},
if_klist = {slh_first = 0x0},
if_pcount = 0x0, if_bpf = 0x0, if_index = 0x1, if_unit = 0x0,
if_timer = 0x0, if_nvlans = 0x0,
if_flags = 0x8843, if_capabilities = 0x8, if_capenable = 0x0,
if_ipending = 0x0, if_linkmib = 0x0,
if_linkmiblen = 0x0, if_data = {ifi_type = 0x6, ifi_physical = 0x0,
ifi_addrlen = 0x6, ifi_hdrlen = 0x12,
ifi_recvquota = 0x0, ifi_xmitquota = 0x0, ifi_mtu = 0x5dc,
ifi_metric = 0x0, ifi_baudrate = 0x5f5e100,
ifi_ipackets = 0x10b22, ifi_ierrors = 0x0, ifi_opackets = 0x663,
ifi_oerrors = 0x0, ifi_collisions = 0x0,
ifi_ibytes = 0x9ef12c, ifi_obytes = 0x1be94, ifi_imcasts = 0x10201,
ifi_omcasts = 0x0, ifi_iqdrops = 0x0,
ifi_noproto = 0x0, ifi_hwassist = 0x0, ifi_unused = 0x0,
ifi_lastchange = {tv_sec = 0x0, tv_usec = 0x0}},
if_multiaddrs = {tqh_first = 0xc25c8640, tqh_last = 0xc25c8620},
if_amcount = 0x0, if_output = 0xc02527e0,
if_input = 0xc0252fb0, if_start = 0xc014b430, if_done = 0x0, if_ioctl
= 0xc014d570,
if_watchdog = 0xc014c140, if_poll_recv = 0x0, if_poll_xmit = 0x0,
if_poll_intren = 0x0,
if_poll_slowinput = 0x0, if_init = 0xc014c180, if_resolvemulti =
0xc02537e0, if_snd = {ifq_head = 0x0,
ifq_tail = 0x0, ifq_len = 0x0, ifq_maxlen = 0x7f, ifq_drops = 0x0,
ifq_mtx = {mtx_object = {
lo_class = 0xc035ab00, lo_name = 0xc031d9bb, lo_type =
0xc03339a6, lo_flags = 0x3, lo_list = {
tqe_next = 0xc260847c, tqe_prev = 0xc25d7274}, lo_witness =
0xc038c700}, mtx_lock = 0x4,
mtx_recurse = 0x0, mtx_blocked = {tqh_first = 0x0, tqh_last =
0xc25ebd08}, mtx_contested = {
le_next = 0x0, le_prev = 0x0}}}, if_poll_slowq = 0x0,
if_prefixhead = {tqh_first = 0x0,
Re: Sis chipset
It seems Martin Blapp wrote: > > Hi, > >Is there a chance to get the built in 100MBit network adapter in the chipset > >working somehow? > I thought I've fixed the support so it should work ? If not, do you > have a "pciconf -lv" output for me ? It works on -current for me... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VESA modes with i815?
Hi guys! I've recently had my Matrox VGA board die on me (don't know why, it just died), and since then I've been doomed to use the on-board i815 chip to get the phosphors in my monitor to light up. This works fine with 'small consoles', and even with VESA_800x600, but when I type 'vidcontrol VESA_132x60` or any other VESA mode, for that matter, the screen just goes blank. When I then type 'vidcontrol -g 100x37 VESA_800x600', or 'vidcontrol 80x25' my screen comes back. First I thought perhaps the prompt was hidden way off the visible area of my monitor, but fiddling with the knobs doesn't bring an answer. Is this a known problem with this chipset, or am I doing something silly? I'm running -CURRENT from a few days ago. Thanks! - Philip -- Philip Paeps Please don't CC me, I am [EMAIL PROTECTED] subscribed to the list. The one thing that money can not buy is poverty. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sis chipset
Hi, >Is there a chance to get the built in 100MBit network adapter in the chipset >working somehow? I thought I've fixed the support so it should work ? If not, do you have a "pciconf -lv" output for me ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
TCP is still broken
This program, based on one from the Apache 2 configure script, still causes
-current to lock up solid despite the recent bug fixes to the tcptw code.
Explicitly closing connected_s before returning from main() seems to avoid
the problem.
#include
#include
#include
#include
#include
#include
int main(void) {
int listen_s, connected_s, client_s;
int listen_port, rc;
struct sockaddr_in sa;
socklen_t sa_len;
socklen_t option_len;
int option;
listen_s = socket(AF_INET, SOCK_STREAM, 0);
if (listen_s < 0) {
perror("socket");
exit(1);
}
memset(&sa, 0, sizeof sa);
sa.sin_family = AF_INET;
/* leave port 0 to get ephemeral */
rc = bind(listen_s, (struct sockaddr *)&sa, sizeof sa);
if (rc < 0) {
perror("bind for ephemeral port");
exit(1);
}
/* find ephemeral port */
sa_len = sizeof(sa);
rc = getsockname(listen_s, (struct sockaddr *)&sa, &sa_len);
if (rc < 0) {
perror("getsockname");
exit(1);
}
listen_port = sa.sin_port;
rc = listen(listen_s, 5);
if (rc < 0) {
perror("listen");
exit(1);
}
client_s = socket(AF_INET, SOCK_STREAM, 0);
if (client_s < 0) {
perror("socket");
exit(1);
}
memset(&sa, 0, sizeof sa);
sa.sin_family = AF_INET;
sa.sin_port = listen_port;
/* leave sin_addr all zeros to use loopback */
rc = connect(client_s, (struct sockaddr *)&sa, sizeof sa);
if (rc < 0) {
perror("connect");
exit(1);
}
sa_len = sizeof sa;
connected_s = accept(listen_s, (struct sockaddr *)&sa, &sa_len);
if (connected_s < 0) {
perror("accept");
exit(1);
}
return 0;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
sis chipset
My ASUS board has a SiS 963 chip and I would like to get rid from the extra 3COM card I have presently in my system. Is there a chance to get the built in 100MBit network adapter in the chipset working somehow? -- Christoph Kukulies To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
wi0: tx failed, retry limit exceeded
I moved my server to new hardware and upgraded to 5.0-current ( 3 weeks ago) pppoe and my ADSL link is up and running since yesterday but my local wireless home network still refuses to work. I have a PCI pccard adapter with an ELSA (Lucent Orinoco) WLAN PCMCIA card which worked flawlessly under 4.4. Now I'm getting kernel messages wi0: tx failed, retry limit exceeded. -- Christoph Kukulies (please cc me, I'm currently not subscribed from the address I'm now sending from) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
