Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup

2010-05-21 Thread Andre Pawlowski
Package: initramfs-tools
Version: 0.94.4
Severity: important


This bugreport was written with the initrd.img-2.6.32-trunk-amd64.bak before 
updating yesterday
to initramfs-tools 0.94.4. I have an encrytped lvm which contains every 
partition except /boot.
It was created by the Debian squeeze setup when I installed the system. Today I 
tried to boot
the system with the new initramfs-tools and after I entered the password I get 
this message:

kernel-provided name 'dm-0' and NAME='/mapper/sda2_crypt' disagree, please use 
SYMLINK+=
or change the kernel to provide the proper name

This bug appears after I upgraded

libudev0
udev
insserv
groff-base
initramfs-tools
libglib2.0-0
libglib2.0-dev
libglib2.0-data
libgps19
libgudev-1.0-0
libjack0
libschroedinger-1.0-0
libwebkit-1.0-common
libwebkit-1.0-2
xserver-xorg-video-intel
xterm

because I only changed the initrd.img and after that I could boot the system 
again 
I think it is a bug in initramfs-tools.


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/handtuch--vg-root ro 
quiet

-- /proc/filesystems
ext4
fuseblk

-- lsmod
Module  Size  Used by
nf_conntrack_ipv4   9817  2 
nf_defrag_ipv4  1139  1 nf_conntrack_ipv4
xt_state1303  2 
nf_conntrack   46359  2 nf_conntrack_ipv4,xt_state
xt_tcpudp   2319  2 
iptable_filter  2258  1 
ip_tables  13899  1 iptable_filter
x_tables   12813  3 xt_state,xt_tcpudp,ip_tables
vboxnetadp  4225  0 
vboxnetflt  9978  0 
vboxdrv  1710854  2 vboxnetadp,vboxnetflt
fuse   50078  1 
loop   11767  0 
firewire_sbp2  11450  0 
snd_hda_codec_conexant21789  1 
joydev  8411  0 
snd_hda_intel  18147  0 
arc41274  2 
ecb 1841  2 
snd_hda_codec  54212  2 snd_hda_codec_conexant,snd_hda_intel
snd_hwdep   5364  1 snd_hda_codec
snd_pcm_oss32399  0 
snd_mixer_oss  12606  1 snd_pcm_oss
iwlagn 71452  0 
iwlcore77494  1 iwlagn
snd_pcm60615  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi4208  0 
snd_rawmidi15291  1 snd_seq_midi
snd_seq_midi_event  4628  1 snd_seq_midi
snd_seq42769  2 snd_seq_midi,snd_seq_midi_event
mac80211  135407  2 iwlagn,iwlcore
snd_timer  15502  2 snd_pcm,snd_seq
pcmcia 19426  0 
uvcvideo   51663  0 
cfg80211  101253  3 iwlagn,iwlcore,mac80211
videodev   29977  1 uvcvideo
thinkpad_acpi  50043  0 
yenta_socket   19051  1 
v4l1_compat11442  2 uvcvideo,videodev
rsrc_nonstatic  7294  1 yenta_socket
snd_seq_device  4477  3 snd_seq_midi,snd_rawmidi,snd_seq
v4l2_compat_ioctl32 8538  1 videodev
i2c_i8017766  0 
rfkill 12996  2 cfg80211,thinkpad_acpi
pcspkr  1699  0 
pcmcia_core24054  3 pcmcia,yenta_socket,rsrc_nonstatic
snd44718  11 
snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
battery 4998  0 
ac  2192  0 
wmi 4307  0 
psmouse49521  0 
soundcore   4598  1 snd
nvram   5061  1 thinkpad_acpi
snd_page_alloc  6217  2 snd_hda_intel,snd_pcm
evdev   7336  24 
serio_raw   3752  0 
processor  29479  2 
ext4  285067  4 
mbcache 4970  1 ext4
jbd2   66855  1 ext4
crc16   1319  1 ext4
sha256_generic  8692  2 
cryptd  5366  0 
aes_x86_64  7340  2 
aes_generic25714  1 aes_x86_64
cbc 2539  1 
dm_crypt   10507  1 
dm_mod 53658  15 dm_crypt
fan 3346  0 
sg 18728  0 
sr_mod 12602  0 
sd_mod 29673  3 
crc_t10dif  1276  1 sd_mod
cdrom  29399  1 sr_mod
uhci_hcd   18457  0 
firewire_ohci  19452  0 
ahci   31494  2 
sdhci_pci   5565  0 
sdhci  13966  1 sdhci_pci
i915  247359  2 
drm_kms_helper 18883  1 i915
libata131655  1 ahci
ricoh_mmc   3069  0 
mmc_core   45456  1 sdhci
led_class   2401  3 iwlcore,thinkpad_acpi,sdhci
firewire_core  36560  2 firewire_sbp2,firewire_ohci
crc_itu_t   1307  1 firewire_core
ehci_hcd   30578  0 
thermal11674  0 
drm   137190  3 i915,drm_kms_helper
i2c_algo_bit4225  1 i915
i2c_core 

