In message [EMAIL PROTECTED], Bryan Liesner writes:
Revision 1.20 / (download) - annotate - [select for diffs], Mon Mar 10 23:41:41
2003 UTC (5 days, 5 hours ago) by phk
Branch: MAIN
CVS Tags: HEAD
Changes since 1.19: +5 -0 lines
Diff to previous 1.19 (colored)
If we run out of
On Sun, 16 Mar 2003, Poul-Henning Kamp wrote:
I think Poul-Henning will have enough information to go with now...
You guys _way_ overestimate my abilities here.
Right now I have a hard time imagining what geom's eventhandling
for withering geoms can possibly have to do with any non-geom
On Sun, 16 Mar 2003, Poul-Henning Kamp wrote:
One thing I'd like you to try is to remove any trace of USB from your
systems. USB does some ugly VOP_REVOKES which I am not happy about, and
I would like to exclude them from the list of suspects.
You can remove USB from your list, I tried
Bryan Liesner wrote:
On Sun, 16 Mar 2003, Poul-Henning Kamp wrote:
One thing I'd like you to try is to remove any trace of USB from your
systems. USB does some ugly VOP_REVOKES which I am not happy about, and
I would like to exclude them from the list of suspects.
You can remove USB from your
walt wrote:
Bryan Liesner wrote:
On Sun, 16 Mar 2003, Poul-Henning Kamp wrote:
One thing I'd like you to try is to remove any trace of USB from your
systems. USB does some ugly VOP_REVOKES which I am not happy about, and
I would like to exclude them from the list of suspects.
You can remove
On Sun, Mar 16, 2003 at 09:29:15AM +0100, Poul-Henning Kamp wrote:
I don't think I'll stand a chance on this one until I can reproduce it
on one of my machines :-(
I'm not sure if that helps, but on my machine it it enough to take
GENERIC kernconf file, add all GEOM_ options and comment out
In message [EMAIL PROTECTED], Krzysztof Parz
yszek writes:
On Sun, Mar 16, 2003 at 09:29:15AM +0100, Poul-Henning Kamp wrote:
I don't think I'll stand a chance on this one until I can reproduce it
on one of my machines :-(
I'm not sure if that helps, but on my machine it it enough to take
On 15-Mar-2003 Bryan Liesner wrote:
On Fri, 14 Mar 2003, Conrad Sabatier wrote:
Now, really, am I the only one experiencing this?
No, you're not. I've been unable to get a bootable kernel running for the
last few days also.
Booting in verbose mode, I see the last thing that occurs just
cheer! wilma heeft het door.
guest werkt.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Conrad Sabatier
Sent: zaterdag 15 maart 2003 13:22
To: Bryan Liesner
Cc: [EMAIL PROTECTED]
Subject: Re: panic on boot (devfs_find)
On 15-Mar-2003 Bryan Liesner wrote
whoops wrong list...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Bug
Sent: zaterdag 15 maart 2003 13:25
To: Conrad Sabatier; Bryan Liesner
Cc: [EMAIL PROTECTED]
Subject: RE: panic on boot (devfs_find)
cheer! wilma heeft het door.
guest werkt
--- Conrad Sabatier [EMAIL PROTECTED] wrote:
Booting in verbose mode, I see the last thing that occurs just before the panic
is mounting root and then starting (or trying to start) /sbin/init. After an
initial hang, it drops into ddb.
--
I found the same problem for the last two days.
On 15-Mar-2003 Shizuka Kudo wrote:
--- Conrad Sabatier [EMAIL PROTECTED] wrote:
Booting in verbose mode, I see the last thing that occurs just before the
panic is mounting root and then starting (or trying to start) /sbin/init.
After an initial hang, it drops into ddb.
--
I found
On 15-Mar-2003 Shizuka Kudo wrote:
I found the same problem for the last two days. However, it seems that this
problem doesn't appear in the GENERIC kernel. I have tried putting the
INVARIANTS stuffs back to my custom config file and it works as well. Very
strange...
I just built a
--- Bryan Liesner [EMAIL PROTECTED] wrote:
I was able to get a kernel up and running (strangely) on 3/12, but
commits after that cause an immediate panic as soon as init starts.
If I build a kernel from sources cut off at 3/10/2003 at 12:00,
everything works fine.
It is related to the
On Sat, 15 Mar 2003, Shizuka Kudo wrote:
--- Bryan Liesner [EMAIL PROTECTED] wrote:
I was able to get a kernel up and running (strangely) on 3/12, but
commits after that cause an immediate panic as soon as init starts.
If I build a kernel from sources cut off at 3/10/2003 at 12:00,
In message [EMAIL PROTECTED], Bryan Liesner writes:
I made posts here recently describing some panics which are somehow
related to disappearing/never created device nodes. I am unable to
produce a core dump at all, as it panics before / is mounted.
The documented kern.dumpdev (unknown oid)
On Fri, 14 Mar 2003, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Bryan Liesner writes:
I made posts here recently describing some panics which are somehow
related to disappearing/never created device nodes. I am unable to
produce a core dump at all, as it panics before / is
On 14-Mar-2003 Bryan Liesner wrote:
I made posts here recently describing some panics which are somehow
related to disappearing/never created device nodes. I am unable to
produce a core dump at all, as it panics before / is mounted.
The documented kern.dumpdev (unknown oid) doesn't exist
On Fri, 14 Mar 2003, Conrad Sabatier wrote:
Now, really, am I the only one experiencing this?
No, you're not. I've been unable to get a bootable kernel running for the last
few days also.
Booting in verbose mode, I see the last thing that occurs just before the panic
is mounting root and
19 matches
Mail list logo
