Hi On Sun, 10 Jul 2005, Pierre Ossman wrote:
> 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. 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 that is indeed the problem. As someone also already suggested, you could also just try to reduce your terminal font size to fit the entire Oops on the monitor. I've tried to make a patche for the high-mem problem of dc395x, but we didn't have any testers. So, would be nice if you could help. Thanks Guennadi > > >Matt Mackall says that a common problem is running kernels with > >a log low level: > > > >Kernel command line: ro root=LABEL=/ rhgb quiet acpi=ht > > > >so remove the "quiet" option there, or change it to "debug". > > > > > > Tried with 'debug' and nothing at all. No effect. I also messed around > with the 'printk' setting in /proc/sys/kernel. Netconsole simply doesn't > like me. :( > > Perhaps I'm misunderstanding the scope of netconsole. Is it supposed to > send out everything I can see with 'dmesg' or just panics? > > 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 - 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
