RE: "SCR access via SIDPR is available but doesn't work"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> -----Original Message-----
> From: Tejun Heo [mailto:tj@xxxxxxxxxx]
> Sent: 08 October 2008 22:50
> To: Rob Whitton
> Cc: linux-ide@xxxxxxxxxxxxxxx
> Subject: Re: "SCR access via SIDPR is available but doesn't work"
> 
> Tejun Heo wrote:
> > Rob Whitton wrote:
> >> I have run this test and I can confirm that NumLock does still
work,
> >> although unreliably. What I mean by this is that once we get to
this
> >> point often it takes a number of presses of numlock to get the
state
> of
> >> the LED to change. Before we get to this point it seems to behave
> fine.
> >> Ctrl-alt-sysrq-t doesn't appear to dump anything to the console.
> After
> >> doing ctrl-alt-sysrq-t numlock no longer functions at all.
> >>
> >> Something I forgot to mention in my original email is that using
> >> "noapic" at boot is also a work around for the problem. It isn't an
> >> option for us as we are going to be using advanced features such as
> MSI
> >> that are only available via the APIC route.
> >
> > I don't think MSI has anything to do with noapic.  Can you please
> post
> > the result of "lspci -nn"?  Also, what kind of motherboard is it?
> 
> Oh.. and one more thing, can you please confirm that commenting out
> PIIX_FLAG_SIDPR settings in piix_port_info structures fix the problem?
> 
> Thanks.
> 
> --
> Tejun

We experience the same problem with two different motherboards (the only
motherboards we have tried in this system):

  TYAN S5211
  Intel S3210SHLC

The original boot logs were from the Tyan motherboard which is what we
have been working with almost exclusively. However, in the lab we
currently have the Intel board in use and as such I've recreated the
failing and succeeding boot logs on the Intel board so that the boots
logs are consistent with the output of "lspci -nn" which is also
attached.

With regard to changing piix_port_info structures this will have to wait
for the moment. Our kernel building expert is currently on vacation. But
maybe this step will be unnecessary - see below.

I note that in the Intel boot logs whilst booting stops at the same
point it doesn't display the message which started this thread and
tended to point the finger of suspicion at the PIIX driver (probably
should change the subject line of the email). Maybe it is a more
fundamental kernel problem? I'm still very surprised that simply moving
the SATA disk between ports causes this problem. Maybe it relates to
interrupt routing or similar. I assume that the two SATA controllers in
the Intel chipset use different interrupts.

Thank you for your info regarding "noapic" and "MSI". We will look into
this more thoroughly but are some way from that point at the moment.

Cheers

Rob





Attachment: intel_rob_s5.cap
Description: intel_rob_s5.cap

00:00.0 Host bridge [0600]: Intel Corporation 3200/3210 Chipset DRAM Controller [8086:29f0]
00:06.0 PCI bridge [0604]: Intel Corporation 3210 Chipset Host-Secondary PCI Express Bridge [8086:29f9]
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02)
00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02)
00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02)
00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02)
00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02)
00:1f.2 IDE interface [0101]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller [8086:2920] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
00:1f.5 IDE interface [0101]: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller [8086:2926] (rev 02)
01:00.0 Mass storage controller [0180]: Device [1a10:0001]
03:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02)
04:02.0 Ethernet controller [0200]: Intel Corporation 82541GI Gigabit Ethernet Controller [8086:1076] (rev 05)

Attachment: intel_rob_s0.cap
Description: intel_rob_s0.cap


[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux