Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42, R52
On Thu, 30 Apr 2009, Bruno Girin wrote: > Zlotan, I just tried Kees's suggestion but it looks like the files in > /proc don't generate any event that can be captured with inotifywait. It > works on standard files but not on the ones we're interested in. I Only a few sysfs attributes have poll/select support, and I don't know if that's enough for inotify or if you also need some sort of special inotify support in sysfs (something I don't know if is even possible but I could check). The attributes with poll/select support are documented in the thinkpad-acpi driver documentation on the kernel sources, at Documentation/laptops/thinkpad-acpi.txt. If inotify is indeed impossible, you will need perl, python or C to deal with poll/select, shell can't do it AFAIK. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42, R52 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355300] Re: Thinkpad Z61m: volume controls control both main and hardware mixer
The IBM-style ThinkPad volume control is a digital mixer to control the volume of the **built-in** speakers and headphones. Newer Lenovo models (past the T60 second generation) don't have it, instead, they have just a hardware MUTE engine. It is impossible to deactivate the hardware mixer unless you resort to changes to the firmware (so, it is NOT going to happen). The IBM-style volume control system is not designed (both from a hardware and a firmware point-of-view) to control anything else than the internal speakers and headphone volume. It does not control the dock's line-out (which doesn't go through the headphone/speakers volume controller (duh!), nor gets the PC speaker signal mixed in). And it doesn't control the main mixer. It doesn't do any of those things in Windows, either. It never did. What it does have in Windows is a proper OSD system, so users would rapidly learn what the volume buttons are, and how to use them. Anyway, as I said, the hardware mixer cannot be disabled. The firmware will always adjust the headphone/speaker volume when the volume buttons are pressed. These buttons are NOT generic volume control hotkeys, they are the more user-friendly version of a "volume knob" for the internal speakers and headphone output. So, to be blunt: you don't have generic volume control keys on your ThinkPads, unless you: 1. Are using a Lenovo hardware-mixer-less ThinkPad that doesn't send events to thinkpad-acpi in the first place (but which also doesn't note that anywhere, so thinkpad-acpi doesn't even know it is running on a thinkpad that lacks the volume notifications). The Lenovo models issue normal keypresses through the KDC for volume up/down (I don't know about MUTE); OR 2. You have modified the ACPI (and probably the EC) firmware to disable the hardware mixer. And all the issues one has with volume control in ThinkPads old and new are directly caused by people who wanted so badly to break the ThinkPad volume control model, that they tried to force semantics that are just not applicable to these keys (they are NOT master volume control keys) and to the driver hotkey system (keypress events are NOT an OSD side-channel). IMO, it is best to look at this in another way: you want to ADD generic volume control keys in your keyboard (because you never had those in the first place!), and you can do just that as long as you stay clear from the few knobs the firmware doesn't let you mess with freely (brightness, volume, thinklight, hibernate). It is not like there is a lack of unassigned _generic_ FN hotkeys in a more modern thinkpad (i.e. any *40 model or newer). I suggest that fn+insert and fn+delete be mapped to KEY_VOLUME_UP and KEY_VOLUME_DOWN, and fn+pgdn be mapped to KEY_MUTE. This is simple (it only takes three lines inside a HAL .fdi file), it works just fine (and it will _remain_ working just fine in the future, which is important), and it doesn't suffer from a number of border conditions and issues like more 'elaborate' attempts such as the one suggested by another post of this thread, do. Of course, this requires unbroken support for KEY_VOLUME_UP, KEY_VOLUME_DOWN and KEY_MUTE in HAL when the events are coming from thinkpad-acpi's input device. I believe the crap (a "passive notification" modifier added to abuse input events for OSD) that could break these has been removed already, but you might want to double-check that. As for OSD, please refer to lauchpad bug #357673. -- Thinkpad Z61m: volume controls control both main and hardware mixer https://bugs.launchpad.net/bugs/355300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357673] Re: No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42
First, please read my post on bug #355300 to know about the hardware volume control and digital volume knob details. Let's start with a key fact: the thinkpad-acpi driver does NOT support any sort of OSD notification events for brightness and volume right now. All that was done for OSD was done by abusing the hotkey key-press events, and it should not be a surprise to anyone involved that it finally decided to break hideously. That's the nature of half-baked hacks. That said, let's see what can be done to fix OSD both in the short term in Ubuntu and in the long term for everyone. Do notice that I *expect* Ubuntu to actively work with me to get the proper long-term fixes deployed this time around. My best guess is that Ubuntu (just like Debian) switched away from procfs-based ACPI events to netlink-based ACPI events. Well, thinkpad- acpi does not, and has never issued keypress events over ACPI netlink. Those events belong to the input layer, so they were not ported to the new, clean netlink ABI when it was introduced in 2.6.23 or thereabouts, and they will _not_ be. That is not only the right thing to do, it also avoids a whole bunch of problems due to duplicated keypress events on the input device and also as an ACPI event. So, all you need to do for a quick fix is to (assuming you don't want to just re-enable ACPI PROCFS events): 1. Hook the OSD snooper to the thinkpad-acpi input device, instead of to the ACPI event stream; 2. Make sure to not regress #355300: 2a. DO NOT attach KEY_VOLUME_UP/DOWN/MUTE to the 0x14, 0x15 and 0x16 thinkpad-acpi keymap positions. Instead, attach some other useless and unhandled keycodes, maybe mark those as passive, and use those as OSD events for volume up/down/mute. You will have to fix HAL .fdi files to make sure of this. 2b. After you reprogram the keymap as above, read the value of hotkey_recommended_mask, set the bits for volume, and write the result to hotkey_mask. Do not just override hotkey_mask with some random crap like 0xff. I provide "hotkey_recommended_mask" in the driver for a good reason. 3. Do the same steps (2a, 2b) for the brightness keys. This will future-proof the hideous hack somewhat, which is a good idea should it outlast its expected lifetime. That should give you working OSD in the short term. DO NOT send the above hackery upstream. Please work with me on the stuff described below, instead. Now, for the long term OSD fixing. 1. Volume notifications The proper place to get OSD information for mixer-related things is ALSA. If OSD is working there, it will work for every mixer, on every hardware, and in a generic way to boot. So, how to do proper OSD for volume on thinkpads? An ALSA mixer for the ThinkPad built-in volume control (which doesn't exist anymore in recent Lenovo firmware) is (finally!) the next thing on my TODO list. The Lenovo models already have an ALSA mixer since they just have the master mixer, so "ALSA mixer OSD" will cover all ThinkPads when I deploy support for the IBM hardware mixer (also present on 1st-gen T60). ALSA mixers are supposed to be capable of doing event generation for OSD, and if they're not doing it as well as they should, I expect Ubutu to move to fix that. I will talk to the Ubuntu kernel team to find the best way to get early code drops from thinkpad-acpi updates to them, so you should get that ALSA mixer for thinkpads quite soon after it is ready. Again, let me reiterate: I expect Ubuntu to do its side and help to get the proper OSD functionality deployed in HAL and other userspace upstream. 2. brightness change notifications All brightness control in the Linux kernel is done through the sysfs backlight class, regardless of whether thinkpad-acpi or ACPI video (with or without OpRegion support) is being used to control brightness. This is valid for all other laptop platform drivers too (or soon will be). The backlight sysfs class gives instant readouts of the current brightness level, which can be used for poll-based OSD _now_. So, please do it. I expect from Ubuntu a poll-based (once a second should be enough) OSD interface for backlight brightness OSD. One can add proper event-driven notification support to it (sysfs can do poll/select), and one can upgrade the poll-based OSD to event-based OSD when implemented by the kernel driver, so in return for Ubuntu deploying backlight-sysfs-class-based OSD, I will write the kernel patches for the sysfs backlight class, and add the event notification it will require to thinkpad-acpi (and if possible, to ACPI video). So, now the ball is in your court. -- No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
[Bug 355300] Re: Thinkpad Z61m: volume controls control both main and hardware mixer
Well, the problem is that you do not have three volume *keys* in your ThinkPad, you have three volume control buttons that are tied to a specific piece of hardware and functionality. What IBM and the early Lenovo ThinkPads give you is the equivalent of a volume knob for the headphone and internal speakers, only nicer. And anything you do to attempt to get it to act in any other way will always have some sort of drawback, because the hardware and the firmware were engineered to not let you get away with it. I have explained how the hardware and the firmware works, and that "disabling the hardware mixer" is not going to happen, because it is impossible to do so. These are all facts. They are not up to discussion, because they cannot be disproved or changed in any meaningful way. And as many people can attest and some have done so even in this bug report, you get absolutely horrid behavior from the headphone output and the internal speakers when you use the volume buttons to _also_ drive the volume of the master AC97/HDA mixer, which causes a bad compound effect on the speakers and headphone volume. IMO, there is no way those drawbacks should be imposed on users that are using the hardware as it was engineered to be used. If you have inserted a dummy plug on the headphone jack to silence the internal speakers, and use only line-out (which requires a dock or port replicator in the first place) to get audio signals, fine. One can easily see why you'd want to drive the master AC97/HDA volume as well using the volume buttons in that case. However, I am sure nobody is arguing for that being such a common setup that it deserves to be the default behavior in a driver or in a distro? Now, if Ubuntu wants to provide easy access to your alternate setup, that'd be fine. Why don't you guys ask for that, instead, and work out a user-friendly way to select alternate platform setups? I certainly am willing to continue providing volume button keypress events in the kernel driver, as long as it is being used sensibly and not causing more problems than it is worth. -- Thinkpad Z61m: volume controls control both main and hardware mixer https://bugs.launchpad.net/bugs/355300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355300] Re: Thinkpad Z61m: volume controls control both main and hardware mixer
(sorry for the double post) -- Thinkpad Z61m: volume controls control both main and hardware mixer https://bugs.launchpad.net/bugs/355300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355300] Re: Thinkpad Z61m: volume controls control both main and hardware mixer
BTW: Windows and Linux supports the ThinkPad flawlessly as long as Ubuntu is messing with those volume keys. In fact, the "volume buttons drive the main mixer" is exactly how Windows DOES NOT behave. That has already been said in this bug report, but apparently some people didn't pay attention. The fact is that the users have wrong expectations of how to use the ThinkPads. The correct way to fix that problem doesn't get anywere close to breaking the volume buttons. You'd be much better off as far as usability goes if you provided a series of small animations or wordless diagrams to the user the first time he logged in. Those diagrams would display how the volume keys work in a old-style ThinkPad. Have you ever used a ThinkPad in Windows with the full suite of "ThinkVantage" software installed? That's exactly what IBM and Lenovo do, at least for the docks and bays. I don't know if they have it for the volume keys, but the idea is sound. -- Thinkpad Z61m: volume controls control both main and hardware mixer https://bugs.launchpad.net/bugs/355300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355300] Re: Thinkpad Z61m: volume controls control both main and hardware mixer
BTW: Windows and Linux supports the ThinkPad flawlessly as long as Ubuntu is NOT messing with those volume keys. ' In fact, the "volume buttons drive the main mixer" is exactly how Windows DOES NOT behave. That has already been said in this bug report, but apparently some people didn't pay attention. The fact is that the users have wrong expectations of how to use the ThinkPads. The correct way to fix that problem doesn't get anywere close to breaking the volume buttons. You'd be much better off as far as usability goes if you provided a series of small animations or wordless diagrams to the user the first time he logged in. Those diagrams would display how the volume keys work in a old-style ThinkPad. Have you ever used a ThinkPad in Windows with the full suite of "ThinkVantage" software installed? That's exactly what IBM and Lenovo do, at least for the docks and bays. I don't know if they have it for the volume keys, but the idea is sound. -- Thinkpad Z61m: volume controls control both main and hardware mixer https://bugs.launchpad.net/bugs/355300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355300] Re: Thinkpad Z61m: volume controls control both main and hardware mixer
This is just a reminder that any OSD-related concerns are to be made on bug #357673, please. There is information on that bug report that is not duplicated here. -- Thinkpad Z61m: volume controls control both main and hardware mixer https://bugs.launchpad.net/bugs/355300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355300] Re: Thinkpad Z61m: volume controls control both main and hardware mixer
Just to get one point clear and across. The problem is not how the ThinkPad works (because you cannot change it, and it works just like that in Windows anyway). It is that the O.S. is failing utterly to convey information to the users in a way that lets them gently (or not) correct their expectations of how the volume keys operate to match the reality of the ThinkPad they're working with. Fix that. Stop trying to make things horribly complicated (and always subtly incorrect) trying to force the hardware to be something it isn't, and to do something it is not prepared to do. There are a number of ways of getting an idea across to the users, and IBM must have found one of them, because the volume keys were not on the top list of complains (it was not even in the list AFAIK) of the *millions* of Windows ThinkPad users from the model 600 up to the T43 and first-gen T60 and Z60. The behavior of the volume changes only changed in Windows for users of the T60 second gen, X61 and Z61. I should know, I got the reports. Before that, it has always been that it would **NOT** touch the main mixer at all. And all the Windows users had was a simple OSD green bar for volume and muting, and a "quick tour" guide (which I frankly don't recall if it mentioned the volume buttons or not). If giving the users a supplementary ALSA mixer that they will see changing when they press the keys will be enough, consider it done. If the problem is OSD for that ALSA mixer, see #357673. If all of that is not enough, it is up to you guys to enhance the desktop environment to do even more hand-holding on this issue and tell the user about the volume keys and how they work outright. -- Thinkpad Z61m: volume controls control both main and hardware mixer https://bugs.launchpad.net/bugs/355300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357673] Re: No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42
Actually, what is needed is proper OSD based on passive notifications _FOR_ OSD (and NOT a hideous hack based on keypress notifications like what exists right now for thinkpad brightness OSD). Don't make a mistake of believing that there exists OSD support in the current scenario. There is none. It is just a jury-rig. OSD support means events engineered to work as OSD notifications, without any side-effects on the rest of the system, nor on the input layer, etc. It means a layered approach, where you have OSD event sources (HAL, applications) and sinks (an applet that display the on- screen notifications). This is how the rest of the notification system (e.g. used to notify of new mail) already works, so it is not anything new. HAL should monitor the kernel interfaces (sysfs backlight, ALSA mixers, etc) and issue OSD events through DBUS. Applets would not get terribly confused doing both active and passive work (which they, invariably, screw up): they would just do OSD (which is always passive in any sane design). Stuff like gnome.*mixer would only generate DBUS OSD notification events, and the on-screen-display functionality would be in a separate component. This gives you a choice of which active producers of OSD events you want, and of which OSD applet you want to display the events. It is also very cross-desktop-environment-friendly. I already offered to help kernel-side to fix and/or extend the kernel interfaces lacking event-based triggers, so that polling is not required, and the offer stands. But there is no need to wait for anything kernel-side, polling-based solutions can be deployed _now_. I strongly suggest we start walking that path, after the short-term fixes are in. -- No notification when sliding audio volume, muting volume, sliding LCD brightness on X31, X32, T60, R50e, T42 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363812] Re: Ericsson F3507g (0bdb:1900) - does not display in NetworkManager, tho USB ACM devices are registered
Ah, I forgot the *obvious*: Make sure EHCI-HCD *and* UHCI-HCD are running properly, or the USB bus won't work, and obviously the device won't be there even if it is enabled. -- Ericsson F3507g (0bdb:1900) - does not display in NetworkManager, tho USB ACM devices are registered https://bugs.launchpad.net/bugs/363812 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363812] Re: Ericsson F3507g (0bdb:1900) - does not display in NetworkManager, tho USB ACM devices are registered
The thinkpad-acpi upstream maintainer here. If the module does not show up in lsusb (run as *root*), it is blocked by the thinkpad firmware (powered down). It will be powered down by the firmware if *any* of the following conditions are met: 1. Set to hidden, radio blocked or something like that in the BIOS setup screens (usually cannot be reenabled by software until reconfigured in BIOS); 2. Disabled in software, and not re-enabled (warning: this state *IS* kept across reboots and power down). In this case, thinkpad-acpi is supposed to be able to re-enable the device, if you use the rfkill sysfs class to do it; 3. Radio-kill physical switch is enabled (i.e. radios are killed). NOTHING can reenable the device until you disable the radio-kill switch. Mind you, I have been told there are kernel bugs in this area for some WLAN devices, but I haven't heard of any on the WWAN devices; 4. The kernel rfkill subsystem orders thinkpad-acpi to kill the radio (check /sys/class/rfkill/*), which it can do at any time, for any reason; 5. Broken backports of the rfkill subsystem, or other kernel bugs. So, please check if any of these conditions are the issue, and do a full checking of the rfkill behaviour to make sure there are no problems with the rfkill subsystem. The thinkpad-acpi driver will log a lot of information if properly compiled with the THINKPAD_ACPI_DEBUG Kconfig option enabled, and loaded with the "debug=0x" parameter. -- Ericsson F3507g (0bdb:1900) - does not display in NetworkManager, tho USB ACM devices are registered https://bugs.launchpad.net/bugs/363812 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52, T500
On Mon, 10 Aug 2009, Aristid Breitkreuz wrote: > I can confirm the muting issue on my T500 running Ubuntu 9.04. Volume > up/down and brightness up/down work as expected, though. The T500 is an entirely different beast, and whatever afflict it has no bearing with this bug which is related to ACPI-based events. The T500 reports MUTE over the regular keyboard (or doesn't report it at all, apparently). Please remove the T500 from this bug. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52, T500 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52
On Sun, 26 Jul 2009, Johannes Hessellund wrote: > The brightness notofication bug is resolved upstream now. Also see bug > #372874. > > http://cgit.freedesktop.org/~dkukawka/hal/commit/?id=d792a792846f9632edfdea3651a74fcd24b2ead7 It was about time. Good news. > Brightness notifications on Thinkpads will to solved. No, they won't. The real fix was submitted by Fedora, as generic brightness change *event* support. I will contribute with sysfs poll() support for actual_brightness on top of that patch soon. It will be in the 2.6.32 kernels, and Ubuntu should backport THOSE as well if they want proper brightness handling, and fix HAL to use select()/poll() or uevents to get the notifications. Patches available in the linux-acpi mailing list. > To enable brightness buttons they should be enabled in the thinkpad_acpi > module: > > options thinkpad_acpi hotkey=enable,0xfd This will, of course, destroy any chances you have of working brightness keys on any Lenovo laptop if the user has to tell ACPI video to switch to "vendor" mode (typically done when brightness change refuses to work with nvidia cards or Xorg OpRegion+KMS). Patches for thinkpad-acpi to auto-enable brightness keys when vendor mode is active on the thinkpads that need it are ready and available in the thinkpad-acpi devel git tree. I will be sending them out soon to the linux-acpi mailinglist. Patches to use the brightness event support are being worked on, should be ready in two weeks. Obviously, any gross hack that enables brightness key events and THEN goes on to *abuse* it as simple notifications will make it completely impossible for thinkpads that actually need they to be processed as keys, to work. This is what is currently employed by Ubuntu+HAL, as far as I know. PS: if you ever need to proplery *reset* thinkpad-acpi's hotkey_mask to the one that the driver wants to be used, do this: cat /sys/bus/platform/devices/thinkpad_acpi/hotkey_recommended_mask > /sys/bus/platform/devices/thinkpad_acpi/hotkey_mask Might be needed when all the proper event support lands. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52
On Sun, 28 Mar 2010, sten wrote: > ahh, I see. So the "ThinkPad Console Audio Control" is a mixer in the > ThinkPad firmware, and that's why it works on older ACPI Thinkpads? Yes. And right now, it only works right on the older thinkpads. It is *not* limited to ACPI thinkpads, it can work on much older boxes like the T20 and even older in NVRAM polling mode. There are a few fixes pending for the NVRAM polling mode, though (minor stuff). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 346303] Re: Kernel oops dialog is inconsistent with kerneloops semantics
On Sun, 15 Nov 2009, Matt Zimmerman wrote: > On Sun, Nov 15, 2009 at 05:13:53PM -0000, Henrique de Moraes Holschuh wrote: > > Oh yes, I am going to change kernel code because your tool scared your > > users senseless for a LOG_WARN message. Forget it. > > I don't know what you're referring to here. Did someone ask you to change > kernel code? Yes. A snide comment promoting a kernel change to get rid of "WARNING" in the printks in the thinkpad-acpi driver, to avoid triggering the tool, instead of fixing the tool (and whatever was causing it to be triggered). Which is, obviously, the exactly wrong way to go about it, and the way it was delivered pissed me off. I don't have a web interface handy right now, or I'd tell you the comment number exactly. > In my view, the way to fix this is to enable apport or kerneloops to > differentiate between serious and non-serious events, and only trigger an > apport problem report for a serious one. > > Is there anything about that which you find problematic? No, I don't think what you propose problematic: that's the correct way to fix the issue. Obviously KERN_WARN and higher-urgency messages need to be shown to the user, it is just a matter of using the right language for each severity level (and also of handling WARN_ON and BUG_ON output blocks). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- Kernel oops dialog is inconsistent with kerneloops semantics https://bugs.launchpad.net/bugs/346303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 557736] Re: Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected!
On Sun, 18 Apr 2010, Alex Chekholko wrote: > How do we get it integrated upstream? The latest kernel source does not > yet have this patch: http://git.kernel.org/?p=linux/kernel/git/next > /linux- > next.git;a=blob_plain;f=drivers/platform/x86/thinkpad_acpi.c;hb=HEAD I will need to fix a few things in the driver, you need more than a simple patch to find the EC for it to work well. Most of the main fixes will be around soon, probably by the end of the week. BTW, the X100e dumps and reports I got show some seriously buggy firmware. Keep it up-to-date. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected! https://bugs.launchpad.net/bugs/557736 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 557736] Re: Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected!
Backports for several *upstream* kernels are available at: http://repo.or.cz/w/linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git (the git:// url is somewhere on that web page). It is easier to work based on those than what is in -next or mainline. The only active release/* branches are: 1. The one for whatever kernel I am using on my T43 (usually the latest or second-to-latest stable upstream kernel). 2. The one for the latest upstream stable kernel, and after -rc5 or thereabouts, the branch for the next upcoming kernel (if there is a reason to create one, i.e., it would not be an empty branch). 3. release/2.6.32 (until it becomes too hard due to code divergence, probably in an year or so). Sometimes I keep a release/ branch alive for a bit, but there are no promises. If anyone is going to start providing Ubuntu kernel module packages based on the above development tree backports, that someone is *urged* to subscribe to the ibm-acpi-devel ML and the x86 platform drivers ML to get in the loop. Those patches are development patches, so they should go through the distro's QA and testing before they're shipped by any distro. If you want stable, you have to get it from the upstream stable kernel. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected! https://bugs.launchpad.net/bugs/557736 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 557736] Re: Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected!
On Mon, 07 Jun 2010, Vladimir Skubriev wrote: > Excusme, i am not understand by reading this bug wrotes: when it will be > fixed ? When you get a new Ubuntu kernel with the thinkpad-acpi driver which is in 2.6.35-rc, or the latest thinkpad-acpi driver backports in ibm-acpi.sf.net. I hope some Ubuntu kernel developer answers you with a date frame or something. I work on the upstream kernel, only. I don't even run Ubuntu... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected! https://bugs.launchpad.net/bugs/557736 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 557736] Re: Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected!
On Mon, 07 Jun 2010, Vladimir Skubriev wrote: > ubuntu running, but sometimes it hangs up for example 1 in two hours. This is not related to thinkpad-acpi, so this bug will not help you. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- Lenovo X100e: thinkpad_acpi: Not yet supported ThinkPad detected! https://bugs.launchpad.net/bugs/557736 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52
On Sat, 27 Mar 2010, Steve Langasek wrote: > I'm happy to report that a test kernel package provided to me by Stefan > Bader now gives the following in /dev/sndstat: > > Card config: > HDA Intel at 0xee24 irq 17 > ThinkPad Console Audio Control at EC reg 0x30, fw 79HT50WW-1.07 > > [...] > > Mixers: > 0: Analog Devices AD1981 > 29: ThinkPad EC 79HT50WW-1.07 > > The mixer is accessible using 'alsamixer -c 29', in read-only mode as > expected. > > Next will be to figure out how to get the desktop to pay attention to > the status of this mixer. Thanks. Please keep me posted. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52
On Thu, 18 Mar 2010, Pete Graner wrote: > On Thu, Mar 18, 2010 at 08:12:54AM +, Mark Shuttleworth wrote: > > On 17/03/10 22:22, Steve Langasek wrote: > > > Pinging the kernel team - is this thinkpad driver backport going to > > > happen for 10.04? > > > > > > ** Changed in: linux (Ubuntu Lucid) > > > Milestone: ubuntu-10.04-beta-1 => ubuntu-10.04-beta-2 > > > > > > > importance high > > > > After getting with apw & slangasek the patch thats needed just came > out in the .10 stable update series. apw is building a test kernel for (I'm the thinkpad-acpi upstream) 2.6.32.10 (and 2.6.33.1) has a lot of thinkpad-acpi fixes, but they are for real bugs in the driver, not extra functionality. I will try to submit the extra event functionality for backlight (not sound, which is what this bug is about) to 2.6.32.y very soon now that the bugfix queue is empty. 2.6.32.y still doesn't have ALSA mixer support, and it will take a while for it to be submitted to 2.6.32.y. The ALSA stuff is not working well in mute-only thinkpads yet, the firmware on the newer mute-only thinkpads changes behaviour depending on OSI(Linux), and not always in the same (or sane ;-) ) way. This results in weird behaviour and the mixer may not report properly the mute state. Using the ALSA mixer to CHANGE mute state is not working well, either. NOTE: I specifically do NOT recommend that the ALSA mixer be enabled in write mode by any distro. The driver defaults to read-only mode which can be used to get events, but the user is to use the volume hotkeys to change volume or mute/unmute. You would do well to heed that warning. If you guys backport this stuff from 2.6.33.1 (or current mainline), I recommend you change the driver to disable the ALSA mixer on mute-only thinkpads for now. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume on ThinkPad X23, X24, X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52
On Mon, 26 Oct 2009, Fabio Marzocca wrote: > thank you for your work. > Just to confirm on my X31 I don't have notifications for audio and backlight > (Karmic 2.6.31-14) Audio (alsa mixer) is not ready yet. Backlight is in 2.6.32, you can ask the Ubuntu kernel team to backport it, but it *does* require userspace applications to be updated to use the backlight class properly for OSD, so just backporting the kernel support is not enough. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 357673] Re: No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52
On Sat, 10 Oct 2009, Nick Bauermeister wrote: > Sorry, I meant "is nominated". There doesn't seem to be a lot of > attention to the issue anymore. Quite the opposite! Backlight has been fixed properly and will be in 2.6.32. The code to support the backlight events is also usable to report volume and mute state changes, so implementing that is next in my list. In fact, I am working on that support *right now*. It will take the form of an alsa mixer. If you want OSD for audio, you hook to the mixer using a proper ALSA-aware program, and it will be notified when the volume changes. Alsa mixer support will be on the kernel upstream for 2.6.33. Ubuntu likes to backport this kind of stuff, so you should see it well before 2.6.33 is out. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- No notification when sliding audio volume, muting volume on ThinkPad X31, X32, X41, X60, T22, T40, T42, T60, R50e, R51, R52 https://bugs.launchpad.net/bugs/357673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 430361] Re: thinkpad_acpi: WARNING: sysfs attribute hotkey_enable is deprecated and will be removed. Hotkey reporting is always enabled
@Steve: The kernel driver will not be changed. -- thinkpad_acpi: WARNING: sysfs attribute hotkey_enable is deprecated and will be removed. Hotkey reporting is always enabled https://bugs.launchpad.net/bugs/430361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 346303] Re: Kernel oops dialog is inconsistent with kerneloops semantics
Oh yes, I am going to change kernel code because your tool scared your users senseless for a LOG_WARN message. Forget it. LOG_WARN is of LOWER severity than KERN_ERR, which is also somewhat common, and in no way means the kernel is unstable. At most it means a driver encountered an error condition that the user should know about. We have KERN_CRIT, KERN_ALERT and KERN_EMERG for the situations where something really bad is about to happen, and WARN_ON() and BUG_ON() for kernel bugs or other really strange situations that should be notified to the kernel people. It gets even more strange to see this kind of answer in a bug (#430361) that was ultimately caused by some utterly broken tool that touches sysfs files at random. Instead of people scrambling out to find out why something they are about to ship is reading files in sysfs at random, I get asked to change a kernel driver log message so that it won't trip a (broken) regexp that thinks anything that start with "WARNING" is the result of WARN_ON?! Compare THIS: [ cut here ] WARNING: at drivers/platform/x86/thinkpad_acpi.c:3759 hotkey_enabledisable_warn+0x50/0x65 [thinkpad_acpi]() Hardware name: 2687DDU thinkpad_acpi: hotkey enable/disable functionality has been removed from the driver. Hotkeys are always enabled Modules linked in: thinkpad_acpi ppp_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc option usbserial usb_storage radeon drm i2c_core tp_smapi thinkpad_ec snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm rfkill snd_seq_dummy ipw2200 libipw video output snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq tg3 libphy snd_timer snd_seq_device snd soundcore snd_page_alloc ehci_hcd uhci_hcd joydev [last unloaded: thinkpad_acpi] Pid: 12451, comm: bash Not tainted 2.6.31.6-t43 #1 Call Trace: [] warn_slowpath_common+0x60/0x90 [] warn_slowpath_fmt+0x24/0x27 [] hotkey_enabledisable_warn+0x50/0x65 [thinkpad_acpi] [] hotkey_write+0x8d/0x164 [thinkpad_acpi] [] dispatch_procfs_write+0x71/0x91 [thinkpad_acpi] [] proc_file_write+0x6b/0x86 [] ? proc_file_write+0x0/0x86 [] proc_reg_write+0x81/0x95 [] ? proc_reg_write+0x0/0x95 [] vfs_write+0x8a/0x113 [] sys_write+0x3b/0x60 [] sysenter_do_call+0x12/0x22 ---[ end trace 7534b65473f2e981 ]--- to THIS: thinkpad_acpi: WARNING: sysfs attribute hotkey_enable is deprecated and will be removed. Hotkeys can be disabled through hotkey_mask That "cut here" and "end trace" lines are not there for show. -- Kernel oops dialog is inconsistent with kerneloops semantics https://bugs.launchpad.net/bugs/346303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882890] Re: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot
So, according to Intel, the probable cause for 0x406e3 and 0x506e3 processors to fail loading the microcode update *early* is an incompatibility when you update from a very old microcode release in BIOS/UEFI (BIOS has a revision older/smaller than 0x80) to the newer microcode updates. This information was provided by Intel in the upstream bug report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31#issuecomment-761228960 However, it looks like it could have been fixed by the latest microcode update batch, from 20210608, which contains microcode revision 0xea for the 0x406e3 and 0x506e3 processors. It would be extremely helpful if anyone that had this issue could test the 20210608 microcode update and report, please. It helps if you include the contents of /proc/cpuinfo *without* the microcode update, and then the contents of /proc/cpuinfo *with* the microcode update installed. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882890 Title: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882890] Re: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot
According to Intel, this bug has been fixed in the microcode updates released in the 20210608 package. HOWEVER one must go from BIOS to the newest microcode update directly, using kernel early updates. This is how it is supposed to happen by default in Debian (and, AFAIK, Ubuntu nowadays) so it should just work. https://github.com/intel/Intel-Linux-Processor-Microcode-Data- Files/issues/31#issuecomment-876558374 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882890 Title: intel-ucode/06-4e-03 from release 20200609 hangs system in early boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900149] Re: Microcode update causes hard lockups in Intel N4200 CPU/SoC
The new microcode update from 20201110 has rev 0x40 for this microcode, can you check if it improves the situation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900149 Title: Microcode update causes hard lockups in Intel N4200 CPU/SoC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1900149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795594] Re: Microcode for 206C2 Westmere EP is missing
I have just uploaded intel-microcode 3.20180807a.2. to Debian, which does distribute 0x206c2. All other microcodes cited on this bug report have been properly distributed by Debian, and presumably by Ubuntu. As far as I am concerned, this bug is either fixed-upstream (in Debian), or more- information-needed because @jan-kellermann has decided to not comment further. As far as I am concerned, unless new information is posted soon, this bug report can be closed as soon as Ubuntu pulls in 3.20180807a.2 from Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795594 Title: Microcode for 206C2 Westmere EP is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1795594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789719] Re: severe performance issue after intel-microcode update
Setting to incomplete, since the fact that spectre, ssb and l1tf mitigations are expensive (and utterly so for some workloads) is well documented and well known, and there is nothing we can suggest unless we know the under-the-hood details of the affected workload. ** Changed in: intel-microcode (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789719 Title: severe performance issue after intel-microcode update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1789719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system breaks overclock
@pragyan: Confirmed by @nanook on #18 that the problem still exists on the Linux microcode package 20180807a. Also, by the bug report date, this issue has existed in the relevant microcode updates for a while: it is not a recent regression. ** Summary changed: - intel-microcode when installed on an i7-6850k based system running Artful breaks overclock + intel-microcode when installed on an i7-6850k based system breaks overclock ** Changed in: intel-microcode (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795594] Re: Microcode for 206C2 Westmere EP is missing
For 0x206c2: Refer to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907402 0x206c2 is missing *from the Debian and Ubuntu packages* on purpose, but we could ship it if Intel explicitly tells us it is not going to permanently disable a box that has a very old BIOS with the blacklisted SINIT ACM for Intel TXT AND which happens to have Intel-TXT-based secure boot enabled in BIOS. For 0x106e5, 0x306e4: They are present in the intel-microcode packages in Debian, so I will leave the answer to the Ubuntu maintainer. Are you sure they are really missing from /lib/firmware/intel-ucode? This will check if the microcodes are in the package (run it with the package installed and no extra manually-added microcodes in /lib/firmware/intel-ucode or /usr/share/misc/intel-microcode*) iucode_tool -q -l -s 0x106e5 -s 0x306e4 /lib/firmware/intel-ucode " reports they exist, then your issue is that they're not being installed to the initramfs. ** Bug watch added: Debian Bug tracker #907402 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907402 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795594 Title: Microcode for 206C2 Westmere EP is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1795594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795594] Re: Microcode for 206C2 Westmere EP is missing
** Changed in: intel-microcode (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795594 Title: Microcode for 206C2 Westmere EP is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1795594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1795594] Re: Microcode for 206C2 Westmere EP is missing
On Tue, 09 Oct 2018, pragyansri.pa...@intel.com wrote: > Confirmed information from microcode team: > > 206F2 – Westmere-EX Rev 0x3B shows as OK for OS load. The prior one marked > as Production was 0x39 and mark as NOT_FOR_OS. > 206C2 – Westmere-EP Rev 0x1F and 0x1E shows as OK for OS load and the prior > production revision 0x1D is marked as NOT_FOR_OS. Thank you. Since you report that the Intel microcode team explicitly told us to ship these two microcode updates to users, I will update the Debian package to do so. Ubuntu will either pick it up from there, or do the same. -- Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795594 Title: Microcode for 206C2 Westmere EP is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1795594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
For the record: Now that Microsoft started distributing the recent batch of Intel microcode updates, there are reports everywhere from Windows 10 users, that the Microcode updates do break i7-6850K over-clocking. As expected, really. The recommended action is to demand a firmware update from the motherboard vendor, for motherboards that were sold with over-clocking as one of their key features. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
On Mon, 24 Sep 2018, Robert Dinse wrote: > Not sure why that would be as expected, Intel specifically sold the > 'K' part to have unlocked multiplier. Any firmware upgrades ought to retain > the features people paid for. Well, it was reported to happen on Linux, and it is the sort of issue that is not related to the operating system. So, *as expected*, it was also going to trigger on Microsoft Windows. All it took was for the microcode update to start being distributed more widely [by Microsoft] to Windows users for it to show up on several news outlets. I am not personally sure Intel is really to blame here, it depends entirely on the motherboard vendor not doing *anything* unsupported [by Intel] to further enhance the overclocking capabilities of the motherboard. So, you'd need to ask your motherboard vendor *and* Intel about it, to know the full story... -- Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
@pragyan: Ubuntu is shipping the same microcode updates as Debian, so I can answer that. The current version of intel-microcode in Debian and Ubuntu ships what is inside Intel's 20180807a "Linux microcode" package as far as the Intel x86-64 processors are concerned. For the i7-6850K (sig: 0x406f1), that would be revision 0xb2e. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
Looks like I should add: As far as I know, Ubuntu Artful is now unsupported, so users of Ubuntu Artful must ensure they switched to Ubuntu Bionic Beaver *or* manually update their intel-microcode package to the one in Bionic Beaver for them to have microcode 0xb2e. I am not sure this will fix this issue, however. A report explicitly stating whether Ubuntu Bionic Beaver is affected by this bug report would be really helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
On Wed, 26 Sep 2018, pragyansri.pa...@intel.com wrote: > Do you have any reported issues with Ubuntu Bionic Beaver that ships with > Intel's latest OS loadable microcode package 20180807a? I am not sure. We need an overclocker with an i7-6850K to test it and be explicit about it, since this bug report has "Artful" in the title. -- Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
@nanook: What we need explicit testing for is this: does the latest version of the intel-microcode package which is present in the latest Ubuntu (Cosmic Cuttlefish *or* up-to-date Bionic Beaver/18.04.01 LTS *or* up- to-date Xenial LTS 16.04.01) disables overclocking on the i7-6850K ? To test this, you need to install the intel-microcode package, and reboot. Then, you check if overclocking is still active *while Ubuntu is running* (overclocking will be working in UEFI/BIOS, regardless). Removing the intel-microcode package and rebooting will undo all changes, so this is a safe test. Please report the contents of /proc/cpuinfo before you installed intel- microcode, and after you installed intel-microcode *and rebooted to activate it*. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
>From reports elsewhere in the Internet, made by Microsoft Windows users with KB4100347 installed. Behavior in Linux might be slightly different. * Several motherboard vendors affected (at least ASUS, EVGA); * Motherboards based on X99 with overclocking features available through vendor UEFI/BIOS; * RAM and uncore overclocking not affected by this issue (overclocked values are preserved); * CPU voltage not affected (changed voltage set points are preserved). Processors reported as affected: Intel 6800k, 5930k, 6900k, 6950x, Xeon (no data about xeon models, assume socket-compatible with X99 chipset). Reports imply the microcode update itself is the problem, not the updated microcode: Motherboards whose UEFI/BIOS already has the latest microcode revision are *not* affected by this issue, and overclock as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
FWIW, since I am a completely neutral party (Debian maintainer), here are some points that may help the Ubuntu teams make a decision: 1. Hypervisors must not (and don't) allow a guest to supply microcode updates, they're blocked at the WRMSR handler. This is required behavior, because it is trivial for a guest to attack the whole host system using microcode updates, resulting in denial-of-service (core hangs) and specially crafted microcode containers (whole box hangs, maybe crashes/reboots, microcode downgrade as a step in a complex attack). Container-based systems cannot filter "guests" (containers) at the WRMSR opcode level like hypervisors can, and therefore must somehow block all entry points to the kernel that could trigger a microcode update from untrusted data. Beware the MSR.ko module. 2. In Debian, we are not aware of any issues with the Trusty's method of microcode updates (late updates) other than the ones related to Intel TSX. However, late microcode updates have increased risk of regressions since they happen after the kernel and modules have initialized MSRs, etc. We have seen such issues related to *BIOS*-initialized MSRs on Xeon E5v3 (which required further microcode updates to fix), but we have not observed anything related to kernel-initialized MSRs. So, this increased risk is a theoretical issue at the moment, AFAIK. 3. Almost nobody tests late updates anymore. All large distros switched to early updates a couple years ago, AFAIK. 4. What Debian did for Debian wheezy (which uses the same outdated method as Ubuntu Trusty to update microcode) was to have two sets of microcode-updating packages and kernel packages (in this case, using wheezy-backports), and drop support for Haswell and later processors using the old method. However, this whole thing did not work very well and now the Wheezy-LTS team will have to very much make the same kind of decision you must make for Ubuntu Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1742903] Re: Microcode updates require a reboot to apply, but package postinst doesn't touch /run/reboot-required
On Thu, 22 Mar 2018, Dimitri John Ledkov wrote: > but it may need to be more smart; e.g. check the new microcode revisions > vs currently loaded; to see if there was an update to microcode for this > system, actually That would be why I did not do it in the Debian package (yet). It is hard to make it fool-proof, and it will be really annoying [to the user] if the package triggers unnecessary reboots (which will be the *rule* on older processors that rarely get updates). If you have good ideas on how to do it, I am listening... -- Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742903 Title: Microcode updates require a reboot to apply, but package postinst doesn't touch /run/reboot-required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1742903] Re: Microcode updates require a reboot to apply, but package postinst doesn't touch /run/reboot-required
On Mon, 26 Mar 2018, Dimitri John Ledkov wrote: > Something like: > > [[ `iucode_tool -s $(sudo iucode_tool --scan-system=2 2>&1 | sed > 's/.*\(0x.*\)$/\1/') -l /lib/firmware/intel-ucode/ | sed -n 's/.* rev > \(0x\),.*/\1/p'` -eq `sudo cat > /sys/devices/system/cpu/cpu0/microcode/version` ]] || echo 'Trigger > reboot' > > should be good enough with bashism... as the kernel file is 0x1f, > yet the tool reports 0x001f. Bashisms aren't a problem, as long as the script declares to be a bash script. Those numbers have to be properly parsed, so using bash is a good solution. They are guaranteed to be 32-bit, too, which doesn't get in the way (bash math is 32-bit). The use of --scan-system=2 is a problem (slow when there are many CPUs, requires a kernel module to be loaded), and I don't understand why the whole dance to feed its output to iucode-tool -s. Looks like just "iucode_tool -S" would do what is required *and* handle systems in mixed stepping configurations better... > There will be false negatives, and false positives, but overall should > be better than the current behavior. There are a lot of corner cases. Also, I am worried that it would have *both* false positives and false negatives. False positives are annoying and cause extra downtime (needlessly request a reboot), but false negatives are *bad* once people start trusting the package to request a reboot when one would be required. For example, one has to consider whether it should be checking the initrds as well or not. Note that while fortunately, the iucode_tool -tr loader option can read the initrd directly, the intel-microcode and iucode-tool packages have no idea where the initrd is, since this knowledge belongs to other layers (initramfs-tools/dracut, bootloader). Anyway, the script must learn to deal with the cases where the microcode update disappeared as well, or it will break badly. > Obviously, no need for sudo, if inside the postinst. Indeed... -- Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742903 Title: Microcode updates require a reboot to apply, but package postinst doesn't touch /run/reboot-required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769043] Re: intel-microcode: update to 20180425 drop
Already in Debian unstable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769043 Title: intel-microcode: update to 20180425 drop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1769043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371695] Re: .deb packages do not support capabilties(7)
This is likely better done in Debian. That said, dpkg-statoverride seems like a possible layer to extend. It is responsible for updating the owner and permission of files installed by packages, after all. Extending it to deal with capabilities, or for that matter POSIX ACLs and Linux extended attributes would make sense. One could then extend debhelper to make its usage more packager- friendly, if a dh_statoverride module doesn't exit already. Until we get that, most packages will do it like iputils-ping does (refer to its postinst script). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371695 Title: .deb packages do not support capabilties(7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1371695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911959] Re: Fresh Ubuntu 20.04 won't boot after intel-microcode update on ThinkPad T460s
For the record: systems with firmware outdated enough to actually hit this microcode update issue *most likely* have several other critical security issues in their Intel platform, not just in the processor. The outdated firmware not only blocks you from updating the processor microcode (thus several processor issues remain), but also very likely has vulnerabilities in other platform components such as the Intel Management Engine. It is your decision to keep your system running like that, but please ensure you actually understand the risks you are taking: review the missing firmware update changelogs/advisories/release notes in your system vendor's website to understand which fixes you are missing, and also check the running processor microcode version to understand which processor microcode fixes you are missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911959 Title: Fresh Ubuntu 20.04 won't boot after intel-microcode update on ThinkPad T460s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908840] Re: Fail to boot due to intel-microcode update
For model 78 stepping 3 processors, look here: https://github.com/intel/Intel-Linux-Processor-Microcode-Data- Files/issues/31 To put it bluntly: update your system firmware. If no such update is available, pressure the system vendor into releasing one. For now, that's the only available fix. The alternative is to not attempt to update the processor microcode at all -- and remain vulnerable to the security and reliability issues the microcode update would have fixed. ** Bug watch added: github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues #31 https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908840 Title: Fail to boot due to intel-microcode update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1908840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1913866] Re: intel-microcode 20201118 bump request
Unless you want regressions on Skylake D0 and R0 for users that are running with severely outdated firmware, please refer to the 3.20201118.1~deb10u1 of the microcode update. Keep the microcode for signatures 0x406e3 and 0x506e3 at revision. 0xd6. Otherwise, it can hang systems where the firmware has versions older (lower) than 0x80 of the microcode. The proper fix for this is to detect and refuse the update in the kernel, but there is no such patch available yet. Assuming it is not fixable in a future microcode update. On Sat, Jan 30, 2021, at 12:11, Hans Joachim Desserud wrote: > ** Tags added: upgrade-software-version > > -- > You received this bug notification because you are subscribed to intel- > microcode in Ubuntu. > Matching subscriptions: Ubuntu intel-microcode, > ubuntu-intel-microcode-bugs-all, x86-microcode > https://bugs.launchpad.net/bugs/1913866 > > Title: > intel-microcode 20201118 bump request > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1913866/+subscriptions > -- Henrique de Moraes Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913866 Title: intel-microcode 20201118 bump request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1913866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913866] Re: intel-microcode 20201118 bump request
You are advised to keep the microcode for skylake D0 and R0 locked at revision 0xd6 using a microcode revision override when backporting 3.2028.1. That is signatures 0x406e3 and 0x506e3. Override to revision 0xd6. Otherwise, systems with old microcode (lower than 0x80) can hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913866 Title: intel-microcode 20201118 bump request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1913866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885248] Re: Update intel-microcode to latest upstream release 20200616 to fix possible regression in 06-5e-03/0x000506e3
Debian will also issue such an update, but we have both "works" and "fails" reports of 0x506e3. We're waiting for some more data re. 0x806eX and 0x906eX, but the situation there is far less clear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885248 Title: Update intel-microcode to latest upstream release 20200616 to fix possible regression in 06-5e-03/0x000506e3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1885248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1883002] [NEW] intel-ucode 20200609: hangs on Whiskey Lake
On Wed, 10 Jun 2020, Andrea C wrote: > CPU family: 6 > Model: 142 > Model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz > Stepping:12 > > microcode: sig=0x806ec, pf=0x80, revision=0xca > > The first sign of a problem was a hard lockup while processing the new > microcode package as part of a larger update; after fixing the resulting At that moment in time, the microcode *is not changed*. Only a *reboot* (or shutdown + powerup) would load the new microcode update. That means the update run hang with whatever older microcode and kernel you already had at the time -- so, it was not caused by the intel-microcode update, *unless* you already had intel-microcode installed and had already rebooted for some reason. > Downgrading intel-microcode to 3.20191115.1ubuntu3 and regenerating the > initramfs fixes the problem. If it is not asking too much, with the computer fully stable and intel-microcode 3.20191115.1ubuntu3 installed (*and* rebooted so that it got applied to the processor), could you please do another install cycle, *just* with the intel-microcode security update that supposedly caused issues? It must complete the update safely, it will not attempt to update the processor. Only when you reboot, will it attempt to install the updated microcode into the processor. Please ensure you have enough free space in /boot: if it fills up, *bad things can (and likely will) happen* the next time you reboot. If the reboot to activate the microcode update does hang, does it also hang when powering up the computer with the new microcode package installed (instead of rebooting)? -- Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883002 Title: intel-ucode 20200609: hangs on Whiskey Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1883002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883002] Re: intel-ucode 20200609: hangs on Whiskey Lake
I see. I will keep that in mind for the future, I thought you guys were doing late-loading triggering *only* inside the initramfs, and not during the update... Well, blacklisting it from late-loading is a no-brainer. I will do that too for Debian, although Debian never late-loads automatically. May I suggest preparing a test package with the late-loading blacklisted for the reporter to try? That would have a non-zero chance of working, given the report that it crashes immediately upon late-load (which gives it a zero chance of working with late-loading enabled). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883002 Title: intel-ucode 20200609: hangs on Whiskey Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1883002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883002] Re: intel-ucode 20200609: hangs on Whiskey Lake
Well, now we need more testing to know if it works or not, since it is kinda expected that some microcode updates would object *heavily* to late-load but work just fine from the early-initramfs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883002 Title: intel-ucode 20200609: hangs on Whiskey Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1883002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
This has been reported to be fixed on very similar processors (with the same microcode signature as yours) in the 20200609 microcode updates, could you test them? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1435695] Re: intel-microcode could use better docs about upstream versions per CPU
~ Two years later... :-) Intel does not keep their microcode guidance docs up-to-date, a new one is issued when they deem it necessary, and they're related to a specific issue being addressed. The processor specification updates are still as opaque as always, and are slowly getting even harder to locate. They're also not necessarily synchronized with the availability of public microcode updates addressing public errata. We include the Intel release notes in the package, as well as our own changelog of the contents. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1435695 Title: intel-microcode could use better docs about upstream versions per CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1435695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
Arnaud, there were some revisions of that security update. Could you retry with the newest? If it still hangs, please check if one of the open bug reports matches your processor model and report there. Otherwise, please open a new report and add your processor model to the bug title, and in the bug report contents, please be sure to incude the output of "/usr/sbin/iucode_tool -Sv" as well as the contents of /proc/cpuinfo. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
That's enough, it confirms that the bug is *fixed*. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
Fixed by upstream 20200609 release. ** Changed in: intel-microcode (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862751] Re: sig=0x806ec/20200609, Hard lockups using microcode releases 20191115 on Intel Whiskey Lake
Debian bug report: https://bugs.debian.org/962757 Facts from debian bug report: Hang only on rev 0xd6 (20200609), works with previous revisions (including rev. 0xca). Since the bug doesn't always trigger, maybe rev 0xd6 made it easier to trigger. ** Bug watch added: Debian Bug tracker #962757 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962757 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862751 Title: sig=0x806ec/20200609, Hard lockups using microcode releases 20191115 on Intel Whiskey Lake To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1834487] Re: Frequent crash at startup after upgrading intel-microcode package
Hello, Please Update the firmware (BIOS/UEFI) on your Asus computer. Asus did something on their firmware which requires the microcode update to be done by the BIOS/UEFI. Asus knows about it, and so does Intel. Supposedly, they're addressing it. Maybe a new microcode update (or for that matter, a new version of Asus firmware) will be more compatible. Until then, you will depend on Asus issuing bios/uefi updates (and you have to apply them to get the fixes). -- Henrique de Moraes Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834487 Title: Frequent crash at startup after upgrading intel-microcode package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1834487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1830123] Re: intel-microcode 20190514 does not provide Sandy Bridge (sigs 0x000206d7 and 0x000206d6)
Hello, Release 20190618 is out, and has these updates. I uploaded it to Debian unstable a few hours agoand we will issue it as a security update as well soon. I imagine Ubuntu will do the same. -- Henrique de Moraes Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830123 Title: intel-microcode 20190514 does not provide Sandy Bridge (sigs 0x000206d7 and 0x000206d6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1830123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781806] Re: With intel-microcode 3.20180425.1, Xorg crashes with SIGABRT in __memcpy_avx_unaligned()
Can you give us the with-old-microcode and with-new-microcode contents of /proc/cpuinfo, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781806 Title: With intel-microcode 3.20180425.1, Xorg crashes with SIGABRT in __memcpy_avx_unaligned() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1781806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789719] Re: severe performance issue after intel-microcode update
I am afraid you need to disclose a _lot_ more information about your workload for us to even have an idea how you'd hit such an extreme slowdown effect... Also, what mitigation modes have you enabled in the kernel, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789719 Title: severe performance issue after intel-microcode update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1789719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743786] Re: intel-microcode-3.20180108.0~ubuntu17.10.1 fails to address spectre variant 2 on Intel i7-6850k platform
I believe this is fixed in the latest version of intel-microcode available on every still-supported branch of Ubuntu... Can you confirm and close the report, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743786 Title: intel-microcode-3.20180108.0~ubuntu17.10.1 fails to address spectre variant 2 on Intel i7-6850k platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1743786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789719] Re: severe performance issue after intel-microcode update
Basically, *you* need to know if: 1. your workload does a LOT of syscalls (kernel entries from userspace) OR 2. your workload does a LOT of VMEXITs (runs on a VM) OR 3. uses Intel SGX (you're on your own in that case, go talk to Intel). Which are directly impacted by the microcode and/or kernel changes. You can also selectively disable KPTI/PTI, L1D flushes (L1TF mitigation), and SSBD mitigation to track down which is not compatible with your workload. That *might* give enough hints on how to change your workload to not suffer as much. https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html and also https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html ( read the documentation for the parameters pti=, spectre_v2=, spec_store_bypass_disable= ) You can disable kernel microcode updating (which will revert to the microcode in your BIOS/UEFI) using the dis_ucode_ldr parameter on the *bootloader* (grub, etc). Instructions are in intel-microcode's README file in /usr/share/doc/intel-microcode You can just install an older version of the intel-microcode package and reboot, if you want to switch to an earlier microcode update **provided that your system firmware (BIOS/UEFI) does not have a newer microcode**. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789719 Title: severe performance issue after intel-microcode update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1789719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789719] Re: severe performance issue after intel-microcode update
For guidance on how to set kernel parameters: https://wiki.ubuntu.com/Kernel/KernelBootParameters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789719 Title: severe performance issue after intel-microcode update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1789719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787126] Re: Update microcode to 20180807 version
20180807 has license problems, and cannot be distributed at the moment. Debian is waiting for Intel to address the matter. I assume Canonical will do the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787126 Title: Update microcode to 20180807 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1787126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686635] Re: amd64-microcode family 0xf not supported
Hardware limitation. Family 0xf cannot, and will never be supported for microcode updates. The one complaining is the kernel, not amd64-microcode itself. ** Changed in: amd64-microcode (Ubuntu) Status: New => Confirmed ** Changed in: amd64-microcode (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686635 Title: amd64-microcode family 0xf not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1686635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686635] Re: amd64-microcode family 0xf not supported
Marked as invalid because there isn't a "working as designed" state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686635 Title: amd64-microcode family 0xf not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1686635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms
Actually, it is not hard to bypass a boot-killer microcode update issue. Just add the "dis_ucode_ldr" parameter to the kernel command line. To make it trivial, add that to a "safe mode" grub menu entry... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1700373][Bug 1713532] regression on intel-microcode 20170707
On Tue, 29 Aug 2017, Robie Basak wrote: > Regression report in bug 1713532. Please could someone familiar with > these microcode updates take a look? First, we should check for the possibility of a kernel or userspace issue that is getting in the way of the bluetooth firmware loading when a microcode update is available to be applied... Hopefully, this should be easy enough to do: intel-microcode package 3.20151106.1 is reported to work, so it is just a matter of testing successive intel-microcode packages, and looking at the full logs of the attempts. Please report the contents of /proc/cpuinfo with the latest intel-microcode package that works, and /proc/cpuinfo with the package that doesn't (3.20170707.1~ubuntu16.04.0). Also, please report the output of "dmesg" or from "journalctl -k -b" (i.e. the kernel logs) in the failure case, so that we can search for some sort of kernel message by the bluetooth stack, etc. You could test when the breakage happened using the Debian packages, They should be 100% compatible with the Ubuntu OS, as far as I know. Packages to test (in order, you can stop when the breakage disappears): http://snapshot.debian.org/package/intel-microcode/3.20170707.1/ http://snapshot.debian.org/package/intel-microcode/3.20170511.1/ http://snapshot.debian.org/package/intel-microcode/3.20161104.1/ http://snapshot.debian.org/package/intel-microcode/3.20160607.2/ Thanks. -- Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
Robert, you have a -K part, which officially "doesn't forbid" overclocking as far as I know, and this is the only reason I have not immediately closed this bug as invalid. It looks like now you get to find out if that means Intel *supports* overclocking or not on -K processors, instead of just passively not blocking it outright: start with ASUS support, it is possible that a properly updated BIOS/UEFI would still allow overclocking on the new microcode. For the record, updating the MSRs for overclocking *after* the microcode is loaded on the processor, as opposed to updating the microcode *after* the overclocking was done by the UEFI/BIOS *can* make all the difference. That means your BIOS/UEFI needs to have the latest microcode update (and you won't need the intel-microcode package). If ASUS can't help you, good luck contacting Intel about this... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748543] Re: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock
(for the record: this bug should be set to "won't fix", as in "**can't** fix", but I don't have the required permission to set the "won't fix" state on the bug report). It might be fixed by Intel in a future microcode update, but unless someone tests this and tell us about it, we won't even know about it being fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748543 Title: intel-microcode when installed on an i7-6850k based system running Artful breaks overclock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1748543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742933] Re: Regression in 2018-01-08 updates
@sdeziel: Please confirm that the i7-7500U has issues resuming from S3 *only* when intel-microcode 20180108 is installed. Also, just to be sure, please attach the contents of /proc/cpuinfo both with the microcode that breaks sleep, and with whatever earlier microcode that works fine. If at all possible, please also test with intel-microcode 20171117 packages. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742933 Title: Regression in 2018-01-08 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212497] Re: [Feature] update microcode to 20130807 version
Guys, could you please notify me (Debian upstream for intel-microcode) of such issues in the future? I will now have to re-upload to Debian with a high priority and changelog, and coordinate uploads to Debian stable... and it was pure luck that I noticed this bug. If it is a matter of embargoed security issues and you cannot notify me, please at least notify the Debian security team, or at the very least drop me a note once the embargo is lifted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212497 Title: [Feature] update microcode to 20130807 version To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1212497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1194370] Re: intel_microcode: prepend_earlyinitramfs: not found
On Sat, 17 Aug 2013, dino99 wrote: > Hopes that report get more attention : > https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1079605 It is a trivial backport of the changes between Debian initramfs-tools v0.112 and v0.113. But someone from Canonical will have to do it. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194370 Title: intel_microcode: prepend_earlyinitramfs: not found To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1194370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608933] Re: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
intel-microcode requires that a new initramfs is built upon install. Like anything else that would need to add new drivers to the initramfs, etc. This requires special support on live media (i.e. the live media MUST have a rewriteable /boot partition which its bootloader will use, and must not have overlays there). This is just a guess, but I'd say there is a good chance it is the issue you have... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608933 Title: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1608933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444682] Re: Software properties gtk implies my cpu is unknown and not working.
FWIW, here are some points to consider when implementing this: 1. A multi-processor system may contain processors that differ in stepping, or for other reasons (e.g. ARM big.LITTLE). This *is* quite common on x86 servers and workstations. So, you might have more than one processor model to list. 2. The "vendor_id" and "model name" fields are not enough to single out the exact processor model, or for that matter, the microcode it needs for Intel processors. It is common for Intel to NOT change the processor model names when there is a bump in stepping, for example. And there are the (unsupported and unsupportable) Engineering Sample processors that people keep buying from the black market, and later sell to unsuspecting third-parties. I don't know if AMD does better. 3. I suggest augmenting the vendor_id and model name fields with: 3a. Family, model, stepping information (cpuinfo fields "cpu family", "model", "stepping"). They are in decimal in /proc/cpuinfo, but nobody uses them like that, so they should be reported in hexadecimal. The kernel actually has a suggested way to display this, which it uses for /lib/firmware/intel-ucode/* files: "%02x-%02x-%02x" (family, model, stepping). 3b. Microcode platform id (cpuinfo field "platform_id", currently being added upstream to the next Linus kernel -- platform_id is a number in decimal). It is enough to add this field only when present: on AMD it will be absent, on Intel it will be present in the future. I suggest these fields to be reported as a single line to identify the "hardware": GenuineIntel, Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz; FMS: 06-2a-07 or, on a kernel that reports platform_id in /proc/cpuinfo: GenuineIntel, Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz; FMS: 06-2a-07 (id: 1) 4. Current microcode version is *relevant* (when it is too old, even the installer will malfunction, as seen with Intel Broadwell and Skylake), so it might also be useful to have it upfront in the screen. This is present in cpuinfo as well (field "microcode"), and should be reported in hexadecimal. NOTE: I suggest compressing repeated sequences of spaces in the "model name" field. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444682 Title: Software properties gtk implies my cpu is unknown and not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1444682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444682] Re: Software properties gtk implies my cpu is unknown and not working.
(BTW: if reporting microcode revision in hexadecimal, it should be prefixed with 0x for clarity). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444682 Title: Software properties gtk implies my cpu is unknown and not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1444682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662718] Re: Processor microcode firmware for AMD CPUs from amd64-microcode.
>From your kernel log, we have this: microcode: AMD CPU family 0xf not supported This means your processor simply does not support microcode updates through the operating system. This is not a bug in the amd64-microcode package: your system is working as designed by AMD. I will close this bug report, as there is nothing we can do in the amd64-microcode package about the message/description you see in the "additional drivers" tab, or about the lack of microcode update support from AMD for your processor. Thank you. ** Changed in: amd64-microcode (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662718 Title: Processor microcode firmware for AMD CPUs from amd64-microcode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1662718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450188] Re: Intermittent boot issues if the proprietary amd64-microcode package is installed on Ubuntu 15.04
There were several bugs in the AMD microcode loader, which were fixed (AFAIK, anyway) on later kernel stable updates from kernel.org. They could easily explain the boot failure with the low-latency kernel. I am not sure if these fixes were incorporated on Ubuntu's 15.10 kernel updates or not. I am also not sure if the low-latency kernel changes to fundamental kernel structures is compatible with the early AMD microcode loader or not. Is anyone still affected by this bug on *up-to-date* Ubuntu 15.10 with the normal kernel? With an up-to-date low-latency kernel? ** Changed in: amd64-microcode (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450188 Title: Intermittent boot issues if the proprietary amd64-microcode package is installed on Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1450188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450188] Re: Intermittent boot issues if the proprietary amd64-microcode package is installed on Ubuntu 15.04
Bug tagged as incomplete due to its age and the high chances that it was fixed by a kernel update (the bug is not in the amd64-microcode package, but rather on the kernel driver). Please retag it confirmed after re-testing on an up-to-date Ubuntu 15.10 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450188 Title: Intermittent boot issues if the proprietary amd64-microcode package is installed on Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1450188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662097] Re: lenovo t500 kernel hangs with flashing caps lock LED after installing intel-microcode
The flashing capslock LED is a kernel-has-crashed (aka "OOPS") indicator. It certainly looks like a bug in the microcode loader. For the record: It is possible to bypass the microcode loader. That would allow you to test that it is indeed the microcode loader, or to fix the system if you did not have a backup kernel/initramfs. To bypass the microcode loader, inside the boot loader (grub), instead of lauching the boot, you ask it to edit the boot config, scroll down to the "kernel command line" (starts with "linux"), and add "dis_ucode_ldr" (without the quotes). Then you tell grub to proceed booting. More details: https://help.ubuntu.com/community/Grub2/Troubleshooting#Editing_the_GRUB_2_Menu_During_Boot Anyway, it looks like this bug should be reassigned to the kernel. You will have to provide a lot more information for anyone to be able to help you, though. Relevant information: contents of /proc/cpuinfo, exactly what kernel is crashing (32 bit? 64 bit? package version?), and if at all possible, kernel logs when it crashes (boot in verbose mode to see). Also could be of help if you want to provide more data (without which this bug cannot be solved): https://wiki.ubuntu.com/DebuggingKernelBoot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662097 Title: lenovo t500 kernel hangs with flashing caps lock LED after installing intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1662097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662718] Re: Processor microcode firmware for AMD CPUs from amd64-microcode.
1. I need the contents of: cat /proc/cpuinfo dmesg | grep microcode dmesg | head -n 100 please attach the output of the above commands to this bug report. 2. Please describe in detail what you mean by "not working". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662718 Title: Processor microcode firmware for AMD CPUs from amd64-microcode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1662718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279184] Re: microcode.ctl (1.18~0+nmu2) package doesn't have /usr/sbin/microcode_ctl file
It is an empty package as designed. This is a transitional package, microcode.ctl is no more. Please refer to the intel-microcode package's documentation. Thank you. ** Changed in: microcode.ctl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279184 Title: microcode.ctl (1.18~0+nmu2) package doesn't have /usr/sbin/microcode_ctl file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/microcode.ctl/+bug/1279184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577161] Re: Please update Xenial and Willy to 1.5.2-1 (support mixed-stepping configurations)
Please update all still-supported Ubuntu releases to iucode-tool v1.5.2 + CVE-2017-0357 patch, or preferably to iucode-tool v2.1.1. Updating to iucode-tool v2.1.1 will fix: * CVE-2017-0357 - fixed in v2.1.1 * Incorrect handling of mixed-stepping systems (one of the two processor steppings *would not be updated* resulting in an unsupported runtime situation) - fixed in v1.5.2 * Memory usage - fixed in v1.6.1 * Reproducible build of the early-initramfs - fixed in v2.0 * Corrupted early-initramfs after y2038 issue - fixed in v2.1. ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-0357 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577161 Title: Please update Xenial and Willy to 1.5.2-1 (support mixed-stepping configurations) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iucode-tool/+bug/1577161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633818] Re: Kernel 4.8.0-25-generic does boot if intel-microcode is installed
Does this bug still exist in an up-to-date kernel? It is not an issue in intel-microcode, but rather a kernel defect. It has to be fixed by an updated kernel (and likely it has already been fixed)... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633818 Title: Kernel 4.8.0-25-generic does boot if intel-microcode is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1633818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644674] Re: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
*** This bug is a duplicate of bug 1608933 *** https://bugs.launchpad.net/bugs/1608933 ** This bug has been marked a duplicate of bug 1608933 package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644674 Title: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1644674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1423296] Re: Only one CPU core gets microcode updated
On Thu, Jan 5, 2017, at 07:59, dino99 wrote: > dmesg | grep -i microcode > [0.00] microcode: microcode updated early to revision 0x70a, date > = 2010-09-29 > [1.520819] microcode: sig=0x10677, pf=0x10, revision=0x70a > [1.529644] microcode: Microcode Update Driver: v2.01 > , Peter Oruba > > this is with 1 cpu with 4 cores: so the output should list all the cores > (intel q9550). This changed on newer kernels. You will notice the kernel message DOES NOT mention any particular cpu anymore (before, it would have CPU# somewhere). That means the kernel is not going to repeat the message for every "CPU" unless they happen to need different microcode, which is not true for your machine. Please check /proc/cpuinfo output: it should list the updated microcode revision for all cores. -- Henrique de Moraes Holschuh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423296 Title: Only one CPU core gets microcode updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iucode-tool/+bug/1423296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945305] Re: trackballs crashed with SIGABRT in __assert_fail_base()
Very likely fixed by the new upload from Debian (version 1.2.3-1 and later). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945305 Title: trackballs crashed with SIGABRT in __assert_fail_base() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trackballs/+bug/945305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms
Relevant information: I have uploaded to Debian yesterday, and it has already been auto- migrated to Ubuntu Artful Aardvark, the newest intel-microcode release (base date: 20170707). This new upstream release fixes the hyper-threading issue (as well as several other undisclosed issues) on Skylake-X and Kaby Lake processors. It also has all the previous fixes from the previous releases (so it fixes the other Skylakes as well). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662097] Re: lenovo t500 kernel hangs with flashing caps lock LED after installing intel-microcode
Rob, are things working for you now? Can we close this bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662097 Title: lenovo t500 kernel hangs with flashing caps lock LED after installing intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1662097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662097] Re: lenovo t500 kernel hangs with flashing caps lock LED after installing intel-microcode
Ok, I "closed" it by tagging it "invalid", since we don't know what really happened to that kernel (so "fixed" wouldn't really be correct). Thanks. ** Changed in: intel-microcode (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662097 Title: lenovo t500 kernel hangs with flashing caps lock LED after installing intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1662097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690512] Re: shutdown/restart/suspend freezes laptop on intel graphics
This is a Kabilake system, the intel-microcode does not support it as of 20161104 or 20170511 (upcoming release, to be uploaded in the next few days). Please ensure your BIOS/UEFI is up-to-date, latest known-to-be-available microcode is revision 0x58, so it is not impossible that there are available fixes through a vendor BIOS/UEFI update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690512 Title: shutdown/restart/suspend freezes laptop on intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1690512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577161] [NEW] Please update Xenial and Willy to 1.5.2-1 (support mixed-stepping configurations)
Public bug reported: I have fixed a major usability bug in iucode-tool 1.5.2, which dates back to iucode-tool 1.2. Without this fix, mixed-stepping hardware configurations are not supported automatically, and require manual configuration. Mixed-stepping configurations are somewhat common on Xeon 5300 (Mac PRO and IBM x-series), for example. I recommend that Ubuntu update their "Willy Werewolf" and "Xenial Xerus" distributions with these changes, in order to properly support users of mixed-stepping Xeon systems. Alternatively, iucode-tool v1.2 up to v1.5.1 must be configured with the --enable-cpuid-device build-time option, but that choice has some drawbacks: it requires root permissions as well as the cpuid module to be loaded in order to detect processor signatures, and it scales *very* poorly in large boxes with too many processors. ** Affects: iucode-tool (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577161 Title: Please update Xenial and Willy to 1.5.2-1 (support mixed-stepping configurations) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iucode-tool/+bug/1577161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637879] Re: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
> update-initramfs: deferring update (trigger activated) > cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file > or directory Read-only boot media is (currently?) unsupportable by anything that needs to update the initramfs... such as intel-microcode. I have no idea what can be done about this bug, but everything is working as it is supposed to: you have a read-only partition, the system cannot write to it and fails. All I know is that intel-microcode is never going to fix this issue. Creating live-cds that can have their kernels and initramfs updated is the business of whatever creates live-cds... and only possible if the live system is in read-write media in the first place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637879 Title: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1637879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637886] Re: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Looks like a duplicate... intel-microcode cannot work on read-only live media: it needs to update the initramfs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637886 Title: package intel-microcode 3.20151106.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1637886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557989] Re: having btrfs installed as the fs is causing a crash when trying to install the intel-microcode package
Well, a couple points. 1. Never attempt to update microcode from inside a VM. It is supposed to fail in the first place (not with a crash, though). Do it on the host /hyper-visor/dom0. 2. The processors showing an issue are too different, and running microcode updates that have been in the field for a long time, without any sort of crash reports. This is *extremely* unlikely to be an issue with the microcode update itself. 3. Therefore, this is leaves us with a bootloader, kernel or initramfs bug. 4. The live-cd issue might be an entirely different bug: the microcode update process requires that the initramfs image be modified, so it requires the live-cd bootloader to deal with reading the modified initramfs *properly*. It can be done using syslinux and the exactly correct setup for kernel/initramfs modification persistence (hint: no overlays). I have no idea if this specific live-cd does anything remotely like that, and if it doesn't use btrfs, it is likely to be a separate bug anyway. Now, microcode updates are applied by the kernel well before *anything* filesystem-related runs, so the btrfs kernel code is not directly involved with the microcode update process itself (the data is loaded by the *bootloader*). Unfortunately, we don't have enough information on this bug report to know what happened (we need a kernel log up to the crash for that :-( ). Anyway, this bug likely has to be reassigned to the kernel... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557989 Title: having btrfs installed as the fs is causing a crash when trying to install the intel-microcode package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1557989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
