Bug#642154: BUG: unable to handle kernel paging request at ffff8803bb6ad000

2011-09-20 Thread rush
Hi,

There are several Not tainted lines in old messages file. There are all of them:

Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm:
debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation
S1200BTL/S1200BTL
Sep 10 22:35:33 xen-dom0 kernel: [24183.985621] RIP:
e030:[810106db]  [810106db]
__sanitize_i387_state+0x23/0xe1
Sep 10 22:35:33 xen-dom0 kernel: [24183.985716] RSP:
e02b:8803bd2c5e00  EFLAGS: 00010246
Sep 10 22:35:33 xen-dom0 kernel: [24183.985767] RAX: 
RBX: 7fff3d69ecc0 RCX: 0200
Sep 10 22:35:33 xen-dom0 kernel: [24183.985824] RDX: 8803be0e8e00
RSI: 8803bd2c5fd8 RDI: 8803bd65aa30
Sep 10 22:35:33 xen-dom0 kernel: [24183.985882] RBP: 8803bd65aa30
R08:  R09: 0002
Sep 10 22:35:33 xen-dom0 kernel: [24183.985939] R10: 000156c1
R11: 0246 R12: 
Sep 10 22:35:33 xen-dom0 kernel: [24183.985997] R13: 
R14: 8803bd65aa30 R15: 7fff3d69ecc0
Sep 10 22:35:33 xen-dom0 kernel: [24183.986056] FS:
7fd34091b700() GS:8803d61f1000()
knlGS:
Sep 10 22:35:33 xen-dom0 kernel: [24183.986144] CS:  e033 DS:  ES:
 CR0: 8005003b
Sep 10 22:35:33 xen-dom0 kernel: [24183.986197] CR2: 8803be0e9000
CR3: 0003bc19b000 CR4: 2660
Sep 10 22:35:33 xen-dom0 kernel: [24183.986255] DR0: 
DR1:  DR2: 
Sep 10 22:35:33 xen-dom0 kernel: [24183.986312] DR3: 
DR6: 0ff0 DR7: 0400
Sep 10 22:35:33 xen-dom0 kernel: [24183.986370] Process debootstrap
(pid: 2605, threadinfo 8803bd2c4000, task 8803bd65aa30)
Sep 10 22:35:33 xen-dom0 kernel: [24183.986500]  81010919
7fff3d69ef90 8803bd2c5f58 0011
Sep 10 22:35:33 xen-dom0 kernel: [24183.986606]  8803bd65aec0
 81008fdd 810459d6
Sep 10 22:35:33 xen-dom0 kernel: [24183.986713]  7fff3d69eaf8
0011 00040001 0a2e
Sep 10 22:35:33 xen-dom0 kernel: [24183.986864]  [81010919]
? save_i387_xstate+0x102/0x1f3
Sep 10 22:35:33 xen-dom0 kernel: [24183.986919]  [81008fdd]
? do_signal+0x212/0x649
Sep 10 22:35:33 xen-dom0 kernel: [24183.986972]  [810459d6]
? copy_process+0x108f/0x10eb
Sep 10 22:35:33 xen-dom0 kernel: [24183.987026]  [81009450]
? do_notify_resume+0x25/0x6b
Sep 10 22:35:33 xen-dom0 kernel: [24183.987082]  [8133bfe0]
? int_signal+0x12/0x17
Sep 10 22:35:33 xen-dom0 kernel: [24183.987737]  RSP 8803bd2c5e00
Sep 10 22:35:33 xen-dom0 kernel: [24183.988232] ---[ end trace
031dc278e15801af ]---


Sep 11 12:55:02 xen-dom0 kernel: [  398.590259] Pid: 2842, comm: forks
Not tainted 3.0.0-1-amd64 #1 Intel Corporation S1200BTL/S1200BTL
Sep 11 12:55:02 xen-dom0 kernel: [  398.590591] RIP:
e030:[810106db]  [810106db]
__sanitize_i387_state+0x23/0xe1
Sep 11 12:55:02 xen-dom0 kernel: [  398.590799] RSP:
e02b:8803be7c3e00  EFLAGS: 00010246
Sep 11 12:55:02 xen-dom0 kernel: [  398.590905] RAX: 
RBX: 7fff1f25e7c0 RCX: 0200
Sep 11 12:55:02 xen-dom0 kernel: [  398.591018] RDX: 8803bbd42e00
RSI: 8803be7c3fd8 RDI: 8803bcbaee20
Sep 11 12:55:02 xen-dom0 kernel: [  398.591130] RBP: 8803bcbaee20
R08: 8803be7c2000 R09: 81684640
Sep 11 12:55:02 xen-dom0 kernel: [  398.591243] R10: 7fc94d5dd9d0
R11: 0246 R12: 
Sep 11 12:55:02 xen-dom0 kernel: [  398.591355] R13: 
R14: 8803bcbaee20 R15: 7fff1f25e7c0
Sep 11 12:55:02 xen-dom0 kernel: [  398.591471] FS:
7fc94d5dd700() GS:8803d616a000()
knlGS:
Sep 11 12:55:02 xen-dom0 kernel: [  398.591614] CS:  e033 DS:  ES:
 CR0: 8005003b
Sep 11 12:55:02 xen-dom0 kernel: [  398.591721] CR2: 8803bbd43000
CR3: 0003bd18d000 CR4: 2660
Sep 11 12:55:02 xen-dom0 kernel: [  398.591833] DR0: 
DR1:  DR2: 
Sep 11 12:55:02 xen-dom0 kernel: [  398.591945] DR3: 
DR6: 0ff0 DR7: 0400
Sep 11 12:55:02 xen-dom0 kernel: [  398.592059] Process forks (pid:
2842, threadinfo 8803be7c2000, task 8803bcbaee20)
Sep 11 12:55:02 xen-dom0 kernel: [  398.592296]  81010919
00413201 8803be7c3f58 0011
Sep 11 12:55:02 xen-dom0 kernel: [  398.592684]  8803bcbaf2b0
 81008fdd 
