public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Rich <kxr@cthulhu.engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ACPI: Uninitialized spinlocks & Unable to dump stack
Date: Thu, 02 Aug 2007 01:06:07 +0000	[thread overview]
Message-ID: <46B12DFF.mailxHXS1AFKS4@cthulhu.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707312246390.14878@schroedinger.engr.sgi.com>

> With those two patches the kernel boots on SN2.
> Life is good.

Yes, I can boot on SN2 now with these two patches also.  However,
I didn't really expect to see no udev messages in boot.log

wine3:/var/log # grep udev boot.msg
wine3:/var/log # 

wine3:/var/log # grep udev boot.omsg
<notice>boot.udev start
Starting udevd done
<notice>'boot.udev start' exits with status 0
Waiting for udev to settle...
Waiting for udev to settle...
udev on /dev type tmpfs (rw)
<notice>boot.udev_retry start
<notice>'boot.udev_retry start' exits with status 0

I also didn't expect to see no usb recognized on this system,
but this problem did not show up on a second system I tried,
so that deserves further observation.

Keith

wine3:/var/log # lsusb
wine3:/var/log # 

wine3:/var/log # grep usb boot.msg
wine3:/var/log # 

wine3:/var/log # grep usb boot.omsg
<6>usbcore: registered new driver usbfs
<6>usbcore: registered new driver hub
<6>usb usb1: new device found, idVendor\000, idProduct\000
<6>usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
<6>usb usb1: Product: EHCI Host Controller
<6>usb usb1: Manufacturer: Linux 2.6.16.27-0.6-default ehci_hcd
<6>usb usb1: SerialNumber: 0001:01:01.2
<6>usb usb1: configuration #1 chosen from 1 choice
<6>usb usb2: new device found, idVendor\000, idProduct\000
<6>usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
<6>usb usb2: Product: OHCI Host Controller
<6>usb usb2: Manufacturer: Linux 2.6.16.27-0.6-default ohci_hcd
<6>usb usb2: SerialNumber: 0001:01:01.0
<6>usb usb2: configuration #1 chosen from 1 choice
<6>usb usb3: new device found, idVendor\000, idProduct\000
<6>usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
<6>usb usb3: Product: OHCI Host Controller
<6>usb usb3: Manufacturer: Linux 2.6.16.27-0.6-default ohci_hcd
<6>usb usb3: SerialNumber: 0001:01:01.1
<6>usb usb3: configuration #1 chosen from 1 choice
<6>usb 2-1: new low speed USB device using ohci_hcd and address 2
<6>usb 2-1: new device found, idVendor\x04a5, idProductp03
<6>usb 2-1: new device strings: Mfr=4, Product , SerialNumber=0
<6>usb 2-1: Product: Generic USB Keyboard
<6>usb 2-1: Manufacturer: NOVATEK
<6>usb 2-1: configuration #1 chosen from 1 choice
<6>usb 3-1: new low speed USB device using ohci_hcd and address 2
<6>usb 3-1: new device found, idVendor\x046d, idProduct¿00
<6>usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0
<6>usb 3-1: Product: N43
<6>usb 3-1: Manufacturer: Logitech
<6>usb 3-1: configuration #1 chosen from 1 choice
<6>usbcore: registered new driver hiddev
<6>input: USB HID v1.10 Keyboard [NOVATEK Generic USB Keyboard] on usb-0001:01:01.0-1
<6>input: USB HID v1.00 Mouse [Logitech N43] on usb-0001:01:01.1-1
<6>usbcore: registered new driver usbhid
<6>drivers/usb/input/hid-core.c: v2.6:USB HID core driver
wine3:/var/log # 

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2007-08-02  1:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  5:48 ACPI: Uninitialized spinlocks & Unable to dump stack Christoph Lameter
2007-08-01 12:18 ` Kenji Kaneshige
2007-08-01 13:33 ` Jes Sorensen
2007-08-01 16:00 ` Russ Anderson
2007-08-01 20:02 ` Christoph Lameter
2007-08-01 20:34 ` Russ Anderson
2007-08-02  1:06 ` Keith Rich [this message]
2007-08-02  1:37 ` Keith Rich

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=46B12DFF.mailxHXS1AFKS4@cthulhu.engr.sgi.com \
    --to=kxr@cthulhu.engr.sgi.com \
    --cc=linux-ia64@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