Warner Losh | 13 Aug 01:12 2014

Re: Support DISCARD (^O)


On Aug 12, 2014, at 2:44 PM, John Baldwin <jhb <at> FreeBSD.org> wrote:

> 
> -- 
> John Baldwin
> 
> From: Eivind Nicolay Evensen <eivinde <at> terraplane.org>
> Subject: Re: Support DISCARD (^O)
> Date: July 5, 2014 at 4:34:16 AM MDT
> To: freebsd-stable <at> freebsd.org
> 
> 
> On Tue, Dec 17, 2013 at 10:18:16PM +0100, Eivind Evensen wrote:
>> Hello.
>> 
>> I don't know if there is any particular reason that support for DISCARD/^O
>> was not included in the tty rewrite that happened from FreeBSD 7 to 8,
>> but in case anybody else wants it, here's a diff functioning mostly
>> like in 7, except output isn't switched back on automatically on input.
>> 
>> Diff is against FreeBSD 8, however, last time I checked I didn't see
>> much difference in the newer versions.
> 
> Here's a diff against FreeBSD 10. It seems to work fine there too.
> 
> 
> diff -r 59ad9c4b7916 -r 6e500f4552b4 sys/kern/tty_ttydisc.c
> --- a/sys/kern/tty_ttydisc.c	Fri Jul 04 17:27:59 2014 +0200
> +++ b/sys/kern/tty_ttydisc.c	Fri Jul 04 17:29:29 2014 +0200
(Continue reading)

Jamie Griffin | 12 Aug 10:26 2014
Picon

Hardware Info: WITH_NEW_XORG

Hi

For information purposes in case it helps or anyone is interested, I've 
built and installed the xorg server and utilities using the 
WITH_NEW_XORG knob and I can confirm it works very well on my hardware; 
which is:

Intel Q45 graphics controller, codenamed Eaglelake. CPU is Pentium 2xCore.

pciconf:

vgapci0 <at> pci0:0:2:0:     class=0x030000 card=0x304817aa chip=0x2e128086 
rev=0x03 hdr=0x00
     vendor     = 'Intel Corporation'
     device     = '4 Series Chipset Integrated Graphics Controller'
     class      = display
     subclass   = VGA
vgapci1 <at> pci0:0:2:1:     class=0x038000 card=0x304817aa chip=0x2e138086 
rev=0x03 hdr=0x00
     vendor     = 'Intel Corporation'
     device     = '4 Series Chipset Integrated Graphics Controller'
     class      = display

dmesg:

VT: running with driver "vga".
vgapci0: <VGA-compatible display> port 0x1c70-0x1c77 mem 
0xfc000000-0xfc3fffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
agp0: <Intel Q45 SVGA controller> on vgapci0
vgapci0: Boot video device
(Continue reading)

Garrett Wollman | 12 Aug 00:33 2014
Picon
Picon

Re: 9.3-RELEASE still instapanics on multi-mps(4) servers

In article <mit.lcs.mail.freebsd-stable/20140811205939.GY83475 <at> funkthat.com> you write:

>One thing you could do is turn on DEBUG_MEMGUARD and DEBUG_REDZONE
>and see if they trigger...

Did that last time around.  Either one will prevent the problem
entirely, without generating any diagnostics.

-GAWollman

--

-- 
Garrett A. Wollman    | What intellectual phenomenon can be older, or more oft
wollman <at> bimajority.org| repeated, than the story of a large research program
Opinions not shared by| that impaled itself upon a false central assumption
my employers.         | accepted by all practitioners? - S.J. Gould, 1993
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Garrett Wollman | 12 Aug 00:32 2014
Picon
Picon

Re: 9.3-RELEASE still instapanics on multi-mps(4) servers

In article <mit.lcs.mail.freebsd-stable/uh7ha1jryjg.fsf <at> P142s.sics.se> you write:

>I have a dual-mps (one Dell H200 and one LSI 9207) system now running
>9.1 (w patched sys/kern/kern_intr.c) that I intend to upgrade to 9.3
>shortly.  Is it enough to boot a 9.3 memstick to provoke the issue?

Yes, it was sufficient on both of the machines that have this problem
for me.  But two mps controllers might not be enough -- the machines
that fail for me all have three.  I have a patch (with debugging
printfs, not a fix) that I haven't had time to try yet, but should be
able to do that tomorrow.

-GAWollman

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Matthias Gamsjager | 10 Aug 20:09 2014
Picon

pkg problem

Hi,

Since a couple of days I get this error when doing a pkg upgrade:

root <at> freebsd:/home/ # pkg upgrade
Updating repository catalogue
Fetching meta.txz: 100% of 260 B
Fetching digests.txz: 100% of 18 KB
Fetching packagesite.txz: 100% of 90 KB

