Date: Sat, 14 Feb 2004 21:49:19 +0100 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: =?iso-8859-1?Q?S=F8ren?= Schmidt <sos@DeepCore.dk> Cc: sos@FreeBSD.ORG Subject: Re: Sony V505BX ATA panic Message-ID: <20040214204918.GF888@arthur.nitro.dk> In-Reply-To: <402E874D.8080909@DeepCore.dk> References: <20040214192736.C23696@news1.macomnet.ru> <20040214203557.GE888@arthur.nitro.dk> <402E874D.8080909@DeepCore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
--R6sEYoIZpp9JErk7 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.02.14 21:38:37 +0100, S=F8ren Schmidt wrote: > Simon L. Nielsen wrote: > >On 2004.02.14 20:24:51 +0300, Maxim Konovalov wrote: > > > >>Hi Soren, > >> > >>It seems the following commit broke my Sony V505BX: > >> > >>%sos 2004/01/30 11:16:08 PST > >>% > >>% FreeBSD src repository > >>% > >>% Modified files: > >>% sys/dev/ata ata-all.c ata-queue.c > >>% Log: > >>% Be more robust in the probe. We dont want to get into a loop with > >>% reinitting when we try to identify devices. If they dont interrupt > >>% on identify we retry once. If this fails we simply ignore that=20 > >>device. > >>% > >>% Revision Changes Path > >>% 1.203 +10 -11 src/sys/dev/ata/ata-all.c > >>% 1.19 +28 -13 src/sys/dev/ata/ata-queue.c > >> > >>It panics right after the message > >> > >>ad0: 57231MB <FUJITSU MHS2060AT> [116280/16/63] at ata0-master UDMA100 > >>ata1-slave: TIMEOUT - ATAPI_IDENTIFY no interrupt > >>ata1-slave: TIMEOUT - ATAPI_IDENTIFY no interrupt > >>acd0: CDRW <UJDA745 DVD/CDRW> at ata1-master UDMA33 > > > > > >This also makes my IBM Thinkpad R40 boot again. >=20 > And it disables the LiteOn workaround... Yes, exactly... (hardware sucks) I mainly wanted to let other poeple with the same hardware know about this workaround. Since this is a real panic, and not a hang, I think this workaround just hides the real problem which might be somewhere else. I hope to have a look what really goes wrong tomorrow. I guess it's time to try firewire debugging. BTW. I haven't told you about the problem before because didn't want to bother you with the problem until I could give you a proper error report. --=20 Simon L. Nielsen FreeBSD Documentation Team --R6sEYoIZpp9JErk7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFALonOh9pcDSc1mlERApxFAJ9FwktSSwxhxcWW+IFrdWCpnzHl6QCfa4k9 Hv8Ty++RhWT8v9Li9Byvufw= =UteF -----END PGP SIGNATURE----- --R6sEYoIZpp9JErk7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040214204918.GF888>