Debian Bug report logs - #626851
linux-image-2.6.38-2-amd64: after last update fails to boot

version graph

Package: linux-2.6; Maintainer for linux-2.6 is Debian Kernel Team <debian-kernel@lists.debian.org>;

Reported by: Rares Aioanei <schaiba@gmail.com>

Date: Sun, 15 May 2011 21:27:03 UTC

Severity: minor

Tags: moreinfo, upstream

Found in versions 2.6.38-5, linux-2.6/2.6.39~rc7-1~experimental.1

Done: Jonathan Nieder <jrnieder@gmail.com>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, schaiba@gmail.com, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Sun, 15 May 2011 21:27:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Rares Aioanei <schaiba@gmail.com>:
New Bug report received and forwarded. Copy sent to schaiba@gmail.com, Debian Kernel Team <debian-kernel@lists.debian.org>. (Sun, 15 May 2011 21:27:10 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Rares Aioanei <schaiba@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Mon, 16 May 2011 00:24:32 +0300
Package: linux-2.6
Version: 2.6.38-5
Severity: important

I'm not even certain that the kernel is the problem and not
initramfs-tools or something, but since when the update occured (14th of
May) only the kernel was updated (and libuuid-perl) so I will report
this against the kernel. Obviously, no kernel log, and the message shown
is as follows (sorry, I don't have a camera) :

Loading, please wait...
/scripts/local-premount/resume : line 63 : /bin/resume : not found
mount : mounting /dev/disk-by-uuid/<uuid here> on /root failed : no such
file or directory
mount : mounting /dev/on /root/dev failed : No such file or directory
[same for /sys and /proc]
Target filesystem doesn't have required /sbin/init
No init found. Try passing init= boot argument
[Busybox prompt follows]

The init=/bin/sh doesn't work for obvious reasons.




-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Gigabyte Technology Co., Ltd.
product_name: M56S-S3
product_version:  
chassis_vendor: Gigabyte Technology Co., Ltd.
chassis_version:  
bios_vendor: Award Software International, Inc.
bios_version: F1
board_vendor: Gigabyte Technology Co., Ltd.
board_name: GA-M56S-S3
board_version: x.x

** Network interface configuration:

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

** PCI devices:
00:00.0 RAM memory [0500]: nVidia Corporation MCP65 Memory Controller [10de:0444] (rev a3)
	Subsystem: Giga-byte Technology Device [1458:5001]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>

00:01.0 ISA bridge [0601]: nVidia Corporation MCP65 LPC Bridge [10de:0441] (rev a3)
	Subsystem: Giga-byte Technology Device [1458:0c11]
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0

00:01.1 SMBus [0c05]: nVidia Corporation MCP65 SMBus [10de:0446] (rev a1)
	Subsystem: Giga-byte Technology Device [1458:0c11]
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at e000 [size=64]
	Region 4: I/O ports at 1c00 [size=64]
	Region 5: I/O ports at 1c40 [size=64]
	Capabilities: <access denied>
	Kernel driver in use: nForce2_smbus

00:01.2 RAM memory [0500]: nVidia Corporation MCP65 Memory Controller [10de:0445] (rev a1)
	Subsystem: Giga-byte Technology Device [1458:0c11]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:02.0 USB Controller [0c03]: nVidia Corporation MCP65 USB Controller [10de:0454] (rev a3) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology Device [1458:5004]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin A routed to IRQ 20
	Region 0: Memory at f6008000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: ohci_hcd

00:02.1 USB Controller [0c03]: nVidia Corporation MCP65 USB Controller [10de:0455] (rev a3) (prog-if 20 [EHCI])
	Subsystem: Giga-byte Technology Device [1458:5004]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin B routed to IRQ 22
	Region 0: Memory at f6006000 (32-bit, non-prefetchable) [size=256]
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:06.0 Ethernet controller [0200]: nVidia Corporation MCP65 Ethernet [10de:0450] (rev a3)
	Subsystem: Giga-byte Technology Device [1458:e000]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (250ns min, 5000ns max)
	Interrupt: pin A routed to IRQ 41
	Region 0: Memory at f6007000 (32-bit, non-prefetchable) [size=4K]
	Region 1: I/O ports at c800 [size=8]
	Capabilities: <access denied>
	Kernel driver in use: forcedeth

00:07.0 Audio device [0403]: nVidia Corporation MCP65 High Definition Audio [10de:044a] (rev a1)
	Subsystem: Giga-byte Technology Device [1458:a002]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (500ns min, 1250ns max)
	Interrupt: pin B routed to IRQ 23
	Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: HDA Intel

00:08.0 PCI bridge [0604]: nVidia Corporation MCP65 PCI bridge [10de:0449] (rev a1) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	I/O behind bridge: 0000a000-0000afff
	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:09.0 IDE interface [0101]: nVidia Corporation MCP65 IDE [10de:0448] (rev a1) (prog-if 8a [Master SecP PriP])
	Subsystem: Giga-byte Technology Device [1458:5002]
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (750ns min, 250ns max)
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
	Region 4: I/O ports at f000 [size=16]
	Capabilities: <access denied>
	Kernel driver in use: pata_amd

00:0a.0 IDE interface [0101]: nVidia Corporation MCP65 SATA Controller [10de:045d] (rev a3) (prog-if 85 [Master SecO PriO])
	Subsystem: Giga-byte Technology Device [1458:b002]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin A routed to IRQ 40
	Region 0: I/O ports at 09f0 [size=8]
	Region 1: I/O ports at 0bf0 [size=4]
	Region 2: I/O ports at 0970 [size=8]
	Region 3: I/O ports at 0b70 [size=4]
	Region 4: I/O ports at dc00 [size=16]
	Region 5: Memory at f6004000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: ahci

00:0d.0 PCI bridge [0604]: nVidia Corporation MCP65 PCI Express bridge [10de:0458] (rev a1) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000b000-0000bfff
	Memory behind bridge: f2000000-f5ffffff
	Prefetchable memory behind bridge: 00000000e0000000-00000000efffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Capabilities: <access denied>

00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Capabilities: <access denied>
	Kernel driver in use: k8temp

02:00.0 VGA compatible controller [0300]: nVidia Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: XFX Pine Group Inc. Device [1682:231f]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f4000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at f2000000 (64-bit, non-prefetchable) [size=32M]
	Region 5: I/O ports at b000 [size=128]
	[virtual] Expansion ROM at f5000000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: nouveau


** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 045e:074a Microsoft Corp. 


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-2.6.38-2-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.39     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.98.8     tools for generating an initramfs
ii  linux-base                    3.2        Linux image base package
ii  module-init-tools             3.12-1     tools for managing Linux kernel mo

Versions of packages linux-image-2.6.38-2-amd64 recommends:
pn  firmware-linux-free           <none>     (no description available)

Versions of packages linux-image-2.6.38-2-amd64 suggests:
ii  grub-pc                      1.99~rc1-13 GRand Unified Bootloader, version 
pn  linux-doc-2.6.38             <none>      (no description available)

Versions of packages linux-image-2.6.38-2-amd64 is related to:
pn  firmware-bnx2                 <none>     (no description available)
pn  firmware-bnx2x                <none>     (no description available)
pn  firmware-ipw2x00              <none>     (no description available)
pn  firmware-ivtv                 <none>     (no description available)
pn  firmware-iwlwifi              <none>     (no description available)
pn  firmware-linux                <none>     (no description available)
pn  firmware-linux-nonfree        <none>     (no description available)
pn  firmware-qlogic               <none>     (no description available)
pn  firmware-ralink               <none>     (no description available)
pn  xen-hypervisor                <none>     (no description available)

-- debconf information:
  linux-image-2.6.38-2-amd64/prerm/removing-running-kernel-2.6.38-2-amd64: true
  linux-image-2.6.38-2-amd64/postinst/missing-firmware-2.6.38-2-amd64:
  linux-image-2.6.38-2-amd64/postinst/ignoring-do-bootloader-2.6.38-2-amd64:
  linux-image-2.6.38-2-amd64/postinst/depmod-error-initrd-2.6.38-2-amd64: false




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Tue, 17 May 2011 10:03:12 GMT) Full text and rfc822 format available.

Acknowledgement sent to Rares Aioanei <rares.aioanei@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 17 May 2011 10:03:18 GMT) Full text and rfc822 format available.

