Re: MIPS boot drivers

[Aurelien Jarno]

On Tue, Jun 08, 2010 at 03:51:33AM +0100, Ben Hutchings wrote:
> Martin, Aurelien,
> 
> When switching from IDE to libata drivers I updated all per-architecture
> configuration files but I failed to cover per-flavour configuration
> files.  These configuration files currently enable some IDE drivers and
> the associated flavours may be broken due to the partial conversion:
> 
> debian/config/armel/config.iop32x
> debian/config/m68k/config.amiga
> debian/config/m68k/config.atari
> debian/config/m68k/config.mac
> debian/config/m68k/config.q40
> debian/config/mips/config.4kc-malta (known broken; see #584784)
> debian/config/mips/config.5kc-malta
> debian/config/mips/config.r4k-ip22
> debian/config/mips/config.r5k-ip32
> debian/config/mips/config.sb1a-bcm91480b
> debian/config/mips/config.sb1-bcm91250a
> debian/config/mipsel/config.r5k-cobalt
> debian/config/sh4/config.sh7751r
> debian/config/sh4/config.sh7785lcr
> 
> Ignoring m68k and sh4 as not release architectures, this leaves mostly
> MIPS platforms.  Since I know approximately nothing about these and I'm
> not sure exactly which boot methods are supposed to be supported, I'll
> have to ask you to review the configurations.  I've attached a patch
> which was my best guess at the necessary changes.
> 

sh4 has always used libata.

MIPS SB1 BCM812501 has been switched to libata some times ago.

For the remaining MIPS flavors, I'll look at that later today, as it 
might include some tests.

Aurelien

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


-- 
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/20100608053143.gl30...@hall.aurel32.net

MIPS boot drivers

[Ben Hutchings]

Martin, Aurelien,

When switching from IDE to libata drivers I updated all per-architecture
configuration files but I failed to cover per-flavour configuration
files.  These configuration files currently enable some IDE drivers and
the associated flavours may be broken due to the partial conversion:

debian/config/armel/config.iop32x
debian/config/m68k/config.amiga
debian/config/m68k/config.atari
debian/config/m68k/config.mac
debian/config/m68k/config.q40
debian/config/mips/config.4kc-malta (known broken; see #584784)
debian/config/mips/config.5kc-malta
debian/config/mips/config.r4k-ip22
debian/config/mips/config.r5k-ip32
debian/config/mips/config.sb1a-bcm91480b
debian/config/mips/config.sb1-bcm91250a
debian/config/mipsel/config.r5k-cobalt
debian/config/sh4/config.sh7751r
debian/config/sh4/config.sh7785lcr

Ignoring m68k and sh4 as not release architectures, this leaves mostly
MIPS platforms.  Since I know approximately nothing about these and I'm
not sure exactly which boot methods are supposed to be supported, I'll
have to ask you to review the configurations.  I've attached a patch
which was my best guess at the necessary changes.

Note that pata_generic replaces ide-pci-generic whereas pata_platform
appears to be the correct replacement for ide-generic.  But you probably
knew that.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Index: debian/config/mipsel/config.r5k-cobalt
===
--- debian/config/mipsel/config.r5k-cobalt	(revision 15825)
+++ debian/config/mipsel/config.r5k-cobalt	(working copy)
@@ -89,6 +89,13 @@
 # CONFIG_TOSHIBA_RBTX4938 is not set
 
 ##
+## file: drivers/ata/Kconfig
+##
+CONFIG_ATA=y
+CONFIG_PATA_PLATFORM=y
+CONFIG_PATA_VIA=y
+
+##
 ## file: drivers/base/Kconfig
 ##
 # CONFIG_STANDALONE is not set
@@ -163,36 +170,7 @@
 ##
 ## file: drivers/ide/Kconfig
 ##
-CONFIG_IDE=y
-# CONFIG_BLK_DEV_IDE_SATA is not set
-CONFIG_IDE_GD=y
-CONFIG_IDE_GD_ATA=y
-# CONFIG_BLK_DEV_IDECD is not set
-# CONFIG_BLK_DEV_IDETAPE is not set
-CONFIG_IDE_GENERIC=y
-# CONFIG_BLK_DEV_OFFBOARD is not set
-# CONFIG_BLK_DEV_GENERIC is not set
-# CONFIG_BLK_DEV_OPTI621 is not set
-# CONFIG_BLK_DEV_AEC62XX is not set
-# CONFIG_BLK_DEV_ALI15X3 is not set
-# CONFIG_BLK_DEV_AMD74XX is not set
-# CONFIG_BLK_DEV_CMD64X is not set
-# CONFIG_BLK_DEV_TRIFLEX is not set
-# CONFIG_BLK_DEV_CY82C693 is not set
-# CONFIG_BLK_DEV_CS5520 is not set
-# CONFIG_BLK_DEV_CS5530 is not set
-# CONFIG_BLK_DEV_HPT366 is not set
-# CONFIG_BLK_DEV_SC1200 is not set
-# CONFIG_BLK_DEV_PIIX is not set
-# CONFIG_BLK_DEV_IT821X is not set
-# CONFIG_BLK_DEV_NS87415 is not set
-# CONFIG_BLK_DEV_PDC202XX_OLD is not set
-# CONFIG_BLK_DEV_PDC202XX_NEW is not set
-# CONFIG_BLK_DEV_SVWKS is not set
-# CONFIG_BLK_DEV_SIIMAGE is not set
-# CONFIG_BLK_DEV_SLC90E66 is not set
-# CONFIG_BLK_DEV_TRM290 is not set
-CONFIG_BLK_DEV_VIA82CXXX=y
+# CONFIG_IDE is not set
 
 ##
 ## file: drivers/infiniband/Kconfig
@@ -590,6 +568,8 @@
 ##
 ## file: drivers/scsi/Kconfig
 ##
+CONFIG_SCSI=y
+CONFIG_BLK_DEV_SD=y
 # CONFIG_SCSI_MULTI_LUN is not set
 # CONFIG_SCSI_CONSTANTS is not set
 # CONFIG_SCSI_LOGGING is not set
Index: debian/config/mips/config.4kc-malta
===
--- debian/config/mips/config.4kc-malta	(revision 15825)
+++ debian/config/mips/config.4kc-malta	(working copy)
@@ -134,12 +134,14 @@
 # CONFIG_SATA_VITESSE is not set
 CONFIG_PATA_CMD64X=y
 CONFIG_ATA_GENERIC=y
+CONFIG_PATA_HPT366=y
 CONFIG_PATA_MPIIX=y
 CONFIG_PATA_OLDPIIX=y
 CONFIG_PATA_NETCELL=y
 CONFIG_PATA_NS87410=y
 CONFIG_PATA_PDC_OLD=y
 CONFIG_PATA_PDC2027X=y
+CONFIG_PATA_PLATFORM=y
 CONFIG_PATA_SIL680=y
 
 ##
@@ -359,38 +361,7 @@
 ##
 ## file: drivers/ide/Kconfig
 ##
-CONFIG_IDE=y
-# CONFIG_BLK_DEV_IDE_SATA is not set
-CONFIG_IDE_GD=y
-CONFIG_IDE_GD_ATA=y
-CONFIG_BLK_DEV_IDECD=m
-CONFIG_BLK_DEV_IDETAPE=m
-# CONFIG_IDE_TASK_IOCTL is not set
-CONFIG_IDE_GENERIC=y
-# CONFIG_BLK_DEV_OFFBOARD is not set
-# CONFIG_BLK_DEV_GENERIC is not set
-# CONFIG_BLK_DEV_OPTI621 is not set
-# CONFIG_BLK_DEV_AEC62XX is not set
-# CONFIG_BLK_DEV_ALI15X3 is not set
-# CONFIG_BLK_DEV_AMD74XX is not set
-# CONFIG_BLK_DEV_CMD64X is not set
-# CONFIG_BLK_DEV_TRIFLEX is not set
-# CONFIG_BLK_DEV_CY82C693 is not set
-# CONFIG_BLK_DEV_CS5520 is not set
-# CONFIG_BLK_DEV_CS5530 is not set
-CONFIG_BLK_DEV_HPT366=y
-# CONFIG_BLK_DEV_JMICRON is not set
-# CONFIG_BLK_DEV_SC1200 is not set
-CONFIG_BLK_DEV_PIIX=y
-# CONFIG_BLK_DEV_IT821X is not set
-# CONFIG_BLK_DEV_NS87415 is not set
-# CONFIG_BLK_DEV_PDC202XX_OLD is not set
-# CONFIG_BLK_DEV_PDC202XX_NEW is not set
-# CONFIG_BLK_DEV_SVWKS is not set
-# CONFIG_BLK_DEV_SIIMAGE is not set
-# CONFIG_BLK_DEV_SLC90E66 is not set
-# CONFIG_BLK_DEV_TRM290 is not set
-# CONFIG_BLK_DEV_VIA82CXXX is not set
+# CONFIG_IDE is not set
 
 ##
 ## file: drivers/input/gameport/Kconfig
@@ -869,6 +840,7 @@
 ## file: drivers/scsi/Kconfig
 

Bug#550320: /bin/sh: error while loading shared libraries: libm.so.6

[Michael Prokop]

* Peng Tao  [Tue Jun 08, 2010 at 09:18:08AM +0800]:
> On Tue, Jun 8, 2010 at 6:58 AM, Michael Prokop  wrote:
> > * maximilian attems  [Mit Mär 24, 2010 at 12:10:31 +0100]:

> >> sorry for late reply, can you still reproduce aboves?

> >> what is ls -l /lib64/libc.so.6
> >> if it is a symlink please provide output of
> >> readlink -f /lib64/libc.so.6
> >> and the ls -l of the target, so
> >> ls -l $( readlink -f /lib64/libc.so.6 )

> > Hi Peng, any news on that?

> > Can you please test current initramfs-tools version (>= 0.95.1) and
> > let us know whether you still explore this issue?

> I've reinstalled my OS with lenny. So I can't reproduce it any more. Sorry.

Thanks for your fast response.

Patrick, are you still able to reproduce that issue?
I can't reproduce it on my own and if no one else stumbles upon this
issue (so we could further debug it) I tend to close this bugreport.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#584891: naming and versioning of linux-image-2.6.32-5-686 and linux-image-2.6.32-trunk-686 confusing

[Ben Hutchings]

On Mon, 2010-06-07 at 14:26 +0200, arne wrote:
> Package: linux-image-2.6
> Severity: normal
> 
> due to some issues i checked today the installed kernel and was rather 
> confused.
> beside others i have installed
> 1) linux-image-2.6.32-trunk-686 
> 2) linux-image-2.6.32-5-686
> 
> dpkg says the versions are respectively
> 1) 2.6.32-5
> 2) 2.6.32-15
> 
> why does -trunk- have the version 2.6.32-5 while -2.6.32-5- has the version 
> 2.6.32-15?

The number (or keyword 'trunk') after '2.6.32' is an ABI version.  It is
like the version '6' that appears in the package name 'libc6' (except
that it changes much more often).  So long as the ABI version stays the
same and is not 'trunk', external modules don't have to be rebuilt for a
new kernel version.

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

Bug#514756: doesn't handle additional arguments in /proc/mdstat, and has device assumptions

[Michael Prokop]

* Martin Michlmayr  [Die Feb 10, 2009 at 05:15:52 +0100]:

> A Debian user ran into a problem with initramfs-tools using a fairly
> strange setup that's described at 
> http://forum.qnap.com/viewtopic.php?f=147&t=11422

> The entry for root in /proc/mdstat looks like this:

> | md1 : active (auto-read-only) raid1 dm-2[1]

> and this is parsed with:

> | block=$(awk "/^${root}/{print substr(\$5, 1, 3); exit}" \
> | /proc/mdstat)

> There are two problems with this:

> 1) initramfs-tools doesn't know about the additional argument
> "(auto-read-only)" and so takes "raid1" rather than "dm-2" as the
> relevant device to parse.

> 2) initramfs-tools only takes the first 3 characters of the device,
> and while this will work for something like sda1, it won't work for
> dm-2.

I've just commited code that addresses this issue:

  
http://git.debian.org/?p=kernel/initramfs-tools.git;a=commit;h=b1c242ffc5762fea6c15fe880e352008a5c34c43

Tested against the following input file which covers several
pitfalls that are known to have been broken:


md9 : active (auto-read-only) raid1 dm-1[0] dm-3[1]

md8 : active (auto-read-only) linear dm-2[1]

md7 : active multipath sda[0] sdb3[1]
  149308032 blocks [2/2] [UU]

md6 : active raid10 sdb4[7](S) sdc4[1] sdh4[6] sdg4[5] sdf4[4] sde4[3] sdd4[2]
  53781280 blocks 32K chunks 2 near-copies [7/6] [_UU]

