linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Bob Tracy <rct@frus.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	mingo@elte.hu, linux-kernel@vger.kernel.org, rjw@sisk.pl,
	rth@twiddle.net, ink@jurassic.park.msu.ru,
	linux-scsi@vger.kernel.org, greg@kroah.com
Subject: Re: [BUG] 2.6.23-rc3 can't see sd partitions on Alpha
Date: Sun, 09 Dec 2007 13:51:47 +1300	[thread overview]
Message-ID: <475B3C23.6010304@orcon.net.nz> (raw)
In-Reply-To: <1197128912.5483.51.camel@lov.site>

Kay Sievers wrote:
> On Fri, 2007-12-07 at 23:05 -0600, Bob Tracy wrote:
>> Kay Sievers wrote:
>>> Is the udev daemon (still) running while it fails?
>> Yes, and there's something else I forgot to mention that may be
>> significant...  For the bad case, in addition to udevd, "ps -ef"
>> shows a "sh -e /lib/udev/net.agent" running with a PPID of 1.  This
>> process doesn't exit until I reboot.  If this is normal under the
>> circumstances, please disregard.
> 
> Does SysRq-T show where it hangs?

Ummm... No.  I didn't have the CONFIG_MAGIC_SYSRQ flag set, so I set it, 
and recompiled the kernel.  Guess what - now the system comes up 
normally without any problem.  The block devices appear in /dev.  To 
recap: without CONFIG_MAGIC_SYSRQ on the 2.6.24-rc3 kernel the missing 
block devices error in /dev occurs and the init scripts fall over on 
startup, and with CONFIG_MAGIC_SYSRQ the system comes up normally.

To answer the earlier questions about distro, and udev version, my 
system is similar to Bob's, except that I am running Debian 
testing/lenny which comes with udev version 114 (dpkg reports udev 
version 0.114-2).  I am running an EV67 variant CPU.

I do not run an initramfs - I have the necessary drivers for the various 
discs compiled into the kernel and use the root kernel option to point 
to the required root partition.

When running the broken kernel udev is running (according to 'ps') and 
executing /sbin/udevtrigger manually generates a number of errors of the 
form:

scsi_id[<pid>]: scsi_id: unable to access '/block'

The missing /dev/* entries do not appear.

Cheerz
Michael.

  reply	other threads:[~2007-12-09  0:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18  5:20 [BUG] 2.6.23-rc3 can't see sd partitions on Alpha Bob Tracy
2007-11-25  6:38 ` Andrew Morton
2007-11-25 12:15   ` Rafael J. Wysocki
2007-11-26 13:48   ` Bob Tracy
2007-11-30 22:30     ` Michael Cree
2007-11-30 22:42       ` Andrew Morton
2007-11-30 23:26         ` Rafael J. Wysocki
2007-12-02 20:53         ` Michael Cree
2007-12-03  1:17           ` Bob Tracy
2007-12-04 12:16             ` Ingo Molnar
2007-12-04 15:36               ` Bob Tracy
2007-12-05 17:30               ` Bob Tracy
2007-12-07  0:16               ` Bob Tracy
2007-12-07  0:33                 ` Andrew Morton
2007-12-07  5:07                   ` Bob Tracy
2007-12-07 10:26                     ` Andrew Morton
2007-12-07 11:37                       ` Ingo Molnar
2007-12-07 13:39                       ` Bob Tracy
2007-12-07 14:55                       ` Bob Tracy
2007-12-07 15:05                         ` Ingo Molnar
2007-12-07 16:59                           ` Bob Tracy
2007-12-07 18:06                             ` Ingo Molnar
2007-12-07 18:19                               ` Kay Sievers
2007-12-07 19:36                                 ` Bob Tracy
2007-12-07 20:43                         ` Michael Cree
2007-12-07 21:19                           ` Kay Sievers
2007-12-07 22:39                             ` Bob Tracy
2007-12-08  4:53                             ` Bob Tracy
2007-12-08  5:05                             ` Bob Tracy
2007-12-08 15:48                               ` Kay Sievers
2007-12-09  0:51                                 ` Michael Cree [this message]
2007-12-09  4:19                                   ` Bob Tracy
2007-12-09 18:07                                     ` Ivan Kokshaysky
2007-12-10 15:08                                       ` Bob Tracy
2007-12-10 23:12                                         ` Ivan Kokshaysky
2007-12-10 15:05                                 ` Bob Tracy
2007-12-07 11:40                     ` Ingo Molnar
2007-12-07  5:42                   ` Bob Tracy
2007-12-07  9:33                   ` Ingo Molnar
2007-12-07  0:44                 ` Rafael J. Wysocki

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=475B3C23.6010304@orcon.net.nz \
    --to=mcree@orcon.net.nz \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rct@frus.com \
    --cc=rjw@sisk.pl \
    --cc=rth@twiddle.net \
    /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;
as well as URLs for NNTP newsgroup(s).