[solution exits] no PCMCIA in 4.0-rc3
On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote: > On Sat, 28 Feb 2015 00:08:52 +0100 > Pavel Machek wrote: > > > Hi! > > > > It seems that pcmcia was unhappy even before, but eject definitely > > oopsed it. > > > > Any ideas? > > Probably a PCMCIA not a block layer change - well I guess could be > either. I fixed a pile of PCMCIA bugs and also reworked the allocator for > pure PCI boxes so it didn't do various bad things. > > Can you tweak drivers/pcmcia/Kconfig for config YENTA and make > > select PCCARD_PCI if PCMCIA !=n && !ISA > > instead do > > select PCCARD_NONSTATIC if PCMCIA !=n && !ISA > > rebuild and re-test If I do that, it breaks compile. If I do that, and delete "config PCCARD_PCI", it fixes PCMCIA. Thanks! > The tracel looks like a block layer bug, but it would be nice to know if > its one that PCMCIA used it hide, or its in fact potentially something > else. Yeah the trace was from 3.18. 4.0 is ok with this regard. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
4.0-rc2+: PATA CF card not detected in PCMCIA slot
Hi! > It seems that pcmcia was unhappy even before, but eject definitely > oopsed it. Aha, I was confused; the oops is with 3.18, not with 4.0. For 4.0, pcmcia does not work at all: [ 617.062718] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 [ 622.840108] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 pavel@duo:~$ zcat /proc/config.gz | grep PATA_PCMCIA CONFIG_PATA_PCMCIA=y Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: 4.0-rc1: Oops on eject of CF card in PCMCIA slot
On Mon 2015-03-09 21:57:01, Pavel Machek wrote: > Hi! > > On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote: > > On Sat, 28 Feb 2015 00:08:52 +0100 > > Pavel Machek wrote: > > > > > Hi! > > > > > > It seems that pcmcia was unhappy even before, but eject definitely > > > oopsed it. > > I meant "the dmesg indicated 'interesting stuff'". > > > > Any ideas? > > > > Probably a PCMCIA not a block layer change - well I guess could be > > either. I fixed a pile of PCMCIA bugs and also reworked the allocator for > > pure PCI boxes so it didn't do various bad things. > > Unfortunately, it happened just once :-(. I'll scream if it happens > again. I tried to reproduce it on 4.0, and failed. Now I got this on 3.18+something... Message from syslogd@duo at Mar 9 22:09:24 ... kernel:CPU: 1 PID: 15120 Comm: umount Tainted: GW 3.18.0+ #407 Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011 Message from syslogd@duo at Mar 9 22:09:24 ... kernel:task: ed988580 ti: c23b6000 task.ti: c23b6000 Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Stack: Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Call Trace: Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Code: 98 54 a5 c4 68 78 06 bb c4 89 4d ec e8 92 a6 01 00 83 c4 10 8b 4d ec e9 ec fe ff ff 8d b4 26 00 00 00 00 85 c0 74 1a 55 89 e5 53 40 20 01 89 c3 74 20 8d 43 1c f0 83 6b 1c 01 74 06 8b 5d fc Message from syslogd@duo at Mar 9 22:09:24 ... kernel:EIP: [] kobject_put+0x8/0x50 SS:ESP 0068:c23b7d64 -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - End forwarded message - -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: 4.0-rc1: Oops on eject of CF card in PCMCIA slot
On Mon 2015-03-09 21:57:01, Pavel Machek wrote: > Hi! > > On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote: > > On Sat, 28 Feb 2015 00:08:52 +0100 > > Pavel Machek wrote: > > > > > Hi! > > > > > > It seems that pcmcia was unhappy even before, but eject definitely > > > oopsed it. > > I meant "the dmesg indicated 'interesting stuff'". > > > > Any ideas? > > > > Probably a PCMCIA not a block layer change - well I guess could be > > either. I fixed a pile of PCMCIA bugs and also reworked the allocator for > > pure PCI boxes so it didn't do various bad things. > > Unfortunately, it happened just once :-(. I'll scream if it happens > again. I tried to reproduce it on 4.0, and failed. Now I got this on 3.18+something... Message from syslogd@duo at Mar 9 22:09:24 ... kernel:CPU: 1 PID: 15120 Comm: umount Tainted: GW 3.18.0+ #407 Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011 Message from syslogd@duo at Mar 9 22:09:24 ... kernel:task: ed988580 ti: c23b6000 task.ti: c23b6000 Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Stack: Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Call Trace: Message from syslogd@duo at Mar 9 22:09:24 ... kernel:Code: 98 54 a5 c4 68 78 06 bb c4 89 4d ec e8 92 a6 01 00 83 c4 10 8b 4d ec e9 ec fe ff ff 8d b4 26 00 00 00 00 85 c0 74 1a 55 89 e5 53 40 20 01 89 c3 74 20 8d 43 1c f0 83 6b 1c 01 74 06 8b 5d fc Message from syslogd@duo at Mar 9 22:09:24 ... kernel:EIP: [] kobject_put+0x8/0x50 SS:ESP 0068:c23b7d64 -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html delme.gz Description: application/gzip ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: 4.0-rc1: Oops on eject of CF card in PCMCIA slot
Hi! On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote: > On Sat, 28 Feb 2015 00:08:52 +0100 > Pavel Machek wrote: > > > Hi! > > > > It seems that pcmcia was unhappy even before, but eject definitely > > oopsed it. I meant "the dmesg indicated 'interesting stuff'". > > Any ideas? > > Probably a PCMCIA not a block layer change - well I guess could be > either. I fixed a pile of PCMCIA bugs and also reworked the allocator for > pure PCI boxes so it didn't do various bad things. Unfortunately, it happened just once :-(. I'll scream if it happens again. > Do you have any other I/O port based PCMCIA device you can insert/eject > in that machine ? I should have cf bluetooth somewhere, but I doubt I can find it... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
4.0-rc1: Oops on eject of CF card in PCMCIA slot
Hi! It seems that pcmcia was unhappy even before, but eject definitely oopsed it. Any ideas? Pavel [ 3562.355010] pci_bus :15: Allocating resources [ 3562.355054] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment [ 3562.355060] pci :00:1f.0: BAR 7: [io 0x1000-0x107f] has bogus alignment [ 3562.355066] yenta_cardbus :15:00.0: CardBus bridge to [bus 16-17] [ 3562.355070] yenta_cardbus :15:00.0: bridge window [io 0x9000-0x90ff] [ 3562.355079] yenta_cardbus :15:00.0: bridge window [io 0x9400-0x94ff] [ 3562.355088] yenta_cardbus :15:00.0: bridge window [mem 0xe000-0xe3ff pref] [ 3562.355097] yenta_cardbus :15:00.0: bridge window [mem 0xc400-0xc7ff] [ 3562.355689] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment [ 3562.355696] pci :00:1f.0: BAR 7: [io 0x1000-0x107f] has bogus alignment [ 3562.355702] yenta_cardbus :15:00.0: CardBus bridge to [bus 16-17] [ 3562.355706] yenta_cardbus :15:00.0: bridge window [io 0x9000-0x90ff] [ 3562.355715] yenta_cardbus :15:00.0: bridge window [io 0x9400-0x94ff] [ 3562.355724] yenta_cardbus :15:00.0: bridge window [mem 0xe000-0xe3ff pref] [ 3562.355733] yenta_cardbus :15:00.0: bridge window [mem 0xc400-0xc7ff] [ 3562.355861] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment [ 3562.355867] pci :00:1f.0: BAR 7: [io 0x1000-0x107f] has bogus alignment [ 3562.355873] yenta_cardbus :15:00.0: CardBus bridge to [bus 16-17] [ 3562.355877] yenta_cardbus :15:00.0: bridge window [io 0x9000-0x90ff] [ 3562.355886] yenta_cardbus :15:00.0: bridge window [io 0x9400-0x94ff] [ 3562.355895] yenta_cardbus :15:00.0: bridge window [mem 0xe000-0xe3ff pref] [ 3562.355905] yenta_cardbus :15:00.0: bridge window [mem 0xc400-0xc7ff] [18217.880077] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 [18217.880093] pcmcia_socket pcmcia_socket0: cs: memory probe 0xe46d-0xe7ff: [18217.883580] excluding 0xe4df4000-0xe5185fff 0xe5fce000-0xe635 0xe6e16000-0xe71a7fff 0xe7ff-0xe8381fff [18217.894812] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 16) [18217.944246] scsi host6: pata_pcmcia [18217.947197] ata7: PATA max PIO0 cmd 0x9100 ctl 0x910e irq 16 [18218.272733] ata7.00: CFA: Transcend, 2N3-0925, max PIO2 [18218.272742] ata7.00: 503808 sectors, multi 0: LBA [18218.280805] ata7.00: configured for PIO0 [18218.281325] scsi 6:0:0:0: Direct-Access ATA Transcend0925 PQ: 0 ANSI: 5 [18218.286091] sd 6:0:0:0: [sdb] 503808 512-byte logical blocks: (257 MB/246 MiB) [18218.286702] sd 6:0:0:0: [sdb] Write Protect is off [18218.286710] sd 6:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [18218.286886] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [18218.294561] sdb: sdb1 [18218.295700] sd 6:0:0:0: Attached scsi generic sg1 type 0 [18218.298445] sd 6:0:0:0: [sdb] Attached SCSI removable disk [18220.110561] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [18340.456042] CE: hpet increased min_delta_ns to 20115 nsec [20992.258625] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 [20992.259674] ata7.00: disabled [20992.303989] sd 6:0:0:0: [sdb] Stopping disk [20992.304465] sd 6:0:0:0: [sdb] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 [20992.321556] BUG: unable to handle kernel paging request at d323a6d8 [20992.321627] IP: [] kobject_put+0x8/0x50 [20992.321670] *pde = 373b2067 *pte = 1323a060 [20992.321704] Oops: [#1] SMP DEBUG_PAGEALLOC [20992.321745] Modules linked in: [20992.321768] CPU: 0 PID: 21669 Comm: umount Not tainted 3.18.0+ #407 [20992.321816] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011 [20992.321877] task: d77d0580 ti: d89ac000 task.ti: d89ac000 [20992.321919] EIP: 0060:[] EFLAGS: 00010286 CPU: 0 [20992.321958] EIP is at kobject_put+0x8/0x50 [20992.321985] EAX: d323a6b8 EBX: c0313800 ECX: d77d0580 EDX: d77d0580 [20992.322032] ESI: d323a6b0 EDI: e6465b00 EBP: d89add68 ESP: d89add64 [20992.322079] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [20992.322118] CR0: 8005003b CR2: d323a6d8 CR3: 15e7f000 CR4: 0710 [20992.322164] Stack: [20992.322172] c0313800 d89add70 c43fdb3f d89add84 c441b536 c0313a0c c0313a04 e6465b00 [20992.322259] d89add98 c43fd7c3 c0313a28 c4b7d370 d92ea420 d89addb8 c427b4fd d5ea0c90 [20992.322350] 0806 0370 c0313a0c d5ea0c14 d89addcc d89addd0 c427b675 0282 [20992.322442] Call Trace: [20992.322463] [] put_device+0xf/0x20 [20992.322498] [] scsi_host_dev_release+0xb6/0xf0 [20992.322540] [] device_release+0x23/0x90 [20992.322574] [] kobject_release+0x7d/0x1d0 [20992.322610] [] kobject_put+0x25/0x50 [20992.322643] [] ? kobject_put+0x25/0x50 [20992.322679] [] put_devic
Re: [PATCH] pcmcia/pxa2xx_sharpsl: retain ops structure on collie
On Fri 2011-08-19 10:19:33, Eric Miao wrote:
> On Thu, Aug 18, 2011 at 7:46 PM, Dmitry Eremin-Solenikov
> wrote:
> > On Sun, Aug 7, 2011 at 3:05 PM, Dmitry Eremin-Solenikov
> > wrote:
> >> The pxa2xx_sharpsl driver part is also used on collie, which (as
> >> a StrongARM board) has different expectations for PCMCIA drivers.
> >> So, on collie place sharpsl_pcmcia_ops in .data section rather than
> >> in __initdata.
> >>
> >> Signed-off-by: Dmitry Eremin-Solenikov
> >> Cc: sta...@kernel.org
> >
> > Any comments on this patch?
> >
> >> diff --git a/drivers/pcmcia/pxa2xx_sharpsl.c
> >> b/drivers/pcmcia/pxa2xx_sharpsl.c
> >> index 69ae2fd..f2405dc 100644
> >> --- a/drivers/pcmcia/pxa2xx_sharpsl.c
> >> +++ b/drivers/pcmcia/pxa2xx_sharpsl.c
> >> @@ -219,7 +219,11 @@ static void sharpsl_pcmcia_socket_suspend(struct
> >> soc_pcmcia_socket *skt)
> >> sharpsl_pcmcia_init_reset(skt);
> >> }
> >>
> >> +#ifdef CONFIG_SA1100_COLLIE
> >> +static struct pcmcia_low_level sharpsl_pcmcia_ops = {
> >> +#else
> >> static struct pcmcia_low_level sharpsl_pcmcia_ops __initdata = {
> >> +#endif
>
> Looks OK, and maybe we can put it even simpler by just removing __initdata.
I'd say so; ifdef to have initdata there is just too ugly. But I
don't think it is stable material...
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
___
Linux PCMCIA reimplementation list
http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: Re: Re: Re: Re: Re: Re: Re: Re: [PATCH 11/18] pcmcia: do not use io_req_t when calling pcmcia_request_io()
Hi! > > Nothing relating to setting CISREG_COR (at least on pcnet_cs) changed, and > serial_cs does not modify CISREG_COR on such pseudo-multifunction devices. > > Would it be possible for you to re-check plain 2.6.35 and 2.6.35 with the > pcmcia patchset availble at > http://userweb.kernel.org/~brodo/pcmcia-2.6.35.diff > ? > > If this works, we know that it's a serial/tty core issue, else it's indeed a > PCMCIA issue. > > Pavel: has the bt / pcmcia issue you were seeing with -rc1 been solved? If > not, could you try out 2.6.35 with this bigdiff as well, please? No, I still have the problem in -rc4. I did a quick test, and 2.6.35+your bigdiff works ok. (did not run make clean, that would be slow) Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
2.6.34-rc6 regression: pcmcia no longer compiles
Hi! -rc5 compiled ok with similar config. Now I get: CHK include/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CALLscripts/checksyscalls.sh CHK include/generated/compile.h CC drivers/pcmcia/pcmcia_ioctl.o drivers/pcmcia/pcmcia_ioctl.c: In function 'ds_open': drivers/pcmcia/pcmcia_ioctl.c:714: error: 'struct ' has no member named 'present' drivers/pcmcia/pcmcia_ioctl.c: In function 'ds_read': drivers/pcmcia/pcmcia_ioctl.c:773: error: 'struct ' has no member named 'dead' drivers/pcmcia/pcmcia_ioctl.c: In function 'ds_ioctl': drivers/pcmcia/pcmcia_ioctl.c:841: error: 'struct ' has no member named 'dead' make[2]: *** [drivers/pcmcia/pcmcia_ioctl.o] Error 1 make[1]: *** [drivers/pcmcia] Error 2 make: *** [drivers] Error 2 -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [git pull] more PCMCIA updates for 2.6.34 (including ioctl deprecation)
On Wed 2010-03-10 22:00:15, Dominik Brodowski wrote: > Hey, > > On Wed, Mar 10, 2010 at 09:45:46PM +0100, Pavel Machek wrote: > > Hi! > > > > > > So you believe that disabling the button in the graphical environment > > > > to allow PCMCIA cards to be removed (such as CF cards) - leaving the > > > > user to merely pull out the CF card, while the FS is mounted, is a > > > > good idea? > > > > > > Do any graphical environments even support the ancient user space > > > pcmcica helper stuff ? I can't find any evidence they do but I realise > > > > Yes; qtopia shipped with zaurus sl-5500 (collie), and very probably > > opie and gpe... > > > > Sharp needed operating system for the handheld, and yes it supported > > all the hw. > > So qtopia still uses the PCMCIA ioctl? Or is it some custom add-on code by > zaurus? I'd very much like to see some more source code, what parts of > the IOCTL it uses etc. pp. Or at least some pointers... Well, Alan asked about "any graphical environments even support the ancient user space pcmcica helper stuff", and yes I believe there are some. I probably have one on ancient collie that's lying somewhere. Not sure about sources, I never used those heavily. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [git pull] more PCMCIA updates for 2.6.34 (including ioctl deprecation)
Hi! > > So you believe that disabling the button in the graphical environment > > to allow PCMCIA cards to be removed (such as CF cards) - leaving the > > user to merely pull out the CF card, while the FS is mounted, is a > > good idea? > > Do any graphical environments even support the ancient user space > pcmcica helper stuff ? I can't find any evidence they do but I realise Yes; qtopia shipped with zaurus sl-5500 (collie), and very probably opie and gpe... Sharp needed operating system for the handheld, and yes it supported all the hw. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [regression] Re: 2.6.26-rc6: pcmcia stopped working
On Wed 2008-06-25 13:01:05, Pavel Machek wrote:
> On Wed 2008-06-25 12:23:47, Pavel Machek wrote:
> > On Mon 2008-06-23 10:30:46, Dominik Brodowski wrote:
> > > On Mon, Jun 23, 2008 at 10:18:11AM +0200, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > > > After s2ram and resume, CF card in PCMCIA-to-CF slot is no longer
> > > > > > detected.
> > > > >
> > > > > might this be related to:
> > > > > http://bugzilla.kernel.org/show_bug.cgi?id=10957 ? There didn't change
> > > > > anything with regard to pcmcia between -rc3 and -rc6...
> > > >
> > > > I'm pretty sure it worked in 2.6.25; I don't know if it worked in
> > > > -rc3, or not.
> > > >
> > > > I don't even see note about card insertion in dmesg, so I figured out
> > > > it is probably pcmcia-core problem (or something deeper).
> > >
> > > Well, even since 2.6.25 not much changed in PCMCIA-land, so...
> >
> > Actually, it is worse. On thinkpad, PCMCIA card is only detected
> > once. If I remove it and reinsert it, it will not be detected, and
> > machine will not reboot.
> >
> > Thinkpad X60.
>
> Hmm, but with -rc8, I actually got some useful info:
>
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> debug: unmapping init memory c099f000..c09ef000
> Write protecting the kernel text: 5320k
> Write protecting the kernel read-only data: 1916k
> Failed to execute /tmp/swsusp-init. Attempting defaults...
> EXT3 FS on sda4, internal journal
> Adding 987988k swap on /dev/sda1. Priority:-1 extents:1 across:987988k
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on sda2, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> pcmcia: Detected deprecated PCMCIA ioctl usage from process: hwclock.
> pcmcia: This interface will soon be removed from the kernel; please expect
> breakage unless you upgrade to new tools.
> pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html
> for details.
> eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
> coda_read_super: Bad mount data
> coda_read_super: device index: 0
> coda_read_super: rootfid is (01234567..08051a38.)
> coda: Unexpected interruption.
> Failure of coda_cnode_make for root: error -4
> pccard: PCMCIA card inserted into slot 0
> cs: memory probe 0x0c-0x0f: excluding 0xc-0xd3fff 0xdc000-0xf
> cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff
> cs: memory probe 0xe000-0xe3ff: excluding 0xe000-0xe3ff
> cs: memory probe 0xe430-0xe7ff: excluding 0xe430-0xe46c
> 0xe4e7-0xe523 0xe5db-0xe617 0xe6cf-0xe70b
> pcmcia: registering new device pcmcia0.0
> Probing IDE interface ide1...
> hdc: SunDisk SDP3B-20, CFA DISK drive
> hdd: SunDisk SDP3B-20, CFA DISK drive
> ide-probe: ignoring undecoded slave
> ide1 at 0x9100-0x9107,0x910e on irq 16
> hdc: max request size: 128KiB
> hdc: 40960 sectors (20 MB) w/1KiB Cache, CHS=640/2/32
> hdc:hdc: set_geometry_intr: status=0x51 { DriveReady SeekComplete Error }
> hdc: set_geometry_intr: error=0x04 { DriveStatusError }
> ide: failed opcode was: unknown
> hdc1 hdc3
> ide-cs: hdc: Vpp = 0.0
> Clocksource tsc unstable (delta = -68835537 ns)
> pccard: card ejected from slot 0
> INFO: task pccardd:1121 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> pccardd D f6dd1e1c 0 1121 2
>f6dd1e30 0086 0002 f6dd1e1c f6dd1e10 c2015e80
> c2015e80
>c09113e0 0286 0286 f72d13b8 f72d1618 c2015e80 f6dd
> f6afedc0
>03a9 f6bcb458 c02bd187 f6dd1e4c 0003
>
> Call Trace:
> [] sysfs_addrm_finish+0x1a7/0x1e0
> [] schedule_timeout+0x7c/0xd0
> [] remove_dir+0x27/0x40
> [] _spin_lock_irq+0x2a/0x40
> [] wait_for_common+0xc0/0x130
> [] default_wake_function+0x0/0x10
> [] ide_unregister+0xcf/0x150
> [] ide_release+0x21/0x40
> [] ide_detach+0x29/0x80
> [] pcmcia_device_remove+0x36/0xe0
> [] __device_release_driver+0x56/0x90
> [] device_release_driver+0x20/0x40
> [] bus_remove_device+0x6b/0x90
> [] device_del+0xcf/0x140
> [] device_unregister+0x8/0x10
> [] pcmcia_card_remove+0x6c/0x80
> [] ds_event+0x64/0xb0
> [] pccardd+0x16f/0x2a0
> [] send_event+0x4b/0x80
> [] socket_shutdown+0xb/0xd0
> [] socket_remove+0x1c/0x30
&
Re: [regression] Re: 2.6.26-rc6: pcmcia stopped working
Hi!
> > > Thinkpad X60.
> >
> > Hmm, but with -rc8, I actually got some useful info:
> >
> > kjournald starting. Commit interval 5 seconds
> > EXT3-fs: mounted filesystem with ordered data mode.
> > VFS: Mounted root (ext3 filesystem) readonly.
> > debug: unmapping init memory c099f000..c09ef000
> > Write protecting the kernel text: 5320k
> > Write protecting the kernel read-only data: 1916k
> > Failed to execute /tmp/swsusp-init. Attempting defaults...
> > EXT3 FS on sda4, internal journal
> > Adding 987988k swap on /dev/sda1. Priority:-1 extents:1 across:987988k
> > kjournald starting. Commit interval 5 seconds
> > EXT3 FS on sda2, internal journal
> > EXT3-fs: mounted filesystem with ordered data mode.
> > pcmcia: Detected deprecated PCMCIA ioctl usage from process: hwclock.
> > pcmcia: This interface will soon be removed from the kernel; please expect
> > breakage unless you upgrade to new tools.
> > pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html
> > for details.
> > eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
> > coda_read_super: Bad mount data
> > coda_read_super: device index: 0
> > coda_read_super: rootfid is (01234567..08051a38.)
> > coda: Unexpected interruption.
> > Failure of coda_cnode_make for root: error -4
> > pccard: PCMCIA card inserted into slot 0
> > cs: memory probe 0x0c-0x0f: excluding 0xc-0xd3fff
> > 0xdc000-0xf
> > cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff
> > cs: memory probe 0xe000-0xe3ff: excluding 0xe000-0xe3ff
> > cs: memory probe 0xe430-0xe7ff: excluding 0xe430-0xe46c
> > 0xe4e7-0xe523 0xe5db-0xe617 0xe6cf-0xe70b
> > pcmcia: registering new device pcmcia0.0
> > Probing IDE interface ide1...
> > hdc: SunDisk SDP3B-20, CFA DISK drive
> > hdd: SunDisk SDP3B-20, CFA DISK drive
> > ide-probe: ignoring undecoded slave
> > ide1 at 0x9100-0x9107,0x910e on irq 16
> > hdc: max request size: 128KiB
> > hdc: 40960 sectors (20 MB) w/1KiB Cache, CHS=640/2/32
> > hdc:hdc: set_geometry_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdc: set_geometry_intr: error=0x04 { DriveStatusError }
> > ide: failed opcode was: unknown
> > hdc1 hdc3
> > ide-cs: hdc: Vpp = 0.0
> > Clocksource tsc unstable (delta = -68835537 ns)
> > pccard: card ejected from slot 0
> > INFO: task pccardd:1121 blocked for more than 120 seconds.
> > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > pccardd D f6dd1e1c 0 1121 2
> >f6dd1e30 0086 0002 f6dd1e1c f6dd1e10 c2015e80
> > c2015e80
> >c09113e0 0286 0286 f72d13b8 f72d1618 c2015e80 f6dd
> > f6afedc0
> >03a9 f6bcb458 c02bd187 f6dd1e4c 0003
> >
> > Call Trace:
> > [] sysfs_addrm_finish+0x1a7/0x1e0
> > [] schedule_timeout+0x7c/0xd0
> > [] remove_dir+0x27/0x40
> > [] _spin_lock_irq+0x2a/0x40
> > [] wait_for_common+0xc0/0x130
> > [] default_wake_function+0x0/0x10
> > [] ide_unregister+0xcf/0x150
> > [] ide_release+0x21/0x40
> > [] ide_detach+0x29/0x80
> > [] pcmcia_device_remove+0x36/0xe0
> > [] __device_release_driver+0x56/0x90
> > [] device_release_driver+0x20/0x40
> > [] bus_remove_device+0x6b/0x90
> > [] device_del+0xcf/0x140
> > [] device_unregister+0x8/0x10
> > [] pcmcia_card_remove+0x6c/0x80
> > [] ds_event+0x64/0xb0
> > [] pccardd+0x16f/0x2a0
> > [] send_event+0x4b/0x80
> > [] socket_shutdown+0xb/0xd0
> > [] socket_remove+0x1c/0x30
> > [] pccardd+0x23e/0x2a0
> > [] default_wake_function+0x0/0x10
> > [] pccardd+0x0/0x2a0
> > [] kthread+0x42/0x70
> > [] kthread+0x0/0x70
> > [] kernel_thread_helper+0x7/0x1c
> > [] device_create_vargs+0x42/0xd0
> > ===
> > no locks held by pccardd/1121.
> > INFO: task pccardd:1121 blocked for more than 120 seconds.
> > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > pccardd D f6dd1e1c 0 1121 2
> >f6dd1e30 0086 0002 f6dd1e1c f6dd1e10 c2015e80
> > c2015e80
> >c09113e0 0286 0286 f72d13b8 f72d1618 c2015e80 f6dd
> > f6afedc0
> >03a9 f6bcb458 c02bd187 f6dd1e4c 0003
> >
> > Call Trace:
> > [] sysfs_addrm_finish+0x1a7/0x1e0
> > [] schedule_timeout+0x7c/0xd0
> > [] remove_dir+0x27/0x40
> > [] _spin_lock_irq+0x2a/0x40
> > [] wait_for_common+0xc0/0x130
> > [] default_wake_function+0x0/0x10
> > [] ide_unregister+0xcf/0x150
> > [] ide_release+0x21/0x40
> > [] ide_detach+0x29/0x80
> > [] pcmcia_device_remove+0x36/0xe0
> > [] __device_release_driver+0x56/0x90
> > [] device_release_driver+0x20/0x40
> > [] bus_remove_device+0x6b/0x90
> > [] device_del+0xcf/0x140
> > [] device_unregister+0x8/0x10
> > [] pcmcia_card_remove+0x6c/0x80
> > [] ds_event+0x64/0xb0
> > [] pccardd+0x16f/0x2a0
> > [] send_event+0x4b/0x80
> > [] socket_shutdown+0xb
Re: [regression] Re: 2.6.26-rc6: pcmcia stopped working
Hi!
> > Hmm, hitting sysrq-w produces no blocked task until I eject pcmcia
> > card. Backtrace there is:
> >
> > Greg, I believe some traces lead to sysfs, can you help here?
>
> ide_unregister() does not complete :-(.
>
> device_unregister(&hwif->gendev);
> + printk("ide_unregister: waiting for rel_comp\n");
> wait_for_completion(&hwif->gendev_rel_comp);
>
> ...that wait_for_completion never returns.
...and this fixes PCMCIA/IDE for me... (Pseudopatch)
Pavel
diff --git a/drivers/ide/ide.c b/drivers/ide/ide.c
--- a/drivers/ide/ide.c
+++ b/drivers/ide/ide.c
@@ -336,29 +341,38 @@ void ide_unregister(ide_hwif_t *hwif)
++irq_count;
g = g->next;
} while (g != hwgroup->hwif);
if (irq_count == 1)
free_irq(hwif->irq, hwgroup);
ide_remove_port_from_hwgroup(hwif);
device_unregister(hwif->portdev);
device_unregister(&hwif->gendev);
- wait_for_completion(&hwif->gendev_rel_comp);
+// wait_for_completion(&hwif->gendev_rel_comp);
+ msleep(1000);
/*
* Remove us from the kernel's knowledge
*/
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
___
Linux PCMCIA reimplementation list
http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [regression] Re: 2.6.26-rc6: pcmcia stopped working
On Wed 2008-06-25 12:23:47, Pavel Machek wrote:
> On Mon 2008-06-23 10:30:46, Dominik Brodowski wrote:
> > On Mon, Jun 23, 2008 at 10:18:11AM +0200, Pavel Machek wrote:
> > > Hi!
> > >
> > > > > After s2ram and resume, CF card in PCMCIA-to-CF slot is no longer
> > > > > detected.
> > > >
> > > > might this be related to:
> > > > http://bugzilla.kernel.org/show_bug.cgi?id=10957 ? There didn't change
> > > > anything with regard to pcmcia between -rc3 and -rc6...
> > >
> > > I'm pretty sure it worked in 2.6.25; I don't know if it worked in
> > > -rc3, or not.
> > >
> > > I don't even see note about card insertion in dmesg, so I figured out
> > > it is probably pcmcia-core problem (or something deeper).
> >
> > Well, even since 2.6.25 not much changed in PCMCIA-land, so...
>
> Actually, it is worse. On thinkpad, PCMCIA card is only detected
> once. If I remove it and reinsert it, it will not be detected, and
> machine will not reboot.
>
> Thinkpad X60.
Hmm, but with -rc8, I actually got some useful info:
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
debug: unmapping init memory c099f000..c09ef000
Write protecting the kernel text: 5320k
Write protecting the kernel read-only data: 1916k
Failed to execute /tmp/swsusp-init. Attempting defaults...
EXT3 FS on sda4, internal journal
Adding 987988k swap on /dev/sda1. Priority:-1 extents:1 across:987988k
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
pcmcia: Detected deprecated PCMCIA ioctl usage from process: hwclock.
pcmcia: This interface will soon be removed from the kernel; please expect
breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
details.
eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
coda_read_super: Bad mount data
coda_read_super: device index: 0
coda_read_super: rootfid is (01234567..08051a38.)
coda: Unexpected interruption.
Failure of coda_cnode_make for root: error -4
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0x0c-0x0f: excluding 0xc-0xd3fff 0xdc000-0xf
cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff
cs: memory probe 0xe000-0xe3ff: excluding 0xe000-0xe3ff
cs: memory probe 0xe430-0xe7ff: excluding 0xe430-0xe46c
0xe4e7-0xe523 0xe5db-0xe617 0xe6cf-0xe70b
pcmcia: registering new device pcmcia0.0
Probing IDE interface ide1...
hdc: SunDisk SDP3B-20, CFA DISK drive
hdd: SunDisk SDP3B-20, CFA DISK drive
ide-probe: ignoring undecoded slave
ide1 at 0x9100-0x9107,0x910e on irq 16
hdc: max request size: 128KiB
hdc: 40960 sectors (20 MB) w/1KiB Cache, CHS=640/2/32
hdc:hdc: set_geometry_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: set_geometry_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
hdc1 hdc3
ide-cs: hdc: Vpp = 0.0
Clocksource tsc unstable (delta = -68835537 ns)
pccard: card ejected from slot 0
INFO: task pccardd:1121 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
pccardd D f6dd1e1c 0 1121 2
f6dd1e30 0086 0002 f6dd1e1c f6dd1e10 c2015e80 c2015e80
c09113e0 0286 0286 f72d13b8 f72d1618 c2015e80 f6dd f6afedc0
03a9 f6bcb458 c02bd187 f6dd1e4c 0003
Call Trace:
[] sysfs_addrm_finish+0x1a7/0x1e0
[] schedule_timeout+0x7c/0xd0
[] remove_dir+0x27/0x40
[] _spin_lock_irq+0x2a/0x40
[] wait_for_common+0xc0/0x130
[] default_wake_function+0x0/0x10
[] ide_unregister+0xcf/0x150
[] ide_release+0x21/0x40
[] ide_detach+0x29/0x80
[] pcmcia_device_remove+0x36/0xe0
[] __device_release_driver+0x56/0x90
[] device_release_driver+0x20/0x40
[] bus_remove_device+0x6b/0x90
[] device_del+0xcf/0x140
[] device_unregister+0x8/0x10
[] pcmcia_card_remove+0x6c/0x80
[] ds_event+0x64/0xb0
[] pccardd+0x16f/0x2a0
[] send_event+0x4b/0x80
[] socket_shutdown+0xb/0xd0
[] socket_remove+0x1c/0x30
[] pccardd+0x23e/0x2a0
[] default_wake_function+0x0/0x10
[] pccardd+0x0/0x2a0
[] kthread+0x42/0x70
[] kthread+0x0/0x70
[] kernel_thread_helper+0x7/0x1c
[] device_create_vargs+0x42/0xd0
===
no locks held by pccardd/1121.
INFO: task pccardd:1121 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
pccardd D f6dd1e1c 0 1121 2
f6dd1e30 0086 0002 f6dd1e1c f6dd1e10 c2015e80 c2015e80
c09113e0 0286 0286 f72d13b8 f72d1618 c201
[regression] Re: 2.6.26-rc6: pcmcia stopped working
On Mon 2008-06-23 10:30:46, Dominik Brodowski wrote: > On Mon, Jun 23, 2008 at 10:18:11AM +0200, Pavel Machek wrote: > > Hi! > > > > > > After s2ram and resume, CF card in PCMCIA-to-CF slot is no longer > > > > detected. > > > > > > might this be related to: > > > http://bugzilla.kernel.org/show_bug.cgi?id=10957 ? There didn't change > > > anything with regard to pcmcia between -rc3 and -rc6... > > > > I'm pretty sure it worked in 2.6.25; I don't know if it worked in > > -rc3, or not. > > > > I don't even see note about card insertion in dmesg, so I figured out > > it is probably pcmcia-core problem (or something deeper). > > Well, even since 2.6.25 not much changed in PCMCIA-land, so... Actually, it is worse. On thinkpad, PCMCIA card is only detected once. If I remove it and reinsert it, it will not be detected, and machine will not reboot. Thinkpad X60. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: 2.6.26-rc6: pcmcia stopped working after resume
Hi! > > After s2ram and resume, CF card in PCMCIA-to-CF slot is no longer > > detected. > > might this be related to: > http://bugzilla.kernel.org/show_bug.cgi?id=10957 ? There didn't change > anything with regard to pcmcia between -rc3 and -rc6... I'm pretty sure it worked in 2.6.25; I don't know if it worked in -rc3, or not. I don't even see note about card insertion in dmesg, so I figured out it is probably pcmcia-core problem (or something deeper). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
2.6.26-rc6: pcmcia stopped working after resume
Hi! After s2ram and resume, CF card in PCMCIA-to-CF slot is no longer detected. Jun 23 00:38:28 amd kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 23 00:38:28 amd kernel: sd 0:0:0:0: [sda] 117210240 512-byte hardware sectors (60012 MB) Jun 23 00:38:28 amd kernel: sd 0:0:0:0: [sda] Write Protect is off Jun 23 00:38:28 amd kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Jun 23 00:38:28 amd kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 23 00:38:28 amd kernel: PM: Writing back config space on device :15:00.2 at offset 4 (was 0, writing e4301800) Jun 23 00:38:28 amd kernel: PM: Writing back config space on device :15:00.2 at offset 3 (was 80, writing 804000) Jun 23 00:38:28 amd kernel: PM: Writing back config space on device :15:00.2 at offset 1 (was 210, writing 216) Jun 23 00:38:28 amd kernel: sleepy: scsi_bus_resume start Jun 23 00:38:28 amd kernel: sleepy: scsi_bus_resume done Jun 23 00:38:28 amd kernel: usb 4-1: reset low speed USB device using uhci_hcd and address 2 Jun 23 00:38:28 amd kernel: PM: Finishing wakeup. Jun 23 00:38:28 amd kernel: Restarting tasks ... done. Jun 23 00:38:28 amd kernel: usb 5-1: USB disconnect, address 2 Jun 23 00:38:28 amd cardmgr[1396]: executing: './ide resume hdc 2>&1' Jun 23 00:38:28 amd cardmgr[1396]: + ./shared: line 127: /var/run/stab: No such file or directory Jun 23 00:38:28 amd cardmgr[1396]: + usage: ./ide [action] [device name] Jun 23 00:38:28 amd cardmgr[1396]: + actions: start check stop suspend resume Jun 23 00:38:28 amd cardmgr[1396]: resume cmd exited with status 1 Jun 23 00:38:28 amd kernel: usb 5-1: new full speed USB device using uhci_hcd and address 4 Jun 23 00:38:28 amd kernel: usb 5-1: configuration #1 chosen from 1 choice Jun 23 00:38:28 amd kernel: usb 5-1: New USB device found, idVendor=0a5c, idProduct=2110 Jun 23 00:38:28 amd kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 23 00:38:28 amd kernel: usb 5-1: Product: BCM2045B Jun 23 00:38:28 amd kernel: usb 5-1: Manufacturer: Broadcom Corp Jun 23 00:38:28 amd kernel: usb 5-2: USB disconnect, address 3 Jun 23 00:38:28 amd kernel: usb 5-2: new full speed USB device using uhci_hcd and address 5 Jun 23 00:38:29 amd kernel: usb 5-2: configuration #1 chosen from 1 choice Jun 23 00:38:29 amd kernel: usb 5-2: New USB device found, idVendor=0483, idProduct=2016 Jun 23 00:38:29 amd kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 23 00:38:29 amd kernel: usb 5-2: Product: Biometric Coprocessor Jun 23 00:38:29 amd kernel: usb 5-2: Manufacturer: STMicroelectronics pccard: card ejected from slot 0 Jun 23 00:38:32 amd kernel: pccard: card ejected from slot 0 I eject it, but nothing happens (and no messages in log) on insertion. I think system will die on next s2ram attempt. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
size of git repository (was Re: [BUG] New Kernel Bugs)
On Tue 2007-11-13 12:50:08, Mark Lord wrote: > Ingo Molnar wrote: > > > >for example git-bisect was godsent. I remember that > >years ago bisection of a bug was a very laborous task > >so that it was only used as a final, last-ditch > >approach for really nasty bugs. Today we can > >autonomouly bisect build bugs via a simple shell > >command around "git-bisect run", without any human > >interaction! This freed up testing resources > .. > > It's only a godsend for the few people who happen to be > kernel developers > and who happen to already use git. > > It's a 540MByte download over a slow link for everyone > else. Hmmm, clean-cg is 7.7G on my machine, and yes I tried git-prune-packed. What am I doing wrong? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [BUG] New Kernel Bugs
Hi! > > Suspend to RAM resume hangs on a tickless (NO_HZ) kernel > > http://bugzilla.kernel.org/show_bug.cgi?id=9275 > > Kernel: 2.6.23 > > This is HP notebook nc6320 T2400 945GM > > No response from developers Maybe I'm optimistic, but I expected Ingo/Thomas to look after nohz problems. nohz=off highres=off fixes more than one suspend problem... ...stuff I've seen with NOHZ even without suspend (cursor blinking irregulary) make me think that nohz perhaps should not be used in production just yet... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [PATCH] PCMCIA: prevent auto insert during resume.
On Fri 2007-10-26 19:18:57, Rodolfo Giometti wrote: > On Fri, Oct 26, 2007 at 06:00:31PM +0100, Russell King wrote: > > > > > > Also if you didn't eject the socket, at resume the device will be > > > > > powered up again, my patch just prevents that a pre-powered off device > > > > > to be turned on at resume time. > > > > > > > > > > However you should consider that some embedded systems have fixed > > > > > PCMCIA devices that can't be removed so there are no reasons to detect > > > > > them after resume, nobody can change them. :) > > > > > > > > > > Also battery powered devices can go very frequently to sleep and the > > > > > current behavior force the user to switch off the unused device each > > > > > time the system resumes from sleep. > > > > > > > > I realise that. I do work on embedded devices, and this behaviour is > > > > explicitly there to support embedded devices. > > > > > > > > I've suggested a workable solution to you which allows both of us to > > > > have the behaviour we both desire from the system. That sounds like > > > > a negotiated solution to me... > > > > > > Do you mean to switch off the socket from userland? It could be a > > > solution but in this case the device is powered on each time even if > > > for a short delay... > > > > If it's a permanent device, and you've powered it down via pccardctl, > > then you've powered it down from userland. So record that it's been > > powered down from userland. Then, on resume, if it's been powered down > > from userland, don't try to re-power it on resume. > > But the userland doesn't re-power it on resume... it's the kernel > itself whos re-powers the device on resume. So the userland can only > power down the device again. I think Russell means: at a flag into kernel. If user powers down the device, set the flag. If flag is set during resume, avoid powering up the device. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [PATCH 1/2] PM: Remove deprecated sysfs files
On Thu 2007-07-12 16:55:07, Alan Stern wrote: > This patch (as932) removes the deprecated sysfs .../power/state > attribute files. > > Signed-off-by: Alan Stern <[EMAIL PROTECTED]> ACK (FWIW) and thanks. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: pcmcia ioctl removal
Hi! > > pcmcia-delete-obsolete-pcmcia_ioctl-feature.patch > > ... > > > Dominik is busy. Will probably re-review and send these direct to Linus. > > The patch above is the removal of cardmgr support. While I'd love to > see this cruft gone it definitively needs maintainer judgement on whether > they time has come that no one relies on cardmgr anymore. I remember needing cardmgr few months ago on sa-1100 arm system. I'm not sure this is obsolete-enough to kill. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
