[FW ide-cs] Re: jvc cdrom drive

[FW ide-cs] Re: jvc cdrom drive

[Komuro]

On Thu, 03 May 2007 15:29:19 +0100
Richard Kennedy <richard@rsk.demon.co.uk> wrote:


IDE bugs should be posted to the linux-ide mailing list.


> Hi all, 
> I have a JVC MP-CDX1 cdrom drive that came with my laptop which used to
> work with ide-cs but stopped working with newer kernels.
> 
> I added its ident to ide-cs.c (see patch below) and the drive now is
> detected and gets mounted when plugged in and seems to work correctly.
> 
> But when I eject the card, pccardctl eject 0, the laptop locks up
> completely, there are no messages in the log, and the fan goes to full
> speed so I guess the cpu is running at 100%.
> Any ideas what's going wrong or how to debug it ? 
> Is there anything else I need to patch to get this working ?
> 
> Thanks
> Richard
> 
> card info :- 
> 
> PRODID_1="KME"
> PRODID_2="KXLC005"
> PRODID_3="00"
> PRODID_4=""
> MANFID=0032,2904
> FUNCID=8
> 
> log messages on insert :- 
> 
> May  3 11:22:52 mininote kernel: pccard: PCMCIA card inserted into slot 0
> May  3 11:22:52 mininote kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> May  3 11:22:52 mininote kernel: pcmcia: registering new device pcmcia0.0
> May  3 11:22:53 mininote kernel: hdc: UJDB130, ATAPI CD/DVD-ROM drive
> May  3 11:22:53 mininote kernel: ide1 at 0x190-0x197,0x396 on irq 3
> May  3 11:22:53 mininote kernel: ide-cs: hdc: Vpp = 0.0
> May  3 11:22:54 mininote kernel: hdc: ATAPI 20X CD-ROM drive, 128kB Cache
> May  3 11:22:54 mininote kernel: Uniform CD-ROM driver Revision: 3.20
> May  3 11:23:04 mininote hald: mounted /dev/hdc on behalf of uid 500
> May  3 11:23:34 mininote hald: unmounted /dev/hdc from '/media/FC_4 i386 ftp #1' on behalf of uid 500
> May  3 11:24:17 mininote kernel: pccard: card ejected from slot 0
> << lockup happened here >>
> 
> patch
> --- linux-2.6.21.1/drivers/ide/legacy/ide-cs.c.orig	2007-05-02 12:09:57.000000000 +0100
> +++ linux-2.6.21.1/drivers/ide/legacy/ide-cs.c	2007-05-02 12:12:40.000000000 +0100
> @@ -362,6 +362,7 @@
>  	PCMCIA_DEVICE_MANF_CARD(0x000a, 0x0000),	/* I-O Data CFA */
>  	PCMCIA_DEVICE_MANF_CARD(0x001c, 0x0001),	/* Mitsubishi CFA */
>  	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x0704),
> +	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x2904),        /* KME KXLCOO5 JVC MP-CDX1 */
>  	PCMCIA_DEVICE_MANF_CARD(0x0045, 0x0401),	/* SanDisk CFA */
>  	PCMCIA_DEVICE_MANF_CARD(0x0098, 0x0000),	/* Toshiba */
>  	PCMCIA_DEVICE_MANF_CARD(0x00a4, 0x002d),
> 
>    
> 

Best Regards
Komuro

Re: [FW ide-cs] Re: jvc cdrom drive lockup

[Richard Kennedy]

On Fri, 2007-05-04 at 23:32 +0900, Komuro wrote:
> On Thu, 03 May 2007 15:29:19 +0100
> Richard Kennedy <richard@rsk.demon.co.uk> wrote:
> 
> 
> IDE bugs should be posted to the linux-ide mailing list.
> 
> 
> > Hi all, 
> > I have a JVC MP-CDX1 cdrom drive that came with my laptop which used to
> > work with ide-cs but stopped working with newer kernels.
> > 
> > I added its ident to ide-cs.c (see patch below) and the drive now is
> > detected and gets mounted when plugged in and seems to work correctly.
> > 
> > But when I eject the card, pccardctl eject 0, the laptop locks up
> > completely, there are no messages in the log, and the fan goes to full
> > speed so I guess the cpu is running at 100%.
> > Any ideas what's going wrong or how to debug it ? 
> > Is there anything else I need to patch to get this working ?
> > 
> > Thanks
> > Richard
> > 
> > card info :- 
> > 
> > PRODID_1="KME"
> > PRODID_2="KXLC005"
> > PRODID_3="00"
> > PRODID_4=""
> > MANFID=0032,2904
> > FUNCID=8
> > 
> > log messages on insert :- 
> > 
> > May  3 11:22:52 mininote kernel: pccard: PCMCIA card inserted into slot 0
> > May  3 11:22:52 mininote kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> > May  3 11:22:52 mininote kernel: pcmcia: registering new device pcmcia0.0
> > May  3 11:22:53 mininote kernel: hdc: UJDB130, ATAPI CD/DVD-ROM drive
> > May  3 11:22:53 mininote kernel: ide1 at 0x190-0x197,0x396 on irq 3
> > May  3 11:22:53 mininote kernel: ide-cs: hdc: Vpp = 0.0
> > May  3 11:22:54 mininote kernel: hdc: ATAPI 20X CD-ROM drive, 128kB Cache
> > May  3 11:22:54 mininote kernel: Uniform CD-ROM driver Revision: 3.20
> > May  3 11:23:04 mininote hald: mounted /dev/hdc on behalf of uid 500
> > May  3 11:23:34 mininote hald: unmounted /dev/hdc from '/media/FC_4 i386 ftp #1' on behalf of uid 500
> > May  3 11:24:17 mininote kernel: pccard: card ejected from slot 0
> > << lockup happened here >>
> > 
> > patch
> > --- linux-2.6.21.1/drivers/ide/legacy/ide-cs.c.orig	2007-05-02 12:09:57.000000000 +0100
> > +++ linux-2.6.21.1/drivers/ide/legacy/ide-cs.c	2007-05-02 12:12:40.000000000 +0100
> > @@ -362,6 +362,7 @@
> >  	PCMCIA_DEVICE_MANF_CARD(0x000a, 0x0000),	/* I-O Data CFA */
> >  	PCMCIA_DEVICE_MANF_CARD(0x001c, 0x0001),	/* Mitsubishi CFA */
> >  	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x0704),
> > +	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x2904),        /* KME KXLCOO5 JVC MP-CDX1 */
> >  	PCMCIA_DEVICE_MANF_CARD(0x0045, 0x0401),	/* SanDisk CFA */
> >  	PCMCIA_DEVICE_MANF_CARD(0x0098, 0x0000),	/* Toshiba */
> >  	PCMCIA_DEVICE_MANF_CARD(0x00a4, 0x002d),
> > 
> >    
> > 
> 
> Best Regards
> Komuro

I rebuilt the kernel with the lock dependency checking turned on, which
shows up 2 problems (and also breaks the deadlock).

