FreeBSD_STABLE_10-i386 - Build #346 - Failure

2015-08-03 Thread jenkins-admin 
FreeBSD_STABLE_10-i386 - Build #346 - Failure:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/346/
Full change log: 
https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/346/changes
Full build log: 
https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/346/console

Change summaries:

No changes


The end of the build log:

Started by an SCM change
Building remotely on kyua5.nyi.freebsd.org (jailer) in workspace 
/jenkins/workspace/FreeBSD_STABLE_10-i386
FATAL: java.io.EOFException
hudson.remoting.RequestAbortedException: java.io.EOFException
at hudson.remoting.Request.abort(Request.java:296)
at hudson.remoting.Channel.terminate(Channel.java:815)
at 
org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to kyua5.nyi.freebsd.org(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361)
at hudson.remoting.Request.call(Request.java:171)
at hudson.remoting.Channel.call(Channel.java:752)
at hudson.FilePath.act(FilePath.java:980)
at hudson.FilePath.act(FilePath.java:969)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1282)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:381)
Caused by: java.io.EOFException
at 
org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[WARNINGS] Skipping publisher since build result is FAILURE
[PostBuildScript] - Execution post build scripts.
ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node 
hudson.slaves.DumbSlave[kyua5.nyi.freebsd.org] which is computer 
hudson.slaves.SlaveComputer@66ee6762 and has channel null
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:76)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript.processBuildSteps(PostBuildScript.java:204)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript.processScripts(PostBuildScript.java:143)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript._perform(PostBuildScript.java:105)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript.perform(PostBuildScript.java:85)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)
at hudson.model.Build$BuildExecution.post2(Build.java:185)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)
at hudson.model.Run.execute(Run.java:1766)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hud

FreeBSD_STABLE_9-i386 - Build #121 - Failure

2015-08-03 Thread jenkins-admin 
FreeBSD_STABLE_9-i386 - Build #121 - Failure:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/121/
Full change log: 
https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/121/changes
Full build log: 
https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/121/console

Change summaries:

No changes


The end of the build log:

Started by an SCM change
Building remotely on kyua1.nyi.freebsd.org (jailer) in workspace 
/jenkins/workspace/FreeBSD_STABLE_9-i386
FATAL: java.io.EOFException
hudson.remoting.RequestAbortedException: java.io.EOFException
at hudson.remoting.Request.abort(Request.java:296)
at hudson.remoting.Channel.terminate(Channel.java:815)
at 
org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to kyua1.nyi.freebsd.org(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361)
at hudson.remoting.Request.call(Request.java:171)
at hudson.remoting.Channel.call(Channel.java:752)
at hudson.FilePath.act(FilePath.java:980)
at hudson.FilePath.act(FilePath.java:969)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1282)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:381)
Caused by: java.io.EOFException
at 
org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[PostBuildScript] - Execution post build scripts.
ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node 
hudson.slaves.DumbSlave[kyua1.nyi.freebsd.org] which is computer 
hudson.slaves.SlaveComputer@495527eb and has channel null
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:76)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript.processBuildSteps(PostBuildScript.java:204)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript.processScripts(PostBuildScript.java:143)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript._perform(PostBuildScript.java:105)
at 
org.jenkinsci.plugins.postbuildscript.PostBuildScript.perform(PostBuildScript.java:85)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)
at hudson.model.Build$BuildExecution.post2(Build.java:185)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)
at hudson.model.Run.execute(Run.java:1766)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)

Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2

