Bug#638068: busybox binary in initrd.img is incorrectly overwritten by klibc hook

2012-05-28 Thread Adam D. Barratt 

On 15.01.2012 20:16, Émeric Maschino wrote:

Le 15 janvier 2012 19:08, maximilian attems  a écrit :
Nice detective work.  So the next question is: why does klibc-utils 
on

ia64 provide /usr/lib/klibc/bin/sh instead of sh.shared like other
architectures?


#439181  ia64 works only static


Thanks for pointing this out.


I'd also be interested to hear how /usr/lib/klibc/bin/sh behaves in
general: e.g., could you try

      ldd /usr/lib/klibc/bin/sh
      /usr/lib/klibc/bin/sh -c 'echo hi'

?


/me too.


Okay, okay, your wish is my command ;-)

emeric@longspeak:~$ ldd /usr/lib/klibc/bin/sh
   not a dynamic executable


The above seems to be the most recent message in the bug log, other 
than a "me too" a few weeks ago.  Has there been any progress towards 
getting this resolved?  Unless I'm missing something, it sounds like a 
fairly large blocker to using Debian on ia64.


Regards,

Adam



--
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/01feac3ad06b8150c9d541461d7d3...@mail.adsl.funky-badger.org

[bts-link] source package src:linux-2.6

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

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

# remote status report for #656062 (http://bugs.debian.org/656062)
# Bug title: pm-utils: pm-suspend does not enter suspend and hangs system on 
Asus U35JC
#  * http://bugzilla.kernel.org/show_bug.cgi?id=37632
#  * remote status changed: (?) -> CLOSED
#  * remote resolution changed: (?) -> CODE-FIX
usertags 656062 + status-CLOSED resolution-CODE-FIX

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/20120528164258.2066.66268.btsl...@busoni.debian.org

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-28 Thread Arief M Utama 
On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder  wrote:

> Arief M Utama wrote:
>
> > This is the output from lsusb:
> >
> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> > Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> > Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp.
> > Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp.
> > Bus 004 Device 004: ID 064e:e258 Suyin Corp.
> >
> > More details from lsusb output on the bluetooth device attached.
>
> Thanks.
>
> > I can confirm that patch number 4
> > [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working
> on
> > my laptop. Haven't tested other patches, although I can report that only
> > patches 1, 4, 6 and 8 that applied successfully.
>
> Ok.  What kernel are you applying these to?  Could you attach "dmesg"
> output from the patched kernel?
>
>
The source package was called this:  linux-2.6-3.2.18, the image is this:
linux-image-3.2.0-2-amd64.

dmesg output attached here.

I was hoping to get a quick sanity check that the other patches at
> least didn't cause the kernel to explode :), but answers to more
> important questions about them would indeed require info from people
> with the matching hardware.  Will look around and then submit these
> for inclusion in 3.2.y from kernel.org if they seem to be well tested.
>
>
I can test the other patches if needed, just to make sure about it :-)



> Hope that helps,
> Jonathan
>


All the best.
-arief

Bug#638068: unbootable initrds are RC

2012-05-28 Thread Andreas Barth 
severity 638068 serious
thanks

Hi,

AFAICS, we cannot release with an initramfs that generates unbootable
initrds on one of our supported architectures. Setting this bug to
serious for this reason.


Andi



-- 
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/20120528184248.gj13...@mails.so.argh.org

Processed: unbootable initrds are RC

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

> severity 638068 serious
Bug #638068 [initramfs-tools] [bisected] initramfs-tools generates unbootable 
initrd.img on IA-64 platform (Itanium)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-28 Thread Jonathan Nieder 
Arief M Utama wrote:
> On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder  wrote:

>>  Will look around and then submit these
>> for inclusion in 3.2.y from kernel.org if they seem to be well tested.
>
> I can test the other patches if needed, just to make sure about it :-)

Yeah, no need.

For the future: it now occurs to me that you might have been applying
the patches with the test-patches script one at a time, which would
explain why some of them didn't apply.  The command takes a list of
patches as arguments to apply in order.  But it's not important: I was
asking to test them together just as a "while at it" extra in the same
boot.  I don't think it's worth the time to compile and boot yet
again. :)

I need to finish gathering a list of people who tested the driver
using hardware with the other USB ids and then I'll send the patches
as a batch to stable@.  Thanks for your help and sorry to be so slow
at this.

Sincerely,
Jonathan



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

Bug#674565: Bluetooth activation failed (btusb module)

2012-05-28 Thread Jonathan Nieder 
Arief M Utama wrote:

> Hit enter too quick, forgot about the dmesg attachment. Here it is.

Wonderful, thanks.  Just for fun, let's parse some unrelated messages.

