Re: iwn crashing on 11n network
On Thu, Nov 9, 2017 at 2:53 AM, Zhihao Yuan wrote: > > The issues is here: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435 > > We observed same error from two cards, > > Intel Centrino Wireless-N 1000 > > and > > Intel Centrino Ultimate-N 6300 > > both on 11. > Ping? Is iwn driver still maintained? -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. ___ ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
iwn crashing on 11n network
The issues is here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435 We observed same error from two cards, Intel Centrino Wireless-N 1000 and Intel Centrino Ultimate-N 6300 both on 11. This card used to work in FreeBSD, where 11n is not supported, so it connects to an 11a network instead. Now it connects to nothing, even after -ht -- which will causes the whole system to reboot after lots of disconnects. -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. ___ ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: No sound with Realtek ALC269
On Feb 23, 2013 12:48 AM, "Shane Ambler" wrote: > I think you can test that with kldload snd_hda I can give it a try, but I don't see any drivers other than snd_hda can install hdaa0, which is what I already have. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Mounting from zfs... failed with error 2, again
Succeed. Thank you. -- Zhihao Yuan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Mounting from zfs... failed with error 2, again
On Feb 19, 2013 10:49 PM, "Xin Li" wrote: > Did you loaded zfs.ko? Yes, as in loader.conf, zfs_load. > Regenerate the zpool.cache with: > > zpool set cachefile=/mnt/boot/zfs/zpool.cache zdell > > Then sync; sleep 5; sync; then reboot. Without exporting the zpool? Anyway, I'll give it a try today. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Mounting from zfs... failed with error 2, again
On Feb 19, 2013 9:00 PM, "Xin Li" wrote: > Show the error message from root mount (plus what shows up after > ?). http://twitpic.com/c57t9b After ?, I see a list of gptids and names; nothing mentions 'zfs'. > It's pretty likely that you have a bad zpool.cache or bad > fstab configuration. I suppose I don't need a fstab, since I used the non-legacy plan, as shown in the RootOnZFS/9.0-RELEASE wiki page. The (/mnt)/boot/zfs/zpool.cache is copied from /tmp/zpool.cache, which was created by -o cachefile. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Mounting from zfs... failed with error 2, again
Yes, the real root which is mounted to / -- Zhihao Yuan On Feb 19, 2013 7:50 PM, "Xin LI" wrote: > 2 = ENOENT. Were you booting from zfs:zdell/ROOT? > > On Tue, Feb 19, 2013 at 2:15 PM, Zhihao Yuan wrote: > > There is no problem with everything that I can think of, and I tried > every > > thread in the mailing list/forum, and the only problem is, nothing works. > > > > http://twipic.com/c56lmz > > > > (taken from the shell on the install CD) > > > > -- > > Zhihao Yuan, ID lichray > > The best way to predict the future is to invent it. > > ___ > > 4BSD -- http://4bsd.biz/ > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > > > > -- > Xin LI https://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Mounting from zfs... failed with error 2, again
> http://twipic.com/c56lmz The URI should be http://twitpic.com/c56lmz -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Mounting from zfs... failed with error 2, again
There is no problem with everything that I can think of, and I tried every thread in the mailing list/forum, and the only problem is, nothing works. http://twipic.com/c56lmz (taken from the shell on the install CD) -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: A BSD-licensed internationalization solution?
libintl is LGPL, we don't have license issues against it. -- Zhihao Yuan On Sep 8, 2012 5:41 AM, "Mike Manilone" wrote: > Hi list, > > Here are many applications using GNU gettext to provide an > internationalized user interface. But I found that there isn't a > BSD-licensed gettext. (so BSD apps do not have internationalization?) > > Is there one? Then I can just switch from gettext to that. > > Sincerely, > Mike Manilone > __**_ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**stable<http://lists.freebsd.org/mailman/listinfo/freebsd-stable> > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@**freebsd.org > " > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: less and vi fail on file whose name begins with +
On Mon, Jul 16, 2012 at 12:03 AM, Thomas Mueller
wrote:
> I notice in my latest build of FreeBSD 9.0-STABLE (#11), a problem with less
> and vi with files whose name begins with +.
>
> These files occur in /var/db/pkg/(pkg-name)/
>
> For instance, if I cd /var/db/pkg/png-1.4.8
> and type
> less +DESC
> I get
>
> Missing filename ("less --help" for help)
>
> but if I type the filename with full path, or even
> less ./+DESC
> it works OK
>
> I also tried going to /tmp and
> echo abcdefg > +junk1.txt
> and the same bug with less showed up (no problem with echo).
>
> I tried vi instead of less, not really wanting to edit the file,
> and vi tried to open a temporary file on /tmp with a strange name.
>
> Has anybody noticed this bug? It affects i386 and amd64 at least.
It's not a bug... Unix shell regards arguments as same as options, so
the command with support + leading options has such a problem.
>
> I have no access to test on other architectures.
>
> If this bug is found, we no doubt want it to be squashed before 9.1-RELEASE.
>
> Tom
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
--
Zhihao Yuan, nickname lichray
The best way to predict the future is to invent it.
___
4BSD -- http://4bsd.biz/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Different features on different CPU cores?!
On Wed, May 30, 2012 at 9:43 AM, Olivier Smedts wrote: > 2012/5/30 Zhihao Yuan : >> OK... I see what happened: >> >> ~> cc a.c >> ~> gcc46 a.c >> In file included from a.c:1:0: >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd8.3/4.6.3/include/pmmintrin.h:32:3: >> error: #error "SSE3 instruction set not enabled" >> ~> clang a.c >> In file included from a.c:1: >> /usr/local/bin/../lib/clang/3.1/include/pmmintrin.h:28:2: error: "SSE3 >> instruction set not enabled" >> #error "SSE3 instruction set not enabled" >> ^ >> 1 error generated. >> ~> gcc46 -msse3 a.c >> ~> clang -msse3 a.c >> ~> >> >> So the chromium port does not define -msse3/-mssse3 explicitly, so it >> does not work with gcc46/clang. > > Isn't it /usr/share/mk/bsd.cpu.mk's job ? > # make -V CPUTYPE > core2 > # make -V MACHINE_CPU > ssse3 sse3 amd64 sse2 sse mmx > > I don't know if that's for the base system solely or if it works for > ports too, but at least on this computer I can compile chromium > 19.0.1084.52. Maybe you use CPUTYPE?=native, which is unsupported by > bsd.cpu.mk. Err, I put nothing on CPUTYPE. Long time ago, this variable only affects base. Thanks. > > -- > Olivier Smedts _ > ASCII ribbon campaign ( ) > e-mail: oliv...@gid0.org - against HTML email & vCards X > www: http://www.gid0.org - against proprietary attachments / \ > > "Il y a seulement 10 sortes de gens dans le monde : > ceux qui comprennent le binaire, > et ceux qui ne le comprennent pas." -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Different features on different CPU cores?!
On Wed, May 30, 2012 at 9:25 AM, Michael Butler wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 05/30/12 10:15, Zhihao Yuan wrote: >> Hi, >> >> Today I want to compile the latest www/chromium, and I found that I >> encountered some SSSE3 problems, with either gcc46/clang, and I found >> that this new version requires (S)SSE3 support. >> >> My CPU is a Intel i5 M 520, which suppose to support these. But when >> I'm checking the CPU features, I see: >> >> CPU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.02-MHz K8-class CPU) >> Origin = "GenuineIntel" Id = 0x20652 Family = 6 Model = 25 Stepping = 2 >> Features=0xbfebfbff> OV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> >> Features2=0x298e3ff> ,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AESNI> >> >> What? Different features on different cores? Is it my CPU's problem or >> FreeBSD's problem? >> > You are misreading this .. they ran out of bits in one word to describe > the available features so they added another word 'features2' to > describe the rest. These capabilities apply to both cores, OK... I see what happened: ~> cc a.c ~> gcc46 a.c In file included from a.c:1:0: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd8.3/4.6.3/include/pmmintrin.h:32:3: error: #error "SSE3 instruction set not enabled" ~> clang a.c In file included from a.c:1: /usr/local/bin/../lib/clang/3.1/include/pmmintrin.h:28:2: error: "SSE3 instruction set not enabled" #error "SSE3 instruction set not enabled" ^ 1 error generated. ~> gcc46 -msse3 a.c ~> clang -msse3 a.c ~> So the chromium port does not define -msse3/-mssse3 explicitly, so it does not work with gcc46/clang. > > imb > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (FreeBSD) > > iEYEARECAAYFAk/GLdwACgkQQv9rrgRC1JI9vgCdHoHEdEV8V+SawdSI+iD8TFc5 > XyoAniiyJ6kkZZ/AjFhgTgXLrvJvdB/k > =y05w > -END PGP SIGNATURE- > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Different features on different CPU cores?!
Hi, Today I want to compile the latest www/chromium, and I found that I encountered some SSSE3 problems, with either gcc46/clang, and I found that this new version requires (S)SSE3 support. My CPU is a Intel i5 M 520, which suppose to support these. But when I'm checking the CPU features, I see: CPU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.02-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x20652 Family = 6 Model = 25 Stepping = 2 Features=0xbfebfbff Features2=0x298e3ff What? Different features on different cores? Is it my CPU's problem or FreeBSD's problem? -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
A problem may relate to USB 3.0 (xhci)
Hi, I found a problem *may* relate to the xhci driver. My laptop, HP Elitebook 8540w, has two USB 3.0 interfaces. After the laptop has been used for several days, the USB 3.0 interfaces does not work anymore; I can only use them to charge mobile devices. A restart will reset everything. Since the problem is reproducible, I found the following in my /var/log/messages: Sep 12 21:34:46 compaq kernel: ugen1.2: at usbus1 (disconnected) Sep 12 21:34:46 compaq kernel: umass1: at uhub1, port 3, addr 1 (disconnected) Sep 12 21:34:46 compaq kernel: (da1:umass-sim1:1:0:0): lost device Sep 12 21:34:46 compaq kernel: (da1:umass-sim1:1:0:0): removing device entry Sep 12 21:34:54 compaq kernel: ugen1.2: at usbus1 (disconnected) And after that, ugen1.2 can no longer be recognized. ~> usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.3: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen2.4: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON It just disappeared. ugen1.1 should be another USB 3.0 interface, but after one of them is down, none of them works, and message ugen1.2: at usbus1 (disconnected) just keep shown when I plug/unplug USB devices. My FreeBSD is FreeBSD compaq.yuetime 8.2-STABLE FreeBSD 8.2-STABLE #8 r225370: Sun Sep 4 05:14:37 CDT 2011 lichray@compaq.yuetime:/usr/obj/home/lichray/devel/freebsd-stable/sys/HOUKAGO amd64 This may be a hardware problem btw, since I only used FreeBSD on this laptop, so I can't say whether other USB stacks work correctly. And in the most cases I plug in my Samsung Exhibit 4G. As you known, after an Android device has been plugged in, you need to select "Connect to USB" manually, which generates: Sep 7 15:04:12 compaq kernel: ugen1.2: at usbus1 Sep 7 15:04:12 compaq kernel: umass1: on usbus1 Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Sep 7 15:04:14 compaq kernel: (probe0:umass-sim1:1:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Sep 7 15:04:14 compaq kernel: da1 at umass-sim1 bus 1 scbus6 target 0 lun 0 Sep 7 15:04:14 compaq kernel: da1: Removable Direct Access SCSI-2 device Sep 7 15:04:14 compaq kernel: da1: 40.000MB/s transfers Sep 7 15:04:14 compaq kernel: da1: Attempt to query device size failed: NOT READY, Medium not present for each time. (Btw, I hope gpart/devfs can detect the medium availability change on USB :) This makes the device not that "regular". So the problem may also caused by the device. -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Fwd: Again, snd_hda headphones problem
Hi, Sorry about to post this on two freebsd- mailing lists. This problem makes me unable to use external headphones/speakers, which is a very serious problem. I pasted a full verbose boot log here: http://lists.freebsd.org/pipermail/freebsd-multimedia/2011-August/012389.html -- Forwarded message -- From: Zhihao Yuan Date: Wed, Aug 3, 2011 at 1:43 PM Subject: Again, snd_hda headphones problem To: freebsd-multime...@freebsd.org Hi, I posted this message on FreeBSD forum, but got no response. So I'm seeking some help here. I bought a laptop, HP Elitebook 8540w. ~> uname -a FreeBSD compaq.yuetime 8.2-STABLE FreeBSD 8.2-STABLE #4 r224501: Fri Jul 29 22:28:38 CDT 2011 lichray@compaq.yuetime:/usr/obj/home/lichray/devel/freebsd-stable/sys/HOUKAGO amd64 I have already set up the default_unit: ~> cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: (play) pcm1: (play) pcm2: (play) pcm3: (play) pcm4: (play/rec) default pcm5: (play) pindump: hdac1: Dumping AFG cad=0 nid=1 pins: hdac1: nid 10 0x2121101f as 1 seq 15 Headphones Jack jack 1 loc 33 color Black misc 0 hdac1: Caps: OUT HP Sense: 0x hdac1: nid 11 0x03a1102e as 2 seq 14 Mic Jack jack 1 loc 3 color Black misc 0 hdac1: Caps: IN VREF Sense: 0x hdac1: nid 12 0x90a70120 as 2 seq 0 Mic Fixed jack 7 loc 16 color Unknown misc 1 hdac1: Caps: IN VREF Sense: 0x hdac1: nid 13 0x90170110 as 1 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1 hdac1: Caps: OUT Sense: 0x hdac1: nid 14 0x21811040 as 4 seq 0 Line-in Jack jack 1 loc 33 color Black misc 0 [DISABLED] hdac1: Caps: IN VREF Sense: 0x hdac1: nid 15 0x03211030 as 3 seq 0 Headphones Jack jack 1 loc 3 color Black misc 0 hdac1: Caps: OUT Sense: 0x hdac1: nid 20 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: IN OUT hdac1: nid 24 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: IN hdac1: nid 25 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: IN hdac1: nid 30 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: OUT hdac1: nid 31 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: OUT EAPD hdac1: nid 32 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: OUT hdac1: NumGPIO=8 NumGPO=0 NumGPI=0 GPIWake=1 GPIUnsol=1 hdac1: GPIO: data=0x enable=0x direction=0x hdac1: wake=0x unsol=0x sticky=0x And the sound comes from the internal speaker, and the internal record works. But the sound does not work on the headphones. I read many posts and the snd_hda(4), and I know I need to bind the headphones and the internal speaker to the same as, and I need to do the same on output. But I don't know which device is which, and I just don't know how to deal with the seq. Please help me if you are pro on this. -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS boot inside on the second partition inside a slice
I finally redo everything with GPT-based solution. At the same time, I found a problem with zpool.cache and I fixed with: http://forums.freebsd.org/showthread.php?t=4185 zpool.cache will be changed after you exported the zpool... Anyway, now I'm OK with my freebsd-only box, again. On Fri, Jun 17, 2011 at 9:18 PM, Zhihao Yuan wrote: > If this problem can not be solved, I probably have to redo everything > to use GPT-based solution and lose my Windows. > > On Fri, Jun 17, 2011 at 12:37 PM, John Baldwin wrote: >> On Friday, June 17, 2011 1:06:22 pm Henri Hennebert wrote: >>> On 06/16/2011 19:35, John Baldwin wrote: >>> > On Thursday, June 16, 2011 8:45:41 am Zhihao Yuan wrote: >>> >> Exactly. The MFCed ZFSv28 is different from any patch maintained by >>> >> mm@. Maybe some untested changes involved. >>> > >>> > Can you try reverting this change: >>> > >>> > Author: jhb >>> > Date: Thu Apr 28 17:44:24 2011 >>> > New Revision: 221177 >>> > URL: http://svn.freebsd.org/changeset/base/221177 >>> > >>> > Log: >>> > Due to space constraints, the UFS boot2 and boot1 use an evil hack where >>> > boot2 calls back into boot1 to perform disk reads. The ZFS MBR boot >>> > blocks >>> > do not have the same space constraints, so remove this hack for ZFS. >>> > While here, remove commented out code to support C/H/S addressing from >>> > zfsldr. The ZFS and GPT bootstraps always just use EDD LBA addressing. >>> > >>> > MFC after: 2 weeks >>> > >>> > Modified: >>> > head/sys/boot/i386/boot2/Makefile >>> > head/sys/boot/i386/common/drv.c >>> > head/sys/boot/i386/zfsboot/Makefile >>> > head/sys/boot/i386/zfsboot/zfsldr.S >>> > >>> I try with this revision (221177) reverted to no avail: >>> same error - 'read error' >> >> Hmm, ok. No other ideas off the top of my head. >> >> -- >> John Baldwin >> > > > > -- > Zhihao Yuan, nickname lichray > The best way to predict the future is to invent it. > ___ > 4BSD -- http://4bsd.biz/ > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS boot inside on the second partition inside a slice
If this problem can not be solved, I probably have to redo everything to use GPT-based solution and lose my Windows. On Fri, Jun 17, 2011 at 12:37 PM, John Baldwin wrote: > On Friday, June 17, 2011 1:06:22 pm Henri Hennebert wrote: >> On 06/16/2011 19:35, John Baldwin wrote: >> > On Thursday, June 16, 2011 8:45:41 am Zhihao Yuan wrote: >> >> Exactly. The MFCed ZFSv28 is different from any patch maintained by >> >> mm@. Maybe some untested changes involved. >> > >> > Can you try reverting this change: >> > >> > Author: jhb >> > Date: Thu Apr 28 17:44:24 2011 >> > New Revision: 221177 >> > URL: http://svn.freebsd.org/changeset/base/221177 >> > >> > Log: >> > Due to space constraints, the UFS boot2 and boot1 use an evil hack where >> > boot2 calls back into boot1 to perform disk reads. The ZFS MBR boot >> > blocks >> > do not have the same space constraints, so remove this hack for ZFS. >> > While here, remove commented out code to support C/H/S addressing from >> > zfsldr. The ZFS and GPT bootstraps always just use EDD LBA addressing. >> > >> > MFC after: 2 weeks >> > >> > Modified: >> > head/sys/boot/i386/boot2/Makefile >> > head/sys/boot/i386/common/drv.c >> > head/sys/boot/i386/zfsboot/Makefile >> > head/sys/boot/i386/zfsboot/zfsldr.S >> > >> I try with this revision (221177) reverted to no avail: >> same error - 'read error' > > Hmm, ok. No other ideas off the top of my head. > > -- > John Baldwin > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS boot inside on the second partition inside a slice
I wish I can get a binary version... Because I have no working FreeBSD box now On Thu, Jun 16, 2011 at 12:35 PM, John Baldwin wrote: > On Thursday, June 16, 2011 8:45:41 am Zhihao Yuan wrote: >> Exactly. The MFCed ZFSv28 is different from any patch maintained by >> mm@. Maybe some untested changes involved. > > Can you try reverting this change: > > Author: jhb > Date: Thu Apr 28 17:44:24 2011 > New Revision: 221177 > URL: http://svn.freebsd.org/changeset/base/221177 > > Log: > Due to space constraints, the UFS boot2 and boot1 use an evil hack where > boot2 calls back into boot1 to perform disk reads. The ZFS MBR boot blocks > do not have the same space constraints, so remove this hack for ZFS. > While here, remove commented out code to support C/H/S addressing from > zfsldr. The ZFS and GPT bootstraps always just use EDD LBA addressing. > > MFC after: 2 weeks > > Modified: > head/sys/boot/i386/boot2/Makefile > head/sys/boot/i386/common/drv.c > head/sys/boot/i386/zfsboot/Makefile > head/sys/boot/i386/zfsboot/zfsldr.S > > -- > John Baldwin > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS boot inside on the second partition inside a slice
Exactly. The MFCed ZFSv28 is different from any patch maintained by mm@. Maybe some untested changes involved. On Thu, Jun 16, 2011 at 7:36 AM, Henri Hennebert wrote: > On 06/16/2011 07:32, Zhihao Yuan wrote: >> >> I just redo everything, and changed the order of freebsd-zfs and >> freebsd-swap. The "Read error" still happens! > > Just a me too. > > Everything was working great with zfsboot from 8.2-RELEASE + a patch > (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/153552). > > As I update to 8.2-STABLE after v28 MFC, I have to write a new zfsboot to be > allowed to upgrade my pool. I get the "Read Error" after that. > > PS - same comfig, a netboot with windows7 on first partition - so I can't > switch to gpt. > > Henri >> >> On Wed, Jun 15, 2011 at 8:07 PM, Zhihao Yuan wrote: >>> >>> On Wed, Jun 15, 2011 at 7:58 PM, Xin LI wrote: >>>> >>>> -BEGIN PGP SIGNED MESSAGE- >>>> Hash: SHA256 >>>> >>>> On 06/15/11 17:42, Zhihao Yuan wrote: >>>>> >>>>> Hi, >>>>> >>>>> I configured my disk layout according to >>>>> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition >>>>> >>>>> But I swapped the order of the freebsd-zfs and freebsd-swap. The 4.0G >>>>> freebsd-swap partition appears first inside the slice. >>>>> After that, I write zfsboot on both ada0s2 and ada0s2b, but the boot0 >>>>> gives me a "Read error". >>>> >>>> Where did your second slice start? There can be a lot of reasons why it >>>> gives Read error. >>> >>> After an NTFS partition of 12GB. >>> This should be the problem with zfsboot, because if I use sysinstall >>> to install a bootmgr, the boot gives me a "not UFS" error, which means >>> the boot0 is done (am I right?). >>> >>>> >>>> I personally recommend using GPT scheme instead of MBR, as you have a >>>> dedicated partition for gptzfsboot, which is much cleaner than this >>>> approach. >>>> >>> >>> Yeah, yeah, I agree. I should not plan to play Windows games. >>> >>>> Cheers, >>>> - -- >>>> Xin LI http://www.delphij.net/ >>>> FreeBSD - The Power to Serve! Live free or die >>>> -BEGIN PGP SIGNATURE- >>>> Version: GnuPG v2.0.17 (FreeBSD) >>>> >>>> iQEcBAEBCAAGBQJN+VUrAAoJEATO+BI/yjfBpksH/2ZswQ+ogdDpYwvhRIjJaqLs >>>> NEl8FtC2Ua+c3F2sNwrLK5a/fn/LL+jPAXndvuQdxOaz41Iqtnt8w1i9Dz5ATkva >>>> T+i0fnRVwXFqjrlRTWK+ODtNtrhI2/7ECAIfOOLNhaiJnPRrJJgvxJ6V5W+/N+l7 >>>> Lt4yMp6hGbhO/9Yp2UoaQuUThOTz+dKNZGECd1nLT+ooHbTPhBvjii080hHowNl6 >>>> Ef+JBaEng2NbRJPxYWrRwz6R7A44RDXvrKzn5w/TuUa+4fYrS25EZxygzIh3xjFX >>>> 2ILP25yabJ+Vw5o8bFCsJ3ExbEfq0PnfROHanRSdTjMDra27dGY9JZKyytE+Ykc= >>>> =D5+X >>>> -END PGP SIGNATURE- >>>> ___ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to >>>> "freebsd-stable-unsubscr...@freebsd.org" >>>> >>> >>> >>> >>> -- >>> Zhihao Yuan, nickname lichray >>> The best way to predict the future is to invent it. >>> ___ >>> 4BSD -- http://4bsd.biz/ >>> >> >> >> > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS boot inside on the second partition inside a slice
I just redo everything, and changed the order of freebsd-zfs and freebsd-swap. The "Read error" still happens! On Wed, Jun 15, 2011 at 8:07 PM, Zhihao Yuan wrote: > On Wed, Jun 15, 2011 at 7:58 PM, Xin LI wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 06/15/11 17:42, Zhihao Yuan wrote: >>> Hi, >>> >>> I configured my disk layout according to >>> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition >>> >>> But I swapped the order of the freebsd-zfs and freebsd-swap. The 4.0G >>> freebsd-swap partition appears first inside the slice. >>> After that, I write zfsboot on both ada0s2 and ada0s2b, but the boot0 >>> gives me a "Read error". >> >> Where did your second slice start? There can be a lot of reasons why it >> gives Read error. > > After an NTFS partition of 12GB. > This should be the problem with zfsboot, because if I use sysinstall > to install a bootmgr, the boot gives me a "not UFS" error, which means > the boot0 is done (am I right?). > >> >> I personally recommend using GPT scheme instead of MBR, as you have a >> dedicated partition for gptzfsboot, which is much cleaner than this >> approach. >> > > Yeah, yeah, I agree. I should not plan to play Windows games. > >> Cheers, >> - -- >> Xin LI http://www.delphij.net/ >> FreeBSD - The Power to Serve! Live free or die >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v2.0.17 (FreeBSD) >> >> iQEcBAEBCAAGBQJN+VUrAAoJEATO+BI/yjfBpksH/2ZswQ+ogdDpYwvhRIjJaqLs >> NEl8FtC2Ua+c3F2sNwrLK5a/fn/LL+jPAXndvuQdxOaz41Iqtnt8w1i9Dz5ATkva >> T+i0fnRVwXFqjrlRTWK+ODtNtrhI2/7ECAIfOOLNhaiJnPRrJJgvxJ6V5W+/N+l7 >> Lt4yMp6hGbhO/9Yp2UoaQuUThOTz+dKNZGECd1nLT+ooHbTPhBvjii080hHowNl6 >> Ef+JBaEng2NbRJPxYWrRwz6R7A44RDXvrKzn5w/TuUa+4fYrS25EZxygzIh3xjFX >> 2ILP25yabJ+Vw5o8bFCsJ3ExbEfq0PnfROHanRSdTjMDra27dGY9JZKyytE+Ykc= >> =D5+X >> -END PGP SIGNATURE- >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> > > > > -- > Zhihao Yuan, nickname lichray > The best way to predict the future is to invent it. > ___ > 4BSD -- http://4bsd.biz/ > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS boot inside on the second partition inside a slice
On Wed, Jun 15, 2011 at 7:58 PM, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 06/15/11 17:42, Zhihao Yuan wrote: >> Hi, >> >> I configured my disk layout according to >> http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition >> >> But I swapped the order of the freebsd-zfs and freebsd-swap. The 4.0G >> freebsd-swap partition appears first inside the slice. >> After that, I write zfsboot on both ada0s2 and ada0s2b, but the boot0 >> gives me a "Read error". > > Where did your second slice start? There can be a lot of reasons why it > gives Read error. After an NTFS partition of 12GB. This should be the problem with zfsboot, because if I use sysinstall to install a bootmgr, the boot gives me a "not UFS" error, which means the boot0 is done (am I right?). > > I personally recommend using GPT scheme instead of MBR, as you have a > dedicated partition for gptzfsboot, which is much cleaner than this > approach. > Yeah, yeah, I agree. I should not plan to play Windows games. > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.17 (FreeBSD) > > iQEcBAEBCAAGBQJN+VUrAAoJEATO+BI/yjfBpksH/2ZswQ+ogdDpYwvhRIjJaqLs > NEl8FtC2Ua+c3F2sNwrLK5a/fn/LL+jPAXndvuQdxOaz41Iqtnt8w1i9Dz5ATkva > T+i0fnRVwXFqjrlRTWK+ODtNtrhI2/7ECAIfOOLNhaiJnPRrJJgvxJ6V5W+/N+l7 > Lt4yMp6hGbhO/9Yp2UoaQuUThOTz+dKNZGECd1nLT+ooHbTPhBvjii080hHowNl6 > Ef+JBaEng2NbRJPxYWrRwz6R7A44RDXvrKzn5w/TuUa+4fYrS25EZxygzIh3xjFX > 2ILP25yabJ+Vw5o8bFCsJ3ExbEfq0PnfROHanRSdTjMDra27dGY9JZKyytE+Ykc= > =D5+X > -END PGP SIGNATURE- > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ZFS boot inside on the second partition inside a slice
Hi, I configured my disk layout according to http://wiki.freebsd.org/RootOnZFS/ZFSBootPartition But I swapped the order of the freebsd-zfs and freebsd-swap. The 4.0G freebsd-swap partition appears first inside the slice. After that, I write zfsboot on both ada0s2 and ada0s2b, but the boot0 gives me a "Read error". What should do? Thanks. -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HEADS UP: ZFS v28 merged to 8-STABLE
Thanks. Everything works fine. 2011/6/6 Lystopad Olexandr : > Hello, Martin Matuska! > > On Mon, Jun 06, 2011 at 12:53:11PM +0200 > m...@freebsd.org wrote about "HEADS UP: ZFS v28 merged to 8-STABLE": >> Hi, >> >> I have merged ZFS version 28 to 8-STABLE (revision 222741) > > finally! Thanks! > > My home server works ok with this update. > > -- > Lystopad Olexandr > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [ZFSv28]gtpzfsboot fails to boot ZFSv28 0511
On Wed, Jun 1, 2011 at 10:29 AM, Zhihao Yuan wrote: > On Wed, Jun 1, 2011 at 3:36 AM, Olivier Smedts wrote: >> 2011/6/1 Jeremy Chadwick : >>> On Tue, May 31, 2011 at 08:15:35PM -0500, Zhihao Yuan wrote: >>>> I met this problem, which is serious. I need some help to recovered >>>> the system, after that I'll show the photos about the error screen. >>>> >>>> I used the ZFSv28 patch maintained by mm@ before, and I have a >>>> backuped working kernel. I need a LiveCD/memstick to boot the system >>>> and recover it. But after I burned the 9.0-current image to memstick, >>>> I found that it keeps giving me kernel panic when booting! How can I >>>> find a LiveFS with ZFSv28 support? Thanks. >>> >>> The closest thing I can think of is this: >>> >>> http://mfsbsd.vx.sk/ >> >> I had a problem with latest gptzfsboot under 9-CURRENT with my v28 >> pool, and restored the old gptzfsboot I had on a snapshot with "gpart >> bootcode" thanks to mfsbsd. > > mfsbsd seems to an installation image. Can I use it to restore my old kernel? Thanks to your help. I have recovered my system. FML, I can do nothing but playing games with Windows these days. The problem should be on the recent update to loader and zfsloader (loader.old and zfsloader.old present). I uploaded the screenshots when fail to boot at https://picasaweb.google.com/lh/photo/-SRBhEJvlslmLkn4JglZ0A5tpALgZSii5oHUBfoPNZY?feat=directlink > >> >>> Except: >>> >>> 1) The ISOs there don't claim to be "LiveFS"; I don't know if they are. >>> 2) There's no memory stick image available, only ISOs, >>> 3) They're 8.2-RELEASE with ZFSv28 patches, not 9.0-CURRENT. I don't >>> know the implications of this. >>> >>> Best to ask mm@. >>> >>> -- >>> | Jeremy Chadwick j...@parodius.com | >>> | Parodius Networking http://www.parodius.com/ | >>> | UNIX Systems Administrator Mountain View, CA, USA | >>> | Making life hard for others since 1977. PGP 4BD6C0CB | >>> >>> ___ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >>> >> >> >> >> -- >> Olivier Smedts _ >> ASCII ribbon campaign ( ) >> e-mail: oliv...@gid0.org - against HTML email & vCards X >> www: http://www.gid0.org - against proprietary attachments / \ >> >> "Il y a seulement 10 sortes de gens dans le monde : >> ceux qui comprennent le binaire, >> et ceux qui ne le comprennent pas." >> > > > > -- > Zhihao Yuan, nickname lichray > The best way to predict the future is to invent it. > ___ > 4BSD -- http://4bsd.biz/ > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [ZFSv28]gtpzfsboot fails to boot ZFSv28 0511
On Wed, Jun 1, 2011 at 3:36 AM, Olivier Smedts wrote: > 2011/6/1 Jeremy Chadwick : >> On Tue, May 31, 2011 at 08:15:35PM -0500, Zhihao Yuan wrote: >>> I met this problem, which is serious. I need some help to recovered >>> the system, after that I'll show the photos about the error screen. >>> >>> I used the ZFSv28 patch maintained by mm@ before, and I have a >>> backuped working kernel. I need a LiveCD/memstick to boot the system >>> and recover it. But after I burned the 9.0-current image to memstick, >>> I found that it keeps giving me kernel panic when booting! How can I >>> find a LiveFS with ZFSv28 support? Thanks. >> >> The closest thing I can think of is this: >> >> http://mfsbsd.vx.sk/ > > I had a problem with latest gptzfsboot under 9-CURRENT with my v28 > pool, and restored the old gptzfsboot I had on a snapshot with "gpart > bootcode" thanks to mfsbsd. mfsbsd seems to an installation image. Can I use it to restore my old kernel? > >> Except: >> >> 1) The ISOs there don't claim to be "LiveFS"; I don't know if they are. >> 2) There's no memory stick image available, only ISOs, >> 3) They're 8.2-RELEASE with ZFSv28 patches, not 9.0-CURRENT. I don't >> know the implications of this. >> >> Best to ask mm@. >> >> -- >> | Jeremy Chadwick j...@parodius.com | >> | Parodius Networking http://www.parodius.com/ | >> | UNIX Systems Administrator Mountain View, CA, USA | >> | Making life hard for others since 1977. PGP 4BD6C0CB | >> >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> > > > > -- > Olivier Smedts _ > ASCII ribbon campaign ( ) > e-mail: oliv...@gid0.org - against HTML email & vCards X > www: http://www.gid0.org - against proprietary attachments / \ > > "Il y a seulement 10 sortes de gens dans le monde : > ceux qui comprennent le binaire, > et ceux qui ne le comprennent pas." > -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[ZFSv28]gtpzfsboot fails to boot ZFSv28 0511
Hi, I met this problem, which is serious. I need some help to recovered the system, after that I'll show the photos about the error screen. I used the ZFSv28 patch maintained by mm@ before, and I have a backuped working kernel. I need a LiveCD/memstick to boot the system and recover it. But after I burned the 9.0-current image to memstick, I found that it keeps giving me kernel panic when booting! How can I find a LiveFS with ZFSv28 support? Thanks. -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cleaning temporary build tree failed
/usr/src is controlled by root. Use `sudo` to perform the system management related works. On Sat, Apr 9, 2011 at 2:25 AM, David Marec wrote: > Hi guys. > > > Since the release of FreeBSD 8.2, building world fails on the following > error: > > > <--> > david:/home/david#cd /usr/src > david:/usr/src#make -j4 buildworld && make kernel > -- >>>> World build started on Sat Apr 9 09:16:50 CEST 2011 > -- > -- >>>> Rebuilding the temporary build tree > -- > rm -rf /usr/obj/usr/src/tmp > rm -rf /usr/obj/usr/src/lib32 > rm: /usr/obj/usr/src/lib32/usr/lib32/libc.so.7: Operation not permitted > rm: /usr/obj/usr/src/lib32/usr/lib32/libcrypt.so.5: Operation not permitted > rm: /usr/obj/usr/src/lib32/usr/lib32/libthr.so.3: Operation not permitted > rm: /usr/obj/usr/src/lib32/usr/lib32/librt.so.1: Operation not permitted > rm: /usr/obj/usr/src/lib32/usr/lib32: Directory not empty > rm: /usr/obj/usr/src/lib32/usr: Directory not empty > rm: /usr/obj/usr/src/lib32: Directory not empty > *** Error code 1 > 1 error > *** Error code 2 > 1 error > david:/usr/src#ls -lo /usr/obj/usr/src/lib32/usr/lib32/ > total 1262 > -r--r--r-- 1 root wheel schg 1143468 22 mar 21:19 libc.so.7 > -r--r--r-- 1 root wheel schg 32060 22 mar 21:19 libcrypt.so.5 > -r--r--r-- 1 root wheel schg 16412 22 mar 21:22 librt.so.1 > -r--r--r-- 1 root wheel schg 76412 22 mar 21:20 libthr.so.3 > <--> > > Im a running FreeBSD 8.2-Stable for amd64. > > So, before building world, i have to change the flags for the files above. > There was no need to do this before. > > > Any idea to get rid of this issue ? > > > -- > Cordialement, > -- > David Marec: http://user.lamaiziere.net/david/Site/ > http://www.freebsd.org/fr/ http://www.diablotins.org/ > > > > _______ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FYI: Userspace DTrace MFC to stable/8
On Wed, Mar 30, 2011 at 3:56 AM, Nikolay Denev wrote: > > On Mar 30, 2011, at 11:24 AM, Zhihao Yuan wrote: > > On Wed, Mar 30, 2011 at 2:57 AM, Nikolay Denev wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > On Mar 1, 2011, at 12:10 PM, Kostik Belousov wrote: > > On Tue, Mar 01, 2011 at 11:03:07AM +0200, Nikolay Denev wrote: > > On 1 Mar, 2011, at 01:33 , Robert Watson wrote: > > Dear all: > > Just an FYI that I've gone ahead and merged userspace DTrace support to > FreeBSD 8.x from 9.x. While it appeared to pass build tests locally, boot > and run, etc, this is a non-trivial merge, and it's possible I've messed up. > If so, apologies in advance, and I'll try to resolve any problems as > quickly as I can! > > And of course, many thanks go to Rui Paulo, who did the port of userspace > DTrace to FreeBSD 9.x with support from the FreeBSD Foundation! > > Thanks, > > Robert N M Watson > > Computer Laboratory > > University of Cambridge > > > That's great news! Many thanks to all that made this possible! > > I have a quick question though, now do I have to rebuild my world with > "WITH_CTF" ? > > I'm asking because I did that by mistake some months ago on a RELENG_8 > machine, and > > the world that was built had some problems, like gcc giving segfault 11 > while compiling world or some ports. > > It was a known issue that ctfconvert (I think it is ctfconvert) damages > > statically linked binaries. Most likely, it was not fixed yet. > > I can confirm this is not fixed yet. > > I have two STABLE-8 machines which had their world rebuilt with WITH_CTF > option, > > and now I'm unable to rebuild the world as both machines fail with > Segmentation Fault: 11 on exactly the same place : > > mkdep -f .depend -a -I/usr/obj/usr/src/tmp/legacy/usr/include > -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib > -I/usr/src/gnu/usr.bin/gperf > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/gen-perf.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/hash-table.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/iterator.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/key-list.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/list-node.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/new.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/options.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/read-line.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/trace.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/vectors.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/version.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib/hash.cc > > cc: Internal error: Segmentation fault: 11 (program cc1plus) > > Please submit a full bug report. > > See http://gcc.gnu.org/bugs.html> for instructions. > > mkdep: compile failed > > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/gperf. > > *** Error code 1 > > Stop in /usr/src. > > *** Error code 1 > > Stop in /usr/src. > > *** Error code 1 > > Stop in /usr/src. > > I have met this problem before. WITH_CTF on world is not required to > use DTrace, and it seems that the gcc is broken. If can get a working > gcc4.2 in the base system, you are ucky. Or, you can download a base > system for the FreeBSD FTP site, and install it to a temp path, then > copy the gcc binary to /usr/bin. > > > Yes, but since now the userspace DTrace portions have been MFCed I believe > one needs a world WITH_CTF to use it? > Anyways, I've already fixed my installations, exactly by downloading a ISO > image and extracting only the > GCC stuff. > Regards, > Nikolay WITH_CTF adds the DTrace provider support to a program (if I was wrong, please correct me). So far, DTrace on FreeBSD is intended for kernel tracing. Some day in the future, we may have DTrace support for the userland tools (we do have userland providers, but they are used to debug a program in general). -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FYI: Userspace DTrace MFC to stable/8
On Wed, Mar 30, 2011 at 2:57 AM, Nikolay Denev wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mar 1, 2011, at 12:10 PM, Kostik Belousov wrote: > >> On Tue, Mar 01, 2011 at 11:03:07AM +0200, Nikolay Denev wrote: >>> On 1 Mar, 2011, at 01:33 , Robert Watson wrote: >>> >>>> Dear all: >>>> >>>> Just an FYI that I've gone ahead and merged userspace DTrace support to >>>> FreeBSD 8.x from 9.x. While it appeared to pass build tests locally, boot >>>> and run, etc, this is a non-trivial merge, and it's possible I've messed >>>> up. If so, apologies in advance, and I'll try to resolve any problems as >>>> quickly as I can! >>>> >>>> And of course, many thanks go to Rui Paulo, who did the port of userspace >>>> DTrace to FreeBSD 9.x with support from the FreeBSD Foundation! >>>> >>>> Thanks, >>>> >>>> Robert N M Watson >>>> Computer Laboratory >>>> University of Cambridge >>>> >>> >>> That's great news! Many thanks to all that made this possible! >>> >>> I have a quick question though, now do I have to rebuild my world with >>> "WITH_CTF" ? >>> I'm asking because I did that by mistake some months ago on a RELENG_8 >>> machine, and >>> the world that was built had some problems, like gcc giving segfault 11 >>> while compiling world or some ports. >>> >> It was a known issue that ctfconvert (I think it is ctfconvert) damages >> statically linked binaries. Most likely, it was not fixed yet. > > I can confirm this is not fixed yet. > > I have two STABLE-8 machines which had their world rebuilt with WITH_CTF > option, > and now I'm unable to rebuild the world as both machines fail with > Segmentation Fault: 11 on exactly the same place : > > mkdep -f .depend -a -I/usr/obj/usr/src/tmp/legacy/usr/include > -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib > -I/usr/src/gnu/usr.bin/gperf > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/gen-perf.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/hash-table.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/iterator.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/key-list.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/list-node.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/new.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/options.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/read-line.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/trace.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/vectors.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/version.cc > /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib/hash.cc > cc: Internal error: Segmentation fault: 11 (program cc1plus) > Please submit a full bug report. > See http://gcc.gnu.org/bugs.html> for instructions. > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/gperf. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. I have met this problem before. WITH_CTF on world is not required to use DTrace, and it seems that the gcc is broken. If can get a working gcc4.2 in the base system, you are ucky. Or, you can download a base system for the FreeBSD FTP site, and install it to a temp path, then copy the gcc binary to /usr/bin. > > Regards, > Nikolay > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iEYEARECAAYFAk2S4nMACgkQHNAJ/fLbfrmHJwCgmpMQVdv5DUuz+exWyTIsew0/ > 0EcAn0kMguIUwwczwDxKeayG9pEDRiBy > =K4KJ > -END PGP SIGNATURE- > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD partitioning
On Tue, Mar 22, 2011 at 4:24 PM, Jason Hsu wrote: > How does partitioning work in FreeBSD? GParted recognizes FAT16, FAT32, > NTFS, ext2, ext3, ext4, swap, and many other formats but labels the FreeBSD > partition as unknown. Then there are the sub-partitions within the main > FreeBSD partition. > Check the manual here: http://www.freebsd.org/doc/handbook/install-steps.html I think the first thing you need to understand is, FreeBSD is a UNIX running on x86, not a UNIX rewrote for x86. So the x86-only concept, such as the partitions, may not apply to FreeBSD. In FreeBSD, the term `slice' refers to a record in MBR or GPT table, aka., a partition in x86 world. In a slice, we can use either bsdlabel to create UFS partitions, or install a ZFS pool. So, may be some day gparted can recognize a freebsd slice, it can never labels UFS partitions. > I'm finding it much more difficult to learn BSD than it was to learn Linux. > However, I'm sure it will be worth it, as BSD is legendary for stability and > is the basis for Mac OS and other proprietary systems. Just ask questions in the mailling lists and forums. We answer your questions for free :) > > -- > Jason Hsu > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
How to bind a static ether address to bridge?
My server is behind a DHCP-enabled router, and it has two network interfaces, wlan0 and bge0. I want to use them together, so I bind them, plus tap0 to bridge0. But bridge has a random MAC address for each time it was created, which makes me hard to reserve an IP for it (since I need to forward some ports to this server). So I set net.link.bridge.inherit_mac=1, which makes bridge0 to use bge0's MAC address, always. But this causes another problem: the packets sent to bridge0 is also sent to bge0, -- the packets are duplicated! The kernel have to drop half of them. So how can I bind a distinct MAC address to a bridge? -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
USB flash drive crashed hal on 8.2-PRERELEASE amd64
Hi: I saw a similair error report before. This only happens on this jump stick. The GEOM lines may be the cause of the problem. Please check it out, thank you. ~> dmesg # tail part ugen7.2: at usbus7 umass1: on usbus7 (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error (probe0:umass-sim1:1:0:0): SCSI status: Check Condition (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: Removable Direct Access SCSI-2 device da1: 40.000MB/s transfers da1: 1910MB (3913664 512 byte sectors: 255H 63S/T 243C) GEOM: da1: partition 1 does not start on a track boundary. GEOM: da1: partition 1 does not end on a track boundary. pid 78290 (hald-probe-volume), uid 0: exited on signal 6 (core dumped) pid 78292 (hald-probe-volume), uid 0: exited on signal 6 (core dumped) ~> uname -a FreeBSD compaq.yuetime 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #2: Sun Dec 12 03:34:43 CST 2010 r...@compaq.yuetime:/usr/obj/usr/src/sys/HOUKAGO amd64 -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. -- let focus = 'computing' in here: http://let-in.blogspot.com (let (me Program!)): http://lichray.blogspot.com pgpVlVKxjkffV.pgp Description: PGP signature
Re: ntpd fails on boot
I read your script. OK. My question is, how can I use more than 1 netwait_if? I know I can just use netwait_ip instead, but, for example, in a mDNS configured environment, ping may take a long time to response. In some conditions, it can be 1min. So I don't want to use the fallback 'ping' method. Most laptops today have both LAN and WLAN internet faces, some of them have even more. So please give my 'utter nonsense' an answer. On Tue, Dec 14, 2010 at 7:12 PM, Jeremy Chadwick wrote: > On Tue, Dec 14, 2010 at 06:55:22PM -0600, Zhihao Yuan wrote: > > ping is slow. I hope that we can change the behavior of detecting network > to > > something event driven. Like to insert a script into syslogd to detect > the > > host's dhclient status (in a static IP environment, we don't need > > 'netwait'), or check ifconfig, something like that. > > > > On Tue, Dec 14, 2010 at 6:47 PM, Jeremy Chadwick > > wrote: > > > > > On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > > > > Recently my network connection now is setup AFTER ntpd is launched > rather > > > than before. > > > > > > > > So when ntpd starts there is no net connection and it gives up. > > > > > > > > I read /usr/src/UPDATING but nothing is mentioned about a change in > boot > > > order. > > > > > > > > Any ideas? > > > > > > This issue has been discussed pretty thoroughly in the past. There's > no > > > official solution, but there is an rc.d script I wrote which addresses > > > this shortcoming. Nothing related to the "boot order" has changed, but > > > network drivers and overall methodology has changed. > > > > > > Anyway, many people are using the below with success. > > > > > > http://jdc.parodius.com/freebsd/netwait > > > > > > Official patches, including the rc.conf(5) change I propose: > > > > > > http://jdc.parodius.com/freebsd/netwait_patches/ > > > > > > Example usage (in rc.conf): > > > > > > netwait_enable="yes" > > > netwait_ip="4.2.2.1 4.2.2.2" > > > netwait_if="em0" > > > > > > For what these variables mean, please see the script itself. They are > > > thoroughly documented. > > I don't know what "ping is slow" means -- utter nonsense. Read the > script. Look at how it works please. Seriously. I spent a lot of time > on it, with the help of a lot of community members (including some with > very complex network setups (multiple NICs of different brands, VLANs, > custom routes)). > > netwait is in no way a permanent solution -- it simply addresses most > non-complex environments *reliably*. ifconfig, devd, etc. are not > sufficient ways of determining if the network is *actually usable*. I > cannot stress this enough. I am not talking out of my ass. > > What everyone's proposing (launchd, "way to monitor syslog", > event-driven, blah blah) is wonderful, but until someone has actually > done it, it's just ideal talk. These words are coming from someone > who's very much an idealist, so keep that in mind too; I'm one of the > "worst offenders" when it comes to recommending solutions but not having > the time to implement them. > > I'm going to bow out of the conversation at this point and simply ask > folks here on the thread to take the time to dig up/read old mailing > list archives on the matter. We (FreeBSD Community and the freebsd-rc > folks) have been over all of this before. > > Sorry for sounding crass and rude, but every time this question comes > up, I feel like I have to "defend" why the netwait script exists, why it > was designed the way it was, and so on. Yes, a better infrastructure is > needed to solve the problem *at the core*, but until someone writes > that, we need something that works. > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ntpd fails on boot
ping is slow. I hope that we can change the behavior of detecting network to something event driven. Like to insert a script into syslogd to detect the host's dhclient status (in a static IP environment, we don't need 'netwait'), or check ifconfig, something like that. On Tue, Dec 14, 2010 at 6:47 PM, Jeremy Chadwick wrote: > On Tue, Dec 14, 2010 at 05:38:49PM -0700, Dan Allen wrote: > > Recently my network connection now is setup AFTER ntpd is launched rather > than before. > > > > So when ntpd starts there is no net connection and it gives up. > > > > I read /usr/src/UPDATING but nothing is mentioned about a change in boot > order. > > > > Any ideas? > > This issue has been discussed pretty thoroughly in the past. There's no > official solution, but there is an rc.d script I wrote which addresses > this shortcoming. Nothing related to the "boot order" has changed, but > network drivers and overall methodology has changed. > > Anyway, many people are using the below with success. > > http://jdc.parodius.com/freebsd/netwait > > Official patches, including the rc.conf(5) change I propose: > > http://jdc.parodius.com/freebsd/netwait_patches/ > > Example usage (in rc.conf): > > netwait_enable="yes" > netwait_ip="4.2.2.1 4.2.2.2" > netwait_if="em0" > > For what these variables mean, please see the script itself. They are > thoroughly documented. > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: pcm says `channel dead' with snd_hda
Anybody has any ideas? At the beginning, I guess it's caused by some software. After seen it many times in my log, I found that it appears whenever I want to use the sound card. If you don't use the sound card for a long time (like 10mins), the next time you use it will cause this warning message. Anyone helps? On Wed, Dec 1, 2010 at 3:53 PM, Zhihao Yuan wrote: > ~> uname -a FreeBSD compaq.yuetime 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE > #8: Thu Nov 25 15:48:19 CST 2010 > r...@compaq.yuetime:/usr/obj/usr/src/sys/HOUKAGO > amd64 > > Sometimes, pcm prints the following message to the console & dmesg. > pcm0: chn_write(): pcm0:virtual:dsp0.vp0: play interrupt timeout, channel > dead > > What's wrong? I haven't seen this in 8.1-RELEASE or other version before. > One post said that such message comes with noise, but I'm not sure. I uses > mplayer, sometimes quodlibet (gstreamer backend). > > -- > Zhihao Yuan > The best way to predict the future is to invent it. > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
On Sat, Dec 4, 2010 at 5:19 AM, Andriy Gapon wrote: > on 04/12/2010 04:28 Zhihao Yuan said the following: > > My world and kernel are sync. Is it possible that the dtrace-enabled > kernel must > > be compiled with '-g'? > > It shouldn't be a requirement. But please try. > > DTrace (userland utility on FreeBSD) self-diagnostics really should be > improved. > Obscure complaints about problem in system .d files do not help at all for > a > user to understand what the actual problem could be. Sigh. > > -- > Andriy Gapon > Yes... I hope the coming 8.2-RELEASE can have these 3 providers http://wiki.freebsd.org/DTrace/userland especially the pid provider. :( So far, we can only trace some system calls used by a userland program, which may bot be that helpful. -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
On Sat, Dec 4, 2010 at 5:19 AM, Andriy Gapon wrote: > on 04/12/2010 04:28 Zhihao Yuan said the following: > > My world and kernel are sync. Is it possible that the dtrace-enabled > kernel must > > be compiled with '-g'? > > It shouldn't be a requirement. But please try. > HAHAHAHA! It matters Not KBD, not DDB, only the DEBUG=-g option. It seems like DTrace requires the symbols inside a kernel/program. Well, now my DTrace works perfectly, and the examples on the wiki also work. The next step is to try to use it to trace my program. SDT may help. I need to learn more. Thanks guys... > DTrace (userland utility on FreeBSD) self-diagnostics really should be > improved. > Obscure complaints about problem in system .d files do not help at all for > a > user to understand what the actual problem could be. Sigh. > > -- > Andriy Gapon > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
My world and kernel are sync. Is it possible that the dtrace-enabled kernel must be compiled with '-g'? On Fri, Dec 3, 2010 at 5:29 PM, Andriy Gapon wrote: > on 03/12/2010 21:53 Zhihao Yuan said the following: > > I added these options, KDB & DDB to my KERNCONF, but Dtrace still does > not work, > > and the commands your shown fail on my system, too. > > Can you send a copy of your KERNCONF to us? > > I can, but I don't think that I have any magic in it. > I suppose that you have some problem with either your local environment or > following the procedures. Most of all, I still suspect that your world and > your > kernel are out of sync. > > -- > Andriy Gapon > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
I added these options, KDB & DDB to my KERNCONF, but Dtrace still does not work, and the commands your shown fail on my system, too. Can you send a copy of your KERNCONF to us? On Fri, Dec 3, 2010 at 8:25 AM, Andriy Gapon wrote: > on 02/12/2010 04:24 Jeremy Chadwick said the following: > > On Wed, Dec 01, 2010 at 08:21:21PM -0600, Zhihao Yuan wrote: > >> ctfdump -S /boot/kernel/kernel works, my system has CTF configured. But > I > >> don't have either > >> options KDB > >> or > >> options DDB > >> I guess these has nothing to do with Dtrace, at least KDB is just a > totally > >> different module. Am I right? > > > > Correct; KDB/DDB shouldn't have anything to do with this. > > Yes. But it might - by accident/bug. > > -- > Andriy Gapon > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
ctfdump -S /boot/kernel/kernel works, my system has CTF configured. But I don't have either options KDB or options DDB I guess these has nothing to do with Dtrace, at least KDB is just a totally different module. Am I right? On Wed, Dec 1, 2010 at 7:47 PM, Navdeep Parhar wrote: > On Wed, Dec 1, 2010 at 5:37 PM, Zhihao Yuan wrote: > > I guess such an error has nothing to do with the difference between > > compilers... I assumed that you used similar KERNCONF on your two > systems. > > So, a hypothesis is: Dtrace does not work correctly on amd64. > > It works just fine for me. I built my amd64 kernel a week or so back > with this KERNCONF: > include GENERIC > ident DWARF > options KDTRACE_FRAME > options KDTRACE_HOOKS > options KDB > options DDB > options DDB_CTF > > Can you check with ctfdump if you objects actually have CTF > information in them? Something like this: > # ctfdump -S /boot/kernel/kernel > > # ctfdump /boot/kernel/kernel | grep ... > > Regards, > Navdeep > > > > > On Wed, Dec 1, 2010 at 6:37 PM, Brandon Gooch > > wrote: > > > >> On Wed, Dec 1, 2010 at 6:27 PM, Jeremy Chadwick > >> wrote: > >> > On Wed, Dec 01, 2010 at 06:22:40PM -0600, Brandon Gooch wrote: > >> >> On Wed, Dec 1, 2010 at 4:30 PM, Zhihao Yuan > wrote: > >> >> > OK. Let's make this more clear: anyone has a working 8-2-PRERELEASE > >> kernel > >> >> > (amd64 is preferred) with Dtrace supports, which can run the > >> >> > scripts/commands on the wiki? If so, please post your kernel > >> configurations > >> >> > here, thanks. > >> >> > >> >> I have an i386 system working: > >> >> [snip] > >> > > >> > Can you please try the command the OP originally provided? See > command > >> > here: > >> > > >> > > >> > http://lists.freebsd.org/pipermail/freebsd-stable/2010-November/060216.html > >> > >> d820# dtrace -lP syscall | head > >> ID PROVIDERMODULE FUNCTION NAME > >> 17syscall syscall > entry > >> 18syscall syscall > return > >> 19syscallexit > entry > >> 20syscallexit > return > >> 21syscallfork > entry > >> 22syscallfork > return > >> 23syscallread > entry > >> 24syscallread > return > >> 25syscall write > entry > >> > >> The error the OP received from the above command was pretty much > >> exactly what I was seeing when I attempting to use DTrace on my HEAD > >> system, built with clang. Same error, at least this part: > >> > >> "/usr/lib/dtrace/psinfo.d", line 88: failed to resolve type > >> kernel`struct thread * for identifier curthread: Unknown type name" > >> > >> I was running simply 'dtrace -l' to list all probes... > >> > >> -Brandon > >> > > > > > > > > -- > > Zhihao Yuan > > The best way to predict the future is to invent it. > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
I guess such an error has nothing to do with the difference between compilers... I assumed that you used similar KERNCONF on your two systems. So, a hypothesis is: Dtrace does not work correctly on amd64. On Wed, Dec 1, 2010 at 6:37 PM, Brandon Gooch wrote: > On Wed, Dec 1, 2010 at 6:27 PM, Jeremy Chadwick > wrote: > > On Wed, Dec 01, 2010 at 06:22:40PM -0600, Brandon Gooch wrote: > >> On Wed, Dec 1, 2010 at 4:30 PM, Zhihao Yuan wrote: > >> > OK. Let's make this more clear: anyone has a working 8-2-PRERELEASE > kernel > >> > (amd64 is preferred) with Dtrace supports, which can run the > >> > scripts/commands on the wiki? If so, please post your kernel > configurations > >> > here, thanks. > >> > >> I have an i386 system working: > >> [snip] > > > > Can you please try the command the OP originally provided? See command > > here: > > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-November/060216.html > > d820# dtrace -lP syscall | head > ID PROVIDERMODULE FUNCTION NAME > 17syscall syscall entry > 18syscall syscall return > 19syscallexit entry > 20syscallexit return > 21syscallfork entry > 22syscallfork return > 23syscallread entry > 24syscallread return > 25syscall write entry > > The error the OP received from the above command was pretty much > exactly what I was seeing when I attempting to use DTrace on my HEAD > system, built with clang. Same error, at least this part: > > "/usr/lib/dtrace/psinfo.d", line 88: failed to resolve type > kernel`struct thread * for identifier curthread: Unknown type name" > > I was running simply 'dtrace -l' to list all probes... > > -Brandon > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
OK. Let's make this more clear: anyone has a working 8-2-PRERELEASE kernel
(amd64 is preferred) with Dtrace supports, which can run the
scripts/commands on the wiki? If so, please post your kernel configurations
here, thanks.
On Tue, Nov 23, 2010 at 7:27 AM, Andriy Gapon wrote:
> on 23/11/2010 15:25 Jeremy Chadwick said the following:
> > On Tue, Nov 23, 2010 at 05:13:53AM -0800, Jeremy Chadwick wrote:
> >> On Tue, Nov 23, 2010 at 02:39:47PM +0200, Andriy Gapon wrote:
> >>> on 23/11/2010 10:20 Zhihao Yuan said the following:
> >>>> Attach my kernel configuration here, just in case.
> >>>>
> >>>> On 00:12 Tue 23 Nov, Jeremy Chadwick wrote:
> >>>>> Forwarding back to the mailing list since the OP didn't CC it on his
> >>>>> reply to me.
> >>>>>
> >>>>> - Forwarded message from Zhihao Yuan -
> >>>>>
> >>>>>> From: Zhihao Yuan
> >>>>>> To: Jeremy Chadwick
> >>>>>> Date: Tue, 23 Nov 2010 01:18:57 -0600
> >>>>>> Subject: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
> >>>>>>
> >>>>>> I followed the instructions, but still can not run any D-scripts.
> All
> >>>>>> scripts shows the error message that I just posted.
> >>>
> >>> Are the installed world and the installed kernel in sync?
> >>> (Built from the same state of source code).
>
> The same question.
>
> >> FWIW, I can reproduce his problem when following the procedure outlined
> >> in the Wiki.
> >>
> >> As a workaround I tried adding WITH_CTF=true to /etc/src.conf and
> >> rebuilding + reinstalling world + reboot, to no avail. I'm rebuilding
> >> the kernel now to see if that makes a difference after the above
> >> workaround.
> >
> > Nope, no go.
> >
> > icarus# kldload dtraceall
> > icarus# dtrace -lP syscall
> > dtrace: invalid probe specifier syscall: "/usr/lib/dtrace/psinfo.d", line
> 37: syntax error near "uid_t"
> >
> > icarus# ls -l /boot/kernel/kernel
> > -r-xr-xr-x 1 root wheel 7180261 Nov 23 05:16 /boot/kernel/kernel
> > icarus# ls -l /usr/lib/dtrace
> > total 32
> > -r--r--r-- 1 root wheel 8608 Nov 23 05:09 drti.o
> > -r--r--r-- 1 root wheel 6910 Nov 23 05:09 errno.d
> > -r--r--r-- 1 root wheel 3196 Nov 23 05:09 psinfo.d
> > -r--r--r-- 1 root wheel 3597 Nov 23 05:09 regs_x86.d
> > -r--r--r-- 1 root wheel 3121 Nov 23 05:09 signal.d
> > -r--r--r-- 1 root wheel 2019 Nov 23 05:09 unistd.d
> >
> > icarus# vim /usr/lib/dtrace/psinfo.d
> > ...
> > 31 typedef struct psinfo {
> > 32 int pr_nlwp;/* number of threads */
> > 33 pid_t pr_pid; /* unique process id */
> > 34 pid_t pr_ppid;/* process id of parent */
> > 35 pid_t pr_pgid; /* pid of process group leader */
> > 36 pid_t pr_sid; /* session id */
> > 37 uid_t pr_uid; /* real user id */
> > 38 uid_t pr_euid;/* effective user id */
> > 39 gid_t pr_gid; /* real group id */
> > 40 gid_t pr_egid;/* effective group id */
> >
>
>
> --
> Andriy Gapon
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
--
Zhihao Yuan
The best way to predict the future is to invent it.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8.1-RELEASE: snd_hda works as module only, suspend/resume leaves display off
I have exactly the same problem, the video never wakes up for acpiconf -s 3. My computer is HP nc8430, with 8.2-PRELEASE amd64. My old laptop Dell Inspiron 1100 with FreeBSD5.5 i386 has the same problem. So FreeBSD just can't handle suspend on my laptops :) On Wed, Dec 1, 2010 at 3:49 PM, David DEMELIER wrote: > 2010/11/15 Stefan Walter : > > Hi, > > > > I've been using 8.1-RELEASE on this desktop machine for a few months > > already, but only now found the time to look at a couple of problems with > > snd_hda and suspend/resume it still has. Maybe someone here has hints to > > fix them - I'd be grateful to hear them. > > > > Audio with snd_hda(4) works, but only if loaded as a module AND only if I > > load the module AFTER booting. If I compile it into the kernel or add > > snd_hda_load="YES" to /boot/loader.conf, dmesg shows the following: > > > > hdac0: HDA Codec #0: ATI RS690/780 HDMI > > pcm0: at cad 0 nid 1 on hdac0 > > hdac1: HDA Codec #0: Realtek ALC885 > > pcm1: at cad 0 nid 1 on hdac1 > > pcm2: at cad 0 nid 1 on hdac1 > > pcm3: at cad 0 nid 1 on hdac1 > > > > mixer(8) shows: > > > > Mixer vol is currently set to 75:75 > > Mixer pcm is currently set to 75:75 > > > > There is no audio in that case. Unloading and reloading the module (or > > just loading the module manually after the boot process) logs: > > > > hdac0: mem > 0xfe024000-0xfe027fff irq 16 at device 20.2 on pci0 > > hdac0: HDA Driver Revision: 20100226_0142 > > hdac0: [ITHREAD] > > hdac0: HDA Codec #0: Realtek ALC885 > > hdac1: mem > 0xfdffc000-0xfdff irq 19 at device 5.1 on pci1 > > hdac1: HDA Driver Revision: 20100226_0142 > > hdac1: [ITHREAD] > > hdac1: HDA Codec #0: ATI RS690/780 HDMI > > pcm0: at cad 0 nid 1 on hdac0 > > pcm1: at cad 0 nid 1 on hdac0 > > pcm2: at cad 0 nid 1 on hdac0 > > pcm3: at cad 0 nid 1 on hdac1 > > > > mixer then shows: > > > > Mixer vol is currently set to 75:75 > > Mixer pcm is currently set to 75:75 > > Mixer speaker is currently set to 75:75 > > Mixer line is currently set to 75:75 > > Mixer mic is currently set to 0:0 > > Mixer mix is currently set to 0:0 > > Mixer rec is currently set to 75:75 > > Mixer igainis currently set to 0:0 > > > > Audio then seems to work fine. (Plugging earphones into the computer's > > case's front plugs doesn't do anything, though - audio still comes from > > the speakers attached to the plug at the back of the case. Any ideas > about > > that?) Loading snd_hda from a startup script would probably work, but I > > guess that's not the way it was meant to work. > > > > The other problem is with suspend/resume: > > > > Suspend To RAM (S3) works by using "acpiconf -s 3", and pushing the power > > button wakes the system up again. Everything seems to work, only the LCD > > monitor remains off. (There also seem to be occasional cases in which the > > keyboard doesn't work any more, but I haven't really looked at that, yet. > > Usually, the system comes back up properly.) Loading dpms(4) doesn't seem > > to make a difference. The only way to turn the display on again seems to > > be typing "shutdown -r now" blindly. > > > > Regards, > > Stefan > > > > Same here, if I have snd_hda directly in kernel, screen doesn't wake > up with or without hw.acpi.reset_video=1. I don't like much modules > since it takes some time to load at boot so if a fix could be made it > will be great.. > > Cheers, > > -- > Demelier David > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
pcm says `channel dead' with snd_hda
~> uname -a FreeBSD compaq.yuetime 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #8: Thu Nov 25 15:48:19 CST 2010 r...@compaq.yuetime:/usr/obj/usr/src/sys/HOUKAGO amd64 Sometimes, pcm prints the following message to the console & dmesg. pcm0: chn_write(): pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead What's wrong? I haven't seen this in 8.1-RELEASE or other version before. One post said that such message comes with noise, but I'm not sure. I uses mplayer, sometimes quodlibet (gstreamer backend). -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Failed to build RELENG_8 with NFSv4 support
I changed my working KERNCONF to support the NFSv4 server & client: - options NFSSERVER + options NFSD -options NFSCLIENT + options NFSCL No matter I enabled NFSLOCKD or not, I can't successfully build the kernel. The error message says: linking kernel nlm_prot_impl.o(.text+0x11b6): In function `nlm_client_recovery_start': : undefined reference to `nlm_client_recovery' nlm_prot_impl.o(.text+0x3e8a): In function `nlm_syscall': : undefined reference to `nlm_advlock' nlm_prot_impl.o(.text+0x3e9c): In function `nlm_syscall': : undefined reference to `nlm_reclaim' *** Error code 1 Stop in /usr/obj/usr/src/sys/HOUKAGO. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Is this caused by an incomplete NFSCL? -- Zhihao Yuan The best way to predict the future is to invent it. -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. -- let focus = 'computing' in here: http://let-in.blogspot.com (let (me Program!)): http://lichray.blogspot.com cpu HAMMER ident HOUKAGO # To statically compile in device wiring instead of /boot/device.hints hints "GENERIC.hints" # Default places to look for devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=value', see kenv(1) # # env "GENERIC.env" #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options NETGRAPH# Graph based kernel networking subsystem options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #optionsUFS_GJOURNAL# Enable gjournal-based UFS journaling #optionsMD_ROOT # MD is a potential root device options NFSCL # Network Filesystem Client (NFSv4) options NFSD# Network Filesystem Server (NFSv4) #optionsNFSLOCKD# Network Lock Manager #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options LIBICONV# Preload iconv options MSDOSFS_ICONV # MSDOS Filesystem with iconv support options EXT2FS # Ext2/3 Filesystem options CD9660 # ISO 9660 Filesystem #optionsPROCFS # Process filesystem (requires PSEUDOFS) #optionsPSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat (sgtty) options COMPAT_FREEBSD32# Compatible with i386 binaries #optionsCOMPAT_FREEBSD4 # Compatible with FreeBSD4 #optionsCOMPAT_FREEBSD5 # Compatible with FreeBSD5 #optionsCOMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. options KBD_INSTALL_CDEV# install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) #optionsAUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache options KDTRACE_FRAME # Ensure frames are compiled in options KDTRACE_HOOKS # Kernel DTrace hooks options DDB_CTF # Kernel ELF linker loads CTF data #optionsINCLUDE_CONFIG_FILE # Include t
Re: Can not build either kernel nor 'world'
I used wget to get the base system, and installed it to a alternative root. Then I replaced the broken gcc with the old working ones, then rebuild everything. Now my system works. On Wed, Nov 24, 2010 at 1:58 AM, Scot Hetzel wrote: > On Tue, Nov 23, 2010 at 9:40 PM, Zhihao Yuan wrote: > > OK, I know what happened. The version that I used to buildworld happens > to > > have a bug in gcc, which just crashes and crashes. Then I tried to use > the > > external gcc42 to build the kernel, but I got the error message: > > cc1: error: unrecognized command line option: -fformat-extension > > > > So what, where can I get a working build tools that work for the kernel & > > world, or how can I downgrade the world so I can get a working gcc and > devd? > > > The following may help in getting your system running, but hasn't been > tested: > > 1. Either update or downgrade your sources to get past the gcc bug. > 2. Boot the FreeBSD livefs CD/memstick > 3. mount your partions > > mkdir /mnt > mount -t ufs /dev/ad0s1a /mnt > mount -t ufs /dev/ad0s1d /mnt/usr > mount -t ufs /dev/ad0s1e /mnt/var > > 4. link /mnt/usr/obj directory > > ln -s /mnt/usr/obj /usr/obj > > 5. Build world and kernel > > cd /mnt/usr/src/ > make buildworld > make buildkernel KERNCONF=MYKERNEL > > 6. Install the new world and kernel > > make installworld DESTDIR=/mnt > make installkernel DESTDIR=/mnt KERNCONF=MYKERNEL > mergemaster -i -C -D /mnt > > 7. Reboot the computer and remove the fixit CD > > Scot > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
I'm sorry, I'm not going to split the topics. So here is the current status: built kernel WITH_CTF and build world without CTF (I assume CTF is just a kernel feature). And the problem is exactly the same as I posted before, say "line 88" staff. And, there are many people who have the same problem. Is it caused by some other options in our KERNCONF? Or it just does not work on some platforms On Tue, Nov 23, 2010 at 11:28 PM, Jeremy Chadwick wrote: > On Tue, Nov 23, 2010 at 10:20:52PM -0600, Zhihao Yuan wrote: > > As I posted in another email, the gcc crashes in latest RELENG_8. Another > > explanation is that buildworld WITH_CTF=1 can crashes the gcc. I > overwrote > > the gcc with the version in 8.1_RELEASE, and I'm rebuilding everything. > > > > I just want to know whether I'm supposed to be able to use Dtrace just > with > > a CTF-enabled kernel. And, if so, what should I do to make it actually > > works. Thanks... guys. > > > > On Tue, Nov 23, 2010 at 4:50 PM, Zhihao Yuan wrote: > > > > > Can not rebuild kernel. As you known, I installed the latest kernel > last > > > night. This afternoon, I installed the latest 'world', which makes the > > > 'world' and the kernel a little bit de-synchronized. And, I found that > the > > > devd can not be started, s I tried to build the kernel again. > > > > > > Here I met the biggest problem: I can not rebuild the kernel now! For > each > > > time the make process stopped at stage 2.3, and gives me a core dump > > > finally. What's wrong? > > > > > > On Tue, Nov 23, 2010 at 2:52 PM, Zhihao Yuan > wrote: > > > > > >> That's what I have done. I did not used WITH_CTF=1 on buildworld. > Anyway, > > >> I;m using it to rebuild the world, which takes some time. > > >> > > >> On Tue, Nov 23, 2010 at 2:48 PM, Andriy Gapon > wrote: > > >> > > >>> on 23/11/2010 22:45 Jeremy Chadwick said the following: > > >>> > make buildkernel WITH_CTF=1 > > >>> > > >>> I believe the above to be necessary and sufficient part (for using > DTrace > > >>> on > > >>> kernel). > > I don't have this problem (re: gcc crashing on buildworld, with or > without WITH_CTF=1). If gcc is crashing with signal 11: > http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11 > > Kindly requested: please apply some focus to a single issue or start > separate threads for the problems you're experiencing (though I > understand how some can be related to one another). So far there's been > 3 or 4 separate topics/items mentioned during the course of this thread > (how to get DTrace working, problems with devd, and now gcc crashing), > and it's becoming more and more difficult to follow what's going on. > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
As I posted in another email, the gcc crashes in latest RELENG_8. Another explanation is that buildworld WITH_CTF=1 can crashes the gcc. I overwrote the gcc with the version in 8.1_RELEASE, and I'm rebuilding everything. I just want to know whether I'm supposed to be able to use Dtrace just with a CTF-enabled kernel. And, if so, what should I do to make it actually works. Thanks... guys. On Tue, Nov 23, 2010 at 4:50 PM, Zhihao Yuan wrote: > Can not rebuild kernel. As you known, I installed the latest kernel last > night. This afternoon, I installed the latest 'world', which makes the > 'world' and the kernel a little bit de-synchronized. And, I found that the > devd can not be started, s I tried to build the kernel again. > > Here I met the biggest problem: I can not rebuild the kernel now! For each > time the make process stopped at stage 2.3, and gives me a core dump > finally. What's wrong? > > On Tue, Nov 23, 2010 at 2:52 PM, Zhihao Yuan wrote: > >> That's what I have done. I did not used WITH_CTF=1 on buildworld. Anyway, >> I;m using it to rebuild the world, which takes some time. >> >> On Tue, Nov 23, 2010 at 2:48 PM, Andriy Gapon wrote: >> >>> on 23/11/2010 22:45 Jeremy Chadwick said the following: >>> > make buildkernel WITH_CTF=1 >>> >>> I believe the above to be necessary and sufficient part (for using DTrace >>> on >>> kernel). >>> >>> -- >>> Andriy Gapon >>> >> >> >> >> -- >> Zhihao Yuan >> The best way to predict the future is to invent it. >> >> > > > -- > Zhihao Yuan > The best way to predict the future is to invent it. > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Can not build either kernel nor 'world'
OK, I know what happened. The version that I used to buildworld happens to have a bug in gcc, which just crashes and crashes. Then I tried to use the external gcc42 to build the kernel, but I got the error message: cc1: error: unrecognized command line option: -fformat-extension So what, where can I get a working build tools that work for the kernel & world, or how can I downgrade the world so I can get a working gcc and devd? On Tue, Nov 23, 2010 at 7:33 PM, Zhihao Yuan wrote: > I built and installed the latest 'world' this afternoon, and found that I > can not build the kernel now. And, the devd can not be started. I do not > know what's wrong. Maybe I need to downgrade my system to 8.1-RELEASE first. > What should I do now? > > -- > Zhihao Yuan > The best way to predict the future is to invent it. > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Can not build either kernel nor 'world'
I built and installed the latest 'world' this afternoon, and found that I can not build the kernel now. And, the devd can not be started. I do not know what's wrong. Maybe I need to downgrade my system to 8.1-RELEASE first. What should I do now? -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Can not build either kernel nor 'world'
I built and installed the latest 'world' this afternoon, and found that I can not build the kernel now. And, the devd can not be started. I do not know what's wrong. Maybe I need to downgrade my system to 8.1-RELEASE first. What should I do now? -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
Can not rebuild kernel. As you known, I installed the latest kernel last night. This afternoon, I installed the latest 'world', which makes the 'world' and the kernel a little bit de-synchronized. And, I found that the devd can not be started, s I tried to build the kernel again. Here I met the biggest problem: I can not rebuild the kernel now! For each time the make process stopped at stage 2.3, and gives me a core dump finally. What's wrong? On Tue, Nov 23, 2010 at 2:52 PM, Zhihao Yuan wrote: > That's what I have done. I did not used WITH_CTF=1 on buildworld. Anyway, > I;m using it to rebuild the world, which takes some time. > > On Tue, Nov 23, 2010 at 2:48 PM, Andriy Gapon wrote: > >> on 23/11/2010 22:45 Jeremy Chadwick said the following: >> > make buildkernel WITH_CTF=1 >> >> I believe the above to be necessary and sufficient part (for using DTrace >> on >> kernel). >> >> -- >> Andriy Gapon >> > > > > -- > Zhihao Yuan > The best way to predict the future is to invent it. > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
if_wpi crashes when renewing in FreeBSD 8 all versions
My laptop is a HP Compaq nc8430, and the wireless card is Intel 3945ABG, with if_wpi driver. wpi0: flags=8802 metric 0 mtu 2290 ether 00:1b:77:31:1d:74 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier I can use the wireless correctly when I start the system. But after some time (depends on your wireless router renewing settings), it can not renew the DHCP settings. And, if you try to renew it with sudo /etc/rc.d/netif restart for like more than 2 times, the whole system will crash. The interesting thing is, the renewing problem only occurs on the wireless network with a WPA2 protocol. For the WEP or None-keys network, there is no problem. For the WPA-EAP network, you can redo the DHCP but not /etc/rc.d/netif restart. -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
That's what I have done. I did not used WITH_CTF=1 on buildworld. Anyway, I;m using it to rebuild the world, which takes some time. On Tue, Nov 23, 2010 at 2:48 PM, Andriy Gapon wrote: > on 23/11/2010 22:45 Jeremy Chadwick said the following: > > make buildkernel WITH_CTF=1 > > I believe the above to be necessary and sufficient part (for using DTrace > on > kernel). > > -- > Andriy Gapon > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
Does the WITH_CTF=1 works for the buildworld? And, what should I do now? On Tue, Nov 23, 2010 at 7:51 AM, Alexander Leidinger < alexan...@leidinger.net> wrote: > Quoting Jeremy Chadwick (from Tue, 23 Nov 2010 > 05:13:53 -0800): > > On Tue, Nov 23, 2010 at 02:39:47PM +0200, Andriy Gapon wrote: >> >>> on 23/11/2010 10:20 Zhihao Yuan said the following: >>> > Attach my kernel configuration here, just in case. >>> > >>> > On 00:12 Tue 23 Nov, Jeremy Chadwick wrote: >>> >> Forwarding back to the mailing list since the OP didn't CC it on his >>> >> reply to me. >>> >> >>> >> - Forwarded message from Zhihao Yuan - >>> >> >>> >>> From: Zhihao Yuan >>> >>> To: Jeremy Chadwick >>> >>> Date: Tue, 23 Nov 2010 01:18:57 -0600 >>> >>> Subject: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE >>> >>> >>> >>> I followed the instructions, but still can not run any D-scripts. All >>> >>> scripts shows the error message that I just posted. >>> >>> Are the installed world and the installed kernel in sync? >>> (Built from the same state of source code). >>> >> >> FWIW, I can reproduce his problem when following the procedure outlined >> in the Wiki. >> >> As a workaround I tried adding WITH_CTF=true to /etc/src.conf and >> > > WITH_CTF for makeoptions is only supported on 9-current (don't remember the > exact rev). > > The text there tells to use WITH_CTF=1 for the buildkernel, but the example > does not use it (it should for 8.x, it shouldn't need to for an approriate > rev. of 9-current). The text that it will not work in make.conf/src.conf is > valid for 8.x, but not (at least it shouldn't) for an appropriate versions > of 9-current. > > Bye, > Alexander. > > -- > For people who like that kind of book, > that is the kind of book they will like. > > http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
Attach my kernel configuration here, just in case. On 00:12 Tue 23 Nov, Jeremy Chadwick wrote: > Forwarding back to the mailing list since the OP didn't CC it on his > reply to me. > > - Forwarded message from Zhihao Yuan ----- > > > From: Zhihao Yuan > > To: Jeremy Chadwick > > Date: Tue, 23 Nov 2010 01:18:57 -0600 > > Subject: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE > > > > I followed the instructions, but still can not run any D-scripts. All > > scripts shows the error message that I just posted. > > > > On Tue, Nov 23, 2010 at 12:29 AM, Jeremy Chadwick > > wrote: > > > > > On Mon, Nov 22, 2010 at 11:45:38PM -0600, Zhihao Yuan wrote: > > > > ~> uname -a > > > > FreeBSD compaq.yuetime 8.1-STABLE FreeBSD 8.1-STABLE #0: Thu Nov 18 > > > 01:32:06 > > > > CST > > > > 2010 r...@compaq.yuetime:/usr/obj/usr/src/sys/HOUKAGO amd64 > > > > > > > > I added the required options to the kernel config file: > > > > > > > > Code: > > > > > > > > options KDTRACE_FRAME > > > > options KDTRACE_HOOKS > > > > options DDB_CTF > > > > > > > > and compiled/installed the kernel WITH_CTF=1 successfully. > > > > > > > > sudo make buildkernel KERNCONF=HOUKAGO WITH_CTF=1 > > > > sudo make installkernel KERNCONF=HOUKAGO WITH_CTF=1 > > > > > > > > The dtraceall is loaded, and dtrace -l works. But whenever I want to run > > > a > > > > dtrace command, I get something like: > > > > > > > > ~> sudo dtrace -lP syscall > > > > dtrace: invalid probe specifier syscall: "/usr/lib/dtrace/psinfo.d", > > > > line > > > > 37: syntax error near "uid_t" > > > > > > > > The error message looks like what you got when WITH_CTF=1 is not > > > presented. > > > > Any idea? > > > > > > I don't know if this will help, but I followed the procedure here: > > > > > > http://wiki.freebsd.org/DTrace > > > > > > Which worked fine. See this thread for verification that the above > > > works correctly: > > > > > > http://lists.freebsd.org/pipermail/freebsd-fs/2010-October/009780.html > > > > > > -- > > > | Jeremy Chadwick j...@parodius.com | > > > | Parodius Networking http://www.parodius.com/ | > > > | UNIX Systems Administrator Mountain View, CA, USA | > > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > > > > > > > -- > > Zhihao Yuan > > The best way to predict the future is to invent it. > > - End forwarded message - > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. -- let focus = 'computing' in here: http://let-in.blogspot.com (let (me Program!)): http://lichray.blogspot.com cpu HAMMER ident HOUKAGO # To statically compile in device wiring instead of /boot/device.hints hints "GENERIC.hints" # Default places to look for devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=value', see kenv(1) # # env "GENERIC.env" #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options NETGRAPH# Graph based kernel networking subsystem options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOF
Fail to use Dtrace on FreeBSD 8.1-STABLE
~> uname -a FreeBSD compaq.yuetime 8.1-STABLE FreeBSD 8.1-STABLE #0: Thu Nov 18 01:32:06 CST 2010 r...@compaq.yuetime:/usr/obj/usr/src/sys/HOUKAGO amd64 I added the required options to the kernel config file: Code: options KDTRACE_FRAME options KDTRACE_HOOKS options DDB_CTF and compiled/installed the kernel WITH_CTF=1 successfully. sudo make buildkernel KERNCONF=HOUKAGO WITH_CTF=1 sudo make installkernel KERNCONF=HOUKAGO WITH_CTF=1 The dtraceall is loaded, and dtrace -l works. But whenever I want to run a dtrace command, I get something like: ~> sudo dtrace -lP syscall dtrace: invalid probe specifier syscall: "/usr/lib/dtrace/psinfo.d", line 37: syntax error near "uid_t" The error message looks like what you got when WITH_CTF=1 is not presented. Any idea? -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Fail to use Dtrace on FreeBSD 8.1-STABLE
I just updated to the latest stable: ~> uname -a FreeBSD compaq.yuetime 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #1: Mon Nov 22 23:44:47 CST 2010 r...@compaq.yuetime:/usr/obj/usr/src/sys/HOUKAGO amd64 OK, a little bit better: ~> sudo dtrace -lP syscall dtrace: invalid probe specifier syscall: "/usr/lib/dtrace/psinfo.d", line 88: failed to resolve type kernel`struct thread * for identifier curthread: Unknown type name -- which means the CTF does work, but fails to work perfectly. HELP On Mon, Nov 22, 2010 at 11:45 PM, Zhihao Yuan wrote: > ~> uname -a > FreeBSD compaq.yuetime 8.1-STABLE FreeBSD 8.1-STABLE #0: Thu Nov 18 > 01:32:06 CST > 2010 r...@compaq.yuetime:/usr/obj/usr/src/sys/HOUKAGO amd64 > > I added the required options to the kernel config file: > > Code: > > options KDTRACE_FRAME > options KDTRACE_HOOKS > options DDB_CTF > > and compiled/installed the kernel WITH_CTF=1 successfully. > > sudo make buildkernel KERNCONF=HOUKAGO WITH_CTF=1 > sudo make installkernel KERNCONF=HOUKAGO WITH_CTF=1 > > The dtraceall is loaded, and dtrace -l works. But whenever I want to run a > dtrace command, I get something like: > > ~> sudo dtrace -lP syscall > dtrace: invalid probe specifier syscall: "/usr/lib/dtrace/psinfo.d", line > 37: syntax error near "uid_t" > > The error message looks like what you got when WITH_CTF=1 is not > presented. Any idea? > > -- > Zhihao Yuan > The best way to predict the future is to invent it. > > -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
