Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Thursday, July 05, 2012 a las 07:28:33AM +0200, Matthias Apitz escribió:
> 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 }
--
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: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Wednesday, July 04, 2012 a las 07:33:08PM +0900, Kaho Toshikazu escribió:
> Hello,
>
> Can you put the file "acpidump-r21.txt" on the Internet?
> When you run `grep "Device" /tmp/acpidump-r21.txt`
> to get device list, can you find "PS2K" or "KBC" or similar word?
Hello,
For some unknown reason today it gives more lines:
# acpidump -dt | wc -l
acpidump: RSDT entry 2 (sig OEMB) is corrupt
3815
when I did this the other day it was only around 2000 lines;
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
Thanks for your help
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"
Re: Why NOT using FreeBSD? Re: ports/169581: editors/libreoffice:
Baptiste Daroussin wrote .. > 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 LibreOffice is pretty massive. I've spent much of the day working on building 3.6.0.0 on 10-CURRENT with gcc48 and openjdk6. I have been using AbiWord but the word-wrap is crazy. Try writing a novel with weird word breaks and moving paragraphs and it's driving me koo-koo pants. Also it does not appear to do right-left opposing margins. I was interested in building AbiWord dev on my machine but the dev team seems very MS-centric, much of a chore using their HEAD. Gnumeric works great, I have successfully interoperated, no urgent issues. on to LibreOffice... 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. At the moment, there is one small change to configure.in. It stubbornly demands libclucene-core instead of libclucene. Most of the libraries are built from ports, then using --with-system-foo in autogen.sh -- Waitman Gobble San Jose California USA -- 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"
side note on the X220 running CURRENT: head phone jack works
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. Erich ___ 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/04/2012 15:02, Pedro Giffuni wrote: > The thing, as I see it, is that people have to understand > this is a volunteer project and if people don't do things > by themselves they really can't demand someone else to > do it for them. Of course. But that's totally different from, "I don't use FreeBSD because it doesn't offer $feature, which is important to me." Don't forget the original purpose of this thread. :) -- This .signature sanitized for your protection ___ 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:
Just IMHO; --- Mer 4/7/12, Doug Barton ha scritto: ... > >> > >> 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". > > > > sure libreoffice is so easy to port... > > > > /me officially gives up with that libreoffice port, > > open for new volunteers > > If you don't have time to work on the port, then don't, > that's not a problem. But throwing a hissy fit here > doesn't help at all. Even on paid jobs, people always have the right to quit. The thing, as I see it, is that people have to understand this is a volunteer project and if people don't do things by themselves they really can't demand someone else to do it for them. > It's a plain fact that a working office suite is a basic > requirement for most desktop users. If _we_ can't provide > that (note, not you, personally, we, as a > project), it's a valid reason for users to avoid FreeBSD for > desktop use. > The system is as strong as it's weakest link. There are perfectly good office suites for FreeBSD and even then for some of us that is not enough to use FreeBSD (or linux) as a desktop. > If we're ever going to make progress in this area we > have to be willing to examine and absorb facts; and > then act accordingly. > If people think a particular office suite is critical then *they* have to spend time on it. If no one has the time or skills then maybe it's not that important at all. Pedro. ___ 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
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. Steve On Jul 4, 2012, at 5:41 PM, Steve Wills wrote: > Hi, > > After updating to r238120, I get a panic whenever X starts up. It works for a > few seconds, then panics. The messages don't look too useful to me, but here > they are: > > Unread portion of the kernel message buffer: > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 3610 (kdm_greet) > trap number = 12 > panic: page fault > cpuid = 0 > > (kgdb) bt > #0 doadump (textdump=dwarf2_read_address: Corrupted DWARF expression. > ) at pcpu.h:224 > #1 0x8087ef79 in kern_reboot (howto=dwarf2_read_address: Corrupted > DWARF expression. > ) at kern_shutdown.c:449 > #2 0x8087f413 in panic (fmt=dwarf2_read_address: Corrupted DWARF > expression. > ) at kern_shutdown.c:637 > #3 0x80b77d08 in trap_fatal (frame=dwarf2_read_address: Corrupted > DWARF expression. > ) at trap.c:852 > #4 0x80b78012 in trap_pfault (frame=dwarf2_read_address: Corrupted > DWARF expression. > ) at trap.c:678 > #5 0x80b777aa in trap (frame=Variable "frame" is not available. > ) at trap.c:456 > #6 0x80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179 > #7 0x80b6f6b0 in pmap_enter (pmap=dwarf2_read_address: Corrupted > DWARF expression. > ) at pmap.c:3587 > #8 0x80adafa0 in vm_fault_hold (map=dwarf2_read_address: Corrupted > DWARF expression. > ) at vm_fault.c:935 > #9 0x80ad9787 in vm_fault (map=Variable "map" is not available. > ) at vm_fault.c:229 > #10 0x80b77f26 in trap_pfault (frame=dwarf2_read_address: Corrupted > DWARF expression. > ) at trap.c:736 > #11 0x80b77670 in trap (frame=Variable "frame" is not available. > ) at trap.c:358 > #12 0x80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179 > #13 0x0008040d7796 in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal > (kgdb) > > Something I saw in a previous panic made me think this was drm related, but I > don't see it in this particular one. > > 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" ___ 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"
panic after starting X with r238120
Hi, After updating to r238120, I get a panic whenever X starts up. It works for a few seconds, then panics. The messages don't look too useful to me, but here they are: Unread portion of the kernel message buffer: processor eflags= interrupt enabled, resume, IOPL = 0 current process = 3610 (kdm_greet) trap number = 12 panic: page fault cpuid = 0 (kgdb) bt #0 doadump (textdump=dwarf2_read_address: Corrupted DWARF expression. ) at pcpu.h:224 #1 0x8087ef79 in kern_reboot (howto=dwarf2_read_address: Corrupted DWARF expression. ) at kern_shutdown.c:449 #2 0x8087f413 in panic (fmt=dwarf2_read_address: Corrupted DWARF expression. ) at kern_shutdown.c:637 #3 0x80b77d08 in trap_fatal (frame=dwarf2_read_address: Corrupted DWARF expression. ) at trap.c:852 #4 0x80b78012 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression. ) at trap.c:678 #5 0x80b777aa in trap (frame=Variable "frame" is not available. ) at trap.c:456 #6 0x80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179 #7 0x80b6f6b0 in pmap_enter (pmap=dwarf2_read_address: Corrupted DWARF expression. ) at pmap.c:3587 #8 0x80adafa0 in vm_fault_hold (map=dwarf2_read_address: Corrupted DWARF expression. ) at vm_fault.c:935 #9 0x80ad9787 in vm_fault (map=Variable "map" is not available. ) at vm_fault.c:229 #10 0x80b77f26 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression. ) at trap.c:736 #11 0x80b77670 in trap (frame=Variable "frame" is not available. ) at trap.c:358 #12 0x80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179 #13 0x0008040d7796 in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) Something I saw in a previous panic made me think this was drm related, but I don't see it in this particular one. 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: Why NOT using FreeBSD? Re: ports/169581: editors/libreoffice:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/03/2012 11:34, Baptiste Daroussin wrote: > 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". > > sure libreoffice is so easy to port... > > /me officially gives up with that libreoffice port, open for new volunteers If you don't have time to work on the port, then don't, that's not a problem. But throwing a hissy fit here doesn't help at all. It's a plain fact that a working office suite is a basic requirement for most desktop users. If _we_ can't provide that (note, not you, personally, we, as a project), it's a valid reason for users to avoid FreeBSD for desktop use. If we're ever going to make progress in this area we have to be willing to examine and absorb facts; and then act accordingly. Doug - -- This .signature sanitized for your protection -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJP9LQnAAoJEFzGhvEaGryEYk4H/0TcxjVnax0xgrt4/3WMvwWU t/GNQ7Fws3EJSrZN2vB3LSnmwRv7UbkmotXLzirS+f/SmwREUH0677DV3EFlxuxx WvXvtYexu4XHWOeODZi5m8crbNUM94HLnwTfo2gecMah+eL6M46EoBAfCJT4NtUD 1AYIsZTpiEqEvLHJCNj+Mwt0YiH3XxAdRhhfSMolKBm7B6lqOsEA5cEnA2QTWBWI bDeUB8hZuW1q6O5U60xdTZMjDQNGroVg6nuCtTihXj7/DWKR41Wgzezh14qFKs7m Hki/eRGzQA3DTLKuf51PY+FO7epBeWC5YCNxe52ASqU+pKdUYpfS3vCw3BmbqPg= =4Mp6 -END PGP SIGNATURE- ___ 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, 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. i386 csu explicitely aligns the stack before calling into C land, everything else should be the C compiler own offence :). pgpQz9OvfgAr6.pgp Description: PGP signature
Re: Java and NIO?
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. -- Greg Lewis Email : gle...@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : gle...@freebsd.org ___ 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: MPSAFE VFS -- List of upcoming actions
2012/6/29 Attilio Rao : > As already published several times, according to the following plan: > http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS > I still haven't heard from Vivien or Edward, anyway as NTFS is basically only used RO these days (also the mount_ntfs code just permits RO mounting) I stripped all the uncomplete/bogus write support with the following patch: http://www.freebsd.org/~attilio/ntfs_remove_write.patch This is an attempt to make the code smaller and possibly just focus on the locking that really matter (as read-only filesystem). On some points of the patch I'm a bit less sure as we could easily take into account also write for things like vaccess() arguments, and make easier to re-add correct write support at some point in the future, but still force RO, even if the approach used in the patch is more correct IMHO. As an added bonus this patch cleans some dirty code in the mount operation and fixes a bug as vfs_mountedfrom() is called before real mounting is completed and can still fail. The patch has been kindly tested by pho@. If none has objections I will commit it friday evening. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein ___ 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 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) -- -|-__ 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: FYI: SIGBUS with world built by clang
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). Note that you would get the same issue with newer versions of gcc, which will also assume this alignment. ___ 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"
FYI: SIGBUS with world built by clang
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.
For example, the following code:
#include
#include
int
foo(const char *format,...)
{
int ret;
va_list ap;
FILE f = {};
va_start(ap, format);
ret = vfprintf(&f, format, ap);
va_end(ap);
return ret;
}
which turns into:
pushl %ebp
movl%esp, %ebp
subl$264, %esp # imm = 0x108
xorps %xmm0, %xmm0
movaps %xmm0, -40(%ebp)
movaps %xmm0, -56(%ebp)
(snip; lots of movaps insns follows)
which results in SIGBUS if %esp - 4 is not at 16 byte boundary.
(Note: movaps expects the address aligned to 16 bytes!)
This problem becomes visible when such functions get called from binaries
compiled with other compilers which don't care about stack alignment.
If the above code is compiled by clang with -mstackrealign:
pushl %ebp
movl%esp, %ebp
andl$-16, %esp
subl$272, %esp # imm = 0x110
xorps %xmm0, %xmm0
movaps %xmm0, 224(%esp)
movaps %xmm0, 208(%esp)
(snip; lots of movaps insns follows)
it tries to align the stack prior to allocating local variables thus no
problem.
If the above code is compiled by clang with -mstack-alignment=8:
pushl %ebp
movl%esp, %ebp
pushl %esi
subl$252, %esp
leal-240(%ebp), %esi
movl%esi, (%esp)
movl$232, 8(%esp)
movl$0, 4(%esp)
calll memset
(snip)
it calls memset instead of a bunch of movaps to clear the storage thus no
problem, of course.
# I don't know why clang doesn't utilize rep stosl, though.
Pros and cons:
-mstackrealign
Pros: no function calls to memset
probably faster because of SSE
Cons: use of SSE means the need of saving FP registers
potentially more stack consumption
-mstack-alignment=#
Pros: normal and predictive stack consumption
don't spill SSE registers; no extra overhead on context switching
Cons: depends on memset
--
-|-__ 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"
sk0 link bouncing
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? Thanx, --WjW dmesg: Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #1: Sat Jun 30 09:35:43 UTC 2012 r...@freetest.digiware.nl:/usr/obj/usr/src/sys/GENERIC amd64 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz (2533.48-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x10676 Family = 6 Model = 17 Stepping = 6 Features=0xbfebfbff Features2=0x8e39d AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 6442450944 (6144 MB) avail memory = 6167552000 (5881 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, dff0 (3) failed cpu0: on acpi0 cpu1: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 uhci0: port 0xb800-0xb81f irq 16 at device 26.0 on pci0 uhci0: LegSup = 0x2f00 usbus0 on uhci0 uhci1: port 0xb880-0xb89f irq 21 at device 26.1 on pci0 uhci1: LegSup = 0x2f00 usbus1 on uhci1 uhci2: port 0xbc00-0xbc1f irq 18 at device 26.2 on pci0 uhci2: LegSup = 0x2f00 usbus2 on uhci2 ehci0: mem 0xfe8ffc00-0xfe8f irq 18 at device 26.7 on pci0 usbus3: EHCI version 1.0 usbus3 on ehci0 hdac0: mem 0xfe8f8000-0xfe8fbfff irq 22 at device 27.0 on pci0 pcib1: irq 17 at device 28.0 on pci0 pci3: on pcib1 pcib2: irq 17 at device 28.4 on pci0 pci2: on pcib2 atapci0: port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem 0xfeaffc00-0xfeaf irq 16 at device 0.0 on pci2 ahci0: at channel -1 on atapci0 ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ata2: at channel 0 on atapci0 pcib3: irq 16 at device 28.5 on pci0 pci1: on pcib3 mskc0: port 0xc800-0xc8ff mem 0xfe9fc000-0xfe9f irq 17 at device 0.0 on pci1 msk0: on mskc0 msk0: Ethernet address: 00:22:15:46:17:9a miibus0: on msk0 e1000phy0: PHY 0 on miibus0 e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow uhci3: port 0xb080-0xb09f irq 23 at device 29.0 on pci0 uhci3: LegSup = 0x2f00 usbus4 on uhci3 uhci4: port 0xb400-0xb41f irq 19 at device 29.1 on pci0 uhci4: LegSup = 0x2f00 usbus5 on uhci4 uh
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello, Can you put the file "acpidump-r21.txt" on the Internet? When you run `grep "Device" /tmp/acpidump-r21.txt` to get device list, can you find "PS2K" or "KBC" or similar word? Matthias Apitz wrote: > 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 ___ 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"
[panic] currnet(r238089) cause panic when using '/usr/sbin/amd'
Hi all, I try to update newest current (r238089). I have kernel panic when using '/usr/sbin/amd'. This kernel panic is not caused without using '/usr/sbin/amd'. In old current (r236371), I have no problem with using '/usr/sbin/amd'. Currently, I don't know how to fix it. So I can only report this proble to ML. Thanks, How to repeat: 1) "svn checkout" r238089 source code 2) "make buildworld" and "make buildkernel" 3) "make installworld" and "make installkernel" 4) reboot 5) boot "GENERIC" kernel 6) run amd, "/etc/rc.d/amd onestart" My environment: - version is 10-current # uname -a FreeBSD venus.tokyo.iiji.jp 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r238089M: Wed Jul 4 10:30:01 JST 2012 r...@venus.tokyo.iiji.jp:/usr/obj/usr/src/sys/GENERIC amd64 - build by r238039 source code - using GENERIC kernel - load kernel modules are # kldstat Id Refs AddressSize Name 1 19 0x8020 15d3ad0 kernel 21 0x817d4000 22b260 zfs.ko 32 0x81a0 8570 opensolaris.ko 41 0x81c12000 38fc ums.ko 51 0x81c16000 1b7a1ng_btsocket.ko 61 0x81c32000 ba58 netgraph.ko 71 0x81c3e000 118b ng_bluetooth.ko --- YAMAMOTO Shigeru ___ 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"
