FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 05-15-2011, 09:24 PM
Rares Aioanei
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110515212432.2265.1531.reportbug@debiand1.locald om.ain">http://lists.debian.org/20110515212432.2265.1531.reportbug@debiand1.locald om.ain
 
Old 05-17-2011, 10:11 AM
Jonathan Nieder
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110517101134.GA30394@elie">http://lists.debian.org/20110517101134.GA30394@elie
 
Old 05-17-2011, 10:35 AM
Jonathan Nieder
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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
 
Old 05-17-2011, 10:41 AM
Rares Aioanei
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110517134100.16022dcd@debiand1.localdom.ain">htt p://lists.debian.org/20110517134100.16022dcd@debiand1.localdom.ain
 
Old 05-17-2011, 10:55 AM
Jonathan Nieder
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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).



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110517105437.GA30856@elie">http://lists.debian.org/20110517105437.GA30856@elie
 
Old 05-17-2011, 11:00 AM
Rares Aioanei
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110517140059.0e2ff6aa@debiand1.localdom.ain">htt p://lists.debian.org/20110517140059.0e2ff6aa@debiand1.localdom.ain
 
Old 05-20-2011, 12:10 PM
Rares Aioanei
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

FYI, the latest kernel from experimental (-rc7) fails to boot in the exact same manner.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110520151013.58979bf8@debiand1.localdom.ain">htt p://lists.debian.org/20110520151013.58979bf8@debiand1.localdom.ain
 
Old 05-26-2011, 12:41 AM
Jonathan Nieder
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110526004142.GB7246@elie">http://lists.debian.org/20110526004142.GB7246@elie
 
Old 05-26-2011, 12:53 AM
Jonathan Nieder
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110526005329.GA7804@elie">http://lists.debian.org/20110526005329.GA7804@elie
 
Old 05-26-2011, 03:36 PM
Jonathan Nieder
 
Default Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot

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



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110526153624.GA24931@elie">http://lists.debian.org/20110526153624.GA24931@elie
 

Thread Tools




All times are GMT. The time now is 12:45 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org