Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Grozdan <neutrino8@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: hancockrwd@gmail.com, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33
Date: Wed, 3 Jun 2009 15:39:48 +0200	[thread overview]
Message-ID: <c5bd819b0906030639o5f9c34ffg500e132d3a0b5117@mail.gmail.com> (raw)
In-Reply-To: <20090603140140.491a8ea8@lxorguk.ukuu.org.uk>

2009/6/3 Alan Cox <alan@lxorguk.ukuu.org.uk>:
> What about 2.6.28 or 2.6.29 ?
>

Hi,

I just installed kernel 2.6.29.4-rt16-2-rt from the SUSE build service
(there's no 2.6.28 one available nor a 'normal' 2.6.29 one) and my
UDMA is set correctly just as when using the default 2.6.27.21 kernel.
Now I'm not sure if there really is a problem in 2.6.30-rc7-git4 or
did I somehow introduced it by configuring something incorrectly
(which I doubt because as I said, I didn't touch anything related to
IDE during configuration. I only tweaked a few options, most of them
in the General and Processor sections). However, this
2.6.29.4-rt16-2-rt kernel seems to have a bug (not sure if it's
present in mainline too or because of the patches Novell used to build
this rt kernel) in rtmutex as I get things such as...

BUG: sleeping function called from invalid context at
/usr/src/packages/BUILD/kernel-rt-2.6.29.4/linux-2.6.29/kernel/rtmutex.c:685
in_atomic(): 1, irqs_disabled(): 1, pid: 17, name: work_on_cpu/0
Pid: 17, comm: work_on_cpu/0 Not tainted 2.6.29.4-rt16-2-rt #1
Call Trace:
[<ffffffff80227b4a>] dump_trace+0xda/0x3d0
[<ffffffff802288ff>] show_trace_log_lvl+0x4c/0x58
[<ffffffff8022891b>] show_trace+0x10/0x12
[<ffffffff804ee605>] dump_stack+0x72/0x7b
[<ffffffff80252635>] __might_sleep+0x10a/0x10c
[<ffffffff804f0af7>] rt_spin_lock+0x2f/0x78
[<ffffffff802ee5b1>] _slab_irq_disable+0x40/0x63
[<ffffffff802f0495>] kmem_cache_alloc_node+0x3a/0x21b
[<ffffffff802a9621>] irq_to_desc_alloc_cpu+0xb7/0x20e
[<ffffffff8023d47a>] io_apic_set_pci_routing+0x63/0xbe
[<ffffffff80238555>] mp_register_gsi+0xc1/0xcc
[<ffffffff802385cc>] acpi_register_gsi+0x3f/0x4b
[<ffffffff803fb41b>] acpi_pci_irq_enable+0x145/0x233
[<ffffffff8045c4bb>] pcibios_enable_device+0x29/0x2e
[<ffffffff803ae1b7>] do_pci_enable_device+0x28/0x40
[<ffffffff803ae224>] __pci_enable_device_flags+0x55/0x70
[<ffffffff803ae24d>] pci_enable_device+0xe/0x10
[<ffffffffa0116292>] usb_hcd_pci_probe+0x42/0x2a0 [usbcore]
[<ffffffff803afc7b>] local_pci_probe+0x12/0x16
[<ffffffff80273224>] do_work_for_cpu+0x13/0x1b
[<ffffffff80273429>] run_workqueue+0x110/0x1b0
[<ffffffff802735a9>] worker_thread+0xe0/0xf1
[<ffffffff80277028>] kthread+0x49/0x76
[<ffffffff80225f9a>] child_rip+0xa/0x20


---------- dmesg IDE of 2.6.29.4-rt16-2-rt----------------

pata_via 0000:00:0f.0: PCI INT A -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20
scsi0 : pata_via
scsi1 : pata_via
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xdc00 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xdc08 irq 15
ata1.00: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133
ata1.00: 160086528 sectors, multi 16: LBA
ata1.01: ATA-5: ST340016A, 3.10, max UDMA/100
ata1.01: 78165360 sectors, multi 16: LBA
ata1.00: configured for UDMA/133
ata1.01: configured for UDMA/100
isa bounce pool size: 16 pages
scsi 0:0:0:0: Direct-Access     ATA      Maxtor 6Y080L0   YAR4 PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access     ATA      ST340016A        3.10 PQ: 0 ANSI: 5
ata2.00: ATAPI: TSSTcorpCD/DVDW TS-H552U, US08, max UDMA/33
ata2.00: configured for UDMA/33
scsi 1:0:0:0: CD-ROM            TSSTcorp CD/DVDW TS-H552U US08 PQ: 0 ANSI: 5
BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
udevd version 128 started
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors: (81.9 GB/76.3 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors: (81.9 GB/76.3 GiB)

  parent reply	other threads:[~2009-06-03 13:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c5bd819b0906021525l13ee9282j1fb270e141985f66@mail.gmail.com>
2009-06-03  4:05 ` Kernel 2.6.30rc7 limits IDE to UDMA33 Robert Hancock
2009-06-03 11:35   ` Grozdan
2009-06-03 12:14     ` Alan Cox
2009-06-03 12:52       ` Grozdan
2009-06-03 13:01         ` Alan Cox
2009-06-03 13:15           ` Grozdan
2009-06-03 13:39           ` Grozdan [this message]
2009-06-04 14:50             ` Grozdan
2009-06-05  9:05               ` Alan Cox
2009-06-05 10:35                 ` Grozdan
2009-06-05 10:42                   ` Alan Cox
2009-06-05 12:43                     ` Grozdan
2009-06-05 13:21                       ` Alan Cox
2009-06-05 14:02                         ` Grozdan
2009-06-06  1:07                     ` Robert Hancock
2009-06-06 14:56                       ` Alan Cox
2009-06-06 18:16                         ` Robert Hancock
2009-06-06 22:08                           ` Alan Cox
2009-06-07  4:39                           ` Grozdan
     [not found]                             ` <4A2BF785.3020402@gmail.com>
2009-06-07 18:24                               ` Grozdan
2009-06-07 18:46                                 ` Michael S. Zick
2009-06-07 19:54                                   ` Alan Cox

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=c5bd819b0906030639o5f9c34ffg500e132d3a0b5117@mail.gmail.com \
    --to=neutrino8@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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