I tried the "abi-tag patch version 4" attachment, and it appears to
introduce some compiler crashes under 'make check-all'. Try out
test/CodeGenCXX/static-local-in-local-class.cpp and you appear to get
unbounded recursion:
$ gdb --args /home/steven/Development/llvm/build/Release/bin/clang -cc1
Public bug reported:
Running on armhf board with binutils 2.24-5ubuntu3. Any attempt to use
-flto with the gold linker yields this internal error:
$ cat test.c
int main(int argc, char **argv)
{
return 0;
}
$ gcc -flto -fuse-ld=gold -o test test.c
/usr/bin/ld.gold: internal error in
I no longer have the system in the original report, and cannot verify
whether the issue is resolved or not. I would appreciate it if someone
else CC'd on this report would chime in -- I don't want to see this
issue dropped on the floor if it's still an issue for others.
--
You received this bug
I've stopped using IPv6 tunneling due to this kind of pain. Might as
well wait for my ISP to get IPv6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154083
Title:
NetworkManager crashed with
I am still experiencing corruption as well using a git build (from the
day before yesterday) of xf86-video-intel... It's very difficult to
reliably reproduce the issue but it's definitely still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I have a SIXXS IPv6 tunnel set up on my Linux router box, using radvd to
announce the route to boxes on the LAN side. With the configuration for
my wireless connection set to 'Automatic' for IPv6, network-manager will
segfault, be restarted, try again, segfault, restart, try
Public bug reported:
All I needed to do to reproduce was run 'lshw' on a Samsung Chromebook.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: lshw 02.16-1
Uname: Linux 3.4.0-02511-g6efeff4 armv7l
ApportVersion: 2.9-0ubuntu2
Architecture: armhf
CrashCounter: 1
Date: Mon Mar 4 13:09:25
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1145306/+attachment/3557452/+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/1145306
apport information
** Tags added: apport-collected
** Description changed:
All I needed to do to reproduce was run 'lshw' on a Samsung Chromebook.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: lshw 02.16-1
Uname: Linux 3.4.0-02511-g6efeff4 armv7l
ApportVersion:
For whatever reason, apport-collect doesn't want to generate
DistroRelease, which is blocking my ability to apport-retrace
** Changed in: lshw (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed, since the report is ill-formed. Perhaps the report data got
modified?
need more than 1 value to unpack
If you encounter the crash again, please file a new report.
Thank you for
Oops, looks like apport's broken.
I'm just going to include a stack trace here via gdb, remove the need-
armhf-retrace tag and call it a day. The ddeb on ddebs.ubuntu.com
doesn't match the CRC for lshw (despite identical package versions):
warning: the debug information found in
Stefan, let's be sure this fix gets upstream 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/1011792
Title:
Kernel lockup running 3.0.0 and 3.2.0 on multiple EC2 instance types
To manage
Just installed Xubuntu 12.04.1 yesterday and hit this issue. What action
is needed to drive this ticket to resolution?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006431
Title:
disabled touchpad
Well, the hosts are still running fine. pgslam.py eventually bombed out
on all of them with InternalError: could not open relation with OID.
Not sure why, but either way there were no lockups. It's possible
test1 resolves the issue. Konrad?
--
You received this bug notification because you are a
I've got 'test1' running on 19 hi1.4xlarge instances using the pgslam.py
workload. They're all up to 40G of capacity used right now, still no
lockups.
I'll leave this running for a while longer and see what happens (9 hours
so far).
--
You received this bug notification because you are a member
Stefan,
I did our internal SSD and network performance testing qualifications on
hi1.4xlarge with CONFIG_PARAVIRT_SPINLOCKS=n in the kernel build.
There's very little discernible difference in performance (within
statistical noise ranges), and the benefits of disabling it are pretty
clear. Can
Re: pv-grub, yeah. The hook that updates the menu.lst is pretty ugly,
and specifically looks for *-virtual kernels, assuming that no other
kernel could possibly support Xen. Why not grep for the right option in
the installed config-$(uname -r)?
Anyway, 3.5.6 -might- fix it, but I only see one
Stefan, here's the Arch Linux kernel package tree:
http://projects.archlinux.org/svntogit/packages.git/tree/linux/repos
/core-x86_64?id=6b8ed4e6660afe873aef3a207b187c5eb124c855
They build from a release tarball on kernel.org with only 4 patches
applied (none of which touch scheduling or anything
OK, with a few more iterations over kernel configs, it looks like it all
comes down to this:
--- config-3.2.0-31-virtual 2012-10-10 01:02:10.0 +
+++ config-3.2.0-31-virtual-noautogroup 2012-10-11 01:33:14.886307000 +
@@ -144,7 +144,7 @@
CONFIG_USER_NS=y
CONFIG_PID_NS=y
Out of curiosity I tried an Arch Linux instance (running Linux
3.5.6-1-ARCH), which also has CONFIG_SCHED_AUTOGROUP:
# zgrep AUTOGROUP /proc/config.gz
CONFIG_SCHED_AUTOGROUP=y
I ran the same pgslam workload on it, and it filled 64G of the
/var/lib/postgres md-raid before I stopped it. This
It looks like Quantal has the same issue. Thing didn't even fill more
than 100MB before deadlocking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011792
Title:
Kernel lockup running 3.0.0 and
Stefan, the kernel version in the Amazon Linux AMI that Matt pointed at
is 3.2.21-1.32.6.amzn1.x86_64, so it is very close to comparable with
the affected Ubuntu kernel (yes, there are source differences, but they
at least have a merge base of 3.2.21 so they share significant lineage).
I was able
I see the same crash here. I'm investigating it, but in the meantime
here's a backtrace.
** Attachment added: gdb-backtrace.txt
https://bugs.launchpad.net/ubuntu/+source/lordsawar/+bug/1038698/+attachment/3267859/+files/gdb-backtrace.txt
--
You received this bug notification because you are
Crash occurs because of a bug in libtar. They're not respecting the
bounds checking code in glibc, and it catches them misbehaving.
Attached patch resolves the issue. This bug should be reassigned to
libtar.
** Patch added: libtar-1.2.11-encode_buffer_overrun_fix.patch
Upstream testing doesn't make sense since the patch is Ubuntu-specific
and newly introduced between 3.2.0-20-generic and 3.2.0-21-generic.
Reverting the patch fixes the issue.
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
The dmesg shows it, but:
[7.027622] BUG: unable to handle kernel NULL pointer dereference at
(null)
[7.027643] IP: [a0757d08] asus_wmi_rfkill_init+0x188/0x200
[asus_wmi]
[7.027647] PGD fd4c28067 PUD fd4c27067 PMD 0
[7.027650] Oops:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970451
Title:
NULL pointer dereference in asus_wmi_rfkill_init
To manage notifications about this bug go to:
Presumably this is where the dereference is happening:
@@ -895,7 +896,7 @@ static int asus_wmi_rfkill_init(struct asus_wmi *asus)
if (result result != -ENODEV)
goto exit;
- if (!asus-driver-hotplug_wireless)
+ if (!asus-driver-quirks-hotplug_wireless)
Okay, this is ridicuous. Those are the latest debug packages on
ddebs.ubuntu.com. Reopening since this is easily reproducible.
** Changed in: golly (Ubuntu)
Status: Invalid = New
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
The call stacks do look very similar, but I'm not quite convinced it's a
duplicate of bug 836250. I'm not experiencing the performance
degradation that Eduardo is.
What's the best way to disable the 802.11n protocol? I tried 'iwconfig
wlan0 modulation 11g', but this failed with 'SET failed on
OK, just tested with the access point set to disable 802.11n entirely,
and split 2.4GHz/5GHz to separate SSIDs.
When connected to 2.4GHz, that particular warning has stopped appearing at
least. I do see this:
[122038.374737] ieee80211: phy0: wlc_prec_enq_head: No where to go, prec == 4
appearing
Apparently my router doesn't support 802.11n on the 2.4GHz band anyway,
only supports 802.11n on 5GHz.
To summarize:
- The chipset refuses to connect to 5GHz 802.11a, repeating the warning in the
original report before giving up.
- The chipset connects to 5GHz 802.11n, but still frequently
Public bug reported:
My kernel log is being filled by this:
WARNING: at /build/buildd/linux-3.0.0/net/mac80211/rx.c:2910
ieee80211_rx+0x9b/0x1b0 [mac80211]()
[... stack trace, etc ]
at a very very fast rate. Since the stack trace shows it is in
ieee80211_rx and the rate is so high, I'm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876231
Title:
very frequent warnings in kernel log with BCM43224
To manage notifications about this bug go to:
I can confirm that reverting 99bbb3a8 fixes the issue for
cc1.4xlarge/cg1.4xlarge.
Public HVM AMI with cheap fix applied: ami-9dbf7ef4 (derived from ami-
0db17064, with manually built kernel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: xorg
First off, yes. I'm running the NVIDIA drivers. This is not related, though. I
have had this issue under multiple conditions:
1. With an ATI card, running -either- open source or proprietary drivers. (this
was very oddly fixed by adding
** Attachment added: 1-broken.jpg
https://bugs.launchpad.net/bugs/734069/+attachment/1904604/+files/1-broken.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734069
Title:
** Attachment added: 2-halfbroken.jpg
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/734069/+attachment/1904632/+files/2-halfbroken.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734069
Here's what things look like after:
sudo killall -9 gnome-settings-daemon
gnome-settings-daemon
killall nautilus
** Attachment added: 3-success.jpg
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/734069/+attachment/1904633/+files/3-success.jpg
--
You received this bug notification
I too experienced this. Took a few days to find this bug report too,
with many hours of frustration. Nothing's been done to fix this in over
a year?
--
[Feisty[mouseemu]Freeze of usb mouse while using keyboard
https://bugs.launchpad.net/bugs/113344
You received this bug notification because you
41 matches
Mail list logo
