Description of problem: Some weird stuff is happening to my encrypted LVM container in /dev/sda2 on resume. It was purely set up with the graphical Mageia 3 install, and since the upgrade to Mageia 4 I observe this sometimes: [267948.430316] ACPI: Low-level resume complete [267948.430371] PM: Restoring platform NVS memory [267948.431442] CPU0: Thermal monitoring handled by SMI [267948.431559] Enabling non-boot CPUs ... [267948.431604] smpboot: Booting Node 0 Processor 1 APIC 0x1 [267948.442776] Disabled fast string operations [267948.442798] CPU1: Thermal monitoring handled by SMI [267948.445309] CPU1 is up [267948.445330] smpboot: Booting Node 0 Processor 2 APIC 0x2 [267948.456367] Disabled fast string operations [267948.456388] CPU2: Thermal monitoring handled by SMI [267948.459243] CPU2 is up [267948.459302] smpboot: Booting Node 0 Processor 3 APIC 0x3 [267948.470816] Disabled fast string operations [267948.470835] CPU3: Thermal monitoring handled by SMI [267948.473739] CPU3 is up [267948.479366] ACPI: Waking up from system sleep state S3 [267948.684600] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI [267948.706584] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI [267948.739689] PM: noirq resume of devices complete after 88.136 msecs [267948.739964] PM: early resume of devices complete after 0.232 msecs [267948.740031] i915 0000:00:02.0: setting latency timer to 64 [267948.740084] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X [267948.740177] ehci-pci 0000:00:1a.0: setting latency timer to 64 [267948.740477] snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X [267948.740568] ehci-pci 0000:00:1d.0: setting latency timer to 64 [267948.740585] ahci 0000:00:1f.2: setting latency timer to 64 [267948.753958] [drm] Wrong MCH_SSKPD value: 0x16040307 [267948.753960] [drm] This can cause pipe underruns and display issues. [267948.753961] [drm] Please upgrade your BIOS to fix this. [267948.948664] usb 2-1.4: reset high-speed USB device number 3 using ehci-pci [267949.056457] ata2: SATA link down (SStatus 0 SControl 300) [267949.058473] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [267949.061646] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [267949.061652] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [267949.061655] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [267949.061938] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [267949.063339] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [267949.063344] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [267949.063347] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [267949.063536] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1 [267949.063542] ata1.00: configured for UDMA/133 [267949.063690] sd 0:0:0:0: [sda] Starting disk [267949.645454] tpm_tis 00:09: TPM is disabled/deactivated (0x6) [267949.722495] PM: resume of devices complete after 982.651 msecs [267949.722925] PM: Finishing wakeup. [267949.723017] iwlwifi 0000:02:00.0: no hotplug settings from platform [267949.723076] rtsx_pci 0000:03:00.0: no hotplug settings from platform [267949.723196] atl1c 0000:08:00.0: no hotplug settings from platform [267949.723291] usb 2-1.1: USB disconnect, device number 45 [267949.722931] Restarting tasks ... done. [267949.729463] video LNXVIDEO:00: Restoring backlight state [267949.829385] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [267949.909526] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S [267949.916916] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3 [267949.948338] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [267949.953531] atl1c 0000:08:00.0: irq 46 for MSI/MSI-X [267949.966328] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [268045.659101] wlan0: authenticate with 00:0b:86:28:91:a1 [268045.663238] wlan0: send auth to 00:0b:86:28:91:a1 (try 1/3) [268045.671166] wlan0: authenticated [268045.671380] iwlwifi 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP [268045.671387] iwlwifi 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP [268045.671832] wlan0: associate with 00:0b:86:28:91:a1 (try 1/3) [268045.690070] wlan0: RX AssocResp from 00:0b:86:28:91:a1 (capab=0x31 status=0 aid=31) [268045.693708] wlan0: associated [268045.693774] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [270129.266924] JFS: nTxBlock = 8192, nTxLock = 65536 [270129.296290] NTFS driver 2.1.30 [Flags: R/O MODULE]. [270129.342802] QNX4 filesystem 0.2.3 registered. [270129.855337] EXT2-fs (sda2): error: unable to read superblock [270129.859097] EXT4-fs (sda2): unable to read superblock [270129.862111] cramfs: wrong magic [270129.887243] FAT-fs (sda2): bogus number of reserved sectors [270129.887250] FAT-fs (sda2): Can't find a valid FAT filesystem [270129.891009] XFS (sda2): bad magic number [270129.891018] ffff880036efc000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [270129.891022] ffff880036efc010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [270129.891042] ffff880036efc020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [270129.891047] ffff880036efc030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ [270129.891052] XFS (sda2): Internal error xfs_sb_read_verify at line 637 of file fs/xfs/xfs_sb.c. Caller 0xffffffffa0995525 [270129.891077] CPU: 0 PID: 317 Comm: kworker/0:1H Not tainted 3.12.9-desktop-1.mga4 #1 [270129.891079] Hardware name: LENOVO 3045A64/3045A64, BIOS 8QET54WW (1.15 ) 01/11/2012 [270129.891112] Workqueue: xfslogd xfs_buf_iodone_work [xfs] [270129.891117] 0000000000000001 ffff8800378dfd68 ffffffff8161051f ffff88001d29f000 [270129.891122] ffff8800378dfd80 ffffffffa099864b ffffffffa0995525 ffff8800378dfdb8 [270129.891127] ffffffffa09986a5 0000027d00000000 ffff880023573b00 0000000000000016 [270129.891133] Call Trace: [270129.891143] [<ffffffff8161051f>] dump_stack+0x45/0x56 [270129.891169] [<ffffffffa099864b>] xfs_error_report+0x3b/0x40 [xfs] [270129.891192] [<ffffffffa0995525>] ? xfs_buf_iodone_work+0x85/0xf0 [xfs] [270129.891217] [<ffffffffa09986a5>] xfs_corruption_error+0x55/0x80 [xfs] [270129.891255] [<ffffffffa09ec5b0>] xfs_sb_read_verify+0x130/0x150 [xfs] [270129.891290] [<ffffffffa0995525>] ? xfs_buf_iodone_work+0x85/0xf0 [xfs] [270129.891309] [<ffffffffa0995525>] xfs_buf_iodone_work+0x85/0xf0 [xfs] [270129.891315] [<ffffffff8107b2bc>] process_one_work+0x17c/0x410 [270129.891319] [<ffffffff8107bea1>] worker_thread+0x121/0x3b0 [270129.891324] [<ffffffff8107bd80>] ? rescuer_thread+0x320/0x320 [270129.891328] [<ffffffff810828b0>] kthread+0xc0/0xd0 [270129.891332] [<ffffffff810827f0>] ? kthread_create_on_node+0x120/0x120 [270129.891338] [<ffffffff8161f6cc>] ret_from_fork+0x7c/0xb0 [270129.891359] [<ffffffff810827f0>] ? kthread_create_on_node+0x120/0x120 [270129.891363] XFS (sda2): Corruption detected. Unmount and run xfs_repair [270129.891377] XFS (sda2): SB validate failed with error 22. [270129.897463] EXT3-fs (sda2): error: unable to read superblock [270129.904424] FAT-fs (sda2): bogus number of reserved sectors [270129.904431] FAT-fs (sda2): Can't find a valid FAT filesystem [270129.912778] MINIX-fs: unable to read superblock [270129.917998] attempt to access beyond end of device [270129.918007] sda2: rw=0, want=3, limit=2 [270129.918013] hfsplus: unable to find HFS+ superblock [270129.921301] qnx4: wrong fsid in superblock. [270129.923820] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [270129.926167] hfs: can't find a HFS filesystem on dev sda2 [270132.947222] loop: module loaded jonas@Cyberman#14: I am not sure why this is happening or what is going on, but it doesnt look like it should be happening. The system seems to operate normally and I never had issues with like the root partition actually failing to get mounted after boot or suspend which I am aware of. How reproducible: Unreliable, e.g. last resume there was nothing like that. Steps to Reproduce: 1. ??? 2. Weird log messages Reproducible: Steps to Reproduce:
Let me guess, you use grub2 ?
CC: (none) => tmb
I haven't changed a thing. This is an original Mageia 3 install upgraded to Mageia 4. So it uses whatever Mageia 3 installed. If necessary I can confirm grub2 usage for you, but for that it would be awesome if you gave me a hint on how to do that. But most distributions use grub2 by now anyway, don't they? Last time I fiddled around with a debian stable it seemed to use grub2.
Any news here?
CC: (none) => fri
What reports the "detectloader" command?
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD