Re: kldxref broken, maybe?

At 12:05 PM -0700 9/20/01, David O'Brien wrote: On Wed, Sep 19, 2001 at 06:22:03PM -0700, Steve Kargl wrote: root[265] make installkernel cd /usr/obj/usr/src/sys/C456086-A; MAKEOBJDIRPREFIX=/usr/obj ... What steps lead up to this? ``make buildworld make kernel make kernelinstall''

Re: gdb(1) broken?

At 9:22 AM +0200 9/18/01, Mark Santcroos wrote: Hi Peter, What is the state of this (for i386)? Mark On Sun, Sep 16, 2001 at 11:24:54AM -0700, Julian Elischer wrote: Marcel Moolenaar wrote: Gang, I don't know exactly what the gdb(1) problems on Alpha are, but we do have a

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

At 9:14 PM -0500 10/19/01, Jonathan Lemon wrote: Below is the patch that I've sent to the people who reported the problem, I'm waiting to hear back from them that it works. Thanks for the real patch. It appears to work fine on my system. No log messages and arps look good so far. Mark To

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

At 11:23 AM +0200 10/18/01, Harti Brandt wrote: On Thu, 18 Oct 2001, Max Khon wrote: MKhi, there! MK MKOn Thu, Oct 18, 2001 at 12:00:52AM +0200, Jose M. Alcaide wrote: MK MK On Wed, Oct 17, 2001 at 12:11:45PM -0700, Julian Elischer wrote: MK I've seen this when DHCP fails to allocate an

Re: kldxref broken, maybe?

At 4:04 PM -0700 10/10/01, Peter Wemm wrote: Warner Losh wrote: In message [EMAIL PROTECTED] Crist J. Clark writes: : I think just running 'installworld' twice will fix it. The error is : non-fatal, but not without implications. The only one that I am aware : of is that your system might

Re: kldxref broken, maybe?

At 9:29 AM -0700 10/10/01, Bruce A. Mah wrote: OK, sounds good. Seems to me this is something that might deserve a mention in UPDATING. Something like: During a source upgrade of a 4-STABLE machine to -CURRENT, the installkernel step will attempt to execute a non-existent kldxref

Re: Mergemaster niggle

At 11:34 AM -0700 2/6/02, Lyndon Nerenberg wrote: David == David W Chapman [EMAIL PROTECTED] writes: David mergemaster only checks to see if RCSID's are different by David default, I forget which option, but there is one to actually David diff the two files when doing its

Re: Problem with gdb 5.2 from ports

At 6:14 PM +0300 6/16/02, Maxim Sobolev wrote: As you have requested, I installed devel/gdb52 port on my -current system and gave it a try. It works most of the time, but I've noticed that breakpoint set to a finction in a shared library doesn't work, at least for libraries which have no

Re: Please install and test the GDB 5.2 port

At 9:01 PM +0200 6/26/02, Joerg Wunsch wrote: David O'Brien [EMAIL PROTECTED] wrote: Mark Peek and DFR have made patches against GDB 5.2 such that it should do everything we need it to. It would be most helpful for people to test this before it goes into /usr/src. j@uriah 133% gdb52

Re: Please install and test the GDB 5.2 port

At 7:50 AM +0200 6/27/02, Joerg Wunsch wrote: As Mark Peek wrote: Hmm, so how to debug a kernel coredump? You need to update your gdb52 port. I can't find a newer one in CVS: j@uriah 85% pkg_info -I gdb-\* gdb-5.2_2 GNU GDB 5.2 developmental snapshot Very odd...here's what I

Panic in -current when using i386_set_ioperm()

There is a reproducible panic in -current after using i386_set_ioperm(). The extended pcb is attempted to be freed in cpu_thread_exit() using kmem_free(). Via private mail, Alan Cox explained it to me as such: The problem runs deeper than Giant not being held: cpu_thread_exit() really can't

Re: Problems with ata probing twice.

At 11:47 PM +0900 6/18/01, Makoto MATSUSHITA wrote: (from dmesg output) atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 This looks right to me. One main PIIX4 ATA controller with two independent

Re: can't build kernel: config doesn't work

At 10:05 AM -0400 7/1/01, Mike Heffner wrote: It works for me ;) Remember that the new default is: /sys/${MACHINEARCH}/compile/${KERNCONF} On 01-Jul-2001 Takeshi Ken Yamada wrote: | | The same here, but 'config -d /sys/compile/GENERIC GENERIC' | did what it is supposed to do. | | Is

Re: can't build kernel: config doesn't work

At 8:27 AM -0700 7/1/01, Alex Zepeda wrote: On Sun, Jul 01, 2001 at 08:09:14AM -0700, Mark Peek wrote: Right, there is a new compile directory. Perhaps this needs to be added to UPDATING. Anyway, did you run cvs update -dP on your cvs tree? Or just do mkdir on the new path mentioned above

Re: chgrp broken on alpha systems

At 4:37 PM +1000 7/6/01, Peter Jeremy wrote: Another random thought: If it was easier to build/install a cross-platform version of gcc, it might be easier to convince developers to at least check that compiling on different platforms works before committing. Peter, I had the same idea last

Re: Cross building FYI

At 3:43 PM -0700 7/10/01, David O'Brien wrote: On Tue, Jul 10, 2001 at 01:29:32PM -0700, Mark Peek wrote: Below are patches which allowed me to run an alpha cross build through to completion using: make -DNOPERL MACHINE_ARCH=alpha MAKEOBJDIRPREFIX=/usr/aobj buildworld Why

Re: chgrp broken on alpha systems

