Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> On Sun, Oct 4, 2015 at 3:33 AM, Meelis Roos wrote: > >> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > >> sometimes it fails to boot with looping errors and finally a watchdog > >> timeout. This console log from a failure. Config is below. > > > > I noticed blk-mq

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> On Sun, Oct 4, 2015 at 3:33 AM, Meelis Roos wrote: > >> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > >> sometimes it fails to boot with looping errors and finally a watchdog > >> timeout. This console log from a failure. Config is below. > > > > I

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Sun, Oct 4, 2015 at 3:33 AM, Meelis Roos wrote: >> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, >> sometimes it fails to boot with looping errors and finally a watchdog >> timeout. This console log from a failure. Config is below. > > I noticed blk-mq related changes

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > sometimes it fails to boot with looping errors and finally a watchdog > timeout. This console log from a failure. Config is below. I noticed blk-mq related changes in todays git. Retested, loop_init still causes the

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > sometimes it fails to boot with looping errors and finally a watchdog > timeout. This console log from a failure. Config is below. I noticed blk-mq related changes in todays git. Retested, loop_init still causes the

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Sun, Oct 4, 2015 at 3:33 AM, Meelis Roos wrote: >> This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, >> sometimes it fails to boot with looping errors and finally a watchdog >> timeout. This console log from a failure. Config is below. > > I noticed blk-mq

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> > Yes, sorry - I applied the last chunk by hand because it was mangled by > > the web UI, and added ti to a wrong struct. > > > > Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times, > > but now it hangs again, seems to be the same message: > > > > [ 107.143910] kobject

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> > Yes, sorry - I applied the last chunk by hand because it was mangled by > > the web UI, and added ti to a wrong struct. > > > > Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times, > > but now it hangs again, seems to be the same message: > > > > [ 107.143910] kobject

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Mon, Sep 21, 2015 at 7:43 PM, Meelis Roos wrote: > > > Yes, sorry - I applied the last chunk by hand because it was mangled by > the web UI, and added ti to a wrong struct. > > Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times, > but now it hangs again, seems to be the same

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> >> > [ 106.370834] kobject (009f2dd8): tried to init an initialized > >> > object, something is seriously wrong. > >> > >> Akinobu found there is one race between CPU hotplug and add_disk, maybe > >> you can try the patch in the following link to see if it can fix your > >> issue. >

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Mon, Sep 21, 2015 at 3:26 PM, Meelis Roos wrote: >> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote: >> > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, >> > sometimes it fails to boot with looping errors and finally a watchdog >> > timeout. This console log from a

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote: > > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > > sometimes it fails to boot with looping errors and finally a watchdog > > timeout. This console log from a failure. Config is below. > > [...] > > [ 90.956986]

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote: > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > sometimes it fails to boot with looping errors and finally a watchdog > timeout. This console log from a failure. Config is below. > > [0.00] PROMLIB: Sun IEEE

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote: > > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > > sometimes it fails to boot with looping errors and finally a watchdog > > timeout. This console log from a failure. Config is below. > > [...] > > [

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Mon, Sep 21, 2015 at 3:26 PM, Meelis Roos wrote: >> On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote: >> > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, >> > sometimes it fails to boot with looping errors and finally a watchdog >> >

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Tue, Sep 15, 2015 at 3:06 AM, Meelis Roos wrote: > This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, > sometimes it fails to boot with looping errors and finally a watchdog > timeout. This console log from a failure. Config is below. > > [0.00]

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

On Mon, Sep 21, 2015 at 7:43 PM, Meelis Roos wrote: > > > Yes, sorry - I applied the last chunk by hand because it was mangled by > the web UI, and added ti to a wrong struct. > > Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times, > but now it hangs again, seems

Re: blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

> >> > [ 106.370834] kobject (009f2dd8): tried to init an initialized > >> > object, something is seriously wrong. > >> > >> Akinobu found there is one race between CPU hotplug and add_disk, maybe > >> you can try the patch in the following link to see if it can fix your > >> issue. >

blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, sometimes it fails to boot with looping errors and finally a watchdog timeout. This console log from a failure. Config is below. [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 3.31.0 2001/07/25 20:31' [0.00]

blk_mq_register_disk: kobject (00000000009f2dd8): tried to init an initialized object, something is seriously wrong.

This is 4.3.0-rc1 on Sun E220R (dual-CPU sparc64). Sometimes it boots, sometimes it fails to boot with looping errors and finally a watchdog timeout. This console log from a failure. Config is below. [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 3.31.0 2001/07/25 20:31' [0.00]