Re: boot fails "Can't stat /dev/da0a: No such file or directory"

2016-05-01 Thread Dave Males 
On 30/04/2016 06:53 PM, Graham Menhennitt wrote:
> Hi all,
>
> I have a USB disk that I use for backup. Up till now, it's mounted
> without any problems at boot time. After updating to -current as of
> yesterday, it doesn't mount and causes the boot to fail.
>
> My /etc/fstab looks like:
>
> # DeviceMountpointFStypeOptionsDumpPass#
>
> /dev/ada0s1a/ufsrw11
> /dev/ada0s1bnoneswapsw00
> /dev/da0a/backupufsrw,late11
>
>
> I tried adding the "late" to fix the problem, but it doesn't help.
>
> The error message is:
>
> /dev/ada0s1a: clean...
> Can't stat /dev/da0a: No such file or directory
> Unknown error; help!
> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>
>
> (hand transcribed - maybe typos)
>
> Can anybody help, please.
>
> Thanks,
> Graham
>Sorry, I forgot to mention...
>
>I commented out that line from fstab which allows the boot to complete.
>I can then manually mount it without any problems. It looks like the
>device doesn't get created early enough.
>
>Graham
Hi,

I had the same error message with a USB storage drive, so I used 
kern.cam.boot_delay="1" in /boot/loader.conf with success.
My /etc/fstab is /dev/da1p1  /mnt/usb1   ufs rw  2   2
Have a look at /boot/defaults/loader.conf under Kernel tunables.

Dave
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

2016-05-01 Thread Glen Barber 
Despite my dissatisfaction with this status update, I'll reply to an
email in public...

On Sun, May 01, 2016 at 08:16:38PM -0700, Jordan Hubbard wrote:
> 
> > On May 1, 2016, at 5:49 PM, Warren Block  wrote:
> > 
> >   The first quarter of 2016 showed that FreeBSD retains a strong sense of
> >   ipseity. Improvements were pervasive, lending credence to the concept
> >   of meliorism. [ … ]
> 
> I, for one, learned at least 4 new words in that announcement, 3
> of which were actually real.  May we all strive for greater meloristic
> ipseity!
> 
> I also applaud both your recent acquisition of a thesaurus and
> your keen appreciation of when to discard it and simply rely on
> your imagination.  it made an otherwise prosaic status report more

 ^^ Should be capitalized, as start of sentence.

> provocative!  Plaudits.
> 

Glen



signature.asc
Description: PGP signature

Re: FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

2016-05-01 Thread Brandon Allbery 
On Sun, May 1, 2016 at 10:25 PM, Kurt Buff  wrote:
>
> That's just good old fun with words, and driving people to the
> thesaurus


So what's it say about those of us who didn't need one?

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

2016-05-01 Thread Kurt Buff 
Further deponent sayeth not...

Kurt

On Sun, May 1, 2016 at 8:14 PM, Brandon Allbery  wrote:
> On Sun, May 1, 2016 at 10:25 PM, Kurt Buff  wrote:
>>
>> That's just good old fun with words, and driving people to the
>> thesaurus
>
>
> So what's it say about those of us who didn't need one?
>
> --
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com  ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

2016-05-01 Thread Kurt Buff 
Trolling? Oh heck no.

That's just good old fun with words, and driving people to the
thesaurus. After all, immediate following that was this:

 Please submit status reports for the second quarter of 2016 by July 7.
   A thesaurus will be provided for submitters who do not have one of
   their own. We will need them back afterwards, preferably with no new
   teeth marks on the covers. Thank you!

Kurt

On Sun, May 1, 2016 at 6:37 PM, Michelle Sullivan  wrote:
> Warren Block wrote:
>>
>> Introduction
>>
>>The first quarter of 2016 showed that FreeBSD retains a strong sense of
>>ipseity. Improvements were pervasive, lending credence to the concept
>>of meliorism.
>>
>>Panegyrics are relatively scarce, but not for lack of need. Perhaps
>>this missive might serve that function in some infinitesimal way.
>>
>>There was propagation, reformation, randomization, accumulation,
>>emulation, transmogrification, debuggenation, and metaphrasal during
>>this quarter.
>>
>>In the financioartistic arena, pork snout futures narrowly edged out
>>pointilism, while parietal art remained fixed.
>>
>>In all, a discomfiture of abundance. View the rubrics below, and marvel
>>at their profusion and magnitude! Marvel!
>
>
> You're trolling right?
>
> --
> Michelle Sullivan
> http://www.mhix.org/
>
>
> ___
> freebsd-sta...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

