From: Keith Owens <kaos@ocs.com.au>
To: Marc Schiffbauer <marc.schiffbauer@links2linux.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: new aic7xxx oopses with AHA2940
Date: Sun, 27 May 2001 11:07:16 +1000 [thread overview]
Message-ID: <21164.990925636@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 26 May 2001 18:05:29 +0200." <20010526180529.A7595@lisa.links2linux.home>
On Sat, 26 May 2001 18:05:29 +0200,
Marc Schiffbauer <marc.schiffbauer@links2linux.de> wrote:
>I have problems with the new aic7xxx-Driver. These problems exist
>with vanilla (2.4.4, 2.5.5, other d.k.) and -ac
>May 26 17:52:33 homer kernel: EIP: 0010:[usbcore:usb_devfs_handle_Re9c5f87f+161255/198895517]
>May 26 17:52:33 homer kernel: Call Trace: [usbcore:usb_devfs_handle_Re9c5f87f+162269/198894503] [usbcore:usb_devfs_handle_Re9c5f87f+164966/198891806] [__delay+19/48] [usbcore:usb_devfs_handle_Re9c5f87f+166493/198890279] [usbcore:usb_devfs_handle_Re9c5f87f+117712/198939060] [usbcore:usb_devfs_handle_Re9c5f87f+185577/198871195] [usbcore:usb_devfs_handle_Re9c5f87f+171751/198885021]
>
>Does it crash with the USB-Driver?? But USB works fine... even after
>the Oops
Because you are using a broken version of klogd that stuffs up oops
traces. Change klogd to run as klogd -x (probably in
/etc/rc.d/init.d/syslog) so it keeps its broken fingers off the oops.
Since you are failing during modprobe, creating /var/log/ksymoops is a
good idea, man insmod, see KSYMOOPS ASSISTANCE. Reproduce the
problem to get a clean oops trace then run it through ksymoops, using
the saved module data in /var/log/ksymoops.
next prev parent reply other threads:[~2001-05-27 1:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 16:05 new aic7xxx oopses with AHA2940 Marc Schiffbauer
2001-05-27 1:07 ` Keith Owens [this message]
2001-05-27 2:21 ` Marc Schiffbauer
2001-05-27 2:32 ` Keith Owens
2001-05-27 2:36 ` Jeff Garzik
2001-05-27 10:41 ` Marc Schiffbauer
2001-05-29 18:55 ` Justin T. Gibbs
2001-05-29 22:26 ` Marc Schiffbauer
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=21164.990925636@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.schiffbauer@links2linux.de \
/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.