Message #10 received at 626851@bugs.debian.org (full text, mbox):

From: Rares Aioanei <rares.aioanei@gmail.com>
To: 626851@bugs.debian.org
Subject: More info
Date: Tue, 17 May 2011 13:00:47 +0300
The error described can be also seen if compiling a vanilla kernel with
the exact config as the Debian one (in my case 2.6.38.6) . I'm writing this from the same machine running 2.6.38.4 with a custom config and it works fine. Hope it helps.

-- 
Rares Aioanei




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Tue, 17 May 2011 10:12:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 17 May 2011 10:12:12 GMT) Full text and rfc822 format available.

Message #15 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Tue, 17 May 2011 05:11:34 -0500
tags 626851 + upstream moreinfo
quit

Hi,

Rares Aioanei wrote:

> Loading, please wait...
> /scripts/local-premount/resume : line 63 : /bin/resume : not found
> mount : mounting /dev/disk-by-uuid/<uuid here> on /root failed : no such file or directory
[...]
> The error described can be also seen if compiling a vanilla kernel with
> the exact config as the Debian one (in my case 2.6.38.6) . I'm writing this
> from the same machine running 2.6.38.4 with a custom config and it works
> fine. Hope it helps.

Could you attach a dmesg from the working configuration and the two .config
files for comparison?  What commands do you use to build and install a
custom kernel?  Does the custom configuration build in the disk driver
(i.e., Y instead of M), and does it use an initramfs?

Thanks for writing,
Jonathan




Added tag(s) upstream and moreinfo. Request was from Jonathan Nieder <jrnieder@gmail.com> to control@bugs.debian.org. (Tue, 17 May 2011 10:12:16 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Tue, 17 May 2011 10:36:47 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 17 May 2011 10:36:48 GMT) Full text and rfc822 format available.

Message #22 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: 626851@bugs.debian.org
Cc: Rares Aioanei <rares.aioanei@gmail.com>
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Tue, 17 May 2011 05:35:24 -0500
[Message part 1 (text/plain, inline)]
tags 626851 - moreinfo
quit

(cc-ing the bug log)
Rares Aioanei wrote:

> I used the exact sequence of commands in building the working kernel and the
> non-working kernel; and yes, the disk driver is , of course, 'y', not built
> as a module. Was there a change in the config file in this last update?

That's possible, but more likely the bug is in some specific driver
that the working kernel does not use (or something like that).

Thanks for the info.  The reason for asking about built-in disk
drivers is that the Debian kernel installs many drivers like that as
modules that get loaded in the initramfs.  One way to track this down
might be to adapt chunks of the .config to more closely resemble the
Debian kernel until it fails, and then pare it down until it succeeds
again.  Others may have better ideas.

Regards,
Jonathan
[Message part 2 (message/rfc822, inline)]
From: Rares Aioanei <rares.aioanei@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Tue, 17 May 2011 13:25:28 +0300
[Message part 3 (text/plain, inline)]
On Tue, 17 May 2011 05:11:34 -0500
Jonathan Nieder <jrnieder@gmail.com> wrote:

> tags 626851 + upstream moreinfo
> quit
> 
> Hi,
> 
> Rares Aioanei wrote:
> 
> > Loading, please wait...
> > /scripts/local-premount/resume : line 63 : /bin/resume : not found
> > mount : mounting /dev/disk-by-uuid/<uuid here> on /root failed : no such file or directory
> [...]
> > The error described can be also seen if compiling a vanilla kernel with
> > the exact config as the Debian one (in my case 2.6.38.6) . I'm writing this
> > from the same machine running 2.6.38.4 with a custom config and it works
> > fine. Hope it helps.
> 
> Could you attach a dmesg from the working configuration and the two .config
> files for comparison?  What commands do you use to build and install a
> custom kernel?  Does the custom configuration build in the disk driver
> (i.e., Y instead of M), and does it use an initramfs?
> 
> Thanks for writing,
> Jonathan

