Bug#576723: linux-2.6: [2.6.33] mising rt2860sta; rt2800 not suitable for, replacement

[Andreas Fackler]

The rtl8187se driver also seems to be missing. My Realtek 8187SE does
not work with the rtl8187 driver and thus is unusable with
linux-image-2.6.33-2-amd64.



-- 
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/4be66e8a.9060...@gmx.de

Bug#580855: linux-2.6: [INTL:ja] initial Japanese debconf translation

[Kenshi Muto]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: linux-2.6
Severity: wishlist
Tags: l10n patch

Hi,

I translated debconf messages into Japanese (ja.po).
Please apply this.

Thanks,
- -- 
Kenshi Muto
km...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ 

iQIcBAEBCgAGBQJL5ot1AAoJEB0hyD3EUuD8mHcP/Aj9jmEBMLhIKc6SSX1rrarx
R8Ul/XaG7WLbhm708HLqlHFct7t7MLZqSKMJyn28gfjkyZY3yxi6Fvq5S+cZNqmx
2TgUfloV4K+nNyArKax49i7T/YWqu8bzyVF/3vAf2xqpAG2JSCSKoj+9zJRda8Um
fEc9WHQTBqD8mRuAOAcSe/ITltrQanH5wJSs46BaNwVRgk6uld5JswRX88N7fTx6
28ye1AGEYnhya9TwXvifcc+aeK3yhf9DaC73jxUKUsV2ExN/qODdxn5gEI4zbP42
6tWeDPm2Ahrs7PH1T1mqudG50uXeuMeOIdBm6GA7fyC0P6c2IlF9szUdVJys2kYk
j7W9VzWBVliFWaaZze554jlj6kvX3Ickod5BTR7asx8eBn6HTAm6Q5C6FJNjYa72
/4YL895ml9Oo2pmBVCwy89+Y/hPOB84l4SD8ypfnSJl7yrUjWkys5no9iIxhSKIo
Hf1C7WK3mlA9J5sMPC4zd0yOqH2S2c+G6za5Lz7Qf184+3U2vMMVQzKjsclBPxfJ
Exym4VYFRQIKgodnv4YcFV9XS4XcTKO3GvEUI195uCbqMpL8fYnpPToHiLBkEKhz
SzDwr0D39KQcuA7Qssbx8BnkTLj0qvcfWDOk7o1zUaVf88IHMb/Iq2oh7wxVnf8K
Beh7JGGZ7+Wiq5tqCUNH
=9DWE
-END PGP SIGNATURE-


ja.po
Description: Binary data

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

[Arne Nordmark]

I find a similar oops very reliably whenever there is moderate network 
traffic, like updating squeeze. This happens on 2.6.32-3-686, 
2.6.32-5-686, and 2.6.33-2-686 from experimental, but not at all on the 
earlier squeeze kernel 2.6.30-2-686. Soon after this the system locks up 
completely.


This makes the b43 driver in the current kernels more or less unusable 
for me.


May  8 09:17:22 dhcp190 kernel: [  724.536095] pcmcia_socket 
pcmcia_socket1: pccard: CardBus card inserted into slot 1
May  8 09:17:22 dhcp190 kernel: [  724.536151] pci :06:00.0: reg 10 
32bit mmio: [0x00-0x001fff]
May  8 09:17:22 dhcp190 kernel: [  724.805197] b43-pci-bridge 
:06:00.0: enabling device ( -> 0002)
May  8 09:17:22 dhcp190 kernel: [  724.805231] b43-pci-bridge 
:06:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
May  8 09:17:22 dhcp190 kernel: [  724.805255] b43-pci-bridge 
:06:00.0: setting latency timer to 64
May  8 09:17:22 dhcp190 kernel: [  724.864209] ssb: Sonics Silicon 
Backplane found on PCI device :06:00.0
May  8 09:17:22 dhcp190 kernel: [  725.054869] cfg80211: Using static 
regulatory domain info
May  8 09:17:22 dhcp190 kernel: [  725.054880] cfg80211: Regulatory 
domain: US
May  8 09:17:22 dhcp190 kernel: [  725.054887]  (start_freq - end_freq @ 
bandwidth), (max_antenna_gain, max_eirp)
May  8 09:17:22 dhcp190 kernel: [  725.054898]  (2402000 KHz - 2472000 
KHz @ 4 KHz), (600 mBi, 2700 mBm)
May  8 09:17:22 dhcp190 kernel: [  725.054909]  (517 KHz - 519 
KHz @ 4 KHz), (600 mBi, 2300 mBm)
May  8 09:17:22 dhcp190 kernel: [  725.054919]  (519 KHz - 521 
KHz @ 4 KHz), (600 mBi, 2300 mBm)
May  8 09:17:22 dhcp190 kernel: [  725.054928]  (521 KHz - 523 
KHz @ 4 KHz), (600 mBi, 2300 mBm)
May  8 09:17:22 dhcp190 kernel: [  725.054938]  (523 KHz - 533 
KHz @ 4 KHz), (600 mBi, 2300 mBm)
May  8 09:17:22 dhcp190 kernel: [  725.054948]  (5735000 KHz - 5835000 
KHz @ 4 KHz), (600 mBi, 3000 mBm)
May  8 09:17:22 dhcp190 kernel: [  725.055883] cfg80211: Calling CRDA 
for country: US
May  8 09:17:23 dhcp190 kernel: [  725.339020] b43-phy0: Broadcom 4318 
WLAN found (core revision 9)
May  8 09:17:23 dhcp190 kernel: [  725.484659] phy0: Selected rate 
control algorithm 'minstrel'
May  8 09:17:23 dhcp190 kernel: [  725.489340] Registered led device: 
b43-phy0::tx
May  8 09:17:23 dhcp190 kernel: [  725.489487] Registered led device: 
b43-phy0::rx
May  8 09:17:23 dhcp190 kernel: [  725.489648] Registered led device: 
b43-phy0::radio
May  8 09:17:23 dhcp190 kernel: [  725.492774] Broadcom 43xx driver 
loaded [ Features: PMLS, Firmware-ID: FW13 ]
May  8 09:17:23 dhcp190 kernel: [  725.712092] b43 ssb0:0: firmware: 
requesting b43/ucode5.fw
May  8 09:17:24 dhcp190 kernel: [  726.215534] b43 ssb0:0: firmware: 
requesting b43/pcm5.fw
May  8 09:17:24 dhcp190 kernel: [  726.240275] b43 ssb0:0: firmware: 
requesting b43/b0g0initvals5.fw
May  8 09:17:24 dhcp190 kernel: [  726.265028] b43 ssb0:0: firmware: 
requesting b43/b0g0bsinitvals5.fw
May  8 09:17:24 dhcp190 kernel: [  726.408095] b43-phy0: Loading 
firmware version 410.2160 (2007-05-26 15:32:10)
May  8 09:17:24 dhcp190 kernel: [  726.590883] ADDRCONF(NETDEV_UP): 
wlan0: link is not ready
May  8 09:17:26 dhcp190 kernel: [  729.008521] wlan0: direct probe to AP 
00:80:c8:19:b5:f4 (try 1)
May  8 09:17:27 dhcp190 kernel: [  729.208094] wlan0: direct probe to AP 
00:80:c8:19:b5:f4 (try 2)