At 1:49 PM -0600 7/8/01, Warner Losh wrote: In message [EMAIL PROTECTED] David O'Brien writes: : On Sun, Jul 08, 2001 at 07:03:26PM +0200, Dag-Erling Smorgrav wrote: : Bruce Evans [EMAIL PROTECTED] writes: : [explaining how to build an LP64 world on i386] : : I just had a major doh moment...

Re: kill -s does not work.

At 3:12 PM -0400 8/7/01, David Hill wrote: While reading the exports(5) manpage, near the bottom is an example kill -s HUP `cat /var/run/mountd.pid` does kill -s causes this error: # kill -s HUP s: Unknown signal; kill -l lists signals. However, reading the kill(1) manpage, -s is documented.

Re: Problem with pxeboot and binutils-2.11

At 4:46 PM +0200 8/9/01, Harti Brandt wrote: some time ago we reported a problem with pxeboot under -current (see below). We have tried to track down the problem and it seems to be a bug or a feature in gas or libbfd. It turns out, that the output from pxeldr before the binutils-2.11 import on

Re: Kernel stack hogs list available

At 11:29 AM -0400 8/16/01, Robert Watson wrote: This is way cool stuff. I assume these are done based on i386 stack frame layouts? Running on other platforms will result in different alignment (minor issue, as most of the time it will just be a few bytes here or there), and some different code

Re: ELF interpreter /co not found

At 3:56 AM +0200 8/18/01, Niels Chr. Bank-Pedersen wrote: On Sat, Aug 18, 2001 at 02:34:35AM +0100, Pierre Y. Dampure wrote: The above message is what I get after upgrading from an August 7 to an August 17 world/kernel and trying to run linux-netscape47-communicator. Prior world/kernel

Re: [RFT] llquantize for FreeBSD's dtrace

On 6/23/12 11:09 AM, Pedro Giffuni wrote: --- Sab 23/6/12, Fabian Keil freebsd-lis...@fabiankeil.de ha scritto: ... My suggestion would be to instead try using the test scripts in cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/llquantize/ err.D_LLQUANT_FACTORSMALL.d (for example) has

Re: Deprecated bfd_read warnings in the gdb(1)

At 9:34 AM -0800 2/25/02, David O'Brien wrote: On Mon, Feb 25, 2002 at 11:51:54AM +0200, Maxim Sobolev wrote: I've noticed that after a recent make world gdb started producing warnings during startup. Please fix. Please send patch. This will require gdb to be updated to GDB 5.1.1 --

Re: Serial break into debugger broken from 'cu' on -CURRENT?

At 4:11 PM +0100 3/10/02, Wilko Bulte wrote: On Sun, Mar 10, 2002 at 10:07:07AM -0500, Robert Watson wrote: For the past couple of months, I've been working with a set of identical test boxes from SGI which, for some reason, stopped responding to serial break on the serial console. I

Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal

At 3:20 PM -0700 5/12/02, Marcel Moolenaar wrote: On Sun, May 12, 2002 at 11:27:42PM +0200, Poul-Henning Kamp wrote: It is not legal to recursively call malloc/free/realloc, and therefore you should either protect all calls to malloc/free/realloc by blocking signals or better: not call

Re: tcsh

At 6:14 PM +0200 5/19/02, Riccardo Torrini wrote: If exists a directory named sort tcsh chdir to that dir instead of executing sort present in path (and no, I have no . anywere in path) # pwd /usr/src/contrib # find . -name Makefile | sort # pwd /usr/src/contrib/sort # cd .. # find . -name

Re: gdb breaks world

At 2:58 PM -0700 5/19/02, Steve Kargl wrote: Finally, since you're quick with the wit, can you tell me how to debug the following problem when I can't compile the debugger. kargl[223] cat a.c #include stdlib.h int main(void) { /* This isn't the problem. The problem is with gdb. */

Re: gdb breaks world

At 10:54 AM -0700 5/27/02, David O'Brien wrote: Verify that your entire kernel is built with -g -gstabs+. If you still cannot use gdb on a core dump, maybe there is a core dump format change GDB needs to catch up with. Please use the various objdump, etc. tools to verify what type of debugging

Re: How to use gdb52 port

At 12:19 AM +0900 6/8/02, Jun Kuriyama wrote: I've installed gdb-5.2_1, but I cannot debug usual code. I've tried with -g, -gstabs+ and -g -gstabs+ but got same result. % cat test1.c int main() { int *p; *p = 1; } % cc -g test1.c -o test1 % ./test1 Bus error (core dumped) % gdb52 test1

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Fri, Mar 16, 2018 at 2:56 AM, Konstantin Belousov wrote: > On Thu, Mar 15, 2018 at 09:38:56PM -0500, Peter Lei wrote: > > Some recent UEFI implementations have begun to leave the CPU with page > > write protection enabled in CR0. > > > > With r330539 which enables kernel

Re: amd64: panic on -CURRENT @r330539 for certain UEFI hosts

On Fri, Mar 23, 2018 at 4:19 PM, Konstantin Belousov <kostik...@gmail.com> wrote: > On Fri, Mar 23, 2018 at 04:06:23PM -0700, Mark Peek wrote: > > I ran into the original issue with r330539 on a Fusion VM. Trying this > > patch causes a different panic: > > > &g

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

Thanks for the cc:. I forwarded the original report on to an internal VMware desktop product contact. What version of Workstation or Fusion is this occurring on? I saw Workstation 14 mentioned but curious if it occurs on Workstation 15 (latest). Mark On Fri, Dec 21, 2018 at 4:19 PM Warner Losh

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wrote: > > > On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > > > > Mark Peek wrote: > >> Thanks for the cc:. I forwarded the original report on to an internal > >> VMware desktop product contact. > > > &