Attached is the dmesg, also the .configs, the commands are : 
1.cp /boot/config<version> ./.config (obviously, in the root dir of the kernel source.)
2.make menuconfig and load config file -> .config
3.make -j3 all
4.sudo make modules_install
5.sudo make install 
6.sudo depmod
7.sudo update-initramfs -c -k <vresion>
8.sudo update-grub

I used the exact sequence of commands in building the working kernel and the non-working kernel; and yes, the disk driver is , of course, 'y', not built as a module. Was there a change in the config file in this last update?

Thanks, 

-- 
Rares Aioanei
[dmesg.txt (text/plain, attachment)]
[config_faulty (application/octet-stream, attachment)]
[config_working (application/octet-stream, attachment)]

Removed tag(s) moreinfo. Request was from Jonathan Nieder <jrnieder@gmail.com> to control@bugs.debian.org. (Tue, 17 May 2011 10:36:54 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Tue, 17 May 2011 10:39:18 GMT) Full text and rfc822 format available.

Acknowledgement sent to Rares Aioanei <rares.aioanei@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 17 May 2011 10:39:20 GMT) Full text and rfc822 format available.

Message #29 received at 626851@bugs.debian.org (full text, mbox):

From: Rares Aioanei <rares.aioanei@gmail.com>
To: 626851@bugs.debian.org
Subject: Fw: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Tue, 17 May 2011 13:37:28 +0300
[Message part 1 (text/plain, inline)]

Begin forwarded message:

Date: Tue, 17 May 2011 13:25:28 +0300
From: Rares Aioanei <rares.aioanei@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot


On Tue, 17 May 2011 05:11:34 -0500
Jonathan Nieder <jrnieder@gmail.com> wrote:

> tags 626851 + upstream moreinfo
> quit
> 
> Hi,
> 
> Rares Aioanei wrote:
> 
> > Loading, please wait...
> > /scripts/local-premount/resume : line 63 : /bin/resume : not found
> > mount : mounting /dev/disk-by-uuid/<uuid here> on /root failed : no such file or directory
> [...]
> > The error described can be also seen if compiling a vanilla kernel with
> > the exact config as the Debian one (in my case 2.6.38.6) . I'm writing this
> > from the same machine running 2.6.38.4 with a custom config and it works
> > fine. Hope it helps.
> 
> Could you attach a dmesg from the working configuration and the two .config
> files for comparison?  What commands do you use to build and install a
> custom kernel?  Does the custom configuration build in the disk driver
> (i.e., Y instead of M), and does it use an initramfs?
> 
> Thanks for writing,
> Jonathan

Attached is the dmesg, also the .configs, the commands are : 
1.cp /boot/config<version> ./.config (obviously, in the root dir of the kernel source.)
2.make menuconfig and load config file -> .config
3.make -j3 all
4.sudo make modules_install
5.sudo make install 
6.sudo depmod
7.sudo update-initramfs -c -k <vresion>
8.sudo update-grub

I used the exact sequence of commands in building the working kernel and the non-working kernel; and yes, the disk driver is , of course, 'y', not built as a module. Was there a change in the config file in this last update?

Thanks, 

-- 
Rares Aioanei


-- 
Rares Aioanei
[dmesg.txt (text/plain, attachment)]
[config_faulty (application/octet-stream, attachment)]
[config_working (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Tue, 17 May 2011 10:42:21 GMT) Full text and rfc822 format available.

Acknowledgement sent to Rares Aioanei <rares.aioanei@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 17 May 2011 10:42:26 GMT) Full text and rfc822 format available.

Message #34 received at 626851@bugs.debian.org (full text, mbox):

From: Rares Aioanei <rares.aioanei@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Tue, 17 May 2011 13:41:00 +0300
On Tue, 17 May 2011 05:35:24 -0500
Jonathan Nieder <jrnieder@gmail.com> wrote:

