Menu
▾
▴
reactos-kernel
|
From: Royce M. I. <ro...@ev...> - 2002-07-11 18:30:44
|
Thanks! > >Subject: Re: [ros-kernel] How do I fix this? > From: Jason Filby <jas...@ya...> > Date: Thu, 11 Jul 2002 10:32:24 -0700 (PDT) > To: rea...@li... > >Congratulations :) > >--- Royce Mitchell III <ro...@ev...> wrote: >> Absolutely, will do that this evening, if my wife doesn't have the >> baby >> first ;) |
|
From: Royce M. I. <ro...@ev...> - 2002-07-11 18:31:40
|
Me too :) > >Subject: Re: [ros-kernel] How do I fix this? > From: Steven Edwards <ste...@ya...> > Date: Thu, 11 Jul 2002 11:07:32 -0700 (PDT) > To: rea...@li... > >Amen to that brother. Hope everything go wells Royce. > >--- Jason Filby <jas...@ya...> wrote: >> Congratulations :) >> >> --- Royce Mitchell III <ro...@ev...> wrote: >> > Absolutely, will do that this evening, if my wife >> doesn't have the >> > baby >> > first ;) > |
|
From: Royce M. I. <ro...@ev...> - 2002-07-11 23:53:20
|
Initializing system32\drivers\class2.sys... Initializing system32\drivers\disk.sys... (disk.c:115) Disk Class Driver 0.0.1 (disk.c:117) RegistryPath '\Registry\Machine\System\CurrentControlSet\Services\d isk' (disk.c:192) DiskClassFindDevices() called. (disk.c:203) PortCapabilities: c03678a6 (disk.c:204) MaximumTransferLength: 65536 (disk.c:205) MaximumPhysicalPages: 16 (disk.c:226) Found 1 Unclaimed devices! (disk.c:233) Searching bus 0 (disk.c:247) Vendor: 'WDC WD300BB-32AUA1 (disk.c:404) DiskClassCreateDeviceObject() called (disk.c:533) SectorSize: 512 (disk.c:338) DiskClassCheckReadWrite() called (disk.c:559) IoReadPartitionTable(): Status: 0 (disk.c:591) Read partition table! (disk.c:593) Number of partitions: 1 (disk.c:605) Partition 00: nr: 1 boot: 1 type: c offset: 63 size: 52484292 (disk.c:618) ScsiClassCreateDeviceObject(): Status 0 (disk.c:662) DiskClassCreateDeviceObjects() done (disk.c:274) DiskClassFindDevices() done (disk.c:192) DiskClassFindDevices() called. (disk.c:203) PortCapabilities: c0368302 (disk.c:204) MaximumTransferLength: 65536 (disk.c:205) MaximumPhysicalPages: 16 (disk.c:226) Found 1 unclaimed devices! (disk.c:233) Searching bus 0 (disk.c:247) Vendor: 'IOMEGA ZIP 100 ' (disk.c:404) DiskClassCreateDeviceObject() called Page fault at high IRQL was 12 Bug detected code: 0x1D Divide Error Exception: 0(2) Processor: 0 CS:EIP 8:c00e3f98 <hal.dll: 3f98> cr2 0 cr3 272000 Proc: c02ffaa6 Pid: 1 <SYSTEM> Thrd: c03106f4 Tid: 1 DS 10 ES 10 FS 30 GS 10 EAX: 00006868 EBX: c0376c7e ECX: 00005e3f EDX: 00000170 EBP: c00800b0 ESI: 00200000 EDI: c036b000 EFLAGS: 00010212 kESP: c0080038 kernel stack base c007e000 ESP c0080038 Frames: <(garbage): 195c><p(garbage): 2511><ntoskrnl.exe: 21c5><hal.dll: 5404><ha l.dll: 5458><hal.dll: 5563><hal.dll: 557f><ntoskrnl.exe: b813><p(garbage): 1d46><ntosk rnl.exe: 2cb38><p(garbage): 19c1><ntoskrnl.exe: 29f9a><ntoskrnl.exe: 29fcb><p(garbage) : 2a51><p(garbage): 25f8><p(garbage):626(garbage): 1d5c><ntoskrnl.exe: 26532><nto skrnl.exe: 33615><ntoskrnl.exe: aa54><ntoskrnl.exe: ab51><ntoskrnl.exe: b0f0><nt oskrnl.exe: 117c> |
|
From: Steven E. <ste...@ya...> - 2002-07-12 00:07:13
|
Have your tried it with the zip unpluged from the ide channel? > (disk.c:247) Vendor: 'IOMEGA ZIP 100 ' > (disk.c:404) DiskClassCreateDeviceObject() called > Page fault at high IRQL was 12 __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 00:27:20
|
I'm sure that would work, but wouldn't it be better to try to find out why it's crashing? ----- Original Message ----- From: "Steven Edwards" <ste...@ya...> To: <rea...@li...> Sent: Thursday, July 11, 2002 7:07 PM Subject: Re: [ros-kernel] disk.sys crash ( debug results ) > Have your tried it with the zip unpluged from the ide > channel? > > > (disk.c:247) Vendor: 'IOMEGA ZIP 100 ' > > (disk.c:404) DiskClassCreateDeviceObject() called > > Page fault at high IRQL was 12 > > > __________________________________________________ > Do You Yahoo!? > Sign up for SBC Yahoo! Dial - First Month Free > http://sbc.yahoo.com > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > PC Mods, Computing goodies, cases & more > http://thinkgeek.com/sf > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel > |
|
From: Steven E. <ste...@ya...> - 2002-07-12 00:31:09
|
Oh yeah, when I first read your emails I though you were still trying to make sure thats where the problem was. I was "multi-tasking" =) and didnt notice that you were trying to find the function that was hosed. Steven --- Royce Mitchell III <ro...@ev...> wrote: > I'm sure that would work, but wouldn't it be better > to try to find out why > it's crashing? __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 00:17:37
|
Crash is in ScsiClassSendSrbSynchronous.... rebooting again :) |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 00:25:22
|
crash is in IoCallDriver()... |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 01:05:27
|
crash is in call to DriverObject->MajorFunction[Param->MajorFunction] Irpsp 0xC036B2A6 MajorFunction 15 DriverObject->MajorFunction[Param->MajorFunction] dcb368f4 I'll start trying to figure out what function this is pointing to, but pointers would be appreciated :) |
|
From: Eric K. <ek...@rz...> - 2002-07-12 11:56:15
|
"Royce Mitchell III" <ro...@ev...> wrote: > crash is in call to DriverObject->MajorFunction[Param->MajorFunction] > > Irpsp 0xC036B2A6 > MajorFunction 15 > DriverObject->MajorFunction[Param->MajorFunction] dcb368f4 > > I'll start trying to figure out what function this is pointing to, but > pointers would be appreciated :) That should be a call to a dispatcher routine in scsiport.sys. I'd like to know whether the ZIP drive is an ATA/IDE or an ATAPI device. Please enable debug output of lines 941 and 959 in drivers/storage/atapi/atapi.c. AFAIK, Iomega made ATA and ATAPI Zip drives. Brrrrr.... :-/ Eric |
|
From: Royce M. I. <ro...@ev...> - 2002-07-13 01:33:02
|
Appx line 1174
Was:
DPRINT("waited %ld usecs for busy to clear\n", Retries * 10);
Should be ( I'm guessing ):
DPRINT("waited %ld usecs for busy to clear\n", RetryCount * 10);
|
|
From: Eric K. <ek...@rz...> - 2002-07-13 11:17:24
|
"Royce Mitchell III" <ro...@ev...> wrote:
> Appx line 1174
>
> Was:
>
> DPRINT("waited %ld usecs for busy to clear\n", Retries * 10);
>
> Should be ( I'm guessing ):
>
> DPRINT("waited %ld usecs for busy to clear\n", RetryCount * 10);
Yes, that's a typo. I'll fix it.
Eric
|
|
From: Rex J. <re...@lv...> - 2002-07-12 01:35:16
|
At 06:48 PM 7/11/02 -0500, you wrote: >Initializing system32\drivers\class2.sys... > >Initializing system32\drivers\disk.sys... [...] >(disk.c:404) DiskClassCreateDeviceObject() called >(disk.c:533) SectorSize: 512 [...] >(disk.c:247) Vendor: 'IOMEGA ZIP 100 ' >(disk.c:404) DiskClassCreateDeviceObject() called >Page fault at high IRQL was 12 >Bug detected code: 0x1D >Divide Error Exception: 0(2) Looks to me like the zip drive may be reporting a sector size of 0. Rex Jolliff re...@lv... |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 04:55:19
|
Hrmm... Could that be because there's no disk in the drive? > Looks to me like the zip drive may be reporting a sector size of 0. |
|
From: James T. <jim...@ad...> - 2002-07-12 05:34:43
|
Rex Jolliff wrote: > > At 06:48 PM 7/11/02 -0500, you wrote: > >Initializing system32\drivers\class2.sys... > > > >Initializing system32\drivers\disk.sys... > > [...] > > >(disk.c:404) DiskClassCreateDeviceObject() called > >(disk.c:533) SectorSize: 512 > > [...] > > >(disk.c:247) Vendor: 'IOMEGA ZIP 100 ' > >(disk.c:404) DiskClassCreateDeviceObject() called > >Page fault at high IRQL was 12 > >Bug detected code: 0x1D > >Divide Error Exception: 0(2) > > Looks to me like the zip drive may be reporting a sector size of 0. > > Rex Jolliff > re...@lv... > Yes, that would be normal for a ide zip drive with out a disk in it. Need to make an exception for handling drives with zero for a size. James |
|
From: David W. <we...@cw...> - 2002-07-12 06:59:00
|
On Thu, Jul 11, 2002 at 06:42:06PM -0700, Rex Jolliff wrote: > Looks to me like the zip drive may be reporting a sector size of 0. > One thing I ought to mention is that the trap number is no longer being reported correctly by the kernel. The place to start, as always, is to find out what routine the crash occurred in. I see from the copy of the crash report that the module was hal.dll so running addr2line --exe=/PATH/TO/REACTOS/hal/halx86/hal.dll 0x13f98 will give the line number. |
|
From: Royce M. I. <ro...@ev...> - 2002-07-12 12:42:03
|
C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x13f98 fake:0 C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x3f98 ??:0 C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0xc00e3f98 ??:0 :( |
|
From: Royce M. I. <ro...@ev...> - 2002-07-13 02:22:26
|
Could the reason why this is not working be because it's using the stripped hal.dll? ----- Original Message ----- From: "Royce Mitchell III" <ro...@ev...> To: <rea...@li...> Sent: Friday, July 12, 2002 7:37 AM Subject: Re: [ros-kernel] disk.sys crash ( debug results ) > C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x13f98 > fake:0 > > C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0x3f98 > ??:0 > > C:\reactos>addr2line --exe=c:\reactos\hal\halx86\hal.dll 0xc00e3f98 > ??:0 > > > :( > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Gadgets, caffeine, t-shirts, fun stuff. > http://thinkgeek.com/sf > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel > |
|
From: David W. <we...@cw...> - 2002-07-13 11:30:26
|
On Fri, Jul 12, 2002 at 09:17:54PM -0500, Royce Mitchell III wrote: > Could the reason why this is not working be because it's using the stripped > hal.dll? > Yes, it should be hal.nostrip.dll, sorry. |
|
From: Robert D. <od...@pn...> - 2002-07-13 12:44:05
|
Hi guys,
Is anybody currently maintaining the posix module? If so a clean checkout
from CVS
fails at the following point: (I haven't looked into it any further, about
to try os2 module)
<snip>
make -C apps/baresh
make[1]: Entering directory `F:/REACTOS/source/posix/apps/baresh'
gcc -D__SUBSYSTEM_WINDOWS__ -I../../../reactos/include -pipe
-march=i386 -c -o sh.o sh.c
windres \
--include-dir ../../../reactos/include \
--output-format coff \
sh.rc sh.coff
make[1]: *** No rule to make target `../../../reactos/dk/psx/lib/psxdll.a',
needed by `sh'. Stop.
make[1]: Leaving directory `F:/REACTOS/source/posix/apps/baresh'
make: *** [all] Error 2
|
|
From: KJK::Hyperion <no...@li...> - 2002-07-13 14:29:19
|
At 14.44 13/07/2002, you wrote: >Is anybody currently maintaining the posix module? yes, it's me. Please don't expect POSIX+ to even build. I'm in the middle of porting the RedHat newlib C runtime and scrapping my half-assed attempt at one, so most of the posix module should be considered dead meat until further notice |
|
From: Casper H. <ch...@us...> - 2002-07-13 13:28:25
|
I have just committed a patch that enables ReactOS to understand .stabs symbols (only line number, function names, and source file names though, but this is enough to get useful stack traces when not using a debugger). When ReactOS is configured for debugging, ReactOS will try to load symbols for every module it loads. E.g. if ReactOS loads ndis.sys, it will also load \SystemRoot\symbols\ndis.sym if this file exists. The .sym files generated by ReactOS dating before today are text files. The new .sym files are binary files extracted by the tools/rsym build utility from the non-stripped module image. If you have old .sym text files in your ReactOS installation, you had better remove them on your next update or expect trouble. Symbol files for user-mode modules are shared across processes and cached, so the performance degration of using the symbol files is not significant. A new FreeLoader is not required, but necesarry if you want to get useful stack traces for modules passed by FreeLoader. I have made a new FreeLoader snapshot available at: http://reactos.wox.org/download.php?id=24 and sources are available here: http://reactos.wox.org/download.php?id=25 Happy bug-hunting to you all ;-) Casper |
|
From: David W. <we...@cw...> - 2002-07-13 21:12:38
|
On Sat, Jul 13, 2002 at 03:18:36PM +0200, Casper Hornstrup wrote: > I have just committed a patch that enables ReactOS to understand .stabs > symbols (only line number, function names, and source file names though, > but this is enough to get useful stack traces when not using a > debugger). When ReactOS is configured for debugging, ReactOS will try to > load symbols for every module it loads. E.g. if ReactOS loads ndis.sys, > it will also load \SystemRoot\symbols\ndis.sym if this file exists. The > .sym files generated by ReactOS dating before today are text files. The > new .sym files are binary files extracted by the tools/rsym build > utility from the non-stripped module image. If you have old .sym text > files in your ReactOS installation, you had better remove them on your > next update or expect trouble. > I still think there are better ways to get the same functionality. The code for loading and parsing stabs should at least be localised in the kernel debugger code (ntoskrnl/kd/). |
|
From: Casper H. <ch...@us...> - 2002-07-13 22:14:40
|
s=F8n, 2002-07-14 kl. 00:12 skrev David Welch: > I still think there are better ways to get the same functionality. How? The code for loading and parsing stabs should at least be localised in the= kernel > debugger code (ntoskrnl/kd/). Okay. Casper |
|
From: David W. <we...@cw...> - 2002-07-14 11:00:54
|
On Sat, Jul 13, 2002 at 11:27:19PM +0200, Casper Hornstrup wrote: > How? > I think this feature rather falls between two stools: for non-technical users we need a core dump facility which can be automatically decoded offline and emailed to us; developers (who don't have two machines) need a kernel debugger which uses all debugging information and has source code available as well. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X