Sep 11 12:55:02 xen-dom0 kernel: [  398.593071]  7fff1f25e5f8
0011 00040001 fffe0b1b
Sep 11 12:55:02 xen-dom0 kernel: [  398.593559]  [81010919]
? save_i387_xstate+0x102/0x1f3
Sep 11 12:55:02 xen-dom0 kernel: [  398.593668]  [81008fdd]
? do_signal+0x212/0x649
Sep 11 12:55:02 xen-dom0 kernel: [  398.593776]  [81009450]
? do_notify_resume+0x25/0x6b
Sep 11 12:55:02 xen-dom0 kernel: [  

Bug#642140: New LVM volumes stop appearing in /dev/ when chromium is running

2011-09-20 Thread Enrico Zini
On Mon, Sep 19, 2011 at 04:08:30PM -0500, Jonathan Nieder wrote:

 # ebf4127cd677 (kobj_uevent: Ignore if some listeners cannot handle message,
 # 2011-08-22), which is in the driver-core tree and hence in linux-next (but
 # not in linus's tree yet).
 tags 642140 + upstream patch
 forwarded 642140 
 http://thread.gmane.org/gmane.linux.kernel/1180877/focus=1182353
 quit

Hello,

James Vega let me know of 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641661
of which this 642140 looks like a duplicate.


Ciao,

Enrico

-- 
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini enr...@enricozini.org


signature.asc
Description: Digital signature


Bug#488665: closed by Jonathan Nieder jrnie...@gmail.com (Re: linux-image-2.6.25-2-686: cannot pass multiple arguments in #! line)

2011-09-20 Thread Michal Suchanek
Excerpts from Debian Bug Tracking System's message of Mon Sep 12 04:06:03 +0200 
2011:
 This is an automatic notification regarding your Bug report
 which was filed against the linux-2.6 package:
 
 #488665: linux-image-2.6.25-2-686: cannot pass multiple arguments in #! line
 
 It has been closed by Jonathan Nieder jrnie...@gmail.com.
 
 Their explanation is attached below along with your original report.
 If this explanation is unsatisfactory and you have not received a
 better one in a separate message then please contact Jonathan Nieder 
 jrnie...@gmail.com by
 replying to this email.
 
 Hi Michal,
 
 Michal Suchanek wrote:
 
  When running script which has multiple arguments in the #! line the
  arguments are joined into one. This breaks scripts that require multiple
  arguments passed to the interpreter.
 [...]
  Observed output of the script:
  ./test|-a -b -c|./test.sh
 
  Expected outout of the script:
  ./test|-a|-b|-c|./test.sh
 
 Sorry for the long silence.  This is a longstanding behavior and,
 roughly speaking, by design.  See [1] and the surrounding thread for
 some context.
 
 I actually wouldn't mind if someone raises this upstream again.  I
 don't think it's worth tracking in Debian, though, hence closing the
 bug.
 
 Thanks,
 Jonathan
 
 [1] http://thread.gmane.org/gmane.linux.kernel/182403/focus=184600

It comes at somewhat unfortunate time kernel.org being down and taking
quite some time to get back up.

Thanks for  the reference.
Interesting and somewhat sad reading :-s

Michal



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1316519577-sup-9...@virtual.ruk.cuni.cz



Processed: tagging 642005

2011-09-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 642005 + upstream wontfix
Bug #642005 [linux-2.6] general: maximum size of SHM memory blocks to low
Added tag(s) upstream and wontfix.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
642005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.131652083627262.transcr...@bugs.debian.org



Bug#642154: BUG: unable to handle kernel paging request at ffff8803bb6ad000

2011-09-20 Thread Ben Hutchings
On Tue, 2011-09-20 at 10:12 +0400, rush wrote:
 Hi,
 
 There are several Not tainted lines in old messages file. There are all of 
 them:
 
 Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm:
 debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation
 S1200BTL/S1200BTL
 Sep 10 22:35:33 xen-dom0 kernel: [24183.985621] RIP:
 e030:[810106db]  [810106db]
 __sanitize_i387_state+0x23/0xe1

Source/disassembly:

void __sanitize_i387_state(struct task_struct *tsk)
{
u64 xstate_bv;
int feature_bit = 0x2;
struct i387_fxsave_struct *fx = tsk-thread.fpu.state-fxsave;
810106b8:   48 8b 97 48 04 00 00mov0x448(%rdi),%rdx

if (!fx)
return;
810106bf:   48 85 d2test   %rdx,%rdx
810106c2:   0f 84 d0 00 00 00   je 0x81010798

BUG_ON(task_thread_info(tsk)-status  TS_USEDFPU);
810106c8:   48 8b 47 08 mov0x8(%rdi),%rax
810106cc:   f6 40 14 01 testb  $0x1,0x14(%rax)
810106d0:   74 02   je 0x810106d4
810106d2:   0f 0b   ud2

xstate_bv = tsk-thread.fpu.state-xsave.xsave_hdr.xstate_bv;
810106db:   48 8b b2 00 02 00 00mov0x200(%rdx),%rsi

So tsk-thread.fpu.state in RDX seems to be invalid.

 Sep 10 22:35:33 xen-dom0 kernel: [24183.985716] RSP:
 e02b:8803bd2c5e00  EFLAGS: 00010246
 Sep 10 22:35:33 xen-dom0 kernel: [24183.985767] RAX: 
 RBX: 7fff3d69ecc0 RCX: 0200
 Sep 10 22:35:33 xen-dom0 kernel: [24183.985824] RDX: 8803be0e8e00
 RSI: 8803bd2c5fd8 RDI: 8803bd65aa30
[...]

RDX looks like a reasonable kernel memory pointer.  Given the hostname,
I assume this kernel is running under Xen.  So could this be a
use-after-free where the freed page has been unmapped for reallocation
by the hypervisor?  Can that happen to arbitrary pages in the dom0
kernel?

Ben.

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


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


Bug#642154: BUG: unable to handle kernel paging request at ffff8803bb6ad000

2011-09-20 Thread Ian Campbell
On Tue, 2011-09-20 at 14:20 +0100, Ben Hutchings wrote:
 On Tue, 2011-09-20 at 10:12 +0400, rush wrote:
  Hi,
  
  There are several Not tainted lines in old messages file. There are all of 
  them:
  
  Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm:
  debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation
  S1200BTL/S1200BTL
  Sep 10 22:35:33 xen-dom0 kernel: [24183.985621] RIP:
  e030:[810106db]  [810106db]
  __sanitize_i387_state+0x23/0xe1
 
 Source/disassembly:
 
 void __sanitize_i387_state(struct task_struct *tsk)
 {
   u64 xstate_bv;
   int feature_bit = 0x2;
   struct i387_fxsave_struct *fx = tsk-thread.fpu.state-fxsave;
 810106b8:   48 8b 97 48 04 00 00mov0x448(%rdi),%rdx
 
   if (!fx)
   return;
 810106bf:   48 85 d2test   %rdx,%rdx
 810106c2:   0f 84 d0 00 00 00   je 0x81010798
 
   BUG_ON(task_thread_info(tsk)-status  TS_USEDFPU);
 810106c8:   48 8b 47 08 mov0x8(%rdi),%rax
 810106cc:   f6 40 14 01 testb  $0x1,0x14(%rax)
 810106d0:   74 02   je 0x810106d4
 810106d2:   0f 0b   ud2
 
   xstate_bv = tsk-thread.fpu.state-xsave.xsave_hdr.xstate_bv;
 810106db:   48 8b b2 00 02 00 00mov0x200(%rdx),%rsi
 
 So tsk-thread.fpu.state in RDX seems to be invalid.
 
  Sep 10 22:35:33 xen-dom0 kernel: [24183.985716] RSP:
  e02b:8803bd2c5e00  EFLAGS: 00010246
  Sep 10 22:35:33 xen-dom0 kernel: [24183.985767] RAX: 
  RBX: 7fff3d69ecc0 RCX: 0200
  Sep 10 22:35:33 xen-dom0 kernel: [24183.985824] RDX: 8803be0e8e00
  RSI: 8803bd2c5fd8 RDI: 8803bd65aa30
 [...]
 
 RDX looks like a reasonable kernel memory pointer.  Given the hostname,
 I assume this kernel is running under Xen.  So could this be a
 use-after-free where the freed page has been unmapped for reallocation
 by the hypervisor?  Can that happen to arbitrary pages in the dom0
 kernel?

In a modern pvops kernel there is a tendency towards leaving a page of
actual dom0 memory behind in these cases, rather than a hole. A page
with no backing mfn should never be escaping into the wild anyway but
it's possible fir a given process to see one if it is doing hypercall
activities, mapping foreign pages etc.

There's been some similar looking threads on xen-devel recently but I
haven't paid attention to the details, list  Konrad CC'd. Full log is
at http://bugs.debian.org/642154.

 
 Ben.
 

-- 
Ian Campbell

Everybody has something to conceal.
-- Humphrey Bogart




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1316526058.3891.65.ca...@zakaz.uk.xensource.com



Processed: Re: New LVM volumes stop appearing in /dev/ when chromium is running

2011-09-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 forcemerge 642140 641661
Bug#642140: New LVM volumes stop appearing in /dev/ when chromium is running
Bug#641661: linux-image-3.0.0-1-686-pae: semid XX: semop failed for cookie 
0xdeadbeef: incorrect semaphore state when using lvm
Forcibly Merged 641661 642140.


End of message, stopping processing here.

Please contact me if you need assistance.
-- 
641661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641661
642140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.131652653623767.transcr...@bugs.debian.org



Bug#642140: New LVM volumes stop appearing in /dev/ when chromium is running

2011-09-20 Thread Jonathan Nieder
Enrico Zini wrote:

 James Vega let me know of 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641661
 of which this 642140 looks like a duplicate.

Thanks, merged (you can do the same, you know :)).



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110920142654.GB7517@elie



Bug#603061: marked as done (sata error msgs when activating ALPM)

2011-09-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Sep 2011 09:34:19 -0500
with message-id 20110920143419.GD7517@elie
and subject line Re: laptop-mode-tools: Errormessages when activating 
intel-sata-powermgmt
has caused the Debian Bug report #603061,
regarding sata error msgs when activating ALPM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
603061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: laptop-mode-tools
Version: 1.55-1
Severity: normal

When I activate intel-sata-powermgmt and plug/unplug ac things like this get 
appended to the syslog:

Nov 10 19:00:18 baghdad kernel: [ 3578.973665] ata1.00: exception Emask 0x10 
SAct 0x1 SErr 0x5 action 0xe frozen
Nov 10 19:00:18 baghdad kernel: [ 3578.975845] ata1.00: irq_stat 0x0040, 
PHY RDY changed
Nov 10 19:00:18 baghdad kernel: [ 3578.978117] ata1: SError: { PHYRdyChg 
CommWake }
Nov 10 19:00:18 baghdad kernel: [ 3578.980314] ata1.00: failed command: WRITE 
FPDMA QUEUED
Nov 10 19:00:18 baghdad kernel: [ 3578.982505] ata1.00: cmd 
61/08:00:18:8a:cc/00:00:0a:00:00/40 tag 0 ncq 4096 out
Nov 10 19:00:18 baghdad kernel: [ 3578.982507]  res 
40/00:04:18:8a:cc/00:00:0a:00:00/40 Emask 0x10 (ATA bus error)
Nov 10 19:00:18 baghdad kernel: [ 3578.987070] ata1.00: status: { DRDY }
Nov 10 19:00:18 baghdad kernel: [ 3578.989333] ata1: hard resetting link
Nov 10 19:00:18 baghdad kernel: [ 3579.713083] ata1: SATA link up 1.5 Gbps 
(SStatus 113 SControl 300)
Nov 10 19:00:18 baghdad kernel: [ 3579.713965] ata1.00: ACPI cmd 
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Nov 10 19:00:18 baghdad kernel: [ 3579.713975] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Nov 10 19:00:18 baghdad kernel: [ 3579.713983] ata1.00: ACPI cmd 
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Nov 10 19:00:19 baghdad kernel: [ 3579.757081] ata1.00: ACPI cmd 
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Nov 10 19:00:19 baghdad kernel: [ 3579.757091] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Nov 10 19:00:19 baghdad kernel: [ 3579.757100] ata1.00: ACPI cmd 
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Nov 10 19:00:19 baghdad kernel: [ 3579.757987] ata1.00: configured for UDMA/133
Nov 10 19:00:19 baghdad kernel: [ 3579.759931] ata1.00: configured for UDMA/133
Nov 10 19:00:19 baghdad kernel: [ 3579.759948] ata1: EH complete

The upper part is also prompted on the console.
My Laptop is a Thinkpad x60s.

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

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

Versions of packages laptop-mode-tools depends on:
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init scrip
ii  psmisc22.11-1utilities that use the proc file s
ii  util-linux2.17.2-3.3 Miscellaneous system utilities

Versions of packages laptop-mode-tools recommends:
ii  acpid 1:2.0.6-1  Advanced Configuration and Power I
ii  apmd  3.2.2-14   Utilities for Advanced Power Manag
ii  ethtool   1:2.6.34-3 display or change Ethernet device 
pn  hal   none (no description available)
ii  hdparm9.27-2.1   tune hard disk parameters for high
ii  net-tools 1.60-23The NET-3 networking toolkit
ii  pm-utils  1.3.0-2utilities and scripts for power ma
ii  sdparm1.02-1 Output and modify SCSI device para
ii  wireless-tools30~pre9-5  Tools for manipulating Linux Wirel

laptop-mode-tools suggests no packages.

-- Configuration Files:
/etc/laptop-mode/laptop-mode.conf changed:
ENABLE_LAPTOP_MODE_TOOLS=1
VERBOSE_OUTPUT=0
LOG_TO_SYSLOG=1
DEBUG=0
ENABLE_LAPTOP_MODE_ON_BATTERY=1
ENABLE_LAPTOP_MODE_ON_AC=1
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0
ENABLE_AUTO_MODULES=0
MINIMUM_BATTERY_CHARGE_PERCENT=3
DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
HD=/dev/[hs]d[abcdefgh]
PARTITIONS=auto /dev/mapper/*
ASSUME_SCSI_IS_SATA=1
LM_BATT_MAX_LOST_WORK_SECONDS=600
LM_AC_MAX_LOST_WORK_SECONDS=360
CONTROL_READAHEAD=1
LM_READAHEAD=3072
NOLM_READAHEAD=128
CONTROL_NOATIME=0
USE_RELATIME=1
CONTROL_HD_IDLE_TIMEOUT=1
LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
NOLM_HD_IDLE_TIMEOUT_SECONDS=7200
CONTROL_HD_POWERMGMT=auto

Bug#603061: sata error msgs when activating ALPM

2011-09-20 Thread Jonathan Nieder
reopen 603061
notfixed 603061 2.6.32-35squeeze2
tags 603061 + moreinfo
quit

Jonathan Nieder wrote:

 Version: 2.6.32-35squeeze2

 Johan Kröckel wrote:

 Hi Jonathan,
 I used the backported Kernel and the wheezy version of
 laptop-mode-tools for some time. Now, with the squeeze-versions, I
 can't retrace it.

 Thanks; that's good to hear.

Err, sorry for the misreading.  Which kernel versions, precisely, have
you tested, and what is the result produced by each?  Does the latest
kernel in squeeze still reproduce this?



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110920144253.GF7517@elie



Processed: Re: sata error msgs when activating ALPM

2011-09-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reopen 603061
Bug #603061 {Done: Jonathan Nieder jrnie...@gmail.com} [linux-2.6] sata error 
msgs when activating ALPM
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
 notfixed 603061 2.6.32-35squeeze2
Bug #603061 [linux-2.6] sata error msgs when activating ALPM
There is no source info for the package 'linux-2.6' at version 
'2.6.32-35squeeze2' with architecture ''
Unable to make a source version for version '2.6.32-35squeeze2'
Ignoring request to alter fixed versions of bug #603061 to the same values 
previously set
 tags 603061 + moreinfo
Bug #603061 [linux-2.6] sata error msgs when activating ALPM
Added tag(s) moreinfo.
 quit
Stopping processing here.

Please contact me if you need assistance.
-- 
603061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13165297868427.transcr...@bugs.debian.org



Bug#642235: linux-2.6: LVM deadlocks and oops

2011-09-20 Thread Hector Oron
Package: linux-2.6
Version: 3.1.0-rc6
Severity: normal
Tags: upstream

Hello,

  While playing with sbuild to build packages on armhf buildd running an
  upstream patched kernel for i.MX53 LOCO boards (next armhf build daemons).

  I have hit a deadlock and oops on LVM, so I think it is worth it to
  document the problem here and maybe it can get fixed.

[74093.782238] kjournald starting.  Commit interval 5 seconds
[74093.821968] EXT3-fs (dm-4): using internal journal
[74093.826917] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[74397.131757] kjournald starting.  Commit interval 5 seconds
[74397.169996] EXT3-fs (dm-4): using internal journal
[74397.174838] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[76601.907689] kjournald starting.  Commit interval 5 seconds
[76601.945944] EXT3-fs (dm-4): using internal journal
[76601.950779] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[76656.111857] kjournald starting.  Commit interval 5 seconds
[76656.150092] EXT3-fs (dm-4): using internal journal
[76656.154937] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[76793.872136] kjournald starting.  Commit interval 5 seconds
[76793.910358] EXT3-fs (dm-4): using internal journal
[76793.915200] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[84651.608193] kjournald starting.  Commit interval 5 seconds
[84651.646426] EXT3-fs (dm-4): using internal journal
[84651.651269] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[84738.700610] 
[84738.700625] ===
[84738.708389] [ INFO: possible circular locking dependency detected ]
[84738.714663] 3.1.0-rc6 #4
[84738.717197] ---
[84738.723467] lvcreate/9492 is trying to acquire lock:
[84738.728435]  (md-suspend_lock){+.+...}, at: [c02c73c4] 
dm_suspend+0x28/0x29c
[84738.735894] 
[84738.735897] but task is already holding lock:
[84738.741740]  (journal-j_barrier){+.+...}, at: [c01481c4] 
journal_lock_updates+0xf0/0xfc
[84738.750141] 
[84738.750145] which lock already depends on the new lock.
[84738.750150] 
[84738.758344] 
[84738.758346] the existing dependency chain (in reverse order) is:
[84738.765839] 
[84738.765842] - #1 (journal-j_barrier){+.+...}:
[84738.771981][c0052114] check_prev_add+0x338/0x680
[84738.777492][c0052e4c] validate_chain+0x4f4/0x674
[84738.782993][c0053714] __lock_acquire+0x748/0x828
[84738.788496][c0053a28] lock_release_non_nested+0x234/0x2bc
[84738.794780][c0053b98] __lock_release+0xe8/0x1cc
[84738.800195][c0053cdc] lock_release+0x60/0x70
[84738.805348][c04636d4] __mutex_unlock_slowpath+0xd4/0x13c
[84738.811551][c046374c] mutex_unlock+0x10/0x14
[84738.816705][c00c9434] freeze_bdev+0x9c/0xa4
[84738.821783][c02c7438] dm_suspend+0x9c/0x29c
[84738.826850][c02cc06c] dev_suspend+0x5c/0x90
[84738.831921][c02ccdd4] ctl_ioctl+0x228/0x2c8
[84738.836990][c02cce8c] dm_ctl_ioctl+0x18/0x1c
[84738.842145][c00a9fa4] do_vfs_ioctl+0x33c/0x38c
[84738.847483][c00aa034] sys_ioctl+0x40/0x64
[84738.852378][c000dfc0] ret_fast_syscall+0x0/0x3c
[84738.857801] 
[84738.857804] - #0 (md-suspend_lock){+.+...}:
[84738.863769][c0051c78] print_circular_bug+0x5c/0xfc
[84738.869445][c0051f10] check_prev_add+0x134/0x680
[84738.874947][c0052e4c] validate_chain+0x4f4/0x674
[84738.880450][c0053714] __lock_acquire+0x748/0x828
[84738.885952][c0053d78] lock_acquire+0x8c/0xa0
[84738.891107][c04643a8] mutex_lock_nested+0x74/0x30c
[84738.896784][c02c73c4] dm_suspend+0x28/0x29c
[84738.901851][c02cc06c] dev_suspend+0x5c/0x90
[84738.906920][c02ccdd4] ctl_ioctl+0x228/0x2c8
[84738.911988][c02cce8c] dm_ctl_ioctl+0x18/0x1c
[84738.917143][c00a9fa4] do_vfs_ioctl+0x33c/0x38c
[84738.922472][c00aa034] sys_ioctl+0x40/0x64
[84738.927367][c000dfc0] ret_fast_syscall+0x0/0x3c
[84738.932783] 
[84738.932786] other info that might help us debug this:
[84738.932791] 
[84738.940814]  Possible unsafe locking scenario:
[84738.940819] 
[84738.946747]CPU0CPU1
[84738.951280]
[84738.955810]   lock(journal-j_barrier);
[84738.959757]lock(md-suspend_lock);
[84738.966049]lock(journal-j_barrier);
[84738.972515]   lock(md-suspend_lock);
[84738.976287] 
[84738.976290]  *** DEADLOCK ***
[84738.976293] 
[84738.982232] 1 lock held by lvcreate/9492:
[84738.986243]  #0:  (journal-j_barrier){+.+...}, at: [c01481c4] 
journal_lock_updates+0xf0/0xfc
[84738.995085] 
[84738.995088] stack backtrace:
[84738.999455] Backtrace: 
[84739.001928] [c00114e0] (dump_backtrace+0x0/0x110) from [c04624e0] 
(dump_stack+0x18/0x1c)
[84739.010372]  r7:dee6f908 r6:dee6f920 r5: r4:
[84739.016090] [c04624c8] (dump_stack+0x0/0x1c) 

Bug#642235: linux-2.6: LVM deadlocks and oops

2011-09-20 Thread Ben Hutchings
On Tue, Sep 20, 2011 at 05:28:49PM +0100, Hector Oron wrote:
 Package: linux-2.6
 Version: 3.1.0-rc6
 Severity: normal
 Tags: upstream
 
 Hello,
 
   While playing with sbuild to build packages on armhf buildd running an
   upstream patched kernel for i.MX53 LOCO boards (next armhf build daemons).
 
   I have hit a deadlock and oops on LVM, so I think it is worth it to
   document the problem here and maybe it can get fixed.
[...]
 
Please add the 'forwarded' reference.

Ben.

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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110920172703.go2...@decadent.org.uk



Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression

2011-09-20 Thread ael
On Tue, Sep 20, 2011 at 09:38:04PM +0200, Bart Hartgers wrote:
  Hope something here gives a clue...
 
 Alas, no. As far as I can tell, the hardware is correctly setup to do
 9600N8 without rtscts handshaking. Nothing in the log about a failing
 transmit, so it seems that gpsbabel's command goes out to the device,
 but somehow nothing is received in response.

I am now worrying that the garmin connector was not making proper
contact. I will try and test again tomorrow, first on the old kernel
so that I am sure there is a good connection, and then try again on
3.0.nnn. But I suspect that it was making contact: I tried to check
carefully, although that is not always reliable.

 I'll try to see if my
 3116 still works with a 3.0 kernel, hopefully tomorrow. Maybe that
 brings us further.

Thanks again,

ael




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110920195937.GA2896@elf.conquest



firmware-nonfree_0.28+squeeze1_i386.changes ACCEPTED into proposed-updates

2011-09-20 Thread Debian FTP Masters


Notes:
Mapping stable to proposed-updates.


Accepted:
firmware-atheros_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-atheros_0.28+squeeze1_all.deb
firmware-bnx2_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-bnx2_0.28+squeeze1_all.deb
firmware-bnx2x_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-bnx2x_0.28+squeeze1_all.deb
firmware-brcm80211_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-brcm80211_0.28+squeeze1_all.deb
firmware-intelwimax_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-intelwimax_0.28+squeeze1_all.deb
firmware-ipw2x00_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-ipw2x00_0.28+squeeze1_all.deb
firmware-ivtv_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-ivtv_0.28+squeeze1_all.deb
firmware-iwlwifi_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-iwlwifi_0.28+squeeze1_all.deb
firmware-linux-nonfree_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-linux-nonfree_0.28+squeeze1_all.deb
firmware-linux_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-linux_0.28+squeeze1_all.deb
firmware-netxen_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-netxen_0.28+squeeze1_all.deb
firmware-nonfree_0.28+squeeze1.dsc
  to non-free/f/firmware-nonfree/firmware-nonfree_0.28+squeeze1.dsc
firmware-nonfree_0.28+squeeze1.tar.gz
  to non-free/f/firmware-nonfree/firmware-nonfree_0.28+squeeze1.tar.gz
firmware-qlogic_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-qlogic_0.28+squeeze1_all.deb
firmware-ralink_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-ralink_0.28+squeeze1_all.deb
firmware-realtek_0.28+squeeze1_all.deb
  to non-free/f/firmware-nonfree/firmware-realtek_0.28+squeeze1_all.deb


Override entries for your package:
firmware-atheros_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-bnx2_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-bnx2x_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-brcm80211_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-intelwimax_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-ipw2x00_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-ivtv_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-iwlwifi_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-linux-nonfree_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-linux_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-netxen_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-nonfree_0.28+squeeze1.dsc - source non-free/kernel
firmware-qlogic_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-ralink_0.28+squeeze1_all.deb - optional non-free/kernel
firmware-realtek_0.28+squeeze1_all.deb - optional non-free/kernel

Announcing to debian-chan...@lists.debian.org


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1r66ql-0004ho...@franck.debian.org



Bug#524438: marked as done (cifs: Crash (OOPS or restart) when accessing Windows ME share with accented sharacters in filenames)

2011-09-20 Thread Debian Bug Tracking System
Your message dated Wed, 21 Sep 2011 01:55:29 +
with message-id e1r6c25-xb...@franck.debian.org
and subject line Bug#524438: fixed in linux-2.6 2.6.26-27
has caused the Debian Bug report #524438,
regarding cifs: Crash (OOPS or restart) when accessing Windows ME share with 
accented sharacters in filenames
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
524438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.26-1-686
Version: 2.6.26-13lenny2
Severity: important



-- Package-specific info:

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-6-k7 (SMP w/1 CPU core)
Locale: LANG=et_EE.iso-8859-15, LC_CTYPE=et_EE.iso-8859-15 
(charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-1-686 depends on:
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92o  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.26-1-686 recommends:
ii  libc6-i6862.7-18 GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.26-1-686 suggests:
ii  grub   0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26   none(no description available)

-- debconf information:
  linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686:
  linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686:
  linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false
  linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true
  linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686:
  linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686:

In Lenny kernel 2.6.26-1-686 I had one OOPS and one restart, when 
trying 
to backup Windows ME computer to my Debian server (using rsync from Debian to 
sync files). Unfortunately, I did not write down OOPS infromation first time 
and 
in second time it just crashed hard. I then reverted to 2.6.18-6-k7 kernel from 
Etch. Then I could run backup, but it reported errors about filenames, with 
accented charactes in filenames (smbfs in Lenny no longer supports codepage 
parameter, which is cause of that problem). So my guess is, that this crash was 
caused by those filenames. Unfortunately I cannot run much test either, because 
it
happened in production server. Windows ME has system codepage set to 775.


---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-27

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

linux-2.6_2.6.26-27.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.26-27.diff.gz
linux-2.6_2.6.26-27.dsc
  to main/l/linux-2.6/linux-2.6_2.6.26-27.dsc
linux-doc-2.6.26_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-27_all.deb
linux-headers-2.6.26-2-all-hppa_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-all-hppa_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-all_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-common_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-27_hppa.deb

Bug#571239: marked as done (linux-image-2.6.26-2-686: CIFS OOPS in cifs:CIFSFindNext+0x174/0x2dc)

2011-09-20 Thread Debian Bug Tracking System
Your message dated Wed, 21 Sep 2011 01:55:29 +
with message-id e1r6c25-xb...@franck.debian.org
and subject line Bug#524438: fixed in linux-2.6 2.6.26-27
has caused the Debian Bug report #524438,
regarding linux-image-2.6.26-2-686: CIFS OOPS in cifs:CIFSFindNext+0x174/0x2dc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
524438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.26-21lenny3
Severity: important

We have a process that periodically checks for files on a cifs mounted
filesystem, using 'find'. The OOPS below occurred and the process got
stuck in 'D' state and was unkillable.

-- Package-specific info:
** Version:
Linux version 2.6.26-2-686 (Debian 2.6.26-21lenny3) (da...@debian.org)
(gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed
Feb 10 08:59:21 UTC 2010

** Command line:
root=/dev/cciss/c0d0p1 ro

** Not tainted

** Kernel log:

[78800.008294] BUG: unable to handle kernel paging request at f800
[78800.008294] IP: [f9082a3f] :cifs:CIFSFindNext+0x174/0x2dc
[78800.008294] *pde = 
[78800.008294] Oops: 0002 [#1] SMP
[78800.008294] Modules linked in: nls_utf8 cifs nls_base sha1_generic
drbd cn iptable_raw xt_comment xt_policy ipt_ULOG ipt_TTL ipt_ttl
ipt_REJECT ipt_REDIRECT ipt_recent ipt_NETMAP ipt_MASQUERADE ipt_LOG
ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp
nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc
nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp
nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink
nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323
nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE
xt_NFLOG xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length
xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack
xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat
nf_nat nf_conntrack_ipv4 nf_conntrack iptable_mangle nfnetlink
iptable_filter ip_tables x_tables ipmi_devintf loop snd_pcm snd_timer
snd soundcore psmouse pcspkr snd_page_alloc serio_raw ipmi_si
ipmi_msghandler hpilo rng_core i5000_edac edac_core container button
shpchp pci_hotplug evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot
dm_mod ide_cd_mod cdrom ata_generic libata dock ide_pci_generic usbhid
hid ff_memless piix ehci_hcd uhci_hcd ide_core usbcore bnx2
firmware_class cciss scsi_mod thermal processor fan thermal_sys [last
unloaded: scsi_wait_scan]
[78800.008294]
[78800.008294] Pid: 23316, comm: find Not tainted (2.6.26-2-686 #1)
[78800.008294] EIP: 0060:[f9082a3f] EFLAGS: 00010282 CPU: 3
[78800.008294] EIP is at CIFSFindNext+0x174/0x2dc [cifs]
[78800.008294] EAX: f7fea400 EBX: c015adf7 ECX: 30051492 EDX: 004f0056
[78800.008294] ESI: f5c63860 EDI: f7fe EBP: f7b0fc94 ESP: f7df9eb8
[78800.008294]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[78800.008294] Process find (pid: 23316, ti=f7df8000 task=f74b7a00
task.ti=f7df8000)
[78800.008294] Stack: c0355c80 f79063c0 000184bc  0003
f7fea400 f7fea400 
[78800.008294]01010096 0098  f909713a f7b0fc94
c017eafc f7df9f94 f75e8e00
[78800.008294]f7b0fc40 c100 000184bc 7422b067 f79063c0
7422b067 006ff260 f79e6000
[78800.008294] Call Trace:
[78800.008294]  [f909713a] cifs_readdir+0x2fe/0xed0 [cifs]
[78800.008294]  [c017eafc] filldir64+0x0/0xc5
[78800.008294]  [c0187c10] mnt_want_write+0x21/0x57
[78800.008294]  [c018525d] touch_atime+0xe/0xd1
[78800.008294]  [c017ecdc] vfs_readdir+0x62/0x8c
[78800.008294]  [c017eafc] filldir64+0x0/0xc5
[78800.008294]  [c017ed69] sys_getdents64+0x63/0xa5
[78800.008294]  [c0103857] sysenter_past_esp+0x78/0xb1
[78800.008294]  [c02b] quirk_vt8235_acpi+0x5e/0x7a
[78800.008294]  ===
[78800.008294] Code: 89 50 4c 8b 44 24 18 66 c7 40 50 06 00 8b 5d 20
81 fb ff 0f 00 00 0f 8f 5e 01 00 00 8b 7c 24 18 89 d9 c1 e9 02 8b 75
1c 83 c7 52 f3 a5 89 d9 83 e1 03 74 02 f3 a4 8b 44 24 18 8d 53 0e 8d
4b 0f
[78800.008294] EIP: [f9082a3f] CIFSFindNext+0x174/0x2dc [cifs]
SS:ESP 0068:f7df9eb8
[78800.008294] ---[ end trace b921610fb330135c ]---

** Loaded modules:
Module  Size  Used by
nls_utf81760  0
cifs  208948  0
nls_base6820  2 nls_utf8,cifs
sha1_generic2304  4
drbd  179724  12
cn  5376  1 drbd
iptable_raw 2176  0
xt_comment  1664  0
xt_policy 

Bug#561890: marked as done (lenny kernel memory leak?)

2011-09-20 Thread Debian Bug Tracking System
Your message dated Wed, 21 Sep 2011 01:55:29 +
with message-id e1r6c25-xh...@franck.debian.org
and subject line Bug#561890: fixed in linux-2.6 2.6.26-27
has caused the Debian Bug report #561890,
regarding lenny kernel memory leak?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
561890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.26-19lenny2
Severity: important

 Forwarded Message 
From: Mikko Rapeli mikko.rap...@iki.fi
To: debian-kernel@lists.debian.org
Subject: lenny kernel memory leak?
Date: Tue, 15 Dec 2009 22:36:56 +0200
Newsgroups: gmane.linux.debian.devel.kernel

(maybe debian-kernel is a better place to ask than debian-user)

I have an old home gateway with 32 MB of ram running email, apache 1.3 with
some static files and an rt2500 based ad-hoc mode WLAN AP with dnsmasq.
Since upgrade from etch to lenny, I've seen a number of OOM situations and
slow downs after a few days of uptime. Is there some perhaps known memory leak
in lenny 2.6.26 kernels, perhaps in rt2500 driver?

In ad-hoc mode the rt2500 driver very chatty about so I disabled klogd for
now, but AFAIK kernel uses a ring buffer which should not slow anything down.

Here's a diff of /proc/meminfo after boot and when seeing a dramatic slow down
after a few days of uptime. I think the anonpages difference shows a memory
leak in kernel, am I correct?

-Mikko
ps. please cc me in replies, thanks.

--- meminfo_after_boot.txt  2009-12-14 14:28:25.0 +0200
+++ meminfo_slow.txt2009-12-14 14:24:01.0 +0200
@@ -1,28 +1,28 @@
 MemTotal:29228 kB
-MemFree:  1172 kB
-Buffers:   552 kB
-Cached:   7488 kB
-SwapCached:404 kB
-Active:  17292 kB
-Inactive: 2632 kB
+MemFree:  1392 kB
+Buffers:   168 kB
+Cached:   1744 kB
+SwapCached:736 kB
+Active:   1360 kB
+Inactive: 1348 kB
 SwapTotal:  204792 kB
-SwapFree:   195728 kB
+SwapFree:   164480 kB
 Dirty:   0 kB
-Writeback:   0 kB
-AnonPages:   11652 kB
-Mapped:   5132 kB
-Slab: 4276 kB
-SReclaimable: 1108 kB
-SUnreclaim:   3168 kB
-PageTables:556 kB
+Writeback: 260 kB
+AnonPages: 384 kB
+Mapped:928 kB
+Slab:21048 kB
+SReclaimable:  952 kB
+SUnreclaim:  20096 kB
+PageTables:688 kB
 NFS_Unstable:0 kB
 Bounce:  0 kB
 WritebackTmp:0 kB
 CommitLimit:219404 kB
-Committed_AS:33172 kB
+Committed_AS:53648 kB
 VmallocTotal:  1007300 kB
 VmallocUsed:  2500 kB
-VmallocChunk:  1004556 kB
+VmallocChunk:  1004624 kB
 HugePages_Total: 0
 HugePages_Free:  0
 HugePages_Rsvd:  0


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


---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-27

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

linux-2.6_2.6.26-27.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.26-27.diff.gz
linux-2.6_2.6.26-27.dsc
  to main/l/linux-2.6/linux-2.6_2.6.26-27.dsc
linux-doc-2.6.26_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-27_all.deb
linux-headers-2.6.26-2-all-hppa_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-all-hppa_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-all_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-common_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc64_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc64_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc_2.6.26-27_hppa.deb
linux-image-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-image-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
linux-image-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-image-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
linux-image-2.6.26-2-parisc64_2.6.26-27_hppa.deb
  to 

Processed: retitle 640964 to Invalid alternatives table in 486 flavour results in BUG at boot

2011-09-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 retitle 640964 Invalid alternatives table in 486 flavour results in BUG at 
 boot
Bug #640964 [linux-image-3.1.0-rc4-486] linux-image-3.1.0-rc4-486: BUG() 
triggered on XO-1 hardware
Changed Bug title to 'Invalid alternatives table in 486 flavour results in BUG 
at boot' from 'linux-image-3.1.0-rc4-486: BUG() triggered on XO-1 hardware'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
640964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.131657084121431.transcr...@bugs.debian.org



linux-2.6_2.6.26-27_hppa.changes ACCEPTED into oldstable-proposed-updates

2011-09-20 Thread Debian FTP Masters


Notes:
Mapping oldstable to oldstable-proposed-updates.


Accepted:
linux-2.6_2.6.26-27.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.26-27.diff.gz
linux-2.6_2.6.26-27.dsc
  to main/l/linux-2.6/linux-2.6_2.6.26-27.dsc
linux-doc-2.6.26_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-27_all.deb
linux-headers-2.6.26-2-all-hppa_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-all-hppa_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-all_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-common_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc64_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc64_2.6.26-27_hppa.deb
linux-headers-2.6.26-2-parisc_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-headers-2.6.26-2-parisc_2.6.26-27_hppa.deb
linux-image-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-image-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb
linux-image-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-image-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb
linux-image-2.6.26-2-parisc64_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-image-2.6.26-2-parisc64_2.6.26-27_hppa.deb
linux-image-2.6.26-2-parisc_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-image-2.6.26-2-parisc_2.6.26-27_hppa.deb
linux-libc-dev_2.6.26-27_hppa.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.26-27_hppa.deb
linux-manual-2.6.26_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-27_all.deb
linux-patch-debian-2.6.26_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-27_all.deb
linux-source-2.6.26_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-source-2.6.26_2.6.26-27_all.deb
linux-support-2.6.26-2_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-27_all.deb
linux-tree-2.6.26_2.6.26-27_all.deb
  to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-27_all.deb


Override entries for your package:
linux-2.6_2.6.26-27.dsc - source devel
linux-doc-2.6.26_2.6.26-27_all.deb - optional doc
linux-headers-2.6.26-2-all-hppa_2.6.26-27_hppa.deb - optional devel
linux-headers-2.6.26-2-all_2.6.26-27_hppa.deb - optional devel
linux-headers-2.6.26-2-common_2.6.26-27_hppa.deb - optional devel
linux-headers-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb - optional devel
linux-headers-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb - optional devel
linux-headers-2.6.26-2-parisc64_2.6.26-27_hppa.deb - optional devel
linux-headers-2.6.26-2-parisc_2.6.26-27_hppa.deb - optional devel
linux-image-2.6.26-2-parisc-smp_2.6.26-27_hppa.deb - optional admin
linux-image-2.6.26-2-parisc64-smp_2.6.26-27_hppa.deb - optional admin
linux-image-2.6.26-2-parisc64_2.6.26-27_hppa.deb - optional admin
linux-image-2.6.26-2-parisc_2.6.26-27_hppa.deb - optional admin
linux-libc-dev_2.6.26-27_hppa.deb - optional devel
linux-manual-2.6.26_2.6.26-27_all.deb - optional doc
linux-patch-debian-2.6.26_2.6.26-27_all.deb - optional devel
linux-source-2.6.26_2.6.26-27_all.deb - optional devel
linux-support-2.6.26-2_2.6.26-27_all.deb - optional devel
linux-tree-2.6.26_2.6.26-27_all.deb - optional devel

Announcing to debian-chan...@lists.debian.org
Closing bugs: 524438 561890 604457 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1r6c24-x5...@franck.debian.org



[PATCH kernel-wedge 0/3] Support use of kernel-wedge in linux-2.6

2011-09-20 Thread Ben Hutchings
These are the same changes I posted before, except:
- Split into 3 coherent changes, as Joey requested
- Removed the bogus -V option to depmod

Ben.

Ben Hutchings (3):
  Allow kernel source packages to use kernel-wedge on themselves
  Allow kernel ABI version to be specified as command-line argument
  Allow configuration files to be placed in a subdirectory

 commands/check |7 +-
 commands/copy-modules  |   29 +++
 commands/gen-control   |   47 +
 commands/gen-deps  |   11 +
 commands/install-files |   49 +--
 debian/changelog   |5 
 6 files changed, 101 insertions(+), 47 deletions(-)

-- 
1.7.5.4




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


[PATCH kernel-wedge 1/3] Allow kernel source packages to use kernel-wedge on themselves

2011-09-20 Thread Ben Hutchings
In this case, the kernel will be installed in a package directory
under debian/ and the source package's only additional build-
dependency is kernel-wedge itself.

check: We should only check the package directories that we generated.
Allow the package names to be specified as arguments, but if no
arguments are given then continue to check all packages.

copy-modules: For Linux kernel packages, depmod is run on installation
and modules.dep does not exist in the package directory.  Generate
modules.dep (etc.) in the temporary directory if necessary.

gen-control: If the configuration file specifies all build-
dependencies as '-', do not generate a source package stanza.

install-files: If the configuration file specifies build-dependencies
as '-', use the appropriate package directory as the source directory.
---
 commands/check |7 ++-
 commands/copy-modules  |   10 ++
 commands/gen-control   |   23 ++-
 commands/install-files |   22 ++
 debian/changelog   |3 +++
 5 files changed, 47 insertions(+), 18 deletions(-)

diff --git a/commands/check b/commands/check
index 8c07359..9fe7470 100755
--- a/commands/check
+++ b/commands/check
@@ -1,6 +1,11 @@
 #!/bin/sh -e
 empty=
-for pkg in $(dh_listpackages -s); do
+if [ $# -ge 1 ]; then
+packages=$*
+else
+packages=$(dh_listpackages -s)
+fi
+for pkg in $packages; do
if [ -z  $(find debian/$pkg -type f) ]; then
echo $pkg will be empty 2
empty=1
diff --git a/commands/copy-modules b/commands/copy-modules
index 75c4208..974347d 100755
--- a/commands/copy-modules
+++ b/commands/copy-modules
@@ -111,9 +111,11 @@ else
 fi
 
 if [ $os = linux ] ; then
-   if [ ! -e $moddir/modules.dep ]; then
-   echo no $moddir/modules.dep. This file is required by 
kernel-wedge 2
-   exit 1
+   if [ -e $moddir/modules.dep ]; then
+   modulesdep=$moddir/modules.dep
+   else
+   modulesdep=$tmpdir/modules.dep
+   depmod ${SOURCEDIR:+-b $SOURCEDIR} $installedname -n 
$modulesdep
fi
 
# get module dependencies from modules.dep
@@ -128,7 +130,7 @@ if [ $os = linux ] ; then
foreach (@words) {
print $module\t$_ unless $_ eq \\;
}
-   ' $moddir/modules.dep | sort -k 2,2  $tmpdir/deps
+   ' $modulesdep | sort -k 2,2  $tmpdir/deps

if [ ! -s $tmpdir/deps ]  [ ! -e $home/no-modules ]; then
echo No module interdependencies found. This probably means 
your modules.dep is broken. 2
diff --git a/commands/gen-control b/commands/gen-control
index ed3f612..f1b742d 100755
--- a/commands/gen-control
+++ b/commands/gen-control
@@ -29,21 +29,26 @@ while (KVERS) {
die parse error;
}
push @versions, [ $arch, $kernelversion, $flavour ];
-   foreach my $pkg (split(, , $builddep)) {
-   push @builddeps, $pkg [$arch];
+   if ($builddep ne -) {
+   foreach my $pkg (split(, , $builddep)) {
+   push @builddeps, $pkg [$arch];
+   }
}
 }
 close KVERS;
 
-open(STUB, debian/control.stub) || die debian/control.stub: $!;
-while (STUB) {
-   chomp;
-   if (/^Build-Depends:/) {
-   $_=join(, , $_, @builddeps);
+# Building with installed kernel package, or as part of a package?
+if (@builddeps) {
+   open(STUB, debian/control.stub) || die debian/control.stub: $!;
+   while (STUB) {
+   chomp;
+   if (/^Build-Depends:/) {
+   $_=join(, , $_, @builddeps);
+   }
+   print $_.\n;
}
-   print $_.\n;
+   close STUB;
 }
-close STUB;
 
 sub read_package_list
 {
diff --git a/commands/install-files b/commands/install-files
index 9b88b71..482fbeb 100755
--- a/commands/install-files
+++ b/commands/install-files
@@ -12,10 +12,7 @@ sub doit {
 my $hostarch=`dpkg-architecture -qDEB_HOST_ARCH`;
 chomp $hostarch;
 
-my $sourcedir=$ENV{SOURCEDIR};
-if (! defined $sourcedir) {
-   $sourcedir=;
-}
+my $fixsourcedir = $ENV{SOURCEDIR};
 
 open(KVERS, kernel-versions) || die kernel-versions: $!;
 my $version = 0;
@@ -31,6 +28,23 @@ while (KVERS) {
}
next unless $arch eq $hostarch;
 
+   my $sourcedir;
+   if (defined $fixsourcedir) {
+   $sourcedir = $fixsourcedir;
+   } else {
+   # Building with installed kernel package, or as part
+   # of a package?
+   if ($builddep ne -) {
+   $sourcedir = ;
+   } elsif ($arch =~ /^kfreebsd-/) {
+   $sourcedir = debian/kfreebsd-image-$installedname;
+   } else {
+   $sourcedir = debian/linux-image-$installedname;
+   }
+   # Set SOURCEDIR for copy-modules
+   $ENV{SOURCEDIR} = $sourcedir;
+   }
+

[PATCH kernel-wedge 2/3] Allow kernel ABI version to be specified as command-line argument

2011-09-20 Thread Ben Hutchings
When building as part of a kernel source package, the kernel ABI
version used should always be the current one.  The 'installed name'
changes with the kernel ABI version but is also quite regular.
Neither of these should need to be specified redundantly in
configuration files.

gen-control, install-files: Allow the version to be specified as a
command-line argument, overriding the configuration file.  In this
case, the configuration file should specify '-'.  Allow the installed
name to be specified as '-', and in that case generate it
automatically.
---
 commands/gen-control   |7 +++
 commands/install-files |   12 
 debian/changelog   |1 +
 3 files changed, 20 insertions(+), 0 deletions(-)

diff --git a/commands/gen-control b/commands/gen-control
index f1b742d..764144d 100755
--- a/commands/gen-control
+++ b/commands/gen-control
@@ -11,6 +11,8 @@ my %packages;
 my @builddeps;
 my %excluded;
 
+my $fixkernelversion = $ARGV[0];
+
 if (open(EXCLUDED, exclude-packages)) {
while (EXCLUDED) {
chomp;
@@ -28,6 +30,11 @@ while (KVERS) {
if (! length $arch || ! length $kernelversion || ! length $flavour) {
die parse error;
}
+   if (defined($fixkernelversion)) {
+   $kernelversion = $fixkernelversion;
+   } elsif ($kernelversion eq -) {
+   die kernel version not set in file or on command line;
+   }
push @versions, [ $arch, $kernelversion, $flavour ];
if ($builddep ne -) {
foreach my $pkg (split(, , $builddep)) {
diff --git a/commands/install-files b/commands/install-files
index 482fbeb..3cabf86 100755
--- a/commands/install-files
+++ b/commands/install-files
@@ -14,6 +14,8 @@ chomp $hostarch;
 
 my $fixsourcedir = $ENV{SOURCEDIR};
 
+my $fixkernelversion = $ARGV[0];
+
 open(KVERS, kernel-versions) || die kernel-versions: $!;
 my $version = 0;
 while (KVERS) {
@@ -28,6 +30,16 @@ while (KVERS) {
}
next unless $arch eq $hostarch;
 
+   if (defined($fixkernelversion)) {
+   $kernelversion = $fixkernelversion;
+   } elsif ($kernelversion eq -) {
+   die kernel version not set in file or on command line;
+   }
+
+   if ($installedname eq -) {
+   $installedname = $kernelversion-$flavour;
+   }
+
my $sourcedir;
if (defined $fixsourcedir) {
$sourcedir = $fixsourcedir;
diff --git a/debian/changelog b/debian/changelog
index 4cfaab0..9cc2682 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -9,6 +9,7 @@ kernel-wedge (2.79) UNRELEASED; urgency=low
 
   [ Ben Hutchings ]
   * Allow kernel source packages to use kernel-wedge on themselves
+  * Allow kernel ABI version to be specified as command-line argument
 
  -- Samuel Thibault sthiba...@debian.org  Mon, 08 Aug 2011 18:34:12 +0200
 
-- 
1.7.5.4





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


[PATCH kernel-wedge 3/3] Allow configuration files to be placed in a subdirectory

2011-09-20 Thread Ben Hutchings
In a kernel source package, which will be non-native, the kernel-wedge
configuration should be placed under the debian/ directory.

copy-modules, gen-control, gen-deps, install-files: Allow the
configuration directory to be specified as a command-line argument.
---
 commands/copy-modules  |   19 ++-
 commands/gen-control   |   17 +
 commands/gen-deps  |   11 ++-
 commands/install-files |   15 ---
 debian/changelog   |1 +
 5 files changed, 34 insertions(+), 29 deletions(-)

diff --git a/commands/copy-modules b/commands/copy-modules
index 974347d..ad8fac8 100755
--- a/commands/copy-modules
+++ b/commands/copy-modules
@@ -81,6 +81,7 @@ processmodules() {
 version=$1-$2
 flavour=$2
 installedname=$3
+configdir=$(readlink -f ${4:-.})
 arch=$(dpkg-architecture -qDEB_HOST_ARCH)
 os=$(dpkg-architecture -qDEB_HOST_ARCH_OS)
 home=$PWD
@@ -102,12 +103,12 @@ if [ ! -d $moddir ]; then
 fi

 # The directory of modules lists to use.
-if [ -d modules/$arch-$flavour ]; then
-   modlistdir=modules/$arch-$flavour
-elif [ -d modules/$flavour ]; then
-   modlistdir=modules/$flavour
+if [ -d $configdir/modules/$arch-$flavour ]; then
+   modlistdir=$configdir/modules/$arch-$flavour
+elif [ -d $configdir/modules/$flavour ]; then
+   modlistdir=$configdir/modules/$flavour
 else
-   modlistdir=modules/$arch
+   modlistdir=$configdir/modules/$arch
 fi
 
 if [ $os = linux ] ; then
@@ -132,9 +133,9 @@ if [ $os = linux ] ; then
}
' $modulesdep | sort -k 2,2  $tmpdir/deps

-   if [ ! -s $tmpdir/deps ]  [ ! -e $home/no-modules ]; then
+   if [ ! -s $tmpdir/deps ]  [ ! -e $configdir/no-modules ]; then
echo No module interdependencies found. This probably means 
your modules.dep is broken. 2
-   echo If this is intentional, touch $home/no-modules 2
+   echo If this is intentional, touch $configdir/no-modules 2
exit 1
fi
 else
@@ -144,7 +145,7 @@ fi
 mkdir $tmpdir/module-deps $tmpdir/module-list
 
 # generate module interrelationships from package-list file
-kernel-wedge gen-deps $flavour  $tmpdir/module-deps.packages
+kernel-wedge gen-deps $flavour $configdir  $tmpdir/module-deps.packages
 
 code=0
 # loop over all udebs, sort that all dependent modules are processed first
@@ -166,7 +167,7 @@ for i in $(

# preprocess file, handle includes and excludes and sort so that
# the joins work, no matter what the order of the input.
-   kernel-wedge preprocess $home/$modlistdir/$i | sort  
$tmpdir/module-list/$i
+   kernel-wedge preprocess $modlistdir/$i | sort  $tmpdir/module-list/$i
 
# exclude modules in exclude from dependency list
join -2 2 -v 2 $tmpdir/exclude $tmpdir/deps |
diff --git a/commands/gen-control b/commands/gen-control
index 764144d..3f75211 100755
--- a/commands/gen-control
+++ b/commands/gen-control
@@ -12,8 +12,9 @@ my @builddeps;
 my %excluded;
 
 my $fixkernelversion = $ARGV[0];
+my $configdir = ($ARGV[1] || '.');
 
-if (open(EXCLUDED, exclude-packages)) {
+if (open(EXCLUDED, $configdir/exclude-packages)) {
while (EXCLUDED) {
chomp;
$excluded{$_}=1;
@@ -21,7 +22,7 @@ if (open(EXCLUDED, exclude-packages)) {
close EXCLUDED;
 }
 
-open(KVERS, kernel-versions) || die kernel-versions: $!;
+open(KVERS, $configdir/kernel-versions) || die kernel-versions: $!;
 while (KVERS) {
chomp;
next if /^#/ || ! length;
@@ -108,7 +109,7 @@ sub read_package_list
close LIST;
 }
 read_package_list(/usr/share/kernel-wedge/package-list);
-read_package_list(package-list);
+read_package_list($configdir/package-list);
 
 foreach my $ver (@versions) {
my ($arch, $kernelversion, $flavour) = @$ver;
@@ -133,14 +134,14 @@ foreach my $ver (@versions) {
# Check for a modules list file for this architecture and
# package.
my $modlistdir=;
-   if (-d modules/$arch-$flavour) {
-   $modlistdir=modules/$arch-$flavour;
+   if (-d $configdir/modules/$arch-$flavour) {
+   $modlistdir = $configdir/modules/$arch-$flavour;
}
-   elsif (-d modules/$flavour) {
-   $modlistdir=modules/$flavour;
+   elsif (-d $configdir/modules/$flavour) {
+   $modlistdir = $configdir/modules/$flavour;
}
else {
-   $modlistdir=modules/$arch;
+   $modlistdir = $configdir/modules/$arch;
}

next unless -e $modlistdir/.$package-(Package);
diff --git a/commands/gen-deps b/commands/gen-deps
index 94e77be..9dfd610 100755
--- a/commands/gen-deps
+++ b/commands/gen-deps
@@ -7,6 +7,7 @@ my $arch=`dpkg-architecture -qDEB_HOST_ARCH`;
 chomp $arch;
 
 my $flavour=$ARGV[0];

Processed: tagging 640964

2011-09-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 640964 + pending
Bug #640964 [linux-image-3.1.0-rc4-486] Invalid alternatives table in 486 
flavour results in BUG at boot
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
640964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.131657997928600.transcr...@bugs.debian.org