2015-08-03 Thread Freddie Cash 
On Aug 3, 2015 8:36 AM, "Paul Mather" 
wrote:
>
> On Aug 3, 2015, at 11:09 AM, Alban Hertroys  wrote:
>
> > On 3 August 2015 at 15:01, Paul Mather 
wrote:
> >> On Aug 2, 2015, at 9:34 PM, Adam McDougall 
wrote:
> >>
> >>> On 08/02/2015 21:22, Paul Mather wrote:
>  I have a 4TB external USB drive (Western Digital My Book 1230) that
I am trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052:
Wed Jul 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX)
motherboard.
> 
>  The drive probes unreliably when plugged in to a USB 3 port.  It
reliably probes when plugged into a USB 2 port.  However, it works in
neither cases.  Attempting to dd from the drive results in a "dd: /dev/da0:
Invalid argument".
> >
> > FYI: I had been experiencing the same with a 2 TB WD MyBook on OS X
> > (Mavericks). The drive was being used for Time Machine backups, but it
> > would at irregular intervals it would just 'disconnect' itself. My
> > guess is that there's a firmware problem in the USB3 chip in those
> > drives.
> >
> > After trying to get the issue fixed for almost half a year I returned
> > it and replaced it by a Seagate, which has been working flawlessly
> > ever since.
> >
> > I'm just saying, perhaps the problem isn't with FreeBSD but with the
drive.
>
>
> I'd love just to get to the "randomly disconnects" stage under FreeBSD at
this point. :-)
>
> Up to now, I have been unable to read ANY data off the drive under
FreeBSD, either via USB 2 or USB 3. :-(
>
> However, you have given me something to think about: does anyone know of
a 4 TB USB 2 or 3 drive that will work reliably under FreeBSD 10-STABLE
right now?

2 TB Toshiba drive in a NexStar 6G enclosure, and a 3 TB WD Black drives in
a NexStar 3 enclosures are working great on FreeBSD 9.3 (home), 8.1 (work)
and 10.0 (work). USB 2.x and 3.0. I use them as ZFS backups drives.

I've never liked the all-in-one external drives. I prefer separate
enclosures and drives. That way, the drives can be replaced or upgraded as
needed.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2

2015-08-03 Thread Paul Mather 
On Aug 3, 2015, at 12:17 PM, Jack Vogel  wrote:
> 
> Have you tried it on HEAD, and have you tried it on the same system with some
> recent flavor of Linux?

No, and no.  It's a good idea, though.  I can try it this weekend, if I can run 
each OS via a USB memstick.

With this being such a commonplace drive, I'd hoped someone might pipe up and 
say something along the lines of, "oh, you have to add USB quirk XYZ to get 
that model working under FreeBSD."  No such luck, it seems.

Cheers,

Paul.

>  
> 
> Jack
> 
> 
> On Mon, Aug 3, 2015 at 8:35 AM, Paul Mather  > wrote:
> On Aug 3, 2015, at 11:09 AM, Alban Hertroys  > wrote:
> 
> > On 3 August 2015 at 15:01, Paul Mather  > > wrote:
> >> On Aug 2, 2015, at 9:34 PM, Adam McDougall  >> > wrote:
> >>
> >>> On 08/02/2015 21:22, Paul Mather wrote:
>  I have a 4TB external USB drive (Western Digital My Book 1230) that I am 
>  trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052: Wed 
>  Jul 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX) 
>  motherboard.
> 
>  The drive probes unreliably when plugged in to a USB 3 port.  It 
>  reliably probes when plugged into a USB 2 port.  However, it works in 
>  neither cases.  Attempting to dd from the drive results in a "dd: 
>  /dev/da0: Invalid argument".
> >
> > FYI: I had been experiencing the same with a 2 TB WD MyBook on OS X
> > (Mavericks). The drive was being used for Time Machine backups, but it
> > would at irregular intervals it would just 'disconnect' itself. My
> > guess is that there's a firmware problem in the USB3 chip in those
> > drives.
> >
> > After trying to get the issue fixed for almost half a year I returned
> > it and replaced it by a Seagate, which has been working flawlessly
> > ever since.
> >
> > I'm just saying, perhaps the problem isn't with FreeBSD but with the drive.
> 
> 
> I'd love just to get to the "randomly disconnects" stage under FreeBSD at 
> this point. :-)
> 
> Up to now, I have been unable to read ANY data off the drive under FreeBSD, 
> either via USB 2 or USB 3. :-(
> 
> However, you have given me something to think about: does anyone know of a 4 
> TB USB 2 or 3 drive that will work reliably under FreeBSD 10-STABLE right now?
> 
> Cheers,
> 
> Paul.
> 
> ___
> freebsd-stable@freebsd.org  mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable 
> 
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org 
> "
> 

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

Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2

2015-08-03 Thread Marc Santhoff 
On Mo, 2015-08-03 at 11:35 -0400, Paul Mather wrote:
> On Aug 3, 2015, at 11:09 AM, Alban Hertroys  wrote:
> 
> > On 3 August 2015 at 15:01, Paul Mather  
> > wrote:
> >> On Aug 2, 2015, at 9:34 PM, Adam McDougall  wrote:
> >> 
> >>> On 08/02/2015 21:22, Paul Mather wrote:
>  I have a 4TB external USB drive (Western Digital My Book 1230) that I am 
>  trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052: Wed 
>  Jul 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX) 
>  motherboard.
>  
>  The drive probes unreliably when plugged in to a USB 3 port.  It 
>  reliably probes when plugged into a USB 2 port.  However, it works in 
>  neither cases.  Attempting to dd from the drive results in a "dd: 
>  /dev/da0: Invalid argument".
> > 
> > FYI: I had been experiencing the same with a 2 TB WD MyBook on OS X
> > (Mavericks). The drive was being used for Time Machine backups, but it
> > would at irregular intervals it would just 'disconnect' itself. My
> > guess is that there's a firmware problem in the USB3 chip in those
> > drives.
> > 
> > After trying to get the issue fixed for almost half a year I returned
> > it and replaced it by a Seagate, which has been working flawlessly
> > ever since.
> > 
> > I'm just saying, perhaps the problem isn't with FreeBSD but with the drive.
> 
> 
> I'd love just to get to the "randomly disconnects" stage under FreeBSD
> at this point. :-)

