Do you see anything relevant for the kernel error? You can make e. g. a
photo of it (if you see something like a stack trace) and attach it
here.
** Project changed: apport => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification bec
:
USERPID ACCESS COMMAND
/dev/snd/controlC1: martin 1248 F pulseaudio
/dev/snd/controlC0: martin 1248 F pulseaudio
Date: Sun Sep 1 10:51:44 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=a00438dd-f132-4cfe
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: martin 1248 F pulseaudio
/dev/snd/controlC0: martin 1248 F pulseaudio
Date: Sun Sep 1 10:51:44 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
It's a custom build notebook I purchased from a small German vendor
based on "PBL00 (HuronRiver_CRB)", vendor Compal, as far as I can see.
There is nothing more noted on the outside of the chassis. Please let me
know if I can get more information about the system. Apart from the
chassis I can't see
Whats the progress on this?
On my Raspberry Pi (wheezy) I have version 1.1.1:
usbip version
usbip (usbip-utils 1.1.1)
On Ubuntu Raring I have version 0.1.7 which seems to be hopelessly outdated:
usbip -v
** (process:19658): WARNING **: running non-root?
usbip 0.1.7 ($Id: vhci_attach.c 42 2007-09
Using Ubuntu 13.04, Kernel 3.8.0.27-generic on Acer Aspire One 756.
sudo setpci -s 00:1c.2 0x50.B=0x40 works and SD Card is recognized.
However, writing files to the SD Card freezes after a few seconds and
data is corrupt.
--
You received this bug notification because you are a member of Kernel
Using Ubuntu 13.04, Kernel 3.8.0.27-generic on Acer Aspire One 756.
sudo setpci -s 00:1c.2 0x50.B=0x41 works and SD Card is recognized.
However, writing files to the SD Card freezes after a few seconds and
data is corrupt.
--
You received this bug notification because you are a member of Kernel
Hi Christopher. I no longer have this wireless card.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
10ec:8176 Wireless not working in 12.04 for rtl8192ce (RTL8188CE)
Statu
The tip about synclient was very helpful to me. My normal typing
position was causing random middle-clicks to occur and I had no idea
what was going on. Disabling RTCornerButton and RBCornerButton fixed
this.
--
You received this bug notification because you are a member of Kernel
Packages, which
Okay, I will try it soon and reply back.
On Sun, Aug 18, 2013 at 11:16 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Raymond Martin, this bug was reported a while ago and there hasn't been
> any activity in it recently. We were wondering if this is
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778411/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
apport information
** Tags added: apport-collected saucy
** Description changed:
Wireless card no longer working under Linux 3.0.x after upgrade from 11.04 to
11.10, system is an HP 2000 laptop with Realtek RTL8188CE card.
Hardware switch(driver?) for wireless no longer operates. Under 11.0
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778408/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/874229
Ti
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778414/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/874229
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778403/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/8
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778412/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778405/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778407/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/874229
Ti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778406/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/874
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778404/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/874229
Titl
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778413/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/8
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778409/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778410/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778416/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/874229
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778417/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/874229/+attachment/3778415/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/874229
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.11rc6
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Yeah, I don't think that applies. There is a bus full of people here
with the same bug on the same hardware. Of course this is still a valid
bug.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Changed in: linux (Ubuntu Precise)
Status: Invalid => Confirmed
--
You re
HP-2000 240-CA (QA076UA) ->
http://h10010.www1.hp.com/wwpc/ca/en/ho/WF06b/321957-321957-3329744-3848802-3848802-5091493-5128938.html?dnr=1
On Mon, Aug 19, 2013 at 8:41 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Raymond Martin, could you please prov
I tried ubuntu-12.04.2-desktop-amd64.iso from usb. After installing the
proprietary driver, everything worked fine: no disconnections.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1191510
It worked in Precise with internal Broadcom card. I didn't check the
Atheros stick. In Raring neither of both works correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1191510
Title:
The workaround from @Batuhan works for me too (Dell Sputnik,
3.8.0-26-generic, BIOS A08)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1169376
Title:
XPS13 backlight stopped working aft
It does not work in Quantal (same symptoms). I attached the syslog.
I did logger to mark the notifications of network-manager in the syslog:
ubuntu@ubuntu:~$ logger "Before connection"
ubuntu@ubuntu:~$ logger "connected"
ubuntu@ubuntu:~$ logger "reconnecting..."
ubuntu@ubuntu:~$ logger "connected"
Public bug reported:
- Boot
- Disable bluetooth
- Can't enable it again
The UI shows it as ON, but still says "bluetooth is disabled".
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: bluez 4.101-0ubuntu8b1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generi
Note that hitting the close button doesn't cause a crash, just hitting
the Quit button. Other than the crash, both do the same thing.
** Summary changed:
- nvidia-settings-325 crash with pressing exit button
+ nvidia-settings-325 crashes on Quit button press
--
You received this bug notificatio
I have the same on my Thinkpad W510 (Nvidia Quadro FX 880M) on Xubuntu
12.10, using the xorg-edgers PPA, which brings in Linux 3.7.0.7-generic.
I installed nvidia-325 via synaptic. I get this in /var/log/syslog after
two crashes:
Sep 3 18:30:57 Escher kernel: [ 990.669702] traps: nvidia-settings
Oops, never mind. I get the same crash whether I hit Quit or simply
close the window. Seems apport stopped bothering to report the crashes
after the first few times. Running nvidia-setttings from the command
line gives this on exit:
Illegal instruction (core dumped)Illegal instruction (core dumped
Looking at this, it looks like an apparmor issue. udev isn't related at
all with building up network connections.
[ 1236.868192] type=1400 audit(1378323693.244:15): apparmor="DENIED"
operation="capable" parent=1387 profile="/sbin/dhclient" pid=1474
comm="dhclient" pid=1474 comm="dhclient" capabil
... additional info to my previous comment:
after enabling "Load Legacy Option Rom" in BIOS, backlight is working ok
(also when I use f4/f5 keys).
Bios version A08, model XPS L322X
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
The same for me, xps13, full hd, booting from UEFI. Working well with
previous kernel version (3.8.0-29-generic). After updating to the latest
(3.8.0-30-generic) the problem is back again.
martin@flegy-nb:~$ uname -a
Linux flegy-nb 3.8.0-30-generic #44-Ubuntu SMP Thu Aug 22 20:52:24 UTC 2013
Hello Jonathan,
can you please follow /usr/share/doc/udev/README.keymap.txt and use the
"keymap -i" tool to find out the scan codes of the broken keys, together
with their intended meaning? Your vendor/model names are already in the
apport information, so I just need the 8 scan codes for the keys
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other services to not
resume
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other services to not
resume
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other services to not
resume
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other services to not
resume
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other services to not
resume
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other services to not
resume
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other services to not
resume
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
This is rather clearly a duplicate of the logind/systemd-shim bug, re-
duplicating.
** This bug has been marked a duplicate of bug 1184262
[logind] stuck in PrepareForSleep, causing network and other ser
I didn't actually see Lennart's comment 20 two years ago, sorry.
Downgrading priority as the actual bug has been fixed two years ago.
What's left is some robustification which I outlined in the last
paragraph of comment 19.
--
You received this bug notification because you are a member of Kernel
I just noticed this still happens in Ubuntu 13.04 and MacBook Pro 2011
(7,1). I'm using grub boot (not efi).
$ uname -a
Linux mck182-MacBookPro 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 19:40:39 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
$ dmidecode -s system-product-name
MacBookPro7,1
--
You re
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/823106
Title:
Kernel panic - not syncing: smp_callin: CPU1 started up but
I'm afraid I have to reassign this back to the kernel. In comment 4 it
is shown that the Fn+Fx keys work, but the topmost keys (labelled "3" in
your image) all generate the same scan code 0x8D, so it's impossible to
assign these to a keycode. These scan codes need to be fixed in the
driver, or it c
christian, on 13.10 (this also works on earlier versions), please
install the "evtest" package and use "sudo evtest". This lets you choose
your input device and basically gives the same information, but is a tad
easier to use.
--
You received this bug notification because you are a member of Kern
Thanks. Your attached udev.txt confirms that the keymap matching worked:
P: /devices/platform/i8042/serio0/input/input4/event4
[...]
E: KEYBOARD_KEY_85=brightnessdown
E: KEYBOARD_KEY_86=brightnessup
[...]
and your evdev output on event10 confirms that the device *claims* to
support KEY_BRIGHTNESS
I can reproduce this. I added a "sleep 5" to a pm-utils sleep.5 script.
When I run systemd-shim in the foreground in my session, I get this
output after resuming:
14:39:18 O: GDBus-debug:Address: In g_dbus_address_get_for_bus_sync() for bus
type 'session'
14:39:18 O: GDBus-debug:Address: env var
Argh, now that I'm looking for what is using the session bus: Look at
the original attempt to flush the bus and spot the error:
https://github.com/desrt/systemd-shim/commit/136ed11430
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
I'll land this upstream and upload an SRU next Monday.
** Changed in: systemd-shim (Ubuntu)
Status: Triaged => In Progress
** Changed in: systemd-shim (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of
Gabriel, can you please create a new systemd-shim log just like in
comment 5?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing resume signal because D-BUS connection
Thanks Gabriel. That confirms that the D-BUS mess is fixed, and it also
times out properly 10 seconds after the suspend call. Both logs now look
spotless. So I'm afraid I need to ask you to get a complete system D-BUS
log of the whole suspend process, to check what happens to the
PrepareForSleep si
This was four years ago... I no longer have this phone, and I did not
use Ubuntu on the desktop for some time now... So I cannot check whether
this bug is still valid.
Ciao
Martin
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
d
** Changed in: systemd-shim (Ubuntu)
Status: In Progress => Incomplete
** Changed in: systemd-shim (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I have ubuntu 13.10 64-bit running on a HP ZBook 15. The notebook uses an
Intel Corporation Centrino Advanced-N 6235 (rev 24) wireless adapter.
The wireless networking principally works. The issue is that it is not possible
to enable or disable it using the hardware butto
Public bug reported:
Please backport commit a4780adeefd042482f624f5e0d577bf9cdcbb760 (which
is included in upstream kernel 3.11) to the ti-omap4 packages for ubuntu
precise.
I tried doing this manually, and when cherrypicking there's a minor
pretty trivial conflict to resolve, and after cherrypic
Can you provide an armhf .deb? I guess it doesn't really matter much
from the kernel point of view, but my dpkg doesn't want to install them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu.
https://bugs.launchpad.
This test kernel doesn't boot at all (I had to modify flash-kernel for
it to be installed at all - flash-kernel points out that my
subarchitecture is omap4 while this kernel is plain omap).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
g. Please test suspend on devices without the alx module
as well (for the record, Martin Pitt did that on his ThinkPad X201)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173952/+subscriptions
--
Mailing list: https://launchpad.net/~
Naming the interfaces is the responsibility of the kernel driver. It
doesn't need to be called "wlanXXX", that's just a convention.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because yo
I can support the statement of comment #23. The bug seems to be fixed in
the latest daily Trusty Tahr build from: http://cdimage.ubuntu.com
/ubuntu-server/daily/current/trusty-server-amd64.iso
The current 13.10 download off of the Ubuntu homepage still hangs.
Thanks for the quick fix though :-)
Christopher, that's probably something that the AppArmor devs
(John/Tylor) should look into. When I discussed this with John and
Tylor, they already seemed to know which area of AppArmor hits this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
amak79, thanks for pointing out! I fixed that upstream in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=c79af123de
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/665918
Title:
M
Thanks; reassigning to the kernel then, as the keyboard driver must
produce scan codes, otherwise we can't reassign their meaning. Of
course, while doing that it could also just produce correct key codes
:-)
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
I own the same machine (Type 3355-64G) and just updated the bios to
lenovos current one:
Package (ID) UEFI BIOS (BIOS ID) ECP (ECP ID) Rev. Issue Date
1.70(hkuj54wd)1.70(HKET70WW) 1.07 (HKEC19WW)012013/03/25
download link:
http://download.lenovo.com/ibmd
One more bit of information:
I opened the hood to confirm to comment #22.
The thing is, the 4GB are crammed on one single memory module ...
the second slot is empty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
I have now tested the latest mainline kernel, namely I used the image
linux-
image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201312061335_amd64.deb
E.g. I can see
vmlinuz -> boot/vmlinuz-3.13.0-031300rc3-generic
in the / directory.
The system behaves in the same way as with the ordinary kernel
The "PrepareForSleep false" signal is missing. Invalidating kernel task
to stop the kernel bug auto-responder from nagging (please ignore the
previous comment).
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ke
Can you please modify ("sudo gedit", for example) /usr/share/dbus-1
/system-services/org.freedesktop.systemd1.service to set the Exec= line
to
Exec=/bin/sh -c 'env G_DBUS_DEBUG=all annotate-output /usr/lib/x86_64
-linux-gnu/systemd-shim >> /tmp/systemd-shim.log 2>&1'
Then please do a suspend/resu
In bug 1184262, Catalin made an interesting observation that this
failure seems to only happen for her when using the lid to suspend, but
not when using the session menu or power button.
It would be interesting if you ever get a suspend failure with this:
sudo gdbus call -y -d org.freedesktop.l
Philipp, Gabriel: I'm sorry, I didn't consider that annotate-output
isn't installed by default. It's in the "devscripts" package. Please
install it with "sudo apt-get install --no-install-recommends
devscripts". (It's useful to add timestamps to the log output).
--
You received this bug notificat
Christopher, thank you very much. I have successfully upgraded bios to
A15 - the string "A15" is displayed in the boot screen, also dmidecode
prints the value:
$ sudo dmidecode -s bios-version
A15
So far everything is working. I will test the setup and post more
information. Many thanks again!
-
Thanks Rafael, Gabriel, Philipp! Your logs agree in the fact that at the
time it tries to call, or called pm-suspend, the shim's D-BUS connection
goes away:
09:20:16 E: (process:3100): GLib-GIO-CRITICAL **:
g_dbus_connection_flush_sync: assertion 'G_IS_DBUS_CONNECTION
(connection)' failed
(and so
Hello Daniel,
Daniel Lombraña González [2013-11-21 7:33 -]:
> Looks like I come from bug #1184262, and I'm experiencing the same
> problem :-) pm-suspend works always, quickly and the network is
> available without problems, however if I suspend the laptop with the lid
> or Unity menu, networ
Please don't apply this udev rule as it is:
* It can be made *much* more efficient and avoid an extra shell with
SUBSYSTEM=="memory", ACTION=="add",
DEVPATH=="/devices/system/memory/memory*[0-9]", ATTR{online}="1"
(same for the other rule)
* In this generic way they don't look plaus
** Also affects: linux (Ubuntu Saucy)
Importance: Undecided
Status: Invalid
** Also affects: systemd (Ubuntu Saucy)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Changed in: systemd (Ubuntu Saucy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235162
Title:
Regression: Persistent net names via /etc/udev
Abhishek Gupta, did you really quote the right mails? Because those
mails are just proving my point, it makes no sense to have an
unconditional userspace rule which is just there to always enable new
memory. To the contrary, as this is always going to involve more memory
allocation (like it might s
Yes, I think Andy's udev rule from comment 14 is an acceptable distro-
level compromise for 13.10, until that gets solved more cleanly. I
didn't see a confirmation from you that this worked, is that the one
which got tested?
> If you absolutely do not want to include the udev rule we can send you
BTW, where does this rule need to live, in the hypervisor or in the
guests? In the latter case I guess we should ship it in udev, in the
former case they hypervisor package could just ship it? That would avoid
the extra rule for other installs.
--
You received this bug notification because you ar
linux-firmware1.71
> SourcePackage: linux
> UpgradeStatus: Upgraded to precise on 2012-03-04 (0 days ago)
> WpaSupplicantLog:
>
> dmi.bios.date: 01/21/2008
> dmi.bios.vendor: LENOVO
> dmi.bios.version: 7LETB0WW (2.10 )
> dmi.board.name: 6465CTO
> dmi.board.vendor: LE
Time is running out for saucy, so I'll upload the rule from comment 14
now, with some correction: I take it you actually mean "memory[0-9]*"
instead of "memory*[0-9]" (same for CPU). @Abhishek, I don't see how
these rules would cause any other kernel module to suddenly not load?
All they do is to c
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for lack of udev rule
St
amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lightdm1474 F pulseaudio
martin 2092 F pulseaudio
Date: Sun Oct 13 16:51:48 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on
untu Saucy)
Importance: Medium
Assignee: Steve Conklin (sconklin)
Status: Invalid
** Changed in: pm-utils (Ubuntu Saucy)
Status: Incomplete => Fix Committed
** Changed in: pm-utils (Ubuntu Saucy)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: lin
*** This bug is a duplicate of bug 430894 ***
https://bugs.launchpad.net/bugs/430894
** This bug has been marked a duplicate of bug 430894
Using Marvell SAS HBA, /dev/disk/by-path is not populated correctly
--
You received this bug notification because you are a member of Kernel
Packages,
Can anyone confirm that you see these bits:
DRIVER=omapfb
VSYNC=
in "udevadm monitor --kernel -e" on that device? It would be really
strange if not, I just want to make double-sure about that before I
start working on a fix tomorrow morning.
--
You received this bug notification because you are
Taking over from Dmitrijs as per Steve's request, Dmitrijs got pulled
into installer bugs.
** Changed in: systemd (Ubuntu)
Assignee: Dmitrijs Ledkovs (xnox) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
> Which appears to be getting a FD to "kernel" event source, via socket
created by
https://android.googlesource.com/platform/hardware/libhardware_legacy/+/android-4.3_r3/uevent/uevent.c
> so if we filter those VSYNC events on the "udev" source, systemd-udev
& upstart & et al user space shouldn't b
> Note, ideally we would already filter them at the "kernel" netlink
source
That's possible because that android driver doesn't use libudev to get
these events, but sets up its own netlink socket. We really don't want
to see these events anywhere else.
--
You received this bug notification becau
This is systemd-udevd with the patch, built on the Ubuntu armhf porter
box. That's what I used for testing on the maguro.
** Attachment added: "patched systemd-udevd (ARM)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1234743/+attachment/3880064/+files/systemd-udevd
--
You received
This patch adds netlink filter rules to ignore change events from omapfb
if they are long enough to be a VSYNC event. It is a rather gross hack,
I don't want to expect the VSYNC= at a specific place in the raw packet
as the order or length of the other properties might change. But I
verified that d
1401 - 1500 of 2223 matches
Mail list logo
