Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
I can reproduce it on a clean 11.0-BETA1 VM. 2016-07-09 9:03 GMT+08:00 Huang Wen Hui : > For some reasons, r302324 seems not include in 11.0-ALPHA6? > > 2016-07-09 8:52 GMT+08:00 Huang Wen Hui : > >> Revert back r302324, Chinese locale problem is gone. >> >> Cheers >> Huang Wen Hui >> >> 2016-07-05 16:50 GMT+08:00 Baptiste Daroussin : >> >>> On Tue, Jul 05, 2016 at 12:16:42PM +0800, Huang Wen Hui wrote: >>> > These 2 files can make ls suck: >>> > >>> > touch 火灾1 >>> > touch 火灾2 >>> > >>> > 2 files start with 2 same Chinese chars. >>> > >>> I cannot reproduce on my head laptop, neither on a clean 11.0-ALPHA6 >>> jail. >>> >>> I'll try on a clean 11.0-ALPHA6 VM >>> >>> Best regards, >>> Bapt >>> >> >> > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
For some reasons, r302324 seems not include in 11.0-ALPHA6? 2016-07-09 8:52 GMT+08:00 Huang Wen Hui : > Revert back r302324, Chinese locale problem is gone. > > Cheers > Huang Wen Hui > > 2016-07-05 16:50 GMT+08:00 Baptiste Daroussin : > >> On Tue, Jul 05, 2016 at 12:16:42PM +0800, Huang Wen Hui wrote: >> > These 2 files can make ls suck: >> > >> > touch 火灾1 >> > touch 火灾2 >> > >> > 2 files start with 2 same Chinese chars. >> > >> I cannot reproduce on my head laptop, neither on a clean 11.0-ALPHA6 jail. >> >> I'll try on a clean 11.0-ALPHA6 VM >> >> Best regards, >> Bapt >> > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
Revert back r302324, Chinese locale problem is gone. Cheers Huang Wen Hui 2016-07-05 16:50 GMT+08:00 Baptiste Daroussin : > On Tue, Jul 05, 2016 at 12:16:42PM +0800, Huang Wen Hui wrote: > > These 2 files can make ls suck: > > > > touch 火灾1 > > touch 火灾2 > > > > 2 files start with 2 same Chinese chars. > > > I cannot reproduce on my head laptop, neither on a clean 11.0-ALPHA6 jail. > > I'll try on a clean 11.0-ALPHA6 VM > > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
These 2 files can make ls suck: touch 火灾1 touch 火灾2 2 files start with 2 same Chinese chars. % lldb /bin/ls (lldb) target create "/bin/ls" Current executable set to '/bin/ls' (x86_64). (lldb) run Process 2185 launching Process 2185 launched: '/bin/ls' (x86_64) Enter Control+C: libc.so.7 was compiled with optimization - stepping may behave oddly; variables may not be available. Process 2185 stopped * thread #1: tid = 100261, 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276, stop reason = signal SIGSTOP frame #0: 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276 [opt] 273 next = (low + high) / 2; 274 p = tab + next; 275 compar = key - p->val; -> 276 if (compar == 0) 277 return (p); 278 if (compar > 0) 279 low = next + 1; (lldb) bt * thread #1: tid = 100261, 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276, stop reason = signal SIGSTOP * frame #0: 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276 [opt] frame #1: 0x000800ff5a81 libc.so.7`_collate_lookup(table=, t=, len=, pri=, which=, state=) + 465 at collate.c:343 [opt] frame #2: 0x000800fd80a9 libc.so.7`wcscoll_l(ws1=, ws2=, locale=) + 985 at wcscoll.c:171 [opt] frame #3: 0x000800fd4d19 libc.so.7`strcoll_l(s="火灾1", s2="火灾2", locale=0x00080124a338) + 393 at strcoll.c:101 [opt] frame #4: 0x000800fe9313 libc.so.7`qsort(a=, n=, es=, cmp=(libc.so.7`fts_compar at fts.c:966)) + 13763 at qsort.c:130 [opt] frame #5: 0x000800f25297 libc.so.7`fts_sort(sp=, head=, nitems=) + 135 at fts.c:995 [opt] frame #6: 0x000800f2638e libc.so.7`fts_children(sp=, instr=2) + 254 at fts.c:570 [opt] frame #7: 0x004030df ls`traverse(argc=, argv=, options=) + 463 at ls.c:576 [opt] frame #8: 0x00402eeb ls`main(argc=, argv=) + 2299 at ls.c:498 [opt] frame #9: 0x004020cf ls`_start + 383 2016-07-04 15:04 GMT+08:00 Baptiste Daroussin : > On Mon, Jul 04, 2016 at 02:51:46PM +0800, Huang Wen Hui wrote: > > 2016-07-04 14:41 GMT+08:00 Baptiste Daroussin : > > > > > On Mon, Jul 04, 2016 at 02:36:11PM +0800, Huang Wen Hui wrote: > > > > 2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > > > > > > > > > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > > > > > Hi, > > > > > > On very recent CURRENT, ls can eat high CPU time when > > > LANG=zh_CN.UTF-8 > > > > > and > > > > > > LC_ALL=zh_CN.UTF-8: > > > > > > > > > > > > % uname -a > > > > > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 > > > r302331M: > > > > > Mon > > > > > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > > > > > /usr/obj/usr/src/sys/MACBOOK > > > > > > amd64 > > > > > > > > > > > > top show: > > > > > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 > 98.86% > > > ls > > > > > > > > > > > > any ideas? > > > > > > > > > > > Is it in all directories or only in directories with files in > chinese > > > > > characters? > > > > > > > > > Yes, the directory contain Chinese characters. > > > > > > > > > > > > > > Is it only happening when you run ls with some arguments (in > particular > > > > > -l) or > > > > > with any arguments? > > > > > > > > > I use ls -wGl > > > > > > > > > > > > > > Do you see the same if you force any other locale like en_US.UTF-8? > > > > > > > > > There is no problem if set en_US.UTF-8. > > > > > > > > > > > > > Best regards, > > > > > Bapt > > > > > > > > > > > Can you try: > > > env -i LANG=zh_CN.UTF-8 LC_COLLATE=C ls -l > > > > > > And tell me if it still happen? > > > > > No problem with this command. > > > > Ok so there might be an very inefficient code in the new chinese collation > code > I will look into it thanks a lot for reporting. > > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
2016-07-04 14:41 GMT+08:00 Baptiste Daroussin : > On Mon, Jul 04, 2016 at 02:36:11PM +0800, Huang Wen Hui wrote: > > 2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > > > > > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > > > Hi, > > > > On very recent CURRENT, ls can eat high CPU time when > LANG=zh_CN.UTF-8 > > > and > > > > LC_ALL=zh_CN.UTF-8: > > > > > > > > % uname -a > > > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 > r302331M: > > > Mon > > > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > > > /usr/obj/usr/src/sys/MACBOOK > > > > amd64 > > > > > > > > top show: > > > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% > ls > > > > > > > > any ideas? > > > > > > > Is it in all directories or only in directories with files in chinese > > > characters? > > > > > Yes, the directory contain Chinese characters. > > > > > > > > Is it only happening when you run ls with some arguments (in particular > > > -l) or > > > with any arguments? > > > > > I use ls -wGl > > > > > > > > Do you see the same if you force any other locale like en_US.UTF-8? > > > > > There is no problem if set en_US.UTF-8. > > > > > > > Best regards, > > > Bapt > > > > > Can you try: > env -i LANG=zh_CN.UTF-8 LC_COLLATE=C ls -l > > And tell me if it still happen? > No problem with this command. > > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > Hi, > > On very recent CURRENT, ls can eat high CPU time when LANG=zh_CN.UTF-8 > and > > LC_ALL=zh_CN.UTF-8: > > > > % uname -a > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 r302331M: > Mon > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > /usr/obj/usr/src/sys/MACBOOK > > amd64 > > > > top show: > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% ls > > > > any ideas? > > > Is it in all directories or only in directories with files in chinese > characters? > Yes, the directory contain Chinese characters. > > Is it only happening when you run ls with some arguments (in particular > -l) or > with any arguments? > I use ls -wGl > > Do you see the same if you force any other locale like en_US.UTF-8? > There is no problem if set en_US.UTF-8. > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
Hi, On very recent CURRENT, ls can eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8: % uname -a FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 r302331M: Mon Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn:/usr/obj/usr/src/sys/MACBOOK amd64 top show: 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% ls any ideas? Huang Wen Hui ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: uefi boot on Apple Mac
I finally make MacBookPro 11,3 UEFI boot successfully: 1. copy boot1.efi to /EFI/boot/BOOTx64.efi in EFI partition 2. Create a small UFS partition in internal SSD, and installworld and installkernel. 3. Without USB stick, then system really can boot, although the loader still stop at: Start @ 0x802d9000... 4. I can ssh log in and found that culprit is XHCI USB controller does not work in UEFI mode. 5. Xorg and nvidia driver also works. 6. verbose boot log can be found at: http://sw.gddsn.org.cn/freebsd/uefi-messages.txt Cheers, Huang Wen Hui 2014-08-10 16:44 GMT+08:00 Anders Bolt Evensen : > If you're interested, you can try out the following ISO: > https://www.dropbox.com/s/srbunx0agrokcs3/freebsd- > current-uefi-bios-amd64.iso > > The image was built on Friday 8th of August for the amd64 platform. > > I tested out the EFI part on VirtualBox (UEFI 2.X) and my MacBook Pro 17 > inch from 2011 (EFI 1.10), and as far as EFI goes, I successfully booted > the image on both my Mac and VirtualBox (however, booting the image from > BIOS using my Mac was a different story). > > So, as I said, as far as (U)EFI goes, the image should work on UEFI 2.X > based PC's and EFI 1.10 based Macs. > > On 12/07/14 19:22, Nathan Whitehorn wrote: > >> I'd point out that, as of last week, the standard -CURRENT ISOs (and >> generate-release.sh script) make EFI-bootable media by default. All the >> snapshots should have this done already, for instance. >> -Nathan >> > I wasn't aware of that, but thanks for the info. :) > > >> On 07/12/14 03:09, Anders Bolt-Evensen wrote: >> >>> I also got a message like that when I booted from a USB stick on a >>> MacBookPro8,3 (17 inch, late 2011). >>> >>> I fixed it by creating a custom ISO image and burned that onto a DVD >>> using an external DVD drive. >>> The UEFI installer boots fine from this external DVD drive. >>> >>> Here is how I did it: >>> >>> Genereste an ISO with the FreeBSD-CURRENT kernel, mount the ISO and copy >>> all files from the root directory in the ISO and unmount >>> > cd /usr/src/release >>> > sh ./generate-release.sh # You may have to run “make buildworld” >>> and be connected to the internet to install required ports. >>> > mount -t cd9660 /scratch/R/release/FreeBSD-something-disc1.iso >>> /mnt >>> > mkdir freebsd_generic_installer >>> #Files copied to the directory in the next command will be copied to >>> a new ISO in step 3 >>> > cp -R /mnt/ freebsd_generic_installer/ >>> > umount /mnt >>> 2. Create a FAT filesystem image and place the loader in it in the >>> default path that UEFI will look for (the following steps are copied from >>> https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI): >>> > dd if=/dev/zero of=efiboot.img bs=4k count=100 >>> > mdconfig -a -t vnode -f efiboot.img >>> > newfs_msdos -F 12 -m 0xf8 /dev/md0 >>> > mount -t msdosfs /dev/md0 /mnt >>> > mkdir -p /mnt/efi/boot >>> > cp loader.efi /mnt/efi/boot/bootx64.efi >>> > umount /mnt >>> > mdconfig -d -u 0 >>> >>> 3. Create the custom ISO image. Please make sure that the entry in >>> freebsd_generic_installer/etc/fstab matches the label you choose in the >>> command below. >>> > makefs -t cd9660 -o bootimage='i386;efiboot.img' -o no-emul-boot >>> -o rockridge -o label=“FREEBSD_UEFI_INSTALL" -o publisher="test" >>> uefi-test.iso freebsd_generic_installer/ >>> >>> To get the example in the command above to work, please make sure that >>> the entry in freebsd_generic_installer/etc/fstab reads >>> "/dev/iso9660/FREEBSD_UEFI_INSTALL/cd9660ro0 0" >>> >>> 4. Burn the image to DVD, reboot your system and choose “EFI Boot”. Note >>> that unless you are using a EFI console like rEFIt or rEFInd, you may have >>> to kind of wait a couple of minutes while the kernel is loading before >>> anything appears on the screen. >>> >>> >>> On 04/07/14 16:34, Huang Wen Hui wrote: >>> >>>> Hi, >>>> On my MacbookPro11,3, I got this error message: >>>> >>>> http://sw.gddsn.org.cn/freebsd/uefi.jpg >>>> >>>> cheers, >>>> >>>> Huang WenHui >>>> >>>> 2014-07-04 22:13 GMT+08:00 Ed Maste : >>>> >>>> On 24 May 2014 19:39, Rafael Espíndola >
Re: UEFI display frozen on Retina MacBook Pro
Hi, 2014-09-06 1:20 GMT+08:00 John Nielsen : > I have a "MacBook Pro Retina, Mid 2012" (MacBookPro10,1) on which I'd like > to be able to boot FreeBSD from an external USB drive. For testing I've > been using the mini-memstick images from the -CURRENT snapshots, most > recently the one from 20140903. > This IMAC model can UEFI boot when I tried before. I install rEFInd( http://www.rodsbooks.com/refind/) as boot manager, You can see FreeBSD boot information under rEFInd. Cheers, Huang Wen Hui > I am able to select "EFI Boot" on the USB device from the Mac's boot menu, > and it does _something_, but the screen never changes--the image of the > boot menu is displayed indefinitely. I think it is actually booting since > there is drive activity and the caps lock key indicator starts working a > few seconds in, but the screen just stays the same. Thinking the resolution > of the Retina display may have been an issue, I tried booting with it > disabled (lid closed) and an external monitor and keyboard. The result was > the same--Mac boot menu frozen on the external display. > > Is there anything I should try to troubleshoot or debug this issue? > Anything else I should include in a PR? I can test patches if needed > (probably after building an image including the patch from a VM). > > Thanks, > > JN > > ___ > 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"
Re: uefi boot on Apple Mac
As loader.efi and kernel not change at all from USB to CD, I am confuse why you can boot from CD. Anyway, I try to boot from CD as you suggest, but I got the same result as before:( 2014-07-12 18:09 GMT+08:00 Anders Bolt-Evensen : > I also got a message like that when I booted from a USB stick on a > MacBookPro8,3 (17 inch, late 2011). > > I fixed it by creating a custom ISO image and burned that onto a DVD using > an external DVD drive. > The UEFI installer boots fine from this external DVD drive. > > Here is how I did it: > > Genereste an ISO with the FreeBSD-CURRENT kernel, mount the ISO and copy > all files from the root directory in the ISO and unmount > > cd /usr/src/release > > sh ./generate-release.sh # You may have to run “make buildworld” and > be connected to the internet to install required ports. > > mount -t cd9660 /scratch/R/release/FreeBSD-something-disc1.iso /mnt > > mkdir freebsd_generic_installer > #Files copied to the directory in the next command will be copied to a > new ISO in step 3 > > cp -R /mnt/ freebsd_generic_installer/ > > umount /mnt > 2. Create a FAT filesystem image and place the loader in it in the default > path that UEFI will look for (the following steps are copied from > https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI): > > dd if=/dev/zero of=efiboot.img bs=4k count=100 > > mdconfig -a -t vnode -f efiboot.img > > newfs_msdos -F 12 -m 0xf8 /dev/md0 > > mount -t msdosfs /dev/md0 /mnt > > mkdir -p /mnt/efi/boot > > cp loader.efi /mnt/efi/boot/bootx64.efi > > umount /mnt > > mdconfig -d -u 0 > > 3. Create the custom ISO image. Please make sure that the entry in > freebsd_generic_installer/etc/fstab matches the label you choose in the > command below. > > makefs -t cd9660 -o bootimage='i386;efiboot.img' -o no-emul-boot -o > rockridge -o label=“FREEBSD_UEFI_INSTALL" -o publisher="test" uefi-test.iso > freebsd_generic_installer/ > > To get the example in the command above to work, please make sure that the > entry in freebsd_generic_installer/etc/fstab reads > "/dev/iso9660/FREEBSD_UEFI_INSTALL/cd9660ro0 0" > > 4. Burn the image to DVD, reboot your system and choose “EFI Boot”. Note > that unless you are using a EFI console like rEFIt or rEFInd, you may have > to kind of wait a couple of minutes while the kernel is loading before > anything appears on the screen. > > > > On 04/07/14 16:34, Huang Wen Hui wrote: > >> Hi, >> On my MacbookPro11,3, I got this error message: >> >> http://sw.gddsn.org.cn/freebsd/uefi.jpg >> >> cheers, >> >> Huang WenHui >> >> 2014-07-04 22:13 GMT+08:00 Ed Maste : >> >> On 24 May 2014 19:39, Rafael Espíndola >>> wrote: >>> >>>> Yes, I got that in the mac laptops I tried, it worked on a Mac Pro. It >>>> might be the frame buffer corruption that Ed Maste was mentioning. >>>> >>> I purchased a new MacBook Air yesterday (model identifier >>> MacBookAir6,2). UEFI boot and vt(4) worked correctly. (My image >>> included Rafael's patch; I haven't tried a boot without.) >>> >>> I also committed a change to display the framebuffer parameters >>> (address, dimensions, etc.) on boot, in order to help identify the >>> source of this issue. If you have a moment can you build a new USB >>> stick image and give it a try? >>> >>> -Ed >>> >>> ___ >> 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"
Re: uefi boot on Apple Mac
I got the same result from Fedora-20: [liveuser@localhost ~]$ dmesg|grep efifb [2.665017] efifb: probing for efifb [2.667915] efifb: framebuffer at 0x8002, mapped to 0xc9000b98, using 28800k, total 28800k [2.667916] efifb: mode is 2880x1800x32, linelength=16384, pages=1 [2.667916] efifb: scrolling: redraw [2.667917] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 stride(4096) *4 = linelength 28800k=stride(4096) *4*1800=0x1c2 2014-07-07 2:59 GMT+08:00 Adrian Chadd : > The linux UEFI peeps have the same problem(s): > > http://mjg59.dreamwidth.org/10014.html > > Look for "stride". > > > -a > > > On 6 July 2014 06:40, Aleksandr Rybalko wrote: > > On Fri, 4 Jul 2014 22:34:30 +0800 > > Huang Wen Hui wrote: > > > >> Hi, > >> On my MacbookPro11,3, I got this error message: > >> > >> http://sw.gddsn.org.cn/freebsd/uefi.jpg > > > > Hmmm, really weird. > > Looks like wrong info about UEFI framebuffer. > > Picture said: > > 1. 2880 x 1800 > > 2. 4 bytes per pixel (masks cover whole 32bit) > > 3. but same time stride eq to 4096 (but have to be (width * > bytes_per_pixel) 4 * 2880) > > > >> > >> cheers, > >> > >> Huang WenHui > >> > >> 2014-07-04 22:13 GMT+08:00 Ed Maste : > >> > >> > On 24 May 2014 19:39, Rafael Esp'indola > wrote: > >> > > > >> > > Yes, I got that in the mac laptops I tried, it worked on a Mac Pro. > It > >> > > might be the frame buffer corruption that Ed Maste was mentioning. > >> > > >> > I purchased a new MacBook Air yesterday (model identifier > >> > MacBookAir6,2). UEFI boot and vt(4) worked correctly. (My image > >> > included Rafael's patch; I haven't tried a boot without.) > >> > > >> > I also committed a change to display the framebuffer parameters > >> > (address, dimensions, etc.) on boot, in order to help identify the > >> > source of this issue. If you have a moment can you build a new USB > >> > stick image and give it a try? > >> > > >> > -Ed > >> > > >> ___ > >> 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" > > > > Thanks. > > WBW > > -- > > Aleksandr Rybalko > > ___ > > 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"
Re: uefi boot on Apple Mac
Hi, On my MacbookPro11,3, I got this error message: http://sw.gddsn.org.cn/freebsd/uefi.jpg cheers, Huang WenHui 2014-07-04 22:13 GMT+08:00 Ed Maste : > On 24 May 2014 19:39, Rafael Espíndola wrote: > > > > Yes, I got that in the mac laptops I tried, it worked on a Mac Pro. It > > might be the frame buffer corruption that Ed Maste was mentioning. > > I purchased a new MacBook Air yesterday (model identifier > MacBookAir6,2). UEFI boot and vt(4) worked correctly. (My image > included Rafael's patch; I haven't tried a boot without.) > > I also committed a change to display the framebuffer parameters > (address, dimensions, etc.) on boot, in order to help identify the > source of this issue. If you have a moment can you build a new USB > stick image and give it a try? > > -Ed > ___ 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: uefi boot on Apple Mac
Hi, I try this patch, but no lucky, loader stop at: Start @ 0x802d6ef0 ... Cheers, Huang WenHui 2014-05-22 23:33 GMT+08:00 Rafael Espíndola : > I just emailed a patch. The issue I was having was just that the text > was not being displayed. > > On 22 May 2014 09:37, Anders Bolt-Evensen wrote: > > MacBookPro8,3 doesn't work with uefi boot either. > > At least mine doesn't. > > > > On 19.05.14 02:36, Huang Wen Hui wrote: > >> > >> Hi, > >> I test uefi boot on Macs, some success, include: > >> iMac13,2 , MacbookPro 2012, Macmini5,3. > >> > >> But have problem on MacbookPro 2013, loader stop at: > >> > >> Start @ 0x802d6ef0 ... > >> > >> Any ideas? > >> > >> Cheers, > >> Huang Wenhui > >> ___ > >> 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" > ___ > 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"
uefi boot on Apple Mac
Hi, I test uefi boot on Macs, some success, include: iMac13,2 , MacbookPro 2012, Macmini5,3. But have problem on MacbookPro 2013, loader stop at: Start @ 0x802d6ef0 ... Any ideas? Cheers, Huang Wenhui ___ 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: Apple Trackpad driver
Hi, I tried to add to support modem macbooks into atp(4) at the beginning, but realized that atp(4) is very different from new touchpad hardware, so I give up, I think some one can do that. Cheers, Huang Wen Hui 2014-02-01 Danilo E. Gondolfo : > On 01/31/14 21:45, 黄文辉@Gmail wrote: > > Hi Hans, > > Yes, I wrote wsp base on atp(4) and bcm5974.c from Linux. Of course we > can add a notice about that. Table and some structure bt_data, tp_finger > from Linux, I only wrote wsp_intr_callback base on usbdump, all other part > should be belong to Hans. > > > > Cheers, > > > > Huang Wen Hui > > > >> 在 2014年2月1日，6:49，Hans Petter Selasky 写道： > >> > >>> On 01/31/14 21:30, Danilo E. Gondolfo wrote: > >>>> On 01/31/14 05:16, Hans Petter Selasky wrote: > >>>>> On 01/31/14 02:46, Huang Wen Hui wrote: > >>>>> Hi Hans, > >>>>> > >>>>> pos_x[] is not non-inialized, it may be previous pos_x, it is still > >>>>> ok for > >>>>> getting dx. > >>>>> "n" var is trying to reduce "untouch" sensor data for post > >>>>> proccessing. I > >>>>> attach a new patch > >>>>> may be more clear, also fixed unexpected movement when button status > or > >>>>> ntouch changing. > >>>>> > >>>>> Cheers, > >>>>> > >>>>> Huang Wen Hui > >>>> Hi, > >>>> > >>>> http://svnweb.freebsd.org/changeset/base/261315 > >>>> > >>>> --HPS > >>> Good work! > >>> > >>> I noticed that your driver is based on the Linux driver [1] and some > >>> pieces of code are copied, are you sure that we won't have any problems > >>> with license? > >>> > >>> These changes can be (should be) merged in the driver atp(4), no? > >>> > >>> Danilo. > >>> > >>> > >>> [1] - > http://lxr.free-electrons.com/source/drivers/input/mouse/bcm5974.c > >> Hi, > >> > >> It looks to me like some tables have been copied. We probably should > add a notice about that. The rest of the code looks OK to me. > >> > >> Huang, any comments? > >> > >> --HPS > >> > > > > Hello, > > And what about keeping these two driver? (atp and wsp) > Both has the same purpose. Wouldn't be better merge the new code on atp? > > On freebsd-drivers@ the author of the atp driver started a thread about > this [1]. > > Danilo. > > [1] - > http://lists.freebsd.org/pipermail/freebsd-drivers/2014-January/001659.html > ___ > 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"
Re: Apple Trackpad driver
Hi Hans,
pos_x[] is not non-inialized, it may be previous pos_x, it is still ok for
getting dx.
"n" var is trying to reduce "untouch" sensor data for post proccessing. I
attach a new patch
may be more clear, also fixed unexpected movement when button status or
ntouch changing.
Cheers,
Huang Wen Hui
2014-01-30 Hans Petter Selasky :
> Hi Huang,
>
>
> On 01/30/14 06:56, Huang Wen Hui wrote:
>
>> Hans,
>>
>> Thanks for you take care of it and commit it! I found two problems:
>>
>> 1. The selection is not expected when selection with 2 fingers sometimes.
>> 2. Unexpected scrolling when Click with 2 fingers.
>>
>> This patch can fix that. The var "n" modify to "ntouch" seems to be
>> necessary.
>>
>>
> Right, but aren't we then accessing non-initialised sc->pos_x[] data ?
>
> Because if ntouch == 2, n can be less than or equal to 2, due to continue
> in for-loop above. What is the purpose of the "n" variable?
>
> Can you explain?
>
> - if (n == 2) {
> + if (ntouch == 2) {
> sc->distance = max(sc->distance, max(
> abs(sc->pos_x[0] - sc->pos_x[1]),
> abs(sc->pos_y[0] - sc->pos_y[1])));
>
> --HPS
>
>
>> Cheers,
>> Huang Wen Hui
>>
>>
>> 2014-01-29 Hans Petter Selasky
>>
>> On 01/29/14 09:49, Lundberg, Johannes wrote:
>>>
>>> Hi
>>>>
>>>> I tested the driver on a 2012 Macbook Air 11" and it works great! Good
>>>> job!
>>>>
>>>> Is there a way to disable click-by-touch? I always preferred clicking
>>>> with
>>>> the physical button that is built in to the pad.
>>>>
>>>>
>>>> Hi,
>>>
>>> I've added an "#if 0" around the 1 finger tap code until further. Maybe
>>> this feature can be tunable?
>>>
>>> I fixed the code style, added some range checks and cleared some buffer
>>> issues.
>>>
>>> When you assign a signed value to an unsigned variable, you should range
>>> check it, because the sign might cause an overflow when you use it later
>>> on.
>>>
>>> int8_t x = -1;
>>>
>>> uint32_t t = x;
>>>
>>> "t" is now "0xU" and not "255".
>>>
>>> Tested the code on my MacBookPro. Hope I didn't break anything. If so,
>>> send a patch to freebsd-usb.
>>>
>>> http://svnweb.freebsd.org/changeset/base/261260
>>>
>>> To get the touchpad working with Xorg, I needed to re-compile HALD with
>>> the attached patch.
>>>
>>> kwm: Can you get the attached patch into ports?
>>>
>>> Auto-loading of wsp via devd will be done later. Simply need to
>>> re-generate usb.conf in /etc ...
>>>
>>> --HPS
>>>
>>>
>>>
>>>
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@
>>> freebsd.org"
>>>
>>
>
--- wsp.c.orig 2014-01-30 08:14:26.0 +0800
+++ wsp.c 2014-01-31 09:44:02.0 +0800
@@ -605,7 +605,8 @@
int dz_count;
#defineWSP_DZ_MAX_COUNT32
int dt_sum; /* T-axis cumulative movement */
-
+
+ uint8_t o_ntouch; /* old touch finger status */
uint8_t finger; /* 0 or 1 *, check which finger moving
*/
uint16_t intr_count;
#defineWSP_TAP_THRESHOLD 3
@@ -871,7 +872,6 @@
int dx = 0;
int dy = 0;
int dz = 0;
- int n = 0;
int len;
int i;
@@ -936,13 +936,9 @@
f[i].tool_major, f[i].tool_minor, f[i].orientation,
f[i].touch_major, f[i].touch_minor, f[i].multi);
- if (f[i].touch_major < tun.pressure_untouch_threshold)
- continue;
-
- sc->pos_x[n] = f[i].abs_x;
- sc->pos_y[n] = params->y.min + params->y.max -
f[i].abs_y;
- sc->index[n] = &f[i];
- n++;
+ sc->pos_x[i] = f[i].abs_x;
+ sc->pos_y[i] = params->y.min + params->y.max -
f[i].abs_y;
+ sc->index[i] = &f[i];
Re: Apple Trackpad driver
Hans,
Thanks for you take care of it and commit it! I found two problems:
1. The selection is not expected when selection with 2 fingers sometimes.
2. Unexpected scrolling when Click with 2 fingers.
This patch can fix that. The var "n" modify to "ntouch" seems to be
necessary.
Cheers,
Huang Wen Hui
2014-01-29 Hans Petter Selasky
> On 01/29/14 09:49, Lundberg, Johannes wrote:
>
>> Hi
>>
>> I tested the driver on a 2012 Macbook Air 11" and it works great! Good
>> job!
>>
>> Is there a way to disable click-by-touch? I always preferred clicking with
>> the physical button that is built in to the pad.
>>
>>
> Hi,
>
> I've added an "#if 0" around the 1 finger tap code until further. Maybe
> this feature can be tunable?
>
> I fixed the code style, added some range checks and cleared some buffer
> issues.
>
> When you assign a signed value to an unsigned variable, you should range
> check it, because the sign might cause an overflow when you use it later on.
>
> int8_t x = -1;
>
> uint32_t t = x;
>
> "t" is now "0xU" and not "255".
>
> Tested the code on my MacBookPro. Hope I didn't break anything. If so,
> send a patch to freebsd-usb.
>
> http://svnweb.freebsd.org/changeset/base/261260
>
> To get the touchpad working with Xorg, I needed to re-compile HALD with
> the attached patch.
>
> kwm: Can you get the attached patch into ports?
>
> Auto-loading of wsp via devd will be done later. Simply need to
> re-generate usb.conf in /etc ...
>
> --HPS
>
>
--- wsp.c.orig 2014-01-30 08:14:26.0 +0800
+++ wsp.c 2014-01-30 13:49:59.0 +0800
@@ -957,8 +957,8 @@
if (h->q2 == 4)
sc->intr_count++;
- if (sc->ntaps < n) {
- switch (n) {
+ if (sc->ntaps < ntouch) {
+ switch (ntouch) {
case 1:
if (f[0].touch_major >
tun.pressure_tap_threshold)
sc->ntaps = 1;
@@ -978,7 +978,7 @@
break;
}
}
- if (n == 2) {
+ if (ntouch == 2) {
sc->distance = max(sc->distance, max(
abs(sc->pos_x[0] - sc->pos_x[1]),
abs(sc->pos_y[0] - sc->pos_y[1])));
@@ -1050,12 +1050,20 @@
if (sc->sc_touch == WSP_SECOND_TOUCH)
sc->sc_touch = WSP_TOUCHING;
- if (n != 0 &&
+ if (ntouch != 0 &&
h->q2 == 4 &&
f[0].touch_major >= tun.pressure_touch_threshold) {
dx = sc->pos_x[0] - sc->pre_pos_x;
dy = sc->pos_y[0] - sc->pre_pos_y;
- if (n == 2 && sc->sc_status.button != 0) {
+
+ /* Ignore movement from ibt=1 to ibt=0 */
+ if (sc->sc_status.obutton != 0 &&
+ sc->sc_status.button == 0) {
+ dx = 0;
+ dy = 0;
+ }
+
+ if (ntouch == 2 && sc->sc_status.button != 0) {
dx = sc->pos_x[sc->finger] -
sc->pre_pos_x;
dy = sc->pos_y[sc->finger] -
sc->pre_pos_y;
if (f[0].origin == 0 || f[1].origin ==
0) {
@@ -1092,7 +1100,7 @@
sc->dx_sum += dx;
sc->dy_sum += dy;
- if (n == 2 && sc->sc_status.button == 0) {
+ if (ntouch == 2 && sc->sc_status.button == 0) {
if (sc->scr_mode == WSP_SCR_NONE &&
abs(sc->dx_sum) + abs(sc->dy_sum) > 50)
sc->scr_mode = abs(sc->dx_sum) >
@@ -1134,7 +1142,7 @@
sc->pre_pos_x = sc->pos_x[0];
sc->pre_pos_y = sc->pos_y[0];
- if (n == 2 && sc->sc_status.button != 0) {
+ if (ntouch == 2 && sc->sc_status.button != 0) {
sc->pre_pos_x = sc->pos_x[sc->finger];
sc->pre_pos_y = sc->pos_y[sc->finger];
}
___
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"
Apple Trackpad driver
Hi, I have a working trackpad driver for my MBP 2013, I am not C programmer usually, so the code may ugly. If someone like to test, you can download it from http://sw.gddsn.org.cn/freebsd/wsp-140129.tar.gz, I only test it on MBP2012 and MBP2013. Right now the driver have these feature: 1. Vertical scrolling with 2 fingers movement, 2. In firefox, 2 fingers horizontal movement act as page back/forward. 3. one finger tap act as left mouse click, 2 fingers tap act as right mouse click, and three fingers tap act as middle mouse click. 4. you also use sysctl to modify some parameters: hw.usb.wsp.scale_factor: 12 hw.usb.wsp.z_factor: 5 hw.usb.wsp.pressure_touch_threshold: 50 hw.usb.wsp.pressure_untouch_threshold: 10 hw.usb.wsp.pressure_tap_threshold: 120 hw.usb.wsp.scr_hor_threshold: 50 Cheers, Huang Wen Hui ___ 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: Install 10.0-RC3 on MacBookPro Late 2013
I try many times plug/unplug, this patch basically works, but I still got the previous problem one time. Cheers, Huang Wen Hui 2014/1/11 Hans Petter Selasky > On 01/11/14 05:14, Huang Wen Hui wrote: > >> Hi, >> >> I got one problem when I unplug/plug "Buffalo WLI-UC-GNM", it is USB WLAN. >> All USB devices become to disconnected after unplug and plug: >> >> > Try this: > > http://svnweb.freebsd.org/changeset/base/260535 > > --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: Install 10.0-RC3 on MacBookPro Late 2013
Hi, I got one problem when I unplug/plug "Buffalo WLI-UC-GNM", it is USB WLAN. All USB devices become to disconnected after unplug and plug: ugen0.9: at usbus0 run0: <1.0> on usbus0 run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 4c:e6:76:d4:c9:5e wlan0: Ethernet address: 4c:e6:76:d4:c9:5e run0: firmware RT2870 ver. 0.33 loaded wlan0: link state changed to UP ugen0.9: at usbus0 (disconnected) run0: at uhub0, port 1, addr 8 (disconnected) wlan0: link state changed to DOWN xhci0: Port routing mask set to 0x usb_alloc_device: device init 9 failed (USB_ERR_IOERROR, ignored) ugen0.9: at usbus0 (disconnected) uhub_reattach_port: could not allocate new device ugen0.2: at usbus0 (disconnected) ums0: at uhub0, port 5, addr 1 (disconnected) ugen0.3: at usbus0 (disconnected) uhub1: at uhub0, port 8, addr 2 (disconnected) ugen0.4: at usbus0 (disconnected) ukbd0: at uhub1, port 1, addr 3 (disconnected) ugen0.5: at usbus0 (disconnected) ums1: at uhub1, port 2, addr 4 (disconnected) ugen0.6: at usbus0 (disconnected) ugen0.7: at usbus0 (disconnected) ukbd1: at uhub0, port 12, addr 6 (disconnected) uhid0: at uhub0, port 12, addr 6 (disconnected) ums2: at uhub0, port 12, addr 6 (disconnected) ugen0.8: at usbus0 (disconnected) umass0: at uhub0, port 19, addr 7 (disconnected) da0 at umass-sim0 bus 0 scbus1 target 0 lun 0 da0: s/n 0820 detached (da0:umass-sim0:0:0:0): Periph destroyed I still revert xhci_interrupt back to 9.1R, unplug/plug this WLAN, xhci driver works perfect. Cheers, Huang Wen Hui 2014/1/7 Hans Petter Selasky > On 01/07/14 08:07, Huang Wen Hui wrote: > >> Hi, >> This patch fixed my problem! >> >> Thanks, >> Huang Wen Hui. >> > > http://svnweb.freebsd.org/changeset/base/260388 > > --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: Install 10.0-RC3 on MacBookPro Late 2013
Hi,
After USB problem fixed, I run some test: builworld/builkernel, mate,
chrome and
eclipse, every thing is fine, no random hang! I guess the hang problem is
gone with
USB problem fixed...
Cheers,
Huang Wen Hui
2014/1/7 Huang Wen Hui
> USB problem fixed by revert to r245731,
> set "hint.ahci.0.msi=0" seem to fixed timeout problem of AHCI.
>
> Random hang I think still exist, will check later...
>
> Cheers,
> Huang Wen Hui
>
>
> 2014/1/7 Lundberg, Johannes
>
> Hi Huang
>>
>> Good job!! By "works", which parts do you mean has been fixed?
>>
>> 1. USB problem
>> or
>> 2. AHCI timeout problem
>> or
>> 3. Random hang
>>
>> Best regards!
>>
>> --
>> Johannes Lundberg
>> BRILLIANTSERVICE CO., LTD.
>>
>>
>> On Tue, Jan 7, 2014 at 11:30 AM, Huang Wen Hui wrote:
>>
>>> Hans,
>>>
>>> This wild guess do NOT works.
>>> I binary sect xhci.c in SVN, found that *r245732
>>> *<http://svnweb.freebsd.org/base?view=revision&revision=245732>*
>>> introduce the bug.*
>>> <http://svnweb.freebsd.org/base?view=revision&revision=245732>
>>>
>>> revert to r345731 fixed this USB problem in 9.2R
>>>
>>> I also copy xhci_interrupt(struct xhci_softc *sc) from 9.1R to CURRENT,
>>> CURRENT also works!
>>>
>>> Cheers,
>>> Huang Wen Hui.
>>>
>>>
>>> 2014/1/7 Hans Petter Selasky
>>>
>>> > On 01/06/14 16:28, Hans Petter Selasky wrote:
>>> >
>>> >> On 01/06/14 15:17, Adrian Chadd wrote:
>>> >>
>>> >>> Right, but it used to work. That's the confusing bit. How'd you make
>>> >>> it not work? :)
>>> >>>
>>> >>
>>> >> Binary sect the sys/dev/usb/controller/xhci.c revision history? There
>>> >> has been several bug reports for the Lynx point, and others XHCI
>>> >> chipsets are working just fine.
>>> >>
>>> >>
>>> > A wild guess:
>>> >
>>> > Copy the USB-code from -current.
>>> >
>>> > Add "#if 0" as shown sys/dev/usb/controller/xhci_pci.c
>>> >
>>> > static int
>>> > xhci_pci_port_route(device_t self, uint32_t set, uint32_t clear)
>>> > {
>>> > #if 0
>>> > uint32_t temp;
>>> >
>>> > temp = pci_read_config(self, PCI_XHCI_INTEL_USB3_PSSEN, 4) |
>>> > pci_read_config(self, PCI_XHCI_INTEL_XUSB2PR, 4);
>>> >
>>> > temp |= set;
>>> > temp &= ~clear;
>>> >
>>> > pci_write_config(self, PCI_XHCI_INTEL_USB3_PSSEN, temp, 4);
>>> > pci_write_config(self, PCI_XHCI_INTEL_XUSB2PR, temp, 4);
>>> >
>>> > device_printf(self, "Port routing mask set to 0x%08x\n", temp);
>>> > #endif
>>> > return (0);
>>> > }
>>> >
>>> > --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"
>>>
>>
>>
>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
>> もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
>> 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
>> ---
>> CONFIDENTIALITY NOTE: The information in this email is confidential
>> and intended solely for the addressee.
>> Disclosure, copying, distribution or any other action of use of this
>> email by person other than intended recipient, is prohibited.
>> If you are not the intended recipient and have received this email in
>> error, please destroy the original message.
>>
>
>
___
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: Install 10.0-RC3 on MacBookPro Late 2013
Hi, This patch fixed my problem! Thanks, Huang Wen Hui. 2014/1/7 Hans Petter Selasky > On 01/07/14 03:30, Huang Wen Hui wrote: > >> Hans, >> >> This wild guess do NOT works. >> I binary sect xhci.c in SVN, found that *r245732 >> *<http://svnweb.freebsd.org/base?view=revision&revision=245732>* >> introduce the bug.* >> <http://svnweb.freebsd.org/base?view=revision&revision=245732> >> revert to r345731 fixed this USB problem in 9.2R >> >> I also copy xhci_interrupt(struct xhci_softc *sc) from 9.1R to CURRENT, >> CURRENT also works! >> >> Cheers, >> Huang Wen Hui. >> > > > Hi, > > We need to take this step by step. Thanks for tracing this down! > > Can you test the attached patch towards -current. > > Thank you! > > --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: Install 10.0-RC3 on MacBookPro Late 2013
Hi,
2014/1/7 Lundberg, Johannes
> Hi Huang
>
> I have also experienced random hangs. However, I'm not sure if they are
> really hangs or just the USB driver stopped working. Since mouse pad,
> keyboard everything is run through USB I couldn't tell really what happened.
>
If LAN is on, you can ping to check if the system is really hangs.
>
> Did you have any problems with the identifier of the ssd? When I first
> tried FreeBSD on MBA2013 it couldn't identify the ssd because there was
> some weird characters in the ssd's identifier. Gavin helped me create a
> patch that solved the problem temporary (by hard coding a different ident)
> but I'm not sure if a permanent fix has been merged.
>
NO, my MBP have customized 1TB SSD:
# camcontrol identify ada0
pass0: ATA-8 SATA 3.x device
pass0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
protocol ATA/ATAPI-8 SATA 3.x
device model APPLE SSD SM1024F
firmware revision UXM6JA1Q
serial number S1K6NYADC02996
WWN 5002538655584d30
cylinders 16383
heads 16
sectors/track 63
sector size logical 512, physical 4096, offset 0
LBA supported 268435455 sectors
LBA48 supported 1954210120 sectors
PIO supported PIO4
DMA supported WDMA2 UDMA6
media RPM non-rotating
>
> --
> Johannes Lundberg
> BRILLIANTSERVICE CO., LTD.
>
>
> On Tue, Jan 7, 2014 at 12:05 PM, Huang Wen Hui wrote:
>
>> USB problem fixed by revert to r245731,
>> set "hint.ahci.0.msi=0" seem to fixed timeout problem of AHCI.
>>
>> Random hang I think still exist, will check later...
>>
>> Cheers,
>> Huang Wen Hui
>>
>>
>> 2014/1/7 Lundberg, Johannes
>>
>>> Hi Huang
>>>
>>> Good job!! By "works", which parts do you mean has been fixed?
>>>
>>> 1. USB problem
>>> or
>>> 2. AHCI timeout problem
>>> or
>>> 3. Random hang
>>>
>>> Best regards!
>>>
>>> --
>>> Johannes Lundberg
>>> BRILLIANTSERVICE CO., LTD.
>>>
>>>
>>> On Tue, Jan 7, 2014 at 11:30 AM, Huang Wen Hui wrote:
>>>
>>>> Hans,
>>>>
>>>> This wild guess do NOT works.
>>>> I binary sect xhci.c in SVN, found that *r245732
>>>> *<http://svnweb.freebsd.org/base?view=revision&revision=245732>*
>>>> introduce the bug.*
>>>> <http://svnweb.freebsd.org/base?view=revision&revision=245732>
>>>>
>>>> revert to r345731 fixed this USB problem in 9.2R
>>>>
>>>> I also copy xhci_interrupt(struct xhci_softc *sc) from 9.1R to CURRENT,
>>>> CURRENT also works!
>>>>
>>>> Cheers,
>>>> Huang Wen Hui.
>>>>
>>>>
>>>> 2014/1/7 Hans Petter Selasky
>>>>
>>>> > On 01/06/14 16:28, Hans Petter Selasky wrote:
>>>> >
>>>> >> On 01/06/14 15:17, Adrian Chadd wrote:
>>>> >>
>>>> >>> Right, but it used to work. That's the confusing bit. How'd you make
>>>> >>> it not work? :)
>>>> >>>
>>>> >>
>>>> >> Binary sect the sys/dev/usb/controller/xhci.c revision history? There
>>>> >> has been several bug reports for the Lynx point, and others XHCI
>>>> >> chipsets are working just fine.
>>>> >>
>>>> >>
>>>> > A wild guess:
>>>> >
>>>> > Copy the USB-code from -current.
>>>> >
>>>> > Add "#if 0" as shown sys/dev/usb/controller/xhci_pci.c
>>>> >
>>>> > static int
>>>> > xhci_pci_port_route(device_t self, uint32_t set, uint32_t clear)
>>>> > {
>>>> > #if 0
>>>> > uint32_t temp;
>>>> >
>>>> > temp = pci_read_config(self, PCI_XHCI_INTEL_USB3_PSSEN, 4) |
>>>> > pci_read_config(self, PCI_XHCI_INTEL_XUSB2PR, 4);
>>>> >
>>>> > temp |= set;
>>>> > temp &= ~clear;
>>>> >
>>>> > pci_write_config(self, PCI_XHCI_INTEL_USB3_PSSEN, temp, 4);
>>>> > pci_write_config(self, PCI_XHCI_INTEL_XUSB2PR, temp, 4);
>>>> >
>>>> > device_printf(self, "Port routing mask set to 0x%08x\n",
>>>> temp);
>>>> >
Re: Install 10.0-RC3 on MacBookPro Late 2013
USB problem fixed by revert to r245731,
set "hint.ahci.0.msi=0" seem to fixed timeout problem of AHCI.
Random hang I think still exist, will check later...
Cheers,
Huang Wen Hui
2014/1/7 Lundberg, Johannes
> Hi Huang
>
> Good job!! By "works", which parts do you mean has been fixed?
>
> 1. USB problem
> or
> 2. AHCI timeout problem
> or
> 3. Random hang
>
> Best regards!
>
> --
> Johannes Lundberg
> BRILLIANTSERVICE CO., LTD.
>
>
> On Tue, Jan 7, 2014 at 11:30 AM, Huang Wen Hui wrote:
>
>> Hans,
>>
>> This wild guess do NOT works.
>> I binary sect xhci.c in SVN, found that *r245732
>> *<http://svnweb.freebsd.org/base?view=revision&revision=245732>*
>> introduce the bug.*
>> <http://svnweb.freebsd.org/base?view=revision&revision=245732>
>>
>> revert to r345731 fixed this USB problem in 9.2R
>>
>> I also copy xhci_interrupt(struct xhci_softc *sc) from 9.1R to CURRENT,
>> CURRENT also works!
>>
>> Cheers,
>> Huang Wen Hui.
>>
>>
>> 2014/1/7 Hans Petter Selasky
>>
>> > On 01/06/14 16:28, Hans Petter Selasky wrote:
>> >
>> >> On 01/06/14 15:17, Adrian Chadd wrote:
>> >>
>> >>> Right, but it used to work. That's the confusing bit. How'd you make
>> >>> it not work? :)
>> >>>
>> >>
>> >> Binary sect the sys/dev/usb/controller/xhci.c revision history? There
>> >> has been several bug reports for the Lynx point, and others XHCI
>> >> chipsets are working just fine.
>> >>
>> >>
>> > A wild guess:
>> >
>> > Copy the USB-code from -current.
>> >
>> > Add "#if 0" as shown sys/dev/usb/controller/xhci_pci.c
>> >
>> > static int
>> > xhci_pci_port_route(device_t self, uint32_t set, uint32_t clear)
>> > {
>> > #if 0
>> > uint32_t temp;
>> >
>> > temp = pci_read_config(self, PCI_XHCI_INTEL_USB3_PSSEN, 4) |
>> > pci_read_config(self, PCI_XHCI_INTEL_XUSB2PR, 4);
>> >
>> > temp |= set;
>> > temp &= ~clear;
>> >
>> > pci_write_config(self, PCI_XHCI_INTEL_USB3_PSSEN, temp, 4);
>> > pci_write_config(self, PCI_XHCI_INTEL_XUSB2PR, temp, 4);
>> >
>> > device_printf(self, "Port routing mask set to 0x%08x\n", temp);
>> > #endif
>> > return (0);
>> > }
>> >
>> > --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
>> "
>>
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
> もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
> 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
> ---
> CONFIDENTIALITY NOTE: The information in this email is confidential
> and intended solely for the addressee.
> Disclosure, copying, distribution or any other action of use of this
> email by person other than intended recipient, is prohibited.
> If you are not the intended recipient and have received this email in
> error, please destroy the original message.
>
___
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: Install 10.0-RC3 on MacBookPro Late 2013
Hans,
This wild guess do NOT works.
I binary sect xhci.c in SVN, found that *r245732
*<http://svnweb.freebsd.org/base?view=revision&revision=245732>*
introduce the bug.*
<http://svnweb.freebsd.org/base?view=revision&revision=245732>
revert to r345731 fixed this USB problem in 9.2R
I also copy xhci_interrupt(struct xhci_softc *sc) from 9.1R to CURRENT,
CURRENT also works!
Cheers,
Huang Wen Hui.
2014/1/7 Hans Petter Selasky
> On 01/06/14 16:28, Hans Petter Selasky wrote:
>
>> On 01/06/14 15:17, Adrian Chadd wrote:
>>
>>> Right, but it used to work. That's the confusing bit. How'd you make
>>> it not work? :)
>>>
>>
>> Binary sect the sys/dev/usb/controller/xhci.c revision history? There
>> has been several bug reports for the Lynx point, and others XHCI
>> chipsets are working just fine.
>>
>>
> A wild guess:
>
> Copy the USB-code from -current.
>
> Add "#if 0" as shown sys/dev/usb/controller/xhci_pci.c
>
> static int
> xhci_pci_port_route(device_t self, uint32_t set, uint32_t clear)
> {
> #if 0
> uint32_t temp;
>
> temp = pci_read_config(self, PCI_XHCI_INTEL_USB3_PSSEN, 4) |
> pci_read_config(self, PCI_XHCI_INTEL_XUSB2PR, 4);
>
> temp |= set;
> temp &= ~clear;
>
> pci_write_config(self, PCI_XHCI_INTEL_USB3_PSSEN, temp, 4);
> pci_write_config(self, PCI_XHCI_INTEL_XUSB2PR, temp, 4);
>
> device_printf(self, "Port routing mask set to 0x%08x\n", temp);
> #endif
> return (0);
> }
>
> --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: Install 10.0-RC3 on MacBookPro Late 2013
Yes, I did it, works like 9.1R. 2014/1/6 Hans Petter Selasky > On 01/06/14 09:19, Huang Wen Hui wrote: > >> The xhci code from 9.1R is OK, but there are a lot of "USB_ERR_TIMEOUT" in >> 9.2R... >> > > Have you copied the USB code from 9.1R to 9.2R and made a build? > > --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: Install 10.0-RC3 on MacBookPro Late 2013
= PCI-PCI bge0@pci0:11:0:0:class=0x02 card=0x00f6106b chip=0x168214e4 rev=0x00 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme BCM57762 Gigabit Ethernet PCIe' class = network subclass = ethernet none3@pci0:3:0:0:class=0x028000 card=0x0134106b chip=0x43a014e4 rev=0x03 hdr=0x00 vendor = 'Broadcom Corporation' class = network none4@pci0:4:0:0:class=0x048000 card=0x157014e4 chip=0x157014e4 rev=0x00 hdr=0x00 vendor = 'Broadcom Corporation' class = multimedia ahci0@pci0:5:0:0:class=0x010601 card=0x chip=0x1600144d rev=0x01 hdr=0x00 vendor = 'Samsung Electronics Co Ltd' class = mass storage subclass = SATA 9.1R xhci code found these devices: ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (70mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (94mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) ugen0.6: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) ugen0.7: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (40mA) ugen0.8: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (224mA) 2014/1/6 Hans Petter Selasky > On 01/06/14 11:15, Huang Wen Hui wrote: > >> 2014/1/6 Hans Petter Selasky >> >> On 01/06/14 10:41, Huang Wen Hui wrote: >>> >>> % grep xhci dmesg-xhci-debug.txt | more >>>> xhci0: mem 0xc1e0-0xc1e0 >>>> at >>>> device 20.0 on pci0 >>>> xhci0: attempting to allocate 1 MSI vectors (8 supported) >>>> xhci0: using IRQ 266 for MSI >>>> xhci0: MSI enabled >>>> >>>> >>> Those USB timeouts are most likely due to port routing not working >>> properly. It is because intel did something special to their lynx point >>> series. >>> >>> Try to set : >>> >>> hw.usb.xhci.xhci_port_route = "-1" >>> >>> in /boot/loader.conf >>> >> >> >> Try this before, hw.usb.xhci.xhci_port_route = "-1" make almost of all >> usb >> devices not found. >> >> external mouse seems to no power at all. >> >> # usbconfig list >> ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER >> (5.0Gbps) pwr=SAVE (0mA) >> ugen0.2: at usbus0, cfg=255 md=HOST >> spd=SUPER (5.0Gbps) pwr=ON (100mA) >> >> > Hi, > > If you check using pciconf -lv, is there a USB controller which has no > driver attached? Typically there should be an EHCI/OHCI/UHCI companion > controller. When the port route is set to -1 these devices should attach to > the companion controller instead. > > --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: Install 10.0-RC3 on MacBookPro Late 2013
2014/1/6 Hans Petter Selasky > On 01/06/14 10:41, Huang Wen Hui wrote: > >> % grep xhci dmesg-xhci-debug.txt | more >> xhci0: mem 0xc1e0-0xc1e0 at >> device 20.0 on pci0 >> xhci0: attempting to allocate 1 MSI vectors (8 supported) >> xhci0: using IRQ 266 for MSI >> xhci0: MSI enabled >> > > Those USB timeouts are most likely due to port routing not working > properly. It is because intel did something special to their lynx point > series. > > Try to set : > > hw.usb.xhci.xhci_port_route = "-1" > > in /boot/loader.conf Try this before, hw.usb.xhci.xhci_port_route = "-1" make almost of all usb devices not found. external mouse seems to no power at all. # usbconfig list ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=255 md=HOST spd=SUPER (5.0Gbps) pwr=ON (100mA) > > --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: Install 10.0-RC3 on MacBookPro Late 2013
Hans, I got this message, and full log in http://sw.gddsn.org.cn/freebsd/dmesg-xhci-debug.txt Cheers, Huang Wen Hui. % grep xhci dmesg-xhci-debug.txt | more xhci0: mem 0xc1e0-0xc1e0 at device 20.0 on pci0 xhci0: attempting to allocate 1 MSI vectors (8 supported) xhci0: using IRQ 266 for MSI xhci0: MSI enabled xhci_halt_controller: xhci_start_controller: xhci_start_controller: CAPLENGTH=0x80 xhci_start_controller: RUNTIMEOFFSET=0x2000 xhci_start_controller: DOOROFFSET=0x3000 xhci_start_controller: xHCI version = 0x0100 xhci_start_controller: HCS0 = 0x200077c1 xhci0: 32 byte context size. xhci_start_controller: CONFIG=0x -> 0x0020 xhci_start_controller: Max slots: 32 xhci_start_controller: Max scratch: 16 xhci_start_controller: HCS2=0x8454 xhci_start_controller: ERSTSZ=0x -> 0x0001 xhci_start_controller: ERDP(0)=0x06881080 xhci_start_controller: ERSTBA(0)=0x06881000 xhci_start_controller: CRCR=0x06881d80 xhci_interrupt_poll: event[0] = 34 (0x0800 0x0100 0x8801) xhci_interrupt_poll: Unhandled event = 34 xhci_interrupt_poll: event[1] = 34 (0x0c00 0x0100 0x8801) xhci_interrupt_poll: Unhandled event = 34 xhci_interrupt_poll: event[2] = 34 (0x1300 0x0100 0x8801) xhci_interrupt_poll: Unhandled event = 34 xhci0: Port routing mask set to 0x usbus0 on xhci0 xhci0: usbpf: Attached xhci_interrupt: real interrupt (status=0x0008) xhci_interrupt: real interrupt (status=0x0008) xhci_set_hw_power: xhci_ep_init: endpoint=0xf8002f68a0d8, addr=0, endpt=0, mode=0 xhci_roothub_exec: type=0x00 request=0x05 wLen=0x wValue=0x0001 wIndex=0x xhci_roothub_exec: type=0x80 request=0x06 wLen=0x0012 wValue=0x0100 wIndex=0x xhci_roothub_exec: type=0x80 request=0x06 wLen=0x0002 wValue=0x0300 wIndex=0x xhci_roothub_exec: type=0x80 request=0x06 wLen=0x0004 wValue=0x0300 wIndex=0x xhci_roothub_exec: type=0x80 request=0x06 wLen=0x0002 wValue=0x0301 wIndex=0x0001 xhci_roothub_exec: type=0x80 request=0x06 wLen=0x000e wValue=0x0301 wIndex=0x0001 xhci_roothub_exec: type=0x80 request=0x06 wLen=0x0002 wValue=0x0302 wIndex=0x0001 xhci_roothub_exec: type=0x80 request=0x06 wLen=0x001c wValue=0x0302 wIndex=0x0001 xhci_roothub_exec: type=0x80 request=0x06 wLen=0x0009 wValue=0x0200 wIndex=0x xhci_roothub_exec: type=0x80 request=0x06 wLen=0x001f wValue=0x0200 wIndex=0x xhci_roothub_exec: type=0x00 request=0x09 wLen=0x wValue=0x0001 wIndex=0x xhci_ep_init: endpoint=0xf80007407a00, addr=1, endpt=129, mode=0 xhci_roothub_exec: type=0xa0 request=0x06 wLen=0x000c wValue=0x2a00 wIndex=0x xhci_roothub_exec: type=0xa0 request=0x06 wLen=0x000e wValue=0x2a00 wIndex=0x xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0001 xhci_roothub_exec: set port power 1 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0002 xhci_roothub_exec: set port power 2 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0003 xhci_roothub_exec: set port power 3 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0004 xhci_roothub_exec: set port power 4 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0005 xhci_roothub_exec: set port power 5 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0006 xhci_roothub_exec: set port power 6 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0007 xhci_roothub_exec: set port power 7 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0008 xhci_roothub_exec: set port power 8 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0009 xhci_roothub_exec: set port power 9 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x000a xhci_roothub_exec: set port power 10 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x000b xhci_roothub_exec: set port power 11 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x000c xhci_roothub_exec: set port power 12 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x000d xhci_roothub_exec: set port power 13 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x000e xhci_roothub_exec: set port power 14 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x000f xhci_roothub_exec: set port power 15 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0010 xhci_roothub_exec: set port power 16 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0011 xhci_roothub_exec: set port power 17 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0012 xhci_roothub_exec: set port power 18 xhci_roothub_exec: type=0x23 request=0x03 wLen=0x wValue=0x0008 wIndex=0x0013 xhci_roothub_exec: set port po
Re: Install 10.0-RC3 on MacBookPro Late 2013
The xhci code from 9.1R is OK, but there are a lot of "USB_ERR_TIMEOUT" in 9.2R... 2014/1/6 Adrian Chadd > .. are you getting this USB_ERR_TIMEOUT even with the xhci code from -9? > > > -a > > On 5 January 2014 23:10, Hans Petter Selasky wrote: > > On 01/06/14 05:11, Huang Wen Hui wrote: > >> > >> Hi, > >> > >> USB still have a lot of USB_ERR_TIMEOUT, but Internal keyboard and > >> external keyboard found and works! > >> usb disk also found, but booting stop at: > >> Mounting from ufs:/dev/da0a failed with error 6. > >> or a lot of cam Retrying command. > >> > >> Cheers, > >> Huang Wen Hui > > > > > > Hi, > > > > I think there is an IRQ problem. Either some IRQ is not handled or IRQ's > are > > not forwarded to the drivers properly. You might want to compile the XHCI > > debugging variable to 16 inside dev/usb/controller/xhci.c, and watch > what is > > going on. > > > > --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: Install 10.0-RC3 on MacBookPro Late 2013
Hi, USB still have a lot of USB_ERR_TIMEOUT, but Internal keyboard and external keyboard found and works! usb disk also found, but booting stop at: Mounting from ufs:/dev/da0a failed with error 6. or a lot of cam Retrying command. Cheers, Huang Wen Hui 2014/1/6 Huang Wen Hui > Hi, > I also install 11-amd64 snapshot 2 days ago, I remember AHCI is OK, but > USB and random hang are still existed. > I will confirm it later. > > Cheers, > Huang Wen Hui. > > > 2014/1/6 Adrian Chadd > >> Hi! >> >> Would you mind a recent 11-amd64 snapshot? Hans has committed a few >> fixes to the driver recently. >> >> Thanks! >> >> >> -a >> >> >> On 5 January 2014 19:01, Huang Wen Hui wrote: >> > Hi, >> > >> > I am trying to install FreeBSD on MacBookPro Late 2013, I got 3 main >> > problems: >> > >> > 1. USB problem >> > >> > This MacBookPro model only have xhci controller, 10.0-RC3 and 9.2R not >> > working, keyboard and touchpad not respond. Error messages are >> > "xhci_do_command: Command timeout!" and "USB_ERR_TIMEOUT". >> > I also try to set "hw.usb.xhci.msi=0", no lucky. >> > >> > But 9.1R is OK, I copy xhci*.* file from 9.1R to 10.0, with very small >> > change, and >> > xhci works under 10.0-RC3! >> > >> > dmesg in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/dmesg-10.0.txt >> > vmstat -i in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/vmstat-10.0.txt >> > pciconf in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/pciconf.txt >> > >> > dmesg in 10.0 + xhci of 9.1R: >> > http://sw.gddsn.org.cn/freebsd/dmesg-10.0+9.1.txt >> > vmstat -i in + xhci of 9.1R: >> > http://sw.gddsn.org.cn/freebsd/vmstat-10.0+9.1.txt >> > >> > 2. AHCI timeout problem >> > >> > After booting, system quickly hit ahci timeout problem, I have to set >> > "camcontrol tags ada0 -N 1". >> > this can decrease timeout problem, but still happen when running heavy >> IO. >> > >> > "hint.ahci.0.msi=0" seem to fix this problem, but ahci and xhci use same >> > IRQ 16, this make 10.0+9.1xhci >> > unstable:( Internal keyboard and touchpad not working, external >> keyboard >> > and mouse working. >> > >> > vmstat -i in 10.0+9.1xhci with "hint.ahci.0.msi=0": >> > http://sw.gddsn.org.cn/freebsd/vmstat-10.0+9.1+msi.txt >> > camcontrol identify: http://sw.gddsn.org.cn/freebsd/cam-identify.txt >> > smartctl: http://sw.gddsn.org.cn/freebsd/smartctl.txt >> > >> > 3. Random hang >> > >> > Sometimes the system(10.0+9.1xhci) hang without any message, keyboard, >> > mouse and ping ping not respond. >> > console no message, ctrl+alt+esc also could not break into ddb, I may >> try >> > firewire/dcons, help it can get some >> > useful information. >> > >> > I really like to have a working freebsd on MacBookPro, anything I can >> > provide or any ideas? >> > >> > Cheers, >> > Huang Wen Hui >> > ___ >> > 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"
Re: Install 10.0-RC3 on MacBookPro Late 2013
Hi, I also install 11-amd64 snapshot 2 days ago, I remember AHCI is OK, but USB and random hang are still existed. I will confirm it later. Cheers, Huang Wen Hui. 2014/1/6 Adrian Chadd > Hi! > > Would you mind a recent 11-amd64 snapshot? Hans has committed a few > fixes to the driver recently. > > Thanks! > > > -a > > > On 5 January 2014 19:01, Huang Wen Hui wrote: > > Hi, > > > > I am trying to install FreeBSD on MacBookPro Late 2013, I got 3 main > > problems: > > > > 1. USB problem > > > > This MacBookPro model only have xhci controller, 10.0-RC3 and 9.2R not > > working, keyboard and touchpad not respond. Error messages are > > "xhci_do_command: Command timeout!" and "USB_ERR_TIMEOUT". > > I also try to set "hw.usb.xhci.msi=0", no lucky. > > > > But 9.1R is OK, I copy xhci*.* file from 9.1R to 10.0, with very small > > change, and > > xhci works under 10.0-RC3! > > > > dmesg in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/dmesg-10.0.txt > > vmstat -i in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/vmstat-10.0.txt > > pciconf in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/pciconf.txt > > > > dmesg in 10.0 + xhci of 9.1R: > > http://sw.gddsn.org.cn/freebsd/dmesg-10.0+9.1.txt > > vmstat -i in + xhci of 9.1R: > > http://sw.gddsn.org.cn/freebsd/vmstat-10.0+9.1.txt > > > > 2. AHCI timeout problem > > > > After booting, system quickly hit ahci timeout problem, I have to set > > "camcontrol tags ada0 -N 1". > > this can decrease timeout problem, but still happen when running heavy > IO. > > > > "hint.ahci.0.msi=0" seem to fix this problem, but ahci and xhci use same > > IRQ 16, this make 10.0+9.1xhci > > unstable:( Internal keyboard and touchpad not working, external keyboard > > and mouse working. > > > > vmstat -i in 10.0+9.1xhci with "hint.ahci.0.msi=0": > > http://sw.gddsn.org.cn/freebsd/vmstat-10.0+9.1+msi.txt > > camcontrol identify: http://sw.gddsn.org.cn/freebsd/cam-identify.txt > > smartctl: http://sw.gddsn.org.cn/freebsd/smartctl.txt > > > > 3. Random hang > > > > Sometimes the system(10.0+9.1xhci) hang without any message, keyboard, > > mouse and ping ping not respond. > > console no message, ctrl+alt+esc also could not break into ddb, I may try > > firewire/dcons, help it can get some > > useful information. > > > > I really like to have a working freebsd on MacBookPro, anything I can > > provide or any ideas? > > > > Cheers, > > Huang Wen Hui > > ___ > > 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"
Install 10.0-RC3 on MacBookPro Late 2013
Hi, I am trying to install FreeBSD on MacBookPro Late 2013, I got 3 main problems: 1. USB problem This MacBookPro model only have xhci controller, 10.0-RC3 and 9.2R not working, keyboard and touchpad not respond. Error messages are "xhci_do_command: Command timeout!" and "USB_ERR_TIMEOUT". I also try to set "hw.usb.xhci.msi=0", no lucky. But 9.1R is OK, I copy xhci*.* file from 9.1R to 10.0, with very small change, and xhci works under 10.0-RC3! dmesg in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/dmesg-10.0.txt vmstat -i in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/vmstat-10.0.txt pciconf in 10.0-RC3: http://sw.gddsn.org.cn/freebsd/pciconf.txt dmesg in 10.0 + xhci of 9.1R: http://sw.gddsn.org.cn/freebsd/dmesg-10.0+9.1.txt vmstat -i in + xhci of 9.1R: http://sw.gddsn.org.cn/freebsd/vmstat-10.0+9.1.txt 2. AHCI timeout problem After booting, system quickly hit ahci timeout problem, I have to set "camcontrol tags ada0 -N 1". this can decrease timeout problem, but still happen when running heavy IO. "hint.ahci.0.msi=0" seem to fix this problem, but ahci and xhci use same IRQ 16, this make 10.0+9.1xhci unstable:( Internal keyboard and touchpad not working, external keyboard and mouse working. vmstat -i in 10.0+9.1xhci with "hint.ahci.0.msi=0": http://sw.gddsn.org.cn/freebsd/vmstat-10.0+9.1+msi.txt camcontrol identify: http://sw.gddsn.org.cn/freebsd/cam-identify.txt smartctl: http://sw.gddsn.org.cn/freebsd/smartctl.txt 3. Random hang Sometimes the system(10.0+9.1xhci) hang without any message, keyboard, mouse and ping ping not respond. console no message, ctrl+alt+esc also could not break into ddb, I may try firewire/dcons, help it can get some useful information. I really like to have a working freebsd on MacBookPro, anything I can provide or any ideas? Cheers, Huang Wen Hui ___ 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: [Fwd: Re: libkse now running quite well on smp]
Huang wen hui ??: ??: Re: libkse now running quite well on smp ???: Huang wen hui <[EMAIL PROTECTED]> ??: Mon, 23 Jun 2003 08:13:54 +0800 ???: Khairil Yusof <[EMAIL PROTECTED]> Khairil Yusof ??: First of all thanks to Julian Elisher who gave hints on what might be wrong (userland/kernel), even though I was a blockhead for not enabling debugging options in the kernel before posting. It help me track down broken stuff in userland first. I hope I can give proper helpful debug info next time I get problems. Tested everything else throughly, before enabling kse one app at a time. Current uptime of 23hrs with these apps running with libkse.so.1, basically a usable Gnome 2.2 desktop environment: jdk1.4.1 (tomcat/netbeans) openoffice 1.03 evolution 1.4 mozilla-firebird 0.6 metacity xmms gnome-terminal nautilus vte dia gnome-panel gkrellm mysql40 (not heavilly tested yet) Wow.. with recent updates, you can now see the threads with top(8): Mozilla-Firebird 826 kaeru 96 0 40508K 32172K select 1 0:07 0.00% 0.00% MozillaFire 826 kaeru 96 0 40508K 32172K select 1 0:07 0.00% 0.00% MozillaFire 826 kaeru 20 0 40508K 32172K kserel 1 0:07 0.00% 0.00% MozillaFire 826 kaeru 20 0 40508K 32172K kserel 1 0:07 0.00% 0.00% MozillaFire Great work by the KSE team! Looks like we might get libpthreads as default on 5.2. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" just for a notes, with David Xu patch http://people.freebsd.org/~davidxu/kse_sig/, I can JBuilder9 with JDK1.4.1-p3. Before JBuilder9 always coredump with without :( the patch. --hwh ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: Re: libkse now running quite well on smp]
--- Begin Message --- Khairil Yusof 写道: >First of all thanks to Julian Elisher who gave hints on what might be >wrong (userland/kernel), even though I was a blockhead for not enabling >debugging options in the kernel before posting. It help me track down >broken stuff in userland first. I hope I can give proper helpful debug >info next time I get problems. > >Tested everything else throughly, before enabling kse one app at a time. >Current uptime of 23hrs with these apps running with libkse.so.1, >basically a usable Gnome 2.2 desktop environment: > >jdk1.4.1 (tomcat/netbeans) >openoffice 1.03 >evolution 1.4 >mozilla-firebird 0.6 >metacity >xmms >gnome-terminal >nautilus >vte >dia >gnome-panel >gkrellm >mysql40 (not heavilly tested yet) > >Wow.. with recent updates, you can now see the threads with top(8): > >Mozilla-Firebird >826 kaeru 96 0 40508K 32172K select 1 0:07 0.00% 0.00% MozillaFire >826 kaeru 96 0 40508K 32172K select 1 0:07 0.00% 0.00% MozillaFire >826 kaeru 20 0 40508K 32172K kserel 1 0:07 0.00% 0.00% MozillaFire >826 kaeru 20 0 40508K 32172K kserel 1 0:07 0.00% 0.00% MozillaFire > >Great work by the KSE team! Looks like we might get libpthreads as >default on 5.2. > > >___ >[EMAIL PROTECTED] mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > just for a notes, with David Xu patch http://people.freebsd.org/~davidxu/kse_sig/, I can JBuilder9 with JDK1.4.1-p3. Before JBuilder9 always coredump with the patch. --hwh --- End Message --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATA unable to map interrupt
hi, I can't boot recent CURRENT on PCM-5823. Is this the problem of ATA driver? Copyright (c) 1992-2003 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 SBOX #0: Sun Mar 2 12:21:09 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ab2000. Preloaded mfs_root "/boot/mfsroot" at 0xc0ab20a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 299237489 Hz CPU: Cyrix GXm (299.24-MHz 586-class CPU) Origin = "CyrixInstead" Id = 0x540 DIR=0x8244 Stepping=8 Revision=2 real memory = 131596288 (125 MB) avail memory = 116523008 (111 MB) Allocating major#253 to "net" Allocating major#252 to "pci" md0: Preloaded image 4423680 bytes at 0xc0678210 npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 3 entries at 0xc00fd9b0 pcib0: at pcibus 0 on motherboard pci0: on pcib0 fxp0: port 0xe000-0xe03f mem 0xe202-0xe203,0xe204-0xe2040fff irq 15 at device 11.0 on pci0 fxp0: Ethernet address 00:d0:c9:53:47:17 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0xe400-0xe43f mem 0xe200-0xe201,0xe2041000-0xe2041fff irq 11 at device 12.0 on pci0 fxp1: Ethernet address 00:d0:c9:53:47:18 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 18.0 on pci0 isa0: on isab0 pci0: at device 18.1 (no driver attached) atapci0: port 0xf000-0xf00f at device 18.2 on pci0 atapci0: unable to map interrupt pci0: at device 18.3 (no driver attached) pci0: at device 18.4 (no driver attached) ohci0: mem 0xe2045000-0xe2045fff irq 15 at device 19.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x0e11) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> db> trace Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc046a380 stack pointer = 0x10:0xc0ad49f8 frame pointer = 0x10:0xc0ad49fc code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 (swapper) kernel: type 12 trap, code=0 --hwh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATAPI CDROM drive not found
hi, I also got same problem under DELL GX260 using recent -CURRENT. This is older -CURRENT dmesg: Feb 20 15:30:26 hwh kernel: FreeBSD 5.0-CURRENT #10: Thu Feb 20 14:42:31 CST 2003 ... Feb 20 15:30:26 hwh kernel: ad0: 76293MB [155009/16/63] at ata0-master UDMA100 Feb 20 15:30:26 hwh kernel: acd0: CD-RW at ata1-master PIO4 Under my ThinkPad T23 I do not hit this problem. --hwh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Could not use pppd under -CURRENT
hi, I could not use pppd under -CURRENT, may be pppd driver could not link into kernel? I am sure I include ppp driver in system config file. # uname -a FreeBSD hwh.gddsn.org.cn 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Tue Sep 17 20:56:16 CST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HWH i386 # pppd pppd: This system lacks kernel support for PPP. To include PPP support in the kernel, please follow the steps detailed in the README.bsd file in the ppp-2.2 distribution. cut from my config file.: # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop # Network loopback device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) pls help! --hwh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Ugly fix patchset7 + XIM server(was: patchset 7 crash under -CURRENT+ chinese XIM Server.)
Huang wen hui дµÀ: >Hi, >I install JDK1.3.1-p7 + hostspot( compiler1) under -CURRENT(2002/07/27). >and use chinput as XIM Server. jdk works fine under >-STABLE or -CURRENT without starting XIM Server. but crash quickly under >-CURRENT + chinese XIM Server. hotspot vm also crash. >I recompile open-motif before build jdk. > > >%java_g -jar /usr/local/jdk1.3.1/demo/jfc/Notepad/Notepad.jar >SIGBUS 10* bus error > >Full thread dump Classic VM (1.3.1-p7-root-020727-22:30, green threads): >"AWT-Motif" (TID:0x28eecfa0, sys_thread_t:0x8407080, state:MW) prio=6 >at sun.awt.motif.MToolkit.run(Native Method) >at java.lang.Thread.run(Thread.java:484) >"SunToolkit.PostEventQueue-0" (TID:0x28eecb90, sys_thread_t:0x83d9680, >state:CW) prio=6 >at java.lang.Object.wait(Native Method) >at java.lang.Object.wait(Object.java:420) >at sun.awt.PostEventQueue.run(SunToolkit.java:491) >"AWT-EventQueue-0" (TID:0x28eecbb8, sys_thread_t:0x83d9480, state:CW) prio=6 >at java.lang.Object.wait(Native Method) >at java.lang.Object.wait(Object.java:420) >at java.awt.EventQueue.getNextEvent(EventQueue.java:260) >at >java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:106) >at >java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98) >at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) >at java.awt.EventDispatchThread.run(EventDispatchThread.java:85) >"Finalizer" (TID:0x28ebf530, sys_thread_t:0x80d9080, state:CW) prio=8 >at java.lang.Object.wait(Native Method) >at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108) >at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123) >at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162) >"Reference Handler" (TID:0x28ebf308, sys_thread_t:0x8096480, state:CW) >prio=10 >at java.lang.Object.wait(Native Method) >at java.lang.Object.wait(Object.java:420) >at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110) >"Signal dispatcher" (TID:0x28ebf338, sys_thread_t:0x8096280, state:CW) >prio=5 >"main" (TID:0x28ebf2f0, sys_thread_t:0x8054080, state:R) prio=5 >at sun.awt.motif.MToolkit.loadSystemColors(Native Method) >at java.awt.SystemColor.updateSystemColors(SystemColor.java:342) >at java.awt.SystemColor.(SystemColor.java:335) >at sun.awt.motif.MWindowPeer.init(MWindowPeer.java:109) >at sun.awt.motif.MFramePeer.(MFramePeer.java:53) >at sun.awt.motif.MToolkit.createFrame(MToolkit.java:138) >at java.awt.Frame.addNotify(Frame.java:353) >at javax.swing.plaf.metal.BumpBuffer.createComponent(MetalBumps.java:209) >at javax.swing.plaf.metal.BumpBuffer.(MetalBumps.java:147) >at javax.swing.plaf.metal.MetalBumps.createBuffer(MetalBumps.java:61) >at javax.swing.plaf.metal.MetalBumps.setBumpColors(MetalBumps.java:96) >at javax.swing.plaf.metal.MetalBumps.(MetalBumps.java:53) >at >javax.swing.plaf.metal.MetalScrollBarUI.installDefaults(MetalScrollBarUI.java:80) >at >javax.swing.plaf.basic.BasicScrollBarUI.installUI(BasicScrollBarUI.java:98) >at javax.swing.JComponent.setUI(JComponent.java:322) >at javax.swing.JScrollBar.updateUI(JScrollBar.java:189) >at javax.swing.JScrollBar.(JScrollBar.java:140) >at javax.swing.JScrollBar.(JScrollBar.java:155) >at javax.swing.JScrollPane$ScrollBar.(JScrollPane.java:635) >at javax.swing.JScrollPane.createVerticalScrollBar(JScrollPane.java:780) >at javax.swing.JScrollPane.(JScrollPane.java:242) >at javax.swing.JScrollPane.(JScrollPane.java:290) >at Notepad.(Notepad.java:95) >at Notepad.main(Notepad.java:128) >Monitor Cache Dump: >sun.awt.PostEventQueue@28EECB90/29059548: >Waiting to be notified: >"SunToolkit.PostEventQueue-0" (0x83d9680) >java.lang.Class@28ED7258/28F350B0: owner "main" (0x8054080) 1 entry >Waiting to enter: >"AWT-Motif" (0x8407080) >java.lang.ref.Reference$Lock@28EBF318/28EF53F8: >Waiting to be notified: >"Reference Handler" (0x8096480) >java.awt.EventQueue@28EECC58/290590C8: >Waiting to be notified: >"AWT-EventQueue-0" (0x83d9480) >java.lang.ref.ReferenceQueue$Lock@28EBF5B8/28EF5948: >Waiting to be notified: >"Finalizer" (0x80d9080) >java.awt.Component$AWTTreeLock@28ECA2E0/28F41470: owner "main" >(0x8054080) 1 entry >Registered Monitor Dump: >utf8 hash table: >JNI pinning lock: >JNI global reference lock: >BinClass lock: >Class linking lock: >System class loader lock: >Code rewrite lock: >Heap lock: >Monitor cache lock: owner "main" (0x8054080) 1 entry >Dynamic loading lock: >Monitor IO lock: >User signal monitor: >Waiting to be notified: >"Signal dispatcher" (0x8096280) >Child death mo
Crash -CURRENT BOX while jdk-p7 with gdb
I got a problem with jdk-p7+XIM input server. I try to use gdb to find out.
But if I run gdb on X11, -CURRENT(07/29) box will crash immediately:
gdb> file /usr/local/jdk1.3.1/bin/i386/green_threads/java_g
gdb> run -version
panic: blockable sleep lock (sleep mutex) sellck @
../../../kern/sys_generic.c:1178
Debugger("panic")
Stopped at Debugger+0x45: xchgl %ebx, in_Debugger.0
db>tr
Debugger(c043bffc) at Debugger+0x45
Panic(.) at panic+0x7c
witness_lock(...) at witness_lock+0x7f
_mtx_lock_flags(...) at _mxt_lock_flags+0x6b
selwakeup(...) at selwakeup+0x1e
ptcwakeup(...) at ptcwakeup+0x23
ptsstart(...) at ptsstart+0x2c
ttstart(...) at ttstart+0x16
tputchar(...) at tputchar+0x35
putchar(...) at putchar+0x55
kvprintf(...) at kvprintf+0x77
printf(...) at printf+0x43
userret(...) at userret+0xd9
ast(...) at ast+02b5
doreti_ast() at doreti_ast+0x1a
On text console, -CURRENT box will not crash. and I got msg:
gdb> file /usr/local/jdk1.3.1/bin/i386/green_threads/java_g
gdb> run -version
lock order reversal
1st 0xc44e0180 pipe mutex (pipe mutex) @ ../../../kern/sys_pipe.c:451
2nd 0xc04af6c0 sigio lock (sigio lock) @ ../../../kern/kern_sig.c:2014
failed to set signal flags properlyt for ast()
failed to set signal flags properlyt for ast()
failed to set signal flags properlyt for ast()
failed to set signal flags properlyt for ast()
failed to set signal flags properlyt for ast()
failed to set signal flags properlyt for ast()
failed to set signal flags properlyt for ast()
I comment printf in function "userret " in file
/usr/src/sys/kern/subr_trap.c
the box does not crash now. so It is not safe for using printf in
/usr/src/sys/kern/subr_trap.c ?
--hwh
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
a gcc3.1 bug ?
hi,
I used gcc3.1 from ports to compile jdk1.3.1-p7 hotspot, I got problem
in compiing /usr/src/lib/libc_r/uthread/pthread_private.h :
-
/* Default thread attributes: */
SCLASS struct pthread_attr pthread_attr_default
<--947
#ifdef GLOBAL_PTHREAD_PRIVATE
= { SCHED_RR, 0, TIMESLICE_USEC, PTHREAD_DEFAULT_PRIORITY,
PTHREAD_CREATE_RUNNING, PTHREAD_CREATE_JOINABLE, NULL, NULL, NULL,
PTHREAD_STACK_DEFAULT, -1 };
#else
;
#endif
/* Default mutex attributes: */
SCLASS struct pthread_mutex_attr pthread_mutexattr_default
#ifdef GLOBAL_PTHREAD_PRIVATE
= { PTHREAD_MUTEX_DEFAULT, PTHREAD_PRIO_NONE, 0, 0 };
#else
;
#endif
/* Default condition variable attributes: */
SCLASS struct pthread_cond_attr pthread_condattr_default
#ifdef GLOBAL_PTHREAD_PRIVATE
= { COND_TYPE_FAST, 0 };
#else
;
#endif
-
Compiling
/usr/ports/java/jdk13/work/hotspot1.3.1/build/linux/../../src/os_cpu/linux_i486/vm/os_linux_i486.cpp
In file included from
/usr/ports/java/jdk13/work/hotspot1.3.1/src/os_cpu/linux_i486/vm/os_linux_i486.cpp:41:
/usr/src/lib/libc_r/uthread/pthread_private.h:947: parse error before
`__null'
/usr/src/lib/libc_r/uthread/pthread_private.h:957: parse error before
`__null'
/usr/src/lib/libc_r/uthread/pthread_private.h:965: parse error before
`__null'
gmake[2]: *** [os_linux_i486.o] Error 1
gmake[2]: Leaving directory
`/usr/ports/java/jdk13/work/hotspot1.3.1/build/linux/linux_i486_core/jvmg'
gmake[1]: *** [the_vm] Error 2
gmake[1]: Leaving directory
`/usr/ports/java/jdk13/work/hotspot1.3.1/build/linux/linux_i486_core/jvmg'
gmake: *** [jvmgcore] Error 2
but if I change " pthread_attr pthread_attr_default " to other name, the
compiler will pass.
Does gcc31 have bug ?
--hwh
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
