On Mon, 13 Aug 2007 20:13:54 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> I'm struggling a bit to work out if this is a scsi bug, a USB bug, an
> MMC bug or whatever. But it's a bug.
>
I can't see anything MMC related in his dmesg, only what seems to be a
USB based reader:
scsi 0:0:0:0:
Andrew Morton wrote:
>
> A quick scan indicates that the following files might be buggy in this
> regard:
>
> drivers/mmc/wbsd.c
> drivers/mmc/sdhci.c
This are probably even buggier than so. They really should be using
page_address(), it seems that kmap_atomic() gives the same result when
not us
randy_dunlap wrote:
>Pierre,
>
>Can you capture the complete panic message using serial console or
>netconsole? or at least use a smaller font on the console so that
>we can see the entire panic message, as some critical parts of it
>have scrolled off the top of the screen.
>
>
>
Hmm... I made
randy_dunlap wrote:
>3c59x ??
>3c59x.c has CONFIG_NET_POLL_CONTROLLER code in it.
>I would expect it to work since it's a fairly common NIC, but I
>can't vouch for it.
>Did you enable CONFIG_NETPOLL in your kernel .config?
>
>
>
Yup. It's enabled. NETPOLL_RX is not enabled though. Is that neede
I've tried to get it running on three separate machines now with no
success (each running a different kernel version), so I'm starting to
suspect I'm doing something wrong here. I've used the following line to
load the module:
modprobe netconsole netconsole=@/,@10.8.0.168/
I've tried changing the
randy_dunlap wrote:
>Are you using netcat on the receive side?
>
>
>
I've been using tcpdump and not a single packet eminates from the
machine when printk:s show up.
>Matt Mackall says that a common problem is running kernels with
>a log low level:
>
>Kernel command line: ro root=LABEL=/ rhgb
Guennadi Liakhovetski wrote:
>
>Have you managed to get netconsole running? Do you have no chance at all
>to use a serial console? You are, perhaps, the only / last user of dc395x
>on a high-mem machine, the driver is known to have a problem there,
>although from your dump I cannot see yet if t
Guennadi Liakhovetski wrote:
>>127MB HIGHMEM available.
>>896MB LOWMEM available.
>>
>>
Quite right. The limit is slightly before 1 GB, not exactly at it. My bad.
Rgds
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED
Finally a dump with a smaller font so that the entire panic is visible:
http://craffe.se/dc395x_panic.jpg
Rgds
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-inf
I have now tried with highmem disabled and the driver still crashes. See
the following image:
http://craffe.se/dc395x_kernel_bug.jpg
Rgds
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vg
randy_dunlap wrote:
>
>Does this happen on every boot?
>
>
Yup
>Please send your .config file (or put it on craffe.se).
>
>
Included
>Does this happen with othe kernel versions?
>
>
Not that I've found. I could try compiling the currently running kernel
(2.6.11.7) without highmem if you
I'm having some problems with your mailserver Randy. I'll cc the mailing
list hoping you'll see this there.
I get:
<<< 550-Verification failed for <[EMAIL PROTECTED]>
<<< 550-unrouteable mail domain "drzeus.cx"
<<< 550 Sender verify failed
As far as i know my MX records are completely correct.
randy_dunlap wrote:
>
>
>That's a highmem bug. IIRC, Guennadi said that highmem does not
>(or may not) work correctly in this driver, so I should have
>asked you to test with HIGHMEM disabled so that the other bug
>can be addressed.
>
>
>
I have now tried 2.6.12{,.1,.2} and only 2.6.12.2 bre
randy_dunlap wrote:
>
>The only 2 differences that I can see that would affect this
>(diff patch-2.6.12.1 vs. patch-2.6.1.2) are: (cut-n-paste, so
>has whitespace munging)
>
>
>
Neither had any effect. :/
Rgd
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
t
randy_dunlap wrote:
>
>oh drat. Please test 2.6.12.2 with the following patch segment
>backed out (-R, reversed). I don't see any other patches that could
>be the cause. If this isn't the problem, I would have to begin
>to suspect some kind of toolchain problem.
>
>
>
It seems the blame fall
Ok, I've now figured out where the bug appears. 2.6.12-rc4 runs fine
while -rc5 does not.
Rgds
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Guennadi Liakhovetski wrote:
>So, now that we have somebody to test alternative patches, let's try it...
>Please, first revert the first patch (apply with -R), and then apply the
>second one. There, probably, will be offsets, don't worry about them.
>Warning: untested. Please, try some read-onl
17 matches
Mail list logo
