From: "Stephen D. Williams" <sdw@lig.net>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Soft lockup in e100 driver ?
Date: Thu, 11 Aug 2005 23:11:18 -0400 [thread overview]
Message-ID: <42FC1356.7080708@lig.net> (raw)
In-Reply-To: <20050811073946.GT22165@mea-ext.zmailer.org>
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]
"noapic" didn't work, nor did "noacpi", etc.
Going to 2.6.13-rc6.2 solved the problem (once I integrated udev, etc.).
The chipset is an Intel 8x0 something. Unfortunately, there is a
heatsink semi-permanently installed over everything. Is there a /proc
pseudofile that will give me good identifying chipset info to report here?
If there is a FAQ for this, we should post a message about it once in a
while.
Nothing here indicates chipset:
http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
The CPU is an Intel Celeron CPU 2.00GHz running at 1495.772 MHz, 128MB
cache.
sdw
Matti Aarnio wrote:
>On Wed, Aug 10, 2005 at 08:32:45PM -0400, Stephen D. Williams wrote:
>
>
>>I just noticed that the Ubuntu setup says "GSI 20(level,low) -> IRQ 20"
>>whereas I remember my built kernels saying "No GSI...... IRQ 11". I'll
>>investigate what that means and how to enable it. Pointers appreciated.
>>
>>
>
>That is most likely unrelated, but I had similar experiences
>at times. It turned out that something done recently in APIC
>management code did break things, but lattest version is again
>working. For a while to have network card working I had to boot
>with "noapic" option in my home SMP box.
>
>In an UP box it is about same to boot as "noapic", but in SMP it
>does result in "one CPU does all interrupts" thingie. (In some
>rare cases it could be desirable, even.)
>
> /Matti Aarnio
>
>
>
>
>>sdw
>>
>>Stephen D. Williams wrote:
>>
>>
>>
>>>I have been working for days to get a recent kernel to work with these
>>>small-format UP Celeron 2Ghz (running at 1.33Ghz) motherboards that I
>>>am planning to use as thin clients. I'm doing a PXE boot, loading
>>>kernels, and trying to get networking to come up.
>>>
>>>I eventually realized that the problem is that the e100 driver loads
>>>but does not allow any packet traffic. The system isn't crashed, but
>>>I do get transmit timeouts.
>>>
>>>I've used kernels: 2.6.10, 2.6.11, and 2.6.12.4, stock with only the
>>>"squashfs" patch applied and compiled as 586/....
>>>
>>>The interesting thing is that Ubuntu 5.04, booted "Live" on the box,
>>>works just fine with the e100 driver with a kernel shown as:
>>>"2.6.10-5-386". I'm going to work on pulling this kernel and its
>>>modules off to use.
>>>
>>>Any help urgently appreciated.
>>>
>>>sdw
>>>
>>>
>
>
>
[-- Attachment #2: sdw.vcf --]
[-- Type: text/x-vcard, Size: 234 bytes --]
begin:vcard
fn:Stephen Williams
n:Williams;Stephen
email;internet:sdw@lig.net
tel;work:703-724-0118
tel;fax:703-995-0407
tel;pager:sdwpage@lig.net
tel;home:703-729-5405
tel;cell:703-371-9362
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2005-08-12 3:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 13:36 Soft lockup in e100 driver ? Matti Aarnio
2005-08-09 13:55 ` Jesper Juhl
2005-08-09 14:37 ` Matti Aarnio
2005-08-09 15:41 ` Steven Rostedt
2005-08-09 15:55 ` Matti Aarnio
2005-08-09 16:14 ` Steven Rostedt
2005-08-09 14:58 ` Lee Revell
2005-08-09 15:23 ` Steven Rostedt
2005-08-09 15:32 ` Daniel Walker
2005-08-09 16:16 ` Daniel Walker
2005-08-09 16:36 ` Matti Aarnio
2005-08-11 0:29 ` Stephen D. Williams
2005-08-11 0:32 ` Stephen D. Williams
2005-08-11 7:39 ` Matti Aarnio
2005-08-12 3:11 ` Stephen D. Williams [this message]
2005-08-12 5:45 ` Jesse Brandeburg
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=42FC1356.7080708@lig.net \
--to=sdw@lig.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.