kernel: pccard: card ejected from slot 0
kernel: 
kernel: ======================================================
kernel: [ INFO: hard-safe -> hard-unsafe lock order detected ]
kernel: 2.6.21.1rsk #2
kernel: ------------------------------------------------------
kernel: pccardctl/3066 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
kernel:  (resource_lock){--..}, at: [<c04222e4>] __release_region+0x32/0xff
kernel: 
kernel: and this task is already holding:
kernel:  (ide_lock){++..}, at: [<c054c2a5>] ide_unregister+0x112/0x573
kernel: which would create a new lock dependency:
kernel:  (ide_lock){++..} -> (resource_lock){--..}
kernel: 
kernel: but this new dependency connects a hard-irq-safe lock:
kernel:  (ide_lock){++..}
kernel: ... which became hard-irq-safe at:
kernel:   [<c0430cdb>] clocksource_get_next+0x39/0x3f
kernel:   [<c0430cac>] clocksource_get_next+0xa/0x3f
kernel:   [<c0434fce>] __lock_acquire+0x3b9/0xb83
kernel:   [<c054e236>] ide_intr+0x15/0x1ba
kernel:   [<c04356fe>] __lock_acquire+0xae9/0xb83
kernel:   [<c04083bd>] mask_and_ack_8259A+0x1b/0xce
kernel:   [<c04357ff>] lock_acquire+0x67/0x81
kernel:   [<c054e236>] ide_intr+0x15/0x1ba
kernel:   [<c0600e95>] _spin_lock_irqsave+0x32/0x41
kernel:   [<c054e236>] ide_intr+0x15/0x1ba
kernel:   [<c054e236>] ide_intr+0x15/0x1ba
kernel:   [<c0448299>] handle_level_irq+0x6c/0xbb
kernel:   [<c044701e>] handle_IRQ_event+0x13/0x3d
kernel:   [<c04482a2>] handle_level_irq+0x75/0xbb
kernel:   [<c044822d>] handle_level_irq+0x0/0xbb
kernel:   [<c0406c4f>] do_IRQ+0xa5/0xca
kernel:   [<ffffffff>] 0xffffffff
kernel: 
kernel: to a hard-irq-unsafe lock:
kernel:  (resource_lock){--..}
kernel: ... which became hard-irq-unsafe at:
kernel: ...  [<c0409ba5>] save_stack_trace+0x1c/0x37
kernel:   [<c0422290>] request_resource+0x10/0x32
kernel:   [<c043506b>] __lock_acquire+0x456/0xb83
kernel:   [<c0422290>] request_resource+0x10/0x32
kernel:   [<c04356fe>] __lock_acquire+0xae9/0xb83
kernel:   [<c05202bb>] tty_register_ldisc+0x1c/0x5d
kernel:   [<c0430df6>] clocksource_register+0x4a/0x16e
kernel:   [<c04357ff>] lock_acquire+0x67/0x81
kernel:   [<c0422290>] request_resource+0x10/0x32
kernel:   [<c0600bff>] _write_lock+0x29/0x34
kernel:   [<c0422290>] request_resource+0x10/0x32
kernel:   [<c0422290>] request_resource+0x10/0x32
kernel:   [<c04ef604>] vgacon_startup+0x171/0x2fe
kernel:   [<c0736e4f>] con_init+0x17/0x213
kernel:   [<c05202f5>] tty_register_ldisc+0x56/0x5d
kernel:   [<c073695f>] console_init+0x1b/0x28
kernel:   [<c071a940>] start_kernel+0x1a1/0x3c6
kernel:   [<c071a42b>] unknown_bootoption+0x0/0x202
kernel:   [<ffffffff>] 0xffffffff

<< snipped lots more lock info >>

kernel: BUG: sleeping function called from invalid context at kernel/rwsem.c:20
kernel: in_atomic():0, irqs_disabled():1
kernel: INFO: lockdep is turned off.
kernel: irq event stamp: 2258
kernel: hardirqs last  enabled at (2257): [<c0462050>] kfree+0x78/0x7f
kernel: hardirqs last disabled at (2258): [<c0600db5>] _spin_lock_irq+0xc/0x3a
kernel: softirqs last  enabled at (2252): [<c0406b41>] do_softirq+0x4d/0xb6
kernel: softirqs last disabled at (2243): [<c0406b41>] do_softirq+0x4d/0xb6
kernel:  [<c042fda6>] down_read+0x15/0x4d
kernel:  [<c04e2498>] pci_get_subsys+0x68/0xea
kernel:  [<c04e2530>] pci_get_device+0x16/0x19
kernel:  [<c054b6f6>] init_hwif_default+0x28/0xf0
kernel:  [<c054c3d5>] ide_unregister+0x242/0x573
kernel:  [<d7b68018>] ide_release+0x18/0x28 [ide_cs]
kernel:  [<d7b68030>] ide_detach+0x8/0x14 [ide_cs]
kernel:  [<c055cd0c>] pcmcia_device_remove+0x50/0xb5
kernel:  [<c0543c50>] __device_release_driver+0x71/0x8e
kernel:  [<c05440a5>] device_release_driver+0x31/0x46
kernel:  [<c0543678>] bus_remove_device+0x70/0x80
kernel:  [<c0541d87>] device_del+0x162/0x1c6
kernel:  [<c0541df3>] device_unregister+0x8/0x10
kernel:  [<c055c95c>] pcmcia_card_remove+0x58/0x77
kernel:  [<c055d4da>] ds_event+0x56/0x87
kernel:  [<c04d5181>] kobject_get+0xf/0x13
kernel:  [<c05590e2>] send_event+0x31/0x49
kernel:  [<c05592c1>] socket_shutdown+0xc/0xb3
kernel:  [<c0559384>] socket_remove+0x1c/0x26
kernel:  [<c05593cd>] pcmcia_eject_card+0x3f/0x4c
kernel:  [<c055bcfc>] pccard_store_eject+0x1b/0x22
kernel:  [<c055bce1>] pccard_store_eject+0x0/0x22
kernel:  [<c054172b>] dev_attr_store+0x27/0x2c
kernel:  [<c049b74b>] sysfs_write_file+0xbf/0xe8
kernel:  [<c049b68c>] sysfs_write_file+0x0/0xe8
kernel:  [<c0465ef1>] vfs_write+0xa8/0x154
kernel:  [<c0466430>] sys_write+0x41/0x67
kernel:  [<c0404c1a>] sysenter_past_esp+0x5f/0x99
kernel:  =======================

Cheers
Richard

Re: [ide-cs] [PCI: fix race with pci_walk_bus and pci_destroy_dev] introduced [jvc cdrom drive lockup] problem

[Komuro]

Hi,

The ide-cs ejection lock up problem is introduced by
[PATCH] PCI: fix race with pci_walk_bus and pci_destroy_dev.
(found by bisect method)

Mr. Zhang Yanmin,
do you have any idea to fix ide-cs ejection problem?


>commit d71374dafbba7ec3f67371d3b7e9f6310a588808
>Author: Zhang Yanmin <yanmin.zhang@intel.com>
>Date:   Fri Jun 2 12:35:43 2006 +0800
>
>    [PATCH] PCI: fix race with pci_walk_bus and pci_destroy_dev
>
>    pci_walk_bus has a race with pci_destroy_dev. When cb is called
>    in pci_walk_bus, pci_destroy_dev might unlink the dev pointed by next.
>    Later on in the next loop, pointer next becomes NULL and cause
>    kernel panic.
>
>    Below patch against 2.6.17-rc4 fixes it by changing pci_bus_lock (spin_lock)
>    to pci_bus_sem (rw_semaphore).
>
>    Signed-off-by: Zhang Yanmin <yanmin.zhang@intel.com>
>    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>


Best Regards
Komuro


