Re: panic: Unaligned free (was: kernel panic while copying files)

On 0701T1330, Gary Jennejohn wrote: > Gary Jennejohn wrote: > > I noticed that the value of vm.debug.divisor affects what value is > > returned in uma_core.c:uma_dbg_kskip(), so I decided to try a few > > different values. > > > > The returned value is used to set skipdbg in uma_core.c:item_dtor(

Re: kernel panic while copying files

On 0610T1150, Gary Jennejohn wrote: > On Tue, 8 Jun 2021 17:54:05 +0200 > Gary Jennejohn wrote: > > [big snip] [..] > So, I did ``git reset --hard 8dc96b74edb844bb621afeba38fe4af104b13120'', > which was the penultimate commit made by trasz to clear CCBs on the stack > after he committed 3394d42

Re: rc.d/zpool runs before ada(4) attaches

On 1201T0834, Ian Lepore wrote: > On Tue, 2020-12-01 at 16:22 +0100, Ronald Klop wrote: [..] > > You can define these in /boot/loader.conf: > > #kern.cam.boot_delay="1" # Delay (in ms) of root mount for CAM > > bus > > #kern.cam.scsi_delay="2000" # Delay (in ms) before probing SCSI > > > > M

Re: rc.d/linux runs unconditionally

On 1003T0947, Michael Butler wrote: > In rc.d/sysvipc we see .. > > name="sysvipc" > desc="Load SysV IPC modules" > rcvar="sysvipc_enable" > start_cmd="${name}_start" > > .. so it won't try to run without explicitly setting sysvipc_enable in > /etc/rc.conf. > > However in rc.d/linux, we have on

FreeBSD Quarterly Status Report - Second Quarter 2019

FreeBSD Project Quarterly Status Report - 2nd Quarter 2019 This quarter our report includes some interesting topics easily accessible to anyone, even if you are not a programmer: we report the link to a presentation of the 2019 FreeBSD survey results at BSDCan 2019 and describe an inte

Call for 2019Q2 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July 31, 2019, for work done since the last round of Quarterly Reports: April, 2019 – June, 2019. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD projec

FreeBSD Quarterly Status Report - First Quarter 2019

FreeBSD Project Quarterly Status Report - 1st Quarter 2019 As spring leads into summer, we reflect back on what the FreeBSD project has accomplished in the first quarter of 2019. Events included FOSDEM and AsiaBSDCon, the FreeBSD Journal is now free to everyone, ASLR is available in -C

Call for 2019Q1 quarterly status reports

Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 30, 2019, for work done since the last round of Quarterly Reports: January, 2019 – March, 2019. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD pr

FreeBSD Quarterly Status Report - Fourth Quarter 2018

FreeBSD Project Quarterly Status Report - 4th Quarter 2018 Since we are still on this island among many in this vast ocean of the Internet, we write this message in a bottle to inform you of the work we have finished and what lies ahead of us. These deeds that we have wrought with our

FreeBSD Quarterly Status Report - Third Quarter 2018

FreeBSD Project Quarterly Status Report - 3rd Quarter 2018 With FreeBSD having gone all the way to 12, it is perhaps useful to take a look back at all the things that have been accomplished, in terms of many visible changes, as well as all the things that happen behind the scenes to e

Re: suspend/resume regression

On 0514T1158, Andriy Gapon wrote: > On 14/05/2018 11:44, Mikaël Urankar wrote: > > Could it be the same problem described here? > > https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html > > That problem is _not_ a regression. FWIW, this machine (the one affected by the sluggish

Re: suspend/resume regression

On 0513T1244, Pete Wright wrote: > > > On 05/13/2018 10:27, Pete Wright wrote: > > > > > > On 05/13/2018 08:58, Theron wrote: > >>> Hi! > >>> I'm also seeing issues, not as severe as Pete, but after I resume > >>> (which works, with drm-next and DMC firmware), the system becomes > >>> sluggish.

Re: devdmatch: Can't read linker file.

FWIW, it seems to be a common problem, see https://reviews.freebsd.org/D14534. On 0312T1027, Warner Losh wrote: > Well, is there a /boot/kernel/linker.hints? > > Warner > > On Mon, Mar 12, 2018 at 9:56 AM, Daniel Braniss wrote: > > > Hi, > > the above i get on arm/nanopi-neo. (it’s the only pl

Re: getfsstat / nullsfs / automount bug?

> On 20 Nov 2017, at 17:39, Jamie Landeg-Jones wrote: > > There appears to be a bug in the system call related to getmntinfo(3) / > getfsstat(2) > , when if the "automount" flag is set on "nullfs" mounts, it is not returned > on > a getfsstat "WAIT" call. The non-refreshed, non-blocking "MNT_N

Re: [autofs] problems with "dirty" UFS2 partitions

On 0808T0717, O. Hartmann wrote: > Hello, > > we're running a NanoBSD based appliance which resides on a small SoC and > utilises a mSATA SSD for logging, database storage and mail folder. The > operating system is recent CURRENT as it is still under development. > > The problem ist, that from ti

Re: Time to increase MAXPHYS?

On 0605T1849, Edward Tomasz Napierała wrote: > On 0604T0952, Hans Petter Selasky wrote: > > On 06/04/17 09:39, Tomoaki AOKI wrote: > > > Hi > > > > > > One possibility would be to make it MD build-time OTIONS, > > > defaulting 1M on regular systems

Re: Time to increase MAXPHYS?

ion and I > reverted it back ASAP > > On 5 Jun 2017, at 19:49, Edward Tomasz Napierała wrote: > > > > On 0604T0952, Hans Petter Selasky wrote: > >> On 06/04/17 09:39, Tomoaki AOKI wrote: > >>> Hi > >>> > >>> One possibility would

Re: Time to increase MAXPHYS?

On 0604T0952, Hans Petter Selasky wrote: > On 06/04/17 09:39, Tomoaki AOKI wrote: > > Hi > > > > One possibility would be to make it MD build-time OTIONS, > > defaulting 1M on regular systems and 128k on smaller systems. > > > > Of course I guess making it a tunable (or sysctl) would be best, > >

Re: regression suspend/resume on Lenovo T420

On 0515T2140, Konstantin Belousov wrote: > On Mon, May 15, 2017 at 06:37:58PM +0100, Edward Tomasz Napiera??a wrote: > > Thanks! The patch fixes resume for me, for both vt(4) and X11. > > Thanks everybody for testing, patch below should be committable, modulo > bugs. I did not tested it and ask

Re: regression suspend/resume on Lenovo T420

On 0506T1103, Manuel Stühn wrote: > On Sat, May 06, 2017 at 10:52:56AM +0200, Manuel Stühn wrote: > >On Wed, 03 May 2017 22:28:41 +0200, Freebsdnewbie wrote > >> > >>> Von: Adrian Chadd > >>> Gesendet: Mo. 01.05.2017 23:31 > >>> An: Manuel Stühn , > >>> Kopie: freebsd-current , > >>> Betreff: Re: r

Re: CURRENT [r308668] autofs kernel panic

For the record, this was fixed in r311284. On 1115T2021, Alex Deiter wrote: > Hello Edward, > > Thank you for the quick reply! > I was able to reproduce this panic on default GENERIC kernel (my test > system and laptop): > > # kgdb /boot/kernel/kernel /var/crash/vmcore.2 > GNU gdb 6.1.1 [FreeBSD

Re: ACPI Error on HP ProBook 430 G2

On 1220T1734, O. Hartmann wrote: > Am Tue, 20 Dec 2016 18:09:20 +0300 > Vladimir Zakharov schrieb: > > > Hello! > > > > Some time ago new ACPI messages appeared on console and in > > /var/log/messages. Like > > these: > > > > ACPI Error: Needed type [Reference], found [Processor] 0xf800043

Re: CURRENT [r308668] autofs kernel panic

On 1115T1016, Alex Deiter wrote: > Hello, > > FreeBSD 12.0-CURRENT-r308668 amd64 crashed on "pkg install” command: > > # cat /usr/local/etc/pkg/repos/local.conf > local: { > url: "file:///net/nostromo/var/devel/pkg", > enabled: yes > } > > Path /net/nostromo/var/devel/pkg accessible via autofs/a

Re: Weirdness in TTY & VT

On 0902T1712, Lundberg, Johannes wrote: > ​Hi > > I'm porting some Linux code and have some weird behavior. > > In this (Linux) code fstat() and minor() is used on a /dev/tty file > descriptor to get a tty number to map to. In FreeBSD this returns a number > around 60-70 for st_rdev which means V

Re: refcnt 0 on LLE at boot....

FWIW, I'm seeing this too. I've filed a PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884 On 0707T0813, Larry Rosenman wrote: > and now it's been up for 13+ hours. I do have both VMCORE's from the 2 > crashes. > > > > On 2016-07-06 18:22, Larry Rosenman wrote: > > Got a similar c

Re: latest memstick image fails to mountroot by default on Thinkpad e565

Dnia 04.06.2016 o godz. 07:52 Matthew Macy napisał(a): > > In order to boot USB reliably on recent laptop hardware (both my thinkpad > and XPS13 need this) you need to add the following to the installer images > loader.conf: > > kern.cam.boot_delay="1" > kern.cam.scsi_delay="3000" What

Re: Resizing a zpool as a VMware ESXi guest ...

On 0510T1522, Matthew Grooms wrote: > On 11/28/2015 10:03 PM, Matthew Grooms wrote: > > On 11/28/2015 6:10 PM, Matthew Grooms wrote: > >> On 11/27/2015 7:44 PM, Matthew Grooms wrote: > >>> I spent the day looking over the FreeBSD cam and scsi_da source code. > >>> After sprinkling a bunch of printf

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

On 0508T0944, Graham Menhennitt wrote: > On 5/05/2016 09:41 PM, Edward Tomasz Napierała wrote: > > On 0505T1847, Graham Menhennitt wrote: > >> On 3/05/2016 07:59 PM, Edward Tomasz Napierała wrote: > >>> On 0503T1922, Graham Menhennitt wrote: > >>>> O

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

On 0505T1847, Graham Menhennitt wrote: > On 3/05/2016 07:59 PM, Edward Tomasz Napierała wrote: > > On 0503T1922, Graham Menhennitt wrote: > >> On 3/05/2016 06:42 PM, Edward Tomasz Napierała wrote: > >>> On 0502T0643, Graham Menhennitt wrote: > >>>> On

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

On 0503T1922, Graham Menhennitt wrote: > On 3/05/2016 06:42 PM, Edward Tomasz Napierała wrote: > > On 0502T0643, Graham Menhennitt wrote: > >> On 30/04/2016 06:53 PM, Graham Menhennitt wrote: > >>> Hi all, > >>> > >>> I have a USB disk that I u

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

On 0502T0643, Graham Menhennitt wrote: > On 30/04/2016 06:53 PM, Graham Menhennitt wrote: > > Hi all, > > > > I have a USB disk that I use for backup. Up till now, it's mounted > > without any problems at boot time. After updating to -current as of > > yesterday, it doesn't mount and causes the boo

Re: [CFT] packaging the base system with pkg(8)

On 0422T0908, David Chisnall wrote: > On 21 Apr 2016, at 21:48, Dan Partelly wrote: > > > > Yes, you are right it misses the media change handler in devd.conf. > > maybe it should bementioned somewhere in a man page if it is not > > already there. Thanks for the pointer. > > > > Anyway, if I w

Re: [CFT] packaging the base system with pkg(8)

s > where this can be handy. And too many directories left there do become > annoying. Well, you have devd notifications for this - and it gives you much more flexibility. > > On 21 Apr 2016, at 23:20, Edward Tomasz Napierała wrote: > > > > On 0421T1526, Dan Partelly w

Re: [CFT] packaging the base system with pkg(8)

On 0421T1526, Dan Partelly wrote: > The scenario is: > > Let’s say I have autofs_enable , working with media map. > > If I have a CD in CD drive , all is well and when the system is fully booted > up > /media contains a directory through which I can access the content of the > CD-ROM. Now if yo

Re: [CFT] packaging the base system with pkg(8)

On 0420T1545, dan_partelly wrote: [..] > Another example is the autofs mounter. The prject was marked as complete > by FreeBSD foundation in 2014. Last I tried it to autmount removable > devices, it left directory after directory in the autofs managed directory. > This is known behavior. Yup. T

Re: [CFT] packaging the base system with pkg(8)

[replying to random post] I have a weird feeling that the main problem with having a lot of packages is that people have bad experiences from other systems. But IMHO the root cause of those problems was not that you had a lot of packages - the root cause was that it was used by distro guys to stri

Re: r298143: something wrong with autofs?

On 0417T1057, O. Hartmann wrote: > > Running FreeBSD 11.0-CURRENT #32 r298143: Sun Apr 17 09:48:26 CEST 2016 > amd64, on both > server and client, reveals today that AUTOFS seems not to work. Did something > changed > unnoticed? > > I realized, that no exported filesystem is bound so far. On t

Re: USB disks attach after rootfs prompt

Dnia 20.03.2016 o godz. 09:13 Poul-Henning Kamp napisał(a): > > In message <20160319215624.ga1...@brick.home>, Edward Tomasz > =?utf-8?Q?Napiera= > C5=82a?= writes: > >>> I am somewhat certain that this used to work... >> >> That might be my fault. > > I built this kernel overnight:

Re: USB disks attach after rootfs prompt

On 0319T1509, Poul-Henning Kamp wrote: > > In message <1458397972.68920.69.ca...@freebsd.org>, Ian Lepore writes: > >On Sat, 2016-03-19 at 13:04 +, Poul-Henning Kamp wrote: > >> Running: > >> > >>FreeBSD 11.0-CURRENT #32 r296137: Sat Feb 27 11:34:01 UTC 2016 > >> > >> I tried "bo

Re: mount_smbfs(8): support for SMBv3.02?

On 0303T1047, O. Hartmann wrote: > Does FreeBSD's mount_smbfs(8) support for Microsoft's SMBv3 protocol > introduced > with Windows 8 and Windows Server 2012/R2? No, it only supports the obsolete SMB1 (aka CIFS) protocol. Since SMB2 is a completely different protocol, supporting it properly pret

Re: Add isboot iSCSI boot driver to FreeBSD

On 0924T0049, Slawa Olhovchenkov wrote: > On Wed, Sep 23, 2015 at 11:25:20PM +0200, Edward Tomasz Napierala wrote: > > > On 0923T0916, John Nielsen wrote: > > > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > > > > > > > isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you

Re: Add isboot iSCSI boot driver to FreeBSD

On 0923T0916, John Nielsen wrote: > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > > > isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to > > boot your root partition using iSCSI. > [,,,] > > This was first announced way back in June, 2010: > > > > https://lists.freeb

Re: racct crash/Linux Emulation

On 0828T1207, Larry Rosenman wrote: > On 2015-08-24 11:07, Edward Tomasz Napierała wrote: > > On 0824T0731, Larry Rosenman wrote: > >> On 2015-08-24 03:37, Edward Tomasz Napierała wrote: > >> > On 0823T2028, Larry Rosenman wrote: > >> >> got the

Re: racct crash/Linux Emulation

On 0824T0731, Larry Rosenman wrote: > On 2015-08-24 03:37, Edward Tomasz Napierała wrote: > > On 0823T2028, Larry Rosenman wrote: > >> got the below panio, on a linux (world community grid) process exit. > >> > >> > >> borg.lerctr.org dumped core -

Re: racct crash/Linux Emulation

On 0823T2028, Larry Rosenman wrote: > got the below panio, on a linux (world community grid) process exit. > > > borg.lerctr.org dumped core - see /var/crash/vmcore.5 > > Sun Aug 23 20:14:24 CDT 2015 > > FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #46 r287028: Sat > Aug 22 18:34:

Re: eventfd lookalike in FreeBSD ?

On 0728T1419, Luigi Rizzo wrote: > Hi, > for some work we are doing on bhyve, we need some lightweight mechanism that > a kernel thread can use to wake up another user thread possibly > waiting for some event. https://reviews.freebsd.org/D2172 ___ freeb

Re: panic when RACCT_RSS still > 0 when struct racct destroyed

On 0614T2200, Konstantin Belousov wrote: > On Sun, Jun 14, 2015 at 02:53:48PM +0200, Jeremie Le Hen wrote: > > Sorry for the early sending in the previous email. > > > > Hi all, > > > > I keep getting the following panic from time to time: > > % panic: destroying non-empty racct: 1142784 allocate

Re: Enabling RACCT/RCTL in GENERIC.

On 0429T1303, Edward Tomasz Napierała wrote: > Hi. With the patch I've just committed, the cost of compiling with RACCT > and RCTL is just a subroutine call and an unlocked variable check, in a few > places. I'd like to add "options RACCT", "options RCTL&qu

Re: Enabling RACCT/RCTL in GENERIC.

On 0429T0441, timp wrote: > Hi! > Does it mean I will manage to use rctl to set limits without recompiling > GENERIC? If so, then it's extremely nice news! Yes. You will still need to enable it using a tunable, though, as explained by rctl(8) error message: rctl: RACCT/RCTL present, but disabled

Enabling RACCT/RCTL in GENERIC.

Hi. With the patch I've just committed, the cost of compiling with RACCT and RCTL is just a subroutine call and an unlocked variable check, in a few places. I'd like to add "options RACCT", "options RCTL", and "options RACCT_DISABLED", to GENERIC on amd64, and MFC it before 10.2. What do you thi

Re: AUTOFS and NFS not playing together nicely

On 0419T1700, David Boyd wrote: > At the risk of being dubbed insane, here goes: > > On five FreeBSD 10.1-RELEASE-p9 production servers autofs(5) is enabled > and working as advertised. On the same servers nfs v3 clients are also > fat, dumb and happy. > > On a test server where autofs(5) is als

Re: Suspend/resume with i915.

On 0123T1040, Konstantin Belousov wrote: > On Thu, Jan 22, 2015 at 12:02:01PM +0100, Edward Tomasz Napiera??a wrote: > > I'm trying to fix resume on my T61, broken by some change several > > months ago; according to pciconf it's 'Mobile GM965/GL960 Integrated > > Graphics Controller (primary)'. It

Suspend/resume with i915.

I'm trying to fix resume on my T61, broken by some change several months ago; according to pciconf it's 'Mobile GM965/GL960 Integrated Graphics Controller (primary)'. It's running current CURRENT and up to date packages. Suspend and resume makes Xorg do something weird - there is screen corruptio

Re: ZFS: i/o error - all block copies unavailable #2

On 1022T1633, Kazik Chujwielki wrote: > … > > So, I tried with upgrading to 9.3, installing bootcode from 9.3, then I > booted 10.0, installed boot code again.. nothing helps. > > Still ends on > http://s.verknowsys.com/1a4f147cbb215da9b16eb61a7e9de9ed26470338.png >

Re: Resizing a zpool as a VMware ESXi guest ...

On 1010T1529, Matthew Grooms wrote: > All, > > I am a long time user and advocate of FreeBSD and manage a several > deployments of FreeBSD in a few data centers. Now that these > environments are almost always virtual, it would make sense that FreeBSD > support for basic features such as dynami

Re: [CFT] Autofs.

On 0904T1624, Hans Ottevanger wrote: > On 09/04/14 14:43, Edward Tomasz Napierała wrote: > >On 0904T0759, Hans Ottevanger wrote: > >>On 08/17/14 16:50, Edward Tomasz Napierała wrote: > >>>On 0817T1244, Hans Ottevanger wrote: > >>>> > >>[

Re: [CFT] Autofs.

On 0904T0759, Hans Ottevanger wrote: > On 08/17/14 16:50, Edward Tomasz Napierała wrote: > >On 0817T1244, Hans Ottevanger wrote: > >> > [...] > >>Hi! > >> > >>Great to see a real autofs finally coming to FreeBSD. > >> > >>I a

Re: [CFT] Autofs.

On 0817T1522, O. Hartmann wrote: > Am Sun, 17 Aug 2014 12:44:30 +0200 > Hans Ottevanger schrieb: > > > On 07/30/14 09:19, Edward Tomasz Napierała wrote: > > > At the link below you will find a patch that adds the new automounter. > > > The patch i

Re: [CFT] Autofs.

On 0817T1244, Hans Ottevanger wrote: > On 07/30/14 09:19, Edward Tomasz Napierała wrote: > >At the link below you will find a patch that adds the new automounter. > >The patch is against yesterdays 11.0-CURRENT. > > > >http://people.freebsd.org/~trasz/autofs-head-20140

Re: [CFT] Autofs.

On 0804T1451, Rick Macklem wrote: > Bjoern A. Zeeb wrote: > > On 30 Jul 2014, at 07:19 , Edward Tomasz Napierała > > wrote: > > > > > At the link below you will find a patch that adds the new > > > automounter. > > > The patch is ag

Re: [CFT] Autofs.

On 0804T1635, Bjoern A. Zeeb wrote: > > On 04 Aug 2014, at 16:17 , Edward Tomasz Napierała wrote: > > > On 0804T1252, Bjoern A. Zeeb wrote: > >> On 30 Jul 2014, at 07:19 , Edward Tomasz Napierała > >> wrote: > >> > >>> At the link bel

Re: [CFT] Autofs.

On 0804T1252, Bjoern A. Zeeb wrote: > On 30 Jul 2014, at 07:19 , Edward Tomasz Napierała wrote: > > > At the link below you will find a patch that adds the new automounter. > > The patch is against yesterdays 11.0-CURRENT. > > > > http://people.freebsd.org/~t

Re: [CFT] Autofs.

On 0730T1851, Craig Rodrigues wrote: > On Wed, Jul 30, 2014 at 12:19 AM, Edward Tomasz Napierała > wrote: > > > At the link below you will find a patch that adds the new automounter. > > The patch is against yesterdays 11.0-CURRENT. > > > > http://people.freebs

Re: [CFT] Autofs.

On 0730T1153, Kevin Oberman wrote: > On Wed, Jul 30, 2014 at 12:19 AM, Edward Tomasz Napierała > wrote: > > > At the link below you will find a patch that adds the new automounter. > > The patch is against yesterdays 11.0-CURRENT. > > > > http://people.freebs

[CFT] Autofs.

At the link below you will find a patch that adds the new automounter. The patch is against yesterdays 11.0-CURRENT. http://people.freebsd.org/~trasz/autofs-head-20140729.diff Slides that explain the project scope and deliverables are here: http://people.freebsd.org/~trasz/autofs.pdf Testing is

Re: FreeBSD Quarterly Status Report - Second Quarter 2014

On 0725T1946, Cy Schubert wrote: > In message <20140725211249.ga3...@brick.home>, Edward Tomasz > =?utf-8?Q?Napiera= > C5=82a?= writes: > > On 0725T1019, Cy Schubert wrote: > > > In message <20140724183353.gl1...@hub.freebsd.org>, Glen Barber writes: > > > > New Automounter > > > > > > > >Con

Re: FreeBSD Quarterly Status Report - Second Quarter 2014

On 0725T1019, Cy Schubert wrote: > In message <20140724183353.gl1...@hub.freebsd.org>, Glen Barber writes: > > New Automounter > > > >Contact: Edward Tomasz Napieral/a > > > >Deficiencies in the current automounter, amd(8), are a recurring > >problem reported by many FreeBSD users. A

Re: FreeBSD iscsi target

On 0703T1615, Craig Rodrigues wrote: > On Tue, Jul 1, 2014 at 2:12 AM, Edward Tomasz Napierała > wrote: > > > In 10-STABLE there is a way to control access based on initiator > > name and IP address. > > > > Edward, > > Out of curiousity, what kind

Re: FreeBSD iscsi target

Hi. I've replied in private, but just for the record: On 0627T0927, Sreenivasa Honnur wrote: > Does freebsd iscsi target supports: > 1. ACL (access control lists) In 10-STABLE there is a way to control access based on initiator name and IP address. > 2. iSNS No; it's one of the iSCSI features

Re: [patch] USB after second suspend/resume on ThinkPads.

On 0618T1515, John Baldwin wrote: > On Wednesday, June 18, 2014 2:46:09 pm Edward Tomasz Napierała wrote: > > On 0618T1303, John Baldwin wrote: > > > On Wednesday, June 18, 2014 12:13:15 pm Edward Tomasz Napierała wrote: > > > > On 0618T0947, John Baldwin wrote: >

Re: [patch] USB after second suspend/resume on ThinkPads.

On 0619T0935, Alexandr Krivulya wrote: > 18.06.2014 12:29, Edward Tomasz Napierała пишет: > > On 0618T1108, Alexandr Krivulya wrote: > >> 16.06.2014 22:21, Edward Tomasz Napierała пишет: > >>> Hi. Patch below should fix a problem where USB stops working after > &

Re: [patch] USB after second suspend/resume on ThinkPads.

On 0618T1303, John Baldwin wrote: > On Wednesday, June 18, 2014 12:13:15 pm Edward Tomasz Napierała wrote: > > On 0618T0947, John Baldwin wrote: > > > On Monday, June 16, 2014 3:21:55 pm Edward Tomasz Napierała wrote: > > > > Hi. Patch below should fix a problem

Re: [patch] USB after second suspend/resume on ThinkPads.

On 0618T0947, John Baldwin wrote: > On Monday, June 16, 2014 3:21:55 pm Edward Tomasz Napierała wrote: > > Hi. Patch below should fix a problem where USB stops working after > > _second_ suspend/resume, which happens on various ThinkPad models. > > Please test, and report bot

Re: [patch] USB after second suspend/resume on ThinkPads.

On 0616T1241, Adrian Chadd wrote: > Hey cool! > > I'll go test this out soon. > > Would you mind throwing it in a bugzilla ticket? It's 191155. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To u

Re: [patch] USB after second suspend/resume on ThinkPads.

On 0618T1108, Alexandr Krivulya wrote: > 16.06.2014 22:21, Edward Tomasz Napierała пишет: > > Hi. Patch below should fix a problem where USB stops working after > > _second_ suspend/resume, which happens on various ThinkPad models. > > Please test, and report both success

[patch] USB after second suspend/resume on ThinkPads.

Hi. Patch below should fix a problem where USB stops working after _second_ suspend/resume, which happens on various ThinkPad models. Please test, and report both success stories and failures. If nothing comes up, I'll commit it in a week or so. (Btw, has anyone encountered the problem on hardwa

Re: iwn driver issue

On 0613T1251, David Wolfskill wrote: > On Fri, Jun 13, 2014 at 09:36:35PM +0200, Edward Tomasz Napiera??a wrote: > > ... > > > I normally don't spend a huge amount of time in head -- enough to build > > > it & do a quick smoke-test. So it's certainly possible that it merits > > > further explorati

Re: iwn driver issue

On 0613T1941, Stefan Parvu wrote: > On Fri, 13 Jun 2014 18:36:44 +0200 > Edward Tomasz Napierała wrote: > > > Can you update to at least r266546 and try again? > > to do this I need to svn update all my /usr/src code and rebuild the kernel - > no iso images > avail

Re: iwn driver issue

I have mixed feelings about this. Sure, a panic is a problem, but without it the problem will remain unfixed - I'm unable to reproduce it, even though I'm using the driver all the time. And it's pretty much useless without that patch. The fix will probably be trivial; I just need a proper backtr

Re: iwn driver issue

On 0613T1126, Stefan Parvu wrote: > Hi, > > Im running FreeBSD current: > FreeBSD nereid 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r265628: Thu May 8 > 08:05:37 UTC 2014 > r...@grind.freebsd.org:/usr/obj/usr/src/sys/VT amd64 > > on Asus Zenbook UX32VD. My wireless network works ok, however fro

Re: "CPU0: local APIC error 0x40"

On 0604T1036, John Baldwin wrote: > On Monday, June 02, 2014 5:32:13 pm Edward Tomasz Napierała wrote: > > Some machines, including ThinkPad T61, emit the following error message > > early during boot: > > > > CPU0: local APIC error 0x40 > > > > The mess

"CPU0: local APIC error 0x40"

Some machines, including ThinkPad T61, emit the following error message early during boot: CPU0: local APIC error 0x40 The message itself doesn't seem to be much of a problem. However, every once in a while booting hangs just before that line. I've tracked that down to call to AcpiHwWritePort()

Re: laptop power cycles due to iwn since r266546

Wiadomość napisana przez Hannes Mehnert w dniu 28 maj 2014, o godz. 23:27: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA384 > > Hi, > > I get random reboots with revision r266546 (Make iwn(4) able to get > itself back into working condition after "fatal firmware error" > happens. Previously i

Re: mtree acl support

Wiadomość napisana przez Mark Felder w dniu 16 sty 2014, o godz. 21:36: > On Wed, Jan 15, 2014, at 23:11, Tim Kientzle wrote: >> >> On Jan 14, 2014, at 6:47 AM, Mark Felder wrote: >> >>> I was recently talking to someone about how one would backup / restore >>> ACLs reliably. I didn't see any me

Re: mtree acl support

Wiadomość napisana przez Tim Kientzle w dniu 16 sty 2014, o godz. 06:11: > On Jan 14, 2014, at 6:47 AM, Mark Felder wrote: > >> I was recently talking to someone about how one would backup / restore >> ACLs reliably. I didn't see any mention of ACLs in the mtree man page >> and after a quick goog

Re: gcc kernel build fail @ SVN r256730

Wiadomość napisana przez Michael Butler w dniu 18 paź 2013, o godz. 14:15: > -current kernel compiled with gcc fails with: > > cc1: warnings being treated as errors > /usr/src/sys/geom/label/g_label.c: In function 'g_label_resize': > /usr/src/sys/geom/label/g_label.c:135: warning: null format st

Re: [SOLVED] Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2

Wiadomość napisana przez Outback Dingo w dniu 17 paź 2013, o godz. 03:11: [..] > Ive actually noticed what i feel is an anomaly with ctladm... i can literally > run ctladm create -b block -o file=/luns/LUN0 numerous times.. and create > a new LUN > every time, using the same file. > > ctl

Re: New iSCSI stack.

Wiadomość napisana przez Outback Dingo w dniu 11 paź 2013, o godz. 14:37: > Quick question, is there a specific reason why ctld doesnt create the file / > device for iscsi, or fc ? > the previous iscsi would read the config file and create the file / device > ... it now appears to be a > manual

Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2

Dnia 11 paź 2013 o godz. 13:15 "Mike C." napisał(a): > >> On 10/11/13 09:24, Edward Tomasz Napierała wrote: >>> Wiadomość napisana przez Mike C. w dniu 10 paź 2013, o godz. 23:41: >>> Hi, >>> >>> I'm running Alpha-2 and wan

Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2

Wiadomość napisana przez Mike C. w dniu 10 paź 2013, o godz. 23:41: > Hi, > > I'm running Alpha-2 and wanted to test with iscsi but it seems I can't > start iscsid. > > > $ sudo service iscsid onerestart > kldload: can't load iscsi: Exec format error > /etc/rc.d/iscsid: WARNING: Unable to load k

Re: panic: make_dev_credv: bad si_name (error=17, si_name=iscsi)

Wiadomość napisana przez "Sergey V. Dyatko" w dniu 24 wrz 2013, o godz. 09:46: > Hi, > > today I tried to play a bit with new iscsi > > r255812 isn't fully complete fix? > > what I did: > 1) create ctl.conf: > pidfile /var/run/ctld.pid > portal-group example2 { >discovery-auth-group no

Re: iscsictl, Waiting for iscsid(8)

Dnia 27 wrz 2013 o godz. 09:50 "Sergey V. Dyatko" napisał(a): > On Fri, 27 Sep 2013 10:36:29 +0300 > "Sergey V. Dyatko" wrote: > >> Hi, >> >> I have a time to play with native iSCSI stack on HEAD. >> I have desktop (Alpha2, r255812) and laptop (alpha3, r255873M with >> reverted r255870 and

Re: iscsictl, Waiting for iscsid(8)

Dnia 27 wrz 2013 o godz. 09:36 "Sergey V. Dyatko" napisał(a): > Hi, > > I have a time to play with native iSCSI stack on HEAD. > I have desktop (Alpha2, r255812) and laptop (alpha3, r255873M with > reverted r255870 and r255871) > On desktop I create following /etc/ctl.conf: > pidfile /var/run/

Re: panic: make_dev_credv: bad si_name (error=17, si_name=iscsi)

Wiadomość napisana przez Sergey Kandaurov w dniu 24 wrz 2013, o godz. 14:04: > On 24 September 2013 15:44, Edward Tomasz Napierała wrote: >> Wiadomość napisana przez Sergey Kandaurov w dniu 24 wrz >> 2013, o godz. 13:00: >>> On 24 September 2013 14:40, Sergey Kand

Re: panic: make_dev_credv: bad si_name (error=17, si_name=iscsi)

Wiadomość napisana przez Sergey Kandaurov w dniu 24 wrz 2013, o godz. 13:00: > On 24 September 2013 14:40, Sergey Kandaurov wrote: >> On 24 September 2013 11:46, Sergey V. Dyatko wrote: >>> Hi, >>> >>> today I tried to play a bit with new iscsi >>> >>> r255812 isn't fully complete fix? >>> >

Re: iSCSI boot ... root?

Wiadomość napisana przez Zaphod Beeblebrox w dniu 16 wrz 2013, o godz. 07:35: > Is it now possible to boot from iSCSI? I'm not talking about an iSCSI > controller, but with > > pxe -> dhcp -> tftp (loads loader) -> (something) -> boot (mounts root from > iSCSI) Not yet. The iSCSI initiator re

Re: New iSCSI stack.

I'm working on last few minor nits to get this into the tree. Give me few days, I'll prepare a patch against 9-STABLE. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail t

Re: New iSCSI stack.

Wiadomość napisana przez Alfred Perlstein w dniu 6 wrz 2013, o godz. 20:18: > On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote: >> Hello. At http://people.freebsd.org/~trasz/cfiscsi-20130904.diff you'll find >> a patch which adds the new iSCSI initiator and target, against 1

Re: New iSCSI stack.

Wiadomość napisana przez Outback Dingo w dniu 6 wrz 2013, o godz. 09:46: > On Fri, Sep 6, 2013 at 1:50 AM, Edward Tomasz Napierała > wrote: > New patch, updated for Capsicum changes, is here: > > http://people.freebsd.org/~trasz/cfiscsi-20130906.diff > > > Bra

Re: New iSCSI stack.

New patch, updated for Capsicum changes, is here: http://people.freebsd.org/~trasz/cfiscsi-20130906.diff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-cur

  1   2   >