Hi there,
2016-05-27 4:12 GMT+02:00 Ngie Cooper :
> It seems like the following /etc/exports should work, but for some
> odd reason specifying both paths on a single line doesn't work (I
> swore it was working on a kernel/userland built in the past month,
> i.e. ^/head@r297950, but I might be
FreeBSD_HEAD_i386 - Build #3223 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3223/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3223/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3223/console
Change summaries:
300
FreeBSD_HEAD_i386 - Build #3222 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3222/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3222/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3222/console
Change summaries:
3
Hi,
It seems like the following /etc/exports should work, but for some
odd reason specifying both paths on a single line doesn't work (I
swore it was working on a kernel/userland built in the past month,
i.e. ^/head@r297950, but I might be misremembering things).
exports(5) claims that 2 mo
On Tuesday, May 17, 2016 06:47:41 PM Gary Jennejohn wrote:
> On Mon, 16 May 2016 10:54:19 -0700
> John Baldwin wrote:
>
> > On Monday, May 16, 2016 12:22:42 PM Gary Jennejohn wrote:
> > > I tried out EARLY_AP_STARTUP, but the kernel hangs and I can't
> > > break into DDB.
> > >
> > > I did a ver
On Thu, 26 May 2016 16:08:03 -0700 Eric McCorkle
wrote
> Letting you know, I had an error in detection. I'm trying to get a change
> done before code slush, but I will circle back and provide a detailed report
>
Thanks. I'm not going to make slush for the changes to sys to
Letting you know, I had an error in detection. I'm trying to get a change done
before code slush, but I will circle back and provide a detailed report
On May 23, 2016 4:12:52 AM EDT, Matthew Macy wrote:
>
>The highlights for today are the following:
>
>Bug fixes:
>- Will Andrews fixed attach f
Graham,
> Last night I updated to the latest -current source and did a build of world
> and kernel. The problem seems to have disappeared! So, either there was
> something broken in the source when I did my previous update, or something
> went wrong in my last build/install. Either way, it's all w
On 27/05/2016 12:27 AM, Maksim Yevmenkin wrote:
please modify /etc/rc.d/bluetooth and make sure it does not exit when
hci reset command fails? it would be useful to know if any other hci
commands fail.
Max,
Last night I updated to the latest -current source and did a build of
world and kernel
On Thu, May 26, 2016 at 11:55:08AM -0300, Otacílio wrote:
> Em 26/05/2016 11:49, Baptiste Daroussin escreveu:
> > On Thu, May 26, 2016 at 09:44:25AM -0500, Eric van Gyzen wrote:
> >> Baptiste and -current,
> >>
> >> I noticed two annoyances with date formatting on head, and I wonder how
> >> we can
Em 26/05/2016 11:49, Baptiste Daroussin escreveu:
On Thu, May 26, 2016 at 09:44:25AM -0500, Eric van Gyzen wrote:
Baptiste and -current,
I noticed two annoyances with date formatting on head, and I wonder how
we can fix them.
I have these settings:
LC_ALL=en_US.ISO8859-1
LANG=en_US.
On Thu, May 26, 2016 at 09:44:25AM -0500, Eric van Gyzen wrote:
> Baptiste and -current,
>
> I noticed two annoyances with date formatting on head, and I wonder how
> we can fix them.
>
> I have these settings:
>
> LC_ALL=en_US.ISO8859-1
> LANG=en_US.ISO8859-1
>
> First, Thunderbird dis
On Thu, May 26, 2016 at 16:42:10 +0200, Gary Jennejohn wrote:
> On Thu, 26 May 2016 10:10:14 -0400
> "Kenneth D. Merry" wrote:
>
> > On Thu, May 26, 2016 at 16:00:41 +0200, Gary Jennejohn wrote:
> > > protocol ATA/ATAPI-9 SATA 3.x
> > > device model ST8000AS0002-1NA17Z
> > >
Baptiste and -current,
I noticed two annoyances with date formatting on head, and I wonder how
we can fix them.
I have these settings:
LC_ALL=en_US.ISO8859-1
LANG=en_US.ISO8859-1
First, Thunderbird displays the date as, for example:
03/ 6/16 ...
The leading space on the day (6) lo
On Thu, 26 May 2016 10:10:14 -0400
"Kenneth D. Merry" wrote:
> On Thu, May 26, 2016 at 16:00:41 +0200, Gary Jennejohn wrote:
> > protocol ATA/ATAPI-9 SATA 3.x
> > device model ST8000AS0002-1NA17Z
> > firmware revision AR13
>
> The firmware is old, the current version
Graham,
can you also please try to start it manually and see where it stops?
i.e. something like
# sh -x /etc/rc.d/bluetooth start ubt0
>>>
>>> Thanks for responding. The output of that command is below. I'll do some
>>> more diagnosis when I get home tonight.
>>
>> + /usr/sbin
On Thu, May 26, 2016 at 15:02:24 +0100, Igor Mozolevsky wrote:
> On 26 May 2016 at 14:41, Kenneth D. Merry wrote:
>
> > On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > > On Thu, 26 May 2016 08:34:45 -0400
> > > "Kenneth D. Merry" wrote:
> > >
> > > > On Thu, May 26, 2016 at 08:
On Thu, May 26, 2016 at 16:00:41 +0200, Gary Jennejohn wrote:
> On Thu, 26 May 2016 09:41:20 -0400
> "Kenneth D. Merry" wrote:
>
> > On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > > On Thu, 26 May 2016 08:34:45 -0400
> > > "Kenneth D. Merry" wrote:
> > >
> > > > On Thu, May
On 26 May 2016 at 14:41, Kenneth D. Merry wrote:
> On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > On Thu, 26 May 2016 08:34:45 -0400
> > "Kenneth D. Merry" wrote:
> >
> > > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > > What kind of drive is it?
> > >
> >
On Thu, 26 May 2016 09:41:20 -0400
"Kenneth D. Merry" wrote:
> On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> > On Thu, 26 May 2016 08:34:45 -0400
> > "Kenneth D. Merry" wrote:
> >
> > > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > > What kind of drive is
On Thu, May 26, 2016 at 15:29:21 +0200, Gary Jennejohn wrote:
> On Thu, 26 May 2016 08:34:45 -0400
> "Kenneth D. Merry" wrote:
>
> > On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> > What kind of drive is it?
> >
>
> ST8000AS 0002-1NA17Z 0X03
Can you send the output of 'camcont
On Thu, 26 May 2016 08:34:45 -0400
"Kenneth D. Merry" wrote:
> On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> What kind of drive is it?
>
ST8000AS 0002-1NA17Z 0X03
> Here are some things you can do on any disk to see what it is:
>
> diskinfo -v /dev/daX
>
I don't have the n
On Thu, May 26, 2016 at 08:42:53 +0200, Gary Jennejohn wrote:
> Now that ken@ has checked in the SMR code I'm wondering how I can see
> whether it's having any effect.
>
> I have a 8TB SMR disk in a USB3 enclosure. Does the kernel emit any
> sort of trace to indicate that it sees the drive as SMR
Le 26/05/2016 11:06, K. Macy a écrit :
It will be fixed in the next iflib update.
Nice, thank you.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curr
Em qui, 26 de mai de 2016 06:01, Juan Ramón Molina Menor
escreveu:
> Hi!
>
> In three different machines running HEAD I have this message in the very
> first lines of the dmesg output:
>
> can't reuse a leaf (ixl_rx_miss_bufs)!
>
> I don’t remember seeing it before and I have not configured any i
It will be fixed in the next iflib update.
On Thursday, May 26, 2016, Juan Ramón Molina Menor wrote:
> Hi!
>
> In three different machines running HEAD I have this message in the very
> first lines of the dmesg output:
>
> can't reuse a leaf (ixl_rx_miss_bufs)!
>
> I don’t remember seeing it bef
Hi!
In three different machines running HEAD I have this message in the very
first lines of the dmesg output:
can't reuse a leaf (ixl_rx_miss_bufs)!
I don’t remember seeing it before and I have not configured any ixl
device. It seems harmless, but I wonder if it’s a sign of a bug somewhere.
On 2016-May-26 08:42:53 +0200, Gary Jennejohn wrote:
>Now that ken@ has checked in the SMR code I'm wondering how I can see
>whether it's having any effect.
camcontrol(8) has been enhanced with SMR options and there's a new
zonectl(8) command - these should be able to report whether the drive
is
28 matches
Mail list logo