2016-05-01 Thread Michelle Sullivan 

Warren Block wrote:

Introduction

   The first quarter of 2016 showed that FreeBSD retains a strong 
sense of

   ipseity. Improvements were pervasive, lending credence to the concept
   of meliorism.

   Panegyrics are relatively scarce, but not for lack of need. Perhaps
   this missive might serve that function in some infinitesimal way.

   There was propagation, reformation, randomization, accumulation,
   emulation, transmogrification, debuggenation, and metaphrasal during
   this quarter.

   In the financioartistic arena, pork snout futures narrowly edged out
   pointilism, while parietal art remained fixed.

   In all, a discomfiture of abundance. View the rubrics below, and 
marvel

   at their profusion and magnitude! Marvel!


You're trolling right?

--
Michelle Sullivan
http://www.mhix.org/

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot fails "Can't stat /dev/da0a: No such file or directory"

2016-05-01 Thread Dave Males 
On 30/04/2016 06:53 PM, Graham Menhennitt wrote:
> Hi all,
>
> I have a USB disk that I use for backup. Up till now, it's mounted
> without any problems at boot time. After updating to -current as of
> yesterday, it doesn't mount and causes the boot to fail.
>
> My /etc/fstab looks like:
>
> # DeviceMountpointFStypeOptionsDumpPass#
>
> /dev/ada0s1a/ufsrw11
> /dev/ada0s1bnoneswapsw00
> /dev/da0a/backupufsrw,late11
>
>
> I tried adding the "late" to fix the problem, but it doesn't help.
>
> The error message is:
>
> /dev/ada0s1a: clean...
> Can't stat /dev/da0a: No such file or directory
> Unknown error; help!
> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>
>
> (hand transcribed - maybe typos)
>
> Can anybody help, please.
>
> Thanks,
> Graham
>Sorry, I forgot to mention...
>
>I commented out that line from fstab which allows the boot to complete.
>I can then manually mount it without any problems. It looks like the
>device doesn't get created early enough.
>
>Graham
Hi,

I had the same error message with a USB storage drive, so I used 
kern.cam.boot_delay="1" in /boot/loader.conf with success.
My /etc/fstab is /dev/da1p1  /mnt/usb1   ufs rw  2   2
Have a look at /boot/defaults/loader.conf under Kernel tunables.

Dave

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

FreeBSD Quarterly Status Report - First Quarter 2016 (fwd)

2016-05-01 Thread Warren Block 

Introduction

   The first quarter of 2016 showed that FreeBSD retains a strong sense of
   ipseity. Improvements were pervasive, lending credence to the concept
   of meliorism.

   Panegyrics are relatively scarce, but not for lack of need. Perhaps
   this missive might serve that function in some infinitesimal way.

   There was propagation, reformation, randomization, accumulation,
   emulation, transmogrification, debuggenation, and metaphrasal during
   this quarter.

   In the financioartistic arena, pork snout futures narrowly edged out
   pointilism, while parietal art remained fixed.

   In all, a discomfiture of abundance. View the rubrics below, and marvel
   at their profusion and magnitude! Marvel!

   --Warren Block
 __

   Please submit status reports for the second quarter of 2016 by July 7.
   A thesaurus will be provided for submitters who do not have one of
   their own. We will need them back afterwards, preferably with no new
   teeth marks on the covers. Thank you!
 __

FreeBSD Team Reports

 * Cluster Admin
 * The FreeBSD Core Team

Projects

 * Address Space Layout Randomization
 * Ceph on FreeBSD
 * Process-Shared Locks for libthr
 * RCTL Disk IO Limits
 * The Graphics Stack on FreeBSD

