Re: [request for testing] isl, cyapa on chromebooks

2016-10-04 Thread Andriy Gapon 
On 05/10/2016 01:48, Michael Gmelin wrote:
> Double-checked the hints, it's all ok.
> 
> Please find a more verbose log file of loading the kernel modules here:
> 
> https://people.freebsd.org/~grembo/c720-20161105.log

Unfortunately this doesn't provide any new insights.

Could you please add some printf-s to iicbus_hinted_child() in
sys/dev/iicbus/iicbus.c to see whether the isl devices are really added via the
hints and what their properties are?
Also, some printf-s to isl_probe() to see if it gets called and where it fails.
And, just in case, to ig4iic_start() to see if gets called.

Thank you!

-- 
Andriy Gapon
___
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"

Final call for 2016Q3 quarterly status reports

2016-10-04 Thread Benjamin Kaduk 
Dear FreeBSD Community,

The deadline for the submissions to the next FreeBSD Quarterly Status is
October 9, 2016, for work done in July through September.  This is the
final call for submissions; please let us know if you are considering
making a submission but are not sure that your submission will be ready by
the deadline.

Status report submissions do not have to be very long.  They may be about
anything happening in the FreeBSD project and community, and provide a
great way to inform FreeBSD users and developers about what you're working
on.  Submission of reports is not restricted to committers.  Anyone doing
anything interesting and FreeBSD-related can -- and should -- write one!

The preferred and easiest submission method is to use the XML generator
[1] with the results emailed to the status report team at monthly at
FreeBSD.org .  There is also an XML template [2] which can be filled out
manually and attached if preferred.  For the expected content and style,
please study our guidelines on how to write a good status report [3].
You can also review previous issues [4][5] for ideas on the style and
format.

We are looking forward to all of your 2016Q3 reports!

Thanks,

Ben (on behalf of monthly@)

[1] https://www.FreeBSD.org/cgi/monthly.cgi
[2] https://www.FreeBSD.org/news/status/report-sample.xml
[3] https://www.FreeBSD.org/news/status/howto.html
[4] https://www.FreeBSD.org/news/status/report-2016-01-2016-03.html
[4] https://www.FreeBSD.org/news/status/report-2016-04-2016-06.html
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-04 Thread Michael Gmelin 
On Tue, 4 Oct 2016 13:07:28 +0300
Andriy Gapon  wrote:

> On 04/10/2016 12:46, Michael Gmelin wrote:
> > iicbus(0|1) actually show up in devinfo -v, but nothing else works.
> > 
> > You can find a log file and various outputs (dmesg, devinfo etc)
> > here:
> > 
> > https://people.freebsd.org/~grembo/c720-20161104.log  
> 
> Thank you.
> Could you please double-check that device.hints contains the
> necessary hints? Could you also set debug.bootverbose=1 before
> kldload ig4 and kldload isl and show me any new log messages that
> appear after doing kldload?
> 

Double-checked the hints, it's all ok.

Please find a more verbose log file of loading the kernel modules here:

https://people.freebsd.org/~grembo/c720-20161105.log

-m

-- 
Michael Gmelin
___
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: Destroy GPT partition scheme absolutely, how?

2016-10-04 Thread Steven Hartland 
CAM already does this, doesn't really help with speed as much as you 
might think though.


On 04/10/2016 19:53, Maxim Sobolev wrote:

For the whole disk destruction, hopefully one day we'd have BIO_DELETE
coalesce code, so that you can batch of lot of operations into handful SATA
commands. I've heard rumours imp@ was doing something along those lines. As
well as SSD disks smart enough to process those requests in the background.
Anyway, just saying. )



___
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: Destroy GPT partition scheme absolutely, how?

2016-10-04 Thread Maxim Sobolev 
For the whole disk destruction, hopefully one day we'd have BIO_DELETE
coalesce code, so that you can batch of lot of operations into handful SATA
commands. I've heard rumours imp@ was doing something along those lines. As
well as SSD disks smart enough to process those requests in the background.
Anyway, just saying. )

-Max

