Re: panic after starting X with r238120
On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills wrote: > Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set > it to 1 for some reason that I can't recall. > > That shouldn't cause a crash in pmap_enter(). What is line 3587 of pmap.c in your sources? You mentioned DRM. Are you using the new Intel graphics driver? Alan ___ 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"
bus_dmamem_alloc failed to align memory properly
Hi,
Someone reported to me that the following happens when allocating a 64K block
aligned to 64K:
freebsd/sys/x86/x86/busdma_machdep.c: printf("bus_dmamem_alloc failed
to align memory properly.\n");
Any clues how to debug?
--HPS
___
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: sk0 link bouncing
On Wed, Jul 04, 2012 at 12:08:16PM +0200, Willem Jan Withagen wrote: > Hi, > > I've got tons of these since I stopped loading the port with traffic > It seems to have a pretty steady 27 min interval. > > Jul 4 07:00:05 freetest kernel: sk0: link state changed to DOWN > Jul 4 07:00:05 freetest kernel: sk0: link state changed to UP > Jul 4 07:27:21 freetest kernel: sk0: link state changed to DOWN > Jul 4 07:27:21 freetest kernel: sk0: link state changed to UP > Jul 4 07:53:48 freetest kernel: sk0: link state changed to DOWN > Jul 4 07:53:48 freetest kernel: sk0: link state changed to UP > Jul 4 08:21:16 freetest kernel: sk0: link state changed to DOWN > Jul 4 08:21:16 freetest kernel: sk0: link state changed to UP > Jul 4 08:48:10 freetest kernel: sk0: link state changed to DOWN > Jul 4 08:48:11 freetest kernel: sk0: link state changed to UP > Jul 4 09:13:38 freetest kernel: sk0: link state changed to DOWN > Jul 4 09:13:38 freetest kernel: sk0: link state changed to UP > Jul 4 09:39:06 freetest kernel: sk0: link state changed to DOWN > Jul 4 09:39:06 freetest kernel: sk0: link state changed to UP > > Very recent 10-current install with std GENERIC kernel. > FreeBSD freetest.digiware.nl 10.0-CURRENT FreeBSD 10.0-CURRENT #1: Sat > Jun 30 09:35:43 UTC 2012 > r...@freetest.digiware.nl:/usr/obj/usr/src/sys/GENERIC amd64 > > The port is connected to a basic netgear 10/100/1000 switch with nothing > modified in the config of that port. > Other connections do not seem to suffer from disconnecting. > > Used the server to 'zfs send' a 360G backup to, and then it did not do > anything like this, the port just stayed up. > > Suggestions where of what to look for this? Probably you have to implement link state change handler for Marvell controller(i.e. sk_marv_miibus_statchg()). Locking for MII access should be revisited too. Sorry, don't have spare time to do that. > > Thanx, > --WjW ___ 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 Thursday, July 05, 2012 a las 03:36:22PM +0900, Kaho Toshikazu escribió:
> Hello Matthias Apitz, and ML members,
>
> Thanks to upload acpi dump. Your keyboard controller ID is "PNP030B",
> and your posted patch may be correct. Please undo your reversion,
> and try your patch.
Hello Kaho and all,
Yes! Now it works after inserting the line shown below:
$ dmesg | fgrep kbd
kbd1 at kbdmux0
atkbdc0: port 0x60,0x64 irq 1 on acpi0
atkbd0: irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: irq 12 on atkbdc0
also the mouse works fine;
Thanks for helping me getting to the point. I will later comment the bug
report in the issue tracker.
Interesting question remains: why it works in the older revision r21?
matthias
> > maybe it helps to add a line like this:
> >
> > static struct isa_pnp_id atkbdc_ids[] = {
> > { 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
> > { 0x2003d041, "Keyboard controller (i8042)" }, /* PNP0320 */
> > + { 0x0b03d041, "Keyboard controller (i8042)" }, /* PNP030B */
> > { 0 }
> >
> >
--
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
___
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 05/07/2012 08:19 Waitman Gobble said the following: > I can create and submit a port for libreoffice 3.6.0.0 if anyone is > interested in trying the "beta" version. Might take a few days. Still working > on it. We have mailing list off...@freebsd.org for people who are interested in openoffice, libreoffice, etc. Thank you for your work! -- Andriy Gapon ___ 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
Hello, > Interesting question remains: why it works in the older revision r21? I don't know exactly resource management, but ISA_PNP_PROBE() ignores device.hints if acpi unknown device takes resources. I think this problem is related to some acpi changes. -- k...@elam.kais.kyoto-u.ac.jp ___ 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"
[clang] world crossbuilding amd64 at i386 fails
Hi List, I've got a fresh CURRENT and try to build amd64 world at i386 host (TARGET=amd64). I get the error: - [...] ===> sbin/conscontrol (depend) ./gengenrtl -h > genrtl.h ./gengenrtl: Exec format error *** [genrtl.h] Error code 126 1 error - The system at the host is built with clang and with options: - WITH_CLANG_IS_CC="YES" WITH_LIBCPLUSPLUS="YES" - -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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
Hello Matthias Apitz, and ML members,
Thanks to upload acpi dump. Your keyboard controller ID is "PNP030B",
and your posted patch may be correct. Please undo your reversion,
and try your patch.
Matthias Apitz wrote:
> > and there is now an entry for "PS2K" (not for "KBC"):
> >
> > Device (PS2K)
> > {
> > Name (_HID, EisaId ("PNP030B"))
> > Name (_CID, EisaId ("PNP030B"))
> > Method (_STA, 0, NotSerialized)
> > {
> > ShiftLeft (0x01, 0x0A, Local0)
> > If (And (IOST, Local0))
> > {
> > Return (0x0F
> >
> > the full file is here: http://www.unixarea.de/acpidump-r21.txt
>
> maybe it helps to add a line like this:
>
> static struct isa_pnp_id atkbdc_ids[] = {
> { 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
> { 0x2003d041, "Keyboard controller (i8042)" }, /* PNP0320 */
> + { 0x0b03d041, "Keyboard controller (i8042)" }, /* PNP030B */
> { 0 }
>
>
--
k...@elam.kais.kyoto-u.ac.jp
___
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: sk0 link bouncing
On 2012-07-06 2:29, YongHyeon PYUN wrote: > On Wed, Jul 04, 2012 at 12:08:16PM +0200, Willem Jan Withagen wrote: >> Hi, >> >> I've got tons of these since I stopped loading the port with traffic >> It seems to have a pretty steady 27 min interval. >> >> Jul 4 07:00:05 freetest kernel: sk0: link state changed to DOWN >> Jul 4 07:00:05 freetest kernel: sk0: link state changed to UP >> Jul 4 07:27:21 freetest kernel: sk0: link state changed to DOWN >> Jul 4 07:27:21 freetest kernel: sk0: link state changed to UP >> Jul 4 07:53:48 freetest kernel: sk0: link state changed to DOWN >> Jul 4 07:53:48 freetest kernel: sk0: link state changed to UP >> Jul 4 08:21:16 freetest kernel: sk0: link state changed to DOWN >> Jul 4 08:21:16 freetest kernel: sk0: link state changed to UP >> Jul 4 08:48:10 freetest kernel: sk0: link state changed to DOWN >> Jul 4 08:48:11 freetest kernel: sk0: link state changed to UP >> Jul 4 09:13:38 freetest kernel: sk0: link state changed to DOWN >> Jul 4 09:13:38 freetest kernel: sk0: link state changed to UP >> Jul 4 09:39:06 freetest kernel: sk0: link state changed to DOWN >> Jul 4 09:39:06 freetest kernel: sk0: link state changed to UP >> >> Very recent 10-current install with std GENERIC kernel. >> FreeBSD freetest.digiware.nl 10.0-CURRENT FreeBSD 10.0-CURRENT #1: Sat >> Jun 30 09:35:43 UTC 2012 >> r...@freetest.digiware.nl:/usr/obj/usr/src/sys/GENERIC amd64 >> >> The port is connected to a basic netgear 10/100/1000 switch with nothing >> modified in the config of that port. >> Other connections do not seem to suffer from disconnecting. >> >> Used the server to 'zfs send' a 360G backup to, and then it did not do >> anything like this, the port just stayed up. >> >> Suggestions where of what to look for this? > > Probably you have to implement link state change handler for > Marvell controller(i.e. sk_marv_miibus_statchg()). Locking for > MII access should be revisited too. > Sorry, don't have spare time to do that. I think I understand you comments. But I do not have the knowledge to do this. :( The board also has an msk0, which I'm now trying. Thanx, --WjW ___ 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: Java and NIO?
On Jul 4, 2012, at 15:49 , Greg Lewis wrote: > On Tue, Jul 03, 2012 at 11:38:23AM -0700, Waitman Gobble wrote: >> 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 >> >> 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? > > This patch was incorporated into the openjdk6 port soon after it was > posted. However, I can still reproduce the problem. Using > -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.KqueueSelectorProvider > makes no difference. > >> also looks like New I/O was updated in jdk7... but would have to check it >> out to see if issue still exists.. > > I can't reproduce the problem with the current openjdk7 port. I haven't > tried out Zookeeper though, so YMMV. I would say it's definitely worth > a try though. > > I don't believe anyone is currently working on a fix for the openjdk6 port > for this. I'm going to give zookeeper a try with openjdk7. Thanks! 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"
Can't build x11/rxvt-unicode after r236890
Hi! After r236890 x11/rxvt-unicode is unbuildable: ... c++ -I.. -I. -I. -I./../libev -I./../libptytty/src -I./../libecb -DHAVE_CONFIG_H -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include -O2 -pipe -fno-strict-aliasing -w -I/usr/local/include -D_REENTRANT -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/libpng15 -I/usr/local/include/glib-2.0 -c rxvtc.C PERL="/usr/bin/perl5" /usr/bin/perl5 /usr/local/lib/perl5/5.12.4/ExtUtils/xsubpp -C++ -typemap /usr/local/lib/perl5/5.12.4/ExtUtils/typemap -typemap typemap.iom -typemap typemap -prototypes ./rxvtperl.xs >rxvtperl.C /usr/bin/perl5 -MExtUtils::Embed -e xsinit -- -std urxvt cc -o rxvtc rxvtc.o rxvtdaemon.o fdpass_wrapper.o -lutil -lsupc++ -lm rxvtdaemon.o: In function `rxvt_connection::recv(auto_ptr&, int*)': rxvtdaemon.C:(.text+0x28e): undefined reference to `operator new[](unsigned long)' On r236889 rxvt-unicode builds properly. Full build log from tb: http://levsha.me/tb/errors/10-HEAD.amd64/rxvt-unicode-9.15_1.log -- LEFT-(UANIC|RIPE) JID: lev...@jabber.net.ua PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 ___ 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: FYI: SIGBUS with world built by clang
On Thu, 5 Jul 2012 00:14:14 +0300 Konstantin Belousov wrote: > On Thu, Jul 05, 2012 at 12:32:01AM +0900, Taku YAMAMOTO wrote: > > On Wed, 04 Jul 2012 17:08:30 +0200 > > Dimitry Andric wrote: > > > > > On 2012-07-04 16:33, Taku YAMAMOTO wrote: > > > > For people having SIGBUS with clang-build world + gcc-build binaries, > > > > > > > > > > > > In short words, for any libraries (and never forget about rtld-elf!) > > > > which are potentially called from arbitrary binaries, > > > > compile them with either -mstackrealign or -mstack-alignment=8! > > > > > > > > The detail is as follows. > > > > > > > > I've observed that clang carelessly expects the stack being aligned at > > > > 16 byte boundary. > > > > > > Eh, this is a requirement of the amd64 ABI. Any compiler that *doesn't* > > > align the stack on 16-byte boundaries is basically broken. Or are you > > > experiencing this on i386? Even there, 16-byte alignment would be much > > > better in combination with SSE instructions (which arent' enabled by > > > default, btw). > > > > Oops, I had to be clear about that! > > Yes, the experiment was took on i386 (actually -march=pentium4). > > > > > Note that you would get the same issue with newer versions of gcc, which > > > will also assume this alignment. > > > > Interesting, but the base gcc we currently have won't on i386, I think. > > (I occationally get bitten by similar problem when using -ftree-vectorize) > As far as I understand the rules, $esp % 16 must be zero before call > instruction is executed. I googled and found that it is enforced by MacOS X ABI for IA32 but i386 SysV ABI defines otherwise (8 bytes instead of 16 bytes). > i386 csu explicitely aligns the stack before calling into C land, everything > else should be the C compiler own offence :). Unfortunately it is difficult when we have to deal with binaries produced by random compilers, such as Win32 app via wine, mplayer with win32-codecs, etc. ;) JITs, like Java and mono, also have possibility to become victims if they emit native codes without paying attention to the stack alignment, though I'm not sure. Just my random thoughts, -- -|-__ YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - ___ 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
On Thursday, July 05, 2012 5:20:35 am Kaho Toshikazu wrote: > Hello, > > > Interesting question remains: why it works in the older revision r21? > > I don't know exactly resource management, but ISA_PNP_PROBE() > ignores device.hints if acpi unknown device takes resources. > I think this problem is related to some acpi changes. The system in general in 9.0 and later is more strict about honoring what the BIOS says in terms of allocating resources, so we have to be more correct in probing devices. The only wrinkles so far do in fact seem to stem from the keyboard controller. -- John Baldwin ___ 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: FYI: SIGBUS with world built by clang
On Fri, Jul 06, 2012 at 04:15:18AM +0900, Taku YAMAMOTO wrote: > On Thu, 5 Jul 2012 00:14:14 +0300 > Konstantin Belousov wrote: > > > On Thu, Jul 05, 2012 at 12:32:01AM +0900, Taku YAMAMOTO wrote: > > > On Wed, 04 Jul 2012 17:08:30 +0200 > > > Dimitry Andric wrote: > > > > > > > On 2012-07-04 16:33, Taku YAMAMOTO wrote: > > > > > For people having SIGBUS with clang-build world + gcc-build binaries, > > > > > > > > > > > > > > > In short words, for any libraries (and never forget about rtld-elf!) > > > > > which are potentially called from arbitrary binaries, > > > > > compile them with either -mstackrealign or -mstack-alignment=8! > > > > > > > > > > The detail is as follows. > > > > > > > > > > I've observed that clang carelessly expects the stack being aligned at > > > > > 16 byte boundary. > > > > > > > > Eh, this is a requirement of the amd64 ABI. Any compiler that *doesn't* > > > > align the stack on 16-byte boundaries is basically broken. Or are you > > > > experiencing this on i386? Even there, 16-byte alignment would be much > > > > better in combination with SSE instructions (which arent' enabled by > > > > default, btw). > > > > > > Oops, I had to be clear about that! > > > Yes, the experiment was took on i386 (actually -march=pentium4). > > > > > > > Note that you would get the same issue with newer versions of gcc, which > > > > will also assume this alignment. > > > > > > Interesting, but the base gcc we currently have won't on i386, I think. > > > (I occationally get bitten by similar problem when using -ftree-vectorize) > > As far as I understand the rules, $esp % 16 must be zero before call > > instruction is executed. > > I googled and found that it is enforced by MacOS X ABI for IA32 but > i386 SysV ABI defines otherwise (8 bytes instead of 16 bytes). No, SysV ABI only requires 4-byte alignment for the stack on i386. > > > i386 csu explicitely aligns the stack before calling into C land, everything > > else should be the C compiler own offence :). > > Unfortunately it is difficult when we have to deal with binaries produced by > random compilers, such as Win32 app via wine, mplayer with win32-codecs, etc. > ;) > > JITs, like Java and mono, also have possibility to become victims if they > emit native codes without paying attention to the stack alignment, though > I'm not sure. > > Just my random thoughts, > -- > -|-__ YAMAMOTO, Taku > | __ < > > - A chicken is an egg's way of producing more eggs. - pgpsCHtGwYwhe.pgp Description: PGP signature
Re: side note on the X220 running CURRENT: head phone jack works
On Wed, Jul 4, 2012 at 8:49 PM, Erich Dollansky wrote: > Hi, > > there have been some people here - including me - wondering whether the head > phone jack works. Yes, it does. > > I just have had the chance to connect the head phone jack. It works when vlc > is set to use /dev/dsp1.0. > > Using /dev/dsp0.1 brings sound to the built-in speakers. The "proper" fix is to add the following to /boot/loader.conf: # Out : speaker + headphones hint.hdac.0.cad0.nid25.config="as=1 seq=15" # In : mic + external mic hint.hdac.0.cad0.nid35.config="as=2" hint.hdac.0.cad0.nid27.config="as=2 seq=15" This will make the mic work for headsets that have a mic and will make the headphones DTRT so that audio is sent to the headphones and the speakers are muted when headphones are plugged in. NOTE: This works on the T520, but the X220 seems to be very similar in most every way I have seen. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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 Thursday, July 05, 2012 a las 07:39:18AM -0400, John Baldwin escribió: > On Thursday, July 05, 2012 5:20:35 am Kaho Toshikazu wrote: > > Hello, > > > > > Interesting question remains: why it works in the older revision r21? > > > > I don't know exactly resource management, but ISA_PNP_PROBE() > > ignores device.hints if acpi unknown device takes resources. > > I think this problem is related to some acpi changes. > > The system in general in 9.0 and later is more strict about honoring what the > BIOS says in terms of allocating resources, so we have to be more correct in > probing devices. The only wrinkles so far do in fact seem to stem from the > keyboard controller. > Somehow the system should bring up at least console in- and output; if not you are completely locked out; in my case it was simple, because I was booting fron an USB key and could tailor the USB booted system to bring up interface+DHCP+SSH to login via SSH; but without this you are lost matthias -- Matthias Apitz 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 ___ 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: FYI: SIGBUS with world built by clang
On Thu, 5 Jul 2012 23:11:31 +0300 Konstantin Belousov wrote: > On Fri, Jul 06, 2012 at 04:15:18AM +0900, Taku YAMAMOTO wrote: > > On Thu, 5 Jul 2012 00:14:14 +0300 > > Konstantin Belousov wrote: > > > > > On Thu, Jul 05, 2012 at 12:32:01AM +0900, Taku YAMAMOTO wrote: > > > > On Wed, 04 Jul 2012 17:08:30 +0200 > > > > Dimitry Andric wrote: > > > > > > > > > On 2012-07-04 16:33, Taku YAMAMOTO wrote: > > > > > > For people having SIGBUS with clang-build world + gcc-build > > > > > > binaries, > > > > > > > > > > > > > > > > > > In short words, for any libraries (and never forget about rtld-elf!) > > > > > > which are potentially called from arbitrary binaries, > > > > > > compile them with either -mstackrealign or -mstack-alignment=8! > > > > > > > > > > > > The detail is as follows. > > > > > > > > > > > > I've observed that clang carelessly expects the stack being aligned > > > > > > at > > > > > > 16 byte boundary. > > > > > > > > > > Eh, this is a requirement of the amd64 ABI. Any compiler that > > > > > *doesn't* > > > > > align the stack on 16-byte boundaries is basically broken. Or are you > > > > > experiencing this on i386? Even there, 16-byte alignment would be > > > > > much > > > > > better in combination with SSE instructions (which arent' enabled by > > > > > default, btw). > > > > > > > > Oops, I had to be clear about that! > > > > Yes, the experiment was took on i386 (actually -march=pentium4). > > > > > > > > > Note that you would get the same issue with newer versions of gcc, > > > > > which > > > > > will also assume this alignment. > > > > > > > > Interesting, but the base gcc we currently have won't on i386, I think. > > > > (I occationally get bitten by similar problem when using > > > > -ftree-vectorize) > > > As far as I understand the rules, $esp % 16 must be zero before call > > > instruction is executed. > > > > I googled and found that it is enforced by MacOS X ABI for IA32 but > > i386 SysV ABI defines otherwise (8 bytes instead of 16 bytes). > No, SysV ABI only requires 4-byte alignment for the stack on i386. (snip) Oh, I stand corrected. Thank you :) -- -|-__ YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - ___ 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: 10.0-CURRENT: kernel: Fatal trap 12: page fault while in kernel mode
On Tuesday, July 03, 2012 1:43:30 am O. Hartmann wrote: > The most recent build of FreeBSD 10.0-CURRENT crashes on one of our > boxes with recent Intel hardware, see dmesg extract below. FreeBSD does > obviously only crash on hardware with modern "Sandy-Bridge" hardware, > the very same kernel config and a very similar setup does work very well > on an older Intel Core2Dua architecture. > > Machine in question runs an older kernel (set via nextboot -k > kernel.old) very well: > FreeBSD 10.0-CURRENT #0 r237697: Thu Jun 28 11:45:08 CEST 2012 > > Most recent buildworls/kernels crash after going into multiuser mode > (/etc/rc-scripts getting executed). Below the kernel trap message. > > I do this report on the fly, so if there is need for deeper > investigations let me know, I will provide necessary detail requested. We would need a stack trace to debug this further. Do you have a crashdump? -- John Baldwin ___ 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
On Thursday, July 05, 2012 4:25:21 pm Matthias Apitz wrote: > El día Thursday, July 05, 2012 a las 07:39:18AM -0400, John Baldwin escribió: > > > On Thursday, July 05, 2012 5:20:35 am Kaho Toshikazu wrote: > > > Hello, > > > > > > > Interesting question remains: why it works in the older revision > > > > r21? > > > > > > I don't know exactly resource management, but ISA_PNP_PROBE() > > > ignores device.hints if acpi unknown device takes resources. > > > I think this problem is related to some acpi changes. > > > > The system in general in 9.0 and later is more strict about honoring what > > the > > BIOS says in terms of allocating resources, so we have to be more correct > > in > > probing devices. The only wrinkles so far do in fact seem to stem from the > > keyboard controller. > > > > Somehow the system should bring up at least console in- and output; if > not you are completely locked out; in my case it was simple, because I > was booting fron an USB key and could tailor the USB booted system to > bring up interface+DHCP+SSH to login via SSH; but without this you are > lost So far I can't think of a non-hackish way to special case keyboard and mouse controllers, though I'm close to doing so (i.e. just ignore any device that tries to allocate resources in the "default" range for those devices unless it is a "known" device ID). The patch in this thread should be committed though. -- John Baldwin ___ 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: 10.0-CURRENT: kernel: Fatal trap 12: page fault while in kernel mode
On 07/05/12 23:27, John Baldwin wrote: > On Tuesday, July 03, 2012 1:43:30 am O. Hartmann wrote: >> The most recent build of FreeBSD 10.0-CURRENT crashes on one of our >> boxes with recent Intel hardware, see dmesg extract below. FreeBSD does >> obviously only crash on hardware with modern "Sandy-Bridge" hardware, >> the very same kernel config and a very similar setup does work very well >> on an older Intel Core2Dua architecture. >> >> Machine in question runs an older kernel (set via nextboot -k >> kernel.old) very well: >> FreeBSD 10.0-CURRENT #0 r237697: Thu Jun 28 11:45:08 CEST 2012 >> >> Most recent buildworls/kernels crash after going into multiuser mode >> (/etc/rc-scripts getting executed). Below the kernel trap message. >> >> I do this report on the fly, so if there is need for deeper >> investigations let me know, I will provide necessary detail requested. > > We would need a stack trace to debug this further. Do you have a crashdump? > Well, I built a GENERIC kernel and bootet that, it also crashes, but I didn't find any coredump (as found in the crashes with the custom kernel). I was able to do a backtrace with the GENERIC kernel, but incapable of saving the trace - I did this in a rush, sorry. I went back, just on a hunch, to FreeBSD 10.0-CURRENT #1 r237000, which works, but this isn't the last working revision. I will look tomorrow for how to generate a dump or backtrace and save that somehow (if available in the handbook). Otherwise, if not not much efford, I would appreciate any hint (for the impatient) how to generate suiatbel debug informations. Regards, Oliver signature.asc Description: OpenPGP digital signature
RAM fragmention problems
I am running into a problem with RAM fragmentation causing contigmalloc() failures and wonder if anyone has a tool that that would allow me to identify the owner(s) of pages of RAM within a region on amd64. -- Peter Jeremy pgpJ5bQo0Tiwa.pgp Description: PGP signature
Interfacing devices with multiple parents within newbus
Hi folks,
The problem has been raised in the last BSDCan during a talk, but no
clear answer has been given. Some (pseudo-)devices might require
resources from multiple other (pseudo-)devices.
For example, a device is sitting on an SMBus, but need to access a
software controlled LED, sitting on a GPIO bus, itself sitting on an
LPC bus... Or a variant where everything is controlled on the same
chip, but different GPIO banks. For that specific example, all the
GPIO pin could be implement on the same GPIObus, however, gpiobus(4)
is limited to 32 pins and the chip provides 5 banks of 8 pins, ie. a
total of 40 pins[0]. In the same idea, a device sitting on GPIOs
controlled by two independant chips, say one being an ICH10R chipset
on a PCI device function, and the other being a
SuperIO on an LPC bus.
This situation make me really dubious that FreeBSD will be able to
support configuration such as:
esdhc@50004000 { /* ESDHC1 */
cd-gpios = <&gpio2 13 0>; /* GPIO3_13 */
wp-gpios = <&gpio3 11 0>; /* GPIO4_11 */
status = "okay";
};
or:
ecspi@5001 { /* ECSPI1 */
fsl,spi-num-chipselects = <2>;
cs-gpios = <&gpio1 30 0>, /* GPIO2_30 */
<&gpio2 19 0>; /* GPIO3_19 */
status = "okay";
[...]
This example is taken from Linux' `arch/arm/boot/dts/imx53-smd.dts'.
Here, SDHC or SPI controller are using different GPIO devices. Note
that these GPIO pins does not seem to be multi-function pins as
another .dts defines ESDHC1 as:
esdhc@50004000 { /* ESDHC1 */
cd-gpios = <&gpio2 13 0>; /* GPIO3_13 */
wp-gpios = <&gpio2 14 0>; /* GPIO3_14 */
status = "okay";
};
AFAIK, newbus is unable to model any of the above situation without
being bypassed one way or another.
any hints ?
Thanks,
- Arnaud
[0]: as a matter of comparison, old PXA27x have up to 121 GPIOs
___
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: panic after starting X with r238120
On 07/05/12 03:00, Alan Cox wrote: > On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills wrote: > >> Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set >> it to 1 for some reason that I can't recall. >> >> > That shouldn't cause a crash in pmap_enter(). What is line 3587 of pmap.c > in your sources? 3587 if ((newpte & PG_RW) == 0) > You mentioned DRM. Are you using the new Intel graphics > driver? > No, I'm using ATI Radeon. Steve ___ 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
Hello John Baldwin, and all, John Baldwin wrote: > The system in general in 9.0 and later is more strict about honoring what the > BIOS says in terms of allocating resources, so we have to be more correct in > probing devices. The only wrinkles so far do in fact seem to stem from the > keyboard controller. I don't have any plans for treating unknown ID device's resources. Many keyboard PNP ID are listed on a file at the below URL, and FreeBSD doesn't know almost of them. http://download.microsoft.com/download/5/7/7/577a5684-8a83-43ae-9272-ff260a9c20e2/pnp_legacy.doc -- k...@elam.kais.kyoto-u.ac.jp ___ 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: Interfacing devices with multiple parents within newbus
On Jul 5, 2012, at 5:14 PM, Arnaud Lacombe wrote:
> Hi folks,
>
> The problem has been raised in the last BSDCan during a talk, but no
> clear answer has been given. Some (pseudo-)devices might require
> resources from multiple other (pseudo-)devices.
>
> For example, a device is sitting on an SMBus, but need to access a
> software controlled LED, sitting on a GPIO bus, itself sitting on an
> LPC bus... Or a variant where everything is controlled on the same
> chip, but different GPIO banks. For that specific example, all the
> GPIO pin could be implement on the same GPIObus, however, gpiobus(4)
> is limited to 32 pins and the chip provides 5 banks of 8 pins, ie. a
> total of 40 pins[0]. In the same idea, a device sitting on GPIOs
> controlled by two independant chips, say one being an ICH10R chipset
> on a PCI device function, and the other being a
> SuperIO on an LPC bus.
>
> This situation make me really dubious that FreeBSD will be able to
> support configuration such as:
>
> esdhc@50004000 { /* ESDHC1 */
>cd-gpios = <&gpio2 13 0>; /* GPIO3_13 */
>wp-gpios = <&gpio3 11 0>; /* GPIO4_11 */
>status = "okay";
> };
>
> or:
>
> ecspi@5001 { /* ECSPI1 */
>fsl,spi-num-chipselects = <2>;
>cs-gpios = <&gpio1 30 0>, /* GPIO2_30 */
> <&gpio2 19 0>; /* GPIO3_19 */
>status = "okay";
> [...]
>
> This example is taken from Linux' `arch/arm/boot/dts/imx53-smd.dts'.
> Here, SDHC or SPI controller are using different GPIO devices. Note
> that these GPIO pins does not seem to be multi-function pins as
> another .dts defines ESDHC1 as:
>
> esdhc@50004000 { /* ESDHC1 */
>cd-gpios = <&gpio2 13 0>; /* GPIO3_13 */
>wp-gpios = <&gpio2 14 0>; /* GPIO3_14 */
>status = "okay";
> };
>
> AFAIK, newbus is unable to model any of the above situation without
> being bypassed one way or another.
>
> any hints ?
That's not correct. You don't need a parent-child relationship in newbus to
interact with another node in the tree. You can look up the other node by
name, and then call functions based on finding that other device.
Warner
___
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 Thursday, July 05, 2012 a las 05:22:22PM -0400, John Baldwin escribió: > So far I can't think of a non-hackish way to special case keyboard and > mouse controllers, though I'm close to doing so (i.e. just ignore any > device that tries to allocate resources in the "default" range for those > devices unless it is a "known" device ID). > > The patch in this thread should be committed though. And one should close this issue with this: http://www.freebsd.org/cgi/query-pr.cgi?pr=169571 thx for all your helping hands 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 ___ 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"
