Added by Alexander Couzens about 9 years ago. Updated about 8 years ago.
100%
Description
first bad commit: 456f495d4e3199146590bcb5cd76e12053c33c9e.
commit is causing
Alexander Couzens wrote:
first bad commit: 456f495d4e3199146590bcb5cd76e12053c33c9e.
The commit before works?
commit is causing
- unreliable/broken sata (linux doesn't boot)
- broken usb
- usb storage: dd if=file of=/dev/sdb write broken data to usb storage
- usb serial: just stops
- lot's of errors in dmesg
Also, is there no way to assign a bug to someone?
Stefan Reinauer wrote:
Alexander Couzens wrote:
first bad commit: 456f495d4e3199146590bcb5cd76e12053c33c9e.
The commit before works?
yescommit is causing
- unreliable/broken sata (linux doesn't boot)
- broken usb
- usb storage: dd if=file of=/dev/sdb write broken data to usb storage
- usb serial: just stops
- lot's of errors in dmesg
Also, is there no way to assign a bug to someone?
it's possible. But not for somebody who is not in this project. everybody who hasn't assign to this project can only report stuff.
Alexander Couzens wrote:
first bad commit: 456f495d4e3199146590bcb5cd76e12053c33c9e.
Similar commit (a3e41c0) for 206ax led to instabilities too. We ended up
disabling CONFIG_PARALLEL_CPU_INIT there (see 0ace013).
Actually pre-456f495d4e3199146590bcb5cd76e12053c33c9e is troublesome too: sata will misbehave if the laptop is docked, although linux boots.