On Tue, Oct 4, 2016 at 10:24 AM, John Baldwin  wrote:

> On Tuesday, October 04, 2016 06:23:26 AM Warren Block wrote:
> > On Mon, 26 Sep 2016, John Baldwin wrote:
> >
> > > On Tuesday, September 27, 2016 12:36:22 AM Ngie Cooper wrote:
> > >>
> > >>> On Sep 26, 2016, at 22:48, Ernie Luzar  wrote:
> > >>
> > >> ...
> > >>
> > >>> This little script has been posted before. Maybe it will be what
> your looking for. Called gpart.nuke
> > >>>
> > >>> #! /bin/sh
> > >>> echo "What disk do you want"
> > >>> echo "to wipe? For example - da1 :"
> > >>> read disk
> > >>> echo "OK, in 10 seconds I will destroy all data on $disk!"
> > >>> echo "Press CTRL+C to abort!"
> > >>> sleep 10
> > >>> diskinfo ${disk} | while read disk sectorsize size sectors other
> > >>> do
> > >>> # Delete MBR and partition table.
> > >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} count=1
> > >>> # Delete GEOM metadata.
> > >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} oseek=`expr
> $sectors - 2` count=2
> > >>> done
> > >>
> > >> Why not just use "gpart destroy -F provider"?
> > >
> > > That doesn't always work.  In particular, if a disk was partitioned
> with GPT
> > > and then you use normal MBR on it afterwards, the 'gpart destroy -F'
> of the
> > > MBR will leave most of the GPT intact and the disk will come up with
> the old
> > > GPT partitions, not as a raw disk.
> >
> > Right.  So do a gpart destroy -F of whatever is on there, ignoring
> > errors, then a gpart create -s gpt.  Now there is definitely a secondary
> > GPT, and a final gpart destroy -F removes it cleanly.
>
> It is usually simpler to just dd zeroes over the first N and last N
> sectors.
> The only fool-proof way to ensure you don't have dangling tables in the
> middle of the disk is to zero the entire disk, but that takes too long.
>
> --
> John Baldwin
> ___
> 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-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: Destroy GPT partition scheme absolutely, how?

2016-10-04 Thread John Baldwin 
On Tuesday, October 04, 2016 06:23:26 AM Warren Block wrote:
> On Mon, 26 Sep 2016, John Baldwin wrote:
> 
> > On Tuesday, September 27, 2016 12:36:22 AM Ngie Cooper wrote:
> >>
> >>> On Sep 26, 2016, at 22:48, Ernie Luzar  wrote:
> >>
> >> ...
> >>
> >>> This little script has been posted before. Maybe it will be what your 
> >>> looking for. Called gpart.nuke
> >>>
> >>> #! /bin/sh
> >>> echo "What disk do you want"
> >>> echo "to wipe? For example - da1 :"
> >>> read disk
> >>> echo "OK, in 10 seconds I will destroy all data on $disk!"
> >>> echo "Press CTRL+C to abort!"
> >>> sleep 10
> >>> diskinfo ${disk} | while read disk sectorsize size sectors other
> >>> do
> >>> # Delete MBR and partition table.
> >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} count=1
> >>> # Delete GEOM metadata.
> >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} oseek=`expr $sectors - 
> >>> 2` count=2
> >>> done
> >>
> >> Why not just use "gpart destroy -F provider"?
> >
> > That doesn't always work.  In particular, if a disk was partitioned with GPT
> > and then you use normal MBR on it afterwards, the 'gpart destroy -F' of the
> > MBR will leave most of the GPT intact and the disk will come up with the old
> > GPT partitions, not as a raw disk.
> 
> Right.  So do a gpart destroy -F of whatever is on there, ignoring 
> errors, then a gpart create -s gpt.  Now there is definitely a secondary 
> GPT, and a final gpart destroy -F removes it cleanly.

It is usually simpler to just dd zeroes over the first N and last N sectors.
The only fool-proof way to ensure you don't have dangling tables in the
middle of the disk is to zero the entire disk, but that takes too long.

