From: Daniele Forsi <dforsi@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: Unable to complete boot with pata_sis
Date: Thu, 7 Aug 2014 23:35:22 +0200 [thread overview]
Message-ID: <CAN_we7P38OjX5dqDV5CuxS32xnnL-xXeu8GaFciwanqMSDGmSg@mail.gmail.com> (raw)
In-Reply-To: <20140730155735.20b6d12c@alan.etchedpixels.co.uk>
2014-07-30 16:57 GMT+02:00 One Thousand Gnomes:
> Somewhere there is a subtle behavioural difference between pata_sis and
> the ancient sis5513 driver. About the only way to find it would be to
> boot both the old and new kernels and log every single access to the disk
> controller to the point of failure (or some short way into booting) in
> both cases somewhere (eg over the network) then compare them.
thank you for your answer, we don't need to use kernel 2.4 because
after blacklisting pata_sis in 3.16.0, sis5513 can be used just fine,
if I don't blacklist pata_sis and I rmmod it after it tried to access
the disk, the controller or the drive are in a state in which sis5513
gives a lot of errors and can't read the disk
what kind of information you need?
I added some printk() to dump the arguments to pci_write_config_*( )
and these are the results for sis3315 in 3.16 which works (values
printed are dev, where and val):
Aug 7 23:00:47 debian2 kernel: [ 1.709953] PCI W byte: c68ed000
where 0xd = 0x10
Aug 7 23:00:47 debian2 kernel: [ 1.709971] PCI W byte: c68ed000
where 0x52 = 0x4<6>[ 1.709984] sis5513 0000:00:00.1: not 100%
native mode: will probe irqs later
Aug 7 23:00:47 debian2 kernel: [ 1.710077] Probing IDE interface ide0...
Aug 7 23:00:47 debian2 kernel: [ 2.695099] hda: host max PIO4
wanted PIO255(auto-tune) selected PIO4
Aug 7 23:00:47 debian2 kernel: [ 2.695167] PCI W byte: c68ed000
where 0x4b = 0x11
Aug 7 23:00:47 debian2 kernel: [ 2.695189] PCI W word: c68ed000
where 0x40 = 0x301<6>[ 2.695402] hda: MWDMA2 mode selected
Aug 7 23:00:47 debian2 kernel: [ 2.695415] PCI W word: c68ed000
where 0x40 = 0x301
Aug 7 23:00:47 debian2 kernel: [ 2.695591] Probing IDE interface ide1...
Aug 7 23:00:47 debian2 kernel: [ 3.264461] sata_promise
0000:00:09.0: version 2.12
Aug 7 23:00:47 debian2 kernel: [ 3.264554] PCI: setting IRQ 10 as
level-triggered
Aug 7 23:00:47 debian2 kernel: [ 3.310072] PCI: setting IRQ 11 as
level-triggered
and these are the values for pata_sis in 3.16 which doesn't work:
Aug 7 23:13:26 debian2 kernel: [ 799.174973] pata_sis 0000:00:00.1:
version 0.5.2
Aug 7 23:13:26 debian2 kernel: [ 799.175325] PCI W byte: c68ed000
where 0xd = 0x80
Aug 7 23:13:26 debian2 kernel: [ 799.180678] PCI W byte: c68ed000
where 0x4b = 0x0
Aug 7 23:13:26 debian2 kernel: [ 799.180699] PCI W byte: c68ed000
where 0x40 = 0x0PCI W byte: c68ed000 where 0x41 = 0x0
Aug 7 23:13:26 debian2 kernel: [ 799.180724] PCI W byte: c68ed000
where 0x4b = 0x0PCI W byte: c68ed000 where 0x42 = 0x0
Aug 7 23:13:26 debian2 kernel: [ 799.180746] PCI W byte: c68ed000
where 0x43 = 0x0PCI W byte: c68ed000 where 0x4b = 0x0
Aug 7 23:13:26 debian2 kernel: [ 799.351890] PCI W byte: c68ed000
where 0x4b = 0x11
Aug 7 23:13:26 debian2 kernel: [ 799.351914] PCI W byte: c68ed000
where 0x40 = 0x1PCI W byte: c68ed000 where 0x41 = 0x3
Aug 7 23:13:26 debian2 kernel: [ 799.372389] sd 3:0:0:0: [sdb] Mode
Sense: 00 3a 00 00
Aug 7 23:13:26 debian2 kernel: [ 799.380402] PCI W byte: c68ed000
where 0x4b = 0x11
Aug 7 23:13:26 debian2 kernel: [ 799.380432] PCI W byte: c68ed000
where 0x44 = 0x0PCI W byte: c68ed000 where 0x45 = 0x0
Aug 7 23:13:26 debian2 kernel: [ 799.380459] PCI W byte: c68ed000
where 0x4b = 0x11PCI W byte: c68ed000 where 0x46 = 0x0
Aug 7 23:13:26 debian2 kernel: [ 799.380483] PCI W byte: c68ed000
where 0x47 = 0x0PCI W byte: c68ed000 where 0x4b = 0x0
Aug 7 23:13:26 debian2 kernel: [ 799.411575] ata4: drained 60 bytes
to clear DRQ
Aug 7 23:13:27 debian2 kernel: [ 799.443446] PCI W byte: c68ed000
where 0x4b = 0x11
Aug 7 23:13:27 debian2 kernel: [ 799.443468] PCI W byte: c68ed000
where 0x40 = 0x0PCI W byte: c68ed000 where 0x41 = 0x0
Aug 7 23:13:27 debian2 kernel: [ 799.443492] PCI W byte: c68ed000
where 0x4b = 0x11PCI W byte: c68ed000 where 0x42 = 0x0
Aug 7 23:13:27 debian2 kernel: [ 799.443513] PCI W byte: c68ed000
where 0x43 = 0x0PCI W byte: c68ed000 where 0x4b = 0x0
Aug 7 23:13:27 debian2 kernel: [ 799.617032] PCI W byte: c68ed000
where 0x4b = 0x11
Aug 7 23:13:27 debian2 kernel: [ 799.617095] PCI W byte: c68ed000
where 0x40 = 0x1PCI W byte: c68ed000 where 0x41 = 0x3
--
Daniele Forsi
next prev parent reply other threads:[~2014-08-07 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 7:45 Unable to complete boot with pata_sis Daniele Forsi
2014-07-30 14:57 ` One Thousand Gnomes
2014-08-07 21:35 ` Daniele Forsi [this message]
2014-09-24 21:07 ` Daniele Forsi
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=CAN_we7P38OjX5dqDV5CuxS32xnnL-xXeu8GaFciwanqMSDGmSg@mail.gmail.com \
--to=dforsi@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.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).