SRSI Support was added to the upstream kernel in November 2013. The
Ubuntu Trusty kernels got this support for 'free'.
Checked the source code for Trusty to verify it was there:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
trusty.git;a=commitdiff;h=8f8b899563f28ef26e381a6eb90d12dead77389f
The OpenIPMI portion of this issue now seems to be fixed in Utopic
Trusty and I will try and verify the fix for Precise:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736
It's better we can have it in 14.04 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+subscriptions
--
Kent Baxley
Field Engineer, Canonical
kent.bax...@canonical.com
@Gabriele and anyone else that sees power consumption problems,
Please open a separate bug on the power consumption. This issue is to
inclue driver support for the touchpad, which Synaptics continues to
work on / refine upstream.
--
You received this bug notification because you are a member
Public bug reported:
It appears we don't set the CONFIG_GPIO_SYSFS on Trusty (or Utopic?) for
x86.
By enabled, I mean:
CONFIG_GPIO_SYSFS=y
This option (along with a few gpio devices) is needed to enable
programming of such things as the I2C Mux through via the CPLDs on some
OEM 'whitebox'
Request to turn on a kernel config option. No logs required.
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1342153
@Sarubh,
Please file a separate bug for your issue as your touchpad does not
appear to be the same as what's being worked on here. Alternatively,
you can add your comments to this bug, which I think covers your
touchpad device:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307015
--
*** This bug is a duplicate of bug 1331513 ***
https://bugs.launchpad.net/bugs/1331513
** This bug has been marked a duplicate of bug 1331513
14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720
--
You received this bug notification because you are a member of Kernel
Packages,
Now that 12.04.4 is out, we can close this as the patches are in the LTS
Enablement kernels.
** Changed in: dell-poweredge
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Working on a reproducer. I've been able to set up the following:
A Xen HVM guest booting off of an iscsi-attached LVM LUN.
Guest is running Wheezy.
Dom0 is 12.04 on a PowerEdge R620, running the 3.11-based LTS kernels.
The eth1 NIC is being used for the iscsi traffic. This is one of the
@wonko,
If there's any more specific information about the Xen VM, please let me
know. What I'm looking for are any special storage or network drivers
that the VM is using outside of what the standard Xen VM would use. If
there's nothing special about the VM in that respect, then I'll continue
Understood. I didn't realize it was *that* specific. How big is the
database you are importing and is there anything special about the VM
itself? I'll try and get this as close as possible.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Bernard,
I may also want to go ahead and get a soup-to-nuts list of how to set up
a machine to reproduce this. I've got an R620 and access to an iscsi
volume in my lab. I'm trying currently to reproduce on a simpler scale,
but, not having much luck at this time (which is no surprise).
--
You
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1331513
Title:
tg3 eth1: transmit timed out, resetting on
Hi David, I still can't reproduce any jumpy mouse behavior on my
touchpad, even with your steps.
--
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/1305522
Title:
Backport Synaptics HID
Hi AceLan,
So far I can't reproduce the jumpy mouse issues.
@David,
If you have any more specifics about what will reproduce it or how long
it takes to see the issue after booting up and loggin in, I'll be glad
to try it out on my sample here. I've tried both single-finger tap as
well as
For those with the XPS 13's that still have a PS/2 interface showing up,
it looks as if that doesn't seem to 'break' anything. The model I have
in the lab has a much older touchpad firmware on it than the ones you
guys have, so, that may be why things are showing up on your systems
like they are.
Also for everyone that still sees a PS/2 device in xinput after applying
AceLan's kernels, can you please paste the output of the following
command in this bug?:
dmesg | grep psmouse
lsmod | grep psmouse
Thanks!
--
You received this bug notification because you are a member of Kernel
Thanks, all.
It turns out on my XPS 13 that I was booted to the wrong kernel, which
is why the PS/2 mouse device wasn't showing up. Once I booted into
Aclean's test kernel the PS/2 device shows up in xinput.
My dmesg output is the same as what Hans is seeing. The psmouse module
is loading up
AceLan and Arash,
I also have an XPS13 Haswell Edition in the Dell lab. This unit does
NOT reproduce what Arash is seeing with your test kernel. In other
words, the PS/2 mouse does not show up in the xinput list. For my
system, xinput reports things as I expect to see them.
The touchscreen
Can't reproduce this on an XPS 15 here in the Dell lab.
This one has:
Intel Graphics
Qualcomm Wifi / bluetooth (I think Dell calls this the DW1420 or something like
that)
Quad-core i7
8GB RAM
Seagate 500GB Hybrid drive
I put it to sleep at 14:30 yesterday by closing the lid. At 15:30 today
I
Tested here with our lab sample. Touchscreen is working again and the
touchpad is working even better than it did with the previous test
kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also tested acelan's kernels with an XPS15 (model 9530) which has the
same touchscreen but a non i2c synaptics touchpad. The touchscreen and
touchpad both work fine and I don't see an regression in behavior. This
machine survived 30 S3's.
The Inspiron 14 (3421) with just a non-i2c synaptics
Tested an Inspiron 3421, which also has a non-i2c synaptics touchpad. I
tested the same components as earlier along with suspend and resume. So
far so good.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ok. I'll not test those if that's the case.
--
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/1284334
Title:
(regression?) openipmi fails to start on kernels 3.13.0-11-generic and
Hi Joseph,
Thanks. I can check the 3.14rc1 kernel and see. I'll also be glad to
try out a test kernel from you with the handler set back to module.
I'll let you know as soon as I find something out with 3.14rc1
--
You received this bug notification because you are a member of Kernel
Trusty 3.13.0-14-generic config shows IPMI_HANDLER option set to Y:
CONFIG_ACPI_IPMI=m
CONFIG_IPMI_HANDLER=y
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
..with the 3.13.0-8 kernel it is set to m, and this was
Any updates on this?
--
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/1284334
Title:
(regression?) openipmi fails to start on kernels 3.13.0-11-generic and
3.13.0-12-generic
Status in
I think I know what might be happening here...
The firmware on these Synaptics touchpads supports i2c mode as well as
psmouse mode. Older kernels prior to 3.11 didn't have very good i2c
support and the firmware on the touchpad would fall back to psmouse
mode. psmouse mode worked nicely on
Here's the apport when booted to 3.13.0-8. I'm wondering if that is
indeed the case. I saw a changelog for the -11 kernel stating IPMI
modules were set to 'y'.
** Attachment added: openipmi-38.apport
Also just tested the 3.13.5 from mainline and noticed that openipmi does
not start there, either. Same symptoms.
--
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/1284334
Title:
This is the kernel that worked for me:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc4-trusty/
I can also go back and test the others until I find one that breaks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
failed to start on reboot. After running 'sudo service openipmi start',
the service would still fail to start because it failed to load the ipmi
modules.
Kernel 3.13.0-8, which was previously on the
I've uploaded the .apport file, since the server can't get out to the
internet very easily. Let me know if you need anything else.
** Attachment added: openipmi.apport
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+attachment/3994996/+files/openipmi.apport
** Changed in:
Public bug reported:
Dell has reported that certain models of their Haswell-based systems
have been having issues with S3, starting with the 3.11 kernels in
13.10.
Here are some data points for now:
1) Doesn't happen on ubuntu or debian with 3.7
2) Doesn't happen on 13.04 with stock 3.8 kernel
Yes. Someone will be able to do this once they get online this morning.
I've let them know the bug number so they can start logging results
here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: dell-poweredge
Importance: High = Medium
--
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/1152580
Title:
[Dell PowerEdge M520] BCM95720 Network disconnects and resets
@Warren,
What they're suggesting by development release is downloading the latest
iso for 14.04 and trying it as well. Those kernels are (I think) still
on version 3.12 instead of the release-candidate 3.13 ones. I believe
the idea is that if the problem is fixed in 3.12-based kernels it'll
Turns out these patches were too invasive to port to 13.04. They do
look to be in 13.10 and these should also be available in the 12.04.4
Saucy HWE kernel once it releases in January.
** Changed in: dell-poweredge
Status: In Progress = Fix Committed
--
You received this bug notification
** Changed in: dell-poweredge
Status: Confirmed = In Progress
--
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/1206602
Title:
Add hotplug support for Micron's PCIe-SSD devices
** Information type changed from Proprietary to Public
** Changed in: dell-poweredge
Status: New = Confirmed
** Changed in: dell-poweredge
Assignee: (unassigned) = Kent Baxley (kentb)
** Changed in: dell-poweredge
Importance: Undecided = Wishlist
** Also affects: linux (Ubuntu
** Changed in: dell-poweredge
Status: New = 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/1152580
Title:
BCM95720 Network disconnects and resets with new Dell R520
This is a request to consider adding a new feature to the mptip32xx
driver. There's no bug or breakage at this time.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
A patch is being worked on to fix this once and for all. We got an FHD
system into the hands of someone to hammer all of this out.
There is some upstream ACPI stuff that needs to settle first, but, this
should be happening very soon if not already. Once that's done the
13.10 development
44 matches
Mail list logo
