Ok, thank you
i added the yakkety-proposed repo to my xenial computer and install the
4.8.0-40.43 kernel
This kernel works also well under xenial :)
I changed the tag 'verification-needed-yakkety' to 'verification-done-
yakkety'
** Tags removed: verification-needed-yakkety
** Tags added:
Looks good,
this bug seems to be solved with the -proposed kernel 4.4.0-65.86 ...
good work ... thank you very much
I changed the tag 'verification-needed-xenial' to 'verification-done-
xenial'
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You
Looks good,
the 4.4.0-65.86 from -proposed do not have the bug for us any longer ...
great work ... thank you very much.
I changed the tag 'verification-needed-xenial' to 'verification-done-
xenial' but i do not run any instance of yakkety, so i can not test it
on this ubuntu version.
But for
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS client : permission denied when trying to access
Ok, looks good, i tried several reboots with this kernel and all were
successfull :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650336
Title:
NFS client : kernel 4.4.0-57 crash with nfsv4
Yes ...
referring to the permission denied when accessing subshares, this kernel
build ( 4.4.0-63 ) works fine.
I has to comment out the second share in /etc/fstab or set it to noauto.
I will work now with this kernel on my PC, hoping there is no other
problem ;)
And also hoping the other bug
This looks very good.
Access to the subshares is possible without permission denied :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS client : permission denied when trying to
Hm, sorry i hope there was no misunderstanding ?!
As i mentioned some times before, there was a strange behaviour when i test the
kernels the first time.
Sometimes a kernel boot successfully for one or two times and crash not before
the third try ...
I could reproduce this behaviour on
So, now i try to formulate a new short bug description with all facts i
know at the moment :
Since kernel version 4.4.0-42 (offical repo for 16.04.1) the boot
process crashed when there are at least two nfsv4 entries to the same
nfs-server in /etc/fstab
With only one share entry in the
@Seth
> Thanks for the clarifications.
Har Har
> Yeah, looks like this build never made it out of our PPA.
Unfortunately, i do not found this kernel versions on one of our computers.
But i am rather sure having seen this kernel in the offical repos
--
You received this bug notification
@Seth : Yes, this problem is very confusing
Since posting #8 i used a dedicated test system with a fresh kubuntu 16.04.1
installation on a well tested system.
During the testing i modify /etc/fstab switching between noauto/auto options of
nfs shares and later changing server uri to ip address
Very stange ...
I test 4.10-rc4 again and found that the kernel is booting without
problems with all shares when using the pure IP address for the server
in /etc/fstab ... it is irrelevant if the correct entry in /etc/hosts
exist or dns resolution is ok.
I dunno why 4.9.4 is working with dns
When you ask if the kernel 4.10-rc4 do not crash any long on boot time,
then i can answer : Yes, the kernel do not crash any longer.
But when you ask if the kernel 4.10-rc4 work as expected with nfs
Then i can answer No, he do not work as expected with nfs shares.
IMHO the mainline kernel 4.9.4
Thank you for your effort
Unfortunately the tests are very confusing
With the two shares from the FreeBSD 11 Server the mainline kernel 4.10.0 has
no problem !!!
Also if i try to mount two additional shares from another FreeBSD 11 Server. No
Problem at all !
But if i am try to mount the two
Sorry, the same behavior.
But i found something else...
It is very frustrating, to be apparent the only one having this problem, so i
try to setup a nfsv4 server on Ubuntu (14.04.5 with linux-generic-lts-wily
kernel 4.2.0-42)
/etc/exports:
/home/exports
No, sorry the kernel crash, too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650336
Title:
NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab
To manage notifications about this
Thank you for the test kernel :)
But unfortunately it also crashs at the same position.
Beginns with: BUG: unable to handle kernel paging request at 814121a8
...
The 4.4.41 also crash, as i mention before ... On all computers i tested
i have the same behavior that i can successfully boot
The mainline kernel 4.8.17-040817 do not have the problem, 4.4.41-040441
have the problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650336
Title:
NFS client : kernel 4.4.0-57 crash with nfsv4
I noticed some additional detail ...
The problem only occur if the second nfs share is on the same NFS Server as the
first share.
I tried to mount a second share from another NFSv4 Server, also running under
FreeBSD 11, without problem
--
You received this bug notification because you are a
The Bug #1650336 seems to have dependency with the number of nfs shares
should be mounted in fstab (from the same server) ...
For your information :
Apart from this kernel crash problem with multible nfs mounts ... the
4.4 mainline kernels, including the 4.4.41 from yesterday seems not to
have
Sorry, no changes ... but i noticed something that could be usefull.
To ensure there is no hardware problem on my computer, i installed a
fresh kubuntu 16.04.01 on a newer maschine and configured it.
Same behaviour ... the base kernel from installation 4.4.0-31 work without
problem ... but all
Unfortunately no changes ... same behavior ...
But i notice something strange ... if i boot some of this corrupt
kernels that crash and then restart with the Magic SysRQ into a "good"
kernel ...this kernel crashes at the same point.
Another Magic SysRQ or a cold start let boot the "good" kernel
Thank you for this test kernel.
Unfortunately this one has the same problems like the official 4.4.0-57
Without /etc/fstab or with noauto entries for nfs the kernel boot fine.
With the nfs entries the kernel crashes ... sorry
--
You received this bug notification because you are a member of
I create a new bug report Bug #1650336 for the crash with the nfs
/etc/fstab entry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS client : permission denied when trying to access
Yes,
in fact it is not possible to execute the apoort-collect command when the
kernel crashed.
If someone need information about the hardware, i can boot the computer
without the nfs stab entry and execute then the command.
But i can also report the same problem from other computers ( for
Public bug reported:
On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
crash on boot when in /etc/fstab a nfsv4 entry is active
When comment the line or set to noauto the kernel boot with no error and
mounting the nfs shares (after uncomment ) is also possible without
error
Ok,
your kernel 4.4.0.54.75... boots and works with no permission error :)
For the kernel crash i will create a new bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
No changing since 4.9-RC8 ... the kernel boots ... mounting shares from
fstab ... but i got permission denied at the second subshare
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
> 4.4.0-38 contains a patch (backported from 4.8)
Hmm, when i remember correctly, after the first time the permission
problem occurs a lot of kernel updates comes in quick succession ... and
when i test this updates i had similar crashes on boot time and booting
without fstab entries works and
Ok, i can boot without the /etc/fstab entries and mount then the NFS
shares without errors ...
I added the logs as an attachment ...
** Attachment added: "kernel_crash.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+attachment/4791915/+files/kernel_crash.txt
--
You
Ah ... to early :(
In the patch i saw "automount" and in fact i configured autofs to mount
the nfs shares.
Now i disabled autofs and uncomment the appropriate entries in
/etc/fstab and the kernel crash on boot time.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
looks good :)
In this kernel the problem is fixed.
Thank you very much !!!
But for my personal interest, could you explain me in a few words in
which part of the kernel this fix works ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
To complete the list :
The 4.4 mainline kernel works without problem (4.4.38-040438-generic)
The versions of mainline kernels 4.8.13 and 4.9.0 RC8 not
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, i test to install these old kernels once again to say nothing wrong
...
The Kernel 4.4.0-31 was working definitive for us. The next Kernel
4.4.0-34 also seems to work and 4.4.0.36 too ...
Kernel 4.4.0-38 now seems to be the first kernel having the problem.
Strange thing ... as i remember
I tested something else ...
Now i change only the group permissions ( chgrp staff and chmod 750 ... but the
result is the same.
Fristlevel subshare with the need of checking permissions will work, the second
level subshare not.
By the way ... one reason why we use a Solaris Fork or FreeBSD as
Maybe i found something interesting ...
I create a structure of zfs filesystems on the server similar my home
path, but with general file permissions ... chown root:root and chmod
775 and mount this on the client under /home/user/staff/fili/data
And i am able to access this directory
When i
Ok, here the logs after login attempt with kernel 4.4.0-57-generic
** Attachment added: "kernel_debug.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+attachment/4791260/+files/kernel_debug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791062/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791061/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791064/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791067/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791068/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791063/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791065/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791066/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791069/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791070/+files/WifiSyslog.txt
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649292/+attachment/4790718/+files/AlsaInfo.txt
--
You
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791059/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4791060/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
Sorry, i forget to trigger the problem before sending apport-collect ...
I will send the right one and delete the old
When i try to login i got :
Could not chdir to home directory /home/VI/staff/fili/linux : Permission denied
...
-bash: /home/VI/staff/fili/linux/.bash_profile: Permisson denied
also ZFS filesystems.
-
- So my homefolder is located on the server under
- /apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
- filesystem. On the client nfs share /apool/AIS/share/home is mounted
- under Similar Bug #1603719 or Bug #1604396 i got a "Permission denied"
- when tr
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790724/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
homefolder is located on the server under
/apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
filesystem. On the client nfs share /apool/AIS/share/home is mounted
under Similar Bug #1603719 or Bug #1604396 i got a "Permission denied"
when trying to access a NFS subshare f
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790722/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790720/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790719/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790721/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790729/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790728/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790726/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790727/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790725/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1649292/+attachment/4790723/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649292
Title:
NFS
e problems to the clients
with FreeBSD 10.3 and OmniOS r151018.
All NFS servers use ZFS as the filesystem and NFSv4 with kerberos for
sharing. For the basic structure we use also ZFS filesystems.
So my homefolder is located on the server under
/apool/AIS/share/home/staff/fili/linux ... each level is a ZFS
Very strange ...
for us the problem is not solved ... all Kernel Versions for Trusty and Xenial
since 4.4.0-31-generic are affected ... 4.4.0-54 also.
Through the report here and Bug #1604396 i tested some mainline kernel ...
By todays post the latest 4.4 mainline kernel ( 4.4.37-040437-generic
Hi,
for me the proposed kernel 4.4.0-46.67 do not work ... Permission denied
...
As mentioned above mainline 4.4.27 work without problem.
Maybe some surveillance will help.
In our enviroment the FreeBSD 11 server shares /apool/NFS/share/home as
NFSv4 + Kerberos ... every directory is a zfs
Similar problem here,
but ubuntu kernel 4.4.0-31 was not affected here, all kernels from there
to the current 4.4.0-45-generic has the problem.
Today i found this thread and test the latest mainline,
4.4.27-040427-generic, this one works without problems :)
NFS Server is FreeBSD 11, but also
Workaround #16 only worked the first reboot. Afterwards not any more.
Since then I just do the following steps everytime I reboot (I know this
can probably be automated, but I am really hoping this bug gets fixed
soon).
gparted - reformat linux-swap
sudo mkswap /dev/sdaX
sudo swapon
I'm experiencing the same bug. It would be great if someone would pick
up the bug because it makes ffserver at the moment completely broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879018
I also had no output on the headphones of my Lenovo Thinkpad R61i,
adding
options snd-hda-intel model=generic
to /etc/modprobe.d/alsa-base.conf helped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
://bugs.launchpad.net/ubuntu/+source/empathy/+bug/560575
I'm running;
Ubuntu 11.04
Empathy 2.34.0
Regards,
Fili
** Affects: empathy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Confirmed on Jaunty
--
memcached not able to be started with invoke-rc.d
https://bugs.launchpad.net/bugs/120784
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
VERY GOOD
** Changed in: ubuntu-website (upstream)
Assignee: Matthew Nuzum = (unassigned)
--
Ubuntu download page lacks a link to Howto burn an image CD
https://bugs.launchpad.net/bugs/112951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
73 matches
Mail list logo
