Re: bin/64198: init(8) may keep zombies
Hi! The problem is still here for 6.0-STABLE: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/64198 For this version init leaves a process not in 'Z' (zombie) state but in 'RE' (trying to exit) state that's strange. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with new DRI/DRM support for Intel 855GM
Le Mardi 27 Décembre 2005 02:48, Julian Stecklina a écrit : Hello, > I just discovered that the DRM drivers have been updated and my 855GM > is now supported by i915.ko. > > If I load the module, the driver attaches: ... > The problem is easily spotted, as there is only /dev/dri/card1. If I > try to symlink card1 to card0, the kernel says: > error: [drm:pid890:drm_unlock] *ERROR* Process 890 using kernel context 0 Look this thread : http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020815.html > But anyway: It's very nice to see that 3D acceleration is going to > work Real Soon Now(tm) on my laptop. :-) Yes :) Regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i915drm
Le Lundi 19 Décembre 2005 21:35, Oliver Fromme : > Patrick Lamaizière <[EMAIL PROTECTED]> wrote: > > But dri does not work, Xorg seems to look for a /dev/dri/card0 and > > i've got only one device /dev/dri/card1 ? > Strange. It works fine for me: With the patch from Alexey Popov (ftp://213.85.11.250/pub/drm3.patch) i've got the good device /dev/dri/card0 > Are you sure that you're using the latest RELENG_6 _and_ > the latest Xorg development snapshot? You need both for > things to work correctly. Yes i run 6.0-STABLE, graphics/dri-devel (dri-6.2.20050719,1) and x11-server/xorg-server-snap (xorg-server-6.8.99.903) With xorg-server-snap i've got the problem : $ glxgears ERROR: line 125, Function intelInitDriver, File intel_screen.c It seems better with xorg-6.8.2, dri is enabled and glxgears reports a FPS ~1200. I've got 500 FPS without DRI. more info about the chipset: [EMAIL PROTECTED]:2:0: class=0x03 card=0x01641028 chip=0x35828086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82852GM/GME/GMV/PM, 855GM/GME Montara Integrated Graphics Device' class= display subclass = VGA Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6-STABLE: panic: vinvalbuf: dirty bufs
Hi guys, [ please Cc: me in your replies as I am not subscribed to this list ] I have a 6-STABLE box : % FreeBSD obiwan.tataz.chchile.org 6.0-STABLE FreeBSD 6.0-STABLE #0: Mon Nov 7 11:50:33 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I got a panic as stated in the subject. In order to not overload the mailing list, I put the dmesg extracted from the core as well as the kgdb(1) backtrace in the following files on my webserver. Note that the dmesg contains errors I got just before the box panic()'ed. http://jeremie.le-hen.org/~tataz/dumps/dmesg.panic.vinvalbuf-dirty_bufs.txt http://jeremie.le-hen.org/~tataz/dumps/kgdb.panic.vinvalbuf-dirty_bufs.txt If you need it, here is a dmesg of an alive system : http://jeremie.le-hen.org/~tataz/dumps/dmesg.no_panic.txt I hope this will help to sweep out the bug. In case you need more things, such as a full backtrace or verbose boot dmesg, please, let me know. FWIW, does the following error means my disk is dead ? % unknown: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=487055103 Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compat 5x libraries missnig after restart
Doug Barton wrote: Add the following to /etc/rc.conf.local: compat5x_enable=yes And it would probably help if you watched the messages printed to the console as the system boots. And you should also have read the message that came when you installed the port - you know, the one that immediately scrolled off the top of the screen. And you should also have checked ports/UPDATING - oops, scratch that last piece of advice. Seriously, I consider my self lucky, not superior, that I caught this change and didn't face the same problems as the OP. I hope you guys fix this "feature" before RELEASE-6.1, otherwise the mailing lists are going to be full of this issue. Stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [fbsd] 6-STABLE panic: unusable core file
Hi, > % obiwan:crash# kgdb kernel.debug vmcore.17 > % kgdb: kvm_read: invalid address (0x190011) > % kgdb: kvm_read: invalid address (0x1000) > % kgdb: kvm_read: invalid address (0x113) > % kgdb: kvm_read: invalid address (0x113) > % kgdb: kvm_read: invalid address (0x113) > % ... > > What am I supposed to do ? Is there a fix to get in HEAD sources or > am I doing things in the wrong way ? My kernel.debug files was not the good one, sorry for the noise. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6-STABLE panic: unusable core file
Hi list, [ please Cc: me in your reply as I am not subscribed to this list ] my 6-STABLE box panic()'ed and generated a crash dump. Once the box was online again, I wanted to get the backtrace with kgdb(1) in order to post here there. Unfortunately, I get the following endless error, as if kgdb(1) entered in an infinite loop : % obiwan:crash# kgdb kernel.debug vmcore.17 % kgdb: kvm_read: invalid address (0x190011) % kgdb: kvm_read: invalid address (0x1000) % kgdb: kvm_read: invalid address (0x113) % kgdb: kvm_read: invalid address (0x113) % kgdb: kvm_read: invalid address (0x113) % ... What am I supposed to do ? Is there a fix to get in HEAD sources or am I doing things in the wrong way ? Thank you. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
On 12/27/05, David Malone <[EMAIL PROTECTED]> wrote: > On Sun, Dec 25, 2005 at 06:41:57PM +0200, Rostislav Krasny wrote: > > defined as 4. In a case the DNS server isn't responding the > > gethostbyname() makes 8 (eight!) reverse resolving attempts for one > > (!) non-responding DNS server before it returns error. And this is by > > default. All that is still true for my current 6.0-STABLE. > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/62139 > > > > As a workaround I may suggest addind "options attempts:2" or even > > "options attempts:1" line to the /etc/resolver.conf > > I've often thought that we shouled make the default login timeout > longer than our DNS timeout, as it means it is hard (or impossible) > to log in to fix your DNS server when your DNS server is down. It > is even worse if you don't control some DNS server in the chain > between the root and the name you're trying to look up. > > I did once mail des@ to ask him if he'd mind me changing the default > login timeout for sshd to be (say) 5 minutes rather than 1 minute, > but I think he was busy at the time. Judging by the PR mentioned > above it should be at least 2m30s by default. I think the RES_DFLRETRY should also be decreased from 4 to 2, as it is defined in most of other systems. By the way, BIND9, that is a part of the FreeBSD base system, has its own resolver, where the RES_DFLRETRY defined as 2 (ses below): > grep RES_DFLRETRY /usr/src/contrib/bind9/lib/bind/include/resolv.h #define RES_DFLRETRY2 /* Default #/tries. */ > grep RES_DFLRETRY /usr/include/resolv.h #define RES_DFLRETRY4 /* retries per each name server */ And doubling of this number of retries by functions like gethostbyname() is also mysterious for me yet. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compat 5x libraries missnig after restart
Add the following to /etc/rc.conf.local: compat5x_enable=yes And it would probably help if you watched the messages printed to the console as the system boots. -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
On Sun, Dec 25, 2005 at 06:41:57PM +0200, Rostislav Krasny wrote: > defined as 4. In a case the DNS server isn't responding the > gethostbyname() makes 8 (eight!) reverse resolving attempts for one > (!) non-responding DNS server before it returns error. And this is by > default. All that is still true for my current 6.0-STABLE. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/62139 > > As a workaround I may suggest addind "options attempts:2" or even > "options attempts:1" line to the /etc/resolver.conf I've often thought that we shouled make the default login timeout longer than our DNS timeout, as it means it is hard (or impossible) to log in to fix your DNS server when your DNS server is down. It is even worse if you don't control some DNS server in the chain between the root and the name you're trying to look up. I did once mail des@ to ask him if he'd mind me changing the default login timeout for sshd to be (say) 5 minutes rather than 1 minute, but I think he was busy at the time. Judging by the PR mentioned above it should be at least 2m30s by default. Des, would you mind this change being made? David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
patch against xl(4) regression in RELENG_6
Colleagues,
here is WIP patch for the regression with PCMCIA 3Com cards that
you have reported. Please test it and tell whether it helps.
--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
Index: cardbus.c
===
RCS file: /home/ncvs/src/sys/dev/cardbus/cardbus.c,v
retrieving revision 1.54
diff -u -r1.54 cardbus.c
--- cardbus.c 28 Oct 2005 06:03:53 - 1.54
+++ cardbus.c 26 Dec 2005 10:17:47 -
@@ -149,14 +149,6 @@
cardbus_add_map(cbdev, child, PCIR_BAR(reg));
}
-static void
-cardbus_do_res(struct resource_list_entry *rle, device_t child, uint32_t start)
-{
- rle->start = start;
- rle->end = start + rle->count - 1;
- pci_write_config(child, rle->rid, rle->start, 4);
-}
-
static int
cardbus_barsort(const void *a, const void *b)
{
@@ -249,8 +241,16 @@
rle = barlist[tmp];
if (rle->type == SYS_RES_MEMORY &&
dinfo->mprefetchable & BARBIT(rle->rid)) {
- cardbus_do_res(rle, child, start);
- start += rle->count;
+ rle->res = bus_alloc_resource(cbdev,
+ rle->type, &rle->rid, start, end,
+ rle->count,
+ rman_make_alignment_flags(rle->count));
+ if (rle->res != NULL) {
+ rle->start = rman_get_start(rle->res);
+ rle->end = rman_get_end(rle->res);
+ pci_write_config(child,
+ rle->rid, rle->start, 4);
+ }
}
}
}
@@ -297,8 +297,20 @@
rle = barlist[tmp];
if (rle->type == SYS_RES_MEMORY &&
(dinfo->mprefetchable & BARBIT(rle->rid)) == 0) {
- cardbus_do_res(rle, child, start);
- start += rle->count;
+ rle->res = bus_alloc_resource(cbdev,
+ rle->type, &rle->rid, start, end,
+ rle->count,
+ rman_make_alignment_flags(rle->count));
+ if (rle->res == NULL) {
+ DEVPRINTF((cbdev, "Cannot pre-allocate "
+ "memory for cardbus device\n"));
+ free(barlist, M_DEVBUF);
+ return (ENOMEM);
+ }
+ rle->start = rman_get_start(rle->res);
+ rle->end = rman_get_end(rle->res);
+ pci_write_config(child,
+ rle->rid, rle->start, 4);
}
}
}
@@ -341,8 +353,20 @@
for (tmp = 0; tmp < count; tmp++) {
rle = barlist[tmp];
if (rle->type == SYS_RES_IOPORT) {
- cardbus_do_res(rle, child, start);
- start += rle->count;
+ rle->res = bus_alloc_resource(cbdev,
+ rle->type, &rle->rid, start, end,
+ rle->count,
+ rman_make_alignment_flags(rle->count));
+ if (rle->res == NULL) {
+ DEVPRINTF((cbdev, "Cannot pre-allocate "
+ "IO port for cardbus device\n"));
+ free(barlist, M_DEVBUF);
+ return (ENOMEM);
+ }
+ rle->start = rman_get_start(rle->res);
+ rle->end = rman_get_end(rle->res);
+ pci_write_config(child,
+ rle->rid, rle->start, 4);
}
}
}
@@ -357,9 +381,10 @@
}
start = rman_get_start(res);
end = rman_get_end(res);
- bus_release_resource(cbdev, SYS_RES_IRQ, rid, res);
resource_list_add(&dinfo->pci.resources, SYS_RES_IRQ, rid, start, end,
1);
+ rle = resource_list_find(&dinfo->pci.resources, SYS_RES_IRQ, rid);
+ rle->res = res;
dinfo->pci.cfg.intline = start;
pci_write_config(child, PCIR_INTLINE, start, 1);
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mai
compat 5x libraries missnig after restart
Hello, I'm using 6-STABLE for desktop, but recenty some ports like archives/rar multimedia/amarok and others stop working after restart. I found the libraries required in misc/compat5x but every time the pc is restarted I need to reinstall this port!. I can figure what is happening.. Also may be related with this behavior is that gtk2 dependent apps crash when I switch to another desktop with the kde pager. Any help will be apreciated. Greetings from Argentina. This message was sent using IMP, the Internet Messaging Program. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On 21/12/2005, at 7:23 PM, Doug Barton wrote: As has been discussed for a couple weeks now, I have MFC'ed to RELENG_6 the changes in /etc/rc* that bring new-style boot scripts from the local_startup directories (by default /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d) into the base rcorder. How does this correlate with the planned implementation of launchd in FreeBSD? http://wikitest.freebsd.org/moin.cgi/launchd Perhaps it is too early for you to say, but it would seem that launchd is a much more sophisticated system that would bring a whole range of benefits to FreeBSD. Is work still progressing on that? Will these changes to /etc/rc allow for a migration path? Cheers Ari Maniatis --> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 PGP fingerprint 08 57 20 4B 80 69 59 E2 A9 BF 2D 48 C2 20 0C C8 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