md5 : active raid0 dm-34[4] dm-33[3] dm-32[2] dm-31[1] dm-30[0]
  52428480 blocks 64k chunks

md4 : active raid5 dm-20[0] dm-24[4] dm-23[3] dm-22[2] dm-21[1]
  2118118912 blocks level 5, 64k chunk, algorithm 2 [5/5] [U]

md3 : active raid6 dm-19[4] dm-18[3] dm-17[2] dm-16[1] dm-15[0]
  981463680 blocks level 6, 64k chunk, algorithm 2 [5/5] [U]
  [===>.]  check = 79.9% (261451776/327154560) 
finish=882.7min speed=1240K/sec

md2 : active raid1 sda[0] sdb[1]
  4883648 blocks [2/2] [UU]

md1 : active raid1 sda3[0] sdb3[1]
  149308032 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sde1[4](S) sdd1[3] sdc1[2] sdb1[1]
  979840 blocks [4/4] []


Will upload soon after some further testing.

regards,
-mika-


signature.asc
Description: Digital signature

Processed: tagging 584217

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 584217 + pending
Bug #584217 [linux-2.6] linux-image-2.6.26-2-686-bigmem: kernel oops in kvm: 
_bounce_end_io_read
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: tagging 584906

[Debian Bug Tracking System]

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

> tags 584906 moreinfo
Bug #584906 [nfs-kernel-server] nfs-kernel-server: nfs stop working suddenly
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#584906: nfs-kernel-server: nfs stop working suddenly

[Ben Hutchings]

On Mon, 2010-06-07 at 15:34 +0200, Leopold Palomo wrote:
> Package: nfs-kernel-server
> Version: 1:1.1.2-6lenny1
> Severity: important
> 
> In this server nfs have been working perfectly one year and half. However,
> lately we have have some serious issues with the nfs. Simply, the service 
> stop and the _only_ way to repair the service is restarting the service.
> 
> In the logs the only reference that we have is:
> 
> orion mountd[4905]: couldn't open /var/lib/nfs/etab
> 
> It's a bit annoying because our little network depends on that service.

Do you have any idea why /var/lib/nfs/etab might be deleted or made
unreadable?  This file is a working copy of /etc/exports (created by
exportfs) and may be read by mountd at any time, so it must always be
present and readable.

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

Bug#584217: [Fwd: Re: Bug#584217: What about Debian Lenny?]

[Ben Hutchings]

 Forwarded Message 
From: Brian 'morlenxus' Miculcy 
To: Ben Hutchings 
Subject: Re: Bug#584217: What about Debian Lenny?
Date: Mon, 7 Jun 2010 15:16:31 +0200

Yes, no more oops.

On Sat, Jun 05, 2010 at 09:17:17PM +0100, Ben Hutchings wrote:
> On Thu, 2010-06-03 at 15:10 +0200, Brian 'morlenxus' Miculcy wrote:
> > Installed linux-source-2.6.26, unpacked, applied the patch - no errors.
> > Don't see why it don't apply for you, i used the debian kernel source
> > package and applied above patch. Can you check that again?
> 
> Did you also build and test that it fixed the bug?
> 
> Ben.
> 
> -- 
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.




--
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/1275961909.14011.11.ca...@localhost

Bug#582177: initramfs-tools: fails to load ram... /proc/mdstat

[Cropper, C. A.]

>
>Can you please provide output of "cat /proc/mdstat" of
>the running linux system?
>

r...@loomis:/# cat /proc/mdstat 
Personalities : [raid1] [raid6] [raid5] [raid4] 
md1 : active raid6 sdg4[0] sde4[5](S) sdf4[4] sdb4[3] sdd4[2] sdc4[1]
  5851753728 blocks level 6, 256k chunk, algorithm 2 [5/5] [U]
  
md0 : active raid1 sdb2[0] sdd2[2](S) sde2[3](S) sdf2[4](S) sdg2[5](S) sdc2[1]
  249792 blocks [2/2] [UU]
  
unused devices: 



-- 
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/201006072127.28639.crop...@acm.org

Bug#550320: /bin/sh: error while loading shared libraries: libm.so.6

[Peng Tao]

On Tue, Jun 8, 2010 at 6:58 AM, Michael Prokop  wrote:
> tags 550320 + moreinfo
> thanks
>
> * maximilian attems  [Mit Mär 24, 2010 at 12:10:31 +0100]:
>> On Tue, 13 Oct 2009, Peng Tao wrote:
>> > On Sat, Oct 10, 2009 at 9:05 AM, Peng Tao  wrote:
>> > > On Fri, Oct 9, 2009 at 5:36 PM, maximilian attems  wrote:
>> > >> thanks, please add
>
>> > >> ldd /bin/busybox
>> > > $ldd initrd/bin/busybox
>> > >        linux-vdso.so.1 =>  (0x7fff9bfff000)
>> > >        libm.so.6 => /lib64/libm.so.6 (0x7f73aa83a000)
>> > >        libc.so.6 => /lib64/libc.so.6 (0x7f73aa4e7000)
>> > >        /lib64/ld-linux-x86-64.so.2 (0x7f73aaabd000)
>> > Just noticed that I should do:
>> > $ldd /bin/busybox
>> >     linux-vdso.so.1 =>  (0x7fff8e1ff000)
>> >     libm.so.6 => /lib64/libm.so.6 (0x7ff6c3af)
>> >     libc.so.6 => /lib64/libc.so.6 (0x7ff6c379d000)
>> >     /lib64/ld-linux-x86-64.so.2 (0x7ff6c3d73000)
>
>> > although the results are same.
>
>> sorry for late reply, can you still reproduce aboves?
>
>> what is ls -l /lib64/libc.so.6
>> if it is a symlink please provide output of
>> readlink -f /lib64/libc.so.6
>> and the ls -l of the target, so
>> ls -l $( readlink -f /lib64/libc.so.6 )
>
> Hi Peng, any news on that?
>
> Can you please test current initramfs-tools version (>= 0.95.1) and
> let us know whether you still explore this issue?
I've reinstalled my OS with lenny. So I can't reproduce it any more. Sorry.

>
> regards,
> -mika-
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iD8DBQFMDXmW2N9T+zficugRAlzwAJ0SdDNHES4I/sVhSsYs1c2R4uWehwCfYrGp
> rSETQ27MK+bFCCMT3VlmvQU=
> =VQw5
> -END PGP SIGNATURE-
>
>



-- 
Thanks,
-Bergwolf



--
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/aanlktinstahtpbl0q8qtmfh08l-epwc-zgzkdhdq7...@mail.gmail.com

Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... BOOT DEBUG DATA

[cropper]

"synchronize"?  I don't understand...

I have actually pulled different devices in-and-out of the MD devices, let the 
MD driver "rebuild" each MD device and made sure the "real" sda is disk number 
0.  It does not seem to change...

C. Cropper


> 
> To the bugreporter: Could you please boot a rescue system / live
> system and synchronize your md device(s) and retry? This strongly
> looks like an issue with out-of-sync data to me.
> 



-- 
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/201006072045.25506.crop...@acm.org

Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... BOOT DEBUG DATA

[Michael Prokop]

* crop...@acm.org  [Mon Jun 07, 2010 at 08:45:25PM -0400]:

> "synchronize"?  I don't understand...

> I have actually pulled different devices in-and-out of the MD devices, let 
> the 
> MD driver "rebuild" each MD device and made sure the "real" sda is disk 
> number 
> 0.  It does not seem to change...

Can you please provide output of "cat /proc/mdstat" of
the running linux system?

regards,
-mika-


signature.asc
Description: Digital signature

Bug#506533: marked as done (initramfs-tools: includes .dpkg-new files into initrd)

[Debian Bug Tracking System]

Your message dated Tue, 8 Jun 2010 02:19:15 +0200
with message-id <2010-06-08t01-57...@devnull.michael-prokop.at>
and subject line [re-]close issue
has caused the Debian Bug report #506533,
regarding initramfs-tools: includes .dpkg-new files into initrd
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.)


-- 
506533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92l
Severity: normal

Hi,

update-initramfs puts a truckload of dpkg-new files into the initrd.
These files should not be included.

Greetings
Marc

-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/root ro profile=2 resume=/dev/mapper/swap1 vga=791 
video=radeon:force_sleep,1400x1050...@60

-- /proc/filesystems
ext3
ext2
iso9660
xfs
udf
vfat

-- lsmod
Module  Size  Used by
snd_seq_dummy   1028  0 
vfat8320  0 
fat37532  1 vfat
nls_utf81024  0 
udf69796  0 
crc_itu_t   1280  1 udf
binfmt_misc 5512  1 
rfcomm 26772  4 
l2cap  17540  9 rfcomm
vboxdrv45472  0 
nf_conntrack_netlink12928  0 
nf_nat 10640  1 nf_conntrack_netlink
nf_conntrack_ipv4   7948  2 nf_nat
nf_conntrack   35888  3 nf_conntrack_netlink,nf_nat,nf_conntrack_ipv4
nfnetlink   1688  4 nf_conntrack_netlink
ipt_ULOG3972  1 
x_tables7300  1 ipt_ULOG
lp  6308  0 
acpi_cpufreq3468  0 
cpufreq_userspace   1304  0 
cpufreq_conservative 3232  0 
cpufreq_stats   2564  0 
cpufreq_powersave768  0 
cpufreq_ondemand3708  1 
freq_table  1796  3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
tun 6916  1 
ipv6  218836  30 
adm1031 8596  0 
hwmon   1172  1 adm1031
sr_mod 11428  0 
sbp2   15372  0 
pcmcia 23716  0 
irtty_sir   2944  0 
sir_dev 7428  1 irtty_sir
snd_intel8x0   20124  1 
irda   75704  1 sir_dev
rtc_cmos6432  0 
snd_intel8x0m   8460  1 
rtc_core8856  1 rtc_cmos
rtc_lib 1536  1 rtc_core
crc_ccitt   1280  1 irda
snd_ac97_codec 77088  2 snd_intel8x0,snd_intel8x0m
ac97_bus 768  1 snd_ac97_codec
snd_pcm50184  3 snd_intel8x0,snd_intel8x0m,snd_ac97_codec
snd_seq33872  1 snd_seq_dummy
snd_timer  14084  2 snd_pcm,snd_seq
snd_seq_device  3724  2 snd_seq_dummy,snd_seq
serio_raw   3076  0 
snd34340  11 
snd_intel8x0,snd_intel8x0m,snd_ac97_codec,snd_pcm,snd_seq,snd_timer,snd_seq_device
soundcore   3552  1 snd
snd_page_alloc  4488  3 snd_intel8x0,snd_intel8x0m,snd_pcm
i2c_i8016416  0 
hci_usb 9368  2 
ipw2200   120520  0 
bluetooth  39780  7 rfcomm,l2cap,hci_usb
ieee80211  22344  1 ipw2200
ieee80211_crypt 2432  1 ieee80211
yenta_socket8204  3 
rsrc_nonstatic  7424  1 yenta_socket
firmware_class  4104  1 ipw2200
pcmcia_core21520  3 pcmcia,yenta_socket,rsrc_nonstatic
parport_pc 17316  1 
parport12992  2 lp,parport_pc
sha256_generic 10496  0 
cbc 2048  7 
dm_crypt9092  1 
usbhid 21120  0 
dm_mirror  13568  0 
dm_log  6272  1 dm_mirror
dm_snapshot11936  0 
dm_mod 34628  44 dm_crypt,dm_mirror,dm_log,dm_snapshot
ide_cd_mod 24836  0 
cdrom  28704  2 sr_mod,ide_cd_mod
ohci1394   23600  0 
tg3   106372  0 
libphy  9472  1 tg3
ieee1394   56132  2 sbp2,ohci1394
ehci_hcd   28172  0 
uhci_hcd   18060  0 

-- /etc/kernel-img.conf
do_symlinks = no
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /usr/sbin/update-grub
postrm_hook   = /usr/sbin/update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto

-- /etc/crypttab
#
root  /dev/mapper/vg0-c_root  none  
luks,keyscript=/etc/

Processed: Re: Bug#549680: fails with RAID over entire IDE disks

[Debian Bug Tracking System]

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

> tags 549680 + fixed pending
Bug #549680 [initramfs-tools] fails with RAID over entire IDE disks
Added tag(s) fixed and pending.
> thanks
Stopping processing here.

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

Bug#549680: fails with RAID over entire IDE disks

[Michael Prokop]

tags 549680 + fixed pending
thanks

* Simon Richter  [Mit Okt 07, 2009 at 09:57:33 +0200]:
> On Wed, Oct 07, 2009 at 12:01:38AM +0200, maximilian attems wrote:

> > please post output of:
> > sh -x mkinitramfs -o /dev/null

> Attached. The bug is fairly obvious, device names in /proc/mdstat are
> always assumed to have a fixed length.

