When I am using mercurial to initialize a freebsd repository, it prints
"warning: filename ends with '.', which is not allowed on Windows:
'tools/test/sort/bigtest/q-1.024.003.'
it seems filename ended with a dot is illegal on Windows, if someone
wants to check out freebsd source code on Window
>From b...@0x20.net Thu Mar 6 22:02:56 2014
>
>On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote:
>> In my initial PR (sparc64 r261798),
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
>>
>> I said that rsync was triggering this panic.
>> While true, I now see that ther
On Thu, Mar 6, 2014, at 11:28, Lowell Gilbert wrote:
> Glen Barber writes:
>
> > On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote:
> >> >Can you go into /etc/periodic/daily and execute those scripts one by
> >> >one? You should be able to narrow down which one is the culprit.
Glen Barber writes:
> On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote:
>> >Can you go into /etc/periodic/daily and execute those scripts one by
>> >one? You should be able to narrow down which one is the culprit.
>>
>> unfortunately I cannot reproduce the panic
>> this way. Wh
On Thu, Mar 06, 2014 at 09:12:36AM +0100, O. Hartmann wrote:
O> > Obviously not. I patched the kernel sources of a box in question and
O> > the kernel has now r262821. The panic is gone, but there is nonetwork
O> > although the interface is up, the firewall is up (IPWF) and even
O> > netstat -rn sh
On 6 Mar 2014, at 16:53, Dimitry Andric wrote:
> Now on a side note, it would be very nice if our kernel debugging
> extensions were ported to the ports version of gdb, which is
> non-ancient... :-)
I believe that emaste has an lldb-based kgdb replacement on his todo list,
although not yet quit
On 06 Mar 2014, at 17:33, Lev Serebryakov wrote:
> CURRENT r262833, kernel from custom config (with symbols ad debugging
> info), crash.
>
> savecore says "Unable to find matching kernel"
>
> kgdb /var/crash/vmcore.1 /boot/kerne/kernel says:
>
> Dwarf Error: wrong version in compilation unit he
Hello, Freebsd-current.
CURRENT r262833, kernel from custom config (with symbols ad debugging
info), crash.
savecore says "Unable to find matching kernel"
kgdb /var/crash/vmcore.1 /boot/kerne/kernel says:
Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in
module
On Thu, Mar 06, 2014 at 08:07:14AM -0800, Anton Shterenlikht wrote:
> >>From g...@freebsd.org Thu Mar 6 15:58:51 2014
> >
> >On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote:
> >> >Can you go into /etc/periodic/daily and execute those scripts one by
> >> >one? You should be able
>From g...@freebsd.org Thu Mar 6 15:58:51 2014
>
>On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote:
>> >Can you go into /etc/periodic/daily and execute those scripts one by
>> >one? You should be able to narrow down which one is the culprit.
>>=20
>> unfortunately I cannot reprod
On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote:
> >Can you go into /etc/periodic/daily and execute those scripts one by
> >one? You should be able to narrow down which one is the culprit.
>
> unfortunately I cannot reproduce the panic
> this way. What I did was:
>
> # cd /etc/
>From: Mark Felder
>
>On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote:
>> In my initial PR (sparc64 r261798),
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
>>
>> I said that rsync was triggering this panic.
>> While true, I now see that there's more to it.
>> I disabled the rsy
On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote:
> In my initial PR (sparc64 r261798),
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
>
> I said that rsync was triggering this panic.
> While true, I now see that there's more to it.
> I disabled the rsync, and the cron jobs.
> Sti
> > Does this mean the bug is fixed in 11-current?
> Yes, the bug is fixed in 11-CURRENT, as of Subversion revision r262809.
> > MFC? Is that to 10-STABLE? Your message is less than clear.
> In FreeBSD, fixes are first applied to head (a.k.a -CURRENT), then
> a
In message <1611.1394047...@critter.freebsd.dk>, Poul-Henning Kamp writes:
>
>Just tried a current kernel -r 262780 on my laptop.
>
>When wlan0 comes up (if_iwn) it explodes with something about witness
>and rtentry.c, but it clears the screen before I can get a photo...
-r262832 works.
--
Poul-
In my initial PR (sparc64 r261798),
http://www.freebsd.org/cgi/query-pr.cgi?pr=187080
I said that rsync was triggering this panic.
While true, I now see that there's more to it.
I disabled the rsync, and the cron jobs.
Still I get exactly the same panic every
night at 03:02:
# grep Dumptime /va
Am 06.03.2014 08:35, schrieb M&S - Krasznai András:
> Hi
>
> I am using freebsd 10 64bit on an IBM T510.
>
> I can not mount ntfs partition from /etc/fstab with the normal method, thatis
> specifying
>
> /dev/ada0s2 /windows/C ntfs-3g ro 0
> 0
F
On Thu, 6 Mar 2014 08:43:07 +0100
"O. Hartmann" wrote:
> On Thu, 6 Mar 2014 08:37:59 +0300
> "Sergey V. Dyatko" wrote:
>
> > В Thu, 6 Mar 2014 12:47:07 +0800
> > 乔楚 пишет:
> >
> > > I have the same panic.
> > > Panic at net use.
> > > ping , svn, etc...
> >
> > It is fixed on r262806
> >
>
18 matches
Mail list logo