Kernel

 * ARM Allwinner SoC Support
 * CAM I/O Scheduler
 * FDT Overlay Support in UBLDR
 * Filemon Performance/Stability Improvements
 * FreeBSD Integration Services (BIS)
 * Infiniband
 * MMC Stack Under CAM Framework
 * NFS Server
 * Static Analysis of the FreeBSD Kernel with PVS Studio

Architectures

 * AmigaOne X5000 Support
 * FreeBSD on Cavium ThunderX (arm64)
 * powerpcspe Target

Userland Programs

 * ELF Tool Chain Tools
 * Native PCI-express HotPlug
 * Updates to GDB
 * Using lld, the LLVM Linker, to Link FreeBSD

Ports

 * GitLab Port
 * GNOME on FreeBSD
 * KDE on FreeBSD
 * Obsoleting Rails 3
 * Ports Collection

Documentation

 * New FreeBSD Mastery Books
 * Spanish FAQ and Chinese Porter's Handbook Translations

Miscellaneous

 * FreeBSD Build
 * Qt 5.6 on Raspberry Pi
 * The FreeBSD Foundation
 __

FreeBSD Team Reports

Cluster Admin

   Contact: 

   This quarter, we:
 * migrated services out of the hosting space in ISC (peter, sbruno)
 * began migration of services into the RootBSD hosting space (peter,
   sbruno)
 * collaborated with the phabricator admin team to migrate to a new
   and improved host in NYI. (allanjude, peter, sbruno)
 * installed a new and beefier Jenkins machine (gnn, lwshu, sbruno)
 * are still looking for more Asian mirrors for pkg, svn, and ftp
   (Japan, India). (sbruno)
 * completed the migration of the Taiwanese mirror to its new
   location. (lwshu)
 * started hosting a clang/llvm buildbbot in the FreeBSD cluster at
   NYI (sbruno, emaste)
 * resolved a UK mirror outage with Bytemark (gavin, peter)
 __

The FreeBSD Core Team

   Contact: FreeBSD Core Team 

   During the first quarter of 2016, the most important business of the
   FreeBSD Core Team has been to respond to the harassment incident last
   year. Core's actions were to assemble a timeline of the events and in
   the light of that to review Core's actions at the time; and to make
   recommendations about how better to handle such cases in future. During
   this process, draft reports were reviewed by people concerned in the
   case and in addition a number of interested members of the FreeBSD
   community. Core would like to thank everyone involved for their
   contributions.

   The report was published to the FreeBSD developer community in
   mid-February, and contained six recommendations for the community to
   consider.

   Core is also coordinating with the committee headed by Anne Dickison
   who are reviewing the Code of Conduct. A corpus of case studies is
   being assembled, which will be re-examined to see what impact changes
   to the Code of Conduct would have had.

   Core, together with John Baldwin, are working on a plan to create a
   separate repository containing GPLv3 toolchain components. This will
   allow modernization of code within base beyond what the existing GPLv2
   toolchain can handle, and permit support of certain new architectures
   where a copyfree licensed alternative (i.e., LLVM) is not yet
   available. A position paper will soon be circulated to developers for
   comment.

   During this quarter three new commit bits were issued, and one was
   returned for safekeeping. Please welcome Wojciech Macek, Jared McNeil
   and Stanislav Galabov, and bid farewell to

Re: boot fails "Can't stat /dev/da0a: No such file or directory"

2016-05-01 Thread Graham Menhennitt 
On 30/04/2016 06:53 PM, Graham Menhennitt wrote:
> Hi all,
>
> I have a USB disk that I use for backup. Up till now, it's mounted
> without any problems at boot time. After updating to -current as of
> yesterday, it doesn't mount and causes the boot to fail.
>
> My /etc/fstab looks like:
>
> # DeviceMountpointFStypeOptionsDumpPass#
>
> /dev/ada0s1a/ufsrw11
> /dev/ada0s1bnoneswapsw00
> /dev/da0a/backupufsrw,late11
>
>
> I tried adding the "late" to fix the problem, but it doesn't help.
>
> The error message is:
>
> /dev/ada0s1a: clean...
> Can't stat /dev/da0a: No such file or directory
> Unknown error; help!
> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>
>
> (hand transcribed - maybe typos)
>
> Can anybody help, please.
>
> Thanks,
> Graham
Sorry, I forgot to mention...