> tags 626851 - moreinfo
> quit
> 
> (cc-ing the bug log)
> Rares Aioanei wrote:
> 
> > I used the exact sequence of commands in building the working kernel and the
> > non-working kernel; and yes, the disk driver is , of course, 'y', not built
> > as a module. Was there a change in the config file in this last update?
> 
> That's possible, but more likely the bug is in some specific driver
> that the working kernel does not use (or something like that).
> 
> Thanks for the info.  The reason for asking about built-in disk
> drivers is that the Debian kernel installs many drivers like that as
> modules that get loaded in the initramfs.  One way to track this down
> might be to adapt chunks of the .config to more closely resemble the
> Debian kernel until it fails, and then pare it down until it succeeds
> again.  Others may have better ideas.
> 
> Regards,
> Jonathan
My custom working config is just the Debian config stripped of unnecessary drivers (wireless, v4l, etc.). I guess I'll get help
from my friend diff(1) and see if I can help further.

Regards,

-- 
Rares Aioanei




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Tue, 17 May 2011 10:57:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 17 May 2011 10:57:08 GMT) Full text and rfc822 format available.

Message #39 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Tue, 17 May 2011 05:55:12 -0500
Rares Aioanei wrote:

> My custom working config is just the Debian config stripped of unnecessary
> drivers (wireless, v4l, etc.). I guess I'll get help from my friend diff(1)
> and see if I can help further.

Excellent.  Also, i'm starting to worry I misread what you wrote. :)
So here's a summary:

 - packaged 2.6.38-4 worked ok
 - packaged 2.6.38-5 did not work ok
 - gregkh's 2.6.38.6 with .config from 2.6.38-5 did not work ok
 - gregkh's 2.6.38.4 with custom .config worked ok

In particular, I had somehow confused myself into thinking that
tested 2.6.38.4 with the Debian configuration failed or 2.6.38.6 with
the custom .config worked ok, but rereading the bug log, I don't see
that.  Am I understanding correctly?

If I am and the .config indeed seems to be a red herring, would you be
willing to bisect between 2.6.38.4 and 2.6.38.5?  I can guide you
through the process if you'd like (and it probably would have been
worth writing a patch for the kernel guide for that by now; sorry).




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Tue, 17 May 2011 11:00:18 GMT) Full text and rfc822 format available.

Acknowledgement sent to Rares Aioanei <rares.aioanei@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Tue, 17 May 2011 11:00:18 GMT) Full text and rfc822 format available.

Message #44 received at 626851@bugs.debian.org (full text, mbox):

From: Rares Aioanei <rares.aioanei@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Tue, 17 May 2011 14:00:59 +0300
On Tue, 17 May 2011 05:55:12 -0500
Jonathan Nieder <jrnieder@gmail.com> wrote:

> Rares Aioanei wrote:
> 
> > My custom working config is just the Debian config stripped of unnecessary
> > drivers (wireless, v4l, etc.). I guess I'll get help from my friend diff(1)
> > and see if I can help further.
> 
> Excellent.  Also, i'm starting to worry I misread what you wrote. :)
> So here's a summary:
> 
>  - packaged 2.6.38-4 worked ok
>  - packaged 2.6.38-5 did not work ok
>  - gregkh's 2.6.38.6 with .config from 2.6.38-5 did not work ok
>  - gregkh's 2.6.38.4 with custom .config worked ok
> 
Yes, that is correct. 

> In particular, I had somehow confused myself into thinking that
> tested 2.6.38.4 with the Debian configuration failed or 2.6.38.6 with
> the custom .config worked ok, but rereading the bug log, I don't see
> that.  Am I understanding correctly?
> 
> If I am and the .config indeed seems to be a red herring, would you be
> willing to bisect between 2.6.38.4 and 2.6.38.5?  I can guide you
> through the process if you'd like (and it probably would have been
> worth writing a patch for the kernel guide for that by now; sorry).

Yes, I could use some guidance. :-)
-- 
Rares Aioanei




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Fri, 20 May 2011 12:12:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Rares Aioanei <rares.aioanei@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Fri, 20 May 2011 12:12:05 GMT) Full text and rfc822 format available.

Message #49 received at 626851@bugs.debian.org (full text, mbox):