[...]
> + awk /^md0/{print substr($5, 1, 4); exit} /proc/mdstat
> + block=hdc[
> + [ hdc[ != hdc[ ]
> + [ hdc[ != hdc[ ]
> + block=hdc[
> + [ -z hdc[ ]
> + [ ! -e /sys/block/hdc[ ]
> + echo mkinitramfs: for root /dev/mapper/honey-root missing hdc[ /sys/block/ 
> entry
[...]

Thanks for the debug information and spotting the issue.

I've just fixed this issue in git and will upload a new i-t version
which incorporates the fix soon.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#582858: initramfs-tools: MODULES=dep fails when / is ubifs

[Michael Prokop]

* Martin Michlmayr  [Mon Jun 07, 2010 at 06:10:49 +0100]:
> * Martin Michlmayr  [2010-06-07 15:07]:
> > The patch below works for me.  Can you try it?

> I should mention that "works for me" means that the initramfs will be
> generated without error.

Thanks for the patch, Martin.
Can I apply it already to i-t?

> I'm not claiming that you'll actually be able to boot from ubifs with
> that ramdisk though.  For that, i-t needs to be taught to know what to
> do about something like root=ubi0:rootfs.

I see "root=ubi0:root ubi.mtd=2 rootfstype=ubifs" in the additional
information section of the original bugreport. Who does evaluate
this stuff in the guruplug device that's supposed to work?
And what's behind ubi0:root?

regards,
-mika-


signature.asc
Description: Digital signature

Processed: Re: Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... BOOT DEBUG DATA

[Debian Bug Tracking System]

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

> tags 582177 + moreinfo
Bug #582177 [initramfs-tools] initramfs-tools: fails to load ramdisk on boot; 
system with RAID & CRYPTO; udev problems?
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... BOOT DEBUG DATA

[Michael Prokop]

tags 582177 + moreinfo
thanks

* maximilian attems  [Mit Mai 19, 2010 at 09:49:56 +0200]:
> On Wed, May 19, 2010 at 02:50:42PM -0400, crop...@acm.org wrote:

[...]

> > _
> > Kernel output (LITERAL DATA, except for "... area below"):

> > [1.185516] rtc_cmos 00:0a: setting system clock to 2010-05-19 18:18:27 UTC 
> > (1274293107)
> > [1.185628] Waiting 12sec before mounting root device
> > [1.199432] input: AT translated Set 2 keyboard as 
> > /devices/platform/i8042/serio0/input/input1
> > [12.992053] List of all partitions:
> > [12.992128] No filesystem could mount root, tried:
> > [12.992221] kernel panic - no syncing: VFS: unable to mount root fs on 
> > unknown wn-block(0,0)
> > [12.992287] Pid: 1, comm: swapper Not tainted 2.6.32-3-amd64 #1
> > [12.992340] Call Trace:
> > [12.992397] [] ? panic+0x86/0x141
> > ... ......
> > ... ......
> > [12.992880] [] ? child_rip+0x0/0x20

> aboves says that linux-2.6 is not getting the initramfs.
> thus indeed blaming GRUB seems the current state of affair.

[...]

> > Questions:
> > 1) Could this be grub?

> > 2) Could "resynchronizing" md0 fix this problem?  I seem to
> > remember doing something like this and the problem went away in
> > March... :-/

> > 3) Any other suggestions?

> adding GRUB maintainers to Cc as this new bug report seems to be a
> recurring trend. #578473 seems to be duplicate of that one.

> GRUB maintainers can you advise?

To the bugreporter: Could you please boot a rescue system / live
system and synchronize your md device(s) and retry? This strongly
looks like an issue with out-of-sync data to me.

To maks + grub maintainers: any objections against reassigning to grub?

regards,
-mika-


signature.asc
Description: Digital signature

Bug#505609: new lilo package maintainer? (was lilo removal in squeeze or please test grub2)

[Michael Prokop]

[Dropped the @lists.debian.org from Cc]

* Stephen Powell  [Mon Jun 07, 2010 at 11:37:57AM -0400]:
> On Mon, 07 Jun 2010 10:33:52 -0400 (EDT), Holger Levsen wrote:

> > thanks for stepping up maintaining lilo in Debian! I hope you'll manage 
> > this 
> > well.

> Um, thanks; but I don't understand the reassignment of bug number 505609 to
> package initramfs-tools.  If you read my previous posts to the bug log, it
> is clear that this problem started with a change to the maintainer scripts
> between Etch and Lenny.  Please read my posts again carefully.  Then consider
> whether this is really a bug in initramfs-tools or a bug in the kernel 
> maintainer
> scripts.
[...]

ACK. I don't think this is an i-t issue.
Any objections against reassigning back to linux-2.6?

regards,
-mika-


signature.asc
Description: Digital signature

Processed: Re: Bug#550320: /bin/sh: error while loading shared libraries: libm.so.6

[Debian Bug Tracking System]

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

> tags 550320 + moreinfo
Bug #550320 [initramfs-tools] /bin/sh: error while loading shared libraries: 
libm.so.6
Ignoring request to alter tags of bug #550320 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#550320: /bin/sh: error while loading shared libraries: libm.so.6

[Michael Prokop]

tags 550320 + moreinfo
thanks

* maximilian attems  [Mit Mär 24, 2010 at 12:10:31 +0100]:
> On Tue, 13 Oct 2009, Peng Tao wrote:
> > On Sat, Oct 10, 2009 at 9:05 AM, Peng Tao  wrote:
> > > On Fri, Oct 9, 2009 at 5:36 PM, maximilian attems  wrote:
> > >> thanks, please add

> > >> ldd /bin/busybox
> > > $ldd initrd/bin/busybox
> > >        linux-vdso.so.1 =>  (0x7fff9bfff000)
> > >        libm.so.6 => /lib64/libm.so.6 (0x7f73aa83a000)
> > >        libc.so.6 => /lib64/libc.so.6 (0x7f73aa4e7000)
> > >        /lib64/ld-linux-x86-64.so.2 (0x7f73aaabd000)
> > Just noticed that I should do:
> > $ldd /bin/busybox
> > linux-vdso.so.1 =>  (0x7fff8e1ff000)
> > libm.so.6 => /lib64/libm.so.6 (0x7ff6c3af)
> > libc.so.6 => /lib64/libc.so.6 (0x7ff6c379d000)
> > /lib64/ld-linux-x86-64.so.2 (0x7ff6c3d73000)

> > although the results are same.

> sorry for late reply, can you still reproduce aboves?

> what is ls -l /lib64/libc.so.6 
> if it is a symlink please provide output of
> readlink -f /lib64/libc.so.6 
> and the ls -l of the target, so
> ls -l $( readlink -f /lib64/libc.so.6 )

Hi Peng, any news on that?

Can you please test current initramfs-tools version (>= 0.95.1) and
let us know whether you still explore this issue?

regards,
-mika-


signature.asc
Description: Digital signature

Processed: Re: Bug#439846: initramfs-tools 0.93.2 still uses mode instead of mode_option

[Debian Bug Tracking System]

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

> tags 439846 + fixed pending
Bug #439846 [initramfs-tools] framebuffer script badly interprets modedb boot 
parameter
Added tag(s) fixed and pending.
> thanks
Stopping processing here.

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

Bug#439846: initramfs-tools 0.93.2 still uses mode instead of mode_option

[Michael Prokop]

tags 439846 + fixed pending
thanks

* maximilian attems  [Fre Apr 24, 2009 at 10:51:02 +0200]:
> On Fri, Apr 24, 2009 at 10:17:27AM +0200, Evgeni Golov wrote:

> > this problem still exists in the current sid version of initramfs-tools.
> > Any plans for updating the framebuffer script?
> > Most fb drivers use mode_option instead now (and some use both for
> > compatibility reasons).

> sure if you looked through the linux-2.6 sources,
> you would see it is not a clear cut. some important
> fb driver still use *exclusively* the old module option.
> so until someone clears that up changing the param is not the way to go.

The framebuffer script has been nuked in git commit
db24ed6ec7887631c05ce0d51c53c8c2cb9c507a which was released as
version initramfs-tools 0.94.

The old framebuffer script is shipped as example through the docs,
I've just added additional information regarding the mode vs.
mode_option issue.

This bug shouldn't be present any longer, if you still run into
problems regardings this issue please feel free to report back.

regards,
-mika-


signature.asc
Description: Digital signature

Processed: Re: Bug#584520: initramfs-tools: copy_exec hook function may exit with a non-zero return value in non-verbose mode

[Debian Bug Tracking System]

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

> tags 584520 + fixed pending
Bug #584520 [initramfs-tools] initramfs-tools: copy_exec hook function may exit 
with a non-zero return value in non-verbose mode
Added tag(s) fixed and pending.
> thanks
Stopping processing here.

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

Bug#584520: initramfs-tools: copy_exec hook function may exit with a non-zero return value in non-verbose mode

[Michael Prokop]

tags 584520 + fixed pending
thanks

* Gerrit Keller  [Fre Jun 04, 2010 at 11:23:21 +0200]:

> copy_exec hook function may exit with a non-zero return value in non-verbose
> mode

> The copy_exec hook function could exit with a return value of 1 in non-verbose
> mode. This happens due to the last command being
> [ "${verbose}" = "y" ] && echo "Adding library ${x}"
> whose return value will be used as the return value for the function. This
> makes hook scripts with a 'set -e' statement abort after the call (see bug
> #578065).
> I've attached a trivial patch which fixes the problem.

Good catch, thanks. Applied and will be uploaded soon.

regards,
-mika-


signature.asc
Description: Digital signature

Processed: Re: Bug#584259: initramfs-tools: breaks software suspend (hibernation)

[Debian Bug Tracking System]

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

> tags 584259 + moreinfo
Bug #584259 [initramfs-tools] initramfs-tools: breaks software suspend 
(hibernation)
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#584259: initramfs-tools: breaks software suspend (hibernation)

[Michael Prokop]

tags 584259 + moreinfo
thanks

* Willi Mann  [Mit Jun 02, 2010 at 06:13:08 +0200]:

> Since the upgrade to 0.94.4 in testing, software suspend's resume
> does not complete. The screen it ends up with is black except a blinking 
> cursor,
> but I can use Alt+F1 to switch to a screen that shows some messages 
> concerning 
> hibernation. In this screen, typed keys are shown on the screen, but no 
> further
> action (especially no reaction of Sys-Rq keys) can be started. Particularly, 
> it
> is not possible to undo the switch done with Alt+F1. 

> I mainly tested the suspend with s2disk from uswsusp, but it's also
> reproduceable with the in-kernel suspend method.

> Downgrading to version 0.93.4 solves the issue (only tested with s2disk). 
> I haven't yet tested the intermediate versions that only ended up in 
> unstable.

[...]

> -- resume
> # RESUME=/dev/sda6
> RESUME='LABEL=amdlinux-swap'

Does it work with 'RESUME=/dev/disk/by-label/amdlinux-swap'?

If it still does not work then: can you please extract the broken
and the working initramfs[1] and check the difference between them?
Especially the included configuration files and the list of files
would be interesting.

[1] Extract the initramfs running:

 cd /tmp/
 mkdir initramfs
 cd initramfs
 gunzip -c /boot/initrd.img-2.6.33... | cpio -i -d -H newc 
--no-absolute-filenames

regards,
-mika-


signature.asc
Description: Digital signature

Processed: tagging 584945, bug 584945 is forwarded to de...@driverdev.osuosl.org

[Debian Bug Tracking System]

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

> tags 584945 upstream
Bug #584945 [linux-2.6] New RTL8192SU variant unsupported
Added tag(s) upstream.
> forwarded 584945 de...@driverdev.osuosl.org
Bug #584945 [linux-2.6] New RTL8192SU variant unsupported
Set Bug forwarded-to-address to 'de...@driverdev.osuosl.org'.
> thanks
Stopping processing here.

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

Bug#584945: rtl8192s_usb vs rtl8192u_usb device IDs

[Ben Hutchings]

Greg,

There seems to be some confusion between the two staging drivers
rtl8192s_usb (aka rtl8192su) and rtl8192u_usb (aka rtl8192u).

Guy Sheffer reported problems using rtl8192s_usb in 2.6.34:
> It is detected, but then returns: unknown rf chip, can't set channel map
> in function:rtl819x_set_channel_map() in dmesg

The USB device has device ID 0bda:8192.  This error appears to indicate
that this test in rtl8192SU_read_eeprom_info() failed:

// To check autoload success or not.
if (tmpU1b & CmdEEPROM_En)

In the vendor driver that came with this device,
, I 
see two separate lists of device IDs for 'RTL8192SU' and 'RTL8192U':

#ifdef RTL8192SU
{USB_DEVICE(0x0bda, 0x8171)},
{USB_DEVICE(0x0bda, 0x8172)},
{USB_DEVICE(0x0bda, 0x8173)},
{USB_DEVICE(0x0bda, 0x8174)},
{USB_DEVICE(0x0bda, 0x8712)},
{USB_DEVICE(0x0bda, 0x8713)},
{USB_DEVICE(0x07aa, 0x0047)},
{USB_DEVICE(0x07d1, 0x3303)},
{USB_DEVICE(0x07d1, 0x3302)},
{USB_DEVICE(0x07d1, 0x3300)},
{USB_DEVICE(0x1740, 0x9603)},
{USB_DEVICE(0x1740, 0x9605)},
{USB_DEVICE(0x050d, 0x815F)},
{USB_DEVICE(0x06f8, 0xe031)},
{USB_DEVICE(0x7392, 0x7612)},
{USB_DEVICE(0x0DF6, 0x0045)},
{USB_DEVICE(0x0E66, 0x0015)},
{USB_DEVICE(0x0E66, 0x0016)},
#else   
{USB_DEVICE(0x0bda, 0x8192)},
{USB_DEVICE(0x0bda, 0x8709)},
{USB_DEVICE(0x07aa, 0x0043)},
{USB_DEVICE(0x050d, 0x805E)},
{USB_DEVICE(0x0df6, 0x0031)},
{USB_DEVICE(0x1740, 0x9201)},
{USB_DEVICE(0x2001, 0x3301)},
{USB_DEVICE(0x5a57, 0x0290)},
{USB_DEVICE(0x043E, 0x7A01)},
#endif  

In mainline, rtl8192su_usb claims a superset of the device IDs of
rtl8192u_usb, but does not seem to include the code to support the
'RTL8192U' devices.  For example, the vendor driver has different EEPROM
access code for the RTL8192U devices, which would explain the failure
Guy reported.

I think the device IDs listed in rtl8192u_usb should be removed from
rtl8192s_usb.

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: notfound 584945 in 2.6.34-1~experemental.2, found 584945 in 2.6.34-1~experimental.2

[Debian Bug Tracking System]

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

> # typo
> notfound 584945 2.6.34-1~experemental.2
Bug #584945 [linux-2.6] New RTL8192SU variant unsupported
There is no source info for the package 'linux-2.6' at version 
'2.6.34-1~experemental.2' with architecture ''
Unable to make a source version for version '2.6.34-1~experemental.2'
Bug No longer marked as found in versions 2.6.34-1~experemental.2.
> found 584945 2.6.34-1~experimental.2
Bug #584945 [linux-2.6] New RTL8192SU variant unsupported
There is no source info for the package 'linux-2.6' at version 
'2.6.34-1~experimental.2' with architecture ''
Unable to make a source version for version '2.6.34-1~experimental.2'
Bug Marked as found in versions 2.6.34-1~experimental.2.
> thanks
Stopping processing here.

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

Processed: tagging 584830, bug 584830 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=16153

[Debian Bug Tracking System]

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

> tags 584830 upstream
Bug #584830 [linux-2.6] linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents 
suspend
Ignoring request to alter tags of bug #584830 to the same tags previously set
> forwarded 584830 https://bugzilla.kernel.org/show_bug.cgi?id=16153
Bug #584830 [linux-2.6] linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents 
suspend
Changed Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=16153' from 
'linux-...@vger.kernel.org'
> thanks
Stopping processing here.

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

Processed: tagging 584945, severity of 584945 is wishlist

[Debian Bug Tracking System]

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

> tags 584945 moreinfo
Bug #584945 [linux-2.6] New RTL8192SU variant unsupported
Added tag(s) moreinfo.
> severity 584945 wishlist
Bug #584945 [linux-2.6] New RTL8192SU variant unsupported
Severity set to 'wishlist' from 'normal'

> thanks
Stopping processing here.

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

Processed: retitle 584945 to New RTL8192SU variant unsupported

[Debian Bug Tracking System]

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

> retitle 584945 New RTL8192SU variant unsupported
Bug #584945 [linux-2.6] linux-2.6: 0bda:8172 Realtek USB WiFi unsupported
Changed Bug title to 'New RTL8192SU variant unsupported' from 'linux-2.6: 
0bda:8172 Realtek USB WiFi unsupported'
> thanks
Stopping processing here.

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

Bug#584945: linux-2.6: 0bda:8172 Realtek USB WiFi unsupported

[Ben Hutchings]

On Mon, 2010-06-07 at 21:01 +0300, Guy Sheffer wrote:
> Package: linux-2.6
> Version: 2.6.34-1~experemental.2
> Severity: normal
> 
> This device should be supported (at least it says that on the cover, and
> supplied driver, which does not compile anymore).

The hardware vendor seems to have lied to you.

Please send the supplied driver and I can try to puzzle out what the
important change is.

> It is detected, but then returns: unknown rf chip, can't set channel map
> in function:rtl819x_set_channel_map() in dmesg
> 
> Seems to be a related problem to the recently fixed #580740
> The device gets an interface, but no rf signals seem to be detected
> (compared to a wifi card next to it, right next to the AP).
[...]

That's an entirely different problem - the driver did not claim the
device ID for a device that it could handle.  Here we have a device that
it can't handle.

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: severity of 584784 is important

[Debian Bug Tracking System]

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

> # This would normally be RC, but since no-one spotted it for 2 months this 
> platform does not seem important enough to block transition to testing.
> severity 584784 important
Bug #584784 [linux-2.6] /boot/vmlinux-2.6.34-1-4kc-malta: no longer boots in 
qemu
Severity set to 'important' from 'grave'

> thanks
Stopping processing here.

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

Bug#584784: also applies to unstable

[Ben Hutchings]

On Mon, 2010-06-07 at 19:59 +0200, Willi Mann wrote:
> Am 2010-06-07 03:44, schrieb Ben Hutchings:
> > On Sun, 2010-06-06 at 23:18 +0200, Willi Mann wrote:
> >>> "Kernel panic - not syncing: To avoid data corruption io_map_base MUST
> >>> be set with multiple PCI domains."
> >>>
> >>> has been applied on all PCI MIPS systems since Linux 2.6.24.  Are you
> >>> quite sure that this was introduced by the kernel upgrade and not a qemu
> >>> upgrade.
> >>
> >> Yes, I didn't change the qemu version, it's really only the kernel that
> >> changed.
> >>
> >> Attached is the dmesg output of the working kernel, version 2.6.32-9.
> > 
> > OK, it looks like this is due to an botched switch from IDE to libata
> > drivers on MIPS.  The qemu emulated HD controller is now being handled
> > by the ide-generic driver whereas it should have been switched from piix
> > to ata_piix, and ide-generic triggers this panic for reasons I don't
> > fully understand.
> > 
> > This will get fixed, but not immediately.
> 
> OK. As long as it gets fixed before the release... Should we notify the
> d-i people so that they can put a note on the errata page?

I'm cc'ing this to the d-i mailing list.

> Though I wonder why the BTS did not fully process my "found" command. It
> still only marks the version in experimental as affected.

No it doesn't.  You may be looking at a cached version of the page.

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

Bug#584944: marked as done (linux-image-2.6.32-5-amd64: Update-grub fails)

[Debian Bug Tracking System]

Your message dated Mon, 7 Jun 2010 20:59:47 +0200
with message-id <20100607185947.gb22...@wavehammer.waldi.eu.org>
and subject line Re: Bug#584944: linux-image-2.6.32-5-amd64: Update-grub fails
has caused the Debian Bug report #584944,
regarding linux-image-2.6.32-5-amd64: Update-grub fails
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.)


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


aptitude installation attempt produces:
Setting up linux-image-2.6.32-5-amd64 (2.6.32-15) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169
cryptsetup: WARNING: target sda3_crypt has a random key, skipped
Running update-grub.
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1

-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/osgiliath-root ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[4.805507]  (Note that use of the override may cause unknown side effects.)
[4.805516] amd64_edac: probe of :00:18.2 failed with error -22
[4.885511] Linux video capture interface: v2.00
[4.919746] saa7146: register extension 'budget_av'.
[4.919800]   alloc irq_desc for 20 on node 0
[4.919801]   alloc kstat_irqs on node 0
[4.919808] budget_av :03:02.0: PCI INT A -> GSI 20 (level, low) -> IRQ 
20
[4.919918] IRQ 20/: IRQF_DISABLED is not guaranteed on shared IRQs
[4.919935] saa7146: found saa7146 @ mem c9001283cc00 (revision 1, irq 
20) (0x1894,0x0020).
[4.919940] saa7146 (0): dma buffer size 192512
[4.919941] DVB: registering new adapter (KNC1 DVB-C)
[4.956951] adapter failed MAC signature check
[4.956953] encoded MAC from EEPROM was 
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
[4.972126] nvidia :01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[4.972133] nvidia :01:00.0: setting latency timer to 64
[4.972137] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[4.972262] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  195.36.24  Thu 
Apr 22 19:10:14 PDT 2010
[5.091378] HDA Intel :00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 
16
[5.167828] hda_codec: ALC888: BIOS auto-probing.
[5.169426] input: HDA Digital PCBeep as 
/devices/pci:00/:00:14.2/input/input6
[5.220378] KNC1-0: MAC addr = 00:09:d6:6d:6b:af
[5.416674] TDA10021: i2c-addr = 0x0c, id = 0x7c
[5.416677] DVB: registering adapter 0 frontend 0 (Philips TDA10021 DVB-C)...
[5.416765] budget-av: ci interface initialised.
[5.855492] EXT3 FS on dm-0, internal journal
[6.138714] padlock: VIA PadLock not detected.
[6.162546] padlock: VIA PadLock Hash Engine not detected.
[6.652203] usb-storage: device scan complete
[6.658435] scsi 6:0:0:0: Direct-Access Generic- Compact Flash1.00 
PQ: 0 ANSI: 0 CCS
[6.664673] scsi 6:0:0:1: Direct-Access Generic- SM/xD-Picture1.00 
PQ: 0 ANSI: 0 CCS
[6.670924] scsi 6:0:0:2: Direct-Access Generic- SD/MMC   1.00 
PQ: 0 ANSI: 0 CCS
[6.677174] scsi 6:0:0:3: Direct-Access Generic- MS/MS-Pro1.00 
PQ: 0 ANSI: 0 CCS
[6.677488] sd 6:0:0:0: Attached scsi generic sg4 type 0
[6.677588] sd 6:0:0:1: Attached scsi generic sg5 type 0
[6.677780] sd 6:0:0:2: Attached scsi generic sg6 type 0
[6.677949] sd 6:0:0:3: Attached scsi generic sg7 type 0
[6.897603] usb-storage: device scan complete
[6.898090] scsi 7:0:0:0: Direct-Access Generic  USB SD Reader1.00 
PQ: 0 ANSI: 0
[6.898581] scsi 7:0:0:1: Direct-Access Generic  USB CF Reader1.01 
PQ: 0 ANSI: 0
[6.899079] scsi 7:0:0:2: Direct-Access Generic  USB SM Reader1.02 
PQ: 0 ANSI: 0
[6.899579] scsi 7:0:0:3: Direct-Access Generic  USB MS Reader1.03 
PQ: 0 ANSI: 0
[6.899886] sd 7:0:0:0: Attached scsi generic sg8 ty

Bug#584948: marked as done (linux-image-2.6.34-1-amd64: Incompatible build without ABI bump)

[Debian Bug Tracking System]

Your message dated Mon, 7 Jun 2010 20:58:22 +0200
with message-id <20100607185822.ga22...@wavehammer.waldi.eu.org>
and subject line Re: Bug#584948: linux-image-2.6.34-1-amd64: Incompatible build 
without ABI bump
has caused the Debian Bug report #584948,
regarding linux-image-2.6.34-1-amd64: Incompatible build without ABI bump
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.)


-- 
584948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.34-1~experimental.2
Severity: important

As you can see in dmesg, vboxdrv and fglrx could not be loaded, because the ABI 
is incompatible with .1

-- Package-specific info:
** Version:
Linux version 2.6.34-1-amd64 (Debian 2.6.34-1~experimental.2) 
(b...@decadent.org.uk) (gcc version 4.4.4 (Debian 4.4.4-4) ) #1 SMP Sun Jun 6 
22:29:25 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.34-1-amd64 
root=UUID=8ce883ce-13bc-4d1e-aff8-d5efc1e40077 ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[2.312353] generic-usb 0003:045E:00DD.0002: input,hidraw1: USB HID v1.11 
Keyboard [Microsoft Comfort Curve Keyboard 2000] on usb-:00:02.0-2/input0
[2.330164] input: Microsoft Comfort Curve Keyboard 2000 as 
/devices/pci:00/:00:02.0/usb2/2-2/2-2:1.1/input/input2
[2.330200] generic-usb 0003:045E:00DD.0003: input,hidraw2: USB HID v1.11 
Device [Microsoft Comfort Curve Keyboard 2000] on usb-:00:02.0-2/input1
[7.076014] scsi2 : 3ware Storage Controller
[7.076068] 3w-: scsi2: Found a 3ware Storage Controller at 0xdc00, IRQ: 
19.
[7.076381] 8139cp :01:0a.0: This (id 10ec:8139 rev 10) is not an 8139C+ 
compatible chip, use 8139too
[7.076461] scsi 2:0:0:0: Direct-Access 3wareLogical Disk 0   1.2  
PQ: 0 ANSI: 0
[7.078466] 8139too: 8139too Fast Ethernet driver 0.9.28
[7.078963] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 18
[7.078969]   alloc irq_desc for 18 on node 0
[7.078971]   alloc kstat_irqs on node 0
[7.078981] 8139too :01:0a.0: PCI INT A -> Link[LNKC] -> GSI 18 (level, 
low) -> IRQ 18
[7.079152] sd 2:0:0:0: Attached scsi generic sg5 type 0
[7.079915] 8139too :01:0a.0: eth0: RealTek RTL8139 at 
0xc967e800, 00:02:2a:df:47:10, IRQ 18
[7.080374] sd 2:0:0:0: [sdd] 586112656 512-byte logical blocks: (300 GB/279 
GiB)
[7.080386] sd 2:0:0:0: [sdd] Write Protect is off
[7.080388] sd 2:0:0:0: [sdd] Mode Sense: 00 00 00 00
[7.080690] sd 2:0:0:0: [sdd] Write cache: enabled, read cache: disabled, 
supports DPO and FUA
[7.081666]  sdd: sdd1
[7.091252] sd 2:0:0:0: [sdd] Attached SCSI disk
[7.241709] PM: Starting manual resume from disk
[7.241713] PM: Resume from partition 8:2
[7.241714] PM: Checking hibernation image.
[7.241863] PM: Error -22 checking image file
[7.241864] PM: Resume from disk failed.
[7.271847] kjournald starting.  Commit interval 5 seconds
[7.271855] EXT3-fs (sda4): mounted filesystem with ordered data mode
[8.775766] udev: starting version 157
[9.155858] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[9.155869] ACPI: Power Button [PWRB]
[9.155988] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[9.155992] ACPI: Power Button [PWRF]
[9.242845] input: PC Speaker as /devices/platform/pcspkr/input/input5
[9.333492] k8temp :00:18.3: Temperature readouts might be wrong - check 
erratum #141
[9.457889] i2c i2c-0: nForce2 SMBus adapter at 0x2d00
[9.457924] i2c i2c-1: nForce2 SMBus adapter at 0x2e00
[9.573869] EDAC MC: Ver: 2.1.0 Jun  6 2010
[9.591603] EDAC amd64_edac:  Ver: 3.3.0 Jun  6 2010
[9.591853] EDAC amd64: This node reports that Memory ECC is currently 
disabled, set F3x44[22] (:00:18.3).
[9.591861] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
[9.591862]  Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
[9.591863]  (Note that use of the override may cause unknown side effects.)
[9.592002] amd64_edac: probe of :00:18.2 failed with error -22
[   10.057646] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[   10.057651]   alloc irq_desc for 20 on node 0
[   10.057653]   alloc kstat_irqs on node 0
[   10.057664] HDA Intel :00:07.0: PCI INT B -> Link[LAZA] -> GSI 20 
(level, low) -> IRQ 20
[   10.057667] hda_intel: Disable MSI for Nvidia chipset
[   10.057763] HDA Intel :00:07.0: setting lat

Bug#584948: linux-image-2.6.34-1-amd64: Incompatible build without ABI bump

[Patrick Matthäi]

Package: linux-2.6
Version: 2.6.34-1~experimental.2
Severity: important

As you can see in dmesg, vboxdrv and fglrx could not be loaded, because the ABI 
is incompatible with .1

-- Package-specific info:
** Version:
Linux version 2.6.34-1-amd64 (Debian 2.6.34-1~experimental.2) 
(b...@decadent.org.uk) (gcc version 4.4.4 (Debian 4.4.4-4) ) #1 SMP Sun Jun 6 
22:29:25 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.34-1-amd64 
root=UUID=8ce883ce-13bc-4d1e-aff8-d5efc1e40077 ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[2.312353] generic-usb 0003:045E:00DD.0002: input,hidraw1: USB HID v1.11 
Keyboard [Microsoft Comfort Curve Keyboard 2000] on usb-:00:02.0-2/input0
[2.330164] input: Microsoft Comfort Curve Keyboard 2000 as 
/devices/pci:00/:00:02.0/usb2/2-2/2-2:1.1/input/input2
[2.330200] generic-usb 0003:045E:00DD.0003: input,hidraw2: USB HID v1.11 
Device [Microsoft Comfort Curve Keyboard 2000] on usb-:00:02.0-2/input1
[7.076014] scsi2 : 3ware Storage Controller
[7.076068] 3w-: scsi2: Found a 3ware Storage Controller at 0xdc00, IRQ: 
19.
[7.076381] 8139cp :01:0a.0: This (id 10ec:8139 rev 10) is not an 8139C+ 
compatible chip, use 8139too
[7.076461] scsi 2:0:0:0: Direct-Access 3wareLogical Disk 0   1.2  
PQ: 0 ANSI: 0
[7.078466] 8139too: 8139too Fast Ethernet driver 0.9.28
[7.078963] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 18
[7.078969]   alloc irq_desc for 18 on node 0
[7.078971]   alloc kstat_irqs on node 0
[7.078981] 8139too :01:0a.0: PCI INT A -> Link[LNKC] -> GSI 18 (level, 
low) -> IRQ 18
[7.079152] sd 2:0:0:0: Attached scsi generic sg5 type 0
[7.079915] 8139too :01:0a.0: eth0: RealTek RTL8139 at 
0xc967e800, 00:02:2a:df:47:10, IRQ 18
[7.080374] sd 2:0:0:0: [sdd] 586112656 512-byte logical blocks: (300 GB/279 
GiB)
[7.080386] sd 2:0:0:0: [sdd] Write Protect is off
[7.080388] sd 2:0:0:0: [sdd] Mode Sense: 00 00 00 00
[7.080690] sd 2:0:0:0: [sdd] Write cache: enabled, read cache: disabled, 
supports DPO and FUA
[7.081666]  sdd: sdd1
[7.091252] sd 2:0:0:0: [sdd] Attached SCSI disk
[7.241709] PM: Starting manual resume from disk
[7.241713] PM: Resume from partition 8:2
[7.241714] PM: Checking hibernation image.
[7.241863] PM: Error -22 checking image file
[7.241864] PM: Resume from disk failed.
[7.271847] kjournald starting.  Commit interval 5 seconds
[7.271855] EXT3-fs (sda4): mounted filesystem with ordered data mode
[8.775766] udev: starting version 157
[9.155858] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[9.155869] ACPI: Power Button [PWRB]
[9.155988] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[9.155992] ACPI: Power Button [PWRF]
[9.242845] input: PC Speaker as /devices/platform/pcspkr/input/input5
[9.333492] k8temp :00:18.3: Temperature readouts might be wrong - check 
erratum #141
[9.457889] i2c i2c-0: nForce2 SMBus adapter at 0x2d00
[9.457924] i2c i2c-1: nForce2 SMBus adapter at 0x2e00
[9.573869] EDAC MC: Ver: 2.1.0 Jun  6 2010
[9.591603] EDAC amd64_edac:  Ver: 3.3.0 Jun  6 2010
[9.591853] EDAC amd64: This node reports that Memory ECC is currently 
disabled, set F3x44[22] (:00:18.3).
[9.591861] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
[9.591862]  Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
[9.591863]  (Note that use of the override may cause unknown side effects.)
[9.592002] amd64_edac: probe of :00:18.2 failed with error -22
[   10.057646] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
[   10.057651]   alloc irq_desc for 20 on node 0
[   10.057653]   alloc kstat_irqs on node 0
[   10.057664] HDA Intel :00:07.0: PCI INT B -> Link[LAZA] -> GSI 20 
(level, low) -> IRQ 20
[   10.057667] hda_intel: Disable MSI for Nvidia chipset
[   10.057763] HDA Intel :00:07.0: setting latency timer to 64
[   10.584016] hda_codec: ALC888: BIOS auto-probing.
[   10.824087] input: HDA Digital PCBeep as 
/devices/pci:00/:00:07.0/input/input6
[   11.136496] ACPI: PCI Interrupt Link [LNEA] enabled at IRQ 17
[   11.136501]   alloc irq_desc for 17 on node 0
[   11.136503]   alloc kstat_irqs on node 0
[   11.136514] HDA Intel :04:00.1: PCI INT B -> Link[LNEA] -> GSI 17 
(level, low) -> IRQ 17
[   11.136572]   alloc irq_desc for 29 on node 0
[   11.136574]   alloc kstat_irqs on node 0
[   11.136582] HDA Intel :04:00.1: irq 29 for MSI/MSI-X
[   11.136606] HDA Intel :04:00.1: setting latency timer to 64
[   15.320120] Adding 1951892k swap on /dev/sda2.  Priority:-1 extents:1 
across:1951892k 
[   15.629879] EXT3-fs (sda4): using internal journal
[   15.822259] loop: module loaded
[   15.841596] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 
5200+ processors (2 cpu 

Bug#584784: also applies to unstable

[Willi Mann]

Am 2010-06-07 03:44, schrieb Ben Hutchings:
> On Sun, 2010-06-06 at 23:18 +0200, Willi Mann wrote:
>>> "Kernel panic - not syncing: To avoid data corruption io_map_base MUST
>>> be set with multiple PCI domains."
>>>
>>> has been applied on all PCI MIPS systems since Linux 2.6.24.  Are you
>>> quite sure that this was introduced by the kernel upgrade and not a qemu
>>> upgrade.
>>
>> Yes, I didn't change the qemu version, it's really only the kernel that
>> changed.
>>
>> Attached is the dmesg output of the working kernel, version 2.6.32-9.
> 
> OK, it looks like this is due to an botched switch from IDE to libata
> drivers on MIPS.  The qemu emulated HD controller is now being handled
> by the ide-generic driver whereas it should have been switched from piix
> to ata_piix, and ide-generic triggers this panic for reasons I don't
> fully understand.
> 
> This will get fixed, but not immediately.

OK. As long as it gets fixed before the release... Should we notify the
d-i people so that they can put a note on the errata page?

Though I wonder why the BTS did not fully process my "found" command. It
still only marks the version in experimental as affected.

WM



-- 
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/4c0d339d.8090...@wm1.at

Bug#584945: linux-2.6: 0bda:8172 Realtek USB WiFi unsupported

[Guy Sheffer]

Package: linux-2.6
Version: 2.6.34-1~experemental.2
Severity: normal

This device should be supported (at least it says that on the cover, and
supplied driver, which does not compile anymore).
It is detected, but then returns: unknown rf chip, can't set channel map
in function:rtl819x_set_channel_map() in dmesg

Seems to be a related problem to the recently fixed #580740
The device gets an interface, but no rf signals seem to be detected
(compared to a wifi card next to it, right next to the AP).

Full dmesg output is:
[  996.420056] usb 3-2: new full speed USB device using uhci_hcd and
address 7
[  996.563524] usb 3-2: not running at top speed; connect to a high
speed hub
[  996.586066] usb 3-2: New USB device found, idVendor=0bda,
idProduct=8192
[  996.586074] usb 3-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[  996.586082] usb 3-2: Product: 802.11n WLAN Adapter
[  996.586087] usb 3-2: Manufacturer: Realtek
[  996.595937] ==>ep_num:6, in_ep_num:1, out_ep_num:5
[  996.595943] ==>RtInPipes:3  
[  996.595949] ==>RtOutPipes:4  5  6  7  13  
[  996.595959] ==>txqueue_to_outpipemap for BK, BE, VI, VO, HCCA, TXCMD,
MGNT, HIGH, BEACON:
[  996.595965] 3  2  1  0  4  4  4  4  4  
[  996.635059] Dot11d_Init()
[  996.635063] rtl819xU:unknown rf chip, can't set channel map in
function:rtl819x_set_channel_map()
[  996.635065] 
[  996.705600] udev: renamed network interface wlan0 to wlan11

lsusb:
0bda:8192 Realtek Semiconductor Corp.

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

Kernel: Linux 2.6.34-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
42


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

Bug#584944: linux-image-2.6.32-5-amd64: Update-grub fails

[Johannes Graumann]

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


aptitude installation attempt produces:
Setting up linux-image-2.6.32-5-amd64 (2.6.32-15) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169
cryptsetup: WARNING: target sda3_crypt has a random key, skipped
Running update-grub.
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.32-5-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1

-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/osgiliath-root ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[4.805507]  (Note that use of the override may cause unknown side effects.)
[4.805516] amd64_edac: probe of :00:18.2 failed with error -22
[4.885511] Linux video capture interface: v2.00
[4.919746] saa7146: register extension 'budget_av'.
[4.919800]   alloc irq_desc for 20 on node 0
[4.919801]   alloc kstat_irqs on node 0
[4.919808] budget_av :03:02.0: PCI INT A -> GSI 20 (level, low) -> IRQ 
20
[4.919918] IRQ 20/: IRQF_DISABLED is not guaranteed on shared IRQs
[4.919935] saa7146: found saa7146 @ mem c9001283cc00 (revision 1, irq 
20) (0x1894,0x0020).
[4.919940] saa7146 (0): dma buffer size 192512
[4.919941] DVB: registering new adapter (KNC1 DVB-C)
[4.956951] adapter failed MAC signature check
[4.956953] encoded MAC from EEPROM was 
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
[4.972126] nvidia :01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[4.972133] nvidia :01:00.0: setting latency timer to 64
[4.972137] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[4.972262] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  195.36.24  Thu 
Apr 22 19:10:14 PDT 2010
[5.091378] HDA Intel :00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 
16
[5.167828] hda_codec: ALC888: BIOS auto-probing.
[5.169426] input: HDA Digital PCBeep as 
/devices/pci:00/:00:14.2/input/input6
[5.220378] KNC1-0: MAC addr = 00:09:d6:6d:6b:af
[5.416674] TDA10021: i2c-addr = 0x0c, id = 0x7c
[5.416677] DVB: registering adapter 0 frontend 0 (Philips TDA10021 DVB-C)...
[5.416765] budget-av: ci interface initialised.
[5.855492] EXT3 FS on dm-0, internal journal
[6.138714] padlock: VIA PadLock not detected.
[6.162546] padlock: VIA PadLock Hash Engine not detected.
[6.652203] usb-storage: device scan complete
[6.658435] scsi 6:0:0:0: Direct-Access Generic- Compact Flash1.00 
PQ: 0 ANSI: 0 CCS
[6.664673] scsi 6:0:0:1: Direct-Access Generic- SM/xD-Picture1.00 
PQ: 0 ANSI: 0 CCS
[6.670924] scsi 6:0:0:2: Direct-Access Generic- SD/MMC   1.00 
PQ: 0 ANSI: 0 CCS
[6.677174] scsi 6:0:0:3: Direct-Access Generic- MS/MS-Pro1.00 
PQ: 0 ANSI: 0 CCS
[6.677488] sd 6:0:0:0: Attached scsi generic sg4 type 0
[6.677588] sd 6:0:0:1: Attached scsi generic sg5 type 0
[6.677780] sd 6:0:0:2: Attached scsi generic sg6 type 0
[6.677949] sd 6:0:0:3: Attached scsi generic sg7 type 0
[6.897603] usb-storage: device scan complete
[6.898090] scsi 7:0:0:0: Direct-Access Generic  USB SD Reader1.00 
PQ: 0 ANSI: 0
[6.898581] scsi 7:0:0:1: Direct-Access Generic  USB CF Reader1.01 
PQ: 0 ANSI: 0
[6.899079] scsi 7:0:0:2: Direct-Access Generic  USB SM Reader1.02 
PQ: 0 ANSI: 0
[6.899579] scsi 7:0:0:3: Direct-Access Generic  USB MS Reader1.03 
PQ: 0 ANSI: 0
[6.899886] sd 7:0:0:0: Attached scsi generic sg8 type 0
[6.900050] sd 7:0:0:1: Attached scsi generic sg9 type 0
[6.900212] sd 7:0:0:2: Attached scsi generic sg10 type 0
[6.900368] sd 7:0:0:3: Attached scsi generic sg11 type 0
[6.904482] sd 7:0:0:0: [sdh] Attached SCSI removable disk
[6.905082] sd 7:0:0:1: [sdi] Attached SCSI removable disk
[6.905868] sd 7:0:0:2: [sdj] Attached SCSI removable disk
[6.906580] sd 7:0:0:3: [sdk] Attached SCSI removable disk
[7.057768] sd 6:0:0:1: [sde] Attached SCSI removable disk
[7.057981] sd 6:0:0:0: [sdd] 2014992 512-byte logical blocks: (1.03 GB/983 
MiB)
[7.058727] sd 6:0:0:2: [sdf] Attached SCSI removable disk
[7.059351] sd 6:0:0:3: [sdg] Attached SCSI removable disk
[7.060103] sd 6:0:0:0: [sdd] Write Protect is off
[7.060106] sd 6:0:0:0: [sdd] Mode Sense: 03 00 00 00
[7.060107] sd 6:0:0:0: [sdd] Assuming drive cache: write thr

Bug#583643: marked as done (linux-image-2.6.34-1-686: iwlagn disassociate under high load)

[Debian Bug Tracking System]

Your message dated Mon, 7 Jun 2010 19:37:30 +0200
with message-id <20100607173730.ga24...@galadriel.inutil.org>
and subject line Re: Bug#583643: linux-image-2.6.34-1-686: iwlagn disassociate 
under high load
has caused the Debian Bug report #583643,
regarding linux-image-2.6.34-1-686: iwlagn disassociate under high load
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.)


-- 
583643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.34-1~experimental.1
Severity: normal

Dear Maintainers,

after upgrading to kernel 2.6.34-1~experimental.1 my iwlagn based
wirless lan gets unstable under higher/heavy load:

[226918.161883] wlan0: deauthenticated from 00:13:5f:ff:04:80 (Reason: 10)
[226918.176600] mac80211-phy0: failed to remove key (0, 00:13:5f:ff:04:80) from 
hardware (-22)
[226918.192593] cfg80211: Calling CRDA to update world regulatory domain
[226918.192637] cfg80211: Calling CRDA for country: EU
[226918.765130] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[226922.877709] wlan0: authenticate with 00:13:5f:ff:04:80 (try 1)
[226922.878811] wlan0: authenticated
[226922.878851] wlan0: associate with 00:13:5f:ff:04:80 (try 1)
[226922.880158] wlan0: RX AssocResp from 00:13:5f:ff:04:80 (capab=0x111 
status=0 aid=1)
[226922.880165] wlan0: associated
[226922.884919] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[228503.826349] wlan0: deauthenticated from 00:13:5f:ff:04:80 (Reason: 2)
[228503.844068] mac80211-phy0: failed to remove key (0, 00:13:5f:ff:04:80) from 
hardware (-22)
[228503.868282] cfg80211: Calling CRDA to update world regulatory domain
[228503.868336] cfg80211: Calling CRDA for country: EU
[228504.465770] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[228508.580218] wlan0: authenticate with 00:13:5f:ff:04:80 (try 1)
[228508.581246] wlan0: authenticated
[228508.581285] wlan0: associate with 00:13:5f:ff:04:80 (try 1)
[228508.582488] wlan0: RX AssocResp from 00:13:5f:ff:04:80 (capab=0x111 
status=0 aid=1)
[228508.582494] wlan0: associated

In my accesspoint (cisco 1131ag) logfile I can see:

May 28 2010 22:00:13.519 CEST: %DOT11-6-ASSOC: Interface Dot11Radio1, Station   
0016.eaef.2cea Associated KEY_MGMT[WPAv2 PSK]
May 28 2010 22:13:51.212 CEST: %DOT11-4-MAXRETRIES: Packet to client 
0016.eaef.2cea reached max retries, removing the client
May 28 2010 22:13:51.213 CEST: %DOT11-6-DISASSOC: Interface Dot11Radio1, 
Deauthenticating Station 0016.eaef.2cea Reason: Previous authentication no 
longer valid 
May 28 2010 22:13:51.215 CEST: %DOT11-4-MAXRETRIES: Packet to client 
0016.eaef.2cea reached max retries, removing the client
May 28 2010 22:13:57.856 CEST: %DOT11-6-ASSOC: Interface Dot11Radio1, Station   
0016.eaef.2cea Associated KEY_MGMT[WPAv2 PSK]
May 28 2010 22:40:18.691 CEST: %DOT11-4-MAXRETRIES: Packet to client 
0016.eaef.2cea reached max retries, removing the client
May 28 2010 22:40:18.695 CEST: %DOT11-6-DISASSOC: Interface Dot11Radio1, 
Deauthenticating Station 0016.eaef.2cea Reason: Previous authentication no 
longer valid 
May 28 2010 22:40:23.558 CEST: %DOT11-6-ASSOC: Interface Dot11Radio1, Station   
0016.eaef.2cea Associated KEY_MGMT[WPAv2 PSK]

With kernel linux-image-2.6.32-5-686 the wlan works prefectly.


-- Package-specific info:
** Version:
Linux version 2.6.34-1-686 (Debian 2.6.34-1~experimental.1) (m...@debian.org) 
(gcc version 4.3.4 (Debian 4.3.4-10) ) #1 SMP Thu May 20 12:14:21 UTC 2010

[5.036056] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 
in-tree:
[5.036059] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[5.036111] iwlagn :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[5.036119] iwlagn :03:00.0: setting latency timer to 64
[5.036155] iwlagn :03:00.0: Detected Intel Wireless WiFi Link 5300AGN 
REV=0x24
[5.272223] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 24 802.11a 
channels
[5.272337] iwlagn :03:00.0: irq 33 for MSI/MSI-X
[5.328754] iwlagn :03:00.0: firmware: requesting iwlwifi-5000-2.ucode
[6.440762] iwlagn :03:00.0: loaded firmware version 8.24.2.12

** Loaded modules:
Module  Size  Used by
des_generic15043  0 
cbc 1987  0 
i915  219529  2 
drm_kms_helper 18209  1 i915
drm   113797  4 i915,drm_kms_helper
i2c_algo_bit3541  1 i915
ip6table_filter  924  0 
ip6_tables  8736  1 ip6table_filter
xt_tcpudp   1675  1 
xt_owner 739  1 
iptable_na

Bug#584891: marked as done (naming and versioning of linux-image-2.6.32-5-686 and linux-image-2.6.32-trunk-686 confusing)

[Debian Bug Tracking System]

Your message dated Mon, 7 Jun 2010 19:35:16 +0200
with message-id <20100607173516.ga22...@galadriel.inutil.org>
and subject line Re: naming and versioning of linux-image-2.6.32-5-686 and 
linux-image-2.6.32-trunk-686 confusing
has caused the Debian Bug report #584891,
regarding naming and versioning of linux-image-2.6.32-5-686 and 
linux-image-2.6.32-trunk-686 confusing
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.)


-- 
584891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6
Severity: normal

due to some issues i checked today the installed kernel and was rather confused.
beside others i have installed
1) linux-image-2.6.32-trunk-686 
2) linux-image-2.6.32-5-686

dpkg says the versions are respectively
1) 2.6.32-5
2) 2.6.32-15