I commented out that line from fstab which allows the boot to complete.
I can then manually mount it without any problems. It looks like the
device doesn't get created early enough.

Graham
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot install the r298793 snapshot image

2016-05-01 Thread Shawn Debnath 
On 05/01, Shawn Debnath wrote:
> On 05/01, RayCherng Yu wrote:
> > I installed the r299793 memstick.img and got this error message:
> > 
> > http://imgur.com/HktHn6b
> > 
> > Then I installed the mini-memstick.img instead. I got another error message:
> > 
> > http://imgur.com/dOPO83t
> > 
> 
> How are you trying to do the install?

Sorry, early here and haven't had my coffee yet. I would suggest trying a
different USB stick for the installation first. Not an expert but memstick
based installations are the finickiest of them all.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot install the r298793 snapshot image

2016-05-01 Thread Shawn Debnath 
On 05/01, RayCherng Yu wrote:
> I installed the r299793 memstick.img and got this error message:
> 
> http://imgur.com/HktHn6b
> 
> Then I installed the mini-memstick.img instead. I got another error message:
> 
> http://imgur.com/dOPO83t
> 

How are you trying to do the install?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: MCA unrecoverable machine check exception on APU2

2016-05-01 Thread Shawn Debnath 
On 05/01, Dimitry Andric wrote:
> On 01 May 2016, at 14:35, Shawn Webb  wrote:

> > MCA: Bank 0, Status 0xb4000135
> > MCA: Global Cap 0x0106, Status 0x0004
> > MCA: Vendor "AuthenticAMD", ID 0x730f01, APIC ID 3
> > MCA: CPU 3 UNCOR DCACHE L1 DRD error
> > MCA: Address 0x44e9830
> > panic: Unrecoverable machine check exception
> > cpuid = 3
> > KDB: stack backtrace:
> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 
> > 0xfe00f53cb390
> > vpanic() at vpanic+0x182/frame 0xfe00f53cb410
> > panic() at panic+0x43/frame 0xfe00f53cb470
> > mca_intr() at mca_intr+0x6b/frame 0xfe00f53cb490

Could you try sysutils/mcelog and see if you can get some meaningful
output? See: https://www.freshports.org/sysutils/mcelog/

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: MCA unrecoverable machine check exception on APU2

2016-05-01 Thread Dimitry Andric 
On 01 May 2016, at 14:35, Shawn Webb  wrote:
> 
> I'm getting this panic. I'm not sure if it's a problem with the OS or
> the hardware as this is a bit too low-level for me. Here's the dmesg
> output along with the stack trace:
> 
> MCA: Bank 0, Status 0xb4000135
> MCA: Global Cap 0x0106, Status 0x0004
> MCA: Vendor "AuthenticAMD", ID 0x730f01, APIC ID 3
> MCA: CPU 3 UNCOR DCACHE L1 DRD error
> MCA: Address 0x44e9830
> panic: Unrecoverable machine check exception
> cpuid = 3
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00f53cb390
> vpanic() at vpanic+0x182/frame 0xfe00f53cb410
> panic() at panic+0x43/frame 0xfe00f53cb470
> mca_intr() at mca_intr+0x6b/frame 0xfe00f53cb490
> trap() at trap+0xa8/frame 0xfe00f53cb6a0
> calltrap() at calltrap+0x8/frame 0xfe00f53cb6a0
> --- trap 0x1c, rip = 0x80b6ffe1, rsp = 0xfe00f53cb770, rbp = 
> 0xfe00f53cb7f0 ---
> callout_process() at callout_process+0x131/frame 0xfe00f53cb7f0
> handleevents() at handleevents+0x16d/frame 0xfe00f53cb830
> timercb() at timercb+0x227/frame 0xfe00f53cb880
> lapic_handle_timer() at lapic_handle_timer+0x9f/frame 0xfe00f53cb8c0
> Xtimerint() at Xtimerint+0x8c/frame 0xfe00f53cb8c0
> --- interrupt, rip = 0x80b85a39, rsp = 0xfe00f53cb990, rbp = 
> 0xfe00f53cba70 ---
> sched_idletd() at sched_idletd+0x439/frame 0xfe00f53cba70
> fork_exit() at fork_exit+0x84/frame 0xfe00f53cbab0
> fork_trampoline() at fork_trampoline+0xe/frame 0xfe00f53cbab0
> --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
> KDB: enter: panic
> [ thread pid 11 tid 16 ]
> Stopped at  kdb_enter+0x3b: movq$0,kdb_why
> db>
> 
> This is running HardenedBSD 11-CURRENT/amd64 on the PC-Engines APU2. Is
> this worth filing a bug report upstream with FreeBSD or is this a
> hardware bug?

