Apologies for the bounced messages.

Hi everyone Due to some issues with my mailserver configuration. Some of the messages bounced back on the list. Please accept my apologies for that inconvenience. And I make sure not to repeat this again. Sorry again, Ashish SHUKLA -- They who can give up essential liberty to obtain a little

TCP BBR in 13.0-RC2 not playing well with pf firewall

___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

TCP BBR in 13.0-RC2 not playing well with pf firewall

[sorry for some reason, the previous message is showing as empty in archives :(] Hi, I just wanted to try TCP BBR functionality available in FreeBSD 13.0-RC2 and noticed that it’s not usable, if FreeBSD pf is enabled. I’m using following pf rules: === block drop all block drop in q

GCC segfaulting while trying to compile latest Qt4 code

] http://wahjava.googlepages.com/crash.tar.bz2 Thanks in advance. -- Ashish SHUKLA pgpkdbZXCNu9L.pgp Description: PGP signature

Re: GCC segfaulting while trying to compile latest Qt4 code

Daniel O'Connor writes: > On Thursday 05 March 2009 02:44:14 Ashish SHUKLA wrote: >> Hi everone, >> >> While trying to update my 'qt4-gui' port, gcc segfaults during >> compilation. I'm running FreeBSD 7.1-STABLE (amd64 architecture) updated &

Re: GCC segfaulting while trying to compile latest Qt4 code

John Baldwin writes: > On Thursday 05 March 2009 11:48:11 am Mark Atkinson wrote: >> Ashish SHUKLA wrote: >> >> > Daniel O'Connor writes: >> >> On Thursday 05 March 2009 02:44:14 Ashish SHUKLA wrote: >> >>> Hi everone, >> >>>

Re: GCC segfaulting while trying to compile latest Qt4 code

Forgot to attach the logs from the last mail. -- Ashish SHUKLA pgpH53VaKJM1m.pgp Description: PGP signature boot.old.log.gz Description: old boot log boot.new.log.gz Description: new boot log ___ freebsd-stable@freebsd.org mailing list http

Re: GCC segfaulting while trying to compile latest Qt4 code

nnot access memory at address 0x80000000 #v- References: [1] http://news.gmane.org/find-root.php?message_id=%3c84dead720902121838p3a72f993xc1c52104c666ed0a%40mail.gmail.com%3e HTH -- Ashish SHUKLA pgpTNMWxrdcnW.pgp Description: PGP signature

Re: GCC segfaulting while trying to compile latest Qt4 code

e-old might solve your compilation problems.If qt depends on > the gcc in ports, you may have to rebuild that one as well afterwards. Okay, I'll try updating my box again. -- Ashish SHUKLA pgpJCzlH3lbNg.pgp Description: PGP signature

Re: GCC segfaulting while trying to compile latest Qt4 code

Ashish SHUKLA writes: > Mark Atkinson writes: > [...] >> If Ashish is still having issues, I've seen this sort of thing with runtime >> library problems. Bad libmap entries and disk corruption can cause this. >> If you can complete a buildworld, a fresh bui

Re: Marvell Yukon 88E8062 - media selection problem

,--[ On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote: | Hi, | | I am trying to bring up gigabit interface in couple of Nexcom blade servers running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers) are recognized properly, but no media is ever detected: |