From: Hans Reiser <reiser@namesys.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Alexander Gran <alex@zodiac.dnsalias.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, "Brown,
Len" <len.brown@intel.com>, Adam Belay <ambx1@neo.rr.com>,
reiserfs-dev@namesys.com, Dave Airlie <airlied@linux.ie>,
"Vladimir V. Saveliev" <vs@namesys.com>,
Alexander Zarochentcev <zam@namesys.com>
Subject: Re: Re. 2.6.15-mm1
Date: Fri, 06 Jan 2006 01:30:22 -0800 [thread overview]
Message-ID: <43BE38AE.80203@namesys.com> (raw)
In-Reply-To: <20060105144720.25085afa.akpm@osdl.org>
Andrew Morton wrote:
>
>
>
>
>>When X startet, the laptops crashed:
>>Jan 5 16:22:43 t40 kernel: <4>reiser4[syslogd(2729)]: disable_write_barrier
>>(fs/reiser4/wander.c:233)[zam-1055]:
>>Jan 5 16:22:43 t40 kernel: WARNING: disabling write barrier
>>
>>
>
>Vladimir, is that expected?
>
>
Vladimir is in France skiing, as this is Russian Christmas right now.
Zam says that this merely means that the underlying device does not
support write barriers, and the code uses synchronous writes for commits
instead of write barriers when this happens. It should not affect
correctness. He will comment more this evening (russian time) when he
gets home. He suggests that he should change it from warning to
notice. He also suggests that this code is new code, so it is possible
it has bugs.....
>
>
>>Jan 5 16:22:43 t40 kernel:
>>Jan 5 16:22:47 t40 kernel: mtrr: 0xe0000000,0x8000000 overlaps existing
>>0xe0000000,0x4000000
>>Jan 5 16:22:48 t40 last message repeated 2 times
>>
>>
>
>Is that new?
>
>
>
>>Jan 5 16:22:48 t40 kernel: agpgart: Found an AGP 2.0 compliant device at
>>0000:00:00.0.
>>Jan 5 16:22:48 t40 kernel: c028b7cf
>>Jan 5 16:22:48 t40 kernel: Modules linked in: irtty_sir sir_dev cfq_iosched
>>ehci_hcd uhci_hcd
>>Jan 5 16:22:48 t40 kernel: EIP: 0060:[<c028b7cf>] Not tainted VLI
>>Jan 5 16:22:48 t40 kernel: EFLAGS: 00013202 (2.6.15-mm1)
>>Jan 5 16:22:48 t40 kernel: <0>c028b9e9 f762ff08 00000002 00000000
>>c19720ec 00000000 1f000217 c1a79400
>>Jan 5 16:22:48 t40 kernel: <0>00000032 00000001 c028bfb5 c0297262
>>c1a79400 c02972af 1f000207 c029727f
>>
>>
>
>hm, it's not clear what oopsed. Can you get a cleaner copy of this?
>
>
>
>>Jan 5 16:22:48 t40 kernel: <3>[drm:drm_release] *ERROR* Device busy: 1 0
>>
>>
>
>drm is unhappy
>
>
>
>
>
next prev parent reply other threads:[~2006-01-06 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 17:01 Re. 2.6.15-mm1 Alexander Gran
2006-01-05 22:47 ` Andrew Morton
2006-01-05 23:33 ` Alexander Gran
2006-01-06 0:21 ` Andrew Morton
2006-01-06 0:28 ` Dave Airlie
2006-01-06 0:38 ` Dave Jones
2006-01-06 9:30 ` Hans Reiser [this message]
2006-01-06 18:29 ` Alexander Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 23:31 Etienne Lorrain
2006-01-06 0:15 ` Andrew Morton
2006-01-06 0:36 ` Linus Torvalds
2006-01-06 10:04 ` Etienne Lorrain
2006-01-06 2:05 Seth, Rohit
2006-01-06 5:36 Brown, Len
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=43BE38AE.80203@namesys.com \
--to=reiser@namesys.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=alex@zodiac.dnsalias.org \
--cc=ambx1@neo.rr.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=vs@namesys.com \
--cc=zam@namesys.com \
/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