If the verification apply also on 16.04, it does fix the issue.
We had a server that triggered the bug at least once a day (I suspect
unattended-upgrade run every morning to trigger it). Since the upgrade -
2 days and half ago - the server had no issue.
--
You received this bug notification beca
** Attachment added: "lspci + software version"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401636/+files/pierref-system-info.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubu
** Attachment added: "Kernel panic when suspending"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401633/+files/pierref-crash.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubu
I have null pointer exception on a XPS 13 (9343) which trigger a kernel
panic when I suspend the laptop. I can reproduce the issue nearly all
times (3 / 4 tries), for this I need to generate network traffic
(looking a video on Internet seem to be enough).
After applying the patch mentioned above,
** Attachment added: "Kernel panic when suspending"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401634/+files/pierref-crash.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubu
I see that trusty has now a kernel with the fix included:
$ cat changelog.Debian
linux (3.13.0-21.43) trusty; urgency=low
[...]
[ Tetsuo Handa ]
* SAUCE: kthread: Do not leave kthread_create() immediately upon SIGKILL.
[...]
After a apt-get dist-upgrade to this kernel, I've successfully boot
I've tested this new kernel, it boot without issue on the server (as
usual, I booted three time the kernel to make it always works well).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1276
Joseph,
kernel freeze is planed in 7 days, which will arrive very fast. Do you
think we could have a fix committed before this deadline ?
I still didn't tested the firmware upgrade. I didn't tested it to keep a
machine which exhibit the bug... upgrading firmware is okay with a local
machine, but
I've tested with kernel from comment #56.
The kernel generated too much logs for IPMI serial console (which
generated too much garbage), so I switched to a real serial console (and
at 115kbauds).
I've attached a archive with 3 runs (the last run it the most
interesting I think):
First run with s
Applied patch on tag v3.14-rc6 (fa389e2), run kernel 4 four times, all
worked.
We seen on output (full output attached):
[5.537193] mousedev: PS/2 mouse device common for all mice
[ [9.776032] floppy0: no floppy controllers found
[ 36.823538] Ignored SIGKILL by systemd-udevd
[ 38.3560
I've tested the final patch againt both 786235ee and tag v3.14-rc6
(fa389e22). It still works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Kernel 3.13 fail to boot with
Yes, it is working!
With this new patch applied (on 786235ee), server boot without any
issue.
I've attached the console ouput (which show no error).
As for other test, I've booter 5 times on this kernel to be sure it was
not by luck that it work.
Thanks for this fix.
** Attachment added: "Cons
** Attachment added: "Console output with kthread-defer-leaving patch applied
on 786235ee"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026609/+files/serial-ouput-patch-kthread-defer-leaving.txt
--
You received this bug notification because you are a member of Ke
I've tested the following:
* v3.14-rc6-trusty from comment #38 : still fail with same error.
* Kernel 786235eeba0e1e85e5cbbb9f97d1087ad03dfa21 with patch check-sigkill :
still got the fail to spawn thread. I will attach full output from serial
console.
* Kernel 786235eeba0e1e85e5cbbb9f97d1087ad0
With few hopes, I've tried the latest kernel from:
* trusty: linux 3.13.0-16.36 (linux-image-3.13.0-16-generic)
* trusty-proposed (downloaded from launchpad directly) : linux 3.13.0-17.37
Both still have the bug.
--
You received this bug notification because you are a member of Kernel
Packages,
If it help, I've done another change (against git hash 786235ee):
diff --git a/kernel/kthread.c b/kernel/kthread.c
index b5ae3ee..25a4780 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -298,7 +298,7 @@ struct task_struct *kthread_create_on_node(int
(*threadfn)(void *data),
I've attached the debdiff patch for trusty.
I'm building a backport for precise to test if slapd can start with this
patch applied (the server on which the issue occure is running precise).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
By more testing, you just mean reboot several time on this kernel to
check that the isssue do not appear sometime ?
During my bisect, I always booted 3 times on good kernel to make sure it
was not by "luck" that the kernel worked. I also booted three time the
kernel from comment #28.
To double ch
Any update ?
If i can help for something tell me, but I don't know kernel and can't do
debuging of it by myself.
I've tried to identify which ENOMEM cause the issue by added the printk
(one before the first ENOMEM, one before the second ENOMEM, one after
both ENOMEM)... but with just this change
Yes, this version is working:
Linux version 3.13.0-12-generic (root@gomeisa) (gcc version 4.8.2
(Ubuntu 4.8.2-15ubuntu3) ) #32 SMP Mon Feb 24 18:50:37 UTC 2014 (Ubuntu
3.13.0-12.32-generic 3.13.4)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Bisect finished. The first bad commit is
786235eeba0e1e85e5cbbb9f97d1087ad03dfa21. It seem more likely as this
commit concerne kthread (and the first error is "scsi4: error handler
thread failed to spawn, error = -12").
I also attach my bisect log if needed.
** Attachment added: "bisect.log"
Ok, I've restarted a bisect without limitation on driver/scsi (git
bisect start v3.13-rc1 v3.12).
Git tell me it's 13 steps, will took some time, but during middle of
next week we should have the bad commit.
--
You received this bug notification because you are a member of Kernel
Packages, which
I can not test this kernel, it was only build for i386. The server is
installed with amd64 :(
Because of timezone difference we can only test one kernel per day, to speed up
the bisect, I've done one by myself, the result is the following:
$ git bisect log
# bad: [6ce4eac1f600b34f2f7f58f9cd8f0
This kernel version is also good:
Linux version 3.12.0-031200rc5-generic (jsalisbury@gomeisa) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402131403 SMP Thu Feb 13
19:04:57 UTC 2014
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This one is good, it is working:
[...]
Linux version 3.12.0-031200rc5-generic (jsalisbury@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402131150 SMP Thu Feb 13 16:54:49 UTC 2014
[...]
--
You received this bug notification because you are a member of Kernel
Packages, which is
Tested this kernel. It is NOT working, it has the issue.
Extract of console log:
[...]
Linux version 3.12.0-031200-generic (jsalisbury@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402101715 SMP Thu Feb 13 14:58:01 UTC 2014
[...]
[ 42.455969] scsi4: error handler thread fail
Yes, I confirm that 3.12-saucy works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Status in “linux” package
None of them worked. All had the same issue.
Tested:
* v3.13-rc3
* v3.13-rc2
* v3.13-rc1 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc1-trusty/)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
It still occure with 3.14.0-031400rc1-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
Status in “linux”
I booted kernel with following common option : "ro console=tty0
console=ttyS1,57600".
When booted with rootdelay, it's "rootdelay=45".
The result are the following:
* 3.13.0-7-generic, rootdelay => error
* 3.13.0-7-generic, no rootdelay => Ok
* 3.6, rootdelay => Ok
* 3.12, rootdelay => Ok, t
Public bug reported:
We have recently upgraded an Dell R300 server to Trusty (was running
fine in precise), and after upgrade it fail to boot.
It is an issue with the SAS controller during the initilisation. It fail
to detect the disk, we have the following error in console log:
[ 36.539955] s
** Attachment added: "lspci -vnn on the server"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/3970067/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
** Attachment added: "dmesg from a running system (no rootdelay, press
control-d in initramfs)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/3970066/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
33 matches
Mail list logo
