Bug#974939: closed by Ben Hutchings (Re: Bug#974939: machine does not boot)
Hi Ben,
On Mon, Nov 23, 2020 at 10:45:09AM +, Debian Bug Tracking System wrote:
> I recommend that you always check the list of packages to be removed in
> a dist-upgrade, if you have some packages installed from
> testing/unstable.
yes. :/
> It doesn't exist in stable. Perhaps you installed something from
> testing/unstable that required it? libgcc-s1 breaks the stable version
> of cryptsetup-initramfs.
I checked. My apt and libc6 are both from stable, and should thus only
have stable dependencies, right?
However, removing libgcc-s1 broke apt ("could not load shared
library...").
Thanks for the heads-ups,
Toni
Bug#974939: machine does not boot
Hi Ben, On Mon, Nov 23, 2020 at 10:12:01AM +, Ben Hutchings wrote: > On Mon, 2020-11-23 at 10:04 +0000, Toni Mueller wrote: > > I agree, but I can only file a bug report against the kernel package. > > Please find the output of this command attached. > cryptsetup support is not included in the newer initramfs images. I saw that, but was not aware of this package: > Did you remove cryptsetup-initramfs by accident? Not that I am aware of, and definitely not intentionally. Until now, I had no idea that it even existed. But I can now see that it was removed in a dist-upgrade run on the 9th of May last year (huh?!?). But there seems to be a problem to re-install it: # apt install cryptsetup-initramfs -y ... The following packages will be REMOVED: libgcc-s1 The following NEW packages will be installed: cryptsetup-initramfs WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! libgcc-s1 0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. Since libgcc-s1 is being provided by libgcc1, I am inclined to run with --allow-remove-essential. But this is still quite scary! (I wasn't aware of libgcc-s1, either. :( ) Thanks, Toni
Bug#974939: machine does not boot
Hi, On Tue, Nov 17, 2020 at 12:50:19PM +0100, Bastian Blank wrote: > On Mon, Nov 16, 2020 at 07:41:05PM +, Toni wrote: > > Severity: critical > > Sorry, no. This problem does not break the package for everyone. > > > On the console, after dmesg, these three lines repeat ad nauseum: > > mdadm: No arrays found in config file or automatically > > Volume group "ev0" not found > > Cannot process volume group ev0 > > mdadm: No arrays found in config file or automatically > > Volume group "ev0" not found > > Cannot process volume group ev0 > > So it actually boots, but the boot process is not able to find your root > filesystem? It loads the kernel, I can see the dmesg, and then I see an endless loop of these messages. So yes, there's something broken with encrypted partitions, that wasn't broken until the -10 kernel. > Yes, that look pretty normal and like something the Debian installer > would create. It did. > What is the content of /etc/crypttab? /etc/fstab? /boot/grub/grub.conf? > What do you have mdadm for? I don't have mdadm devices in this machine (it's a laptop with only one SSD, anyway). I don't know why mdadm is present on this machine, but it has "always" been, with no detrimental effects until possibly recently. Thanks, Toni
Bug#920547: Crashes every few hours
Hi Ben, On Mon, Jan 28, 2019 at 12:42:37AM +, Ben Hutchings wrote: > On Sat, 26 Jan 2019 20:03:49 + Toni wrote: > > Package: src:linux > > Version: 4.19.16-1 > > Severity: critical > > File: linux-image-4.19.0-2-amd64 > > Is this a new problem with version 4.19.16-1? Or did it happen with > earlier versions as well? it happened with the 4.18.* kernel as well. The machine came with Ubuntu and 4.13 preinstalled, but I wiped it as soon as I could and installed Debian. So I don't know if it would have worked with Ubuntu - the entire setup was not suitable for my purposes, but I thought that 4.9 might be too old for this hardware. However, the machine came with a 1.3 BIOS, which I updated to 1.6 and then to 1.7. I think, I had 4.18 together with 1.6 running, but closed the corresponding bug report when I noticed that both a newer kernel and a newer BIOS were available. Well, the situation compared has improved a little, compared to that, but it is still very bad. > When you say "data loss", are you talking about data in memory or > corruption of files that were saved and sync'd to disk? I mean, files on disk were destroyed. I noticed some because I use etckeeper with git, and suddenly, I could no longer see my update history because files in /etc/.git were corrupt to the point that no "git fsck" or "git gc" could resurrect the tree. > On x86 laptops thermal management is (by default) done by the system > firmware (BIOS and management engine code). If you didn't override > that, and yet the CPU overheats, this is the manufacturer's fault. Ok... In the BIOS, I set the corresponding parameter from "performance" to "normal", which I hoped would be a more conservative setting, to prevent exactly this problem. Cheers, Toni
Bug#815037: problem still present in Stretch and stretch-backports?
Hi, I am seeing this problem with linux-image-4.15.0-0.bpo.2-amd64 4.15.11-1~bpo9+1 amd64 and firmware-iwlwifi 20170823-1~bpo9+1, and with their counterparts from Stable on my XPS 13 from around 2013. FWIW, on some networks, I have no trouble connecting, but on others, it just won't work at all. I've tried this backport version after losing connectivity with the stable package. $ journalctl -b 0 | grep iwlwifi | head Apr 30 23:27:08 debian kernel: iwlwifi :01:00.0: can't disable ASPM; OS doesn't have ASPM control Apr 30 23:27:08 debian kernel: iwlwifi :01:00.0: firmware: direct-loading firmware iwlwifi-6000g2b-6.ucode Apr 30 23:27:08 debian kernel: iwlwifi :01:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm Apr 30 23:27:08 debian kernel: iwlwifi :01:00.0: CONFIG_IWLWIFI_DEBUG disabled Apr 30 23:27:08 debian kernel: iwlwifi :01:00.0: CONFIG_IWLWIFI_DEBUGFS disabled Apr 30 23:27:08 debian kernel: iwlwifi :01:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled Apr 30 23:27:08 debian kernel: iwlwifi :01:00.0: Detected Intel(R) Centrino(R) Advanced-N 6235 AGN, REV=0xB0 Apr 30 23:27:09 debian kernel: iwlwifi :01:00.0: Radio type=0x2-0x1-0x0 Apr 30 23:27:09 debian kernel: iwlwifi :01:00.0: Radio type=0x2-0x1-0x0 Apr 30 23:27:38 debian kernel: iwlwifi :01:00.0: Radio type=0x2-0x1-0x0 $ iwconfig wlan0 wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Frequency:5.22 GHz Access Point: Not-Associated Tx-Power=15 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Here's one such section from the logs, I get them every few seconds: Apr 30 23:43:30 debian kernel: [ 995.983609] ieee80211 phy0: Hardware restart was requested Apr 30 23:43:30 debian kernel: [ 995.996648] iwlwifi :01:00.0: Radio type=0x2-0x1-0x0 Apr 30 23:43:30 debian kernel: [ 996.297641] iwlwifi :01:00.0: Radio type=0x2-0x1-0x0 Apr 30 23:43:38 debian kernel: [ 1003.669572] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. Apr 30 23:43:38 debian kernel: [ 1003.669589] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1 Apr 30 23:43:38 debian kernel: [ 1003.669781] iwlwifi :01:00.0: Start IWL Error Log Dump: Apr 30 23:43:38 debian kernel: [ 1003.669789] iwlwifi :01:00.0: Status: 0x004C, count: 6 Apr 30 23:43:38 debian kernel: [ 1003.669797] iwlwifi :01:00.0: 0x0034 | NMI_INTERRUPT_WDG Apr 30 23:43:38 debian kernel: [ 1003.669803] iwlwifi :01:00.0: 0x00010564 | uPc Apr 30 23:43:38 debian kernel: [ 1003.669810] iwlwifi :01:00.0: 0x0001054E | branchlink1 Apr 30 23:43:38 debian kernel: [ 1003.669816] iwlwifi :01:00.0: 0x00010580 | branchlink2 Apr 30 23:43:38 debian kernel: [ 1003.669824] iwlwifi :01:00.0: 0xDBEA | interruptlink1 Apr 30 23:43:38 debian kernel: [ 1003.669831] iwlwifi :01:00.0: 0x0001CB38 | interruptlink2 Apr 30 23:43:38 debian kernel: [ 1003.669837] iwlwifi :01:00.0: 0x0002 | data1 Apr 30 23:43:38 debian kernel: [ 1003.669844] iwlwifi :01:00.0: 0x0703 | data2 Apr 30 23:43:38 debian kernel: [ 1003.669851] iwlwifi :01:00.0: 0x0002617C | line Apr 30 23:43:38 debian kernel: [ 1003.669858] iwlwifi :01:00.0: 0x11C0121E | beacon time Apr 30 23:43:38 debian kernel: [ 1003.669865] iwlwifi :01:00.0: 0x9B5B2DE2 | tsf low Apr 30 23:43:38 debian kernel: [ 1003.669871] iwlwifi :01:00.0: 0x0055 | tsf hi Apr 30 23:43:38 debian kernel: [ 1003.669876] iwlwifi :01:00.0: 0x | time gp1 Apr 30 23:43:38 debian kernel: [ 1003.669882] iwlwifi :01:00.0: 0x0070585B | time gp2 Apr 30 23:43:38 debian kernel: [ 1003.669889] iwlwifi :01:00.0: 0x | time gp3 Apr 30 23:43:38 debian kernel: [ 1003.669896] iwlwifi :01:00.0: 0x754312A8 | uCode version Apr 30 23:43:38 debian kernel: [ 1003.669905] iwlwifi :01:00.0: 0x00B0 | hw version Apr 30 23:43:38 debian kernel: [ 1003.669911] iwlwifi :01:00.0: 0x00484B00 | board version Apr 30 23:43:38 debian kernel: [ 1003.669918] iwlwifi :01:00.0: 0x0207001C | hcmd Apr 30 23:43:38 debian kernel: [ 1003.669924] iwlwifi :01:00.0: 0xA7863002 | isr0 Apr 30 23:43:38 debian kernel: [ 1003.669930] iwlwifi :01:00.0: 0x11898000 | isr1 Apr 30 23:43:38 debian kernel: [ 1003.669935] iwlwifi :01:00.0: 0x0E17 | isr2 Apr 30 23:43:38 debian kernel: [ 1003.669941] iwlwifi :01:00.0: 0x8543FCC0 | isr3 Apr 30 23:43:38 debian kernel: [ 1003.669947] iwlwifi :01:00.0: 0x | isr4 Apr 30 23:43:38 debian kernel: [ 1003.669954] iwlwifi :01:00.0: 0x00804110 | isr_pref Apr 30 23:43:38 debian kernel: [ 1003.669961] iwlwifi :01:00.0: 0x0002617C | wait_event Apr 30 23:43:38 debian kernel: [ 1003.669969] iwlwifi :01:00.0: 0x00B4 | l2p_control Apr 30 23:43:38 debian kernel: [ 1003.669976] iwlwifi :01:00.0: 0x00A4 | l2p_duration Apr 30 23:43:38 debian
Bug#841750: XPS13 Jessie->Stretch: No sound
Hi Ben, On Sat, Nov 19, 2016 at 11:04:07AM +, Ben Hutchings wrote: > Perhaps it depends on whether you reboot or start from power-off? I can't remember right now, but I think I tried both rebooting and starting from power-off. The latter would be one of the first things that come to mind... Cheers, --Toni++
Bug#841750: XPS13 Jessie->Stretch: No sound
Hi Adrian, On Sun, Oct 23, 2016 at 10:41:57AM +0300, Adrian Bunk wrote: > Control: reassign -1 src:linux > > On Sun, Oct 23, 2016 at 06:57:53AM +0800, Toni Mueller wrote: > > Package: upgrade-reports > > Severity: important > > recently, I felt the need to upgrade my XPS 13 laptop (2013 model?) from > > Jessie to Stretch, but have not had any sound ever since. > > > > To be more precise, I had no sound ever after trying the 4.7 backported > > kernel on Jessie, which was what originally prompted me to upgrade to > > Stretch. > >... > > thanks for your report. > > This sounds like a bug in the kernel, I'm moving it there. in the meantime, the problem was resolved. Short story: After booting the 4.x kernel for the first time, sound disappeared. I recently did a factory reset in the BIOS, and sound re-appeared. So yes, at this point, I also suspect that there is some problem with the kernel, but why this seemingly happens only on upgrade, I don't know. Cheers, --Toni++
Bug#730049: linux-image-3.12-1-amd64: kernel does not boot
Hi Ben,
On Thu, Jan 21, 2016 at 01:40:30AM +, Ben Hutchings wrote:
> On Thu, 2015-12-10 at 04:03 +, Ben Hutchings wrote:
> > Do you still see a failure to set up the RAID ("mdadm: No devices
> > listed in conf file were found") on some machines? Can you send the
> > /etc/mdadm.conf file from one of those?
>
> Please answer these questions, or we will eventually just close the bug.
I have no longer access to the relevant hardware, so it's imho ok to
close the bug. Sorry that I could not help more, and thanks for tracking
this.
Kind regards,
--Toni++
Bug#771661: machine is completely unusable
Hi Ben, On Sat, Dec 27, 2014 at 03:15:52PM +0100, Ben Hutchings wrote: Never mind, I've seen your later message with a complete log and I will reply to that. I haven't heard back from you, but in the meantime reformatted the machine from i386 (i686) to amd64, but also upgraded to testing, and the problem mostly went away. HTH, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150302121724.ga4...@lappi1.office.oeko.net
Bug#771661: machine is completely unusable
Hi Ben,
On Sat, Dec 27, 2014 at 02:39:06AM +0100, Ben Hutchings wrote:
1, Enable an emulated serial port for the VM, with output going to a
file.
I modified the VM to have:
serial type='file'
source path='/var/tmp/vm1-serial.log'/
target port='0'/
/serial
console type='file'
source path='/var/tmp/vm1-serial.log'/
target type='serial' port='0'/
/console
2. Enable a serial console on the kernel command line.
I added this to the end of the kernel boot line in the guest's
/boot/grub/grub.cfg:
serial console=ttyS00,115200
3. Set sysctl kernel.printk=7 (i.e. send all non-debug logging to the
console).
I set this in the guest's /etc/sysctl.cfg
4. Do whatever you have to do, to reproduce the hang.
All that is necessary is to say virsh start vm1.
I am confused because the output is really not that much more verbose
than the screnshots, but here you are:
[ 22.224014] INFO: rcu_sched self-detected stall on CPU { 1} (t=5251 jiffies
g=-153 c=-154 q=307)
[ 22.232010] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by
0, t=5252 jiffies, g=-153, c=-154, q=307)
[ 22.232010] CPU: 0 PID: 122 Comm: systemd-udevd Not tainted
3.16.0-0.bpo.4-686-pae #1 Debian 3.16.7-ckt2-1~bpo70+1
[ 22.232010] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 22.232010] task: f6c96560 ti: f6cd6000 task.ti: f6cd6000
[ 22.232010] Stack:
[ 22.232010] Call Trace:
[ 22.232010] Code: 00 d3 ff ff 80 e5 10 75 ee c1 e3 18 89 98 10 d3 ff ff 89
f0 09 d0 80 ce 04 83 fe 02 0f 44 c2 8b 15 c4 8c 61 c1 89 82 00 d3 ff ff 89 f8
50 9d 8d 74 26 00 8b 5d f4 8b 75 f8 8b 7d fc 89 ec 5d c3
[ 22.224014] CPU: 1 PID: 129 Comm: modprobe Not tainted
3.16.0-0.bpo.4-686-pae #1 Debian 3.16.7-ckt2-1~bpo70+1
[ 22.224014] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 22.224014] task: f6d23ab0 ti: f6d44000 task.ti: f6d44000
[ 22.224014] Stack:
[ 22.224014] Call Trace:
[ 22.224014] Code: d3 e2 03 50 04 ec 0f b6 c0 5d c3 89 f6 8d bc 27 00 00 00
00 55 89 e5 53 3e 8d 74 26 00 89 cb 0f b6 48 35 d3 e2 03 50 04 89 d8 ee 5b 5d
c3 8d b6 00 00 00 00 55 89 e5 3e 8d 74 26 00 0f b6 50 36
[ 22.224014] CPU: 1 PID: 129 Comm: modprobe Not tainted
3.16.0-0.bpo.4-686-pae #1 Debian 3.16.7-ckt2-1~bpo70+1
[ 22.224014] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 22.224014] task: f6d23ab0 ti: f6d44000 task.ti: f6d44000
[ 22.224014] Stack:
[ 22.224014] Call Trace:
[ 22.224014] Code: 00 d3 ff ff 80 e5 10 75 ee c1 e3 18 89 98 10 d3 ff ff 89
f0 09 d0 80 ce 04 83 fe 02 0f 44 c2 8b 15 c4 8c 61 c1 89 82 00 d3 ff ff 89 f8
50 9d 8d 74 26 00 8b 5d f4 8b 75 f8 8b 7d fc 89 ec 5d c3
[ 22.332011] CPU: 0 PID: 122 Comm: systemd-udevd Not tainted
3.16.0-0.bpo.4-686-pae #1 Debian 3.16.7-ckt2-1~bpo70+1
[ 22.332011] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 22.332011] task: f6c96560 ti: f6cd6000 task.ti: f6cd6000
[ 22.332011] Stack:
[ 22.332011] Call Trace:
[ 22.332011] Code: 5d e9 38 a0 c0 ff 90 8d b4 26 00 00 00 00 55 89 e5 3e 8d
74 26 00 ba 00 01 00 00 f0 66 0f c1 10 0f b6 ce 38 d1 75 04 5d c3 f3 90 0f b6
10 38 ca 75 f7 5d c3 8d 76 00 8d bc 27 00 00 00 00 55 89
[ 48.032012] BUG: soft lockup - CPU#0 stuck for 22s! [systemd-udevd:122]
[ 48.032012] CPU: 0 PID: 122 Comm: systemd-udevd Not tainted
3.16.0-0.bpo.4-686-pae #1 Debian 3.16.7-ckt2-1~bpo70+1
[ 48.032012] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 48.036010] BUG: soft lockup - CPU#1 stuck for 22s! [modprobe:129]
[ 48.036010] CPU: 1 PID: 129 Comm: modprobe Not tainted
3.16.0-0.bpo.4-686-pae #1 Debian 3.16.7-ckt2-1~bpo70+1
[ 48.036010] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 48.036010] task: f6d23ab0 ti: f6d44000 task.ti: f6d44000
[ 48.036010] Stack:
[ 48.036010] Call Trace:
[ 48.036010] Code: 00 00 8d bf 00 00 00 00 89 48 04 89 10 c3 8d 76 00 8d bc
27 00 00 00 00 83 ec 08 89 74 24 04 89 c6 89 1c 24 89 d3 8b 00 8b 56 04 f0 0f
c7 0e 75 fa 8b 1c 24 8b 74 24 04 83 c4 08 c3 8d b6 00 00
[ 48.032012] task: f6c96560 ti: f6cd6000 task.ti: f6cd6000
[ 48.032012] Stack:
[ 48.032012] Call Trace:
[ 48.032012] Code: 5d e9 38 a0 c0 ff 90 8d b4 26 00 00 00 00 55 89 e5 3e 8d
74 26 00 ba 00 01 00 00 f0 66 0f c1 10 0f b6 ce 38 d1 75 04 5d c3 f3 90 0f b6
10 38 ca 75 f7 5d c3 8d 76 00 8d bc 27 00 00 00 00 55 89
At this point, I shut the VM down because it did not seem to produce
any more useful information.
Kind regards,
--Toni++
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141227112034.ga11...@lappi1.office.oeko.net
Bug#771661: machine is completely unusable
Hi Ben, I tweaked it a bit, and now I get much more telling messages: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-0.bpo.4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.16.7-ckt2-1~bpo70+1 (2014-12-08) [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x6cbfdfff] usable [0.00] BIOS-e820: [mem 0x6cbfe000-0x6cbf] reserved [0.00] BIOS-e820: [mem 0xfeffc000-0xfeff] reserved [0.00] BIOS-e820: [mem 0xfffc-0x] reserved [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: KVM [0.00] e820: last_pfn = 0x6cbfe max_arch_pfn = 0x100 [0.00] PAT not supported by CPU. [0.00] found SMP MP-table at [mem 0x000f1e90-0x000f1e9f] mapped at [c00f1e90] [0.00] init_memory_mapping: [mem 0x-0x000f] [0.00] init_memory_mapping: [mem 0x3720-0x373f] [0.00] init_memory_mapping: [mem 0x3400-0x371f] [0.00] init_memory_mapping: [mem 0x0010-0x33ff] [0.00] init_memory_mapping: [mem 0x3740-0x375fdfff] [0.00] RAMDISK: [mem 0x361ac000-0x370cdfff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F1D10 14 (v00 BOCHS ) [0.00] ACPI: RSDT 0x6CBFE410 34 (v01 BOCHS BXPCRSDT 0001 BXPC 0001) [0.00] ACPI: FACP 0x6CBFFF80 74 (v01 BOCHS BXPCFACP 0001 BXPC 0001) [0.00] ACPI: DSDT 0x6CBFE450 001135 (v01 BOCHS BXPCDSDT 0001 BXPC 0001) [0.00] ACPI: FACS 0x6CBFFF40 40 [0.00] ACPI: SSDT 0x6CBFF6C0 00087A (v01 BOCHS BXPCSSDT 0001 BXPC 0001) [0.00] ACPI: APIC 0x6CBFF5D0 80 (v01 BOCHS BXPCAPIC 0001 BXPC 0001) [0.00] ACPI: HPET 0x6CBFF590 38 (v01 BOCHS BXPCHPET 0001 BXPC 0001) [0.00] 854MB HIGHMEM available. [0.00] 885MB LOWMEM available. [0.00] mapped low ram: 0 - 375fe000 [0.00] low ram: 0 - 375fe000 [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.00] kvm-clock: cpu 0, msr 0:375fd001, primary cpu clock [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] Normal [mem 0x0100-0x375fdfff] [0.00] HighMem [mem 0x375fe000-0x6cbfdfff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009efff] [0.00] node 0: [mem 0x0010-0x6cbfdfff] [0.00] Using APIC driver default [0.00] ACPI: PM-Timer IO Port: 0xb008 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [0.00] ACPI: IOAPIC (id[0x00] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 0, version 17, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) [0.00] Using ACPI (MADT) for SMP configuration information [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.00] smpboot: Allowing 2 CPUs, 0 hotplug CPUs [0.00] PM: Registered nosave memory: [mem 0x0009f000-0x0009] [0.00] PM: Registered nosave memory: [mem 0x000a-0x000e] [0.00] PM: Registered nosave memory: [mem 0x000f-0x000f] [0.00] e820: [mem 0x6cc0-0xfeffbfff] available for PCI devices [0.00] Booting paravirtualized kernel on KVM [0.00] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:2 nr_node_ids:1 [0.00] PERCPU: Embedded 14 pages/cpu @f75d8000 s35328 r0 d22016 u57344 [0.00] KVM setup async PF for cpu 0 [0.00] kvm-stealtime: cpu 0, msr 375db280 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 443568 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-0.bpo.4-686-pae root=UUID=c707415e-9478-46ac-b02e-2ac1c4a70087 ro vga=normal console=ttyS0 [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) [
Bug#771661: machine is completely unusable
Hi Ben, possibly unrelated, but neither the kernels of the Ubuntu installers for 12.04 and 14.04, nor the kernel for Fedora 21 installer, even boot on my VM. I reckoned that you might be interested, being a kernel hacker. CentOS 6.5 or OpenBSD 5.6 don't have a problem, though. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141227122135.gc11...@lappi1.office.oeko.net
Bug#771661: new vm, same problem
Hi Ben, I deleted the VM and created a completely new one, though on the same host, which I currently cannot change. Installing the linux-image-3.16.0-0.bpo.4-686-pae kernel results in no way to boot the VM with neither dracut from wheezy nor initramfs-tools from wheezy-backports. Please see the attached picture for details. The host cpu is basically maxed out during the time the VM is in this state.. Kind regards, --Toni++
Bug#771661: sample kernel strace
Hi,
the problem just re-occurred directly after booting the VM, even
preventing me from logging in. I will raise the severity in a separate
message:
Process 28101 attached - interrupt to quit
ppoll([{fd=15, events=POLLIN|POLLERR|POLLHUP}, {fd=13,
events=POLLIN|POLLERR|POLLHUP}, {fd=24, events=POLLIN|POLLERR|POLLHUP}, {fd=3,
events=POLLIN|POLLERR|POLLHUP}, {fd=5, events=POLLIN}, {fd=14, events=POLLIN},
{fd=4, events=POLLIN}], 7, {0, 201525089}, NULL, 8) = 0 (Timeout)
read(5, 0xbfed0a6c, 16) = -1 EAGAIN (Resource temporarily
unavailable)
clock_gettime(CLOCK_MONOTONIC, {1030038, 1150862}) = 0
poll([{fd=7, events=POLLOUT}], 1, 0)= 1 ([{fd=7, revents=POLLOUT|POLLHUP}])
clock_gettime(CLOCK_MONOTONIC, {1030038, 1243891}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030038, 1283002}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030038, 1316107}) = 0
gettimeofday({1418136114, 204054}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030038, 1386716}) = 0
gettimeofday({1418136114, 204119}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030038, 1448805}) = 0
ppoll([{fd=15, events=POLLIN|POLLERR|POLLHUP}, {fd=13,
events=POLLIN|POLLERR|POLLHUP}, {fd=24, events=POLLIN|POLLERR|POLLHUP}, {fd=3,
events=POLLIN|POLLERR|POLLHUP}, {fd=5, events=POLLIN}, {fd=14, events=POLLIN},
{fd=4, events=POLLIN}], 7, {0, 99900}, NULL, 8) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {1030039, 1598057}) = 0
poll([{fd=7, events=POLLOUT}], 1, 0)= 1 ([{fd=7, revents=POLLOUT|POLLHUP}])
clock_gettime(CLOCK_MONOTONIC, {1030039, 1685289}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030039, 1724749}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030039, 1757784}) = 0
gettimeofday({1418136115, 204496}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030039, 1829232}) = 0
gettimeofday({1418136115, 204566}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030039, 1890483}) = 0
ppoll([{fd=15, events=POLLIN|POLLERR|POLLHUP}, {fd=13,
events=POLLIN|POLLERR|POLLHUP}, {fd=24, events=POLLIN|POLLERR|POLLHUP}, {fd=3,
events=POLLIN|POLLERR|POLLHUP}, {fd=5, events=POLLIN}, {fd=14, events=POLLIN},
{fd=4, events=POLLIN}], 7, {0, 99900}, NULL, 8) = 1 ([{fd=24,
revents=POLLIN}], left {0, 996929065})
clock_gettime(CLOCK_MONOTONIC, {1030039, 4137977}) = 0
read(24,
\1\200\302\0\0\0\376T\0a\34\27\0BB\3\0\0\0\0\0\200\0\0'\23\266\334\375\0\0...,
69632) = 52
clock_gettime(CLOCK_MONOTONIC, {1030039, 4227304}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030039, 4260758}) = 0
gettimeofday({1418136115, 206994}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030039, 4322707}) = 0
gettimeofday({1418136115, 207060}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030039, 4388498}) = 0
ppoll([{fd=15, events=POLLIN|POLLERR|POLLHUP}, {fd=13,
events=POLLIN|POLLERR|POLLHUP}, {fd=24, events=POLLIN|POLLERR|POLLHUP}, {fd=3,
events=POLLIN|POLLERR|POLLHUP}, {fd=5, events=POLLIN}, {fd=14, events=POLLIN},
{fd=4, events=POLLIN}], 7, {0, 99600}, NULL, 8) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {1030040, 1563556}) = 0
poll([{fd=7, events=POLLOUT}], 1, 0)= 1 ([{fd=7, revents=POLLOUT|POLLHUP}])
clock_gettime(CLOCK_MONOTONIC, {1030040, 1751220}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 1833004}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 1971010}) = 0
gettimeofday({1418136116, 204956}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 2291023}) = 0
gettimeofday({1418136116, 205093}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 2426934}) = 0
ppoll([{fd=15, events=POLLIN|POLLERR|POLLHUP}, {fd=13,
events=POLLIN|POLLERR|POLLHUP}, {fd=24, events=POLLIN|POLLERR|POLLHUP}, {fd=3,
events=POLLIN|POLLERR|POLLHUP}, {fd=5, events=POLLIN}, {fd=14, events=POLLIN},
{fd=4, events=POLLIN}], 7, {0, 515708977}, NULL, 8) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {1030040, 518878711}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 518919009}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 518955187}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 519015949}) = 0
write(4, \1\0\0\0\0\0\0\0, 8) = 8
clock_gettime(CLOCK_MONOTONIC, {1030040, 519088444}) = 0
gettimeofday({1418136116, 721826}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 519159333}) = 0
gettimeofday({1418136116, 721896}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 519227358}) = 0
ppoll([{fd=15, events=POLLIN|POLLERR|POLLHUP}, {fd=13,
events=POLLIN|POLLERR|POLLHUP}, {fd=24, events=POLLIN|POLLERR|POLLHUP}, {fd=3,
events=POLLIN|POLLERR|POLLHUP}, {fd=5, events=POLLIN}, {fd=14, events=POLLIN},
{fd=4, events=POLLIN}], 7, {0, 48100}, NULL, 8) = 1 ([{fd=4,
revents=POLLIN}], left {0, 480995600})
clock_gettime(CLOCK_MONOTONIC, {1030040, 519350558}) = 0
write(5, \1\0\0\0\0\0\0\0, 8) = 8
read(4, \1\0\0\0\0\0\0\0, 512)= 8
clock_gettime(CLOCK_MONOTONIC, {1030040, 519451619}) = 0
clock_gettime(CLOCK_MONOTONIC, {1030040, 519484304}) = 0
gettimeofday({1418136116, 71}, NULL) = 0
ppoll([{fd=4, events=POLLIN|POLLERR|POLLHUP}], 1, {0, 0}, NULL, 8) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {1030040, 519712685}) = 0
Bug#771661: machine is completely unusable
severity 771661 grave thanks Hi, I guess the same would apply to #771602, but I would like to not go the extra five miles to reproduce it there. In any case, a kernel that maxes out the CPU immediately after start while doing nothing is not entirely production quality (although I have very good experiences with it in other settings). I'd likely be happy to produce more evidence if you can give me useful directions. Oh, as a side note: The VM thus maxed out cannot be shut down with $ virsh shutdown nameofvm but only with killing the kvm process. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141209145227.gb27...@lappi1.office.oeko.net
Bug#771661: machine is completely unusable
Hi Ben, On Tue, Dec 09, 2014 at 06:11:09PM +, Ben Hutchings wrote: Also, this is assigned to linux-image-3.16-0.bpo.3-686-pae but the screenshot you attached shows that package being newly installed. Therefore it is not the kernel you were running at the time you first saw this problem. Did you subsequently boot into that kernel? yes, the problem occurred with the 3.16-bpo kernel several times, basically each time I tried to run it, but so far never that early. Today the machine just locked up this way during or shortly after boot (I did not have a console for it when it happened). Should I create another screen shot when the problem happens next time? We would need a more complete kernel log. You could use an emulated serial console to get this. What exactly do you want? I mean, at this point I am almost confident to unfortunately reproduce the problem soonish. How much memory does this VM have? Does it have a swap file? memory unit='KiB'1638400/memory It has a swap partition, but no separate swap file. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141209225118.ga15...@lappi1.office.oeko.net
Bug#730049: 2x amd64 - now both don't boot at all
Hi, On Wed, Nov 20, 2013 at 08:27:36PM +0100, Toni Mueller wrote: this is the dmesg for the other machine which does not boot any of the 3.10 or 3.11 kernels at all, but under 3.2: today, the other machine (recognizable by the 945 instead of 964 cpu) refused to boot the 3.11 kernel as well. It now runs 3.2. It always stops at this line: [2.096047] Switching to clocksource tsc I suspect some kind of timing or driver problem. An attempt to compare their initrds did not yield anything useful to my (untrained) eye. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131122124633.ga11...@spruce.wiehl.oeko.net
Bug#671801: please backport the 3.3 wacom driver to 3.2 [afterthought]
Hi Jonathan, On Mon, May 14, 2012 at 04:54:50PM -0500, Jonathan Nieder wrote: Toni Mueller wrote: (using a patched kernel) in the meantime, I was able to perform an upgrade, and the tablet appears to work now: I can use the stylus, including the button that it has, with the new 0.12 X driver. Excellent. Thanks for the update. Kernel maintainers: please consider the 25-patch series from [1] for sid. It adds support for various new wacom tablets to the input subsystem, most notably the Bamboo PenTouch gen3. it occurred to me that I saw no obvious way to configure the tablet, so the only operating mode is to have the small, approximately A5-sized sensitive area represent the whole screen. Which makes using the tablet sort of difficult if you have a large screen resolution because the cursor jumps at every small move. It's sort of like a mouse with high accelleration. So while it technically works, I'm a bit doubtful about the usefulness of it - but then, I have no expectations. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120515092038.ga5...@spruce.wiehl.oeko.net
Bug#671801: please backport the 3.3 wacom driver to 3.2 [afterthought]
On Tue, May 15, 2012 at 02:58:52PM -0500, Jonathan Nieder wrote: Toni Mueller wrote: it occurred to me that I saw no obvious way to configure the tablet Don't gnome-control-center, kde-config-tablet, and xinput have support for tablets? I don't know, as I don't use these things. *nod* I vaguely remember programs like the GIMP and Krita automatically making tablets represent the canvas instead of the screen, but I'm not sure. Me neither. :/ Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120515210833.gg4...@spruce.wiehl.oeko.net
Bug#673083: linux-image-3.3.0-trunk-686-pae: unable to load KVM extension
Package: linux-2.6 Version: 3.3.4-1~experimental.1 Severity: important Hi, I have a problem loading KVM: # lsmod|grep kvm kvm 240621 0 # modprobe kvm_intel FATAL: Error inserting kvm_intel (/lib/modules/3.3.0-trunk-686-pae/kernel/arch/x86/kvm/kvm-intel.ko): Operation not supported # modprobe kvm_amd FATAL: Error inserting kvm_amd (/lib/modules/3.3.0-trunk-686-pae/kernel/arch/x86/kvm/kvm-amd.ko): Operation not supported # But my CPU should be able to do it: # egrep '^(flags.*(vmx|svm)|model name)' /proc/cpuinfo model name : AMD Phenom(tm) II X4 945 Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save model name : AMD Phenom(tm) II X4 945 Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save model name : AMD Phenom(tm) II X4 945 Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save model name : AMD Phenom(tm) II X4 945 Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock nrip_save Therefore, KVM runs like a dead snail on my machine. Didn't try Xen yet... Kind regards, --Toni++ -- Package-specific info: ** Version: Linux version 3.3.0-trunk-686-pae (Debian 3.3.4-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-4) ) #1 SMP Wed May 2 12:54:40 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.3.0-trunk-686-pae root=/dev/mapper/ev0-root ro root=/dev/mapper/ev0-root ro ** Not tainted ** Kernel log: [ 153.733778] Bluetooth: Core ver 2.16 [ 153.742581] NET: Registered protocol family 31 [ 153.747740] Bluetooth: HCI device and connection manager initialized [ 153.752916] Bluetooth: HCI socket layer initialized [ 153.758127] Bluetooth: L2CAP socket layer initialized [ 153.763195] Bluetooth: SCO socket layer initialized [ 153.933263] Bluetooth: RFCOMM TTY layer initialized [ 153.944450] Bluetooth: RFCOMM socket layer initialized [ 153.952750] Bluetooth: RFCOMM ver 1.11 [ 154.027012] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 154.035306] Bluetooth: BNEP filters: protocol multicast [ 155.166515] Ebtables v2.0 registered [ 155.245662] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 157.655480] drbd: initialized. Version: 8.3.11 (api:88/proto:86-96) [ 157.664126] drbd: srcversion: 0D2B62DEDB020A425130935 [ 157.672894] drbd: registered as block device major 147 [ 157.681610] drbd: minor_table @ 0xeb853d40 [14788.207717] tun: Universal TUN/TAP device driver, 1.6 [14788.207726] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [16181.480593] device vnet0 entered promiscuous mode [16181.488245] br0: port 2(vnet0) entered forwarding state [16181.488287] br0: port 2(vnet0) entered forwarding state [16181.601939] br0: port 2(vnet0) entered disabled state [16181.602978] br0: port 2(vnet0) entered disabled state [16181.603091] device vnet0 left promiscuous mode [16181.603098] br0: port 2(vnet0) entered disabled state [16254.527370] device vnet0 entered promiscuous mode [16254.528979] br0: port 2(vnet0) entered forwarding state [16254.528987] br0: port 2(vnet0) entered forwarding state [16263.552030] br0: port 2(vnet0) entered forwarding state [16320.995768] br0: port 2(vnet0) entered disabled state [16320.996868] br0: port 2(vnet0) entered disabled state [16320.996970] device vnet0 left promiscuous mode [16320.996978] br0: port 2(vnet0) entered disabled state [16580.856224] device vnet0 entered promiscuous mode [16580.871339] br0: port 2(vnet0) entered forwarding state [16580.871363] br0: port 2(vnet0) entered forwarding state [16581.002228] br0: port 2(vnet0) entered disabled state [16581.003222] br0: port 2(vnet0) entered disabled state [16581.003323] device vnet0 left promiscuous mode [16581.003330] br0: port 2(vnet0) entered
Bug#673083: unable to load KVM extension
Hi Jonathan, On Tue, May 15, 2012 at 05:04:38PM -0500, Jonathan Nieder wrote: Toni Mueller wrote: [21052.623069] kvm: disabled by bios I assume that's the cause. hrmpf, didn't see that one. Sorry. :( Will try with changed BIOS settings tomorrow. What make and model is this machine? It's a BTO machine from a local dealer. Does dmidecode know about it? Are there any BIOS settings relevant to virtualization? I don't know atm - usually, I don't touch the BIOS. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120515220908.gh4...@spruce.wiehl.oeko.net
Bug#671801: please backport the 3.3 wacom driver to 3.2
Hi Jonathan, On Sat, May 12, 2012 at 08:59:38AM -0500, Jonathan Nieder wrote: Toni Mueller wrote: the machine runs Squeeze and cannot be upgraded right now. So it's in the meantime, I was able to perform an upgrade, and the tablet appears to work now: I can use the stylus, including the button that it has, with the new 0.12 X driver. Ok, thanks. If you get a chance to try the driver from wheezy then: - if it isn't fixed, we can pursue this upstream. - if it is fixed, we can think about how to support these tablets well in squeeze, either by preparing a stable update or updating the package at backports.debian.org. Imho, the only missing part seems to be the kernel-level driver, which is not in the stock 3.2 kernel. The X driver is already fine. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120514214615.gh5...@spruce.wiehl.oeko.net
Bug#671801: please backport the 3.3 wacom driver to 3.2
Hi Jonathan, On Sun, May 06, 2012 at 11:37:15PM -0500, Jonathan Nieder wrote: # hardware support severity 671801 important tags 671801 + upstream patch moreinfo found 671801 linux-2.6/3.2.15-1 quit today, I was able to use the new kernel generated along the ways you outlined. It's a 3.2.16 plus your patches: ii linux-image-3.2.0-2-amd64 3.2.16-1a~test plus its prerequisites. A little too much for the upstream -stable trees, but these look like good changes for wheezy. The results are, as with the 3.3 kernel: * Using the tablet with one finger works, although very clumsily. It's more like trial-and-error to put the pointer somewhere, and tapping the tablet does not work at all - one has to press the appropriate button. * When I put the stylus close to the tablet, the blue LED changes its colour to white. But otherwise, the stylus has no effect whatsoever - can't use the mouse, nor press a button. * None of the more advanced functions of the tablet (pressure sensitivity, 3D, or multi-touch) work. I didn't made any effort to specifically configure the X server to work with this tablet, so those results only reflect what I got out of auto-detecting the device (ie, plugging it in and see what I get). That may or may not make any difference... but I'm no expert in this kind of stuff. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120512101622.gb5...@spruce.wiehl.oeko.net
Bug#671801: please backport the 3.3 wacom driver to 3.2
Hi, On Sat, May 12, 2012 at 07:46:44AM -0500, Jonathan Nieder wrote: What version of xserver-xorg-input-wacom do you have installed? Could you attach /var/log/Xorg.0.log? the machine runs Squeeze and cannot be upgraded right now. So it's ii xserver-xorg-input-wacom 0.10.5+20100416-1 I've attached the Xorg.0.log. The no such device error at the end of it is a result of my pulling the USB cable. Kind regards, --Toni++ X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.0.0-1-amd64 x86_64 Debian Current Operating System: Linux birch 3.2.0-2-amd64 #1 SMP Sat May 12 00:15:58 CEST 2012 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/ev0-root ro quiet Build Date: 29 October 2011 06:58:14PM xorg-server 2:1.7.7-14 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat May 12 12:00:33 2012 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c8a40 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 7 (--) PCI:*(0:1:5:0) 1002:9616:1043:8388 ATI Technologies Inc 760G [Radeon 3000] rev 0, Mem @ 0xd000/268435456, 0xfe9f/65536, 0xfe80/1048576, I/O @ 0xc000/256 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: record (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: dri (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: dri2 (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so (II) Module dri2: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.1.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (==) Matched ati as autoconfigured driver 0 (==) Matched vesa as autoconfigured driver 1 (==) Matched fbdev as autoconfigured driver 2 (==) Assigned the driver to the xf86ConfigLayout (II) LoadModule: ati (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so (II) Module ati: vendor=X.Org Foundation
Bug#631963: linux-image-3.0.0-rc4-686-pae: no sound out the rear plugs
Hi Takashi, On Thu, 30.06.2011 at 07:59:19 +0200, Takashi Iwai ti...@suse.de wrote: I guess this must be the new feature, Auto-Mute Mode. it turns out that you're right - I just had the opportunity to verify that. Thanks for the idea. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110701210656.4471.qm...@oak.oeko.net
Bug#631963: linux-image-3.0.0-rc4-686-pae: no sound out the rear plugs
Hi, On Wed, 29.06.2011 at 20:45:02 +0200, Toni Mueller supp...@oeko.net wrote: this first post is for the non-working kernel. The other kernel's information will follow tomorrow. this is the same info for the other kernel. HTH @Takashi: Thank you for your suggested workaround/change/fix. Will try it, but I'm not an expert. Will keep you posted. Kind regards, --Toni++ upload=truescript=truecardinfo= !! !!ALSA Information Script v 0.4.60 !! !!Script ran on: Thu Jun 30 09:10:20 UTC 2011 !!Linux Distribution !!-- Debian GNU/Linux 6.0 \n \l !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version !!Kernel Information !!-- Kernel release:2.6.38-bpo.2-686-bigmem Operating System: GNU/Linux Architecture: i686 Processor: unknown SMP Enabled: Yes !!ALSA Version !! Driver version: 1.0.23 Library version:1.0.23 Utilities version: 1.0.23 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! ESound Daemon: Installed - Yes (/usr/bin/esd) Running - No aRts: Installed - Yes (/usr/bin/artsd) Running - No !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe8f irq 16 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeaf4000 irq 19 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] !!Advanced information - PCI Vendor/Device/Subsystem ID's !! 00:14.2 0403: 1002:4383 Subsystem: 1043:841b -- 01:05.1 0403: 1002:970f Subsystem: 1043:843e !!Modprobe options (Sound related) !! snd-atiixp-modem: index=-2 snd-intel8x0m: index=-2 snd-via82xx-modem: index=-2 snd-pcsp: index=-2 snd-usb-audio: index=-2 !!Loaded sound module options !!-- !!Module: snd_hda_intel bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) position_fix : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 power_save : 0 power_save_controller : Y probe_mask : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 probe_only : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 single_cmd : N !!Module: snd_hda_intel bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null
Bug#631963: linux-image-3.0.0-rc4-686-pae: no sound out the rear plugs
Hi, On Wed, 29.06.2011 at 07:21:33 +0200, Takashi Iwai ti...@suse.de wrote: I'd definitely need alsa-info.sh outputs on both working and non-working kernels, i.e. on 2.6.38 and 3.0-rc4. this first post is for the non-working kernel. The other kernel's information will follow tomorrow. Kind regards, --Toni++ upload=truescript=truecardinfo= !! !!ALSA Information Script v 0.4.60 !! !!Script ran on: Wed Jun 29 18:43:33 UTC 2011 !!Linux Distribution !!-- Debian GNU/Linux 6.0 \n \l !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version !!Kernel Information !!-- Kernel release:3.0.0-rc4-686-pae Operating System: GNU/Linux Architecture: i686 Processor: unknown SMP Enabled: Yes !!ALSA Version !! Driver version: 1.0.24 Library version:1.0.23 Utilities version: 1.0.23 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! ESound Daemon: Installed - Yes (/usr/bin/esd) Running - No aRts: Installed - Yes (/usr/bin/artsd) Running - No !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe8f irq 16 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeaf4000 irq 19 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] !!Advanced information - PCI Vendor/Device/Subsystem ID's !! 00:14.2 0403: 1002:4383 Subsystem: 1043:841b -- 01:05.1 0403: 1002:970f Subsystem: 1043:843e !!Modprobe options (Sound related) !! snd-atiixp-modem: index=-2 snd-intel8x0m: index=-2 snd-via82xx-modem: index=-2 snd-pcsp: index=-2 snd-usb-audio: index=-2 !!Loaded sound module options !!-- !!Module: snd_hda_intel bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) position_fix : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 power_save : 0 power_save_controller : Y probe_mask : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 probe_only : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 single_cmd : N !!Module: snd_hda_intel bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
Bug#631802: linux-image-3.0.0-rc3-686-pae: kernel oops while running 'aptitude install' on a package
Package: linux-2.6 Version: 3.0.0~rc3-1~experimental.1 Severity: important Hi, today, while running 'aptitude install' on a package, the machine crashed hard, requiring me to press the reset button: Jun 27 10:32:12 spruce kernel: [ 6982.765536] [ cut here ] Jun 27 10:32:12 spruce kernel: [ 6982.765602] kernel BUG at /build/buildd-linux-2.6_3.0.0~rc3-1~experimental.1-i386-z_zgCg/linux-2.6-3.0.0~rc3/debian/build/source_i386_none/fs/inode.c:1368! Jun 27 10:32:12 spruce kernel: [ 6982.765777] invalid opcode: [#1] SMP Jun 27 10:32:12 spruce kernel: [ 6982.765837] Modules linked in: snd_hrtimer binfmt_misc drbd lru_cache cn ip6table_filter ip6_tables ebtable_nat ebtables bnep rfcomm bluetooth rfkill crc16 battery powernow_k8 mperf cpufreq_userspace cpufreq_conservative speedstep_lib cpufreq_powersave cpufreq_stats nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc nf_nat_ftp nf_nat_irc nf_conntrack_ftp nf_conntrack_irc ipt_MASQUERADE iptable_nat nf_nat ipt_LOG xt_limit xt_tcpudp xt_state nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc bridge stp deflate zlib_deflate ctr twofish_generic twofish_i586 twofish_common camellia serpent blowfish cast5 des_generic xcbc rmd160 sha512_generic sha1_generic hmac crypto_null af_key fuse loop kvm snd_hda_codec_hdmi snd_hda_codec_realtek snd_seq_midi snd_rawmidi snd_hda_intel snd_hda_codec snd_hwdep snd_seq_midi_event snd_pcm_oss snd_mixer_oss snd_seq snd_pcm snd_seq_ device snd_timer radeon snd soundcore Jun 27 10:32:12 spruce kernel: ttm drm_kms_helper drm wmi sp5100_tco button snd_page_alloc i2c_algo_bit processor power_supply i2c_piix4 pcspkr thermal_sys asus_atk0110 tpm_tis evdev tpm tpm_bios k10temp shpchp pci_hotplug i2c_core ext3 jbd mbcache sha256_generic cryptd aes_i586 aes_generic cbc dm_crypt dm_mod raid1 md_mod usbhid hid sg sd_mod sr_mod crc_t10dif cdrom ata_generic ohci_hcd pata_atiixp ahci libahci ehci_hcd libata usbcore scsi_mod e1000e r8169 mii [last unloaded: scsi_wait_scan] Jun 27 10:32:12 spruce kernel: [ 6982.767938] Jun 27 10:32:12 spruce kernel: [ 6982.767959] Pid: 9428, comm: rm Not tainted 3.0.0-rc3-686-pae #1 System manufacturer System Product Name/M4A88T-V EVO Jun 27 10:32:12 spruce kernel: [ 6982.768007] EIP: 0060:[c10dd30d] EFLAGS: 00010202 CPU: 1 Jun 27 10:32:12 spruce kernel: [ 6982.768007] EIP is at iput+0x13/0x113 Jun 27 10:32:12 spruce kernel: [ 6982.768007] EAX: eaa132d0 EBX: eaa132d0 ECX: c13fa8c0 EDX: f6d82be0 Jun 27 10:32:12 spruce kernel: [ 6982.768007] ESI: e9769914 EDI: eaa132d0 EBP: 0001 ESP: c015ff48 Jun 27 10:32:12 spruce kernel: [ 6982.768007] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Jun 27 10:32:12 spruce kernel: [ 6982.768007] Process rm (pid: 9428, ti=c015e000 task=c020e530 task.ti=c015e000) Jun 27 10:32:12 spruce kernel: [ 6982.768007] Stack: Jun 27 10:32:12 spruce kernel: [ 6982.768007] de901994 e9769914 eaa132d0 c10db424 de901994 de9019e0 eaa132d0 eaa132d0 Jun 27 10:32:12 spruce kernel: [ 6982.768007] c10db9e8 e8b41080 4010 c10ce29f e8b41088 de901994 f191fd80 e8b41080 Jun 27 10:32:12 spruce kernel: [ 6982.768007] f170bec0 c015e000 c10cb8e7 f170bec0 0005 090688d0 c10cb945 Jun 27 10:32:12 spruce kernel: [ 6982.768007] Call Trace: Jun 27 10:32:12 spruce kernel: [ 6982.768007] [c10db424] ? dentry_kill+0xd1/0xe6 Jun 27 10:32:12 spruce kernel: [ 6982.768007] [c10db9e8] ? dput+0xaf/0xb7 Jun 27 10:32:12 spruce kernel: [ 6982.768007] [c10ce29f] ? fput+0x185/0x19d Jun 27 10:32:12 spruce kernel: [ 6982.768007] [c10cb8e7] ? filp_close+0x54/0x5a Jun 27 10:32:12 spruce kernel: [ 6982.768007] [c10cb945] ? sys_close+0x58/0x85 Jun 27 10:32:12 spruce kernel: [ 6982.768007] [c12b9e5f] ? sysenter_do_call+0x12/0x28 Jun 27 10:32:12 spruce kernel: [ 6982.768007] Code: 3f c1 e8 ae 79 1d 00 b8 7c e2 3f c1 e8 c1 30 f7 ff 5e 5f 5b 5e 5f 5d c3 57 85 c0 56 53 89 c3 0f 84 02 01 00 00 f6 40 1c 40 74 04 0f 0b eb fe 8d 50 14 8d 40 68 e8 18 7c 07 00 85 c0 0f 84 e5 00 Jun 27 10:32:12 spruce kernel: [ 6982.768007] EIP: [c10dd30d] iput+0x13/0x113 SS:ESP 0068:c015ff48 Jun 27 10:32:12 spruce kernel: [ 6982.808070] ---[ end trace 5d90f1080d07b8fe ]--- Jun 27 10:32:33 spruce kernel: [ 7004.128099] 'IN-unknown:'IN=br0 OUT= MAC=01:00:5e:00:00:01:bc:ae:c5:ae:d2:21:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Jun 27 10:32:37 spruce kernel: [ 7008.300087] [ cut here ] Jun 27 10:32:37 spruce kernel: [ 7008.300108] WARNING: at /build/buildd-linux-2.6_3.0.0~rc3-1~experimental.1-i386-z_zgCg/linux-2.6-3.0.0~rc3/debian/build/source_i386_none/fs/fs-writeback.c:356 writeback_single_inode+0x5b/0x17b() Jun 27 10:32:37 spruce kernel: [ 7008.300118] Hardware name: System Product Name Jun 27 10:32:37 spruce kernel: [ 7008.300122] Modules linked in: snd_hrtimer binfmt_misc drbd lru_cache cn ip6table_filter ip6_tables
Bug#607534: linux-image-2.6.32-5-xen-686: crash upon calling 'startx'
Hi Ian, On Mon, 20.12.2010 at 10:38:46 +, Ian Campbell i...@hellion.org.uk wrote: This is likely the same underlying issue as 601341 and friends, which is that the Xen dom0 kernel does not currently fully support DRI/DRM graphics. thanks for the heads-up. Uhhh... Patches which resolve the issue have been posted upstream, but I don't know if the maintainer accepted them yet. The patches also need a non-trivial amount of backport to the kernel to be used in Squeeze. Hmmm. Would it be reasonable to switch to eg. 2.6.36 or higher? The problem appears to occur only with the entry in grub.cfg that I marked below, but I only tried the first and the marked entry (...XEN 4.0): That is the only entry which would result in you running under Xen so this is not surprising. Ok. Thank you for the explanation. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101220115557.10910.qm...@oak.oeko.net
Bug#607534: linux-image-2.6.32-5-xen-686: crash upon calling 'startx'
Hi, On Mon, 20.12.2010 at 12:42:50 +, Ian Campbell i...@hellion.org.uk wrote: Squeeze is frozen so there is no chance of moving to 2.6.36 for that, if that was your question. thanks, but that wasn't the question. The question was rather, whether I should be looking at an appropriate backport. The patches are not in 2.6.37-rc so 2.6.36 isn't helpful for a private kernel build either. I suppose the patches are likely to land in 2.6.38. Ok, I'll have an eye on that. Quality Control, n.: The process of testing one out of every 1,000 units coming off a production line to make sure that at least one out of 100 works. ;) Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101220181739.7426.qm...@oak.oeko.net
Bug#607534: linux-image-2.6.32-5-xen-686: crash upon calling 'startx'
Package: linux-2.6
Version: 2.6.32-29
Severity: normal
Tags: squeeze
Hi,
I wanted to start the GUI, but couldn't. After logging in, I usually say
'startx'. For this computer, which I have just installed, the command
resulted in the screen going blank, immediately followed by a hard reboot.
The problem appears to occur only with the entry in grub.cfg that I
marked below, but I only tried the first and the marked entry
(...XEN 4.0):
- cut
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=4
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 97da3623-a193-4fe3-a9ce-13f91f9123fc
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
### THE FOLLOWING ENTRY WORKS:
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 97da3623-a193-4fe3-a9ce-13f91f9123fc
echo'Loading Linux 2.6.32-5-xen-686 ...'
linux /vmlinuz-2.6.32-5-xen-686 root=/dev/mapper/ev0-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-xen-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 97da3623-a193-4fe3-a9ce-13f91f9123fc
echo'Loading Linux 2.6.32-5-xen-686 ...'
linux /vmlinuz-2.6.32-5-xen-686 root=/dev/mapper/ev0-root ro single
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-xen-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 97da3623-a193-4fe3-a9ce-13f91f9123fc
echo'Loading Linux 2.6.32-5-686 ...'
linux /vmlinuz-2.6.32-5-686 root=/dev/mapper/ev0-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 97da3623-a193-4fe3-a9ce-13f91f9123fc
echo'Loading Linux 2.6.32-5-686 ...'
linux /vmlinuz-2.6.32-5-686 root=/dev/mapper/ev0-root ro single
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### THE FOLLOWING ENTRY CAUSES THE CRASH:
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386'
--class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 97da3623-a193-4fe3-a9ce-13f91f9123fc
echo'Loading Linux 2.6.32-5-xen-686 ...'
multiboot /xen-4.0-i386.gz placeholder
module /vmlinuz-2.6.32-5-xen-686 placeholder root=/dev/mapper/ev0-root
ro quiet
echo'Loading initial ramdisk ...'
module /initrd.img-2.6.32-5-xen-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386
(recovery mode)' --class debian --class gnu-linux --class gnu --class os
--class xen {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 97da3623-a193-4fe3-a9ce-13f91f9123fc
echo'Loading Linux 2.6.32-5-xen-686 ...'
multiboot /xen-4.0-i386.gz placeholder
module /vmlinuz-2.6.32-5-xen-686 placeholder root=/dev/mapper/ev0-root
ro single
echo'Loading initial ramdisk ...'
module /initrd.img-2.6.32-5-xen-686
}
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END
Bug#606686: linux-image-2.6.32-5-686-bigmem: problem mounting CD, even as a loop device
Hi Ben, On Sat, 11.12.2010 at 02:06:59 +, Ben Hutchings b...@decadent.org.uk wrote: We need to see the *first* oops message. This... below I have included the first BUG message I could find, ...shows the D and W flags which indicate there were prior BUG and WARN messages. but the 'W' flag is already set: Dec 10 22:38:53 debian kernel: [1736183.557889] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] Dec 10 22:38:53 debian kernel: [1736183.557900] Info fld=0x509aa, ILI Dec 10 22:38:53 debian kernel: [1736183.557905] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track Dec 10 22:38:53 debian kernel: [1736183.557917] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 05 09 aa 00 00 01 00 Dec 10 22:38:53 debian kernel: [1736183.557937] end_request: I/O error, dev sr0, sector 1320616 Dec 10 22:38:53 debian kernel: [1736183.562482] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 10 22:38:53 debian kernel: [1736183.562494] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] Dec 10 22:38:53 debian kernel: [1736183.562505] Info fld=0x509a9, ILI Dec 10 22:38:53 debian kernel: [1736183.562510] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track Dec 10 22:38:53 debian kernel: [1736183.562522] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 05 09 a8 00 00 02 00 Dec 10 22:38:53 debian kernel: [1736183.562541] end_request: I/O error, dev sr0, sector 1320608 Dec 10 22:39:34 debian kernel: [1736225.147779] ISO 9660 Extensions: Microsoft Joliet Level 3 Dec 10 22:39:34 debian kernel: [1736225.296822] ISO 9660 Extensions: RRIP_1991A Dec 10 22:39:36 debian kernel: [1736227.289668] BUG: unable to handle kernel paging request at 4ced1b76 Dec 10 22:39:36 debian kernel: [1736227.289681] IP: [c1090d31] zone_watermark_ok+0x5c/0x9d Dec 10 22:39:36 debian kernel: [1736227.289700] *pdpt = 0edfa001 *pde = Dec 10 22:39:36 debian kernel: [1736227.289712] Oops: [#1] SMP Dec 10 22:39:36 debian kernel: [1736227.289720] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:14/ATK0110:00/hwmon/hwmon0/fan3_input Dec 10 22:39:36 debian kernel: [1736227.289732] Modules linked in: nls_utf8 isofs udf crc_itu_t xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 fuse ip6table_filter ip6_tables ebtable_nat ebtables binfmt_misc drbd lru_cache cn sco bnep rfcomm l2cap crc16 bluetooth rfkill kvm_amd kvm battery powernow_k8 cpufreq_userspace cpufreq_conservative cpufreq_powersave cpufreq_stats nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc nf_nat_ftp nf_nat_irc nf_conntrack_ftp nf_conntrack_irc ipt_MASQUERADE iptable_nat nf_nat ipt_LOG xt_limit xt_tcpudp xt_state nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc bridge stp deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish cast5 des_generic xcbc rmd160 sha1_generic hmac crypto_null af_key loop snd_hda_codec_via snd_hda_intel snd_hda_codec radeon ttm snd_hwdep drm_kms_helper snd_pcm_oss snd_mixer_oss drm snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_eve Dec 10 22:39:36 debian kernel: nt snd_seq snd_timer snd_seq_device i2c_algo_bit asus_atk0110 parport_pc evdev snd shpchp pcspkr i2c_piix4 processor button soundcore parport snd_page_alloc i2c_core pci_hotplug acpi_processor ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc dm_crypt dm_mod raid1 md_mod sg usbhid hid sr_mod cdrom sd_mod crc_t10dif ata_generic ohci_hcd pata_atiixp ahci e1000e libata thermal thermal_sys scsi_mod ehci_hcd r8169 usbcore nls_base mii [last unloaded: fuse] Dec 10 22:39:36 debian kernel: [1736227.289976] Dec 10 22:39:36 debian kernel: [1736227.289985] Pid: 13859, comm: ls Tainted: G W (2.6.32-5-xen-686 #1) System Product Name Dec 10 22:39:36 debian kernel: [1736227.289996] EIP: 0060:[c1090d31] EFLAGS: 00010246 CPU: 0 Dec 10 22:39:36 debian kernel: [1736227.290006] EIP is at zone_watermark_ok+0x5c/0x9d Dec 10 22:39:36 debian kernel: [1736227.290013] EAX: a2f41292 EBX: c11cd122 ECX: EDX: 90c35d5f Dec 10 22:39:36 debian kernel: [1736227.290021] ESI: EDI: EBP: 5356c789 ESP: e9ad3cf8 Dec 10 22:39:36 debian kernel: [1736227.290029] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Dec 10 22:39:36 debian kernel: [1736227.290038] Process ls (pid: 13859, ti=e9ad2000 task=c5ed9100 task.ti=e9ad2000) Dec 10 22:39:36 debian kernel: [1736227.290045] Stack: Dec 10 22:39:36 debian kernel: [1736227.290049] c5ac43c0 c102f844 c145ee1c e9ad3d68 000200d0 e9ad3ed0 Dec 10 22:39:36 debian kernel: [1736227.290065] 0 c1092879 a2f41292 0041 c5a84424 a2f41292 Dec 10 22:39:36 debian kernel: [1736227.290081] 0 000200d0 c13f57ec c5ac4418 c5ac441c Dec 10 22:39:36 debian kernel: [1736227.290098] Call Trace: Dec 10 22:39:36 debian kernel: [1736227.290109] [c102f844] ?
Bug#606686: linux-image-2.6.32-5-686-bigmem: problem mounting CD, even as a loop device
Package: linux-2.6 Version: 2.6.32-27 Severity: important Hello, I have a problem when I try to mount a CD image, regardless of whether it's a physical CD in a drive, or an ISO image on the file system. I've tried different images, to be sure. This is what I get (one sample): Dec 10 23:38:48 debian kernel: [1739778.791782] BUG: unable to handle kernel paging request at 4ced1b76 Dec 10 23:38:48 debian kernel: [1739778.791796] IP: [c1090d31] zone_watermark_ok+0x5c/0x9d Dec 10 23:38:48 debian kernel: [1739778.791814] *pdpt = 35e98001 *pde = Dec 10 23:38:48 debian kernel: [1739778.791826] Oops: [#4] SMP Dec 10 23:38:48 debian kernel: [1739778.791834] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:14/ATK0110:00/hwmon/hwmon0/fan3_input Dec 10 23:38:48 debian kernel: [1739778.791846] Modules linked in: nls_utf8 isofs udf crc_itu_t xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 fuse ip6table_filter ip6_ tables ebtable_nat ebtables binfmt_misc drbd lru_cache cn sco bnep rfcomm l2cap crc16 bluetooth rfkill kvm_amd kvm battery powernow_k8 cpufreq_userspace cpufreq_conservative cpufre q_powersave cpufreq_stats nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc nf_nat_ftp nf_nat_irc nf_conntrack_ftp nf_conntrack_irc ipt_MASQUERADE iptable_nat nf_nat ipt_L OG xt_limit xt_tcpudp xt_state nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc bridge stp deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish cast5 des_generic xcbc rmd160 sha1_generic hmac crypto_null af_key loop snd_hda_codec_via snd_hda_intel sn d_hda_codec radeon ttm snd_hwdep drm_kms_helper snd_pcm_oss snd_mixer_oss drm snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_eve Dec 10 23:38:48 debian kernel: nt snd_seq snd_timer snd_seq_device i2c_algo_bit asus_atk0110 parport_pc evdev snd shpchp pcspkr i2c_piix4 processor button soundcore parport snd_pag e_alloc i2c_core pci_hotplug acpi_processor ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc dm_crypt dm_mod raid1 md_mod sg usbhid hid sr_mod cdrom sd_mod crc_t10dif ata_g eneric ohci_hcd pata_atiixp ahci e1000e libata thermal thermal_sys scsi_mod ehci_hcd r8169 usbcore nls_base mii [last unloaded: fuse] Dec 10 23:38:48 debian kernel: [1739778.792097] Dec 10 23:38:48 debian kernel: [1739778.792106] Pid: 22347, comm: ls Tainted: G D W (2.6.32-5-xen-686 #1) System Product Name Dec 10 23:38:48 debian kernel: [1739778.792117] EIP: 0060:[c1090d31] EFLAGS: 00010246 CPU: 0 Dec 10 23:38:48 debian kernel: [1739778.792127] EIP is at zone_watermark_ok+0x5c/0x9d Dec 10 23:38:48 debian kernel: [1739778.792135] EAX: a2f41292 EBX: c11cd122 ECX: EDX: 90c35d5f Dec 10 23:38:48 debian kernel: [1739778.792142] ESI: EDI: EBP: 5356c789 ESP: c7cf3cf8 Dec 10 23:38:48 debian kernel: [1739778.792150] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Dec 10 23:38:48 debian kernel: [1739778.792160] Process ls (pid: 22347, ti=c7cf2000 task=f5854c80 task.ti=c7cf2000) Dec 10 23:38:48 debian kernel: [1739778.792166] Stack: Dec 10 23:38:48 debian kernel: [1739778.792171] 0003 f6e1852c f6dece00 c7cf3d68 000200d0 c7cf3ed0 Dec 10 23:38:48 debian kernel: [1739778.792186] 0 c1092879 a2f41292 0041 c5a063e8 f6dece00 a2f41292 Dec 10 23:38:48 debian kernel: [1739778.792203] 0 000200d0 c13f57ec c1056a46 c10264d1 8000 0003 Dec 10 23:38:48 debian kernel: [1739778.792220] Call Trace: Dec 10 23:38:48 debian kernel: [1739778.792232] [c1092879] ? get_page_from_freelist+0xc0/0x3c7 Dec 10 23:38:48 debian kernel: [1739778.792244] [c1056a46] ? queue_lock+0x44/0x49 Dec 10 23:38:48 debian kernel: [1739778.792256] [c10264d1] ? kmap_atomic_prot+0xd7/0xfc Dec 10 23:38:48 debian kernel: [1739778.792267] [c1026360] ? kunmap_atomic+0x48/0x57 Dec 10 23:38:48 debian kernel: [1739778.792277] [c11cd122] ? pci_hp_diva_setup+0x0/0x6b Dec 10 23:38:48 debian kernel: [1739778.792289] [c1092e41] ? __alloc_pages_nodemask+0xf3/0x4e0 Dec 10 23:38:48 debian kernel: [1739778.792299] [c11cd122] ? pci_hp_diva_setup+0x0/0x6b Dec 10 23:38:48 debian kernel: [1739778.792309] [c11cd122] ? pci_hp_diva_setup+0x0/0x6b Dec 10 23:38:48 debian kernel: [1739778.792322] [f8262035] ? isofs_lookup+0x35/0x3e4 [isofs] Dec 10 23:38:48 debian kernel: [1739778.792332] [c1094e7c] ? activate_page+0xa8/0xd1 Dec 10 23:38:48 debian kernel: [1739778.792344] [c10c8e2c] ? d_alloc+0x1b/0x154 Dec 10 23:38:48 debian kernel: [1739778.792355] [c10c8f31] ? d_alloc+0x120/0x154 Dec 10 23:38:48 debian kernel: [1739778.792364] [c10c1a71] ? do_lookup+0xa6/0x116 Dec 10 23:38:48 debian kernel: [1739778.792375] [c10c22e0] ? __link_path_walk+0x4b7/0x5de Dec 10 23:38:48 debian kernel: [1739778.792385] [c10c25bd] ? path_walk+0x4f/0xa3 Dec 10 23:38:48 debian kernel: [1739778.792395]
Bug#517449: problem also occurs on 2.6.32
Hi, I have the almost latest of 2.6.32-bpo.5-amd64 (2.6.32-21~bpo50+1), and the problem occured to me several times today. Oct 4 12:22:23 debian kernel: [1963080.712134] INFO: task sync:18607 blocked for more than 120 seconds. Oct 4 12:22:23 debian kernel: [1963080.712138] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 4 12:22:23 debian kernel: [1963080.712141] sync D 0 18607 18591 0x Oct 4 12:22:23 debian kernel: [1963080.712145] 814591f0 0086 88009c6bbe30 Oct 4 12:22:23 debian kernel: [1963080.712150] f9e0 88009c6bbfd8 00015780 Oct 4 12:22:23 debian kernel: [1963080.712153] 00015780 88011d78f100 88011d78f3f8 810402dc Oct 4 12:22:23 debian kernel: [1963080.712157] Call Trace: Oct 4 12:22:23 debian kernel: [1963080.712166] [8110658f] ? bdi_sched_wait+0x0/0xe Oct 4 12:22:23 debian kernel: [1963080.712170] [81106598] ? bdi_sched_wait+0x9/0xe Oct 4 12:22:23 debian kernel: [1963080.712174] [812f81d5] ? __wait_on_bit+0x41/0x70 Oct 4 12:22:23 debian kernel: [1963080.712177] [8110658f] ? bdi_sched_wait+0x0/0xe Oct 4 12:22:23 debian kernel: [1963080.712180] [812f826f] ? out_of_line_wait_on_bit+0x6b/0x77 Oct 4 12:22:23 debian kernel: [1963080.712184] [810638fc] ? wake_bit_function+0x0/0x23 Oct 4 12:22:23 debian kernel: [1963080.712188] [81106610] ? sync_inodes_sb+0x73/0x12a Oct 4 12:22:23 debian kernel: [1963080.712191] [8110a175] ? __sync_filesystem+0x4b/0x70 Oct 4 12:22:23 debian kernel: [1963080.712194] [8110a234] ? sync_filesystems+0x9a/0xe3 Oct 4 12:22:23 debian kernel: [1963080.712197] [8110a2c2] ? sys_sync+0x1c/0x2e Oct 4 12:22:23 debian kernel: [1963080.712202] [81010b42] ? system_call_fastpath+0x16/0x1b Oct 4 12:24:22 debian kernel: [1963200.712565] INFO: task sync:18607 blocked for more than 120 seconds. Oct 4 12:24:22 debian kernel: [1963200.712569] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 4 12:24:22 debian kernel: [1963200.712572] sync D 0 18607 18591 0x Oct 4 12:24:22 debian kernel: [1963200.712577] 814591f0 0086 88009c6bbe30 Oct 4 12:24:22 debian kernel: [1963200.712581] f9e0 88009c6bbfd8 00015780 Oct 4 12:24:22 debian kernel: [1963200.712585] 00015780 88011d78f100 88011d78f3f8 810402dc Oct 4 12:24:22 debian kernel: [1963200.712588] Call Trace: Oct 4 12:24:22 debian kernel: [1963200.712598] [8110658f] ? bdi_sched_wait+0x0/0xe Oct 4 12:24:22 debian kernel: [1963200.712601] [81106598] ? bdi_sched_wait+0x9/0xe Oct 4 12:24:22 debian kernel: [1963200.712606] [812f81d5] ? __wait_on_bit+0x41/0x70 Oct 4 12:24:22 debian kernel: [1963200.712609] [8110658f] ? bdi_sched_wait+0x0/0xe Oct 4 12:24:22 debian kernel: [1963200.712613] [812f826f] ? out_of_line_wait_on_bit+0x6b/0x77 Oct 4 12:24:22 debian kernel: [1963200.712616] [810638fc] ? wake_bit_function+0x0/0x23 Oct 4 12:24:22 debian kernel: [1963200.712620] [81106610] ? sync_inodes_sb+0x73/0x12a Oct 4 12:24:22 debian kernel: [1963200.712623] [8110a175] ? __sync_filesystem+0x4b/0x70 Oct 4 12:24:22 debian kernel: [1963200.712626] [8110a234] ? sync_filesystems+0x9a/0xe3 Oct 4 12:24:22 debian kernel: [1963200.712629] [8110a2c2] ? sys_sync+0x1c/0x2e Oct 4 12:24:22 debian kernel: [1963200.712634] [81010b42] ? system_call_fastpath+0x16/0x1b Oct 4 12:26:22 debian kernel: [1963320.712059] INFO: task sync:18607 blocked for more than 120 seconds. Oct 4 12:26:22 debian kernel: [1963320.712064] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 4 12:26:22 debian kernel: [1963320.712066] sync D 0 18607 18591 0x Oct 4 12:26:22 debian kernel: [1963320.712071] 814591f0 0086 88009c6bbe30 Oct 4 12:26:22 debian kernel: [1963320.712075] f9e0 88009c6bbfd8 00015780 Oct 4 12:26:22 debian kernel: [1963320.712079] 00015780 88011d78f100 88011d78f3f8 810402dc Oct 4 12:26:22 debian kernel: [1963320.712083] Call Trace: Oct 4 12:26:22 debian kernel: [1963320.712092] [8110658f] ? bdi_sched_wait+0x0/0xe Oct 4 12:26:22 debian kernel: [1963320.712096] [81106598] ? bdi_sched_wait+0x9/0xe Oct 4 12:26:22 debian kernel: [1963320.712100] [812f81d5] ? __wait_on_bit+0x41/0x70 Oct 4 12:26:22 debian kernel: [1963320.712103] [8110658f] ? bdi_sched_wait+0x0/0xe Oct 4 12:26:22 debian kernel: [1963320.712106] [812f826f] ? out_of_line_wait_on_bit+0x6b/0x77
Bug#579125: linux-headers-2.6.32-4-amd64: problem initializing LSI controller
Hi Moritz, On Tue, 06.07.2010 at 01:16:18 +0200, Moritz Muehlenhoff j...@inutil.org wrote: tags 579125 moreinfo thanks On Sun, Apr 25, 2010 at 04:38:16PM +0200, Toni Mueller wrote: Package: linux-headers-2.6.32-4-amd64 Version: 2.6.32-11~bpo50+1 Severity: normal Hi, I'm not quite sure that this is the right package to report against. Please reassign as you see fit. [...] This renders the card unusable. This seems to have been fixed in 2.6.32.12, which we pulled in upload 2.6.32-12: commit 3def5de896ab77232d1cb35fa63dbf627d1db328 Author: Kashyap, Desai kashyap.de...@lsi.com Date: Wed Oct 7 11:27:40 2009 +0530 mptspi: Fix for incorrect data underrun errata Could you try this kernel and see verify it's fixed there? I've now booted ii linux-image-2.6.32-bpo.5-amd64 2.6.32-15~bpo50+1Linux 2.6.32 for 64-bit PCs and get this in my /var/log/dmesg: [ 23.172818] [ cut here ] [ 23.172871] WARNING: at /tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/page_alloc.c:1806 __alloc_pages_nodemask+0x167/0x5d0() [ 23.172930] Hardware name: System Product Name [ 23.172972] Modules linked in: pata_amd sata_nv usbhid hid mptspi mptscsih mptbase scsi_transport_spi e1000e forcedeth firewire_ohci ata_generic firewire_core crc_itu_t ohci_hcd ehci_hcd libata usbcore nls_base scsi_mod thermal fan thermal_sys [ 23.173797] Pid: 760, comm: scsi_scan_9 Not tainted 2.6.32-bpo.5-amd64 #1 [ 23.173842] Call Trace: [ 23.173886] [810b97cb] ? __alloc_pages_nodemask+0x167/0x5d0 [ 23.173932] [810b97cb] ? __alloc_pages_nodemask+0x167/0x5d0 [ 23.173979] [8104dc40] ? warn_slowpath_common+0x77/0xa3 [ 23.174025] [810b97cb] ? __alloc_pages_nodemask+0x167/0x5d0 [ 23.174074] [81015af6] ? dma_generic_alloc_coherent+0x9a/0x120 [ 23.174124] [a010a3e5] ? mptspi_write_spi_device_pg1+0xa1/0x1ce [mptspi] [ 23.174179] [811965b6] ? __bitmap_weight+0x3a/0x7e [ 23.174227] [a010a576] ? mptspi_write_width+0x64/0x69 [mptspi] [ 23.174275] [a010adb5] ? mptspi_target_alloc+0x18c/0x1a1 [mptspi] [ 23.174327] [a001fd47] ? scsi_alloc_target+0x1e5/0x260 [scsi_mod] [ 23.174376] [a0020fa5] ? __scsi_scan_target+0x5a/0x593 [scsi_mod] [ 23.174423] [8100f5e7] ? __switch_to+0xd0/0x297 [ 23.174471] [a002152b] ? scsi_scan_channel+0x4d/0x78 [scsi_mod] [ 23.174520] [a0021633] ? scsi_scan_host_selected+0xdd/0x11d [scsi_mod] [ 23.174577] [a00216e4] ? do_scan_async+0x0/0x13a [scsi_mod] [ 23.174625] [a00216fa] ? do_scan_async+0x16/0x13a [scsi_mod] [ 23.174674] [a00216e4] ? do_scan_async+0x0/0x13a [scsi_mod] [ 23.174720] [81064819] ? kthread+0x79/0x81 [ 23.174765] [81011baa] ? child_rip+0xa/0x20 [ 23.174810] [810647a0] ? kthread+0x0/0x81 [ 23.174854] [81011ba0] ? child_rip+0x0/0x20 [ 23.174898] ---[ end trace 131c10636b3743aa ]--- This doesn't look comforting. I'm also under the impression that the bug should be assigned to linux-image instead of linux-headers... right? Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100718181804.14495.qm...@oak.oeko.net
Bug#583870: Acknowledgement (linux-image-2.6.26-2-686: inconsistencies in ext3 file systems)
Hi, the problem only surfaced when the machine did not come up after an attempt to reboot (shutdown -r now). Trying to check the affected file system yields tons of these (almost 2000 lines): # fsck -p /dev/mapper/uv0-srv fsck 1.41.3 (12-Oct-2008) /dev/mapper/uv0-srv contains a file system with errors, check forced. /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (23) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (23) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (23) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (37) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (37) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (37) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (47) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (47) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (47) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (70) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (70) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (70) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (83) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (83) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (83) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (87) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (87) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (87) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (113) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (113) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (113) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (137) has invalid depth (2) ... /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (7580) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (7585) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (7585) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (7585) not referenced /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (7605) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (7605) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (7605) not referenced /dev/mapper/uv0-srv: Invalid HTREE directory inode 20742394 (/qmailscan/archives/new). /dev/mapper/uv0-srv: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100531182702.11771.qm...@oak.oeko.net
Bug#583870: Acknowledgement (linux-image-2.6.26-2-686: inconsistencies in ext3 file systems)
Hi, On Mon, 31.05.2010 at 20:27:02 +0200, Toni Mueller supp...@oeko.net wrote: the problem only surfaced when the machine did not come up after an attempt to reboot (shutdown -r now). Trying to check the affected file system yields tons of these (almost 2000 lines): # fsck -p /dev/mapper/uv0-srv fsck 1.41.3 (12-Oct-2008) /dev/mapper/uv0-srv contains a file system with errors, check forced. /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) has invalid depth (2) /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) has bad max hash /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node (5) not referenced it turns out that only one directory was affected. This directory contains 488984 files. I don't think that having many files in a directory should be an error, only (possibly) a performance problem. But in no case should the file system become corrupted, imho. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100531184249.12659.qm...@oak.oeko.net
Bug#579126: linux-headers-2.6.32-4-amd64: Need NFS support
Package: linux-headers-2.6.32-4-amd64 Version: 2.6.32-11~bpo50+1 Severity: normal Hi, I'd like to use this kernel on an NFS server, but although the configuration file (/boot/config-2.6.32-bpo.4-amd64) mentions NFS being a module, I get: # /etc/init.d/nfs-kernel-server start Not starting NFS kernel daemon: no support in current kernel. (warning). Consequently, I also can't see my exported file systems: # showmount -e portmap getport: RPC: Success # This is quite confusing, as I also get: # lsmod|grep nfs nfsd 252966 2 exportfs3138 1 nfsd nfs 239738 0 lockd 57411 2 nfsd,nfs fscache29562 1 nfs nfs_acl 2031 2 nfsd,nfs auth_rpcgss33396 2 nfsd,nfs sunrpc160727 6 nfsd,nfs,lockd,nfs_acl,auth_rpcgss # which suggests that all required NFS modules are loaded. /etc/init.d/nfs-common starts without a problem, but I don't see much in the process list, and only this with rpcinfo: # rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 3910022 tcp962 sgi_fam 1000241 udp 43620 status 1000241 tcp 52123 status FWIW, NFS worked fine with 2.6.26. Kind regards, --Toni++ -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates'), (450, 'testing'), (250, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-bpo.4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100425144555.6231.55040.report...@birch.oeko.net
Bug#552142: Acknowledgement (linux-image-2.6.26-2-686: machine hangs with nf_conntrack: table full, dropping packet - needs hard reboot)
On Sat, 24.10.2009 at 09:28:22 +0200, Bastian Blank wa...@debian.org wrote: The buckets are created during module loading. But /etc/sysctl.conf is evaluated earlier. Aren't you seeing errors about unknown keys during boot? I'll have to check that, probably RSN, but in the meantime, I got confused by your explanation and my tour of the file system. While it was counter-intuitive right from the start that modules should be loaded after sysctl tried to use them, I see this in /etc/rcS.d: S20module-init-tools S30procps S30procps is the script where /etc/sysctl.conf gets evaluated, so it seems to me that /etc/sysctl.conf already gets evaluated *after*, not before, modules were loaded. -- Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552142: Acknowledgement (linux-image-2.6.26-2-686: machine hangs with nf_conntrack: table full, dropping packet - needs hard reboot)
On Sat, 24.10.2009 at 09:28:22 +0200, Bastian Blank wa...@debian.org wrote: The buckets are created during module loading. But /etc/sysctl.conf is evaluated earlier. Aren't you seeing errors about unknown keys during boot? No, I didn't, or at least not in any of the system's logs. But I also didn't see any traces of sysctl being executed, and I'm a bit confused about how, or why, sysctl runs that early. I found messages about the loading of the nf_conntrack module, with the 32k max buckets. So you suggest that I should make that number be a module's parameter? -- Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552142: Acknowledgement (linux-image-2.6.26-2-686: machine hangs with nf_conntrack: table full, dropping packet - needs hard reboot)
On Sat, 24.10.2009 at 12:48:05 +0200, Bastian Blank wa...@debian.org wrote: On Sat, Oct 24, 2009 at 12:31:35PM +0200, Toni Mueller wrote: On Sat, 24.10.2009 at 09:28:22 +0200, Bastian Blank wa...@debian.org wrote: Aren't you seeing errors about unknown keys during boot? No, I didn't, or at least not in any of the system's logs. This is sent to /dev/console, not the log. Well, then I might not have seen it, but I can try to reproduce the situation. Isn't there a way to capture such messages in the kernel's log? -- Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552142: Acknowledgement (linux-image-2.6.26-2-686: machine hangs with nf_conntrack: table full, dropping packet - needs hard reboot)
Hi, I just wanted to add: Despite my having this: $ grep track /etc/sysctl.conf net.ipv4.netfilter.ip_conntrack_max = 485760 I found this after reboot: $ cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max 32768 I had to manually set the value: # sysctl -w net.ipv4.netfilter.ip_conntrack_max=485760 net.ipv4.netfilter.ip_conntrack_max = 485760 After that, the desired value is being displayed: $ cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max 485760 I'm a bit confused as to why the wrong value gets set at boot time, but it doesn't really improve on the situation... I've checked my other values from /etc/sysctl.conf, and they get set correctly. What gives? Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552142: Acknowledgement (linux-image-2.6.26-2-686: machine hangs with nf_conntrack: table full, dropping packet - needs hard reboot)
Hi, On Sat, 24.10.2009 at 01:38:30 +0100, Ben Hutchings b...@decadent.org.uk wrote: On Fri, 2009-10-23 at 19:27 +0200, Toni Mueller wrote: $ grep track /etc/sysctl.conf net.ipv4.netfilter.ip_conntrack_max = 485760 $ cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max 32768 Perhaps some other init script is changing it. I thought so as well, but a grep -rF 32768 /etc as root didn't yield a hit. That seems to leave the possibility that the value is hardcoded somewhere else... Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532861: problem with initrd or module building?
Hi, I've now verified that the machine works with 2.6.29 from lenny-backports. I'd rather move back to a release kernel, however. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#442508: coreutils: dd demolishes my computer
Hi, On Mon, 17.09.2007 at 20:04:24 -0400, Michael Stone [EMAIL PROTECTED] wrote: I'm going to reassign this to linux-image. The basic problem seems to be the loss of responsiveness, which is probably caused by excessive amounts of large block size IO on the encrypted volume. There's a possible issue with the OOM killer. FWIW, today I also saw OOM killer in (broken?) action. Imho, OOM killer should only trigger if there's at least either no more RAM to work with, and note this in the syslog, or when swap is exhausted. My kern.log has this, with the time stamp and hostname removed: DMA: 465*4kB 17*8kB 1*16kB 1*32kB 1*64kB 0*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 5948kB DMA32: empty Normal: empty HighMem: empty Swap cache: add 2195725, delete 2046650, find 782418/975703, race 1+47 Free swap = 2489952kB Total swap = 4194296kB Free swap: 2489952kB 483649 pages of RAM 14999 reserved pages 70 pages shared 149071 pages swap cached Unfortunately, I can't make too much out of these numbers. Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442508: coreutils: dd demolishes my computer
Hi Mike, On Mon, 17.09.2007 at 20:04:24 -0400, Michael Stone [EMAIL PROTECTED] wrote: there's nothing especially unique in dd that would demolish a computer. there's still the difference in behaviour between dd and cp, the latter causing no such problems. With demolish I wanted to say that it really breaks the regular system's operation, and that it required me to reboot the machine, which is a shame, imho. Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#377959: problem exists also in 2.6.17.6
Hi, On Tue, 16.01.2007 at 16:08:09 +0100, maximilian attems [EMAIL PROTECTED] wrote: how is linux image 2.6.18 performing? well... I didn't specifically check (and also forgot about this bug), but 2.6.18 is reasonably fast, or at least fast enough that I don't have too many problems with it. Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#377959: problem exists also in 2.6.17.6
Hello, I just created a 2.6.17.6 kernel (patch as of yesterday), and tried again, with much the same results. So, I suspect it's somewhere in the guts of the 2.6.17 kernel - switching back to 2.6.16 also brings performance back to acceptable levels (already included in the report). Should I report this bug upstream? Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#377959: linux-image-2.6.17-1-686: abysmal disk throughput
Package: linux-image-2.6.17-1-686 Version: 2.6.17-2 Severity: important Hello, I have a severe problem running this kernel in that it brings my computer to a crawl, compared to the 2.6.16-1-686-smp kernel I was running before, and am running again until this problem is fixed. The dmesg as created by the 2.6.16 kernel is included below, and you can see that this machine should be reasonably fast (it is, under older 2.6.x kernels). But actual performance looks like this: Starting X (fvwm): some 5 minutes instead of some 10-20 seconds baz commit, worth 1 revision and some 100KB data in some 10-15 small files (ie, nothing): around 7 minutes instead of 5 seconds Unpacking a small tarball (273 KB, psycopg 2.0.2): ~1 file per second and so forth In other words, this kernel makes the machine unusable for me. This is the dmesg of the machine, as created by the 2.6.16 kernel I'm running: Linux version 2.6.16-1-686-smp (Debian 2.6.16-12) ([EMAIL PROTECTED]) (gcc version 4.0.4 20060422 (prerelease) (Debian 4.0.3-2)) #2 SMP Thu May 4 18:28:53 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - 3ffb (usable) BIOS-e820: 3ffb - 3ffc (ACPI data) BIOS-e820: 3ffc - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff7c - 0001 (reserved) 0MB HIGHMEM available. 1023MB LOWMEM available. On node 0 totalpages: 262064 DMA zone: 4096 pages, LIFO batch:0 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 257968 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:0 DMI 2.3 present. ACPI: RSDP (v000 ACPIAM) @ 0x000f8db0 ACPI: RSDT (v001 A M I OEMRSDT 0x11000503 MSFT 0x0097) @ 0x3ffb ACPI: FADT (v002 A M I OEMFACP 0x11000503 MSFT 0x0097) @ 0x3ffb0200 ACPI: MADT (v001 A M I OEMAPIC 0x11000503 MSFT 0x0097) @ 0x3ffb0390 ACPI: OEMB (v001 A M I AMI_OEM 0x11000503 MSFT 0x0097) @ 0x3ffc0040 ACPI: DSDT (v001 K8UNF K8UNF150 0x0150 INTL 0x02002026) @ 0x ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:15 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs More than 8 CPUs detected and CONFIG_X86_PC cannot handle it. Use CONFIG_X86_GENERICARCH or CONFIG_X86_BIGSMP. Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 5000 (gap: 4000:bec0) Built 1 zonelists Kernel command line: root=/dev/sda1 ro ramdisk_size=10 lang=us apm=power-off nomce vga=normal mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 2009.787 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) Memory: 1030560k/1048256k available (1504k kernel code, 17132k reserved, 546k data, 176k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4026.11 BogoMIPS (lpj=2013056) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff e3d3fbff 0001 0001 CPU: After vendor identify, caps: 078bfbff e3d3fbff 0001 0001 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After all inits, caps: 078bfbff e3d3fbff 0410 0001 0001 Checking 'hlt' instruction... OK. CPU0: AMD Athlon(tm) 64 Processor 3200+ stepping 02 Total of 1 processors activated (4026.11 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1 Brought up 1 CPUs migration_cost=0 checking if image is initramfs... it is Freeing initrd memory: 4535k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Subsystem revision 20060127 ACPI:
Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
Package: kernel-image-2.6.10-1-686-smp Severity: important Hello, I find error messages like the one above (not sure about the actual value of gfp_mask) on a regular basis in the logs. Sometimes I just find out hard because the machine simply crashes shortly after. This makes the machine in question unreliable, crashing at least every few weeks. Therefore I'm flagging this bug as important. Hardware is a rather new IBM x205, with ServeRAID4, GigE, and 1GB RAM. Best, --Toni++ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307457: kernel-image-2.6.10-1-686-smp: running into oom-killer: gfp_mask=0xd0 often
Hi, On Tue, 03.05.2005 at 17:02:22 +0200, maximilian attems [EMAIL PROTECTED] wrote: On Tue, 03 May 2005, Toni Mueller wrote: On Tue, 03.05.2005 at 12:16:51 +0200, maximilian attems [EMAIL PROTECTED] wrote: oom-killer: gfp_mask=0xd0 oom-killer: gfp_mask=0x1d2 oom-killer: gfp_mask=0x4d0 anyway please try kernel-image-2.6.11 from unstable! This is currently impossible, due to #306930. Currently, I try to fix this (ie, create a local kernel-nonfree-... package). in oom cases 2.6.11 is very recommended as it has nice fixes from -aa in that release. thanks for this statement. I almost assumed as much after some research on Google... some remarks, though: I have an identical machine running 2.6.10 with no problems. Why does one machine exhibit this problem, and the other doesn't? here you'lll find the intersting non-free bits: http://www.acm.cs.rpi.edu/~dilinger/kernel-source-nonfree-2.6.11/ Thanks, this may speed things up considerably. do you have enough swap, is it activated? $ free total used free sharedbuffers cached Mem: 1033256 505200 528056 0 118348 168228 -/+ buffers/cache: 218624 814632 Swap: 2104220 02104220 Should be sufficient... ;-) Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