I had a problem on 9.3R and USB drives, too. The external disk was a
"Intenso memory box 3TB". For some details look in the list archives for
a subject "USB3 disk failing on 9.3R". Sadly there is no detailed list
from usbconfig or so. But I have the empty case lying around.

I solved it by ripping the disk drive out of the case implanting it into
a cheap Logilink case, which I knew before it is actually working using
FreeBSD. The type on the sticker says "UA0107A", slightly different when
not silver but black anodized aluminium, but both do work wiht 3TB
drives for me.

The disk drive is a Toshiba DT01ACA300, working nicely.

HTH somehow,
Marc

> Up to now, I have been unable to read ANY data off the drive under
> FreeBSD, either via USB 2 or USB 3. :-(
> 
> However, you have given me something to think about: does anyone know
> of a 4 TB USB 2 or 3 drive that will work reliably under FreeBSD
> 10-STABLE right now?
> 
> Cheers,
> 
> Paul.
> 
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

-- 
Marc Santhoff 

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

Re: pkg clean question

2015-08-03 Thread Baptiste Daroussin 
On Mon, Aug 03, 2015 at 09:49:33AM -0700, jungle Boogie wrote:
> On 3 August 2015 at 09:13, Paul Mather  
> wrote:
> > On Aug 3, 2015, at 11:39 AM, Zoran Kolic  wrote:
> >
> >> Amd64, 9.3. Updated few times, packages also. At first I
> >> found on laptop that /var directory was at 102%. Using
> >> "pkg clean" i removed about 400mb of cache packages from
> >> /var/cache/pkg. Tried to clean desktop cache and the out-
> >> put of the command was "nothing to do". I see about 400
> >> mb of files in the cache directory. Is it safe to remove
> >> them by the hand?
> >
> >
> > Use "pkg clean -ay" to delete all cached packages, not just the ones that 
> > are no longer current or provided by the upstream repository.
> >
> 
> 
> You may want to autoremove, too:
> 
> autoremove
>  Delete packages which were automatically installed as dependen-
>  cies and are not required any more.
> 
> > Cheers,
> >
> > Paul.
> 
> 
Note that since recent updates of pkg there is a new AUTOCLEAN option to add in
pkg.conf which will automatically cleanup the cache after each pkg operation.

Best regards,
Bapt


pgpE1oWcrSDGk.pgp
Description: PGP signature

Re: pkg clean question

2015-08-03 Thread jungle Boogie 
On 3 August 2015 at 09:13, Paul Mather  wrote:
> On Aug 3, 2015, at 11:39 AM, Zoran Kolic  wrote:
>
>> Amd64, 9.3. Updated few times, packages also. At first I
>> found on laptop that /var directory was at 102%. Using
>> "pkg clean" i removed about 400mb of cache packages from
>> /var/cache/pkg. Tried to clean desktop cache and the out-
>> put of the command was "nothing to do". I see about 400
>> mb of files in the cache directory. Is it safe to remove
>> them by the hand?
>
>
> Use "pkg clean -ay" to delete all cached packages, not just the ones that are 
> no longer current or provided by the upstream repository.
>


You may want to autoremove, too:

autoremove
 Delete packages which were automatically installed as dependen-
 cies and are not required any more.

> Cheers,
>
> Paul.




-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg clean question

2015-08-03 Thread Zoran Kolic 
> Use "pkg clean -ay" to delete all cached packages, not just the ones that are 
> no longer current or provided by the upstream repository.

Thanks.

 Zoran

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

Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2

2015-08-03 Thread Jack Vogel 
Have you tried it on HEAD, and have you tried it on the same system with
some
recent flavor of Linux?

Jack


On Mon, Aug 3, 2015 at 8:35 AM, Paul Mather <
freebsd-li...@gromit.dlib.vt.edu> wrote:

> On Aug 3, 2015, at 11:09 AM, Alban Hertroys  wrote:
>
> > On 3 August 2015 at 15:01, Paul Mather 
> wrote:
> >> On Aug 2, 2015, at 9:34 PM, Adam McDougall 
> wrote:
> >>
> >>> On 08/02/2015 21:22, Paul Mather wrote:
>  I have a 4TB external USB drive (Western Digital My Book 1230) that I
> am trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052: Wed
> Jul 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX)
> motherboard.
> 
>  The drive probes unreliably when plugged in to a USB 3 port.  It
> reliably probes when plugged into a USB 2 port.  However, it works in
> neither cases.  Attempting to dd from the drive results in a "dd: /dev/da0:
> Invalid argument".
> >
> > FYI: I had been experiencing the same with a 2 TB WD MyBook on OS X
> > (Mavericks). The drive was being used for Time Machine backups, but it
> > would at irregular intervals it would just 'disconnect' itself. My
> > guess is that there's a firmware problem in the USB3 chip in those
> > drives.
> >
> > After trying to get the issue fixed for almost half a year I returned
> > it and replaced it by a Seagate, which has been working flawlessly
> > ever since.
> >
> > I'm just saying, perhaps the problem isn't with FreeBSD but with the
> drive.
>
>
> I'd love just to get to the "randomly disconnects" stage under FreeBSD at
> this point. :-)
>
> Up to now, I have been unable to read ANY data off the drive under
> FreeBSD, either via USB 2 or USB 3. :-(
>
> However, you have given me something to think about: does anyone know of a
> 4 TB USB 2 or 3 drive that will work reliably under FreeBSD 10-STABLE right
> now?
>
> Cheers,
>
> Paul.
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg clean question

2015-08-03 Thread Paul Mather 
On Aug 3, 2015, at 11:39 AM, Zoran Kolic  wrote:

> Amd64, 9.3. Updated few times, packages also. At first I
> found on laptop that /var directory was at 102%. Using
> "pkg clean" i removed about 400mb of cache packages from
> /var/cache/pkg. Tried to clean desktop cache and the out-
> put of the command was "nothing to do". I see about 400
> mb of files in the cache directory. Is it safe to remove
> them by the hand?


Use "pkg clean -ay" to delete all cached packages, not just the ones that are 
no longer current or provided by the upstream repository.

Cheers,

Paul.

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

pkg clean question

2015-08-03 Thread Zoran Kolic 
Amd64, 9.3. Updated few times, packages also. At first I
found on laptop that /var directory was at 102%. Using
"pkg clean" i removed about 400mb of cache packages from
/var/cache/pkg. Tried to clean desktop cache and the out-
put of the command was "nothing to do". I see about 400
mb of files in the cache directory. Is it safe to remove
them by the hand?
Best regards all

  Zoran

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

Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2

2015-08-03 Thread Paul Mather 
On Aug 3, 2015, at 11:09 AM, Alban Hertroys  wrote:

> On 3 August 2015 at 15:01, Paul Mather  
> wrote:
>> On Aug 2, 2015, at 9:34 PM, Adam McDougall  wrote:
>> 
>>> On 08/02/2015 21:22, Paul Mather wrote:
 I have a 4TB external USB drive (Western Digital My Book 1230) that I am 
 trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052: Wed 
 Jul 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX) 
 motherboard.
 
 The drive probes unreliably when plugged in to a USB 3 port.  It reliably 
 probes when plugged into a USB 2 port.  However, it works in neither 
 cases.  Attempting to dd from the drive results in a "dd: /dev/da0: 
 Invalid argument".