From: Rares Aioanei <rares.aioanei@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Fri, 20 May 2011 15:10:13 +0300
FYI, the latest kernel from experimental (-rc7) fails to boot in the exact same manner.




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Thu, 26 May 2011 00:45:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 26 May 2011 00:45:03 GMT) Full text and rfc822 format available.

Message #54 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Wed, 25 May 2011 19:41:42 -0500
Hi,

Rares Aioanei wrote:
> Jonathan Nieder <jrnieder@gmail.com> wrote:

>> If I am and the .config indeed seems to be a red herring, would you be
>> willing to bisect between 2.6.38.4 and 2.6.38.5?  I can guide you
>> through the process if you'd like (and it probably would have been
>> worth writing a patch for the kernel guide for that by now; sorry).
>
> Yes, I could use some guidance. :-)

Sorry for the long silence.  Now the aforementioned patch is at [1]
but I'd rather give more pertinent advice directly.

First I would suggest testing with 2.6.39-1 from experimental.  If
that doesn't work, here is how to bisect:

	apt-get install build-essential git
	git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
	cd linux-2.6
	git remote add stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.38.y.git
	git fetch stable

The above grabs the kernel sources and in addition fetches the 2.6.38.y
series.

	git checkout v2.6.38.5
	git log v2.6.38.4..v2.6.38.5; # look over the changes
	git revert 068e0202; # back out the most relevant-seeming one
	make localmodconfig; # minimal configuration
	make -j4 deb-pkg

This spends its time building, so go for a hot beverage of your
choice.  Then you can test the resulting .deb:

	cd ..
	dpkg -i linux-image-*.deb
	reboot

If it also exhibits the problem, it would be time to test more
systematically.  It works like this (git-bisect(1) has details):

	cd ~/src/linux-2.6
	git bisect start
	git bisect bad; # current revision is bad
	git bisect bad v2.6.38.5
	git bisect good v2.6.38.4

Now it checks out a version halfway between to test:

	make silentoldconfig; # reuse configuration
	make -j4 deb-pkg

Hopefully this would be faster than the original build.  One can
test by installing the resulting package and rebooting.  Then
report back:

	git bisect good; # if it boots correctly
	git bisect bad; # if it exhibits the problem
	git bisect skip; # if some other problem makes it hard to test 

and it will check out a next version.  Since there are 56 patches
between 2.6.38.4 and 2.6.38.5, this would take log(56)/log(2) ~= 6
rounds to pinpoint to an individual patch.  The result of testing is
still useful to narrow it down if one gets bored before then. :)
You can get a picture of what's happening at any time with "git bisect
visualize" if the gitk package is installed.

Thanks again, and sorry I don't have any more clever ideas.

Regards,
Jonathan

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=20;bug=627960




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Thu, 26 May 2011 00:57:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 26 May 2011 00:57:03 GMT) Full text and rfc822 format available.

Message #59 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Wed, 25 May 2011 19:53:29 -0500
found 626851 linux-2.6/2.6.39~rc7-1~experimental.1
quit

Jonathan Nieder wrote:

> First I would suggest testing with 2.6.39-1 from experimental.

Ah, no need for this part --- you already checked rc7.




Bug Marked as found in versions linux-2.6/2.6.39~rc7-1~experimental.1. Request was from Jonathan Nieder <jrnieder@gmail.com> to control@bugs.debian.org. (Thu, 26 May 2011 00:57:05 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Thu, 26 May 2011 15:39:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 26 May 2011 15:39:06 GMT) Full text and rfc822 format available.

Message #66 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Thu, 26 May 2011 10:36:24 -0500
Hi,

Rares Aioanei wrote:

> Sorry, but after bisecting the results are roughly the same (roughly as in
> the error message is now "Giving up waiting for root device"). I'm puzzled as
> to what to do next. If I can help any further, I will do it gladly.

To be clear, do you mean that you got this result with the version
halfway between v2.6.38.4 and v2.6.38.5?  What does the .config file
look like --- could you send it?  (Sorry for the tedious questions.)