why does -trunk- have the version 2.6.32-5 while -2.6.32-5- has the version 
2.6.32-15?

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

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


--- End Message ---
--- Begin Message ---
On Mon, Jun 07, 2010 at 02:26:19PM +0200, arne wrote:
> Package: linux-image-2.6
> Severity: normal
> 
> due to some issues i checked today the installed kernel and was rather 
> confused.
> beside others i have installed
> 1) linux-image-2.6.32-trunk-686 
> 2) linux-image-2.6.32-5-686
> 
> dpkg says the versions are respectively
> 1) 2.6.32-5
> 2) 2.6.32-15
> 
> why does -trunk- have the version 2.6.32-5 while -2.6.32-5- has the version 
> 2.6.32-15?

The version with "trunk" in the version was accidentally uploaded some time
ago. You should use linux-image-2.6.32-5-686.

Cheers,
Moritz

--- End Message ---

Bug#576635: marked as done (Unable to access an encrypted root partition after a failed resume)

[Debian Bug Tracking System]

Your message dated Mon, 7 Jun 2010 19:32:18 +0200
with message-id <20100607173218.ga13...@galadriel.inutil.org>
and subject line Re: Seems to be resolved already
has caused the Debian Bug report #576635,
regarding Unable to access an encrypted root partition after a failed resume
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.)


