[arch-general] linux-3.5.0-1 enters [testing]
Hi guys, Upstream changes: http://kernelnewbies.org/LinuxChanges Please report any issues that arise. Thanks. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
2012/7/23 Tobias Powalowski <tobias.powalowski@googlemail.com>:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that arise. Thanks.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Booted flawlessly. Only issues is vbox modules, but I can leave a day or two without vbox :) Besides this, so far so good. Here is my lspci : [fred@fredo-arch ~]$ lspci 00:00.0 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a1) 00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2) 00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2) 00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2) 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3) 00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3) 00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1) 00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2) 00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2) 00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control 02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) 02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) Great work as usual. My 2 cents :D -- Frederic Bezies fredbezies@gmail.com
Op maandag 23 juli 2012 15:43:12 schreef fredbezies:
2012/7/23 Tobias Powalowski <tobias.powalowski@googlemail.com>:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that arise. Thanks.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Booted flawlessly. Only issues is vbox modules, but I can leave a day or two without vbox :)
Besides this, so far so good. Here is my lspci :
[fred@fredo-arch ~]$ lspci 00:00.0 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a1) 00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2) 00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2) 00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2) 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3) 00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3) 00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1) 00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2) 00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2) 00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2) 00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control 02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) 02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
Great work as usual.
My 2 cents :D
-- Frederic Bezies fredbezies@gmail.com
Frederic, do you have community-testing enabled? the virtualbox modules should be there. --Ike
2012/7/23 Ike Devolder <ike.devolder@gmail.com>:
Op maandag 23 juli 2012 15:43:12 schreef fredbezies:
2012/7/23 Tobias Powalowski <tobias.powalowski@googlemail.com>:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that arise. Thanks.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Booted flawlessly. Only issues is vbox modules, but I can leave a day or two without vbox :)
[...]
do you have community-testing enabled? the virtualbox modules should be there.
I do have it enabled. Looks like packages were *not totally* spread when I done my sudo pacman -Syu in order to get linux-3.5.0-1. Bad luck, so :D -- Frederic Bezies fredbezies@gmail.com
Am 23.07.2012 14:57, schrieb Tobias Powalowski:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that arise. Thanks.
greetings tpowa
Booted fine for me as well. I was affected by the backlight regression, so its nice to see this included into mainline now ;). Best regards, Karol Babioch
Am 23.07.2012 16:11, schrieb Karol Babioch:
Am 23.07.2012 14:57, schrieb Tobias Powalowski:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that arise. Thanks.
greetings tpowa
Booted fine for me as well. I was affected by the backlight regression, so its nice to see this included into mainline now ;).
Best regards, Karol Babioch
hi, I get a "systemd-udevd not tainted" error with a stack trace on boot on my Sony Vaio VPCS11C5E. Other than that the system seems to work fine. Since you happen to have a similiar Vaio model, can you confirm any of this, Karol? dmesg: http://pastebin.com/qguWkgR4 (line 853) systemctl status systemd-udevd.service: systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Mon, 23 Jul 2012 17:58:20 +0200; 4min 40s ago Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 179 (systemd-udevd) CGroup: name=systemd:/system/systemd-udevd.service └ 179 /usr/lib/systemd/systemd-udevd Jul 23 17:58:20 mus-laptop systemd-udevd[179]: worker [210] terminated by signal 9 (Killed) Jul 23 17:58:20 mus-laptop systemd-udevd[179]: worker [210] failed while handling '/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/SNY5001:00' Jul 23 17:58:20 mus-laptop su[296]: pam_unix(su:session): session opened for user mus by (uid=0) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. best regards, Marius
Hi, Am 23.07.2012 18:11, schrieb Marius T.:
I get a "systemd-udevd not tainted" error with a stack trace on boot on my Sony Vaio VPCS11C5E. Other than that the system seems to work fine. Since you happen to have a similiar Vaio model, can you confirm any of this, Karol?
Interestingly I don't get any of this. I've tried it with both the old systemd 186-2 (http://pastebin.com/mvVK763V) as well as the new 187-2 (http://pastebin.com/QzhFSfhF) one. What else have you upgraded? So far I've upgraded the following packages from testing amd/or community-testing: [2012-07-23 18:21] upgraded linux-headers (3.4.6-1 -> 3.5-1) [2012-07-23 18:22] upgraded linux-docs (3.4.6-1 -> 3.5-1) [2012-07-23 18:22] upgraded linux (3.4.6-1 -> 3.5-1) [2012-07-23 18:22] upgraded virtualbox-modules (4.1.18-4 -> 4.1.18-5) [2012-07-23 18:26] upgraded systemd-sysvcompat (186-2 -> 187-2) [2012-07-23 18:26] upgraded libsystemd (186-2 -> 187-2) [2012-07-23 18:26] upgraded systemd-tools (186-2 -> 187-2) [2012-07-23 18:26] upgraded systemd (186-2 -> 187-2) Interestingly enough my dmesg output still contains the following: [ 0.904375] systemd-udevd[51]: starting version 186 Yours is reporting version 187 here, so I'm not entirely sure what is going on. Is there something wrong with the packages?
systemctl status systemd-udevd.service:
[johnpatcher@vpcs ~]$ systemctl status systemd-udevd.service systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Mon, 23 Jul 2012 18:27:08 +0200; 8min ago Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 213 (systemd-udevd) CGroup: name=systemd:/system/systemd-udevd.service └ 213 /usr/lib/systemd/systemd-udevd Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. Best regards, Karol Babioch
On Mon, 23 Jul 2012 18:36:52 +0200 Karol Babioch <karol@babioch.de> wrote:
Hi,
Am 23.07.2012 18:11, schrieb Marius T.:
I get a "systemd-udevd not tainted" error with a stack trace on boot on my Sony Vaio VPCS11C5E. Other than that the system seems to work fine. Since you happen to have a similiar Vaio model, can you confirm any of this, Karol?
Interestingly I don't get any of this. I've tried it with both the old systemd 186-2 (http://pastebin.com/mvVK763V) as well as the new 187-2 (http://pastebin.com/QzhFSfhF) one.
What else have you upgraded? So far I've upgraded the following packages from testing amd/or community-testing:
[2012-07-23 18:21] upgraded linux-headers (3.4.6-1 -> 3.5-1) [2012-07-23 18:22] upgraded linux-docs (3.4.6-1 -> 3.5-1) [2012-07-23 18:22] upgraded linux (3.4.6-1 -> 3.5-1) [2012-07-23 18:22] upgraded virtualbox-modules (4.1.18-4 -> 4.1.18-5) [2012-07-23 18:26] upgraded systemd-sysvcompat (186-2 -> 187-2) [2012-07-23 18:26] upgraded libsystemd (186-2 -> 187-2) [2012-07-23 18:26] upgraded systemd-tools (186-2 -> 187-2) [2012-07-23 18:26] upgraded systemd (186-2 -> 187-2)
Interestingly enough my dmesg output still contains the following:
[ 0.904375] systemd-udevd[51]: starting version 186
Yours is reporting version 187 here, so I'm not entirely sure what is going on. Is there something wrong with the packages?
Rebuild your initramfs.
systemctl status systemd-udevd.service:
[johnpatcher@vpcs ~]$ systemctl status systemd-udevd.service systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Mon, 23 Jul 2012 18:27:08 +0200; 8min ago Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 213 (systemd-udevd) CGroup: name=systemd:/system/systemd-udevd.service └ 213 /usr/lib/systemd/systemd-udevd
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Best regards, Karol Babioch
-- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Hi, Am 23.07.2012 18:46, schrieb Leonid Isaev:
Rebuild your initramfs.
Of course, I have completely forgotten that I've updated the kernel first this time. Quite stupid, sorry for the noise. Nevertheless I don't get any errors: http://pastebin.com/NwmNAciN So, I'm afraid this is something specific to your system :(. Best regards, Karol Babioch
Am 23.07.2012 19:10, schrieb Karol Babioch:
Hi,
Am 23.07.2012 18:46, schrieb Leonid Isaev:
Rebuild your initramfs. Of course, I have completely forgotten that I've updated the kernel first this time. Quite stupid, sorry for the noise.
Nevertheless I don't get any errors: http://pastebin.com/NwmNAciN
So, I'm afraid this is something specific to your system :(.
Best regards, Karol Babioch
I found the culprit: I have a custom udev rule which watches for a HDMI hotplug event and then starts a script which configures the screens with xrandr accordingly. When I disable it, 3.5 boots up without errors. Still strange that it works fine in 3.4.6 (I downgraded to confirm it). I know that you are not supposed to run long scripts from udev rules, maybe this has something to do with it (although the script shouldn't take much time). I'm gonna have a look into it... thanks and best regards, Marius
Am 23.07.2012 19:24, schrieb Marius T.:
Am 23.07.2012 19:10, schrieb Karol Babioch:
Hi,
Am 23.07.2012 18:46, schrieb Leonid Isaev:
Rebuild your initramfs. Of course, I have completely forgotten that I've updated the kernel first this time. Quite stupid, sorry for the noise.
Nevertheless I don't get any errors: http://pastebin.com/NwmNAciN
So, I'm afraid this is something specific to your system :(.
Best regards, Karol Babioch
I found the culprit: I have a custom udev rule which watches for a HDMI hotplug event and then starts a script which configures the screens with xrandr accordingly. When I disable it, 3.5 boots up without errors. Still strange that it works fine in 3.4.6 (I downgraded to confirm it).
I know that you are not supposed to run long scripts from udev rules, maybe this has something to do with it (although the script shouldn't take much time). I'm gonna have a look into it...
thanks and best regards, Marius sorry, turns out I spoke too soon, this wasn't related to the udev rule, it just doesn't happen on every boot. sometimes it also gets stuck at the stack trace and I have to do a hard reset.
suspending is also broken, it gets stuck with the following: Freezing user space processes ... (elapsed 0.01 seconds) done. Freezing remaining freezable tasks... (elapsed 0.01 seconds) done. PM: Entering mem sleep Suspending console(s) (use no_console_suspend to debug) god damnit, I hate this laptop, one issue after the other... :(
On Mon, Jul 23, 2012 at 7:24 PM, Marius T. <mus.svz@googlemail.com> wrote:
I know that you are not supposed to run long scripts from udev rules, maybe this has something to do with it (although the script shouldn't take much time). I'm gonna have a look into it...
A short-running script to configure something should be fine. Just no "daemons". -t
On 07/23/2012 08:57 AM, Tobias Powalowski wrote:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that arise. Thanks.
Thank you for getting this to us so quickly :-) 1 machine in testing so far - ecnrypted home/swap - intel graphics, iwlagn wireless - as of now no problems. I am aware of the AP mode intel wireless problem, tho' it seems it will be pushed to stable shortly. (https://lkml.org/lkml/2012/7/23/38) gene
My integrated USB Wacom tablet ISDv4 (056a:0094) is no longer recognized, the wacom kernel module doesn't get loaded, the device shows up in lsusb, but isn't even mentioned in Xorg.0.log (xf86-input-wacom 0.16.0-1) Then, the system completely froze an hour ago, not even sysrqs were working. Nothing was logged after the freeze.
Am 23.07.2012 14:57, schrieb Tobias Powalowski:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that arise. Thanks.
greetings tpowa There seem to be no serious regression, any objections if 3.5.0-2 move to [core] ? greetings tpowa
-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On 08/01/2012 11:38 AM, Tobias Powalowski wrote:
Am 23.07.2012 14:57, schrieb Tobias Powalowski: There seem to be no serious regression, any objections if 3.5.0-2 move to [core] ? greetings tpowa
I am not using [testing], but are you guys aware of the following power regression [0]? Is that a no-go or do you want to update the kernel and incorporate a soon-to-come patch ASAP? Greetings, Christoph [0]: http://www.phoronix.com/scan.php?page=news_item&px=MTE1MTI
On 08/01/2012 05:38 AM, Tobias Powalowski wrote:
There seem to be no serious regression, any objections if 3.5.0-2 move to [core] ? greetings tpowa
I am noticing some network hangs with my Intel N6300 wifi using iwlagn driver. No problems under 3.4, but now I get hangs. I connect fine and traffic starts but then hangs. Oddly, ping works but no tcp traffic flows. e.g. I can ssh out, but then my ssh becomes totallly unresponsive after a small amount of traffic. While this ssh is hung I can ping same host. Killing ssh I can reconnect with no problem, but then it will hang. It is also somewhat intermittent. It may be similar to this: http://comments.gmane.org/gmane.linux.kernel.wireless.general/95505 regards, gene
On Mon, Jul 23, 2012 at 3:57 PM, Tobias Powalowski <tobias.powalowski@googlemail.com> wrote:
Please report any issues that arise.
I have an interesting problem on my laptop: about 1 in 3 times during boot, the initrd fails to find the root file system, which is located on LVM. I'm quite sure that this started after upgrading to linux 3.5.0-1 Booting via EFI on Dell Latitude E6410, disks configured in AHCI mode, x86_64, using systemd. Root FS is not encrypted, but I'm using /etc/crypttab for other file systems Kernel command line: /vmlinuz-linux root=/dev/mapper/larcvg-larc--root ro quiet Output during failed boot: No volume groups found [ ... waits some seconds ... ] ERROR: device '/dev/mapper/larcvg-larc--root' not found. Skipping fsck. ERROR: Unable to find root device '/dev/mapper/larcvg-larc--root'. You are being dropped to a recovery shell ... /dev/mapper is empty, but when I run 'lvm vgchange -a y' then all devices successfully appear. /etc/mkinitcpio.conf: MODULES="ahci ext4 dm-crypt aesni-intel" BINARIES="" FILES="" HOOKS="base udev autodetect pata scsi sata lvm2 filesystems usbinput fsck" There aren't any obvious causes in dmesg output either. There are some differences in EFI stuff, SATA disks are discovered in a slightly different order and there's an additional message "spurious 8259A interrupt: IRQ7." during a successful boot. Here's a diff of dmesg (timestamps removed): --- dmesg_failed 2012-08-01 21:21:00.711241065 +0300 +++ dmesg_success 2012-08-01 21:21:03.137946066 +0300 @@ -38,13 +38,13 @@ efi: mem11: type=1, attr=0xf, range=[0x00000000d7a79000-0x00000000d7a97000) (0MB) efi: mem12: type=7, attr=0xf, range=[0x00000000d7a97000-0x00000000d7aa3000) (0MB) efi: mem13: type=2, attr=0xf, range=[0x00000000d7aa3000-0x00000000d7ab5000) (0MB) - efi: mem14: type=4, attr=0xf, range=[0x00000000d7ab5000-0x00000000d7ab9000) (0MB) - efi: mem15: type=3, attr=0xf, range=[0x00000000d7ab9000-0x00000000d7aca000) (0MB) - efi: mem16: type=4, attr=0xf, range=[0x00000000d7aca000-0x00000000d7acb000) (0MB) - efi: mem17: type=3, attr=0xf, range=[0x00000000d7acb000-0x00000000d7ad7000) (0MB) - efi: mem18: type=4, attr=0xf, range=[0x00000000d7ad7000-0x00000000d7adc000) (0MB) - efi: mem19: type=3, attr=0xf, range=[0x00000000d7adc000-0x00000000d7ade000) (0MB) - efi: mem20: type=4, attr=0xf, range=[0x00000000d7ade000-0x00000000d7ae3000) (0MB) + efi: mem14: type=4, attr=0xf, range=[0x00000000d7ab5000-0x00000000d7ab6000) (0MB) + efi: mem15: type=3, attr=0xf, range=[0x00000000d7ab6000-0x00000000d7ab7000) (0MB) + efi: mem16: type=4, attr=0xf, range=[0x00000000d7ab7000-0x00000000d7ab8000) (0MB) + efi: mem17: type=3, attr=0xf, range=[0x00000000d7ab8000-0x00000000d7acb000) (0MB) + efi: mem18: type=4, attr=0xf, range=[0x00000000d7acb000-0x00000000d7acd000) (0MB) + efi: mem19: type=3, attr=0xf, range=[0x00000000d7acd000-0x00000000d7ad8000) (0MB) + efi: mem20: type=4, attr=0xf, range=[0x00000000d7ad8000-0x00000000d7ae3000) (0MB) efi: mem21: type=3, attr=0xf, range=[0x00000000d7ae3000-0x00000000d7ae4000) (0MB) efi: mem22: type=4, attr=0xf, range=[0x00000000d7ae4000-0x00000000d7ae5000) (0MB) efi: mem23: type=3, attr=0xf, range=[0x00000000d7ae5000-0x00000000d7ae6000) (0MB) @@ -519,8 +519,9 @@ please try 'cgroup_disable=memory' option if you don't want memory cgroups hpet clockevent registered Fast TSC calibration using PIT - Detected 2660.066 MHz processor. - Calibrating delay loop (skipped), value calculated using timer frequency.. 5322.80 BogoMIPS (lpj=8866886) + spurious 8259A interrupt: IRQ7. + Detected 2660.038 MHz processor. + Calibrating delay loop (skipped), value calculated using timer frequency.. 5322.74 BogoMIPS (lpj=8866793) pid_max: default: 32768 minimum: 301 init_memory_mapping: [mem 0xdb400000-0xdbffffff] [mem 0xdb400000-0xdbffffff] page 2M @@ -570,7 +571,7 @@ CPU3: Thermal monitoring handled by SMI Booting Node 0, Processors #1 #2 #3 Brought up 4 CPUs - Total of 4 processors activated (21289.21 BogoMIPS). + Total of 4 processors activated (21288.98 BogoMIPS). devtmpfs: initialized PM: Registering ACPI NVS region [mem 0xdb27f000-0xdb36efff] (983040 bytes) NET: Registered protocol family 16 @@ -916,7 +917,7 @@ software IO TLB [mem 0xd3936000-0xd7935fff] (64MB) mapped at [ffff8800d3936000-ffff8800d7935fff] Simple Boot Flag at 0xf1 set to 0x1 audit: initializing netlink socket (disabled) - type=2000 audit(1343844854.319:1): initialized + type=2000 audit(1343845089.366:1): initialized HugeTLB registered 2 MB page size, pre-allocated 0 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) @@ -950,13 +951,13 @@ cpuidle: using governor menu drop_monitor: Initializing network drop monitor service TCP: cubic registered - input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 NET: Registered protocol family 10 NET: Registered protocol family 17 + input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 Key type dns_resolver registered PM: Hibernation image not present or could not be loaded. registered taskstats version 1 - rtc_cmos 00:06: setting system clock to 2012-08-01 18:14:15 UTC (1343844855) + rtc_cmos 00:06: setting system clock to 2012-08-01 18:18:10 UTC (1343845090) Freeing unused kernel memory: 756k freed Write protecting the kernel read-only data: 8192k Freeing unused kernel memory: 1504k freed @@ -982,9 +983,9 @@ ata5: SATA max UDMA/133 abar m2048@0xf6940000 port 0xf6940300 irq 40 ata6: SATA max UDMA/133 abar m2048@0xf6940000 port 0xf6940380 irq 40 ata2: SATA link down (SStatus 0 SControl 300) - ata6: SATA link down (SStatus 0 SControl 300) - ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5: SATA link down (SStatus 0 SControl 300) + ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) + ata6: SATA link down (SStatus 0 SControl 300) ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) ata1.00: ATA-8: WDC WD3200BEKT-75PVMT0, 01.01A01, max UDMA/133 ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32), AA @@ -1034,5 +1035,181 @@ usb 2-1.7: new full-speed USB device number 3 using ehci_hcd usb 2-1.8: new full-speed USB device number 4 using ehci_hcd usb 2-1.8: config 0 descriptor?? ---- Regards, Marti
Am 01.08.2012 20:33, schrieb Marti Raudsepp:
On Mon, Jul 23, 2012 at 3:57 PM, Tobias Powalowski <tobias.powalowski@googlemail.com> wrote:
Please report any issues that arise.
I have an interesting problem on my laptop: about 1 in 3 times during boot, the initrd fails to find the root file system, which is located on LVM. I'm quite sure that this started after upgrading to linux 3.5.0-1
This might be unavoidable. Try lvmwait=/dev/sdXY on the command line, where sdXY is the partition that holds the LVM PV.
On Wed, Aug 1, 2012 at 10:47 PM, Thomas Bächler <thomas@archlinux.org> wrote:
This might be unavoidable.
Try lvmwait=/dev/sdXY on the command line, where sdXY is the partition that holds the LVM PV.
So you're saying that Linux 3.5 didn't introduce any bugs, but simply boots up so fast that the disk isn't initialized yet by the time the initrd tries to activate LVM? Couldn't this be fixed in initrd to try again every second for 5 seconds or so, if the root device hasn't appeared? (Or maybe monitoring udev events, although that sounds much more complicated) Regards, Marti
Am 01.08.2012 22:13, schrieb Marti Raudsepp:
On Wed, Aug 1, 2012 at 10:47 PM, Thomas Bächler <thomas@archlinux.org> wrote:
This might be unavoidable.
Try lvmwait=/dev/sdXY on the command line, where sdXY is the partition that holds the LVM PV.
So you're saying that Linux 3.5 didn't introduce any bugs, but simply boots up so fast that the disk isn't initialized yet by the time the initrd tries to activate LVM?
Yes, this has happened before.
Couldn't this be fixed in initrd to try again every second for 5 seconds or so, if the root device hasn't appeared? (Or maybe monitoring udev events, although that sounds much more complicated)
We do this already, for every device but for LVM and RAID. For RAID, there is the auto-assembly with the mdadm_udev hook. For LVM2, I wrote something similar once, but it had problems. If you want the initramfs to wait for the devices, use the lvmwait parameter and you should be fine.
participants (12)
-
Christoph Vigano
-
fredbezies
-
Genes MailLists
-
Ike Devolder
-
Jonas Jelten
-
Karol Babioch
-
Leonid Isaev
-
Marius T.
-
Marti Raudsepp
-
Thomas Bächler
-
Tobias Powalowski
-
Tom Gundersen