From: Jos van der Ende <seraph@xs4all.nl>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 10374] New: sym53c8xx: weird behavior with udev
Date: Tue, 1 Apr 2008 16:47:40 +0200 [thread overview]
Message-ID: <20080401164740.c4a5ec3f.seraph@xs4all.nl> (raw)
In-Reply-To: <1207059115.3100.9.camel@localhost.localdomain>
On Tue, 01 Apr 2008 09:11:55 -0500
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Tue, 2008-04-01 at 01:15 -0700, Andrew Morton wrote:
> >
> > 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?
Yes, the Sun GEM interface is the problem. Ethernet over FireWire (a direct link between the webserver and database server) works just fine. In a minimal config with no devices enabled except the SU serial line (needed for console), the dual SCSI adapter and the Sun GEM nic, the problem still remained the same.
> 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?
Here goes:
seraphim ~ # cat /proc/interrupts
CPU0
0: 7259 <NULL> timer
8: 0 sun4u power
9: 405 sun4u su(serial)
11: 1 sun4u eth0
12: 95 sun4u ohci1394
13: 0 sun4u ohci_hcd:usb1
14: 0 sun4u ALI 5451
15: 2265 sun4u ide0
16: 293 sun4u sym53c8xx
17: 69 sun4u sym53c8xx
seraphim ~ # cat /proc/iomem
1fe020002e8-1fe020002ef : su
1fe020003f8-1fe020003ff : su
1fe02000800-1fe02000803 : power
1ff00000000-1ffffffffff : /pci@1f,0
1ff000a0000-1ff000bffff : Video RAM area
1ff000c0000-1ff000c7fff : Video ROM
1ff000f0000-1ff000fffff : System ROM
1ff00400000-1ff0041ffff : sungem
1ff00420000-1ff004207ff : ohci1394
1ff00424000-1ff00425fff : ALI 5451
1ff02000000-1ff02ffffff : ohci_hcd
1ff03000000-1ff03001fff : sym53c8xx
1ff03002000-1ff03003fff : sym53c8xx
1ff03004000-1ff03005fff : sym53c8xx
1ff03006000-1ff03007fff : sym53c8xx
1ffc0000000-1ffdfffffff : IOMMU
1fff1000000-1fff1001fff : clock
seraphim ~ # cat /proc/ioports
00000600-0000061f : ali1535_smbus
1fe02000000-1fe02ffffff : /pci@1f,0
1fe02000600-1fe0200061f : 0000:00:03.0
1fe02000800-1fe0200083f : 0000:00:03.0
1fe02000900-1fe020009ff : ALI 5451
1fe02000a00-1fe02000a07 : ide0
1fe02000a1a-1fe02000a1a : ide0
1fe02000a20-1fe02000a27 : ide0
1fe02000a28-1fe02000a2f : ide1
1fe02001000-1fe020010ff : sym53c8xx
1fe02001100-1fe020011ff : sym53c8xx
--
Jos van der Ende <seraph@xs4all.nl>
next prev parent reply other threads:[~2008-04-01 14:47 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
2008-04-01 14:47 ` Jos van der Ende [this message]
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=20080401164740.c4a5ec3f.seraph@xs4all.nl \
--to=seraph@xs4all.nl \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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