-- 
576635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.32-3-amd64
Version: 2.6.32-9
Severity: important

  I set up unstable on a new laptop last week, using the same
configuration that I had on my last laptop: a single LVM physical
volume, encrypted (with the configuration created by the installer),
divided into two logical volumes, one for swap and one for the root
partition.  /boot, obviously, isn't on that partition.

  This morning, I tried to unhibernate the laptop for the second or
third time ever.  I entered my password and the screen blanked, but this
time I was unlucky and it didn't come back (I was starting to hope
hibernate would actually work ... oh well).  So after giving it a good
five minutes to do something, I finally just killed the power and
rebooted.

  After the reboot, the initrd wouldn't accept my encryption passphrase.
More specifically: it would unlock the partition, then announce that it
couldn't find a filesystem on the device.  I've booted the Squeeze live
CD on the laptop, and it appears that the initrd was correct.  I can
unlock the partition by hand, but pvdisplay insists that the unencrypted
device is not an LVM physical volume.  Nor does it appear to be a
filesystem of any normal sort.  I'm not sure what sort of horrible thing
happened to it at this point.

  I'm currently trying to hook the laptop in question up to the network
so I can grab an image of the block device for analysis, in the hope
that I can eventually figure out how to get my data off it (I'd like to
get a working system on the laptop soon so I can use it one the bus).
Obviously, I'd appreciate any suggestions you can give me with regard to
tracking down what happened and/or repairing the system.

  Daniel

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

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


