Phil Richardson, as per
http://www.dell.com/support/drivers/us/en/19/Product/optiplex-755 an update is
available for your BIOS (A22). If you update to this following
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it
doesn't, could you please both specify what happene
This bug is not confined to cifs mounts in fstab.
I can get a kernel crash if i mount it manually but too soon after boot. I have
a rather fast boot since i am running on an ssd and lubuntu so i think there
might be some timing. issue, either network isn't properly up or some other
process is d
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114673
T
*** This bug is a duplicate of bug 1070256 ***
https://bugs.launchpad.net/bugs/1070256
apport information
** Tags added: apport-collected staging
** Description changed:
Seeing the same as in bug #1070256
Linux phil-server 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC
2013
*** This bug is a duplicate of bug 1070256 ***
https://bugs.launchpad.net/bugs/1070256
Of note, it took three systems reboots to allow CIFS operation following
report generation.
CPU load was spiralling out of control an with each passing second was
picking up at a linear pace.
Unfortunately
*** This bug is a duplicate of bug 1070256 ***
https://bugs.launchpad.net/bugs/1070256
fstab config
# Mount the NAS drives
//192.168.0.200/Volume_1 /media/verbatim cifs
guest,uid=1000,iocharset=utf8,codepage=unicode,unicode 0 0
//192.168.0.199/store /media/a cifs
guest,uid=1000,iocharset=ut
** This bug is no longer a duplicate of bug 1070256
mount.cifs occasionally causes GPF error/kernel panic when mounting at boot
[crypto_larval_kill+0x2b/0x90]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Phil:
Could you try following the instructions here:
https://wiki.ubuntu.com/Kernel/BugTriage/Responses#Please_Test_Latest_Upstream
to see if it happens on the latest upstream kernel.
** Tags added: needs-upstream-testing
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You
High: Lots of people seeing these oops on samba stuff
Incomplete: Asking for upstream testing
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I will try, but that page is by far the most confusing thing I have ever
read.
I get the process of conducting the install, of which files I need due
to arch and stuff, but the process of determining which is the upstream
one to use ?!?!
Given I am on 3.2.0-37.58, does that mean I use the one in
Take the one right at the bottom of http://kernel.ubuntu.com/~kernel-
ppa/mainline/ (currently v3.8-rc7-raring/)
If it works reliably then no, doesn't need any other debug; if it oopses or
breaks in any other way just say what happened;
all I'm trying to do here is see if the very latest bleedin
Whole host of additional hassle from this, as fstab adjustments were
required (already aware of these from second system on 12.10).
Feb 11 19:10:59 phil-server kernel: [ 20.417424] CIFS VFS: cifs_mount failed
w/return code = -13
Feb 11 19:10:59 phil-server kernel: [ 20.513764] general protect
Triaged: Tested upstream - still fails
Thanks for trying that Phil; ok, so that means it still fails upstream.
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
To add, this kernel caused me to pain. On removing it, it failed during
removal an a spontaneous reboot left me with a system that would not
boot as it could not find the kernel.
As it's headless, finally managed to get on an boot to old kernel. When
loaded, completed the removal and rebuild Grub.
14 matches
Mail list logo