Per the earlier conversation:
https://irclogs.ubuntu.com/2018/09/25/%23ubuntu-devel.html#t09:22
need to know:
* exact version number of last working Linux kernel
* exact version number of non-working Linux kernel
--
You received this bug notification because you are a member of Kernel
Pa
TL;DR: probably mdadm commit from April 2018; see end.
Today's IRC logs of debugging session with reporter:
https://irclogs.ubuntu.com/2018/09/26/%23ubuntu-devel.html#t06:41
Current understanding of the situation from log analysis:
08:21 reboot with (4.15.0-29.31-generic), no problem
08:21
https://irclogs.ubuntu.com/2018/09/27/%23ubuntu-devel.html#t11:31
The BIOS shows a RAID1 (mirror) pair, this is designated as:
RAID Level: "Recovery (Cont.)" in the BIOS. (screenshot)
This stands for "Recovery Set" == RAID1/Mirror group.
Newer 'mdadm --detail-platform' only reports:
$ sudo
Christian: looking back and your reply in #478, it would appear that
you're on Mint, not Ubuntu. It is likely the case that Mint is still
shipping the buggy kernel(s).
We can see in #478: "When installing the Kernels provided above, I can
again do changes in BIOS and they stay over reboot. Howev
FWIW, the Intel-SPI Readme contains:
https://github.com/torvalds/linux/blob/master/Documentation/mtd/intel-
spi.txt
"makes it possible to read and write the SPI serial flash, if certain
protection bits are not set and locked."
"… If it finds any of them set, the whole MTD device is made re
I've emailed Mika Westerberg (author of the module) to ask to share
anything further documentation they've got that would allow a better
understanding of the (intended) operation of the 'intel-spi' module.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Page 5 of:
http://opensecuritytraining.info/IntroBIOS_files/Day2_03_Advanced%20x86%20-%20BIOS%20and%20SMM%20Internals%20-%20SPI%20Flash%20Protection%20Mechanisms.pptx
Talks about "Flash Protection Mechanism";
"Write Protect / Writes blocked / Not Range Specific / SMI# override:
Same as Write P
Have received an excellent reply from Mika Westerberg (thank you!). One
with a suggestion regarding 'GigaDevice' flash chips, and one regarding
certain 'Winbond' flash chips.
Is somebody with access or one of more of these machine(s) able to
provide insight into what flash parts are in their mach
(For clarity the above upload of linux (kernel)=4.13.0-21.24) is a
workaround that just disables compiling in of the module under
suspicion. Because the module is not compiled it, it will not therefore
be loaded either).
--
You received this bug notification because you are a member of Kernel
Pa
[The two theories provided by Mika Westerberg, verbatim]
"""
Instead I have a theory since as far as I know there have been to kinds
of issues.
1. Flash is left locked. This makes the BIOS impossible to save
settings.
This seems to happen only for GigaDevice flashes and for all of thos
Mika Westerberg emailed again with a pointer to the commit from a few
months ago, specifically dealing with a similar issue on Lenovo Yoga
machines:
"""
mfd: lpc_ich: Do not touch SPI-NOR write protection bit on Haswell/Broadwell
At least on Lenovo Thinkpad Yoga, the BIOS seems to monitor the SPI
Could somebody with the hardware also do a test with the following lines
commented out in 'intel-spi.c', commenting out the writel() that
disables SMI interrupt generation, re-compile the kernel and retest:
https://github.com/torvalds/linux/blob/8afda8b26d01ee26a60ef2f0284a7f01a5ed96f8/drivers/mtd
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Tes
Register map documentation for the SPI (Serial Peripheral Interface) in
recent Intels begins on page 5626
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z8000
-datasheet-vol-2.pdf
HSFSTS (Hardware Sequencer Status) + HSFCTL (Hardware Sequencer Control)
are covered on
@Paul sabret00the. Please can you file separate new bugs for the
"disassociated with its launcher icon", "my swap disk has issues", and
"I can't launch any Virtual Boxes". These are not related to the CMP
bit in the flash chip, and putting them on this bug report adds
confusion to this issue whic
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205791
Title:
Dell Vostro V131: special keys not working
Status in “linux”
** Tags removed: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1205791
Title:
Dell Vostro V131: special keys not working
Status in “linux” package in Ubuntu:
Incomplete
Bug de
Whoopie: please can you attach a copy of 'lspnp'.
** Description changed:
- Hi,
+ Bug filed, following conversation on IRC at:
- I own a Dell Vostro V131. This model has 3 special hotkeys (quick launch
keys, see
http://www.notebookcheck.net/fileadmin/_migrated/pics/v131tastatur_01.jpg).
- Th
Page 12 of:
http://odm.ubuntu.com/uhs/2011/Enabling%20Hotkey%20Features%20on%20Ubuntu.pdf
gives this as the Dell WMI GUID:
9DBB5994-A997-11DA-B012-B622A1EF5492 dell_wmi
Whoopie: are you seeing "unhandled WMI event" at the same time as the
key is pressed?
If this is not obviously the case it
19 matches
Mail list logo