--- End Message ---
--- Begin Message ---
Version: 2.6.32-15

On Sun, Jun 06, 2010 at 04:10:14PM +0300, Oren Held wrote:
> I'm using now linux-image-2.6.32-5-amd64 (v2.6.32-15), and I do not
> experience this bug anymore

Thanks, marking as fixed.

Cheers,
Moritz

--- End Message ---

Bug#582858: initramfs-tools: MODULES=dep fails when / is ubifs

[Martin Michlmayr]

* Martin Michlmayr  [2010-06-07 15:07]:
> The patch below works for me.  Can you try it?

I should mention that "works for me" means that the initramfs will be
generated without error.

I'm not claiming that you'll actually be able to boot from ubifs with
that ramdisk though.  For that, i-t needs to be taught to know what to
do about something like root=ubi0:rootfs.

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
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/20100607171049.ga31...@jirafa.cyrius.com

Bug#561203: threads and fork on machine with VIPT-WB cache

[dann frazier]

On Fri, Jun 04, 2010 at 12:44:55PM +0200, Thibaut VARENE wrote:
> On Fri, Jun 4, 2010 at 7:21 AM, dann frazier  wrote:
> > On Fri, Jun 04, 2010 at 10:03:07AM +0900, NIIBE Yutaka wrote:
> >> Modestas Vainius wrote:
>  Note that Debian's buildds run a UP kernel, so as soon as those fixes
>  go upstream we can pull them in. Thanks for all your work here!
> 
> >>>
> >>> Well, as long as this is unfixed or at least "common", I don't see how 
> >>> hppa
> >>> can be considered to be a release arch. Is that UP patch available 
> >>> somewhere?
> >>
> >> My case and my analysis talked about UP kernel, and John David Anglin
> >> made a patch:
> >>       http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561203#144
> >>
> >> After that, the discussion went to SMP cases.
> >>
> >> It would be better to evaluate the patch again, and make sure it works
> >> for UP case and fix failures of buildd, then apply for Linux in Debian
> >> (only) for HPPA.
> >>
> >> I know that the patch is not that ideal because it touches
> >> architecture independent part of Linux, but it is worth for Linux in
> >> Debian (or Linux for the HPPA machine of buildd, at least).
> >
> > I'm happy to test the patch if necessary to help push this change
> > upstream. However, we do need the change to go upstream before we can
> > include it in the Debian kernel.
> 
> Just for reference, I've summarized the test cases and related patches here:
> http://wiki.parisc-linux.org/TestCases