> 
> FYI: I had been experiencing the same with a 2 TB WD MyBook on OS X
> (Mavericks). The drive was being used for Time Machine backups, but it
> would at irregular intervals it would just 'disconnect' itself. My
> guess is that there's a firmware problem in the USB3 chip in those
> drives.
> 
> After trying to get the issue fixed for almost half a year I returned
> it and replaced it by a Seagate, which has been working flawlessly
> ever since.
> 
> I'm just saying, perhaps the problem isn't with FreeBSD but with the drive.


I'd love just to get to the "randomly disconnects" stage under FreeBSD at this 
point. :-)

Up to now, I have been unable to read ANY data off the drive under FreeBSD, 
either via USB 2 or USB 3. :-(

However, you have given me something to think about: does anyone know of a 4 TB 
USB 2 or 3 drive that will work reliably under FreeBSD 10-STABLE right now?

Cheers,

Paul.

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

Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2

2015-08-03 Thread Alban Hertroys 
On 3 August 2015 at 15:01, Paul Mather  wrote:
> On Aug 2, 2015, at 9:34 PM, Adam McDougall  wrote:
>
>> On 08/02/2015 21:22, Paul Mather wrote:
>>> I have a 4TB external USB drive (Western Digital My Book 1230) that I am 
>>> trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052: Wed Jul 
>>> 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX) motherboard.
>>>
>>> The drive probes unreliably when plugged in to a USB 3 port.  It reliably 
>>> probes when plugged into a USB 2 port.  However, it works in neither cases. 
>>>  Attempting to dd from the drive results in a "dd: /dev/da0: Invalid 
>>> argument".