> [0.00] DMI: Hewlett-Packard HP ENVY 15 NOTEBOOK PC/1688, BIOS F.04 
> 11/12/2011
[...]
> [2.529762] \_SB_.PCI0:_OSC invalid UUID
> [2.529763] _OSC request data:1 8 1f 
[...]
> [2.573816] \_SB_.PCI0:_OSC invalid UUID
> [2.573817] _OSC request data:1 1f 1f 
> [2.573820]  pci:00: Requesting ACPI _OSC control (0x1d)
> [2.573865] \_SB_.PCI0:_OSC invalid UUID
> [2.573866] _OSC request data:1 0 1d 
> [2.573869]  pci:00: ACPI _OSC request failed (AE_ERROR), returned 
> control mask: 0x1d
> [2.573871] ACPI _OSC control for PCIe not granted, disabling ASPM

That's , perhaps.
Could be a bug in the BIOS or an ACPI bug in the kernel, or a
misleading message.

[...]
> [   10.250808] rts_pstor: module is from the staging directory, the quality 
> is unknown, you have been warned.
> [   10.251583] Initializing Realtek PCIE storage driver...
[...]
> [   11.452078] rts_pstor: device scan complete
> [   11.452316] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S.   1.00 
> PQ: 0 ANSI: 0 CCS
> [   11.452417] Bad LUN (0:1)
> [   11.452607] Bad target number (1:0)
> [   11.452746] Bad target number (2:0)
> [   11.452878] Bad target number (3:0)
> [   11.452998] Bad target number (4:0)
> [   11.453141] Bad target number (5:0)
> [   11.453257] Bad target number (6:0)
> [   11.453353] Bad target number (7:0)
> [   11.453724] sd 6:0:0:0: [sdb] Attached SCSI removable disk

.  I get the impression that Realtek
has abandoned this driver and is working on a new version (not
published yet) that follows a different approach.

[...]
> [   77.448484] atkbd serio0: Unknown key pressed (translated set 2, code 0xab 
> on isa0060/serio0).
> [   77.448494] atkbd serio0: Use 'setkeycodes e02b ' to make it 
> known.

If this is the brightness key, sounds like
.  There is a related upstream
report at .

Thanks,
Jonathan



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

Bug#656062: Asus suspend hang (USB-related) - fixed?

2012-05-28 Thread Ben Hutchings 
This is supposed to have been fixed in version 3.2.17-1.  Has it?

Ben.

-- 
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.


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

Bug#609846: Toshiba Satellite battery not recognized by acpi

2012-05-28 Thread Taylor Brown 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The bug still exists (no output from `acpi -b`, no gui battery status)
in version '2.6.32-45' of squeeze kernel package
'linux-image-2.6.32-5-amd64'.

Passing 'acpi=copy_dsdt' makes no difference.

Battery status works after overriding dsdt, recompiling kernel
following these steps:
http://nearlyalaugh.com/2011/08/override-dsdt/


Taylor

On 05/06/2012 08:07 PM, Jonathan Nieder wrote:
> tags 609846 + moreinfo quit
> 
> Hi again,
> 
> Jonathan Nieder wrote:
> 
>> found 609846 linux-2.6/2.6.32-29
> [...]
>> Sounds like .  Does passing 
>> acpi=copy_dsdt on the kernel command line help?
> 
> Ping.  Do you still have access to this hardware?  If so, do kernel
> versions >= 2.6.32-41 still reproduce the bug?
> 
> In suspense, Jonathan
> 
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPxFn1AAoJED72CDEetIMvEEkIAOPjcJoxtJZW+MuDsdCZqYlZ
5PY7INZcix3+myZnX5lWjbYHaUMVgPjNrj5lVC/yyOMnNtuemBjGZD5c/iAkxEHj
tu6y4tLVCJ6D35Gvhf8wKM8L+QgaAZUJeo38tuEOPy1gAAZsxv/+RJ6PjPfLZIwy
sdyYdv+cwpjGqXMtFMihiA1aQcJrm1w8sf1b680s/zj6aSoa8zVTteXzN6DC5VcG
FRyrSukoU8qUYueQx0P0PPsXmjBiHmcPgtqY8joxKQDtLrPEYzslg0XQFkyQcGRj
xVOtfBRtRr+Xp3lWMFIJbj8TlGgDib16FWuRZBDlS3T3fKxvnPHHMJoK03xi4W0=
=mlvE
-END PGP SIGNATURE-



-- 
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/4fc459fc.1040...@nearlyalaugh.com

Bug#609846: Toshiba Satellite battery not recognized by acpi

2012-05-28 Thread Jonathan Nieder 
severity 609846 important
tags 609846 + upstream
forwarded 609846 https://bugzilla.kernel.org/show_bug.cgi?id=15707
quit

Taylor Brown wrote:

> The bug still exists (no output from `acpi -b`, no gui battery status)
> in version '2.6.32-45' of squeeze kernel package
> 'linux-image-2.6.32-5-amd64'.
>
> Passing 'acpi=copy_dsdt' makes no difference.

Thanks for the update.

> Battery status works after overriding dsdt, recompiling kernel
> following these steps:
> http://nearlyalaugh.com/2011/08/override-dsdt/