Cool - that is helpful. I've updated the kernel on peri/penalosa with
the various patches listed there that have gone upstream, but I'm not
seeing better results with any failing packages.

btw, I thought it would be useful to edit that page and tag each patch
with its status in Debian (in-official-kernel, installed-on-buildds,
etc), but the page appears to be immutable.

-- 
dann frazier




--
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/20100607171136.ga14...@lackof.org

Bug#584830: linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents suspend

[Ben Hutchings]

On Mon, Jun 07, 2010 at 09:20:07AM -0700, Sarah Sharp wrote:
> On Mon, Jun 07, 2010 at 02:18:26AM +0100, Ben Hutchings wrote:
> > On Mon, 2010-06-07 at 00:33 +0200, Thomas Jollans wrote:
> > > Package: linux-2.6
> > > Version: 2.6.32-15
> > > Severity: normal
> > > 
> > > My motherboard includes a USB 3.0 controller, handled by the xhci
> > > module. When the xhci module is loaded, the system fails to suspend with
> > > the following log messages:
> > > 
> > > [  458.601622] pm_op(): usb_dev_suspend+0x0/0xa [usbcore] returns -2
> > > [  458.601624] PM: Device usb2 failed to suspend: error -2
> > > 
> > > When I unload the xhci module, the system suspends just fine, without
> > > this message.
> > 
> > Sarah, any idea what's going on here?  Debian version 2.6.32-15 is
> > closely based on stable version 2.6.32.14.  I didn't see any later
> > changes to xhci that look related to PM.
> 
> The report is expected behavior, since the xHCI driver doesn't implement
> PCI and USB bus power management yet.

That seems like a big problem if the xhci driver is going to be auto-loaded
in desktops and laptops.

> The xHCI power management code is still under development.  I'm not sure
> if this code will be added to 2.6.32 stable, since it will add a lot of
> code to the driver.  The code may need to be backported.

I doubt it is a candidate for 2.6.32 stable, but I think we would want to
include it in Debian's kernel packages based on 2.6.32.

> Can you add this bug (or a link to the debian bug) to the kernel.org
> bugzilla?  I'm trying to get all my xHCI-related bug reports and feature
> requests there.
 
Will do.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
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/20100607165501.gn5...@decadent.org.uk

[bts-link] source package linux-2.6

[bts-link-upstream]

#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #580601 (http://bugs.debian.org/580601)
#  * https://bugs.freedesktop.org/show_bug.cgi?id=27589
#  * remote status changed: (?) -> NEW
usertags 580601 + status-NEW

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100607163416.25754.90881.btsl...@merkel.debian.org

Bug#584830: linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents suspend

[Sarah Sharp]

On Mon, Jun 07, 2010 at 02:18:26AM +0100, Ben Hutchings wrote:
> On Mon, 2010-06-07 at 00:33 +0200, Thomas Jollans wrote:
> > Package: linux-2.6
> > Version: 2.6.32-15
> > Severity: normal
> > 
> > My motherboard includes a USB 3.0 controller, handled by the xhci
> > module. When the xhci module is loaded, the system fails to suspend with
> > the following log messages:
> > 
> > [  458.601622] pm_op(): usb_dev_suspend+0x0/0xa [usbcore] returns -2
> > [  458.601624] PM: Device usb2 failed to suspend: error -2
> > 
> > When I unload the xhci module, the system suspends just fine, without
> > this message.
> 
> Sarah, any idea what's going on here?  Debian version 2.6.32-15 is
> closely based on stable version 2.6.32.14.  I didn't see any later
> changes to xhci that look related to PM.

The report is expected behavior, since the xHCI driver doesn't implement
PCI and USB bus power management yet.

The xHCI power management code is still under development.  I'm not sure
if this code will be added to 2.6.32 stable, since it will add a lot of
code to the driver.  The code may need to be backported.

Can you add this bug (or a link to the debian bug) to the kernel.org
bugzilla?  I'm trying to get all my xHCI-related bug reports and feature
requests there.

Sarah Sharp



-- 
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/20100607162007.gb8...@xanatos

Re: new lilo package maintainer? (was lilo removal in squeeze or please test grub2)

[Stephen Powell]

On Mon, 07 Jun 2010 10:33:52 -0400 (EDT), Holger Levsen wrote:
> 
> Hi Stephen,
>
> thanks for stepping up maintaining lilo in Debian! I hope you'll manage this 
> well.

Um, thanks; but I don't understand the reassignment of bug number 505609 to
package initramfs-tools.  If you read my previous posts to the bug log, it
is clear that this problem started with a change to the maintainer scripts
between Etch and Lenny.  Please read my posts again carefully.  Then consider
whether this is really a bug in initramfs-tools or a bug in the kernel 
maintainer
scripts.  initramfs-tools only gets involved when

   update-initramfs -u

is issued.  And it *does* invoke the boot loader under these conditions, if
"do_bootloader = yes" is present in /etc/kernel-img.conf and lilo is installed.
But for a kernel install or reconfigure, it is the responsibility of the
kernel maintainer scripts to invoke the bootloader.  See also, for example,
linux-image-2.6.26-2-s390.postinst, where zipl is assigned as the bootloader
on line 38.  This really is an "open and shut case", if only I can the kernel
people to actually look at it!  Please look at it!




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

Processed: Re: new lilo package maintainer? (was lilo removal in squeeze or please test grub2)

[Debian Bug Tracking System]

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

> reassign 505609 initramfs-tools
Bug #505609 [linux-2.6] Unbootable after kernel upgrade: Lilo can't load kernel
Bug reassigned from package 'linux-2.6' to 'initramfs-tools'.
> thanks
Stopping processing here.

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

Re: new lilo package maintainer? (was lilo removal in squeeze or please test grub2)

[Holger Levsen]

reassign 505609 initramfs-tools
thanks

Hi Stephen,

thanks for stepping up maintaining lilo in Debian! I hope you'll manage this 
well.

On Montag, 7. Juni 2010, Stephen Powell wrote:
> Perhaps I can offer a solution here.  Since William obviously doesn't wish
> to maintain this package any longer, I am willing to take over his
> responsibilities as a Debian package maintainer for lilo under two
> conditions:  (1) The kernel team fixes bug number 505609, and (2) Debian
> ceases its attempts to remove lilo from the distribution.

There is no attempt "from Debian". The current lilo maintainer thought this 
was the best option for lilo as he was going to orphan it and also because 
there was no upstream. If you step up to maintain lilo (and the codebase is 
and stays acceptable) and maintain lilo in Debian, removing lilo is moot.

> Keep in mind that I have never been a Debian package maintainer before.

The Debian New Maintainers Guide (ie at 
http://www.debian.org/doc/maint-guide/) shall be your friend, as well as 
lintian and debian-ment...@lists.debian.org as well as #debian-mentors on 
IRC.

Have fun! :-)

> As for whether or not lilo continues to be offered as an alternate boot
> loader by the Debian installer, that is entirely up to them.  

Fair enough. 


cheers,
Holger


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

Bug#582858: initramfs-tools: MODULES=dep fails when / is ubifs

[Martin Michlmayr]

tags 582858 + patch
thanks