FYI: I had been experiencing the same with a 2 TB WD MyBook on OS X
(Mavericks). The drive was being used for Time Machine backups, but it
would at irregular intervals it would just 'disconnect' itself. My
guess is that there's a firmware problem in the USB3 chip in those
drives.

After trying to get the issue fixed for almost half a year I returned
it and replaced it by a Seagate, which has been working flawlessly
ever since.

I'm just saying, perhaps the problem isn't with FreeBSD but with the drive.

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

Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2

2015-08-03 Thread Paul Mather 
On Aug 2, 2015, at 9:34 PM, Adam McDougall  wrote:

> On 08/02/2015 21:22, Paul Mather wrote:
>> I have a 4TB external USB drive (Western Digital My Book 1230) that I am 
>> trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052: Wed Jul 
>> 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX) motherboard.
>> 
>> The drive probes unreliably when plugged in to a USB 3 port.  It reliably 
>> probes when plugged into a USB 2 port.  However, it works in neither cases.  
>> Attempting to dd from the drive results in a "dd: /dev/da0: Invalid 
>> argument".
>> 
>> When plugged in to a USB 2 port, this is how the drive is probed:
>> 
>> ugen6.2:  at usbus6
>> umass0:  on 
>> usbus6
>> umass0:  SCSI over Bulk-Only; quirks = 0xc001
>> umass0:9:0:-1: Attached to scbus9
>> da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
>> da0:  Fixed Direct Access SPC-4 SCSI device
>> da0: Serial Number 57434334453056594A4C4A4A
>> da0: 40.000MB/s transfers
>> da0: 3815415MB (976746240 4096 byte sectors: 255H 63S/T 60799C)
>> da0: quirks=0x2
>> ses0 at umass-sim0 bus 0 scbus9 target 0 lun 1
>> ses0:  Fixed Enclosure Services SPC-4 SCSI device
>> ses0: Serial Number 57434334453056594A4C4A4A
>> ses0: 40.000MB/s transfers
>> ses0: SCSI-3 ENC Device
>> 
>> When booting with it connected to a USB 3 port, this is what is output:
>> 
>> xhci0:  mem 0xfeafe000-0xfeaf irq 18 
>> at device 0.0 on pci3
>> xhci0: 64 bytes context size, 64-bit DMA
>> usbus0 on xhci0
>> [[...]]
>> ohci0:  mem 0xfe7fe000-0xfe7fefff irq 
>> 16 at device 18.0 on pci0
>> usbus1 on ohci0
>> ohci1:  mem 0xfe7fd000-0xfe7fdfff irq 
>> 16 at device 18.1 on pci0
>> usbus2 on ohci1
>> ehci0:  mem 0xfe7ff800-0xfe7ff8ff 
>> irq 17 at device 18.2 on pci0
>> usbus3: EHCI version 1.0
>> usbus3 on ehci0
>> ohci2:  mem 0xfe7fc000-0xfe7fcfff irq 
>> 18 at device 19.0 on pci0
>> usbus4 on ohci2
>> ohci3:  mem 0xfe7f7000-0xfe7f7fff irq 
>> 18 at device 19.1 on pci0
>> usbus5 on ohci3
>> ehci1:  mem 0xfe7ff400-0xfe7ff4ff 
>> irq 19 at device 19.2 on pci0
>> usbus6: EHCI version 1.0
>> usbus6 on ehci1
>> [[...]]
>> ohci4:  mem 0xfe7f6000-0xfe7f6fff irq 
>> 18 at device 20.5 on pci0
>> usbus7 on ohci4
>> [[...]]
>> usbus0: 5.0Gbps Super Speed USB v3.0
>> usbus1: 12Mbps Full Speed USB v1.0
>> usbus2: 12Mbps Full Speed USB v1.0
>> usbus3: 480Mbps High Speed USB v2.0
>> usbus4: 12Mbps Full Speed USB v1.0
>> usbus5: 12Mbps Full Speed USB v1.0
>> usbus6: 480Mbps High Speed USB v2.0
>> usbus7: 12Mbps Full Speed USB v1.0
>> ugen7.1:  at usbus7
>> uhub0:  on usbus7
>> ugen6.1:  at usbus6
>> uhub1:  on usbus6
>> ugen5.1:  at usbus5
>> uhub2:  on usbus5
>> ugen4.1:  at usbus4
>> uhub3:  on usbus4
>> ugen3.1:  at usbus3
>> uhub4:  on usbus3
>> ugen2.1:  at usbus2
>> uhub5:  on usbus2
>> ugen1.1:  at usbus1
>> uhub6:  on usbus1
>> ugen0.1: <0x1912> at usbus0
>> uhub7: <0x1912 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
>> uhub0: 2 ports with 2 removable, self powered
>> uhub2: 3 ports with 3 removable, self powered
>> uhub3: 3 ports with 3 removable, self powered
>> uhub5: 3 ports with 3 removable, self powered
>> uhub6: 3 ports with 3 removable, self powered
>> uhub7: 8 ports with 8 removable, self powered
>> [[...]]
>> Root mount waiting for: usbus6 usbus3 usbus0
>> Root mount waiting for: usbus6 usbus3 usbus0
>> uhub1: 6 ports with 6 removable, self powered
>> uhub4: 6 ports with 6 removable, self powered
>> ugen0.2:  at usbus0
>> umass0:  on 
>> usbus0
>> umass0:  SCSI over Bulk-Only; quirks = 0x8000
>> Root mount waiting for: usbus0
>> [[...]]
>> Root mount waiting for: usbus0
>> Root mount waiting for: usbus0
>> umass0: Get Max Lun not supported (USB_ERR_TIMEOUT)
>> umass0:9:0:-1: Attached to scbus9
>> [[...]]
>> da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
>> da0: <  > Fixed Direct Access SCSI device
>> da0: Serial Number WCC4E0VYJLJJ
>> da0: 400.000MB/s transfers
>> da0: 3815415MB (976746240 4096 byte sectors: 255H 63S/T 60799C)
>> da0: quirks=0x2
>> 
>> 
>> This external USB drive works fine under OSX Yosemite and also when plugged 
>> in to my Raspberry Pi 2 running OSMC.
>> 
>> Is there anyone using this model of USB drive under FreeBSD/amd64 10.2?  Is 
>> it a matter of finding the correct quirk to get it working?
>> 
>> Cheers,
>> 
>> Paul.
> 
> The trouble detecting is probably related to
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196332
> 
> I have trouble with my 2T WD "My passport" but I did not create a bug
> report because I found the one above which didn't get a reply.