"Giving up waiting for the root device" can mean many things, but it often
means the hard disk driver didn't load.  Maybe that means an (unrelated)
localmodconfig bug; trying with a known-good .config file (like so:

	cp /path/to/my/good/config/file .config
	make oldconfig
	make deb-pkg
	cd ..
	dpkg -i ...
	reboot

) could be a good idea.

If this *was* a known-good .config file, I'd suggest running

	git bisect bad

and building and testing the next version it suggests.

Sorry for the lack of clarity.
Jonathan




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Thu, 26 May 2011 18:06:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Thu, 26 May 2011 18:06:08 GMT) Full text and rfc822 format available.

Message #71 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Thu, 26 May 2011 13:03:12 -0500
[Message part 1 (text/plain, inline)]
Rares Aioanei wrote:

> Here's the config; I tried the good config already with vanilla and
> it works ok, hence my idea that it's more of a config issue rather
> than a kernel bug per se.

The simplest way to check would be to try with a stock configuration
file (like the one from /boot/config-2.6.38-2-amd64).

Looking through the config file you sent, I see

| Linux/x86_64 2.6.38.5 Kernel Configuration

which makes it seem you were building v2.6.38.5.  Is that right?  If
so, it would not be unexpected that it failed to boot, since the stock
Debian 2.6.38-5 package failed, too, right?  The idea if you got the
same message as started the bug would be to run "git bisect bad" and
then build the next kernel after that.  But:

Other notable bits from the .config file:

. CONFIG_EXPERT=y makes it easy to build a kernel that doesn't boot;
  it should be easier to debug with it off.

. "# CONFIG_BLK_DEV_SD is not set" means it can't read your disk ---
  libata presents disks as SCSI to the kernel.
[Message part 2 (message/rfc822, inline)]
From: Rares Aioanei <rares.aioanei@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Thu, 26 May 2011 20:40:43 +0300
[Message part 3 (text/plain, inline)]
On Thu, 26 May 2011 10:36:24 -0500
Jonathan Nieder <jrnieder@gmail.com> wrote:

> Hi,
> 
> Rares Aioanei wrote:
> 
> > Sorry, but after bisecting the results are roughly the same (roughly as in
> > the error message is now "Giving up waiting for root device"). I'm puzzled as
> > to what to do next. If I can help any further, I will do it gladly.
> 
> To be clear, do you mean that you got this result with the version
> halfway between v2.6.38.4 and v2.6.38.5?  What does the .config file
> look like --- could you send it?  (Sorry for the tedious questions.)
> 
> "Giving up waiting for the root device" can mean many things, but it often
> means the hard disk driver didn't load.  Maybe that means an (unrelated)
> localmodconfig bug; trying with a known-good .config file (like so:
> 
> 	cp /path/to/my/good/config/file .config
> 	make oldconfig
> 	make deb-pkg
> 	cd ..
> 	dpkg -i ...
> 	reboot
> 
> ) could be a good idea.
> 
> If this *was* a known-good .config file, I'd suggest running
> 
> 	git bisect bad
> 
> and building and testing the next version it suggests.
> 
> Sorry for the lack of clarity.
> Jonathan
Here's the config; I tried the good config already with vanilla and it works ok, hence my idea that it's more of a config issue rather than a kernel bug per se.

Cheers, 

-- 
Rares Aioanei
[.config (application/octet-stream, attachment)]

