Re: Java and NIO?
g...@freebsd.org wrote .. > Howdy, > > Can someone tell me if anyone is working on this Java NIO bug? > > http://freebsd.1045724.n5.nabble.com/i386-159787-openjdk-1-6-nio-muti-thread-bug-td4700530.html > > I would like to avoid using Linux just to run Zookeeper: > > http://zookeeper-user.578899.n2.nabble.com/What-s-the-problem-with-nio-on-FreeBSD-td5208183.html > > Best, > George > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Hi George, There is/was a patch from David Xu http://lists.freebsd.org/pipermail/freebsd-java/2010-August/008747.html maybe this fixes it? also looks like New I/O was updated in jdk7... but would have to check it out to see if issue still exists.. -- Waitman Gobble San Jose California USA ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Why NOT using FreeBSD? Re: ports/169581: editors/libreoffice:
On Tue, Jul 03, 2012 at 10:59:03AM +0200, Hartmann, O. wrote: > On 07/02/12 08:09, Sayetsky Anton wrote: > > I will test libreoffice build on 8.3-RELEASE today or tomorrow. > > I have both gstreamer and boost installed now. > > > > > We use FreeBSD 9.0STABLE and FreeBSD 10.0-CURRENT (both amd64). > > devel/boost-lib gets reeled in now by editors/libreoffice by default, so > it doesn't need to be installed explicitely. > > I saw a patch flushed in yesterday, submitted by bapt@. This patch also > installs LLVM/CLANG from the ports - with ASSERTS deactivated. > > I have on both systems, FreeBSD 9 and 10, LLVM/CLANG 3.1 as the standard > backend compiler, I guess this version has the suspected ASSERTS activated. > > Why another LLVM port? We already have LLVM/CLANG in the base system (9 > and 19). If the ASSERTS proble is the cause for breaks reported on the > list and elsewhere on the net, why isn't the maintainer still stuck on > the "old" version? > > I just managed it to install the prior version on broken systems and was > really lucky having LibreOffice working again. But the other day I was > bothered by the next non-working version and now I have lots of > notebooks remaining with NO LibreOffice on FBSD 9-STABLE. > > This is not what I expect from quality securing! It is simply a mess and > definitely another reason and point for the thread "Why NOT using FreeBSD". > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" sure libreoffice is so easy to port... /me officially gives up with that libreoffice port, open for new volunteers bapt pgpbzelHb1oea.pgp Description: PGP signature
Java and NIO?
Howdy, Can someone tell me if anyone is working on this Java NIO bug? http://freebsd.1045724.n5.nabble.com/i386-159787-openjdk-1-6-nio-muti-thread-bug-td4700530.html I would like to avoid using Linux just to run Zookeeper: http://zookeeper-user.578899.n2.nabble.com/What-s-the-problem-with-nio-on-FreeBSD-td5208183.html Best, George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Why NOT using FreeBSD? Re: ports/169581: editors/libreoffice:
On 07/03/12 12:30, Chris Rees wrote: > On Jul 3, 2012 10:00 AM, "Hartmann, O." wrote: >> >> On 07/02/12 08:09, Sayetsky Anton wrote: >>> I will test libreoffice build on 8.3-RELEASE today or tomorrow. >>> I have both gstreamer and boost installed now. >>> >> >> >> We use FreeBSD 9.0STABLE and FreeBSD 10.0-CURRENT (both amd64). >> >> devel/boost-lib gets reeled in now by editors/libreoffice by default, so >> it doesn't need to be installed explicitely. >> >> I saw a patch flushed in yesterday, submitted by bapt@. This patch also >> installs LLVM/CLANG from the ports - with ASSERTS deactivated. >> >> I have on both systems, FreeBSD 9 and 10, LLVM/CLANG 3.1 as the standard >> backend compiler, I guess this version has the suspected ASSERTS > activated. >> >> Why another LLVM port? We already have LLVM/CLANG in the base system (9 >> and 19). If the ASSERTS proble is the cause for breaks reported on the >> list and elsewhere on the net, why isn't the maintainer still stuck on >> the "old" version? >> >> I just managed it to install the prior version on broken systems and was >> really lucky having LibreOffice working again. But the other day I was >> bothered by the next non-working version and now I have lots of >> notebooks remaining with NO LibreOffice on FBSD 9-STABLE. >> >> This is not what I expect from quality securing! It is simply a mess and >> definitely another reason and point for the thread "Why NOT using > FreeBSD". > > For anyone struggling with the new version of libreoffice, I made a package > for 9/amd64. > > http://www.bayofrum.net/tb/packages/9-local/All/libreoffice-3.5.4.tbz > > Setting up a Tinderbox is easy, and will fix the problems you are having. > > Please heed advice before shouting and blaming about problems. > > Chris > Thank you very much for the package, I'll try it and report back in. Oliver ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Tuesday, July 03, 2012 a las 09:51:37AM +0900, Kaho Toshikazu escribió:
> Hello Matthias Apitz and -current member,
>
> "sys/dev/atkbdc/atkbdc_isa.c" may not have your keyboard controller's ID.
> Run `acpidump -dt` and search your keyboard description.
> Is your keyboard controller "PNP0303" ?
>
> --
> k...@ed.niigata-u.ac.jp
Hello Kaho Toshikazu and all,
The command `acpidump -dt` in both releases (r21 and r235646) gives
an error:
# acpidump -dt > /tmp/acpidump-r21.txt
acpidump: RSDT entry 2 (sig OEMB) is corrupt
the output in r235646 is only some 70 lines and in r21 I do not see
any keyboard related; so I can't answer your question if the
keyboard controller is "PNP0303";
Based on r235646 sources, I have checked the SVN-diff between r21
(where the keyboard is working) and r235646, see attachment
/tmp/atkbdc_isa.c-r21:r235646; and the logic of the kb detection has
changed; I will just give it a try and will revert this SVN change, i.e.
'svn up -r r21 atkbdc_isa.c
to see if this works... it does not help;
Thanks
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
Index: atkbdc_isa.c
===
--- atkbdc_isa.c(revision 21)
+++ atkbdc_isa.c(revision 235646)
@@ -49,6 +49,11 @@
static int atkbdc_isa_attach(device_t dev);
static device_tatkbdc_isa_add_child(device_t bus, u_int order, const
char *name,
int unit);
+static struct resource *atkbdc_isa_alloc_resource(device_t dev, device_t child,
+ int type, int *rid, u_long start, u_long end,
+ u_long count, u_int flags);
+static int atkbdc_isa_release_resource(device_t dev, device_t child,
+ int type, int rid, struct resource *r);
static device_method_t atkbdc_isa_methods[] = {
DEVMETHOD(device_probe, atkbdc_isa_probe),
@@ -61,8 +66,8 @@
DEVMETHOD(bus_read_ivar,atkbdc_read_ivar),
DEVMETHOD(bus_write_ivar, atkbdc_write_ivar),
DEVMETHOD(bus_get_resource_list,atkbdc_get_resource_list),
- DEVMETHOD(bus_alloc_resource, bus_generic_rl_alloc_resource),
- DEVMETHOD(bus_release_resource, bus_generic_rl_release_resource),
+ DEVMETHOD(bus_alloc_resource, atkbdc_isa_alloc_resource),
+ DEVMETHOD(bus_release_resource, atkbdc_isa_release_resource),
DEVMETHOD(bus_activate_resource, bus_generic_activate_resource),
DEVMETHOD(bus_deactivate_resource, bus_generic_deactivate_resource),
DEVMETHOD(bus_get_resource, bus_generic_rl_get_resource),
@@ -82,6 +87,7 @@
static struct isa_pnp_id atkbdc_ids[] = {
{ 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
+ { 0x2003d041, "Keyboard controller (i8042)" }, /* PNP0320 */
{ 0 }
};
@@ -170,8 +176,6 @@
device_verbose(dev);
error = atkbdc_probe_unit(device_get_unit(dev), port0, port1);
- if (error == 0)
- bus_generic_probe(dev);
bus_release_resource(dev, SYS_RES_IOPORT, 0, port0);
bus_release_resource(dev, SYS_RES_IOPORT, 1, port1);
@@ -216,14 +220,25 @@
return ENXIO;
}
+ /*
+* If the device is not created by the PnP BIOS or ACPI, then
+* the hint for the IRQ is on the child atkbd device, not the
+* keyboard controller, so this can fail.
+*/
+ rid = 0;
+ sc->irq = bus_alloc_resource_any(dev, SYS_RES_IRQ, &rid, RF_ACTIVE);
+
error = atkbdc_attach_unit(unit, sc, sc->port0, sc->port1);
if (error) {
bus_release_resource(dev, SYS_RES_IOPORT, 0, sc->port0);
bus_release_resource(dev, SYS_RES_IOPORT, 1, sc->port1);
+ if (sc->irq != NULL)
+ bus_release_resource(dev, SYS_RES_IRQ, 0, sc->irq);
return error;
}
*(atkbdc_softc_t **)device_get_softc(dev) = sc;
+ bus_generic_probe(dev);
bus_generic_attach(dev);
return 0;
@@ -233,9 +248,11 @@
atkbdc_isa_add_child(device_t bus, u_int order, const char *name, int unit)
{
atkbdc_device_t *ivar;
+ atkbdc_softc_t *sc;
device_tchild;
int t;
+ sc = *(atkbdc_softc_t **)device_get_softc(bus);
ivar = malloc(sizeof(struct atkbdc_device), M_ATKBDDEV,
M_NOWAIT | M_ZERO);
if (!ivar)
@@ -251,18 +268,21 @@
ivar->rid = order;
/*
-* If the device is not created by the PnP BIOS or ACPI,
-* refer to device hints for IRQ.
+* If the device is not created by the PnP BIOS or ACPI, refer
+* to device hints for IRQ. We always populate the resource
+* li
Re: Why NOT using FreeBSD? Re: ports/169581: editors/libreoffice:
On Jul 3, 2012 10:00 AM, "Hartmann, O." wrote: > > On 07/02/12 08:09, Sayetsky Anton wrote: > > I will test libreoffice build on 8.3-RELEASE today or tomorrow. > > I have both gstreamer and boost installed now. > > > > > We use FreeBSD 9.0STABLE and FreeBSD 10.0-CURRENT (both amd64). > > devel/boost-lib gets reeled in now by editors/libreoffice by default, so > it doesn't need to be installed explicitely. > > I saw a patch flushed in yesterday, submitted by bapt@. This patch also > installs LLVM/CLANG from the ports - with ASSERTS deactivated. > > I have on both systems, FreeBSD 9 and 10, LLVM/CLANG 3.1 as the standard > backend compiler, I guess this version has the suspected ASSERTS activated. > > Why another LLVM port? We already have LLVM/CLANG in the base system (9 > and 19). If the ASSERTS proble is the cause for breaks reported on the > list and elsewhere on the net, why isn't the maintainer still stuck on > the "old" version? > > I just managed it to install the prior version on broken systems and was > really lucky having LibreOffice working again. But the other day I was > bothered by the next non-working version and now I have lots of > notebooks remaining with NO LibreOffice on FBSD 9-STABLE. > > This is not what I expect from quality securing! It is simply a mess and > definitely another reason and point for the thread "Why NOT using FreeBSD". For anyone struggling with the new version of libreoffice, I made a package for 9/amd64. http://www.bayofrum.net/tb/packages/9-local/All/libreoffice-3.5.4.tbz Setting up a Tinderbox is easy, and will fix the problems you are having. Please heed advice before shouting and blaming about problems. Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Why NOT using FreeBSD? Re: ports/169581: editors/libreoffice:
On 07/02/12 08:09, Sayetsky Anton wrote: > I will test libreoffice build on 8.3-RELEASE today or tomorrow. > I have both gstreamer and boost installed now. > We use FreeBSD 9.0STABLE and FreeBSD 10.0-CURRENT (both amd64). devel/boost-lib gets reeled in now by editors/libreoffice by default, so it doesn't need to be installed explicitely. I saw a patch flushed in yesterday, submitted by bapt@. This patch also installs LLVM/CLANG from the ports - with ASSERTS deactivated. I have on both systems, FreeBSD 9 and 10, LLVM/CLANG 3.1 as the standard backend compiler, I guess this version has the suspected ASSERTS activated. Why another LLVM port? We already have LLVM/CLANG in the base system (9 and 19). If the ASSERTS proble is the cause for breaks reported on the list and elsewhere on the net, why isn't the maintainer still stuck on the "old" version? I just managed it to install the prior version on broken systems and was really lucky having LibreOffice working again. But the other day I was bothered by the next non-working version and now I have lots of notebooks remaining with NO LibreOffice on FBSD 9-STABLE. This is not what I expect from quality securing! It is simply a mess and definitely another reason and point for the thread "Why NOT using FreeBSD". ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
