Bug#623514: Hibernate problem
Hi, while I haven't conducted as many tests as Denis has, I can say that my T500 hibernated nicely up until 2.6.32 last version before -36 (I can't currently confirm for 2.6.32-36), and breaks for every later kernel. I can also say that, for the even more recent kernels, the machine does not even suspend-to-ram. I'm running the -686 variant of things, not the amd64 stuff. Feel free to ask any questions. 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/4e7702f3.5090...@oeko.net
Bug#642066: linux-image-loongson-2f: Please include gnewsense patches
Hi Panayiotis, On 11-09-19 at 10:36am, Panayiotis Karabassis wrote: Currently the kernel is missing various bits of functionality, such as webcam operation and battery monitoring. Googling, I found this functionality is enabled if a Linux Libre kernel is used. However I have not been able to verify this, since the kernel does not install on my machine. I kindly request that the patches available at the following URL be included in the Debian package: http://www.fsfla.org/download/linux-libre/lemote/gnewsense/pool/ I suggest to contact gnewsense and kindly request them to pass their improvement upstream to the main Linux kernel development. Perhaps they already did. If so, they can then provide you some reference on where it is in the process of getting into the mainline tree. And you can forward that info here, to help track the process. Regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan Didn't make any difference. Here is dmesg now: If you turn modesetting off you should be able to get the xserver running again. radeon.modeset=0 didn't seem to affect anything. Xorg.0.log: http://pastebin.com/3JKs85PP dmesg: http://pastebin.com/fZehesaK with radeon.modeset=0 There's just no way the GPU can be used properly if its PCI resources aren't properly set up. I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- 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/1316429594.8237.26.camel@thor.local
Bug#642066: [bug #34331] Request to submit linux patches upstream
URL: http://savannah.nongnu.org/bugs/?34331 Summary: Request to submit linux patches upstream Project: gNewSense GNU/Linux Submitted by: panayk Submitted on: Mon 19 Sep 2011 11:09:30 AM GMT Category: None Severity: 3 - Normal Item Group: mipsel Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any ___ Details: Hi! The Longsoon running Lemote Yeelong requires your patched kernel to function properly. However the kernel does not install on Debian Wheezy. After contacting the Debian maintainers, it was suggested that I ask you to submit your patches upstream. It would be a great help to Debian users if you could do this. The Debian bug I opened is #642066. ___ Reply to this item at: http://savannah.nongnu.org/bugs/?34331 ___ Message sent via/by Savannah http://savannah.nongnu.org/ -- 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/20110919-110930.sv85314.56...@savannah.nongnu.org
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
ma, 2011-09-19 kello 12:53 +0200, Michel Dänzer kirjoitti: On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: Hi Tomi, Tomi Leppänen wrote: [0.073485] PCI: Ignoring host bridge windows from ACPI; if necessary, use pci=use_crs and report a bug I was hoping it would be that. Does adding pci=use_crs to the kernel command line help? Thanks, Jonathan Didn't make any difference. Here is dmesg now: If you turn modesetting off you should be able to get the xserver running again. radeon.modeset=0 didn't seem to affect anything. Xorg.0.log: http://pastebin.com/3JKs85PP dmesg: http://pastebin.com/fZehesaK with radeon.modeset=0 There's just no way the GPU can be used properly if its PCI resources aren't properly set up. That's what I thought. I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. If it helps, I have a Nvidia GeForce 2 MX (AGP) and it seems to work completely. (though that card doesn't support interlacing) I can get dmesg for that too if needed but it takes probably a bit longer. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? Yes, it does work. I've been using it because Radeon doesn't work, but Rage's XVideo is broken when using interlaced output (already reported). The DRI thing just requires to disable dri and I don't need 3D so I don't know about that part. dmesg didn't have anything except (AFAIK) that there is something on line 140 and below, but I'm not quite sure if this is an error: [0.068060] pci_root PNP0A03:00: host bridge window [io 0x-0x0cf7] (ignored) full dmesg with Rage 128VR (PCI): pastebin.com/j9YVk9xj -- 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/1316436903.3683.16.camel@tomppeli-laptop
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
On Mon, 2011-09-19 at 15:55 +0300, Tomi Leppänen wrote: ma, 2011-09-19 kello 12:53 +0200, Michel Dänzer kirjoitti: On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. If it helps, I have a Nvidia GeForce 2 MX (AGP) and it seems to work completely. (though that card doesn't support interlacing) I can get dmesg for that too if needed but it takes probably a bit longer. I don't think that'll buy anything at this point. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? Yes, it does work. Then it seems most likely that the problem is with the BIOS or the card. At this point I don't see many options left other than trying if the card works in another machine or with another OS, or maybe trying to re-flash the ROM image on the card if that's possible. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- 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/1316438338.8237.35.camel@thor.local
Bug#642109: Updated po file into Catalan translation for the package linux-latest-2.6
Package: linux-latest-2.6 Version: 2.6_39 Severity: wishlist Tags: l10n linux-latest-2.6 po file have been translated and checked by Debian L10n Catalan Team. It would be fantastic if you could add attached .po file in linux-latest-2.6 package. Thanks! I. De Marchi # debconf templates for linux-latest-2.6; translation into Catalan. # Copyright (C) 2011 Software in the Public Interest # This file is distributed under the same license as the linux-latest-2.6 # package. # Innocent De Marchi tangram.pe...@gmail.com, 2011 # msgid msgstr Project-Id-Version: 2.6_39\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2011-07-24 16:15+0200\n PO-Revision-Date: 2011-09-15 16:52+0100\n Last-Translator: Innocent De Marchi tangram.pe...@gmail.com\n Language-Team: Catalan debian-l10n-cata...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=utf-8\n Content-Transfer-Encoding: 8bit\n X-Poedit-Language: Catalan\n X-Poedit-Country: Spain\n #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid This system requires a different kernel configuration msgstr El sistema requereix una configuració diferent del nucli #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid Debian's '686' kernel configuration has been replaced by the '686-pae' configuration, which uses PAE (Physical Address Extension). However, the CPU in this system does not support PAE. msgstr S'ha reemplaçat la configuració «686» de Debian del nucli per la configuració «686-pae», que fa servir PAE («Physical Address Extension», extensió l'adreça física). No obstant, la UCP del sistema no pot fer servir PAE. #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid You should install linux-image-486 and remove linux-image-686 and/or linux-image-2.6-686 if they are currently installed. msgstr Heu d'instal·lar «linux-image-486» i eliminar «linux-image-686» i/o «linux-image-2.6-686» si estan instal·lats en el sistema.
Bug#641176: xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M
Monday, September 19, 2011 9:18 AM Michel Dänzer wrotew: On Mon, 2011-09-19 at 15:55 +0300, Tomi Leppänen wrote: ma, 2011-09-19 kello 12:53 +0200, Michel Dänzer kirjoitti: On Son, 2011-09-18 at 11:38 +0300, Tomi Leppänen wrote: la, 2011-09-17 kello 06:10 -0700, Will Set kirjoitti: Saturday, September 17, 2011 6:49 AM Tomi Leppänen wrote: pe, 2011-09-16 kello 15:43 -0500, Jonathan Nieder kirjoitti: I wonder why my grub is just some colorful crap on bottom of my screen. I can't really edit anything on fly but I have to always make changes to /etc/default/grub and then issue update-grub. That may have something to do with this bug. It's further indication that the problem may stem from the BIOS, or possibly even the hardware itself. If it helps, I have a Nvidia GeForce 2 MX (AGP) and it seems to work completely. (though that card doesn't support interlacing) I can get dmesg for that too if needed but it takes probably a bit longer. I don't think that'll buy anything at this point. Problem iirc, both your other video cards -- ATI Rage 128VR and Nvidia GeForce 2 MX (AGP) -- have less than 64 MB of VRAM. I've found with my old AGP cards, 64MBs VRAM to be a minimum for mode switching as a general rule. Mobos with video onboard have different limits. I'm starting to see other pentium 4 limits with the newer 3.0.0 kernels, so I'm not really surprised having troubles trying 3.0.0 kernels And the PCI card is IMHO way to new to be used in the PCI slot of that old mobo. The video card has almost as much processing power as the mobo does. I'll bet the mobo's chipset can't access even half that Radeon 9200SE's resources. I also noticed that all of my memory is LOWMEM. Though graphics card doesn't change that (tried with ATI Rage 128VR that has trouble with DRI on Debian 6). Does that card basically work though? Do you also get PCI related errors in dmesg with it? Yes, it does work. Then it seems most likely that the problem is with the BIOS or the card. At this point I don't see many options left other than trying if the card works in another machine or with another OS, or maybe trying to re-flash the ROM image on the card if that's possible. I agree, especially if the BIOS is not being changed to reflect the PCI socket is being used for video instead of the mobos AGP slot. http://www.gigabyte.lv/products/mb/specs/ga-6bxe.html?print_page=1 I'd suggest using a Debian Live CD while testing, especially with older and oddly mixed hardware. http://cdimage.debian.org/cdimage/release/current-live/i386/iso-hybrid/ -- 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/1316443018.87530.yahoomail...@web35607.mail.mud.yahoo.com
Bug#623514: Hibernate problem
Hi Toni, Toni Müller wrote: while I haven't conducted as many tests as Denis has, I can say that my T500 hibernated nicely up until 2.6.32 last version before -36 (I can't currently confirm for 2.6.32-36), and breaks for every later kernel. I can also say that, for the even more recent kernels, the machine does not even suspend-to-ram. That doesn't necessarily sound like the same bug (Denis was testing with 3.0.0-1 and had no trouble suspending iirc). The narrow regression range is good news from the point of view of being able to find a fix. Could you file a new bug listing kernels you've tested and results for each? The upgrade history of the kernel image packages can be found at /var/log/dpkg.log*. If the symptoms turn out to have the same cause, we can merge the bugs later. Thank you, Jonathan -- 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/20110919155708.GA2861@elie
[bts-link] source package src:linux-2.6
# # bts-link upstream status pull for source package src:linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #637511 (http://bugs.debian.org/637511) # Bug title: i915 GPU Hang on First Login with Display Manager # * https://bugs.freedesktop.org/show_bug.cgi?id=40181 # * remote status changed: (?) - NEW usertags 637511 + status-NEW # remote status report for #641622 (http://bugs.debian.org/641622) # Bug title: [regression 3.0-3.1-rc1] i915: screen corruption unless i915.i915_enable_fbc=0 # * https://bugs.freedesktop.org/show_bug.cgi?id=40883 # * remote status changed: (?) - NEW usertags 641622 + status-NEW thanks -- 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/20110919163809.11503.94675.btsl...@busoni.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #641665 (http://bugs.debian.org/641665) # Bug title: 915GM (Eee PC 900): fonts have some corrupted glyphs: strikethrough # * https://bugs.freedesktop.org/show_bug.cgi?id=36326 # * remote status changed: (?) - NEW usertags 641665 + status-NEW thanks -- 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/20110919163815.11503.52086.btsl...@busoni.debian.org
Bug#642043: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives
On Sun, Sep 18, 2011 at 05:27:05PM -0500, Jonathan Nieder wrote: [ 9762.594980] Pid: 4271, comm: scsi_eh_6 Tainted: G O 3.0.0-1-amd64 #1 Gigabyte Technology Co., Ltd. H61M-USB3-B3/H61M-USB3-B3 (This is not the first oops after booting.) Actually it is (no D in the flags). But it have out-of-tree modules loaded. Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, Errand of Mercy, stardate 3198.9 -- 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/20110919165101.ga8...@wavehammer.waldi.eu.org
Bug#642140: New LVM volumes stop appearing in /dev/ when chromium is running
Package: linux-2.6 Version: 3.0.0-3 Severity: serious Hello, this is on testing, the relevant package versions are: udev 172-1 chromium 13.0.782.220~r99552-1 lvm2 2.02.86-1 This seems to be relevant and contains a patch: https://bugs.archlinux.org/task/24614 This is how I reproduce it: System just booted, chromium NOT running: root@viaza:~# lvcreate -L 1G -n foo viaza Logical volume foo created root@viaza:~# lvremove /dev/viaza/foo Do you really want to remove active logical volume foo? [y/n]: y Logical volume foo successfully removed After starting chromium: root@viaza:~# lvcreate -L 1G -n foo viaza /dev/mapper/viaza-foo: open failed: No such file or directory /dev/viaza/foo: not found: device not cleared Aborting. Failed to wipe start of new LV. LV viaza/foo in use: not deactivating Unable to deactivate failed new LV. Manual intervention required. After closing chromium: root@viaza:~# lvcreate -L 1G -n bar viaza Logical volume bar created After reopening chromium: root@viaza:~# lvcreate -L 1G -n baz viaza /dev/mapper/viaza-baz: open failed: No such file or directory /dev/viaza/baz: not found: device not cleared Aborting. Failed to wipe start of new LV. Unable to deactivate open viaza-baz (254:14) Unable to deactivate failed new LV. Manual intervention required. After closing chromium: root@viaza:~# lvcreate -L 1G -n wibble viaza Logical volume wibble created ...and so on. Nothing shows up in dmesg: the version you see attached is taken just after running the sequence of commands above. Chromium is running as a normal user, which means that whatever it is doing can make root unable[1] to create LVM volumes, which sounds to me like a security issue as well. Ciao, Enrico [1] running /etc/init.t/lvm2 restart causes those half-created volumes to show up, but still. -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64 root=/dev/mapper/viaza-root ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 10.173145] Bluetooth: SCO socket layer initialized [ 10.329770] Bluetooth: Generic Bluetooth USB driver ver 0.6 [ 10.329978] usbcore: registered new interface driver btusb [ 10.503476] scsi6 : pata_pcmcia [ 10.503531] ata7: PATA max PIO0 cmd 0x2100 ctl 0x210e irq 22 [ 10.517882] iwlagn :43:00.0: loaded firmware version 9.221.4.1 build 25532 [ 10.518177] Registered led device: phy0-led [ 10.804002] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 10.833225] fbcon: inteldrmfb (fb0) is primary device [ 11.216716] Linux media interface: v0.10 [ 11.241662] Linux video capture interface: v2.00 [ 11.266342] uvcvideo: Found UVC 1.00 device HP Webcam [2 MP Macro] (04f2:b163) [ 11.304316] input: HP Webcam [2 MP Macro] as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input12 [ 11.304384] usbcore: registered new interface driver uvcvideo [ 11.304385] USB Video Class driver (v1.1.0) [ 12.815400] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [ 12.896425] Console: switching to colour frame buffer device 160x50 [ 12.898421] fb0: inteldrmfb frame buffer device [ 12.898422] drm: registered panic notifier [ 12.919658] acpi device:0e: registered as cooling_device4 [ 12.919934] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input13 [ 12.920020] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 12.920091] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 12.924343] HDA Intel :00:1b.0: power state changed by ACPI to D0 [ 12.924352] HDA Intel :00:1b.0: power state changed by ACPI to D0 [ 12.924362] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 12.924455] HDA Intel :00:1b.0: irq 47 for MSI/MSI-X [ 12.924493] HDA Intel :00:1b.0: setting latency timer to 64 [ 13.007969] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input14 [ 13.017426] HDMI status: Pin=4 Presence_Detect=0 ELD_Valid=0 [ 13.017929] HDMI status: Pin=6 Presence_Detect=0 ELD_Valid=0 [ 13.034386] input: HDA Intel Line In at Sep Rear Jack as /devices/pci:00/:00:1b.0/sound/card0/input15 [ 13.034465] input: HDA Intel Mic at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input16 [ 13.034541] input: HDA Intel HP Out at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input17 [ 13.034615] input: HDA Intel HP Out at Sep Rear Jack as /devices/pci:00/:00:1b.0/sound/card0/input18 [ 13.034787] input: HDA Intel HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input19 [ 13.034861] input: HDA Intel HDMI/DP as
Bug#642154: BUG: unable to handle kernel paging request at ffff8803bb6ad000
Package: linux-2.6 Version: 3.0.0-3 Severity: important Tags: upstream Dear Maintainer, I have some suspicious activities on my server: i've continiously repeated messages in dmesg about BUG: unable to handle kernel paging request, also there are many messages like Message from syslogd@xen-dom0 at Sep 20 00:45:04 ... kernel:[430010.207876] Oops: [#3453] SMP Message from syslogd@xen-dom0 at Sep 20 00:45:04 ... kernel:[430010.213958] Stack: Message from syslogd@xen-dom0 at Sep 20 00:45:04 ... kernel:[430010.215212] Call Trace: Message from syslogd@xen-dom0 at Sep 20 00:45:04 ... kernel:[430010.215745] Code: e8 13 2a ff ff 66 90 c3 48 8b 97 48 04 00 00 48 85 d2 0f 84 d0 00 00 00 48 8b 47 08 f6 40 14 01 74 02 0f 0b 48 8b 05 45 4e 71 00 Message from syslogd@xen-dom0 at Sep 20 00:45:04 ... kernel:[430010.220251] CR2: 8803bbe85000 falling down in console or ssh session. I've checked memory: they are fine (also they are new, just a week from a shop). I tried to reboot several times without any effect. Also there is xen on this machine ii libxenstore3.0 4.1.1-2 Xenstore communications library for Xen ii xen-hypervisor-4.0-amd64 4.0.1-2 The Xen Hypervisor on AMD64 ii xen-linux-system-3.0.0-1-amd64 3.0.0-3 Xen system with Linux 3.0.0 on 64-bit PCs (meta-package) ii xen-qemu-dm-4.04.0.1-2 Xen Qemu Device Model virtual machine hardware emulator ii xen-tools 4.2.1-1 Tools to manage Xen virtual servers ii xen-utils-4.0 4.0.1-2 XEN administrative tools ii xen-utils-common 4.1.0~rc6-1 XEN administrative tools - common files ii xenstore-utils 4.1.1-2 Xenstore utilities for Xen It can take some influence on this messages? Is it serious and my server in dangerous? How i make fix it or at least turn off messages in console and ssh session? By the way, munin monitoring sometimes show blank spaces in graphics when quering xen time. But xen virtual machine works fine without any problems. Please help me =) -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011 ** Command line: placeholder root=/dev/mapper/xen-system ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [430009.942525] RSP: e02b:88005895fe00 EFLAGS: 00010246 [430009.942630] RAX: RBX: 7fff294b9380 RCX: 0200 [430009.942769] RDX: 8803bbf13e00 RSI: 88005895ffd8 RDI: 88005813b510 [430009.942905] RBP: 88005813b510 R08: 88005895e000 R09: 81684640 [430009.943044] R10: 00012800 R11: 0246 R12: [430009.943179] R13: R14: 88005813b510 R15: 7fff294b9380 [430009.943321] FS: 7f7d27518700() GS:8803d620c000() knlGS: [430009.943463] CS: e033 DS: ES: CR0: 8005003b [430009.943570] CR2: 8803bbf14000 CR3: 000214dd3000 CR4: 2660 [430009.943711] DR0: DR1: DR2: [430009.943851] DR3: DR6: 0ff0 DR7: 0400 [430009.943995] Process swap (pid: 2786, threadinfo 88005895e000, task 88005813b510) [430009.944136] Stack: [430009.944231] 81010919 00413201 88005895ff58 0011 [430009.944617] 88005813b9a0 81008fdd [430009.945001] 7fff294b91b8 0011 00040001 fffe0ae3 [430009.945387] Call Trace: [430009.945485] [81010919] ? save_i387_xstate+0x102/0x1f3 [430009.945594] [81008fdd] ? do_signal+0x212/0x649 [430009.945701] [81009450] ? do_notify_resume+0x25/0x6b [430009.945811] [810fbfa6] ? sys_read+0x5f/0x6b [430009.956650] [8133bfe0] ? int_signal+0x12/0x17 [430009.956757] Code: e8 13 2a ff ff 66 90 c3 48 8b 97 48 04 00 00 48 85 d2 0f 84 d0 00 00 00 48 8b 47 08 f6 40 14 01 74 02 0f 0b 48 8b 05 45 4e 71 00 [430009.959514] 8b b2 00 02 00 00 48 89 c1 48 21 f1 48 39 c1 0f 84 a7 00 00 [430009.960980] RIP [810106db] __sanitize_i387_state+0x23/0xe1 [430009.961151] RSP 88005895fe00 [430009.961251] CR2: 8803bbf14000 [430009.961350] ---[ end trace 35f1420b1560dba9 ]--- [430010.207109] BUG: unable to handle kernel paging request at 8803bbe85000 [430010.207350] IP: [810106db] __sanitize_i387_state+0x23/0xe1 [430010.207525] PGD 1604067 PUD 3d82d9067 PMD 3d84b9067 PTE 0 [430010.207876] Oops: [#3453] SMP [430010.208099] CPU 4 [430010.208166] Modules linked in: xt_tcpudp xt_physdev iptable_filter
Bug#642140: New LVM volumes stop appearing in /dev/ when chromium is running
# ebf4127cd677 (kobj_uevent: Ignore if some listeners cannot handle message, # 2011-08-22), which is in the driver-core tree and hence in linux-next (but # not in linus's tree yet). tags 642140 + upstream patch forwarded 642140 http://thread.gmane.org/gmane.linux.kernel/1180877/focus=1182353 quit Hi Enrico, Enrico Zini wrote: After starting chromium: root@viaza:~# lvcreate -L 1G -n foo viaza /dev/mapper/viaza-foo: open failed: No such file or directory /dev/viaza/foo: not found: device not cleared Aborting. Failed to wipe start of new LV. LV viaza/foo in use: not deactivating Unable to deactivate failed new LV. Manual intervention required. After closing chromium: root@viaza:~# lvcreate -L 1G -n bar viaza Logical volume bar created Weird. Thanks for reporting it. -- 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/20110919210830.GA6343@elie
Processed: Re: New LVM volumes stop appearing in /dev/ when chromium is running
Processing commands for cont...@bugs.debian.org: # ebf4127cd677 (kobj_uevent: Ignore if some listeners cannot handle message, # 2011-08-22), which is in the driver-core tree and hence in linux-next (but # not in linus's tree yet). tags 642140 + upstream patch Bug #642140 [linux-2.6] New LVM volumes stop appearing in /dev/ when chromium is running Added tag(s) upstream and patch. forwarded 642140 http://thread.gmane.org/gmane.linux.kernel/1180877/focus=1182353 Bug #642140 [linux-2.6] New LVM volumes stop appearing in /dev/ when chromium is running Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel/1180877/focus=1182353'. quit Stopping processing here. Please contact me if you need assistance. -- 642140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.131646655013065.transcr...@bugs.debian.org
Re: Bug#642043: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives
Bastian Blank wrote: On Sun, Sep 18, 2011 at 05:27:05PM -0500, Jonathan Nieder wrote: [ 9762.594980] Pid: 4271, comm: scsi_eh_6 Tainted: G O 3.0.0-1-amd64 #1 Gigabyte Technology Co., Ltd. H61M-USB3-B3/H61M-USB3-B3 (This is not the first oops after booting.) Actually it is (no D in the flags). But it have out-of-tree modules loaded. Thanks, Bastian. I need to study up on my print_tainted flags... (In particular, I wish that not proprietary didn't show up as a taint flag with the same letter as debbugs uses for grave bug. :)) -- 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/20110919212804.GC6343@elie
Re: Bug#642043: linux-image-3.0.0-1-amd64 frequently kerneloops on unmounting USB drives
I should point out that I have seen this error occur on a wheezy install with no out-of-tree modules installed (that module being virtualbox) even though the syslog etc I uploaded here did have the offending module active and that I have also seen it occur when removing fat32 drives, not just NTFS. Indeed, this bug report does seem to be a duplicate although I did search before I posted. I haven't been able to try the experimental kernel yet as the machine in question is my girlfriends but if this oops doesn't occur when doing a normal unmount (as the original report suggests) then its not as severe a bug as I first thought. Dan On Mon, Sep 19, 2011 at 10:28 PM, Jonathan Nieder jrnie...@gmail.com wrote: Bastian Blank wrote: On Sun, Sep 18, 2011 at 05:27:05PM -0500, Jonathan Nieder wrote: [ 9762.594980] Pid: 4271, comm: scsi_eh_6 Tainted: G O 3.0.0-1-amd64 #1 Gigabyte Technology Co., Ltd. H61M-USB3-B3/H61M-USB3-B3 (This is not the first oops after booting.) Actually it is (no D in thve Thanks, Bastian. I need to study up on my print_tainted flags... (In particular, I wish that not proprietary didn't show up as a taint flag with the same letter as debbugs uses for grave bug. :)) -- 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/canooojujkzf5n4gzgsra12mj5mxi0rwgdgrxyba8niwezfh...@mail.gmail.com
Bug#642154: BUG: unable to handle kernel paging request at ffff8803bb6ad000
Hi, rush wrote: I have some suspicious activities on my server: i've continiously repeated messages in dmesg about BUG: unable to handle kernel paging request Yes, if this server is open to the public (especially if it has untrusted local users), you should probably take it down. A kernel BUG means that something happened the kernel did not expect, and after that point, all bets (including security bets) are off. Of course we would be happiest if you can make it happen again, in order to track it down and fix it, though. :) [...] I've checked memory: they are fine Thanks! [...] * Kernel has oopsed before. [...] [430009.960980] RIP [810106db] __sanitize_i387_state+0x23/0xe1 Can you recover a trace of the first oops (for example from /var/log/message*)? Instead of a Tainted line containing a D (has oopsed before), it should have a Not tainted line. Thanks for writing, Jonathan -- 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/20110919212211.GB6343@elie
Bug#641919: linux-image-3.0.0-1-amd64: VIA-Rhine II resetting: network connectivity lost
El Lunes, 19 de Septiembre de 2011, Ben Hutchings escribió: On Sat, 2011-09-17 at 15:59 +0100, Antonio Marcos López Alonso wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream This is the same behavior as bug #549606. Network connection is lost somehow and dmesg outputs lots of: via-rhine :00:12.0: eth0: Transmit timed out, status 0003, PHY status 786d, resetting... via-rhine :00:12.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 Resetting the machine fixes the issue. This behavior has been happening now and then since the previous bug was closed. [...] I think bug #549606 was closed in error, as the supposed fix is related to behaviour after a transmit timeout and not the cause of timeouts. Before it was closed, you found that the kernel parameter 'noapic' was a workaround for the problem on your system, which means it probably isn't a bug in the driver). I notice that you are currently *not* using that parameter. Hi Ben: I effectively used noapic to apparently workaround the problem but in the long run I found it just minimized the problem somehow (occurrences were less). I asked you to report this bug at http://bugzilla.kernel.org, including the fact that 'noapic' works around it. The product should be 'Platform Specific/Hardware' and the component 'i386'. You won't be able to do that at the moment because that server is done, but please try to do that in a week or so. Then let us know the bug number so we can keep track of it. OK, I'll do it so and let you know. Antonio -- 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/201109192342.32486.amlopezalo...@gmail.com
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
Hi Miguel, I have already built kernel 3.0.0-1-amd64 with the required debugging symbols. I've rebooted into the debug kernel, and loaded the iwlagn module with debugging symbols enabled. Or so I think. [MV] I don't see much iwlagn debugging information in the log you sent me. Can you please load the iwlagn module with the following parameters: modprobe iwlagn debug=0x43FFF Thanks, Meenakshi -- 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/c5a7fb31fd9aea42b600bdc3c74f8e0014ad3...@orsmsx511.amr.corp.intel.com
Bug#641424: iwlagn: fails to reconnect to WPA2-enterprise (Reason: 23)
I'm quite sure I loaded the module with debug information. It is not in the beginning of the debug log, since it connected to Eduroam before I rmmod'ed and modprobed iwlagn with the debug symbols enabled. Anyway, I'll try again tomorrow. -- Dr. Miguel Martinez Canales Department of Physics Astronomy University College London Gower Street, London, WC1E 6BT (UK) Fax: +44 207 679 0595 Tlf: +44 207 678 3476 If you have an apple and I have an apple and we exchange these apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas. George Bernard Shaw -- 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/20110926.17057.el.qu...@gmail.com
Bug#641069: [ehci_hcd] reset high speed USB device using ehci_hcd
Le 16/09/2011 23:40, Jonathan Nieder a écrit : retitle 641069 ehci_hcd resets when copying data to/from Samsung Wave II, copying stalls (USB1 works ok) tags 641069 - moreinfo quit Hi Laurent, Laurent Besson wrote: There's some freeze when copied data from or to this storage (Samsung Wave II) But a friend of mine had the same message for his mouse, and when it hapened the mouse stop moving during 1-2-3-4 seconds... It's difficult to produce this, because it's erratic (sometimes work and after not... ?) A solution on debian is to remove module when I plug my smartphone (then I copied with 1-2Mb/s) , when it's finished I remove my smartphone and reload module... It's not really clean... but works ! Quick questions: - can you reproduce this with your friend's mouse (or any other mouse)? If not, could your friend file a separate report so we can get to know his hardware? - please attach output from /usr/share/bug/linux-image-$(uname -r)/script 31 - please also test a recent kernel (3.x) from sid or experimental. It should not require any other packages from sid except for linux-base and initramfs-tools. If this is reproducible with a recent kernel, we should pass this upstream (I guess that is linux-...@vger.kernel.org, cc-ing Alan Stern st...@rowland.harvard.edu and this bug log). Otherwise, we can try to find the fix and backport it. Thanks, Jonathan Hi Thank's for your response, I can reproduce this with the friend's mouse because I could take on my PC and have the same bug ! I will send (today at job) output when i plug this, and /usr/share/bug/linux-image-$(uname -r)/script Ok -- 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/4e7803c2.6000...@system-linux.net
Processed: tagging 633738
Processing commands for cont...@bugs.debian.org:
tags 633738 + pending
Bug #633738 {Done: dann frazier da...@debian.org} [linux-2.6] ip6_tunnel:
kernel BUG at net_namespace.c:497
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
633738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.13164905021522.transcr...@bugs.debian.org
Processed: Re: Bug#642005: general: maximum size of SHM memory blocks to low
Processing commands for cont...@bugs.debian.org: reassign 642005 linux-2.6 Bug #642005 [general] general: maximum size of SHM memory blocks to low Bug reassigned from package 'general' to 'linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. -- 642005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13164920888261.transcr...@bugs.debian.org
Re: Upcoming Point Releases
On Wed, Sep 07, 2011 at 09:30:50PM +0200, Philipp Kern wrote: Hi, we finally got target dates for the next point releases of both Lenny and Squeeze. Lenny should get 5.0.9 on October 1st; Squeeze will follow on October 8th with 6.0.3. NEW for Lenny will be closed on the weekend of September 24th; NEW for Squeeze on the weekend of October 1st. The upload of debian-installer for Lenny should happen on the closing weekend at the latest; the middle of week 38 would be appreciated, so that we have everything together on the 24th. We have a lenny security update about ready to release (just waiting on a couple builds). I've merged those changes into the lenny branch and I can upload an o-p-u build tomorrow (which I'll do, barring any objection). This should allow for a d-i upload before the weekend. I don't think a d-i upload is strictly necessary - we haven't added any hardware support since the last point release - but it is probably a good idea given the large number of changes since the last update. For Squeeze it would be cool to have the kernel in for testing end of next week (16/17th). The d-i upload should be there the middle of week 39, October 1st at the latest. base-files can be uploaded now, as it will be held in NEW until closing time anyway. Kind regards and thanks for your efforts Philipp Kern -- 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/2011092004.gc18...@dannf.org
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux-2.6_3.0.0-4.diff.gz linux-2.6_3.0.0-4.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:27:56, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1r5sd8-0001rt...@franck.debian.org
Processing of linux-2.6_3.0.0-4_multi.changes
linux-2.6_3.0.0-4_multi.changes uploaded successfully to localhost along with the files: linux-2.6_3.0.0-4.dsc linux-2.6_3.0.0-4.diff.gz linux-doc-3.0.0_3.0.0-4_all.deb linux-manual-3.0.0_3.0.0-4_all.deb linux-patch-debian-3.0.0_3.0.0-4_all.deb linux-source-3.0.0_3.0.0-4_all.deb linux-support-3.0.0-1_3.0.0-4_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1r5si0-00029i...@franck.debian.org
Bug#641069: [ehci_hcd] reset high speed USB device using ehci_hcd
Le 16/09/2011 23:40, Jonathan Nieder a écrit : Quick questions: - can you reproduce this with your friend's mouse (or any other mouse)? If not, could your friend file a separate report so we can get to know his hardware? - please attach output from /usr/share/bug/linux-image-$(uname -r)/script 31 - please also test a recent kernel (3.x) from sid or experimental. It should not require any other packages from sid except for linux-base and initramfs-tools. If this is reproducible with a recent kernel, we should pass this upstream (I guess that is linux-...@vger.kernel.org, cc-ing Alan Stern st...@rowland.harvard.edu and this bug log). Otherwise, we can try to find the fix and backport it. Thanks, Jonathan I don't know if I could test with a kernel 3.x... But I'm going to try. -- 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/4e78260b.8040...@system-linux.net
Bug#636242: marked as done ([INTL:es] po-debconf linux 2.6 updated Spanish translation)
Your message dated Tue, 20 Sep 2011 05:34:37 +
with message-id e1r5syb-0003xh...@franck.debian.org
and subject line Bug#636242: fixed in linux-2.6 3.0.0-4
has caused the Debian Bug report #636242,
regarding [INTL:es] po-debconf linux 2.6 updated Spanish translation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
636242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32+5
Severity: wishlist
Tags: l10n, patch
Regards,
--
Omar Campagne Polaino
# linux-2.6 po-debconf translation to Spanish
# This file is distributed under the same license as the linux-2.6 package.
#
# Changes:
#- Initial translation
#Omar Campagne ocampa...@gmail.com 2010, 2011
#
#- Review and update
#Javier Fernandez-Sanguino, December 2010
#
# Traductores, si no conocen el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
# Equipo de traducción al español, por favor lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas y normas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid
msgstr
Project-Id-Version: linux-2.6 2.6.32+5\n
Report-Msgid-Bugs-To: linux-...@packages.debian.org\n
POT-Creation-Date: 2011-07-04 04:24+0100\n
PO-Revision-Date: 2011-07-16 17:59+0200\n
Last-Translator: Omar Campagne ocampa...@gmail.com\n
Language-Team: Debian l10n Spanish debian-l10n-span...@lists.debian.org\n
Language: es\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Plural-Forms: nplurals=2; plural=(n != 1);\n
X-Generator: Virtaal 0.6.1\n
X-POFile-SpellExtra: initrd postinsthook conf lib contrib yes IDE depmod\n
X-POFile-SpellExtra: runningversion img script boot Free exitvalue version\n
X-POFile-SpellExtra: Debian CORE free running dobootloader UUID dep SIGNAL\n
X-POFile-SpellExtra: Guidelines modulesbase vmlinuz postinst\n
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid Abort installation after depmod error?
msgstr
¿Desea interrumpir la instalación cuando se produzca un fallo de depmod?
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid
The 'depmod' command exited with the exit code ${exit_value}
(${SIGNAL}${CORE}).
msgstr
La orden «depmod» finalizó con el código de salida «${exit_value}
(${SIGNAL}${CORE})».
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid
Since this image uses initrd, the ${modules_base}/=V/modules.dep file will
not be deleted, even though it may be invalid.
msgstr
Debido a que esta imagen usa una imagen de arranque «initrd», no se
eliminará el fichero «${modules_base}/=V/modules.dep», aún cuando no sea
válido.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid
You should abort the installation and fix the errors in depmod, or
regenerate the initrd image with a known good modules.dep file. If you don't
abort the installation, there is a danger that the system will fail to boot.
msgstr
Debería cancelar la instalación y arreglar los errores de depmod, o
regenerar la imagen de arranque «initrd» con un fichero «modules.dep»
fiable. Si no cancela la instalación, existe el peligro de que el sistema no
pueda arrancar.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid Abort kernel removal?
msgstr ¿Desea cancelar la eliminación del núcleo?
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid
You are running a kernel (version ${running}) and attempting to remove the
same version.
msgstr
Su sistema está ejecutando el núcleo (versión ${running}), y está intentando
eliminar la misma versión del núcleo.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid
This can make the system unbootable as it will remove /boot/vmlinuz-
${running} and all modules under the directory /lib/modules/${running}. This
can only be fixed with a copy of the kernel image and the corresponding
modules.
msgstr
Puede que el sistema no pueda arrancar
Bug#636531: marked as done (linux-image-3.0.0-1-kirkwood: NULL pointer deref in rt2800usb_get_txwi)
Your message dated Tue, 20 Sep 2011 05:34:38 + with message-id e1r5syc-0003xn...@franck.debian.org and subject line Bug#636531: fixed in linux-2.6 3.0.0-4 has caused the Debian Bug report #636531, regarding linux-image-3.0.0-1-kirkwood: NULL pointer deref in rt2800usb_get_txwi to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 636531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-1 Severity: critical Tags: upstream Justification: breaks the whole system Hello, I'm running a Ralink RT2870 USB Wireless NIC on a sheeva plug in accesspoint mode. The wireless network is bridged to the internal ethernet port. linux-image and ralink firmware should be latest and greatest. After some hours of operation the kernel oopes, see below. cheers, Marc [frogger@salsvatn:~]$ brctl show bridge name bridge id STP enabled interfaces br-bs-lan 8000.001ee5e2b77c no lan wlan0 [frogger@salsvatn:~]$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1737:0071 Linksys WUSB600N v1 Dual-Band Wireless-N Network Adapter [Ralink RT2870] [frogger@salsvatn:~]$ sudo cat /etc/hostapd/hostapd.conf interface=wlan0 bridge=br-bs-lan driver=nl80211 logger_syslog=-1 logger_syslog_level=3 logger_stdout=-1 logger_stdout_level=3 dump_file=/tmp/hostapd.dump ctrl_interface=/var/run/hostapd ctrl_interface_group=0 ssid=blackshift-ng5 max_num_sta=255 rts_threshold=2347 fragm_threshold=2346 ieee80211d=1 country_code=DE hw_mode=a channel=40 #hw_mode=g #channel=8 ieee80211n=1 wme_enabled=1 ht_capab=[HT40-][SHORT-GI-20][SHORT-GI-40][GF][TX-STBC][RX-STBC12][MAX-AMSDU-7935][DELAYED-BA] #[SMPS-STATIC] wmm_enabled=1 # # # Low priority / AC_BK = background wmm_ac_bk_cwmin=4 wmm_ac_bk_cwmax=10 wmm_ac_bk_aifs=7 wmm_ac_bk_txop_limit=0 wmm_ac_bk_acm=0 # Note: for IEEE 802.11b mode: cWmin=5 cWmax=10 # # Normal priority / AC_BE = best effort wmm_ac_be_aifs=3 wmm_ac_be_cwmin=4 wmm_ac_be_cwmax=10 wmm_ac_be_txop_limit=0 wmm_ac_be_acm=0 # Note: for IEEE 802.11b mode: cWmin=5 cWmax=7 # # High priority / AC_VI = video wmm_ac_vi_aifs=2 wmm_ac_vi_cwmin=3 wmm_ac_vi_cwmax=4 wmm_ac_vi_txop_limit=94 wmm_ac_vi_acm=0 # Note: for IEEE 802.11b mode: cWmin=4 cWmax=5 txop_limit=188 # # Highest priority / AC_VO = voice wmm_ac_vo_aifs=2 wmm_ac_vo_cwmin=2 wmm_ac_vo_cwmax=3 wmm_ac_vo_txop_limit=47 wmm_ac_vo_acm=0 # Note: for IEEE 802.11b mode: cWmin=3 cWmax=4 burst=102 wpa=2 wpa_passphrase=geheim wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP rsn_pairwise=CCMP wpa_group_rekey=600 wpa_ptk_rekey=600 output on serial line: [35438.609781] Unable to handle kernel NULL pointer dereference at virtual address 00ac [35438.619110] pgd = c0004000 [35438.622930] [00ac] *pgd= [35438.626684] Internal error: Oops: 17 [#1] [35438.630707] Modules linked in: nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc bridge ipv6 stp ext2 arc4 rt2800usb rt2800lib crc_ccitt rt2x00usb rt2x00lib mac80211 hmac cfg80211 rfkill sha1_generic mv_cesa aes_generic ext4 mbcache jbd2 mmc_block ehci_hcd usbcore mvsdio mmc_core mv643xx_eth libphy inet_lro [35438.658325] CPU: 0Not tainted (3.0.0-1-kirkwood #1) [35438.663670] PC is at rt2800usb_get_txwi+0x10/0x20 [rt2800usb] [35438.669456] LR is at rt2800_txdone_entry+0x34/0xe0 [rt2800lib] [35438.675313] pc : [bf1c001c]lr : [bf1b6348]psr: 8013 [35438.675319] sp : dfa93f00 ip : 0001 fp : 0021 [35438.686855] r10: 000a r9 : 0001 r8 : 003c [35438.692106] r7 : r6 : de8f8fc0 r5 : 808c21f5 r4 : dee613a8 [35438.698663] r3 : r2 : r1 : 808c21f5 r0 : dee613a8 [35438.705222] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel [35438.712563] Control: 0005397f Table: 1f978000 DAC: 0017 [35438.718336] Process kworker/u:0 (pid: 1684, stack limit = 0xdfa92270) [35438.724806] Stack: (0xdfa93f00 to 0xdfa94000) [35438.729190] 3f00: 808c21f5 de8f8fc0 dee613a8 808c21f5 de64e0b4 bf1b64cc [35438.737411] 3f20: c042c4c4 de8f8fc0 de8f8fc4 bf1c0d88 de8f93c4 c040600c 0012 [35438.745635] 3f40: c108aa05 bf1c0d9c de8f93c4 df0a8920 c108aa00 bf1c0d88 de8f93c4 [35438.753858] 3f60: c040600c 0012 c108aa05 c005b9cc df0a8920 df0a8920 c0450034 c045003c [35438.762081] 3f80: dfa92000 df0a8930 c040600c 0001 0089 c005d634 df0a8920 [35438.770303] 3fa0: a013 de4e3f10 df0a8920
Bug#638696: marked as done (FTBFS on alpha; GPIO config is insane)
Your message dated Tue, 20 Sep 2011 05:34:38 + with message-id e1r5syc-0003xt...@franck.debian.org and subject line Bug#638696: fixed in linux-2.6 3.0.0-4 has caused the Debian Bug report #638696, regarding FTBFS on alpha; GPIO config is insane to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 638696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-2 Severity: normal From the build log: CC [M] drivers/hwmon/sht15.o In file included from +/build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/arch/alp +ha/include/asm/gpio.h:20, from +/build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/include/ +linux/gpio.h:18, from +/build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/drivers/ +hwmon/sht15.c:21: /build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/include/a +sm-generic/gpio.h: In function 'gpio_get_value_cansleep': /build/buildd-linux-2.6_3.0.0-2-alpha-uWIvrQ/linux-2.6-3.0.0/debian/build/source_alpha_none/include/a +sm-generic/gpio.h:223: error: implicit declaration of function 'gpio_get_value' Full build log available at: http://buildd.debian-ports.org/status/fetch.php?pkg=linux-2.6arch=alphaver=3.0.0-2stamp=1313880281 Setting CONFIG_GPIOLIB should fix this. Regards Michael Cree. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 3.0.0-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_3.0.0-4.diff.gz to main/l/linux-2.6/linux-2.6_3.0.0-4.diff.gz linux-2.6_3.0.0-4.dsc to main/l/linux-2.6/linux-2.6_3.0.0-4.dsc linux-doc-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-4_all.deb linux-manual-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-4_all.deb linux-patch-debian-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-4_all.deb linux-source-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-source-3.0.0_3.0.0-4_all.deb linux-support-3.0.0-1_3.0.0-4_all.deb to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 638...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 19 Sep 2011 14:40:42 +0100 Source: linux-2.6 Binary: linux-tools-3.0.0 linux-source-3.0.0 linux-doc-3.0.0 linux-manual-3.0.0 linux-patch-debian-3.0.0 linux-support-3.0.0-1 linux-libc-dev linux-headers-3.0.0-1-all linux-headers-3.0.0-1-all-alpha linux-headers-3.0.0-1-common linux-image-3.0.0-1-alpha-generic linux-headers-3.0.0-1-alpha-generic linux-image-3.0.0-1-alpha-smp linux-headers-3.0.0-1-alpha-smp linux-image-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-all-amd64 linux-image-3.0.0-1-amd64 linux-headers-3.0.0-1-amd64 linux-image-3.0.0-1-amd64-dbg xen-linux-system-3.0.0-1-amd64 linux-headers-3.0.0-1-common-rt linux-image-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-rt-amd64 linux-image-3.0.0-1-rt-amd64-dbg xen-linux-system-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-all-armel linux-image-3.0.0-1-iop32x linux-headers-3.0.0-1-iop32x linux-image-3.0.0-1-ixp4xx linux-headers-3.0.0-1-ixp4xx linux-image-3.0.0-1-kirkwood linux-headers-3.0.0-1-kirkwood linux-image-3.0.0-1-orion5x linux-headers-3.0.0-1-orion5x linux-image-3.0.0-1-versatile linux-headers-3.0.0-1-versatile linux-headers-3.0.0-1-all-armhf linux-image-3.0.0-1-mx5 linux-headers-3.0.0-1-mx5 linux-image-3.0.0-1-omap linux-headers-3.0.0-1-omap linux-headers-3.0.0-1-all-hppa linux-image-3.0.0-1-parisc linux-headers-3.0.0-1-parisc linux-image-3.0.0-1-parisc-smp linux-headers-3.0.0-1-parisc-smp linux-image-3.0.0-1-parisc64 linux-headers-3.0.0-1-parisc64 linux-image-3.0.0-1-parisc64-smp linux-headers-3.0.0-1-parisc64-smp linux-headers-3.0.0-1-all-i386
Bug#639439: marked as done (reportbug script fails on s390: no PCI bus)
Your message dated Tue, 20 Sep 2011 05:34:38 + with message-id e1r5syc-0003xw...@franck.debian.org and subject line Bug#639439: fixed in linux-2.6 3.0.0-4 has caused the Debian Bug report #639439, regarding reportbug script fails on s390: no PCI bus to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 639439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-35 Severity: normal Hi, I get the following error message when reportbug tries to execute the bug script: | Gathering additional data, this may take a while... | Include network configuration and status from this computer? y | pcilib: Cannot open /proc/bus/pci | lspci: Cannot find any working access method. | The package bug script /usr/share/bug/linux-image-2.6.32-5-s390x/script exited with an error status (return code = 256). Do you still want to file a report? [y|N|q|?]? y The call to PCI utilities should not cause the script to fail on architectures that don't have a PCI bus. Kind regards Philipp Kern -- Package-specific info: ** Version: Linux version 2.6.32-5-s390x (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:22:54 UTC 2011 ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 3.0.0-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_3.0.0-4.diff.gz to main/l/linux-2.6/linux-2.6_3.0.0-4.diff.gz linux-2.6_3.0.0-4.dsc to main/l/linux-2.6/linux-2.6_3.0.0-4.dsc linux-doc-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-4_all.deb linux-manual-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-4_all.deb linux-patch-debian-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-4_all.deb linux-source-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-source-3.0.0_3.0.0-4_all.deb linux-support-3.0.0-1_3.0.0-4_all.deb to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 639...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 19 Sep 2011 14:40:42 +0100 Source: linux-2.6 Binary: linux-tools-3.0.0 linux-source-3.0.0 linux-doc-3.0.0 linux-manual-3.0.0 linux-patch-debian-3.0.0 linux-support-3.0.0-1 linux-libc-dev linux-headers-3.0.0-1-all linux-headers-3.0.0-1-all-alpha linux-headers-3.0.0-1-common linux-image-3.0.0-1-alpha-generic linux-headers-3.0.0-1-alpha-generic linux-image-3.0.0-1-alpha-smp linux-headers-3.0.0-1-alpha-smp linux-image-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-all-amd64 linux-image-3.0.0-1-amd64 linux-headers-3.0.0-1-amd64 linux-image-3.0.0-1-amd64-dbg xen-linux-system-3.0.0-1-amd64 linux-headers-3.0.0-1-common-rt linux-image-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-rt-amd64 linux-image-3.0.0-1-rt-amd64-dbg xen-linux-system-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-all-armel linux-image-3.0.0-1-iop32x linux-headers-3.0.0-1-iop32x linux-image-3.0.0-1-ixp4xx linux-headers-3.0.0-1-ixp4xx linux-image-3.0.0-1-kirkwood linux-headers-3.0.0-1-kirkwood linux-image-3.0.0-1-orion5x linux-headers-3.0.0-1-orion5x linux-image-3.0.0-1-versatile linux-headers-3.0.0-1-versatile linux-headers-3.0.0-1-all-armhf linux-image-3.0.0-1-mx5 linux-headers-3.0.0-1-mx5 linux-image-3.0.0-1-omap linux-headers-3.0.0-1-omap linux-headers-3.0.0-1-all-hppa linux-image-3.0.0-1-parisc linux-headers-3.0.0-1-parisc linux-image-3.0.0-1-parisc-smp linux-headers-3.0.0-1-parisc-smp linux-image-3.0.0-1-parisc64 linux-headers-3.0.0-1-parisc64 linux-image-3.0.0-1-parisc64-smp linux-headers-3.0.0-1-parisc64-smp linux-headers-3.0.0-1-all-i386 linux-image-3.0.0-1-486 linux-headers-3.0.0-1-486 linux-image-3.0.0-1-686-pae linux-headers-3.0.0-1-686-pae linux-image-3.0.0-1-686-pae-dbg xen-linux-system-3.0.0-1-686-pae linux-headers-3.0.0-1-all-ia64 linux-image-3.0.0-1-itanium
Bug#639949: marked as done (linux-image-3.0.0-1-sparc64-smp: Kernel fails to boot with illegal instruction on ultrasparc V240)
Your message dated Tue, 20 Sep 2011 05:34:38 + with message-id e1r5syc-0003xz...@franck.debian.org and subject line Bug#639949: fixed in linux-2.6 3.0.0-4 has caused the Debian Bug report #639949, regarding linux-image-3.0.0-1-sparc64-smp: Kernel fails to boot with illegal instruction on ultrasparc V240 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 639949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-3 Severity: important Dear Maintainer, Kernel fails to boot on my V240 dual processor ultrasparc machine. It does not boot at all. Last kernel known to work is 2.6.39. I join to the but report the output of the boot capture through the serial port. -- Package-specific info: ** Kernel log: boot messages should be attached Boot device: disk File and args: SILO Version 1.4.14 boot: Allocated 64 Megs of memory at 0x4000 for kernel Uncompressing image... Loaded kernel version 3.0.0 Loading initial ramdisk (11381463 bytes at 0x127F00 phys, 0x40C0 virt)... [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 4.22.33 2007/06/18 12:45' [0.00] PROMLIB: Root node compatible: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.0.0-1-sparc64-smp (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 19:51:14 UTC 2011 [0.00] bootconsole [earlyprom0] enabled [0.00] ARCH: SUN4U [0.00] Ethernet address: 00:03:ba:83:9d:e5 [0.00] Kernel: Using 2 locked TLB entries for main kernel image. [0.00] Remapping the kernel... done. [0.00] OF stdout device is: /pci@1e,60/isa@7/serial@0,3f8 [0.00] PROM: Built device tree with 91187 bytes of memory. [0.00] Top of RAM: 0x127fee8000, Total RAM: 0x1ffe78000 [0.00] Memory hole size: 67584MB [0.00] [0100-f840] page_structs=131072 node=0 entry=0/8192 [0.00] [0100-f880] page_structs=131072 node=0 entry=1/8192 [0.00] [01000200-f8c0] page_structs=131072 node=0 entry=8/8192 [0.00] [01000200-f8000100] page_structs=131072 node=0 entry=9/8192 [0.00] [01000400-f8000140] page_structs=131072 node=0 entry=16/8192 [0.00] [01000400-f8000180] page_structs=131072 node=0 entry=17/8192 [0.00] [01000480-f80001c0] page_structs=131072 node=0 entry=18/8192 [0.00] [01000480-f8000200] page_structs=131072 node=0 entry=19/8192 [0.00] [01002000-f8000240] page_structs=131072 node=0 entry=128/8192 [0.00] [01002000-f8000280] page_structs=131072 node=0 entry=129/8192 [0.00] [01002080-f80002c0] page_structs=131072 node=0 entry=130/8192 [0.00] [01002080-f8000300] page_structs=131072 node=0 entry=131/8192 [0.00] [01002400-f8000340] page_structs=131072 node=0 entry=144/8192 [0.00] [01002400-f8000380] page_structs=131072 node=0 entry=145/8192 [0.00] [01002480-f80003c0] page_structs=131072 node=0 entry=146/8192 [0.00] [01002480-f8000400] page_structs=131072 node=0 entry=147/8192 [0.00] Zone PFN ranges: [0.00] Normal 0x - 0x0093ff74 [0.00] Movable zone start PFN for each node [0.00] early_node_map[9] active PFN ranges [0.00] 0: 0x - 0x0002 [0.00] 0: 0x0008 - 0x000a [0.00] 0: 0x0010 - 0x0014 [0.00] 0: 0x0080 - 0x0084 [0.00] 0: 0x0090 - 0x0093f7ff [0.00] 0: 0x0093f800 - 0x0093ff30 [0.00] 0: 0x0093ff38 - 0x0093ff40 [0.00] 0: 0x0093ff48 - 0x0093ff49 [0.00] 0: 0x0093ff70 - 0x0093ff74 [0.00] Booting Linux... [0.00] CPU CAPS: [flush,stbar,swap,muldiv,v9,ultra3,mul32,div32] [0.00] CPU CAPS: [v8plus,popc,vis,vis2] [0.00] \|/ \|/ [0.00] @'/ .. \`@ [0.00] /_| \__/ |_\ [0.00] \__U_/ [0.00] swapper(0): Kernel illegal instruction [#1] [0.00] TSTATE: 001180e01605 TPC: 005e0920 TNPC: 005e0924 Y: Not tainted [0.00] TPC: __ffs+0x8/0x88 [
Bug#641487: marked as done ([L10N,DE] linux-2.6: updated german debconf translation)
Your message dated Tue, 20 Sep 2011 05:34:38 + with message-id e1r5syc-0003y2...@franck.debian.org and subject line Bug#641487: fixed in linux-2.6 3.0.0-4 has caused the Debian Bug report #641487, regarding [L10N,DE] linux-2.6: updated german debconf translation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 641487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Tags: patch,l10n Attached is the updated german debconf translation for linux-2.6 version 3.0.0-3. Please include it in the linux-2.6 package. Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 3.0.2 under DEBIAN GNU/LINUX 6.0 - S q u e e z e Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = linux-2.6_3.0.0-3_de.po.tar.gz Description: Binary data ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 3.0.0-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_3.0.0-4.diff.gz to main/l/linux-2.6/linux-2.6_3.0.0-4.diff.gz linux-2.6_3.0.0-4.dsc to main/l/linux-2.6/linux-2.6_3.0.0-4.dsc linux-doc-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-4_all.deb linux-manual-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-4_all.deb linux-patch-debian-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-4_all.deb linux-source-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-source-3.0.0_3.0.0-4_all.deb linux-support-3.0.0-1_3.0.0-4_all.deb to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 641...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 19 Sep 2011 14:40:42 +0100 Source: linux-2.6 Binary: linux-tools-3.0.0 linux-source-3.0.0 linux-doc-3.0.0 linux-manual-3.0.0 linux-patch-debian-3.0.0 linux-support-3.0.0-1 linux-libc-dev linux-headers-3.0.0-1-all linux-headers-3.0.0-1-all-alpha linux-headers-3.0.0-1-common linux-image-3.0.0-1-alpha-generic linux-headers-3.0.0-1-alpha-generic linux-image-3.0.0-1-alpha-smp linux-headers-3.0.0-1-alpha-smp linux-image-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-alpha-legacy linux-headers-3.0.0-1-all-amd64 linux-image-3.0.0-1-amd64 linux-headers-3.0.0-1-amd64 linux-image-3.0.0-1-amd64-dbg xen-linux-system-3.0.0-1-amd64 linux-headers-3.0.0-1-common-rt linux-image-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-rt-amd64 linux-image-3.0.0-1-rt-amd64-dbg xen-linux-system-3.0.0-1-rt-amd64 linux-headers-3.0.0-1-all-armel linux-image-3.0.0-1-iop32x linux-headers-3.0.0-1-iop32x linux-image-3.0.0-1-ixp4xx linux-headers-3.0.0-1-ixp4xx linux-image-3.0.0-1-kirkwood linux-headers-3.0.0-1-kirkwood linux-image-3.0.0-1-orion5x linux-headers-3.0.0-1-orion5x linux-image-3.0.0-1-versatile linux-headers-3.0.0-1-versatile linux-headers-3.0.0-1-all-armhf linux-image-3.0.0-1-mx5 linux-headers-3.0.0-1-mx5 linux-image-3.0.0-1-omap linux-headers-3.0.0-1-omap linux-headers-3.0.0-1-all-hppa linux-image-3.0.0-1-parisc linux-headers-3.0.0-1-parisc linux-image-3.0.0-1-parisc-smp linux-headers-3.0.0-1-parisc-smp linux-image-3.0.0-1-parisc64 linux-headers-3.0.0-1-parisc64 linux-image-3.0.0-1-parisc64-smp linux-headers-3.0.0-1-parisc64-smp linux-headers-3.0.0-1-all-i386 linux-image-3.0.0-1-486 linux-headers-3.0.0-1-486 linux-image-3.0.0-1-686-pae linux-headers-3.0.0-1-686-pae linux-image-3.0.0-1-686-pae-dbg xen-linux-system-3.0.0-1-686-pae linux-headers-3.0.0-1-all-ia64 linux-image-3.0.0-1-itanium linux-headers-3.0.0-1-itanium linux-image-3.0.0-1-mckinley linux-headers-3.0.0-1-mckinley linux-headers-3.0.0-1-all-m68k linux-image-3.0.0-1-amiga linux-headers-3.0.0-1-amiga linux-image-3.0.0-1-atari linux-headers-3.0.0-1-atari linux-image-3.0.0-1-bvme6000 linux-headers-3.0.0-1-bvme6000 linux-image-3.0.0-1-mac linux-headers-3.0.0-1-mac
linux-2.6_3.0.0-4_multi.changes ACCEPTED into unstable
Accepted: linux-2.6_3.0.0-4.diff.gz to main/l/linux-2.6/linux-2.6_3.0.0-4.diff.gz linux-2.6_3.0.0-4.dsc to main/l/linux-2.6/linux-2.6_3.0.0-4.dsc linux-doc-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-doc-3.0.0_3.0.0-4_all.deb linux-manual-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-manual-3.0.0_3.0.0-4_all.deb linux-patch-debian-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-patch-debian-3.0.0_3.0.0-4_all.deb linux-source-3.0.0_3.0.0-4_all.deb to main/l/linux-2.6/linux-source-3.0.0_3.0.0-4_all.deb linux-support-3.0.0-1_3.0.0-4_all.deb to main/l/linux-2.6/linux-support-3.0.0-1_3.0.0-4_all.deb Override entries for your package: linux-2.6_3.0.0-4.dsc - source devel linux-doc-3.0.0_3.0.0-4_all.deb - optional doc linux-manual-3.0.0_3.0.0-4_all.deb - optional doc linux-patch-debian-3.0.0_3.0.0-4_all.deb - optional kernel linux-source-3.0.0_3.0.0-4_all.deb - optional kernel linux-support-3.0.0-1_3.0.0-4_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 636242 636531 637740 638696 639439 639949 641487 Thank you for your contribution to Debian. -- 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/e1r5syb-0003xb...@franck.debian.org
