Re: [zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

[Ranjan1018 .]

2016-01-09 11:18 GMT+01:00 Xin Li :

> Please subscribe:
>
> https://bugs.freebsd.org/205882
>
> You can locally apply -r292066 or modify the code to skip the check when
> pguid is 0 as a stopgap.
>
> Cheers,
>
>
Thank you Xin it works,
I have replace vdev_geom.c r292066 with r274619, rebuild and reinstalled
the kernel and now, the zfs cache, works as before.
I have done this test with:
# uname -a
FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r293438: Fri Jan  8
21:19:19 CET 2016 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

Regards,
--
Maurizio
___
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"

[zfs] Cache on SD stops working after updating to 11-CURRENT r291458 amd64

[Ranjan1018 .]

Hi,

I use a SD card as cache for a laptop pool sys:

# zpool status -v

 pool: sys

state: ONLINE

 scan: scrub repaired 0 in 1h13m with 0 errors on Mon Jan  4 00:02:42 2016

config:

   NAME STATE READ WRITE CKSUM

   sys  ONLINE   0 0 0

 gpt/sys0   ONLINE   0 0 0

   cache

 gpt/cache  ONLINE   0 0 0


After updating 11.0-CURRENT from r291458 to r293055 the cache stops working.

I am running:

# uname -a

FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r293055: Sun Jan  3
00:15:33 CET 2016 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

Fault cache status after the boot:

# zpool status -v


 pool: sys

state: ONLINE

status: One or more devices could not be opened.  Sufficient replicas exist
for

   the pool to continue functioning in a degraded state.

action: Attach the missing device and online it using 'zpool online'.

  see: http://illumos.org/msg/ZFS-8000-2Q

 scan: scrub repaired 0 in 1h13m with 0 errors on Mon Jan  4 00:02:42 2016

config:

   NAME   STATE READ WRITE CKSUM

   sysONLINE   0 0 0

 gpt/sys0 ONLINE   0 0 0

   cache

 1553023247900193278  UNAVAIL  0 0 0  was /dev/gpt/cache

errors: No known data errors


Trying to online the cache I have the error:

# zpool online sys gpt/cache

warning: device 'gpt/cache' onlined, but remains in faulted state

use 'zpool replace' to replace devices that are no longer present


To use the cache I need to remove & add it:

# zpool remove sys gpt/cache

# zpool add sys cache gpt/cache

--
Maurizio
___
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: Panic at shutdown

[Ranjan1018 .]

2015-11-29 0:10 GMT+01:00 Garrett Cooper :

>
> > On Nov 28, 2015, at 12:32, Ranjan1018 . <21474...@gmail.com> wrote:
> >
> > Hi,
> >
> > sometimes I have the panic in the photo at shutdown:
> >
> > http://imgur.com/mXrgFLp
> >
> > Unfortunately this happens randomly.
> >
> > I am running:
> >
> > $ uname -a
> >
> > FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r291160M: Sun Nov 22
> > 17:10:38 CET 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64
>
> The panic is in the ZFS code.
>
> Have you run memtest on the machine recently?
>

Good suggestion I have run memtest successfully for few hours on my laptop.

I have understood the panic cause: is an invalid offset.

The original function in
/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/txg.c is:

boolean_t
txg_list_member(txg_list_t *tl, void *p, uint64_t txg)
{
int t = txg & TXG_MASK;
txg_node_t *tn = (txg_node_t *)((char *)p + tl->tl_offset);

return (tn->tn_member[t] != 0);
}

I have modified the function to print an uncommon or invalid tl->tl_offset :

boolean_t
txg_list_member(txg_list_t *tl, void *p, uint64_t txg)
{
size_t ofs = tl->tl_offset;
{
static int cnt=0;
if ( (cnt++ % 1000) == 0
|| (ofs != 88 && ofs != 984) )
printf(" %d) tl->tl_offset %zu\n", cnt, ofs);
}

txg_node_t *tn = (txg_node_t *)((char *)p + ofs);

return (tn->tn_member[txg & TXG_MASK] != 0);
}

I have received the panic again with an invalid  tl->tl_offset of
16045693110842147038.
In /val/log/messages I have:

Dec  8 10:32:42 ativ kernel: Waiting (max 60 seconds) for system process
`vnlru' to stop...done
Dec  8 10:32:42 ativ kernel: Waiting (max 60 seconds) for system process
`bufdaemon' to stop...done
Dec  8 10:32:42 ativ kernel: Waiting (max 60 seconds) for system process
`syncer' to stop...
Dec  8 10:32:42 ativ kernel: Syncing disks, vnodes remaining...0 0 0 done
Dec  8 10:32:42 ativ kernel: All buffers synced.
Dec  8 10:32:42 ativ kernel:  9692) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9693) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9694) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9695) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9708) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9709) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9710) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9711) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9720) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9721) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9722) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel:  9723) tl->tl_offset 384
Dec  8 10:32:42 ativ kernel: Uptime: 1h57m42s
Dec  8 10:32:42 ativ kernel:  9736) tl->tl_offset 16045693110842147038
Dec  8 10:32:42 ativ kernel:
Dec  8 10:32:42 ativ kernel:
Dec  8 10:32:42 ativ kernel: Fatal trap 9: general protection fault while
in kernel mode
Dec  8 10:32:42 ativ kernel: cpuid = 2; apic id = 02
Dec  8 10:32:42 ativ kernel: instruction pointer=
0x20:0x8211b1cb
Dec  8 10:32:42 ativ kernel: stack pointer=
0x28:0xfe0119525990
Dec  8 10:32:42 ativ kernel: frame pointer=
0x28:0xfe01195259c0
Dec  8 10:32:42 ativ kernel: code segment= base 0x0, limit 0xf,
type 0x1b
Dec  8 10:32:42 ativ kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
Dec  8 10:32:42 ativ kernel: processor eflags= interrupt enabled,
resume, IOPL = 0
Dec  8 10:32:42 ativ kernel: current process= 0 (dbu_evict)

Probably the panic is caused by some memory already freed, the hex  value
of 16045693110842147038 is 0xdeadc0dedeadc0de.
To solve the panic I need some tips form someone more expert than me in ZFS
code.

Thanks.

-- Maurizio
___
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: [PATCH] XOR uses

[Ranjan1018 .]

2015-12-08 5:40 GMT+01:00 Marcelo Araujo :

> Hi Michael,
>
> What would be the advantage of it?
> I still prefer explicit than implicit. The current code is much more
> readable.
>
> Best,
>
> 2015-12-08 11:13 GMT+08:00 Michael McConville :
>
> > A minor simplification patch:
> >
> >
> > Index: sys/arm/allwinner/a10_gpio.c
> > ===
> > --- sys/arm/allwinner/a10_gpio.c(revision 291978)
> > +++ sys/arm/allwinner/a10_gpio.c(working copy)
> > @@ -356,10 +356,7 @@
> > sc = device_get_softc(dev);
> > A10_GPIO_LOCK(sc);
> > data = A10_GPIO_READ(sc, A10_GPIO_GP_DAT(bank));
> > -   if (data & (1 << pin))
> > -   data &= ~(1 << pin);
> > -   else
> > -   data |= (1 << pin);
> > +   data ^= (1 << pin);
> > A10_GPIO_WRITE(sc, A10_GPIO_GP_DAT(bank), data);
> > A10_GPIO_UNLOCK(sc);
> >
> > Index: sys/arm/altera/socfpga/socfpga_gpio.c
> > ===
> > --- sys/arm/altera/socfpga/socfpga_gpio.c   (revision 291978)
> > +++ sys/arm/altera/socfpga/socfpga_gpio.c   (working copy)
> > @@ -336,10 +336,7 @@
> >
> > GPIO_LOCK(sc);
> > reg = READ4(sc, GPIO_SWPORTA_DR);
> > -   if (reg & (1 << i))
> > -   reg &= ~(1 << i);
> > -   else
> > -   reg |= (1 << i);
> > +   reg ^= (1 << i);
> > WRITE4(sc, GPIO_SWPORTA_DR, reg);
> > GPIO_UNLOCK(sc);
> >
> > Index: sys/arm/rockchip/rk30xx_gpio.c
> > ===
> > --- sys/arm/rockchip/rk30xx_gpio.c  (revision 291978)
> > +++ sys/arm/rockchip/rk30xx_gpio.c  (working copy)
> > @@ -375,10 +375,7 @@
> > return (EINVAL);
> > RK30_GPIO_LOCK(sc);
> > data = RK30_GPIO_READ(sc, RK30_GPIO_SWPORT_DR);
> > -   if (data & (1U << pin))
> > -   data &= ~(1U << pin);
> > -   else
> > -   data |= (1U << pin);
> > +   data ^= (1U << pin);
> > RK30_GPIO_WRITE(sc, RK30_GPIO_SWPORT_DR, data);
> > RK30_GPIO_UNLOCK(sc);
> >
> > Index: sys/arm/samsung/exynos/exynos5_pad.c
> > ===
> > --- sys/arm/samsung/exynos/exynos5_pad.c(revision 291978)
> > +++ sys/arm/samsung/exynos/exynos5_pad.c(working copy)
> > @@ -722,10 +722,7 @@
> >
> > GPIO_LOCK(sc);
> > reg = READ4(sc, bank.port, bank.con + 0x4);
> > -   if (reg & (1 << pin_shift))
> > -   reg &= ~(1 << pin_shift);
> > -   else
> > -   reg |= (1 << pin_shift);
> > +   reg ^= (1 << pin_shift);
> > WRITE4(sc, bank.port, bank.con + 0x4, reg);
> > GPIO_UNLOCK(sc);
> >
> > Index: sys/dev/nand/nandsim_ctrl.c
> > ===
> > --- sys/dev/nand/nandsim_ctrl.c (revision 291978)
> > +++ sys/dev/nand/nandsim_ctrl.c (working copy)
> > @@ -388,9 +388,6 @@
> > rand = random();
> > if ((rand % 100) < chip->error_ratio) {
> > bit = rand % 8;
> > -   if (*byte & (1 << bit))
> > -   *byte &= ~(1 << bit);
> > -   else
> > -   *byte |= (1 << bit);
> > +   *byte ^= (1 << bit);
> > }
> >  }
> >
>

Hi,

I prefer the syntax in the patch:
- the semantic is more clear for me: if you want to flip a bit you should
use xor
- it saves, probably, some bytes of assembly code

Regards
Maurizio
___
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"

Panic at shutdown

[Ranjan1018 .]

Hi,

sometimes I have the panic in the photo at shutdown:

http://imgur.com/mXrgFLp

Unfortunately this happens randomly.

I am running:

$ uname -a

FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r291160M: Sun Nov 22
17:10:38 CET 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

Regards,

Maurizio
___
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"

‘zpool get’ command help output.

[Ranjan1018 .]

Hi,

running the command

$ zpool get

missing property argument

usage:

   get [-Hp] [-o "all" | field[,...]] <"all" | property[,...]> 
...

the following properties are supported:

   PROPERTY EDIT   VALUES

   allocated  NO   

   capacity   NO   

   dedupratio NO   <1.00x or higher if deduped>

   expandsize NO   

   fragmentation  NO   

   free   NO   

   freeingNO   

   guid   NO   

   health NO   

   leaked NO   

   size   NO   

   altroot   YES   

   autoexpandYES   on | off

   autoreplace   YES   on | off

   bootfsYES   

   cachefile YES| none

   comment   YES   

   dedupdittoYES   

   delegationYES   on | off

   failmode  YES   wait | continue | panic

   listsnapshots YES   on | off

   readonly  YES   on | off

   version   YES   

   feature@...   YES   disabled | enabled | active

The feature@ properties must be appended with a feature name.

See zpool-features(7).

I notice that:

   -

   the property “capacity” is a  and not a 
   -

   the property “name” is missing.


Regards
Maurizio
___
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: CFT: wpa_supplicant/hostapd 2.5

[Ranjan1018 .]

2015-10-14 7:00 GMT+02:00 Rui Paulo :

> Hi,
>
> Please download and test the wpa_supplicant/hostapd import patch:
>
> http://people.freebsd.org/~rpaulo/patches/wpa-2.5.diff
>
>
> Changelog:
>
> http://w1.fi/cgit/hostap/plain/hostapd/ChangeLog
> http://w1.fi/cgit/hostap/plain/wpa_supplicant/ChangeLog
>
>
> Please report success/failures.
>
> Thanks,
> --
> Rui Paulo
> Wishlist: http://amzn.com/w/ZU4EQTF9M613
>
> ___
> 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"
>

Hi,
I am using this patch on my home laptop for three days and all things work
well.
# pciconf -l -v | grep -A 3 ath
ath0@pci0:1:0:0:class=0x028000 card=0x4105144d chip=0x0032168c rev=0x01
hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'AR9485 Wireless Network Adapter'
class  = network
# uname -a
FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #10 r289378M: Thu Oct 15
21:57:57 CEST 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

Before the patch I have some trouble connecting to the office Netgear
DGND4000, but now is ok.
Thanks.
- Maurizio
___
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: Panic running "/etc/rc.d/netif restart" with LAGG(4) on 11.0-CURRENT

[Ranjan1018 .]

2015-10-15 15:33 GMT+02:00 Hans Petter Selasky :

> On 10/15/15 15:23, Ranjan1018 . wrote:
>
>> My laptop is running:
>> # uname -a
>> FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #8 r289136M: Sun Oct 11
>> 14:08:51 CEST 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64
>>
>> In /etc/rc.conf I have:
>> # LAGG
>> ifconfig_re0="ether 18:67:b0:7d:c1:3b up"
>> wlans_ath0="wlan0"
>> ifconfig_wlan0="WPA"
>> cloned_interfaces="lagg0"
>> ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP"
>>
>> Running the command:
>> # /etc/rc.d/netif restart
>> a kernel panic will happen.
>>
>>
> Seems like a known issue. Does this patch help:
>
> https://reviews.freebsd.org/D3883
>
> --HPS
>
> Thank you Hans, it works!

Maurizio
___
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"

Panic running "/etc/rc.d/netif restart" with LAGG(4) on 11.0-CURRENT

[Ranjan1018 .]

My laptop is running:
# uname -a
FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #8 r289136M: Sun Oct 11
14:08:51 CEST 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

In /etc/rc.conf I have:
# LAGG
ifconfig_re0="ether 18:67:b0:7d:c1:3b up"
wlans_ath0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP"

Running the command:
# /etc/rc.d/netif restart
a kernel panic will happen.

# cat /var/run/panicmail.0
Dump header from device: /dev/gpt/swap
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 402313216
  Blocksize: 512
  Dumptime: Wed Oct 14 23:39:24 2015
  Hostname: ativ
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 11.0-CURRENT #8 r289136M: Sun Oct 11 14:08:51
CEST 2015
root@ativ:/usr/obj/usr/src/sys/GENERIC
  Panic String: page fault
  Dump Parity: 2234708060
  Bounds: 0
  Dump Status: good

Backtrace:
Reading symbols from /boot/kernel/zfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/zfs.ko.debug...done.
done.
Loaded symbols for /boot/kernel/zfs.ko
Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from
/usr/lib/debug//boot/kernel/opensolaris.ko.debug...done.
done.
Loaded symbols for /boot/kernel/opensolaris.ko
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/fdescfs.ko.debug...done.
done.
Loaded symbols for /boot/kernel/fdescfs.ko
Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/tmpfs.ko.debug...done.
done.
Loaded symbols for /boot/kernel/tmpfs.ko
Reading symbols from /boot/kernel/i915kms.ko...Reading symbols from
/usr/lib/debug//boot/kernel/i915kms.ko.debug...done.
done.
Loaded symbols for /boot/kernel/i915kms.ko
Reading symbols from /boot/kernel/drm2.ko...Reading symbols from
/usr/lib/debug//boot/kernel/drm2.ko.debug...done.
done.
Loaded symbols for /boot/kernel/drm2.ko
Reading symbols from /boot/kernel/iicbus.ko...Reading symbols from
/usr/lib/debug//boot/kernel/iicbus.ko.debug...done.
done.
Loaded symbols for /boot/kernel/iicbus.ko
Reading symbols from /boot/kernel/iic.ko...Reading symbols from
/usr/lib/debug//boot/kernel/iic.ko.debug...done.
done.
Loaded symbols for /boot/kernel/iic.ko
Reading symbols from /boot/kernel/iicbb.ko...Reading symbols from
/usr/lib/debug//boot/kernel/iicbb.ko.debug...done.
done.
Loaded symbols for /boot/kernel/iicbb.ko
Reading symbols from /boot/kernel/coretemp.ko...Reading symbols from
/usr/lib/debug//boot/kernel/coretemp.ko.debug...done.
done.
Loaded symbols for /boot/kernel/coretemp.ko
Reading symbols from /boot/modules/acpi_call.ko...done.
Loaded symbols for /boot/modules/acpi_call.ko
Reading symbols from /boot/kernel/if_lagg.ko...Reading symbols from
/usr/lib/debug//boot/kernel/if_lagg.ko.debug...done.
done.
Loaded symbols for /boot/kernel/if_lagg.ko
Reading symbols from /boot/modules/cuse4bsd.ko...done.
Loaded symbols for /boot/modules/cuse4bsd.ko
Reading symbols from /boot/kernel/ng_ubt.ko...Reading symbols from
/usr/lib/debug//boot/kernel/ng_ubt.ko.debug...done.
done.
Loaded symbols for /boot/kernel/ng_ubt.ko
Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from
/usr/lib/debug//boot/kernel/netgraph.ko.debug...done.
done.
Loaded symbols for /boot/kernel/netgraph.ko
Reading symbols from /boot/kernel/ng_hci.ko...Reading symbols from
/usr/lib/debug//boot/kernel/ng_hci.ko.debug...done.
done.
Loaded symbols for /boot/kernel/ng_hci.ko
Reading symbols from /boot/kernel/ng_bluetooth.ko...Reading symbols from
/usr/lib/debug//boot/kernel/ng_bluetooth.ko.debug...done.
done.
Loaded symbols for /boot/kernel/ng_bluetooth.ko
Reading symbols from /boot/modules/vboxnetflt.ko...done.
Loaded symbols for /boot/modules/vboxnetflt.ko
Reading symbols from /boot/modules/vboxdrv.ko...done.
Loaded symbols for /boot/modules/vboxdrv.ko
Reading symbols from /boot/kernel/ng_ether.ko...Reading symbols from
/usr/lib/debug//boot/kernel/ng_ether.ko.debug...done.
done.
Loaded symbols for /boot/kernel/ng_ether.ko
Reading symbols from /boot/modules/vboxnetadp.ko...done.
Loaded symbols for /boot/modules/vboxnetadp.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux.ko.debug...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/linux_common.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linux_common.ko.debug...done.
done.
Loaded symbols for /boot/kernel/linux_common.ko
Reading symbols from /boot/kernel/fuse.ko...Reading symbols from
/usr/lib/debug//boot/kernel/fuse.ko.debug...done.
done.
Loaded symbols for /boot/kernel/fuse.ko
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from
/usr/lib/debug//boot/kernel/linprocfs.ko.debug...done.
done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/if_tap.ko...Reading symbols from
/usr/lib/debug//boot/kernel/if_tap.ko.debug...done.
done.
Loaded symbols for /boot/kernel/if_tap.ko
Reading symbols 

Re: [CTF] pkg 1.6.0

[Ranjan1018 .]

2015-09-21 23:27 GMT+02:00 Baptiste Daroussin :

> Hi all,
>
> We are about to release pkg 1.6.0. pkg-devel has been updated to 1.5.99.13
> aka
> 1.6.0 rc3 that we hope will become the new pkg 1.6.0 btw the end of the
> Week
> (release planned for Saturday 26th of September or no important issues are
> raised)
>
> On the list of changes:
> - Lots of improvements in the solver (in particular fixes the case like the
>   recent jpeg upgrade)
> - Lots of fixes in the 3 way merge code
> - pkg add can now work without a version specified in the dependency line
> - pkg check -d now also check the required libraries
> - Improved support for partial upgrades
> - Improved zsh completion support
> - Improved linux support (now all regression tests passes on linux)
> - Messages can now be context aware: (only print a given message during
>   installation, upgrade - version aware -, removal, or always)
> - @keywords now accepts new entries to add context aware messages
> - Add the ability to generate graphiz's dot format representation of the
>   solver's problem
> - pkg search now default on showing the comments of of the matched packages
> - Lots of bug fixes and code cleanup
> - Plenty of new bugs
>
> Please test heavily, I would like to make a release quite soon to limit the
> number of users suffering from the jpeg->jpeg-turbo update.
>
> Best regards,
> Bapt
>

Thank you Batp,

running version 1.5.3 I have this error message:
# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (40 candidates): 100%
Processing candidates (40 candidates): 100%
Checking integrity... done (1 conflicting)
pkg: Cannot solve problem using SAT solver:
dependency rule: package Thunar(l) depends on:
xfce4-tumbler(r)xfce4-tumbler(l)
upgrade rule: upgrade local xfce4-tumbler-0.1.31_1 to remote
xfce4-tumbler-0.1.31_1
cannot install package xfce4-tumbler, remove it from request? [Y/n]:
pkg: cannot find xfce4-tumbler in the request
pkg: cannot solve job using SAT solver
Checking integrity... done (0 conflicting)
Your packages are up to date.

With this version I have been able to update the packages.

I am running:
$ uname -a
FreeBSD microserver 10.2-STABLE FreeBSD 10.2-STABLE #1 r287746: Sun Sep 13
14:06:46 CEST 2015 root@microserver:/usr/obj/usr/src/sys/GENERIC  amd64

With the latest repository:
$ cat /etc/pkg/FreeBSD.conf
# $FreeBSD: stable/10/etc/pkg/FreeBSD.conf 263938 2014-03-30 15:29:54Z
bdrewery $
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
#   mkdir -p /usr/local/etc/pkg/repos
#   echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
#

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

Regards,
Maurizio
___
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: Upgrading to r297291 LAGG(4) stops working.

[Ranjan1018 .]

2015-08-30 17:12 GMT+02:00 Adrian Chadd :

> hi,
>
> don'tr set ath0 to the MAC of your ethernet device, set your ethernet
> MAC to the MAC of your atheros device.
>
> (But I keep telling people, failover between ethernet/wifi isn't
> supported by the wifi code...)
>
>
> -a
>
> @David
Ehm... sorry it’s r287291 not r297291.
@Adrian
Thank you, it works as before. Now in /etc/rc.conf I have:
# LAGG
ifconfig_re0="ether 18:67:b0:7d:c1:3b up"
wlans_ath0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP"

Maurizio
___
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"

Upgrading to r297291 LAGG(4) stops working.

[Ranjan1018 .]

On my laptop I am using LAGG(4) as explained in
"Example 30.3. Failover Mode Between Ethernet and Wireless Interfaces" in
the Handbook.
In rc.conf i have:
# LAGG
ifconfig_re0="up"
ifconfig_ath0="ether 18:67:b0:39:bd:23"
wlans_ath0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP"

What's wrong ?
Thanks,
Maurizio
___
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: Slow shutdown

[Ranjan1018 .]

2015-06-12 1:13 GMT+02:00 Henry Hu :

> On Thu, Jun 11, 2015 at 1:55 PM Kevin Oberman  wrote:
>
>> The same issue exists in fusefs, but has an uglier result. The fuse daemon
>> shuts down before any fusefs based file systems are unmounted, but, for
>> several R/W file systems including NTFS and exFAT, the result is a corrupt
>> file system. I did the same thing to work around this problem... an init
>> script, but I wonder if this should not be handled in some cleaner and
>> more
>> global manner. (No, I have no idea right now of how to implement this.)
>>
>
> I think that I've hit this problem several times, because I've lost files
> on my NTFS portable harddisk several times. Now I force an unmount in the
> shutdown script.
> I remember that when fuse module was still in fusefs-kmod, the rc script
> unmounts the file systems, and there's even a _safe flag to ensure safety.
>
>
Hi,
I have the same issue in my laptop a dual boot FreeBSD/Windows 8. In
FreeBSD, the Win8 partition, is mounted via fusefs and is unmounted in a
shutdown script.
But if I do not unmount this partition in a script, it is not unmounted by
the OS or fusefs at shutdown. Probably this is a different or new bug.

For the original bug I have opened a PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200784
Please comment here if you like.

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

Re: Slow shutdown

[Ranjan1018 .]

2015-05-24 22:33 GMT+02:00 Garrett Cooper :

> On May 24, 2015, at 6:33, Ranjan1018 . <21474...@gmail.com> wrote:
>
> > On my laptop running r283297, after the message “All buffers synced.” and
> > before “Uptime: …..” it takes more than 55 seconds.
>
> Not a lot of info here to diagnose your issue...
> - What happens if you hit control-t, i.e. what wait channel does it print
> out?
> - What filesystems do you have mounted (fuse, NFS, UFS, ZFS)?
> - What’s your root media (SSDs, SATA/PATA hard drives, etc)?
>
> Thanks..
>

Solved !

The slow shutdown is caused by some remote smbfs shares mounted via
openvpn: the remote drives are unmounted after the openvpn daemon
termination, this induces some long timeout. The solution is to unmount the
smbfs shares in a shutdown script before the openvpn daemon termination. I
have discovered this issue with this ‘dirty’ patch that displays  the
unmounted fs at shutdown:

http://pastebin.com/Xfiz9nsv

With this patch shutting down my laptop appear as:

https://drive.google.com/file/d/0BzoWQoMqq1sfcHZyRnlEeTRobFU/view?usp=sharing
.

For testing the the patch apply it in /sys/kern, rebuild and install the
kernel.

Set the new OID:

# sysctl kern.shutdown.show_umountfs=1

Halt the system:

# shutdown -h now

Regards,

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

Re: how do I downgrade from 11-current to 10-stable

[Ranjan1018 .]

2015-05-30 11:52 GMT+02:00 Aryeh Friedman :

> My desktop machine is 11-current and I want to down grade it to 10-stable
> how do I do this without needing a reinstall?
>
> I have done the downgrade of my home server few weeks ago.
I have done this rebuilding the whole OS from source:
1 - Upgrade the 11-CURRENT if old.
2 - Make a backup or make a new environment if you use beadm
3 - Download the 10-STABLE source
4 - Build and install the new 10-STABLE
5 - Upgrade the packages.

If you need further details let me know.

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

Re: Slow shutdown

[Ranjan1018 .]

2015-05-24 22:33 GMT+02:00 Garrett Cooper :

> On May 24, 2015, at 6:33, Ranjan1018 . <21474...@gmail.com> wrote:
>
> > On my laptop running r283297, after the message “All buffers synced.” and
> > before “Uptime: …..” it takes more than 55 seconds.
>
> Not a lot of info here to diagnose your issue...
> - What happens if you hit control-t, i.e. what wait channel does it print
> out?
>
control-t doesn't works.

> - What filesystems do you have mounted (fuse, NFS, UFS, ZFS)?
>
ZFS and NTFS via fuse, removing NTFS mount doesn't reduce the shutdown time.

> - What’s your root media (SSDs, SATA/PATA hard drives, etc)?
>
 SATA.

>
> Thanks..
>
Thanks to you.

I noticed that with  the command ‘shutdown -h now’ the phrase “The
operating system has halted. Please press any key to reboot.” is missing,
pressing a key the laptop reboots.

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

Slow shutdown

[Ranjan1018 .]

On my laptop running r283297, after the message “All buffers synced.” and
before “Uptime: …..” it takes more than 55 seconds.

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

Re: CM6206 USB Audio is mute.

[Ranjan1018 .]

2015-04-22 9:40 GMT+02:00 Hans Petter Selasky :

> On 04/21/15 21:30, Ranjan1018 . wrote:
>
>> Connecting the USB cable the item is recognized:
>> ugen0.5:  at usbus0
>> uaudio0: > 5>
>> on usbus0
>> uaudio0: Play: 48000 Hz, 4 ch, 16-bit S-LE PCM format, 2x8ms buffer.
>> uaudio0: Play: 44100 Hz, 4 ch, 16-bit S-LE PCM format, 2x8ms buffer.
>> uaudio0: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer.
>> uaudio0: Record: 44100 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer.
>> uaudio0: No MIDI sequencer.
>> pcm1:  on uaudio0
>> uaudio0: HID volume keys found.
>>
>>
> Hi,
>
> Did you check:
>
> mixer -f /dev/mixerX
>
> that sound volume is OK?
>
>  Setting it as default unit
>> # sysctl  hw.snd.default_unit=1
>> and playing a song the interrupts count increase:
>>
>
> Some volume knobs might be hidden. Try to get all:
>
> sysctl -a | grep pcm
>
>
>  But the output is mute.
>>
>> In Debian Linux it works:
>> # lsusb
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 002 Device 014: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
>> Sound
>> Device
>> # aplay -l
>>  List of PLAYBACK Hardware Devices 
>> card 1: Device [USB Sound Device], device 0: USB Audio [USB Audio]
>>   Subdevices: 0/1
>>   Subdevice #0: subdevice #0
>>
>> Looking at http://lxr.free-electrons.com/source/sound/usb/quirks.c I have
>> found this code:
>> /*
>> 632 * C-Media CM106/CM106+ have four 16-bit internal registers that are
>> nicely
>> 633 * documented in the device's data sheet.
>> 634 */
>> 635 static int snd_usb_cm106_write_int_reg(struct usb_device *dev, int
>> reg,
>> u16 value)
>> 636 {
>> 637 u8 buf[4];
>> 638 buf[0] = 0x20;
>> 639 buf[1] = value & 0xff;
>> 640 buf[2] = (value >> 8) & 0xff;
>> 641 buf[3] = reg;
>> 642 return snd_usb_ctl_msg(dev, usb_sndctrlpipe(dev, 0),
>> USB_REQ_SET_CONFIGURATION,
>> 643USB_DIR_OUT | USB_TYPE_CLASS |
>> USB_RECIP_ENDPOINT,
>> 6440, 0, &buf, 4);
>> 645 }
>>
>
> This USB control request can be issued from userspace like this (you need
> to convert all variables below into constants):
>
> usbconfig -d X.Y do_request "USB_DIR_OUT | USB_TYPE_CLASS |
> > USB_RECIP_ENDPOINT" "USB_REQ_SET_CONFIGURATION" 0 0 4 0x20 "(value &
> 0xff)" "(value >> 8) & 0xff" "reg"
>
> Such a command can easily be added like a devd script to run automatically
> during device attach.
>
>
>  646
>>   647 static int snd_usb_cm106_boot_quirk(struct usb_device *dev)
>> 648 {
>> 649 /*
>> 650 * Enable line-out driver mode, set headphone source to front
>> 651 * channels, enable stereo mic.
>> 652 */
>> 653 return snd_usb_cm106_write_int_reg(dev, 2, 0x8004);
>> 654 }
>> 655
>>   656 /*
>> 657 * C-Media CM6206 is based on CM106 with two additional
>> 658 * registers that are not documented in the data sheet.
>> 659 * Values here are chosen based on sniffing USB traffic
>> 660 * under Windows.
>> 661 */
>> 662 static int snd_usb_cm6206_boot_quirk(struct usb_device *dev)
>> 663 {
>> 664 int err  = 0, reg;
>> 665 int val[] = {0x2004, 0x3000, 0xf800, 0x143f, 0x, 0x3000};
>> 666
>>   667 for (reg = 0; reg < ARRAY_SIZE(val); reg++) {
>> 668 err = snd_usb_cm106_write_int_reg(dev, reg, val[reg]);
>> 669 if (err < 0)
>> 670 return err;
>> 671 }
>> 672
>>   673 return err;
>> 674 }
>> 675
>>
>> How can I test this code in FreeBSD ?
>>
>>
> See answer above.
>
> Please also use -stable or -current when testing.
>
> --HPS
>
>
Thank you Hans, it works !!!
This is only the first step in supporting the C-Media CM6206 in FreeBSD,
but works.

I have converted the C code in a bash script: snd-cm6206.sh  available at
http://pastebin.com/dLtJAqE7
Instructions:
- Connect the USB cable of the CM6206
- With the command
  # dmesg | tail
  look at the the line : ugenX.Y:  at usbus
  and the line : pcmZ:  on uaudio
- Run the script:  # snd-cm6206.sh X.Y
- Run the command: # sysctl hw.snd.default_unit=Z
- Reduce the volume ;-) : # mixer -f /dev/mixerZ 10

On my laptop running 11-CUR

CM6206 USB Audio is mute.

[Ranjan1018 .]

Connecting the USB cable the item is recognized:
ugen0.5:  at usbus0
uaudio0: 
on usbus0
uaudio0: Play: 48000 Hz, 4 ch, 16-bit S-LE PCM format, 2x8ms buffer.
uaudio0: Play: 44100 Hz, 4 ch, 16-bit S-LE PCM format, 2x8ms buffer.
uaudio0: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer.
uaudio0: Record: 44100 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer.
uaudio0: No MIDI sequencer.
pcm1:  on uaudio0
uaudio0: HID volume keys found.

Setting it as default unit
# sysctl  hw.snd.default_unit=1
and playing a song the interrupts count increase:
# sysctl hw.snd.verbose=2
# cat /dev/sndstat
FreeBSD Audio Driver (64bit 2009061500/amd64)
Installed devices:
pcm0:  on hdaa0  (1p:1v/0r:0v)
snddev
flags=0x2e7
[pcm0:play:dsp0.p0]: spd 48000, fmt 0x00200010, flags 0x6100,
0x0004
interrupts 0, underruns 0, feed 0, ready 0
[b:4096/2048/2|bs:4096/2048/2]
channel flags=0x6100
{userland} -> feeder_mixer(0x00200010) -> {hardware}
pcm0:play:dsp0.p0[pcm0:virtual:dsp0.vp0]: spd 8000, fmt 0x0018,
flags 0x1000, 0x
interrupts 0, underruns 0, feed 0, ready 0 [b:0/0/0|bs:0/0/0]
channel flags=0x1000
{userland} -> feeder_root(0x) -> {hardware}
pcm1:  at ? kld snd_uaudio (1p:1v/1r:1v) default
snddev flags=0x2e6
[pcm1:play:dsp1.p0]: spd 48000, fmt 0x00200010/0x00400010, flags
0x2108, 0x0044
interrupts 4926, underruns 0, feed 9850, ready 0
[b:6144/3072/2|bs:4096/2048/2]
channel flags=0x2108
{userland} -> feeder_mixer(0x00200010) -> feeder_matrix(2.0 -> 4.0) ->
{hardware}
pcm1:play:dsp1.p0[pcm1:virtual:dsp1.vp0]: spd 44100/48000, fmt
0x00200010, flags 0x110c, 0x0029, pid 1769 (mplayer)
interrupts 0, underruns 0, feed 9287, ready 62192
[b:0/0/0|bs:65536/2048/32]
channel flags=0x110c
{userland} -> feeder_root(0x00200010) -> feeder_volume(0x00200010) ->
feeder_rate(0x00200010 q:1 44100 -> 48000) -> {hardware}
[pcm1:record:dsp1.r0]: spd 48000, fmt 0x00200010, flags 0x2100,
0x0005
interrupts 0, overruns 0, feed 0, hfree 3072, sfree 4096
[b:3072/1536/2|bs:4096/2048/2]
channel flags=0x2100
{hardware} -> feeder_root(0x00200010) -> feeder_mixer(0x00200010) ->
{userland}
pcm1:record:dsp1.r0[pcm1:virtual:dsp1.vr0]: spd 8000, fmt 0x0018,
flags 0x1000, 0x
interrupts 0, overruns 0, feed 0, hfree 0, sfree 0 [b:0/0/0|bs:0/0/0]
channel flags=0x1000
{hardware} -> feeder_root(0x) -> {userland}

But the output is mute.

In Debian Linux it works:
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 014: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound
Device
# aplay -l
 List of PLAYBACK Hardware Devices 
card 1: Device [USB Sound Device], device 0: USB Audio [USB Audio]
 Subdevices: 0/1
 Subdevice #0: subdevice #0

Looking at http://lxr.free-electrons.com/source/sound/usb/quirks.c I have
found this code:
/*
632 * C-Media CM106/CM106+ have four 16-bit internal registers that are
nicely
633 * documented in the device's data sheet.
634 */
635 static int snd_usb_cm106_write_int_reg(struct usb_device *dev, int reg,
u16 value)
636 {
637 u8 buf[4];
638 buf[0] = 0x20;
639 buf[1] = value & 0xff;
640 buf[2] = (value >> 8) & 0xff;
641 buf[3] = reg;
642 return snd_usb_ctl_msg(dev, usb_sndctrlpipe(dev, 0),
USB_REQ_SET_CONFIGURATION,
643USB_DIR_OUT | USB_TYPE_CLASS |
USB_RECIP_ENDPOINT,
6440, 0, &buf, 4);
645 }
646
 647 static int snd_usb_cm106_boot_quirk(struct usb_device *dev)
648 {
649 /*
650 * Enable line-out driver mode, set headphone source to front
651 * channels, enable stereo mic.
652 */
653 return snd_usb_cm106_write_int_reg(dev, 2, 0x8004);
654 }
655
 656 /*
657 * C-Media CM6206 is based on CM106 with two additional
658 * registers that are not documented in the data sheet.
659 * Values here are chosen based on sniffing USB traffic
660 * under Windows.
661 */
662 static int snd_usb_cm6206_boot_quirk(struct usb_device *dev)
663 {
664 int err  = 0, reg;
665 int val[] = {0x2004, 0x3000, 0xf800, 0x143f, 0x, 0x3000};
666
 667 for (reg = 0; reg < ARRAY_SIZE(val); reg++) {
668 err = snd_usb_cm106_write_int_reg(dev, reg, val[reg]);
669 if (err < 0)
670 return err;
671 }
672
 673 return err;
674 }
675

How can I test this code in FreeBSD ?

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

Re: CTF: wpa_supplicant/hostapd 2.4 import

[Ranjan1018 .]

2015-04-19 23:35 GMT+02:00 Rui Paulo :

> Hi,
>
> Please test the new wpa_supplicant/hostapd.  Here's the patch against
> FreeBSD
> HEAD:
>
> https://people.freebsd.org/~rpaulo/wpa-2.4.diff
>
> Thanks,
>
>
It works for me with LAGG(4).
# uname -a
FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #5 r281782M: Mon Apr 20
21:31:22 CEST 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

# ifconfig
ath0: flags=8843 metric 0 mtu 2290
ether 18:67:b0:39:bd:23
nd6 options=21
media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
status: associated
re0: flags=8843 metric 0 mtu 1500

options=8209b
ether 18:67:b0:39:bd:23
nd6 options=29
media: Ethernet autoselect (none)
status: no carrier
lo0: flags=8049 metric 0 mtu 16384
options=63
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet 127.0.0.1 netmask 0xff00
nd6 options=21
groups: lo
lagg0: flags=8843 metric 0 mtu 1500
ether 18:67:b0:39:bd:23
inet 192.168.0.51 netmask 0xff00 broadcast 192.168.0.255
nd6 options=29
media: Ethernet autoselect
status: active
groups: lagg
laggproto failover lagghash l2,l3,l4
laggport: re0 flags=1
laggport: wlan0 flags=4
wlan0: flags=8843 metric 0 mtu 1500
ether 18:67:b0:39:bd:23
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid netis channel 1 (2412 MHz 11g ht/20) bssid 08:10:77:53:bc:b5
regdomain 101 indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF TKIP 2:128-bit txpower 20 bmiss 7 scanvalid 60
protmode CTS ampdulimit 32k ampdudensity 16 shortgi wme burst
roaming MANUAL
groups: wlan
vboxnet0: flags=8802 metric 0 mtu 1500
ether 0a:00:27:00:00:00
nd6 options=29
media: Ethernet autoselect
status: active
tun0: flags=8051 metric 0 mtu 1500
options=8
inet6 fe80::1a67:b0ff:fe39:bd23%tun0 prefixlen 64 scopeid 0x7
inet 10.7.0.6 --> 10.7.0.5 netmask 0x
nd6 options=21
groups: tun
Opened by PID 990
tun1: flags=8051 metric 0 mtu 1500
options=8
inet6 fe80::1a67:b0ff:fe39:bd23%tun1 prefixlen 64 scopeid 0x8
inet 10.8.0.14 --> 10.8.0.13 netmask 0x
nd6 options=21
groups: tun
Opened by PID 997

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

Re: Synaptics Touchpad stops working in r281560

[Ranjan1018 .]

2015-04-16 20:06 GMT+02:00 Jan Kokemüller :

>
> On 16.04.2015 06:16, Ranjan1018 . wrote:
>
>> Upgrade from r280855 to r281560 (amd64) on a Samsung Ativ Book 2 Laptop.
>> The Synaptics Touchpad stops working,  in Xorg.0.log  I have the error
>> message :
>>
>> [  1047.413] (EE) synaptics: Mouse: Unable to query/initialize Synaptics
>> hardware.
>>
>> [  1047.449] (EE) PreInit returned 11 for "Mouse"
>>
>
>
> Could you try to rebuild xf86-input-synaptics via ports? The kernel ABI
> has changed due to the additions to synapticshw_t in
> /usr/include/sys/mouse.h. The xorg driver calls the MOUSE_SYN_GETHWINFO
> ioctl which returns a synapticshw_t.
>

Thanks Jan, it works !
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Synaptics Touchpad stops working in r281560

[Ranjan1018 .]

2015-04-16 6:36 GMT+02:00 Rui Paulo :

> On Thursday 16 April 2015 06:16:45 Ranjan1018 . wrote:
> > Upgrade from r280855 to r281560 (amd64) on a Samsung Ativ Book 2 Laptop.
> > The Synaptics Touchpad stops working,  in Xorg.0.log  I have the error
> > message :
> >
> > [  1047.413] (EE) synaptics: Mouse: Unable to query/initialize Synaptics
> > hardware.
> >
> > [  1047.449] (EE) PreInit returned 11 for "Mouse"
>
> What are your boot loader settings?
>
> --
> Rui Paulo
>

My /boot/loader.conf is:
zfs_load=YES
vfs.root.mountfrom="zfs:sys/ROOT/CURRENT"

# solo prova
drm.i915.init_backlight=10
#i915kms_load="YES"

# ZFS tunable
vfs.zfs.prefetch_disable=0 # funzia!

# Synaptics
hw.psm.synaptics_support=1

# Shutdown
hw.usb.no_shutdown_wait=1

# Risparmio energia
hint.p4tcc.0.disabled=1
hint.acpi_throttle.0.disabled=1
drm.i915.enable_rc6=7
hw.snd.latency=10

# LAGG(4)
#if_lagg_load="YES" # Lo carico in rc.conf
# VirtualBox
#vboxdrv_load="YES" # Lo carico in rc.conf
# DVD: 18.6.2. Configuration
hw.ata.atapi_dma="1"

hw.pci.clear_buses=1
hw.pci.clear_bars=1
hw.pci.clear_pcib=1
# Qt paint engine makes common use of shared memory...
kern.ipc.shmall=32768
kern.ipc.shmmni=1024
kern.ipc.shmseg=1024
# SOLO RPOVA
#hw.x2apic_enable=0

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

Synaptics Touchpad stops working in r281560

[Ranjan1018 .]

Upgrade from r280855 to r281560 (amd64) on a Samsung Ativ Book 2 Laptop.
The Synaptics Touchpad stops working,  in Xorg.0.log  I have the error
message :

[  1047.413] (EE) synaptics: Mouse: Unable to query/initialize Synaptics
hardware.

[  1047.449] (EE) PreInit returned 11 for "Mouse"


Regards

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

Re: [PATCH] Adding backlight support for the i915 driver.

[Ranjan1018 .]

2015-03-27 16:53 GMT+01:00 Hans Petter Selasky :

> On 03/27/15 16:01, Ranjan1018 . wrote:
>
>> This  patch exposes the backlight support  via a sysctl:
>>
>> set the backlight to 10%:
>>
>> # sysctl hw.dri.0.i915_backlight=10
>>
>> hw.dri.0.i915_backlight: 25 -> 10
>>
>> set the backlight to 50%:
>>
>> # sysctl hw.dri.0.i915_backlight=50
>>
>> hw.dri.0.i915_backlight: 10 -> 50
>>
>> decrease  the current backlight value:
>>
>> # sysctl hw.dri.0.i915_backlight=-1000
>>
>> hw.dri.0.i915_backlight: 50 -> 43
>>
>> increment the current backlight value:
>>
>> # sysctl hw.dri.0.i915_backlight=1000
>>
>> hw.dri.0.i915_backlight: 43 -> 51
>>
>> # sysctl hw.dri.0.i915_backlight=1000
>>
>> hw.dri.0.i915_backlight: 51 -> 60
>>
>> I am running this path on for about a week without issue.
>>
>> This path can be found at:
>> https://github.com/maurizio-emmex/i915_backlight_freebsd
>>
>> I thank Elizabeth Myers, elizabeth at interlinked dot me, for the idea of
>> adding the backlight support for the i915 driver and for the original
>> patch.
>>
>> Regards,
>> Maurizio
>>
>
> Maybe you want to use "CTLFLAG_RWTUN" so that it also can be set from
> /boot/loader.conf ?
>
> --HPS
>

The ability to set the backlight at startup may be useful. With this new
patch I expose two ways to do this:
- with the tunable "drm.i915.init_backlight" in /boot/loader.conf, just
after the driver initialization (eg.  drm.i915.init_backlight=20)
- with the OID "hw.dri.0.i915_backlight" in /etc/sysctl.conf as suggested
by Hans
I don’t know if setting the backlight with the tunable
"drm.i915.init_backlight" is useful, but I have already written the code
and is simple to remove it.
The patch file is i915_backlight.patch at
https://github.com/maurizio-emmex/i915_backlight_freebsd

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

[PATCH] Adding backlight support for the i915 driver.

[Ranjan1018 .]

This  patch exposes the backlight support  via a sysctl:

set the backlight to 10%:

# sysctl hw.dri.0.i915_backlight=10

hw.dri.0.i915_backlight: 25 -> 10

set the backlight to 50%:

# sysctl hw.dri.0.i915_backlight=50

hw.dri.0.i915_backlight: 10 -> 50

decrease  the current backlight value:

# sysctl hw.dri.0.i915_backlight=-1000

hw.dri.0.i915_backlight: 50 -> 43

increment the current backlight value:

# sysctl hw.dri.0.i915_backlight=1000

hw.dri.0.i915_backlight: 43 -> 51

# sysctl hw.dri.0.i915_backlight=1000

hw.dri.0.i915_backlight: 51 -> 60

I am running this path on for about a week without issue.

This path can be found at:
https://github.com/maurizio-emmex/i915_backlight_freebsd

I thank Elizabeth Myers, elizabeth at interlinked dot me, for the idea of
adding the backlight support for the i915 driver and for the original patch.

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

Re: [Call for testers] DRM device-independent code update to Linux 3.8

[Ranjan1018 .]

2015-02-18 0:45 GMT+01:00 Jean-Sébastien Pédron :

> Hi!
>
> An update to the DRM subsystem, not including the drivers, is ready for
> wider testing!
>
> The patch against HEAD is here:
> https://people.freebsd.org/~dumbbell/graphics/drm-update-38.f.patch
>
> I'm interested in success/failure reports for amd64, powerpc and
> powerpc64 users, for i915 and Radeon GPUs. I already know there is a
> build issue on i386, please wait for the next patch if you are in this
> case.
>
> The changes brought by this patch are explained in a blog post:
> http://blogs.freebsdish.org/graphics/2015/02/18/testing-the-drm-update/
>
> This is working well for some Radeon users for more than a year.
> However, it only started to work with i915 a month ago, when the i915
> refresh was committed.
>
> Try your day-to-day applications, try suspend/resume, try all output
> connectors, try OpenGL stuff, try backlight controls, everything :)
>
> Thank you!
>
> --
> Jean-Sébastien Pédron
>
> Just upgraded my laptop to r278960.
Testing the patch I receive these errors:
# patch -sC < ~/downloads/drm-update-38.f.patch
1 out of 3 hunks failed while patching sys/dev/drm2/drm_agpsupport.c
1 out of 4 hunks failed while patching sys/dev/drm2/drm_auth.c
1 out of 26 hunks failed while patching sys/dev/drm2/drm_bufs.c
1 out of 17 hunks failed while patching sys/dev/drm2/drm_context.c
1 out of 39 hunks failed while patching sys/dev/drm2/drm_crtc.h
1 out of 5 hunks failed while patching sys/dev/drm2/drm_dma.c
1 out of 1 hunks failed while patching sys/dev/drm2/drm_drawable.c
1 out of 8 hunks failed while patching sys/dev/drm2/drm_drv.c
1 out of 5 hunks failed while patching sys/dev/drm2/drm_edid.h
1 out of 17 hunks failed while patching sys/dev/drm2/drm_edid_modes.h
1 out of 7 hunks failed while patching sys/dev/drm2/drm_fb_helper.h
1 out of 9 hunks failed while patching sys/dev/drm2/drm_fops.c
1 out of 3 hunks failed while patching sys/dev/drm2/drm_fourcc.h
1 out of 1 hunks failed while patching sys/dev/drm2/drm_internal.h
1 out of 4 hunks failed while patching sys/dev/drm2/drm_ioctl.c
1 out of 50 hunks failed while patching sys/dev/drm2/drm_irq.c
1 out of 3 hunks failed while patching sys/dev/drm2/drm_lock.c
1 out of 2 hunks failed while patching sys/dev/drm2/drm_memory.c
1 out of 10 hunks failed while patching sys/dev/drm2/drm_mm.h
1 out of 11 hunks failed while patching sys/dev/drm2/drm_mode.h
1 out of 1 hunks failed while patching sys/dev/drm2/drm_sman.c
1 out of 1 hunks failed while patching sys/dev/drm2/drm_sman.h
1 out of 4 hunks failed while patching sys/modules/drm2/radeonkms/Makefile

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

Re: Suspend/resume on i915 stop working between r278348 and r278741.

[Ranjan1018 .]

2015-02-16 10:50 GMT+01:00 Konstantin Belousov :

> On Sun, Feb 15, 2015 at 08:43:55PM +0100, Ranjan1018 . wrote:
> > 2015-02-15 19:59 GMT+01:00 Konstantin Belousov :
> >
> > > On Sun, Feb 15, 2015 at 07:45:44PM +0100, Ranjan1018 . wrote:
> > > >
> > > > Unfortunately does not work for me. Tested with r278803.
> > >
> > > Does your machine resume if you boot with hw.x2apic_enable set to 0
> > > from the loader prompt ?
> >
> > Yes. I have added to it to loader.conf
> > $ cat /boot/loader.conf | grep x2apic_enable
> > hw.x2apic_enable=0
> >
> >   Confirm that x2apic is disabled after tunable
> > > frobbing, with sysctl hw.apic.x2apic_mode.
> > >
> > $ sysctl hw.apic.x2apic_mode
> > hw.apic.x2apic_mode: 0
>
> And, does your machine resumed successfully with the tunable set ?
>
Yes.

>
> Below is the patch which seemingly worked for Gleb.
> You should not set the tunable to test it properly.
>
> diff --git a/sys/amd64/amd64/mp_machdep.c b/sys/amd64/amd64/mp_machdep.c
> index 13c3d43..b767691 100644
> --- a/sys/amd64/amd64/mp_machdep.c
> +++ b/sys/amd64/amd64/mp_machdep.c
> @@ -1507,6 +1507,7 @@ cpususpend_handler(void)
> vmm_resume_p();
>
> /* Resume MCA and local APIC */
> +   lapic_xapic_mode();
> mca_resume();
> lapic_setup(0);
>
> diff --git a/sys/i386/i386/mp_machdep.c b/sys/i386/i386/mp_machdep.c
> index 32b9540..a80de54 100644
> --- a/sys/i386/i386/mp_machdep.c
> +++ b/sys/i386/i386/mp_machdep.c
> @@ -1555,6 +1555,7 @@ cpususpend_handler(void)
> cpu_ops.cpu_resume();
>
> /* Resume MCA and local APIC */
> +   lapic_xapic_mode();
> mca_resume();
> lapic_setup(0);
>
> diff --git a/sys/x86/acpica/acpi_wakeup.c b/sys/x86/acpica/acpi_wakeup.c
> index 74522be..e652419 100644
> --- a/sys/x86/acpica/acpi_wakeup.c
> +++ b/sys/x86/acpica/acpi_wakeup.c
> @@ -270,6 +270,7 @@ acpi_wakeup_machdep(struct acpi_softc *sc, int state,
> int sleep_result,
> initializecpu();
> PCPU_SET(switchtime, 0);
> PCPU_SET(switchticks, ticks);
> +   lapic_xapic_mode();
>  #ifdef SMP
> if (!CPU_EMPTY(&suspcpus))
> acpi_wakeup_cpus(sc);
> diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c
> index 1809fa6..1b66674 100644
> --- a/sys/x86/x86/local_apic.c
> +++ b/sys/x86/x86/local_apic.c
> @@ -527,7 +527,6 @@ native_lapic_xapic_mode(void)
> saveintr = intr_disable();
> if (x2apic_mode)
> native_lapic_enable_x2apic();
> -   native_lapic_disable();
> intr_restore(saveintr);
>  }
>
>
Thank you Konstantin, it works for me too!

I have commented 'hw.x2apic_enable=0' in /boot/loader.conf
$ cat /boot/loader.conf | grep x2apic_enable
#hw.x2apic_enable=0

the 2xapic result enabled
$ sysctl hw.apic.x2apic_mode
hw.apic.x2apic_mode: 1

and suspend/resume works again.

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

Re: Suspend/resume on i915 stop working between r278348 and r278741.

[Ranjan1018 .]

2015-02-15 19:59 GMT+01:00 Konstantin Belousov :

> On Sun, Feb 15, 2015 at 07:45:44PM +0100, Ranjan1018 . wrote:
> >
> > Unfortunately does not work for me. Tested with r278803.
>
> Does your machine resume if you boot with hw.x2apic_enable set to 0
> from the loader prompt ?

Yes. I have added to it to loader.conf
$ cat /boot/loader.conf | grep x2apic_enable
hw.x2apic_enable=0

  Confirm that x2apic is disabled after tunable
> frobbing, with sysctl hw.apic.x2apic_mode.
>
$ sysctl hw.apic.x2apic_mode
hw.apic.x2apic_mode: 0
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Suspend/resume on i915 stop working between r278348 and r278741.

[Ranjan1018 .]

2015-02-15 16:11 GMT+01:00 Konstantin Belousov :

> On Sun, Feb 15, 2015 at 03:37:17PM +0100, Ranjan1018 . wrote:
> > Hi,
> > the bug was introduced in r278473. Suspend/resume works again if I
> disable
> > the x2APIC support with hw.x2apic_enable=0 in /boot/loader.conf, tested
> in
> > r278473 and r278741.
>
> So how it is related to i915 ?
>
> Sorry, just my guess.


> Try the patch.
>
> diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c
> index 1809fa6..c8ea35e 100644
> --- a/sys/x86/x86/local_apic.c
> +++ b/sys/x86/x86/local_apic.c
> @@ -541,6 +541,9 @@ native_lapic_setup(int boot)
>
> saveintr = intr_disable();
>
> +   if (!boot && x2apic_mode)
> +   native_lapic_enable_x2apic();
> +
> la = &lapics[lapic_id()];
> KASSERT(la->la_present, ("missing APIC structure"));
> maxlvt = (lapic_read32(LAPIC_VERSION) & APIC_VER_MAXLVT) >>
> MAXLVTSHIFT;
>

Unfortunately does not work for me. Tested with r278803.

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

Re: Suspend/resume on i915 stop working between r278348 and r278741.

[Ranjan1018 .]

Hi,
the bug was introduced in r278473. Suspend/resume works again if I disable
the x2APIC support with hw.x2apic_enable=0 in /boot/loader.conf, tested in
r278473 and r278741.

Regards,
Maurizio  2015-02-15 2:03 GMT+01:00 Adrian Chadd :

> Hi,
>
> Can you narrow it down a little further please? That'd be really helpful.
>
> Thanks!
>
>
> -adrian
>
>
> On 14 February 2015 at 13:31, Ranjan1018 . <21474...@gmail.com> wrote:
> > Just updated my Samsung Ativ Book 2, running 11-CURRENT, from r278348 to
> > r278741.
> > Now suspend via ‘acpiconf -s3’ does not work: the LCD stay dark, the
> > keyboard doesn't react when pressing CapsLock and I have to switch the
> > laptop off pressing the power button.
> >
> > Regards,
> > Maurizio
> > ___
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Suspend/resume on i915 stop working between r278348 and r278741.

[Ranjan1018 .]

Just updated my Samsung Ativ Book 2, running 11-CURRENT, from r278348 to
r278741.
Now suspend via ‘acpiconf -s3’ does not work: the LCD stay dark, the
keyboard doesn't react when pressing CapsLock and I have to switch the
laptop off pressing the power button.

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

Re: Questions on adding backlight support for the i915 driver

[Ranjan1018 .]

> I have a sort of "rough draft" of this. I've tested all the percentages
> (Ivy Bridge) and they do seem to correlate linearly (and to the
> intel_backlight userland program used by a lot of people). I haven't
> been able to test on any other hardware as I don't have it, and I don't
> know what chipsets require the value to be inverted, so I've not
> implemented that.
>
> If anyone else would like to help test, it'd be nice.
>
>
Thank you Elizabeth for the patch. It works on my Samsung Ativ Book 2 with
Ivy Bridge.
I have modified the patch for 11-CURRENT and corrected these little bugs:
1) is possible to specify a percentage greater than 100%
eg. with the command: ‘sysctl hw.dri.0.i915_backlight=111’ is possible to
set the hardware register above the maximum allowed.
2) the percentage values are truncated instead of rounded:
if I set 10% with the intel_backlight program is reported as 9% with the
command ‘sysctl hw.dri.0.i915_backlight’:
# intel_backlight 10
current backlight value: 20% (976/4882)
set backlight to 10% (488/4882)
# sysctl hw.dri.0.i915_backlight
hw.dri.0.i915_backlight: 9
but 488/4882 is more near to 10% than 9%

I have tested the patch with:
# uname -a
FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #10 r277961: Sat Jan 31
06:03:15 CET 2015 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

The patch is available at: http://pastebin.com/vKK7026H

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

Re: drm2 regression: backlight adjustment on ivybridge no longer works

[Ranjan1018 .]

2015-01-28 10:11 GMT+01:00 Adrian Chadd :

> ugh, so because i can't sleep, I read the Linux i915 history for
> backlight changes.
>
> Turns out if I disable bit 30 in ivb_pch_pwm_override() to register
> BLC_PWM_PCH_CTL1, the acpi video setting works. The keyboard settings
> still don't, but I'll worry about that later.
>
> Bit 30 in the linux drm code is:
>
> #define   BLM_PCH_OVERRIDE_ENABLE   (1 << 30)
>
> The linux dri code doesn't set that for ivybridge - only for broadwell.
>
> (also, the linux driver has POSTING_READ() which I'm guessing is to
> ensure things made it out to the device and have been flushed before
> doing another IO operation.)
>
> I have my (via sysctl) panel backlight control working again.
>
>
>
> -adrian
>

Thank you guys,
the backlight control works again on my laptop with this patch, suggested
by Adrian :

--- sys/dev/drm2/i915/intel_display.c.orig   (revision 277487)
+++ sys/dev/drm2/i915/intel_display.c(working copy)
@@ -6995,7 +6995,7 @@
  */
 I915_WRITE(BLC_PWM_CPU_CTL2, PWM_ENABLE);
 I915_WRITE(BLC_PWM_CPU_CTL, 0);
-I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE | (1<<30));
+I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE);
 }

 void intel_modeset_init_hw(struct drm_device *dev)

but the patch by Andrew does not hurts:
http://foxkit.us/FreeBSD/i915-uninitialised-var-fix.diff

I am running r277871 with both patches applied.

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

Re: drm2 regression: backlight adjustment on ivybridge no longer works

[Ranjan1018 .]

2015-01-27 7:38 GMT+01:00 Andrew Wilcox :

> Ranjan1018 . sent: 26 January 2015 06:19:
> > 2015-01-24 23:25 GMT+01:00 Adrian Chadd :
> > > The backlight adjustment doesn't work on my ivybridge mobile laptop
> > > (Lenovo X230) after the dri update.
> > >
> > I have the same issue on my Samsung Ativ 2 laptop.
>
> I have a Sandy Bridge laptop (Apple MacBook Pro 8,2) - HD 3000:
>
> vgapci0@pci0:0:2:0: class=0x03 card=0x00db106b chip=0x01268086
> rev=0x09 hdr=0x00
> vendor = 'Intel Corporation'
> device = '2nd Generation Core Processor Family Integrated Graphics
> Controller'
> class  = display
> subclass   = VGA
>
> It is running:  FreeBSD pwyll.foxkit.us 11.0-CURRENT #1 r277781M: Mon Jan
> 26 18:41:15 CST 2015 r...@pwyll.foxkit.us:/usr/obj/usr/src/sys/GENERIC
> amd64
>
> I have no issues using acpi_video's sysctls
> (hw.acpi.video.lcd0.brightness) to adjust backlight, though it does not
> have good granularity.  The stepping is about 7, so it goes as
> 13%..20%..27%..35%..etc.
>
> > > The "intel_backlight" program from intel-gpu-tools" also no longer
> > > changes the backlight value.
>
> This program works fine for me on both an older kernel (r277523) and this
> kernel (r277781), after applying some patches to allow the library to build
> on FreeBSD.  It also has better granularity (the stepping is 2-3).
>
> If there is anything I can do/run to aide in debugging why it works for me
> but not others, let me know.
>
> Best,
> Andrew
> --
> Andrew Wilcox, C/C++/Python developer, kernel hacker
> Blog:   http://blog.foxkit.us/  WWW: http://foxkit.us/
> GitHub:  https://github.com/awilfox
>
> Hi,
my Samsung laptop has an Intel IvyBridge:
vgapci0@pci0:0:2:0: class=0x03 card=0xc708144d chip=0x01668086
rev=0x09 hdr=0x00
vendor = 'Intel Corporation'
device = '3rd Gen Core processor Graphics Controller'
class  = display
subclass   = VGA

The regression was introduced in r277487.
The backlight adjustment works in FreeBSD 11.0-CURRENT r277395, r277486 but
not in r277487, r277534 and r277639.

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

Re: drm2 regression: backlight adjustment on ivybridge no longer works

[Ranjan1018 .]

2015-01-24 23:25 GMT+01:00 Adrian Chadd :

> Hi,
>
> I've just found a regression.
>
> The backlight adjustment doesn't work on my ivybridge mobile laptop
> (Lenovo X230) after the dri update.
>
> I've added debugging. It's making it all the way to the pch backlight
> panel update routine in intel_panel.c, but it's not changing the
> backlight appearance itself.
>
> The "intel_backlight" program from intel-gpu-tools" also no longer
> changes the backlight value.
>
> I'm going to finish rebuilding -HEAD on the sandy bridge laptop here
> and try it out.
>
> Thanks,
>
>
>
> -adrian
>

Hi,
I have the same issue on my Samsung Ativ 2 laptop.

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

i915 backlight control broken

[Ranjan1018 .]

Just upgraded my laptop from r277395 to r277534. The backlight control via
hw.acpi.video.lcd0.brightness do not works: the backlight is always at 100%.

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

Re: Intel i915 GPU hung

[Ranjan1018 .]

2014-09-11 16:49 GMT+02:00 Ranjan1018 . <21474...@gmail.com>:

>
> Hello,
>
> I have just upgrade my laptop, a Samsung Ativ Book 2 with an integrated
> Intel HD Graphics 4000, to:
>
> FreeBSD ativ.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r271400: Wed Sep
> 10 21:40:48 CEST 2014 root@ativ.local:/usr/obj/usr/src/sys/NEWCONS
> amd64
>
> Using Firefox, after some minutes, I receive the error:
>
> error: [drm:pid12:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
> elapsed... GPU hung
> info: [drm] capturing error event; look for more information in sysctl
> hw.dri.0.info.i915_error_state
>
> This error is not related to r271400, but I first saw it few months ago in
> current.
>
> The output of the command
> sysctl hw.dri.0.info.i915_error_state
> is:
>
>
> https://drive.google.com/file/d/0BzoWQoMqq1sfa0tyVGJVYVBhRnc/edit?usp=sharing
>
> After the error I am not able to run mplayer for videos: the window is
> black.
>
> Regards,
> Maurizio
>
> I resume this my old thread to say that it is at least a month that my
laptop do not crashes.

Now I am running:
# uname -a
FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r275958: Sat Dec 20
19:22:20 CET 2014 root@ativ:/usr/obj/usr/src/sys/GENERIC  amd64

with xorg:
# pkg info | grep xorg-server
xorg-server-1.14.7,1   X.Org X server and related programs

Merry Christmas To All.

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

Re: sysctl -zarc for ZFS users

[Ranjan1018 .]

2014-12-08 5:34 GMT+01:00 Yoshihiro Ota :
>
> Thank you for your report, Maurizio.
>
> I missed 'svn add zarc.c' and resuled an incompelte patch.
> I uploaded a new one with a complete set to the bugzilla.
>
> Please try against clean directory, i.e. svn revert -R usr.bin/systat.
>
> Thanks,
> Hiro
>
>
> On Sat, 6 Dec 2014 15:28:05 +0100
> "Ranjan1018 ." <21474...@gmail.com> wrote:
>
> > 2014-12-06 11:35 GMT+01:00 Yoshihiro Ota :
> >
> > > Hi all.
> > >
> > > I've been watching ZFS activites on my machine and
> > > improved systat to monitor such.
> > >
> > > One of my first goals is to watch ZFS cache statistics.
> > >
> > > I posted my patch to the bugzilla @
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195460
> > > I've been using on 11-CURRENT and 10.1-RELEASE myself.
> > >
> > > Regards,
> > > Hiro
> > >
> > > % systat -zarc
> > >Total MFU MRUAnon Hdr   L2Hdr
> > >  Other
> > >  ZFS ARC206M 63M136M826K   1102K  0K
> > >  5251K
> > >
> > > ratehits  misses   total hits total
> > > misses
> > >  arcstats  : 75%1183 38823721
> > >  4202
> > >  arcstats.demand_data  :  0%   0   0  528
> > >   0
> > >  arcstats.demand_metadata  : 76%1007 30821441
> > >  2757
> > >  arcstats.prefetch_data:  0%   0   00
> > >   0
> > >  arcstats.prefetch_metadata: 68% 176  80 1752
> > >  1445
> > >  zfetchstats   : 44% 954120426410
> > > 25482
> > >  arcstats.l2   :  0%   0   00
> > >   0
> > >  vdev_cache_stats  :  0%   0   00
> > >   0
> > >
> >
> > Hi Hiro,
> >
> > just applied the patch, but I receive the error:
> >
> > # make
> > make: don't know how to make zarc.c. Stop
> > make: stopped in /usr/src/usr.bin/systat
> >
> > The file zarc,c is missing. Where can I find it ?
> >
> > Thanks.
> > Maurizio
> > ___
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscr...@freebsd.org"
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>

This patch is running on a 9.3-STABLE server for about a week with no
problems.
Only two cosmetics issues
- big numbers are difficult to read eg.

zfetchstats   : 99% 646   4272407322143761103

is more readable, for me, as

 zfetchstats   : 99% 646   4272.41M143.76M

- a total rate percent is missing.

Thank you for your work Hiro.
--
Maurizio.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: LOR on head using virtualbox between intel kms and sound, with system lockup

[Ranjan1018 .]

2014-12-09 23:39 GMT+01:00 Guido Falsi :

> Hi,
>
> I've experienced a  hard lockup on head r275563, amd64.
>
> The hardware is a laptop with an intel graphics card.
>
> If any further info is required just ask.
>
> I had just launched a virtualbox VM with Windows 7, the system locked up
> just after the startup sound was played in the VM, X11 disappeared and
> the system locked hard and a LOR data on screen.
>
> (I already tested recompiling the virtualbox kmod and the bug shows up
> with and without 3d/2d acceleration enabled in the VM)
>
> I copied (by hand, so sorry for any typos) the LOR data:
>
> Lock order reversal: (sleepable after non-sleepable)
>  1st 0xf8000874da90 so_snd (so_snd) @
> /usr/src/sys/kern/uipc_sockbuf.c:666
>  2nd 0xf80057ff20a0 drmslk (drmslk) @
>
> /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/intel_display.c:2317
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> 0xfe022ed8eff0
> kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe022ed8f0a0
> witness_checkorder() at witness_checkorder+x0dad/frame 0xfe022ed8f130
> _sx_xlock() at _sx_xlock+0x71/frame 0xfe022ed8f170
> intel_pipe_set_base() at intel_pipe_set_base+0x77/frame 0xfe022ed8f1d8
> drm_crtc_helper_set_config() at drm_crtc_helper_set_config+0x7c0/frame
> 0xfe022ed8f290
> vt_kms_postswitch() at vt_kms_postswitch+0x5c/frame 0xfe022ed8f2c0
> vt_window_switch() at vt_window_switch+0xc3/frame 0xfe022ed8f300
> vtterm_cngrab() at vtterm_cngrab+0x23/frame 0xfe022ed8f320
> cngrab() at cngrab+0x35/frame 0xfe022ed8f340
> kdb_trap() at kdb_trap+0x183/frame 0xfe022ed8f3e0
> trap_fatal() at ytap_fatal+0x34c/frame 0xfe022ed8f440
> trap_pfault() at trap_pfault+0x262/frame 0xfe022ed8f4a0
> trap() at trap+0x44c/frame 0xfe022ed8f5f0
> calltrap() at calltrap+0x8/frame 0xfe022ed8f5f0
> --- trap 0xc, tip = 0x8056834d, rsp = 0xfe022ed8f6b0, rbp =
> 0xfe022ed8f6e0 ---
> sbappendstream_locked() at sbappendstream_locked+0x2d/frame
> 0xfe022ed8f6e0
> sbappendstream() at sbappendstream+0x3c/frame 0xfe022ed8f710
> tcp_usr_send() at tcp_usr_send+0x1ab/frame 0xfe022ed8f790
> sosend_generic() at sosend_generic+0x40b/frame 0xfe022ed8f850
> kern_sendit() at kern_sendit+0x19e/frame 0xfe022ed8f900
> sendit() at sendit+0x129/frame 0xfe022ed8f950
> sys_sendto() at sys_sendto+0x4d/frame 0xfe022ed8f9a0
> amd64_syscall() at amd64_syscall+0x211/frame 0xfe022ed8fab0
> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe022ed8fab0
> --- syscall (133, FreeBSD ELF64, sys_sendto), rip = 0x80126c5a, rsp =
> 0x7fffdf1e9df8, rbp = 0x7fffdf1e9e40 ---
>
> Please note that this is the last one, but at least another one, almost
> identical to this one, was scrolled up. I've been unable to recover
> their data, since, as I said the system is hard locked and did not even
> write them to any system log.
>
> Anyone can help? should this one be looked into? How can I try to debut
> it more?
>
> Thanks in advance!
>
> --
> Guido Falsi 
>
Hi Guido,
I have opened a PR for this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195822

For me works if the VM Network Adapter is attached to Bridged Adapter.
Please comment this bug in the PR.

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

Re: Xfce crashes FreeBSD 11-CURRENT

[Ranjan1018 .]

2014-11-25 21:57 GMT+01:00 Ranjan1018 . <21474...@gmail.com>:

> Right-click on desktop - Desktop Settings… - click on the “Create a new
> list, or load an existing one” - Type a non existent file name in the
> windows with the title “Crete/Load Backdrop List” - Open
>
> The laptop freezes and displays only a blank screen with the mouse cursor
> and the text cursor on the top left corner. The only things I can do is to
> press the power button for some seconds to switch off the laptop.
>
> Note: I have some images in a Image list as background.
> I am running vt(4) with KMS on Intel driver.
> $ uname -a
> FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r274845: Sat Nov 22
> 14:59:02 CET 2014 root@ativ:/usr/obj/usr/src/sys/NEWCONS  amd64
>
> This is only a bug in xfce !
I have upgraded the laptop to r275515 and with the above procedure these
two programs crashes with a core dump: xfdesktop and xfdesktop-settings.

More details:
The above procedure put two invalid values in Xconf, preventing  xfdesktop
and xfdesktop-settings to run.
The commands:

xfconf-query -c xfce4-desktop -p /backdrop/screen0/monitor0/last-image-list
-s ~/.config/xfce4/desktop/backdrop.list
xfconf-query -c xfce4-desktop -p /backdrop/screen0/monitor0/image-path -s
~/.config/xfce4/desktop/backdrop.list

restores the correct values.

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

Re: sysctl -zarc for ZFS users

[Ranjan1018 .]

2014-12-06 11:35 GMT+01:00 Yoshihiro Ota :

> Hi all.
>
> I've been watching ZFS activites on my machine and
> improved systat to monitor such.
>
> One of my first goals is to watch ZFS cache statistics.
>
> I posted my patch to the bugzilla @
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195460
> I've been using on 11-CURRENT and 10.1-RELEASE myself.
>
> Regards,
> Hiro
>
> % systat -zarc
>Total MFU MRUAnon Hdr   L2Hdr
>  Other
>  ZFS ARC206M 63M136M826K   1102K  0K
>  5251K
>
> ratehits  misses   total hits total
> misses
>  arcstats  : 75%1183 38823721
>  4202
>  arcstats.demand_data  :  0%   0   0  528
>   0
>  arcstats.demand_metadata  : 76%1007 30821441
>  2757
>  arcstats.prefetch_data:  0%   0   00
>   0
>  arcstats.prefetch_metadata: 68% 176  80 1752
>  1445
>  zfetchstats   : 44% 954120426410
> 25482
>  arcstats.l2   :  0%   0   00
>   0
>  vdev_cache_stats  :  0%   0   00
>   0
>

Hi Hiro,

just applied the patch, but I receive the error:

# make
make: don't know how to make zarc.c. Stop
make: stopped in /usr/src/usr.bin/systat

The file zarc,c is missing. Where can I find it ?

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

Re: Virtualbox 4.3.20 crashes FreeBSD 11.0-CURRENT

[Ranjan1018 .]

Hi Hans,

the bug is network related: in VirtualBox per VM Settings - Network -
Attach to -  changing from "NAT" to "Bridged Adapter" it works. Probably I
will open a new PR for this bug.

I am testing your patch and I will report the result in the above PR (id
194196).

Maurizio


2014-11-29 17:49 GMT+01:00 Hans Petter Selasky :

> On 11/29/14 16:00, Ranjan1018 . wrote:
>
>> *Just upgrade  emulators/virtualbox-ose-4.3.20 via pkg upgrade. Starting
>> a
>>
>> VM, Windows XP or Ubuntu x86, after few seconds the laptop freezes.The
>> system responds only to power off, pressing the power button for few
>> seconds. The only things I can do is a photo of the screen:
>> https://plus.google.com/112995826906094353410/posts/6amoaitgP8e
>> <https://plus.google.com/112995826906094353410/posts/6amoaitgP8e>*
>>
>> *Maurizio*
>>
>
> Hi,
>
> Can you try to apply the patch in the following PR:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194196
>
> Not sure if it helps.
>
> --HPS
>
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Virtualbox 4.3.20 crashes FreeBSD 11.0-CURRENT

[Ranjan1018 .]

*Just upgrade  emulators/virtualbox-ose-4.3.20 via pkg upgrade. Starting a
VM, Windows XP or Ubuntu x86, after few seconds the laptop freezes.The
system responds only to power off, pressing the power button for few
seconds. The only things I can do is a photo of the screen:
https://plus.google.com/112995826906094353410/posts/6amoaitgP8e
*

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

Xfce crashes FreeBSD 11-CURRENT

[Ranjan1018 .]

Right-click on desktop - Desktop Settings… - click on the “Create a new
list, or load an existing one” - Type a non existent file name in the
windows with the title “Crete/Load Backdrop List” - Open

The laptop freezes and displays only a blank screen with the mouse cursor
and the text cursor on the top left corner. The only things I can do is to
press the power button for some seconds to switch off the laptop.

Note: I have some images in a Image list as background.
I am running vt(4) with KMS on Intel driver.
$ uname -a
FreeBSD ativ 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r274845: Sat Nov 22
14:59:02 CET 2014 root@ativ:/usr/obj/usr/src/sys/NEWCONS  amd64

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

[PATCH] gstat on SSD

[Ranjan1018 .]

I am running a pair of servers with SSD. In gstat the default display of
operation/ms is only one digit after the comma and there are a lot of R/W
operation displayed with the 0.1 value. This simple patch displays  the
operation/ms with two decimal digit.

What’s next ? After testing this patch for a day, recording the values in a
log file, I have found that some write operation are only 0.02 ms short, on
a OCZ Vertex SSD. Probably the next patch is to display micro seconds
instead of milli seconds.

Maurizio

FreeBSD 11 gstat.c.patch 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Ver 2 of the patch [was: Re: i915 driver update testing]

[Ranjan1018 .]

2014-10-08 19:05 GMT+02:00 Konstantin Belousov :

> On Tue, Oct 07, 2014 at 04:04:54PM -0400, Adam McDougall wrote:
> > On 10/07/2014 14:01, Konstantin Belousov wrote:
> > > On Tue, Oct 07, 2014 at 07:44:19PM +0300, Konstantin Belousov wrote:
> > >> >From the same frame, please do
> > >> p *(struct drm_i915_private *)(dev->private)
> p *(struct drm_i915_private *)(dev->dev_private)
>
> > >
> > > I probably figured out what is wrong, but it is still interesting to
> > > see this piece of data.
> > >
> > > For everybody who has the issue with blank screen or panic after
> > > the patch:
> > > 1. please try the updated patch,
> > > https://www.kib.kiev.ua/kib/drm/i915.2.patch
> > > 2. if you use "kldload i915kms" to test the patch and get the blank
> > >screen, verify do you get panic or just a black screen.  It is
> > >expected for sc, not so for vt.  For vt, if you do get blank screen
> > >and not a panic, do not load i915kms manually and run the X server.
> > >I am interested if running X server does show proper output.
> > >
> >
> > Backtrace seems the same, I repeated the prior commands:
> > http://www.egr.msu.edu/~mcdouga9/i915-patch2-1.txt
>
> There are more occurences of the bug I fixed once in patch version 2.
> Also, since pmap changes were committed in modified form, please try
> the updated patch at https://www.kib.kiev.ua/kib/drm/i915.3.patch .
>
On my Samsung ATIV Book 2 the result is always the blank screen with
i915.2.patch or i9153.patch.
The result of the command "kldload i915kms" or running the X server is
always the blank screen.
Note: if I listen some music, after the "blank screen", I can hear some
noise from speakers.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Ver 2 of the patch [was: Re: i915 driver update testing]

[Ranjan1018 .]

2014-10-07 21:29 GMT+02:00 Ed Maste :

> On 7 October 2014 15:20, Ranjan1018 . <21474...@gmail.com> wrote:
> >
> > Hmm...  The next patch looks like a unified diff to me...
> > The text leading up to this was:
> > --
> > |diff --git a/sys/amd64/conf/X b/sys/amd64/conf/X
> > |index 0cd80c6..2d630d5 100644
> > |--- a/sys/amd64/conf/X
> > |+++ b/sys/amd64/conf/X
> > --
> > File to patch:
> >
> > I haven't the file X.
>
> You can just hit Enter and then answer 'y' to the "skip this patch"
> question:
>
> File to patch:
> No file found--skip this patch? [n] y
> Skipping patch...
> Hunk #1 ignored at 67.
> 1 out of 1 hunks ignored--saving rejects to Oops.rej
>
> X in the patch is a kernel config file that's not important for the
> change itself.
>

Thanks Ed, it works.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Ver 2 of the patch [was: Re: i915 driver update testing]

[Ranjan1018 .]

2014-10-07 20:01 GMT+02:00 Konstantin Belousov :

> On Tue, Oct 07, 2014 at 07:44:19PM +0300, Konstantin Belousov wrote:
> > >From the same frame, please do
> > p *(struct drm_i915_private *)(dev->private)
>
> I probably figured out what is wrong, but it is still interesting to
> see this piece of data.
>
> For everybody who has the issue with blank screen or panic after
> the patch:
> 1. please try the updated patch,
> https://www.kib.kiev.ua/kib/drm/i915.2.patch
> 2. if you use "kldload i915kms" to test the patch and get the blank
>screen, verify do you get panic or just a black screen.  It is
>expected for sc, not so for vt.  For vt, if you do get blank screen
>and not a panic, do not load i915kms manually and run the X server.
>I am interested if running X server does show proper output.
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>

Hi,

applying the patch I receive this message:
# patch -p1 -C < ~/downloads/i915.2.patch
.
.
.
Patching file sys/amd64/amd64/pmap.c using Plan A...
Hunk #1 succeeded at 1710.
Hunk #2 succeeded at 6226.
Hunk #3 succeeded at 6562.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/sys/amd64/conf/X b/sys/amd64/conf/X
|index 0cd80c6..2d630d5 100644
|--- a/sys/amd64/conf/X
|+++ b/sys/amd64/conf/X
--
File to patch:

I haven't the file X.

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

Re: CURRENT: buildworld fails to compile: cannot find -lctf cc: error: linker command failed [libproc.so.3]

[Ranjan1018 .]

2014-10-05 11:37 GMT+02:00 Arseny Nasokin :

> Waiting for patch in -CURRENT.
>
> -- Eir Nym
>
> This patch work in r272559 for me: http://pastebin.com/2QJRYjCK

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

Re: i915 driver update testing

[Ranjan1018 .]

2014-10-03 19:02 GMT+02:00 Konstantin Belousov :

> Please find at the
> https://kib.kiev.ua/kib/drm/i915.1.patch
> a patch which provides some updates to the i915 driver. At large, this
> is import of the batch of Linux commits, and as such, it is interesting
> mostly as attempt to restart the race to get us more up to date Linux code
> imported. It might provide some bug fixes, most likely for IvyBridge.
> Interesting from the development PoV is the update of the GEM i/o ioctl
> code path to mimic Linux code structure.
>
> I am asking _only_ for reports of regressions with the patch applied,
> comparing with the code which is currently in HEAD. I will not debug
> any existing bugs, my goal right now is to commit this update, which is
> needed for further work. I.e., only when you get an issue with the patch
> applied, but cannot reproduce the problem without the patch, please
> prepare a bug report.
>
> FYI, the driver will attach to haswell gfx, but I am not interested in
> reports about this (see above paragraph). On my test box, which is Core
> i7 4770S, the mode-setting and front-buffer rendering works, but Mesa
> immediately cause renderer to bug out.
>
> Work was sponsored by The FreeBSD Foundation, both by time and hardware,
> and Intel provided access to the documentation.
> ___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org"
>

On a Samsung ATIV Book 2 15.6” Notebook - NP270E5E, specs,
 the patch
does not works.
The result of the command

# kldload i915kms
is a blank screen.

After rebooting the notebook, in /var/log/messages I can read:
Oct  4 08:12:44 ativ kernel: info: [drm] Initialized drm 1.1.0 20060810
Oct  4 08:12:45 ativ kernel: drmn0:  on vgapci0
Oct  4 08:12:45 ativ kernel: info: [drm] MSI enabled 1 message(s)
Oct  4 08:12:45 ativ kernel: info: [drm] AGP at 0xe000 256MB
Oct  4 08:12:45 ativ kernel: iicbus0:  on iicbb0 addr 0xff
Oct  4 08:12:45 ativ kernel: iic0:  on iicbus0
Oct  4 08:12:45 ativ kernel: iic1:  on iicbus1
Oct  4 08:12:45 ativ kernel: iicbus2:  on iicbb1 addr 0x0
Oct  4 08:12:45 ativ kernel: iic2:  on iicbus2
Oct  4 08:12:45 ativ kernel: iic3:  on iicbus3
Oct  4 08:12:45 ativ kernel: iicbus4:  on iicbb2 addr 0x0
Oct  4 08:12:45 ativ kernel: iic4:  on iicbus4
Oct  4 08:12:45 ativ kernel: iic5:  on iicbus5
Oct  4 08:12:45 ativ kernel: iicbus6:  on iicbb3 addr 0x0
Oct  4 08:12:45 ativ kernel: iic6:  on iicbus6
Oct  4 08:12:45 ativ kernel: iic7:  on iicbus7
Oct  4 08:12:45 ativ kernel: iicbus8:  on iicbb4 addr 0x0
Oct  4 08:12:45 ativ kernel: iic8:  on iicbus8
Oct  4 08:12:45 ativ kernel: iic9: 
Oct  4 08:12:45 ativ kernel: on iicbus9
Oct  4 08:12:45 ativ kernel: iicbus10:  on iicbb5 addr 0x0
Oct  4 08:12:45 ativ kernel: iic10:  on iicbus10
Oct  4 08:12:45 ativ kernel: iic11:  on iicbus11
Oct  4 08:12:45 ativ kernel: info: [drm] Supports vblank timestamp caching
Rev 1 (10.10.2010).
Oct  4 08:12:45 ativ kernel: info: [drm] Driver supports precise vblank
timestamp query.

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

Intel i915 GPU hung

[Ranjan1018 .]

Hello,

I have just upgrade my laptop, a Samsung Ativ Book 2 with an integrated
Intel HD Graphics 4000, to:

FreeBSD ativ.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r271400: Wed Sep 10
21:40:48 CEST 2014 root@ativ.local:/usr/obj/usr/src/sys/NEWCONS  amd64

Using Firefox, after some minutes, I receive the error:

error: [drm:pid12:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
elapsed... GPU hung
info: [drm] capturing error event; look for more information in sysctl
hw.dri.0.info.i915_error_state

This error is not related to r271400, but I first saw it few months ago in
current.

The output of the command
sysctl hw.dri.0.info.i915_error_state
is:

https://drive.google.com/file/d/0BzoWQoMqq1sfa0tyVGJVYVBhRnc/edit?usp=sharing

After the error I am not able to run mplayer for videos: the window is
black.

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

Re: Numeric Keypad does not works in 11.0-CURRENT amd64 r266916

[Ranjan1018 .]

2014-06-01 11:00 GMT+02:00 Ranjan1018 . <21474...@gmail.com>:

> I have upgrade to FreeBDS CURRENT amd64, with vt (newcons),  version
> r266916 from r266536 and some keys on the keypad do not work: running the
> xev command I  receive no output for the ‘/’, ‘*’ and ‘-’ keys, but even
> for the ‘+’ key I have some strange output:
>
> r266916:
>
> ButtonPress event, serial 38, synthetic NO, window 0x2a1,
>
> root 0x9d, subw 0x0, time 708649, (79,90), root:(117,172),
>
> state 0x0, button 3, same_screen YES
>
>  ButtonRelease event, serial 38, synthetic NO, window 0x2a1,
>
> root 0x9d, subw 0x0, time 708649, (79,90), root:(117,172),
>
> state 0x400, button 3, same_screen YES
>
>  ButtonPress event, serial 38, synthetic NO, window 0x2a1,
>
> root 0x9d, subw 0x0, time 708649, (79,90), root:(117,172),
>
> state 0x0, button 3, same_screen YES
>
>  ButtonRelease event, serial 38, synthetic NO, window 0x2a1,
>
> root 0x9d, subw 0x0, time 708650, (79,90), root:(117,172),
>
> state 0x400, button 3, same_screen YES
>
>
> r266536, as expected:
>
> KeyPress event, serial 38, synthetic NO, window 0x2c1,
>
> root 0x9d, subw 0x0, time 368450, (114,90), root:(1233,135),
>
> state 0x0, keycode 86 (keysym 0xffab, KP_Add), same_screen YES,
>
> XLookupString gives 1 bytes: (2b) "+"
>
> XmbLookupString gives 1 bytes: (2b) "+"
>
> XFilterEvent returns: False
>
>  KeyRelease event, serial 38, synthetic NO, window 0x2c1,
>
> root 0x9d, subw 0x0, time 368654, (114,90), root:(1233,135),
>
> state 0x0, keycode 86 (keysym 0xffab, KP_Add), same_screen YES,
>
> XLookupString gives 1 bytes: (2b) "+"
>
> XFilterEvent returns: False
>
> Regards
> Maurizio
>

I have upgraded to r267068 and the problem is gone: the keyboard works as
expected.

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

Numeric Keypad does not works in 11.0-CURRENT amd64 r266916

[Ranjan1018 .]

I have upgrade to FreeBDS CURRENT amd64, with vt (newcons),  version
r266916 from r266536 and some keys on the keypad do not work: running the
xev command I  receive no output for the ‘/’, ‘*’ and ‘-’ keys, but even
for the ‘+’ key I have some strange output:

r266916:

ButtonPress event, serial 38, synthetic NO, window 0x2a1,

root 0x9d, subw 0x0, time 708649, (79,90), root:(117,172),

state 0x0, button 3, same_screen YES

ButtonRelease event, serial 38, synthetic NO, window 0x2a1,

root 0x9d, subw 0x0, time 708649, (79,90), root:(117,172),

state 0x400, button 3, same_screen YES

ButtonPress event, serial 38, synthetic NO, window 0x2a1,

root 0x9d, subw 0x0, time 708649, (79,90), root:(117,172),

state 0x0, button 3, same_screen YES

ButtonRelease event, serial 38, synthetic NO, window 0x2a1,

root 0x9d, subw 0x0, time 708650, (79,90), root:(117,172),

state 0x400, button 3, same_screen YES


r266536, as expected:

KeyPress event, serial 38, synthetic NO, window 0x2c1,

root 0x9d, subw 0x0, time 368450, (114,90), root:(1233,135),

state 0x0, keycode 86 (keysym 0xffab, KP_Add), same_screen YES,

XLookupString gives 1 bytes: (2b) "+"

XmbLookupString gives 1 bytes: (2b) "+"

XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x2c1,

root 0x9d, subw 0x0, time 368654, (114,90), root:(1233,135),

state 0x0, keycode 86 (keysym 0xffab, KP_Add), same_screen YES,

XLookupString gives 1 bytes: (2b) "+"

XFilterEvent returns: False

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

In r265803 i915kms.ko must be loaded in /boot/loader.conf

[Ranjan1018 .]

Hi all,

in r265172 I was able to load the i915kms.ko driver in /etc/rc.conf via
kld_list. eg. kld_list='i915kms'.

Today I have update to r265803 in my laptop, but loading the driver with
kld_list result in a blank screen. I need to add the line
i915kms_load="YES"
in /boot/loader.conf

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

Re: dual-booting windows 7 and freebsd 10 from gpt partition SSD

[Ranjan1018 .]

I have installed Windows 8 and FreeBSD on the same Hard Disk, in a Samsung
laptop, as explained in this post :
https://forums.freebsd.org/viewtopic.php?f=12&t=44015

Maurizio


2014-03-21 19:44 GMT+01:00 Allan Jude :

> On 2014-03-21 03:47, M&S - Krasznai András wrote:
> > hi
> >
> > I have been using freebsd and windows 7 on mbr partitioned hdd (using
> easybcd on windows to manipulate boot menu and boot code).
> >
> > recently I bought an new machine with Intel I7 processor,  uefi bios,
> ssd and installed windows 7 64-bit first.
> >
> > after that I installed freebsd 10 (amd64); I used guided partitioning,
> which created a 64-kB freebsd-boot partition, a 48GB / partition and a swap
> about 2.5 GB.
> >
> >
> > Then I tried to set up booting by the same method: install easybcd in
> windows, then set up boot menu with easybcd, add an entry   freebsd as
> BSD/FreeBSD type entry,  but this time I am not able to get it work.
> >
> > Win 7 boots OK, but freebsd does not start, the windows boot manager
> complains about missing or corrupt boot block, which is definitely on the
> given full path.
> >
> > How can I get a working dual booting system in this case? Can anbody
> help me?
> >
> > Regards
> > Krasznai András
> > rendszermérnök
> > M&S Informatikai Zrt.
> > 1136 Budapest, Pannónia u. 17/A.
> > Telefon: +36   1 703-2923
> > Mobil:+36 30 703-2923
> >
> >
> > ___
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscr...@freebsd.org"
> >
>
> If I recall correctly, Windows will only boot a GPT partition if uEFI is
> enabled, and FreeBSD cannot boot uEFI (yet). I have only successfully
> dual booted using 2 different drives and using the BIOS boot selection
> menu, with the BIOS set to uEFI/CSM fallback mode, so that it uses uEFI
> for the Windows disk and CSM for the FreeBSD disk.
>
> Although, I didn't really try that hard, as I had the two drives and it
> worked.
>
> --
> Allan Jude
>
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CURRENT]: claws-mail and firefox fail with "Invalid alignment"

[Ranjan1018 .]

2014-02-22 15:44 GMT+01:00 Rainer Hurling :

> Am 22.02.2014 10:03, schrieb Ranjan1018 .:
> > The problem is still present in r262325. Verified with Firefox.
>
> Just for the record. With r262334 the problem seems to be solved,
> Firefox, Thunderbird etc. work again :-)
>
> Thanks to davidxu@ for the quick fix.
>
> I can confirm, with r262336 the problem is solved, Firefox works again.

Thanks to davidxu@ for the quick fix and thanks to Rainer for reporting it.

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

Re: [CURRENT]: claws-mail and firefox fail with "Invalid alignment"

[Ranjan1018 .]

The problem is still present in r262325. Verified with Firefox.



2014-02-22 9:12 GMT+01:00 Alexandr :

> 21.02.2014 20:03, O. Hartmann пишет:
> > On Fri, 21 Feb 2014 19:00:13 +0100
> > "O. Hartmann"  wrote:
> >
> >> On Fri, 21 Feb 2014 18:49:13 +0100
> >> Dimitry Andric  wrote:
> >>
> >>> On 21 Feb 2014, at 18:40, O. Hartmann 
> >>> wrote:
>  On every FreeBSD 11.0-CURRENT #0 r262294: Fri Feb 21 14:11:20 CET
>  2014 amd64 I run neither claws-mail nor firfox run after the last
>  buildworld. They fail both with the error
> 
>  Invalid alignment
> 
>  Does anyone see this problem too? I tried to recompile claws-mail
>  and firefox, but without success (compilation succeeded, but the
>  error stays).
> 
>  What happened here? How to solve?
> >>> Can you try reverting r262277, rebuilding libexec/rtld-elf and
> >>> reinstalling it, and seeing if that fixes it?
> >>>
> >>> -Dimitry
> >>>
> >> Hello Dimitry,
> >>
> >> in r262277 there is no change in libexec/rtld-elf, I had to go back to
> >> r262270. I did as requested and reinstalling libexec/rtld-elf fixes
> >> the reported issue.
> >>
> >> Regards,
> >> Oliver
> > Sorry, it is r262276
> >
>
> I have the same issue with firefox and thunderbird. Reverting
> libexec/rtld-elf to r262276 solves a problem.
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [PATCH] PCI bus number management

[Ranjan1018 .]

Works fine setting all 3 on a Samsung ATIV BOOK 2 model NP270E5E-K02IT on
FreeBSD 11.0-CURRENT amd64 r261561 with NEWCONS.

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

SDHC Sony SF-8UX, advertised as 94MB/s max read speed, don’t works.

[Ranjan1018 .]

I’m trying to use this SDHC as a ZFS cache on a Samsung laptop:

da0 at umass-sim0 bus 0 scbus3 target 0 lun 0

da0:  Removable Direct Access SCSI-0 device

da0: Serial Number 058F63666438

da0: 40.000MB/s transfers

da0: 7667MB (15702016 512 byte sectors: 255H 63S/T 977C)

da0: quirks=0x2

After some minutes of usage this error is displayed :

(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 0a 97 9f 00 00 05 00

(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error

(da0:umass-sim0:0:0:0): SCSI status: Check Condition

(da0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to
ready change, medium may have changed)

(da0:umass-sim0:0:0:0): Command Specific Info: 0xaa5501

(da0:umass-sim0:0:0:0): Retrying command (per sense data)

(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 0a 97 9f 00 00 05 00

(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error

(da0:umass-sim0:0:0:0): SCSI status: Check Condition

(da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)

(da0:umass-sim0:0:0:0): Command Specific Info: 0xaa5501

(da0:umass-sim0:0:0:0): Error 6, Unretryable error

(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 01 00 00 01 00

(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error

(da0:umass-sim0:0:0:0): SCSI status: Check Condition

(da0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to
ready change, medium may have changed)

(da0:umass-sim0:0:0:0): Command Specific Info: 0xaa5501

(da0:umass-sim0:0:0:0): Retrying command (per sense data)

(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 01 00 00 01 00

(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error

(da0:umass-sim0:0:0:0): SCSI status: Check Condition

(da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)

(da0:umass-sim0:0:0:0): Command Specific Info: 0xaa5501

(da0:umass-sim0:0:0:0): Error 6, Unretryable error

GEOM: da0: corrupt or invalid GPT detected.

GEOM: da0: GPT rejected -- may not be recoverable.

Trying to use the SDHC as a MS-DOS device I have receive the error:

(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 4a 00 00 00 00 80 00

(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error

(da0:umass-sim0:0:0:0): SCSI status: Check Condition

(da0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to
ready change, medium may have changed)

(da0:umass-sim0:0:0:0): Command Specific Info: 0xaa5501

(da0:umass-sim0:0:0:0): Retrying command (per sense data)

(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 4a 00 00 00 00 80 00

(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error

(da0:umass-sim0:0:0:0): SCSI status: Check Condition

(da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)

(da0:umass-sim0:0:0:0): Command Specific Info: 0xaa5501

(da0:umass-sim0:0:0:0): Error 6, Unretryable error

I’m using:

[root@ativ ~/bin]# uname -a

FreeBSD ativ.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r260700: Thu Jan 16
07:03:04 CET 2014 root@ativ.local:/usr/obj/usr/src/sys/NEWCONS  amd64

I’ve tested the card in Mac OS X on a Mac mini and in Windows 8 on the same
laptop, without problems. I’ve only noted that the I/O speed is  much lower
on the Mac mini.

Mac Write:

mac-mini:~ maurizio$ sudo dd if=/dev/zero  of=/dev/disk1 bs=1048576
count=200

209715200 bytes transferred in 138.019361 secs (1519462 bytes/sec)

Mac Read:

mac-mini:~ maurizio$ sudo dd of=/dev/null  if=/dev/disk1 bs=1048576
count=200

209715200 bytes transferred in 23.719487 secs (8841473 bytes/sec)

FreeBSD Write:

[root@ativ ~]# dd if=/dev/zero  of=/dev/da0 bs=1048576 count=200

209715200 bytes transferred in 13.647264 secs (15366831 bytes/sec)

FreeBSD Read:

[root@ativ ~]# dd of=/dev/null  if=/dev/da0 bs=1048576 count=200

209715200 bytes transferred in 11.050251 secs (18978320 bytes/sec)

Windows Write:

with DH_Speed 1 min. test 16M/sec

Windows Read:

with DH_Speed 1 min. test 17.4M/sec

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