Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jul 2004 17:11:32 -0400
From:      "Dan Langille" <dan@langille.org>
To:        Bruce M Simpson <bms@spc.org>
Cc:        freebsd-mobile@freebsd.org
Subject:   Re: How's current lately for laptops? (was Two questions on Thinkpad T41)
Message-ID:  <40F6BAC4.15798.CDE62A7@localhost>
In-Reply-To: <20040709013152.GR15368@empiric.dek.spc.org>
References:  <40EDB001.4311.E98BBCCC@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
On 9 Jul 2004 at 2:31, Bruce M Simpson wrote:

> On Thu, Jul 08, 2004 at 08:35:13PM -0400, Dan Langille wrote:
> > Bruce: I think this answers my question.  My ThinkPad T41 is now in 
> > the shop getting a new system board (I hope).  When it returns, I was 
> > considering running -CURRENT on it rather than 5.2.1-RELEASE.  Your 
> > experience above has encouraged me to try it.  I'll cvsup to the 
> > above date and let you know how it goes.... when I get it back.
> 
> You also said on IRC:
> > [John Baldwin had a look at it at USENIX, and he figured it
> >  was a cable or controller problem, which means the system board]
> 
> If we can establish that the problem is isolated to a specific ATA
> controller revision, we may be getting somewhere....
> 
> My T40, which does not demonstrate any of these problems, has the following:
> atapci0@pci0:31:1:      class=0x01018a card=0x052d1014 chip=0x24ca8086
> rev=0x01 hdr=0x00
> 
> A locally affected T41 has the following:
> atapci0@pci0:31:1:      class=0x01018a card=0x052d1014 chip=0x24ca8086
> rev=0x01 hdr=0x00
> 
> ...which are again, identical.
> 
> Your T41 is... off to the shop for a motherboard replacement.

My T41 is back, with a new motherboard installed.

atapci0@pci0:31:1:      class=0x01018a card=0x052d1014 
chip=0x24ca8086 rev=0x01 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801DBM (ICH4-M) UltraATA/100 EIDE Controller'
    class    = mass storage
    subclass = ATA

My T41 boot OK with 

> What I'd like to do next is for people with affected machines to run
> acpidump, extract their DSDT, and then run md5 to at least establish
> if they're different; and following on from THAT, to run iasl and diff
> for possibly differing ACPI methods with regards to the CD-RW module.

Would it be useful to see a non-affected machine?  Here's mine:

[root@laptop:~] # acpidump -d > ~/acpidump.DSDT
[root@laptop:~] # md5 ~/acpidump.DSDT
MD5 (/root/acpidump.DSDT) = a1db426b9d8061620e7bb0bf287896b4
[root@laptop:~] #
-- 
Dan Langille : http://www.langille.org/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40F6BAC4.15798.CDE62A7>