Bug#1072570: gnome-shell: Gnome 43.9 Wayland: UI freezes in various apps, e.g. ~3mins when starting Totem
Package: gnome-shell Version: 43.9-0+deb12u2 Severity: important X-Debbugs-Cc: da...@balch.co.uk Dear Maintainer, I keep on getting UI freezes in Gnome Wayland, where the UI won't respond for between a few seconds and a few minutes. Possibly related: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5453 System details: - Dell Inc. OptiPlex 7040 - Intel® Core™ i5-6500 (four-core) - Mesa Intel® HD Graphics 530 (SKL GT2) - 16.0 GiB RAM - PM951 NVMe SAMSUNG 256GB SSD - WDC WD20EZRX-19DC0B0 2TB HDD - "High speed with ethernet" HDMI cable (presumably 1.4) - Debian 12 (64-bit) - Gnome 43.9 - Extensions disabled (using the master switch in _Extensions_) - Video problem apparent when testing with 1280x720@60 1920x1080@60 and 3840x2160@30 - although with lower resolutions, the periodic UI updates are more frequent, e.g. every 10s (rather than 30s when using 3840x2160). * What led up to the situation? Just regular desktop use. * What exactly did you do (or not do) that was effective (or ineffective)? I've noticed clear stalls in FreeCAD, but they're more noticeable in _Videos_ (AKA _Totem_), so I've done the most testing with _Videos_: * What was the outcome of this action? Using _Files_ to open a SD H.264 .mkv video with _Videos_: * What was the outcome of this action? - UI stops responding (no screen updates) - _Videos_ Window opens - After a couple of seconds, the video's sound plays - Sometimes, the "_Files_ is not responding" dialog appears - Periodically the UI updates, showing an updated video frame and new mouse position (so mouse input is working) - If I have pressed the Super key and there's a UI update the Activities overview will appear (so keyboard input is working) - After approx 2-3 minutes, the video plays normally, and the UI starts responding. Some videos in other formats (e.g. MPEG4 .avis) trigger the same problem, but only for ~5 seconds. Playing the same files with VLC works immediately, with no freezing. Playing the same files with Totem in Gnome xorg works immediately, with no freezing. I know it's not the most powerful system but, once it's going, it can play the video fullscreen with no freezes or frame drops that I've noticed. * What outcome did you expect instead? UI does not freeze, respondint to input, with Totem playing the video immediately. What I've tried to identify the problem... As the screen is not updating, _System Monitor_ doesn't give me any indication of CPU spikes. Checking the log from running _atop_ (writing to file) shows no obvious resource shortages, with _totem_ using 49% CPU at peak. _gnome-shell_ makes an appearance in the last ~20 seconds with 7% and 10% CPU. Using the CLI: `totem vid.mkv` gives the same results, with the following messages repeated over-and-over in the terminal: (seemingly as long as the video is playing, so I guess it's not related): ``` (totem:20105): Gdk-CRITICAL **: 17:35:04.926: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed (totem:20105): Gdk-CRITICAL **: 17:35:04.926: gdk_window_get_toplevel: assertion 'GDK_IS_WINDOW (window)' failed (totem:20105): Gdk-CRITICAL **: 17:35:04.926: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed ``` Having set up [FPS logging](https://her01n.com/2022/01/14/show-fps-in-gnome/), _journalctl_ shows FPS dropping below 1fps in apparent connection with the error `timeout from dbind`. Relevant part of _journalctl_ log when starting video: Jun 02 17:32:30 Optiplex gnome-shell[17165]: *** HDMI-1 frame timings over 1.0s: 30.13 FPS, average: 2.4ms, peak: 13.4ms Jun 02 17:32:31 Optiplex gnome-shell[17165]: *** HDMI-1 frame timings over 1.0s: 28.79 FPS, average: 2.4ms, peak: 3.7ms Jun 02 17:32:33 Optiplex gnome-shell[17165]: Failed to read extents of text caret: Failed to validate parent window: GLib.Error atspi_error: timeout from dbind Jun 02 17:32:34 Optiplex gnome-shell[17165]: *** HDMI-1 frame timings over 2.4s: 9.84 FPS, average: 1.6ms, peak: 12.5ms Jun 02 17:32:34 Optiplex gnome-shell[17165]: Failed to read extents of focused component: Failed to validate parent window: GLib.Error atspi_error: timeout from dbind Jun 02 17:32:35 Optiplex gnome-shell[17165]: Failed to read extents of text caret: Failed to validate parent window: GLib.Error atspi_error: timeout from dbind Jun 02 17:32:47 Optiplex gnome-shell[17165]: *** HDMI-1 frame timings over 13.1s: 0.31 FPS, average: 7.3ms, peak: 22.7ms Jun 02 17:32:47 Optiplex gnome-shell[17165]: Failed to read extents of text caret: Failed to validate parent window: GLib.Error atspi_error: timeout from dbind Jun 02 17:32:48 Optiplex gnome-shell[17165]: Failed to read extents of text caret: timeout from dbind Jun 02 17:32:49 Optiplex gnome-shell[17165]: Failed to read extents of text caret: timeout from dbind Jun 02 17:32:50 Optiplex gnome-shell[17165]: Failed to read extents of text caret: timeout from dbind Jun 02 17:32:51 Optiplex
Bug#1065112: Acknowledgement (linux-image-6.1.0-18-amd64: System unresponsive after resume from suspend when WoWLAN enabled in iwlwifi)
Some more data... Testing various kernels from https://snapshot.debian.org/binary/?cat=l , I have found that: • linux-image-6.0.0-0.deb11.2-amd64 - has an error, but stays responsive (log except below, full dmesg at http://paste.debian.net/1309322/). • linux-image-6.0.0-1-amd64 - has an error, and is unresponsive except for (some) sysrq keys (stack trace photo at https://imgur.com/a/1R6gYLh ). Although there is some sort of error/crash in both kernels, only linux-image-6.0.0-1-amd64 becomes unusable, so that's probably more urgent. Log excerpt for linux-image-6.0.0-0.deb11.2-amd6 ... [9.755992] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 10.556787] wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by 4c:22:f3:aa:0a:c3 [ 127.171444] PM: suspend entry (deep) [ 127.180424] Filesystems sync: 0.008 seconds [ 127.205820] (NULL device *): firmware: direct-loading firmware regulatory.db [ 127.205857] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [ 127.206064] (NULL device *): firmware: direct-loading firmware iwlwifi-7265D-29.ucode [ 127.206147] (NULL device *): firmware: direct-loading firmware i915/skl_dmc_ver1_27.bin [ 127.206217] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 127.207668] OOM killer disabled. [ 127.207677] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 127.210388] serial 00:01: disabled [ 127.210518] e1000e: EEE TX LPI TIMER: 0011 [ 127.232775] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 127.232926] sd 0:0:0:0: [sda] Stopping disk [ 127.236750] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 127.696949] ACPI: PM: Preparing to enter system sleep state S3 [ 127.698270] ACPI: PM: Saving platform NVS memory [ 127.698427] Disabling non-boot CPUs ... [ 127.700468] smpboot: CPU 1 is now offline [ 127.703320] smpboot: CPU 2 is now offline [ 127.705876] smpboot: CPU 3 is now offline [ 127.708599] ACPI: PM: Low-level resume complete [ 127.708642] ACPI: PM: Restoring platform NVS memory [ 127.709314] Enabling non-boot CPUs ... [ 127.709350] x86: Booting SMP configuration: [ 127.709352] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 127.710109] CPU1 is up [ 127.710136] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 127.710779] CPU2 is up [ 127.710813] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 127.711515] CPU3 is up [ 127.712376] ACPI: PM: Waking up from system sleep state S3 [ 127.720256] pcieport :00:1b.0: Intel SPT PCH root port ACS workaround enabled [ 127.720642] pcieport :00:1d.0: Intel SPT PCH root port ACS workaround enabled [ 127.724156] i915 :00:02.0: [drm] [ENCODER:94:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it [ 127.724168] i915 :00:02.0: [drm] [ENCODER:103:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it [ 127.724172] i915 :00:02.0: [drm] [ENCODER:114:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it [ 127.724175] i915 :00:02.0: [drm] [ENCODER:124:DDI E/PHY E] is disabled/in DSI mode with an ungated DDI clock, gate it [ 127.724389] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [DRQL] at bit offset/length 136/8 exceeds size of target Buffer (128 bits) (20220331/dsopcode-198) [ 127.724397] ACPI Error: Aborting method \_SB.PCI0.LPCB.SIO1.DSRS due to previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529) [ 127.724403] ACPI Error: Aborting method \_SB.PCI0.LPCB.UAR1._SRS due to previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529) [ 127.724409] serial 00:01: activation failed [ 127.724411] serial 00:01: PM: dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -5 [ 127.724417] serial 00:01: PM: failed to resume: error -5 [ 127.733272] sd 0:0:0:0: [sda] Starting disk [ 127.743867] [ cut here ] [ 127.743869] Timeout waiting for hardware access (CSR_GP_CNTRL 0x080403d8) [ 127.743883] WARNING: CPU: 2 PID: 1113 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2128 __iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi] [ 127.743899] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device ctr ccm qrtr snd_hda_codec_hdmi binfmt_misc intel_rapl_msr intel_rapl_common nls_ascii nls_cp437 vfat fat x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_ctl_led kvm iwlmvm irqbypass snd_hda_codec_realtek ghash_clmulni_intel mac80211 snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi libarc4 aesni_intel crypto_simd snd_hda_codec cryptd mei_hdcp mei_wdt snd_hda_core iwlwifi snd_hwdep rapl snd_pcm intel_cstate dell_wmi sparse_keymap ledtrig_audio intel_uncore snd_timer iTCO_wdt dell_smbios dcdbas intel_pmc_bxt cfg80211 wmi_bmof dell_wmi_descriptor pcspkr snd mei_me iTCO_vendor_support watchdog ee1004 rfkill soundcore mei intel_pch_thermal intel_pmc_core acpi_pad evdev sg msr parport_pc ppdev lp parport fuse efi_pstore loop dm_mod configfs efivarfs ip_tables x_tables
Bug#1065112: Acknowledgement (linux-image-6.1.0-18-amd64: System unresponsive after resume from suspend when WoWLAN enabled in iwlwifi)
Clarification: The above step: "3. After suspend, press a key" is to wake the system up. (I had tried magic packet and it didn't work, so pressed a key to wake and got a lit screen but no interactivity.) With WoWLAN disabled, pressing a key would successfully wake. With WoWLAN enabled, WoWLAN didn't work, and pressing a key would wake it enough to light the display - but not respond except to sysrq. On Thu, 29 Feb 2024 at 21:18, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1065112: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065112. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > da...@balch.co.uk > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian Kernel Team > > If you wish to submit further information on this problem, please > send it to 1065...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1065112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065112 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#1065112: linux-image-6.1.0-18-amd64: System unresponsive after resume from suspend when WoWLAN enabled in iwlwifi
Package: src:linux
Version: 6.1.76-1
Severity: normal
X-Debbugs-Cc: da...@balch.co.uk
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I am trying to get WoWLAN working on an old DELL via a PCIe WiFi card (
https://www.amazon.co.uk/dp/B0BTCNG9TD?psc=1=ppx_yo2ov_dt_b_product_details
)
that uses the Intel 7265 chipset (
https://www.intel.com/content/www/us/en/products/sku/83635/intel-dual-band-wirelessac-7265/specifications.html
).
The card's result from lspci:
03:00.0 Network controller [0280]: "Intel Corporation Wireless 7265
[8086:095a] (rev 59)"
* What exactly did you do (or not do) that was effective (or
ineffective)?
1. Enabled WoWLAN with magic-packet with `iw phy0 wowlan enable magic-packet`
2. Suspend PC with `echo "mem" > /sys/power/state`
3. After suspend, press a key.
I also tried this with a pristine build of linux 6.7.6, and encountered the
same problem.
* What was the outcome of this action?
The display lit up, showing the same information as before suspend, but the
mouse and keyboard don't respond.
Magic SysRq does respond.
I found my way to seeing the kernel crash message (via preventing
console_suspend, and tweaking /proc/sys/kernel/{prink,sysrq} values),
as shown in the image at: https://imgur.com/a/E7dD0ND
Initial analysis of that photo from iam_tj[m]1 on irc #debian-kernel
(2024-02-29 19:48):
>From your photo we see
>`drivers/net/wireless/intel/iwlwifi/iwl-trans.c::iwl_trans_txq_enable_cfg()`
>report "bad state" and that is called from
>`drivers/net/wireless/intel/iwlwifi/mvm/d3.c::iwl_mvm_send_wowlan_get_status()`
> that reports "failed to query wakeup status (-5)".
>From reading the code around WoWLAN it seems a special WoWLAN firmware should
>be loaded into the device on suspend and on resume the driver is checking it
>is (still) there.
If not the driver should cause a full device reset.
`asm_exc_invalid_op` is a TRAP leading to
`arch/x86/kernel/traps.c::handle_invalid_op()` which may imply the code in RAM
has been corrupted (in the function `iwl_pcie_tx_start()` presumably).
Doesn't seem too likely though since code (.text sections) should be read-only
unless the RAM itself is faulty - but if that one wouldn't expect the same
error every time.
* What outcome did you expect instead?
The system resumes from suspend and is fully interactive (as it does when
WoWLAN is disabled).
-- Package-specific info:
** Version:
Linux version 6.1.0-18-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64
root=UUID=b15802a9-4b38-4cb9-9109-fdf1cad881b0 ro quiet crashkernel=384M-:128M
** Not tainted
** Kernel log:
[4.039828] mei_me :00:16.0: enabling device ( -> 0002)
[4.064801] input: PC Speaker as /devices/platform/pcspkr/input/input9
[4.066671] ee1004 0-0051: 512 byte EE1004-compliant SPD EEPROM, read-only
[4.066685] ee1004 0-0053: 512 byte EE1004-compliant SPD EEPROM, read-only
[4.110654] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=4,
TCOBASE=0x0400)
[4.112303] dcdbas dcdbas: Dell Systems Management Base Driver (version
5.6.0-3.4)
[4.113931] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[4.128354] cfg80211: Loading compiled-in X.509 certificates for regulatory
database
[4.128506] cfg80211: Loaded X.509 cert 'b...@debian.org:
577e021cb980e0e820821ba7b54b4961b8b4fadf'
[4.128645] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com:
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[4.128783] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[4.128917] cfg80211: Loaded X.509 cert 'wens:
61c038651aabdcf94bd0ac7ff06c7248db18c600'
[4.133009] platform regulatory.0: firmware: direct-loading firmware
regulatory.db
[4.133129] platform regulatory.0: firmware: direct-loading firmware
regulatory.db.p7s
[4.133616] input: Dell WMI hotkeys as
/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input10
[4.154628] Intel(R) Wireless WiFi driver for Linux
[4.166726] pcieport :00:1d.0: Intel SPT PCH root port ACS workaround
enabled
[4.166880] iwlwifi :03:00.0: enabling device (0100 -> 0102)
[4.169833] iwlwifi :03:00.0: firmware: direct-loading firmware
iwlwifi-7265D-29.ucode
[4.169856] iwlwifi :03:00.0: Found debug destination: EXTERNAL_DRAM
[4.169857] iwlwifi :03:00.0: Found debug configuration: 0
[4.170045] iwlwifi :03:00.0: loaded firmware version 29.4063824552.0
7265D-29.ucode op_mode iwlmvm
[4.184779] snd_hda_intel :00:1f.3: enabling device (0100 -> 0102)
[4.187148] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms
ovfl timer
[4.187150] RAPL PMU: hw unit of domain
Bug#673824: gnome-shell: Same/similar problem.
Package: gnome-shell Version: 3.12.2-3 Followup-For: Bug #673824 Dear Maintainer, I am also encountering problems with gnome-shell when using multiple monitors (with a single monitor, the problem does not appear). With two monitors, screen refresh is very slow, and gnome-shell CPU use at least 70%. Running glxgears repors a higher framerate that the visible refresh rate of the window. From lspci: VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii evolution-data-server3.12.2-1 ii gir1.2-accountsservice-1.0 0.6.37-2 ii gir1.2-atspi-2.0 2.12.0-2 ii gir1.2-caribou-1.0 0.4.13-1 ii gir1.2-clutter-1.0 1.18.2-2 ii gir1.2-freedesktop 1.40.0-2 ii gir1.2-gcr-3 3.12.2-1 ii gir1.2-gdesktopenums-3.0 3.12.2-1 ii gir1.2-gdm3 3.12.2-2 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.40.0-2 ii gir1.2-gmenu-3.0 3.8.0-2 ii gir1.2-gnomebluetooth-1.03.8.1-3 ii gir1.2-gnomedesktop-3.0 3.12.2-2 ii gir1.2-gtk-3.0 3.12.2-1+b1 ii gir1.2-ibus-1.0 1.5.7-1 ii gir1.2-mutter-3.03.12.2-2 ii gir1.2-networkmanager-1.00.9.10.0-1 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.3-1 ii gir1.2-polkit-1.00.105-6.1 ii gir1.2-soup-2.4 2.46.0-2 ii gir1.2-telepathyglib-0.120.24.0-1 ii gir1.2-telepathylogger-0.2 0.8.0-3 ii gir1.2-upowerglib-1.00.99.0-3 ii gjs 1.40.1-2 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.12.2-1 ii gnome-shell-common 3.12.2-3 ii gnome-themes-standard3.12.0-1 ii gsettings-desktop-schemas3.12.2-1 ii libatk-bridge2.0-0 2.12.1-1+b1 ii libatk1.0-0 2.12.0-1 ii libc62.19-7 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.18.2-2 ii libcogl-pango20 1.18.2-1 ii libcogl201.18.2-1 ii libcroco30.6.8-2 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.2-1 ii libedataserver-1.2-183.12.2-1 ii libgcr-base-3-1 3.12.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgirepository-1.0-11.40.0-2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.40.1-2 ii libglib2.0-0 2.40.0-3 ii libgstreamer1.0-01.4.0-1 ii libgtk-3-0 3.12.2-1+b1 ii libical1 1.0-1 ii libjson-glib-1.0-0 1.0.2-1 ii libmozjs-24-024.2.0-2 ii libmutter0d 3.12.2-2 ii libnm-glib4 0.9.10.0-1 ii libnm-util2 0.9.10.0-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpolkit-agent-1-0 0.105-6.1 ii libpolkit-gobject-1-00.105-6.1 ii libpulse-mainloop-glib0 5.0-2 ii libpulse05.0-2 ii libsecret-1-00.18-1 ii libstartup-notification0 0.12-3 ii libsystemd-journal0 208-6 ii libtelepathy-glib0 0.24.0-1 ii libx11-6 2:1.6.2-2 ii libxfixes3 1:5.0.1-2 ii libxi6 2:1.7.2-1 ii python
Bug#727708: Thoughts on Init System Debate
On 21 Jan 2014 04:57, Steve Langasek vor...@debian.org wrote: On Mon, Jan 20, 2014 at 07:09:51PM -0800, Nikolaus Rath wrote: I would add the very presence of the mountall tool to this list. Lennart has described the issues with mountall in https://plus.google.com/u/0/+LennartPoetteringTheOneAndOnly/posts/ip8e1DqJdxT , and apparently the upstart developers have been aware them as well since the very beginning (at least since Ubuntu 8.04) I will not respond to this except to say that I do not agree with Lennart's characterization of mountall as evidence that upstart's model is incorrect. Given https://plus.google.com/+KaySievers/posts/C3chC26khpq#z13jjz3zyofuv3122230ufubgwvfv1myv04#1390263990323502Scott James Remnant's agreement with Lennart (in a comment on https://plus.google.com/+KaySievers/posts/C3chC26khpq, around 1UTC on Jan 21st)... Hindsight certainly lends a different perspective, and I'd be the first person to say that Upstart doesn't work as intended. +Lennart Poettering makes a great point about mountall in a recent post, it was written because Upstart couldn't do the complex filesystem cases it was designed to be able to do; and I was very aware even at the time that was a failure that would need to be addressed. ...it seems that further discussion of these design issues might be a good idea. At the least, there should be some progress on the Upstart bug tracker indicating the shape of a solution for the mountall and The and/or bugs (and any other design issues). Cheers, Dave.