> On Fri, 2007-05-04 at 23:32 +0900, Komuro wrote:
> > On Thu, 03 May 2007 15:29:19 +0100
> > Richard Kennedy <richard@rsk.demon.co.uk> wrote:
> > 
> > 
> > IDE bugs should be posted to the linux-ide mailing list.
> > 
> > 
> > > Hi all, 
> > > I have a JVC MP-CDX1 cdrom drive that came with my laptop which used to
> > > work with ide-cs but stopped working with newer kernels.
> > > 
> > > I added its ident to ide-cs.c (see patch below) and the drive now is
> > > detected and gets mounted when plugged in and seems to work correctly.
> > > 
> > > But when I eject the card, pccardctl eject 0, the laptop locks up
> > > completely, there are no messages in the log, and the fan goes to full
> > > speed so I guess the cpu is running at 100%.
> > > Any ideas what's going wrong or how to debug it ? 
> > > Is there anything else I need to patch to get this working ?
> > > 
> > > Thanks
> > > Richard
> > > 
> > > card info :- 
> > > 
> > > PRODID_1="KME"
> > > PRODID_2="KXLC005"
> > > PRODID_3="00"
> > > PRODID_4=""
> > > MANFID=0032,2904
> > > FUNCID=8
> > > 
> > > log messages on insert :- 
> > > 
> > > May  3 11:22:52 mininote kernel: pccard: PCMCIA card inserted into slot 0
> > > May  3 11:22:52 mininote kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> > > May  3 11:22:52 mininote kernel: pcmcia: registering new device pcmcia0.0
> > > May  3 11:22:53 mininote kernel: hdc: UJDB130, ATAPI CD/DVD-ROM drive
> > > May  3 11:22:53 mininote kernel: ide1 at 0x190-0x197,0x396 on irq 3
> > > May  3 11:22:53 mininote kernel: ide-cs: hdc: Vpp = 0.0
> > > May  3 11:22:54 mininote kernel: hdc: ATAPI 20X CD-ROM drive, 128kB Cache
> > > May  3 11:22:54 mininote kernel: Uniform CD-ROM driver Revision: 3.20
> > > May  3 11:23:04 mininote hald: mounted /dev/hdc on behalf of uid 500
> > > May  3 11:23:34 mininote hald: unmounted /dev/hdc from '/media/FC_4 i386 ftp #1' on behalf of uid 500
> > > May  3 11:24:17 mininote kernel: pccard: card ejected from slot 0
> > > << lockup happened here >>
> > > 
> > > patch
> > > --- linux-2.6.21.1/drivers/ide/legacy/ide-cs.c.orig	2007-05-02 12:09:57.000000000 +0100
> > > +++ linux-2.6.21.1/drivers/ide/legacy/ide-cs.c	2007-05-02 12:12:40.000000000 +0100
> > > @@ -362,6 +362,7 @@
> > >  	PCMCIA_DEVICE_MANF_CARD(0x000a, 0x0000),	/* I-O Data CFA */
> > >  	PCMCIA_DEVICE_MANF_CARD(0x001c, 0x0001),	/* Mitsubishi CFA */
> > >  	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x0704),
> > > +	PCMCIA_DEVICE_MANF_CARD(0x0032, 0x2904),        /* KME KXLCOO5 JVC MP-CDX1 */
> > >  	PCMCIA_DEVICE_MANF_CARD(0x0045, 0x0401),	/* SanDisk CFA */
> > >  	PCMCIA_DEVICE_MANF_CARD(0x0098, 0x0000),	/* Toshiba */
> > >  	PCMCIA_DEVICE_MANF_CARD(0x00a4, 0x002d),
> > > 
> > >    
> > > 
> > 
> > Best Regards
> > Komuro
> 
> I rebuilt the kernel with the lock dependency checking turned on, which
> shows up 2 problems (and also breaks the deadlock).
> 
> kernel: pccard: card ejected from slot 0
> kernel: 
> kernel: ======================================================
> kernel: [ INFO: hard-safe -> hard-unsafe lock order detected ]
> kernel: 2.6.21.1rsk #2
> kernel: ------------------------------------------------------
> kernel: pccardctl/3066 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
> kernel:  (resource_lock){--..}, at: [<c04222e4>] __release_region+0x32/0xff
> kernel: 
> kernel: and this task is already holding:
> kernel:  (ide_lock){++..}, at: [<c054c2a5>] ide_unregister+0x112/0x573
> kernel: which would create a new lock dependency:
> kernel:  (ide_lock){++..} -> (resource_lock){--..}
> kernel: 
> kernel: but this new dependency connects a hard-irq-safe lock:
> kernel:  (ide_lock){++..}
> kernel: ... which became hard-irq-safe at:
> kernel:   [<c0430cdb>] clocksource_get_next+0x39/0x3f
> kernel:   [<c0430cac>] clocksource_get_next+0xa/0x3f
> kernel:   [<c0434fce>] __lock_acquire+0x3b9/0xb83
> kernel:   [<c054e236>] ide_intr+0x15/0x1ba
> kernel:   [<c04356fe>] __lock_acquire+0xae9/0xb83
> kernel:   [<c04083bd>] mask_and_ack_8259A+0x1b/0xce
> kernel:   [<c04357ff>] lock_acquire+0x67/0x81
> kernel:   [<c054e236>] ide_intr+0x15/0x1ba
> kernel:   [<c0600e95>] _spin_lock_irqsave+0x32/0x41
> kernel:   [<c054e236>] ide_intr+0x15/0x1ba
> kernel:   [<c054e236>] ide_intr+0x15/0x1ba
> kernel:   [<c0448299>] handle_level_irq+0x6c/0xbb
> kernel:   [<c044701e>] handle_IRQ_event+0x13/0x3d
> kernel:   [<c04482a2>] handle_level_irq+0x75/0xbb
> kernel:   [<c044822d>] handle_level_irq+0x0/0xbb
> kernel:   [<c0406c4f>] do_IRQ+0xa5/0xca
> kernel:   [<ffffffff>] 0xffffffff
> kernel: 
> kernel: to a hard-irq-unsafe lock:
> kernel:  (resource_lock){--..}
> kernel: ... which became hard-irq-unsafe at:
> kernel: ...  [<c0409ba5>] save_stack_trace+0x1c/0x37
> kernel:   [<c0422290>] request_resource+0x10/0x32
> kernel:   [<c043506b>] __lock_acquire+0x456/0xb83
> kernel:   [<c0422290>] request_resource+0x10/0x32
> kernel:   [<c04356fe>] __lock_acquire+0xae9/0xb83
> kernel:   [<c05202bb>] tty_register_ldisc+0x1c/0x5d
> kernel:   [<c0430df6>] clocksource_register+0x4a/0x16e
> kernel:   [<c04357ff>] lock_acquire+0x67/0x81
> kernel:   [<c0422290>] request_resource+0x10/0x32
> kernel:   [<c0600bff>] _write_lock+0x29/0x34
> kernel:   [<c0422290>] request_resource+0x10/0x32
> kernel:   [<c0422290>] request_resource+0x10/0x32
> kernel:   [<c04ef604>] vgacon_startup+0x171/0x2fe
> kernel:   [<c0736e4f>] con_init+0x17/0x213
> kernel:   [<c05202f5>] tty_register_ldisc+0x56/0x5d
> kernel:   [<c073695f>] console_init+0x1b/0x28
> kernel:   [<c071a940>] start_kernel+0x1a1/0x3c6
> kernel:   [<c071a42b>] unknown_bootoption+0x0/0x202
> kernel:   [<ffffffff>] 0xffffffff
> 
> << snipped lots more lock info >>
> 
> kernel: BUG: sleeping function called from invalid context at kernel/rwsem.c:20
> kernel: in_atomic():0, irqs_disabled():1
> kernel: INFO: lockdep is turned off.
> kernel: irq event stamp: 2258
> kernel: hardirqs last  enabled at (2257): [<c0462050>] kfree+0x78/0x7f
> kernel: hardirqs last disabled at (2258): [<c0600db5>] _spin_lock_irq+0xc/0x3a
> kernel: softirqs last  enabled at (2252): [<c0406b41>] do_softirq+0x4d/0xb6
> kernel: softirqs last disabled at (2243): [<c0406b41>] do_softirq+0x4d/0xb6
> kernel:  [<c042fda6>] down_read+0x15/0x4d
> kernel:  [<c04e2498>] pci_get_subsys+0x68/0xea
> kernel:  [<c04e2530>] pci_get_device+0x16/0x19
> kernel:  [<c054b6f6>] init_hwif_default+0x28/0xf0
> kernel:  [<c054c3d5>] ide_unregister+0x242/0x573
> kernel:  [<d7b68018>] ide_release+0x18/0x28 [ide_cs]
> kernel:  [<d7b68030>] ide_detach+0x8/0x14 [ide_cs]
> kernel:  [<c055cd0c>] pcmcia_device_remove+0x50/0xb5
> kernel:  [<c0543c50>] __device_release_driver+0x71/0x8e
> kernel:  [<c05440a5>] device_release_driver+0x31/0x46
> kernel:  [<c0543678>] bus_remove_device+0x70/0x80
> kernel:  [<c0541d87>] device_del+0x162/0x1c6
> kernel:  [<c0541df3>] device_unregister+0x8/0x10
> kernel:  [<c055c95c>] pcmcia_card_remove+0x58/0x77
> kernel:  [<c055d4da>] ds_event+0x56/0x87
> kernel:  [<c04d5181>] kobject_get+0xf/0x13
> kernel:  [<c05590e2>] send_event+0x31/0x49
> kernel:  [<c05592c1>] socket_shutdown+0xc/0xb3
> kernel:  [<c0559384>] socket_remove+0x1c/0x26
> kernel:  [<c05593cd>] pcmcia_eject_card+0x3f/0x4c
> kernel:  [<c055bcfc>] pccard_store_eject+0x1b/0x22
> kernel:  [<c055bce1>] pccard_store_eject+0x0/0x22
> kernel:  [<c054172b>] dev_attr_store+0x27/0x2c
> kernel:  [<c049b74b>] sysfs_write_file+0xbf/0xe8
> kernel:  [<c049b68c>] sysfs_write_file+0x0/0xe8
> kernel:  [<c0465ef1>] vfs_write+0xa8/0x154
> kernel:  [<c0466430>] sys_write+0x41/0x67
> kernel:  [<c0404c1a>] sysenter_past_esp+0x5f/0x99
> kernel:  =======================
> 
> Cheers
> Richard
> 

Re: [FW ide-cs] Re: jvc cdrom drive lockup

[Zhang, Yanmin]