May  8 09:17:27 dhcp190 kernel: [  729.209492] wlan0: direct probe responded
May  8 09:17:27 dhcp190 kernel: [  729.209503] wlan0: authenticate with 
AP 00:80:c8:19:b5:f4 (try 1)

May  8 09:17:27 dhcp190 kernel: [  729.20] wlan0: authenticated
May  8 09:17:27 dhcp190 kernel: [  729.211173] wlan0: associate with AP 
00:80:c8:19:b5:f4 (try 1)
May  8 09:17:27 dhcp190 kernel: [  729.215767] wlan0: RX AssocResp from 
00:80:c8:19:b5:f4 (capab=0x471 status=0 aid=1)

May  8 09:17:27 dhcp190 kernel: [  729.215779] wlan0: associated
May  8 09:17:27 dhcp190 kernel: [  729.217770] ADDRCONF(NETDEV_CHANGE): 
wlan0: link becomes ready
May  8 09:17:27 dhcp190 kernel: [  729.225075] cfg80211: Calling CRDA 
for country: EU
May  8 09:35:48 dhcp190 kernel: [ 1830.644213] BUG: scheduling while 
atomic: irq/11-b43/2018/0x0101
May  8 09:35:48 dhcp190 kernel: [ 1830.644225] Modules linked in: arc4 
ecb b43 rng_core mac80211 cfg80211 led_class ssb mmc_core isofs udf 
crc_itu_t r128 drm ppdev lp sco bridge stp bnep l2cap crc16 bluetooth
 rfkill speedstep_lib cpufreq_userspace cpufreq_conservative 
cpufreq_powersave cpufreq_stats binfmt_misc uinput fuse loop 
snd_maestro3 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm 
snd_page_alloc
snd_seq_midi snd_rawmidi snd_seq_midi_event pcmcia snd_seq joydev 
snd_timer yenta_socket snd_seq_device rsrc_nonstatic pcmcia_core 
i2c_piix4 parport_pc snd tpm_tis parport dcdbas tpm i2c_core processor 
batter
y ac soundcore shpchp tpm_bios psmouse pcspkr serio_raw evdev 
pci_hotplug

Bug#580068: Bug#580050: linux-image-2.6.32-3-amd64: kcryptd crashes under heavy I/O

[Juha]

Hello,

this turned out to be a hardware problem so this bug can be closed.

Regards,
Juha



-- 
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/aanlktikxdaxzxddp5jp_up32wcmunb1egniipzari...@mail.gmail.com

Bug#580068: marked as done (Data corruption using NFS + dm-crypt)

[Debian Bug Tracking System]

Your message dated Sun, 9 May 2010 16:22:48 +0200
with message-id <20100509142248.gd13...@baikonur.stro.at>
and subject line Re: Bug#580068: Bug#580050: linux-image-2.6.32-3-amd64: 
kcryptd  crashes under heavy I/O
has caused the Debian Bug report #580068,
regarding Data corruption using NFS + dm-crypt
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.)


-- 
580068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-9
Severity: critical
Justification: breaks the whole system

Hello,