Hi Shawn,

This particular part seems to indicate a hardware problem:

MCA: Vendor "AuthenticAMD", ID 0x730f01, APIC ID 3
MCA: CPU 3 UNCOR DCACHE L1 DRD error
MCA: Address 0x44e9830
panic: Unrecoverable machine check exception

I'm not a MCE expert, but it looks like core 3 got an uncorrectable L1
data cache error.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Cannot install the r298793 snapshot image

2016-05-01 Thread RayCherng Yu 
I installed the r299793 memstick.img and got this error message:

http://imgur.com/HktHn6b

Then I installed the mini-memstick.img instead. I got another error message:

http://imgur.com/dOPO83t



-- 
"Life is like a snowball. The important thing is finding wet snow and a
really long hill."

"Price is what you pay. Value is what you get."

"The first rule of Investing is don't lose money; the second rule is don't
forget rule #1..."

"Wall Street is the only place that people ride to work in a Rolls-Royce to
get advice from those who take the subway..."


— Warren Buffett.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

MCA unrecoverable machine check exception on APU2

2016-05-01 Thread Shawn Webb 
Hey All,

I'm getting this panic. I'm not sure if it's a problem with the OS or
the hardware as this is a bit too low-level for me. Here's the dmesg
output along with the stack trace:

MCA: Bank 0, Status 0xb4000135
MCA: Global Cap 0x0106, Status 0x0004
MCA: Vendor "AuthenticAMD", ID 0x730f01, APIC ID 3
MCA: CPU 3 UNCOR DCACHE L1 DRD error
MCA: Address 0x44e9830
panic: Unrecoverable machine check exception
cpuid = 3
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00f53cb390
vpanic() at vpanic+0x182/frame 0xfe00f53cb410
panic() at panic+0x43/frame 0xfe00f53cb470
mca_intr() at mca_intr+0x6b/frame 0xfe00f53cb490
trap() at trap+0xa8/frame 0xfe00f53cb6a0
calltrap() at calltrap+0x8/frame 0xfe00f53cb6a0
--- trap 0x1c, rip = 0x80b6ffe1, rsp = 0xfe00f53cb770, rbp = 
0xfe00f53cb7f0 ---
callout_process() at callout_process+0x131/frame 0xfe00f53cb7f0
handleevents() at handleevents+0x16d/frame 0xfe00f53cb830
timercb() at timercb+0x227/frame 0xfe00f53cb880
lapic_handle_timer() at lapic_handle_timer+0x9f/frame 0xfe00f53cb8c0
Xtimerint() at Xtimerint+0x8c/frame 0xfe00f53cb8c0
--- interrupt, rip = 0x80b85a39, rsp = 0xfe00f53cb990, rbp = 
0xfe00f53cba70 ---
sched_idletd() at sched_idletd+0x439/frame 0xfe00f53cba70
fork_exit() at fork_exit+0x84/frame 0xfe00f53cbab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe00f53cbab0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 11 tid 16 ]
Stopped at  kdb_enter+0x3b: movq$0,kdb_why
db>

This is running HardenedBSD 11-CURRENT/amd64 on the PC-Engines APU2. Is
this worth filing a bug report upstream with FreeBSD or is this a
hardware bug?

Thanks,

-- 
Shawn Webb
HardenedBSD

GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature