patch: add specific support for Marvell MV88SE9186 (AHCI + PCI quirk)

Dear polite inhabitants of LKML, see the attached patch - I think it's pretty clear and simple. Today I've found myself in a situation where an onboard AHCI chip from Marvell did not properly detect a DVD drive. Not so long story short, I had to add the device ID to both drivers/ata/ahci.c an

Re: [noob q. on block layer] block IO read-ahead during sequential *write*?

On 7 Jan 2008 at 13:49, Jörn Engel wrote: > > If you retry the dd with bs=4096 (or whatever your architecture's page > size happens to be), does this still occur? > > JĂśrn > wow, thanks, it works, this is so obvious. I tend to use values like bs=512000 or suchlike, but probably never stroke this

[noob q. on block layer] block IO read-ahead during sequential *write*?

Dear Everyone, let me start with a simple example. The following commands: cp /dev/zero /dev/hda dd if=/dev/zero of=/dev/hda [bs=512] both have one common side-effect: apart from the disk being properly overwritten with zeroes, the kernel seems to keep reading sectors ahead of the current se

Re: [newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU

On 20 Sep 2007 at 0:53, Chuck Ebbert wrote: > Looks like process 2382 is stuck with the kernel trying to send > SIGBUS to that bash process, here: > Wow, thanks for that hint, certainly I wouldn't be able to trace the problem as far as this :-) Does this mean that perhaps bash or glibc (my outda

Re: [newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU

On 19 Sep 2007 at 17:34, Randy Dunlap wrote: > On Wed, 19 Sep 2007 10:50:53 +0200 Frantisek Rysanek wrote: > > I've been trying in vain to post a response to this thread... > Check the taboo expressions here: > http://vger.kernel.org/majordomo-info.html#taboo > Thanks

Re: [newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU

Dear Mr. Piggin, thanks for your response in the first place :-) On 13 Sep 2007 at 2:30, Nick Piggin wrote: > > Can you see if it is looping in userspace or kernel? Can you kill -9 > the process? > This is interesting. I can't run any classic system command. Any command hangs or coredumps. Any

Re: PCI Interrupt

On 19 Sep 2007 at 12:14, Jarek Poplawski wrote: > On 18-09-2007 16:42, Rafael J. Wysocki wrote: > > Hm, edge-triggered interrupts cannot be shared, AFAIK. > > > Let's agree it's only a superstition... > http://en.wikipedia.org/wiki/Edge_triggered_interrupt > Superstition? Depends on how stringent

Re: [newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU

I've been trying in vain to post a response to this thread... Content is text/plain, encoding is ISO 8859-1. Yet it doesn't land in the mailing list. I've included about three URL's to captured data. Is that a problem? Any further hints on what to avoid, and how else to pass big logfiles / binary s

Re: [newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU

Dear Mr. Piggin, thanks for your response in the first place :-) On 13 Sep 2007 at 2:30, Nick Piggin wrote: > > Can you see if it is looping in userspace or kernel? Can you kill -9 > the process? > I can't run any command. Any command hangs or coredumps. > Are you able to test with the latest 2

[newbie:] Bonnie++2 hangs recent 2.6 kernels? Bash keeps looping in waitpid(), eating 100% CPU

Dear everyone, apologies in advance for a silly question... I'm using a homebrew stripped-down mini-distro based on Fedora 5, with various newer kernels, on a live CD, to test hardware with. The live CD is composed by means of scripted binary copy of the key necessary components (libc, init, b