I have the following setup in my system: 6 x 500GB drives with software RAID6 + 
encryption (luks) + LVM. This is a new installation and I'm having troubles 
with encryption. Every once and a while kcryptd crashes and system becomes 
unresponsive. Well it responds to ping and currently running applications will 
continue running (if they don't need disk access I suppose) but I'm unable to 
ssh to the box anymore or run any new applications.

These crashes (always?) happen when there are lots of I/O going on. Ie. I can 
reproduce these crashes easily.

I have tested this with latest stable kernel version 2.6.33.3 but the problem 
persists.

I don't know if this is related to this or a different bug but I also noticed 
that when I transfer lots of files over nfs from my previous system about 5% of 
these files are corrupted. Ie. checksums do not match. Sometimes I need to 
transfer these files several times before everything is transferred ok. I'm 
able to transfer these files to my other box with no problems. Data gets 
corrupted only when transferring files to the box having this kcryptd problem.

Nothing appears in system logs after the crash but I was able to get the 
following using netconsole:

[ 3295.969539] [ cut here ]
[ 3295.969580] kernel BUG at 
/build/mattems-linux-2.6_2.6.32-9-amd64-NYTFdD/linux-2.6-2.6.32-9/debian/build/source_amd64_none/include/linux/scatterlist.h:63!
[ 3295.969627] invalid opcode:  [#1] SMP 
[ 3295.969654] last sysfs file: /sys/module/nfsd/initstate
[ 3295.969678] CPU 1 
[ 3295.969699] Modules linked in: autofs4 nfsd exportfs nfs lockd fscache 
nfs_acl auth_rpcgss sunrpc ext2 netconsole configfs loop snd_hda_codec_realtek 
snd_hda_intel psmouse snd_hda_codec snd_hwdep parport_pc snd_pcm edac_core 
parport asus_atk0110 snd_timer serio_raw edac_mce_amd snd pcspkr evdev 
i2c_nforce2 soundcore wmi snd_page_alloc i2c_core button processor ext4 mbcache 
jbd2 crc16 sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod 
raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx 
raid1 md_mod sd_mod crc_t10dif ata_generic ide_pci_generic ahci ohci_hcd 
amd74xx floppy ehci_hcd libata forcedeth scsi_mod ide_core usbcore nls_base 
thermal thermal_sys [last unloaded: scsi_wait_scan]
[ 3295.970250] Pid: 450, comm: kcryptd Not tainted 2.6.32-3-amd64 #1 System 
Product Name
[ 3295.970287] RIP: 0010:[]  [] 
crypt_convert+0xe9/0x269 [dm_crypt]
[ 3295.970336] RSP: 0018:88012c39fd80  EFLAGS: 00010206
[ 3295.970360] RAX: 0002 RBX: 8800358533c0 RCX: 0002
[ 3295.970386] RDX: b2901491843e73a7 RSI:  RDI: 26726b70
[ 3295.970412] RBP: 88012b86f330 R08:  R09: 0001
[ 3295.970438] R10: 88012ba548d0 R11:  R12: 88003585fff0
[ 3295.970464] R13: 88012b86f200 R14: 88012c351000 R15: 
[ 3295.970492] FS:  7fb5063f86f0() GS:88000548() 
knlGS:
[ 3295.970530] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
[ 3295.970554] CR2: 7f5f81faf000 CR3: 00012054c000 CR4: 06e0
[ 3295.970580] DR0:  DR1:  DR2: 
[ 3295.970606] DR3:  DR6: 0ff0 DR7: 0400
[ 3295.970633] Process kcryptd (pid: 450, threadinfo 88012c39e000, task 
88012cb0cdb0)
[ 3295.970669] Stack:
[ 3295.970687]  880035853408 0003 8801d000 
88012b86f338
[ 3295.970776] <0> 88012ba54800 8800ceaf83c0  
0202
[ 3295.970827] <0> 880035853390 df00  
a0187fec
[ 3295.970892] Call Trace:
[ 3295.970919]  [] ? kcryptd_crypt+0x40f/0x432 [dm_crypt]
[ 3295.970951]  [] ? worker_thread+0x188/0x21d
[ 3295.970979]  [] ? kcryptd_crypt+0x0/0x432 [dm_crypt]
[ 3295.971008]  [] ? autoremove_wake_function+0x0/0x2e
[ 3295.971035]  [] ? worker_thread+0x0/0x21d
[ 3295.971

Bug#580832: lsmod from linux-image-2.6.32-3-powerpc64

[maximilian attems]

On Sun, May 09, 2010 at 01:26:44PM +1000, Erik de Castro Lopo wrote:
> maximilian attems wrote:
> 
> > they used to be hardcoded loaded by initramfs.
> > 
> > thought that powerpc plattform code had catched up and
> > that udev would just load them.
> > 
> > as workaround put aboves line in /etc/modules.
> > 
> > this needs to be reported to the powerpc linux-2.6 maintainers,
> > thanks.
> 
> How do I do that?

there mailinglist is linuxppc-...@ozlabs.org, listed maintainers:
M:  Benjamin Herrenschmidt 
M:  Paul Mackerras 

another possibility would be to have a bug report on bugzilla.kernel.org
first and then notify them about it. with the bug nr the progress of
that bugreport can be tracked here in debian.


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/20100509142049.gc13...@baikonur.stro.at

Bug#580889: linux-image-2.6.32-3-amd64: tasks get stuck at pvclock_clocksource_read under xen

[Timo Juhani Lindfors]

Package: linux-2.6
Version: 2.6.32-9
Severity: normal

Sometimes when I download large files with iceweasel to my home
directory (which is on NFS) some processes seem to get stuck. xen
console prints the following errors. I do not know how to reproduce
this but it has happened three times in a week now.

Dom0 runs SUSE and shows the following info about xen:

$ sudo xm info
lindi's password:
host   : overlord1
release: 2.6.31.12-0.1-xen
version: #1 SMP 2010-01-27 08:20:11 +0100
machine: x86_64
nr_cpus: 4
nr_nodes   : 1
cores_per_socket   : 4
threads_per_core   : 1
cpu_mhz: 2394
hw_caps: 
bfebfbff:20100800::0140:e3bd::0001:
virt_caps  : hvm
total_memory   : 8189
free_memory: 20
max_free_memory: 394
max_para_memory: 390
max_hvm_memory : 381
node_to_cpu: node0:0-3
node_to_memory : node0:20
xen_major  : 3
xen_minor  : 4
xen_extra  : .1_19718_04-2.1
xen_caps   : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler  : credit
xen_pagesize   : 4096
platform_params: virt_start=0x8000
xen_changeset  : 19718
cc_compiler: gcc version 4.4.1 [gcc-4_4-branch revision 150839] 
(SUSE Linux)
cc_compile_by  : abuild
cc_compile_domain  :
cc_compile_date: Tue Oct 27 16:31:01 UTC 2009
xend_config_format : 4



INFO: task kswapd0:30 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kswapd0   D 0002 030  2 0x
 88003fdc0e20 0246  88003de5b900
 0001 2ea7 f8a0 88003de5bfd8
 000155c0 000155c0 88003fe3d4c0 88003fe3d7b8
Call Trace:
 [] ? pvclock_clocksource_read+0x3a/0x70
 [] ? nfs_wait_bit_uninterruptible+0x0/0xd [nfs]
 [] ? nfs_wait_bit_uninterruptible+0x0/0xd [nfs]
 [] ? io_schedule+0x73/0xb7
 [] ? nfs_wait_bit_uninterruptible+0x9/0xd [nfs]
 [] ? _spin_unlock_irqrestore+0xd/0xe
 [] ? __wait_on_bit+0x41/0x70
 [] ? __lookup_tag+0xad/0x11b
 [] ? nfs_wait_bit_uninterruptible+0x0/0xd [nfs]
 [] ? out_of_line_wait_on_bit+0x6b/0x77
 [] ? wake_bit_function+0x0/0x23
 [] ? nfs_sync_mapping_wait+0xfa/0x227 [nfs]
 [] ? nfs_wb_page+0x94/0xc3 [nfs]
 [] ? __remove_from_page_cache+0x33/0xb6
 [] ? nfs_release_page+0x3a/0x57 [nfs]
 [] ? shrink_page_list+0x481/0x617
 [] ? isolate_pages_global+0x1a0/0x20f
 [] ? shrink_list+0x44a/0x725
 [] ? determine_dirtyable_memory+0xd/0x1d
 [] ? get_dirty_limits+0x1d/0x259
 [] ? shrink_zone+0x280/0x342
 [] ? _spin_unlock_irqrestore+0xd/0xe
 [] ? shrink_slab+0x141/0x153
 [] ? kswapd+0x4b9/0x683
 [] ? isolate_pages_global+0x0/0x20f
 [] ? autoremove_wake_function+0x0/0x2e
 [] ? check_events+0x12/0x20
 [] ? kswapd+0x0/0x683
 [] ? kthread+0x79/0x81
 [] ? child_rip+0xa/0x20
 [] ? int_ret_from_sys_call+0x7/0x1b
 [] ? retint_restore_args+0x5/0x6
 [] ? child_rip+0x0/0x20
INFO: task firefox-bin:1669 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
firefox-bin   D  0  1669  1 0x
 8144b1f0 0286  000ecf18
 0001 9a59 f8a0 88003f02bfd8
 000155c0 000155c0 8800029a3170 8800029a3468
Call Trace:
 [] ? pvclock_clocksource_read+0x3a/0x70
 [] ? nfs_wait_bit_uninterruptible+0x0/0xd [nfs]
 [] ? io_schedule+0x73/0xb7
 [] ? nfs_wait_bit_uninterruptible+0x9/0xd [nfs]
 [] ? _spin_unlock_irqrestore+0xd/0xe
 [] ? __wait_on_bit+0x41/0x70
 [] ? __lookup_tag+0xad/0x11b
 [] ? nfs_wait_bit_uninterruptible+0x0/0xd [nfs]
 [] ? out_of_line_wait_on_bit+0x6b/0x77
 [] ? wake_bit_function+0x0/0x23
 [] ? nfs_sync_mapping_wait+0xfa/0x227 [nfs]
 [] ? nfs_wb_page+0x94/0xc3 [nfs]
 [] ? __remove_from_page_cache+0x33/0xb6
 [] ? nfs_release_page+0x3a/0x57 [nfs]
 [] ? shrink_page_list+0x481/0x617
 [] ? isolate_pages_global+0x1a0/0x20f
 [] ? shrink_list+0x44a/0x725
 [] ? determine_dirtyable_memory+0xd/0x1d
 [] ? get_dirty_limits+0x1d/0x259
 [] ? xen_restore_fl_direct_end+0x0/0x1
 [] ? get_page_from_freelist+0x4b0/0x754
 [] ? shrink_zone+0x280/0x342
 [] ? _spin_unlock_irqrestore+0xd/0xe
 [] ? shrink_slab+0x141/0x153
 [] ? try_to_free_pages+0x232/0x38e
 [] ? isolate_pages_global+0x0/0x20f
 [] ? __alloc_pages_nodemask+0x3bb/0x5ce
 [] ? hypercall_page+0x22a/0x1001
 [] ? new_slab+0x42/0x1ca
 [] ? __slab_alloc+0x1f0/0x39b
 [] ? nfs_writedata_alloc+0x74/0x98 [nfs]
 [] ? __kmalloc+0xf1/0x141
 [] ? __lookup_tag+0xad/0x11b
 [] ? nfs_writedata_alloc+0x74/0x98 [nfs]
 [] ? nfs_writedata_alloc+0x74/0x98 [nfs]
 [] ? nfs_flush_one+0x14/0xce [nfs]
 [] ? nfs_pageio_doio+0x2a/0x51 [nfs]
 [] ? nfs

Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate

[Ritesh Raj Sarraf]

On Thursday 06 May 2010 07:16:01 Ben Hutchings wrote:
> On Mon, 2010-05-03 at 23:58 +0530, Ritesh Raj Sarraf wrote:
> > Package: linux-2.6
> > Version: 2.6.32-11
> > Severity: normal
> > 
> > I often keep getting this allocation failure message. My gut feel is
> > that it gets triggered when I do some I/O. Today, it got triggered when
> > I was copying a couple of Gig data from my local encrypted backup
> > partition to an external USB disk.
> [...]
> 
> This is a bug/limitation in the iwlwifi drivers.  It appears to be fixed
> in Linux 2.6.33, but it requires quite a large change.  The next release
> of Debian will be based on Linux 2.6.32 and I don't know whether we will
> be able to apply that change.
> 

Too bad. There will be many users using this wifi device. :-(
And the symptom is also not a good one. When the bug triggers, it seems to 
almost eat
down all of your memory.

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
"Necessity is the mother of invention."


signature.asc
Description: This is a digitally signed message part.

Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate

[Ritesh Raj Sarraf]

On Sunday 09 May 2010 21:38:25 Ritesh Raj Sarraf wrote:
> On Thursday 06 May 2010 07:16:01 Ben Hutchings wrote:
> > On Mon, 2010-05-03 at 23:58 +0530, Ritesh Raj Sarraf wrote:
> > > Package: linux-2.6
> > > Version: 2.6.32-11
> > > Severity: normal
> > > 
> > > I often keep getting this allocation failure message. My gut feel is
> > > that it gets triggered when I do some I/O. Today, it got triggered when
> > > I was copying a couple of Gig data from my local encrypted backup
> > > partition to an external USB disk.
> > [...]
> > 
> > This is a bug/limitation in the iwlwifi drivers.  It appears to be fixed
> > in Linux 2.6.33, but it requires quite a large change.  The next release
> > of Debian will be based on Linux 2.6.32 and I don't know whether we will
> > be able to apply that change.
> > 
> 
> Too bad. There will be many users using this wifi device. :-(
> And the symptom is also not a good one. When the bug triggers, it seems to 
> almost eat
> down all of your memory.
> 
> 


Ben,

I think this bug is more than the iwlwifi driver.

While this kernel message is from the 2.6.33 kernel, I think the bug is the 
same one.

May  9 22:07:07 champaran kernel: [34858.683705] Xorg: page allocation failure. 
order:1, mode:0x50d0
May  9 22:07:07 champaran kernel: [34858.683710] Pid: 2860, comm: Xorg Not 
tainted 2.6.33-2-amd64 #1
May  9 22:07:07 champaran kernel: [34858.683712] Call Trace:
May  9 22:07:07 champaran kernel: [34858.683724]  [] ? 
__alloc_pages_nodemask+0x56d/0x5e2
May  9 22:07:07 champaran kernel: [34858.683728]  [] ? 
new_slab+0x5b/0x1ca
May  9 22:07:07 champaran kernel: [34858.683731]  [] ? 
__slab_alloc+0x1f0/0x3a2
May  9 22:07:07 champaran kernel: [34858.683735]  [] ? 
agp_alloc_page_array+0x2b/0x4a
May  9 22:07:07 champaran kernel: [34858.683739]  [] ? 
__kmalloc+0xf1/0x141
May  9 22:07:07 champaran kernel: [34858.683741]  [] ? 
agp_alloc_page_array+0x2b/0x4a
May  9 22:07:07 champaran kernel: [34858.683744]  [] ? 
agp_alloc_page_array+0x2b/0x4a
May  9 22:07:07 champaran kernel: [34858.683746]  [] ? 
agp_generic_alloc_user+0x6e/0xe2
May  9 22:07:07 champaran kernel: [34858.683749]  [] ? 
agp_allocate_memory+0x48/0xe8
May  9 22:07:07 champaran kernel: [34858.683802]  [] ? 
drm_agp_bind_pages+0x4e/0xd0 [drm]
May  9 22:07:07 champaran kernel: [34858.683817]  [] ? 
i915_gem_object_bind_to_gtt+0x1c5/0x27a [i915]
May  9 22:07:07 champaran kernel: [34858.683825]  [] ? 
i915_gem_object_pin+0x1e/0x87 [i915]
May  9 22:07:07 champaran kernel: [34858.683834]  [] ? 
i915_gem_do_execbuffer+0x4aa/0xe89 [i915]
May  9 22:07:07 champaran kernel: [34858.683839]  [] ? 
vmap_page_range_noflush+0x287/0x2ec
May  9 22:07:07 champaran kernel: [34858.683842]  [] ? 
map_vm_area+0x25/0x36
May  9 22:07:07 champaran kernel: [34858.683845]  [] ? 
__vmalloc_area_node+0x12e/0x152
May  9 22:07:07 champaran kernel: [34858.683848]  [] ? 
__vmalloc_node+0x5f/0x8e
May  9 22:07:07 champaran kernel: [34858.683856]  [] ? 
i915_gem_execbuffer+0x194/0x223 [i915]
May  9 22:07:07 champaran kernel: [34858.683861]  [] ? 
_lock_kernel+0x53/0x8a
May  9 22:07:07 champaran kernel: [34858.683870]  [] ? 
drm_ioctl+0x260/0x32b [drm]
May  9 22:07:07 champaran kernel: [34858.683873]  [] ? 
__do_fault+0x380/0x3c3
May  9 22:07:07 champaran kernel: [34858.683882]  [] ? 
i915_gem_execbuffer+0x0/0x223 [i915]
May  9 22:07:07 champaran kernel: [34858.683887]  [] ? 
__remove_hrtimer+0x74/0x80
May  9 22:07:07 champaran kernel: [34858.683892]  [] ? 
vfs_ioctl+0x21/0x92
May  9 22:07:07 champaran kernel: [34858.683894]  [] ? 
do_vfs_ioctl+0x495/0x4d3
May  9 22:07:07 champaran kernel: [34858.683898]  [] ? 
do_setitimer+0xbc/0x1d9
May  9 22:07:07 champaran kernel: [34858.683901]  [] ? 
sys_setitimer+0x5c/0x9a
May  9 22:07:07 champaran kernel: [34858.683903]  [] ? 
sys_ioctl+0x51/0x70
May  9 22:07:07 champaran kernel: [34858.683908]  [] ? 
system_call_fastpath+0x16/0x1b
May  9 22:07:07 champaran kernel: [34858.683910] Mem-Info:
May  9 22:07:07 champaran kernel: [34858.683912] Node 0 DMA per-cpu:
May  9 22:07:07 champaran kernel: [34858.683915] CPU0: hi:0, btch:   1 
usd:   0
May  9 22:07:07 champaran kernel: [34858.683917] CPU1: hi:0, btch:   1 
usd:   0
May  9 22:07:07 champaran kernel: [34858.683918] Node 0 DMA32 per-cpu:
May  9 22:07:07 champaran kernel: [34858.683920] CPU0: hi:  186, btch:  31 
usd: 168
May  9 22:07:07 champaran kernel: [34858.683922] CPU1: hi:  186, btch:  31 
usd:   0
May  9 22:07:07 champaran kernel: [34858.683926] active_anon:282314 
inactive_anon:90268 isolated_anon:0
May  9 22:07:07 champaran kernel: [34858.683927]  active_file:140695 
inactive_file:158480 isolated_file:0
May  9 22:07:07 champaran kernel: [34858.683928]  unevictable:0 dirty:6 
writeback:0 unstable:0
May  9 22:07:07 champaran kernel: [34858.683929]  free:7506 
slab_reclaimable:30686 slab_unreclaimable:14882
May  9 22:07:07 champaran kernel: [34858.683930]  mapped:31957 shmem:84560 
pagetables:10876 bounce:0
May  9 22:07:07 champaran kernel: [34

Processed: Re: Bug#580894: linux-image-2.6.32-5-amd65: linux-image-2.6.32-5-amd64 crashes at boot

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 580894 linux-2.6
Bug #580894 [linux-image-2.6.32-5-amd65] linux-image-2.6.32-5-amd65: 
linux-image-2.6.32-5-amd64 crashes at boot
Warning: Unknown package 'linux-image-2.6.32-5-amd65'
Bug reassigned from package 'linux-image-2.6.32-5-amd65' to 'linux-2.6'.
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
580894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580894
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.127342485331676.transcr...@bugs.debian.org

Processed: tagging 498576

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 498576 - l10n
Bug #498576 [linux-2.6] linux-image-2.6.26-1-686: USB Mouse stopped working 
during copying files to USB drive
Removed tag(s) l10n.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
498576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498576
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.12734256478576.transcr...@bugs.debian.org

Bug#580894: linux-image-amd64

[Hans-J. Ullrich]

Dear maintainer-team,

as I did not know, how to reassign, I send the whole text again. Please ignore 
my former message. It is not quite clear for me, which package is affected, IMO 
it is linux-image-2.6.32-5-amd64, although this one is a dependency of linux-
image-amd64 as well as of linux-image-2.6. The affected package is indeed 
linux-image-2.6.32-5-amd64. 

Description: 

I just made an upgrade from kernel linux-image-2.6.32-3-amd64 to -5-amd64.

Sadly I have to tell, thatthe new kernel does not start, more precisely, the 
screen goes black (switches off). 
I can see, that the boot process is going on, until X starts. 

The last thing, I can see, is something with "drm" and "noveau". As it is 
going too fast to read the lines, I checked
the logs. the relevant output (i suppose) is this:

--- snip -

May  9 17:36:40 localhost kernel: [7.531235] input: Acer Crystal Eye 
webcam  as /devices/pci:00/:00:02.1/usb1/1-3/1-3:1.0/input/input10
May  9 17:36:40 localhost kernel: [7.556239] usbcore: registered new 
interface driver uvcvideo
May  9 17:36:40 localhost kernel: [7.581926] USB Video Class driver 
(v0.1.0)
May  9 17:36:40 localhost kernel: [7.632919] [drm] nouveau :02:00.0: 
512 MiB GART (aperture)
May  9 17:36:40 localhost kernel: [7.661120] [drm] nouveau :02:00.0: 
Allocating FIFO number 1
May  9 17:36:40 localhost kernel: [7.661203] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661249] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661294] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661338] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661383] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661427] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661472] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661516] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661560] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661606] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661651] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661694] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661740] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661784] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661829] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661873] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661922] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.661974] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662026] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662080] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662131] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662181] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662233] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662284] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662334] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662385] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662436] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662488] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662540] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662593] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662644] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662695] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 localhost kernel: [7.662744] [drm] nouveau :02:00.0: 
PFIFO_INTR 0x0010 - Ch 127
May  9 17:36:40 loca

