linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Orson <orson.wellies@gmail.com>
To: Show lu <showlu@jmicron.com>
Cc: 'Steven Chen' <stevenchen@jmicron.com>,
	'Jonathan Nieder' <jrnieder@gmail.com>,
	linux-ide@vger.kernel.org, 'Tejun Heo' <tj@kernel.org>,
	'Aries Lee' <arieslee@jmicron.com>
Subject: Re: JMicron Technology JMB362 JMB363 SError: { DevExch } ExpressCard, sometimes fails to boot
Date: Sat, 07 Jan 2012 12:21:55 +0200	[thread overview]
Message-ID: <4F081CC3.90506@gmail.com> (raw)
In-Reply-To: <201112160255.pBG2tqEd003330@jmr105.jmicron.com>

Hi,

Having received the replacement express card (197b:2363) I can confirm 
that the card in question appears to have been faulty.

The new express card performs flawlessly, I can cold boot / warm boot to 
Linux or windows without receiving any error message, and after several 
days of testing external disks I can honestly say that everything went 
without a hitch.

So, I would be happy if the bug report was closed with reason being due 
to faulty hardware.

regards

Orson

On 16/12/11 04:55, Show lu wrote:
> Dear Sirs,
> Good day,
> I am JMicron/Show and take over JMB36X FAE activity
> Please help to shows the PCIE CFG registers(of JMB36X) at first.
>
>
> Thanks
> Sincerely
> Show
>
>
>
> -----Original Message-----
> From: Steven Chen [mailto:stevenchen@jmicron.com]
> Sent: Friday, December 16, 2011 10:52 AM
> To: 'Jonathan Nieder'; linux-ide@vger.kernel.org; 'Show lu'
> Cc: 'Tejun Heo'; 'Orson'; 'Aries Lee'
> Subject: RE: JMicron Technology JMB362 JMB363 SError: { DevExch }
> ExpressCard, sometimes fails to boot
>
> Add Show in this mail loop.
>
> -----Original Message-----
> From: Jonathan Nieder [mailto:jrnieder@gmail.com]
> Sent: Wednesday, December 14, 2011 6:45 AM
> To: linux-ide@vger.kernel.org
> Cc: 'Tejun Heo'; 'Orson'; Aries Lee
> Subject: Re: JMicron Technology JMB362 JMB363 SError: { DevExch }
> ExpressCard, sometimes fails to boot
>
> (Aries: sorry for the duplicate message)
> Hi,
>
> Aries Lee wrote:
>
>> Is it possible to install windows OS on the same hardware,
>> If it still get the same error, that we can conclude it as a hardware
> issue.
>
> Orson wrote:
>
>> I installed WinXP SP3 as a dual boot option onto my HP NX6325.
>> I booted into windows and my dual port express card was found immediately,
> I
>> installed the latest driver from J Micron and everything seemed to be OK.
>> I looked through the winxp system messages and all was OK, I looked
> through
>> device manager and it said everything was OK, all resources were OK.
>> I attached an external esata drive and it was detected instantly and was
>> available in my list of drives, I copied some files over, all went OK, I
> ran
>> scandisk to check the drive and all went OK, the drive did not seem to
>> re-attach itself or give any errors.  So it seems to work fine in windows.
> All right; looks like the hardware works.
>
>> I then shut down my laptop and removed the esata drive and booted into
> Debian
>> wheezy, same error appeared during boot (without any drive attached)
>> irq_stat 0x00000040, connection status changed
>> ata1: SError: { PHYInt CommWake DevExch }
>> ata1: hard resetting link
>> ata1: COMRESET failed (errno=-32)
>> ata1: reset failed (errno=-32), retrying in 8 secs
>> ata1: limiting SATA link speed to 1.5 Gbps
>> ata1: hard resetting link
>> ata1: SATA link down (SStatus 0 SControl 310)
>> ata1: EH complete
>>
>> etc, etc.
> Right.
>
>> I booted back to windows and all was OK, but, here is what I have found,
> if I
>> boot into Linux from windows without shutting down (warm boot) then the
>> express card is initialised in Debian without problems and works as
> normal, if
>> I shut down and cold boot straight to Debian, the error appears again.
> Interesting.  So it sounds like Windows is doing some initialization
> that Linux does not.
>
>> Perhaps the card is faulty or (I suspect) there is a problem with the bios
> on
>> the NX6325, the latest bios is dated 2007 and HP seem to have stopped
>> supporting this model, even though mine was purchased new in 2007.
> Please send "acpidump" output as an attachment for reference.
>
>> Anyway, because the express card is so cheap I have just ordered a
> replacement
>> of the same type, so this will tell me if it's the card that is at fault.
> Ok.  Thanks for your work.
>
> linux-ide folks: any ideas for debugging this further?  For example,
> is there a way to find the difference between the state after a cold
> boot and a warm boot from windows?
>
> Ciao,
> Jonathan
>

  parent reply	other threads:[~2012-01-07 10:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 15:02 JMicron Technology JMB362 JMB363 SError: { DevExch } ExpressCard, sometimes fails to boot Orson
2011-10-30 21:12 ` Tejun Heo
2011-10-31  2:59   ` Aries Lee
2011-12-13 22:44     ` Jonathan Nieder
2011-12-16  2:52       ` Steven Chen
2011-12-16  2:55         ` Show lu
2011-12-16  9:58           ` Jonathan Nieder
2012-01-07 10:21           ` Orson [this message]
2012-01-09  6:37             ` Show lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F081CC3.90506@gmail.com \
    --to=orson.wellies@gmail.com \
    --cc=arieslee@jmicron.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=showlu@jmicron.com \
    --cc=stevenchen@jmicron.com \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).