Incremental update completed, 372 packages processed:
0 packages updated, 0 removed and 0 added.
FreeBSD repository is up-to-date

Checking for upgrades: 100%
Assertion failed: (var == elt->var), function pkg_solve_sat_problem,
file pkg_solve.c, line 508.
Child process pid=44594 terminated abnormally: Abort trap

Any ideas what's wrong?
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Zoran Kolic | 9 Aug 15:45 2014

solved laptop X server mismatch

Just as the subject says, thanks to help of guys on
both lists, I succeeded to understand that there was
more than one app version on repo server.

Using search option to pkg, I found correct versions
and installed them on lenovo e320 laptop. X went up
at proper resolution. All seems fine on amd64 9.3. The
whole panic was my own mistake. xorg-server has new
1.12.4_8,1 version now.

I'd like to thanks again to all who took their time
to answer and help. Best regards

                              Zoran

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Zoran Kolic | 8 Aug 15:11 2014

Re: xorg problem

> Do you have sysutils/hal installed? Might be that xorg-minimal is a bit  
> too minimal?

Never used hal. 9.1 worked without it just fine.
If I get no clue in a day or two, I will stick
with "latest" repo and remove "new_xorg". Btw,
there should be a set of rules in FreeBSD_new_xorg
saying Freebsd: {enabled: no}, right? I do not
see it in manuals. That might be a reason I failed.
What I plan to do if everything else becomes
nothing is to remove new_xorg, upgrade again to
"latest", "pkg delete -f" libdrm, dri, xorg-server,
input-keyboard, input-mouse and video-intel. Then,
I would portmaster them (install them using still
existing lines in make.conf). How it sounds?
Thank you for answer. I feel stranded.

                       Zoran

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Zoran Kolic | 7 Aug 17:27 2014

xorg problem

Problem again. I upgraded to 9.3 and upgraded
packages using pkg upgrade -f. All went fine,
except I cannot run X.
Here is the log:

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/system:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 9.1-RELEASE-p17 amd64 
Current Operating System: FreeBSD mycenae 9.3-RELEASE FreeBSD 9.3-RELEASE #2: Thu Aug  7 16:11:06 CEST
2014     root <at> mycenae:/usr/obj/usr/src/sys/NEWKERN amd64
Build Date: 30 July 2014  11:17:45PM

Current version of pixman: 0.32.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug  7 17:19:23 2014
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(Continue reading)

Julie Koubová | 7 Aug 13:55 2014

Trying to upgrade from 9.2 to 10-STABLE, make buildworld fails on yacc

Hi,

I am trying to upgrade from 9.2 to 10-STABLE, kernel-toolchain and buildkernel completes successfully,
but make buildworld fails when linking yacc. Any ideas, please? I deleted everything in /usr/obj and
started from scratch, but it didn't help.

Hopefully all relevant files are here: 
https://gist.github.com/jachymko/8d1de9eb1826ae942f67

Thanks!
Julie
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Trond Endrestøl | 7 Aug 13:50 2014
Picon

Heads up! Some of your ports may erroneously be listed as depending on ports-mgmt/pkg

Hi,

The EOL for the old pkg_* tools is coming.

One thing to watch out for prior to running pkg2ng is the possible 
existence of /var/db/pkg/pkg-*/+REQUIRED_BY.

Simply delete this file and avoid the frustration I experienced 
earlier this week.

I wrote a few select words in my blog post, 
http://ximalas.info/2014/08/07/pkg2ng-some-notes-from-my-experience/. 
Maybe they're useful not only to me.

--

-- 
+-------------------------------+------------------------------------+
| Vennlig hilsen,               | Best regards,                      |
| Trond Endrestøl,              | Trond Endrestøl,                   |
| IT-ansvarlig,                 | System administrator,              |
| Fagskolen Innlandet,          | Gjøvik Technical College, Norway,  |
| tlf. mob.   952 62 567,       | Cellular...: +47 952 62 567,       |
| sentralbord 61 14 54 00.      | Switchboard: +47 61 14 54 00.      |
+-------------------------------+------------------------------------+
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"

Zoran Kolic | 7 Aug 06:21 2014

upgrade from memstick?

Is it possible to use memstick image to upgrade
freebsd? Like as openbsd has an option using the
bsd.rd file with <upgrade> to do the task?
I'm aware that freebsd-update would be the only
method available. Though not finding it right now,
there might be a way to point the app to the local
device using freebsd-update.conf file?
The reason to avoid net upgrade is sloweness of
the connection.
Best regards

                         Zoran

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"


Gmane