Public bug reported:
Binary package hint: linux-source-2.6.20
Hello.
I'm building custom flavour kernels, but I'm experiencing compilation failure
since 2.6.20-17.37.
2.6.20-17.39 refers a nonexistent directory
linux-source-2.6.20-2.6.20/debian/abi/2.6.20-17.39/
while running "debian/rules bina
Public bug reported:
Binary package hint: linux-source-2.6.15
$ wget
'https://launchpad.net/ubuntu/dapper/+source/linux-source-2.6.15/2.6.15-54.76/+files/linux-source-2.6.15_2.6.15.orig.tar.gz'
$ tar -zxf linux-source-2.6.15_2.6.15.orig.tar.gz
$ cd linux-source-2.6.15-2.6.15/
$ wget
'https://la
Sorry.
As of my first report, 2.6.27-5.8 was the current and 2.6.27-4.7 was the
previous.
As of this report, 2.6.27-6.9 is the current and 2.6.27-5.8 is the previous.
It seems that I was missing some preparations before building custom flavours.
I tried to build "generic" flavour kernel, and debi
This is not a bug.
It turned out that I was missing some preparations before building custom
flavours.
Please close this topic and #278459.
--
Building custom flavours fails for 2.6.20-17.39
https://bugs.launchpad.net/bugs/261708
You received this bug notification because you are a member of Ub
Public bug reported:
Binary package hint: linux-source-2.6.27
Hello.
I'm experiencing similar problem reported at
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/261708 .
2.6.27-5.8 refers a nonexistent directory linux-2.6.27/debian/abi/2.6.27-5.8/ .
Only previous version's
Public bug reported:
2.6.26-5.17 fails to compile et131x.ko for CONFIG_NET_ET131X=m and
CONFIG_LOCKDEP=y because et131x.ko needs to access lockdep_init_map .
-
[EMAIL PROTECTED]:/usr/src/linux-2.6.26# make -sj2
...
Kernel: arch/x86/boot/bzImage is ready (#2)
FATAL: modpost: GPL-incompatib
Hello.
Leann Ogasawara wrote:
> Just curious why you're trying to build the kernel yourself?
To test my TOMOYO Linux patch for Ubuntu 8.10 kernel.
> It also looks like you are enabling CONFIG_LOCKDEP=y by modifying the default
> Intrepid kernel config.
Yes, I enabled CONFIG_LOCKDEP=y by hand.
I re
Hello.
> Please let us know immediately if this newer 2.6.27 kernel resolves the bug
> reported here or if the issue remains.
The issue is remaining in 2.6.27 too, as EXPORT_SYMBOL_GPL(lockdep_init_map);
remains unchanged in kernel/lockdep.c .
I reported this topic at
https://lists.ubuntu.com/
Public bug reported:
I get OOM-killer whenever compiling the kernel.
[ 96.079516] gcc invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
[ 96.079524] gcc cpuset=/ mems_allowed=0
[ 96.079531] Pid: 4095, comm: gcc Not tainted 2.6.32-22-generic #36-Ubuntu
[ 96.079535] Call Trace:
[ 9
I'm sorry. It turned out that this is my misconception.
make's job limit was not configured correctly.
Please ignore this bug.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
[Lucid] OOM-killer
https://bugs.launchpad.net/bugs/590605
You received this bug notification because you
I can't answer what is happening here. But can you obtain more information
using SysRq-t
and SysRq-m as described at
https://akari.osdn.jp/capturing-kernel-messages.html#Tips5 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
No plan to land upstream yet. Casey's upstream proposal
(
http://kernsec.org/pipermail/linux-security-module-archive/2017-December/004728.html
) is stalling.
Please carry my patch as UBUNTU: SAUCE: patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Thanks for reporting. This is a duplicate of bug 1734327 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752621
Title:
BUG: unable to handle kernel paging request at ded533a0
To manage not
Since 18.04 seems to give up LSM stacking patchset, safest choice (if
acceptable) would be to completely revert LSM stacking patchset for
17.10 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
It seems to me that this is not a kernel problem.
I guess that there was a NULL pointer dereference in RSG-Linux-Shipping when
the system started entering severe memory pressure. Then, due to severe memory
pressure, many memory allocation requests started stalling. But there is no
kernel oops mess
Well, not 6 seconds. It is 21 seconds.
I overlooked that timestamp in syslog and uptime are not in sync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928
Title:
Kernel segfault playing EVERSPAC
As far as I can see, nothing is wrong, except you put too much memory
pressure on your machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928
Title:
Kernel segfault playing EVERSPACE
To man
Just a comment from a security module developer.
What happens if you pass security=none to kernel command line options
(i.e. disable AppArmor security module), for I think it might help
isolating the problem because you are hitting oops at
security_vm_enough_memory_mm() and security_file_free().
Since you are using apparmor=0 parameter,
this will be a duplicate of bug 1734327.
Try removing apparmor=0 parameter for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749221
Title:
kernel cr
Thank you for reporting this problem. Ubuntu 17.10 kernel has
"LSM: Stacking for major security modules" patches enabled and
this problem will be a bug in the patches. That's why mainline
4.13.11 kernel works fine.
I reported this problem at
http://kernsec.org/pipermail/linux-security-module-archi
The dump looks like below bug. Was the bug already fixed in 4.13.0-25.29
?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731031
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734327
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Forgot to mention. Try removing apparmor=0 parameter for now.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734686
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742572
Title:
System Hangs
OK. Your report will be duplicate of 1731031, 1734327, 1734686.
Explanation of the bug is
http://kernsec.org/pipermail/linux-security-module-archive/2017-November/004532.html
and the fix for the bug is
http://kernsec.org/pipermail/linux-security-module-archive/2017-December/004638.html
.
Accor
The problematic patches are not yet in mainline/upstream kernels,
and hence the fix patch is not yet in mainline/upstream kernels.
Please ask Joseph Salisbury when the action for Artful kernel will be
taken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
F.Y.I. Here is the kernel panic message.
You can google for "PANIC: double fault, error_code: 0x0".
[ 193.361839] PANIC: double fault, error_code: 0x0
[ 193.363960] Kernel panic - not syncing: Machine halted.
[ 193.366020] CPU: 1 PID: 1822 Comm: a.out Not tainted 3.13.0-140-generic
#189-Ubuntu
You can monitor
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744199 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744071
Title:
linux 3.13.0-140.189 - kernel panic after trying to launch
All the detail is in Bug #1276705.
(1) Currently finit_module() of mptsas kernel module does need more than
30 seconds to initialize LSI SAS1068E disk.
(2) Currently systemd-udevd unconditionally sends SIGKILL upon hardcoded
30 seconds timeout. As a result, finit_module() of mptsas kernel
Public bug reported:
TOMOYO in Linux 3.2 and later kernels depend on tomoyo-tools 2.5.
To fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1106992 ,
can somebody please backport tomoyo-tools 2.5 to Precise? (Or at least delete
tomoyo-tools 2.4 from Precise ?)
** Affects: tomoyo-tools (Ubu
Public bug reported:
Moving the discussion from http://www.spinics.net/lists/hotplug/msg05769.html
to launchpad, for I think that this bug needs to be handled in initramfs-tools
package rather than in udev package.
--
I'm experiencing random boot failures with wait-for-root utility in Ub
I confirmed that below patch fixes my problem.
-- patch start --
--- a/src/wait-for-root.c
+++ b/src/wait-for-root.c
@@ -88,7 +88,9 @@ main (int argc,
/* When the device doesn't exist yet, or is still being processed
* by udev, use the monitor socket to wait it t
(a) Linux kernel guys think that a hardcoded timeout is a systemd bug.
https://lkml.org/lkml/2014/3/23/42
(b) The systemd guys think that kernel module loading takes more than
30 seconds is a kernel module's bug. But Linux kernel guys won't
be able to fix it immediately. Also, solutio
I'm not planning to submit this patch to linux-stable tree because this bug is
not a user-triggerable crach/memleak/panic. But if you prefer applying this
patch via linux-stable release, I'll submit this patch to linux-stable tree.
--
You received this bug notification because you are a member of
> This patch was accepted in jmorris/linux-security.git and is currently in
> next/linux-next.git and will be merged into torvalds/linux.git as 3.4-rc1.
FYI: This patch was merged into 3.4-rc1.
commit df91e49477a9be15921cb2854e1d12a3bdb5e425
Author: Tetsuo Handa
Date: Wed Feb 29 21:53:2
This patch was accepted in jmorris/linux-security.git and is currently in
next/linux-next.git and will be merged into torvalds/linux.git as 3.4-rc1.
In case devel freeze date for kernel package comes before 3.4-rc1 comes,
I posted this request without waiting for 3.4-rc1.
--
You received this bug
apport information
** Tags added: apport-collected
** Description changed:
Please apply commit df91e494 "TOMOYO: Fix mount flags checking order." which
is
in linux-next.git and will be included in 3.4-rc1. Without this patch, when
security=tomoyo is given to kernel boot parameter, certain
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885698/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952010
Ti
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885699/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952010
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885700/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952010
Title:
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885701/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885702/+files/Card0.Codecs.codec97.0.ac97.0.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885703/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885704/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952010
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885705/+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/952010
Title:
[Preci
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885706/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952010
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885707/+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/952010
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885708/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9520
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885709/+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/952010
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885710/+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/952010
Title:
[Pre
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885712/+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/952010
Titl
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/952010/+attachment/2885711/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952010
Title:
[P
Martin Pitt (pitti) wrote on 2013-08-26:
> I have never actually seen ENOBUFS, or uevents being missed due to it,
> so I think the chance of that is quite small. But I can't assert that
> all messages will be received after an ENOBUFS. But as you said,
> waiting longer in that case is a safer fallb
Similar report in systemd package.
https://bugzilla.redhat.com/show_bug.cgi?id=655857
** Bug watch added: Red Hat Bugzilla #655857
https://bugzilla.redhat.com/show_bug.cgi?id=655857
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Thank you.
By the way, is there any possibility that "the message of a block device which
the wait-for-root is waiting for" cannot be received after ENOBUFS?
I think that any messages of block devices which are generated while the socket
buffer is full cannot be received using recvmsg(). I worry
> Yes it would be great if you can see if this patch will be accepted in
linux-stable.
OK. This patch was accepted to 3.0.28, 3.2.15 and 3.3.2 upstream.
Please close this bug when Precise kernel rebases to 3.2.15.
Thank you.
--
You received this bug notification because you are a member of Ubun
Hello, Marco.
The problem handled by this entry is about mptsas_probe() hitting
scsi4: error handler thread failed to spawn, error = -12
mptsas: ioc0: WARNING - Unable to register controller with SCSI subsystem
BUG: unable to handle kernel NULL pointer dereference at 0060
due t
Recent distros can silently hang due to insufficient RAM while decompressing
kernel image. Did you give enough RAM?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303657
Title:
Cannot boot trusty ke
starvation because the OOM killer cannot kill such users.
kthread_create() is one of such users and this patch fixes the problem for
kthreadd by making kthread_create() killable.
Signed-off-by: Tetsuo Handa
Cc: Oleg Nesterov
Acked-by: David Rientjes
Signed-off-by: Andrew Morton
--
I think
OK. I read this thread.
I'm sure that somebody is sending SIGKILL to the systemd-udevd process
who is doing finit_module() system call, after waiting for 30 seconds.
However, since the probe function takes more than 30 seconds, the probe
function already received SIGKILL by the moment scsi_host_al
Would you try this patch?
** Patch added: "kthread: defer leaving kthread_create() upon SIGKILL."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026192/+files/kthread-defer-leaving.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs
Thank you. I missed that we are not allowed to call wait_for_completion() again
if wait_for_completion_timeout() succeeded, for do_wait_for_common() does
x->done-- which cancels x->done++ done by complete(). I must update this patch.
--
You received this bug notification because you are a member
I changed this patch to call wait_for_completion() again only if
wait_for_completion_timeout() returned 0, for
wait_for_completion_timeout() will return non-0 if completed.
** Patch added: "kthread: defer leaving kthread_create() upon SIGKILL. (v2)"
https://bugs.launchpad.net/ubuntu/+source/l
Great!
I updated this patch to be more OOM killer friendly.
I will propose this patch for 3.14-final.
** Patch added: "Final patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026689/+files/kthread-Do-not-leave-kthread_create-immediately.patch
--
You received
I reproduced a similar result using test patch shown below.
-- test patch start --
diff --git a/drivers/message/fusion/mptspi.c b/drivers/message/fusion/mptspi.c
index 5653e50..eaaa5e2 100644
--- a/drivers/message/fusion/mptspi.c
+++ b/drivers/message/fusion/mptspi.c
@@ -1412,6 +14
Pierre, would you give me a hand? I proposed the final patch but
I'm unable to prove that SIGKILL sent by systemd-udevd's 30 seconds
timeout is the trigger of this problem, for I don't have a real
machine which takes very long time upon initialization.
According to https://lkml.org/lkml/2014/3/18/
PierreF wrote:
> Applied patch on tag v3.14-rc6 (fa389e2), run kernel 4 four times, all
> worked.
Thank you!
Now we proved that systemd-udevd's 30 seconds timeout is the trigger of
this problem. It would be best if we can fix systemd side.
Joseph, is there any possibility that systemd-udevd's ti
Public bug reported:
Coming from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705
.
Commit 786235ee in the upstream kernel made kthread_create() return
immediately upon SIGKILL. On several machines, device initialization
phase takes more than 30 seconds before kthread_create() is call
Hello from upstream author.
This bug was discussed at tomoyo-dev-ja mailing list, but it seems that
tomoyo-tools-2.5 package did not arrive in time for Ubuntu 12.04 release.
http://sourceforge.jp/projects/tomoyo/lists/archive/dev/2011-October/001362.html
(2011/10/25):
Today I uploaded tomoyo-t
Public bug reported:
Please consider applying below bugfix patches.
All patches are already in upstream Linux 3.0 kernel.
For Ubuntu 10.04 LTS kernel:
[PATCH] TOMOYO: Fix race on updating profile's comment line.
(commit 2a086e5d3a23570735f75b784d29b93068070833 upstream.)
http://tomoyo.sourceforge
"apport-collect 830298" didn't work.
root@ubuntu:~# apport-collect 830298
ERROR: connecting to Launchpad failed: 'NoneType' object has no attribute
'makefile'
You can reset the credentials by removing the file
"/root/.cache/apport/launchpad.credentials"
Below output shows that patch for CVE-201
I posted this topic to netdev ML.
http://www.spinics.net/lists/netdev/msg180263.html
According to Eric W. Biederman, Debian has tweaked
vsftpd to not use network namespaces on 2.6.32.
By combining tweaking vsftpd and this patch, I think
we might be able to reenable CONFIG_NET_NS.
What do you thi
> How about adding this one too?
Already applied.
# grep call_usermodehelper
ubuntu-11.04/linux-2.6.38-15.59/drivers/block/drbd/drbd_nl.c
ubuntu-11.10/linux-3.0.0-19.33/drivers/block/drbd/drbd_nl.c
ubuntu-12.04/linux-3.2.0-24.37/drivers/block/drbd/drbd_nl.c
ubuntu-11.04/linux-2.6.38-15.59/drive
Public bug reported:
Please apply commit df91e494 "TOMOYO: Fix mount flags checking order." which is
in linux-next.git and will be included in 3.4-rc1. Without this patch, when
security=tomoyo is given to kernel boot parameter, certain combination of mount
request cannot be granted.
Test case:
Public bug reported:
I tried to boot
http://cdimage.ubuntu.com/daily-live/current/precise-desktop-i386.iso
with security=tomoyo kernel boot parameter. But it can't boot (kernel panic)
because kernel was built with CONFIG_SECURITY_TOMOYO_OMIT_USERSPACE_LOADER=y .
CONFIG_SECURITY_TOMOYO_OMIT_USERS
This bug depends on Bug 952035.
Also, apport-collect does not help because this is a TOMOYO's bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
This is a kernel panic before /sbin/init starts.
Thus, apport-collect cannot be used.
Attached file is kernel log obtained using "security=tomoyo
console=ttyS0,119200n8 console=tty".
** Attachment added: "kernel log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/952035/+attachment/284
OK. I'll try to run apport-collect after Bug 952035 was fixed.
I think John Johansen knows what this bug is, for I found this bug while I was
reviewing AppArmor's patches.
http://www.spinics.net/linux/fedora/linux-security-module/msg13088.html
http://www.spinics.net/linux/fedora/linux-security-mod
apport information
** Tags added: apport-collected
** Description changed:
I tried to boot
http://cdimage.ubuntu.com/daily-live/current/precise-desktop-i386.iso
with security=tomoyo kernel boot parameter. But it can't boot (kernel panic)
because kernel was built with CONFIG_SECURITY_TOMOY
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849735/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952035
Ti
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849736/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952035
Title:
apport information
** Attachment added: "Card0.Amixer.info.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849737/+files/Card0.Amixer.info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849738/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849739/+files/Card0.Codecs.codec97.0.ac97.0.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
apport information
** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849740/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849741/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952035
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849742/+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/952035
Title:
[Preci
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849743/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952035
I guess that the latest kernel config is
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;f=debian.master/config/config.common.ubuntu;h=7ac2ddf7eb5cac9f2af0354fe05d9f2a06892333;hb=e9c4a165e75b9a308a10e5e0ae0a5956a46d9a6a
,
and it contains a line
4605 CONFIG_SECURITY_TOMOYO_OMIT_USERSPA
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849750/+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/952035
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849745/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9520
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849744/+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/952035
Ti
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849752/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952035
Title:
[P
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849751/+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/952035
Title:
[Pre
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/952035/+attachment/2849753/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Does vsftpd retry without CLONE_NEWNET if attempt with CLONE_NEWNET failed?
If yes, reenabling CONFIG_NET_NS with this (untested) patch might help.
Even if no, reenabling CONFIG_NET_NS with this patch with
adequate initial value (e.g. 64) assigned to max_netns_count might help.
** Patch added: "u
Public bug reported:
I tried to install
http://releases.ubuntu.com/natty/ubuntu-11.04-beta1-server-i386.iso
on VMware Workstation on Windows XP.
The bootloader runs in graphical mode but the installer runs in text mode.
However, due to vga=788 parameter which is automatically applied,
the screen
95 matches
Mail list logo
