linux-kernel - Re: Bugs on aspire one A150

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1229191479.13970.6.camel@maxim-laptop>
Date:	Sat, 13 Dec 2008 20:04:39 +0200
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	ath5k-devel@...ts.ath5k.org, alsa-devel@...a-project.org,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: Bugs on aspire one A150

On Sat, 2008-12-13 at 18:42 +0100, Rafael J. Wysocki wrote:
> On Saturday, 13 of December 2008, Maxim Levitsky wrote:
> > On Sat, 2008-12-13 at 14:35 +0100, Rafael J. Wysocki wrote:
> > > On Saturday, 13 of December 2008, Maxim Levitsky wrote:
> > > > 
> > > > So, big thanks for everything.
> > > > 
> > > > Now aspire one linux support is very close to perfect,
> > > > (only problem left is that wireless is limited to 18Mbits/s raw rate,
> > > > but at some point I or developers of ath5k will get to the bottom of
> > > > this)
> > > > 
> > > > I also noticed, that now the SD only card reader is always enabled
> > > > regardless of card been there while booting, and same happens in
> > > > windows, I suspect that this is permanent hardware change, which worries
> > > > me, but this reader works fine otherwise.
> > > > (This is another reason why binary bioses are evil, go and find out why
> > > > it enables it)
> > > > 
> > > > 
> > > > Also forgot to mention that both readers ignore write protect tab on SD
> > > > card, and I will report this to correct mailing list soon.
> > > > Everything else works fine
> > > > 
> > > > please include acpiphp fix in 2.6.28.
> > > 
> > > Which one is this?
> > 
> > 
> > 
> > acpiphp: Identify more removable slots
> >     
> >     According to section 6.3.6 of the ACPI spec, the presence of an _RMV
> >     method that evaluates to 1 is sufficient to indicate that a slot is
> >     removable without needing an eject method. This patch refactors the
> >     ejectable slot detection code a little in order to flag these slots as
> >     ejectable and register them. Acpihp therefore binds to the expresscard
> >     slot on my HP test machine.
> >     
> >     Signed-off-by: Matthew Garrett <mjg@...hat.com>
> > 
> > 
> > this makes acpiphp handle hotplug of (now one, sd reader is somehow
> > always present) card reader.
> 
> This is
> http://git.kernel.org/?p=linux/kernel/git/jbarnes/pci-2.6.git;a=commit;h=db9fe9a7230d65916c9938c4f91c75f9c5e00cb7
> in the PCI tree.
> 
> It's scheduled for 2.6.29 and may be included into 2.6.28 -stable, but please
> remember to notify the stable team as soon as this patch gets merged into the
> mainline.

I will, sure.


Just to note, that I might not need that patch as I told that now one of
readers is permanently enabled, I don't know why but this seems to be
hardware failure.

I disconnected power/battery, no cards are in slots, and yet on boot
there is a sd reader in lspci.
Same happens in windows.
It could happen due to suspend/resume, If I remember correctly I put
card once in slot, and then for whole week system wasn't rebooted, but
instead went through suspend/resume cycles.

One thing for sure, nobody will fix this (I mean no point to call acer
support, this is too minor problem)


What I worry about is that second one could show same behavier.
I like this hotplug, as it allows me to test pci hotplug code for real.
Besides, this isn't done without purpose, device might draw less power
this way.


Best regards,
	Maxim Levitsky


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/