-- 
John Baldwin
___
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 11.0 i386 buildworld failure

2016-10-04 Thread John Baldwin 
On Monday, October 03, 2016 10:47:26 PM Robert_Burmeister wrote:
> Robert_Burmeister wrote
> > FreeBSD 11.0 i386 Stable
> > 
> > I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September
> > 2016.
> > Upon refreshing and rebuilding world to catch the 28 September 2016
> > Release update,
> > buildworld failed using the same build options that had worked for the 22
> > Sept code.
> 
> Refreshed source to FreeBSD 11 Stable revision 306664 as of Oct 3rd
> and tried buildworld with a FreeBSD 10.3 backup kernel
> with the same result.
> 
> Has anyone been able to bootstrap FreeBSD 11.0 i386?

It seems like your build is using the host headers during the build instead
of the staged headers (both errors were indicative of that).  I would check
your clock via ntpdate or the like in case that is confusing make into
not installing the headers.  Also, a build with an empty /usr/obj would be
the next thing to try.

-- 
John Baldwin
___
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: Destroy GPT partition scheme absolutely, how?

2016-10-04 Thread Warren Block 

On Mon, 26 Sep 2016, John Baldwin wrote:


On Tuesday, September 27, 2016 12:36:22 AM Ngie Cooper wrote:



On Sep 26, 2016, at 22:48, Ernie Luzar  wrote:


...


This little script has been posted before. Maybe it will be what your looking 
for. Called gpart.nuke

#! /bin/sh
echo "What disk do you want"
echo "to wipe? For example - da1 :"
read disk
echo "OK, in 10 seconds I will destroy all data on $disk!"
echo "Press CTRL+C to abort!"
sleep 10
diskinfo ${disk} | while read disk sectorsize size sectors other
do
# Delete MBR and partition table.
dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} count=1
# Delete GEOM metadata.
dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} oseek=`expr $sectors - 2` 
count=2
done


Why not just use "gpart destroy -F provider"?


That doesn't always work.  In particular, if a disk was partitioned with GPT
and then you use normal MBR on it afterwards, the 'gpart destroy -F' of the
MBR will leave most of the GPT intact and the disk will come up with the old
GPT partitions, not as a raw disk.


Right.  So do a gpart destroy -F of whatever is on there, ignoring 
errors, then a gpart create -s gpt.  Now there is definitely a secondary 
GPT, and a final gpart destroy -F removes it cleanly.

___
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 11.0 i386 buildworld failure

2016-10-04 Thread Robert_Burmeister 
Robert_Burmeister wrote
> FreeBSD 11.0 i386 Stable
> 
> I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September
> 2016.
> Upon refreshing and rebuilding world to catch the 28 September 2016
> Release update,
> buildworld failed using the same build options that had worked for the 22
> Sept code.

Refreshed source to FreeBSD 11 Stable revision 306664 as of Oct 3rd
and tried buildworld with a FreeBSD 10.3 backup kernel
with the same result.

Has anyone been able to bootstrap FreeBSD 11.0 i386?




--
View this message in context: 
http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-i386-buildworld-failure-tp6133823p6134583.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
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: ZFS - Abyssal slow on copying

2016-10-04 Thread Fabian Keil 
"O. Hartmann"  wrote:

> Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct  2 09:34:50 
> CEST 2016 ), I
> have a NanoBSD setup which creates an image for a router device.
> 
> The problem I face is related to ZFS. The system has a system's SSD (Samsung 
> 850 Pro,
> 256GB) which has an UFS filesystem. Aditionally, I have also a backup and a 
> data HDD,
> both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both the 
> sources for
> the NanoBSD and the object tree as well as the NANO_WORLDDIR are residing on 
> the 3 TB
> data drive. 
> 
> The box itself has 8 GB RAM. When it comes to create the memory disk, which 
> is ~ 1,3 GB
> in size, the NanoBSD script starts creating the memory disk and then 
> installing world
> into this memory disk. And this part is a kind of abyssal in terms of the 
> speed.