* Daniel Kahn Gillmor  [2010-05-24 09:00]:
> 0 r...@moo:~# update-initramfs -k all -u
> update-initramfs: Generating /boot/initrd.img-2.6.32-5-kirkwood
> readlink: missing operand
> Try `readlink --help' for more information.
> stdin: Illegal seek
> mkinitramfs: for root  missing  /sys/block/ entry

The patch below works for me.  Can you try it?

--- a/hook-functions2010-06-07 15:03:22.0 +0100
+++ b/hook-functions2010-06-07 15:06:06.0 +0100
@@ -226,6 +226,14 @@
 
# findout root block device + fstype
eval "$(mount | awk '/\/dev\// {if ($3 == "/") {print "root=" $1 
"\nFSTYPE=" $5; exit}}')"
+
+   # handle ubifs and return since ubifs root is a char device but
+   # most of the commands below only work with block devices.
+   if [ "${FSTYPE}" = "ubifs" ]; then
+   manual_add_modules "${FSTYPE}"
+   return
+   fi
+
if [ "${root}" = "/dev/root" ] ; then
root="/dev/disk/by-uuid/"$(blkid -o value -s UUID ${root}) 
2>/dev/null
fi

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
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/20100607140726.gy4...@jirafa.cyrius.com

Processed: Re: Bug#582858: initramfs-tools: MODULES=dep fails when / is ubifs

[Debian Bug Tracking System]

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

> tags 582858 + patch
Bug #582858 [initramfs-tools] initramfs-tools: MODULES=dep fails when / is ubifs
Added tag(s) patch.
> thanks
Stopping processing here.

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

new lilo package maintainer? (was lilo removal in squeeze or please test grub2)

[Stephen Powell]

On Mon, 07 Jun 2010 03:22:46 -0400 (EDT), sean finney wrote:
> On Mon, Jun 07, 2010 at 01:44:05AM +0400, William Pitcock wrote:
>> Have fun.  When you have a release that actually has merit, it can be
>> reconsidered for inclusion in Debian.
>> 
>> In the meantime, the original plan continues.
> 
> actually, i don't think you have any say about what software can and
> can not be in debian, that is the sole privilege of ftp-master.  your
> options are (a) to claim you still want to maintain the package and
> continue to do so, or (b) ask for its removal by ftp-master.  given your
> comments here i think if you were to claim (a) there would be a decent
> case for someone to take to the tech-ctte.
> 
> ftp-master, if they're aware of this argument, may just say "why not
> orphan it instead?".  but regardless, if someone else is interested they 
> can just follow that removal with a new upload using their name as
> Maintainer, and then again it's up to ftp-master to accept or deny it.
> given that there may be an active upstream and maintainer, and the
> software is otherwise DFSG-compatible, i don't see why they would deny
> such a new upload.
> 
> of course, it would be a lot nicer if you could just hand over the reins
> of the current package to those who have been asking for them, to avoid
> some un-needed overhead...
>
>
> sean

Perhaps I can offer a solution here.  Since William obviously doesn't wish
to maintain this package any longer, I am willing to take over his
responsibilities as a Debian package maintainer for lilo under two
conditions:  (1) The kernel team fixes bug number 505609, and (2) Debian
ceases its attempts to remove lilo from the distribution.  What do you
say, William?  Do you have any objections?  Does anyone else have any
objections?  If so, speak now, or forever hold your peace.

Keep in mind that I have never been a Debian package maintainer before.
This will be my first package.  Please be patient with me as I "learn the
ropes", so to speak.

As for whether or not lilo continues to be offered as an alternate boot
loader by the Debian installer, that is entirely up to them.  I would
think that the path of least resistance would be to maintain the status
quo, but if they want to remove lilo from the Debian installer menu
that's their call, as far as I am concerned.  I just don't want to see
lilo removed from the distribution.

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

Bug#584906: nfs-kernel-server: nfs stop working suddenly

[Leopold Palomo]

Package: nfs-kernel-server
Version: 1:1.1.2-6lenny1
Severity: important

In this server nfs have been working perfectly one year and half. However,
lately we have have some serious issues with the nfs. Simply, the service 
stop and the _only_ way to repair the service is restarting the service.

In the logs the only reference that we have is:

orion mountd[4905]: couldn't open /var/lib/nfs/etab

It's a bit annoying because our little network depends on that service.

Regards,

Leo

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1   1.41.3-1 block device id library
ii  libc6   2.7-18lenny2 GNU C Library: Shared libraries
ii  libcomerr2  1.41.3-1 common error description library
ii  libgssglue1 0.1-2mechanism-switch gssapi library
ii  libkrb531.6.dfsg.4~beta1-5lenny4 MIT Kerberos runtime libraries
ii  libnfsidmap20.20-1   An nfs idmapping library
ii  librpcsecgss3   0.18-1   allows secure rpc communication us
ii  libwrap07.6.q-16 Wietse Venema's TCP wrappers libra
ii  lsb-base3.2-20   Linux Standard Base 3.2 init scrip
ii  nfs-common  1:1.1.2-6lenny1  NFS support files common to client
ii  ucf 3.0016   Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information



-- 
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/20100607133408.6326.22692.report...@orion.upc.es

Bug#584217: What about Debian Lenny?

[Brian 'morlenxus' Miculcy]

Yes, no more oops.

On Sat, Jun 05, 2010 at 09:17:17PM +0100, Ben Hutchings wrote:
> On Thu, 2010-06-03 at 15:10 +0200, Brian 'morlenxus' Miculcy wrote:
> > Installed linux-source-2.6.26, unpacked, applied the patch - no errors.
> > Don't see why it don't apply for you, i used the debian kernel source
> > package and applied above patch. Can you check that again?
> 
> Did you also build and test that it fixed the bug?
> 
> Ben.
> 
> -- 
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.





-- 
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/20100607131645.gb24...@omicron.homeip.net

Bug#584891: naming and versioning of linux-image-2.6.32-5-686 and linux-image-2.6.32-trunk-686 confusing

[arne]

Package: linux-image-2.6
Severity: normal

due to some issues i checked today the installed kernel and was rather confused.
beside others i have installed
1) linux-image-2.6.32-trunk-686 
2) linux-image-2.6.32-5-686

dpkg says the versions are respectively
1) 2.6.32-5
2) 2.6.32-15

why does -trunk- have the version 2.6.32-5 while -2.6.32-5- has the version 
2.6.32-15?

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

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100607122619.9473.79294.report...@mcrkoord.rrz.uni-hamburg.de

Processed: Re: Bug#584891: naming and versioning of linux-image-2.6.32-5-686 and linux-image-2.6.32-trunk-686 confusing

[Debian Bug Tracking System]

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

> reassign 584891 linux-2.6
Bug #584891 [linux-image-2.6] naming and versioning of linux-image-2.6.32-5-686 
and linux-image-2.6.32-trunk-686 confusing
Warning: Unknown package 'linux-image-2.6'
Bug reassigned from package 'linux-image-2.6' to 'linux-2.6'.
> --
Stopping processing here.

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

Bug#581554: ndiswrapper worked for RTL8188SU

[jidanni]

On Mon, Jun 07, 2010 at 08:24:47PM +1000, Geoff Simmons wrote:
> [Please do not CC 581...@bugs.debian.org in any reply, as this does not
> concern firmware for the in-tree rtl8192su driver]
I must, just in case there are other Jeffs out there stuck in the same boat... 
as I
have a workaround!:

OK Jeff my man, the ndiswrapper stuff works! Here are the already extracted
INF files that I found on my Windows disk.
http://filebin.ca/duhdb/RTL8192suWindowsDrivers.cpio.gz
All you have to do is follow the http://wiki.debian.org/NdisWrapper
instructions, and remember to do
# echo blacklist r8192s_usb >> /etc/modprobe.d/blacklist.conf
Worked for my
0bda:8171 Realtek Semiconductor Corp. RTL8188SU 802.11n WLAN Adapter
(It worked even on the same machine where a Sparklan ndiswrapper driver
caused a kernel Oops.)

> 32-bit and 64-bit
> Windows XP drivers for use with NDISwrapper are available within the
> RTL8188_8191_8192_SU_Drv_XP_1084.26.0310.2010_Win7_1086.12.0310.2010_UI_1.00.0150.L/88_91_92_SU_Driver/{WinXP,WinX64}
> directories in the referenced RTL8188SU_InstallPackage.zip archive.

OK that is great to know too! I would have never thought of it!



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100607120657.ga12...@ps11007.dreamhostps.com

Processed: reassign 584881 to linux-2.6

[Debian Bug Tracking System]

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

> reassign 584881 linux-2.6 2.6.26-21lenny4
Bug #584881 [linux-image-2.6.26-2-686-bigmem] Lockups under heavy disk IO; md 
(RAID) resync/check implicated
Bug reassigned from package 'linux-image-2.6.26-2-686-bigmem' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-21lenny4.
Bug #584881 [linux-2.6] Lockups under heavy disk IO; md (RAID) resync/check 
implicated
There is no source info for the package 'linux-2.6' at version 
'2.6.26-21lenny4' with architecture ''
Unable to make a source version for version '2.6.26-21lenny4'
Bug Marked as found in versions 2.6.26-21lenny4.
> thanks
Stopping processing here.

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

Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated

[Ian Jackson]

Package: linux-image-2.6.26-2-686-bigmem
Version: 2.6.26-21lenny4

I keep getting soft lockups; the symptoms appear to be that user
processes become deadlocked when they try to access the disk, but the
kernel doesn't notice that anything is wrong.

It appears that the lockups happen when:
 (a) my software (mdadm) RAID mirror is resyncing or checking
 (b) some other program does heavy disk IO

I'm currently trying to work around the problem by disabling the
system's backups (which are a prime trigger in category (b)) until the
post-crash mirror resync is complete, combined with setting the sysctl
dev.raid.speed_limit_max to 1000.  Just disabling the backups wasn't
sufficient because, it seems, various recovery tasks in the most
recent crash are sufficient to trigger the bug.

I observe that the message from the md driver, and the presence of the
sysctls dev.raid.speed_limit_{min,max}, suggest that the md driver is
using a fundamentally incorrect algorithm which depends on guessing
the available IO bandwidth.


Actual hard data:

* chiark locked up at 0355 on the 2nd of May.  It did so shortly after
  the backups start.  chiark's backups are done with LVM snapshots and
  rsync.  I don't any more have information about exactly at what
  stage the backups were at.

* chiark locked up again at 0355 on Sunday morning the 6th of June.
  In this case I was able to see that the system had successfully
  created and mounted the LVM snapshot as the rsync process on the
  backup master system was still present.

* Note that both these two crashes happened on the 1st Sunday of the
  month.  Investigating the kernel logs for the 2nd crash show this:
Jun  6 00:57:01 chiark kernel: [3250794.079478] md: data-check of RAID 
array md127
Jun  6 00:57:01 chiark kernel: [3250794.079479] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
Jun  6 00:57:01 chiark kernel: [3250794.079479] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for data-check.
Jun  6 00:57:01 chiark kernel: [3250794.079479] md: using 128k window, over 
a total of 97980 blocks.
  However there is no sign of it completing.

* Shortly after I power cycled the system to get it back up, it locked
  up again.  At that point, the RAID was doing a post-crash resync,
  and the crash happened at the point where the backup master
  attempted to start on the next partition.

* Some research dug up some reports of first-Sunday-of-the-month
  crashes associated with RAID integrity checks.[1] So I tried setting
  the max IO bandwidth sysctl to the lowest reasonable value (by hand)
  and left the system running.  However, it locked up again as the
  backups started.

* I power cycled the machine again and disabled the backups and made
  sure they were truly stopped.  However chiark locked up again mere
  minutes after coming back up.

* I have now power cycled chiark once more and this time I set the
  max IO bandwidth sysctl.  So far it seems to have stayed up for
  about half an hour.

If nothing more goes wrong I intend to leave the backups disabled
until the RAID finishes its resync, which we can expect to be some
time on Wednesday night.


chiark is running LVM-on-MD-on-LVM.  So the two "disks" which form the
mirror which is resyncing are actually LVM LVs, and that mirror is
itself an LVM PV.  The underlying hardware is a Dell R210 with two
WD SATA disks (WD7500AYPS-0).


[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/212684
  seems relevant for example.


Ian.


lvs:

  LVVG   Attr   LSize   Origin Snap%  Move Log 
Copy%  Convert
  mirror-base   chiark-early-a   -wi-ao 400.00G
  stripe-base   chiark-early-a   -wi-ao  52.00G
  swap  chiark-early-a   -wi-ao   4.00G
  mirror-base   chiark-early-b   -wi-ao 400.00G
  stripe-base   chiark-early-b   -wi-ao  52.00G
  swap  chiark-early-b   -wi-ao   4.00G
  lv-quicksand  vg-chiark-stripe -wi-ao  40.00G
  twomack-relations vg-chiark-stripe -wi-ao  60.00G
  lv-logvg-main  -wi-ao   3.00G
  lv-mail   vg-main  -wi-ao   3.00G
  lv-news   vg-main  -wi-ao  15.94G
  lv-root   vg-main  -wi-ao   1.00G
  lv-u  vg-main  -wi-ao   9.75G
  lv-u2 vg-main  -wi-ao  12.25G
  lv-u3 vg-main  -wi-ao   7.06G
  lv-usrvg-main  -wi-ao   4.12G
  lv-varvg-main  -wi-ao   5.94G
  lv-volt   vg-main  -wi-ao  77.44G


pvs:

  PVVG   Fmt  Attr PSize   PFree 
  /dev/md_chiark-mirror vg-main  lvm2 a-   211.94G 72.44G
  /dev/md_chiark-stripe vg-chiark-stripe lvm2 a-   103.94G  3.94G
  /dev/sdb2 chiark-early-a   lvm2 a-   464.00G  8.00G
  /dev/sdc2 chiark-early-b   lvm2 a-   464.00G  8.00G


/proc/mdstat:

Personalities : [raid0] [raid1] 
md126 : active raid0 dm-2[0] dm-5[1]
  1090517

Bug#581554: can't even extract the .cab file

[jidanni]

Looks like we are s*it out of luck,
$ apt-cache search installshield
orange - extracts CAB files from self-extracting installers
unshield - extracts CAB files from InstallShield installers
can't even deal with the data2.cab file in the windows drivers in
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8192SU
Can't even extract the file. So how do you think we will get anywhere
with ndiswrapper?



-- 
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/8739wz89ey@jidanni.org

Bug#581554: Firmware

[jidanni]

It looks like we will have to go the ndiswrappers route.



-- 
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/87ocfn8c41@jidanni.org

Bug#581554: Firmware

[jt]

I am having this problem too.  I am trying to get wireless to work on  
a Samsung N220.  I am using 64bit Squeeze with a 2.6.32 kernel with  
the RTL8192E staging driver compiled in.  I have tried all the  
firmware versions I can find and none of them work.  The latest  
version that I can find is rtl8192e_linux_2.6.0014.  According to the  
release note for this firmware it is for “Kernel version =  
2.6.28/2.6.30/2.6.31”, i.e. not 2.6.32.  As far as I can tell in fact  
the actual firmware in all versions up to now is identical.  I have  
tried emailing Realtek for drivers but I have had no response.




--
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/20100607082216.aswfknc2io4cs8g4-qc...@webmail.spamcop.net