Displaying 20 results from an estimated 140 matches similar to: "FreeBSD 4.11 -> 6.2 Oplocks issue.."
2009 Aug 28
1
FreeBSD 7.2 and Samba 3.3.7 AD 2003 Authentication Problem
I am having problems upgrading samba 3.0.36 to 3.3.7. I have a working
installation of Samba 3.0.36 on FreeBSD 7.2 amd64, configured as a
domain member in a 2003 AD, running in native mode. Domain controllers
have Services for Unix 3.5 installed and I am using idmap backend with
SFU schema mode. I have enclosed my configuration files and compile
options further down. When I upgrade to version
2006 Jun 05
1
Conflicting Signal 6 and 11 messages..
Hello All,
I'm trying to figure out where the problem is, but I'm not having much
luck as I seem to get conflicting information from the various logs on
my FreeBSD 6.1 system.
I'm getting this in the /var/log/samba/log.smbd:
[2006/06/05 12:31:43, 0]
smbd/oplock.c:release_level_2_oplocks_on_change(771)
release_level_2_oplocks_on_change: failed to lock share mode entry
for
2006 Nov 18
2
can't join samba to win2k3 domain - please help
Hello, I've managed to join four other samba servers to win2k3 domains
in the past but I am stuck doing so with samba-3.0.23c_2,1. I've
verified hosts / domain forward and reverse lookups succeed. Below are
my configurations. I'm running FreeBSD 6.1-stable cvsupped as of Nov 17.
I've built Samba with the following options...
WITH_LDAP=true
WITH_ADS=true
WITHOUT_CUPS=true
2008 Feb 27
0
Samba 3.0.26a: "Attempt to create file with volid set - please report this"
Hi everyone;
I noticed today while watching my syslog, a few entries like this:
Nov 8 15:17:08 [machine] smbd[26137]: Attempt to create file (FILE.GHO) with volid set - please report this
Nov 8 15:28:08 [machine] smbd[26137]: Attempt to create file (FILE0001.GHS) with volid set - please report this
Nov 8 15:41:46 [machine] smbd[26137]: Attempt to create file (FILE0002.GHS) with volid
2007 Jan 01
0
HEADS UP: FreeBSD 4.11, 6.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On January 31st, FreeBSD 4.11 and FreeBSD 6.0 will have reached their End
of Life dates and will no longer be supported by the FreeBSD Security Team.
Users of either of these FreeBSD releases are strongly encouraged to upgrade
to FreeBSD 5.5, FreeBSD 6.1, or the upcoming FreeBSD 6.2 before that date.
Discussion concerning FreeBSD
2017 Jun 08
0
nouveau "eDP-1: EDID is invalid" regression after 4.11 with HP ZBook 15 G3
Ben,
I think I'm being hit with this bug (I see EDID is invalid in dmesg), is
there any workaround outside of recompiling without that commit and can I
give any information to help?
Max
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20170608/de78457c/attachment.html>
2017 Jun 13
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
Ilia Mirkin <imirkin at alum.mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
QA Contact| |xorg-team at lists.x.org
Product|DRI |xorg
Assignee|dri-devel at
2017 Jun 14
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
--- Comment #8 from Ben Skeggs <skeggsb at gmail.com> ---
I investigated an issue a while back that I believe is likely the same as what
you're experiencing. I'm, unfortunately, not able to reproduce properly (long
story) on any hardware I own.
I've identified a few issues that could result in what you're seeing, however,
2017 Jun 20
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
--- Comment #9 from wilrikerDE+freedesktop at gmail.com ---
I have the same issue on an Asus PL80Jt which has the same Nvidia Chip built
in. Using modprobe.blacklist=nouveau let's me but just fine (except that PRIME
won't be enabled and the card will not be disabled by vgaswitcheroo). Otherwise
I experience what has been described here.
2017 Jun 21
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
--- Comment #10 from Ben Steel <bhs_suse at precisionforesight.com> ---
Thank you Mr. Coenen. I agree. Kernel 4.12.0-rc6 does not exhibit the problem
on a Lenovo T510 either.
Between a fix already in the pipeline and a modeset workaround in the meantime,
I'm happy. Does anyone still need the bisection completed?
--
You are receiving
2017 Jun 22
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
Ben Steel <bhs_suse at precisionforesight.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--
You are receiving this mail
2017 Jun 23
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
--- Comment #11 from Ben Skeggs <skeggsb at gmail.com> ---
(In reply to Ben Steel from comment #10)
> Thank you Mr. Coenen. I agree. Kernel 4.12.0-rc6 does not exhibit the
> problem on a Lenovo T510 either.
> Between a fix already in the pipeline and a modeset workaround in the
> meantime, I'm happy. Does anyone still need
2017 Jun 23
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
--- Comment #12 from Ben Steel <bhs_suse at precisionforesight.com> ---
Yikes. I only waited about 28 hours before completely restoring that machine
from backup and putting it back in service. Food for thought: my greatest fear
is that the problem may have been illuminated by the change to GCC 7, which
doesn't like compiling 4.10
2017 Jun 26
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
https://bugs.freedesktop.org/show_bug.cgi?id=101368
Daniel Otero <otero.o.daniel at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.freedesktop.or
| |g/show_bug.cgi?id=101587
--
2017 Aug 14
0
nouveau driver locks up with 4.11 kernel
On Mon, Aug 14, 2017 at 4:29 PM, Michal Hocko <mhocko at kernel.org> wrote:
> On Mon 14-08-17 15:27:20, Ilia Mirkin wrote:
>> On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko <mhocko at kernel.org> wrote:
> [...]
>> > nouveau 0000:03:00.0: fifo: channel 6 [mpv/vo[3535]] kick timeout
>> > nouveau: mpv/vo[3535]:00000000:0000906f: detach gr failed, -110
>>
2017 Aug 14
1
nouveau driver locks up with 4.11 kernel
On Mon 14-08-17 15:27:20, Ilia Mirkin wrote:
> On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko <mhocko at kernel.org> wrote:
[...]
> > nouveau 0000:03:00.0: fifo: channel 6 [mpv/vo[3535]] kick timeout
> > nouveau: mpv/vo[3535]:00000000:0000906f: detach gr failed, -110
>
> Are you using mpv in conjunction with the GL video output and
> VDPAU-based acceleration? That
2019 Jan 04
1
xen 4.11
Hi
is there a reason why xen 4.11 isnt released for centos7 (I cant find it
on http://mirror.centos.org/centos/7/virt/)?
--
------
Greetz
2004 Aug 02
1
Netware 4.11 -> Samba 30
Hello,
I have to migrate 30GB from a Novell Netware 4.11 to Samba (ReiserFS/ACL).
When I used robocopy.exe from the Windows XP Resource-Kit, it will only
copy the Timestamp, but
not the owner. Is there a way to copy the owner of a file or directory?
matze
2019 Sep 22
0
Samba 4.11 "Stale file handle"
Can you please post your smb.conf?
On Sat, Sep 21, 2019 at 12:45 PM Kacper via samba <samba at lists.samba.org>
wrote:
> Hello,
>
> After upgrading to Samba 4.11 (from 4.10) I noticed that python
> scripts using tempfile.mkstemp fail when run against samba cifs
> mounts. Before I submit a bug report, could someone else try this out
> so it's not just my setup?
>
2019 Sep 22
0
Samba 4.11 "Stale file handle"
On 21/09/2019 17:43, Kacper via samba wrote:
> Hello,
>
> After upgrading to Samba 4.11 (from 4.10) I noticed that python
> scripts using tempfile.mkstemp fail when run against samba cifs
> mounts. Before I submit a bug report, could someone else try this out
> so it's not just my setup?
>
> How to reproduce:
> 1. Mount a Samba 4.11 share using the mount command: