Re: BSD sleep
On 5/28/2013 6:01 PM, Kenta Suzumoto wrote: Hi. Is there no built-in way of making sleep sleep in increments of minutes, hours, etc? The GNU sleep can be invoked like sleep 1h for an hour. The FreeBSD one's manpage leads me to believe we can only use seconds, which is kind of annoying. Is there an undocmented or missing feature here? Seems really trivial to implement. ~ $ sleep 1h usage: sleep seconds You think it's trivial until you read this: http://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time If you sleep one hour, do you sleep one hour from now or one hour from the system clock which may change in the next hour? If it's the system clock, you may sleep for ten minutes or ten hours. If you need to sleep for 3600 seconds, that's simple and understandable. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Audio Hints, T520?
On 5/5/2013 5:33 PM, Sean Bruno wrote: Yes. I've toggled both, but I see no difference. Zero input from on board microphone. http://people.freebsd.org/~sbruno/verbose_hdaac.txt Sean p.s. physically, there is no microphone jack on this machine. There is just the headphone jack. So, what were you using to test the microphone? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Audio Hints, T520?
On 5/5/2013 6:11 PM, Sean Bruno wrote: On Sun, 2013-05-05 at 17:54 -0500, Joshua Isom wrote: On 5/5/2013 5:33 PM, Sean Bruno wrote: Yes. I've toggled both, but I see no difference. Zero input from on board microphone. http://people.freebsd.org/~sbruno/verbose_hdaac.txt Sean p.s. physically, there is no microphone jack on this machine. There is just the headphone jack. So, what were you using to test the microphone? ___ I was using audacity. Should I try something else? Sean I meant what hardware? How's it connected? So far I think you've only focused on the software side. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Audio Hints, T520?
On 5/5/2013 7:03 PM, Sean Bruno wrote: On Sun, 2013-05-05 at 18:57 -0500, Joshua Isom wrote: On 5/5/2013 6:11 PM, Sean Bruno wrote: On Sun, 2013-05-05 at 17:54 -0500, Joshua Isom wrote: On 5/5/2013 5:33 PM, Sean Bruno wrote: Yes. I've toggled both, but I see no difference. Zero input from on board microphone. http://people.freebsd.org/~sbruno/verbose_hdaac.txt Sean p.s. physically, there is no microphone jack on this machine. There is just the headphone jack. So, what were you using to test the microphone? ___ I was using audacity. Should I try something else? Sean I meant what hardware? How's it connected? So far I think you've only focused on the software side. It's a laptop. On board microphone thingy. No wires required. :-) Sean Are you sure it's not a USB microphone? What do you get when you run `usbconfig list`? It's probably doubtful, since your keyboard could be PS/2 and manufacturers don't like change. Also, what's the output of `pciconf -lv` just for clarity? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Light humour
On 4/29/2013 9:46 AM, David Chisnall wrote: On 28 Apr 2013, at 19:09, Stephen Montgomery-Smith step...@missouri.edu wrote: But let's not get into the Linux bashing the same way he bashed BSD. There is already a very good Linux Haters' Blog, in the tradition of the UNIX Haters' Handbook. Unlike the antibsd blog (which contains ill-informed rants and nonsense), it actually provides well-thought-out criticisms of Linux in general and various distributions. I'd love to see a similar blog for FreeBSD, with legitimate criticisms... David All you need is one good blog, with someone posting as Devil's Advocate. Good debate requires someone opposing unanimity. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Light humour
I found it a few weeks ago. I left a comment in the jails article about citing sources. Comments need moderator approval, and of course it was never approved. The blog actually turned up in google's list in the front page when I searched for FreeBSD Linux jail. I read an article on slashdot that BSD style licenses are becoming more popular, probably realizing the long term ramifications of GPL style licenses. I think the most dangerous thing in many GPLed projects is any later version. It gives the FSF licensing control instead of developers. There needs to be a pro-BSD blog. Regarding the licensing differences, it's simple. BSD: If you love something, set it free. If it comes back to you, it was meant to be. GPL: If you love something, set if free, but put a chain around it's neck to make sure it doesn't get out of sight. On 4/28/2013 12:54 PM, Adrian Chadd wrote: Yeah, the trouble is that people can/will believe this nonsense. So, question. Where's the pro-BSD blog(s) to offset it? :) adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: panic when booting HEAD on i386
On 4/21/2013 6:54 AM, Ganbold Tsagaankhuu wrote: As mentioned in one of my previous email I have 2GB machine which is probably not worth to have zfs on such system. Sorry for the noise. thanks, Ganbold Before I upgraded my system, I used 2GB of ram with ZFS on root, no UFS on the system. Right now my ARC is 17GB, and in some situations it seems slower with the excess caching. Here are the memory settings I used. vm.kmem_size=512M vm.kmem_size_max=1024M vfs.zfs.arc_max=512M One major difference is I'm using amd64, not i386. Although ZFS works on i386, it uses a lot of 64 bit math, for performance reasons you should use ZFS on amd64. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Booting an alternative kernel from loader prompt fails the first time only
On 4/20/2013 12:41 PM, Manfred Antar wrote: At 10:24 AM 4/20/2013, Rainer Hurling wrote: On 20.04.2013 18:47 (UTC+2), Florian Smeets wrote: On 20.04.13 18:05, Steven Hartland wrote: When trying to boot an alternative kernel from the loader prompt it fails the first time the command is run but succeeds the second time. Type '?' for a list of commands, 'help' for more detailed help. OK boot kernel.generic Booting... don't know how to load module '/boot/kernel.generic/kernel' OK boot kernel.generic Booting... /boot/kernel.generic/kernel text=0xd21288 data=.. Yes, I've been seeing the same thing for about 6-12 months maybe more. None of the people I asked were able to confirm, so I'm happy that I'm not imagining it :) I also can confirm this behaviour for month now (on 10.0-CURRENT amd64 with clang). Rainer Have you tried: OK boot /boot/kernel.generic/kernel Use full path name always works for me Manfred I couldn't get any other method to work. I can also confirm this. While working with Adrian testing ath changes, I frequently had to reboot into an old kernel(/boot/ATH/kernel, full path seemed required) to regain networking unless I physically moved the computer to add ethernet. Also, it's really annoying when I would have to manually kldload each module in order, especially opensolaris.ko and zfs.ko, and making sure I loaded /boot/ATH/if_ath.ko before /boot/ATH/if_ath_pci.ko or else the loader would load from /boot/kernel instead of /boot/ATH and I'd end up with broken networking even though the kernel was right. I'd really love it if there were a way for modules to be bundled with the kernel file and loaded from the kernel instead of the filesystem, especially since many modules can't be compiled in. As a side note, my /boot/loader is from -STABLE, mod time of January 24 this year. This could be an issue on -STABLE also. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: control of order of inet devices
On 4/17/2013 4:14 AM, Willy Offermans wrote: This is what I read in some of the articles or handbook as well. Can I reorder this linked list? Can I control the order by creating the kernel and reordering the inclusion of the device drivers? I am aware that the request sounds silly, but I have a third party program which checks its licence against the first inet device. Since I have added a new inet controller, the sequence has changed. Of course I ask for a new licence, but they want to charge me for that and I do not see any reason for that. Load old inet devices like normal, in loader.conf. Then load the new device driver before networking, after rc's started. If it'd because of probe order, then you might just have to control the probe order the hard way. If the program's calling ifconfig itself, you could write a wrapper to resort the output. And call a lawyer, getting a new ethernet card shouldn't void a license. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: After a source upgrade from 8.3-RELEASE to r249432 (HEAD)
On 4/15/2013 7:50 PM, George Mitchell wrote: I tried that and there was no change. I still get the mountroot: prompt and have to type ufs:/dev/ada0s1a. -- George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org What if you change it to ad0 instead of ada0? I wonder if the legacy aliases isn't being set properly, or something related to that. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Kernel panics, one starting with r248508
I updated today and tried it out, so far it's booted and is working. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Kernel panics, one starting with r248508
I've been helping Adrian test the new ath improvements that support the chipset I have. The first kernel panic is on my system if I have the cd driver loaded into the kernel, I would get a panic on boot. While Mounting local file systems: it would panic with Memory modified after free. Removing the driver solved it. I'd rather have wireless than cd for right now anyway. But a couple days ago a new build would always panic, a couple seconds after getty is spawned. All I get is panic: Bio too short 0xfe000b1395d0. Before that, the builds worked other than occasional issues due to cleaning. The only place that panic can be generated is geom_io.c so I'm guessing I can't just remove the driver. What needs done so I can get a working kernel again? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Kernel panics, one starting with r248508
On 3/21/2013 5:38 PM, Konstantin Belousov wrote:
On Thu, Mar 21, 2013 at 03:58:55PM -0500, Joshua Isom wrote:
I've been helping Adrian test the new ath improvements that support the
chipset I have. The first kernel panic is on my system if I have the cd
driver loaded into the kernel, I would get a panic on boot. While
Mounting local file systems: it would panic with Memory modified
after free. Removing the driver solved it. I'd rather have wireless
than cd for right now anyway. But a couple days ago a new build would
always panic, a couple seconds after getty is spawned. All I get is
panic: Bio too short 0xfe000b1395d0. Before that, the builds
worked other than occasional issues due to cleaning. The only place
that panic can be generated is geom_io.c so I'm guessing I can't just
remove the driver. What needs done so I can get a working kernel again?
Try r248596. If it does not help, get a core dump, load it into kgdb
and do p *(struct bio *)addr, where addr is reported in the panic message.
[jri:/var/crash] root# kgdb /boot/kernel/kernel vmcore.10
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...
Unread portion of the kernel message buffer:
panic: Bio too short 0xfe000a224c98
cpuid = 1
KDB: enter: panic
Reading symbols from /boot/kernel/zfs.ko...Reading symbols from
/boot/kernel/zfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/zfs.ko
Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from
/boot/kernel/opensolaris.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/opensolaris.ko
Reading symbols from /boot/kernel/geom_mirror.ko...Reading symbols from
/boot/kernel/geom_mirror.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/geom_mirror.ko
Reading symbols from /boot/kernel/if_ath.ko...Reading symbols from
/boot/kernel/if_ath.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/if_ath.ko
Reading symbols from /boot/kernel/amdtemp.ko...Reading symbols from
/boot/kernel/amdtemp.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/amdtemp.ko
Reading symbols from /boot/kernel/if_ath_pci.ko...Reading symbols from
/boot/kernel/if_ath_pci.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/if_ath_pci.ko
Reading symbols from /boot/kernel/ums.ko...Reading symbols from
/boot/kernel/ums.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ums.ko
Reading symbols from /boot/kernel/ulpt.ko...Reading symbols from
/boot/kernel/ulpt.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ulpt.ko
Reading symbols from /boot/kernel/uhid.ko...Reading symbols from
/boot/kernel/uhid.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/uhid.ko
Reading symbols from /boot/kernel/ipfw.ko...Reading symbols from
/boot/kernel/ipfw.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ipfw.ko
kgdb: kvm_read: invalid address (0x3545415)
#0 0x in ?? ()
(kgdb) p *(struct bio *)0xfe000a224c98
$1 = {bio_cmd = 1 '\001', bio_flags = 16 '\020', bio_cflags = 0 '\0',
bio_pflags = 0 '\0',
bio_dev = 0x0, bio_disk = 0x0, bio_offset = 0, bio_bcount = 0,
bio_data = 0xff8000206000 Address 0xff8000206000 out of bounds,
bio_ma = 0xff80204266d0, bio_ma_offset = 0, bio_ma_n = 17, bio_error = 0,
bio_resid = 0,
bio_done = 0x8078e9b0 g_dev_done, bio_driver1 = 0x0, bio_driver2 =
0x0,
bio_caller1 = 0x0, bio_caller2 = 0x0, bio_queue = {tqe_next = 0x0,
tqe_prev = 0x8122f418}, bio_attribute = 0x0, bio_from =
0xfe000a29f700,
bio_to = 0xfe0007486800, bio_length = 65536, bio_completed = 0,
bio_children = 0,
bio_inbed = 0, bio_parent = 0xfe000a2c7d90, bio_t0 = {sec = 83,
frac = 2480829560582148726}, bio_task = 0, bio_task_arg = 0x0,
bio_classifier1 = 0x0,
bio_classifier2 = 0x0, bio_pblkno = 0}
(kgdb)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
