Bug#622828: recovery
Contrary to my earlier conclusion, the upgrade did not delete older images. It appears a ramdisk generation change may have included a bad module whose loading crashed the system later. I could not boot other images because my Grub 2 configuration file grub.cfg missed the corresponding initrd lines. The latter were missing probably because of a ramdisk generation failure. This resulted in a cryptic error message at the boot failure about inability to find a root filesystem in a certain (0,0) disk. As I mentioned earlier, after loading to a shell prompt by editing the linux line in grub boot screen and adding init=/bin/bash, I could disable swapping with swapoff -a, remount the root partition in a read-write mode and start networking. This allowed me to update packages in aptitude. I also had to boot off a recent Debian installer CD-R disk, http://cdimage.debian.org/cdimage/daily-builds/unstable/current/i386/iso-cd/ because I did not understand the reason for the (0,0) root disk mount crash. I also suspect that my manual invocation of update-initramfs failed to include all required modules. In the end, I dropped to shell from the rescue disk, mounted my root filesystem with mount -t ext3 /dev/sda1 /mnt and changed to it with chroot /mnt. I then re-generated the initial ramdisk images with update-initramfs -k 2.6.32-5-686 -d update-initramfs -k 2.6.32-5-686 -c and same commands for some other kernel versions. This allowed me to boot my system in full with 2.6.32-5-686 which turned to be the original kernel version that worked long time for me. (The newer 2.6.38..-686 kernel on which 2.6-686 depends crashes in the Wi-Fi module mac80211 calling a function in cfg80211 when I attempt to associate with my Wi-Fi router. I logged that issue under bug #622833). Still, I do not understand how possible differences in update-initramfs could cause a libata kernel crash. -- -- 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/20110422135659.ga5...@ei.homeip.net
Bug#622828: corrected
Thanks for quashing my hasty conclusion about the timing of the kernel crash. I now see that the crash occurred after the ramdisk stage succeeded. Probably, this may have something to do with memory paging to disk. I could boot to the shell, disable swapping, launch udev, resolvconf, dnsmasq, networking, submit the bug, update packages with aptitude. I could not find a work-around. I cannot remember the version of my last successful image as the upgrade deleted it. Perhaps, I can look up my logs to find the version. My online search showed only the current unstable and stable packages, both of which failed to boot for different reasons. The earlier (oldstable?) package 2.6.26 bailed to a ramdisk shell prompt after failing to run a newer udev daemon. Perhaps, the package information for that earlier image could require a ramdisk make tool and/or ramdisk components relevant to that version. I sent screenshots of the stack trace just before receiving your email requesting them. I see the screen shots in the log of this bug report. Cheers. --
Bug#622828: linux-image-2.6.32-5-686: kernel panic mentions libata in the stack trace
Package: linux-2.6 Version: 2.6.32-30 Severity: critical Justification: breaks the whole system Both normal and safe boot modes panicked when running the ram disk image. Worse, the upgrade DELETED the earlier kernel image and ram disk image. I managed to boot by editing the safe mode command line and adding the option init=/bin/bash. When the kernel panicks, it shows a stack trace mentioning libata. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 04:01:41 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=281d76c7-ee09-4f0e-825b-425e95d75878 ro single init=/bin/bash ** Not tainted ** Kernel log: [3.331507] PM: Checking hibernation image. [3.331689] PM: Error -22 checking image file [3.331692] PM: Resume from disk failed. [3.338369] PM: Marking nosave pages: 0009f000 - 0010 [3.338378] PM: Basic memory bitmaps created [3.345712] PM: Basic memory bitmaps freed [3.372024] usb 2-1: new full speed USB device using ohci_hcd and address 2 [3.401886] kjournald starting. Commit interval 5 seconds [3.401897] EXT3-fs: mounted filesystem with ordered data mode. [3.568751] usb 2-1: New USB device found, idVendor=03f0, idProduct=0517 [3.568808] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.568857] usb 2-1: Product: hp LaserJet 1000 [3.568903] usb 2-1: Manufacturer: Hewlett-Packard [3.569118] usb 2-1: configuration #1 chosen from 1 choice [7.505287] usb-storage: device scan complete [7.506404] scsi 6:0:0:0: Direct-Access RIM BlackBerry SD0003 PQ: 0 ANSI: 4 CCS [7.507080] sd 6:0:0:0: Attached scsi generic sg2 type 0 [7.508515] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 184.561988] EXT3 FS on sda1, internal journal [ 1241.810372] 30udev[382]: starting version 167 [ 1242.505471] 30udev[405]: renamed network interface eth0 to tp [ 1243.710686] input: PC Speaker as /devices/platform/pcspkr/input/input2 [ 1244.157244] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 1244.250681] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 1244.250866] ACPI: Power Button [PWRB] [ 1244.251036] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 1244.251271] ACPI: Power Button [PWRF] [ 1244.613408] processor LNXCPU:00: registered as cooling_device0 [ 1244.614971] processor LNXCPU:01: registered as cooling_device1 [ 1244.619420] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x0517 [ 1244.619503] usbcore: registered new interface driver usblp [ 1244.625601] parport_pc 00:06: reported by Plug and Play ACPI [ 1244.627407] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 1244.639042] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 1245.015484] ali1535_smbus :00:1e.1: ALI1535_smb region uninitialized - upgrade BIOS? [ 1245.015576] ali1535_smbus :00:1e.1: ALI1535 not detected, module not inserted. [ 1245.025103] ali15x3_smbus :00:1e.1: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr [ 1245.025165] ali15x3_smbus :00:1e.1: ALI15X3 not detected, module not inserted. [ 1245.089649] alim7101_wdt: Steve Hill st...@navaho.co.uk. [ 1245.089710] alim7101_wdt: ALi 1543 South-Bridge not present - WDT not set [ 1245.404977] cfg80211: Using static regulatory domain info [ 1245.405031] cfg80211: Regulatory domain: US [ 1245.405076] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 1245.405130] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [ 1245.405178] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405226] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405274] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405322] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405369] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 1245.405922] cfg80211: Calling CRDA for country: US [ 1245.609148] adm8211 :03:11.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [ 1245.619583] :03:11.0 (adm8211): Channel range: 1 - 11 [ 1245.619588] :03:11.0 (adm8211): RFtype=1 BBPtype=1 Specific BBP=0 Transceiver=0 [ 1246.177701] phy0: Selected rate control algorithm 'minstrel' [ 1246.178756] phy0: hwaddr 00:04:e2:7b:70:6b, Rev 0x11 [ 1246.189113] 30udev[403]: renamed network interface wlan0 to wl [ 1246.938086] HDA Intel :00:1d.0: PCI INT C - GSI 22 (level, low) - IRQ 22 [ 1246.938155] hda_intel: position_fix set to 1 for device 1043:81b3 [ 1247.383775] input: HDA Digital PCBeep as /devices/pci:00/:00:1d.0/input/input5 [ 1252.897954] usblp0: removed [ 1323.238716] r8169: tp: link down [ 1323.238987] ADDRCONF(NETDEV_UP): tp: link is not ready [ 1332.520717] ADDRCONF(NETDEV_UP): wl: link is not ready [
Bug#622833: linux-image-2.6.38-2-686: kernel panic in mac80211
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
bad_area_nosemaphore, no_context (from the least to the most recently
called).
I will send screenshots of the trace.
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
not available
** Network interface configuration:
auto tp
iface tp inet static
address 192.168.3.1
netmask 255.255.255.0
network 192.168.3.0
broadcast 192.168.3.255
auto wl
iface wl inet static
address 192.168.2.172
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
dns-nameservers 192.168.2.1
wpa-ssid D3
wpa-bsssid 00:21:91:F8:36:6E
wpa-psk *
up sleep 5; /sbin/iwconfig ${IFACE}
up /sbin/ip route add 224.0.0.0/4 dev ${IFACE}
iface tun6to4 inet6 v4tunnel
address $(printf 2002:%02x%02x:%02x%02x::1 \
$(printf %s\r\n%s\r\n\r\n \
GET / HTTP/1.1 \
Host: checkip.dyndns.org \
| /bin/nc checkip.dyndns.org 80 \
| /bin/sed -ne 's/.*Address: \([.0-9]*\).*/\1/p' \
| tr '.' ' ') \
)
netmask 16
endpoint 192.88.99.1
local any
ttl 64
up /sbin/ip -6 route add 2000::/3 dev tun6to4
down /sbin/ip -6 route flush dev tun6to4
auto lo
iface lo inet loopback
** PCI devices:
00:00.0 Host bridge [0600]: ATI Technologies Inc Radeon Xpress 200 Host Bridge
[1002:5a33] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:819a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort-
TAbort- MAbort+ SERR- PERR- INTx-
Latency: 64
Region 3: Memory at e000 (64-bit, non-prefetchable) [size=512M]
00:01.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a3f]
(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=medium TAbort-
TAbort- MAbort- SERR- PERR- INTx-
Latency: 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: c000-cfff
Memory behind bridge: c000-dfdf
Prefetchable memory behind bridge: a000-afff
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: [b0] Subsystem: ATI Technologies Inc RS480 PCI Bridge
[1002:5a3f]
00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
(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: 64 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: d000-dfff
Memory behind bridge: dfe0-dfef
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: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v1) Root Port (Slot-), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 64ns,
L1 1us
ExtTag+ RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr-
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x2, ASPM L0s L1, Latency
L0 64ns, L1 1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
