Hi,
Using any vt but vt1 for X work around this issue.
I've made some testing with buster.
The crash only occurs when X is launched from vt1.
Leave vt1 free!
--
igor
I think this package must by installed by default
I think this bug report will be closed soon
It looks very much like this one
https://bugs.debian.org/845720
--
igor
Package: zerofree
Version: 1.0.3-1
Severity: normal
Dear Maintainer,
Earlier in this year, upstream's URL was moved.
Here's a patch for debian/watch:
2c2
< http://intgat.tigress.co.uk/rmy/uml/zerofree-(.*)\.tgz
---
http://frippery.org/uml/zerofree-(.*)\.tgz
Hope this helps.
igor
-- System
Package: src:linux
Version: 3.16.7-ckt11-1+deb8u3
Severity: normal
Dear Maintainer,
It is the default gnome desktop.
The whole system freezes after that Oops.
I do not have a clue of what could possibly be the cause.
Thanks.
-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (de
Dear Maintainer,
Same problem with a LifeBook C1020.
Solved this way :
- remove xserver-xorg-video-savage (BTW is it DRI2 compatible?)
- take care of some meta packages (task-*, *-video-all)
- comment/remove 'blacklist savagefb' from /etc/modprobe.d/fbdev-blacklist.conf
- use fbdev as the device
Hi,
Not found in 3.14.5 anymore.
Everything is back to normal.
Thanks.
--
igor
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
Same oops found in 3.14.4
I got only 1G of RAM.
What do you think about x32 kernel in debian-ports?
Backtrace
[ 113.028011] INFO: rcu_sched self-detected stall on CPU { 1} (t=5250 jiffies
g=3455 c=3454 q=42)
[ 113.028011] sending NMI to all CPUs:
[ 113.028011] NMI backtrace for cpu 1
[
Hi,
I've made some diffs on linux config files to understand what's going on.
$ diff config-3.13-0.bpo.1-amd64 config-3.13-0.bpo.1-686-pae | grep -i kvm
< CONFIG_KVM_DEVICE_ASSIGNMENT=y
CONFIG_KVM_DEVICE_ASSIGNMENT is set for amd64 arch
$ diff config-3.13-0.bpo.1-686-pae config-3.12-0.bpo.1-686-
Package: src:linux
Version: 3.13.7-1~bpo70+1
Followup-For: Bug #742184
Dear Maintainer,
Oops again with 3.13.7 kernel
However I don't need to kill qemu-kvm manually this time.
It ends as expected when I close the window.
Thanks,
--
igor
-- Package-specific info:
** Version:
Linux version 3.13-0.
Package: src:linux
Version: 3.13.5-1~bpo70+1
Severity: important
Dear Maintainer,
This is an amd64 system running 32 bits 686-pae kernel
1G of RAM
I have not (can not) tested with full 64 bits system
qemu-kvm is working for some seconds then oops
I tried both qemu-kvm from wheezy and from wheezy-b
> No, thanks, that looks good. I don't know when I will have time to
> upload the backport myself though, so if you trick someone into doing
> it, that's fine with me, of course.
>
> Lucas
Ok. I'll contact debian-backports list then.
Thanks.
igor
--
To UNSUBSCRIBE, email to debian-bugs-dist-re
Hi Lucas,
You can find the local backport there
http://igor80.free.fr/how-can-i-help/
Diff with original gives
diff -r how-can-i-help-4/debian/changelog
how-can-i-help-4~bpolocal/debian/changelog
0a1,6
> how-can-i-help (4~bpolocal) stable-backports; urgency=medium
>
> * wheezy-
Package: how-can-i-help
Version: 4
Severity: wishlist
Dear Maintainer,
I tried and succeed in building a usable backport for wheezy
One just need to match wheezy versions in two depends:
- ruby-debian (>= 0.3.8+b1) instead of 0.3.8+b2
- ruby-json (>= 1.7.3-3) instead of 1.8.0-1
However I may have
13 matches
Mail list logo