Bug#580901: core i3: suspend to disk break multithreading

[Bill Allombert]

Package: linux-2.6
Version: 2.6.32-9
Severity: normal

Dear Debian kernel team,

I have a Sony Vaio laptop with a core i3 processor, dual core and
hyperthreaded to 4 virtual CPUs.  When compiling with 'make -j4', top
show the 4 CPUs used.

After suspend-to-disk however, performance degrade to the equivalent of a
single core system: top still show 4 cpus, but only one CPU ever get
used and compilation time is twice longer (real time). The same happen
with programs using multiple POSIX threads.

I found this report which seems similar but with a core i7:

http://superuser.com/questions/136291/core-i7-on-linux-loses-its-multithreading-capability-after-suspend

Note: I have disabled KMS because it causes segfault after suspend-to-disk
(this is bug 534422). This is a very bare-bone system, X is not running.

Cheers,
Bill.


-- Package-specific info:
** Version:
Linux version 2.6.32-3-amd64 (Debian 2.6.32-9) (m...@debian.org) (gcc version 
4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Feb 24 18:07:42 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-amd64 
root=UUID=cb8e6b0f-b188-4e36-a732-63694c2af4ca ro vga=normal nomodeset quiet

** Not tainted

** Kernel log:
[3.775208] Bluetooth: Generic Bluetooth USB driver ver 0.6
[3.775531] usbcore: registered new interface driver btusb
[3.777348] Monitor-Mwait will be used to enter C-1 state
[3.795821] Linux video capture interface: v2.00
[3.814678] Monitor-Mwait will be used to enter C-2 state
[3.814796] processor LNXCPU:00: registered as cooling_device0
[3.815761] ACPI: SSDT b3690a98 00303 (v01   Sony VAIO 20100107 
INTL 20061109)
[3.816531] ACPI: SSDT b368ed98 00119 (v01   Sony VAIO 20100107 
INTL 20061109)
[3.876520] processor LNXCPU:01: registered as cooling_device1
[3.896722] uvcvideo: Found UVC 1.00 device  (05ca:18b7)
[3.897346] ACPI: AC Adapter [AC] (on-line)
[3.898876] input: UVC Camera (05ca:18b7) as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input6
[3.898987] usbcore: registered new interface driver uvcvideo
[3.899030] USB Video Class driver (v0.1.0)
[3.920889] ACPI: Battery Slot [BAT1] (battery absent)
[3.957380] processor LNXCPU:02: registered as cooling_device2
[4.072640] processor LNXCPU:03: registered as cooling_device3
[4.094364] ACPI: WMI: Mapper loaded
[4.097400] sony-laptop: Sony Notebook Control Driver v0.6.
[4.149822] input: Sony Vaio Keys as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/SNY5001:00/input/input7
[4.150181] input: Sony Vaio Jogdial as /devices/virtual/input/input8
[4.150467] sony-laptop: brightness ignored, must be controlled by ACPI 
video driver
[4.171318] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 
1.3.27ks
[4.171321] iwlagn: Copyright(c) 2003-2009 Intel Corporation
[4.171391] iwlagn :02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[4.171400] iwlagn :02:00.0: setting latency timer to 64
[4.171458] iwlagn :02:00.0: Detected Intel Wireless WiFi Link 6000 
Series 2x2 AGN REV=0x74
[4.196368] iwlagn :02:00.0: Tunable channels: 13 802.11bg, 24 802.11a 
channels
[4.196422]   alloc irq_desc for 35 on node -1
[4.196425]   alloc kstat_irqs on node -1
[4.196446] iwlagn :02:00.0: irq 35 for MSI/MSI-X
[4.256105] phy0: Selected rate control algorithm 'iwl-agn-rs'
[4.268538]   alloc irq_desc for 22 on node -1
[4.268541]   alloc kstat_irqs on node -1
[4.268551] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 
22
[4.268623] HDA Intel :00:1b.0: setting latency timer to 64
[4.567946] EXT3 FS on sda1, internal journal
[4.643992] loop: module loaded
[4.769324] Synaptics Touchpad, model: 1, fw: 7.4, id: 0x1c0b1, caps: 
0xd04731/0xa4
[4.786244] Adding 11718648k swap on /dev/mapper/Debian-swap.  Priority:-1 
extents:1 across:11718648k 
[4.816656] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input9
[4.905589] kjournald starting.  Commit interval 5 seconds
[4.905708] EXT3 FS on dm-5, internal journal
[4.905718] EXT3-fs: mounted filesystem with ordered data mode.
[4.907473] kjournald starting.  Commit interval 5 seconds
[4.907678] EXT3 FS on dm-4, internal journal
[4.907686] EXT3-fs: mounted filesystem with ordered data mode.
[4.909288] kjournald starting.  Commit interval 5 seconds
[4.909431] EXT3 FS on dm-1, internal journal
[4.909438] EXT3-fs: mounted filesystem with ordered data mode.
[4.911040] kjournald starting.  Commit interval 5 seconds
[4.911193] EXT3 FS on dm-2, internal journal
[4.911200] EXT3-fs: mounted filesystem with ordered data mode.
[4.913038] kjournald starting.  Commit interval 5 seconds
[4.913179] EXT3 FS on dm-3, internal journal
[4.913187] EXT3-fs: mounted filesystem with ordered data mode.
[5.097935] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[5.0

Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate

[maximilian attems]

On Sun, May 09, 2010 at 10:16:55PM +0530, Ritesh Raj Sarraf wrote:
> 
> All these messages (this one and the previous one with iwlwifi) get triggered 
> only when there is heavy I/O activity.
> I don't think this bug is related to iwlwifi. What do you think ?

it is, can trigger it easily on x61s, things got better although.
changes are to big to feed them to stable, upstream bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=15766



-- 
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/20100509175650.ge13...@baikonur.stro.at

Bug#579332:

[Orlando Bedoya Marin]

Opps ..
I already reported the bug in bugzilla.kernel
https://bugzilla.kernel.org/show_bug.cgi?id=15949 But this is useless
now
Thanks Jean-Francois Moine



-- 
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/aanlktilt18tc5mzga_io3lyw0-kxp-cp2ixsarfw2...@mail.gmail.com

Bug#580915: [INTL:da] Danish translation of the debconf templates linux-2.6

[Joe Dalton]

Package: linux-2.6
Severity: wishlist
Tags: l10n patch

Please include the attached Danish debconf translation

j...@joe-desktop:~/over/debian/linux26$ msgfmt --statistics -c -v -o /dev/null 
da.po
41 oversatte tekster.

bye
Joe

# Danish translation linux-2.6.
# Copyright (C) 2010 linux-2.6 & Joe Hansen.
# This file is distributed under the same license as the linux-2.6 package.
# Joe Hansen , 2010.
#
msgid ""
msgstr ""
"Project-Id-Version: linux-2.6\n"
"Report-Msgid-Bugs-To: linux-...@packages.debian.org\n"
"POT-Creation-Date: 2010-03-29 14:15+0100\n"
"PO-Revision-Date: 2010-05-09 17:30+01:00\n"
"Last-Translator: Joe Hansen \n"
"Language-Team: Danish  \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../linux-base.templates:1001
msgid "Update disk device ids in system configuration?"
msgstr "Opdater diskenheds-id'er i systemkonfigurationen?"

#. Type: boolean
#. Description
#: ../linux-base.templates:1001
msgid ""
"The new Linux kernel version provides different drivers for some PATA (IDE) "
"controllers.  The names of some hard disk, CD-ROM and tape devices may "
"change."
msgstr ""
"Den nye version af Linuxkernen har forskellige drivere for nogle PATA-kontrollere "
"(IDE). Navnene på nogle harddiske, cd-rom og båndenheder kan skifte."

#. Type: boolean
#. Description
#: ../linux-base.templates:1001
msgid ""
"You are recommended to identify disk devices in configuration files by label "
"or UUID (unique identifier) rather than by device name, which will work with "
"both old and new kernel versions.  Your system configuration can be updated "
"automatically in most cases."
msgstr ""
"Det anbefales at du identificerer diskenheder i konfigurationsfiler med etiket "
"eller UUID (unik identifikation) fremfor via enhedsnavn, som vil virke med "
"både gamle og nye kerneversioner. Din systemkonfiguration kan i de fleste "
"tilfælde automatisk opdateres."

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "Apply these configuration changes to disk device ids?"
msgstr "Anvend disse konfigurationsændringer til diskenheds-id'er?"

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid "These devices will be assigned UUIDs or labels:"
msgstr "Disse enheder vil få tildelt UUID'er eller etiketter:"

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid "${relabel}"
msgstr "${relabel}"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "These configuration files will be updated:"
msgstr "Disse konfigurationsfiler vil blive opdateret:"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "${files}"
msgstr "${files}"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "The device ids will be changed as follows:"
msgstr "Enheds-id'erne vil blive ændret som vist i det følgende:"

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:2001 ../linux-base.templates:3001
msgid "${id_map}"
msgstr "${id_map}"

#. Type: note
#. Description
#: ../linux-base.templates:4001
msgid "Please check these configuration files before rebooting"
msgstr "Tjek venligst disse konfigurationsfiler før genstart"

#. Type: note
#. Description
#: ../linux-base.templates:4001
msgid ""
"These configuration files still use some device names that may change when "
"using the new kernel:"
msgstr ""
"Disse konfigurationsfiler bruger stadig nogle enhedsnavne som måske vil "
"ændre sig, når den nye kerne bruges:"

#. Type: note
#. Description
#: ../linux-base.templates:4001
msgid "${unconverted}"
msgstr "${unconverted}"

#. Type: note
#. Description
#: ../linux-base.templates:5001
msgid "Check the boot loader configuration before rebooting"
msgstr "Tjek opstartsindlæserens (boot loader) konfiguration før genstart"

#. Type: note
#. Description
#: ../linux-base.templates:5001
msgid ""
"The boot loader configuration for this system was not recognised.  These "
"settings in the configuration may need to be updated:"
msgstr ""
"Opstartslæserens (boot loader) konfiguration på dette system blev ikke "
"genkendt. Disse indstillinger i konfigurationen skal måske opdateres:"

#. Type: note
#. Description
#: ../linux-base.templates:5001
msgid ""
" * The root device id passed as a kernel parameter\n"
" * The boot device id used to install and update the boot loader"
msgstr ""
" * Rootenheds-id'et passeret som en kerneparameter\n"
" * Rootenheds-id'et brugt til at installere og opdatere opstartsindlæseren "
"(boot loader)"

#. Type: note
#. Description
#: ../linux-base.templates:5001
msgid ""
"We recommend that you identify these devices by UUID or label, except that "
"on MIPS s

Bug#556009: ath9k disassociates frequently, regression from 2.6.30

[Russ Allbery]

Package: linux-2.6
Severity: normal

There were apparently multiple problems involved here, and the upstream
bug is still open, so I'm not sure whether you want to close this.  But
for the record, my problems were completely resolved by 2.6.32 and have
not recurred.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
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/20100509201844.1918.40721.report...@windlord.stanford.edu

Bug#580925: This error is presenting while installing linux-image-2.6.32-5-686:

[yanu]

Package: linux-2.6
Version: 2.6.32-12
Severity: normal
Tags: sid


Preconfiguring packages ...
Selecting previously deselected package linux-image-2.6.32-5-686.
(Reading database ... 315673 files and directories currently installed.)
Unpacking linux-image-2.6.32-5-686 (from 
.../linux-image-2.6.32-5-686_2.6.32-12_i386.deb) ...
Setting up linux-image-2.6.32-5-686 (2.6.32-12) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-686
Running update-grub.
Generating grub.cfg ...
/usr/sbin/grub-probe: error: no mapping exists for `md5'.
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.32-5-686 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.32-5-686

So it looks like there is a problem with md5.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM 
Controller [8086:29c0] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI 
Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 [8086:2938] (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 [8086:2939] (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 [8086:293c] (rev 02) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci_hcd

00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller [8086:293e] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:829f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express 
Port 1 [8086:2940] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express 
Port 5 [8086:2948] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express 
Port 6 [8086:294a]

Bug#580927: linux-image-2.6.32-5-openvz-686: Uncharging too much ... res shmpages ub

[Achim Schaefer]

Package: linux-2.6
Version: 2.6.32-12
Severity: normal
Tags: sid upstream

Hi,

I get quite a lot of the messages you can find under kernel.log-)

I think the upstream bug is:
http://bugzilla.openvz.org/show_bug.cgi?id=1299
But I don't know how to tell bts...

Thanks

Achim

-- Package-specific info:
** Version:
Linux version 2.6.32-5-openvz-686 (Debian 2.6.32-12) (b...@decadent.org.uk) 
(gcc version 4.3.4 (Debian 4.3.4-10) ) #1 SMP Sat May 1 06:37:28 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-openvz-686 
root=UUID=588e7852-827b-47ea-8078-d6eae5769855 ro video=VGA-1:1024x768 
nmi_watchdog=0 quiet

** Not tainted

** Kernel log:
[  183.917479] Uncharging too much 16113 h 0, res shmpages ub 0
[  183.917494] Uncharging too much 14977 h 0, res shmpages ub 0
[  183.917510] Uncharging too much 15057 h 0, res shmpages ub 0
[  183.917526] Uncharging too much 16161 h 0, res shmpages ub 0
[  183.917542] Uncharging too much 15441 h 0, res shmpages ub 0
[  183.917557] Uncharging too much 15921 h 0, res shmpages ub 0
[  183.917572] Uncharging too much 15937 h 0, res shmpages ub 0
[  183.917588] Uncharging too much 16177 h 0, res shmpages ub 0
[  183.917604] Uncharging too much 16033 h 0, res shmpages ub 0
[  183.917619] Uncharging too much 15473 h 0, res shmpages ub 0
[  183.919288] Uncharging too much 16081 h 0, res shmpages ub 0
[  183.919305] Uncharging too much 15121 h 0, res shmpages ub 0
[  183.919319] Uncharging too much 14881 h 0, res shmpages ub 0
[  183.919332] Uncharging too much 15281 h 0, res shmpages ub 0
[  183.919344] Uncharging too much 15617 h 0, res shmpages ub 0
[  183.919357] Uncharging too much 15889 h 0, res shmpages ub 0
[  183.919369] Uncharging too much 15841 h 0, res shmpages ub 0
[  183.919381] Uncharging too much 15185 h 0, res shmpages ub 0
[  183.919394] Uncharging too much 15425 h 0, res shmpages ub 0
[  183.919406] Uncharging too much 16145 h 0, res shmpages ub 0
[  183.919418] Uncharging too much 15169 h 0, res shmpages ub 0
[  183.919430] Uncharging too much 15729 h 0, res shmpages ub 0
[  183.919443] Uncharging too much 15649 h 0, res shmpages ub 0
[  183.919456] Uncharging too much 15777 h 0, res shmpages ub 0
[  183.919468] Uncharging too much 15569 h 0, res shmpages ub 0
[  183.919480] Uncharging too much 15537 h 0, res shmpages ub 0
[  183.919493] Uncharging too much 16305 h 0, res shmpages ub 0
[  183.919505] Uncharging too much 15025 h 0, res shmpages ub 0
[  183.919517] Uncharging too much 15585 h 0, res shmpages ub 0
[  183.919530] Uncharging too much 15697 h 0, res shmpages ub 0
[  183.919542] Uncharging too much 14993 h 0, res shmpages ub 0
[  183.919555] Uncharging too much 15985 h 0, res shmpages ub 0
[  183.919568] Uncharging too much 16257 h 0, res shmpages ub 0
[  183.919581] Uncharging too much 16113 h 0, res shmpages ub 0
[  183.919593] Uncharging too much 14977 h 0, res shmpages ub 0
[  183.919605] Uncharging too much 15057 h 0, res shmpages ub 0
[  183.919618] Uncharging too much 16161 h 0, res shmpages ub 0
[  183.919630] Uncharging too much 15441 h 0, res shmpages ub 0
[  183.919642] Uncharging too much 15921 h 0, res shmpages ub 0
[  183.919654] Uncharging too much 15937 h 0, res shmpages ub 0
[  183.919666] Uncharging too much 16177 h 0, res shmpages ub 0
[  183.919679] Uncharging too much 16033 h 0, res shmpages ub 0
[  183.919692] Uncharging too much 15473 h 0, res shmpages ub 0
[  183.919710] Uncharging too much 15761 h 0, res shmpages ub 0
[  183.919736] Uncharging too much 16337 h 0, res shmpages ub 0
[  183.919754] Uncharging too much 16289 h 0, res shmpages ub 0
[  183.919771] Uncharging too much 14913 h 0, res shmpages ub 0
[  184.348574] Uncharging too much 300 h 0, res shmpages ub 0
[  184.726306] Uncharging too much 11 h 4, res shmpages ub 0
[  184.763452] Uncharging too much 30 h 9, res shmpages ub 0
[  486.471592] Uncharging too much 478 h 362, res shmpages ub 0
[  490.481915] Uncharging too much 3 h 0, res shmpages ub 0
[  490.481941] Uncharging too much 3 h 0, res shmpages ub 0
[  490.488102] Uncharging too much 4 h 2, res shmpages ub 0
[  496.471620] Uncharging too much 220 h 5, res shmpages ub 0
[  536.471902] Uncharging too much 220 h 43, res shmpages ub 0
[  546.471922] Uncharging too much 2 h 0, res shmpages ub 0
[  546.471948] Uncharging too much 1 h 0, res shmpages ub 0
[  546.471965] Uncharging too much 30 h 0, res shmpages ub 0
[  546.471983] Uncharging too much 1 h 0, res shmpages ub 0
[  546.472027] Uncharging too much 5 h 0, res shmpages ub 0
[  546.472043] Uncharging too much 1 h 0, res shmpages ub 0
[  546.472055] Uncharging too much 1 h 0, res shmpages ub 0
[  546.472070] Uncharging too much 1 h 0, res shmpages ub 0
[  546.472086] Uncharging too much 107 h 0, res shmpages ub 0
[  674.920120] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder 
(output 0)
[  674.940253] [drm] nouveau :01:00.0: Setting dpms mode 0 on vga encoder 
(output 0)
[  674.940261] [drm] nouveau :01:00.0: Output VGA-1 is running

Bug#580925: marked as done (This error is presenting while installing linux-image-2.6.32-5-686:)

[Debian Bug Tracking System]

Your message dated Mon, 10 May 2010 00:18:48 +0200
with message-id <20100509221848.gf13...@baikonur.stro.at>
and subject line Re: Bug#580925: This error is presenting while installing 
linux-image-2.6.32-5-686:
has caused the Debian Bug report #580925,
regarding This error is presenting while installing linux-image-2.6.32-5-686:
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.)


-- 
580925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-12
Severity: normal
Tags: sid


Preconfiguring packages ...
Selecting previously deselected package linux-image-2.6.32-5-686.
(Reading database ... 315673 files and directories currently installed.)
Unpacking linux-image-2.6.32-5-686 (from 
.../linux-image-2.6.32-5-686_2.6.32-12_i386.deb) ...
Setting up linux-image-2.6.32-5-686 (2.6.32-12) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-686
Running update-grub.
Generating grub.cfg ...
/usr/sbin/grub-probe: error: no mapping exists for `md5'.
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.32-5-686 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-2.6.32-5-686

So it looks like there is a problem with md5.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM 
Controller [8086:29c0] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI 
Express Root Port [8086:29c1] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 [8086:2938] (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 [8086:2939] (rev 02) (prog-if 00 [UHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: uhci_hcd

00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 [8086:293c] (rev 02) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci_hcd

00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller [8086:293e] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:829f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express 
Port 1 [8086:2940] (rev 02) (prog-if 00 [Normal decode])

Processed: bug 580927 is forwarded to http://bugzilla.openvz.org/show_bug.cgi?id=1299

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 580927 http://bugzilla.openvz.org/show_bug.cgi?id=1299
Bug #580927 [linux-2.6] linux-image-2.6.32-5-openvz-686: Uncharging too much 
... res shmpages ub
Set Bug forwarded-to-address to 
'http://bugzilla.openvz.org/show_bug.cgi?id=1299'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
580927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580927
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.127344413717077.transcr...@bugs.debian.org