That PR describes a lot of the symptoms occurring with this WD My Book drive 
(although I haven't tried it under FreeBSD 9).  I notice there was a comment 
added to that PR today---maybe in response to your observation above?


> As far as "dd: /dev/da0: Invalid argument", did you supply a bs=
> argument to dd?  I noticed: "da0: 3815415MB (976746240 4096 byte
> sectors" which means it is reporting as a 4k drive and it will reject
> 512 byte IO requests like dd would u

Re: Many core dumps in pthread_getspecific.

2015-08-03 Thread Andre Meiser 
Hi,

On 27 July 2015 at 22:41, Adrian Chadd wrote:
> What was that option actually doing? How'd it break things?

old operating systems like Windows 98 can't handle a CPUID higher than 3.  But 
Pentium 4 with HTT (Hyper-Threading Technologie) has a higher value.  So the 
BIOS can limit it to 3.

The default value from the BIOS is set to limit the CPUID.  And this caused 
troubles with FreeBSD which used for all but the first CPU a far bigger data 
structure (ucontext_t) for threads.  So sometimes the stack didn't had enough 
space for this big structure and made a segmentation fault (see subject -> many 
core dumps).

This become fixed by Konstantin Belousov today.  So the next FreeBSD release 
won't be affected by this BIOS setting on P4 with HTT.

Sincerely yours Andre.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

/usr/bin/unzip regression?

2015-08-03 Thread Daniel Braniss 
hi,
the file in question is rather big, 5.3G,
older 9.3-stable works ok, while 10.x complains with
unzip: Invalid central directory signature

so is this a regression?

thanks,
danny

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

Re: KSTACK_PAGES stuck at 2 despite options KSTACK_PAGES=4

2015-08-03 Thread Steven Hartland 

This should be fixed by r286223 in HEAD.

I'll MFC to stable/10 after the relevant time-out.

Thanks again for the report :)

