From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: whiteheadm@acm.org
Cc: Tejun Heo <tj@kernel.org>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_legacy: Allow disabling of legacy PATA device probes on non-PCI systems
Date: Mon, 12 Dec 2016 13:21:56 +0100 [thread overview]
Message-ID: <2575141.gMpqs59WaB@amdc3058> (raw)
In-Reply-To: <CAP8WD_bUW9cAAQpvenL73sxvpoxNYwZdRqpj92YWEyanK51+0g@mail.gmail.com>
Hi,
On Monday, December 05, 2016 09:19:35 AM tedheadster wrote:
> Tejun,
> that new patch worked better.
>
> Here is the dmesg output:
>
> [ 34.347350] scsi0 : pata_legacy
> [ 34.367366] ata1: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14
> [ 34.523330] ata1.00: ATA-4: QUANTUM FIREBALL CR8.4A, A5U.1200, max UDMA/66
> [ 34.524804] ata1.00: 16514064 sectors, multi 0: LBA
> [ 34.525747] ata1.00: configured for PIO
> [ 34.569330] scsi 0:0:0:0: Direct-Access ATA QUANTUM
> FIREBALL A5U. PQ: 0 ANSI: 5
> [ 34.655313] sd 0:0:0:0: [sda] 16514064 512-byte logical blocks:
> (8.45 GB/7.87 GiB)
> [ 34.674309] sd 0:0:0:0: [sda] Write Protect is off
> [ 34.675683] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 34.689347] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 34.691283] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [ 34.800293] sda: sda1 sda2 sda3 sda4
> [ 34.890325] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 34.976270] scsi1 : pata_legacy
> [ 34.999263] ata2: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
> [ 35.448191] scsi2 : pata_legacy
> [ 35.486192] ata3: PATA max PIO4 cmd 0x1e8 ctl 0x3ee irq 11
> [ 35.997114] scsi3 : pata_legacy
> [ 36.051103] ata4: PATA max PIO4 cmd 0x168 ctl 0x36e irq 10
> [ 36.384057] genirq: Flags mismatch irq 8. 00000000 (platform) vs.
> 00000000 (rtc0)
> [ 36.571024] scsi4 : pata_legacy
> [ 36.626014] ata5: PATA max PIO4 cmd 0x160 ctl 0x366 irq 12
> [ 42.143223] EXT4-fs (sda4): mounting ext3 file system using the
> ext4 subsystem
>
> and /proc/interrupts looks good:
>
> CPU0
> 0: 558552 XT-PIC-XT-PIC timer
> 1: 337 XT-PIC-XT-PIC i8042
> 2: 0 XT-PIC-XT-PIC cascade
> 4: 1 XT-PIC-XT-PIC
> 8: 0 XT-PIC-XT-PIC rtc0
> 14: 51538 XT-PIC-XT-PIC platform
Thank you for testing.
Tejun, is this information sufficient to fix the issue or do you still
want Matthew to test your last debug patch?
[ http://marc.info/?l=linux-ide&m=148096582017930&w=2 ]
> I would still like to get my patch in. If you have a motherboard where
> you cannot disable the secondary hard drive controllers, the
> pata_legacy driver will detect them and allocate the interrupt. Some
If there are no devices attached to the controller, the driver will
free the resources so I don't quite get what would be the issue here.
Could you please explain it more?
> way to disable this behavior is useful.
>
> - Matthew
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2016-12-12 12:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 17:53 [PATCH] pata_legacy: Allow disabling of legacy PATA device probes on non-PCI systems Matthew Whitehead
2016-11-29 19:41 ` Tejun Heo
2016-11-29 20:12 ` tedheadster
2016-11-29 20:46 ` Tejun Heo
2016-11-30 13:06 ` Bartlomiej Zolnierkiewicz
2016-11-30 17:13 ` tedheadster
2016-11-30 13:11 ` Sergei Shtylyov
2016-11-30 14:53 ` One Thousand Gnomes
2016-11-30 15:03 ` tedheadster
2016-11-30 18:15 ` One Thousand Gnomes
2016-12-02 13:37 ` tedheadster
2016-12-02 16:24 ` One Thousand Gnomes
2016-11-30 20:22 ` Tejun Heo
[not found] ` <CAP8WD_bZWeLBhLXqJG5uDwBe+zBubw+A+ecSuaihOuwvw9QoCQ@mail.gmail.com>
2016-12-02 17:07 ` Tejun Heo
2016-12-05 14:19 ` tedheadster
2016-12-05 19:23 ` Tejun Heo
[not found] ` <CAP8WD_becq+h2=-g7t-6Pp1psmkCCvdB0YUcg+wYPocUP4dYdw@mail.gmail.com>
2016-12-12 17:01 ` Tejun Heo
[not found] ` <CAP8WD_YMtnsuYmJHGz1eLmrQNemsB1Z6Soyb6f72brAfMNUNeg@mail.gmail.com>
2016-12-20 2:12 ` tedheadster
2016-12-22 16:37 ` Tejun Heo
2016-12-22 17:14 ` tedheadster
2016-12-22 17:19 ` Tejun Heo
2016-12-22 18:30 ` tedheadster
2016-12-22 19:22 ` Tejun Heo
2017-01-03 17:34 ` One Thousand Gnomes
[not found] ` <CAP8WD_bS61spyQkd7cvktFf_dPc0wgNZ8qEa7GVrXgUobHQdvw@mail.gmail.com>
2017-01-19 21:37 ` Tejun Heo
2017-01-20 17:08 ` tedheadster
2017-01-20 19:19 ` Tejun Heo
2017-01-20 19:38 ` Tejun Heo
2017-01-23 23:36 ` Gwendal Grignou
2017-01-23 23:57 ` tedheadster
2017-01-24 16:19 ` Tejun Heo
2017-01-27 3:01 ` tedheadster
2017-02-07 20:21 ` Gwendal Grignou
2017-02-08 19:43 ` Tejun Heo
2017-02-09 23:49 ` Gwendal Grignou
2017-02-10 0:36 ` tedheadster
2017-02-10 13:19 ` Tejun Heo
2017-02-23 19:26 ` tedheadster
2017-03-03 17:00 ` [PATCH] libata: transport: Remove circular dependency at free time Gwendal Grignou
2017-03-03 18:28 ` Sergei Shtylyov
2017-03-03 18:36 ` Tejun Heo
2017-03-06 20:09 ` Tejun Heo
2017-03-06 20:11 ` Sergei Shtylyov
2017-03-06 20:26 ` Tejun Heo
2017-01-24 15:57 ` [PATCH] pata_legacy: Allow disabling of legacy PATA device probes on non-PCI systems Tejun Heo
2016-12-12 12:21 ` Bartlomiej Zolnierkiewicz [this message]
2016-11-30 13:12 ` Bartlomiej Zolnierkiewicz
2016-11-30 13:15 ` Sergei Shtylyov
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=2575141.gMpqs59WaB@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@kernel.org \
--cc=whiteheadm@acm.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