On Sun, 2007-05-06 at 16:00 +0100, Richard Kennedy wrote:
> On Fri, 2007-05-04 at 23:32 +0900, Komuro wrote:
> > On Thu, 03 May 2007 15:29:19 +0100
> > Richard Kennedy <richard@rsk.demon.co.uk> wrote:
> > 
> > 
> > IDE bugs should be posted to the linux-ide mailing list.
> > 
> > 
> > > Hi all, 
> > > I have a JVC MP-CDX1 cdrom drive that came with my laptop which used to
> > > work with ide-cs but stopped working with newer kernels.
> > > 
> > > I added its ident to ide-cs.c (see patch below) and the drive now is
> > > detected and gets mounted when plugged in and seems to work correctly.
> > > 
> > > But when I eject the card, pccardctl eject 0, the laptop locks up
> > > completely, there are no messages in the log, and the fan goes to full
> > > speed so I guess the cpu is running at 100%.
> > > Any ideas what's going wrong or how to debug it ? 
> > > Is there anything else I need to patch to get this working ?
> > > 
> > > Thanks
> > > Richard
> > > 
> > > card info :- 
> > > 
> > > May  3 11:22:52 mininote kernel: pccard: PCMCIA card inserted into slot 0
> > > May  3 11:22:52 mininote kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> > > May  3 11:22:52 mininote kernel: pcmcia: registering new device pcmcia0.0
> > > May  3 11:22:53 mininote kernel: hdc: UJDB130, ATAPI CD/DVD-ROM drive
> > > May  3 11:22:53 mininote kernel: ide1 at 0x190-0x197,0x396 on irq 3
> > > May  3 11:22:53 mininote kernel: ide-cs: hdc: Vpp = 0.0
> > > May  3 11:22:54 mininote kernel: hdc: ATAPI 20X CD-ROM drive, 128kB Cache
> > > May  3 11:22:54 mininote kernel: Uniform CD-ROM driver Revision: 3.20
> > > May  3 11:23:04 mininote hald: mounted /dev/hdc on behalf of uid 500
> > > May  3 11:23:34 mininote hald: unmounted /dev/hdc from '/media/FC_4 i386 ftp #1' on behalf of uid 500
> > > May  3 11:24:17 mininote kernel: pccard: card ejected from slot 0
> > > << lockup happened here >>

> I rebuilt the kernel with the lock dependency checking turned on, which
> shows up 2 problems (and also breaks the deadlock).
> 
> kernel: pccard: card ejected from slot 0
> kernel: 

> kernel: BUG: sleeping function called from invalid context at kernel/rwsem.c:20
> kernel: in_atomic():0, irqs_disabled():1
> kernel: INFO: lockdep is turned off.
> kernel: irq event stamp: 2258
> kernel: hardirqs last  enabled at (2257): [<c0462050>] kfree+0x78/0x7f
> kernel: hardirqs last disabled at (2258): [<c0600db5>] _spin_lock_irq+0xc/0x3a
> kernel: softirqs last  enabled at (2252): [<c0406b41>] do_softirq+0x4d/0xb6
> kernel: softirqs last disabled at (2243): [<c0406b41>] do_softirq+0x4d/0xb6
> kernel:  [<c042fda6>] down_read+0x15/0x4d
> kernel:  [<c04e2498>] pci_get_subsys+0x68/0xea
> kernel:  [<c04e2530>] pci_get_device+0x16/0x19
> kernel:  [<c054b6f6>] init_hwif_default+0x28/0xf0
> kernel:  [<c054c3d5>] ide_unregister+0x242/0x573
> kernel:  [<d7b68018>] ide_release+0x18/0x28 [ide_cs]
> kernel:  [<d7b68030>] ide_detach+0x8/0x14 [ide_cs]
> kernel:  [<c055cd0c>] pcmcia_device_remove+0x50/0xb5
> kernel:  [<c0543c50>] __device_release_driver+0x71/0x8e
> kernel:  [<c05440a5>] device_release_driver+0x31/0x46
> kernel:  [<c0543678>] bus_remove_device+0x70/0x80
> kernel:  [<c0541d87>] device_del+0x162/0x1c6
> kernel:  [<c0541df3>] device_unregister+0x8/0x10
> kernel:  [<c055c95c>] pcmcia_card_remove+0x58/0x77
> kernel:  [<c055d4da>] ds_event+0x56/0x87
> kernel:  [<c04d5181>] kobject_get+0xf/0x13
> kernel:  [<c05590e2>] send_event+0x31/0x49
> kernel:  [<c05592c1>] socket_shutdown+0xc/0xb3
> kernel:  [<c0559384>] socket_remove+0x1c/0x26
> kernel:  [<c05593cd>] pcmcia_eject_card+0x3f/0x4c
> kernel:  [<c055bcfc>] pccard_store_eject+0x1b/0x22
> kernel:  [<c055bce1>] pccard_store_eject+0x0/0x22
> kernel:  [<c054172b>] dev_attr_store+0x27/0x2c
> kernel:  [<c049b74b>] sysfs_write_file+0xbf/0xe8
> kernel:  [<c049b68c>] sysfs_write_file+0x0/0xe8
> kernel:  [<c0465ef1>] vfs_write+0xa8/0x154
> kernel:  [<c0466430>] sys_write+0x41/0x67
> kernel:  [<c0404c1a>] sysenter_past_esp+0x5f/0x99
> kernel:  =======================
Before calling init_hwif_default, ide_unregister gets lock ide_lock and disables irq.
init_hwif_default calls ide_default_io_base which calls pci_get_device and later
pci_get_subsys tries to apply for semaphore pci_bus_sem and goes to sleep.

Mostly, pci_get_device should be called when irq is turned on.

I still don't understand an issue. If you test it on a mobile, mostly, the process won't
sleep when applying for pci_bus_sem because there is no too many opportunities for 2 processes
to apply for the semaphore at the same time.

As just needing know if pci is initiated, ide_default_io_base just needs find if list
pci_devices is empty.

Could you try below patch against 2.6.21?

Signed-off-by: Zhang Yanmin <yanmin.zhang@intel.com>

---

diff -Nraup linux-2.6.21/drivers/pci/probe.c linux-2.6.21_fix/drivers/pci/probe.c
--- linux-2.6.21/drivers/pci/probe.c	2007-05-10 11:35:06.000000000 +0800
+++ linux-2.6.21_fix/drivers/pci/probe.c	2007-05-10 13:33:57.000000000 +0800
@@ -22,6 +22,18 @@ EXPORT_SYMBOL(pci_root_buses);
 
 LIST_HEAD(pci_devices);
 
+/*
+ * Some device drivers need know if pci is initiated.
+ * Basically, we think pci is not initiated when there
+ * is no device in list of pci_devices.
+ */
+int no_pci_devices(void)
+{
+	return list_empty(&pci_devices);
+}
+
+EXPORT_SYMBOL(no_pci_devices);
+
 #ifdef HAVE_PCI_LEGACY
 /**
  * pci_create_legacy_files - create legacy I/O port and memory files
diff -Nraup linux-2.6.21/include/asm-i386/ide.h linux-2.6.21_fix/include/asm-i386/ide.h
--- linux-2.6.21/include/asm-i386/ide.h	2007-02-05 02:44:54.000000000 +0800
+++ linux-2.6.21_fix/include/asm-i386/ide.h	2007-05-10 13:15:57.000000000 +0800
@@ -40,14 +40,13 @@ static __inline__ int ide_default_irq(un
 
 static __inline__ unsigned long ide_default_io_base(int index)
 {
-	struct pci_dev *pdev;
 	/*
 	 *	If PCI is present then it is not safe to poke around
 	 *	the other legacy IDE ports. Only 0x1f0 and 0x170 are
 	 *	defined compatibility mode ports for PCI. A user can 
 	 *	override this using ide= but we must default safe.
 	 */
