RE: usb regression in 2.6.24-rc4

2007-12-08 Thread Bob Gill
Hi.  Just a quick reply.  Is /proc/bus/usb empty?  Is there no symlink 
named devices (and so you can't cat devices to see what is there)?  
Also, (if /proc/bus/usb is empty), is /dev/bus/usb/devices not empty?  
(When you cat devices does it list usb devices you have plugged in?)  If 
so, then that's the problem I'm having.  Its very similar to yours, 
xsane points to the tv card only (not the scanner).  Something went away 
with the recent kernel.


Bob
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


RE: usb regression in 2.6.24-rc4

2007-12-08 Thread Bob Gill
Hi.  Just a quick reply.  Is /proc/bus/usb empty?  Is there no symlink 
named devices (and so you can't cat devices to see what is there)?  
Also, (if /proc/bus/usb is empty), is /dev/bus/usb/devices not empty?  
(When you cat devices does it list usb devices you have plugged in?)  If 
so, then that's the problem I'm having.  Its very similar to yours, 
xsane points to the tv card only (not the scanner).  Something went away 
with the recent kernel.


Bob
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


High cpu load due to pdflush

2007-11-03 Thread Bob Gill
Hi.  My computer is constipated.  The load average when idle never goes 
below 100%.  Top shows this:

top - 11:01:27 up 5 min,  2 users,  load average: 2.63, 1.73, 0.76
Tasks:  91 total,   2 running,  89 sleeping,   0 stopped,   0 zombie
Cpu(s): 13.5%us,  4.4%sy,  1.6%ni,  9.9%id, 70.2%wa,  0.3%hi,  0.2%si,  
0.0%st
Note that we are at 70% for the wait state, 9.9% idle.  Now when I run  
ps aux | grep pdflush | grep -v grep  ...I get:

root   144  0.0  0.0  0 0 ?S10:56   0:00 [pdflush]
root   145  0.0  0.0  0 0 ?D10:56   0:00 [pdflush]
the second pdflush is dirty (and won't write).  I haven't changed 
anything in /proc/sys/vm and am running the 2.6.24-rc1-git12 kernel on 
Ubuntu Gutsy.  The original Gutsy kernel worked fine.  The only way I 
can get around the problem is to go into a terminal and run:

>while true
>do
>sync
>sleep 10
>done
...which will force writes and give me (from top)
top - 11:06:55 up 10 min,  3 users,  load average: 0.42, 1.23, 0.85
Tasks:  93 total,   2 running,  91 sleeping,   0 stopped,   0 zombie
Cpu(s):  3.0%us,  0.9%sy,  0.0%ni, 95.6%id,  0.3%wa,  0.3%hi,  0.0%si,  
0.0%st

(on the very same load as before and the load is still dropping).

The only real change I made to Ubuntu was in 
/etc/init.d/mountdevsubfs.sh where I uncommented:

# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs 
-obusmode=0700,devmode=0600,listmode=0644

ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usb

...so that usb would work with a custom kernel...

Oh, and btw, my cpu is an Intel P4.
Also, I applied the following patch and build/ran a kernel (but it did 
not reduce the cpu load on my system):
>/> -- fs/jbd/transaction.c 
-/

>/> index cceaf57..d38e0d5 100644/
>/> @@ -55,7 +55,7 @@ get_transaction(journal_t *journal, transaction_t 
*transaction)/

>/> spin_lock_init(>t_handle_lock);/
>/> /
>/> /* Set up the commit timer for the new transaction. *//
>/> - journal->j_commit_timer.expires = 
round_jiffies(transaction->t_expires);/

>/> + journal->j_commit_timer.expires = transaction->t_expires;/
>/> add_timer(>j_commit_timer);/
>/> /
>/> J_ASSERT(journal->j_running_transaction == NULL);

/Any ideas?  Please mail me if you need more information. 
Thanks in Advance,

Bob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


High cpu load due to pdflush

2007-11-03 Thread Bob Gill
Hi.  My computer is constipated.  The load average when idle never goes 
below 100%.  Top shows this:

top - 11:01:27 up 5 min,  2 users,  load average: 2.63, 1.73, 0.76
Tasks:  91 total,   2 running,  89 sleeping,   0 stopped,   0 zombie
Cpu(s): 13.5%us,  4.4%sy,  1.6%ni,  9.9%id, 70.2%wa,  0.3%hi,  0.2%si,  
0.0%st
Note that we are at 70% for the wait state, 9.9% idle.  Now when I run  
ps aux | grep pdflush | grep -v grep  ...I get:

root   144  0.0  0.0  0 0 ?S10:56   0:00 [pdflush]
root   145  0.0  0.0  0 0 ?D10:56   0:00 [pdflush]
the second pdflush is dirty (and won't write).  I haven't changed 
anything in /proc/sys/vm and am running the 2.6.24-rc1-git12 kernel on 
Ubuntu Gutsy.  The original Gutsy kernel worked fine.  The only way I 
can get around the problem is to go into a terminal and run:

while true
do
sync
sleep 10
done
...which will force writes and give me (from top)
top - 11:06:55 up 10 min,  3 users,  load average: 0.42, 1.23, 0.85
Tasks:  93 total,   2 running,  91 sleeping,   0 stopped,   0 zombie
Cpu(s):  3.0%us,  0.9%sy,  0.0%ni, 95.6%id,  0.3%wa,  0.3%hi,  0.0%si,  
0.0%st

(on the very same load as before and the load is still dropping).

The only real change I made to Ubuntu was in 
/etc/init.d/mountdevsubfs.sh where I uncommented:

# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs  /dev/bus/usb/.usbfs 
-obusmode=0700,devmode=0600,listmode=0644

ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usb

...so that usb would work with a custom kernel...

Oh, and btw, my cpu is an Intel P4.
Also, I applied the following patch and build/ran a kernel (but it did 
not reduce the cpu load on my system):
/ -- fs/jbd/transaction.c 
-/

/ index cceaf57..d38e0d5 100644/
/ @@ -55,7 +55,7 @@ get_transaction(journal_t *journal, transaction_t 
*transaction)/

/ spin_lock_init(transaction-t_handle_lock);/
/ /
/ /* Set up the commit timer for the new transaction. *//
/ - journal-j_commit_timer.expires = 
round_jiffies(transaction-t_expires);/

/ + journal-j_commit_timer.expires = transaction-t_expires;/
/ add_timer(journal-j_commit_timer);/
/ /
/ J_ASSERT(journal-j_running_transaction == NULL);

/Any ideas?  Please mail me if you need more information. 
Thanks in Advance,

Bob
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 2.6.12-rc3:microtek.c:338: error: for each function it appears in.

2005-04-23 Thread Bob Gill
Thank you.
On Fri, 2005-04-22 at 08:20 +0200, Oliver Neukum wrote:
> Am Freitag, 
> 22. April 2005 03:20 schrieb Bob Gill:
> > OK.  I downloaded, patched and started the build.  Basically everything
> > stops when I get a "microtek.c:338: error: `FAILURE' undeclared" error
> 
> Known problem. Fix in the pipeline.
> 
>       Regards
>   Oliver
-- 
Bob Gill <[EMAIL PROTECTED]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 2.6.12-rc3:microtek.c:338: error: for each function it appears in.

2005-04-23 Thread Bob Gill
Thank you.
On Fri, 2005-04-22 at 08:20 +0200, Oliver Neukum wrote:
 Am Freitag, 
 22. April 2005 03:20 schrieb Bob Gill:
  OK.  I downloaded, patched and started the build.  Basically everything
  stops when I get a microtek.c:338: error: `FAILURE' undeclared error
 
 Known problem. Fix in the pipeline.
 
   Regards
   Oliver
-- 
Bob Gill [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 2.6.12-rc3:microtek.c:338: error: for each function it appears in.

2005-04-21 Thread Bob Gill
OK.  I downloaded, patched and started the build.  Basically everything
stops when I get a "microtek.c:338: error: `FAILURE' undeclared" error
(the build keeps trying, but no modules get created).  
I suspect others may have the same problem, but feel free to e-mail me
for more information (and you will have to as I am not on the list).
...ok, also I have tried adding 
 #define MTS_SCSI_ERR_MASK ~0x3fu
>#define FAILURE   ~0x3fu
on line 55 of microtek.h ...basically a copycat of the previous error
line...(but I suspect the kernel maintainer would be a better person to
define FAILURE somewhere...)
And...it does boot and I can
taint.the.kernel.with.nvidia.video

TIA,
Bob
-- 
Bob Gill <[EMAIL PROTECTED]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 2.6.12-rc3:microtek.c:338: error: for each function it appears in.

2005-04-21 Thread Bob Gill
OK.  I downloaded, patched and started the build.  Basically everything
stops when I get a microtek.c:338: error: `FAILURE' undeclared error
(the build keeps trying, but no modules get created).  
I suspect others may have the same problem, but feel free to e-mail me
for more information (and you will have to as I am not on the list).
...ok, also I have tried adding 
 #define MTS_SCSI_ERR_MASK ~0x3fu
#define FAILURE   ~0x3fu
on line 55 of microtek.h ...basically a copycat of the previous error
line...(but I suspect the kernel maintainer would be a better person to
define FAILURE somewhere...)
And...it does boot and I can
coughtaint.the.kernel.with.nvidia.videocough

TIA,
Bob
-- 
Bob Gill [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 2.6.12-rc2

2005-04-06 Thread Bob Gill
OK.  So far so good.  I can get 2.6.12-rc2 to run fine if:
1. I do not in any way attempt to *ahem* overclock the box.
--if I do, I get really ugly race errors flying around from just about
everywhere (pick a device at random, have it trip, and the scheduler
tripping right behind it).
2. I do not attempt in any way to run any sort of Nvidia (non-GPL)
driver.  It fights with SBP2 (in a lot of different ways, first the
drivers want to kill off Firewire drives (one detected, the other not,
then on next boot, the reverse...), and also, when using GLX apps (and
trying to write to an SBP2 connected device, they clash (and fight and
the kernel doesn't die but gets bogged in errors...)
and with the notes above, as I say, so far, so good.  I am
attempting to hammer away at every device I have on the box (scanner,
printer, video (only GPL Nvidia), audio, cd, dvd, tv tuner etc.) so far,
so good.
Bob
-- 
Bob Gill <[EMAIL PROTECTED]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Linux 2.6.12-rc2

2005-04-06 Thread Bob Gill
OK.  So far so good.  I can get 2.6.12-rc2 to run fine if:
1. I do not in any way attempt to *ahem* overclock the box.
--if I do, I get really ugly race errors flying around from just about
everywhere (pick a device at random, have it trip, and the scheduler
tripping right behind it).
2. I do not attempt in any way to run any sort of Nvidia (non-GPL)
driver.  It fights with SBP2 (in a lot of different ways, first the
drivers want to kill off Firewire drives (one detected, the other not,
then on next boot, the reverse...), and also, when using GLX apps (and
trying to write to an SBP2 connected device, they clash (and fight and
the kernel doesn't die but gets bogged in errors...)
and with the notes above, as I say, so far, so good.  I am
attempting to hammer away at every device I have on the box (scanner,
printer, video (only GPL Nvidia), audio, cd, dvd, tv tuner etc.) so far,
so good.
Bob
-- 
Bob Gill [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: ... no drivers for IEEE1394 product 0x/0x/0x in kernel 2.6.12-rc1-bk6

2005-04-05 Thread Bob Gill
Actually I don't use CONFIG_DEVFS_FS as it tends to break things here
(and I found wasn't necessary for things to work, in fact it got in the
way of some things working, some of the autodetect/hotplug peripherels
didn't like it).  Thank you for the reply though.
Bob

On Mon, 2005-04-04 at 20:14 -0700, Barry K. Nathan wrote:
> On Mon, Apr 04, 2005 at 08:22:56PM -0600, Bob Gill wrote:
> > Hi.  I recently built 2.6.12-rc1-bk6.  The kernel seems to be tripping
> > over sbp2.  The error messages keep right on rolling till I hit the
> > reboot button (I let it run for more than 90 seconds last time).
> > 2.6.11.6 builds/runs without any problems.
> [snip]
> 
> I was having the same problem on a system of mine too, but it went away
> after I disabled CONFIG_DEVFS_FS. You didn't include enough of your
> .config for me to be able to tell if that is at all relevant in your
> case however.
> 
> -Barry K. Nathan <[EMAIL PROTECTED]>
-- 
Bob Gill <[EMAIL PROTECTED]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: ... no drivers for IEEE1394 product 0x/0x/0x in kernel 2.6.12-rc1-bk6

2005-04-05 Thread Bob Gill
Actually I don't use CONFIG_DEVFS_FS as it tends to break things here
(and I found wasn't necessary for things to work, in fact it got in the
way of some things working, some of the autodetect/hotplug peripherels
didn't like it).  Thank you for the reply though.
Bob

On Mon, 2005-04-04 at 20:14 -0700, Barry K. Nathan wrote:
 On Mon, Apr 04, 2005 at 08:22:56PM -0600, Bob Gill wrote:
  Hi.  I recently built 2.6.12-rc1-bk6.  The kernel seems to be tripping
  over sbp2.  The error messages keep right on rolling till I hit the
  reboot button (I let it run for more than 90 seconds last time).
  2.6.11.6 builds/runs without any problems.
 [snip]
 
 I was having the same problem on a system of mine too, but it went away
 after I disabled CONFIG_DEVFS_FS. You didn't include enough of your
 .config for me to be able to tell if that is at all relevant in your
 case however.
 
 -Barry K. Nathan [EMAIL PROTECTED]
-- 
Bob Gill [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


... no drivers for IEEE1394 product 0x/0x/0x in kernel 2.6.12-rc1-bk6

2005-04-04 Thread Bob Gill
ers).

As I say, things are working ok with 2.6.11.6 (what I'm using to mail
this).
You will have to mail me back as I'm not on the list.

TIA,
Bob
-- 
Bob Gill <[EMAIL PROTECTED]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


... no drivers for IEEE1394 product 0x/0x/0x in kernel 2.6.12-rc1-bk6

2005-04-04 Thread Bob Gill
 Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev
d0)
00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI
Fast Ethernet (rev 90)
00:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
07)
00:09.1 Input device controller: Creative Labs SB Live! MIDI/Game Port
(rev 07)
00:0b.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 02)
00:0b.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 02)

00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 43)

01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti
4200] (rev a3)
(emphasis mine)

.
While it's true I tend to default to nVidia drivers for graphics/video,
I have not (yet) tainted the kernel with any such drivers (this is the
first boot, no foreign drivers).

As I say, things are working ok with 2.6.11.6 (what I'm using to mail
this).
You will have to mail me back as I'm not on the list.

TIA,
Bob
-- 
Bob Gill [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Nasty ReiserFS bug in 2.6.12-rc1, 2.6.12-rc1-bk1

2005-03-19 Thread Bob Gill
0x1001/6878
Mar 19 12:25:13 localhost kernel:  [] schedule+0x558/0x606
Mar 19 12:25:13 localhost kernel:  [] unmap_page_range
+0x7f/0xb6
Mar 19 12:25:13 localhost kernel:  [] cond_resched+0x27/0x40
Mar 19 12:25:13 localhost kernel:  [] unmap_vmas+0x209/0x21d
Mar 19 12:25:13 localhost kernel:  [] exit_mmap+0x84/0x15b
Mar 19 12:25:13 localhost kernel:  [] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [] mmput+0x2b/0x8e
Mar 19 12:25:13 localhost kernel:  [] do_exit+0xba/0x3a1
Mar 19 12:25:13 localhost kernel:  [] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [] do_trap+0x0/0xd5
Mar 19 12:25:13 localhost kernel:  [] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [] printk+0x17/0x1b
Mar 19 12:25:13 localhost kernel:  [] do_page_fault
+0x3c4/0x5c7
Mar 19 12:25:13 localhost kernel:  [] as_update_arq+0x25/0x5a
Mar 19 12:25:13 localhost kernel:  [] as_add_request
+0x1c8/0x25a
Mar 19 12:25:13 localhost kernel:  [] __elv_add_request
+0x84/0xb4
Mar 19 12:25:13 localhost kernel:  [] mempool_alloc+0x75/0x170
Mar 19 12:25:13 localhost kernel:  [] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [] error_code+0x2b/0x30
Mar 19 12:25:13 localhost kernel:  [] as_find_arq_hash
+0x38/0x7d
Mar 19 12:25:13 localhost kernel:  [] as_merge+0x64/0x1ad
Mar 19 12:25:13 localhost kernel:  [] __make_request
+0xac/0x4ed
Mar 19 12:25:13 localhost kernel:  [] generic_make_request
+0x90/0x1ff
Mar 19 12:25:13 localhost kernel:  [] bio_alloc_bioset
+0x10f/0x1bf
Mar 19 12:25:13 localhost kernel:  [] autoremove_wake_function
+0x0/0x4 b
Mar 19 12:25:13 localhost kernel:  [] autoremove_wake_function
+0x0/0x4 b
Mar 19 12:25:13 localhost kernel:  [] do_mpage_readpage
+0x28e/0x3c7
Mar 19 12:25:13 localhost kernel:  [] submit_bio+0x4d/0xdc
Mar 19 12:25:13 localhost kernel:  [] radix_tree_insert
+0x83/0x12a
Mar 19 12:25:13 localhost kernel:  [] __pagevec_lru_add
+0xde/0x107
Mar 19 12:25:13 localhost kernel:  [] mpage_bio_submit
+0x2b/0x32
Mar 19 12:25:13 localhost kernel:  [] mpage_readpages
+0xd3/0x173
Mar 19 12:25:13 localhost kernel:  [] reiserfs_get_block
+0x0/0x1530
Mar 19 12:25:13 localhost kernel:  [] read_pages+0x13f/0x14f
Mar 19 12:25:13 localhost kernel:  [] reiserfs_get_block
+0x0/0x1530
Mar 19 12:25:13 localhost kernel:  [] __alloc_pages
+0x173/0x3e1
Mar 19 12:25:13 localhost kernel:  []
__do_page_cache_readahead+0x14c/ 0x183
Mar 19 12:25:13 localhost kernel:  [] filemap_nopage
+0x29a/0x3d9
Mar 19 12:25:13 localhost kernel:  [] filemap_nopage+0x0/0x3d9
Mar 19 12:25:13 localhost kernel:  [] do_no_page+0xaf/0x3a5
Mar 19 12:25:13 localhost kernel:  [] pte_alloc_map+0x99/0xbe
Mar 19 12:25:13 localhost kernel:  [] handle_mm_fault
+0x16e/0x1b0
Mar 19 12:25:13 localhost kernel:  [] do_page_fault
+0x1c5/0x5c7
Mar 19 12:25:13 localhost kernel:  [] do_mmap_pgoff
+0x4a7/0x78e
Mar 19 12:25:13 localhost kernel:  [] sys_mmap2+0x7a/0xa9
Mar 19 12:25:13 localhost kernel:  [] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [] error_code+0x2b/0x30
Mar 19 12:27:16 localhost su(pam_unix)[7554]: session opened for user
root by bo b(uid=500)
Mar 19 12:35:45 localhost gpm[5318]: *** info [mice.c(1766)]:


... When booted with 2.6.11-4, unmounted and checked with reiserfsck it
shows
Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
###
reiserfsck --check started at Sat Mar 19 12:46:48 2005
###
Replaying journal..
Reiserfs journal '/dev/hdb1' in blocks [18..8211]: 0 transactions
replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 185935
Internal nodes 1237
Directories 617339
Other files 1196346
Data block pointers 14019144 (162053 of them are zero)
Safe links 0
###
reiserfsck finished at Sat Mar 19 13:05:10 2005
###
It may not be a ReiserFS problem, but something that tripped some
ReiserFS code... 
...So my drive isn't dead/corrupted, and all data is accessable when
booting with an older kernel.  Please feel free to mail me for more info
(and you will have to as I'm not on the list).

TIA,
Bob
-- 
Bob Gill <[EMAIL PROTECTED]>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Nasty ReiserFS bug in 2.6.12-rc1, 2.6.12-rc1-bk1

2005-03-19 Thread Bob Gill
 6c 75 04 a8 10 75 1c 89 54 24 04
8b 07 89 04 24 e8
Mar 19 12:25:13 localhost kernel:  6note: cc1[6878] exited with
preempt_count
1
Mar 19 12:25:13 localhost kernel: scheduling while atomic:
cc1/0x1001/6878
Mar 19 12:25:13 localhost kernel:  [c02b2098] schedule+0x558/0x606
Mar 19 12:25:13 localhost kernel:  [c01426c8] unmap_page_range
+0x7f/0xb6
Mar 19 12:25:13 localhost kernel:  [c02b288e] cond_resched+0x27/0x40
Mar 19 12:25:13 localhost kernel:  [c0142908] unmap_vmas+0x209/0x21d
Mar 19 12:25:13 localhost kernel:  [c0147277] exit_mmap+0x84/0x15b
Mar 19 12:25:13 localhost kernel:  [c01129f4] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [c0115977] mmput+0x2b/0x8e
Mar 19 12:25:13 localhost kernel:  [c011a06f] do_exit+0xba/0x3a1
Mar 19 12:25:13 localhost kernel:  [c01129f4] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [c010406e] do_trap+0x0/0xd5
Mar 19 12:25:13 localhost kernel:  [c01129f4] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [c0118021] printk+0x17/0x1b
Mar 19 12:25:13 localhost kernel:  [c0112db8] do_page_fault
+0x3c4/0x5c7
Mar 19 12:25:13 localhost kernel:  [c021cde5] as_update_arq+0x25/0x5a
Mar 19 12:25:13 localhost kernel:  [c021daea] as_add_request
+0x1c8/0x25a
Mar 19 12:25:13 localhost kernel:  [c021542a] __elv_add_request
+0x84/0xb4
Mar 19 12:25:13 localhost kernel:  [c0137fba] mempool_alloc+0x75/0x170
Mar 19 12:25:13 localhost kernel:  [c01129f4] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [c0103907] error_code+0x2b/0x30
Mar 19 12:25:13 localhost kernel:  [c021c4af] as_find_arq_hash
+0x38/0x7d
Mar 19 12:25:13 localhost kernel:  [c021de95] as_merge+0x64/0x1ad
Mar 19 12:25:13 localhost kernel:  [c02188f5] __make_request
+0xac/0x4ed
Mar 19 12:25:13 localhost kernel:  [c0219044] generic_make_request
+0x90/0x1ff
Mar 19 12:25:13 localhost kernel:  [c015762a] bio_alloc_bioset
+0x10f/0x1bf
Mar 19 12:25:13 localhost kernel:  [c012b3b7] autoremove_wake_function
+0x0/0x4 b
Mar 19 12:25:13 localhost kernel:  [c012b3b7] autoremove_wake_function
+0x0/0x4 b
Mar 19 12:25:13 localhost kernel:  [c017536d] do_mpage_readpage
+0x28e/0x3c7
Mar 19 12:25:13 localhost kernel:  [c0219200] submit_bio+0x4d/0xdc
Mar 19 12:25:13 localhost kernel:  [c01be8a9] radix_tree_insert
+0x83/0x12a
Mar 19 12:25:13 localhost kernel:  [c013e309] __pagevec_lru_add
+0xde/0x107
Mar 19 12:25:13 localhost kernel:  [c0174fc4] mpage_bio_submit
+0x2b/0x32
Mar 19 12:25:13 localhost kernel:  [c0175579] mpage_readpages
+0xd3/0x173
Mar 19 12:25:13 localhost kernel:  [c018fd2d] reiserfs_get_block
+0x0/0x1530
Mar 19 12:25:13 localhost kernel:  [c013b747] read_pages+0x13f/0x14f
Mar 19 12:25:13 localhost kernel:  [c018fd2d] reiserfs_get_block
+0x0/0x1530
Mar 19 12:25:13 localhost kernel:  [c01394e2] __alloc_pages
+0x173/0x3e1
Mar 19 12:25:13 localhost kernel:  [c013b8a3]
__do_page_cache_readahead+0x14c/ 0x183
Mar 19 12:25:13 localhost kernel:  [c0135b71] filemap_nopage
+0x29a/0x3d9
Mar 19 12:25:13 localhost kernel:  [c01358d7] filemap_nopage+0x0/0x3d9
Mar 19 12:25:13 localhost kernel:  [c0143fd6] do_no_page+0xaf/0x3a5
Mar 19 12:25:13 localhost kernel:  [c0142101] pte_alloc_map+0x99/0xbe
Mar 19 12:25:13 localhost kernel:  [c0144530] handle_mm_fault
+0x16e/0x1b0
Mar 19 12:25:13 localhost kernel:  [c0112bb9] do_page_fault
+0x1c5/0x5c7
Mar 19 12:25:13 localhost kernel:  [c0146224] do_mmap_pgoff
+0x4a7/0x78e
Mar 19 12:25:13 localhost kernel:  [c0108813] sys_mmap2+0x7a/0xa9
Mar 19 12:25:13 localhost kernel:  [c01129f4] do_page_fault+0x0/0x5c7
Mar 19 12:25:13 localhost kernel:  [c0103907] error_code+0x2b/0x30
Mar 19 12:27:16 localhost su(pam_unix)[7554]: session opened for user
root by bo b(uid=500)
Mar 19 12:35:45 localhost gpm[5318]: *** info [mice.c(1766)]:


... When booted with 2.6.11-4, unmounted and checked with reiserfsck it
shows
Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
###
reiserfsck --check started at Sat Mar 19 12:46:48 2005
###
Replaying journal..
Reiserfs journal '/dev/hdb1' in blocks [18..8211]: 0 transactions
replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 185935
Internal nodes 1237
Directories 617339
Other files 1196346
Data block pointers 14019144 (162053 of them are zero)
Safe links 0
###
reiserfsck finished at Sat Mar 19 13:05:10 2005
###
It may not be a ReiserFS problem, but something that tripped some
ReiserFS code... 
...So my drive isn't dead/corrupted, and all data is accessable when
booting with an older kernel.  Please feel free to mail me for more info
(and you will have to as I'm not on the list).

TIA,
Bob
-- 
Bob Gill [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