Processed: Re: Processed: asdf

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 291039 kernel-source-2.6.10
Bug#291039: kernel-patch-debian-2.6.10: bashism in apply file
Warning: Unknown package 'kernel-patch-source-2.6.10'
Bug reassigned from package `kernel-patch-source-2.6.10' to 
`kernel-source-2.6.10'.

> reassign 291107 kernel-source-2.6.9
Bug#291107: kernel-patch-debian-2.6.9: bashism in apply/debian file
Warning: Unknown package 'kernel-patch-source-2.6.9'
Bug reassigned from package `kernel-patch-source-2.6.9' to 
`kernel-source-2.6.9'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#290013: marked as done (kernel-source-2.4.27: apm problem on IBM Thinkpad T40p: no suspend after closing the lid)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#290013: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 12 Jan 2005 11:28:44 +
>From [EMAIL PROTECTED] Wed Jan 12 03:28:44 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mrelay3.uni-hannover.de [130.75.2.41] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cogg8-0008J9-00; Wed, 12 Jan 2005 03:28:44 -0800
Received: from server1.learninglab.uni-hannover.de (server1.l3s.uni-hannover.de 
[130.75.87.1])
by mrelay3.uni-hannover.de (8.12.10/8.12.10) with ESMTP id 
j0CBSZ9e023809
for <[EMAIL PROTECTED]>; Wed, 12 Jan 2005 12:28:35 +0100 (MET)
Received: from server1.learninglab.uni-hannover.de 
(server1.learninglab.uni-hannover.de [130.75.87.1])
by server1.learninglab.uni-hannover.de (Postfix) with SMTP id 
94FE41D64005
for <[EMAIL PROTECTED]>; Wed, 12 Jan 2005 12:28:35 +0100 (CET)
Received: from diederich by localhost.localdomain with local (Exim 4.34)
id 1Cogfy-Th-RD; Wed, 12 Jan 2005 12:28:34 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Joerg Diederich <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.4.27: apm problem on IBM Thinkpad T40p: no suspend 
after
 closing the lid
X-Mailer: reportbug 3.2
Date: Wed, 12 Jan 2005 12:28:34 +0100
Message-Id: <[EMAIL PROTECTED]>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 
(mrelay3.uni-hannover.de [130.75.2.41]); Wed, 12 Jan 2005 12:28:35 +0100 (MET)
X-Scanned-By: MIMEDefang 2.42
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-source-2.4.27
Version: 2.4.27-6
Severity: normal

Hi kernel maintainers,

Starting from kernel-source-2.4.27-6, my Thinkpad T40p does not go into
suspend mode when I close the lid (even though I use the 'standard'
kernel-config provided with kernel-image-2.4.27-2, where ACPI and APM
support is compiled in, ACPI is not used according to the output of
dmesg:

ACPI: Subsystem revision 20040326
ACPI: Interpreter disabled.
[...]
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)

)

It worked perfectly with the original debian kernel
kernel-image-2.4.27-2 (which is based on kernel-source-2.4.27-5 according
to the changelog). Now I have compiled my own kernel from
kernel-source-2.4.27-6 in two versions:
- including the patch 103-enter-acpi-early.diff (so the original source
  package)
- reverting the patch 103-enter-acpi-early.diff

in the first case, suspend does not work when I close the lid, in the
second case it does. And I do not use any extra kernel modules such as
the thinkpad modules.

For me, it's perfectly possible to work with a self-compiled kernel, but for
this IBM the debian-provided kernel worked out-of-the-box up to version
-2, which is pretty convenient for upgrading to newer version. That's
why I want to report this bug and hope that it can be fixed so that I
can go back to using the debian kernels without recompiling...

Thanks and best regards,

/Joerg

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.27
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kernel-source-2.4.27 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-1A high-quality block-sorting file 
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  fileutils 5.2.1-2The GNU file management utilities 

-- no debconf information

---
Received: (at 290013-close) by bugs.debian.org; 21 Jan 2005 04:23:02 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqK6-0001De-00; Thu, 20 Jan 2005 20:23:02 -0800
Received: from katie by newraff.debian.org with local (Ex

Bug#289517: marked as done (kernel-image-2.4.27-1-686: startup errors)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#289517: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 9 Jan 2005 15:08:46 +
>From [EMAIL PROTECTED] Sun Jan 09 07:08:46 2005
Return-path: <[EMAIL PROTECTED]>
Received: from master.debian.org [146.82.138.7] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CnegQ-0003vn-00; Sun, 09 Jan 2005 07:08:46 -0800
Received: from roulaize.skamp-zo.org ([127.0.0.1]) [82.67.109.46] 
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CnegP-0006ni-00; Sun, 09 Jan 2005 09:08:45 -0600
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Arno <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-image-2.4.27-1-686: startup errors
X-Mailer: reportbug 3.2
Date: Sun, 09 Jan 2005 16:08:44 +0100
X-Debbugs-Cc: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.2 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
FROM_HAS_MIXED_NUMS,HAS_PACKAGE,OUR_MTA_MSGID,UPPERCASE_25_50,
X_DEBBUGS_CC autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-image-2.4.27-1-686
Version: 2.4.27-6
Severity: normal


Hello,

At the start of the computer, i've got some errors (that i haven't got with a 
2.6 kernel).
Here is a copy of the problem form /var/log/kernel