Added tag(s) moreinfo. Request was from Jonathan Nieder <jrnieder@gmail.com> to control@bugs.debian.org. (Thu, 26 May 2011 22:15:07 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#626851; Package linux-2.6. (Sat, 28 May 2011 23:24:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jonathan Nieder <jrnieder@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. (Sat, 28 May 2011 23:24:03 GMT) Full text and rfc822 format available.

Message #78 received at 626851@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Sat, 28 May 2011 18:20:14 -0500
severity 626851 minor
quit

Rares Aioanei wrote:

> CONFIG_BLK_DEV_SD was the culprit. However, I don't understand exactly what
> happened, since I did not alter no config file. I guess it's something I'm
> missing; now it's all ok. Sorry for the bother. :-)

Okay, that's puzzling.  I think I've missed something in your description
of the problem: could you please enlighten me?

If I understand correctly now:

 * you always build the kernel from source, never using the pre-built
   linux-image-... files.

 * the configuration you use (with "make *config" or by copying in a
   .config file) is made by hand, not the stock configuration.

 * for some reason, versions at and before 2.6.38-4 correctly included
   CONFIG_BLK_DEV_SD in that .config file, and later versions did not.

Is that right?  It's possible that some dependency between
configuration items changed in a bad way, but without knowing exactly
how the configuration was chosen that is hard to check.

The configuration system is documented in
"Documentation/kbuild/kconfig-language.txt".

For now, I'm lowering the severity since it seems you have a working
system.  If you have ideas for how "make config" could work, better
documentation, build-time sanity checks, run-time error messages,
etc. to improve this, then maybe this can move forward; otherwise,
please feel free to close this bug by sending mail to
626851-done@bugs.debian.org.

Sorry for all the confusion.
Jonathan




Severity set to 'minor' from 'important' Request was from Jonathan Nieder <jrnieder@gmail.com> to control@bugs.debian.org. (Sat, 28 May 2011 23:24:05 GMT) Full text and rfc822 format available.

Reply sent to Jonathan Nieder <jrnieder@gmail.com>:
You have taken responsibility. (Sun, 29 May 2011 17:25:44 GMT) Full text and rfc822 format available.

Notification sent to Rares Aioanei <schaiba@gmail.com>:
Bug acknowledged by developer. (Sun, 29 May 2011 17:25:44 GMT) Full text and rfc822 format available.

Message #85 received at 626851-done@bugs.debian.org (full text, mbox):

From: Jonathan Nieder <jrnieder@gmail.com>
To: Rares Aioanei <rares.aioanei@gmail.com>
Cc: 626851-done@bugs.debian.org
Subject: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Date: Sun, 29 May 2011 12:22:45 -0500
Rares Aioanei wrote:

> I did copy a working config (from /boot), just as you told me, then 
> started from there.
[...]
> Jonathan Nieder <jrnieder@gmail.com> wrote:

>>  * for some reason, versions at and before 2.6.38-4 correctly included
>>    CONFIG_BLK_DEV_SD in that .config file, and later versions did not.
>
> Yes, that is right. The most simple answer here is : after a kernel update my
> system stopped booting. I don't know what caused the exclusion of BLK_DEV_SD.
> It would be best, I think, if you'd decide how/if this bug should go further

Okay, I'm closing the bug then, since it's not clear how to figure out
what happened without actually being there.

To track this down, what would be useful is a reproduction recipe, like:

 "I have attached a known-good configuration file.  When I import it
  with 'make menuconfig' in the source tree for gregkh's v2.6.38.4,
  make no changes, and save, the resulting .config file has BLK_DEV_SD
  enabled as a module.  If I do the same in the source tree for
  gregkh's v2.6.38.5, the resulting .config file has BLK_DEV_SD
  disabled.  I've also attached the two resulting .config files for
  reference."

Or:

 "Some change in the standard configuration file seems not to play well
  with my build procedure.  When I import config-2.6.38-4-amd64 with
  'make menunconfig' and then disable the following modules in the
  following order, the resulting .config file is sane (attached).
  When I import config-2.6.38-5-amd64 and make the same sequence of
  changes, the resulting .config file has BLK_DEV_SD disabled (also
  attached)."

Or:

 "When I configure the kernel, I read the 'If unsure, do X' text for
  each item and generally follow it.  The text for BLK_DEV_SD says
  'If unsure, say N' [jn: I haven't actually checked] and the text
  above that doesn't give any indication that a person without SCSI
  disks needs to enable it.  The result of following that advice is a
  .config file with BLK_DEV_SD disabled and the need for arcane
  knowledge to build a working custom kernel."

Or something else entirely, but similarly concrete and reproducible.
If we can't reproduce the symptoms (or at least imagine how to if
given the same hardware), there's nothing we can do to fix the
underlying problem.

Given such a reproduction recipe, I'd be happy to reopen this.

Cheers.
Jonathan




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 27 Jun 2011 07:37:56 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Wed Apr 23 07:38:50 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.