from: drivers/acpi/apei/ghes.c (this is git head rather than any
specific version):
if (hest_disable) {
pr_info(GHES_PFX HEST is not enabled!\n);
return -EINVAL;
}
then drivers/acpi/apei/hest.c:
bool hest_disable;
EXPORT_SYMBOL_GPL(hest_disable);
Hi Joseph,
this still occurs for me with the 3.5.7 from that link (and with current
raring), but as stated not with the 3.5.0-19 from quantal.
My test procedure on my box is:
* Fresh boot
* Log in via kdm as my default user
* Wait for my standard KDE desktop to settle
* K
Triaged: Because the reporter describes the problem exactly
Medium: I was thinking originally low since It's got an easy work around and I
think this is a very unusual situation,
however to someone not experienced it's going to be hard to understand and
I actually don't know how unusual the
Peter; could you state the OS install version, and package version of
the virt-manager and qemu-kvm you've got.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1093292
Title:
vm
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093365
Title:
apport
id2ndr:
To me that looks like a separate problem from this one; all the people on
this one had keys that showed up as combination CDROM/disk pairs and it was the
kernel getting upset at the cdrom which from the limited debug from yours
doesn't seem to be the case. I suggest reporting a
High - Accessibility of core app
** Changed in: ubiquity (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093303
Title:
can't switch from orca to ubiquity in
Triaged: Because the reporter describes the problem exactly
Medium: I was thinking originally low since It's got an easy work around and I
think this is a very unusual situation,
however to someone not experienced it's going to be hard to understand and
I actually don't know how unusual the
Peter; could you state the OS install version, and package version of
the virt-manager and qemu-kvm you've got.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093292
Title:
vm won't start if host
Triaged since the reporter has debugged and fixed it.
** Changed in: libproc-processtable-perl (Ubuntu)
Importance: Undecided = Medium
** Changed in: libproc-processtable-perl (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Flipping to linux package since it's a kernel bug.
You'll be asked to record some logs; please do this on the kernel that
does boot ok, and put a note on the end reminding people that it's the
different version that fails
** Package changed: ubuntu-release-upgrader (Ubuntu) = linux (Ubuntu)
**
Confirmed this on 4.6.3-13ubuntu1 on raring.
** Changed in: gcc-4.6 (Ubuntu)
Importance: Undecided = Medium
** Changed in: gcc-4.6 (Ubuntu)
Status: New = Confirmed
** Also affects: gcc-4.7 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Also triggered on 4.7.2-16ubuntu1 on raring:
$ g++-4.7 cc8HZt1y.i
ParserFunctions/BasicIntegerParser_continuous.cpp: In member function ‘virtual
Vertica::UDParser*
BasicIntegerParserFactory::prepare(Vertica::ServerInterface,
Vertica::PerColumnParamReader, Vertica::PlanContext, const
Hi Christopher,
Which model thinkpad is this?
(I've got thinkfan on a w520 and I don't think I had to edit those files to get
it to work - although I can't remember).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ken:
Can you submit a separate bug for it please and attach your logs showing the
oops to it please, and then add a comment here giving the bug number.
(They may well get merged)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Maarten:
OK, it still crashes, and the reason is you're MIN/MAX aren't sufficient:
cirRefreshArea: pbox: (-958,52 / -236,486) clipped: (0,52 / -236,486)
pScrn-vX/Y 1024,768 rotate=0
you need to use both MIN and MAX on each coordinate to cope with the box
being completely off one side of the
Here's a fix; it was carefully snprintf'ing with a limit of 24 into a 20
char buffer - and then terminating at 23 chars for good luck.
** Changed in: barrage (Ubuntu)
Status: Confirmed = Triaged
** Patch added: Fix the name field in the menuentry
bah, after writing that fix I noticed it was already fixed in 1.04
upstream (but not in Debian yet)
** Bug watch added: Debian Bug tracker #696562
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696562
** Also affects: barrage (Debian) via
id2ndr: Can you attach the output of the
dmesgcommand
and
lsusbcommand
after having plugged the flash disk in.
My guess is this is actually a different problem than the sandisk one but
similar symptoms.
--
You received this bug notification because you are a member of
Hang on, scrap that analysis - I noticed the logs show it's not loading
the rebuilt cirrus module with that change; It's now showing an EABI
mismatch error. I'll get back to you.
Dave
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Triaged = Incomplete
--
You received this
and to compound things, the kernel driver is now working on raring, so I
can't load this one to test it; let me get back to you next weekend.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lankhostversion.png
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1043513/+attachment/3460902/+files/lankhostversion.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: myversion.png
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1043513/+attachment/3460904/+files/myversion.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Maarten,
That patch isn't happy; but I'm not sure why yet; I've attached three screen
captures:
1) The version with the ubuntu built package - which shows the strange
crosshatching from bug 1080674
2) myversion.png - the version with my patch, looks the same as (1) but
doesn't
psivaa: Can you run an xdpyinfo in VBox and KVM and attach both the
outputs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080674
Title:
[QEMU] Corrupted desktop screen for raring desktop
*** This bug is a duplicate of bug 1071209 ***
https://bugs.launchpad.net/bugs/1071209
** This bug has been marked a duplicate of bug 1071209
memtest86 test #7 false positives (random number sequence error)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
.invert_brightness=1
All give me the same lower screen resolution (1024 x 768) instead of the
one I used to have (1366 x 768). Changing brightness does not work and
using Alt-Tab reminds me of Windows 3.1.
Merci,
Gilbert
2012/12/8 Kangarooo 765...@bugs.launchpad.net
Did you really tryd changing brightness
The following bugs appear to all be ftrace related oopsen happening on
3.5.0-20.31 :
bug 1087967
bug 1087622
bug 1087584
So looks like something not too happy.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
High (dead on startup) - set for hjd
** Changed in: horgand (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891939
Title:
horgand segfaults at startup (due
#5 0x004066f7 in strcpy (__src=0x430ed0 m(Maj7)(b5), __dest=0x65dd00
hor+105536 )
at /usr/include/x86_64-linux-gnu/bits/string3.h:104
No locals.
#6 HOR::HOR (this=0x6440c0 hor) at organ.C:633
tapsg = {36, 33, 29, 27, 24, 21, 17, 15, 13, 16, 21, 24, 27, 31, 33, 36}
OK, here's a patch that gets past the overflow; I think it's safe; there are a
LOT of fixed length string buffers in the
code. This stretches this 10 char to 12 char to fit the string being copied
in; there are places that append that string
into others in other bits of the code, but I *think*
** Bug watch added: Debian Bug tracker #695467
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695467
** Also affects: horgand (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695467
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I've set your bug 1024578 back to New; it shouldn't time out for a long time
now.
There are lots and lots and lots of bugs though, so whether or not yours is
seen by the developer
I cannot say.
** Changed in: cups (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Marking Low (because it has a workaround)
** Changed in: musescore (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087975
Title:
Title prints duplicate and
In your report you say that you had previously also used HP printers;
have you tried this, after the upgrade that broke it; it would be
interesting to know if the problem was only effecting Brother printers
or was something more general.
** Changed in: cups (Ubuntu)
Status: Incomplete =
Both parameters had no effect. The screen backlighting went off, as it did
in the first place.
g
2012/12/8 Kangarooo 765...@bugs.launchpad.net
try without acpi_osi and check if works with changing brightness and
if alt+tab gives 3d effect.
if not good then try it should work.
Triaged: Trivially repeatable test case
Fails on g++ 4:4.7.2-1ubuntu7 on current Raring.
** Changed in: gcc-4.7 (Ubuntu)
Importance: Undecided = Medium
** Changed in: gcc-4.7 (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1071209 ***
https://bugs.launchpad.net/bugs/1071209
** This bug has been marked a duplicate of bug 1071209
memtest86 test #7 false positives (random number sequence error)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
reporter asked for it to be closed.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087115
Title:
Xorg process is eating my CPU cores in
I disagree; it needs a signed boot loader; whether it's grub or not is a
different matter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086981
Title:
Signed Kernel should depend on
Setting to confirmed since it's a kernel bug (albeit in external module it
seems reasonable to treat the same way)
High-seems appropriate for oops on server.
Gavin:
Can you paste more of the syslog please; in particular is there are a line of
4 numbers just before it ; I can see an eprintk in
** Changed in: qemu-linaro (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078397
Title:
kvm-spice[15252]: segfault at 20 ip 7fb7b9e83986 sp
Can you confirm when you say 'waking the computer to to resume work' you
mean it had previously booted but was hibernating/sleeping, and it only
does this when you wake it up from the sleep?
Dave
** Summary changed:
- Need to login three times to reach the desktop
+ Need to login three times
This oops looks like the nasty; I can see a similar oops in bug 1087584
in the WiFiSyslog.txt around the 08:34 mark.
[ 17.782530] Could not create debugfs 'i915_gem_object_create' directory
[ 17.782595] Error: Driver 'i915' is already registered, aborting...
[ 17.848044] BUG: unable to
I notice at 08:34 there is this (similar to bug 1087622):
Dec 7 08:34:51 ubuntu kernel: [ 13.229526] BUG: unable to handle kernel
paging request at a0418f08
Dec 7 08:34:51 ubuntu kernel: [ 13.229562] IP: [810fd2ca]
register_ftrace_event+0x7a/0x2b0
Dec 7 08:34:51 ubuntu
, now it's 1024 x 768. Can it be tweaked?
Acer emachnines e725 with Mobile 4 Series Chipset Integrated Graphics
Controller
Gilbert Dion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/765438
Title
Hi,
Attached is a patch that seems to fix this; however it needs looking at by
someone who understands the code; in particular I have some questions:
1) Does this also need to go in cirRefreshArea8/16/24/32 ?
2) Why is the generic one being called if there are those specialised ones
Yeh I'm also seeing this; note that the cirrus driver is the same
1:1.5.1-0ubuntu2 Quantal (that works) and Raring (where it gets this
corruption).
Note that Cirrus tends to run with 24bpp packed that always adds fun and
excitement; and might explain the odd rhythmic patterning.
--
You
OK, it's a one char overrun in the hours reading code; because someone forgot
the remove the \n
This starts up, but I don't know the game so haven't checked the 'hours' work
as intended.
** Patch added: Fix for a 1 char overrun in hours reading code
Gah - got the wrong bug
** Bug watch added: Debian Bug tracker #695294
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695294
** Also affects: xpilot-ng (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695294
Importance: Unknown
Status: Unknown
** Changed in:
** Bug watch added: Debian Bug tracker #695294
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695294
** Also affects: moria (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695294
Importance: Unknown
Status: Unknown
--
You received this bug notification because
the right bug
** Bug watch added: Debian Bug tracker #695297
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695297
** Changed in: xpilot-ng (Debian)
Importance: Undecided = Unknown
** Changed in: xpilot-ng (Debian)
Status: New = Unknown
** Changed in: xpilot-ng (Debian)
Remote
Trivially repeatable on raring
** Changed in: tcpick (Ubuntu)
Importance: Undecided = Medium
** Changed in: tcpick (Ubuntu)
Status: New = Confirmed
** Summary changed:
- *** buffer overflow detected ***: tcpick terminated
+ *** buffer overflow detected ***: tcpick terminated with -t
(From a rebuild from the package) run with -t:
(gdb) bt full
#0 0x77814e35 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 22722
selftid = 22722
#1 0x77818498 in __GI_abort () at abort.c:90
This is a cut-n-paste thinko; fix attached.
(upstream seems dead looking at sourceforge so not sure what the best thing to
do is)
** Patch added: Fix for memset thinko
https://bugs.launchpad.net/ubuntu/+source/tcpick/+bug/1086534/+attachment/3453310/+files/time_ascii-memset_thinko.diff
--
Patch also submitted upstream (although it seems pretty dead):
https://sourceforge.net/tracker/?func=detailaid=3593303group_id=95657atid=612164
** Bug watch added: Debian Bug tracker #695307
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695307
** Also affects: tcpick (Debian) via
** Summary changed:
- Ispci crashed with SIGSEGV in pci_load_name_list()
+ Ispci crashed with SIGSEGV in pci_load_name_list() (with invalid parameter to
-i)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed this still happens on debian and upstream's pciutils-3.1.10; I
can see a trivial fix to lib/names-parse.c:
if (len = 3 memcmp(a-id_file_name + len - 3, .gz, 3) != 0)
return result;
to become
if (len 3 || memcmp(a-id_file_name + len - 3, .gz, 3) != 0)
return result;
but
OK, I'll leave it as 'incomplete' for the moment; if you get around to trying
12.10 again then please add any more detail you can and flip it back to 'New'.
There's probably not too much we can do without more diagnostics, other than to
remember this and watch out for any similar reports.
Thanks
Just an observation that maybe the /dev/disk-by-path stuff is a useful
way of describing what you want to boot reliably
for me in my test setup I have:
ip-192.168.122.10:3260-iscsi-iqn.2008-09.com.example:server1.share1-lun1-part1
as one of the names in there; certainly the iscsi iqn seems not
(You said Precise, but I assume you mean Quantal since that's what I was
previously on - if you really meant precise just ask and I'll try)
I don't seem to be able to trigger it on the Quantal 3.5.0-19, but
managed to repeat the failure on the Raring 3.7.0 (same Raring
userspace)
My test
Reported upstream;
http://sourceforge.net/tracker/?func=detailaid=3591921group_id=13411atid=113411
bzr branch linked with fix.
** Changed in: xpilot-ng (Ubuntu)
Status: Triaged = In Progress
** Bug watch added: SourceForge.net Tracker #3591921
Marking critical since it doesn't boot, and even worse this is a minor
update that triggers it.
** Changed in: linux (Ubuntu)
Importance: Undecided = Critical
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi Jorge,
If you use shift during booting to get the 'grub' menu to display, it should
let you choose a previous kernel version to try;
if that helps you then please add a note saying the kernel version that works
and the version that fails.
Also can you describe the make and model of the
Still happens on Raring in pciutils 1:3.1.9-6ubuntu1
The problem here is that the argument 'i' is supposed to take a
filename; and in this case it's the second i that's being taken as the
filename,
names-parse.c has a broken check for the filename; it's expecting it to
end in .gz which it strips
Have you got a different resolution monitor that you could borrow to try it
with?
I notice the monitors you are using are 1366x768 and I've seen other problems
with that res because it's not divisible by 8
exactly, and various things sometimes get upset.
(Only a hunch, may be wrong).
--
You
http://www.debian.org/doc/debian-policy/ch-relationships.html says:
'If a relationship field has a version number attached, only real packages will
be considered to see whether the relationship is satisfied (or the prohibition
violated, for a conflict or breakage). In other words, if a version
Public bug reported:
This is on a machine upgraded from Quantal to Raring.
I switched between two users, and then switched back under KDE and
managed to trigger that Failed to parse relocation. It happened (and
the screen went blank) at the moment I clicked the 'activate' button on
the screen
Public bug reported:
After an upgrade to Raring (as of today) from Quantal I'm seeing tons of
these in /var/log/upstart/ureadahead.log:
Counted 8 CPUs
ureadahead: ��a��w: Ignored relative path
ureadahead: : Ignored relative path
ureadahead: �=%���n�T9: Ignored relative path
ureadahead:
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910890
Title:
gdb should at least suggest libc6-dbg
To manage notifications about this bug go to:
Tried on Raring; Looks like this got fixed somewhere in the last 4
years.
** Changed in: compiz (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285703
I think there are really two separate bugs going on here;
1) For some reason the Intel chipset doesn't like something and gives up
2) When it cleans up from (1) it panics
It looks to me like 3.5.0-19-generic has fixed the panic on my box; although I
still get a black screen - but that looks
Hmm; I'm closing this as invalid - it does work following your
instructions; but not if I use my image file I'd previously created.
Hmm that's going to be trickier to chase down.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because
Hmm; I'm closing this as invalid - it does work following your
instructions; but not if I use my image file I'd previously created.
Hmm that's going to be trickier to chase down.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because
Confirmed still happening in Raring (That's a raring guest with Quantal
host) as of today's install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in
Whether the two failures are related is difficult to say; the SecondLife
one seems to be failing with a fairly clear problem finding the dri
modules:
libGL: OpenDriver: trying /tls/i965_dri.so
libGL: OpenDriver: trying /i965_dri.so
libGL error: dlopen /i965_dri.so failed (/i965_dri.so: cannot
Interesting; no I don't get that menu - it doesn't get that far for me.
Both of the machines I tried it on are Quantal installs; both using
virt-manager to set the vm up; I'll try your command line set to see if
it makes any difference.
--
You received this bug notification because you are a
My full backtrace on this (quantal 64bit):
#0 0x7f8710ffe425 in __GI_raise (sig=optimised out) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
resultvar = 0
pid = optimised out
selftid = 9345
#1 0x7f8711001b8b in __GI_abort () at abort.c:91
save_stage = 2
It's interesting, I can't trigger this in either my quantal or raring
vm, but I've had it happen on two different quantal machines; one Intel
graphics one ATI (open driver).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting; no I don't get that menu - it doesn't get that far for me.
Both of the machines I tried it on are Quantal installs; both using
virt-manager to set the vm up; I'll try your command line set to see if
it makes any difference.
--
You received this bug notification because you are a
This looks to me as a bug in a debian specific patch; see
debian/patches/gdbinit-ownership.patch
+ warning (not using untrusted file \%s\, file);
+ fclose (stream);
+ do_cleanups (old_cleanups);
+ return;
As far as I can tell from the weird cleanup system, the
** Bug watch added: Debian Bug tracker #694256
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694256
** Also affects: gdb (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694256
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
I've just put a load of comments on the upstream bug
The short story is that a patch to
Xext/xres.c ResFindAllRes
to change
counts[(type TypeMask) -1]++
to
if ((type TypeMask)!=0) counts[(type TypeMask) - 1]++;
stops the crash.
The longer story is, I don't think that case of a 0
Public bug reported:
To repeat:
* Grab freedos ISO from from http://www.freedos.org/download/
* Add it as a CD to your KVM guest
* Boot and go through the defaults (I'm using a small - ~90MB - IDE hard
drive raw image as the 1st IDE disk)
* Go through all the defaults
* Install FreeDOS
** Attachment added: libvirt config for the vm
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1080369/+attachment/3437655/+files/DOS.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Public bug reported:
To repeat:
* Grab freedos ISO from from http://www.freedos.org/download/
* Add it as a CD to your KVM guest
* Boot and go through the defaults (I'm using a small - ~90MB - IDE hard
drive raw image as the 1st IDE disk)
* Go through all the defaults
* Install FreeDOS
** Attachment added: libvirt config for the vm
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1080369/+attachment/3437655/+files/DOS.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
My dad's new machine (freshly installed with Quantal) reliably kernel panics at
boot iff connected via a kvm
switch.
6.265801] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart
module.
[6.280161] BUG: unable to handle kernel NULL pointer dereference at
Some addirtional notes:
* It works if the monitor is connected directly
* The KVM is an old Belkin 8 way Omniview 8 pro (which works fine with the
other machines)
* This ubuntu-bug capture was made from the rescue shell after bringing up
the networking manually
* The symptom as far as
I've just reported bug 1077658 which looks like it might be the same as this.
This only happens for me if I plug in via a KVM switch, not direclty in via a
monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is probably a dupe of bug 1070690
3.7.0-030700rc5 #20120835 from the nightlies works for me
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc5-raring/ although I'm on
a quantal userspace)
So I say that makes it a fixed upstream
3.6.3-030603 #201210211349 boots but won't start X
3.7.0-030700rc5 #20120835 from the nightlies works for me
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc5-raring/ although I'm on
a quantal userspace)
So I say that makes it a fixed upstream
3.6.3-030603 #201210211349 boots but won't start X (but ctrl-alt-f1 gets
me a console)
OK; so we've got to be careful to keep the debug together; I think you really
have two separate things going on:
a) Slow when transferring lots of stuff (as per your vmstat in #9)
b) 'hang up's
Is that perf report from the 'hang up' state - it doesn't seem to have
much system/kernel CPU
Pilot6: Thanks for noting it's now fixed (not sure what fixed it)
** Changed in: aisleriot (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973592
note that sudo echo 2 /proc/sys/vm/dirty_ratiowill give you the perm
denied (because the is in the parent shell)
so if you do
echo 2 /proc/sys/vm/dirty_ratio
from a root shell (e.g. sudo -s ) it should work.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
To simplify my instructions from comment #15:
1) Open a terminal (sits in top left)
2) Ctrl-alt-down arrow to move down one virtual deskop
It blows up at (2).
(pScrn-virtual X/y in cirRefreshArea is 1024/768)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
OK, lets see what we've got; if I'm reading this vmstat correctly it's split
pretty
much between system time and wait (for IO):
procs ---memory-----swap---io
-system-- cpu
r b swpd free buff cache si so
oh, the other thing you might want to see is whether you're running with
jumbo frames or not, they should help the load at both ends.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071978
Title:
Hmm thanks!
OK, so I don't have a /dev/root either; what seems to happen (see
/usr/share/initramfs-tools/hook-functions) is that it
checks the output of
mount
to see where / is mounted, and it's finding that it says /dev/root - and
so that's what it uses /dev/disk/by-uuid to look at via blkid
Thanks for testing that Alan,
Marking as invalid because it looks like it was an old file left behind
somehow.
Note: If someone sees more cases of this then it's probably worth figuring out
if there is something causing them to be left behind rather than it being one
case.
** Changed in:
601 - 700 of 3687 matches
Mail list logo