Oh, nice!  Please test a 3.x.y kernel from sid, squeeze-backports, or
experimental.  The only packages from outside squeeze that should be
needed for this test are the kernel image itself, linux-base, and
initramfs-tools.

If we're lucky then v3.0-rc1~12^2~3 (ACPICA: Execute an orphan _REG
method under the EC device, 2011-04-13) fixed it.

Hope that helps,
Jonathan



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

Processed: Re: Toshiba Satellite battery not recognized by acpi

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

> severity 609846 important
Bug #609846 [linux-2.6] Toshiba Satellite battery not recognized by acpi
Severity set to 'important' from 'normal'
> tags 609846 + upstream
Bug #609846 [linux-2.6] Toshiba Satellite battery not recognized by acpi
Added tag(s) upstream.
> forwarded 609846 https://bugzilla.kernel.org/show_bug.cgi?id=15707
Bug #609846 [linux-2.6] Toshiba Satellite battery not recognized by acpi
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=15707'.
> quit
Stopping processing here.

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

Bug#656062: Asus suspend hang (USB-related) - fixed?

2012-05-28 Thread Jonathan Nieder 
Ben Hutchings wrote:

> This is supposed to have been fixed in version 3.2.17-1.  Has it?

If I understood correctly, I think it was fixed at the cost of not
being able to wake up with a keypress from suspend.

 commit 46730c8667e7
 Author: Oleksij Rempel 
 Date:   Mon May 14 22:25:58 2012 +0200

 ACPI / PCI / PM: Make _SxD/_SxW check follow ACPI 4.0a spec

 This patch makes _SxD/_SxW check follow the ACPI 4.0a specification
 more closely and fixes suspend bug found on ASUS Zenbook UX31E.

 Some OEM use _SxD fields to blacklist broken device Dx states, so
 if _SxD/_SxW return values are checked before suspend as appropriate,
 some nasty suspend/resume issues may be avoided.

 References: https://bugzilla.kernel.org/show_bug.cgi?id=42728
 Signed-off-by: Oleksij Rempel 
 Acked-by: Bjorn Helgaas 
 Cc: sta...@vger.kernel.org
 Signed-off-by: Rafael J. Wysocki 

from linux-next is supposed to follow a better approach that would
avoid that downside and work on more machines.  There is a patch
attached to [1] that has been tested and will probably replace it.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=42728



-- 
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/20120529055112.GB14697@burratino

Bug#609846: Toshiba Satellite battery not recognized by acpi

2012-05-28 Thread Taylor Brown 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

No battery status in kernel version '3.2.17-1~bpo60+1'
(squeeze-backports package 'linux-image-3.2.0-0.bpo.2-amd64') or
'3.2.18-1' (sid package 'linux-image-3.2.0-2-amd64').


Taylor

On 05/28/2012 10:43 PM, Jonathan Nieder wrote:
> severity 609846 important tags 609846 + upstream forwarded 609846
> https://bugzilla.kernel.org/show_bug.cgi?id=15707 quit
> 
> Taylor Brown wrote:
> 
>> The bug still exists (no output from `acpi -b`, no gui battery
>> status) in version '2.6.32-45' of squeeze kernel package 
>> 'linux-image-2.6.32-5-amd64'.
>> 
>> Passing 'acpi=copy_dsdt' makes no difference.
> 
> Thanks for the update.
> 
>> Battery status works after overriding dsdt, recompiling kernel 
>> following these steps: 
>> http://nearlyalaugh.com/2011/08/override-dsdt/
> 
> Oh, nice!  Please test a 3.x.y kernel from sid, squeeze-backports,
> or experimental.  The only packages from outside squeeze that
> should be needed for this test are the kernel image itself,
> linux-base, and initramfs-tools.
> 
> If we're lucky then v3.0-rc1~12^2~3 (ACPICA: Execute an orphan
> _REG method under the EC device, 2011-04-13) fixed it.
> 
> Hope that helps, Jonathan
> 
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPxG++AAoJED72CDEetIMvjzwIAIqvb7TbQsklwVJD+r9BcTd7
K9wn8080NG09ekHQmbzbGze85l4vMeWfJar+BrK9pXg3Jcu+EGtdtyYPWor0z8qP
Vz3r0wcwrBgMsnX+C009YY39sUkPrIywyvjaR0EcVm/QxMv5p3EHGmd/UUBi8S6X
f4Jjd56CI61o6ga8NzSSlpPIMM28OIX3Fnhb9MfmWRhoXi9FDGtqAbPHrP8zfvMA
DPTzgagBhSsxY1CyrsekGpHZyUNockozzNZOjwYSr2d5bs5c4LrIDGEQXKHXLQsV
tyrFB8yoy0VNpGBdG7suj0EKvMb8WeTr30WcGUfXGLElCyoqsA310Htt++huB3I=
=68py
-END PGP SIGNATURE-



-- 
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/4fc46fc2.8010...@nearlyalaugh.com