Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles
Package: linux-2.6
Version: 3.0.0-3
Severity: important
Dear Maintainer,
I have some nonstandard console settings that require running /etc/init.d/kbd to configure console.
Using the newer console-setup is a non-starter for reasons that are not relevant at this time.
Somewhere in the last two months (it's hard to tell exactly), there was a regression such that
after restoring from hibernate, some console settings are not restored correctly. Running
/etc/init.d/kbd start successfully restores them.
Bug might be related to #647153. I had to reapply my original patch as the maintainer patch did not work for me.
-- Package-specific info:
** Version:
Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (ben@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011
** Command line:
auto BOOT_IMAGE=Lin ro root=801 resume=/dev/sda5
** Tainted: PO (4097)
* Proprietary module has been loaded.
* Out-of-tree module has been loaded.
** Kernel log:
[98776.388039] sr 0:0:0:0: [sr0] Add. Sense: Read of scrambled sector without authentication
[98776.388047] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 04 00 00 00 02 00
[98776.388055] end_request: I/O error, dev sr0, sector 4096
[98776.388060] Buffer I/O error on device sr0, logical block 512
[104211.293746] PM: Marking nosave pages: 000000000009e000 - 0000000000100000
[104211.293752] PM: Marking nosave pages: 00000000d7f90000 - 0000000100000000
[104211.294608] PM: Marking nosave pages: 00000000cc000000 - 00000000d0000000
[104211.294861] PM: Basic memory bitmaps created
[104211.294863] PM: Syncing filesystems ... done.
[104211.307845] Freezing user space processes ... (elapsed 0.01 seconds) done.
[104211.324293] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[104211.340610] PM: Preallocating image memory... done (allocated 474682 pages)
[104211.663624] PM: Allocated 1898728 kbytes in 0.32 seconds (5933.52 MB/s)
[104211.663662] Suspending console(s) (use no_console_suspend to debug)
[104211.663869] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
[104211.663960] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[104211.664466] serial 00:0b: disabled
[104211.664473] serial 00:0b: wake-up capability disabled by ACPI
[104211.664796] parport_pc 00:05: disabled
[104211.665152] ata2: port disabled. ignoring.
[104211.896227] HDA Intel 0000:00:07.0: PCI INT A disabled
[104211.912255] HDA Intel 0000:00:07.0: power state changed by ACPI to D3
[104211.912289] PM: freeze of devices complete after 248.581 msecs
[104211.912873] PM: late freeze of devices complete after 0.580 msecs
[104211.912940] ACPI: Preparing to enter system sleep state S4
[104211.914039] PM: Saving platform NVS memory
[104211.914644] Disabling non-boot CPUs ...
[104211.916090] CPU 1 is now offline
[104211.916791] PM: Creating hibernation image:
[104211.920062] PM: Need to copy 475120 pages
[104211.920062] PM: Normal pages needed: 475120 + 1024, available pages: 1572515
[104211.920062] PM: Restoring platform NVS memory
[104211.920062] PCI-DMA: Resuming GART IOMMU
[104211.920062] PCI-DMA: Restoring GART aperture settings
[104211.920062] Enabling non-boot CPUs ...
[104211.920062] Booting Node 0 Processor 1 APIC 0x1
[104211.920062] smpboot cpu 1: start_ip = 99000
[104211.916052] Switch to broadcast mode on CPU1
[104212.008348] NMI watchdog enabled, takes one hw-pmu counter.
[104212.012222] Switched to NOHz mode on CPU #1
[104212.012272] CPU1 is up
[104212.012626] ACPI: Waking up from system sleep state S4
[104212.014256] pata_amd 0000:00:06.0: restoring config space at offset 0x1 (was 0xb00001, writing 0xb00005)
[104212.014280] HDA Intel 0000:00:07.0: restoring config space at offset 0x1 (was 0xb00006, writing 0xb00002)
[104212.014365] ahci 0000:00:09.0: restoring config space at offset 0x1 (was 0xb00503, writing 0xb00507)
[104212.014871] nvidia 0000:02:00.0: restoring config space at offset 0xc (was 0xfebe0000, writing 0x0)
[104212.014878] nvidia 0000:02:00.0: restoring config space at offset 0x1 (was 0x100107, writing 0x100007)
[104212.014978] PM: early restore of devices complete after 1.064 msecs
[104212.151091] ohci_hcd 0000:00:02.0: setting latency timer to 64
[104212.151132] ehci_hcd 0000:00:02.1: setting latency timer to 64
[104212.151148] ohci_hcd 0000:00:04.0: setting latency timer to 64
[104212.151158] ehci_hcd 0000:00:04.1: setting latency timer to 64
[104212.151172] pata_amd 0000:00:06.0: setting latency timer to 64
[104212.151239] pci 0000:00:08.0: setting latency timer to 64
[104212.151248] ahci 0000:00:09.0: setting latency timer to 64
[104212.151545] pci 0000:00:0b.0: setting latency timer to 64
[104212.152768] HDA Intel 0000:00:07.0: power state changed by ACPI to D0
[104212.152774] HDA Intel 0000:00:07.0: power state changed by ACPI to D0
[104212.152780] HDA Intel 0000:00:07.0: power state changed by ACPI to D0
[104212.152784] HDA Intel 0000:00:07.0: power state changed by ACPI to D0
[104212.152793] HDA Intel 0000:00:07.0: PCI INT A -> Link[LAZA] -> GSI 21 (level, low) -> IRQ 21
[104212.152798] HDA Intel 0000:00:07.0: setting latency timer to 64
[104212.154231] ata2: port disabled. ignoring.
[104212.155346] parport_pc 00:05: activated
[104212.156548] serial 00:0b: activated
[104212.157140] sd 2:0:0:0: [sda] Starting disk
[104212.157204] sd 4:0:0:0: [sdb] Starting disk
[104212.210022] usb usb4: root hub lost power or was reset
[104212.210047] usb usb2: root hub lost power or was reset
[104212.210056] ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
[104212.212058] usb usb3: root hub lost power or was reset
[104212.213763] forcedeth 0000:00:0a.0: irq 41 for MSI/MSI-X
[104212.213978] forcedeth 0000:00:0a.0: eth0: no link during initialization
[104212.214316] usb usb1: root hub lost power or was reset
[104212.214326] ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
[104212.316563] ata1.01: ACPI cmd ef/03:21:00:00:00:b0 (SET FEATURES) filtered out
[104212.316568] ata1.01: ACPI cmd ef/03:01:00:00:00:b0 (SET FEATURES) filtered out
[104212.316572] ata1.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[104212.324512] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 (SET FEATURES) filtered out
[104212.324518] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[104212.324530] ata1: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:120:0x11)
[104212.324535] ata1: nv_mode_filter: 0x39f&0x739f->0x39f, BIOS=0x0 (0xc5000000) ACPI=0x39f (30:120:0x11)
[104212.340434] ata1.00: configured for UDMA/66
[104212.356490] ata1.01: configured for MWDMA2
[104212.472213] ata7: SATA link down (SStatus 0 SControl 300)
[104212.472228] ata8: SATA link down (SStatus 0 SControl 300)
[104212.472242] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[104212.472254] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[104212.474387] ata3.00: configured for UDMA/133
[104212.475068] ata5.00: configured for UDMA/133
[104212.476212] ata4: SATA link down (SStatus 0 SControl 300)
[104212.476226] ata6: SATA link down (SStatus 0 SControl 300)
[104212.836222] usb 3-1: reset low speed USB device number 2 using ohci_hcd
[104213.504218] usb 4-1: reset low speed USB device number 2 using ohci_hcd
[104213.863288] PM: restore of devices complete after 1712.271 msecs
[104213.865842] PM: Image restored successfully.
[104213.865844] Restarting tasks ... done.
[104213.869238] PM: Basic memory bitmaps freed
[104213.869246] video LNXVIDEO:00: Restoring backlight state
[104214.907483] forcedeth 0000:00:0a.0: eth0: link up
** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 1009
board_vendor: ASUSTeK Computer INC.
board_name: M3N78-VM
board_version: Rev X.0x
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation C77 [GeForce 8200] [10de:0849] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:82f2]
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
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at f0000000 (64-bit, prefetchable) [size=128M]
Region 3: Memory at fa000000 (64-bit, prefetchable) [size=32M]
Region 5: I/O ports at ec00 [size=128]
[virtual] Expansion ROM at febe0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 004 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-3.0.0-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.44
it initramfs-tools [linux-initramfs-tool] 0.106
ii linux-base 3.5
ii module-init-tools 8-2
Versions of packages linux-image-3.0.0-1-amd64 recommends:
ii firmware-linux-free 3.1
Versions of packages linux-image-3.0.0-1-amd64 suggests:
ii lilo 1:23.2-4
pn linux-doc-3.0.0 <none>
Versions of packages linux-image-3.0.0-1-amd64 is related to:
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-linux <none>
pn firmware-linux-nonfree <none>
pn firmware-qlogic <none>
pn firmware-ralink <none>
pn xen-hypervisor <none>
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120707170439.13263.47356.reportbug@nova
07-07-2012, 05:15 PM
Jonathan Nieder
Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles
Hi,
Joshua wrote:
> Version: 3.0.0-3
[...]
> I have some nonstandard console settings that require running
> /etc/init.d/kbd to configure console. Using the newer console-setup
> is a non-starter for reasons that are not relevant at this time.
>
> Somewhere in the last two months (it's hard to tell exactly), there
> was a regression such that after restoring from hibernate, some
> console settings are not restored correctly. Running /etc/init.d/kbd
> start successfully restores them.
Thanks for reporting. Before investigating further, a few questions:
The Debian kernel team does not maintain 3.0.y any more. Does a 3.2.y
or 3.4.y kernel reproduce the problem?
You mentioned that this is a regression. What is the oldest broken
kernel and newest non-broken one you know of? (/var/log/dpkg.log
might help to jog memory, and there are precompiled historical kernels
at http://snapshot.debian.org/ if you need to test some.)
Can you more precisely describe the symptoms? If I had the same
hardware as you, what steps should I perform to reproduce the bug,
what is the expected result, what happens instead, and how does the
difference indicate a bug?
Hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120707171523.GB30924@burratino
07-07-2012, 06:31 PM
Joshua Hudson
Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles
For some reason a new apt-get dist-upgrade fixed bug. A new kernel
package was pulled but the version did not change.
On 7/7/12, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi,
>
> Joshua wrote:
>
>> Version: 3.0.0-3
> [...]
>> I have some nonstandard console settings that require running
>> /etc/init.d/kbd to configure console. Using the newer console-setup
>> is a non-starter for reasons that are not relevant at this time.
>>
>> Somewhere in the last two months (it's hard to tell exactly), there
>> was a regression such that after restoring from hibernate, some
>> console settings are not restored correctly. Running /etc/init.d/kbd
>> start successfully restores them.
>
> Thanks for reporting. Before investigating further, a few questions:
>
> The Debian kernel team does not maintain 3.0.y any more. Does a 3.2.y
> or 3.4.y kernel reproduce the problem?
>
> You mentioned that this is a regression. What is the oldest broken
> kernel and newest non-broken one you know of? (/var/log/dpkg.log
> might help to jog memory, and there are precompiled historical kernels
> at http://snapshot.debian.org/ if you need to test some.)
>
> Can you more precisely describe the symptoms? If I had the same
> hardware as you, what steps should I perform to reproduce the bug,
> what is the expected result, what happens instead, and how does the
> difference indicate a bug?
>
> Hope that helps,
> Jonathan
>
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CA+jjjYSEeKF8kd+6iiHej1soenO04GQUcMtxhNK4vtG7zcOuQ g@mail.gmail.com">http://lists.debian.org/CA+jjjYSEeKF8kd+6iiHej1soenO04GQUcMtxhNK4vtG7zcOuQ g@mail.gmail.com
07-07-2012, 06:35 PM
Jonathan Nieder
Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles
Hi,
Joshua Hudson wrote:
> For some reason a new apt-get dist-upgrade fixed bug. A new kernel
> package was pulled but the version did not change.
You can get the version of the kernel package with
dpkg-query -W linux-image-$(uname -r)
or
cat /proc/version
Perhaps the package name (which includes an ABI name like
"3.0.0-1-amd64") did not change but the version number (e.g. 3.0.0-3)
did change.
Glad to hear your system is working again. Please don't forget that
the packaged 3.0.y kernels are way out of date, though.
Ciao,
Jonathan
[*] http://kernel-handbook.alioth.debian.org/ch-versions.html#s-version-types
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120707183542.GB3457@burratino
07-08-2012, 07:17 PM
Joshua Hudson
Bug#680649: linux-image-3.0.0-1-amd64: Restoring from hibernate requires rerunning /etc/init.d/kbd start manually to fix broken consoles
Package version changed from 3.0.0-2 to 3.0.0.3.
Incidentally I have upgraded to 3.2 and the problem does not occur there either.
On 7/7/12, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi,
>
> Joshua Hudson wrote:
>
>> For some reason a new apt-get dist-upgrade fixed bug. A new kernel
>> package was pulled but the version did not change.
>
> You can get the version of the kernel package with
>
> dpkg-query -W linux-image-$(uname -r)
>
> or
>
> cat /proc/version
>
> Perhaps the package name (which includes an ABI name like
> "3.0.0-1-amd64") did not change but the version number (e.g. 3.0.0-3)
> did change.
>
> Glad to hear your system is working again. Please don't forget that
> the packaged 3.0.y kernels are way out of date, though.
>
> Ciao,
> Jonathan
>
>[*]
> http://kernel-handbook.alioth.debian.org/ch-versions.html#s-version-types
>
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CA+jjjYQK_NSaWcZSTB7ckaF0ViDietF9seAMQi=WZqOzKZyhm g@mail.gmail.com