-	if ((pdev = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, NULL)) == NULL) {
+	if (no_pci_devices()) {
 		switch(index) {
 			case 2: return 0x1e8;
 			case 3: return 0x168;
@@ -55,7 +54,6 @@ static __inline__ unsigned long ide_defa
 			case 5: return 0x160;
 		}
 	}
-	pci_dev_put(pdev);
 	switch (index) {
 		case 0:	return 0x1f0;
 		case 1:	return 0x170;
diff -Nraup linux-2.6.21/include/linux/pci.h linux-2.6.21_fix/include/linux/pci.h
--- linux-2.6.21/include/linux/pci.h	2007-05-10 11:35:07.000000000 +0800
+++ linux-2.6.21_fix/include/linux/pci.h	2007-05-10 13:33:43.000000000 +0800
@@ -424,6 +424,8 @@ extern struct bus_type pci_bus_type;
  * code, or pci core code. */
 extern struct list_head pci_root_buses;	/* list of all known PCI buses */
 extern struct list_head pci_devices;	/* list of all devices */
+/* Some device drivers need know if pci is initiated */
+extern int no_pci_devices(void);
 
 void pcibios_fixup_bus(struct pci_bus *);
 int __must_check pcibios_enable_device(struct pci_dev *, int mask);
@@ -709,6 +711,7 @@ static inline struct pci_dev *pci_get_cl
 { return NULL; }
 
 #define pci_dev_present(ids)	(0)
+#define no_pci_devices()	(1)
 #define pci_find_present(ids)	(NULL)
 #define pci_dev_put(dev)	do { } while (0)
 

Re: [FW ide-cs] Re: jvc cdrom drive lockup

[Richard Kennedy]

On Thu, 2007-05-10 at 14:06 +0800, Zhang, Yanmin wrote:
> On Sun, 2007-05-06 at 16:00 +0100, Richard Kennedy wrote:
> > On Fri, 2007-05-04 at 23:32 +0900, Komuro wrote:
> > > On Thu, 03 May 2007 15:29:19 +0100
> > > Richard Kennedy <richard@rsk.demon.co.uk> wrote:
> > > 
> > > 
> > > IDE bugs should be posted to the linux-ide mailing list.
> > > 
> > > 
> > > > Hi all, 
> > > > I have a JVC MP-CDX1 cdrom drive that came with my laptop which used to
> > > > work with ide-cs but stopped working with newer kernels.
> > > > 
> > > > I added its ident to ide-cs.c (see patch below) and the drive now is
> > > > detected and gets mounted when plugged in and seems to work correctly.
> > > > 
> > > > But when I eject the card, pccardctl eject 0, the laptop locks up
> > > > completely, there are no messages in the log, and the fan goes to full
> > > > speed so I guess the cpu is running at 100%.
> > > > Any ideas what's going wrong or how to debug it ? 
> > > > Is there anything else I need to patch to get this working ?
> > > > 
> > > > Thanks
> > > > Richard
> > > > 
> > > > card info :- 
> > > > 
> > > > May  3 11:22:52 mininote kernel: pccard: PCMCIA card inserted into slot 0
> > > > May  3 11:22:52 mininote kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> > > > May  3 11:22:52 mininote kernel: pcmcia: registering new device pcmcia0.0
> > > > May  3 11:22:53 mininote kernel: hdc: UJDB130, ATAPI CD/DVD-ROM drive
> > > > May  3 11:22:53 mininote kernel: ide1 at 0x190-0x197,0x396 on irq 3
> > > > May  3 11:22:53 mininote kernel: ide-cs: hdc: Vpp = 0.0
> > > > May  3 11:22:54 mininote kernel: hdc: ATAPI 20X CD-ROM drive, 128kB Cache
> > > > May  3 11:22:54 mininote kernel: Uniform CD-ROM driver Revision: 3.20
> > > > May  3 11:23:04 mininote hald: mounted /dev/hdc on behalf of uid 500
> > > > May  3 11:23:34 mininote hald: unmounted /dev/hdc from '/media/FC_4 i386 ftp #1' on behalf of uid 500
> > > > May  3 11:24:17 mininote kernel: pccard: card ejected from slot 0
> > > > << lockup happened here >>
> 
> > I rebuilt the kernel with the lock dependency checking turned on, which
> > shows up 2 problems (and also breaks the deadlock).
> > 
> > kernel: pccard: card ejected from slot 0
> > kernel: 
> 
> > kernel: BUG: sleeping function called from invalid context at kernel/rwsem.c:20
> > kernel: in_atomic():0, irqs_disabled():1
> > kernel: INFO: lockdep is turned off.
> > kernel: irq event stamp: 2258
> > kernel: hardirqs last  enabled at (2257): [<c0462050>] kfree+0x78/0x7f
> > kernel: hardirqs last disabled at (2258): [<c0600db5>] _spin_lock_irq+0xc/0x3a
> > kernel: softirqs last  enabled at (2252): [<c0406b41>] do_softirq+0x4d/0xb6
> > kernel: softirqs last disabled at (2243): [<c0406b41>] do_softirq+0x4d/0xb6
> > kernel:  [<c042fda6>] down_read+0x15/0x4d
> > kernel:  [<c04e2498>] pci_get_subsys+0x68/0xea
> > kernel:  [<c04e2530>] pci_get_device+0x16/0x19
> > kernel:  [<c054b6f6>] init_hwif_default+0x28/0xf0
> > kernel:  [<c054c3d5>] ide_unregister+0x242/0x573
> > kernel:  [<d7b68018>] ide_release+0x18/0x28 [ide_cs]
> > kernel:  [<d7b68030>] ide_detach+0x8/0x14 [ide_cs]
> > kernel:  [<c055cd0c>] pcmcia_device_remove+0x50/0xb5
> > kernel:  [<c0543c50>] __device_release_driver+0x71/0x8e
> > kernel:  [<c05440a5>] device_release_driver+0x31/0x46
> > kernel:  [<c0543678>] bus_remove_device+0x70/0x80
> > kernel:  [<c0541d87>] device_del+0x162/0x1c6
> > kernel:  [<c0541df3>] device_unregister+0x8/0x10
> > kernel:  [<c055c95c>] pcmcia_card_remove+0x58/0x77
> > kernel:  [<c055d4da>] ds_event+0x56/0x87
> > kernel:  [<c04d5181>] kobject_get+0xf/0x13
> > kernel:  [<c05590e2>] send_event+0x31/0x49
> > kernel:  [<c05592c1>] socket_shutdown+0xc/0xb3
> > kernel:  [<c0559384>] socket_remove+0x1c/0x26
> > kernel:  [<c05593cd>] pcmcia_eject_card+0x3f/0x4c
> > kernel:  [<c055bcfc>] pccard_store_eject+0x1b/0x22
> > kernel:  [<c055bce1>] pccard_store_eject+0x0/0x22
> > kernel:  [<c054172b>] dev_attr_store+0x27/0x2c
> > kernel:  [<c049b74b>] sysfs_write_file+0xbf/0xe8
> > kernel:  [<c049b68c>] sysfs_write_file+0x0/0xe8
> > kernel:  [<c0465ef1>] vfs_write+0xa8/0x154
> > kernel:  [<c0466430>] sys_write+0x41/0x67
> > kernel:  [<c0404c1a>] sysenter_past_esp+0x5f/0x99
> > kernel:  =======================
> Before calling init_hwif_default, ide_unregister gets lock ide_lock and disables irq.
> init_hwif_default calls ide_default_io_base which calls pci_get_device and later
> pci_get_subsys tries to apply for semaphore pci_bus_sem and goes to sleep.
> 
> Mostly, pci_get_device should be called when irq is turned on.
> 
> I still don't understand an issue. If you test it on a mobile, mostly, the process won't
> sleep when applying for pci_bus_sem because there is no too many opportunities for 2 processes
> to apply for the semaphore at the same time.
> 
> As just needing know if pci is initiated, ide_default_io_base just needs find if list
> pci_devices is empty.
> 
> Could you try below patch against 2.6.21?
> 
> Signed-off-by: Zhang Yanmin <yanmin.zhang@intel.com>
> 
> ---
> 
> diff -Nraup linux-2.6.21/drivers/pci/probe.c linux-2.6.21_fix/drivers/pci/probe.c
> --- linux-2.6.21/drivers/pci/probe.c	2007-05-10 11:35:06.000000000 +0800
> +++ linux-2.6.21_fix/drivers/pci/probe.c	2007-05-10 13:33:57.000000000 +0800
> @@ -22,6 +22,18 @@ EXPORT_SYMBOL(pci_root_buses);
>  
>  LIST_HEAD(pci_devices);
>  
> +/*
> + * Some device drivers need know if pci is initiated.
> + * Basically, we think pci is not initiated when there
> + * is no device in list of pci_devices.
> + */
> +int no_pci_devices(void)
> +{
> +	return list_empty(&pci_devices);
> +}
> +
> +EXPORT_SYMBOL(no_pci_devices);
> +
>  #ifdef HAVE_PCI_LEGACY
>  /**
>   * pci_create_legacy_files - create legacy I/O port and memory files
> diff -Nraup linux-2.6.21/include/asm-i386/ide.h linux-2.6.21_fix/include/asm-i386/ide.h
> --- linux-2.6.21/include/asm-i386/ide.h	2007-02-05 02:44:54.000000000 +0800
> +++ linux-2.6.21_fix/include/asm-i386/ide.h	2007-05-10 13:15:57.000000000 +0800
> @@ -40,14 +40,13 @@ static __inline__ int ide_default_irq(un
>  
>  static __inline__ unsigned long ide_default_io_base(int index)
>  {
> -	struct pci_dev *pdev;
>  	/*
>  	 *	If PCI is present then it is not safe to poke around
>  	 *	the other legacy IDE ports. Only 0x1f0 and 0x170 are
>  	 *	defined compatibility mode ports for PCI. A user can 
>  	 *	override this using ide= but we must default safe.
>  	 */
> -	if ((pdev = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, NULL)) == NULL) {
> +	if (no_pci_devices()) {
>  		switch(index) {
>  			case 2: return 0x1e8;
>  			case 3: return 0x168;
> @@ -55,7 +54,6 @@ static __inline__ unsigned long ide_defa
>  			case 5: return 0x160;
>  		}
>  	}
> -	pci_dev_put(pdev);
>  	switch (index) {
>  		case 0:	return 0x1f0;
>  		case 1:	return 0x170;
> diff -Nraup linux-2.6.21/include/linux/pci.h linux-2.6.21_fix/include/linux/pci.h
> --- linux-2.6.21/include/linux/pci.h	2007-05-10 11:35:07.000000000 +0800
> +++ linux-2.6.21_fix/include/linux/pci.h	2007-05-10 13:33:43.000000000 +0800
> @@ -424,6 +424,8 @@ extern struct bus_type pci_bus_type;
>   * code, or pci core code. */
>  extern struct list_head pci_root_buses;	/* list of all known PCI buses */
>  extern struct list_head pci_devices;	/* list of all devices */
> +/* Some device drivers need know if pci is initiated */
> +extern int no_pci_devices(void);
>  
>  void pcibios_fixup_bus(struct pci_bus *);
>  int __must_check pcibios_enable_device(struct pci_dev *, int mask);
> @@ -709,6 +711,7 @@ static inline struct pci_dev *pci_get_cl
>  { return NULL; }
>  
>  #define pci_dev_present(ids)	(0)
> +#define no_pci_devices()	(1)
>  #define pci_find_present(ids)	(NULL)
>  #define pci_dev_put(dev)	do { } while (0)
>  
Yes that works for me. there's no lockup, nothing unusual in the logs,
and the CD works correctly.

I didn't turn on the lock dependency checks, but I can if you think it
will tell you anything useful.

Cheers
Richard  

Re: [FW ide-cs] Re: jvc cdrom drive lockup

[Andrew Morton]

On Thu, 10 May 2007 14:06:54 +0800
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com> wrote:

> On Sun, 2007-05-06 at 16:00 +0100, Richard Kennedy wrote:
> > On Fri, 2007-05-04 at 23:32 +0900, Komuro wrote:
> > > On Thu, 03 May 2007 15:29:19 +0100
> > > Richard Kennedy <richard@rsk.demon.co.uk> wrote:
> > > 
> > > 
> > > IDE bugs should be posted to the linux-ide mailing list.
> > > 
> > > 
> > > > Hi all, 
> > > > I have a JVC MP-CDX1 cdrom drive that came with my laptop which used to
> > > > work with ide-cs but stopped working with newer kernels.
> > > > 
> > > > I added its ident to ide-cs.c (see patch below) and the drive now is
> > > > detected and gets mounted when plugged in and seems to work correctly.
> > > > 
> > > > But when I eject the card, pccardctl eject 0, the laptop locks up
> > > > completely, there are no messages in the log, and the fan goes to full
> > > > speed so I guess the cpu is running at 100%.
> > > > Any ideas what's going wrong or how to debug it ? 
> > > > Is there anything else I need to patch to get this working ?
> > > > 
> > > > Thanks
> > > > Richard
> > > > 
> > > > card info :- 
> > > > 
> > > > May  3 11:22:52 mininote kernel: pccard: PCMCIA card inserted into slot 0
> > > > May  3 11:22:52 mininote kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
> > > > May  3 11:22:52 mininote kernel: pcmcia: registering new device pcmcia0.0
> > > > May  3 11:22:53 mininote kernel: hdc: UJDB130, ATAPI CD/DVD-ROM drive
> > > > May  3 11:22:53 mininote kernel: ide1 at 0x190-0x197,0x396 on irq 3
> > > > May  3 11:22:53 mininote kernel: ide-cs: hdc: Vpp = 0.0
> > > > May  3 11:22:54 mininote kernel: hdc: ATAPI 20X CD-ROM drive, 128kB Cache
> > > > May  3 11:22:54 mininote kernel: Uniform CD-ROM driver Revision: 3.20
> > > > May  3 11:23:04 mininote hald: mounted /dev/hdc on behalf of uid 500
> > > > May  3 11:23:34 mininote hald: unmounted /dev/hdc from '/media/FC_4 i386 ftp #1' on behalf of uid 500
> > > > May  3 11:24:17 mininote kernel: pccard: card ejected from slot 0
> > > > << lockup happened here >>
> 
> > I rebuilt the kernel with the lock dependency checking turned on, which
> > shows up 2 problems (and also breaks the deadlock).
> > 
> > kernel: pccard: card ejected from slot 0
> > kernel: 
> 
> > kernel: BUG: sleeping function called from invalid context at kernel/rwsem.c:20
> > kernel: in_atomic():0, irqs_disabled():1
> > kernel: INFO: lockdep is turned off.
> > kernel: irq event stamp: 2258
> > kernel: hardirqs last  enabled at (2257): [<c0462050>] kfree+0x78/0x7f
> > kernel: hardirqs last disabled at (2258): [<c0600db5>] _spin_lock_irq+0xc/0x3a
> > kernel: softirqs last  enabled at (2252): [<c0406b41>] do_softirq+0x4d/0xb6
> > kernel: softirqs last disabled at (2243): [<c0406b41>] do_softirq+0x4d/0xb6
> > kernel:  [<c042fda6>] down_read+0x15/0x4d
> > kernel:  [<c04e2498>] pci_get_subsys+0x68/0xea
> > kernel:  [<c04e2530>] pci_get_device+0x16/0x19
> > kernel:  [<c054b6f6>] init_hwif_default+0x28/0xf0
> > kernel:  [<c054c3d5>] ide_unregister+0x242/0x573
> > kernel:  [<d7b68018>] ide_release+0x18/0x28 [ide_cs]
> > kernel:  [<d7b68030>] ide_detach+0x8/0x14 [ide_cs]
> > kernel:  [<c055cd0c>] pcmcia_device_remove+0x50/0xb5
> > kernel:  [<c0543c50>] __device_release_driver+0x71/0x8e
> > kernel:  [<c05440a5>] device_release_driver+0x31/0x46
> > kernel:  [<c0543678>] bus_remove_device+0x70/0x80
> > kernel:  [<c0541d87>] device_del+0x162/0x1c6
> > kernel:  [<c0541df3>] device_unregister+0x8/0x10
> > kernel:  [<c055c95c>] pcmcia_card_remove+0x58/0x77
> > kernel:  [<c055d4da>] ds_event+0x56/0x87
> > kernel:  [<c04d5181>] kobject_get+0xf/0x13
> > kernel:  [<c05590e2>] send_event+0x31/0x49
> > kernel:  [<c05592c1>] socket_shutdown+0xc/0xb3
> > kernel:  [<c0559384>] socket_remove+0x1c/0x26
> > kernel:  [<c05593cd>] pcmcia_eject_card+0x3f/0x4c
> > kernel:  [<c055bcfc>] pccard_store_eject+0x1b/0x22
> > kernel:  [<c055bce1>] pccard_store_eject+0x0/0x22
> > kernel:  [<c054172b>] dev_attr_store+0x27/0x2c
> > kernel:  [<c049b74b>] sysfs_write_file+0xbf/0xe8
> > kernel:  [<c049b68c>] sysfs_write_file+0x0/0xe8
> > kernel:  [<c0465ef1>] vfs_write+0xa8/0x154
> > kernel:  [<c0466430>] sys_write+0x41/0x67
> > kernel:  [<c0404c1a>] sysenter_past_esp+0x5f/0x99
> > kernel:  =======================
> Before calling init_hwif_default, ide_unregister gets lock ide_lock and disables irq.
> init_hwif_default calls ide_default_io_base which calls pci_get_device and later
> pci_get_subsys tries to apply for semaphore pci_bus_sem and goes to sleep.
> 
> Mostly, pci_get_device should be called when irq is turned on.
> 
> I still don't understand an issue. If you test it on a mobile, mostly, the process won't
> sleep when applying for pci_bus_sem because there is no too many opportunities for 2 processes
> to apply for the semaphore at the same time.
> 
> As just needing know if pci is initiated, ide_default_io_base just needs find if list
> pci_devices is empty.
> 
> Could you try below patch against 2.6.21?
> 
> Signed-off-by: Zhang Yanmin <yanmin.zhang@intel.com>
> 
> ---
> 
> diff -Nraup linux-2.6.21/drivers/pci/probe.c linux-2.6.21_fix/drivers/pci/probe.c
> --- linux-2.6.21/drivers/pci/probe.c	2007-05-10 11:35:06.000000000 +0800
> +++ linux-2.6.21_fix/drivers/pci/probe.c	2007-05-10 13:33:57.000000000 +0800
> @@ -22,6 +22,18 @@ EXPORT_SYMBOL(pci_root_buses);
>  
>  LIST_HEAD(pci_devices);
>  
> +/*
> + * Some device drivers need know if pci is initiated.
> + * Basically, we think pci is not initiated when there
> + * is no device in list of pci_devices.
> + */
> +int no_pci_devices(void)
> +{
> +	return list_empty(&pci_devices);
> +}
> +
> +EXPORT_SYMBOL(no_pci_devices);
> +
>  #ifdef HAVE_PCI_LEGACY
>  /**
>   * pci_create_legacy_files - create legacy I/O port and memory files
> diff -Nraup linux-2.6.21/include/asm-i386/ide.h linux-2.6.21_fix/include/asm-i386/ide.h
> --- linux-2.6.21/include/asm-i386/ide.h	2007-02-05 02:44:54.000000000 +0800
> +++ linux-2.6.21_fix/include/asm-i386/ide.h	2007-05-10 13:15:57.000000000 +0800
> @@ -40,14 +40,13 @@ static __inline__ int ide_default_irq(un
>  
>  static __inline__ unsigned long ide_default_io_base(int index)
>  {
> -	struct pci_dev *pdev;
>  	/*
>  	 *	If PCI is present then it is not safe to poke around
>  	 *	the other legacy IDE ports. Only 0x1f0 and 0x170 are
>  	 *	defined compatibility mode ports for PCI. A user can 
>  	 *	override this using ide= but we must default safe.
>  	 */
> -	if ((pdev = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, NULL)) == NULL) {
> +	if (no_pci_devices()) {
>  		switch(index) {
>  			case 2: return 0x1e8;
>  			case 3: return 0x168;
> @@ -55,7 +54,6 @@ static __inline__ unsigned long ide_defa
>  			case 5: return 0x160;
>  		}
>  	}
> -	pci_dev_put(pdev);
>  	switch (index) {
>  		case 0:	return 0x1f0;
>  		case 1:	return 0x170;
> diff -Nraup linux-2.6.21/include/linux/pci.h linux-2.6.21_fix/include/linux/pci.h
> --- linux-2.6.21/include/linux/pci.h	2007-05-10 11:35:07.000000000 +0800
> +++ linux-2.6.21_fix/include/linux/pci.h	2007-05-10 13:33:43.000000000 +0800
> @@ -424,6 +424,8 @@ extern struct bus_type pci_bus_type;
>   * code, or pci core code. */
>  extern struct list_head pci_root_buses;	/* list of all known PCI buses */
>  extern struct list_head pci_devices;	/* list of all devices */
> +/* Some device drivers need know if pci is initiated */
> +extern int no_pci_devices(void);
>  
>  void pcibios_fixup_bus(struct pci_bus *);
>  int __must_check pcibios_enable_device(struct pci_dev *, int mask);
> @@ -709,6 +711,7 @@ static inline struct pci_dev *pci_get_cl
>  { return NULL; }
>  
>  #define pci_dev_present(ids)	(0)
> +#define no_pci_devices()	(1)
>  #define pci_find_present(ids)	(NULL)
>  #define pci_dev_put(dev)	do { } while (0)
>  

yeah, we already fixed this twice.  Please see the list_empty(&pci_devices)
tests in drivers/pci/search.c, added by the below patch.

I'd suggest that we consolidate that change and yours together.  I'll do
a separate patch for that.


commit 6ae4adf50380d0fc5176a76d98d324f8fa491a8f
Author: Ard van Breemen <ard@telegraafnet.nl>
Date:   Fri Jan 5 16:36:21 2007 -0800

    [PATCH] PCI: prevent down_read when pci_devices is empty
    
    The pci_find_subsys gets called very early by obsolete ide setup parameters.
    This is a bogus call since pci is not initialized yet, so the list is empty.
    But in the mean time, interrupts get enabled by down_read.  This can result in
    a kernel panic when the irq controller gets initialized.
    
    This patch checks if the device list is empty before taking the semaphore, and
    hence will not enable irq's.  Furthermore it will inform that it is called
    while pci_devices is empty as a reminder that the ide code needs to be fixed.
    
    The pci_get_subsys can get called in the same manner, and as such is patched
    in the same manner.
    
    [akpm@osdl.org: cleanups]
    Signed-off-by: Ard van Breemen <ard@telegraafnet.nl>
    Cc: Greg KH <greg@kroah.com>
    Signed-off-by: Andrew Morton <akpm@osdl.org>
    Signed-off-by: Linus Torvalds <torvalds@osdl.org>

diff --git a/drivers/pci/search.c b/drivers/pci/search.c
index 45f2b20..fab381e 100644
--- a/drivers/pci/search.c
+++ b/drivers/pci/search.c
@@ -193,6 +193,18 @@ static struct pci_dev * pci_find_subsys(
 	struct pci_dev *dev;
 
 	WARN_ON(in_interrupt());
+
+	/*
+	 * pci_find_subsys() can be called on the ide_setup() path, super-early
+	 * in boot.  But the down_read() will enable local interrupts, which
+	 * can cause some machines to crash.  So here we detect and flag that
+	 * situation and bail out early.
+	 */
+	if (unlikely(list_empty(&pci_devices))) {
+		printk(KERN_INFO "pci_find_subsys() called while pci_devices "
+				"is still empty\n");
+		return NULL;
+	}
 	down_read(&pci_bus_sem);
 	n = from ? from->global_list.next : pci_devices.next;
 
@@ -259,6 +271,18 @@ pci_get_subsys(unsigned int vendor, unsi
 	struct pci_dev *dev;
 
 	WARN_ON(in_interrupt());
+
+	/*
+	 * pci_get_subsys() can potentially be called by drivers super-early
+	 * in boot.  But the down_read() will enable local interrupts, which
+	 * can cause some machines to crash.  So here we detect and flag that
+	 * situation and bail out early.
+	 */
+	if (unlikely(list_empty(&pci_devices))) {
+		printk(KERN_NOTICE "pci_get_subsys() called while pci_devices "
+				"is still empty\n");
+		return NULL;
+	}
 	down_read(&pci_bus_sem);
 	n = from ? from->global_list.next : pci_devices.next;
 

[SMP BUG] kernel 2.6.21: irqbalance does not work properly

[Komuro]

Hi,

The irqbalance does not work properly with kernel 2.6.21
on DualCore processor(AMD Athlon64 X2)

(The irq is not distributed to two Core
 ,most of the irq is distributed to CPU1)

Kernel 2.6.20 does not have this problem.

The irqbalance version is 1.13-4.fc6.

Any idea to fix this problem?

           CPU0       CPU1       
  0:         85          0   IO-APIC-edge      timer
  1:          0        698   IO-APIC-edge      i8042
  6:          0          5   IO-APIC-edge      floppy
  8:          0          1   IO-APIC-edge      rtc
  9:          0          0   IO-APIC-fasteoi   acpi
 12:          0        114   IO-APIC-edge      i8042
 14:        369       2281   IO-APIC-edge      ide0
 15:          0         24   IO-APIC-edge      ide1
 16:         15      38239   IO-APIC-fasteoi   yenta, pcnet_cs
 17:          0          0   IO-APIC-fasteoi   yenta
NMI:          0          0 
LOC:      50548      50547 
ERR:          0
MIS:      15503


Best Regards
Komuro

[SMP BUG] [clockevents: i386 drivers patch] introduces irqbalance-does-not-work-properly problem

[Komuro]

Hi,


[clockevents: i386 drivers patch] introduces
  irqbalance-does-not-work-properly problem.

 
(The irq is not distributed to two Core
  ,most of the irq is distributed to CPU1)
 

 Mr. Thomas Gleixner,
 any idea to fix this problem?


>e9e2cdb412412326c4827fc78ba27f410d837e6e is first bad commit
>commit e9e2cdb412412326c4827fc78ba27f410d837e6e
>Author: Thomas Gleixner <tglx@linutronix.de>
>Date:   Fri Feb 16 01:28:04 2007 -0800
>
>    [PATCH] clockevents: i386 drivers
>    
>    Add clockevent drivers for i386: lapic (local) and PIT/HPET (global).  Update
>    the timer IRQ to call into the PIT/HPET driver's event handler and the
>    lapic-timer IRQ to call into the lapic clockevent driver.  The assignement of
>    timer functionality is delegated to the core framework code and replaces the
>    compile and runtime evalution in do_timer_interrupt_hook()
>    
>    Use the clockevents broadcast support and implement the lapic_broadcast
>    function for ACPI.
>    
>    No changes to existing functionality.
>    
>    [ kdump fix from Vivek Goyal <vgoyal@in.ibm.com> ]
>    [ fixes based on review feedback from Arjan van de Ven <arjan@infradead.org> ]
>    Cleanups-from: Adrian Bunk <bunk@stusta.de>
>    Build-fixes-from: Andrew Morton <akpm@osdl.org>
>    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>    Signed-off-by: Ingo Molnar <mingo@elte.hu>
>    Cc: john stultz <johnstul@us.ibm.com>
>    Cc: Roman Zippel <zippel@linux-m68k.org>
>    Cc: Andi Kleen <ak@suse.de>
>    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>


Best Regards
Komuro


> Hi,
> 
> The irqbalance does not work properly with kernel 2.6.21
> on DualCore processor(AMD Athlon64 X2)
> 
> (The irq is not distributed to two Core
>  ,most of the irq is distributed to CPU1)
> 
> Kernel 2.6.20 does not have this problem.
> 
> The irqbalance version is 1.13-4.fc6.
> 
> Any idea to fix this problem?
> 
>            CPU0       CPU1       
>   0:         85          0   IO-APIC-edge      timer
>   1:          0        698   IO-APIC-edge      i8042
>   6:          0          5   IO-APIC-edge      floppy
>   8:          0          1   IO-APIC-edge      rtc
>   9:          0          0   IO-APIC-fasteoi   acpi
>  12:          0        114   IO-APIC-edge      i8042
>  14:        369       2281   IO-APIC-edge      ide0
>  15:          0         24   IO-APIC-edge      ide1
>  16:         15      38239   IO-APIC-fasteoi   yenta, pcnet_cs
>  17:          0          0   IO-APIC-fasteoi   yenta
> NMI:          0          0 
> LOC:      50548      50547 
> ERR:          0
> MIS:      15503
> 
> 
> Best Regards
> Komuro

Re: [SMP BUG] [clockevents: i386 drivers patch] introduces irqbalance-does-not-work-properly problem

[Jeff Garzik]

Komuro wrote:
> [clockevents: i386 drivers patch] introduces
>   irqbalance-does-not-work-properly problem.
> 
>  
> (The irq is not distributed to two Core
>   ,most of the irq is distributed to CPU1)
>  
> 
>  Mr. Thomas Gleixner,
>  any idea to fix this problem?

Do you mean userspace irqbalance daemon?

It might need to be modified to work properly with a new and unusual 
event source.

Also, for some irq events, it may be good to send most interrupts to one 
core/CPU.  That enhances caching effects, among other benefits.  Again, 
this is highly dependent on the event source, I'm not saying that is the 
case here.

Regards,

	Jeff

Re: [SMP BUG] [clockevents: i386 drivers patch] introduces irqbalance-does-not-work-properly problem

[Komuro]

On Sat, 19 May 2007 23:03:56 -0400
Jeff Garzik <jeff@garzik.org> wrote:


> Do you mean userspace irqbalance daemon?

Yes. I mean userspace irqbalance daemon.


Best Regards
Komuro

> Komuro wrote:
> > [clockevents: i386 drivers patch] introduces
> >   irqbalance-does-not-work-properly problem.
> > 
> >  
> > (The irq is not distributed to two Core
> >   ,most of the irq is distributed to CPU1)
> >  
> > 
> >  Mr. Thomas Gleixner,
> >  any idea to fix this problem?
> 
> Do you mean userspace irqbalance daemon?
> 
> It might need to be modified to work properly with a new and unusual 
> event source.
> 
> Also, for some irq events, it may be good to send most interrupts to one 
> core/CPU.  That enhances caching effects, among other benefits.  Again, 
> this is highly dependent on the event source, I'm not saying that is the 
> case here.
> 
> Regards,
> 
> 	Jeff
> 
> 

Re: [SMP BUG] [clockevents: i386 drivers patch] introduces irqbalance-does-not-work-properly problem

[Thomas Gleixner]

On Sun, 2007-05-20 at 11:14 +0900, Komuro wrote:
> Hi,
> 
> 
> [clockevents: i386 drivers patch] introduces
>   irqbalance-does-not-work-properly problem.

it disables irq balancing for IRQ0, but this does not affect any other
interrupts. It is almost irrelevant as the PIT/HPET timer interrupt
(irq0) is disabled anyway and the local apic timer is used.

> >            CPU0       CPU1       
> >   0:         85          0   IO-APIC-edge      timer

There is no interrupt happening after bootup, so balancing is not a
problem here.

> Mr. Thomas Gleixner,
>  any idea to fix this problem?

Which problem ?

	tglx

Re: [SMP BUG] [clockevents: i386 drivers patch] introduces irqbalance-does-not-work-properly problem

[Komuro]

On Sun, 20 May 2007 09:09:16 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:


> > Mr. Thomas Gleixner,
> >  any idea to fix this problem?
> 
> Which problem ?

The problem is CPU1 receives 38239 interrupt-16
but CPU0 receives only 15 interrupt-16
CPU0 should receive more interrupts.

           CPU0       CPU1       
  0:         85          0   IO-APIC-edge      timer
  1:          0        698   IO-APIC-edge      i8042
  6:          0          5   IO-APIC-edge      floppy
  8:          0          1   IO-APIC-edge      rtc
  9:          0          0   IO-APIC-fasteoi   acpi
 12:          0        114   IO-APIC-edge      i8042
 14:        369       2281   IO-APIC-edge      ide0
 15:          0         24   IO-APIC-edge      ide1
 16:         15      38239   IO-APIC-fasteoi   yenta, pcnet_cs   <<< problem
 17:          0          0   IO-APIC-fasteoi   yenta
NMI:          0          0 
LOC:      50548      50547 
ERR:          0
MIS:      15503


Best Regards
Komuro

> On Sun, 2007-05-20 at 11:14 +0900, Komuro wrote:
> > Hi,
> > 
> > 
> > [clockevents: i386 drivers patch] introduces
> >   irqbalance-does-not-work-properly problem.
> 
> it disables irq balancing for IRQ0, but this does not affect any other
> interrupts. It is almost irrelevant as the PIT/HPET timer interrupt
> (irq0) is disabled anyway and the local apic timer is used.
> 
> > >            CPU0       CPU1       
> > >   0:         85          0   IO-APIC-edge      timer
> 
> There is no interrupt happening after bootup, so balancing is not a
> problem here.
> 
> > Mr. Thomas Gleixner,
> >  any idea to fix this problem?
> 
> Which problem ?
> 
> 	tglx
> 
> 

Re: [SMP BUG] [clockevents: i386 drivers patch] introduces irqbalance-does-not-work-properly problem

[Thomas Gleixner]

On Sun, 2007-05-20 at 19:48 +0900, Komuro wrote:
> The problem is CPU1 receives 38239 interrupt-16
> but CPU0 receives only 15 interrupt-16
> CPU0 should receive more interrupts.
> 
>            CPU0       CPU1       
>   0:         85          0   IO-APIC-edge      timer
>   1:          0        698   IO-APIC-edge      i8042
>   6:          0          5   IO-APIC-edge      floppy
>   8:          0          1   IO-APIC-edge      rtc
>   9:          0          0   IO-APIC-fasteoi   acpi
>  12:          0        114   IO-APIC-edge      i8042
>  14:        369       2281   IO-APIC-edge      ide0
>  15:          0         24   IO-APIC-edge      ide1
>  16:         15      38239   IO-APIC-fasteoi   yenta, pcnet_cs   <<< problem
>  17:          0          0   IO-APIC-fasteoi   yenta
> NMI:          0          0 
> LOC:      50548      50547 
> ERR:          0
> MIS:      15503

And how exactly is this related to clock events ?

	tglx

Re: [SMP BUG] [clockevents: i386 drivers patch] introduces irqbalance-does-not-work-properly problem

[Komuro]

On Sun, 20 May 2007 15:47:04 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:

> And how exactly is this related to clock events ?

Maybe, side-effects.

I will re-analyze this problem.

Thanks.


Best Regards
Komuro


> On Sun, 2007-05-20 at 19:48 +0900, Komuro wrote:
> > The problem is CPU1 receives 38239 interrupt-16
> > but CPU0 receives only 15 interrupt-16
> > CPU0 should receive more interrupts.
> > 
> >            CPU0       CPU1       
> >   0:         85          0   IO-APIC-edge      timer
> >   1:          0        698   IO-APIC-edge      i8042
> >   6:          0          5   IO-APIC-edge      floppy
> >   8:          0          1   IO-APIC-edge      rtc
> >   9:          0          0   IO-APIC-fasteoi   acpi
> >  12:          0        114   IO-APIC-edge      i8042
> >  14:        369       2281   IO-APIC-edge      ide0
> >  15:          0         24   IO-APIC-edge      ide1
> >  16:         15      38239   IO-APIC-fasteoi   yenta, pcnet_cs   <<< problem
> >  17:          0          0   IO-APIC-fasteoi   yenta
> > NMI:          0          0 
> > LOC:      50548      50547 
> > ERR:          0
> > MIS:      15503
> 
> And how exactly is this related to clock events ?
> 
> 	tglx
> 
>