Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1580579
| From | "hch@lst.de" <hch@lst.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") |
| Date | 2017-02-14 15:40 +0100 |
| Message-ID | <taMqS-320-29@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <t8RuF-3aL-3@gated-at.bofh.it> <t8X76-6JS-83@gated-at.bofh.it> <t9kQ3-4Jf-33@gated-at.bofh.it> <taLEt-2wc-5@gated-at.bofh.it> <taM7v-2Vs-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Ok, thanks for testing. Can you try the patch below? It fixes a clear problem which was partially papered over before the commit you bisected to, although it can't explain why blk-mq still works.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-14 14:50 +0100
Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-14 15:40 +0100
RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") Dexuan Cui <decui@microsoft.com> - 2017-02-14 15:50 +0100
Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-14 16:00 +0100
Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-14 17:40 +0100
RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") Dexuan Cui <decui@microsoft.com> - 2017-02-15 15:00 +0100
csiph-web