From: Nuno Tavares <nuno.tavares@dri.pt>
To: linux-kernel@vger.kernel.org
Subject: [Fwd: Re: Dell OptiPlex 320 - Core 2 Duo]
Date: Wed, 05 Mar 2008 22:57:11 +0000 [thread overview]
Message-ID: <1204757831.6067.12.camel@localhost.localdomain> (raw)
I now notice this hasn't been CC'ed to the list. Apologies to all.
-NT
------ Mensagem Reencaminhada ------
> Assunto: Re: Dell OptiPlex 320 - Core 2 Duo
> Data: Wed, 05 Mar 2008 22:49:18 +0000
>
> Lennart, those options came from the SuSE installer, I guess. It wasn't
> me installing the machine, and I have no idea why the guy doing it
> whould add so many. I also found it strange, but since it's a Failsafe,
> and SuSE is not my favourite dist, I just left it alone. My first tests
> were done removing several of those (those that, to my knowledge, didn't
> make sense, like: acpi=off, apm=off, mce=off, maxcpus=0, probably
> pci=..).
>
> Actually, the default boots to the not-failsafe:
>
> kernel /boot/vmlinuz-2.6.22.5-23-default
> root=/dev/disk/by-id/scsi-SATA_WDC_WD800JD-75M_WD-WMAM9TA95509-part2
> apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux
> psmouse.proto=bare irqpoll pci=nommconf resume=/dev/sda1 splash=silent
> showopts
>
> Both share lots of options, anyway. I wonder what "irqpoll" does, though
> (it's probably related with "Misrouted IRQ fixup and polling support
> enabled" dmesg)... I just lack the opportunity to test all the
> combinations (the machine is remote)..
>
> Even if the model is not the same as described, Optiplex has a nice
> (not!) history of problems:
>
> http://www.suseforums.net/index.php?showtopic=34172
>
> http://suseroot.com/blog/blog.php?postid=74
>
> I forgot to mention that this last time I tried the combinations:
> * acpi=on + pci=nomsi
> * acpi=on + pci=routeirq
>
> -NT
>
>
> Qua, 2008-03-05 às 16:39 -0500, Lennart Sorensen escreveu:
> [...]
> > > kernel /boot/vmlinuz-2.6.22.5-23-default
> > > root=/dev/disk/by-id/scsi-SATA_WDC_WD800JD-75M_WD-WMAM9TA95509-part2
> > > showopts ide=nodma apm=off noresume noapic pci=route edd=off 3
>
> [errata: it's pci=routeirq, obviously]
>
> > > It didn't help. The boot stops at the line PCI: xxxxxx something. I'll
> > > try to try the BIOS update issue. I'll report back later.
> >
> > Well most of the options seem like a bad idea in general.
> >
> > ide=nodma, noapic and maxcpus I just can't imagine why would be listed
> > there. Usually you add an option if it solves a problem, you don't add
> > all of the possible options. Multi processor requires some of those
> > features, and disabling dma on ide makes no sense unless you are using a
> > very broken ide drive.
> >
> > Who added all those options and why?
> >
> > --
> > Len Sorensen
> >
--
Nuno Tavares
DRI, Consultoria Informática
Telef: +351 936 184 086
reply other threads:[~2008-03-05 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1204757831.6067.12.camel@localhost.localdomain \
--to=nuno.tavares@dri.pt \
--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
all inboxes | Powered by JetHome®