Fbsd8 wrote:
> 6. At the "Complete screen" when the reboot option is selected the
> cd/dvd drive should automatically open so the install media can be
> removed just like sysinstall does. If disc1.iso or dvd.iso was installed
> to memstick and used to boot from to install the system, then a message
On Sun, Sep 25, 2011 at 3:01 PM, Fbsd8 wrote:
> deeptec...@gmail.com wrote:
>>
>> Fbsd8 wrote:
>>>
>>> 6. At the "Complete screen" when the reboot option is selected the
>>> cd/dvd drive should automatically open so the install media can be
&g
A panic occured while I was ``rm -rf''ing a large file&directory tree
(that I just created with untar) on an old drive that I have not used
for a long time. Unfortunately I'm not 100% sure that the filesystem
was clean when I mounted it today. Could that result in such a panic?
I don't have the in
On Fri, Oct 28, 2011 at 3:40 PM, Bjoern A. Zeeb
wrote:
> On Fri, 28 Oct 2011, deeptec...@gmail.com wrote:
>> I don't have the intermediate object files for the kernel; now I'm
>> building the kernel again (from the appropriate, exact sources). That
>> shou
With object files which were built using the original kernel
configuration file (no debugging symbols included):
#kgdb kernel /var/crash/vmcore.4
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
welco
On Fri, Oct 28, 2011 at 11:16 AM, deeptec...@gmail.com
wrote:
> I don't have the intermediate object files for the kernel; now I'm
> building the kernel again (from the appropriate, exact sources). That
> shouldn't harm debugging, should it?
On Sat, Oct 29, 2011 at 2:35 A
If a USB mass storage device was connected when the computer was
turned on or reset and the device is left connected, then the system
locks up somewhere around the ``acpi0: on
motherboard'' line (not exactly deterministically at that line).
Otherwise (if the device is connected or disconnected jus
Spam:
== ``dmesg'' begins ==
Copyright (c) 1992-2011 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
On Sun, Oct 30, 2011 at 9:27 PM, Hans Petter Selasky wrote:
> On Saturday 29 October 2011 23:26:29 deeptec...@gmail.com wrote:
>> I don't recall this case happening some time ago. But now, this
>> happens with and without the NEW_PCIB option. I mention this because
>>
On Mon, Oct 31, 2011 at 3:01 AM, Garrett Cooper wrote:
> On Oct 30, 2011, at 6:47 PM, deeptec...@gmail.com wrote:
>
>> On Sun, Oct 30, 2011 at 9:27 PM, Hans Petter Selasky
>> wrote:
>>
>>> On Saturday 29 October 2011 23:26:29 deeptec...@gmail.com wrote:
Every time I run mergemaster, I have to manually confirm all of the
local changes I have done to /etc (ie., state how to merge the
temporary and existing files), even files have not changed in the
upstream since the last mergemaster run (for example,
temproot/etc/master.passwd virtually never chang
Well, I did not actually get a full membership to the "rm -rf /"
fanclub, but I managed to remove all installed ports, basically
requiring a full reinstall. Here's how it happened:
Once upon a time, I did a full reinstall (not because of "rm -rf
/"-like things). I kept the old installation's full
On Thu, Feb 23, 2012 at 11:41 PM, deeptec...@gmail.com
wrote:
> X11R6 is actually a symlink to /usr/local, and not usr/local or
> .usr/local! Also, /home is a symlink to /usr/home, and not usr/home or
> ./usr/home
I meant to say that X11R6 should be a symlink to local or ./local.
Ab
As of r232144, SeaMonkey (a web browser) runs rather slowly and is
constantly eating 100% CPU time. Before r232144, SeaMonkey would start
up and run faster, and when it is not in use (is idling), its CPU
usage would slowly converge to 0.
I have a P4 processor [with HT], an r232012 world, and simil
pcib1: at device 1.0 on pci0
pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff
the console output is cut shortly after those 2 lines (but the machine
seems to continue booting, as i have reset'd the machine, after which
"/" was found to be improperly dismounted).
this happ
On Sat, May 14, 2011 at 6:27 PM, deeptec...@gmail.com
wrote:
> pcib1: at device 1.0 on pci0
> pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff
>
> this happens with a the r221862 kernel, but not with the r221309 kernel.
> a quick search reveals so
On Tue, May 17, 2011 at 3:44 PM, John Baldwin wrote:
> On Saturday, May 14, 2011 12:27:59 pm deeptec...@gmail.com wrote:
>> pcib1: at device 1.0 on pci0
>> pcib1: failed to allocate initial prefetch window: 0xd000-0xfaff
>>
>> the console output is cut short
On Tue, May 17, 2011 at 10:40 PM, John Baldwin wrote:
> On Tuesday, May 17, 2011 2:03:42 pm deeptec...@gmail.com wrote:
>> On Tue, May 17, 2011 at 3:44 PM, John Baldwin wrote:
>> > On Saturday, May 14, 2011 12:27:59 pm deeptec...@gmail.com wrote:
>> >> pcib1: at
On Thu, May 19, 2011 at 2:13 PM, John Baldwin wrote:
> Yeah, your BIOS continues to behave very poorly. Please try this hack to see
> if it allows your video to still work with any AGP aperture size:
>
> Index: pci_pci.c
> ===
> ---
On Thu, May 19, 2011 at 11:35 PM, John Baldwin wrote:
> On Thursday, May 19, 2011 12:28:46 pm deeptec...@gmail.com wrote:
>> On Thu, May 19, 2011 at 2:13 PM, John Baldwin wrote:
>> > Yeah, your BIOS continues to behave very poorly. Please try this hack to
> see
>> &
On Sat, May 21, 2011 at 3:59 PM, deeptec...@gmail.com
wrote:
> On Thu, May 19, 2011 at 11:35 PM, John Baldwin wrote:
>> Index: pci_pci.c
>> ===
>> --- pci_pci.c (revision 222093)
>> +++ pci_pci.c
On Thu, May 26, 2011 at 3:40 PM, John Baldwin wrote:
> Ohh, you have two devices behind this bridge that have prefetch ranges.
>
> As a hack, can you try this:
>
> Index: pci_pci.c
> ===
> --- pci_pci.c (revision 85)
> +++ pci_p
On Mon, Jun 6, 2011 at 4:52 PM, John Baldwin wrote:
> Can you try out this change. It is a possible "real" solution (or at least a
> stopgap until we start using multipass to untangle the resource mess a bit
> further):
[snip]
that doesn't work. i get an allocation failure.
_
On Tue, Jun 7, 2011 at 4:35 PM, John Baldwin wrote:
> On Monday, June 06, 2011 11:02:59 pm deeptec...@gmail.com wrote:
>> On Mon, Jun 6, 2011 at 4:52 PM, John Baldwin wrote:
>> > Can you try out this change. It is a possible "real" solution (or at
> least a
&g
On Wed, Jun 8, 2011 at 7:56 PM, John Baldwin wrote:
> Hmmm, can you revert all your changes to pci_pci.c
let me note that so far i had at most 1 of the (4) patches applied at
a time (always the last one). if u'd like me to apply "multiple"
patches, please send 1 combined patch.
__
On Wed, Jun 8, 2011 at 7:56 PM, John Baldwin wrote:
> On Wednesday, June 08, 2011 11:20:17 am deeptec...@gmail.com wrote:
>> On Tue, Jun 7, 2011 at 4:35 PM, John Baldwin wrote:
>> found-> vendor=0x1002, dev=0x4170, revid=0x00
>> domain=0, bus=1, slot=0, func=1
On Thu, Jun 9, 2011 at 3:22 PM, John Baldwin wrote:
> Hmm, I would say 'progress' actually as it's getting better:
>
>
>> map[10]: type Prefetchable Memory, range 32, base 0xe000, size 28,
>> enabled
>> pcib1: attempting to grow prefetch window for
>> (0xe000-0xefff,0x1000)
On Thu, Jun 9, 2011 at 8:56 PM, John Baldwin wrote:
> On Thursday, June 09, 2011 2:07:31 pm deeptec...@gmail.com wrote:
>> pcib1: attempting to grow prefetch window for
>> (0xe000-0xefff,0x1000)
>> back candidate range: 0xe000-0xefff
>> pci
the FreeBSD Developers' Handbook recommends /var/crash to have
drwx-- permissions [1]. ``make installworld'' alters those
permissions to drwxr-x---. one of the two is trolling. which one?
[1]
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBT
(i intend the discussion to take place primarily on the
freebsd-hackers list, i'm CCing the freebsd-current list for a reason
stated below.)
(original first post:
http://lists.freebsd.org/pipermail/freebsd-questions/2011-June/231301.html)
On Mon, Jul 4, 2011 at 4:20 PM, Lowell Gilbert wrote:
> Y
as of recent times, some git rebase operations fail unexpectedly with
an error: "cannot create .git/index.lock: file exists". an
investigation session was something like the following:
$ ls -l .git
the index.lock file is not in the shown list.
$ ls -l .git/index.lock
the file is listed! it's a regu
On Mon, Aug 8, 2011 at 12:57 AM, Doug Barton wrote:
> On 08/06/2011 23:08, deeptec...@gmail.com wrote:
>> i'd note that the hard drive is kind of old (>7 years), and i recently
>> had the power cut during port build operations twice, although the
>> (UFS) filesyste
in the following kernel configuration (notably without ``device
bfp''), i get the following kernel build error. which is either a bug,
or not; just posting in case it's in someone's interest.
build log snippet begins
===> pfsync (all)
cc -O2 -fno-strict-aliasing -pipe -march=pen
33 matches
Mail list logo