Jan  9 15:57:56 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 
0.5
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.MDET] (Node cfbc69c0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0._CRS] (Node cfbc6a80), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-0154: *** Error: Method execution 
failed [\_SB_.PCI0._CRS] (Node cfbc6a80), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: shpchp: acpi_shpchprm:\_SB_.PCI0 _CRS fail=0x6
Jan  9 15:57:56 localhost kernel: shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate 
_CRS fail=0x6
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c130bc20), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-0154: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c130bc20), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.PS2K._STA] (Node c130bd00), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-0154: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.PS2K._STA] (Node c130bd00), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.ENFG] (Node c13093a0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.LPT_._STA] (Node c13098e0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-0154: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.LPT_._STA] (Node c13098e0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.ENFG] (Node c13093a0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.ECP_._STA] (Node c13099c0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-0154: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.ECP_._STA] (Node c13099c0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.ENFG] (Node c13093a0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.GAME._STA] (Node c1309aa0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-0154: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.GAME._STA] (Node c1309aa0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.ENFG] (Node c13093a0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACPI-1133: *** Error: Method execution 
failed [\_SB_.PCI0.SBRG.GSTA] (Node c1309ce0), AE_NOT_EXIST
Jan  9 15:57:56 localhost kernel: ACP

Bug#289202: marked as done (CAN-2004-1235: uselib() privilege escalation)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#289202: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 7 Jan 2005 14:41:07 +
>From [EMAIL PROTECTED] Fri Jan 07 06:41:07 2005
Return-path: <[EMAIL PROTECTED]>
Received: from inutil.org (vserver151.vserver151.serverflex.de) 
[193.22.164.111] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CmvIZ-0007RW-00; Fri, 07 Jan 2005 06:41:07 -0800
Received: from wlan-client-025.informatik.uni-bremen.de ([134.102.116.26] 
helo=localhost.localdomain)
by vserver151.vserver151.serverflex.de with asmtp 
(TLS-1.0:RSA_ARCFOUR_SHA:16)
(Exim 4.34)
id 1CmvIX-0007Sb-Lt
for [EMAIL PROTECTED]; Fri, 07 Jan 2005 15:41:05 +0100
Received: from jmm by localhost.localdomain with local (Exim 4.34)
id 1CmvIU-0001lw-3s; Fri, 07 Jan 2005 15:41:02 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Moritz Muehlenhoff <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: CAN-2004-1235: uselib() privilege escalation
X-Mailer: reportbug 3.5
Date: Fri, 07 Jan 2005 15:41:01 +0100
Message-Id: <[EMAIL PROTECTED]>
X-SA-Exim-Connect-IP: 134.102.116.26
X-SA-Exim-Mail-From: [EMAIL PROTECTED]
X-SA-Exim-Scanned: No (on vserver151.vserver151.serverflex.de); SAEximRunCond 
expanded to false
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_DSBL autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-source-2.6.8
Version: 2.6.8
Severity: grave
Tags: security
Justification: user security hole

Paul Starzetz from iSec Security Research has discovered a local root exploit in
the Linux kernel:
> Locally exploitable  flaws have  been  found in  the  Linux
> binary format loaders' uselib() functions that allow  local
> users to gain root privileges.

The full advisory text: http://isec.pl/vulnerabilities/isec-0021-uselib.txt

I haven't found a patch for 2.6 yet, a patch for 2.4 is available in
the 2.4 Bitkeeper branch.

Cheers,
Moritz

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-386
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages kernel-source-2.6.8 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-2high-quality block-sorting file co
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

---
Received: (at 289202-close) by bugs.debian.org; 21 Jan 2005 04:23:19 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:19 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqKN-0001TX-00; Thu, 20 Jan 2005 20:23:19 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027k-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#289202: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 7

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in the latest version of
kernel-source-2.4.27, which is due to be installed in the Debian FTP archive:

kernel-doc-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-8_all.deb
kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  to 
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-8_all.deb
kernel-source-2.4.27_2.4.27-8.diff.gz
  to pool/main/k/kernel-source-2.4.27/kerne

Bug#288272: marked as done (kernel-image-2.4.27-1-686: Very slow on Tecra 8100)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288272: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 2 Jan 2005 19:50:20 +
>From [EMAIL PROTECTED] Sun Jan 02 11:50:20 2005
Return-path: <[EMAIL PROTECTED]>
Received: from cpe-65-172-238-145.sanbrunocable.com (montara) [65.172.238.145] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1ClBk3-0003MR-00; Sun, 02 Jan 2005 11:50:19 -0800
Received: from laurent by montara with local (Exim 3.36 #1 (Debian))
id 1ClBkS-IV-00; Sun, 02 Jan 2005 11:50:44 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Laurent Charriere <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-image-2.4.27-1-686: Very slow on Tecra 8100
X-Mailer: reportbug 3.2
Date: Sun, 02 Jan 2005 11:50:44 -0800
Message-Id: <[EMAIL PROTECTED]>
Sender: Laurent Charriere <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-4.3 required=4.0 tests=BAYES_00,FORGED_YAHOO_RCVD,
HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-image-2.4.27-1-686
Version: 2.4.27-6
Severity: important

Upgrading the kernel to 2.4.27-1-686 makes my Toshiba Tecra 8100  
very slow (think: running with a Pentium 75), to a point that it is 
almost unusable. 
Reverting to 2.4.26 fixes the problem.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-image-2.4.27-1-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  fileutils 5.2.1-2The GNU file management utilities 
ii  initrd-tools  0.1.74 tools to create initrd image for p
ii  modutils  2.4.26-1.2 Linux module utilities

-- no debconf information

---
Received: (at 288272-close) by bugs.debian.org; 21 Jan 2005 04:23:05 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqK8-0001Gs-00; Thu, 20 Jan 2005 20:23:04 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027e-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#288272: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 4

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in the latest version of
kernel-source-2.4.27, which is due to be installed in the Debian FTP archive:

kernel-doc-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-8_all.deb
kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  to 
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-8_all.deb
kernel-source-2.4.27_2.4.27-8.diff.gz
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.diff.gz
kernel-source-2.4.27_2.4.27-8.dsc
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.dsc
kernel-source-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8_all.deb
kernel-tree-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-tree-2.4.27_2.4.27-8_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you

Bug#285563: marked as done (kernel-source-2.4.27: drm locking fix missing in 2.4 kernels)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#285563: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 14 Dec 2004 06:31:51 +
>From [EMAIL PROTECTED] Mon Dec 13 22:31:51 2004
Return-path: <[EMAIL PROTECTED]>
Received: from atlrel6.hp.com [156.153.255.205] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Ce6Dv-DV-00; Mon, 13 Dec 2004 22:31:51 -0800
Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.15.136.253])
by atlrel6.hp.com (Postfix) with ESMTP id 89DD5C72E
for <[EMAIL PROTECTED]>; Tue, 14 Dec 2004 01:31:50 -0500 (EST)
Received: from ldl.fc.hp.com (ldl.fc.hp.com [15.11.146.30])
by smtp2.fc.hp.com (Postfix) with ESMTP
id 09E2541DF4B; Mon, 13 Dec 2004 23:31:49 -0700 (MST)
Received: from localhost (localhost [127.0.0.1])
by ldl.fc.hp.com (Postfix) with ESMTP id B8FA31341E2;
Mon, 13 Dec 2004 23:31:48 -0700 (MST)
Received: from ldl.fc.hp.com ([127.0.0.1])
by localhost (ldl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 23124-03; Mon, 13 Dec 2004 23:31:47 -0700 (MST)
Received: from krebs (krebs.dannf [10.8.0.7])
by ldl.fc.hp.com (Postfix) with ESMTP id D62E61341DF;
Mon, 13 Dec 2004 23:31:47 -0700 (MST)
Received: by krebs (Postfix, from userid 20800)
id 8705F3B626C; Mon, 13 Dec 2004 23:33:09 -0700 (MST)
Content-Type: multipart/mixed; boundary="===1837287680827107496=="
MIME-Version: 1.0
From: dann frazier <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.4.27: drm locking fix missing in 2.4 kernels
X-Mailer: reportbug 3.4
Date: Mon, 13 Dec 2004 23:33:09 -0700
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at ldl.fc.hp.com
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

This is a multi-part MIME message sent by reportbug.

--===1837287680827107496==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: kernel
Version: 2.4.27-6
Severity: important

The fix for CAN-2004-1056, added in 2.6.8-11, also applies to 2.4 - however,
I don't think it will compile, because 2.4 doesn't define the
LOCK_TEST_WITH_RETURN() in drmP.h.

from 2.6.8's changelog:
  * [SECURITY] Fix insufficient locking checks in DRM code;
CAN-2004-1056 (Fabio M. Di Nitto).

I've attached a backport of the patch from 2.6 w/ this macro missing.

Sorry for being lazy and not fixing it myself - I don't have time to look at
it now, but I also didn't want us to collectively forget about it.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64
Kernel: Linux 2.6.9-1-mckinley
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-source-2.4.27 depends on:
ii  binutils 2.15.90.0.3-0dannf1 The GNU assembler, linker and bina
ii  bzip21.0.2-2 high-quality block-sorting file co
ii  coreutils [fileutils 5.2.1-2 The GNU core utilities
ii  fileutils5.2.1-2 The GNU file management utilities 

-- no debconf information

--===1837287680827107496==
Content-Type: text/x-c; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="drm-locking-checks-2.4.27.patch"

diff -urN kernel-source-2.4.27.orig/drivers/char/drm/i810_dma.c 
kernel-source-2.4.27/drivers/char/drm/i810_dma.c
--- kernel-source-2.4.27.orig/drivers/char/drm/i810_dma.c   2004-12-01 
03:07:54.0 -0700
+++ kernel-source-2.4.27/drivers/char/drm/i810_dma.c2004-12-13 
22:18:50.404864367 -0700
@@ -952,10 +952,7 @@
drm_file_t*priv   = filp->private_data;
drm_device_t  *dev= priv->dev;
 
-   if(!_DRM_LOCK_IS_HELD(dev->lock.hw_lock->lock)) {
-   DRM_ERROR("i810_flush_ioctl called without lock held\n");
-   return -EINVAL;
-   }
+   LOCK_TEST_WITH_RETURN( dev, filp );
 
i810_flush_queue(dev);
return 

Bug#288712: marked as done (kernel-image-2.4.27-1-686: power off button on dell d800 does not work anymore)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288712: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 5 Jan 2005 09:58:31 +
>From [EMAIL PROTECTED] Wed Jan 05 01:58:31 2005
Return-path: <[EMAIL PROTECTED]>
Received: from furon.ujf-grenoble.fr [152.77.2.202] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cm7vz-00062C-00; Wed, 05 Jan 2005 01:58:31 -0800
Received: from tibre2.ujf-grenoble.fr (tana2.ujf-grenoble.fr [152.77.24.22])
by furon.ujf-grenoble.fr (Switch-3.1.3/Switch-3.1.0/Configured  by JE 9 
8 2004) with ESMTP id j059vpvI029486
for <[EMAIL PROTECTED]>; Wed, 5 Jan 2005 10:57:59 +0100 (CET)
Received: from ifapp1.ujf-grenoble.fr (mozart.ujf-grenoble.fr [193.54.241.5])
by tibre2.ujf-grenoble.fr (8.12.8p1/8.12.8) with ESMTP id j059vpWS075556
for <[EMAIL PROTECTED]>; Wed, 5 Jan 2005 10:57:51 +0100 (CET)
(envelope-from [EMAIL PROTECTED])
Message-Id: <[EMAIL PROTECTED]>
Received: from [127.0.0.1] ([:::193.48.255.242])
  by fourier.ujf-grenoble.fr with esmtp; Wed, 05 Jan 2005 10:57:50 +0100
  id 0301D95D.41DBBA1E.6A02
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: San Vu-Ngoc <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-image-2.4.27-1-686: power off button on dell d800 does not work
 anymore
X-Mailer: reportbug 3.2
Date: Wed, 05 Jan 2005 10:57:51 +0100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.3 required=4.0 tests=BAYES_00,HAS_PACKAGE,
MSGID_FROM_MTA_HEADER autolearn=no 
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-image-2.4.27-1-686
Version: 2.4.27-6
Severity: important


I have just upgraded the kernel image for linux 2.4.27 and now I
cannot halt my notebook d800: the power-off button does not respond.
Before the upgrade the computer would not automatically swith off, (I
know I have to switch to kernel 2.6 for this, but I don't want to for
other reasons), but still I could finally switch it off using the
button.

Now the only tricks I know for switching the power off is to unplug
the AC and remove the battery... or restart with CTRL-ALT-DEL (which
works) and then immediately use the power button (which would work
then). But this is bad ! And it forces the BIOS to do a longer check
up at the next reboot.

Any help appreciated.

Best regards
San

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages kernel-image-2.4.27-1-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  fileutils 5.2.1-2The GNU file management utilities 
ii  initrd-tools  0.1.74 tools to create initrd image for p
ii  modutils  2.4.26-1.2 Linux module utilities

-- no debconf information

---
Received: (at 288712-close) by bugs.debian.org; 21 Jan 2005 04:23:18 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:18 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqKM-0001SH-00; Thu, 20 Jan 2005 20:23:18 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027i-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#288712: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 6

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in t

Bug#288046: marked as done (kernel: NFS fh_verify causes lost output (2.4 kernel))

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288046: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 31 Dec 2004 21:23:44 +
>From [EMAIL PROTECTED] Fri Dec 31 13:23:44 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 195-240-184-66-mx.xdsl.tiscali.nl (elrond.fjphome.nl) 
[195.240.184.66] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CkUFM-0003eR-00; Fri, 31 Dec 2004 13:23:44 -0800
Received: from strider.fjphome.nl ([10.19.66.89] ident=fjp)
by elrond.fjphome.nl with esmtp (Exim 4.34)
id 1CkUEp-0003AQ-Ka
for [EMAIL PROTECTED]; Fri, 31 Dec 2004 22:23:11 +0100
From: Frans Pop <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: kernel: NFS fh_verify causes lost output (2.4 kernel)
Date: Fri, 31 Dec 2004 22:23:10 +0100
User-Agent: KMail/1.6.2
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: kernel-source-2.4.27
Severity: grave
Justification: can cause data loss

I am seeing the problem described in #255931 in the Sarges current 2.4 
kernel (2.4.27-6).
The problem is also described in [1].

I have experienced data loss in my mail files that I keep in a 
NFS-exported home directory because of this problem.

The Mail directory and its subdirs were set to drwx--
After changing this to drwxr-xr-x

According to #255931 this has been fixed in 2.6 kernels, but apparently it 
was not fixed in 2.4 kernels.

Note: my server is running Sarge with 2.4.27 kernel; the client is running 
Sarge with 2.6.8 kernel.

[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110421

Cheers,
Frans Pop

---
Received: (at 288046-close) by bugs.debian.org; 21 Jan 2005 04:23:05 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqK9-0001H5-00; Thu, 20 Jan 2005 20:23:05 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027c-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#288046: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 3

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in the latest version of
kernel-source-2.4.27, which is due to be installed in the Debian FTP archive:

kernel-doc-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-8_all.deb
kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  to 
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-8_all.deb
kernel-source-2.4.27_2.4.27-8.diff.gz
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.diff.gz
kernel-source-2.4.27_2.4.27-8.dsc
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.dsc
kernel-source-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8_all.deb
kernel-tree-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-tree-2.4.27_2.4.27-8_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon Horman <[EMAIL PROTECTED]> (supplier of updated ker

kernel-source-2.4.27_2.4.27-8_i386.changes ACCEPTED

[Debian Installer]

Accepted:
kernel-doc-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-8_all.deb
kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  to 
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-8_all.deb
kernel-source-2.4.27_2.4.27-8.diff.gz
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.diff.gz
kernel-source-2.4.27_2.4.27-8.dsc
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.dsc
kernel-source-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8_all.deb
kernel-tree-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-tree-2.4.27_2.4.27-8_all.deb
Announcing to debian-devel-changes@lists.debian.org
Closing bugs: 285521 285563 288046 288272 288279 288712 289202 289517 289682 
290013 290039 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

kernel-image-2.4.27-i386_2.4.27-8_i386.changes ACCEPTED

[Debian Installer]

Accepted:
kernel-build-2.4.27-2_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-build-2.4.27-2_2.4.27-8_i386.deb
kernel-headers-2.4.27-2-386_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-386_2.4.27-8_i386.deb
kernel-headers-2.4.27-2-586tsc_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-586tsc_2.4.27-8_i386.deb
kernel-headers-2.4.27-2-686-smp_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-686-smp_2.4.27-8_i386.deb
kernel-headers-2.4.27-2-686_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-686_2.4.27-8_i386.deb
kernel-headers-2.4.27-2-k6_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-k6_2.4.27-8_i386.deb
kernel-headers-2.4.27-2-k7-smp_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-k7-smp_2.4.27-8_i386.deb
kernel-headers-2.4.27-2-k7_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-k7_2.4.27-8_i386.deb
kernel-headers-2.4.27-2_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2_2.4.27-8_i386.deb
kernel-image-2.4.27-2-386_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-386_2.4.27-8_i386.deb
kernel-image-2.4.27-2-586tsc_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-586tsc_2.4.27-8_i386.deb
kernel-image-2.4.27-2-686-smp_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-686-smp_2.4.27-8_i386.deb
kernel-image-2.4.27-2-686_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-686_2.4.27-8_i386.deb
kernel-image-2.4.27-2-k6_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-k6_2.4.27-8_i386.deb
kernel-image-2.4.27-2-k7-smp_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-k7-smp_2.4.27-8_i386.deb
kernel-image-2.4.27-2-k7_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-k7_2.4.27-8_i386.deb
kernel-image-2.4.27-i386_2.4.27-8.dsc
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-i386_2.4.27-8.dsc
kernel-image-2.4.27-i386_2.4.27-8.tar.gz
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-i386_2.4.27-8.tar.gz
kernel-pcmcia-modules-2.4.27-2-386_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-386_2.4.27-8_i386.deb
kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-8_i386.deb
kernel-pcmcia-modules-2.4.27-2-686-smp_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-686-smp_2.4.27-8_i386.deb
kernel-pcmcia-modules-2.4.27-2-686_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-686_2.4.27-8_i386.deb
kernel-pcmcia-modules-2.4.27-2-k6_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-k6_2.4.27-8_i386.deb
kernel-pcmcia-modules-2.4.27-2-k7-smp_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-k7-smp_2.4.27-8_i386.deb
kernel-pcmcia-modules-2.4.27-2-k7_2.4.27-8_i386.deb
  to 
pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-k7_2.4.27-8_i386.deb
Announcing to debian-devel-changes@lists.debian.org


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#285521: marked as done (kernel-image-2.4.27-1: kernel-image-2.4.27-1 v6: thinkpad does not suspend upon lid closing)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#285521: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 13 Dec 2004 20:57:11 +
>From [EMAIL PROTECTED] Mon Dec 13 12:57:11 2004
Return-path: <[EMAIL PROTECTED]>
Received: from appel.xs4all.nl (oliebij.flower) [80.126.34.178] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CdxFm-0004vZ-00; Mon, 13 Dec 2004 12:57:11 -0800
Received: by oliebij.flower (Postfix, from userid 1000)
id 6F3C0AFAE8; Mon, 13 Dec 2004 21:57:11 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jan Nieuwenhuizen <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-image-2.4.27-1: kernel-image-2.4.27-1 v6: thinkpad does not 
suspend
 upon lid closing
X-Mailer: reportbug 3.4
Date: Mon, 13 Dec 2004 21:57:11 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: kernel-image-2.4.27-1-686
Version: 2.4.27-6
Severity: normal
File: kernel-image-2.4.27-1


APM does not see or react upon closing the lid of my IBM thinkpad X22

Version 2.4.27-2, and earlier kernels are fine.  With v2,
 closing the lid shows

Dec 13 21:46:25 oliebij apmd[1064]: Suspending now

in the log.  Nothing appears with 2.4.27-6.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=nl_NL, LC_CTYPE=nl_NL (charmap=ISO-8859-1)

Versions of packages kernel-image-2.4.27-1-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  fileutils 5.2.1-2The GNU file management utilities 
ii  initrd-tools  0.1.75 tools to create initrd image for p
ii  modutils  2.4.27-0.1 Linux module utilities

-- no debconf information

---
Received: (at 285521-close) by bugs.debian.org; 21 Jan 2005 04:23:18 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:18 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqKL-0001Re-00; Thu, 20 Jan 2005 20:23:17 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027Y-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#285521: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in the latest version of
kernel-source-2.4.27, which is due to be installed in the Debian FTP archive:

kernel-doc-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-8_all.deb
kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  to 
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-8_all.deb
kernel-source-2.4.27_2.4.27-8.diff.gz
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.diff.gz
kernel-source-2.4.27_2.4.27-8.dsc
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.dsc
kernel-source-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8_all.deb
kernel-tree-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-tree-2.4.27_2.4.27-8_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
an

Bug#288279: marked as done (kernel-patch-debian-2.4.27: patches are 600 instead of 644)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288279: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 2 Jan 2005 20:19:02 +
>From [EMAIL PROTECTED] Sun Jan 02 12:19:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from pelican.talon.net [199.224.105.18] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1ClCBq-0005d0-00; Sun, 02 Jan 2005 12:19:02 -0800
Received: from localhost (199.224.114-135.pe2996-2.ppp.talon.net 
[199.224.114.135])
by pelican.talon.net (Postfix) with ESMTP id 9BE3C11176C;
Sun,  2 Jan 2005 15:18:36 -0500 (EST)
Received: from pretzalz by localhost with local (Exim 4.34)
id 1ClCBl-0007Ow-TR; Sun, 02 Jan 2005 15:18:57 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Travis Crump <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-patch-debian-2.4.27: patches are 600 instead of 644
X-Mailer: reportbug 3.2
Date: Sun, 02 Jan 2005 15:18:57 -0500
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-patch-debian-2.4.27
Version: 2.4.27-7
Severity: important

The debian kernel patches are installed with permissions 600 instead of
644 making it impossible for a normal user to use the patches and most 
people do not compile their kernels as root.  Since the patch files had
the correct permissions in 2.4.27-5 and the change occurred in 2.4.27-6
without mention in the changelog I suspect it was an accidental
oversight.

Travis

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-tc1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-patch-debian-2.4.27 depends on:
ii  bzip2 1.0.2-1A high-quality block-sorting file 

-- no debconf information

---
Received: (at 288279-close) by bugs.debian.org; 21 Jan 2005 04:23:04 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqK8-0001FV-00; Thu, 20 Jan 2005 20:23:04 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027g-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#288279: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 5

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in the latest version of
kernel-source-2.4.27, which is due to be installed in the Debian FTP archive:

kernel-doc-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-8_all.deb
kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  to 
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-8_all.deb
kernel-source-2.4.27_2.4.27-8.diff.gz
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.diff.gz
kernel-source-2.4.27_2.4.27-8.dsc
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.dsc
kernel-source-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8_all.deb
kernel-tree-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-tree-2.4.27_2.4.27-8_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the 

Bug#289682: marked as done (kernel-source-2.4.27: ./debian/rules prune is broken)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#289682: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 10 Jan 2005 14:48:54 +
>From [EMAIL PROTECTED] Mon Jan 10 06:48:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail2.expro.pl (kallisto.expro.pl) [193.25.166.6] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Co0qi-0002A9-00; Mon, 10 Jan 2005 06:48:54 -0800
Received: from porridge by kallisto.expro.pl with local (Exim 4.34)
id 1Co0qX-00034B-LG; Mon, 10 Jan 2005 15:48:41 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Marcin Owsiany <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.4.27: ./debian/rules prune is broken
X-Mailer: reportbug 2.63
Date: Mon, 10 Jan 2005 15:48:41 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: Marcin Owsiany <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-source-2.4.27
Version: 2.4.27-7
Severity: normal

Or rather - made unusable by the following check, earlier in the file:

ifneq (,$(wildcard ../kernel-source-$(upstream)_$(upstream).orig.tar.gz))
[...]
else
$(error "Can't find orig tarball.")
endif

This results in:

$ debian/rules prune
debian/rules:30: *** "Can't find orig tarball.".  Stop.
$

I suggest turning the check into a regular at-rule-runtime abort...

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686-smp
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-source-2.4.27 depends on:
ii  binutils  2.15-4 The GNU assembler, linker and bina
ii  bzip2 1.0.2-1A high-quality block-sorting file 
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

-- no debconf information

---
Received: (at 289682-close) by bugs.debian.org; 21 Jan 2005 04:23:20 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:20 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqKO-0001U2-00; Thu, 20 Jan 2005 20:23:20 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027o-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#289682: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 9

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in the latest version of
kernel-source-2.4.27, which is due to be installed in the Debian FTP archive:

kernel-doc-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-8_all.deb
kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  to 
pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-8_all.deb
kernel-source-2.4.27_2.4.27-8.diff.gz
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.diff.gz
kernel-source-2.4.27_2.4.27-8.dsc
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8.dsc
kernel-source-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-8_all.deb
kernel-tree-2.4.27_2.4.27-8_all.deb
  to pool/main/k/kernel-source-2.4.27/kernel-tree-2.4.27_2.4.27-8_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL 

Bug#290039: marked as done (3c59x problems after kernel upgrade from 2.4.27-2 to 2.4.27-6)

[Debian Bug Tracking System]

Your message dated Thu, 20 Jan 2005 23:17:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#290039: fixed in kernel-source-2.4.27 2.4.27-8
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 12 Jan 2005 14:49:01 +
>From [EMAIL PROTECTED] Wed Jan 12 06:49:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from env-gw-02.leeds.ac.uk (mail.env.leeds.ac.uk) [129.11.116.13] 
(mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cojnw-0007Iy-00; Wed, 12 Jan 2005 06:49:00 -0800
Received: from finity-new.leeds.ac.uk ([129.11.116.16] helo=finity-new)
by mail.env.leeds.ac.uk with esmtp (Exim 4.34)
id 1Cojns-V6-Fj
for [EMAIL PROTECTED]; Wed, 12 Jan 2005 14:48:58 +
Received: from jason (helo=localhost)
by finity-new with local-esmtp (Exim 3.35 #1 (Debian))
id 1Cojni-0001tA-00
for <[EMAIL PROTECTED]>; Wed, 12 Jan 2005 14:48:46 +
Date: Wed, 12 Jan 2005 14:48:41 + (GMT)
From: Jason Lander <[EMAIL PROTECTED]>
X-X-Sender: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: 3c59x problems after kernel upgrade from 2.4.27-2 to 2.4.27-6
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-ENV-Spam: -4.9 ()
X-ENV-Spam-Report: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
spamassassin=2.63
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


Package: kernel-image-2.4.27-1-686
Version: 2.4.27-6

After upgrading a kernel-image-2.4.27-1-686 kernel on a Debian sarge
system from 2.4.27-2 to 2.4.27-6, the 3c59x ethernet driver was no longer
working.

Installing a 2.6.8 kernel fixes the problem.

The problem may be at least partially within the PCI subsystem.

The system is an IBM thinkpad T20 laptop with an 3C556B Mini-PC
ethernet/winmodem card.

The principle symptom of the bug is that the MAC address, product code and
revision and revision date reported by the driver are have all bits set.

 00:03.0: 3Com PCI 3c556B Laptop Hurricane at 0x1400. Vers LK1.1.18-ac
 PCI: Setting latency time of devive 00.03.0 to 64
 ff:ff:ff:ff:ff:ff, IRQ 11
  product code  rev .15 date 15-31-127

and the eth0 device fails with messages like

 eth0: command 0x5800 did not complete! Status=0x
  (similarly for command 0x2804, 0x3002)

It would appear that whatever the driver is sending, the response always
has all bits set.

Other possible symptoms include messages such as

 ACPI-1133: *** Error: Method execution failure [\.SB.LNKA._STA]
(Node c11866a0), AE_NOT_EXIST

Similar problems have been reported in the past

  http://www.spinics.net/lists/kernel/old/2003-q1/threads.html#22099

These have usually been attributed to ACPI and APM or to the machine
having run Windows at some point. These problems persist if ACPI and APM
are disabled and the laptop never runs Windows...

- Jason

-- 
Jason Lander   [EMAIL PROTECTED]



---
Received: (at 290039-close) by bugs.debian.org; 21 Jan 2005 04:23:02 +
>From [EMAIL PROTECTED] Thu Jan 20 20:23:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrqK5-0001Bl-00; Thu, 20 Jan 2005 20:23:01 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CrqEz-00027s-00; Thu, 20 Jan 2005 23:17:45 -0500
From: Simon Horman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#290039: fixed in kernel-source-2.4.27 2.4.27-8
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2005 23:17:45 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 11

Source: kernel-source-2.4.27
Source-Version: 2.4.27-8

We believe that the bug you reported is fixed in the latest version of
kernel-s

Processing of kernel-image-2.4.27-i386_2.4.27-8_i386.changes

[Archive Administrator]

kernel-image-2.4.27-i386_2.4.27-8_i386.changes uploaded successfully to 
localhost
along with the files:
  kernel-image-2.4.27-i386_2.4.27-8.dsc
  kernel-image-2.4.27-i386_2.4.27-8.tar.gz
  kernel-headers-2.4.27-2_2.4.27-8_i386.deb
  kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-8_i386.deb
  kernel-headers-2.4.27-2-586tsc_2.4.27-8_i386.deb
  kernel-image-2.4.27-2-586tsc_2.4.27-8_i386.deb
  kernel-pcmcia-modules-2.4.27-2-386_2.4.27-8_i386.deb
  kernel-headers-2.4.27-2-386_2.4.27-8_i386.deb
  kernel-image-2.4.27-2-386_2.4.27-8_i386.deb
  kernel-pcmcia-modules-2.4.27-2-686-smp_2.4.27-8_i386.deb
  kernel-headers-2.4.27-2-686-smp_2.4.27-8_i386.deb
  kernel-image-2.4.27-2-686-smp_2.4.27-8_i386.deb
  kernel-pcmcia-modules-2.4.27-2-686_2.4.27-8_i386.deb
  kernel-headers-2.4.27-2-686_2.4.27-8_i386.deb
  kernel-image-2.4.27-2-686_2.4.27-8_i386.deb
  kernel-pcmcia-modules-2.4.27-2-k6_2.4.27-8_i386.deb
  kernel-headers-2.4.27-2-k6_2.4.27-8_i386.deb
  kernel-image-2.4.27-2-k6_2.4.27-8_i386.deb
  kernel-pcmcia-modules-2.4.27-2-k7_2.4.27-8_i386.deb
  kernel-headers-2.4.27-2-k7_2.4.27-8_i386.deb
  kernel-image-2.4.27-2-k7_2.4.27-8_i386.deb
  kernel-pcmcia-modules-2.4.27-2-k7-smp_2.4.27-8_i386.deb
  kernel-headers-2.4.27-2-k7-smp_2.4.27-8_i386.deb
  kernel-image-2.4.27-2-k7-smp_2.4.27-8_i386.deb
  kernel-build-2.4.27-2_2.4.27-8_i386.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of kernel-source-2.4.27_2.4.27-8_i386.changes

[Archive Administrator]

kernel-source-2.4.27_2.4.27-8_i386.changes uploaded successfully to localhost
along with the files:
  kernel-source-2.4.27_2.4.27-8.dsc
  kernel-source-2.4.27_2.4.27-8.diff.gz
  kernel-patch-debian-2.4.27_2.4.27-8_all.deb
  kernel-doc-2.4.27_2.4.27-8_all.deb
  kernel-source-2.4.27_2.4.27-8_all.deb
  kernel-tree-2.4.27_2.4.27-8_all.deb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel abiname transition and security updates status

[Horms]

On Thu, Jan 20, 2005 at 05:46:39PM +0900, Horms wrote:
> On Fri, Jan 14, 2005 at 08:41:26PM +0900, Horms wrote:
> > On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote:
> > > On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> > > > * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:24]:
> > > > > As far as I know, no other arches except amd64 (not tracking
> > > > > that) are
> > > > 
> > > > mips and mipsel have been updated.  However, given the new local
> > > > root exploit (fixed in SVN), we'll all need to make another round
> > > > of updates anyway.
> > > 
> > > Josh Kwan and I chatted about this yesterday on IRC.  He and I are
> > > both pretty happy with kernel-source-2.4.27 as it is, but I would
> > > like a chance to go through recent bug reports just to make sure
> > > there isn't anything missing. As a result we are aiming to release
> > > next week.
> 
> Sorry for this taking a bit longer than I had hoped.  I now have
> kernel-source-2.4.27 in a state where I am happy to release it as
> 2.4.27-8. 
> 
> I have made both kernel-source-2.4.27 and kernel-image-2.4.27-i386 up on
> http://debian.vergenet.net/pending/ for people to take a look at.
> 
> I aim to releaase these verbatim tomorrow if there are no objections. If
> you make an updates to SVN please drop me an email, so I make sure that
> they make it in. As I am not intending to rebuild again. If you put
> [EMAIL PROTECTED] in To or CC then it will go to the top of my
> mail-reading priority list.

I take it by the stunning silence that no one has any objections to
these packages. I have gone ahead and uploaded them to d.o just now.

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#291039: kernel-patch-debian-2.6.10: bashism in apply file

[Horms]

tags 291039 +pending
tags 291107 +pending
thanks

On Fri, Jan 21, 2005 at 12:31:26PM +0900, Horms wrote:
> > With some good will you can read this from:
> >  
> > http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_03
> > ---
> >   If the command substitution consists of a single subshell, such as:
> >   
> >   $( (command) )
> >   
> >   a conforming application shall separate the "$(" and '(' into two tokens
> >   (that is, separate them with white space). This is required to avoid any
> >   ambiguities with arithmetic expansion.
> > ---
> 
> Thanks for that clarification, I will make the relevant updates.

I have applied the following change to SVN which should rectify this
for 2.6.8, 2.6.9 and 2.6.10. 

-- 
Horms

Index: kernel-source-2.6.8-2.6.8/debian/apply
===
--- kernel-source-2.6.8-2.6.8/debian/apply  (revision 2332)
+++ kernel-source-2.6.8-2.6.8/debian/apply  (working copy)
@@ -157,7 +157,7 @@
exit 0
fi
 
-   for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
if [ $srev -le $current_rev ]; then
@@ -168,7 +168,7 @@
fi
done
 elif [ "$current_rev" = "$upstream" ] || [ $target_rev -gt $current_rev ]; then
-   for base in $((cd $home/series/ && ls -d *) | sort -nt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -nt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
if [ $srev -gt $current_rev ] && [ $srev -le 
$target_rev ]; then
@@ -182,7 +182,7 @@
echo "Nothing to do, exiting."
exit 0
 elif [ $target_rev -lt $current_rev ]; then
-   for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
# -gt because you don't want to unapply the target 
series
Index: kernel-source-2.6.9-2.6.9/debian/apply
===
--- kernel-source-2.6.9-2.6.9/debian/apply  (revision 2332)
+++ kernel-source-2.6.9-2.6.9/debian/apply  (working copy)
@@ -157,7 +157,7 @@
exit 0
fi
 
-   for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
if [ $srev -le $current_rev ]; then
@@ -168,7 +168,7 @@
fi
done
 elif [ "$current_rev" = "$upstream" ] || [ $target_rev -gt $current_rev ]; then
-   for base in $((cd $home/series/ && ls -d *) | sort -nt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -nt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
if [ $srev -gt $current_rev ] && [ $srev -le 
$target_rev ]; then
@@ -182,7 +182,7 @@
echo "Nothing to do, exiting."
exit 0
 elif [ $target_rev -lt $current_rev ]; then
-   for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
# -gt because you don't want to unapply the target 
series
Index: kernel-source-2.6.10-2.6.10/debian/apply
===
--- kernel-source-2.6.10-2.6.10/debian/apply(revision 2332)
+++ kernel-source-2.6.10-2.6.10/debian/apply(working copy)
@@ -157,7 +157,7 @@
exit 0
fi
 
-   for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
if [ $srev -le $current_rev ]; then
@@ -168,7 +168,7 @@
fi
done
 elif [ "$current_rev" = "$upstream" ] || [ $target_rev -gt $current_rev ]; then
-   for base in $((cd $home/series/ && ls -d *) | sort -nt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -nt- -k 2); do
srev=${base#*-}
if [ -n "$srev" ]; then
if [ $srev -gt $current_rev ] && [ $srev -le 
$target_rev ]; then
@@ -182,7 +182,7 @@
echo "Nothing to do, exiting."
exit 0
 elif [ $target_rev -lt $current_rev ]; then
-   for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
+   for base in $( (cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
srev=${base#*-}
   

Re: Bug#291039: kernel-patch-debian-2.6.10: bashism in apply file

[Horms]

On Wed, Jan 19, 2005 at 05:11:23PM +, Gerrit Pape wrote:
> On Wed, Jan 19, 2005 at 04:15:26PM +0900, Horms wrote:
> > On Tue, Jan 18, 2005 at 07:48:38PM +0900, Kenshi Muto wrote:
> > > When I tried to build kernel 2.6.10 from debian source, I got
> > > following message.
> > > 
> > > /usr/src/kernel-patches/all/2.6.10/apply/debian 2.6.10-3
> > > /usr/src/kernel-patches/all/2.6.10/apply/debian: 160: Syntax error: 
> > > Missing '))'
> > > 
> > > I'm using dash as sh.  I think patch-code should use #!/bin/bash or
> > > be fixed for plain bourne shell.
> 
> I agree that this may be a problem in dash.  Anyway, there's a simple
> workaround, the only problem is this line
> 
>  for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
> 
> and to make it the parser easier, simply put a space between the two '(':
> 
>  for base in $( (cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
> 
> With some good will you can read this from:
>  
> http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_03
> ---
>   If the command substitution consists of a single subshell, such as:
>   
>   $( (command) )
>   
>   a conforming application shall separate the "$(" and '(' into two tokens
>   (that is, separate them with white space). This is required to avoid any
>   ambiguities with arithmetic expansion.
> ---

Thanks for that clarification, I will make the relevant updates.

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#283164: marked as done (kernel-source-2.6.9: kernel throws NULL pointer dereference when playing music)

[Debian Bug Tracking System]

Your message dated Fri, 21 Jan 2005 12:15:02 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#283164: 2.6.10 fixed?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 26 Nov 2004 22:53:26 +
>From [EMAIL PROTECTED] Fri Nov 26 14:53:25 2004
Return-path: <[EMAIL PROTECTED]>
Received: from p54816eee.dip.t-dialin.net (xts.homelinux.net) [84.129.110.238] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CXoxw-0007I4-00; Fri, 26 Nov 2004 14:53:24 -0800
Received: by xts.homelinux.net (Postfix, from userid 1000)
id 422F64FD9C; Fri, 26 Nov 2004 23:53:20 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Matthias Heinz <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.6.9: kernel throws NULL pointer dereference when 
playing
 music
X-Mailer: reportbug 3.2
Date: Fri, 26 Nov 2004 23:53:20 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: kernel-source-2.6.9
Version: 2.6.9-3
Severity: important

Hi,


i got this lovely NULL pointer dereference when playing audio files.
(This one occured while selecting another webradio stream in the playlist of 
xmms while an audio file was playing, shouldn't be a problem normally)

dmesg-output:

Linux version 2.6.9 ([EMAIL PROTECTED]) (gcc-Version 3.3.5 (Debian
1:3.3.5-2)) #1Fri Nov 26 23:19:16 CET 2004
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009fc00 (usable)
 BIOS-e820: 0009fc00 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 1ffec000 (usable)
 BIOS-e820: 1ffec000 - 1ffef000 (ACPI data)
 BIOS-e820: 1ffef000 - 1000 (reserved)
 BIOS-e820: 1000 - 2000 (ACPI NVS)
 BIOS-e820:  - 0001 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131052
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 126956 pages, LIFO batch:16
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 ASUS  ) @ 0x000f6920
ACPI: RSDT (v001 ASUS   CUV4X0x30303031 MSFT 0x31313031) @
0x1ffec000
ACPI: FADT (v001 ASUS   CUV4X0x30303031 MSFT 0x31313031) @
0x1ffec080
ACPI: BOOT (v001 ASUS   CUV4X0x30303031 MSFT 0x31313031) @
0x1ffec040
ACPI: DSDT (v001   ASUS CUV4X0x1000 MSFT 0x010b) @
0x
Built 1 zonelists
Kernel command line: BOOT_IMAGE=Linux ro root=301
No local APIC present or hardware disabled
Initializing CPU#0
CPU 0 irqstacks, hard=c0457000 soft=c0456000
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 803.928 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 515164k/524208k available (2390k kernel code, 8524k reserved,
868k data, 132k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Calibrating delay loop... 1572.86 BogoMIPS (lpj=786432)
Security Scaffold v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383f9ff   
CPU: After vendor identify, caps:  0383f9ff   
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps:0383f9ff   0040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Coppermine) stepping 06
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: IRQ9 SCI: Edge set to Level Trigger.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0cc0, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040816
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 1

Bug#287939: kernel-image-2.4.27-i386: Palm sync freezes computer

[Horms]

reassign 87939 kernel-source-2.4.27
thanks

On Thu, Jan 20, 2005 at 11:21:28PM +0100, Maurits van Rees wrote:
> Package: kernel-image-2.4.27-i386
> Followup-For: Bug #287939
> 
> 
> Hi,
> 
> I saw reports for Palm trouble with kernel-image-2.4.27-2-k7. I have a
> K6 so I installed kernel-image-2.4.27-2-k6. I got the same problem. So
> it is probably good that this bug is mentioned in the bug list for
> kernel-image-2.4.27-i386, which I guess is where it would need to be
> fixed. If I should file a bug specifically against
> kernel-image-2.4.27-2-k6 please say so.

I am reassigning it to kernel-source-2.4.27 as that is where the
problem most likely lies.

Can you plase try the 2.4.27-8 kernels from 
http://debian.vergenet.net/pending/
I plan to upload these later today.

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291375: initrd-tools for Debian are one big mess

[Horms]

On Thu, Jan 20, 2005 at 08:28:00PM +0100, Christoph Hellwig wrote:
> On Thu, Jan 20, 2005 at 07:25:21PM +0100, Harald Dunkel wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > 
> > Christoph Hellwig wrote:
> > | Complete agreement here.  We're still looking for a volunteer, though
> > | ;-)
> > |
> > |
> > 
> > Come on! I had offered to take over initrd-tools several
> > months ago. I am sure that there would be several other
> > volunteers.
> 
> Hey, it's not up to me to decide, I'm not even a DD.
> But I'd be happy to see initrd-tools properly maintained
> by you.

I think that the current maintainers of initrd-tools
are pretty busy, gauging on the level of activity there.
I'd welcome someone fixing it up.

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291386: kernel-image-2.4.27-2-686: creates bad initrd with complex lvm2 setup

[Horms]

reassign 291386 initrd-tools
thanks

On Thu, Jan 20, 2005 at 02:17:34PM +0100, Eric Deplagne wrote:
> Package: kernel-image-2.4.27-2-686
> Version: 2.4.27-7
> Severity: critical
> Justification: breaks the whole system
> 
> When the install of kernel-image tries to create initrd,
> those lines go to /var/log/messages:
> 
> Jan 20 09:39:39 fregate kernel: device-mapper: unknown block ioctl 0x801c6d02
> Jan 20 09:39:40 fregate last message repeated 14 times
> 
> I do have 15 logical volumes, which explains how many times the message is 
> emitted...
> 
> I guess I should mention a bit of my partitionning scheme, out of my 
> /etc/fstab:
> 
> # system
> /dev/mapper/vg-root /   ext3defaults,errors=remount-ro 0  
>  1
> /dev/mapper/vg-usr_lib /usr/lib  ext3defaults 0   1
> /dev/mapper/vg-usr_share /usr/share  ext3defaults 0   1
> /dev/mapper/vg-doc /usr/share/docext3defaults 0   1
> /dev/mapper/vg-locale /usr/share/localeext3defaults 0   1
> /dev/mapper/vg-cache_apt /var/cache/apt/archivesext3defaults  
>   0   2
> 
> maybe my having /usr/lib on a different logical volume is relevant...
> just a guess of mine, of course...
> 
> my other logical volumes are one for /home, and some for subdirectories of 
> /home,
> so should not be relevant...
> 
> Last thing I guess I can mention is that on another machine, with only one 
> logical volume for /,
> and one for /home, /var/log/messages gets its two lines, but the system boots 
> properly...
> 
> you might notice I presently run a 2.4.27-1-686, this is my rescue that I had 
> a hard time to setup
> when the problem first happend to me with the last update of 2.4.27-1-868,
> which really hang the computer, having overwritten my working kernel.
> (that did not happen this time because of the -1-686 to -2-686 move)
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.27-1-686
> Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
> 
> Versions of packages kernel-image-2.4.27-2-686 depends on:
> ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
> ii  fileutils 5.2.1-2The GNU file management 
> utilities 
> ii  initrd-tools  0.1.76 tools to create initrd image for 
> p
> ii  modutils  2.4.26-1.2 Linux module utilities
> 
> -- no debconf information
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291357: marked as done (kernel-source-2.4.27: SIGHUP not being sent when controlling process exits)

[Debian Bug Tracking System]

Your message dated Fri, 21 Jan 2005 12:16:36 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291357: kernel-source-2.4.27: SIGHUP not being sent when 
controlling process exits
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 20 Jan 2005 09:16:40 +
>From [EMAIL PROTECTED] Thu Jan 20 01:16:40 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-210-15-201-110.qld.netspace.net.au 
(adsl-brisbane.lubemobile.com.au) [210.15.201.110] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrYQi-0004Hj-00; Thu, 20 Jan 2005 01:16:40 -0800
Received: from master.brisbane.lube ([10.7.0.10])
by adsl-brisbane.lubemobile.com.au with esmtps 
(TLS-1.0:RSA_ARCFOUR_SHA:16)
(Exim 4.43)
id 1CrYQc-00060t-Bj; Thu, 20 Jan 2005 19:16:34 +1000
Received: from virus_scan (helo=master.brisbane.lube)
by master.brisbane.lube with local-smtp (Exim 4.43)
id 1CrYQb-lW-WC; Thu, 20 Jan 2005 19:16:34 +1000
Received: from rstuart by master.brisbane.lube with local (Exim 4.43)
id 1CrYQb-lR-KM; Thu, 20 Jan 2005 19:16:33 +1000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Russell Stuart <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: kernel-source-2.4.27: SIGHUP not being sent when controlling process 
exits
X-Mailer: reportbug 3.2
Date: Thu, 20 Jan 2005 19:16:33 +1000
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kernel-source-2.4.27
Version: 2.4.27-6
Severity: important



-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-6-lube-686-smp
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages kernel-source-2.4.27 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-1A high-quality block-sorting file 
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

-- no debconf information

drivers/char/tty_io.c, line 768, contains this line:

/* tty_deferred_ldisc_switch(N_TTY);

Note: no trailing "*/".  I am not sure what was intended here,
but the net result is to comment out the code that sends a
SIGHUP to child processed when their leader exits.

This is bad, real bad.  This means that after:

login: me
$ sleep 1000
$ exit

sleep still runs.  The errant patch is in
093_tty_lockup.diff.bz2.


---
Received: (at 291357-done) by bugs.debian.org; 21 Jan 2005 03:28:09 +
>From [EMAIL PROTECTED] Thu Jan 20 19:28:09 2005
Return-path: <[EMAIL PROTECTED]>
Received: from koto.vergenet.net [210.128.90.7] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CrpSz-0005Bp-00; Thu, 20 Jan 2005 19:28:09 -0800
Received: by koto.vergenet.net (Postfix, from userid 7100)
id E683934171; Fri, 21 Jan 2005 12:08:56 +0900 (JST)
Date: Fri, 21 Jan 2005 12:16:36 +0900
From: Horms <[EMAIL PROTECTED]>
To: Thiemo Seufer <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#291357: kernel-source-2.4.27: SIGHUP not being sent when 
controlling process exits
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-Cluestick: seven
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

On Thu, Jan 20, 2005 at 04:12:35PM +0100, Thiemo Seufer wrote:
> tags 291357 +sarge
> thanks
> 
> Russell Stuart wrote:
> > Package: kernel-source-2.4.27
> > Version: 2.4.27-6
> > Severity: important
> [snip]
> > drivers/char/tty_io.c, line 768, contains this line:
> > 
> > /* tty_deferred_ldisc_switch(N_TTY);
> > 
> > Note: no trailing "*/".
> 
> This is fixed in 2.4.

Bug#289810: same fix as in 2.6.9

[Itai Seggev]

This bug is exactly the same as bug 282234 in 2.6.9, and it has the
same fix. You need to edit drivers/video/vesafb.c and move line 480
(which reads "module_init(vesafb_init);") outside of the #ifdef
MODULE. I move it up to line 474 and everything works just
fine. Perhaps the debian patch can be fixed so it no longer moves this
line into the ifdef? (it's not in the pristine sources)

Many thanks,

-- 
Itai

Itai Seggev, University of Chicago, Department of Physics

In 1997 a group of programmers started writing a desktop environment
to fix a travesty they didn't create.  Their program promptly found
its way onto un*x systems everywhere. Today, still opposed by a
software monopolist, they survive as soldiers of fortune.  If you share
their vision, if you know you can help, and if you can connect to
internet, maybe you can join... the K-Team.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#285017: kernel-image-2.4.27-1-686: upgrading from v2 to v6 slows down my modem: upgrading from v2 to v6 slows down my modem

[Horms]

On Wed, Jan 19, 2005 at 10:23:29AM +0100, Joan Andersen og Jesper Gertz wrote:
> Hi
> 
> I have the same problem:
> 
>   
> Package: kernel-image-2.4.27-1-686
> Version: 2.4.27-6
> OS version: Testing
> 
> My connection tops off at 1K.
> My external 56K modem is connected to ttys0.
> It doesn't matter if I disable acpi in kernel.
> My modem connects to my ISP at about 40K.
> It doesn't matter if I disable discover version 2.0.6-3.
> 
> When I boot Debian into my other kernel (bf2.4 from Stable),
> the problem dissapears.

Please try the 2.4.27-8 kernel that is in 
http://debian.vergenet.net/pending/

I plan to upload this later today.

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel abiname transition and security updates status

[Steve Langasek]

On Thu, Jan 20, 2005 at 11:11:14PM +0100, Christian T. Steigies wrote:

> > > I have no idea about the abichanges, m68k uses no abiname? Is that a 
> > > problem?

> > The downside of not includeing an abiname in the package name is that
> > past d-i releases will break once the updated kernels and udebs reach
> > testing.

> So they not yet released d-i "releases" break on the most popular arch of
> the early nineties. Does anybody care? If there were abinames in the m68k
> package (-1, -2, ... added to the package name?), would we create a new
> package for every abichange? Doesn't that contradict the plan of d-kernel to
> reduce the number of kernel-packages?

The point of using an abiname in your package naming is that you're assured
(barring bugs) that all kernel modules in your search path are compatible
with that kernel version.  If you use /lib/modules/2.4.27-$subarch instead
of /lib/modules/2.4.27-$abiname-$subarch, you have no mechanism for coping
with version skew when a Debian revision includes a change to the public
interfaces used by modules.

It does not contradict the plans for keeping the kernel package count down,
because you don't get to keep both ABI versions around -- you don't want the
old one *anyway*, because it has security bugs.  In any case, the source
package names are kept the same and only the binary package names change, so
you only ever get one of these in testing at a time.

-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Bug#287939: kernel-image-2.4.27-i386: Palm sync freezes computer

[Maurits van Rees]

Package: kernel-image-2.4.27-i386
Followup-For: Bug #287939


Hi,

I saw reports for Palm trouble with kernel-image-2.4.27-2-k7. I have a
K6 so I installed kernel-image-2.4.27-2-k6. I got the same problem. So
it is probably good that this bug is mentioned in the bug list for
kernel-image-2.4.27-i386, which I guess is where it would need to be
fixed. If I should file a bug specifically against
kernel-image-2.4.27-2-k6 please say so.

My Palm IIIc is connected with /dev/pilot, which is a symlink to
/dev/ttyS0. With kernel 2.4.24 all is fine. I used the debian source
to build that kernel and tweaked the config.

With the stock Debian kernel image 2.4.27-k6 syncing doesn't
work. When I try to connect to it using JPilot or pilot-xfer or some
of the other programs in pilot-link the whole computer freezes. This
is before I even touch the sync button on the cradle. The keyboard
doesn't function anymore, not even the led for NumLock can be
changed. Mouse doesn't work. When some music is playing that sound is
stopped as well. It only reacts to a hard reset.

Other than that, 2.4.27 seems to run just fine. I had to put 8139too
into /etc/modules in order to get some network traffic flowing, but
that was the only hiccup.

I've booted into 2.4.24 now, hence the kernel version mentioned
below. If reportbug wants to supply this info, who am I to argue with
it. :)

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.4.24
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291464: kernel-source-2.6.10: Kernel Panic with SMP PIII as NFS Client under heavy NFS Load

[Stuart Sheldon]

Package: kernel-source-2.6.10
Version: 2.6.10-4
Severity: important



-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (900, 'testing'), (100, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686-actusa
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-source-2.6.10 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-1A high-quality block-sorting file 
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

-- no debconf information
System kernel is installed on displays following message on screen:
Kernel panic - not syncing: Attempting to free lock with active block list 

References found in this thread from linux-kernel list:
http://seclists.org/lists/linux-kernel/2005/Jan/1198.html

This bug report is being generated from our main build machine, not system
that was kernel panic'ing. Thread was not clear if this was resolved with
the patch listed, but problem still exists in unpatched kernel-source-2.6.10-4.

Please advise if I can be of any assistance.

Stu Sheldon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel abiname transition and security updates status

[Christian T. Steigies]

On Thu, Jan 20, 2005 at 04:58:10PM -0500, Joey Hess wrote:
> Christian T. Steigies wrote:
> > I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make 
> > it
> > urgent...: Too young, only 7 of 10 days old
> > For 2.4.27 I am waiting for the latest kernel-source to be released before I
> > build new images. This is supposed to happen today/tomorrow? I should be 
> > able
> > to get those images ready over the weekend then, and I'll try to remember to
> > make it more urgent...
> 
> I don't think we actually use the 2.6 m68k kernels in d-i yet, only 2.4
> (and 2.2 for some aubarches).

Oh, right, I forgot we are stuck in the middle ages. But you don't need an
updated 2.2 with abichanges so they continue to work with new d-i releases?
I guess I haven't grasped the whole abichange thingy.

> > I have no idea about the abichanges, m68k uses no abiname? Is that a 
> > problem?
> 
> The downside of not includeing an abiname in the package name is that
> past d-i releases will break once the updated kernels and udebs reach
> testing.

So they not yet released d-i "releases" break on the most popular arch of
the early nineties. Does anybody care? If there were abinames in the m68k
package (-1, -2, ... added to the package name?), would we create a new
package for every abichange? Doesn't that contradict the plan of d-kernel to
reduce the number of kernel-packages?
 
> > Is there anything else m68k has to do, like build new d-i-k-i-m68k packages?
> > Anything else I am missing?
> 
> We will need to rebuild that package once the new kernel is uploaded,
> yes.

If that is all (somebody else builds the d-i kernel package for m68k), we
should be ready within a week (keeping fingers crossed that none of my
hardware breaks...)

Christian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel abiname transition and security updates status

[Steve Langasek]

On Thu, Jan 20, 2005 at 10:25:47PM +0100, Christian T. Steigies wrote:
> On Thu, Jan 20, 2005 at 04:13:17PM -0500, Joey Hess wrote:
> > 
> > Update for current status, 10 days after my first mail:
> > 
> > m68k
> > No abiname; not updated. ?
> > 
> > [This is another arch that I'd consider releasing d-i rc3 without
> > it being updated for the kernel security fixes.]

> > So s390 and hppa are the main potential rc3 blockers, while alpha and
> > sparc just need to get kernels into testing and arm, m68k, and powerpc
> > (2.4) need to get a move on if you want them updated for the rc3
> > release. We're fast approaching the point where the kernel updates are
> > the only significant thing blocking the rc3 release.

> > Note that besides the abiname changes, there are pending uploads for
> > both 2.4 and 2.6, for all arches, to fix numerous other security holes.
> > I'm not considering those above, since it should be much easier to roll
> > a fix for a "normal" kernel security hole into d-i than the it is for
> > these security fixes that involve ABI changes.

> I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make it
> urgent...: Too young, only 7 of 10 days old

Since this is a security fix, I've bumped the urgency to let this package in
with tonight's run.

Thanks,
-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Re: kernel abiname transition and security updates status

[Thiemo Seufer]

Christian T. Steigies wrote:
[snip]
> I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make it
> urgent...: Too young, only 7 of 10 days old
> For 2.4.27 I am waiting for the latest kernel-source to be released before I
> build new images. This is supposed to happen today/tomorrow? I should be able
> to get those images ready over the weekend then, and I'll try to remember to
> make it more urgent...

Supposed-to-be final kernel-source can be found at
http://debian.vergenet.net/pending/

> I have no idea about the abichanges, m68k uses no abiname? Is that a problem?
> Is there anything else m68k has to do, like build new d-i-k-i-m68k packages?
> Anything else I am missing?

External modules, as well as modules separated out for d-i, will break,
so they need to be kept in sync. IOW, needs new d-i-k-i-m68k, preferably
uploaded at the same time than the new kernel, and also updated external
modules if there are any.


Thiemo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel abiname transition and security updates status

[Thiemo Seufer]

Horms wrote:
[snip]
> I have made both kernel-source-2.4.27 and kernel-image-2.4.27-i386 up on
> http://debian.vergenet.net/pending/ for people to take a look at.

Builds fine for mips, images soon available at
http://people.debian.org/~ths/mips-kernels/kernel-patch-2.4.27-mips/


Thiemo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel abiname transition and security updates status

[Joey Hess]

Christian T. Steigies wrote:
> I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make it
> urgent...: Too young, only 7 of 10 days old
> For 2.4.27 I am waiting for the latest kernel-source to be released before I
> build new images. This is supposed to happen today/tomorrow? I should be able
> to get those images ready over the weekend then, and I'll try to remember to
> make it more urgent...

I don't think we actually use the 2.6 m68k kernels in d-i yet, only 2.4
(and 2.2 for some aubarches).

> I have no idea about the abichanges, m68k uses no abiname? Is that a problem?

The downside of not includeing an abiname in the package name is that
past d-i releases will break once the updated kernels and udebs reach
testing.

> Is there anything else m68k has to do, like build new d-i-k-i-m68k packages?
> Anything else I am missing?

We will need to rebuild that package once the new kernel is uploaded,
yes.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: kernel abiname transition and security updates status

[Christian T. Steigies]

On Thu, Jan 20, 2005 at 04:13:17PM -0500, Joey Hess wrote:
> 
> Update for current status, 10 days after my first mail:
> 
> m68k
>   No abiname; not updated. ?
> 
>   [This is another arch that I'd consider releasing d-i rc3 without
>   it being updated for the kernel security fixes.]

 
> So s390 and hppa are the main potential rc3 blockers, while alpha and
> sparc just need to get kernels into testing and arm, m68k, and powerpc
> (2.4) need to get a move on if you want them updated for the rc3
> release. We're fast approaching the point where the kernel updates are
> the only significant thing blocking the rc3 release.
> 
> Note that besides the abiname changes, there are pending uploads for
> both 2.4 and 2.6, for all arches, to fix numerous other security holes.
> I'm not considering those above, since it should be much easier to roll
> a fix for a "normal" kernel security hole into d-i than the it is for
> these security fixes that involve ABI changes.

I uploaded new 2.6.8 kernel-images for m68k a week ago, but I did not make it
urgent...: Too young, only 7 of 10 days old
For 2.4.27 I am waiting for the latest kernel-source to be released before I
build new images. This is supposed to happen today/tomorrow? I should be able
to get those images ready over the weekend then, and I'll try to remember to
make it more urgent...

I have no idea about the abichanges, m68k uses no abiname? Is that a problem?
Is there anything else m68k has to do, like build new d-i-k-i-m68k packages?
Anything else I am missing?

Christian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291217: NFS-ACL patches for kernel 2.6.9rc2

[Thiemo Seufer]

Paul Coray wrote:
> The latest patches for kernel 2.6.9rc2 can be found at 
> http://acl.bestbits.at/nfsacl/ (not linked on homepage).

The usual way to get feature patches in the debian kernel is by sending
them upstream to kernel.org. The "known problems" section on that
webpage suggests there's still some work needed to make the patch
acceptable for general use.


Thiemo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#291362: installation-reports: LVM install failed due to missing dmsetup

[Joey Hess]

Wesley W. Terpstra wrote:
> On Thu, Jan 20, 2005 at 02:59:00PM -0500, Joey Hess wrote:
> > initrd-tools 0.1.76 changed to abort on install to LVM if dmsetup was
> > not installed. I think this was a mistake. I'm ccing tbm, who made the
> > change.
> 
> I made the change.

Right, tbm only committed it.

> > This was apparently added as part of a patch to support encrypted root
> > filesystems, which is not supported by d-i at all; silently adding a
> > requirement that dmsetup be installed for lvm systems when previously it
> > was not needed is not a good thing to have done.
> 
> Why is the d-i seeing the new initrd-tools at all?
> I thought base was frozen?

a) People can install unstable using d-i and we want this to keep working.
b) We had to let the new initrd-tools into testing because it fixed
   other RC bugs.

> > It seems to me that the above code could easily be rewritten to skip
> > calling dmsetup if it was not installed, and run the lvm function. This
> > might be a little less robust on systems that do use encrypted root
> > filesystems, but at least it wouldn't require us to make last-minute changes
> > to d-i and debian-cd to add dmsetup everywhere.
> 
> At any rate, I agree with your solution, if there is no dmsetup it makes
> sense to fall back to using lvm. Since cryptsetup depends on dmsetup, there
> is nothing wrong with this solution.

Great, so something like this? (Untested)

--- mkinitrd.orig   2005-01-20 16:15:03.0 -0500
+++ mkinitrd2005-01-20 16:16:43.0 -0500
@@ -390,20 +390,19 @@
 dm() {
local dmname

-   if ! command -v dmsetup > /dev/null 2>&1; then
-   echo Root is on a DM device, but dmsetup not installed >&2
-   exit 1
-   fi
+   if command -v dmsetup > /dev/null 2>&1; then
+   dmdev=$(printf "(%d, %d)" $major $minor)

-   dmdev=$(printf "(%d, %d)" $major $minor)
-   
-   if ! dmsetup ls | grep -q "$dmdev\$"; then
-   echo Unknown DM device $major:$minor >&2
-   exit 1
+   if ! dmsetup ls | grep -q "$dmdev\$"; then
+   echo Unknown DM device $major:$minor >&2
+   exit 1
+   fi
+   
+   dmname=$(dmsetup ls | grep "$dmdev\$" | sed 
's/^\([^[:space:]]*\).*$/\1/')
fi

-   dmname=$(dmsetup ls | grep "$dmdev\$" | sed 
's/^\([^[:space:]]*\).*$/\1/')
-   if dmsetup table $dmname | cut -d" " -f3 | grep -q ^crypt$ ; then
+   if [ -n "$dmname" ] && \
+  dmsetup table $dmname | cut -d" " -f3 | grep -q ^crypt$ ; then
dmcrypt
elif command -v lvmiopversion > /dev/null 2>&1; then
lvm

-- 
see shy jo


signature.asc
Description: Digital signature

Re: kernel abiname transition and security updates status

[Joey Hess]

Joey Hess wrote:
> Before we can release d-i rc3 we need all the kernels updated with at
> least some security fixes, notably the ones that change the kernel
> module ABI, and we need to update things to reflect the new kernel
> "abiname". Here's my understanding of the current status of that:

Update for current status, 10 days after my first mail:

alpha
Kernel updated, but not yet in testing (old binaries); udebs updated;
rootskel/base-installer/debian-cd not yet updated.

amd64
Updated, but I'm not tracking this arch.

arm
No abiname; not updated. ?

[At the moment this is one of the arches that I'd consider
releasing d-i rc3 without it being updated for the kernel
security fixes, since it has no abiname, and since the daily
builds have been down since October.]

hppa
2.4 lacks abiname, has not been updated, and we're in the process of
dropping it.

2.6 has abiname; not updated.

[This is likely to block d-i rc3 until the new hppa 2.6 kernels
with the new abiname are available.]

i386
2.4 and 2.6 updated to -2 abiname; 2.4 debs in testing, 2.6
not; udebs updated; rootskel/base-installer/debian-cd not yet
updated.

ia64
2.4 and 2.6 updated to -2 abiname; debs in testing; udebs
updated; rootskel/base-installer/debian-cd not yet updated.
No initrd builds for last 10 days, at least 2.4 udebs untested.

m68k
No abiname; not updated. ?

[This is another arch that I'd consider releasing d-i rc3 without
it being updated for the kernel security fixes.]

mips
No abiname. Kernel updated and in testing; udebs updated.
No initrd daily builds since Dec 31 so new udebs untested.

mipsel
No abiname. Kernel updated and in testing; udebs updated.

powerpc
No abiname. 2.4 not updated. 2.6 updated, debs in testing;
udebs updated.

[If powerpc 2.4 is not updated with the security fixes soon, I
will probably not let it block a d-i rc3 release.]

s390
Has abiname; not updated

[This is likely to block d-i rc3 until the new kernels with the new
abiname are available.]

sparc
2.6 updated to -2 abiname; 2.4 not yet updated (except in svn); 
2.6 debs not yet in testing (due to RC #288180); udebs updated;
rootskel/base-installer/debian-cd not yet updated.

So s390 and hppa are the main potential rc3 blockers, while alpha and
sparc just need to get kernels into testing and arm, m68k, and powerpc
(2.4) need to get a move on if you want them updated for the rc3
release. We're fast approaching the point where the kernel updates are
the only significant thing blocking the rc3 release.

Note that besides the abiname changes, there are pending uploads for
both 2.4 and 2.6, for all arches, to fix numerous other security holes.
I'm not considering those above, since it should be much easier to roll
a fix for a "normal" kernel security hole into d-i than the it is for
these security fixes that involve ABI changes.

-- 
see shy jo


signature.asc
Description: Digital signature

Two gcc on the same machine - how to use one when needed?

[Drasko Draskovic]

I had problem compiling 2.4.18 vanilla kernel. I am
currently using gcc-3.3. I was wondering is there a
way to have two compilers on the same machine (I
suppose apt-get gcc-2.95 would do the job), and then
switch between them elegantly when needed. Gentoo has
a cute tool called gcc-config. Is there something like
this in Debian? 
How to switch between compilers?

Thanks,
I really need this 2.4.28 kernel with LinSec patch
compiled, for the project I'm working on

Drasko



__ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#291362: installation-reports: LVM install failed due to missing dmsetup

[Wesley W. Terpstra]

On Thu, Jan 20, 2005 at 02:59:00PM -0500, Joey Hess wrote:
> initrd-tools 0.1.76 changed to abort on install to LVM if dmsetup was
> not installed. I think this was a mistake. I'm ccing tbm, who made the
> change.

I made the change.

> This was apparently added as part of a patch to support encrypted root
> filesystems, which is not supported by d-i at all; silently adding a
> requirement that dmsetup be installed for lvm systems when previously it
> was not needed is not a good thing to have done.

Why is the d-i seeing the new initrd-tools at all?
I thought base was frozen?

> It seems to me that the above code could easily be rewritten to skip
> calling dmsetup if it was not installed, and run the lvm function. This
> might be a little less robust on systems that do use encrypted root
> filesystems, but at least it wouldn't require us to make last-minute changes
> to d-i and debian-cd to add dmsetup everywhere.

At any rate, I agree with your solution, if there is no dmsetup it makes
sense to fall back to using lvm. Since cryptsetup depends on dmsetup, there
is nothing wrong with this solution.

-- 
Wesley W. Terpstra


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#291362: installation-reports: LVM install failed due to missing dmsetup

[Joey Hess]

severity 291362 serious
reassign 291362 initrd-tools
thanks

Lupe Christoph wrote:
> Kernel installation (2.4.27) failed because the initrd could not be
> generated. dmsetup is missing.
> 
> Root is on a DM device, but dmsetup not installed
> Failed to create initrd image.
> 
> Same happens with 2.6.8.
> 
> Manually installing dmsetup as /target/sbin/dmsetup before installing
> the base system cures the problem. The dmsetup package must be part of
> the base system to solve this permanently.

initrd-tools 0.1.76 changed to abort on install to LVM if dmsetup was
not installed. I think this was a mistake. I'm ccing tbm, who made the
change.

Here's the diff:

 dm() {
-   if command -v lvmiopversion > /dev/null 2>&1; then
+   local dmname
+   
+   if ! command -v dmsetup > /dev/null 2>&1; then
+   echo Root is on a DM device, but dmsetup not installed >&2
+   exit 1
+   fi
+   
+   dmdev=$(printf "(%d, %d)" $major $minor)
+   
+   if ! dmsetup ls | grep -q "$dmdev\$"; then
+   echo Unknown DM device $major:$minor >&2
+   exit 1
+   fi
+   
+   dmname=$(dmsetup ls | grep "$dmdev\$" | sed 's/^\([^[:space:]]*\).*$/\1
/')
+   if dmsetup table $dmname | grep -q crypt; then
+   dmcrypt
+   elif command -v lvmiopversion > /dev/null 2>&1; then
lvm
elif [ ! -x /etc/mkinitrd/scripts/evms ]; then
echo Unknown DM device $major:$minor >&2

This was apparently added as part of a patch to support encrypted root
filesystems, which is not supported by d-i at all; silently adding a
requirement that dmsetup be installed for lvm systems when previously it
was not needed is not a good thing to have done.

It seems to me that the above code could easily be rewritten to skip
calling dmsetup if it was not installed, and run the lvm function. This
might be a little less robust on systems that do use encrypted root
filesystems, but at least it wouldn't require us to make last-minute changes
to d-i and debian-cd to add dmsetup everywhere.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#291375: initrd-tools for Debian are one big mess

[Christoph Hellwig]

On Thu, Jan 20, 2005 at 07:25:21PM +0100, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Christoph Hellwig wrote:
> | Complete agreement here.  We're still looking for a volunteer, though
> | ;-)
> |
> |
> 
> Come on! I had offered to take over initrd-tools several
> months ago. I am sure that there would be several other
> volunteers.

Hey, it's not up to me to decide, I'm not even a DD.
But I'd be happy to see initrd-tools properly maintained
by you.

> If you want to replace initrd-tools by something else,
> then I would suggest to switch to the new initramfs
> procedure (see Gentoo).

Dito for Red Hat/Fedora


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291375: initrd-tools for Debian are one big mess

[Harald Dunkel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Hellwig wrote:
| Complete agreement here.  We're still looking for a volunteer, though
| ;-)
|
|
Come on! I had offered to take over initrd-tools several
months ago. I am sure that there would be several other
volunteers.
But a big part of the mess about initrd-tools is a lack of
documentation. It can do a lot, if you make use of the
scripts directory, for example.
If you want to replace initrd-tools by something else,
then I would suggest to switch to the new initramfs
procedure (see Gentoo).
Regards
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB7/eRUTlbRTxpHjcRAvKLAJ0a2LZritHwCj6mR0JOmVKmg1uS9wCfa0tI
jBGiG1sEe3z5HDJiDe8hNd0=
=WlFn
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291217: NFS-ACL patches for kernel 2.6.9rc2

[Paul Coray]

The latest patches for kernel 2.6.9rc2 can be found at 
http://acl.bestbits.at/nfsacl/ (not linked on homepage).

Greets
Paul
--
Paul Coray
Administrator Server und Netzwerk
Oeffentliche Bibliothek der Universitaet Basel
EDV-Abteilung
Schoenbeinstrasse 18-20
CH-4056 Basel
Tel: +41 61 267 05 13
Fax: +41 61 267 31 03
mailto:[EMAIL PROTECTED]
http://www.ub.unibas.ch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#287100: CONFIG_AUDIT is indeed fairly critical for

[Manoj Srivastava]

Hi,

CONFIG_AUDIT is required to have Se-Linux be usefully
 deployed, since without tht we can't even test any other aspect of
 Se-Linux functionality in the Debian kernel image packages. Without
 audit, any modifications needed to policy are hard to discover, since
 policy violations are just silently blocked -- even if that is not
 the desired option. Also, as a user, it is nice to know when attempts
 are made that violate security polices ;-)

Indeed, this is what Kconfig says in 2.6.10:
==
config AUDIT
bool "Auditing support"
default y if SECURITY_SELINUX
default n
help
  Enable auditing infrastructure that can be used with another
  kernel subsystem, such as SELinux (which requires this for
  logging of avc messages output).  Does not do system-call
  auditing without CONFIG_AUDITSYSCALL.
==

Adding AUDIT has a very minimal affect on the size of the
 resulting image.

manoj
-- 
A computer scientist is someone who fixes things that aren't broken.
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291357: kernel-source-2.4.27: SIGHUP not being sent when controlling process exits

[Thiemo Seufer]

tags 291357 +sarge
thanks

Russell Stuart wrote:
> Package: kernel-source-2.4.27
> Version: 2.4.27-6
> Severity: important
[snip]
> drivers/char/tty_io.c, line 768, contains this line:
> 
>   /* tty_deferred_ldisc_switch(N_TTY);
> 
> Note: no trailing "*/".

This is fixed in 2.4.27-7.


Thiemo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#291357: kernel-source-2.4.27: SIGHUP not being sent when controlling process exits

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 291357 +sarge
Bug#291357: kernel-source-2.4.27: SIGHUP not being sent when controlling 
process exits
There were no tags set.
Tags added: sarge

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#274720: enumerating kernels where IDE detection fails

[Stephen Gildea]

I have the same hardware as Florent (Athlon, ASUS VIA, Adaptec RAID),
and I'm running into the same bug.  That is, the kernel sees my Adaptec
RAID disk fine (presented as SCSI, aacraid driver), but it doesn't see
any of my IDE disks.

I have done some experiments to try to pin down the location of this bug:

2.4.21-1-k7 fails to find the RAID array, but it works if I compile the
kernel with the Adaptec aacraid driver 1.1.5, and then it can see the
IDE disks.  Earlier 2.4 Debian kernels behave the same.

2.4.22-1-k7 and a 2.4.22 kernel I built with the Adaptec driver both see
the RAID array but fail to see the IDE disks.  Later 2.4 Debian kernels
behave the same.

2.6.0-1-k7 works completely.  Both the RAID and IDE disks work.

2.6.2-1-k7 fails to see the IDE disks.  Rebuilding myself gives the same
results.  Later 2.6 Debian kernels behave the same.

KNOPPIX works with recent 2.4 and all 2.6 kernels.  In particular,
2.4.26 and 2.6.6 kernels from KNOPPIX work.  That makes me think this is
a Debian bug, not a Linux bug.

So ... what broke between 2.4.21 and 2.4.22 and between 2.6.0 and 2.6.2?
Changes from 2.4.21 to 2.4.22 include the E-IDE driver (drivers/ide/)
changing from revision 6.31 to 7.00beta4.  I built a 2.4.22 kernel with
the ide driver from 2.4.21, and this worked.  It seems there has been a
regression.

I hope this information helps someone debug this further.  How can I help?
This problem is getting in my way.

 < Stephen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291357: A Better Example

[Russell Stuart]

It appears the example I gave happens on a working
kernel as well.  This one doesn't:

[EMAIL PROTECTED]:~$ ssh 10.7.0.3
Linux titan.brisbane.lube 2.4.27-6-lube-686-smp #1 SMP Thu Jan 13 
16:01:29 EST 2005 i686 GNU/Linux

[EMAIL PROTECTED]:~$ ps -fu $LOGNAME
UIDPID  PPID  C STIME TTY  TIME CMD
rstuart  15870 15868  0 23:33 ?00:00:00 sshd: [EMAIL 
PROTECTED]/0
rstuart  15872 15870  2 23:33 pts/000:00:00 -bash
rstuart  15895 15872  0 23:33 pts/000:00:00 ps -fu rstuart
[EMAIL PROTECTED]:~$ (sleep 2; kill -9 15870) & sleep 12345
[1] 15900
Connection to 10.7.0.3 closed by remote host.
Connection to 10.7.0.3 closed.
[EMAIL PROTECTED]:~$ ssh 10.7.0.3
Linux titan.brisbane.lube 2.4.27-6-lube-686-smp #1 SMP Thu Jan 13 
16:01:29 EST 2005 i686 GNU/Linux

[EMAIL PROTECTED]:~$ ps -fu $LOGNAME
UIDPID  PPID  C STIME TTY  TIME CMD
rstuart  15872 1  0 23:33 ?00:00:00 -bash
rstuart  15901 15872  0 23:33 ?00:00:00 sleep 12345
rstuart  15905 15903  0 23:33 ?00:00:00 sshd: [EMAIL 
PROTECTED]/2
rstuart  15907 15905  2 23:33 pts/200:00:00 -bash
rstuart  15932 15907  0 23:33 pts/200:00:00 ps -fu rstuart
[EMAIL PROTECTED]:~$

Notice the sleep is still running.  On a working kernel is isn't
because it has been sent a SIGHUP.

By the way, it appears the code concerned was copied from 2.6.8,
or a 2.6 kernel a least.  In 2.6.8, the code looks like this:

/* Defer ldisc switch */
/* tty_deferred_ldisc_switch(N_TTY);

  This should get done automatically when the port closes and
  tty_release is called */

read_lock(&tasklist_lock);

When copied to 2.4.27, the code ended up like this:

/* Defer ldisc switch */
/* tty_deferred_ldisc_switch(N_TTY);

read_lock(&tasklist_lock);

When the trailing */ is restored, the kernel works again.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291386: kernel-image-2.4.27-2-686: creates bad initrd with complex lvm2 setup

[Eric Deplagne]

Package: kernel-image-2.4.27-2-686
Version: 2.4.27-7
Severity: critical
Justification: breaks the whole system

When the install of kernel-image tries to create initrd,
those lines go to /var/log/messages:

Jan 20 09:39:39 fregate kernel: device-mapper: unknown block ioctl 0x801c6d02
Jan 20 09:39:40 fregate last message repeated 14 times

I do have 15 logical volumes, which explains how many times the message is 
emitted...

I guess I should mention a bit of my partitionning scheme, out of my /etc/fstab:

# system
/dev/mapper/vg-root /   ext3defaults,errors=remount-ro 0   1
/dev/mapper/vg-usr_lib /usr/lib  ext3defaults 0   1
/dev/mapper/vg-usr_share /usr/share  ext3defaults 0   1
/dev/mapper/vg-doc /usr/share/docext3defaults 0   1
/dev/mapper/vg-locale /usr/share/localeext3defaults 0   1
/dev/mapper/vg-cache_apt /var/cache/apt/archivesext3defaults
0   2

maybe my having /usr/lib on a different logical volume is relevant...
just a guess of mine, of course...

my other logical volumes are one for /home, and some for subdirectories of 
/home,
so should not be relevant...

Last thing I guess I can mention is that on another machine, with only one 
logical volume for /,
and one for /home, /var/log/messages gets its two lines, but the system boots 
properly...

you might notice I presently run a 2.4.27-1-686, this is my rescue that I had a 
hard time to setup
when the problem first happend to me with the last update of 2.4.27-1-868,
which really hang the computer, having overwritten my working kernel.
(that did not happen this time because of the -1-686 to -2-686 move)

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages kernel-image-2.4.27-2-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  fileutils 5.2.1-2The GNU file management utilities 
ii  initrd-tools  0.1.76 tools to create initrd image for p
ii  modutils  2.4.26-1.2 Linux module utilities

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291127: Please fix for sarge

[Thomas Hood]

Please note that it would be good if this patch were applied to the 2.6
kernel that releases with sarge; otherwise users of sarge may encounter
bug #288423.

-- 
Thomas Hood <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291375: initrd-tools for Debian are one big mess

[Christoph Hellwig]

Complete agreement here.  We're still looking for a volunteer, though
;-)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291375: initrd-tools for Debian are one big mess

[Bozhan Boiadzhiev]

Package: initrd-tools
Version: 0.1.76
Severity: wishlist


If someone ever tried initrd tools for debian and red hat
you'l find a "little" difference .
With red hat tools you can do whatever you want and to customize 
initrd image the way you want very easy.
IN other way the dabian mkinitrd is very bad documented, can't do
most of the things for more complex operation or isn't documented how to 
do this operations. 
So my suggestion is ... get red hat initrd-tools and make them work in
debian and drop current initrd-tools OR make this thing works as it works 
in Red Hat .
This my opinion is based on my battle for crating initrd image for
booting strange raid controler  ITE8212f and complains from my friend
that he can't make initrd image to boot from USB Ffash memory with
debian but there isn't ANY problems with redhat.
And wow there are so many bug about initrd-tools.
I think debian kernel development team have to take this things very
seriosly.

Sorry for bad english and this is only my opinion.
It is possible that i am wrong:)

Thanks

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages initrd-tools depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  cpio  2.5-1.1GNU cpio -- a program to manage ar
ii  cramfsprogs   1.1-6  Tools for CramFs (Compressed ROM F
ii  dash  0.5.1-3The Debian Almquist Shell
ii  fileutils 5.2.1-2The GNU file management utilities 
ii  util-linux2.12-10Miscellaneous system utilities

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: abi 1 to abi 2

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 269823 kernel-image-2.4.27-2-386
Bug#269823: hpt366 module makes ide drive not show up in /dev/discs/ (devfs) 
until manually accessed
Warning: Unknown package 'kernel-image-2.4.27-1-386'
Bug reassigned from package `kernel-image-2.4.27-1-386' to 
`kernel-image-2.4.27-2-386'.

> reassign 280480 kernel-image-2.4.27-2-586tsc
Bug#280480: kernel-image-2.4.27-1-586tsc: No suitable image for Via C3
Warning: Unknown package 'kernel-image-2.4.27-1-586tsc'
Bug reassigned from package `kernel-image-2.4.27-1-586tsc' to 
`kernel-image-2.4.27-2-586tsc'.

> reassign 269383 kernel-image-2.4.27-2-686-smp:
Bug#269383: kernel-image-2.4.27-1-686: Problem with devicemapper.
Warning: Unknown package 'kernel-image-2.4.27-1-686-smp'
Bug reassigned from package `kernel-image-2.4.27-1-686-smp' to 
`kernel-image-2.4.27-2-686-smp:'.

> reassign 283167 kernel-image-2.4.27-2-k6
Bug#283167: usb: raced timeout
Warning: Unknown package 'kernel-image-2.4.27-1-k6'
Bug reassigned from package `kernel-image-2.4.27-1-k6' to 
`kernel-image-2.4.27-2-k6'.

> reassign 272768 kernel-image-2.4.27-2-k7
Bug#272768: USB device detection broken in latest kernels version 2.4.26 and 
2.4.27
Warning: Unknown package 'kernel-image-2.4.27-1-k7'
Bug reassigned from package `kernel-image-2.4.27-1-k7' to 
`kernel-image-2.4.27-2-k7'.

> reassign 276109 kernel-image-2.4.27-2-k7
Bug#276109: kernel-image-2.4.27-1-k7: oops with NFS
Warning: Unknown package 'kernel-image-2.4.27-1-k7'
Bug reassigned from package `kernel-image-2.4.27-1-k7' to 
`kernel-image-2.4.27-2-k7'.

> reassign 277358 kernel-image-2.4.27-2-k7
Bug#277358: kernel-image-2.4.27-1-k7: cannot mount SCSI LVM at boot
Warning: Unknown package 'kernel-image-2.4.27-1-k7'
Bug reassigned from package `kernel-image-2.4.27-1-k7' to 
`kernel-image-2.4.27-2-k7'.

> reassign 287326 kernel-image-2.4.27-2-k7
Bug#287326: kernel-image-2.4.27-1-k7: IDE disk performance problem
Warning: Unknown package 'kernel-image-2.4.27-1-k7'
Bug reassigned from package `kernel-image-2.4.27-1-k7' to 
`kernel-image-2.4.27-2-k7'.

> reassign 287939 kernel-image-2.4.27-2-k7
Bug#287939: kernel-image-2.4.27-1-k7: synchronisation with a Palm on ttyS0 is 
broken
Warning: Unknown package 'kernel-image-2.4.27-1-k7'
Bug reassigned from package `kernel-image-2.4.27-1-k7' to 
`kernel-image-2.4.27-2-k7'.

> reassign 277579 kernel-image-2.6.8-2-mckinley-smp
Bug#277579: hang in futex_wait()
Warning: Unknown package 'kernel-image-2.6.8-1-mckinley-smp'
Bug reassigned from package `kernel-image-2.6.8-1-mckinley-smp' to 
`kernel-image-2.6.8-2-mckinley-smp'.

> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: kernel-image-2.4.27-1-686 -> kernel-image-2.4.27-2-686

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 266872 kernel-image-2.4.27-2-686
Bug#266872: ohci1394 doesn't load this `Ricoh Co Ltd R5C552 IEEE 1394 
Controller'
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 269560 kernel-image-2.4.27-2-686
Bug#269560: kernel-2.4.27 bug in r8169 driver
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 271090 kernel-image-2.4.27-2-686
Bug#271090: kernel-image-2.6.7-1-686: scsi dump 0 > /proc/scsi/scsi
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 275938 kernel-image-2.4.27-2-686
Bug#275938: kernel-image-2.4.27-1-686: Terrible realtime performance
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 283653 kernel-image-2.4.27-2-686
Bug#283653: kernel-image-2.4.27-1-686: Unable to handle kernel NULL pointer 
dereference
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 285017 kernel-image-2.4.27-2-686
Bug#285017: kernel-image-2.4.27-1-686: upgrading from v2 to v6 slows down my 
modem
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 285521 kernel-image-2.4.27-2-686
Bug#285521: kernel-image-2.4.27-1: kernel-image-2.4.27-1 v6: thinkpad does not 
suspend upon lid closing
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 288272 kernel-image-2.4.27-2-686
Bug#288272: kernel-image-2.4.27-1-686: Very slow on Tecra 8100
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 288712 kernel-image-2.4.27-2-686
Bug#288712: kernel-image-2.4.27-1-686: power off button on dell d800 does not 
work anymore
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 289517 kernel-image-2.4.27-2-686
Bug#289517: kernel-image-2.4.27-1-686: startup errors
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> reassign 290039 kernel-image-2.4.27-2-686
Bug#290039: 3c59x problems after kernel upgrade from 2.4.27-2 to 2.4.27-6
Warning: Unknown package 'kernel-image-2.4.27-1-686'
Bug reassigned from package `kernel-image-2.4.27-1-686' to 
`kernel-image-2.4.27-2-686'.

> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291357: kernel-source-2.4.27: SIGHUP not being sent when controlling process exits

[Russell Stuart]

Package: kernel-source-2.4.27
Version: 2.4.27-6
Severity: important



-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-6-lube-686-smp
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages kernel-source-2.4.27 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-1A high-quality block-sorting file 
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

-- no debconf information

drivers/char/tty_io.c, line 768, contains this line:

/* tty_deferred_ldisc_switch(N_TTY);

Note: no trailing "*/".  I am not sure what was intended here,
but the net result is to comment out the code that sends a
SIGHUP to child processed when their leader exits.

This is bad, real bad.  This means that after:

login: me
$ sleep 1000
$ exit

sleep still runs.  The errant patch is in
093_tty_lockup.diff.bz2.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#291354: kernel-image-2.6.10-1-686: Clock is running too fast under Suspend to RAM.

[Mike Hommey]

Package: kernel-image-2.6.10-1-686
Version: 2.6.10-4
Severity: normal

Preliminary note: this didn't happen with 2.6.9.

When suspending to RAM for a quite long time (like, the whole night),
at wake up time, the clock is far ahead. It seems to be running twice as
fast, actually, because it was 10 hours ahead this morning, after
roughly 10 hours of suspend to RAM...


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)

Versions of packages kernel-image-2.6.10-1-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  initrd-tools  0.1.76 tools to create initrd image for p
ii  module-init-tools 3.1-rel-2  tools for managing Linux kernel mo

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: lack of support for specific hardware is not RC

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 291348 important
Bug#291348: kernel-image-2.6.8: SiS USB 1.0 Controller Fails in Bulk Transport 
with, 2.6.8, fixed in 2.6.10
Severity set to `important'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kernel abiname transition and security updates status

[Horms]

On Fri, Jan 14, 2005 at 08:41:26PM +0900, Horms wrote:
> On Thu, Jan 13, 2005 at 04:24:36PM +0900, Horms wrote:
> > On Mon, Jan 10, 2005 at 10:27:20PM +, Martin Michlmayr wrote:
> > > * Joey Hess <[EMAIL PROTECTED]> [2005-01-10 16:24]:
> > > > As far as I know, no other arches except amd64 (not tracking
> > > > that) are
> > > 
> > > mips and mipsel have been updated.  However, given the new local
> > > root exploit (fixed in SVN), we'll all need to make another round
> > > of updates anyway.
> > 
> > Josh Kwan and I chatted about this yesterday on IRC.  He and I are
> > both pretty happy with kernel-source-2.4.27 as it is, but I would
> > like a chance to go through recent bug reports just to make sure
> > there isn't anything missing. As a result we are aiming to release
> > next week.

Sorry for this taking a bit longer than I had hoped.  I now have
kernel-source-2.4.27 in a state where I am happy to release it as
2.4.27-8. 

I have made both kernel-source-2.4.27 and kernel-image-2.4.27-i386 up on
http://debian.vergenet.net/pending/ for people to take a look at.

I aim to releaase these verbatim tomorrow if there are no objections. If
you make an updates to SVN please drop me an email, so I make sure that
they make it in. As I am not intending to rebuild again. If you put
[EMAIL PROTECTED] in To or CC then it will go to the top of my
mail-reading priority list.

-- 
Horms


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]