From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org, seraph@xs4all.nl
Subject: Re: [Bugme-new] [Bug 10374] New: sym53c8xx: weird behavior with udev
Date: Tue, 01 Apr 2008 09:11:55 -0500 [thread overview]
Message-ID: <1207059115.3100.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20080401011518.eb683cff.akpm@linux-foundation.org>
On Tue, 2008-04-01 at 01:15 -0700, Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
> > Steps to reproduce:
> >
> > Let udev load sym53c8xx in kernel 2.6.23 or newer.
>
> urgh. Perhaps it's related to platform IRQ routing or something.
>
> I'd suggest that the next step would be to send us the `dmesg -s 1000000'
> output for both good and bad kernels. A comparison might show where things
> went bad.
Yes, that would be my guess too ... although I don't see anything amiss
in the dmesg I note you have two ethernet interfaces:
eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:03:ba:08:61:7c
eth1394: eth1: IPv4 over IEEE 1394 (fw-host0)
I'm assuming eth0 is the problem?
Could you also send us the output of /proc/interrupts, /proc/iomem
and /proc/ioports just to see if we have a problem. Also, if eth0 is on
its own interrupt line, does the interrupt count rise even while the
interface is non functional?
Thanks,
James
next prev parent reply other threads:[~2008-04-01 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10374-10286@http.bugzilla.kernel.org/>
2008-04-01 8:15 ` [Bugme-new] [Bug 10374] New: sym53c8xx: weird behavior with udev Andrew Morton
2008-04-01 8:58 ` Jos van der Ende
2008-04-01 14:11 ` James Bottomley [this message]
2008-04-01 14:47 ` Jos van der Ende
2008-04-01 19:05 ` Jos van der Ende
2008-04-01 20:19 ` James Bottomley
2008-04-01 20:57 ` Jos van der Ende
2008-04-01 21:14 ` James Bottomley
2008-04-01 22:30 ` Jos van der Ende
2008-04-02 10:29 ` Jos van der Ende
2008-04-02 12:06 ` Matthew Wilcox
2008-04-02 14:09 ` Jos van der Ende
2008-04-02 15:49 ` James Bottomley
2008-04-02 16:06 ` Jos van der Ende
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=1207059115.3100.9.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=seraph@xs4all.nl \
--cc=sparclinux@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