Can you reproduce the issue if you replace the memory disk with
a zvol or tmpfs?

While I agree that depulication could be the cause of the problem,
it probably wouldn't hurt to rule out a memory-disk related issue
before recreating the pool.

Fabian


pgph6o96DoQK7.pgp
Description: OpenPGP digital signature

Re: [request for testing] isl, cyapa on chromebooks

2016-10-04 Thread Andriy Gapon 
On 04/10/2016 12:46, Michael Gmelin wrote:
> iicbus(0|1) actually show up in devinfo -v, but nothing else works.
> 
> You can find a log file and various outputs (dmesg, devinfo etc) here:
> 
> https://people.freebsd.org/~grembo/c720-20161104.log

Thank you.
Could you please double-check that device.hints contains the necessary hints?
Could you also set debug.bootverbose=1 before kldload ig4 and kldload isl and
show me any new log messages that appear after doing kldload?

-- 
Andriy Gapon
___
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: [request for testing] isl, cyapa on chromebooks

2016-10-04 Thread Michael Gmelin 
On Tue, 4 Oct 2016 01:04:10 +0300
Andriy Gapon  wrote:

> On 03/10/2016 23:25, Michael Gmelin wrote:
> > On Mon, 3 Oct 2016 19:41:17 +0300
> > Andriy Gapon  wrote:
> >   
> >> On 03/10/2016 19:07, Michael Gmelin wrote:  
> >>> I upgraded the latter the r306641, applied your patches (cleanly)
> >>> and ran "make kernel" (GENERIC kernel), added the entries to
> >>> device.hints and rebooted. Unfortunately ig4 won't load:
> >>>
> >>> # kldload ig4
> >>> link_elf_obj: symbol iicbus_transfer_desc undefined
> >>> linker_load_file: Unsupported file type
> >>
> >> Hmm, seems like forgot to declare the iicbus module dependency.
> >> Could you please kldload iicbus and see if that helps?
> >> Meanwhile I'll add the dependency.  
> > 
> > Unfortunately this doesn't help, you should be able to reproduce it
> > yourself without access to the actual hardware though.
> > 
> > I worked around this by adding the iicbus dependency to ig4_pci.c
> > (and also to "files").  
> 
> Okay, this should be in the latest patch anyway.

Based on what you wrote, I wasn't aware that there was a new patch. I
downloaded the latest version from the same URL as your first one and
built a new kernel.


> 
> > Now loading ig4 works and both lynx point controllers are detected.
> > Loading isl doesn't create any output and doesn't seem to detect any
> > devices. Also, devinfo shows both controllers (ig4iic0, ig4iic1),
> > but no iicbus devices.
> > 
> > # devinfo | grep iic
> > ig4iic0
> > ig4iic1  
> 
> Is there anything interesting from from ig4 in the log / dmesg?
> Could you please check that your copy of the patch contains this
> chunk? @@ -549,7 +780,7 @@ ig4iic_attach(ig4iic_softc_t *sc)
>   IG4_CTL_RESTARTEN |
>   IG4_CTL_SPEED_STD);
> 
> -   sc->smb = device_add_child(sc->dev, "smbus", -1);
> +   sc->smb = device_add_child(sc->dev, "iicbus", -1);
> if (sc->smb == NULL) {
> device_printf(sc->dev, "smbus driver not found\n");
> error = ENXIO;
> 

That code was in there, yes.

iicbus(0|1) actually show up in devinfo -v, but nothing else works.

You can find a log file and various outputs (dmesg, devinfo etc) here:

https://people.freebsd.org/~grembo/c720-20161104.log

-m

-- 
Michael Gmelin
___
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: Regression with revision 303970 (was kern.proc.pathname failure while booting from zfs)

2016-10-04 Thread Andriy Gapon 

I've written a patch that implements zfs_vptocnp() using z_parent property.
The new code should be 100% reliable for directories and "mostly" reliable for
files (that is, when hardlinks across directories are not used).

Could you please review / test it?
https://reviews.freebsd.org/D8146

Thanks!
-- 
Andriy Gapon
___
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"