Regards
Steve

On 31/07/2015 22:21, Trond Endrestøl wrote:

stable/10, i386, r286139, 4 GiB RAM, custom kernel loudly claims:

ZFS NOTICE: KSTACK_PAGES is 2 which could result in stack overflow panic!
Please consider adding 'options KSTACK_PAGES=4' to your kernel config

Well, my custom kernel config does contain:

options KSTACK_PAGES=4

and

options ZFS

sysctl kern.conftxt backs up my story:

kern.conftxt: options  CONFIG_AUTOGENERATED
ident   VBOX
machine i386
cpu I686_CPU
cpu I586_CPU
cpu I486_CPU
makeoptions WITH_CTF=1
makeoptions DEBUG=-g
options ZFS
options KSTACK_PAGES=4 < !!
options FDESCFS
...

What more does it want?



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

Re: KSTACK_PAGES stuck at 2 despite options KSTACK_PAGES=4

2015-08-03 Thread Steven Hartland 

Thanks for the report Trond, I've reproduced this and am investigating.

On 31/07/2015 22:21, Trond Endrestøl wrote:

stable/10, i386, r286139, 4 GiB RAM, custom kernel loudly claims:

ZFS NOTICE: KSTACK_PAGES is 2 which could result in stack overflow panic!
Please consider adding 'options KSTACK_PAGES=4' to your kernel config

Well, my custom kernel config does contain:

options KSTACK_PAGES=4

and

options ZFS

sysctl kern.conftxt backs up my story:

kern.conftxt: options  CONFIG_AUTOGENERATED
ident   VBOX
machine i386
cpu I686_CPU
cpu I586_CPU
cpu I486_CPU
makeoptions WITH_CTF=1
makeoptions DEBUG=-g
options ZFS
options KSTACK_PAGES=4 < !!
options FDESCFS
...

What more does it want?



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