On 01/30/2013 01:09 AM, Jonathan Nieder wrote:
Hi Gasha,
Gasha wrote:
Package: linux
Version: 3.2.0-2-amd64
What version? The above is part of the package name, not the version
number --- you can see the currently running version of Linux with
cat /proc/version
(look in t
Thank you for the speedy reply.
Your assumption was correct. I was using 3.2.35-2.
I tried
http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-486_3.2.35-3~jcristau.1_i386.deb
first.
Then I tried
http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.de
I had a similar issue as described in this bug. I recently installed debian
wheezy on a thinkpad x230. As far as I know I use the same i915 module. I'm
using amd64 system and my cpu is "Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz"
My system would freeze sometimes. When it did, I wasn't able to move t
Processing control commands:
> tag -1 moreinfo
Bug #699277 [src:linux] linux-image-3.6-trunk-amd64: OOM killer running loose
on system with lots of memory
Added tag(s) moreinfo.
--
699277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699277
Debian Bug Tracking System
Contact ow...@bugs.debi
Control: tag -1 moreinfo
On Tue, Jan 29, 2013 at 06:29:25PM +0100, Michal Suchanek wrote:
> Package: src:linux
> Version: 3.6.9-1~experimental.1
> Severity: normal
[...]
Please test the current version (3.7.3-1~experimental.1).
Ben.
--
Ben Hutchings
We get into the habit of living before acqu
Hi Gasha,
Gasha wrote:
> Package: linux
> Version: 3.2.0-2-amd64
What version? The above is part of the package name, not the version
number --- you can see the currently running version of Linux with
cat /proc/version
(look in the parentheses) or the currently installed version with
Package: linux
Version: 3.2.35-2
Severity: wishlist
In the current Wheezy kernel, all EDAC modules are built save for the
one for
Intel's Sandy Bridge architecture. It would be nice if one could read
out
EDAC on Sandy Bridge systems, thanks!
The missing kernel configuration is:
CONFIG_EDAC_
Package: src:linux
Version: 3.6.9-1~experimental.1
Severity: normal
Hello,
AFAICT I have enough memory but OOM killer killed my processes.
Before that happened I noticed that large disk writes in kvm would
trigger system pauses and all CPU cores running 100% in system for
extended periods of tim
I stumbled upon this bug while using a backported kernel on squeeze,
and in the process of trying to find a solution, I noticed that there
is also a bug report against Ubuntu kernels in launchpad. The patch
attached to a comment there that reverts a certain commit seems to
solve the problem for me
Package: linux
Version: 3.2.0-2-amd64
Debian: wheezy
Two ethernet interfaces configured in bond0: (/etc/network/interfaces)
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond-mode 2
bond-miimon 100
bond-downdelay 200
bond-updelay 200
post-up ifup br576 br575 br200
# bond for VLAN 576
ifa
Raoul Bhatia [IPAX] 2013-01-29 11:01:
On 2012-10-12 20:52, Brian Kroth wrote:
Brian Paul Kroth 2012-10-11 14:06:
Jonathan Nieder 2012-10-01 01:25:
Once again very sorry for the delay :(
I forgot to disable the DEBUG_INFO and kept filling up my build
VMs disk during compile. Then realiz
T writes:
> Reloading module with: modprobe usbserial vendor=0x12d1 product=0x1003
Probably unrelated to your problem, but...
You should not do that. This device is mode-switched by the usb-storage
driver and handled in modem mode by the option driver. Forcing the
generic serial driver to hand
Package: linux-image-3.2.0-4-amd64
Version: 3.2.35-2
Severity: important
Xen dom0: Debian Wheezy
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
Mainboard Gigabyte Z77X-D3H
lsusb(module xhci_hcd disabled)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 0
Am Dienstag, den 29.01.2013, 12:19 +0100 schrieb Sebastian Riemer:
[…]
> Any further objection?
Small typo (occurs) in commit message.
Thanks,
Paul
From adfac4df99edc1a83dced9c732464634d3381a9f Mon Sep 17 00:00:00 2001
From: Sebastian Riemer
Date: Fri, 25 Jan 2013 12:46:59 +0100
Subject: [P
Hi!
I have rebooted the server, dom0 is now running the 3.2.35-2 image
from backports, with the "nosmap" command line option as suggested.
Previous oopses occurred after some time, a few days or so, so I'll watch and
see what happens.
Thanks for taking the time.
BR
// Mattias
Den 28 January 2
On 29.01.2013 06:45, Ben Hutchings wrote:
> I'm slightly uneasy about returning 0 for all writes to a read-only
> deivce, because if someone ever fails to check the read-only flag
> elsewhere this could turn into silent data loss. Does this work:
>
> BUG_ON(bio_segments(bio));
>
>
On 2012-10-12 20:52, Brian Kroth wrote:
Brian Paul Kroth 2012-10-11 14:06:
Jonathan Nieder 2012-10-01 01:25:
Once again very sorry for the delay :(
I forgot to disable the DEBUG_INFO and kept filling up my build VMs
disk during compile. Then realized I had grabbed the 3.7 rc code,
which
Jonathan Nieder writes:
>> after updating the linux-image-3.7-trunk-amd64 from
>> 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting,
>> the tools ps, pgrep and pkill (package procps) are always segfaulting:
>
> Just to check: if you downgrade to 3.7.1 again, do the segfaults go
Hi,
We had another system triggering this same BUG which did not come out of
resume/hibernate, so the hibernation/suspend does not seem relevant.
Although the issue seems to be a lot easier to hit when using
hibernate/suspend.
Regards,
Rik
--
To UNSUBSCRIBE, email to debian-kernel-requ...
On Tue, Jan 29, 2013 at 12:18:02AM +0100, Sascha Silbe wrote:
> after updating the linux-image-3.7-trunk-amd64 from
> 3.7.1-1~experimental.2 to 3.7.3-1~experimental.1 today and rebooting,
> the tools ps, pgrep and pkill (package procps) are always segfaulting:
And there was nothing else updated at
20 matches
Mail list logo