Bug#581353: System badly crashes completely

2010-05-21 Thread Jan Hauke Rahm
Hi Max,

On Wed, May 12, 2010 at 09:27:02PM +0200, maximilian attems wrote:
 On Wed, May 12, 2010 at 08:18:51PM +0200, Jan Hauke Rahm wrote:
  There is nothing related. I reported a bug on 2.6.32-9 because it
  happened there. I can't run a newer kernel, i.e. 2.6.32-12,
 
 2.6.32-9 is old and thus unsupported, you are out of luck there.
 much happened since.
 
 with snapshot you could start bisecting which package does boot for you?
 thanks

just found the problem: I had that stupid 'vga=791' as boot parameter
which conflicted with KMS. The current kernel in sid runs fine without
it. Sorry for that huge waste of time.

What this bug was actually about never resolved but since it's about an
old kernel we probably don't have to care much.

Hauke

-- 
 .''`.   Jan Hauke Rahm j...@debian.org   www.jhr-online.de
: :'  :  Debian Developer www.debian.org
`. `'`   Member of the Linux Foundationwww.linux.com
  `- Fellow of the Free Software Foundation Europe  www.fsfe.org


signature.asc
Description: Digital signature


Bug#582487: linux-image-2.6.32-5-686: bad page state

2010-05-21 Thread Thiemo Nagel
Package: linux-2.6
Version: 2.6.32-12
Severity: normal

Cheers!

Thiemo

[ 3587.353975] BUG: Bad page state in process 10_linux  pfn:352fe
[ 3587.353996] page:c1b67fc0 flags:4000 count:0 mapcount:-9835008 
mapping:(null) index:bfffe
[ 3587.354013] Pid: 9401, comm: 10_linux Not tainted 2.6.32-5-686 #1
[ 3587.354022] Call Trace:
[ 3587.354046]  [c108ae4b] ? bad_page+0xd7/0xeb
[ 3587.354063]  [c108c057] ? get_page_from_freelist+0x2e7/0x3c7
[ 3587.354078]  [c108c3f8] ? __alloc_pages_nodemask+0xf3/0x4e0
[ 3587.354093]  [c108c0aa] ? get_page_from_freelist+0x33a/0x3c7
[ 3587.354108]  [c108793c] ? find_get_page+0x1f/0x81
[ 3587.354120]  [c1087b40] ? lock_page+0x8/0x1d
[ 3587.354135]  [c109a6f2] ? do_wp_page+0x3eb/0x727
[ 3587.354150]  [c109c0c6] ? handle_mm_fault+0x812/0x890
[ 3587.354168]  [c101c35f] ? do_page_fault+0x0/0x287
[ 3587.354186]  [c126969b] ? error_code+0x73/0x78
[ 3587.354200]  [c101c5d0] ? do_page_fault+0x271/0x287
[ 3587.354214]  [c101c35f] ? do_page_fault+0x0/0x287
[ 3587.354228]  [c126969b] ? error_code+0x73/0x78
[ 3587.354237] Disabling lock debugging due to kernel taint

-- Package-specific info:
** Version:
Linux version 2.6.32-5-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 04:16:37 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/sda7_crypt ro vga=6 quiet

** Tainted: B (32)
 * System has hit bad_page.

** Kernel log:
[ 1989.682270] option 1-6:1.1: no reset_resume for driver option?
[ 1989.682283] option 1-6:1.2: no reset_resume for driver option?
[ 1989.682784] option1 ttyUSB1: GSM modem (1-port) converter now disconnected 
from ttyUSB1
[ 1989.682822] option 1-6:1.0: device disconnected
[ 1989.682981] option1 ttyUSB2: GSM modem (1-port) converter now disconnected 
from ttyUSB2
[ 1989.683031] option 1-6:1.1: device disconnected
[ 1989.683182] option1 ttyUSB3: GSM modem (1-port) converter now disconnected 
from ttyUSB3
[ 1989.683227] option 1-6:1.2: device disconnected
[ 1989.792188] usb 1-8: reset high speed USB device using ehci_hcd and address 4
[ 1989.978930] pci :00:02.0: setting latency timer to 64
[ 1990.000466] ath5k :01:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19
[ 1990.000752] option 1-6:1.0: GSM modem (1-port) converter detected
[ 1990.000971] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB0
[ 1990.001106] option 1-6:1.1: GSM modem (1-port) converter detected
[ 1990.001280] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB2
[ 1990.001393] option 1-6:1.2: GSM modem (1-port) converter detected
[ 1990.001557] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB3
[ 1990.001989] PM: Finishing wakeup.
[ 1990.001995] Restarting tasks ... done.
[ 1999.247523] ATL1E :03:00.0: irq 27 for MSI/MSI-X
[ 1999.269311] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1999.363968] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1999.492360] CPU0 attaching NULL sched-domain.
[ 1999.492374] CPU1 attaching NULL sched-domain.
[ 1999.520375] CPU0 attaching sched-domain:
[ 1999.520396]  domain 0: span 0-1 level SIBLING
[ 1999.520413]   groups: 0 (cpu_power = 589) 1 (cpu_power = 589)
[ 1999.520447]   domain 1: span 0-1 level MC
[ 1999.520461]groups: 0-1 (cpu_power = 1178)
[ 1999.520488] CPU1 attaching sched-domain:
[ 1999.520501]  domain 0: span 0-1 level SIBLING
[ 1999.520515]   groups: 1 (cpu_power = 589) 0 (cpu_power = 589)
[ 1999.520545]   domain 1: span 0-1 level MC
[ 1999.520559]groups: 0-1 (cpu_power = 1178)
[ 2010.952695] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 1)
[ 2010.954646] wlan0: direct probe responded
[ 2010.954662] wlan0: authenticate with AP 00:1c:f0:84:61:52 (try 1)
[ 2010.956254] wlan0: authenticated
[ 2010.956327] wlan0: associate with AP 00:1c:f0:84:61:52 (try 1)
[ 2010.958468] wlan0: RX AssocResp from 00:1c:f0:84:61:52 (capab=0x431 status=0 
aid=2)
[ 2010.958482] wlan0: associated
[ 2010.960787] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 2021.776031] wlan0: no IPv6 routers present
[ 2909.060189] No probe response from AP 00:1c:f0:84:61:52 after 500ms, 
disconnecting.
[ 2910.710795] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 1)
[ 2910.909149] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 2)
[ 2911.109135] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 3)
[ 2911.309151] wlan0: direct probe to AP 00:1c:f0:84:61:52 timed out
[ 2922.234184] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 1)
[ 2922.432155] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 2)
[ 2922.632144] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 3)
[ 2922.832154] wlan0: direct probe to AP 00:1c:f0:84:61:52 timed out
[ 2925.679583] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 1)
[ 2925.876162] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 2)
[ 2926.076178] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 3)
[ 2926.276144] wlan0: direct probe to AP 00:1c:f0:84:61:52 timed out
[ 2937.180776] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 

Bug#582487: addendum

2010-05-21 Thread Thiemo Nagel
Maybe to avoid confusion I should add that during the time of reporting 
the bug, I had 2.6.32-13 already installed, but not rebooted yet.  The 
bug applies to 2.6.32-12.


Cheers!

Thiemo



--
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/4bf6437c.5010...@googlemail.com



Bug#580149: linux-image-2.6.32-trunk-amd64: usb - sata Sense not available

2010-05-21 Thread formind22

More information.

The usb mouse works fine on PCI USB 2.0 Host Controller Card
(4-Ext, 1-Int. Ports)
but the usb storage (DataTraveler), and the USB-SATA
converter does not work.

Ggreetings



-- 
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/mtelekom-vm.20100421115648.52...@maxbe08a.t-online.private



Processed: Re: Bug#580149: linux-image-2.6.32-trunk-amd64: usb - sata Sense not available

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 580149 moreinfo
Bug #580149 [linux-2.6] linux-image-2.6.32-trunk-amd64: usb - sata  Sense not 
available
Added tag(s) moreinfo.
 stop
Stopping processing here.

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



Bug#580149: linux-image-2.6.32-trunk-amd64: usb - sata Sense not available

2010-05-21 Thread maximilian attems
tags 580149 moreinfo
stop

On Fri, May 21, 2010 at 11:56:48AM +0200, formin...@t-online.hu wrote:
 
 More information.
 
 The usb mouse works fine on PCI USB 2.0 Host Controller Card
 (4-Ext, 1-Int. Ports)
 but the usb storage (DataTraveler), and the USB-SATA
 converter does not work.

could you please try to reproduce on a recent 2.6.32 aka
2.6.32-13 from unstable, thanks.

also is it fixed in 2.6.34 in experimental?



-- 
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/20100521141533.gb13...@baikonur.stro.at



Bug#582281: Promised utility now available

2010-05-21 Thread Stephen Powell
As promised in my original post, I have written a little
utility program to zap the disk labels of minidisks corrupted
by this bug.  Running it against all affected disks will allow
existing data to be accessed safely by both types of Linux kernels:
those that have the bug and those that have the fix applied.
The utility can be found here:

   http://www.wowway.com/~zlinuxman/kernel/ZAPLABEL.ASM

This is s390 assembler language source code for the utility.
The comments explain how to assemble and use it.  It is designed
to be assembled and used under CMS.

Now, how do you want to work this?  Do you (the Debian Kernel Team)
want to function as an intermediary between me and upstream?
Or would you prefer that I report the problem to upstream myself?

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-



-- 
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/274713590.319959.1274455956217.javamail.r...@md01.wow.synacor.com



Bug#582107: marked as done (NFS mounts default to version 4, don't fall back automatically)

2010-05-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 May 2010 22:14:02 +0200
with message-id 7ieih5qagl@lanthane.pps.jussieu.fr
and subject line Re: Bug#582107: NFS mounts default to version 4, don't fall 
back automatically
has caused the Debian Bug report #582107,
regarding NFS mounts default to version 4, don't fall back automatically
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.)


-- 
582107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: nfs-common
Version: 1:1.2.2-1

Recent versions of mount.nfs default to NFS version 4.  The result is
that mounting ordinary version 3 filesystems fails with EPERM.

The bug is not the new default, which is open to debate; the bug is that
Sun RPC is supposed to allow negotiation of the protocol version, and
that mount appears unable to fall back to version 3 if version 4 is not
supported by the server.

A workaround is to add vers=3 to the options column in /etc/fstab.

--jch


pgpBWMdIGkqLH.pgp
Description: PGP signature
---End Message---
---BeginMessage---
 The result is that mounting ordinary version 3 filesystems fails with EPERM.

 I can't reproduce this.

Neither can I -- it now appears to work without the vers=3.  Sorry for the 
noise.

Juliusz

---End Message---


Bug#582107: NFS mounts default to version 4, don't fall back automatically

2010-05-21 Thread Juliusz Chroboczek
 The result is that mounting ordinary version 3 filesystems fails with EPERM.

 I can't reproduce this.

Neither can I -- it now appears to work without the vers=3.  Sorry for the 
noise.

Juliusz



-- 
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/7ieih5qagl@lanthane.pps.jussieu.fr



Bug#582281: Promised utility now available

2010-05-21 Thread Jonathan Nieder
reassign 582281 linux-2.6
tags 582281 + upstream
quit

Stephen Powell wrote:

 Now, how do you want to work this?  Do you (the Debian Kernel Team)
 want to function as an intermediary between me and upstream?
 Or would you prefer that I report the problem to upstream myself?

I am not the kernel team, but for issues in upstream code, it is
_always_ a good idea to go to upstream directly[1].

 $ grep '^[0-9]*)' Documentation/SubmittingPatches
 1) diff -up
 2) Describe your changes.
 3) Separate your changes.
 4) Style check your changes.
 5) Select e-mail destination.
 6) Select your CC (e-mail carbon copy) list.
 7) No MIME, no links, no compression, no attachments.  Just plain text.
 8) E-mail size.
 9) Name your kernel version.
 10) Don't get discouraged.  Re-submit.
 11) Include PATCH in the subject
 12) Sign your work
 13) When to use Acked-by: and Cc:
 14) Using Reported-by:, Tested-by: and Reviewed-by:
 15) The canonical patch format
 16) Sending git pull requests  (from Linus emails)
 1) Read Documentation/CodingStyle
 2) #ifdefs are ugly
 3) 'static inline' is better than a macro
 4) Don't over-design.
 $ scripts/get_maintainer.pl -f fs/partitions/ibm.c
 Martin K. Petersen martin.peter...@oracle.com
 Jens Axboe jens.ax...@oracle.com
 linux-ker...@vger.kernel.org

Summary: the best thing is to send your patch as a _unified_ diff
(i.e. generated with diff -u), and include it inline in a message
to the addresses listed above, with the following format:

 some timeless words about the patch

 Signed-off-by line (see Documentation/SubmittingPatches for what
 this means and why)
 ---
 some timely words about the patch 

 the patch (diff -up output)

It seems I have only been able to make more work for you lately.
Sorry.  I would also be willing to pass on the patch myself, but at
minimum this requires your signed-off-by line, and it might be good to
get to know the process anyway.

You can see lots of examples at http://news.gmane.org/gmane.linux.kernel

Hope that helps,
Jonathan

[1] The corresponding Debian bug report is still useful, as a way to
track the status of the bug in Debian (e.g., what versions have the
patch applied).



-- 
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/20100521204838.ga1...@progeny.tock



Processed: Re: Promised utility now available

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 582281 linux-2.6
Bug #582281 [linux-source-2.6.32] Partition starting sector and partition size 
calculated incorrectly for reserved CMS minidisk on FBA DASD with blocksize  
512 using DIAG driver (s390 architecture only)
Bug reassigned from package 'linux-source-2.6.32' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.32-12.
 tags 582281 + upstream
Bug #582281 [linux-2.6] Partition starting sector and partition size calculated 
incorrectly for reserved CMS minidisk on FBA DASD with blocksize  512 using 
DIAG driver (s390 architecture only)
Added tag(s) upstream.
 quit
Stopping processing here.

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



Processed: Re: Processed: Re: Promised utility now available

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Bug #582281 [linux-source-2.6.32] Partition starting sector and partition 
 size calculated incorrectly for reserved CMS minidisk on FBA DASD with 
 blocksize  512 using DIAG driver (s390 architecture only)
 # Bug reassigned from package 'linux-source-2.6.32' to 'linux-2.6'.
 # Bug No longer marked as found in versions linux-2.6/2.6.32-12.
 found 582281 linux-2.6/2.6.32-12
Bug #582281 [linux-2.6] Partition starting sector and partition size calculated 
incorrectly for reserved CMS minidisk on FBA DASD with blocksize  512 using 
DIAG driver (s390 architecture only)
Bug Marked as found in versions linux-2.6/2.6.32-12.
 quit
Stopping processing here.

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



Bug#582487: linux-image-2.6.32-5-686: bad page state

2010-05-21 Thread Ben Hutchings
On Fri, 2010-05-21 at 10:15 +0200, Thiemo Nagel wrote:
 Package: linux-2.6
 Version: 2.6.32-12
 Severity: normal
 
 Cheers!
 
 Thiemo
 
 [ 3587.353975] BUG: Bad page state in process 10_linux  pfn:352fe
 [ 3587.353996] page:c1b67fc0 flags:4000 count:0 mapcount:-9835008 
 mapping:(null) index:bfffe
 [ 3587.354013] Pid: 9401, comm: 10_linux Not tainted 2.6.32-5-686 #1
 [ 3587.354022] Call Trace:
 [ 3587.354046]  [c108ae4b] ? bad_page+0xd7/0xeb
 [ 3587.354063]  [c108c057] ? get_page_from_freelist+0x2e7/0x3c7
 [ 3587.354078]  [c108c3f8] ? __alloc_pages_nodemask+0xf3/0x4e0
 [ 3587.354093]  [c108c0aa] ? get_page_from_freelist+0x33a/0x3c7
 [ 3587.354108]  [c108793c] ? find_get_page+0x1f/0x81
 [ 3587.354120]  [c1087b40] ? lock_page+0x8/0x1d
 [ 3587.354135]  [c109a6f2] ? do_wp_page+0x3eb/0x727
 [ 3587.354150]  [c109c0c6] ? handle_mm_fault+0x812/0x890
 [ 3587.354168]  [c101c35f] ? do_page_fault+0x0/0x287
 [ 3587.354186]  [c126969b] ? error_code+0x73/0x78
 [ 3587.354200]  [c101c5d0] ? do_page_fault+0x271/0x287
 [ 3587.354214]  [c101c35f] ? do_page_fault+0x0/0x287
 [ 3587.354228]  [c126969b] ? error_code+0x73/0x78
 [ 3587.354237] Disabling lock debugging due to kernel taint
[...]

Has this error occurred before, or just once?

You could look for earlier occurrences by running:
zgrep 'Bad page state' /var/log/messages*

Which filesystem are you using for /boot?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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


Processed: tagging 582487

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 582487 moreinfo
Bug #582487 [linux-2.6] linux-image-2.6.32-5-686: bad page state
Added tag(s) moreinfo.
 thanks
Stopping processing here.

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



Bug#582275: linux-image-2.6.32-bpo.4-686: ext3 filesystem corruption with md RAID1 on Seagate disks

2010-05-21 Thread Ben Hutchings
On Wed, 2010-05-19 at 18:50 +0200, Reiner Buehl wrote:
 Package: linux-2.6
 Version: 2.6.32-11~bpo50+1
 Severity: critical
 Justification: causes serious data loss
 
 I keep getting ext3 filesystem corruptions on one of my md RAID1
 arrays. Shortly after booting, I get messages like the following one:
[...]

I see that you've also send a bug report to some kernel mailing lists,
and the problem has now disappeared.  Do you still want to keep this bug
report open?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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


Processed: bug 582275 is forwarded to linux-fsde...@vger.kernel.org, tagging 582275

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 forwarded 582275 linux-fsde...@vger.kernel.org
Bug #582275 [linux-2.6] linux-image-2.6.32-bpo.4-686: ext3 filesystem 
corruption with md RAID1 on Seagate disks
Set Bug forwarded-to-address to 'linux-fsde...@vger.kernel.org'.
 tags 582275 moreinfo
Bug #582275 [linux-2.6] linux-image-2.6.32-bpo.4-686: ext3 filesystem 
corruption with md RAID1 on Seagate disks
Added tag(s) moreinfo.
 thanks
Stopping processing here.

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



Bug#578262: Intel 5300 wireless does not work on Acer, TravelMate6293.

2010-05-21 Thread Ben Hutchings
On Wed, 2010-05-19 at 14:45 +0200, Zdeněk Matěj wrote:
 Thank you for your replay.
 
 I applied the supplied patches:
 
 0001-mac80211-explicitly-disable-enable-QoS.patch
 0002-iwlwifi-manage-QoS-by-mac-stack.patch
[...]
 If I understand the patches correctly, the 0002...patch removes a void 
 iwl_reset_qos(struct iwl_priv *priv) function and unused qos_cap bits. 
 But the function is still used in int iwl_init_drv(struct iwl_priv 
 *priv) function in the iwl-core.c. I removed a part of code:
 ---
 iwl_reset_qos(priv);
 
 priv-qos_data.qos_active = 0;
 priv-qos_data.qos_cap.val = 0;
 ---
 as it is done in int iwl3945_init_drv(struct iwl_priv *priv) at the 
 end of the 0002patch.

Well spotted.  Thanks.

 With this adjustment (attached 
 0002-iwlwifi-manage-QoS-by-mac-stack-adjust.patch file) I can compile 
 the source and it works fine with APs with which it didn't work before.

Good.  I'll apply all these fixes.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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


Processed: tagging 578262

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 578262 + pending
Bug #578262 [linux-2.6] iwlwifi compatibility problem with non-QoS APs
Bug #578263 [linux-2.6] iwlwifi compatibility problem with non-QoS APs
Added tag(s) pending.
Added tag(s) pending.

End of message, stopping processing here.

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



Processed: bug 571251 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=14716

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 forwarded 571251 https://bugzilla.kernel.org/show_bug.cgi?id=14716
Bug #571251 [linux-2.6] base: hp pavillon won't start (30% success)
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=14716'.
 thanks
Stopping processing here.

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



Processed: tagging 571251

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 571251 - moreinfo
Bug #571251 [linux-2.6] base: hp pavillon won't start (30% success)
Removed tag(s) moreinfo.
 thanks
Stopping processing here.

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



Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254

2010-05-21 Thread Steven Shiau

Same problem here. However, mine is on the client side.
On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1.
When I mount my NFS server 192.168.120.254, it works. However, if I want 
to use some tool which need to lock file to save the file on the NFS 
server, e.g.

vgcfgbackup -f $NFS_MNT_POINT/vg.cfg
I get the message lockd: cannot monitor 192.168.120.254, and the 
message shown on the /var/log/daemon.log:
May 21 08:52:44 debian rpc.statd[1298]: STAT_FAIL to debian for SM_MON 
of 192.168.120.254
May 21 08:52:44 debian rpc.statd[1298]: No canonical hostname found for 
192.168.120.254


I have to put a lookup setting in /etc/hosts, something like
192.168.120.254 nfs-server
then the command vgcfgbackup can successfully save the file on the NFS dir.
This bug is really annoying especially in the private IP addresses 
environment. It's really a pain to put all the possible machines on the 
/etc/hosts.
Please consider this as a serious issue, because it will cause a lot of 
NFS-based computing clusters fail.

My 2 cents.

Steven.

--
Steven Shiausteven _at_ nchc org tw  steven _at_ stevenshiau org
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A




--
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/4bf71c27.7070...@nchc.org.tw



Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254

2010-05-21 Thread Ben Hutchings
On Sat, 2010-05-22 at 07:49 +0800, Steven Shiau wrote: 
 Same problem here. However, mine is on the client side.
 On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1.
 When I mount my NFS server 192.168.120.254, it works. However, if I want 
 to use some tool which need to lock file to save the file on the NFS 
 server, e.g.
 vgcfgbackup -f $NFS_MNT_POINT/vg.cfg
 I get the message lockd: cannot monitor 192.168.120.254, and the 
 message shown on the /var/log/daemon.log:
 May 21 08:52:44 debian rpc.statd[1298]: STAT_FAIL to debian for SM_MON 
 of 192.168.120.254
 May 21 08:52:44 debian rpc.statd[1298]: No canonical hostname found for 
 192.168.120.254
[...]

nfs-utils 1.2.2 includes the change:

commit 8ce130c4c828b9d13d429f22160f992b9c1d45cd
Author: Chuck Lever chuck.le...@oracle.com
Date:   Thu Jan 14 12:24:15 2010 -0500

statd: Support IPv6 in sm_mon_1_svc()

This appears to have removed support for IPv4 literals.  Was this
intentional?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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


Processed: tagging 579397, bug 579397 is forwarded to linux-...@vger.kernel.org

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 579397 upstream
Bug #579397 [nfs-kernel-server] nfs-kernel-server: statd wont't work without 
reverse lookups, mountd won't allow ip-based exports with reverse lookups
Added tag(s) upstream.
 forwarded 579397 linux-...@vger.kernel.org
Bug #579397 [nfs-kernel-server] nfs-kernel-server: statd wont't work without 
reverse lookups, mountd won't allow ip-based exports with reverse lookups
Set Bug forwarded-to-address to 'linux-...@vger.kernel.org'.
 thanks
Stopping processing here.

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



Processed: reassign 508289 to wicd

2010-05-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 508289 wicd
Bug #508289 [nfs-common] [nfs-common] mount nfs at boot fails when insserv with 
shell or startpar concurrency is enabled
Bug reassigned from package 'nfs-common' to 'wicd'.
Bug No longer marked as found in versions nfs-utils/1:1.1.4-1.
 thanks
Stopping processing here.

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



Bug#542275: hwclock should not try to calculate the drift if rtc time is invalid [was: Re: Bug#542275: kernel error message for #542275 + patch]

2010-05-21 Thread Mark Purcell
On Wednesday 03 February 2010 15:43:29 Benjamin Cama wrote:
 So, the correct command in this context would be (see #478663) :
 # hwclock --systohc --noadjfile --utc
 
 But it took me some hard time to find it ...

Benjamin  Ben,

Thanks for this.

I was having the same issue with a ibook G4, that I couldn't get to boot and 
couldn't set the time past 1970, due to the flat battery.

--noadjfile fixed things up for me, so I could reboot with a sensible time.

Mark


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


Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup

2010-05-21 Thread maximilian attems
On Fri, 21 May 2010, Andre Pawlowski wrote:

 Package: initramfs-tools
 Version: 0.94.4
 Severity: important
 
 
 This bugreport was written with the initrd.img-2.6.32-trunk-amd64.bak before 
 updating yesterday
 to initramfs-tools 0.94.4. I have an encrytped lvm which contains every 
 partition except /boot.
 It was created by the Debian squeeze setup when I installed the system. Today 
 I tried to boot
 the system with the new initramfs-tools and after I entered the password I 
 get this message:
 
 kernel-provided name 'dm-0' and NAME='/mapper/sda2_crypt' disagree, please 
 use SYMLINK+=
 or change the kernel to provide the proper name
 
 This bug appears after I upgraded
 
 libudev0
 udev
 insserv
 groff-base
 initramfs-tools
 libglib2.0-0
 libglib2.0-dev
 libglib2.0-data
 libgps19
 libgudev-1.0-0
 libjack0
 libschroedinger-1.0-0
 libwebkit-1.0-common
 libwebkit-1.0-2
 xserver-xorg-video-intel
 xterm
 
 because I only changed the initrd.img and after that I could boot the system 
 again 
 I think it is a bug in initramfs-tools.

no we dont set udev symlinks, so it is either a crytsetup
or an udev bug.
 
 
 -- Package-specific info:
 -- /proc/cmdline
 BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/handtuch--vg-root ro 
 quiet
 
 -- /proc/filesystems
   ext4
   fuseblk
 
 -- lsmod
 Module  Size  Used by
 nf_conntrack_ipv4   9817  2 
 nf_defrag_ipv4  1139  1 nf_conntrack_ipv4
 xt_state1303  2 
 nf_conntrack   46359  2 nf_conntrack_ipv4,xt_state
 xt_tcpudp   2319  2 
 iptable_filter  2258  1 
 ip_tables  13899  1 iptable_filter
 x_tables   12813  3 xt_state,xt_tcpudp,ip_tables
 vboxnetadp  4225  0 
 vboxnetflt  9978  0 
 vboxdrv  1710854  2 vboxnetadp,vboxnetflt
 fuse   50078  1 
 loop   11767  0 
 firewire_sbp2  11450  0 
 snd_hda_codec_conexant21789  1 
 joydev  8411  0 
 snd_hda_intel  18147  0 
 arc41274  2 
 ecb 1841  2 
 snd_hda_codec  54212  2 snd_hda_codec_conexant,snd_hda_intel
 snd_hwdep   5364  1 snd_hda_codec
 snd_pcm_oss32399  0 
 snd_mixer_oss  12606  1 snd_pcm_oss
 iwlagn 71452  0 
 iwlcore77494  1 iwlagn
 snd_pcm60615  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
 snd_seq_midi4208  0 
 snd_rawmidi15291  1 snd_seq_midi
 snd_seq_midi_event  4628  1 snd_seq_midi
 snd_seq42769  2 snd_seq_midi,snd_seq_midi_event
 mac80211  135407  2 iwlagn,iwlcore
 snd_timer  15502  2 snd_pcm,snd_seq
 pcmcia 19426  0 
 uvcvideo   51663  0 
 cfg80211  101253  3 iwlagn,iwlcore,mac80211
 videodev   29977  1 uvcvideo
 thinkpad_acpi  50043  0 
 yenta_socket   19051  1 
 v4l1_compat11442  2 uvcvideo,videodev
 rsrc_nonstatic  7294  1 yenta_socket
 snd_seq_device  4477  3 snd_seq_midi,snd_rawmidi,snd_seq
 v4l2_compat_ioctl32 8538  1 videodev
 i2c_i8017766  0 
 rfkill 12996  2 cfg80211,thinkpad_acpi
 pcspkr  1699  0 
 pcmcia_core24054  3 pcmcia,yenta_socket,rsrc_nonstatic
 snd44718  11 
 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
 battery 4998  0 
 ac  2192  0 
 wmi 4307  0 
 psmouse49521  0 
 soundcore   4598  1 snd
 nvram   5061  1 thinkpad_acpi
 snd_page_alloc  6217  2 snd_hda_intel,snd_pcm
 evdev   7336  24 
 serio_raw   3752  0 
 processor  29479  2 
 ext4  285067  4 
 mbcache 4970  1 ext4
 jbd2   66855  1 ext4
 crc16   1319  1 ext4
 sha256_generic  8692  2 
 cryptd  5366  0 
 aes_x86_64  7340  2 
 aes_generic25714  1 aes_x86_64
 cbc 2539  1 
 dm_crypt   10507  1 
 dm_mod 53658  15 dm_crypt
 fan 3346  0 
 sg 18728  0 
 sr_mod 12602  0 
 sd_mod 29673  3 
 crc_t10dif  1276  1 sd_mod
 cdrom  29399  1 sr_mod
 uhci_hcd   18457  0 
 firewire_ohci  19452  0 
 ahci   31494  2 
 sdhci_pci   5565  0 
 sdhci  13966  1 sdhci_pci
 i915  247359  2 
 drm_kms_helper 18883  1 i915
 libata131655  1 ahci
 ricoh_mmc   3069  0 
 mmc_core   45456  1 sdhci
 led_class   2401  3 iwlcore,thinkpad_acpi,sdhci
 firewire_core