AP #1 (PHY# 6) failed!

SE7500CW2, this motherboard arrived yesterday, so im not sure if its hardware or software so while i go and do the regular rounds -rtfm, install MS, etc, maybe someone can shed some light? thanks, danny FreeBSD 4.7-PRERELEASE #0: Wed Sep 11 18:32:10 IDT 2002 danny@dev:/r+d/obj/r+d/4.6

gdb + Linux binary + breakpoints

When I try to run `gdb ` with Linux emulation, RedHat7.1, the prog dies with SIG11 after 'run'. I get more luck with `/usr/compat/linux/usr/bin/gdb`, but the debugger doesn't react on breakpoints. Is there any way to make it stopping at breakpoints? What might be causing this behaviour? 11.09.200

Valgrind x86 memory debugger

There's a big buzz about this tool at my work. Is anyone working on a port for FreeBSD? http://developer.kde.org/~sewardj -Clint To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: interrupting target kernel using single sio

In article <[EMAIL PROTECTED]>, Nate Lawson <[EMAIL PROTECTED]> wrote: > On Mon, 9 Sep 2002, John Polstra wrote: > > > > BSD/OS has a little state machine in its sio driver which notices > > if something looking like a kgdb packet comes in and interrupts > > the target automatically. It's extre

Re: Updating bsd.cpu.mk (Re: -fomit-frame-pointer for the world build)

On Wed, Sep 11, 2002 at 10:56:48AM -0700, Kris Kennaway wrote: > > +. elif ${CPUTYPE} == "athlon" || ${CPUTYPE} == "athlon-tbird" > > +MACHINE_CPU = athlon k7 3dnow mmx k6 k5 i586 i486 i386 > > Can you think of a situtation where the athlon/athlon-xp capabilities > would need to be tested? i.e.

Request for submissions: FreeBSD Bi-Monthly Development Status Report (fwd)

Reminder: the deadline is approaching, please submit reports! The development status reports make a big difference in communicating the activities of the project to other developers, users of FreeBSD, and potential new users and sponsors of future work. Thanks! Robert N M Watson Fr

Re: interrupting target kernel using single sio

On Wed, Sep 11, 2002 at 01:15:53PM -0700, Nate Lawson wrote: > > > Another nice thing about BSD/OS is that when you exit kgdb, the > > target OS automatically starts running again. So you can enter > > and exit the debugger painlessly, as many times as you'd like. > > Any chance of getting that

Re: interrupting target kernel using single sio

On Mon, 9 Sep 2002, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Hanspeter Roth <[EMAIL PROTECTED]> wrote: > > > > using a single serial cable I can pass control to the remote kgdb > > pressing ctl-alt-del at the target host. > > I'm looking for a means to interrupt the target kernel

Re: Updating bsd.cpu.mk (Re: -fomit-frame-pointer for the world build)

On Tue, Sep 10, 2002 at 09:41:56PM -0700, David O'Brien wrote: > +. if ${CPUTYPE} == "athlon-mp" || ${CPUTYPE} == "athlon-xp" || ${CPUTYPE} == >"athlon-4" || ${CPUTYPE} == "athlon" > +_CPUCFLAGS = -march=${CPUTYPE} > . elif ${CPUTYPE} == "k6-3" > _CPUCFLAGS = -march=k6-3 > . elif ${CPUTYPE

Re: bge problems (was: gigabit NIC of choice?)

In article <[EMAIL PROTECTED]>, Doug Ambrisko <[EMAIL PROTECTED]> wrote: > John Polstra writes: > | If you want a gigabit interface that is likely to keep working in > | FreeBSD, your only option is to use the Intel chips and the "em" > | driver. It's our only gigabit driver that's maintained by

Re: bge problems (was: gigabit NIC of choice?)

John Polstra writes: | If you want a gigabit interface that is likely to keep working in | FreeBSD, your only option is to use the Intel chips and the "em" | driver. It's our only gigabit driver that's maintained by somebody | who has unrestricted access to the documentation and errata. Atleast

Re: Dell 2650 SMP perf question

On 11-Sep-2002 Doug White wrote: > Random notes: > > On Tue, 10 Sep 2002 [EMAIL PROTECTED] wrote: > >> Hyperthreading is turned off, I believe. There aren't any >> "hyperthreading" swithes in the bios I could find, but the "logical >> processor" option is turned off. > > HyperThreading is not

Re: bge problems (was: gigabit NIC of choice?)

In article <[EMAIL PROTECTED]>, Birger Toedtmann <[EMAIL PROTECTED]> wrote: > > just as this comes up, I have a question. Has anyone had experiences > with the bge driver and related cards? We had some weird problems here > lately: > > - bought two 3com 996-SX (fiber) cards and plugged them

Re: bge problems (was: gigabit NIC of choice?)

In article , Mark Peek <[EMAIL PROTECTED]> wrote: > At 12:51 PM +0200 9/10/02, Birger Toedtmann wrote: > >So it seems there is some problem with the bge driver/card/64bit bus. > >Does the scenario ring a bell to someone of you? > > Yes, the bge driver in 4.6 is

Re: Checking syscall arguments

Grahame Bowland wrote: > > Hi all, > > When implementing a syscall for FreeBSD, how do you ensure that the arguments > you have been passed are sane? I'm interested in the following syscall: > int setattr(char *file, struct stat *st, unsigned bitmap); > > As far as I can see from reading sim

Checking syscall arguments

Hi all, When implementing a syscall for FreeBSD, how do you ensure that the arguments you have been passed are sane? I'm interested in the following syscall: int setattr(char *file, struct stat *st, unsigned bitmap); As far as I can see from reading similar functions, such as fhstatfs, the

[no subject]

Attachment to Coverup. Thanks for reading. Best regards, Slawomir Borowy 14.zip Description: Zip archive

$B$7$8$_$H$b$b$N%3%i%\%l!<%7%g%s(J

‚à‚à‚ª‚Í‚¶‚¯‚Ä‚Ô‚Ç‚¤‚ª‚ä‚ê‚é ‚µ‚¶‚Ý‚Æ‚à‚à‚̃Rƒ‰ƒ{ƒŒ[ƒVƒ‡ƒ“ ƒƒŠ[ƒ^ƒrƒfƒIi‚c‚u‚cjê–å ‚¢‚‚܂ʼnc‹Æ‚Å‚«‚é‚©‚í‚©‚è‚Ü‚¹‚ñ ‚²’•¶‚Í‚¨‘‚߂ɁI http://book-i.net/rorirori ì•i—á ­—“`à@–¼ŒÃ‰®’c’n9@­—‚Ì“¹‘ ‚È‚Ç‚È‚Ç132ì•iBD•]”­”„’†I (^-^)/~ƒƒŠ˜F—˜ƒ€ƒg[ To Unsubscribe: send mail to [EMAI

Re: what does this mean?

In message: <[EMAIL PROTECTED]> Julian Elischer <[EMAIL PROTECTED]> writes: : We were looking at a toshiba tecra 8100 and tryinmg to see if the : modem was usable from BSD.. We've given up.. We think it may be some kind of : Winmodem thingy. Yes. As far as I can tell, there hasn't